HyperMesh 11.0 User Guide

HyperWorks 11.
0 HyperMesh User Guide
Altair Engineering Contact Information

Web site FTP site www.altair.com Address: ftp.altair.com or ftp2.altair.com or http://ftp.altair.com/ftp Login: ftp Password: <your e-mail address>
Location
North America China France Germany India
Telephone
248.614.2425 86.400.619.6186. 33.1.4133.0992 49.7031.6208.22 91.80.6629.4500 1800.425.0234 (toll free) 39.800.905.595 81.3.5396.2881 82.70.4050.9200 46.46.286.2052 01926 .468.600 55.11.3384.0414 61.3.9016.9042 64.9.413.7981
e-mail
hwsupport@altair.com support@altair.com.cn francesupport@altair.com hwsupport@altair.de support@india.altair.com
Italy Japan Korea Scandinavia United Kingdom Brazil Australia New Zealand
support@altairengineering.it support@altairjp.co.jp help@altair.co.kr support@altair.se support@uk.altair.com br_support@altair.com.br anzsupport@altair.com anzsupport@altair.com
The following countries have distributors for Altair Engineering: Asia Pacific: Indonesia, Malaysia, Singapore, Taiwan, Thailand Europe: Czech Republic, Hungary, Poland, Romania, Spain, Turkey. 2011 Altair Engineering, Inc. All rights reserved. No part of this publication may be reproduced, transmitted, transcribed, stored in a retrieval system, or translated to another language without the written permission of Altair Engineering, Inc. To obtain this permission, write to the attention Altair Engineering legal department at: 1820 E. Big Beaver, Troy, Michigan, USA, or call +1-248-614-2400.
HyperWorks 11.0 Release Notes
Listed below are Altair HyperWorks applications. Copyright Altair Engineering Inc., All Rights Reserved for: HyperMesh 1990-2011; HyperCrash 2001-2011; OptiStruct 1996-2011; RADIOSS 1986-2011; HyperView 1999-2011; HyperView Player 2001-2011; HyperStudy 1999-2011; HyperGraph 1995-2011; MotionView 1993 2011; MotionSolve 2002-2011; HyperForm 1998-2011; HyperXtrude 1999-2011; Process Manager 2003-2011; Templex 1990-2011; Data Manager 2005-2011; MediaView 1999-2011; BatchMesher 2003-2011; TextView 1996-2011; HyperMath 2007-2011; ScriptView 2007-2011; Manufacturing Solutions 2005-2011; HyperWeld 2009-2011; HyperMold 2009-2011; solidThinking 1993-2011; solidThinking Inspired 2009-2011; Durability Director 2009-2011; Suspension Director 2009-2011; AcuSolve 1997-2011; and AcuConsole 2006-2011. In addition to HyperWorks trademarks noted above, GridWorks, PBS Gridworks, PBS Professional, PBS and Portable Batch System are trademarks of ALTAIR ENGINEERING INC., as is patent # 6,859,792. All are protected under U.S. and international laws and treaties. All other marks are the property of their respective owners.
Trademark and Registered Trademark Acknowledgments
Altair HyperMesh User's Guide
Graphical User Interface Toolbar/Panel Changes in HyperMesh 11.0 ...........................................................................................................................................2 Standard Toolbar Changes ...........................................................................................................................................3 Standard Views Toolbar Changes ...........................................................................................................................................5 Visualization Toolbar Changes ...........................................................................................................................................6 Geometry Panel Changes ...........................................................................................................................................8 HyperMesh Color Options dialog ...........................................................................................................................................14 HyperMesh Menu Bar ...........................................................................................................................................19 HyperMesh Toolbars ...........................................................................................................................................22 Collectors Toolbar ...........................................................................................................................................23 Checks Toolbar ...........................................................................................................................................25 Display Toolbar ...........................................................................................................................................27 Visualization Toolbar ...........................................................................................................................................29 Element and ply visualization ..............................................................................................................................37 HyperMesh tabs ...........................................................................................................................................40 HyperMesh Calculator ...........................................................................................................................................41 Browsers Basic Browser Operations ...........................................................................................................................................44 Sorting Entities ...........................................................................................................................................46 Filtering Entities ...........................................................................................................................................47 Finding Entities ...........................................................................................................................................50 Dialogs ...........................................................................................................................................52 Connector Browser ...........................................................................................................................................54 Link Entity Browser ...........................................................................................................................................56 Link Entity Browser Action Modes Tools ..............................................................................................................................57 Link Entity Browser View Option Toggle buttons ..............................................................................................................................59 Link Entity Browser Advanced Action Buttons ..............................................................................................................................65 Link Entity Browser Global Display Tools ..............................................................................................................................66 Link Entity Browser Context Menu ..............................................................................................................................67 Link Entity Browser Configuration Window ..............................................................................................................................69 Connector Entity Browser ...........................................................................................................................................71 Connector Entity Browser Action Modes Tools ..............................................................................................................................74 Connector Entity Browser View Option Toggle Buttons ..............................................................................................................................76 Connector Entity Browser Advanced Action Buttons ..............................................................................................................................82 Connector Entity Browser Global Display Tools ..............................................................................................................................83 Connector Entity Browser Context Menu ..............................................................................................................................84 Connector Entity Browser Configuration Window ..............................................................................................................................88
Altair Engineering

Proprietary Inform ation of Altair Engineering
Utility Tool Set - Connector Browser ...........................................................................................................................................91 Link Definition ...........................................................................................................................................92 Add Link ...........................................................................................................................................93 Remove Links ...........................................................................................................................................96 Update Links ...........................................................................................................................................97 Modifying Link Rules ..............................................................................................................................100 Modifying Link States ..............................................................................................................................103 Part Replacement ..............................................................................................................................106 Find Connectors from Parts or Links ...........................................................................................................................................111 Find Connectors from Realizations ...........................................................................................................................................112 Find Links from Connectors ...........................................................................................................................................113 Entity State Browser ...........................................................................................................................................114 Entity State Browser Context Menu ...........................................................................................................................................116 Model Browser ...........................................................................................................................................118 Model Browser Views ...........................................................................................................................................122 Model ..............................................................................................................................129 Browser Optimization View Model ..............................................................................................................................131 Browser Include View Direct/Indirect Property Assignment ..............................................................................................................................133 Direct/Indirect Property View ..............................................................................................................................135 Display Controls & Browser Modes ...........................................................................................................................................140 Global ..............................................................................................................................141 Display Tools Local Display Controls ..............................................................................................................................142 Action ..............................................................................................................................144 Mode Tools Context-Sensitive Menu ...........................................................................................................................................152 Configuring the Model Browser ...........................................................................................................................................156 Loadsteps Browser ...........................................................................................................................................158 Loadsteps Browser: OptiStruct & Nastran Profiles ...........................................................................................................................................160 To Create a New Loadstep ..............................................................................................................................162 To Edit a Loadstep ..............................................................................................................................163 To Display a Loadstep ..............................................................................................................................165 To Rename, Renumber, Delete, or Edit the Card of a Loadstep ..............................................................................................................................166 To Edit the Global Options of a Loadstep ..............................................................................................................................167 Loadsteps: Auto-manage Load References ..............................................................................................................................168 Mask Browser ...........................................................................................................................................169 Mask Browser Context Menu ...........................................................................................................................................171 Set...........................................................................................................................................172 Browser To Set Display Options for the Set Browser ...........................................................................................................................................173 To Use the Set Browser's Right-click Functionality ...........................................................................................................................................174 To Change the Set Browser's Display and Export States ...........................................................................................................................................176 Solver Browser ...........................................................................................................................................177 Utility Menus ...........................................................................................................................................181
ii

Altair Engineering
Default Utility Menu ...........................................................................................................................................183 QA/Model Utility Menu ...........................................................................................................................................184 BOM Comparison Tool ..............................................................................................................................187 BOM Comparison Tool GUI ..........................................................................................................................188 BOM Comparison Tool Control Section ..........................................................................................................................190 BOM Comparison Tool Tree Section ..........................................................................................................................192 BOM Comparison Tool Master Column ..........................................................................................................................194 BOM Comparison Tool BOM Display Section ..........................................................................................................................195 BOM Comparison Tool Metadata Display Section ..........................................................................................................................198 BOM Comparison Tool Failed Records Section ..........................................................................................................................199 Disp Utility Menu ...........................................................................................................................................200 Geom/Mesh Utility Menu ...........................................................................................................................................201 Preserve Edges ..............................................................................................................................203 Project Points ..............................................................................................................................205 Auto Connectors Macro ..............................................................................................................................206 Master Weld Files ..........................................................................................................................209 Diameter vs. Thickness Files ..........................................................................................................................210 ACM Welds ..........................................................................................................................211 CWELD Elements ..........................................................................................................................214 Midsurf Thickness ..............................................................................................................................215 To assign thickness and z-offset values using the Elements option ..........................................................................................................................219 To assign thickness and z-offset values using the Properties on Components option ..........................................................................................................................220 To assign thickness and z-offset values using the Properties on Elements option ..........................................................................................................................221 To organize elements using the Organize Only option ..........................................................................................................................222 To contour thickness and z-offset values using the Elements option ..........................................................................................................................223 To contour thickness and z-offset values using the Properties on Components option ..........................................................................................................................224 To contour thickness and z-offset values using the Properties on Elements option ..........................................................................................................................225 Gauge..........................................................................................................................226 File Format & Example Midsurf Thickness Behavior Under Different User Profiles ..........................................................................................................................227 Quick TetraMesh ..............................................................................................................................235 Fix 2nd Order Midnodes ..............................................................................................................................239 Add Washer ..............................................................................................................................243 Trim Hole Macro ..............................................................................................................................246 Fill Hole Macro ..............................................................................................................................248 Box Trim Macro ..............................................................................................................................250 Bead utility ..............................................................................................................................253 Fix Sliver Tetra Elements ..............................................................................................................................255 Abaqus Utility Menu ...........................................................................................................................................259 Contact Manager ..............................................................................................................................261
Altair Engineering

iii
Interface Tab ..........................................................................................................................263 Surface Tab ..........................................................................................................................290 Surface Interaction Tab ..........................................................................................................................330 Dummy Positioning Process Manager ..............................................................................................................................341 Solid Face Alignment Utility ..............................................................................................................................343 Step Manager ..............................................................................................................................344 Step Manager Dialog Environment ..........................................................................................................................347 Step Manager Tab Environment ..........................................................................................................................349 Abaqus Step Manager Step Tab ..........................................................................................................................350 Abaqus Step Manager Load Case Tab ..........................................................................................................................430 ANSYS Utility Menu ...........................................................................................................................................432 ANSYS Component Manager ..............................................................................................................................433 To Create a Component Collector ..........................................................................................................................435 To Create a Component Card with the Component Manager ..........................................................................................................................437 To Edit a Component Card ..........................................................................................................................438 ANSYS Material Macro ..............................................................................................................................439 Create..........................................................................................................................441 Material Dialog Edit Material Dialog ..........................................................................................................................442 ANSYS Section Macro ..............................................................................................................................443 Create..........................................................................................................................445 Section Dialog Edit Section Dialog ..........................................................................................................................447 To Create a SECDATA Card with the Section Macro ..........................................................................................................................449 ANSYS Real Sets Macro ..............................................................................................................................453 Create..........................................................................................................................455 Real Sets Dialog Edit Real Sets Dialog ..........................................................................................................................456 ANSYS ET Type Macro ..............................................................................................................................457 Create..........................................................................................................................459 ETType Dialog Edit ETType Dialog ..........................................................................................................................460 ANSYS Convert to Special 2nd Order Macro ..............................................................................................................................461 ANSYS Contact Manger ..............................................................................................................................464 Auto Contact - ANSYS Interface ..........................................................................................................................469 To Set..........................................................................................................................471 Up an Auto Contact Run Auto Contact Browser ..........................................................................................................................473 Modifying Auto Contact Entities ..........................................................................................................................475 Modal ..............................................................................................................................476 Analysis Tool LS-DYNA Utility Menu ...........................................................................................................................................477 Error Check ..............................................................................................................................479 Part Info ..............................................................................................................................482 Name Mapping ..............................................................................................................................483 Clone Part ..............................................................................................................................484 Create..............................................................................................................................485 Part
iv

Altair Engineering
Part Replacement ..............................................................................................................................486 To use..............................................................................................................................492 the Convert To Rigid macro Convert To Rigid Flow Chart ..............................................................................................................................493 Component Table ..............................................................................................................................494 Material Table ..............................................................................................................................499 Customizing Views of the Material Table ..........................................................................................................................501 Creating, Editing, and Loading Materials ..........................................................................................................................503 Managing Materials ..........................................................................................................................505 Sort Materials ..........................................................................................................................506 Create..........................................................................................................................507 a New Material Edit a ..........................................................................................................................508 Material's Properties Merge..........................................................................................................................509 Materials Find Duplicate Materials ..........................................................................................................................510 See the Load Curve for a Material ..........................................................................................................................511 Export..........................................................................................................................512 Data from the Material Table MADYMO Utility Menu ...........................................................................................................................................513 NASTRAN Utility Menu ...........................................................................................................................................516 Nastran1 Page ..............................................................................................................................517 BCTABLE Manager ..........................................................................................................................518 Nastran Part Replacement ..........................................................................................................................521 Rigid Spider ..........................................................................................................................525 PartInfo ..........................................................................................................................526 Component Table ..........................................................................................................................527 Property Table ..........................................................................................................................534 Materials Table ..........................................................................................................................538 RSSCON Create ..........................................................................................................................539 RSPLINE Create ..........................................................................................................................540 TABLE Create ..........................................................................................................................541 Nastran2 Page ..............................................................................................................................543 Convert Shells ..........................................................................................................................544 Display SETs ..........................................................................................................................545 Tag on Nodes ..........................................................................................................................546 SPOINT ..........................................................................................................................547 PAM-CRASH 2G Utility Menu ...........................................................................................................................................548 Tool Menu ..............................................................................................................................549 Dummy Positioning Tool Start Macro ..........................................................................................................................552 Part Replacement Macro ..........................................................................................................................557 Part Info Macro ..........................................................................................................................559 Substructure Tool Macro ..........................................................................................................................560 RBODY Manager Macro ..........................................................................................................................561 Apply ..........................................................................................................................564 Initial Metric Macro
Altair Engineering

Organize Xlinks Macro ..........................................................................................................................565 MASS..........................................................................................................................566 Manager Macro Input Fields in the Show ID Ranges User Interface ..........................................................................................................................567 Find Menu ..............................................................................................................................568 Card Menu ..............................................................................................................................569 Sum Menu ..............................................................................................................................571 M1 Menu ..............................................................................................................................572 M2 Menu ..............................................................................................................................574 Conn Menu ..............................................................................................................................577 GES Macro ..............................................................................................................................579 Component Table Macro ..............................................................................................................................582 PERMAS Utility Menu ...........................................................................................................................................583 Convert Groups ..............................................................................................................................584 Creating an NLLOAD Card ..............................................................................................................................585 RADIOSS (Block Format) Utility Menu ...........................................................................................................................................588 Tools Menu ..............................................................................................................................589 RBODY Manager ..........................................................................................................................591 Part Info ..........................................................................................................................594 Clone ..........................................................................................................................595 Part Create..........................................................................................................................596 Part ADMAS Manager ..........................................................................................................................597 Engine File Tool ..........................................................................................................................599 Meshless Welds Macro ..........................................................................................................................614 Material Table Macro ..........................................................................................................................620 Model ..........................................................................................................................622 Check Macro Component Table ..........................................................................................................................623 Other Tools ..............................................................................................................................631 Accelerometer Tool ..........................................................................................................................632 Relative Displacement Tool ..........................................................................................................................633 BCs Manager Tool ..........................................................................................................................635 RADIOSS (Bulk Data Format), OptiStruct Utility Menu ...........................................................................................................................................640 Summary Page ..............................................................................................................................641 FEA Page ..............................................................................................................................643 I-DEAS to RADIOSS ..........................................................................................................................645 Export..........................................................................................................................646 in MDL Part Replacement ..........................................................................................................................647 Material Table ..........................................................................................................................651 Component Table ..........................................................................................................................653 Property Table ..........................................................................................................................655 Load Collector Table ..........................................................................................................................657 Buckling ..........................................................................................................................659
vi

Altair Engineering
RADIOSS (Bulk Data Format) Model Checker ..........................................................................................................................660 Opti Page ..............................................................................................................................663 Voxelmesh ..........................................................................................................................665 Matfrac ..........................................................................................................................667 Reg. Volfrac ..........................................................................................................................668 PBAR, PROD Opti. ..........................................................................................................................669 CBAR, CROD Opti. ..........................................................................................................................670 Design Variables ..........................................................................................................................672 Design Constraints ..........................................................................................................................675 HyperMesh Entities & Solver Interfaces Example Template Code ...........................................................................................................................................686 Example FE-Input Code ...........................................................................................................................................688 User Profiles ...........................................................................................................................................695 Include Files ...........................................................................................................................................697 Support of Includes: Abaqus ...........................................................................................................................................700 Support of Includes: LS-Dyna ...........................................................................................................................................701 Nodes ...........................................................................................................................................702 Collectors and Collected Entities ...........................................................................................................................................708 Assemblies ...........................................................................................................................................712 Components ...........................................................................................................................................718 Points ..............................................................................................................................729 Lines ..............................................................................................................................730 Surfaces ..............................................................................................................................731 Solids ..............................................................................................................................732 Elements ..............................................................................................................................733 Bar2 ..........................................................................................................................816 Bar3 ..........................................................................................................................817 Gap ..........................................................................................................................818 Hex8 ..........................................................................................................................819 Hex20..........................................................................................................................820 Joint ..........................................................................................................................821 Mass ..........................................................................................................................822 Master3 ..........................................................................................................................823 Master4 ..........................................................................................................................824 Penta6 ..........................................................................................................................825 Penta15 ..........................................................................................................................826 Plot ..........................................................................................................................827 Pyramid5 ..........................................................................................................................828 Pyramid13 ..........................................................................................................................829 Quad4..........................................................................................................................830 Quad8..........................................................................................................................832
Altair Engineering

vii
RBE3 ..........................................................................................................................833 Rigid ..........................................................................................................................834 Rigidlink ..........................................................................................................................835 Rod ..........................................................................................................................836 Slave1..........................................................................................................................837 Slave3..........................................................................................................................838 Slave4..........................................................................................................................839 Spring..........................................................................................................................840 Tetra4..........................................................................................................................841 Tetra10 ..........................................................................................................................842 Tria3 ..........................................................................................................................843 Tria6 ..........................................................................................................................844 Weld ..........................................................................................................................845 Connectors ..............................................................................................................................846 Load Collectors ...........................................................................................................................................847 Loads ..............................................................................................................................881 Accelerations ..........................................................................................................................903 Constraints ..........................................................................................................................904 Fluxes..........................................................................................................................905 Forces ..........................................................................................................................906 Moments ..........................................................................................................................907 Pressures ..........................................................................................................................908 Temperatures ..........................................................................................................................909 Velocities ..........................................................................................................................910 Equations ..............................................................................................................................911 System Collectors ...........................................................................................................................................916 Systems ..............................................................................................................................920 Vector Collectors ...........................................................................................................................................931 Vectors ..............................................................................................................................936 Beamsection Collectors ...........................................................................................................................................937 Beamsections ..............................................................................................................................952 Multibodies ...........................................................................................................................................956 Ellipsoids ..............................................................................................................................960 Multibody Planes ..............................................................................................................................961 Multibody Joints ..............................................................................................................................962 Bags ...........................................................................................................................................967 Generic ..............................................................................................................................969 Optimization Problem ..............................................................................................................................970 FBD Forces (All Loads) ..............................................................................................................................971 FBD Forces (Applied Loads Only) ..............................................................................................................................972 FBD Forces (Reaction Loads Only) ..............................................................................................................................973
viii

Altair Engineering
FBD Displacements ..............................................................................................................................974 Resultant Force & Moment ..............................................................................................................................975 FBD Cross-section ..............................................................................................................................976 ADM Part ..............................................................................................................................977 ADM Material ..............................................................................................................................978 Named Entities ...........................................................................................................................................979 Blocks ...........................................................................................................................................980 Curves ...........................................................................................................................................984 Contact Surfaces ...........................................................................................................................................991 Control Volumes ...........................................................................................................................................995 Groups ...........................................................................................................................................1011 Load Steps ...........................................................................................................................................1087 Materials ...........................................................................................................................................1103 Laminates ...........................................................................................................................................1200 Output Blocks ...........................................................................................................................................1204 Plots ...........................................................................................................................................1224 Plies ...........................................................................................................................................1227 Properties ...........................................................................................................................................1230 Sensors ...........................................................................................................................................1272 Sets ...........................................................................................................................................1279 Tags ...........................................................................................................................................1295 Titles ...........................................................................................................................................1297 Morphing Entities ...........................................................................................................................................1299 Domains ...........................................................................................................................................1300 Handles ...........................................................................................................................................1301 Morph Constraints ...........................................................................................................................................1303 Morph Volumes ...........................................................................................................................................1304 Shapes ...........................................................................................................................................1305 Symmetries ...........................................................................................................................................1306 Optimization Entities ...........................................................................................................................................1307 Design Variables ...........................................................................................................................................1308 Design Variable Links ...........................................................................................................................................1312 Design Variable Property Relationships ...........................................................................................................................................1315 Discrete Design Variables ...........................................................................................................................................1319 Optimization Responses ...........................................................................................................................................1321 Optimization Constraints ...........................................................................................................................................1324 Optimization Equations ...........................................................................................................................................1327 Optimization Table Entries ...........................................................................................................................................1329 Objectives ...........................................................................................................................................1331 Objective References ...........................................................................................................................................1334 Optimization Constraint Screenings ...........................................................................................................................................1336
Altair Engineering

ix
Optimization Controls ...........................................................................................................................................1338 Control Cards ...........................................................................................................................................1341 Element Property and Material Assignement Rules ...........................................................................................................................................1392 Supported Cards by Solver ...........................................................................................................................................1395 Unsupported Cards by Solver ...........................................................................................................................................1486 Geometry Terminology ...........................................................................................................................................1501 Nodes ...........................................................................................................................................1504 Free Points ...........................................................................................................................................1505 Lines ...........................................................................................................................................1506 Faces ...........................................................................................................................................1507 Surfaces ...........................................................................................................................................1508 Fixed..............................................................................................................................1509 Points Free Edges ..............................................................................................................................1510 Shared Edges ..............................................................................................................................1511 Suppressed Edges ..............................................................................................................................1512 Non-manifold Edges ..............................................................................................................................1513 Solids ...........................................................................................................................................1514 Bounding Faces ..............................................................................................................................1515 Fin Faces ..............................................................................................................................1516 Full Partition Faces ..............................................................................................................................1517 CAD Cleanup Tolerance ...........................................................................................................................................1518 Geometry Cleanup Tolerance ...........................................................................................................................................1519 Geometry Feature Angle ...........................................................................................................................................1520 CAD Interfacing ...........................................................................................................................................1521 CAD Import ...........................................................................................................................................1522 CAD Reader Support ..............................................................................................................................1523 ACIS..........................................................................................................................1525 Reader Support CATIA Reader Support ..........................................................................................................................1526 DXF Reader Support ..........................................................................................................................1528 IGES..........................................................................................................................1529 Reader Support JT Reader Support ..........................................................................................................................1531 Parasolid Reader Support ..........................................................................................................................1532 PDGS Reader Support ..........................................................................................................................1533 Pro E Reader Support ..........................................................................................................................1534 SolidWorks Reader Support ..........................................................................................................................1535 STEP Reader Support ..........................................................................................................................1536 Tribon Reader Support ..........................................................................................................................1537 UG Reader Support ..........................................................................................................................1540 VDAFS Reader Support ..........................................................................................................................1543 CAD ..............................................................................................................................1544 Import Options

Altair Engineering
ACIS..........................................................................................................................1546 Import Options CATIA Import Options ..........................................................................................................................1550 DXF Import Options ..........................................................................................................................1556 IGES..........................................................................................................................1558 Import Options JT Import Options ..........................................................................................................................1567 Parasolid Import Options ..........................................................................................................................1572 PDGS Import Options ..........................................................................................................................1576 Pro E Import Options ..........................................................................................................................1578 SolidWorks Import Options ..........................................................................................................................1583 STEP Import Options ..........................................................................................................................1587 Tribon Import Options ..........................................................................................................................1592 UG Import Options ..........................................................................................................................1602 VDAFS Import Options ..........................................................................................................................1615 CAD ..........................................................................................................................1619 Import Message Files CAD ..........................................................................................................................1620 Import Difficulties CAD ..........................................................................................................................1621 Metadata Naming CAD Export ...........................................................................................................................................1623 CAD ..............................................................................................................................1624 Writer Support IGES..........................................................................................................................1625 Writer Support CAD ..............................................................................................................................1626 Export Options IGES..........................................................................................................................1627 Export Options Functionality ...........................................................................................................................................1629 Creating Geometry ...........................................................................................................................................1630 Editing Geometry ...........................................................................................................................................1635 Querying Geometry ...........................................................................................................................................1639 Meshing 0-D Elements ...........................................................................................................................................1642 SPH Mesh ...........................................................................................................................................1643 SPH Mesh Generation Input ...........................................................................................................................................1644 SPH Mesh Type and Pitch ...........................................................................................................................................1645 Material Density or Mass of Filled Volume ...........................................................................................................................................1646 Filling Options ...........................................................................................................................................1647 Solver Interfacing ...........................................................................................................................................1648 Visualization of SPH (Mass) Elements ...........................................................................................................................................1649 Line Meshing ...........................................................................................................................................1650 Surface Meshing ...........................................................................................................................................1652 Automatic Mesh Generation ...........................................................................................................................................1653 Element Biasing ..............................................................................................................................1655 Linear Biasing ..........................................................................................................................1656 Exponential Biasing ..........................................................................................................................1657 Bellcurve Biasing ..........................................................................................................................1658
Altair Engineering

xi
Linked or Locked Edges ..............................................................................................................................1659 Smoothing Algorithms ..............................................................................................................................1660 Mesh..............................................................................................................................1661 Generation Algorithms Using..............................................................................................................................1663 the Automeshing Secondary Panel Shrink Wrap Meshing ...........................................................................................................................................1664 Loose Shrink Wrap Mesh ..............................................................................................................................1665 Tight ..............................................................................................................................1670 Shrink Wrap Mesh Generate 2D BL Mesh ...........................................................................................................................................1674 Meshing a 2D Planar Area with Boundary Layers ..............................................................................................................................1676 Volume Meshing ...........................................................................................................................................1682 Solid Meshing Practices ...........................................................................................................................................1683 Partitioning Solids for Mappability ..............................................................................................................................1684 Solid Map Meshing ...........................................................................................................................................1687 Tetra Meshing ...........................................................................................................................................1689 CFD Meshing in HyperMesh ..............................................................................................................................1692 Boundary Layers ..............................................................................................................................1693 Tetramesh Process Panel ...........................................................................................................................................1695 Geometry Import Panel - Tetramesh Process Manager ..............................................................................................................................1697 Geometry Cleanup Panel - Tetramesh Process Manager ..............................................................................................................................1699 Cleanup & Organize Holes Panel - Tetramesh Process Manager ..............................................................................................................................1700 Mesh..............................................................................................................................1702 Holes Panel - Tetramesh Process Manager User Defined Features - Tetramesh Process Manager ..............................................................................................................................1704 Fillets Organize & Cleanup - Tetramesh Process Manager ..............................................................................................................................1706 Mesh..............................................................................................................................1708 User Defined Features - Tetramesh Process Manager Global Organize & Cleanup - Tetramesh Process Manager ..............................................................................................................................1709 Global Mesh - Tetramesh Process Manager ..............................................................................................................................1710 Element Cleanup - Tetramesh Process Manager ..............................................................................................................................1711 Volume Shrink Wrap ...........................................................................................................................................1714 Acoustic Cavity Meshing ...........................................................................................................................................1715 Acoustic Cavity Tab ..............................................................................................................................1718 Voxel meshing ...........................................................................................................................................1721 Checking & Editing Mesh ...........................................................................................................................................1723 Element Quality ...........................................................................................................................................1724 How Element Quality is Calculated ..............................................................................................................................1725 Element Quality Calculation: HyperMesh ..........................................................................................................................1726 Element Quality Calculation: HyperMesh-Alt ..........................................................................................................................1731 Element Quality Calculation: OptiStruct ..........................................................................................................................1734 Element Quality Calculation: Radioss (BulkData) ..........................................................................................................................1736 Element Quality Calculation: Abaqus ..........................................................................................................................1738 Element Quality Calculation: ANSYS ..........................................................................................................................1740 Element Quality Calculation: I-DEAS ..........................................................................................................................1744
xii

Altair Engineering
Element Quality Calculation: Medina ..........................................................................................................................1747 Element Quality Calculation: Moldflow ..........................................................................................................................1749 Element Quality Calculation: Nastran ..........................................................................................................................1750 Element Quality Calculation: Patran ..........................................................................................................................1752 Hole Detection tool ...........................................................................................................................................1758 Penetration check ...........................................................................................................................................1764 Mesh Coarsening ...........................................................................................................................................1766 BatchMesher ...........................................................................................................................................1769 About BatchMesher ...........................................................................................................................................1770 To start BatchMesh on a PC: ..............................................................................................................................1772 To start BatchMesh in UNIX: ..............................................................................................................................1773 BatchMesher Setup ...........................................................................................................................................1774 Batch Mesh Tab ...........................................................................................................................................1776 Configurations Tab ...........................................................................................................................................1779 Run Status Tab ...........................................................................................................................................1781 User Procedures Tab ...........................................................................................................................................1784 BatchMesher Customization ...........................................................................................................................................1786 User-registered Procedures ...........................................................................................................................................1788 BatchMesher Parameter Editor ...........................................................................................................................................1790 Editing Parameter Files ..............................................................................................................................1791 Basic Options: Target Element Size, Import Model Tolerance, Extract Midsurface ..........................................................................................................................1794 Geometry Cleanup Options ..........................................................................................................................1795 Create Mesh Options ..........................................................................................................................1797 Special Component Selection Options ..........................................................................................................................1799 Editing Criteria Files ..............................................................................................................................1800 hw_batchmesh ...........................................................................................................................................1802 BatchMesher Error Codes ...........................................................................................................................................1805 Grid Computing with BatchMesher ...........................................................................................................................................1807 Connectors Connector Entity ...........................................................................................................................................1811 Connector Definition ...........................................................................................................................................1812 Example of Connecting Assemblies ...........................................................................................................................................1814 Connector Terminology ...........................................................................................................................................1815 Connector Location ...........................................................................................................................................1816 Connector Realization ...........................................................................................................................................1819 How HyperMesh determines realization ..............................................................................................................................1820 HiLock Realization ..............................................................................................................................1825 Connector Rules ...........................................................................................................................................1831 Connector State ...........................................................................................................................................1832 Link Entity State ...........................................................................................................................................1833 Link Entity ...........................................................................................................................................1834
Altair Engineering

xiii
Number of Layers ...........................................................................................................................................1835 Re-connect Rules ...........................................................................................................................................1836 Connector Review ...........................................................................................................................................1837 Connectors User Control Mode ...........................................................................................................................................1838 Master Connectors File ...........................................................................................................................................1839 Multiple Weld File Format ...........................................................................................................................................1841 Spotweld Interface ...........................................................................................................................................1842 Import Templates ...........................................................................................................................................0 FE Configuration File ...........................................................................................................................................1844 FE Configuration Examples ...........................................................................................................................................1849 Abaqus Connector Types ...........................................................................................................................................1851 LS-DYNA Connector Types ...........................................................................................................................................1860 Nastran Connector Types ...........................................................................................................................................1871 OptiStruct Connector Types ...........................................................................................................................................1896 PAM-CRASH Connector Types ...........................................................................................................................................1920 RADIOSS Connector Types ...........................................................................................................................................1922 Model Setup Properties ...........................................................................................................................................1929 HyperLaminate ...........................................................................................................................................1930 Environment ..............................................................................................................................1931 Menus ..............................................................................................................................1933 Toolbar ..............................................................................................................................1936 Laminate Browser ..............................................................................................................................1937 Create Entities ..........................................................................................................................1939 Review and Update Entities ..........................................................................................................................1940 Rename Entities ..........................................................................................................................1941 Duplicate Entities ..........................................................................................................................1942 Delete Entities ..........................................................................................................................1943 HyperLaminate Solver ..............................................................................................................................1944 To Select HLS loadcases for the current laminate ..........................................................................................................................1946 Define/Edit Pane ..............................................................................................................................1947 To Define a new HyperLaminate Solver loadcase ..........................................................................................................................1956 To Review or modify an existing HL Solver loadcase ..........................................................................................................................1957 Review/Results Pane ..............................................................................................................................1958 Define a New Material: ..............................................................................................................................1960 Review or Modify an Existing Material ..............................................................................................................................1962 Define a New Laminate ..............................................................................................................................1963 Review and Modify an Existing Laminate ..............................................................................................................................1965 Define a New Design Variable ..............................................................................................................................1966 Review and Modify an Existing Design Variable ..............................................................................................................................1967 HyperBeam ...........................................................................................................................................1968
xiv

Altair Engineering
HyperBeam View ..............................................................................................................................1969 Section Browser and Parameter Definition ..........................................................................................................................1970 HyperBeam View Toolbar ..........................................................................................................................1974 Graphics Window ..........................................................................................................................1975 HyperBeam Results Pane ..........................................................................................................................1980 HyperBeam Sections ..............................................................................................................................1982 Example: Creating and Assigning a Standard Section ..........................................................................................................................1983 Example: Creating and Assigning a Shell Section ..........................................................................................................................1987 Cross..............................................................................................................................1992 Sectional Properties Calculated by HyperBeam Working with Beamsections in HyperMesh ..............................................................................................................................1996 Importing and Exporting HyperBeam Comments ..............................................................................................................................1998 Example: Importing and Automatic Beamsection Creation ..........................................................................................................................2000 Importing Geometry ...........................................................................................................................................2001 Import Error Messages ...........................................................................................................................................2003 Creating Collectors ...........................................................................................................................................2004 Changing the Current Component Collector ...........................................................................................................................................2005 Changing the Current Load Collector ...........................................................................................................................................2006 Creating Geometry Data ...........................................................................................................................................2007 Temporary Nodes ...........................................................................................................................................2011 Picking Surfaces ...........................................................................................................................................2012 Editing Surfaces ...........................................................................................................................................2013 Associativity ...........................................................................................................................................2015 Geometry Cleanup ...........................................................................................................................................2016 Applying Loads ...........................................................................................................................................2018 Creating Systems ...........................................................................................................................................2020 Control Cards ...........................................................................................................................................2021 Using the Card Previewer ...........................................................................................................................................2022 Boundary Conditions ...........................................................................................................................................2023 Loads on Geometry ...........................................................................................................................................2024 Terminology and Definitions ..............................................................................................................................2025 Application of Loads to Geometry ..............................................................................................................................2026 Exporting Loads ..............................................................................................................................2027 Visualization of Loads on Geometry and on Mesh ..............................................................................................................................2028 Creating Load Collectors ..............................................................................................................................2029 Transformation Manager ...........................................................................................................................................2030 Morphing Approaches to Morphing ...........................................................................................................................................2036 The Domains and Handles Concept ...........................................................................................................................................2038 Global Domains and Handles ..............................................................................................................................2039 Local..............................................................................................................................2044 Domains and Handles Partitioning ..............................................................................................................................2051 Dependent Handles ..............................................................................................................................2053 Altair Engineering Altair HyperMesh User's Guide
xv
Working with Shapes ..............................................................................................................................2057 Setting Up Optimization ..............................................................................................................................2059 The Morph Volume Concept ...........................................................................................................................................2060 The Freehand Concept ...........................................................................................................................................2061 Space Frame Model Strategies ...........................................................................................................................................2062 Creating Handles and Domains - Space Frame Model ...........................................................................................................................................2063 Matching a Mesh, Line, or Surface Data ...........................................................................................................................................2066 Making Parametric Changes ...........................................................................................................................................2070 Controlling Global Morphing with Handle Placement ...........................................................................................................................................2073 Mirror Images - Using 1-Plane Symmetry ...........................................................................................................................................2077 Reducing 3D to 2D - Using Linear Symmetry ...........................................................................................................................................2080 Reducing 3D to 1D - Using Planar Symmetry ...........................................................................................................................................2083 Shell Model Strategies ...........................................................................................................................................2086 Creating Handles and Domains - shell model ...........................................................................................................................................2087 Morphing on Local Domains ...........................................................................................................................................2094 Morphing Global Handles ...........................................................................................................................................2110 Using Constraints ...........................................................................................................................................2111 Using Biasing ...........................................................................................................................................2113 Solid Model Strategies ...........................................................................................................................................2115 Creating Handles and Domains - solid model ...........................................................................................................................................2116 Viewing Solid Models ...........................................................................................................................................2123 Optimization Model Browser Optimization View ...........................................................................................................................................2126 The Menu Bar ...........................................................................................................................................2127 The Panels ...........................................................................................................................................2128 Conversion between Solver Formats Abaqus Conversion Tools ...........................................................................................................................................2131 Abaqus to Nastran Conversion ...........................................................................................................................................2132 Abaqus to RADIOSS (Block Format) Conversion ...........................................................................................................................................2137 Abaqus to RADIOSS (Bulk Data Format), OptiStruct Conversion ...........................................................................................................................................2141 ANSYS Conversion Tools ...........................................................................................................................................2146 ANSYS to Abaqus Conversion ...........................................................................................................................................2147 ANSYS to Nastran Conversion ...........................................................................................................................................2150 ANSYS to RADIOSS (Bulk Data Format) Conversion ...........................................................................................................................................2152 LS-DYNA Conversion Tools ...........................................................................................................................................2154 LS-DYNA to Nastran Conversion ...........................................................................................................................................2155 LS-DYNA to RADIOSS (Block Format) Conversion ...........................................................................................................................................2157 LS-DYNA to RADIOSS (Bulk Data Format) Conversion ...........................................................................................................................................2163 Nastran Conversion Tools ...........................................................................................................................................2165 Nastran to Abaqus Conversion ...........................................................................................................................................2166 Nastran to ANSYS Conversion ...........................................................................................................................................2173
xvi

Altair Engineering
Nastran to LS-DYNA Conversion ...........................................................................................................................................2176 Nastran to RADIOSS (Block Format) Conversion ...........................................................................................................................................2179 PAM-CRASH 2G to RADIOSS (Block Format) Conversion ...........................................................................................................................................2182 RADIOSS Conversion Tools ...........................................................................................................................................2189 RADIOSS (Bulk Data Format), OptiStruct to Abaqus Conversion ...........................................................................................................................................2190 RADIOSS (Bulk Data Format) to ANSYS Conversion ...........................................................................................................................................2197 RADIOSS (Block Format) to PAM-CRASH 2G Conversion ...........................................................................................................................................2200 XY Plotting XY Plots Module ...........................................................................................................................................2209 Creating an XY Plot ...........................................................................................................................................2211 Modifying an XY Plot ...........................................................................................................................................2212 Working with Multiple XY Plots ...........................................................................................................................................2213 Modifying Multiple XY Plots ...........................................................................................................................................2214 Creating Curves on XY Plots ...........................................................................................................................................2215 Reading Curves from an ASCII File ...........................................................................................................................................2216 Creating Analysis Based Curves ...........................................................................................................................................2217 Creating Curves Using Simple Math Operators ...........................................................................................................................................2218 Creating Curves from Files or Math Expressions ...........................................................................................................................................2219 Modifying Curve Attributes ...........................................................................................................................................2220 Displaying Selected Curves on Plots ...........................................................................................................................................2221 Curve Editor ...........................................................................................................................................2222 To create a new curve: ...........................................................................................................................................2224 To display curves in the graph area: ...........................................................................................................................................2225 To change the graph's attributes: ...........................................................................................................................................2226 To change a curve's attributes: ...........................................................................................................................................2227 To delete a curve: ...........................................................................................................................................2228 To rename a curve: ...........................................................................................................................................2229 Post-processing Analysis HyperMesh Results Database ...........................................................................................................................................2231 Results Translation ...........................................................................................................................................2232 hmabaqus Results Translation ...........................................................................................................................................2233 Translating Complex Results ..............................................................................................................................2238 Translating Element Results for Different Positions ..............................................................................................................................2239 Supported Result Types ..............................................................................................................................2240 Post-processing Actran Results ...........................................................................................................................................2244 hmansys Results Translation ...........................................................................................................................................2246 MADYMO Results Translation ...........................................................................................................................................2253 hmnast Results Translation ...........................................................................................................................................2255 hmnast Utility ..............................................................................................................................2256 Splitting Punch Files ..........................................................................................................................2260 To translate two punch files and read them in HyperMesh: ..........................................................................................................................2271
Altair Engineering

xvii
hmnasto2 Utility ..............................................................................................................................2272 To create a model file from an op2 file and load the model file ..........................................................................................................................2277 hmnastf06 Utility ..............................................................................................................................2278 hmnastop Utility ..............................................................................................................................2279 Translating Complex Results ..............................................................................................................................2280 To post-process NASTRAN results in HyperMesh: ..............................................................................................................................2281 hmpam Results Translation ...........................................................................................................................................2283 PAM-CRASH Results Translation ..............................................................................................................................2284 Viewing the Results ..........................................................................................................................2290 Reading XY-Plotting Data from the THP (DSY) File ..........................................................................................................................2291 PAM-CRASH 2G Results Translation ..............................................................................................................................2295 Viewing the Results ..........................................................................................................................2301 Reading XY-Plotting Data from the THP (DSY) File ..........................................................................................................................2302 PERMAS Results Translation ...........................................................................................................................................2307 RADIOSS (Fixed Format) Results Translation ...........................................................................................................................................2308 Analysis Results Files ..............................................................................................................................2310 RADIOSS (Bulk Data Format) Results Translation ...........................................................................................................................................2311 Specifying the Results File ...........................................................................................................................................2312 Creating Deformed Geometry Plots ...........................................................................................................................................2313 Creating Animations ...........................................................................................................................................2314 Creating Vector Plots ...........................................................................................................................................2315 Creating Contour Plots ...........................................................................................................................................2316 Creating Assigned Plots ...........................................................................................................................................2317 Adding Plot Identification ...........................................................................................................................................2318 Inspecting the Results ...........................................................................................................................................2319 Free Body Diagrams ...........................................................................................................................................2320 FBD Displacements ...........................................................................................................................................2322 To extract displacement data for a user-defined node set ..............................................................................................................................2323 FBD Forces ...........................................................................................................................................2326 To select a results file ..............................................................................................................................2327 To select a sub-case ..............................................................................................................................2328 To select entities ..............................................................................................................................2329 To specify output options ..............................................................................................................................2330 FBD Cross-section manager ...........................................................................................................................................2332 To define a cross-section manually ..............................................................................................................................2333 To define a cross-section automatically ..............................................................................................................................2335 FBD Resultant Force and Moment ...........................................................................................................................................2336 To select a results file ..............................................................................................................................2337 To select a sub-case ..............................................................................................................................2338 To select a cross-section ..............................................................................................................................2339 To specify output options ..............................................................................................................................2340 FBD Results Manager ...........................................................................................................................................2342 xviii Altair HyperMesh User's Guide
Altair Engineering
To review and manage FBD load collectors ..............................................................................................................................2343 FBD Export Manager ...........................................................................................................................................2345 To export FBD, Displacement, or Resultant Force & Moment collectors ..............................................................................................................................2346 FBD Grid Point Force Balance ...........................................................................................................................................2348 FBD Solver Interfacing ...........................................................................................................................................2355 Abaqus - Free Body Diagrams ..............................................................................................................................2356 Ansys - Free Body Diagrams ..............................................................................................................................2357 Nastran - Free Body Diagrams ..............................................................................................................................2358 Radioss (Bulk Data) and OptiStruct - Free Body Diagrams ..............................................................................................................................2359 H3D Writer ...........................................................................................................................................2360 Creating an H3D file from HyperMesh ...........................................................................................................................................2361 Create an H3D file from HyperMesh: ..............................................................................................................................2362 Embedding a HyperView Player Object in HTML Documentation ...........................................................................................................................................2363 Sharing H3D Files ...........................................................................................................................................2365 H3D FAQ ...........................................................................................................................................2367 HyperMesh Interfacing with External Products Abaqus Solver Interface ...........................................................................................................................................2369 Actran Solver Interface ...........................................................................................................................................2371 ANSYS Solver Interface ...........................................................................................................................................2372 RBE3 Elements ...........................................................................................................................................2373 Tips and Techniques ...........................................................................................................................................2376 Pressure Load on Beam Elements ...........................................................................................................................................2378 FE Input Enhancement ...........................................................................................................................................2380 LS-DYNA Solver Interface ...........................................................................................................................................2381 Recommended Process ...........................................................................................................................................2383 Mass Calculation ...........................................................................................................................................2384 Exporting Decks ...........................................................................................................................................2385 MADYMO Solver Interface ...........................................................................................................................................2386 MARC Solver Interface ...........................................................................................................................................2388 Nastran Solver Interface ...........................................................................................................................................2389 PAM-CRASH 2G Solver Interface ...........................................................................................................................................2390 PERMAS Solver Interface ...........................................................................................................................................2393 RADIOSS (Bulk Data), OptiStruct Interface ...........................................................................................................................................2395 RADIOSS (Block Format) Interface Overview ...........................................................................................................................................2397 Supported Cards ...........................................................................................................................................2399 Supported ENGINE Cards in RADIOSS (Block Format) ..............................................................................................................................2400 Unsupported ENGINE Cards in RADIOSS (Block Format) 5.1, 9.0 and 10.0 ..............................................................................................................................2403 Samcef Interface ...........................................................................................................................................2405 Contact .MCT ...........................................................................................................................................2406 Contact .STI ...........................................................................................................................................2408
Altair Engineering

xix
Graphical User Interface

This section describes parts of the HyperWorks Desktop user interface which only display when HyperMesh is the active application.
HyperMesh Color Options dialog HyperMesh Menu Bar HyperMesh Toolbars HyperMesh Tabs HyperMesh Calculator

Altair Engineering
Toolbar/Panel Changes in HyperMesh 11.0

The HyperMesh user interface has undergone significant changes since version 10, including updated toolbar icons and the transfer of more functionality to the toolbars and drop-down menus. The following topics outline the changes from version 10 to version 11. In many cases, multiple toolbar buttons can appear in the same location. These buttons have a down-arrow ( ) next to them, and clicking this arrow reveals a menu of available buttons for that toolbar space. Such menus are common in the Standard Toolbar, but also appear in some of the buttons on other toolbars as well.
The "New " button in the Standard Toolbar can have different functions depending on w hat you select from the menu. Some options are not available in HyperMesh.
Separate topics detail the changes for specific areas of functionality. Note that toolbars which have not changed fundamentally are not described; only those with substantially different organization or icon imagery are detailed here. Standard Toolbar Changes Standard Views Toolbar Changes Visualization Toolbar Changes Geometry Panel Changes
Altair Engineering

Standard Toolbar Changes

Note: This chart illustrates the differences between the formerly stand-alone HyperMesh 10.0 and the new, integrated HyperMesh Desktop 11.0. Some small differences, particularly in the Pull Down Menu locations, may exist between HyperMesh 11.0 stand-alone and HyperMesh Desktop versions.
Where an old toolbar button has been replaced by one with multiple options (as described in Panel/Dialog Reorganization in HyperMesh 11.0), the corresponding new options are listed separately and indented under the old button's name.
Function
Old 10.0
New 11.0
(varies)
New 11.0 Location
Alternate Location (Pull down menus)

File > New File > New > Model File > New > Session
New File Model Session
Standard Toolbar Standard Toolbar Standard Toolbar
Open File Model Session Save File Model Session Import Session Model Solver Deck
(varies)
File > Open File > Open > Model File > Open > Session File > Save File > Save > Model File > Save > Session File > Import File > Import > Session File > Import > Model File > Import > Solver Deck
(varies)
(varies)
Standard Toolbar Standard Toolbar Standard Toolbar Standard Toolbar

Altair Engineering
Geometry Connectors Export Model Solver Deck Geometry Connectors Curves User Profile Load File Load Results Load Preference Load Solver Template Run Tcl/TK Script Command File ---------------(varies) (varies)
Standard Toolbar Standard Toolbar Standard Toolbar Standard Toolbar Standard Toolbar Standard Toolbar Standard Toolbar Standard Toolbar Standard Toolbar Standard Toolbar Standard Toolbar Standard Toolbar Standard Toolbar
File > Import > Geometry File > Import > Connectors File > Export File > Export > Model File > Export > Solver Deck File > Export > Geometry File > Export > Connectors File > Export > Curves File > Load > User Profile File > Load File > Load > Results File > Load > Preference File > Load > Solver Template
Pull-Down Only Pull-Down Only
File > Run > Tcl/TK Script File > Run > Command File
Altair Engineering

Standard Views Toolbar Changes
Function
Old 10.0
New 11.0
New 11.0 Location

None None None
Previous View Fit Model Refresh Graphics Area (Plot Refresh) XY Top Plane View XY Bottom Plane View XZ Left Plane View XZ Right Plane View YZ Rear Plane View YZ Front Plane View Isometric View Reverse View User View/True View
Standard Views Toolbar Standard Views Toolbar Standard Views Toolbar
Standard Views Toolbar Standard Views Toolbar
None None
Standard Views Toolbar Standard Views Toolbar Standard Views Toolbar Standard Views Toolbar Standard Views Toolbar Standard Views Toolbar Standard Views Toolbar
None None None None None None Model Browser Context Menu (Create > View)

Altair Engineering
Visualization Toolbar Changes

While most of the functionality in the visualization toolbar remains the same, some of the icons used are quite different from previous versions and the organization of buttons isn't quite the same. In addition, the menus for geometry and mesh styles work differently; rather than right-clicking the button to select from its menu, you must click the separate down-arrow button beside it (as described in Panel/Dialog Reorganization in HyperMesh 11.0).
Function
Old 10.0
New 11.0
New 11.0 Location
Alternate Location
Geometry Color Wireframe Geometry
Visualization Toolbar None Visualization Toolbar None
Wireframe Geometry and Surface Lines Shaded Geometry and Surface Edges Shaded Geometry
Visualization Toolbar None
Element Color Mode Wireframe Elements (skin only) Wireframe Elements
Shaded Elements and Mesh Lines Shaded Elements and Feature Lines Shaded Elements
Transparency Geom/Mesh Styles n/a
Visualization Toolbar None None: this legacy feature from pre-10.0 Use the Model Browser's optional FEStyle and GeomStyle columns
Altair Engineering

has been removed.
to change styles for each component.
Shrink Elements Visualization Options

Altair Engineering
Geometry Panel Changes

The Geometry panels have been changed for version 11 to use toolbars instead of radio buttons for selection of subpanels. In addition, some functions have been moved--for example, the functions of the Circles panel were moved into the Lines panel and Primitives features were moved into Surfaces and Solids. The table below summarizes these changes as they relate to the older 10.0 panel structure. Note also that many new geometry subpanels and functions have been added for version 11, but these tables focus on the new locations of functions that are already familiar to users of version 10 and earlier--they serve as a roadmap for users to find the tools that they are already familiar with. For full details on geometry panels, including new functions, see the dedicated panel help for each geometry panel listed in the "See Also" section at the end of this topic. Unless otherwise stated, the New 11.0 Name is a subpanel of the same panel as the old 10.0 location.
10.0 Nodes Panel
Subpanels
New Icon
New 11.0 Name

Geometry > Create > Nodes > XYZ Geometry > Create > Free Points > XYZ Geometry > Create > Nodes > On Geometry
Type In
Nodes Panel > XYZ Points Panel > XYZ On Geometry (points, lines, surfs) Extract On line
Pick Geom
On Line
Geometry > Create > Nodes > Extract on Line Geometry > Create > Nodes > Interpolate on Line Geometry > Create > Nodes > On Geometry
Interpolate on Line
At point
On Geometry
Between
Interpolate Nodes
Geometry > Create > Nodes > Interpolate
Interpolate On Line
Geometry > Create > Nodes > Interpolate on Line Geometry > Create > Nodes > Interpolate on Surface Geometry > Create > Nodes > On Geometry
Interpolate On Surface
On Plane
On Geometry (plane)
Altair Engineering

10.0 Lines Panel
Subpanels
New Icon
New 11.0 Name

Geometry > Create > Lines > Linear Nodes
From Nodes
Linear Nodes
Standard Nodes
Geometry > Create > Lines > Standard Nodes Geometry > Create > Lines > Smooth Nodes
Smooth Nodes
Controlled Nodes
Geometry > Create > Lines > Controlled Nodes Geometry > Create > Lines > Offset
Offset
Offset
Midline
Geometry > Create > Lines > Midline
From Surf Edges From Features
Extract edge
Geometry > Create > Lines > Extract Edge
Features
Geometry > Create > Lines > Features
At Intersection
Intersect
Geometry > Create > Lines > Intersect
At Tangent
Tangent
Geometry > Create > Lines > Tangent
Fillets
Fillet
Geometry > Create > Lines > Fillet
10.0 Circles Panel

Note: The Circles panel no longer exists. Its features have been moved entirely into the Lines, Nodes, and new Free Points panels.

Altair Engineering
Subpanels
New Icon
New 11.0 Name

Geometry > Create > Lines > Arc Center and Radius Geometry > Create > Lines > Circle Center and Radius Geometry > Create > Lines > Arc Nodes and Vector Geometry > Create > Lines > Circle Nodes and Vector Geometry > Create > Lines > Arc Three Nodes Geometry > Create > Lines > Circle Three Nodes Geometry > Create > Nodes > Arc Center
Center & Radius
Lines Panel > Arc Center and Radius Lines Panel > Circle Center and Radius
Points & Vector
Lines Panel > Arc Nodes and Vector Lines Panel > Circle Nodes and Vector
Three Points
Lines Panel > Arc Three Nodes Lines Panel > Circle Three Nodes
Find Center
Nodes Panel > Arc Center Points Panel > Arc Center
Geometry > Create > Free Points > Arc Center
10.0 Surfaces Panel
Subpanels
New Icon
New 11.0 Name

Geometry > Create > Surfaces > Ruled
Ruled
Ruled
Spline/Filler
Spline/Filler
Geometry > Create > Surfaces > Spline/Filler
Skin
Skin
Geometry > Create > Surfaces > Skin
Altair Engineering

10
Drag/Spin
Drag along Vector
Geometry > Create > Surfaces > Drag Along Vector Geometry > Create > Surfaces > Drag Along Line Geometry > Create > Surfaces > Drag Along Normal Geometry > Create > Surfaces > Spin
Drag Along Line
Drag Along Normal
Spin
From FE
From FE
Geometry > Create > Surfaces > From FE
Fillets
Fillet
Geometry > Create > Surfaces > Fillet
10.0 Solids Panel
Subpanels
New Icon
New 11.0 Name

Geometry > Create > Solids > Bounding Surfaces Geometry > Create > Solids > Drag Along Vector Geometry > Create > Solids > Drag Along Normal Geometry > Create > Solids > Drag Along Line Geometry > Create > Solids > Spin
Bounding Surfs Drag Along Vector Drag Along Normal Drag Along Line Spin
Bounding Surfaces
Drag Along Vector
Drag Along Normal
Drag Along Line
Spin
10.0 Primitives Panel

Note: The Primitives panel no longer exists; its functions have been entirely migrated to the Surfaces and Solids panels.
11

Altair Engineering
Subpanels
New Icon
New 11.0 Name

Geometry > Create > Surfaces > Square
Square/Block
Surfaces > Square
Solids > Block
Geometry > Create > Solids > Block
Cylinder/Cone
Surfaces > Cylinder Full Surfaces > Cylinder Partial Surfaces > Cone Full
Geometry > Create > Surfaces > Cylinder Full Geometry > Create > Surfaces > Cylinder Partial Geometry > Create > Surfaces > Cone Full
Surfaces > Cone Partial Solids > Cylinder Full
Geometry > Create > Surfaces > Cone Partial
Geometry > Create > Solids > Cylinder Full
Solids > Cylinder Partial Solids > Cone Full
Geometry > Create > Solids > Cylinder Partial Geometry > Create > Solids > Cone Full
Solids > Cone Partial
Geometry > Create > Solids > Cone Partial
Sphere
Surfaces > Sphere Center and Radius Surfaces > Sphere Four Nodes Surfaces > Sphere Partial
Geometry > Create > Surfaces > Sphere Center and Radius Geometry > Create > Surfaces > Sphere Four Nodes Geometry > Create > Surfaces > Sphere Partial
Solids > Sphere Center Geometry > Create > Solids > Sphere Center and Radius and Raidus
Altair Engineering

12
Solids > Sphere Four Nodes Torus Surfaces > Torus Center and Radius
Geometry > Create > Solids > Sphere Four Nodes Geometry > Create > Surfaces > Torus Center and Radius
Surfaces > Torus Three Geometry > Create > Surfaces > Torus Three Nodes Nodes Surfaces > Torus Partial Solids > Torus Center and Radius Solids > Torus three Nodes Solids > Torus Partial Geometry > Create > Surfaces > Torus Partial Geometry > Create > Solids > Torus Center and Radius Geometry > Create > Solids > Torus Three Nodes Geometry > Create > Solids > Torus Partial
13

Altair Engineering
HyperMesh Color Options dialog

Location: Preferences menu > colors This dialog allows you to specify the colors you wish to use for various elements of the Graphical User Interface (GUI) as well as for different types of geometry and mesh entities. These categories are broken down into separate tabs.
General Tab
The General tab controls the colors of the background in the graphics area, the direction of the gradient, and the colors used by the global axes.
You can select any colors you wish for background 1 and background 2. These control the background gradient:
Altair Engineering

14
You can also use the series of gradient boxes to change the direction or style of the gradient. The boxes themselves illustrate the gradient pattern that they apply, but not the current colors. Finally, you can specify the colors of the X, Y, and Z global axis vectors, and the color of their letter labels (X/ Y/Z), that display in the bottom corner of the graphics area. Click Reset to return to the default settings. Apply immediately applies your changes, but does not close the window. Close closes the window without applying the current settings.
Geometry tab
This tab allows you to set the colors used to display a wide range of geometric entities.
15

Altair Engineering
Different types of geometric features are broken down first by dimensionality (2D surfaces, 3D solids) and each has no influence on geometry of the other type. However, a third category, By mappable display mode (solids), applies to qualities of solids rather than parts of them. These colors apply specifically to how many possible directions solids can be mapped in, and are specific to the mappable geometry display mode. They will not show in any other display mode, even if the model contains solid entities. Surface data free edges shared edges suppressed edges Edges of surfaces that do not connect to any other surfaces. Edges of surfaces that connect to one other surface. Shared edges that have been manually suppressed so that the automesher will treat the shared surfaces as if they were one surface, allowing elements to
Altair Engineering

16
cross the edge as if it were not there at all. t-junctions Edges shared by 3 or more surfaces.
3d solids fin faces bounding faces full partition faces 2d faces (topo) ignored (topo) edges (comp) Fin faces are surfaces that split a 3D solid entity, but only partway through-they do not actually extend through the entire entity. The outer faces of solid entity. The faces of adjoined solids When using the by 2D topo visualization mode, this is the color of 2D faces that aren't part of a solid. The color of 2D faces when using the by 2D topo visualization mode. Mesh edges when coloring mesh with the by comp visualization mode.
by mappable display control (solids) 1 dir. map 3 dir. map ignored map not mappable Visualization for solids that can be mapped (for 3D meshing) in one direction. Visualization for solids that can be mapped (for 3D meshing) in three directions. Default visualization for solids that require partitioning to become mappable. Visualization for solids that have been edited, but still require further partitioning to create mappable solids
Mesh tab
This tab allows you to set the colors used to display a wide range of geometric entities.
17

Altair Engineering
Mesh Lines refers to the visual (non-geometric) lines that define the edges of each element. Elems, no prop/mat means elements that do not currently have any properties or materials assigned to them, either directly or inherited from the collectors that they belong to. Elems, unresolved prop/mat means elements that do have a property or material assigned, but the referenced prop/mat cannot be found in the current model. For example, they might reference "Mat9" but no material with that name exists in the current model. One possible source of such elements is from include files.
Altair Engineering

18
HyperMesh Menu Bar

The menu bar, located just beneath the title bar, enable access to many types of HyperMesh functionality. Most menu options access HyperMesh panels, but some options perform other tasks such as configuring the layout of the HyperMesh environment.
Each menu contains many different options, and clicking on the menu name (such as Geometry) "pulls down" a list of the options available in that menu:
Notice that there are three lists of options displayed in this screen shot; this is because some menu items have sub-menus of additional options. This approach sub-groups similar features together, rather than presenting every option in a single list (which could result in very long lists). Menu items can work in several different ways: Sub-Menu heading These items are marked with a triangular arrow. Selecting a submenu heading opens a sub-menu of options related to the sub-
19

Altair Engineering
menu heading. This method allows similar commands to be grouped logically, and helps prevent any single menu list from becoming excessively long. Toggle When clicked, these items are marked with a checkbox and activate or deactivate a feature. One example is the Solver Browser item found in the View menu; clicking it alternates between showing and hiding the Solver Browser in one of the tab area sidebars. Most menu items simply execute a command when selected, such as accessing a specific HyperMesh panel.
Command
There are multiple ways to select a pull-down menu or a menu item within it: Mouse Keyboard (menu) Click the menu or menu item with the mouse. First, press the alt key to activate the menu area. Then: Use the keyboard key indicated by the menu or item; these keys are underlined (as the "F" in the File menu). or Use the left and right arrow keys to move among the menu headings, and the up and down arrow keys to open a menu and navigate among its options. Keyboard (menu item) Menu items can be selected with the keyboard in two ways: Use the keyboard key indicated by the menu item; these keys are underlined (as the "O" in the Open menu item). or Use the arrow keys to move among list of options, and press enter to select a highlighted option. Each of the pull-down menus in HyperMesh groups certain types of functions: File Contains functions to load, save, import, and export models and other files. Note: To work with only one model at a time, use Open. To add extra models to your workspace, use Import.
Edit View
Tools for masking, deleting, or finding entities. Change the angle of view on the model, lighting, or visibility and location of tab area items, among other options. Tools for creating and renaming collectors, assemblies, etc. Tools for geometry editing and cleanup.
Collectors Geometry
Altair Engineering

20
Mesh Connectors Materials Properties BCs Setup Tools Morphing Post XY Plots Preferences
Meshing tools, such as automesh, tetramesh, solid map, element edit, etc. Create, edit, realize/unrealize, and manipulate various types of connectors. Create, edit, and assign Material cards to components. Create, edit, and assign Property cards to components. Boundary Conditions such as forces, pressures, moments, or constraints. Model properties such as materials, connectors, and contact surfaces. Morph, Rotate, Translate, Reflect, or Scale entities, among other options. Create, edit, and manipulate mesh-morphing entities with HyperMorph. View results of solved simulations (contour or vector plots, for example). Create plots (graphs) of simulation qualities and/or results. HyperMesh preferences such as User Profiles, global options, and keyboard configuration. Quickly access other HyperWorks programs, such as OptiStruct. Access the on-line Help system.
Applications Help
21

Altair Engineering
HyperMesh Toolbars
Toolbars contain groups of icon buttons used to perform the most common tasks. Each toolbar can be docked to any of the toolbar locations. Toolbars can also be undocked or free-floating anyway in the HyperMesh application window. Many toolbars are common to both HyperMesh and other HyperWorks Desktop applications, so they are described in the HyperWorks Desktop user's guide. The toolbars described here are specific to HyperMesh.
Toolbars Included in HyperMesh:

Collectors Checks Display Visualization
Altair Engineering

22
Collectors Toolbar
The Collector toolbar controls basic operations of creating, editing, deleting, card editing, organizing, and renumbering HyperMesh collectors. The Collectors toolbar can be turned on and off from the View > Toolbars menu.
The detailed behavior of each tool button is described in the table below. Button Left-click LEFT Behavior Right-click RIGHT Behavior Same
Assemblies
Left-click to open the Assemblies panel. Left-click to open the Components panel. Left-click to open the Materials panel. Left-click to open the Properties panel. Left-click to open the Load Collectors panel Left-click to open the System Collector, Vector Collector, BeamSection Collector, or MultiBody panels.
Component s Materials
Same
Same
Properties
Same
Load Collectors System Collectors
Same
Vector Collectors
Select Right-click to option from expand options; Menu Left-click an icon to set new Or current icon and perform the Left-click lower right icons left-click behavior. arrow
BeamSectio n Collectors
MultiBodies Delete Left-click to open the Delete panel. Same
23

Altair Engineering
Card Edit
Left-click to open the Card Edit panel. Left-click to open the Organize panel. Left-click to open the Renumber panel.
Same
Organize
Same
Renumber
Same
Altair Engineering

24
Checks Toolbar
The Checks toolbar contains quick access to functionality for various checks and calculations that are commonly used in the model building process.
The Checks toolbar can be turned on and off from the View menu's Toolbars sub-menu. The detailed behavior of each tool button is described in the table below: Button Left-click LEFT Behavior Right-click RIGHT Behavior Same Same Same
Distance Length Mass/Area Calc Edges Features Faces Normals
Opens the Distance panel Opens the Length panel Opens the Mass Calc panel
Opens the Edges panel Opens the Features panel Opens the Faces panel Opens the Normals panel
Same Same Same Same Same
Penetration/ Opens the Penetration panel Intersection Check Check Elements Model Summary Loads Summation Count Opens the Check Elements panel Opens the Summary panel
Same
Same
Opens the Loads Summary tab Opens the Count panel
Same
Same
25

Altair Engineering
Altair Engineering

26
Display Toolbar
The Display toolbar controls what entities are displayed in the graphics area, primarily by masking entities to hide or display them. Other display controls for all collectors and entities are manipulated at a high level using the Model Browser and the Mask Browser.
The Display toolbar can be turned on and off from the View menu's Toolbars sub-menu. The Model Browser and Mask Browser can be turned on and off from the View menu. The detailed behavior of each button is described in the table below. Button Left-click LEFT Behavior Right-click RIGHT Behavior Same
Mask Reverse Elements
Opens the Mask panel
Reverses the mask state of all Reverse All Reverses the elements in currently displayed mask state of collectors all entities (elements, loads, etc) in currently displayed collectors. Unmask the row of elements Same adjacent to the currently displayed ones. If some of the unmasked elements reside in components which are currently not displayed, those components will also be unmasked Unmask all entities (elements, loads, etc) in currently displayed collectors. Same
Unmask Adjacent
Unmask All
Mask Not Shown
Mask all entities (elements, Unmask loads, etc) located outside of Shown the graphics area but in currently displayed collectors.
Unmask all entities (elements, loads, etc) located outside of the graphics area but in currently
27

Altair Engineering
displayed collectors. Spherical Clipping Open the Spherical Clipping panel, which lets you select a center point and radius for the spherical clipping and enable or disable it. Open the Find panel Open the Numbers panel Same
Find Display Numbers Display Element Handles
Same Same
Toggle element handles on/off. The same operation can be performed from the Graphics subpanel located in the Preferences > Graphics menu. Toggle load handles on/off. The same operation can be performed from the Graphics subpanel located in the Preferences > Graphics menu.
Same
Display Load Handles
Same
Display Fixed Points
Toggle fixed points on/off. The Same same operation can be performed from the Graphics subpanel located in the Preferences > Graphics menu.
Altair Engineering

28
Visualization Toolbar
The Visualization toolbar controls how entities are visualized in the graphics area, including control for setting the geometry and mesh color mode The visualization toolbar can be turned on and off from the View menu, Toolbars sub-menu.
The detailed behavior of each tool button is described in the table below. Button Leftclick LEFT Behavior Rightclick RIGHT Behavior
Pick a Automatically selects one of the following Same differen color modes based on the currently t mode active panel. All colors can be changed from the Options > Colors panel. This panel can be accessed from the Menu bar via Preferences > Colors or by pressing the <o> key. Pick a All surfaces and solid faces are colored differen by the color assigned to the component t mode in which that geometry resides. All surface edges and solid face edges are colored black. A component's color can be changed using the Model Browser > Component View . Same
Pick a Surfaces are colored gray (2D faces Same differen (topo) with surface edges colored by t mode topology: red (free edges), green (shared edges), yellow (t-junctions), or blue (suppressed edges). Solid faces and face edges are colored transparent green (bounding faces) with internal faces colored yellow (full partition faces). Pick a Surfaces are colored gray (2D faces differen (topo) with surface edges colored by t mode topology: red (free edges), green (shared edges), yellow (t-junctions), or blue (suppressed edges). Solid faces and face edges are colored blue, ignoring solid topology. Same
29

Altair Engineering
Pick a Surfaces and surface edges are colored Same differen blue, ignoring surface topology. Solid t mode faces and face edges are colored transparent green (bounding faces) with internal faces colored yellow (full partition faces). Pick a Surfaces are colored by component with Same differen surface edges colored by topology. Solid t mode faces are colored by component with solid face edges colored by topology. Pick a Surfaces display in wireframe mode, with Same differen surface edges colored blue (ignoring t mode topology). Solid faces are colored by mappability: red (not mappable), yellow (1d mappable), or green (3d mappable). Solid face edges are colored by topology. Shaded Geome try with Surface Edges Button: set geometry mode to shaded with surface edges. Arrow (lower-right): Select option from menu Same Same
Shaded Button: set geometry mode to shaded. Geome Arrow (lower-right): Select option from try menu Wirefra me Geome try with Surface s Lines
Button: set geometry to wireframe with Same surface lines. Arrow (lower-right): Select option from menu
Wirefra Button: set geometry to wireframe me mode. Geome Arrow (lower-right): Select option from try menu Transp arency Opens the Transparency panel
Same
Same
Pick a All elements are colored by the color differen assigned to the component in which that t mode element resides. A component's color can be changed in the Model Browser
Same
Altair Engineering

30
by right-clicking its color box and picking a new color. Pick a All elements are colored by the property Same differen assigned to that element. Properties are t mode assigned to elements directly or indirectly. Properties are assigned directly to the element by using the Property > Assign panel. Indirect element properties are inherited from the component in which the element resides; component properties are assigned in the Component > Assign panel. Directly assigned properties override indirect ones. Solvers in group #1 (RADIOSS (Bulk Data), OptiStruct, Nastran) can support both direct and indirect element property assignment. Solvers in group #2 (RADIOSS (Block), LS-DYNA) only support indirect element property assignments. Any element without a property is colored gray. A property's color can be changed in the Model Browser by right-clicking its color box and picking a new color Pick a All elements are colored by the material Same differen assigned to that element. Materials are t mode assigned to elements differently for solver group #1 and solver group #2; Solver Group #1 (RADIOSS (Bulk Data), OptiStruct, Nastran) assign materials to properties, and then properties to elements (either directly or indirectly as discussed in Color by Property). Elements with both direct and indirect property assignments use the material associated with the direct element property assignment. Solver group #2 (RADIOSS (Block), LS-DYNA) assigns materials to elements indirect by assigning materials to the component in which the element resides using the Component > Assign panel. Any element which does not have a material assigned to it, directly or indirectly, will be colored gray. A material's color can be changed in the Model Browser by right-clicking its color box and picking a new color.
31

Altair Engineering
Pick a All elements are colored based on the Same differen assemblies they belong to. Each t mode assembly receives a different color (although models with many assemblies may have colors repeated for more than one assembly). Any elements that do not belong to an assembly are colored gray. An assembly's color can be changed in the Model Browser by rightclicking its color box and picking a new color. Pick a All elements are colored by their differen topology: green (1D), blue (2D), and red t mode (3D). Same
Pick a All elements are colored by their element Same differen configuration (mass, reb2, spring, bar, t mode rod, gap tria3, quad4, tetra4, etc.). An element's configuration color can be changed from the Element Types panel. Pick a Shell elements are colored according to Same differen their thickness values; if no thickness is t mode specified for any element they will all be the same color. However, elements with thickness values are colored individually according to their thicknesses, and a key to indicate which thickness corresponds with each color displays in the corner of the graphics area.
This feature works in conjunction with the Detailed Element display option described below. Shaded Elemen ts with Mesh Lines Set current element visual mode to Select shaded with mesh lines. Elements are option shaded, and surface mesh lines display. from menu Left-click the lower right arrow to expand the Options Menu. Right-click to expand Options Menu; Left-click an icon to
Altair Engineering

32
set new current icon and perform icons left behavior. Shaded Elemen ts with Feature Lines Set current element visual mode to shaded with feature lines. Elements are shaded but have no mesh lines, while feature lines display. Left-click the lower right arrow to expand the Options Menu. Select option from menu Right-click to expand Options Menu; Left-click an icon to set new current icon and perform icons left behavior. Right-click to expand Options Menu; Left-click an icon to set new current icon and perform icons left behavior. Right-click to expand Options Menu; Left-click an icon to set new current icon and perform icons left behavior. Right-click to expand Options
Shaded Set current element visual mode to Elemen shaded. Elements are shaded, but no ts lines display. Left-click the lower right arrow to expand the Options Menu.
Select option from menu
Wirefra me Elemen ts (skin only)
Set the current element visual mode to wireframe (skin only). Internal mesh lines will not display. Left-click the lower right arrow to expand the Options Menu
Wirefra Set the current element visual mode to me wireframe . Internal and surface mesh Elemen lines display.
Select option from
33

Altair Engineering
ts
Left-click the lower right arrow to expand the Options Menu.
menu
Menu; Left-click an icon to set new current icon and perform icons left behavior. Right-click to expand Options Menu; Left-click an icon to set new current icon and perform icons left behavior. Right-click to expand Options Menu; Left-click an icon to set new current icon and perform icons left behavior. Right-click to expand Options Menu; Left-click an icon to set new current icon and perform icons left behavior. Right-click
Transp arent Elemen ts and Feature Lines
Set current element visual mode to transparent with elements and feature lines. Elements are shaded but transparent, no mesh lines display, but feature lines do. Left-click the lower right arrow to expand the Options Menu.
Traditio Display only the simple elements for nal 2D beams and similar entities. Elemen t Repres entatio n
3D Elemen t Repres entatio n
Display more detailed, shape-based representations of beams and similar entities. Shell elements with thickness values will display as 3D blocks, although they are not treated as 3D solid entities--they remain 2D shell elements in every respect except how they display. Offsets are also shown.
Traditio Display both the simple and detailed,
Select
Altair Engineering

34
nal and 3D Elemen t Repres entatio n
shape-based representations of beams and similar entities. Shell elements with thickness values will display as 3D blocks superimposed over their true 2D selves, but these blocks are for display purposes only--the elements are not treated as 3D solids for any calculation. Offsets are also shown.
option from menu
to expand Options Menu; Left-click an icon to set new current icon and perform icons left behavior. Right-click to expand Options Menu; Left-click an icon to set new current icon and perform the icons left behavior. Right-click to expand Options Menu; Left-click an icon to set new current icon and perform the icons left behavior. Right-click to expand Options Menu; Left-click an icon to set new current icon and perform
Layers off
Ply layers are not displayed.
Compo Plies in a composite material are site displayed. layers
The exact nature of the display depends on the 2D/3D element visualization button. See Element and ply visualization for details. Compo Display layers with vectors indicating site their appropriate ply orientation. layers with fiber directio n The exact nature of the display depends on the 2D/3D element visualization Select option from menu
35

Altair Engineering
button. See Element and ply visualization for details.
the icons left behavior.
Shrink Left-click the tool button to toggle on/off Same Elemen shrink elements by shrink factor. ts Shrink factor can be set from the Options > Graphics panel. The Options panel can be accessed from the menu bar; Preferences > Graphics. Visuali zation Option s Left-click the tool button to open Visualization Controls tab. Same
Altair Engineering

36
Element and ply visualization

The exact visualization of ply layers in a composite material depends on both the composite visualization button and the element (complexity) visualization button. These two work in tandem to determine exactly how composite layers display.
2D/3D element visualization
composite visualization
Simple Element display:

Composite layers, when visible, are represented as 2D shells:
Layers off
Composite Layers
Layers w ith fiber direction
37

Altair Engineering
3D element Representation:
Layers off
Composite Layers
Traditional and 3D Representation:
Altair Engineering

38
Layers off
Composite Layers
39

Altair Engineering
HyperMesh tabs
The primary use for tabs in HyperMesh is to house browsers. You may still encounter other tabs, such as file import/export tabs, while using HyperMesh--but these are common features that appear in multiple HyperWorks Desktop applications, and are not specific to HyperMesh itself. In addition you may encounter other browsers in the tab area as well when using other applications, but this section of the HyperMesh Help refers specifically to the features that only display when HyperMesh is the active desktop application. HyperMesh tabs include the following: HyperMesh Connector Browser HyperMesh Entity State Browser HyperMesh Loadcase Browser HyperMesh Mask Browser HyperMesh Model Browser HyperMesh Solver Browser HyperMesh Utility Menu
Altair Engineering

40
HyperMesh Calculator
The HyperMesh calculator opens when you right-click on any active numeric field. This calculator is designed using "reverse Polish" notation, meaning that you enter the value that you wish to apply first, and then click the operation that you wish to perform. To enter a value (such as 80), just click the numbers to represent this number and click the enter key. 1) Click 8. 2) Click 0. 3) Click enter.
HyperMesh converts this number into scientific notation: 8.000 e+-1.
Working with pre-populated values

In the example below the Distance panel was used to populate the calculator with the current value of 1.430 e+02; this value was already in the active numeric field when the field was right-clicked. If you wish to divide this value by two, you click 2 and then the divide symbol (/). Thus, the overall syntax of the math operation would be written as "1.43e+1 2 /" rather than "1.43e+1 / 2".
1) With the current value of 1.430 e +01, Click the number 2. 2) Click the / symbol. 3) Click enter. The new calculated value displays:
41

Altair Engineering
Thus, you divided the original value (14.30 or 1.430e+2) by 2 to yield 7.150 (7.150e+1).
Click exit to close the popup.
Altair Engineering

42
Browsers
Browsers supply a great deal of view-related functionality in HyperMesh by listing the parts of a model in a tabular and/or tree-based format, and providing controls inside the table that allow you to alter the display of model parts.
Basic Browser Operations Connector Browser Entity State Browser Include Browser Loadsteps Browser Mask by Config Browser Model Browser Set Browser Solver Browser Utility Menu
43

Altair Engineering
Basic Browser Operations

Browsers display information in a tree view. In tree views, collectors such as Components or Groups appear at the top level of the hierarchy, while collected entities such as Elements or Surfaces display as "children" nested within the collector to which they belong. Each item in a tree view is commonly referred to as a "node", regardless of whether it's a Parent Node or a Child Node.
This example show s several instances of children nested w ithin parent nodes.
Generally speaking, performing an action on a child node affects only that item, be it a single Load or the entire collection of Elements in the model (which, in the example above, are collectively a child node of the
Altair Engineering

44
Components parent node). However, performing the same action on a parent node automatically applies it to all children of that node as well. For example, in the screenshot above you could turn off display of the Elements without affecting the display of connectors, geometry, or Components (the parent node of the Elements. However, if you turned off the display of Components, then Connectors, Elements, and Geometry would also be turned off because they are children of the Components node. Different browsers are customized for usage with regard to the types of parts that you want to work with. Most browsers have similar basic functionality for Sorting Entities, Filtering Entities, and Finding Entities. However, most browsers also include include a context-sensitive right-click menu and sets of control buttons (similar to toolbars, but unable to be detached to re-docked) that are specific to the browser in which they appear. Each of these is described in the appropriate browser's help.
45

Altair Engineering
Sorting Entities
You can sort the entities in a folder by clicking on the heading of each column. Click the Entities heading to sort alphabetically by name, or click the ID heading to sort numerically by entity ID. In either case, repeated clicks toggle between ascending and descending order.
Altair Engineering

46
Filtering Entities
You can filter the entity types that appear in the browsers tree structure by clicking the Show Filter option from the browser context sensitive menu. This feature allows you to determine which categories of entity appear in the browsers tree structure. Clicking this feature adds a new list box to the browser, named Show: and located just below the browser view controls. Click this list box to open a list of all the entity types that can display in the tree structure. Each entity type in the list has a checkbox next to it; click the checkboxes to toggle the display of that entity type as a folder in the browsers tree structure. For example, the Components folder only displays in the tree structure if Components is checked in this list. In this way, you can make the tree structure shorter and easier to navigate by removing entity types from the browser list that you do not need to work with.
47

Altair Engineering
Altair Engineering

48
Notice that the list of available entity types includes you aricons for Display All, Display None , and Reverse Display as described in the Global Display Tools. However, in this case they are used for selection; Select All, Select None , and Reverse Selection. In addition, the list contains buttons labeled OK and Cancel. Whene satisfied with your selection of entity types, click OK to close the list. Otherwise, click Cancel to discard your changes and close the list without altering the Model Browsers tree structure. You can also select groups of entities based on a wildcard search. Accomplish this via the Matching: combo text/list box. For example, if you type *collector into this combo box and press <enter>, then all entity types ending with "collector" will be checked and display in the list. Fine-tune the search/selection by choosing an option from the ( ) button:
Match case only selects tree items that match the entered text exactly, including upper/lower case letters Whole name only selects tree items whose entire name matches the specified text. For example, typing pillar in the matching field when using the whole name option will not locate a component named "CH-A-PILLAR-B-I-L". To find such a component, you would need to run a wildcard search for something such as *pillar*.
49

Altair Engineering
Finding Entities
You can locate an entity by clicking the Show Find option within the context sensitive menu. This opens a new line of entries within the top of the browser; the additional options include a combination text/list Find: box and arrow buttons for Find Next, Find Previous, Find All and Options for searching (represented by a downward-facing double arrow).
To find an entity, type a search string into the combination box and (if necessary) click the Options for searching button to reveal a list that allows you to specify search behavior: Match Case Only entities whose names contain the search string with upper/lower case matching what you typed into the Find: box. For example, with this option active, a search for "chassis" will ignore an entity called "Chassis". Only those entities whose complete name matches what you typed into the Find will be found: box, rather than only part of the name. In other words, if you type "chassis" into the Find: box, entities labeled "chassis1", "FrontChassis", or "RearChassis1" will be ignored. Wildcards allow you to search for any items that partially match the text you are searching for. For instance, you could search for "*pillar" and find components named "A-Pillar" and "B-Pillar". Note that using wildcards is generally not compatible with searching for whole names! By ID Using this option allows you to type an entity ID into the Find: box instead
Whole Names
Use Wildcards
Altair Engineering

50
of a text-based name.
Note that these options are on/off toggles; clicking one activates it (represented by a checkbox in the list). To deactivate the option, select it again to remove the checkbox. In this way you can combine the search options, such as searching for whole names with matching case. To find entities matching your specified string and options, click the up or down arrow buttons to search upward or downward through the browsers tree. In this way, you can continue searching by repeat clicks of these buttons; for example, after clicking the down-arrow and finding the first match, you can find the next match by clicking the down-arrow again. When the find function reaches the bottom of the tree it will start over again from the top, until it has performed a single full loop from its starting point. So, for instance, if the tree contains three entities matching your search string, clicking the down-arrow button finds match #1; clicking again finds match #2; clicking third time finds match #3; clicking a fourth time reaches the end of the tree and starts over from the top, finding match #1 again. To find all of the matching entries, click the Find All button (the double-headed arrow). This finds and highlights all matching entries in the tree list. Once the entity that matches the entered string is found, it is highlighted in the Model Browser. If the entity is found inside an assembly that is collapsed, the appropriate assemblies are expanded to expose the entity. Since this function works in combination with the filters, it only searches for items currently shown in the tree.
51

Altair Engineering
Dialogs
Whenever you create, edit, or assign properties to a new component, property, or material, you enter the relevant information in a dialog box that opens when you choose the desired function. For example, if you right-click on a component in Model Browser and and select create from its context-sensitive menu, the Create Component dialog opens.
Dialogs are dynamic, with different fields and tabs being enabled or disabled depending on the needs of the solver associated with your current user profile. Dialogs also retain the last set of information entered upon the previous create action; if you create a new entity, the details are saved for the next time you used the create dialog. If, however, you cancel the dialog without creating anything, these details are lost. Finally, due to the dependence on user profiles, changing your profile while a dialog is open has the same effect as clicking Cancel. When you create a new entity, the dialog does not close unless you activate the Close dialog upon creation checkbox (or click the "X" in the dialog's title bar). This allows you to use the same dialog to create multiple entities of the same type without needing to go through the right-click menu to open a new dialog each time. By default, you must click the Cancel button to close the dialog. When you access a dialog by right-clicking on an existing item in the browser, the dialog defaults to the same information as the item that you right-clicked on. This allows you to quickly create series of similar properties and components by changing only one or two variables without having to re-enter all of the common information for each item. Even if you don't begin the process by right-clicking an item, you can still populate the fields in the dialog by activating the same as checkbox and picking an existing item from the list box. The color and other properties will be set to the same values as the item you selected. Note that the same as field is disabled if there are no other entities in the database of the same type. The material and property tabs of the Assign dialog allow you to type in a name for the desired material or property. When you type in a name that already exists in the database, the values associated with that
Altair Engineering

52
preexisting material or property automatically fill in the fields of the tab. This behavior appears on the Create Component dialog's Property and Material tabs, as well as in the Create Property dialog. Note : If you attempt to assign properties or materials using names that already exist in the database, the pre-existing property or material will be assigned. Its values will display in the dialog as described above, but cannot be edited.
Updating Multiple Entities

You can use typical <shift>-click and <ctrl>-click functionality in the Model Browser to select multiple entities. If you choose multiple entities and then edit their properties or materials, the Name field in the Update dialog will be empty, and all of the selected entities will be set to the same values and color chosen in the dialog. When you have selected multiple entities with different data in certain fields, those fields will also display as blank. If you leave these blank fields empty, the corresponding data for each selected entity will not be updated--the original, individual values will be kept. If, however, you enter a new value into the blank field, that value will be applied to all of the selected entities, overwriting whatever values they previously had for that field.
53

Altair Engineering
Connector Browser
The Connector Browser is used to view and modify connectors in the current model (for details on what a connector is, see Connectors and its sub-topics in the section on HyperMesh Entities). The Connector Browser can be invoked from the View menu and displays in the tab area.
The browser includes two major areas: The Link Entity Browser in the top of the tab, which displays information for the linked entities in the model, and A tree view of all the connections contained in the model, located in the lower half of the tab.. These connectors display in folders, organized based on the respective realization types. The names of the folders are obtained from the FE configuration names specified for respective solvers in the feconfig.cfg file. The browser can directly affect the graphics engine by selecting, highlighting, showing or hiding entities. It also provides quick access to HyperMesh functionality such as finding links, finding connectors from links or realizations, renumbering, masking, creating & deleting; and quick access to connector entity functionality such as add links, remove links, update links, and editing connector attributes. The browser and the HyperMesh database synchronize to ensure that all changes to the connector or component information in
Altair Engineering

54
the database is reflected correctly in the browser at all times. The browser can be configured to display only the information that you wish to see; the current configuration is saved, so that the next time you open the browser it opens with the same configuration as the last time that it was used.
Connector Browser Functionality

Tool sets and context-sensitive menus provide functionality in the Connector Browser. Each section (Link Entity Browser and Connector Entity Browser) includes its own set of tools. The Link Entity Browser includes a context-sensitive menu, a Global Display tool set, and an Action Modes tool set similar to that found in the model browser (rimmed in blue below). In addition, it contains toggle buttons for view options (red) and advanced action buttons (yellow).
The Connector Entity Browser includes a context-sensitive menu, a Global Display tool set, and an Action Modes tool set (rimmed in blue below). In addition, it contains toggle buttons for view options (red) and advanced action buttons (yellow). Finally, a Utility tool set at the bottom of the browser accesses various HyperMesh panels, and exports connector data in XML format.
Specific tasks that can be performed using the Connector Browser include: Adding Links or Removing Links Update Links Finding Connectors from Parts or Finding Connectors from Realizations, and Finding Links from Connectors.
55

Altair Engineering
Link Entity Browser

This contains a tabular display of the links that are connected using the connectors in the model. Currently only a component view is supported. This information is non-editable, but can be used to quickly locate certain links and appropriate connectors in the graphics area. Unless all view option toggle buttons are inactive (with an orange background) the global display tool set, the action mode tool set and the context menu actions (show, hide, isolate, isolate only) work exactly as it they do in the Model Browser's component view. Only component links are taken into account for these actions. If at least one of the view option toggle buttons is active, the behavior of show, hide, isolate and isolate only is different. The style of the action buttons changes to indicate the different behaviour (additional connector symbol on the standard action buttons).
The actions take into account connector-link-relations, and the display result depends on the active view options. Therefore parts of the model are separated into three different categories based on the link selection. These categories are: 1st link entity: selected links (components) linked connectors: connectors which reference at least one of the selected links 2nd link entity: links (components) which are referenced by the linked connectors
Note that in this case connectors and their realizations are treated as being a separate category from their links, in order to prevent unpredictable cross-references. This kind of categorical separation is only used for the actions show , hide , isolate and isolate only, and only when one of the view option toggle buttons is active, regardless of whether the actions are taken from the context menu or the action buttons. No other functionality uses this categorization at all. You can also change the base features of the Link Entity Browser in the Link Entity Browser configuration window.
Altair Engineering

56
Link Entity Browser Action Modes Tools

The series of icons found on the right side of the Link Entity Browser control both entity selection and the display of the model. These buttons behave in two different ways depending on the setting of the view option buttons. If no view option button is active, the core behavior of the action mode tools remains exactly the same as in the component view of the Model Browser. For that reason, this topic focuses on the behavior when a view option is active. In this mode the actions like show , hide , isolate or isolate only are not only done on the pure selection. Based on the selection a certain process of finding and filtering is performed so that further entities can be taken into account for the action depending on the setting of the view option toggle buttons.
Each tool button is explained below: The next and previous buttons cycle through the selected links in the table, but are only active when link entities in the table are selected (highlighted). These are especially helpful when not all selected links can be seen in the partial view of the list. This button affects how the rest of the tools work, by determining what type of entity they will act on. For example, when set to "components", the selector tool (described below) will only select or deselect components. This icon is disabled and set to component because the Connector Browser only supports components as links. In addition to the previous button, this one limits the action mode tools to affect only elements, geometry, or both. elements only geometry only both Note that even if you choose elements only, you can still perform actions on connectors (geometric entities) by selecting their link entities. However, any action taken (such as Isolate) will only affect the entity types specified by this button. In the case of geometry only, only connectors with at least one link state defined as "geometry" are taken into account. Since connectors can be defined as linking elements, surfaces, or a combination of both, this button affects actions taken on them in a similar manner. For example, if you set the button to "elements only" but select a connector that only connects geometry, the actions you might take
57

Altair Engineering
on that connector will not affect it. However, if the connector links both geometry and elements, then any actions taken would still apply to the connector due to the element links. Use the Selector tool to interactively select any type of supported link entity via the browser, or by selecting within the graphics area. The Selector can be used to Find link entities from the graphics area which will then be highlighted in the list, and is also an efficient way of selecting multiple link entities at once. Finally, the Selector can be used in conjunction with the action buttons show , hide , isolate and isolate only as well as the advanced action buttons show/hide connectors between and isolate/isolate only connectors between; simply select link entities from the browser or graphics area using the Selector, then click the desired action button. Note that these advanced action buttons only activate when at least two link entities are selected. In other respects the Selector works exactly the same as described for the Model Browser. The Add to Panel Collector is a function whereby the browser can be used to select and add entities to the panel collectors within HyperMesh. This is an alternative method to using the advanced selection capabilities already available in each panel collector's extended entity selection menu. This button only becomes available when you have a HyperMesh panel open that includes at least one entity collector. Show/Hide the currently selected entities, depending on the currently active view option toggles. Alternatively, click this mode on and then pick the desired links from the graphics area; links (and any other entities determined by the view options) are hidden as you click on them. Note that when used to select from the graphics area, this button only works on visible links. Isolate/isolate only the currently selected entities. Alternatively, click this mode on and then pick the desired link entity from the graphics area. Isolate displays only the selected entities which match the view option toggles, turning their display state to on and turning all other entities of the same type off. Isolate works locally within a specific entity type--for example if component(s) are isolated then all display states of other displayable entities, such as Load Collectors, remain untouched. Isolate Only works like Isolate , except that it also affects entity types different from the matching, selected entities. Thus, it turns off ALL displayable entities (regardless of type) except for the selected one(s) that match the view option settings. Note that unlike the normal isolate button, when used in the graphics area this button only works on visible links. Reverts the most recent action taken. When you perform an action, the current display states of all elements and the view is stored before executing the action. Up to 5 states can be stored, so repeated use of the Undo button allows you to revert multiple actions in reverse order.
Altair Engineering

58
Link Entity Browser View Option Toggle buttons

The Link Entity Browser is a tool to easily examine the connections between the different parts of a model. One strategy to do that is to start the investigation on one part or a certain group of parts, so each action in the Link Entity Browser starts with a selection of parts. Parts can be considered as links. These view options affect the Link Entity Browser Action Modes Tools, and thus determine the entities that display when you select and then show , hide , or isolate a link.
Each button is modal--that is, you click it once to activate it, and click it again to deactivate it. Active buttons remain active until you specifically deactivate them, so you do not need to worry about them "resetting" after you perform an action such as isolate .
active
inactive
The following model illustrates the effects of these search options. Note the highlighted component; this component is the starting point for the following examples.
59

Altair Engineering
(Model provided courtesy of Audi)
In each case below, the selected component has been Isolated, using only the relevant view option. Option Name 1st link entity Effect The selected link entity can always be seen as the 1st link entity, even if the selected part isn't referenced by any connector at all. If the 1st link entity view option button is active, the selected links will be taken into account for the action regardless. This means that in case of the isolation, all selected links will be isolated.
Altair Engineering

60
Linked connector entity If this linked connector entity view option button is active all connectors linked to the 1st link entities will be taken into account for the action. It doesn't matter if the 1st link entity view option button is active or inactive, its connectors will still be located (this determination has nothing to do with any display states). This means that in case of the isolation, only the connectors which are referenced by the selected links (1st link entity) are isolated.
2nd link entity
If the 2nd link entity view option button is active, all link entities referenced by the determined connectors except the (selected) 1st link entities will be taken into account for the action. It doesn't matter if the 1st link entity or the linked connector entity view option buttons are active or inactive; this determination has nothing to do with any display states. In the case of isolation, this means that only the links that share connectors with the selected entities are isolated.
Note that the selected link is hidden because 1st link entity w as not active.
Realization
When this option is active, all realizations belonging to the determined linked connector entities will be taken into account for
61

Altair Engineering
the action.
Fit view
This button is meant to be used in combination with other view option toggle buttons and show , hide, isolate, or isolate only or together with the advanced action buttons. After the action is performed, the newly found connectors are placed in the middle of the screen. If this button is used in any combination with one of the previously mentioned buttons, it works like a pure fit view .
In this example, the link entity w as Isolated w ith the fit view option.
Cumulative effect of multiple options

These options work accumulatively--for example, when both the 1st link entity and 2nd link entity buttons are active, then selecting and isolating a component link displays both it and all of the components connected it. If you had realization, 1st link entity, and 2nd link entity active when you isolated the same component link, then the model would display all of the component links connected to the selected one, as well as graphical representation of the realizations of each connector linking those component links together.
Altair Engineering

62
The first image show s an isolated view w ith only 1st link and connectors. The second includes 1st and 2nd links, connectors, and realizations.
Using the 2nd Link option to expand the selection

You can use the 1st link and 2nd link options together to gradually add more and more component links to your viewable model by starting with a small area, such as a single component, and then selecting additional components. The example below starts with a single component that has been isolated using the 1st link and linked connector entity options. Then, using the 1st link, linked connector entity, and 2nd link options, the Show action mode tool is activated. In each subsequent image, one component (highlighted) is selected to be shown. Because the 2nd link option is active, all components connected to the selected one are revealed.
Here, the initial isolated component has been selected.
63

Altair Engineering
All entities attached to the component are revealed. Another is selected.
Again, link entities attached to the selected one are revealed. A third is selected...
...And still more entities, having no direct connection to the original part, display.
Altair Engineering

64
Link Entity Browser Advanced Action Buttons

Located adjacent to the view option toggle buttons, these two buttons allow you to show , hide , isolate or isolate only connectors shared by two or more link entities, by picking the component links (or other supported link entities) that they connect. These advanced actions then select the connectors referenced by the selected link entities and perform the desired action (show, hide, etc.) upon them.
These buttons only enable when you select at least two entities from the graphics area or the Link Entity Browser list, and they perform different actions depending on the mouse button used: Button Name Show/Hide Left-Click behavior Show connectors between the selected entities. Isolate the selected entities and the connectors between them. Right-Click behavior Hide connectors between the selected entities. Isolate only the connectors between the selected entities.
Isolate/ Isolate Only
Unlike other action-type buttons, these two are not affected by the link view option toggle buttons (1st link, 2nd link, or linked connector). However, they do work in conjunction with the realization view option button. You can specify how these shared connectors are determined by changing settings in the Link Entity Browser configuration window.
65

Altair Engineering
Link Entity Browser Global Display Tools

Use this tool set to display or hide the graphics for components in the browser list.
Elems/Geom/Both (filter for All/None/Reverse and local display control) Display All Display None Display reverse The Elements/Geometry/Both button determines what the other buttons act on; left click the small triangular downward arrow to reveal a drop-down menu of options. You can select Elements, Geometry, or Both. The Display All, Display None , and Reverse Display buttons at the top of the tab change the display state of all linked components in the list. All displays and None hides all of the items shown in the list/tree. Reverse reverses the state of all entities (displaying the hidden and hiding the displayed). However, if you have multiple link entities selected in the browser list, then these actions are only performed on the selected entities. To deselect all currently selected entities, simply left-click in any empty "white space" within the browser list, such as between columns. Note : These buttons only affect the display state. They do not actually remove entities from the model, but only show or hide them in the graphics area.
Altair Engineering

66
Link Entity Browser Context Menu

Access the Link Entity Browser's context-sensitive menu by right-clicking on one or more components in the list.
You must select one or more components before using the context menu. You can select components by left-clicking a component, using <shift>-click and <ctrl>-click functionality to select multiple components in the list, or using the Link Entity Browser Global Display tool set. Once you have selected the desired components, right-click anywhere inside the list to open the context menu; the available options are: Find / Find with FE The selected component links and all connectors referencing them are isolated in the graphics area. The component links as well as the linked connectors are highlighted in their browsers. This Find operation considers only the realization and fit view buttons. When the realization button Find Attached / Find Attached with FE is active, Find changes to Find With FE.
The selected component links, all connectors referencing them, and all component links referenced by these connectors are isolated in the graphics area. All the found component links as well as the linked connectors are highlighted in their browsers. This Find Attached operation considers only the realization and fit view buttons. When the realization button With FE. is active, Find Attached changes to Find Attached
Find Between / Find Between with FE
The selected component links and connectors that link them together are isolated in the graphics area. All the found component links as well as their shared connectors are highlighted in their browsers. This Find Between operation considers only the realization and fit view buttons.
67

Altair Engineering
When the realization button With FE.
is active, Find Attached changes to Find Attached
Note that the definition which kind of connector is found by this action can be set in the options tab of the Link Entity Browser configuration window. By default, a connector which references at minimum two of the selected component links is treated as a "between" connector. Show Works exactly like the action button Show . All view option button settings are considered. Works exactly like the action button Hide . All view option button settings are considered. Works exactly like the action button Isolate . All view option button settings are considered. Works exactly like the action button Isolate Only. All view option button settings are considered. Reveals or hides the Find box described in Finding Entities under Basic Browser Operations. Opens the Link Entity Browser configuration window.
Hide
Isolate
Isolate Only
Show find / Hide find Configure Browser
Altair Engineering

68
Link Entity Browser Configuration Window

Accessed from the right-click Link Entity Browser Context Menu, this new window allows you to alter the columns that display in the Link Entity Browser, and how the special features such as the find between tool operate.
Columns tab
This tab allows you to check all of the columns that you wish to display in the browser, and uncheck ones that you wish to hide so that they do not display.
When the Column types radio button is active, the checkboxes also become active. Furthermore, the buttons for select all, select none , and invert selection also become active, as they only affect the listed column checkboxes.
Options tab
This tab allows you to determine how the find between tool locates connectors.
69

Altair Engineering
The options to for using the find between tool include: minimum two selected links: only connectors that link to at least two selected entities will be affected. Connectors with only one link to any of the selected entities will be ignored. exact selected links: only connectors that only link to the selected entities will be affected. This can vary from the minimum two selected links option, because connectors with three or more links which link two selected entities with at least one unselected entity, would still be found by the minimum two selected links option but not by this one. all selected links: any connector shared by the selected entities will be found. Note, however, that connectors which link selected components to any unselected ones will not be found, as they are not located between the selected comps. In addition, you can select the global option to use the striped background (in which each line of the browser lists will alternate background colors.)
Altair Engineering

70
Connector Entity Browser

The lower section of the Connector Browser contains a tree view of all the connections contained in the model, and has its own set of tools similar to the ones found in the link entity browser. All the connectors in the model are displayed in folders organized based on the respective realization types. The names of the folders are obtained from the FE configuration names specified for respective solvers in the feconfig. cfg file. The connector information in the tree can be used to find link entities connected by specific connectors, and also to modify certain connector attributes. The columns display a sub-set of connector information that is important for recognizing connection information easily. Unless all view option toggle buttons in the global display tool set are inactive, the action mode tool set and the context menu actions (show, hide, isolate, isolate only) work similarly to their functions in the Model Browser's component view . If at least one of the view option toggle buttons is active (appearing in orange), the behavior of show, hide, isolate and isolate only is different. The image on the action buttons changes to include a connector symbol, indicating the different behaviour.
The actions take into account connector-link relations, and the display result depends on the active view options. Therefore parts of the model are separated into three different categories based on the connector selection: 1st connector entity: selected connectors linked entities: links (components) which are referenced by one of the selected connectors 2nd connector entity: connectors which reference at least one of the linked entities (components) Note that in this case connectors and their realizations are treated as being a separate category from their links, in order to prevent unpredictable cross-references. This kind of categorical separation is only used for the actions show , hide , isolate and isolate only, and only when one of the view option toggle buttons is active, regardless of whether the actions are taken from the context menu or the action buttons. No other functionality uses this categorization at all. You can also change the base features of the Connector Entity Browser in the Connector Entity Browser configuration window.
71

Altair Engineering
The following connector details are displayed as column data in the browser tree: Entities ID of the connector and an image that represents the respective connectors style (spot, seam, bolt, etc). The total number of link entities to be joined by the connector. This is also marked as thickness layers (2T/3T/4T, etc). The realization tolerance of the connector. You can change this by right-clicking the field and typing in a new value, then pressing <return>. The name of the component to which the connector belongs (this column is not displayed in default view). These columns (one for each link that the connector possesses) display the following information: The type of entity the connector is linked to (node, element, surface, component, etc.) and the linked entitys ID or name. Note : Link reconnect rule (use name , use id, etc) and the link state (connect to mesh or geometry) can be viewed in the link column by selecting the extended link information checkbox in the Connector Entity Browser configuration window.
Layer Tolerance
Component
Link(Number)
If you left-click and hold the mouse button on a link, the relevant component (part) highlights in the model:
Altair Engineering

72
Realize To
Where the connector is realized. One of three possible values may display here: Current comp Connector comp Property Script You can right-click and pick between current comp and connector comp, but if a property script is defined for the connectors you cannot change this field.
State
Realization state of the connector entity: unrealized, realized, or failed. Note : For those writing scripts instead of using the GUI, a more detailed report can be created by using the following lines in your script: set error_report [ hm_ce_errorreport CE_ID 1 ]
Functionality is accessed from the global display tool set, an action modes tool set, and a right-click context menu.
73

Altair Engineering
Connector Entity Browser Action Modes Tools

The series of icons found on the right side of the Connector Entity Browser control both entity selection and the display of the model. These buttons behave in two different ways depending on the setting of the view option buttons. If no view option button is active, the core behavior of the action mode tools (show / hide /isolate ) applies exclusively to the selected connectors, similarly to components in the component view of the Model Browser. For that reason, this topic focuses on their behavior when a view option is active. In this mode the actions like show , hide , isolate or isolate only are not only done on the selection; based on the selection, the browser performs a process of finding and filtering so that further entities can be taken into account for the action depending on the setting of the view option toggle buttons. Use these tool set buttons to advance or step back through multiple selected connectors, pick connectors from the graphics area, add connectors to an active panel's entity collector, turn the display of individual connectors on and off, visually isolate specific connectors, or undo any visual modifications (show /hide / isolate ).
The next and previous buttons cycle through the selected connectors in the tree, but are only active when entities in the tree are selected (highlighted). These are especially helpful when not all selected connectors can be seen in the partial view of the tree. These buttons affect how the rest of the tools work, by determining what type of entity they will act on. For example, when set to "connectors", the Selector tool (described below) will only select or deselect connectors. Note, however, that these icons are disabled and set to their default values ("connectors" and "both geometry and elements") since only connectors can be selected in the connector entity browser, but the connector browser works with all k inds of connectors--both geometry and FEbased. Use the Selector tool to interactively select any type of supported connector entity via the browser, or by selecting within the graphics area. The Selector can be used to find connector entities from the graphics area which will then be highlighted in the list, and is also an efficient way of selecting multiple connector entities at once. Finally, the Selector can be used in conjunction with the action buttons show , hide , isolate and isolate only as well as the advanced action buttons show/hide twin connectors and isolate/ isolate only twin connectors; simply select connector entities from the browser or graphics area using the Selector, then click the desired action button. Note that these advanced action buttons only activate when at least two connector entities are selected.
Altair Engineering

74
In other respects the Selector works exactly the same as described for the Model Browser. The Add to Panel Collector is a function whereby the browser can be used to select and add entities to the panel collectors within HyperMesh. This is an alternative method to using the advanced selection capabilities already available in each panel collector's extended entity selection menu. This button only becomes available when you have a HyperMesh panel open that includes at least one entity collector. Show/Hide the currently selected entities, depending on the currently active view option toggles. Alternatively, click this mode on and then pick the desired connectors from the graphics area; connectors and any other entities determined by the view option toggle settings are hidden as you click on them. Note that when used to select from the graphics area, this button only works on visible connectors. Isolate/isolate only the currently selected entities. Alternatively, click this mode on and then pick the desired connector entity from the graphics area. Isolate displays only the selected entities which match the view option toggles, turning their display state to on and turning all other entities of the same type off. Isolate works locally within a specific entity type--for example if component(s) are isolated then all display states of other displayable entities, such as Load Collectors, remain untouched. Isolate Only works like Isolate , except that it also affects entity types different from the matching, selected entities. Thus, it turns off ALL displayable entities (regardless of type) except for the selected one(s) that match the view option settings. Note that unlike the normal isolate button, when used in the graphics area this button only works on visible connectors. Reverts the most recent action taken. When you perform an action, the current display states of all elements and the view is stored before executing the action. Up to 5 states can be stored, so repeated use of the Undo button allows you to revert multiple actions in reverse order.
75

Altair Engineering
Connector Entity Browser View Option Toggle Buttons

These options affect the action mode tools, and thus determine the entities that display when you select and then show , hide , or isolate a component.
Each button is modal--that is, you click it once to activate it, and click it again to deactivate it. Active buttons remain active until you specifically deactivate them, so you do not need to worry about them "resetting" after you perform an action such as isolate .
active
inactive
The following model illustrates the effects of these search options. Note the highlighted connector; this connector is the starting point for the following examples.
Note the small, w hite-highlighted connector entity on the grey-meshed part. (Model provided courtesy of Audi)
In each case below, the selected connector has been Isolated, using only the relevant view option.
Altair Engineering

76
Option
Name
Effect
1st connector entity The selected connector entity can always be seen as the 1st connector entity, even if the selected connector doesnt reference any links at all. If the 1st connector entity view option button is active, the selected connectors will be taken into account for the action regardless. This means that in the case of isolation, all selected connectors will be isolated.
Here, only the single selected connector w as isolated (also show n in magnified view ).
Linked entity
Finds the link entities/components to which the selected connector connects. If this linked entity view option button is active all entities linked to the 1st connector entities will be taken into account for the action. It doesn't matter if the 1st connector entity view option button is active or inactive, its entities will still be located (this determination has nothing to do with any display states). This means that in case of isolation, only the entities which are referenced by the selected connectors (1st connector entity) are isolated.
77

Altair Engineering
The connector does not display because "1st connector entity" is not active.
2nd connector entity Finds other connectors that are connected to the chosen connectors' linked entities. If this 2nd connector entity view option button is active, all connectors referenced by the determined linked entities except the originallyselected 1st connector entities will be taken into account for the action. It doesn't matter if the 1st connector entity or the linked entity view option buttons are active or inactive; this determination has nothing to do with any display states. In the case of isolation, this means that only the connectors that share links with the selected 1st connector entities are isolated.
The entity does not display because "linked entity" is not active.
Realization
Finds and displays the realization for the selected connectors.
Fit view
This button is meant to be used in combination with other view option toggle buttons and show , hide, isolate, or isolate only or together with the advanced action buttons. After the action is performed, the newly found connectors and/or entities are placed in the middle of the screen. If this button is used in any combination with one of the previously
Altair Engineering

78
mentioned buttons, it works like a pure fit view .
In this example, the 1st connector and the link entity w ere Isolated w ith the fit view option.
Cumulative Effect of Multiple View Options

These options work accumulatively--for example, when both the Linked Entity and 2nd connector entity buttons are active, then selecting and isolating a connector displays the component that it links to, and all the other connectors that link to that component. If you had realization, Linked Entity, and 2nd connector entity active when you isolated the same connector, then the model would display the component to which the connector links, all other connectors linking to that component, and the realizations of each displayed connector.
The first image show s an isolated view w ith linked entity, 2nd connectors and realizations. The second includes the same options, but w ithout realizations and additional fit view .
Using Connector Links to Expand the Selection

You can use the Show feature to gradually increase the components and connectors that display. In the following example, a single connector's link entities and 2nd connectors have been isolated. By activating the Show action mode, the components and connectors that display can be expanded by clicking on connectors that currently display; since the link entities and 2nd connectors view modes are still active, each clicked connector's link entities and 2nd connectors are added to the view.
79

Altair Engineering
Here, the highlighted connector is selected for Show .
A new connected component displays. Again, the highlighted connector is clicked...
...And another connected component displays. A third highlighted connector is clicked...
Altair Engineering

80
...And a third connected component displays.
You can continue revealing more and more parts this way, theoretically eventually revealing the entire model. The reverse option is also true; by activating the Hide mode instead of Show , you could gradually "chip away" at the model, removing one connected component at a time--or multiple components in the case of multi-layer connectors.
81

Altair Engineering
Connector Entity Browser Advanced Action Buttons

Located adjacent to the view option toggle buttons, these two buttons allow you to show , hide , isolate or isolate only "twin" connectors. Twin connectors are connectors which reference at least two matching link entities. The criteria for exactly how twin connectors must match can be increased in the Connector Entity Browser configuration window to require all links to match exactly, instead of only two or more matching ones. These advanced actions then select the connectors referencing the same links and perform the desired action (show, hide, etc.) upon them.
These buttons only enable when you select at least one connector entity from the graphics area or the Connector Entity Browser tree, and they perform different actions depending on the mouse button used: Button Name Show/Hide Isolate/ Isolate Only Left-Click behavior Show twin connectors. Isolate twin connectors. Right-Click behavior Hide twin connectors. Isolate only twin connectors.
Unlike other action-type buttons, these two are not affected by the view option toggle buttons (1st connector , 2nd connector, or linked entity). However, they do work in conjunction with the realization view option button.
Altair Engineering

82
Connector Entity Browser Global Display Tools

Use this tool set to control the display of connectors.
The functionality works at three levels; if nothing is selected, this is called the global level, the display action will work on all connectors. At the folder level, if the folder is highlighted then the action will only operate on the connectors within the folder. At the local entity level, if a single or multiple connectors are selected then the operation will operate only on those selected. Display All Display None Display reverse
Note :
These buttons only affect the display state. They do not actually remove entities from the model, but only show or hide them in the graphics area.
83

Altair Engineering
Connector Entity Browser Context Menu

The Connector Entity Browser context menu includes all of the functionality available in the Connector Entity Browser, including connector creation and deletion, renumbering, updating, finding connectors, and much more. Access the Connector Entity Browser's context-sensitive menu by right-clicking in the tree list. (Note, however, that if you right-click on the Tolerance or Realize to fields of a specific connector, you will access those fields for edit rather than opening the context menu.)
The tools available in the context menu vary depending on what you right-click on; for example, right-clicking on a connector (in the entities column) accesses the full menu, but right-clicking a link (in the Link1 or Link2 columns) only presents the Remove Link option. Depending on the column clicked, the following options may or may not be available as appropriate to the
Altair Engineering

84
item clicked: Create This accesses a sub-menu of connector types; picking a type opens the related connector panel in the HyperMesh panel area, as well as the FE Absorb user interface. This accesses a sub-menu with options to delete connectors or connectors and their related FE elements. Allows a single connector to be renumbered; the change is permanently recorded in the database and the browser. Opens a dialog to input the layer value that you wish to assign to the selected connectors (this function works for multiple selections).
Delete
Renumber
Update layer
Simply type the desired number of layers into the text box and press <enter>. The layer value defines the number of thicknesses (2T/3T/etc) a connector connects at its location. The layer value defined in a connector can be greater than or equal to number of links connected by the connector. The connectors will be unrealized after this update, but the change is recorded permanently in the database and in the browser. Alternatively, you can also update the layer directly by right-clicking on the field itself rather than using the context menu. Update tolerance Opens a dialog to input the tolerance value that you wish to assign to the selected connectors (this function works for multiple selections).
You can also do this directly by right-clicking on the field itself rather than using the context menu. Update realize to If the connector doesn't currently use a property script for realization, this opens a small pop-up menu that lets you choose between current comp and connector comp.
You can also do this directly by right-clicking on the field itself rather than using the context menu. Add Link Opens a new set of controls in the bottom of the tab to add links to the selected connectors. See Add Links for in-depth instructions.
85

Altair Engineering
Update Link
Opens a new set of controls in the bottom of the tab to perform a part replacement. Note that editing a connector causes it to become unrealized.
Remove Link
This option is accessible only from the column(s) that display the link information. A sub-menu gives the option to remove the selected link(s) from the selected connectors or all connectors in the browser. The connectors will be unrealized and the change is recorded permanently in the database and in the browser. This option removes all of the links from the selected connectors. The connectors will be unrealized and the change is recorded permanently in the database and in the browser selected connectors or all connectors in the browser. The connectors will be unrealized and the change is recorded permanently in the database and in the browser. Calls the *CE_Realize command to realize connectors by accepting only a connector mark. The underlying assumption in the command is that each connector passed in the mark has the required information to be successfully realized. The required information such as tolerance, weld configuration, diameter, etc is not defined for connectors created using the FE Absorb utility; hence the Rerealize feature in the Connector Browser works only for connectors that were realized through an HM connector panel.
Remove Links
Rerealize
Unrealize
Unrealizes the selected connectors.
Altair Engineering

86
Find Parts / The components that are linked in the selected connectors are isolated in the display Find Parts with with the connectors. If the realization view option is turned on then the realized FE FE of the connectors is also displayed. The isolated components are highlighted in the table. Show Works exactly like the action button Show . All view option button settings are considered. Works exactly like the action button Hide . All view option button settings are considered. Works exactly like the action button Isolate . All view option button settings are considered. Works exactly like the action button Isolate Only. All view option button settings are considered. Activates a new tool set used to perform searches. This works exactly the same as described in Finding Entities. This option closes all the expanded folders in the browser. This option expands all the folders to display all the connectors. This operation may take some time for folders that contain thousands of connectors. Opens the Connector Entity Browser configuration window which contains options to configure the Connector Browser's list display and button behavior.
Hide
Isolate
Isolate Only
Show find / Hide find Collapse All Expand All
Configure Browser
See also *CE_Realize FE Absorb Connectors panel
87

Altair Engineering
Connector Entity Browser Configuration Window

Accessed from the Connector Entity Browser context menu, this new window allows you to alter the columns that display in the link entity browser, and how the special features such as the find twin connectors tool operate.
Columns tab
This tab allows you to check all of the columns that you wish to display in the browser, and uncheck ones that you wish to hide so that they do not display.
When the Column types radio button is active, the checkboxes also become active. Furthermore, the buttons for select all, select none , and invert selection also become active, as they only affect the listed column checkboxes.
Options tab
This tab allows you to determine how the find twin connectors tool locates connectors.
Altair Engineering

88
The Local connector options include: Extended information: When checked, this causes each link to display its link state (connect to mesh or geometry) and its reconnection rule (use ID, use name , or at fe realize ). The reconnect rule is set when the connector is created, and determines what the connector will automatically try to reconnect with when a part is deleted and then replaced: If the new part has the same part ID as the deleted one, then use ID will automatically reconnect. If the new part has the same name as the deleted one, then use name will automatically reconnect.
89

Altair Engineering
Max viewed: regardless of how many links a connector might have, only this many Link columns will display in the browser. The options for using the find twin connectors tool include: Minimum two links: Only connectors with two or more matching links will be found. Exact links: Only connectors with exactly the same links will be found. Thus, if you start with a connector with two links, another connector with three links would not be found even if its first two links matched. In addition, you can select the global option to use the striped background (in which each line of the browser lists will alternate background colors.)
Altair Engineering

90
Utility Tool Set - Connector Browser

This tool set, located at the bottom of the Connector Browser, provides tools for output of a Master Connectors File, opening specific connector-related HyperMesh panels, or utilize specialized visualization options.
Allows the connector information to be exported as a Master Connectors File in XML format (*.xml). All the connectors in the browser or currently selected connectors can be exported. Opens a temporary HyperMesh panel in which elements can be selected. Clicking the proceed button finds all the connectors that have the selected elements as their realized FE, and highlights them in the browser. This utility can be used to easily find connectors from their realized welds. Opens the spot connector panel in HyperMesh. Opens the bolt connector panel in HyperMesh. Opens the seam connector panel in HyperMesh. Opens the area connector panel in HyperMesh. Opens the apply mass connector panel in HyperMesh. Opens the connector FE Absorb GUI.
91

Altair Engineering
Link Definition
A link is a reference to a separate entity. To a connector are one or more links added. The entities to which the links refer are connected during realization. The link definition consists of the following information: Link Type Link ID/name This is the type of entity that can be added to the selected connector(s) as a link reference. Supported entities are assemblies, components, surfaces, elements, tags, and nodes. The ID or name of the entity added as a link to a connector. In the Update Link and Add Link dialog in the Connector Browser, the Link Select row corresponds to the link ID and the link name. Clicking into the fields in this row opens a temporary panel in which a specific entity can be selected. Clicking proceed returns to the Update Link or Add Link dialog. The selected entity is used to add or update a link reference. Link State This defines whether the weld created during connector realization connects to geometry or mesh on the link. This only applies to assembly, component, and surface entities that can contain geometry and/or mesh information. This defines how a connector treats an entity added as a link. Adding a link with an ID or name rule forces the connector to retain the links ID or name even if that link entity no longer exists in the database. This aids in part replacement, when a new part replaces an old part and both share the same ID or name. Adding a link with the at fe-realize rule ensures that each time a connector is realized the closest entity of the correct type is found and connected. This is useful when connectors need to connect to a closest part in an assembly.
Link Rule
Note :
The Link reconnect rule (use name, use id, etc) and the link state (connect to mesh or geometry) can be viewed in the link column by selecting the extended link information checkbox in the Connector Entity Browser configuration window.
The Connector Browser permits the performance of different actions on the links.
See also Add Link Update Links Remove Links
Altair Engineering

92
Add Link
The Add Link operation is available from the Connector Entity Browser context menu.
This tool allows one link (component, assembly, surface. element, tag, node) to be added at a time to one or more connectors. The connector(s) number of layer (T) value can be incremented during the link addition operation.
93

Altair Engineering
To add links 1. Select the connectors from the browser for which a link needs to be added. The connectors can also be selected from the graphics area by using the selector button in the action modes tool set. The connectors selected in the graphics area will be highlighted in the browser tree. 2. Right-click onto one of the highlighted connectors in the entities column to open the context menu and select the Add Link function. An Add Link dialog opens at the bottom of the connector browser. All highlighted connectors will be affected by the subsequent add link action. Note : if the Add Link dialog is still open from a previous add link execution, all blue highlighted connectors will be affected when the add link function is performed again. 3. By default the Increment T checkbox is activated. This means the number of layers of the appropriate connectors will be raised by one for every added link. If the checkbox is deactivated the number of layers remains constant. By default the Link Type is set to component. Choose the Link Type which has to be added first. Available link entities are: component, assembly, surface , element, tag, and node . Select the link that needs to be added by clicking on the Link Select field in the Option column. After selecting the link click proceed to return to the Add Link dialog.
4. 5.
Altair Engineering

94
6.
If the specific link needs to be remembered in the connector for a future part replacement operation by Id or by Name , select the appropriate value for the Link Rule field. Similarly, the Link State value determines whether the realized FE of the connector connects mesh or geometry.
7.
Click the Add button to acknowledge and execute the operation.
95

Altair Engineering
Remove Links
The remove link option can be accessed from the Connector Entity Browser context menu by right-clicking in the Entities column or the Link column. The browser allows either one link or many link(s) to be removed from one or many connectors at a time. The updated connectors will be unrealized and the change will be permanently updated in the database and the browser.
To remove all links from connectors

1. Select the connectors from the browser for which all the links needs to be removed. The connectors can also be selected from graphics by using the Selector button in the Connector Entity Browser Action Modes tool set. The selected connectors in the graphics area will be highlighted in the browser tree. 2. 3. Open the default context menu by right-clicking in the Entities column of the tree list. Select the Remove Links option to confirm and execute the operation.
To remove specific links from connectors

1. 2. 3. Select the link that needs to be removed Right-click a link (not a connector) in the tree list to bring up the remove link context menu. Choose to remove link from selected connectors option or remove link from all connectors option to confirm and execute the operation. Note that no connector needs to be selected; even in the case of the Selected Connectors option, the browser automatically determines the affected connectors through the selected links.
Altair Engineering

96
Update Links
The Update Link operation is available in the Connector Browser tree context menu.
This operation allows the link attributes to be easily edited.
97

Altair Engineering
To update links in general 1. Select the connectors from the browser for which one or more links need to be updated. The connectors can also be selected from the graphics area by using the selector button in the action modes tool set. The connectors selected in the graphics area will be highlighted in the browser tree. 2. Right-click onto one of the highlighted connectors in the entities column to open the full context menu and select the Update Link function. An Update Link dialog opens at the bottom of the connector browser. All highlighted connectors will be affected by the subsequent update link action. Note : if the Update Link dialog is still open from a previous update link operation, all blue highlighted connectors will be affected when the update link function is performed again. Note also that the lines for Link State and Link Rule are grayed out by default in the Update Link dialog. When the extended information in the Connector Entity Browser configuration window is activated, these lines become active as well.
Altair Engineering

98
3.
Fill in the fields in the search column. Due to this selection the links of the selected (highlighted) connectors are filtered down to the links which fit to all given search attributes. Only the remaining links are taken into account for the subsequent attribute replacement. Note : not all of the search attributes have to be defined; an asterisk can be used.
4.
Fill in the fields in the replace column. All the remaining links will be updated with the attributes defined by these attributes. Note : not all of the replace attributes have to be defined; an asterisk can be used. The prior attributes are maintained.
5.
Click on the Update button to acknowledge and execute the operation. Note : not every combination of search and replace attributes are valid. For example, it is not possible to select the asterisk for the link select field in the search column and replace it with a concrete link. This helps to prevent global creation of unwanted modifications.
Update link operations are frequently used for: part replacement modifying link rules modifying link states If a part replacement needs to be performed the browser provides quick tools to update one or more connectors with the link referencing the new redesigned part. The following sections present steps to edit and update the link rule and the link state attributes as well as the part replacement.
99

Altair Engineering
Modifying Link Rules

The link rule defines how a connector treats an entity added as a link. Adding a link with the ID or name rule forces the connector to retain the links ID or name even if that link entity no longer exists in the database. Adding a link with the at fe-realize rule ensures that each time a connector is realized the closest entity of the correct type is found and connected.
To update link rules 1. 2. Mark the extended information checkbox in the Options tab of the Connector Entity Browser configuration window to activate the lines for Link State and Link Rule in the Update Link dialog. Select one or more connectors from the browser. The connectors can also be selected from graphics by using the virtual collector selector button in the Connector Browser tool set. The selected connectors in the graphics will be highlighted in the browser tree. 3. 4. 5. Right-click to open the context menu, and select update link . In the Search column's Link Rule list box, select the link rule to search and under the Replace column Link Rule list box, select the new rule. Click on the Update button and acknowledge.
Notes: The link column for the selected connectors will now display the modified information. The connectors state remains unchanged.
Example The following screenshots illustrate a link rule modification.
Altair Engineering

100
The starting link rule is underlined in red. Note that use-id is specified as the replacement link rule.
After performing the modification, the current link rule has changed for the selected links:
101

Altair Engineering
The new ly replaced link rule is underlined in blue.
Altair Engineering

102
Modifying Link States

The link state defines if the weld created during connector realization connects to geometry or mesh on the link. This is applicable to only components and surfaces entities that can contain geometry and/or mesh information. To update link states 1. 1. 2. Mark the extended information checkbox in the Options tab of the Connector Entity Browser configuration window to activate the lines for Link State and Link Rule in the Update Link dialog. Open the Configure Browser window (browser context menu) and select view extended link information. Select one or more connectors from the browser. The connectors can also be selected from graphics by using the Selector button in the Connector Entity Browser Action Mode Tools. The selected connectors in the graphics will be highlighted in the browser tree. 3. 4. 5. Right-click to open the context menu, and select update link . In the Search column's Link State list box, select the link state to search and under the Replace column Link State list box, select the new state. Click on the Update button and acknowledge.
Notes: The link column for the selected connectors will now display the modified information. The updated connectors will be unrealized and its realized welds will be permanently removed. If the link state was switched for a component link from elems to geom then realizing the connector again will result in the weld connecting to a surface (geometry) contained in that component.
Example The following screenshots illustrate a link state modification.
103

Altair Engineering
The starting link state is underlined in red. Note that use-id is specified as the replacement link state.
After performing the modification, the current link state has changed for the selected links:
Altair Engineering

104
The new ly replaced link state is underlined in blue.
105

Altair Engineering
Part Replacement
The Update Link operation available in the Connector Entity Browser Context Menu aids in performing part replacement. The functionality allows one link reference at a time to be replaced in one or more connectors. The connectors whose links were modified during this operation will be unrealized and the connector's realized elements will be permanently removed.
To update links for the purpose of part replacement (link reference) 1. Identify and select the connectors referencing to the component (link entity) to be replaced. This step is not essential, but gives you a better overview; you could also select all connectors. Using these settings in the Link Entity Browser and right clicking on the component to be replaced will isolate the component and all connectors referencing it component in the graphics.
By using the selector button in the Connector Entity Browser you can chose all connectors in a window selection in the graphics. The selected connectors appear highlighted in the browser.
Altair Engineering

106
2.
<Right-click> one of the highlighted connectors in the entities column to get access to the full context menu and select the Update Link function. An Update Link dialog opens at the bottom of the connector browser. All highlighted connectors will be affected by the subsequent update link action. Note : the lines for Link State and Link Rule are grayed out by default in the Update Link dialog. When the extended information in the Connector Entity Browser configuration window is activated, these lines become active as well.
3.
For pure part replacements, simply select the component that needs to be replaced from the component list by clicking on the Link Select field under the Search column as shown below.
107

Altair Engineering
After selecting the component click proceed to return to the Update Link dialog. Note : due to the attributes given in the Search column the links of the selected (highlighted) connectors are filtered down to the links which fit all given search attributes. Only the remaining links are taken into account for the following attribute replacement. 4. Select the component that needs to replace the previously selected one from the component list by clicking on the Link Select field in the Replace column as shown below. After selecting the component click proceed to return to the Update Link dialog.
Altair Engineering

108
5.
Click on the Update button to execute the part replacement operation.
Notes The updated connectors will be unrealized and its realized welds will be permanently removed. The connectors can be realized again without providing any inputs by using the Rerealize context menu operation. Rerealize calls the *CE_Realize command to realize connectors by accepting only a connector mark. The underlying assumption in the command is that each connector passed in the mark has the required information to be successfully realized. The required information such as tolerance, weld configuration, diameter, etc is not defined for connectors created using the FE Absorb utility; hence the Rerealize feature in the Connector Browser works only for connectors that were realized through the connector panel.
109

Altair Engineering
See also *CE Realize FE Absorb Utility connector panel
Altair Engineering

110
Find Connectors from Parts or Links

The find functionality finds and isolates connectors that connect the selected component(s)/part(s) in the Link Entity Browser. The found connectors are also highlighted in the browser tree making it easy to perform further operation. The find feature will also isolate the realized welds of a connector if the realization view options button is activated in the link browser tool set. The find connectors from components feature can be accessed through the Link Entity Browser's contextsensitive menu.
How do I find connectors from components/parts?

This process depends on the Link Entity Browser. 1. Ensure that the Linked Connector view option toggle ( ) is active. button.
If the realized welds of the connectors also need to be displayed in graphics then activate the 2. Either: or use the selector Ensure that the Show/Hide button ( entity,
) is active in Show mode, and then click the desired link
to pick the desired link entities, and then left-click the Show/Hide button.
How do I find connectors between two or more components/parts?

1. Select two or more components from the link entity table to find their connecting connectors. The component(s) can be easily located in the browser table list by using the selector button in the component table tool set. Click the button and select the components in the graphics area to highlight it in the table. If the realized welds of the connectors also need to be displayed in graphics then activate the 2. Use the Link Entity Browser Advanced Action Buttons to show or isolate the shared connectors. button.
111

Altair Engineering
Find Connectors from Realizations

1. 2. 3. 4. Select the desired link entites from the link entity browser list or the graphics area. Click the button in the utility tool set (at the bottom of the Connector Browser) to open an elements selection panel. Click proceed in the panel. The connectors that contain the selected elements as their realized welds will be highlight in the browser.
Altair Engineering

112
Find Links from Connectors

The find parts feature in the connector browser context menu finds the component(s)/part(s) connected by specific connector(s), and isolates them in the graphics area. The components found are also highlighted in the Link Entity Browser making it easy to perform further operations. The find parts feature will also isolate the realized welds of a connector if the realization toggle button is activated in the browser.
To find link entities from connectors: 1. Select one or more connectors in the Connector Entity Browser. The connectors can also be selected from the graphics area by using the selector button in the Connector Entity Browser Action Modes tool set. The connectors selected in the graphics area will be highlighted in the browser tree. If the realized welds of the connectors also need to be isolated, activate the realization button. 2. Right-click in the browser tree to open the context menu, then click find parts.
Notes: The selected connectors, the components that are connected by those connectors, and the realized welds of the selected connectors (if toggle is activated) will be isolated in the graphics area and the found components are also highlighted in the component table.
113

Altair Engineering
Entity State Browser

The Entity State Browser can be accessed by selecting Entity State Browser from the View drop down menu. It allows you to set various entity states (including active /inactive and export/do not export) for entities in the model. An example of a model in the Entity State Browser is shown below.
The active/inactive state is a controllable state whereby the display of inactive entities will be turned off from the display in the graphics, the browsers, the display panel, and any panel entity collectors. It is designed to aid users who frequently work with large models and need be able to filter the list and display, to reduce the number of available or visible entities. Inactive are still present within the model but are removed from access until they are made active again. The export/do not export state determines whether entities are exported when using the custom export option in the Export tab. Note: This state does not have any effect on the all and displayed export options.
Altair Engineering

114
Furthermore, the active/inactive and export/do not export states are independent of each other--one does not affect the other. Entities that are set inactive are still eligible for all and custom export. They are not output when using the displayed export option since they are, by definition, not eligible for display. All entities in the current model that have active and export states are shown in the browser at all times. The check-boxes in the Active and Export columns indicate the current settings for those entities and can be clicked to change the state. Each entity is individually controlled via the browser, but all collected entities contained within a collector are subsequently set to the same state as the parent collector--control is not available at the individual collected entity level. Changing the state of an assembly has two functions: first, it sets the state of that assembly directly. Secondly, it sets the state of all sub-assemblies, components and multibodies referenced by that assembly to the same state as the parent assembly. Include files do not directly contain any states that can be controlled by the Entity State Browser. Operating on an include will, instead, operate on all supported entities that are referenced by that include. The Entity State Browser context menu contains functionality unique to the Entity State Browser, but much of the basic browser functionality--such as sorting and filtering the tree list as well as the functions within the tool sets--are shared with the same features in the Model Browser: Action Mode tools Finding Entities Filtering Entities Sorting Entities
115

Altair Engineering
Entity State Browser Context Menu

A context sensitive pop-up menu provides many Entity State Browser functionalities. Right click in the browser to invoke the following pop-up menu:
Option Set Active
Available for: Permanently
Description Sets the currently selected entities in the browser to the active state. Sets the entities currently selected in each folder to the active state and sets the remaining entities in those folders to the inactive state. Sets the currently selected entities in the browser to the inactive state. Sets the entities currently selected in each folder to the inactive state and sets the remaining entities in those folders to the active state. Sets the currently selected entities in the browser to the export state. Sets the entities currently selected in each folder to the export state and sets the remaining entities in those folders to the do not export state. Sets the currently selected entities in the browser to the do not export state.
Set Active Only
Permanently
Set Inactive
Permanently
Set Inactive Only
Permanently
Set Export
Permanently
Set Export Only
Permanently
Set Do Not Export
Permanently
Altair Engineering

116
Set Do Not Export Only
Permanently
Sets the entities currently selected in each folder to the do not export state and sets the remaining entities in those folders to the export state. Closes all of the folders in the tree structure, so that only the top-most level of items displays. Opens all of the folders in the entire tree structure, exposing every item nested at every level. Turns the browser Find on/off functionality see Find section for more information Turns the browser Filter functionality on/off see Filter section for more information This allows you to hide or show the various columns in the tree control. Opens the Entity State Browsers Browser Configuration window, which allows you to determine what entities display in the tree as well as which columns the browser displays.
Collapse All
All
Expand All
All
Show Find
All
Show Filter
All
Columns
All
Configure Browser
All
117

Altair Engineering
Model Browser
The Model Browser resides on a tab in a tab area sidebar and allows you to view the model structure while providing full find, display, and editing control of entities. The model structure is viewed as a flat, listed tree structure within the browser. However, if the model has an assembly hierarchy then the Model Browser accommodates this hierarchical structure. The browser can list every named entity within the session and places those entities into their respective folders; however, it does not support non-named entities such as nodes and elements. Some of the more important entities within the model include: assemblies, components, multibodies, properties, materials, entity sets, groups, load collectors, system collectors, vector collectors, and beamsectcols -- all of which are placed into a tree-like display. To open the Model Browser, click the Model Browser item located within the View pull-down menu. The browser displays on one of the tab area sidebars.
Altair Engineering

118
This screenshot show s many of the entities that can display in the brow ser.
Multiple entities of the same type are collected into folders in the tree structure. Each folder can be expanded or collapsed to display or hide its contents. Assemblies can also have sub-folders within the main Assembly folder, so that the items related to each assembly appear within that assemblys folder in the Assembly Hierarchy. Materials, properties, entity sets, groups, load cols, system cols, vector cols, and beamsectcols cannot be organized into assemblies and are all placed at the top level of the tree, each in their corresponding folder (for example all sets are placed as a flat list in the Sets folder). Components and Assemblies may appear in multiple places in the tree; for example, a specific component might appear under Components and again as a sub-item of a specific Assembly. When appropriate, the color and display style of entities also display in the Model Browser.
119

Altair Engineering
The Model Browser tools include toolbars, a context-sensitive menu, and controls built into the display tree. Toolbars provide the ability to change model views, show or hide entities within the model, and add entities to a panel collector. These abilities are collectively referred to as display controls and browser modes. The context sensitive menu includes most of the same functions as the toolbars, as well as the ability to activate or deactivate search and sorting capability. You can find, sort, and filter entities in the Model Browser's tree list. The tree list within the browser is configurable, so that you can determine which columns and entity types that display in the tree.
Tool button groups

Many of the Model Browser functions are accessed via the View, Global Display, and Action Modes groups of buttons. In the image below; the blue call-out is the View toolbar, cyan is the Action Modes, and red is the Global Display. Rest the mouse cursor over a tool set or call-out in the image below to see the name, or click to jump to help for that tool set.
Drag and Drop

Components, multibodies, and assemblies can be dragged and dropped with the left and right mouse button. The left mouse button allows you to move the item into another assembly; the right mouse button activates a menu that allows you to remove an item from an assembly. If an assembly is moved, all the items in the assembly are moved to the new location (items that are not seen in the tree due to filters are also moved). You can drag and drop multiple items at any time using the standard <shift> and <ctrl> keys. Note : If an item is dragged out of the tree and dropped onto empty space, it is deleted in all its parent assemblies and placed at the top level of the tree. A dragged item is added to the bottom of the list in an assembly.
Altair Engineering

120
See also Model Browser Configuration window HyperMesh Environment Tab Area
121

Altair Engineering
Model Browser Views

Within the Model Browser there are four predefined browser view modes; Model View , Component View , Material View , Property View , and (when using the OptiStruct or RADIOSS user profile) Optimization View . The different view modes are accessed via the first row of icons within the Model Browser. Browser view modes provide a quick mechanism to view specific entities, and within the component, material and property view modes additional information associated with the entity displays in the tree list. The optimization view is a mode which not only controls the display, but also allows you to create optimization problem definitions. Optimization view mode is only available when the OptiStruct or RADIOSS Bulk user profile is set. Using the browser view modes in conjunction with the selector mechanism provides a powerful and easy way to find and query entities. The key traits of each view are as follows:
Model View
This is the standard view mode for the Model Browser: All entities within the session will be listed in the tree. Include full display control for all applicable entities--allowing alteration of mesh or geometry visualization, for example, or making entities visible or invisible.
Altair Engineering

122
Include View
All entities within the session will be listed in the tree. Include full display control for all applicable entities--allowing alteration of mesh or geometry visualization, for example, or making entities visible or invisible. For more details, see Model Browser Include View.
123

Altair Engineering
Component View
Turns off all other entities in the browser and lists only components in a flat list. Turns on FE and Geometry style columns Populates Indirect Property and Material columns (dependant on user profile) Includes the Direct Property column, which allows you to toggle between direct/indirect property assignment. Visualization mode is set to By Comp
Altair Engineering

124
Material View
Turns off all other entities in the browser and lists only materials Type grouping for materials is introduced: each material is placed into a folder for easy find and editing operations Type and Card Image columns are turned on Visualization mode is set to By Mat
125

Altair Engineering
Property View
Turns off all other entities in the browser and lists only properties Type grouping for properties is introduced, each property is placed into a folder for easy find and editing operations Type and Card Image columns are turned on Visualization mode is set to By Prop A new button for element visualization by direct or indirect property is added.
Altair Engineering

126
Optimization View
The optimization view is only available when the OptiStruct or RADIOSS (Bulk) user profile is set. Turns off all other entities in the browser and lists only optimization related entities Visualization mode is set to By Comp.
127

Altair Engineering
The optimization view can be used to define optimization problems and objectives. Click here for a more detailed description of the capabilities of this view.
Altair Engineering

128
Model Browser Optimization View

The optimization view of the Model Browser turns off all other entities in the browser and lists only optimization related entities. These entities include: Objectives, Objective References, Optimization Tables, Design Equations, Responses, Design Variables, Design Variable Relationships, Design Variable Links, Constraints, Loadsteps, Optimization Controls and Discrete Design Values. Note: For an image of the optimization view, see Model Browser Views.
The Optimization Browser view consists of two sections: an entity repository section and a problem definition section. The repository lists all the optimization related entities in the model, and the problem definition section allows users to define multiple optimization problems. To choose which problem will be included in the exported file one (and only one) of the problems must be set to export. A secondary function of the Optimization Browser is to provide the user with a quick over view of the optimization problem(s) they have defined.
Defining a Problem
The context sensitive menu allows users to create, delete and rename optimization problems. Once a
129

Altair Engineering
problem is created users must drag and drop optimization entities into the problem to properly define it. Users can drag one or many entities from either the repository or a previously defined problem into a problem. There are no active problems; users must drag and drop to define problems.
Context Sensitive Menu

The context sensitive menu allows users to create, edit and assign optimization entities in the same manner as the Optimization menu. All newly created optimization entities are placed in the repository and must be added to a problem to be considered. There is an option in the context sensitive menu to remove any optimization entities from a problem without deleting it from the repository. The delete option removes the entity from the database completely.
Exporting Problems
Although multiple problems can be defined with the optimization view, only one can be exported. Through the context sensitive menu, users can select which problem is set to export. The problem set to export is highlighted in bold type and gets written out to the input file. The export state can also be defined in the Entity State Browser, the export state is set by simply checking the checkbox next to the required problem in the export column. The optimization problems can be found under the Bag folder in the Entity State Browser.
Known Limitations
Only one objective and one opticontrol can be defined in one session.
Altair Engineering

130
Model Browser Include View

The Include view can be accessed by clicking the Include View button in the Model Browser. It allows you create, review, edit, organize, and update the contents of a model into various include files. An example of a model in the Include view is shown below.
The Master Model is at the top level of the Include view. Data which does not have any references to an include file, is stored in the master model. Each include file is represented with an icon along with its name and internal HyperMesh ID. Each include can be expanded to reveal its contents. The contents of each include is organized (grouped) into folders containing each type, next to which appears the total number of entities of each type. In the above example, the include named suspen.k contains 37 components, 62 sets, 25 properties, 3 groups, 10 materials and 1 card. Each of the folders can be expanded to review the individual entities in that folder. You can select entities (using the standard Shift and Control keys) and drag various entities between two includes or between the master model and an include. The browser can be configured to show only specific entities of interest. You can drag-and-drop includes within the tree to nest them within other includes. In addition, when in
131

Altair Engineering
Include view mode, the Model Browser context menu options Make Current and Move to Current become available when the menu is invoked by right-clicking on a valid include: Make Current flags the highlighted include to be the default for subsequent Include operations such as Move to Current. Move to Current organizes the highlighted include(s) to become part of the pre-designated current include. The selected includes are removed from their original location and added to the current one.
Altair Engineering

132
Direct/Indirect Property Assignment

Many solver user profiles include a column called Direct Property when in Component View . This column holds checkboxes for each component.
When checked, the component uses a direct property assignment When unchecked, the component's direct property assignment is "unassigned" and the component will use indirect property assignment, if available. The Direct Property column displays for all solver profiles except Ansys, Ls-Dyna, PamCrash2G, RADIOSS (Block), and any profile in Manufacturing Solutions. The Indirect Property column displays for all user profiles except Pamcrash2G and Samcef. The checkbox may be checked or unchecked based on the type of assignment already defined in the model, but you can change the assignment type by changing the state of the checkbox. You can check or uncheck multiple components at a time, if you have multiple components selected before changing the state of the checkbox. The exact results depend on a number of factors: If you select more than one component and uncheck the DIRECT checkbox for one of them, then all selected components should have their property relationship unassigned. If you select more than one component and check one of the DIRECT checkboxes for that selection, then if and only if the INDIRECT properties are common they will be be assigned. If there is a mixture of INDIRECT properties, the operation fails because multiple property assignments are not possible. If the component has no INDIRECT property, but does have DIRECT property assignment, and you uncheck the checkbox, then the component has NO property assignment. This means that if you then recheck the checkbox, you receive an error stating that no property is available, so automatic
133

Altair Engineering
direct property assignment is not possible. The checkbox, in this instance, will be disabled until you make an indirect/direct property assignment for the relevant components. Like most browser columns, you can sort components by the state of their Direct Property flag. See Also Direct/Indirect Property View Model Browser Views
Altair Engineering

134
Direct/Indirect Property View

When in Property View and the Model Browser gains another list button in its toolbar. The buttons within this list allow you to filter the elements that display in the graphics area based on their property assignments. Note that this feature is not supported by the user profiles for Ansys, Ls-Dyna, Marc, Pamcrash2G, RADIOSS (Block), Samcef, and any profile in Manufacturing Solutions Both direct and indirect properties Direct properties only Indirect properties only Selecting one of these options immediately filters the view in the graphics area. These filters are accumulative with the current component display state--so, for example, if you have only a few components displayed in the graphics area and the rest are hidden, selecting Direct Properties Only will filter out any elements from the currently displayed set, but will not cause previously-hidden elements to become visible again even if they have direct properties assigned. Similarly, Show , Hide , and Isolate functions work in conjunction with these controls rather than overriding them. If you switch to a different model browser view, the effects of your current direct/indirect property view remain. Selecting any of these view modes automatically hides any non-element entities, such as boundary conditions or morphing domains. Note that entities with no property assignments at all will be filtered out of the view by any of these options.
Examples
The simple model shown below (using component view ) has elements organized into four components, each representing a property state: direct only, indirect only, mixed, and no property. The mixed component consists of three elements with indirect properties and one element with direct properties, but this only becomes apparent when using one of the property views.
135

Altair Engineering
Property View: Both
Altair Engineering

136
Property View: Indirect only
137

Altair Engineering
Property View: Direct only
Altair Engineering

138
See Also Direct/Indirect Property Assignment Model Browser Views
139

Altair Engineering
Display Controls & Browser Modes

These controls affect which entities display in the graphics area, and how they display (such as shaded or wireframe). The Global Display Tools can be used to turn the display of large numbers of entities on and off. The Local Display Controls affect the visual style of individual entities (such as shaded or wireframe). The Action Mode Tools allows you to turn entities' display on and off individually, isolate certain entities so that only they appear in the graphics area, or add entities to panel collectors.
Altair Engineering

140
Global Display Tools

These controls lie at the left side of the browser, just below the View tools.
The Elements/Geometry button determines what the other buttons act on; right-click the button (or left-click the small triangular downward arrow) to reveal a drop-down menu of options. You can select Elements, Geometry, or both. The Display All , Display None , and Reverse Display buttons at the top of the tab change the display state of all assemblies, multibodies, components, groups, system cols, load cols, and vector cols shown in the tree. All displays and None hides all of the items shown in the tree. Reverse
reverses the state of all entities (displaying the hidden and hiding the displayed). Since these functions work in combination with the filters, only the items displayed in the tree are affected--hidden items that are also filtered out of the tree will not be displayed. By default, the global display controls will work on all entities listed in the browser, however, these controls can also work at the folder and individual named entity level too. As an example, highlighting the components folder and then clicking None will turn off all components. If an individual component is highlighted within the component folder the All, None and Reverse controls will only work on that specific entity. To enable the All , None, Reverse functions to work at the global level again simply clicking on the white space within the browser (de-selecting any selected entities) will enable the control back to the highest level. Note : These buttons only affect the display state. They do not actually remove entities from the model, but only show or hide them.
141

Altair Engineering
Local Display Controls

These controls are located within the tree list, and each affects the specific entity that it appears beside.
Entity Display Icons

Entities are displayed or hidden by toggling the corresponding icons (located next to each line item in the tree view). The following rules apply: A bold icon next to an entity (components, multibodies, load collector, etc.) represents that the entity is currently displayed; a dimmed icon next to an unchecked entity represents that the entity is turned off from display. Assemblies containing components or multibodies are considered displayed only when all of the contents are displayed. Activating an assemblys display control icon displays all of its contents. Activating an assemblys display control icon displays all its components and multibodies. Deactivating the display control icon check box for an assembly hides all of its components and multibodies. Deactivating the display control icon for an item hides all of its parent assemblies. Deactivating the display control icon for an item does not affect the state of its parent assembly. An empty assembly never displays.
Colors
Assemblies, BeamSection Collectors, Blocks, Components, Contact Surfaces, Curves, Groups, Load Collectors, Materials, Properties, Shapes, System Collectors, Tags, Titles and Vector Collectors can all be colored individually, the Model Browser allows you to set each entitys color without using the Color panel. The currently assigned color displays in the column.
To change an entitys color, right-click on the current color in the Model Browser. In this instance, the right-click menu contains only a single option: color. Select this to open the color picker, and click the desired color from the palette. Note : When the color picker palette appears, the mouse pointer automatically moves to its center. The palette automatically disappears when you move the mouse pointer beyond its boundaries.
Display Mode
Components have several display states, based on a combination of their elements and their geometry. You can select these display modes by right-clicking clicking the small icons in the column for each component, assembly, or load collector. Right-clicking opens a pop-up menu from which you can choose the new style. Depending on which option you select, the entity displays differently: FE Styles
Altair Engineering

142
Wireframe mesh. Shaded elements (no mesh). Shaded elements with mesh lines. Shaded elements with feature lines (no mesh) Transparent shaded elements without mesh. Geometry Styles Wireframe geometry Wireframe geometry with surface lines Shaded geometry Shaded geometry with feature lines
143

Altair Engineering
Action Mode Tools

The series of icons found on the right side of the Model Browser control both entity selection and the display of the model. The first two determine the type of entity that you wish to manipulate, while the rest perform specific actions. The specific buttons available are Entity Type , Elements/Geometry, Selector, Add to Panel Collector, Show/Hide , Isolate , and Undo.
Entity Type
The first button in the action modes tool set functions as a "mode" selector for the rest of the tools, by determining what type of entity the remaining tools will act on. For example, when set to "components", the Selector (described below) tool will only select or deselect components. Right-click the button to drop down a menu of available entity types -- all entities are available -- then leftclick the desired type to select it. Note that once an entity type is selected, left-clicking the button does not perform any additional action; the button is used strictly as a setting to determine what the other tools will affect when used.
Elements/Geometry
The second button in the action modes tool set also functions as a "mode" selector for the rest of the tools, by determining what type of contained entities the remaining tools will act on. For example, when set to "elements", the Selector (described below) tool will only select or deselect elements. Right-click the button to drop down a menu of available entity types, then left-click the desired type to select it. Note that you can choose between elements only, geometry only, or both--in which case the other tools (such as the Selector) will work on both elements and geometry. Note also that once an entity type is selected, left-clicking the button does not perform any additional action; the button is used strictly as a setting to determine what the other tools will affect when used.
Selector
The Selector is a tool to interactively select any type of supported entity via the browser, or by selecting within the graphics area. The type of entity selection is made via the entity type pull-down menu. The Selector can be used to find entities from the graphics area which will then be highlighted in the list, and is also an efficient way of selecting multiple entities at once--such as when changing color.
Altair Engineering

144
Notes:
The Visualization mode when picking materials and properties will change to by Mat and by Prop respectively.
In a Microsoft Windows environment, you can also use a scroll-wheel-equipped mouse to "drill down" through the model to select parts that may not be immediately visible. Simply left-click an entity, and hold the left mouse button down while rolling the scroll wheel--forward to move deeper into the field of view away from you, or backward to move the selection closer to you. Highlighting indicates the component that will be selected once you release the left button. Remember, however, that this only works in a Windows environment; it will not work in UNIX, LINUX, etc. Finally, the Selector can be used in conjunction with the Isolate function (see below); a selection is made from the browser or graphics area using the Selector, then click Isolate to isolate that selection. In general, the left mouse button selects entities while the right mouse button de-selects them: Picking in the graphics area Left-click to select entities. Left-click and hold to pre-highlight entities; the entity under the Selector at any given moment highlights, but is is not selected until you release the mouse button. <shift> + left-click to use window selection to highlight or select multiple entities. Right-click an entity to deselect it. <shift> + right-click to use window selection to deselect multiple entities. When using a panel with an active collector, each entity selected gets added to the collector, while each one de-selected gets removed from the collector. Selected entities' line items highlight within the browser.
Picking in the Model Browser tree list
145

Altair Engineering
Left-click to select & highlight an entity in the browser the entity is also highlighted in graphics area. <ctrl> + left-click to select multiple entities in both the browser and graphics area. Multiple entities of the same type can be appended to the selection. Left-click can be used to add/remove components from an active collector on a panel. <shift> + left-click highlights multiple entities in the browser and the graphics area. You can append and remove entities from a panel's active collector list depending on which entity entry is selected. Right-clicking highlights components in the list and invokes the context sensitive menu no highlighting of the entity in graphics area will occur with this operation.
Virtual Collector
The Virtual Collector is a function whereby the browser can be used to select and add entities to the panel collectors. This is an alternative method to using the advanced selection capabilities already available in each collector's extended entity selection menu. This button only becomes available when you have a panel open that includes at least one entity collector.
Altair Engineering

146
Note :
The selected entities are only added to the panel's active (blue halo) collector. Additionally--as should be obvious--only entities of the correct type will be added to the active collector; for example, you cannot add lines to an Elements collector.
There are two ways of using this tool: You can use the Selector to choose a set of entities beforehand, and then click the Add to Panel Collector button to add them to the panel's collector. In this method, the Selector effectively gives a preview of the selection, because the selected entities are highlighted but only added to the active panel collector when you click the Add to Panel Collector button. For example:
Alternatively, you can click the Add to Panel Collector button first to activate it, then pick the entities you wish to add to the collector. Each selection is added to the collector immediately upon each release of the mouse button. Either method can be used in the graphics area or the browser tree list. <Ctrl>-clicks and <shift>-clicks are supported in the browser list; window selections (<shift>+click-and-drag) are supported in the graphics area. To remove entities from a panel collector, you can either clear the collector by clicking its reset button ( ) or--when the Add to Panel Collector button is active--you can use the right mouse button (with full shift-, control-, or window-based selection) to remove individual entities.
Show/Hide
The Show/Hide mode enables the control of the model display via interactively selecting entities within the graphics area. This mode is only intended for graphics selection and is not designed for operation within the
147

Altair Engineering
browser (use the local entity controls found inside the browser's tree structure for browser display control). Note : When using window selection (<shift>-click-and-drag) an entity is considered selected if any portion of it falls within the window; you do not need to encompass the entire entity with the window, only a small portion of it. Also remember that only entities of the types determined by the Entity Types and Elements/Geometry buttons will be hidden or revealed. The Visualization mode when picking materials and properties will change to by Mat and by Prop respectively. However, no graphics highlighting of material or properties occurs when using the Selector. Picking in Graphics Left-click turns on entities to the display that are currently turned off. Left-click-and-drag pre-highlights only the entities that are currently turned off in the display (entities already turned on do not highlight.) Right-click turns off entities in the display. Right-click-and-drag pre-highlights only the entities that are currently turned on in the display (entities already turned off do not highlight.) Single Selection
<Shift> + left-click-and-drag uses window selection to turn on multiple entities in the display.
Altair Engineering

148
<Shift> + right-click-and-drag uses window selection to turn off multiple entities in the display Window Selection
Picking in Browser This tool does not function on line items within the browser's tree list. To control the display of the listed entities use All/None/Reverse , the individual local display control inside the tree structure, or the show/hide/isolate functions from the context sensitive menu.
Isolate
Isolate is a mechanism whereby only the selected entity will be displayed. The isolate tool isolates within the entity type; for example, if there are components and load collectors displayed, and you use Isolate while the Entity Type button is set to Component, then only that component will become isolated -- the load collectors will remain untouched in the display. In other words, all of the other components will be turned off, but the isolated component and the load collectors will still display. Note : You can use Isolate in conjunction with the Selector. In such a case, after you've selected the desired entities, clicking Isolate hides everything else except for the selected entities. However, as described above only entities of the chosen type are hidden--so connectors and similar entities
149

Altair Engineering
will still remain visible. Using the Selector may give you more precise control over which entities to retain--but for simple isolation tasks, direct usage of the Isolate button is generally quicker. Picking in Graphics In general, the left mouse button is used to isolate visible entities, while the right button is used to isolate entities that can be visible or already hidden (thus turning the hidden ones back on): Left-click will isolate the clicked entity from those on display (single-click selection). Left-click-and-drag will pre-highlight entities that are currently displayed. It will not highlight entities that are currently turned off in the display. Upon release, the pre-highlighted entity will be isolated. <Shift> + left-click-and-drag uses window selection to isolate multiple entities (but only entities currently visible). Right-click will isolate entities from all available entities (whether currently on or off in display). Right-click-and-drag will pre-highlight an entity that is displayed or turned off from the display in the graphics area. Upon release, the pre-highlighted entity will be turned on and isolated. <Shift> + right-click-and-drag uses window selection to isolate entities from all available entities (whether displayed or turned off from the display). Single and Window Selection
Altair Engineering

150
Note :
When using window selection (<shift>+click-and-drag) an entity is considered selected if any portion of it falls within the window; you do not need to encompass the entire entity with the window, only a small portion of it. Also remember that only entities of the types determined by the Entity Types and Elements/Geometry buttons will be hidden or revealed.
Picking in Browser In Isolate mode, clicking on an entity folder such as the Components folder will isolate all components, therefore turning every component on. Left-click will select/highlight an entity in the list the entity is isolated and displayed in graphics area. <Ctrl> + left-click highlights an entity name in the browser and isolates it in the graphics area. multiple entities of the same type--e.g. components--can be appended to the selection, thus displaying more than one entity but still hiding all non-selected ones. Selected/isolated entities can be de-selected by <Ctrl> + left-clicking on them a second time. <Shift> + left-click highlights all entities of the same type--e.g. components--in the browser between the first click and the most recent click, and displays the selected entities isolated from the nonselected ones in the graphics area. You can use additional <shift>-clicks or <ctrl>-clicks to modify the selection of displayed entities.
Undo
The final tool in the Action Modes tool set is the Undo button. This button undoes the last visual display change that you executed. For example, you can use undo to undo the effects of the isolate or show/hide buttons. Note : The Undo button only undoes display changes (show/hide entities). It cannot be used to undo other operations, such as deleting components, adding entities to a panel collector, or changing the viewing angle.
151

Altair Engineering
Context-Sensitive Menu
Clicking the right mouse button on a folder or entity within the browsers tree structure allows you to change a variety of options. The options available depend on the entity that you right-click on. Options selected in an empty space apply to the entire model.
Option Create
Available for: Assembly, Beamsection Collector, Component, Load Collector, Material, Multibody, Plot, Property. System Collector, Vector Collector Assembly, Beamsection Collector,
Description A new assembly, component, or multibody can be created inside an assembly (activate the menu by right-clicking an assembly). Once created, the item is automatically assigned a unique generic name that can be changed by entering the new name in the highlighted field. A new assembly, beamsection collector, component, load collector, material, multibody, plot, property, system collector, or vector collector can be created at the top level.
Edit
Opens the Edit dialog, containing the selected entities' information so that you can make any necessary changes.
Altair Engineering

152
Component, Load Collector, Material, Multibody, Plot, Property. System Collector, Vector Collector Assign Components Opens a dialog used to assign properties and materials to the selected components. Moves the selected entities to the current include, component, or load collector as appropriate. Most items can be deleted. If a component or multibody is present in more than one assembly in the model, you will be given a choice of either deleting that item from the database entirely or only removing it from the present location. If you want to entirely delete an assembly, and that assembly has children that are not present anywhere else, those children will be automatically moved to the top level. Card Edit All Any single item's card can be edited. Multiple items can be edited provided that they use identical card images. This option displays the card image of the chosen entity for the current solver template; if a template is not loaded or if the entity does not have any card images associated with the loaded template, an error message displays in the status bar. Any item can be renamed by entering a new name in the name text field and pressing <enter>, but the new name must be unique. All instances of the renamed item will be automatically updated. You can cancel the rename operation by pressing <Esc>. The high-level entity folders are non-editable, but folders containing the assembly hierarchy can be renamed. Make Current BeamSection Collector, Components, Load Collector, Multibody All The entities listed can be made current using the pop-up menu. The current collector status is indicated by the bold font. Any new components, loads, beamsections or multibodies will be created within the respective current collector. Displays the item in the graphics area. This selection affects each items local display control, i.e., will make the icon become bold indicating the display state is on. You can also use this on the entire folder. In such cases, this
Organize
Components, Materials, Properties All except the toplevel of Assemblies
Delete
Rename
All
Show
153

Altair Engineering
shows all of the items within that folder (e.g. all components etc.). Hide All Turns off the entity in the graphics area. This selection affects each items local display control, i.e., will make the icon become ghosted indicating the display state is off. You can also use this on the entire folder. In such cases, this hides all of the items within that folder (e.g. all components etc.). Isolate All Isolate works locally within a specific entity type--for example if component(s) are isolated then all display states of other displayable entities such as load collectors remain untouched. Isolate displays only the selected entities, turning their display state to on, and turning all other entities of the same type off. This works like Isolate , except that it also affects entity types different from the selected entities. This, it turns off ALL displayable entities (regardless of type) except for the selected one(s). Removes a component from within an assembly if that component has been referenced in more than one assembly. Note that this does not delete the component, but merely removes one listing of it within the Model Browser tree. Closes all of the folders in the tree structure, so that only the topmost level of items displays. Opens all of the folders in the entire tree structure, exposing every item nested at every level. Turns the Browser Find on/off functionality see Find section for more information. Turns the Browser Filter functionality on/off see Filter section for more information. Allows you to set the various options for a selected include. The available options are: The File name to be exported A Do not export flag (allows you to review the contents of an include but not export it). Includes that have this flag turned on display in the browser in italics. The File Path to export the include to (absolute path or path relative to its parent include). A flag representing the section of the input deck that the include belongs in. This flag is specific to some solvers
Isolate Only
All
Remove
Components
Collapse All
All
Expand All
All
Show Find
All
Show Filter
All
Include File Options...
(Include View only)
Altair Engineering

154
such as OptiStruct, Nastran, etc., which subdivide their data deck into various sections such as Bulk Data, Executive Control, or Case Control. For the remaining solvers this option is not available and does not display. A flag representing Include type . This flag is specific to LSDYNA, which subdivides their includes into various types such as Include, Include_Transform, and Include_Compensation_options. The Instance Option: a flag representing the instance relationship between the includes, allowing you to create a copy of your include files. This flag is specific to LSDYNA, and only applies to Include files of the "Include_Transform" type . Export an Include Export All Includes Columns (Include View only) Exports the contents of the selected include into the chosen file name. Exports all the includes with their corresponding content (not the master model - only the includes) This allows you to hide or show the Color, FE Styles, and Geometry Styles columns in the tree control. Opens the Model Browsers Browser Configuration window, which allows you to determine what entities display in the tree as well as which columns the browser displays.
(Include View only)
All
Configure Browser
All
155

Altair Engineering
Configuring the Model Browser

This window opens when you select the Configure Browser option from the Model Browsers context menu. Use this window to change the columns and entity types that display in the Model Browser.
Separate tabs organize entities and columns.
Entities Tab
To show all of the entity types that the currently loaded model possesses, choose the radio button marked select all entity types in the current model. To select entity types manually, click the Entity types: radio button, and then activate the checkboxes next to each desired entity type. A checkmark indicates that the entity type will display in the browser. You can also use the select all, select none , and select reverse buttons in this mode.
Columns tab
Altair Engineering

156
To show columns for all of the attributes that the currently loaded model possesses, choose the radio button marked Select all column types in the current model. To select columns manually, click the Column types: radio button, and then activate the checkboxes next to each desired column. A checkmark indicates that the column will display in the browser. You can also use the select all, select none , and select reverse buttons in this mode.
Options tab
To control various behaviors within the Model Browser, there are a few options available. Autocolor visualization mode Save view with mask Move to current Autoscroll on selection will automatically open the folder in the Model Browser and highlight the selected entity in the browser list and adjust the browser list so that the highlighted entity is shown automatically. This functionality is only available when an entity has been selected via the Selector functionality in the graphics area. If the Autoscroll on selection option is not activate then the folders will continue to open automatically and the entity will be highlighted in the browser list, however, the browser list will not adjust to show the selected entity. Autocolor visualization mode when active will automatically change the graphics display if a certain browser view is selected. If the Model or Component View is selected then "By Comp" visualization mode is used, if Material View is entered then the visualization mode will change to "By Mat", if in Property View then the visualization mode will change to "By Prop". If the Autocolor visualization mode is not active then the visualization modes will not change automatically when in a certain browser view and can only be changed manually via the visualization toolbar. Autofit will automatically fit the selected entities to the graphics area whether using the context menu or the Selector, Show/Hide, or Isolate functionality to control the display. Stripe background causes the browser tree to display an alternating pattern of white and gray lines in the background, making it easier to distinguish individual lines within the browser. When turned off, the browser background is flat white.
Command buttons
Once you finish configuring the browser, click one of the command buttons to close the dialog: Click OK to keep the new settings and close the window. Click Cancel to discard the changes (keeping the original settings) and close the window.
See also Model Browser
157

Altair Engineering
Loadsteps Browser
The Loadsteps Browser is used to create, manage and display loadsteps (sub-cases) and the associated control cards. The information is arranged into a tree structure for ease of use, with controls for altering the display of the information and/or exporting it. A right-click menu accesses editing and advanced options, while popup forms allow you to quickly enter or select relevant information. The Loadsteps Browser displays in its own tab in the tab area, but may not be active by default. Select it from the Tools menu to display its tab in the tab area.
Toolbar buttons
The browser includes its own toolbar, used primarily to determine which loadsteps to export but also to sync the display between the browser and the graphics area. Each control has its own function: Select all, select none, reverse selection Use these to select the items in the tree and mark them for export. You can also select individual items by clicking on them, or select multiple items by shift-clicking or control-clicking. When a loadstep is selected, the export icon next to its name is clear; when de-selected, the icon has a red "x" to indicate that it will not be exported. Note: Export state is independent of visibility in the graphics area. Only one loadstep can display in the graphics area at a time, but any number of loadsteps can be exported.
Sync browser
For large models, keeping the browser in sync with other actions taken can require considerable processing time. To alleviate this, the Loadsteps Browser does not automatically sync itself with the database. Instead, the Sync button becomes active whenever you make changes to the current database. This allows you to perform many operations without performance issues, and then sync the browser with one click. Filter buttons allow for additional selection control, including a name filter that uses standard filtering syntax. Use this feature to limit the tree to display only loadsteps whose names match a specific text string either partly or completely.
Filter
The main functionality of the Loadsteps Browser varies depending on the active user profile. For help specific to each profile, refer to the topics below: Loadsteps Browser: OptiStruct & Nastran profiles Other profiles will be added in future versions of HyperMesh.
See also HyperMesh Environment
Altair Engineering

158
Tab Area
159

Altair Engineering
Loadsteps Browser: OptiStruct & Nastran Profiles

The browsers tree structure lists relevant control cards and loadstep information, organized into folders. There are many functions available, accessed by right-clicking on the tree background or on individual or multiple items. For the OptiStruct and Nastran profiles, these options include:
New loadstep
Create a new loadstep, either from scratch or by creating an exact copy of an existing loadstep. Depending on the entity selected, this will bring up an appropriate GUI for editing of the loadstep or control card information. Review the selected entity in the HM card editor. Delete the selected entity or entities. Rename the selected entity. Renumber the selected entity. Generates a summary table of the selected loadsteps. This launches the BCs Contour utility and automatically selects the loadcols associated with the selected loadstep. This launches the Loads Summary utility and automatically selects the loadcols associated with the selected loadstep. Collapses all selected folders and subfolders, or all folders if none are selected. Expands all selected folders and subfolders, or all folders if none are selected. This option is for users who wish to have existing DLOAD, LOAD, MLOAD, MOTION, MPCADD and SPCADD cards auto-managed. This option creates a copy of loadcols with these card images and converts them into an auto-managed naming convention for easy editing/reviewing inside the Edit options popup. Opens the OptiStruct panel in HyperMesh.
Edit options
Edit card Delete Rename Renumber Summary table BCs Contour
Loads Summary
Collapse all/selection
Expand all/selection
Auto-manage load references
OptiStruct
In addition, every loadstep listed in the tree has a small checkbox next to it as well as an export state indicator. You can click these to toggle them back and forth:
Altair Engineering

160
The loadcols in the loadstep display in the HyperMesh graphics area. The loadcols in the loadstep do not display in the HyperMesh graphics area. This loadstep will not be exported. This loadstep will be exported. Note: When you first open the Loadsteps Browser, all of the loadsteps in the model default to the blank (unchecked) state.
161

Altair Engineering
To Create a New Loadstep

1. Right-click anywhere in the Loadsteps Browser and select New loadstep. A pop-up window opens, allowing you to: Type in a loadstep name Select the same as option, if desired, then pick an existing loadstep to base the new one on. When this option is active, the new loadstep is an exact copy of the existing one. 2. Click create. Another pop-up window opens, allowing you to edit the loadstep.
Altair Engineering

162
To Edit a Loadstep
1. Right-click on the desired loadstep folder, or any subfolder in the Loadsteps Browser, and select Edit options. Note: This step is skipped when you create a new loadstep! A popup window opens, allowing you to edit the loadstep. The popup has several tabs to gather the relevant information. 2. To activate an option, check the box next to the desired option and fill in the required fields. Depending on the Loadstep Type, the list of appropriate Load References will change accordingly. A tree structure lists the load references that are available for the selected loadstep type. A bold reference signifies that the load reference is defined. A red indicator signifies that a load reference is mandatory for the loadstep type and requires attention. A green indicator signifies that a load reference is mandatory for the loadstep type and is defined. 3. The table on the left lists the loadcols that are valid for a particular load reference, depending on the card image or types of loads contained within. Depending on the load reference selected in the tree, the list will change accordingly. You can sort the loadcols by clicking on the column heading that you wish to sort by (repeated clicks alternate between ascending and descending order). Note, however, that you cannot sort based on the display column. Name, ID, Type, and Color filtering is available by using standard filtering syntax (color filtering is based on the HyperMesh color ID number). 4. The table on the right lists the loadcols currently selected for that load reference. To add a loadcol to the load reference, select the loadcol in the left table and use the right arrow to add the loadcol to the table on the right. If a loadcol is assigned and that loadcol is not appropriate for that particular load reference, a warning message appears to notify you. If a loadcol is assigned and that loadcol does not exist in the database, a warning message appears to notify you. When importing a model, it is possible that the loadstep may reference loadcols that have not been imported (they are in a separate include file). In order to support this, the Add <unavailable> load reference ID option is available. This allows users to modify a loadstep and add in references to loadcols that do not exist in the current model. These references are also listed in the right table with a warning message to notify you that the loadcol doesnt exist in the database 5. 6. 7. To remove a loadcol from the load reference, select the loadcol in the right table and use the left arrow to remove the loadcol. To select multiple loadcols, use the all/none/reverse buttons where appropriate. These buttons select loadcols from the currently active table. Right-click options allow for additional functionality depending on the current selection.
163

Altair Engineering
The Add <unavailable> load reference ID option allows you to add a reference to a loadcol ID that does not currently exist in the database (as described in step 5). 8. Click Accept to apply your changes and close the editing window. Alternatively, click cancel to close the window, discarding your changes. Comments You can also edit multiple loadsteps simultaneously by selecting more than one loadstep in the browser (such as by shift-clicking) before you choose edit options from the right-click menu. For each of the options, if the option values are the same for all selected loadsteps, that option is checked "on" and shown with the appropriate values. If the option values are not the same for all selected loadsteps, that option is checked "off" and shown with the default values. If the loadstep type is not the same for all selected loadstep, it shows a blank value on the "Loadstep Type" tab. If the loadstep type is not the same, the "Load References" tab will only display the load reference types that are in common between all of the loadstep types for the selected loadsteps. Any edits you make will be applied equally to all of the selected loadsteps. Any values that are checked "off" will not be modified, but options checked "on" will all be set to the same values.
Altair Engineering

164
To Display a Loadstep
1. 2. Check/uncheck the display checkbox next to the loadstep of interest. Additional control is also available at both the Global Options and Loadstep Load References level:
3. Click the display checkboxes for each desired loadstep to check (display) or clear (hide) it. All of the loads contained in a loadcol display regardless of their relevance to the load reference they are assigned to. It is up to you to organize their loads for proper display. Global load references are not checked on/off by selecting or deselecting a loadstep. You must determine the appropriate loadcols to check on/off depending on the loadstep type. Note: You can also launch the "BCs Contour" and "Loads Summary" utilities from the Loadsteps Browser. The selected utility launches with the loadcols associated with the selected loadstep automatically selected.
165

Altair Engineering
To Rename, Renumber, Delete, or Edit the Card of a Loadstep

1. 2. 3. Right click on the appropriate loadstep or loadcol. Select the desired option from the popup menu. For renaming and renumbering, an entry box appears so that you can enter the appropriate information in the browser.
Altair Engineering

166
To Edit the Global Options of a Loadstep

Editing Global Options works exactly like editing a loadstep, except that the first step is to right-click on the Global Options folder or any of its sub-folders, instead of clicking on a specific loadsteps folder or sub-folder.
167

Altair Engineering
Loadsteps: Auto-manage Load References

This option is recommended for all users. There has traditionally only been one way to create DLOAD, LOAD, MLOAD, MOTION, MPCADD and SPCADD loadcols: by creating a loadcol, assigning the appropriate card image, and selecting the appropriate loadcols. However, many users do not want to be responsible for managing these load collectors, nor are they always aware of their existence. To satisfy both types of users, the Auto-manage load references option is available. This option does the following:
1.
Looks at each loadstep and at each load reference. If the load reference points to a loadcol with one of the card images indicated above, it will: Create a copy of that loadcol and assign it a new name, based on a fixed naming convention (auto<CARD IMAGE NAME>_#). For example, if a load reference pointed to an SPCADD loadcol, a new copy would be created and named "autoSPCADD_1". Assign that new loadcol to the original load reference. (The original loadcol is not deleted or modified in any way.)
2.
Inside the Edit options popup, if a load reference points to a loadcol with one of the card images above and that loadcol has not been converted to the auto-managed naming convention, the loadcol will not be expanded or editable inside the GUI. The only way to modify the loadcol is via the card editor (right-click option from the editor GUI). Inside the Edit options popup, if a load reference points to a loadcol with one of the card images above and that loadcol has been converted to the auto-managed naming convention, the loadcol is expanded and editable inside the GUI.
If the loadcol selected for the load reference already has the card image assigned (for users wishing to manually manage their loadcols and point to an existing loadcol with one of the card images listed above) no additional action takes place. However, when appropriate, a loadcol is automatically created and assigned the correct card image when any of these conditions are met: More than one loadcol is selected for the load reference One loadcol is selected and the local scale factor is not 1.0 (DLOAD and LOAD) The global scale factor is not 1.0 (DLOAD and LOAD)
Altair Engineering

168
Mask Browser
The Mask Browser can be accessed by selecting Mask Browser from the View menu. It allows you to set the mask/unmask state for entities at the entity configuration level. The Mask Browser is shown below.
The entities are logically organized in the browser to represent the collectors they belong to. Regardless of the current model, the entities listed in the browser remain the same. The Show/Hide/Isolate columns contain icons that can be clicked to perform the relevant masking operations. The buttons perform the masking operations at the selected entity and folder level, and for all entities and sub-folders that may be contained within that folder. These operations are only valid for entities contained in collectors that are currently displayed. The Show column corresponds to the unmask operation. It unmasks the relevant entities for the current row and sub-folders. For example, the Show icon at the Geometry folder unmasks all points, lines, surfaces and solids within any displayed components.
169

Altair Engineering
The Hide column corresponds to the mask operation. It masks the relevant entities for the current row and sub-folders. For example, the Hide icon at the 1D folder masks all rod, bar2, bar3, weld, joint and plot elements within any displayed components. The Isolate column corresponds to both a mask and an unmask operation. It performs a Hide on the top level folder and then a Show on the current row and sub-folders. For example, the Isolate icon at the 3D folder masks all connectors, geometry, 0D/rigid elements, spring/gap elements, 1D elements and 2D elements and unmasks all 3D elements within any displayed components. The exception to this rule is when the Isolate button is selected at a top-level folder; in this case, all sub-folders underneath the top-level folder are unmasked and all other top-level folders (and their contents) are masked. For example, the Isolate icon at the Components folder masks all supported entities in any displayed groups, load collectors, morphing, multibodies and system collectors--and unmasks all supported entities within any displayed components. The Mask Browser Context Menu contains functionality unique to the Mask Browser.
Altair Engineering

170
Mask Browser Context Menu

A context sensitive pop-up menu provides several Mask Browser functions. Right-click in the browser to invoke the following pop-up menu:
Option Collapse All
Available for: All
Description Closes all of the folders in the tree structure, so that only the top-most level of items displays. Opens all of the folders in the entire tree structure, exposing every item nested at every level. Determines whether the masking operations for morph entities apply to all/displayed elements.
Expand All
All
Morph operates on all elements / Morph operates on displayed elements
All
171

Altair Engineering
Set Browser
Location: Tools menu (to access the Set Browser) Tab Area (to use the Set Browser)
Use the Set Browser tool to automate the grouping and display of model components through the entity set functionality. The Set Browser consists of a tree structure listing the current entity sets in the model, along with the entity set display and export states. It also includes functions for displaying, creating, deleting, renaming, appending entities to, and changing the export state of entity sets.
Synching the Set Browser with the graphics display

The Set Browser is meant to allow users to easily control the display and review of entity sets for model grouping and visualization purposes. For large models, constantly synchronizing the display state of entity sets with the current display can introduce performance issues. To remedy these occurrences, the Set Browser utility does not automatically synchronize the display states of entity sets with the current display. Instead, the Display button at the bottom of the Set Browser updates the display to match the Set Browser settings, while the Synch button in the Set Browser toolbar allows you to update the Set Browser to match the current state of the display. When the Display button is used to update the display to the current Set Browser selection, the Set Browser and the display remain synchronized until another selection is made within the Set Browser.
Altair Engineering

172
To Set Display Options for the Set Browser

1. Open the Set Browser. The Set Browser displays in the tab area. 2. Use the toolbar buttons in the Set Browser tab to manipulate the display options, as desired:
Use <ctrl>-click and <shift>-click to select multiple items in the tree structure. For large numbers of selections, use the select all/none/reverse buttons. The entity type options allow you to control the entities (elements or geometry) that the selection buttons apply to. These buttons are toggles; you can have one or both active at the same time. In the screenshot above, the Element button is active but the geometry one is not. The sync button synchronizes the entity set display states with the current display. This means that if you have changed the display states of various entities, for example from within the Model Browser, you can use this button to force the selection of entities in the set browser to match the current display states. The name filter uses standard filtering syntax in the text box; click the funnel icon to activate the text box, type in the string you wish to filter by, and then press <enter>. This can limit the entities which display in the tree structure. To undo the filter, click the funnel icon again to disable the text box.
173

Altair Engineering
To Use the Set Browser's Right-click Functionality

1. Open the Set Browser. The Set Browser displays in the tab area. Its tree structure lists all entity set currently existing in the model, grouped in folders by type. 2. Right-click anywhere within the tree structure to open the right-click menu:
There are many functions available, accessed by right clicking in the background, on folders, or on individual or multiple items within folders. Most options require that you click on a folder or one or more items, and are grayed out of no selection is made; exceptions are specifically noted below. The graphic above shows the available options, including: Create: Create a new entity set of the specified type. You are prompted to type in a name for the set or accept a default name. Supported entity set types are shown above. This option does not require any existing sets to be selected. Edit: Edit the element set, by picking a different group of elements to assign to it. Delete: Deletes the currently selected set(s). Multiple sets may be selected by using standard Ctrl/ Shift-click functionality.
Altair Engineering

174
Card edit: Edit the property card assigned the set (but not the entities within it). Rename: Rename the selected set. Delete Reference: Removes a set reference from a entity set type of sets. Add Entities to Set: Adds entities into the currently selected set. This operation brings up an entity selector to select entities to add to the set. Remove Entities from Set: Removes entities from the currently selected set. This operation brings up an entity selector to select entities to remove from the set. Show: This operation adds the entities contained in the selected set(s) to the display. Hide: This operation removes the entities contained in the selected set(s) from the display. Isolate: This operation turns off (masks) the display of all entities not currently selected, so that only the selected entities display. Collapse All: Collapses all branches (folders) of the tree. This option does not require any selection. Expand All: Expands all branches (folders) of the tree. This option does not require any selection. Display Options: Determines how the sets are labeled in the Set Browser tree. Available options are shown above. This option does not require any selection. Display IDs: Displays a popup window showing the IDs of all entities contained in the selected set. Export Session File: Saves a session file (.ses), containing group definitions for the selected node or element sets, to the disk. Import Session File: Loads a session file (.ses) containing group definitions. These group definitions will be converted into entity sets. This option does not require any selection.
175

Altair Engineering
To Change the Set Browser's Display and Export States

1. Open the Set Browser. The Set Browser displays in the tab area. Its tree structure lists all entity set currently existing in the model, grouped in folders by type . 2. The display states of entity sets are controlled by clicking the checkboxes located next to each set on or off. Once the display checkboxes are changed, click the Display button at the bottom of the browser to update the display with the current selection. The checked state signifies that all entities in the entity set are currently displayed, after clicking the Display button. The blank state signifies that one or more of the entities in that entity set are not displayed, after clicking either the Display button.
Altair Engineering

176
Solver Browser
The Solver Browser provides a solver perspective view of the model structure in flat, listed tree structure. Hierarchical structures are only available for card images that allow variations with themselves. For example, a MAT card image has several different material types and each material has its own entity defined in HyperMesh, so a hierarchical structure is used to list them all. The Solver Browser lists every entity mapped to a solver card image within the session and places those entities into their respective solver card image folders. The total number of entities is displayed in parenthesis next to the entity name. Expand the folder to see its contents. The Solver Browser include toolbars, a context-sensitive menu, and controls built into the display tree. Toolbars provide the ability to show or hide entities (component, material and property) within the model, and add entities to a panel collector. These abilities are collectively referred to as display controls and browser modes. Context-sensitive menu provide basic functions such as card editing, creation, deletion, display control, and review.
177

Altair Engineering

A context-sensitive menu of action is available for any selected item in the Solver Browser tree. To view the context menu, right-click on either an entity folder, or an individual entity. Note: Some of these options will vary depending on which user profile you have loaded. Create provides an extended menu that gives you the option of quickly creating a new solver card / entity directly from the browser. Once you select an option, the panels necessary to create the entity or card are opened. Delete allows you to delete a selected item from the session. If the selected item has "children" associated to it, the children are retained and only the entity is deleted. For example, if a contact has a surface and node set associated with it, and the contact is deleted, only the contact card image is deleted. The surface and node set associated with it is retained. This is the same at both folder and individual entity level. Card Edit opens the Card Image panel for the selected card. It works on both folder and individual entity levels. Review works on all the individual entities listed in the Solver Browser, but not at the folder level. Review highlights the selected item on the graphics screen and greys out all other items. In case of card images like contacts, boundary conditions, etc, that do not have entities of its own but refers to another entity (namely sets), it highlights the entities that constitute the set. The graphics screen remains in that review mode until Reset Review is applied. Reset Review resets the screen from review mode to normal mode. Show displays the selected item on the graphics screen if it is currently hidden. In case of card images like contacts, boundary conditions, etc, that do not have entities of their own but refers to another entity, namely sets, it displays the components whose entities (node, element) are used in the set that is referred in the selected card image. Also, it displays any handles as geometric representation associated with entities. The implementation was done with focus on the components for easy navigation through the model. Hide turns off the selected item on the graphics screen if it is currently visible. In case of card images like contacts, boundary conditions, etc, that do not have entities of its own but refers to another entity, namely sets, it turns off the components whose entities (node, element) are used in the set that is referred in the selected card image. Also, it turns off any handles, geometric representation associated with entities. The implementation was done with focus on the components for easy navigation through the model. Isolate works like Isolate Only in the Model Browser and on all the entities listed in the Solver Browser. It isolates the selected item on the graphics screen and turns off all other items from the graphics screen. In case of card images like contacts, boundary conditions, etc, that do not have entities of its own but refers to another entity, namely sets, it isolates the components whose entities (node, element) are used in the set that is referred in the selected card image. Also, it shows any handles, geometric representation associated with selected solver entity. The implementation was done with focus on the components for easy navigation through the model. Collapse All closes all of the folders in the tree structure, so that only the top-most level of items displays. Expand All opens all of the folders in the entire tree structure, exposing every item nested at every level.
Altair Engineering

178
Show Find turns the Find functionality on/off. Show Filter turns the Filter functionality on/off. Columns allows you to hide or show the Color and FE Style columns in the tree control. Configure Browser opens the Browser Configuration dialog, which allows you to determine which entities display in the tree as well as which columns the browser displays.
Solver Browser for Crash user profiles

In addition to the options listed above, the Solver Browser toolbar for the LS-DYNA, RADIOSS (Block Format) and PAM-CRASH 2G interfaces includes an additional function: Find attached is implemented only for the card images mapped to component collectors, namely PART cards and 1D elements that include beams, mass elements, truss, rigid and joints. Find attached displays elements (0D, 1D) and components that are connected to the selected entity through sharing a common node, connectors, and special connection cards like *CONSTRAINED_EXTRA_NODE, *CONSTRAINED_RIGID_BODY.
179

Altair Engineering
See also Browsers HyperMesh Entities and Solver Support Interfacing with External Products
Altair Engineering

180
Utility Menus
The Utility Menu allows you to customize the standard interface to include function buttons, radio options, and text that have HyperMesh-supplied and user-defined macros associated with them. The menu is located on a tab of the tab area pane(s), and can be shown or hidden from within the view pull-down menu. The Utility Menu includes several pages of its own, each dedicated to different tasks. Thus it is actually a group of menus, although only one displays at a time. Each page is associated with a button at the bottom of the Utility Menu; clicking one of these buttons opens the page associated with it. Only one button can be depressed at a time, similar to the way that only one radio button can be active at a time - selecting a button de-selects all of the other buttons in the group. A macro file (hm.mac) controls the display and available operations of the Utility Menu. Attributes that you can change include: The Utility Menu page on which the operations appear Text to be displayed on each control Location and size of the menu The help string to be displayed on the menu bar The macro to call when each control is used, with optional arguments to pass The page number allows you to create multiple pages, so that you can group the macros by type of operation. Macros may contain any valid command file command, and are enclosed by the *beginmacro() and *endmacro() commands. Macros may accept variable arguments, passed to them from a control, by using the arguments $1, $2, etc. to specify where the arguments should be substituted. The *callmacro () command allows you to call a macro from within another one, which allows you to create groups of standard reusable macros. When HyperMesh starts, it looks for a macro file named hm.mac in the current directory, HOME directory (UNIX only), or the applications base directory. If it finds this macro, HyperMesh runs it automatically to define the attributes and contents of the Utility Menu. You may also select and run a macro file after HyperMesh starts from within the options panel. The default hm.mac file sources the following additional macro files: disppage.mac geommeshpage.mac globalpage.mac qamodelpage.mac userpage.mac Populates the Display page of the Utility Menu. Populates the Geom/Mesh page of the Utility Menu. Creates the button group that allows you to switch pages. Populates the QA/Model page of the Utility Menu. Populates the User page of the Utility Menu.
A userpage.mac file may exist in the installation directory for HyperMesh or in the directory from which HyperMesh launches. When HyperMesh starts, it first looks for the userpage.mac file in the directory from
181

Altair Engineering
which it launches and then in the installation directory. UNIX users also have the option of putting the userpage.mac file in their home directory. This file defines the attributes and contents of the User page of the Utility Menu. By default, the Utility Menu displays when HyperMesh starts, but display of the menu is controlled by a command in the HyperMesh Configuration. Note : While macros offer a great deal of flexibility, you must remember that once a macro is executed, there is no way to cancel the execution or reject the results, and a macro may not be called recursively.
Altair Engineering

182
Default Utility Menu

The Utility Menu is normally located on the left side of the graphics region, in the tab area pane. However, it can also be dragged-and-dropped to the right-side explorer pane, if that pane is open. It contains page selection buttons at the bottom of the menu, with the current pages button depressed. The different pages of the Utility Menu are: Geom/Mesh (macros related to model geometry and FE mesh) Disp (Options related to the graphical display of entities) QA/Model (macros related to element quality and loads) User (user-created macros only) The Utility Menu displays by default, although it may be obscured by another tab such as the Model Browser or Connector Browser. You can turn the Utility Menu off completely (removing its tab from the tab area) by un-checking it in the View menu. You can also turn the Utility Menu off by clicking the small "x" in the upper corner of the tab area when the Utility Menu tab is in the forefront, or even by clicking-anddragging the tab to the title bar. To restore the Utility Menu, simply check it in the View menu. Note, however, that it still might not display if the tab area pane on which it resides is not active. For example, if the Utility Menu is on the right-hand tab area pane, but you have only the left-hand pane showing in the HyperMesh environment, the Utility Menu will still be invisible even though you have it checked in the View menu. The Geom/Mesh, QA/Model, and Disp pages contain a variety of macros that allow you to quickly perform functions which would normally take several steps.
183

Altair Engineering
QA/Model Utility Menu

The QA Utility Menu contains many tools to help you quickly review and clean up the quality of a preexisting mesh. The element quality criteria used by these tools comes directly from the values entered on the Check Elements panel. Since the criteria on that panel are customizable, the quality criteria used by these macros remains consistent with those used throughout the rest of HyperMesh and can be indirectly adjusted by changing the settings on the Check Elements panel. There are eight tools to isolate elements that fail certain element check criteria Length This macro checks all the displayed elements against the minimum length criteria. If any elements fail the criteria, it displays the failed elements and masks the remaining elements. If none of the displayed elements fail the criteria, it displays a message and leaves the model display unchanged This macro checks all the displayed elements against the maximum Jacobian value. If any elements fail the criteria, it displays the failed elements and masks the remaining elements. If none of the displayed elements fail the criteria, it displays a message and leaves the display unchanged This macro checks all the displayed elements for their warpage. If any elements fail the warpage test, it displays the failed elements and masks the remaining elements. If none of the displayed elements fail the criteria, it displays a message and leaves the display unchanged This macro checks all the displayed elements for their aspect ratio. If any elements fail the criteria, it displays the failed elements and masks the remaining elements. If none of the displayed elements fail the criteria, it displays a message and leaves the display unchanged This macro checks all the displayed quad elements against the maximum internal angle. If any elements fail the criteria, it displays the failed elements and masks the remaining elements. If none of the displayed elements fail the criteria, it displays a message and leaves the display unchanged This macro checks all the displayed tria elements against the maximum internal angle. If any elements fail the criteria, it displays the failed elements and masks the remaining elements. If none of the displayed elements fail the criteria, it displays a message and leaves the display unchanged This macro checks all the displayed quad elements against the minimum internal angle. If any elements fail the criteria, it displays the failed elements and masks the remaining elements. If none of the displayed elements fail the criteria, it displays a message and leaves the display unchanged
Jacob (Jacobian)
Warp (warpage)
Aspect (aspect ratio)
Max ang: Q (quad)
Max ang: T (tria)
Min ang: Q (quad)
Altair Engineering

184
Min ang: T (tria)
This macro checks all the displayed tria elements against the minimum internal angle. If any elements fail the criteria, it displays the failed elements and masks the remaining elements. If none of the displayed elements fail the criteria, it displays a message and leaves the display unchanged
You can use the following macros to quickly modify any elements that fail the element checks. Split Warped Checks all displayed quad elements for warp exceeding the acceptable value. Each element failing this criterion is then split along its diagonal to form two tria elements instead of the original quad. Finds all of the elements attached to the displayed elements. Allows you to remesh the selected elements plus one, two, or three attached layers of elements (one button for each). The remesh uses the current size, does not break connectivity, and uses the mixed element type. Allows you to apply the smoothing algorithm to the selected elements plus one, two, or three attached layers of elements (one button for each). Brings up a user interface that allows you to set the various quality values and check the quality of all the 2D elements in the model. The results are shown as the number of elements and percentage of elements failing each criterion. You can also export the results to a text file using save as. Note : Changing the criteria on this report interface does not change the settings in the Check Elements panel. They only affect the report.
Find Attached Remesh
Smooth
Quality Report
Model Tour
Allows you to review (tour) the selected components individually. This macro displays the component name, number of elements in that component and their ID range. It also displays a dialog that allows you to review the free edges of the component and any elements attached to the component. Reads a generic Bill Of Materials file and provides an interface to manipulate data in the BOM as well as the corresponding FE model.
BOM Comparison Tool
The model tools included on this page are: Load Size These numbered buttons represent different display sizes for load indicators: 0 is the smallest, while 3 is the largest. Since these buttons affect all loads, including forces, pressures, constraints, and so on, the numbers do not directly correspond to any specific values or ratios. Note that this only affects the graphical display of load indicators it does not change the load magnitudes.
185

Altair Engineering
Find Elems>>Loads
Automatically finds all elements directly attached to any and all load indicators. If masked, these elements are un-masked. Automatically finds all components directly attached to any and all load indicators. If masked, these comps are un-masked. Automatically finds all loads directly attached to a selected component. If masked, these loads are un-masked. Automatically finds all elements directly attached to any and all connectors. If masked, these elements are un-masked.
Find Comps>>Loads
Find Loads>>Comps
Find Elems>>Connectors
Altair Engineering

186
BOM Comparison Tool

The BOM Comparison Tool located on the QA/Model Utility Menu reads a generic Bill of Materials (BOM) file and provides an interface to manipulate data in the BOM and its corresponding FE model. A BOM is often used as the master document for model meshing, assembly, property assignments, model comparison, and updates between design iterations as well as other CAE activities. Since users in different design and analysis groups use BOM information, the formats and content of the BOM can vary. One BOM may contain more data than another BOM for the same program. BOMs usually use Microsoft Excel format (CSV format) or XML format. The HyperMesh BOM Comparison Tool focuses primarily on the Excel format. The BOM reader includes the following abilities: Reads a generic BOM file of CSV format (comma separated values file) Provides a GUI to manipulate data in the BOM and the corresponding FE model Provides an option to update attributes in the FE model based on the data available in the BOM Provides an option to complete the existing BOM based on the data available from the model Filters out all vague information present in the BOM and provides a feature to edit the vague information into a valid data and move it back to the BOM Provides a functionality to export a new BOM file. For an in-depth description of the parts that make up the BOM Comparison Tool user interface and how to use them, see the following topics: BOM Comparison Tool Graphical User Interface (GUI) BOM Comparison Tool Control Section BOM Comparison Tool Tree Section BOM Comparison Tool Master Column BOM Comparison Tool BOM Display Section BOM Comparison Tool Metadata Display Section BOM Comparison Tool Failed Records section Note : The BOM Comparison Tool only applies to the Nastran, LS-DYNA, RADIOSS (Block Format), and Abaqus user profiles.
187

Altair Engineering
BOM Comparison Tool GUI

The BOM Comparison Tools GUI consists of seven sections as shown below:
Control section:
Contains menu items and buttons to perform various operations. This section controls most tool functions. Contains a tree structure displaying part names and IDs. Contains master column selection. This section contains a table to display BOM info as it is seen in the actual BOM file. Contains options for metadata management. Displays failed records from a loaded BOM file. Contains filtering options for displaying tree and table info; part of the tree section.
Tree section: Master column: BOM display section:
Metadata display section: Failed records section: Display filter section:
Altair Engineering

188
189

Altair Engineering
BOM Comparison Tool Control Section

This portion of the interface contains drop-down menus and the toolbar. File menu New Open Create a new session Browse for and load a new BOM file. HyperMesh checks for the standard headers Part Name , Part ID, Material, Material ID, and Gauge . If all are found, details populate the relevant fields in the BOM comparison tool. If any are missing, you will be prompted select the heading from the BOM file that corresponds to each standard header. Show Failed Display all the invalid records that the tool encounters while reading a BOM file in a table. Only valid records from a BOM file display in the BOM Display Sections table. Invalid records can be edited to form valid data and can be moved to the BOM Display table. Save and export the current information shown in the BOM Display section as a new BOM csv file in a user selected location. Close the BOM Comparison Tool. Update the model attributes to match the BOM. Sometimes the BOM doesnt contain all of the data you want. If the corresponding model contains the missing data, you can complete the BOM data by querying the database and extracting the data. Use the Complete BOM operation to either complete an existing BOM, or generate a new BOM by querying the model in current session. This option opens a new window listing the items to be added to the BOM file. You can select additional items from a combo box, or type a new header into it and add them, or click an item already in the list and insert the new item just above it. You may also select items in the list and delete them from the file. Once you had added or deleted all necessary entries, click Continue to generate the new file. Check Model Checks the model against the BOM. This option switches the BOM Display Section to Comparison mode if it is currently in BOM View mode (see below).
Save and Export
Exit Edit menu Update Model Complete BOM
Altair Engineering

190
View menu
BOM View
Display section displays BOM info as it appears in the BOM file. Categorizes BOM information into four sections: Match: components in BOM whose standard attributes match exactly with those in the model. Different: components in BOM whose standard attributes differ from those in the model. In_BOM_Only: components found in BOM but not in model. In_Model_Only: components found in model but not in BOM. Same function as File > Open.
Compare View
Same function as File >Save and Export.
Same function as Edit > Update Model.
Same function as Edit > Complete BOM.
Same function as Edit > Check Model.
Same function as File > Show Failed.
191

Altair Engineering
BOM Comparison Tool Tree Section

When a BOM file is loaded into the tool, the tool identifies the part name and part id of all valid records. It then displays the part names, appended with part IDs, in brackets in the form of a tree structure located on the left side of the tool window. Each tree branch is associated with a row in the BOM display table containing all standard information for the part in the tree branch. This section also includes selection and filtering controls, to affect which parts display in the tree and which parts are selected or deselected. Filter options are given for displaying only the desired part info in the tree and the associated data in the BOM display table.
You can enter a string in the combo box, select the desired header in the options menu, and press the <return> key to display the desired information in the tree and BOM display table. The combo box remembers previously entered strings until you quit the tool, and can be used to filter the BOM info anytime in the session. Apart from this there are filter buttons each one of which is explained below: Displays all the branches in the tree and the associated data in the BOM display table Switch off all the branches in the tree and delete all the data in the BOM display table Switch on all the "off" branches in the tree and vice versa. Data associated with switched-on branches displays in the BOM display table Switch on only those branches in the tree (and associated data in the BOM display table) that correspond to the displayed parts in the model
(Select All)
(Select None)
(Reverse selection)
(Show displayed)
Altair Engineering

192
193

Altair Engineering
BOM Comparison Tool Master Column

The central top portion of the tool window contains the master column section. This section allows you to select the desired master column option. The master column is the column in the BOM file whose attributes are considered as a key in comparison and validation operations. Only columns with three attributes can be used as master columns, i.e. columns containing part ID, part name and part number. The master column data is used as a key for the following operations: Update model attributes as in BOM Complete BOM by querying model Check model against BOM The tool allows three master column combinations between the BOM and the model. The tool queries the data in the model based on any one of these column combinations: Compare Part Id in BOM with Part Id in model: the tool compares the attributes of a part in the BOM with the part in the model using part id as the key. Compare by Part Name in BOM with Part Name in model: the tool compares attributes of a part in the BOM with the part in the model using part name as the key. Compare by Part Number in BOM with Part Name in model: the tool compares attributes of a part in the BOM with the part in the model using part number as the key.
Altair Engineering

194
BOM Comparison Tool BOM Display Section

BOM info displays in a table in the BOM display section, located in the center of the tool window just below the master column section. BOM info can be displayed in two different modes: BOM only, and Comparison. By default information displays in BOM Only view:
Use the toggle button located in the top-right portion of the GUI to switch to Comparison mode, which categorizes the BOM information into four categories: Match: BOM components whose standard attributes exactly match those in the model Different: BOM components whose standard attributes differ from those in the model In_BOM_Only: components found in the BOM but not in the model In_Model_Only: components found in the model but not in the BOM The screenshot below illustrates Comparison view:
195

Altair Engineering
Column 1 shows the category name with the number of parts falling under that category enclosed in brackets; remaining columns display the BOM info. In the Different category, mismatched attributes between BOM and the model are highlighted in light blue.
Right-click menu Right-clicking on the table opens a menu of functions: Display selected parts displays parts in the model corresponding to the selected rows in the BOM display table. Display all parts will display all the parts in the model. Create metadata creates metadata of all the attributes of the parts in the model corresponding to the selected row in the table. Update metadata updates metadata of all the attributes of the parts corresponding to the selected row in the table. Delete metadata deletes metadata of all the attributes of the parts corresponding to the selected row in the table. Delete deletes the selected row in the table.
Altair Engineering

196
197

Altair Engineering
BOM Comparison Tool Metadata Display Section

You can create, update and delete metadata using some of the menu items on the BOM display table. Metadata information contains all the attributes for a part in the model. The metadata display section contains four display options in the form of a combo box. After selecting a row in the BOM Display table, and then use this combo box to select the type of information displayed in the metadata display table:
None Metadata related to BOM
Clear the table if already some data exists Display BOM related metadata for the selected row in the BOM display table Display all the metadata for the selected row in the BOM display table Display two rows of info in the metadata table. First row corresponds to BOM info, second row corresponds to metadata associated with the model
All metadata
Differences between BOM/metadata
Altair Engineering

198
BOM Comparison Tool Failed Records Section

When a BOM file is loaded, the tool checks for the validity of each standard attribute in a record (a record corresponds to one line of info in the BOM file). The tool considers the following five terms as standard attributes: Part Name Part ID Material Material ID Gauge If at least one attribute is missing or repetitive, the whole record is considered invalid and will be stored outof-sight. Click the Show failed menu item or corresponding button in the control section to see the failed records. This opens a Failed records table as shown below.
You have the option to edit each of those failed records to make them valid and move them to the BOM display table using the Move button.
199

Altair Engineering
Disp Utility Menu

The Disp Utility Menu allows you to clear temporary nodes.
Clear Temp Nodes

Use this button to automatically remove any temporary nodes in the model.
Altair Engineering

200
Geom/Mesh Utility Menu

This menu contains a set of macros related to working with model geometry, as well as a set for working with FE mesh.
The geometry macros are: Preserve edges Prevents specific edges from being suppressed during autocleanup or batchmeshing. Projects free points to surface edges. Depending on the tolerance you specify, points may even project to multiple edges. This can be helpful to achieve uniform meshing with regard to weld points. Isolates either an inner or an outer surface layer (based on the user selected surface) from a 3D model. This macro works only on the surfaces attached to the selected surface. The other layers and thickness are then placed in a temp directory and masked. Extracts a midsurface from a thin solid representation of sheet metal stamped parts, by offsetting one side surfaced to midplane. You select a line whose length represents the solid thickness and a surface, which is part of either the inner or outer side of the solid. The macro also creates the corresponding property card and updates the thickness. This macro is intended to be used with sheet metal parts with uniform thickness and does not work for molded solid parts, etc. with ribs (T junctions). Note that all involved surfaces must have their normals point inward toward the center of the enclosed volume. Note also that this macro only works on enclosed volumes consisting of surfaces; it does not work on 3D solid entities. Washer Scales a copy of a selected circular line to 1.5 times its original size, and then trims this new line into the surface. This allows a higher quality mesh around circular holes. Places four additional fixed points on an inner line, and then projects those points to a concentric line, creating a higher quality mesh.
Project points
Isolate Surface
ThinSolid=>Midsurf
Adj Circ Pts
The mesh macros are: Auto Connectors A pop-up menu that allows you to automatically create connectors and FE realize them from a master connection file. Assigns the thickness of a midsurface geometry to FE properties or elements. Its primary use cases are solid parts with varying thickness.
Midsurf Thickness
201

Altair Engineering
You can also review the thickness as a contour plot on the elements or nodes. Quick Tetramesh Quickly creates an automatic tetrahedral mesh while meeting the requirements for minimum element angle and element size. Improves element quality by moving the mid-edge nodes of second order elements. Fixes slivers and wedges (tetra elements that are so thin as to be nearly planar) by moving nodes to make them more three-dimensional and improve their quality criteria. Creates a layer of washer elements around a circular hole in the mesh. Creates a circular hole (of a given radius) in the mesh at the selected node (as the center of the hole). An optional layer of washer elements can be created along with a rigid spider along the hole. Fills the selected hole and remeshes the surrounding mesh to maintain connectivity. This macro does not remove any rigid spiders that fill the hole; if necessary, delete the rigid spider before using this macro. Trims the model along user-defined trim lines. This is useful for reducing the model size by taking advantage of symmetry etc. Creates a bead of a given height and width along the selected two nodes and connects to the surrounding mesh.
Fix 2nd Order Midnodes Fix Sliver Tetra Elements
Add Washer Trim Hole
Fill Hole
Box Trim
Bead
Altair Engineering

202
Preserve Edges
Both the BatchMesher and the autocleanup features seek to improve mesh speed and/or quality by suppressing minor features (which are assumed to be insignificant). However, sometimes minor features are still important to your analysis. The Preserve Edges macro provides a way to ensure that specific components edges and feature lines do not accidentally get discarded during autocleanup or batch meshing. When you click the preserve edges button, a new pop-up window opens to accept your settings:
The following options are available for the Preserve Edges macro: Clear at start When this checkbox is active, any previously stored feature lines will purge each time you click select edges or select comps. Thus, picking a new set of lines starts over instead of adding to the selection. Clicking this button displays a line selector in the panel area. Use the lines selector to choose the edges you wish preserved. Click this button to highlight the lines already marked for preservation. When active, this checkbox prevents the auto-cleanup function from equivalencing the boundaries between adjacent components. Clicking this button displays a component selector in the panel area. Use the comps selector to choose the components whose boundary edges you wish preserved. Note that this will not preserve lines inside the components only the outer boundary edge. Removes all edges from the preservation list. Saves the preservation state, so that autocleanup and BatchMesher will know which lines must be preserved.
Select Edges
Show Preserved Comps selection boundary Select comps
Clear all edges Save preserved
203

Altair Engineering
Reset highlights
After clicking the show preserved button, use this button to remove the highlight from the preserved lines. The lines remain preserved; only the visual highlighting effect is removed (until you click show preserved again).
OK Cancel
Accepts any changes youve made and closes the pop-up window. Discards any changes youve made and closes the pop-up window.
Altair Engineering

204
Project Points
Use this macro to project geometric points (such as weld points) to nearby edges. Clicking this button opens a surfs selector in the panel area; use this to select the surfaces whose edges you wish to project points to. After selecting surfs and clicking proceed, a target element size field is displayed. Type a value into this field, using the same units as your model. Any points within this distance of the selected surfaces edges will be projected to those edges.
205

Altair Engineering
Auto Connectors Macro

Note: If you are unfamiliar with HyperMesh connector entities, refer to Connector Definition and Connector Realization for more information.
The Auto Connectors macro automates the importation and FE realization of connectors from either a Master Connectors File or an older Master Weld File. Virtually every option available for FE realization in the connectors module is also available in the Auto Connectors macro.
Automated Connector Creation and Fe Realization dialog
Altair Engineering

206
Automated Connector Creation and Fe Realization dialog - custom option
Input requirements for connector entity creation and FE realization are: Master connectors/weld file FE config Projection tolerance Note: In the case of a custom FE config, the custom FE type-to-realize is required. The custom FE type definitions can be found in the appropriate feconfig.cfg file. This script automatically reads the default feconfig.cfg file and displays a list of all the appropriate user-defined FE types (found in the feconfig.cfg file) in the Fe type field.
The property and diameter can be specified if necessary. Additional options are:
207

Altair Engineering
Build systems Snap to node Attach to shells
Altair Engineering

208
Master Weld Files

The Master Weld File provides the weld location and parts to be connected. A format example is shown below. PointId 12:: 23:: 1t/2t/3t 2:: 3:: X 2.25: 3.05:: Y 2.25:: 3.25:: Z 1.0:: 0.25:: PartId1 2:: 2:: PartId2 3:: 3:: 5:: PartId3
209

Altair Engineering
Diameter vs. Thickness Files

DvsT file (diameter vs thickness) contains a table that associates the thickness of components and the nugget diameter of the weld. The equivalent area is taken to determine the side of the hexa. The file format includes thickness range and the corresponding diameter of the weld nugget. Minimum thickness 1.4 2.0 Maximum thickness 1.9 3.0 Nugget diameter 7 8
The nugget diameter is 7.0 for the thickness range of 1.4 to 1.99.
Altair Engineering

210
ACM Welds
An ACM (Area Contact Method) weld is a special representation of a spot weld. The weld is defined using a solid (HEXA) element whose cross-sectional area is equivalent to the area of the weld nugget. The solid element is created at the exact weld location independent of the shell elements that represent the sheet metal parts. These solid elements are connected to the corresponding components using RBE3 elements. The size of the solid element is determined using the DvsT file. The nugget diameter corresponding to the minimum thickness of the connecting parts is obtained from the DvsT file. The size of the hexa is calculated to match the cross-sectional area of the weld nugget. The length of the weld element is calculated using one of the following methods:
(T1+T2)/2
This creates the hexa elements with a length equal to the average component thickness it is connecting. T1 and T2 are the component thicknesses. The first figure below shows the ACM weld created using this method. This creates the hexa elements between the component/element shell surface. The length of the hexa element will be equal to the actual distance between the two connecting components/elements. The second figure below shows the ACM weld created using this method.
Project to shell
The figures below show ACM created using the two currently available methods.
ACM creation using (T1+T2)/2.0 option
211

Altair Engineering
ACM creation using Project to Shells option
The weights of the RBE3 elements are calculated based on the projection of the dependent node on the shell element. The nodes of the shell element closest to the dependent node are assigned a greater weight relative to the node that is farther away. ACM welds can be created and managed using connectors. Once a connector is created, they can be realized as ACM spotwelds as follows: 1. 2. 3. 4. Make sure that the connectors are created at each of the weld locations along with connecting parts information. Make sure all the connecting parts have PSHELL cards with correct thicknesses. Select the connectors to be realized as ACMs in the FE Realize panel of the Connectors module. Choose custom element config and select type = Nastran 70 ACM((T1+T2)/2) or type = Nastran 71 ACM (Shell Gap) per your requirements. The appropriate property script is automatically loaded for the selected type. Set the appropriate tolerance (proj tol= ) value. Make sure the attach to shell and snap to node options are turned off in fe options. Select a DvsT file, which determines the size of the hexa based on the thicknesses of the components being connected. If no DvsT file is selected, hexas are created with weld nugget diameter =1.0
5. 6. 7.
Altair Engineering

212
8.
Click realize.
213

Altair Engineering
CWELD Elements
CWELD elements are created as patch-patch, meshless elements. The 1D element is not connected to the shell element. For details regarding connected shell elements or nodal information see the element card. For CWELD elements, the diameter is determined from a DvsT file based on the component thickness. In addition to the creation of CWELD elements, a corresponding property card (PWELD) is created with an updated diameter D attribute value.
Altair Engineering

214
Midsurf Thickness
Geometric surfaces that represent the mid-plane of a solid part have thickness information stored in their definition if they are extracted using the HyperMesh midsurface function. The thickness data can be a single value for the entire part or a varying function. The Midsurf thickness macro, located on the Geom/ Mesh Utility Menu, allows you to transfer thickness data from surfaces to the associated nodes/elements. You can also review the contour plot of thickness data with this macro. Note : Currently the utility only supports tria3 and quad4 elements. This utility may behave differently under different user profiles.
When you click the Midusrf thickness menu button, the controls for this macro display in a new tab in the tab area.
The following options are available in the Midsurf thickness... macro: Assign thickness to You can choose to assign or view the thickness values using several methods. Use the Elements option to assign the thickness and Z-offset values (where supported) directly to the element cards. For each user profile, the values will be updated on the element card for that solver. Refer to the User profile section for more details on the unique behavior of the Midsurf Thickness utility for each user profile. Use the Properties on elements option to group elements that fall within user-specified thickness intervals into common ranges, then create and
215

Altair Engineering
assign to each of those elements in each range a property with the range thickness value assigned to the property card image. Most solvers only have Z-offset defined on the element card, so this value will always be populated on the element cards for any solver that supports Z-offset. In order to execute this mode, a base property named t0 must be defined. The t0 property definition will be used for all created properties based on the option specified in the Organization Method section described below. This option performs the following generic steps: 1. Creates properties with name "t[thickness value]" by copying the properties of the base property t0 and assigning the appropriate thickness based on the value of the Organization Method. Assigns to the elements that have thickness values within the specified ranges, based on the value of the Organization Method, the relevant property.
2.
You can also choose Organize only to create new components and sort the selected elements into them according to the Organization Method (see below) that you specify. Use the Properties on components option to group elements that fall within user-specified thickness intervals into common components, then create and assign to each of those components a property with the thickness value assigned to the property card image. Most solvers only have Z-offset defined on the element card, so this value will always be populated on the element cards for any solver that supports z-offset. In order to execute this mode, a base property named t0 must be defined. The t0 property definition will be used for all created properties based on the option specified in the Organization Method section described below. This option performs the following generic steps: 1. Creates components and properties with name "t[thickness value]" by copying the properties of the base property t0 and assigning the appropriate thickness based on the value of the Organization Method. Assigns to property to its corresponding component. Removes any property assignments to the elements. Organizes the elements that have thickness values within the specified ranges into the new components based on the value of the Organization Method.
2. 3. 4.
You can also choose Organize only to create new components and sort the selected elements into them according to the Organization Method. Use Z-Offset values Activate this checkbox to take z-offsets into account. HyperMesh uses zoffsets when midsurfacing parts that have variable thickness; the z-offset (which is saved as part of the midsurface data) tells a solver how much of a positive-normal offset exists between the actual part surface and the midsurface:
Altair Engineering

216
To assign z-offset values to the element cards for supported solvers, check the Use Z-offset values checkbox. This option is only valid for certain user profiles. Thickness calculation method This option determines how the thickness value is calculated for each element. Nodal values Multiple thickness values are calculated for each element by finding the thickness at each of the element nodes. It is possible for a node to have multiple thickness values at a single location (shared surface edge where the surfaces have different thickness). The thickness calculated using that node for an element is dependent on which surface that element is associated to. Average A single thickness value is calculated for each element by averaging the thickness at each of the element nodes. Centroid A single thickness value is calculated for each element by calculating the thickness at the centroid of the element. Max A single thickness value is calculated for each element by calculating the thickness at each node of the element and taking the max value. Min A single thickness value is calculated for each element by calculating the thickness at each node of the element and taking the min value. Organization method This option specifies the thickness range intervals used to generate properties based on their thickness values. Based on the Assign thickness to option, the properties and components are generated for certain thickness ranges. Any element with a thickness value within that range is assigned that property or organized into that component. You can specify thickness range intervals by two methods: 1. 2. Gauge file You must specify the thickness range intervals in a Gauge File. Click here for details on the format of the gauge file. Range Interval You must specify a thickness tolerance. Thickness range intervals are automatically generated based on the thickness tolerance using the following formula. The thickness assigned to each created component is n*tolerance. Lower limit = (tolerance / 2) + (tolerance* i )
217

Altair Engineering
Upper limit = (tolerance / 2) + (tolerance* (i + 1)) Assigned value = tolerance*(i+1) Where i = 0n, n is determined by the maximum thickness in model divided by the user specified tolerance and then rounding to up to the next integer. Assign Assigns the thickness from the surface definition to the selected elements, based on the options specified. Creates a contour plot of the thicknesses on the selected elements/nodes based on the options specified. This step does not assign the thickness to the nodes or elements; it is a review/display function only. It is very useful for visualizing and verifying the results of the Midsurf Thickness utility before applying the midsurf thickness mapping operation. If you chose Properties on elements, Properties on components, or Organize only under the Assign thickness to option, HyperMesh honors the Organization method settings during the contour process and the contour value is assigned based on that organization. This allows the contour to match with the applied results. If you chose Elements or Properties on components for the Assign thickness to option, and choose to use Nodal values for the Thickness calculation method, the values may not exactly match the nodal values that are actually applied. There can be multiple thicknesses associated to a node if it shares an edge with multiple surfaces. Since HyperMesh can only provide one value for the contour, it always chooses the first value which might not match exactly with the applied values in these situations. Close Closes the tab.
Contour
Altair Engineering

218
To assign thickness and z-offset values using the Elements option

1. 2. 3. 4. 5. 6. 7. 8. Change to your preferred user profile. Load the desired model file. Access the Midsurf thickness utility from the Geom/Mesh page of the Utility Menu. Select the Elements option. Optional: use the Use Z-Offset value check box to assign both thickness and Z-offset values. Leave the checkbox blank to assign only the thickness values. Click the Assign button to open the element selection panel. Select the elements to map the midsurface thickness onto. Click the proceed button to perform the thickness mapping.
219

Altair Engineering
To assign thickness and z-offset values using the Properties on Components option
1. 2. 3. 4. 5. 6. 7. 8. 9. Change to your preferred user profile. Load the desired model file. Create the base component "t0", the base property "t0" and assign the base property the relevant card image. Enter any default values for this card. Access the Midsurf thickness utility from the Geom/Mesh page of the Utility Menu. Select the Properties on components option. Optional: use the Use Z-Offset value check box to assign both thickness and Z-offset values. Leave the checkbox blank to assign only the thickness values. Select a Thickness calculation method. Select a Component organization method and either select a file or enter a tolerance based on the method. Click the Assign button to open the element selection panel.
10. Select the elements to map the midsurface thickness onto. 11. Click the proceed button to perform the thickness mapping
Altair Engineering

220
To assign thickness and z-offset values using the Properties on Elements option
1. 2. 3. 4. 5. 6. 7. 8. 9. Change to your preferred user profile. Load the desired model file. Create the base property "t0" and assign the base property the relevant card image. Enter any default values for this card. Access the Midsurf thickness utility from the Geom/Mesh page of the Utility Menu. Select the Properties on elements option. Optional: use the Use Z-Offset value check box to assign both thickness and Z-offset values. Leave the checkbox blank to assign only the thickness values. Select a Thickness calculation method. Select a Component organization method and either select a file or enter a tolerance based on the method. Click the Assign button to open the element selection panel.
10. Select the elements to map the midsurface thickness onto. 11. Click the proceed button to perform the thickness mapping.
221

Altair Engineering
To organize elements using the Organize Only option

1. 2. 3. 4. 5. 6. 7. 8. Change to your preferred user profile. Load the desired model file. Create the base component "t0". Access the Midsurf thickness utility from the Geom/Mesh page of the Utility Menu. Select the Organize only option. Click the Assign button to open the element selection panel. Select the elements to organize. Click the proceed button to perform the organization.
Altair Engineering

222
To contour thickness and z-offset values using the Elements option

1. 2. 3. 4. 5. 6. 7. 8. 9. Change to your preferred user profile. Load the desired model file. Access the Midsurf thickness utility from the Geom/Mesh page of the Utility Menu. Select the Elements option. Optional: use the Use Z-Offset value check box to assign both thickness and Z-offset values. Leave the checkbox blank to assign only the thickness values. Click the Contour button to open the node selection panel. Optional: Select nodes to generate the midsurface thickness contour. Click the proceed button to open the element selection panel. Optional: Select elements to generate the midsurface thickness contour.
10. Click the proceed button. The utility opens the Contour panel and shows the thickness contour. If both nodes and elements were selected, the data type can be changed inside the panel to review the nodal or elemental thickness contours. If the Use Z-Offset value box was checked, the data type can also be changed to view the Z-Offset contour.
223

Altair Engineering
To contour thickness and z-offset values using the Properties on Components option
1. 2. 3. 4. 5. 6. 7. 8. 9. Change to your preferred user profile. Load the desired model file. Access the Midsurf thickness utility from the Geom/Mesh page of the Utility Menu. Select the Properties on components option. Optional: use the Use Z-Offset value check box to assign both thickness and Z-offset values. Leave the checkbox blank to assign only the thickness values. Select a Thickness calculation method. Select a Component organization method and either select a file or enter a tolerance based on the method. Click the Contour button to open the node selection panel. Optional: Select the nodes to generate the midsurface thickness contour.
10. Click the proceed button to open the element selection panel. 11. Optional: Select the elements to generate the midsurface thickness contour. 12. Click the proceed button. The utility opens the Contour panel and shows the thickness contour. If both nodes and elements were selected, the data type can be changed inside the panel to review the nodal or elemental thickness contours. If the Use Z-Offset value box was checked, the data type can also be changed to view the Z-Offset contour.
Altair Engineering

224
To contour thickness and z-offset values using the Properties on Elements option
1. 2. 3. 4. 5. 6. 7. 8. 9. Change to your preferred user profile. Load the desired model file. Access the Midsurf thickness utility from the Geom/Mesh page of the Utility Menu. Select the Properties on elements option. Optional: use the Use Z-Offset value check box to assign both thickness and Z-offset values. Leave the checkbox blank to assign only the thickness values. Select a Thickness calculation method. Select a Component organization method and either select a file or enter a tolerance based on the method. Click the Contour button to open the node selection panel. Optional: Select the nodes to generate the midsurface thickness contour.
10. Click the proceed button to open the element selection panel. 11. Optional: Select the elements to generate the midsurface thickness contour. 12. Click the proceed button. The utility opens the Contour panel and shows the thickness contour. If both nodes and elements were selected, the data type can be changed inside the panel to review the nodal or elemental thickness contours. If the Use Z-Offset value box was checked, the data type can also be changed to view the Z-Offset contour.
225

Altair Engineering
Gauge File Format & Example

The Gauge file uses the following format:
Number of Gauges [Number of Gauge Data Lines] Gauges Begin [min Thk] If the Assigned Value is not specified, then the average of the upper and lower limits will be used as Assigned Value. Below is a specific example of a gauge file: End [max Thk] Assigned Value [Assigned Thk]
Number of Gauges 4
Gauges Begin 0.0 0.05 0.1 0.15 End 0.05 0.1 0.15 0.2 Assigned Value 0.05 0.1 0.15 0.2
Altair Engineering

226
Midsurf Thickness Behavior Under Different User Profiles

Common to All User Profiles
Organize only Creates new components based on the Organization method. Organizes elements into these components.
Contour Creates a contour of the thickness values of nodes and elements, based on the specified options. If you chose Properties on elements, Properties on components, or Organize only under the Assign thickness to option, HyperMesh honors the Organization method settings during the contour process and the contour value is assigned based on that organization. This allows the contour to match with the applied results. If you chose Elements or Properties on components for the Assign thickness to option, and choose to use Nodal values for the Thickness calculation method, the values may not exactly match the nodal values that are actually applied. There can be multiple thicknesses associated to a node if it shares an edge with multiple surfaces. Since HyperMesh can only provide one value for the contour, it always chooses the first value which might not match exactly with the applied values in these situations.
Abaqus
Properties on components Creates new components based on the Organization method. Creates new properties based on the Organization method. Assigns the properties to the corresponding components. Assigns a single thickness to each property based on the Thickness calculation method, using property attribute TK. Organizes elements into the corresponding components. Clears any element property references for the selected elements.
Properties on elements Creates new properties based on the Organization method. Assigns a single thickness to each property based on the Thickness calculation method, using property attribute TK.
227

Altair Engineering
Assigns the properties to the corresponding elements.
ANSYS
Properties on components Nodal values Creates new components based on ordered nodal thickness values. Creates new properties based on ordered nodal thickness values. Assigns the properties to the corresponding components. Assigns multiple thicknesses to each property, using real values. Organizes elements into the corresponding components.
Properties on components all others Creates new components based on the Organization method. Creates new properties based on the Organization method. Assigns the properties to the corresponding components. Assigns a single thickness to each property based on the Thickness calculation method, using real values. Organizes elements into the corresponding components.
LS-Dyna
Elements Assigns multiple thicknesses to each element, based on the nodal thickness values for that element: For tria3 elements, uses attributes: Elem_Option LSD_ELEM_T1 LSD_ELEM_T2 LSD_ELEM_T3 For quad4 elements, uses attributes: Elem_Option LSD_ELEM_T1 LSD_ELEM_T2
Altair Engineering

228
LSD_ELEM_T3 LSD_ELEM_T4
Properties on components Creates new components based on the Organization method. Creates new properties based on the Organization method. Assigns the properties to the corresponding components. Assigns a single thickness to each property based on the Thickness calculation method, using property attribute LSD_T1. Organizes elements into the corresponding components.
Marc
Properties on elements Creates new properties based on the Organization method. Assigns a single thickness to each property based on the Thickness calculation method, using component attribute TK. Assigns the properties to the corresponding elements.
Moldflow
Properties on components Creates new components based on the Organization method. Assigns a single thickness to each property based on the Thickness calculation method, using component attribute T. Organizes elements into the corresponding components.
Nastran
Elements Assigns multiple thicknesses to each element, based on the nodal thickness values for that element: For tria3 elements, uses attributes:
229

Altair Engineering
CTRIA3_T1T2T3 CTRIA3_T1 CTRIA3_T2 CTRIA3_T3 CTRIA3_ZOFFS [if requested] ZOFFS [if requested] For quad4 elements, uses attributes: CQUAD4_T1T2T3T4 CQUAD4_T1 CQUAD4_T2 CQUAD4_T3 CQUAD4_T4 CQUAD4_ZOFFS [if requested] ZOFFS [if requested] Turns off the TFLAG option when necessary.
Properties on components Creates new components based on the Organization method. Creates new properties based on the Organization method. Assigns the properties to the corresponding components. Assigns a single thickness to each property based on the Thickness calculation method, using property attribute PSHELL_T.
For tria3 elements, uses z-offset attributes [if requested]: CTRIA3_ZOFFS ZOFFS
For quad4 elements, uses z-offset attributes [if requested]: CQUAD4_ZOFFS ZOFFS
Organizes elements into the corresponding components. Clears any element property references for the selected elements.
Altair Engineering

230
Properties on elements Creates new properties based on the Organization method. Assigns a single thickness to each property based on the Thickness calculation method, using property attribute PSHELL_T.
OptiStruct/RADIOSS (Bulk Data Format)

Elements Assigns multiple thicknesses to each element, based on the nodal thickness values for that element: For tria3 elements, uses attributes: CTRIA3_T1T2T3 CTRIA3_T1 CTRIA3_T2 CTRIA3_T3 CTRIA3_ZOFFS [if requested] ZOFFS [if requested] For quad4 elements, uses attributes: CQUAD4_T1T2T3T4 CQUAD4_T1 CQUAD4_T2 CQUAD4_T3 CQUAD4_T4
231

Altair Engineering
CQUAD4_ZOFFS [if requested] ZOFFS [if requested]
Properties on components Creates new components based on the Organization method. Creates new properties based on the Organization method. Assigns the properties to the corresponding components. Assigns a single thickness to each property based on the Thickness calculation method, using property attribute PSHELL_T.
Organizes elements into the corresponding components. Clears any element property references for the selected elements.
Properties on elements Creates new properties based on the Organization method. Assigns a single thickness to each property based on the Thickness calculation method, using property attribute PSHELL_T.
Altair Engineering

232
PAM-CRASH 2G
Elements Assigns a single thickness at the element level based on the Thickness calculation method. Uses element attribute ELEM_THK.
Properties on components Creates new components based on the Organization method. Assigns a single thickness to each component based on the Thickness calculation method, using component attribute MAT_THK. Organizes elements into the corresponding components.
PERMAS
Properties on components Nodal values Creates new components based on ordered nodal thickness values. Creates new properties based on ordered nodal thickness values. Assigns the properties to the corresponding components. Assigns multiple thicknesses to each property, using property attributes: ThicknessSelEnumField Thick_value_shell1 Thick_value_shell2 Thick_value_shell3 Thick_value_shell4 Organizes elements into the corresponding components.
Properties on components all others Creates new components based on the Organization method. Creates new properties based on the Organization method. Assigns the properties to the corresponding components. Assigns a single thickness to each property based on the Thickness calculation method, using property attributes:
233

Altair Engineering
ThicknessSelEnumField Thick_value_shell1 Organizes elements into the corresponding components.
RADIOSS (Block Format)

Elements Assigns a single thickness at the element level based on the Thickness calculation method. Uses element attribute THICK.
Properties on components Creates new components based on the Organization method. Creates new properties based on the Organization method. Assigns the properties to the corresponding components. Assigns a single thickness to each property based on the Thickness calculation method, using property attribute THICK. Organizes elements into the corresponding components.
Altair Engineering

234
Quick TetraMesh
The Quick TetraMesh macro quickly creates a tetramesh of an enclosed volume defined by geometry and/or elements. Its main objective is to quickly and automatically create a tetramesh that meets the minimum interior angle and minimum element size. During the process of quick tetramesh, the mesh may deviate from the underlying geometry in order to maintain good quality elements. To alleviate this, you can select "sacred elements" so that the tetmeshing function closely follows the original geometry. This macro is accessed on the Geom/Mesh Utility Menu located on the standard Utility Menu, and displays in a new tab in the tab area.
The following options are available in the Quick TetraMesh macro: Volume complist Double-click components and use the comps collector that displays in the panel area to select comps representing the geometry of the solid to
235

Altair Engineering
be tetra meshed. Surfaces and/or elements can be used to define the volume. Click proceed to finalize the selection. Minimum tria angle The surface trias from which the tetramesh will be extrapolated will be generated with angles that measure at least this many degrees. Use this control to limit how acute the resulting elements will be. The maximum feature angle protects nodes on corners with a feature angle greater than the value specified, helping to better maintain the geometry. This applies only to cases where you can maintain features while fixing minimum element size. For example, if two nodes of an element share different features (as in thin steps), the features may not be maintained as they do not pass minimum element criteria. The maximum feature angle allowed between normals of adjacent elements. If the feature angle exceeds the given value, two adjacent elements are considered reversed and actions are performed to correct the situation. Average element size of the mesh to be created. No single edge of any generated element will be shorter than this. Minimum allowable area for any element. When element nodes are moved to improved element quality, it gives special preference to trying to keep the nodes on a sacred surface. Note: this does not work if two adjacent surfaces are both marked as sacred! Sacred elements These are existing trias that you have created according to your requirements and wish to maintain while tetrameshing the part. This is useful in ensuring that a particular feature is captured exactly the way you want it to be. The tetramesher will not move the nodes of these elements, even if doing so would improve element quality. Note that this setting overrides the float setting in the tet from option, but only for the elements selected as sacred. Mesh type The mesh type options are Trias Only and Mixed. With the Mixed mesh type, both trias and quads may be created. Choose between chordal deviation and uniform . Chordal deviation uses smaller elements along curves, feature lines, and edges to improve accuracy, but requires more computing time. Uniform uses identicallysized elements throughout the mesh, but may produce low-quality elements along such locations. Choose floating, in which the quick tetramesher is free to move nodes in
Maximum feature angle
Maximum reverse angle
Mesh size Minimum edge size Minimum elem size Sacred surface
Mesh density
Tet from
Altair Engineering

236
a surface tria mesh to achieve better tetra elements based on them, or fixed, in which the mesher must keep the tria mesh unchanged. Mesher Choose between automesh and batch. This determines the meshing engine used: the one used by the Automesh panel, or the one used by the BatchMesher. The BatchMesher generally produces better results, but does not currently support sacred surfaces or elements, ignores/ replaces existing elements, and always uses uniform density. When this option is checked, no tetra elements are created and the macro simply goes through the cleanup steps for the shell mesh. Some of the cleanup operations performed are: the suppression of free edges, correction of sliver elements, splitting of elements, and projections onto the original geometry. All the cleanup steps are designed to improve the mesh quality. Perform the quick tetramesh with the specified settings. Note: There is no Undo function! You can, however, attempt to remesh using different settings if you do not like the initial results. Debug Surface Mesh A series of tools that help you located problem areas which can cause poor meshing: Find Holes Find T-Con Dihedrals Locate holes in your model. Locate T-connections in the model. Locate features in the model that have feature angles greater than 150 degrees. Locate entities attached to the selected components. After making adjustments, click this to re-run the meshing operation on the same components.
Perform mesh cleanup only
Mesh
Attached Try TetraMesh
Help
Opens a pop-up window with basic information about each control that displays on the tab. Closes the tab.
Close
The Quick Tetramesh macro meshes the unmeshed surfaces in the model using chordal deviation and fixes all the elements that fail the criteria provided. You can manually mesh some critical geometry and select those elements as sacred elements. These sacred elements need to be trias. As a part of the cleanup, the tool heals small cracks in the model. Suggested process to effectively use quick tetramesh: 1. 2. Load the geometry. For critical areas where you want to control the mesh such as bolt holes, manually mesh using chordal
237

Altair Engineering
deviation. Select these elements as sacred elements. This helps to obtain the desired mesh in critical areas. 3. 4. 5. 6. Launch the Quick Tetramesh macro. Run with the desired mesh size. Identify problem areas, if any (e.g. any surfaces edges that were ignored, or if mesh in certain areas is not satisfactory). Use the Delete panel to delete the tetras, then manually mesh problem areas. Re-launch the Quick Tetramesh macro and select sacred elements to protect.
Altair Engineering

238
Fix 2nd Order Midnodes

This macro improves element quality by moving the mid-edge nodes of second order elements. You select the elements on which you want to improve the quality, and specify the quality constraints: Minimum Jacobian (evaluated at the corner nodes or integration points), Minimum Ratio between the minimum and maximum edge length, and Maximum angle. Note: Moved midnodes are saved to your save list; this persists until you exit the program. In addition, moved midnodes lose any preexistent association with the underlying geometry.
Typical usage of this utility begins with use of the Check Elems panel to identify poorly-formed elements, and using that panels save failed option. From that point onward, you use the Fix 2nd Order Midnodes utility: 1. Open the Fix 2nd Order Midnodes dialog. An element selector and proceed button display in the panel area. 2. 3. Click the elems selector and select retrieve to load the saved failed elements. Click proceed. The Fix 2nd Order Midnodes window opens. This pop-up window exists independently of the rest of the environment, so you can click-and-drag it to any desired location.
239

Altair Engineering
The Fix 2nd Order Midnodes w indow .
4.
In the Fix 2nd Order Midnodes dialog, choose your element quality constraints: Choose a maximum angle . The utility will move midnodes such that the angle at the ends of each segment will not deviate from a straight line by more than this amount (thought of another way, the angle between the segments at the midnode will not exceed 180 degrees minus this value). See the screenshot above for an example using a value of 30 degrees. Specify a limit to the Aspect Ratio (minimum versus maximum length for the segments of the midnode-bearing edges). A value of 1 represents perfectly equal segment length, while a length of 0 would mean that the shorter segment might not exist, so this value must be greater than 0, but no greater than 1. Remember that this is a minimum ratio, so a value of 0.5 would allow the shorter segment to be half as long as the longer segment, or longer but not shorter than half the length of the longer segment. Specify a minimum Jacobian value, and use the radio buttons to determine whether HyperMesh should evaluate each elements Jacobian at the corner nodes or the integration points.
Altair Engineering

240
Use the allow movement checkbox to tell HyperMesh to keep the boundary nodes on the underlying model geometry, but attempt to improve the Jacobian value by moving internal nodes. If unchecked, the Move off geometry if needed option will be activated automatically. Use the Move along geometry first checkbox to allow nodes on geometry to move along (but not leave) the geometry features before any other node movement occurs. Check Move off geometry if needed to allow HyperMesh to move boundary nodes off of the underlying geometry if a satisfactory Jacobian value cannot be achieved by moving along geometry or moving internal nodes. Note that this feature is always active when Allow movement is unchecked. 5. Click one of the command buttons to perform an action: Jacobian checks the current selected elements' Jacobian values and displays them in the results area. Apply tells HyperMesh to move the midnodes to try to match the criteria you specified. Reject undoes any changes made when you pressed apply. Close closes the Fix 2nd Order Midnodes dialog. When you click Apply, a message displays under the Results heading to inform you of exactly what HyperMesh did to the mesh. The images below illustrate the before-and-after state of a specific midnode and the criteria used, as well as the overall results:
Before clicking Apply
241

Altair Engineering
After clicking Apply
Altair Engineering

242
Add Washer
This utility creates one or more layers of washer elements around a circular hole in an existing mesh. When you click the add washer button, a temporary panel in the panel area allows you to pick a single node from the edge of a hole.
Once you do so and click proceed, all nodes on the hole are selected automatically and the utility opens.
The utility automatically determines the Hole radius. You can specify a Number of layers of concentric washer elements to add around the hole.
243

Altair Engineering
If you choose to add more than one layer, you can also choose whether or not to have all layers be Uniform in width, or to allow them to have Varying widths from one another. If you choose Varying, each layer displays separately in the table below this option, allowing you to specify a different value for each layer. Each layer of elements can be given a specific Width (the size of the elements) or a Scale (a factor of the hole's radius--i.e. using a scale of 1.0 produces washer elements whose size is the same as the hole's radius).
Mesh size 5, 2 w asher layers of w idth 2.
Mesh size 5, 1 w asher layer of scale 1.0.
Finally, you can select a few creation options: Create rigid spider along hole :
Altair Engineering

244
Create local coordinate system :
Minimum number of nodes around hole: Prevents the washer from using fewer nodes than this around the hole, in order to maintain a desired level of granularity. Note that a larger number than this may be generated in order to generate a uniform mesh of washer elements, particularly when using smaller numbers for the minimum. When active, this also enables the Density numeric box, which lets you specify the exact minimum number. Click Add to create the washer layers. If the results are not acceptable, click Reject and alter your settings.
245

Altair Engineering
Trim Hole Macro

This function creates a circular hole of a given radius in the mesh at a node specifying the center of the hole. You can also specify a number of layers of washer elements to include. Clicking Trim Hole opens a nodes selector panel. Pick nodes on your model for the centers of each hole that you wish to create, then click proceed. A dialog opens:
The options in the Mesh Trimming with Circular Holes dialog determine the type of hole that is created at each chosen node: Hole radius Number of layers Each node will receive a hole of this radius, measured from the node. This is the number of layers of washer mesh elements that you want to surround each hole. This toggle only applies when the number of layers is more than zero, and specifies whether you want mesh layers to all be the same width, or to vary from one another. The number of a specific washer layer. If you chose varying width for the layers, the table displays one row for each of the number of layers that you specified. Otherwise, only one row displays because all layers will be set to the same values. Determines the width of the washer layers.
Uniform/Varying
No.
Scale/Width
Altair Engineering

246
Scale: you can specify each layers scale relative to the Hole radius. For example, use "0.5" for a washer layer thats half as wide as the hole radius. Width: specify a fixed width for each layer. Value The scale factor or width of the layer(s).
Create rigid spider along This checkbox will create a rigid spider in each of the new holes created, the hole and enables two more options: Choose individual rigid links to create rigid elements at each node of the new hole. Choose single rigid link to create one rigid element that connects to all of the nodes around the new hole. Minimum number of nodes around the hole This determines the mesh density around the new hole(s). Each new hole will be created with at least the number of nodes that you specify in the density field, evenly spaced around its circumference. Click this button to create the new hole(s). If you dont like the results of the last trim operation, click this button to undo it. Note that this only undoes a single click of the trim button, so it can only undo multiple holes if they were created simultaneously during a single trim operation. Close the Mesh Trimming with Circular Holes dialog.
Trim Reject
Close
247

Altair Engineering
Fill Hole Macro

The Fill Hole dialog fills in one or more holes in your geometry with automatically-generated mesh. Note: This macro does not remove any rigid spiders that currently fill the hole; if necessary, delete the rigid spider before using this macro.
When you open the Fill Hole function, a new dialog opens:
There are two methods of filling holes: Manual Use this option to select the holes that you wish to fill: 1. 2. 3. Click the yellow Select Nodes button. The panel area is once again displayed, with a nodes selector active. Select nodes on the edges of the holes that you wish to fill. Click proceed in the panel area. The Filling holes with mesh dialog returns, with the Select Nodes button now green to indicate that nodes have been chosen. Click the Fill button to fill the selected holes with mesh.
4. Automatic
Use this option to select holes automatically based on size. Type a value into the entry field labeled Fill circular holes with radius smaller than:. The model is automatically scanned for holes smaller than this value, and attempt to fill them with mesh. Click this button to perform the fill operation, whether you choose to select your holes manually or automatically. If you dont like the results of the last fill operation, click this button to undo it. Note that this only undoes a single click of the fill button, so it can only undo multiple fills if they were created simultaneously during a single fill operation. Close the Filling holes with mesh dialog.
Fill
Reject
Close
Altair Engineering

248
249

Altair Engineering
Box Trim Macro

The Box Trim macro allows you to trim the model (or selected subset) along the global axis to fit the selected 3-D box. For example, a full car model can be trimmed along the Y=0 axis to obtain the left or right side of the car. The selected model can be trimmed along eight standard types: left Split the model along global Y=ymiddle and save the model between Y=ymin and Y= ymiddle (ymiddle =(ymin+ymax)/2). Split the model along global Y=ymiddle and save the model between Y= ymiddle and Y=ymax. Split the model along global X=value (selected value) and save the model between X=xmin and X=value. Split the model along global X=value (selected value) and save the model between X=value and X=xmax. Split the model along global Y=ymiddle and X=value (selected value) and save the model between Y=ymin and Y=ymiddle, and X=xmin and X=value. Split the model along global Y=0.0 and X=value (selected value) and save the model between Y=0.0 and Y=ymax, and X=xmin and X=value. Split the model along global Y=0.0 and X=value (selected value), and save the model between Y=ymin and Y=0.0, and X=value and X=xmax. Split the model along global Y=0.0 and X=value (selected value) and save the model between Y=0.0 and Y=ymax, and X=value and X=xmax.
right
front
rear
frontleft
frontright
rearleft
rearright
This macro is useful in applications where some types of analysis can be performed on one-half (or quarter) of the model using symmetry boundary conditions. The axis directions and terminology are based on modeling standards in the automotive industry.
Altair Engineering

250
The model can also be trimmed using custom box by either selecting the two corner nodes or center node and dimensions. Note This macro is for the 1st order plate elements only.
To box trim a model: 1. 2. Open the Box Trim function. Using the extended entity selection, select the elements you would like to trim and click proceed or the middle mouse button.
251

Altair Engineering
If no elements are selected, all displayed elements are selected. 3. From the Box Trim dialog, choose the appropriate option from the Box trim type: menu. If you select a standard type, select the node/enter value for trim location. If you select custom , define the box by either selecting two corner nodes (Corners) or selecting the center node and dimensions (Distance from center). If you select Corners, click the icon, and Z bounds of the box. , and select the two corner nodes that define the outer X, Y
If you select Distance from center, click the icon, , and select the center node. Then enter Delta X, Delta Y and Delta Z values which is the distance from the center node to the outer bounds of the box in global X, Y and Z directions. 4. You can turn on the option of creating constraints (SPCs) for all the nodes along the face of the box. The nodes are constrained in the appropriate directions depending on the trim axes and are stored in the specified load collector (SPC collector). If no load collector is specified, the constraints are created in the current load collector. You can also specify a Box collector. A large hexa element that represents the box will be created for visualization in the specified collector. Click Trim . (Reject will undo all the above.)
5. 6.
Altair Engineering

252
Bead utility
Use this utility to add a bead between two points in a mesh. Note that if you need to make a curved bead, or a bead across jointed or highly-curved components, this is best accomplished with the sculpting tools in HyperMorph's Freehand panel. However, the bead utility presents a quick and easy way to create simple linear beads, such as those used to initiate crumple zones in vehicular crash mitigation. Beads can be of any height or radius, and can be sharp (curved or angled along the top) or flat (raised from the surface, but flat along the top.) However, this distinction will only be apparent if the radius and height are relatively close to the existing element size.
Radius 20, height 5, either sharp or flat, w ith mesh size 8
Radius 10, height 5, sharp, w ith mesh size 8
Radius 10, height 5, flat, w ith mesh size 8
When you select the bead utility, a temporary panel in the panel area allows you to pick two nodes to define the beginning and end of the bead. Only two nodes are supported by this tool. Once you select the nodes and proceed, the panel closes and the bead utility opens in a new dialog window.
253

Altair Engineering
This dialog allows you to specify several bead characteristics: Bead radius determined the width of the bead at its base. It's best to base this to some degree on the existing element size. Bead height is how far the bead rises above the mesh on which the end nodes reside. The Bead shape determines whether the bead has a flat top, or a peaked or rounded one. When the characteristics are set, click Create to generate the bead. If the results are not satisfactory, click Reject and change the characteristics, then create again. If you need to change the start and end nodes, you will need to Reject any bead already created, Close the utility, and then re-open it to select new nodes.
Altair Engineering

254
Fix Sliver Tetra Elements

Sliver Elements are tetrahedral elements which are so flattened that all of its nodes are very close to planar. If the element's Aspect Ratio (the ratio of its maximum length to its minimum length) is high, the element is a wedge; otherwise, it's a sliver.
This sliver is nearly flat in the horizontal plane, w hile this w edge is nearly flat in the vertical plane.
The Fix Sliver Elements tool attempts to improve the element quality of slivers and wedges by moving or merging nodes. When you click Fix Sliver Elements, you will first be prompted to select a set of elements to fix. Once you do so and proceed, a new window opens which contains the tools and settings for fixing slivers and wedges.
255

Altair Engineering
There are many criteria that you can consider in fixing such elements, each of which is drawn from the Criteria File Editor. fix sliver tetras fix wedge tetras If left unselected, slivers will not be fixed. If left unselected, wedges will not be fixed.
permit moving internal nodesThis option moves internal nodes of each element to improve quality. This does not apply to mesh boundary nodes. boundary nodes: permit moving boundary nodes: permit adding/deleting This option moves boundary nodes of each element to improve quality, and may result in deviations from the base geometry features. Wedge elements are fixed by merging the nodes of their shortest edge. However, if the short edge includes boundary nodes, the wedge will not be fixed unless you activate this option (by default it is not active).
Altair Engineering

256
Aspect Ratio Tet collapse
The ratio of the longest edge of an element to its shortest edge. Tetra collapse is calculated by the following procedure. At each of the four nodes of the tetra, the distance from the node to the opposite side of the element is divided by the square root of the area of the opposite side. The minimum value found is normalized by dividing it by 1.24, and then reported. As the tetra collapses, this value approaches 0.0. For a perfect tetra, this value is 1.0. Volumetric skew is calculated by the following procedure. A sphere is fit through the four nodes of the tetra. That sphere defines an ideally shaped equilateral tetra, whose volume is tetra element is then calculated. . The actual volume of the
Vol Skew
The element's volumetric skew is then (Videal -Vactual)/Videal. This measure will, normally, equal the skew measure from Tgrid, and equal 1 minus the equivalent check in Abaqus. Skew Skew applies to trias, so in this case it's applied to the faces of a tetrahedron. In trias is calculated by finding the minimum angle between the vector from each node to the opposing mid-side and the vector between the two adjacent mid-sides at each node of the element. Ninety degrees minus the minimum angle found is reported as the skew. Vol AR Vol AR for tetrahedral elements is calculated using the following procedure: first it finds the longest edge of the tetrahedron, then it finds the shortest altitude of the tetrahedron. The element's Vol AR, then, is the length of the longest edge divided by the length of the shortest altitude. For other types of 3d element, the ratio of the longest to the shortest edge is reported. The amount by which an element or element face (in the case of solid elements) deviates from being planar. Warpage of up to five degrees is generally acceptable. The minimum allowable interior angle for the tria face of a tetra element. The maximum allowable interior angle for the tria face of a tetra element. A measure of the deviation of an element from an ideally shaped element. The Jacobian value ranges from 0.0 to 1.0, where 1.0 represents a perfectly shaped element. However, Jacobian values of 0.7 and above are generally acceptable. The determinant of the Jacobian relates the local stretching of the parametric space required to fit it onto global coordinate space. HyperMesh evaluates the determinant of the Jacobian matrix at each of the elements integration points (also called Gauss points), and reports the ratio between the smallest and the largest. You can specify a time limit on the attempts to fix the mesh. Note that a low time limit might prove insufficient in a large mesh with many features, wedges, and/or slivers, especially if the mesh is not permitted to deviate from the features (e.g. the "permit moving nodes" options are not checked). Access the Criteria File Editor to change the element quality requirements.
Warpage
Min Interior Angle Max Interior Angle Jacobian
Time Limit (minutes)
Edit Criteria
257

Altair Engineering
Check
Examine the mesh and count the number of bad elements, according to the criteria supplied (Jacobian, Volume Skew, etc.) The results display in the Results: area. Begin the fix process. The mesh is scanned and the program will try to fix as many elements as it can in accordance with the specified settings and criteria. You can abort the fix attempt early by clicking holding down the right-mouse button. Note that there can be a significant delay before HyperMesh finishes its current fix attempts and stops processing.
Fix
Reject
If the results of the fixes are unacceptable, click this to revert the mesh to its pre-fixed state. Note You can only undo one fix operation this way--you cannot "back up" more than one step!
Close
Close the Fix Sliver Tetra Elements tool.
Altair Engineering

258
Abaqus Utility Menu

The following macros are included on the Abaqus page of the Utility Menu when you load the Abaqus user profile.
Utility
Solid Face Alignment Align Faces
Description
Applies to templates: Standard3D, Explicit Determines the default stack or thickness direction for Abaqus composite solid, gasket and continuum shell elements. The Review button opens the HyperMesh element selector panel and allows you to pick solid elements. Selected elements are highlighted. When you click proceed, it highlights the face1 of selected solids and draws an arrow along the default stack (or thickness) direction of selected solids. The Reset button deletes the stack (or thickness) direction arrows. Applies to templates: Explicit Tool that guides you through a workflow of positioning a dummy in a seat. Applies to templates: Standard2D, Standard3D, Explicit Activates the Abaqus Step Manager, which allows you to define Abaqus history (*STEP) information in HyperMesh. Activates the Abaqus Contact Manager, which allows you to create, edit and review the following cards in HyperMesh: *CONTACT *CONTACT DAMPING *CONTACT PAIR *FRICTION *PRE-TENSION SECTION *SHELL TO SOLID COUPLING *SURFACE, TYPE = ELEMENT *SURFACE, TYPE = NODE
Review
Reset Dummy Positioning Process Manager Tools Step Manager
Contact Manager
259

Altair Engineering
Utility
Description
*SURFACE, COMBINE *SURFACE, CROP *SURFACE, TYPE = CUTTING SURFACE *SURFACE, TYPE = CYLINDER, REVOLUTION or SEGMENTS *SURFACE INTERACTION *SURFACE BEHAVIOR *TIE
Altair Engineering

260
Contact Manager
The Abaqus Contact Manager allows you to create, edit and review the following cards in HyperMesh: *CONTACT *CONTACT DAMPING *CONTACT PAIR *FRICTION *PRE-TENSION SECTION *SHELL TO SOLID COUPLING *SURFACE, TYPE = ELEMENT *SURFACE, TYPE = NODE *SURFACE, COMBINE *SURFACE, CROP *SURFACE, TYPE = CUTTING SURFACE *SURFACE, TYPE = CYLINDER, REVOLUTION or SEGMENTS *SURFACE INTERACTION *SURFACE BEHAVIOR *TIE The Abaqus Contact Manager is organized into three main tabs: Interface Surface Surface Interaction
To start the Contact Manager:

1. 2. Load the Abaqus user profile. Click Contact Manager in the Abaqus Utility Menu.
The following rules apply when you are using the Abaqus Contact Manager. When the Contact Manager window is minimized or it is behind the HyperMesh window, restore it by clicking the Contact Manager button in the Abaqus Utility Menu. To display the bubble help for a button, place the cursor over the button for a few moments. Double click on the interface, surface and surface interaction names in the table to open the corresponding edit windows. Right click on the names to display pull-down menu options.
261

Altair Engineering
Table columns can be resized by positioning the cursor along a column border, pressing the left or right mouse button, and dragging the border to a new position. The shift and ctrl keys can be used with a left mouse click to select multiple items in a table. Press ctrl and the left or right arrow key to move the cursor within the active cell. Use the left, right, up and down arrows to change the active cell. Right click on the Review button to clear the review selections. If you create, update or delete components, groups, properties, or entity sets from HyperMesh panels while the Contact Manager is open, click the Sync button to update the Contact Manager with the new changes. In the Friction and Surface Behavior tables, right click in the tables to display a pull-down menu containing copy, cut and paste options. Comma delimited data can be copied, cut, or pasted in these tables. Relevant hot keys, for example, ctrl-c, ctrl-x, and ctrl-v on PC, will also work. In some fields in the Contact Manager, you can access the Entity Browser, which is available via the button. The Entity Browser makes it more convenient to view and sort long lists of components or other entities when selecting them for the field.
Altair Engineering

262
Interface Tab
The Interface tab contains a description of the *CONTACT PAIR, *TIE, *PRE-TENSION SECTION, *CONTACT, and *SHELL TO SOLID COUPLING cards with corresponding surfaces and surface interactions. You can create, edit, review, and delete interfaces from this tab. You can also edit, review, and delete surfaces and surface interactions that are displayed on this tab.
The Interface table contains the following columns: Name The contact interface names. These names are not exported to the Abaqus input file. They are useful for identifying the various interfaces in HyperMesh. The interface types. The currently supported types are contact pair, tie, pre-tension section, general contact, and shell to solid coupling. The names of the slave surfaces in Abaqus Standard (or the first surface in Abaqus Explicit). The names of the master surfaces in Abaqus Standard (or the second surface in Abaqus Explicit). The names of the surface interaction properties. The display on/off check boxes and color change buttons for the surfaces shown in the Slave column. The color can be changed by clicking the color button and selecting a color from the menu. The display on/off check boxes and color change buttons for the surfaces shown in the Master column. The color can be changed by clicking the color button and selecting a color from the menu.
Interface Type
Slave
Master
Surface Interaction Slave display
Master display
263

Altair Engineering
Note: The display on/off check boxes and color change buttons are disabled if the corresponding surface is defined with sets and no displays are created for them. Double click on the interface, surface, and surface interaction names in the table to open the corresponding edit windows. Right click on a name to display menu options. Right click on an interface, surface, and surface interaction name to display menu options. The available options are: - Edit - Delete - Swap Master-Slave - Swap CP-Tie - Review - Review with underlying entity - Reset review - Review Options (Review by Highlighting, Review by Color Change, Transparency, and Grey Color) - Display All - Display None - Display Reverse - Draw Rigid Surfaces The Edit, Review , Delete, Display All, Display None and Display Reverse options work like the corresponding buttons (described below). Review with underlying entity highlights the surface along with the attached elements (or nodes). The Reset review button clears the review selections. Table columns can be resized by positioning the cursor along a column border, pressing the left or right mouse button, and dragging the border to a new position. The shift or ctrl key and a left click can be used to select multiple items in a table.
The Interface tab contains the following buttons: Auto Launches the Auto Contact dialog that allows you to quickly and easily create interactions between several parts of your model. Opens the Create New Interface dialog in which you enter the name and type of the new interface. The Same as: option allows you to create an interface by copying from an existing interface. The Create... button in this dialog creates the interface and opens the corresponding Contact Pair, Tie , Pre-Tension Section or Shell to Solid Coupling dialog.
New ...
Altair Engineering

264
Edit ...
Opens the corresponding dialog for editing the selected interface, surface, or surface interaction. Reviews the selected interface, surface, or surface interaction as follows: For surfaces, the selected surface is highlighted in red in the HyperMesh window. If the surface is defined with sets, the underlying elements are highlighted. A right-click on the Review button clears the review selections. For interface types, corresponding slave and master surfaces are highlighted in red and blue in the HyperMesh window. A right-click on the Review button clears the review selections. For surface interactions, the names of all interfaces using the selected surface interaction in the table are highlighted. There is no graphical review in the HyperMesh window for surface interaction.
Review
Delete
Deletes the selected interfaces, surfaces, or surface interactions. You can delete single or multiple selections from the table. Rename the selected interface, surface, or surface interaction. Updates the Contact Manager with the current HyperMesh database. If you manually create, update, or delete components, groups, properties, or entity sets from HyperMesh panels while the Contact Manager is open, click the Sync button to update the Contact Manager with the new changes. Closes the Contact Manager.
Rename Sync
Close
265

Altair Engineering
Help
Invokes the online help for Abaqus Contact Manager.
See also Contact Pair Pre-Tension Section Tie General Contact Auto Contact Abaqus Contact Manager
Altair Engineering

266
Contact Pair
The Contact Pair dialog allows you to define the *CONTACT PAIR card. Options vary according to the active template. There are two tabs in this dialog. Define Parameter
The Contact Pair dialog contains the following buttons: OK Updates the HyperMesh database with the changes and closes the Contact Pair dialog. Updates the HyperMesh database with the changes without closing the Contact Pair dialog. Closes the Contact Pair dialog without updates.
Apply
Cancel
See also Pre-Tension Section Tie Auto Contact Element Based Surface Node Based Surface
267

Altair Engineering
Surface Combine or Crop Cutting Surface Analytical Rigid Surface Surface Interaction General Contact Abaqus Contact Manager
The Define tab allows you to select the slave surface, master surface, and surface interaction for the *CONTACT PAIR card. You can also review the selected surfaces or create new ones.
The Define Tab contains the following options: Auto-generated surface Select this option for HyperMesh to automatically generate *SURFACE from component cards from a selected component. When this option is selected, the Surface: field becomes a Component: field, and you can select a component from the adjacent drop-down list. Click Slave>> or Master>> to add them to the table of included surfaces as slave or master, respectively. Surface The Surface: field contains a list of the existing surfaces. Select a slave surface from the list or use the button to open the Entity Browser to select a surface.
Altair Engineering

268
Click the Slave>> button to add the surface as a slave to the table of selected surfaces. Click the Master>> button to add the surface as a master. Click Remove>> to remove any selected surface from the table. You can add multiple sets of surfaces to the table. Click the New button to create a new surface. Once you have specified the surface properties, the surface appears in the drop-down list, where you can select it and add it to the table. For a description of defining surfaces, see Element Based Surface or Node Based Surface. The Review button highlights the selected slave surface in red and displays it through solid mesh in performance graphics in the HyperMesh window. If the surface is defined with sets, the underlying elements are highlighted. Right click on Review to clear the review selections. Interaction The Interaction: field contains a list of the existing surface interaction properties. You can select a surface interaction from the list. You can also use the button to open the Entity Browser to select a surface. The New button opens the Create New Surface Interaction dialog for creating a new surface interaction. When the new surface interaction has been defined, the Contact Pair dialog reflects the newly-created surface interaction as the interaction of the contact pair. For a description of defining surface interactions, see Surface Interaction. Note: The surface interaction is optional in explicit template. The Define tab will show a Surface interaction check box if the explicit template is loaded. This option should be checked first if a surface interaction property is intended for the contact pair card.
Note that if you create multiple pairs of contacts, they will appear on the Interface tab in separate entries using the same name.
The Parameter tab allows you to define optional parameters for the contact pair card. Options vary according to the template loaded. The supported parameters are: For Standard.3d/2d template Adjust, Extension Zone , Smooth, Hcrit, Tied, Small sliding and Type . When the Type field is set to SURFACE TO SURFACE, the Geometric Correction field becomes activated. See the Abaqus Online Documentation for a detailed description of these parameters.
269

Altair Engineering
For Explicit template
Mechanical constraint, CPSET, OP, Weight, and Small sliding. See the Abaqus Online Documentation for a detailed description of these parameters.
Altair Engineering

270
Tie
The Tie dialog allows you to define the *TIE card. This dialog contains two tabs: Define Parameter
The Tie dialog contains the following buttons: OK Apply Cancel Updates the HyperMesh database with the changes and closes the Tie dialog. Updates the HyperMesh database with the changes without closing the Tie dialog. Closes the Tie dialog without updates.
See also Contact Pair Pre-Tension Section Auto Contact Element Based Surface Node Based Surface
271

Altair Engineering
Surface Combine or Crop Cutting Surface Analytical Rigid Surface Surface Interaction General Contact Abaqus Contact Manager
The Define tab allows you to select slave surface and master surface for the *TIE card. You can also review the selected surfaces or create new ones.
The Define Tab contains the following options: Auto-generated surface from component Select this option for HyperMesh to automatically generate *SURFACE cards from a selected component. When this option is selected, the Surface: field becomes a Component: field, and you can select a component from the adjacent drop-down list. Click Slave>> or Master>> to add them to the table of included surfaces as slave or master, respectively.
Altair Engineering

272
Select slave surface
Select this option for HyperMesh to automatically generate *SURFACE cards from a selected component. When this option is selected, the Surface: field becomes a Component: field, and you can select a component from the adjacent drop-down list. Click Slave>> or Master>> to add them to the table of included surfaces as slave or master, respectively .
Select master surface
The Surface: field contains a list of the existing surfaces. Select a slave surface from the list or use the button to open the Entity Browser to select a surface. Click the Slave>> button to add the surface as a slave to the table of selected surfaces. Click the Master>> button to add the surface as a master. Click Remove>> to remove any selected surface from the table. You can add multiple sets of surfaces to the table. Click the New button to create a new surface. Once you have specified the surface properties, the surface appears in the drop-down list, where you can select it and add it to the table. For a description of defining surfaces, see Element Based Surface or Node Based Surface. The Review button highlights the selected slave surface in white and displays it through solid mesh in performance graphics in the HyperMesh window. If the surface is defined with sets, the underlying elements are highlighted. Right click on Review to clear the review selections.
Note that if you create multiple pairs of ties, they will appear on the Interface tab in separate entries using the same name.
The Parameter tab allows you to define optional parameters for the *TIE card. Explicit:
273

Altair Engineering
Standard2D/Standard3D:
Altair Engineering

274
The supported parameters are: Position tolerance , Tied nset, Cyclic symmetry (standard only), Constraint ratio, No rotation, Adjust, No Thickness and Type . The Position tolerance and Tied nset are optional mutually exclusive parameters. Select None if you do not want to select either of them. See the Abaqus Online Documentation for detailed descriptions of these parameters. Tied nset Selection The Tied nset menu contains a list of existing node sets. You can select a node set from the list. Review Set button The Review Set button reviews the selected node set by highlighting it in the HyperMesh window. The Create/Edit Set button opens the Entity Sets panel in HyperMesh. When you finish creating/editing the set, click return. The Tie window is updated with the new set displayed in node set list.
Create/Edit Set button
275

Altair Engineering
Pre-Tension Section
The Pre-Tension Section dialog allows you to define the *PRE-TENSION SECTION card. This dialog contains two tabs: Define Parameter
The Pre-Tension Section dialog contains the following buttons: OK Updates the HyperMesh database with the changes and closes the Pre-tension Section dialog. Updates the HyperMesh database with the changes without closing the Pretension Section dialog. Closes the Pre-tension Section dialog without updates.
Apply
Cancel
See also Contact Pair Tie
Altair Engineering

276
Auto Contact Element Based Surface Node Based Surface Surface Combine or Crop Cutting Surface Analytical Rigid Surface Surface Interaction General Contact Abaqus Contact Manager
The Define tab allows you to select the pre-tension node ID and element ID for beam or truss element or the surface for the *PRE-TENSION SECTION card. You can also review the selected surface or create a new one.
The Define tab contains the following options: Pre-tension node Pick Node allows you to pick a node graphically, or you can enter a node number in the text box.
277

Altair Engineering
Review highlights the selected node in the window. Element This option is valid for beam or truss elements only. It is mutually exclusive to the Select surface option. Pick Element allows you to select an element graphically, or you can enter an element number in the text box. Review highlights the selected element in the window. Select surface The Select surface menu contains a list of the existing surfaces. You can select a surface from the list. Review highlights the selected surface in white and displays it through solid mesh in performance graphics in the window. If the surface is defined with sets, the underlying elements are highlighted. Create New opens the Create New Surface dialog for creating a new surface. When the new surface has been defined, the Pre-Tension Section dialog reflects the newly created surface. For a description of defining surfaces, see Element Based Surface or Node Based Surface. Note: Right click on Review to clear the review selections in the graphic area.
The Parameter tab allows you to define optional data lines for the *PRE-TENSION SECTION card.
Altair Engineering

278
Check Dataline to activate all three input boxes for the first, second, and third component of the normal. See the Abaqus Online Documentation for a detailed description of these items. Click the Define by vector button to define the values in the input boxes by a vector. To create a vector, click the Create/Edit vector.. button. Note: The NSET parameter is currently only supported on the card image.
279

Altair Engineering
Shell to Solid Coupling

The Shell to Solid Coupling dialog allows you to define the *SHELL TO SOLID COUPLING card. There are two tabs in this dialog. Define Parameter
The Contact Pair dialog contains the following buttons:
OK Apply Cancel
Updates the database with the changes and closes the dialog. Updates the database with the changes without closing the dialog. Closes the dialog without updates.
The Define tab allows you to select the slave surface, master surface, and surface interaction for the *SHELL TO SOLID COUPLING card. You can also review the selected surfaces or create new ones.
Altair Engineering

280
The Define tab contains the following options: Surface The Surface: field contains a list of the existing surfaces. Select a slave surface from the list or use the button to open the Entity Browser to select a surface. Click the Slave>> button to add the surface as a slave to the table of selected surfaces. Click the Master>> button to add the surface as a master. Click <<Remove to remove any selected surface from the table. You can add multiple sets of surfaces to the table. Click the New button to create a new surface. Once you have specified the surface properties, the surface appears in the drop-down list, where you can select it and add it to the table. For a description of defining surfaces, see Element Based Surface or Node Based Surface. The Review button highlights the selected slave surface in white and displays it through solid mesh in performance graphics in the window. If the surface is defined with sets, the underlying elements are highlighted. Right click on Review to clear the review selections.
Note that if you create multiple pairs of contacts, they will appear on the Interface tab in separate entries using the same name.
281

Altair Engineering
The Parameter tab allows you to define optional parameters for the contact pair card. Options vary according to the template loaded. The supported parameters are: For Standard.3d/2d template and Explicit template INFLUENCE DISTANCE and POSITION TOLERANCE. To add them, enable the checkbox and then add an appropriate value. See the Abaqus Online Documentation for a detailed description of these parameters.
Altair Engineering

282
General Contact
The General Contact option allows you to define the *CONTACT, *CONTACT INCLUSIONS, *CONTACT EXCLUSIONS and *CONTACT PROPERTY ASSIGNMENT. The keywords *SURFACE PROPERTY ASSIGNMENT, *CONTACT FORMULATION, *CONTACT CONTROLS ASSIGNMENT and *SURFACE PROPERTY CONTACT CLEARANCE ASSIGNMENT cards are available for Explicit template only.
Click the Edit... button in the Contact Manager to go into the card editor to define all relevant keywords, parameters and data lines. When you are finished, click return and the Contact Manager window will once again be displayed.
See also Contact Pair Pre-Tension Section Tie Auto Contact Element Based Surface Node Based Surface Surface Combine or Crop Cutting Surface Analytical Rigid Surface Surface Interaction Abaqus Contact Manager
283

Altair Engineering
Auto Contact
The Auto Contact dialog helps you define the *CONTACT PAIR and *TIE keywords along with the corresponding *SURFACE cards. Auto Contact is functionality within the Abaqus user profile that allows you to quickly and easily create interactions between several parts of your model. Based on a proximity distance, Auto Contact will search the model and automatically define surfaces from identified components. The interactions and surfaces are placed into a temporary Auto Contact Browser, where you can review the pairs and make adjustments as needed. Two types of interactions can be created by the auto contact functionality: *CONTACT PAIR: Definition of pairs of surfaces, which can contact or interact during an analysis. When selecting this type of interaction, you must also specify the surface interaction properties. *TIE: Definition of constraints and interactions between pairs of surfaces. No surface interaction definition is required.
The Auto Contact dialog contains the following buttons: Find Cancel Remove Selection icon Searches the model for interacting components. Closes the Contact Pair dialog without updates. Removes selected components from the table. You can use the CTRL and Shift key to select multiple items in the table.
Altair Engineering

284
Review Selection icon
Highlights the selected component in the graphic area. All other components are grayed out. You can use the CTRL and Shift key to select multiple items in the table. Right-click to return the model to normal display.
Help icon
Opens the Auto Contact online help.
See also To Set Up an Auto Contact Run Auto Contact Browser Modifying Auto Contact Entities
1. 2. 3. 4. 5.
Load the Abaqus user profile and select either the 2D or 3D template. Click Contact Manager in the Abaqus Utility Menu. Click Auto. This opens the Auto Contact dialog. Select the type of interface to create in the Type of Interface: field. Click the yellow components button and select your components. The components are automatically placed in the Component table in the Auto Contact dialog.
6.
In the Proximity Distance: field, enter a value. The proximity distance is the maximum distance between two selected components. When you create the pair, any surfaces that are farther away than the value entered here will not be created as a contact pair. The default value is zero.
285

Altair Engineering
7.
In the Maximum reverse angle: field, enter a value. If the angle between two normals of elements or element faces exceeds this value, the element will not be added to the master or slave surface.
8. 9.
If creating a contact pair, select the type of interaction in the Interaction: field. You can use the icon to open a browser to view the options more easily, or you can click New to create a new interaction. Click Find. The status bar activates and the Auto Contact Browser opens.
10. Use the Auto Contact Browser to make any necessary adjustments to the interfaces and surfaces. When finished modifying, click Create. The interfaces and surfaces marked as Accepted are created. The Contact Manager window reopens with the new information listed.
See also Auto Contact Auto Contact Browser Modifying Auto Contact Entities
The Auto Contact Browser provides options for viewing and modifying the contact pairs identified in the Auto Contact process. Naming Convention During creation, a name is assigned to each interface and surface identified. Interface:
Altair Engineering

286
Contact Pair example: CP:(comp name)_(comp_name) Tie example: TIE:(comp name)_(comp_name) Surface: S:(comp name) If more than one surface is selected, the naming convention uses S:(comp name):<index>
The Auto Contact Browser contains the following columns: Name Lists the name of the interfaces, surfaces and surface interactions that were assigned. Underneath the interface name are the temporary surfaces included in that interface. Red indicates a slave surface, and blue indicates a master surface. Accept When the Accept box is checked, the Interface will be included in the creation process. Type of contact pair created. Color assigned to the interaction and surfaces Opens the Auto Contact online help.
Type Color Surface Interaction
The Auto Contact Browser contains the following icons: Options icon This opens the options dialog.
Enter a new feature angle or customize the transparency for a selected entity. Click OK when finished.
287

Altair Engineering
Highlight Elements icon Review Elements icon
Highlights the elements stored in selected entities in the graphics window. You can use the CTRL and Shift key to select multiple items in the table. Review of elements stored in the selected entities. Elements are highlighted by color, all other components are grayed out. You can use the CTRL and Shift key to select multiple items in the table. Review and Highlight are mutually exclusive. It is also possible to switch both options off. This is helpful when working with big models.
Fit View to Elements icon Display All Elements icon Display Components with Elements icon Display Only Elements icon Select Elements Manually icon Add by Adjacent icon
Automatically zooms in to the elements stored in the currently selected items . In combination with the Highlight Elements or the Review Elements option, current contents remain unchanged on the screen. Highlights or reviews the elements referred by an interaction or surfaces and shows the components they belong to. All other components will be masked.
Only elements are highlighted or reviewed. The rest of the component and other components will be masked. Opens the element selection panel so that individual elements can be added/removed manually. Click proceed when finished.
Adds the elements adjacent to the surface to the selected surface. Right-click to undo one time. Adds the adjacent face to the selected surface. Right-click to undo one time. Opens the Auto Contact dialog to recheck the select interfaces. Recheck will either add more contacts to the existing contacts for modify the existing ones. You can select interfaces from the browser, and the GUI will automatically populate the components that the interaction was based on. This helps modify an existing interface.
Add by Face icon
Recheck icon
See also Auto Contact To Set Up an Auto Contact Run Modifying Auto Contact Entities
Altair Engineering

288
Right-clicking on an item in the Auto Contact Browser displays a context sensitive menu which offers options for modifying the surfaces and contact pairs.
Rename Delete Swap Master Slave
Rename an existing entry. Delete items from the browser. Allows you to switch the surfaces identified as master and slave. When selected, you will see the surfaces flip from the master/slave positions in the browser. Select multiple entities by using the CRTL and Shift keys when clicking on entities.
Swap CP - Tie
Allows you to change the type of interface created. Because a surface interaction is required for Contact Pair but not for Tie, any surface interaction identified earlier will be lost upon a swamp from CP to TIE. (If you switch back from TIE to CP, the surface interaction will not be retained.) Allows you to manually edit the faces of the surfaces. This opens the elements selection panel where you can select and deselect the elements to include on the face of the surface. Adds adjacent elements to the selected surface.
Edit Faces
Add by Adjacent Add by Face
Adds all elements to a selected surface, until the feature angle exceeds the value (the feature angle can by set by clicking the Options icon).
Accept All/None Automatically accept or reject all items in the Auto Contact Browser. Reverse Expand All/ Collapse Reverses the current selections in the Accept column. Expands or collapses folders in the Auto Contact Browser.
See also Auto Contact To Set Up an Auto Contact Run Auto Contact Browser
289

Altair Engineering
Surface Tab
The Surface tab contains a description of the *SURFACE cards with corresponding types. You can create, edit, review, and delete surfaces from this tab.
The Surface table contains the following columns: Name Type The name of surfaces in the HyperMesh database. The types of surfaces. Currently supported types are ELEMENT, NODE, and ANALYTICAL RIGID (SEGMENTS, CYLINDER or REVOLUTION). The display on/off check boxes and color change buttons for the surface. The color of a surface can be changed by clicking on the color buttons and selecting a color from the menu.
Display
Note: The display on/off check boxes and color change buttons are disabled if the corresponding surface is defined with sets and a display is not created. Double click on a surface name in the table to open its corresponding editing dialogs. Right click on a surface name to display menu options. The available options are - Edit - Delete - Review - Review with underlying entity
Altair Engineering

290
- Reset review - Review Options (Review by Highlighting, Review by Color Change, Transparency, and Grey Color) - Display All - Display None - Display Reverse - Draw Rigid Surfaces The Edit, Review , Delete, Display All, Display None and Display Reverse options work like the corresponding buttons (described below). Review with underlying entity highlights the surface along with the attached elements (or nodes). The Reset review button clears the review selections. Table columns can be resized by positioning the cursor along a column border, pressing the left or right mouse button, and dragging the border to a new position. The shift or ctrl key and a left click can be used to select multiple items in a table.
The Surface tab contains the following buttons: Auto Launches the Auto Contact dialog that allows you to quickly and easily create interactions between several parts of your model. Opens the Create New Surface dialog, on which you enter the name and type of the new surface. The Create button in this dialog creates the surface and opens the corresponding Element Based Surface , Node Based Surface , or Analytical Rigid Surface dialog or takes you to the corresponding HyperMesh card image.
New ...
291

Altair Engineering
Edit ...
Opens the Element Based Surface , Node Based Surface , or Analytical Rigid Surface dialog or takes you to the corresponding HyperMesh card image for editing the selected surface. Reviews the selected surface. Surfaces are highlighted in white and show up through solid mesh in performance graphics the window. If the surface is defined with sets (display option disabled), the underlying elements are highlighted. Right-click the Review button to clear the review selections. Deletes selected surfaces. You can delete single or multiple selections from the Surface table. Rename the selected surface. Updates the Contact Manager with the current HyperMesh database. If you manually create, update or delete components, groups, properties, or entity sets from HyperMesh panels while the Contact Manager is open, click Sync to update the Contact Manager with the new changes. Closes the Contact Manager. Displays all surfaces in the graphic area. Hides all surfaces in the graphic area. Displays all unchecked surfaces and hides all checked surfaces in the graphic area.
Review
Delete
Rename Sync
Close Display All Display None Display Reverse
Altair Engineering

292
Draw Rigid Surfaces
Shows analytical rigid surfaces in the graphic area.
See also Element Based Surface Node Based Surface Surface Combine or Crop Cutting Surface Analytical Rigid Surface Abaqus Contact Manager
293

Altair Engineering
Element Based Surface

The Element Based Surface dialog allows you to define and edit the *SURFACE, TYPE = ELEMENT card. There are four tabs in this dialog: Define Adjust Normal Delete Face Optional Parameters
The Element Based Surface dialog contains the following buttons: Surface color Review Changes the color of the current surface in the display. Reviews the current surface by highlighting in white and displaying it through solid mesh in performance graphics in the window. If the surface is defined with sets, the underlying elements are highlighted. Right click on the Review button to clear the review selections. Updates the HyperMesh database with the optional parameters specified and closes the Element Based Surface window.
Close
See also Contact Pair Pre-Tension Section Tie General Contact
Altair Engineering

294
Auto Contact Node Based Surface Surface Combine or Crop Cutting Surface Analytical Rigid Surface Surface Interaction Abaqus Contact Manager
The Define tab allows you to define surfaces for solid, shell, membrane, rigid, gasket, beam, pipe, or truss elements. You can also define the surface by specifying the face identifier for an element set. There are six available surface definition options for various element types: 3D solid, gasket 3D shell, membrane, rigid 3D solid coated with shell 3D shell - edge based 2D solid, axisymmetric, gasket Beam, pipe, truss Element set The layout of the Define tab changes, based on your selection (displayed in blue). Some options may be disabled depending on the current template.
The 3D solid or gasket elements option allows you to define the *SURFACE card by specifying face identifiers for individual solid and gasket elements. These faces are displayed by special face elements. In order to create surface, you need to select the underlying solid or gasket elements first. The Elements buttons opens the element selector panel and allows you to pick the underlying 3-D solid or gasket elements from the graphic area. Selected elements are highlighted. The corresponding Reset resets the selected elements. After that, you can define the face identifiers for the selected solids in two ways: (a) by creating a solid skin and manually picking the faces from the skin, (b) by picking nodes on a specific face and sweeping through a break angle. Select Solid skin option for (a) and Nodes on face option for (b) from the Select faces by: radio buttons.
295

Altair Engineering
(a) Solid skin option has the following buttons : Faces Creates a temporary skin of the selected solids, opens the element selector panel, and allows you to pick face elements from this skin. The selected faces are highlighted. The corresponding Reset button resets the selected faces and deletes the skin. Note : by face on the element selector panel can be used to find all faces within a feature angle of the selected face. The feature angle setting can be accessed by clicking the Preferences menu and selecting Geometry Options.
The skin will initially have the same color as the current surface. You can change the skin color using Solid skin color: button. Add Adds the selected faces to the current surface and creates special face elements for display. It also checks for duplicate faces and displays a message if any are found. Note: The Delete Face tab contains tools to find and delete duplicate faces in the current surface.
Reject
Rejects the recently added faces.
Altair Engineering

296
(b) Nodes on face option has the following buttons: Nodes Opens the node selector panel and allows you to pick nodes from the graphic area. Three nodes (or two corner nodes) from the same solid element must be picked to define a face of that solid. The selected nodes are highlighted. The corresponding Reset button resets the selected nodes . Note : Several three-node or two-corner-node sets can be selected at the same time to define faces in different solids.
Add
Finds all faces from the selected solids that fall within a specified break angle of the face(s) defined by nodes. These faces are then added to the current surface and creates special face elements for display. It also checks for duplicate faces and displays a message if any are found. Note : The Delete Face tab contains tools to find and delete duplicate faces in the current surface.
Reject
See also 3-D Shell, Membrane, or Rigid Elements 3-D Solid Coated with Shell 3-D Shell - Edge Based 2-D Solid, Axisymmetric, or Gasket Elements Beam, Pipe, or Truss Elements Element Set Element Based Surface: Define Tab
297

Altair Engineering
The 3D shell, membrane , or rigid elements option allows you to define the *SURFACE card by specifying face identifiers for individual shell, membrane, and rigid elements. In HyperMesh graphics, these faces are displayed by special face elements. These face elements have their own normals to define the SPOS and SNEG faces. The face with normals along the underlying element normals define the SPOS faces. In contrast, the face with opposing normals define the SNEG face.
The 3D shell, membrane, or rigid elements option has the following buttons: Elements Opens the element selector panel and allows you to pick the underlying 3-D shell, membrane, or rigid elements from the graphic area. The selected elements are highlighted and their normals are displayed. The corresponding Reset button resets the selected elements and hides the normals. Adds the selected elements to the current surface and creates special face elements for display. It also checks for duplicate faces and displays a message if any are found. By default, SPOS faces are created. In order to create SNEG faces, activate the Reverse check box and click Add. Note: The Delete Face tab contains tools to find and delete duplicate faces in the current surface.
Add
Reject
See also 3-D Solid or Gasket 3-D Solid Coated with Shell 3-D Shell - Edge Based 2-D Solid, Axisymmetric, or Gasket Elements
Altair Engineering

298
Beam, Pipe, or Truss Elements Element Set Element Based Surface: Define Tab
In HyperMesh, surfaces on 3-D solid or gasket elements that are coated with shell, membrane, or rigid elements are treated differently from surfaces on regular solids. The 3D solid coated with shell option allows you to define the *SURFACE card by specifying face identifiers for these 3-D solid or gasket elements. The faces are displayed by special contactsurface elements. Unlike, regular solids, there is only one way to define the face identifiers for solids with shell coating: by picking nodes on a specific face and sweeping through a break angle. Therefore, the Nodes on face option is always selected. This option is valid for Standard.3D template or 3-D models in Explicit template only.
The 3D solid coated with shell option has the following buttons: Elements Opens the element selector panel and allows you to pick the underlying 3-D solid and gasket elements from the graphic area. The selected elements are highlighted. The corresponding Reset button resets the selected elements. Opens the node selector panel and allows you to pick nodes from the graphic area. Three nodes (or two corner nodes) from the same solid element must be picked to define a face of that solid. The selected nodes are highlighted. The corresponding Reset button resets the selected nodes. Note: Several three-node or two-corner-node sets can be selected at the same time to define faces in different elements.
Nodes
Add
Finds all faces from the selected 3-D solids that fall within a specified break angle of the face(s) defined by nodes. These faces are then added to the current surface and special contactsurface elements are created for display. Note: You cannot add duplicate contactsurfaces for the same element in HyperMesh. Therefore, the Add button does not check for duplicates
299

Altair Engineering
and there is no Reject button.
See also 3-D Solid or Gasket 3-D Shell, Membrane, or Rigid Elements 3-D Shell - Edge Based 2-D Solid, Axisymmetric, or Gasket Elements Beam, Pipe, or Truss Elements Element set Element Based Surface: Define Tab
The 3D shell edge based option allows you to define the *SURFACE card by specifying edge identifiers for 3-D shell elements. The edges are displayed by special contactsurface elements. Face identifiers for solids with shell coating are defined by picking nodes on a specific edge and sweeping through a break angle. Therefore, the Nodes on edge option is always selected.
The 3D shell edge based option has the following buttons: Elements Opens the element selector panel and allows you to pick the underlying 3-D shell elements from the graphic area. The selected elements are highlighted. The corresponding Reset button resets the selected elements. Opens the node selector panel and allows you to pick nodes from the graphic area. Two nodes from the same solid element must be picked to define a edge of that shell. The selected nodes are highlighted. The corresponding Reset button resets the selected nodes.
Nodes
Altair Engineering

300
Note:
Several two-node sets can be selected at the same time to define edges in different elements.
Add
Finds all edges from the selected 3-D shells that fall within a specified break angle of the edge(s) defined by nodes. These edges are then added to the current surface and special contactsurface elements are created for display. Note: You cannot add duplicate contactsurfaces for the same element in HyperMesh. Therefore, the Add button does not check for duplicates and there is no Reject button.
See also 3-D Solid or Gasket 3-D Shell, Membrane, or Rigid Elements 3-D Solid Coated with Shell 2-D Solid, Axisymmetric, or Gasket Elements Beam, Pipe, or Truss Elements Element Set Element Based Surface: Define Tab
The 2D solid, axisymmetric, or gasket elements option is valid for Standard.2D template or 2-D models in Explicit template only. It allows you to define the *SURFACE card by specifying edge identifiers for individual 2-D solid, axisymmetric, and gasket elements. In the graphic area, these edges are displayed by special contactsurface edge elements. Unlike, 3-D solids, there is only one way to define the face identifiers for 2D solids: by picking nodes on a specific edge and sweeping through a break angle. Therefore, the Nodes on edge option is always selected.
301

Altair Engineering
The 2D solid, axisymmetric, or gasket elements option has the following buttons: Elements Opens the element selector panel and allows you to pick the underlying 2-D solid, axisymmetric, and gasket elements from the graphic area. The selected elements are highlighted. The corresponding Reset button resets the selected elements. Opens the node selector panel and allows you to pick nodes from the graphic area. Two nodes from the same element must be picked to define an edge of that element. The selected nodes are highlighted. The corresponding Reset button resets the selected nodes . Note: Several node pairs can be selected at the same time to define edges in different element.
Nodes
Add
Finds all edges from the selected 2-D solids that fall within a specified break angle of the edge(s) defined by nodes. These edges are then added to the current surface and special contactsurface edge elements are created for display. Note: You cannot add duplicate contactsurface edges for the same element in HyperMesh. Therefore, the Add button does not check for duplicates and there is no Reject button.
See also 3-D Solid or Gasket 3-D Shell, Membrane, or Rigid Elements 3-D solid coated with shell 3-D Shell - Edge Based Beam, Pipe, or Truss Elements Element Set Element Based Surface: Define Tab
The Beam, pipe, or truss elements option allows you to define the *SURFACE card for individual beam, pipe and truss elements. In the graphic area, these faces are displayed by special contactsurface elements. These contactsurface elements have their own normals to define the SPOS and SNEG faces. The contactsurface with normals along the underlying element normals define the SPOS faces. In contrast, the face with opposing normals defines the SNEG face. Note: For 3-D beam, pipe and truss elements, the SPOS and SNEG faces do not have any meaning. Therefore, these face identifiers will be ignored by the Standard.3d template.
Altair Engineering

302
The Beam, pipe, or truss elements option has the following buttons: Elements Opens the element selector panel and allows you to pick the underlying beam, pipe or truss elements from the graphic area. The selected elements are highlighted. The corresponding Reset button resets the selected elements. Adds the selected elements to the current surface and creates special contactsurface elements for display. By default, SPOS faces are created. In order to create SNEG faces, activate the Reverse check box and click Add. Note : You can not add duplicate contactsurfaces for the same element in HyperMesh. The Add button does not check for duplicates and there is no Reject button.
Add
See also 3-D Solid or Gasket 3-D Shell, Membrane, or Rigid Elements 3-D solid coated with shell 3-D Shell - Edge Based 2-D Solid, Axisymmetric, or Gasket Elements Element Set Element Based Surface: Define Tab
The Element set option allows you to define the *SURFACE card for element sets. HyperMesh allows only one elset in a surface. It does not support a combination of elsets and individual elements in the same *SURFACE data line.
303

Altair Engineering
The Element set: menu contains a list of the existing elsets. (You can also use the button to open the Entity Browser to select an elset.) There are two types of elsets in Hypermesh: Components and Entity sets. The Abaqus elsets that are linked to sectional property cards (such as *SOLID SECTION, *SHELL SECTION, etc.) become components in HyperMesh. Others become entity sets. To differentiate between these two types, there is a divider line "- - - - -" in the elset lists that pops up if you click the Element set: menu. The elsets listed below the divider line are components.
The Element set option has the following buttons: Review Set Reviews the selected elsets set by highlighting them in the the graphic area. Right click on the Review button to clear the review selections.
Create/Edit Sets... Opens the Entity Sets panel. When you finish creating/editing the set, click return. The Element Based Surface tab is updated with the new set appearing in the element set list. Show Faces Creates a temporary skin of the selected elset, opens the element selector panel, and allows you to pick face elements from this skin. When you return from the element selector panel, the selected faces will display color coded face identifier tags. In the graphic area, these tags are sometimes blocked by the solid mesh. You may need to rotate the model a little to view the tags. Adds the selected elset into the current surface. By default, HyperMesh does not create a display for surfaces defined with elsets. However, if you check the Display option before clicking Update , it creates a special display using contactsurface elements. Note: The special display created with contactsurface elements does not have links to the elset in the HyperMesh database. Therefore, if you edit the elset later on, the display will not automatically reflect your changes. In this case, check the Display option and click Update again.
Update
After selecting an element set, click the arrow keys to move the set into table on the right. Once an elset
Altair Engineering

304
has been added to the table, the face column becomes activated and you can manually define the appropriate face identifier for the selected elset. Select None if you do not want to define a face identifier for the set. In this case, Abaqus will create a surface with the free faces for the selected element set.
See also 3-D Solid or Gasket 3-D Shell, Membrane, or Rigid Elements 3-D solid coated with shell 3-D Shell - Edge Based 2-D Solid, Axisymmetric, or Gasket Elements Beam, Pipe or Truss Elements Element Based Surface: Define Tab
The Adjust Normal tab allows you to display and reverse normal direction for surfaces defined on 3-D shell, membrane, rigid and 2-D beam, pipe, and truss elements. For these elements, the normal directions are used to define the SPOS or SNEG face identifiers. In HyperMesh, surfaces can be displayed in two ways: by special face elements or by contactsurfaces. The surfaces defined on 3-D shell, membrane, rigid elements are displayed by face elements while surfaces on 2-D beam, pipe, and truss elements are displayed by contactsurfaces. The normal directions of the contactsurfaces are part of their display. However, the normal directions of the faces have to be turned on for displaying. Use the Display normals checkbox to display the normals of the faces. Use the Size: entry box to define the size of the normals before selecting the Display normals checkbox. Note: 3D solid and gasket elements are also displayed by face elements. But, the normal direction do not have any meaning for them.
There are two options for reversing normals: (a) Reverse all normals at a time, (b) Reverse normals by individual faces or contactsurfaces.
305

Altair Engineering
(a) Reverse normals: All option has the following buttons: Reverse Reverses normals of all faces for 3-D shell, membrane, rigid elements and all contactsurfaces for 2-D beam, pipe, truss elements in the current surface. Note: The normals of the underlying elements are not reversed. It reverses the normals of the faces or contactsurfaces only.
(b) Reverse normals: By element option has the following buttons: Element faces Opens the element selector panel. For 3-D shell, membrane, rigid elements, pick the faces (not the underlying elements). However, for 2-D beam, pipe, truss elements, pick the elements themselves as the contactsurfaces can not be picked from the graphic area. The corresponding Reset button resets the selected elements. Reverses normals of the selected faces for 3-D shell, membrane, rigid elements and contactsurfaces of the selected 2-D beam, pipe, truss elements. Note: The normals of the underlying elements are not reversed. It reverses the normals of the faces or contactsurfaces only.
Reverse
See also Element Based Surface: Define Tab Element Based Surface: Delete Face Tab Element Based Surface: Optional Parameters Tab
Surfaces can be displayed in two ways: by special face elements or by contactsurfaces. The surfaces defined on 3-D solid, gasket, shell, membrane, rigid elements are displayed by face elements while surfaces on 2-D solid, axisymmetric, gasket and all beam, pipe, truss elements are displayed by contactsurfaces. The Delete Face tab allows you to delete faces or contactsurface from all elements types. It contains tools to find and delete duplicate faces for 3-D solid, gasket, shell, membrane, or rigid elements. There are three options for deletion: (a) All, or (b) By element, and (c) Duplicate faces.
Altair Engineering

306
(a) All option has the following buttons: Delete Deletes all the faces or contactsurfaces in the current surface.
(b) By element option has the following buttons: Element Faces Opens the element selector panel. For 3-D solid, gasket, shell, membrane, and rigid elements, pick the faces (not the underlying elements). However, for 2-D solid, axisymmetric, gasket or all beam, pipe, truss elements, pick the elements themselves as the contactsurfaces can not be picked from the graphic area. The corresponding Reset button resets the selected elements. Deletes the selected faces or contactsurfaces from the selected 2-D solid, axisymmetric, gasket, beam, pipe, truss elements.
Delete
(c) Duplicate faces option has the following buttons: Find Duplicate Faces Finds duplicate faces, if any exists, for the current surface and highlights them in the graphic area. The status bar shows the number of duplicates found. The corresponding Reset button resets the selected elements. Deletes the highlighted duplicate faces found. Note: Duplicate contactsurfaces cannot be added to the same
Delete
307

Altair Engineering
surface in HyperMesh. Therefore, Duplicate Faces is only valid for 3-D solid, gasket, shell, membrane, and rigid elements.
See also Element Based Surface: Define Tab Element Based Surface: Adjust Normal Tab Element Based Surface: Optional Parameters Tab
The Optional Parameters tab allows you to define optional parameters for the *SURFACE card. The supported parameters are: Standard.3D/2D template: Trimming of open free surface Explicit template: Max ratio, Scale thick ness, Region type for adoptive meshing, No offset and No thick ness . See the Abaqus Online Documentation for a detailed description of these parameters. Click on the Update button to activate the Optional Parameters selection in the HyperMesh database.
Altair Engineering

308
Node Based Surface

The Node Based Surface dialog allows you to define and edit the *SURFACE, TYPE = NODE card. There are three tabs in this window: Define Delete Surface Node Optional Parameters
The Node Based Surface dialog contains the following buttons: Surface color Changes the color of the current surface in the graphic area. Review Reviews the current surface by highlighting it in white and displays it through solid mesh in the graphic area. If the surface is defined with sets, the underlying nodes are highlighted. Right click on the Review button to clear the review selections. Updates the HyperMesh database with the optional parameters specified and closes the Node Based Surface window.
Close
See also Contact Pair Pre-Tension Section Tie General Contact Auto Contact
309

Altair Engineering
Element Based Surface Surface Combine or Crop Cutting Surface Analytical Rigid Surface Surface Interaction Abaqus Contact Manager
The Define tab allows you to define surfaces with individual nodes. You can also define the surface by specifying a node set. There are two available surface definition options: Individual nodes Node set The layout of the Define tab changes based on your selections.
See also Node Based Surface: Delete Surface Node Tab Node Based Surface: Optional Parameters Tab Node Based Surface
The Individual nodes option allows you to define the *SURFACE, TYPE = NODE card by specifying individual node IDs. In the graphic area, these nodes are displayed by special single node elements with a SurfaceNodes tag.
Altair Engineering

310
The Individual nodes option has the following buttons: Pick Nodes Opens the node selector panel and allows you to pick nodes the graphic area. The selected nodes will be highlighted. The corresponding Reset button resets the selected nodes. Adds the selected nodes to the current surface and creates special single node SurfaceNodes elements for display. The Add button does not check for duplicates and there is no Reject button.
Add
See also Node Set Node Based Surface: Define tab
This option allows you to define the *SURFACE, TYPE = NODE card for node sets. HyperMesh allows only one node set in a surface. It does not support combination of node sets and individual nodes in the same *SURFACE data line.
The Node set: menu contains a list of the existing node sets. The Node set option has the following buttons: Review Set Reviews the selected node sets by highlighting the nodes in the graphic area. Right-click on the Review button to clear the review selections. Opens the Entity Sets panel. When you finish creating/editing the set, click return. The Node Based Surface dialog is updated with the new set
Create/Edit Set...
311

Altair Engineering
appearing in the node set list. Area This check box allows you to define the optional cross-sectional area at each nodes of the node set selected. Note: In HyperMesh, the cross-sectional area data item is supported only for surfaces defined by node sets.
Update
Adds the selected node set into the current surface. HyperMesh does not create a display for surfaces defined with node sets.
Node bases surfaces are displayed by special single node SurfaceNode elements. The Delete Surface Node tab allows you to delete the SurfaceNode elements. There are two options for deletion: (a) All, (b) By node.
(a) All option has the following buttons: Delete Deletes all SurfaceNodes elements from the current surface.
(b) By node option has the following buttons: Surface nodes Opens the element selector panel for you to select SurfaceNodes elements from the graphic area. The corresponding Reset button resets the selected elements.
Altair Engineering

312
Delete
Deletes the selected SurfaceNodes elements from the current surface
See also Node Based Surface: Define Tab Node Based Surface: Optional Parameters Tab Node Based Surface
The Optional Parameter tab allows you to define optional parameters for the *SURFACE card. The supported parameters are: Standard.3D/2D template: Trim Explicit template: Max ratio, Scale thick ness, Region type, No offset and No thick ness . See the Abaqus Online Documentation for a detailed description of these parameters. Click on the Update button to activate the optional parameter selection in the HyperMesh database.
See also Node Based Surface: Define Tab Node Based Surface: Delete Surface Node Tab Node Based Surface
313

Altair Engineering
Surface Combine or Crop

The Surface Combine or Crop option allows you to define the *SURFACE, COMBINE, or CROP. The current version of Contact Manager does not have a Tcl/Tk dialog to define the surface combine or crop. Review by highlighting or color change also does not work for these types of surfaces in HyperMesh. Instead, it takes you to the corresponding card image panel for edit or review. Click the edit button to go into the card editor to define all relevant keywords, parameters, and data lines. When you are finished, click return and the Contact Manager window will once again be displayed.
See also Contact Pair Pre-Tension Section Tie General Contact Auto Contact Element Based Surface Node Based Surface Cutting Surface Analytical Rigid Surface Surface Interaction Abaqus Contact Manager
Altair Engineering

314
Cutting Surface
The Cutting Surface option allows you to define the *SURFACE, TYPE = CUTTING SURFACE. The current version of Contact Manager does not have a Tcl/Tk dialog to define the cutting surface. Review by highlighting or color change also does not work for these types of surfaces in the graphic area. Instead, it takes you to the corresponding card image panel for edit or review. Click the edit button to go into the card editor to define all relevant keywords, parameters, and data lines. When you are finished, click return and the Contact Manager window will once again be displayed.
See also Contact Pair Pre-Tension Section Tie General Contact Auto Contact Element Based Surface Node Based Surface Surface Combine or Crop Analytical Rigid Surface Surface Interaction Abaqus Contact Manager
315

Altair Engineering
Analytical Rigid Surface

The Analytical Rigid Surface option helps you define the *SURFACE, TYPE = CYLINDER, REVOLUTION or SEGMENTS card. When you select this option and click Create the Analytical Rigid Surface dialog appears. There are four tabs in this dialog: Define Adjust Normal Rigid Body Optional Parameters
Each tab of the Analytical Rigid Surface dialog contains the following buttons: Surface color Review Changes the color of the current surface in the display. Reviews the current surface by highlighting line segments and generated revolute or swept surfaces in white. Right-click on the Review button to clear the review selections. Updates the HyperMesh database with the optional parameters that you
Close
Altair Engineering

316
specified and closes the Analytical Rigid Surface window.
See also Contact Pair Pre-Tension Section Tie General Contact Auto Contact Element Based Surface Node Based Surface Surface Combine or Crop Cutting Surface Surface Interaction Abaqus Contact Manager
Specify the main characteristics of the surface on this tab. Depending on which Abaqus template you have loaded (Standard3D, Standard2D, or Explicit), you can create surfaces defined by segments, cylinders, or revolutions. The Standard3D template enables you to define rigid surfaces of type REVOLUTION and CYLINDER. The Standard2D template enables you to define surfaces of type SEGMENTS. The Explicit template enables you to define all three types: REVOLUTION, CYLINDER, and SEGMENTS. You can define the line segments in three different ways by picking nodes, by picking existing lines, or by manually entering the coordinate values. The options on the Define tab vary according to the type selected. Refer to the following topics for details: SEGMENTS CYLINDER REVOLUTION
See also Analytical Rigid Surface Abaqus Contact Manager
317

Altair Engineering
Analytical rigid surface of type SEGMENTS
Select the following options on the Define tab for planar rigid surfaces:
Plane definition
Plane/axis: Abaqus does not require the plane/axis definition for SEGMENTS type. In HyperMesh, however, the XY plane must be used for a 2D model. Therefore, the XY plane is selected by default. If the model is not in the XY plane, you can choose to select a "User Defined" plane on which the rigid surface should be defined. If you choose to manually define the plane/axis, you must enter values for three points (the origin, x axis, and y axis) that define the local coordinate system. You can also use the following buttons to automatically define the plane in the Local System table: Pick System... Click to select an existing system from the model. Once you select a plane from the model and click proceed, the values are populated in the table. Click to create new coordinate systems using the Systems panel.
Create/Edit System...
Altair Engineering

318
Line definition
No. of line segment In this field you specify the number of datalines needed to define the line datalines segments. The actual number of line segments is one less than this number. Start by typing the number of datalines needed to define the line segments and click the Set button. The corresponding number of rows appears in the Line Type table below. In this table, specify the coordinates of the ends of each line segment. The first entry in the table is always the START node. This value specifies the beginning point of the first segment. The subsequent segments starting point is always the end point of the previous segment, or the START node if the segment is the first in the definition. For each line type, select a type from the Line Type column: LINE, CIRCL, or PARAB. Each selection activates the appropriate number of columns for the segment definition. The segments can be circles, parabolas, or lines. Enter data in the columns as described below: Lines are defined with the x and y coordinates of the end point in the two active columns. For circles, specify the x and y coordinate of the end point in the first two columns and then, define the x and y coordinate of the center in the last two columns. For parabolas, specify the x and y coordinate of the mid point in the first two columns and then, define the x and y coordinate of the end point in the last two columns. You can also pick nodes or lines from existing geometry using the following buttons: Pick Nodes Click to pick nodes from the HyperMesh model for selected line segments. When you click proceed, the coordinate values of the selected nodes will appear in selected line segment cells. In addition, temporary line segments (white color) will also be drawn in the graphic area from the picked nodes. Ensure that you select two nodes in the correct order for circles and parabolas. Use this option to define line segments from existing lines in HyperMesh. These lines must be single curvature, connected and node1 of a line must be same as node2 of the previous line. Click to pick a line from the HyperMesh model. When you click proceed, the coordinate values and line types for the selected lines will appear in the table. Note: In HyperMesh, the sequence of node1 and node2 for lines can be visualized from the Line Edit/Extend Line panel.
Pick Lines
319

Altair Engineering
Click the Update button to update the HyperMesh database with your settings.
See also CYLINDER Option REVOLUTION Option Analytical Rigid Surface Abaqus Contact Manager
Analytical rigid surface of type CYLINDER
Select the following options on the Define tab for cylindrical rigid surfaces:
Plane definition
Plane/axis: Choose User Defined if you want to create or select the system, or choose XY, YZ, or XZ to define it in the respective plane.
Altair Engineering

320
If you choose to manually define the plane/axis, you must enter values for three points (the origin, x axis, and generator axis) that define the local plane on which the line segments will be defined. You can also use the following buttons to define the plane: Pick System... Click to select an existing system from the model. Once you select a system from the graphic area and click proceed, the values are populated in the table. Click to create a new coordinate system using the Systems panel.
Line definition
No. of line segment datalines In this field you specify the number of datalines needed to define the line segments. The actual number of line segments is one less than this number. Start by typing the number of segment datalines to define the surface and click the Set button. The corresponding number of rows appears in the Line Type table below. In this table, specify the coordinates of the ends of each line segment. The first entry in the table is always the START node. This value specifies the beginning point of the first segment. The subsequent segments starting point is always the end point of the previous segment, or the START node if the segment is the first in the definition. For each line type, select a type from the Line Type column: LINE, CIRCL, or PARAB. Each selection activates the appropriate number of columns for the segment definition. The segments can be circles, parabolas, or lines. Enter data in the columns as described below: Lines are defined with the local x- and local y-coordinates of the end point in the two active columns. For circles, specify the local-x and local-y coordinate of the end point in the first two columns and then, define the local-x and local-y coordinate of the center in the last two columns. . For parabolas, specify the local-x and local-y coordinate of the mid point in the first two columns and then, define the local-x and local-y coordinate of the end point in the last two columns. Note: The local x- and local y-coordinates must be relative to the plane defined in the Plane/axis table.
You can also pick nodes or lines from existing geometry using the following buttons:
321

Altair Engineering
Pick Nodes
Click to pick nodes from the HyperMesh model for selected line segments. When you click proceed, the coordinate values of the selected nodes in terms of the defined plane will appear in selected line segment cells. In addition, temporary line segments (white color) will also be drawn in the graphic area from the picked nodes. Ensure that you select two nodes in the correct order for circles and parabolas. Use this option to define line segments from existing lines in HyperMesh. These lines must be single curvature, connected and node1 of a line must be same as the node2 of the previous line. Click to pick a line from the HyperMesh model. When you click proceed, the coordinate values relative to the defined plane and line types for the selected lines will appear in the table. Note: In HyperMesh, the sequence of node1 and node2 for lines can be visualized from the Line Edit/Extend Line panel.
Pick Lines
Sweep Distance
Abaqus does not need the sweep distance. The CYLINDER type surfaces are swept to infinity in Abaqus. However, in HyperMesh, you must define a sweeping distance to draw the three-dimensional surface. Select the Sweep distance check box to specify a sweep distance and type a value in the adjacent box. Select the Both directions check box to sweep in opposite directions along the generator vector.
See also SEGMENTS Option REVOLUTION Option Analytical Rigid Surface Abaqus Contact Manager
Altair Engineering

322
Analytical rigid surface of type REVOLUTION
Select the following options on the Define tab for rigid surfaces of revolution:
Plane definition
Plane/axis: Choose User Defined if you want to create or select the revolution axis, or choose X, Y, or Z to define it in the respective axis. If you choose to manually define the axis, you must enter values for two points (the origin and the z axis). Abaqus does not need the x axis values because any plane that passes through the z axis will define the same revolute surface. However, HyperMesh requires the definition of the x (or radial) axis to define the plane on which the line segments are drawn. You can also use the following buttons to automatically define the axis of revolution and x (radial) axis. Note: The coordinate values to define the x axis change if you pick a node (or line) from HyperMesh as the START node. Click to select an existing system from the model. Once you select a system from the graphic area and click proceed, the values are populated in the table.
Pick System...
323

Altair Engineering
Click to create a new coordinate system using the Systems panel.
Line definition
No. of segment datalines: In this field you specify the number of datalines needed to define the line segments. The actual number of line segments is one less than this number. Start by typing the number of line segment datalines to define the surface and click the Set button. The corresponding number of rows appears in the Line Type table below. In this table, specify the coordinates of the ends of each line segment. The first entry in the table is always the START node. This value specifies the beginning point of the first segment. The subsequent segments starting point is always the end point of the previous segment, or the START node if the segment is the first in the definition. For each line type, select a type from the Line Type column: LINE, CIRCL, or PARAB. Each selection activates the appropriate number of columns for the segment definition. The segments can be circles, parabolas, or lines. Enter data in the columns as described below: Lines are defined with the local-x (or r) and local-y (or z ) coordinates of the end point in the two active columns. For circles, specify the local-x (or r) and local-y (or z ) coordinate of the end point in the first two columns and then, define the local-x (or r) and local-y (or z ) coordinate of the center in the last two columns. For parabolas, specify the local-x (or r) and local-y (or z ) coordinate of the mid point in the first two columns and then, define the local-x and local-y (or z ) coordinate of the end point in the last two columns. You can also pick nodes or lines from existing geometry using the following buttons: Pick Nodes Click to pick nodes from the HyperMesh model for selected line segments. When you click proceed, the coordinate values of the selected nodes relative to the defined plane will appear in selected line segment cells. In addition, temporary line segments (white color) will also be drawn in the graphic area from the picked nodes. Ensure that you select two nodes in the correct order for circles and parabolas. Click to pick a line from the HyperMesh model. When you click proceed, the coordinate values in terms of the defined
Pick Lines
Altair Engineering

324
plane and line types for the selected lines will appear in the table. Note: The sequence of node1 and node2 for lines can be visualized from the Line Edit /Extend Line panel.
Revolution angle:
Abaqus does not need the revolution angle. The REVOLUTION type surfaces are revolved around 360 degrees in Abaqus. However, in HyperMesh, you must define a revolution angle to draw the three-dimensional surface. Select the Revolution angle check box to specify the angle of revolution and type a value in the adjacent box.
See also SEGMENTS Option CYLINDER Option Analytical Rigid Surface Abaqus Contact Manager
Select the following options on the Adjust Normal tab: Display normals Select the Display normals check box to show the normals on the display. Specify a length for the normals in the Size field. To change the size, toggle the check box to update the display. Select one of the radio buttons to reverse the direction of the normals. You can only choose to reverse the normals of all line segments in this type of surface. Click the Reverse button to do this. When reversed, all coordinates and sequence of all the line segments will be updated. The analytical rigid surface should be oriented so that the outward normals point toward any body of contact.
Reverse normals:
325

Altair Engineering
An analytical rigid surface must have a *RIGID BODY card with a reference node associated with it. When you create a new rigid surface in the Contact Manager, an empty *RIGID BODY component is created automatically. You can also associate the surface to an existing *RIGID BODY component or create a new one from this tab. This tab also includes several options related to preparing the model for visualization in HyperView. HyperView currently does not support geometrical entities like analytical rigid surfaces. If you mesh analytical rigid surfaces with rigid elements that point to the same *RIGID BODY card, these elements would not participate in the analysis; they would move with the reference node as a rigid body. These rigid elements would act like a "display body" in Abaqus, and would be imported in HyperView.
Altair Engineering

326
Select the following options on the Rigid Body tab: Select a *Rigid Body: Use the drop-down list or the Entity Browser to select a rigid body. You can also create a new rigid body by clicking the Create New button. Type the node ID used as a reference to define the rigid body motion. Click Pick Node to pick a node from the model. Alternatively, type a node value in the box and click Review to view the location of the node in the model. (If you type a value that does not exist in the model, nothing is highlighted.) Specify the density of the line mesh. Uniform uses the value you specify as the mesh density for each line segment. Variable brings you to the Line Mesh panel to create the mesh. Select either Uniform or Variable and click Mesh to create the line mesh. Sweep distance/ Sweep angle: The sweep field differs depending on whether the surface is of type CYLINDER or REVOLUTION. If the surface is cylindrical, the field is Sweep distance . Type a value for the distance of the sweep of the mesh. Select the Both direction check box to extend the sweep in both directions for the specified distance. When the Both direction check box is selected, the number of layers refers to the depth of segments in the sweep (number of layers of elements).
Reference Node:
Line mesh density:
327

Altair Engineering
If the surface is a revolution, the field is Sweep angle . Type a value for the angle of the revolution. In the No. of layers field, type the value of how many segments the rim of the revolution should be divided into.
See also Analytical Rigid Surface Abaqus Contact Manager Automesh panel
Select the following options on the Optional Parameters tab: Trimming of open free surface Select to specify open free surface trimming. Then click the adjacent button to select whether to trim. Select to adjust the thicknesses for surface facets in which the thickness to minimum edge or diagonal length ratio exceeds the specified value. Then type an adjustment value in the adjacent field. Select to scale all of the surface facets by a single factor. Then type the scaling factor in the adjacent field.
Max ratio
Scale thickness
Altair Engineering

328
Region type for adaptive meshing
For surfaces defined on the boundary of an adaptive mesh domain, select to create a boundary region for the surfaces. Click the adjacent button to select the type of region. Select for the surface to ignore midplane offsets. Select for the surface to ignore thicknesses. Do not select this option if the surface will be double-sided or a self-contact surface. Select to define a radius of curvature to smooth discontinuities between segments. Then type a length in the adjacent field.
No offset No thickness
Fillet radius
329

Altair Engineering
Surface Interaction Tab

The Surface Interaction tab contains a description of the *SURFACE INTERACTION cards. You can create, edit, review, and delete surface interactions from this tab.
The Surface Interaction table contains the following column: Name The name of the surface interaction cards in the HyperMesh database.
Note: Double click on a surface interaction name in the table to open the corresponding Surface Interaction dialog. Right click on a name to display an option menu. Table columns can be resized by positioning the cursor along a column border, pressing the left or right mouse button, and dragging the border to a new position. The shift or ctrl key and a left click can be used to select multiple items in a table.
The Surface Interaction tab contains the following buttons: Auto Launches the Auto Contact dialog that allows you to quickly and easily create interactions between several parts of your model. Opens the Create New Surface Interaction dialog in which you enter the name of the new surface interaction. The Create.. button in this dialog creates the surface interaction and opens the corresponding Surface Interaction dialog.
New...
Altair Engineering

330
Edit ...
Opens the Surface Interaction dialog for editing the selected surface interaction. Not active on this tab. Deletes single or multiple surface interactions from the Surface Interaction table. Rename the selected surface interaction. Updates the Contact Manager with the current HyperMesh database. If you manually create, update, or delete components, groups, properties, or entity sets from HyperMesh panels while the Contact Manager is open, click Sync to update the Contact Manager with the new changes. Closes the Contact Manager.
Review Delete
Rename Sync
Close
See also Surface Interaction Abaqus Contact Manager
331

Altair Engineering
Surface Interaction
The Surface Interaction dialog allows you to define the *SURFACE INTERACTION card with corresponding *FRICTION, *SURFACE BEHAVIOR, *CONTACT DAMPING cards. This dialog contains the following tabs: Define Surface Behavior Contact Damping Friction
The Surface Interaction dialog contains the following buttons: OK Updates the HyperMesh database with the changes and closes the Surface Interaction window. Updates the HyperMesh database with the changes without closing the Surface Interaction window. Closes the Surface Interaction window without any update.
Apply
Cancel
Altair Engineering

332
See also Contact Pair Pre-Tension Section Tie General Contact Auto Contact Element Based Surface Node Based Surface Surface Combine or Crop Cutting Surface Analytical Rigid Surface Abaqus Contact Manager
The Define tab allows you to select the surface interaction properties. The available options are: Surface behavior, Contact damping, and Friction. Once you select an interaction property, its corresponding tab will be activated. You can also define optional parameters (Pad thickness) and data lines (out-of-plane thickness for 2-D model or cross-sectional area at every nodes for node based surface). See the Abaqus Online Documentation for a detailed description of these parameters.
333

Altair Engineering
The Surface Behavior tab allows you to create *SURFACE BEHAVIOR cards with optional parameters and corresponding data lines. The supported optional parameters are: No separation and Pressure overclosure. Options vary according to the selection made in the Pressure overclosure drop down.
Altair Engineering

334
Five types of pressure-overclosure are supported: Hard In the 2D/3D template, selecting this option provides four new radio buttons: Augmented lagrange , Direct, Penalty, and None . If Penalty is selected, select whether the penalty is linear or nonlinear and enter the corresponding information in the fields that appear. In the Explicit template, there are no data lines needed for this option. Exponential There are three fields to define the data line for this option. They are: Clearance at zero contact pressure , Pressure at zero clearance and Direct (for 2D/3D templates only) or maximum stiffness (for explicit only). There are two fields to define the data line for this option. They are Direct (for 2D/3D templates only) and Slope of the pressure-overclosure curve . There is a table available for defining the data line values for this option. You need to input the number of data lines required at the Number of data lines entry box. Clicking the corresponding Set button will update the table to have the specified number of rows. For inputting values in the table, click on a cell to make it active and write down the values from keyboard. The table works like a regular spread sheet. You can also read comma delimited data from a text file by clicking Read from file . This button opens a file browser window. Select the file and click Open to export the comma delimited data. The row number is set to the number of data
Linear
Tabular
335

Altair Engineering
lines found in the file. Note: Right click in the table to display a pull-down menu containing copy, cut and paste options. Comma delimited data can be copied/cut into or pasted from the clipboard using these options. Hot keys, for example, Ctrl-c, Ctrl-x and Ctrl-v on PC, can also be used. Left click in a cell to activate the cell. Click in an active cell to move the insertion cursor to the character nearest the mouse. The shift and ctrl keys can be used with a left mouse click to select multiple items in a table. Press ctrl and the left or right arrow key to move the cursor within the active cell. Use the left, right, up and down arrows to change the active cell. Press Backspace to delete the character before the insertion cursor in the active cell. If multiple cells are selected, Backspace deletes all selected cells. Press Delete to delete the character after the insertion cursor in the active cell. If multiple cells are selected, Delete deletes all selected cells. Table columns can be resized by positioning the cursor along a column border, pressing the left or right mouse button, and dragging the border to a new position. Scale Factor Modify the default contact stiffness by a scale factors. Available only in the Explicit user profile. Refer to the Abaqus Online Documentation for a detailed description of these parameters.
The Contact Damping tab allows you to create *CONTACT DAMPING cards with corresponding parameters and data lines. The supported parameters are: Definition and Tangent fraction (explicit only). The two definition types supported are: Damping coefficient and Critical damping fraction (explicit only). The data item entry options change based on the current template. See the Abaqus Online Documentation for a detailed description of these parameters.
Altair Engineering

336
The Friction tab allows you to create *FRICTION cards with corresponding parameters and data lines. The supported friction types (mutually exclusive parameters) are: Default (Coulomb), Elastic slip, Slip tolerance , Lagrange multiplier, and Rough. Depending on the template loaded and friction type selected, the window layout changes to show only the relevant options for defining other parameters and data items. Other supported optional parameters are: Exponential decay, Test data , Anisotropic, Taumax , and Dependencies. See the Abaqus documentation for detailed descriptions of these parameters. Note: The friction type User is not supported in the Contact Manager. However, it is supported in HyperMesh in the *SURFACE INTERACTION card image.
337

Altair Engineering
For all friction types (except Rough), there are four options to define the friction coefficient: Direct This is the default method for defining the friction coefficient. Selecting this option means that the Exponential decay and Anisotropic parameters will not be written in the input file. The No of Dependencies check box and corresponding entry box should be used to define the Dependencies parameter. There is a table available for defining the corresponding data lines. The available data items are: Friction coefficient, Slip rate , Contact pressure , Average temperature at the contact point, and average field variable values. The column numbers in the table will change based on the setting for No of Dependencies. The row numbers can be defined at the No of data lines entry box. Click Set to update the table to reflect the specified number of rows. To enter values in the table, click on a cell to make it active and write down the
Altair Engineering

338
values from keyboard. The table works like a regular spread sheet. You can also read comma delimited data from a text file by clicking Read From a File . This button opens a file browser. Select the file and click Open to export the comma delimited data. The row number will be set to the number of data lines found in the file. Anisotropic This option allows you to define the data lines for the Anisotropic parameter. The No of Dependencies check box and corresponding entry box should be used to define the Dependencies parameter. There is a table available for defining the corresponding data lines. The available data items are: Friction coefficient1 (first slip direction), Friction coefficient2 (second slip direction), Slip rate , Contact pressure , Average temperature at the contact point, and average field variable values. The column numbers in the table will change based on the setting for No of Dependencies. The row numbers can be defined at the No of data lines entry box. Click Set to update the table to reflect the specified number of rows. To enter values in the table, click on a cell to make it active and write down the values from keyboard. The table functions like a regular spread sheet. You can also read comma delimited data from a text file by clicking Read From a File . This button opens a file browser. Select the file and click Open to export the comma delimited data. The row number will be set to the number of data lines found in the file. Exponential decay This option allows you to define the data lines for the Exponential decay parameter. The available data items are: Static friction coefficient, Kinetic friction coefficient, and decay coefficient. Exponential decay, test data This option allows you to define the data lines for the Exponential decay, test data parameter. The available data items are: Friction coefficient at point 1 (first data line), Friction coefficient at point 2 (second data line), Slip rate at point 2 (second data line) and Kinematic friction coefficient (optional third data line).
Note: Using the Direct and Anisotropic tables: Right click in the table to display a pull-down menu containing copy, cut and paste options. Comma delimited data can be copied/cut into or pasted from the clipboard using these options. Hot keys, for example, Ctrl-c, Ctrl-x and Ctrl-v on PC, can also be used. Left click in a cell to activate the cell. Click in an active cell to move the insertion cursor to the character nearest the mouse. The shift and ctrl keys can be used with a left mouse click to select multiple items in a table. Press ctrl and the left or right arrow key to move the cursor within the active cell. Use the left, right, up and down arrows to change the active cell
339

Altair Engineering
Press Backspace to delete the character before the insertion cursor in the active cell. If multiple cells are selected, Backspace deletes all selected cells. Press Delete to delete the character after the insertion cursor in the active cell. If multiple cells are selected, Delete deletes all selected cells. Table columns can be resized by positioning the cursor along a column border, pressing the left or right mouse button, and dragging the border to a new position.
Altair Engineering

340
Dummy Positioning Process Manager

The Dummy Positioning Process Manager is a tool that guides you through a workflow of positioning a dummy in a seat. The recommended steps include an interactive positioning process, during which you specify the H-point position of the dummy, as well as the rotation angles of each joint (arm, leg, etc.). When finished with this phase, youll be able to store a transformation file which can later be applied on the dummy only in the next phase, the automatic positioning process. In this phase, you can choose to export only the nodes, which creates a copy of the original dummy file with the updated nodes. The rest of the dummy input file remains unchanged with this option. In the ProcessManager tab, you will see the workflow process. As you complete the positioning process, the boxes will become filled with green checkmarks to indicate the completion of each step. The H-Point subpanel allows you to position the dummy to the H-Point or rotate the entire dummy about the H-Point. For positioning, you can specify either the coordinates or a node for the new H-Point. For rotating, specify the axis of rotation and the angle. In either case, picking any component in the dummy is sufficient. The incremental subpanel allows you to rotate an assembly about the coordinate system specified in the tree structure. In this panel, you have an option to rotate about the child or the parent system. The min stop and max stop angles for the x, y, z, axis associated with the joint are retrieved from the dummy database. When the minimum and maximum angles are reached, the assembly is not allowed to rotate any further. Note : Do not use the Rotate panel in the Tools panel to rotate the dummy. Doing so corrupts the tree structure and produces incorrect results when you reposition the dummy.
Process: 1. 2. 3. 4. 5. In the Abaqus Explicit template, open the Utility Menu and click the button PositioningProcess. Click Create/Open to start a new ProcessManager instance. In the panel area, select the Interactive positioning radio button and select Apply. Click the file browser icon to browse for the dummy input file (*.inp) to open. In the Positioner filename field, browse for the *.pos file to load. When both files are established, click the Load button. You can change the default settings for the import options as needed. Default settings include using free format import and preserving include files upon import. The Import Process Message dialog box may appear. If it does, click Close the dialog and continue the process. If you are intending to exchange only the nodal coordinates of the dummy file at the end of the process, eventually reported unsupported cards do not require action in this case.
Note:
6.
In the next panel, use the browse button to select the non-dummy files, such as the seat. If you have more than one file to load, click the Add button to display more fields. Click Load to load the file(s).
341

Altair Engineering
Use the Load File icon to brow se for the file to open
7.
After the files are loaded, click on the H-point subpanel and position the dummy in the H-Point using the fields available. Click the comps button and select the dummy graphically. Enter the coordinates to position the model and rotate as needed. Once the dummy is positioned in the H-point, click on the Incremental subpanel. Make your changes and click return. In the next panel, you can visualize the stop angles (lower/upper/current) for the elements used in the dummy. Click the Show Plot button to display the plot in the graphics area. Click Next to move to the next panel.
8. 9.
10. The transformation file is now created. This is needed to automatically position the dummy later when no other file (such as the seat) is loaded. In the field, enter a name and folder location and click Create. 11. In the Create documentation panel, you can create an HTML report that lists the document angles and positions of the dummy, as well as screen shots of the model. Enter a name and location for the HTML document and click Create. 12. In the ExportFiles steps, select whether to export the model or save it as an HM file. You can also choose to skip this task and export the dummy later, during the automatic process. Click Export to export the model, or click Next to skip the step. 13. The AutomaticPositioning phase now begins. In this panel, the files entered at the beginning of the InteractivePositioning process are already filled in the fields. Click Load to load the files into HyperMesh. Click OK to delete the current model. Note: The Import Process Message dialog box may appear. If it does, click Close the dialog and continue the process. If you are intending to exchange only the nodal coordinates of the dummy file at the end of the process, eventually reported unsupported cards do not require action in this case.
14. The Transformation filename is automatically loaded in the panel. Click Execute. 15. Similarly to the InteractivePositioning phase, you can create an HTML document with the model specifics. Click Create, or click Next to skip the documentation task. 16. The last task is to export the dummy solver format or create a HyperMesh file. If exporting in solver format, the recommended setting is to select exchange only nodes. This will copy the original dummy file to a new one that uses a name you specified, and will exchange the node positions. Youll find a comment in front of and after the node block to highlight the exchanged nodes. The comments are: ** Begin replaced node block by dummy positioning tool ** End replaced node block by dummy positioning tool" The ProcessManager tree should now be completed, with each task showing a green checkmark.
Altair Engineering

342
Solid Face Alignment Utility

The Solid Face Alignment utility uses the face1 to face2 direction to determine the default stack or thickness direction for Abaqus composite solid, gasket and continuum shell elements. This tool allows enables you to align the face1 of selected solid elements (hexa and penta) to match with a planar face. As a result, the default stack (or thickness) directions for all selected elements become normal to a plane. In addition, you can review the face1 and default stack (or thickness) direction of selected solids. The utility has three buttons: Align Faces The Align Faces button opens the element selector panel and allows you to pick solid elements. Selected elements are highlighted. When you click proceed, it creates a temporary skin of the selected solids and allows you to pick face elements from this skin. The selected faces are highlighted. When you click proceed, the face1 of all selected solid elements will match with the selected face element and a review of the stack (or thickness) direction will be shown. The Review button opens the element selector panel and allows you to pick solid elements. Selected elements are highlighted. When you click proceed, it highlights the face1 of selected solids and draws an arrow along the default stack (or thickness) direction of selected solids. The Reset button deletes the stack (or thickness) direction arrows.
Review
Reset
See also Abaqus Utility Menu
343

Altair Engineering
Step Manager
The Abaqus Step Manager is a graphical interface that allows you to define Abaqus history keywords. The Abaqus Step Manager is accessed by loading the Abaqus user profile and clicking the Step Manager button on the Abaqus Utility Menu. The process that allows you to create, edit, and review the following keywords in HyperMesh begins in the Step tab:
*STEP Analysis types: *BUCKLE *DYNAMIC *FREQUENCY *HEAT TRANSFER *MODAL DYNAMIC *STATIC *STEADY STATE DYNAMICS Loads: *BOUNDARY *CLOAD *DLOAD *DSLOAD *FILM *CFILM *SFILM *TEMPERATURE *INERTIA RELIEF *INITIAL CONDITIONS {TYPE=TEMPERATURE, VELOCITY}
Altair Engineering

344
Output requests: *OUTPUT *NODE OUTPUT *ELEMENT OUTPUT *STEP OUTPUT *ENERGY OUTPUT *NODE FILE *EL FILE *STEP FILE *ENERGY FILE *NODE PRINT *EL PRINT *STEP PRINT *ENERGY PRINT Interface controls: *MODEL CHANGE *CONTACT INTERFERENCE *CHANGE FRICTION *CLEARANCE *CONTACT CONTROLS Others: *MONITOR *FILE FORMAT *PRINT *RESTART
345

Altair Engineering
See also Abaqus Step Manager Step Tab Abaqus Step Manager: Load Step Dialog HM-4340: Pre-Processing for Bracket and Cradle Analysis using Abaqus
Altair Engineering

346
Step Manager Dialog Environment

The following procedures are used to navigate through the Step Manager dialogs: When the Step Manager window is minimized or it is behind the HyperMesh window, restore it by clicking the Step Manager button in the Abaqus Utility Menu. Double click on a cell entry to open the corresponding editing window. The first row contains a list of all initial condition (or model) load collectors. Double click on an Initial Condition name to open the corresponding dialog for defining initial condition loads. Right click on a table to display menu options. Examples of options are Display: all, Display: none, Display: reverse, Text review , Review Load collectors, Reset review, Review Options, Reorder, Export: all, and Export: none . The Text review and Review load collectors options work like the Text and Review buttons, respectively (see Abaqus Step Manager: Load Step Dialog). The Reset review option clears the highlighted selections. Table columns can be resized by positioning the cursor along a column border, pressing the left or right mouse button, and dragging the border to a new position. The shift or ctrl key combined with a left click can be used to select multiple items in a table. To display bubble help, place the cursor over a button for a few moments. Press ctrl and the left or right arrow key to move the cursor within the active cell. Use the left, right, up, and down arrows to change the active cell. Right click on the Review button to clear the highlighted selections. If you create, update or delete steps, load collectors, output blocks, components, groups, properties, or entity sets from panels while the Step Manager is open, click the Sync button to update the Step Manager with the new changes. In some fields in the Step Manager, you can access the Entity Browser, which is available via the button. The Entity Browser makes it more convenient to view and sort long lists of components or other entities when selecting them for the field.
347

Altair Engineering
Entity Browser
Use the Entity Browser to easily sort and select an entity for a field on a dialog. The Entity Browser is available through the button and lists the entities of the relevant type for the selection.
The entities are listed in a tree view. To select an entity, highlight it in the list and click OK. Use the buttons on the dialog to sort the list to more easily view the choices when there are many entities in the list. The buttons perform the following actions: Filter Type text in the adjacent field and click Filter to show only the entities with names that contain the text. You can use the wildcard character (*) to specify that the text can appear anywhere within the entity name. To clear the results and show all entities, right-click the Filter button. Highlights the selected entity in the model. Lists the entities in alphabetical order. Click again to reverse the order. Selects an entity for the field on the dialog. Closes the Entity Browser without making a selection.
Review Sort OK Cancel
Altair Engineering

348
Step Manager Tab Environment

Editable cells have a white background, unless it is the active cell. You can input values using the keyboard in editable cells. Non-editable cells have a gray background. Left click in an editable (white background) cell to activate it for input. Click in an active cell to move the insertion cursor to the character nearest the mouse. Press ctrl and the left or right arrow key to move the cursor within the active cell. Use the left, right, up, and down arrows to change the active cell. Press Backspace to delete the character before the insertion cursor in the active cell. Press Delete to delete the character after the insertion cursor in the active cell. Table columns can be resized by positioning the cursor along a column border, pressing the left or right mouse button, and dragging the border to a new position. In some fields, you can use the button to open the Entity Browser to select the entity for that field.
349

Altair Engineering
Abaqus Step Manager Step Tab

The Abaqus Step Manager opens when you load the Abaqus user profile and click Step Manager on the Abaqus Utility Menu. The Step Manager window is organized into two tabs: Step and Load Case. The Step tab contains the descriptions of existing load steps with the corresponding analysis types, load collectors, output requests, and interface controls. You can create, edit, review, rename, reorder, and delete load steps from this tab as well as set the export and display status of the load steps.
See Step Manager Dialog Environment for tips on navigating through the dialogs. The Step table contains the following columns: Export The export status of the load step. If the export status is on, the load step is written to the input file when exported from HyperMesh. If the export status is off, the STEP is not exported to the input file. The name of the load step. The analysis type of the load step.
Name Analysis Type
Load Collector The list of load collectors in the load step. Output Block Interface Controls The list of output blocks in the load step. The list of interface controls in the load step. Interface Controls defines the following Abaqus keywords: Contact Pair, Surface Interaction, Contact, Contact Controls, Clearance, Contact Interference, Model Change, Change Friction, and Controls. Turns the load step display on/off.
Display
The Step tab contains the following buttons:
Altair Engineering

350
New...
Opens the Create New Step dialog. Enter the name of the new load step in the Name: text box and click Create to create the load step and open the corresponding Load Step editing dialog. The Same as: option allows you to create a new load step by copying from an existing load step.
Edit... Review
Opens the load step editing dialog for the selected load step. Reviews the selected load collectors. All loads in the load collectors are highlighted in the graphic area. The highlighted loads show through the solid mesh in performance graphics. If a load is defined with set, the underlying nodes or elements are highlighted. Right-click Review to clear the highlighted selections. Reviews the selected load step in a text window. Opens the Rename panel for renaming load steps, load collectors, output blocks, or various interface controls. When you finish renaming, click return to update the Step Manager with the new names. Deletes the selected load steps. Updates the Step Manager with the current HyperMesh database. If you manually create, update, or delete load steps, load collectors, output blocks, groups, or entity sets from panels while the Step Manager is open, click Sync to update the Step Manager with the new changes. Closes the Step Manager. Moves the selected load steps up one row.
Text Rename
Delete Sync
Close
Moves the selected load steps down one row.
See also
351

Altair Engineering
Abaqus Step Manager Load Case Tab Abaqus Step Manager: Load Step Dialog Abaqus Step Manager Overview HM-4340: Pre-Processing for Bracket and Cradle Analysis using Abaqus
Altair Engineering

352
Abaqus Step Manager: Load Step Dialog

The Load Step dialog allows you to define the *STEP-*END STEP block as well as the associated Abaqus history keywords. To open this dialog, double-click on the load step name in the Name: column on the Step tab or select the load step from the Name: column and click Edit.... Options vary according to the active template. There are three vertical sections in this dialog. left-most section Contains a tree structure with various Abaqus history options. Selecting an option from the tree changes the dialog layout. Contains the corresponding collectors in a table and relevant buttons to create, review, organize, reorder, rename, or delete these collectors. All loads must be organized into load collectors and all output requests must be under output blocks. When you select a load type, output request type, or interface control from the tree, the load collector table, output block table, or interfaces table is displayed in the middle section. Contains the various tabs and options to define, edit, review, or delete the currently selected tree item. If the tree item needs to be organized in a collector (such as a load or output request), a collector must be selected from the middle section.
middle section
right-most section
The Load Step dialog contains the following general buttons: Review Reviews all load collectors in the current load step. All loads in the load collectors are highlighted in the graphic area. The highlighted loads show through the solid mesh in performance graphics. If a load is defined with set, the underlying nodes or
353

Altair Engineering
elements are highlighted. Right-click on the Review button to clear the highlighted selections. Text... Synchronize Reviews the current load step in a text window Updates the Step Manager with the current HyperMesh database. If you manually create, update, or delete load steps, load collectors, output blocks, groups, or entity sets from panels while the Step Manager is open, click Synchronize to update the Step Manager with the new changes. Closes the Load Step window and opens the Step Manager window.
Close
The following options are available on the Load Step dialog tree: Load Step Title Parameter Analysis procedure Load collector Boundary Concentrated loads CLOAD CFILM Distributed loads DLOAD FILM Surface loads DSLOAD SFILM Temperature Inertia Relief Interface controls Contact Pair Surface Interaction General Contact Contact Controls Clearance
Altair Engineering

354
Contact Interference Model Change Change Friction Controls Output requests ODB file Result file (.fil) Data file (.dat) Monitor Print File Format File Output Restart write Unsupported cards
See also Load Collector Table Abaqus Step Manager Step Tab Abaqus Step Manager Overview HM-4340: Pre-Processing for Bracket and Cradle Analysis using Abaqus
Each load or constraint must belong to a load collector. Therefore, when you select load types from the tree, the load collector table appears in the middle section of the Load Step dialog. The Load collector table contains a list of the load collectors with their corresponding display, color, and history status. You can create, edit, review, rename, reorder, and delete load collectors from this table. You can also organize (copy or move) loads into load collectors and edit the load labels here.
355

Altair Engineering
The Load collector table contains the following columns: Status The history status of the load collector. If the status is on, the load collector belongs to the current load step. This means, all loads in the load collector will be written under the current *STEP block. If the status is off, no loads from the load collector will be written under the current *STEP block. The name of the load collector. The load collector names are for internal use only. The Abaqus input file does not need them. The display on/off check boxes and color change buttons for the load collector. The color can be changed by clicking the color button and selecting a color from the menu.
Name
Display
Click on a load collector name to set it as the current load collector. All loads created from this point are placed into the selected load collector. The Load Type: status bar (below the load collector table) shows all the load types present in the selected load collector. In addition, these load types are highlighted with bold font in the tree. See Step Manager Dialog Environment for tips on navigating through the dialogs. The Load collector table contains the following buttons: New... Opens the Create Load Collector dialog in which you enter the name of the new load collector. The Same as: option allows you to create a load collector by copying attributes (except loads created from panels) from an existing load collector. The Create button in this dialog creates the load collector and adds it to the current load step.
Altair Engineering

356
Review
Reviews the selected load collector. All loads in the load collector are highlighted in the graphic area. The highlighted loads show through the solid mesh in performance graphics. If a load is defined with set, the underlying nodes or elements are highlighted. Right click on the Review button to clear the highlighted selections. Opens the Organize panel where you can copy/move loads into different load collectors. When you have finished, click return to update the Step Manager with the new organization. Opens the corresponding panel where you can turn on/off load labels or update the label size. Opens the Delete panel where you can delete load collectors. When you are finished, click return to update the Load collector table.
Organize...
Label...
Delete
See also Abaqus Step Manager: Load Step Dialog Abaqus Step Manager Overview
The Title option in the tree allows you to define a one line title or sub-heading for the load step. This line appears under the *STEP keyword in the input file. The title is also used in the ODB file to identify the step. Check the Step Heading option to input the title and click Update to update the HyperMesh database.
See also
357

Altair Engineering
Abaqus Step Manager: Load Step Dialog Abaqus Step Manager Overview
The Parameter option in the tree allows you to define the parameters of the *STEP card. The supported parameters are: Name, Amplitude, Extrapolation, Unsymmetric, Increment, Nlgeom, and Perturbation See the Abaqus online documentation for a detailed description of these parameters. Click Update to activate the parameters defined in the HyperMesh database.
The Analysis procedure option in the tree allows you to define the analysis type of the load step. The following analysis types with the corresponding parameters and data lines are supported: Analysis types: Parameter:
Altair Engineering

358
*FREQUENCY
PROPERTY EVALUATION, EIGENSOLVER = {SUBSPACE, LANCZOS, AMS}, NORMALIZATION = {MASS, DISPLACEMENT}, RESIDUAL MODES, ACOUSTIC COUPLING, NUMBER INTERVAL, BIAS, USER BOUNDARIES EIGENSOLVER = {SUBSPACE, LANCZOS}
*BUCKLE
*DYNAMIC (Standard) *DYNAMIC (Explicit)
HAFTOL, DIRECT, DIRECT=NO STOP, SUBSPACE, ADIABATIC, ALPHA, INITIAL, NOHAF EXPLICIT, SCALE FACTOR, ADIABATIC FIXED TIME INCREMENTATION, DIRECT USER CONTROL, ELEMENT BY ELEMENT IMPROVED DT METHOD = YES or NO
*HEAT TRANSFER
DELTMX, END = {PERIOD, SS}, STEADY STATE, MXDEM
*MODAL DYNAMIC
CONTINUE = YES or NO
*STATIC
ADIABATIC, FULLY PLASTIC, RIKS, STABALIZE, DIRECT, DIRECT=NO STOP, FACTOR, LONG TERM DIRECT, SUBSPACE PROJECTION = {ALL FREQUENCIES, CONSTANT, EIGENFREQUENCY, PROPERTY CHANGE}, FREQUENCY SCALE, INTERVAL, REAL ONLY, DAMPING CHANGE, STIFFNESS CHANGE
*STEADY STATE DYNAMICS
There are two tabs for each analysis type: Parameter and Dataline . The layout of the tabs change, based on the analysis types selected.
359

Altair Engineering
See the Abaqus online documentation for a detailed description of these parameters. Click Update to activate the optional parameter or data item selection in the HyperMesh database.
The Boundary dialog allows you to define and edit the *BOUNDARY card. To open this dialog, select Boundary from the tree and a load collector from the Load collector table. The Boundary dialog contains three tabs: Define Delete Parameter
See also Abaqus Step Manager: Load Step Dialog Load Collector Dialog Abaqus Step Manager Overview
The Define tab allows you to define *BOUNDARY cards on individual nodes or geometry (surfaces, points, lines). You can also define the boundary on node sets. There are five different types of boundary conditions
Altair Engineering

360
available: Boundary types Abaqus keyword
Default (disp)
*BOUNDARY
Velocity
*BOUNDARY, TYPE = VELOCITY
Acceleration
*BOUNDARY, TYPE = ACCELERATION
Temperature
*BOUNDARY on dof 11
Electric potential
*BOUNDARY on dof 9
It is recommended that you use only one boundary type per load collector in HyperMesh. If you need to use multiple boundary types in the same STEP, define each type in a separate load collector and add them to the same load step. You can define a *BOUNDARY card on nodes/geometry or on node sets. For Define Boundary on:, the following options are available: Nodes or geometry Node sets
The layout of the Define tab changes, based on your selection.
See also
361

Altair Engineering
Load Step: Boundary
The Define Boundary on: Nodes or geometry option allows you to define various types of boundaries on individual nodes or geometry. Boundaries created on nodes have a special graphical display in HyperMesh. Loads created on geometric entities like surfaces, lines or points are automatically mapped to FEA mesh on export. You can also map them using the Map Loads on Geometry button.
The Define tab for Define Boundary on: Nodes or geometry has the following buttons: Define from 'Constraints' panels Opens the Constraints panel to create/update boundary conditions. To create a boundary on nodes, go to the create sub-panel, select the nodes button, pick the desired nodes from HyperMesh graphics, check the constrained degrees of freedoms, and click create. To create a boundary on geometry, go to the create sub-panel, select surfs, points, or lines using the switch, pick the desired geometry from the HyperMesh graphics, check the constrained degrees of freedom , and click create. Notes: Loads created on geometric entities are automatically mapped to FEA mesh on export. You can also map them using the Map Loads on Geometry button. An existing boundary can be updated from the update sub-panel. While you are in the constraints panel, press the h key to view panelspecific help. When you are finished creating or updating boundary conditions, click return to update Step Manager with the new loads.
Altair Engineering

362
Map Loads on Opens the HyperMesh loads on geom panel to map loads on geometry to FEA Geometry mesh entities. Click Map loads to map all geometric loads in the current load collector to FEA entities. Note: You can also pick other load collectors by clicking the loadcols button and map loads in all of them together. While you are in the loads on geom panel, press the h key to view panelspecific help. When you are finished, click return to update Step Manager with the new loads.
See also Load Step: Boundary: Define Tab
The Define Boundary on: Node sets option defines various types of boundaries on node sets. The node set names are used in the *BOUNDARY data lines instead of the individual nodes. Unlike Abaqus surfaces in HyperMesh, you can combine node sets with individual node IDs in the same *BOUNDARY card. Note : HyperMesh does not graphically display loads created on sets. Therefore, when you review a load collector in the Step Manager, only loads created on individual entities are highlighted. For loads defined on sets, the underlying nodes or elements are highlighted.
This dialog contains a Node sets menu with a list of the existing node sets. It also has a table for data line input containing the following columns:
363

Altair Engineering
Nset
The name of the node sets. Node sets can only be added or deleted from this column using the or buttons, respectively.
1st dof
The first degree of freedom. You can input any integer or any of the following types in this column: XSYMM, YSYMM, ZSYMM, ENCASTRE, PINNED, XASYMM, YASYMM, ZASYMM, NOWARP, NOOVAL, NODEFORM
Last dof Magnitude Load Id
The last degree of freedom. The magnitude. The ID of the load collector
The Define tab for Define Boundary on: Node sets contains the following buttons: Review Set Reviews the selected node sets by highlighting them in the HyperMesh graphics. Right-click the Review button to clear the review selections. Opens the entity sets panel in HyperMesh. When you finish creating/editing the set, click return. The Step Manager is updated with the new set appearing in the node set list. Add the selected node set from the pull down menu to the data line table on the right. Delete the selected node set from the data line table. Review Reviews the selected node set in the data line table. Right-click Review to clear the highlighted selections. Updates the HyperMesh database with the data lines defined in the table. By default, HyperMesh does not create a display for loads defined with sets. Opens the appropriate HyperMesh panel. Use the Review button to expand the loads and constraints on the sets for visualization purposes.
Create/Edit Set
Update
Display/Review from panel
For tips on entering information and navigating in the Define tab, see Step Manager Tab Environment.
See also Load Step: Boundary: Define Tab
Altair Engineering

364
The Delete tab allows you to delete boundaries and other loads from HyperMesh. There are three options: All loads in current collector The Delete button deletes all the loads from the current load collector. The Delete button deletes only *BOUNDARY loads from the current load collector. The Pick Loads button opens the HyperMesh load selector panel. Pick the loads you want to delete and click proceed. The corresponding Reset button resets the selected loads. The Delete button deletes the selected loads.
All 'Boundary' in current collector
By selection
See also Load Step: Boundary
The Parameter tab allows you to define optional parameters for the *BOUNDARY card. The supported parameters are:
365

Altair Engineering
Amplitude, OP, Load Case, Fixed, and Region Type See the Abaqus online documentation for a detailed description of these parameters. Click Update to activate the optional parameter selection in the HyperMesh database.
See also Load Step: Boundary
In Abaqus, *CLOAD can have degrees of freedom (dof) 1 through 6. In HyperMesh, concentrated loads with dofs 1 through 3 are called force and those with dofs 4 through 6 are called moments. The force and moments are two separate entities that are defined from separate panels. Their graphical displays are also different. As a result, Step Manager has two distinct tree options for *CLOAD: CLOAD-Force and CLOADMoment. The CLOAD-Force dialog allows you to define the *CLOAD card for dofs 1 through 3 and the CLOADMoment for dofs 4 through 6. Open Concentrated loads in the tree, select CLOAD-Force or CLOADMoment, and a load collector from the Load collector table to open the corresponding dialog in the right most section of the Load Step window. It is recommended that you do not use both CLOADForce and CLOAD-Moment in the same load collector in HyperMesh. If you need to use both types of *CLOAD in the same STEP, define each type in a separate load collector and add them to the same load step. Each dialog contains three tabs: Define Delete Parameter
Altair Engineering

366
See also Load Collector Abaqus Step Manager: Load Step Dialog Abaqus Step Manager Overview
The Define tab allows you to define *CLOAD (force or moment) cards on individual nodes or geometry (points). You can also define the *CLOAD on node sets. You can define CLOAD-Force/Moment on nodes/geometry or on node sets. For Define CLOAD-Force/ Moment on:, the following options are available: Nodes or geometry Node sets The layout of the Define tab changes, based on your selection.
See also Load Step: CLOAD
The Define CLOAD-Force/Moment on: Nodes or geometry option allows you to define *CLOAD (force or moment) on individual nodes or geometry. The concentrated loads created on nodes have special graphical display in HyperMesh. Loads created on geometric entities such as surfaces, lines, or points are automatically mapped to FEA mesh on export. They can also be mapped using the Map Loads on
367

Altair Engineering
Geometry button.
The Define tab for Define CLOAD-Force/Moment on: Nodes or geometry contains the following buttons: Define from 'Forces'/Moments Panel Opens the HyperMesh forces or moments panel to create/update a CLOAD. To create a CLOAD on nodes, go to the create sub-panel, select nodes using the switch, pick the desired nodes from HyperMesh graphics, select the global/ local system, select a vector, input a magnitude, and click create. To create a CLOAD on geometry, go to the create sub-panel, select points using the switch, pick the desired geometry from HyperMesh graphics, select the global/local system, select a vector, input a magnitude, and click create. Note: Loads created on geometric entities are automatically mapped to FEA mesh on export. You can also map them using the Map Loads on Geometry button. You can also update an existing force or moments from the update sub-panel. While you are in the forces or moments panel, press the h key to view panel-specific help. When you finish creating or updating CLOAD, click return to update Step Manager with the new loads. Map Loads on geometry Opens the HyperMesh loads on geom panel to map loads on geometry to FEA mesh entities. Click Map loads to map all geometric loads in the current load collector to FEA entities. Note: You can also pick other load collectors by clicking on the loadcols
Altair Engineering

368
button and map loads in all of them together. While you are in the loads on geom panel, press the h key to view panel-specific help. When you are finished, click return to update the Step Manager with the new loads.
See also Load Step: CLOAD Tab
The Define CLOAD-Force/Moment on: Node sets option defines CLOAD on node sets. The node set names are used in the *CLOAD data lines instead of the individual nodes. Unlike Abaqus surfaces in HyperMesh, you can combine node sets with individual node IDs in the same *CLOAD card. Note: Loads created on sets are not graphically displayed in HyperMesh. Therefore, when you review a load collector in Step Manager, only loads created on individual entities are highlighted. For loads defined on sets, the underlying nodes or elements are highlighted.
This Define tab for Define CLOAD-Force/Moment on: Node sets includes a Node sets menu containing a list of existing node sets. A data line input table also appears on the Define tab. The table contains the following columns: Nodeset
The name of the node sets. Node sets are added or removed using , respectively.
or
Comp_x
The component in x direction. The x-direction indicates dof 1 for force and dof 4 for moment.
369

Altair Engineering
Comp_y
The component in y direction. The y-direction indicates dof 2 for force and dof 5 for moment. The component in z direction. The x-direction indicates dof 3 for force and dof 6 for moment. The magnitude. This column is non-editable. The magnitude is calculated based on the Comp_x, Comp_y, and Comp_z defined for each node set when you click Update. The ID of the load collector.
Comp_z
Magnitude
Load Id
For tips on entering information and navigating in the Define tab, see Step Manager Tab Environment. The Define tab for Define CLOAD-Force/Moment on: Node sets contains the following buttons: Review Set Reviews the selected node sets by highlighting them in the HyperMesh graphics. Right click Review to clear the review selections. Opens the entity sets panel in HyperMesh. When you finish creating/editing the set, click return. Step Manager is updated with the new set appearing in the node set list. Opens the appropriate HyperMesh panel. Use the review button to expand the loads and constraints on the sets for visualization purposes. Add the selected node set from the drop-down menu to the data line table on the right. Delete the selected node set from the data line table. Define by vector Opens the HyperMesh vector selector panel. Pick a vector and click proceed . This vector is used to define the Comp_x, Comp_y, Comp_z, and Magnitude of the CLOAD for the selected node set. Opens the vectors panel in HyperMesh. When you finish creating/editing the vector, click return. Creates special review forces or moments in HyperMesh graphics for the selected node set. These review forces or moments take into consideration the *TRANSFORM cards that may be associated with nodes in the node set. Right click Review to clear the special review loads and highlighting. Updates the HyperMesh database with the data lines defined in the table. By default, HyperMesh does not display loads defined with sets.
Create/Edit Set..
Create/Edit vector..
Review
Update
Altair Engineering

370
See also Load Step: CLOAD Tab
The Delete tab allows you to delete *CLOAD and other loads from HyperMesh. There are three options for deletion: All loads in current collector The Delete button deletes all the loads from the current load collector. The Delete button deletes only *CLOAD loads from the current load collector. The Pick Loads button opens the HyperMesh load selector panel. Pick the loads you want to delete and click proceed. The corresponding Reset button resets the selected loads. The Delete button deletes the selected loads.
All 'CLOAD' in current collector
By selection
371

Altair Engineering
The Parameter tab allows you to define optional parameters for the *CLOAD card. The supported parameters are: Amplitude, OP, Load Case, Cyclic Mode, Follower, and Region Type See the Abaqus online documentation for a detailed description of these parameters. Click Update to activate the optional parameter selection in the HyperMesh database.
The CFILM dialog allows you to define the *CFILM card on node sets. To open the dialog in the Load Step window, open Concentrated loads in the tree, select CFILM , and select a load collector from the Load Collector table. The dialog contains three tabs: Define Delete Parameter
Altair Engineering

372
The Define tab allows you to define a *CFILM card on node sets only. HyperMesh does not support *CFILM on individual nodes. The Define CFILM-Force/Moment on: Node sets option defines CFILM on node sets. The node set names are used in the *CFILM data lines instead of the individual nodes. Unlike Abaqus surfaces in HyperMesh, you can combine node sets with individual node IDs in the same *CFILM card. Note: Loads created on sets are not graphically displayed in HyperMesh. Therefore, when you review a load collector in the Step Manager, only loads created on individual entities are highlighted. For loads defined on sets, the underlying nodes or elements are highlighted.
This dialog has a node sets menu containing a list of the existing node sets. It also has a data line input table with the following columns:
373

Altair Engineering
Nodeset
The name of the node sets. Node sets are added or removed using respectively. The area associated with the nodes. Reference sink temperature. Reference film coefficient.
or
Area Sink temp Film coef
For tips on entering information and navigating in the Define tab, see Step Manager Tab Environment. The Define CFILM on: Node sets option has the following buttons: Review Set Reviews the selected node sets by highlighting them in the HyperMesh graphics. Right-click Review to clear the review selections. Opens the entity sets panel in HyperMesh. When you finish creating/editing the set, click return. The Step Manager is updated with the new set appearing in the node set list. Adds the selected node set from the drop-down menu to the data line table on the right. Deletes the selected node set from the data line table. Review Reviews the selected node set in the data line table. Right-click Review to clear the highlighted selections. Updates the HyperMesh database with the data lines defined in the table. By default, HyperMesh does not create a display for loads defined with sets.
Create/Edit Set..
Update
See also Load Step: CFILM
The Delete tab allows you to delete CFILM and other loads from HyperMesh. There are three options: All loads in current collector The Delete button deletes all the loads from the current load collector. The Delete button deletes only *CFILM loads from the current
All 'CFILM' in current collector
Altair Engineering

374
load collector. By selection The Pick Loads button opens the HyperMesh load selector panel. Pick the loads you want to delete and click proceed. The corresponding Reset button resets the selected loads. The Delete button deletes the selected loads.
The Parameter tab allows you to define optional parameters for the *CFILM card. The supported parameters are: Amplitude, Film Amplitude, OP, and Region Type See the Abaqus online documentation for a detailed description of these parameters. Click Update to activate the optional parameter selection in the HyperMesh database.
The DLOAD dialog allows you to define the *DLOAD cards on individual elements or geometry (surfaces). You can also define the DLOAD on element sets. To open the dialog in the Load Step window, open
375

Altair Engineering
Distributed loads in the tree, select DLOAD, and select a load collector from the Load collector table. The dialog contains three tabs: Define Delete Parameter
The Define tab allows you to define *DLOAD cards on individual elements or geometry (surfaces) as well as on element sets. There are seven different DLOAD types available: default (Pressure), centrifugal, rotary acceleration, gravity, pressure in pipe/elbow, hydro pressure, and hydro pressure in pipe/elbow. Only default (Pressure) type DLOAD can be created on an individual element or geometry in HyperMesh. The other types are available only for element sets. It is recommended that you use only one type of DLOAD in a load collector in HyperMesh. If you need to use multiple types of DLOAD in the same STEP, define each type in a separate load collector and add them to the same load step. You can define DLOAD on elements, geometry, or element sets. For Define DLOAD on:, the following options are available: Elements or geometry Element sets The layout of the Define tab changes, based on your selection.
Altair Engineering

376
See also Load Step: DLOAD
The Define DLOAD on: Elements or geometry option allows you to define the default (pressure) type of DLOAD on individual elements or geometric surfaces. Pressure loads created on elements have special graphical display in HyperMesh. Loads created on geometric entities such as surfaces are automatically mapped to FEA mesh on export. You can also map them using the Map Loads on Geometry button.
The Define tab for Define DLOAD on: Elements or geometry contains the following buttons: Define from 'pressures' panels Opens the pressures panel to create/update DLOAD. To create a pressure on elements, go to the create sub-panel, select the elems button, pick the desired elements from the HyperMesh graphics, select nodes using the switch, pick two or three nodes from a face of a selected element, input the magnitude, and click create. To create a pressure on geometry, go to the create sub-panel, select the surfs option from the toggle, pick the desired geometry from the HyperMesh graphics, input the magnitude, and click create. Note: Loads created on geometric entities are automatically mapped to FEA mesh on export. You can also map them using the Map Loads on Geometry button. You can also update an existing DLOAD from the update sub-panel. While you are in the pressure panel, press the h key to view panelspecific help. When you finish creating or updating boundary conditions, click return and the Step Manager is updated with the new loads.
377

Altair Engineering
Map Loads on geometry
Opens the loads on geom panel to map loads on geometry to FEA mesh entities. Click Map loads to map all geometric loads in the current load collector to FEA entities. Note: You can also pick other load collectors by clicking on the loadcols and map loads in all of them together. While you are in the loads on geom panel, press the h key to view panel-specific help. When you finish, click return to update the Step Manager with the new loads.
See also Load Step: DLOAD Define Tab
The Define DLOAD on: Element sets option allows you to define various DLOAD types on element sets. The element set names are used in the *DLOAD data lines instead of the individual elements. Unlike Abaqus surfaces in HyperMesh, you can combine element sets with individual element IDs in the same *DLOAD card. Note: There is no graphical display in HyperMesh for loads created on sets. Therefore, when you review a load collector in the Step Manager, only loads created on individual entities are highlighted. For loads defined on sets, the underlying nodes or elements are highlighted.
This dialog contains a element sets menu with a list of the existing element sets. There are two types of elsets in HyperMesh: Components and Entity sets. The Abaqus elsets that are linked to sectional property cards (such as *SOLID SECTION, *SHELL SECTION, etc.) become Components in HyperMesh. Others
Altair Engineering

378
become Entity sets. To differentiate between these two types, there is a divider line "- - - - -" in the elset list that pops up if you click the element sets menu. The elsets listed below the divider line are Components. This dialog also contains a table for data line input. The table changes depending on the DLOAD type selected. The table contains the following columns: For Default (Pressure) type: The name of the element sets. Element sets are added and deleted in this Elset column using Label or , respectively.
The labels of pressure load. The available labels are: P1, P2, P3, P4, P5, P6, and P. The magnitude of the load. The ID of the load collector.
Magnitude Load Id
For Centrifugal type: Elset The name of the element sets. Element sets are added and deleted in this column using Label or , respectively.
The labels of centrifugal loads and Coriolis forces. The available labels are: CENTRIF, CENT, and CORIO. The magnitude of the load. Coordinate 1 of a point on the axis of rotation. Coordinate 2 of a point on the axis of rotation. Coordinate 3 of a point on the axis of rotation. 1-component of the direction cosine of the axis of rotation. 2-component of the direction cosine of the axis of rotation. 3-component of the direction cosine of the axis of rotation. The ID of the load collector.
Magnitude Coord1 Coord2 Coord3 DirCos1 DirCos2 DirCos3 Load Id
For Rotary acceleration type:
379

Altair Engineering
Elset
The name of the element sets. Element sets are added and deleted in this column using or , respectively.
Label Magnitude Coord1 Coord2 Coord3 DirCos1 DirCos2 DirCos3 Load Id
The labels of the DLOAD type. The available labels are: ROTA. The magnitude of the load. Coordinate 1 of a point on the axis of rotary acceleration. Coordinate 2 of a point on the axis of rotary acceleration. Coordinate 3 of a point on the axis of rotary acceleration. 1-component of the direction cosine of the axis of rotary acceleration. 2-component of the direction cosine of the axis of rotary acceleration. 3-component of the direction cosine of the axis of rotary acceleration. The ID of the load collector.
For Gravity type: The name of the element sets. Element sets are added and deleted in Elset this column using Label Magnitude Comp1 Comp2 Comp3 Load Id or , respectively.
The labels of the DLOAD type. The available labels are: GRAV. The magnitude of the load. 1-component of the gravity vector. 2-component of the gravity vector. 3-component of the gravity vector. The ID of the load collector.
For pressure in pipe/elbow type: The name of the element sets. Element sets are added and deleted in this column using or , respectively.
Elset
Altair Engineering

380
Label
The labels of the pressure in pipe/elbow elements. The available labels are: PE, PI, PENU, and PINU. The magnitude of the load. The effective inner or outer diameter. The end loading condition: CLOSE (default) or OPEN. The ID of the load collector.
Magnitude Diameter Condition Load Id
For hydro pressure type: The name of the element sets. Element sets are added and deleted in this Elset column using Label Magnitude Zero press or , respectively.
The labels of the hydrostatic pressure. The available labels are: HP. The magnitude of the load. Z-coordinate of zero pressure level in three-dimensional or axisymmetric cases; Y-coordinate of zero pressure level in two-dimensional cases. Z-coordinate of the point at which the pressure is defined in threedimensional or axisymmetric cases; Y-coordinate of the point at which the pressure is defined in two-dimensional cases. The ID of the load collector.
Press point
Load Id
For hydro pressure in pipe/elbow type: The name of the element sets. Element sets are added and deleted in this column using Label or , respectively.
Elset
The labels of the hydrostatic pressure in pipe.elbow elements. The available labels are: HPE, and HPI. The magnitude of the load. Z-coordinate of zero pressure level in three-dimensional or axisymmetric cases; Y-coordinate of zero pressure level in two-dimensional cases.
Magnitude Zero press
381

Altair Engineering
Press point
Z-coordinate of the point at which the pressure is defined in threedimensional or axisymmetric cases; Y-coordinate of the point at which the pressure is defined in two-dimensional cases. The effective inner or outer diameter. The end loading condition: CLOSE (default) or OPEN. The ID of the load collector.
Diameter Condition Load Id
The Define tab for Define DLOAD on: Element sets contains the following buttons: Review Set Reviews the selected element sets by highlighting them in the HyperMesh graphics. Right-click Review to clear the review selections. Opens the entity sets panel in HyperMesh. When you finish creating/editing the set, click return. The Step Manager is updated with the new set appearing in the element set list. Opens the appropriate HyperMesh panel. Use the review button to expand the loads and constraints on the sets for visualization purposes. Add the selected element set from the pull down menu to the data line table on the right. Delete the selected element set from the data line table. Show faces This option is only shown for Default (pressure) type. It is mainly used to review the face identifiers of elements in the selected set. It creates a temporary skin of the selected elset, opens the HyperMesh element selector panel, and allows you to pick face elements from this skin. When you return from the element selector panel, the selected faces display color-coded face identifier tags. In performance graphics, these tags are sometimes blocked by the solid mesh. You may need to rotate the model a little to view the tags. Right-click the Show faces button to clear the face review. Define by vector This option is only shown for Gravity type. It opens the HyperMesh vector selector panel. Pick a vector and click proceed. This vector is used to define the Comp1, Comp2, Comp3, and Magnitude of the gravity load for the selected elset.
Create/Edit Set
Create/Edit vector.. This option is only shown for Gravity type. Opens the vectors panel in HyperMesh. When you finish creating/editing the vector, click return. Review For Default (pressure) type. Creates special review pressure loads in the HyperMesh graphics for the selected set. For other types, it reviews the selected element set. Right-click the Review button to clear the special
Altair Engineering

382
review loads and highlighting. Update Updates the HyperMesh database with the data lines defined in the table. By default, HyperMesh does not create a display for loads defined with sets.
See also Load Step: DLOAD Define Tab
The Delete tab allows you to delete DLOAD and other loads from HyperMesh. There are three options: All loads in current collector The Delete button deletes all the loads from the current load collector. The Delete button deletes all distributed (*DLOAD, *FILM) loads from the current load collector. The Pick Loads button opens the HyperMesh load selector panel. Pick the loads you want to delete and click proceed. The corresponding Reset button resets the selected loads. The Delete button deletes the selected loads.
All 'Distributed loads' in current collector By selection
383

Altair Engineering
The Parameter tab allows you to define optional parameters for the *DLOAD card. The supported parameters are: Amplitude, OP, Load Case, Cyclic Mode, and Region Type See the Abaqus Online Documentation for a detailed description of these parameters. Click Update to activate the optional parameter selection in the HyperMesh database.
Altair Engineering

384
The FILM dialog allows you to define the *FILM cards on individual elements or geometry (surfaces). You can also define the FILM on element sets. To open this dialog in the Load Step window, select FILM from the tree and a load collector from the Load collector table. The dialog contains three tabs: Define Delete Parameter
There are two options for defining film coefficient on FILM created on individual elements or geometry: By selection The Pick Loads button opens the HyperMesh load selector panel. Pick the FILM loads to which you want to assign film coefficient, and click proceed.
385

Altair Engineering
The corresponding Reset button resets the selected loads. The Update button assigns the value specified in the Film coefficient: text box to all selected FILM loads. All FILMs in current collector The Update button assigns the value specified in the Film coefficient: text box to all the FILM loads in the current load collector.
See also Load Step: FILM
The Define tab allows you to define *FILM cards on individual elements or geometry (surfaces) as well as on element sets. For Define DLOAD on:, the following options are available: Elements or geometry Element sets The layout of the Define tab changes, based on your selection. For options to assign FILM coefficient, see FILM coefficient.
Altair Engineering

386
The Define FILM on: Elements or geometry option allows you to define FILM on individual elements or geometric surfaces. FILM loads created on elements have special graphical display in HyperMesh. Loads created on geometric entities like surfaces are automatically mapped to FEA mesh on export. You can also map them using the Map Loads on Geometry button.
The Define tab for Define FILM on: Elements or geometry has the following buttons: Define from 'pressures' panels Opens the HyperMesh pressures panel to create/update FILM. It only allows you to define the reference sink temperature. The film coefficient needs to be defined separately. To create a FILM on elements, go to the create sub-panel, select elems using the switch, pick the desired elements from the HyperMesh graphics, click nodes, pick two or three nodes from a face of a selected element, input the magnitude (sink temperature), and click create. To create a pressure on geometry, go to the create sub-panel, select surfs using the switch, pick the desired geometry from the HyperMesh graphics, input the magnitude (sink temperature), and click create. Note: Loads created on geometric entities are automatically mapped to FEA mesh on export. You can also map them using the Map Loads on Geometry button. You can also update an existing FILM from the update sub-panel. While you are in the pressure panel, press the h key to view panel-specific help. When you are finished creating or updating boundary conditions, click return and the Step Manager will be updated with the new loads. Map Loads on Opens the HyperMesh loads on geom panel to map loads on geometry to FEA
387

Altair Engineering
geometry
mesh entities. Click the Map loads button to map all geometric loads in the current load collector to FEA entities. Note: You can also pick other load collectors by clicking the loadcols button and map loads in all of them together. While you are in the loads on geom panel, press the h key to view panelspecific help. When you are done, click return and the Step Manager will be updated with the new loads.
The Define FILM on: Element sets option allows you to define the FILM load on element sets. The element set names are used in the *FILM data lines instead of the individual elements. Unlike Abaqus surfaces in HyperMesh, you can combine element sets with individual element IDs in the same *FILM card. Note: There is no graphical display in HyperMesh for loads created on sets. Therefore, when you review a load collector in the Step Manager, only loads created on individual entities are highlighted. For loads defined on sets, the underlying nodes or elements are highlighted.
This dialog contains an element sets menu containing a list of the existing element sets. There are two types of elsets in Hypermesh: Components and Entity sets. The Abaqus elsets that are linked to sectional property cards (such as *SOLID SECTION, *SHELL SECTION, etc.) become Components in HyperMesh. Others become Entity sets. To differentiate between these two types, there is a divider line "- - - - -" in the
Altair Engineering

388
elset list that pops up if you click the element sets menu. The elsets listed below the divider line are Components. This dialog also contains a table for data line input, which contains the following columns: Elset The name of the element sets. Element sets are added or deleted in this column using Label or , respectively.
The labels of FILM load. The available labels are: F1, F2, F3, F4, F5, F6, FPOS, and FNEG. The reference sink temperature. The reference film coefficient. The ID of the load collector.
Sink Temp Film coeff Load Id
The Define tab for Define FILM on: Element sets contains the following buttons: Review Set Reviews the selected element sets by highlighting them in the HyperMesh graphics. Right-click Review to clear the review selections. Opens the entity sets panel in HyperMesh. When you finish creating/editing the set, click return. The Step Manager is updated with the new set appearing in the element set list. Opens the appropriate HyperMesh panel. Use the review button to expand the loads and constraints on the sets for visualization purposes. Add the selected element set from the pull down menu to the data line table on the right. Delete the selected element set from the data line table. Show faces Used mainly to review the face identifiers of elements in the selected set. It creates a temporary skin of the selected elset, opens the HyperMesh element selector panel, and allows you to pick face elements from this skin. When you return from the element selector panel, the selected faces will display colorcoded face identifier tags. In performance graphics, these tags are sometimes blocked by the solid mesh. You may need to rotate the model a little to view the tags. Right-click Show faces to clear the face review. Review Creates special review FILM loads in HyperMesh graphics for the selected set. Right-click Review to clear the special review loads and highlighting.
Create/Edit Set
Display/Review from Panel
389

Altair Engineering
Update
Updates the HyperMesh database with the data lines defined in the table. By default, HyperMesh does not create a display for loads defined with sets.
The Delete tab allows you to delete FILM and other loads from HyperMesh. There are three deletion options: All loads in current collector The Delete button deletes all the loads from the current load collector. The Delete button deletes all distributed (*DLOAD, *FILM) loads from the current load collector. The Pick Loads button opens the HyperMesh load selector panel. Pick the loads you want to delete and click proceed. The corresponding Reset button resets the selected loads. The Delete button deletes the selected loads.
All 'Distributed loads' in current collector By selection
Altair Engineering

390
The Parameter tab allows you to define optional parameters for the *FILM card. The supported parameters are: Amplitude, Film Amplitude, OP, and Region Type See the Abaqus Online Documentation for a detailed description of these parameters. Click Update to activate the optional parameter selection in the HyperMesh database.
The DSLOAD dialog allows you to define the *DSLOAD card on Abaqus surfaces (*SURFACE). To open the dialog in the Load Step window, select DSLOAD from the tree and a load collector from the Load collector table. The dialog contains three tabs: Define Delete Parameter
391

Altair Engineering
You can use Abaqus Contact Manager to create Abaqus surfaces.
See also Load collector Abaqus Step Manager: Load Step Dialog Abaqus Step Manager Overview
The Define tab allows you to define *DSLOAD card on Abaqus surfaces (*SURFACE). There are two types of DSLOAD available: default (Pressure) and hydro pressure. It is recommended that you use only one type of DSLOAD per load collector in HyperMesh. If you need to use multiple types of DSLOAD in the same STEP, define each type in a separate load collector and add them to the same load step. Note: There is no graphical display in HyperMesh for loads created on Abaqus SURFACEs. Therefore, when you review a load collector in the Step Manager, only loads created on individual entities are highlighted. For loads defined on SURFACE, the underlying SURFACE elements are highlighted.
Altair Engineering

392
This dialog also contains a table for data line input. The table changes depending on the DSLOAD type selected. The table columns for each DSLOAD type are listed below: Default (Pressure) type: The name of the Abaqus surface. Surfaces are added and deleted in this column Surface using Label Magnitude or , respectively.
The labels of pressure load. The available labels are P, PNU, and VP. The magnitude of the load.
hydro pressure type: The name of the Abaqus surface. Surfaces are added and deleted in this column using Label Magnitude Zero press or , respectively.
Surface
The labels of the hydrostatic pressure. The available label is HP. The magnitude of the load. Z-coordinate of zero pressure level in three-dimensional or axisymmetric cases; Y-coordinate of zero pressure level in two-dimensional cases. Z-coordinate of the point at which the pressure is defined in three-dimensional or axisymmetric cases; Y-coordinate of the point at which the pressure is defined in two-dimensional cases.
Press point
393

Altair Engineering
The DSLOAD option has the following buttons: Review Surface Reviews the selected surface by highlighting them in the HyperMesh graphics. Right-click on the Review button to clear the review selections. Opens a message with information about surface definition in HyperMesh.
Create/Edit Surface..
Adds the selected surface from the pull down menu to the data line table on the right. Deletes the selected surface from the data line table. Review Reviews the selected surface in the data line table. Right-click on the Review button to clear the highlighted selections. Updates the HyperMesh database with the data lines defined in the table. By default, HyperMesh does not create a display for loads defined with sets.
Update
See also Load Step: DSLOAD
The Delete tab allows you to delete *DSLOAD and other loads from HyperMesh. There are three options: All loads in current collector All 'DSLOAD' in current collector By selection The Delete button deletes all the loads from the current load collector.
The Delete button deletes only *DSLOAD loads from the current load collector. The Pick Loads button opens the HyperMesh load selector panel. Pick the loads you want to delete and click proceed. The corresponding Reset button resets the selected loads. The Delete button deletes the selected loads.
Altair Engineering

394
The Parameter tab allows you to define optional parameters for the *DSLOAD card. The supported parameters are: Amplitude, OP, Load Case, Cyclic Mode, and Region Type See the Abaqus online documentation for a detailed description of these parameters. Click Update to activate the optional parameter selection in the HyperMesh database.
395

Altair Engineering
The SFILM dialog allows you to define the *SFILM card on Abaqus surfaces (*SURFACE). To open the dialog in the Load Step window, select SFILM from the tree and a load collector from the Load collector table. The dialog contains three tabs: Define Delete Parameter
You can use Abaqus Contact Manager to create Abaqus surfaces.
The Define tab allows you to define *SFILM card on Abaqus surfaces (*SURFACE). Note: There is no graphical display in HyperMesh for loads created on Abaqus SURFACEs. Therefore, when you review a load collector in the Step Manager, only loads created on individual entities are highlighted. For loads defined on SURFACE, the underlying SURFACE elements are highlighted.
Altair Engineering

396
This dialog contains a Surface menu containing a list of the existing Abaqus surfaces. It also has a table for data line input. The table contains the following columns: The name of the surfaces. Surfaces are added and deleted in this column using Surface or Label Sink temp Film coef , respectively.
The SFILM labels. The available labels are F and FNU. Reference sink temperature. Reference film coefficient.
The SFIM option has the following buttons: Review Surface Reviews the selected surface by highlighting them in the HyperMesh graphics. Right-click on the Review button to clear the review selections. Opens a message with information about surface definition in HyperMesh
Create/Edit Surface..
Adds the selected surface from the drop-down menu to the data line table on the right. Deletes the selected surface from the data line table. Review Reviews the selected surface in the data line table. Right-click on the Review button to clear the highlighted selections. Updates the HyperMesh database with the data lines defined in the table. By
Update
397

Altair Engineering
default, HyperMesh does not create a display for loads defined with sets.
See also Load Step: SFILM
The Delete tab allows you to delete *SFILM and other loads from HyperMesh. There are three options: All loads in current collector All 'SFILM' in current collector By selection The Delete button deletes all the loads from the current load collector. The Delete button deletes only *SFILM loads from the current load collector The Pick Loads button opens the HyperMesh load selector panel. Pick the loads you want to delete and click proceed. The corresponding Reset button resets the selected loads. The Delete button deletes the selected loads.
The Parameter tab allows you to define optional parameters for the *SFILM card. The supported parameters are: Amplitude, Film Amplitude, OP, and Region Type See the Abaqus online documentation for a detailed description of these parameters. Click Update to activate the optional parameter selection in the HyperMesh database.
Altair Engineering

398
The Temperature dialog allows you to define and edit the *TEMPERATURE card. To open the dialog in the Load Step window, select Temperature from the tree and a load collector from the Load collector table. The dialog contains three tabs: Define Delete Parameter
See also Load collector Abaqus Step Manager: Load Step Dialog Abaqus Step Manager Overview
The Define tab allows you to define *TEMPERATURE cards on individual nodes or geometry (surfaces, points, lines). You can also define the temperature on node sets It is recommended that you do not use *TEMPERATURE and *BOUNDARY with dof 11 together in a load collector in HyperMesh. If you need to use multiple types of temperature in the same STEP, define each type in a separate load collector and add them to the same load step. You can define *TEMPERATURE on nodes, geometry, or node sets. For Define Temperature on:, the following options are available: Nodes or geometry Node sets The layout of the Define tab changes, based on your selection.
399

Altair Engineering
See also Load Step: Temperature
The Define Temperature on: Nodes or geometry option allows you to define temperature on individual nodes or geometry. Temperatures created on nodes have special graphical display in HyperMesh. Loads created on geometric entities like surfaces, lines or points are automatically mapped to FEA mesh on export. You can also map them using the Map Loads on Geometry button.
The Define tab for Define Temperature on: Nodes or geometry contains the following buttons: Define from 'temperatures' panel Opens the temperature panel to create/update temperature. To create a temperature on nodes, go to the create sub-panel, select nodes using the switch, input a value, and click create. To create a temperature on geometry, go to the create sub-panel, select surfs, points, or lines using the switch, input a value, and click create. Note: Loads created on geometric entities are automatically mapped to FEA mesh on export. You can also map them using the Map Loads on Geometry button. You can also update an existing temperature from the update subpanel. While you are in the temperature panel, press the h key to view panel-specific help. When you are finished creating or updating temperature, click return and the Step Manager will be updated with the new loads.
Altair Engineering

400
Map Loads on geometry
Opens the loads on geom panel to map loads on geometry to FEA mesh entities. Click the Map loads button to map all geometric loads in the current load collector to FEA entities. Note: You can also pick other load collectors by clicking on the loadcols button and map loads in all of them together. While you are in the loads on geom panel, press the h key to view panel-specific help. When you are finished, click return and the Step Manager will be updated with the new loads.
See also Load Step: Temperature Define Tab
The Define Temperature on: Node sets option defines temperature on node sets. The node set names are used in the *TEMPERATURE data lines instead of the individual nodes. Unlike Abaqus surfaces in HyperMesh, you can combine node sets with individual node IDs in the same *TEMPERATURE card. Note: There is no graphical display in HyperMesh for loads created on sets. Therefore, when you review a load collector in the Step Manager, only loads created on individual entities are highlighted. For loads defined on sets, the underlying nodes or elements are highlighted.
This dialog contains a node sets menu with a list of the existing node sets. It also contains a table for data line input with the following columns:
401

Altair Engineering
Nset
The name of the node sets. Node sets are added and deleted in this column using or , respectively.
Temperature Gradient1
Reference temperature value. Temperature gradient in the n2-direction for beams or temperature gradient through the thickness for shells. Temperature gradient in the n1-direction for beams. The ID of the load collector.
Gradient2 Load Id
The Define tab for Define Temperature on: Node sets has the following buttons: Review Set Reviews the selected node sets by highlighting them in the HyperMesh graphics. Right-click on the Review button to clear the review selections. Opens the entity sets panel in HyperMesh. When you finish creating/editing the set, click return. The Step Manager is updated with the new set appearing in the node set list.
Create/Edit Set
Display/Review from Panel Adds the selected node set from the pull down menu to the data line table on the right. Deletes the selected node set from the data line table. Review Reviews the selected node set in the data line table. Right click on the Review button to clear the highlighted selections. Updates the HyperMesh database with the data lines defined in the table. By default, HyperMesh does not create a display for loads defined with sets.
Update
See also Load Step: Temperature Define Tab
Altair Engineering

402
The Delete tab allows you to delete boundaries and other loads from HyperMesh. There are three options: All loads in current collector All 'Temperature' in current collector By selection The Delete button deletes all the loads from the current load collector.
The Delete button deletes only *TEMPERATURE loads from the current load collector. The Pick Loads button opens the HyperMesh load selector panel. Pick the loads you want to delete and click proceed. The corresponding Reset button resets the selected loads. The Delete button deletes the selected loads.
The Parameter tab allows you to define optional parameters for the *TEMPERATURE card. The supported parameters are: Amplitude, OP, Bstep, Binc, Estep, Einc, Input, Result (File), and MidSide See the Abaqus online documentation for a detailed description of these parameters. Click Update to activate the optional parameter selection in the HyperMesh database.
403

Altair Engineering
The Inertia relief dialog allows you to define and edit the *INERTIA RELIEF card. To open the dialog in the Load Step window, select Inertia relief from the tree and a load collector from the Load collector table. The dialog contains two tabs: Define Parameter
See also Load Collector Abaqus Step Manager: Load Step Dialog
Altair Engineering

404
Abaqus Step Manager Overview
The Define tab allows you to define * INERTIA RELIEF cards. Activate the Inertia relief check box to make the *INERTIA RELIEF load active for the current load collector. There are two data line options available: Free direction Reference points Integer list of degrees of freedom identifying the free directions Global X, Y, and Z-coordinates of the reference point.
Click Update to activate the data line selection in the HyperMesh database.
See also Load Step: Inertia Relief
The Parameter tab allows you to define optional parameters for the * INERTIA RELIEF card. The supported parameters are: Orientation, Fixed, Remove, and None See the Abaqus online documentation for a detailed description of these parameters. Click Update to activate the optional parameter selection in the HyperMesh database.
405

Altair Engineering
See also Load Step: Inertia Relief
The Interface Controls option defines the following Abaqus keywords: *CONTACT, *CONTACT CONTROLS, *CLEARANCE, *CONTACT INTERFERENCE, *MODEL CHANGE, *CHANGE FRICTION, and *CONTROLS. It also allows you to add *CONTACT PAIR and *SURFACE INTERACTION cards created from the Abaqus Contact Manager to a load step. When you select an interface controls option from the tree, the corresponding table is displayed in the Load Step window. The Interface controls: table contains a list of interface controls of the type selected in the tree. You can create, edit, rename, reorder, and delete interface controls from this table.
Altair Engineering

406
The Interface controls table contains the following columns: Status The history status of the interface control. If the status is on, the corresponding interface control parameters and data lines will be exported in the current load step. If the status is off, the interface control will not be exported under the current *STEP block. The name of the interface controls. Some of the interface controls names are for HyperMesh internal use only. Abaqus input files do not require them.
Name
Note: Right click on the table to display menu options. The available options are Rename and Reorder. Table columns can be resized by positioning the cursor along a column border, pressing the left or right mouse button, and dragging the border to a new position. The Interface controls table contains the following buttons: New Opens the Create dialog for the corresponding interface control. The name of the new interface control is entered in this dialog. The Same as: option allows you to create an interface control by copying attributes from an existing interface control of the same type. The Create button creates an interface control and adds it to the current load step. Opens the card image panel for the selected interface control. Click edit to open the card editor and define all relevant keywords, parameters, and data lines. When you are
Edit
407

Altair Engineering
finished, click return twice and the Step Manager is updated. Delete Opens the HyperMesh delete panel to delete interface controls. When you are finished, click return and the Interface controls table will be updated.
In HyperMesh, Abaqus output requests are organized into HyperMesh collectors called output blocks. The Output requests option in the tree allows you to define output options for ODB, result (.fil) and data (. dat) file formats. When you select an output request file format from the tree, the output block table is displayed in the Load Step window. The Output block: table contains a list of the output blocks with corresponding history status. You can create, edit, review, rename, reorder, and delete output blocks from this table.
The Ouput block: table contains the following columns: Status The history status of the output block. If the status is on, the output block belongs to the current load step. This means, all parameter and data line information in the output block will be written under the current *STEP block. If the status is off, no
Altair Engineering

408
parameters or data lines from the output block will be written under the current *STEP block. Name The name of the output block. These names are for HyperMesh internal use only.
Note: Click on an output block name to set it as the current output block in HyperMesh. All changes and additions to the parameters and data line will be for the selected output block. The Output type: status bar (below the output block table) shows all the output types present in the selected output block. Right-click on the table to display menu options. The available options are Rename and Reorder. See Step Manager Dialog Environment for tips on navigating through the dialogs. The Output block table contains the following buttons: New.. Opens the Create Output block dialog in which you enter the name of the new output block. The Create button in this dialog creates the output block and adds it to the current load step. Reviews the selected output block in a text window. All parameters and data lines associated with the selected output block are listed in the text window. Opens the HyperMesh delete panel to delete output blocks. When you are finished, click return and the Output block table will be updated.
Review
Delete
See also Load Step: Output request: ODB File Load Step: Output request: Result file (.fil) Load Step: Output request: Data file (.dat) Abaqus Step Manager: Load Step Dialog Abaqus Step Manager Overview
The ODB file dialog allows you to define and edit the output requests for the ODB file. Supported keywords are: *OUTPUT, *NODE OUTPUT, *ELEMENT OUTPUT, *CONTACT OUTPUT, and *ENERGY OUTPUT. To open the dialog in the Load Step window, select ODB file from the tree and an output block from the Output block table. The dialog contains five tabs: Output
409

Altair Engineering
Node Output Element Output Contact Output Energy Output
See also Output request Abaqus Step Manager Overview
The Output tab allows you to define *OUTPUT cards with associated parameters. Supported parameters are: Field, History, OP, Variable, Frequency, Time marks, Number interval, Time interval, and Mode list
See the Abaqus online documentation for a detailed description of these parameters. Click Update to activate the parameters defined in the HyperMesh database.
Altair Engineering

410
To enable the Node Output, Element Output, Contact Output, and Energy Output tabs used to define the *NODE OUTPUT, *ELEMENT OUTPUT, *CONTACT OUTPUT and *ENERGY OUTPUT cards, you must first activate the corresponding check boxes.
The Node Output tab allows you to define *NODE OUTPUT for the selected Output block. Nset and Variable parameters are supported. Activate/deactivate the check boxes in the tree on the Node Output tab to add/remove identifier keys in the table. The data lines added in this manner have a gray background indicating they cannot be manually edited. You may also add user-defined identifiers, by typing them directly into the table. User-defined data lines appear with a white background, indicating they are editable. Right-click on the Data lines table to display menu options. The available options are Cut, Copy, Paste, Add row, and Delete row.
The following buttons are available on the Node Output tab: Create/Edit Opens the entity sets panel in HyperMesh. When you finish creating/editing the set, click return. The Step Manager is updated with the new set appearing in the node set list. Reviews the selected node sets by highlighting them in the HyperMesh graphics. Right-click on the Review button to clear the review selections. Updates the HyperMesh database with the data lines defined in the table and the parameters.
Review
Update
411

Altair Engineering
See also Output Request Abaqus Step Manager Overview
The Element Output tab allows you to define *ELEMENT OUTPUT for the selected Output block. The following parameters are supported: Elset, Position, and Variable. Activate/deactivate the check boxes in the tree on the Element Output tab to add/remove identifier keys in the table. Data lines added in this manner have a gray background indicating they cannot be manually edited. You may also add user-defined identifiers, by typing them directly into the table. The user-defined data lines appear with a white background, indicating they are editable. Right-click on the Data lines table to display menu options. The available options are Cut, Copy, Paste, Add row, and Delete row.
The Element Output tab has the following buttons: Create/Edit Opens the entity sets panel in HyperMesh. When you finish creating/editing the set, click return. The Step Manager is updated with the new set appearing in the element set list. Reviews the selected element sets by highlighting them in the HyperMesh graphics. Right-click on the Review button to clear the review selections. Updates the HyperMesh database with the data lines defined in the table and the parameters.
Review
Update
Altair Engineering

412
The Contact Output tab allows you to define *CONTACT OUTPUT for the selected Output block. The following parameters are supported: Nlset, Master, Slave, General Contact, and Variable. Activate/ deactivate the check boxes in the tree on the Contact Output tab to add/remove identifier keys in the table. The data lines added in this manner have a gray background, indicating they cannot be manually edited. You may also add user-defined identifiers, by typing them directly into the table. The user-defined data lines appear with a white background, indicating they are editable. Right-click on the Data lines table to display menu options. The available options are Cut, Copy, Paste, Add row, and Delete row.
The Contact Output tab has the following buttons: Create/Edit Opens the entity sets panel in HyperMesh. When you finish creating/editing the set, click return. The Step Manager is updated with the new set appearing in the node set list. Reviews the selected node sets, master surface, or slave surface by highlighting them in the HyperMesh graphics. Right-click on the Review button to clear the review selections. Updates the HyperMesh database with the data lines defined in the table and the parameters.
Review
Update
See also
413

Altair Engineering
Output request Abaqus Step Manager Overview
The Energy Output tab allows you to define *ENERGY OUTPUT for the selected Output block. The following parameters are supported: Elset and Variable. Activate/deactivate the check boxes in the tree on the Energy Output tab to add/remove identifier keys in the table. The data lines added in this manner have a gray background, indicating they cannot be manually edited. You may also add user-defined identifiers by typing them directly into the table. The user-defined data lines appear with a white background, indicating they are editable. Right-click on the Data lines table to display menu options. The available options are Cut, Copy, Paste, Add row, and Delete row.
The Energy Output tab has the following buttons: Create/Edit Opens the entity sets panel in HyperMesh. When you finish creating/editing the set, click return. The Step Manager is updated with the new set appearing in the element set list. Reviews the selected element sets by highlighting them in the HyperMesh graphics. Right-click on the Review button to clear the review selections. Updates the HyperMesh database with the data lines defined in the table and the parameters.
Review
Update
Altair Engineering

414
The Result file (.fil) dialog allows you to define and edit the output requests for the Result file. Supported keywords are *NODE FILE, *ELEMENT FILE, *CONTACT FILE, and *ENERGY FILE. To open the dialog in the Load Step window, select Result File (.fil) from the tree and an output block from the Output block table. The dialog contains five tabs: Define Node File Element File Contact File Energy File
The Define tab allows you to enable the Node File, Element File, Contact File, and Energy File tabs, which are used to define the *NODE FILE, *ELEMENT FILE, *CONTACT FILE, and *ENERGY FILE cards, respectively.
The Node File tab allows you to define *Node file for the selected Output block. The following parameters are supported: Nset, Frequency, Last mode, Global, and Mode. Activate/deactivate the check boxes in
415

Altair Engineering
the tree on the Node File tab to add/remove identifier keys in the table. The data lines added in this manner have a gray background, indicating they cannot be manually edited. You may also add user-defined identifiers by typing them directly into the table. User-defined data lines appear with a white background, indicating they are editable. Right-click on the Data lines table to display menu options. The available options are Cut, Copy, Paste, Add row, and Delete row.
The Node File tab contains the following buttons: Create/Edit Opens the entity sets panel in HyperMesh. When you finish creating/editing the set, click return. The Step Manager is updated with the new set appearing in the node set list. Reviews the selected node sets by highlighting them in the HyperMesh graphics. Right-click on the Review button to clear the review selections. Updates the HyperMesh database with the data lines defined in the table and the parameters.
Review
Update
The Element File tab allows you to define *ELEMENT FILE for the selected Output block. The following parameters are supported: Elset, Directions, Mode, Frequency, Position, and Last Mode. Activate/ deactivate the check boxes in the tree on the Element File tab to add/remove identifier keys in the table. The data lines added in this manner have a gray background, indicating they cannot be manually edited.
Altair Engineering

416
You may also add user-defined identifiers by typing them directly into the table. User-defined data lines appear with a white background, indicating they are editable. Right-click on the Data lines table to display menu options. The available options are Cut, Copy, Paste, Add row, and Delete row.
The Element File tab contains the following buttons: Create/Edit Opens the entity sets panel in HyperMesh. When you finish creating/editing the set, click return. The Step Manager is updated with the new set appearing in the element set list. Reviews the selected element sets by highlighting them in the HyperMesh graphics. Right-click on the Review button to clear the review selections. Updates the HyperMesh database with the data lines defined in the table and the parameters.
Review
Update
The Contact File tab allows you to define *CONTACT FILE for the selected Output block. The following parameters are supported: Nset, Master, Slave, and Frequency. Activate/deactivate the check boxes in the tree on the Contact File tab to add/remove identifier keys in the table. The data lines added in this manner have a gray background, indicating they cannot be manually edited. You may also add user-defined identifiers, by typing them directly into the table. The user-defined data lines appear with a white background, indicating they are editable.
417

Altair Engineering
Right-click on the Data lines table to display menu options. The available options are Cut, Copy, Paste, Add row, and Delete row.
The Contact File tab contains the following buttons: Create/Edit Opens the entity sets panel in HyperMesh. When you finish creating/editing the set, click return. The Step Manager is updated with the new set appearing in the node set list. Reviews the selected node sets, master surface, or slave surface by highlighting them in the HyperMesh graphics. Right-click on the Review button to clear the review selections. Updates the HyperMesh database with the data lines defined in the table and the parameters.
Review
Update
The Energy File tab allows you to define *ENERGY FILE for the selected Output block. The following parameters are supported: Elset and Frequency.
Altair Engineering

418
The Energy File tab contains the following buttons: Create/Edit Opens the entity sets panel in HyperMesh. When you finish creating/editing the set, click return. The Step Manager is updated with the new set appearing in the element set list. Reviews the selected element sets by highlighting them in the HyperMesh graphics. Right-click on the Review button to clear the review selections. Updates the HyperMesh database with the data lines defined in the table and the parameters.
Review
Update
The Data file (.dat) dialog allows you to define and edit the output requests for the data file. Supported keywords are *NODE PRINT, *ELEMENT PRINT, *CONTACT PRINT, and *ENERGY PRINT. To open the dialog in the Load Step window, select Data File (.dat) from the tree and an output block from the Output block table. The dialog contains five tabs : Define Node Print Element Print
419

Altair Engineering
Contact Print Energy Print
The Define tab allows you to enable the Node Print, Element Print, Contact Print, and Energy Print tabs, which are used to define the *NODE PRINT, *ELEMENT PRINT, *CONTACT PRINT, and *ENERGY PRINT cards.
The Node Print tab allows you to define *NODE PRINT for the selected Output block. The following parameters are supported: Nset, Frequency, Mode, Global, Summary, Last mode, and Totals. Activate/ deactivate the check boxes in the tree on the Node Print tab to add/remove identifier keys in the table. The data lines added in this manner have a gray background, indicating they cannot be manually edited. You may also add user-defined identifiers by typing them directly into the table. User-defined data lines appear with a white background, indicating they are editable. Right-click on the Data lines table to display menu options. The available options are Cut, Copy, Paste, Add row, and Delete row.
Altair Engineering

420
The following buttons are available on the Node Print tab: Create/Edit Opens the entity sets panel in HyperMesh. When you finish creating/editing the set, click return. The Step Manager is updated with the new set appearing in the node set list. Reviews the selected node sets by highlighting them in the HyperMesh graphics. Right-click on the Review button to clear the review selections. Updates the HyperMesh database with the data lines defined in the table and the parameters.
Review
Update
The Element Print tab allows you to define *ELEMENT PRINT for the selected Output block. The following parameters are supported: Elset, Position, Totals, Frequency, Last mode, Summary, and Mode. Activate/deactivate the check boxes in the tree on the Element Print tab to add/remove identifier keys in the table. The data lines added in this manner have a gray background indicating they can not be manually edited. You may also add user-defined identifiers by typing them directly into the table. User-defined data lines appear with a white background, indicating they are editable. Right click on the Data lines table to display menu options. The available options are Cut, Copy, Paste, Add row, and Delete row.
421

Altair Engineering
The following buttons are available on the Element Print tab: Create/Edit Opens the entity sets panel in HyperMesh. When you finish creating/editing the set, click return. The Step Manager is updated with the new set appearing in the element set list. Reviews the selected element sets by highlighting them in the HyperMesh graphics. Right-click on the Review button to clear the review selections. Updates the HyperMesh database with the data lines defined in the table and the parameters.
Review
Update
The Contact Print tab allows you to define *CONTACT PRINT for the selected Output block. The following parameters are supported: Nset, Master, Slave, Frequency, Totals, and Summary. Activate/deactivate the check boxes in the tree on the Contact Print tab to add/remove identifier keys in the table. The data lines added in this manner have a gray background, indicating they cannot be manually edited. You may also add user-defined identifiers by typing them directly into the table. User-defined data lines appear with a white background, indicating they are editable. Right click on the Data lines table to display menu options. The available options are Cut, Copy, Paste, Add row, and Delete row.
Altair Engineering

422
The following buttons are available on the Contact File tab: Create/Edit Opens the entity sets panel in HyperMesh. When you finish creating/editing the set, click return. The Step Manager is updated with the new set appearing in the node set list. Reviews the selected node sets, master surface, or slave surface by highlighting them in the HyperMesh graphics. Right-click on the Review button to clear the review selections. Updates the HyperMesh database with the data lines defined in the table and the parameters.
Review
Update
The Energy Print tab allows you to define *ENERGY PRINT for the selected Output block. The following parameters are supported: Elset and Frequency.
423

Altair Engineering
The following buttons are available on the Energy File tab: Create/Edit Opens the entity sets panel in HyperMesh. When you finish creating/editing the set, click return. The Step Manager is updated with the new set appearing in the element set list. Reviews the selected element sets by highlighting them in the HyperMesh graphics. Right-click on the Review button to clear the review selections. Updates the HyperMesh database with the data lines defined in the table and the parameters.
Review
Update
The Monitor option in the tree allows you to define the *MONITOR card. The supported attributes are: Node, DOF, and Frequency. See the Abaqus online documentation for a detailed description of these attributes. Click Update to activate the monitor attributes defined in the HyperMesh database.
Altair Engineering

424
The following buttons are available on the Monitor dialog: Pick node Opens the node selection panel in HyperMesh. When you finish picking a node from the model, click return. The Step Manager is updated with the selected node number appearing in the Node entry. Updates the HyperMesh database with the data lines defined in the table and the parameters.
Update
See also Abaqus Step Manager Step Tab Abaqus Step Manager: Load Step Dialog Abaqus Step Manager Overview
The Print option in the tree allows you to define the *PRINT card. The supported attributes are: Contact, Model change, Plasticity, Residual, Solve, Frequency, Allke, Critical element, Dmass, and Etotal. See the Abaqus online documentation for a detailed description of these attributes. Click Update to activate the monitor attributes defined in the HyperMesh database.
425

Altair Engineering
The File format option in the tree allows you to define the *FILE FORMAT card. This option is available when a standard Abaqus template is loaded. The supported attributes are: File format and Zero increment. See the Abaqus online documentation for a detailed description of these attributes. Click Update to activate the monitor attributes defined in the HyperMesh database.
Altair Engineering

426
The File output option in the tree allows you to define the *FILE OUTPUT card. This option is available when the Abaqus explicit template is loaded. The supported attributes are: File output, Number interval, and Time marks. See the Abaqus online documentation for a detailed description of these attributes. Click Update to activate the monitor attributes defined in the HyperMesh database.
The Restart write option in the tree allows you to define the *RESTART, WRITE card.
427

Altair Engineering
The supported attributes are: Overlay, Frequency, Number interval, and Time marks. See the Abaqus online documentation for a detailed description of these attributes. Click Update to activate the monitor attributes defined in the HyperMesh database.
The Unsupported cards option in the tree enables you to review and edit unsupported history data within the Step Manager. Select the check box to activate the text area. You can enter the unsupported cards by typing directly or copying and pasting into the text area. Then click Update to include the cards.
Altair Engineering

428
429

Altair Engineering
Abaqus Step Manager Load Case Tab

The Load Case tab contains the descriptions of all existing load cases with the corresponding load collectors. You can create, edit, review, rename, reorder, and delete load cases from this tab as well as set the display status of the load steps.
See Step Manager Dialog Environment for tips on navigating through the dialogs. The Load Case tab contains the following buttons: New... Opens the Create New Load Case dialog. Enter the name of the new load case in the Name: text box and click Create to create the load step and open the corresponding Load Case editing dialog. Opens the Load Step Editing dialog for the selected load step. Reviews the selected load collectors. All loads in the load collectors are highlighted in the HyperMesh graphics. The highlighted loads show through the solid mesh in performance graphics. If a load is defined with set, the underlying nodes or elements are highlighted. Right-click Review to clear the highlighted selections. Reviews the selected load step in a text window. Opens the rename panel for renaming load steps, load collectors, output blocks, or various interface controls. When you finish renaming, click return to update the Step Manager with the new names. Deletes the selected load steps. Updates the Step Manager with the current HyperMesh database. If you manually create, update, or delete load steps, load collectors, output blocks, groups, or entity sets from HyperMesh panels while the Step Manager is open, click Sync to update the Step Manager with the new changes. Closes the Step Manager.
Edit... Review
Text Rename
Delete Sync
Close
Altair Engineering

430
Moves the selected load cases up one row.
Moves the selected load cases down one row.
See also Abaqus Step Manager Step Tab Abaqus Step Manager Overview Pre-Processing for Bracket and Cradle Analysis using Abaqus - HM-4340
431

Altair Engineering
ANSYS Utility Menu

The ANSYS Utility Menu is loaded when you open the ANSYS user profile. The macros on the ANSYS Utility Menu simplify some common tasks for the ANSYS user profile. The following ANSYS macros are available. Component Manager Material Section Real Sets Displays components and attributes in an interactive table. Creates and defines material cards. Creates and defines section cards. Creates property card images for elements defined with the ET Type macro. Creates HyperMesh card images for ANSYS element types. Creates new contact pairs and manages existing contact pairs. Converts a first-order meshed part to a special second-order meshed part. Updates older model files. Converts ANSYS decks to OptiStruct Converts ANSYS deck to Nastran Set the modal analysis
ET Type Contact Manager Convert to Spl. 2nd Order
Update Pre-8.0 HM Model Ansys to OptiStruct Convert Ansys to Nastran Convert Modal Analysis Tool
See also ANSYS Interface Overview
Altair Engineering

432
ANSYS Component Manager

This macro displays components and their associated attributes in an interactive table. You can also configure the table; only configured items are displayed in the table. With this macro, you can also create components, select components, assign materials to components, change component colors, and change component visualization modes. Most actions are available from shortcut (right-click) menus. You can also find options in the drop-down menus. Before performing actions such as changing the values of component data, you must select Editable from the Table menu. Once the components are writable, you can modify the values of existing components. The following sections describe how to use the Component Manager in both read-only mode and editable mode.
Using the Component Manager in Read-Only Mode
When you open the Component Manager, existing components are listed in a table using a default configuration. This configuration displays the name, ID number, ET reference number, element type, real set number, material set number, section set number, and number of elements and nodes in each component. A sum of elements is shown at the bottom of the table. If a component is invalid for any reason and cannot be exported to the ANSYS data deck, its row in the table will appear in red. The display of the data in the Component Manager can be customized according to your preferences. You can: Change which columns are displayed Change the order of the columns Sort the components by column data, ascending or descending Filter which components are displayed based on column data values (see below) You can save your settings by creating a configuration file. From the Table menu, open the Configure submenu and select the Save CFG-File option. This configuration file saves the set of table configuration options so you can use them again. By default, a configuration file (comptable.cfg) is saved in the working directory for each component table session and settings from this file are applied each time the table is built.
Using the Component Manager in Editable Mode
433

Altair Engineering
When you switch the Component Manager from the default read-only mode to editable mode (by selecting Editable from the Table menu), you can perform all the actions described in the section above, plus edit the attributes of the components listed in the table. To change the value of an attribute, select the attribute in the Assign Values drop-down, type the new value in the adjacent field, and click Set.
Filtering the List of Components

If you have a long list of components and you want to narrow down the list of components that appear in the table, you can use the filtering feature to specify the criteria for matching components. To set up a filter, from the Table menu, select Filter The Filter dialog box appears. Type a match value in the box next to the criteria by which you want to filter.
How Do I Create a new component card with the Component Manager Edit a component card
See also ANSYS Utility Menu ANSYS Interface Overview
Altair Engineering

434
To Create a Component Collector
To use the Component Manager to create a component collector:

1. 2. 3. 4. 5. In the ANSYS Utility Menu, click Component Manager. The Components dialog appears, listing all components. From the Action menu, select Create New.... The Create Component dialog appears. Type a name for the component in the Component name field. In the Element reference number field, select the number of the element type you wish to associate in the component. In the Real set number field, select a real set number from the pull-down menu. This list shows only applicable real sets for the selected element type. For elements that support sections, this field is optional. In the Material reference number field, select a material property card from the pull-down menu. For elements that support sections, select a section reference number from the Section reference number field. For these elements, you do not need to provide a real set number. Click the color block in the Color field to choose a color to assign to the component. Click Apply to create the component. Click Close to close the Create Component dialog.
6. 7. 8. 9.
To use HyperMesh panels to create a component collector:

1. 2. 3. 4. 5. 6. 7. Click the button to open the collectors panel, or click Collectors, then click Create and Component. Type a name for the component in the comp name = box. Choose a color for the component collector. Click card image = to select the only available card image, HM_COMP. Click property = to select an existing property. Click the material = button to select an existing material. Click create to create a component without component attributes associated to it, or click create/edit... to open to card image to assign attributes to the component. If you click create/edit, follow these steps: Click on the yellow Type button to see the list of element reference IDs. Select the element reference number of the element type to associate with the component. Next, assign a real set to the component by clicking on the yellow $REAL button and choosing a set from the list. For elements types that support both real sets and sections, a check box is available. When you select the check box, the Section tab appears. For elements that take only sections, the Section tab appears in place of $REAL button.
435

Altair Engineering
8.
Click return to exit the component card image.
Altair Engineering

436
To Create a Component Card with the Component Manager

1. In the ANSYS Component Manager, click the Action menu and select Create New.... The Create Component dialog appears.
2. 3. 4. 5. 6. 7. 8.
Type a name for the component in the Component name field. Select an element type in the Element reference number field. Select a real set in the Real set number field. Select a material in the Material reference number field. Select a section in the Section reference number field. Click the button in the Color field to select a color for the component that will be used in HyperMesh. Click Create. Click Close to go back to the Component Manager.
437

Altair Engineering
To Edit a Component Card

1. 2. 3. 4. 5. Click anywhere in the components row in the Component Manager table to select it. If not already in Edit mode, click Table and Editable. In the Assign Values drop-down, select a field to modify. In the adjacent field, type or select the new value. Click the Set button. The new value appears in the table.
Altair Engineering

438
ANSYS Material Macro

The Material macro creates and defines material cards.
This macro lists the existing materials in the model in a table and displays the material set number, type, and name for each material. From this macro dialog, you can create a new material, edit an existing material, or delete a material. Rows can be sorted by set number, material type and name columns. The following buttons are available on the Material macro dialog: Help New Provides information about the macro. Opens the Create Material dialog, from which you can specify parameters for a new material and create it. Opens the Edit Material dialog, from which you can review and change parameters for an existing material that is selected in the table. Refreshes the HyperMesh database with changes you made through the Material macro. You must click this button before closing the dialog to successfully export the ANSYS deck. Deletes the material that is selected in the table. Closes the Material macro dialog.
Edit
Refresh
Delete Close
Right-clicking on a row displays a context sensitive menu with the option to delete unused materials. Selecting this option can help you clean up your model by deleting materials. You can also edit materials, edit material properties, and delete materials from the menu that appears when you right-click in the table when a row/material is selected.
439

Altair Engineering
Altair Engineering

440
Create Material Dialog

Create new materials from the Material dialog. Specify the following options and click Create to create the material and return to the Material macro, or Create/Edit to create the material and open the card image panel in HyperMesh to specify the materials properties. Material Set No Type a number for the material set. If you do not specify a value, a number will be automatically provided that is one higher than the highest current material set number. Type a name to identify the material. Select MP or MPDATA depending on the material card you want to use.
Material Name Material Type
441

Altair Engineering
Edit Material Dialog

Edit existing materials from the Edit Material dialog. Specify the following options and click Update to save the changes. Then click Close to return to the Material macro. You can also click Edit Material Properties to open the card image panel in HyperMesh to modify the materials properties. Material Set No This field is initially populated by the reference number of the material card that you have chosen to edit. You can change the number to any other reference number if the number is not already used by an existing material card. This field is initially populated with the current name of the material. You can modify the name of the material. You can change the card image type.
Material Name
Material Type
If you make changes to a material, you must click Update to reflect the changes in the card image.
Altair Engineering

442
ANSYS Section Macro

The Section macro creates and defines section cards for beam and shell sections. You can create new section, edit existing sections, and use the HyperBeam application to create and edit beam section and associate them to section cards.
The following buttons are available on the Section macro dialog: Help New Provides information about the macro. Opens the Create Section Dialog, from which you can specify parameters for a new section and create it. Opens the Edit Section Dialog, from which you can review and change parameters for an existing material that is selected in the table. Refreshes the HyperMesh database with changes you made through the Material macro. Deletes the section card(s) that is selected in the table. Closes the Section macro dialog.
Edit
Refresh
Delete Close
Right-clicking on a row displays a context sensitive menu with the option to delete unused sections. Selecting this option can help you clean up your model by deleting unused sections. You can also edit sections, edit section properties, and delete sections from the menu that appears when you right-click in the table when a row/section is selected.
443

Altair Engineering
See also ANSYS Utility Menu ANSYS Interface Overview Create Section Dialog Edit Section Dialog To Create a SECDATA Card with the Section Macro
Altair Engineering

444
Create Section Dialog

Create new beam, shell or pretension section from the Create Section dialog. Specify the following options and click Create to create the section card and return to the Section macro, or Create/Edit to create the section card and open the card image panel in HyperMesh to specify section properties. Section Ref No Type a reference number for the section. If you do not specify a value, a number will be automatically provided that is one higher than the highest current section ID number. Type a name for the section. Select the type of section to create: Beam , Taper, Shell or Pretension . (This selection only applies to beam sections.) Choose a subtype from the drop-down list. (This option is only available if Beam Section is selected.) Select the check box to define the section with HyperBeam. Then select: New Section to create a section in HyperBeam and associate it to the section card image. Existing Section to select an available HyperBeam section of the chosen sub-type in the Sub Type field. When you click Create, a section card is created with the selected HyperBeam section or if you click Create/Edit, the card image is opened in HyperMesh.
Section Name Section Type
Sub Type
Define by HyperBeam
When you are in the HyperBeam application, it is possible to create
445

Altair Engineering
multiple HyperBeam sections. However, only the most recently created section is attached the section card.
Altair Engineering

446
Edit Section Dialog

Edit existing beam, shell or pretension sections from the Edit Section dialog. Modify the following options and click update to save the changes. Click return to return to the Section macro. You can also click Edit Properties to open the card image panel in HyperMesh to edit the sections properties. Section reference number: This field is initially populated by the reference number of the section card that you have chosen to edit. You can change the number to any other reference number if the number is not already used by an existing material card. This field is initially populated with the current name of the section. You can modify the name of the section. You can change the type of section to create. (This selection only applies to beam sections.) You can select another subtype from the drop-down list. (This option is only available if Beam Section is selected.) Select the check box to modify the section definition with HyperBeam. Then click Edit HyperBeam to modify the section in HyperBeam. If you edit a section card that was created with HyperBeam sections, then this check box is initially selected. However, you can clear the check box and make updates via the card image or vice versa. If you make changes to a section, you must click Update to reflect the changes in the card image.
Section name:
Section type: Sub type:
Define by HyperBeam
447

Altair Engineering
Altair Engineering

448
To Create a SECDATA Card with the Section Macro

1. From the ANSYS Utility Menu, click the Section... button. The Section dialog appears. 2. To create a new section card click the New... button at the bottom of the window. The Create Section dialog appears. 3. 4. 5. 6. 7. Type a reference number for the section in the Section reference number field. A number will already be provided by HyperMesh, but you can replace this value. Type the name for the section card in the Section name field. Select the type of section you want to create: Beam or Shell. If you chose Beam in step 5, then select a Sub type from the pull down menu. Shell sections do not have subtypes. At this stage you need to decide if you want to associate a HyperBeam section to the section card image you are creating. If you do not want to use HyperBeam sections, clear the Define by HyperBeam check box and skip to step 10. To use a HyperBeam section, select Define by HyperBeam . If you have already created sections in HyperBeam of the selected subtype, you can associate that section with the new section card image. (To create a new section, skip to step 10.) Select the existing section option and choose an existing HyperBeam section from the pull-down menu. Skip to step 10. To create a new section in HyperBeam and associate it to the section card image you are creating, select the New section option and click Create to create a section without properties defined, or Create/Edit... to edit the properties in the section card before saving. The HyperBeam application opens. Create the section and exit from HyperBeam. Click return in the HyperBeam panel in HyperMesh to go back to the Create Section dialog. Skip to step 11. 10. Click Create to create a section without properties defined, or Create/Edit... to edit the properties in the section card before saving. The following images indicate the location of the value fields in the SECDATA card (W1, W2, t1, t2, etc). I Beam HREC Beam
8. 9.
449

Altair Engineering
T Beam
L Beam
Z Beam
CHAN Beam
Altair Engineering

450
CTUBE Beam
CSOLID Beam
QUAD Beam
RECT Beam
451

Altair Engineering
HATS Beam
11. In the Section dialog, click Close to return to HyperMesh.
Altair Engineering

452
ANSYS Real Sets Macro

The Real Sets macro creates property card images for all elements that the ANSYS interface supports.
With this macro, you can view the real constant values of existing real sets, create new real sets, and edit the properties and reference numbers of existing real sets. The Real Sets macro dialog displays the real set, reference numbers, element type of the property set, and the real constant values for that element type. Rows can be sorted by set name, set ID and the element type column. The following buttons are available on the Real Sets macro dialog: Help New Provides information about the macro. Opens the Create Real Sets dialog, from which you can specify parameters for a new real set and create it. Opens the Edit Real dialog, from which you can review and change parameters for an existing real set that is selected in the table. Allows you to export the table in .csv format Refreshes the HyperMesh database with changes you made through the Real Sets macro. Deletes the real set(s) that is selected in the table. Closes the Real Sets macro dialog.
Edit
Export... Refresh
Delete Close
Right-clicking on a row displays a context sensitive menu with the option to delete unused real constants. Selecting this option can help you clean up your model by deleting unused real constants.
453

Altair Engineering
You can also edit real sets, edit real constants, and delete real sets from the menu that appears when you right-click in the table when a row/real set is selected.
Altair Engineering

454
Create Real Sets Dialog

Create new real sets from the Create Real Sets dialog. Specify the following options and click Create to create the real set and return to the Real macro, or Create/ Edit to create the real set and open the card image panel in HyperMesh to specify the real constants for the element type. Real Set No Type an identification number for the real set. If you do not specify a value, a number will be automatically provided that is one higher than the highest current real set ID number. Select an element type from the drop-down list for which a real set is to be created. The element types are listed in groups sorted by type, as shown in the image below.
Element Type
455

Altair Engineering
Edit Real Sets Dialog

Edit existing real sets from the Edit Real Sets dialog. Modify the following options and click Update to save the modified real set. Then click return to return to the Real Sets macro. You can also modify the real constants by clicking the Edit Real Constants button, which opens the card image panel. Real Set No This field is initially populated by the reference number of the real set that you have selected to edit. You can change the number to any other reference number that is not already used by an existing real set. This field is initially populated by the element type of the real set that you have selected to edit. You can change the element type by selecting a new element type from the drop-down list. The element types are listed in groups sorted by type, as shown in the image below.
Element Type
If you make changes to a real set, you must click Update to reflect the changes in the card image.
Altair Engineering

456
ANSYS ET Type Macro

The ET Type macro creates HyperMesh card images for ANSYS element types.
The ET Type macro dialog displays the ET type identification number, the element type name, and the key option values for each element type. From this macro dialog, you can create card images for any element type that HyperMesh supports, view existing ET types along with their reference numbers and key options, edit existing element types, or delete element types. Rows can be sorted by ET Type name, ID and the element type column. The following buttons are available on the ET Type macro dialog: Help New Provides information about the macro. Opens the Create ETType dialog, from which you can specify an element reference number and key options for a new element type and create it. Opens the Edit ETType dialog, from which you can review and change the reference number and key options for an existing element type that is selected in the table. Allows you to export the table in .csv format Refreshes the HyperMesh database with changes you made through the HyperMesh panels. Deletes the element type(s) that is selected in the table. Closes the ET Type macro dialog.
Edit
Export... Refresh
Delete Close
Right-clicking on a row displays a context sensitive menu with the option to delete unused ET types. Selecting this option can help you clean up your model by deleting unused ET types.
457

Altair Engineering
You can also edit element types, edit key options, and delete element types from the menu that appears when you right-click in the table when a row/element type is selected.
Altair Engineering

458
Create ETType Dialog

Create new element types from the Create ETType dialog. Specify the following options and click Create to create the element type and return to the ET Type macro, or Create/Edit to create the element type and open the card image panel in HyperMesh to specify the key options for the element type. Element Ref No Type an identification number for the real set. If you do not specify a value, a number will be automatically provided that is one higher than the highest current real set ID number. Select an element type from the drop-down list. The element types are listed in groups sorted by type, as shown in the image below.
Element Type
459

Altair Engineering
Edit ETType Dialog

Edit existing element types from the Edit ETType dialog. Modify the following options and click Update to save the changes to the element type. Then click return to return to the ET Type macro. You can also click Edit Key Options to modify the key options for the element type in the HyperMesh card image panel. Element Ref No This field is initially populated with the reference number of the element type you have selected to edit. You can change the reference number to any number that is not already used by an existing element type. This field is initially populated with the type of the element type you have selected to edit. You can select another element type from the drop-down list. The element types are listed in groups sorted by type, as shown in the image below.
Element Type
If you make changes to an ET Type, you must click Update to reflect the changes in the card image.
Altair Engineering

460
ANSYS Convert to Special 2nd Order Macro

Models created for the ANSYS solver often contain second-order pyramid and tetra elements in which most sides contain "mid-side nodes". These types of elements exist in a transition layer between the first-order hexa and second-order tetra elements, as shown below.
461

Altair Engineering
Beginning in HyperMesh 8.0, these types of elements are supported and preserved in the model. HyperMesh can import: Pyramid-shaped SOLID95 and SOLID92 elements with side edges containing mid-side nodes and bottom (base) edges that do not contain mid-side nodes Tetrahedron elements with one or more edges that do not contain mid-side nodes SOLID95 (special type) SOLID187 (special type) These special elements will be imported as full second-order elements, including mid-side nodes. Imported full second-order elements are exported as special elements, thereby restoring the original element configuration. Similarly, special second-order elements created in HyperMesh are also exported as special second-order elements. When you run the Convert to Special 2nd Order macro, a mesh matching is used to remove the mid-side nodes at the shared edges between these first and second order elements. Follow these steps to complete a full conversion: 1. 2. 3. 4. 5. 6. 7. Mesh the part for first-order with hexa or penta elements. Place these elements in a collector with the correct element type (SOLID45). Mesh the mating volume with second-order tetra elements. Place this mesh in a separate component with the correct element type (SOLID95 or SOLID92). Ensure that the two mesh patterns have a common layer with shared edges between. From the ANSYS Tools page of the Utility Menu, click the Convert to Special 2nd Order macro. Select the first-order component from the drop-down menu that shares a common face with the secondorder meshed component. Select the second-order meshed component in the next drop-down menu and click apply. The special order elements are generated. Export the file. Read it in the solver and check the elements.
Altair Engineering

462
The following images show examples of proper meshing for the above procedure.
463

Altair Engineering
ANSYS Contact Manger

The Contact Manager utility helps you create new contact pairs and manage existing contact pairs. You can create 2-D and 3-D contact pairs with Surface to Surface and Point to Surface options. You can also define contacts using the Pilot Node option. Existing contact pairs are listed in the Contact Manager table according to their target and master components, color, ET type used, property cards, material and pilot node name, if any. You can update any of these columns and as well as element key options, properties and materials of contact pairs at any time. You can view the contact normal an reverse with the buttons provided in the Contact table. You can also choose to create a Symmetry contact pair during creation of the contacts. By selecting Yes to the Symmetric Contact option during creation, two pairs of contacts will be generated. Contact elements in the first pair will be target elements in the second pair. Target elements in first pair will be the contact elements in the second pair. Different properties and ET types will be created for the second pair. You can update the contact pair later with desired properties and contact options. To create a symmetry pair, the selected elements need to meet all the element configuration requirements.
To run the Contact Manager:

1. From the Utility Menu, click Contact Manager.... The ANSYS Contact Manager opens. 2. To create a new contact pair, click New The Create New Contact Pair window opens.
Altair Engineering

464
3. 4. 5. 6. 7. 8. 9.
Under Creation method: select either Flexible or Pilot node. In the Contact type: field, select 2D or 3D. In the Create from: section, select whether to create a surface to surface contact pair or a point to surface contact pair. Under Symmetric Contact, select Yes or No. To select the target body components, click the Pick Target button. The component selector panel opens. Click the yellow comps button and select the components that belong to the target component elements. Click proceed. The Target Elements Selection dialog appears.
10. Click the yellow Elements button. The Elements selector window opens. 11. Click the yellow elems button and select the target elements of the contact pair. 12. Click proceed. 13. In the Target Elements Selection dialog, click Next > . The Target Component Details dialog opens. This window displays default Target component name and color, but you can alter these if desired. You can also modify the ET Type name and the ID of the target component.
465

Altair Engineering
14. Click Next > . 15. In the Contact Components Selection dialog, click the yellow Components button. The Component selector window opens. 16. Click the yellow comps button and select the components to assign as the target body. 17. Click proceed. 18. Click Next > . 19. In the Select Contact Elements dialog, click the yellow Elements button. The Elements selector window opens. 20. Click the yellow elems button and select the elements to assign as the contact surface elements. 21. Click proceed. 22. Click Next > . The Contact Component Details dialog opens. This window displays the default contact component name and color, but you can alter these if desired. You can also change the ET type and the ID of the contact component. 23. Click Next > . The Contact Property dialog opens.
Altair Engineering

466
24. Enter the values for items shown. You can create a new property, or create a new one based on an existing property, which helps expedite the process. 25. Click Next > . The Contact Material dialog opens.
26. To define a new material, click New under Define Material. Enter a name in the Name: field and enter values in the other fields. Select None to skip defining a material. Click Next > . 27. Click Next > . The Summary window opens. A summary of the target and contact elements is shown. 28. Click Exit to close the Contact Manager, or click the Restart button to step through the process again. The contact pair just created is now displayed in the ANSYS Contact Manager dialog.
467

Altair Engineering
See also Auto Contact - ANSYS Interface To Set Up an Auto Contact Run Auto Contact Browser Modifying Auto Contact Entities
Altair Engineering

468
Auto Contact - ANSYS Interface

Auto Contact is functionality within the ANSYS user profile that allows you to quickly and easily create interactions between several parts of your model. Based on a proximity distance, Auto Contact will search the model and automatically define contact elements from identified components. The interactions and surfaces are placed into a temporary Auto Contact Browser, where you can review the pairs and make adjustments as needed. Each contact element pair will be created with a contact and target element on each selected element surface. Contact element options (ET types) and contact property (REAL sets) are simultaneously created with the contact pair assigning default values. You have to edit these options and properties using the Contact Managers edit options if you want to assign different values other than the default. Similar properties (REAL sets) are shared by both contact and target elements. Material cards are also generated during the contact pair creation. You have to edit the material card to set the correct material property values. Currently, only surface to surface 3D contact elements can be created. Future releases will be enhanced to add other contact element types.
The Auto Contact dialog contains the following buttons: Find Cancel Searches the model for interacting components Closes the Contact Pair dialog without updates
469

Altair Engineering
Remove Selection icon
Removes selected components from the table. You can use the CTRL and Shift key to select multiple items in the table. Highlights the selected component in the graphic area. All other components are grayed out. You can use the CTRL and Shift key to select multiple items in the table. Right-click to return the model to normal display.
Review Selection icon
Help icon
Opens the Auto Contact online help.
See also ANSYS Contact Manager To Set Up an Auto Contact Run Auto Contact Browser Modifying Auto Contact Entities
Altair Engineering

470
To Set Up an Auto Contact Run

1. 2. 3. 4. 5. Load the Ansys user profile. Click Contact Manager in the ANSYS Utility Menu. Click Auto. This opens the Auto Contact dialog. In the Contact Type: field, select the type of contact pair to create. Click the yellow components button to select your components. The components are automatically placed in the Component table in the Auto Contact dialog. The proximity distance is the maximum distance between two selected components. When you create the pair, any surfaces that are farther away than the value entered here will not be created as a contact pair. The default value is zero.
6. 7. 8.
In the Maximum reverse angle field, enter a value. If the angle between two normals of elements or element faces exceeds this value, the element will not be added to the master or slave surface. Click Find. The status bar activates and the Auto Contact Browser opens. Use the Auto Contact Browser to make any necessary adjustments to the interface and surfaces. When finished modifying, click Create. The interfaces and surfaces marked as Accepted are created. The Contact Manager window reopens with the new information listed.
See also ANSYS Contact Manager Auto Contact
471

Altair Engineering
Auto Contact Browser Modifying Auto Contact Entities
Altair Engineering

472
Auto Contact Browser

The Auto Contact Browser provides options for viewing and modifying the contact pairs identified in the Auto Contact process. It contains the following columns: Name Lists the name of the interfaces, surfaces and surface interactions that were assigned. Underneath the interface name are the temporary surfaces included in that interface. Red indicates a slave surface, and blue indicates a master surface. Accept When the Accept box is checked, the Interface will be included in the creation process. Color assigned to the interaction and surfaces ET Type
Color ET Type Real Set Mat
Material assigned
The Auto Contact Browser contains the following icons: Options icon This opens the Options dialog.
Enter a new feature angle or customize the transparency for a selected entity. Click OK when finished. Highlight Elements icon Review Highlights the elements stored in selected entities in the graphics window. You can use the CTRL and Shift key to select multiple items in the table. Review of elements stored in the selected entities. Elements are highlighted
473

Altair Engineering
Elements icon
by color; all other components are grayed out. You can use the CTRL and Shift key to select multiple items in the table. Review and Highlight are mutually exclusive. It is also possible to switch both options off. This is helpful when working with big models.
Fit View to Elements icon Display All Elements icon Display Components with Elements icon Display Only Elements icon Select Elements Manually icon Add by Adjacent icon
Automatically zooms in to the elements stored in the currently selected items. In combination with the Highlight Elements or the Review Elements option, current contents remain unchanged on the screen. Highlights or reviews the elements referred by an interaction or surfaces and shows the components they belong to. All other components will be masked.
Only elements are highlighted or reviewed. The rest of the component and other components will be masked. Opens the Element selection panel so that individual elements can be added/ removed manually. Click proceed when finished.
Adds the elements adjacent to the surface to the selected surface. Right-click to undo one time.
Add by Face icon
Adds the adjacent face to the selected surface. Right-click to undo one time.
Recheck icon
Opens the Auto Contact dialog to recheck the select interfaces. Recheck will either add more contacts to the existing contacts for modify the existing ones. You can select interfaces from the browser, and the GUI will automatically populate the components that the interaction was based on. This helps modify an existing interface.
See also ANSYS Contact Manger Auto Contact - ANSYS Interface To Set Up an Auto Contact Run Auto Contact Browser Modifying Auto Contact Entities
Altair Engineering

474
Modifying Auto Contact Entities

Right-clicking on an item in the Auto Contact Browser displays a context sensitive menu which offers options for modifying the surfaces and contact pairs. Rename Delete Swap Master - Slave Rename an existing entry. Delete items from the browser. Allows you to switch the surfaces identified as master and slave. When selected, you will see the surfaces flip from the master/slave positions in the browser. Select multiple entities by using the CRTL and Shift keys when clicking on entities. Edit Faces Allows you to manually edit the faces of the surfaces. This opens the elements selection panel where you can select and deselect the elements to include on the face of the surface. Adds adjacent elements to the selected surface. Adds all elements to a selected surface, until the feature angle exceeds the value (the feature angle can by set by clicking the Options icon). Automatically accept or reject all items in the Auto Contact Browser. Reverses the current selections in the Accept column. Expands or collapses folders in the Auto Contact Browser.
Add by Adjacent Add by Face
Accept All/None Reverse Expand All/ Collapse
See also ANSYS Contact Manger Auto Contact - ANSYS Interface To Set Up an Auto Contact Run Auto Contact Browser
475

Altair Engineering
Modal Analysis Tool

The Modal Analysis Setup tool can be used to set the modal analysis in the model. You can use this tool to define modal analysis cards, such as extraction methods, frequency range, modes to expand, iterative solver tolerance, modes significance level and solution control options. All commonly used cards and options for modal analysis in the ANSYS solver are listed in the dialog. You do not need to search for relevant cards in the control card list, and you do not need to know the control cards that are used for modal analysis. All other implied ANSYS cards, such as /SOLU, SOLVE are set up automatically. If any option or card is not required, then default values will be exported. For example: in the image shown below, if Mass and stiffness matrix multiplier value need not required If Modal analysis needs to be carried out in the ANSYS solver, this dialog needs to be set up before exporting the model to an ANSYS deck . This GUI can be accessed in HyperMesh from the Tools menu by selecting Analysis Setup.
Altair Engineering

476
LS-DYNA Utility Menu

The LS-DYNA Utility Menu on the Utility tab is automatically loaded when you select the LsDyna user profile, and contains shortcuts and tools that can help simplify LS-DYNA tasks. Set the user profile from the User Profiles... option of the Preferences pull-down menu. The LsDyna user profile sets the FE input reader to DYNA KEY and loads the dyna.key (ver 971) FE output template and LS-DYNA Utility Menu. Also, the graphical user interface becomes LS-DYNA focused, renaming or removing some panels and/or options. The entire ALE Setup is available only when the LsDyna user profile is loaded.
Tools Menu
The LS-DYNA Utility Menu contains a Tools menu in addition to the standard HyperMesh Utility Menu. This menu includes special time-saving setup macros and other features that are specific to an LS-DYNA analysis. The following macros are available: Error Check Part Info Name Mapping Checks the LS-DYNA data deck for errors. Displays statistics of a selected part. Converts differing part names to either the HyperMesh name or the LSDYNA name. Creates a new part from the properties of an existing part. Creates a new component quickly. This macro allows you to replace the elements in an existing component (*PART) with new elements. This macro converts a selected portion of elements to rigid. It performs the following: Organizes elements to rigid components Creates and assigns the required *MAT_RIGID cards Converts welds to *CONSTRAINED_EXTRA_NODES See Convert To Rigid Flow Chart and Use the Convert To Rigid macro Find free Finds the welds (*Constained_Spotweld), rigids (*Constrained_Node_Sets & *Constrained_Nodal_RigidBody), and rigidlinks (*Constrained_Node_Sets and *Constrained_Nodal_RigidBody), and checks if any of its nodes are free (not connected to any other entities). The display is cleared and then only free 1d elements are displayed. Finds the welds, rigids, and rigidlinks that are free as described above (
Clone Part Create Part Part Replacement
Convert To Rigid
Find Fix Free
477

Altair Engineering
Find free macro) and corrects them. These elements are corrected as follows: All 2-noded rigid and weld elements that have one free node are deleted. For the rigidlink elements that have free nodes, those nodes are removed from the rigidlink element. A check is performed for any rigidlinks with only one node and they are deleted. Fix Incorrect Finds: Rigid elements (rigids, welds) that are connected to other rigids and combines them into one rigid element. Rigid elements that are connected to other xtra_nodes_to_rigidbodies and converts them to xtra_nodes. Rigid elements connected directly to rigid component (MAT 20) will be converted to xtra_nodes. RLs With Sets The macro, RLs with Sets, finds all the rigid and rigidlink elements that are not attached to a set and converts them so that they are attached to a set. Displays a tabular list of all the components that exist in the model along with their properties and materials. Allows you to easily create and edit materials. Converts all the contacts that are defined using node sets or segment sets in the Entity Sets panel to master and slave elements in groups so that they can be easily displayed on/off.
Component Table
Material Table C-Interfto50
See also HyperMesh Tab Area
Altair Engineering

478
Error Check
The Error check dialog checks your LS-DYNA deck for potential problems with components, properties, materials, rigids, joints, boundary conditions, and other entities and reports them on-screen. The report identifies the problem entity by ID, describes the error, and then enables you to isolate the entity in the model and quickly make changes. Click Error check on the LS-DYNA Utility Menu to open the dialog as shown below:
Select the types of errors for which you want to search and click Check . When the check is complete, the results appear on the Errors tab of the dialog, as shown below:
479

Altair Engineering
Each error in the list is a hyperlink that, when clicked, highlights the affected visualizations in the model and opens the relevant card image or panel for correcting the error. You can systematically click on each error in the list, correcting them as you go. On the Settings tab, click Check again to verify that the errors were corrected. If you want to restore the full view of the model including all components, click View - Show full model button on the Errors tab of the dialog. To return to the previous view, click View - Restore View. Use the Options menu button to update or saving settings for the Error Check dialog. You can specify minimum and maximum values for the material check and a maximum value for the distance of a constrained extra node to its part. To save the current settings, choose Save Settings from the Options menu button and specify a file name and location. You can also load previously-saved error check settings. Click the Close button to close the Error Check dialog.
See also LS-DYNA Utility Menu
Altair Engineering

480
481

Altair Engineering
Part Info
The Part Info macro summarizes a parts statistics in a dialog. 1. 2. 3. To start the macro, click Part Info on the Utility Menu. Click component on the main menu area to select a component or click a component in the graphics area to select it. Click proceed. The Part Information dialog appears, which lists the part ID, name, thickness, and material type. 4. 5. Tip To view additional statistics about the part, click the More Details tab. To display statistics for a different part, select the part in the graphics area or the components selector and click proceed again. Click the middle mouse button instead of the proceed button to quickly select components.
Altair Engineering

482
Name Mapping
LS-DYNA and HyperMesh maintain separate names for solver keywords mapped to named HM entities. To make the names consistent, you can run the Name Mapping macro, which provides the ability to change names for various entity types to either the HyperMesh name or the LS-DYNA name. This macro can be accessed by clicking Name Mapping on the Utility Menu when the LsDyna user profile is loaded. Select whether you want to convert the HyperMesh names to LS-DYNA names or vice-versa by choosing the corresponding radio button at the top of the dialog. Then select the entity group(s) you want to update by clicking its row in the entity list. Click Convert selected; the names for all the entities that exist in the selected groups are automatically changed to either the HyperMesh or LS-DYNA format, depending on which setting is active. The Custom option provides the ability to change individual entities instead of an entire entity group. A new dialog appears when you click the Custom button. All the entities of that type are listed in a new table, from which you can select individual entities and click Edit to open the card image and manually change the name or click Apply to automatically match names based on the current setting of the main Name Mapping dialog box. Note: If there is no card image available, the LS-DYNA name does not appear in the Custom table and name mapping is not available.
483

Altair Engineering
Clone Part
The Clone Part macro enables you to quickly create a new part from the properties of an existing part. It can be accessed by clicking Clone Part on the Utility Menu when the LsDyna user profile is loaded. Select the existing part on which to model the new part by clicking the button, which opens a dialog listing all the existing components. Select a component from the list and click OK. Type a name for the new part in the New Part field and click the color icon to select a color for the component. Select whether to duplicate the material and section properties or to re-use the original material and section properties. Duplicate means that a new material and section is created (the name is suffixed with .n version numbers and new IDs are used) with the same properties, while Reuse refers to the same material and section as the original. Select whether to duplicate the elements. Duplicate elements will make a copy of the elements from the selected part to new part in the same location. Click Create to either create or create and edit the card.
Altair Engineering

484
Create Part
The Create Part macro enables you to create components on-the-fly. It can be accessed by clicking Create Part on the Utility Menu when the LS-DYNA user profile is loaded. Type a name for the new component in the Part name field and select a color by clicking the adjacent color icon. Select a section in the Section field by choosing Create New (create a new section), Same As (create a new section based on an existing section), or Model (select an existing section) from the selection menu. Select a material for the component in the Material field by the same method as described above for the Section field. Click Create>> to either create or create and edit the card.
485

Altair Engineering
Part Replacement
The Part Replacement macro allows you to replace the elements in an existing component (*PART) with new elements; typically replacing a similar part remeshed or slightly reshaped. It can be accessed in the Tool macro page when the LsDyna user profile is loaded. This macro not only replaces nodes and elements between parts, it also restores the referenced items in the original model to the new part, e.g. 1-D connections, distributed mass, contacts, loads, and database history. A message log is provided, which lists the entities being replaced and reconnected as well as cases that required or will require user interaction.
To replace parts with the Part Replacement macro:

1. Select the old and new part. Both parts must be available in the database. Identify the Old Part and New Part. The name and color of the components are reported once the parts are selected. Click Apply.
Click the icon
, to turn on/off the corresponding part from the graphics area.
Click View log anytime during the part replacement process to view a list of events. 2. Assign the material and property. Specify which material and property to assign to the new part. In the example that follows, the material from the old part (ID 219) is retained and the property from the new part (ID 224) is selected.
Altair Engineering

486
Click Apply to accept the selection or click Next to skip this step and proceed with the part replacement process. Note that the IDs of the new and old part will be swapped. This automatically preserves any LSDYNA card that refers to this part ID directly or through a set of parts. 3. Fix 1-D connections and mesh-less welds. This step offers both an automatic and interactive reconnection to the new part for 1-D elements (e.g. beams, rigids, and springs) and mesh-less welds (beam type 9 and hexa). For Tolerance:, specify a tolerance value for the reconnection attempt.
Check Remesh new part to establish connection to allow a local remesh of the new part to restore connection.
487

Altair Engineering
If you select Remesh new part to establish connection, HyperMesh will locally remesh the new part to establish the connection. In this case, the tolerance specified is the projection distance between the end node of the 1-D and the closest element in the new part. A new element is created and the 1-D connection may be restored with a smaller tolerance value. If you do not select Remesh new part to establish connection, the value specified for the search tolerance will be the nodal distance between the end node of the 1-D element and the closest node in the new part. In this case, the 1-D element keeps its original ID and properties; only the node previously connected to the old part will be moved. Click Apply to replace the 1-D connection and the mesh-less welds within that tolerance and display the elements that cannot be fixed in red. Click the EID field to select the remaining elements, increase the tolerance, and preview the effect of the increased value on the 1-D elements.
Click Apply to use the defined tolerance to fix the elements displayed in green. A message reports the tolerance required to fix the selected elements. This tolerance is used to fix all the 1-D connections. Use a higher tolerance value to fix all 1-D elements that are still reported as failing or select one or more 1-D elements and click Interactive-fix.
Altair Engineering

488
Interactive-fix is recommended for cases where you want to directly monitor the nodes being connected and is only available for 1-D elements replaced using nodal tolerance. Unnecessary entities will be masked and the Replace panel will be opened. The 1-D element requiring an interactive fix will have one end already detached and a node of the new part can be selected as needed. You must select the 1-D end node as the first node and a node of the new part as the second node.
Use the Meshless welds tab to replace beam type 9 or a hexa used in a mesh-less connection. The same preview functionality described for regular 1-D connections is also available. Interactivefix and the Remesh new part for fix are disabled since they do not apply to this type of connection. A contact spotweld, materials, and properties for the mesh-less welds will also be created if the new part shows a different thickness or material information. Review the log file created during the part replacement to determine if any connections remain unfixed. 4. Fix mass elements. Masses attached to the old part can be connected to a new part using steps similar to the ones previously illustrated for 1-D elements. Specify a tolerance value for the mass element reconnection when prompted. The value specified for search tolerance will be the nodal distance between the node of the old part where the mass was originally located and the closest node in the new part. Click Apply to replace the masses within that tolerance and display the elements that could not be fixed in red. Click the EID field to select the remaining elements, increase the tolerance, and preview the effect of the increased value on the mass elements.
489

Altair Engineering
Click Apply to use the defined tolerance to fix the mass elements displayed in green. Use a higher tolerance value to fix all 1-D elements that are still reported as failing or select one or more 1-D elements and click Interactive-fix. A message reports the tolerance required to fix the selected elements. This tolerance is used to fix all the mass connections.
Additional Entities
The Part Replacement macro not only replaces elements, it also restores the referenced items in the original model to the new part. Contact and Rigidwall Since the IDs of the new and old part are swapped at the beginning of the part replacement process, most of the common contact definitions (*set_part_list) will be automatically preserved as the part ID did not change. In some instances, a contact or rigidwall may be defined by a set of nodes, set of elements, or set of segments. Consider the case of a contact node-to-surface, where the slave entity is defined using a set of nodes. The contact slave entity will be updated only if it contains every node of the old part. In all other situations, it is reported that the contact was not updated and the user must update interactively. A similar approach is used when a contact is defined using a set of elements or set segment (contactsurf). Database History
Altair Engineering

490
HyperMesh detects and fixes Database_history_nodes and Database_History_shell. To fix a history_node or history_shell, all the nodes/shells must follow the tolerance that you have specified. For shells, the tolerance will not be a nodal distance between nodes but the distance between the element centroid in the old part and its projection (if any) to the elements of the new part. Constrained_extra_node HyperMesh detects and fixes constrained_extra_node and constrained_extra_node_set. To fix a constrained_extra_node all its nodes must follow the tolerance that you have specified. Click Preview to identify the tolerance value required to fix a particular xtranode. Boundary Condition HyperMesh can detect and fix the following individual loads: temperature, moments, constraints, and forces.
491

Altair Engineering
To use the Convert To Rigid macro

This macro is used to convert deformable parts of an LS-DYNA model to rigid. 1. 2. 3. 4. 5. Click Tools in the Utility Menu. Click Convert To Rigid. Select the elements to convert to rigid and click proceed. Select an existing rigid component in the model for merging the newly created rigid body and Click Proceed. Click return.
The Convert To Rigid macro performs the following steps when the selected elements are converted to rigid. 1. For the selected elements, a check is performed on the comps for rigid (MAT_RIGID or matl20) or deformable materials (all, except matl20). If deformable materials exist, rigid materials (MAT_RIGID) are created with the properties from the original deformable materials. A check is performed for rigid materials that are already defined. If rigid materials are found, the comps and rigid materials are retained. Comps located partially within the window are split into two comps. The new comp has the same property (section ID) but new material (Material ID). For example, if A-pillar is partially within the window, then a new comp A-pillar_rig is created. A-pillar_rig is updated with newly created material. All the spotwelds and rigids located entirely within the window are removed. For example, *CONSTRAINED_NODAL_RIGID_BODY_option, *CONSTRAINED_NODE_SET, *CONSTRAINED_SPOTWELD, and *CONSTRAINED_GENERALIZED_WELD_option. For spotwelds that are connected from the deformable body to the rigid body, an extra node is created and referenced by the master rigid body. A check is performed to detect joints located partially or entirely within the window. Detected joints are deleted. A check is performed to detect springs located partially or entirely within the window. Detected springs are deleted. A check is performed to detect seatbelt elements (seatbelt elements, Retractor, Pretensioner) located partially or entirely within the window. Detected seatbelt elements are deleted. Master and slave comps are defined (for example, CONSTRAINED_RIGID_BODIES). You are prompted to select a comp for master rigid body. A slave set is created with the newly created rigid bodies (except the master rigid body comp). A message is displayed when the conversion is complete.
2.
3.
4. 5. 6. 7. 8.
9.
Altair Engineering

492
Convert To Rigid Flow Chart
493

Altair Engineering
Component Table
The LS-DYNA Component Table is an interactive tabular list used to represent LS-DYNA components with associated properties and materials. It is accessed by loading the LsDyna user profile and clicking the Component Table button on the LS-DYNA Utility Menu.
The table contains a variety of tools that allow you to review, edit, and update the model. The essential features are: LS-DYNA components with various associated properties and materials are listed in separate columns. You can select the column types from a set of available options. There are two modes of operation: review and editable . The review mode allows you to quickly review the component information without changing any values. The editable mode, allows you to change values for the selected components. There are enhanced selection, review, display, and filter options for components. Components can be sorted according to any available column. The current configuration is saved automatically to a file at the end of a session and recalled on reload. You can also save and load a configuration file. The table data can be export in CSV and HTML formats. Right click on the table to display menu options. All pull-down menu options are also available using a right click. Columns can be moved or swapped by holding the left mouse button on a column title and dragging it to the desired location. Columns can be resized by positioning the cursor along a column border, pressing the left or right mouse button, and dragging the border to a new position. The shift or ctrl key combined with a left click can be used to select multiple rows. The following tools are available in the LS-DYNA Component Table :
Table
Refresh Editable Regenerates the table with all the parts in the model Sets the table mode to editable mode, allowing you to change values for the
Altair Engineering

494
selected components Filter Configure Save Quit Enables the filtering GUI Allows you to specify the number and type of columns listed in the table Saves the information listed in the table in CSV or HTML format Quit the table function.
Selection
All None Reverse Displayed User Selects all rows or parts Selects none or deselects parts/rows that were previously selected Reverses the selection Selects the rows or the displayed parts User graphic interaction to select parts
Display
By default, the table is invoked with only the displayed parts. You can refresh the table to show a new part being displayed or use one of the following display commands. All None Reverse Show selection Show only Selection Hide selection By Material By Properties By Thickness Displays all the components in the model Turns off every component displayed Reverses the display of the part Displays the components of the selected rows Displays only the components of the selected rows Hides the components of the selected rows from the display Displays components sorted by material Displays components sorted by properties Displays components sorted by thickness values
495

Altair Engineering
Action
Delete Selection Deletes selected rows (parts) from the model
User
Set MatDB Path Opens a dialog on which you can set the location of an external database of material definitions. Updates the list of available materials in the Component Table .
Refresh Material List
Editable Mode The editable mode in the Component Table allows you to change values for all selected components at the same time. Select the Table > Editable option to open the Component Table in editable mode. Cells with a white background can be manually edited. When you click on an editable cell, it is selected with a cursor. Once a cell is selected, enter a value and press Enter. If you want to assign the same value to multiple components at once, select the column type and value from the Assign Values: pull-down menu and click Set. All the selected components will be updated with the assigned values.
Filter The Component Table supports advanced filtering based on available columns. The Table > Filter... menu option opens the Filter dialog as shown below.
You can write any valid string with a wildcard (*) in any of the available column types and click Apply to filter the table. For example, if you want to show all components that start with letter c and use material steel, you can use the dialog as shown below. Note that the filter strings are case-sensitive.
Altair Engineering

496
Show All turns off the filtering and displays all the components. Select the Table > Configure > Filter on top option to keep the Filter dialog posted after clicking Apply or Show All. Otherwise, it closes.
Configure Columns Column types can be selected from the Table > Configure > Columns... menu option. The table displays only the selected columns. The available columns types are: Title Vis Part name Part id Material name Material id Material type Thickness Section name Section id Section type Color Int points HGID Elem form Description Visualization status. 1 = display on, 0 = display off HyperMesh name of the component (maximum 32 characters) HyperMesh ID of the component Material name associated with the component Material ID associated with the component Material type associated with the component Thickness of elements specified in *section_shell *Section name associated with the component *Section ID associated with the component Type of the *Section associated with the component Component color Number of integration points specified for the *Section_shell Hourglass ID associated with component Element formulation for the *section of the component
497

Altair Engineering
Elems Nodes Mass cg_x cg_y cg_z
Number of elements in the component Number of nodes in the component Total mass of the component Center of gravity for the x coordinate Center of gravity for the y coordinate Center of gravity for the z coordinate
Components All or Displayed mode The Component Table lists components in two modes: All or Displayed. If All is selected from the Table > Configure > Components menu, the table will list all the components in the model. If Displayed is selected, only the visible components will be shown. Blank components are not shown in the Displayed mode even though their display status is on.
Altair Engineering

498
Material Table
The LS-DYNA Material Table enables you to easily create and edit materials. To access the Material Table , click Material Table on the Utility Menu. All the existing materials are retrieved and populated in the table. From the Material Table , you can also merge identical materials, search for duplicate materials, and change the properties of materials. When you first display the Material Table , all materials are listed in the table, showing the material's ID, name, type, description, list of components in which it is used, and the RHO, E, and Nu values. An example is shown below.
Materials in the table can be selected by clicking the row, which is then highlighted in blue. Many functions are performed by selecting materials in the table and choosing an option from the context menu or clicking a button below the table. shift+click and ctrl+click can be used to select multiple rows. Refer to the links below for details about using the Material Table .
How Do I... Sort materials Create a new material Edit a material's properties Merge materials Find duplicate materials See the load curve for a material Export data from the Material Table
See also Customizing Views of the Material Table Creating, Editing, and Loading Materials Managing Materials LS-DYNA Utility Menu
499

Altair Engineering
Altair Engineering

500
Customizing Views of the Material Table

The Material Table initially lists all existing materials, but you can sort and filter the list to more easily identify materials that you want to work with. Each of the columns in the table can be used to sort the list. Click the column heading to sort by that characteristic, such as ID number or material type. To view only materials of a particular type, select that type in the Material type drop-down at the top of the window. For example, if you want to identify materials that are not used so you can delete them, you can click the Comp used column heading to quickly group together all materials that contain the value "No", which indicates that none of the components use the material. Note: To view all material properties in the table, select a material type from the drop-down. When all material types are shown in the table, only the RHO (density), E (Young's modulus), and Nu (Poisson's ratio) properties appear. However, when a particular material type is displayed, all the relevant properties for that material type also appear in the table, as shown in the image below.
The Material Table also enables you to view the model's components based on the material used. These options are available by selecting Display from the menu that appears when you right-click anywhere in the table. Options include: viewing only the selected materials hiding the selected materials viewing all or none of the materials adding the selected materials to the current display reversing the current display option. Once you make your selection, the corresponding components appear or become hidden in the graphics area.
How Do I... Sort materials Merge materials Find duplicate materials See the load curve for a material
501

Altair Engineering
Export data from the Material Table
See also Creating, Editing, and Loading Materials Managing Materials LS-DYNA Material Table
Altair Engineering

502
Creating, Editing, and Loading Materials

You can create, edit and load materials all from within the Material Table . Materials can be added or modified with the Create/Load and Edit buttons or by selecting the same options in the menu that appears when you right-click anywhere inside the table. To save time, you can choose the Same As selection to begin creating a material with the same properties as the currently-selected material in the table. When you create a new material, you specify a name and the type of material. The materials are conveniently organized into categories, including groups of recently used materials and only materials that exist in the model. These categories are further listed by the LS-DYNA keyword or type identifier, as shown in the following image.
You can add the material to the table immediately by clicking Create or by going to the Card Image panel to specify its properties by clicking Create/Edit. At any time you can select a material in the table and click the Edit button to open the material's card image. In the card image, you can modify values for the keyword's variables. In addition, the material's load curve appears in a pop-up graph, as shown below.
503

Altair Engineering
How Do I... Create a new material Edit a material's properties See the load curve for a material Export data from the Material Table
See also Customizing Views of the Material Table Managing Materials LS-DYNA Material Table
Altair Engineering

504
Managing Materials
In addition to viewing, creating, modifying, and deleting materials, you can also identify duplicate materials, merge like materials into one, and rename materials. The names of materials and the material IDs can be edited directly in the table. (All other values must be edited with the Edit button, which opens the card image.) Materials that have the same properties can be identified using the Check duplicates button. This feature, which is only available when all materials are displayed in the table, finds all materials that have identical properties and returns them in result sets. You can then select each result set to view the matching materials. Optionally, you can merge the duplicate materials into one material using the Merge button, which is the same feature as described in the following paragraph.
When you select multiple materials from the table, you can merge them into one of the selected materials using the Merge As button. Typically this action is performed on materials with like properties to simplify a model, although it can be performed on dis-similar materials with all selected materials taking on the properties of one of the materials. When materials are merged into one, the remaining materials still exist and appear in the table, but do not have any components assigned to them.
How Do I... Sort materials Merge materials Find duplicate materials See the load curve for a material Export data from the Material Table
See also Customizing Views of the Material Table Creating, Editing, and Loading Materials LS-DYNA Material Table
505

Altair Engineering
Sort Materials
1. 2. Click the column heading of the criteria by which you want to sort. Click the column heading again to list the materials in reverse order.
See Customizing Views of the Material Table to learn about other ways to filter the list of materials in the table.
Altair Engineering

506
Create a New Material

You can create a new material, or create a new material based on an existing material. Both procedures are described below.
To create a new material:

1. 2. 3. Click Create/Load and select New from the menu. New fields appear at the bottom of the Material Table . Type a name for the material in the New Material Name field. Select a material type from the drop-down list. The list expands to categories of material types, and also sorts them by keyword or material ID. You can view the complete list of material types under the All category. Click Create/Edit to open the material card image to specify the properties, or click Create to add the material to the table without immediately specifying any properties. Click return to exit the Create/Load mode.
4. 5.
To create a new material based on an existing material:

1. 2. 3. 4. 5. Select a material in the table that you want to use as the basis for a new material. Click Create/Load and select Same as from the menu. New fields appear at the bottom of the Material Table . The material you selected appears in the Selected material field. Type a name for the material in the New Material Name field. Click Create/Edit to open the material card image to specify the properties, or click Create to add the material to the table without immediately specifying any properties. Click return to exit the Create/Load mode.
507

Altair Engineering
Edit a Material's Properties

1. 2. 3. Select a material in the table that you want to edit. Click the Edit button. The card image for the material appears and, if applicable, the load curve appears in a pop-up window. Modify values in the card image and click return to go back to the Material Table .
Altair Engineering

508
Merge Materials
1. 2. 3. 4. In the table, select the materials you want to merge. (Use SHIFT+click to select multiple, consecutive rows and CTRL+click to select non-consecutive rows.) Click Merge As. The Material Table expands to include new fields for merging materials. Select the material ID to use as the new material in the Retain material(id) field. Click the Merge button. The components for each of the selected materials are merged into the material you selected. The remaining materials still exist and are listed in the table, but they are not assigned to any components.
509

Altair Engineering
Find Duplicate Materials

1. 2. 3. Ensure that ALL is selected in the Material type field. Click the Check duplicates button. The Material Table expands to include new fields for handling duplicate materials. Choose a group number from the View materials in duplicate group field. The materials in that group appear in the table. (The results for the duplicates check are divided into consecutively numbered groups of the same material type.)
You can easily merge the duplicate materials using the Merge button. See How Do I Merge Materials for steps on using the merge feature. To view another result group of duplicate materials, select another group number from the View materials in duplicate groups field. That groups list of duplicate materials appears in the table.
Altair Engineering

510
See the Load Curve for a Material

1. 2. Select a material in the table for which a load curve ID has been defined. Click the Edit button. The load curve appears in a pop-up window.
511

Altair Engineering
Export Data from the Material Table

1. 2. 3. Select a material type or ALL from the Material type field to export only materials of a particular type or all materials, respectively. Right-click anywhere in the table and select Save and then CSV for comma- or semicolon-separated values or HTML for an HTML-based table. The Select output file dialog appears. Browse for or type a name in the File name field and click Save. The file containing material data is saved in the location you specified.
Altair Engineering

512
MADYMO Utility Menu

The MADYMO Utility Menu (madymo.mac) is loaded when you open the MADYMO user profile. It contains utilities, tools, macros, and shortcuts to display options. The menu and its utilities are fully customizable. The MADYMO Utility Menu contains two pages, Tools and Define Entities. Both menu pages contain the following Display: options used to control the display of entities in the graphics window. Body Elems Triads Shading Turns on and off all ellipsoids, planes, cylinders, and joints. Turns on and off all FE elements. Turns on and off all coordinate systems. Set to visualization mode for the entire model. Four modes are available: 0 1 2 3 Only Comps/MBs Performance graphics wireframe Shaded Shaded with mesh lines Shaded with feature lines
Turns off all entities except elements, ellipsoids, planes, cylinders, and joints. Removes all temporary nodes (a.k.a. 3-D location markers) Reduces display size of coordinate system and boundary conditions for modeling in meters. Colors all ellipsoids, planes, cylinders, and joints based on their rigid body reference. Also colors FE elements by part card.
Clear Temp Nodes Work in Meters
Autocolor
The Tools page contains a series of utilities and tools: Set Light Source Opens a window with button-based light source options. Click the icon button that corresponds to your preferred direction of the light source, and click the button that corresponds to your preferred level of specularity. Then click Close. Converts linear elements to ellipsoids. Each element becomes a new body with an ellipsoid. A joint is created between each body. The organize, delete, and mbs joints panels can then be used to move the created ellipsoids to a single rigid body, delete extra bodies and joints, or change the joint type. Used to rotate coordinate systems about their axes.
Elems to Ellipsoids
Rotate Systems
513

Altair Engineering
Resize Ellipsoids Mesh Ellipsoids
Expands/shrinks ellipsoids about their individual axes. Used to mesh ellipsoids. Mesh is created to represent the actual geometry of the ellipsoid. Turns on numerical ID display for specified coordinate systems. Useful for seeing which coordinate system is selected when selecting coincident coordinate systems. Applies contents of JNTPOS file to loaded model. Brings up file browser for selecting the JNTPOS file and applies the Euler parameters for the last time step on all joints contained in the file. Opens an editable table of all the rigid bodies in the model listing each body name, center of gravity, mass, and moment of inertia. Also contains noneditable fields for reviewing the body ID and parent body.
Display Syst IDs
Apply JNTPOS
Body Properties
Both the Define Entities and Tools pages contain Display: options, while the Define Entities page also contains buttons for creating new coordinate systems and location markers in 3-D space: The New Cord Sys: options allow you to create new coordinate systems. Parallel Global Creates new coordinate systems at specified nodes. The created systems are oriented parallel to the global system. Creates new coordinate systems at specified nodes. The created systems are oriented parallel to a specified local coordinate system. Opens the HyperMesh systems panel for created coordinate systems in any orientation by specifying three nodes or temporary nodes.
Parallel Local
From 3 Nodes
The New loc marker: options allow you to create new temporary nodes, which are used as location markers throughout HyperMesh. At Coord System At Ellipsoids Cover Ellipsoids At Body COGs At Other Creates a new marker at specified coordinate systems. Creates new markers at specified ellipsoids centers and axis. Covers ellipsoids with new markers. Creates new markers at specified rigid bodies center of gravities. Opens the HyperMesh create nodes panel for creating markers by entering coordinates (local or global), between existing nodes/temp nodes, on a plane, or on CAD geometry.
Altair Engineering

514
See also MADYMO Interface Overview
515

Altair Engineering
NASTRAN Utility Menu

The Nastran user profile contains two macro menus on the Utility Menu: Nastran1 and Nastran2.
See also: Nastran1 Page Nastran2 Page
Altair Engineering

516
Nastran1 Page
The following macros are available on the Nastran1 macro menu: Auto Property Creation Auto Property Creation If two or more components points to single property this utility will create a separate property for each component.
Analysis Setup Load Steps Browser BCTABLE Manager
Generate Nastran subcase definitions. Create, edit, and delete BCTABLEs from a convenient tabbed interface.
Model Editor
Part Replacement
Replace elements in a component/part (PSHELL) with new elements.
Rigids & Welds
Rigid Spider
Create a spider (RBE2 elements) around holes.
Comps, Props & Mats Info
PartInfo
Review details for a specified part.
Component Table Property Table Material Table
Create, review, and edit components Create, review and edit properties Review and edit MAT1.
Miscellaneous RSSCON Create RSPLINE Create TABLE Create
Create a transition element between solids and shells. Create RSPLINE elements as bulk unsupported cards. Create a tabular function card.
517

Altair Engineering
BCTABLE Manager
The BCTABLE Manager enables you to create, edit, and delete BCTABLEs from a convenient tabbed interface. The three tabs, BCTABLE, Contact Elems, and Parameters, each contain tools related to BCTABLEs.
BCTABLE tab
The BCTABLE tab lists existing BCTABLEs in the database. For each item in the list, you can choose whether to display it with the Display check box. To view the content of a particular BCTABLE, select the Status check box and click the Contact Elems tab. The following buttons are also available on this tab: Sync Delete Create Close Synchronize the settings in the BCTABLE tool and the database. Delete the selected BCTABLE. Create a new BCTABLE. Exit the BCTABLE Manager.
Contact Elems tab
Altair Engineering

518
The Contact Elems tab lists existing contact elements for the selected BCTABLE. The BCTABLE is selected on the BCTABLE tab, as described above. The following buttons are also available on this tab: Add Delete Close Add a row/contact element. Delete the selected contact element. Exit the BCTABLE Manager.
Parameters tab
519

Altair Engineering
The Parameters tab lists existing parameter values for each pair of contact elements. The following buttons are also available on this tab: Reset Update Close Set to default values. Update the values. Close the tool.
Click the Slave and Master buttons to see all the BCBODYs.
See also Nastran Utility Menu
Altair Engineering

520
Nastran Part Replacement

The Part Replacement dialog enables you to replace elements in an existing component/part (PSHELL) with new elements. It also restores the referenced items in the original model to the new part, e.g. 1-D connections, masses, equations, boundary conditions, and loads. A message log is provided, which lists the entities being replaced and reconnected as well as cases that require or will require user interaction. The Part Replacement dialog generates a log file that contains a list of the entities being replaced and reconnected in addition to cases that require user interaction.
To replace elements in parts using the Part Replacement macro:

1. From the Tools menu, click Part Replacement. The Nast Part Replacement dialog appears:
1.
In the Old part field, select a component by clicking the button, which opens a comps selector in panel area. Choose a component and click proceed. The new part is created in the database. (If you already created a new part, delete it before performing this step.) In the New part field, select a part (sub-model) to import. Click Import.... (optional) Clear the Delete old part check box to save the old part at the end of the replacement procedure. (optional) Click View log at any time to open the Part Replacement macros log file. Click Next. The following dialog appears:
2. 3. 4. 5.
521

Altair Engineering
6. 7.
In the New part field, select a component by clicking the comps button, which opens a comps selector in the panel area. Choose a component, click select and click proceed. Click Next. The following dialog appears:
8.
Select a material for the new part from the radio button list of available materials that appears in the dialog. Click Apply.
Altair Engineering

522
9.
Specify a tolerance value for the Fix 1-D connections/meshless welds option. This option provides an automatic and an interactive reconnection to the new part for 1-D elements (beams, rigids, springs, etc.) and meshless welds (beam type 9 and hexa). The tolerance value determines the range of 1-D connections and meshless welds that will be replaced. Elements that cannot be replaced will be displayed in red.
12. Click Apply. The results of the replacement are displayed in tabs on the dialog.
523

Altair Engineering
13. Click the EID field on the 1-D tab to select the remaining elements, increase the tolerance, and preview the effect of the increased value on the 1-D elements. 14. Click Apply to use the defined tolerance to fix the elements displayed in green. A message appears that reports the tolerance used to fix the selected elements. If some elements still report as failed, repeat step 11 using a higher tolerance value. 15. Repeat steps 12 and 13 for the Meshless welds tab. Masses attached to the old part can be connected to a new part using the basic steps outlined above. In addition, HyperMesh can detect and fix the following individual loads: forces, moments, temperatures, equations, and constraints. Pressure must be corrected manually.
Altair Engineering

524
Rigid Spider
The RigidSpider macro is used to create a spider (RBE2 elements) around holes. You can create a spider with or without a washer and with one or multiple RBE2 elements.
To create a spider:
1. From the Nastran Utility Menu, click RigidSpider.
2. 3. 4.
Select the component where the spider is needed. Click the button to access a list of all available components. Select the Spider type: Normal or Washer. If you select Washer, an additional field appears on the dialog. In the Washer Type field select Every node or Every other node. Every node indicates that an RBE2 for a washer will be created for each node. Every other node indicates that an RBE2 for a washer will be created between the dependent node and every other independent node. In the Rigid Type field, select Single or Multiple. Single indicates that a single RBE2 element will be created between the independent node and all dependent nodes. Multiple indicates that multiple RBE2 elements will be created between the independent node and each dependent node. Click Generate. The tool redraws the component chosen in step 2 using plotel elements around the holes and component perimeter. Pick a plotel element around the hole where the spider is needed. Click proceed.
5.
6. 7. 8.
525

Altair Engineering
PartInfo
The PartInfo macro summarizes a parts statistics in a dialog. 1. 2. 3. To start the macro, click PartInfo on the Utility Menu. Click component in the main menu area to select a component or click a component in the graphics area to select it. Click proceed. The Part Information dialog appears, which lists the part ID, name, thickness, and material type.
4. 5. Tip
To view additional statistics about the part, click the More Details tab. To display statistics for a different part, select the part in the graphics area or the components selector and click proceed again. Click the middle mouse button instead of the proceed button to quickly select components.
Altair Engineering

526
Component Table
This macro opens the Nastran Component Table, which displays components and their associated attributes in an interactive table. You can also configure the table; only configured items are displayed in the table. With this macro, you can also create components, select components, assign materials to components, change component colors, and change component visualization modes. Most actions are available from shortcut (right-click) menus. You can also find options in the drop-down menus. Before performing actions such as changing the values of component data, you must select Editable from the Table menu. Once the components are writable, you can modify the values of existing components. The following sections describe how to use the Component Table in both read-only mode and editable mode. Using the Component Table in Read-Only Mode When you open the Component Table, existing components are listed in a table using a default configuration. This configuration displays the component name, component ID number, properties on component, component color, thickness, property on element, material name, material ID, material type, and the visualization status of each component. The Nodes and Elems display is turned off by default. When activated, the total numbers of elements and nodes are shown at the bottom of the table. The display of the data in the Component Table can be customized according to your preferences. You can: Change which columns are displayed Change the order of the columns Sort the components by column data, ascending or descending Filter which components are displayed based on column data values (see below) You can save your settings by creating a configuration file. From the Table menu, open the Configure submenu and select the Save CFG-File option. This configuration file saves the set of table configuration options so you can use them again. By default, a configuration file (comptable.cfg) is saved in the working directory for each component table session and settings from this file are applied each time the table is built. Using the Component Table in Editable Mode When you switch the Component Table from the default read-only mode to editable mode (by selecting Editable from the Table menu), you can perform all the actions described in the section above, plus edit the attributes of the components listed in the table. To change the value of an attribute, select the attribute in the Assign Values drop-down, type the new value in the adjacent field, and click Set.
527

Altair Engineering
To Create a New Component

1. 2. 3. 4. 5. 6. From the Table menu of the Component Table, select New. The Component Create dialog opens. Type a name in the Component Name = field. Select a material type for the component from the Mat Name: drop-down field. (Or click the adjacent New button to define a new material and select it.) Click the Properties button to assign a property, or click the adjacent New button to define a new property and select it. Click Create. A panel opens, on which you must confirm the component creation. Click return. The new component appears in the Component Table.
Altair Engineering

528
To Create a New Material or Edit an Existing Material

1. From the Assign Values drop-down field, select Mat Name.
2.
Click New to create a new material or select a material from the HM-Mats drop-down field and click Edit to edit that material.
529

Altair Engineering
To Assign a Value to Multiple Components

1. 2. 3. 4. Select the components that you want to change. You can use ctrl+click and shift+click to select nonadjacent and adjacent rows in the table, respectively. Other options are available in the Selection menu. Select the column type you want to change from the Assign Values drop-down field. Type the new value in the adjacent field. Click Assign. The selected column types are updated to the new value you specified.
Altair Engineering

530
To Filter the List of Components in the Table

The Component Table includes advanced filtering features based on the available columns of data. If your model contains a large number of components, you can filter the components to quickly see components that are of interest to you. 1. 2. From the Table pull-down menu, select Filter. The Filter dialog opens. Type a search string, with optional wildcard characters (*), in the fields for the columns you want to search. (Search strings are case-sensitive.) For example, to search for all components that begin with the letter c and have steel as the material type, you would complete the dialog as shown below:
3.
Click Apply in the Filter dialog. The filter is applied to the Component Table and only those components that match the search criteria are shown.
To remove filtering and display all the components, click the Show All button on the Filter dialog. You can also keep the Filter dialog open after applying filter changes by selecting the Table menu and selecting Configure and Filter on top.
531

Altair Engineering
To Customize the Contents of the Table

To customize what appears in the table, you can specify which columns of data appear in the table. 1. 2. 3. From the Table menu, select Configure and Columns The Configure dialog opens. The Configure dialog contains a list of column types that are available. Select the check boxes for the data you want to view. Click OK.
Altair Engineering

532
To Export Data in CSV or HTML Format

1. 2. 3. From the Table menu, click Save and then either CSV or HTML, depending on which type of data file you prefer. If you chose CSV, you must select delimiter Comma (,) or delimiter Semi-colon (;), depending on which character you want to be the data delimiter in the output file. The Select Output File dialog opens, on which you can select an existing file to overwrite or type the name of the file you are creating. Click Save. The data file is saved in the location you specified.
533

Altair Engineering
Property Table
This macro opens the Nastran Property Table, which is an interactive table of Nastran one-dimensional properties and their associated materials. Note This table contains 1D properties only. Use the Component Table to create 2D and 3D properties.
With this macro, you can also create properties, select properties, assign materials to properties, and export the data in CSV or HTML format. Most actions are available from shortcut (right-click) menus. You can also find options in the drop-down menus. Before performing actions such as changing the values of property data, you must select Editable from the Table menu. Once the properties are writable, you can modify the values of existing properties. The following sections describe how to use the property table in both read-only mode and editable mode. Using the Property Table in Read-Only Mode When you open the Property Table, existing properties are listed in a table using a default configuration. This configuration displays the name, ID, type, material description, material ID, material type, number of elements, and visualization status for each property. The total numbers of elements is shown at the bottom of the table. The display of the data in the property table can be customized according to your preferences. You can: Change which columns are displayed Change the order of the columns Sort the components by column data, ascending or descending Filter which components are displayed based on column data values (see below) You can save your settings by creating a configuration file. From the Table menu, open the Configure submenu and select the Save CFG-File option. This configuration file saves the set of table configuration options so you can use them again. By default, a configuration file is saved in the working directory for each Property Table session and settings from this file are applied each time the table is built. Using the Property Table in Editable Mode When you switch the Property Table from the default read-only mode to editable mode (by selecting Editable from the Table menu), you can perform all the actions described in the section above, plus edit the attributes of the components listed in the table. To change the value of an attribute, select the attribute in the Assign Values drop-down, type the new value in the adjacent field, and click Set.
Altair Engineering

534
To Filter the List of Properties in the Table

The Property Table includes advanced filtering features based on the available columns of data. If your model contains a large number of properties, you can filter the list to quickly see properties that are of interest to you. 1. 2. From the Table pull-down menu, select Filter. The Filter dialog opens. Type a search string, with optional wildcard characters (*), in the fields for the columns you want to search. (Search strings are case-sensitive.) For example, to search for all properties that begin with the letter P and have steel as the material type, you would complete the dialog as shown below:
3.
Click Apply in the Filter dialog. The filter is applied to the Property Table and only those properties that match the search criteria are shown.
To remove filtering and display all the properties, click the Show All button on the Filter dialog. You can also keep the Filter dialog open after applying filter changes by selecting the Table menu and selecting Configure and Filter on top.
535

Altair Engineering
To Create a New Property

1. 2. 3. 4. 5. 6. From the Table menu of the Property Table, select New. The Property Create dialog opens. Type a name in the Property Name = field. Select a property type for the property from the Prop Name drop-down field. (Or click the adjacent New button to define a new property and select it.) Select the type of property (PBAR, PBEAM, etc.) Click Create. A panel opens, on which you must confirm the property creation. Click return.
The new property appears in the Property Table.
Altair Engineering

536
To Assign a Value to Multiple Properties

1. 2. 3. 4. Select the properties that you want to change. You can use ctrl+click and shift+click to select nonadjacent and adjacent rows in the table, respectively. Other options are available in the Selection menu. Select the column type you want to change from the Assign Values drop-down field. Type the new value in the adjacent field. Click Set. The selected column types are updated to the new value you specified.
537

Altair Engineering
Materials Table
The Materials Table is used to review and edit MAT1.
To review MAT1: 1. From the Nastran Utility Menu, click Material Table. All MAT1 in the model are displayed.
To create MAT1: 1. 2. 3. From the Nastran Utility Menu, click Material Table. Click Create Mat1.... The following dialog is displayed.
4. 5.
Fill in the necessary fields. Click Create. The material is created and added to the Material Table.
To delete MAT1: 1. 2. From the Nastran Utility Menu, click Material Table. Use the check boxes to select the material to be deleted. Check Select all to select all materials. Check the small X box next to the check box to delete the material.
3. Click Close.
Altair Engineering

538
RSSCON Create
The RSSCON Create macro creates an RSSCON element that connects the shell and solid. Because RSSCON elements are not directly supported, these elements are stored in unsupported bulk data cards.
To create an RSSCON element:

1. 2. 3. Click the RSSCON Create macro. Pick the elements to be connected in the model. Click proceed.
Note:
When you renumber element or node IDs, RSSCON elements are not also updated because they are supported only as text.
539

Altair Engineering
RSPLINE Create
The RSPLINE Create macro creates RSPLINE elements as bulk unsupported cards.
To create an RSPLINE element:

1. 2. 3. Click the RSPLINE create macro. Select nodes on the model. Click proceed.
The default value for the third field of this card is 0.1.
Altair Engineering

540
TABLE Create
Use the TABLE Create macro to create a tabular function card or add data to an existing card. You can use the macro to import XY data or enter the data manually.
To create a new table card manually: 1. Click TABLE Create on the Utility Menu. Select Create/Edit Table, select the table type (for example, TABLED1), and click Next. The Create/ Edit Table dialog appears.
2. 3.
Type values in the XY table for the XY pairs you want to include in the table. Select either Create New Table or Edit Existing Table. If you selected Create New Table, type a name for the new load collector in the Name field and select a color for the load collector with the color selector button. A new load collector will be created with the table card image including the data from the XY table on the dialog. If you selected Edit Existing Table, choose a load collector from the Select drop-down menu. The data in the XY table will be added to the existing table card that you specified.
4. 5.
Click Apply. Click Exit.
To create or add data to a table card from a data file: 1. Click TABLE Create on the Utility Menu. Select Import Table, select the table type (for example, TABLED1), and click Next. The Import Table dialog appears.
541

Altair Engineering
2. 3.
In the File field, specify an XY data file. This file must be either .csv or .txt format. Select either Create New Table or Replace Existing Table. If you selected Create New Table, type a name for the new load collector in the Name field and select a color for the load collector with the color selector button. A new load collector will be created with the table card image including the data from the XY data file. If you selected Replace Existing Table, choose a load collector from the Select drop-down menu. The data in the XY data file replace the data in the existing table card that you specified.
4. 5.
Click Apply. Click Exit.
Altair Engineering

542
Nastran2 Page
The following macros are available on the Nastran2 macro menu: Miscellaneous Convert Shells Convert degenerate second order shells into first order shells. Review and expand (before renumber) SETs. Create a tag on every node that has a comment in its 10th field. Create SPOINT.
Display Sets Tag on Nodes
SPOINT
543

Altair Engineering
Convert Shells
The Convert Shells macro is used to convert degenerate second order shells into first order shells.
To convert degenerate second order shells: 1. 2. Select the file for which the second order shell elements are to be converted. Click Convert. Messages are displayed in the message box, which state the name and location of the new file as well as the file where all the unconverted second order shells will be placed. Note : You can import the Nastran file directly, and all the degenerate second order shells will be written into the hmx file. In doing this, you will miss all the degenerate second order shells in the imported Nastran file.
Altair Engineering

544
Display SETs
The Display SETs macro is used to review and expand (before renumber) SETs.
To display and expand the SET: 1. 2. Choose the SETs from the Selection column. Click Display.
Notes: "HM SET" means the ID in the SET can be renumbered. "TEXT SET" means the ID in the SET cannot be renumbered. Empty SET cannot be viewed or renumbered.
545

Altair Engineering
Tag on Nodes
The Tag on Nodes macro is used to create a tag on every node that has a comment in its 10th field.
To create tags on nodes: 1. 2. Choose the color of the tags. Click create.
Altair Engineering

546
SPOINT
The SPOINT macro is used to create SPOINTs.
To create SPOINTs: 1. Input nodes in the Node ID(s) window using any the following formats: 2 100 THRU 200 13,24,25 13 14 15 13 THRU 25,30 50 Click Add. The new SPOINTs are created and added to the SPOINTS window. Note: SPOINTs are treated as NODEs. Delete them as you would NODEs.
2.
547

Altair Engineering
PAM-CRASH 2G Utility Menu

The PAM-CRASH 2G Utility Menu (pamcrash2G.mac) contains shortcuts and tools that help simplify PAM-CRASH 2G tasks. The PAM-CRASH 2G Utility Menu contains the following submenus: Conn Card Find M1 M2 Sum Tool
Altair Engineering

548
Tool Menu
The Tool menu options allow you to simplify safety tasks. The following macros are included: View Manager Dummy Positioning Tool Start Starts process manager and loads the Pamcrash2G_DummyPos template in preparation for dummy positioning. Opens the dummy positioning panel in HyperMesh and sets the radio button to incremental positioning. The initial rotation angles of JOINTs, needed for the dummy positioning, are updated with the relative rotation between the parent and the child system. This must be done before the dummy is exported. General tools Substructure Tool RBODY Manager Part Replacement Part Info Organize Xlinks MASS Manager Apply Initial Metric Prepare Model By ID Auto-colors the components. It reorders the components by ID, and displays only the components of the model. This macro is normally used after the FE input of a model. Auto-colors the components. It reorders the components by name, and displays only the components of the model. This macro is normally used after the FE input of a model. Creates and modifies substructures. Displays information about rigid bodies in the model. Replaces an existing part with a new part. Displays statistics of a selected part. Organize LINK-type elements among components. Displays information about masses in the model. Apply an initial metric to the model. Allows you to save and restore different view of the model.
DummyPosPanel
Update Jt Angles
By Name
Resolve include
549

Altair Engineering
Resolve
Resolves the include files with the INCLU / card recursively. You must give the original file name and the target file name. Allows you to edit the target file from the Resolve macro.
Edit Show ID ranges Select Ent
Displays various options. Make your selections and press OK. The editor displays the output file that contains the desired information in the format specified in the user interface. Displays the result file containing information related to all the entities of the model. Displays information related to the entities currently displayed on the screen. Only the result file is displayed. Input Fields in the User Interface
All
Dis
Protocol file Show Clear Hmx file Show Delete Help file Define Define macro lets you define a help file and the required application to open it. This configuration is saved and used by the Show macro to display the help file. Displays the help file using the configuration created with the Define macro, described above. Displays the recent .hmx file for the imported FE input model. Deletes the recent .hmx file for the imported FE input model. Displays the user message box. Clears the user message box.
Show
Model document Edit Opens the Model Documentation card in an editor. You can edit the information and this will be exported while outputting the model. Overwrites the Model Documentation card from the Imported Documentation card.
Overwrite
Altair Engineering

550
Append
Appends the information from Imported Documentation card to the Model Documentation card.
GES
Helps you manage sets in the model. This macro appears on all Utility sub-menus. Displays components and their associated attributes in an interactive table. This macro appears on all Utility sub-menus.
Component Table
See also Conn Card Find M1 M2 Sum Tool
551

Altair Engineering
Dummy Positioning Tool Start Macro

Once the template is loaded, you will be asked to create a process instance or open an existing process instance. After this step, you could see a task tree defining the process of dummy positioning in HyperMesh. You can then traverse through these tasks and position the dummy. Once the dummy is positioned, this position can be saved as a transformation file and can be later applied to the dummy to bring it into this final position without user interaction. The following tasks are listed in the process tree for dummy positioning.
Task Name Configure Process:
Action Select either Interactive positioning or Automatic positioning. Depending on the selection, the process tree will change. LoadDummy You are asked for the PAM-CRASH 2G dummy and the positioner file. When the PAM-CRASH 2G dummy is loaded in HyperMesh, the pampostohm tool is automatically started and the dummy is prepared for positioning, as described in Dummy Positioning. System collectors, systems, and assemblies are created and nodes are associated with the systems. Allows you to import other parts of the model, which may be required in order to position the dummy correctly. Moves to the dummy panel in HyperMesh. Shows the list of joints in the model and allows you to select a joint for viewing the load curves associated with that joint. You can select which curves (x,y,z) should be shown, the updatePlot utility shows the current position of the joint on the load curve by drawing a vertical line. The deletePlot utility deletes the plots created by this tool. If you exit this task without deleting plots, you would need to do that in the delete panel afterwards. Note that only plots will be deleted, none of the load curves will be deleted from the database. Once finished with the positioning of the dummy, you can save this information into a transformation file. This enables you to update the model documentation as well as create HTML documentation of the process. You can also
Interactive Positioning:
LoadNoDummyFiles
SelectJoints
CreateTransformation
CreateDocumentation
Altair Engineering

552
select an image to be embedded in the HTML file. A browser can also be selected to display the HTML file. An h3d file is also embedded into the HTML documentation. ExportFiles You can save the model as a HyperMesh database as well as in PAM-CRASH 2G format. While exporting in PAM-CRASH 2G format, you have the choice of specifying whether you want to delete the additional entities created by the dummy positioning tool. Same as LoadDummy .
Automatic Positioning:
LoadOnlyDummy
ExecuteTransformatio You can select a transformation file, which will n be executed automatically to position the dummy. Documentation ExportDummy Same as CreateDocumentation. Same as ExportFiles.
Note:
The same transformation file could be applied to different dummies, provided the tree structure remains same.
See also Tool Macro Menu PAM-CRASH 2G Materials Supported for Dummy Positioning Stop Angle Implementation Update Initial Rotation Angle in the JOINT Card
553

Altair Engineering
Materials Supported for Dummy Positioning in PAM-CRASH 2G

For the computation of the minimum and maximum angle for the rotation in each direction, the PAM-CRASH 2G materials 220 and 221 are implemented.
See also Dummy Positioning Tool Start Macro Stop Angle Implementation Update Initial Rotation Angle in the JOINT Card
Altair Engineering

554
Stop Angle Implementation

Normally, the stop angles are given by load curves. The second and last curve points are used to determine the stop angle. If a load curve has less than four entries, the first and the last entries are used. You can find the implementation of the stop angle in the HM_JOINT_INFO function in the function template of the PAMCRASH 2G Interface. If load curves are not defined for a joint, default values for stop angles ( -270C to +270C ) will be displayed in the Dummy Positioning panel.
See also Dummy PositioningTool Start Macro PAM-CRASH 2G Materials Supported for Dummy Positioning Update Initial Rotation Angle in the JOINT Card
555

Altair Engineering
Update Initial Rotation Angle in the JOINT Card

The initial rotation angles in the JOINT cards are updated automatically. To update them, use the macro Update Jt Angles on the Tool page.
See also Dummy PositioningTool Start Macro PAM-CRASH 2G Materials Supported for Dummy Positioning Stop Angle Implementation
Altair Engineering

556
Part Replacement Macro

The Part Replacement macro allows you to replace the elements in an existing component/part with new elements, typically replacing a part with a similar part that has been re-meshed or slightly re-shaped. This macro not only replaces nodes and elements between parts, it also restores the referenced items in the original model to the new part, e.g. 1-D connections, distributed mass, contacts, loads, and database history. Results are provided that list the entities being replaced and reconnected as well as cases that required, or will require, user interaction.
To replace parts with the Part Replacement macro:

1. Select the old and new parts. The old part must be in the HyperMesh database. You can use the Select From File button to select a new part from an external PAM-CRASH file or select a part from the HyperMesh database for the new part. Identify the Old Part and New Part components. The name and color of the components are reported once the parts are selected. Click the eye icon to enable/disable the visibility of the part in the graphics area.
2.
Click the Material button to set the material options. Select whether the new part should retain its thickness and material properties or inherit those properties from the old part. Alternatively, you can specify a new thickness value by selecting the UsrThk option and typing a value in the adjacent text box.
3.
Click the Tolerance button to set the tolerance options. The default HyperMesh value for tolerance is 10.0. You can type a different tolerance value in the adjacent text box. Select the No global tolerance check box to suppress tolerance comparisons during the
557

Altair Engineering
replacement operations.
4.
Click Start to activate the replacement operation. The status for each check appears in the Process Manager tab.
The results appear in the main menu area. The entities are sorted on separate tabs; on each tab, the status of the replacement is listed by ID. Successful replacements are marked as fixed, while suggested tolerance values are provided for those that failed.
See also Tool Macro Menu
Altair Engineering

558
Part Info Macro

The Part Info macro summarizes a parts statistics in a dialog. 1. 2. 3. 4. 5. Tip To start the macro, click Part Info on the Utility Menu. Click component on the main menu area to select a component or click a component in the graphics area to select it. Click proceed. The Part Information dialog appears, which lists the part ID, name, thickness, and material type. To view additional statistics about the part, click More Detail>> . To display statistics for a different part, select the part in the graphics area or the components selector and click proceed again. Click the middle mouse button instead of the proceed button to quickly select components.
559

Altair Engineering
Substructure Tool Macro

The Substructure Tool macro provides several features for creating and modifying substructures. Substructures are user-defined sets of finite elements, elements and nodes, or nodes from the initial model. Information defining the substructures and their boundary node displacements are saved in a special file during the initial run. In subsequent runs, this saved data is read in and the saved displacement time histories are applied as imposed displacements to the boundary nodes. The input data set for a subrun must contain all the information needed to perform the subrun. Notes: The SUBDF card is supported as a vector collector in HyperMesh. You must have a pre-existing GES created that contains the nodes/elements of the part defining the substructure. When you open the Substructure Tool macro, the existing substructures are listed in a table-based interface, as shown below. The substructures are sorted by order of creation. The following columns appear in the table: Keyword Name IDEF The name of the substructure Indicates the definition type of the substructure: 0: Only via elements 1: Via elements and boundary nodes 2: Only via boundary nodes DTSUB Elements Specifies the time intervals for the boundary node displacement time histories Displays the ID of the element-based entity set. You can click the GES button to use the GES Browser to select an entity set. Displays the ID of the boundary node-based entity set. You can click the GES button to use the GES Browser to select an entity set. Name of the file that contains the definition of the substructure and its boundary node displacements Time unit scaling factor Length unit scaling factor
Boundary Nodes
Filename SUBRUN
Time Factor Length Factor
Altair Engineering

560
RBODY Manager Macro

The RBODY Manager is accessible in the PAM-CRASH 2G Tool menu. The RBODY Manager provides the following features in one convenient tab: Display all rigid bodies in the model Display individual rigid bodies Create new, and edit existing, simple and complex rigid body formulations View and update details of individual rigid bodies, though the card editor and the rigid panel The tool is also available in the RADIOSS user profile and offers similar features.
The RBODY Manager in the Tab Area
561

Altair Engineering
Existing rigid bodies are shown in the table. For each rigid body, the display status, ID number, name, master node ID, and type is shown. Column Disp ID Title Master Node Type Description Indicates whether the rigid body is displayed in the graphics area. The ID number of the rigid body. The descriptive name of the rigid body. The ID of the node that serves as the master node of the rigid body. S or C. S indicates a simple rigid body, which is a typical spider formulation. C indicates a complex formulation, such as an RBODY that points to a part or a set of sets.
Highlight individual entries or groups of entries to perform an action on the rigid body. Actions are available from the context menu (by right-clicking over the table entries) or the tool bar buttons. These actions are described below: Icon Name Review Options Action Customize the way the selected rigid bodies are displayed. Options include transparency and auto-review selections. Highlights the nodes to which the selected RBODY is attached. The master node is shown in blue and the slave nodes are shown in red. Highlights the elements that are attached to the selected rigid body.
Review
Find Attached
Edit
Modify the definition of the rigid body through the rigid panel.
Card Edit
Opens the RBODY card in the card editor.
Delete Refresh
Deletes the selected rigid body. Update the table of rigid bodies.
New rigid bodies can be created with the RBODY Manager. The following fields are available at the bottom of the RBODY Manager tab, which enable you to supply all the basic data needed to create a new RBODY.
Altair Engineering

562
Nodes, parts, materials, properties, and GES can be used to define the slave nodes. Once the RBODY is created, click the refresh button to list it in the table. Then you can select the RBODY to edit the card image, display the RBODY, etc.
Fields to create a new RBODY
Notes: When a large number of slave nodes are attached to a master node, the connecting lines are not displayed in the graphical model. The table of rigid bodies can be sorted by the ID, title, mater node, and type columns. Select Show Details from the context menu to display a summary of details about the rigid body including the ID, name, master node ID, and number of slave nodes. Select Editable from the context menu to make the title column editable. When the Title column is editable you can modify the names of the rigid bodies.
563

Altair Engineering
Apply Initial Metric Macro

The Apply Initial Metric macro applies the initial metric to the current model for simulating the inflation of airbags. Refer to the PAM-CRASH documentation for details about using the initial metric. Before using this macro, you must specify an .im file in the METRIC control card. This file specifies the conditions of the airbag inflation.
When you click the Apply Initial Metric macro button, the macro applies the settings in the .im file to the currently-loaded model and displays the inflation motion in the graphics area. When the execution is complete, the macro creates a log file named initial_metric.nodes that contains the NODAL information.
Altair Engineering

564
Organize Xlinks Macro

The XLINK Organizer macro can be used to move and arrange existing LINK type elements (PLINK, ELINK, LLINK, SLINK) to existing components. The macro contains the following fields and buttons: Select element: Prefix: Select the element type you want to work with. Filter the element results by the text you type in the adjacent text box. Click Set to run the filter. Makes only the selected elements visible in the graphics display.
Select a component/part to which the selected elements will be added.
Import a component from a PAM-CRASH 2G input file.
To move an XLINK element to a component:

1. Select the type of link element from the Select element field. The list of elements of that link type are listed in the table along with the parts with which they are associated. 2. 3. Click the component button to select a component to which you want to add the selected elements. Click Apply. The selected elements are added to the selected component.
565

Altair Engineering
MASS Manager Macro

The MASS Manager is a tool accessible in the PAM-CRASH 2G Tool menu. The MASS Manager provides the following features in one convenient tab: Display all masses in the model Display individual masses Create new, and edit existing simple and advanced mass formulations View, find attached, and update details of individual MASS, though the card editor and the MASS panel.
Altair Engineering

566
Input Fields in the Show ID Ranges User Interface
Input Fields in the User Interface:

Existing Entity Types in the Model Allows you to select the entity type for which you want to have the ID range information. SELECT displays a list of all entity types present in the model. You can select a single entity or multiple entities. all displays information for all the entities present in the model. Nodes and elements are always selected. Allows you to provide the maximum number of ranges (default is 10) to be displayed in the output file. If an entity has a larger number of ranges, it will be truncated. Allows you to choose to view either the used IDs for an entity or the free IDs for an entity. The option to output free IDs is valid only when you choose Detailed for the overview type. Allows you to select the method in which elements are written to the output file. You can select either HM_entitytype or Element_type. Element_type writes out elements according to the solver definition. Allows you to choose the overview type. You can select either Detailed or Condensed. If Condensed is selected, only the overall maximum and minimum IDs and the total number of ranges for each entity are displayed. In this case, free IDs will not be displayed even if it is selected. For Detailed, maximum and minimum IDs for each range number (subject to the maximum number of ranges specified) is displayed along with the corresponding range number. In this case, the overall maximum and minimum IDs and the total number of ranges for that entity will also be displayed at the beginning of the information related to the entity. Allows you to specify whether you want the information for all the entities in the model or only for the entities currently displayed. Allows you to input a string/character that is placed at the beginning of each line in the output file. This enables you to include the information in the solver deck for further use.
Maximum Number of Ranges
Display Ids Type
Display Entity Type
Overview Type
Id Info for Entities
Comment String for Solver
567

Altair Engineering
Find Menu
The Find menu contains options that help you find and visualize data. The following macros are included. Temporary Nodes CNODE Clr/All/Dis Clr: deletes all temp nodes from the model. All/Dis: Finds CNODEs in the complete/displayed model and highlights the nodes as temp nodes. Find Components: By Elems Finds all components which have elements in the current (masked) display.
Rbody visualization: All/Dis/Sel Updates the rigid bodies definition by resolving the references to a GES (set/setofset) by converting them into node lists and displaying the web on the screen. All: Updates all rigid bodies Dis/Sel: Updates displayed or selected rigid bodies, respectively Find/Mask Finds/Masks the respective entities. Review the buttons tool tips to see the full entity name.
See also Conn Card M1 M2 Sum Tool
Altair Engineering

568
Card Menu
The Card menu contains options that help display the PAM-CRASH 2G cards in an editor. The following macros are included. PAM2G cards: PARTS MATER Shows the 1D, 2D, and 3D PART cards of the displayed components in a viewer. Shows the 1D, 2D, and 3D MATER cards of the displayed components in a viewer. Shows the NSM cards of the displayed groups in a viewer. Shows the CNTAC cards of the displayed groups in a viewer. Shows the SECFO cards of the displayed groups in a viewer. Shows the RWALL cards of the displayed groups in a viewer. Shows the GROUP cards of the displayed sets in a viewer.
NSM CNTAC SECFO RWALL GROUP HM entities: Properties Sensors Loads
Shows all properties cards of the displayed properties in a viewer. Shows all SENSOR cards of the displayed sensors in a viewer. Shows all loads and load collectors cards of the displayed loads and load collectors in a viewer. Shows all FUNCT cards of the model in a viewer. Shows all BAGIN and CHAMBER cards of the displayed control volumes in a viewer.
Curves Airbags
See also Conn Find M1 M2 Sum Tool
569

Altair Engineering
Altair Engineering

570
Sum Menu
The Sum menu contains options that execute the PAM-CRASH 2G summary templates and display the resulting text file in a viewer. The following macros are included. Components All/Dis Execute the components_txt summary and show the results for the complete/displayed model in a viewer. Execute the materials_txt summary and show the results for the complete/displayed model in a viewer. Execute the elements_txt summary and show the results for the complete/displayed model in a viewer. Execute the ctr_of_gravity_txt summary and show the results for the complete/displayed model in a viewer. Execute the moment_of_inertia_txt summary and show the results for the complete/displayed model in a viewer. Execute the groups_txt summary and show the results for the complete/displayed model in a viewer. Execute the nsmas_txt summary and show the results for the complete/displayed model in a viewer. Execute the property_txt summary and show the results for the complete/displayed model in a viewer. Execute the sensors_txt summary and show the results for the complete/displayed model in a viewer.
Materials All/Dis
Elements All/Dis
Center Of Gravity All/Dis Moment Of Inertia All/Dis Interfaces All/Dis
Non Struct Masses All/Dis
Property ALL
Sensors ALL
571

Altair Engineering
M1 Menu
The M1 menu contains options that set the correct element or load type and enter the appropriate HyperMesh panel. The following macros are included. PART/: 3D/2D/1D/LINK Enters the components panel, selects the comps collector, and sets the correct card image.
MATER/: 3D/2D/1D/LINK Enters the components panel, selects the mats collector, and sets the correct card image. Enters the components panel, selects the mats collector, and sets the correct dictionary.
PLY_DATA
Mass elements : MASS NSMAS Constraints: RBODY NODCO RWALL CNTAC TIED Elements: BAR BEAM KJOINT JOINT SPRING Sets the element type 1dele = to BAR and enters the 1d elems panel. Sets the element type beam = to BEAM and enters the beams panel. Sets the element type 1dele = to KJOIN and enters the 1d elems panel. Sets the element type 1dele = to JOINT and enters the 1d elems panel. Sets the element type spring = to SPRING and enters the springs panel. Sets the element type rigid = to RBODY and enters the rigids panel. Sets the element type rigid = to NODCO and enters the rigids panel. Enters the rigid walls panel and set the card image = to RWALL. Enters the interfaces panel and sets the card image = to CNTAC. Enters the interfaces panel and sets the card image = to TIED. Sets the element type mass = to MASS and enters the mass panel. Enters the interfaces panel and sets the card image to nsmas.
Altair Engineering

572
SHELL MEMBR TRIA_C SOLID BSHEL Link elements: PLINK ELINK LLINK SLINK
Sets the element type tria3 = and quad4 = to SHELL. Sets the element type tria3 = and quad4 = to SHELL. Sets the element type tria3 = TRIA_C. Sets the element type tetra4, pyramid5, penta6, and hex8 = to SOLID. Sets the element type hex8 = to BSHEL.
Sets the element type mass = to PLINK and enters the mass panel. Sets the element type 1dele = to ELINK and enters the 1d elems panel. Sets the element type 1dele = to LLINK and enters the 1d elems panel. Sets the element type tria3 = and quad4 = to SLINK.
See also Conn Card Find M2 Sum Tool
573

Altair Engineering
M2 Menu
The M2 menu contains options that set the correct element or load type and enter the appropriate HyperMesh panel. The following macros are included. Auxiliaries: FRICT Enters the components panel, selects the props collector, and sets card image = to FRICTION. Enters the components panel, selects the props collector, and sets card image = to RUPTURE_MODEL. Enters the sensors panel. Enters the edit curves panel and set the radio button to modify.
RUPMO
SENSO CURVES Safety : SLIPR RETRA BAGIN CHAMB GASPC
Sets element type mass = to SLIPRING and enters the mass panel. Sets element type mass = to RETRACTR and enters the mass panel. Enters the airbag panel and sets the card image to BAGIN. Enters the airbag panel and sets the card image to CHAMBER. Enters the components panel, selects the props collector, and sets card image = to GASPEC.
Plot output: THNOD THELE SENPT SECFO_SECTION SECFO_SUPPORT SECFO_VOLFRAC Enters the output blocks panel and changes the type to nodes. Enters the output blocks panel and changes the type to elements. Sets element type mass = to SENPT and enters the mass panel. Enters the interfaces panel and sets card image = to SECFO_SECTION. Enters the interfaces panel and sets card image = to SECFO_SUPPORT. Enters the interfaces panel and sets card image = to SECFO_VOLFRAC . Enters the rigid walls panel and sets card image = to SECFO_PLANE.
SECFO_PLANE
Altair Engineering

574
Nodals: FRAME NODE INVEL VEL3D RVE3D ACC3D Enters the systems panel. Enters the nodes panel. Sets load type velocity = to INVEL and enters the velocity panel. Sets load type velocity = to VEL3D and enters the velocity panel. Sets load type velocity = to RVE3D and enters the velocity panel. Sets load type acceleration = to ACC3D and enters the acceleration panel. Sets load type velocity = to RDV3D and enters the velocity panel. Sets load type acceleration = to RDA3D and enters the acceleration panel. Sets load type acceleration = to RAC3D and enters the acceleration panel. Sets load type constraint = to BOUNC and enters the constraints panel. Sets load type constraint = to DIS3D and enters the constraints panel. Sets load type constraint = to DIS3DX and enters the constraints panel. Sets load type constraint= to DIS3DM and enters the constraints panel. Sets load type constraint= to RAN3D and enters the constraints panel. Sets load type constraint= to RDD3D and enters the constraints panel. Sets load type force= to CONLO and enters the forces panel.
RDV3D RDA3D
RAC3D
BOUNC DIS3D DIS3DX DIS3DM RAN3D RDD3D CONLO Analysis by keyword: LOADCOLS
Enters the collector panel, switches the type to loadcols and sets the card image to INVEL.
See also Conn Card
575

Altair Engineering
Find M1 Sum Tool
Altair Engineering

576
Conn Menu
The Conn menu contains options that lets you manage connectors in the model. The following macros are included. Connector organize: ByPinkPart Renumber: NodeID/Plink ID Node ID: Renumber nodes for displayed plinks such that plinkId = plinkNodeId. Plink ID: Renumber displayed plinks such that plinkId = plinkNodeId. Connector panel: Feabsorb/Quality/ Realize Find att to P(X)LINKs Enters the connectors panel, and then fe absorb/quality/fe realize panel, depending on the selected macro. Ces: finds connectors attached to the displayed link entity. Com: finds all components attached to the displayed link entity. Mcom: finds all master components attached to the displayed link entity. Scom: finds all slave components attached to the displayed link entity. Find att to CE PL: finds Plinks attached to the displayed connectors. Com: finds all components attached to the displayed connectors. Find att to Comps Find/Mask Finds entities attached to the displayed components. Finds/Masks the entities depending upon the selected macros. Organizes the connectors by the parts of the associated Plink elements.
See also Card Find M1 M2 Sum Tool
577

Altair Engineering
Altair Engineering

578
GES Macro
The GES macro displays a GES Browser that lets you manage sets in the model. Because general entity selection is mapped as a set of sets in the PAM-CRASH 2G interface, the need to manage the sets becomes more crucial for the effective and efficient handling of the model.
Functionalities included in the GES Browser
Creating a set, group or GES. Renaming sets. Modifying sets (drag and drop facility is available). Reviewing sets Deleting sets Adding/deleting entities to sets Adding/removing keywords to/from GES (set of set) Adding ranges/comments to the sets Resolving ranges Reviewing as PAM-CRASH 2G card Changing the keyword (for example, ELE to DELELE) Filter the entities to be displayed in the browser. For example, you can only select sets of sets or component sets for viewing. Filtering by ID and name is also possible. For example, if you enter 1-100; 200; 300-400 in the Ids field, it will display all GES/Sets (including child items) with IDs 1 to100, 200 and 300 to 400. Similarly in the Name field, you can enter a keyword such as face and the browser displays all items (including child items) whose name contains face . Selecting by name Finding and deleting empty GES Finding unused GES Resolving unresolved groups - This function is useful in case of assembling model from different files. It may happen that the group referenced in first file is defined in second file. In this case when first file is loaded, the group is imported as an unresolved group. When the second file is also loaded, this utility can be used to resolve the unresolved group references. Creating/modifying interfaces Reviewing interfaces as contact surfaces
579

Altair Engineering
Creating/modifying rigid walls Creating/modifying section forces Creating/modifying loadcols Direct access to the card editor for interfaces, loadcols and components DELNOD Card The following parameters are available via the DELNOD card: ELE GRP PART NOD SEG EDG ELE > NOD PART > NOD GRP > NOD DELNOD DELELE DELPART DELGRP DELELE > NOD DELPART > NOD DELGRP > NOD Note: When you add a set to the GES using drag and drop functionality of the browser, a new set is created with the exact copy of the contents of the original set, therefore, the changes made to this new set are local in effect but in case of adding a group to the GES, only a reference is made to the existing GROUP definition. You can modify the GROUP by using the references also but there exist only one copy of the group in the model. Therefore while modifying one of the references, you should always keep in mind that this change will also affect all the other references to this group and the group itself is modified. In case the group does not exist in the model, it is created. If you don't want to create the group, instead use the functionality Unresolved Groups > Edit and add the group there. This will be exported correctly. You can also create a config file, which saves all information about various GES Browser options, such as DisplayComments (Yes/No), DisplayRanges (Yes/No), confirmChanges (Yes/No), etc. Later on, this config file can be used to restore these settings. By default, a config file ( gesbrowser.cfg) is saved in the working directory for each session of the GES Browser and
Altair Engineering

580
settings from this file are applied every time the browser is built. These functionalities can be invoked from the buttons LoadCFG/SaveCFG.
581

Altair Engineering
Component Table Macro

This macro displays the components and their associated attributes in an interactive, customizable table. Only the configured items will be displayed in the table. You can create a component, select components, assign materials to components, change component colors and visualization mode, etc. The mass, nsmass, and center of gravity of the components can be viewed in the table. The sum of selected attributes, such as mass and nsmass, are also displayed at the bottom of the Component Table. This tool can also be used to assign database materials to the components. Under the menu item user, there is an option to set the path for material database. Once this path is set you can reload the table in edit mode. At the top menu bar, separate lists for materials in the model and database materials appear. You can then select the component(s) and assign the material from any of the lists. Database materials are shown in green color while the normal materials are shown in grey. Unresolved materials are shown in red color. Columns can be moved interactively to arrange them in a desired order. This can be done by pressing the left mouse button and dragging the column to the desired location (left mouse button must be kept pressed while dragging). This information is saved and on reloading the Component Table, columns will be arranged accordingly. Most of the functions in the Component Table can also be accessed by a mouse-click. You can also create a config file, which saves all information about various Component Table options, such as which columns to show, displayed or all, confirmChanges (Yes/No), etc. Later on, this config file can be used to restore these settings. By default, a config file (comptable.cfg) is saved in the working directory for each Component Table session and settings from this file are applied every time the table is built. This functionality can be found in the Table > Configure submenu.
Altair Engineering

582
PERMAS Utility Menu

The PERMAS Utility Menu is loaded when you open the PERMAS user profile. The macros on the PERMAS Utility Menu simplifies some common tasks for the PERMAS user profile. The following PERMAS macros are available:
Convert Groups
Convert element-based surfaces that were created in Abaqus to PERMAS surfaces Macro plotting NLLOAD cards
PLOT NLLOAD
583

Altair Engineering
Convert Groups
The Convert Groups macro allows you to convert element-based surfaces that were created in Abaqus to PERMAS surfaces. While in the Abaqus user profile, use the Contact Manager to create as many element-based surfaces (*SURFACE, TYPE=ELEMENT) as needed. When finished, switch to the PERMAS user profile (by clicking Preferences > User Profile ) and click the Convert Groups macro. $SURFACE ELEMENTS are created based on the contact surfaces identified in the model. Currently, only *SURFACE cards defined on individual element IDs of shells or solids are translated. If a surface is defined on sets, it will not be translated. Also, it is necessary to have face identifiers defined.
Examples of entities converted:

*SURFACE, NAME = surf_1, TYPE = ELEMENT 1, SPOS *SURFACE, NAME = surf_2, TYPE = ELEMENT 2, S1
Examples of entities that will not convert:

**Element ID, but no face identifier given *SURFACE, NAME = surf_3, TYPE = ELEMENT 2, **Surface definition based on element set *SURFACE, NAME = surf_4, TYPE = ELEMENT Element_set1, SPOS
Altair Engineering

584
Creating an NLLOAD Card

To create an NLLOAD card, you must first create and edit a loadstep card. When a loadstep is created, an NLLOAD card can be created by checking the NLLOAD checkbox in the card image of the loadstep. The NLLOAD card defines the tabular load history for static or transient analysis. To utilize the NLLOAD card, the LOADING option must be selected. LOADING is set as the default. The card image lists all the load collectors currently assigned to the load step. Continue following the steps to set the NLLOAD card time load history: 1. In the Card Editor, ensure that the AnalysisProcedure toggle is set to LOADING.
2. 3.
Place a check next to NLLOAD. Under TIME Selection, choose either TIME/LIST or TIME/dt. If you select TIME/LIST, the load pattern is determined by individual values entered in the TIME fields. It will set the iterations to a series of steps at specific points. If you select TIME/dt, you can specify the time steps in the first dataline with the start value and increment value. All subsequent datalines are automatically populated based on this information. The load history is now set to a series of regular intervals.
4. 5.
Enter a value in the NoOfLPATS field. This determines the number of load patterns (load collectors) you want to add to the NLLOAD card. Enter the value in the TimeSteps field in the upper part of the card image.
6. 7.
For each TIME/STEP pattern created, enter values in the TIME fields to set the starting value and the increment values. For each TIME/dt pattern created, enter the starting value in the t field and the increment value in the dt field. The TIME fields are automatically populated.
585

Altair Engineering
Note:
For a better readablility on export, if the columns exceed the line length (currently set to 80 characters), a new NLLOAD keyword is written. On import NLLOAD will be written in this format but also if lines of each load pattern is continued with ampersands.
. 8. 9. Click return to close the Card Editor. Click return to close the Load Steps panel. On export, if the columns exceed the line length (currently set to 80 characters), the lines will be continued by an ampersand (&). This is also the format the reader can understand from the .dat file only.
Note:
Using the PLOT NLLOAD Macro

You can use the PLOT NLLOAD macro on the Utility Menu to draw the load history plots. 1. On the Utility Menu, click the Plot NLLOAD button. The load step just created is displayed and the values entered in the NLLOAD card are shown. 2. 3. You can edit these values in the $NLLOAD table on the right side of the window, although you cannot add new columns or new load collectors at this point. Use the Display checkbox to turn the display of particular load steps on and off.
Altair Engineering

586
587

Altair Engineering
RADIOSS (Block Format) Utility Menu

The RADIOSS (Block Format) Utility Menu is accessible when the RADIOSS (Block Format) user profile is loaded. It contains shortcuts and tools that help simplify RADIOSS tasks.
To load the RADIOSS (Block Format) user profile:

1. 2. 3. From the Preferences menu, select the User Profile option. Select the RADIOSS Block profile. Select the Block110, Block100, Block91, Block51, Block44 or Block42 template.
The RADIOSS user profile activates the RADIOSS macro, sets the FE input reader to RadiossBlk, and loads the corresponding RADIOSS FE output template. Also, the graphical user interface becomes RADIOSS specific, renaming and/or removing some panels and options. The RADIOSS (Block Format) Utility Menu contains the Tools sub-menu in addition to the standard Utility Menu functions.
See also Tools Menu Other Tools
Altair Engineering

588
Tools Menu
The Tools menu contains utilities that simplify many common tasks in RADIOSS (Block Format). The following macros are included:
Create Part Clone Part Part Info Material Table... Component Table
Creates a new component quickly. Creates a new part from the properties of an existing part. Displays statistics of a selected part. Allows you to easily create materials for RADIOSS (Block Format). Opens the Components and Properties table, displaying a tabular list of the \PARTs (components) in the model. Helps create the TH/SPRING card, which supports time histories with spring output. Displays information about rigid bodies in the model. Creates boundary conditions of any load collector type other than ACTIV. Displays information about masses in the model. Creates and edits time history ACCEL cards to track accelerometer output requests. Creates meshless welding using the RADIOSS (Block Format) interface type 2 and springs. Identifies and removes duplicate master and slave elements from Interface and Rigidwall. Exports cards with runtime options in D01 format. Checks your model for potential problems with properties, materials, element quality, etc. and reports them on-screen. The report identifies the problem entity by ID, and describes the error.
Relative Displacement RBODY Manager BCs Manager ADMAS Manager Accelerometer
Welds
Delete Dup Elems
Engine File Tool Model Check
See also RADIOSS (Block Format) Utility Menu
589

Altair Engineering
Altair Engineering

590
RBODY Manager
The RBODY Manager is accessible in the RADIOSS (Block Format) Utility Menu. The RBODY Manager provides the following features in one convenient tab: Display all rigid bodies in the model Display individual rigid bodies Create new, and edit existing, simple and complex rigid body formulations View and update details of individual rigid bodies, though the card editor and the Rigid panel
The RBODY Manager in the tab area
Existing rigid bodies are shown in the table. For each rigid body, the display status, ID number, name,
591

Altair Engineering
master node ID, and type is shown. Column Disp ID Title Master Node Type Description Indicates whether the rigid body is displayed in the graphics area. The ID number of the rigid body. The descriptive name of the rigid body. The ID of the node that serves as the master node of the rigid body. S or C. S indicates a simple rigid body, which is a typical spider formulation. C indicates a complex formulation, such as an RBODY that points to a part or a set of sets.
Highlight individual entries or groups of entries to perform an action on the rigid body. Actions are available from the context menu (by right-clicking over the table entries) or the tool bar buttons. These actions are described below: Icon Name Review Options Action Customize the way the selected rigid bodies are displayed. Options include transparency and auto-review selections. Highlights the nodes to which the selected RBODY is attached. The master node is shown in blue and the slave nodes are shown in red. Highlights the elements that are attached to the selected rigid body. Modify the definition of the rigid body through the Rigid panel.
Review
Find Attached
Edit
Card Edit
Opens the RBODY card in the Card Editor.
Delete Refresh
Deletes the selected rigid body. Update the table of rigid bodies.
New rigid bodies can be created with the RBODY Manager. The following fields are available at the bottom of the RBODY Manager tab, which enable you to supply all the basic data needed to create a new RBODY.
Altair Engineering

592
Nodes, parts, materials, properties, and GRNODs can be used to define the slave nodes. Once the RBODY is created, click the refresh button to list it in the table. Then you can select the RBODY to edit the card image, display the RBODY, etc.
Fields to create a new RBODY
Notes: When a large number of slave nodes are attached to a master node, the connecting lines are not displayed in the graphical model. The table of rigid bodies can be sorted by the ID, title, mater node, and type columns. Select Show Details from the context menu to display a summary of details about the rigid body including the ID, name, master node ID, and number of slave nodes. Select Editable from the context menu to make the title column editable. When the Title column is editable you can modify the names of the rigid bodies.
The tool is also available in the PAM-CRASH 2G user profile and offers similar features.
See also Tools Menu RADIOSS (Block Format) Utility Menu
593

Altair Engineering
Part Info
The Part Info macro summarizes a parts statistics in a dialog. 1. 2. 3. 4. 5. Tip To start the macro, click Part Info on the Utility Menu. Click component on the main menu area to select a component or click a component in the graphics area to select it. Click proceed. The Part Information dialog appears, which lists the part ID, name, thickness, and material type. To view additional statistics about the part, click More Detail>> . To display statistics for a different part, select the part in the graphics area or the components selector and click proceed again. Click the middle mouse button instead of the proceed button to quickly select components.
Altair Engineering

594
Clone Part
The Clone Part macro enables you to quickly create a new part from the properties of an existing part. Select the existing part on which to model the new part by clicking the button, which opens a dialog listing all the existing components. Select a component from the list and click OK. Type a name for the new part in the New Part field and click the color icon to select a color for the component. Select whether to duplicate the material and section properties or to re-use the original material and section properties. Duplicate means that a new material and section is created (the name is suffixed with .n version numbers and new IDs are used) with the same properties, while Reuse refers to the same material and section as the original. Select whether to duplicate the elements. Duplicate elements will make a copy of the elements from the selected part to new part in the same location. Click Create>> to either create or create and edit the card.
595

Altair Engineering
Create Part
The Create Part macro enables you to create components on-the-fly. It can be accessed by clicking Create Part on the Utility Menu. Type a name for the new component in the Part name field and select a color by clicking the adjacent color icon. Select a section in the Section field by choosing Create New (create a new section), Same As (create a new section based on an existing section), or Model (select an existing section) from the selection menu. Select a material for the component in the Material field by the same method as described above for the Section field. Click Create>> to either create or create and edit the card.
Altair Engineering

596
ADMAS Manager
The ADMAS Manager is a tool accessible in the RADIOSS (Block Format) Utility Menu. The ADMAS Manager provides the following features in one convenient tab: Display all masses in the model Display individual masses Create new, and edit existing, simple and advanced mass formulations View, find attached, and update details of individual ADMAS, though the card editor and the admas panel.
Create ADMAS
To create a new mass, make a selection in the Type : field. M option - nodal mass defined separately on each selected node. MADV0 option - nodal mass defined on the selected nodes as a set. Defined mass is the mass added to each node in the set. MADV1 option - nodal mass defined on the selected nodes as a set. Defined mass is the total mass added to nodes in the set.
597

Altair Engineering
Note: The tool is also available in the PAM-CRASH 2G user profile and offers similar features.
How do I... Create a standard M mass Create an advanced mass Update the mass element
See also admas panel Tools Menu RADIOSS (Block Format) Utility Menu
Altair Engineering

598
Engine File Tool

The RADIOSS Engine File Tool is accessible through the Tools page on the RADIOSS (Block Format) Utility Menu. When you click the Engine File button, the following dialog is displayed:
Engine files are used to set up the model, including termination times, output requests, and other checks that control the execution of the job. This tool helps you export Engine files cards with runtime options in the RADIOSS (Block Format) Engine File Tool. You can begin by loading a 0000.rad file and/or an existing 0001.rad file. Then use the tabs on the tools dialog to prepare keywords. Each tab corresponds to a supported keyword or group of keywords in the input deck. An additional tab (UNSUP) exists for manual entry of unsupported keywords. When you have finished setting up keywords in the Engine File Tool, click the Export button to create the engine file. The following list describes the tabs that are available on the Engine File Tool dialog. For detailed descriptions of the keywords and options refer to the RADIOSS ENGINE documentation.
GENERAL
Contains fields for several basic keywords. The /RUN and /VERS fields are required. Contains animation-related options. Contains boundary condition-related options.
ANIM BC
599

Altair Engineering
DEL DT FUNCT INTER RBODY MISC
Contains deletion-related options including interfaces and elements. Contains options related to time step defaults. Contains the keyword for redefining the function number Ifunc. Contains the keyword for activation and deactivation of interfaces. Contains options for rigid body activation and deactivation. Contains a collection of unrelated options, including /MADYMO/ON to activate MADYMO/RADIOSS couplings, /PATRAN to write PATRAN displacement and element files, /KEREL to set kinetic energy relaxation, and /KEREL/1 to set kinetic energy relaxation based on node group numbers. Contains options to set initial rotational and translational velocities for single or multiple sets of nodes. Contains options to set rotational and translational velocities. Contains a text box in which you can manually specify cards. Refer to the RADIOSS ENGINE documentation for syntax rules. The text box supports basic text editing, such as the Copy/Paste functions (CTRL+X, CTRL+C, CTRL+V). You can use this tab to paste plain text from an existing deck.
INIV
VEL UNSUP
The Engine File Tool also contains the following buttons, which are available from any tab. Apply Updates the database with the changes. Click Apply before exporting to ensure that all changes are included in the D01 file. Deletes data from the fields on the current tab. When you click the Clear button, you can select options from a pop-up menu to clear the values on the current tab (Clear Page ) or the fields on all tabs (Clear All). Deletes data on the current tab that has been entered since the last time the database was refreshed with the Apply button. Opens the Save As dialog, where you can specify the location of the D01 file. Click Export after entering all the required information on the tabs. Closes the Engine File Tool macro.
Clear
Undo
Export
Close
Altair Engineering

600
601

Altair Engineering
GENERAL Tab
Type values for the /TITLE, /RUN, and /VERS fields; these keywords are required. Optionally, select keywords from the bottom row. When you select a check box, rows are created in the table below, in which you can specify parameters for the keyword.
Click Apply to save the changes for the GENERAL tab.
Altair Engineering

602
ANIM Tab
Choose keywords by selecting the adjacent check box. For /ANIM/Key2/Key3, /ANIM/BRICK/TENS/Key4, ANIM/Key1/FORC, /ANIM/SHELL/TENS/Key4, and /ANIM/VECT/Key3 specify the number of cards you want to create by typing a value in the Card count field and pressing Enter. The corresponding number of rows will appear below for you to specify the keyword options. Select the keyword options from the drop down lists, as shown in the following example of /ANIM/Key2/Key3.
For /ANIM/SENSOR, type the number of cards in the Card count field and press Enter to create the corresponding number of rows below. Then type values for the sensor property set (ISens) and time frequency (Tfreq). Similarly for /ANIM/DT, type values for the start time (TStart) and time frequency (Tfreq). Click Apply to save the changes for the ANIM tab.
603

Altair Engineering
BC Tab
Choose keywords by selecting the adjacent check box. Type the number of cards in the Card count field and press Enter; the corresponding number of rows appears below in which you must select the directions (any combination of X, Y, and Z) for the rotational or material translational degrees of freedom. Choose a direction from the drop-down menus in the DOF list. Optionally, specify a frame number in the frame id column, which applies the boundary conditions only to the specified frame number. You can also choose a system from the model by right-clicking in the frame id column and selecting Pick System Id from Model. Then specify nodes for which the boundary condition is applied (or released) in the Nodes section at the bottom of the tab. You can type the node values in the cells directly or right-click on a cell and choose Pick Node from Model to select node data from the database. If you manually enter a node value that does not exist in the model, a warning message appears and the node value is displayed in red in the cell. Note: You can select multiple values at once by picking several nodes before clicking proceed. If you renumber the entities in HyperMesh, the node values you have already selected in the Engine File Tool will be automatically updated to reflect the new numbering.
Click Apply to save the changes for the BC tab.
Altair Engineering

604
605

Altair Engineering
DEL Tab
To select /DELINT and /DEL/INTER, select the adjacent check box. For /DEL/INTER, specify interface ID numbers in the cells below. Type a number in the field next to the check box and press Enter to create more rows of cells to type data into. For /DEL/Keyword2 and /DEL/Keyword2/1, select the check boxes next to the element types you want to delete. Type a number in the Card count field to create cards below. Then type element ID numbers in the cells or right-click in a cell and choose Pick Element from Model to pick an element from the model. If you manually enter a node value that does not exist in the model, a warning message appears and the node value is displayed in red in the cell. Note If you renumber the entities in HyperMesh, the node values you have already selected in the Engine File Tool will be automatically updated to reflect the new numbering.
Click Apply to save the changes for the DEL tab.
Altair Engineering

606
DT Tab
Select the check boxes of the keywords you want to include. For /DT, /DT1/SHELL, and /DTIX, specify values for the various scale and time options in the fields to the right of each check box. For /DT/Keyword2, specify a number of cards in the Card Count= field, which creates a row for each card in the table below. For each row, select an option type and type values for the time step scale factor, minimum time step, group node ID number, and group node flag. For /DT/Keyword2/Keyword3, specify a number of cards in the Card Count= field, which creates a row for each card in the table below. For each row, select the option type and time step control type and type values for the time step scale factor, minimum time step, group node ID number, and group node flag. Click Apply to save the changes for the DT tab.
607

Altair Engineering
FUNCT Tab
Select the check box to include the /FUNCT keyword, which is used to redefine the function number that was initially defined in the RADIOSS STARTER D00 file. Type a function number in the Add IFUNC field and press Enter. The function number appears in the IFUNC drop-down list. Then type the list of X and Y value pairs for the points. The number of points must match the number of points used to define the original function number. Click Apply to save the changes for the FUNCT tab.
Altair Engineering

608
INTER Tab
Select the check box to include the /INTER keyword, which is used to activate and deactivate interfaces. Type the number of cards in the Card Count field and press Enter. The corresponding number of rows appears in the table below. Type values in each column for the interface number, search cycle , start time , and stop time . Click Apply to save the changes for the INTER tab.
609

Altair Engineering
RBODY Tab
Select the check boxes to include the /RBODY/ON and /RBODY/OFF keywords. For each keyword, type the number of cards in the Card Count field and press Enter. The corresponding number of rows appears in the table below each keyword. Type values in the table cells for the primary node numbers of the rigid bodies. You can type the node values in the cells directly or right-click on a cell and choose Pick Node from Model to select node data from the database. If you manually enter a node value that does not exist in the model, a warning message appears and the node value is displayed in red in the cell. Note: You can select multiple values at once by picking several nodes before clicking proceed. If you renumber the entities in HyperMesh, the node values you have already selected in the Engine File Tool will be automatically updated to reflect the new numbering.
Click Apply to save the changes for the RBODY tab.
Altair Engineering

610
MISC Tab
For /MADYMO/ON and /PATRAN, select the check boxes and type values for the associated keyword options. For /KEREL, select the check box. For /KEREL/1, select the check box, type a number of cards in the Card Count field, and type node group numbers in the GR_Nodes list below. Click Apply to save the changes for the MISC tab.
611

Altair Engineering
INIV Tab
For all keywords on this tab, select the check box to include the keyword, type the number of cards in the Card Count field, and press Enter. The corresponding number of rows appears in the DOF list below each keyword. Select a degree of freedom for the rotational or translational velocity (any combination of X, Y, and Z) with the drop-down lists. Type node values in the table at the bottom of the tab. Increase the Card count field value to add more rows to the table. You can type the node values in the cells directly or right-click on a cell and choose Pick Node from Model to pick node data from the database. If you manually enter a node value that does not exist in the model, a warning message appears and the node value is displayed in red in the cell. Note: You can select multiple values at once by picking several nodes before clicking proceed. If you renumber the entities in HyperMesh, the node values you have already selected in the Engine File Tool will be automatically updated to reflect the new numbering.
Click Apply to save the changes for the INIV tab.
Altair Engineering

612
VEL Tab
Choose keywords by selecting the adjacent check box. Type the number of cards in the Card count field and press Enter; the corresponding number of rows appears below in which you must select the directions (any combination of X, Y, and Z) for the rotational velocity or velocity for material translational degrees of freedom. Choose a direction from the drop-down menus in the DOF list. Optionally, specify a frame number in the frame id column, which applies the velocity equation to the specified frame number. Then specify nodes on which the velocity equation will be applied in the Nodes section at the bottom of the tab. You can type the node values in the cells directly or right-click on a cell and choose Pick Node from Model to pick node data from the database. If you manually enter a node value that does not exist in the model, a warning message appears and the node value is displayed in red in the cell. Note: You can select multiple values at once by picking several nodes before clicking proceed. If you renumber the entities in HyperMesh, the node values you have already selected in the Engine File Tool will be automatically updated to reflect the new numbering.
Click Apply to save the changes for the VEL tab.
613

Altair Engineering
Meshless Welds Macro

The RADIOSS Meshless Welds macro is accessible through the Tools page on the RADIOSS Utility Menu . When you select the Welds button, the following dialog is displayed:
This macro allows you to create meshless welds for RADIOSS (Block Format) using /SPRING elements and /INTER/TYPE2 to connect the shell together. Additionally, a /PROP/SPR_BEAM with user-defined custom properties is created. The macro identifies the current template and creates welds for both RADIOSS (Fixed Format) or (Block Format) models.
To use the Meshless Welds macro:

1. Select a master weld file to define the weld locations. This file must contain the coordinates of the weld points and the component IDs of connected parts. Weld files can be written out by exporting connectors in the Export tab. Select the spring property file. Specify the Spring FE config and an appropriate weld research tolerance. Click create.
2. 3. 4.
Meshless welds are created and grouped into components based on the parts to which they are attached and the property of the spring is created according to the strength of attached parts. INTER/Type2 interfaces are created. Plot elements are created to facilitate the review of meshless welds and attached components. These plot elements connect the welds to corresponding parts.
Altair Engineering

614
You can select one of the following options: Activate create single components for spring to store all the /SPRINGs into the same component. Activate the Convert plotels to spring to replace the default HMPLOT element (not supported by RADIOSS) into a /SPRING element that can be imported back into the program and used together with find attached. Weld tolerance is used in the connector search algorithm to identify welds and attached parts. The spring property file defines the data to be used in computing spring properties for RADIOSS (Block Format) beam type springs /PROP/SPR_BEAM. The sample file, Radiossweld_config.ini, is stored in the hm\scripts\connectors directory of the Altair installation and its format is shown below. Radiossweld_config.ini n the hm\scripts\connectors\ # HWVERSION_11.0 Variables MASS Inertia K1 K2 K3 K4 K5 K6 Delmin1 Delmax1 Delmin2 Delmax2 Delmin3 Delmax3 Delmin4 Delmax4 Delmin5 Delmax5 Delmin6 Delmax6 End 0.002 0.1 100.0 500.0 500.0 5000.0 5000.0 5000.0 -1.25 1.25 -1.25 1.25 -1.25 1.25 0.0 0.0 0.0 0.0 0.0 0.0
615

Altair Engineering
# Normal Force Function CVID1 9 -100.0 -1.26 -1.25 -0.125 0.0 0.125 1.25 1.26 100.0 0.0 0.0 -Fn -Fn 0.0 Fn Fn 0.0 0.0
# End Normal Force Function
# Shear Force Function CVID2 9 -100.0 -1.26 -1.25 -0.125 0.0 0.125 1.25 1.26 100.0 0.0 0.0 -Fs -Fs 0.0 Fs Fs 0.0 0.0
# End Shear Force Function
Generic Spot Weld Failure Force Table Sheet metal gauge in mm T > Steel T =< YS < 120 MPa Shear force Fs[kN] Normal force Fn[kN]
Altair Engineering

616
~ 0.6 0.8 0.9 1.0 1.1 1.3 1.4 1.5 1.8 2.0 2.3 2.7
0.6 0.8 0.9 1.0 1.1 1.3 1.4 1.5 1.8 2.0 2.3 2.7 ~
2.7 3.6 4.4 5.3 6.2 7.1 8.0 9.1 11.1 12.5 15.1 18.2 21.8
0.9 1.2 1.5 1.9 2.2 2.5 2.8 3.2 3.9 4.4 5.3 6.4 7.6
Steel1 ~ 0.6 0.8 0.9 1.0 1.1 1.3 1.4 1.5 1.8 2.0 2.3 2.7
YS = 120to220 MPa 0.6 0.8 0.9 1.0 1.1 1.3 1.4 1.5 1.8 2.0 2.3 2.7 ~ 2.7 3.6 4.4 5.3 6.2 7.1 8.0 9.1 11.1 12.5 15.1 18.2 21.8 0.9 1.2 1.5 1.9 2.2 2.5 2.8 3.2 3.9 4.4 5.3 6.4 7.6
617

Altair Engineering
Steel3 ~ 0.6 0.8 0.9 1.0 1.1 1.3 1.4 1.5 1.8 2.0 2.3 2.7
YS = 221to500 MPa 0.6 0.8 0.9 1.0 1.1 1.3 1.4 1.5 1.8 2.0 2.3 2.7 ~ 4.9 6.7 8.5 10.2 12.0 13.8 15.6 17.8 21.8 25.0 31.1 38.7 44.5 1.7 2.3 3.0 3.6 4.2 4.8 5.5 6.2 7.6 8.8 10.9 13.5 15.6
Steel4 ~ 0.6 0.8 0.9 1.0 1.1 1.3 1.4 1.5 1.8 2.0 2.3 2.7
YS > 500 MPa 0.6 0.8 0.9 1.0 1.1 1.3 1.4 1.5 1.8 2.0 2.3 2.7 ~ 4.9 6.7 8.5 10.2 12.0 13.8 15.6 17.8 21.8 25.0 31.1 38.7 44.5 1.7 2.3 3.0 3.6 4.2 4.8 5.5 6.2 7.6 8.8 10.9 13.5 15.6
Altair Engineering

618
The values of relevant variables are defined in the first section and these values are copied directly onto the RADIOSS (Block Format) spring property cards. The second and third sections define the normal and shear force functions with nine data points. Based on the strength of the connected components, the Weld macro calculates appropriate force function for each weld. Except for the value of Fn and Fs, the data points remain constant and equal to the values defined in the normal and shear force functions. Force function defines deformation vs force values as required by RADIOSS (Block Format). Finally, the last section contains the force tables as a function of yield stress of the material. You can enter any number of tables into this section. Each table identifies the yield strength of the material and the normal and shear force of the weld corresponding to the thickness range. During the macro execution for every weld the macro identifies the connected parts and for each part, the macro extracts the corresponding shear and normal force from these tables based on the part thickness and material yield strength. The lowest shear and normal force of each weld is identified by comparing the force values of the attached components and is used in the spring property definition of the weld.
619

Altair Engineering
Material Table Macro

The Material Table macro, located on the Tools page of the RADIOSS (Block Format) Utility Menu, allows you to easily create materials for RADIOSS (Block Format).
To use the Material Table macro:

1. 2. Select the Tools macro page. Click the Material Table... macro button. All existing materials are retrieved and populated in the table.
The columns can be sorted by clicking the column heading, and can be resized by clicking and dragging the edges of the columns within the table itself. Create/Load Allows you to create a new material. There are three options, New..., Same as... and Load/edit. New... Opens entry fields and menus that allow you name and select the properties of the new material. To use the New... option: 1. 2. Enter a name for the new material in the New Material Name: field. Click the Material type: switch and select a material type from the drop-down menu. This menu contains the subcategories of materials. Each sub category clearly indicates the supported material type. Materials are listed with the MAT# and complete RADIOSS (Block Format) type. Select the type and click the create/edit button to create a material and open the card edit mode. 3. Input the appropriate values as necessary for the material in the card image.
Altair Engineering

620
4. 5. Same as
After you input the values, click return to exit from the panel. Click Return in the Material Table .
The parameters are exactly the same as New... except that the Material Type alias, existing material for Same as must be selected from the table. 1. 2. 3. 4. 5. 6. 7. Left click on the material row that you want to duplicate. Click Create/Load. Click Same as... Specify a name for the new material in the New Material Name: field. Click create/edit to display the card image. Specify the appropriate values and click return on the panel. Click Return in the material table. The E, Nu, and Rho columns are populated only if the fields are available in the material card.
Note:
Load/edit The Load/edit function allows you to change the material type of a selected material and load the appropriate card image so that you can make changes to it. 1. 2. 3. 4. 5. Edit... Merge As Check Duplicates Left click on the material row that you want to edit. Click Create/Load. Make a selection in the Material Type: field. Click the Load/edit button. Specify the appropriate values and click return on the panel.
Displays the card image, where you can input values.
621

Altair Engineering
Model Check Macro

Checks your model for potential problems with properties, materials, element quality, etc. and reports them on-screen. The report identifies the problem entity by ID and describes the error. You can use the results to quickly identify problems with your model so you can correct them. Various threshold settings are available from the Options menu to customize the range of data that is reported back as a potential problem in the model. The available checks are sorted into four types of tests: Properties, Materials, Element Quality, and BCs and Cards. You can select how many of these tests are run.
To set up and run a model check:

1. Click Model Check in the Utility Menu. The RADIOSS Model Checker dialog appears. 2. 3. 4. 5. Review the threshold settings in the Options menu. Set values that are meaningful for your model. Review the model check tool settings from the Interrogator Settings option of the Options menu. Choose which tests you want to run from the Select Tests option of the Run menu. Tests that have a check mark next to them will be run. From the Run menu, select Run Interrogator. The model check begins and the results appear in a text report in the RADIOSS Model Checker dialog.
The report can be saved as a plain text file by selecting Save Report from the File menu. Additionally, model check test settings can both be saved and imported from the Options menu.
Altair Engineering

622
Component Table
The RADIOSS (Block Format) Component Table is an interactive tabular list used to represent RADIOSS (Block Format) components with associated properties and materials. It is accessed by loading the RADIOSS (Block Format) user profile and clicking the Component Table button on the Utility Menu. The table contains a variety of tools that allow you to review, edit and update the model. The essential features are: RADIOSS (Block Format) components with various associated properties and materials are listed in separate columns. You can select the column types from a set of available options. There are two modes of operation: review and editable . The review mode allows you to quickly review the component information without changing any values. The editable mode allows you to change values for the selected components. There are enhanced selection, review , display and filter options for components. Components can be sorted according to any available column. The current configuration is saved automatically to a file at the end of a session and recalled on reload. You can also save and load a configuration file. The table data can be exported in CSV and HTML formats. Right-click on the table to display menu options. All pull-down menu options are also available using a right-click. Columns can be moved or swapped by holding the left mouse button on a column title and dragging it to the desired location. Columns can be resized by positioning the cursor along a column border, pressing the left or right mouse button and dragging the border to a new position. The shift or control key combined with a left click can be used to select multiple rows. The following tools are available in the RADIOSS (Block Format) Component Table : Table Refresh Editable Regenerates the table with all the parts in the model Sets the table mode to editable mode, allowing you to change values for the selected components Enables the filtering GUI Allows you to specify the number and type of columns listed in the table Saves the information listed in the table in CSV or HTML format Quit the table function.
Filter Configure Save Quit
623

Altair Engineering
Selection All None Reverse Displayed User Selects all rows or parts Selects none or deselects parts/rows that were previously selected Reverses the selection Selects the rows or the displayed parts User graphic interaction to select parts
Display By default, the table is invoked with only the displayed parts. You can refresh the table to show a new part being displayed or use one of the following display commands. All None Reverse Show selection Show only Selection Hide selection By Material By Properties By Thickness Displays all the components in the model Turns off every component displayed Reverses the display of the part Displays the components of the selected rows Displays only the components of the selected rows Hides the components of the selected rows from the display Displays components sorted by material Displays components sorted by properties Displays components sorted by thickness values
Action Delete Selection Create Part Deletes selected rows (parts) from the model
Altair Engineering

624
User Set MatDB Path Opens a dialog on which you can set the location of an external database of material definitions. Updates the list of available materials in the Component Table .
Refresh Material List
See also Editable Mode Filter Configure Columns All or Displayed Mode
625

Altair Engineering
Editable Mode
The editable mode in the Component Table allows you to change values for all selected components at the same time. Select the Table > Editable option to open the Component Table in editable mode. Cells with a white background can be manually edited. When you click on an editable cell, it is selected with a cursor. Once a cell is selected, enter a value and press Enter. If you want to assign the same value to multiple components at once, select the column type and value from the Assign Values: pull-down menu and click Set. All the selected components will be updated with the assigned values.
See also Component Table RADIOSS (Block Format) Utility Menu
Altair Engineering

626
Filter
The Components and Properties Table supports advanced filtering based on available columns. The Table > Filter... menu option opens the Filter dialog as shown below. You can write any valid string with a wildcard (*) in any of the available column types and click Apply to filter the table. For example, if you want to show all properties that start with letter c and use material type steel, you can use the dialog as shown below. Note that the filter strings are case-sensitive.
Show All turns off the filtering and displays all the components. Select the Table > Configure > Filter on top option to keep the Filter dialog posted after clicking Apply or Show All. Otherwise, it closes.
627

Altair Engineering
Configure Columns
Column types can be selected from the Table > Configure > Columns... menu option. The table displays only the selected columns. The available columns types are: Title Vis Part Title Part id Prop name Prop id Prop Type Material name Material id Material type Thick Elems Nodes Color SigY Harden_Param(b) Mass cg_x cg_y cg_z Total mass of the component Center of gravity for the x coordinate Center of gravity for the y coordinate Center of gravity for the z coordinate Description Visualization status. 1 = display on, 0 = display off Title of the part HyperMesh ID of the component HyperMesh name of the property HyperMesh ID of the property Property type associated with the component Material name associated with the component Material ID associated with the component Material type associated with the component Thickness of elements specified in *section_shell Number of elements in the component Number of nodes in the component Component color
Altair Engineering

628
629

Altair Engineering
All or Displayed Mode

The Component Table lists components in two modes: All or Displayed. If All is selected from the Table > Configure > Components menu, the table will list all the components in the model. If Displayed is selected, only the visible components will be shown. Blank components are not shown in the Displayed mode even though their display status is on.
Altair Engineering

630
Other Tools
The following tools are also available:
Accelerometer Tool Relative Displacement Tool BCs Manager Tool
631

Altair Engineering
Accelerometer Tool
The Accelerometer tool helps you create and edit time history ACCEL cards to track accelerometer output requests. This tool will automatically create the ACCEL card as part of an output block. To display the tool, select Accelerometer on the Utility Menu. The tool appears as a tab in the tab area.
Creating Accelerometers
To create a new accelerometer, begin by typing a name in the Accelerometer Name field, selecting a node for the accelerometers location, specifying a cut off frequency value (Fcut), and specifying a system. Systems can be selected from existing systems, or you can create a new system from the Accelerometer tools interface. To create a system, enter a name in the Accelerometer: field and click Create/edit. Choose whether the new system is moving or fixed, and choose the coordinate combination that will define the system. To use an existing system, specify it with the System input collector, which is visible when Select is active on the System toggle. Click Create to choose to either create the card only, or create the card and open it for editing.
Modifying Existing Accelerometers

Accelerometers that already exist in the model can also be modified through the Accelerometer tool. All existing accelerometers are listed at the top of the tab. Select a tool to display its current settings on the tab. An example is shown below.
Double-click the display fields to update the values for the name, location, cut off frequency, and system. The ACCEL card opens for editing in the main menu area, where you can make updates and click return to save the changes to the card.
Altair Engineering

632
Relative Displacement Tool

The Relative Displacement tool interactively helps you create the TH/SPRING card, which supports time histories with spring output. This tool appears as a tab named Relative Displacement. To display the tool, select Relative Displacement from the Utility Menu. The tool appears as a tab in the tab area.
Creating Time Histories of Springs

1. To begin creating a time history of springs, type a name in the Time History Name field and click Create/Edit A pop-up menu appears from which you can choose either to create the spring and edit the card that is generated or simply create the spring.
633

Altair Engineering
2. 3.
The time history appears in the Output Blocks list. Right-click the list item and select Add Springs to create springs for that time history. You are prompted to pick nodes from the model to define springs. Note that the first node you select is used as Node1 in the definition of the spring.
Editing Time Histories of Springs

1. 2. To edit a time history, right-click its name in the Output Blocks list and select Edit. The card for that time history opens in the main panel area. From here you can provide names for each element, and add or modify variables. To add variables, click [NUM_VA to bring up a pop-up window of numbers. Click the number of variables you want to include in the card. Var fields appear where you can type the variable names.
When you use the relative displacement tool to create time histories of springs, you also create a component named Comp_Rel_Disp. This component is of the Springs/Rivets type and no material is assigned. The component contains one property, SPR_GENE, with only the mass value specified.
Altair Engineering

634
BCs Manager Tool

The BCs Manager tool can be used to create boundary conditions of any load collector type other than ACTIV. This tool combines required actions from several panels into one convenient tab interface, including the ability to create a boundary condition from both sets and individual nodes. To display the tool, select BCs Manager from the Utility Menu. The tool appears as a tab in the tab area.
635

Altair Engineering
Creating New Boundary Conditions
Altair Engineering

636
1. 2.
To begin creating a new boundary condition, select the type of boundary condition you want to create in the Select type: field. In the Name field, type a name for the load collector .
3. 4.
Select the type from the drop down menu in the Select type field. Based on the type selected, the options that display may change. Use the selectors to pick sets and/or individual nodes to define boundary conditions. The switch allows you change the selector to access parts, nodes, materials, properties, GRNOD (set), and GRNOD (box). Select the type of entity to be selected from the pull down menu and click on the yellow button to open the selector panel. Enter the loading conditions in the options. Empty fields require user input, and yellow buttons provide links to another entity that need to be linked; namely curve, system or sensor. Each yellow tab has two options: create /select and select. Create/select allows you to directly create the entity from this GUI Select allows you to select an entity already defined
5.
6.
Click Create to create the database with the boundary condition data entered. Click Cancel to cancel the creation and Close to close the dialog.
Updating Existing Boundary Conditions

1. Highlight a boundary condition in the list to display its properties. This opens the editing mode of the dialog, as shown below.
637

Altair Engineering
2.
In Review mode every defined entity/entry in the field can replaced with new entity or modified. To replace the entity on which boundary condition is define, set the GRNOD tab to the desired entity to be selected and make the selection. The selection will replace the existing entity on which the BC is defined. Similarly the curve, system and sensor can be changed. The table appears with list of entities that are referred in the selected boundary condition. To edit the exiting entity, select the entity, right-click on it and select edit. This opens a corresponding panel with editing features. Update : update the changes made to the selected boundary condition. Click return to go back to Create mode. Cancel: Nullify all updates made to the selected boundary condition. Click return to go back to Create mode. Close: Nullify all updates to the selected boundary condition and close the dialog Review: Highlight the entities on which the selected boundary condition is defined
3.
Altair Engineering

638
Table functions
The table in the dialog lists the boundary conditions in the model by default. This can be limited to the desired boundary condition using the select type option on the top of the table. Right-clicking on each entity in the table provides the following functions: Refresh list: Refreshes the table based on the option in the select type field Card edit: Opens the selected boundary conditions's card image panel Delete: Deletes the selected boundary condition Review: Highlights the entities on which the selected boundary condition is defined and grays out the others Clear review: Returns the graphics window to regular mode Show all: No pre-selection is needed. Displays the part on which the boundary conditions in the table are defined and shows the load with handles Show: Displays the part on which the selected boundary condition is defined (if hidden) and shows the load with handle Isolate: Isolates the part on which the selected boundary condition is defined in the graphics and shows the load with handle
639

Altair Engineering
RADIOSS (Bulk Data Format), OptiStruct Utility Menu

The Utility Menu for the RADIOSS (Bulk Data Format), OptiStruct user profile contains, in addition to the default utility menus, three pages (Summary, FEA and Opti) of specific utilities for RADIOSS (Bulk Data Format) and OptiStruct. The Summary page provides a short summary of the entities making up the model. The FEA page is dedicated to modeling and load setup, while the OPTI page is devoted to optimization. The Utility Menu is available on the Utility tab when the RADIOSS (Bulk Data Format), OptiStruct user profile is loaded. The Utility tab may be activated/deactivated from the View menu.
See also Summary Page FEA Page Opti Page
Altair Engineering

640
Summary Page
The Summary page of the Nastran Utility Menu lists a short summary using displayed or entire model for components, loads, elements, center of gravity, moment of inertia, responses and constraints. See the examples below:
For components:
For elements:
641

Altair Engineering
Altair Engineering

642
FEA Page
The following macros are available on the FEA page of the Nastran Utility Menu: Auto Property Creation Auto Property Creation If two or more components points to single property this utility will create a separate property for each component.
Converters
I-DEAS to RADIOSS Export in MDL
Convert from I-DEAS to RADIOSS (Bulk Data Format) Export bodies (groups) and joint to an MDL (Model Definition Language) file to be read into MotionView.
Model Edit
Part Replacement
Replace elements in a component/part (PSHELL) with new elements.
Model Info
Material Table Component Table 1D Property Table Load Collector Table
Create, review and edit materials Create, review and edit components Create, review and edit properties Review and edit load collectors
Tools
Curve Editor TABLE Create
Launches the Curve Editor Create a tabular function card.
LoadSteps
Loadsteps Browser
Generate RADIOSS (Bulk Data Format) subcase definitions. Create a linear buckling subcase and referenced static subcase.
Buckling
Fatigue Process
Create New Load Existing
Solution
Model Checker
Model checker
643

Altair Engineering
Radioss OptiStruct
Shortcut to the Radioss panel. Shortcut to the OptiStruct panel.
Altair Engineering

644
I-DEAS to RADIOSS
The I-DEAS to RADIOSS converter utility will convert an I-DEAS input file to a RADIOSS (Bulk Data) input file. Follow these steps to perform a conversion. 1. 2. Select an I-DEAS file as the source file, or check the Use current HM model box to use the model loaded in the current session. Select a file name and location to save the RADIOSS (Bulk Data) file that will be generated, or check the Apply to current HM session only box to generate the RADIOSS (Bulk Data) model in the current session. Click Convert.
3.
645

Altair Engineering
Export in MDL
The Export in MDL utility enables you to export body and joint definitions in the current database to a MDL (Model Definition Language) file that can be opened with MotionView.
To export bodies and joints using the Export in MDL utility:

1. 2. Enter a file name in the Save file as: field or click on the open folder icon file pop-up window, choose where to save the generated MDL file. Click Accept to export body and joint definitions to an MDL file. The Treat flexible bodies as rigid bodies check box controls the output of flexible bodies. Flexible bodies may be exported as either rigid or flexible bodies (flexible body export is not available at this time). The Use prescribed cog, mass and inertias where available check box controls the output of cog, mass and inertia values for each body. If this check box is unchecked, HyperMesh determines these properties for each body based on the model data. If this check box is checked, the values defined on the parameters subpanel of the bodies panel, should they exist, will be exported instead. The Select nodes for additional point definitions in MDL check box allows nodes to be selected for which MDL point definitions will be exported to the file. and, on the Save
Altair Engineering

646
Part Replacement
The Part Replacement dialog enables you to replace elements in an existing component/part with new elements. It also restores the referenced items in the original model to the new part, e.g. 1-D connections, masses, equations, boundary conditions, and loads. A message log is provided, which lists the entities being replaced and reconnected as well as cases that require or will require user interaction. The Part Replacement dialog generates a log file that contains a list of the entities being replaced and reconnected in addition to cases that require user interaction.
To replace elements in parts using the Part Replacement macro:

1. From the Tools menu, click Part Replacement. The OptiStruct Part Replacement dialog appears:
2.
In the Old part field, select a component by clicking the button, which opens a comps selector in panel area. Choose a component and click proceed. The new part is created in the database. (If you already created a new part, delete it before performing this step.) In the New part field, select a part (sub-model) to import. Click Import.... (optional) Clear the Delete old part check box to save the old part at the end of the replacement procedure. (optional) Click View log at any time to open the Part Replacement macros log file. Click Next. In the New part field, select a component by clicking the comps button, which opens a comps selector in the panel area. Choose a component, click select and click proceed. Click Next. The following dialog appears:
3. 4. 5. 6. 7. 8.
647

Altair Engineering
9.
Select a material for the new part from the radio button list of available materials that appears in the dialog. Click Apply.
10. Specify a tolerance value for the Fix 1-D connections/meshless welds option. This option provides an automatic and an interactive reconnection to the new part for 1-D elements (beams, rigids, springs, etc.) and meshless welds (beam type 9 and hexa). The tolerance value determines the range of 1-D connections and meshless welds that will be replaced. Elements that cannot be replaced will be displayed in red.
Altair Engineering

648
11. Click Apply. The results of the replacement are displayed in tabs on the dialog.
13. Click the EID field on the 1-D tab to select the remaining elements, increase the tolerance, and preview the effect of the increased value on the 1-D elements. 14. Click Apply to use the defined tolerance to fix the elements displayed in green. A message appears that reports the tolerance used to fix the selected elements. If some elements still report as failed, repeat step 11 using a higher tolerance value. 15. Repeat steps 12 and 13 for the Meshless welds tab.
649

Altair Engineering
Masses attached to the old part can be connected to a new part using the basic steps outlined above. In addition, HyperMesh can detect and fix the following individual loads: forces, moments, temperatures, equations, and constraints. Pressure must be corrected manually.
Altair Engineering

650
Material Table
The Material Table utility is used to review and edit RADIOSS (Bulk Data) materials.
Icon Description
Create new material Refresh table Toggles between table edit and table display mode Filter table Export table to CSV format Select all Select none Reverse selection Select displayed Delete selected
651

Altair Engineering
Altair Engineering

652
Component Table
The RADIOSS (Bulk Data) Component Table displays components and their associated attributes in an interactive table. The information displayed in the table may be configured.
This utility also allows you to create components, assign materials to components, change component colors, and change component visualization modes. Most actions are available either from shortcut (rightclick) menus or from the pull-down menus. Before performing actions, such as changing the values of component data, you must select Editable from the Table menu. Once the table is editable, you can modify the values of existing components. The following sections describe how to use the component table in both read-only mode and editable mode. Using the Component Table in Read-Only Mode When you open the Component Table , displayed components are listed in a table using a default configuration. This configuration displays the name, ID number, type, thickness, material name, material ID, material type, color, and visibility (display) for each displayed component. The table may be adjusted to display information for all components by selecting Table > Configure > Components > All. The display of the Component Table can be customized according to your preferences. You can: Change which columns are displayed. Sort the components by column data, ascending or descending. Filter which components are displayed based on column data values (see below). You can save your settings by creating a configuration file. From the Table menu, open the Configure submenu and select the Save CFG-File option. This configuration file saves the set of table configuration options so you can use them again. By default, a configuration file (comptable.cfg) is saved in the working directory for each component table session and settings from this file are applied each time the table is built. Using the Component Table in Editable Mode
653

Altair Engineering
When you switch the Component Table from the default read-only mode to editable mode (by selecting Editable from the Table menu), you can perform all the actions described in the section above, plus edit the attributes of the components listed in the table. To change the value of an attribute, select the attribute in the Assign Values drop-down, type the new value in the adjacent field, and click Set.
Altair Engineering

654
Property Table
The RADIOSS (Bulk Data) Property Table displays properties and their associated attributes in an interactive table. The information displayed in the table may be configured.
This utility also allows you to create properties, assign materials to properties, and change property colors. Most actions are available either from shortcut (right-click) menus or from the pull-down menus. Before performing actions such as changing the values of property data, you must select Editable from the Table menu. Once the table is editable, you can modify the values of existing properties. The following sections describe how to use the Property Table in both read-only and editable modes.
Using the Property Table in Read-Only Mode

When you open the Property Table , all properties are listed in a table using a default configuration. This configuration displays the name, ID number, type, material name, material ID, material type, color, number of elements and visibility (display) for each property. The display of the Property Table can be customized according to your preferences. You can: Change which columns are displayed Sort the components by column data, ascending or descending Filter which components are displayed based on column data values (see below) You can save your settings by creating a configuration file. From the Table menu, open the Configure submenu and select the Save CFG-File option. This configuration file saves the set of table configuration options so you can use them again. By default, a configuration file (comptable.cfg) is saved in the working directory for each component table session and settings from this file are applied each time the table is built.
Using the Property Table in Editable Mode

When you switch the Property Table from the default read-only mode to editable mode (by selecting Editable from the Table menu), you can perform all the actions described in the section above, plus edit the attributes of the properties listed in the table. To change the value of an attribute, select the attribute in the
655

Altair Engineering
Assign Values drop-down, type the new value in the adjacent field, and click Set.
Altair Engineering

656
Load Collector Table

The Load Collector Table utility is used to review and edit RADIOSS (Bulk Data) load collectors.
Icon Description
Refresh table Toggles between table edit and table display mode Filter table Export table to CSV format Select all Select none Reverse selection Select displayed Delete selected
657

Altair Engineering
See also Utility Menu
Altair Engineering

658
Buckling
The Buckling utility allows a buckling subcase to be defined simultaneously with its referenced static subcase.
1. 2. 3.
Enter name. Provide data for V1, V2 (upper and lower limits for eigenvalue calculation) and/or ND (number of modes to be calculated). Select appropriate load collectors for LOAD and SPC references. Only load collectors containing valid loads are displayed in the drop down menus.
4.
Click Create. The EIGRL load collector is created. The static and buckling load steps are also created.
659

Altair Engineering
RADIOSS (Bulk Data Format) Model Checker

The RADIOSS (Bulk Data) Model Checker utility allows you to check the quality of elements, properties, materials, and load steps in a RADIOSS (Bulk Data) model. The dialog consists of four pull-down menus and a report window. The pull-down menus: File , Options, Run , and Help are described here: File Save Report Allows you to select a file name and location to save the information in the report window to a text file. Deletes everything from the report window. Exit and close the Model Checker.
Clear Report Window Close
Options
Open Settings Save Settings 1D Element Quality Settings
Allows you to retrieve settings from a data file. Allows you to save the current settings to a data file. Allows you to alter settings for 1-D element checks. The settings which can be altered are: Minimum 1-D element length (default = 0.0) Maximum 1-D element length (default = 20.0)
2D Element Quality Settings
Allows you to alter settings for 2-D element checks. The settings which can be altered are: Minimum 2-D element length (default = 0.0) Maximum 2-D element length (default = 20.0) Minimum jacobian value (default = 0.7) Maximum warpage (default = 5.0) Maximum aspect ratio (default = 5.0) Minimum quad angle (default = 45) Maximum quad angle (default = 135) Minimum tria angle (default = 20) Maximum tria angle (default = 120)
3D Element Quality Settings
Allows you to alter settings for 3-D element checks. The settings which can be altered are:
Altair Engineering

660
Minimum 3-D element length (default = 0.0) Maximum 3-D element length (default = 20.0) Minimum jacobian value (default = 0.7) Maximum warpage (default = 5.0) Maximum aspect ratio (default = 5.0) Minimum quad angle (default = 45) Maximum quad angle (default = 135) Minimum tria angle (default = 20) Maximum tria angle (default = 120) Minimum tetra-collapse value (default = 0.5) Property settings Allows you to alter settings for property checks. The settings which can be altered are: Shell Zero Gauge Threshold (default = 0.001) PSHELL or PCOMP components with a thickness less than this value fail this check. Cross Section Zero Area Threshold (default = 0.001) - PBAR, PBEAM or PROD properties with a cross-section less than this value fail this check. Material settings Allows you to alter settings for material checks. The settings which can be altered are: Zero Density Threshold (Default = 1e-9) - All material densities must be greater than this value. Zero Modulus Threshold (Default = 1e-3) - All modulii must be greater than this value. Zero Poisson's Ratio Threshold (Default = 1e-3) All Poisson's ratios must be greater than this value. Model Checker Settings Allows you to specify additional settings. Choose from the list: Perform 1-D element checks (Default = yes) Perform 2-D element checks (Default = yes) Perform 3-D element checks (Default = yes) Create sets for failed elements (Default = no)
661

Altair Engineering
Output % failed - element quality (Default = yes) Output warning/error count for property checks (Default = no) Settings to defaults (all) Reset all settings to defaults.
Run
Select Tests
Allows you to check which tests to perform from the list: Property Checks Material Checks Element Checks Loadstep Checks Default (all)
Run Model Checker
Performs model checking and populates the report window with the results.
Help
Help About
Provides operation instructions. Provides information about version and developer.
Altair Engineering

662
Opti Page
The following macros are available on the Opti page of the Nastran Utility Menu: Del All Opt Entities Deletes all DesignVariable, OptimizationResponse, DesignVariablePropertyRelationship, OptimizationConstraint, Objective, ObjectiveReference, OptimizationTableEntry, OptimizationEquation, DesignVariableLink, OptimizationControl, and OptimizationConstraintScreening entities.
Topology
Voxelmesh Hex-core Design Space Matfrac Reg. Volfrac
Creates voxels (hexa elements) from closed shell meshes.
Shortcut to the Topology panel. Setup a material fraction topology optimization. Create regional volfrac responses combining several components, properties or materials
Topography
Design Space
Shortcut to the Topography panel.
Shape
Create Shapes Shape Variables
Shortcut to the HyperMorph panels. Shortcut to the Shape panel.
Size
Size Variables PBAR, PROD Opti
Shortcut to the Size panel. Define size optimization for multiple PBAR or PROD sections. Define size optimization for multiple CBAR or CROD elements with circular section.
CBAR, CROD Opti
Optimization Info
Design Variables
Create, review and edit Size (including Gauge) and Shape Design Variables. Review and edit optimization constraints.
Design Constraints
663

Altair Engineering
Solution
OptiStruct OSSmooth OSSmooth Volume
Shortcut to the OptiStruct panel. Shortcut to the OSSmooth panel. Compute the volume enclosed by iso-density surface (Elements Displayed) After running OSSmooth this helps you to compute the true volume of the geometry recovered. The iso-surface must be displayed as elements. Use Nastran or STL format when running OSSmooth.
Altair Engineering

664
Voxelmesh
Available for the OptiStruct and Radioss (Bulk) user profiles on Windows, LINUX, IRIX, HPUX, SUN. Fills an enclose volume with voxels (hexas) of a predefined size. This type of mesh is only useful in topology optimization. It does not give meaningful results in a stress analysis. To work properly, the volume must be enclosed completely by shell elements (quads and trias) without TConnections or free edges. The normals of these elements should point inwards. The voxels (hexa elements) are stored in the component, hexas.
To generate a voxelmesh:
1. On the Opti page of the utility menu, under Topology: click Voxelmesh. A comps collector displays in the panel area. 2. 3. Select components that contain shell elements enclosing one volume. (If more than one volume is selected, normals should be adjusted manually). Click proceed. The Voxelmesh dialog is launched. 4. Check the relevant boxes: Perform element check: Checks for T-connections and free edges. If some are found, the results are stored in collectors of the corresponding names. Adjust normals: Automatic adjustment of normals (to inward). This works if the selection is one connected volume only. The volume may contain internal voids. Fill undercuts: Areas that are hidden in each coordinate direction are filled even if they are not touching the enclosed volume. These elements are stored in the component, hexasfill. One component for each number of inner nodes: The voxels created are stored in nine components (hexas0, hexas1...) depending on the number of nodes that are inside the volume. Note: Zero inner nodes may occur if one edge of the volume intersects the center of a hexa-face. Use local coordinates: Allows selecting a coordinate system along which to align the mesh. If no selection is made, the global (basic, screen) coordinate system is used. Edge size for hexa elements: Choose from Cubes or Rectangles. For cubes, enter a single value for the edge size; for rectangles enter x, y, and z edge lengths. Keep in mind that a grid of nodes is created for the box wrapping the
665

Altair Engineering
volume. So the memory usage may be high for unreasonably small values. 3. 4. Click Start. If you checked the Use local coordinates box, you will be prompted to select a coordinate system. Select the system and click proceed. The voxelmesh is generated.
Altair Engineering

666
Matfrac
Material Fraction optimization utility sets up an optimization problem to minimize the combined compliance index and constrain the volume fraction to be less than a user-defined value. 1. 2. 3. Click Matfrac. Enter a matfrac value. Click calculate. The objective is set to minimize COMB for the entire model, while constraining the VOLFRAC for the entire model to be less than the MATFRAC value entered.
667

Altair Engineering
Reg. Volfrac
The Reg. Volfrac utility creates a regional volume fraction response for a number of components, properties, or materials. 1. Click Reg. Volfrac. You are prompted to select a number of components, properties, or materials. 2. Select the entities. Volume responses are generated for each entity (vol#). An equation is then created to calculate the total volume fraction over the entire region. A function response is generated using the equation with reference to the volume responses.
Altair Engineering

668
PBAR, PROD Opti.

This utility may be used to set-up size optimization for multiple PBAR or PROD properties 1. Click PBAR, PROD Opti. You are prompted to select a number of properties. 2. 3. 4. 5. Select properties. Select either a PBAR or a PROD card and a section type. Enter initial values and bounds. Click calculate. Depending on the cross section, a number of design variables, equations, and DVPREL2 cards are generated.
669

Altair Engineering
CBAR, CROD Opti.

This utility may be used to setup size optimization for multiple CBAR or CROD elements. 1. Click CROD, CBAR Opti. You are prompted to select 1-D elements for topological optimization. 2. 3. Select elements. Select PBAR or PROD. A new PBAR or PROD property is created for each 1-D element selected. These properties are called DPROP#. A size design variable is created for each 1-D element selected. 4. Input the initial value and upper and lower limits for this variable. The design variables are called DV#. These design variables represent the cross-sectional area of each 1-D element. A DVPREL1 card is created linking each of the DV#s to the cross-sectional area of each DPROP# card. These are called DX#. For simplicity, we assume the 1-D elements have solid, circular cross-sections. Two equations are created to calculate the I and J values if the PBAR property type is chosen: a) Equation for Ix and Iy values : Y(X1) = 0.0796*X1**2 b) Equation for J values: Y(X1) = 0.1592*X1**2 A DVPREL2 card is created for the I1 value of each DPROP#, referencing equation (a) and the appropriate design variable. These are named DA#. A 2nd DVPREL2 card is created for the I2 value of each DPROP#, referencing equation (a) and the appropriate design variable. These are named DB#. A 3rd DVPERL2 card is created for the J value of each DPROP#, referencing equation (b) and the appropriate design variable. These are named DC#. A 3rd equation is created to calculate the regional volume fraction for all DPROP# properties: Y(X1,Xi,....,Xn) = (X1+Xi+....+Xn)/(X1o+Xio+...+Xno) where Xi is the value of DVi, and where Xio is initial value of Xi. A function response, called BVFRAC, is generated using this equation and referencing all design variables.
Altair Engineering

670
671

Altair Engineering
Design Variables
The Design Variables utility is used to review and edit OptiStruct size (including gauge), and shape design variables. All DESVAR design variables are listed in the table.
To edit a design variable:

1. 2. 3. In the table, click on the Initial Value, Lower Bound, or Upper Bound field of a design variable. Replace the current value with the desired value. Hit the Enter key. The design variable is updated.
To create a design variable:

1. Click .
The following dialog is displayed.
Altair Engineering

672
2. 3.
Fill in the fields as desired. Click Create.
Icon Description
Create new design variables Refresh table Toggles between table edit and table display mode Filter table Export table to CSV format Select all Select none Reverse selection Select displayed Delete selected
673

Altair Engineering
Altair Engineering

674
Design Constraints
The Design Constraints utility is used to review OptiStruct optimization constraints. All optimization constraints are listed in the table.
Icon Description
Refresh table Toggles between table edit and table display mode Filter table Export table to CSV format Select all Select none Reverse selection Select displayed Delete selected
675

Altair Engineering
Altair Engineering

676
HyperMesh Entities & Solver Interfaces

HyperMesh Entities HyperMesh is architected around entities and solver interfaces. HyperMesh entities can have none or multiple card images associated to them. Card images are defined within a solver interface template and allow for creation, editing, and deletion of a solver card within a HyperMesh model. HyperMesh entities contain two types of data; data names and attributes. Data names are a part of the entity data structure itself and are available to all instantiations of the entity regardless if the entity has an associated card image or not. Attributes are additional data, defined in a solver interface template, which are necessary to store solver specific data for a card image associated with an entity. HyperMesh entities can be subdivided into five major groups; Collectors, Collected Entities, Named Entities, Optimization Entities, and Morphing Entities. Collectors are named organizational containers for Collected Entities. An example of a Collector is the component collector which collects points, lines, surface, solids, elements, and connectors for model organization purposes. Collected Entities are nameless entities which must reside within one, and only one, collector. Examples of collected entities include points, lines, surfaces, solids, elements, and connectors, which are collected by a component collector. Named entities are entities which are given a name but are not collected or organized into containers. Examples of named entities include materials and properties. Optimization entities and morphing entities are special groupings of named entities for optimization and morphing specific data respectively. Include Files Collectors and Collected Entities Named Entities Optimization Entities Morphing Entities
Solver Interfaces A solver interface is made up of a template and an FE-input reader. A template defines the mapping between solver cards and HyperMesh entities, the attributes necessary to store data for solver cards, and the format which the solver cards are exported from a HyperMesh database. FE-input readers perform the function of reading solver decks and importing solver cards into the appropriate HyperMesh entities with the appropriate card images, data names, and attributes set as defined by the template. Furthermore, FE-input readers require template attribute definitions to perform their tasks. A schematic of the HyperMesh solver interface architecture is shown below.
677

Altair Engineering
Templates An example of the interaction between HyperMesh entities and templates with data names and attributes for a RADIOSS (Bulk Data Format) MAT1 card is given below. The RADIOSS (Bulk Data Format) MAT1 card has the following definition: (1) MAT1 (2) MID ST (3) E SC (4) G SS (5) NU (6) RHO (7) A (8) TREF (9) GE (10)
The HyperMesh material named entity has data names of name and ID. Therefore the template would also have to define attributes for E, G, NU, RHO, A, TREF, GE, ST, SC, and SS in order to completely define and store the RADIOSS (Bulk Data Format) MAT1 solver card within a HyperMesh material named entity with a MAT1 card image. Templates define attributes using the *defineattribute() command. The example template code uses the *defineattribute() command to define these attributes. In order to associate the RADIOSS (Bulk Data Format) MAT1 solver card to the HyperMesh material named entity with a MAT1 card image the template would contain a *materials(MAT1) definition block to define this association. Within the *materials(MAT1) definition block a MAT1 card image would be defined using a *beginmenu() definition block . This *beginmenu() definition block is read every time a materials named entity with a MAT1 card image is card edited using the card editor within HyperMesh. In addition, an export format for the RADIOSS (Bulk Data Format) MAT1 solver card would be defined using a *format() definition block within the *materials(MAT1) definition block. This *format() definition block is read every time an export of the HyperMesh database is requested which contains a materials named entity with a MAT1 card image. Example template code which performs these definitions for the RADIOSS (Bulk Data Format) MAT1 solver card is given. For more information on templates see Custom Templates in the HyperMesh Reference Manual.
Loading a Template
Altair Engineering

678
Templates are necessary to tell HyperMesh how entities behave and what data are associated with them. HyperMesh cannot be used efficiently until a template is loaded. Templates are loaded into HyperMesh using the global panel. The global panel can be accessed using the 'g' key. Once a template is loaded into HyperMesh, it can be used to create, edit, card edit, and delete entities with card images which are defined within the template. Copy the example template code into a text editor, save as a file, and load into a new session of HyperMesh using the global panel. Alternatively the example template code can be found in [Install Directory]\hm\examples\templates.
Creating and Card Editing Entities HyperMesh is now ready to create, edit, card edit, and delete material entities with a MAT1 card image. The Model Browser can be used to create and card edit a material entity with a MAT1 card image. Within the Model Browser, right click to bring up the context sensitive menu. Select Create and select Material to display the Create Material dialog. Enter information as shown to create a material named entity called Aluminum with a MAT1 card image.
679

Altair Engineering
Now that a material entity with a MAT1 card image, named Aluminum, has been created it can be card edited to enter the remaining attributes that were defined for the MAT1 card image in the template. Using the Model Browser, left click the Aluminum material entity to select it, then right click right on the entity to bring up the context sensitive menu associated with that entity. On the context sensitive menu select Card Edit... to bring up the card editor for the Aluminum material entity and enter data for the attributes associated with the MAT1 card image as shown. Clicking return to close the card editor saves the data entered for the attributes on the entity. These are the basic operations in HyperMesh for creating and card editing entities with card images.
Altair Engineering

680
681

Altair Engineering
Exporting a HyperMesh Database as a Solver Deck Now that a material entity with a MAT1 card image exists in the HyperMesh database, the database can be exported as a Solver Deck. The example template code defined the export format for material entities with MAT1 card images using the *format() definition block within the *materials(MAT1) definition block. To export a HyperMesh database as a solver deck, click the export icon on the standard toolbar to bring up the Export tabbed dialog. On the Export dialog define: File type: Custom (for a custom template. This will automatically be set if you are using user profiles in HyperMesh) Template: Select the template file you saved. (This will automatically be set if you are using user profiles in HyperMesh) File: Enter a file name to contain the exported solver deck. Click Export to perform the export of the HyperMesh database as a Solver Deck.
Altair Engineering

682
The solver deck exported above is shown below. Notice that the file contains a single MAT1 solver card with the same data as the data entered on the MAT1 card image of the material named entity, Aluminum, as this is the only entity in the database. Also notice that the solver deck is exported in 8 character field widths as this is what was defined in the *format() definition block within the *materials(MAT1) definition block. Example Exported Solver Deck ([Install Directory] \hm\examples\feinput\ExampleExport.fem) MAT1 11.00E+070.0 0.0 0.33 0.101 1.20E-050.0 0.0
60000.0 0.0
FE-Input, Importing a Solver Deck into a HyperMesh Database The role of an FE-input reader within a solver interface is to read solver decks and import each solver card into the appropriate HyperMesh entity with the appropriate card image, data names, and attributes defined by the template. FE-input readers are C/C++ code written using the HyperMesh hm.lib and hmin.lib libraries as the API for creating entities in the HyperMesh database. Example FE-input code for the ExampleTemplate.tpl is given. This code can be copied and compiled with any ANSI C++ complier using hmlib.h and hminlib.h header files and hm.lib and hmin.lib libraries. See the notes section below for location of header files, libraries, and example code. For more information on FE-input readers see Custom Readers in the HyperMesh Reference Manual. To import a Solver Deck into the HyperMesh database, click the import icon on the standard toolbar to bring up the Import tabbed dialog. On the Import dialog define: File type: Custom (for customer FE-input readers. This will automatically be set if you are using user profiles in HyperMesh) Reader: select the ExampleFEInput reader executable compiled with below code. (This will automatically be set if you are using user profiles in HyperMesh) File: enter a file name that contains the solver deck. Click Import to perform the import of the Solver Deck into a HyperMesh database.
683

Altair Engineering
Notes: Templates for HyperMesh supported solver interfaces are located in [Install Directory] \templates\feoutput. FE-input readers for HyperMesh supported solver interfaces are located in [Install Directory]\io\model_readers\feinput\bin\[Platform] Macro files and Tcl/Tk scripts for HyperMesh supported solver interfaces are located in [Install Directory]\hm\scripts\[Solver Interface] HMLIB.H and HMINLIB.H can be found in [Install Directory]\hm\include HM.LIB and HMIN.LIB can be found in [Install Directory]\hm\lib\[Platform] The Example Templates can be found in [Install Directory]\hm\examples\templates The Example FE-Input readers can be found in [Install Directory] \hm\examples\feinput
See also The HyperMesh Environment Browsers Collectors and Collected Entities Named Entities
Altair Engineering

684
Morphing Entities Optimization Entities Solver Templates FE Input and Result Readers
685

Altair Engineering
Example Template Code

Example Template Code ([Install Directory]\hm\examples\templates\ExampleTemplate.tpl) * c odenam e( Ex am pl eTem pl at e, 100) //M AT1 At t r i but es * def i neat t r i but e( M AT1, 1, i nt eger , none) * def i neat t r i but e( E, 2, r eal , none) * def i neat t r i but e( G, 3, r eal , none) * def i neat t r i but e( NU, 4, r eal , none) * def i neat t r i but e( RHO, 5, r eal , none) * def i neat t r i but e( A, 6, r eal , none) * def i neat t r i but e( TREF, 7, r eal , none) * def i neat t r i but e( GE, 8, r eal , none) * def i neat t r i but e( ST, 9, r eal , none) * def i neat t r i but e( SC, 10, r eal , none) * def i neat t r i but e( SS, 11, r eal , none) //M at er i al s Nam ed Ent i t y - M AT1 Car d I m age and Ex por t For m at *m at er i al s ( M AT1) //M AT1 Car d I m age * begi nm enu( ) *m enus t r i ng( " M AT1 ")
*m enuf i el d( " I D" , i nt eger , i d, 8) *m enuf i el d( " E" , r eal , $E, 8) *m enuf i el d( " G" , r eal , $G, 8) *m enuf i el d( " NU" , r eal , $NU, 8) *m enuf i el d( " RHO" , r eal , $RHO, 8) *m enuf i el d( " A" , r eal , $A, 8) *m enuf i el d( " TREF" , r eal , $TREF, 8) *m enuf i el d( " GE" , r eal , $GE, 8) *m enul i neend( ) *m enus t r i ng( " ")
*m enuf i el d( " ST" , r eal , $ST, 8) *m enuf i el d( " SC" , r eal , $SC, 8)
Altair Engineering

686
*m enuf i el d( " SS" , r eal , $SS, 8) *m enul i neend( ) * endm enu( ) //M AT1 Ex por t For m at * f or m at ( ) * s t r i ng( " M AT1 ")
* f i el d( i nt eger , i d, 8) * f i el d( r eal , $E, 8) * f i el d( r eal , $G, 8) * f i el d( r eal , $NU, 8) * f i el d( r eal , $RHO, 8) * f i el d( r eal , $A, 8) * f i el d( r eal , $TREF, 8) * f i el d( r eal , $GE, 8) * end( ) * s t r i ng( " ")
* f i el d( r eal , $ST, 8) * f i el d( r eal , $SC, 8) * f i el d( r eal , $SS, 8) * end( ) * out put ( )
See also HyperMesh Entities & Solver Interfaces
687

Altair Engineering
Example FE-Input Code

Example FE-Input Code ([Install Directory]\hm\examples\feinput\ExampleFEInput.cxx) #i nc l ude <i os t r eam > #i nc l ude <f s t r eam > #i nc l ude <c s t r i ng> #i nc l ude " hm l i b. h" #i nc l ude " hm i nl i b. h" us i ng nam es pac e s t d; //M at er i al Dat a St r uc t ur e i nt num m at er i al s ; s t r uc t m at er i al s { c har nam e[ 12] ; i nt i d; doubl e E; doubl e G; doubl e NU; doubl e RHO; doubl e A; doubl e TREF; doubl e GE; doubl e ST; doubl e SC; doubl e SS; } m at er i al [ 100] ; / / Func t i on Pr ot ot y pes i nt get _dat a( c har * f i l ept r ) ; ent i t y f unc t i onpt r HM _get f unc t i on( i nt f unc t i on, HM _ent i t y t y pe ent i t i es ) ; i nt HM _get M at er i al s ( ) ; i nt m ai n( i nt ar gc , c har * ar gv [ ] ) { / * The m ai n f unc t i on c al l s get _dat a t o pr oc es s t he dat a i n t he s ol v er dec k , i ni t i al i z es Hy per M es h, s et s t he s ol v er t o 100 ( t he s am e num ber def i ned in t he t em pl at e) , r eads t he m odel and pas s es m at er i al dat a s t r uc t ur es t o Hy per M es h, and f i nal l y c l os es t he c onnec t i on bet ween HM and t he FE- i nput r eader . */ get HM I HM I HM I HM I _dat a( ar gv [ 1] ) ; N_i ni t ( " Ex am pl eFEI nput " , " 10. 0" , ar gc , ar gv ) ; N_s et s ol v er ( 100) ; N_r eadm odel ( HM _get f unc t i on) ; N_c l os e( ) ;
r et ur n( 0) ; } i nt get _dat a( c har * f i l ept r ) { / * Thi s f unc t i on opens a s ol v er dec k def i ned as t he f i r s t ar gum ent on t he
Altair Engineering

688
i nput l i ne and r eads t he s ol v er dec k f or M AT1 c ar ds . f ound t hen t he M AT1 s ol v er c ar d i s r ead and a m at er i al popul at ed. * / i f s t r eam i nf i l e; c har t ok en[ 9] ; c har l i ne[ 128] ; / / Open Sol v er Dec k i nf i l e. open( f i l ept r , i os : : i n) ; i f ( i nf i l e. f ai l ( ) ) r et ur n( 1) ;
If a M AT1 c ar d i s
dat a s t r uc t ur e i s
/ / Read Sol v er Dec k f or M AT1 Sol v er Car ds and Popul at e M at er i al Dat a St r uc t ur e num m at er i al s = 0; whi l e ( ! i nf i l e. eof ( ) ) { i nf i l e. get ( t ok en, 9) ; i f ( st r cm p( t ok en, " M AT1 " ) == 0) { / / Nam e s t r c py _s ( m at er i al [ num m at er i al s ] . nam e, " m at er i al " ) ; //id i nf i l e. get ( t ok en, 9) ; m at er i al [ num m at er i al s ] . i d = at oi ( t ok en) ; //E i nf i l e. get ( t ok en, 9) ; m at er i al [ num m at er i al s ] . E = at of ( t ok en) ; //G i nf i l e. get ( t ok en, 9) ; m at er i al [ num m at er i al s ] . G = at of ( t ok en) ; / / NU i nf i l e. get ( t ok en, 9) ; m at er i al [ num m at er i al s ] . NU = at of ( t ok en) ; / / RHO i nf i l e. get ( t ok en, 9) ; m at er i al [ num m at er i al s ] . RHO = at of ( t ok en) ; //A i nf i l e. get ( t ok en, 9) ; m at er i al [ num m at er i al s ] . A = at of ( t ok en) ; / / TREF i nf i l e. get ( t ok en, 9) ; m at er i al [ num m at er i al s ] . TREF = at of ( t ok en) ; / / GE i nf i l e. get ( t ok en, 9) ; m at er i al [ num m at er i al s ] . GE = at of ( t ok en) ; i nf i l e. get ( ) ; / / Bl ank Fi el d i nf i l e. get ( t ok en, 9) ; / / ST i nf i l e. get ( t ok en, 9) ;
689

Altair Engineering
m at er i al [ num m at er i / / SC i nf i l e. get ( t ok en, m at er i al [ num m at er i / / SS i nf i l e. get ( t ok en, m at er i al [ num m at er i i nf i l e. get ( ) ; num m at er i al s ++; } el s e
al s ] . ST = at of ( t ok en) ; 9) ; al s ] . SC = at of ( t ok en) ; 9) ; al s ] . SS = at of ( t ok en) ;
i nf i l e. get l i ne( l i ne, s i z eof ( l i ne) ) ; } r et ur n( 0) ; } ent i t y f unc t i onpt r HM _get f unc t i on( i nt f unc t i on, HM _ent i { / * Thi s us er - def i ned f unc t i on i s pas s ed i nt o hm i us ed by hm i nl i b t o f i nd al l of t he us er - def i ned whi c h per f or m r eadi ng and i nf or m at i on pas s i ng. t hat i f a us er - def i ned f unc t i on i s not r equi r ed, m us t r et ur n NULL. * / s wi t c h ( f unc t i on) { c as e HM I N_OPENFUNCTI ON: br eak ; c as e HM I N_ENTI TYOPENFUNCTI ON: br eak ; c as e HM I N_ENTI TYGETFUNCTI ON: s wi t c h ( ent i t i es ) { c as e HM _ENTI TYTYPE_NULL: br eak ; c as e HM _ENTI TYTYPE_CARDS: br eak ; c as e HM _ENTI TYTYPE_SYSTCOLS: br eak ; c as e HM _ENTI TYTYPE_SYSTS: br eak ; c as e HM _ENTI TYTYPE_NODES: br eak ; c as e HM _ENTI TYTYPE_VECTORCOLS: br eak ; c as e HM _ENTI TYTYPE_VECTORS: br eak ; c as e HM _ENTI TYTYPE_M ATS: r et ur n( HM _get M at er i al s ) ; c as e HM _ENTI TYTYPE_PROPS: br eak ; c as e HM _ENTI TYTYPE_COM PS: t y t y pe ent i t i es ) nl i b and i s f unc t i ons Not e t hi s f unc t i on
Altair Engineering

690
br eak ; c as e HM _ENTI br eak ; c as e HM _ENTI br eak ; c as e HM _ENTI br eak ; c as e HM _ENTI br eak ; c as e HM _ENTI br eak ; c as e HM _ENTI br eak ; c as e HM _ENTI br eak ; c as e HM _ENTI br eak ; c as e HM _ENTI br eak ; c as e HM _ENTI br eak ; c as e HM _ENTI br eak ; c as e HM _ENTI br eak ; c as e HM _ENTI br eak ; c as e HM _ENTI br eak ; c as e HM _ENTI br eak ; c as e HM _ENTI br eak ; c as e HM _ENTI br eak ; c as e HM _ENTI br eak ; c as e HM _ENTI br eak ; c as e HM _ENTI br eak ; c as e HM _ENTI br eak ; c as e HM _ENTI br eak ; c as e HM _ENTI br eak ; c as e HM _ENTI br eak ; c as e HM _ENTI br eak ; c as e HM _ENTI br eak ;
TYTYPE_GROUPS: TYTYPE_ELEM S: TYTYPE_LOADCOLS: TYTYPE_EQUATI ONS: TYTYPE_LOADS: TYTYPE_GEOM ETRY: TYTYPE_LI NES: TYTYPE_SURFS: TYTYPE_POI NTS: TYTYPE_ASSEM S: TYTYPE_CURVES: TYTYPE_PLOTS: TYTYPE_BLOCKS: TYTYPE_TI TLES: TYTYPE_SETS: TYTYPE_OUTPUTBLOCKS: TYTYPE_LOADSTEPS: TYTYPE_SENSORS: TYTYPE_DESI GNVARS: TYTYPE_BEAM SECTCOLS: TYTYPE_BEAM SECTS: TYTYPE_OPTI TABLEENTRS: TYTYPE_OPTI FUNCTI ONS: TYTYPE_OPTI RESPONSES: TYTYPE_DVPRELS: TYTYPE_OPTI CONSTRAI NTS:
691

Altair Engineering
c as e HM _ENTI br eak ; c as e HM _ENTI br eak ; c as e HM _ENTI br eak ; c as e HM _ENTI br eak ; c as e HM _ENTI br eak ; c as e HM _ENTI br eak ; c as e HM _ENTI br eak ; c as e HM _ENTI br eak ; c as e HM _ENTI br eak ; c as e HM _ENTI br eak ; c as e HM _ENTI br eak ; c as e HM _ENTI br eak ; c as e HM _ENTI br eak ; c as e HM _ENTI br eak ; c as e HM _ENTI br eak ; c as e HM _ENTI br eak ; c as e HM _ENTI br eak ; c as e HM _ENTI br eak ; c as e HM _ENTI br eak ; c as e HM _ENTI br eak ; c as e HM _ENTI br eak ; c as e HM _ENTI br eak ; c as e HM _ENTI br eak ;
TYTYPE_DESVARLI NKS: TYTYPE_OBJ ECTI VES: TYTYPE_CONTROLVOLS: TYTYPE_M ULTI BODI ES: TYTYPE_ELLI PSOI DS: TYTYPE_OPTI CONTROLS: TYTYPE_OPTI DSCREENS: TYTYPE_TAG: TYTYPE_M BJ OI NT: TYTYPE_M BPLANE: TYTYPE_DOBJ REFS: TYTYPE_CONTACTSURFS: TYTYPE_CONNECTORS: TYTYPE_SYM M ETRYS: TYTYPE_HANDLES: TYTYPE_DOM AI NS: TYTYPE_SHAPES: TYTYPE_SOLI DS: TYTYPE_M ORPHCONSTRAI NTS: TYTYPE_HYPERCUBES: TYTYPE_DDVALS: TYTYPE_BAGS: TYTYPE_M AX:
} br eak ; c as e HM I N_ENTI TYCLOSEFUNCTI ON: br eak ; c as e HM I N_NAM EFUNCTI ON: br eak ; c as e HM I N_M OVEFUNCTI ON:
Altair Engineering

692
br eak ; c as e HM I N_COLORFUNCTI ON: br eak ; c as e HM I N_ASSOCI ATEFUNCTI ON: br eak ; c as e HM I N_CEDATAFUNCTI ON: br eak ; c as e HM I N_M ETADATAFUNCTI ON: br eak ; c as e HM I N_CLOSEFUNCTI ON: br eak ; } r et ur n( NULL) ; } i nt HM _get M at er i al s ( ) { / * Thi s f unc t i on wr i t es eac h m at er i al */ i nt i ; //W r i t e eac h m at er i al dat a s t r uc t ur e t o Hy per M es h f or ( i =0; i <num m at er i al s ; i ++) { HM I N_m at er i al _wr i t e( m at er i al [ i ] . i d, m at er i al [ i ] . nam e) ; HM I N_wr i t eat t r i but e_i nt ( HM _ENTI TYTYPE_M ATS, m at er i al [ i ] . i d, 1, 0, 1, 1) ; HM I 0, 1, m at er i al [ HM I 0, 1, m at er i al [ HM I 0, 1, m at er i al [ HM I 0, 1, m at er i al [ HM I 0, 1, m at er i al [ HM I 0, 1, m at er i al [ HM I 0, 1, m at er i al [ HM I 0, 1, m at er i al [ HM I 0, 1, m at er i al [ HM I 0, 1, m at er i al [ } N_wr i t eat i ] . E) ; N_wr i t eat i ] . G) ; N_wr i t eat i ] . NU) ; N_wr i t eat i ] . RHO) ; N_wr i t eat i ] . A) ; N_wr i t eat i ] . TREF) ; N_wr i t eat i ] . GE) ; N_wr i t eat i ] . ST) ; N_wr i t eat i ] . SC) ; N_wr i t eat i ] . SS) ; t r i but e_doubl e( HM _ENTI TYTYPE_M ATS, m at er i al [ i ] . i d, 2, t r i but e_doubl e( HM _ENTI TYTYPE_M ATS, m at er i al [ i ] . i d, 3, t r i but e_doubl e( HM _ENTI TYTYPE_M ATS, m at er i al [ i ] . i d, 4, t r i but e_doubl e( HM _ENTI TYTYPE_M ATS, m at er i al [ i ] . i d, 5, t r i but e_doubl e( HM _ENTI TYTYPE_M ATS, m at er i al [ i ] . i d, 6, t r i but e_doubl e( HM _ENTI TYTYPE_M ATS, m at er i al [ i ] . i d, 7, t r i but e_doubl e( HM _ENTI TYTYPE_M ATS, m at er i al [ i ] . i d, 8, t r i but e_doubl e( HM _ENTI TYTYPE_M ATS, m at er i al [ i ] . i d, 9, t r i but e_doubl e( HM _ENTI TYTYPE_M ATS, m at er i al [ i ] . i d, 10, t r i but e_doubl e( HM _ENTI TYTYPE_M ATS, m at er i al [ i ] . i d, 11,
dat a s t r uc t ur e t o Hy per M es h.
r et ur n( 0) ; }
693

Altair Engineering
Altair Engineering

694
User Profiles
User profiles in HyperMesh automatically manage the loading of templates and FE-input readers for a given solver interface in the current HyperMesh session. User profiles also customize the Utility Menus and the HyperMesh panels that are available during the current HyperMesh session. HyperMesh is shipped with support for several user profiles including: RADIOSS (Bulk Data Format), OptiStruct RADIOSS (Block Format) RADIOSS (Fixed Format) Abaqus (Standard 2D/3D/Explicit) Actran Ansys LS-DYNA MADYMO Marc Nastran PAM-CRASH PAM-CRASH 2G PERMAS Samcef A user profile should be selected before opening a HyperMesh database file or importing a solver deck. Select a user profile using the user profile icon on the standard toolbar. Once a user profile is selected, it is recommended to not change it while the current HyperMesh database is populated. To safely switch user profiles, first start a new HyperMesh database using the new .hm file icon then switch the user profile. Note: on the standard toolbar,
Selecting a user profile does NOT convert a currently populated HyperMesh database to the selected solver interface. For the purpose of converting the current HyperMesh database to another solver interface use the Tools > Convert menu item on menu bar.
695

Altair Engineering
Altair Engineering

696
Include Files
Most solvers allow solver decks to be split into separate files for organizational purposes. They also provide a mechanism to include these files in a master solver deck, typically using an include statement. This capability is commonly referred to as solver include files. Solver include files can generally have any solver card defined within them, therefore the HyperMesh include file entity needs the capability to store and organize all HyperMesh entities. Every HyperMesh entity is stored and organized into a HyperMesh include file. There is a special HyperMesh include file called the master model which corresponds to the master solver deck and is automatically created for every HyperMesh model. The current HyperMesh include file is shown in the status bar and can be set by clicking on that status bar area or by using the context sensitive menu of the Model Browser. HyperMesh entities are automatically stored and organized into the current HyperMesh include file. If there are no HyperMesh include files defined then HyperMesh entities are automatically stored and organized into the master model. The Model Browser can be used to create, edit, and delete HyperMesh include files. Every HyperMesh include file has a name and a location with a full or relative path. The Model Browser can also be used to review and organize HyperMesh entities into HyperMesh include files using drag and drop functionality. The Organize panel can also be used to organize HyperMesh entities into HyperMesh include files. HyperMesh include files do not have a display, active, or export state of their own. However, the Model Browser and Entity State Browser can be used to manipulate the display, active, and export state of all HyperMesh entities organized within the HyperMesh include file as a group by using the context sensitive menu within these browsers. HyperMesh imports and exports solver decks with include file structures using three options which are selected on the import and export tabbed dialogs: preserve includes Preserves the solver include file structure by generating HyperMesh include files to match and organizes all data within the solver include files into the appropriate HyperMesh include file. The option also preserves the solver include file references in the master model. When exporting with this option all HyperMesh entities are written into their corresponding solver include files along with their references in the master solver deck. The data within the solver include files is not imported into HyperMesh. The solver include file references are maintained and are written out to the master solver deck during export. The data from the all solver include files are imported into the HyperMesh master model and the solver include file references are not maintained. When exporting, all entities are written into the master solver deck.
skip includes
merge includes
697

Altair Engineering
Abaqus Support of Include Files The following rules and considerations apply to the Abaqus include file support in HyperMesh: Include files must include complete information for each keyword. A keyword and its data lines must be part of the same file. Include files must contain complete information for cards that contain multiple sub-keywords. For example, all sub-keywords and their data lines in a *Material card must be part of the same include file. Include files must contain complete information for *Step cards. All history keywords and their data lines must be a part of the same file. The HyperMesh Abaqus interface is comprised of four types of include files: Model (start), Model (middle), Model, and History. They define the sequence of the *Include keywords in the model. Model (start) type of include files are written at the beginning of the deck, after the *Node block. Model (middle) is written in the middle of the deck, after the *Material block. Model is
Altair Engineering

698
written at the end of the model definition, and History keywords are written after the model definition. Include file names are sorted according to their names in the browser. The sequence in the exported model is primarily determined by the four types of includes files as described above. Within each type the sequence is determined by the order in which they are created. The Abaqus syntax for the include file path is: o In Abaqus, file names can include a full or relative path name. Relative path names must be in relation to the directory from which the job was started. If a path is not specified, it is assumed that the file is located in the same directory from which the job was submitted. From HyperMesh, it is, however, not always possible to predict the directory from which the job will finally be submitted. Therefore a relative path must be defined. This relative path should be defined with respect to the folder where the corresponding *Include keyword appears. If you run the job from a different folder in subsequent runs, you must also update the path name.
See also Browsers HyperMesh Entities & Solver Interfaces Collectors and Collected Entities Named Entities Morphing Entities Optimization Entities Custom Templates Custom Readers Model Setup
699

Altair Engineering
Support of Includes: Abaqus

The following rules and considerations apply to the Abaqus include file support in HyperMesh: Include files must include complete information for each keyword. A keyword and its data lines must be part of the same file. Include files must contain complete information for cards that contain multiple sub-keywords. For example, all sub-keywords and their data lines in a *Material card must be part of the same include file. Include files must contain complete information for *Step cards. All history keywords and their data lines must be a part of the same file. The HyperMesh Abaqus interface is comprised of four types of include files: Model (start), Model (middle), Model, and History. They define the sequence of the *Include keywords in the model. Model (start) type of include files are written at the beginning of the deck, after the *Node block. Model (middle) is written in the middle of the deck, after the *Material block. Model is written at the end of the model definition, and History keywords are written after the model definition. Include file names are sorted according to their names in the browser. The sequence in the exported model is primarily determined by the four types of includes files as described above. Within each type the sequence is determined by the order in which they are created. The Abaqus syntax for the include file path is: o In Abaqus, file names can include a full or relative path name. Relative path names must be in relation to the directory from which the job was started. If a path is not specified, it is assumed that the file is located in the same directory from which the job was submitted. From HyperMesh, it is, however, not always possible to predict the directory from which the job will finally be submitted. Therefore a relative path must be defined. This relative path should be defined with respect to the folder where the corresponding *Include keyword appears. If you run the job from a different folder in subsequent runs, you must also update the path name.
Altair Engineering

700
Support of Includes: LS-Dyna

LSDYNA keywords *INCLUDE, *INCLUDE_TRANSFORM, *INCLUDE_COMPENSATION_OPTION are mapped to include files in HyperMesh. The user can switch to different type of include with the the exception of *INCLUDE_TRANSFORM using the the context sensitive menu Include File options in the include browser. INCLUDE_TRANSFORM is manged using the Transfromation manager in HM. During import if same include file is referred more than once using the *INCLUDE_TRANSFORM then they are imported but appended with .# where # = 1n and shown in the include browser. These will not be exported unless the user changes the Instance option check box off.
701

Altair Engineering
Nodes
Nodes are the most basic finite element entity. A node represents a physical position on the structure being modeled and is used by an element entity to define the location and shape of that element. It is also used as temporary input to create geometry entities. A node may contain a pointer to other geometric entities and can be associated directly to them. Nodes are considered to be used if they are referenced in the definition of an element, system, vector, group, load, equation, or are referenced by any card image on any HyperMesh entity. HyperMesh automatically deletes unused nodes and any loads that are attached to unused nodes. Nodes can not be organized into components. Nodes can be organized into HyperMesh include files, which defines the solver include file they will be exported to. Use the Organize panel to organize nodes into include files. The Organize panel can be accessed using the Organize icon on the collectors toolbar.
The following panels can be used to create and edit nodes: Nodes Node Edit Temp Nodes
The data names associated with nodes can be found in the data names section of the HyperMesh Reference Guide.
Solver Card Support for Nodes
The supported RADIOSS D00 cards in RADIOSS (Block Format) 5.1 and 9.0 are listed below. You can quickly create these cards by right-clicking in the Solver Browser and selecting Create Cards. Supported Cards Solver Description Supported Parameters Notes
/NODE
RADIOSS (Bulk Data Format), OptiStruct
Altair Engineering

702
HyperMesh Nodes are used to represent GRID and SPOINT bulk data entries. Supported Cards Solver Description Supported Parameters Notes
GRID
Defines the location of a geometric grid point of the structural model, the directions of its displacement, and its permanent single-point constraints. Defines a scalar point.
Exported in large field format by optistructlf template.
SPOINT
Ideally a scalar point has no location, but in HyperMesh it is represented as a node.
RADIOSS (Fixed Format)
Node cards are fully input into HyperMesh. Nodal coordinates are defined with X, Y, and Z coordinates. Skew frames for nodal time history is supported for RADIOSS (Fixed Format) version 4.1.
Abaqus
Supported Cards
Solver Description
Supported Parameters NSET and SYSTEM
Notes
*NODE
Specify nodal coordinates
The SYSTEM parameter is created automatically during export based upon the type of reference coordinate system that is assigned to the nodes. The card image for a node is displayed in global Cartesian coordinates in HyperMesh.
703

Altair Engineering
Actran
Supported Cards
Solver Description
Supported Parameters
Notes
NODE
ANSYS
Supported Cards
Solver Description
Supported Parameters NODE, X, Y, Z, THXY, THYZ, THZX R5.1, Type, NODE, SOLID, VAL1, VAL2, VAL3 R5.3, LOC, NODE, SOLID, NODLOC, VAL1, VAL2, VAL3 ID, SOLIDFLG, LINELOC, X, Y, Z
Notes
Defines a node
Defines a node
Defines a node
NBLOCK
Nodal block
LS-DYNA
Supported Cards
Solver Description
Notes
*NODE
Define a node and it's coordinates in the global coordinate system.
Card can be previewed, but not edited Card can be previewed, but not edited
*NODE_RIGID_SURF Define a rigid node and it's ACE coordinates in the global coordinate system.
MADYMO
Altair Engineering

704
Supported Cards
Solver Description
Supported Parameters X, Y, Z coordinates
Notes
COORDINATE. CARTESIAN
Nodal coordinate definition in a Cartesian coordinate system
If the node is created through type in, the entered values for x, y and z coincide with the X, Y, and Z coordinates of the COORDINATE. CARTESIAN, while system and as node are not used. NAME can be entered on the card image.
POINT_OBJECT
Point on a body or on the reference space, or a finite element node.
REF_SPACE if the POINT_OBJECT is on the reference space RIGID_BODY if the POINT_OBJECT is on a rigid body FLEX_BODY if the POINT_OBJECT is on a flexible body FE_NODE if the POINT_OBJECT is a finite element node
POINT_OBJECT_FE
Point on a body or on the reference space, or a finite element node. Defines a point associated with, and located relative to, a body or the reference space. Defined through the parent element.
POINT_OBJECT_1_F E
POINT_OBJECT_1_M Defines a point associated with, B and located relative to, a body or the reference space. POINT_OBJECT_2_F E Defines a second point associated with, and located relative to, a body or the reference space.
POINT_OBJECT_2_M Defines a second point B associated with, and located
705

Altair Engineering
Supported Cards
Solver Description
Notes
relative to, a body or the reference space.
Nastran
Supported Cards
Solver Description
Supported Parameters PS SPOINT CD-1 GRID_COMMENT
Notes
GRID
Defines the location of a geometric grid point, the directions of its displacement, and its permanent single-point constraints.
Permanent single point constraint field supported for feinput only. On export, equivalent SPC cards are output. SPOINT is supported the same way GRID is supported. On import or export, all the nodes that are designated to be SPOINT will be converted to nodes at the origin.
SPOINT
Defines scalar points.
n/a
PAM-CRASH 2G
Supported Cards
Solver Description
Notes
CNODE /
Common node definition
In the card previewer, the toggle button Common_Node allows you to change between NODE and CNODE.
NODE /
Node definition
Altair Engineering

706
Supported Cards
Solver Description
Notes
Note:
Use the find_cnodes summary template to highlight all CNODE nodes as temporary nodes.
PERMAS
Supported Cards
Solver Description
Notes
$COOR
Definition of nodal points and their coordinates
Samcef
The following cards are supported in the HyperMesh Samcef interface: Supported Cards Solver Description Supported Parameters NODEID, X, Y, Z Notes
.NOE
Allows the entry of the coordinates of the nodes of the structure.
See also Browsers HyperMesh Entities & Solver Interfaces Geometry Meshing Model Setup
707

Altair Engineering
Collectors and Collected Entities

Collectors are named organizational containers for collected entities. An example of a collector is the component collector which collects points, lines, surface, solids, elements, and connectors for model organization purposes. Collectors also control the display state, on or off, of all their collected entities as a group. The display state of collectors can be controlled using the Model Browser. Collected entities are nameless entities which must reside within one, and only one, collector. Therefore, collected entities are mutually exclusive to a collector. Examples of collected entities include points, lines, surfaces, solids, elements, and connectors, which are collected by a component collector.
HyperMesh Collectors and Collected Entities Include Files Assemblies Nodes Components Points Lines Surfaces Solids Elements Connectors Load Collectors Loads Equations System Collectors Systems Vector Collectors Vectors Beamsection Collectors Beamsections Multibodies Ellipsoids Multibody Planes Multibody Joints Bags Generic Optimization Problem FBD Forces (All Loads) FBD Forces (Applied Loads)
Altair Engineering

708
FBD Forces (Reaction Loads) FBD Displacements Resultant Force & Moment FBD Cross-section ADM Part ADM Material
The Current Collector Since a collected entity must belong to one, and only one, collector, there must be a current collector for which newly created collected entities will automatically be organized into. The status bar shows the current collector for include files, components, and load collectors respectively. The current collector is also shown bold in the Model Browser. In addition, the Model Browser context sensitive menu allows for setting the current collector via the Make Current selection.
709

Altair Engineering
Organizing Collected Entities into Collectors Collected entities can be organized into collectors at any point using the Organize panel. The Organize panel can be accessed using the organize icon on the collectors toolbar.
Altair Engineering

710
See also Browsers HyperMesh Entities & Solver Interfaces Model Setup
711

Altair Engineering
Assemblies
Assemblies collect and organize sub-assemblies and components into hierarchal data structures which are intended to reflect the data structure of the product being modeled. Furthermore, components are intended to be organizational containers for the geometry and FE idealization of physical parts which make up the product. Assemblies are created, edited, and deleted from the Model Browser and are shown under the Assembly Hierarchy folder. The Assembly Hierarchy folder shows a list of assemblies which can be expanded to show the components organized within those assemblies. The Assembly Hierarchy folder also shows a list of components which are currently not organized into any assembly at the bottom of the Assembly Hierarchy folder. Components can be organized into an assembly using drag and drop technology within the Model Browser. Components can be organized into more than one assembly. Therefore, components are not mutually exclusive to an assembly. To organize a component into more than one assembly drag and drop with the control key depressed. In general it is not recommended to organize components into multiple assemblies if it can be avoided. Assemblies have a display state, on or off, which control the display state of all components organized within the assembly in the graphics area. The display state of an assembly can be controlled using the icons next to the assembly in the Model Browser. Geometry and element display states can be controlled separately for assemblies. See components for the display state rules of components. Assemblies also have an active and export state. The active state of an assembly controls the display state of the assembly and the listing of the assembly and its components in the Model Browser and any of its views. If an assembly is active, then its display state is available to be turned on or off and the assembly and its components are listed in the Model Browser and any of its views. If an assembly is inactive, then its display state is turned off permanently (and hence also its components) and the assembly and its components are not listed in the Model Browser or any of its views. If a find operation "finds" an inactive assembly, that assembly will automatically be set to active. The export state of an assembly controls whether or not that assembly, including all components organized within the assembly, are exported when the custom export option is utilized. The all export option is not affected by the export state of an assembly. The active and export states of assemblies can be controlled using the Entity State Browser. See components for the active and export state rules for components. Operations performed on an assembly do not affect the components collected within the assembly. For example, if you delete an assembly, the components in the assembly are not deleted, but are instead returned to the list of components which are currently not organized into any assembly. The data names associated with assemblies can be found in the data names section of the HyperMesh Reference Guide.
Altair Engineering

712
Solver Card Support for Assemblies

Supported Cards
Solver Description
Supported Parameters n/a
HyperMesh Notes
/SUBSET
Describes the subsets.
MADYMO
Because MADYMO uses a hierarchical data structure, it is crucial to set up the correct hierarchy in HyperMesh using the Assembly panel. The MADYMO hierarchy requires: one root assembly of the type MADYMO one assembly of the type SYSTEM, subtype REF_SPACE assemblies of the type FE_MODEL must be placed in an assembly of the type SYSTEM collectors of the type PART must be placed in an assembly of the type FE_MODEL multibodies must be placed in an assembly of the type SYSTEM
713

Altair Engineering
For newly-created elements, the parent in the hierarchy is derived from the related elements or attributes, or set manually on the card image. For imported elements, the parent is usually set according to the value found in the imported file. Supported Cards Solver Description Supported Parameters HyperMesh Notes
CHAR_MOD
Scaling and shifting parameter of a characteristic on a global level.
CHAR, Defined on the card DAMP_COEF_SCALE, of the parent element HYS_SLOPE_SCALE, ELAS_LIMIT_SCALE, DAMP_COEF_SHIFT, HYS_SLOPE_SHIFT, ELAS_LIMIT_SHIFT THERMC, BLOCK_FLOW, AMBIENT_PRES, AMBIENT_TEMP, AMBIENT_DAMP_CO EF Defined on the card of the parent FE_MODEL.
CONTROL_AIRBAG
Parameters to control airbag model behaviour.
CONTROL_ALLOCAT This element allows the NR_PROC, l_SIZE, ION memory size allocated to R_SIZE, C_SIZE MADYMO, given in integers, real numbers and characters, to be set. The number of processors to be used in the solution can also be specified. CONTROL_ANALYSI S Control element for inputting time domain analysis data relevant to the multi-body solver. Used to set analysis duration, size of time step, tolerances and ramp functions.
Defined on the MADYMO card.
TIME_START, Defined on the TIME_END, MADYMO card. TIME_STEP, ANALYSIS_TYPE, INT_MTH, RAMP1 & 2, RACO1 & 2, CONSTRAINT_TOL, CONTACT_TOL, CONTACT_MAX_ITER, USE_FE_TIME_STEP ALPHA_COEF, MASS_LUMP_MTH, ALPHA_FUNC, ALPHA_REL_BODY Defined on the card of the parent FE_MODEL.
CONTROL_FE_MOD EL
Defines Rayleigh damping and mass lumping method for the parent FE model.
CONTROL_FE_TIME _STEP
This element allows the user to specify the range of acceptable
REDUCTION_FACTOR Defined on the card , of the parent
Altair Engineering

714
Supported Cards
Solver Description
HyperMesh Notes
values for the FE model time step, and parameters used by the program to automate time step size.
CRITICAL_ELEMENTS FE_MODEL. , MIN_STEP, MAX_STEP, TIME_INT_MTH, NR_OF_CYCLES BASED_ON, TIME_WINDOW, ELAPSED_TIME, MAX_STRETCH_PRIN T CHECK_REF_MESH, EPS_REF_MESH, DYNAMIC_RELAX Defined on the card of the parent FE_MODEL.
CONTROL_IMM
Parameters to control the IMM method
CONTROL_OUTPUT
Specifies which output data are to be written and the frequency with which this is done. Also defines how often restart output is written.
FILTER_IGNORE, Defined on the PADDING_TIME, MADYMO card. SCALE_FACTOR_ANI, TIME_START_OUTPU T, TIME_STEP, TIME_STEP_ANI, TIME_STEP_RESTAR T, WRITE_DEBUG, WRITE_FEMESH, MAX_FILE_SIZE CONTROL_FE_MODE L CONTROL_FE_TIME_ STEP CONTROL_AIRBAG CONTROL_IMM FUNC_MOD CHAR_MOD INITIAL_PART SCALING type = FE_MODEL comps = references to related PARTs and CONSTRAINT. RIGID_FEs Assemblies and multibodies should be left empty.
FE_MODEL
Finite element model
FUNC_MOD
Scaling and shifting of functions FUNC, X_SCALE, on a global level. Y_SCALE, X_SHIFT, Y_SHIFT MADYMO XML Root element card image =
Defined on the card of the parent element. Multibodies should
MADYMO
715

Altair Engineering
Supported Cards
Solver Description
Supported Parameters MADYMO comps = references to related BELTs and CONTROL_SYSTEMs assems = references to the SYSTEM. REF_SPACE and any SYSTEM.MODELs
HyperMesh Notes
be left empty.
RUNID
Allows a short text description n/a of the analysis to be entered, and contains MADYMO product information. Scaling of coordinates. SCALE_TYPE, NODE_LIST, REF_NODE, X_SCALE, Y_SCALE, Z_SCALE card image = SYSTEM
Defined on the MADYMO card.
SCALING
Defined on the card of the parent FE_MODEL.
SYSTEM.MODEL
Parent element for model definition data
Select MODEL.
Select the INITIAL. comps = references to FE_MODEL check related BELTs box and specify the number of related assems = references INITIAL.FE_MODEL to related FE_MODELs elements to add. multibodies = references to related BODYs
SYSTEM. REF_SPACE
Parent element for reference space definition data
card image = SYSTEM
assems = references to related FE_MODELs Select REF_SPACE. Select the INITIAL. FE_MODEL check box and specify the number of related INITIAL.FE_MODEL elements to add.
Comps and multibodies should be left empty.
Altair Engineering

716
MARC
Supported Cards
Solver Description
HyperMesh Notes
ASSEMBLIES PAM-CRASH 2G
Supported Cards
Solver Description
Supported Parameters TITLE H_POINT
HyperMesh Notes
MBSYS /
Describes an assembly of multibodies
See also Browsers HyperMesh Entities & Solver Interfaces Include Files Components
717

Altair Engineering
Components
Components collect and organize points, lines, surfaces, solids, elements and connectors. Components are intended to be organizational containers for the geometry and FE idealization of a physical part which makes up a product. Components are created, edited, and deleted from the Model Browser and are shown under the Component folder. Components also have a component view within the Model Browser which lists only components and has advanced options for component creation and editing. Points, lines, surfaces, solids, elements, and connectors can be organized into a component using the Organize panel. Every point, line, surface, solid, element, and connector must be organized into one, and only one, component and therefore are mutually exclusive to a component. Newly created points, lines, surfaces, solids, elements, and connectors are automatically organized into the current component. The current component is shown in the status bar and is also bold in the Model Browser. The current component can be set using the Model Browser context sensitive menu on a selected component within the Component folder. Components can also be card edited using the Model Browser context sensitive menu on selected components. Components have a display state, on or off, which control the display of all points, lines, surfaces, solids, elements, and connectors organized within the component in the graphics area. The display state of a component can be controlled using the icons next to the component in the Model Browser. Geometry and element display states can be controlled separately for components. Components also have an active and export state. The active state of a component controls the display state of the component and the listing of the component in the Model Browser and any of its views. If a component is active, then its display state is available to be turned on or off and it is listed in the Model Browser and any of its views. If a component is inactive, then its display state is turned off permanently and it is not listed in the Model Browser or any of its views. If a find operation "finds" an inactive component, that component will automatically be set to active. The export state of a component controls whether or not that component and all points, lines, surfaces, solids, elements, and connectors organized within the component are exported when the custom export option is utilized. The all export option is not affected by the export state of a component. The active and export states of components can be controlled using the Entity State Browser. Components can also be assigned properties and materials. Component property and material assignments are user profile (solver interface) dependent, and are described in the section Element Property and Material Assignment Rules. In general, when a component is assigned a property or material, that property or material assignment is applied to all elements organized within that component. The method of assigning properties and materials at the component level is therefore referred to as indirect property and material assignment. Direct property and material assignment is performed directly on the elements themselves. Direct property and material assignments always take precedence over indirect property and material assignments. Operations performed on a component affect all points, lines, surfaces, solids, elements, and connectors within the component. For example, if you delete a component, the points, lines, surfaces, solids, elements, and connectors within the component are also deleted. The data names associated with components can be found in the data names section of the HyperMesh Reference Guide.
Altair Engineering

718
Solver Card Support for Components

719

Altair Engineering
The supported RADIOSS cards in RADIOSS (Block Format) up to 110 are listed below. You can quickly create these cards by right-clicking in the Solver Browser and selecting Create Cards. Supported Cards Solver Description Supported Parameters Prop_ID, Mat_ID, Subset_ID, Thick Notes
/PART
Defines a part.
Actran
You can define the following Actran components: Supported Cards Solver Description Supported Parameters Notes
COUPLING_SURFAC Used for BC_MESH and Name, ID E INTERFACE purposes to handle incompatible meshes. DISCRETE Corresponds to springs and lumped mass elements. Name, ID
FIELD_POINT_SURF ACE FINITE_FLUID Corresponds to the finite elements used to model acoustic media.
Name, ID
Name, ID, POWER EVALUATION
INCIDENT_SURFACE A set of finite element faces supporting the evaluation of the incident acoustic power. INFINITE_DOMAIN Collection of infinite elements that discretize an unbounded acoustic domain. Corresponds to the infinite elements used to model acoustic free field. The INFINITE MESH data block is made of two subsections INFINITE_DOMAIN and
Name, ID
INFINITE_FLUID
Order ORIGIN, VECTOR
INFINITE_MESH
Altair Engineering

720
Supported Cards
Solver Description
Notes
INFINITE_ELEMENT MODAL_BASIS Defines the modal content of the sound field in a modal component MATERIAL, Coord Syst, Shape, MODE, DIRECTION, PROPERTY, Flow
MODAL_SURFACE
Defines the coupling surface between modal components and the acoustic finite element model Corresponds to finite elements used to model poro-elastic media. Name, ID, POWER EVALUATION
POROUS_UP
RADIATING_SURFAC A set of finite element faces on E which the acoustic power is calculated. RAYLEIGH_SURFAC A set of boundary elements E used to model a semi-infinite acoustic fluid interfaced with a plane or nearly plane baffled structure. RIGID_POROUS Corresponds to finite elements used to model rigid porous media. Corresponds to finite elements used to model shell viscoelastic media. Corresponds to finite elements used to model solid viscoelastic materials.
Name, ID
Name, ID
Name, ID, POWER EVALUATION
SHELL
Name, ID, POWER EVALUATION, AUTO ORIENT Name, ID, POWER EVALUATION
SOLID
STIFFENER
Corresponds to finite elements Name, ID used to model Actran equivalent stiffeners.
SUPER_CONNECTO Used to couple an Actran model COUPLING R to a Nastran super-element. SURFACE:
721

Altair Engineering
Supported Cards
Solver Description
Supported Parameters SURFACE, GAP_TOL, PLANE_TOL TRANSLATION STIFFNESS: Normal, Tang1, Tang2 ROTATIONAL STIFFNESS: Normal, Tang1, Tang2
Notes
VISCOTHERMAL_FL UID
Corresponds to finite elements Name, ID, POWER used to model viscothermal fluid EVALUATION, AUTO media. ORIENT
ANSYS
Supported Cards
Solver Description
Supported Parameters TYPE, MAT, REAL
Notes
*HM_COMP
ET card, R card, MAT, and SECDATA card
LS-DYNA
Supported Cards
Solver Description
Supported Parameters LCID, SF, FLAG Options (None, Inertia, Reposition, Interia_Contact, Reposition_Contact, Contact) BETA Options (None, Inertia,
Notes
*DAMPING_PART_M ASS
Define mass weighted damping by part ID
*DAMPING_PART_ STIFFNESS
Assign Rayleigh stiffness damping coefficient by part ID
Altair Engineering

722
Supported Cards
Solver Description
Supported Parameters Reposition, Interia_Contact, Reposition_Contact, Contact)
Notes
*INCLUDE_STAMPE D_ PART
Allows the plastic strain and thickness distribution of the stamping simulation to be mapped onto a part in the crash model.
FILENAME, THICK, PSTRN, STRAIN, INCOUT, RMAX, N1S, N2S, N3S, N2C, N3C, TENSOR Options (None, Inertia, Reposition, Interia_Contact, Reposition_Contact, Contact)
*PART
Define parts for part adaptivity.
comment EOSID, HGID, GRAV, ADPOPT, TMID Options (None, Inertia, Reposition, Interia_Contact, Reposition_Contact, Contact) PrintOption RigidBodyMerge DampingMass DampingStiffness IncludeStampPart PartMove
*PART_COMPOSITE
Provides a simplified method of defining a composite material model for shell elements that eliminates the need for user defined integration rules and part IDs for each composite layer. Allows part based contact parameters to be use with the automatic contact types a3, 4,
HEADING, ELFORM, SHRF, NLOC, MAREA, HGID, ADPOPT, MID, THICK, B ContactOption Number_of_Plies HEADING, ELFORM, SHRF, NLOC, MAREA, HGID,
*PART_COMPOSITE _ CONTACT
723

Altair Engineering
Supported Cards
Solver Description
Supported Parameters ADPOPT, FS, FD, DC, VC, OPTT, SFT, SSF Number_of_Plies
Notes
a5, a10, 13, 15 and 26.
*PART_CONTACT
Allows part-based contact parameters to be used with the automatic contact types a3, a5, a10, a13, 15 and 26
comment, EOSID, HGID, GRAV, ADPOPT, TMID, SCFC, DCFC, EDC, VCFC, OPTT, SFT, SSF ConRigidBodiesHelp
*PART_CONTACT_P RINT
comment, EOSID, HGID, GRAV, ADPOPT, TMID, SCFC, DCFC, EDC, VCFC, OPTT, SFT, SSF, PRBF ConRigidBodiesHelp
*PART_INERTIA
Allows the inertial properties and initial conditions to be defined rather than calculated from the finite element mesh.
comment, EOSID, HGID, GRAV, ADPOPT, TMID, XC, YC, ZC, TM, IRCS, NODEID, IXX, IXY, IXZ, IYY, IYZ, IZZ, VTX, VTY, VTZ, VRX, VRY, VRZ comment, EOSID, HGID, GRAV, ADPOPT, TMID, XC, YC, ZC, TM, IRCS, NODEID, IXX, IXY, IXZ, IYY, IYZ, IZZ, VTX, VTY, VTZ, VRX, VRY, VRZ, PRBF comment, EOSID, HGID, GRAV, ADPOPT, TMID, XC, YC, ZC, TM, IRCS, NODEID, IXX, IXY, IXZ, IYY, IYZ, IZZ, VTX, VTY, VTZ, VRX, VRY,
*PART_INERTIA_CO NTACT
*PART_INERTIA_CO NTACT _PRINT
Altair Engineering

724
Supported Cards
Solver Description
Supported Parameters VRZ, SCFC, DCFC, EDC, VCFC, OPTT, SFT, SSF, PRBF
Notes
*PART_INERTIA_PRI NT
comment, EOSID, HGID, GRAV, ADPOPT, TMID, XC, YC, ZC, TM, IRCS, NODEID, IXX, IXY, IXZ, IYY, IYZ, IZZ, VTX, VTY, VTZ, VRY, VRZ, PRBF Translate a part by an incremental displacement in either a local or a global coordinate system. XMOV, YMOV, ZMOV, CID Options (None, Inertia, Reposition, Interia_Contact, Reposition_Contact, Contact)
*PART_MOVE
*PART_PRINT
Allows user control over whether comment output data is written into the EOSID, HGID, GRAV, ASCII files MATSUM and ADPOPT, TMID, PRBF RBDOUT. Options (None, Inertia, Reposition, Interia_Contact, Reposition_Contact, Contact) comment EOSID, HGID, GRAV, ADPOPT, TMID, CMSN, MDEP, MOVOPT
*PART_REPOSITION Applies to deformable materials and is used to reposition deformable materials attached to rigid dummy components whose motion is controlled by either CAL3D or MADYMO. *PART_REPOSITION _ CONTACT
comment EOSID, HGID, GRAV, ADPOPT, TMID, CMSN, MDEP, MOVOPT, SCFC, DCFC, EDC, VCFC, OPTT, SFT, SSF
725

Altair Engineering
Supported Cards
Solver Description
Supported Parameters comment EOSID, HGID, GRAV, ADPOPT, TMID, CMSN, MDEP, MOVOPT, SCFC, DCFC, EDC, VCFC, OPTT, SFT, SSF, PRBF comment EOSID, HGID, GRAV, ADPOPT, TMID, CMSN, MDEP, MOVOPT, PRBF
Notes
*PART_REPOSITION _ CONTACT_PRINT
*PART_REPOSITION _ PRINT
MADYMO
Supported Cards
Solver Description
Supported Parameters POINT_OBJECT_1. REF
Notes
BELT
This is the root element for defining belt models. Fuse belts can model the tearing of seat belt stitches, which is used as a load limiting device. Retractor with webbing grabber.
BELT_FUSE
Defined on the card of parent BELT_SEGMENT
BELT_RETRACTOR
Reference to parent BELT. Reference to parent BELT.
BELT_SEGMENT
A belt segment is a section of a belt, defined as a straight line between two points. Where these points are attached to a body, e.g. a dummy model, the belt will slide only along the direction of the belt segment.
Altair Engineering

726
Supported Cards
Solver Description
Notes
BELT_TYING
Belt segments are joined together using the BELT_TYING elements to specify the segment ends to be joined and the slip friction at the junction. Rigid elements and rigid parts that form one rigid FE entity.
Reference to parent BELT.
CONSTRAINT. RIGID_FE
CONTACT_EVALUAT Scale the contact force related CONTACT_LIST E to a list of selected contacts of ellipsoids with planes, cylinders NR_OF_CONTACTS and ellipsoids.
Type the number of CONTACTs in the CONTACT_LIST and select the desired CONTACT.MB_MBs .
CONTROL_SYSTEM
Control module for multi-body systems. All finite elements of the same formulation, properties and material are assigned to a part. This XML element indicates which property and material parameters are to be applied to a given part.
ID, NAME
PART
ID, NAME, PROPERTY, MATERIAL
PAM-CRASH 2G
Supported Cards
Solver Description
Supported Parameters SOLID, BSHEL, TETRA TSHEL, SHELL, MEMBR
Notes
PART /
Part_3D
PART /
Part_2D
727

Altair Engineering
Supported Cards
Solver Description
Supported Parameters BAR, BEAM, SPRING, JOINT, KJOIN, MBSPR, MBKJN, SPRGBM TIED, SLINK, ELINK, PLINK, LLINK
Notes
PART /
Part_1D
PART /
PART_LINK
PERMAS
Supported Cards
Solver Description
Notes
$ELPROP
Assignment of geometrical data Mass/Springs and material to elements
See also Browsers HyperMesh Entities & Solver Interfaces Include Files Assemblies
Altair Engineering

728
Points
A point is a zero-dimensional geometry entity. There are two different types of points in HyperMesh; Free Points and Fixed Points. A free point is a zero-dimensional geometry entity in space that is not associated with a surface. It is displayed as a small "x". These types of points are typically used for weld locations and connectors. A fixed point is a zero-dimensional geometry entity that is associated with a surface. It is displayed as a small "o". The automesher places a node at each fixed point on the surface being meshed. A fixed point that is placed at the junction of three or more non-suppressed edges is called a vertex or vertex point. Such vertices cannot be suppressed (removed). The following panels can be used to create and edit points: Quick Edit Point Edit
The data names associated with points can be found in the data names section of the HyperMesh Reference Guide.
See also Geometry Terminology CAD Interfacing Geometry Functionality Include Files Assemblies Components
729

Altair Engineering
Lines
A line represents a curve in space and is not attached to any surface or solid. A line is a one-dimensional geometric entity. A line can be composed of one or more line types. Each line type in a line is referred to as a segment. The end point of each line segment is connected to the first point of the next segment. A joint is the common point between two line segments. Line segments are maintained as a single line entity, so operations performed on the line affect each segment of the line. In general, HyperMesh automatically uses the appropriate number and type of line segments to represent the geometry. Lines are different from surface edges and are sometimes handled differently for certain HyperMesh operations. The following panels can be used to create and edit lines: Lines Line Edit
The data names associated with lines can be found in the data names section of the HyperMesh Reference Guide.
Altair Engineering

730
Surfaces
A surface represents the geometry associated with a physical part. A surface is a two-dimensional geometric entity that may be used in automatic mesh generation. A surface is comprised of one or more faces. Each face contains a mathematical surface and edges to trim the surface, if required. When a surface has several faces, HyperMesh maintains all of the faces as a single surface entity. Operations performed on the surface affect all the faces that comprise the surface. In general, HyperMesh automatically uses the appropriate number of and type of surface faces to represent the geometry. Surface edges are different from lines and are sometimes handled differently for certain HyperMesh operations. The connectivity of surface edges constitutes the geometric topology. The following panels can be used to create and edit surfaces: Surfaces Surface Edit Defeature Midsurface Quick Edit Edge Edit Autocleanup
The data names associated with surfaces can be found in the data names section of the HyperMesh Reference Guide.
731

Altair Engineering
Solids
Solids are closed volume of surfaces that can take any shape. Solids are three-dimensional entities that can be used in automatic tetra and solid meshing. The surfaces defining a solid can belong to multiple component collectors. The display of a solid and its bounding surfaces are controlled only by the component collector to which the solid belongs. The following panels can be used to create and edit solids: Solids Solid Edit Primitives
The data names associated with solids can be found in the data names section of the HyperMesh Reference Guide.
Altair Engineering

732
Elements
Elements are FE idealizations for a portion of a physical part. Each element in HyperMesh has an associated element configuration. An element configuration tells HyperMesh how to draw, store, and work with the element. HyperMesh supports the following element configurations.
0D Element Types Mass Rigid Element Types RBE3 Rigid Rigidlink 1D Element Types Bar2 Bar3 Gap Joint Plot Rod Spring Weld 2D Element Types Quad4 Quad8 Tria3 Tria6 3D Element Types Hex8 Hex20 Penta6 Penta15 Pyramid5
733

Altair Engineering
Pyramid13 Tetra4 Tetra10 Interface Element Types Master3 Master4 Slave1 Slave3 Slave4
Solver Card Support for Elements

The supported RADIOSS cards in RADIOSS 100 are listed below. You can quickly create these cards by right-clicking in the Solver Browser and selecting Create Cards.
Supported Cards
Solver Description
Supported Elem Types Mass Bar Hex20 Hex8, Penta6, Pyramid5, Tetra4
Notes
/ADMAS /BEAM /BRIC20 /BRICK
Describes the added masses. Describes the beam elements. Describes 3D solid elements. Defines a Hexahedral Solid Element and Thick Shell Element with 8 nodes. Describes the cylindrical joints. Describes the 2D solid elements.
/CYL_JOINT /QUAD
Rigid Quad4
/RBE2
Ties degree of freedom of Rigid multiple nodes to one node with option to choose the degree freedom that need to be tied.
Altair Engineering

734
Supported Cards
Solver Description
Supported Elem Types RBE3
Notes
/RBE3
Ties degree of freedom of one node to multiple nodes. Describes the rigid bodies. Describes the rivet or spotweld. Describes the rigid links. Describes the 4 node shell elements. Describes the 3 node shell elements Describes the SPH cells. Describes the spring elements. Describes the 4-noded tetra elements Describes the 10-noded tetra elements Describes the truss elements.
/RBODY /RIVET /RLINK /SHELL
Rigid Weld Rigid Quad4
/SH3N
Tria3
/SPHCEL /SPRING /TETRA4
Mass Spring Tetra4
/TETRA10
Tetra10
/TRUSS
Rod
Most RADIOSS (Bulk Data Format), OptiStruct structural elements used in finite element analysis solution sequences are supported as elements in the interface.
Supported Cards
Solver Description
Supported Elem Types Tria3 Quad4
Notes
BMFACE
Defines quad or tria faces that are in turn used to define a barrier to limit the total deformation for free-shape design regions.
735

Altair Engineering
Supported Cards
Solver Description
Supported Elem Types
Notes
CAABSF
Defines a frequency-dependent Mass acoustic absorber element in coupled fluid-structural analysis. Rod Tria3 Quad4
CBAR
Defines a simple beam element.
Bar2
CBEAM
Defines a beam element Bar2 (BEAM) of the structural model. Defines a generalized springdamper structural element. Defines a one-dimensional spring-damper structural element. Defines a scalar damper element. Spring
CBUSH
CBUSH1D
Mass Spring Spring Mass Represented as a spring element type or as a mass element type (grounded CDAMP1). Represented as a spring element type or as a mass element type (grounded CDAMP2). Represented as a spring element type or as a mass element type (when a coordinate is constrained). Represented as a spring element type or as a mass element type (when a coordinate is constrained).
CDAMP1
CDAMP2
Defines a scalar damper element, without reference to a property.
Spring Mass
CDAMP3
Defines a scalar damper element that is connected only to scalar points.
Spring Mass
CDAMP4
Defines a scalar damper element that is connected only to scalar points and is without reference to a material or property entry.
Spring Mass
Altair Engineering

736
Supported Cards
Solver Description
Supported Elem Types Spring Mass
Notes
CELAS1
Defines a scalar spring element of the structural model.
Represented as a spring element type or as a mass element type (grounded CELAS1). Represented as a spring element type or as a mass element type (grounded CELAS2). Exported in large field format by optistructlf template.
CELAS2
Defines a scalar spring element of the structural model without reference to a property entry.
Spring Mass
CELAS3
Defines a scalar spring element that connects only to scalar points.
Spring Mass
Represented as a spring element type or as a mass element type (when a coordinate is constrained). Represented as a spring element type or as a mass element type (when a coordinate is constrained). The type of gap elements (either CGAP or CGAPG) is automatically determined based on whether the element is node-to-node or node-to-elem. The type of gap elements (either CGAP or CGAPG) is automatically determined based on whether the element
CELAS4
Defines a scalar spring element Spring that is connected only to scalar Mass points without reference to a property entry.
CGAP
Defines a gap or friction element.
Gap
CGAPG
Defines a node-to-obstacle gap element. The obstacle may be an element face or a patch of nodes.
Gap Mass
737

Altair Engineering
Supported Cards
Solver Description
Notes
is node-to-node or node-to-elem. CHACAB Defines the acoustic absorber element in coupled fluidstructural analysis Defines a surface element for application of thermal boundary condition. Defines a first order solid element, composed of 6 quadrilateral faces. Defines a second order solid element, composed of 6 quadrilateral faces. Hex8
CHBDYE
Slave1
Defined using the Interfaces panel with the CONDUCTION or CONVECTION type.
CHEXA (8-noded)
Hex8
CHEXA (20-noded)
Hex20
A second order element with missing mid-side nodes can be defined in RADIOSS (Bulk Data). Input data decks containing such elements are read by the translator as a first-order element. A message is written to the OptiStruct.msg file indicating the corresponding element ID. Represented as a spring element type or as a mass element type (grounded CMASS1). Represented as a spring element type or as a mass element type (grounded CMASS2). Represented as a
CMASS1
Defines a scalar mass element. Spring Mass
CMASS2
Defines a scalar mass element without reference to a property entry.
Spring Mass
CMASS3
Defines a scalar mass element
Spring
Altair Engineering

738
Supported Cards
Solver Description
Notes
that is connected only to scalar Mass points.
spring element type or as a mass element type (when a coordinate is constrained). Represented as a spring element type or as a mass element type (when a coordinate is constrained).
CMASS4
Defines a scalar mass element Spring that is connected only to scalar points and is without reference Mass to a property.
CMBEAM
Defines a beam element for Bar2 multi-body dynamics solution sequence without reference to a property entry. Defines a spring damper element without reference to a property entry for multi-body solution sequence. Defines a 6x6 mass matrix at a geometric grid point. Spring
CMSPDP
CONM1
Mass
CONM2
Defines a concentrated mass at Mass a grid point of the structural model.
CONROD
Defines a rod element without reference to a property entry. Specifies a free convection boundary condition for heat transfer analysis.
Rod
CONV
Slave1
Represented as a continuation to CHBDYE slave element card.
CPENTA (6-noded)
Defines a first order solid element, composed of 3 quadrilateral and 2 triangular faces. Defines a second order solid
Penta6
CPENTA (15-noded)
Penta15
A second order
739

Altair Engineering
Supported Cards
Solver Description
Notes
element, composed of 3 quadrilateral and 2 triangular faces.
element with missing mid-side nodes can be defined in RADIOSS (Bulk Data). Input data decks containing such elements are read by the translator as a first-order element. A message is written to the OptiStruct.msg file indicating the corresponding element ID. Pyramid5
CPYRA (5-noded)
Defines a first order solid element, composed of 1 quadrilateral and 4 triangular faces. Defines a second order solid element, composed of 1 quadrilateral and 4 triangular faces.
CPYRA (13-noded)
Pyramid13
A second order element with missing mid-side nodes can be defined in RADIOSS (Bulk Data Format). Input data decks containing such elements are read by the translator as a first-order element. A message is written to the OptiStruct.msg file indicating the corresponding element ID.
CQUAD4
Defines a quadrilateral plate element (QUAD4) of the structural model. Defines a curved quadrilateral shell element with eight grid points.
Quad4
CQUAD8
Quad8
Altair Engineering

740
Supported Cards
Solver Description
Supported Elem Types Rod
Notes
CROD
Defines a tension-compression element (ROD) of the structural model. Defines a shear panel element. Defines a first order solid element, composed of 4 triangular faces. Defines a second order solid element, composed of 4 triangular faces.
CSHEAR CTETRA (4-noded)
Quad4 Tetra4
CTETRA (10-noded)
Tetra10
A second order element with missing mid-side nodes can be defined in RADIOSS (Bulk Data Format). Input data decks containing such elements are read by the translator as a first-order element. A message is written to the OptiStruct.msg file indicating the corresponding element ID.
CTRIA3
Defines a triangular plate element (TRIA3) of the structural model. Defines a second order triangular element.
Tria3
CTRIA6
Tria6
CTUBE
Defines a tension-compression- Rod torsion element (TUBE) of the structural model. Defines a viscous damper element. Spring Represented as a spring element type. Represented as a rod element type.
CVISC
CWELD
Defines a weld or fastener Mass connecting two surface patches Rod or points.
741

Altair Engineering
Supported Cards
Solver Description
Notes
HMSPRING
Defines a spring element, which Spring is converted to RADIOSS (Bulk Data Format) entities on export, in a manner similar to that explained in Using HM_ELAS. Defines a joint used in multibody dynamics. Defines a one-dimensional dummy element for use in plotting. Joint
JOINT
PLOTEL
Plot
PLOTEL3
Defines a three-noded, twoTria dimensional dummy element for Quad4 use in plotting. Defines a four-noded, twoTria dimensional dummy element for Quad4 use in plotting. Defines a uniform heat flux for CHBDYE elements. Flux
PLOTEL4
QBDY1
RBAR
Defines a rigid bar with 6 Weld degrees of freedom at each end.
RBE2
Defines a rigid body whose Rigid independent degrees of freedom RigidLink are specified at a single grid point and whose dependent degrees of freedom are specified at an arbitrary number of grid points.
An RBE2 element with one dependent node is represented as a rigid element type, while an element with multiple dependent nodes is represented as a rigid link element type.
RBE3
Defines the motion at a Rbe3 "reference" grid point as the weighted average of the motions at a set of other grid points. Defines a pin-ended rod that is Rod
RROD
Altair Engineering

742
Supported Cards
Solver Description
Notes
rigid in extension.
Abaqus
Standard.2d Template
Supported Cards
Solver Description
Supported Elem Types Rigid
Supported Parameters COUP_KIN *COUPLING with element-based *SURFACE cards are defined as groups TYPE and ELSET
*COUPLING
Define a surface-based coupling constraint where the *SURFACE card points to nodes.
*ELEMENT
Define elements by giving their nodes. Mass
MASS, ROTARYI, SPRING1, DASHPOT1, CONN2D2, ITT21 R2D2, RAX2, RB2D2, BEAM, LINK, PIN, TIE, KINCOUP, COUP_KIN DCOUP2D, COUP_DIS SPRING2, SPRINGA,
Rigid
RBE3
Spring
743

Altair Engineering
Supported Cards
Solver Description
Supported Parameters DASHPOT2, DASHPOTA, JOINTC
Bar2
SAX1, B21, B21H, B23, B23H, PIPE21, PIPE21H, F2D2, FAX2, AC1D2 B22, SAX2, AC1D3, B22H, PIPE22, PIPE22H T2D2, T2D2H, T2D2T, T2D2E, GK2D2, GK2D2N, CONN2D2, SFMAX1, MGAX1, SFMGAX1, DC1D2 GAPUNI, GAPCYL, GAPSPHER CPE3, CPS3, CPS3E, CPE3H, CPE3E, CAX3, CAX3H, CAX3E, CGAX3, CGAX3H, DCAX3, DCAX3E, DC2D3, DC2D3E, AC2D3, ACAX3, CAX3T CPE4I, CPS4, CPS4I, CPS4R, CPS4T, CPS4E, CPE4, CPE4H, CPE4IH, CPE4R, CPE4RH, CPE4T, CPE4HT, CPE4E, CAX4, CAX4H, CAX4I, CAX4IH, CAX4R, CAX4RH, CGAX4, CGAX4H, CGAX4R,
Bar3
Rod
Gap
Tria3
Quad4
Altair Engineering

744
Supported Cards
Solver Description
Supported Parameters CGAX4RH, DCAX4, DCCAX4, DCCAX4D, DCAX4E, CAX4T, CAX4HT, ACAX4, CAX4E, DC2D4, DC2D4E, AC2D4, CPE4P, CPE4PH, CPE4RP, CPE4RPH, CAXA41, CAXA4H1, CAXA4R1, CAXA4RH1, GKPS4, GKPE4, GKPS4N, COH2D4, COHAX4
Tria6
DCAX6, CPS6, CPS6M, CAX6, CAX6H, CAX6M, CAX6MH, CGAX6, CGAX6H, CPE6, CPE6H, CPE6M, CPE6MH, DC2D6, DCAX6E, DC2D6E, AC2D6, ACAX6, CPE6MP, CPE6MPH CPS8, CAX8, CAX8H, CAX8HT, CAX8R, CAX8RH, CAX8RHT, CAX8RT, CGAX8, CGAX8H, CGAX8R, CGAX8RH, CPE8, CPE8H, CPE8R, CPE8RH, CPS8R, DC2D8, CAXA81, CAXA8H1, CAXA8P1, CAXA8R1, CAXA8RH1, CAXA8RP1, DCAX8, DCAX8E, DC2D8E, AC2D8, ACAX8,
Quad8
745

Altair Engineering
Supported Cards
Solver Description
Supported Parameters CAX8T, CGAX8T, CGE8P, CPE8PH, CPE8RP, CPE8RPH
Hex8 *KINEMATIC COUPLING Constrain all or specific Rigid degrees of freedom of a set of nodes to the rigid body motion of a reference node. Define multi-point constraints. Rigid
EC3D8R KINCOUP
*MPC
BEAM, LINK, PIN, TIE See Note**
*RELEASE
Release rotational degrees of Bar2/Bar3 freedom at one or both ends of a beam element.
Standard.3d Template
Supported Cards
Solver Description
Supported Parameters COUP_KIN, COUP_DIS TYPE and ELSET
*COUPLING
Define a surface-based coupling constraint. Define elements by giving their nodes.
*ELEMENT
Mass
MASS, ROTARYI, SPRING1, DASHPOT1, CONN3D2, ITT31 RB3D2 DCOUP3D, COUP_DIS SPRING2,
Rigid RBE3
Spring
Altair Engineering

746
Supported Cards
Solver Description
Supported Parameters SPRINGA, DASHPOT2, DASHPOTA, JOINTC
Bar2
B31, B31H, B33, B33H, B31OS, B31OSH, PIPE31, PIPE31H, GK3D2, GK3D2N, AC1D2, ELBOW31, ELBOW31B, ELBOW31C B32, B32H, B32OS, B32OSH, AC1D3, ELBOW32, PIPE32, PIPE32H, MGAX2, SFMGAX2, SFMAX2 T3D2, T3D2H, T3D2T, T3D2E, CONN3D2, SFMAX1, MGAX1, SFMGAX1 GAPUNI, GAPCYL, GAPSPHER S3, S3R, STRI3, M3D3, R3D3, DS3, SFM3D3, R3D3, DS3, F3D3, ACIN3D3 S4, S4R, S4R5, M3D4, M3D4R, R3D4, DS4, SFM3D4, SFM3D4R, GK3D4L, GK3D4LN, F3D4, ACIN3D4
Bar3
Rod
Gap
Tria3
Quad4
747

Altair Engineering
Supported Cards
Solver Description
Supported Elem Types Tria6
Supported Parameters STRI65, DS6, M3D6, SFM3D6 S8R, S8R5, S8RT, DS8, M3D8, M3D8R, SFM3D8, SFM3D8R C3D4, C3D4H, DC3D4, C3D4E, DC3D4E, AC3D4 C3D8, C3D8I, C3D8H, C3D8T, C3D8HT, C3D8IH, C3D8R, C3D8RH, C3D8E, C3D6, C3D6H, C3D6E, C3D8RT, C3D8RHT C3D6, C3D6H, DC3D6, C3D6E, DC3D6E, GK3D6, GK3D6N, SC6R, COH3D6, AC3D6 C3D8I, C3D8, C3D8T, C3D8H, C3D8HT, C3D8IH, C3D8R, C3D8RH, C3D8E, DC3D8, AC3D8, DC3D8E, DCC3D8, DCC3D8D, GK3D8, GK3D8N, SC8R, COH3D8, C3D8P, C3D8PH, C3D8RP, C3D8RPH, C3D8RT, C3D8RHT C3D10, C3D10H, C3D10I, C3D10M, C3D10MH, C3D10MT, DC3D10,
Quad8
Tetra4
Pyramid5
Penta6
Hex8
Tetra10
Altair Engineering

748
Supported Cards
Solver Description
Supported Parameters C3D10E, DC3D10E, AC3D10, C3D10MP, C3D10MPH
Pyramid13
C3D20, C3D20H, C3D20R, C3D20RH, C3D20E, C3D20RE, C3D20T, C3D20HT, C3D20RT, C3D20RHT, C3D15, C3D15H, C3D15E C3D15, C3D15H, DC3D15, C3D15E, DC3D15E, AC3D15 C3D20, C3D20H, C3D20R, C3D20RH, DC3D20, AC3D20, C3D20E, C3D20RE, C3D20T, C3D20HT, C3D20RT, C3D20RHT, DC3D20E, C3D20P, C3D20PH, C3D20RP, C3D20RPH KINCOUP
Penta15
Hex20
*KINEMATIC COUPLING
Constrain all or specific degrees of freedom of a set of nodes to the rigid body motion of a reference node. Define multi-point constraints.
Rigid
*MPC
Rigid
BEAM, LINK, PIN, TIE See Note**
*RELEASE
Release rotational degrees of Bar2/Bar3 freedom at one or both ends of a beam element.
Explicit Template
749

Altair Engineering
Supported Cards
Solver Description
Supported Parameters COUP_KIN
*COUPLING
Define a surface-based coupling constraint. Define elements by giving their nodes.
*ELEMENT
TYPE and ELSET
Mass
MASS, ROTARYI, CONN3D2, CONN2D2 R2D2, RAX2, BEAM, LINK, PIN, TIE, COUP_KIN COUP_DIS SPRINGA, DASHPOTA B21, B31, SAX1, F2D2, FAX2 B22, B32 T2D2, T3D2, CONN3D2, CONN2D2 CPS3, CPE3, CAX3, S3R, R3D3, M3D3, S3RS, SFM3D3, F3D3, AC2D3, ACAX3, CAX3T, S3, ACIN3D3 CPS4R, CPE4R, CAX4R, S4R, R3D4, M3D4R, S4RS, S4RSW, SFM3D4R, COH2D4, COHAX4, F3D4, S4, ACIN3DR
Rigid
RBE3 Spring
Bar2
Bar3 Rod
Tria3
Quad4
Altair Engineering

750
Supported Cards
Solver Description
Supported Elem Types Tetra4 Pyramid5
Supported Parameters C3D4, AC3D4 C3D8, C3D8T, C3D8I, C3D8R, C3D6, C3D8RT, C3D8RHT C3D6, SC6R, COH3D6, AC3D6, C3D6R C3D8I, C3D8, C3D8T, SC8R, C3D8R, COH3D8, AC3D8R, C3D8RT, C3D8RHT, EC3D8R C3D10M, C3D10MT BEAM, LINK, PIN, TIE See Note**
Penta6
Hex8
Tetra10 *MPC Define multi-point constraints Rigid
*RELEASE
Release rotational degrees of Bar2/Bar3 freedom at one or both ends of a beam element
Note** To add a *RELEASE card to this element, click pins a = and pins b = and type in the HyperMesh dof code for the Abaqus release combination code you want from the following table: HyperMesh dof Code 4 5 45 6 46 56 456 Abaqus Release Combination Code T M2 M2-T M1 M1-T M1-M2 ALLM
751

Altair Engineering
Note:
For 2-D problems, only dof6 (M1) is active.
Actran
The following Actran element types are supported: Supported Cards Solver Description Supported Configurations bar2 tria3 tria6 quad4 quad8 tet4 tet10 penta6 penta15 hex8 hex20 Notes
ELEMENTS
ANSYS
Supported Cards
Solver Description
Supported Elem Types Bar2 Bar2
Notes
BEAM3 BEAM4
2-D Elastic Beam 3-D Elastic Beam
Config 60, Type 2 Config 60, Type 1
Altair Engineering

752
Supported Cards
Solver Description
Supported Elem Types Bar2 Bar2 Bar2
Notes
BEAM23 BEAM24 BEAM44
2-D Plastic Beam 3-D Thin-walled Beam 3-D Elastic Tapered Unsymmetric Beam 2-D Elastic Tapered Unsymmetric Beam 3-D Linear Finite Strain Beam 3-D Quadratic Finite Strain Beam Ldof, Ldof2, Ldof3, Ldof4, Ldof5
Config 60, Type 9 Config 60, Type 6 Config 60, Type 7
BEAM54
Bar2
Config 60, Type 10
BEAM188 BEAM189
Bar2 Bar3
CERIG
Rigid
Defines a rigid region. Config 5, Type 1, 2
CIRCU124
General circuit element applicable to circuit simulation Spring-Damper Nonlinear Spring Combination 2-D 2-Node Surface-to-Surface Contact 2-D 3-Node Surface-to-Surface Contact 3-D 4-Node Surface-to-Surface Contact
Rod
COMBIN14 COMBIN39 COMBIN40 CONTA171
Spring Spring Spring Plot
Config 21, Type 1 Config 21, Type 2 Config 21, Type 3 Config 2, Type 3
CONTA172
Bar3
Config 63, Type 12
CONTA173
Tria3 Quad4 Tria6 Quad 8 Mass
Config 103, Type 13 Config 104, Type 13 Config 106, Type 10 Config 108, Type 10 Config 1, Type 14
CONTA174
3-D 8-Node Surface-to-Surface Contact
CONTA175
2-D/3-D Node-to-Surface
753

Altair Engineering
Supported Cards
Solver Description
Notes
Contact CONTA177 3-D Line-to-Surface Contact Bar2 Bar3 CONTA178 CONTAC12 CONTAC48 CONTAC49 3-D Node-to-Node Contact 2-D Point-to-Point Contact Gap Gap Tria3 Tria3 Quad4 CONTAC52 CP 3-D Point-to-Point Contact Defines (or modifies) a set of coupled degrees of freedom. Gap Rigid Config 70, Type 1 Config 55, Type 1, 2 Config 70, Type 3 Config 70, Type 2
CP_ELEC CP_STRUC FLUID29 2-D Axisymmetric Harmonic Acoustic Fluid
Rigid Rigid Tria3 Quad4 Tetra4 Penta6 Hex8
FLUID30
3-D Acoustic Fluid
FLUID80 FLUID116 HF118
3-D Contained Fluid Coupled Thermal-Fluid Pipe 2-D High-Frequency Quadrilateral Solid
Hex8 Rod Tria6 Quad8
HF119
3-D High-Frequency Tetrahedral Tetra10 Solid
Altair Engineering

754
Supported Cards
Solver Description
Notes
HF120
3-D High-Frequency Brick Solid Pyramid13 Penta15 Hex20
Config 213, Type 3 Config 215, Type 3 Config 220, Type 3 Config 204, Type 11 Config 206, Type 11 Config 208, Type 11 Config 61, Type 5 Config 61, Type 1 Config 61, Type 2
HYPER58
3-D 8-Node Mixed u-P Hyperelastic Solid
Tetra4 Penta6 Hex8
LINK1 LINK8 LINK10
2-D Spar (or Truss) 3-D Spar (or Truss) Tension-only or Compressiononly Spar Radiation Link 2-D Conduction Bar 3-D Conduction Bar Convection Link Coupled Thermal-Electric Line
Rod Rod Rod
LINK31 LINK32 LINK33 LINK34 LINK68 LINK180 MASS21 MASS71 MESH200
Rod Rod Rod Rod Rod
Config 61, Type 6 Config 61, Type 7 Config 61, Type 8 Config 61, Type 9 Config 61, Type 14 Config 61, Type 11 Config 1, Type 1 Config 1, Type 2 Config 63, Type 26 Config 61, Type 26 Config 103, Type 26 Config 204, Type 26 Config 210, Type 26 Config 104, Type 26
3-D Finite Strain Spar (or Truss) Rod Structural Mass Thermal Mass Meshing Facet Mass Mass Bar3 Rod Tria3 Tetra4 Tetra10 Quad4
755

Altair Engineering
Supported Cards
Solver Description
Supported Elem Types Hex8 Tria6 Quad8 Hex20
Notes
MPC184
Multipoint Constraint Elements: Rigid Link, Rigid Beam, Slider, Spherical, Revolute, Universal Elastic Straight Pipe Elastic Curved Pipe (Elbow) Plastic Straight Pipe Plastic Curved Pipe (Elbow)
Rod
PIPE16 PIPE18 PIPE20 PIPE60 PLANE2
Bar2 Bar2 Rod Bar2
2-D 6-Node Triangular Structural Tria6 Solid 2-D Coupled-Field Solid Tria3 Quad4
PLANE13
PLANE25
Axisymmetric-Harmonic 4-Node Tria3 Structural Solid Quad4 2-D 6-Node Triangular Thermal Solid 2-D Structural Solid Tria6
PLANE35
PLANE42
Tria3 Quad4
Config 103, Type 4 Config 104, Type 4 Config 106, Type 9 Config 108, Type 9 Config 103, Type 5 Config 104, Type 5
PLANE53
2-D 8-Node Magnetic Solid
Tria6 Quad8
PLANE55
2-D Thermal Solid
Tria3 Quad4
Altair Engineering

756
Supported Cards
Solver Description
Supported Elem Types Tria3 Quad4
Notes
PLANE67
2-D Coupled Thermal-Electric Solid
Config 103, Type 21 Config 104, Type 21 Config 103, Type 9 Config 104, Type 9 Config 106, Type 2 Config 108, Type 2 Config 106, Type 8 Config 108, Type 8 Config 106, Type 1 Config 108, Type 1 Config 106, Type 3 Config 108, Type 3 Config 106, Type 22 Config 108, Type 22 Config 106, Type 23 Config 108, Type 23 Config 106, Type 31 Config 103, Type 22 Config 104, Type 22 Config 103, Type 23 Config 104, Type 23 Config 106, Type 19 Config 108, Type 19
PLANE75
Axisymmetric-Harmonic 4-Node Tria3 Thermal Solid Quad4 2-D 8-Node Thermal Solid Tria6 Quad8
PLANE77
PLANE78
Axisymmetric-Harmonic 8-Node Tria6 Thermal Solid Quad8 2-D 8-Node Structural Solid Tria6 Quad8
PLANE82
PLANE83
Axisymmetric-Harmonic 8-Node Tria6 Structural Solid Quad8 2-D 8-Node Electrostatic Solid Tria6 Quad8
PLANE121
PLANE145
2-D Quadrilateral Structural Solid p-Element
Tria6 Quad8 Tria6
PLANE146 PLANE162 Explicit 2-D Structural Solid
Tria3 Quad4
PLANE182
2-D 4-Node Structural Solid
Tria3 Quad4
PLANE183
Tria6 Quad8
PLANE223
2-D 8-Node Coupled-Field Solid
Tria6
757

Altair Engineering
Supported Cards
Solver Description
Supported Elem Types Quad8
Notes
PRETS179
Define a 2-D or 3-D pretension section within a meshed structure Distributes the force/moment applied at the master node to a set of slave nodes, taking into account the geometry of the slave nodes as well as weighting factors. Shear/Twist Panel Membrane Shell
Bar2
Config 60, Type 17
RBE3
Rbe3
SHELL28 SHELL41
Quad4 Tria3 Quad4
Config 104, Type 12 Config 103, Type 19 Config 104, Type 19 Config 103, Type 2 Config 104, Type 2 Config 60, Type 14 Config 103, Type 7 Config 104, Type 7 Config 60, Type 15
SHELL43
4-Node Plastic Large Strain Shell
Tria3 Quad4 Bar2 Tria3 Quad4
SHELL51 SHELL57
Axisymmetric Structural Shell Thermal Shell
SHELL61
Axisymmetric-Harmonic Structural Shell Elastic Shell
Bar2
SHELL63
Tria3 Quad4
Config 103, Type 1 Config 104, Type 1 Config 106, Type 6 Config 108, Type 6 Config 106, Type 4 Config 108, Type 4 Config 106, Type 5
SHELL91
Nonlinear Layered Structural Shell
Tria6 Quad8 Tria6 Quad8
SHELL93
8-Node Structural Shell
SHELL99
Linear Layered Structural Shell
Tria6
Altair Engineering

758
Supported Cards
Solver Description
Notes
Config 108, Type 5 Config 103, Type 25 Config 104, Type 25 Config 106, Type 24 Config 108, Type 24 Config 103, Type 10 Config 104, Type 10 Config 106, Type 20 Config 108, Type 20 Config 103, Type 20 Config 104, Type 20 Config 103, Type 17 Config 104, Type 17 Config 103, Type 11 Config 104, Type 11
SHELL131
4-Node Layered Thermal Shell
Tria3 Quad4
SHELL132
8-Node Layered Thermal Shell
Tria6 Quad8
SHELL143
4-Node Plastic Small Strain Shell
Tria3 Quad4 Tria6 Quad8 Tria3 Quad4
SHELL150
8-Node Structural Shell pElement
SHELL157
Thermal-Electric Shell
SHELL163
Explicit Thin Structural Shell
Tria3 Quad4
SHELL181
4-Node Finite Strain Shell
Tria3 Quad4
SHELL208
2-Node Finite Strain Axisymmetric Shell 3-Node Finite Strain Axisymmetric Shell 8-Node Finite Strain Shell
Bar2
SHELL209
Bar2
SHELL281
Tria6 Quad8
SOLID5
3-D Coupled-Field Solid
Penta6 Hex8
SOLID45
3-D Structural Solid
Tetra4 Penta6
759

Altair Engineering
Supported Cards
Solver Description
Supported Elem Types Hex8
Notes
Config 208, Type 1 Config 204, Type 6 Config 206, Type 6 Config 208, Type 6 Config 204, Type 15 Config 205, Type 15 Config 206, Type 15 Config 208, Type 15 Config 204, Type 7 Config 206, Type 7 Config 208, Type 7 Config 204, Type 4 Config 206, Type 4 Config 208, Type 4 Config 204, Type 3 Config 206, Type 3 Config 208, Type 3
SOLID46
3-D 8-Node Layered Structural Solid
Tetra4 Penta6 Hex8
SOLID62
3-D Magneto-Structural Solid
Tetra4 Pyramid5 Penta6 Hex8
SOLID64
3-D Anisotropic Structural Solid Tetra4 Penta6 Hex8
SOLID69
3-D Coupled Thermal-Electric Solid
Tetra4 Penta6 Hex8
SOLID70
3-D Thermal Solid
Tetra4 Penta6 Hex8
SOLID72 SOLID73
Tetra4 Tetra4 Penta6 Hex8
SOLID87
3-D 10-Node Tetrahedral Thermal Solid 3-D 20-Node Thermal Solid
Tetra10
Config 210, Type 5
SOLID90
Tetra10 Pyramid13
Altair Engineering

760
Supported Cards
Solver Description
Supported Elem Types Penta15 Hex20
Notes
SOLID92
3-D 10-Node Tetrahedral Structural Solid 3-D 20-Node Structural Solid
Tetra10
Config 210, Type 3
SOLID95
Config 210, Type 1 Config 213, Type 1 Config 215, Type 1 Config 220, Type 1 Config 204, Type 5 Config 205, Type 5 Config 206, Type 5 Config 208, Type 5 Config 204, Type 8 Config 205, Type 8 Config 206, Type 8 Config 208, Type 8 Config 210, Type 4 Config 210, Type 8 Config 213, Type 8 Config 215, Type 8 Config 220, Type 8
SOLID96
3-D Magnetic Scalar Solid
SOLID97
3-D Magnetic Solid
SOLID98 SOLID117
Tetrahedral Coupled-Field Solid 3-D 20-Node Magnetic Solid
Tetra10 Tetra10 Pyramid13 Penta15 Hex20
SOLID147
3-D Brick Structural Solid pElement
Penta15 Hex20 Penta15 Tetra10 Config 215, Type 9 Config 210, Type 9
SOLID148
3-D Tetrahedral Structural Solid p-Element
761

Altair Engineering
Supported Cards
Solver Description
Notes
SOLID164
Explicit 3-D Structural Solid
SOLID168
Explicit 3-D 10-Node Tetrahedral Structural Solid 3-D 8-Node Structural Solid
Tetra10
SOLID185
Tetra4 Penta6 Hex8
Config 204, Type 13 Config 206, Type 13 Config 208, Type 13 Config 210, Type 7 Config 213, Type 7 Config 215, Type 7 Config 220, Type 7 Config 210, Type 6
SOLID186
SOLID187
3-D 10-Node Tetrahedral Structural Solid 3-D 20-Node Layered Structural Solid
Tetra10
SOLID191
Tetra10 Penta15 Hex20
SOLID226
SOLID227
Tetra10
Altair Engineering

762
Supported Cards
Solver Description
Supported Elem Types Penta6 Hex8
Notes
SOLSH190
3-D 8-Node Layered Solid Shell
Config 206 Config 208, Type 17
SURF151 SURF152
2-D Thermal Surface Effect 3-D Thermal Surface Effect
Bar2 Quad4 Quad8 Tria6
SURF153
2-D Structural Surface Effect
Bar2 Bar3
SURF154
3-D Structural Surface Effect
Quad4 Quad8 Tria6
SURF156
3-D Structural Surface Line Load Effect 2-D Target Segment
Bar3
TARGE169
Mass Bar2 Bar3
TARGE170
3-D Target Segment
Mass Tria3 Quad4 Tria6 Quad8
VISCO88
2-D 8-Node Viscoelastic Solid
Tria6 Quad8
VISCO107
3-D 8-Node Viscoplastic Solid
Tetra4 Penta6
763

Altair Engineering
Supported Cards
Solver Description
Notes
Config 208, Type 16
LS-DYNA
Supported Cards
Solver Description
Notes
*CONSTRAINED_ Define the butt type of weld. GENERALIZED_WEL D_ BUTT_(ID)
Spot(default)/type 1, Fillet/type 2, and Butt/type 3 failure modes are supported. Failure information is based on weld type selected. Coordinate System ID can be selected. No Failure/Type 0 Card 36 entities are defined as *CONSTRAINED_ NODAL_RIGID_BODI ES in Keyword. They are a separate element type.
*CONSTRAINED_ Define the fillet type of weld. GENERALIZED_WEL D_ FILLET_(ID) *CONSTRAINED_ Define the spot type of weld. GENERALIZED_WEL D_ SPOT_(ID) *CONSTRAINED_ INTERPOLATION *CONSTRAINED_JOI NT_ Define an interpolation constrain. Define a joint between two rigid bodies.
Rigid
Rigid
RBE3
Joint
Altair Engineering

764
Supported Cards
Solver Description
Notes
CYLINDRICAL *CONSTRAINED_JOI NT_ CYLINDRICAL_FAILU RE(ID) *CONSTRAINED_JOI NT_ CYLINDRICAL_LOCA L(ID) *CONSTRAINED_JOI NT_ CYLINDRICAL_LOCA L_ FAILURE(ID) *CONSTRAINED_JOI NT_ LOCKING(ID) *CONSTRAINED_JOI NT_ LOCKING_FAILURE (ID) *CONSTRAINED_JOI NT_ LOCKING_LOCAL(ID) *CONSTRAINED_JOI NT_ LOCKING_LOCAL_ FAILURE(ID) *CONSTRAINED_JOI NT_ PLANAR(ID) *CONSTRAINED_JOI NT_ PLANAR_FAILURE (ID) Joint
Joint
Joint
Joint
Joint
Joint
Joint
Joint
Joint
765

Altair Engineering
Supported Cards
Solver Description
Supported Elem Types Joint
Notes
*CONSTRAINED_JOI NT_ PLANAR_LOCAL(ID) *CONSTRAINED_JOI NT_ PLANAR_FAILURE_L OCAL (ID) *CONSTRAINED_JOI NT_ REVOLUTE *CONSTRAINED_JOI NT_ REVOLUTE_LOCAL (ID) *CONSTRAINED_JOI NT_ REVOLUTE_FAILUR E(ID) *CONSTRAINED_JOI NT_ REVOLUTE_LOCAL_ FAILURE(ID) *CONSTRAINED_JOI NT_ SPHERICAL(ID) *CONSTRAINED_JOI NT_ SPHERICAL_LOCAL (ID) *CONSTRAINED_JOI NT_ SPHERICAL_FAILUR E(ID) *CONSTRAINED_JOI
Joint
Joint
Joint
Joint
Joint
Joint
Joint
Joint
Joint
Altair Engineering

766
Supported Cards
Solver Description
Notes
NT_ SPHERICAL_LOCAL _ FAILURE(ID) *CONSTRAINED_JOI NT_ TRANSLATIONAL(ID) *CONSTRAINED_JOI NT_ TRANSLATIONAL_FA ILURE (ID) *CONSTRAINED_JOI NT_ TRANSLATIONAL_LO CAL (ID) *CONSTRAINED_JOI NT_ TRANSLATIONAL_LO CAL_ FAILURE(ID) *CONSTRAINED_JOI NT_ UNIVERSAL(ID) *CONSTRAINED_JOI NT_ UNIVERSAL_FAILUR E(ID) *CONSTRAINED_JOI NT_ UNIVERSAL_LOCAL (ID) *CONSTRAINED_JOI NT_ UNIVERSAL_LOCAL Joint
Joint
Joint
Joint
Joint
Joint
Joint
Joint
767

Altair Engineering
Supported Cards
Solver Description
Notes
_ FAILURE(ID) *CONSTRAINED_NO DAL_ RIGID_BODY *CONSTRAINED_NO DAL_ RIGID_BODY (2Noded) *CONSTRAINED_NO Used when inertial properties DAL_ are defined rather than RIGID_BODY_INERTI computed. A *CONSTRAINED_NO DAL_ RIGID_BODY_INERTI A (2Noded) *CONSTRAINED_NO DAL_ RIGID_BODY_INERTI A _SPC *CONSTRAINED_NO DAL_ RIGID_BODY_INERTI A _SPC (2-Noded) *CONSTRAINED_NO DAL_ RIGID_BODY_SPC *CONSTRAINED_NO DAL_ RIGID_BODY_SPC (2Noded) *CONSTRAINED_NO Define nodal constraint sets for Define a nodal rigid body. Rigid
Rigid
Rigid
Rigid
Rigid
Rigid
Rigid
Rigid
Rigid
Altair Engineering

768
Supported Cards
Solver Description
Notes
DE_ SET *CONSTRAINED_NO DE_ SET (2-Noded) *CONSTRAINED_NO DE_ SET_ID
translational motion in global coordinates. Rigid
Rigid
*CONSTRAINED_RIV Define massless rivets between Weld ET non-contiguous nodal pairs. *CONSTRAINED_SH ELL_ TO_SOLID *CONSTRAINED_ SPOTWELD_ID Define a tie between a shell edge and solid elements. Rigid
Define massless spot welds between non-contiguous nodal pairs.
Weld
Normal and shear failure values can be edited.
*CONSTRAINED_ SPOTWELD_FILTER ED_ FORCE_ID
Weld
*ELEMENT_BEAM
Define two node elements including 3D beams, trusses, 2D axisymmetric shells and 2D plane strain beam elements.
Bar
Thickness option can be added. This allows you to edit the parameters based on the element formulation in the property to which the beam points.
*ELEMENT_BEAM_ OFFSET *ELEMENT_BEAM_ OFFSET_PID
Bar
Bar
769

Altair Engineering
*ELEMENT_BEAM
Bar
*ELEMENT_BEAM_ OFFSET_THICKNES S *ELEMENT_BEAM_ ORIENTATION *ELEMENT_BEAM_P ID *ELEMENT_BEAM_P ID_ ORIENTATION *ELEMENT_BEAM_P ID_ SCALAR *ELEMENT_BEAM_ SCALAR *ELEMENT_BEAM_ SCALAR_ORIENTATI ON *ELEMENT_BEAM_ SECTION *ELEMENT_BEAM_ SECTION_ORIENTAT ION *ELEMENT_BEAM_ SECTION_PID *ELEMENT_BEAM_ THICKNESS
Bar
Bar
Bar
Bar
Bar
Bar
Bar
Bar
Bar
Bar
Bar
Altair Engineering

770
*ELEMENT_BEAM
Bar
*ELEMENT_BEAM_ THICKNESS_ORIENT ATION *ELEMENT_BEAM_ THICKNESS_PID *ELEMENT_BEAM_ THICKNESS_SCALA R *ELEMENT_DISCRET Define a discrete (spring or E damper) element between two nodes or a node and ground. *ELEMENT_INERTIA Define a lumped inertia element assigned to a nodal point.
Bar
Bar
Bar
Spring
Scale factor, printing flags, and offset values can be edited.
Mass
*ELEMENT_INERTIA _ OFFSET *ELEMENT_MASS Define a lumped mass element assigned to a nodal point or equally distributed to the nodes of a node set.
Mass
Mass
*ELEMENT_MASS_ NODE_SET
Mass elements defined on node Mass set Mass
*ELEMENT_MASS_P Define additional non-structural ART mass to be distributed by an area weighted distribution to all nodes of a given part ID. *ELEMENT_MASS_ PART_SET Mass elements defined on part set.
Mass
771

Altair Engineering
*ELEMENT_BEAM
Bar
*ELEMENT_PLOTEL
Define a null beam element for visualization.
Plot
*ELEMENT_SEATBE Define a seat belt element. LT *ELEMENT_SEATBE Define a seat belt LT_ accelerometer. ACCELEROMETER *ELEMENT_SEATBE Define seat belt pretensioner. LT_ PRETENSIONER *ELEMENT_SEATBE Define seat belt retractor. LT_ RETRACTOR *ELEMENT_SEATBE Define seat belt sensor. LT_ SENSOR *ELEMENT_SEATBE Define seat belt slip ring. LT_ SLIPRING *ELEMENT_SHELL Define three, four, six and eight node elements including 3D shells, membranes, 2D plane stress, plane strain, and axisymmetric solids.
Rod
Tria3
Mass
Mass
Sensors
Mass
Tria3, Quad4
Thickness and beta options can be added singularly or together. This allows you to edit the thickness and material angles to override the SECTION card.
*ELEMENT_SHELL_ BETA
Tria3, Quad4
Altair Engineering

772
*ELEMENT_BEAM
Bar
*ELEMENT_SHELL_ BETA_ OFFSET *ELEMENT_SHELL_ DOF *ELEMENT_SHELL_ MCID *ELEMENT_SHELL_ MCID_ OFFSET *ELEMENT_SHELL_ OFFSET *ELEMENT_SHELL_ THICKNESS *ELEMENT_SHELL_ THICKNESS_BETA *ELEMENT_SHELL_ THICKNESS_BETA_ OFFSET *ELEMENT_SHELL_ THICKNESS_MCID *ELEMENT_SHELL_ THICKNESS_MCID_ OFFSET *ELEMENT_SHELL_ THICKNESS_OFFSE T
Tria3, Quad4
Tria3, Quad4
Tria3, Quad4
Tria3, Quad4
Tria3, Quad4
Tria3, Quad4
Tria3, Quad4
Tria3, Quad4
Tria3, Quad4
Tria3, Quad4
Tria3, Quad4
773

Altair Engineering
*ELEMENT_BEAM
Bar
*ELEMENT_SOLID
Define three-dimensional solid elements including 4 noded tetrahedrons and 8-noded hexahedrons.
Tetra4, Penta6, Hex8, Tetra10
*ELEMENT_SOLID_O Define a local coordinate RTHO system for orthotropic and anisotropic materials *ELEMENT_SOLID_ TET4TOTET10 Converts 4 node tetrahedron solids to 10 node quadratic tetrahedron solids. Define a lumped mass element assigned to a nodal point Define an eight node thick shell element which is available with either fully reduced or selectively reduced integration rules.
Tetra4, Penta6, Hex8, Tetra10
Tetra4
*ELEMENT_SPH
Mass
*ELEMENT_TSHELL
Penta6, Hex8
*INITIAL_MOMENTU M
Defines initial momentum in the Tetra4, Penta6, Hex8, solid element at the start of Tetra10 analysis. These momentum could be from previous analysis/ step carried forward to next analysis/step.
This is supported as an attribute to an element to maintain its associativity with element inside HM
*INITIAL_STRAIN_SH Defines stress in the shell Tria3, Quad4 ELL element at the start of analysis. These stress could be from previous analysis/step carried forward to next analysis/step. *INITIAL_STRAIN_SO Defines stress in the solid Tetra4, Penta6, Hex8, LID element at the start of analysis. Tetra10 These stress could be from
This is supported as an attribute to an element to maintain its associativity with element inside HM This is supported as an attribute to an element to maintain
Altair Engineering

774
*INITIAL_MOMENTU M
Defines initial momentum in the Tetra4, Penta6, Hex8, solid element at the start of Tetra10 analysis. These momentum could be from previous analysis/ step carried forward to next analysis/step. previous analysis/step carried forward to next analysis/step.
This is supported as an attribute to an element to maintain its associativity with element inside HM
its associativity with element inside HM This is supported as an attribute to an element to maintain its associativity with element inside HM This is supported as an attribute to an element to maintain its associativity with element inside HM This is supported as an attribute to an element to maintain its associativity with element inside HM
*INITIAL_STRESS_B EAM
Defines stress in the beam Bar element at the start of analysis. These stress could be from previous analysis/step carried forward to next analysis/step. Defines stress in the shell Tria3, Quad4 element at the start of analysis. These stress could be from previous analysis/step carried forward to next analysis/step. Defines stress in the solid Tetra4, Penta6, Hex8, element at the start of analysis. Tetra10 These stress could be from previous analysis/step carried forward to next analysis/step.
*INITIAL_STRESS_S HELL
*INITIAL_STRESS_S OLID
MADYMO
Supported Cards
Solver Description
Supported Elem Types Rod
Notes
COMP_SIX_DOF
Component for six degree of freedom restraint (for internal use only).
Defined on the card of the parent RESTRAINT. Defined when creating the parent SPOTWELD. Defined when creating the parent SPOTWELD.
CONNECT_N2
Spotweld connection between 2 Rigid nodes.
CONNECT_N3
Spotweld connection between 3 Rigid nodes.
775

Altair Engineering
Supported Cards
Solver Description
Notes
CONSTRAINT. SIMPLE
Simple constraints for FE nodes Rigid
independent node + dependent nodes = references to nodes representing GROUP_LIST dof1 = dof2 = dof3 = dof4 = dof5 = dof6 = DOF_DX DOF_DY DOF_DZ DOF_RX DOF_RY DOF_RZ
ELEMENT.MASS1
Nodal mass element
Mass
nodes = N1 mass = MASS property and system are not used ASSEMBLY = reference to the parent FE_MODEL
MODE
Flexible body deformation mode Rigid shape Nodal displacements define a deformable body mode shape. Rigid Defined on the card of the parent MODE.
MODE_SHAPE
RESTRAINT. CARDAN
A Cardan restraint consists of Rod three torsional parallel springs and dampers that connect two bodies. The torques depend on the Cardan angles that describe the relative orientation of the corresponding restraint coordinate systems.
TYPE = CARDAN The first node and second node are used to create the related elements CRDSYS_OBJECT_1 and CRDSYS_OBJECT_2 . property is not used
RESTRAINT. FLEX_TORS
A flexion torsion restraint Rod consists of a damper and two torsional springs that connect two bodies. The torques depend
TYPE = FLEX_TORS The first node and second node are
Altair Engineering

776
RESTRAINT. CARDAN
TYPE = CARDAN The first node and second node are used to create the related elements CRDSYS_OBJECT_1 and CRDSYS_OBJECT_2 . property is not used
on the bending and torsion angles that describe the relative orientation of the corresponding restraint coordinate systems.
used to create the related elements CRDSYS_OBJECT_1 and CRDSYS_OBJECT_2 . property is not used
RESTRAINT.JOINT
A joint restraint specifies elastic, damping and friction loads in kinematic joints corresponding to joint degrees of freedom.
Rod
TYPE = JOINT None of the nodes are actually used, except for the graphical positioning of the RESTRAINT. However, it is recommended to use the same nodes defining the referenced JOINT for defining the RESTRAINT too. property is not used
RESTRAINT.KELVIN
A Kelvin restraint consists of a parallel spring and damper that connect two bodies. The force depends on the distance between the attachment points.
Rod
TYPE = KELVIN Select STRAIN or LENGTH to either specify the INITIAL_STRAIN or the UNTENS_LENGTH. The first node and second node are used to create the
777

Altair Engineering
RESTRAINT. CARDAN
TYPE = CARDAN The first node and second node are used to create the related elements CRDSYS_OBJECT_1 and CRDSYS_OBJECT_2 . property is not used related elements POINT_OBJECT_1 and POINT_OBJECT_2. property is not used
RESTRAINT. MAXWELL
A Maxwell restraint consists of a spring and damper in series that connect two bodies. The force depends on the distance between the attachment points.
Rod
TYPE = MAXWELL The first node and second node are used to create the related elements POINT_OBJECT_1 and POINT_OBJECT_2. property is not used
RESTRAINT.POINT
A point restraint consists of three mutually perpendicular parallel springs and dampers that connect two bodies. The force depends on the coordinates of the restrained point relative to the corresponding restraint coordinate system.
Rod
TYPE = POINT The first node and second node are used to create the related elements CRDSYS_OBJECT_1 and POINT_OBJECT_2. property is not used
RESTRAINT.SIX_DOF Six degrees of freedom restraint Rod
TYPE = SIX_DOF None of the nodes are actually used, except for the graphical positioning of the RESTRAINT.
Altair Engineering

778
RESTRAINT. CARDAN
TYPE = CARDAN The first node and second node are used to create the related elements CRDSYS_OBJECT_1 and CRDSYS_OBJECT_2 . property is not used However, it is recommended to use the same nodes defining the referenced JOINT for defining the RESTRAINT too. property is not used
RIGID_ELEMENT
Elements and/or nodes that form a rigid part.
Rigid
independent node + dependent nodes = references to all nodes represented in NODE_LIST, ELEMENT_LIST and GROUP_LIST. dof1 through dof6 are not used.
779

Altair Engineering
SPOTWELD. NODE_NODE
Node-node spotweld.
Weld
Choose using nodes and node-node , set element config to weld and select an independent node + a dependent node (these are used in NODE_2 of the related element CONNECT_N2). property and move dep node are not used Choose individual spotweld failure to enter the attributes for the current SPOTWELD, or choose spotweld failure by property to use predefined attributes. To define a set of spotweld failure attributes that can be referenced here (and in other SPOTWELD definitions), create a property of type (SPOTWELD) and enter the spotweld attributes on the card image. [ASSEMBLY] = reference to the parent, if not selected, will be written to the MADYMO assembly, which is the top level of the assembly hierarchy
SPOTWELD. THREE_NODE
Three node spotweld.
Rigid
Select an independent node + 2 dependent nodes (these are used in NODE_3 of the
Altair Engineering

780
SPOTWELD. NODE_NODE
Node-node spotweld.
Weld
Choose using nodes and node-node , set element config to weld and select an independent node + a dependent node (these are used in NODE_2 of the related element CONNECT_N2). property and move dep node are not used Choose individual spotweld failure to enter the attributes for the current SPOTWELD, or choose spotweld failure by property to use predefined attributes. To define a set of spotweld failure attributes that can be referenced here (and in other SPOTWELD definitions), create a property of type (SPOTWELD) and enter the spotweld attributes on the card image. [ASSEMBLY] = reference to the parent, if not selected, will be written to the MADYMO assembly, which is the top level of the assembly hierarchy related element CONNECT_N3). dof1 through dof6 are not used
781

Altair Engineering
SPOTWELD. NODE_NODE
Node-node spotweld.
Weld
Choose using nodes and node-node , set element config to weld and select an independent node + a dependent node (these are used in NODE_2 of the related element CONNECT_N2). property and move dep node are not used Choose individual spotweld failure to enter the attributes for the current SPOTWELD, or choose spotweld failure by property to use predefined attributes. To define a set of spotweld failure attributes that can be referenced here (and in other SPOTWELD definitions), create a property of type (SPOTWELD) and enter the spotweld attributes on the card image. [ASSEMBLY] = reference to the parent, if not selected, will be written to the MADYMO assembly, which is the top level of the assembly hierarchy Choose individual spotweld failure to enter the attributes for the current SPOTWELD, or
Altair Engineering

782
SPOTWELD. NODE_NODE
Node-node spotweld.
Weld
Choose using nodes and node-node , set element config to weld and select an independent node + a dependent node (these are used in NODE_2 of the related element CONNECT_N2). property and move dep node are not used Choose individual spotweld failure to enter the attributes for the current SPOTWELD, or choose spotweld failure by property to use predefined attributes. To define a set of spotweld failure attributes that can be referenced here (and in other SPOTWELD definitions), create a property of type (SPOTWELD) and enter the spotweld attributes on the card image. [ASSEMBLY] = reference to the parent, if not selected, will be written to the MADYMO assembly, which is the top level of the assembly hierarchy choose spotweld failure by property to use predefined attributes. To define a set of spotweld failure
783

Altair Engineering
SPOTWELD. NODE_NODE
Node-node spotweld.
Weld
Choose using nodes and node-node , set element config to weld and select an independent node + a dependent node (these are used in NODE_2 of the related element CONNECT_N2). property and move dep node are not used Choose individual spotweld failure to enter the attributes for the current SPOTWELD, or choose spotweld failure by property to use predefined attributes. To define a set of spotweld failure attributes that can be referenced here (and in other SPOTWELD definitions), create a property of type (SPOTWELD) and enter the spotweld attributes on the card image. [ASSEMBLY] = reference to the parent, if not selected, will be written to the MADYMO assembly, which is the top level of the assembly hierarchy attributes that can be referenced here (and in other SPOTWELD definitions), create a property of type
Altair Engineering

784
SPOTWELD. NODE_NODE
Node-node spotweld.
Weld
Choose using nodes and node-node , set element config to weld and select an independent node + a dependent node (these are used in NODE_2 of the related element CONNECT_N2). property and move dep node are not used Choose individual spotweld failure to enter the attributes for the current SPOTWELD, or choose spotweld failure by property to use predefined attributes. To define a set of spotweld failure attributes that can be referenced here (and in other SPOTWELD definitions), create a property of type (SPOTWELD) and enter the spotweld attributes on the card image. [ASSEMBLY] = reference to the parent, if not selected, will be written to the MADYMO assembly, which is the top level of the assembly hierarchy (SPOTWELD) and enter the spotweld attributes on the card image.
785

Altair Engineering
SPOTWELD. NODE_NODE
Node-node spotweld.
Weld
Choose using nodes and node-node , set element config to weld and select an independent node + a dependent node (these are used in NODE_2 of the related element CONNECT_N2). property and move dep node are not used Choose individual spotweld failure to enter the attributes for the current SPOTWELD, or choose spotweld failure by property to use predefined attributes. To define a set of spotweld failure attributes that can be referenced here (and in other SPOTWELD definitions), create a property of type (SPOTWELD) and enter the spotweld attributes on the card image. [ASSEMBLY] = reference to the parent, if not selected, will be written to the MADYMO assembly, which is the top level of the assembly hierarchy [ASSEMBLY] = reference to the parent, if not selected, will be written to the
Altair Engineering

786
SPOTWELD. NODE_NODE
Node-node spotweld.
Weld
Choose using nodes and node-node , set element config to weld and select an independent node + a dependent node (these are used in NODE_2 of the related element CONNECT_N2). property and move dep node are not used Choose individual spotweld failure to enter the attributes for the current SPOTWELD, or choose spotweld failure by property to use predefined attributes. To define a set of spotweld failure attributes that can be referenced here (and in other SPOTWELD definitions), create a property of type (SPOTWELD) and enter the spotweld attributes on the card image. [ASSEMBLY] = reference to the parent, if not selected, will be written to the MADYMO assembly, which is the top level of the assembly hierarchy MADYMO assembly, which is the top level of the assembly hierarchy
787

Altair Engineering
SPOTWELD. NODE_NODE
Node-node spotweld.
Weld
Choose using nodes and node-node , set element config to weld and select an independent node + a dependent node (these are used in NODE_2 of the related element CONNECT_N2). property and move dep node are not used Choose individual spotweld failure to enter the attributes for the current SPOTWELD, or choose spotweld failure by property to use predefined attributes. To define a set of spotweld failure attributes that can be referenced here (and in other SPOTWELD definitions), create a property of type (SPOTWELD) and enter the spotweld attributes on the card image. [ASSEMBLY] = reference to the parent, if not selected, will be written to the MADYMO assembly, which is the top level of the assembly hierarchy
STRAP
Massless linear tension-only spring between two nodes.
Spring
Choose no vector and select: first node = N1 second node = N2
Altair Engineering

788
SPOTWELD. NODE_NODE
Node-node spotweld.
Weld
Choose using nodes and node-node , set element config to weld and select an independent node + a dependent node (these are used in NODE_2 of the related element CONNECT_N2). property and move dep node are not used Choose individual spotweld failure to enter the attributes for the current SPOTWELD, or choose spotweld failure by property to use predefined attributes. To define a set of spotweld failure attributes that can be referenced here (and in other SPOTWELD definitions), create a property of type (SPOTWELD) and enter the spotweld attributes on the card image. [ASSEMBLY] = reference to the parent, if not selected, will be written to the MADYMO assembly, which is the top level of the assembly hierarchy dof1 through dof6 and property are not used ASSEMBLY =
789

Altair Engineering
SPOTWELD. NODE_NODE
Node-node spotweld.
Weld
Choose using nodes and node-node , set element config to weld and select an independent node + a dependent node (these are used in NODE_2 of the related element CONNECT_N2). property and move dep node are not used Choose individual spotweld failure to enter the attributes for the current SPOTWELD, or choose spotweld failure by property to use predefined attributes. To define a set of spotweld failure attributes that can be referenced here (and in other SPOTWELD definitions), create a property of type (SPOTWELD) and enter the spotweld attributes on the card image. [ASSEMBLY] = reference to the parent, if not selected, will be written to the MADYMO assembly, which is the top level of the assembly hierarchy reference to the parent FE_MODEL
MARC
Altair Engineering

790
Supported Cards
Solver Description
Supported Elem Types Mass
Notes
CBUSH E_1 Two-node axisymmetric shell element. Axisymmetric, triangular ring element.
Plot
E_2
Tria3
E_3
Two-dimensional (plane stress), Quad4 four-node, isoparametric quadrilateral. Beam column. Two-dimensional plane strain, constant stress triangle. Eight-node isoparametric three dimensional hexahedron. Three dimensional truss element. Axisymmetric quadrilateral element (isoparametric). Plane strain quadrilateral element (isoparametric). Closed section beam. Four node, isoparametric membrane. Axisymmetric torsional quadrilateral. Three-dimensional, 20-node brick. Closed section beam in three dimensions. Plane stress, eight-node Bar2 Tria3
E_5 E_6
E_7
Hex8
E_9
Rod
E_10
Quad4
E_11
Quad4
E_14 E_18
Bar2 Quad4
E_20
Quad4
E_21
Hex20
E_25
Bar2
E_26
Quad8
791

Altair Engineering
Supported Cards
Solver Description
Notes
distorted quadrilateral. E_27 Plane strain, eight-node distorted quadrilateral. Axisymmetric, eight-node distorted quadrilateral. Generalized, plane strain, distorted quadrilateral. Quad8
E_28
Quad8
E_29
Quad8
E_32
Plane strain, eight-node Quad8 distorted quadrilateral, Hermann or Mooney material formulation. Axisymmetric, eight-node Quad8 distorted quadrilateral, Hermann or Mooney material formulation. Generalized plane strain, eightnode, distorted quadrilateral, Hermann or Mooney material formulation. Three-dimensional, 20-node brick, Hermann or Mooney material formulation. Heat transfer element (arbitrary axisymmetric triangle). Heat transfer element (planar bilinear quadrilateral). Curved Timoshenko beam element in a plane. Elastic beam. Plane stress, eight-node quadrilateral with reduced integration. Plane strain, eight-node Quad8
E_33
E_34
E_35
Hex20
E_38
Tria3
E_39
Quad4
E_45
Bar3
E_52 E_53
Bar2 Quad8
E_54
Quad8
Altair Engineering

792
Supported Cards
Solver Description
Notes
quadrilateral with reduced integration. E_55 Axisymmetric, eight-node distorted quadrilateral with reduced integration. Three-dimensional, 20-node brick with reduced integration. Plane strain, eight-node distorted quadrilateral for incompressible behavior with reduced integration. Axisymmetric, eight-node distorted quadrilateral for incompressible behavior with reduced integration. Generalized plane strain, tennode distorted quadrilateral for incompressible behavior with reduced integration. Three-dimensional, 20-node brick for incompressible behavior with reduced integration. Axisymmetric, eight-node quadrilateral for arbitrary loading, Hermann formulation. Isoparametric, three-node truss element. Eight-node axisymmetric with twist, Hermann formulation. Eight-node axisymmetric with twist. Elastic, four-node shear panel. Quad8
E_57
Hex20
E_58
Quad8
E_59
Quad8
E_60
Quad8
E_61
Hex20
E_63
Quad8
E_64
Bar3
E_66
Quad8
E_67
Quad8
E_68
Quad4
793

Altair Engineering
Supported Cards
Solver Description
Notes
E_69
Heat transfer element (eightnode planar, biquadratic quadrilateral with reduced integration). Heat transfer element (eightnode, biquadratic quadrilateral with reduced integration). Axisymmetric, eight-node quadrilateral for arbitrary loading, Hermann formulation with reduced integration. Bilinear thick shell. Thin-walled beam in three dimensions without warping. Incompressible arbitrary quadrilateral plane strain. Incompressible generalized plane strain quadrilateral. Incompressible arbitrary quadrilateral axisymmetric ring. Incompressible axisymmetric torsional quadrilateral. Incompressible, threedimensional arbitrarily distorted cube. Thick, curved, axisymmetric shell. Axisymmetric quadrilateral with bending element. Axisymmetric eight node distorted quadrilateral with bending.
E_70
Quad8
E_74
Quad8
E_75 E_78
Quad4 Bar2
E_80
Quad4
E_81
Quad4
E_82
Quad4
E_83
Quad4
E_84
Hex8
E_89
Bar3
E_95
Quad4
E_96
Quad8
Altair Engineering

794
Supported Cards
Solver Description
Supported Elem Types Bar2
Notes
E_98
Elastic beam with transverse shear. Four-node quadrilateral plane stress, reduced integration with hourglass control. Four-node quadrilateral plane strain, reduced integration with hourglass control. Four-node quadrilateral axisymmetric, reduced integration with hourglass control. Eight-node, three dimensional brick, reduced integration with hourglass control. Incompressible 4+1 node, quadrilateral, plane strain, reduced integration with hourglass control. Incompressible 4+1 node, quadrilateral, axisymmetric, reduced integration with hourglass control.
E_114
Quad4
E_115
Quad4
E_116
Quad4
E_117
Hex8
E_118
Quad4
E_119
Quad4
E_120
Incompressible 8+1 node, three- Hex8 dimensional brick, reduced integration with hourglass control. Six-node, plane stress triangle. Six-node, plane strain triangle. Six-node, axisymmetric triangle. Ten-node, tetrahedron. Tria6 Tria6 Tria6
E_124 E_125 E_126
E_127
Tetra10
795

Altair Engineering
Supported Cards
Solver Description
Supported Elem Types Tria6
Notes
E_128
Incompressible, six-node triangle. Incompressible, six-node triangle. Incompressible, ten-node tetrahedron. Four-node, tetrahedral. Three node, thin shell. Four-node, thin shell. Four-node, thick shell, reduced integration with hourglass control.
E_129
Tria6
E_130
Tetra10
E_134 E_138 E_139 E_140
Tetra4 Tria3 Quad4 Quad4
E_149 E_157
Hex8 4+1-node, three dimensional, Tetra4 low order, tetrahedron, Hermann formulations. Spring Mass
E-195
MASSES RBE2 RBE3 SPRING TYING tying100
Mass Rigid RBE3 Spring Rigid Rigid
Nastran
Altair Engineering

796
Supported Cards
Solver Description
Notes
CAABSF
Defines a frequency-dependent Mass acoustic absorber element in coupled fluid-structural analysis. Rod Tria3 Quad4
CAERO1
Defines an aerodynamic macro Quad4 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. Defines aerodynamic slender body and interference elements for Doublet-Lattice aerodynamics. Rod
CAERO2
CBAR CBEAM CBEND
Defines a simple beam element. Bar Defines a beam element. Defines a curved beam, curved pipe, or elbow element. Defines a generalized springand-damper structural element that may be nonlinear or frequency dependent. Defines the connectivity of a one-dimensional spring and viscous damper element. Defines a scalar damper element. Bar Bar
CBUSH
Mass Spring
Both elements with grounded terminals are supported
CBUSH1D
Mass Spring Mass Spring
Both elements with grounded terminals are supported Elements CDAMP1 and CDAMP2 with grounded terminals are not supported. Elements CDAMP1 and CDAMP2 with
CDAMP1
CDAMP2
Defines a scalar damper element without reference to a
Mass Spring
797

Altair Engineering
Supported Cards
Solver Description
Notes
material or property entry.
grounded terminals are not supported. Mass Spring Elements CDAMP1 and CDAMP2 with grounded terminals are not supported. Elements CDAMP1 and CDAMP2 with grounded terminals are not supported.
CDAMP3
Defines a scalar damper element that is connected only to scalar points.
CDAMP4
Defines a scalar damper element that connected only to scalar points and without reference to a material or property entry.
Mass Spring
CELAS1
Defines a scalar spring element. Mass Spring
Elements CDAMP1 and CDAMP2 with grounded terminals are not supported. Elements CDAMP1 and CDAMP2 with grounded terminals are not supported. Elements CDAMP1 and CDAMP2 with grounded terminals are not supported. Elements CDAMP1 and CDAMP2 with grounded terminals are not supported
CELAS2
Defines a scalar spring element without reference to a property entry.
Mass Spring
CELAS3
Defines a scalar spring element that connects only to scalar points.
Mass Spring
CELAS4
Defines a scalar spring element Mass that is connected only to scalar Spring points, without reference to a property entry. Defines a fastener with material orientation connecting two surface patches. Defines a gap or friction element. Defines the acoustic absorber element in coupled fluidstructural analysis. Mass Rod
CFAST
CGAP
Gap
CHACAB
Hex8
Altair Engineering

798
Supported Cards
Solver Description
Notes
CHBDYE
Defines a boundary condition surface element with reference to a heat conduction element. Defines a second order solid element, composed of 6 quadrilateral faces. Hex20
This element is supported as GROUP. In Nastran, you can define a second order element with missing mid-side nodes. Input data decks containing such elements are read by the translator as a first-order element. A message is written to the nastran.msg file indicating the corresponding element ID.
CHEXA (20-noded)
CHEXA (8-noded)
Defines a first order solid element, composed of 6 quadrilateral faces.
Hex8
CMASS1
Defines a scalar mass element. Mass Spring
CMASS2
Defines a scalar mass element without reference to a property entry.
Mass Spring
CMASS3
Defines a scalar mass element Mass that is connected only to scalar Spring points. Defines a scalar mass element Mass that is connected only to scalar Spring points, without reference to a property entry. Defines a 6 x 6 symmetric Mass mass matrix at a geometric grid point. Defines a concentrated mass at Mass
CMASS4
CONM1
CONM2
799

Altair Engineering
Supported Cards
Solver Description
Notes
a grid point. CONROD Defines a rod element without reference to a property entry. Defines the connections of a five-sided solid element with six to fifteen grid points. Defines the connections of a five-sided solid element with six to fifteen grid points. Rod
CPENTA (6-noded)
Penta6
CPENTA (15-noded)
Penta15
In Nastran, you can define a second order element with missing mid-side nodes. Input data decks containing such elements are read by the translator as a first-order element. A message is written to the nastran.msg file indicating the corresponding element ID.
CQUAD4
Defines an isoparametric membrane-bending or plane strain quadrilateral plate element. Defines a curved quadrilateral shell or plane strain element with eight grid points.
Quad4
CQUAD8
Quad8
CQUADR
Defines an isoparametric
Quad4
Altair Engineering

800
Supported Cards
Solver Description
Notes
membrane and bending quadrilateral plate element. However, this element does not include membrane-bending coupling. This element is less sensitive to initial distortion and extreme values of Poissons ratio than the CQUAD4 element. It is a companion to the CTRIAR element. CROD Defines a tension-compression- Rod torsion element. Defines a shear panel element. Quad4 Rod Defines the connections of the four-sided solid element with four grid points. Tetra4
CSHEAR CSEAM CTETRA (4-noded)
CTETRA (10-noded)
Defines the connections of the Tetra10 four-sided solid element with ten grid points.
CTRIA3
Defines an isoparametric membrane-bending or plane strain triangular plate element.
Tria3
CTRIA6
Defines a curved triangular shell Tria6 element or plane strain with six grid points.
In Nastran, you can define a second order element with missing
801

Altair Engineering
Supported Cards
Solver Description
Notes
mid-side nodes. Input data decks containing such elements are read by the translator as a first-order element. A message is written to the nastran.msg file indicating the corresponding element ID. CTRIAR Defines an isoparametric Tria3 membrane-bending triangular plate element. However, this element does not include membrane-bending coupling. It is a companion to the CQUADR element. Defines a tension-compression- Rod torsion tube element. Defines a viscous damper element. Spring Elements CDAMP1 and CDAMP2 with grounded terminals are not supported. Node-Node, NodePatch, or PatchPatch weld elements can be read. CWELD element is stored as an element of the rod configuration. CWELD elements using the ELEMID option not created in HyperMesh will be displayed as zero length. Currently, the spotweld panel can only create Node-Node and
CTUBE
CVISC
CWELD
Defines a weld or fastener Mass connecting two surface patches Rod or points.
Altair Engineering

802
Supported Cards
Solver Description
Notes
Patch-Patch CWELD elements. HyperMesh always calculates the location of GA and GB by projecting GS in the normal direction of surface patch A and surface patch B, respectively. GENEL HM_SPRING Defines a general element. RBE3
Defines a spring element, which Spring is converted to Nastran entities on export, in a manner similar to that explained in Using HM_ELAS. Defines a bolt for use in SOL 600 in countries outside the USA. Defines a bolt for use only in SOL 600 and only in the USA. Defines a one-dimensional dummy element for use in plotting. Mass
MBOLT
MBOLTUS
Mass
PLOTEL
Plot
RBAR
Defines a rigid bar with six Weld degrees-of-freedom at each end.
RBAR CNA field defaults to 123456. To edit the CNA, CNB, CMA, or CMB fields, you must view the card image for the RBAR element.
803

Altair Engineering
Supported Cards
Solver Description
Notes
RBE2
Defines a rigid body with Rigid independent degrees-of-freedom Rigidlink that are specified at a single grid point and with dependent degrees-of-freedom that are specified at an arbitrary number of grid points.
An RBE2 element with one dependent node is identified as a rigid element, while an element with multiple dependent nodes is identified as a rigid link element. Individual weight factors can be created on the independent nodes of RBE3 using the update functionality in the RBE3 panel. See the on-line help for the RBE3 panel for more information. RBE2
RBE3
Defines the motion at a RBE3 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.
PAM-CRASH 2G
The component of the element refers to a material, which contains the material definition for PAM-CRASH 2G . To change an element type, use the Elem Types panel. Edit the elements in the card previewer to determine the element types that require additional information beyond element connectivity. FE input reader will not create connectors for Plinks, instead you must use the FE absorb functionality to create connectors from PLINKs.
Supported Cards
Solver Description
Supported Elem Types Rigids
Notes
ASSOCIATE
Defines entities to be converted from deformable to rigid.
Altair Engineering

804
BAR / BASE_BODY
Bar element. Rigid bodies on which the boundary conditions are defined, used in Multibody systems. Beam element.
Rod Rigid
BEAM /
Bar2
If the orientation vector is defined via vectors, the string VECTOR is displayed in the N3 field, and a zero is written in the exported deck. If the y-direction node is directly specified, its ID is displayed in the N3 field.
BSHEL / EDG ELINK /
8-noded brick shell element.
Hex8 Rod
Link element.
Rod
The element must be edited in the card previewer to define the connections. The element must be edited in the card previewer to define element orientation. The element must be edited in the card previewer to define element orientation. The element must be edited in the card previewer to define the connections.
JOINT /
Joint element.
Rod
KJOIN /
Kinematic joint element.
Rod
LLINK /
Link element.
Rod
MASS MEMBR /
Added mass. Membrane element.
Mass Tria3
805

Altair Engineering
MEMBR / MTOCO NODCO / Rigid element. Nodal constraint definition.
Quad4 Rigid Rigid This configuration allows you to create nodal constraints via entity sets. The element must be edited in the card previewer. Degrees of freedom are ignored. The element must be edited in the card previewer. Mass value is ignored. Use the following templates to handle the welds: find_welds find_master_com ps_welds find_slave_comp s_welds find_comps_weld s. These elements are created during connector realization to show the actual connections. They are not exported. The element must be edited in the card previewer. Mass value is ignored. When created, the default value for rigid body type is 1. This configuration allows you to create rigid bodies via entity sets. The element
PLINK /
Plink element.
Mass
PLINK_VI
Rod
RETRA /
Mass
RBODY /
Rigid body with 2 nodes.
Weld
RBODY /
Rigid
Altair Engineering

806
must be edited in the card previewer. Degrees of freedom are ignored. SEG SEG Tria3 Quad4 The elements are used in entity selection. With this keyword, only nodes of these elements are output along with SEG keyword.
SENPT / SHELL / Shell element.
Mass Mass Mass value is ignored. Mass defined with a keyword other than NOD is not supported. The reader creates one mass element for each NOD definition in the MASS card, therefore the exported deck will contain the same number of MASS/ cards as many NOD definitions. The default behavior for tria3 elements is Coo triangles. To output standard triangles (N3 = N4).
SHELL /
Tria3
SHELL / SLINK / SLINK /
Quad4 Tria3 Quad4 The element must be edited in the card previewer to define the connections. The element must be edited in the card
SLIPR /
Mass
807

Altair Engineering
previewer. Mass value is ignored. SOLID / SOLID / SOLID / SOLID / SPH / SPRING / Spring element. 8-noded brick element. Tetra4 Pyramid5 Penta6 Hex8 Mass Spring The element must be edited in the card previewer to define element orientation. The element must be edited in the card previewer to define element orientation. Local frame definition
SPRGBM /
Spring beam element.
Spring
TETRA / TETR4 / TSHEL /
10-noded tetra element. 4-noded tetra element. 4-noded thick shell element.
Tetra10 Tetra4 Quad4
The element must be edited in the card previewer to define the connections.
PERMAS
The following cards are supported in the PERMAS interface:
Supported Cards
Solver Description
Supported Elem Types Bar2 Bar2
Notes
BEAM2 BECOC
2 noded straight general beam. 2 noded straight thin-walled tube.
Altair Engineering

808
Supported Cards
Solver Description
Supported Elem Types Bar2 Tria3
Notes
BECOS CONA3
2 noded straight solid beam. 3 noded triangular surface convection and radiation element. 4 noded quadrilateral surface convection and radiation element. 6 noded triangular surface convection and radiation element. 8 noded quadrilateral surface convection and radiation element. 3 noded triangular shell surface convection and radiation element.
CONA4
Quad4
CONA6
Tria6
CONA8
Quad8
CONS3
Tria3
CONS4
4 noded quadrilateral shell Quad4 surface convection and radiation element. 6 noded triangular shell surface convection and radiation element. Tria6
CONS6
CONS8
8 noded quadrilateral shell Quad8 surface convection and radiation element. Translational viscous damper. Viscous damper for three degrees of freedom. Spring Spring
DAMP1 DAMP3
DAMP6
Viscous damper for six degrees Spring of freedom. 2 noded straight flange (rod). Rod
FLA2
809

Altair Engineering
Supported Cards
Solver Description
Supported Elem Types Bar3 Hex8 Hex20 Penta6 Penta15 Pyramid5 Tetra4 Tetra10
Notes
FLA3 FLHEX8 FLHEX20 FLPENT6 FLPENT15 FLPYR5 FLTET4 FLTET10 FSINTA3
3 noded straight flange (rod). 8 noded fluid hexahedron. 20 noded fluid hexahedron. 6 noded fluid pentahedron. 15 noded fluid pentahedron. 5 noded fluid pyramid. 4 noded fluid tetrahedron. 10 noded fluid tetrahedron.
3 noded triangular fluid structure Tria3 interface element. 4 noded quadrilateral fluid structure interface element. Quad4
FSINTA4
FSINTA6
6 noded triangular fluid structure Tria6 interface element. 8 noded quadrilateral fluid structure interface element. 8 noded solid hexahedron. 20 noded solid hexahedron. 6 noded solid pentahedron. 15 noded solid pentahedron. 8 noded solid hexahedron. 20 noded solid hexahedron. 3 node triangular load carrying membrane element. Quad8
FSINTA8
GKHEX8 GKHEX20 GKPNT6 GKPNT15 HEXE8 HEXE20 LOADA3
Hex8 Hex20 Penta6 Penta15 Hex8 Hex20 Tria3
Altair Engineering

810
Supported Cards
Solver Description
Notes
LOADA4
4 node quadrilateral load carrying membrane element. 6 node triangular load carrying membrane element. 8 node quadrilateral load carrying membrane element. Point mass. Rigid mass. Pairwise identical displacements.
LOADA6
Tria6
LOADA8
Quad8
MASS3 MASS6 MPC JOIN
Mass Mass Rigid For more information on MPC cards and using duplicate ID pools, see the Permas Interface Overview topic. For more information on MPC cards and using duplicate ID pools, see the Permas Interface Overview topic. For more information on MPC cards and using duplicate ID pools, see the Permas Interface Overview topic. For more information on MPC cards and using duplicate ID pools, see the Permas Interface Overview topic.
MPC RIGID
Rigid regions.
Rigid
MPC SAME
Identical corresponding displacements.
Rigid
MPC WLSC
Weighted averaged connection.
RBE3
NLDAMP
Nonlinear translational viscous damper. Nonlinear rotational viscous
Spring
NLDAMPR
Spring
811

Altair Engineering
Supported Cards
Solver Description
Notes
damper. NLSTIFF NLSTIFFR PENTA6 PENTA15 PLOTA3 PLOTA4 Nonlinear translational spring. Nonlinear rotational spring. 6 noded solid pentahedron. 15 noded solid pentahedron. 3 noded triangular plot element. 4 noded quadrilateral plot element. 6 noded triangular plot element. 8 noded quadrilateral plot element. 2 noded straight line plot element. 3 noded straight line plot element. 5 noded solid pyramid. 4 noded quadrilateral shell element. 4 noded quadrilateral plane membrane element. 4 noded quadrilateral plane shear panel element. Spring Spring Penta6 Penta15 Tria3 Quad4
PLOTA6 PLOTA8
Tria6 Quad8
PLOTL2
Plot
PLOTL3
Bar3
PYRA5 QUAD4
Pyramid5 Quad4
QUAM4
Quad4
SHEAR4
Quad4
SHELL3
3 noded triangular shell element Tria3 for laminates. 4 noded quadrilateral shell element for laminates. Quad4
SHELL4
Altair Engineering

812
Supported Cards
Solver Description
Supported Elem Types Spring Spring
Notes
SPRING1 SPRING3
Translational spring. Spring with three translational stiffnesses. Spring with three translational and three rotational stiffnesses. 4 noded solid tetrahedron. 10 noded solid tetrahedron. 3 noded triangular shell element. 3 noded triangular thin shell element. 3 noded triangular plane membrane element. 6 noded triangular plane membrane element. 6 noded triangular solid shell element. Scalar viscous damper at one node with three degrees of freedom. Scalar viscous damper at one node with six degrees of freedom. General element at one node with six degrees of freedom. Scalar mass at two nodes with three degrees of freedom. Scalar mass at one node with six degrees of freedom.
SPRING6
Spring
TET4 TET10 TRIA3
Tetra4 Tetra10 Tria3
TRIA3K
Tria3
TRIM3
Tria3
TRIM6
Tria6
TRIMS6
Tria6
X1DAMP3
Mass
X1DAMP6
Mass
X1GEN6
Mass
X1MASS3
Mass
X1MASS6
Mass
813

Altair Engineering
Supported Cards
Solver Description
Supported Elem Types Mass
Notes
X1STIFF3
Scalar spring at one node with three degrees of freedom. Scalar spring at one node with six degrees of freedom. Scalar viscous damper at two nodes with three degrees of freedom. Scalar viscous damper at two nodes with six degrees of freedom. General element at two nodes with six degrees of freedom. Scalar spring at two nodes with three degrees of freedom. Scalar spring at two nodes with six degrees of freedom.
X1STIFF6
Mass
X2DAMP3
Spring
X2DAMP6
Spring
X2GEN6
Mass
X2STIFF3
Spring
X2STIFF6
Spring
Samcef
The following cards are supported in the HyperMesh Samcef interface: Supported Cards Solver Description Supported Elem Types Pyramid5, Penta6, Hex8, Pyramid13, Penta15, Hex20 Rod, Tria3, Quad4, Tria6, Quad8 Bar2, Rod, Tria3, Quad4, Tria6, Quad8 Tria3, Tria6 Notes
COMPVOL
FLUXTHE
HYBRVOLU
MEMBRANE
Altair Engineering

814
Supported Cards
Solver Description
Supported Elem Types Bar2, Rod, Tria3, Quad4, Tetra4, Pyramid5, Penta6, Hex8, Tria6, Quad8, Tetra10, Pyramid13, Penta15, Hex20 Rod, Tria3, Quad4, Tria6, Quad8 Rod, Tria3, Quad4, Tetra4, Pyramid5, Penta6, Hex8, Tria6, Quad8, Tetra10, Pyramid13, Penta15, Hex20 Rod Rod, Tria3, Quad4, Tria6, Quad8
Notes
MINDLIN
THERM CO
THERMIQU
TUYAU VOLUMIC
See also Include Files Assemblies Components
815

Altair Engineering
Bar2
Bar2 elements are 1D (1st order) elements with 2 nodes used to model axial, bending, and torsion behavior. Bar2 elements have a property reference, an orientation vector, offset vectors and ends A and B, and pin flags at ends A and B. The following panels can be used to create and edit bar2 elements: Bars Split Detatch Config Edit Elem Types
The data names associated with bar2 elements can be found in the data names section of the HyperMesh Reference Guide.
See also Include Files Assemblies Components Elements
Altair Engineering

816
Bar3
Bar3 elements are 1D (2nd order) elements with 3 nodes used to model axial, bending, and torsion behavior. Bar3 elements have a property reference, an orientation vector, offset vectors and ends A and B, and pin flags at ends A and B. The following panels can be used to create and edit bar3 elements: Bars Split Detatch Config Edit Elem Types
The data names associated with bar3 elements can be found in the data names section of the HyperMesh Reference Guide.
817

Altair Engineering
Gap
Gap elements are 1D elements with 2 nodes used to model gaps and contact. Gap elements have a property reference and an orientation vector. The following panels can be used to create and edit gap elements: Gaps Connectors Config Edit Elem Types
The data names associated with gap elements can be found in the data names section of the HyperMesh Reference Guide.
See also Include Files Assemblies Components Elements Connectors
Altair Engineering

818
Hex8
Hex8 elements are 3D (1st order) hexahedra elements with 8 nodes ordered in HyperMesh as shown below.
The following panels can be used to create and edit hex8 elements: Solid Map Shrink Wrap Elem Offset Edit Element Split Detatch Order Change Config Edit Elem Types
The data names associated with hex8 elements can be found in the data names section of the HyperMesh Reference Guide.
819

Altair Engineering
Hex20
Hex20 elements are 3D (2nd order) hexahedra elements with 20 nodes ordered in HyperMesh as shown below.
The following panels can be used to create and edit hex8 elements: Solid Map Shrink Wrap Elem Offset Edit Element Split Detatch Order Change Config Edit Elem Types The data names associated with hex20 elements can be found in the data names section of the HyperMesh reference guide.
Altair Engineering

820
Joint
Joint elements are elements with 2, 4, or 6 nodes which have a property and orientation systems or nodes. A joint element does not allow types other than specified below. The type of the element controls the number of nodes used in the element and the permissible orientations of the element. Type 1 2 3 4 5 6 7 Type Name Spherical Revolute Cylindrical Planar Universal Translational Locking # nodes 2 4 4 4 4 6 6 Orientation none/systems/nodes none/systems none/systems none/systems none/systems none/systems none/systems
The following panels can be used to create and edit joint elements: FE Joints Connectors Config Edit Elem Types
The data names associated with joint elements can be found in the data names section of the HyperMesh Reference Guide.
821

Altair Engineering
Mass
Mass elements are 0D elements with a single node that allow you to assign concentrated mass to the model in order to represent physical part that may not be modeled with another FE idealization. The following panels can be used to create and edit mass elements: Masses SPH Apply Mass Config Edit Elem Types
The data names associated with mass elements can be found in the data names section of the HyperMesh Reference Guide.
Altair Engineering

822
Master3
Master3 elements are master interface elements with 3 nodes. (Must be Type 1) The following panels can be used to create and edit master3 elements: Interfaces
The data names associated with master3 elements can be found in the data names section of the HyperMesh Reference Guide.
823

Altair Engineering
Master4
Master4 elements are master interface elements with 4 nodes. (Must be Type 1) The following panels can be used to create and edit master4 elements: Interfaces
The data names associated with master4 elements can be found in the data names section of the HyperMesh Reference Guide.
Altair Engineering

824
Penta6
Penta6 elements are 3D (1st order) triangular prism pentahedra elements with 6 nodes ordered in HyperMesh as shown below.
The following panels can be used to create and edit penta6 elements: Elem Offset Edit Element Split Detatch Order Change Config Edit Elem Types
The data names associated with penta6 elements can be found in the data names section of the HyperMesh Reference Guide.
825

Altair Engineering
Penta15
Penta15 elements are 3D (2nd order) triangular prism pentahedra elements with 15 nodes ordered in HyperMesh as shown below.
The following panels can be used to create and edit penta15 elements: Elem Offset Edit Element Split Detatch Order Change Config Edit Elem Types
The data names associated with penta15 elements can be found in the data names section of the HyperMesh Reference Guide.
Altair Engineering

826
Plot
Plot elements are 1D elements with 2 nodes used for display purposes. The following panels can be used to create and edit plot elements: Spot Connectors Config Edit Elem Types The data names associated with plot elements can be found in the data names section of the HyperMesh Reference Guide.
See also Include Files Assemblies Components Connectors Elements
827

Altair Engineering
Pyramid5
Pyramid5 elements are 3D (1st order) pyramid pentahedra elements with 5 nodes ordered in HyperMesh as shown below.
The following panels can be used to create and edit pyramid5 elements: Elem Offset Edit Element Split Detatch Order Change Config Edit Elem Types
The data names associated with pyramid5 elements can be found in the data names section of the HyperMesh Reference Guide.
Altair Engineering

828
Pyramid13
Pyramid13 elements are 3D (2nd order) pyramid pentahedra elements with 5 nodes ordered in HyperMesh as shown below.
The following panels can be used to create and edit pyramid13 elements: Elem Offset Edit Element Split Detatch Order Change Config Edit Elem Types
The data names associated with pyramid13 elements can be found in the data names section of the HyperMesh Reference Guide.
829

Altair Engineering
Quad4
Quad4 elements are 2D (1st order) quadrilateral elements with 4 nodes ordered in HyperMesh as shown below.
The following panels can be used to create and edit quad4 elements: Automesh Shrink Wrap Elem Offset Quality Index Elem Cleanup Edit Element Split Detatch Order Change Config Edit Elem Types
The data names associated with quad4 elements can be found in the data names section of the HyperMesh Reference Guide.
Altair Engineering

830
831

Altair Engineering
Quad8
Quad8 elements are 2D (2nd order) quadrilateral elements with 8 nodes ordered in HyperMesh as shown below.
The following panels can be used to create and edit quad8 elements: Automesh Shrink Wrap Elem Offset Quality Index Elem Cleanup Edit Element Split Detatch Order Change Config Edit Elem Types
The data names associated with quad8 elements can be found in the data names section of the HyperMesh Reference Guide.
Altair Engineering

832
RBE3
RBE3 elements are rigid elements with one dependent node and variable independent nodes typically used to define the motion at the dependent node as a weighted average of the motions at the independent nodes. Both the dependent node and independent nodes contain a coefficient (weighting factor) and user-defined degrees of freedom. The following panels can be used to create and edit quad8 elements: RBE3 Config Edit Elem Types
The data names associated with RBE3 elements can be found in the data names section of the HyperMesh Reference Guide.
833

Altair Engineering
Rigid
Rigid elements are rigid 1D elements with 2 nodes used to model rigid connections. The following panels can be used to create and edit rigid elements: Rigid Spot Weld Spot
The data names associated with rigid elements can be found in the data names section of the HyperMesh Reference Guide.
Altair Engineering

834
Rigidlink
Rigidlink elements are rigid elements with one independent node and variable dependent nodes typically used to model rigid bodies. Rigidlink elements have user-defined degrees of freedom which apply to all dependent nodes. The following panels can be used to create and edit rigidlink elements: Rigids Config Edit Elem Types
The data names associated with rigidlink elements can be found in the data names section of the HyperMesh Reference Guide.
835

Altair Engineering
Rod
Rod elements are 1D elements with 2 nodes used to model axial behavior only. Rod elements have a property reference. The following panels can be used to create and edit rod elements: Rods Split Detatch Config Edit Elem Types
The data names associated with rod elements can be found in the data names section of the HyperMesh Reference Guide.
Altair Engineering

836
Slave1
Slave1 elements are slave interface elements with 1 node. (Must be Type 1) The following panels can be used to create and edit slave1 elements: Interfaces
The data names associated with slave1 elements can be found in the data names section of the HyperMesh Reference Guide.
837

Altair Engineering
Slave3
Altair Engineering

838
Slave4
839

Altair Engineering
Spring
Spring elements are 1D elements with 2 nodes used to model spring connections. Spring elements have user-defined degrees of freedom, an orientation vector, and a property reference. The following panels can be used to create and edit spring elements: Springs Split Detatch Config Edit Elem Types
The data names associated with spring elements can be found in the data names section of the HyperMesh Reference Guide.
Altair Engineering

840
Tetra4
Tetra4 elements are 3D (1st order) tetrahedra elements with 4 nodes ordered in HyperMesh as shown below.
The following panels can be used to create and edit tetra4 elements: Tetramesh Elem Offset Edit Element Split Detatch Order Change Config Edit Elem Types
The data names associated with tetra4 elements can be found in the data names section of the HyperMesh Reference Guide.
841

Altair Engineering
Tetra10
Tetra10 elements are 3D (2nd order) tetrahedra elements with 10 nodes ordered in HyperMesh as shown below.
The following panels can be used to create and edit tetra4 elements: Tetramesh Elem Offset Edit Element Split Detatch Order Change Config Edit Elem Types
The data names associated with tetra10 elements can be found in the data names section of the HyperMesh Reference Guide.
Altair Engineering

842
Tria3
Tria3 elements are 2D (1st order) triangular elements with 3 nodes ordered in HyperMesh as shown below.
The following panels can be used to create and edit tria3 elements: Automesh Elem Offset Quality Index Elem Cleanup Edit Element Split Detatch Order Change Config Edit Elem Types
The data names associated with tria3 elements can be found in the data names section of the HyperMesh Reference Guide.
843

Altair Engineering
Tria6
Tria6 elements are 2D (2nd order) triangular elements with 6 nodes ordered in HyperMesh as shown below.
The following panels can be used to create and edit tria6 elements: Automesh Elem Offset Quality Index Elem Cleanup Edit Element Split Detatch Order Change Config Edit Elem Types
The data names associated with tria6 elements can be found in the data names section of the HyperMesh Reference Guide.
Altair Engineering

844
Weld
Weld elements are rigid 1D elements with 2 nodes used to model welded connections. The following panels can be used to create and edit weld elements: Spot Weld Spot
The data names associated with weld elements can be found in the data names section of the HyperMesh Reference Guide.
845

Altair Engineering
Connectors
Connectors are geometric entities (not FE) used to create connections between link entities. Assemblies, components, elements, surfaces, nodes, and tags may act as link entities. Connectors are used to realize FE idealizations of the physical connection between the link entities. Just as you create a FE elements on a surface, you create FE connections by realizing a connector. The following panels can be used to create and edit connectors: Connectors
See also Include Files Assemblies Components Connectors
Altair Engineering

846
Load Collectors
Load collectors collect and organize loads and equations. Load collectors are created, edited, and deleted from the Model Browser and are shown under the LoadCollector folder. Loads and equations can be organized into a load collector using the Organize panel. Every load and equation must be organized into one, and only one, load collector and therefore are mutually exclusive to a load collector. Newly created loads and equations are automatically organized into the current load collector. The current load collector is shown in the status bar and is also bold in the Model Browser. The current load collector can be set using the Model Browser context sensitive menu on a selected load collector within the LoadCollector folder. Load collectors can also be card edited using the Model Browser context sensitive menu on selected load collectors within the LoadCollector folder. Load collectors have a display state, on or off, which control the display of all loads and equations organized within the load collector in the graphics area. The display state of a load collector can be controlled using the icons next to the load collector in the Model Browser. Geometry and element display states can be controlled separately for load collectors. Load collectors also have an active and export state. The active state of a load collector controls the display state of the load collector and the listing of the load collector in the Model Browser and any of its views. If a load collector is active, then its display state is available to be turned on or off and it is listed in the Model Browser and any of its views. If a load collector is inactive, then its display state is turned off permanently and it is not listed in the Model Browser or any of its views. If a find operation "finds" an inactive load collector, that load collector will automatically be set to active. The export state of a load collector controls whether or not that load collector and all loads and equations organized within the load collector are exported when the custom export option is utilized. The all export option is not affected by the export state of a load collector. The active and export states of load collectors can be controlled using the Entity State Browser. Operations performed on a load collector affect loads and equations within the load collector. For example, if you delete a load collector, the loads and equations within the load collector are also deleted. The data names associated with load collectors can be found in the data names section of the HyperMesh Reference Guide.
847

Altair Engineering
Solver Card Support for Load Collectors

When working with RADIOSS (Block Format), HyperMesh requires that all the loads be placed in the load collectors with one of the following valid card images:
Altair Engineering

848
Supported Cards
Solver Description
Notes
/ACTIV
Describes the deactivation/ activation of element groups. Describes the ALE boundary conditions. Defines boundary conditions. ALE_BCS_option RADIOSS_COMMENT _FLAG Translation_Vx Translation_Vy Translation_Vz Rotation_Wx Rotation_Wy Rotation_Wz
/ALE/BCS
/BCS
/CLOAD
Describes the concentrated loads.
GRNodeBox RADIOSS_COMMENT _FLAG Surface Type (Sets, ContactSurfs, Blocks)
/CONVEC
Describes the imposed convective flux. Describes the line detonators Describes the point detonators.
/DFS/DETLINE /DFS/DETPOIN /DFS/LASER /DFS/WAV_SHA /EBCS
Describes the elementary boundary condition sets. Describes the gravity load. GRNodeBox RADIOSS_COMMENT _FLAG
/GRAV
/IMPACC
Describes the imposed accelerations.
GRNodeBox RADIOSS_COMMENT
849

Altair Engineering
Supported Cards
Solver Description
Supported Parameters _FLAG
Notes
/IMPDISP
Describes the imposed displacements. Defines imposed temperatures on a group of nodes. Describes the imposed velocities. Describes the initial nodal temperature. Describes the initial velocities. Describes the initial velocities around the axis. Describes the pressure loads. Describes the SPH symmetry conditions. Describes the SPH inlet/outlet conditions.
/IMPTEMP
/IMPVEL
/INITEMP
/INIVEL /INIVEL/AXIS
/PLOAD /SPHBCS
/SPH/INOUT
There are two choices for assigning loads to a load collector: Create individual loads, all of the same type and degree of freedom, and store them in the appropriate load collector. Identify the nodes on which loads/BCs act by selecting them through a set. The selection of the set is possible by editing the card image of the load collector. RADIOSS (Bulk Data Format), OptiStruct
Specific load collectors are used for specialized loading cards, such as EIGRL, SPCADD, GRAV, RLOAD, DTABLEi, etc. Specific load collectors have card images, which can be edited to do the following: Group other load collectors together for simultaneous application in a single subcase. Provide special information for a specific analysis type (such as modal analysis, or frequency
Altair Engineering

850
response analysis). General boundary conditions should not be collected into specific load collectors. Organizing loads and constraints into a specific load collector may result in an error termination. The following is a list of RADIOSS (Bulk Data Format), OptiStruct cards, which are represented as specific load collectors. Supported Cards Solver Description Supported Parameters DELAY_OPTION DPHASE_OPTION Notes
ACSRCE
Defines acoustic source as a function of power vs. frequency.
CMSMETH
Defines the method, frequency TYPE (Structure Only, upper limit, and number of Fluid Structure) modes to be used in component mode synthesis for flexibly-body preparation solution sequence. Defines a dynamic loading condition for frequency response problems as a linear combination of load sets defined via RLOAD1 and RLOAD2 entries, or for transient problems as a linear combination of load sets defined via TLOAD1 and TLOAD2 entries. Correlates spectra lines specified on TABLED1 entries with damping values. Defines data needed to perform complex eigenvalue analysis. Defines data needed to perform real eigenvalue analysis (vibration or buckling) with the Lanczos Method. Defines elements, and associated fatigue properties, for consideration in a fatigue analysis. ELSET PSHELL PSOLID XELSET
DLOAD
DTI_SPECSEL
EIGC
EIGRL
FATDEF
851

Altair Engineering
Supported Cards
Solver Description
Supported Parameters XELEM
Notes
FATEVNT
Defines loading events for fatigue analysis. Defines fatigue loading parameters. Defines fatigue analysis parameters. Defines a loading sequence for fatigue analysis. Defines a set of frequencies to be used in the solution of frequency response problems. FATSEQ_NUM FATEVNT_NUM_FLOA D
FATLOAD
FATPARM
FATSEQ
FREQ
FREQ FREQ1 - FREQ5 Defined using FREQi
FREQ1
Defines a set of frequencies to FREQ be used in the solution of FREQ1 - FREQ5 frequency response problems by specification of a starting frequency, frequency increment, and the number of increments desired. Alternative form of frequency FREQ list. Defines a set of frequencies FREQ1 - FREQ5 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. Frequency List, Alternate Form FREQ 3. Defines a set of frequencies FREQ1 - FREQ5 for the modal method of frequency response analysis by specifying the number of frequencies between modal frequencies. Frequency List, Alternate Form 4. Defines a set of frequencies FREQ
FREQ2
Defined using FREQi
FREQ3
Defined using FREQi
FREQ4
Defined using FREQi
Altair Engineering

852
Supported Cards
Solver Description
Notes
for the modal method of FREQ1 - FREQ5 frequency response analysis by specifying the amount of "spread" around each modal frequency and the number of equally spaced frequencies within the spread. FREQ5 Frequency List, Alternate Form FREQ 5. Defines a set of frequencies FREQ1 - FREQ5 for the modal method of frequency response analysis by specification of a frequency range and fractions of the natural frequencies within that range. Defines the gravity vectors for use in determining gravity loading for the structural model. Defines initial velocity in a multibody situation. Defines a static load as a linear LOAD_Num_Set combination of load sets defined via FORCE, MOMENT, FORCE1, MOMENT1, PLOAD, PLOAD1, PLOAD2, PLOAD4, RFORCE, and GRAV entries. Defines the entity/set to be activated in the multi-body system for the subsequent simulation. Defines the entity/set to be deactivated in the multi-body system for the subsequent simulation. Defines the parameters for a multi-body system linear analysis. THRU MBACT_NUMIDS Defined using FREQi
GRAV
INVELB
LOAD
MBACT
MBDEACT
THRU MBEACT_NUMIDS
MBLIN
853

Altair Engineering
Supported Cards
Solver Description
Supported Parameters MBSEQ_NUM_ID
Notes
MBSEQ
Defines the simulation sequence for the multi-body solver. Defines the parameters for a multi-body simulation.
MBSIM
Simulation Type (Transient, Static, Quasi-static)
MBSIMP
Parameters for subsequent multi-body simulation. Defines a multi-body as a linear MLOAD_NUM_L combination of load sets defined via GRAV, MBFRC, MBFRCC, MBFRCE, MBMNT, MBMNTC, MBMNTE, MBSFRC, MBSFRCC, MBSFRCE, MBSMNT, MBSMNTC, MBSMNTE. Defines a multi-body as a combination of motion sets defined via MOTNJ, MOTNJC, MOTNJE, MOTNG, MOTNGC, MOTNGE Multi-point constraint set combination. MOTION_Num_Set
MLOAD
MOTION
MPCADD
Number_Of_Sets
NLOAD
Defines a loading condition for NLOAD_NUM nonlinear problems as a linear combination of load sets defined via NLOAD1. Defines a time-dependent load or enforced motion for use in geometric nonlinear analysis. SENSID_OPTION
NLOAD1
NLPARM
Defines parameters for nonlinear NINC, DT, KMETHOD, static analysis iteration KSTEP, MAXITER, strategy. CONV, INTOUT, EPSU, EPSP, EPSW, MAXDIV, MAXQN, MAXLS, FSTRESS,
Altair Engineering

854
Supported Cards
Solver Description
Supported Parameters LSTOL, MAXBIS, MAXR, RTOLB NLPCI
Notes
NSMADD
Defines non-structural mass as the sum of the sets listed. Defines element properties for fatigue analysis FINISH_REAL TREATMENT_REAL RANDT1
PFAT
RANDPS
Power Spectral Density Specification Defines a static loading condition due to a centrifugal force field. Defines a frequency-dependent dynamic load for use in frequency response problems.
RFORCE
RLOAD1
DELAY_OPTION DPHASE_OPTION
RLOAD2
Defines a frequency-dependent dynamic load for use in frequency response problems.
RSPEC
Defines a directional combination method, modal combination method, excitation direction(s), response spectra and scale factors for response spectrum analysis. Defines a rigid wall set as a union of rigid walls defined via RWALL entries. RWALADD_Num_set
RWALADD
SOLVTYP
Defines the solver to be used for Solver Type (PCG) static analysis.
855

Altair Engineering
Supported Cards
Solver Description
Supported Parameters SPCADD_Num_Set
Notes
SPCADD
Single-point constraint set combination. Defines modal damping as a tabular function of natural frequency. Defines a tabular function for use in generating frequencydependent and time-dependent dynamic loads.
TABDMP1
TABDMP1_NUM
TABLED1
TABLED1_NUM
TABLED2
Dynamic Load Tabular TABLED2_NUM Function, Form 2. Defines a tabular function for use in generating frequency-dependent and time-dependent dynamic loads. Also contains parametric data for use with the table. Dynamic Load Tabular TABLED3_NUM Function, Form 3. Defines a tabular function for use in generating frequency-dependent and time-dependent dynamic loads. Also contains parametric data for use with the table. Dynamic Load Tabular Function, Form 4.Defines the coefficients of a power series for use in generating frequencydependent and time-dependent dynamic loads. Also contains parametric data for use with the table. Defines y values of each point on the loading time history. Defines a tabular function for use in generating temperaturedependent material properties.
TABLED3
TABLED4
TABLEFAT
TABLEM1
Altair Engineering

856
Supported Cards
Solver Description
Notes
TABLEM2
Material Property Table, Form 2. Defines a tabular function for use in generating temperaturedependent material properties. Also contains parametric data for use with the table. Material Property Table, Form 3. Defines a tabular function for use in generating temperaturedependent material properties. Also contains parametric data for use with the table. Material Property Table, Form 4. Defines coefficients of a power series for use in generating temperaturedependent material properties. Also contains parametric data for use with the table. Defines a tabular function for use as stress-strain curve in one-step stamping material property MATHF Defines power spectral density as a tabular function of frequency for use in random analysis. Defines a temperature value for all grid points of the structural model that have not been given a temperature on a TEMP entry. Defines a time-dependent dynamic load or enforced motion of the form: TABLES1_NUM
TABLEM3
TABLEM4
TABLES1
TABRND1
TABRND1_NUM
TEMPD
TLOAD1
for use in transient response analysis.
857

Altair Engineering
Supported Cards
Solver Description
Notes
TLOAD2
Defines a time-dependent dynamic excitation or enforced motion of the form:
for use in a transient response problem, where
TSTEP
Defines time step intervals at which a solution will be generated and output in transient analysis. Defines a time history output set as a union of time history outputs defined via XHIST entries. Defines explicit analysis control. XHISADD_Num_set
XHISADD
XSTEP
XSTEP_NUM
Abaqus
A load collector is a repository for loads and constraints. Each load or constraint must belong to a load collector. There are two card images called HISTORY and INITIAL_CONDITION. Loads or constraints that are to be used as history data (under *STEP) should be collected into load collectors with the HISTORY card image. These load collectors also need to be added to the corresponding load steps (*STEP) from the load steps panel. In contrast, loads or constraints for model data should be collected into load collectors with INITIAL_CONDITION card image. They will automatically be written out in the model portion of the Abaqus input deck. Note The Import tab - Options section provides the user to select to Expand Loads on Sets. Selecting this option means that all loads and boundary conditions on sets are expanded to individual nodes and elements. Solver Description Supported Parameters AMPLITUDE, FILM Notes
Supported Card
*CFILM
Define film coefficients and
Only in HISTORY
Altair Engineering

858
associated sink temperatures at one or more nodes or vertices
AMPLITUDE, REGION card image TYPE = {LAGRANGIAN/ SLIDING, EULEREIAN}, OP AMPLITUDE, LOAD CASE, OP Only in HISTORY card image
*CONNECTOR LOAD Specify loads for available components of relative motion in connector elements *CONNECTOR MOTION Specify the motion of available components of relative motion in connector elements
AMPLITUDE, LOAD CASE, OP
In both HISTORY and INTIAL_CONDITION card image Only in HISTORY card image
*DSLOAD
Specify distributed surface loads
AMPLITUDE, LOAD CASE, CYLIC MODE, OP FIXED, ORIENTATION, REMOVE
*INERTIA RELIEF
Apply inertia-based load balancing
Only in HISTORY card image of Standard template TYPE = FLUID PRESSURE TYPE= TEMPERATURE TYPE=VELOCITY
*INITIAL_CONDITION Specifies initial pressures for S hydrostatic fluid filled cavities. *INITIAL_CONDITION Specifies initial temperatures S for heat transfer analysis. *INITIAL_CONDITION Specifies initial velocities for S dynamic analysis. *SFILM Define film coefficients and associated sink temperatures over a surface for heat transfer analysis AMPLITUDE, FILM AMPLITUDE, OP
Only in HISTORY card image
LS-DYNA
Load collector information is specified with a required $HMNAME comment card and an optional $HMCOLOR comment card. If an input translator encounters one of these comments while reading a load card, a new load collector is created. For the comments to be valid, they must follow a load keyword or the last line of the previous Structured block. The loads that follow a $HMNAME LOADCOLS comment are read into that collector. If there is a new Keyword or Structured block, the previous load
859

Altair Engineering
collector information is ignored. For non-HyperMesh generated input decks, loads are divided into collectors based on classification. The following load collectors are created: Mechanical loads for forces and moments Constraints/Displacements Velocities Accelerations Pressures If translational or rotational constraints are defined in the input model, they are placed in a separate load collector named Nodal Constraints. Load collectors are not used by LS-DYNA, but are useful for visualization. Additional load collectors can be defined to describe other entities. Supported Cards Solver Description Supported Parameters Notes
*BOUNDARY_ CONVECTION_SET
Define convection boundary SSID, HLCID, HMULT, conditions for a thermal or TLCID, TMULT, LOC coupled thermal/structural analysis. Two cards are defined for each option. Define a non-reflecting boundary. Define a non-reflecting boundary. Define an imposed nodal motion (velocity, acceleration, or displacement) on a node or a set of nodes. Define an imposed nodal motion (velocity, acceleration, or displacement) on a node or a set of nodes. SSID, AD, AS 2D_Option NSID
*BOUNDARY_NON_ REFLECTING *BOUNDARY_NON_ REFLECTING_2D *BOUNDARY_ PRESCRIBED_MOTI ON_ RIGID *BOUNDARY_ PRESCRIBED_MOTI ON_ RIGID_ID *BOUNDARY_ PRESCRIBED_MOTI ON_ RIGID_LOCAL
PID, DOF, VAD, LCID, RIGID_LOCAL and SF, VID, DEATH, _SET options are BIRTH supported.
Dyna_Name PID, DOF, VAD, LCID, SF, VID, DEATH, BIRTH PID, DOF, VAD, LCID, SF, VID, DEATH, BIRTH Title
Altair Engineering

860
Supported Cards
Solver Description
Supported Parameters Dyna_Name PID, DOF, VAD, LCID, SF, VID, DEATH, BIRTH
Notes
*BOUNDARY_ PRESCRIBED_MOTI ON_ RIGID_LOCAL_ID *BOUNDARY_ PRESCRIBED_MOTI ON_ SET Define an imposed nodal motion (velocity, acceleration, or displacement) on a node or a set of nodes.
NSID, DOF, VAD, LCID, SF, VID, DEATH, BIRTH TITLE Dyna_Name NSID, DOF, VAD, LCID, SF, VID, DEATH, BIRTH SSID, TYPE, RAD_GRP, FILE_NO, RFLCID, RFMULT, TILCID, TIMULT NSID, CID, DOFX, DOFY, DOFZ, DOFRX, DOFRY, DOFRZ Title
*BOUNDARY_ PRESCRIBED_MOTI ON_ SET_ID
*BOUNDARY_RADIA Defines surface segment sets TION_SET that transfer energy by radiation to the environment.
*BOUNDARY_SPC_ SET
Define nodal single point constraints.
*BOUNDARY_SPC_ SET_ ID
Dyna_Name NSID, CID, DOFX, DOFY, DOFZ, DOFRX, DOFRY, DOFRZ Define temperature boundary conditions for a thermal or coupled thermal/structural analysis. NCID, LCID, CMULT, LOC
*BOUNDARY_ TEMPERATURE_SE T
*CONSTRAINED_RIG Stops the motion based on a ID_ time dependent constraint. The BODY_STOPPERS stopper overrides prescribed motion boundary conditions
PID, LCMAX, LCMIN, PSIDMX, PSIDMN, LCVMNX, DIR, VID, TB, TD
861

Altair Engineering
Supported Cards
Solver Description
Supported Parameters LCMAX_as_displacme nt LCMIN_as_displacem ent
Notes
(except relative displacement) operating in the same direction for both the master and slaved rigid bodies. *DEFINE_CURVE_ FEEDBACK
Define information that is used LCID, PID, BOXID, as the solution evolves to scale FLDID, FSL, TSL, the ordinate values of the SFF, SFT, BIAS specified load curve ID. Title Title, LCID, PID, BOXID, FLDID, FSL, TSL, SFF, SFT, BIAS Select an arraycount for the PSID and MRB pairs.
*DEFINE_CURVE_ FEEDBACK_TITLE
*DEFORMABLE_TO_ Define materials to be switched ArrayCount RIGID to rigid at the start of the PSID, MRB calculation. DeformToRigidHelp Options (NONE, AUTOMATIC) *DEFORMABLE_TO_ Define materials to be switched SWSET, CODE, RIGID to rigid or to deformable at TIME1, TIME2, TIME3, _AUTOMATIC some stage in the calculation. ENTNO, RELSW, PAIRED, NRBF, NCSF, RWF, DTMAX, #D2R, #R2D DeformToRigidHelp D2R_Flag R2D_Flag *DEFORMABLE_TO_ Inertial properties can be RIGID defined for the new rigid bodies _INERTIA that are created when the deformable parts are switched. These can only be defined in the initial input if they are needed in a later restart. PID, XC, YC, ZC, TM, IXX, IXY, IXZ, IYY, IYZ, IZZ
Change the option to automatic and card edit. In the D2R fields enter the number of PIDs that need to be converted to Rigid. Create an entity set of comps of the slave PIDs and select the set.
*INITIAL_AXIAL_FOR Initialize axial force in the beam BSID, LCID CE_ for modeling bolt BEAM
Altair Engineering

862
Supported Cards
Solver Description
Supported Parameters PID, X, Y, Z, LT PartOption
Notes
*INITIAL_DETONATIO Define points to initiate the N location of high explosive detonations in part IDs which use the material (type 8) *MAT_HIGH_EXPLOSIVE_BU RN. *INITIAL_STRESS_ SECTION Initialize stress in solid sections
CSID, LCID, PSID, VID NSID, TEMP, LOC
*INITIAL_TEMPERAT Define initial nodal point URE_ temperatures using nodal set SET IDs or node numbers. *INITIAL_VEHICLE_ KINEMATICS Define initial kinematical information for a vehicle.
GRAV, PSID, XO, YO, ZO, XF, YF, ZF, VX, VY, VZ, AAXIS, BAXIS, CAXIS, AANG, BANG, CANG, WA, WB, WB Card 30 NSID, NSIDEX, BOXID, IRIGID, VX, VY, VZ, VXR, VYR, VZR Options (NONE, Generation, Rigidbody) InitialVel This card changes the INITV definition on Control Card 11. Only the first card defined is valid for Structured.
*INITIAL_VELOCITY
Define initial nodal point translational velocities using nodal set IDs. This may also be used for sets in which some nodes have other velocities.
*INITIAL_VELOCITY_ Define initial velocities for GENERATION rotating and translating bodies.
PSID, OMEGA, VX, VY, VZ, IVATN, XC, YC, ZC, NX, NY, NZ, PHASE STYP (Part Set ID, Part ID, Node Set ID, ENTIRE MODEL)
*INITIAL_VELOCITY_ Define the initial translational PID, VX, VY, VZ, VXR, RIGID_ and rotational velocities at the VYR, VZR BODY center of gravity for a rigid body or a nodal rigid body.
863

Altair Engineering
Supported Cards
Solver Description
Supported Parameters PSID, NSHV, FTYPE Option1 (NONE, LSDYNA, NASTRAN, SEAMLESS) Option2 (None, THICKNESS, NO THICKNESS)
Notes
*INTERFACE_ SPRINGBACK
Define a material subset for an implicit springback calculation in LS-DYNA and any nodal constraint to eliminate rigid body degrees-of-freedom.
*INTERFACE_ SPRINGBACK_LSDY NA
PSID, NSHV, FTYPE Option1 (LSDYNA, NASTRAN, SEAMLESS, NONE) Option2 (None, THICKNESS, NOTHICKNESS)
*INTERFACE_ SPRINGBACK_LSDY NA_ NOTHICKNESS
Define a material subset for an implicit springback calculation in LS-DYNA and any nodal constraints to eliminate rigid body degrees-of-freedom.
PSID, NSHV, FTYPE
*INTERFACE_ SPRINGBACK_LSDY NA_ THICKNESS *INTERFACE_ SPRINGBACK_NAST RAN *INTERFACE_ SPRINGBACK_NAST RAN_ NOTHICKNESS *INTERFACE_ SPRINGBACK_NAST RAN_ THICKNESS
PSID, NSHV, FTYPE
PSID, NSHV, FTYPE
PSID, NSHV, FTYPE
PSID, NSHV, FTYPE
Altair Engineering

864
Supported Cards
Solver Description
Supported Parameters PSID, NSHV, FTYPE
Notes
*INTERFACE_ SPRINGBACK_SEA MLESS *INTERFACE_ SPRINGBACK_SEA MLESS _NOTHICKNESS *INTERFACE_ SPRINGBACK_SEA MLESS _THICKNESS *LOAD_BEAM_SET Defines load on beam element set Define an airblast function for the application of pressure loads due to explosives in conventional weapons. Define body force loads due to a prescribed base acceleration or prescribed angular velocity over a subset of the complete problem.
PSID, NSHV, FTYPE
PSID, NSHV, FTYPE
ESID, DAL, LCID, SF
*LOAD_BLAST
WGT, XBO, YBO, ZBO, TBO, IUNIT, ISURF, CFM, CFL, CFT, CFP Card 46 N1, N2, LCID, DRLCID, XC, YC, ZC, AX, AY, AZ, OMX, OMY, OMZ Card 45 PSID Select component set.
*LOAD_BODY_ GENERALIZED
*LOAD_BODY_PART Define body force loads due to S a prescribed base acceleration or angular velocity using global axes directions *LOAD_BODY_X Define body force loads due to a prescribed base acceleration using global axes directions
Card 39 LCID, SF, LCIDDR, CID
Activate the proper option and enter the data. Only the first card defined is valid for Structured. Activate the proper option and enter the data. Only the first card defined is valid
*LOAD_BODY_Y
Card 40 LCID, SF, LCIDDR, CID
865

Altair Engineering
Supported Cards
Solver Description
Notes
for Structured. *LOAD_BODY_Z Card 41 LCID, SF, LCIDDR, CID Activate the proper option and enter the data. Only the first card defined is valid for Structured. Activate the proper option and enter the data. Only the first card defined is valid for Structured. Activate the proper option and enter the data. Only the first card defined is valid for Structured. Activate the proper option and enter the data. Only the first card defined is valid for Structured.
*LOAD_BODY_RX
Define body force loads due to a prescribed angular velocity using global axes directions
Card 42 LCID, SF, LCIDDR, XC, YC, ZC, CID
*LOAD_BODY_RY
*LOAD_BODY_RZ
*LOAD_BRODE
Define Brode function for application of pressure loads due to explosion. Apply a distributed pressure load over a three-dimensional shell part. Apply a concentrated nodal force to a node or a set of nodes.
YLD, BHT, XBO, YBO, ZBO, TBO, TALC, SFLC, CFL, CFT, CFP PID, LCID, VID1, OFF, BOXID, LCIDM, VID2, INOUT, ICYCLE NSID, DOFX, LCID, SF, CID FollowerForce PID, DOF, LCID, SF, CID, M1, M2, M3 LCID_as_displacemen t
*LOAD_MASK
*LOAD_NODE_SET
*LOAD_RIGID_BODY
Altair Engineering

866
Supported Cards
Solver Description
Supported Parameters SSID, LCID, SF, AT LCIDoption
Notes
*LOAD_SEGMENT_ SET
Apply the distributed pressure load over each segment in a segment set. Apply the distributed pressure load over one shell element or shell element set.
*LOAD_SHELL_SET
ESID, LCID, SF, AT LCIDoption
*LOAD_SUPERELAS TIC_ FORMING
LCP1, CSP1, NCP1, LCP1, CSP1, NCP1, ERATE, SCMIN, SCMAX, NCYL Define nodal sets giving the temperature that remains constant for the duration of the calculation. NSID, INSIDEX, BOXID, T, TE
*LOAD_THERMAL_ CONSTANT
*LOAD_THERMAL_L OAD_ CURVE *LOAD_THERMAL_ VARIABLE Define nodal sets giving the temperature that is variable in the duration of the calculation.
LCID, LCIDDR
NSID, NSIDEX, BOXID, TS, TB, LCID, TSE, TBE, LCIDE
Nastran
There are two types of load collectors for Nastran: Specific load collectors with a card image Generic load collectors without a card image Generic load collectors are used to collect loads and constraints for display purposes and to assign an ID to the loads. Specific load collectors are used for specialized loading cards, such as SPCADD, MPCADD, EIGRL, EIGB, EIGC, EIGP, EIGR, FREQ, FREQ1, LOAD, GRAV, RFORCE, and TEMPD. Specific load collectors have card images which can be edited to do the following: Group other load collectors together for simultaneous application in a single subcase Provide special information for a specific analysis type (such as modal analysis) General boundary conditions, such as loads and constraints, should not be collected into specific load
867

Altair Engineering
collectors. When reading in a Nastran deck, loads that have the same SID are collected into the same load collector. If a load collector already exists in the database with the same SID, one of the following can occur: If overwrite is off (default), the new load collectors ID is offset and all loads in that collector will have a new SID upon export. If overwrite is on, the new load collector replaces the existing load collector. The original load collector and the loads it contains are deleted. Supported Cards Solver Description Supported Parameters EXCITEID, DELAY, DPHASE, TP, RHO, B DELAY_OPTION DPHASE_OPTION AEFACT Defines real numbers for aeroelastic analysis. Defines contact parameters. Total_Number Notes
ACSRCE
Defines the power versus frequency curve for a simple acoustic source.
BCPARA
PARAM, VALUE BCPARA_NUM
BMFACE DELAY Defines the time delay term in the equations of the dynamic loading function Defines a dynamic loading DLOAD_NUM 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 Defines table data blocks SPECSEL, RECNO, TYPE, TID, DAMP DTI_TID_NUM Supported as constraints
DLOAD
DTI SPECSEL
Altair Engineering

868
Supported Cards
Solver Description
Supported Parameters contOpt
Notes
EIGB
Defines data needed to perform buckling analysis Defines data needed to perform complex eigenvalue analysis
EIGC
Cont
EIGP
Defines poles that are used in n/a complex eigenvalue extraction by the Determinant method Defines data needed to perform real eigenvalue analysis contOpt
EIGR
EIGRL
Defines data needed to n/a perform real eigenvalue (vibration or buckling) analysis with the Lanczos method Used to specify density ratios, Mach numbers, reduced frequencies, and velocities for flutter analysis. Defines data needed to perform flutter analysis. FORMAT (IDS, THRU_FORMAT)
FLFACT
FLUTTER
n/a
FREQ
Defines a set of frequencies to n/a be used in the solution of frequency response problems. Defines a set of frequencies to n/a be used in the solution of frequency response problems by specification of a starting frequency, frequency increment, and the number of increments desired. Alternative form of frequency list. Defines a set of frequencies to be used in the solution of frequency response problems by FREQ FREQ1 - FREQ5
Defined using FREQi.
FREQ1
FREQ2
869

Altair Engineering
Supported Cards
Solver Description
Notes
specification of a starting frequency, final frequency, and the number of logarithmic increments desired. FREQ3 Frequency List, Alternate FREQ Form 3. Defines a set of FREQ1 - FREQ5 frequencies for the modal method of frequency response analysis by specifying the number of frequencies between modal frequencies. Frequency List, Alternate FREQ Form 4. Defines a set of FREQ1 - FREQ5 frequencies for the modal method of frequency response analysis by specifying the amount of "spread" around each modal frequency and the number of equally spaced frequencies within the spread. Frequency List, Alternate FREQ Form 5. Defines a set of FREQ1 - FREQ5 frequencies for the modal method of frequency response analysis by specification of a frequency range and fractions of the natural frequencies within that range. Defines acceleration vectors for gravity or other acceleration loading n/a Defined using FREQi.
FREQ4
FREQ5
GRAV
LOAD
Defines a static load as a LOAD_Num_Set linear combination of load sets defined via FORCE, MOMENT, FORCE1, MOMENT1, FORCE2, MOMENT2, PLOAD, PLOAD1, PLOAD2, PLOAD4, PLOADX1, SLOAD, RFORCE, and GRAV entries.
Altair Engineering

870
Supported Cards
Solver Description
Supported Parameters EXCITE, LID, TID
Notes
LSEQ
Defines a sequence of static load sets.
MARCOUT
Selects output to be saved on WHERE, IO the Marc t16 end/or t19 file(s) MARCOUT_MAX used in SOL 600 only. Defines a multipoint constraint Number_Of_Sets set as a union of multipoint constraint sets defined via MPC entries. Defines parameters for automatic or fixed load/time stepping used in SOL 600 only. ID, TINIT, TFINAL, RSMALL, RBIG, TSMIN, TSMAX, NSMAX, NRECYC, IENHAN, IDAMP, NSTATE, NCUT, LIMTAR, IFINISH, FTEMP, IFLAG, CRITERIA, SETID, Y1Y4, X1-X4
MPCADD
NLAUTO
NLDAMP
Defines damping constants for EID1, EID2, ALPHA, nonlinear analysis when Marc BETA, GAMMA is executed from SOL 600 only. Defines a set of parameters for nonlinear static analysis iteration strategy ID, NINC, DT, KMETHOD, KSTEP, MAXITER, CONV, INTOUT, EPSU, EPSP, EPSW, MAXDIV, MAXQN, MAXLS, FSTRESS, LSTOL, MAXBIS, MAXR, RTOLB NLPCI
NLPARM
NLRGAP
Defines a nonlinear radial (circular) gap for transient response or nonlinear harmonic response.
ID, GA, GB, PLANE, TABK, TABG, TABU, RADIUS
871

Altair Engineering
Supported Cards
Solver Description
Supported Parameters PARAM, VALUE ID options (1, 0, User)
Notes
NLSTRAT
Defines strategy parameters for nonlinear structural analysis used in SOL 600 only. Defines non structural mass as the sum of the sets listed. Defines nodal thickness values for beams, plates and/ or shells.
NSMADD
NTHICK
ID, THICK
RANDPS
Defines load set power NUMBER_OF_RANDP spectral density factors for S use in random analysis having the frequency dependent form RANDT1
RFORCE
Defines a static loading condition due to an angular velocity and/or acceleration Defines a frequencydependent dynamic load of the form
n/a
RLOAD1
for use in frequency response problems RLOAD2 DELAY_OPTION Defines a frequencydependent dynamic excitation DPHASE_OPTION of the form
for use in frequency response problems
RSPEC
Defines a directional combination method, modal combination method,
Altair Engineering

872
Supported Cards
Solver Description
Notes
excitation direction(s), response spectra and scale factors for response spectrum analysis. SPCADD Defines a single-point constraint set as a union of single-point constraint sets defined on SPC or SPC1 entries Defines modal damping as a tabular function of natural frequency Defines a tabular function for use in generating frequencydependent and timedependent dynamic loads SPCADD_Num_Set
TABDMP1
TABDMP1_NUM
TABLED1
TABLED1_NUM
TABLED2
Defines a tabular function for TABLED2_NUM use in generating frequencydependent and timedependent dynamic loads. Also contains parametric data for use with the table Defines a tabular function for TABLED3_NUM use in generating frequencydependent and timedependent dynamic loads. Also contains parametric data for use with the table Defines the coefficients of a TABLED4_NUM power series for use in generating frequencydependent and timedependent dynamic loads. Also contains parametric data for use with the table Defines a tabular function for use in generating TABLEM1_NUM
TABLED3
TABLED4
TABLEM1
873

Altair Engineering
Supported Cards
Solver Description
Notes
temperature-dependent material properties. TABLEM2 Defines a tabular function for use in generating temperature-dependent material properties. Also contains parametric data for use with the table. Defines a tabular function for use in generating temperature-dependent material properties. Also contains parametric data for use with the table. TABLEM2_NUM
TABLEM3
TABLEM3_NUM
TABLEM4
Defines coefficients of a power TABLEM4_NUM series for use in generating temperature-dependent material properties. Also contains parametric data for use with the table. Defines a tabular function for TABLES1_NUM stress-dependent material properties such as the stressstrain curve (MATS1 entry), creep parameters (CREEP entry) and hyperelastic material parameters (MATHP entry). Specifies the material TABLEST_NUM property tables for nonlinear elastic temperature-dependent materials Defines power spectral TABRND1_NUM density as a tabular function of frequency for use in random analysis. Referenced by the RANDPS entry.
TABLES1
TABLEST
TABRND1
Altair Engineering

874
Supported Cards
Solver Description
Notes
TEMPD
Defines a temperature value n/a for all grid points of the structural model that have not been given a temperature on a TEMP entry. 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. Defines a time-dependent dynamic load or enforced motion of the form DELAY_OPTION
TIC
TLOAD1
for use in transient response analysis TLOAD2 Defines a time-dependent dynamic excitation or enforced motion of the form DELAY_OPTION
for use in a transient response problem, where
TRIM
Specifies constraints for SID, MACH, Q, LABEL, aeroelastic trim variables. The UX, AEQR, SPLINE1 and SPLINE4 NUM_LABEL entries need to be here for the finite plate spline. Defines time step intervals at TSTEP_NUM
TSTEP
875

Altair Engineering
Supported Cards
Solver Description
Notes
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. ID, NDT, DT, NO, KSTEP, MAXITER, CONV, EPSU, EPSP, EPSW, MAXDIV, MAXQN, MAXLS, FSTRESS, MAXBIS, ADJUST, MSTEP, RB, MAXR, UTOL, RTOLB
PAM-CRASH 2G
Supported Cards
Solver Description
Supported Parameters IFUN1, IFUN2, IFUN3, SCAL1, SCAL2, SCAL3, IFRAM, ISENS, TITLE, GES
Notes
ACC3D /
Imposed accelerations
Keyword input
ACFLD /
Acceleration field
IFUN1, SCAF1, IFUN2, Keyword input. SCAF2, IFUN3, SCAF3, TITLE, GES X Y Z x y z, IFRAM, ISENS, TITLE, GES IDR, LC, SCALE, ISENS, ITYPE, TITLE, GES Follower_Force Keyword input
BOUNC /
Specify boundary conditions on the base body Concentrated nodal load
CONLO /
Keyword input
DAMP /
Nodal damping group cards
ADAMP, TIDAMP, TFDAMP, IDAMP, TITLE, GES NUMNOD_option DAMP START/END
Keyword input
Altair Engineering

876
Supported Cards
Solver Description
Supported Parameters (TIME, SENSOR)
Notes
DIS3D /
Imposed displacement
IFUN1, IFUN2, IFUN3, SCAL1, SCAL2, SCAL3, IFRAM, ISENS, TITLE, GES IFUN1, IFUN2, IFUN3, SCAL1, SCAL2, SCAL3, IFRAM, ISENS, TITLE, GES IFUN1, IFUN2, IFUN3, SCAL1, SCAL2, SCAL3, IFRAM, ISENS, TITLE, GES
Keyword input
DIS3DM /
Imposed minimum displacement
Keyword input
DIS3DX /
Imposed maximum displacement
Keyword input
INVEL /
Specify the initial velocity of the VELX, VELY, VELZ, base body ROTX, ROTY, ROTZ, IFRAM, IRIGB, TITLE, GES Pressure on shells FUNCTION, MULT, ISENS, TITLE, GES FUNCTION, MULT, ISENS, TITLE, GES IFUN1, IFUN2, IFUN3, SCAL1, SCAL2, SCAL3, IFRAM, ISENS, TITLE, GES IFUN1, IFUN2, IFUN3, SCAL1, SCAL2, SCAL3, IFRAM, ISENS, TITLE, GES IFUN1, IFUN2, IFUN3, SCAL1, SCAL2, SCAL3, IFRAM, ISENS, TITLE, GES IFUN1, IFUN2, IFUN3,
Keyword input
PREFA /
Keyword input
PREBM /
Pressure on beams
Keyword input
RAC3D /
Imposed rotational acceleration
Keyword input
RAN3D /
Imposed angular rotations
Keyword input
RDA3D /
Radial 3D boundary conditions
Keyword input
RDD3D /
Keyword input
877

Altair Engineering
Supported Cards
Solver Description
Supported Parameters SCAL1, SCAL2, SCAL3, IFRAM, ISENS, TITLE, GES
Notes
RDV3D /
IFUN1, IFUN2, IFUN3, SCAL1, SCAL2, SCAL3, IFRAM, ISENS, TITLE, GES IFUN1, IFUN2, IFUN3, SCAL1, SCAL2, SCAL3, IFRAM, ISENS, TITLE, GES IFUN1, IFUN2, IFUN3, SCAL1, SCAL2, SCAL3, IFRAM, ISENS, TITLE, GES
Keyword input
RVE3D /
Imposed rotational velocities
Keyword input
VEL3D /
Imposed velocities
Keyword input
PERMAS
Supported Cards
Solver Description
Notes
$ADDMODES
Definition of static mode shapes DOFTYPE to be added to the set of RSYS eigenmodes used for SOURCE transformation to modal space.
Available as a load collector when the source = loads. To change the LPAT = field, set the AddmodeLoads toggle to LOADSELECT, which ensures that each data line will define different ADDMODES. In the NoOfLoads_AddMo de = field, enter the number of load patterns to assign
Altair Engineering

878
Supported Cards
Solver Description
Notes
the ADDMODES to. $CONTVAL Assignment of properties to contacts referenced by contact identifier or name. FRICTION GAPWIDTH NORMAL Supported as a load collector (card image LOADS). To create a card, use an existing load collector or create a new one with card image LOADS and enable the CONTVAL checkbox. A maximum number of 5 keywords are allowed per load collector (load pattern). $PRETENSION LOAD Assignment of load properties to pretension threads/areas referenced by identifier or name. Supported as a load collector (card image LOADS). To create a card, use an existing load collector or create a new one with card image LOADS and enable the PRETENSION checkbox.
$SUPPRESS
Definition of suppressed degrees of freedom. The degrees of freedom given on the header line are suppressed for all nodes listed within the data block.
See also Status Bar Model Browser Entity State Browser Entities & Solver Interfaces Include Files
879

Altair Engineering
Altair Engineering

880
Loads
Load entities have an associated load configuration. A load configuration determines how to draw, store, and work with the load. The follwoing load configurations are supported: Accelerations Constraints Fluxes Forces Moments Pressures Temperatures Velocities
Solver Card Support for Loads

General boundary conditions should not be collected into specific load collectors. Organizing loads and constraints into a specific load collector may result in an error termination. The following is a list of RADIOSS (Bulk Data Format), OptiStruct cards, which are represented as various types of loads. Supported Card Solver Description Supported Load Types Notes
ASET
Defines the boundary degrees of Constraints freedom of a superelement assembly for matrix reduction. Defines the boundary degrees of Constraints freedom of a superelement assembly for matrix reduction. Defines scale (area) factors for dynamic loads. Defines the time delay term tau in the equations of the dynamic loading function. Constraints
ASET1
DAREA
DELAY
Constraints
881

Altair Engineering
DEFORM
Defines enforced axial Flux deformation for one-dimensional elements for use in statics problems. Defines the phase lead term lower theta in the equation of the dynamic loading function. Defines a static force at a grid point by specifying a vector. Constraints
DPHASE
FORCE
Force
MBFRC
Defines a constant force at a Force grid point by specifying a vector.
MBFRCC
Defines a curve force at a grid point by specifying a vector.
Force
MBMNT
Defines a constant moment at a Moment grid point by specifying a vector. Defines a curve moment at a Moment grid point by specifying a vector. Defines a static moment at a Moment grid point by specifying a vector. Defines a static moment by Moment specification of a value and two grid points, which determine the direction. Defines a constant grid point motion. Defines a grid point motion vs. time by specifying a curve. Defines a static pressure load on a triangular or quadrilateral element. Defines concentrated, uniformly distributed, or linearly distributed applied loads to the CBAR or CBEAM elements at Constraint
MBMNTC
MOMENT
MOMENT1
MOTNG
MOTNGC
Constraint
PLOAD
Pressure
PLOAD1
Pressure
Altair Engineering

882
user-chosen points along the axis. PLOAD2 Defines a uniform static Pressure pressure load applied to twodimensional elements. Only QUAD4 or TRIA3 elements may have a pressure load applied to them via this entry. Defines a load on a face of a HEXA, PENTA, TETRA, PYRA, TRIA3, or QUAD4 element. Defines a uniform heat flux for CHBDYE elements. Rate of volumetric heat addition for a conduction element. Defines sets of single-point constraints and enforced displacements. Defines an enforced displacement value for static analysis, which is requested as a LOAD. Defines determinate reaction degrees of freedom in a free body. Pressure
PLOAD4
QBDY1
Flux
QVOL
Flux
SPC
Constraint
SPCD
Constraint
SUPORT
Constraint
SUPORT1
Defines determinate reaction Constraint degrees of freedom in a free body. The SUPORT1 bulk data entry must be requested in the I/O Options or Subcase Information sections by the SUPORT1 data selection command. Defines temperature at grid points for determination of Thermal Loading and Stress recovery. Temperature
TEMP
883

Altair Engineering
TIC(D) or (V)
Defines values for the initial conditions of variables used in structural transient analysis. Both displacement and velocity values may be specified at independent degrees-offreedom. Set of Degrees of Freedom for Residual Vector Calculation. Alternate Form of USET1
Constraint
USET
Constraint
USET1
Constraint
Abaqus
Each load or constraint must belong to a load collector. Loads or constraints in history data (under *STEP) should be organized into load collectors with HISTORY card image. These load collectors need to be added to a load step from the Load Steps panel. Loads or constraints in model data, however, should be organized into load collectors with the INITIAL_CONDITION card image. These load collectors do not need to be added to a load step. All loads and boundary conditions are recommended to be defined from the Step Manager in the Abaqus user profile. Note: Note The Import tab - Options section provides the user to select to Expand Loads on Sets. Selecting this option means that all loads and boundary conditions on sets are expanded to individual nodes and elements.
Supported Card
Solver Description
Supported Load Types Flux
Supported Parameters FIXED USER LOADCASE AMPLITUDE REGION TYPE = {LAGRANGIAN, SLIDING, EULERIAN} OP
*BOUNDARY Specifies flux boundary (electric potential, dof conditions for piezoelectric 9) analysis.
*BOUNDARY (structural)
Creates structural boundary conditions.
Constraint
TYPE = {DISPLACEMENT, VELOCITY, ACCELERATION} FIXED
Altair Engineering

884
USER LOADCASE AMPLITUDE REGION TYPE = {LAGRANGIAN, SLIDING, EULERIAN} OP *BOUNDARY (temperature, dof 11) Specifies temperature boundary conditions. Temperatures FIXED USER LOADCASE AMPLITUDE REGION TYPE = {LAGRANGIAN, SLIDING, EULERIAN} OP *CECHARGE Specifies concentrated electric Flux charges for piezoelectric analysis. Specifies concentrated current in electric conduction. Specify concentrated fluxes in heat transfer or mass diffusion analyses. Creates concentrated forces. Flux OP
*CECURRENT
OP
*CFLUX
Flux
OP
*CLOAD
Force
AMPLITUDE LOADCASE CYCLIC MODE FOLLOWER REGION TYPE = {LAGRANGIAN, SLIDING, EULERIAN} OP
*CLOAD
Creates concentrated moments.
Moment
AMPLITUDE LOADCASE CYCLIC MODE FOLLOWER REGION TYPE =
885

Altair Engineering
{LAGRANGIAN, SLIDING, EULERIAN} OP *COUPLING Define a surface-based coupling constraint Constraint CONSTRAINT NAME REF NODE SURFACE INFLUENCE RADIUS ORIENTATION *DECHARGE Distributes electric charges for piezoelectric analysis. Specify distributed fluxes in heat transfer or mass diffusion analyses. Define a distributing coupling constraint Pressure OP
*DFLUX
Pressure
OP
*DISTRIBUTING
Constraint
WEIGHTING METHOD = {UNIFORM, LINEAR, QUADRATIC, CUBIC} MASS
*DISTRIBUTING COUPLING
Specify nodes and weighting for distributing coupling elements Specifies distributed loads
See Elements.
*DLOAD
Pressure
AMPLITUDE LOADCASE CYCLIC MODE REGION TYPE = {LAGRANGIAN, SLIDING, EULERIAN} OP
*FILM
Define film coefficients and associated sink temperatures.
Pressure
AMPLITUDE FILM AMPLITUDE REGION TYPE = {LAGRANGIAN/ SLIDING, EULERIAN} OP
*KINEMATIC
Define a kinematic coupling constraint
Multi-point Constraints
Altair Engineering

886
*KINEMATIC COUPLING
Constrain all or specific degrees of freedom of a set of nodes to the rigid body motion of a reference node Define multi-point constraints
Multi-point Constraints ORIENTATION See Elements.
*MPC
Multi-point Constraints BEAM LINK See Elements. PIN TIE
*RADIATE
Specify radiation conditions in heat transfer analyses
Pressure
AMPLITUDE OP REGION TYPE (explicit)
*TEMPERATURE
Specifies predefined temperature field.
Temperature
AMPLITUDE BSTEP BINC ESTEP EINC INPUT FILE MIDSIDE OP
Actran
Supported Card
Solver Description
Supported Load Types Face BC Face BC Displacement Face BC Face BC
Notes
ACCELERATION ADMITTANCE DISPLACEMENT
Boundary conditions Boundary conditions Boundary conditions
DISTRIBUTED_LOAD Boundary conditions DISTRIBUTED_PRES Boundary conditions
887

Altair Engineering
SURE DIV_TOTAL INFINITE ADMITTANCE POINT_LOAD PRESSURE VELOCITY Boundary conditions Boundary conditions Face BC Face BC
Boundary conditions Boundary conditions Boundary conditions
Load Pressure Face BC
ANSYS
Supported Card
Solver Description
Supported Load Types
Notes
BF
Defines a nodal body force load. Flux
FLUE and HGEN labels are
BF_FLUE
Flux
Supported under the Flux panel. Supported under the Flux panel. (Structural temperatures) label is supported under the Temperatures panel.
BF_HGEN
Flux
BF_TEMP
Temperatures
BFE_FLUE
Defines an element body force load
Flux
BFE_HGEN BFE_TEMP ConvBulkTe
Flux Flux Pressure
Altair Engineering

888
ConvFilmCo D_CONSTRNT Defines DOF constraints at nodes.
Pressure Constraint
D_TEMP D_VOLT F_FLOW F_HEAT FLOTRAN Specifies "FLOTRAN data settings" as the subsequent status topic. Specifies force loads at nodes.
Temperature Constraint Flux Flux Pressure FLOTRAN surface load label FSI [fluidstructure interaction flag] is available under pressure load. You must use DOF1 to add value for this label.
FORCE
Selects the element nodal force Force type for output. Moment Pressure Specifies initial conditions at nodes. Constraint
FORCE2 HFLUX IC_CONSTRN
IC_TEMP IC_VOLT PRESSURE SFE Defines elemental surface load
Temperature Constraint Pressure Pressure, Convection, Heatflux Structural, thermal and Fluid labels are covered Structural label: PRES Thermal label: CONV, HLFUX
SFE
Surface load
Structural, thermal, and fluid
889

Altair Engineering
Fluid label: FSI
LS-DYNA
Several load types cause three cards to be output for x, y, and z components. During input, these are grouped into one load. Loads cannot be applied to sets, components, or boxes. Load curves are input and output. Use the Card Editor to select load curves. Unless mentioned in the Notes column, load cards cannot be edited. Supported Card Solver Description Supported Load Types Notes
*BOUNDARY_ PRESCRIBED_MOTI ON_ NODE
Define an imposed nodal motion Constraints (velocity, acceleration, or Type 2; Card 26, VAD displacement) on a node or a =2 set of nodes. DEATH, BIRTH
DOF 4, -4, 8, -8, 9, 9, 10, -10, 11, -11 are not supported
Define an imposed nodal motion Velocity (velocity, acceleration, or Type 1; Card 26; displacement) on a node or a VAD = 0 set of nodes.
Define an imposed nodal motion Acceleration (velocity, acceleration, or Type 1 displacement) on a node or a set of nodes. Card 26 VAD = 1 Velocity
*BOUNDARY_ PRESCRIBED_MOTI ON_ NODE_(ID) *BOUNDARY_ PRESCRIBED_MOTI ON_ NODE_(ID)
Constraints Type 2; Card 26, VAD =2 dynaName, DEATH, BIRTH
*BOUNDARY_SPC_ NODE
Define nodal single point constraint
Constraints
Altair Engineering

890
Type 1; Card 13 SPC CID *BOUNDARY_SPC_ NODE_ (ID) *BOUNDARY_ Define temperature boundary TEMPERATURE_NO conditions for a thermal or DE coupled thermal/structural analysis. *CONSTRAINED_GL OBAL Define a global boundary constraint plane. Constraints dynaName, CID Temperature LCID, LOC
Constraints
*INITIAL_TEMPERAT Define initial nodal point URE_ temperatures using nodal set NODE IDs or node number.s *INITIAL_VELOCITY Define initial nodal point translational velocities using nodal set IDs.
Temperatures LOC Type 2 Card 30 INITV = 3 For structured output, global velocity is set to 0.0. For structured input, nonzero values for INITV = 1 or INITV = 5 create velocities. INITV values of 2, 4, 6, and 7 are ignored.
*INITIAL_VELOCITY_ Define initial nodal point NODE velocities for a node. *LOAD_BEAM_ELE MENT *LOAD_MASK Defines load on beam elements
Rotation
Pressure
Apply a distributed pressure load over a three-dimensional shell part Apply a concentrated nodal force to a node or a set of nodes.
n/a
*LOAD_NODE_POIN T
Force Type 1; Card 23; Point Loads FollowerForce
LS-DYNA Load Configs 1, 2, 3 and 4 A load curve can be selected for these loads. LS-DYNA Load
*LOAD_NODE_POIN
Apply a concentrated nodal
Moment
891

Altair Engineering
force to a node or a set of nodes.
Type 1 Card 23 Point Loads
Configs 5, 6 7 and 8.
*LOAD_SEGMENT
Apply the distributed pressure Pressure load over one triangular or quadrilateral segment defined by LCID, AT four, six or eight nodes. Apply the distributed pressure Pressure load over one triangular or quadrilateral segment defined by LCID, AT four, six or eight nodes. Apply the distributed pressure load over one shell element or shell element set. Apply the distributed pressure load over one shell element or shell element set. Apply the distributed pressure load over one shell element or shell element set. Pressure AT, LCIDoption Pressure LCID, AT Pressure Type 2 Card 24 Pressure BC
*LOAD_SEGMENT_I D
*LOAD_SHELL_ELE MENT
*LOAD_SHELL_ELE MENT_ ID *LOAD_SHELL_ PRESSURE
*LOAD_THERMAL_ CONSTANT_NODE
Define nodal sets giving the temperature that remains constant for the duration of the calculation.
Temperature n/a
*LOAD_THERMAL_ VARIABLE_NODE
Define nodal temperature that is Temperature variable during the calculation. TS, LCID
MADYMO
Supported Card
Solver Description
Supported Load Types Equation
Notes
CONSTRAINT. LINEAR
Linear constraint for FE nodes
Altair Engineering

892
EDGE
Force Moment
ELEMENT_AC INITIAL.NODE_DISP INITIAL.NODE_VEL LOAD Initial nodal displacement Initial nodal velocity
Pressure Constraints Constraints Defined on the card of the applicable load type. Prescribed nodal displacement. Constraints Defined on the card of the referenced JOINT.
MOTION. NODE_DISP
MOTION.NODE_VEL NODE
Prescribed nodal velocity.
Constraints
Time dependent point loads Force (forces and moments) applied to Moment nodes. Pressure Define which degrees of Constraints freedom of nodes are constrained, by supporting them on a rigid body or the reference space.
PRES SUPPORT
MARC
Supported Card
Solver Description
Supported Load Types Constraints Pressure Constraints Constraints Constraints
Notes
Disp_chang DIST_LOADS Fixed_Acce Fixed_Disp Fixed_Pres
893

Altair Engineering
FOUNDATION Init_Disp INITIAL_vel MOMENT POINT_LOAD
Pressure Constraints Velocity Moment Constraints
Nastran
Supported Card
Solver Description
Supported Load Types Constraints
Notes
ASET
Defines degrees-of-freedom in the analysis set (a-set) Defines degrees-of-freedom in the analysis set (a-set)
ASET1
Constraints
BNDFIX1 BSET1 Defines analysis set (a-set) degrees-of-freedom to be fixed (b-set) during generalized dynamic reduction or component mode synthesis calculations.
Constraints Constraints
CSET1
Defines analysis set (a-set) Constraints degrees-of-freedom to be free (c-set) during generalized dynamic reduction or component modes calculations. Defines scale (area) factors for static and dynamic loads. In dynamic analysis, DAREA is used in conjunction with RLOADi and TLOADi entries. Constraints
DAREA
DEFORM
Defines enforced axial Flux deformation for one-dimensional elements for use in statics
Altair Engineering

894
problems. FORCE Requests the form and type of element force output or particle velocity output in coupled fluidstructural analysis. Defines a static concentrated moment at a grid point by specifying a scale factor and a vector that determines the direction. Defines degrees-of-freedom to be excluded (o-set) from the analysis set (a-set). Defines a uniform static pressure load on a triangular or quadrilateral surface comprised of surface elements and/or the faces of solid elements. Defines concentrated, uniformly distributed, or linearly distributed applied loads to the CBAR or CBEAM elements at user-chosen points along the axis. Force
MOMENT
Moment
OMIT1
Constraints
PLOAD
Pressure
PLOAD1
Pressure
PLOAD2
Defines a uniform static Pressure pressure load applied to CQUAD4, CSHEAR, or CTRIA3 two-dimensional elements.
The THRU field is supported for feinput only. On export, additional pressure cards for the range specified are written. The THRU field is supported for feinput only. On export, additional pressure cards for the range specified are written. Unequal nodal pressures are now supported. The average pressure
PLOAD4
Defines a pressure load on a face of a CHEXA, CPENTA, CTETRA, CTRIA3, CTRIA6, CTRIAR, CQUAD4, CQUAD8, or CQUADR element.
Pressure
895

Altair Engineering
value is used as the magnitude of the pressure for visualization only. The individual field values, P1-P4, can be viewed or edited using the card editor. Updating the magnitude of pressure from the Pressures panel will have no effect on PLOAD4 cards defined using unequal nodal pressures. QBDY1 Defines a uniform heat flux into CHBDYj elements. Defines generalized degrees-offreedom (q-set) to be used for generalized dynamic reduction or component mode synthesis. Volume Heat Addition - Defines a rate of volumetric heat addition in a conduction element. Flux
QSET1
Constraints
QVOL
Flux
SPC
Defines a set of single-point Constraints constraints and enforced motion (enforced displacements in static analysis and enforced displacements, velocities or acceleration in dynamic analysis).
Constraints on nodes are supported through SPC cards. PS field in GRID card is not supported. Upon import, any PS entry on the GRID card will be converted into an SPC card. Supported for feinput only. On export, equivalent SPC cards are written. Alternate format with THRU in the fifth field is supported.
SPC1
Defines a set of single-point constraints.
Constraints
Altair Engineering

896
SPCD
Defines an enforced displacement value for static analysis and an enforced motion value (displacement, velocity or acceleration) in dynamic analysis. Defines determinate reaction degrees-of-freedom in a free body. Defines determinate reaction degrees-of-freedom (r-set) in a free body-analysis. SUPORT1 must be requested by the SUPORT1 Case Control command. Transient Initial Condition Defines values for the initial conditions of variables used in structural transient analysis. Transient Initial Condition Defines values for the initial conditions of variables used in structural transient analysis. Defines temperature at grid points for determination of thermal loading, temperaturedependent material properties, or stress recovery. Defines a degree-of-freedom set. Defines a degrees-of-freedom set.
Constraints
SUPORT
Constraints
SUPORT1
Constraints
TIC(D)
Constraints
TIC(V)
Constraints
TEMP
Temperatures
USET
Constraints
USET1
Constraints
Note :
Other loads such as SPCADD, MPCADD, FREQ, FREQ1, EIGR, EIGRL, EIGC, EIGP, EIGB, GRAV, and RFORCE are supported as load collectors.
PAM-CRASH 2G
897

Altair Engineering
Supported Card
Solver Description
Supported Load Types Acceleration
Notes
ACC3D /
Imposed accelerations
Acceleration type can be specified in the Acceleration panel.
BOUNC / CONLO / DIS3D / DIS3DM /
Define boundary condition Concentrated nodal load Imposed displacement Imposed minimum displacement Imposed maximum displacement Define initial velocity Pressure on shells Imposed rotational acceleration
Constraints Force(1) Constraints Constraints
DIS3DX /
Constraints
INVEL / PREFA / RAC3D /
Velocity Pressure(1) Acceleration Acceleration type can be specified in the Acceleration panel.
RAN3D / RDA3D /
Imposed angular rotations Radial 3D boundary conditions
Constraints Acceleration Acceleration type can be specified in the Acceleration panel.
RDD3D / RDV3D / RVE3D / RWALL / SECFO_PLANE / Radial 3D boundary conditions Imposed rotational velocities Rigid wall definition
Constraints Velocity Velocity
Altair Engineering

898
VEL3D /
Imposed velocities
Velocity
PERMAS
Supported Card
Solver Description
Supported Load Types Constraints
Notes
$ADDMODES
Definition of static mode shapes to be added to the set of eigenmodes used for transformation to modal space.
If static mode shapes will be added directly to nodes or nodesets (SOURCE=INPUT), the $ADDMODES can be created through the Constraints panel. Click sysid to specify the system regarding to which the modes shall be applied. Use the DOFTYPE button to select an option: DISP, TEMP, PRES, POTE and MATH.
$ADDMODES
Definition of static mode shapes to be added to the set of eigenmodes used for transformation to modal space.
Pressure
If mode shapes will be applied based on the natural deformation of elements (SOURCE=INPUT) the $ADDMODES keyword needs to be created here.
$CONLOAD
Definition of concentrated loads Force at nodal point degrees of freedom. Definition of concentrated loads Moment at nodal point degrees of freedom.
$CONLOAD
899

Altair Engineering
$DISLOAD PRESS
Definition of pressure loads for elements, where loads are given for elements or element sets. Nodal temperatures defined on elements or element sets.
Pressure
$DISLOAD TEMP
Pressure
$DISLOAD TEMPFILM
Surrounding temperatures for Pressure convective heat transfer applied on elements or element sets. Nodal temperatures definition applied on nodes or node sets Temperature
$DISLOADN TEMP
$DISLOADN TEMPFILM
Surrounding temperatures for Temperature convective heat transfer applied on nodes or node sets. Definition of initial values for Constraints nodal point degrees of freedom. For $INIVAL source parameter INPUT is currently supported to specify the initial values based on nodal points. Only ACCELERATION and GRAVITY are supported. This card is created in the Pressure panel. Assign to a set of elements, and the set statement displays in the card image. To create the card without a set, create a pressure on a 'dummy' element; the card will be created without a set and can be applied to the whole model. Only ACCELERATION and GRAVITY are
$INIVAL
$INERTIA
Definition of inertia forces acting Pressure on entire component or element sets. Available are force distributions due to linear acceleration, constant or accelerated rotation and coriolis acceleration.
$INERTIAX
Definition of inertia forces acting Pressure on entire axisymmetric component or element sets.
Altair Engineering

900
Available are force distributions due to linear acceleration and constant rotation.
supported. This card is created in the Pressure panel. Assign to a set of elements, and the set statement displays in the card image. To create the card without a set, create a pressure on a 'dummy' element; the card will be created without a set and can be applied to the whole model. Equation Both cards are created simultaneously in the Equation panel. The equation needs to be placed into a load collector with card image SUPRESS. By attaching the load collector to a load step with CONSTRAINTS attribute set, the $MPCVAL card gets written in the desired $CONSTRAINTS variant.
$MPC Multipoint constraint definition. GENERAL/$MPCVAL
$PRESCRIBE/ PREVAL
Prescribed degrees of freedom/ Nodal point values (implemented as HyperMesh constraints)
Constraints
$SUPPRESS
Suppressed degrees of freedom Constraints
Samcef
The following cards are supported in the Samcef interface:
901

Altair Engineering
Supported Cards
Solver Description
Supported Load Types CONSTRAINT
Notes
.CLM FIX
Defines a set of single-point constraints Defines sets of enforced displacements
.CLM DEP
CONSTRAINT
.CLM CHA COMP 123
Defines a static force at a grid FORCE point by specifying a vector and a value.
.CLM FOL COMP 123 Defines a follower force at a grid FORCE point by specifying a vector and a value .CLM CHA COMP 456 Defines a static moment at a MOMENT grid point by specifying a vector and a value. MOMENT
.CLM FOL COMP 456 Defines a follower moment by specifying a vector and a value .CLM PRESSURE Defines a static pressure load on any elements type
PRESSURE
See also Include Files Load Collectors
Altair Engineering

902
Accelerations
Acceleration loads allow for an acceleration (length/time2) to be defined on the model. The following panels can be used to create and edit accelerations: Accels Load Types
The data names associated with acceleration loads can be found in the data names section of the HyperMesh Reference Guide.
See also Include Files Load Collectors Loads
903

Altair Engineering
Constraints
Constraints allow for constrained degrees of freedom to be defined on the model. The following panels can be used to create and edit constraints: Constraints Load Types
The data names associated with constraint loads can be found in the data names section of the HyperMesh Reference Guide.
Altair Engineering

904
Fluxes
Flux loads are defined as an amount that flows through a unit area per unit time (amount/length2/time). Fluxes are typically used in modeling transport phenomena such as heat transfer, mass transfer, fluid dynamics, and electromagnetism. The following panels can be used to create and edit fluxes: Flux Load Types
The data names associated with flux loads can be found in the data names section of the HyperMesh Reference Guide.
905

Altair Engineering
Forces
Force loads allow for a concentrated force (mass*length/time2) to be applied to the model. The following panels can be used to create and edit forces: Forces Load Types
The data names associated with force loads can be found in the data names section of the HyperMesh Reference Guide.
Altair Engineering

906
Moments
Moment loads allow for a concentrated moment (length*force) to be applied to the model. The following panels can be used to create and edit moments: Moments Load Types
The data names associated with moment loads can be found in the data names section of the HyperMesh Reference Guide.
907

Altair Engineering
Pressures
Pressure loads allow for a pressure (force*length2) to be applied to the model. The following panels can be used to create and edit pressures: Pressures Load Types
The data names associated with pressure loads can be found in the data names section of the HyperMesh Reference Guide.
Altair Engineering

908
Temperatures
Temperature loads allow for a concentrated temperature to be applied to the model. The following panels can be used to create and edit temperatures: Temperatures Load Types
The data names associated with temperature loads can be found in the data names section of the HyperMesh Reference Guide.
909

Altair Engineering
Velocities
Velocity loads allow for a velocity (length/time) to be applied to the model. The following panels can be used to create and edit velocities: Velocities Load Types
The data names associated with velocity loads can be found in the data names section of the HyperMesh Reference Guide.
Altair Engineering

910
Equations
Equation entities contain mathematical equations that define more complex loads. They are used to define linear constraints in local and global coordinate systems. The following panels can be used to create and edit equations: Equations Load Types
The data names associated with equation loads can be found in the data names section of the HyperMesh Reference Guide.
Solver Card Support for Equations

Supported Card
Solver Description
Notes
MPC
Defines a multipoint constraint equation of the form.
Abaqus
Each load or constraint must belong to a load collector. Loads or constraints in history data (under *STEP) should be organized into load collectors with HISTORY card image. These load collectors need to be added to a load step from the Load Steps panel. Loads or constraints in model data, however, should be organized into load collectors with the INITIAL_CONDITION card image. These load collectors do not need to be added to a load step. All Loads and Boundary conditions are recommended to be defined from the Step Manager in the Abaqus user profile. Note: If a **HMLOAD_SETS_EXPAND comment is found in the input file, all loads and boundary conditions on sets are expanded to individual nodes and elements.
Supported Card
Solver Description
Supported Load Types Equations
Supported Parameters Explicit node IDs are supported. Node sets
*EQUATION
Define linear multi-point constraints
911

Altair Engineering
are not supported. Equations are considered as loads and therefore, they are collected in load collectors. Upon export, they write to the bulk data portion of the Abaqus deck.
ANSYS
Supported Card
Solver Description
Notes
CE
Defines a constraint equation relating to degrees of freedom.
LS-DYNA
Several load types cause three cards to be output for x, y, and z components. During input, these are grouped into one load. Loads cannot be applied to sets, components, or boxes. Load curves are input and output. Use the Card Editor to select load curves. Load cards cannot be edited.
Supported Card
Solver Description
Supported Load Types Equations
Notes
*CONSTRAINED_LIN EAR
Define linear constraint equations between displacements and rotations, which can be defined in a local coordinate system. Define linear constraint equations between displacements and rotations, which can be defined in global
*CONSTRAINED_LIN EAR_ GLOBAL
Equations
Altair Engineering

912
coordinate systems.
MADYMO
Supported Card
Solver Description
Supported Load Types independent node + dependent nodes = references to nodes representing GROUP_LIST dof1 = dof2 = dof3 = dof4 = dof5 = dof6 = DOF_DX DOF_DY DOF_DZ DOF_RX DOF_RY DOF_RZ
Notes
CONSTRAINT. LINEAR
Linear constraint for FE nodes.
In the Element Types panel, select CONSTRAINT for element type = rigid.
EQUATION.MASTER Dependent part of linear constraint equation (eliminated degree of freedom).
node = NODE_ID Select: dof1 for DIRECTION = D1 dof2 for DIRECTION = D2 dof3 for DIRECTION= D3 dof4 for DIRECTION = R1 dof5 for DIRECTION = R2 dof6 for DIRECTION = R3 or an arbitrary DOF for DIRECTION = ALL w = FACTOR
Select set all DOFs of MASTER NODE equal to the corresponding DOFs of the SLAVE NODE(s) for DIRECTION = ALL.
EQUATION.SLAVE
Independent part linear constraint equation (retained degrees of freedom).
Equations nodes = NODE_ID Select: dof1 for DIRECTION = D1 dof2 for DIRECTION =
Select set all DOFs of MASTER NODE equal to the corresponding DOFs of the SLAVE NODE(s) for DIRECTION = ALL.
913

Altair Engineering
D2 dof3 for DIRECTION = D3 dof4 for DIRECTION = R1 dof5 for DIRECTION = R2 dof6 for DIRECTION = R3. w = FACTOR constant is not used Each unique combination of a node and a DOF represents one EQUATION. SLAVE.
Nastran
Supported Card
Solver Description
Notes
MPC
Defines a multipoint constraint equation of the form.
Individual weight factors can be created on the nodes of an MPC equation using the update functionality in the Equations panel.
Note :
Other loads such as SPCADD, MPCADD, FREQ, FREQ1, EIGR, EIGRL, EIGC, EIGP, EIGB, GRAV, and RFORCE are supported as load collectors.
Permas
Supported Card
Solver Description
Notes
MPC GENERAL
General linear constraint equation
For more information on MPC cards and using duplicate ID pools, see the Permas Interface
Altair Engineering

914
Overview topic.
See also Include Files Load Collectors
915

Altair Engineering
System Collectors
System collectors collect and organize systems. System collectors are created, edited, and deleted from the Model Browser and are shown under the SystemCollector folder. Systems can be organized into a system collector using the Organize panel. Every system must be organized into one, and only one, system collector and therefore are mutually exclusive to a system collector. Newly created systems are automatically organized into the current system collector. The current system collector is shown bold in the Model Browser. The current system collector can be set using the Model Browser context sensitive menu on a selected system collector within the SystemCollector folder. System collectors can also be card edited using the Model Browser context sensitive menu on selected system collectors. System collectors have a display state, on or off, which control the display of all systems organized within the system collector in the graphics area. The display state of a system collector can be controlled using the icons next to the system collector in the Model Browser. System collectors also have an active and export state. The active state of a system collector controls the display state of the system collector and the listing of the system collector in the Model Browser and any of its views. If a system collector is active, then its display state is available to be turned on or off and it is listed in the Model Browser and any of its views. If a system collector is inactive, then its display state is turned off permanently and it is not listed in the Model Browser or any of its views. If a find operation "finds" an inactive system collector, that system collector will automatically be set to active. The export state of a system collector controls whether or not that system collector and all systems organized within the system collector are exported when the custom export option is utilized. The all export option is not affected by the export state of a system collector. The active and export states of system collectors can be controlled using the Entity State Browser. Operations performed on a system collector affect systems within the system collector. For example, if you delete a system collector, the systems within the system collector are also deleted. The data names associated with system collectors can be found in the data names section of the HyperMesh Reference Guide.
Altair Engineering

916
Solver Card Support for System Collectors

The supported RADIOSS cards in RADIOSS (Block Format) 100 are listed below. You can quickly create these cards by right-clicking in the Solver Browser and selecting Create Cards. Supported Card Solver Description Supported Parameters Notes
917

Altair Engineering
/TRANSFORM/ROT
Defines rotational transformation on the node set. Defines translational transformation on the node set. Defines scaling transformation on the node set. Defines symmetry transformation on the node set.
/TRANSFORM/TRA
/TRANSFORM/SCA
/TRANSFORM/SYM
LS-DYNA
The system collector cards can be previewed, but not edited. Supported Card Solver Description Supported Parameters Notes
*DEFINE_ Define a transformation for the OPTION (SCALE, ROTATE, TRANSL) TRANSFORMATION INCLUDE_TRANSFORM keyword option. A1, A2, A3 Title NumDatalines *INCLUDE_TRANSF Include file that supports ORM offset on its content IDs and transforms on its contents. FILENAME IDNOFF, IDEOFF, IDPOFF, IDMOFF, IDSOFF, IDFOFF, IDDOFF, IDROFF, FCTMAS, FCTTIM, FCTLEN, FCTTEM, INCOUT, TRANID
Transformations can be created using the Transformation Manager .
HyperMesh support offset on the entity ID's. During import, offsets are applied on to the ID's of the corresponding include_transform file contents. During export, offset is subtracted from the ID's. The current release only supports Input and output therefore the offsets cannot be changed. Transformations can be created using the
*NODE_TRANSFOR Transformation defined on M node set
TRSID, NSID
Altair Engineering

918
Title
Transformation Manager .
PAM-CRASH 2G
Supported Card
Solver Description
Supported Parameters NAME, Selection, Keyword, D, X, Y, Z, N1, N2 NumDatalines
Notes
TRANSFORMATION /
See also Model Browser Organize panel Entity State Browser HyperMesh Entities & Solver Interfaces Include Files
919

Altair Engineering
Systems
System entities, commonly called coordinate systems, can be defined as rectangular, cylindrical, or spherical coordinate systems. Several systems may be nested. There are two types of system assignments to entities; as a reference system, or as a displacement system. A system may be a reference system, a displacement system, or both. A reference system is used to define the geometric positions of entities. Entities that can be assigned a reference system include systems, nodes, and loads. By default, each of these entities is defined in the global system with an ID of zero. Entity data is always displayed and reviewed transformed into the global system. When a reference system is deleted, the position of the entity assigned that reference system is maintained relative to the global system in the transformation process. For example, if you define the nodes of a cylindrical structure in a cylindrical reference coordinate system, and then delete the cylindrical reference coordinate system in which the nodes are defined, the model retains its cylindrical shape and also its location in space but is now referenced to the global system. A displacement system is used to define the nodal degree of freedom coordinate system assigned to a node. The only entity that may be assigned a displacement system is a node. When you delete a displacement system, the nodal degrees of freedom are not transformed to the global system, so all degree of freedom definitions after the deletion of the displacement system are now simply in the global system. The data names associated with systems can be found in the data names section of the HyperMesh Reference Guide.
The following panels can be used to create and edit systems: Systems
Solver Card Support for Systems

The supported RADIOSS cards in RADIOSS (Block Format) 100 are listed below. You can quickly create these cards by right-clicking in the Solver Browser and selecting Create Cards. Supported Card Solver Description Supported Parameters Notes
/FRAME/FIX /FRAME/MOV
Describes the frames. Describes the moving frames. Relative motion with respect to a reference frame. System definition with Z axis and YZ plane.
/FRAME/MOV2
Altair Engineering

920
/FRAME/NOD
Describes the node defined moving frame. Describes the fixed skew frames. Describes the moving skew frames. System definition with Z axis and YZ plane.
/SKEW/FIX
/SKEW/MOV
/SKEW/MOV2
The Systems panel offers two methods to create local coordinate systems, working with the RADIOSS (Bulk Data), OptiStruct user profile as follows: Supported Card Solver Description Supported Parameters Notes
CORD1C
Defines a cylindrical coordinate system by referencing three grid points. The first point is the origin, the second lies on the z-axis, and the third lies in the plane of the azimuthal origin. Defines a rectangular coordinate system by reference to three grid points. The first point is the origin, the second lies on the z-axis, and the third lies on the x-z plane. Defines a spherical coordinate system by reference to three grid points. The first point is the origin, the second lies on the polar axis, and the third lies on the plane of the azimuthal origin. Defines a cylindrical
This type of system is created from the create by node reference subpanel when cylindrical is the chosen type.
CORD1R
This type of system is created from the create by node reference subpanel when rectangular is the chosen type.
CORD1S
This type of system is created from the create by node reference subpanel when spherical is the chosen type.
CORD2C
This type of system is
921

Altair Engineering
coordinate system by reference to the coordinates of three grid points. 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.
created from the create by axis direction subpanel when cylindrical is the chosen type. HyperMesh allows various combinations of axes and planes to be indicated in the create by axis direction subpanel, but will write out the appropriate coordinates to define the z- axis and the x-z plane. This type of system is created from the create by axis direction subpanel when rectangular is the chosen type. HyperMesh allows various combinations of axes and planes to be indicated in the create by axis direction subpanel, but will write out the appropriate coordinates to define the z- axis and the x-z plane. This type of system is created from the create by axis direction subpanel when spherical is the chosen type. HyperMesh allows various combinations of axes and planes to be indicated in the create by axis direction subpanel, but will write out the appropriate coordinates to define the z- axis and the x-z plane. This type of system is created from the create
CORD2R
Defines a rectangular coordinate system by reference to the coordinates of three points. 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.
CORD2S
Defines a spherical coordinate system by reference to the coordinates of three points. The first point defines the origin. The second point defines the direction of the zaxis. The third lies in the plane of the azimuthal origin.
CORD3R
Defines a rectangular coordinate system by
Altair Engineering

922
reference to three points. The first point is the origin, the second lies on the x-axis, and the third lies on the xy plane. CORD4R Defines a rectangular coordinate system by reference to the coordinates of three points. The first point is the origin, the second lies on the x-axis, and the third lies on the xy plane.
by node reference subpanel when rectangular is the chosen type. This type of system is created from the create by axis direction subpanel when rectangular is the chosen type. HyperMesh allows various combinations of axes and planes to be indicated in the create by axis direction subpanel, but will write out the appropriate coordinates to define the z- axis and the x-z plane. Editing the card image for a CORD2R will allow users to define a CORD4R.
RADIOSS (Fixed Format) system formulations, or skew frames, are read into HyperMesh. Defined coordinate systems using three nodes or two vectors are converted to use three points. This is based on the RADIOSS (Fixed Format) definition of those coordinate systems. Non-unit vectors can be input in the data deck. HyperMesh computes the coordinate system from vectors 1 and 2, which are supplied. Vector 2 may be stored differently than the way vector 1 is stored. Vectors 1 and 2 form an orthogonal system. HyperMesh stores the vector 2 equivalent to the vector 2 supplied through the data file. When Imove equals one, the system is defined by 3 nodes. This is not supported. In the translator, the system is computed from the nodes and exported as vectors 1 and 2 with node ID attributes. Check this data before using it, as the updates made in the card previewer do not update the system. A warning message is displayed if this occurs. Modifying the interface allows HyperMesh to display the vector orientation along corresponding X, Y, and Z directions.
Abaqus
The coordinate systems are defined from the Systems panels. A system can be exported as a
923

Altair Engineering
*SYSTEM or *TRANSFORM card depending on the nodal assignment of the system. To export an *ORIENTATION card it is required to enable the option in the card image of the system card. The following Abaqus (system) keywords are supported: Supported Card Solver Description Supported Parameters LOCAL DIRECTIONS NAME SYSTEM DEFINITION = COORDINATES /NODES Notes
*ORIENTATION
Define a local axis system for material or element property definition, for kinematic coupling constraints, for free directions for inertia relief loads, or for connectors
The *ORIENTATION card needs a name in Abaqus. Since systems do not have a name, a name needs to be entered in the system card image. The restriction of one system per system collector has been removed with version 10.0 SA1-130. DEFINITION = NODES option with only two nodes is converted to DEFINITION=COORDINAT ES upon import from an input file. *ORIENTATION with SYSTEM = Z RECTANGULAR is converted to RECTANGULAR upon import from an input file.
*SYSTEM
Specify a local coordinate system in which to define nodes
Whenever a system is assigned to nodes with the set reference option from the Systems panel activated, a *SYSTEM card is exported before the node block of its assignment. TYPE NSET If assigned to individual nodes, on export each *TRANSFORM card creates references to an automatically generated *NSET card. This *NSET card is followed by the list of the nodes that are
*TRANSFORM
Specify a local coordinate system at nodes.
Altair Engineering

924
assigned to the coordinate system with the set displacement option. Systems can be assigned to node sets with the same assignment procedure.
ANSYS
Supported Card
Solver Description
Supported Parameters KCN, KCS, XC, YC, ZC, THXY, THYZ, THZX, PAR1, PAR2 R5.0, Type, NCSY, CSYTYP, VAL1, VAL2, VAL3
Notes
LOCAL
Defines a local coordinate system by location and orientation. Defines a local coordinate system by location and orientation.
Even if KCN>10, 10 is added to the current value.
LOCAL
Type = PRM not supported
LS-DYNA
The systems cards can be previewed, but not edited. Supported Card Solver Description Supported Parameters Notes
*DEFINE_COORDIN Define a local coordinate ATE_ system with three nodes. NODES *DEFINE_COORDIN Define a local coordinate ATE_ system with three points. SYSTEM *DEFINE_COORDIN Define a local coordinate ATE_ system with two vectors. VECTOR
MADYMO
925

Altair Engineering
Supported Card
Solver Description
Notes
FE_CRDSYS
Coordinate system for FE elements. Orientation defined by the direction cosine matrix. NAME, Xaxis, Yaxis, Zaxis, inputsystemid, Xglobal, Yglobal, Zglobal, Xpos, Ypos, Zpos Use either the create or create dependent method to create this type of element. To define a coordinate system relative to another coordinate system (e.g. an ORIENT_INERTIA relative to the body local system of a BODY.RIGID) use the assign method: choose systs and select the child coordinate system(s), select the parent coordinate system, and click set reference . Use either the create or create dependent method to create this type of element. To define a coordinate system relative to another coordinate system (e.g. an ORIENT_INERTIA relative to the body local system of a BODY.RIGID) use the assign method: choose systs and select the child coordinate system(s), select the parent coordinate system, and click set reference . Use either the create or create dependent method to create this type of element. To define a coordinate system relative to another coordinate system (e.g. an ORIENT_INERTIA relative
ORIENTATION. MATRIX
ORIENTATION. SCREW_AXIS
Orientation defined by a screw axis and a rotation angle.
ORIENTATION. Orientation defined by up to SUCCESSIVE_ROT three successive rotations.
Altair Engineering

926
to the body local system of a BODY.RIGID) use the assign method: choose systs and select the child coordinate system(s), select the parent coordinate system, and click set reference . ORIENTATION. VECTOR Orientation defined by two vectors. Use either the create or create dependent method to create this type of element. To define a coordinate system relative to another coordinate system (e.g. an ORIENT_INERTIA relative to the body local system of a BODY.RIGID) use the assign method: choose systs and select the child coordinate system(s), select the parent coordinate system, and click set reference .
Nastran
Supported Card
Solver Description
Supported Parameters N/A
Notes
CORD1R
Defines a rectangular coordinate system using three grid points. Defines a rectangular coordinate system using the coordinates of three points. Defines a cylindrical coordinate system using three grid points. Defines a cylindrical coordinate system using the
CORD2R
N/A
CORD1C
N/A
CORD2C
N/A
927

Altair Engineering
coordinates of three points . CORD1S Defines a spherical coordinate N/A system by reference to three grid points. Defines a spherical coordinate N/A system using the coordinates of three points.
CORD2S
PAM-CRASH
Supported Card
Solver Description
Notes
FRAME /
Local frame definition system collectors
PAM-CRASH frames are placed in the system collector FRAME_systcol.
FRAME /
Local frame definition - system
If a base node is not given, the THLOC card (which refers to FRAME) is used as the base node. If a base node is not found, the first node is used as the base node.
PAM-CRASH 2G
Supported Card
Solver Description
Notes
FRAME /
Local frame definition system collectors
If there is a $HMMOVE directive found for a system and that system collector exists in the model, the system is placed in that collector. Otherwise, a separate system collector is made for the frame.
Altair Engineering

928
FRAME /
Local frame definition systems
NAME, NODS Frame Update Options (Initial Orientation Rotates with Attached Entity, Fixed Orientation, Self-Rotating Orientation) Frame Axis Definitions (Via 2 Vectors, Via 3 Nodes)
If a base node is not given, system is created at the global origin 0, 0, 0. In case of frame definition with nodes, system is created at the first node.
TRSFM /
Select elements and nodes subject to transformation
NAME, Selection, Keyword, D, X, Y, Z, N1, N2 NumDatalines
PERMAS
Supported Card
Solver Description
Supported Parameters {CART|CYL| SPHERE}
Notes
$RSYS
Reference system
Assign the system to nodes to write the RSYS parameter in to the nodal coordinates card $COORD Assign a system as displacement system to nodes to receive this card.
$ROTB
Analysis or displacement system assigned to nodes
RSYS
Samcef
929

Altair Engineering
Supported Cards
Solver Description
Notes
.FRA
Coordinate system definition
Frame type: Cartesian, I frame_nr TYPE Cylindrical, Spherical chosen_frame_type ORIGIN frame_origin V1 axis_definition V2 axis_definition V3 axis_definition
See also Include Files System Collectors
Altair Engineering

930
Vector Collectors
Vector collectors collect and organize vectors. Vector collectors are created, edited, and deleted from the Model Browser and are shown under the VectorCollector folder. Vectors can be organized into a vector collector using the Organize panel. Every vector must be organized into one, and only one, vector collector and therefore are mutually exclusive to a vector collector. Newly created vectors are automatically organized into the current vector collector. The current vector collector is shown bold in the Model Browser. The current vector collector can be set using the Model Browser context sensitive menu on a selected vector collector within the VectorCollector folder. Vector collectors can also be card edited using the Model Browser context sensitive menu on selected vector collectors. Vector collectors have a display state, on or off, which control the display of all vectors organized within the vector collector in the graphics area. The display state of a vector collector can be controlled using the icons next to the vector collector in the Model Browser. Vector collectors also have an active and export state. The active state of a vector collector controls the display state of the vector collector and the listing of the vector collector in the Model Browser and any of its views. If a vector collector is active, then its display state is available to be turned on or off and it is listed in the Model Browser and any of its views. If a vector collector is inactive, then its display state is turned off permanently and it is not listed in the Model Browser or any of its views. If a find operation "finds" an inactive vector collector, that vector collector will automatically be set to active. The export state of a vector collector controls whether or not that vector collector and all vectors organized within the vector collector are exported when the custom export option is utilized. The all export option is not affected by the export state of a vector collector. The active and export states of vector collectors can be controlled using the Entity State Browser. Operations performed on a vector collector affect vectors within the vector collector. For example, if you delete a vector collector, the vectors within the vector collector are also deleted. The data names associated with vector collectors can be found in the data names section of the HyperMesh Reference Guide.
931

Altair Engineering
Solver Card Support for Vector Collectors

MADYMO
Supported Card
Solver Description
Notes
INFLATOR
card image = INFLATOR
AIRBAG_CHAMBER = reference to the parent element.
Altair Engineering

932
Choose the kind of gas mixture composition ( FIXED or VARIABLE). For a variable gas mixture, Type the number of time steps (i.e. the number of related GAS_MIXTURE_VARIAB LE elements). Type the number of gas fractions in the gas mixture (i.e. the number of related GAS_FRACTION elements). INFLATOR.CHAR Inflator characteristic ID, NAME, POLYTROPIC_CON STANT, MASS_FLOW_RATE _FUNC, TEMP_FUNC, EXIT_PRES_FUNC, ASSEMBLY INTERPOLATION, X_SCALE, Y_SCALE, X_SHIFT, Y_SHIFT GAS MIXTURE composition (CONSTANT, VARIABLE) NR_OF_GAS_FRAC TIONS INFLATOR.DEF Injection of gas (mixture) into an airbag chamber. ID, NAME, AIRBAG CHAMBER, POLYTROPIC_CON STANT, SWITCH, MASS_FLOW_RATE _FUNC, TEMP_FUNC, EXIT_PRES_FUNC INTERPOLATION, X_SCALE, Y_SCALE, X_SHIFT,
933

Altair Engineering
Y_SHIFT GAS MIXTURE composition (CONSTANT, VARIABLE) NR_OF_GAS_FRAC TIONS INFLATOR.REF Injection of gas (mixture) into an airbag chamber with includable characteristics. ID, NAME, AIRBAG_CHAMBER , INFLATOR_CHAR, SWITCH
JET
Gas jet type
Nastran
Vector collectors are used to group vectors. For Nastran, vectors can be used to define orientation directions for some 1-D elements and forces, or to define the SNORM card. For orientation vectors, it is not necessary to load any card image data onto the vector collector. For SNORM vectors, you must load the SNORM card image onto the vector collector. Once this is done, all vectors organized into that vector collector will write out as SNORM vectors to the Nastran bulk data file. Supported Card Solver Description Supported Parameters Notes
SNORM
Defines a surface normal vector at a grid point for CQUAD4, CQUADR, CTRIA3, and CTRIAR shell elements.
There is no card image associated with the collector. In order to view the actual SNORM cards, each vector must be individually card edited. Loading the SNORM card image onto the collector assigns the SNORM type onto all of the vectors contained in that collector.
PAM-CRASH 2G
Altair Engineering

934
Supported Card
Solver Description
Supported Parameters lnilev, Maxlev Selection
Notes
ADAPT /
PICK /
TITLE, RESTART_FILE, mppNpic, TIME_PICK, PartSet Substructure definition IDEF, DTSUB, IFRAM, TITLE, SUBDFELEM, IFLAG_OPT
SUBDF /
See also Model Browser Organize panel Entity State Browser HyperMesh Entities & Solver Interfaces Include Files
935

Altair Engineering
Vectors
Vector entities in HyperMesh allow for the definition of a vector in 3D space. Vectors can be created using three methods; base & magnitude, two nodes, or cross-product. The following panels can be used to create and edit vectors: Vectors
The data names associated with vectors can be found in the data names section of the HyperMesh Reference Guide.
Solver Card Support for Vector Collectors

LS-DYNA
Supported Card
Solver Description
Notes
*DEFINE_SD_ORIEN Define orientation vectors for TATION discrete springs and dampers. *DEFINE_VECTOR Define a vector by defining the coordinates of two points.
See also Include Files Vector Collectors
Altair Engineering

936
Beamsection Collectors
Beamsection collectors collect and organize beamsections and are used in HyperBeam to organize 1D beam section data. Beamsection collectors are created, edited, and deleted from HyperBeam or the Model Browser and are shown under the BeamSectionCollector folder. Beamsections can be organized into a beamsection collector using HyperBeam or the Organize panel. Every beamsection must be organized into one, and only one, beamsection collector and therefore are mutually exclusive to a beamsection collector. Newly created beamsections are automatically organized into the current beamsection collector. The current beamsection collector is shown bold in the Model Browser. The current beamsection collector can be set using the Model Browser context sensitive menu on a selected beamsection collector within the BeamsectionCollector folder. Beamsection collectors can also be card edited using the Model Browser context sensitive menu on selected beamsection collectors. Beamsection collectors have an active and export state. The active state of a beamsection collector controls the listing of the beamsection collector in the Model Browser and any of its views. If a beamsection collector is active, then it is listed in the Model Browser and any of its views. If a beamsection collector is inactive, then it is not listed in the Model Browser or any of its views. The export state of a beamsection collector controls whether or not that beamsection collector and all beamsections organized within the beamsection collector are exported when the custom export option is utilized. The all export option is not affected by the export state of a beamsection collector. The active and export states of beamsection collectors can be controlled using the Entity State Browser. Operations performed on a beamsection collector affect beamsections within the beamsection collector. For example, if you delete a beamsection collector, the beamsections within the beamsection collector are also deleted. The data names associated with beamsection collectors can be found in the data names section of the HyperMesh Reference Guide.
937

Altair Engineering
Solver Card Support for Beamsection Collectors

ANSYS
Supported Card
Solver Description
Supported Parameters VAL1, VAL2, VAL3, VAL4, VAL5, VAL6, VAL7
Notes
SECCONTROLS
Overrides program calculated properties.
Altair Engineering

938
SECDATA
Describes the geometry of a section
Geometrical data for the section types supported by SECTYPE. CENT, SHRC, ORIGIN, or USER. SUBTYPE (RECT, QUAD, CSOLID, CTUBE, CHAN, I, Z, L, T, HATS, HREC, ASEC), SECNAME.
SECOFFSET
Defines the section offset for cross sections. Associates section type information with a section ID number.
SECTYPE
MADYMO
Supported Card
Solver Description
Supported Parameters EXTENDED, WRITE_COG_MARK ER, WRITE_FORMAT EXTERNAL_REF, BODY, EXTERNAL_DATA
Notes
ANIMATION
Output activation and format/ file selection for kinematic animation output.
COUPLING_BODY
Data of MADYMO bodies to be transferred to the external coupled program for contact evaluation by the external program.
NR_OF_EXTERNAL_DAT A_S = array size of EXTERNAL_DATA
COUPLING_SURFA CE
Data of planes, hyperEXTERNAL_REF, ellipsoids and hyper-cylinders SURFACE to be transferred. ELLIPSOID, EXTERNAL_DATA, SURFACE type
First choose the type of SURFACE to be referenced, then select the actual SURFACE (ellipsoid or mbplane).
NR_OF_EXTERNAL_DAT NR_OF_EXTERNAL_ A_S = array size of DATA_S EXTERNAL_DATA MOTION_STRUCT_ FE Activation of structural motion FE_MODEL output. elements in MOTION_STRUCT_ OUTPUT_LIST (ALL, NONE, SELECT)
939

Altair Engineering
PRINT_MARKER
Activation of writing marker data to the KIN3 file.
SYSTEM
Although NONE is the initial value for the elements in MARKER_OUTPUT_LIST MARKER_OUTPUT_ when creating a LIST (ALL, NONE, PRINT_MARKER, it is not SELECT) a legal value. Either select the elements in the MARKER_OUTPUT_LIST by setting the NR_OF_MARKER_OUTP UTS and assigning outputblocks of type OUTPUT_MARKER to each MARKER_OUTPUT button, or set the elements in the MARKER_OUTPUT_LIST to be ALL. FE_MODEL Either SELECT the elements in the elements in AIRBAG_CHAMBER_OUT AIRBAG_CHAMBER PUT_LIST by setting the _OUTPUT_LIST NR_OF_AIRBAG_CHAMB (ALL, NONE, ER_OUTPUTS and SELECT) assigning outputblocks of type elements in ELEMENT_OUTPUT OUTPUT_AIRBAG_CHAM _LIST (ALL, NONE, BER to each AIRBAG_CHAMBER_OUT SELECT) PUT button, or set the elements in the elements in ELEMENT_INITIAL_ AIRBAG_CHAMBER_OUT OUTPUT_LIST (ALL, PUT_LIST to be ALL, or indicate the absence of an NONE, SELECT) AIRBAG_CHAMBER_OUT elements in PUT_LIST by leaving the NODE_OUTPUT_LIS elements in the T (ALL, NONE, AIRBAG_CHAMBER_OUT SELECT) PUT_LIST to be NONE. elements in NODE_INITIAL_LIST (ALL, NONE, SELECT) Either SELECT the elements in the ELEMENT_OUTPUT_LIST by setting the NR_OF_ELEMENT_OUTP UTS and assigning outputblocks of type OUTPUT_ELEMENT to
PRINT_OUTPUT_FE Activates output for a certain FE model.
Altair Engineering

940
each ELEMENT_OUTPUT button, or set the elements in the ELEMENT_OUTPUT_LIST to be ALL, or indicate the absence of a ELEMENT_OUTPUT_LIST by leaving the elements in the ELEMENT_OUTPUT_LIST to be NONE. Either SELECT the elements in the ELEMENT_INITIAL_OUTP UT_LIST by setting the NR_OF_ELEMENT_INITIA L_OUTPUTS and assigning outputblocks of type OUTPUT_ELEMENT_INITI AL to each ELEMENT_INITIAL_OUTP UT button, or set the elements in the ELEMENT_INITIAL_OUTP UT_LIST to be ALL, or indicate the absence of a ELEMENT_INITIAL_OUTP UT_LIST by leaving the elements in the ELEMENT_INITIAL_OUTP UT_LIST to be NONE. Either SELECT the elements in the NODE_OUTPUT_LIST by setting the NR_OF_NODE_OUTPUTS and assigning outputblocks of type OUTPUT_NODE to each NODE_OUTPUT button, or set the elements in the NODE_OUTPUT_LIST to be ALL, or indicate the absence of a NODE_OUTPUT_LIST by leaving the elements in the NODE_OUTPUT_LIST to
941

Altair Engineering
be NONE. Either SELECT the elements in the NODE_INITIAL_OUTPUT_ LIST by setting the NR_OF_NODE_INITIAL_O UTPUTS and assigning outputblocks of type OUTPUT_NODE_INITIAL to each NODE_INITIAL_OUTPUT button, or set the elements in the NODE_INITIAL_OUTPUT_ LIST to be ALL, or indicate the absence of a NODE_INITIAL_OUTPUT_ LIST by leaving the elements in the NODE_INITIAL_OUTPUT_ LIST to be NONE. RESULT_ANIMATIO Activation of FE animation N_FE output file. FE_MODEL, WRITE_FORMAT Either SELECT the elements in the ANIMATION_OUTPUT_LIS elements in T by setting the ANIMATION_OUTPU NR_OF_ANIMATION_OUT T_LIST (ALL, NONE, PUTS and assigning SELECT) outputblocks of type OUTPUT_ANIMATION to elements in ANIMATION_GF_OU each ANIMATION_OUTPUT TPUT_ button, or set the elements LIST (ALL, NONE, in the SELECT) ANIMATION_OUTPUT_LIS T to be ALL, or indicate the absence of an ANIMATION_OUTPUT_LIS T by leaving the elements in the ANIMATION_OUTPUT_LIS T to be NONE. Either SELECT the elements in the ANIMATION_GF_OUTPUT _LIST by setting the NR_OF_ANIMATION_GF_ OUTPUTS and assigning
Altair Engineering

942
outputblocks of type OUTPUT_ANIMATION_GF to each ANIMATION_GF_OUTPUT button, or set the elements in the ANIMATION_GF_OUTPUT _LIST to be ALL, or indicate the absence of an ANIMATION_GF_OUTPUT _LIST by leaving the elements in the ANIMATION_GF_OUTPUT _LIST to be NONE. TIME_DURATION_IN File and format selection for JURY duration injury signals. ID, NAME, SYSTEM, WRITE_FORMAT ID, NAME elements in CONTACT_OUTPUT _LIST (ALL, NONE, SELECT) Although NONE is the initial value for the CONTACT_OUTPUT_LIST when creating a TIME_HISTORY_CONTAC T, it is not a legal value. Either SELECT the elements in the CONTACT_OUTPUT_LIST by setting the NR_OF_CONTACT_OUTP UTS and assigning outputblocks of type OUTPUT_CONTACT to each CONTACT_OUTPUT button, or set the elements in the CONTACT_OUTPUT_LIST to be ALL.
TIME_HISTORY_CO Activates time history output NTACT for certain contacts.
TIME_HISTORY_EN Activates time history output ERGY for energy.
ID, NAME
Although NONE is the initial value for the elements in ENERGY_OUTPUT_LIST ENERGY_OUTPUT_ when creating a LIST (ALL, NONE, TIME_HISTORY_ENERGY SELECT) , it is not a legal value. Either SELECT the elements in the ENERGY_OUTPUT_LIST by setting the
943

Altair Engineering
NR_OF_ENERGY_FE_M ODEL_OUTPUTS and assigning outputblocks of type OUTPUT_ENERGY_FE_M ODEL to each ENERGY_OUTPUT button, or set the elements in the ENERGY_OUTPUT_LIST to be ALL. TIME_HISTORY_FE Activates time history output for a particular FE model. ID, NAME, FE_MODEL Either SELECT the elements in the AIRBAG_CHAMBER_OUT elements in PUT_LIST by setting the AIRBAG_CHAMBER NR_OF_AIRBAG_CHAMB _OUTPUT_LIST ER_OUTPUTS and (ALL, NONE, assigning outputblocks of SELECT) type OUTPUT_AIRBAG_CHAM elements in CROSS_SECTION_ BER to each OUTPUT_LIST (ALL, AIRBAG_CHAMBER_OUT PUT button, or set the NONE, SELECT) elements in the AIRBAG_CHAMBER_OUT elements in ELEMENT_OUTPUT PUT_LIST to be ALL, or _LIST (ALL, NONE, indicate the absence of a AIRBAG_CHAMBER_OUT SELECT) PUT_LIST by leaving the elements in elements in the JET_OUTPUT_LIST AIRBAG_CHAMBER_OUT (ALL, NONE, PUT_LIST to be NONE. SELECT) Either SELECT the elements in elements in the NODE_OUTPUT_LIS CROSS_SECTION_OUTP T (ALL, NONE, UT_LIST by setting the SELECT) NR_OF_CROSS_SECTIO N_OUTPUTS and elements in assigning outputblocks of STRAP_OUTPUT_LI type ST (ALL, NONE, OUTPUT_CROSS_SECTI SELECT) ON to each CROSS_SECTION_OUTP UT button, or set the elements in the CROSS_SECTION_OUTP UT_LIST to be ALL, or
Altair Engineering

944
indicate the absence of a CROSS_SECTION_OUTP UT_LIST by leaving the elements in the CROSS_SECTION_OUTP UT_LIST to be NONE. Either SELECT the elements in the ELEMENT_OUTPUT_LIST by setting the NR_OF_ELEMENT_OUTP UTS and assigning outputblocks of type OUTPUT_ELEMENT to each ELEMENT_OUTPUT button, or set the elements in the ELEMENT_OUTPUT_LIST to be ALL, or indicate the absence of a ELEMENT_OUTPUT_LIST by leaving the elements in the ELEMENT_OUTPUT_LIST to be NONE. Either SELECT the elements in the JET_OUTPUT_LIST by setting the NR_OF_JET_OUTPUTS and assigning outputblocks of type OUTPUT_JET to each JET_OUTPUT button, or set the elements in the JET_OUTPUT_LIST to be ALL, or indicate the absence of a JET_OUTPUT_LIST by leaving the elements in the JET_OUTPUT_LIST to be NONE. Either SELECT the elements in the NODE_OUTPUT_LIST by setting the NR_OF_NODE_OUTPUTS
945

Altair Engineering
and assigning outputblocks of type OUTPUT_NODE to each NODE_OUTPUT button, or set the elements in the NODE_OUTPUT_LIST to be ALL, or indicate the absence of a NODE_OUTPUT_LIST by leaving the elements in the NODE_OUTPUT_LIST to be NONE. Either SELECT the elements in the STRAP_OUTPUT_LIST by setting the NR_OF_STRAP_OUTPUT S and assigning outputblocks of type OUTPUT_STRAP to each STRAP_OUTPUT button, or set the elements in the STRAP_OUTPUT_LIST to be ALL, or indicate the absence of a STRAP_OUTPUT_LIST by leaving the elements in the STRAP_OUTPUT_LIST to be NONE. TIME_HISTORY_INJ File and format selection for URY injury signals. ID, NAME, SYSTEM, WRITE_FORMAT ID, NAME, SYSTEM Either SELECT the elements in the elements in BELT_OUTPUT_LIST by BELT_OUTPUT_LIST setting the (ALL, NONE, NR_OF_BELT_OUTPUTS SELECT) and assigning outputblocks of type elements in BODY_OUTPUT_LIS OUTPUT_BELT to each BELT_OUTPUT button, or T (ALL, NONE, set the elements in the SELECT) BELT_OUTPUT_LIST to be ALL, or indicate the elements in BODY_REL_OUTPU absence of a T_LIST (ALL, NONE, BELT_OUTPUT_LIST by
TIME_HISTORY_MB Activates time history output for a particular multi-body system.
Altair Engineering

946
SELECT)
elements in CONTROL_SYSTEM _ Either SELECT the OUTPUT_LIST (ALL, elements in the NONE, SELECT) BODY_OUTPUT_LIST by setting the elements in NR_OF_BODY_OUTPUTS JOINT_DOF_OUTPU and assigning T_LIST (ALL, NONE, outputblocks of type SELECT) OUTPUT_BODY to each BODY_OUTPUT button, or elements in RESTRAINT_OUTPU set the elements in the T_LIST (ALL, NONE, BODY_OUTPUT_LIST to be ALL, or indicate the SELECT) absence of a BODY_OUTPUT_LIST by elements in SENSOR_OUTPUT_ leaving the elements in the BODY_OUTPUT_LIST to LIST (ALL, NONE, be NONE. SELECT)
leaving the elements in the BELT_OUTPUT_LIST to be NONE.
Either SELECT the elements in the BODY_REL_OUTPUT_LIS T by setting the NR_OF_BODY_REL_OUT PUTS and assigning outputblocks of type OUTPUT_BODY_REL to each BODY_REL_OUTPUT button, or set the elements in the BODY_REL_OUTPUT_LIS T to be ALL, or indicate the absence of a BODY_REL_OUTPUT_LIS T by leaving the elements in the BODY_REL_OUTPUT_LIS T to be NONE. Either SELECT the elements in the CONTROL_SYSTEM_OUT PUT_LIST by setting the NR_OF_CONTROL_SYST EM_OUTPUTS and assigning outputblocks of
947

Altair Engineering
type OUTPUT_CONTROL_SYS TEM to each CONTROL_SYSTEM_OUT PUT button, or set the elements in the CONTROL_SYSTEM_OUT PUT_LIST to be ALL, or indicate the absence of a CONTROL_SYSTEM_OUT PUT_LIST by leaving the elements in the CONTROL_SYSTEM_OUT PUT_LIST to be NONE. Either SELECT the elements in the JOINT_DOF_OUTPUT_LIS T by setting the NR_OF_JOINT_DOF_OUT PUTS and assigning outputblocks of type OUTPUT_JOINT_DOF to each JOINT_DOF_OUTPUT button, or set the elements in the JOINT_DOF_OUTPUT_LIS T to be ALL, or indicate the absence of a JOINT_DOF_OUTPUT_LIS T by leaving the elements in the JOINT_DOF_OUTPUT_LIS T to be NONE. Either SELECT the elements in the JOINT_CONSTRAINT_OUT PUT_LIST by setting the NR_OF_JOINT_CONSTRA INT_OUTPUTS and assigning outputblocks of type OUTPUT_JOINT_CONSTR AINT to each JOINT_CONSTRAINT_OUT PUT button, or set the elements in the JOINT_CONSTRAINT_OUT
Altair Engineering

948
PUT_LIST to be ALL, or indicate the absence of a JOINT_CONSTRAINT_OUT PUT_LIST by leaving the elements in the JOINT_CONSTRAINT_OUT PUT_LIST to be NONE. MUSCLE_OUTPUT_LIST is not yet supported. Either SELECT the elements in the RESTRAINT_OUTPUT_LIS T by setting the NR_OF_RESTRAINT_OUT PUTS and assigning outputblocks of type OUTPUT_RESTRAINT to each RESTRAINT_OUTPUT button, or set the elements in the RESTRAINT_OUTPUT_LIS T to be ALL, or indicate the absence of a RESTRAINT_OUTPUT_LIS T by leaving the elements in the RESTRAINT_OUTPUT_LIS T to be NONE. Either SELECT the elements in the SENSOR_OUTPUT_LIST by setting the NR_OF_SENSOR_OUTPU TS and assigning outputblocks of type OUTPUT_SENSOR to each SENSOR_OUTPUT button, or set the elements in the SENSOR_OUTPUT_LIST to be ALL, or indicate the absence of a SENSOR_OUTPUT_LIST by leaving the elements in the SENSOR_OUTPUT_LIST
949

Altair Engineering
to be NONE. TIME_HISTORY_SY Activates time history output STEM for systems. ID, NAME Although NONE is the initial value for the elements in SYSTEM_COG_OUTPUT_ SYSTEM_COG_OUT LIST when creating a PUT_ TIME_HISTORY_SYSTEM LIST (ALL, NONE, , it is not a legal value. SELECT) Either SELECT the elements in the SYSTEM_COG_OUTPUT_ LIST by setting the NR_OF_SYSTEM_COG_ OUTPUTS and assigning outputblocks of type OUTPUT_SYSTEM_COG to each SYSTEM_COG_OUTPUT button, or set the elements in the SYSTEM_COG_OUTPUT_ LIST to be ALL. ID, NAME, WRITE_FORMAT
TIME_HISTORY_TIM Output activation and format/ E_ file selection for time-step. STEP
PAM-CRASH 2G
Supported Card
Solver Description
Supported Parameters Ftol, TITLE, StartPt, Ns, Ni, FRICPR, TOLSLP, EndPt, Ne NUM_SLIPRG
Notes
BELTS /
Output activation and format/ file selection for kinematic animation output.
See also Model Browser Organize panel Entity State Browser
Altair Engineering

950
HyperMesh Entities & Solver Interfaces Include Files HyperBeam
951

Altair Engineering
Beamsections
Beamsection entities in HyperMesh store 1D beam cross-section data. Beamsections are typically created in HyperMesh and edited in HyperBeam. Beamsections can be created from geometry, elements, or from solver standard sections (i.e. I-Sections, H-Sections, etc.) in HyperMesh. The following beamsections can be defined in HyperBeam; Generic sections, Shell sections, Solid sections, and Standard sections. Generic sections allow users to define sections without defining actual cross-section geometry. Areas, inertias, centroids, and other coefficients are supported directly through spreadsheet data entry of values. Shell sections allow users to define thin cross-sections with geometric lines or 1D elements in HyperMesh. Once the cross-section is created in HyperMesh, it can further further be edited in HyperBeam.
Solid sections allow for users to define solid cross-sections with surfaces, lines that form a closed loop, or 2D elements in HyperMesh. Once the cross-section is created in HyperMesh is can further be edited in HyperBeam.
Altair Engineering

952
953

Altair Engineering
Standard sections allow users to automatically define solver supported cross-sections. Each supported solver interface in HyperMesh has a library of supported solver cross-sections. For standards sections, only the dimensions of the section are necessary as input.
Altair Engineering

954
On import in HyperMesh, each 1D beam property card within a solver deck is automatically imported as a beamsection entity and a property entity with associated beamsection. The beamsection entity holds the 1D beam section data (A, I, etc..., and/or Dimensions) and is associated to the property entity which has a 1D property card image. The beamsection association to a property is what transfers the 1D section data to the 1D property solver card for export. Editing of all 1D beam section data is accomplished through HyperBeam. The following panels can be used to create and edit beamsections: HyperBeam The data names associated with beamsections can be found in the data names section of the HyperMesh Reference Guide.
See also Include Files Beamsection Collectors HyperBeam
955

Altair Engineering
Multibodies
Multibodies collect and organize ellipsoids, multibody planes, and multibody joints and are typically used in multi-body analysis. Multibodies are created, edited, and deleted from the Model Browser and are shown under the Multibody folder. Ellipsoids, multibody planes, and multibody joints can be organized into a multibody using the Organize panel. Every ellipsoid, multibody plane, and multibody joint must be organized into one, and only one, multibody and therefore are mutually exclusive to a multibody. Newly created ellipsoids, multibody planes, and multibody joints are automatically organized into the current multibody. The current multibody is shown bold in the Model Browser. The current multibody can be set using the Model Browser context sensitive menu on a selected multibody within the Multibody folder. Multibodies can also be card edited using the Model Browser context sensitive menu on selected multibodies. Multibodies have a display state, on or off, which control the display of all ellipsoids, multibody planes, and multibody joints organized within the multibody in the graphics area. The display state of a multibody can be controlled using the icons next to the multibody in the Model Browser. Multibodies also have an active and export state. The active state of a multibody controls the display state of the multibody and the listing of the multibody in the Model Browser and any of its views. If a multibody is active, then its display state is available to be turned on or off and it is listed in the Model Browser and any of its views. If a multibody is inactive, then its display state is turned off permanently and it is not listed in the Model Browser or any of its views. If a find operation "finds" an inactive multibody, that multibody will automatically be set to active. The export state of a multibody controls whether or not that multibody and all ellipsoids, multibody planes, and multibody joints organized within the multibody are exported when the custom export option is utilized. The all export option is not affected by the export state of a multibody. The active and export states of multibodies can be controlled using the Entity State Browser. Operations performed on a multibody collector affect ellipsoids, multibody planes, and multibody joints within the multibody collector. For example, if you delete a multibody collector, the ellipsoids, multibody planes, and multibody jonts within the multibody collector are also deleted. The data names associated with multibodies can be found in the data names section of the HyperMesh Reference Guide.
Altair Engineering

956
Creating a Multibody Collector The create subpanel is used for creating multibody collectors. create provides four data blocks for defining: the collector's name, card image type, center of gravity, and the bodys local coordinate system. Moments of inertia and other rigid body properties are defined in the multibody collectors card image, which is access through the Card panel after the multibody collector has been created. creation method: assigns the multibody type specified in the card image= field. The types of multibody collectors available are dependent on the loaded solver interface specified as a template file. The most common type of multibody collector is a "rigid body". Setting creation method: to no card image specifies that a multibody collector type is not assigned at the time of creation, but one can be assigned later in the card image subpanel. Setting creation method: to same as assigns a copy of the card image of another multibody collector to the created collector. Using or not using a card image has no bearing on how multibody collectors behave and only effect data being exported.
957

Altair Engineering
center of gravity: provides an N1 node/geometry selection box to define the x, y, and z, location of the center of gravity. The N1 box contains the same functionality as the N1 selection buttons found elsewhere in the program. To define a center of gravity location, select a node on in the model window. If only surfaces or lines are available for selection, click and hold the left mouse button in the model window until the cursor becomes a square, drag the cursor over geometry to select it, release the mouse button, and click anywhere on the geometry to define a location. For an alternative method to define the center of gravity, click on the edit button under the N1 selection box to bring up x= , y= , and z= entry fields. Note: The element handles option in the modeling subpanel (Options panel) allows you to display the center of gravity for multibody collectors and text labels for 1D elements.
body local system: defines the body local coordinate system of the created body by assigning a local coordinate system entity to the multibody collector. There are three ways to define the bodys orientation: body system assigns a copy of the local coordinate system assigned to the current multibody collector specified in the Global panel. duplicate system ensures a unique coordinate system is assigned to the created body by creating a duplicate of the selected coordinate system and assigning this duplicated coordinate system to the created body. use system assigns the selected system to the created body.
Updating a Multibody Collector The update subpanel is provided to modify the bodys local coordinate system and center of gravity. The same fields and options available in the create subpanel are also available in the update subpanel.
Solver Card Support for Multibody Collectors

MADYMO
Supported Card
Solver Description
Supported Parameters FE_MODEL, MODAL_STIF, MODAL_DAMP, LOAD.BODY_ACC
Notes
BODY. DEFORMABLE
Deformable body.
body local system and center of gravity are not used. Enter the number of MODEs in MODE_LIST and select each applicable MODE element. Select the DAMPING check box to apply MODAL_DAMP.
Altair Engineering

958
BODY. FLEXIBLE_BEAM
Flexible beam.
FE_MODEL, LINE3 body local system and (N1, N2, N3), center of gravity are not DEF_NODE_LIST, used. AREA, Ml11, l11, l22, l33, STIF_AXIAL, DENSITY, E, NU, DAMP_COEF LOAD.BODY_ACC
BODY.RIGID
This element contains the information necessary to define a unique rigid body: mass, inertia matrix and location of center of gravity.
ORIENT_INERTIA, MASS, INTERIA XX, YY, ZZ, XY, YZ, ZX LOAD.BODY_ACC
body local system = ORIENT_INERTIA. If you 'use' the referenced system, no system of a JOINT or BODY should be selected. center of gravity = CENTRE_OF_GRAVITY
JOINT SURFACE. CYLINDER Hyper-elliptical cylinder.
See also Model Browser Organize panel Entity State Browser Browsers HyperMesh Entities & Solver Interfaces Include Files
959

Altair Engineering
Ellipsoids
Solver Card Support for Ellipsoids
Currently no solver support is available.
See also Include Files Multibodies
Altair Engineering

960
Multibody Planes
Solver Card Support for Multibody Planes
MADYMO
Supported Card
Solver Description
Notes
SURFACE.PLANE
Rectangular plane
multibody = BODY N1 = POINT_1 N2 = POINT_2 N3 = POINT_3 To create a SURFACE under the SYSTEM. REF_SPACE, a reference to a null body must be selected because a reference to a multibody is required when creating a multibody plane. A null body can be created like any other BODY (card image is not relevant and should not be used), Nullbody should be put under the SYSTEM. REF_SPACE assembly.
961

Altair Engineering
Multibody Joints
Solver Card Support for Multibody Joints
MADYMO
Supported Card
Solver Description
Notes
JOINT.BRAC
The syst and card image = BRAC multibody to be specified at parent and child refer to the CRDSYS_OBJECT_1 and CRDSYS_OBJECT_2 related elements. The syst and multibody to be specified at parent and child refer to the CRDSYS_OBJECT_1 and CRDSYS_OBJECT_2 related elements. The syst and multibody to be specified at parent and child refer to the CRDSYS_OBJECT_1 and CRDSYS_OBJECT_2 related elements. card image = CYLI D1 and R1 can not be changed, because they are defined by the position and orientation of the systems connected by the JOINT. card image = FREE D1 through D3, R1 through R3 and ORIENT can not be changed, because they are defined by the position and orientation of the systems connected by the JOINT. When importing a model containing non-zero values for Q1 through Q7, these values are translated into the values for displacement and rotation; since no values for Q1 through Q7 can be set, no values will be exported. card image = FREE D1 through D3, R1 through R3 and ORIENT can not
JOINT.CYLI
JOINT.FREE
JOINT. FREE_BRYANT
The syst and multibody to be specified at parent
Altair Engineering

962
and child refer to the CRDSYS_OBJECT_1 and CRDSYS_OBJECT_2 related elements.
be changed, because they are defined by the position and orientation of the systems connected by the JOINT. When importing a model containing non-zero values for Q1 through Q7, these values are translated into the values for displacement and rotation; since no values for Q1 through Q7 can be set, no values will be exported. card image = FREE D1 through D3, R1 through R3 and ORIENT can not be changed, because they are defined by the position and orientation of the systems connected by the JOINT. When importing a model containing non-zero values for Q1 through Q7, these values are translated into the values for displacement and rotation; since no values for Q1 through Q7 can be set, no values will be exported. card image = FREE_BRYANT D1 through D3, R1 through R3 and ORIENT can not be changed, because they are defined by the position and orietation of the systems connected by the JOINT. Any JOINT. FREE_ROT_DISP is translated into a JOINT. FREE during import of the model. When importing a model containing non-zero values for Q1 through Q7, these values are translated
JOINT. FREE_EULER
The syst and multibody to be specified at parent and child refer to the CRDSYS_OBJECT_1 and CRDSYS_OBJECT_2 related elements.
JOINT. FREE_ROT_DISP
963

Altair Engineering
into the values for displacement and rotation; since no values for Q1 through Q7 can be set, no values will be exported. JOINT.PLAN The syst and multibody to be specified at parent and child refer to the CRDSYS_OBJECT_1 and CRDSYS_OBJECT_2 related elements. The syst and multibody to be specified at parent and child refer to the CRDSYS_OBJECT_1 and CRDSYS_OBJECT_2 related elements. The syst and multibody to be specified at parent and child refer to the CRDSYS_OBJECT_1 and CRDSYS_OBJECT_2 related elements. card image = PLAN R1, D2 and D3 can not be changed, because they are defined by the position and orientation of the systems connected by the JOINT. card image = REVO R1 can not be changed, because it is defined by the position and orientation of the systems connected by the JOINT.
JOINT.REVO
JOINT.REVO_TRAN
card image = REVO_TRAN D1 and R2 can not be changed, because they are defined by the position and orientation of the systems connected by the JOINT. card image = SPHE R1 through R3 and ORIENT can not be changed, because they are defined by the position and orientation of the systems connected by the JOINT. When importing a model containing non-zero values for Q1 through Q4, these values are translated into the values for rotation; since no values for Q1 through Q4 can be set, no
JOINT.SPHE
Altair Engineering

964
values will be exported. JOINT. SPHE_BRYANT The syst and multibody to be specified at parent and child refer to the CRDSYS_OBJECT_1 and CRDSYS_OBJECT_2 related elements. card image = SPHE_BRYANT R1 through R3 can not be changed, because they are defined by the position and orientation of the systems connected by the JOINT. card image = SPHE_EULER R1 through R3 can not be changed, because they are defined by the position and orientation of the systems connected by the JOINT. card image = TRAN D1 can not be changed, because it is defined by the position and orientation of the systems connected by the JOINT.
JOINT. SPHE_EULER
JOINT.TRAN
The syst and multibody to be specified at parent and child refer to the CRDSYS_OBJECT_1 and CRDSYS_OBJECT_2 related elements. The syst and multibody to be specified at parent and child refer to the CRDSYS_OBJECT_1 and CRDSYS_OBJECT_2 related elements.
JOINT.TRAN_REVO
card image = TRAN_REVO D1 and R2 can not be changed, because they are defined by the position and orientation of the systems connected by the JOINT. card image = TRAN_UNIV D1, R2 and R3 can not be changed, because they are defined by the position and orientation of the systems connected by the JOINT.
JOINT.TRAN_UNIV
The syst and multibody to be specified at parent and child refer to the CRDSYS_OBJECT_1 and CRDSYS_OBJECT_2 related
965

Altair Engineering
JOINT.UNIV
The syst and multibody to be specified at parent and child refer to the CRDSYS_OBJECT_1 and CRDSYS_OBJECT_2 related elements. The syst and multibody to be specified at parent and child refer to the CRDSYS_OBJECT_1 and CRDSYS_OBJECT_2 related elements.
card image = UNIV R1 and R2 can not be changed, because they are defined by the position and orientation of the systems connected by the JOINT. card image = UNIV_TRAN D1, R2 and R3 can not be changed, because they are defined by the position and orientation of the systems connected by the JOINT.
JOINT.UNIV_TRAN
JOINT.USER
The syst and card image = USER multibody to be specified at parent and child refer to the CRDSYS_OBJECT_1 and CRDSYS_OBJECT_2 related elements.
Altair Engineering

966
Bags
Bags collect and organize entities. The entities that are permissible for a bag entity to collect are determined by the configuration of the bag. There are ten configurations of a bag entity which can be created as listed below. Bags are shown under the Bag folder within the Model Browser.
Bag Configurations Generic Optimization FBD Forces (All Loads) FBD Forces (Applied Loads) FBD Forces (Reaction Loads) FBD Displacements Resultant Force & Moment FBD Cross-section ADM Part ADM Material Currently, only the optimization configuration of bag entity can be created, edited, and deleted. Optimization bag entities can be created, edited, and deleted using the Optimization Browser View within the Model Browser. All other configurations of bag entities can be created, edited, and deleted using the Tcl Modify Commands *bagcreate and *bagentityupdate. Bags have a display state, on or off, which control the display state of all entities organized within the bag in the graphics area. The display state of a bag can be controlled using the icons next to the bag in the Model Browser. Bags also have an active and export state. The active state of a bag controls the display state of the bag and the listing of the bag and its collected entities in the Model Browser and any of its views. If a bag is active, then its display state is available to be turned on or off and the bag and its collected entities are listed in the Model Browser and any of its views. If a bag is inactive, then its display state is turned off permanently (and hence also all its collected entities) and the bag and its collected entities are not listed in the Model Browser or any of its views. The export state of a bag controls whether or not that bag and its collected entities are exported when the custom export option is utilized. The all export option is not affected by the export state of a bag. The active and export states of bags can be controlled using the Entity State Browser. Operations performed on a bag do not affect the entities collected within the bag. For example, if you delete a bag, the entities collected within the bag are not deleted. The data names associated with bags can be found in the data names section of the HyperMesh Reference Guide.
967

Altair Engineering
Solver Card Support for Bags

Currently no solver support is available.
See also Optimization Browser View Model Browser Entity State Browser HyperMesh Entities & Solver Interfaces Include Files
Altair Engineering

968
Generic
Generic configurations of the bag entity can collect and organize any entities, including other bag entities. Generic configurations of the bag entity can currently only be created, edited, and deleted using the Tcl Modify Commands *bagcreate and *bagentityupdate. The data names associated with bags can be found in the data names section of the HyperMesh Reference Guide.
See also Include Files Bags Collectors and Collected Entities Named Entities Morphing Entities Optimization Entities
969

Altair Engineering
Optimization Problem
Optimization problem configurations of the bag entity can collect and organize any of the Optimization entities; Design Variables Design Variable Links Objective Design Variable Property Relationships Objective References Optimization Constraints Optimization Constraint Screenings Optimization Controls Optimization Equations Optimization Responses Optimization Table Entries Discrete Design Variables
Optimization problem configurations of the bag entity can be created, edited, and deleted using the Optimization Browser View within the Model Browser. The data names associated with bags can be found in the data names section of the HyperMesh Reference Guide.
See also Optimization Browser View Model Browser Include Files Bags Optimization Entities
Altair Engineering

970
FBD Forces (All Loads)

FBD forces (all loads) configurations of the bag entity can collect and organize nodes element sets systems load collectors
FBD forces (all loads) configurations of the bag entity can currently only be created, edited, and deleted using the Tcl Modify Commands *bagcreate and *bagentityupdate. The data names associated with bags can be found in the data names section of the HyperMesh Reference Guide.
See also Include Files Bags Collector and Collected Entities Named Entities
971

Altair Engineering
FBD Forces (Applied Loads Only)

FBD forces (applied loads only) configurations of the bag entity can collect and organize: nodes element sets systems load collectors.
FBD forces (applied loads only) configurations of the bag entity can currently only be created, edited, and deleted using the Tcl Modify Commands *bagcreate and *bagentityupdate. The data names associated with bags can be found in the data names section of the HyperMesh Reference Guide.
Altair Engineering

972
FBD Forces (Reaction Loads Only)

FBD forces (reaction loads only) configurations of the bag entity can collect and organize: nodes element sets systems load collectors
FBD forces (reaction loads only) configurations of the bag entity can currently only be created, edited, and deleted using the Tcl Modify Commands *bagcreate and *bagentityupdate. The data names associated with bags can be found in the data names section of the HyperMesh Reference Guide.
973

Altair Engineering
FBD Displacements
FBD displacement configurations of the bag entity can collect and organize: node sets element sets systems load collectors
FBD displacement configurations of the bag entity can currently only be created, edited, and deleted using the Tcl Modify Commands *bagcreate and *bagentityupdate. The data names associated with bags can be found in the data names section of the HyperMesh Reference Guide.
Altair Engineering

974
Resultant Force & Moment

Resultant Force & Moment configurations of the bag entity can collect and organize; systems load collectors FBD cross-section bag entities
Resultant Force & Moment configurations of the bag entity can currently only be created, edited, and deleted using the Tcl Modify Commands *bagcreate and *bagentityupdate. The data names associated with bags can be found in the data names section of the HyperMesh Reference Guide.
975

Altair Engineering
FBD Cross-section
FBD cross-section configurations of the bag entity can collect and organize; nodes node sets element sets systems
FBD cross-section configurations of the bag entity can currently only be created, edited, and deleted using the Tcl Modify Commands *bagcreate and *bagentityupdate. The data names associated with bags can be found in the data names section of the HyperMesh Reference Guide.
Altair Engineering

976
ADM Part
ADM part configurations of the bag entity can collect and organize any entities, including other bag entities. ADM part configurations of the bag entity can currently only be created, edited, and deleted using the Tcl Modify Commands *bagcreate and *bagentityupdate. The data names associated with bags can be found in the data names section of the HyperMesh Reference Guide.
See also Include Files Bags Collector and Collected Entities Named Entities Morphing Entities Optimization Entities
977

Altair Engineering
ADM Material
ADM material configurations of the bag entity can collect and organize any entities, including other bag entities. ADM material configurations of the bag entity can currently only be created, edited, and deleted using the Tcl Modify Commands *bagcreate and *bagentityupdate. The data names associated with bags can be found in the data names section of the HyperMesh Reference Guide.
See also Include Files Bags Collector and Collected Entities Named Entities Morphing Entities Optimization Entities
Altair Engineering

978
Named Entities
Named entities are entities which are given a name but are not collected or organized into containers. Examples of named entities include materials and properties. Some named entities also have a display state, on or off, which control the display of that entity in the graphics area. The display state of named entities can be controlled using the Model Browser. All named entities have active and export states. The active state of a named entity controls the display state of the named entity and the listing of the named entity in the Model Browser and any of its views. The export state of a named entity controls the export of that entity to a solver deck. The active and export states of named entities can be controlled using the Entity State Browser.
Named entities Blocks Curves Contact Surfaces Control Cards Control Volumes Groups Load Steps Materials Output Blocks Plies Plots Properties Sensors Sets Tags Titles
See also Model Browser Entity State Browser HyperMesh Entities & Solver Interfaces Include Files
979

Altair Engineering
Blocks
Block entities are enclosed volumes represented by a "box" or a block. Blocks can be created by picking diagonal corner nodes, or by entering diagonal corner coordinates which define the block. Nodes, elements, points, lines, surfaces, solids, loads, equations, systems, vectors, and connectors can be reviewed and saved within a block. Blocks are shown under the Block folder within the Model Browser. Blocks have a display state, on or off, which controls the display of a block in the graphics area. The display state of a block can be controlled using the icon next to the block entity in the Model Browser. Blocks also have an active and export state. The active state of a block controls the display state of the block and the listing of the block in the Model Browser and any of its views. If a block entity is active, then its display state is available to be turned on or off and it is listed in the Model Browser and any of its views. If a block entity is inactive, then its display state is turned off permanently and it is not listed in the Model Browser or any of its views. The export state of a block entity controls whether or not that block is exported when the custom export option is utilized. The all export option is not affected by the export state of a block. The active and export states of block entities can be controlled using the Entity State Browser.
Altair Engineering

980
The following panels can be used to create and edit blocks: Blocks
The data names associated with blocks can be found in the data names section of the HyperMesh Reference Guide.
Solver Card Support for Blocks

The supported RADIOSS cards in RADIOSS (Block Format) 100 are listed below. You can quickly create these cards by right-clicking in the Solver Browser and selecting Create Cards.
Supported Card
Solver Description
Notes
/GRBEAM/BOX
Describes the beam groups box Describes the beam groups box Describes the brick groups box Describes the brick groups box Describes the node groups box Describes the quad groups box Describes the quad groups box Describes the 3 node shell groups - box
/GRBEAM/BOX2
/GRBRIC/BOX
/GRBRIC/BOX2
/GRNOD/BOX
/GRQUAD/BOX
/GRQUAD/BOX2
/GRSH3N/BOX
981

Altair Engineering
/GRSH3N/BOX2
Describes the 3 node shell groups - box Describes the shell groups box Describes the shell groups box Describes the spring groups box Describes the spring groups box Describes the truss groups box Describes the truss groups box Definition of the line - box Definition of the line - box Describes the surface definition on shell elements by box. Describes the surface definition on shell elements by box. Describes the surfaced definition on solid elements both interior and exterior face by box. Describes the surface definition on solid elements exterior face by box.
/GRSHEL/BOX
/GRSHEL/BOX2
/GRSPRI/BOX
/GRSPRI/BOX2
/GRTRUS/BOX
/GRTRUS/BOX2
/LINE/BOX /LINE/BOX2 /SURF/BOX
/SURF/BOX2
/SURF/BOX/ALL
/SURF/BOX/EXT
LS-DYNA
Altair Engineering

982
Supported Card
Solver Description Defines a box to select entities in the model
Notes
*DEFINE_BOX
See also Model Browser Entity State Browser HyperMesh Entities & Solver Interfaces Include Files
983

Altair Engineering
Curves
Curve entities are used to define and store xy data and are associated with a plot entity. Curves are shown under the Curve folder within the Model Browser. Curves do not have a display state. However, the display of a curve in a xy plot window is controlled by the display state and active state of its associated plot. Curves have an active and export state. The active state of a curve controls the display of a curves within its associated plot and the listing of the curve in the Model Browser and any of its views. If a curve entity is active, then it is displayed within its associated plot and it is listed in the Model Browser and any of its views. If a curve entity is inactive, then it is not displayed within its associated plot and it is not listed in the Model Browser or any of its views. The export state of a curve entity controls whether or not that curve is exported when the custom export option is utilized. The all export option is not affected by the export state of a curve. The active and export states of curve entities can be controlled using the Entity State Browser.
Altair Engineering

984
The following panels can be used to create and edit curves: Read Curves Results Curves Simple Math Edit Curves Curve Attribs Query Curves Integrate
985

Altair Engineering
The data names associated with curves can be found in the data names section of the HyperMesh Reference Guide.
Solver Card Support for Curves

Supported Card
Solver Description
Notes
/FUNCT
Input formats to define the function Describes the function scale and shift
/MOVE_FUNC
Multi-body dynamics curves are represented as curves. Supported Card Solver Description Supported Parameters Notes
MBCRV
Defines a data curve for use in multi-body dynamics simulations.
Supported as a curve entity. Defined through the Curve Editor utility.
Outputting curves creates a function card in RADIOSS (Fixed Format). Input and output of function cards is supported. HyperMesh XY curves that are referenced by a load, material, property, or rigid wall, for example, are output. References to curves during input are preserved and are output with the card.
Abaqus
Curves are exported as *AMPLITUDE card in the Abaqus input file.
Altair Engineering

986
Supported Card
Solver Description
Supported Parameters NAME DEFINITION = TABULAR,
Notes
*AMPLITUDE
Define an amplitude curve
Standard, Explicit
The TABULAR definition reads either pairwise DEFINITION = entries (new) or four pairs SMOOTH STEP/ of values per dataline (old). EQUALLY SPACED, The EQUALLY SPACED TIME, VALUE, option has been updated FIXED INTERVAL, to the new format as well. BEGIN The old format is required by users using pre 6.9 Abaqus solver. The reader can read both formats. The card will be exported the same way as it was imported. The card image allows users to switch between both formats.
LS-DYNA
Output of curves creates a *DEFINE_CURVE or Structured Card 22 using Option 0 *DEFINE_CURVE can be changed to *DEFINE_TABLE in the card previewer. When DEFINE_CURVE is changed to DEFINE_TABLE, the number of curves the table should contain depends on the XY curves that are referenced by a load, material, component, property, and so on are output Upon input, the *DEFINE_CURVE and *DEFINE_TABLE/Card 22 cards are read and placed in a plot called LS-DYNA Load Curves Upon input, references to curves are preserved and are output along with the card, such as material, component, property, load and so on To export curves, click the Export icon and select the type of file to export as Curves. The following keywords are supported: Supported Card Solver Description Supported Parameters SIDR, SFA, SFO, OFFA, OFFO, DATTYP Notes
*DEFINE_CURVE
Define a curve
987

Altair Engineering
CurveTableHelp DEFINE_TABLE Option (None, TRIM, SMOOTH) Title *DEFINE_CURVE_ SMOOTH Define a smoothly varying curve using few parameters. SIDR, DIST, TSTART, TEND, TRISE, V0 CurveTableHelp DEFINE_TABLE Title *DEFINE_CURVE_T Define a curve for trimming. RIM TCTYPE, TFLG, TDIR, TCTOL, IGB CurveTableHelp DEFINE_TABLE Title *DEFINE_CURVE_T Define a curve for trimming. RIM_3D Trimming is processed based on the element normal rather than the vector. TCTYPE, TFLG, TDIR, TCTOL, TOLN, NSEED CurveTableHelp DEFINE_TABLE Title *DEFINE_TABLE Define a table. ArrayCount
MADYMO
Supported Card
Solver Description
Notes
FUNCTION.XY
Provides a definition of a n/a function, described as a series of X-Y pairs.
Curves can be created by different methods; refer to the online help. Curves are always exported as a
Altair Engineering

988
TABLE of XY_PAIRs. [ASSEMBLY] = reference to the parent, if not selected, will be written to the MADYMO assembly, which is the top level of the assembly hierarchy)
PAM-CRASH
Supported Card
Solver Description
Notes
FUNCT /
Definition of curves
The FUNCT toggle can switch output to a LOCUR card. The FUNCT toggle can switch output to a FUNCT card.
LOCUR /
PAM-CRASH 2G
Supported Card
Solver Description
Notes
FUNCT / Note: PERMAS
Definition of curves
Curve definition can be modified using the card previewer.
The following cards are supported in the PERMAS interface: Supported Card Solver Description Supported Parameters Notes
$FUNCTION
Function definition
989

Altair Engineering
See also Model Browser Entity State Browser HyperMesh Entities & Solver Interfaces Include Files Plots Model Setup XY Plotting
Altair Engineering

990
Contact Surfaces
Contact surface entities are used to define and store contact definitions typically used in contact analysis. Contact surfaces are defined using elements (1D/2D/3D) and their respective facecodes. A contact surface is displayed as an arrow on the selected element faces. The direction of the arrow is along the element normal that defines the contact surface. Contact surfaces are shown under the ContactSurface folder within the Model Browser. Contact surfaces have a display state, on or off, which controls the display of a contact surface in the graphics area. The display state of a contact surface can be controlled using the icon next to the contract surface entity in the Model Browser. Contact surfaces also have an active and export state. The active state of a contact surface controls the display state of the contact surface and the listing of the contact surface in the Model Browser and any of its views. If a contact surface entity is active, then its display state is available to be turned on or off and it is listed in the Model Browser and any of its views. If a contact surface entity is inactive, then its display state is turned off permanently and it is not listed in the Model Browser or any of its views. If a find operation "finds" an inactive contact surface entity, that contact surface entity will automatically be set to active. The export state of a contact surface entity controls whether or not that contact surface is exported when the custom export option is utilized. The all export option is not affected by the export state of a contact surface. The active and export states of contact surface entities can be controlled using the Entity State Browser.
991

Altair Engineering
The following panels can be used to create and edit contact surfaces: Contactsurfs
Solver Card Support for Contact Surfaces

Supported Card
Solver Description
Notes
/LEVSET /LINE/SEG/
Definition of the levelset. Definition of the line -
Altair Engineering

992
segments /SURF/SEG/ Describes the surface definition - segments
Master Slave contact is represented using contact surfaces. Supported Card Solver Description Supported Parameters Notes
SURF
Defines a surface used in a contact definition.
Defined using the Contact Surfs panel
Actran
The following Actran specific surfaces are supported : Supported Card Solver Description Supported Parameters Notes
BC_MESH INCIDENT_SURFAC ES INFINITE_ELEMEN TS INTERFACE MODAL_BASIS RADIATING_SURF ACES RAYLEIGH_SURFA CES Ls-Dyna
993

Altair Engineering
Supported Card
Solver Description
Notes
*SET_SEGMENT
Definition segements on element faces.
PERMAS
Supported Card
Solver Description
Supported Parameters ELEMENTS, SURFID, SYSTEM, MAXSMOOTH
Notes
$SURFACE
Surface definition
Samcef
Supported Card
Solver Description
Supported Parameters GROUP, NOM, MAILLE, FACE
Notes
.SEL FACE
Defines a set of faces of 3D elements
See also Browsers HyperMesh Entities & Solver Interfaces Include Files Model Setup
Altair Engineering

994
Control Volumes
Control volume entities are used to define and store control volumes typically used in safety analysis. Control volumes are shown under the ControlVolume folder within the Model Browser. Control volumes do not have a display state. Control volumes have an active and export state. The active state of a control volume controls the listing of the control volume in the Model Browser and any of its views. If a control volume entity is active, then it is listed in the Model Browser and any of its views. If a control volume entity is inactive, then it is not listed in the Model Browser or any of its views. The export state of a control volume entity controls whether or not that control volume is exported when the custom export option is utilized. The all export option is not affected by the export state of a control volume. The active and export states of control volume entities can be controlled using the Entity State Browser. The data names associated with control volumes can be found in the data names section of the HyperMesh Reference Guide.
995

Altair Engineering
The following panels can be used to create and edit control volumes: Control Vol
Solver Card Support for Control Volumes

Supported Card
Solver Description
Notes
/MONVOL
Describes the monitored volume types Describes the airbag monitored volume type. Defines the airbag using standard gas Describes the monitored volume type AREA. SelectsurfBox
/MONVOL/AIRBAG
/MONVOL/ AIRBAG1 /MONVOL/AREA
SelectsurfBox
/MONVOL/COMMU Describes the airbag with communications monitored volume type. /MONOVOL/ FVMBAG /MONVOL/GAS Describes the airbag with FVMBAG type. Describes the perfect gas monitored volume type. Describes the pressure load curve monitored volume type. Describes the reference state (stress free state) of elements
SelectsurfBox
SelectsurfBox
SelectsurfBox
/MONVOL/PRES
SelectsurfBox
REFSTA
You need to create a new include file, set the include file type as REFSTA and create this card in the include file.
LS-DYNA
Altair Engineering

996
Entities can be created using the Solver Browser. All the supported LS-DYNA keywords appear in the tree view in the Solver Browser, sorted by type of input data. To display the Solver Browser, select Solver Browser from the View menu. The complete list of LS-DYNA keywords that are supported are listed below. An alternate way to identify a supported card is to invoke the "create new keyword" tool. This convenient selection tool can be invoked using the context-sensitive menu in the Solver Browser, using the Create New option in the Tools pull-down menu. Once you select a card of interest, the right panel is opened with the necessary options set. The Control Volume panel allows you to control volume objects within a model. The *AIRBAG_OPTION card is output from this panel. The POP option is supported for WANG_NEFSKE options. The following keywords are supported: Supported Card Solver Description Supported Parameters Title SIDTYP, RBID, VSCA, PSCA, VINI, MWD, SPSF, PSF, LCID, GAMMA, P0, PE, RO ControlVolHelp *AIRBAG_ADVANC *DEFINE_ALEBAG_BAG, ED_ *DEFINE_ALEBAG_HOLE, ALE and *DEFINE_ALEBAG_INFLATO R to define ALE type AIRBAG in modular way BAGID1 - BAGID8 HOLEID1 - HOLEID8 INFLID1 - INFLID8 NX, NY, NZ, ARSNID, IDCENT, EXSID, LX, LY, LZ, ITRANS, UIDAIR, ATMOST, ATMOSP, GC, CC, MWD, SPSF, SWTIME, HG, NAIR ALE MESH OPTION (GENERATE MESH, SELECT MESH) *AIRBAG_ALE Provides a simplified approach to defining the deployment of the airbag using the ALE capabilities with an option to switch from the initial ALE Title, SIDTYP, MWD, SPSF, ATMOST, ATMOSP, GC, CC, TNKVOL, Notes
*AIRBAG_ADIABAT Define an airbag or control IC_GAS volume _MODEL_ID
997

Altair Engineering
method to control volume method at a chosen time.
TNKFINP, NQUAD, CTYPE, PFAC, FRIC, FRCMIN, NORMTYP, ILEAK, PLEAK, IV_PSETID, IBLOCK, VNTCOF, NX, NY, NZ, MOVERN, ZOOM, SWTIME, HG, NAIR, NGAS, NORIF, LCVEL, LCT, MWAIR, INITM1, AIRA, AIRB, AIRC PFAC_Option IVTYPE (PartSetID, PartID, Segment Set) NX_NY_Option
*AIRBAG_HYBRID_ Define an airbag or control CHEMKIN_ID volume
Title, SIDTYP, RBID, VSCA, PSCA, VINI, MWD, SPSF, LCIDM, LCIDT, NGAS, DATA, ATMT, ATMP, RG, HCONV, C23, A23 LCIDM_Cubic_Interp LCIDT_Cubic_Interp
*AIRBAG_HYBRID_ Define an airbag or control ID volume
Title, SIDTYP, RBID, VSCA, PSCA, VINI, MWD, SPSF, ATMOST, ATMOSP, ATMOSD, GC, CC, C23, LCC23, A23, LCA23, CP23, LCCP23, AP23, LCAP23, OPT, PVENT, NGAS LCC23_Relative_Pre ssure A23_Option Jetting Reference Geometry
Altair Engineering

998
*AIRBAG_HYBRID_ JETTING_ID
Title, SIDTYP, RBID, VSCA, PSCA, VINI, MWD, SPSF, ATMOST, ATMOSP, ATMOSD, GC, CC, C23, LCC23, A23, LCA23, CP23, LCCP23, AP23, LCAP23, OPT, PVENT, NGAS, XJFP, YJFP, ZJFP, XJVH, YJVH, ZJVH, CA, BETA, XSJFP, YSJFP, ZSJFP, PSID, NODE1, NODE2, NODE3, NREACT Control LCC23_Relative_Pre ssure A23_Option Jetting Reference Geometry
*AIRBAG_HYBRID_ JETTING_CM_ID
Title, SIDTYP, RBID, VSCA, PSCA, VINI, MWD, SPSF, ATMOST, ATMOSP, ATMOSD, GC, CC, C23, LCC23, A23, LCA23, CP23, LCCP23, AP23, LCAP23, OPT, PVENT, NGAS, XJFP, YJFP, ZJFP, XJVH, YJVH, ZJVH, CA, BETA, XSJFP, YSJFP, ZSJFP, PSID, NODE1, NODE2, NODE3, NREACT Control LCC23_Relative_Pre ssure A23_Option Jetting
999

Altair Engineering
Reference Geometry *AIRBAG_INTERAC Define two connected airbags TION_ID which vent into each other AB1, AB2, AREA, SF, PID, LCID, IFLOW LCID_orificeAreaCurv e LCID_orificeCoeffCur ve *AIRBAG_LINEAR_ FLUID_ ID Title, SIDTYP, RBID, VSCA, PSCA, VINI, MWD, SPSF, BULK, RO, LCINT, LCOUTT, LCOUTP, LCFIT, LCBULK, LCID ControlVolHelp *AIRBAG_LOAD_C URVE_ ID Title, SIDTYP, RBID, VSCA, PSCA, VINI, MWD, SPSF, STIME, LCID, RO, PE, P0, T, T0 ControlVolHelp *AIRBAG_PARTICL To define an airbag using the E particle method. STYPE1, SD1, STYPE2, SD2, BLOCK, HCONV, NP, UNIT, VISFLAG, TATM, PATM, NVENT, TEND, TSW, IAIR, NGAS, NORIF, NID1, NID2, NID3
*AIRBAG_REFERE If the reference configuration of BIRTH NCE_ the airbag is taken as the GEOMETRY_BIRTH folded configuration, the geometrical accuracy of the deployed bag will be affected by both the stretching and the compression of elements during the folding process. *AIRBAG_REFERE NCE_ BIRTH
Altair Engineering
Altair HyperMesh User's Guide 1000

GEOMETRY_BIRTH _RDT *AIRBAG_REFERE NCE_ GEOMETRY_RDT *AIRBAG_SHELL_ REFERENCE_GEO METRY *AIRBAG_SIMPLE_ AIRBAG_MODEL_I D Title SIDTYP, RBID, VSCA, PSCA, VINI, MWD, SPSF, CV, CP, T, LCID, MU, A, PE, RO, LOU, TEXT, A, B, MW, GASC ControlVolHelp Mu_Option A_Option ReferenceGeometry *AIRBAG_SIMPLE_ PRESSURE_VOLU ME_ID Title SIDTYP, RBID, VSCA, PSCA, VINI, MWD, SPSF, CN, BETA, LCID, LCIDDR ControlVolHelp CN_LCID_Option *AIRBAG_WANG_N EFSKE _ID Title SIDTYP, RBID, VSCA, PSCA, VINI, MWD, SPSF, CV, CP, T, LCT, LCMT, TVOL, LCDT, IABT, C23, LCC23, A23, LCS23, CP23, LCCP23, AP23, LCAP23, PE, RO, GC, LCEFR, POVER, PPOP, n/a
1001 Altair HyperMesh User's Guide

Altair Engineering
OPT, KNKDN, TEXT, A, B, MW, GASC Pop, Jetting, ReferenceGeometry *AIRBAG_WANG_N EFSKE _JETTING_ID Title SIDTYP, RBID, VSCA, PSCA, VINI, MWD, SPSF, CV, CP, T, LCT, LCMT, TVOL, LCDT, IABT, C23, LCC23, A23, LCA23, CP23, LCCP23, AP23, LCAP23, PE, RO, GC, LCEFR, POVER, PPOP, OPT, KNKDN, TEXT, A, B, MW, GASC, XJFP, YJFP, ZJFP, XJVH, YJVH, ZJVH, CA, BETA, XSJFP, YSJFP, ZSJFP, PSID, ANGLE, NODE1, NODE2, NODE3 MultipleJetting, CA_Option *AIRBAG_WANG_N EFSKE _JETTING_CM Title SIDTYP, RBID, VSCA, PSCA, VINI, MWD, SPSF, CV, CP, T, LCT, LCMT, TVOL, LCDT, IABT, C23, LCC23, A23, LCA23, CP23, LCCP23, AP23, LCAP23, PE, RO, GC, LCEFR, POVER, PPOP, OPT, KNKDN, TEXT, A, B, MW, GASC, XJFP, YJFP, ZJFP, XJVH, JSVH, ZJVH, CA, BETA, XSJFP, YSJFP, ZSJFP, ANGLE, NODE,
Altair Engineering

NREACT *AIRBAG_WANG_N EFSKE _JETTING_POP_ID Title SIDTYP, RBID, VSCA, PSCA, VINI, MWD, SPSF, CV, CP, T, LCT, LCMT, TVOL, LCDT, IABT, C23, LCC23, A23, LCA23,CP23, LCCP23, AP23, LCAP23, PE, RO, GC, LCEFR, POVER, PPOP, OPT, KNKDN, TEXT, A, B, MW, GASC MultipleJetting; CA_Option BETA Option CM Reference Geometry *AIRBAG_WANG_N EFSKE _JETTING_POP_C M Title SIDTYP, RBID, VSCA, PSCA, VINI, MWD, SPSF, CV, CP, T, LCT, LCMT, TVOL, LCDT, IABT, C23, LCC23, A23, LCA23, CP23, LCCP23, AP23, LCAP23, PE, RO, GC, LCEFR, POVER, PPOP, OPT, KNKDN, TEXT, A, B, MW, GASC, TDP, AXP, AYP, AZP, AMAGP, TDURP, TDA, RBIDP, XJFP, YJFP, ZJFP, XJVH, YJVH, ZJVH, CA, BETA, XSJFP, YSJFP, ZSJFP, PSID, ANGLE, NODE, NREACT

Altair Engineering
*AIRBAG_WANG_N EFSKE _MULTIPLE_JETTIN G_CM_ ID
Title, SIDTYP, RBID, VSCA, PSCA, VINI, MWD, SPSF, CV, CP, T, LCT, LCMT, TVOL, LCDT, IABT, C23, LCC23, A23, LCA23,CP23, LCCP23, AP23, LCAP23, PE, RO, GC, LCEFR, POVER, PPOP, OPT, KNKDN, IOC, IOA, IVOL, IRO, IT, LCBF,TEXT, A, B, MW, GASC, XJFP, YJFP, ZJFP, XJVH, YJVH, ZJVH, LCJRV, BETA, XSJFP, YSJFP, ZSJFP, PSID, ANGLE, NODE1, NODE2, NODE3, NREACT Title, SIDTYP, RBID, VSCA, PSCA, VINI, MWD, SPSF, CV, CP, T, LCT, LCMT, TVOL, LCDT, IABT, C23, LCC23, A23, LCA23,CP23, LCCP23, AP23, LCAP23, PE, RO, GC, LCEFR, POVER, PPOP, OPT, KNKDN, TEXT, A, B, MW, GASC, XJFP, YJFP, ZJFP, XJVH, YJVH, ZJVH, LCJRV, BETA, XSJFP, YSJFP, ZSJFP, PSID, ANGLE, NODE1, NODE2, NODE3 BETA_Option CM ReferenceGeometry
*AIRBAG_WANG_N EFSKE _MULTIPLE_JETTIN G_ID
Altair Engineering

*AIRBAG_WANG_N EFSKE _MULTIPLE_JETTIN G_POP _CM_ID
Title SIDTYP, RBID, VSCA, PSCA, VINI, MWD, SPSF, CV, CP, T, LCT, LCMT, TVOL, LCDT, IABT, C23, LCC23, A23, LCA23, CP23, LCCP23, AP23, LCAP23, PE, RO, GC, LCEFR, POVER, PPOP, OPT, KNKDN, TEXT, A, B, MW, GASC, TDP, AXP, AYP, AZP, AMAGP, TDURP, TDA, RBIDP, XJFP, YJFP, ZJFP, XJVH, YJVH, ZJVH, LCJRV, BETA, XSJFP, YSJFP, ZSJFP, PSDI, ANGLE, NODE, NREACT Title SIDTYP, RBID, VSCA, PSCA, VINI, MWD, SPSF, CV, CP, T, LCT, LCMT, TVOL, LCDT, IABT, C23, LCC23, A23, LCA23,CP23, LCCP23, AP23, LCAP23, PE, RO, GC, LCEFR, POVER, PPOP, OPT, KNKDN, TEXT, A, B, MW, GASC, XJFP, YJFP, ZJFP, XJVH, YJVH, ZJVH, LCJRV, BETA, XSJFP, YSJFP, ZSJFP, PSID, NODE1, NODE2, NODE3 BETA Option CM
*AIRBAG_WANG_N EFSKE _MULTIPLE_JETTIN G_POP _ID

Altair Engineering
Reference Geometry *AIRBAG_WANG_N EFSKE _POP_ID Title SIDTYP, RBID, VSCA, PSCA, VINI, MWD, SPSF, CV, CP, T, LCT, LCMT, TVOL, LCDT, IABT, C23, LCC23, A23, LCA23,CP23, LCCP23, AP23, LCAP23, PE, RO, GC, LCEFR, POVER, PPOP, OPT, KNKDN, TEXT, A, B, MW, GASC, TDP, AXP, AYP, AZP, AMAGP, TDURP, TDA, RBIDP Reference Geometry *DEFINE_ALEBAG _BAG Defines the surface that constitutes the airbag's outer surface for ALE airbag CVBAG, IBLOCK, VTCOEF, VENTSID, NQUAD, CTYPE, PFAC, FRIC, FRCMIN, NORMTYP, ILEAK, PLEAK, NORM, START, END SID TYPE (Part Set ID, Part ID) VENTYP (Part Set ID, Part ID, Set Segment) PFAC_Option *DEFINE_ALEBAG _HOLE Defines the surface that constitutes the vents for ALE airbag SID_SET, NQUAD, XOFF, NFOLD, XCLEN SID TYPE (Part Set ID, Part ID) *DEFINE_ALEBAG _ INFLATOR Defines the inflator for ALE airbag NGAS, NORIF, LCIDVEL, LCIDT
Altair Engineering

*INITIAL_FOAM_ The reference configuration REFERENCE_GEO allows stresses to be METRY initialized in the following hyperelastic material models: 2, 7, 21, 23, 27, 31, 38, 57, 73, 83, 132 and 181.
n/a
MADYMO
Supported Card
Solver Description
Notes
AIRBAG_CHAMBE R
Defines special characteristics CHAMBER_V0 of a finite-element structure AUTO_VOLUME which models an airbag. (ON/OFF) HOLE GAS_FLOW_GRID COMMENT output REFERENCE_COO RDINATEs
Choose elems and select all elements forming the AIRBAG_CHAMBER, i.e. all elements contained in all LISTs (ELEMENT_LIST, GROUP_LIST, INV_ELEMENT_LIST and INV_GROUP_LIST). [INV_ELEMENT_LIST] = reference to a set of elements, containing all elements in both INV_ELEMENT_LIST and INV_GROUP_LIST. Select the HOLE check box to add a related HOLE element.
COORDINATE_REF Nodal reference definition in a . Cartesian coordinate system. CARTESIAN
n/a
nodes = collection of all nodes representing a COORDINATE_REF in the present AIRBAG_CHAMBER Select the output REFERENCE_COORDINA TEs check box to export the selected nodes in the present AIRBAG_CHAMBER as COORDINATE_REF. CARTESIANs.

Altair Engineering
GAS_FLOW_GRID
GasFlow grid definition.
BODY
Defined on the card of the GRID_I_DIR (X, Y, Z) parent AIRBAG_CHAMBER. GRID (I, J, K) MIN_SIZE GRID_J_DIR (X, Y, Z) OFFSET (I, J, K) ANTI_THROUGH_FL OW (OFF/ON) INFLATOR_MTH (MOMENTUM, SONIC CELL)
GAS_FRACTION
Molar fraction of the specified GAS in the mixture.
Defined on the same card as its parent GAS_MIXTURE (_VARIABLE). N2, MOL_FRACTION TIME, N2, Defined on the card of the parent. Defined on the card of the parent.
GAS_MIXTURE
Gas mixture with a fixed composition.
GAS_MIXTURE_VA Gas mixture at a fixed time RIABLE after inflator triggering. HOLE
HOLE.MODEL, BLOCK_FLOW, CDEX, DPEX, DTEX, DELTEX, SWITCH, SWITCH_SCALE, CDP_FUNC, CDT_FUNC, SCALE_FUNC HOLE_AREA HOLE_SUBSEGME NT
HOLE_AREA
HOLE_AREA (ACTUAL, REFERENCE, SCALE_ACTUAL, SCALE_REFERENC E) HOLE_SUBSEGME NT (AUTO, USER)
HOLE_SUBSEGME NT
Altair Engineering

PAM-CRASH 2G
Supported Card
Solver Description
Supported Parameters Pa; Ta; Ru; INACT: YPV; RHOPV; TIPV; AHEAT; LCTRAN; NCYFR; AHEAT, LCTRAN, TITLE DISP_EXT_SKIN_CA RDS WALL_OPENING WALL_FABRIC INI_COND LEAKAGE INFLATOR
Notes
BAGIN
Airbag definition
CHAMBER
Multiple chamber definitions
END_BAGIN
Terminates the whole general airbag definition Ends each chamber description Chamber outer skin elements Sub-keyword of CHAMBER Sub-keyword of BAGIN Sub-keyword of CHAMBER Sub-keyword of BAGIN Sub-keyword of CHAMBER
END_CHAMBER
EXT_SKIN
FPM FPM_HOLE
FPM definition card Hole for SPHCEL
GAS
Chamber GAS definition
GEN_INI_COND INFLATOR
Chamber gas initial condition Airbag inflator definition
Sub-keyword of BAGIN Sub-keyword of CHAMBER Sub-keyword of
INI_COND
Initial condition of gas

Altair Engineering
CHAMBER JET Jet definition Sub-keyword of CHAMBER Sub-keyword of CHAMBER Sub-keyword of BAGIN
LEAKAGE
Vents and holes definition in airbag FPM - Local smoothing length card Define chamber wall fabric S, MATFAB, NLD
LOCAL_H
WALL_FABRIC
Sub-keyword of CHAMBER
WALL_OPENING
Chamber wall opening
NUL_SHELL, S, Sub-keyword of MATOP, COP, CHAMBER NLDCOT, NLDCOP, IFLOPT, VEN_AREA, IOPEN, OPIN, OPOUT NUMNULSHELL NUM_VENAREA
Altair Engineering

Groups
Group entities are used to define and store interfaces and rigid walls typically used in contact analysis. Groups are shown under the Group folder within the Model Browser. Groups have a display state, on or off, which controls the display of a group in the graphics area. The display state of a group can be controlled using the icon next to the group entity in the Model Browser. Groups also have an active and export state. The active state of a group controls the display state of the group and the listing of the group in the Model Browser and any of its views. If a group entity is active, then its display state is available to be turned on or off and it is listed in the Model Browser and any of its views. If a group entity is inactive, then its display state is turned off permanently and it is not listed in the Model Browser or any of its views. If a find operation "finds" an inactive group entity, that group entity will automatically be set to active. The export state of a group entity controls whether or not that group is exported when the custom export option is utilized. The all export option is not affected by the export state of a group. The active and export states of group entities can be controlled using the Entity State Browser. The data names associated with groups can be found in the data names section of the HyperMesh Reference Guide.

Altair Engineering
The following panels can be used to create and edit groups: Interfaces (configurations 1-4) Rigid Walls (configuration 5)
Solver Card Support for Groups

Supported Card
Solver Description
Notes
/INTER /INTER/LAGMUL/ TYPE7 /INTER/TYPE1 /INTER/TYPE2 /INTER/TYPE3 /INTER/TYPE5 /INTER/TYPE6 /INTER/TYPE7 /INTER/TYPE8 /INTER/TYPE9
Describes the interfaces. Describes the Lagrange multiplier interface type 7. Describes the interface type 1 Describes the interface type 2 Describes the interface type 3 Describes the interface type 5 Describes the interface type 6 Describes the interface type 7 Describes the interface type 8 Describes the ALE Lagrange with void opening and free space. Describes the tied contact with void. Describes the edge to edge or line to line interface. Describes the interface type 12 - fluid/fluid.
/INTER/TYPE10
/INTER/TYPE11
/INTER/TYPE12
Altair Engineering

/INTER/TYPE14
This interface simulates impacts between an hyperellipsoidal rigid master surface and a list of slave nodes. This interface is a penalty contact interface without damping. Describes the Euler/Lagrange or ALE/Lagrange. This is a combination of interface Type 7 and Type 11, with common input based on the same slave / master surfaces. This is a general single surface or surface to surface contact interface. Edge to edge contact is also possible. Also allows zero gap between the contacts. Specific interface between a non-deformable master surface and a slave surface designed for stamping. Describes the rigid walls. Describes the rigid walls cylinder of diameter Describes the rigid walls parallelogram Describes the rigid walls plane Describes the rigid walls sphere of diameter Describes the ALE rigid wall. Definition of sections for time
/INTER/TYPE15
/INTER/TYPE18
/INTER/TYPE19
/INTER/TYPE20
INTER/TYPE21
/RWALL /RWALL/CYL
/RWALL/PARAL
/RWALL/PLANE
/RWALL/SPHER
/RWALL/THERM /SECT

Altair Engineering
history plots.
Contact, thermal analysis definitions, multi-body dynamics bodies, non-structural mass, rigid walls and section outputs are represented using group entities Supported Card Solver Description Supported Parameters Notes
CONTACT
Defines master-slave contact between two entities. Defines CHBDYE slave elements used for thermal conduction analysis Defines CHBDYE slave elements used for thermal conduction analysis, and also allows for CONV continuation cards to be defined. Defines the ground body for multi-body dynamics simulation. Defines a multi-body contact between a node and a deformable surface. Defines a multi-body contact between rigid bodies.
Defined using the Interfaces panel Defined using the interfaces panel.
CONDUCTION
CONVECTION
Defined using the interfaces panel.
GROUND
Defined using the bodies panel
MBCNTDS
Defined using the interfaces panel
MBCNTR
NODESET NSM1 Defines non-structural mass per unit length/area on properties or elements. Defines lumped non-structural mass on properties or elements. Specifies the free convection Defined using the nsm panel.
NSML1
Defined using the nsm panel.
PCONV
Defined using the
Altair Engineering

boundary condition properties for heat transfer analysis. PFBODY Defines a flexible body for multi-body dynamics simulation. Defines a rigid body for multibody dynamics simulation. Defines a rigid wall of the following types: Infinite Plane, Infinite Cylinder, Sphere and Parallelogram. Defines a section for force output in geometric nonlinear analysis. Defines a kinematic tied contact used in geometric non-linear analysis. Defines damping used in geometric non-linear analysis.
interfaces panel
Defined using the bodies panel
PRBODY
Defined using the bodies panel Defined using the rigid walls panel.
RWALL
SECT
TIE
XDAMP
Abaqus
Groups are entities for various types of interfaces. It is recommended that all contact interfaces, such as *CONTACT PAIR, *TIE, *PRE-TENSION SECTION, *SURFACE, *SURFACE INTERACTION, as *CONTACT, be defined from the Contact Manager in the Abaqus user profile. All history type interface controls, such as Contact Interference, Model Change, Change Friction, Contact Controls, Controls, and Clearance, be defined from the Step Manager in the Abaqus user profile. The following Abaqus keywords are supported as groups in the Interface panel: Supported Card Solver Description Supported Parameters Notes
*BLOCKAGE
Control contacting surfaces for n/a blockage
Must be used in conjunction with the *SURFACE INTERACTION card. The Standard template
*CHANGE
Change friction properties
AMPLITUDE

Altair Engineering
FRICTION
ELSET INTERACTION RESET
only. It must be added to a load step (*STEP). Must be added to a load step (*STEP) in explicit template.
*CLEARANCE
CPSET Specify a particular initial clearance value and a contact INPUT direction for the slave nodes on MASTER a surface SLAVE TABULAR VALUE
*CONTACT (General Contact) *CONTACT CLEARANCE
Begin the definition of general contact
OP
Define contact clearance properties
ADJUST CLEARANCE NAME SEARCH ABOVE SEARCH BELOW SEARCH NSET
*CONTACT CLEARANCE ASSIGNMENT *CONTACT CONTROLS
Assign contact clearances between surfaces in the general contact domain Specify additional controls for contact
N/A
APPROACH AUTOMATIC TOLERANCES FRICTION ONSET LAGRANGE MULTIPLIER MASTER MAXCHP PERRMX RESET SLAVE SLIDE DISTANCE STABILIZE TANGENT FRACTION
Must be added to a load step (*STEP).
Altair Engineering

UERRMX *CONTACT CONTROLS ASSIGNMENT *CONTACT DAMPING Assign contact controls for the TYPE = SCALE general contact algorithm PENALTY, NODAL EROSION Define viscous damping between contacting surfaces This card is a sub-option in the *CONTACT card image.
DEFINITION=DAMPI This card is a sub-option NG COEFFICIENT in the *SURFACE INTERACTION card image. Surface1 Surface2 This card is a sub-option in the *CONTACT card image
*CONTACT EXCLUSIONS
Specify self-contact surfaces or surface pairings to exclude from the general contact domain Specify a nondefault contact formulation for the general contact algorithm Specify self-contact surfaces or surface pairings to include in the general contact domain Prescribe time-dependent allowable interferences of contact pairs and contact elements
*CONTACT FORMULATION
TYPE = PURE MASTER-SLAVE
This card is a sub-option in the * CONTACT card image. This card is a sub-option in the *CONTACT card image. The Standard template only. Must be added to a load step (*STEP).
*CONTACT INCLUSIONS
ALL ELEMENT BASED ALL EXTERIOR AMPLITUDE OP SHRINK TYPE= {CONTACT PAIR, ELEMENT}
*CONTACT INTERFERENCE
*CONTACT PAIR
Define surfaces that contact each other
ADJUST CPSET EXTENSION ZONE GEOMETRIC CORRECTION HCRIT INTERACTION MECHANICAL CONSTRAINT NO THICKNESS OP SMALL SLIDING SMOOTH SUPPLEMENTARY

Altair Engineering
CONSTRAINTS TIED TRACKING TYPE WEIGHT *CONTACT PROPERTY ASSIGNMENT *CONTROLS Assign contact properties for the general contact algorithm SURFACE1 SURFACE2 This card is a sub-option in the *CONTACT card image.
Reset solution controls
OPTIONS (Analysis, Parameters, Reset, Type) CONSTRAINT NAME INFLUENCE RADIUS ORIENTATION REF NODE SURFACE The *COUPLING is also supported as rigid elements (COUP_KIN) and RBE3 (COUP_DIS) when *SURFACE points to nodes.
*COUPLING
Define a surface-based coupling constraint where the *SURFACE card points to elements
*DIAGNOSTICS
Control diagnostic messages
ADAPTIVE MESH = {STEP SUMMARY / SUMMARY / DETAIL / OFF} CONTACT INITIAL OVERCLOSURE = {DETAIL / SUMMARY} CUTOFF RATIO DEFORMATION SPEED CHECK = {SUMMARY / DETAIL / OFF} DETECT CROSSED SURFACES = {ON / OFF} PLASTICITY = {SUMMARY / DETAIL / OFF} WARNING RATIO WARPED SURFACE =
Explicit template only. Must be added to a load step (*STEP).
Altair Engineering

{SUMMARY / DETAIL / OFF} *DISTRIBUTING Define a distributing coupling constraint WEIGHTING METHOD = {UNIFORM, LINEAR, QUADRATIC, CUBIC} This card is a sub-option in the *COUPLING card image. It is also supported as COUP_DIS type rbe3 elements. The *FASTENER PROPERTY card is defined from the Property panel.
*FASTENER (SPOT Define mesh-independent WELD) fasteners
ADJUST ORIENTATION ATTACHMENT METHOD COUPLING ELSET INTERACTION NAME NUMBER OF LAYERS ORIENTATION PROPERTY RADIUS OF INFLUENCE REFERENCE NODE SET SEARCH RADIUS WEIGHTING METHOD UNSORTED
*FILTER
Define a filter for output filtering NAME TYPE= {BUTTERWORTH, CHEBYS1, CHEBYS2} Specify mass scaling at the beginning of the step DT ELSET TYPE= {BELOW MIN, UNIFORM, SET EQUAL DT} FACTOR
Explicit template only
*FIXED MASS SCALING

Altair Engineering
*FRICTION
Specify a friction model
ANISOTROPIC EXPONENTIAL DECAY TAUMAX DEPENDENCIES ROUGH USER ELASTIC SLIP LAGRANGE SLIP TOLERANCE DEPVAR PROPERTIES
This card is a sub-option in the *SURFACE INTERACTION card image.
*FRICTION
Specify a friction model
ANISOTROPIC EXPONENTIAL DECAY TAUMAX DEPENDENCIES ROUGH USER ELASTIC SLIP LAGRANGE SLIP TOLERANCE DEPVAR PROPERTIES
This card is a sub-option in the *CHANGE FRICTION card image.
*INTEGRATED OUTPUT SECTION
Define an integrated output section over a surface with a local coordinate system and a reference point
NAME SURFACE REF NODE ORIENTATION PROJECT ORIENTATION POSITION = { INPUT, CENTER} REF NODE MOTION = {INDEPENDENT, AVERAGE TRANSLATION, AVERAGE}
Altair Engineering

*KINEMATIC
Define a kinematic coupling constraint
dof1, dof2
This card is a sub-option in the *COUPLING card image. It is also supported as COUP_KIN type rigid elements.
*MODEL CHANGE
Remove or reactivate elements ACTIVATE and contact pairs ADD = {STRAIN FREE, WITH STRAIN} REMOVE
The Standard template only. Must be added to a load step (*STEP).
*PRE-TENSION SECTION
Associate a pre-tension node with a pre-tension section
NODE NSET ELEMENT SURFACE
*SHELL TO SOLID COUPLING
Define a surface-based coupling between a shell edge and a solid face
CONSTRAINT NAME INFLUENCE DISTANCE POSITION TOLERANCE
The EDGE BASED surfaces can be created from the Contact Manager.
*SURFACE
Define a surface or region in a model
NAME TRIM
For analytical rigid surfaces (TYPE= SEGMENTS, CYLINDER, TYPE= {ELEMENT, REVOLUTION), NODE, SEGMENTS, corresponding *RIGID CYLINDER, BODY card should also be REVOLUTION, created from the collector CUTTING panel. SURFACE} CROP COMBINE = {UNION, INTERSECTION, DIFFERENCE} Type Material
*SURFACE BEHAVIOR
Define alternative pressureoverclosure relationships for contact
NO SEPARATION PRESSUREOVERCLOSURE= {HARD,
This card is a sub-option in the *SURFACE INTERACTION card image.

Altair Engineering
EXPONENTIAL, LINEAR, TABULAR} AUGMENTED LAGRANGE PENALTY *SURFACE INTERACTION Define surface interaction properties PAD THICKNESS USER Explicit template only. This card is defined from the Property panel in case of Standard 3D and Standard 2D templates. This card is a sub-option in the *CONTACT card image.
*SURFACE PROPERTY ASSIGNMENT
Assign surface properties to a surface for the general contact algorithm
PROPERTY = (FEATURE EDGE CRITERIA, THICKNESS OF FSET FRACTION)
*TIE
POSITION Define surface-based tie and cyclic symmetry constraints or TOLERANCE coupled acoustic-structural TIED NSET interactions ADJUST CYCLIC SYMMETRY NO ROTATION TYPE NO THICKNESS CYCLIC SYMMETRY CONSTRAIN RATIO
*VARIABLE MASS SCALING
Specify mass scaling during the step
DT ELSET TYPE= {BELOW MIN, UNIFORM, SET EQUAL DT, ROLLING} FREQUENCY NUMBER INTERVAL CROSS SECTION NODES EXTRUDED LENGTH
Altair Engineering

FEED RATE . LS-DYNA
Groups can be created and edited from the Interface panel (Configurations 1-4), Rigid Wall panel (Configuration 5), and Ale Setup panel (Configuration 6). An LS-DYNA entity that utilizes a *SET_ [NODE, SHELL, PART, etc.] keyword card belongs to a group, with the exception of Rigid Bodies/ RBE2s. REVIEW allows you to efficiently visualize the entities defining master and slave. A transparency mode as well as the ability to turn on/off master and slave entities is also available. In review mode, review opts allows you to customize the graphical review of the interfaces. The Interface panel allows you to define groups with HyperMesh configurations of 1, 2, 3, and 4. The difference among these configurations is the type of entities contained within the group. Config 1 Config 2 Config 3 Config 4 Holds master and slave elements. Holds master elements and slave nodes. Holds slave elements. Holds slave nodes.
The Rigid Wall panel allows you to define a group with the HyperMesh configuration 5. This group configuration holds the additional geometric data for LS-DYNA rigid wall definitions. Sliding Interfaces Accessed via the Rigid Wall panel. The Keyword _TITLE option is supported. The _THERMAL(IREAD==3) option is not supported. Use the additional cards option in Keyword decks to select number of lines of data. If this is on, two additional cards are available. In Structured, additional cards are controlled by using the IREAD variable. Valid values are 0, 1, and 2. Boxes, part sets, and sets are supported. The $HMNAME fields are used for names. When using the _TITLE option, the 70-character field is considered a comment. If the line following the keyword (No TITLE option), or the first line of the Structured card contains $HM_NAME, the name supplied is read and used as the group's name. If the string $HM_ID also exists, this is used as the groups ID. NAME is 16 characters, starting in Column 9. ID field is 8 characters, starting in Column 35.

Altair Engineering
The HyperMesh interface type defines the general type of the LS-DYNA Sliding Interface. Use the card previewer to make changes to the LS-DYNA type. HyperMesh SlidingOnly Option Keyword *CONTACT_ Structured
Defines a *CONTACT_SLIDING_ONLY_option card. Off On <nothing> PENALTY Type 1 Type p1
SurfaceToSurfa Defines a *CONTACT_option_SURFACE_TO_SURFACE card. ce None Automatic <nothing> AUTOMATIC_ Type 3 Type a3
The None and Automatic options have an additional option to define a OneWayInterface. If this option is on, the following cards are created. None and OneWay Automatic and OneWay ONE_WAY_ AUTOMATIC_ONE_W AY_ CONSTRAINT_ ERODING_ TIEBREAK_ Type 10 Type a10
Constraint Eroding TieBreak The Tied option has an additional option to define OFFSET. Tied Tied and offset Tiedshell Tiedshell and offset
Type 17 Type 14 Type 9
TIED TIED_OFFSET TIED_SHELL_EDGE TIED_SHELL_EDGE_ OFFSET
Type 2
NodesToSurfac Defines a *CONTACT_option_NODES_TO_SURFACE card. e
Altair Engineering

None Automatic Constraint Eroding TieBreak
<nothing> AUTOMATIC CONSTRAINT_ ERODING_ TIEBREAK_
Type 5 Type a5 Type 18 Type 16 Type 8
The Tied option has an additional option to define OFFSET. Tied Tied and offset SingleSurface TIED_ TIED_OFFSET Type 6
Defines a *CONTACT_option_SINGLE_SURFACE card. none Automatic Airbag Eroding <nothing> AUTOMATIC_ AIRBAG_ ERODING_ Type 4 Type 13 Type a13 Type 15
RgdBodyToRgd Defines a *CONTACT_RIGID_BODY_option_TO RIGID_BODY card Body Off On RgdNodeToRgd N/A Body DrawBead Interior N/A Defines a *CONTACT_INTERIOR card. ONE_WAY_ TWO_WAY_ Type 21 Type 19
RIGID_NODES_TO_RI Type 20 GID BODY DRAW_BEAD Type 23
AutomaticGene Defines a *CONTACT_AUTOMATIC_GENERAL card. ral ForceTransduc er Defines a *CONTACT_FORCE_TRANSDUCER_option card

Altair Engineering
On Off
PENALTY CONSTRAINT
ContactSpotwel Defines a *CONTACT_SPOTWELD card d none Torsion WITH_TORSION
ContactSIngEd Defines a *CONTACT_SINGLE_EDGE card ge
Supported Card
Solver Description
Notes
*ALE_MULTIDefines the appropriate ALE PSID TBD MATERIAL_GROUP material groupings for interface reconstruction when many ALE Multi-Material Groups are present in a model. *ALE_REFERENCE Defines a motion and/or a _ deformation prescribed for a SYSTEM_CURVE geometric entity (where a geometric entity may be any part, part set, node set or segment set). curveCount
*ALE_REFERENCE Used to associate a geometric SID TBD, PRTYPE, _ entity to a reference system XC, YC, ZC, EXPLIM SYSTEM_GROUP type. *ALE_REFERENCE Defines a group of nodes that _ control the motion of an ALE SYSTEM_NODE mesh. *ALE_REFERENCE Allows many choices of the _ reference system types for SYSTEM_SWITCH any ALE geometric entity. *ALE_SMOOTHING Smoothing constraint that keeps a node at its initial parametric location along a line between two other nodes. NodeCount
T1 - T7 TYPE1 - TYPE8 IdCount IPRE, SNID TBD, MNID1 TBD, MNID2 TBD
Altair Engineering

*ALE_TANK_TEST
Allows for the airbag information input of the control volume approach to be used as input for the ALE/Eulerian fluid-structure interaction model of the airbag.
MDOTLC, TANKVOL, PAMB, PFINAL, MACHLIM, VELMAX, AORIF, AMMGIDG, AMMGIDA, NUMPNT PID, LCID
*BOUNDARY_AMBI Defines the IDs of 2 load ENT_ curves: 1) internal energy per EOS unit reference specific volume and 2) relative volume. *BOUNDARY_FLUX Define flux boundary _SET conditions for a thermal or coupled thermal/structural analysis.
LCID, MLC1-4, LOC Heat Flux Options (None, Function vs. Time, Function vs. Temperature) STYP, DOF, VAD, LCID, SF, DEATH, BIRTH, VID XtraNodeSetHelp
*BOUNDARY_SPH _FLOW
Define a flow of particle
*CONSTRAINED_E XTRA_ NODES_NODE *CONSTRAINED_E XTRA_ NODES_SET
Define extra nodes for rigid body.
Define extra nodes for rigid body.
XtraNodeSetHelp
TITLE, NQUAD, *CONSTRAINED_ Provides the coupling LAGRANGE_IN_SO mechanism for modeling Fluid- CTYPE, DIREC, MCOUP, PSID TBD LID Structure Interaction. (START/END), PFAC, FRIC, FRCMIN, NORM, NORMTYP, DAMP, CQ, HMIN, HMAX, ILEAK, LCIDPOR, NVENT, IBLOCk MCOUP_SetMultiMa tGrp PFAC_curve OptionalCard *CONSTRAINED_RI Merge two rigid bodies. n/a

Altair Engineering
GID_ BODIES SNSID TBD *CONSTRAINED_TI Define a tied shell edge to Eshell edge interface that can MNSID TBD BREAK release locally as a function of plastic strain of the shells surrounding the interface nodes. *CONSTRAINED_TI Define a tied node set with ED_ failure based on plastic strain. NODES_FAILURE EPPF, ETYPE, NSID TBD TiedNodesFailureHel p HEADING, SBOXID, MBOXID, SPR, MPR, SSID TBD, FS, FD, DC, VC, VDC, PENCHK, BT, DT, SFS, SFM, SST, MST, SFST, SFMT, FSF, VSF SlaveMasterAddHelp mppOption Additional Cards *CONTACT_AIRBA G_ SINGLE_SURFACE _MPP (ID) HEADING, TRACKPEN, BUCKET, LCBUCKET, NSEG2TRACK, INITITER, PARMAX, CPARM8, SBOXID, MBOXID, SPR, MPR, SSID TBD, FS, FD, DC, VC, VDC, PENCHK, BT, DT, SFS, SFM, SST, MST, SFST, SFMT, FSF, VSF SlaveMasterAddHelp OptionalCard AdditionalCards *CONTACT_AUTO_ Move the master surface in a MOVE contact definition to close an CID, VID, LCID, ATIME
*CONTACT_AIRBA Define a contact interface. G_ SINGLE_SURFACE (ID)
Altair Engineering

initial gap between the slave and master surfaces. *CONTACT_AUTOM Define a contact interface. ATIC_ GENERAL(ID) HEADING, SBOXID, MBOXID, SPR, MPR, SSID TBD, FS, FD, DC, VC, VDC, PENCHK, BT, DT, SFS, SFM, SST, MST, SFST, SFMT, FSF, VSF SlaveMasterAddHelp interiorOption mppOption AdditionalCards *CONTACT_AUTOM Define a contact interface. ATIC_ GENERAL_INTERI OR(ID) HEADING, SBOXID, MBOXID, SPR, MPR, SSID TBD, FS, FD, DC, VC, VDC, PENCHK, BT, DT, SFS, SFM, SST, MST, SFST, SFMT, FSF, VSF SlaveMasterAddHelp mppOption AdditionalCards *CONTACT_AUTOM ATIC_ GENERAL_INTERI OR_ MPP(ID) HEADING, TRACKPEN, BUCKET, LCBUCKET, NSEG2TRACK, INITITER, PARMAX, CPARM8, SBOXID, MBOXID, SPR, MPR, SSID TBD, FS, FD, DC, VC, VDC, PENCHK, BT, DT, SFS, SFM, SST, MST, SFST, SFMT, FSF, VSF SlaveMasterAddHelp OptionalCard AdditionalCards

Altair Engineering
*CONTACT_AUTOM ATIC_ GENERAL_MPP(ID)
HEADING, TRACKPEN, BUCKET, LCBUCKET, NSEG2TRACK, INITITER, PARMAX, CPARM8, SBOXID, MBOXID, SPR, MPR, SSID TBD, FS, FD, DC, VC, VDC, PENCHK, BT, DT, SFS, SFM, SST, MST, SFST, SFMT, FSF, VSF SlaveMasterAddHelp interiorOption OptionalCard AdditionalCards
*CONTACT_AUTOM Define a contact interface. ATIC_ NODES_TO_SURF ACE(ID)
Heading, SSID TBD, MSID TBD, SBOXID, MBOXID, SPR, MPR, FS, FD, DC, VC, VDC, PENCHK, BT, DT, SFS, SFM, SST, MST, SFST, SFMT, FSF, VSF SlaveMasterAddHelp SMOOTH mppOption AdditionalCards
*CONTACT_AUTOM ATIC_ NODES_TO_SURF ACE_ MPP(ID)
HEADING, TRACKPEN, BUCKET, LCBUCKET, NSEG2TRACK, INITITER, PARMAX, CPARM8, SBOXID, MBOXID, SPR, MPR, SSID TBD, MSID TBD,FS, FD, DC, VC, VDC, PENCHK, BT, DT, SFS, SFM, SST, MST, SFST, SFMT, FSF, VSF
Altair Engineering

SlaveMasterAddHelp OptionalCard AdditionalCards *CONTACT_AUTOM Define a contact interface. ATIC_ NODES_TO_SURF ACE_ SMOOTH(ID) Heading, SSID TBD, MSID TBD, SBOXID, MBOXID, SPR, MPR, FS, FD, DC, VC, VDC, PENCHK, BT, DT, SFS, SFM, SST, MST, SFST, SFMT, FSF, VSF SlaveMasterAddHelp mppOption AdditionalCards *CONTACT_AUTOM ATIC_ NODES_TO_SURF ACE_ SMOOTH_MPP(ID) HEADING, TRACKPEN, BUCKET, LCBUCKET, NSEG2TRACK, INITITER, PARMAX, CPARM8, SBOXID, MBOXID, SPR, MPR, SSID TBD, MSID TBD,FS, FD, DC, VC, VDC, PENCHK, BT, DT, SFS, SFM, SST, MST, SFST, SFMT, FSF, VSF SlaveMasterAddHelp OptionalCard AdditionalCards *CONTACT_AUTOM ATIC_ ONE_WAY_SURFA CE_TO _SURFACE(ID) HEADING, SBOXID, MBOXID, SPR, MPR, SSID TBD, FS, FD, DC, VC, VDC, PENCHK, BT, DT, SFS, SFM, SST, MST, SFST, SFMT, FSF, VSF mppOption AdditionalCards

Altair Engineering
*CONTACT_AUTOM ATIC_ ONE_WAY_SURFA CE_TO _SURFACE_SMOO TH(ID)
HEADING, SBOXID, MBOXID, SPR, MPR, SSID TBD, FS, FD, DC, VC, VDC, PENCHK, BT, DT, SFS, SFM, SST, MST, SFST, SFMT, FSF, VSF mppOption AdditionalCards
*CONTACT_AUTOM ATIC_ ONE_WAY_SURFA CE_TO _SURFACE_TIEBR EAK (ID)
HEADING, SSID TBD, MSID TBD, SBOXID, MBOXID, SPR, MPR, FS, FD, DC, VC, VDC, PENCHK, BT, DT, SFS, SFM, SST, MST, SFST, SFMT, FSF, VSF, SFLS, CN SlaveMasterAddHelp
*CONTACT_AUTOM ATIC_ SINGLE_SURFACE (ID)
HEADING, SSID TBD, MSID TBD, SBOXID, MBOXID, SPR, MPR, FS, FD, DC, VC, VDC, PENCHK, BT, DT, SFS, SFM, SST, MST, SFST, SFMT, FSF, VSF SlaveMasterAddHelp SMOOTH mppOption AdditionalCards
*CONTACT_AUTOM ATIC_ SINGLE_SURFACE _MPP (ID)
HEADING, TRACKPEN, BUCKET, LCBUCKET, NSEG2TRACK, INITITER, PARMAX, CPARM8, SBOXID, MBOXID, SPR, MPR, SSID TBD, MSID TBD,FS, FD,
Altair Engineering

DC, VC, VDC, PENCHK, BT, DT, SFS, SFM, SST, MST, SFST, SFMT, FSF, VSF SlaveMasterAddHelp SMOOTH OptionalCard AdditionalCards *CONTACT_AUTOM ATIC_ SINGLE_SURFACE _ SMOOTH(ID) HEADING, SSID TBD, MSID TBD, SBOXID, MBOXID, SPR, MPR, FS, FD, DC, VC, VDC, PENCHK, BT, DT, SFS, SFM, SST, MST, SFST, SFMT, FSF, VSF SlaveMasterAddHelp mppOption AdditionalCards *CONTACT_AUTOM ATIC_ SINGLE_SURFACE _ SMOOTH_MPP(ID) HEADING, TRACKPEN, BUCKET, LCBUCKET, NSEG2TRACK, INITITER, PARMAX, CPARM8, SBOXID, MBOXID, SPR, MPR, SSID TBD, MSID TBD,FS, FD, DC, VC, VDC, PENCHK, BT, DT, SFS, SFM, SST, MST, SFST, SFMT, FSF, VSF SlaveMasterAddHelp OptionalCard AdditionalCards *CONTACT_AUTOM ATIC_ SURFACE_TO_SU RFACE Heading, SSID TBD, MSID TBD, SBOXID, MBOXID, SPR, MPR, FS, FD, DC,

Altair Engineering
(ID)
VC, VDC, PENCHK, BT, DT, SFS, SFM, SST, MST, SFST, SFMT, FSF, VSF SlaveMasterAddHelp mppOption
*CONTACT_AUTOM ATIC_ SURFACE_TO_SU RFACE_ MPP(ID)
HEADING, TRACKPEN, BUCKET, LCBUCKET, NSEG2TRACK, INITITER, PARMAX, CPARM8, SBOXID, MBOXID, SPR, MPR, SSID TBD, MSID TBD,FS, FD, DC, VC, VDC, PENCHK, BT, DT, SFS, SFM, SST, MST, SFST, SFMT, FSF, VSF SlaveMasterAddHelp OptionalCard AdditionalCards
*CONTACT_AUTOM ATIC_ SURFACE_TO_SU RFACE_ SMOOTH(ID)
Heading, SSID TBD, MSID TBD, SBOXID, MBOXID, SPR, MPR, FS, FD, DC, VC, VDC, PENCHK, BT, DT, SFS, SFM, SST, MST, SFST, SFMT, FSF, VSF SlaveMasterAddHelp mppOption
*CONTACT_AUTOM ATIC_ SURFACE_TO_SU RFACE_ SMOOTH_MPP(ID)
HEADING, TRACKPEN, BUCKET, LCBUCKET, NSEG2TRACK, INITITER, PARMAX, CPARM8, SBOXID, MBOXID, SPR, MPR, SSID TBD, MSID TBD,FS, FD,
Altair Engineering

DC, VC, VDC, PENCHK, BT, DT, SFS, SFM, SST, MST, SFST, SFMT, FSF, VSF SlaveMasterAddHelp OptionalCard AdditionalCards *CONTACT_AUTOM ATIC_ SURFACE_TO_SU RFACE_ TIEBREAK(ID) Heading, SSID TBD, MSID TBD, SBOXID, MBOXID, SPR, MPR, FS, FD, DC, VC, VDC, PENCHK, BT, DT, SFS, SFM, SST, MST, SFST, SFMT, FSF, VSF, OPTION, SFLS SlaveMasterAddHelp mppOption *CONTACT_AUTOM ATIC_ SURFACE_TO_SU RFACE_ TIEBREAK_MPP (ID) HEADING, TRACKPEN, BUCKET, LCBUCKET, NSEG2TRACK, INITITER, PARMAX, CPARM8, SBOXID, MBOXID, SPR, MPR, SSID TBD, MSID TBD,FS, FD, DC, VC, VDC, PENCHK, BT, DT, SFS, SFM, SST, MST, SFST, SFMT, FSF, VSF SlaveMasterAddHelp OptionalCard AdditionalCards *CONTACT_CONST RAINT_ NODES_TO_SURF ACE(ID) Heading, SSID TBD, MSID TBD, SBOXID, MBOXID, SPR, MPR, FS, FD, DC, VC, VDC, PENCHK, BT, DT, SFS, SFM, SST, MST, SFST,

Altair Engineering
SFMT, FSF, VSF, KPF SlaveMasterAddHelp mppOption AdditionalCards *CONTACT_CONST RAINT_ NODES_TO_SURF ACE_ MPP(ID) HEADING, TRACKPEN, BUCKET, LCBUCKET, NSEG2TRACK, INITITER, PARMAX, CPARM8, SBOXID, MBOXID, SPR, MPR, SSID TBD, FS, FD, DC, VC, VDC, PENCHK, BT, DT, SFS, SFM, SST, MST, SFST, SFMT, FSF, VSF, KPF SlaveMasterAddHelp OptionalCard AdditionalCards *CONTACT_CONST RAINT_ SURFACE_TO_SU RFACE (ID) Heading, SSID TBD, MSID TBD, SBOXID, MBOXID, SPR, MPR, FS, FD, DC, VC, VDC, PENCHK, BT, DT, SFS, SFM, SST, MST, SFST, SFMT, FSF, VSF, KPF SlaveMasterAddHelp mppOption AdditionalCards *CONTACT_CONST RAINT_ SURFACE_TO_SU RFACE_ MPP(ID) HEADING, TRACKPEN, BUCKET, LCBUCKET, NSEG2TRACK, INITITER, PARMAX, CPARM8, SBOXID, MBOXID, SPR, MPR, SSID TBD, FS, FD, DC, VC,
Altair Engineering

VDC, PENCHK, BT, DT, SFS, SFM, SST, MST, SFST, SFMT, FSF, VSF, KPF SlaveMasterAddHelp OptionalCard AdditionalCards *CONTACT_DRAW BEAD (ID) HEADING, SBOXID, MBOXID, SPR, MPR, SSID, MSID, FS, FD, DC, VC, VDC, PENCHK, BT, DT, SFS, SFM, SST, MST, SFST, SFMT, FSF, VSF, LCIDRF, LCIDNF, DBDTH, DFSCL, NUMINT, DBPID, ELOFF SlaveMasterAddHelp mppOption AdditionalCards *CONTACT_DRAW BEAD_ MPP(ID) Heading, TRACKPEN, BUCKET, LCBUCKET, NSEG2TRACK, INITITER, PARMAX, CPARM8, SSID TBD, MSID TBD, SBOXID, MBOXID, SPR, MPR, FS, FD, DC, VC, VDC, PENCHK, BT, DT, SFS, SFM, SST, MST, SFST, SFMT, FSF, VSF, LCIDRF, LCIDNF, DBDTH, DFSCL, NUMINT, DBPID, ELOFF SlaveMasterAddHelp OptionalCard AdditionalCards *CONTACT_ENTITY Define a contact entity PARTID, SF, df, cf, intord, SSID, BT, DT,

Altair Engineering
(ID)
SO, GO, AX, AY, AZ, BX, BY, BZ, InOut ContEntityHelp mppOption
*CONTACT_ENTITY _MPP (ID)
TRACKPEN, BUCKET, LCBUCKET, NSEG2TRACK, INITITER, PARMAX, CPARM8, PARTID, SF, df, cf, intord, SSID, BT, DT, SO, GO, AX, AY, AZ, BX, BY, BZ, InOut ContEntityHelp OptionalCard
*CONTACT_ERODI NG_ NODES_TO_SURF ACE(ID)
Heading, SSID TBD, MSID TBD, SBOXID, MBOXID, SPR, MPR, FS, FD, DC, VC, VDC, PENCHK, BT, DT, SFS, SFM, SST, MST, SFST, SFMT, FSF, VSF, ISYM, EROSOP, IADJ SlaveMasterAddHelp mppOption AdditionalCards
*CONTACT_ERODI NG_ NODES_TO_SURF ACE_ MPP(ID)
Heading, TRACKPEN, BUCKET, LCBUCKET, NSEG2TRACK, INITITER, PARMAX, CPARM8, SSID TBD, MSID TBD, SBOXID, MBOXID, SPR, MPR, FS, FD, DC, VC, VDC, PENCHK, BT, DT, SFS, SFM, SST, MST, SFST, SFMT,
Altair Engineering

FSF, VSF, ISYM, EROSOP, IADJ SlaveMasterAddHelp OptionalCard AdditionalCards *CONTACT_ERODI NG_ SINGLE_SURFACE (ID) Heading, SSID TBD, MSID TBD, SBOXID, MBOXID, SPR, MPR, FS, FD, DC, VC, VDC, PENCHK, BT, DT, SFS, SFM, SST, MST, SFST, SFMT, FSF, VSF, ISYM, EROSOP, IADJ SlaveMasterAddHelp mppOption AdditionalCards *CONTACT_ERODI NG_ SINGLE_SURFACE _MPP (ID) Heading, TRACKPEN, BUCKET, LCBUCKET, NSEG2TRACK, INITITER, PARMAX, CPARM8, SSID TBD, MSID TBD, SBOXID, MBOXID, SPR, MPR, FS, FD, DC, VC, VDC, PENCHK, BT, DT, SFS, SFM, SST, MST, SFST, SFMT, FSF, VSF, ISYM, EROSOP, IADJ SlaveMasterAddHelp OptionalCard AdditionalCards *CONTACT_ERODI NG_ SURFACE_TO_SU RFACE (ID) Heading, SSID TBD, MSID TBD, SBOXID, MBOXID, SPR, MPR, FS, FD, DC, VC, VDC, PENCHK, BT, DT, SFS, SFM, SST, MST, SFST,

Altair Engineering
SFMT, FSF, VSF, ISYM, EROSOP, IADF SlaveMasterAddHelp mppOption AdditionalCards *CONTACT_ERODI NG_ SURFACE_TO_SU RFACE_ MPP(ID) Heading, TRACKPEN, BUCKET, LCBUCKET, NSEG2TRACK, INITITER, PARMAX, CPARM8, SSID TBD, MSID TBD, SBOXID, MBOXID, SPR, MPR, FS, FD, DC, VC, VDC, PENCHK, BT, DT, SFS, SFM, SST, MST, SFST, SFMT, FSF, VSF, ISYM, EROSOP, IADF SlaveMasterAddHelp *CONTACT_FORCE _ TRANSDUCER_ CONSTRAINT(ID) HEADING, SBOXID, MBOXID, SPR, MPR, SSID, MSID, FS, FD, DC, VC, VDC, PENCHK, BT, DT, SFS, SFM, SST, MST, SFST, SFMT, FSF, VSF SlaveMasterAddHelp mppOption AdditionalCards *CONTACT_FORCE _ TRANSDUCER_ CONSTRAINT_MPP (ID) Heading, TRACKPEN, BUCKET, LCBUCKET, NSEG2TRACK, INITITER, PARMAX, CPARM8, SBOXID, MBOXID, SPR, MPR, SSID, MSID, FS, FD, DC, VC,
Altair Engineering

VDC, PENCHK, BT, DT, SFS, SFM, SST, MST, SFST, SFMT, FSF, VSF SlaveMasterAddHelp OptionalCard AdditionalCards *CONTACT_FORCE _ TRANSDUCER_PE NALTY (ID) HEADING, SBOXID, MBOXID, SPR, MPR, SSID, MSID, FS, FD, DC, VC, VDC, PENCHK, BT, DT, SFS, SFM, SST, MST, SFST, SFMT, FSF, VSF SlaveMasterAddHelp mppOption AdditionalCards *CONTACT_FORCE _ TRANSDUCER_PE NALTY_ MPP(ID) Heading, TRACKPEN, BUCKET, LCBUCKET, NSEG2TRACK, INITITER, PARMAX, CPARM8, SBOXID, MBOXID, SPR, MPR, SSID, MSID, FS, FD, DC, VC, VDC, PENCHK, BT, DT, SFS, SFM, SST, MST, SFST, SFMT, FSF, VSF SlaveMasterAddHelp OptionalCard AdditionalCards *CONTACT_FORMI NG_ NODES_TO_SURF ACE(ID) HEADING, SBOXID, MBOXID, SPR, MPR, SSID, MSID, FS, FD, DC, VC, VDC, PENCHK, BT, DT, SFS, SFM, SST, MST, SFST, SFMT, FSF, VSF

Altair Engineering
SlaveMasterAddHelp SMOOTH mppOption AdditionalCards *CONTACT_FORMI NG_ NODES_TO_SURF ACE_ MPP(ID) Heading, TRACKPEN, BUCKET, LCBUCKET, NSEG2TRACK, INITITER, PARMAX, CPARM8, SBOXID, MBOXID, SPR, MPR, SSID, MSID, FS, FD, DC, VC, VDC, PENCHK, BT, DT, SFS, SFM, SST, MST, SFST, SFMT, FSF, VSF SlaveMasterAddHelp OptionalCard AdditionalCards *CONTACT_FORMI NG_ NODES_TO_SURF ACE_ SMOOTH(ID) HEADING, SBOXID, MBOXID, SPR, MPR, SSID, MSID, FS, FD, DC, VC, VDC, PENCHK, BT, DT, SFS, SFM, SST, MST, SFST, SFMT, FSF, VSF SlaveMasterAddHelp mppOption AdditionalCards *CONTACT_FORMI NG_ NODES_TO_SURF ACE_ SMOOTH_MPP(ID) Heading, TRACKPEN, BUCKET, LCBUCKET, NSEG2TRACK, INITITER, PARMAX, CPARM8, SBOXID, MBOXID, SPR, MPR, SSID, MSID, FS, FD, DC, VC, VDC, PENCHK, BT, DT, SFS, SFM, SST,
Altair Engineering

MST, SFST, SFMT, FSF, VSF SlaveMasterAddHelp OptionalCard AdditionalCards *CONTACT_FORMI NG_ ONEWAY_SURFA CE_TO_ SURFACE(ID) HEADING, SBOXID, MBOXID, SPR, MPR, SSID, MSID, FS, FD, DC, VC, VDC, PENCHK, BT, DT, SFS, SFM, SST, MST, SFST, SFMT, FSF, VSF SlaveMasterAddHelp SMOOTH mppOption AdditionalCards *CONTACT_FORMI NG_ ONEWAY_SURFA CE_TO_ SURFACE_CONST RAINED _OFFSET(ID) Heading, SBOXID, MBOXID, SPR, MPR, FS, FD, DC, VC, VDC, PENCHK, BT, DT, SFS, SFM, SST, MST, SFST, SFMT, FSF, VSF SMOOTH *CONTACT_FORMI NG_ ONEWAY_SURFA CE_TO_ SURFACE_CONST RAINED _OFFSET_MPP(ID) Heading, TRACKPEN, BUCKET, LCBUCKET, NSEG2TRACK, INITITER, PARMAX, CPARM8, SBOXID, MBOXID, SPR, MPR, SSID, MSID, FS, FD, DC, VC, VDC, PENCHK, BT, DT, SFS, SFM, SST, MST, SFST, SFMT, FSF, VSF SlaveMasterAddHelp SMOOTH OptionalCard

Altair Engineering
AdditionalCards *CONTACT_FORMI NG_ ONEWAY_SURFA CE_TO_ SURFACE_CONST RAINED _OFFSET_SMOOT H(ID) *CONTACT_FORMI NG_ ONEWAY_SURFA CE_TO_ SURFACE_CONST RAINED _OFFSET_SMOOT H_MPP (ID) Heading, SBOXID, MBOXID, SPR, MPR, FS, FD, DC, VC, VDC, PENCHK, BT, DT, SFS, SFM, SST, MST, SFST, SFMT, FSF, VSF
Heading, TRACKPEN, BUCKET, LCBUCKET, NSEG2TRACK, INITITER, PARMAX, CPARM8, SBOXID, MBOXID, SPR, MPR, SSID, MSID, FS, FD, DC, VC, VDC, PENCHK, BT, DT, SFS, SFM, SST, MST, SFST, SFMT, FSF, VSF SlaveMasterAddHelp OptionalCard AdditionalCards
*CONTACT_FORMI NG_ ONEWAY_SURFA CE_TO_ SURFACE_MPP(ID)
Altair Engineering

*CONTACT_FORMI NG_ ONEWAY_SURFA CE_TO_ SURFACE_SMOOT H(ID)
HEADING, SBOXID, MBOXID, SPR, MPR, SSID, MSID, FS, FD, DC, VC, VDC, PENCHK, BT, DT, SFS, SFM, SST, MST, SFST, SFMT, FSF, VSF SlaveMasterAddHelp mppOption AdditionalCards
*CONTACT_FORMI NG_ ONEWAY_SURFA CE_TO_ SURFACE_SMOOT H_ MPP(ID)
*CONTACT_FORMI NG_ SURFACE_TO_SU RFACE (ID)
HEADING, SBOXID, MBOXID, SPR, MPR, SSID, MSID, FS, FD, DC, VC, VDC, PENCHK, BT, DT, SFS, SFM, SST, MST, SFST, SFMT, FSF, VSF SlaveMasterAddHelp mppOption AdditionalCards
*CONTACT_FORMI NG_ SURFACE_TO_SU RFACE_
SBOXID, MBOXID, SPR, MPR, FS, FD, DC, VC, VDC, PENCHK, BT, DT,

Altair Engineering
CONSTRAINED_OF FSET (ID)
SFS, SFM, SST, MST, SFST, SFMT, FSF, VSF SlaveMasterAddHelp OneWay, SMOOTH mppOption AdditionalCards
*CONTACT_FORMI NG_ SURFACE_TO_SU RFACE_ CONSTRAINED_OF FSET_ MPP(ID)
Heading, TRACKPEN, BUCKET, LCBUCKET, NSEG2TRACK, INITITER, PARMAX, CPARM8, SBOXID, MBOXID, SPR, MPR, FS, FD, DC, VC, VDC, PENCHK, BT, DT, SFS, SFM, SST, MST, SFST, SFMT, FSF, VSF OneWay, SMOOTH OptionalCard
*CONTACT_FORMI NG_ SURFACE_TO_SU RFACE_ CONSTRAINED_OF FSET_ SMOOTH(ID)
SBOXID, MBOXID, SPR, MPR, FS, FD, DC, VC, VDC, PENCHK, BT, DT, SFS, SFM, SST, MST, SFST, SFMT, FSF, VSF SlaveMasterAddHelp OneWay, SMOOTH mppOption AdditionalCards
*CONTACT_FORMI NG_ SURFACE_TO_SU RFACE_ CONSTRAINED_OF FSET_ SMOOTH_mpp(ID)
Heading, TRACKPEN, BUCKET, LCBUCKET, NSEG2TRACK, INITITER, PARMAX, CPARM8, SBOXID, MBOXID, SPR,
Altair Engineering

MPR, FS, FD, DC, VC, VDC, PENCHK, BT, DT, SFS, SFM, SST, MST, SFST, SFMT, FSF, VSF OneWay, SMOOTH OptionalCard *CONTACT_FORMI NG_ SURFACE_TO_SU RFACE_ MPP(ID) Heading, TRACKPEN, BUCKET, LCBUCKET, NSEG2TRACK, INITITER, PARMAX, CPARM8, SBOXID, MBOXID, SPR, MPR, SSID, MSID, FS, FD, DC, VC, VDC, PENCHK, BT, DT, SFS, SFM, SST, MST, SFST, SFMT, FSF, VSF SlaveMasterAddHelp OptionalCard AdditionalCards *CONTACT_FORMI NG_ SURFACE_TO_SU RFACE_ SMOOTH(ID) HEADING, SBOXID, MBOXID, SPR, MPR, SSID, MSID, FS, FD, DC, VC, VDC, PENCHK, BT, DT, SFS, SFM, SST, MST, SFST, SFMT, FSF, VSF SlaveMasterAddHelp mppOption AdditionalCards *CONTACT_FORMI NG_ SURFACE_TO_SU RFACE_ SMOOTH_MPP(ID) Heading, TRACKPEN, BUCKET, LCBUCKET, NSEG2TRACK, INITITER, PARMAX, CPARM8, SBOXID, MBOXID, SPR,

Altair Engineering
MPR, SSID, MSID, FS, FD, DC, VC, VDC, PENCHK, BT, DT, SFS, SFM, SST, MST, SFST, SFMT, FSF, VSF SlaveMasterAddHelp OptionalCard AdditionalCards *CONTACT_INTERI OR(ID) Define interior contact for foam PSID hexahedral and tetrahedral SlaveDefnSelectHelp elements. mppOption Heading, TRACKPEN, BUCKET, LCBUCKET, NSEG2TRACK, INITITER, PARMAX, CPARM8, PSID HEADING, SBOXID, MBOXID, SPR, MPR, SSID, MSID, FS, FD, DC, VC, VDC, PENCHK, BT, DT, SFS, SFM, SST, MST, SFST, SFMT, FSF, VSF SlaveMasterAddHelp SMOOTH mppOption AdditionalCards *CONTACT_NODES _TO_ SURFACE_ INTERFERENCE (ID) Heading, SSID TBD, MSID TBD, SBOXID, MBOXID, SPR, MPR, FS, FD, DC, VC, VDC, PENCHK, BT, DT, SFS, SFM, SST, MST, SFST, FSF, VSF, LCID1, LCID2 SlaveMasterAddHelp mppOption
*CONTACT_INTERI OR_ MPP(ID)
*CONTACT_NODES _TO_ SURFACE(ID)
Altair Engineering

AdditionalCards *CONTACT_NODES _TO_ SURFACE_ INTERFERENCE_M PP(ID) Heading, TRACKPEN, BUCKET, LCBUCKET, NSEG2TRACK, INITITER, PARMAX, CPARM8, SBOXID, MBOXID, SPR, MPR, SSID, MSID, FS, FD, DC, VC, VDC, PENCHK, BT, DT, SFS, SFM, SST, MST, SFST, SFMT, FSF, VSF, LCID1, LCID2 SlaveMasterAddHelp OptionalCard AdditionalCards *CONTACT_NODES _TO_ SURFACE_MPP(ID) Heading, TRACKPEN, BUCKET, LCBUCKET, NSEG2TRACK, INITITER, PARMAX, CPARM8, SBOXID, MBOXID, SPR, MPR, SSID, MSID, FS, FD, DC, VC, VDC, PENCHK, BT, DT, SFS, SFM, SST, MST, SFST, SFMT, FSF, VSF SlaveMasterAddHelp SMOOTH OptionalCard AdditionalCards *CONTACT_NODES _TO_ SURFACE_SMOOT H(ID) Heading, SSID TBD, MSID TBD, SBOXID, MBOXID, SPR, MPR, FS, FD, DC, VC, VDC, PENCHK, BT, DT, SFS, SFM, SST, MST, SFST,

Altair Engineering
FSF, VSF SlaveMasterAddHelp mppOption AdditionalCards *CONTACT_NODES _TO_ SURFACE_SMOOT H_ MPP(ID) Heading, TRACKPEN, BUCKET, LCBUCKET, NSEG2TRACK, INITITER, PARMAX, CPARM8, SBOXID, MBOXID, SPR, MPR, SSID, MSID, FS, FD, DC, VC, VDC, PENCHK, BT, DT, SFS, SFM, SST, MST, SFST, SFMT, FSF, VSF SlaveMasterAddHelp OptionalCard AdditionalCards Heading, SSID TBD, MSID TBD, SBOXID, MBOXID, SPR, MPR, FS, FD, DC, VC, VDC, PENCHK, BT, DT, SFS, SFM, SST, MST, SFST, FSF, VSF SlaveMasterAddHelp mppOption AdditionalCards *CONTACT_ONE_ WAY_ SURFACE_TO_SU RFACE_ INTERFERENCE (ID) Heading, SSID TBD, MSID TBD, SBOXID, MBOXID, SPR, MPR, FS, FD, DC, VC, VDC, PENCHK, BT, DT, SFS, SFM, SST, MST, SFST, FSF, VSF, LCID1, LCID2 SlaveMasterAddHelp
*CONTACT_ONE_ WAY_ SURFACE_TO_SU RFACE (ID)
Altair Engineering

mppOption AdditionalCards *CONTACT_ONE_ WAY_ SURFACE_TO_SU RFACE_ INTERFERENCE_ CONSTRAINED_OF FSET (ID) Heading, SBOXID, MBOXID, SPR, MPR, FS, FD, DC, VC, VDC, PENCHK, BT, DT, SFS, SFM, SST, MST, SFST, SFMT, FSF, VSF, LCID1, LCID2 SlaveMasterAddHelp OneWay mppOption AdditionalCards *CONTACT_ONE_ WAY_ SURFACE_TO_SU RFACE_ INTERFERENCE_ CONSTRAINED_OF FSET_ MPP(ID) Heading, TRACKPEN, BUCKET, LCBUCKET, NSEG2TRACK, INITITER, PARMAX, CPARM8, SBOXID, MBOXID, SPR, MPR, SSID, MSID, FS, FD, DC, VC, VDC, PENCHK, BT, DT, SFS, SFM, SST, MST, SFST, SFMT, FSF, VSF SlaveMasterAddHelp OptionalCard AdditionalCards *CONTACT_ONE_ WAY_ SURFACE_TO_SU RFACE_ INTERFERENCE_M PP(ID) Heading, TRACKPEN, BUCKET, LCBUCKET, NSEG2TRACK, INITITER, PARMAX, CPARM8, SBOXID, MBOXID, SPR, MPR, SSID, MSID, FS, FD, DC, VC, VDC, PENCHK, BT, DT, SFS, SFM, SST, MST, SFST, SFMT,

Altair Engineering
FSF, VSF, LCID1, LCID2 SlaveMasterAddHelp OptionalCard AdditionalCards *CONTACT_ONE_ WAY_ SURFACE_TO_SU RFACE_ MPP(ID) Heading, TRACKPEN, BUCKET, LCBUCKET, NSEG2TRACK, INITITER, PARMAX, CPARM8, SBOXID, MBOXID, SPR, MPR, SSID, MSID, FS, FD, DC, VC, VDC, PENCHK, BT, DT, SFS, SFM, SST, MST, SFST, SFMT, FSF, VSF SlaveMasterAddHelp OptionalCard AdditionalCards *CONTACT_ONE_ WAY_ SURFACE_TO_SU RFACE_ SMOOTH(ID) Heading, SSID TBD, MSID TBD, SBOXID, MBOXID, SPR, MPR, FS, FD, DC, VC, VDC, PENCHK, BT, DT, SFS, SFM, SST, MST, SFST, FSF, VSF SlaveMasterAddHelp mppOption AdditionalCards *CONTACT_ONE_ WAY_ SURFACE_TO_SU RFACE_ SMOOTH_MPP(ID) Heading, TRACKPEN, BUCKET, LCBUCKET, NSEG2TRACK, INITITER, PARMAX, CPARM8, SBOXID, MBOXID, SPR, MPR, SSID, MSID, FS, FD, DC, VC, VDC, PENCHK, BT,
Altair Engineering

DT, SFS, SFM, SST, MST, SFST, SFMT, FSF, VSF SlaveMasterAddHelp OptionalCard AdditionalCards *CONTACT_RIGID_ BODY_ ONE_WAY_TO_RI GID_ BODY(ID) Define rigid surface contact. HEADING, SBOXID, MBOXID, SPR, MPR, SSID, MSID, FS, FD, DC, VC, VDC, PENCHK, BT, DT, SFS, SFM, SST, MST, SFST, SFMT, FSF, VSF, LCID, FCM, US, LCDC, DSF, UNLCID SlaveMasterAddHelp TwoWayOption mppOption AdditionalCards *CONTACT_RIGID_ BODY_ ONE_WAY_TO_RI GID_ BODY_MPP(ID) Heading, TRACKPEN, BUCKET, LCBUCKET, NSEG2TRACK, INITITER, PARMAX, CPARM8, SBOXID, MBOXID, SPR, MPR, SSID, MSID, FS, FD, DC, VC, VDC, PENCHK, BT, DT, SFS, SFM, SST, MST, SFST, SFMT, FSF, VSF, LCID, FCM, US, LCDC, DSF, UNLCID SlaveMasterAddHelp TwoWayOption OptionalCard AdditionalCards *CONTACT_RIGID_ BODY_ HEADING, SBOXID, MBOXID, SPR, MPR, SSID, MSID,

Altair Engineering
TWO_WAY_TO_RI GID_ BODY(ID)
FS, FD, DC, VC, VDC, PENCHK, BT, DT, SFS, SFM, SST, MST, SFST, SFMT, FSF, VSF, LCID, FCM, US, LCDC, DSF, UNLCID SlaveMasterAddHelp mppOption AdditionalCards
*CONTACT_RIGID_ BODY_ TWO_WAY_TO_RI GID_ BODY_MPP(ID)
Heading, TRACKPEN, BUCKET, LCBUCKET, NSEG2TRACK, INITITER, PARMAX, CPARM8, SBOXID, MBOXID, SPR, MPR, SSID, MSID, FS, FD, DC, VC, VDC, PENCHK, BT, DT, SFS, SFM, SST, MST, SFST, SFMT, FSF, VSF, LCID, FCM, US, LCDC, DSF, UNLCID SlaveMasterAddHelp OptionalCard AdditionalCards
*CONTACT_RIGID_ NODES _TO_RIGID_BODY (ID)
HEADING, SBOXID, MBOXID, SPR, MPR, SSID, MSID, FS, FD, DC, VC, VDC, PENCHK, BT, DT, SFS, SFM, SST, MST, SFST, SFMT, FSF, VSF, LCID, FCM, US, LCDC, DSF, UNLCID SlaveMasterAddHelp mppOption AdditionalCards
*CONTACT_RIGID_
Heading, TRACKPEN,
Altair Engineering

NODES _TO_RIGID_BODY_ MPP (ID)
BUCKET, LCBUCKET, NSEG2TRACK, INITITER, PARMAX, CPARM8, SBOXID, MBOXID, SPR, MPR, SSID, MSID, FS, FD, DC, VC, VDC, PENCHK, BT, DT, SFS, SFM, SST, MST, SFST, SFMT, FSF, VSF, LCID, FCM, US, LCDC, DSF, UNLCID SlaveMasterAddHelp OptionalCard AdditionalCards
*CONTACT_RIGID_ SURFACE(ID)
BOXID, SEGID, FS, FD, DC, VC, LCIDX, LCIDY, LCIDZ, FSLCID, FDLCID, SFS, STTHK, SFTHK, XPENE, BSORT mppOption
*CONTACT_RIGID_ SURFACE_MPP(ID)
Heading, TRACKPEN, BUCKET, LCBUCKET, NSEG2TRACK, INITITER, PARMAX, CPARM8, BOXID, SEGID, FS, FD, DC, VC, LCIDX, LCIDY, LCIDZ, FSLCID, FDLCID, SFS, STTHK, SFTHK, XPENE, BSORT HEADING, SBOXID, MBOXID, SPR, MPR, SSID, MSID, FS, FD, DC, VC, VDC, PENCHK, BT, DT, SFS, SFM, SST, MST, SFST, SFMT,
*CONTACT_SINGL E_ EDGE(ID)

Altair Engineering
FSF, VSF SlaveMasterAddHelp mppOption AdditionalCards *CONTACT_SINGL E_ EDGE_MPP(ID) Heading, TRACKPEN, BUCKET, LCBUCKET, NSEG2TRACK, INITITER, PARMAX, CPARM8, SBOXID, MBOXID, SPR, MPR, SSID, MSID, FS, FD, DC, VC, VDC, PENCHK, BT, DT, SFS, SFM, SST, MST, SFST, SFMT, FSF, VSF SlaveMasterAddHelp OptionalCard AdditionalCards *CONTACT_SINGL E_ SURFACE(ID) HEADING, SBOXID, MBOXID, SPR, MPR, SSID, FS, FD, DC, VC, VDC, PENCHK, BT, DT, SFS, SFM, SST, MST, SFST, SFMT, FSF, VSF SlaveMasterAddHelp mppOption AdditionalCards *CONTACT_SINGL E_ SURFACE_MPP(ID) Heading, TRACKPEN, BUCKET, LCBUCKET, NSEG2TRACK, INITITER, PARMAX, CPARM8, SBOXID, MBOXID, SPR, MPR, SSID, FS, FD, DC, VC, VDC, PENCHK, BT, DT, SFS, SFM, SST,
Altair Engineering

MST, SFST, SFMT, FSF, VSF SlaveMasterAddHelp OptionalCard AdditionalCards *CONTACT_SLIDIN G_ ONLY(ID) HEADING, SBOXID, MBOXID, SPR, MPR, FS, FD, DC, VC, VDC, PENCHK, BT, DT, SFS, SFM, SST, MST, SFST, SFMT, FSF, VSF SlaveMasterAddHelp PenaltyOption mppOption AdditionalCards *CONTACT_SLIDIN G_ ONLY_MPP(ID) Heading, TRACKPEN, BUCKET, LCBUCKET, NSEG2TRACK, INITITER, PARMAX, CPARM8, SBOXID, MBOXID, SPR, MPR, SSID, FS, FD, DC, VC, VDC, PENCHK, BT, DT, SFS, SFM, SST, MST, SFST, SFMT, FSF, VSF SlaveMasterAddHelp OptionalCard AdditionalCards *CONTACT_SLIDIN G_ ONLY_PENALTY (ID) HEADING, SBOXID, MBOXID, SPR, MPR, FS, FD, DC, VC, VDC, PENCHK, BT, DT, SFS, SFM, SST, MST, SFST, SFMT, FSF, VSF SlaveMasterAddHelp PenaltyOption

Altair Engineering
mppOption AdditionalCards *CONTACT_SLIDIN G_ ONLY_PENALTY_ MPP(ID) Heading, TRACKPEN, BUCKET, LCBUCKET, NSEG2TRACK, INITITER, PARMAX, CPARM8, SBOXID, MBOXID, SPR, MPR, SSID, FS, FD, DC, VC, VDC, PENCHK, BT, DT, SFS, SFM, SST, MST, SFST, SFMT, FSF, VSF SlaveMasterAddHelp OptionalCard AdditionalCards *CONTACT_SPOT WELD (ID) HEADING, SBOXID, MBOXID, SPR, MPR, FS, FD, DC, VC, VDC, PENCHK, BT, DT, SFS, SFM, SST, MST, SFST, SFMT, FSF, VSF SlaveMasterAddHelp Options (None, Torsion) mppOption AdditionalCards *CONTACT_SPOT WELD_ MPP(ID) Heading, TRACKPEN, BUCKET, LCBUCKET, NSEG2TRACK, INITITER, PARMAX, CPARM8, SBOXID, MBOXID, SPR, MPR, SSID, FS, FD, DC, VC, VDC, PENCHK, BT, DT, SFS, SFM, SST, MST, SFST, SFMT,
Altair Engineering

FSF, VSF SlaveMasterAddHelp OptionalCard AdditionalCards *CONTACT_SPOT WELD_ WITH_TORSION(ID) HEADING, SBOXID, MBOXID, SPR, MPR, FS, FD, DC, VC, VDC, PENCHK, BT, DT, SFS, SFM, SST, MST, SFST, SFMT, FSF, VSF SlaveMasterAddHelp Options (None, Torsion) mppOption AdditionalCards *CONTACT_SPOT WELD_ WITH_TORSION_M PP(ID) Heading, TRACKPEN, BUCKET, LCBUCKET, NSEG2TRACK, INITITER, PARMAX, CPARM8, SBOXID, MBOXID, SPR, MPR, SSID, FS, FD, DC, VC, VDC, PENCHK, BT, DT, SFS, SFM, SST, MST, SFST, SFMT, FSF, VSF SlaveMasterAddHelp OptionalCard AdditionalCards Heading, SSID TBD, MSID TBD. SBOXID, MBOXID, SPR, MPR, FS, FD, DC, VC, VDC, PENCHK, BT, DT, SFS, SFM, SST, MST, SFST, SFMT, FSF, VSF SlaveMasterAddHelp
*CONTACT_SURFA CE_TO _SURFACE(ID)

Altair Engineering
OFFSET CONSTRAINED_OF FSET mppOption AdditionalCards *CONTACT_SURFA CE_TO _SURFACE_ INTERFERENCE (ID) Heading, SSID TBD, MSID TBD. SBOXID, MBOXID, SPR, MPR, FS, FD, DC, VC, VDC, PENCHK, BT, DT, SFS, SFM, SST, MST, SFST, SFMT, FSF, VSF, LCID1, LCID2 SlaveMasterAddHelp OneWay mppOption AdditionalCards *CONTACT_SURFA CE_TO _SURFACE_ INTERFERENCE_ CONSTRAINED_OF FSET Heading, SSID TBD, MSID TBD. SBOXID, MBOXID, SPR, MPR, FS, FD, DC, VC, VDC, PENCHK, BT, DT, SFS, SFM, SST, MST, SFST, SFMT, FSF, VSF, LCID1, LCID2 SlaveMasterAddHelp OneWay mppOption AdditionalCards *CONTACT_SURFA CE_TO _SURFACE_ INTERFERENCE_ CONSTRAINED_OF FSET_ MPP(ID) Heading, TRACKPEN, BUCKET, LCBUCKET, NSEG2TRACK, INITITER, PARMAX, CPARM8, SSID TBD, MSID TBD. SBOXID, MBOXID, SPR, MPR, FS, FD, DC, VC, VDC, PENCHK, BT, DT,
Altair Engineering

SFS, SFM, SST, MST, SFST, SFMT, FSF, VSF, LCID1, LCID2 SlaveMasterAddHelp OneWay OptionalCard AdditionalCard *CONTACT_SURFA CE_TO _SURFACE_ INTERFERENCE_M PP(ID) Heading, TRACKPEN, BUCKET, LCBUCKET, NSEG2TRACK, INITITER, PARMAX, CPARM8, SSID TBD, MSID TBD. SBOXID, MBOXID, SPR, MPR, FS, FD, DC, VC, VDC, PENCHK, BT, DT, SFS, SFM, SST, MST, SFST, SFMT, FSF, VSF, LCID1, LCID2 SlaveMasterAddHelp OneWay OptionalCard AdditionalCards *CONTACT_SURFA CE_TO _SURFACE_MPP (ID) Heading, TRACKPEN, BUCKET, LCBUCKET, NSEG2TRACK, INITITER, PARMAX, CPARM8, SSID TBD, MSID TBD. SBOXID, MBOXID, SPR, MPR, FS, FD, DC, VC, VDC, PENCHK, BT, DT, SFS, SFM, SST, MST, SFST, SFMT, FSF, VSF SlaveMasterAddHelp

Altair Engineering
OFFSET CONSTRAINED_OF FSET OptionalCard AdditionalCards *CONTACT_SURFA CE_TO _SURFACE_SMOO TH(ID) Heading, SSID TBD, MSID TBD. SBOXID, MBOXID, SPR, MPR, FS, FD, DC, VC, VDC, PENCHK, BT, DT, SFS, SFM, SST, MST, SFST, SFMT, FSF, VSF SlaveMasterAddHelp OneWay, THERMAL, SMOOTH mppOption AdditionalCards *CONTACT_SURFA CE_TO _SURFACE_SMOO TH_ MPP(ID) Heading, TRACKPEN, BUCKET, LCBUCKET, NSEG2TRACK, INITITER, PARMAX, CPARM8, SSID TBD, MSID TBD. SBOXID, MBOXID, SPR, MPR, FS, FD, DC, VC, VDC, PENCHK, BT, DT, SFS, SFM, SST, MST, SFST, SFMT, FSF, VSF SlaveMasterAddHelp OneWay, THERMAL, SMOOH OptionalCard AdditionalCards *CONTACT_THERM AL_ SURFACE_TO_SU Heading, SSID TBD, MSID TBD. SBOXID, MBOXID, SPR, MPR, FS, FD, DC,
Altair Engineering

RFACE_(ID)
VC, VDC, PENCHK, BT, DT, SFS, SFM, SST, MST, SFST, SFMT, FSF, VSF, K, FRAD, H0, LMIN, LMAX, CHLM, BC_FLAG, ALGO SlaveMasterAddHelp OneWay, THERMAL, SMOOTH mppOption AdditionalCards
*CONTACT_THERM AL_ SURFACE_TO_SU RFACE_ MPP(ID)
Heading, TRACKPEN, BUCKET, LCBUCKET, NSEG2TRACK, INITITER, PARMAX, CPARM8, SSID TBD, MSID TBD. SBOXID, MBOXID, SPR, MPR, FS, FD, DC, VC, VDC, PENCHK, BT, DT, SFS, SFM, SST, MST, SFST, SFMT, FSF, VSF, K, FRAD, H0, LMIN, LMAX, CHLM, BC_FLAG, ALGO SlaveMasterAddHelp OneWay, THERMAL, SMOOTH OptionalCard AdditionalCards Heading, SSID TBD, MSID TBD, SBOXID, MBOXID, SPR, MPR, FS, FD, DC, VC, VDC, PENCHK, BT, DT, SFS, SFM, SST, MST, SFST,
*CONTACT_TIEBRE AK_ NODES_TO_SURF ACE(ID)

Altair Engineering
SFMT, FSF, VSF, NFLF, SFLF, NEN, MES SlaveMasterAddHelp mppOption AdditionalCards *CONTACT_TIEBRE AK_ NODES_TO_SURF ACE_ MPP(ID) Heading, TRACKPEN, BUCKET, LCBUCKET, NSEG2TRACK, INITITER, PARMAX, CPARM8, SSID TBD, MSID TBD, SBOXID, MBOXID, SPR, MPR, FS, FD, DC, VC, VDC, PENCHK, BT, DT, SFS, SFM, SST, MST, SFST, SFMT, FSF, VSF, NFLF, SFLF, NEN, MES SlaveMasterAddHelp OptionalCard AdditionalCards *CONTACT_TIEBRE AK_ SURFACE_TO_SU RFACE (ID) Heading, SSID TBD, MSID TBD, SBOXID, MBOXID, SPR, MPR, FS, FD, DC, VC, VDC, PENCHK, BT, DT, SFS, SFM, SST, MST, SFST, SFMT, FSF, VSF, NFLS, SFLS, TBLCID, THKOFF SlaveMasterAddHelp mppOption AdditionalCards *CONTACT_TIEBRE AK_ SURFACE_TO_SU RFACE_ MPP(ID) Heading, TRACKPEN, BUCKET, LCBUCKET, NSEG2TRACK, INITITER, PARMAX,
Altair Engineering

CPARM8, SSID TBD, MSID TBD, SBOXID, MBOXID, SPR, MPR, FS, FD, DC, VC, VDC, PENCHK, BT, DT, SFS, SFM, SST, MST, SFST, SFMT, FSF, VSF, NFLS, SFLS, TBLCID, THKOFF SlaveMasterAddHelp OptionalCard AdditionalCards *CONTACT_TIED_N ODES_ TO_SURFACE(ID) HEADING, SBOXID, MBOXID, SPR, MPR, FS, FD, DC, VC, VDC, PENCHK, BT, DT, SFS, SFM, SST, MST, SFMT, FSF, VSF SlaveMasterAddHelp OFFSET CONSTRAINED_OF FSET mppOption AdditionalCards *CONTACT_TIED_N ODES_ TO_SURFACE_ CONSTRAINED_OF FSET (ID) HEADING, SBOXID, MBOXID, SPR, MPR, FS, FD, DC, VC, VDC, PENCHK, BT, DT, SFS, SFM, SST, MST, SFMT, FSF, VSF SlaveMasterAddHelp OFFSET CONSTRAINED_OF FSET mppOption AdditionalCards *CONTACT_TIED_N ODES_ Heading, TRACKPEN,

Altair Engineering
TO_SURFACE_ CONSTRAINED_OF FSET_ MPP(ID)
BUCKET, LCBUCKET, NSEG2TRACK, INITITER, PARMAX, CPARM8, SBOXID, MBOXID, SPR, MPR, FS, FD, DC, VC, VDC, PENCHK, BT, DT, SFS, SFM, SST, MST, SFMT, FSF, VSF SlaveMasterAddHelp OFFSET CONSTRAINED_OF FSET OptionalCard AdditionalCards
*CONTACT_TIED_N ODES_ TO_SURFACE_MP P(ID)
Heading, TRACKPEN, BUCKET, LCBUCKET, NSEG2TRACK, INITITER, PARMAX, CPARM8, SBOXID, MBOXID, SPR, MPR, FS, FD, DC, VC, VDC, PENCHK, BT, DT, SFS, SFM, SST, MST, SFMT, FSF, VSF SlaveMasterAddHelp OFFSET CONSTRAINED_OF FSET OptionalCard AdditionalCards
*CONTACT_TIED_N ODES_ TO_SURFACE_OF FSET (ID)
HEADING, SBOXID, MBOXID, SPR, MPR, FS, FD, DC, VC, VDC, PENCHK, BT, DT, SFS, SFM, SST, MST, SFMT, FSF, VSF SlaveMasterAddHelp
Altair Engineering

OFFSET CONSTRAINED_OF FSET mppOption AdditionalCards *CONTACT_TIED_N ODES_ TO_SURFACE_OF FSET _MPP(ID) Heading, TRACKPEN, BUCKET, LCBUCKET, NSEG2TRACK, INITITER, PARMAX, CPARM8, SBOXID, MBOXID, SPR, MPR, FS, FD, DC, VC, VDC, PENCHK, BT, DT, SFS, SFM, SST, MST, SFMT, FSF, VSF SlaveMasterAddHelp OFFSET CONSTRAINED_OF FSET OptionalCard AdditionalCards *CONTACT_TIED_S HELL_ EDGE_TO_SURFA CE(ID) HEADING, SBOXID, MBOXID, SPR, MPR, FS, FD, DC, VC, VDC, PENCHK, BT, DT, SFS, SFM, SST, MST, SFMT, FSF, VSF SlaveMasterAddHelp TiedOptions (None, Offset, BeamOffset, Constrained Offset) mppOption AdditionalCards *CONTACT_TIED_S HELL_ EDGE_TO_SURFA CE_ BEAM_OFFSET(ID) HEADING, SBOXID, MBOXID, SPR, MPR, FS, FD, DC, VC, VDC, PENCHK, BT, DT, SFS, SFM,

Altair Engineering
SST, MST, SFMT, FSF, VSF SlaveMasterAddHelp mppOption AdditionalCards *CONTACT_TIED_S HELL_ EDGE_TO_SURFA CE_ BEAM_OFFSET_M PP(ID) Heading, TRACKPEN, BUCKET, LCBUCKET, NSEG2TRACK, INITITER, PARMAX, CPARM8, SBOXID, MBOXID, SPR, MPR, FS, FD, DC, VC, VDC, PENCHK, BT, DT, SFS, SFM, SST, MST, SFMT, FSF, VSF SlaveMasterAddHelp OptionalCard AdditionalCards *CONTACT_TIED_S HELL_ EDGE_TO_SURFA CE_ CONSTRAINED_OF FSET (ID) HEADING, SBOXID, MBOXID, SPR, MPR, FS, FD, DC, VC, VDC, PENCHK, BT, DT, SFS, SFM, SST, MST, SFMT, FSF, VSF SlaveMasterAddHelp mppOption AdditionalCards *CONTACT_TIED_S HELL_ EDGE_TO_SURFA CE_ CONSTRAINED_OF FSET_ MPP(ID) Heading, TRACKPEN, BUCKET, LCBUCKET, NSEG2TRACK, INITITER, PARMAX, CPARM8, SBOXID, MBOXID, SPR, MPR, FS, FD, DC, VC, VDC, PENCHK, BT, DT, SFS, SFM, SST, MST, SFMT, FSF, VSF
Altair Engineering

SlaveMasterAddHelp OptionalCard AdditionalCards *CONTACT_TIED_S HELL_ EDGE_TO_SURFA CE_ MPP(ID) Heading, TRACKPEN, BUCKET, LCBUCKET, NSEG2TRACK, INITITER, PARMAX, CPARM8, SBOXID, MBOXID, SPR, MPR, FS, FD, DC, VC, VDC, PENCHK, BT, DT, SFS, SFM, SST, MST, SFMT, FSF, VSF SlaveMasterAddHelp OptionalCard AdditionalCards *CONTACT_TIED_S HELL_ EDGE_TO_SURFA CE_ OFFSET(ID) HEADING, SBOXID, MBOXID, SPR, MPR, FS, FD, DC, VC, VDC, PENCHK, BT, DT, SFS, SFM, SST, MST, SFMT, FSF, VSF SlaveMasterAddHelp mppOption AdditionalCards *CONTACT_TIED_S HELL_ EDGE_TO_SURFA CE_ OFFSET_MPP(ID) Heading, TRACKPEN, BUCKET, LCBUCKET, NSEG2TRACK, INITITER, PARMAX, CPARM8, SBOXID, MBOXID, SPR, MPR, FS, FD, DC, VC, VDC, PENCHK, BT, DT, SFS, SFM, SST, MST, SFMT, FSF, VSF SlaveMasterAddHelp

Altair Engineering
OptionalCard AdditionalCards *CONTACT_TIED_ SURFACE_TO_SU RFACE (ID) HEADING, SBOXID, MBOXID, SPR, MPR, FS, FD, DC, VC, VDC, PENCHK, BT, DT, SFS, SFM, SST, MST, SFMT, FSF, VSF SlaveMasterAddHelp OFFSET CONSTRAINED_OF FSET mppOption AdditionalCards *CONTACT_TIED_ SURFACE_TO_SU RFACE_ CONSTRAINED_OF FSET (ID) HEADING, SBOXID, MBOXID, SPR, MPR, FS, FD, DC, VC, VDC, PENCHK, BT, DT, SFS, SFM, SST, MST, SFMT, FSF, VSF SlaveMasterAddHelp OFFSET CONSTRAINED_OF FSET mppOption AdditionalCards *CONTACT_TIED_ SURFACE_TO_SU RFACE_ CONSTRAINED_OF FSET_ MPP(ID) Heading, TRACKPEN, BUCKET, LCBUCKET, NSEG2TRACK, INITITER, PARMAX, CPARM8, SBOXID, MBOXID, SPR, MPR, FS, FD, DC, VC, VDC, PENCHK, BT, DT, SFS, SFM, SST, MST, SFMT, FSF, VSF SlaveMasterAddHelp
Altair Engineering

OptionalCard AdditionalCards *CONTACT_TIED_ SURFACE_TO_SU RFACE_ MPP(ID) Heading, TRACKPEN, BUCKET, LCBUCKET, NSEG2TRACK, INITITER, PARMAX, CPARM8, SBOXID, MBOXID, SPR, MPR, FS, FD, DC, VC, VDC, PENCHK, BT, DT, SFS, SFM, SST, MST, SFMT, FSF, VSF SlaveMasterAddHelp OptionalCard AdditionalCards *CONTACT_TIED_ SURFACE_TO_SU RFACE_ OFFSET(ID) HEADING, SBOXID, MBOXID, SPR, MPR, FS, FD, DC, VC, VDC, PENCHK, BT, DT, SFS, SFM, SST, MST, SFMT, FSF, VSF SlaveMasterAddHelp mppOption AdditionalCards *CONTACT_TIED_ SURFACE_TO_SU RFACE_ OFFSET_MPP(ID) Heading, TRACKPEN, BUCKET, LCBUCKET, NSEG2TRACK, INITITER, PARMAX, CPARM8, SBOXID, MBOXID, SPR, MPR, FS, FD, DC, VC, VDC, PENCHK, BT, DT, SFS, SFM, SST, MST, SFMT, FSF, VSF SlaveMasterAddHelp OptionalCard

Altair Engineering
AdditionalCards *CONTACT_TIED_ SURFACE_TO_SU RFACE_ TITLE(ID)
*CONTACT_2D_ Define a 2-dimensional AUTOMATIC_SURF contact or slide line. ACE_ TO_SURFACE(ID) *CONTACT_2D_ AUTOMATIC_SURF ACE_ TO_SURFACE_THE RMAL_ TITLE(ID) Dyna_Name, SFACT, FREQ, FS, FD, DC, MEMBS, TBIRTH, TDEATH, SOS, SOM, NDS, NDM, IPF, INIT, K, FRAD, H0, LMIN, LMAX, CHLM, BC_FLAG, ALGO SlaveMasterAddHelp Options (Automatic) mppOption AdditionalCards *CONTACT_2D_ AUTOMATIC_SURF ACE_ TO_SURFACE_THE RMAL_ TITLE_MPP(ID) TRACKPEN, BUCKET, LCBUCKET, NSEG2TRACK, INITITER, PARMAX, CPARM8, Dyna_Name, SFACT, FREQ, FS, FD, DC, MEMBS, TBIRTH, TDEATH, SOS, SOM, NDS, NDM, IPF, INIT, K, FRAD, H0, LMIN, LMAX, CHLM, BC_FLAG, ALGO SlaveMasterAddHelp Options (Automatic) OptionalCard AdditionalCards
Altair Engineering

*CONTACT_2D_ AUTOMATIC_SURF ACE_ TO_SURFACE_TITL E(ID)
Dyna_Name, SFACT, FREQ, FS, FD, DC, MEMBS, TBIRTH, TDEATH, SOS, SOM, NDS, NDM, IPF, INIT SlaveMasterAddHelp Options (Automatic) THERMAL mppOption AdditionalCards
*CONTACT_2D_ AUTOMATIC_SURF ACE_ TO_SURFACE_TITL E_MPP (ID)
TRACKPEN, BUCKET, LCBUCKET, NSEG2TRACK, INITITER, PARMAX, CPARM8, Dyna_Name, SFACT, FREQ, FS, FD, DC, MEMBS, TBIRTH, TDEATH, SOS, SOM, NDS, NDM, IPF, INIT SlaveMasterAddHelp Options (Automatic) THERMAL OptionalCard AdditionalCards
*DATABASE_CRO SS_ SECTION_SET(ID)
Define a cross section for resultant forces written to ASCII file SECFORC.
Dyna_Name, HSID, BSID, SSID, TSID, DSID, PID DatabaseXSectSetH elp LocalSystemFlag (RigidBody, Accelerometer, Coordinate ID)
*DATABASE_CRO SS_ SECTION_PLANE (ID)
XsectionPlane
PSID TBD

Altair Engineering
*DATABASE_FSI
Used to output information about certain coupled Lagrangian surfaces. Define a nodal force group for output into ASCII file NODFOR and the binary file XTFILE.
PSID TBD
*DATABASE_NOD AL_ FORCE_GROUP
CID
*ELEMENT_TRIM
Define a part subset to be trimmed by *DEFINE_CURVE_TRIM MMGID TEMP PSID TBD RO1 - RO8
*INITIAL_GAS_MIXT Used to specify a) which ALE URE multi-material groups may be present inside an ALE mesh set at time zero and b) the corresponding reference gas temperature and density which define the initial thermodynamic state of the gases. *INITIAL_VOID (PART and SET) Define initial voided part set IDs or part numbers.
n/a
*INITIAL_VOLUME_ Define initial volume fractions FRACTION of different materials in multimaterial ALE elements. *INITIAL_VOLUME_ Volume filling command for FRACTION_GEOM defining the volume fractions of ETRY various ALE multi-material group that can occupy certain regions in some specified ALE mesh set. BAMMG NTRACE FILLOPT FAMMG
*INTERFACE_ Define an interface for linking COMPONENT_NOD calculations. E *INTERFACE_ Define an interface for linking COMPONENT_SEG calculations. MENT
n/a
n/a
Altair Engineering

*INTERFACE_LINKI Define an interface for linking NG_ discrete nodes to an interface DISCRETE_NODE_ file. SET
IFID Edge
*INTERFACE_LINKI Define an interface for linking a IFID NG_ series of nodes in a shell EDGE structure to an interface file for the second analysis using L=isf2 on the execution command line. *INTERFACE_LINKI Define an interface for linking NG_ segments to an interface file SEGMENT for the second analysis using L=isf2 on the execution command line. IFID
*RIGIDWALL_GEO METRIC _CYLINDER_ID *RIGIDWALL_GEO METRIC _CYLINDER_MOTI ON_ID *RIGIDWALL_GEO METRIC _FLAT_ID *RIGIDWALL_GEO METRIC _FLAT (FINITE) *RIGIDWALL_GEO METRIC _FLAT_MOTION_ID *RIGIDWALL_GEO METRIC _FLAT_MOTION (FINITE) *RIGIDWALL_GEO METRIC _PRISM_ID
Define a rigid wall with an analytically described form.
Name, exclude, BOXID, BIRTH, DEATH, Fric Name, exclude, BOXID, BIRTH, DEATH, Fric
Name, exclude, BOXID, BIRTH, DEATH, Fric

Altair Engineering
*RIGIDWALL_GEO METRIC _PRISM_ID (FINITE) *RIGIDWALL_GEO METRIC _PRISM_MOTION_I D *RIGIDWALL_GEO METRIC _PRISM_MOTION (FINITE) *RIGIDWALL_GEO METRIC _SPHERE_ID *RIGIDWALL_GEO METRIC _SPHERE_MOTION _ID Define a rigid wall with an analytically described form. Name, exclude, BOXID, BIRTH, DEATH, Fric Name, exclude, BOXID, BIRTH, DEATH, Fric Name, exclude, BOXID, BIRTH, DEATH, Fric
*RIGIDWALL_PLAN Define planar rigid walls with AR_ID either finite or infinite size.
Name, exclude, BOXID, OFFSET, BIRTH, DEATH, RWKSF, Fric OrthoOpt Force
*RIGIDWALL_PLAN AR_ FINITE(ID)
Name, exclude, BOXID, OFFSET, BIRTH, DEATH, RWKSF, Fric OrthoOpt Force
*RIGIDWALL_PLAN AR_ FINITE_FORCES_I D
Name, exclude, BOXID, OFFSET, BIRTH, DEATH, RWKSF, Fric, SOFT, SSID, N1-N2 Name, exclude,
*RIGIDWALL_PLAN
Altair Engineering

AR_ FINITE_FORCES_M OVING (ID) *RIGIDWALL_PLAN AR_ FINITE_MOVING_ID
BOXID, OFFSET, BIRTH, DEATH, RWKSF, Fric, mass, SOFT, SSID, N1-NR Name, exclude, BOXID, OFFSET, BIRTH, DEATH, RWKSF, Fric, mass Name, exclude, BOXID, OFFSET, BIRTH, DEATH, RWKSF, Fric, SOFT, SSID, N1-N4 Name, exclude, BOXID, OFFSET, BIRTH, DEATH, RWKSF, Fric, mass, SOFT, SSID, N1-N4 Name, exclude, BOXID, OFFSET, BIRTH, DEATH, RWKSF, Fric, mass OrthoOpt Force
*RIGIDWALL_PLAN AR_ FORCE_ID
*RIGIDWALL_PLAN AR_ FORCES_MOVING (ID)
*RIGIDWALL_PLAN AR_ MOVING(ID)
*RIGIDWALL_PLAN AR_ ORTHO(ID)
Name, exclude, BOXID, OFFSET, BIRTH, DEATH, RWKSF, Fric, SfricA, SfricB, DfricA, DfricB, DecayA, DecayB, Node1, Node2 VectorOption Force
*RIGIDWALL_PLAN AR_ ORTHO_FINITE_ID
Name, exclude, BOXID, OFFSET, BIRTH, DEATH, RWKSF, Fric, SfricA, SfricB, DfricA, DfricB,

Altair Engineering
DecayA, DecayB, Node VectorOption Force *RIGIDWALL_PLAN AR_ ORTHO_FINITE_FO RCES (ID) Name, exclude, BOXID, OFFSET, BIRTH, DEATH, RWKSF, Fric, SfricA, SfricB, DfricA, DfricB, DecayA, DecayB, Node1, Node2, SOFT, SSID, N1-N4 Name, exclude, BOXID, OFFSET, BIRTH, DEATH, RWKSF, Fric, SfricA, SfricB, DfricA, DfricB, DecayA, DecayB, Node1, Node2, mass Name, exclude, BOXID, OFFSET, BIRTH, DEATH, RWKSF, Fric, SfricA, SfricB, DfricA, DfricB, DecayA, DecayB, Node1, Node2, mass, SOFT, SSID, N1-N4 Name, exclude, BOXID, OFFSET, BIRTH, DEATH, RWKSF, Fric, SfricA, SfricB, DfricA, DfricB, DecayA, DecayB, Node, SOFT, SSID, N1-N4 VectorOption
*RIGIDWALL_PLAN AR_ ORTHO_FINITE_M OVING_ ID
*RIGIDWALL_PLAN AR_ ORTHO_FINITE_FO RCES_ MOVING_ID
*RIGIDWALL_PLAN AR_ ORTHO_FORCES (ID)
Altair Engineering

*RIGIDWALL_PLAN AR_ ORTHO_FORCES_ MOVING_ID
Name, exclude, BOXID, OFFSET, BIRTH, DEATH, RWKSF, Fric, SfricA, SfricB, DfricA, DfricB, DecayA, DecayB, Node1, Node2, mass, SOFT, SSID, N1-N4 Name, exclude, BOXID, OFFSET, BIRTH, DEATH, RWKSF, Fric, SfricA, SfricB, DfricA, DfricB, DecayA, DecayB, Node1, Node2, mass VectorOption Force
*RIGIDWALL_PLAN AR_ ORTHO_MOVING_I D
*SET_MULTIMATERIAL_GROUP _LIST (TITLE)
Defines an ALE multi-material set ID which contains a collection of one or more ALE multi-material group IDs.
AMMGID1 AMMGID8
MADYMO
Supported Card
Solver Description
Supported Parameters CONTACT_SURFAC E, SWITCH, CONTACT_METHOD , CONTACT_FORCE, INITIAL_PEN_TRAC K, REDUCTION_FACT OR, MAX_FORCE_PAR, DAMP_COEF,
Notes
CONTACT.FE_FE
Selects groups of FE objects to be used as master and slave surfaces in a contact calculation, and allows the user to specify the contact method.
After creating the CONTACT, add both SURFACEs: master: Select sets and add desired GROUP_FEs as set references to the MASTER_SURFACE. slave: Select 'sets' and add desired GROUP_FEs as set references to the

Altair Engineering
TIME_STEP, FRIC_FUNC, GAP_TYPE, GAP_FUNC, CONTACT_FORCE
SLAVE_SURFACE.
Defined on the card of the parent CONTACT. Defines a contact between multibody surfaces (master surface) and finite element surfaces (slave surface). CONTACT_FORCE, CONTACT_TYPE, CONTACT_AREA, After creating the CONTACT, add both SURFACEs: master: Select 'sets' and add desired GROUP_MBs as set references to the MASTER_SURFACE. slave: Select 'sets' and add desired GROUP_FEs as set references to the SLAVE_SURFACE.
CONTACT.MB_FE
CONTACT.MB_MB
Selects groups of multibody surfaces to be used as master (planes, cylinders and ellipsoids) and slave (ellipsoids) in a contact calculation, and allows the user to specify contact detection parameters. Friction, contact damping and damping amplification can also be specified.
EVALUATION_TYPE , BOUNDARY_WIDTH , INITIAL_TYPE, FRIC_COEF, DAMP_COEF, DAMP_AMP_FUNC, DAMP_VEL_FUNC, SWITCH, CONTACT_FORCE, CONTACT_TYPE FRIC_FUNC,
After creating the CONTACT, add both SURFACEs: master: Select sets and add desired GROUP_MBs as set references to the MASTER_SURFACE. slave: Select sets and add desired GROUP_MBs as set references to the SLAVE_SURFACE. .
MARC
Supported Card
Solver Description
Notes
Body 3D Deformable Body 3D Rigid Contact Header
Altair Engineering

Contact Table
Nastran
Contact, thermal analysis definitions and non-structural mass are represented using group entities Supported Card Solver Description Supported Parameters BID, DIM, BEHAV, BSID, ISTYP, FRIC, IDSPL, CONTROL, 3D, DEFORM, NLOAD, ANGVEL, DCOS1, DCOS3, VELRB1, VELRB2, VELRB3 Notes
BCBODY
Defines a flexible or rigid contact body in 2D or 3D.
BCTABLE
Defines a contact table.
Use BCTABLE Manager tool to create BCTABLE, located in the utilities tab inside NASTRAN1 LIST OF ELEMENTS Defined using the interfaces panel
BSURF
Defines a contact body or surface defined by Element IDs. 3D Contact Region Definition by Solid Elements. Defines CHBDYE slave elements used for thermal conduction analysis. Defines CHBDYE slave elements used for thermal conduction analysis, and also allows for CONV continuation cards to be defined. Defines non-structural mass per unit length/area on properties or elements. Defines lumped non-structural mass on properties or
BSURFS
LIST OF ELEMENTS NX Nastran only. Defined using the interfaces panel Defined using the interfaces panel
CONDUCTION
CONVECTION
NSM1
Defined using the nsm panel
NSML1
Defined using the nsm panel

Altair Engineering
elements. PCONV Specifies the free convection boundary condition properties of a boundary condition surface element used for heat transfer analysis. Defined using the interfaces panel
PAM-CRASH 2G
Supported Card
Solver Description
Notes
CNTAC / Type 1 CNTAC / Type 10
Contact Interface Internal solid anticollapse contact
CNTAC / Type 13 CNTAC / Type 14 CNTAC / Type 15 CNTAC / Type 16 CNTAC / Type 17 CNTAC / Type 18 CNTAC / Type 19 CNTAC / Type 21 CNTAC / Type 33 Body to multiplane contact Symmetric node-to-segment contact with edge treatment Non-symmetric node-tosegment contact with edge treatment Self-impacting node-tosegment contact with edge
CNTAC / Type 34
CNTAC / Type 36
Altair Engineering

treatment CNTAC / Type 37 Enhanced self-impact contact for airbag Node-to-segment contact with smoothing for shock Edge-to-edge self-impacting contact Non-symmetric node-tosegment contact with edge treatment and zero contact thickness
CNTAC / Type 44
CNTAC / Type 46
CNTAC / Type 54
MASS_GES / NSMAS / SECFO_CONTACT / SECFO_PLANE Section definition for force output IFRA TITLE R Transmission forces are supported through the Interfaces panel. Slave nodes and master elements define the cross section. To define nonshell elements, create an entity set first. The master definition must be by sets. Non structural mass
SECFO_SECTION / SECFO_SUPPORT / SECFO_VOLFRAC / TIED /
Section definition for force output
Node-to-surface tied interface
PERMAS

Altair Engineering
The following cards are supported in the PERMAS interface: Supported Card Solver Description Supported Parameters NODE/SURFNODE TO NODE/ SURFNODE/ GROUND SURFACE TO NODE/ SURFNODE/ SURFACE/GROUND FRICTION OUTTOL (Surface contact) DISTOL (Surface contact) CONTSYS $MPC ISURFACE Coupling of two surfaces DPDOFS DOFTYPE = DISP DPITYP = (NODE/ SURFNODE) CELLPART DISTOL OUTTOL $MPC WLSSURFACE/ WLDSURFACE Weld connection between nodes and surfaces ISURFACE For more information on MPC cards and using duplicate ID pools, see the Permas Interface Overview topic. For more information on MPC cards and using duplicate ID pools, see the Permas Interface Overview topic. Notes
$CONTACT
Contact definitions
$PRETENSION PLANE
Pretension definition without detailing the threaded connection.
PLANE NODE TO NODE/ SURFNODE/ GROUND PLANE SURFACE TO NODE/ SURFNODE/ GROUND PLANE SURFNODE TO SURFNODE/ NODE/GROUND PREDIR={NORMAL/
Altair Engineering

system and axis/ vector} ORTDIR={JOIN/ FREE} GUIDING={AUTO/ CONTACT/ PRESCRIBE/ EXTERNAL/FREE} DISTOL OUTTOL $PRETENSION THREAD Modeling a threaded pretension section THREAD NODE TO NODE/SURFNODE/ GROUND THREAD SURFACE TO NODE/ SURFNODE/ GROUND THREAD SURFNODE TO SURFNODE/NODE/ GROUND {PREDIR/ SCREWDIR}= {system and axis/ vector} ALPHA RADIAL={JOIN/ FREE} PITCH CIRCUM={JOIN/ FREE} GUIDING DISTTOL OUTTOL Samcef The following cards are supported in the Samcef interface: Supported Card Solver Description Supported Parameters Notes

Altair Engineering
.MCT
Defines a flexible contact
For more information about the supported parameters see the topic Contact .MCT For more information about the supported parameters see the topic Contact .STI
.STI
Defines a glue contact
Altair Engineering

Load Steps
Load step entities are used to define and store load cases for a given analysis. Load steps are defined by selecting the associated load collectors and output blocks which define the load step. Load steps are shown under the Loadstep folder within the Model Browser. Some solver interfaces also support the Load Step Browser to create and edit load steps. Load steps have a display state, on or off, which controls the display state of load collectors associated with the load step in the graphics area. The display state of a load step can be controlled using the icon next to the load step entity in the Model Browser. Load steps also have an active and export state. The active state of a load step controls the display state of the load step and the listing of the load step in the Model Browser and any of its views. If a load step entity is active, then its display state is available to be turned on or off and it is listed in the Model Browser and any of its views. If a load step entity is inactive, then its display state is turned off permanently and it is not listed in the Model Browser or any of its views. The export state of a load step entity controls whether or not that load step is exported when the custom export option is utilized. The all export option is not affected by the export state of a load step. The active and export states of load step entities can be controlled using the Entity State Browser. The data names associated with load steps can be found in the data names section of the HyperMesh Reference Guide.

Altair Engineering
The following panels can be used to create and edit load steps: Load Steps
Solver Card Support for Load Steps

The Loadsteps panel generates entities called loadsteps. These loadsteps directly correspond to RADIOSS (Bulk Data Format) subcases. The Loadsteps panel allows load collectors to be explicitly defined as the referenced static load (LOAD), constraint (SPC), dynamic load (DLOAD), etc. for a subcase. Other RADIOSS (Bulk Data Format), OptiStruct input data is automatically generated or may be added to the subcase definition through the
Altair Engineering

edit function. The user can choose the analysis type for the subcase being defined. This will filter the data selectors displayed, so that only those appropriate for the selected analysis type (solution sequence) are displayed. There is also a generic option which will display all selectors. The following table describes how different RADIOSS (Bulk Data Format) Subcase information and I/O Option entries are generated on a subcase level: Supported Card Solver Description Supported Parameters Notes
ACCELERATION
Control acceleration results output on a subcase level.
Select a subcase (loadstep) and click edit. Check the box next to Output and then the one next to Acceleration. Select a subcase (loadstep) and click edit. Check the box next to ANALYSIS and then select an analysis type. Select a component mode synthesis method definition for use in a subcase. Check the box next to CMSMETH and select a load collector with a CMSMETH card image. Select a subcase (loadstep) and click edit. Check the box next to Output and then the one next to Cstrain. Select a subcase (loadstep) and click edit. Check the box next to Output and then the one next to Cstress. Part of the optimization problem setup, created in the Objectives panel.
ANALYSIS
Define a solution sequence for individual subcases.
CMSMETH
Defines the method, frequency upper limit, and number of modes to be used in component mode synthesis for flexibly-body preparation solution sequence.
CSTRAIN
Control ply strain results output for composites on a subcase level.
CSTRESS
Control ply stress results output for composites on a subcase level.
DESOBJ
Define a subcase specific objective.

Altair Engineering
DESSUB
Define a subcase specific design constraint.
Part of the optimization problem setup, created in the Dconstraints panel. Select a subcase (loadstep) and click edit. Check the box next to Output and then the one next to Displacement. Check the box next to DLOAD and select a load collector with dynamic loading information (DLOAD, RLOAD1, RLOAD2, TLOAD1, TLOAD2). Select a subcase (loadstep) and click edit. Check the box next to EIGVRETRIEVE, choose the number of integer values to be defined, and enter the integer values in the card previewer. Select a subcase (loadstep) and click edit. Check the box next to EIGVSAVE, and enter an integer value in the card previewer. Select a subcase (loadstep) and click edit. Check the box next to Output and then the one next to Elforce . Select a subcase (loadstep) and click edit. Check the box next to Output and then the one next to Ese. Select a subcase (loadstep) and click edit.
DISPLACEMENT
Control displacement results output on a subcase level.
DLOAD
Select dynamic loading information for a subcase.
EIGVRETRIEVE
Retrieve eigenvalue and eigenvector results from a normal modes analysis from an external data file.
EIGVSAVE
Output eigenvalue and eigenvector results from a normal modes analysis to an external data file.
ELFORCE
Control elemental force results output on a subcase level.
ESE
Control element strain energy results output on a subcase level.
EXCLUDE
Select a set of properties to be excluded from a linear
Altair Engineering

buckling analysis.
Check the box next to EXCLUDE, then select a SET definition from the card previewer. Check the box next to FATDEF and select a load collector with a FATDEF card image. Check the box next to FATPARM and select a load collector with a FATPARM card image. Check the box next to FATSEQ and select a load collector with a FATSEQ card image. Check the box next to FREQ and select a load collector containing frequency information (FREQ, FREQ1, FREQ2, FREQ3, FREQ4, FREQ5). Select a subcase (loadstep) and click edit. Check the box next to Output and then the one next to Gpforce . Select a subcase (loadstep) and click edit. Check the box next to Output and then the one next to Gpstress. Check the box next to IC and select a load collector with initial condition information (TIC). Check the box next to INVEL and select a load collector with initial velocity information
FATDEF
Select elements, and associated fatigue properties for fatigue analysis
FATPARM
Select parameters for fatigue analysis.
FATSEQ
Select loading sequence for fatigue analysis.
FREQUENCY
Select the set of forcing frequencies to be solved in a frequency response problem.
GPFORCE
Control grid point force results output on a subcase level.
GPSTRESS
Control grid point stress results output on a subcase level.
IC
Select initial conditions for a transient analysis subcase.
INVEL
Select multi-body dynamics initial velocity information for a subcase.

Altair Engineering
(INVELB). LABEL Provide a label for a subcase. Select a subcase (loadstep) and click edit. Check the box next to LABEL and enter a label in the card previewer. Check the box next to LOAD and select a load collector containing static loads (FORCE, MOMENT, PLOAD, PLOAD2, PLOAD4, LOAD), or inertial loading information (GRAV, RFORCE). Check the box next to MBSIM and select the load collector with an MBLIN, MBSEQ or MBSIM card image. Check the box next to METHOD(STRUCT) or METHOD(FLUID) and select a load collector with an EIGRL card image. Check the box next to MLOAD and select a load collector containing multibody dynamics loads (GRAV, MBFRC, MBFRCC, MBMNT, MBMNTC, MLOAD). Part of the optimization problem setup, created in the Responses panel.
LOAD
Select static loading information for a subcase.
MBSIM
Select a multi-body dynamics simulation definition for a subcase.
METHOD
Select eigenvalue extraction information for a subcase.
MLOAD
Select multi-body dynamics loading information for a subcase.
MODEWEIGHT
Define a multiplier for computed eigenvalues that are to be used in the calculation of the "weighted reciprocal eigenvalue" and "combined compliance index" optimization responses. Select multi-body dynamics motion information for a subcase.
MOTION
Check the box next to MOTION and select a load collector containing multi-
Altair Engineering

body dynamics motions (MOTION, MOTNG, MOTNGC). MPC Select multi-point constraints for use in a subcase. Check the box next to MPC and select a load collector containing MPCs. Select a subcase (loadstep) and click edit. Check the box next to Output and then the one next to Mpcforce . Check the box next to NLPARM and select a load collector with an NLPARM card image. Check the box nex to NSM and select a group with a NSM1 or NSML1 card image or select a load collector with a NSMADD card image. This option is not allowed in the subcase. Select a subcase (loadstep) and click edit. Check the box next to Output and then the one next to Ofrequency. Select a subcase (loadstep) and click edit. Check the box next to Output and then the one next to Oload. Select a subcase (loadstep) and click edit. Check the box next to Output and then the one next to Omodes. Select a subcase (loadstep) and click edit.
MPCFORCE
Control MPC force results output on a subcase level.
NLPARM
Select non-linear static analysis settings for use in a subcase.
NSM
Select non-structural mass input for entire model.
OFREQUENCY
Define a set of frequencies for output requests for a subcase.
OLOAD
Request the output of applied loads for a subcase.
OMODES
Define a set of modes for output requests for a normal modes or linear buckling subcase.
RESVEC
Control the calculation of modal acceleration vectors.

Altair Engineering
Check the box next to RESVEC and choose the desired TYPE and OPTION in the card previewer. RSPEC Select response spectra information for use in a subcase. Check the box next to RSPEC and select a load collector containing response spectra analysis information (RSPEC). Check the box next to RWALL or RWLADD and select a group (RWALL) or a load collector (RWALADD). Check the box next to SDAMPING and select a load collector containing damping information (TABDMP1). Select a linear static subcase (loadstep) and click edit. Check the box next to SOLVTYP and then choose a load collector with the SOLVTYP card image. Check the box next to SPC and select a load collector containing SPCs. Select a subcase (loadstep) and click edit. Check the box next to Output and then the one next to Spcf. Check the box next to STATSUB and select a static subcase. Select a subcase (loadstep) and click edit.
RWALL
Defines a rigid wall of the following types: Infinite Plane, Infinite Cylinder, Sphere and Parallelogram.
SDAMPING
Select damping information for use in a subcase.
SOLVTYP
Select the iterative solver.
SPC
Select single-point constraints for use in a subcase. Control SPC force results output on a subcase level.
SPCFORCES
STATSUB
Select a linear static subcase for linear buckling analysis.
STRAIN
Control strain results output on a subcase level.
Altair Engineering

Check the box next to Output and then the one next to Strain. STRESS Control stress results output on a subcase level. Select a subcase (loadstep) and click edit. Check the box next to Output and then the one next to Stress. Created automatically, when a new subcase is created. The subcase ID matches the ID of the HyperMesh loadstep entity. Select a subcase (loadstep) and click edit. Check the box next to SUBTITLE and enter a subtitle in the card previewer. Check the box next to SUPORT1 and select a load collector containing SUPORT1 loads. Check the box next to TEMP and select a load collector containing TEMP loads or a load collector with the TEMPD card image. Check the box next to TSTEP and select a load collector with the TSTEP card image. Set the toggle to either TIME or FOURIER, depending on the type of transient solution desired. Check the box next to TTERM and input a real value for the termination
SUBCASE
Define a subcase.
SUBTITLE
Provide a subtitle for a loadstep.
SUPORT1
Select fictitious supports for use in a subcase.
TEMP
Select thermal loading information for a subcase.
TSTEP
Select integration and time step information for a transient analysis subcase.
TTERM
Define the termination time of a geometric non-linear subcase

Altair Engineering
time. VELOCITY Control velocity results output on a subcase level. Select a subcase (loadstep) and click edit. Check the box next to Output and then the one next to Velocity. Part of the optimization problem setup, created in the Responses panel.
WEIGHT
Define a weighting factor (multiplier) for the compliance of a linear static or inertia relief subcase, which is used in the calculation of the "weighted compliance" and "combined compliance index" optimization responses. Select time history output for geometric non-linear analysis
XHIST
Check the box next to XHIST or XHISADD and select a group (XHIST) or a load collector (XHISADD).
Abaqus
A load step corresponds to a *STEP definition in Abaqus model history. Load collectors, output blocks and groups within a load step are exported under the corresponding *STEP block in the Abaqus input deck. It is recommended that all history (*STEP) data be defined from the Step Manager in the Abaqus user profile. Supported Card Solver Description Supported Parameters EIGENSOLVER = (SUBSPACE/ LANCZOS) b1, b2 Notes
*BUCKLE
Obtain eigenvalue buckling estimates
Defined in the load step card image
*BULK VISCOSITY
Modify bulk viscosity parameters Dynamic stress/displacement analysis
Explicit template only. History data. Defined in the load step card image.
*DYNAMIC (Explicit)
EXPLICIT SCALE FACTOR ADIABATIC FIXED TIME INCREMENTATION
Altair Engineering

DIRECT USER CONTROL ELEMENT BY ELEMENT IMPROVED DT METHOD = YES or NO *DYNAMIC (Standard) Dynamic stress/displacement analysis HAFTOL DIRECT DIRECT=NO STOP, SUBSPACE, ADIABATIC, ALPHA, INITIAL, NOHAF Specify format for results file output and invoke zeroincrement results file output Extract natural frequencies and modal vectors ASCII BINARY ZERO INCREMENT PROPERTY EVALUATION EIGENSOLVER = SUBSPACE, LANCZOS, AMS NORMALIZATION = MASS, DISPLACEMENT RESIDUAL MODES ACOUSTIC COUPLING NUMBER INTERVAL BIAS USER BOUNDARIES *HEAT TRANSFER Transient or steady-state uncoupled heat transfer analysis DELTMX END = PERIOD or SS, STEADY STATE, MXDEM Defined in the load step card image. Defined in the load step card image. Defined in the load step card image. Defined in the load step card image.
*FILE FORMAT
*FREQUENCY
*LOAD CASE
Begin a load case definition for NAME Defined in the load step multiple load case analysis card image. Number_of_LoadCas e

Altair Engineering
LoadCase_maximum _data_ lines *MODAL DYNAMIC Dynamic time history analysis using modal superposition *MONITOR Define a degree of freedom to monitor CONTINUE = YES or NO DOF NODE FREQUENCY *PRINT Request or suppress output to the message file in an Abaqus/ Standard analysis or to the status file in an Abaqus/ Explicit analysis CONTACT MODEL CHANGE FREQUENCY PLASTICITY RESIDUAL SOLVE ALLKE CRITICAL ELEMENT DMASS ETOTAL *RESTART Save and reuse data and analysis results WRITE FREQUENCY OVERLAY NUMBER INTERVAL TIME MARKS *STATIC Static stress/displacement analysis ADIABATIC ALLSDTOL CONTINUE DIRECT DIRECT=NO STOP, FACTOR, LONG TERM FULLY PLASTIC RIKS STABILIZE *STEADY STATE DYNAMICS Steady-state dynamic response based on harmonic DAMPING CHANGE Defined in the load step card image. DIRECT Defined in the load step card image. Defined in the load step card image. Defined in the load step card image. Defined in the load step card image. Defined in the load step card image.
Altair Engineering

excitation
FREQUENCY SCALE INTERVAL REAL ONLY STIFFNESS CHANGE SUBSPACE PROJECTION = {ALL FREQUENCIES, CONSTANT, EIGENFREQUENCY , PROPERTY CHANGE, RANGE}
*STEP
Begin a step
CONVERT SDI INCREMENT NAME NLGEOM PERTURBATION UNSYMMETRIC AMPLITUDE=STEP, RAMP EXTRAPOLATION =LINEAR, PARABOLIC, NO
Parameters are defined in the load step card image.
*VISCO
Transient, static, stress/ displacement analysis with time-dependent material response (creep, swelling, and viscoelasticity)
CETOL CREEP FACTOR STABILIZE
Defined in the load step card image.
Note:
Only load collectors with the HISTORY card image should be added to a load step. Load collectors with INITIAL_CONDITION card images need not be added to any load steps. They will be ignored, if added.
ANSYS
Supported Card
Solver Description
Supported
Notes

Altair Engineering
Parameters ACEL Specifies the linear acceleration of the structure. Specifies the translational acceleration of an element component. ACELX, ACELY, ACELZ CM_NAME, CMACEL_X, CMACEL_Y, CMACEL_Z CM_NAME, DOMEGAX, DOMEGAY, DOMEGAZ, X1, Y1, Z1, X2, Y2, Z2 CM_NAME, DOMEGAX, DOMEGAZ, X1, Y1, Z1, X2, Y2, Z2, KSPIN LSMIN, LSMAX, LSINC
CMACEL
CMDOMEGA
Specifies the rotational acceleration of an element component about a userdefined rotational axis.
CMOMEGA
Specifies the rotational velocity of an element component about a userdefined rotational axis.
LSSOLVE
Reads and solves multiple load steps.
Marc
Supported Card
Solver Description
Notes
FOUNDATION INITIAL_vel Init_Disp Fixed_Acce Fixed_Pres
Nastran
The Loadsteps panel is available when the Nastran user profile is loaded. It is used to generate Nastran subcase definitions. The panel creates loadstep entities. These loadstep entities directly correspond to
Altair Engineering

Nastran subcase definitions. The Loadsteps panel allows load collectors to be explicitly defined as the referenced constraint (SPC), static load (LOAD), multi-point constraint (MPC), fictitious support (SUPORT1), non-linear parameters (NLPARM), eigenvalue extraction data (METHOD), frequency range (FREQ), damping (SDAMPING), dynamic load (DLOAD), thermal loading (TEMP), etc. for a subcase. Other input data is automatically generated (the SUBCASE header) or may be added to the subcase definition through the edit function. It is recommended to set up a subcase using the Loadstep Browser. Supported Card Solver Description Supported Parameters LABEL, ANALYSIS, IC, BCONTACT, TRIM, OUTPUT Notes
SUBCASE
PERMAS
The following cards are supported in the PERMAS interface: Supported Card Solver Description Supported Parameters NAME Notes
$CONSTRAINTS
Constraint variant bracket header line
Create a loadstep and open its card image. Set the Analysis Procedure to CONSTRAINTS. The AnalysisProcedure toggle must be set to LOADING in the card image.
$FREQLOAD
Definition of frequency dependent dynamic loads for use in frequency response analysis. Loading variant bracket header line Define a nonlinear static load history.
DOFTYPE
$LOADING
NAME
$NLLOAD
TABLE TIME={LIST/Time and increment} EXTRA=CONST DOFTYPE=DISP
The AnalysisProcedure toggle must be set to LOADING in the card image. To visualize the nonlinear load history curves you can use the Plot NLLOAD tool from the utility page.

Altair Engineering
$SITUATION
Situation definition header line NAME
Open the loadstep and set the AnalysisProcedure to SITUATION The TRANSLOAD card and FREQLOAD cards are mutually exclusive.
$TRANSLOAD
Definition of time dependent dynamic loads for use in transient response analysis.
AMPLITUDE BOUNDS DELAY DOFTYPE FUNCTION PHASE
See also Browsers HyperMesh Entities & Solver Interfaces Include Files Element Property and Material Assignment Rules Model Setup
Altair Engineering

Materials
Material entities are used to define and store material definitions for a model. Materials are created, edited, deleted, and shown under the Material folder within the Model Browser. Materials also have a material view within the Model Browser which lists only materials and has advanced options for materials creation and modification. Materials do not have a display state, but they do have a "by material" visualization color mode which colors the model according to the colors assigned to each material based on element material relationships. The "by material" visualization color mode is automatically set when you enter the material view within the Model Browser. In addition, you can manually set the "by material" visualization color mode using the element color mode icon on the visualization toolbar. Element material relationships are user profile (solver interface) dependent and are described in the section Element Property and Material Assignment Rules. In general, when a component is assigned a material, that material assignment is applied to all elements collected by that component. The method of assigning materials at the component level is therefore referred to as indirect material assignment. Direct material assignment is performed directly on the elements themselves, typically via a property assignment. Direct material assignments always take precedence over indirect property and material assignments.
Materials have an active and export state. The active state of a material controls the listing of the material in the Model Browser and any of its views. If a material entity is active, then it is listed in the Model Browser and any of its views. If a material entity is inactive, then it is not listed in the Model Browser or any of its views. The export state of a material entity controls whether or not that material is exported when the custom export option is utilized. The all export option is not affected by the export state of a material. The active and export states of material entities can be controlled using the Entity State Browser. The data names associated with materials can be found in the data names section of the HyperMesh Reference Guide.

Altair Engineering
Solver Card Support for Materials

RADIOSS (Block Format) has many materials, and most of them are supported. In addition RADIOSS allows you to program your own materials that can be used in a simulation. In order to handle the unsupported RADIOSS materials and user defined RADIOSS material, a separate card image called "MAT_UNSUPPORTED" has been introduced. Any unsupported material will be read with card image MAT_UNSUPPORTED with its ID and associtivity with component preserved. You can also create the material as well. In this card image, all material suboptions, parameters, and data lines are supported as simple text. HyperMesh does not check the validity or syntax of any data in this mode. You must manually check the validity of the data. No editing, updating, or review of the material data is intended. Also time step calculation and mass calculation are
Altair Engineering

not available for the component that refers to this material. The material is displayed in Model Browser, Solver Browser, Material table and Component table. The supported RADIOSS D00 cards in RADIOSS (Block Format) 5.1 and 9.0 are listed below. You can quickly create these cards by right-clicking in the Solver Browser and selecting Create Cards. Supported Card Solver Description Supported Parameters Notes
ALE/MAT /MAT /MAT/B-K-EPS /MAT/BARLAT3 /MAT/BIMAT /MAT/BIPHAS /MAT/BOLTZMAN /MAT/BOUND /MAT/CHANG /MAT/COMPSH /MAT/COMPSO /MAT/CONC /MAT/CONNECT /MAT/COSSER /MAT/COWPER /MAT/DAMA /MAT/DPRAG MAT/DPRAG1 /MAT/ELAST
Describes the ALE material. LAW11 LAW57 LAW20
LAW37 LAW34 LAW11 LAW15 LAW25 LAW14 LAW24 LAW59 LAW68 LAW44 LAW22 LAW21 LAW10 LAW1, LAW01

Altair Engineering
/MAT/ELASTOMER LAW65 /MAT/FABR_A /MAT/FABRI /MAT/FOAM_PLAS /MAT/FOAM_TAB /MAT/FOAM_VISC /MAT/GAS /MAT/GRAY /MAT/GURSON /MAT/HANSEL /MAT/HILL /MAT/HILL_MMC /MAT/HILL_TAB /MAT/ HONEYCOMB /MAT/HYD_JCOOK /MAT/HYD_VISC /MAT/HYDPLA /MAT/HYDRO /MAT/JWL /MAT/K-EPS /MAT/KELVINMAX /MAT/LAW05 LAW16 LAW52 LAW63 LAW32 LAW72 LAW43 LAW28 LAW58 LAW19 LAW33 LAW70 LAW35
LAW4 LAW6 LAW3 LAW6 LAW5 LAW6 LAW40 LAW5
Altair Engineering

/MAT/LAW10 /MAT/LAW23 /MAT/LAW50 /MAT/LAW51 /MAT/LAW53 /MAT/LAW54 /MAT/LAW62 /MAT/LAW63 /MAT/LAW65 /MAT/LAW66 /MAT/LAW82 /MAT/LEE_T /MAT/LES_FLUID /MAT/OGDEN /MAT/PLAS_BRIT /MAT/PLAS_DAMA /MAT/ PLAS_JOHNS /MAT/PLAS_TAB /MAT/PLAS_T3 /MAT/PLAS_ZERIL /MAT/RIGID /MAT/SAMP LAW13 LAW76 LAW66 LAW82 LAW41 LAW46 LAW42 LAW27 LAW23 LAW2
LAW36 LAW60

Altair Engineering
/MAT/STEINB /MAT/THERM /MAT/TSAI_TAB /MAT/UGINE_ALZ /MAT/USERij /MAT/VISC_TAB /MAT/VOID /MAT/ZERIL /MAT/ZHAO /VISC_PRONY
LAW49 LAW18 LAW53 LAW64
LAW38 LAW0
LAW48 Prony series input for Visco elastic plastic piesewise linear material MAT/LAW66
The material data cards for RADIOSS (Bulk Data Format) can be created by loading and editing the appropriate card images for materials. These card images have the same name as the corresponding cards. Supported Card Solver Description Supported Parameters Notes
MAT1
Defines the material properties MATS1 for linear, temperatureMATT1 independent, isotropic MAT4 materials. MAT5 MATFAT MATX02, MATX27, MATX36, MATX44, MATX65, MATX82 MATX13, MATX33, MATX42, MATX62, MATX70,
Altair Engineering

MAT2
Defines the material properties for linear, temperatureindependent, anisotropic materials for two-dimensional elements. Defines constant thermal material properties for conductivity, heat capacity, density, and heat generation. Supported as MAT4 material and as an optional card on the structural material definitions. Supported as MAT5 material and as an optional card on the structural material definitions.
MAT4
MAT5
Defines the thermal material properties for anisotropic materials.
MAT8
Defines the material property for an orthotropic material for two-dimensional elements. Defines the material properties for linear, temperatureindependent, anisotropic materials for solid elements. Defines material properties for fluid elements in coupled fluidstructural analysis. Defines material properties for fatigue analysis. Supported as an optional card on the structural material definitions. Supported as an extension to the MAT1 material.
Exported in large field format by optistructlf template. Exported in large field format by optistructlf template.
MAT9
MAT10
Exported in large field format by optistructlf template. Exported in large field format by optistructlf template.
MATFAT
MATT1
Specifies temperaturedependent material properties on MAT1 entry fields via TABLEMi entries. Specifies temperaturedependent material properties on MAT2 entry fields via TABLEMj entries. Specifies temperature-
MATT2
Supported as an extension to the MAT2 material.
MATT8
Supported as an

Altair Engineering
dependent material properties on MAT8 entry fields via TABLEMi entries. MATT9 Specifies temperaturedependent material properties on MAT9 entry fields via TABLEMk entries.
extension to the MAT8 material.
Supported as an extension to the MAT9 material.
Abaqus
Three material keywords are supported - *MATERIAL, *GASKET MATERIAL, *CONNECTOR BEHAVIOUR in the corresponding card images. They are: ABAQUS_MATERIAL, GASKET_MATERIAL and CONNECTOR_BEHAVIOR, respectively. Because Abaqus has a large selection of material types, many of which are not supported, a separate mode of material creation is included called "Generic Material". This model of created is supported through the GENERIC_MATERIAL card image. In this mode, all material sub-options, parameters, and data lines are supported as simple text. The validity or syntax of any data is not checked in this mode. You must manually check the validity of the data. This method is most helpful when the material models are already defined and they are imported for the purpose of adding them to the corresponding sectional properties. No editing, updating, or review of the material data is intended. You can import a model in the generic material mode by using the Solver Options dialog in the Import tab. You can also add an **HM_GENERIC_MATERIAL comment before a material card to have it imported as a generic material. Also see the Unsupported Data Blocks topic to learn more about how the Abaqus interface handles unsupported data. Supported Card Solver Description Supported Parameters NStress, NStrain, NLStrain Notes
*BIAXIAL TEST DATA
Used to provide biaxial test data (compression and/or tension). Specify simultaneously the normalized shear and bulk compliance or relaxation moduli as functions of time.
*COMBINED TEST DATA
SHRINF VOLINF
This option can be used only in conjunction with the *VISCOELASTIC option and cannot be used if the *SHEAR TEST DATA and *VOLUMETRIC TEST DATA options are used.
Altair Engineering

*CONDUCTIVITY
Specify thermal conductivity
DEPENDENCIES, This card is a sub-option TYPE=ISO, ORTHO, in the ANISO ABAQUS_MATERIAL card image. NAME, INTEGRATION N/A This card is a sub-option in the CONNECTOR_BEHAVIOR card image. This card is a sub-option in the CONNECTOR_BEHAVIOR card image. This card is a sub-option in the CONNECTOR_BEHAVIOR card image.
*CONNECTOR BEHAVIOR *CONNECTOR CONSTITUTIVE REFERENCE
Begin the specification of a connector behavior Define reference lengths and angles to be used in specifying connector constitutive behavior Define the damping behavior for connector elements.
*CONNECTOR CONTACT FORCE
INDEPENDENT COMPONENT, DEPENDENCIES
*CONNECTOR DAMPING
Define connector damping behavior
COMPONENT, COUPLED, DEPENDENCIES, NONLINEAR, INDEPENDENT COMPONENTS COMPONENT, COUPLED, DEPENDENCIES, NONLINEAR, MOTION DEPENDENCIES COMPONENT, RELEASE
*CONNECTOR ELASTICITY
Define connector elastic behavior
This card is a sub-option in the CONNECTOR_BEHAVIOR card image.
*CONNECTOR FAILURE
Define a failure criterion for connector elements
Only in Explicit template This card is a sub-option in the CONNECTOR_BEHAVIOR card image.
*CONNECTOR Define friction forces and FRICTION moments in connector (Abaqus 6.4 version) elements
INTERACTION COMPONENT INDEPENDENT COMPONENT DEPENDENCIES STICK STIFFNESS
This card is a sub-option in the CONNECTOR_BEHAVIOR card image.
*CONNECTOR
Define friction forces and
PREDEFINED
This card is a sub-option

Altair Engineering
FRICTION (Abaqus 6.5 or later version)
moments in connector elements
COMPONENT INDEPENDENT COMPONENT DEPENDENCIES STICK STIFFNESS CONTACT FORCE
in the CONNECTOR_BEHAVIOR card image. This needs a *FRICTION card, which can be created as a property using the FRICTION card image. This card is a sub-option in the CONNECTOR_BEHAVIOR card image. This card is a sub-option in the CONNECTOR_BEHAVIOR card image. This card is a sub-option in both the ABAQUS_MATERIAL and *GASKET MATERIAL card images. Not in Explicit template.
*CONNECTOR LOCK
Define a locking criterion for connector elements
COMPONENT LOCK
*CONNECTOR STOP
Specify connector stops for connector elements
COMPONENT
*CREEP
Define a creep law
DEPENDENCIES LAW=STRAIN, TIME, HYPERB, USER
*CRUSHABLE FOAM
Specify the crushable foam plasticity model
HARDENING = {VOLUMETRIC, ISOTROPIC} DEPENDENCIES
This card is a sub-option in the ABAQUS_MATERIAL card image. This card is a sub-option in the ABAQUS_MATERIAL card image. This card is a sub-option in the ABAQUS_MATERIAL card image.
*CRUSHABLE Specify hardening for the FOAM HARDENING crushable foam plasticity model
DEPENDENCIES
*DAMPING
Specify material damping
ALPHA BETA COMPOSITE STRUCTURAL
*DENSITY
Specify material mass density
DEPENDENCIES
This card is a sub-option in the ABAQUS_MATERIAL card image.
Altair Engineering

*DIELECTRIC
Specify dielectric material properties
TYPE=ISO, ORTHO, This card is a sub-option ANISO in the ABAQUS_MATERIAL card image. DEPENDENCIES MODULI TYPE=ISOTROPIC, LAMINA, ENGINEERING CONSTANTS, ORTHOTROPIC, ANISOTROPIC This card is a sub-option in the ABAQUS_MATERIAL card image.
*ELASTIC
Specify elastic material properties
*EXPANSION
Specify thermal expansion
ZERO DEPENDENCIES PORE FLUID USER TYPE=ISO, ORTHO, ANISO, SHORT FIBER
This card is a sub-option in both the ABAQUS_MATERIAL and *GASKET MATERIAL card images.
*FLUID BEHAVIOR
Define fluid behavior for a fluid NAME cavity Begin the specification of a gasket behavior Specify a gasket contact area or contact width for average pressure output NAME Only in Standard template.
*GASKET BEHAVIOR *GASKET CONTACT AREA
DEPENDENCIES
This card is a sub-option in the *GASKET_MATERIAL card image. This card is a sub-option in the *GASKET BEHAVIOR card image.
*GASKET ELASTICITY
Specify elastic properties for DEPENDENCIES the membrane and transverse COMPONENT= shear behaviors of a gasket MEMBRANE, TRANSVERSE SHEAR VARIABLE=STRES S, FORCE
*GASKET THICKNESS BEHAVIOR
Specify a gasket thicknessdirection behavior
DEPENDENCIES TENSILE STIFFNESS FACTOR
This card is a sub-option in the *GASKET_MATERIAL card image.

Altair Engineering
SLOPE DROP YIELD ONSET DIRECTION=LOADI NG, UNLOADING VARIABLE=STRES S, FORCE TYPE=ELASTICPLASTIC, DAMAGE *HYPERELASTIC Specify elastic properties for approximately incompressible elastomers ARRUDA-BOYCE BETA MARLOW MODULI MOONEY-RIVLIN N NEO HOOKE OGDEN POLYNOMIAL POISSON PROPERTIES REDUCED POLYNOMIAL TEST DATA INPUT USER VAN DER WAALS YEOH *HYPERFOAM Specify elastic properties for a hyperelastic foam MODULI N POISSON TEST DATA INPUT Sub-options supported: *BIAXIAL TEST DATA *PLANAR TEST DATA *SIMPLE SHEAR TEST DATA *UNIAXIAL TEST DATA *VOLUMETRIC TEST DATA This card is a sub-option in the ABAQUS_MATERIAL card image. Sub-options supported: *BIAXIAL TEST DATA *PLANAR TEST DATA *UNIAXIAL TEST DATA *VOLUMETRIC TEST DATA This card is a sub-option in the ABAQUS_MATERIAL card image.
Altair Engineering

*MATERIAL
Begin the definition of a material
NAME RTOL SRATE FACTOR
*MULLINS EFFECT
Specify Mullins effect material parameters for elastomers
BETA DEPENDENCIES M PROPERTIES R TEST DATA INPUT USER
This card is a sub-option in the ABAQUS_MATERIAL card image. Sub-options supported: *BIAXIAL TEST DATA *PLANAR TEST DATA *UNIAXIAL TEST DATA
*PIEZOELECTRIC
Specify piezoelectric material TYPE=S, E properties
This card is a sub-option in the ABAQUS_MATERIAL card image. Not in Explicit template.
*PLANAR TEST DATA
Used to provide planar test (or pure shear) data (compression and/or tension).
N_Stress
Used to provide planar test (or pure shear) data N_Strain (compression and/or FOAMPLANARTEST tension). DATACARDS This option is used to provide planar test (or pure shear) data. It can be used only in conjunction with the *HYPERELASTIC option, the *HYPERFOAM option, and the *MULLINS EFFECT option. This type of test does not define the hyperelastic material constants fully; at the least, uniaxial or biaxial test data should also be given.
*PLASTIC
Specify a metal plasticity model
DATA TYPE HARDENING=ISOTR OPIC, KINEMATIC, COMBINED, JOHNSON COOK NUMBER

Altair Engineering
BACKSTRESSES RATE *RATE DEPENDENT Define a rate-dependent viscoplastic model TYPE= {POWER LAW, JOHNSON COOK, YIELD RATIO} DEPENDENCIES *SHEAR FAILURE Specify a shear failure model and criterion TYPE= {TABULAR, JOHNSON COOK} ELEMENT DELETION = {YES, NO} DEPENDENCIES *SHEAR TEST DATA Used to provide shear test data ShearComp Time Shrinf *SIMPLE SHEAR TEST DATA Used to provide simple shear ShearStress test data ShearStrain TransverseStress This option can be used only in conjunction with the *VISCOELASTIC option. This option is used to provide simple shear test data. It can be used only in conjunction with the *HYPERFOAM option. This card is a sub-option in the ABAQUS_MATERIAL card image. This option is used to provide uniaxial test data. It can be used only in conjunction with the *HYPERELASTIC option, the *HYPERFOAM option, and the *MULLINS EFFECT option. This card is a sub-option in the ABAQUS_MATERIAL card image. This card is a sub-option in the ABAQUS_MATERIAL card image in the Explicit template. This card is a sub-option in the ABAQUS_MATERIAL card image.
*SPECIFIC HEAT
Define specific heat
DEPENDENCIES
*UNIXIAL TEST DATA
Used to provide uniaxial test data (compression and/or tension).
Nstress Nstrain Nlstrain
*USER MATERIAL
Define material constants for use in subroutine UMAT, UMATHT, or VUMAT
CONSTANTS TYPE= {MECHANICAL, THERMAL} UNSYMM
Altair Engineering

*USER OUTPUT VARIABLES
Specify number of user variables
Value
This card is a sub-option in both the ABAQUS_MATERIAL and *GASKET MATERIAL card images. This card is a sub-option in the ABAQUS_MATERIAL card image. Sub-options supported: *COMBINED TEST DATA *SHEAR TEST DATA *VOLUMETRIC TEST DATA For the sub-options, the parameters SHRINF and VOLINF are supported.
*VISCOELASTIC
Specify dissipative behavior for use with elasticity
ERRTOL NMAX FREQUENCY=FOR MULA, TABULAR TIME= CREEP TEST DATA, RELAXATION TEST DATA, PRONY
*VOLUMETRIC TEST DATA
Provide volumetric test data.
Pressure VolumeRatio
A User Comments block is supported for all materials. See the information below on how to add comments to any material card image. These comments are preserved during import and export of the Abaqus input deck. See also Unsupported Data Blocks
Actran
The following material data blocks are supported in Actran: Supported Card Solver Description Supported Parameters X_STIFFNESS Y_STIFFNESS Z_STIFFNESS Notes
DISCRETE

Altair Engineering
X_MASS Y_MASS Z_MASS STIFFNESS normal and transveral MASS normal and transversal FLUID SOUND SPEED (+ J) FLUID DENSITY CP CV REFERENCE TEMPERATURE FLUID_BULK_MOD ULUS REFERENCE_FLO W POROUS YOUNG_MODULUS (+ j) POISSON_RATIO SOLID_DENSITY FLUID_DENSITY VISCOSITY THERMAL CONDUCTIVITY POROSITY CP CV FLOW_RESISTIVITY BULK_MODULUS BLOT_FACTOR TORTUOSITY Allard & Johnson model POROUS_UP
Altair Engineering

RIGID_POROUS SHELL SOLID STIFFENER ELONGATION_MOD ULUS (+ j) FLEXION_MODULU S (+ j) FLEXION_OFFSET SHEAR_MODULUS (+ j) TRANSLATION_DEN SITY (+ j) ROTATION_DENSIT Y (+ j) ROTATION_OFFSET VISCO_ELASTIC Young modulus (+ j) POISSON_RATIO SOLID_DENSITY VISCOTHERMAL FLUID SOUND_SPEED (+ j) FLUID_DENSITY VISCOSITY THERMAL_CONDU CTIVITY CP CV
ANSYS
The input translator recognizes the ANSYS cards listed below. If an unsupported field in a card is found, a message is displayed on the status bar. The messages are also printed to the file ansys.msg. General slash commands, SOLUTION commands, POST1 commands, and POST26 commands are referred to as control cards. Unrecognized cards are written to a *.hmx file.

Altair Engineering
Supported Card
Solver Description
Supported Parameters mat
Notes
MAT
Sets the element material attribute pointer. Defines a linear material property as a constant or a function of temperature. Defines property data to be associated with the temperature table. Defines property data to be associated with the temperature table. Defines a temperature table for material properties.
MP
Lab, MAT, C0, C1, C2, C3, C4
MPDATA
Lab, MAT, STLOC, C1, C2, C3, C4, C5, C6 R5.0, LENGTH, Lab, MAT, STLOC, VAL1, VAL2, VAL3 STLOC, T1, T2, T3, T4, T5, T6 FLAGS: DENS, EX, NUXY, ALPX, CTEX, CTEY, CTEZ, THSX, TSHY, TSHZ, REFT, KXXX, EY, EZ, NUYZ, NUXZ, PRXY, PRYZ, PRXZ, GXY, GYZ, GXZ, ALPY, ALPZ, DAMP, DMPR, C, ENTH, KYY, KZZ, HF, EMIS, QRATE, VISC, SONC, RSVX, RXVY, RXVZ, PERX, PERY, PERZ, MURX, MURY, MURZ, MGXX, MGYY, MGZZ, LSST, SBKX, SBKY, SBKZ, LSSM Supports temperature tables for each material attribute
MPDATA
MPTEMP
MPTEMP
R5.0, LENGTH, STLOC, TEMP1, TEMP2, TEMP3 Activates a data table for nonlinear material properties TB_LAB, ID, NTEMP, NPTS,
Supports temperature tables for each material attribute
TB
Altair Engineering

or special element input. TBDATA Defines data for the data table.
TBOPT, EOSOPT STLOC, C2(i)
LS-DYNA
LS- DYNA has many materials and most of them are supported. In addition, LS-DYNA allows users to program their own materials that can be used in a simulation. In order to handle the unsupported LS-DYNA materials and user defined LS-DYNA material, a separate card image called "MAT_UNSUPPORTED" is available. Any unsupported material will be read with the card image MAT_UNSUPPORTED, and its ID and associtivity with components is preserved. You can also create the material as well. In this card image, all material sub-options, parameters, and data lines are supported as simple text. The validity or syntax of any data is not checked in this mode. You must manually check the validity of the data. No editing, updating, or review of the material data is intended. Also, time step calculation and mass calculation are not available for the component that refers to this material. The material is displayed in Model Browser, Solver Browser, Material Table and Component Table . Supported Card Solver Description Supported Parameters RO, C, BETA, CF, ATMOS, GRAV, XP, YP, ZP, XN, YN, ZN Title Notes
*MAT_ACOUSTIC
Appropriate for tracking low pressure stress waves in an acoustic media such as air or water and can be used only with the acoustic pressure element formulation.
Material Type 90
*MAT_ANISOTROPI Valid for modeling the elastic- Rho, C11, C12, C_ orthotropic behavior of solids, C13, C23, C33, C24, C34, C44, ELASTIC shells and thick shells. C25, C35, C45, C16, C26, C36, C56, C66 Title
C22, Material Type 2 C14, C15, C55, C46,
Anisotropy axis definition (0.0, 1.0, 2.0, 3.0, 4.0, by system) *MAT_ANISOTROPI Valid for modeling the elastic- RO, SIGY, LCSS, C_ orthotropic behavior of solids, QR1, CR1, QR2, CR2, C11-C16, C22ELASTIC_PLASTIC shells and thick shells and Material Type 157

Altair Engineering
solid elements.
C26, C46, R00, S22, Title
C33-C36, C44C55,C56, C66, R45, R90, S11, S33, S12
Anisotropy axis definition (0.0, 1.0, 2.0, 3.0, 4.0, by system) *MAT_ANISOTROPI Simplified version of the C_ Material Type 103. Applies PLASTIC only to shell elements. RO, E, PR, SIGY, Material Type 103P LCSS, QR1, CR1, QR2, CR2, R00, R45, R90, S11, S22, S33, S12 Title Anisotropy axis definition (0.0, 1.0, 2.0, 3.0, 4.0, by system) *MAT_ANISOTROPI Applies to shell and brick C_ elements. VISCOPLASTIC RO, E, PR, SIGY, Material Type 103 FLAG, LCSS, ALPHA, QR1, CR1, QR2, CR2, QX1, CX1, QX2, CX2, VK, VM, ROO, R45, R90, L, M, N, AOPT, FAIL, NUMINT Title *MAT_ARRUDA_BO Provides a hyperelastic rubber Rho, K, G, N, LCID, Material Type 127 YCE_ model combined optionally TRAMP, NT, RUBBER with linear viscoelasticity. ArrayCount, GI, beta Title *MAT_ARUP_ADHE Used for adhesive bonding in SIVE aluminum structures. RO, E, PR, TENMAX, GCTEN, SHRMAX, GCSHR, PWRT, PWRS, SHRP, SHT_SL, EDOT0, EDOT2 Title Material Type 169
Altair Engineering

*MAT_BAMMAN
Allows the modeling of temperature and rate dependent plasticity with a fairly complex model that has many input parameters. Extension of model 51 which includes the modeling of damage.
Rho, E, PR, T, HC, C1 - C18, A1-A6, KAPPA, Title
Material Type 51
*MAT_BAMMAN_D AMAGE
Rho, E, PR, T, HC, Material Type 52 C1-18, A1-A6, N, D0, FS Title
*MAT_BARLAT_ Used for modeling anisotropic Rho, E, PR, K, E0, N, M, A, B, C, F, G, ANISOTROPIC_PLA material behavior in forming H, LCID, AOPT STICITY processes. Title *MAT_BARLAT_YLD Developed to overcome some 2000 shortcomings of the six parameters Barlat model implemented at Material Type 33. Available for shell elements only.
Material Type 33
RO, E, PR, FIT, Material Type 133 BETA, ITER, K, E0, N, C, P, A, ALPHA1ALPHA8 Title Hardening Law (Exponential hardening, Voce hardening, By Curve) Anisotropy axis definition (By element nodes, Define global vector, Define local vector, Pick system)
*MAT_BARLAT_YLD Used for modeling anisotropic 96 material behavior in forming processes in particular for aluminum alloys. Available for shell elements only.
Rho, E, PR, K, E0, Material Type 33b N, ESRO, M, HARD, A, C1, C2, C3, CR, AX, AY, AZ0, AZ1, AOPT Title LCID_hardeningOpt
*MAT_BILKHU/ DUBOIS_FOAM
Used for the simulation of isotropic crushable forms.
RHO, YM, LCPY, LCUYS, VC, PC, VPC, TSC, VTSC, LCRATE, PR, KCON, ISFLG Title
Material Type 75

Altair Engineering
*MAT_BLATZKO_FOAM
Used for the definition of rubber-like foams of polyurethane. This one parameter allows the modeling of nearly incompressible continuum rubber.
Rho, G, REF Title Rho, G, REF Title
Material Type 38
*MAT_BLATZKO_RUBBER
Material Type 7
*MAT_BRITTLE_DA MAGE
RO, E, PR, TLIMIT, SLIMIT, FTOUGH, SRETEN, VISC, FRA_RF, E_RF, YS_RF, EH_RF, FS_RF, SIGY Title
Material Type 96
*MAT_CABLE_DISC Permits elastic cables to be Rho, E, LCID, FO, RETE_ realistically modeled; thus, no TMAXFO, TRAMP, BEAM force will develop in IREAD compression. Title *MAT_CELLULAR_R Provides a cellular rubber UBBER model with confined air pressure combined with linear viscoelasticity.
Material Type 71
RO, PR, N, C10, Material Type 87. C01, C11, C20, C02, PO, PHI, IVS, G, BETA Title
*MAT_CLOSED_CE LL_ FOAM
Allows the modeling of low density, closed cell polyurethane foam.
Rho, E, A, B, C, P0, PHI, GAMA0, LCID Title RO, ROFLG, INTFAIL, ET, EN, FN_FAIL Title
Material Type 53.
*MAT_COHESIVE_ ELASTIC
Simple cohesive elastic model for use with solid element types 19 and 20 and is not available for other solid element formulations. An orthotropic material with optional brittle failure for composites can be defined.
Material Type 184
*MAT_COMPOSITE _ DAMAGE
Rho, EA, EB, EC, Material Type 22. PRBA, PRCA, PRCB, GAB, GBC, GCA, KFAIL, MACF, SC, XT, YT, YC, ALPH, SN, SYZ, SZX
Altair Engineering

Title Anisotropy axis definition (0.0, 1.0, 2.0, 3.0, 4.0, by system) *MAT_COMPOSITE _ FAILURE_MODEL RO, EA, EB, EC, PRBA, PRCA, PRCB, GAB, GBC, GCA, KF, AOPT, MAFLAG, TSIZE, ALP, SOFT, FBRT, SR, SF, XC, XT, YC, YT, SC Options (Shell, Solid, None) Title *MAT_COMPOSITE _ FAILURE_SHELL_M ODEL RO, EA, EB, EC, PRBA, PRCA, PRCB, GAB, GBC, GCA, KF, AOPT, MAFLAG, TSIZE, ALP, SOFT, FBRT, SR, SF, XC, XT, YC, YT, SC Option (Shell, Solid, None) Title *MAT_COMPOSITE _ FAILURE_SOLID_M ODEL RO, EA, EB, EC, PRBA, PRCA, PRCB, GAB, GBC, GCA, KF, AOPT, MAFLAG, SBA, SCA, SCB, XXC, YYC, ZZC, XXT, YYT, ZZT Title *MAT_COMPOSITE _LAYUP Used for modeling the elastic responses of composite layups that have an arbitrary number of layers through the shell thickness. Rho, EA, EB, EC, PRBA, PRCA, PRCB, GAB, GBC, GCA, AOPT Title RO, PR, SIGF, AO, Material Type 72 Material Type 116. Material Type 59. Material Type 59. Material Type 59.
*MAT_CONCRETE_ Used to analyze buried steel

Altair Engineering
DAMAGE
reinforced concrete structures A1, A2, AOY, A1Y, subjected to impulsive A2Y, A1F, A2F, B1, loadings. B2, B3, PER, ER, PRR, SIGY, ETAN, LCP, LCR, L1-L13, NU1-NU13 Title Anisotropy axis definition (0, 1, 2, 3, 4, by system)
*MAT_CORUS_VEG Plane stress orthotropic TER material model for metal forming
RO, E, PR, N, FBI, RBI0, LCID, SYS, SIP, SHS, SHL, ESH, E0, ALPHA, LCID2, FUN, RUN, FPS1, FPS2, FSH Title Anisotropy axis definition (0, 1, 2, 3, 4, by system)
Material Type 136
*MAT_CRUSHABLE Used to model crushable _FOAM foam with optional damping and tension cutoff. *MAT_CSCM Concrete material
Rho, E, NU, LCID, TSC, DAMP Title
Material Type 63.
RO, NPLOT, INCRE, Material Type 159. IRATE, ERODE, RECOV, ITRETRC, PRED, G, K, ALPHA, THETA, LAMDA, BETA, NH, CH, ALPHA1, THETHA1, LAMDA1, BETA1, ALPHA2, THETA2, LAMBDA2, BETA2, R, X0, W, D1, D2, B, GFC, D, GFT, GFS, PWRC, PWRT, PMOD, ETA0C, NC, ETA0T, NT, OVERC, OVERT, SRATE, REPOW Options (None,
Altair Engineering

Concrete) Title RECOV Options (1, 2) *MAT_CSCM_CONC Concrete material RETE RO, NPLOT, INCRE, Material Type 159. IRATE, ERODE, RECOV, ITRETRC, PRED, FPC, DAGG, UNITS Title RECOV Options (1, 2) LCDR Title
*MAT_DAMPER_ Used for discrete springs and NONLINEAR_VISCU dampers. OUS *MAT_DAMPER_VI SCOUS Used for discrete springs and dampers.
Material Type SD-5.
DC Title
Material Type SD-2.
*MAT_DESHPANDE Used for modeling aluminum _ foam used as a filler material FLECK_FOAM in aluminum extrusions to enhance the energy absorbing capability of the extrusion. For solid elements.
Rho, E, PR, ALPHA, Material Type 154. GAMMA, EPSD, ALPHA2, BETA, SIGP, DERFI, CFAIL Title
*MAT_ELASTIC
Isotropic elastic material that is available for beam, shell and solid elements.
Rho, E, Nu, DA, DB, Material Type 1. K Fluid_Option Title
*MAT_ELASTIC_FL UID
Isotropic elastic material available for beam, shell and solid elements.
Rho, E, Nu, DA, DB, Material Type 1. K, VC, CP Title RO, G, SIGY, EH, PC, FS, CHARL SPALL Material Type 10.
*MAT_ELASTIC_PL ASTIC_ HYDRO
Allows the modeling of an elastic-plastic hydrodynamic material.

Altair Engineering
Title *MAT_ELASTIC_PL ASTIC_ THERMAL *MAT_ELASTIC_SP RING_ DISCRETE_BEAM Temperature dependent material coefficients can be defined. Permits elastic springs with damping to be combined and represented with a discrete beam element type 6. Rho Title Rho, K, FO, D, CDF, Material Type 74. TDF, FLCID, HLCID, C1, C2, DLE, GLCID Title RO, E, PR, SIGY, Material Type 106. ALPHA, LCSS, QR1, CR1, QR2, CR2, QX1, CX1, QX2, CX2, C, P, LCE, LCPR, LCSIGY, LCR, LCX, LCALPH, LCC, LCP Title *MAT_ELASTIC_WI TH_ VISCOSITY Used to simulate forming of glass products at high temperatures. RO, V0, A, B, C, LCID, PR1- PR8, T1 - T8, V1 - V8, E1 E8, ALPHA1 ALPHA8 Title *MAT_ELASTIC_6D OF_ SPRING_DISCRETE _BEAM 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. Rho, TPIDR, TPIDS, TPIDT, RPIDR, RPIDS, RPIDT Title Material Type 93. Material Type 60. Material Type 4.
*MAT_ELASTIC_ VISCOPLASTIC_TH ERMAL
Elastic viscoplastic material with thermal effects.
*MAT_ENHANCED_ Enhanced versions of the COMPOSITE_DAM composite model Material AGE Type 22.
Rho, EA, EB, EC, Material Types 54-55. PRBA, PRCA, PRCB, GAB, GBC, GCA, KF, AOPT, DFAILM, DFAILS, TFAIL, ALPH, FBRT, YCFAC, DFAILT, EFS, XC, XT, YC, YT, SC, CRIT, BETA Title
Altair Engineering

*MAT_FABRIC
Developed for airbag materials.
Rho, EA, EB, EC, PRBA, PRCA, PRCB, GAB, GBC, GCA, CSE, EL, PRL, LRATIO, DAMP, AOPT, X2, X3, ELA, LNRC, FORM, FVOPT, TSRFAC, X0, X1 Title LCID_leakCoeff LCID_areaCoeff LCID_effLeakArea LCID_tensileStressC urve
Material Type 34.
*MAT_FINITE_ELAS TIC_ STRAIN_PLASTICIT Y
An elasto-plastic material with an arbitrary stress versus strain curve and arbitrary strain rate dependency can be defined.
Rho, E, PR, SIGY, ETAN, C, P, LCSS, LCSR, ArrayCount, EPS, ES Title Rho, E, PR, SIGY, ETAN, R, HLCID, LCIDFLD Title
Material Type 112.
*MAT_FLD_ TRANSVERSELY_ ANISOTROPIC
Used for simulating sheet forming processes with anisotropic material.
Material Type 39.
*MAT_FLD_3_ PARAMETER_BAR LAT
Used for modeling sheets with Rho, E, PR, P1, P2, Material Type 190. anisotropic materials under ITER, M, R00, R45, plane stress conditions. R90, SPI, C, P, FLDCID, RN, RT, FLDSAFE, FLDNIPF Title Hardening Law (Linear, Swift exponential, By load curve, Voce exponential, Gosh exponential, HocketSherby exponential) Anisotropy axis definition (By element nodes, Define global vector,

Altair Engineering
Define local vector, Pick system) *MAT_FORCE_LIMI TED With this material model, for the Belytschko-Schwer beam only, plastic hinge forming at the ends of a beam can be modeled using curve definitions. Rho, E, NU, DF, AOPT, YTFLAG, ASOFT, LC1- LC8, LPS1, SFS1, LPS2, SFS2, YMS1, YMS2, LPT1, SFT1, LPT2, SFT2, YMT1, YMT2, LPR, SFR, YMR Title *MAT_FRAZER_NA SH_ RUBBER_MODEL This model defines rubber from uniaxial test data. Rho, Nu, C100-C400, Material Type 31. C110, C210, C010, C020, EXIT, EMAX, EMIN, REF, SGL, SW, ST, LCID Title *MAT_FU_CHANG_ FOAM Rate effects can be modeled in low and medium density foams. RO, E, ED, TC, Material Type 83. FAIL, DAMP, TBID, BVFLAG, SFLAG, RFLAG, TFLAG, PVID, SRAF, REF, HU, DO, NO, N1, N2, N3, CO, C1, C2, C3, C4, C5, AIJ, SIJ, MINR, MAXR, SHAPE Title Material Type 29.
*MAT_GAS_MIXTUR Used for the simulation of E thermally equilibrated ideal gas mixtures.
IADIAB, RUNIV, CVmass, CPmass Title
Material Type 148.
*MAT_GENERAL_J OINT_ DISCRETE_BEAM
Used to define a general joint constraining any combination of degrees of freedom between two nodes.
Rho, TR, TS, TT, RR, Material Type 97. RS, RT, RPST, RPSR Title Rho, K, UNLDOPT, OFFSET, DAMPF, Material Type 121.
*MAT_GENERAL_ NONLINEAR_1DOF
Very general spring and damper model.
Altair Engineering

_ DISCRETE_BEAM
LCIDT, LCIDTU, LCIDTD, LCIDTE, UTFAIL, UCFAIL, IU Title
*MAT_GENERAL_ NONLINEAR_6DOF _ DISCRETE_BEAM
Very general spring and damper model.
Rho, KT, KR, Material Type 119 UNLDOPT, OFFSET, DAMPF, LCIDTR, LCIDTS, LCIDTT, LCIDRR, LCIDRS, LCIDRT, LCIDTUR, LCIDTUS, LCIDTUT, LCIDRUR, LCIDRUS, LCIDRUT, LCIDTDR, LCIDTDS, LCIDTDT, LCIDRDR, LCIDRDS, LCIDRDT, LCIDTER, LCIDTES, LCIDTET, LCIDRER, LCIDRES, LCIDRET, UTFAILR, UTFAILS, UTFAILT, WTFAILR, WTFAILS, WTFAILT, UCFAILR, UCFAILS, UCFAILT, WCFAILR, WCFAILS, WCFAILT, IUR, IUS, IUT, IWR, IWS, IWT Title
*MAT_GENERAL_S PRING_ DISCRETE_BEAM
Permits elastic and elastoplastic springs with damping to be represented with a discrete beam element type 6 using six springs each acting about one of the six local degrees of freedom. 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.
Rho, DOF, TYPE, K, Material Type 196. D, CDF, TDF, FLCID, HLCID, C1, C2, DLE, GLCID Title
*MAT_GENERAL_ VISCOELASTIC
RHO, BULK, PCF, EF, TREF, A, B, LCID, NT, BSTART, TRAMP, LCIDK, NTK, BSTARTK, TRAMPK Title
Material Type 76.

Altair Engineering
*MAT_GEOLOGIC_ CAP_ MODEL
This is an inviscid two invariant geologic cap model.
Rho, BULK, G, Material Type 25. ALPHA, THETA, GAMMA, BETA, R, D, W, X0, C, N, PLOT, FTYPE, VEC, TOFF Title
*MAT_GEPLASTIC_ Characterizes General SRATE Electric's commercially _2000a available engineering thermoplastics subjected to high strain rate events.
Rho, E, PR, RATESF, EDOT0, ALPHA, LCSS, LCFEPS, LCFSIG, LCE Title
Material Type 101.
*MAT_GURSON
Gurson dilatational-plastic model. Available for shell and solid elements.
RO, E, PR, SIGY, N, Material Type 120. Q1, Q2, FC, FO, EN, SN, FN, ETAN, ATYP, FFO, EPS1EPS8, ES1-ES8, L1L4, FF1-FF4, LCSS, LCLF, NUMINT, LCFO, LCFC, LCFN, VGTYP Title
*MAT_GURSON_JC Enhancement of Material Type 120. Gurson model with additional Johnson-Cook failure criterion.
RO, E, PR, SIGY, N, Material Type 120b. Q1, Q2, FC, FO, EN, SN, FN, ETAN, ATYP, FFO, EPS1EPS8, SIG1-SIG8, LCDAM, L1, L2, D1D4, LCSS, LCFF, NUMINT, LCFO, LCFC, LCFN, VGTYP Title
*MAT_HIGH_EXPLO Allows the modeling of the Rho, D, PCJ, BETA SIVE_ detonation of a high explosive. Title BURN *MAT_HILL_FOAM Highly compressible foam. Rho, K, N, MU, LCID, FITTYPE, LCSR, C1-C8, B1-
Material Type 8.
Material Type 177.
Altair Engineering

B8, R, M Title *MAT_HILL_3R Planar anisotropic material model with 3 R values. RO, E, PR, HR, P1, P2, ROO, R45, R90, LCID, EO Title Anisotropy axis definition (0, 1, 2, 3, 4, by system) *MAT_HONEYCOM B The major use of this material model is for honeycomb and foam materials with real anisotropic behavior. Rho, E, NU, SIGY, VF, MU, BULK, LCA, LCB, LCC, LCS, LCAB, LCBC, LCCA, LCSR, EAAU, EBBU, ECCU, GABU, GBCU, GCAU, AOPT, MACF, TSEF, SSEF Title *MAT_HYDRAULIC_ GAS_ DAMPER_DISCRET E_ BEAM Special purpose element represents a combined hydraulic and gas-filled damper which has a variable orifice coefficient. RO, CO, N, PO, PA, Material Type 70. AP, KH, LCID, FR, SCLF, CLEAR Title RO, PR, N, NV, G, Material Type 77. SIGF, C10, C01, C11, C20, C02, C30, ArrayCount Title Material Type 26. Material Type 122.
*MAT_HYPERELAS Provides a general TIC_ hyperelastic rubber model RUBBER combined optionally with linear viscoelasticity.
*MAT_INELASTIC_S Allows elastoplastic springs PRING_ with damping to be DISCRETE_BEAM represented with a discrete beam element type 6.
Rho, K, FO, D, CDF, Material Type 94. TDF, FLCID, HLCID, C1, C2, DLE, GLCID Title Rho, TPIDR, TPIDS, TPIDT, RPIDR, RPIDS, RPIDT Material Type 95.
*MAT_INELASTIC_6 Defined for simulating the DOF_ effects of nonlinear inelastic SPRING_DISCRETE and nonlinear viscous beams

Altair Engineering
_BEAM
by using six springs each acting about one of the six local degrees of freedom. Non-iterative plasticity with simple plastic strain failure model.
Title
*MAT_ISOTROPIC_ ELASTIC_FAILURE
Rho, G, SIGY, ETAN, BULK, EPF, PRF, REM, TREM Title
Material Type 13.
*MAT_ISOTROPIC_ ELASTIC_PLASTIC
Very low cost isotropic plasticity model for threedimensional solids.
Rho, G, SIGY, ETAN, BULK Title
Material Type 12.
*MAT_JOHNSON_C The Johnson/Cook strain and OOK temperature sensitive plasticity is sometimes used for problems where the strain rates vary over a large range and adiabatic temperature increases due to plastic heating causes material softening.
Rho, G, E, Nu, DTF, VP, RATEOP, A, B, N, C, M, TM, TR, EPSO, CP, PC, SPALL, IT, D1 - D5, C2/P Title
Material Type 15.
*MAT_JOHNSON_ Useful for modeling ceramics, RO, G, A, B, C, M, HOLMQUIST_CERA glass and other brittle N, EPSI, T, SFMAX, MICS materials. HEL, PHEL, BETA, D1, D2, K1, K2, K3, FS Title *MAT_KELVINUsed for modeling MAXWELL_VISCOE viscoelastic bodies, e.g., LASTIC foams. Rho, BULK, G0, G1, DC, FO, SO Title RO, E, PR, R, CB, Y, SC, K, RSAT, SB, H, EA, COE Title
Material Type 110.
Material Type 61.
*MAT_KINEMATIC_ HARDENING_ TRANSVERSELY_ ANISOTROPIC
Material Type 125
*MAT_LAMINATED_ Depending on the type of COMPOSITE_FABR failure surface, may be used IC to model composite materials with unidirectional layers,
Rho, EA, EB, EC, Material Type 58. PRBA, TAU1, GAMMA1, GAB, GBC, GCA, SLIMT1,
Altair Engineering

complete layers, complete laminates, and woven fabrics.
SLIMC1, SLIMT2, SLIMC2, SLIM2, TSIZE, ERODS, SOFT, FS, E11C, E11T, E22C, E22T, GMS, XC, XT, YC, YT, SC Title Anisotropy axis definition (By element nodes, Define global vector, Define local vector, Pick system)
*MAT_LAMINATED_ With this material model, a GLASS layered glass including polymeric layers can be modeled.
Rho, E, Nu, SYG, ETG, EFG, EP, PRP, SYP, ETP Title RO, E, PR, SIGY, ETAN, FAIL, TDEL, C, P, LCSS, LCSR, EPS1-EPS8, ES1ES8 Title
Material Type 32.
*MAT_LAYERED_LI Layered elastoplastic material NEAR_ with an arbitrary stress versus PLASTICITY strain curve and an arbitrary strain rate dependency can be defined.
Material Type 114.
*MAT_LINEAR_ELA STIC_ DISCRETE_BEAM
Used for simulating the effects of a linear elastic beam by using six springs each acting about one of the six local degrees of freedom.
Rho, TKR, TKS, Material Type 66. TKT, RKR, RKS, RKT,TDR, TDS, TDT, RDR, RDS, RDT, FOR, FOS, FOT, MOR, MOS, MOT Title
*MAT_LOW_DENSI TY_ FOAM
Used for modeling high density foams.
Rho, E, LCID, TC, Material Type 57. HU, BETA, DAMP, SHAPE, FAIL, ED, BETA1, KCON, REF Title
*MAT_LOW_DENSI TY_ SYNTHETIC_FOAM
Used for modeling rate independent low density foams, which have the property that the hysteresis in
Rho, E, LCID1, LCID2, HU, BETA, DAMP, SHAPE, FAIL, BVFLAG, ED,
Material Type 179.

Altair Engineering
the loading-unloading curve is BETA1, KCON, considerably reduced after the REF, TC first loading cycle. Options (None, DEFINE TABLE, FAILURE) Title DAMP_Option *MAT_LOW_DENSI TY_ SYNTHETIC_FOAM _ ORTHO Used for modeling rate independent low density foams, which have the property that the hysteresis in the loading-unloading curve is considerably reduced after the first loading cycle. Rho, E, LCID1, LCID2, HU, BETA, DAMP, SHAPE, FAIL, BVFLAG, ED, BETA1, KCON, REF, TC Options (None, DEFINE TABLE, FAILURE) Title DAMP_Option *MAT_LOW_DENSI TY_ SYNETHIC_FOAM_ ORTHO _WITH_FAILURE Used for modeling rate independent low density foams, which have the property that the hysteresis in the loading-unloading curve is considerably reduced after the first loading cycle. Rho, E, LCID1, LCID2, HU, BETA, DAMP, SHAPE, FAIL, BVFLAG, ED, BETA1, KCON, REF, TC, K, GAMA1, GAMA2, EH Title DAMP_Option *MAT_LOW_DENSI TY_ SYNTHETIC_FOAM _WITH_ FAILURE Used for modeling rate independent low density foams, which have the property that the hysteresis in the loading-unloading curve is considerably reduced after the first loading cycle. Rho, E, LCID1, LCID2, HU, BETA, DAMP, SHAPE, FAIL, BVFLAG, ED, BETA1, KCON, REF, TC, K, GAMA1, GAMA2, EH Title DAMP_Option *MAT_LOW_DENSI TY_ VISCOUS_FOAM Used for modeling Low Density Urethane Foam with high compressibility and with rate sensitivity which can be Rho, E, LCID, TC, HU, BETA, DAMP, SHAPE, FAIL, BVFLAG, KCON, Material Type 73. Material Type 179. Material Type 180. Material Type 180.
Altair Engineering

characterized by a relaxation curve.
LCID2, BSTART, TRAMP, NV Title DAMP_Option Rho, E, PR, TID, TSC, DAMP, NCYCLE, SCRLMT Title Rho, E, NU, SIGY, Material Type 126. VF, MU, BULK, LCA, LCB, LCC, LCS, LCAB, LCBC, LCCA, LCSR, EAAU, EBBU, ECCU, GABU, GCAU, AOPT, MACF, TSEF, SSEF, VREF, TREF, SHDFLG Title LCA, LCB, LCC, LCS, LCAB, LCBC, LCCA options
*MAT_MODIFIED_ CRUSHABLE_FOA M
Dedicated to modeling crushable foam with optional damping, tension cutoff, and strain rate effects. Used for aluminum honeycomb crushable foam materials with anisotropic behavior.
Material Type 163
*MAT_MODIFIED_ HONEYCOMB
*MAT_MODIFIED_ PIECEWISE_LINEA R_ PLASTICITY
An elasto-plastic material with an arbitrary stress versus strain curve and arbitrary strain-rate dependency can be defined.
Rho, E, PR, SIGY, ETAN, FAIL, TDEL, C, P, LCSS, LCSR, VP, EPSTHIN, EPSMAJ, NUMINT, ArrayCount, EPS, ES RATE_Option Title
Material Type 123.
*MAT_MODIFIED_ PIECEWISE_LINEA R_ PLASTICITY_RATE
An elasto-plastic material with an arbitrary stress versus strain curve and arbitrary strain rate dependency can be defined.
Rho, E, PR, SIGY, ETAN, FAIL, TDEL, C, P, LCSS, LCSR, VP, EPSTHIN, EPSMAJ, NUMINT, ArrayCount, EPS, ES, LCTSRF Title
Material Type 123.
*MAT_MODIFIED_
Rate and temperature
Rho, G, E0, N,
Material Type 65.

Altair Engineering
ZERILLI_ARMSTRO NG
sensitive plasticity model which is sometimes preferred in ordinance design calculations.
TROOM, PC, SPALL, C1-C6, EFAIL, VP, B1-B3, G1-G4, BULK Title
*MAT_MOONEY_RI VLIN_ RUBBER
A two-parametric material model for rubber can be defined.
Rho, NU, A, B, REF, Material Type 27. SGL, SW, ST, LCID Title RO, SIGA, SIGI, Material Type 88. SIGS, SIGO, BULK, HFO, HF1, HF2, SIGSO, EDOTSO, BURG, CAPA, BOLTZ, SMO, SM1, SM2, EDOTO, GO, PINV, QINV, EDOT1, GOI, PINVI, QINVI, EDOTS, GOS, PINVS, QINVS, RHOCPR, TEMPRF, ALPHA, EPSO Title Rho, LCIDTR, Material Type 67. LCIDTS, LCIDTT, LCIDRR, LCIDRS, LCIDRT, LCIDTDR, LCIDTDS, LCIDTDT, LCIDRDR, LCIDRDS, LCIDRDT, FOR FOS, FOT, MOR MOS, MOT Title
*MAT_MTS
Available for applications involving large strains, high pressures and strain rates.
*MAT_NONLINEAR_ ELASTIC_DISCRET E_ BEAM
Used 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.
*MAT_NONLINEAR_ Allows the definition of an ORTHOTROPIC orthotropic nonlinear elastic material based on a finite strain formulation with the initial geometry as the reference.
Rho, EA, EB, EC, PRBA, PRCA, PRCB, GAB, GBC, GCA, DT, TRAMP, ALPHA, LCIDA, LCIDB, EFAIL, DTFAIL, CDAMP, AOPT, MACF, LCIDC, LCIDAB, LCIDBC, LCIDCA
Material Type 40.
Altair Engineering

Title *MAT_NONLINEAR_ PLASTIC_DISCRET E_ BEAM Used 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. Rho, TKR, TKS, RKR, RKS, RKT, TDR, TDS, TDT, RDR, RDS, RDT, LCPDR, LCPDS, LCPDT, LCPMR, LCPMS, LCPMT, FFAILR, FFAILS, FFAILT, MFAILR, MFAILS, MFAILT, UFAILR, UFAILS, UFAILT, TFAILR, TFAILS, TFAILT, FOR, FOS, FOT, MOR, MOS, MOT Title *MAT_NULL Allows equations of state to be considered without computing deviatoric stresses. Ro, PC, MU, TEROD, CEROD, E, PR Title RO, PR, N, NV, G, SIGF, MU1-MU8, AL1-AL8, ViscoConst Title *MAT_ORIENTED_C This material may be used to RACK model brittle materials which fail due to large tensile stresses. Rho, E, PR, SIGY, ETAN, FS, PRF Title Material Type 2 Material Type 17. Material Type 9. Material Type 68.
*MAT_OGDEN_RUB Provides the Ogden (1984) BER rubber model combined optionally with linear viscoelasticity.
Material Type 77.
*MAT_ORTHOTROP Valid for modeling the elastic- Rho, EA, EB, EC, IC_ orthotropic behavior of solids, PRBA, PRCA, ELASTIC shells and thick shells. PRCB, GAB, GBC, GCA, G, SIGF Aniso_Option Title Anisotropy axis definition (0.0, 1.0, 2.0, 3.0, 4.0, by system)

Altair Engineering
*MAT_ORTHOTROP A linearly elastic, orthotropic IC_ material with orthotropic THERMAL thermal expansion.
RO, EA, EB, EC, PRBA, PRCA, PRCB, GAB, GBC, GCA, AA, AB, AC, AOPT, MACF, REF Title
Material Type 21.
*MAT_ORTHOTROP Allows the definition of an IC_ orthotropic material with a VISCOELASTIC viscoelastic part. Applies to shell elements.
RO, EA, EB, EC, Material Type 86. VF, K, GO, GINF, BETA, PRBA, PRCA, PRCB, GAB, GBC, GCA Title Anistropy axis definition (By element nodes, Define global vector, Define local vector, Pick system)
*MAT_PIECEWISE_ An elasto-plastic material with LINEAR_PLASTICIT an arbitrary stress versus Y strain curve and arbitrary strain rate dependency can be defined.
Rho, E, NU, SIGY, Material Type 24. ETAN, EPPF, TDEL, C, P, LCSS, LCSR, VP, ArrayCount Title RO, E, PR, C, P, Material Type 124. Fail, TDEL, LCIDC, LCIDT, LCSRC, LCSRT, SRFLAG, LCFAIL, PC, PT, PCUTC, PCUTT, PCUTF, K, ArrayCount, GI, beta Title
*MAT_PLASTICITY_ An isotropic elastic-plastic COMPRESSION_TE material where unique yield NSION stress versus plastic strain curves can be defined for compression and tension.
*MAT_PLASTICITY_ COMPRESSION_TE NSION_ E0S
An isotropic elastic-plastic material where unique yield stress versus plastic strain curves can be defined for compression and tension.
RO, E, PR, C, P, Material Type 155. Fail, TDEL, LCIDC, LCIDT, LCSRC, LCSRT, SRFLAG, PC, PT, PCUTC, PCUTT, PCUTF, K, ArrayCount, GI, beta Title
Altair Engineering

*MAT_PLASTIC_ KINEMATIC
Suited to model isotropic and Rho, E, NU, SIGY, kinematic hardening plasticity ETAN, BETA, SRC, with the option of including SRP, FS, VP rate effects. Title RO, E, PR, C, P, LSCC, LCSR, EFTX, DAMP, RATEFAC, LCFAIL Title
Material Type 3
*MAT_PLASTICITY_ An elasto-plastic material with POLYMER an arbitrary stress versus strain curve and arbitrary strain rate dependency can be defined.
Material Type 89.
*MAT_PLASTICITY_ An elasto-visco-plastic WITH_DAMAGE material with an arbitrary stress versus strain curve and arbitrary strain rate dependency can be defined.
RO, E, PR, SIGY, Material Types 81-82. ETAN, EPPF, TDEL, C, P, LCSS, LCSR, EPPFR, VP, LCDM, NUMINT, ArrayCount Options (None, ORTHO, ORTHO_RCDC) Title
*MAT_PLASTICITY_ Invokes an orthotropic WITH_DAMAGE_O damage model RTHO
RO, E, PR, SIGY, Material Types 81-82. ETAN, EPPF, TDEL, C, P, LCSS, LCSR, EPPFR, VP, LCDM, NUMINT, ArrayCount Title
*MAT_PLASTICITY_ Invokes the damage model WITH_DAMAGE_RC developed by Wilkins DC
RO, E, PR, SIGY, Material Types 81-82. ETAN, EPPF, TDEL, C, P, LCSS, EPPFR, VP, LCDM, NUMINT, ArrayCount, ALPHA, BETA, GAMMA, D0, B, LAMBA, DS, L Rho, E, NU, K, N, SRC, SRP, SIGY, VP Title Rho, G, PR, SIGF, A0, A1, A2, A0F, Material Type 16. Material Type 18.
*MAT_POWER_LA W_ PLASTICITY
This is an isotropic plasticity model with rate effects which uses a power law hardening rule.
*MAT_PSEUDO_TE NSOR
This model has been used to analyze buried steel

Altair Engineering
reinforced concrete structures A1F, B1, PER, ER, subjected to impulsive PRR, SIGY, ETAN, loadings. LCP, LCR, X1- X16, YS1-YS16 Title Rho, E, Nu, K, M, N, Material Type 64. E0, VP, EPS0 Title K_Option Rho, E11P, E22P, V12P, V21P, G12P, G23P, G31P, E11B, E22B, V12B, V21B, G12B, AOPT, LN11, LN22, LN12, LQ1, LQ2, LM11, LM22, LM12 Title *MAT_RESULTANT_ A resultant formulation for PLASTICITY beam and shell elements including elasto-plastic behavior can be defined. *MAT_RIGID Rho, E, NU, SIGY, ETAN Title Material Type 28. Material Type 170.
*MAT_RATE_SENSI TIVE_ POWERLAW_PLAS TICITY
Used to model strain rate sensitive elasto-plastic material with a power law hardening.
*MAT_RESULTANT_ This model is available the ANISOTROPIC Belytschko-Tsay and the C0 triangular shell elements and is based on a resultant stress formulation.
Parts made from this material Rho, E, NU, N, Material Type 20. are considered to belong to a COUPLE, M, ALIAS, rigid body (for each part ID). CMO, A1-A3, V1-V3 Title LocalCoordinateSyst em RO, BULK, GMOD, Material Type 187. EMOD, NUE, LCIDT, LCID-C, LCID-S, LCID-B, NUEP, LCID-P, LCID-D, DC, DEPRPT, LCID_TRI, LCID_LC, MITER, MIPS, IVM, IQUAD, ICONV Title
*MAT_SAMP-1
Uses an isotropic C-1 smooth yield surface for the description of non-reinforced plastics.
Altair Engineering

*MAT_SCHWER_ MURRARY_CAP_M ODEL
The Schwer & Murray Cap Model, known as the Continuous Surface Cap Model, is a three invariant extension of the Geological Cap Model (Material Type 25) that also includes viscoplasticity for rate effects and damage mechanics to model strain softening.
RO, SHEAR, BULK, Material Type 145. GRUN, SHOCK, PORE, ALPHA, THETA, GAMMA, BETA, EFIT, FFIT, ALPHAN, CALPHA, R0, X0, IROCK, SECP, AFIT, BFIT, RDAMO, W, D1, D2, NPLOT, EPSMAX, CFIT, DFIT, TFAIL, FAILFG, DBETA, DDELTA, VPTAU, ALPHA1, THETA1, GAMMA1, BETA1, ALPHA2, THETA2, GAMMA2, BETA2 Title
*MAT_SEATBELT
Define a seat belt material.
MPUL, LLCID, ULCID, LMIN Title
*MAT_SHAPE_ME MORY
This material model describes the superelastic response present in shape-memory alloys that is the peculiar material ability to undergo large deformations with full recovery in loading-unloading cycles. 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.
Rho, E, Nu, Material Type 30. SIG_ASS, SIG_ASF, SIG_SAS, SIG_SAF, EPSL, ALPHA, YMRT Title
*MAT_SID_DAMPE R_ DISCRETE_BEAM
Rho, SST, D, R, H, K, C, C3, STF, RHOF, C1, C2, LCIDF, LCIDD, S0, ArrayCount Title K_Option Rho, E, PR, VP, A, B, N, C, PSFAIL, SIGMAX, SIGSAT, EPSO Title
Material Type 69.
*MAT_SIMPLIFIED_ Used for problems where the JOHNSON_COOK strain rates vary over a large range.
Material Type 98.

Altair Engineering
*MAT_SIMPLIFIED_ JOHNSON_COOK_ ORTHOTROPIC_DA MAGE
Implemented with multiple through thickness integration points. Extension of Model 98 to include orthotropic damage as a means of treating failure in aluminum panels.
Rho, E, PR, VP, Material Type 99. EPPFR, LCDM, NUMINT, A, B, N, C, PSFAIL, SIGMAX, SIGSAT, EPSO Title Rho, KM, MU, G, SIGF, REF, PRTEN, SGL, SW, ST, LC/ TBID, TENSION, RTYPE, AVGOPT, PR/BETA With-Failure Title Material Type 181.
*MAT_SIMPLIFIED_ Provides a rubber and foam RUBBER/FOAM model defined by a single uniaxial load curve or by a family of uniaxial curves at discrete strain rates.
*MAT_SIMPLIFIED_ Provides an incompressible RUBBER_WITH_DA rubber model defined by a MAGE single uniaxial load curve for loading (or a table if rate effects are considered) and a single uniaxial load curve for unloading. *MAT_SOIL_AND_F OAM Simple model that works in some ways like a fluid.
RHO, K, MU, G, Material Type 183. SIGF, SGL, SW, ST, LCLD, TENSION, RTYPE, AVGOPT, LCUNLD Title
Rho, G, BULK, A0 A2, PC, VCR, REF, EPS, P Title
Material Type 5.
*MAT_SOIL_AND_F OAM_ FAILURE
The input for this model is the same as for *MAT_SOIL_AND_FOAM; however, when the pressure reaches the failure pressure, the element loses its ability to carry tension. Applies to beam elements Type 9 and to solid elements Type 1 with Type 6 hourglass controls.
Rho, G, BULK, A0 A2, PC, VCR, REF, EPS, P Title
Material Type 14.
*MAT_SPOTWELD
Rho, E, PR, SIGY, ET, DT, TFAIL, EFAIL, NRR, NRS, MRR, MSS, MTT, NF Damage-Failure Title LCID-NRR LCID-NRS
Material Type 100.
Altair Engineering

*MAT_SPOTWELD_ Applies to solid elements DAIMLER_CHRYSL Type 1 with Type 6 hourglass ER controls.
RO, E, PR, DT, TFAIL, EFAIL, NF, RS, TRUE_T, CON_ID Title
Material Type 100.
*MAT_SPOTWELD_ Applies to beam element type DAMAGE 9 and to solid element type 1 with type 6 hourglass controls.
Rho, E, PR, SIGY, Material Type 100. ET, DT, TFAIL, OPT, EFAIL, NRR, NRS, NRT, MRR, MSS, MTT, NF, RS, OPT, FVAL, TRUE_T, BETA Title
*MAT_SPRING_ELA Used for discrete springs and STIC dampers. Provides a translational or rotational elastic spring located between two nodes. *MAT_SPRING_ ELASTOPLASTIC
K Title
Material Type SD-1.
Used for discrete springs and K, KT, FY dampers. Provides an Title elastoplastic translational or rotational spring with isotropic hardening located between two nodes. Used for discrete springs and dampers. Provides a general nonlinear translational or rotational spring with arbitrary loading and unloading definitions. Used for discrete springs and dampers. Provides an inelastic tension or compression only, translational or rotational spring. Used for discrete springs and dampers. Provides a three Parameter Maxwell Viscoelastic translational or rotational spring.
Material Type SD-3.
*MAT_SPRING_GE NERAL_ NONLINEAR
LCDL, LCDU, BETA, Material Type SD-6. TYI, CYI Title
*MAT_SPRING_INE LASTIC
LCFD, KU, CTF Title
Material Type SD-8.
*MAT_SPRING_MA XWELL
K0, KI, BETA, TC, FC, COPT Title
Material Type SD-7.

Altair Engineering
*MAT_SPRING_ NONLINEAR_ELAS TIC
Used for discrete springs and LCD, LCR dampers. Provides a nonlinear Title elastic translational and rotational spring with arbitrary force versus displacement and moment versus rotation, respectively. This material is available for modeling materials deforming at very high strain rates (>105) and can be used with solid elements.
Material Type SD-4.
*MAT_STEINBERG
Rho, G0, SIGO, Material Type 11. BETA, N, GAMMA, SIGM, B, BP, H, F, A, TMO, GAMO, SA, PC, SPALL, RP, FLAG, MMN, MMX, EC0 - 9 LUND, Title
*MAT_STEINBERG_ This material is a modification LUND of the Steinberg model to include the rate model of Steinberg and Lund (1989).
Rho, G0, SIGO, Material Type 11. BETA, N, GAMMA, SIGM, B, BP, H, F, A, TMO, GAMO, SA, PC, SPALL, RP, FLAG, MMN, MMX, EC0 - 9, UK, C1, C2, YP, YA, YM Title
*MAT_STRAIN_RAT A strain rate dependent E_ material can be defined DEPENDENT_PLAS TICITY
Rho, E, NU, VP, LC1, ETAN, LC2, LC3, LC4, TDEL, RDEF Title
Material Type 19.
*MAT_TEMPERATU An orthotropic elastic material RE_ with arbitrary temperature DEPENDENT_ dependency can be defined. ORTHOTROPIC
RO, AOPT, REF, Material Type 23. MACF, ArrayCount, EA, EB, EC, PRBA, PRCA, PRCB, AA, AB, AC, GAB, GBC, GCA, T Title
*MAT_THERMAL_ ISOTROPIC
Allows isotropic thermal properties to be defined.
TRO, TGRLC, TGMULT, TLAT, HLAT, HC, TC
Thermal Material Property Type 1.
Altair Engineering

Title *MAT_THERMAL_ ISOTROPIC_TD_LC Allows isotropic thermal properties that are temperature dependent specified by load curves to be defined. TRO, TGRLC, TGMULT, HCLC, TCLC Title TGRCL_Option *MAT_THERMAL_ ORTHOTROPIC Allows orthotropic thermal properties to be defined. TRO, TGRLC, TGMULT, AOPT, TLAT, HLAT, HC, K1, K2, K3 Title *MAT_TRANSVERS ELY_ ANISOTROPIC_ CRUSHABLE_FOA M Used for an extruded foam material that is transversely istropic, crushable, and of low density with no significant Poisson effect. Rho, E11, E22, E12, Material Type 142. E23, G, K, NY, ANG, MU, ISCL, MACF Anisotropy axis definition (0.0, 1.0, 2.0, 3.0, 4.0, by system) RO, E, PR, SIGY, ETAN, R, HLCID Echange_Option Title RO, E, PR, SIGY, ETAN, R, HLCID, IDSCALE, EA, COE Title Material Type 37. Material Type 37. Thermal Material Property Type 2. Thermal Material Property Type 6.
*MAT_TRANSVERS This model is for simulating ELY_ sheet forming processes with ANISOTROPIC_ELA anisotropic material. STIC_ PLASTIC *MAT_TRANSVERS This model is for simulating ELY_ sheet forming processes with ANISOTROPIC_ELA anisotropic material. STIC_ PLASTIC_ECHANG E *MAT_TRIP
Isotropic elasto-plastic RO, E, PR, CP, T0, Material Type 113. material model that applies to TREF, TA0, A, B, C, shell elements only. D, P, Q, E0MART, VM0, AHS, BHS, M, N, EPS0, HMART, K1, K2 Title

Altair Engineering
*MAT_UNSUPPORT ED *MAT_USER_DEFIN User can supply their own ED_ subroutines. MATERIAL Dummy material representing Rho a vacuum in a multi-material Title Euler/ALE model. Rho, BULK, G0, GI, BETA Title Rho, K, N, MU, Material Type 178. LCID1, FITTYPE, LCSR, LCVE, NT, GSTART, C1-C8, B1B8, ArrayCount, GI, beta Title *MAT_VISCOUS_F OAM Used to represent the Confor Foam on the ribs of EuroSID side impact dummy. Rho, E1, N1, V2, E2, Material Type 62. N2, Nu Title Material Types 41-50.
*MAT_VACUUM
Material Type 140.
*MAT_VISCOELAST Allows the modeling of IC viscoelastic behavior for beams (Hughes-Liu), shells, and solids. *MAT_VISCOELAST Highly compressible foam. IC_HILL _FOAM
Material Type 6.
*MAT_WINFRITH_ CONCRETE
Only Type 84 includes rate effects. Model is a smeared crack, smeared rebar model implemented in the 8-node single integration point continuum element.
RO, TM, PR, UCS, UTS, FE, ASIZE, E, YS, EH, UELONG, RATE, CONM, CONL, CONT, EPS1-EPS8, P1-P8 Title
Material Type 84 and Type 85.
*MAT_WOOD
Wood material.
RO, NPLOT, ITERS, IRATE, GHARD, IFAIL, IVOL, EL, ET, GLT, GTR, PR, XT, XC, YT, YC, SXY, SYZ, GF1_PAR, GF2_PAR, BFIT, DMAX, GF1_PREP,
Material Type 143.
Altair Engineering

GF2_PREP, DFIT, DMAX, FLPAR, FLPARC, POWPAR, FLPER, FLPERC, POWPER, NPAR, CPAR, NPER, CPER, MACF, BETA Options (None, Pine, Fir) Title Anisotropy axis definition *MAT_WOOD_FIR Wood material. RO, NPLOT, ITERS, IRATE, GHARD, IFAIL, IVOL, MOIS, TEMP, QUAL_C, UNITS, IQUAL, MACF, BETA Title Quality factor options Anisotropy axis definition *MAT_WOOD_OPTI Transversely isotropic ON material and is available for solid elements RO, NPLOT, ITERS, IRATE, GHARD, IFAIL, IVOL, MOIS, TEMP, QUAL_C, UNITS, IQUAL, MACF, BETA Title Quality factor options Anisotropy axis definition *MAT_WOOD_PINE Wood material. RO, NPLOT, ITERS, IRATE, GHARD, IFAIL, IVOL, MOIS, TEMP, QUAL_C, UNITS, IQUAL, MACF, BETA Title Quality factor options Anisotropy axis definition Material Type 143. Material Type 143. Material Type 143.

Altair Engineering
*MAT_1DOF_ GENERALIZED_SP RING
Linear or spring damper that allows different degrees of freedom at two nodes to be coupled.
Rho, K, C, SCLN1, SCLN2, DOFN1, DOFN2, CID1, CID2 Title
Material Type 146.
*MAT_3PARAMETER_BAR LAT
Used for modeling sheets with Rho, E, PR, HR, P1, Material Type 36. anisotropic materials under P2, ITER, M, R00, plane stress conditions. R45, R90, LCID, SPI, C, P, VLCID Title YoungsModulusAsF unctionOfStrain R00FunctionOfPlasti cStrain R45FunctionOfPlasti cStrain R90FunctionOfPlasti cStrain Anistropy axis definition (By element nodes, Define global vector, Define local vector, Pick system)
MADYMO
Supported Card
Solver Description
Notes
COMPONENT
Material component used for definition of layered materials.
Defined on the card of the parent MATERIAL. Defined on the card of the parent MATERIAL.
DAMAGE
MATERIAL.ANISO
Linear elastic anisotropic material model.
DENSITY, C11, C22, C44, C12, C24, C41, MAT_DIR, MAT_DIR (X), Y, Z, MU, DAMP_COEF,
MAT_DIR can be specified by either selecting a coordinate system or entering the components of the direction vector. If a
Altair Engineering

ASSEMBLY airbag fabric properties COMMENT
coordinate system was selected, the (local) direction of the X-axis is used as MAT_DIR. KAPPA becomes available if a PERMEABILITY. MODEL is being used.
MATERIAL. ENCRYPTED MATERIAL.FABRIC Loosely woven fabric material model.
ASSEMBLY
DENSITY, TENSION_ONLY, MU, DAMP_COEF, MAT_DIR_1, MAT_DIR_1(X), Y, Z, E_1, SCALE_FACTOR_1, LOAD_FUNC_1, INTERPOLATION, X_SCALE, Y_SCALE, X_SHIFT, Y_SHIFT, ASSEMBLY NR_OF_THREADS strain rate dependent airbag fabric properties COMMENT
Choose the number of thread definitions. KAPPA becomes available if a PERMEABILITY. MODEL is being used. REDUCTION_LIMIT_STRAI N becomes available when TENSION_ONLY is ON
MATERIAL.FOAM
Foam material
DENSITY, CHAR, ASSEMBLY strain rate dependent COMMENT
MATERIAL.HOLE
Hole material
HOLE.MODEL, BLOCK_FLOW, CDEX, DPEX, DTEX, DELTEX, SWITCH, SWITCH_SCALE, CDP_FUNC, CDT_FUNC, SCALE_FUNC, ASSEMBLY HOLE_AREA

Altair Engineering
HOLE_SUBSEGME NT COMMENT MATERIAL. HONEYCOMB Honeycomb material model with tri-linear stress-strain behaviour. DENSITY, E11_1, E11_2, E11_3, CMPFC_A1, E22_1, E22_2, E22_3, CMPFC_A2, E33_1, E22_2, E33_3, CMPFCA3, G12_1, G12_2, G12_3, CMPFC_A4, G23_1, G23_2, G23_3, CMPFC_A5, G31_1, G31_2, G31_3, CMPFC_A6, CMPFC_B, MAT_DIR, MAT_DIR (X), Y, Z, MAT_DIR_2(X), Y, Z, ASSEMBLY COMMENT MATERIAL. HONEYCOMB_PLA STIC Honeycomb material using plasticity formulation. DENSITY, MAT_DIR, MAT_DIR_1(X), Y, Z, MAT_DIR_2(X), Y, Z, E11, E22, E33, G12, G23, G31, CMPC_11_FUNC, CMPC_22_FUNC, CMPC_33_FUNC, CMPC_12_FUNC, CMPC_23_FUNC, CMPC_31_FUNC, INTERPOLATION, X_SCALE, Y_SCALE, X_SHIFT, Y_SHIFT, CMPC_VOLUME, E, NU, YIELD_STRESS, ASSEMBLY COMMENT MATERIAL.HYSISO Elastic isotropic material model with hysteresis. DENSITY, CHAR, TENSION_ONLY, ASSEMBLY KAPPA becomes available if a PERMEABILITY. MAT_DIR_1 and MAT_DIR_2 can be specified by either selecting one coordinate system or entering the components of both direction vectors. If a coordinate system was selected, the (local) directions of the X-axis and Y-axis are used as MAT_DIR_1 and MAT_DIR_2. MAT_DIR_1 and MAT_DIR_2 can be specified by either selecting one coordinate system or entering the components of both direction vectors. If a coordinate system was selected, the (local) directions of the X-axis and Y-axis are used as MAT_DIR_1 and MAT_DIR_2.
Altair Engineering

airbag fabric properties COMMENT MATERIAL. INTERFACE Material model for interface element. MAXTFN, AN, MAXTFS, AS, GMODE1, GMODE2, WINDOW, ASSEMBLY COMMENT MATERIAL.ISOLIN Linear elastic isotropic material DENSITY, E, NU, TENSION_ONLY, MU, DAMP_COEF, ASSEMBLY apply damage airbag fabric properties COMMENT MATERIAL.ISOPLA Isotropic elastoplastic material. DENSITY, E, YIELD_STRESS, NU, KAPPA, ASSEMBLY strain rate dependent hardening model apply damage airbag fabric properties COMMENT MATERIAL. KELVIN1D Linear 1-dimensional Kelvin material. STIF, DAMP_COEF, ASSEMBLY COMMENT MATERIAL. KELVIN1D_NL Non-linear 1-dimenional Kelvin CHAR, ASSEMBLY material. COMMENT Linear 3-dimensional Kelvin material D1_STIF, D2_STIF, D3_STIF, R1_STIF, R2_STIF, R3_STIF, D1_DAMP, D2_DAMP,
MODEL is being used.
KAPPA becomes available if a PERMEABILITY. MODEL is being used. REDUCTION_LIMIT_STRAI N becomes available when TENSION_ONLY is ON
KAPPA becomes available if a PERMEABILITY. MODEL is being used.
MATERIAL. KELVIN3D

Altair Engineering
D3_DAMP, R1_DAMP, R2_DAMP, R3_DAMP, ASSEMBLY COMMENT MATERIAL. KELVIN3D_NL Non-linear 3-dimensional Kelvin material. D1_CHAR, D2_CHAR, D3_CHAR, R1_CHAR, R2_CHAR, R3_CHAR, ASSEMBLY COMMENT MATERIAL.LINVIS Linear visco-elastic isotropic material. DENSITY, BULK, GINF, GD1, TAU1, GD2, TAU2, GD3, TAU3, GD4, TAU4, ASSEMBLY COMMENT MATERIAL. MOONRIV Mooney-Rivlin hyperelastic isotropic material (rubber materials). DENSITY, A, B, NU, MU, DAMP_COEF, ASSEMBLY COMMENT MATERIAL.NULL NULL material DENSITY_NULL, ASSEMBLY COMMENT MATERIAL. ORTHOLIN Linear elastic orthotropic material. DENSITY, E11, E22, G12, NU12, TENSION_ONLY, MAT_DIR, MAT_DIR (X), Y, Z, MU, DAMP_COEF, DAMPING apply damage airbag fabric properties COMMENT MAT_DIR can be specified by either selecting a coordinate system or entering the components of the direction vector. If a coordinate system was selected, the (local) direction of the X-axis is used as MAT_DIR. KAPPA becomes available if a PERMEABILITY. MODEL is being used.
Altair Engineering

REDUCTION_LIMIT_STRAI N becomes available when TENSION_ONLY is ON MATERIAL. ORTHOLIN_LAYER ED Linear elastic orthotropic layered material. COMMENT MAT_DIR can be specified by either selecting a coordinate system or entering the components of the direction vector. If a coordinate system was selected, the (local) direction of the X-axis is used as MAT_DIR. KAPPA becomes available if a PERMEABILITY. MODEL is being used. MATERIAL. ORTHOPLA Orthotropic elastic-plastic material based on Hill's yield condition. strain rate dependent MAT_DIR can be specified by either selecting a hardening model coordinate system or entering the components apply damage of the direction vector. If a coordinate system was airbag fabric selected, the (local) properties direction of the X-axis is COMMENT used as MAT_DIR. KAPPA becomes available if a PERMEABILITY. MODEL is being used. MATERIAL.RIGID MATERIAL. SANDWICH Rigid material Linear elastic orthotropic sandwich material. COMMENT COMMENT MAT_DIR can be specified by either selecting a coordinate system or entering the components of the direction vector. If a coordinate system was selected, the (local) direction of the X-axis is used as MAT_DIR.
MATERIAL.STRAP
Tension-only perfect elasticplastic material model with failure for straps. Tension-only elastic material
COMMENT
MATERIAL.TONER
COMMENT

Altair Engineering
with rupture. MATERIAL.USER MATERIAL. VISCO_NL PERMEABILITY User defined material model Non-linear visco-elastic isotropic material COMMENT COMMENT
Defined on the card of the parent MATERIAL. Defined on the card of the parent MATERIAL.
RATE
RUPTURE THREAD Definition of material properties via a characteristic specification for a thread (FABRIC material). Defined on the card of the parent MATERIAL.
MARC
Supported Card
Solver Description
Supported Parameters NoOfSets, UnitNo, NoOfTerms, DataInputMode, ModFlag, MassDen, CoeffThermExp, RefValueu, RefValuea, RefValueb, UNSUPPORTED_DA TA YieldCrit, HardRule, ConCrack, DataIndex, VisPlasParm, YoungMod, PoissRat, MassDensity, ThermExp, VonMises, HardType, CostPerVol,
Notes
MAT_FOAM
MAT_ISOTROPIC
Altair Engineering

CostPerMass, StrainRateData, WorkHardData, TempEffectData MAT_MOONEY NoOfSets, UnitNo, DataInputMode, RivConC10, RivConC01, MassDen, CoeffThermExp, HOrderC11, HOrderC20, HOrderC30, BulkMod, UNSUPPORTED_DA TA NoOfSets, UnitNo, NoOfTerms, ModelType, DataInputMode, BulkModK, MassDen, CoeffThermExp, RefValueu, RefValuea, UNSUPPORTED_DA TA NoOfSets, UnitNo, YieldCrit, HardRule, IANELSFLAG, DataReadType, DataIndex, VisPlasParm, YoungModE11, YoungModE22, YoungModE33, PoisRatV12, PoisRatV23, PoisRatV31, MassDen, ShearModG12, ShearModG23, ShearModG31, ThermExpA11, ThermExpA22, ThermExpA33,
MAT_OGDEN
MAT_ORTHOTROPI C

Altair Engineering
CostPerVol, CostPerMass, TenYStress, EqvYStress, YRDIR1_M, YRDIR2_C1, YRDIR3_C2, YRSHR1_C3, YRSHR2_C6, YRSHR3, UNSUPPORTED_DA TA, StrainRateData, WorkHardData, TempEffectData
Nastran
Some of the material data cards provided by Nastran can be created by loading and editing the appropriate card images. These card images have the same name as the corresponding cards. Supported Card Solver Description Supported Parameters MATS1 MATEP MATT1 MAT4 MAT5 MAT2 Defines the material properties for linear anisotropic materials for twodimensional elements. MATEP MATT2 MAT4 MAT5 MAT4 n/a 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 singlephase change. Notes
MAT1
Defines the material properties for linear isotropic materials.
Altair Engineering

MAT5
Defines the thermal material properties for anisotropic materials Defines the material property for an orthotropic material for isoparametric shell elements. Defines the material properties for linear, temperature-independent, anisotropic materials for solid isoparametric elements.
KXX, KYY, KXZ, KYY, KYZ, KZZ, CP, RHO, HGEN MATT8 MAT4 MAT5 MATEP MATT9 MAT4 MAT5
MAT8
MAT9
MAT10
Defines material properties for MAT4 fluid elements in coupled fluidMAT5 structural analysis. Specifies hyperelastic (rubber-like) material properties for nonlinear (large strain and large rotation) analysis in SOL 600 and MD Nastran SOL 400 only Specifies gasket material properties to be used in SOL 600 and MD Nastran SOL 400. MODEL, K, RHO, TEXP, TREF, GE, C10, C01, C20, C11, C30, TAB1, TAB2, TAB3, TAB4, TABD
MATHE
MATG
IDMEM, BEHAV, TABLD, TABLU, YPRS, EPL
MATHP
Specifies material properties n/a for use in fully nonlinear (i.e., large strain and large rotation) hyperelastic analysis of rubber-like materials (elastomers).
The PCOMP card contains all information regarding composite materials, including the orientation of the longitudinal direction of each ply. You can view each ply direction through the Composites panel. The material longitudinal axis of the element, shown in the Composites panel as elem orientation is obtained either by rotating the x axis of the element THETA degree (from THETA field in the element card) counterclockwise, or by projecting the x axis of a system (from MCID field in the element card) onto the surface of the element. Each ply orientation, shown in the Composites panel as ply direction, is obtained by rotating the material longitudinal axis THETAi degree (from the THETAi field in the PCOMP card) counterclockwise. PAM-CRASH 2G

Altair Engineering
Supported Card
Solver Description
Notes
MAT_SECURE PLY DENSITY, E11, E22, E33, G12, G23, G13, V12, V23, V13, Emtsi, Emts1, Emtsu, Dmts1, Dmtsu, Emtvi, Evmtv1, Emtvu, Dmtv1, Dmtvu, Eft, AlphaF, Efti, Eft1, Eftu, Dft1, Dftu, Ply model, Ply failure criteria, Strain rate Model Elastic Plastic Strain rate Model (no Post-Yield behavior strain rate, Cowper- defined by Yield Stress Symonds, Johnson- list box. Cook, ModifiedJones, Left Shifted, KrupKowsky) MAUX1 (None, ed) Yield Stress (Yield Stress, Point Curve, Curve, POWER, KRUPK, LOOKU, VOCEG) Hardening Type (None, AFCHA, OWANG) TYPE 2 Crushable Foam Strain rate Model (no strain rate, CowperSymonds, JohnsonCook, ModifiedJones, Left Shifted, KrupKowsky) MAUX1 (None, Ev, Pv, Edv) MAUX2 (None, Ev, Pv, Edv)
TYPE 1
Altair Engineering

MAUX3 (None, Ev, Pv, Edv) TYPE 5 Linear Viscoelastic Strain rate Model (no strain rate, CowperSymonds, JohnsonCook, ModifiedJones, Left Shifted, KrupKowsky) MAUX1 - MAUX6 (None, Exx, Eyy, Ezz, Exy, Eyz, Ezx, Exx+Eyy+Ezz, E1, E2, E3) TYPE 7 Isotropic - Elastic-PlasticHydrodynamic Strain rate Model (no strain rate, CowperSymonds, JohnsonCook, ModifiedJones, Left Shifted, KrupKowsky) MAUX1 - MAUX2 (None, Eint, Vol) TYPE 11 Blatz-Ko Rubber Strain rate Model (no strain rate, CowperSymonds, JohnsonCook, ModifiedJones, Left Shifted, KrupKowsky) MAUX1 - MAUX6 (None, Exx, Eyy, Ezz, Exy, Eyz, Ezx, Exx+Eyy+Ezz, E1, E2, E3) TYPE 16 Elastic-Plastic with Damage Strain rate Model (no strain rate, CowperSymonds, JohnsonCook, ModifiedJones, Left Shifted, KrupKowsky) MAUX1 - MAUX2 (None, d, ed) Yield Stress (Yield

Altair Engineering
Stress, Point Curve, Curve, POWER, KRUPK) TYPE 17 Hyperleastic Mooney-Rivlin Strain rate Model (no To enter LTC on card 4, a strain rate, Cowper- curve must exist. Symonds, JohnsonCook, ModifiedJones, Left Shifted, KrupKowsky) MAUX1 - MAUX6 (None, Exx, Eyy, Ezz, Exy, Eyz, Ezx, Exx+Eyy+Ezz, E1, E2, E3) TYPE 18 Hyperelastic Hart-Smith Strain rate Model (no strain rate, CowperSymonds, JohnsonCook, ModifiedJones, Left Shifted, KrupKowsky) MAUX1 - MAUX6 (None, Exx, Eyy, Ezz, Exy, Eyz, Ezx, Exx+Eyy+Ezz, E1, E2, E3) TYPE 20 Inelastic Crushable Foam Strain rate Model (no strain rate, CowperSymonds, JohnsonCook, ModifiedJones, Left Shifted, KrupKowsky) MAUX1 - MAUX6 (None, Pair, Ev, c) TYPE 21 Elastic Foam Strain rate Model (no Curve definition may be strain rate, Cowper- defined with points or with Symonds, Johnson- curve entities. Cook, ModifiedJones, Left Shifted, KrupKowsky) MAUX1 - MAUX6 (None, E1, E2, E3, Sigma1, Sigma2,
Altair Engineering

Sigma3, fe1, fe2, fe3, Ac, Ed1, Ed2, Ed3) Curve Flag (Single curve via points, Specify curves) TYPE 22 Non-linear Viscoelastic Strain rate Model (no strain rate, CowperSymonds, JohnsonCook, ModifiedJones, Left Shifted, KrupKowsky) MAUX1 - MAUX6 (None, Exx, Eyy, Ezz, Exy, Eyz, Ezx, Exx+Eyy+Ezz, E1, E2, E3, Ac) TYPE 25 Solid for Foam Side Impact Barriers Strain rate Model (no strain rate, CowperSymonds, JohnsonCook, ModifiedJones, Left Shifted, KrupKowsky) MAUX1 - MAUX5 (None, Pair, Ev, c, s, Ed) TYPE 26 Elastic Plastic with Gurson Damage Model Strain rate Model (no strain rate, CowperSymonds, JohnsonCook, ModifiedJones, Left Shifted, KrupKowsky) MAUX1 - MAUX5 (None, d, Ed) Yield Stress (Yield Stress, Point Curve, Curve, POWER, KRUPK) TYPE 30 Unidirectional Composite BiPhase DENSITY, NINT, To enter IPLY on card 3, a ISHG, IFROZ, QVIS, material collector with a C, defined PLY_DATA card

Altair Engineering
THERDATASETNUM image must exist. , TITLE, IPLY, EsLIM, NMIN Strain rate Model (no strain rate, CowperSymonds, JohnsonCook, ModifiedJones, Left Shifted, KrupKowsky) MAUX1 - MAUX6 (None, SigmaM11, SigmaM22, SigmaM33, SigmaM12, SigmaM23, SigmaM31, dF, dT, dsM, dvM, Exx, Eyy, Ezz, Exy, Eyz, Ezx) TYPE 31 Unidirectional Composite Non- DENSITY, NINT, linear ISHG, IFROZ, QVISC, THERDATASETNUM , TITLE, IPLY, EsLIM, NMIN, NMAIN, NUNLD, NRELD, Q1-Q3, E1E8, S1-S8 Strain rate Model (no strain rate, CowperSymonds, JohnsonCook, ModifiedJones, Left Shifted, KrupKowsky) MAUX1 - MAUX6 (None, SigmaM11, SigmaM22, SigmaM33, SigmaM12, SigmaM23, SigmaM31, dF, dT, dsM, dvM, Exx, Eyy, Ezz, Exy, Eyz, Ezx) TYPE 36 Elastic/Stiffening - Plastic with DENSITY, NINT, Failure ISHG, IFROZ, To enter IPLY on card 3, a material collector with a defined PLY_DATA card image must exist.
Altair Engineering

QVISC, THERDATASETNUM , TITLE, V, LC1-LC8, Erate1-Erate8, EtMAX, LC2, DampRatio, DampFreq, Q1-Q3 Strain rate Model (no strain rate, CowperSymonds, JohnsonCook, ModifiedJones, Left Shifted, KrupKowsky) MAUX1 - MAUX3 (None, Etmax, F1, Ed) TYPE 37 Viscoelastic Ogden Rubber DENSITY, NINT, ISHG, IFROZ, QVISC, THERDATASETNUM , TITLE, V, N, M, ShearMod1ShearMod8, Exponent1Exponent8, LTCuniaxial, LTCbiaxial, LTCpshear, LTCvolume, Q1-Q3 Strain rate Model (no strain rate, CowperSymonds, JohnsonCook, ModifiedJones, Left Shifted, KrupKowsky) MAUX1 - MAUX6 (None, Exx, Eyy, Ezz, Exy, Eyz, Ezx, Exx+Eyy+Ezz, E1E3) TYPE 41 Improved Side Impact Barrier TYPEerial DENSITY, NINT, Full material input and ISHG, IFROZ, simplified material input QVISC, are available THERDATASETNUM

Altair Engineering
, TITLE, EoT, EyT, E1T, E2T, GoTL, EyTL, G1TL, GyieldT, EoL, EyL, E1L, E2L, GoLW, EyLW, G1LW, GyieldL, EoW, EyW, E1W, E2W, GoWT, EyWT, G1WT, GyieldW, Ec, DampRatio, DampFreq, d1, du, Ei, E1, Eu, alpha, eps_d_off, eps_d_tens, eps_elim, Q1-Q3 Strain rate Model (no strain rate, CowperSymonds, JohnsonCook, ModifiedJones, Left Shifted, KrupKowsky) MAUX1 - MAUX6 (None, dmax, En, Es Exx, Eyy, Ezz, Exy, Eyz, Ezx, Ac, Edxx, Edyy, Edxy, Edyz, Edxz) TYPE 42 DENSITY, NINT, ISHG, IFROZ, QVISC, THERDATASETNUM , TITLE, EC_TT, AC_TT, ICUC_TT, MVC_TT, ASIC_TT, ESIC_TT, ALIC_TT, ELIC_TT, ET_TT, AT_TT, ICUT_TT, MVT_TT, ASIT_TT, ESIT_TT, ALIT_TT, ELIT_TT, EC_LL, AC_TT, ICUC_LL, MVC_LL, ASIC_LL, ESIC_LL, ALIC_LL, ELIC_LL, ET_LL, AC_TT, ICUT_LL, MVT_LL, ASIT_LL,
Altair Engineering

ESIT_LL, ALIT_LL, ELIT_LL, EC_WW, AC_TT, ICUC_WW, MVC_WW, ASIC_WW, ESIC_WW, ALIC_WW, ELIC_WW, ET_WW, AC_TT, ICUT_WW, MVT_WW, ASIT_WW, ESIT_WW, ALIT_WW, ELIT_WW, G_TL, AC_TT, ICU_TL, MVL_TL, ASI_TL, ESI_TL, ALI_TL, ELI_TL, G_LW, A_LW, ICU_LW, MVL_LW, ASI_LW, ESI_LW, ALI_LW, ELI_LW, G_TW, A_TW, ICU_TW, MVL_TW, ALI_TW, ESI_TW, ALI_TW, ELI_TW, DampRatio, DampFreq, D, p, Q1Q3, LCSTRAT, EVOLC, EVOLT, EVOMC, EVOMT, EVSLC, EVSLT, EVSMC, EVSMT, ESWITCH, NU_SWI, LCYILD, LCDAM, ISWITCH, ASWITCH TYPE 45 General Non-linear Strain Rate DENSITY, NINT, Dependent ISHG, IFROZ, QVISC, THERDATASETNUM , TITLE, E, Alpha, Hydro, DampRatio, SlMult, DampFreq, xratUI, iratExt, LCC1-LCC8, EC1EC8, LCT1-LCT8, ET1-ET8, LccUI, LctUI, Q1-Q3

Altair Engineering
Strain rate Model (no strain rate, CowperSymonds, JohnsonCook, ModifiedJones, Left Shifted, KrupKowsky) TYPE 52 Elastic-Plastic Solid with Fracture Criteria DENSITY, NINT, ISHG, IFROZ, QVISC, THERDATASETNUM , TITLE, G, Yield, Etan, K, ks, NF, LC, DampRatio, DampFreq, Gd_LC1, Gd_LC8, Gd_e1Gd_e8, Gs_LC1Gs_LC8, Gs_e1Gs_e8 Strain rate Model (no strain rate, CowperSymonds, JohnsonCook, ModifiedJones, Left Shifted, KrupKowsky) MAUX1-MAUX6 (None, Plastric strain rate, Ductile damage contour, Shear damage contour, Overall damage contour, stress triaxiality factor, Shear stress factor) Yield Stress (Yield Stress, Point Curve, Curve, POWER, KRUPK, LOOKU) TYPE 61 Elastic-Plastic 8 Node Thick Shell DENSITY, NINT, ISHG, IFROZ, QVISC, THERDATASETNUM , TITLE, E, v, TRANSsh Strain rate Model (no
Altair Engineering

strain rate, CowperSymonds, JohnsonCook, ModifiedJones, Left Shifted, KrupKowsky) MAUX1-MAUX6 (None, Exx, Eyy, Exy, Eyz, Ezx, Ezz) TYPE 62 Elastic-Plastic for 8-Node Thick Shell Elements with Total Lagrangian Formulation NINT, ISHG, IFROZ, QVISC, THERDATASETNUM , TITLE, E, Yield, v, IFLAW, TRANSsh, E1-E7, Sig1-Sig7, RELIM, Sigi, Sigl, dl, Sigu, du, Epmax, StrLmt, DampRatio, DampFreq Strain rate Model (no strain rate, CowperSymonds, JohnsonCook, ModifiedJones, Left Shifted, KrupKowsky) MAUX1-MAUX6 (None, Exx, Eyy, Exy, Eyz, Ezx, Ezz, d, e, Sxx, Syy, Sxy, Syz, Szx, Szz) TYPE 71 Elastic-Plastic with EWK Damage and Failure DENSITY, NINT, ISHG, IFROZ, QVISC, THERDATASETNUM , TITLE, G, Yield, Etan, K, Dc, Rc, Plim, Alpha, Beta, Epmax, Di, D1, d1, Du, du, DampRatio, DampFreq, Q1-Q3 MAUX1-MAUX5 (None, Pair, Ev, c, s, Ed)

Altair Engineering
YieldStress (Yield Stress, Point Curve, Curve, POWER, KRUPK) TYPE 99 Null TYPEerial for Solid DENSITY, NINT, ISHG, IFROZ, QVISC, THERDATASETNUM , TITLE, E, v Strain rate Model (no strain rate, CowperSymonds, JohnsonCook, ModifiedJones, Left Shifted, KrupKowsky) TYPE 100 Null TYPEerial S, density, NINT, ISHG, IFROZ, QVISC, ITHDSNUM, TITLE Strain rate Model (no strain rate, CowperSymonds, JohnsonCook, ModifiedJones, Left Shifted, KrupKowsky) TYPE 101 Elastic S, density, NINT, ISHG, IFROZ, QVISC, ITHDSNUM, TITLE, E, v, MEMBRhrC, PLANEhrC, ROThrC, TRANSsh, DampRatio, DampFreq Strain rate Model (no strain rate, CowperSymonds, JohnsonCook, ModifiedJones, Left Shifted, KrupKowsky) TYPE 102 Elastic Plastic S, density, NINT, ISHG, IFROZ,
Altair Engineering

QVISC, ITHDSNUM, TITLE, E, Yield, v, MEMBRhrC, PLANEhrC, ROThrC, TRANSsh, E1-E7, Sig1-Sig7, EpMAX, REL_THIN, REL_THIC, DampRatio, DampFreq, EPMX, GRUC_VAL Strain rate Model (no strain rate, CowperSymonds, JohnsonCook, ModifiedJones, Left Shifted, KrupKowsky) YieldStress (Yield Stress, Point Curve, Curve, POWER, KRUPK) GRUC Option (EPMX, THIC, NONE) TYPE 103 Elastic Plastic S, density, NINT, ISHG, IFROZ, QVISC, ITHDSNUM, TITLE, E, Yield, v, MEMBRhrC, PLANEhrC, ROThrC, TRANSsh, E1-E7, Sig1-Sig7, EpMAX, REL_THIN, REL_THIC, DampRatio, DampFreq, EPMX, GRUC_VAL Strain rate Model (no strain rate, CowperSymonds, JohnsonCook, ModifiedJones, Left Shifted, KrupKowsky) YieldStress (Yield Stress, Point Curve,

Altair Engineering
Curve, POWER, KRUPK) GRUC Option ( EPMX, THIC, NONE) TYPE 105 Elastic Plastic with Isotropic Damage S, density, NINT, ISHG, IFROZ, QVISC, ITHDSNUM, TITLE, E, Yield, v, MEMBRhrC, PLANEhrC, ROThrC, TRANSsh, E1-E7, Sig1-Sig7, REL_THIN, Ei, E1, d1, Eu, du, EpMAX, EESL, DampRatio, DampFreq, EPMX, GRUC_VAL, REL_THIC Strain rate Model (no strain rate, CowperSymonds, JohnsonCook, ModifiedJones, Left Shifted, KrupKowsky) YieldStress (Yield Stress, Point Curve, Curve, POWER, KRUPK) GRUC Option (EPMX, DMG, THIC, NONE) TYPE 106 Elastic Plastic with Anisotropic Damage S, density, NINT, ISHG, IFROZ, QVISC, ITHDSNUM, TITLE, E, Yield, v, MEMBRhrC, PLANEhrC, ROThrC, TRANSsh, E1-E7, Sig1-Sig7, REL_THIN, Ei, E1, d1, Eu, du, EpMAX, EESL, DampRatio, DampFreq, DMG,
Altair Engineering

REL_THIC Strain rate Model (no strain rate, CowperSymonds, JohnsonCook, ModifiedJones, Left Shifted, KrupKowsky) YieldStress (Yield Stress, Point Curve, Curve, POWER, KRUPK) GRUC Option (EPMX, DMG, THIC, NONE) TYPE 107 S, density, NINT, ISHG, IFROZ, QVISC, ITHDSNUM, TITLE Strain rate Model (no strain rate, CowperSymonds, JohnsonCook, ModifiedJones, Left Shifted, KrupKowsky) TYPE 108 Anisotropic Elastic Plastic S, density, NINT, ISHG, IFROZ, QVISC, ITHDSNUM, TITLE, E, Yield, v, MEMBRhrC, PLANEhrC, ROThrC, TRANSsh, E1-E7, Sig1-Sig7, EpMAX, REL_THIN, DampRatio, DampFreq, LANK, G, F, N, EPMX, GRUC_VAL, REL_THIC Strain rate Model (no strain rate, CowperSymonds, JohnsonCook, ModifiedJones, Left Shifted,

Altair Engineering
KrupKowsky) YieldStress (Yield Stress, Point Curve, Curve, POWER, KRUPK) Orthotropic elasticity (Initial isotropic Young's modules, orthotropic stiffness derived from orthotropic plasticity law, orthotropic stiffness coefficients are provided) GRUC Option (EPMX, THIC, NONE) TYPE 109 S, density, NINT, ISHG, IFROZ, QVISC, ITHDSNUM, TITLE Strain rate Model (no strain rate, CowperSymonds, JohnsonCook, ModifiedJones, Left Shifted, KrupKowsky) TYPE 110 Super Elastic S, density, NINT, ISHG, IFROZ, QVISC, ITHDSNUM, TITLE, Ea, Em, nu, Hgm, Hgw, Hgq, As, Beta, Alpha, CURVE, LC1, LC2, Dr, F0 Strain rate Model (no strain rate, CowperSymonds, JohnsonCook, ModifiedJones, Left Shifted, KrupKowsky) TYPE 115 Elastic Plastic with Gurson S, density, NINT, TYPE 109 data will not be exported (not valid for PAM 2006 and aove)
Altair Engineering

Damage
ISHG, IFROZ, QVISC, ITHDSNUM, TITLE, E, Yield, v, MEMRhrC, PLANEhrC, ROThrC, TRANSsh, E1-E7, Sig1-Sig7, REL_THIN, RELIM, q1, q2, fi, fc, DampRatio, DampFreq, fn, Sn, En, Tn, EPMX, GRUC_VAL, REL_THIC Strain rate Model (no strain rate, CowperSymonds, JohnsonCook, ModifiedJones, Left Shifted, KrupKowsky) YieldStress (Yield Stress, Point Curve, Curve, POWER, KRUPK) GRUC Option (EPMX, DMG, THIC, NONE)
TYPE 116
Elastic Plastic with Isotropic Damage
S, density, NINT, ISHG, IFROZ, QVISC, ITHDSNUM, TITLE, E, Yield, v, MEMRhrC, PLANEhrC, ROThrC, TRANSsh, E1-E7, Sig1-Sig7, RELIM, Sigi, Sigl, dl, Sigu, du, Epmax, StrLmt, DampRatio, DampFreq, DMG, REL_THIC, E, Yield, E1-E7, Sig1-Sig7, Ei, El, Dl, Eu, Du Strain rate Model (no strain rate, CowperSymonds, Johnson-

Altair Engineering
Cook, ModifiedJones, Left Shifted, KrupKowsky) YieldStress (Yield Stress, Point Curve, Curve, POWER, KRUPK) GRUC Option (EPMX, DMG, THIC, NONE) YieldStress (Yield Stress, Point Curve, Curve, POWER, KRUPK) TYPE 117 S, density, NINT, ISHG, IFROZ, QVISC, ITHDSNUM, TITLE Strain rate Model (no strain rate, CowperSymonds, JohnsonCook, ModifiedJones, Left Shifted, KrupKowsky) TYPE 118 Anisotropic Elastic Plastic S, density, NINT, ISHG, IFROZ, QVISC, ITHDSNUM, TITLE, E, Yield, v, MEMRhrC, PLANEhrC, ROThrC, TRANSsh, E1-E7, Sig1-Sig7, Ft, RELIM, DampRatio, DampFreq, LANK, G, F, N, EPMX, GRUC_VAL, q1, q2, fi, fc, fn, Sn, En, Tn Strain rate Model (no strain rate, CowperSymonds, JohnsonCook, ModifiedJones, Left Shifted, KrupKowsky) Type 117 data will not be exported (not valid for Pam 2006 and above)
Altair Engineering

YieldStress (Yield Stress, Point Curve, Curve, POWER, KRUPK) GRUC Option (EPMX, DMG, THIC, NONE) TYPE 121 CRASH/FORMING, Non-linear S, density, NINT, Visco Elastic ISHG, IFROZ, QVISC, ITHDSNUM, TITLE, E, v, MEMRhrC, PLANEhrC, ROThrC, TRANSsh, CONST, k, m, h1, h2, w, tfil, Eref, EpMAX, REL_THIN, EppMAX, REL_THIC Strain rate Model (no strain rate, CowperSymonds, JohnsonCook, ModifiedJones, Left Shifted, KrupKowsky) G Sell model (CONST, CURVE) TYPE 126 Glass S, density, NINT, ISHG, IFROZ, QVISC, ITHDSNUM, TITLE, E, v, MEMRhrC, PLANEhrC, ROThrC, TRANSsh, sigmaC, Tf, DampRatio, DampFreq Strain rate Model (no strain rate, CowperSymonds, JohnsonCook, ModifiedJones, Left Shifted, KrupKowsky) TYPE 128 Anisotropic Elastic Plastic S, density, NINT, ISHG, IFROZ,

Altair Engineering
QVISC, ITHDSNUM, TITLE, E, YieldStress, v, MEMRhrC, PLANEhrC, ROThrC, TRANSsh, E1-E7, Sig1-Sig7, RELIM, Lc, NFIL, DEPS, DampRatio, DampFreq, G, F, N, m, Eos, ns, ms, Eod, nd, md, Er, r0, r45, r90, KH1, KH2, KH3, d, FLDS1FLDS4, FLDD1FLDD4, DFS1-DFS3, DFD1-DFD3, DFA1DFA2, SFS1-SFS3, SFD1-SFD3, SFK Strain rate Model (no strain rate, CowperSymonds, JohnsonCook, ModifiedJones, Left Shifted, KrupKowsky) YieldStress (Yield Stress, Point Curve, Curve, POWER, KRUPK, KINEM) Yield Criterion (Hill 1948, Hill 1990, Barlat 1991) TYPE 130 Multilayered Shell Elements S, density, NINT, ISHG, IFROZ, QVISC, ITHDSNUM, TITLE, DampRatio, DampFreq, NOPLY, MEMRhrC, PLANEhrC, ROThrC, TRANSsh, NMIN, DMG, GRUC_VAL, IFAIL, ERATIO, Ply#, Aux1-Aux48 Strain rate Model (no strain rate, CowperTo specify a ply database, a material collector with the PLY_DATA card image must exist in the database. Ply auxiliary variables default to blank and can be overridden.
Altair Engineering

Symonds, JohnsonCook, ModifiedJones, Left Shifted, KrupKowsky) GRUC Option (DMG, THIC, NONE) TYPE 131 Multilayered Shell Elements S, density, NINT, ISHG, IFROZ, QVISC, ITHDSNUM, TITLE, DampRatio, DampFreq, NOPLY, MEMRhrC, PLANEhrC, ROThrC, TRANSsh, NMIN, DMG, GRUC_VAL, IFAIL, ERATIO, Ply#, Aux1-Aux48 Strain rate Model (no strain rate, CowperSymonds, JohnsonCook, ModifiedJones, Left Shifted, KrupKowsky) GRUC Option (DMG, THIC, NONE) TYPE 132 Multilayered Shell Elements S, density, NINT, ISHG, IFROZ, QVISC, ITHDSNUM, TITLE, DampRatio, DampFreq, NOPLY, MEMRhrC, PLANEhrC, ROThrC, TRANSsh, NMIN, DMG, GRUC_VAL, IFAIL, ERATIO, Ply#, Aux1-Aux48 Strain rate Model (no strain rate, CowperSymonds, JohnsonCook, ModifiedJones, Left Shifted, KrupKowsky) GRUC Option (DMG, To specify a ply database, a material collector with the PLY_DATA card image must exist in the database. Ply auxiliary variables default to blank and can be overridden. To specify a ply database, a material collector with the PLY_DATA card image must exist in the database. Ply auxiliary variables default to blank and can be overridden.

Altair Engineering
THIC, NONE) TYPE 143 Elastic-Plastic with Elastic Stiffening S, density, NINT, ISHG, IFROZ, QVISC, ITHDSNUM, TITLE, v, MEMRhrC, PLANEhrC, ROThrC, TRANSsh, LC1-LC8, Erate1-Erate8, EtMAX, RELIM, LC2, DampRatio, DampFreq, EPMX, GRUC_VAL Strain rate Model (no strain rate, CowperSymonds, JohnsonCook, ModifiedJones, Left Shifted, KrupKowsky) Flag for unidirectional failure (possible in both local directions, not active; failure possible only in element local Xdirection; failure possible only in element local Ydirection) GRUC Option (EPMX, DMG, THIC, NONE) TYPE 150 Layered TYPEerials for Membrane Elements S, density, NINT, ISHG, IFROZ, QVISC, ITHDSNUM, TITLE, E, v, EcLIM, AREDUC, u, Edamp, IFLA90, E1, G1, Wrink1, E2, G2, Wrink2, MATLAW, LCLEAK Strain rate Model (no strain rate, CowperSymonds, Johnson-
Altair Engineering

Cook, ModifiedJones, Left Shifted, KrupKowsky) TYPE 151 Fabric Membrane Elements with Non Linear Fibre S, density, NINT, ISHG, IFROZ, QVISC, ITHDSNUM, TITLE, Edamp, AREDUC, G0h, PSI_lock, G1h, LCLOD1, H1, D1, eps_10, LCLOD2, H2, D2, eps_20, LCLEAK, LCSTRS, LCRAT1, LCRAT2, eps_i, eps_u, k0 Strain rate Model (no strain rate, CowperSymonds, JohnsonCook, ModifiedJones, Left Shifted, KrupKowsky) Effects of temperature THETA (not active, curve direction) Hysteresis model flag (exponenetial unloading Model A, unloading via slope to a curve Model B) TYPE 161 Elastic for 4-Node Thick Shell S, density, NINT, ISHG, IFROZ, QVISC, ITHDSNUM, TITLE, E, v, TRANSsh, PlStrFlg, DampRatio, DampFreq Strain rate Model (no strain rate, CowperSymonds, JohnsonCook, ModifiedJones, Left Shifted, KrupKowsky)

Altair Engineering
TYPE 162
Elastic Plastic with 4-Node Thick Shell
S, density, NINT, ISHG, IFROZ, QVISC, ITHDSNUM, TITLE, E, Yield, v, IFLAW, TRANSsh, E1-E7, Sig1-Sig7, RELIM, Sigi, Sigl, dl, Sigu, du, Epmax, StrLmt, DampRatio, DampFreq, DMG Strain rate Model (no strain rate, CowperSymonds, JohnsonCook, ModifiedJones, Left Shifted, KrupKowsky) Yield Stress (Yield Stress, Curve, POWER, KRUPK) GRUC Option (EPMX, DMG, THIC, NONE)
TYPE 171
Elastic Plastic with EWK Damage
S, density, NINT, ISHG, IFROZ, QVISC, ITHDSNUM, TITLE, E, Yield, v, MEMRhrC, PLANEhrC, ROThrC, TRANSsh, E1-E7, Sig1-Sig7, Di, D1, di, Du, du, DampRatio, DampFreq, tf/t, Dc, Rc, Plim, Apha, Beta Strain rate Model (no strain rate, CowperSymonds, JohnsonCook, ModifiedJones, Left Shifted, KrupKowsky) Yield Stress (Yield Stress, Curve, POWER, KRUPK) EWK Option (Critical
Altair Engineering

Damage, Parameter Identifier Activation) GRUC Option (EPMX, DMG, THIC, NONE) TYPE 200 Null TYPERerial density, NINT, ISHG, IFROZ, QVISC, THERDATASETNUM , TITLE, E Strain rate Model (No strain rate, Cowper-Symonds, Johnson-Cook, Modified-Jones, Left Shifted, KrupKowsky) TYPE 201 Elastic density, NINT, ISHG, Card fields vary depending IFROZ, QVISC, upon the element type THERDATASETNUM selected (beam or bar). , TITLE, E, Mdamp) Strain rate Model (No strain rate, Cowper-Symonds, Johnson-Cook, Modified-Jones, Left Shifted, KrupKowsky) Element Type (Bar, Beam) TYPE 202 Elastic-Plastic density, NINT, ISHG, IFROZ, QVISC, THERDATASETNUM , TITLE, E, Yield, Et, Mdamp, EpMAX) Strain rate Model (No strain rate, Cowper-Symonds, Johnson-Cook, Modified-Jones, Left Shifted, KrupKowsky) Yield Stress (Yield Card fields vary depending upon the element type selected. Post-Yield behavior - defined by Yield Stress list box.

Altair Engineering
Stress, Point Curve, Curve, POWER, KRUPK) TYPE 203 Nonlinear for BAR density, NINT, ISHG, Number of editable fields IFROZ, QVISC, depends on NLOAD, THERDATASETNUM NUNLD, and NRELD. , TITLE, Eo, Celim, Telim, Telas, Celas, NMAIN, NUNLD, NRELD) d1 - d8 MAIN f1 - f8 MAIN Strain rate Model (No strain rate, Cowper-Symonds, Johnson-Cook, Modified-Jones, Left Shifted, KrupKowsky) TYPE 204 Nonlinear for BAR/DASHPOT density, NINT, ISHG, IFROZ, QVISC, THERDATASETNUM , TITLE, NLOAD, Lmult, NUNLD, Umult, NDAMP, Dmult, NMULT, k, c, dinit, m, ko, Ft, Fc, Telim, Celim) Strain rate Model (No strain rate, Cowper-Symonds, Johnson-Cook, Modified-Jones, Left Shifted, KrupKowsky) Hysteresis Model Flag (Model A, B, or C) TYPE 205 Nonlinear Tension Only Bar density, NINT, ISHG, IFROZ, QVISC, THERDATASETNUM , TITLE, NLOAD, H, D, kP, DampRatio, NLOAD can be set to 0 or to a curve (right-click field label to reset NLOAD curve selection). Other fields for material type 205 Force-deflection curve specification requires existence of curves in the database.
Altair Engineering

Eo, Mu, E1, Eu) Strain rate Model (No strain rate, Cowper-Symonds, Johnson-Cook, Modified-Jones, Left Shifted, KrupKowsky) Hysteresis Model Flag for unloading/ reloading (Model A, B, or C) TYPE 212 Elastic-Plastic for Beam Elements
depend on the value of NLOAD.
density, NINT, ISHG, Post-Yield behavior IFROZ, QVISC, defined by Yield Stress THERDATASETNUM list box. , TITLE, E, v, Yield, Et, Mdamp, Bdamp, Tdamp, EpMAX, IFLAG Strain rate Model (No strain rate, Cowper-Symonds, Johnson-Cook, Modified-Jones, Left Shifted, KrupKowsky) Yield Stress (Yield Stress, Point Curve, Curve, POWER, KRUPK)
TYPE 213
Elastic-Plastic for Beam Elements
density, NINT, ISHG, IFROZ, QVISC, THERDATASETNUM , TITLE, E, v, Yield, Et, SF, Mdamp, Bdamp, Tdamp, EpMAX, IFLAG Strain rate Model (No strain rate, Cowper-Symonds, Johnson-Cook, Modified-Jones, Left Shifted,
Post-Yield behavior defined by Yield Stress list box. Specification of the cross section description through the list box affects the layout of cards 8 through NIPS 8.

Altair Engineering
KrupKowsky) Yield Stress (Yield Stress, Point Curve, Curve, POWER, KRUPK) TYPE 214 Global Beam Column density, NINT, ISHG, Curves must exist in the IFROZ, QVISC, model before specifying THERDATASETNUM curve fields. , TITLE, E, v, LCMS, LCMScale, LCMT, LCMTscale, Mdamp, Bdamp, Tdamp, LC1-LC8, M1-M8 Strain rate Model (No strain rate, Cowper-Symonds, Johnson-Cook, Modified-Jones, Left Shifted, KrupKowsky) TYPE 220 Nonlinear 6-DOF Spring/ Dashpot density, NINT, ISHG, Curves must exist in the IFROZ, QVISC, model before specifying THERDATASETNUM curve fields. , TITLE, NLOADR, FLTR, RUPLOW, RUPUPP, WALLOW, WALUPP, NCDOF, WDAMP, NUNLDR, FTUR, Mr, NDAMPR, FTDR, Kro, Frelas, NLOADS, NUNLDS, FTUS, Ms, NDAMPS, FTDS, Kso, Fselas, NLOADT, FTLT, RUPLOW, RUPUPP, WALLOW, WALUPP, NCDOF, WDAMP, NUNLDT, FTUT, Mt, NDAMPT, FTDT, Kto, Ftelas, MLOADR, FMLR,
Altair Engineering

RUPLOW, RUPUPP, WALLOW, WALUPP, NCDOF, WDAMP, MUNLDR, FMUR, lR, MDAMPR, FMDR, Kmro, Mrelas, MLOADS, FMLS, RUPLOW, RUPUPP, WALLOW, WALUPP, NCDOF, WDAMP, MUNLDS, FMUS, ls, MDAMPS, FMDS, Kmso, Mselas, MLOADT, FMLT, RUPLOW, RUPUPP, WALLOW, WALUPP, NCDOF, WDAMP, MUNLDT, FMUT, lt, MDAMPT, FMDT, Kmto, Mtelas Strain rate Model (No strain rate, Cowper-Symonds, Johnson-Cook, Modified-Jones, Left Shifted, KrupKowsky) Hysteresis Model Flag in r-direction (Model A, B, C) Hysteresis Model Flag in s-direction (Model A, B, C) Hysteresis Model Flag in t-direction (Model A, B, C) Hysteresis Model Flag in th1-direction (Model A, B, C) Hysteresis Model

Altair Engineering
Flag in th2-direction (Model A, B, C) Hysteresis Model Flag in th3-direction (Model A, B, C) TYPE 221 Spherical Joint Elements density, NINT, ISHG, Curves must exist in the IFROZ, QVISC, model before specifying THERDATASETNUM curve fields. , TITLE, MLOADR, FMLR, MUNLDR, FMUR, Cr, Mrelas, MLOADS, FMLS, MUNLDS, FMUS, Cs, Mselas, MLOADT, FMLT, MUNLDT, FMUT, Ct, Mtelas, MuR, MuS, MuT, Winit, Wfin, Ktrans, dtrans, ctrans Strain rate Model (No strain rate, Cowper-Symonds, Johnson-Cook, Modified-Jones, Left Shifted, KrupKowsky) Hysteresis Model Flag for rotation about r-axis (Model A, B, C) Hysteresis Model Flag for rotation about s-axis (Model A, B, C) Hysteresis Model Flag for rotation about t-axis (Model A, B, C) TYPE 222 Flexion Torsion Joint Elements density, NINT, ISHG, Curves must exist in the IFROZ, QVISC, model before specifying THERDATASETNUM curve fields. , TITLE, MLOADU,
Altair Engineering

FMLU, MUNLDU, FMUU, Cu, Muelas, MDIR, FDIR, MLOADT, FMLT, MUNLDT, FMUT, Ct, Mtelas, MuA, MuB, Winit, Wfin, Ktrans, dtrans, ctrans Strain rate Model (No strain rate, Cowper-Symonds, Johnson-Cook, Modified-Jones, Left Shifted, KrupKowsky) Hysteresis Model Flag for rotation about u-axis (Model A, B, C) Hysteresis Model Flag for rotation about t-axis (Model A, B, C) TYPE 223 Nonlinear 6-DOF Spring-Beam Elements density, NINT, ISHG, Curves must exist in the IFROZ, QVISC, model before specifying THERDATASETNUM curve fields. , TITLE, NLOADR, FTLR, RUPLOW, RUPUPP, NMFRDT, delRinit, INDOF, IDRUP, NUNLDR, FTUR, Mr, NDAMPR, FTDR, SLOPER, delRelas, NLOADS, FTLS, RUPLOW, RUPUPP, NMFSDT, delSinit, ILENGTH, NUNLDS, FTUS, Ms, NDAMPS, FTDS, SLOPES, delSelas, NLOADT, FTLT, RUPLOW, RUPUPP, NMFTDT, delTinit, NUNLDT, FTUT, Mt, NDAMPT,

Altair Engineering
FTDT, SLOPET, delTelas, MLOADR, FMLR, RUPLOW, RUPUPP, NMMRDT, thetaRinit, MUNLDR, FMUR, lr, MDAMPR, FMDR, SLOPER, delRelas, MLOADS, FMLS, RUPLOW, RUPUPP, NMMSDT, thetaSinit, MUNLDS, FMUS, ls, MDAMPS, FMDS, SLOPES, delSelas, MLOADT, FMLT, RUPLOW, RUPUPP, NMMTDT, thetaTinit, MUNLDT, FMUT, MDAMPT, FMDT, SLOPET, delTelas Strain rate Model (No strain rate, Cowper-Symonds, Johnson-Cook, Modified-Jones, Left Shifted, KrupKowsky) Hysteresis Model Flag in r-direction (Model A, B, C) Hysteresis Model Flag in s-direction (Model A, B, C) Hysteresis Model Flag in t-direction (Model A, B, C) Hysteresis Model Flag in th1-direction (Model A, B, C) Hysteresis Model Flag in th2-direction (Model A, B, C)
Altair Engineering

Hysteresis Model Flag in th3-direction (Model A, B, C) TYPE 224 6-DOF Penalty Spring Beam Elements density, NINT, ISHG, 6-DOF penalty spring IFROZ, QVISC, beam elements THERDATASETNUM , TITLE, SLFACMT, SLFACMR, SDMP1, XMASS, INERTIA, INDOF, IDRUPT, IFLGP Strain rate Model (No strain rate, Cowper-Symonds, Johnson-Cook, Modified-Jones, Left Shifted, KrupKowsky) TYPE 230 KineTYPEic Joint Elements density, NINT, ISHG, Curves must exist in the IFROZ, QVISC, model before specifying THERDATASETNUM curve fields. , TITLE, NLOADR1, muR1, vinit, vfinal, NUNLDR1, SLOPER1, NDAMPR1, delR1elas, NLOADS1, muS1, vinit, vfinal, NUNLDS1, SLOPES1, NDAMPS1, delS1elas, NLOADT1, muT1, vinit, vfinal, NUNLDT1, SLOPET1, NDAMPT1, delT1elas, MLOAD1, muTH1, ominit, omfinal, MUNLD1, SLOPE1, MDAMP1, TH1elas, MLOAD2, muTH2, ominit, omfinal, MUNLD2, SLOPE2, MDAMP2,

Altair Engineering
TH2elas, MLOAD3, muTH3, ominit, omfinal, MUNLD3, SLOPE3, MDAMP3, TH3elas Strain rate Model (No strain rate, Cowper-Symonds, Johnson-Cook, Modified-Jones, Left Shifted, KrupKowsky) Hysteresis Model Flag in r1-direction (Model A, B) Hysteresis Model Flag in s1-direction (Model A, B) Hysteresis Model Flag in t1-direction (Model A, B) Hysteresis Model Flag in th1-direction (Model A, B) Hysteresis Model Flag in th2-direction (Model A, B) Hysteresis Model Flag in th3-direction (Model A, B) TYPE 301 SLINK, ELINK elements or TIED interface. density, NINT, ISHG, IFROZ, QVISC, THERDATASETNUM , TITLE, SDMP1, SLFACM, FSVNL, DELTNL, IDEABEN, SDMPR, IDRUP, NTU, DSTART, DRELEA, RFAC Strain rate Model (No strain rate, Cowper-Symonds, Johnson-Cook,
Altair Engineering

Modified-Jones, Left Shifted, KrupKowsky) Flag for releasing rotational degrees of freedom (tying all 6 degrees of freedom, rotational degrees of freedom are not tied) Flag for tensile force orientation used in the rupture model (based on the slave position, based on the master segment normal) TYPE 302 PLINK elements. density, NINT, ISHG, IFROZ, QVISC, THERDATASETNUM , TITLE, SLFACM, FSVNL, DELTNL, STNOR, STTAN, IFLAGC, TOLCOR, IDRUP Strain rate Model (No strain rate, Cowper-Symonds, Johnson-Cook, Modified-Jones, Left Shifted, KrupKowsky) Flag for releasing rotational degrees of freedom (tying all 6 degrees of freedom, rotational degrees of freedom are not tied) TYPE 303 LLINK elements density, NINT, ISHG, IFROZ, QVISC, THERDATASETNUM , TITLE, SDMP1, SLFACM, IDEABEN, IDMOD, hcont, E0, G0, D, P, NFILT,

Altair Engineering
sPropage, yPropage, gM1, gM2, sStart, yStart, NCYCLE, GCONT Strain rate Model (No strain rate, Cowper-Symonds, Johnson-Cook, Modified-Jones, Left Shifted, KrupKowsky) Flag for releasing rotational degrees of freedom (tying all 6 degrees of freedom, rotational degrees of freedom are not tied) TYPE 304 TIED Interfaces density, NINT, ISHG, IFROZ, QVISC, THERDATASETNUM , TITLE, SDMP1, hcont, D, p, NFILT, IDEABEN, EC_NN, CELC_NN, ET_NN, CELT_NN, G_NT, CEL_NT, G_NU, CEL_NU, LKC_N, INC_N, INC_NT, INC_NU, LKT_N, INT_N, INT_NT, INT_NU, LK_NT, ITN_N, ITN_NT, ITN_NU, LK_NU, INU_N, INU_NT, INU_NU Strain rate Model (No strain rate, Cowper-Symonds, Johnson-Cook, Modified-Jones, Left Shifted, KrupKowsky) PLYDATA Only TSAI-WU failure criterion supported DENSITY, TITLE, E11, E22, E33, G12, G23, G13, v12, v23,
Altair Engineering

v13, Emtsi, Emts1, Emtsu, Dmts1, Dmtsu, Emtvi, Emtv1, Emtvu, Dmtv1, Dmtvu, Eft, AlphaF, Efti, Eft1, Eftu, Dft1, Dftu, E11, E22, E33, G12, G23, G13, v12, v23, v13, Emcsi, Emcs1, Emcsu, Dmcs1, Dmcsu, Emcvi, Emcv1, Emcvu, Dmcs1, Dmcsu, Efc, AlphaF, Efci, Efc1, Efcu, Dfc1, Dfcu Ply model (0: Unidirectional composite bi-phase, 1: Unidirectional composite global, 2: Isotropic elasticplastic damaging, 3: Anisotropic elasticplastic, 4: Anisotropic elasticplastic Hill 1990, 5: Hyperelastic Mooney-Rivlin, 6: Fabric composite biphase, 7: Fabric composite global Ply failure criteria ( None, Activates ply failure criterion on IBEG card) Strain rate Model (No strain rate, Cowper-Symonds, Johnson-Cook, Modified-Jones, Left Shifted, KrupKowsky) Type of ply failure model on IBEG card (Tsai Wu, Equivalent

Altair Engineering
shear strain, Hoffmann, Tsai Hill, Modified Puck, Maximum stress, Maximum Strain, 3invariants, User defined, Equivalent shear stress)
PERMAS
The following material data blocks are supported in the PERMAS interface: Supported Card Solver Description Supported Parameters Compressibility PLANE BEAM INPUT={TABLE/ DATA} DEP=TEMP $DAMPING Structural damping INPUT={TABLE/ DATA} Notes
$COMPRESS $CONDUCTIVITY
Fluid Compressibility Heat conductivity
$DENSITY $DIELECTRIC $ELASTIC
Material density Definition of dielectricity. Linear elastic material data Coefficient Material Property Type (General, Shell, Plane, Beam, Core) INPUT={TABLE/ DATA}
$ELCONDUCT
Definition of electric conductivity.
Coefficient
$ENTER MATERIAL Material input bracket header line
Altair Engineering

$FLDENS
Definition of fluid material density. Opens the bracket for definition of a fluid material Definition of material for gaskets Definition of the loading behavior for gasket material.
Density
$FLUID
$GASKET
$GSKLOAD
Temperature (Off/On) GSKLOADFIELDS Temperature (Off/On) GSKUNLOADFIELD S INPUT={TABLE/ DATA} INPUT={TABLE/ DATA} TYPE=ISO
$GSKUNLOAD
Definition of the unloading behavior for gasket material.
$HARDENING
Hardening
$HEATCAP
Heat capacity
$MATERIAL
Definition of homogenous material Definition of magnetic permeability. Plasticity data
$PERMEABILITY
Coefficient
$PLASTIC
PLANE INPUT={TABLE/ DATA}
$SURFABS
Definition of absorption at the boundary surface of a fluid.
INPUT={TABLE/ DATA}
$THERMEXP
Thermal expansion coefficients PLANE BEAM INPUT={TABLE/ DATA}
$VOLDRAG
Definition of volumetric drag of a fluid.
INPUT={TABLE/ DATA}

Altair Engineering
$YIELD
Yield limit
PLANE Criterion =VMISES/ TRESCA/DPAS/ MCAS/ DPNA/ MCNA/PMVMISES/ CASTIRON INPUT={TABLE/ DATA}
Samcef
The following material data blocks are supported in the Samcef interface: Supported Card Solver Description Supported Parameters BEHA ELASTIC YT H1111 H2211-H2222 H3311-H3333 H1211-H1212 H2311-H2323 H3111-H3123 AL1-AL3 M TREF Selection of strain/ stress measurement (KIRC, BIOT, CAUC) .MAT, ISOTROPIC Define the properties of one or several materials BEHA, ELASTIC E, NU, A, M MODULUS (YOUNGS MODULAS, BULK MODULUS) Selection of strain/ stress measurement (KIRC, BIOT, CAUC) Notes
.MAT, ANISOTROPIC
Define the properties of one or several materials
Altair Engineering

TREF .MAT, ORTHOTROPIC Define the properties of one or several materials BEHA ELASTIC E1-E3, G12, G23, G13, AL1-AL3, M Selection of strain/ stress measurement (KIRC, BIOT, CAUC)
See also Browsers HyperMesh Entities & Solver Interfaces Include Files Components Properties Element Property and Material Assignment Rules Model Setup

Altair Engineering
Laminates
Laminate entities are used to define laminates, which make up a laminated structure by defining the stacking sequence of ply entities that make up the laminated structure. There are three types of laminates which can be defined: ply laminates, sublaminates, and interface laminates. Ply laminates are used to define laminates which make up flat or slightly curved laminated structures. Ply laminates stack ply entities. The stack direction for the plies of a ply laminate is in the direction of the element's normal.
Sublaminates are very similar to ply laminates in that they also stack ply entities. However, they define only a portion of a laminate rather than a complete laminate structure. The stack direction for the plies of a sublaminate is defined by an interface definition within an associated interface laminate. However, the ply order defined within a sublaminate must remain in the defined order. An interface definition of an interface laminate defines which ply of the sublaminate is on top and which is on the bottom relative to the elements normal.
Altair Engineering

Interface laminates are used to define laminates which make up complex laminated structures that wrap around corners. Interface laminates stack sublaminates. The stack direction for the sublaminates of an interface laminate is in the direction of the element's normal. The exact stacking sequence of the plies of the sublaminates is defined by the interface definitions within an interface laminate. An interface definition defines which surface plies of two sublaminates touch, or interface, with each other. Each sublaminate stacked within an interface laminate must have at least one interface definition.

Altair Engineering
Laminates have an active and export state. The active and export states of laminate entities can be controlled using the Entity State Browser. The active state of a laminate controls the listing of the laminate in the Model Browser and any of its views. If a laminate entity is active, then it is listed in the Model Browser and any of its views. If a laminate entity is inactive, then it is not listed in the Model Browser or any of its views. The export state of a laminate entity controls whether or not that laminate is exported when the custom export option is utilized. The all export option is not affected by the export state of a laminate. The data names associated with laminates can be found in the data names section of the HyperMesh Reference Guide.
Solver Card Support for Laminates

RADIOSS (Bulk Data Format)
RADIOSS (bulk data format) STACK card is represented in HyperMesh as a laminate entity. Laminate entities are created and edited using the laminate create and edit dialogs from the Model Browser. Laminates control the stacking sequence of a set of defined plies.
Supported Card
Solver Description
Notes
STACK
Defines the stacking information
Can only be created
Altair Engineering

and stacking sequence for plybased composite definition.
and edited in the Laminate Editor from the Model Browser.
See also Browsers HyperMesh Entities & Solver Interfaces

Altair Engineering
Output Blocks
Output block entities are used to define and store solver output requests. Output blocks are shown under the OutputBlock folder within the Model Browser. Output blocks do not have a display state. Output blocks have an active and export state. The active state of a output block controls the listing of the output block in the Model Browser and any of its views. If a output block entity is active, then it is listed in the Model Browser and any of its views. If a output block entity is inactive, then it is not listed in the Model Browser or any of its views. The export state of a output block entity controls whether or not that set is exported when the custom export option is utilized. The all export option is not affected by the export state of a output block. The active and export states of output block entities can be controlled using the Entity State Browser. The data names associated with output blocks can be found in the data names section of the HyperMesh Reference Guide.
Altair Engineering

The following panels can be used to create and edit output blocks: Output Block
Solver Card Support for Output Blocks

The supported RADIOSS cards in RADIOSS 100 are listed below. You can quickly create these cards by right-clicking in the Solver Browser and selecting Create Cards.
Supported Card
Solver Description
Supported Parameters NUM_VARIABLES Var Keyword (ACCEL, SECTIO) RADIOSS_COMME NT_FLAG
Notes
/TH/ACCEL/
Describes the time history Accelerometer
Options to assign ATH... ITH
/TH/BEAM/
Describes the time history Beams Describes the time history Solids Describes the time history Cylindrical joints Describes the time history Frame NUM_VARIABLES Var RADIOSS_COMME NT_FLAG
Options to assign ATH... ITH Options to assign ATH... ITH Options to assign ATH... ITH Options to assign ATH... ITH
/TH/BRIC/
/TH/CYL_JO/
/TH/FRAME/
/TH/INTER/
Describes the time history Interface
NUM_VARIABLES Var Keyword (INTER, RWALL) RADIOSS_COMME NT_FLAG
/TH/MONV/
Describes the time history Monitored volume and Airbag
NUM_VARIABLES Var

Altair Engineering
RADIOSS_COMME NT_FLAG /TH/NODE/ Describes the time history Nodes NUM_VARIABLES lskew NODname RADIOSS_COMME NT_FLAG /TH/QUAD/ Describes the time history 2D quads Describes the time history Parts NUM_VARIABLES lskew Var RADIOSS_COMME NT_FLAG /TH/RBODY/ Describes the time history Rigid body Describes the time history Rigid wall NUM_VARIABLES Var Keyword (INTER, RWALL) RADIOSS_COMME NT_FLAG /TH/SECTIO/ Describes the time history Section NUM_VARIABLES Var Keyword (ACCEL, SECTIO) RADIOSS_COMME NT_FLAG /TH/SH3N/ Describes the time history - 3 node shells Describes the time history - 4 node shells NUM_VARIABLES Var ElName RADIOSS_COMME NT_FLAG Options to assign ATH... ITH Options to assign ATH... ITH Options to assign ATH... ITH Options to assign ATH... ITH Options to assign ATH... ITH Options to assign ATH... ITH Options to assign ATH... ITH Options to assign ATH... ITH
/TH/PART/
/TH/RWALL/
/TH/SHEL/
Altair Engineering

/TH/SPHCEL/
Describes the SPH cell output to time history. Describes the time history Springs Describes the time history Subsets NUM_VARIABLES Var RADIOSS_COMME NT_FLAG
Options to assign ATH... ITH Options to assign ATH... ITH Options to assign ATH... ITH
/TH/SPRING/
/TH/SUBS/
/TH/TRUSS/
Describes the time history Trusses
RADIOSS (Bulk Data Entry, OptiStruct)
Supported Card
Solver Description
Supported Parameters DEF ACCE VR AR XYZ
Notes
XHIST
Abaqus
An output block is a repository for output requests. Output blocks are added to load steps (*STEP) from the Load Steps panel. Output requests organized into the output blocks are written out within the corresponding step definition in the Abaqus input deck. It is recommended that all output requests be defined from the Step Manager in the Abaqus user profile.
Supported Card
Solver Description
Supported Parameters NSET FREQUENCY MASTER SLAVE
Notes
*CONTACT FILE
Define results file requests for contact variables

Altair Engineering
*CONTACT OUTPUT
Specify contact variables to be NSET written to the output database MASTER SLAVE VARIABLE = {ALL, PRESELECT} CPSET GENERAL CONTACT
*CONTACT PRINT
Define print requests for contact variables Define results file requests for element variables
NSET FREQUENCY ELSET FREQUENCY POSITION = {NODES, AVERAGED AT NODES, CENTROIDAL, INTEGRATION POINTS} DIRECTIONS LAST MODE MODE REBAR
*EL FILE
*EL PRINT
Define data file requests for element variables
ELSET FREQUENCY POSITION = {NODES, AVERAGED AT NODES, CENTROIDAL, INTEGRATION POINTS} SUMMARY TOTALS LAST MODE MODE
*ELEMENT OUTPUT
Define output database requests for element variables
DIRECTION ELSET POSITION =
Altair Engineering

{NODES, CENTROIDAL, INTEGRATION POINTS} VARIABLE = {ALL, PRESELECT} *ENERGY FILE Write energy output to the results file ELSET FREQUENCY ELSET VARIABLE = {ALL, PRESELECT} NSET FREQUENCY MASTER SLAVE SUMMARY TOTAL *INCREMENTATION Define output database OUTPUT requests for time incrementation data *INTEGRATED OUTPUT Specify variables integrated over a surface to be written to the output database VARIABLE = {ALL/ PRESELECT} Explicit template only. History data. Only for *OUTPUT, HISTORY. Only for *OUTPUT, HISTORY
*ENERGY OUTPUT Define output database requests for whole model or element set energy data *ENERGY PRINT Print a summary of the total energies
SECTION SURFACE VARIABLE = {ALL, PRESELECT} VARIABLE = ALL
*MODAL OUTPUT
Write generalized coordinate (modal amplitude) data to the output database during a mode-based dynamic or complex eigenvalue extraction procedure Define results file requests for nodal data
Standard 2D and 3D templates only. History data. Only for *OUTPUT, HISTORY.
*NODE FILE
NSET FREQUENCY GLOBAL LAST MODE MODE
*NODE OUTPUT
Define output database
NSET

Altair Engineering
requests for nodal data
GLOBAL VARIABLE = {ALL, PRESELECT}
*NODE PRINT
Define print requests for nodal variables
NSET FREQUENCY GLOBAL LAST MODE MODE SUMMARY TOTALS
*OUTPUT
Define output requests to the output database
FIELD HISTORY OP VARIABLE FREQUENCY TIME MARKS TIME INTERVAL NUMBER INTERVAL MODE LIST FILTER NAME
Note:
Output blocks must be added to the corresponding load steps for them to be written out to the Abaqus deck. All types of output requests in an output block are defined from the card image. The edit button in the panel displays the card image of the currently loaded output block. The entity selector buttons available in the Output Block panel are not useful for Abaqus. They should be ignored.
LS-DYNA
Data on LS-DYNA output blocks cannot be edited. Supported Card Solver Description Supported Parameters Notes
*DATABASE_HIST ORY_ BEAM(ID)
Describe time history for beam elements.
Altair Engineering

*DATABASE_HIST ORY_ BEAM_SET *DATABASE_HIST ORY_ DISCRETE *DATABASE_HIST ORY_ DISCRETE_SET *DATABASE_HIST ORY_ NODE(ID) *DATABASE_HIST ORY_ NODE_LOCAL(ID) *DATABASE_HIST ORY_ NODE_SET
Describe time history for beam element sets.
Describe time history for nodes.
LocalOption ID
Describe time history for nodes.
Describe time history for node sets.
LocalOption
*DATABASE_HIST Describe time history for node ORY_ sets. NODE_SET_LOCAL *DATABASE_HIST Describe time history for node ORY_ sets. NODE_SET_LOCAL (ID) *DATABASE_HIST ORY_ SEATBELT *DATABASE_HIST ORY_ SHELL *DATABASE_HIST ORY_ SHELL(ID) *DATABASE_HIST ORY_ Define time history on seat belt element.
CID REF n/a
ID
Describe time history for shell elements.
n/a
Describe time history for shell elements.
ID
Describe time history for shell element sets.

Altair Engineering
SHELL_SET *DATABASE_HIST ORY_ SOLID *DATABASE_HIST ORY_ SOLID(ID) *DATABASE_HIST ORY_ SOLID_SET *DATABASE_HIST ORY_ SPH *DATABASE_HIST ORY_ TSHELL *DATABASE_HIST ORY_ TSHELL(ID) *DATABASE_HIST ORY_ TSHELL_SET Describe time history for solid elements.
Describe time history for solid elements.
Describe time history for solid element sets.
Describe time history for SPH elements.
Describe time history for TSHELL elements.
Describe time history for TSHELL elements.
Describe time history for TSHELL element sets.
MADYMO
Supported Card
Solver Description
Notes
INITIAL
Defined on the card of the parent system.
INJURY OUTPUT_AIRBAG_ CHAMBER Airbag chamber output. AIRBAG_CHAMBE R FE_MODEL NR_OF_AIRBAG_C
Altair Engineering

HAMBERS SELECT.HEAT SELECT.INFLOW SELECT. INFLOW_PART SELECT.MASS SELECT. MASS_FLOW_RAT E SELECT. MASS_INFLOW_R ATE_PART SELECT. MASS_OUTFLOW_ RATE_PART SELECT_MOLAR_ FRACTIONS SELECT. OUTFLOW SELECT. OUTFLOW_HOLE SELECT. OUTFLOW_PART SELECT. OUTFLOW_PERM SELECT.PRES SELECT.TEMP SELECT. TEMP_INFLOW_P ART SELECT. TEMP_OUTFLOW_ PART SELECT.VOLUME COMMENT OUTPUT_ANIMATIO Finite element output for N animation. PART_LIST FE_MODEL SELECT.CONTACT SELECT.NODE SELECT.PRES

Altair Engineering
SELECT.STRAIN SELECT.STRESS SELECT.THICK COMMENT ANIMATION_GF AIRBAG_CHAMBE R_LIST FE_MODEL NR_OF_AIRBAG_C HAMBERS SELECT.COVER SELECT.DENS SELECT.MASS SELECT.PRES SELECT.TEMP SELECT. VEL_VECTOR COMMENT OUTPUT_BELT Belt output. INPUT_CLASS (BELT_SEGMENT, BELT_TYING, BELT_RETRACTO R) INPUT_REF EXTENDED (OFF/ ON) FILTER (NONE, CFC60, CFC180, CFC600, CFC1000, FIR100) ASSEMBLY, COMMENT OUTPUT_BODY Angular or linear body related output. SIGNAL_TYPE (ANG_VEL, ANG_ACC, LIN_DISP, LIN_POS, LIN_VEL, LIN_ACC) FILTER (NONE, CFC60, CFC180, CFC600, CFC1000, FIR100)
Altair Engineering

CRDSYS (REF_SPACE, OBJECT_1, OBJECT_2) CORRECT AX - AZ (OFF/ON) ASSEMBLY define CRDSYS_OBJECT _1.MB or select CRDSYS_OBJECT _1.REF? (OBJECT, REF) OUTPUT_BODY_R EL Output of a motion quantity of a SIGNAL_TYPE (REL_DISP, point on a body relative to a REL_POS, point on another body. DIST_VEL) FILTER (NONE, CFC60, CFC180, CFC600, CFC1000, FIR100) define POINT_OBJECT_1. MB or select POINT_OBJECT_1. REF? (OBJECT, REF) COMMENT OUTPUT_CONTACT Contact output. EXTENDED (OFF/ ON) FILTER (NONE, CFC60, CFC180, CFC600, CFC1000, FIR100) ASSEMBLY COMMENT OUTPUT_CONTROL Output of control system _ elements. SYSTEM INPUT_CLASS (CONTROLLER, SIGNAL, OPERATOR) INPUT_REF FILTER (NONE, CFC60, CFC180,

Altair Engineering
CFC600, CFC1000, FIR100) COMMENT OUTPUT_CROSS_ SECTION Defines a plane for which cross POS (X, Y, Z) sectional forces and moments NORMAL_DIR (X, are outputted. Y, Z) EDGE_DIR (X, Y, Z) LENGTH_L , LENGTH_M, FILTER (NONE, CFC60, CFC180, CFC600, CFC1000, FIR100) FE_MODEL OUTPUT_ELEMENT Element output. INT_POINT_LIST FILTER (NONE, CFC60, CFC180, CFC600, CFC1000, FIR100) FE_MODEL NR_OF_INT_POINT S SELECT. PROPERTY SELECT. PRES_EXTERNAL SELECT.STRESS SELECT.STRAIN SELECT. STRESS_TRUSS2 SELECT. STRAIN_TRUSS2 SELECT. STRESS_BEAM2 SELECT. STRAIN_BEAM2 SELECT. STRESS_INTERFA CE SELECT. STRAIN_INTERFAC
Altair Engineering

E COMMENT OUTPUT_ELEMENT Element output of initial state. _ INITIAL SELECT_FRAME (OFF/ON) SELECT_LUMP (OFF/ON) FE_MODEL COMMENT OUTPUT_ENERGY _FE_ MODEL Energy output of the FE models or its parts. FE_MODEL_LIST SUM_FE_MODEL (OFF/ON) ENERGY_ALL (OFF/ON) KINETIC (OFF/ON) DISSIPATION (OFF/ON) DISSIPATION_IMM (OFF/ON) DISSIPATION_MAT ERIAL (OFF/ON) DISSIPATION_PLA STIC (OFF/ON) DISSIPATION_RAY LEIGH (OFF/ON) INTERNAL (OFF/ ON) INTERNAL_PLASTI C (OFF/ON) INTERNAL_HOURG LASS (OFF/ON) INTERNAL_IMM (OFF/ON) EXTERNAL (OFF/ ON) EXTERNAL_CONT ACT (OFF/ON) EXTERNAL_FORC ES (OFF/ON) FE_PART (OFF/ ON)

Altair Engineering
TOTAL (OFF/ON) BALANCE (OFF/ ON) MASS_SCALING (OFF/ON) FILTER (NONE, CFC60, CFC180, CFC600, CFC1000, FIR100) NR_OF_FE_MODE LS COMMENT OUTPUT_JET Output of jet related properties. JET_LIST FE_MODEL NR_OF_JETS SELECT. FORCE_RES COMMENT OUTPUT_JOINT_ CONSTRAINT Joint constraint force or torque output. JOINT SIGNAL_TYPE (FORCE, TORQUE) FILTER (NONE, CFC60, CFC180, CFC600, CFC1000, FIR100) ASSEMBLY COMMENT OUTPUT_JOINT_DO Joint position, velocity or F acceleration degrees of freedom (DOF) output. JOINT SIGNAL_TYPE (POS, VEL, ACC) ASSEMBLY COMMENT OUTPUT_MARKER Marker output for animation. ASSEMBLY define CRDSYS_OBJECT _1.MB or select CRDSYS_OBJECT _1.REF (OBJECT, REF)
Altair Engineering

COMMENT OUTPUT_MOTION_ Data for creating a structural STRUCT motion output file. MOTION_TYPE (DISP, VEL) FILE FE_MODEL COMMENT OUTPUT_MUSCLE ASSEMBLY COMMENT OUTPUT_NODE Nodal output. FE_MODEL SELECT.POS SELECT.DISP SELECT.ROT SELECT.VEL SELECT.ACC SELECT.FORCE SELECT. FORCE_INTERNAL SELECT. FORCE_EXTERNA L SELECT. FORCE_REAC SELECT. MOMENT_REAC COMMENT OUTPUT_NODE_INI Nodal output of initial state. TIAL SELECT_POS (OFF/ON) SELECT_VEL (OFF/ON) SELECT_ACC (OFF/ON) SELECT_MASS (OFF/ON) FE_MODEL COMMENT OUTPUT_RESTRAI NT Restraint output. EXTENDED (OFF/ ON)

Altair Engineering
FILTER (NONE, CFC60, CFC180, CFC600, CFC1000, FIR100) ASSEMBLY COMMENT OUTPUT_SENSOR Sensor signal output. SENSOR ASSEMBLY COMMENT OUTPUT.STRAP FE_MODEL SELECT. FORCES_RES SELECT.ELONG SELECT. PROPERTY COMMENT OUTPUT_SYSTEM_ Position, velocity and COG acceleration output of the combined center of gravity of the selected system(s). WRITE_ALL WRITE_POS WRITE_VEL WRITE_ACC FILTER (NONE, CFC60, CFC180, CFC600, CFC1000, FIR100) ASSEMBLY COMMENT SELECT Defined on the card of the parent element. Rectangular plane multibody = BODY To create a SURFACE under the SYSTEM. N1 = POINT_1 REF_SPACE, a reference N2 = POINT_2 to a null body must be N3 = POINT_3 selected because HyperMesh requires a reference to a multibody when creating a multibody plane. A null body can be created like any other BODY (card image is not
SURFACE.PLANE
Altair Engineering

relevant and should not be used), Nullbody should be put under the SYSTEM. REF_SPACE assembly.
PAM-CRASH 2G
Keyword selection for output blocks is supported as GES selection. The appropriate keyword is output when selecting elements for time-history output. Supported Card Solver Description Supported Parameters Notes
PLANE SECFO / Section definition for force output Transmission forces are supported through the Interfaces panel. Slave nodes and master elements define the cross section. To define nonshell elements, create an entity set first. The master definition must be by sets.
SECTION SENPT / SENPTG / SUPPORT THELE / Element time history TITLE Uses element output Definition Mode (Use block. EntityId List, Define Using General Entity Selection) IFRAM ICORR IDAFLD In card previewer, a toggle switches between THLNO and THLOC. Additional input fields are shown in Sensor point output definition Sensor point output definition
THLOC /
Local frame definition for node output

Altair Engineering
TITLE GES Definition Mode (Use EntityId List, Define Using General Entity Selection) Coordinate System (Local System, Nodes N1 and N2) THNOD / Nodal time history TITLE GES Definition Mode (Use EntityId List, Define Using General Entity Selection) VOLFRAC
the card previewer for THLOC keyword.
Uses output block including nodes.
PERMAS
Supported Card
Solver Description
Supported Parameters PRIMARY={LIST/ EQUI/LOG/EIG/ FUNCTION} BOUNDS CLUSTER/GEOM DOFTYPE PRIMARY
Notes
$FREQUENCY
Definition of frequency list for frequency response analysis.
The FREQUENCY option is available in the results bracket.
$NLRESULTS
Output request for nonlinear static analysis
STEPS={ALL/EQUI/ INTERVAL/PERIOD/ LIST} KIND={ABS/RATIO} DOFTYPE
$TIMESTEPS
Specify specific time steps when results are written
KIND={ABS/RATIO} DOFTYPE
Altair Engineering

See also Browsers HyperMesh Entities & Solver Interfaces Include Files Properties Element Property and Material Assignment Rules Model Setup

Altair Engineering
Plots
Plot entities are used to associate and organize curve entities within a xy plot window. Plots can be created from and are shown under the Plot folder within the Model Browser. Plots have a display state, on or off, which controls the display of a xy plot window and all associated curve entities in the graphics area. The display state of a plot can be controlled using the icon next to the plot entity in the Model Browser. Plots also have an active and export state. The active state of a plot controls the display state of the plot and the listing of the plot and all associated curves in the Model Browser and any of its views. If a plot entity is active, then its display state is available to be turned on or off and the plot and its associated curves are listed in the Model Browser and any of its views. If a plot entity is inactive, then its display state is turned off permanently and the plot and its associated curves are not listed in the Model Browser or any of its views. The export state of a plot entity controls whether or not that plot and all associated curve entities are exported when the custom export option is utilized. The all export option is not affected by the export state of a plot. The active and export states of plot entities can be controlled using the Entity State Browser. The data names associated with plots can be found in the data names section of the HyperMesh Reference Guide.
Altair Engineering

The following panels can be used to edit plots: Plots Axis Scaling Axis Labels Grid Attribs Grid Labels Plot Titles Legend Border

Altair Engineering
See also Browsers HyperMesh Entities & Solver Interfaces Include Files Curves Model Setup XY Plotting
Altair Engineering

Plies
Ply entities are used to define an FEA ply which is the FEA correlation to a physical ply. Physical plies are used to manufacture laminates which make up composite structures. A physical ply has attributes of material, shape (area), thickness, and fiber orientation; where its shape is any complex flat pattern that can be cut from a roll of material. Similarly, an FEA ply is composed of the same data attributes as a physical ply (material, shape/area, thickness, and fiber orientation) except that its shape can only be approximated from the elements which most closely represent its actual complex shape. The data attributes of an FEA ply are defined in the figures below. The shape (area) of an FEA ply is defined by selecting elements which most closely represent the complex shape of a physical ply. In the example below, an elliptical physical ply shape is defined by the brown line. The corresponding FEA ply shape is defined by the gray shaded elements of the associated FEA mesh. Typically, if an element's centroid exists within the bounds of the physical ply shape, that element is considered part of the FEA ply shape.
The ply thickness is typically defined as the final cured thickness of a single ply of material as shown below. In addition, the ply can be made of any material: isotropic, orthotropic, anisotropic, or any other material law.
The fiber orientation of a ply defines the direction fibers lay within that ply. The ply fiber orientation is

Altair Engineering
typically an integer value between -90 and 90. The fiber orientation of a ply is always defined relative to each elements material direction using right hand rule around the elements normal, or thru-thickness direction, to define positive angles. Even though a ply's fiber orientation is a constant integer, element material directions can vary from element to element, and this allows varying fiber directions within a ply to be modeled. Element material directions are defined differently from solver to solver, and can be defined in the HyperMesh Composites panel.
Once all the plies which make up a composite structure are defined, just as in the actual hand-layup manufacturing process, plies are stacked in a specific given order within the laminate entity to define a laminate of the structure. Plies have a display state, on or off, which controls the display of a ply in the graphics area. The display state of a ply can be controlled using the icon next to the ply entity in the Model Browser. In addition, in order for plies to be displayed on the screen, the composite layers visualization mode must be turned on. The composite layers visualization mode displays the layers within every element which have proper laminate definitions and composite properties assigned. Plies can be displayed in a traditional shell representation or in a 3D representation by turning on the appropriate element representation visualization mode. Both the element representation and composite layers visualization modes can be set on the visualization toolbar.
Plies also have an active and export state. These states of a ply entities can be controlled using the Entity State Browser The active state of a ply controls the listing of the ply in the Model Browser and any of its views. If a ply entity is active, then it is listed in the Model Browser and any of its views. If a ply entity is inactive, then it is not listed in the Model Browser or any of its views. The export state of a ply entity controls whether or not that ply is exported when the custom export option is utilized. The all export option is not affected by the export state of a ply. The data names associated with plies can be found in the data names section of the HyperMesh Reference Guide.
Altair Engineering

Solver Card Support for Plies

The RADIOSS (bulk data format) PLY card is represented in HyperMesh as a ply entity. Ply entities are created and edited using the ply create and edit dialogs from the Model Browser. Plies can be created from selection of individual elements or from predefined element sets which define the ply shape. Supported Card Solver Description Supported Parameters Notes
PLY
Defines the properties of a ply used in ply-based composite definition.
Can only be created and edited in the Ply Editor from the Model Browser.
See also Browsers HyperMesh Entities & Solver Interfaces

Altair Engineering
Properties
Property entities are used to define and store 1D, 2D, and 3D property definitions for a model. Properties are created, edited, deleted, and shown under the Property folder within the Model Browser. Properties also have a property view within the Model Browser. Properties do not have a display state, but they do have a "by property" visualization color mode which colors the model according to the colors assigned to each property based on element property relationships. The "by property" visualization color mode is automatically set when you enter the property view within the Model Browser. In addition, you can manually set the "by property" visualization color mode using the element color mode icon on the visualization toolbar. Element property relationships are user profile (solver interface) dependent and are described in the section Element Property and Material Assignment Rules. In general, when a component is assigned a property, that property assignment is applied to all elements collected by that component. The method of assigning properties at the component level is therefore referred to as indirect property assignment. Direct property assignment is performed directly on the elements themselves. Direct property assignments always take precedence over indirect property assignments.
Properties have an active and export state. The active state of a property controls the listing of the property in the Model Browser and any of its views. If a property entity is active, then it is listed in the Model Browser and any of its views. If a property entity is inactive, then it is not listed in the Model Browser or any of its views. The export state of a property entity controls whether or not that property is exported when the custom export option is utilized. The all export option is not affected by the export state of a property. The active and export states of property entities can be controlled using the Entity State Browser. The data names associated with properties can be found in the data names section of the HyperMesh Reference Guide.
Altair Engineering

Solver Card Support for Properties

RADIOSS (Block Format) has many properties and most of them are supported. In addition RADIOSS allows you to program your own properties (mostly for springs) that can be used in a simulation. In order to handle the unsupported and user defined RADIOSS properties, a separate card image called "PROP_UNSUPPORTED" has been introduced. Any unsupported property will be read with card image PROP_UNSUPPORTED with its ID and its

Altair Engineering
associativity with component preserved. You can also create the property in HyperMesh as well. In this card image, all property sub-options, parameters, and data lines are supported as simple text. HyperMesh does not check the validity or syntax of any data in this mode. You must manually check the validity of the data. No editing, updating, or review of the property data is intended. Also time step calculation, mass calculation, penetration check are not available for the component that refers to this property. The property is displayed in the Model Browser, Solver Browser, and in the Component table. The supported RADIOSS D00 cards in RADIOSS (Block Format) 5.1 and 9.0 are listed below. You can quickly create these cards by right-clicking in the Solver Browser and selecting Create Cards. Supported Card Solver Description Supported Parameters Notes
/ACCEL /ADMESH/SET
Defines accelerometers. Describes the adaptive meshing. Describes the failure models. Describes the Chang failure model. Failure for solid elements used to model welds. Describes the specific energy failure model. Describes the forming limit. Describes the Hashin failure model. Describes the failure criteria by Johnson-Cook failure model. Describes the Ladeveze failure model Describes the Puck failure model Describes the Spalling and Johnson-Cook failure model.
/FAIL /FAIL/CHANG
/FAIL/CONNECT
/FAIL/ENERGY
/FAIL/FLD /FAIL/HASHIN
/FAIL/JOHNSON
/FAIL/LAD_DAMA
/FAIL/PUCK
/FAIL/SPALLING
Altair Engineering

/FAIL/TBUTCHER
Describes the TulerTBUTCHER model.
/FAIL/TENSSTRAIN Describes the strain failure model. /FAIL/USER1, / FAIL/USER2 or / FAIL/USER3 /FAIL/WIERZBICKI Describes the user failure model.
Describes the BAO-XUEWierzbicki failure model. Describes the Wilkins failure model. Describes the XFEM (eXtended Finite Element Method) failure model. Describes the property sets. Describes the beam property set.
/FAIL/WILKINS
/FAIL/XFEM
/PROP /PROP/BEAM /PROP/TYPE3 /PROP/CONNECT /PROP/TYPE43 /PROP/FLUID /PROP/TYPE14 /PROP/INJECT1
Property for solid elements used to model welds.
Describes the general fluid property set.
Describes mass injected for each constituent gas. Describes molar fraction injected for each constituent gas and total mass injected. Describes the integrated beam property set.
/PROP/INJECT2
/PROP/INT_BEAM /PROP/TYPE18 /PROP/KJOINT /PROP/TYPE33
Describes the joint type spring.

Altair Engineering
/PROP/PLY /PROP/TYPE19 /PROP/POROUS /PROP/TYPE15 /PROP/RIVET /PROP/TYPE5 /PROP/SHELL /PROP/TYPE1 /PROP/SH_COMP /PROP/TYPE10 /PROP/SH_FABR /PROP/TYPE16 /PROP/SH_ORTH /PROP/TYPE9 /PROP/SH_PLY /PROP/TYPE19
Defines the ply property set used in ply-based composite definition. Describes the porous solid element property set (extended Darcy's law). Describes the rivet property set.
Describes the shell property set.
RADIOSS_COMME NT_FLAG
Defines the composite shell property set.
Defines the anisotropic layered shell property set Defines the orthotropic shell property.
This property set is used to define the ply property set used in ply-based composite definition. Defines the sandwich shell property set.
/PROP/ SH_SANDW /PROP/TYPE11 /PROP/SH_STACK /PROP/TYPE17 /PROP/SOLID /PROP/TYPE14 /PROP/SOL_ORTH /PROP/TYPE6
This property set is used to define the sandwich shell property set. Defines the general solid property set.
Describes the orthotropic solid property set.
Altair Engineering

/PROP/SPH /PROP/SPRING /PROP/TYPE4
Describes SPH property set. Defines the spring property set.
/PROP/SPR_BEAM Describes the beam type spring property set. /PROP/TYPE13 /PROP/SPR_GENE Describes the general spring property set. /PROP/TYPE8 /PROP/SPR_PRE /PROP/TYPE32 /PROP/SPR_PUL /PROP/TYPE12 /PROP/TRUSS /PROP/TYPE2 /PROP/TSHELL /PROP/TYPE20 /PROP/TSH_ORTH /PROP/TYPE21 /PROP/TYPE0 /PROP/VOID /PROP/USER /THERM_STRESS/ MAT User defined property Add thermal expansion property for RADIOSS material (shell and solid). type = line Defines the general thick shell property set. Describes the pre-tension spring property set.
Describes the pulley spring property set.
Defines the truss property set.
Defines the orthotropic thick shell property set.
Defines the void property set.

Altair Engineering
The property data cards for RADIOSS (Bulk Data) can be created by loading and editing card images into property collectors. Properties can be assigned to components or elements.
Supported Card
Solver Description
Notes
PAABSF
Defines the properties of a frequency-dependent acoustic absorber element. Defines the properties of the acoustic absorber element. Defines the properties of a simple beam (bar), which is used to create bar elements via the CBAR entry. CONT1 PBARX
PACABS
PBAR
PBARL
Defines the properties of a PBARX simple beam (bar) by crosssectional dimensions, which is used to create bar elements via the CBAR entry. Defines the properties of a beam that is used to create beam elements via the CBEAM entry. CONTINUATION LINE 2 CONTINUATION LINE 5 CONTINUATION LINE 6 PBEAMX
PBEAM
PBEAML
Defines the properties of a PBEAMX beam element by crosssectional dimensions that are used to create beam elements via the CBEAM entry. Defines the nominal property values for a generalized spring-and-damper structural element. K_LINE B_LINE GE_LINE M_LINE PBUSHT
PBUSH
PBUSH1D
Property with Springs_Gaps
SPRING_LINE
Altair Engineering

ID pool. PCOMP Defines the structure and properties of an n-ply composite laminate material. Defines the structure and properties of an n-ply composite laminate, allowing for global ply identification. Defines the properties of a composite laminate material used in ply-based composite definition. Defines properties of a contact interface. Defines a free convection boundary condition properties. Specifies the damping of a scalar damper element using defined CDAMP1 or CDAMP3 entry. Used to define the stiffness and stress coefficient of a scalar elastic element (spring) by means of the CELAS1 or CELAS3 entry. Defines properties of the gap U0_opts (AUTO) (CGAP or CGAPG) elements. KA_opts (AUTO, SOFT, HARD) KT_opts (AUTO) MU1_opts (STICK, FREEZE) CONT PMASS Defines the mass value of a scalar mass element (CMASS1 or CMASS3 entry). Defines the properties of a Exported in large field PCONTX Number_of_Plies Exported in large field format by optistructlf template. Exported in large field format by optistructlf template.
PCOMPG
Number_of_Plies
PCOMPP
PCONT
PCONV
PDAMP
PELAS
PGAP
PROD

Altair Engineering
rod, which is referenced by the CROD entry. PSHEAR Defines the properties of a shear panel. Defines the membrane, bending, transverse shear, and membrane-bending coupling of shell elements. MID2_opts MID3_opts CONT PSHELLX PSOLID Defines the properties of solid PSOLIDX elements. Referenced by CHEXA, CPENTA, CPYRA and CTETRA entries. Defines the properties of a thin-walled cylindrical tube element. Referenced by the CTUBE entry. Defines properties of a onedimensional viscous damping element (CVISC entry). Defines properties of connector (CWELD) elements. Defines properties for a HM_Spring element, as explained in Using HM_ELAS. DOF GE S
format by optistructlf template.
PSHELL
PTUBE
PVISC
PWELD
HM_ELAS
Note: Only one property definition is allowed on each property collector. For definitions like PMASS, which allow more than one definition on the same card, this is separated on import into four different cards. 1-D elements can be organized into components with 2-D and 3-D elements, and these component groupings are maintained on export and import. However, this usage is not recommended. To assign 1-D elements to property collectors, select the property collector from the property = field in the appropriate 1-D element panel. Abaqus
Altair Engineering

The following Abaqus keywords are supported as properties:
Supported Card
Solver Description
Supported Parameters ALPHA, COMPOSITE, Mass, CM_x1, CM_x2, Angle, l11, l22, l12 ELSET, SECTION No_auto_prefix_for_n ames, Use_long_names, Use_quotes, Density, Dependency, Poisson, Zero, RotaryIntertia, SectionType, Section_Axis, BMG_Mat, Centroid, ShearCenter, SectionPoints, Beam_Added_Inertia , Ignore_HyperBeam_ Section_Type TransverseShearStiff ness ELSET, MATERIAL, SECTION
Notes
*BEAM ADDED INERTIA
Define additional beam inertia.
*BEAM GENERAL SECTION
Specify a beam section when numerical integration over the section is not required.
Only one *BEAM GENERAL SECTION card is output per component. Therefore, the beam elements in each component must have the same cross-sectional properties. Sub-options *AXIAL, *BEAM ADDED INERTIA, *CENTROID, *SHEAR CENTER, *THERMAL EXPANSION and *TRANSVERSE SHEAR STIFFNESS are supported.
*BEAM SECTION
Specify a beam section when numerical integration over the section is required.
Only one *BEAM SECTION card is output per component. Therefore, a, b, t1-t4 the beam elements in No_auto_prefix_for_n each component must ames, have the same crossUse_long_names, sectional properties. Use_quotes, Temperature, Sub-options *BEAM Poisson, ADDED INERTIA and RotaryInertia, *TRANSVERSE SHEAR SectionType, STIFFNESS are Section_Axis, supported. Integration_Points, Beam_Added_Inertia , Ignore_HyperBeam_ Section_Type,

Altair Engineering
TransverseShearStiff ness *COHESIVE SECTION Specify element properties for cohesive elements. ELSET MATERIAL CONTROLS ORIENTATION RESPONSE= {TRACTION SEPARATION, CONTINUUM, GASKET} STACK DIRECTION = {1,2,3, ORIENTATION} THICKNESS= {GEOMETRY, SPECIFIED} *CONNECTOR SECTION Specify connector attributes for connector elements. ELSET BEHAVIOR ELIMINATION The following types are supported: Standard template: ACCELEROMETER, ALIGN, AXIAL, BEAM, BUSHING, CARDAN, CARTESIAN, CONSTANT VELOCITY, CVJOINT, CYLINDRICAL, EULER, FLEXION-TORSION, FLOW-CONVERTER, HINGE, JOIN, LINK, PLANAR, PROJECTION CARTESIAN, PROJECTION FLEXIONTORSION, RADIALTHRUST, RETRACTOR, REVOLUTE, ROTATION, SLIDE-PLANE, SLIPRING, SLOT, TRANSLATOR, UJOINT, UNIVERSAL, WELD, Explicit template: All listed above, as well as ROTATIONACCELEROMETER Sub-option *TRANSVERSE SHEAR STIFFNESS is supported.
Altair Engineering

*CONTACT DAMPING
Define viscous damping between contacting surfaces.
DEFINITION=DAMPI This card is a sub-option NG COEFFICIENT in the *SURFACE INTERACTION card image. ELSET NONLINEAR ORIENTATION DEPENDENCIES Only one *DASHPOT card is output per component. Therefore, the spring elements in each component must have the same properties. When the *DASHPOT card is written for DASHPOT1 elements, both dof1 and dof2 are written, but Abaqus only reads dof1. For DASHPOTA elements, choose the DASHPOTA option in the *DASHPOT card image.
*DASHPOT
Define dashpot behavior.
*ELEMENT PROPERTIES
OFFSET ORIENTATION THICKNESS
*EULERIAN SECTION
Define properties of Eulerian ELSET continuum elements, including the list of materials that may occupy the elements. NAME MASS Bulk_Mod Temp Dependency This option is used to define compressibility for the hydraulic fluid model. It can be used only in conjunction with the *FLUID BEHAVIOR option or the *FLUID PROPERTY option. This option is used to define the reference fluid density for fluid cavities. It
*FASTENER (SPOT Prescribe mesh-independent WELD) PROPERTY fastener properties. *FLUID BULK MODULUS Define compressibility for a hydraulic fluid.
*FLUID DENSITY
Specify hydrostatic fluid density.
Pressure Temperature

Altair Engineering
is applicable only for hydraulic and pneumatic fluids and should not be used for user-defined fluids. The *FLUID DENSITY option can be used only in conjunction with the *FLUID BEHAVIOR option or the *FLUID PROPERTY option. *FLUID EXPANSION Specify the thermal expansion Mean coefficient for a hydraulic fluid. Temp Zero Dependency This option is used to define thermal expansion coefficients for the hydraulic fluid model. It can be used only in conjunction with the *FLUID BEHAVIOR option or the *FLUID PROPERTY option. Sub-options *FLUID DENSITY, *FLUID EXPANSION, and *FLUID BULK MODULUS are supported.
*FLUID PROPERTY Define properties for hydrostatic fluid elements.
ELSET REF NODE TYPE AMBIENT NAME
*FRICTION
Specify a friction model.
ANISOTROPIC DEPENDENCIES DEPVAR ELASTIC SLIP EXPONENTIAL DECAY LAGRANGE PROPERTIES SLIP TOLERANCE ROUGH TAUMAX USER
This card is a sub-option in the *SURFACE INTERACTION card image. It is also supported as a separate card image to allow for it to be used as a sub-option of the *CONNECTOR FRICTION card (in *CONNECTOR BEHAVIOR).
*GAP
Specify clearance and local geometry for GAP-type elements.
ELSET
Only one *GAP card is output per component. Therefore, the gap
Altair Engineering

elements in each component must have the same properties. Not in Explicit template. *GASKET SECTION Specify element properties for gasket elements. ELSET MATERIAL BEHAVIOR ORIENTATION STABILIZATION STIFFNESS *JOINT Define properties for JOINTC elements. ELSET ORIENTATION Only one *JOINT card is output per component. Therefore, the spring elements in each component must have the same properties. The *SPRING and *DASHPOT cards in the *JOINT property behave the same way as the individual cards mentioned above. See the How do I section below for more information. Not in Explicit template. *MASS Specify a point mass. ELSET COMPOSITE ALPHA Only one *MASS card is output per component. Therefore, the mass elements in each component must have the same properties. Sub-option *HOURGLASS STIFFNESS is supported. Only in Standard templates.
*MEMBRANE SECTION
Specify section properties for membrane elements.
ELSET MATERIAL ORIENTATION NODAL THICKNESS POISSON CONTROLS
*NONSTRUCTURAL Specify mass contribution to
ELSET
For Abaqus Explicit

Altair Engineering
MASS
the model from nonstructural features.
UNITS = {TOTAL MASS, MASS PER VOLUME, MASS PER AREA, MASS PER LENGTH} DISTRIBUTION = {MASS PROPORTIONAL, VOLUME PROPORTIONAL}
template only
*PHYSICAL CONSTANTS
Specify physical constants.
ABSOLUTE ZERO SPL REFERENCE PRESSURE STEFAN BOLTZMANN UNIVERSAL GAS CONSTANT
*RIGID BODY
Define a set of elements as a rigid body and define rigid element properties.
ELSET REFNODE ANALYTICAL SURFACE ISOTHERMAL PIN NSET TIE NSET POSITION DENSITY NODAL THICKNESS OFFSET
For Analytical Rigid Surfaces, the ANALYTICAL SURFACE parameter should point to the corresponding ANALYTICAL_RIGID_SUR FACE group from the card image of the *RIGID BODY card.
*ROTARY INERTIA (no longer listed on panel)
Define rigid body rotary inertia. ELSET ALPHA COMPOSITE ORIENTATION
Only one *ROTARY INERTIA card is output per component. Therefore, the ROTARY1 elements in each component must have the same properties.
*SECTION CONTROLS
Specify section controls.
NAME WEIGHT FACTOR SECOND ORDER ACCURACY DISTORTION CONTROL
Altair Engineering

LENGTH RATIO HOURGLASS = {VISCOUS, COMBINED, ENHANCED, RELAXED STIFFNESS, STIFFNESS} KINEMATIC SPLIT = {CENTROID, AVERAGE STRAIN, ORTHOGONAL} ELEMENT DELETION INITIAL GAP OPENING MAX DEGRADATION VISCOSITY *SHELL GENERAL SECTION Define a general, arbitrary, elastic shell section. COMPOSITE: COMPOSITE, ELSET, DENSITY, CONTROLS, LAYUP, OFFSET, ORIENTATION, POISSON, SMEAR ALL LAYERS, STACK DIRECTION, SYMMETRIC, THICKNESS MODULUS, NODAL THICKNESS HOMOGENOUS: MATERIAL, ELSET, DENSITY, BENDING ONLY, CONTROLS, MEMBRANE ONLY, OFFSET, ORIENTATION, POISSON, STACK DIRECTION, THICKNESS MODULUS, NODAL THICKNESS USER: Sub-options *HOURGLASS STIFFNESS and *TRANSVERSE SHEAR STIFFNESS are supported.for Composite and Homogenous

Altair Engineering
USER, ELSET, DENSITY, CONTROLS, OFFSET, ORIENTATION, POISSON, STACK DIRECTION, THICKNESS MODULUS, NODAL THICKNESS, I PROPERTIES, PROPERTIES, UNSYMM, VARIABLES DIRECT: ELSET, DENSITY, BENDING ONLY, CONTROLS, MEMBRANE ONLY, OFFSET, ORIENTATION, POISSON, STACK DIRECTION, THICKNESS MODULUS, ZERO, DEPENDENCIES *SHELL SECTION Specify a shell cross-section. COMPOSITE: COMPOSITE, CONTROLS, ELSET, DENSITY, LAYUP, NODAL THICKNESS, OFFSET, ORIENTATION, POISSON, SECTION INTEGRATION, STACK DIRECTION, SYMMETRIC, TEMPERATURE, THICKNESS MODULUS HOMOGENOUS: MATERIAL, CONTROLS, ELSET, DENSITY, NODAL Sub-options *HOURGLASS STIFFNESS and *TRANSVERSE SHEAR STIFFNESS are supported.
Altair Engineering

THICKNESS, OFFSET, ORIENTATION, POISSON, SECTION INTEGRATION, STACK DIRECTION, TEMPERATURE, THICKNESS MODULUS *SOLID SECTION Specify element properties for solid, infinite, acoustic, and truss elements. COMPOSITE: COMPOSITE, CONTROLS, ELSET, LAYUP, ORIENTATION, STACK DIRECTION, SYMMETRIC HOMOGENOUS: CONTROLS, ELSET, MATERIAL, ORIENTATION, REF NODE *SPRING Define spring behavior. ELSET NONLINEAR ORIENTATION DEPENDENCIES Only one *SPRING card is output per component. Therefore, the spring elements in each component must have the same properties. When the *SPRING card is written for SPRING1 elements, both dof1 and dof2 are written, but Abaqus only reads dof1. For SPRINGA elements, choose the SPRINGA option in the *SPRING card image. *SURFACE BEHAVIOR Define alternative pressureoverclosure relationships for contact. NO SEPARATION PRESSUREOVERCLOSURE= HARD, EXPONENTIAL, LINEAR, TABULAR, AugmeNted This card is a sub-option in the *SURFACE INTERACTION card image. Sub-option *HOURGLASS STIFFNESS is supported. REF NODE - generalized plane strain and acoustic infinite elements

Altair Engineering
Lagrange, PENALTY *SURFACE INTERACTION Define surface interaction properties. NAME For Abaqus Explicit template, this card is defined as a group from the Interface panel.
*SURFACE SECTION *SURFACE SMOOTHING
Specify section properties for surface elements.
ELSET DENSITY
Create a surface smoothing NAME definition for contact interactions. It must be used in conjunction with the *CONTACT PAIR option. K23, K13, SCF Define transverse shear stiffness for beams and shells. This option must be used in conjunction with the *BEAM GENERAL SECTION option, the *BEAM SECTION option, the *COHESIVE SECTION option, the *SHELL GENERAL SECTION option, or the *SHELL SECTION option. The transverse shear stiffness defined with this option affects only the transverse shear flexible elements whose section properties are defined by the immediately preceding section option.
*TRANSVERSE SHEAR STIFFNESS
LS-DYNA
Supported Card
Solver Description
Supported Parameters PIDA, PIDB, CIDA, CIDB, JID, LCIDAL, LCIDG, LCIDBT, DLCIDAL, DLCIDG,
Notes
*CONSTRAINED_J OINT_ STIFFNESS_FLEXI ON-
Define optional rotational and translational joint stiffness for joints.
Altair Engineering

TORSION
DLCIDBT, ESAL, FMAL, ESBT, FMBT, SAAL, NSABT, PSABT Define optional rotational and translational joint stiffness for joints. PIDA, PIDB, CIDA, CIDB, JID, LCIDPH, LCIDT, LCIDPS, DLCIDPH, DLCIDDT, DLCIDPS, ESPH, FMPH, EST, FMT, ESPS, FMPS, NSAPH, PSAPH, NSAT, PSAT, NSAPS, PSAPS Options (Generalized, FlexionTorsion, Translational)
*CONSTRAINED_J OINT_ STIFFNESS_ GENERALIZED
*CONSTRAINED_J OINT_ STIFFNESS_ TRANSLATIONAL
Define optional rotational and translational joint stiffness for joints.
PIDA, PIDB, CIDA, CIDB, JID, LCIDX, LCIDY, LCIDZ, DLCIDX, DLCIDY, DLCIDZ, ESX, FFX, ESY, FFY, ESZ, FFZ, NSDX, PSDX, NSDY, PSDY, NSDZ, PSDZ CDAMP, FREQ, PIDRB, PSID PROPRUL, AREAEQ, DG_TYP, D_SIGY, D_ETAN, D_DG_PR, D_RANK, D_SN, D_SB, D_SS, D_EXSN, D_EXSB, D_EXSS, D_LCSN, D_LCSB, D_LCSS, MID, SGIY, ETAN, DG_PR, RANK, SN, SB, SS, EXSN, EXSB, EXSS, LCSN, LCSB, LCSS
*DAMPING_RELATI Apply damping relative to the VE motion of a rigid body. *DEFINE_CONNEC Define failure related TION_ parameters for solid element PROPERTIES spot weld failure by *MAT_SPOTWELD_DAIMLER CHRYSLER.

Altair Engineering
Number_of_Materials *EOS_GRUNEISEN Equation of state Form 4. (EOS 4) C, S1, S2, S3, GAMA0, A, E0, V0 Title Equation of state for 12 for modeling ideal gas. CV0, CP0, CL, CQ, T0, V0 Title *EOS_IGNITION_A Equation of state Form 7. ND_ GROWTH_OF_REA CTION_ IN_HE (EOS 7) A, B, XP1, XP2, FRER, G, R1 - R6, FMXIG, FREQ, GROW1, EM, AR1, ES1, CVP, CVR, EETAL, CCRIT, ENQ, TMP0, GROW2, AR2, ES2, EN, FMXGR, FMNGR Title *EOS_JWL (EOS 2) Equation of state Form 2. A, B, R1, R2, Omeg, E0, V0 Title *EOS_LINEAR_ POLYNOMIAL (EOS 1) Equation of state Form 1. c0 - c6, E0, V0 Define coefficients for linear polynomial EOS and initialize Title the initial thermodynamic state of the material. C0 - C6, E0, V0, LCID Title
*EOS_IDEAL_GAS (EOS 12)
*EOS_LINEAR_ Equation of state Form 6. POLYNOMIAL_WIT H_ ENERGY_LEAK (EOS 6) *EOS_PROPELLAN Equation of state Form 10. T_ Added to model airbag DEFLAGRATION propellants. (EOS 10)
A, B, XP1, XP2, FRER, G, R1, R2, R3, R5, R6, FMXIG, FREQ, GROW1, EM, AR1, ES1, CVP, CVR, CCRIT, ENQ, TMP0,
Altair Engineering

GROW2, AR2, ES2, EN, FMXGR, FMNGR Title *EOS_RATIO_OF_ POLYNOMIALS (EOS 5) Equation of state Form 5. A10 - A13, A20 A23, A30 - A33, A40 - A43, A50 - A53, A60 - A63, A70 A73, A14, A24, ALPH, BETA, E0, V0 Title *EOS_SACK_TUES Equation of state Form 3. DAY (EOS 3) A1, A2, A3, B1, B2, E0, V0 Title GAMA, E0, V0, EV1- EV10, C1 C10, T1 - T10 Title *EOS_TABULATED Equation of state Form 8. _ COMPACTION (EOS 8) E0, V0, EV1 - EV10, C1 - C10, T1 - T10, K1 - K10 Title NLD, NCR, MU1, MU2, IE0, EC0 Title Define hourglass and bulk viscosity properties which are referenced via HGID in the *PART command. IHQ, QM, IBQ, Q1, Q2, QB, QW Title
*EOS_TABULATED Equation of state Form 9. (EOS 9)
*EOS_TENSOR_P ORE_ COLLAPSE (EOS 11) *HOURGLASS
Equation of state Form 11.
*INTEGRATION_BE Define user defined through the LSD_NIP, RA, ISCT, AM thickness integration rules for K the beam element. Title *INTEGRATION_SH Define user defined through the LSID_NIP, ESOP, ELL thickness integration rules for FAILOPT

Altair Engineering
the shell element. *MAT_ADD_EROSI ON Many of the consitutive models in LS-DYNA do not allow failure and erosion. This option provides a way of including failure in these models although the option can also be applied to constitutive models of other failure/erosion criterion. Define cross sectional properties for beam, truss, discrete beam and cable elements.
Title ID, EXCL, MXPRES, MNEPS, MNPRES, SIGP1, SIGVM, MEXPS, EPSSH, SIGTH, IMPULSE, FAILTM Title
*SECTION_BEAM (TITLE)
ELFORM, SHRF, QR, CST, SCOOR, NSM, Area, ISS, ITT, IRR, SA, Title, Int_Rule_ID Options (Generic, Standard)
*SECTION_DISCRE Define spring and damper TE elements for translation and (TITLE) rotation.
DRO, KD, V0, CL, FD, CDL, TDL Title LCIDT, LCIDVOLR, LCIDVEL, NIDLC001, NIDLC002, NICDL003, IDIR, NumPtSrc, NODEID, VECID, ORIFAREA MIXTURE, Title
*SECTION_POINT_ SOURCE(TITLE)
Provides the inlet boundary condition for single gas flow (inflation potential) via a set of point source(s).
*SECTION_POINT_ Provides: (a) an element SOURCE_MIXTURE formulation for a solid ALE part (TITLE) of the type similar to ELFORM=11 of *SECTION_SOLID and (b) the inlet gas injection boundary condition for multiple-gas mixture in-flow via a set of point sources. *SECTION_SEATB ELT (TITLE) Define section properties for the seat belt elements.
LCIDT, LCIDVEL, NIDL001, NIDLC002, NIDLC003, IDIR, LCMDOT1 LCMDOT8, NumPtSrc, NODEID, VECID, ORIFAREA Title Title
Altair Engineering

*SECTION_SHELL (TITLE)
Define section properties for shell elements.
ELFORM, SHRF, NIP, PROPT, QR, ICOMP, SETYP, T1, NLOC, MAREA, EDGSET Options (NONE, ALE, EFG) Title, Int_Rule_ID, NonUniform Thickness
*SECTION_SHELL_ Define section properties for ALE shell elements. (TITLE)
ELFORM, SHRF, NIP, PROPT, QR, ICOMP, SETYP, T1, NLOC, MAREA, EDGSET, AFAC, BFAC, CFAC, DFAC, EFAC, START, END, AAFAC Title, Int_Rule_ID, NonUniform Thickness
*SECTION_SHELL_ Define section properties for EFG shell elements. (TITLE)
ELFORM, SHRF, NIP, PROPT, QR, ICOMP, SETYP, T1, NLOC, MAREA, EDGSET, DX, DY Title, Int_Rule_ID, NonUniform Thickness
*SECTION_SOLID (TITLE)
Define section properties for solid continuum and fluid elements.
ELFORM, AET Options (NONE, ALE, EFG) Title
*SECTION_SOLID_ ALE (TITLE)
ELFORM, AET, AFAC, BFAC, CFAC, DFAC, START, END, AAFAC Title

Altair Engineering
*SECTION_SOLID_ EFG (TITLE)
ELFORM, AET, DX, DY, DZ Title CSLH, HMIN, HMAX, SPHNI, DEATH, START Title
*SECTION_SPH
Define section properties for SPH particles.
*SECTION_TSHELL Define section properties for (TITLE) SPH particles.
ELFORM, SHRF, NIP, PROPT, QR, ICOMP Title
MADYMO
Supported Card
Solver Description
Supported Parameters C1 - C5 ASSEMBLY COMMENT
Notes
AMPLIFICATION. ABS_POLY
Deformation rate dependent amplification factor of the elastic load given by the following polynomial C1 + C2|v| + C3|v|2 + C4|v|3 + C5|v|4 where v is the deformation rate corresponding to the force model.
Choose FACTOR = ABS_POLY [ASSEMBLY] = reference to the parent, if not selected, will be written to the MADYMO assembly, which is the top level of the assembly hierarchy.
AMPLIFICATION. EXP
Deformation rate dependent amplification factor of the elastic load given by the following exponential function C1 + C2 (|v|/C3) C4 (C3 > 0) where v is the deformation rate corresponding to the force model.
C1 - C4 ASSEMBLY COMMENT
Choose FACTOR = EXP [ASSEMBLY] = reference to the parent, if not selected, will be written to the MADYMO assembly, which is the top level of the assembly hierarchy.
AMPLIFICATION. LOG
Deformation rate dependent amplification factor of the
C1 - C3 ASSEMBLY
Choose FACTOR = LOG [ASSEMBLY] = reference
Altair Engineering

elastic load given by the following logarithmic function C1 + C2 log(|v|/C3) ( |v| > C3, C3 > 0) C1 ( |v| < C3, C3 > 0) where v is the deformation rate corresponding to the force model. AMPLIFICATION. POLY Deformation rate dependent amplification factor of the elastic load given by the following polynomial 1 + C1 v + C2 v2 + C3 v3 + C4 v4 (v = 0, Ci = 0, i = 1, 2, 3, 4) 1/{1 - C1 v + C2 v2 - C3 v3 + C4 v4} (v < 0, Ci = 0, i = 1, 2, 3, 4) where v is the deformation rate corresponding to the force model. CHARACTERISTIC. CONTACT Supplies the data for describing a characteristic for a contact.
COMMENT
to the parent, if not selected, will be written to the MADYMO assembly, which is the top level of the assembly hierarchy.
C1 - C4 ASSEMBLY COMMENT
Choose FACTOR = POLY [ASSEMBLY] = reference to the parent, if not selected, will be written to the MADYMO assembly, which is the top level of the assembly hierarchy.
CONTACT_MODEL, HYS_MODEL, LOAD_FUNC, AMPLIFICATION, ASSEMBLY
TYPE = CONTACT [ASSEMBLY] = reference to the parent, if not selected, will be written to the MADYMO assembly, which is the top level of the assembly hierarchy. TYPE = LOAD [ASSEMBLY] = reference to the parent, if not selected, will be written to the MADYMO assembly, which is the top level of the assembly hierarchy. TYPE = MATERIAL [ASSEMBLY] = reference to the parent, if not selected, will be written to
CHARACTERISTIC. LOAD
Characteristic for restraints, belt segments and belt retractors defining loading, unloading, damping and hysteresis.
HYS_MODEL, CONTACT_MODEL, DAMP_COEF, LOAD_FUNC, DAMP_VEL_FUNC, AMPLIFICATION, ASSEMBLY HYS_MODEL, DAMP_COEF, LOAD_FUNC, DAMP_FUNC, ASSEMBLY
CHARACTERISTIC. MATERIAL
Characteristic for materials defining loading, unloading, damping and hysteresis.

Altair Engineering
the MADYMO assembly, which is the top level of the assembly hierarchy. LAYER Layer definition of material. Defined on the card of the parent property. SECTION AREA I11 I22 I33 Q22 Q33 INT_PNT FE_MODEL COMMENT PROPERTY. Solid circular beam crossBEAM2_CIRCULAR section. SECTION RADIUS INT_MTH (GLOBAL, GAUSS, LOBATTO, TRAPEZIUM) FE_MODEL PROPERTY. Two node spring element. BEAM2_DISCRETE PROPERTY. General beam cross-section. BEAM2_GENERAL SECTION FE_MODEL SECTION AREA I11 I22 I33 Q22 Q33 INT_PNT FE_MODEL PROPERTY. BEAM2_PIPE Closed thin-walled circular beam cross-section (pipe). SECTION RADIUS THICK Choose SECTION = PIPE Choose SECTION = DISCRETE Choose SECTION = GENERAL Choose SECTION = CIRCULAR Choose SECTION = BOX
PROPERTY. BEAM2_BOX
Closed thin-walled rectangular beam cross-section.
Altair Engineering

INT_MTH (GLOBAL, GAUSS, LOBATTO, TRAPEZIUM) INT_POINTS FE_MODEL PROPERTY. Solid rectangular beam crossBEAM2_RECTANG section. ULAR WIDTH HEIGHT INT_MTH (GLOBAL, GAUSS, LOBATTO, TRAPEZIUM) INT_POINTS FE_MODEL PROPERTY. BEAM2_USER User defined beam crosssection. SECTION LOCAL_Y LOCAL_Z WEIGHT_FACTOR FE_MODEL NR_OF_USER_INTS PROPERTY. FACET6 THICK INT_POINT UPDATE_THICK (OFF/ON) FE_MODEL COMMENT PROPERTY. INTERFACE4 Linear four node interface element. THICK FE_MODEL COMMENT PROPERTY.MEM3 Linear three node triangular membrane element. THICK UPDATE_THICK (OFF/ON) IMM_DAMP IMM_STRAIN IMM_DAMP_MTH (0, 1, 2) IMM_STIF_REDUC COROTATION_FOR M (FIXED, Choose SECTION = USER Enter the number of related elements with user defined integration information. Choose SECTION = RECTANGULAR

Altair Engineering
OBJECTIVE) STRAIN_FORM (LINEAR, LOG, GREEN) FE_MODEL COMMENT PROPERTY. MEM3_LAYERED Linear three node layered triangular membrane element. IMM_DAMP IMM_STRAIN IMM_DAMP_MTH (0, 1, 2) IMM_STIF_REDUC COROTATION_FOR M (FIXED, OBJECTIVE) STRAIN_FORM (LINEAR, LOG, GREEN) UPDATE_THICK (OFF/ON) THICK COMPONENT ANGLE FE_MODEL display_components NR_OF_LAYERS COMMENT PROPERTY. MEM3NL Non-linear three node triangular membrane element. THICK IMM_DAMP IMM_STRAIN UPDATE_THICK (OFF/ON) IMM_DAMP_MTH (0, 1, 2) IMM_STIF_REDUC FE_MODEL COMMENT PROPERTY. MEM3NL_LAYERE Linear three node layered triangular membrane element. IMM_DAMP IMM_STRAIN Enter the number of related LAYER elements. Enter the number of related LAYER elements.
Altair Engineering

UPDATE_THICK (OFF/ON) IMM_DAMP_MTH (0, 1, 2) IMM_STIF_REDUC THICK COMPONENT ANGLE FE_MODEL display components NR_OF_LAYERS COMMENT
PROPERTY.MEM4
Linear quadrilateral membrane element.
THICK UPDATE_THICK (OFF/ON) HOURGLASS_PAR HOURGLASS_MTH (STIFFNESS, VISCOUS) FULL_INT (OFF/ON) IMM_DAMP IMM_STRAIN IMM_DAMP_MTH (0, 1, 2) IMM_STIF_REDUC COROTATION_FOR M (FIXED, OBJECTIVE) STRAIN_FORM (LINEAR, LOG, GREEN) FE_MODEL COMMENT
PROPERTY. MEM4NL
Non-linear quadrilateral membrane element.
THICK UPDATE_THICK (OFF/ON) HOURGLASS_PAR HOURGLASS_MTH (STIFFNESS,

Altair Engineering
VISCOUS) FULL_INT (OFF/ON) IMM_DAMP IMM_STRAIN IMM_DAMP_MTH IMM_STIF_REDUC FE_MODEL COMMENT PROPERTY. SHELL3 Three-node shell element. THICK INT_POINT UPDATE_THICK TIME_STEP_DEL FE_MODEL COMMENT PROPERTY. SHELL4 Shell4 element. THICK INT_POINT UPDATE_THICK HOURGLASS_PAR HOURGLASS_MTH (STIFFNESS, VISCOUS) TIME_STEP_DEL COMMENT PROPERTY. Linear four node layered SHELL4_LAYERED quadrilateral shell element. HOURGLASS_PAR HOURGLASS_MTH (STIFFNESS, VISCOUS) THICK COMPONENT ANGLE INT_POINT FE_MODEL display_components NR_OF_LAYERS COMMENT PROPERTY. Six node triangular shell THICK Enter the number of related LAYER elements.
Altair Engineering

SHELL6
element.
INT_POINT UPDATE_THICK (OFF/ON) BENDING_COUPLIN G (OFF/ON) FE_MODEL COMMENT
PROPERTY. SOLID4
Four node solid element.
ADV_STRAIN (OFF/ ON) FE_MODEL COMMENT
PROPERTY. SOLID8
Eight node solid element.
HOURGLASS_PAR FULL_INT (ON/OFF) ADV_STRAIN (ON/ OFF)
PROPERTY. TRUSS2
Property definition truss2 element.
AREA LENGTH FE_MODEL COMMENT
PROPERTY. USERL2 PROPERTY. USERL3 PROPERTY. USERP3 PROPERTY. USERP4 PROPERTY. USERV8 USER_INT
User element
FE_MODEL COMMENT
User element
FE_MODEL COMMENT
User element
FE_MODEL COMMENT
User element
FE_MODEL COMMENT
User element
FE_MODEL COMMENT
User-defined integration information for general beam cross section.
Defined on the card of the parent PROPERTY.
MARC

Altair Engineering
Supported Card
Solver Description
Notes
PBUSH PROP_GEOMETRY IOFFSET (0, 1, 2) IORIENT (0, 10) IPIN (0, 100) EGEOM1 EGEOM7 UNSUPPORTED_D ATA
Nastran
Only one card image can be loaded into each property collector. 1-D elements can be grouped into components with 2-D and 3-D elements for display purposes. The component groupings are maintained on export and import. To assign 1-D elements to property collectors, select the property collector from property = in the appropriate 1-D element panel. Properties for PBAR and PBEAM cards can be manually input in the card image or automatically created using the HyperBeam module. See the HyperBeam online help for more information. The HM_ELAS card defines properties for an HM_Spring element. Note: Nastran users should consider using the PBUSH property card instead of HM_ELAS.
The spring entity is a single DOF and single spring constant finite-length element. HM_ELAS property cards can be used to convert single spring elements into a group of zero-length springs and rigids. Six DOFs are defined in a single property card, and the springs in this group are created as zero-length to avoid some of the common modeling errors caused by finite-length springs. The following diagram illustrates how a single HM_ELAS spring element converts to a Nastran bulk data file:
Altair Engineering

As shown above, the single spring element writes a group of rigids and springs. On export, the following occurs: 1. 2. 3. A new node is created (Node 3) which is coincident with Node 2. The new node references the same local coordinate system as Node 2. An RBE2 element is created, with 6 DOFS fixed, between Node 1 and Node 3. Up to six zero-length elements are created, between Node 2 and Node 3, based on the following settings in the HM_ELAS property card: 4. If the DOF is a value you set, a CELAS2 element is created for that DOF, with the K field equal to the supplied value If the DOF is set to RIGID, an RBE2 element is created, with that DOF fixed If the DOF is set to FREE, no elements are created for that DOF
Comment cards are written at the beginning and end of each HM_SPRING (HMSPRING) element so that the element can be imported correctly in the session. These comment cards suppress the reading of the individual CELAS2 and RBE2 elements and the third "artificial" nodes so that you are left with the two original nodes and a single spring element once the bulk data file is loaded back into HyperMesh. Removing these comment cards allows you to load the elements back into HyperMesh the way Nastran sees them. If this is done, make sure that any equivalencing operations performed using these elements are done properly.
Note:
Supported Card
Solver Description
Supported Parameters TZREID, TZIMID, S, A, B, K, RHOC
Notes
PAABSF
Defines the properties of a frequency-dependent acoustic absorber element. Defines the properties of the
PACABS
SYNTH, TID1-TID3,

Altair Engineering
acoustic absorber element.
TESTAR, CUTFR, B, K, M PID, B NUM_B PID, ORIENT, WIDTH, AR, LRSB, LRIB, LTH1, LTH2, THI, THN beamsec A, I1, I2, J, NSM CONT1 beamsec GROUP CStype (ROD, TUBE, I, CHAN, T, BOX, BAR, CROSS, H, T1, I1, CHAN1, Z, CHAN2, T2, BOX1, HEXA, HAT, HAT1, DBOX) DIMs NSM
PAERO1
Defines associated bodies for the panels in the DoubletLattice method. Defines the cross-sectional properties of aerodynamic bodies.
PAERO2
PBAR
Defines the properties of a simple beam element (CBAR entry). Defines the properties of a simple beam element (CBAR entry) by cross-sectional dimensions.
PBARL
PBEAM
beamsec Defines the properties of a beam element (CBEAM entry). Aa, I1a, I2a, Ja, This element may be used to NSMa model tapered beams. PBEAM_CARD3 CONTINUATION LINE2 CONTINUATION LINE5 CONTINUATION LINE6
Blank fields are not supported for intermediate stations. Appropriate default values are inserted during feinput.
PBEAML
Defines the properties of a beam element by crosssectional dimensions.
beamsec GROUP TYPE (ROD, TUBE, L, I, CHAN, T, BOX, BAR, CROSS, H,
Blank fields are not supported for intermediate stations. Appropriate default values are inserted during feinput.
Altair Engineering

T1, I1, CHAN1, Z, CHAN2, T2, BOX1, HEXA, HAT, HAT1, DBOX) DIM1A, NSM pbeamlintStationslen PBEND A, I1, I2, J, RB, Defines the properties of a THETAB curved beam, curved pipe, or elbow element (CBEND entry). AltFormatOption (CONT1) Defines the nominal property K_LINE, B_LINE, values for a generalized spring- RCV_LINE, and-damper structural GE_LINE, PBUSHT element. Defines linear and nonlinear properties of a onedimensional spring and damper element (CBUSH1D entry). K, C, M, SA, SE SHOCKA_LINE SPRING_LINE DAMPER_LINE GENER_LINE PBUSHT Defines the frequency dependent properties or the stress dependent properties for a generalized spring and damper structural element. Defines the properties of an nply composite material laminate. PID, Z0, NSM, SB, FT, TREF, GE, LAM, MID, T, THETA, SOUT NUMBER_of_Plies PCOMPG Defines global (external) ply IDs and properties for a composite material laminate. PID, Z0, NSM, SB, FT, TREF, GE, LAM, GPLYID, MID, T, THETA, SOUT NUMBER_of_Plies PDAMP Specifies the damping value of B a scalar damper element using defined CDAMP1 or CDAMP3 entries.
PBUSH
PBUSH1D
PCOMP

Altair Engineering
PELAS
Specifies the stiffness, damping coefficient, and stress coefficient of a scalar elastic (spring) element (CELAS1 or CELAS3 entry). Defines the frequency dependent properties for a PELAS Bulk Data entry. Defines the CFAST fastener property values.
K1, GE1, S1 PELAST
PELAST
PFAST
D, MFLAG, KT1, KT2, KT3, KR1, KR2, KR3, MASS, GE MCID (-1, BLANK, MCID)
PGAP
Defines the properties of the gap element (CGAP entry). Defines a fully nonlinear (i.e., large strain and large rotation) hyperelastic solid element. Specifies the mass value of a scalar mass element (CMASS1 or CMASS3 entries). Defines the properties of a rod element (CROD entry).
U0, F0, KA, KB, KT, MU1, MU2, CONT STR (GRID, GAUS)
PLSOLID
PMASS
PID, M
PROD
beamsec A, J, C, NSM TYPE, W, T
PSEAM
Defines the PSEAM property values. Defines the properties of a shear panel (CSHEAR entry).
PSHEAR
PID, MID, T, NSM, F1, F2
PSHELL
Defines the membrane, PID, MID, T, I12_T3, bending, transverse shear, and TS_T, NSM coupling properties of thin shell MID1_blank, elements. MID2_opts, MID3_opts, CONT Defines the properties of solid PID, MD, IN,
PSOLID
Altair Engineering

elements (CHEXA, CPENTA, and CTETRA entries).
STRESS, ISPO, FCTN CORDM options (BLANK, -1, USER)
PTUBE
Defines the properties of a thin-walled cylindrical tube element (CTUBE entry). Defines properties of a onedimensional viscous damping element (CVISC entry).
beamsec OD, T, NSM, OD2
PVISC
CE1, CR1
PWELD
beamsec Defines the properties of connector (CWELD) elements. D, MSET, TYPE LDMIN, LDMAX
The Nastran, OptiStruct, and Radioss (Bulk Data) interfaces allow the property between groups to have the same ID. For example, PBAR3, PSHELL 3, PSOLID 3, etc. Duplicate IDs within the same group is not allowed.
Nastran, OptiStruct, and Radioss (Bulk Data) properties are grouped as follows: 0D_Rigids 1D SPRING_GAP 2D 3D PMASS PBAR, PBARL, PBEAM, PBEAML, PBEAND, PROD, PTUBE, PWELD PBUSH, PBUSH1D, PDAMP, PELAS, PGAP, PVISC PSHELL, PSHEAR, PCOMP, PCOMG PSOLID
PAM-CRASH 2G
Supported Card
Solver Description
Supported Parameters FRICT TITLE Friction model:
Notes
FRICT /
Friction modeling definition.

Altair Engineering
1: Standard Coulomb 2: Pressure dependent by curve 3: Velocity dependent by curve 4: Pressure and velocity dependent by curves 5: Pressure dependent by standard function 1 6: Pressure dependent by standard function 2 10. Orthotropic friction using element direction 11. Orthotropic friction using arbitrary direction GASPEC / Specification of air bag gas. WSGAS, ASGAS, BSGAS, CSGAS, DSGAS IRUPT, IFMON, TITLE, FAILT, FAILD, AFAILN, AFAILS, A1, A2, INTF, D1, D2
RUPMO /
Rupture model definition.
PERMAS
The following property data blocks are supported in the PERMAS interface: Supported Card Solver Description Supported Parameters BECONST (Secttype, Shear, Warp, Ce, Offset, Lmass) BETAPER Notes
$GEODAT BEAM
Beam
Altair Engineering

(Secttype, Shear, Warp, Ce, Offset, Lmass) BEAM2 (Secttype, Shear, Warp, Intsec, Ce, Offset, Lmass, Xylmass) $GEODAT CONA Surface convection UNIFORM THICK (TFilm) VARYING THICK (TFilm) $GEODAT CONS Shell surface convection UNIFORM THICK (TFilm, Offset) VARYING THICK (TFilm, Offset) $GEODAT DAMPER Viscous damper DAMP1 (Mass) DAMP3 (Mass, Refsys) DAMP6 (Mass, Refsys, Offset) NLDAMPER (Xlin, Mass, Refsys) $GEODAT FLANGE Flange ALL (Lmass) 2NODE (Lmass) 3NODE (Lmass) $GEODAT GASKET Gasket GAXIS VMASS $GEODAT MASS Mass MASS3 MASS6 (Offset, Refsys) $GEODAT SCALAR Scalar $GEODAT SHELL Shell DOF UNIFORM THICK (Offset, Cntrl, Core, Amass, Rsurf, Noffset) VARYING THICK (Offset, Cntrl, Core,

Altair Engineering
Amass, Rsurf, Noffset) $GEODAT SOLID Solid VMASS SPRING1 (Mass, Volume) SPRING3 (Mass, Volume, Refsys) SPRING6 (Mass, Volume, Refsys, Offset) NLSPRING (Xlin, Mass, Volume, Refsys)
$GEODAT SPRING Spring
Samcef
Supported Cards
Solver Description
Supported Parameters NOM, UNITE TYPE (I, DOUBLE T, U, L, L2, ZD, ZD2, T, FULL RECTANGLE, HOLLOW RECTANGLE, FULL CIRCLE, HOLLOW CIRCLE) H, B, TW, TF, R, R1, R2 AIRE, IT, IU, IV, ALPHA, YC, ZC, YM, ZM, AY, AZ UNITE (MILLIMETER, CENTIMETER, INCH, METER) INERTIA OPTIONS (CROSSSECTION_OP TION, PARAMETERS
Notes
.BPR
Define beam profiles.
Altair Engineering

Supported Cards
Solver Description
Supported Parameters FOR DEFINING INERTIA PROPERTIES) PHP BEAM DEGRE
Notes
.ETASHELL
Used to assign the laminate to the elements. The Projection method is supported.
LAM DIR NODE1 DIR NODE2 ANG
.ETASOLID
Used to assign the laminate to the elements. The Projection method is supported.
LAM DIR NODE1 DIR NODE2 ANG DEGRE
This is a dummy property, just to have a link between the elements and the material, as it is not possible to assign directly a material to the elements.
.PHP SHELL
Assign physical properties to an THICK existing mesh. SMAS DEGRE
See also Browsers HyperMesh Entities & Solver Interfaces Include Files Components Materials Element Property and Material Assignment Rules Model Setup

Altair Engineering
Sensors
Sensor entities are used to define and store sensors typically used in safety analysis. Sensors are shown under the Sensor folder within the Model Browser. Sensors do not have a display state. Sensors have an active and export state. The active state of a sensor controls the listing of the sensor in the Model Browser and any of its views. If a sensor entity is active, then it is listed in the Model Browser and any of its views. If a sensor entity is inactive, then it is not listed in the Model Browser or any of its views. The export state of a sensor entity controls whether or not that sensor is exported when the custom export option is utilized. The all export option is not affected by the export state of a sensor. The active and export states of sensor entities can be controlled using the Entity State Browser. The data names associated with sensors can be found in the data names section of the HyperMesh Reference Guide.
The following panels can be used to create and edit sensors:
Altair Engineering

Sensors
Solver Card Support for Sensors

Supported Card
Solver Description
Notes
/SENSOR /SENSOR/ACCE/ /SENSOR/AND/
Describes the sensors. Accelerometer. ON as long as sensors sensor_ID1 AND sensor_ID2 are ON. Nodal distance. Interface activation and deactivation. ON as long as sensor_ID1 is OFF. ON as long as sensors sensor_ID1 OR sensor_ID2 are ON. Rigid wall activation and deactivation. Activation with sensor_ID1, deactivation with sensor IS2. Start time.
/SENSOR/DIST/ /SENSOR/INTER/
/SENSOR/NOT/
/SENSOR/OR/
/SENSOR/RWAL/
/SENSOR/SENS/
/SENSOR/TIME/
Supported Card
Solver Description
Notes

Altair Engineering
MARKER
Defines a marker used in multi-body dynamics.
Defined in the markers panel.
LS-DYNA
Supported Card
Solver Description
Supported Parameters PID, SIDA, ACTIVE
Notes
*PART_SENSOR
Links part/component to a sensor to activate and deactivate during the analysis.
This is supported as an attribute to an element to maintain its associativity with element inside HyperMesh
*SENSOR_CONTR OL
Applies sensor result on an entity during run.
TYPE, TYPEID, INITSTT, SWIT Number of Switch
*SENSOR_DEFINE _ ELEMENT *SENSOR_DEFINE _ FORCE
Strain gauge type sensor.
ETYPE, ELEMID, COMP, CTYPE
Force transducer type sensor.
FTYPE, TYPEID, CRD Vector Type (X, Y, Z, XMOMENT, YMOMENT, ZMOMENT, VECTOR)
*SENSOR_DEFINE _NODE
Accelerometer type sensor.
NODE1, NODE2, CRD, CTYPE Vector Type (X, Y, Z, VECTOR)
*SENSOR_DEFINE _ CALC-MATH
Perform mathematical calculations on sensor values.
CALC, SENS Number of Sensors TYPE, SENSID, LOGIC, VALUE, TIMWIN SWIT1
*SENSOR_SWITCH Compares sensor value with input value and gives a logical signal. *SENSOR_SWITCH Performs mathematical
Altair Engineering

_ CALC-LOGIC
calculations on the logical signal from sensor logic.
Number of Switch Switch 1 Option
MADYMO
Supported Card
Solver Description
Supported Parameters TYPE (BODY, BODY_REL, JOINT_BRAKE, JOINT_POS) INPUT_CLASS (CONTROLLER, OPERATOR, SENSOR, SIGNAL) INPUT REF LOAD_TYPE (FORCE, TORQUE) CRDSYS (REF_SPACE, OBJECT) LOAD_DIR (X, Y, Z) POINT_OBJECT_1. MB (OBJECT, REF_SPACE) POS (X, Y, Z)
Notes
ACTUATOR
ACTUATOR.BODY applies a concentrated load (force or torque) on a single body with the magnitude of a selected input signal, in the direction specified by the user. ACTUATOR.BODY_REL applies a concentrated load, being a force or torque, on two bodies with the magnitude given by a selected input signal, at user specified points on those bodies. ACTUATOR.JOINT_BRAKE applies a concentrated Coulomb friction load on the parent body of a joint with the magnitude of a selected input signal multiplied by the gain, the friction coefficient and the reaction load on the corresponding child body.
define POINT_OBJECT_1. MB or select ACTUATOR.JOINT_POS applies a concentrated load on POINT_OBJECT_1. the parent body of a joint with REF? (OBJECT, REF) the magnitude of a selected input signal and the reaction COMMENT load on the corresponding child body. CONTROLLER Proportional integrating and differentiating controller TYPE (PID) CONTROL_SYSTEM INPUT_CLASS (CONTROLLER, OPERATOR, SENSOR, SIGNAL)

Altair Engineering
INPUT_REF, GAIN, TAUI, TAUD, COMMENT OPERATOR TYPE (DELAY, FUNC, MULTIPLY, SUM) CONTROL_SYSTEM INPUT_CLASS (CONTROLLER, OPERATOR, SENSOR, SIGNAL) INPUT_REF TIME_DELAY COMMENT PORT Port selection for SWITCH. MULTI_PORT. TYPE (BODY, BODY_REL, CONTACT, JOINT, JOINT_CONSTRAIN T, RESTRAINT, RETRACTOR, SURFACE_DIST) SIGNAL_TYPE (ANG_DISP, ANG_VEL, ANG_ACC, LIN_POS, LIN_VEL, LIN_ACC, PLAN_ACC) CRDSYS (OBJECT, REF SPACE) VECTORX, VECTORY, VECTORZ REF_SPACE, POS_X, POS_Y, POS_Z define POINT_OBJECT_1. MB or select POINT_OBJECT_1. REF? (OBJECT, Defined on the card of the parent SWITCH.
SENSOR
Altair Engineering

REF) COMMENT SIGNAL TYPE (FUNC, EXTERNAL_INPUT, EXTERNAL_OUTPU T) CONTROL_SYSTEM ABS_VALUE (OFF/ ON) INTERPOLATION (LINEAR, SPLINE) X_SCALE, Y_SCALE, X_SHIFT, Y_SHIFT COMMENT SIGNAL_VALUE Signal value. Defined on the card of the parent OPERATOR. TYPE (CONTACT, FE_MODEL, INFLATOR, JOINT, JOINT_REMOVE, RESTRAINT_REMO VE) SWITCH NR_OF_CONTACTS COMMENT SURFACE.PLANE Rectangular plane multibody = BODY N1 = POINT_1 N2 = POINT_2 N3 = POINT_3 To create a SURFACE under the SYSTEM. REF_SPACE, a reference to a null body must be selected because a reference to a multibody is required when creating a multibody plane. A null body can be created like any other BODY (card image is not relevant and should not be used), Nullbody should be put under the SYSTEM. REF_SPACE assembly.
STATE

Altair Engineering
SWITCH
Switch on signal from a sensor.
TYPE (CONTROL_SYSTE M, LOGIC, MULTIPORT, SENSOR, TIME, TIME_DELAY, TIME_FUNC) INVERT (OFF,ON) DYNAMIC_RELAX (NORMAL_ONLY, RELAX_ONLY, BOTH) TIME_TYPE (ELAPSED, SIMULATION) TIME COMMENT
PAM-CRASH 2G
Supported Card
Solver Description
Notes
SENSO /
Definition of a sensor
Types 2 and 4 are not supported. Types 2 and 4 are not supported.
SENSOR/
Definition of a sensor
Altair Engineering

Sets
Set entities are used to define and store lists of entity IDs for a specific entity. Sets can be generated for nodes, elements, components, assemblies, properties, materials, ellipsoids, multibody planes, multibody joints, and multibodies which contain entity IDs for that specific entity. Sets can also be generated as sets of sets, or lists of set IDs. Sets are shown under the Set folder within the Model Browser. The Set Browser can be used to create, edit, and review sets. Sets do not have a display state. Sets have an active and export state. The active state of a set controls the listing of the set in the Model Browsers and any of its views. If a set entity is active, then it is listed in the Model Browsers and any of its views. If a set entity is inactive, then it is not listed in the Model Browsers or any of its views. The export state of a set entity controls wether or not that set is exported when the custom export option is utilized. The all export option is not affected by the export state of a set. The active and export states of set entities can be controlled using the Entity State Browser. The data names associated with sets can be found in the data names section of the HyperMesh Reference Guide.

Altair Engineering
The following panels can be used to create and edit sets: Entity Sets
Solver Card Support for Sets

Note: Sets of different types but with the same ID are supported. Supported Card Solver Description Supported Notes
Altair Engineering

Parameters /GRBEAM /GRBEAM/BEAM /GRBEAM/ GRBEAM /GRBEAM/MAT /GRBEAM/PART /GRBEAM/PROP /GRBEAM/SUBSET /GRBRIC /GRBRIC/BRIC /GRBRIC/GRBRIC /GRBRIC/MAT /GRBRIC/PART /GRBRIC/PROP /GRBRIC/SUBSET /GRNOD /GRNOD/GENE /GRNOD/GRBEAM /GRNOD/GRBRIC /GRNOD/GRQUAD /GRNOD/GRSH3N /GRNOD/GRSHEL Describes a node group Describes the brick groups. Describes the beam groups.

Altair Engineering
/GRNOD/GRSPRI /GRNOD/GRTRUS /GRNOD/MAT /GRNOD/NODE /GRNOD/NODENS /GRNOD/PART /GRNOD/PROP /GRNOD/SUBSET /GRNOD/SURF /GRQUAD /GRQUAD/GRQUAD /GRQUAD/QUAD /GRQUAD/MAT /GRQUAD/PART /GRQUAD/PROP /GRQUAD/SUBSET /GRPART /GRSH3N Part set. Describes the 3 node shell groups. Describes the quad groups.
/GRSH3N/GRSH3N /GRSH3N/MAT /GRSH3N/PART /GRSH3N/PROP
Altair Engineering

/GRSH3N/SH3N /GRSH3N/SUBSET /GRSHEL /GRSHEL/GRSHEL /GRSHEL/MAT /GRSHEL/PART /GRSHEL/PROP /GRSHEL/SHEL /GRSHEL/SUBSET /GRSPRI /GRSPRI/GRSPRI /GRSPRI/PART /GRSPRI/PROP /GRSPRI/SPRI /GRSPRI/SUBSET /GRTRUS /GRTRUS/GRTRUS /GRTRUS/MAT /GRTRUS/PART /GRTRUS/PROP /GRTRUS/SUBSET /GRTRUS/TRUS /LINE Definition of the line. Describes the truss groups. Describes the spring groups. Describes the shell groups.

Altair Engineering
/LINE/EDGE /LINE/GRBEAM /LINE/GRTRUS /LINE/MAT /LINE/PROP /LINE/SURF /SURF Describes the surface definition.
/SURF/GRSHELL /SURF/MAT /SURF/MAT/ALL /SURF/MAT/EXT /SURF/PART /SURF/PART/ALL /SURF/PART/EXT /SURF/PROP /SURF/PROP/ALL /SURF/PROP/EXT /SURF/SRSH3N /SURF/SUBSET /SURF/SUBSET/ ALL /SURF/SUBSET/ EXT
Altair Engineering

/SURF/SURF
RADIOSS (Bulk Data), OptiStruct
RADIOSS (Bulk Data Format) sets are represented in HyperMesh as entity sets, and are controlled in the Entity Sets panel. The sets can be composed of grids, elements, design variables, MBD entities, mode numbers, frequencies or times for reference by other input definitions. In addition to the definition of entity sets through the explicit selection of the constituents, it is possible to define a set of nodes or a set of elements through a combination of formulaic expressions. Supported Card Solver Description Supported Parameters Notes
MBDCRV
Defines an ordered list of grids as a Multi-body Deformable Curve. Defines a Multi-body Deformable Surface. Defines a Multi-body Parametric Curve using node sets. Defines up to four sets of grid points as panels for panel participation output for a frequency response analysis of a coupled fluid-structural model. Defines a set of grids, elements, design variables, MBD entities, mode numbers, frequencies or times for reference by other input definitions. n/a
MBDSRF
MBPCRV
PANEL
SET
SET_DESVAR Contains design variables SET_ELEM Contains elements, properties, blocks or materials. SET_FREQ Contains real values. SET_GRID Contains nodes or
Sets of integer and real values are supported as entity sets.

Altair Engineering
blocks. SET_MODE Contains real values. SET_TIME Contains real values.
Note :
Sets that are created in HyperMesh are maintained on I/O by using $HMSET comment cards.
Abaqus
Sets can be created of nodes, elements, components, and other sets. Supported Card Solver Description Supported Parameters LOCATION NAME TYPE *ELSET Assign elements to an element set Specify an element or a group of elements that lie embedded in a group of host elements in a model ELSET GENERATE ABSOLUTE EXTERIOR TOLERANCE EXTERIOR TOLERANCE HOST ELSET ROUNDOFF TOLERANCE *NODAL THICKNESS *NSET Define shell or membrane thickness at nodes Assign nodes to a node set GENERATE Notes
*DISTRIBUTION
Define spatial distributions
*EMBEDDED ELEMENT
NSET ELSET GENERATE UNSORTED
Altair Engineering

Sets can be specified directly from nodes and elements in the model or by a formula. Sets of sets and components are also supported in Abaqus templates. To create sets that contain a combination of sets and individual nodes or elements, select the add by IDs option in a formula-based set. A User Comments block is supported for all sets. See the information below on how to add comments to any set card image. These comments will be preserved during import and export of the Abaqus input deck. Sets using the GENERATE parameter can be expanded upon imported using the Expand sets defined by range solver option in the Import panel. This is useful for when node/element IDs are renumbered during import. ANSYS
Supported Card
Solver Description
Supported Parameters Name
Notes
CMGRP
Groups components and assemblies into an assembly.
This is supported as sets of sets.
LS-DYNA
The default LS-DYNA attribute values for the set can be edited. Individual values cannot be edited. Supported Card Solver Description Supported Parameters Title Notes
*DEFINE_HEX_SPO Assembly of elements that TWELD describes a spotweld. _ASSEMBLY *DEFINE_HEX_SPO TWELD _ASSEMBLY_N *SET_BEAM(TITLE) Define a set of beam elements.
DA1-DA4 GenerateOption Title
*SET_BEAM_ADD
Define a beam set by combining beam sets.
Title

Altair Engineering
*SET_BEAM_GENE Generates a block of beam RATE element IDs between a (TITLE) starting ID and an ending ID. *SET_DISCRETE (TITLE) Define a set of discrete elements.
DA1 - DA4 NBEG, NEND Title DA1 - DA4 GenerateOption Title
*SET_DISCRETE_A DD *SET_DISCRETE_ GENERATE(TITLE)
Define a discrete set by combining discrete sets.
Title
Generates a block of discrete DA1 - DA4 element IDs between a NBEG, NEND starting ID and an ending ID. Title Define a node set by combining node sets. A1 - A4 Title A1 - A4 Title
*SET_NODE_ADD
*SET_NODE_ADD_ ADVANCED
Define a node set by combining node sets or by combining NODE, SHELL, SOLID, BEAM, SEGMENT, DISCRETE and THICK SHELL sets. Define a nodal set with some identical or unique attributes.
*SET_NODE_COLU MN
DA1 - DA4 A1 - A4 Title
*SET_NODE_LIST (TITLE)
Define a nodal set with some identical or unique attributes.
DA1 - DA4 Options (None, Generate, Column) DA1 - DA4 NBEG, NEND Title Title
*SET_NODE_LIST_ GENERATE(TITLE)
Generate a block of node IDs between a starting nodal ID number and an ending nodal ID number. Define a part set by combining part sets. Define a set of parts with optional attributes.
*SET_PART_ADD
*SET_PART_COLU MN (TITLE)
DA1 - DA4 A1 - A4 Title
Altair Engineering

*SET_PART_LIST_ GENERATE(TITLE)
DA1 - DA4 Generate a block of part IDs between a starting part ID NBEG, NEND number and an ending part ID Title number. Definition of contact surface from parts, elements, box. Define a shell set by combining shell sets. n/a
*SET_SEGMENT_ GENERAL *SET_SHELL_ADD
Title
*SET_SHELL_COLU Define a set of shell elements DA1 - DA4 MN with optional identical or A1 - A4 unique attributes. Title *SET_SHELL_LIST (TITLE) Define a set of shell elements DA1 - DA4 with optional identical or Options (None, unique attributes. Generate, Column) Title *SET_SHELL_LIST_ Define a set of shell elements DA1 - DA4 GENERATE(TITLE) with optional identical or NBEG, NEND unique attributes. Title *SET_SOLID(TITLE) Define a set of solid elements. DA1 - DA4 GenerateOption Title *SET_SOLID_ADD Define a solid set by combining solid sets. Title
*SET_SOLID_GENE RAL *SET_SOLID_GENE Generate a block of solid RATE element IDs between a (TITLE) starting ID and an ending ID. *SET_TSHELL (TITLE) Define a set of thick shell elements. DA1 - DA4 NBEG, NEND
DA1 - DA4 GenerateOption Title
*SET_TSHELL_GEN ERAL

Altair Engineering
*SET_TSHELL_GEN Generate a block of thick ERATE shell element IDs between a (TITLE) starting ID and an ending ID.
Set_Title DA1 - DA4 NBEG, NEND
MADYMO
Supported Card
Solver Description
Supported Parameters FE_MODEL
Notes
GROUP_FE
Assembles a selected set of finite element objects within an FE model into a group. Assembles a selected set of multibody objects into a group.
GROUP_MB
BODY_LIST
MARC
Supported Card
Solver Description
Notes
DEFINE OSET
Nastran
Supported Card
Solver Description
Supported Parameters C
Notes
BNDFREE1 CSUPER
Defines the grid or scalar SSID, PSID point connections for identical or mirror image superelements or superelements from an
Altair Engineering

external source. CSUPEXT Assigns exterior points to a superelement. Defines one or more panels by referencing sets of grid points, elements or properties. SEID
PANEL
NAME, SETID,
SEBNDRY
Defines a list of grid points in SEIDB Options (ALL, a partitioned superelement for VALUE) the automatic boundary search between a specified superelement or between all other superelements in the model. Defines boundary degrees-of- SEID, C freedom to be fixed (b-set) during generalized dynamic reduction or component mode calculations . Defines boundary degrees-of- SEID, C freedom to be free (c-set) ALL during generalized dynamic reduction or component mode synthesis calculations. Defines the generalized SEID, C degrees-of-freedom of the superelement to be used in generalized dynamic reduction or component mode synthesis. Defines interior grid points for a superelement. Defines a set of element or grid point numbers to be plotted. SEID
SEBSET1
SECSET1
SEQSET1
SESET
SET
ID
Node and element sets supported with the THRU option.
SET1
Defines a list of structural grid ID points or element SKIN identification numbers.

Altair Engineering
SEUSET1
Defines a degree-of-freedom set for a superelement.
SEID, SNAME, C
Note:
When reading input decks that were not created in HyperMesh, an attempt is made to create two sets for each set found: one containing elements and one containing nodes. You can delete the unnecessary set. Sets that are created are maintained as node or element sets by using $HMSET comment cards.
PAM-CRASH 2G
During import, entity sets are automatically generated. PAM-CRASH 2G cards with general entity selection generate entity sets.
Supported Card
Solver Description
Notes
GES / GROUP / Keyword selection PAM-CRASH 2G GROUP / card and general entity selection (GES) are mapped as set of sets . A set is created if only one keyword is used. A set of sets is created in the following cases: If the definition uses more than one keyword. Unresolved groups are used in the definition. More than one GRP keyword is present in the definition. A GROUP definition is
Altair Engineering

always implemented as set of set. In card previewer a toggle switches between PAMCRASH 2G GROUP and General Entity Selection.
PERMAS
Supported Card
Solver Description
Supported Parameters NAME DESCRIPTION
Notes
ESET
Definition of new element sets. An element set may be defined by a list of element numbers or other element set names or using some generation rules.
ESETBIN
Definition of element set bins. NAME An element set bin is defined DESCRIPTION by a list of element set names. Definition of new node sets. A NAME node set may be defined by a DESCRIPTION list of node numbers or other node set names or using some generation rules. Definition of node set bins. A node set bin is defined by a list of node set names. NAME DESCRIPTION
NSET
NSETBIN
SFSET
Definition of new surface sets. NAME A surface set may be defined DESCRIPTION by a list of surface numbers or other surface set names or using some generation rules.
Samcef

Altair Engineering
Supported Card
Solver Description
Supported Parameters GROUP, NOM, NUD, MAILLE GROUP, NOM, MAILLE
Notes
.SEL NOE
Defines a set of grids
.SEL MAI
Defines a set of elements
Altair Engineering

Tags
Tag entities are used to tag a piece of information, called the body, onto a node or element within the model. Tags are shown under the Tag folder within the Model Browser. Tags have a display state, on or off, which controls the display of a tag in the graphics area. The display state of a tag can be controlled using the icon next to the tag entity in the Model Browser. Tags also have an active and export state. The active state of a tag controls the display state of the tag and the listing of the tag in the Model Browser and any of its views. If a tag entity is active, then its display state is available to be turned on or off and it is listed in the Model Browser and any of its views. If a tag entity is inactive, then its display state is turned off permanently and it is not listed in the Model Browser or any of its views. The export state of a tag entity controls wether or not that tag is exported when the custom export option is utilized. The all export option is not affected by the export state of a tag. The active and export states of tag entities can be controlled using the Entity State Browser. The data names associated with tags can be found in the data names section of the HyperMesh Reference Guide.

Altair Engineering
The following panels can be used to create and edit tags: Tags
Altair Engineering

Titles
Title entities are used attach a title box with text to the graphics area, or to node, element, load, or system. If attached to a node, element, load, or system the title moves with the model. If attached to the graphics area the title is static. Titles are shown under the Title folder within the Model Browser. Titles have a display state, on or off, which controls the display of a title in the graphics area. The display state of a title can be controlled using the icon next to the tag entity in the Model Browser. Titles also have an active and export state. The active state of a title controls the display state of the title and the listing of the title in the Model Browser and any of its views. If a title entity is active, then its display state is available to be turned on or off and it is listed in the Model Browser and any of its views. If a title entity is inactive, then its display state is turned off permanently and it is not listed in the Model Browser or any of its views. The export state of a title entity controls wether or not that title is exported when the custom export option is utilized. The all export option is not affected by the export state of a title. The active and export states of title entities can be controlled using the Entity State Browser. The data names associated with titles can be found in the data names section of the HyperMesh Reference Guide.

Altair Engineering
The following panels can be used to create and edit titles: Titles
Altair Engineering

Morphing Entities
HyperMorph contains a wide array of functionality for morphing the shape FE models. HyperMorph utilizes six exclusive morphing entities; domains, handles, morph constraints, morph volumes, shapes, and symmetries. While all the entities and functions are fully compatible, and may be used in a complementary fashion, they can be divided into three basic approaches to morphing; the domains and handles concept, the morph volume concept, and the freehand concept. Each approach has its own strengths and weaknesses when dealing with the numerous applications of morphing and you are advised to gain a basic understanding of each approach so that you can decide which approach is best for your needs. The morphing chapter is intended to illustrate the capabilities of HyperMorph and introduce you to both the basic and advanced functionality to help you get the most out of the tool.
Morphing Entities Domains Handles Morph Constraints Morph Volumes Shapes Symmetries
See also Browsers HyperMesh Entities & Solver Interfaces Morphing

Altair Engineering
Domains
Domain entities are used in the domains and handles concept to morphing by dividing the model into domains. Handles are then used to control the domains shape. When the handles associated with a domain move, the shape of the domain changes, which in turn changes the positions of the nodes inside those domains. There are two groups of domains; global and local domains. Local domains have several types including; 1D, 2D, 3D, edge, and general domains. All types of domains are shown under the Domain folder within the Model Browser. Domains have a display state, on or off, which controls the display of a domain in the graphics area. The display state of a domain can be controlled using the icon next to the domain entity in the Model Browser. Domains do not have active or export states.
The following panels can be used to create and edit domains: Domains
See also Model Browser HyperMesh Entities & Solver Interfaces Morphing The Domains and Handles Concept
Altair Engineering

Handles
Handle entities are used in the domains and handles concept to morphing by dividing the model into domains. Handles are then used to control the domains shape. When the handles associated with a domain move, the shape of the domain changes, which in turn changes the positions of the nodes inside those domains. Handles are associated to their domains. Global handles are red and are associated to global domains. Local handles are orange and are associated to local domains. Both global and local handles can have dependent handles which are of varying colors and sizes as defined in the topic dependent handles. All types of handles are shown under the Handle folder within the Model Browser. Handles have a display state, on or off, which controls the display of a handle in the graphics area. The display state of a handle can be controlled using the icon next to the handle entity in the Model Browser. Handles do not have active or export states.
The following panels can be used to create and edit handles: Handles
See also Dependent Handles Model Browser HyperMesh Entities & Solver Interfaces

Altair Engineering
Morphing The Domains and Handles Concept
Altair Engineering

Morph Constraints
Morph constraint entities are used to restrict the movement of nodes during morphing operations. The following types of morph constraints can be applied to any node: fixed, cluster, along vector, on plane, along line, on surface, and on elements. Morph constraints are shown under the MorphingCoinstraint folder within the Model Browser. Morph constraints have a display state, on or off, which controls the display of a morph constraint in the graphics area. The display state of a morph constraint can be controlled using the icon next to the morph constraint entity in the Model Browser. Morph constrains do not have active or export states.
The following panels can be used to create and edit morph constrains: Morph Constraints
See also Model Browser HyperMesh Entities & Solver Interfaces Morphing Using Constraints

Altair Engineering
Morph Volumes
Morph volume entities are highly deformable six-sided prisms which surround a portion of the FE mesh. Morph volumes support tangency between adjoining edges and allow for multiple control points along their edges. Handles placed at the corners and along the edges of the morph volumes allow for the morphing of the morph volumes which in turn morphs the mesh inside the morph volumes. Morph volumes are shown under the MorphingVolume folder within the Model Browser. Morph volumes have a display state, on or off, which controls the display of a morph volume in the graphics area. The display state of a morph volume can be controlled using the icon next to the morph volume entity in the Model Browser. Morph volumes do not have active or export states.
The following panels can be used to create and edit morph volumes: Morph Volumes
See also Model Browser HyperMesh Entities & Solver Interfaces Morphing The Morph Volume Concept
Altair Engineering

Shapes
Shape entities are collections of handle and/or node perturbations from the initial configuration of the FE mesh before the morph. When you morph your model, HyperMorph stores the morph internally as a collection of perturbations which you can then undo, redo, and/or save as a shape. Shapes are shown under the Shape folder within the Model Browser. Shapes have a display state, on or off, which controls the display of a shape in the graphics area. The display state of a shape can be controlled using the icon next to the shape entity in the Model Browser. Shapes do not have active or export states.
The following panels can be used to create and edit shapes: Morph Freehand Shapes
See also Model Browser HyperMesh Entities & Solver Interfaces Morphing Working with Shapes

Altair Engineering
Symmetries
Symmetry entities are utilized to define planes of symmetry within a model so that morphs can be applied in a symmetric fashion. Symmetries are shown under the Symmetry folder within the Model Browser. Symmetries have a display state, on or off, which controls the display of a symmetry in the graphics area. The display state of a symmetry can be controlled using the icon next to the symmetry entity in the Model Browser. Symmetries do not have active or export states.
The following panels can be used to create and edit symmetries: Symmetry
See also Model Browser HyperMesh Entities & Solver Interfaces Morphing
Altair Engineering

Optimization Entities
A wide array of functionality exists for setting up optimization problems. There are twelve exclusive optimization entities listed below. The optimization chapter is intended to illustrate the capabilities available for setting up optimization problems.
Optimization Entities Design Variables Design Variable Links Design Variable Property Relationships Discrete Design Variables Optimization Responses Optimization Constraints Optimization Equations Optimization Table Entries Objectives Objective References Optimization Constraint Screenings Optimization Controls
See also Browsers HyperMesh Entities & Solver Interfaces Include Files Optimization

Altair Engineering
Design Variables
Design variable entities are used to define and store design variables for optimization problems. Design variables are shown under the DesignVariable folder within the Model Browser. The Optimization Browser View can be utilized to create, edit, and delete optimization problems. Design variables do not have a display state. Design variables have an active and export state. The active state of a design variable controls the listing of the design variable in the Model Browser and any of its views. If a design variable entity is active, then it is listed in the Model Browser and any of its views. If a design variable entity is inactive, then it is not listed in the Model Browser or any of its views. The export state of a design variable entity controls whether or not that design variable is exported when the custom export option is utilized. The all export option is not affected by the export state of a design variable. The active and export states of design variable entities can be controlled using the Entity State Browser. The data names associated with design variables can be found in the data names section of the HyperMesh Reference Guide.
The following panels can be used to create and edit design variables: Topology Topography Free Size Free Shape Composite Size Size Gauge Shape
Altair Engineering

Solver Card Support for Design Variables

An optimization problem is set up by defining responses, which are in turn constrained or set as objectives. Design variables identify the varying quantities in an optimization problem. The optimization panels are available from the Optimization menu when the RADIOSS (Bulk Data) or OptiStruct user profile is loaded. Supported Card Solver Description Supported Parameters Notes
DCOMP
Manufacturing constraints for composite sizing optimization. Supported as a designvariable entity. Design variable definition. Supported as a designvariable entity.
Defined in the Composite Size panel.
DESVAR
Explicitly defined in the Size panel. Also defined automatically by the Gauge panel and the Shape panel. Defined in the Free Shape panel.
DSHAPE
Free-shape design variable definition. Supported as a designvariable entity. Solid surface nodes or shell edge nodes may be selected as free-shape design regions.
DSHUFFLE
Parameters for the generation of composite shuffling design variables. Supported as a designvariable entity. Free-size design variable definition. Supported as a designvariable entity. PCOMP, PCOMPG, and PSHELL components may be selected as free-size design regions.
Defined in the Composite Shuffle panel.
DSIZE
Defined in the Free Size panel.

Altair Engineering
DTPG
Topography design variable definition. Supported as a designvariable entity. PSHELL, PCOMP and PCOMPG components as well as predefined shape design variables may be selected as topography design regions.
Defined in the Topography panel.
DTPL
Topology design variable definition. Supported as a designvariable entity. PBAR, PBUSH, PCOMP, PCOMPG, PROD, PSHELL, PSOLID, PWELD can be selected.
Defined in the Topology panel.
DVGRID
Perturbation vector definition for shape optimization. Automatically defined on export, when HyperMorph shapes are used to generate shape design variables in the shape panel. Defined in the shape panel.
Exported in large field format by both the optistruct and optistructlf templates.
Nastran
Some of the functionality of the optimization capability is general. This includes the equation utility, delete, rename, renumber, and reorder. To set up an optimization problem, responses, an objective function and constraints need to be defined. Further, design variables need to be defined. The optimization panels have separate Delete , Rename , Renumber, and Reorder panels to manipulate optimization entries. These can be reached through the Optimization panel. Supported Card Solver Description Supported Parameters Notes
DESVAR
Defines a design variable for design optimization. Relates one design variable to one or more other design variables.
Design variable definition Design variable link
DLINK
Altair Engineering

See also Optimization Browser View Entity State Browser Browsers HyperMesh Entities & Solver Interfaces Include Files Optimization

Altair Engineering
Design Variable Links

Design variable link entities are used to define links between design variables for optimization problems. Design variable links are shown under the DesignVariableLink folder within the Model Browser. The Optimization Browser View can be utilized to create, edit, and delete optimization problems. Design variable links do not have a display state. Design variable links have an active and export state. The active state of a design variable link controls the listing of the design variable link in the Model Browser and any of its views. If a design variable link entity is active, then it is listed in the Model Browser and any of its views. If a design variable link entity is inactive, then it is not listed in the Model Browser or any of its views. The export state of a design variable link entity controls whether or not that design variable link is exported when the custom export option is utilized. The all export option is not affected by the export state of a design variable link. The active and export states of design variable link entities can be controlled using the Entity State Browser. The data names associated with design variable links can be found in the data names section of the HyperMesh Reference Guide.
The following panels can be used to create and edit design variable links: Desvar Link
Solver Card Support for Design Variable Links

An optimization problem is set up by defining responses, which are in turn constrained or set as objectives. Design variables identify the varying quantities in an optimization problem. All of the optimization panels are available from the Optimization menu when the RADIOSS (Bulk Data), OptiStruct user profile is loaded.
Altair Engineering

Supported Card
Solver Description
Supported Parameters designvariablelink
Notes
DLINK
Design variable link. Supported as a designvariablelink entity. Used to define links between DESVARs.
Defined in the Desvar Link panel.
DLINK2
Defines a link of one design variable to one or more other design variables defined by a DEQATN card.
Nastran
Some of the functionality of the optimization capability is general. This includes the equation utility, delete, rename, renumber, and reorder functions. To set up an optimization problem, responses, an objective function and constraints need to be defined. Further, design variables need to be defined. The optimization panels have separate Delete , Rename , Renumber, and Reorder panels to manipulate optimization entries. These can be reached through the Optimization drop down menu.
Supported Card
Solver Description
Notes
DLINK
Relates one design variable to one or more other design variables.
Design variable link
DLINK2

Altair Engineering
Altair Engineering

Design Variable Property Relationships

Design variable property relationship entities are used to define relationships between design variables and properties for optimization problems. Design variable property relationships are shown under the DesignVariablePropertyRelationship folder within the Model Browser. The Optimization Browser View can be utilized to create, edit, and delete optimization problems. Design variable property relationships do not have a display state. Design variables property relationships have an active and export state. The active state of a design variable property relationship controls the listing of the design variable property relationship in the Model Browser and any of its views. If a design variable property relationship entity is active, then it is listed in the Model Browser and any of its views. If a design variable property relationship entity is inactive, then it is not listed in the Model Browser or any of its views. The export state of a design variable property relationship entity controls whether or not that design variable property relationship is exported when the custom export option is utilized. The all export option is not affected by the export state of a design variable property relationship. The active and export states of design variable property relationship entities can be controlled using the Entity State Browser. The data names associated with design variable property relationships can be found in the data names section of the HyperMesh Reference Guide.
The following panels can be used to create and edit design variable property relationships: Size Gauge
Solver Card Support for Design Variable Property Relationships

An optimization problem is set up by defining responses, which are in turn constrained or set as

Altair Engineering
objectives. Design variables identify the varying quantities in an optimization problem. All of the optimization panels are available from the Optimization menu when the RADIOSS (Bulk Data), OptiStruct user profile is loaded. Supported Card Solver Description Supported Parameters Notes
DVCREL1
Generic design variable to connectivity property relationship. Supported as a designvariablepropertyrelation ship entity. CBAR, CELAS2, CELAS4, CMASS2, CMASS4, CDAMP2, CDAMP4, CONM1, CONM2, CONROD, CQUAD4, CTRIA3, CQUAD8, CTRIA6 elements can be selected.
Defined in the generic relationship subpanel of the Size panel.
DVCREL2
Generic design variable to connectivity property relationship. Supported as a designvariablepropertyrelation ship entity. CBAR, CELAS2, CELAS4, CMASS2, CMASS4, CDAMP2, CDAMP4, CONM1, CONM2, CONROD, CQUAD4, CTRIA3, CQUAD8, CTRIA6 elements can be selected.
Defined in the function relationship subpanel of the Size panel.
DVMREL1
Generic design variable to material relationship. Supported as a designvariablepropertyrelation ship entity. MAT1, MAT2, MAT8 and MAT9 materials can be selected.
Defined in the generic relationship subpanel of the Size panel.
DVMREL2
Function design variable to material relationship. Supported as a designvariablepropertyrelation ship entity.
Defined in the function relationship subpanel of the Size panel. Requires a dequation definition.
Altair Engineering

MAT1, MAT2, MAT8 and MAT9 materials can be selected. DVPREL1 Generic design variable to property relationship. Supported as a designvariablepropertyrelation ship entity. PBAR, PBARL, PBEAM, PBEAML, PBUSH, PCOMP, PCOMPG*, PCOMPP, PDAMP, PELAS, PMASS, PROD, PSHEAR, PSHELL, PVISC properties and PLY entities can be selected. Function design variable to property relationship. Supported as a designvariablepropertyrelation ship entity. PBAR, PBARL, PBEAM, PBEAML, PBUSH, PCOMP, PCOMPG*, PCOMPP, PDAMP, PELAS, PMASS, PROD, PSHEAR, PSHELL, PVISC properties and PLY entities can be selected. Defined in the generic relationship subpanel of the Size panel. Automatically defined in the Gauge panel for shell or ply thickness and ply orientations. * For PCOMPG, either global plies or property specific plies may be selected. Defined in the function relationship subpanel of the Size panel. Requires a dequation definition. * For PCOMPG, either global plies or property specific plies may be selected
DVPREL2
Nastran
Some of the functionality of the optimization capability is general. This includes the equation utility, delete , rename , renumber, and reorder functions. To set up an optimization problem, responses, an objective function and constraints need to be defined. Further, design variables need to be defined. The optimization panels have separate Delete , Rename , Renumber, and Reorder panels to manipulate optimization entries. These can be reached through the Optimization menu. Supported Card Solver Description Supported Parameters Notes
DVCREL1
Defines the relation between a connectivity property and design variables.
Generic Property

Altair Engineering
DVCREL2
Defines the relation between a connectivity property and design variables with a user-supplied equation. Defines the relation between a material property and design variables Defines the relation between a material property and design variables with a user-supplied equation Defines the relation between an analysis model property and design variables. Defines the relation between an analysis model property and design variables with a usersupplied equation. Generic Property
DVMREL1
DVMREL2
DVPREL1
DVPREL2
Function Property
Altair Engineering

Discrete Design Variables

Discrete design variable entities are used to define and store discrete design variables for optimization problems. Discrete design variables are shown under the DiscreteDesignVariable folder within the Model Browser. The Optimization Browser View can be utilized to create, edit, and delete optimization problems. Discrete design variables do not have a display state. Discrete design variables have an active and export state. The active state of a discrete design variable controls the listing of the discrete design variable in the Model Browser and any of its views. If a discrete design variable entity is active, then it is listed in the Model Browser and any of its views. If a discrete design variable entity is inactive, then it is not listed in the Model Browser or any of its views. The export state of a discrete design variable entity controls whether or not that discrete design variable is exported when the custom export option is utilized. The all export option is not affected by the export state of a discrete design variable. The active and export states of discrete design variable entities can be controlled using the Entity State Browser. The data names associated with discrete design variables can be found in the data names section of the HyperMesh Reference Guide.
The following panels can be used to create and edit discrete design variables: Discrete DVS
Solver Card Support for Discrete Design Variables


Altair Engineering
Supported Card
Solver Description
Notes
DDVAL
Discrete design variable value lists. Supported as a ddval entity.
Defined in the Discrete DVS panel.
Nastran
An optimization problem is set up by defining responses, which are in turn constrained or set as objectives. Design variables identify the varying quantities in an optimization problem. All of the optimization panels are available from the Optimization menu when the Nastran user profile is loaded.
Supported Card
Solver Description Define real, discrete design variable values for discrete variable optimization. Supported as a ddval entity.
Notes
DDVAL
Defined in the Discrete DVSpanel.
Altair Engineering

Optimization Responses
Optimization response entities are used to define and store model responses for optimization problems. Optimization responses are shown under the OptimizationResponse folder within the Model Browser. The Optimization Browser View can be utilized to create, edit, and delete optimization problems. Optimization responses do not have a display state. Optimization responses have an active and export state. The active state of an optimization response controls the listing of the optimization response in the Model Browser and any of its views. If an optimization response entity is active, then it is listed in the Model Browser and any of its views. If an optimization response entity is inactive, then it is not listed in the Model Browser or any of its views. The export state of an optimization response entity controls whether or not that optimization response is exported when the custom export option is utilized. The all export option is not affected by the export state of an optimization response. The active and export states of optimization response entities can be controlled using the Entity State Browser. The data names associated with optimization responses can be found in the data names section of the HyperMesh Reference Guide.
The following panels can be used to create and edit optimization responses: Responses
Solver Card Support for Optimization Responses

An optimization problem is set up by defining responses, which are in turn constrained or set as objectives. Design variables identify the varying quantities in an optimization problem.

Altair Engineering
All of the optimization panels are available from the Optimization menu when the RADIOSS (Bulk Data), OptiStruct user profile is loaded.
Supported Card
Solver Description
Notes
DRESP1
Generic response. Supported as a response entity.
Defined in the Responses panel. (All response types except function). Defined in the Responses panel. (Use function response type). Defined in the Responses panel. Defined in the Responses panel for WFREQ and COMB response types
DRESP2
Function response. Supported as a response entity.
DSYSID
Design objective for target optimization The weighting applied to modes for response types WFREQ, COMB. Automatically created within relevant subcase definitions on export. The weighting applied to compliances for response types WCOMP, COMB. Automatically created within relevant subcase definitions on export.
MODEWEIGHT
WEIGHT
Defined in the Responses panel for WCOMP and COMB response types.
Nastran
Some of the functionality of the optimization capability is general. This includes the equation utility, delete, rename, renumber, and reorder functions. To set up an optimization problem, responses, an objective function and constraints need to be defined. Further, design variables need to be defined. The optimization panels have separate Delete , Rename , Renumber, and Reorder panels to manipulate optimization entries. These can be reached through the Optimization menu.
Supported Card
Solver Description
Notes
Altair Engineering

DRESP1
Defines a set of structural responses that is used in the design either as constraints or as an objective. Defines equation responses that are used in the design, either as constraints or as an objective.
Generic response
DRESP2
Function response

Altair Engineering
Optimization Constraints
Optimization constraint entities are used to define and store constraints on model responses for optimization problems. Optimization constraints are shown under the OptimizationConstraint folder within the Model Browser. The Optimization Browser View can be utilized to create, edit, and delete optimization problems. Optimization constraints do not have a display state. Optimization constraints have an active and export state. The active state of an optimization constraint controls the listing of the optimization constraint in the Model Browser and any of its views. If an optimization constraint entity is active, then it is listed in the Model Browser and any of its views. If an optimization constraint entity is inactive, then it is not listed in the Model Browser or any of its views. The export state of an optimization constraint entity controls whether or not that optimization constraint is exported when the custom export option is utilized. The all export option is not affected by the export state of an optimization constraint. The active and export states of optimization constraint entities can be controlled using the Entity State Browser. The data names associated with optimization constraints can be found in the data names section of the HyperMesh Reference Guide.
The following panels can be used to create and edit optimization constraints: Dconstraints
Solver Card Support for Optimization Constraints

RADIOSS (Bulk Data Format, OptiStruct)
An optimization problem is set up by defining responses, which are in turn constrained or set as objectives.
Altair Engineering

Design variables identify the varying quantities in an optimization problem. All of the optimization panels are available from the Optimization menu when the RADIOSS (Bulk Data), OptiStruct user profile is loaded.
Supported Card
Solver Description
Notes
DCONADD
Collects constraints. DCONADD do not exist within the database, they are created automatically on export for opticonstraint entities. A constraint definition, defining lower and/or upper bounds for a response. Supported as an opticonstraint entity. Global constraint selection. Automatically created on export for opticonstraints that do not require a loadstep (subcase) selection. Subcase dependent constraint selection. Automatically created on export when a loadstep (subcase) is selected in an opticonstraint definition. Defined in the Dconstraints panel.
DCONSTR
DESGLB
opticonstraints are defined in the Dconstraints panel.
DESSUB
opticonstraints are defined in the Dconstraints panel.
Nastran
Some of the functionality of the optimization capability is general. This includes the equation utility, delete, rename, renumber, and reorder functions. To set up an optimization problem, responses, an objective function and constraints need to be defined. Further, design variables need to be defined. The optimization panels have separate Delete , Rename , Renumber, and Reorder panels to manipulate optimization entries. These can be reached through the Optimization drop down menu.
Supported Card
Solver Description
Notes
DCONADD
Defines the design constraints
Collects constraints

Altair Engineering
for a subcase as a union of DCONSTR entries. DCONSTR Defines design constraints. Constraint to define lower and upper bounds Global constraint; belongs in the subcase section Constraint dependent on the load step; Belongs in the subcase section
DESGLB
Selects the design constraints to be applied at the global level in a design optimization task. Selects the design constraints to be used in a design optimization task for the current subcase.
DESSUB
Altair Engineering

Optimization Equations
Optimization equation entities are used to define and store equations for optimization problems. Optimization equations are shown under the OptimizationFunction folder within the Model Browser. The Optimization Browser View can be utilized to create, edit, and delete optimization problems. Optimization equations do not have a display state. Optimization equations have an active and export state. The active state of an optimization equation controls the listing of the optimization constraint in the Model Browser and any of its views. If an optimization equation entity is active, then it is listed in the Model Browser and any of its views. If an optimization equation entity is inactive, then it is not listed in the Model Browser or any of its views. The export state of an optimization equation entity controls whether or not that optimization equation is exported when the custom export option is utilized. The all export option is not affected by the export state of an optimization equation. The active and export states of optimization equation entities can be controlled using the Entity State Browser. The data names associated with optimization equations can be found in the data names section of the HyperMesh Reference Guide.
The following panels can be used to create and edit optimization equations: Dequations
Solver Card Support for Optimization Equations


Altair Engineering
Supported Card
Solver Description
Notes
DEQATN
Equations referenced on DRESP2, DVPREL2. Supported as an optimizationequation entity.
Defined in the Dequations panel.
Nastran
Supported Card
Solver Description
Notes
DEQATN
Defines one or more equations for use in design sensitivity or pelement analysis.
Equations referenced on DRESP2, DVPREL2
Altair Engineering

Optimization Table Entries

Optimization table entry entities are used to define and store table data for optimization problems. Optimization table entries are shown under the OptimizationTableEntry folder within the Model Browser. The Optimization Browser View can be utilized to create, edit, and delete optimization problems. Optimization table entries do not have a display state. Optimization table entries have an active and export state. The active state of an optimization table entry controls the listing of the optimization table entry in the Model Browser and any of its views. If an optimization table entry entity is active, then it is listed in the Model Browser and any of its views. If an optimization table entry entity is inactive, then it is not listed in the Model Browser or any of its views. The export state of an optimization table entry entity controls whether or not that optimization table entry is exported when the custom export option is utilized. The all export option is not affected by the export state of an optimization table entry. The active and export states of optimization table entry entities can be controlled using the Entity State Browser. The data names associated with optimization table entries can be found in the data names section of the HyperMesh Reference Guide.
The following panels can be used to create and edit optimization table entries: Table Entries
Solver Card Support for Optimization Table Entries


Altair Engineering
Supported Card
Solver Description
Notes
DTABLE
Table entries referenced on DRESP2, DVPREL2. Supported as a optimizationtableentries entity.
Defined in the Table Entries panel.
Nastran
Supported Card
Solver Description
Notes
DTABLE
Defines a table of real constants that are used in equations (see DEQATN entry).
Table entries referenced on DRESP2, DVPREL2
Altair Engineering

Objectives
Objective entities are used to define and store an objective for an optimization problem. Each optimization problem can only have one objective. Objectives are shown under the Objective folder within the Model Browser. The Optimization Browser View can be utilized to create, edit, and delete optimization problems. Objectives do not have a display state. Objectives have an active and export state. The active state of an objective controls the listing of the objective in the Model Browser and any of its views. If an objective entity is active, then it is listed in the Model Browser and any of its views. If an objective entity is inactive, then it is not listed in the Model Browser or any of its views. The export state of an objective entity controls whether or not that objective is exported when the custom export option is utilized. The all export option is not affected by the export state of an objective. The active and export states of objective entities can be controlled using the Entity State Browser. The data names associated with objectives can be found in the data names section of the HyperMesh Reference Guide.
The following panels can be used to create and edit objectives: Objective
Solver Card Support for Objectives


Altair Engineering
Supported Card
Solver Description
Supported Parameters objective
Notes
DESOBJ
Objective function, can occur before the first SUBCASE statement or within a subcase (depending on the response type). Supported as an objective. Objective functions for minmax (maxmin) problems. Supported as an objective.
Defined in the Objective panel.
MINMAX MAXMIN
Defined in the Objective panel.
Nastran
Some of the functionality of the optimization capability is general. This includes the equation utility, delete , rename , renumber, and reorder functions. To set up an optimization problem, responses, an objective function and constraints need to be defined. Further, design variables need to be defined. The optimization panels have separate Delete , Rename , Renumber, and Reorder panels to manipulate optimization entries. These can be reached through the Optimization menu. Supported Card Solver Description Supported Parameters Notes
DESOBJ
Selects the DRESP1 or DRESP2 entry to be used as the design objective.
Objective function, can be in or out of the load step; Belongs in the subcase section
MAXMIN
Objective functions for maxmin problems. Objective functions for minmax problems.
MINMAX
Altair Engineering


Altair Engineering
Objective References
Objective reference entities are used to define and store objective references for an optimization problem. Objective references are shown under the DesignObjectiveReference folder within the Model Browser. The Optimization Browser View can be utilized to create, edit, and delete optimization problems. Objective references do not have a display state. Objective references have an active and export state. The active state of an objective reference controls the listing of the objective reference in the Model Browser and any of its views. If an objective reference entity is active, then it is listed in the Model Browser and any of its views. If an objective reference entity is inactive, then it is not listed in the Model Browser or any of its views. The export state of an objective reference entity controls whether or not that objective reference is exported when the custom export option is utilized. The all export option is not affected by the export state of an objective reference. The active and export states of objective reference entities can be controlled using the Entity State Browser. The data names associated with objective references can be found in the data names section of the HyperMesh Reference Guide.
The following panels can be used to create and edit objective references: OBJ Reference
Solver Card Support for Objective References

Altair Engineering

Supported Card
Solver Description
Notes
DOBJREF
Reference definition for minmax (maxmin) optimization problems. Supported as an objectivereference.
Defined in the Obj Reference panel.

Altair Engineering
Optimization Constraint Screenings

Optimization constraint screening entities are used to define and store constraint screening data for optimization problems. Optimization constraint screenings are shown under the OptidScreens folder within the Model Browser. The Optimization Browser View can be utilized to create, edit, and delete optimization problems. Optimization constraint screenings do not have a display state. Optimization constraint screenings have an active and export state. The active state of an optimization constraint screening controls the listing of the optimization constraint screening in the Model Browser and any of its views. If an optimization constraint screening entity is active, then it is listed in the Model Browser and any of its views. If an optimization constraint screening entity is inactive, then it is not listed in the Model Browser or any of its views. The export state of an optimization constraint screening entity controls whether or not that optimization constraint screening is exported when the custom export option is utilized. The all export option is not affected by the export state of a optimization constraint screening. The active and export states of optimization constraint screening entities can be controlled using the Entity State Browser. The data names associated with optimization constraint screenings can be found in the data names section of the HyperMesh Reference Guide.
The following panels can be used to create and edit optimization constraint screenings: Constr Screen
Solver Card Support for Optimization Constraint Screenings

An optimization problem is set up by defining responses, which are in turn constrained or set as objectives. Design variables identify the varying quantities in an optimization problem.
Altair Engineering

All of the optimization panels are available from the Optimization menu when the RADIOSS (Bulk Data), OptiStruct user profile is loaded.
Supported Card
Solver Description
Notes
DSCREEN
Constraint screening. Supported as an optimizationconstraintscreenin g entity.
Defined in the Constr Screen panel.
Nastran
Supported Card
Solver Description
Notes
DSCREEN
Defines screening data for constraint deletion.
Constraint screening

Altair Engineering
Optimization Controls
Optimization control entities are used to define and store controls for optimization problem run. Optimization controls are shown under the OptiControls folder within the Model Browser. The Optimization Browser View can be utilized to create, edit, and delete optimization problems. Optimization controls do not have a display state. Optimization controls have an active and export state. The active state of an optimization control controls the listing of the optimization control in the Model Browser and any of its views. If an optimization control entity is active, then it is listed in the Model Browser and any of its views. If an optimization control entity is inactive, then it is not listed in the Model Browser or any of its views. The export state of an optimization control entity controls whether or not that optimization control is exported when the custom export option is utilized. The all export option is not affected by the export state of an optimization control. The active and export states of optimization control entities can be controlled using the Entity State Browser. The data names associated with optimization controls can be found in the data names section of the HyperMesh Reference Guide.
The following panels can be used to create and edit optimization controls: Opti Control
Solver Card Support for Optimization Entities

Altair Engineering

Supported Card
Solver Description
Supported Parameters optimizationcontrol
Notes
DOPTPRM
Optimization control card. Supported as an optimizationcontrol entity.
Defined in the Opti Control panel. If an unsupported argument is encountered on importing a DOPTPRM card, the data is stored as UNSUPPORTED_DO PTPRM on the DOPTPRM card. This may be reviewed or edited through the card editor. It is also possible to create an unsupported DOPTPRM card using the UNSUPPORTED_DO PTPRM option on the opticontrol card image.
Nastran
Supported Card
Solver Description
Notes
DOPTPRM
Overrides default values of parameters used in design optimization.
Optimization control card

Altair Engineering
Altair Engineering

Control Cards
Control card entities are used to create solver control cards such as results file I/O options, CPU and memory limits, and others. A solver interface template must be loaded which defines control cards in order to create and edit control cards. Control cards are shown under the Card folder within the Model Browser. The following panels can be used to create and edit control cards: Control Cards
Solver Card Support for Control Cards

Supported Card
Solver Description
Notes
/ADMESH/GLOBAL Defines the global parameters. /ALE/DISP Describes the displacement formulation.

Altair Engineering
/ALE/DONEA
Describes the ALE grid velocity. Describes the spring formulation. Describes the standard formulation. Describes the Euler formulation. Description of advanced mass scaling in the model Describes the analysis flags. Describes the architecture flag. Sets the run name, the version of the input manual, the number of Starter run and input and work unit systems. Describes the computation Aero-Acoustic formulation. Describes the Rayleigh damping. Describes the shell default values initialization. Describes the solid default values initialization. Describes the initial state file. Describes the input-output flags. Describes the memory request. Describes the nodal random
/ALE/SPRING
/ALE/STANDARD
/ALE/ZERO
/AMS
/ANALY /ARCH
/BEGIN
/CAA
/DAMP
/DEF_SHELL
/DEF_SOLID
/INISTA /IOFLAG
/MEMORY
/RANDOM
Altair Engineering

noise. /SPHGLO Describes the SPH global parameters. Describes the SPMD computation. Improvement of error messages for stamping applications Describes the title. Describes the local unit system. Describes the upwind coefficient.
/SPMD
/STAMPING
/TITLE /UNIT
/UPWIND
Control cards are used to support many different things for the RADIOSS (Bulk Data), OptiStruct user profile. The following I/O option entries are supported as control cards when appearing before the first SUBCASE statement. In many cases, information supplied on these entries is overridden by repeated definitions within subcases.
Supported Card
Solver Description
Notes
ACCELERATION
Controls the output of acceleration results
Found under GLOBAL_OUPUT_REQU EST. Supported as an output option on the subcase definition when it appears within a subcase. (Use the edit button in the Loadsteps panel.)

Altair Engineering
ANALYSIS
Flag indicating that only analysis is to be performed (i. e. no optimization), CHECK overrides ANALYSIS.
Supported as an output option on the subcase definition when it appears within a subcase. (Use the edit button in the Loadsteps panel.)
CHECK
Flag indicating that only a check run is to be performed (i.e. no analysis or optimization). CHECK overrides ANALYSIS. Subcase information for explicit analysis Found under GLOBAL_OUPUT_REQU EST. Found under GLOBAL_OUPUT_REQU EST. Supported as an output option on the subcase definition when it appears within a subcase. (Use the edit button in the Loadsteps panel.)
CONTF
CSTRAIN
Controls the output of strain results for composite shells.
CSTRESS
Controls the output of stress results for composite shells.
DAMAGE
Controls the output of fatigue damage results.
Altair Engineering

DENSITY
Controls the output of density results from a topology or freesize optimization. Controls the output of density results from a topology or freesize optimization. Controls the creation of the . hgdata file. Controls the output of displacement (and rotation) results. Found under GLOBAL_OUPUT_REQU EST. Supported as an output option on the subcase definition when it appears within a subcase. (Use the edit button in the Loadsteps panel.)
DENSRES
DESHIS
DISPLACEMENT
DMIGNAME
Defines the name given to the reduced matrices written to an external data file. Controls the echo of input data to the .out or .echo files. Defines the prefix to be used for the saving and retrieval of external eigenvalue data files. Controls the output of element force results. Found under GLOBAL_OUPUT_REQU EST. Supported as an output option on the subcase definition when it appears within a subcase. (Use the edit button in the Loadsteps panel.)
ECHO
EIGVNAME
ELFORCE
ENERGY
Subcase information for explicit analysis Controls the output of element FORMAT Found under
ESE

Altair Engineering
strain energy results.
TYPE DMIG ESE_V1
GLOBAL_OUPUT_REQU EST. Supported as an output option on the subcase definition when it appears within a subcase. (Use the edit button in the Loadsteps panel.) Found under GLOBAL_OUPUT_REQU EST. Supported as an output option on the subcase definition when it appears within a subcase. (Use the edit button in the Loadsteps panel.)
FLUX
Controls the gradient and flux output for heat transfer analysis.
FORMAT
Controls the format of results output.
Formats are: H3D (default), HM, FLX, OPTI, OUTPUT2, PUNCH, PATRAN, APATRAN, NONE. Found under GLOBAL_OUPUT_REQU EST. Supported as an output option on the subcase definition when it appears within a subcase. (Use the edit button in the Loadsteps panel.)
GPFORCE
Controls the output of grid point force results.
GPSTRESS
Controls the output of grid point stress results (available for PSOLID components only).
Altair Engineering

HISOUT
Controls the contents of the . hgdata file. When using the two-file setup, INFILE indicates the prefix of the file containing the bulk data information. Controls the output of fatigue life results. Its extension must be . fem.
INFILE
LIFE
LOADLIB
Defines the libraries to be loaded for external responses (DRESP3). Requests force output for a set of joints and/or force elements from multi-body dynamics subcases. Requests output for all formats for only a subset of the model and results. Found under GLOBAL_OUPUT_REQU EST.
MBFORCE
MODEL
This option is intended for multi-body dynamics and transient solution sequences with which users often require results for only a subsection of a model, but it is applied to all solution sequences. Found under GLOBAL_OUPUT_REQU EST. Supported as an output option on the subcase definition when it appears within a subcase. (Use the edit button in the Loadsteps panel.)
MPCFORCES
Controls the output of MPC force results.

Altair Engineering
MSGLMT
Can be used in the I/O Options section to limit the number of ERROR, WARNING and INFORMATION messages output, or to elevate a WARNING or INFORMATION message to an ERROR. Defines a set of frequencies at which results are output for frequency response analysis.
TYPE (ERROR, WARNING) VALUE (OFF, NONE) TYPE_ID VALUE_INT Found under GLOBAL_OUPUT_REQU EST. Supported as an output option on the subcase definition when it appears within a subcase. (Use the edit button in the Loadsteps panel.)
OFREQUENCY
OLOAD
Controls the output of applied force results.
OTIME
Defines a set of times at which results are output for transient analysis. Defines the path to, and the prefix of, the results files output by RADIOSS (Bulk Data), OptiStruct. Controls the frequency and format of results output by RADIOSS (Bulk Data), OptiStruct. Can be used in the I/O Options section to request output of acoustic grid participation factors for all frequency response subcases. GRIDS (SETG_SID) GRIDF (SETFL_SID) FREQUENCY (SETF_SID)
Found under GLOBAL_OUPUT_REQU EST.
OUTFILE
OUTPUT
PFGRID
Altair Engineering

NULL RPCUTOFF PFMODE Can be used in the I/O Options section to request output of modal participation factors for all frequency response subcases. STRUCTURE (STRUCTMP, FREQUENCY, FILTER, NULL, RPCUTOFF) FLUID (FLUIDMP, STRUCTMP, PANELMP, FREQUENCY, FILTER, NULL, RPCUTOFF) PFPANEL Can be used in the I/O Options section to request output of acoustic panel participation factors for all frequency response subcases. PANEL FREQUENCY (SETF_SID) FILTER NULL RPCUTOFF PRESSURE Controls the output of pressure results. Found under GLOBAL_OUPUT_REQU EST. Supported as an output option on the subcase definition when it appears within a subcase. (Use the edit button in the Loadsteps panel.) PROPERTY Controls the output of the property definitions used in the last iteration of an optimization. Controls the output of unretained optimization constraints. Flag that indicates that a restart run is to be performed. Also indicates the prefix of the .sh file to be used as the starting iteration for the restart.
RESPRINT
RESTART

Altair Engineering
RESULTS
Controls the frequency of output of analytical results during an optimization. Controls the form and type of modal participation acceleration output during an analysis. Found under GLOBAL_OUPUT_REQU EST. Supported as an output option on the subcase definition when it appears within a subcase. (Use the edit button in the Loadsteps panel.) Found under GLOBAL_OUPUT_REQU EST. Supported as an output option on the subcase definition when it appears within a subcase. (Use the edit button in the Loadsteps panel.)
SACCELERATION
SDISPLACEMENT
Controls the form and type of modal participation displacement output during an analysis
SCREEN
Controls the information echoed to the screen during a run. Controls the output of responses and sensitivities for size and shape design variables to a Microsoft Excel spreadsheet. Controls the frequency of output of responses and sensitivities to a Microsoft Excel spreadsheet. Controls the output of shape optimization results from a shape, topography or freeshape optimization. Controls the frequency of output of the state files (.sh and .grid). Controls the output of singlepoint force of constraint Found under GLOBAL_OUPUT_REQU
SENSITIVITY
SENSOUT
SHAPE
SHRES
SPCFORCES
Altair Engineering

results.
EST. Supported as an output option on the subcase definition when it appears within a subcase. (Use the edit button in the Loadsteps panel.)
STRAIN
Controls the output of elemental strain results.
STRESS
Controls the output of elemental stress results.
SORTING (SORT1, SORT2)
Found under GLOBAL_OUPUT_REQU FORMAT (HM, H3D, EST. OPTI, PUNCH, OUTPUT2, PATRAN, Supported as an output option on the subcase APATRAN) definition when it appears FORM (COMPLEX, within a subcase. (Use REAL, IMAG, the edit button in the PHASE, BOTH) Loadsteps panel.) TYPE (ALL, VON, PRINC, MAXS, SHEAR, TENSOR, DIRECT) LOCATION (CENTER, CUBIC, SGAGE, CORNER, BILIN) RANDOM (PSDF) STRESS_OPT (YES, NONE, NO, ALL, SID, PSID)
SVELOCITY
Controls the form and type of modal participation displacement output during an analysis,
Found under GLOBAL_OUPUT_REQU EST. Supported as an output option on the subcase definition when it

Altair Engineering
appears within a subcase. (Use the edit button in the Loadsteps panel.) SUBTITLE Defines a default subtitle for a RADIOSS (Bulk Data), OptiStruct model. Individual subcases may have their own SUBTITLE definitions which are supported on the subcase definition (use the edit button in the Loadsteps panel). These will override the default subtitle. OS_RAM OS_RAM_INIT CARDLENGTH RAM_SAFETY RAMDISK SYNTAX SPSYNTAX LOADTEMP NPROC_CPU PLOTELID SCRFMODE THERMAL Controls the temperature output for heat transfer analysis. Found under GLOBAL_OUPUT_REQU EST. Supported as an output option on the subcase definition when it appears within a subcase. (Use the edit button in the Loadsteps panel.) THICKNESS Controls the output of thickness results from topology, free-size, or size optimization. Can be used in the I/O Options or Subcase Information sections to request thinning and thickness output for all Found under GLOBAL_OUPUT_REQU EST.
SYSSETTING
Run control
THIN
Altair Engineering

geometric nonlinear analysis subcases or individual geometric nonlinear analysis subcases respectively. TITLE Defines a title for a RADIOSS (Bulk Data), OptiStruct model. Defines a temporary directory where scratch files will be written. RADIOSS (Bulk Data), OptiStruct allows multiple TMPDIR entries, but only one instance is currently supported.
TMPDIR
UNITS
Defines a system of units for the model. Controls the output of velocity results. Found under GLOBAL_OUPUT_REQU EST. Supported as an output option on the subcase definition when it appears within a subcase. (Use the edit button in the Loadsteps panel.)
VELOCITY
XSHLPRM
Defines default shell element parameters for geometric nonlinear analysis. Defines default SOLID properties for geometric nonlinear analysis.
XSOLPRM
The following Global Matrix Selectors are supported as control cards: Global Matrix Selector B2GG Solver Description Supported Parameters Notes
Identifies a DMIG bulk data entry as a viscous damping matrix.

Altair Engineering
K2GG
Identifies a DMIG bulk data entry as a stiffness matrix. Can be used in the Subcase number_of_k2pps Information section to select a direct input stiffness matrix, which is not included in normal modes. Identifies a DMIG bulk data entry as a structural element damping matrix. Identifies a DMIG bulk data entry as a mass matrix. Identifies a DMIG bulk data entry as a load matrix.
K2PP
K42GG
M2GG
P2G
Other RADIOSS (Bulk Data), OptiStruct cards supported as control cards: Supported Cards Solver Description Supported Parameters INTER INFOR FSET SSET NORMAL SHNEPS DSKNEPS INTO SRCHUNIT MAXSGRID CONTPRM Defines the default properties of all contacts STATIC_CONTACT (CONTGAP, GPAD, MU1, MU2, STIFF) SLIDE_EXPLICIT (BMULT, C1 - C6, FDAMP, FGAP, FILT, FRIC, Notes
ACMODL
Defines the fluid-structure interface parameters.
Altair Engineering

FRICPEN, GAPMAX, GAPMIN, IBC, IDEL, IGAP, IFFILT, IFRIC, ISTF, SDAMP, STFAC, STMAX, STMIN, TEND, TSTART) TIED_EXPLICIT (DS, IDEL2) UNSUPPORTED_C ONTPRMS DESVARG Defines an override for design variable settings. Defines units for multi-body dynamics and component mode synthesis solution sequences. Defines defaults for fields 3, 7, and 8 on all GRID entries. Defines parameters for gap element connectivity and configuration. The following GAPPRM arguments are supported: CHKRUN, CKGPDIR, GAPCMPL, GAPGPRJ, HMGAPST, PRTSW, ERRMSG. If an unsupported argument is encountered on importing a PARAM card, the data is stored as UNSUPPORTED_PARAM S on the PARAM card. It is also possible to create an unsupported PARAM card using the UNSUPPORTED_PARAM S option.
DTI_UNITS
GRDSET
GAPPRM
PARAM
Defines RADIOSS (Bulk Data), The following OptiStruct run parameters. PARAM arguments are supported: ALPHA1, ALPHA2, ALPHAFL1, ALPHAFL2, AMLSASPC, AMLSMAXR, AMLSUCON, AMLS, AMLSNCPU, AUTOSPC, AUTOSPRT, CB2, CHECKEL, CHKGPDIR, CHECKMAT, CK2,

Altair Engineering
CM2, CMFTINIT, CMFTSTEP, COUPMASS, CP2, DFREQ, DUPTOL, EFFMAS, EXPERTNL, EXTOUT, FLEXH3D, FLIPOK, FRIC, FZERO, G, GAPOFFSET, GMAR, GMAR1, HASHASSM, INREL, INRGAP, ITAPE, KDAMP, KGRGD, MBDH3D, MEMTRIM, MODETRAK, NEGMASS, OGEOM, OMACHRP, OMID, POST, POSTEXT, PRGPST, REANAL, RBMEIG, SH4NRP, SORTCON, SS2GC4, W3, W4, WTMASS. SWLDPRM Defines parameters for CWELD connectivity search. The following SWLDPRM arguments are supported: CHKRUN, GSPROJ, PROJTOL, PRTSW, ERRMSG.
Other control cards for the RADIOSS (Bulk Data Format), OptiStruct interface: Supported Cards Solver Description Supported Parameters Notes
BULK_UNSUPPOR TED_ CARDS
If a line (not a continuation line) occurs after the BEGIN BULK statement in an input file and starts with a keyword that is not recognized or supported,
Altair Engineering

then the entire card gets written to BULK_UNSUPPORTED_C ARDS. It is also possible to manually define an unsupported bulk data card using the BULK_UNSUPPORTED_C ARDS. BULK_UNSUPPORTED_C ARDS are exported near the bottom of the exported RADIOSS (Bulk Data), OptiStruct input file, just before the ENDDATA statement. CTRL_UNSUPPOR TED_ CARDS If a line (not a continuation line) occurs before the BEGIN BULK statement and before the first SUBCASE statement and starts with a keyword that is not recognized or supported, then the entire card gets written to CTRL_UNSUPPORTED_C ARDS. It is also possible to manually define data cards appearing above the first SUBCASE statement using the CTRL_UNSUPPORTED_C ARDS. CTRL_UNSUPPORTED_C ARDS are exported near the top of the exported RADIOSS (Bulk Data), OptiStruct input file, just before the first SUBCASE statement. DEBUG Some special or custom features can be accessed

Altair Engineering
through the use of 'debug, <string>, <real>' statements. GLOBAL_CASE_C ONTROL ANALYSIS, CMETHOD, CMSMETH, CNTNLSUB, DEFORM, DESVAR, DLOAD, FATDEF, It also handles the data FATPARM, selector DESVAR, used to FATSEQ, FREQ, IC, select a set of design variables INVEL, LOAD, for use in an optimization run. MBSIM, METHOD_FLUID, It also handles the output METHOD_STRUCT, control OMODES, used to MLOAD, MOTION, define a set of modes for MPC, NLOAD, output requests. NLPARM, OMODES, RANDOM, RWALL, RWALADD, SDAMPING_FLUID, SDAMPING_STRUC T, SPC, STATSUB, SUPORT1, TEMP, TEMP_LOAD, TSTEP, XHIST, XHISADD Handles the data selectors FREQ, METHOD, MPC, SDAMPING and SPC appearing above the first SUBCASE statement. This control card OMODES is also supported as an output option on the subcase definition when it appears within a subcase. (Use the edit button in the Loadsteps panel.)
INCLUDE_BULK
This control card is retained to support old database files. This control card is retained to support old database files. $HMBEGINDOC and $HMENDDOC indicate a section of comment cards which are supported on import and export. The comments are stored on control card Model Documentation. This information is exported at the top of the
INCLUDE_CTRL
Model Documentation
Altair Engineering

exported RADIOSS (Bulk Data), OptiStruct input file. OSDIAG Some special diagnostic information can be processed through the use of 'osdiag, <integer>, <integer>, <real>, <real>' statements.
Abaqus
Control cards define model information, which needs to be specified only once in the input file. The following Abaqus keywords are supported as control cards: Supported Card Solver Description Supported Parameters NO CHECKS NO CHANGES DELETE SLAVE *DEPVAR Specify solution-dependent state variables Print a heading on the output svcount Notes
*CONSTRAINT CONTROLS
Reset overconstraint checking controls
*HEADING
Title MultipleLines
*PREPRINT
Select printout for the analysis CONTACT input file processor. ECHO HISTORY MASS PROPERTY MODEL
*RESTART
Save and reuse data and analysis results
READ WRITE STEP INC END STEP FREQUENCY OVERLAY

Altair Engineering
Actran
The last step before creating the Actran input deck is completing control cards, which define the properties of the model that are not directly related to the mesh. You can define the title, analysis specifications, dimensions of the problem, interfaces between incompatible meshes, a color map and frequency response function solution, external structural vibration, and acoustic sources. Control cards can be accessed from the Control Cards panel: Supported Card Solver Description Supported Parameters Type of analysis (Frequency, Modal Extraction, Time Response, External Matrices) Solver (KRYLOV, SPARSE, SUPERLU, CG_ILU) Frequency n_freq n_k_freq BC_MESH Define an excitation from a previous computation performed in Nastran, Actran, or Abaqus. Surface GAP_TOL PLANE_TOL MESH format, file name RESULTS format, type, file name Dimension Define the dimension of the problem. Define interfaces for incompatible meshes. Dimension (3D, 2D, 2D AXI) n_interfaces 2D, 3D, or axisymmetric The excitation must be defined in two files: a mesh file and a results file defining the vibration on each node. Notes
Analysis
Specify options about the analysis
Specify: Frequency or modal analysis Frequency range and/or number of modes The solver
Interface
Optional. Each interface must be linked with two coupling surfaces.
LIGHTHILL
Use for predicting broadband aero-acoustic noise Include a file containing the FLOW data block.
HDF File name num_hdf_la FLOW FORMAT (ACTRAN, HDF) Used for further convected acoustic simulations
MEAN_FLOW
Altair Engineering

Flow file name OUTPUT_FRF Define field points on the model (virtual microphone). PLT file name fieldpoint storage_nodes OUTPUT_MAP Define color map solutions OS Command Actran type Output format Results file name Mesh file name Output step field point mesh color map superelement color map SOURCE Define acoustic sources in the n_sources model (virtual loudspeaker). Generate the SUPERELEMENT data block, specifying the OP2 file name. SUPER ELEMENT BLOCK DEFINITION MESH FILE NAME MATRIX PARAMETERS FILE NAME MATRIX COEFFICIENT FILE NAME MODES FILE NAME super_point_load super_storage_node Title Specify a name for the analysis. Model Name Description Optional
SUPER_ELEMENT
ANSYS
The input translator recognizes the ANSYS cards listed below. If an unsupported field is found in a card, a message is displayed on the status bar. The messages are also printed to the file ansys.msg. General slash commands, SOLUTION commands, POST1 commands, and POST26 commands are

Altair Engineering
referred to as control cards. Unrecognized cards are written to a *.hmx file.
Supported Card
Solver Description
Supported Parameters ACELX, ACELY, ACELZ Value
Notes
ACEL
Specifies the linear acceleration of the structure. Defines the mass matrix multiplier for damping. Specifies the analysis type and restart status.
ALPHAD
ANTYPE
Type (STATIC, BUCKLE, MODAL, HARMIC, TRANS, SUBSTR, SPECTR) Status (NEW, REST)
ARCLEN
Activates the arc length method.
Key (OFF/ON), MAXARC, MINARC
ARCTRM
Controls termination of the arc- Lab (OFF, L, U), length solution VAL, NODE, DOF (UX, UY, UZ, ROTX, ROTY, ROTZ)
/ASSIGN
Reassigns a file name to an ANSYS file identifier.
ldent Fname Key (off/on)
AUTOTS
Specifies whether to use automatic time stepping or load stepping. Sets the program mode to "batch" Defines the stiffness matrix multiplier for damping. Assigns a uniform body force load to all nodes. Specifies buckling analysis
/BATCH
List
BETAD
Value
BFUNIF
Lab, Value
BUCOPT
METHOD, NMODE,
Altair Engineering

options CGLOC Specifies the origin location of the acceleration coordinate system.
SHIFT, LDMULTE XLOC, YLOC, ZLOC
CGOMGA
Specifies the rotational velocity CGOMX, CGOMY, of the global origin. CGOMZ Specifies the rotational acceleration of an element component about a userdefined rotational axis. CM_NAME, DOMEGAX, DOMEGAY, DOMEGAZ, X1, Y1, Z1, X2, Y2, Z2 CM_NAME, DOMEGAX, DOMEGAY, DOMEGAZ, X1, Y1, Z1, X2, Y2, Z2, KSPIN Lab, VALUE, TOLER, NORM, MINREF
CMDOMEGA
CMOMEGA
Specifies the rotational velocity of an element component about a user-defined rotational axis.
CNVTOL
Sets convergence values for nonlinear analyses.
/COM
Places a comment in the output. Copies a file.
n/a
/COPY CRPLIM
FileName
Specifies the creep criterion for CRCR, Option automatic time stepping. Specifies the rotational acceleration of the global origin. Deletes a file. Specifies the time step sizes to be used for this load step. DCGOX, DCGOY, DCGOZ
DCGOMG
/DELETE DELTIM
FileName DTIME, DTMIN, DTMAX Carry
DMPRAT DOF
Sets a constant damping ratio. RATIO Adds degrees of freedom to LAB1 - LAB10

Altair Engineering
the current DOF set. DOMEGA Specifies the rotational acceleration of the structure. Specifies the system of units for magnetic field problems. Specifies the type of equation solver. Specifies extrapoloation of integration point results. Reorient SOLID elements' axes Fills a table of element values for further processing. Specifies an expansion pass of an analysis. DOMGX, DOMGY, DOMGZ LAB, VAL
EMUNIT
EQSLV
Lab, TOLER, MULT
ERESX
Key
EORIENT
ETYPE, Dir, Tol
ETABLE
LAB, ITEM, COMP
EXPASS
Key
HARFRQ
Defines the frequency range in FREQB, FREQE the harmonic response analysis. Specifies the phase angle for the harmonic analysis expansion pass. Specifies harmonic analysis options. ANGLE
HREXP
HROPT
Method, MAXMODE, MINMODE, MCout, Damp REIMKY, CLUST, MCONT Key
HROUT
Specifies the harmonic analysis output options. Specifies that inertia relief calculations are to be performed. Specifies stepped or ramped loading within a load step.
IRLF
KBC
Key
KUSE
Specifies whether or not to Key reuse the triangularized matrix.
Altair Engineering

LNSRCH
Activates a line search to be used with Newton-Raphson.
Key
LSSOLVE
Reads and solves multiple load LSMIN, LSMAX, steps. LSINC Scales the load vector for mode superposition analyses. Defines the damping ratios as a function of mode. FACT
LVSCALE
MDAMP
STLOC, V1, V2, V3, V4, V5, V6
MODE
Specifies the harmonic loading MODE, ISYM term for this load step. Specifies modal analysis options. Method, NMODE, FREQB, FREQE, PRMODE, Nrmkey
MODOPT
MXPAND
Specifies the number of modes NMODE, FREQB, to expand and write for a FREQE, Ecalc, modal or buckling analysis. SIGNIF Sets the key to terminate an analysis. KSTOP, DLIM, ITLIM, ETLIM, CPLIM
NCNV
NEQIT
Specifies the maximum number of equilibrium iterations for nonlinear analyses. Includes large-deflection effects in a static or full transient analysis.
NEQIT
NLGEOM
Key
NROPT
Specifies the Newton-Raphson Option, --, Adptky options in a static or full transient analysis. Specifies the number of NSBSTP, NSBMAX, substeps to be taken this load NSBMIN, Carry step. Specifies the rotational velocity OMEGX, OMEGY, of the structure. OMEGZ, KSPIN
NSUBST
OMEGA

Altair Engineering
OUTRES
Controls the solution data written to the database. Enters the database results post-processor. Activates a predictor in a nonlinear analysis. Prints the solution results for elements. Specifies whether prestress effects are calculated or included. Activates a coordinate system for printout or display of results. Loads a pretension section.
Item, FREQ, Cname
/POST1
n/a
PRED
Sskey, Lskey
PRESOL
PRESOLITEM
PSTRES
Key
RSYS
KCN
SLOAD
SECID, PLNLAB, KINIT, KFD, FDVALUE, LSLOAD, LSLOCK n/a NVAR, ITEMLABEL, COMPLABEL, SOLUNAME n/a Key
/SOLU SOLU
Enters the solution processor. Specifies solution summary data per substep to be stored.
SOLVE SSTIF
Starts a solution. Activates stress stiffness effects in a nonlinear analysis. Defines subtitles.
/STITLE
NLINE TITLE
SUBOPT
Specifies options for subspace SUBSIZ, NPAD, iteration eigenvalue extraction. NPERBK, NUMSSI, NSHIFT, Strmck, JCGITR Passes a command string to the operating system. String
/SYS
Altair Engineering

TIME TIMINT TINTP
Sets the time for a load step. Turns on transient effects. Defines transient integration parameters.
Time Key, Lab GAMMA, ALPHA, DELTA, THETA, OSLM, TOL, --, --, AVSMOOTH, ALPHAF, ALPHAM Title_string Value
/TITLE TOFFST
Defines a main title. Specifies the temperature offset from absolute zero to zero. Specifies automatic MDOF generation. Defines the reference temperature for the thermal strain calculations. Specifies transient analysis options.
TOTAL
NTOT, NRMDF
TREF
TREF
TRNOPT
Method, MAXMODE, Dmpkey, MINMODE, MCout, TINTOPT
TUNIF
Assigns a uniform temperature TEMP to all nodes. Annotates the database with the system of units used. Label, LENFACT, MASSFACT, TIMEFACT, TEMPFACT, TOFFSET, CHARGEFACT, FORCEFACT, HEATFACT
/UNITS
UNSU_END UNSU_PREP7
LS-DYNA

Altair Engineering
*DATABASE_OPTION cards in Keyword are listed from the Setup drop down menu, after selecting Control Cards. An active field is output as the appropriate individual card in the data deck. A control card can be in one of three states: State Undefined Color Gray Explanation The control card was either never created or was deleted. Any control card viewed in the card previewer is activated. A card that has been defined may be disabled. The attributes for that card remain; however, the control card is not output.
Defined (See Note)
Green
Inactive
Red
Note:
Those control cards that are defined (green in the control card editor) are output.
Default values for attributes are common throughout the card previewer. A default value field has one of the following states: State Default = ON Description In this state, the field label color is yellow and no data entry is allowed. To override a default value field, pick the yellow field label. When you override a default value field, the label text color changes to cyan and you can enter data in the field.
Default = OVERRIDDEN
The following keywords are supported: Supported Card Solver Description Supported Parameters Notes
*CONTROL_ACCURA CY
Define control parameters that can OSU, INN, PIDOSU improve the accuracy of the calculation. Define control parameters for contact interface force update during each adaptive cycle. Activate adaptive meshing. FACTIN, DFACTR
*CONTROL_ADAPST EP
*CONTROL_ADAPTIV
ADPFREQ, ADPTOL,
Altair Engineering

ADPOPT, MAXLVL, TBIRTH, TDEATH, LCADP, IOFLAG, AdaptiveOptions To refine the element mesh along a curve. IDSET, N, SMIN, ITRIOPT ITYPE (PartSetID, PartID), Set global control parameters for the Arbitrary Lagrange-Eulerian and Eulerian calculations. DCT, NADV, METH, AFAC - EFAC, START, END, AAFAC, VFACT, PRIT, EBC, PREF, NSIDEBC
*CONTROL_ADAPTIV E_ CURVE
*CONTROL_ALE
*CONTROL_BULK_ VISCOSITY *CONTROL_CHECK
Q1, Q2, IBQ Reset the default values of the bulk viscosity coefficients globally. Check for various problems in the mesh. PID, IFAUTO, CONVEX, ADPT, ARATIO, ANGLE, SMIN, Shell
*CONTROL_COARSE N
ICOARSE, ANGLE, Adaptively de-refine (coarsen) a shell mesh by selectively merging NSEED, PSID four adjacent elements into one. Change defaults for computation with contact surfaces. SLSFAC, RWPNAL, ISLCHK, SHLTHK, PENOPT, THKCHG, ORIEN, ENMASS, USRSTR, USRRFC, NSBCS, INTERM, XPENE, SSTHK, ECDT, TIEDPRJ UNLENG, UNTIME, UNFORC, TIMIDL, FLIPX - FLIPZ, SUBCYL CPUTIM, IGLST
*CONTROL_CONTAC T
*CONTROL_COUPLIN Change defaults for MADYMO3D/ G CAL3D coupling.
*CONTROL_CPU
Control CPU time.
*CONTROL_DYNAMIC Initialize stresses and deformation NRCYCK, DRTOL, _ in a model to simulate a preload. DRFCTR, DRTERM, TSSFDR, IRELAL, RELAXATION EDTTL, IRDFLG

Altair Engineering
*CONTROL_EFG
Define controls for the mesh-free computation. Provide controls for energy dissipation options
ISPLINE, IDILA, ININT, IMLM, ETOL HGEN, RWEN, SLNTEN, RYLEN
*CONTROL_ENERGY
*CONTROL_EXPLOSI VE_ SHADOW *CONTROL_HOURGL ASS
Compute detonation times in n/a explosive elements for which there is no direct line of sight. Set the default values of the hourglass control to override the default values. IHQ, QH
*CONTROL_IMPLICIT_ Define parameters for automatic AUTO time step control during implicit analysis.
IAUTO, ITEOPT, ITEWIN, DTMIN, DTMAX, DTEXP, DTMAX_Option NMODE
*CONTROL_IMPLICIT_ Activate implicit buckling analysis BUCKLE when termination time is reached.
*CONTROL_IMPLICIT_ Activate implicit dynamic analysis IMASS, GAMMA, BETA, TDYBIR, DYNAMICS and define time integration TDYDTH, TDYBUR, constants. IRATE *CONTROL_IMPLICIT_ Activate implicit eigenvalue EIGENVALUE analysis and define associated input parameters. NEIG, CENTER, LFLAG, LFTEND, RFLAG, RHTEND, EIGMTH, SHFSCL, NEIG_Option IMFLAG, DT0, IMFORM, NSBS, IGS, CNSTN, FORM, ZERO_V, IMFLAG_Option IRFLAG THRESH
*CONTROL_IMPLICIT_ Activate implicit analysis and GENERAL define associated control parameters.
*CONTROL_IMPLICIT_ Allows analysis of linear static INERTIA_RELIEF problems that have rigid body modes. *CONTROL_IMPLICIT_ Defines control parameters for LINEAR linear portion of implicit solver
*CONTROL_IMPLICIT_ Request calculation of constraint NSIDC MODES and/or attachment modes for later NSIDA
Altair Engineering

use in modal analysis using *PART_MODES. *CONTROL_IMPLICIT_ Defines control parameters for NONLINEAR nonlinear portion of implicit solver *CONTROL_IMPLICIT_ Optional card that applies to SOLUTION implicit calculations.Used to specify whether a linear or nonlinear solution is desired. *CONTROL_IMPLICIT_ Optional card that applies to SOLVER implicit calculations. The linear equation solver performs the CPUintensive stiffness matrix inversion. *CONTROL_IMPLICIT_ Optional card that applies to STABILIZATION implicit calculations. Artificial stabilization is required for multistep unloading in implicit springback analysis. *CONTROL_IMPLICIT_ Specify termination criteria for TERMINATION implicit transient simulations. *CONTROL_MPP_ DECOMPOSITION_ AUTOMATIC Instructs the program to apply a simple heuristic to try to determine the proper decomposition for the simulation. NSOLVR, ILIMIT, MAXREF, DCTOL, ECTOL, RCTOL, LSTOL, ABSTOL LSOLVR, LPRINT, NEGEV, ORDER, DRCM, DRCPRM, AUTOSPC, AUTOTOL
IAS, SCALE, TSTART, TEND, SCALE_Option
DELTAU
n/a
*CONTROL_MPP_ DECOMPOSITION_C HECK _SPEED *CONTROL_MPP_ DECOMPOSITION_ CONTACT_DISTRIBUT E
Modifies the decomposition n/a depending on the relative speed of the processors involved.
Ensures that the indicated contact ID1 - ID5 interfaces are distributed across all processors, which can lead to better load balance for large contact interfaces. Ensures that the indicated contact ID1 - ID5 interferences are isolated on a single processor, which can lead to decreased communication.
*CONTROL_MPP_ DECOMPOSITION_ CONTACT_ISOLATE

Altair Engineering
*CONTROL_MPP_ DECOMPOSITION_FI LE *CONTROL_MPP_ DECOMPOSITION_ METHOD *CONTROL_MPP_ DECOMPOSITION_ NUMPROC *CONTROL_MPP_ DECOMPOSITION_S HOW *CONTROL_MPP_ DECOMPOSITION_ TRANSFORMATION
Allow for pre-decomposition and a Name subsequent run or runs without having to do the decomposition. Specify the decomposition method to use. Name
Specify the number of processors for decomposition.
Allows display of the final decomposition.
n/a
Specifies transformations to apply TYPE(1) to modify the decomposition. VAL(1) n/a
*CONTROL_MPP_IO_ Suppress the output of all dump NOD3DUMP files.
*CONTROL_MPP_IO_ Suppresses the output of all dump n/a NODUMP files and full deck restart files. *CONTROL_MPP_IO_ Suppresses the output of the full NOFULL deck restart files. n/a
*CONTROL_MPP_IO_ Swap bytes on some of the output n/a SWAPBYTES files. *CONTROL_OUTPUT Set miscellaneous output parameters. NPOPT, NEECHO, NREFUP, IACCOP, OPIFS, IPNINT, IKEDIT, IFLUSH NCPU, NUMRHS, CONST, PARA
*CONTROL_PARALLE Control parallel processing usage L for shared memory computers by defining the number of processors invoking the optional consistency of the global vector assembly.
*CONTROL_REMESHI Provide control over the remeshing RMIN, RMAX, VF_LOSS, MFRAC, NG of solids which are meshed with the solid tetrahedron element type DT_MIN 13.
Altair Engineering

*CONTROL_RIGID
Special control options related to rigid bodies and the rigid-flexible bodies. Provide controls for computing shell response.
LMF, JNTF, ORTHMD, PARTM, SPARSE, METALF WRPANG, ESORT, IRNXX, ISTUPD, THEORY, BWC, MITER, PROJ ESORT, FMATRIX, NIPTETS, SWLOCL SOLN, NLQ, ISNAN, LCINT
*CONTROL_SHELL
*CONTROL_SOLID
Provide controls for solid element response.
*CONTROL_SOLUTIO Specify the analysis solution N procedure if thermal only or coupled thermal analysis is performed. *CONTROL_SPH Provide controls for computing SPH particles.
NCBS, BOXID, DT, IDIM, MEMORY, FORM, START, MAXV, CONT, DERIV, INI
LCT, LCS, T_ORT, *CONTROL_SPOTWE Provides factors for scaling the PRTFLG, T_ORS, LD_ failure force resultants of beam RPBHX BEAM spot welds as a function of their parametric location on the contact segment and the size of the segment. *CONTROL_STRUCTU Write out a LS-DYNA structured RED input deck for version 970. *CONTROL_STRUCTU Write out a LS-DYNA structured RED input deck for version 970. _TERM Termination will occur after the structured input file is written. *CONTROL_SUBCYC LE Control time step subcycling. n/a
n/a
n/a
*CONTROL_TERMINA Stop the job. TION
ENDTIM, ENDCYC, DTMIN, ENDENG, ENDMASS REFMAX, TOL, DCP, LUMPBC, THLSTL, NLTHPR, PHCHPN
*CONTROL_THERMA L_ NONLINEAR
Set parameters for a nonlinear thermal or coupled structural/ thermal analysis.

Altair Engineering
*CONTROL_THERMA L_ SOLVER
Set options for the thermal solution in a thermal only or coupled structural-thermal analysis. Set time step controls for the thermal solution in a thermal only or a coupled structural/thermal analysis. Set structural time step size control using different options.
ATYPE, PTYPE, SOLVER, CGTOL, GPT, EQHEAT, FWORK, SBC TS, TIP, ITS, TMIN, TMAX, DTEMP, TSCP, LCTS
*CONTROL_THERMA L_ TIMESTEP
*CONTROL_TIMESTE P
DTINIT, TSSFAC, ISDO, TSLIMIT, DT2MS, LCTM, ERODE, MS1ST CDAMP, FLOW, FHIGH, PSID
*DAMPING_FREQUE NCY_ RANGE *DAMPING_GLOBAL
Provides approximately constant damping over a range of frequencies. Define mass weighted nodal damping that applies globally to the nodes of deformable bodies and to the mass center of rigid bodies.
LCID, VALDMP, STX STZ, SRX - SRZ
*DATABASE_ABSTAT Specify time interval and file type for Airbag statistics time history file output. *DATABASE_AVSFLT Specify time interval for AVS database output. *DATABASE_BINARY Dt for complete output states. _ D3PLOT *DATABASE_BINARY Dynamic relaxation database. _ D3DRLF DT, LCDT, NOBEAM, NPLTC, PSETID, IOOPT CYCLE
*DATABASE_BINARY Dt for time history data of element DT, LCDT _ subsets. D3THDT *DATABASE_BINARY Binary output restart files. Define _ output frequency in cycles. D3DUMP DT
Altair Engineering

*DATABASE_BINARY ALE interface force database _ FSIFOR *DATABASE_BINARY Dt for output of contact interface _ data. INTFOR *DATABASE_BINARY Binary output restart file. Define _ output frequency in cycles. RUNRSF *DATABASE_BINARY Flag to specify output of extra _ time history data to XTFILE at XTFILE same time as D3THDT file. *DATABASE_BNDOU Specify time interval and file type T for Boundary condition forces and energy time history file output. *DATABASE_DEFGE O *DATABASE_DEFOR C Specify time interval deformed geometry file output. Specify time interval and file type for discrete element forces time history file output. Specify time interval and file type for element data time history file output.
DT, LCDT, NOBEAM, NPLTC, PSETID
DT, LCDT
DT
DT
*DATABASE_ELOUT
*DATABASE_EXTENT Specify output database to be _AVS written. *DATABASE_EXTENT Specify output database to be _ written. BINARY
VTYPE, COMP
NEIPH, NEIPS, MAXINT, STRFLAG, SIGFLG, EPSFLG, RLTFLG, ENGFLG, CMPFLG, IEVERP, BEAMIP, DCOMP, SHGE, STSSZ, N3THDT, IALEMAT, NINTSLD, PKP_SEN, SCLP, MSSCL, THERM VTYPE, COMP
*DATABASE_EXTENT Specify output database to be _ written.

Altair Engineering
MOVIE *DATABASE_EXTENT _ MPGS *DATABASE_EXTENT _ SSSTAT *DATABASE_FORMA T *DATABASE_GCEOU Specify time interval and file type T for Geometric contact entities force time history file output *DATABASE_GLSTAT Specify time interval and file type for global model data time history file output. *DATABASE_JNTFOR Specify time interval and file type C for joint force time history file output *DATABASE_MATSU M Specify time interval and file type for material energies time history file output Specify time interval for movie output Specify time interval for MPGS Specify time interval and file type for nodal interface forces time history file output VTYPE, COMP
PSID(1), ArrayCount
IFORM, IBINARY
*DATABASE_MOVIE
*DATABASE_MPGS *DATABASE_NCFOR C
*DATABASE_NODFO Specify time interval and file type R for nodal force groups time history file output *DATABASE_NODOU Specify time interval and file type T for nodal point data time history file output *DATABASE_OPTION Control cards for all ASCII output ABSTAT,
Altair Engineering

ABSTAT_CPM, AVSFLT, BNDOUT, DCFAIL, DEFGEO, DEFORC, ELOUT, GCEOUT, GLSTAT, JNTFORC, MATSUM, MOVIE, MPGS, NCFORC, NODFOR, NODOUT, RBDOUT, RCFORC, RWFORC, SBTOUT, SECFORC, SLEOUT, SPCFORC, SPHOUT, SSSTAT, SWFORC, TPRINT, TRHIST *DATABASE_RBDOU Specify time interval and file type T for rigid body data time history file output. *DATABASE_RCFOR C Specify time interval and file type for resultant interface forces time history file output.
*DATABASE_RWFOR Specify time interval and file type C for rigid wall forces time history file output. *DATABASE_SBTOU T Specify time interval and file type for Seat belt time history file output. Specify time interval and file type for cross section forces time history file output Specify time interval and file type for sliding interface energy time history file output Specify time interval and file type for SPC reaction forces time history file output
*DATABASE_SECFO RC
*DATABASE_SLEOU T
*DATABASE_SPCFO RC
*DATABASE_SPHOU Specify time interval and file type T for SPH element data time history file output

Altair Engineering
*DATABASE_SPRING Create spring forward nodal force _ file. FORWARD *DATABASE_SSSTAT Specify time interval and file type for Subsystem data time history file output *DATABASE_ SUPERPLASTIC_ FORMING Specify the output intervals to the superelastic forming output files.
IFLAG
DTOUT
*DATABASE_SWFOR Specify time interval and file type C for nodal constraint reaction forces time history file output *DATABASE_TPRINT Specify time interval and file type for thermal time history file output. Thermal output from a coupled structural/thermal or thermal only analysis. *DATABASE_TRACE R Tracer particles will save a history of either a material point or a spatial point into an ASCII file, TRHIST. Tracer particle history information METHOD, SL, SF, ELREF, PSIDm, UNDCT TIME, TRACK, X, Y, Z
*DATABASE_TRHIST
*INTERFACE_ Calculate the deviation of the part COMPENSATION_NE from its intended design of the W stamped part and automatically compensate the tool to minimize the deviation, modify the trimming curve after the die modification, and automatically detect the undercut problem
MADYMO
Supported Card
Solver Description
Supported Parameters N2, O2, CO2, CO,
Notes
GAS
Specify a gas (molecular
Altair Engineering

weight and specific heat coefficients).
HE, NE, AR, H2, H2O, NH3, H2S, C6H6, N20
MARC
Supported Card
Solver Description
Supported Parameters ASSUMED (ON/ OFF)
Notes
ASSUMED (ASSUMED STRAIN) AUTO INCREMENT
AUTOINC (ON/OFF) Fraction_a, MaxNumOflnc, NumOfRecPerInc, MaxFracTotLoad, MaxMulArcLength,
CONSTANT DILATATION CONTACT_TYPE
CONSTANT (ON/ OFF) CONTACT_TYPE (MECHANICAL DISPLACEMENT, HEAT TRANSFER, COUPLING DIFFUSION, ACOUSTIC BOUNDARY, JOULE HEAT) DISTLOADS (ON/ OFF) ListMax, ElemMax, NodeMax
DIST LOADS
ELSTO
ELSTO (ON/OFF), ELSTO_BUFSIZE FEATURE (ON/ OFF), feature, FEATURE_IDS_NU M FINITE (ON/OFF)
FEATURE
FINITE

Altair Engineering
FOLLOW FOR
FOLLOWFOR (ON/ OFF), DistLoads, BndryCond, PointLoads LARGEDISP (ON/ OFF) MPCCHECK (ON/ OFF), MpcOrder NOLIST (ON/OFF) OPTIMIZE (ON/ OFF), AlgoType, OptMesh, UnitNMesh, UnitOCord, Print ORIENT (ON/OFF), NoOfSets, UnitNo PLASTICITY (ON/ OFF), PLASTICITY (value) POST (ON/OFF), NoOfElemVar, UnitNumNewBinPost , UnitNumPreBinPost, FileGenFlag, UnitNumPreFrmtPos t POST_DATA POST_DATA_NUM
LARGE DISP
MPC_CHECK
NO LIST OPTIMIZE
ORIENTATION
PLASTICITY
POST
RBE
RBE (ON/OFF), RBE_AnalType, RBE2_LDISP, RBE3_LDISP SHELLSECT (ON/ OFF), SHSECTSimRule, SHSECTIntBeam, SHSECTIntShell SIZING (ON/OFF), Attribute
SHELL SECT
SIZING
Altair Engineering

SOLVER
SOLVER (ON/OFF), SolverType, NonSymSysFlag, NonPosDefSys, PreConType, 4ByteWords, AUTOSPC, ConGradlter, InitTrialFlag, InfoSolType, TotConGradConv SUMMARY (ON/ OFF), UnitNo, IncFreq TABLE_LOAD, TABLE_MAT, TABLE_CON TIE (ON/OFF), TIE_ATTRI1, TIE_ATTR2, TIE_MAXNODES, TIE_ATTR4 TITLE (ON/OFF), TITLE_DATA, TITLE_DATA_NUM UPDATE (ON/OFF), Blank, IncrRot, IntStrStiff VERSION NUMBER
SUMMARY
TABLE
TIE
TITLE
UPDATE
VERSION
Nastran
Supported Card
Solver Description
Supported Parameters INTER, INFOR, FSET, SSET, NORMAL, METHOD, SHNEPS, DSKNEPS, INTOL, ALLSSET, SRCHUNIT
Notes
ACMODL
Defines modeling parameters for the interface between the fluid and the structure.

Altair Engineering
BEGIN BULK
Designates the end of the Case Control Section and/or the beginning of a Bulk Data Section.
n/a
When the model is created from HyperMesh, this card is on by default.
BULKUNSUPPORTED_ CARD
n/a
On import, all unsupported bulk data will be written into this card. You can edit the card. If CEND and SUBCASE exist, on import, all unsupported cards between CEND and the first SUBCASE will be written into this card. You can edit the card. If SUBCASE does not exist and BEGIN BULK exists, all unsupported cards between CEND and BEGIN BULK will be written into this card. When the model is created from HyperMesh, this card is on by default.
CASEUNSUPPORTED_ CARD
n/a
CEND
n/a
DIAG
Requests diagnostic output or special options.
DIAG DIAGIDLEN When the model is created from HyperMesh, this card is on by default. If CEND exists in the imported deck, on import, all unsupported cards before CEND will be written into this card. You can edit the card. If CEND does not exist, on import, all unsupported cards before BEGIN BULK will be written into this card.
ENDDATA
Designates the end of the Bulk n/a Data Section.
EXEC_UNSUPPOR TED_ CARDS
n/a
GLOBAL CASE
LABEL, ANALYSIS, AUTOSPC,
Altair Engineering

CONTROL
BCONTACT, CMETHOD, DEFORM, DLOAD, FREQ, IC, LOAD, LOADSET, METHOD_FLUID, METHOD_STRUCT, MPC, NLPARM, RANDOM, SDAMPING_FLUID, SDAMPING_STRUC T, SPC, SUPORT1, TEMP, TEMP_LOAD, TSTEP ACCELERATION, DISPLACEMENT, EKE, ELFORCE, ESE, GPFORCE, GPSTRESS, MCFRACTION, MPCFORCES, OFREQ, OLOAD, OTIME, PARTN, SACCELERATION, SDISPLACEMENT, SPCFORCES, STRAIN, STRESS, SVECTOR, SVELOCITY, THERMAL, VELOCITY CP, CD, SEID, Defines default options for fields 3, 7, 8, and 9 of all GRID Single Point Constraint 1- 6 entries Specifies a comment. Inserts an external file into the input file Inserts an external file into the input file Inserts an external file into the input file l1, l2 number of includes in bulk number of includes in ctrl number of includes in exec
GLOBAL OUTPUT REQUEST
GRDSET
ID INCLUDE_BULK
INCLUDE_CTRL
INCLUDE_EXEC

Altair Engineering
K2PP
Selects direct input stiffness matrices, which are not included in normal modes Sets the maximum number of output lines.
number of k2pps
MAXLINES
nmax
The maximum number of lines is 999999999 (Nastran default). By selecting this control card, you are forcing HyperMesh to not write BEGIN BULK CARD By selecting this control card, you are forcing HyperMesh to not write the CEND card. By selecting this card, you are forcing HyperMesh to not write the END_BULK card.
OMIT_BEGIN_BUL K
OMIT_CEND
OMIT_END_BULK
PARAM
Specifies values for parameters.
ALPHA1, ALPHA2, AMLS, AMLSNCPU, ASING, AUTOSPC, AUTOSPRT, BAILOUT, COUPMASS, CURV, CURVPLOT, DDRMM, EPPRT, EPZERO, FZERO, G, GFL, GRDPNT, GRDEQ, INREL, K6ROT, LGDISP, MARCSLHT, MAXRATIO, MPCX, NEWSEQ, OGEOM, OLDSEQ, OMACHPR, OMID, OUNIT2, POST, POSTEXT, PRGPST, SPCGEN, TINY, USETPRT, WTMASS. setid, SET_realList
On import, all unsupported PARAM cards are written into the UNSUPPORTED PARAMS block within PARAM CARD in the Control Cards panel. You can edit this data block.
SET CARD
Defines a set of element or grid point numbers to be
Only real number sets can be created using control
Altair Engineering

plotted.
cards. For node and element sets, see Sets.
SOL
Specifies the solution sequence or main subDMAP to be executed.
Analysis (Statics, Normal Modes, Buckling, Nonlinear Statics, Dir. Complex Eigenvalues, Dir. Frequency Response, Dir. Transient Response, Model Complex Eigenvalues, Modal Frequency Response, Modal Transient Response, Nonlin. Transient Resp., Design Optimization, Statics & Lin. Heat Transfer, Implicit) n/a
SUBTITLE
Defines a subtitle that will appear on the second heading line of each page of printer output. Overrides default values of parameters for CFAST, CWELD, and CSEAM connectivity search.
SWLDPRM
GSMOVE, NREDIA
TIME
Sets the maximum CPU and I/ MaxIO O time. Defines a character string that n/a will appear on the first heading line of each page of NX Nastran printer output.
TITLE
PAM-CRASH 2G
Supported Card
Solver Description
Supported
Notes

Altair Engineering
Parameters NA Imported Model Documentation n/a The input deck can contain model documentation text that is imported and exported via the comment lines. For decks not written by HyperMesh, all comment lines before the first noncomment line are treated as model documentation. For decks written by HyperMesh, the documentation lines must be placed in a block that begins with the line $HMBEGINDOC and ends with the line $HMENDDOC. The text can be created and changed using the card previewer. This card is always overwritten by the current model documentation. This card is not created during FE input process. You can create this card, but once this card is defined, only this will be exported. You can access macros from the PAM-CRASH 2G user profile to append or overwrite the information from Imported Model Documentation to this card. Added in PAM-CRASH 2004
NA
Model Documentation
n/a
AIRBAGCHECK
Airbag Check
Option (YES/NO) Qualifier (VOLUME, ORIENT)
ANALYSIS
Analysis
Analysis Selection (EXPLICIT, IMPLICIT_PCG)
Altair Engineering

AUTOSLEEP CCTRL / Contact Control Parameters
Option (YES/NO) ITER_INIPEN_N ITER_FORCE_N ITER_FORCE_EPS LEAKFILTER This card contains all the information about the interfaces control parameters such as initial penetration.
COUPLING
Coupling
MADYMO, PAMFLOW Yes/No Execution (None, QUIT, STOP)
DATACHECK
Data Check
DEBUG DCOMP ECTRL /
Debug DMP Domain Decomposition Element Control Parameters
Yes/No Type, Direction ANTIDRILL, SPRINGBACK, STRAINRATE, RATEFILTER, RATESCALE, RATECURVE, KINJ, ENERMONT, MET3DLOAD n/a This card contains all the information about the element control parameters.
ENDDATA
End of Data
Cards after the ENDDATA card are ignored.
FILE INCLU /
File Name Include Cards
FILENAME fileName NUM_INCLUDES
INPUTVERSION MAXMEMORY MERGEGAP METRIC/
Input Version Max Memory Common Node Merge Initial Metric
n/a MAXMEMORY tolerance metric, NUM_METRICS Option (YES/NO) Added in PAM-CRASH
METRICCHECK
Metric Check

Altair Engineering
Tolerance OCTRL / Output Control Parameters THPOUTPUT INTERVAL TIOD DSYOUTPUT INTERVAL PIOD Output Parameters Selction (All, THOUTPUT, DSYOUTPUT, RSTOUTPUT, PRTOUTPUT, TOTAL_STRAIN, PRINT, PREFILTER, GLBTHP, SHLTHP, NODPLOT, SOLPLOT, SHLPLOT, BEAPLOT, MPPOUTPUT, RBODY_DISPLAY, FPM OUTPUT, SPHPLOT) Thpoutput Qualifier (Interval, Point, Curve) Dsyoutput Qualifier (Interval, State, Curve) PIPE RESTARTFILES RUNEND/ Pipe Restart Files End Of Run Definition Yes/No NumberOfFiles TIME SENSOR_OPT RWALL_KIN_CHEC K SHELLCHECK Shell Check Option (YES/NO)
2004 This card contains all the information about the output of data, e.g., PRINT, SHLTHP, THPOUTPUT, DSYOUTPUT, GLBTHP, BEAPLOT, etc. In card previewer you have the option of defining all the parameters.
Yes/No Warpage, Aspect, QMinAngle, QMaxAngle, TMinAngle, TMaxAngle
Altair Engineering

SIGNAL SOLIDCHECK
Signalling Solid Check
Yes/No Yes/No Aspect, QMinFace, QMaxFace, TMinFace, TMaxFace
SOLID4N
Solid4N
YES/NO
This card must be defined in order to support 4-noded tetra elements by using SOLID / keyword in PAMCRASH 2004. Its value should be set to "YES".
SOLVER SPCTRL /
Solver
CRASH, STAMP
KERNAL_OPT NUMBER_NEIGHBO RS_OPT BUFFER_MULTIPLIE RS_OPT NN_ACCELERATOR_ OPT X_SYMMETRY_OPT Y_SYMMETRY_OPT Z_SYMMETRY_OPT ARTVISC_TENSION_ OPT MOMENTUM_FORMA LISM_OPT DIMENSION_1D_OPT DIMENSION_2D_OPT
SPH /
IDKERN, FACNEI, ISPHAC, LSPHAC, X, Y, Z, IOPSPH, IPBDIM, SECLA, FACBUF, IVSH Stop Run ENERGY, CPULIMIT, TIMESTEP, CONTACT_DIVERG ENCE
STOPRUN

Altair Engineering
SUBRUN
Substructure Run
filename, TimeFactor, LengthFactor, FrameNumber NUM_SUBRUNS
SUBTA /
Substructure Run Link Table
EQUIVALENCE, IDNEW, IDOLD NUM_EQUIV_NODE S
TCTRL /
Timestep Control Parameters
Timestep This card contains all the Parameters information about the time Selection (All, step control parameters. INITIAL, PREFER, SCALE, STIFFNESS_SCALE , INIT_MASS_SCALE, NODAL, DYNA_MASS_SCAL E, SHELL_TIMESTEP) TITLE Length, Mass, Time, Temperature All unsupported information found in the input deck is imported in this card. You can edit this card.
TITLE / UNIT
Title Unit System
Unsupported Cards
PERMAS
The following cards are supported in the PERMAS interface:
Supported Card
Solver Description
Supported Parameters Name
Notes
$COMPONENT
Component Input Bracket Header Line
Altair Engineering

TYPE (AXISYM, DISCRETE) DOFFIELDS (DISP, TEMP, PRES, POTE, MATH) $ECHO Controls the echo print of PERMAS data input lines. Definition of viscous or structural modal damping. HEADER, ON, OFF, GEN DOFTYPE KIND TYPE $SYSTEM Opens the bracket for input of system data. Name PARAMETER MODDAMP UnsupportedDataLin esSystem This option is available in the SYSTEM card as a separate checkbox.
$MODDAMP
Samcef
Supported Cards
Solver Description
Supported Parameters N/A
Notes
UNSUPPORTED_CA RDS
See also Browsers HyperMesh Entities & Solver Interfaces Model Setup

Altair Engineering
Element Property and Material Assignement Rules

Element property and material assignment rules are based on the current user profile (solver interface). There are two basic solver groups supported in HyperMesh; solver group1 and solver group2. Solver Group1 RADIOSS (Bulk Data Format), OptiStruct Abaqus Nastran Solver Group2 RADIOSS (Block Format) LS-DYNA PAM-CRASH ANSYS PERMAS
Element Property and Material Assignment Rules for Solver Group1 Components have no card images. Properties are assigned to elements or components using the following rules in order: 1. If a property is assigned directly to an element, then that property is the elements property regardless of any other property assignments. Properties are assigned directly to elements on the properties:assign subpanel. If there is no property assigned directly to an element, then the property assigned to the component the element is organized into becomes the elements property. Properties are assigned to components on the components:assign subpanel. If there is no property assigned to the component, then the element has no property assignment.
2.
3.
Materials are always assigned to properties. Elements are assigned the material of their assigned property. If a property has no assigned material, then all elements assigned to that property have no material assignment. Materials are assigned to properties on the properties:assign subpanel or properties:assign subpanel.
Solver Group1 Property/Material Assignment Schematic
Altair Engineering

Element Property and Material Assignment Rules for Solver Group 2 Components have card images; typically "part" card images. Properties and materials are assigned to components only. There is no property or material assignment directly to elements. Properties and materials are assigned to components on the components:assign subpanel. Elements are assigned the property and material assigned to the component in which they are organized into. If a component is not assigned a property or material, then all elements within that component have no property or material assignment.

Altair Engineering
Solver Group2 Property/Material Assignment Schematic
See also Components Properties Materials Browsers HyperMesh Entities & Solver Interfaces Model Setup
Altair Engineering

Supported Cards by Solver

RADIOSS (Block Format) /ACCEL /ACTIV /ACTN /ADMAS /ADMESH/GLOBAL /ADMESH/SET /ALE/BCS /ALE/DISP /ALE/DONEA /ALE/MAT /ALE/SPRING /ALE/STANDARD /ALE/ZERO /AMS /ANALY /ARCH /BCS /BEAM /BEGIN /BRIC20 /BRICK /CAA /CLOAD /CONVEC /CYL_JOINT /DAMP /DEF_SHELL /DEF_SOLID /DFS/DETLINE /DFS/DETPOIN /DFS/LASER /DFS/WAV_SHA /EBCS

Altair Engineering
/FAIL /FAIL/CHANG /FAIL/CONNECT /FAIL/ENERGY /FAIL/FLD /FAIL/HASHIN /FAIL/JOHNSON /FAIL/LAD_DAM /FAIL/PUCK /FAIL/SPALLING /FAIL/TBUTCHER /FAIL/TENSSTRAIN /FAIL/USER1, FAIL/USER2 OR /FAIL/USER3 /FAIL/WIERZBICKI /FAIL/WILKINS /FAIL/XFEM /FRAME/FIX /FRAME/MOV /FRAME/MOV2 /FRAME/NOD /FUNCT /GRAV /GRBEAM /GRBEAM/BOX /GRBEAM/BOX2 /GRBEAM/BEAM /GRBEAM/GRBEAM /GRBEAM/MAT /GRBEAM/PART /GRBEAM/PROP /GRBEAM/SUBSET /GRBRIC /GRBRIC/BOX /GRBRIC/BOX2 /GRBRIC/BRIC /GRBRIC/GRBRIC /GRBRIC/MAT
Altair Engineering

/GRBRIC/PART /GRBRIC/PROP /GRBRIC/SUBSET /GRNOD /GRNOD/BOX /GRNOD/GENE /GRNOD/GRBEAM /GRNOD/GRBRIC /GRNOD/GRQUAD /GRNOD/GRSH3N /GRNOD/GRSHEL /GRNOD/GRSPRI /GRNOD/GRTRUS /GRNOD/MAT /GRNOD/NODE /GRNOD/NODENS /GRNOD/PART /GRNOD/PROP /GRNOD/SUBSET /GRNOD/SURF /GRPART /GRQUAD /GRQUAD/BOX /GRQUAD/BOX2 /GRQUAD/GRQUAD /GRQUAD/QUAD /GRQUAD/MAT /GRQUAD/PART /GRQUAD/PROP /GRQUAD/SUBSET /GRSH3N /GRSH3N/BOX /GRSH3N/BOX2 /GRSH3N/GRSH3N /GRSH3N/MAT /GRSH3N/PART /GRSH3N/PROP

Altair Engineering
/GRSH3N/SH3N /GRSH3N/SUBSET /GRSHEL /GRSHEL/BOX /GRSHEL/BOX2 /GRSHEL/GRSHEL /GRSHEL/MAT /GRSHEL/PART /GRSHEL/PROP /GRSHEL/SHEL /GRSHEL/SUBSET /GRSPRI /GRSPRI/BOX /GRSPRI/BOX2 /GRSPRI/GRSPRI /GRSPRI/PART /GRSPRI/PROP /GRSPRI/SPRI /GRSPRI/SUBSET /GRTRUS /GRTRUS/BOX /GRTRUS/BOX2 /GRTRUS/GRTRUS /GRTRUS/MAT /GRTRUS/PART /GRTRUS/PROP /GRTRUS/SUBSET /GRTRUS/TRUS /HEAT/MAT /IMPACC /IMPDISP /IMPTEMP /IMPVEL /INISTA /INITEMP /INIVEL /INIVEL/AXIS
Altair Engineering

/INTER /INTER/LAGMUL/TYPE7 /INTER/TYPE1 /INTER/TYPE2 /INTER/TYPE3 /INTER/TYPE5 /INTER/TYPE6 /INTER/TYPE7 /INTER/TYPE8 /INTER/TYPE9 /INTER/TYPE10 /INTER/TYPE11 /INTER/TYPE12 /INTER/TYPE14 /INTER/TYPE15 /INTER/TYPE18 /INTER/TYPE19 /INTER/TYPE20 /INTER/TYPE21 /INITHICK/V5 /IOFLAG /LEVSET /LINE /LINE/BOX /LINE/BOX2 /LINE/EDGE /LINE/GRBEAM /LINE/GRTRUS /LINE/MAT /LINE/PROP /LINE/SEG /LINE/SURF /MAT /MAT/B-K-EPS /MAT/BARLAT3 /MAT/BIMAT /MAT/BIPHAS

Altair Engineering
/MAT/BOLTZMAN /MAT/BOUND /MAT/CHANG /MAT/COMPSH /MAT/COMPSO /MAT/CONC /MAT/CONNECT /MAT/COSSER /MAT/COWPER /MAT/DAMA /MAT/DPRAG /MAT/DPRAG1 /MAT/ELAST /MAT/ELASTOMER /MAT/FABR_A /MAT/FABRI /MAT/FOAM_PLAS /MAT/FOAM_TAB /MAT/FOAM_VISC /MAT/GAS /MAT/GRAY /MAT/GURSON /MAT/HANSEL /MAT/HILL /MAT/HILL_MMC /MAT/HILL_TAB /MAT/HONEYCOMB /MAT/HYD_JCOOK /MAT/HYD_VISC /MAT/HYDPLA /MAT/HYDRO /MAT/JWL /MAT/K-EPS /MAT/KELVINMAX /MAT/LAW10 /MAT/LAW23 /MAT/LAW50 /MAT/LAW51
Altair Engineering

/MAT/LAW53 /MAT/LAW54 /MAT/LAW62 /MAT/LAW63 /MAT/LAW65 /MAT/LAW66 /MAT/LAW82 /MAT/LEE_T /MAT/LES_FLUID /MAT/OGDEN /MAT/PLAS_BRIT /MAT/PLAS_DAMA /MAT/PLAS_JOHNS /MAT/PLAS_TAB /MAT/PLAS_T3 /MAT/PLAS_ZERIL /MAT/RIGID /MAT/SAMP /MAT/STEINB /MAT/THERM /MAT/TSAI_TAB /MAT/UGINE_ALZ /MAT/USERij /MAT/VISC_TAB /MAT/VOID /MAT/ZERIL /MAT/ZHAO /MEMORY /MONVOL /MONVOL/AIRBAG /MONVOL/AIRBAG1 /MONVOL/AREA /MONVOL/COMMU /MONVOL/FVMBAG /MONVOL/GAS /MONVOL/PRES /MOVE_FUNC

Altair Engineering
/NODE /PART /PLOAD /PROP /PROP/BEAM /PROP/CONNECT /PROP/FLUID /PROP/INJECT1 /PROP/INJECT2 /PROP/INT_BEAM /PROP/KJOINT /PROP/PLY /PROP/POROUS /PROP/RIVET /PROP/SHELL /PROP/SH_COMP /PROP/SH_FABR /PROP/SH_ORTH /PROP/SH_PLY /PROP/SH_SANDW /PROP/STACK /PROP/SOLID /PROP/SOL_ORTH /PROP/SPH /PROP/SPRING /PROP/SPR_BEAM /PROP/SPR_GENE /PROP/SPR_PRE /PROP/SPR_PUL /PROP/TRUSS /PROP/TSHELL /PROP/TSH_ORTHO /PROP/TYPE0 /PROP/USER /QUAD /RADIATION /RANDOM
Altair Engineering

/RBE2 /RBE3 /RBODY /REFSTA /RIVET /RLINK /RWALL /RWALL/CYL /RWALL/PARAL /RWALL/PLANE /RWALL/SPHER /RWALL/THERM /SECT /SENSOR /SENSOR/ACCE /SENSOR/AND /SENSOR/DIST /SENSOR/INTER /SENSOR/NOT /SENSOR/OR /SENSOR/RWAL/ /SENSOR/SENS /SENSOR/TIME /SHELL /SH3N /SKEW/MOV /SKEW/MOV2 /SPHBCS /SPHCEL /SPHGLO /SPH/INOUT /SPH/RESERVE /SPMD /SPRING /STAMPING /SUBSET /SURF

Altair Engineering
/SURF/BOX /SURF/BOX2 /SURF/BOX/ALL /SURF/BOX/EXT /SURF/GRSHELL /SURF/MAT /SURF/MAT/ALL /SURF/MAT/EXT /SURF/PART /SURF/PART/ALL /SURF/PART/EXT /SURF/PROP /SURF/PROP/ALL /SURF/PROP/EXT /SURF/SEG /SURF/SRSH3N /SURF/SUBSET /SURF/SUBSET/ALL /SURF/SUBSET/EXT /SURF/SURF /TABLE /TETRA4 /TETRA10 /TH/ACCEL/ /TH/BEAM/ /TH/BRIC/ /TH/CYL_JO/ /TH/FRAME/ /TH/INTER/ /TH/MONV/ /TH/NODE/ /TH/QUAD/ /TH/PART/ /TH/RBODY/ /TH/RWALL/ /TH/SECTIO/ /TH/SH3N/
Altair Engineering

/TH/SHEL/ /TH/SPHCEL/ /TH/SPRING/ /TH/SUBS /TH/TRUSS/ /THERM_STRESS/MAT /TITLE /TRANSFORM/ROT /TRANSFORM/SCA /TRANSFORM/SYM /TRANSFORM/TRA /TRUSS /UNIT /UPWIND /VISC_PRONEY RADIOSS (Fixed Format) Accelerometer ADMAS MLAW0 MLAW1 MLAW2 MLAW3 MLAW4 MLAW6 MLAW10 MLAW14 MLAW19 MLAW21 MLAW22 MLAW23 MLAW24 MLAW25 MLAW27 MLAW28 MLAW32 MLAW33

Altair Engineering
MLAW34 MLAW35 MLAW36 MLAW38 MLAW40 MLAW42 Monitored Volume M_43_HILL_TAB PART Sections Sect Void/P0_VOID Sect Shell/P1_SHELL Sect Truss/P2_TRUS Sect Beam/P3_BEAM Sect Sprg/P4_SPRING Sect Rivet/P5_RIVET Sect Ort Sld/P6_SOL_ORTH Sect Abag Sect GenSpr/P8_SPR_GENE Sect OrtShl/P9_SH_ORTH Sect ComShl/P10_SH_COMP Sect ComShl2/P11_SH_SANDW Sect 3NSpr/P12_SPR_PUL Sect BemSpr/P13_SPR_BEAM Sect GenSol/P14_SOLID RADIOSS (Bulk Data Format) ACCELERATION ACCLR ACMODL ACSRCE ANALYSIS ASET ASET1 B2GG BMFACE
Altair Engineering

CAABSF CBAR CBEAM CBUSH CBUSH1D CDAMP1 CDAMP2 CDAMP3 CDAMP4 CELAS1 CELAS2 CELAS3 CELAS4 CGAP CGAPG CHACAB CHBDYE CHECK CHEXA (8-noded) CHEXA (20-noded) CMASS1 CMASS2 CMASS3 CMASS4 CMBEAM CMSMETH CMSPDP CONM1 CONM2 CONROD CONTACT CONTF CONTPRM CONV CORD1C CORD1R CORD1S

Altair Engineering
CORD2C CORD2R CORD2S CORD3R CORD4R CPENTA (6-noded) CPENTA (15-noded) CPYRA (5-noded) CPYRA (13-noded) CQUAD4 CQUAD8 CROD CSHEAR CSTRAIN CSTRESS CTETRA (4-noded) CTETRA (10-noded) CTRIA3 CTRIA6 CTUBE CVISC CWELD DAMAGE DAREA DCOMP DCONADD DCONSTR DDVAL DEBUG DEFORM DENSITY DENSRES DEQATN DESGLB DESHIS DESOBJ DESSUB
Altair Engineering

DESVAR DESVARG DISPLACEMENT DLINK DLINK2 DLOAD DMIGNAME DOBJREF DOPTPRM DPENTA6 DRESP1 DRESP2 DSCREEN DSHAPE DSHUFFLE DSIZE DSYSID DTABLE DTI_SPECSEL DTI_UNITS DTPG DTPL DVCREL1 DVCREL2 DVGRID DVMREL1 DVMREL2 DVPREL1 DVPREL2 ECHO EIGC EIGRL EIGVNAME EIGVRETRIEVE EIGVSAVE ELFORCE ENERGY

Altair Engineering
ESE EXCLUDE FATDEF FATEVNT FATLOAD FATPARM FATSEQ FLUX FORCE FORMAT FREQ FREQ1 FREQ2 FREQ3 FREQ4 FREQ5 FREQUENCY GAPPRM GLOBAL_CASE_CONTROL GPFORCE GPSTRESS GRAV GRDSET GRID GROUND HISOUT HM_ELAS HMSPRING IC INCLUDE_BULK INCLUDE_CTRL INFILE INVEL INVELB JOINT K2GG K2PP
Altair Engineering

K42GG LABEL LIFE LOAD LOADLIB M2GG MARKER MAT1 MAT2 MAT4 MAT5 MAT8 MAT9 MAT10 MATFAT MATS1 MATT1 MATT2 MATT8 MATT9 MATX02 MATX13 MATX27 MATX33 MATX36 MATX42 MATX44 MATX62 MATX65 MATX70 MATX82 MBACT MBCNTDS MBCNTR MBCRV MBDCRV MBDEACT

Altair Engineering
MBDSRF MBFORCE MBFRC MBFRCC MBLIN MBMNT MBMNTC MBPCRV MBSEQ MBSIM MBSIMP METHOD MINMAX MLOAD MODEL MODEWEIGHT MOMENT MOTION MOTNG MOTNGC MPC MPCADD MPCFORCE MPCFORCES MSGLMT NLOAD (Constraint Load) NLOAD (Case Control) NLOAD1 NLPARM NSM (Global Case Control Card) NSMADD NSM1 NSML1 OFREQUENCY OLOAD OMODES OSDIAG
Altair Engineering

OTIME OUTFILE OUTPUT P2G PAABSF PACABS PANEL PARAM PBAR PBARL PBEAM PBEAML PBUSH PBUSH1D PCOMP PCOMPG PCOMPP PCONT PCONV PDAMP PELAS PFAT PFBODY PFGRID PFMODE PFPANEL PGAP PLOAD PLOAD1 PLOAD2 PLOAD4 PLOTEL PLOTEL3 PLOTEL4 PLY PMASS PRBODY

Altair Engineering
PRESSURE PROD PROPERTY PSHEAR PSHELL PSOLID PTUBE PVISC PWELD QBDY1 QVOL RANDPS RBAR RBE2 RBE3 RESPRINT RESTART RESULTS RESVEC RFORCE RLOAD1 RLOAD2 RROD RSPEC RSPEC (Case Control) RWALL (Group) RWALL (Case Control) RWALLADD SCREEN SDAMPING SECT SENSITIVITY SENSOUT SET SHAPE SHRES SOLVTYP
Altair Engineering

SPC SPCADD SPCD SPCFORCES SPOINT STACK STATSUB STRAIN STRESS SUBCASE SUBTITLE SUPORT SUPORT1 SURF SWLDPRM SYSSETTING TABDMP1 TABLED1 TABLED2 TABLED3 TABLED4 TABLEFAT TABLEM1 TABLEM2 TABLEM3 TABLEM4 TABLES1 TABRND1 TEMP TEMPD THERMAL THICKNESS THIN TIC TIE TITLE TLOAD1

Altair Engineering
TLOAD2 TMPDIR TSTEP TTERM UNITS USET USET1 VELOCITY WEIGHT XDAMP XHIST (Output Block) XHIST (Case Control) XHISTADD XSHLPRM XSOLPRM XSTEP (Load Collector) Abaqus
To create Abaqus cards, load the Abaqus user profile and select the appropriate template (Standard.2d, Standard.3d, or Explicit). The supported Abaqus cards: *AMPLITUDE *BEAM ADDED INERTIA *BEAM GENERAL SECTION *BEAM SECTION *BIAXIAL TEST DATA *BLOCKAGE *BOUNDARY *BUCKLE *BULK VISCOSITY *CECHARGE *CECURRENT *CFILM *CFLUX *CHANGE FRICTION *CLEARANCE
Altair Engineering

*CLOAD *COHESIVE SECTION *COMBINED TEST DATA *CONDUCTIVITY *CONNECTOR BEHAVIOR *CONNECTOR CONSTITUTIVE REFERENCE *CONNECTOR CONTACT FORCE *CONNECTOR DAMPING *CONNECTOR ELASTICITY *CONNECTOR FAILURE *CONNECTOR FRICTION *CONNECTOR LOAD *CONNECTOR LOCK *CONNECTOR MOTION *CONNECTOR SECTION *CONNECTOR STOP *CONSTRAINT CONTROLS *CONTACT (General Contact) *CONTACT CLEARANCE *CONTACT CLEARANCE ASSIGNMENT *CONTACT CONTROLS *CONTACT CONTROLS ASSIGNMENT *CONTACT DAMPING (Explicit template) *CONTACT DAMPING (Standard templates) *CONTACT EXCLUSIONS *CONTACT FILE *CONTACT FORMULATION *CONTACT INCLUSIONS *CONTACT INTERFERENCE *CONTACT OUTPUT *CONTACT PAIR *CONTACT PRINT *CONTACT PROPERTY ASSIGNMENT *CONTACT PROPERTY ASSIGNMENT, PROPERTY=OFFSET FRACTION *CONTACT PROPERTY ASSIGNMENT, PROPERTY=THICKNESS *CONTROLS *COUPLING

Altair Engineering
*CREEP *CRUSHABLE FOAM *CRUSHABLE FOAM HARDENING *DAMPING *DASHPOT *DECHARGE *DENSITY *DEPVAR *DFLUX *DIAGNOSTICS *DIELECTRIC *DISTRIBUTING *DISTRIBUTING COUPLING *DISTRIBUTION *DLOAD *DSLOAD *DYNAMIC *DYNAMIC (Explicit) *EL FILE *EL PRINT *ELASTIC *ELEMENT *ELEMENT OUTPUT *ELEMENT PROPERTIES *ELSET *EMBEDDED ELEMENT *ENERGY FILE *ENERGY OUTPUT *ENERGY PRINT *EQUATION *EULERIAN SECTION *EXPANSION *FASTENER (SPOT WELD) *FASTENER PROPERTY *FILE FORMAT *FILM *FILTER
Altair Engineering

*FIXED MASS SCALING *FLUID BEHAVIOR *FLUID BULK *FLUID DENSITY *FLUID EXPANSION *FLUID PROPERTY *FREQUENCY *FRICTION (Explicit template) *FRICTION (Standard templates) *GAP *GASKET BEHAVIOR *GASKET CONTACT AREA *GASKET ELASTICITY *GASKET SECTION *GASKET THICKNESS BEHAVIOR *HEADING *HEAT TRANSFER *HYPERELASTIC *HYPERFOAM *INCREMENTATION OUTPUT *INERTIA RELIEF *INITIAL CONDITIONS (TYPE=PRESSURE) *INITIAL CONDITIONS (TYPE=TEMPERATURE) *INITIAL CONDITIONS (TYPE=VELOCITY) *INTEGRATED OUTPUT *INTEGRATED OUTPUT SECTION *JOINT *KINEMATIC *KINEMATIC COUPLING *LOAD CASE *MASS *MATERIAL *MEMBRANE SECTION *MODAL DYNAMIC *MODAL OUTPUT *MODEL CHANGE *MONITOR

Altair Engineering
*MPC *MULLINS EFFECT *NODAL THICKNESS *NODE *NODE FILE *NODE OUTPUT *NODE PRINT *NONSTRUCTURAL MASS *NSET *ORIENTATION *OUTPUT *PHYSICAL CONSTANT *PIEZOELECTRIC *PLANAR TEST DATA *PLASTIC *PREPRINT *PRE-TENSION SECTION *PRINT *RADIATE *RATE DEPENDENT *RELEASE *RESTART *RESTART *RIGID BODY *ROTARY INERTIA *SECTION CONTROLS *SFILM *SHEAR FAILURE *SHEAR TEST DATA *SHELL GENERAL SECTION *SHELL SECTION *SHELL TO SOLID COUPLING *SIMPLE SHEAR TEST DATA *SOLID SECTION *SPECIFIC HEAT *SPRING *STATIC
Altair Engineering

*STEADY STATE DYNAMICS *STEP *SURFACE *SURFACE BEHAVIOR (Explicit template) *SURFACE BEHAVIOR (Standard templates) *SURFACE INTERACTION (Explicit template) *SURFACE INTERACTION (Standard templates) *SURFACE PROPERTY ASSIGNMENT (Explicit template) *SURFACE SECTION *SURFACE SMOOTHING *SYSTEM *TEMPERATURE *TIE *TRANSFORM *TRANSVERSE SHEAR STIFFNESS *UNIAXIAL TEST DATA *USER MATERIAL *USER OUTPUT VARIABLES *VARIABLE MASS SCALING *VISCO *VISCOELASTIC *VOLUMETRIC TEST DATA Actran
The following Actran blocks are supported:
ACCELERATION ADMITTANCE ANALYSIS AXISYMMETRY BC_MESH BOUNDARY_CONDITION COUPLING_SURFACE DIMENSION DISCRETE DISPLACEMENT

Altair Engineering
DISTRIBUTED_LOAD DISTRIBUTED_PRESSURE ELEMENT FIELD_POINT_SURFACE FREQUENCY_DOMAIN IMPERVIOUS INCIDENT_SURFACE INFINITE ADMITTANCE INFINITE_DOMAIN INFINITE_ELEMENT INFINITE_FLUID INFINITE_MESH INTERFACE LIGHTHILL MATERIAL (FLUID) MATERIAL (SHELL) MATERIAL (SOLID) MATERIAL (POROUS_UP) MATERIAL (POROUS_RIGID) MATERIAL (VISCOTHERMAL) MESH MEAN_FLOW MODAL_BASIS MODAL_EXTRACTION MODAL_SURFACE NODE OUTPUT_FRF OUTPUT_MAP POINT_LOAD POROUS_UP PRESSURE RADIATING_SURFACE RAYLEIGH_SURFACE RIGID_POROUS SAVE SHELL SOLID
Altair Engineering

SOLVER SOURCE STIFFENER SUPER_CONNECTOR SUPER_ELEMENT TEMPERATURE_PRESSURE TITLE VELOCITY VISCOTHERMAL VISCOTHERMAL_FLUID ANSYS
The input translator recognizes the ANSYS cards listed below. If an unsupported field is found in a card, a message is displayed on the status bar. The messages are also printed to the file ansys.msg. General slash commands, SOLUTION commands, POST1 commands, and POST26 commands are referred to as control cards. Unrecognized cards are written to a *.hmx file.
ACEL ALPHAD ANTYPE ARCLEN ARCTRM /ASSIGN AUTOTS /BATCH BEAM3 BEAM4 BEAM23 BEAM24 BEAM44 BEAM54 BEAM188 BEAM189 BETAD /BFUNIF BF

Altair Engineering
BF_FLUE BF_HGEN BF_TEMP BFE_FLUE BFE_HGEN BFE_TEMP BUCOPT CE CERIG CGLOC CGOMGA CIRCU124 CMACEL CMDOMEGA CMOMEGA CMGRP CNVTOL /COM COMBIN14 COMBIN39 COMBIN40 CONTA171 CONTA172 CONTA173 CONTA174 CONTA175 CONTA177 CONTA178 CONTAC12 CONTAC48 CONTAC49 CONTAC52 ConvBulkTe ConvFilmCo /COPY CP_ELEC CP_STRUC
Altair Engineering

CRPLIM D_CONSTRNT D_TEMP D_VOLT DCGOMG /DELETE DELTIM DMPRAT DOF DOMEGA EMUNIT EQSLV ERESX EORIENT ETABLE EXPASS F_FLOW F_HEAT FLOTRAN FLUID FLUID29 FLUID30 FLUID80 FLUID116 FORCE FORCE2 HARFRQ HF118 HF119 HF120 HFLUX HM_COMP HREXP HROPT HROUT HYPER58 IC_CONSTRN

Altair Engineering
IC_TEMP IC_VOLT IRLF KBC KUSE LINK1 LINK8 LINK10 LINK31 LINK32 LINK33 LINK34 LINK68 LINK180 LNSRCH LOCAL LSSOLVE LVSCALE MASS21 MASS71 MAT MATRIX27 MDAMP\ MESH200 MODE MODOPT MP MPDATA MPC184 MPTEMP MXPAND N NBLOCK NCNV NEQIT NLGEOM NROPT
Altair Engineering

NSUBST OMEGA OUTRES PIPE16 PIPE18 PIPE20 PIPE60 PLANE2 PLANE13 PLANE25 PLANE35 PLANE42 PLANE53 PLANE55 PLANE67 PLANE75 PLANE77 PLANE78 PLANE82 PLANE83 PLANE121 PLANE145 PLANE146 PLANE162 PLANE182 PLANE183 PLANE223 /POST1 PRED PRESOL PRESSURE PRETS179 PSTRES RBE3 RSYS SECCONTROLS SECDATA

Altair Engineering
SECOFFSET SECTYPE SFE SHELL28 SHELL41 SHELL43 SHELL51 SHELL57 SHELL61 SHELL63 SHELL91 SHELL93 SHELL99 SHELL131 SHELL132 SHELL143 SHELL150 SHELL157 SHELL163 SHELL181 SHELL208 SHELL209 SHELL281 SLOAD SOLID5 SOLID45 SOLID46 SOLID62 SOLID64 SOLID69 SOLID70 SOLID72 SOLID73 SOLID87 SOLID90 SOLID92 SOLID95
Altair Engineering

SOLID96 SOLID97 SOLID98 SOLID117 SOLID147 SOLID148 SOLID164 SOLID168 SOLID185 SOLID186 SOLID187 SOLID191 SOLID226 SOLID227 SOLSH190 /SOLU SOLU SOLVE SSTIF /STITLE SUBOPT SURF151 SURF152 SURF153 SURF154 SURF156 /SYS TARGE169 TARGE170 TB TBDATA TIME TIMINT TINTP /TITLE TOFFST TOTAL

Altair Engineering
TREF TRNOPT TUNIF /UNITS VISCO88 VISCO107 Note: One component collector is created for every unique combination of Type, Real, Mat, and SECNUM. Surface loads on 1-D elements is not supported. Property collectors are created for each real set defined in the ANSYS deck. Material collectors are also created for each material ID encountered. The component in HyperMesh is different from the component (CM) in ANSYS.
LS-DYNA
The following cards are supported by LS-DYNA: *AIRBAG_ADIABATIC_GAS_MODEL_ID *AIRBAG_ALE *AIRBAG_ADVANCED_ALE *AIRBAG_HYBRID_CHEMKIN_ID *AIRBAG_HYBRID_ID *AIRBAG_HYBRID_JETTING_CM_ID *AIRBAG_HYBRID_JETTING_ID *AIRBAG_INTERACTION_ID *AIRBAG_LINEAR_FLUID_ID *AIRBAG_LOAD_CURVE_ID *AIRBAG_PARTICLE *AIRBAG_REFERENCE_GEOMETRY_BIRTH *AIRBAG_REFERENCE_GEOMETRY_BIRTH_RDT *AIRBAG_REFERENCE_GEOMETRY_RDT *AIRBAG_SIMPLE_AIRBAG_MODEL_ID *AIRBAG_SIMPLE_PRESSURE_VOLUME_ID *AIRBAG_WANG_NEFSKE_ID *AIRBAG_WANG_NEFSKE_JETTING_ID *AIRBAG_WANG_NEFSKE_JETTING_CM *AIRBAG_WANG_NEFSKE_JETTING_POP_ID *AIRBAG_WANG_NEFSKE_JETTING_POP_CM *AIRBAG_WANG_NEFSKE_MULTIPLE_JETTING_CM_ID
Altair Engineering

*AIRBAG_WANG_NEFSKE_MULTIPLE_JETTING_ID *AIRBAG_WANG_NEFSKE_MULTIPLE_JETTING_POP_CM *AIRBAG_WANG_NEFSKE_MULTIPLE_JETTING_POP_ID *AIRBAG_WANG_NEFSKE_POP_ID *ALE_MULTI_MATERIAL_GROUP *ALE_REFERENCE_SYSTEM_CURVE *ALE_REFERENCE_SYSTEM_GROUP *ALE_REFERENCE_SYSTEM_NODE *ALE_REFERENCE_SYSTEM_SWITCH *ALE_SMOOTHING *ALE_TANK_TEST *BOUNDARY_AMBIENT_EOS *BOUNDARY_CONVECTION_SET *BOUNDARY_FLUX_SET *BOUNDARY_NON_REFLECTING *BOUNDARY_NON_REFLECTING_2D *BOUNDARY_PRESCRIBED_MOTION_NODE *BOUNDARY_PRESCRIBED_MOTION_NODE_(ID) *BOUNDARY_PRESCRIBED_MOTION_RIGID *BOUNDARY_PRESCRIBED_MOTION_RIGID_(ID) *BOUNDARY_PRESCRIBED_MOTION__RIGID_LOCAL_(ID) *BOUNDARY_PRESCRIBED_MOTION_SET_(ID) *BOUNDARY_RADIATION_SET *BOUNDARY_SPC_NODE_(ID) *BOUNDARY_SPC_SET *BOUNDARY_SPC_SET_(ID) *BOUNDARY_SPH_FLOW *BOUNDARY_TEMPERATURE_NODE *BOUNDARY_TEMPERATURE_SET *CONSTRAINED_EXTRA_NODES_NODE *CONSTRAINED_EXTRA_NODES_SET *CONSTRAINED_GENERALIZED_WELD_BUTT_(ID) *CONSTRAINED_GENERALIZED_WELD_FILLET_(ID) *CONSTRAINED_GENERALIZED_WELD_SPOT_(ID) *CONSTRAINED_GLOBAL *CONSTRAINED_INTERPOLATION *CONSTRAINED_JOINT_CYLINDRICAL

Altair Engineering
*CONSTRAINED_JOINT_CYLINDRICAL_FAILURE(ID) *CONSTRAINED_JOINT_CYLINDRICAL_LOCAL(ID) *CONSTRAINED_JOINT_CYLINDRICAL_LOCAL_FAILURE(ID) *CONSTRAINED_JOINT_LOCKING(ID) *CONSTRAINED_JOINT_LOCKING_FAILURE(ID) *CONSTRAINED_JOINT_LOCKING_LOCAL(ID) *CONSTRAINED_JOINT_LOCKING_LOCAL_FAILURE(ID) *CONSTRAINED_JOINT_PLANAR(ID) *CONSTRAINED_JOINT_PLANAR_FAILURE(ID) *CONSTRAINED_JOINT_PLANAR_LOCAL_FAILURE_(ID) *CONSTRAINED_JOINT_PLANAR_LOCAL(ID) *CONSTRAINED_JOINT_REVOLUTE *CONSTRAINED_JOINT_REVOLUTE_FAILURE(ID) *CONSTRAINED_JOINT_REVOLUTE_LOCAL(ID) *CONSTRAINED_JOINT_REVOLUTE_LOCAL_FAILURE(ID) *CONSTRAINED_JOINT_SPHERICAL(ID) *CONSTRAINED_JOINT_SPHERICAL_LOCAL(ID) *CONSTRAINED_JOINT_SPHERICAL_FAILURE(ID) *CONSTRAINED_JOINT_SPHERICAL_LOCAL_FAILURE(ID) *CONSTRAINED_JOINT_STIFFNESS_FLEXION-TORSION *CONSTRAINED_JOINT_STIFFNESS_GENERALIZED *CONSTRAINED_JOINT_STIFFNESS_TRANSLATION *CONSTRAINED_JOINT_TRANSLATIONAL(ID) *CONSTRAINED_JOINT_TRANSLATIONAL_FAILURE(ID) *CONSTRAINED_JOINT_TRANSLATIONAL_LOCAL(ID) *CONSTRAINED_JOINT_TRANSLATIONAL_LOCAL_FAILURE(ID) *CONSTRAINED_JOINT_UNIVERSAL(ID) *CONSTRAINED_JOINT_UNIVERSAL_FAILURE(ID) *CONSTRAINED_JOINT_UNIVERSAL_LOCAL(ID) *CONSTRAINED_JOINT_UNIVERSAL_LOCAL_FAILURE(ID) *CONSTRAINED_LAGRANGE_IN_SOLID *CONSTRAINED_LINEAR *CONSTRAINED_LINEAR_GLOBAL *CONSTRAINED_NODAL_RIGID_BODY *CONSTRAINED_NODAL_RIGID_BODY (2-Noded) *CONSTRAINED_NODAL_RIGID_BODY_INERTIA *CONSTRAINED_NODAL_RIGID_BODY_INERTIA (2-Noded)
Altair Engineering

*CONSTRAINED_NODAL_RIGID_BODY_INERTIA _SPC *CONSTRAINED_NODAL_RIGID_BODY_INERTIA _SPC (2-Noded) *CONSTRAINED_NODAL_RIGID_BODY_SPC *CONSTRAINED_NODAL_RIGID_BODY_SPC (2-Noded) *CONSTRAINED_NODE_SET *CONSTRAINED_NODE_SET (2-Noded) *CONSTRAINED_NODE_SET_ID *CONSTRAINED_RIGID_BODIES *CONSTRAINED_RIGID_BODY_STOPPERS *CONSTRAINED_RIVET *CONSTRAINED_SHELL_TO_SOLID *CONSTRAINED_SPOTWELD_FILTERED_FORCE_ID *CONSTRAINED_SPOTWELD_ID *CONSTRAINED_TIE_BREAK *CONSTRAINED_TIED_NODES_FAILURE *CONTACT_AIRBAG_SINGLE_SURFACE(ID) *CONTACT_AIRBAG_SINGLE_SURFACE_MPP(ID) *CONTACT_AUTO_MOVE *CONTACT_AUTOMATIC_GENERAL(ID) *CONTACT_AUTOMATIC_GENERAL_INTERIOR(ID) *CONTACT_AUTOMATIC_GENERAL_INTERIOR_MPP(ID) *CONTACT_AUTOMATIC_GENERAL_MPP(ID) *CONTACT_AUTOMATIC_NODES_TO_SURFACE(ID) *CONTACT_AUTOMATIC_NODES_TO_SURFACE_MPP(ID) *CONTACT_AUTOMATIC_NODES_TO_SURFACE_SMOOTH(ID) *CONTACT_AUTOMATIC_NODES_TO_SURFACE_SMOOTH_MPP(ID) *CONTACT_AUTOMATIC_ONE_WAY_SURFACE_TO_SURFACE(ID) *CONTACT_AUTOMATIC_ONE_WAY_SURFACE_TO_SURFACE_SMOOTH(ID) *CONTACT_AUTOMATIC_ONE_WAY_SURFACE_TO_SURFACE_TIEBREAK(ID) *CONTACT_AUTOMATIC_SINGLE_SURFACE(ID) *CONTACT_AUTOMATIC_SINGLE_SURFACE_MPP(ID) *CONTACT_AUTOMATIC_SINGLE_SURFACE_SMOOTH(ID) *CONTACT_AUTOMATIC_SINGLE_SURFACE_SMOOTH_MPP(ID) *CONTACT_AUTOMATIC_SURFACE_TO_SURFACE(ID) *CONTACT_AUTOMATIC_SURFACE_TO_SURFACE_MPP(ID) *CONTACT_AUTOMATIC_SURFACE_TO_SURFACE_SMOOTH(ID) *CONTACT_AUTOMATIC_SURFACE_TO_SURFACE_SMOOTH_MPP(ID)

Altair Engineering
*CONTACT_AUTOMATIC_SURFACE_TO_SURFACE_TIEBREAK(ID) *CONTACT_AUTOMATIC_SURFACE_TO_SURFACE_TIEBREAK_MPP(ID) *CONTACT_CONSTRAINT_NODES_TO_SURFACES(ID) *CONTACT_CONSTRAINT_NODES_TO_SURFACE_MPP(ID) *CONTACT_CONSTRAINT_SURFACE_TO_SURFACE(ID) *CONTACT_CONSTRAINT_SURFACE_TO_SURFACE_MPP(ID) *CONTACT_DRAWBEAD(ID) *CONTACT_DRAWBEAD_MPP(ID) *CONTACT_ENTITY(ID) *CONTACT_ENTITY_MPP(ID) *CONTACT_ERODING_NODES_TO_SURFACE(ID) *CONTACT_ERODING_NODES_TO_SURFACE_MPP(ID) *CONTACT_ERODING_SINGLE_SURFACE(ID) *CONTACT_ERODING_SINGLE_SURFACE_MPP(ID) *CONTACT_ERODING_SURFACE_TO_SURFACE(ID) *CONTACT_ERODING_SURFACE_TO_SURFACE_MPP(ID) *CONTACT_FORCE_TRANSDUCER_CONSTRAINT(ID) *CONTACT_FORCE_TRANSDUCER_CONSTRAINT_MPP(ID) *CONTACT_FORCE_TRANSDUCER_PENALTY(ID) *CONTACT_FORCE_TRANSDUCER_PENALTY_MPP(ID) *CONTACT_FORMING_NODES_TO_SURFACE(ID) *CONTACT_FORMING_NODES_TO_SURFACE_MPP(ID) *CONTACT_FORMING_NODES_TO_SURFACE_SMOOTH(ID) *CONTACT_FORMING_NODES_TO_SURFACE_SMOOTH_MPP(ID) *CONTACT_FORMING_ONEWAY_SURFACE_TO_SURFACE(ID) *CONTACT_FORMING_ONEWAY_SURFACE_TO_SURFACE_CONSTRAINED_OFFSET(ID) *CONTACT_FORMING_ONEWAY_SURFACE_TO_SURFACE_CONSTRAINED_OFFSET_MPP(ID) *CONTACT_FORMING_ONEWAY_SURFACE_TO_SURFACE_CONSTRAINED_OFFSET_SMOOTH(ID) *CONTACT_FORMING_ONEWAY_SURFACE_TO_SURFACE_CONSTRAINED_OFFSET_SMOOTH_MP P(ID) *CONTACT_FORMING_ONEWAY_SURFACE_TO_SURFACE_MPP(ID) *CONTACT_FORMING_ONEWAY_SURFACE_TO_SURFACE_SMOOTH(ID) *CONTACT_FORMING_ONEWAY_SURFACE_TO_SURFACE_SMOOTH_MPP(ID) *CONTACT_FORMING_SURFACE_TO_SURFACE(ID) *CONTACT_FORMING_SURFACE_TO_SURFACE_CONSTRAINED_OFFSET(ID) *CONTACT_FORMING_SURFACE_TO_SURFACE_CONSTRAINED_OFFSET_SMOOTH(ID) *CONTACT_FORMING_SURFACE_TO_SURFACE_MPP(ID)
Altair Engineering

*CONTACT_FORMING_SURFACE_TO_SURFACE_SMOOTH(ID) *CONTACT_INTERIOR(ID) *CONTACT_INTERIOR_MPP(ID) *CONTACT_NODES_TO_SURFACE(ID) *CONTACT_NODES_TO_SURFACE_INTERFERENCE(ID) *CONTACT_NODES_TO_SURFACE_INTERFERENCE_MPP(ID) *CONTACT_NODES_TO_SURFACE_MPP(ID) *CONTACT_NODES_TO_SURFACE_SMOOTH *CONTACT_NODES_TO_SURFACE_SMOOTH_MPP(ID) *CONTACT_ONE_WAY_SURFACE_TO_SURFACE(ID) *CONTACT_ONE_WAY_SURFACE_TO_SURFACE_INTERFERENCE(ID) *CONTACT_ONE_WAY_SURFACE_TO_SURFACE_INTERFERENCE_MPP(ID) *CONTACT_ONE_WAY_SURFACE_TO_SURFACE_INTERFERENCE_CONSTRAINED_OFFSET(ID) *CONTACT_ONE_WAY_SURFACE_TO_SURFACE_INTERFERENCE_CONSTRAINED_OFFSET_MPP (ID) *CONTACT_ONE_WAY_SURFACE_TO_SURFACE_MPP(ID) *CONTACT_ONE_WAY_SURFACE_TO_SURFACE_SMOOTH(ID) *CONTACT_ONE_WAY_SURFACE_TO_SURFACE_SMOOTH_MPP(ID) *CONTACT_RIGID_BODY_ONE_WAY_TO_RIGID_BODY(ID) *CONTACT_RIGID_BODY_ONE_WAY_TO_RIGID_BODY_MPP(ID) *CONTACT_RIGID_BODY_TWO_WAY_TO_RIGID_BODY(ID) *CONTACT_RIGID_BODY_TWO_WAY_TO_RIGID_BODY_MPP(ID) *CONTACT_RIGID_NODES_TO_RIGID_BODY(ID) *CONTACT_RIGID_NODES_TO_RIGID_BODY_MPP(ID) *CONTACT_RIGID_SURFACE(ID) *CONTACT_RIGID_SURFACE_MPP(ID) *CONTACT_SINGLE_EDGE(ID) *CONTACT_SINGLE_EDGE_MPP(ID) *CONTACT_SINGLE_SURFACE(ID) *CONTACT_SINGLE_SURFACE_MPP(ID) *CONTACT_SLIDING_ONLY(ID) *CONTACT_SLIDING_ONLY_MPP(ID) *CONTACT_SLIDING_ONLY_PENALTY(ID) *CONTACT_SLIDING_ONLY_PENALTY_MPP(ID) *CONTACT_SPOTWELD(ID) *CONTACT_SPOTWELD_MPP(ID) *CONTACT_SPOTWELD_WITH_TORSION(ID)

Altair Engineering
*CONTACT_SPOTWELD_WITH_TORSION_MPP(ID) *CONTACT_SURFACE_TO_SURFACE(ID) *CONTACT_SURFACE_TO_SURFACE_CONSTRAINED_OFFSET *CONTACT_SURFACE_TO_SURFACE_CONSTRAINED_OFFSET_MPP *CONTACT_SURFACE_TO_SURFACE_CONSTRAINED_OFFSET_SMOOTH *CONTACT_SURFACE_TO_SURFACE_CONSTRAINED_OFFSET_SMOOTH_MPP *CONTACT_SURFACE_TO_SURFACE_MPP(ID) *CONTACT_SURFACE_TO_SURFACE_INTERFERENCE(ID) *CONTACT_SURFACE_TO_SURFACE_INTERFERENCE_MPP(ID) *CONTACT_SURFACE_TO_SURFACE_INTERFERENCE_CONSTRAINED_OFFSET *CONTACT_SURFACE_TO_SURFACE_INTERFERENCE_CONSTRAINED_OFFSET_MPP *CONTACT_SURFACE_TO_SURFACE_SMOOTH(ID) *CONTACT_SURFACE_TO_SURFACE_THERMAL(ID) *CONTACT_SURFACE_TO_SURFACE_THERMAL_MPP(ID) *CONTACT_TIEBREAK_NODES_TO_SURFACE(ID) *CONTACT_TIEBREAK_NODES_TO_SURFACE_MPP(ID) *CONTACT_TIEBREAK_SURFACE_TO_SURFACE(ID) *CONTACT_TIEBREAK_SURFACE_TO_SURFACE_MPP(ID) *CONTACT_TIED_NODE_TO_SURFACE(ID) *CONTACT_TIED_NODE_TO_SURFACE_MPP(ID) *CONTACT_TIED_NODE_TO_SURFACE_CONSTRAINED_OFFSET(ID) *CONTACT_TIED_NODE_TO_SURFACE_CONSTRAINED_OFFSET_MPP(ID) *CONTACT_TIED_NODE_TO_SURFACE_OFFSET(ID) *CONTACT_TIED_NODE_TO_SURFACE_OFFSET_MPP(ID) *CONTACT_TIED_SHELL_EDGE_TO_SURFACE(ID) *CONTACT_TIED_SHELL_EDGE_TO_SURFACE_BEAM_OFFSET(ID) *CONTACT_TIED_SHELL_EDGE_TO_SURFACE_BEAM_OFFSET_MPP(ID) *CONTACT_TIED_SHELL_EDGE_TO_SURFACE_CONSTRAINED_OFFSET(ID) *CONTACT_TIED_SHELL_EDGE_TO_SURFACE_CONSTRAINED_OFFSET_MPP(ID) *CONTACT_TIED_SHELL_EDGE_TO_SURFACE_MPP(ID) *CONTACT_TIED_SHELL_EDGE_TO_SURFACE_OFFSET(ID) *CONTACT_TIED_SHELL_EDGE_TO_SURFACE_OFFSET_MPP(ID) *CONTACT_TIED_SURFACE_TO_SURFACE(ID) *CONTACT_TIED_SURFACE_TO_SURFACE_CONSTRAINED_OFFSET(ID) *CONTACT_TIED_SURFACE_TO_SURFACE_CONSTRAINED_OFFSET_MPP(ID) *CONTACT_TIED_SURFACE_TO_SURFACE_MPP(ID) *CONTACT_TIED_SURFACE_TO_SURFACE_OFFSET(ID)
Altair Engineering

*CONTACT_TIED_SURFACE_TO_SURFACE_OFFSET_MPP(ID) *CONTACT_2D_AUTOMATIC_SURFACE_TO_SURFACE(ID) *CONTACT_2D_AUTOMATIC_SURFACE_TO_SURFACE_THERMAL_TITLE(ID) *CONTACT_2D_AUTOMATIC_SURFACE_TO_SURFACE_THERMAL_TITLE_MPP(ID) *CONTACT_2D_AUTOMATIC_SURFACE_TO_SURFACE_TITLE(ID) *CONTACT_2D_AUTOMATIC_SURFACE_TO_SURFACE_TITLE_MPP(ID) *CONTROL_ACCURACY *CONTROL_ADAPSTEP *CONTROL_ADAPTIVE *CONTROL_ADAPTIVE_CURVE *CONTROL_ALE *CONTROL_BULK_VISCOSITY *CONTROL_CHECK *CONTROL_COARSEN *CONTROL_CONTACT *CONTROL_COUPLING *CONTROL_CPU *CONTROL_DYNAMIC_RELAXATION *CONTROL_EFG *CONTROL_ENERGY *CONTROL_EXPLOSIVE_SHADOW *CONTROL_HOURGLASS *CONTROL_IMPLICIT_AUTO *CONTROL_IMPLICIT_BUCKLE *CONTROL_IMPLICIT_DYNAMICS *CONTROL_IMPLICIT_EIGENVALUE *CONTROL_IMPLICIT_GENERAL *CONTROL_IMPLICIT_INERTIA_RELIEF *CONTROL_IMPLICIT_LINEAR *CONTROL_IMPLICIT_MODES *CONTROL_IMPLICIT_NONLINEAR *CONTROL_IMPLICIT_SOLUTION *CONTROL_IMPLICIT_SOLVER *CONTROL_IMPLICIT_STABILIZATION *CONTROL_IMPLICIT_TERMINATION *CONTROL_MPP_DECOMPOSITION_AUTOMATIC *CONTROL_MPP_DECOMPOSITION_CHECK_SPEED

Altair Engineering
*CONTROL_MPP_DECOMPOSITION_CONTACT_DISTRIBUTE *CONTROL_MPP_DECOMPOSITION_CONTACT_ISOLATION *CONTROL_MPP_DECOMPOSITION_FILE *CONTROL_MPP_DECOMPOSITION_METHOD *CONTROL_MPP_DECOMPOSITION_NUMPROC *CONTROL_MPP_DECOMPOSITION_SHOW *CONTROL_MPP_DECOMPOSITION_TRANSFORMATION *CONTROL_MPP_IO_NOD3DUMP *CONTROL_MPP_IO_NODUMP *CONTROL_MPP_IO_NOFULL *CONTROL_MPP_IO_SWAPBYTES *CONTROL_OUTPUT *CONTROL_PARALLEL *CONTROL_REMESHING *CONTROL_RIGID *CONTROL_SHELL *CONTROL_SOLID *CONTROL_SOLUTION *CONTROL_SPH *CONTROL_SPOTWELD_BEAM *CONTROL_STRUCTURED *CONTROL_STRUCTURED_TERM *CONTROL_SUBCYCLE *CONTROL_TERMINATION *CONTROL_THERMAL_NONLINEAR *CONTROL_THERMAL_SOLVER *CONTROL_THERMAL_TIMESTEP *CONTROL_TIMESTEP *DAMPING_FREQUENCY_RANGE *DAMPING_GLOBAL *DAMPING_PART_MASS *DAMPING_PART_STIFFNESS *DAMPING_RELATIVE *DATABASE_ABSTAT *DATABASE_ABSTAT_CPM *DATABASE_AVSFLT *DATABASE_BINARY_D3PLOT
Altair Engineering

*DATABASE_BINARY_D3DRLF *DATABASE_BINARY_D3THDT *DATABASE_BINARY_D3DUMP *DATABASE_BINARY_FSIFOR *DATABASE_BINARY_INTFOR *DATABASE_BINARY_RUNRSF *DATABASE_BINARY_XTFILE *DATABASE_BNDOUT *DATABASE_CROSS_SECTION_PLANE(ID) *DATABASE_CROSS_SECTION_SET(ID) *DATABASE_DCFAIL *DATABASE_DEFGEO *DATABASE_DEFORC *DATABASE_ELOUT *DATABASE_EXTENT_AVS *DATABASE_EXTENT_BINARY *DATABASE_EXTENT_MOVIE *DATABASE_EXTENT_MPGS *DATABASE_EXTENT_SSSTAT *DATABASE_FORMAT *DATABASE_FSI *DATABASE_GCEOUT *DATABASE_GLSTAT *DATABASE_HISTORY_BEAM(ID) *DATABASE_HISTORY_BEAM_SET *DATABASE_DISCRETE *DATABASE_DISCRETE_SET *DATABASE_HISTORY_NODE(ID) *DATABASE_HISTORY_NODE_LOCAL(ID) *DATABASE_HISTORY_NODE_SET *DATABASE_HISTORY_NODE_SET_LOCAL *DATABASE_HISTORY_NODE_SET_LOCAL(ID) *DATABASE_HISTORY_SEATBELT *DATABASE_HISTORY_SHELL *DATABASE_HISTORY_SHELL(ID) *DATABASE_HISTORY_SHELL_SET *DATABASE_HISTORY_SOLID

Altair Engineering
*DATABASE_HISTORY_SOLID(ID) *DATABASE_HISTORY_SOLID_SET *DATABASE_HISTORY_SPH *DATABASE_HISTORY_TSHELL *DATABASE_HISTORY_TSHELL(ID) *DATABASE_HISTORY_TSHELL_SET *DATABASE_JNTFORC *DATABASE_MATSUM *DATABASE_MOVIE *DATABASE_MPGS *DATABASE_NCFORC *DATABASE_NODAL_FORCE_GROUP *DATABASE_NODFOR *DATABASE_NODOUT *DATABASE_OPTION *DATABASE_RBDOUT *DATABASE_RCFORC *DATABASE_RWFORC *DATABASE_SBTOUT *DATABASE_SECFORC *DATABASE_SLEOUT *DATABASE_SPCFORC *DATABASE_SPHOUT *DATABASE_SPRING_FORWARD *DATABASE_SSSTAT *DATABASE_SUPERELASTIC_FORMING *DATABASE_SWFORC *DATABASE_TPRINT *DATABASE_TRACER *DATABASE_TRHIST *DEFINE_ALEBAG_BAG *DEFINE_ALEBAG_HOLE *DEFINE_ALEBAG_INFLATOR *DEFINE_BOX *DEFINE_BOX_ADAPTIVE *DEFINE_BOX_COARSEN *DEFINE_BOX_DRAWBEAD
Altair Engineering

*DEFINE_BOX_SPH *DEFINE_CONNECTION_PROPERTIES *DEFINE_COORDINATE_NODES *DEFINE_COORDINATE_SYSTEM *DEFINE_COORDINATE_VECTOR *DEFINE_CURVE *DEFINE_CURVE_FEEDBACK *DEFINE_CURVE_SMOOTH *DEFINE_CURVE_TRIM *DEFINE_CURVE_TRIM_3D *DEFINE_HEX_SPOTWELD_ASSEMBLY *DEFINE_HEX_SPOTWELD_ASSEMBLY_N *DEFINE_SD_ORIENTATION *DEFINE_TABLE *DEFINE_TRANSFORMATION *DEFINE_VECTOR *DEFORMABLE_TO_RIGID *DEFORMABLE_TO_RIGID_AUTOMATIC *DEFORMABLE_TO_RIGID_INERTIA *ELEMENT_BEAM *ELEMENT_BEAM_OFFSET *ELEMENT_BEAM_OFFSET_PID *ELEMENT_BEAM_OFFSET_THICKNESS *ELEMENT_BEAM_ORIENTATION *ELEMENT_BEAM_PID *ELEMENT_BEAM_SCALAR *ELEMENT_BEAM_THICKNESS *ELEMENT_DISCRETE *ELEMENT_INERTIA *ELEMENT_INERTIA_OFFSET *ELEMENT_MASS *ELEMENT_MASS_NODE_SET *ELEMENT_MASS_PART *ELEMENT_MASS_PART_SET *ELEMENT_PLOTEL *ELEMENT_SEATBELT *ELEMENT_SEATBELT_ACCELEROMETER

Altair Engineering
*ELEMENT_SEATBELT_PRETENSIONER *ELEMENT_SEATBELT_RETRACTOR *ELEMENT_SEATBELT_SENSOR *ELEMENT_SEATBELT_SLIPRING *ELEMENT_SHELL *ELEMENT_SHELL_BETA *ELEMENT_SHELL_BETA_OFFSET *ELEMENT_SHELL_DOF *ELEMENT_SHELL_MCID *ELEMENT_SHELL_MCID_OFFSET *ELEMENT_SHELL_OFFSET *ELEMENT_SHELL_THICKNESS *ELEMENT_SHELL_THICKNESS_BETA *ELEMENT_SHELL_THICKNESS_BETA_OFFSET *ELEMENT_SHELL_THICKNESS_MCID *ELEMENT_SHELL_THICKNESS_MCID_OFFSET *ELEMENT_SHELL_THICKNESS_OFFSET *ELEMENT_SOLID *ELEMENT_SOLID_ORTHO *ELEMENT_SOLID_TET4TOTET10 *ELEMENT_SPH *ELEMENT_TRIM *ELEMENT_TSHELL *END *EOS_GRUNEISEN (EOS 4) *EOS_IDEAL_GAS (EOS 12) *EOS_IGNITION_AND_GROWTH_OF_REACTION_IN_HE (EOS 7) *EOS_JWL (EOS 2) *EOS_LINEAR_POLYNOMIAL (EOS 1) *EOS_LINEAR_POLYNOMIAL_WITH_ENERGY_LEAK (EOS 6) *EOS_PROPELLANT_DEFLAGRATION (EOS 10) *EOS_RATIO_OF_POLYNOMIALS (EOS 5) *EOS_SACK_TUESDAY (EOS 3) *EOS_TABULATED (EOS 9) *EOS_TABULATED_COMPACTION (EOS 8) *EOS_TENSOR_PORE_COLLAPSE (EOS11) *HOURGLASS
Altair Engineering

*INCLUDE_COMPENSATION *INCLUDE_COMPENSATION_BLANK_AFTER_SPRINGBACK *INCLUDE_COMPENSATION_BLANK_BEFORE_SPRINGBACK *INCLUDE_COMPENSATION_COMPENSATED_SHAPE *INCLUDE_COMPENSATION_DESIRED_BLANK_SHAPE *INCLUDE_CURRENT_TOOLS *INCLUDE_STAMPED_PART *INCLUDE_TRANSFORM *INITIAL_AXIAL_FORCE_BEAM *INITIAL_DETONATION *INITIAL_FOAM_REFERENCE_GEOMETRY *INITIAL_GAS_MIXTURE *INITIAL_MOMENTUM *INITIAL_STRAIN_SHELL *INITIAL_STRAIN_SOLID *INITIAL_STRESS_BEAM *INITIAL_STRESS_SECTION *INITIAL_STRESS_SHELL *INITIAL_STRESS_SOLID *INITIAL_TEMPERATURE_NODE *INITIAL_TEMPERATURE_SET *INITIAL_VEHICLE_KINEMATICS *INITIAL_VELOCITY *INITIAL_VELOCITY_GENERATION *INITIAL_VELOCITY_NODE *INITIAL_VELOCITY_RIGID_BODY *INITIAL_VOID *INITIAL_VOLUME_FRACTION *INITIAL_VOLUME_FRACTION_GEOMETRY *INTEGRATION_BEAM *INTEGRATION_SHELL *INTERFACE_COMPENSATION_NEW *INTERFACE_COMPONENT_NODE *INTERFACE_COMPONENT_SEGMENT *INTERFACE_LINKING_DISCRETE_NODE_SET *INTERFACE_LINKING_EDGE *INTERFACE_LINKING_SEGMENT *INTERFACE_SPRINGBACK

Altair Engineering
*INTERFACE_SPRINGBACK_LSDYNA *INTERFACE_SPRINGBACK_LSDYNA_NOTHICKNESS *INTERFACE_SPRINGBACK_LSDYNA_THICKNESS *INTERFACE_SPRINGBACK_NASTRAN *INTERFACE_SPRINGBACK_NASTRAN_NOTHICKNESS *INTERFACE_SPRINGBACK_NASTRAN_THICKNESS *INTERFACE_SPRINGBACK_SEAMLESS *INTERFACE_SPRINGBACK_SEAMLESS_NOTHICKNESS *INTERFACE_SPRINGBACK_SEAMLESS_THICKNESS *LOAD_BEAM_ELEMENT *LOAD_BEAM_SET *LOAD_BLAST *LOAD_BODY_GENERALIZED *LOAD_BODY_PARTS *LOAD_BODY_RX *LOAD_B0DY_RY *LOAD_BODY_RZ *LOAD_BODY_X *LOAD_BODY_Y *LOAD_BODY_Z *LOAD_BRODE *LOAD_MASK *LOAD_NODE_POINT *LOAD_NODE_SET *LOAD_RIGID_BODY *LOAD_SEGMENT *LOAD_SEGMENT_ID *LOAD_SEGMENT_SET_ID *LOAD_SHELL_ELEMENT *LOAD_SHELL_ELEMENT_ID *LOAD_SHELL_PRESSURE *LOAD_SHELL_SET_ID *LOAD_SUPERELASTIC_FORMING *LOAD_THERMAL_CONSTANT *LOAD_THERMAL_CONSTANT_NODE *LOAD_THERMAL_LOAD_CURVE *LOAD_THERMAL_VARIABLE
Altair Engineering

*LOAD_THERMAL_VARIABLE_NODE *LOAD_THERMAL_VARIABLE_SHELL *LOAD_THERMAL_VARIABLE_SHELL_SET *MAT_ACOUSTIC *MAT_ADD_EROSION *MAT_ANISOTROPIC_ELASTIC *MAT_ANISOTROPIC_ELASTIC_PLASTIC *MAT_ANISOTROPIC_PLASTIC *MAT_ANISOTROPIC_VISCOPLASTIC *MAT_ARRUDA_BOYCE_RUBBER *MAT_ARUP_ADHESIVE *MAT_BAMMAN *MAT_BAMMAN_DAMAGE *MAT_BARLAT_ANISOTROPIC_PLASTICITY *MAT_BARLAT_YLD2000 *MAT_BARLAT_YLD96 *MAT_BILKHU/DUBOIS_FOAM *MAT_BLATZ-KO_FOAM *MAT_BLATZ-KO_RUBBER *MAT_BRITTLE_DAMAGE *MAT_CABLE_DISCRETE_BEAM *MAT_CELLULAR_RUBBER *MAT_COHESIVE_ELASTIC *MAT_CLOSED_CELL_FOAM *MAT_COMPOSITE_DAMAGE *MAT_COMPOSITE_FAILURE_MODEL *MAT_COMPOSITE_FAILURE_SHELL_MODEL *MAT_COMPOSITE_FAILURE_SOLID_MODEL *MAT_COMPOSITE_LAYUP *MAT_CONCRETE_DAMAGE *MAT_CORUS_VEGTER *MAT_CRUSHABLE_FOAM *MAT_CSCM *MAT_CSCM_CONCRETE *MAT_DAMPER_NONLINEAR_VISCUOUS *MAT_DAMPER_VISCOUS *MAT_DESHPANDE_FLECK_FOAM

Altair Engineering
*MAT_ELASTIC *MAT_ELASTIC_FLUID *MAT_ELASTIC_PLASTIC_HYDRO *MAT_ELASTIC_PLASTIC_THERMAL *MAT_ELASTIC_SPRING_DISCRETE_BEAM *MAT_ELASTIC_VISCOPLASTIC_THERMAL *MAT_ELASTIC_WITH_VISCOSITY *MAT_ELASTIC_6DOF_SPRING_DISCRETE_BEAM *MAT_ENHANCED_COMPOSITE_DAMAGE *MAT_FABRIC *MAT_FINITE_ELASTIC_STRAIN_PLASTICITY *MAT_FLD_TRANSVERSELY_ANISOTROPIC *MAT_FLD_3_PARAMETER_BARLAT *MAT_FORCE_LIMITED *MAT_FRAZER_NASH_RUBBER_MODEL *MAT_FU_CHANG_FOAM *MAT_GAS_MIXTURE *MAT_GENERAL_JOINT_DISCRETE_BEAM *MAT_GENERAL_NONLINEAR_1DOF_DISCRETE_BEAM *MAT_GENERAL_NONLINEAR_6DOF_DISCRETE_BEAM *MAT_GENERAL_SPRING_DISCRETE_BEAM *MAT_GENERAL_VISCOELASTIC *MAT_GEOLOGIC_CAP_MODEL *MAT_GEPLASTIC_SRATE_2000a *MAT_GURSON *MAT_GURSON_JC *MAT_HIGH_EXPLOSIVE_BURN *MAT_HILL_FOAM *MAT_HILL_3R *MAT_HONEYCOMB *MAT_HYDRAULIC_GAS_DAMPER_DISCRETE_BEAM *MAT_HYPERELASTIC_RUBBER *MAT_INELASTIC_SPRING_DISCRETE_BEAM *MAT_INELASTIC_6DOF_SPRING_DISCRETE_BEAM *MAT_ISOTROPIC_ELASTIC_FAILURE *MAT_ISOTROPIC_ELASTIC_PLASTIC *MAT_JOHNSON_COOK
Altair Engineering

*MAT_JOHNSON_HOLMQUIST_CERAMICS *MAT_KELVIN-MAXWELL_VISCOELASTIC *MAT_KINEMATIC_HARDENING_TRANSVERSELY_ANISOTROPIC *MAT_LAMINATED_COMPOSITE_FABRIC *MAT_LAMINATED_GLASS *MAT_LAYERED_LINEAR_PLASTICITY *MAT_LINEAR_ELASTIC_DISCRETE_BEAM *MAT_LOW_DENSITY_FOAM *MAT_LOW_DENSITY_SYNTHETIC_FOAM *MAT_LOW_DENSITY_SYNTHETIC_FOAM_ORTHO *MAT_LOW_DENSITY_SYNETHIC_FOAM_ORTHO_WITH_FAILURE *MAT_LOW_DENSITY_SYNTHETIC_FOAM_WITH_FAILURE *MAT_LOW_DENSITY_VISCOUS_FOAM *MAT_MODIFIED_CRUSHABLE_FOAM *MAT_MODIFIED_HONEYCOMB *MAT_MODIFIED_PIECEWISE_LINEAR_PLASTICITY *MAT_MODIFIED_PIECEWISE_LINEAR_PLASTICITY_RATE *MAT_MODIFIED_ZERILLI_ARMSTRONG *MAT_MOONEY_RIVLIN_RUBBER *MAT_MTS *MAT_NONLINEAR_ELASTIC_DISCRETE_BEAM *MAT_NONLINEAR_ORTHOTROPIC *MAT_NONLINEAR_PLASTIC_DISCRETE_BEAM *MAT_NULL *MAT_OGDEN_RUBBER *MAT_ORIENTED_CRACK *MAT_ORTHOTROPIC_ELASTIC *MAT_ORTHOTROPIC_THERMAL *MAT_ORTHOTROPIC_VISCOELASTIC *MAT_PIECEWISE_LINEAR_PLASTICITY *MAT_PLASTICITY_COMPRESSION_TENSION *MAT_PLASTICITY_COMPRESSION_TENSION_E0S *MAT_PLASTIC_KINEMATIC *MAT_PLASTICITY_POLYMER *MAT_PLASTICITY_WITH_DAMAGE *MAT_PLASTICITY_WITH_DAMAGE_ORTHO *MAT_PLASTICITY_WITH_DAMAGE_RCDC

Altair Engineering
*MAT_POWER_LAW_PLASTICITY *MAT_PSEUDO_TENSOR *MAT_RATE_SENSITIVE_POWERLAW_PLASTICITY *MAT_RESULTANT_ANISOTROPIC *MAT_RESULTANT_PLASTICITY *MAT_RIGID *MAT_SAMP-1 *MAT_SCHWER_MURRARY_CAP_MODEL *MAT_SEATBELT *MAT_SHAPE_MEMORY *MAT_SID_DAMPER_DISCRETE_BEAM *MAT_SIMPLIFIED_JOHNSON_COOK *MAT_SIMPLIFIED_JOHNSON_COOK_ORTHOTROPIC_DAMAGE *MAT_SIMPLIFIED_RUBBER *MAT_SIMPLIFIED_RUBBER_WITH_DAMAGE *MAT_SOIL_AND_FOAM *MAT_SOIL_AND_FOAM_FAILURE *MAT_SPOTWELD *MAT_SPOTWELD_DAIMLER_CHRYSLER *MAT_SPOTWELD_DAMAGE *MAT_SPRING_ELASTIC *MAT_SPRING_ELASTOPLASTIC *MAT_SPRING_GENERAL_NONLINEAR *MAT_SPRING_INELASTIC *MAT_SPRING_MAXWELL *MAT_SPRING_NONLINEAR_ELASTIC *MAT_STEINBERG *MAT_STEINBERG_LUND *MAT_STRAIN_RATE_DEPENDENT_PLASTICITY *MAT_TEMPERATURE_DEPENDENT_ORTHOTROPIC *MAT_THERMAL_ISOTROPIC *MAT_THERMAL_ISOTROPIC_TD_LC *MAT_THERMAL_ORTHOTROPIC *MAT_TRANSVERSELY_ANISOTROPIC_CRUSHABLE_FOAM *MAT_TRANSVERSELY_ANISOTROPIC_ELASTIC_PLASTIC *MAT_TRANSVERSELY_ANISOTROPIC_ELASTIC_PLASTIC_ECHANGE *MAT_TRIP
Altair Engineering

*MAT_UNSUPPORTED *MAT_USER_DEFINED_MATERIAL *MAT_VACUUM *MAT_VISCOELASTIC *MAT_VISCOELASTIC_HILL_FOAM *MAT_VISCOUS_FOAM *MAT_WINFRITH_CONCRETE *MAT_WOOD *MAT_WOOD_FIR *MAT_WOOD_OPTION *MAT_WOOD_PINE *MAT_1DOF_GENERALIZED_SPRING *MAT_3-PARAMETER_BARLAT *NODE *NODE_RIGID_SURFACE *NODE_TRANSFORM *PART *PART_COMPOSITE *PART_COMPOSITE_CONTACT *PART_CONTACT *PART_CONTACT_PRINT *PART_INERTIA *PART_INERTIA_CONTACT *PART_INERTIA_CONTACT_PRINT *PART_INERTIA_PRINT *PART_MOVE *PART_PRINT *PART_REPOSITION *PART_REPOSITION_CONTACT *PART_REPOSITION_CONTACT_PRINT *PART_REPOSITION_PRINT *PART_SENSOR *RIGIDWALL_GEOMETRIC_CYLINDER(ID) *RIGIDWALL_GEOMETRIC_CYLINDER_MOTION(ID) *RIGIDWALL_GEOMETRIC_FLAT(ID) *RIGIDWALL_GEOMETRIC_FLAT_MOTION(ID) *RIGIDWALL_GEOMETRIC_PRISM(ID)

Altair Engineering
*RIGIDWALL_GEOMETRIC_PRISM_MOTION(ID) *RIGIDWALL_GEOMETRIC_SPHERE(ID) *RIGIDWALL_GEOMETRIC_SPHERE_MOTION(ID) *RIGIDWALL_PLANAR(ID) *RIGIDWALL_PLANAR_FINITE(ID) *RIGIDWALL_PLANAR_FINITE_FORCES_MOVING(ID) *RIGIDWALL_PLANAR_FINITE_MOVING(ID) *RIGIDWALL_PLANAR_FORCE(ID) *RIGIDWALL_PLANAR_FORCE_FINITE(ID) *RIGIDWALL_PLANAR_FORCES_MOVING(ID) *RIGIDWALL_PLANAR_MOVING(ID) *RIGIDWALL_PLANAR_ORTHO(ID) *RIGIDWALL_PLANAR_ORTHO_FINITE_FORCES(ID) *RIGIDWALL_PLANAR_ORTHO_FORCES(ID) *SECTION_BEAM(TITLE) *SECTION_DISCRETE(TITLE) *SECTION_POINT_SOURCE(TITLE) *SECTION_POINT_SOURCE_MIXTURE(TITLE) *SECTION_SEATBELT(TITLE) *SECTION_SHELL(TITLE) *SECTION_SHELL_ALE(TITLE) *SECTION_SHELL_EFG(TITLE) *SECTION_SOLID(TITLE) *SECTION_SOLID_ALE(TITLE) *SECTION_SOLID_EFG(TITLE) *SECTION_SPH *SECTION_TSHELL(TITLE) *SENSOR_CONTROL *SENSOR_DEFINE_CALC_MATH *SENSOR_DEFINE_ELEMENT *SENSOR_DEFINE_FORCE *SENSOR_DEFINE_NODE *SENSOR_SWITCH *SENSOR_SWITCH_CALC_LOGIC *SET_BEAM(TITLE) *SET_BEAM_ADD *SET_BEAM_GENERATE(TITLE)
Altair Engineering

*SET_DISCRETE(TITLE) *SET_DISCRETE_ADD *SET_DISCRETE_GENERAL *SET_DISCRETE_GENERATE(TITLE) *SET_MULTI_MATERIAL_GROUP_LIST(TITLE) *SET_NODE_ADD *SET_NODE_ADD_ADVANCED *SET_NODE_COLUMN *SET_NODE_LIST(TITLE) *SET_NODE_LIST_GENERATE(TITLE) *SET_PART_ADD *SET_PART_COLUMN(TITLE) *SET_PART_LIST_GENERATE(TITLE) *SET_SEGMENT *SET_SEGMENT(TITLE) *SET_SEGMENT_GENERAL *SET_SEGMENT_GENERATE(TITLE) *SET_SHELL_ADD *SET_SHELL_COLUMN *SET_SHELL_LIST(TITLE) *SET_SHELL_LIST_GENERATE(TITLE) *SET_SOLID(TITLE) *SET_SOLID_ADD *SET_SOLID_ADD(TITLE) *SET_SOLID_GENERAL *SET_SOLID_GENERAL(TITLE) *SET_SOLID_GENERATE(TITLE) *SET_TSHELL(TITLE) *SET_TSHELL_GENERAL *SET_TSHELL_GENERAL(TITLE) *SET_TSHELL_GENERATE(TITLE) *SPRINGBACK MADYMO
The following cards are supported in MADYMO:

Altair Engineering
ACTUATOR AIRBAG_CHAMBER AMPLIFICATION.ABS_POLY AMPLIFICATION.EXP AMPLIFICATION.LOG AMPLIFICATION.POLY ANIMATION BELT BELT_FUSE BELT_RETRACTOR BELT_SEGMENT BELT_TYING BODY.DEFORMABLE BODY.FLEXIBLE_BEAM BODY.RIGID CHAR_MOD CHARACTERISTIC.CONTACT CHARACTERISTIC.LOAD CHARACTERISTIC.MATERIAL COMP_SIX_DOF COMPONENT CONNECT_N2 CONNECT_N3 CONSTRAINT.LINEAR CONSTRAINT.RIGID_FE CONSTRAINT.SIMPLE CONTACT_EVALUATE CONTACT.FE_FE CONTACT_FORCE CONTACT.MB_FE CONTACT.MB_MB CONTROL_AIRBAG CONTROL_ALLOCATION CONTROL_ANALYSIS CONTROL_FE_MODEL CONTROL_FE_TIME_STEP CONTROL_IMM
Altair Engineering

CONTROL_OUTPUT CONTROL_SYSTEM CONTROLLER COORDINATE.CARTESIAN COORDINATE_REF.CARTESIAN COUPLING_BODY COUPLING_SURFACE DAMAGE ELEMENT.MASS1 EQUATION.MASTER EQUATION.SLAVE FE_CRDSYS FE_MODEL FUNC_MOD FUNCTION.XY GAS GAS_FLOW_GRID GAS_MIXTURE GAS_MIXTURE_VARIABLE GROUP_FE GROUP_MB HOLE HOLE_AREA HOLE_SUBSEGMENT INFLATOR INFLATOR.CHAR INFLATOR.DEF INFLATOR.REF INJURY JET JOINT LAYER LOAD MADYMO MATERIAL.ANISO MATERIAL.FABRIC MATERIAL.FOAM

Altair Engineering
MATERIAL.HOLE MATERIAL.HONEYCOMB MATERIAL.HONEYCOMB_PLASTIC MATERIAL.HYSISO MATERIAL.INTERFACE MATERIAL.ISOLIN MATERIAL ISOLIN MATERIAL ISOPLA MATERIAL.KELVIN1D MATERIAL.KELVIN1D_NL MATERIAL.KELVIN3D MATERIAL KELVIN3D_NL MATERIAL LINVIS MATERIAL MOONRIV MATERIAL NULL MATERIAL ORTHOLIN MATERIAL ORTHOLIN_LAYERED MATERIAL ORTHOPLA MATERIAL RIGID MATERIAL SANDWICH MATERIAL STRAP MATERIAL TONER MATERIAL USER MATERIAL.VISCO_NL MODE MODE_SHAPE MOTION.NODE MOTION_STRUCT_FE OPERATOR ORIENTATION.MATRIX ORIENTATION.SCREW_AXIS ORIENTATION.SUCCESSIVE_ROT ORIENTATION.VECTOR OUTPUT_AIRBAG_CHAMBER OUTPUT_ANIMATION OUTPUT_BELT OUTPUT_BODY
Altair Engineering

OUTPUT_BODY_REL OUTPUT_CONTACT OUTPUT_CONTROL_SYSTEM OUTPUT_CROSS_SECTION OUTPUT_ELEMENT OUTPUT_ELEMENT_INITIAL OUTPUT_ENERGY_FE_MODEL OUTPUT_JET OUTPUT_JOINT_CONSTRAINT OUTPUT_JOINT_DOF OUTPUT_MARKER OUTPUT_MOTION_STRUCT OUTPUT_NODE OUTPUT_NODE_INITIAL OUTPUT_RESTRAINT OUTPUT_SENSOR OUTPUT_SYSTEM_COG PART PERMEABILITY POINT_OBJECT POINT_OBJECT_1_MB POINT_OBJECT_2_MB POINT_OBJECT_FE POINT_OBJECT_1_FE POINT_OBJECT_2_FE PORT PRINT_MARKER PRINT_OUTPUT_FE PROPERTY.BEAM2_BOX PROPERTY.BEAM2_CIRCULAR PROPERTY.BEAM2_DISCRETE PROPERTY.BEAM2_GENERAL PROPERTY2.BEAM2_PIPE PROPERTY.BEAM2_RECTANGULAR PROPERTY.BEAM2_USER PROPERTY.FACET6 PROPERTY.INTERFACE4

Altair Engineering
PROPERTY.MEM3 PROPERTY.MEM3_LAYERED PROPERTY.MEM3NL PROPERTY.MEM3NL_LAYERED PROPERTY.MEM4 PROPERTY.MEM4NL PROPERTY.SHELL3 PROPERTY.SHELL4 PROPERTY.SHELL4_LAYERED PROPERTY.SHELL6 PROPERTY.SOLID4 PROPERTY.SOLID8 PROPERTY.TRUSS2 PROPERTY.USERL2 PROPERTY.USERL3 PROPERTY.USERP3 PROPERTY.USERP4 PROPERTY.USERV8 RATE RESTRAINT.CARDAN RESTRAINT.JOINT RESTRAINT.KELVIN RESTRAINT.POINT RESTRAINT.SIX_DOF RESULT_ANIMATION_FE RIGID_ELEMENT RUNID SCALING SELECT SENSOR SIGNAL SPOTWELD.NODE_NODE SPOTWELD.THREE_NODE STATE STRAP SUPPORT SURFACE.CYLINDER
Altair Engineering

SURFACE.PLANE SWITCH SYSTEM.MODEL SYSTEM.REF_SPACE TIME_HISTORY_CONTACT TIME_HISTORY_ENERGY TIME_HISTORY_FE TIME_HISTORY_MB TIME_HISTORY_SYSTEM USER_INT Marc ASSUMED (ASSUMED STRAIN) AUTO INCREMENT Body 3D Deformable Body 3D Rigid CBUSH Constant Dilatation Contact Header Contact Table CONTACT_TYPE Disp_chang DIST_LOADS DIST LOADS (CONTROL CARD) E_1 E_2 E_3 E_5 E_6 E_7 E_9 E_10 E_11 E_14 E_18 E_20 E_21

Altair Engineering
E_25 E_26 E_27 E_28 E_29 E_32 E_33 E_34 E_35 E_38 E_39 E_45 E_52 E_53 E_54 E_55 E_57 E_58 E_59 E_60 E_61 E_63 E_64 E_66 E_67 E_68 E_69 E_70 E_74 E_75 E_78 E_80 E_81 E_82 E_83 E_84 E_89 E_95
Altair Engineering

E_96 E_98 E_114 E_115 E_116 E_117 E_118 E_119 E_120 E_124 E_125 E_126 E_127 E_128 E_129 E_130 E_134 E_138 E_139 E_140 E_157 E-195 ELSTO FEATURE Finite Fixed_Acce Fixed_Disp Fixed_Pres FOLLOW FOR FOUNDATION Init_Disp INITIAL_vel LARGE DISP MASSES MAT_FOAM MAT_ISOTROPIC MAT_MOONEY MAT_OGDEN

Altair Engineering
MAT_ORTHOTROPIC MOMENT MPC CHECK NO LIST OPTIMIZE ORIENTATION OSET PBUSH PLASTICITY POINT_LOAD POST PROP_GEOMETRY RBE RBE2 RBE3 SHELL SECT SIZING SOLVER SPRING SUMMARY TABLE TIE TITLE TYING tying100 UPDATE VERSION NASTRAN
The following cards are supported in Nastran:
ACMODL AEFACT ASCRCE ASET ASET1
Altair Engineering

BCBODY BCTABLE BCPARA BEGIN BULK BMFACE BNDFREE1 BNDFX1 BSET1 BSURF BSURFS BULK-UNSUPPORTED_CARD CAABSF CAERO1 CAERO2 CASE-UNSUPPORTED CARD CBAR CBEAM CBEND CBUSH CBUSH1D CDAMP1 CDAMP2 CDAMP3 CDAMP4 CELAS1 CELAS2 CELAS3 CELAS4 CEND CFAST CGAP CHACAB CHBDYE CHEXA (20-noded) CHEXA (8-noded) CMASS1 CMASS2

Altair Engineering
CMASS3 CMASS4 CONM1 CONM2 CONROD CORD1C CORD1R CORD1S CORD2C CORD2R CORD2S CPENTA (6-noded) CPENTA (15-noded) CQUAD4 CQUAD8 CQUADR CROD CSET1 CSHEAR CSUPER CSUPEXT CTETRA (4-noded) CTETRA (10-noded) CTRIA3 CTRIA6 CTRIAR CTUBE CVISC CWELD DAREA DCONADD DCONSTR DDVAL DEFORM DELAY DEQATN DESGLB
Altair Engineering

DESOBJ DESSUB DESVAR DIAG DLINK DLINK2 DLOAD DOPTPRM DPHASE DRESP1 DRESP2 DSCREEN DTABLE DTISPECSEL DVCREL1 DVCREL2 DVMREL1 DVMREL2 DVPREL1 DVPREL2 EIGB EIGC EIGP EIGR EIGRL ENDDATA EXEC_UNSUPPORTED_CARDS FLFACT FLUTTER FORCE FREQ FREQ1 FREQ2 FREQ3 FREQ4 FREQ5 GENEL

Altair Engineering
GLOBAL CASE CONTROL GLOBAL OUTPUT REQUEST GRAV GRDSET GRID HM_ELAS HM_SPRING ID INCLUDE BULK INCLUDE_CTRL INCLUDE_EXEC K2PP LOAD LOADSEQ MARCOUT MAT1 MAT2 MAT4 MAT5 MAT8 MAT9 MAT10 MATEP MATG MATHE MATHP MATS1 MATT1 MAXLINES MAXMIN MBOLT MBOLTUS MINMAX MOMENT MPC MPCADD NLAUTO
Altair Engineering

NLDAMP NLPARM NLRGAP NLSTRAT NSMADD NSM1 NSML1 NTHICK OMIT1 OMIT_BEGIN_BULK OMIT_CEND OMIT_END_BULK PAABSF PACABS PAERO1 PAERO2 PANEL PARAM PBAR PBARL PBEAM PBEAML PBEND PBUSH PBUSH1D PBUSHT PCOMP PCOMPG PCONV PDAMP PELAS PELAST PFAST PGAP PLOAD PLOAD1 PLOAD2

Altair Engineering
PLOAD4 PLOTEL PLSOLID PMASS PROD PSEAM PSHEAR PSHELL PSOLID PTUBE PVISC PWELD QBDY1 QSET1 QVOL RANDPS RBAR RBE2 RBE3 RFORCE RJOINT RLOAD1 RLOAD2 RSPEC SEBNDRY SEBSET1 SECSET1 SEQSET1 SESET SET SET (Control Card) SET1 SEUSET1 SNORM SOL SPC SPCADD
Altair Engineering

SPCD SPOINT SUBCASE SUBTITLE SUPORT SUPORT1 SWLDPRM TABDMP1 TABLED1 TABLED2 TABLED3 TABLED4 TABLEM1 TABLEM2 TABLEM3 TABLEM4 TABLES1 TABLEST TABRND1 TEMP TEMPD TIC TIME TITLE TLOAD1 TLOAD2 TRIM TSTEP TSTEPNL USET USET1 PAM-CRASH
The following cards are supported in PAM-CRASH: ACC3D / ACFLD /

Altair Engineering
ADAPT / AIRBAGCHECK ALLOCATE ANALYSIS BAR / BEAM / BEAPLOT BOUNC / BSHEL / CNODE / CONLO / COUPLING CPULIMIT CTRL / CYLINDRI DAMP / DATACHECK DEBUG DELNOD DIS3D / ELINK / ENDDATA FILE FLEX-TOR FRAME / FREE FRICT / FUNCT / FZMET / GASPEC / GENERAL GROUP / INCLU / INVEL / JOINT / KINJ KJOIN /
Altair Engineering

LIST/NOLIS LLINK / LOCUR / MASS / MBSYS_RI MBSYS_SP MEMBR / MERGEGAP METRIC MNTR NODCO / NODCO_S / NODE / NODPLOT NSMAS PICK / PIPE PLANAR PLINK / PREFILTER PRESH / PRESO / PRINT/NOPRINT RAC3D / RAN3D / RBODY / RESTARTFILES RETRA / RETRACTR REVOLUTE REZONE RIGBO RIGBO / RIGBO_S / RUPMO / RVE3D / SCRATCHDIR

Altair Engineering
SECFO / SENPT / SENSO / SENSOR / SHELL / SHELLCHECK SHLTHP SHLPLOT SIGNAL SLINK / SLINT1 SLINT2_E SLINT2_N SLINT3 SLINT4 SLINT5 SLINT6 SLINT7 SLINT10 SLINT11 SLINT12 SLINT13 SLINT14 SLINT15 SLINT18 SLINT21 SLINT23 SLINT24 SLINT26 SLINT31 SLINT32 SLINT33 SLINT34 SLINT36 SLINT37 SLINT42 SLINT46
Altair Engineering

SLIPR / SOLID / SOLPLOT SOLVER SPHERICA SPOTBEAM SPOTCONN SPOTERRO SPOTW / SPRGBM / SPRING / SUBDF / SUBRUN TCTRL / TETRA / TETR4 / THLBM / THLKJ / THLOC / THLNO / THLSO / THLSH / THLSW / THPLOT TIMESTEP TITLE / TRAFO / TRANSLAT TRIA_C TRSFM / TSHEL / TYPE 1 TYPE 2 TYPE 5 TYPE 7 TYPE 11 TYPE 16

Altair Engineering
TYPE 17 TYPE 18 TYPE 19 TYPE 20 TYPE 21 TYPE 22 TYPE 24 TYPE 25 TYPE 26 TYPE 28 TYPE 30 TYPE 31 TYPE 35 TYPE 36 TYPE 37 TYPE 41 TYPE 42 TYPE 45 TYPE 52 TYPE 61 TYPE 62 TYPE 71 TYPE 80-83 TYPE 99 TYPE 100 TYPE 101 TYPE 102 TYPE 103 TYPE 105 TYPE 106 TYPE 107 TYPE 108 TYPE 109 TYPE 110 TYPE 115 TYPE 116 TYPE 117
Altair Engineering

TYPE 118 TYPE 121 TYPE 126 TYPE 128 TYPE 130 TYPE 131 TYPE 132 TYPE 143 TYPE 150 TYPE 151 TYPE 161 TYPE 162 TYPE 171 TYPE 200 TYPE 201 TYPE 202 TYPE 203 TYPE 204 TYPE 205 TYPE 212 TYPE 213 TYPE 214 TYPE 220 TYPE 221 TYPE 222 TYPE 223 TYPE 224 TYPE 230 TYPE 301 TYPE 302 TYPE 303 TYPE 304 UNIT UNIVERSA VELBC / VEL3D / VERSION

Altair Engineering
PAM-CRASH 2G
The following cards are supported in PAM-CRASH 2G: ACC3D / ACFLD / ADAPT / AIRBAGCHECK ANALYSIS ASSOCIATE AUTOSLEEP BAGIN / BAR / BASE_BODY BEAM / BELTS / BOUNC / BSHEL / CCTRL / CHAMBER / CNODE / CNTAC / Type 1 CNTAC / Type 10 CNTAC / Type 13 CNTAC / Type 14 CNTAC / Type 15 CNTAC / Type 16 CNTAC / Type 17 CNTAC / Type 18 CNTAC / Type 19 CNTAC / Type 21 CNTAC / Type 33 CNTAC / Type 34 CNTAC / Type 36 CNTAC / Type 37 CNTAC / Type 44 CNTAC / Type 46 CNTAC / Type 54
Altair Engineering

CONLO / COUPLING DAMP / DATACHECK DCOMP DEBUG DIS3D / DIS3DM / DIS3DX / ECTRL / EDG ELINK / END_BAGIN END_CHAMBER ENDDATA EXT_SKIN FILE FPM FPM_HOLE FRAME / FRICT / FUNCT / GAS GASPEC / GEN_INI_COND GES / GROUP / INCLU / INFLATOR INI_COND INPUTVERSION INVEL / JET JOINT / KJOIN / LEAKAGE LLINK /

Altair Engineering
LOCAL_H MASS MASS_GES / MAT_SECURE MAXMEMORY MBSYS / MERGEGAP MEMBR / METRIC / METRICCHECK MTOCO / NODCO / NODE / NSMAS / OCTRL / PART / PICK PICKING / PIPE PLANE PLINK / PLINK_VI PLY PLYDATA PREBM / PREFA / RAC3D / RAN3D / RBODY / RDA3D / RDD3D / RDV3D / RESTARTFILES RETRA / RVE3D / RUNEND RUPMO /
Altair Engineering

RWALL / RWALL_KIN_CHECK SECFO / SECFO_CONTACT / SECFO_PLANE / SECFO_SECTION / SECFO_SUPPORT / SECFO_VOLFRAC / SECTION SEG SENPT / SENPTG / SENSO / SENSOR / SHELL / SHELLCHECK SIGNAL SLINK / SLIPR / SOLID / SOLIDCHECK SOLID4N SOLVER SPCTRL SPH SPRING / SPRGBM / STOPRUN SUBDF / SUBRUN SUBTA / SUPPORT TCTRL / TETRA / TETR4 / THELE / THLOC /

Altair Engineering
THNOD / TIED / TITLE / TRANSFORMATION / TRSFM / TSHEL / TYPE 1 TYPE 2 TYPE 5 TYPE 7 TYPE 11 TYPE 16 TYPE 17 TYPE 18 TYPE 20 TYPE 21 TYPE 22 TYPE 25 TYPE 26 TYPE 30 TYPE 31 TYPE 36 TYPE 37 TYPE 41 TYPE 42 TYPE 45 TYPE 52 TYPE 61 TYPE 62 TYPE 71 TYPE 99 TYPE 100 TYPE 101 TYPE 102 TYPE 103 TYPE 105 TYPE 106
Altair Engineering

TYPE 107 TYPE 108 TYPE 109 TYPE 110 TYPE 115 TYPE 116 TYPE 117 TYPE 118 TYPE 121 TYPE 126 TYPE 128 TYPE 130 TYPE 131 TYPE 132 TYPE 143 TYPE 150 TYPE 151 TYPE 161 TYPE 162 TYPE 171 TYPE 200 TYPE 201 TYPE 202 TYPE 203 TYPE 204 TYPE 205 TYPE 212 TYPE 213 TYPE 214 TYPE 220 TYPE 221 TYPE 222 TYPE 223 TYPE 224 TYPE 230 TYPE 301 TYPE 302

Altair Engineering
TYPE 303 TYPE 304 UNIT VEL3D / VOLFRAC WALL_FABRIC WALL_OPENING
PERMAS
The following cards are supported in PERMAS: $ADDMODES $BEAM2 $BECOC $BECOS $COMPONENT $COMPRESS $CONA3 $CONA4 $CONA6 $CONA8 $CONDUCTIVITY - materials $CONDUCTIVITY - loads $CONLOAD $CONS3 $CONS4 $CONS6 $CONS8 $CONSTRAINTS $CONTACT $CONTVAL $COOR $DAMP1 $DAMP3 $DAMP6 $DAMPING
Altair Engineering

$DENSITY $DIELECTRIC $DISLOAD $DISLOADN $ECHO $ELASTIC $ELCONDUCT $ELPROP $ELSYS $ENTER MATERIAL $ESET $ESETBIN $FLA2 $FLA3 $FLDENS $FLHEX8 $FLHEX20 $FLPENT6 $FLPENT15 $FLPYR5 $FLTET4 $FLTET10 $FLUID $FREQLOAD $FREQUENCY $FSINTA3 $FSINTA4 $FSINTA6 $FSINTA8 $FUNCTION $GASKET $GEODAT $GKHEX8 $GKHEX20 $GKPNT6 $GKPNT15 $GSKLOAD

Altair Engineering
$GSKUNLOAD $HARDENING $HEATCAP $HEXE8 $HEXE20 $INERTIA $INERTIAX $INIVAL $JOIN $LOADA3 $LOADA4 $LOADA6 $LOADA8 $LOADING $LOADS $MASS3 $MASS6 $MATERIAL $MODDAMP $MPC MPC GENERAL $MPC ISURFACE $MPC JOIN $MPC_RIGID $MPC_SAME $MPC WLDSURFACE $MPC WLSCN $MPC WLSSURFACE $NLDAMP $NLDAMPR $NLSTIFF $NLSTIFFR $NSET $NSETBIN $PENTA15 $PENTA6 $PERMEABILITY
Altair Engineering

$PLASTIC $PLOTA3 $PLOTA4 $PLOTA6 $PLOTA8 $PLOTL2 $PLOTL3 $POINTS $PRESCRIBE/PREVAL $PRETENSION LOAD $PRETENSION PLANE $PRETENSION THREAD $PYRA5 $QUAD4 $QUAM4 $REFSYS $RIGID $ROTB $RSYS $SAME $SFSET $SHEAR4 $SHELL3 $SHELL4 $SITUATION $SPRING1 $SPRING3 $SPRING6 $SUPPRESS $SURFABS $SURFACE $SYSTEM TEMP TEMPFILM $TET4 $TET10 $THERMEXP

Altair Engineering
$TRANSLOAD $TRIA3 $TRIA3K $TRIM3 $TRIM6 $TRIMS6 $VOLDRAG $X1DAMP3 $X1DAMP6 $X1GEN6 $X2GEN6 $X1MASS3 $X1MASS6 $X1STIFF3 $X1STIFF6 $X2DAMP3 $X2DAMP6 $X2GEN6 $X2STIFF3 $X2STIFF6 $YIELD
Samcef .BPR .CLM .ETASHELL .ETASOLID .FRA .HYP .LAM .MAT, ANISOTROPIC .MAT, ISOTROPIC .MAT, ORTHOTROPIC .MCT .NOE
Altair Engineering

.PHP SHELL .PLI .STI

Altair Engineering
Unsupported Cards by Solver

Radioss (Block Format) The following D00 cards are not supported for RADIOSS (Block Format) 5.1 and 9.0:
/ADMESH/STATE/SHELL /ADMESH/STATE/SH3N /ALE/CLOSE /ANIM/VERS /BCS/LAGMUL /BEM/FLOW /BOX /BOX/BOX /CNODE /EBCS/MONVOL /EULER/MAT /EIG /EOS/GRUNEISEN /EOS/POLYNOMIAL /EOS/TILLOTSON /EXTERN/LINK /FAIL/POWER_DAM /FAIL/XFEM_FLD /FAIL/XFEM_JOHNS /FAIL/XFEM_TBUTC /FXBODY /GJOINT /GAUGE /IBVEL /IMPLICIT /INICONT /INIVOL /IMPVEL/LAGMUL /INIBRI /INIQUA /INISHE/AUX or /INISH3/AUX /INISHE/EPSP or /INISH3/EPSP /INISHE/EPSP F or /INISH3/EPSP F /INISHE/ORTHO or /INISH3/ORTHO
Altair Engineering

/INISHE/STRA F or /INISH3/STRA F /INISHE/STRS F/GLOB /INTER/HERTZ /INTER/HERTZ/TYPE17 /INTER/LAGDT /INTER/LAGDT/TYPE7 /INTER/LAGMUL/TYPE2 /INTER/LAGMUL/TYPE16 /INTER/LAGMUL/TYPE17 /KEY /LAGMUL /MADYMO/EXFEM /MADYMO/LINK /MAT/LAW69 /MAT/LAW74 /MAT/LAW77 /MAT/LAW78 /MPC /PROP/TYPE25 (SPR_AXI) /PROP/TYPE28 (NSTRAND) /PROP/TYPE35 (STITCH) /PROP/USER4 /RBODY/LAGMUL /RWALL/LAGMUL /SHEL16 /STATE/STR_FILE /SUBMODEL /SURF/MDELLIPS /TH/FXBODY /TH/GAUGE /TH/NSTRAND /TH/PART /UNIT/name /XELEM /XREF
Radioss (Bulk), Nastran

Altair Engineering
This interface is the same for both Nastran and Radioss (Bulk), and can handle unsupported cards in several ways. There are three basic types of unsupported cards: Fully unsupported cards, partially supported cards and forced unsupported cards. Fully unsupported cards are read in and written out with the UNSUPPORTED_CARDS control card. This is described in more detail below. Partially unsupported cards are keywords that are recognized, but may have new or unrecognized fields within the card. HyperMesh will read the card and all supported fields, but will ignore any unrecognized fields (meaning that unrecognized data will be lost). Forced unsupported cards are manually added to the UNSUPPORTED_CARDS control card through the use of $HM_BEGIN_UNSUPPORTED and $HM_END_UNSUPPORTED HyperMesh comments in the input deck itself. These are described in more detail below.
Unsupported Cards
Cards that arent recognized by the HyperMesh interface are automatically written into one of three [two for Radioss] control cards depending on where they exist within the input file. They only receive simple supported as text, and are written in and out of the same section of the input file. EXEC_UNSUPPORTED_CARDS [Nastran only] Unrecognized cards starting from the top of the input file until the CEND keyword are stored in this control card, and written back out to the same part of the file. This is known as the executive control section. CASE_UNSUPPORTED_CARDS Unrecognized cards between the CEND keyword and the BEGIN BULK keyword are stored in this control card, and written back out to the same part of the file. This is known as the case control section. BULK_UNSUPPORTED_CARDS Unrecognized cards between the BEGIN BULK keyword and the ENDDATA keyword are stored in this control card, and written back out to the same part of the file. This is known as the bulk data section.
Forced Unsupported Cards

Any block of text in an input file can be forced into any of the UNSUPPORTED_CARDS by bracketing the text with $HM_BEGIN_UNSUPPORTED and $HM_END_UNSUPPORTED.
Altair Engineering

For example, consider the DTPL card shown above with a new field that isnt supported in HyperMesh. Without forcing the entire card into UNSUPPORTED_CARDS, the NEWFIELD would become lost during import/export.
Include Files
Include files can also handle unsupported cards in the same way as the master file as described above. Abaqus
The Abaqus interface can handle several types of unsupported cards. Unsupported materials Unsupported cards (model part) Unsupported step data (history part) Unsupported material Unsupported materials can be handled in two ways. Automatically detect materials that contain certain cards that are currently unsupported. Once detected, those cards are preserved as simple text within the material card. On export, they will be written within the original material block and labeled with the comment **HM_UNSUPPORTED_MATERIAL Declare entire materials as unsupported. To handle unsupported materials by this method: Insert the comment **HM_GENERIC_MATERIAL before each *MATERIAL card that contains unsupported keywords. Only materials with the comment will be imported as plain text. or

Altair Engineering
Select the Generic material check box on the options panel of the Utility Menu. All material cards will be set as unsupported. If a supported material card has a parameter that is currently unsupported, the card will be imported but the parameter will be ignored. You will receive a warning message during the import process. Contents of unsupported or generic materials can be reviewed or edited with the card editor in the Model Browser. Unsupported cards (model data) In addition to the unsupported material card and the generic material there are three places where currently unsupported keywords can be stored. All concerned cards placed before the first *NODE card will go to the UNSUPPORTED_CARDS_START, those between *NODE and last *MATERIAL block are placed in UNSUPPORTED_CARDS_MIDDLE card and all other unsupported cards of the model part can be found in UNSUPPORTED_CARDS after import. Once unsupported cards are detected you will receive a warning message during import. The cards and their contents can be reviewed in the control cards area or in the Model Browser. On export, a comment is inserted before each type of unsupported card: **HM_UNSUPPORTED_CARDS_START **HM_UNSUPPORTED_CARDS_MIDDLE **HM_UNSUPPORTED_CARDS The start of unsupported cards will be placed before the first node card, the middle part behind the last *MATERIAL card and the last part will be placed directly before the Step definition. However, there is one special case for unsupported model data cards. Abaqus provides several type options for the *INITIAL CONDITIONS card. Currently, the VELOCITY, TEMPERATURE, and FLUID PRESSURE types are supported. For these cards, a load collector will be created on import. However, in cases where the type parameter value is not one of these supported values, this card will be handled as an unsupported card according to the rules described above. Unsupported step data (history data) If unknown keywords are detected within a *STEP definition, they will be placed in the unsupported cards section within the step. There is an unsupported card available in every *STEP. New unsupported cards can also be added and exported by the Step Manager.
LS-DYNA
The complete list of LS-DYNA keywords that are not supported are listed below.
Altair Engineering

*ALE_FSI_PROJECTION *ALE_FSI_SWITCH_MMG_ID *ALE_UP_SWITCH *BOUNDARY_ACOUSTIC_COUPLING *BOUNDARY_CONVECTION_SEGMENT *BOUNDARY_CYCLIC *BOUNDARY_ELEMENT_METHOD_CONTROL *BOUNDARY_ELEMENT_METHOD_OPTION *BOUNDARY_ELEMENT_METHOD_FLOW *BOUNDARY_ELEMENT_METHOD_NEIGHBOR *BOUNDARY_ELEMENT_METHOD_SYMMETRY *BOUNDARY_ELEMENT_METHOD_WAKE *BOUNDARY_FLUX_OPTION *BOUNDARY_MCOL *BOUNDARY_PRESCRIBED_ACCELEROMETER_RIGID *BOUNDARY_PRESCRIBED_ORIENTATION_RIGID_ANGLES *BOUNDARY_PRESCRIBED_ORIENTATION_RIGID_DIRCOS *BOUNDARY_PRESCRIBED_ORIENTATION_RIGID_EULERP *BOUNDARY_PRESSURE_OUTFLOW_SEGMENT *BOUNDARY_PRESSURE_OUTFLOW_SET *BOUNDARY_RADIATION_SEGMENT *BOUNDARY_RADIATION_SEGMENT_VF_CALCULATE *BOUNDARY_RADIATION_SEGMENT_VF_READ *BOUNDARY_RADIATION_SET_EF_CALCULATE *BOUNDARY_RADIATION_SET_EF_READ *BOUNDARY_RADIATION_SET_VF_CALCULATE *BOUNDARY_RADIATION_SET_VF_READ *BOUNDARY_SLIDING_PLANE *BOUNDARY_SPH_SYMMETRY_PLANE *BOUNDARY_SYMMETRY_FAILURE *BOUNDARY_THERMAL_WELD *BOUNDARY_USA_SURFACE *CASE *CASE_BEGIN_CIDn *CASE_END_CIDN *CONSTRAINED_ADAPTIVITY

Altair Engineering
*CONSTRAINED_BUTT_WELD *CONSTRAINED_EULER_IN_EULER *CONSTRAINED_GENERALIZED_WELD_COMBINED_ID *CONSTRAINED_GENERALIZED_WELD_CROSS_FILLET_ID *CONSTRAINED_INTERPOLATION_LOCAL *CONSTRAINED_JOINT_CONSTANT_VELOCITY *CONSTRAINED_JOINT_GEARS *CONSTRAINED_JOINT_PULLEY *CONSTRAINED_JOINT_RACK_AND_PINION *CONSTRAINED_JOINT_ROTATIONAL_MOTOR *CONSTRAINED_JOINT_TRANSLATIONAL_MOTOR *CONSTRAINED_JOINT_SCREW *CONSTRAINED_JOINT_STIFFNESS_TRANSLATIONAL *CONSTRAINED_POINTS *CONSTRAINED_SPLINE *CONTACT_COUPLING *CONTACT_GEBOD_OPTION *CONTACT_GUIDED_CABLE *CONTACT_GUIDED_CABLE_SET *CONTACT_SURFACE_TO_SURFACE_CONTRACTION_JOINT(ID) *CONTACT_TIEBREAK_NODES_ONLY(ID) *CONTACT_TIED_SURFACE_TO_SURFACE_TITLE(ID) *CONTACT_TIED_SURFACE_TO_SURFACE_FAILURE TITLE(ID) *CONTACT_1D *CONTACT_2D_AUTOMATIC_NODE_TO_SURFACE *CONTACT_2D_AUTOMATIC_SINGLE_SURFACE *CONTACT_2D_AUTOMATIC_SURFACE_IN_CONTINUUM *CONTACT_2D_AUTOMATIC_TIED *CONTACT_2D_AUTOMATIC_TIED_ONE_WAY *CONTACT_2D_PENALTY *CONTACT_2D_PENALTY_FRICTION *CONTROL_CHECK_SHELL *CONTROL_FORMING_POSITION *CONTROL_FORMING_PROJECTION *CONTROL_FORMING_TEMPLATE *CONTROL_FORMING_TRAVEL *CONTROL_FORMING_USER
Altair Engineering

*CONTROL_NONLOCAL *DATABASE_ADAMS *DATABASE_H3OUT *DATABASE_BINARY_D3PART *DATABASE_BINARY_D3PROP *DATABASE_BINARY_FSIFOR *DATABASE_BINARY_D3CRACK *DATABASE_FSI_SENSOR *DATABASE_HISTORY_SPH_SET *DEFINE_CONNECTION_PROPERTIES_ADD *DEFINE_CONSTRUCTION_STAGES *DEFINE_CONTACT_VOLUME *DEFINE_CURVE_COMPENSATION *DEFINE_CURVE_DRAWBEAD *DEFINE_CURVE_ENTITY *DEFINE_CURVE_FUNCTION *DEFINE_DEATH_TIMES_NODES *DEFINE_DEATH_TIMES_RIGID *DEFINE_DEATH_TIMES_SET *DEFINE_ERODING_SINGLE_SURFACE *DEFINE_FRICTION_AUTOMATIC_GENERAL *DEFINE_FRICTION_AUTOMATIC_NODES_TO_SURFACE *DEFINE_FRICTION_AUTOMATIC_ONE_WAY_SURFACE_TO_SURFACE *DEFINE_FRICTION_AUTOMATIC_SINGLE_SURFACE *DEFINE_FRICTION_AUTOMATIC_SURFACE_TO_SURFACE *DEFINE_FRICTION_SINGLE_SURFACE *DEFINE_SET_ADAPTIVE *DEFINE_SPOTWELD_FAILURE_RESULTANTS *DEFINE_SPOTWELD_RUPTURE_PARAMETER *DEFINE_SPOTWELD_RUPTURE_STRESS *DEFINE_STAGED_CONSTRUCTION_PART *EF_CONTROL *EF_GRID *EF_MATERIAL *EF_TOGGLES *ELEMENT_BEAM_WARPAGE *ELEMENT_DIRECT_MATRIX_INPUT

Altair Engineering
*ELEMENT_SHELL_SOURCE_SINK *ELEMENT_SOLID_DOF *EOS_GASKET *EOS_JWLB *INCLUDE_BINARY *INCLUDE_NASTRAN *INCLUDE_PATH *INCLUDE_STAMPED_PART_SET_MATRIX_INVERSE *INCLUDE_STAMPED_SET *INCLUDE_TRANSFORM_BINARY *INITIAL_STRESS_DEPTH *INITIAL_STRESS_SHELL_SET *INITIAL_STRESS_TSHELL *INTERFACE_JOY *INTERFACE_LINKING_DISCRETE_NODE_NODE *LOAD_ALE_CONVECTION *LOAD_ALE_CONVECTION_ID *LOAD_BODY_POROUS *LOAD_DENSITY_DEPTH *LOAD_HEAT_CONTROLLER *LOAD_HEAT_GENERATION_SET *LOAD_HEAT_GENERATION_SOLID *LOAD_MOTION_NODE *LOAD_MOVING_PRESSURE *LOAD_REMOVE_PART *LOAD_SEGMENT_NONUNIFORM_ID *LOAD_SEGMENT_SET_NONUNIFORM_ID *LOAD_SSA *LOAD_STIFFEN_PART *LOAD_SURFACE_STRESS *LOAD_SURFACE_STRESS_SET *LOAD_THERMAL_TOPAZ *LOAD_VOLUME_LOSS *NODE_SCALAR *NODE_SCALAR_VALUE *MAT_ALE_VACCUM *MAT_ALE_VISCOUS
Altair Engineering

*MAT_ALE_GAS_MIXTURE *MAT_ANISOTROPIC_THERMOELASTIC *MAT_BRAIN_LINEAR_VISCOELASTIC *MAT_CFD_OPTION *MAT_COHESIVE_GENERAL *MAT_COHESIVE_MIXED_MODE *MAT_COHESIVE_TH *MAT_COMPOSITE_DIRECT *MAT_COMPOSITE_MATRIX *MAT_CONCRETE_BEAM *MAT_CONCRETE_EC2 *MAT_DAMAGE_1 *MAT_DAMAGE_2 *MAT_DAMAGE_3 *MAT_DRUCKER_PRAGER *MAT_EMMI *MAT_FHWA_SOIL *MAT_FHWA_SOIL_NBRASKA *MAT_GURSON_RCDC *MAT_HEART_TISSUE *MAT_HYSTERIC_SOIL *MAT_INV_HYPERBOLIC_SIN *MAT_ISOTROPIC_SMEARED_CRACK *MAT_JOHNSON_HOLMQUIST_CONCRETE *MAT_JOINTED_ROCK *MAT_LUNG_TISSUE *MAT_MCCORMICK *MAT_MODIFIED_FORCE_LIMITED *MAT_MODIFIED_JOHNSON_COOK *MAT_MOHR_COULOUMB *MAT_MOMENT_CURVATURE_BEAM *MAT_MUSCLE *MAT_ORTHO_ELASTIC_PLASTIC *MAT_ORTHOTROPIC_SMEARED_CRACK *MAT_PITZER_CRUSHABLE_FOAM *MAT_PLASTIC_GREEN-NAGHDI_RATE *MAT_PLASTIC_NONLINEAR_KINEMATIC

Altair Engineering
*MAT_PLASTICITY_COMPRESSION_TENSION_EOS *MAT_POLYMER *MAT_QUASILINEAR_VISCOELASTIC *MAT_RAMBERG-OSGOOD *MAT_RATE_SENSITIVE_COMPOSITE_FABRIC *MAT_RATE_SENSITIVE_POLYMER *MAT_RC_BEAM *MAT_RS_SHEAR_WALL *MAT_SEISMIC_BEAM *MAT_SEISMIC_ISOLATOR *MAT_SOIL_BRIC *MAT_SOIL_CONCRETE *MAT_SPECIAL_ORTHOTROPIC *MAT_SPRING_MUSCLE *MAT_SPRING_SQUAT_SHEARWALL *MAT_SPRING_TRILINEAR_DEGRADING *MAT_STEEL_CONCENTRIC_BRACE *MAT_THERMAL_ISOTROPIC_TD *MAT_THERMAL_ISOTROPIC_PHASE_CHANGE *MAT_THERMAL_ORTHTROPIC_TD *MAT_THERMAL_USER_DEFINED *MAT_THERMO_ELASTO_VISCOPLASTIC_CREEP *MAT_UNIFIED_CREEP *MAT_VISCO_ELASTIC_THERMAL *MAT_WTM_STM *MAT_WTM_STM_PLC *PARAMETER *PARAMETER_EXPRESSION *PART_ADAPTIVE_FAILURE *PART_MODES *PERTURBATION_NODE *PERTURBATINO_SHELL_THICKNESS *RAIL_TRACK *RAIL_TRAIN *SET_2D_SEGMENT(TITLE) *SET_2D_SEGMENT_SET(TITLE) *TERMINATION_BODY
Altair Engineering

*TERMINATION_CONTACT *TERMINATION_CURVE *TERMINATION_DELETED_SHELLS *TERMINATION_DELETED_SHELLS_SET *TERMINATION_NODE *USER_LOADING
MADYMO
DEFINE CRDSYS_REF_1 CRDSYS_REF_2
PAM-CRASH 2G 3D AMCTRL / ARGUMENT CNTAD / CONTACT CPCTRL CTCTRL / DRAWB END_MODULE EXPORT / FLCEL / FUNCTION H_POINT IMPFIL / IMPORT / KELVIN LINCO / LOCAL_H LOOKU / MARK /

Altair Engineering
Material Type 19 Material Type 24 Material Type 35 Material Type 80-83 MAXWELL MBSYS / MDBODY MGRID MODULE / MSTRM / MUSC1 / MUSCL / OUTPUT SCALEF_MGRID SECURE / SPCTRL / SPHEL / SUBCYCLE_ECL SYMPL / PERMAS The PERMAS interface can handle two different types of unsupported cards: Materials Solver cards Depending on which bracket or variant they belong to, unsupported keywords are maintained as ASCII text within the HyperMesh database and are placed in the right place on export again. Unsupported material Unsupported materials can be handled in two ways. Generic material Unsupported material If materials are completely unsupported, they will be read in as generic material, whereas unsupported cards which are dependent on a certain material will be imported as unsupported material and can be reviewed from within the material card image. On export, a comment will be written before each generic material (!!HM_GENERIC_MATERIAL) or unsupported material (!!HM_UNSUPPORTED_CARDS). Unsupported card mechanism Cards
Altair Engineering

Generic material
$SANDWICH $LAMINATE $FLFSOLID $MATERIAL TYPE= TRANS, ORTHO, MONOCLINIG, TRICLINIC, ANISO
Unsupported material
$DIELECTRIC $ELCONDUCT $FLDENS $NLELASTIC $NLKINHARD $PERMEABILITY $VISCOSITY
Unsupported cards In addition to the unsupported material card and the generic material, other unsupported data will be maintained based on the location in their bracket/variant and placed there again on export. The following table shows in which entity an unsupported card will go. All information is accessible after import through the card editor and will be written out exactly the same as imported. PERMAS Variant/Bracket $SYSTEM $STRUCTURE $CONSTRAINTS $LOADING $RESULTS Entity Control Card "System" Control Card "Unsupported_Structure" Load Step Load Step Output Block

Altair Engineering
Geometry
The following general geometry capabilities are available: Import geometry from an external CAD file Export geometry to an external CAD file Create new geometry Edit and defeature existing or imported geometry Create connectors on geometry Create loads/BCs on geometry Create meshes on geometry
See also Terminology CAD Interfacing Functionality
Altair Engineering

Terminology
The image below illustrates various geometric features, each labeled with the relevant terminology:

Altair Engineering
See also Nodes Free Points Lines Faces Surfaces Fixed Points Free Edges Shared Edges Suppressed Edges Non-manifold Edges Solids Bounding Faces Fin Faces
Altair Engineering

Full Partition Faces CAD Cleanup Tolerance Geometry Cleanup Tolerance Geometry Feature Angle

Altair Engineering
Nodes
A node is the most basic finite element entity. A node represents a physical position on the structure being modeled and is used by an element entity to define the location and shape of that element. It is also used as temporary input to create geometric entities. A node may contain a pointer to other geometric entities and can be associated directly to them. It is displayed as a small circle or sphere, depending on the mesh graphics mode. Its color is always yellow.
See also Geometry Terminology
Altair Engineering

Free Points
A free point is a zero-dimensional geometry entity in space that is not associated with a surface. It is displayed as a small "x". Its color is determined by the component collector to which it belongs. These types of points are typically used for weld locations and connectors.

Altair Engineering
Lines
A line represents a curve in space is not attached to any surface or solid. A line is a one-dimensional geometric entity. Its color is determined by the component collector to which it belongs. A line can be composed of one or more line types. Each line type in a line is referred to as a segment. The end point of each line segment is connected to the first point of the next segment. A joint is the common point between two line segments. Line segments are maintained as a single line entity, so operations performed on the line affect each segment of the line. In general, HyperMesh automatically uses the appropriate number and type of line segments to represent the geometry. All lines in HyperMesh are represented mathematically with the following formulations: straight elliptical NURBS Lines are different from surface edges and are sometimes handled differently for certain operations.
Altair Engineering

Faces
A face is a single Non-uniform Rational B-Spline (NURBS) and is the smallest area entity. It has a separate underlying mathematical definition, specified when it was created. All faces are represented mathematically with the following formulations: plane cylinder/cone sphere torus NURBS A surface can be made up of a single face type or of multiple face types. Multiple types are used for more complex surfaces that contain sharp corners or highly complex shapes.
See also Surfaces Geometry Terminology

Altair Engineering
Surfaces
A surface represents the geometry associated with a physical part. A surface is a two-dimensional geometric entity that may be used in automatic mesh generation. Its color is determined by the component collector to which it belongs. A surface is comprised of one or more faces. Each face contains a mathematical surface and edges to trim the surface, if required. When a surface has several faces, all of the faces are maintained as a single surface entity. Operations performed on the surface affect all the faces that comprise the surface. In general, HyperMesh automatically uses the appropriate number of and type of surface faces to represent the geometry. The perimeter of a surface is defined by edges. There are four types of surface edges: Free edges Shared edges Suppressed edges Non-manifold edges Surface edges are different from lines and are sometimes handled differently for certain operations. The connectivity of surface edges constitutes the geometric topology.
See also Faces Fixed Points Free Edges Shared Edges Suppressed Edges Non-manifold Edges Geometry Terminology
Altair Engineering

Fixed Points
A fixed point is a zero-dimensional geometry entity that is associated with a surface. Its color is determined by the surface to which it is associated. It is displayed as a small "o". The automesher places an FE node at each fixed point on the surface being meshed. A fixed point that is placed at the junction of three or more non-suppressed edges is called a vertex or vertex point. Such vertices cannot be suppressed (removed).
See also Surfaces Free Edges Shared Edges Suppressed Edges Non-manifold Edges Geometry Terminology

Altair Engineering
Free Edges
A free edge is an edge that is owned by only one surface. Free edges are colored red by default. On a clean model consisting of surfaces, free edges appear only along the outer perimeter of the part and around any interior holes. Free edges that appear between two adjacent surfaces indicate the existence of a gap between the two surfaces. The automesher will leave a gap in the mesh wherever there is a gap between two surfaces.
See also Surfaces Fixed Points Shared Edges Suppressed Edges Non-manifold Edges Geometry Terminology
Altair Engineering

Shared Edges
A shared edge is an edge that is owned, or shared, by two adjacent surfaces. Shared edges are colored green by default. When the edge between two surfaces is a shared edge, there is no gap or overlap between the two surfaces they are geometrically continuous. The automesher always places seed nodes along the length a shared edge and will produce a continuous mesh without any gaps along that edge. The automesher will not construct any individual elements that cross over a shared edge.
See also Surfaces Fixed Points Free Edges Suppressed Edges Non-manifold Edges Geometry Terminology

Altair Engineering
Suppressed Edges
A suppressed edge is shared by two surfaces but it is ignored by the automesher. Suppressed edges are colored blue by default. Like a shared edge, a suppressed edge indicates geometric continuity between two surfaces but, unlike a shared edge, the automesher will mesh across a suppressed edge as if were not even there. The automesher does not place seed nodes along the length of a suppressed edge and, consequently, individual elements will span across it. By suppressing undesirable edges you are effectively combining surfaces into larger logical meshable regions.
See also Surfaces Fixed Points Free Edges Shared Edges Non-manifold Edges Geometry Terminology
Altair Engineering

Non-manifold Edges
A non-manifold edge is owned by three or more surfaces. Non-manifold edges are colored yellow by default. They typically occur at "T" intersections between surfaces or when 2 or more duplicate surfaces exist. The automesher always places seed nodes along their length and will produce a continuous mesh without any gaps along that edge. The automesher will not construct any individual elements that cross over a T-joint edge. These edges cannot be suppressed.
See also Surfaces Fixed Points Free Edges Shared Edges Suppressed Edges Geometry Terminology

Altair Engineering
Solids
A solid is a closed volume of surfaces that can take any shape. Solids are three-dimensional entities that can be used in automatic tetra and solid meshing. Its color is determined by the component collector to which it belongs. The surfaces defining a solid can belong to multiple component collectors. The display of a solid and its bounding surfaces are controlled only by the component collector to which the solid belongs.
See also Bounding Faces Fin Faces Full Partition Faces Geometry Terminology
Altair Engineering

Bounding Faces
A bounding face is a surface that defines the outer boundary of a single solid. Bounding faces are shaded green by default. A bounding face is unique and is not shared with any other solid. A single solid volume is defined entirely by bounding faces.
See also Solids Fin Faces Full Partition Faces Geometry Terminology

Altair Engineering
Fin Faces
A fin face is a surface that has the same solid on all sides i.e. it acts as a fin inside of a single solid. Fin faces are shaded red by default. A fin face can be created when manually merging solids or when creating solids with internal fin surfaces.
See also Solids Bounding Faces Full Partition Faces Geometry Terminology
Altair Engineering

Full Partition Faces

A full partition face is a surface that defines a shared boundary between one or more solids. Full partition faces are shaded yellow by default. A full partition face can be created when splitting a solid or when using Boolean operations to join multiple solids at shared or intersecting locations.
See also Solids Bounding Faces Fin Faces Geometry Terminology

Altair Engineering
CAD Cleanup Tolerance

The CAD cleanup tolerance is used to determine if two surface edges are the same and if two surface vertices are the same. There are two items controlled by this setting: The determination of if two surface edges are close enough to be automatically combined (creating shared edges) If a surface is degenerate and should be removed If you use the automatic setting, the complexity of the surface and edge geometries are taken into account and a tolerance is selected to maximize the number of shared edges. To specify a manual cleanup tolerance value, it must be greater than the default value. The readers only modify data if the data stays within the original data tolerance. Increasing the tolerance may cause problems. When this value is modified, any features equal to or less than the tolerance are eliminated. The readers do not include any edge with a length less than the tolerance; if there are edges present that are important to the surface, that surface will be distorted, or will fail to trim properly. Similarly, surfaces smaller than the tolerance may not be imported. If the file you have read has many very short edges, it may be worthwhile to reread the file using a larger tolerance. The same holds true if surfaces appear to be "inside out" when surface lines are displayed. The tolerance value should not be set to a value greater than the node tol used for your element mesh, set in the Options panel.
Altair Engineering

Geometry Cleanup Tolerance

Cleaning up refers to fixing geometry data by creating proper topology, defeaturing, and eliminating extraneous vertices. The cleanup tolerance value specifies how much HyperMesh is allowed to modify the geometry in the course of cleaning it, either manually or automatically. Since the geometry is approximated with a finite element mesh, a cleanup tolerance that is less than the node tolerance used in the mesh generation is required. The tolerance value should not be set to a value greater than the node tol used for your element mesh, set in the Options panel.

Altair Engineering
Geometry Feature Angle

This setting is used to determine when model geometry should have a new vertex added (creating two surfaces from one) or removed (merging two surfaces into one).
Altair Engineering

CAD Interfacing
This section describes the support provided by the CAD readers/writers, as well as the options available for importing/exporting CAD geometry data into/from HyperMesh. These readers/writers are dynamically loaded upon demand, and include support for the following CAD formats:
Import ACIS CATIA V4/V5 DXF IGES JT Parasolid PDGS Pro E SolidWorks STEP Tribon UG VDAFS
Export IGES
See also CAD Import CAD Export

Altair Engineering
CAD Import
This section describes the support provided by the CAD readers, as well as the options available for importing CAD geometry data. These readers are dynamically loaded upon demand, and include support for the following CAD formats:
ACIS CATIA V4/V5 DXF IGES JT Parasolid PDGS Pro E SolidWorks STEP Tribon UG VDAFS
See also CAD Reader Support CAD Import Options CAD Export
Altair Engineering

CAD Reader Support

Latest CAD Version CAD Format Supported ACIS CATIA DXF IGES JT Parasolid PDGS Pro E SolidWorks STEP Tribon r19 v4 v5r20 AutoCAD 12 v6 JAMA-IS 9.4 v19 v26 Wildfire 5 2010 AP203 AP214 TXHSTL-R Tribon XML Export v1.3 NX5 NX6 NX7 v2 Platforms1
x86
Y Y Y Y Y Y Y Y Y Y Y
Windows x86_64
Linux x86
x86_64
UG VDAFS
1 2
Y Y
Y Y
N Y
Y2 Y
Refer to the official HyperWorks platform support list for full details. UG NX7 is not available on Linux64.
See also ACIS Reader Support CATIA Reader Support DXF Reader Support IGES Reader Support JT Reader Support Parasolid Reader Support PDGS Reader Support Pro E Reader Support SolidWorks Reader Support STEP Reader Support Tribon Reader Support

Altair Engineering
UG Reader Support VDAFS Reader Support CAD Import Options
Altair Engineering

ACIS Reader Support

The following entities are supported by the ACIS reader: Free points Free curves Surfaces Quilt bodies Solid bodies
See also CAD Reader Support ACIS Import Options

Altair Engineering
CATIA Reader Support

The CATIA v5 reader supports .CatProduct, .CatPart and .cgr files. The following entities are supported by the CATIA v5 reader: Free points Free curves Surfaces Quilt bodies Solid bodies Facets/triangles Parts (.CatPart) Assemblies (.CatProduct) Entities that are part of other entities are not created as independent entities. CATIA models are stored in millimeter scale, so an appropriate scale factor is required to use other unit systems.
The CATIA v4 reader supports both .model and .exp files. The following entities are supported by the CATIA v4 reader: Point (type 1) Line segment (type 2) Parametric curve (type 3) Conics (types 20-23) Composite curve (type 24) Parametric surface (type 5) Face (type 6) Volume (type 7) Coordinate system (type 8) Skin (type 13) Mock-up solids (type 17-1) Exact solids (type 17-2) Ditto (type 28)
See also
Altair Engineering

CAD Reader Support CATIA Import Options

Altair Engineering
DXF Reader Support

The following entities are supported by the DXF reader: Free points (POINT) Free curves (LINE) Surfaces (3DFACE) Solids (SOLID) Facets/triangles (POLYLINE with Group Code 70=64 for polyface mesh)
See also CAD Reader Support DXF Import Options
Altair Engineering

IGES Reader Support

The following entities are supported by the IGES reader: Circular arc (100) Composite curve (102) Conic arc (104) Copius data (106) Plane (108) Line (110) Parametric spline curve (112) Parametric spline surface (114) Point (116) Ruled surface (118, form 1 only) Surface of revolution (120) Tabulated cylinder (122) Direction (123) Transformation matrix (124) Flash (125) Rational B-spline curve (126) Rational B-spline surface (128) Offset surface (140) Boundary (141) Curve on a parametric surface (142) Bounded surface (143) Trimmed (parametric) surface (144) Manifold solid B-rep object (186) Plane surface (190) Right circular cylindrical surface (192) Right circular conical surface (194) Spherical surface (196) Toroidal surface (198) Angular dimension (202)

Altair Engineering
Diameter dimension (206) General label (210) General note (212) Leader (214) Linear dimension (216) Radius dimension (222) General symbol (228) Sectioned area (230) Line font definition (304) Subfigure definition (308) Color definition (314) Form 7 group without back pointers (402) Drawing (404) Form 15 name (406) Singular subfigure instance (408) View (410) Vertex (502) Edge (504) Loop (508) Face (510) Shell (514)
See also CAD Reader Support IGES Import Options
Altair Engineering

JT Reader Support
The following entities are supported by the JT reader: Free points Free curves Surfaces Solid bodies (JT B-rep) Embedded Parasolid (XT B-rep) Facets (triangular only)
See also CAD Reader Support JT Import Options

Altair Engineering
Parasolid Reader Support

The following entities are supported by the Parasolid reader for schema up to SCH_20000 (20) Free points Free curves Surfaces Quilt bodies Solid bodies Assemblies
See also CAD Reader Support Parasolid Import Options
Altair Engineering

PDGS Reader Support

The following entities are supported by the PDGS reader: Entity #5
See also CAD Reader Support PDGS Import Options

Altair Engineering
Pro E Reader Support

The following entities are supported by the Pro E reader: Free points Free curves Surfaces Quilt bodies Solid bodies Assemblies Assembly Level Features are currently not supported. Family Tables are currently not supported.
See also CAD Reader Support Pro E Import Options
Altair Engineering

SolidWorks Reader Support

The following entities are supported by the SolidWorks reader: Free points Free curves Surfaces Solid bodies Assemblies
See also CAD Reader Support SolidWorks Import Options

Altair Engineering
STEP Reader Support

The following entities are supported by the STEP reader: Free points Free curves Surfaces Quilt bodies Solid bodies Facets/triangles Assemblies
See also CAD Reader Support STEP Import Options
Altair Engineering

Tribon Reader Support

The following entities are supported by the Tribon reader: Plane panels Curved panels Knuckled panels Plane plates Curved plates Pillars Stiffeners (also with sub-flanges) Curved stiffeners Face plates (also with sub-flanges) Flanges Brackets
An assembly tree is created and organized as follows: 1 assembly corresponding to the whole ship (1 ship per part). 1 assembly per block. 1 assembly per PlanePanel. 1 component for the detailed contour of the current PlanePanel (with relevant option). 1 component for the simple contour of the current PlanePanel (with relevant option). 1 component per PlanePlateGroup. The material name, material side, thickness and offset are created as metadata. If material data are available, a PSHELL material is created. 1 surface per PlanePlate. The profile existing in the file is used for the external loop. Holes can be added as internal loops (with relevant option). 1 component per PlanePillarGroup. 1 set of trace lines per PlanePillar. 1 surface per web (with relevant option). 1 component per PlaneFlangeGroup. 1 set of trace lines per PlaneFlange. 1 component per PlaneStiffenerGroup. 1 set of trace lines per PlaneStiffener. 1 surface per web and per flange (with relevant option). 1 component per PlaneFaceplateGroup.

Altair Engineering
1 set of trace lines per PlaneFaceplate. 1 surface per web and per flange (with relevant option). 1 assembly per sub-PlanePanel. The contents correspond to the ones for normal PlanePanels. 1 assembly per PlaneBracketGroup. 1 component per bracket if no sub-elements exist (stiffeners, planeplates, flanges). 1 assembly if sub-elements exist. 1 surface per PlaneBracket. The profile existing in the file is used for the external loop. No holes are allowed by the Tribon format. If sub-elements are present in the current PlaneBracketGroup, a specific component is created for the surface in order to keep it separate from its sub-elements. 1 component per PlaneStiffenerGroup sub-element (no flanges inside the stiffener group are allowed). 1 component per PlaneFaceplateGroup sub-element (no flanges inside the faceplate group are allowed). 1 component per PlaneFlangeGroup sub-element. 1 assembly per CurvedPanel. 1 component for the simple contour of the current CurvedPanel (with relevant option). 1 component per CurvedPlateGroup. 1 surface per CurvedPlate. The profile existing in the file is used for the external loop. Internal holes are implemented. 1 component per CurvedStiffenerGroup. 1 set of trace lines per CurvedStiffener. 1 assembly per KnuckledPanel.
PlanePlates, CurvedPlates and PlaneBrackets are mapped as surfaces. Other objects are imported as curves, lying on the plates. Groups of objects may share similar properties (such as material, material side, thickness and offset). In this case, metadata are added to these objects, and if possible the material description is also created. Holes of curved surfaces are not taken into consideration for this release. The reader instantiates objects in their nominal position, hence there may be gaps between panels, brackets etc due to idealizations that dont take into account thickness. Hence, no stitching between surfaces is performed on import. Available material fields include Young's modulus, Poisson's ratio, expansion coefficient, and density. Yield stress and ultimate stress are not imported. Each material is associated with a unique grade name. When a thickness is provided, the corresponding value is given to an HM object. Objects affected by material/thickness include PlanePlateGroup, PlanePillarGroup, PlaneFlangeGroup, PlaneStiffenerGroup, PlaneFaceplateGroup, PlaneBracketGroup, CurvedPlateGroup and CurvedStiffenerGroup.
Altair Engineering

See also CAD Reader Support Tribon Import Options

Altair Engineering
UG Reader Support
The UG reader utilizes the UGOpen library to read files from UG. The reader relies on a valid UG installation and license to access these libraries. Environment variables must be set appropriately to ensure proper access to these libraries. See the UG Environment Variables section for more information. Any UG file formats not supported by the available UG installation are not supported. The following entities are supported by the UG reader: UF_point UF_line UF_circle UF_conic UF_spline UF_faceted_model UF_solid When reading a UG assembly or part file with material information, the material information is read into HyperMesh as Nastran MAT1 material collectors. If there is more than one material associated to the entities in a given part file, HyperMesh splits the part into multiple component collectors. A property collector is always created when importing material information and assigned to the component (see note below), and the material collector is then associated to the respective property collector. The UG reader also recognizes midsurface thickness information for each part of an assembly. After the part is imported, the thickness information is stored in Nastran PSHELL property collectors. The thickness is imported only if a material property is associated to the part containing the mid-surface feature to which the thickness is applied. If no thickness information is present but material information does exist, an empty PSHELL property collector is created and the material is assigned to the property collector. The property collector is then assigned to the component collector.
See also CAD Reader Support UG Environment Variables UG Import Options
Altair Engineering

UG Environment Variables
Since the UG reader needs to use the UGOpen library during the run time, it requires that a valid UG installation and UG license1 be present and available to the user with the assemblies, gateway and solid_modeling modules. The UG installation must be the same bit-level and platform as the version of HyperMesh (e.g. 32-bit HM must be used with 32-bit UG). It is not possible to mix 32-bit and 64-bit versions.
The following environment variables must be set prior to starting:
WINDOWS
UGII_BASE_DIR UGII_ROOT_DIR PATH This must point to the UG installation directory 2. This must point to the UG installation UGII directory 2. This must include the %UGII_BASE_DIR%\UGII\ directory.
UGS_LICENSE_SERVER This must point to the UG license server1. UGS_LICENSE_BUNDLE This must specify the UG license bundle1. Example: UG installation located at C:\Program Files\UGS\NX 6.0 UGII_BASE_DIR: C:\Program Files\UGS\NX 6.0 UGII_ROOT_DIR: %UGII_BASE_DIR%\UGII\ PATH: %UGII_BASE_DIR%\UGII\ UGS_LICENSE_SERVER: 28000@licsrv UGS_LICENSE_BUNDLE: NXPTNR100
LINUX
UGII_BASE_DIR UGII_ROOT_DIR This must point to the UG installation directory 2. This must point to the UG installation bin directory 2.
UGS_LICENSE_SERVER This must point to the UG license server1. UGS_LICENSE_BUNDLE This must specify the UG license bundle1. Example: UG installation located at /soft/usr/ugs060 UGII_BASE_DIR: /soft/usr/ugs060 UGII_ROOT_DIR: /soft/usr/ugs060/bin/ UGS_LICENSE_SERVER: 28000@licsrv UGS_LICENSE_BUNDLE: NXPTNR100

Altair Engineering
1 2
When using UG versions prior to NX6, a UG license is not required. UG is very sensitive about the environment variables. You should NOT have '/' at the end of UGII_BASE_DIR path and you MUST have '/' at the end of UGII_ROOT_DIR path.
See also UG Reader Support
Altair Engineering

VDAFS Reader Support

The following entities are supported by the VDAFS reader: POINT LINE PLANE PSET MDI CIRCLE CURVE SURF FACE
See also CAD Reader Support VDAFS Import Options

Altair Engineering
CAD Import Options

The CAD readers provide options for processing data during import. Some of these options are available from the Import tab while others options are accessed from each reader's _reader.ini file. The options that can be specified using the Import tab include the scale factor, cleanup tolerance, import of blanked components, and naming of components by layer. The Scale factor option allows you to define how to scale the model during import. Some CAD formats store their model data using a set of units that may be different from what you want to use. This value can be used to define the scaling for all entities that are imported. For more information about the Cleanup tol option, refer to the CAD Cleanup Tolerance section. The Import hidden (blanked/no show) entities option specifies whether relevant formats should import entities that are hidden, blanked or no show. See each format's available import options for supported formats.
Default versions of the _reader.ini files are included in the directory [Altair Home]/io/ afc_translators/bin/[platform]. When a CAD reader is activated, each reader first checks the current working directory for the appropriate _reader.ini file. If the file is not found, the translator uses the default _reader.ini file in the above directory. In this way the _reader.ini file can have "global" or "local" user scope. For instance, "local" user changes for a current job can be made by copying and modifying the _reader.ini file in the local current working directory. Options can take on only one value at a time. Options can also be commented out (ignored) by placing a # in front of an option, in which case the default value for that option will be used. The available _reader.ini options are explained in detail within the Import Options sections for each reader. Many CAD translators also import other relevant information as metadata attached to specific entities (assemblies, components, points, lines, surfaces, solids). Some metadata is generated by default while other metadata is generated by enabling/disabling certain options in the _reader.ini files. Metadata is stored in the database and can be used for review or to perform process automation. For example, you can obtain the tag (name) of a surface from the CAD file and apply certain mesh criteria to that surface inside HyperMesh. Refer to the Import Options topics for each format and the CAD Metadata Naming topic for specific details about metadata.
See also ACIS Import Options CATIA Import Options DXF Import Options IGES Import Options JT Import Options
Altair Engineering

Parasolid Import Options PDGS Import Options Pro E Import Options SolidWorks Import Options STEP Import Options Tribon Import Options UG Import Options VDAFS Import Options Import tab CAD Import Message Files CAD Import Difficulties CAD Metadata Naming CAD Reader Support

Altair Engineering
ACIS Import Options

The ACIS reader uses the ct_reader.ini file with the following available options:
@ColorsAsMetadata Value on Description Read color attributes of geometric entities as metadata. COLOR_RGB off Do not read color attributes (default).
@DensityAsMetadata Value on Description Read density value as metadata (default). DENSITY off Do not read density value.
@ImportForVisualizationOnly Value on Description Import the model for visualization purposes only. This will skip many of the import steps (cleanup, stitching, solid creation, etc...) to provide a fast import. The resulting model may not be suitable for other uses. Import the model in the normal fashion (default).
off
@ImportFreeCurves Value on off Description Import free curves (wireframe entities) into the model (default). Do not import free curves.
Altair Engineering

@ImportFreePoints Value on off Description Import free points into the model (default). Do not import free points.
@MetadataPrefix Value string Description The string is prefixed to all metadata names. No prefix is used by default. See CAD Metadata Naming for more details.
@SkipCreationOfSolid Value on off Description Surfaces are read but solid entities are not created. Solid entities are created (default).
@StitchingAcrossBodies Value on off Description Surfaces belonging to different components are stitched. Surfaces belonging to different components are not stitched (default).
See also ACIS Metadata Support ACIS Reader Support CAD Import Options

Altair Engineering
ACIS Metadata Support

The ACIS reader generates the following metadata:
COLOR_RGB Type string Entities points lines surfs solids Description Three RGB values, ranging from 0 to 255, indicating the color of the entity in the CAD model. Generated when @ColorsAsMetadata = on
DENSITY Type double Entities solids Description The value of the density of a solid. Generated when @DensityAsMetadata = on
MODELUNIT Type integer Entities comps Description The model units specified in the CAD file. Values include: 1 = inches 2 = millimeters 4 = feet 5 = miles 6 = meters 7 = kilometers 8 = mils 9 = microns 10 = centimeters 11 = microinches 12 = decimeters 13 = yards This is always generated.
Altair Engineering

See also ACIS Import Options ACIS Reader Support CAD Import Options CAD Metadata Naming hm_metadata

Altair Engineering
CATIA Import Options

The CATIA v4 and CATIA v5 readers use the ct_reader.ini file with the following available options:
@FullNameAsMetadata Value on Description The full CAD name, as retrieved from the CAD part, is generated as metadata. This consists of assembly name/part name/feature name/entity name. FULL_IDENTIFIER off Do not generate full name metadata (default).
@ImportBlanked Value on Description Import of invisible (blanked/NO SHOW) components is enabled. This option, when used, takes priority over any other similar options/settings.
Altair Engineering

off
Import of invisible (blanked/NO SHOW) components is disabled (default). This option, when used, takes priority over any other similar options/settings.
off
@SkipCreationOfSolid

Altair Engineering
Value on off
Description Surfaces are read but solid entities are not created. Solid entities are created (default).
@TagsAsMetadata Value on Description Read tags of supported entities as metadata (default). TAG off Do not read tags.
See also CATIA Metadata Support CATIA Reader Support CAD Import Options
Altair Engineering

CATIA Metadata Support

The CATIA reader generates the following metadata:
COMMENT_BLOCK Type string Entities assems Description The command block text for a CATIA v4 file. This is only attached to the root assembly.
COORDINATE_SYSTEM_<name> Type string Entities assems Description The <name> field is the name of the local coordinate system and the value is the local coordinate system information.
FULL_IDENTIFIER Type Entities Description

Altair Engineering
string
points lines surfs solids comps assems
A string indicating the name in the following format: "part_name/name" Generated when @FullNameAsMetadata = on
TAG Type string Entities points lines edges surfs solids Description The tag (name) of the entity as read from the CAD model, if one exists. Generated when @TagsAsMetadata = on
Altair Engineering

See also CATIA Import Options CATIA Reader Support CAD Import Options hm_metadata

Altair Engineering
DXF Import Options

The DXF reader does not have any available customizations.
See also DXF Metadata Support DXF Reader Support CAD Import Options
Altair Engineering

DXF Metadata Support

The DXF reader does not generate any metadata.
See also DXF Import Options DXF Reader Support CAD Import Options hm_metadata

Altair Engineering
IGES Import Options

The IGES reader uses the iges_reader.ini file. This file has two sections. The first section contains the instructions for reading each type of IGES entity. It is recommended that you do not change this section. The second section controls the options for the translator. The IGES reader has the following available options:
@CheckFacet Value on Description Based on the success of the normal faceting operation, more cleanup attempts may be required. One option is to mesh it in advance to check the faceting. This may slow down the import due to the possible use of meshing operations but should result in cleaner surfaces (default). The faceting is not checked and only the normal cleanup is applied.
off
off
@ImportFreeCurves Value Description
Altair Engineering

on off
Import free curves (wireframe entities) into the model (default). Do not import free curves.
@ImportLayers Value Layers to skip Description Enables the specification of layer numbers to import, in order to skip unwanted layers. Layer groupings can be specified with a hyphen between the beginning and ending values of the desired group, and groups are separated by commas. Example: @ImportLayers = "1,2-5,100-200"
@ImportType Value ASSEMBLY Description An assembly tree corresponding to the one contained in the file is generated (default). The components are created depending on the layer (=level) structure of the file.
LAYERS_ONLY
LAYERS_AND_GROUPS The components are created corresponding to layers and groups contained in the file.
@MetadataPrefix Value string Description The string is prefixed to all metadata names. No prefix is used by default.

Altair Engineering
See CAD Metadata Naming for more details.
@ReadAsIndependent Value INDEPENDENT Description
Enables the import of three types of independent entities. Use a PHYSICALLY_DEPENDENT semicolon to separate multiple values. When more than one value is used, both independent and logically dependent entities are treated as LOGICALLY_DEPENDENT independent. Generally, this option should only be used for a particular vendor that marks some entities as dependent when they are imported. The reader will import the entities according to the value specified in the file. The default is INDEPENDENT.
@SkipEntities Value Description
Entity types Specific entity types, or even subtypes (i.e. entity types with specific form and subtypes to numbers) that should be skipped during import. The list of types uses skip semicolons as separators. Example: @SkipEntities = "ENTTYPE1;ENTTYPE2.FORM2"
@Transform402form16 Value on Description Entities referenced by an entity type #402 form #16 are tramsformed from 2D local space into 3D absolute space. Early IGES files from SolidWorks require such an operation.
Altair Engineering

off
(default)
@TraverseGroups Value on off Description The reader attempts to traverse group entities (default). References to entities within a group are ignored.
@TrimRevolvedWithModelSpaceCurves Value on Description The reader attempts to compute the boundary definition by projecting 3D trimming curves (if such curves are available) onto the surface only for revolution surface entities (type #120). Parameter space trimming loops are used whenever possible. Given an IGES file containing correct data, this option is faster and more robust than reading object space loops (default).
off
@TrimWithModelSpaceCurves Value on Description The reader attempts to compute the boundary definition by projecting 3D trimming curves (if such curves are available) onto the surface. This is useful if the parameter space trimming loops in the file contain incorrect geometry data. Parameter space trimming loops are used whenever possible. Given an IGES file containing correct data, this option is faster and more robust than reading object space loops (default).
off
@TrimWithPreferredRepresentation Value on Description The reader attempts to create the boundary definition using 2D or 3D curves, based on the preferred representation provided by entity type #142. This

Altair Engineering
option can be overridden by either @TrimRevolvedWithModelSpaceCurves = on or @TrimWithModelSpaceCurves = on. off (default)
@UseAnsys128Format Value on off Description The reader attempts to read Ansys NURBS surface format. (default)
@vendors Value List of vendor names Description This vendor information is used to search the global section of the file to determine if it is from a particular vendor. Each vendor name is separated by semicolons and all spaces in the vendor name must be replaced by an underscore. Example: @vendors = "vendor1;vendor2;vendor3" After a vendor has been added to the list, options for that particular vendor can be specified. If a file is recognized as coming from a particular vendor, settings for that vendor take priority over "general" settings. Example: @<vendor>.<option> = "<value>"
See also IGES Metadata Support IGES Reader Support CAD Import Options
Altair Engineering

IGES Metadata Support

The IGES reader generates the following metadata:
AUTHOR Type string Entities comps Description The author block as read from the 'G' section of the file. This is generated only when the block is found in the file.
AUTHORS_ORGANIZATION Type string Entities comps Description The author's organization block from the 'S' section of the file. This is generated only when the block is found in the file.
COLOR_RGB Type string Entities lines surfs Description Three RGB values, ranging from 0 to 255, indicating the color of the entity in the CAD model. Generated when @ColorsAsMetadata = on
COMMENT_BLOCK Type string Entities comps Description The comment block from the 'S' section of the file. This is generated only when the block is found in the file.
DRAFTING_STANDARD Type integer Entities comps Description The drafting standard block from the 'G' section of the file. This is generated only when the block is found in the file.

Altair Engineering
IGES_VERSION Type integer Entities comps Description The IGES version block from the 'G' section of the file. This is generated only when the block is found in the file.
FILE_NAME Type string Entities comps Description The file name block from the 'G' section of the file. This is generated only when the block is found in the file.
IMPORT_DATE Type string Entities comps Description The import date block from the 'G' section of the file. This is generated only when the block is found in the file.
MODELUNIT Type integer Entities comps Description The model units specified in the CAD file. Values include: 1 = inches 2 = millimeters 4 = feet 5 = miles 6 = meters 7 = kilometers 8 = mils 9 = microns 10 = centimeters 11 = microinches 12 = decimeters 13 = yards
Altair Engineering

This is always generated.
MODIFICATION_DATE Type string Entities comps Description The modification date block from the 'G' section of the file. This is generated only when the block is found in the file.
PREPROCESSOR_VERSION Type string Entities comps Description The preprocessor version block from the 'G' section of the file. This is generated only when the block is found in the file.
PRODUCT_IDENTIFICATION Type string Entities comps Description The product identification block from the 'G' section of the file. This is generated only when the block is found in the file.
RECEIVING_PRODUCT_ID Type string Entities comps Description The receiving product ID block from the 'G' section of the file. This is generated only when the block is found in the file.
SYSTEM_ID Type string Entities comps Description The system ID block from the 'G' section of the file. This is generated only when the block is found in the file.
TAG

Altair Engineering
Type string
Entities points lines surfs
Description The tag (name) of the entity as read from the CAD model, if one exists. Generated when @TagsAsMetadata = on
UNITS Type string Entities comps Description The units block from the 'G' section of the file. This is generated only when the block is found in the file.
See also IGES Import Options IGES Reader Support CAD Import Options hm_metadata
Altair Engineering

JT Import Options
The JT reader uses the jt_reader.ini file with the following available options:
@AttributesAsMetadata Value on Description All non-blank name/value attributes are imported as metadata attached to the relevant entities (default). No name/value pair attributes are imported.
off
@BrepAndTessLoadOption Value 0 Description Import B-rep or tessellation, with B-rep given preference. If any B-rep is present, no tessellation is imported (default). Import both the B-rep and the tessellation. Import only the B-rep. If no B-rep is present, nothing is imported. Import only the tessellation. If no tessellation is present, nothing is imported.
1 2 3
@ImportForVisualizationOnly Value on Description Import the model for visualization purposes only. This will skip many of the import steps (cleanup, stitching, solid creation, etc...) to provide a fast

Altair Engineering
import. The resulting model may not be suitable for other uses. off Import the model in the normal fashion (default).
See also JT Metadata Support
Altair Engineering

JT Reader Support CAD Import Options

Altair Engineering
JT Metadata Support
The JT reader generates the following metadata:
COLOR_RGB Type string Entities lines surfs comps Description Three RGB values, ranging from 0 to 255, indicating the color of the entity in the CAD model. Generated when @ColorsAsMetadata = on
<name> Type integer double string Entities comps assems Description The <name> field is the JT attribute name and the integer/double/string is the value of the JT attribute. Generated when @AttributesAsMetadata = on
Altair Engineering

See also JT Import Options JT Reader Support CAD Import Options hm_metadata

Altair Engineering
Parasolid Import Options

The Parasolid reader uses the ct_reader.ini file with the following available options:
off
Altair Engineering

See also Parasolid Metadata Support Parasolid Reader Support CAD Import Options

Altair Engineering
Parasolid Metadata Support

The Parasolid reader generates the following metadata:
Altair Engineering

See also Parasolid Import Options Parasolid Reader Support CAD Import Options hm_metadata

Altair Engineering
PDGS Import Options

The PDGS reader does not have any available customizations.
See also PDGS Metadata Support PDGS Reader Support CAD Import Options
Altair Engineering

PDGS Metadata Support

The PDGS reader does not generate any metadata.
See also PDGS Import Options PDGS Reader Support CAD Import Options hm_metadata

Altair Engineering
Pro E Import Options

The Pro E reader uses the ct_reader.ini file with the following available options:
Altair Engineering

off
off

Altair Engineering
Value on off
See also Pro E Metadata Support Pro E Reader Support CAD Import Options
Altair Engineering

Pro E Metadata Support

The Pro E reader generates the following metadata:
FULL_IDENTIFIER Type string Entities points lines surfs solids comps assems Description A string indicating the name in the following format: "part_name/name" Generated when @FullNameAsMetadata = on
MODELUNIT Type integer Entities comps Description The model units specified in the CAD file. Values include: 1 = inches 2 = millimeters

Altair Engineering
4 = feet 5 = miles 6 = meters 7 = kilometers 8 = mils 9 = microns 10 = centimeters 11 = microinches 12 = decimeters 13 = yards This is always generated.
See also Pro/E Import Options Pro/E Reader Support CAD Import Options hm_metadata
Altair Engineering

SolidWorks Import Options

The SolidWorks reader uses the ct_reader.ini file with the following available options:
off

Altair Engineering
See also SolidWorks Metadata Support SolidWorks Reader Support CAD Import Options
Altair Engineering

SolidWorks Metadata Support

The SolidWorks reader generates the following metadata:

Altair Engineering
See also SolidWorks Import Options SolidWorks Reader Support CAD Import Options hm_metadata
Altair Engineering

STEP Import Options

The STEP reader uses the ct_reader.ini file with the following available options:

Altair Engineering
off
off
Altair Engineering

Value on off
See also STEP Metadata Support STEP Reader Support CAD Import Options

Altair Engineering
STEP Metadata Support

The STEP reader generates the following metadata:
FULL_IDENTIFIER Type string Entities points lines surfs solids comps assems Description A string indicating the name in the following format: "part_name/name" Generated when @FullNameAsMetadata = on
MODELUNIT Type integer Entities comps Description The model units specified in the CAD file. Values include: 1 = inches 2 = millimeters
Altair Engineering

4 = feet 5 = miles 6 = meters 7 = kilometers 8 = mils 9 = microns 10 = centimeters 11 = microinches 12 = decimeters 13 = yards This is always generated.
TAG Type string Entities lines surfs solids Description The tag (name) of the entity as read from the CAD model, if one exists. Generated when @TagsAsMetadata = on
See also STEP Import Options STEP Reader Support CAD Import Options hm_metadata

Altair Engineering
Tribon Import Options

The Tribon reader uses the tribon_reader.ini file with the following available options:
@ImportHoles Value on off Description Create holes (default). Do not create create holes.
@ImportCutoutProfiles Value on off Description Import cutout profiles. Do not import cutout profiles (default).
@ImportFaceplatesAsSurfaces Value on Description Import faceplates as surfaces if the surface description is present in the file, otherwise import as curves (default). Import faceplates as curves.
off
@ImportNotchProfiles Value on off Description Import notch profiles. Do not import notch profiles (default).
@ImportPanelProfiles
Altair Engineering

Value on off
Description Create curves along the panel profiles. Do not create curves along the panel profiles (default).
@ImportPillarsAsSurfaces Value on Description Import pillars as surfaces if the surface description is present in the file, otherwise import as curves (default). Import pillars as curves.
off
@ImportStiffenersAsSurfaces Value on Description Import stiffeners as surfaces if the surface description is present in the file, otherwise import as curves (default). Import stiffeners as curves.
off
@ImportUnboundedCurvedPlates Value on off Description Import curved plates lacking boundary descriptions (default). Do not import curved plates lacking boundary descriptions.
@PreferDetailed

Altair Engineering
Value on
Description When multiple representations of a Tribon object are available, import the most complex one (default). When multiple representations of a Tribon object are available, import the least complex one.
off
@TribonCurvedPlateColor Value string Description An RGB description of the color to use for curved plates, with values ranging from 0.0 to 1.0 (e.g. "0.1,0.5,0.4"). If not specified, default color management will be utilized.
@TribonCurvedSimpleContourColor Value string Description An RGB description of the color to use for curved simple contours, with values ranging from 0.0 to 1.0 (e.g. "0.1,0.5,0.4"). If not specified, default color management will be utilized.
@TribonCurvedStiffenerColor Value string Description An RGB description of the color to use for curved stiffeners, with values ranging from 0.0 to 1.0 (e.g. "0.1,0.5,0.4"). If not specified, default color management will be utilized.
@TribonFlangeColor Value string Description An RGB description of the color to use for flanges, with values ranging from 0.0 to 1.0 (e.g. "0.1,0.5,0.4"). If not specified, default color management will be utilized.
Altair Engineering

@TribonPlaneBracketColor Value string Description An RGB description of the color to use for plane brackets, with values ranging from 0.0 to 1.0 (e.g. "0.1,0.5,0.4"). If not specified, default color management will be utilized.
@TribonPlaneDetailedContoursColor Value string Description An RGB description of the color to use for plane detailed contours, with values ranging from 0.0 to 1.0 (e.g. "0.1,0.5,0.4"). If not specified, default color management will be utilized.
@TribonPlaneFaceplateColor Value string Description An RGB description of the color to use for plane faceplates, with values ranging from 0.0 to 1.0 (e.g. "0.1,0.5,0.4"). If not specified, default color management will be utilized.
@TribonPlanePillarColor Value string Description An RGB description of the color to use for plane pillars, with values ranging from 0.0 to 1.0 (e.g. "0.1,0.5,0.4"). If not specified, default color management will be utilized.
@TribonPlanePlateColor Value string Description An RGB description of the color to use for plane plates, with values ranging from 0.0 to 1.0 (e.g. "0.1,0.5,0.4"). If not specified, default color management will be utilized.

Altair Engineering
@TribonPlaneSimpleContourColor Value string Description An RGB description of the color to use for plane simple contours, with values ranging from 0.0 to 1.0 (e.g. "0.1,0.5,0.4"). If not specified, default color management will be utilized.
@TribonPlaneStiffenerColor Value string Description An RGB description of the color to use for plane stiffeners, with values ranging from 0.0 to 1.0 (e.g. "0.1,0.5,0.4"). If not specified, default color management will be utilized.
@TribonSubFaceplateColor Value string Description An RGB description of the color to use for sub-faceplates, with values ranging from 0.0 to 1.0 (e.g. "0.1,0.5,0.4"). If not specified, default color management will be utilized.
@TribonSubFlangeColor Value string Description An RGB description of the color to use for sub-flanges, with values ranging from 0.0 to 1.0 (e.g. "0.1,0.5,0.4"). If not specified, default color management will be utilized.
@TribonSubStiffenerColor Value string Description An RGB description of the color to use for sub-stiffeners, with values ranging from 0.0 to 1.0 (e.g. "0.1,0.5,0.4"). If not specified, default color management will be utilized.
Altair Engineering

See also Tribon Metadata Support Tribon Reader Support CAD Import Options

Altair Engineering
Tribon Metadata Support

The Tribon reader generates the following metadata:
BENDING_RADIUS Type string Entities assems Description The value of the BendingRadius attribute for a plane flange group.
COLOR_RGB Type string Entities comps Description Three RGB values, ranging from 0 to 255, indicating the color for the object. Generated when the corresponding @Tribon<object>Color option is used.
COMP_ID Type string Entities assems Description The value of the CompId attribute for a plate or bracket.
DATA_TYPE Type string Entities assems Description The value of the DataType attribute for a panel.
EXTENT_MAX Type string Entities assems Description The value of the maximum extent of a block or panel, as retrieved from the Max attribute of the object.
EXTENT_MIN
Altair Engineering

Type string
Entities assems
Description The value of the minimum extent of a block or panel, as retrieved from the Min attribute of the object.
FORCE_UNITS Type string Entities assems Description The value of the ForceUnits attribute for a ship units object.
FUNCTIONAL_PROPERTY Type string Entities assems Description The value of the FunctionalProperty attribute for a panel or a group of subobjects of a panel.
HEIGHT Type string Entities assems Description The value of the Height attribute for a plane flange group.
LENGTH_UNITS Type string Entities assems Description The value of the LengthUnits attribute for a ship units object.
MATERIAL_DIRECTION Type string Entities faces Description The value of the MaterialDirection attribute for a flange, curved panel or knuckled panel.
MATERIAL_SIDE

Altair Engineering
Type string
Entities assems
Description The value of the material side data for a plate group or bracket group.
OFFSET Type string Entities assems Description The value of the offset data for a plate group.
RENDERING_TYPE Type string Entities assems Description The value of the Type attribute for a ship rendering object.
THICKNESS Type string Entities assems Description The value of the Thickness attribute for a plane flange group.
VERSION Type string Entities assems Description The value of the Version attribute for a ship.
WEIGHT_UNITS Type string Entities assems Description The value of the WeightUnits attribute for a ship units object.
See also Tribon Import Options Tribon Reader Support
Altair Engineering

CAD Import Options hm_metadata

Altair Engineering
UG Import Options
The UG reader uses the ug_reader.ini file. The UG reader also includes a browser to control the import of assemblies, the sorting of entities by component, and various other import details. For more information, refer to the UG Part Browser section. The UG reader and part browser have the following available options:
@AttributesAsMetadata Value on Description All non-blank name/value attributes are imported as metadata attached to the relevant entities (default). No name/value pair attributes are imported.
off
@CoordinateSystem Value global Description The Coordinate system option is set to Global when the Part Browser comes up (default). The Coordinate system option is set to Local when the Part Browser comes up.
local
@CreateWeldsInHypermesh Value on Description The Create welds in HyperMesh option is checked when the Part Browser comes up. The Create welds in HyperMesh option is unchecked when the Part Browser comes up (default).
off
@Display Value categories Description The Categories option is enabled when the Part Browser comes up (default).
Altair Engineering

layerfiltering
The Layer filtering option is enabled when the Part Browser comes up.
@ExportToMasterWeldFile Value on Description The Export to master weld file <filename> option is checked when the Part Browser comes up. The Export to master weld file <filename> option is unchecked when the Part Browser comes up (default).
off
off
@IncludeInvisibleGeometry Value on Description The Include invisible geometry option is checked when the Part Browser comes up. The Include invisible geometry option is unchecked when the Part Browser comes up (default).
off
@IncludeWireFrame Value on Description The Include wireframe geometry option is checked when the Part Browser comes up (default). The Include wireframe geometry option is unchecked when the Part Browser comes up.
off

Altair Engineering
@LoadColorAttributes Value on Description Read color attributes of geometric entities as metadata. COLOR_RGB off Do not read color attributes (default).
@LoadDensityAttributes Value on Description Read density and transformation matrix as metadata (default). DENSITY TRANSFORMATION_MATRIX off Do not read density and transformation matrix.
@Merge Value on Description The Merge assemblies option is checked when the Part Browser comes up. If the option is then accepted by the user, the .ALTAIR.HW.UG.MERGE metadata is generated. The Merge assemblies option is unchecked when the Part Browser comes up (default).
off
@Midsurface Value on Description When @Display= layerfiltering, the Midsurface checkbox is checked when the Part Browser comes up. When @Display= layerfiltering, the Midsurface checkbox is unchecked when the Part Browser comes up (default).
off
Altair Engineering

@ShowAllCategories Value on Description When @Display= categories, all categories will be retrieved and displayed when the Part Browser comes up. When @Display= categories, only categories in the top assembly will be retrieved and displayed when the Part Browser comes up (default).
off
@Solid Value on Description When @Display= layerfiltering, the Solid checkbox is checked when the Part Browser comes up (default). When @Display= layerfiltering, the Solid checkbox is unchecked when the Part Browser comes up.
off
@StitchDifferentSheets Value on Description Stitching across different sheet bodies belonging to the same UG part/ instance is enabled (default). Stitching across different UG sheet bodies is disabled.
off
@TagsAsMetadata

Altair Engineering
Value on
Description Read tags of supported entities as metadata (default). TAG
off
Do not read tags.
See also UG Metadata Support UG Part Browser UG Reader Support CAD Import Options
Altair Engineering

UG Metadata Support
The UG reader generates the following metadata:
COLOR_RGB Type string Entities points lines surfs solids Description Three RGB values, ranging from 0 to 255, indicating the color of the entity in the CAD model. Generated when @LoadColorAttributes = on
DENSITY Type double Entities solids Description The density value, as specified in the CAD model, if one exists. Generated when @LoadMassAttributes = on
MERGE Type integer Entities comps Description Set to 1 if the Merge assemblies option is chosen in the Part Browser. Generated when @Merge = on
MODELUNIT Type integer Entities comps Description The model units specified in the CAD file. Values include: 1 = inches 2 = millimeters 4 = feet 5 = miles 6 = meters

Altair Engineering
7 = kilometers 8 = mils 9 = microns 10 = centimeters 11 = microinches 12 = decimeters 13 = yards This is always generated.
TRANSFORMATION_MATRIX Type string Entities solids Description A 4x4 transformation matrix from the global reference system to the part reference system. Generated when @LoadMassAttributes = on
UNIQUE_ID Type string Entities assems Description The name of the UG assembly. This is always generated.
<name> Type Entities Description
Altair Engineering

integer double string
points lines surfs solids comps assems
The <name> field is the UG attribute name and the integer/double/string is the value of the UG attribute. Generated when @AttributesAsMetadata = on
See also UG Import Options UG Reader Support CAD Import Options hm_metadata

Altair Engineering
UG Part Browser
The UG Part Browser allows for advanced selection and filtering options for importing UG parts and assemblies. The browser is launched from the Import tab when importing a UG file.
On the left of the browser is the model tree. The parts listed in the model tree are shown either using the File name or Instance name options. A part can be selected for import by activating its check box. If the root is selected, all parts are considered selected. Root assembly/part is selected by default. The UG Part Browser searches all part files for weld information as well as mid-surface definitions. Parts in the assembly that have welds assembled to them are marked with a "W", . Parts with mid-surface definitions are marked with an "M", .
On the right of the browser are the available import options. These options include: Display by: - Determines whether to import the selected Categories for the parts specified in the model tree or whether to use Layer filtering to import only selected layers for the parts specified in the model tree.
Altair Engineering

When the Categories option is enabled, some categories may be available in multiple parts/ assemblies and some may be available in only one. You can choose multiple categories to import. All the categories for the selected parts are imported. When the Layer filtering option is enabled, you can specify specific layers to Enable or Disable for import. Commas and dashes can be used for designating more than one layer or a range of layers. For example, 1,4-7 designates layers 1, 4, 5, 6 and 7. An asterisk (*) matches everything. Only one of these two options may be specified. If any layers are specified for Disable, all other layers containing entities are imported. The default is to enable all layers. When the Layer filtering option is enabled, you can additionally choose to import the Midsurface and/or the faces of Solid entities.
The Include wireframe geometry option determines whether to import free curves and points. The default is to import these entities. The Include invisible geometry option determines whether to import geometry contained in invisible layers. The default is to not import these entities. The Assign components by name option allows for customizing the organization and names of components (UG parts). The naming options are specified using the Format button as described below:
<Part Name>
Uses the string attribute DB_PART_NAME from the part. If that attribute does not exist, the part file name is used. Uses the string attribute DB_PART_NUMBER or DB_PART_NO from the part. If that attribute does not exist, the part filename is used. Uses the string attribute DB_PART_REV from the part. Creates and names components based off of the layers of the geometry being imported.
<Part Number>
<RID-PDI> <Layer>
<Instance Name> Uses the name of the part's instance in an assembly. If the part is the root of an assembly, the part filename is used.

Altair Engineering
<Material Name> If a material is specified for the geometry being imported, the name of the material is used. Otherwise, the name of the component is unaltered. <Thickness> If the geometry being imported is a midsurface with thickness information, the thickness value is used. Otherwise, the name of the component is unaltered. The internal numerical ID of each geometric body. This value is unique for each geometric body imported. The internal numerical tag of the part instance. This value is unique for each part instance imported.
<UG Body ID>
<UG Tag>
The Save settings as default checkbox saves the settings into a customized ug.ini file in the current working directory for future use. Additional options for coordinate system, weld creation, merging assemblies, and importing of attributes can be accessed by clicking the Options button at the bottom of the browser. These options include:
The Co-ordinate system option determines whether to import an individual part from an assembly in the global coordinate system or its local coordinate system. If the whole assembly file is selected, it can only be imported in the global coordinate system. The Create welds in HyperMesh option provides for the use of two methods to create welds. They are placed in a component named ^weld. If the part file has mid-surface definition and the Midsurface option is selected while reading the part, the welds are created between two mid-surfaces. If there is no mid-surface definition or the Midsurface option is not selected while importing the part, the welds are created as they were initially created in the UG part file.
The Export to master weld file option writes a master weld file from the weld data that can later be used to create the welds.
Altair Engineering

If some parts of an assembly have been previously loaded and you want to add additional parts from the same assembly, you can choose to merge the parts with the existing assembly using the Merge assemblies option. The Model and component attributes option allows the user to choose the attributes in the UG part file that are to be imported. Currently, the UG readers have the ability to import any userdefined attributes attached to a UG part, and attach that information as metadata to the component corresponding to the UG part. The naming options are specified using the Format button.
The values setup and used to populate the UG Part Browser are stored in a file named ughm16.txt, located in the current working directory.
See also *feinputwithdata2 - UG UG Import Options

Altair Engineering
UG Load Options
The UG reader provides additional customization options for loading of UG models. The ug_load_options.def file can be used for this purpose. The behavior of this file is as follows. This file can be setup and written out of UG using the File->Options->Assembly Load Options dialog. The UG reader passes the options in this file to UGOpen during import, and UG utilizes the options accordingly.
A default version of the ug_load_options.def file is located in the directory [Altair Home]/io/ afc_translators/bin/[platform]. When the UG reader is activated, it first checks the current working directory for the ug_load_options.def file. If the file is not found, the translator uses the default ug_load_options.def file in the above directory. In this way the ug_load_options.def file can have "global" or "local" user scope. For instance, "local" user changes for a current job can be made by copying and modifying the ug_load_options.def file in the local current working directory.
Altair Engineering

VDAFS Import Options

The VDAFS reader uses the vdafs_reader.ini file with the following available options:
off
@ParameterTolerance

Altair Engineering
Value Any positive real number.
Description The reader considers this tolerance as the parametric tolerance used to process the CAD data. The default value is 1.00E-06.
@Planes Value on off preferred Description The reader will treat each surface as found in the CAD file (planes/NURBS). The reader will convert planes into NURBS surfaces. The reader will convert NURBS surfaces to planes if they are within the object space tolerance of being planar (default).
@StraightPolynomials Value on Description The reader will treat each polynomial segment as a straight line segment. This is necessary for reading some VDAFS files, COMPUTERVISION CADDS 4X in particular. The reader will treat each polynomial as found in the CAD file (default).
off
@Tolerance Value Any positive Description The reader considers this tolerance as the object space tolerance used to
Altair Engineering

real number.
process the CAD data. The default value is 0.01.
See also VDAFS Metadata Support VDAFS Reader Support CAD Import Options

Altair Engineering
VDAFS Metadata Support

The VDAFS reader generates the following metadata:
TAG Type string Entities points lines surfs Description The tag (name) of the entity as read from the CAD model, if one exists. Generated when @TagsAsMetadata = on
See also VDAFS Import Options VDAFS Reader Support CAD Import Options hm_metadata
Altair Engineering

CAD Import Message Files

Each reader reads the CAD file and sends the geometry information to HyperMesh. When a CAD file is read, a .msg file is created (or appended to) in the current working directory. For example, the file iges_reader.msg is created for the IGES reader. Three types of messages appear in the .msg file: info warning error Messages that include information about the file being read. Messages that indicate that data was modified Messages that indicate when a geometric entity could not be created.
These files can be useful for debugging errors found during import. Also refer to the CAD Import Difficulties section for other suggestions.
See also CAD Import Difficulties CAD Import Options

Altair Engineering
CAD Import Difficulties

If a line does not import correctly and has gaps, the gaps are filled with straight lines. If necessary, pieces of composite curves are reversed to make the entire line continuous. Lines shorter than the object space tolerance are rejected. A line cannot intersect itself. This condition is not detected, and results may be incorrect if this kind of line is imported. A closed loop can have coincident starting and ending points. Untrimmed surfaces are corrected if they do not import correctly. Internal gaps (C0-discontinuity) are removed by blending each edge of the gap together. Breaks at C1-discontinuities are controlled internally and may accept lower-level continuities depending on the reader's internal tolerance. While surfaces with one or two dimensions smaller than the object space tolerance are not prohibited, it is likely that they may be rejected. Each point in the interior of the surfaces parameter space should map to a distinct point in object space. This condition is not detected and incorrect results may occur if such a surface is imported. A surface may be closed in one or both directions. Trimmed surfaces are a combination of untrimmed surfaces and one or more lines. The above restrictions apply to trimmed surfaces. If a surface cannot be trimmed, as much geometry information as possible is supplied. In most cases, both the underlying surface and its lines are created. It is then possible to use the surface edit panel to trim the surface manually. It is also useful to refer to the .msg files generated by each CAD reader to find warnings/errors that may help in resolving import difficulties.
See also CAD Cleanup Tolerance CAD Import Message Files CAD Import Options
Altair Engineering

CAD Metadata Naming

The metadata names generated by the CAD readers are composed of a general prefix followed by a metadata specific name. The prefix is specified using the @MetadataPrefix option in each _reader. ini file. The @MetadataPrefix option works as follows: The user specified string is appended as a prefix to the metadata name generated by that reader. The prefix is used explicitly with the metadata name. No . (period) is automatically added if it is not specified by the option. For example: @MetadataPrefix = ".ALTAIR.HW" .ALTAIR.HW<metadata name> @MetadataPrefix = ".ALTAIR.HW." .ALTAIR.HW.<metadata name> If the option is commented out, or the value is set to null "", no prefix is prepended and only the names of the metadata are used. For example: @MetadataPrefix = "" <metadata name> There are some pre-defined strings that have specific meaning. These pre-defined strings are automatically substituted with specific data where applicable. These strings are as follows: <FORMAT> - the format of the CAD file (CATIA, STEP, UG, etc...) <VERSION> - the version of the CAD file. For CATIA, this is V4 or V5. No other format currently supports this option. In the case where there is no <VERSION> possible, an empty string is substituted. All other strings are used verbatim. For example: @MetadataPrefix = "<MYSTRING>" <MYSTRING><metadata name> By default, the prefix is empty string for all readers. To maintain consistency with metadata names used by previous versions, a value of ".ALTAIR.HW.<FORMAT>." is appropriate.
Some additional examples: @MetadataPrefix = ".ALTAIR.HW.<FORMAT>." .ALTAIR.HW.CATIA.<metadata name>
@MetadataPrefix = "/ALTAIR/HW/<FORMAT>/" /ALTAIR/HW/CATIA/<metadata name>

Altair Engineering
@MetadataPrefix = "<FORMAT><VERSION>." CATIAV5.<metadata name> @MetadataPrefix = "<FORMAT>.<VERSION>." CATIA.V5.<metadata name>
See also CAD Import Options hm_metadata
Altair Engineering

CAD Export
This section describes the support provided by the CAD writers, as well as the options available for exporting CAD geometry data from HyperMesh. These writers are dynamically loaded upon demand, and include support for the following CAD formats:
IGES
See also CAD Writer Support CAD Export Options CAD Import

Altair Engineering
CAD Writer Support

Latest CAD Version CAD Format Supported v6.0 IGES JAMA-IS
1
Platforms1
x86
Y
Windows x86_64
Y
Linux x86
Y
x86_64
Y
Refer to the official HyperWorks platform support list for full details.
See also IGES Writer Support CAD Export Options
Altair Engineering

IGES Writer Support

The following entities are supported by the IGES writer: Composite curve (102) Plane (108) Line (110) Point (116) Rational B-spline curve (126) Rational B-spline surface (128) Curve on a parametric surface (142) Trimmed (parametric) surface (144) Form 7 group without back pointers (402) Fixed points (those associated with lines or surfaces) are not supported by the IGES standard and are not exported. Free points, however, are supported. In order to export fixed points, it is necessary to convert them to free points. Then, after import, those free points must be projected onto the appropriate lines or surfaces in order to generate fixed points with the proper association.
See also CAD Writer Support

Altair Engineering
CAD Export Options

The CAD writers provide options for processing data during export. All of these options are currently available from the Export tab. There are no corresponding _writer.ini files. The available options are explained in detail within the Export Options sections for each writer. There are also no message files generated for the export of CAD data.
See also IGES Export Options CAD Writer Support Export tab
Altair Engineering

IGES Export Options

When IGES data is exported, it writes lines in a form resembling the database. Each segment on the line becomes a separate curve in IGES. If there is more than one segment in the line, the resulting curves in IGES are joined together with a composite curve entity. NURBS curves and ellipses are written as rational bspline curves (IGES's rational B-splines are general NURBS). HyperMesh writes the surface faces that comprise the surface. This allows for output type options. NURBS surfaces are output as rational B-spline surfaces in IGES, as are cones, spheres, and tori. If necessary, curves on parametric surfaces and trimmed surface entities are used to trim the NURBS surface.
The Outer loop option affects the output of surface faces. In each case, a solid surface whose trimming loop corresponds to the natural trimming loop of the surface is written as an untrimmed NURBS surface. These options control the writing of a surface with holes: Optional1 The IGES 6.0 standard allows you to default to the natural outer loop of the surface being trimmed. If you are trimming a NURBS surface with several holes and no exterior trimming, the outer loop can be left out of the IGES file, making the surface representation shorter and more accurate. Use this option if it is supported by your IGES post-processor. This is not available with the JAMA-IS standard. For those post-processors that do not allow an optional outer loop, this option forces an outer loop to be written for trimmed surfaces.
Mandatory2
Surface faces can be grouped into their corresponding surfaces by editing the Layers option. The selected option is dependent upon the post-processor for the file and the intended use of the file in the post processor: Layers Each component is sent as a different layer (level) in the IGES file. This is the most efficient format. Each component is sent as an associative instance entity (type 402, form 7).
Groups
Layers and Groups Each component is sent as a different layer (level). Each set of faces comprising one HyperMesh surface is sent as an associativity instance (group).
The most efficient form is JAMA planes and the Outer Loop Optional option; however, this choice may cause compatibility difficulties.
2
To be JAMA-IS compatible, select the JAMA planes and the Outer Loop Mandatory options.
See also IGES Writer Support

Altair Engineering
CAD Export Options
Altair Engineering

Functionality
HyperMesh has extensive capabilities to create geometry from scratch as well as edit and cleanup existing geometry (including geometry from CAD). The available functionalities are described in the following topics.
See also Creating Geometry Editing Geometry Querying Geometry

Altair Engineering
Creating Geometry
There are many different ways to create geometry in HyperMesh which include importing from external CAD models, as well as creating new geometry from scratch. The methods used to create a particular geometry depend on both the entities available for input and the level of detail required. The following methods are available for creating geometry in HyperMesh:
Nodes
xyz - Creates by specifying (x,y,z) coordinates (Nodes panel). on geometry - Creates at graphically selected locations on points, lines, surfaces and planes (Nodes panel). arc center - Creates nodes at the center of the arc that best approximates the input set of nodes, points or lines (Nodes panel). extract parametric - Creates nodes at parametric locations on lines and surfaces (Nodes panel). extract on line - Creates evenly spaced or biased nodes on a selection of lines (Nodes panel). interpolate nodes - Creates evenly spaced or biased nodes by interpolating between existing nodes in space (Nodes panel). interpolate on line - Creates evenly spaced or biased nodes by interpolating between existing nodes on a line (Nodes panel). interpolate on surface - Creates evenly spaced or biased nodes by interpolating between existing nodes on a surface (Nodes panel). intersect - Creates nodes at the intersection of geometric entities: lines/lines, lines/surfaces, lines/ solids, lines/planes, vector/lines, vector/surfaces, vector/solids and vector/plane (Nodes panel). temp nodes - Creates nodes by duplicating existing nodes or creating nodes on existing geometry or elements (Temp Nodes panel). circle center - Creates nodes at the center of the circle defined by exactly three nodes (Distance panel). duplicate - Creates nodes by duplicating existing nodes. This is available in many panels when the "duplicate" advanced entity selector is available on a nodes input collector. on screen - Creates nodes by pre-selecting existing geometry or elements and clicking on the locations to create the nodes. This is available in any panel that has a node or node list input collector (Picking nodes on geometry or elements). Misc. API commands that do not have an associated panel.
Free Points
xyz - Creates free points by specifying (x,y,z) coordinates (Points panel). arc center - Creates at the center of the arc that best approximates the input set of nodes, points or lines (Points panel). extract parametric - Creates free points at parametric locations on lines and surfaces (Points panel).
Altair Engineering

intersect - Creates free points at the intersection of geometric entities: lines/lines, lines/surfaces, lines/solids, lines/planes, vector/lines, vector/surfaces, vector/solids and vector/plane (Points panel). suppressed fixed points - Creates free points at suppressed fixed point locations (Point Edit panel). circle center - Creates free points at the center of the circle defined by three free or fixed points ( Distance panel). duplicate - Creates free points by duplicating existing free or fixed points. This is available in many panels when the "duplicate" advanced entity selector is available on a points collector. Misc. API commands that do not have an associated panel.
Fixed Points
by cursor - Creates fixed points at cursor locations on surfaces and surface edges (Point Edit panel, Quick Edit panel). on edge - Creates fixed points at uniform locations on a surface edge (Point Edit panel, Quick Edit panel). on surface - Creates fixed points at existing node/free point locations on/near a surface (Point Edit panel). project - Creates fixed points on surface edges by projecting existing free or fixed points (Point Edit panel, Quick Edit panel). defeature pinholes - When defeaturing pinholes, fixed points are created at the center of the each removed pinhole (Defeature panel). Misc. API commands that do not have an associated panel.
Lines
xyz - Create lines by specifying (x,y,z) coordinates (Lines panel). linear nodes - Creates linear lines between nodes (Lines panel). standard nodes - Creates standard lines between nodes (Lines panel). smooth nodes - Creates smooth lines between nodes (Lines panel). controlled nodes - Creates controlled lines between nodes (Lines panel). drag along vector - Creates lines by dragging nodes a specified distance along a vector (Lines panel). arc center and radius - Creates arcs by specifying the center and radius (Lines panel). arc nodes and vector - Creates arcs by specifying two nodes and a vector (Lines panel). arc three nodes - Creates arcs by specifying three nodes on the circumference (Lines panel). circle center and radius - Creates circles by specifying the center and radius (Lines panel). circle nodes and vector - Creates circles by specifying two nodes and a vector (Lines panel). circle three nodes - Creates circles by specifying three nodes on the circumference (Lines panel). conic - Creates conic lines by specifying the start, end and tangent locations (Lines panel).

Altair Engineering
extract edge - Creates lines as copies of surface edges (Lines panel). extract parametric - Creates lines at parametric locations on surfaces (Lines panel). intersect - Creates lines at the intersection of geometric entities: plane/lines, plane/surfaces, plane/ elements, plane/plane and surfaces/surfaces (Lines panel). manifold - Creates linear and smooth lines on surfaces using nodes (Lines panel). offset - Creates lines by offsetting lines a uniform or variable distance (Lines panel). midline - Creates lines by interpolating between existing lines (Lines panel). fillet - Creates fillet lines between free lines (Lines panel). tangent - Creates tangent lines between a line and a node list or line (Lines panel). normal to geometry - Creates lines perpendicular to lines, surfaces and solids from node or point locations (Lines panel). normal from geometry - Creates lines perpendicular from node or point locations on lines, surfaces and solids (Lines panel). normal 2D on plane - Creates lines that lie on a plane, are perpendicular to a line, and are defined from node or point locations (Lines panel). features - Creates lines from element features (Lines panel). duplicate - Creates lines by duplicating existing lines. This is available in many panels when the "duplicate" advanced entity selector is available on a lines collector. Misc. API commands that do not have an associated panel. Additional capabilities are available in solidThinking and solidThinking Inspired.
Surfaces
square - Creates two-dimensional square surface primitives (Surfaces panel, Planes panel). cylinder full - Creates three-dimensional full cylinder surface primitives (Surfaces panel, Cones panel ). cylinder partial - Creates three-dimensional partial cylinder surface primitives (Surfaces panel, Cones panel). cone full - Creates three-dimensional full cone surface primitives (Surfaces panel, Cones panel). cone partial - Creates three-dimensional partial cone surface primitives (Surfaces panel, Cones panel ). sphere center and radius - Creates three-dimensional sphere surface primitives by specifying the center and radius (Surfaces panel, Spheres panel). sphere four nodes - Creates three-dimensional sphere surface primitives by specifying four nodes ( Surfaces panel, Spheres panel). sphere partial - Creates three-dimensional partial sphere surface primitives (Surfaces panel, Spheres panel).
Altair Engineering

torus center and radius - Creates three-dimensional torus surface primitives by specifying the center, normal direction, minor radius and major radius (Surfaces panel, Torus panel). torus three nodes - Creates three-dimensional torus surface primitives by specifying three nodes ( Surfaces panel, Torus panel). torus partial - Creates three-dimensional partial torus surface primitives (Surfaces panel, Torus panel ). spin - Creates surfaces by spinning lines or a node list around an axis Surfaces panel, Spin panel). drag along vector- Creates surfaces by dragging lines or a node list along a vector (Surfaces panel, Drag panel). drag along line - Creates surfaces by dragging lines or a node list along a line (Surfaces panel, Line Drag panel). drag along normal - Creates surfaces by dragging lines along their normal (Surfaces panel). ruled - Creates surfaces by interpolating linearly between lines or nodes (Surfaces panel, Ruled panel). spline/filler - Creates surfaces by filling in gaps, such as a hole in an existing surface (Surfaces panel, Spline panel, Quick Edit panel). skin - Createssurfaces by skinning lines (Surfaces panel, Skin panel). fillet - Creates constant radius fillet surfaces across surface edges (Surfaces panel). from FE - Creates surfaces that closely fit a selection of shell elements (Surfaces panel). meshlines - A toolkit for creating lines associated to shell elements for advanced selection or surface creation (Surfaces panel). auto midsurface - Creates midsurface geometry automatically from multiple surfaces or solids ( Midsurface panel). surface pair - Creates midsurface geometry from one surface pair (Midsurface panel). duplicate - Creates surfaces by duplicating existing surfaces. This is available in many panels when the "duplicate" advanced entity selector is available on a surfaces collector. Misc. API commands that do not have an associated panel. Additional capabilities are available in solidThinking and solidThinking Inspired.
Solids
block - Creates three-dimensional block-shaped solid primitives (Solids panel). cylinder full - Creates three-dimensional full cylinder solid primitives (Solids panel). cylinder partial - Creates three-dimensional partial cylinder solid primitives (Solids panel). cone full - Creates three-dimensional full cone solid primitives (Solids panel). cone partial - Creates three-dimensional partial cone solid primitives (Solids panel). sphere center and radius - Creates three-dimensional sphere solid primitives by specifying the center

Altair Engineering
and radius (Solids panel). sphere four nodes - Creates three-dimensional sphere solid primitives by specifying four nodes ( Solids panel). torus center and radius - Creates three-dimensional torus solid primitives by specifying the center, normal direction, minor radius and major radius (Solids panel). torus three nodes - Creates three-dimensional torus solid primitives by specifying three nodes ( Solids panel). torus partial - Creates three-dimensional partial torus solid primitives (Solids panel). bounding surfaces - Creates solids by converting closed surface shells which define the solid boundary (Solids panel). spin - Creates solids by spinning surfaces around an axis (Solids panel). drag along vector - Creates solids by dragging surfaces along a vector (Solids panel). drag along line - Creates solids by dragging surfaces along a line (Solids panel). drag along normal - Creates solids by dragging surfaces along their normal (Solids panel). ruled linear - Creates solids by interpolating linearly between surfaces (Solids panel). ruled smooth - Creates solids by interpolating smoothly between surfaces (Solids panel). duplicate - Creates solids by duplicating existing solids. This is available in many panels when the "duplicate" advanced entity selector is available on a solids collector. Misc. API commands that do not have an associated panel. Additional capabilities are available in solidThinking and solidThinking Inspired.
See also Editing Geometry Querying Geometry
Altair Engineering

Editing Geometry
There are many different ways to edit existing geometry in HyperMesh. The methods used to edit a particular geometry depend on both the entities available for input and the level of detail required. The following methods are available for editing geometry in HyperMesh:
Nodes
clear - Deletes temp nodes (Temp Nodes panel). associate - Associates nodes to fixed points, surface edges and surfaces by moving them onto those entities (Node Edit panel). move - Moves nodes along surfaces (Node Edit panel). place - Places nodes on a surface at a specified location (Node Edit panel). remap - Moves nodes by mapping them from one line or surface edge to another (Node Edit panel). align - Aligns/projects nodes to an imaginary line (Node Edit panel). find - Create temp nodes by finding FE nodes associated with other FE entities (Find panel). translate - Moves nodes along a vector direction (Translate panel). rotate - Rotates nodes about a vector axis (Rotate panel). scale - Scales the dimensions of nodes either proportionally or uniformly (Scale panel). reflect - Reflects nodes about a plane to create a mirror image (Reflect panel). project - Projects nodes onto a plane, vector, line/surface edge or surface (Project panel). position - Translates and rotate nodes into new positions (Position panel). permute - Switches the coordinates of nodes (Permute panel). renumber - Renumbers nodes (Renumber panel). Misc. API commands that do not have an associated panel.
Free Points
delete - Deletes free points (Delete panel). translate - Moves free points along a vector direction (Translate panel). rotate - Rotates free points about a vector axis (Rotate panel). scale - Scales the dimensions of free points either proportionally or uniformly (Scale panel). reflect - Reflects free points about a plane to create a mirror image (Reflect panel). project - Projects free points onto a plane, vector, line/surface edge or surface (Project panel). position - Translates and rotate free points into new positions (Position panel). permute - Switches the coordinates of free points (Permute panel).

Altair Engineering
renumber - Renumbers free points (Renumber panel). Misc. API commands that do not have an associated panel.
Fixed Points
suppress/remove - Suppresses non-vertex fixed points (Point Edit panel, Quick Edit panel). replace - Combine smultiple fixed points by moving them to one fixed point location (Point Edit panel , Quick Edit panel). release - Releases fixed point vertices such that any shared edges attached to the point become free edges (Point Edit panel, Quick Edit panel). renumber - Renumbers fixed points (Renumber panel). Misc. API commands that do not have an associated panel.
Lines
delete - Deletes lines (Delete panel, Lines panel). combine - Combines two lines into one (Line Edit panel). split at point - Splits lines at graphically selected locations (Line Edit panel). split at joint - Splits lines at segment end points (Line Edit panel). split at line - Splits lines by using a cut line (Line Edit panel). split at plane - Splits lines at plane intersection locations (Line Edit panel). smooth - Smooths segmented lines (Line Edit panel). extend - Extends lines by either a specified distance, or to meet an existing node, point, line/surface edge or surface (Line Edit panel). translate - Moves lines along a vector direction (Translate panel). rotate - Rotates lines about a vector axis (Rotate panel). scale - Scales the dimensions of lines either proportionally or uniformly (Scale panel). reflect - Reflects lines about a plane to create a mirror image (Reflect panel). project - Projects lines onto a plane, vector or surface (Project panel). position - Translates and rotate lines into new positions (Position panel). permute - Switches the coordinates of lines (Permute panel). renumber - Renumbers lines (Renumber panel). Misc. API commands that do not have an associated panel. Additional capabilities are available in solidThinking and solidThinking Inspired.
Altair Engineering

Surfaces
delete - Deletes surfaces (Delete panel, Quick Edit panel). trim - Trims surfaces using nodes, lines, surfaces and planes (Surface Edit panel, Quick Edit panel). untrim/unsplit - Removes various trim/split lines from surfaces (Surface Edit panel, Edge Edit panel, Quick Edit panel). offset - Offsets surfaces along their normal directions while maintaining topological connectivity ( Surface Edit panel). extend - Extends the edges of surfaces to meet or intersect other surfaces (Surface Edit panel, Midsurface panel). shrink - Shrinks surfaces by drawing in all surfaces edges (Surface Edit panel). defeature - Removes pinholes, surface fillets, edge fillets and duplicate surfaces (Defeature panel, Edge Edit panel). midsurfaces - Modifies and edits extracted midsurfaces (Midsurface panel). surface edges - Toggles, suppresses, unsuppresses and equivalences surface edges (Edge Edit panel, Quick Edit panel). washer - Trims surfaces using free edge closed loop or shared edge offsets (Quick Edit panel). autocleanup - Performs basic automatic geometry cleanup functions in preparation for meshing ( Autocleanup panel). dimensioning - Modifies dimensions of or between surfaces (Dimensioning panel). morphing - Morphs surfaces that have had associated nodes morphed away from them (Morph panel ). translate - Moves surfaces along a vector direction (Translate panel). rotate - Rotates surfaces about a vector axis (Rotate panel). scale - Scales the dimensions of surfaces either proportionally or uniformly (Scale panel). reflect - Reflects surfaces about a plane to create a mirror image (Reflect panel). position - Translates and rotate surfaces into new positions (Position panel). permute - Switches the coordinates of surfaces (Permute panel). renumber - Renumbers surface edges and surfaces (Renumber panel). Misc. API commands that do not have an associated panel. Additional capabilities are available in solidThinking and solidThinking Inspired.
Solids
delete - Deletes solids (Delete panel). trim - Trims solids using nodes, lines, surfaces and planes (Solid Edit panel).

Altair Engineering
merge - Combines two or more solids into a single solid (Solid Edit panel). detach - Detaches solids that have shared fin faces from each other (Solid Edit panel). boolean - Performs complex merge and split functions on solids (Solid Edit panel). dimensioning - Modifies dimensions of or between surfaces (Dimensioning panel). translate - Moves solids along a vector direction (Translate panel). rotate - Rotates solids about a vector axis (Rotate panel). scale - Scales the dimensions of solids either proportionally or uniformly (Scale panel). reflect - Reflects solids about a plane to create a mirror image (Reflect panel). position - Translates and rotate solids into new positions (Position panel). permute - Switches the coordinates of solids (Permute panel). renumber - Renumbers solids (Renumber panel). Misc. API commands that do not have an associated panel. Additional capabilities are available in solidThinking and solidThinking Inspired. See tutorial HM2080 for an example.
See also Creating Geometry Querying Geometry
Altair Engineering

Querying Geometry
There are many different ways to query geometry in HyperMesh. The following methods are available for querying geometry in HyperMesh:
Nodes
card editor - With an appropriate template loaded, the card editor can be used to review node information (Card Editor panel). distance - Finds the distance between two nodes (Distance panel). angle - Finds the angle between three nodes (Distance panel). organize - Moves nodes into different include files (Organize panel). numbers - Displays the IDs of nodes (Numbers panel). count - Counts the total or displayed nodes (Count panel). Misc. API commands that do not have an associated panel.
Free Points
distance - Finds the distance between two free points (Distance panel). angle - Finds the angle between three free points (Distance panel). organize - Moves free points into different component collectors (Organize panel). numbers - Displays the IDs of free points (Numbers panel). count - Counts the total or displayed free points (Count panel). Misc. API commands that do not have an associated panel.
Fixed Points
distance - Finds the distance between two fixed points (Distance panel). angle - Finds the angle between three fixed points (Distance panel). numbers - Displays the IDs of fixed points (Numbers panel). count - Counts the total or displayed fixed points (Count panel). Misc. API commands that do not have an associated panel.
Lines
length - Finds the total length of selected lines/surface edges (Lines panel). organize - Moves lines into different component collectors (Organize panel). numbers - Displays the IDs of lines/surface edges (Numbers panel).

Altair Engineering
count - Counts the total or displayed line/surface edges (Count panel). Misc. API commands that do not have an associated panel.
Surfaces
normal - Reviews the normal direction of surfaces (Normals panel). organize - Moves surfaces into different component collectors (Organize panel). numbers - Displays the IDs of surface edges and surfaces (Numbers panel). count - Counts the total or displayed surfaces (Count panel). area - Queries the total area of the selected surfaces (Mass Calc panel). dimensioning - Queries dimensions of or between surfaces (Dimensioning panel). Misc. API commands that do not have an associated panel.
Solids
normal - Reviews the normal direction of solid surfaces (Normals panel). organize - Moves solids into different component collectors (Organize panel). numbers - Displays the IDs of solids (Numbers panel). count - Counts the total or displayed solids (Count panel). area - Queries the total area of the selected solids' surfaces (Mass Calc panel). volume - Queries the total volume of the selected solids (Mass Calc panel). dimensioning - Queries dimensions of or between surfaces (Dimensioning panel). Misc. API commands that do not have an associated panel.
See also Creating Geometry Editing Geometry
Altair Engineering

Meshing
Models are typically meshed automatically, but individual elements can be modified by hand if need to be to improve element quality in problem areas. Meshing is organized by the number of dimensions involved: 0-D Elements Line Meshing Surface Meshing Volume Mesh

Altair Engineering
0-D Elements
0-D elements are essentially mesh nodes with an additional value attached to them. The 0-D elements currently supported are masses. Masses have the ability to store one node, a value of mass, and a property reference.
Masses can be created in the masses panel, and the underlying concept is also the basis for Smooth Particle Hydrodynamcs Mesh.
Altair Engineering

SPH Mesh
Smooth Particle Hydrodynamics (SPH), Finite Point Method (FPM) is a technique used to analyze bodies that do not have high cohesive forces among themselves and undergo large deformation, such as liquids and gases. Typical applications for SPH FPM include airbag modeling in crash, fuel tank slosh, bird strike and explosion analysis. In SPH FPM, a given volume of the body of interest is discretized into particles, called SPH elements. SPH elements (called particles) are like nodes which do not have any geometric connectivity among themselves. Each SPH element has an effective mass. The mass sum of all particles in the filled volume of the body should be equal to the mass of the filled volume. In HyperMesh, SPH elements are currently supported as 0D MASS elements. The SPH mesh panel is shown below:
The SPH mesh panel has been added to the 1D page to facilitate the creation of SPH elements. When using the RADIOSS (Block) user profile, the SPH mesh panel can also be accessed via the menu bar by clicking Mesh, clicking Create and clicking SPH Mesh. The SPH mesh panel is shown below:

Altair Engineering
SPH Mesh Generation Input

Elements, components, surfaces and solids are supported as input to the SPH mesher. Selected elements can be shell or solid elements; however, the selected elements need to form a closed volume. Selected components can contain either an FE mesh or geometry; however, the FE mesh or geometry must also form a closed volume. More than one component can be selected to form a closed volume for SPH meshing. If the selected components are such that one is completely contained within another, SPH elements are created within the volume between the two selected components as shown below:
Component Volume Meshing
Altair Engineering

SPH Mesh Type and Pitch

The SPH mesher supports two mesh types for SPH element generation - simple cubic, and face centered cubic (FCC). Face centered cubic is similar to a hexagonal close packed (HCP) structure and is recommended for use in RADIOSS models. Pitch is defined as the distance between two SPH elements, h, as shown below, for both simple cubic and face centered cubic mesh types.

Altair Engineering
Material Density or Mass of Filled Volume

Each SPH element must have an effective mass. The effective mass for each SPH element is determined by entering either a material density of the material which fills the volume; or the total mass of the material in the filled volume, called the filled volume mass. If entering a material density, the SPH mesher determines the effective mass for each SPH element from material density, volume to be filled with SPH elements, and number of SPH elements generated as follows:
If entering the filled volume mass, the SPH mesher calculates effective mass for each SPH element from filled volume mass, and number of SPH elements generated as follows:
Altair Engineering

Filling Options
The input mesh/geometry can be filled either partially or completely by turning on the partial fill checkbox in the SPH mesh panel. In case of a partial fill, you need to provide the fill percentage and direction of fill. The direction can be defined using global X, Y, Z axis, a user defined vector, or the standard vector selector, which accepts 2 or 3 nodes to define a vector for the fill direction. The defined fill direction can be reversed by turning the reverse checkbox. A schematic of fill direction is shown below.

Altair Engineering
Solver Interfacing
It is recommended that you create a new component collector before starting the SPH mesh generation so that the generated mesh is stored in a separate collector. The generated SPH elements are mapped to the following cards for each supported user profile:
RADIOSS SPHCEL In addition, a new property card PROP/SPH is created for RADIOSS interface.
LS-Dyna *ELEMENT_SPH PAM-CRASH 2G SPHEL
Altair Engineering

Visualization of SPH (Mass) Elements

The generated SPH elements (particles) produces elements of mass configuration. Mass elements have a graphical representation of a spherical and also can have an element handle which places an additional label of the elements configuration with the graphical representation. In order to improve the visualization of SPH elements, it is suggested to turn off element handles. Element handles can easily be turned on/off from the Display toolbar using the Element Handles icon . SPH elements, like any element in HyperMesh, are created in the current component and are also colored the same as that component. The component color can be changed using standard Model Browser functionality.
Examples of SPH elements (particle) generation of a partially (50%) filled fuel tank

Altair Engineering
Line Meshing
1-D mesh allows accurate testing of connectors (such as bolts) and similar rod-like or bar-like objects that can be modeled as a simple line for FEA purposes. One-dimensional elements currently supported include bar2s, bar3s, rigid links, rbe3s, plots, rigids, rods, springs, welds, gaps, and joints. The following list indicates the storage capabilities and purpose of each of the 1-D elements. 1-D Element Bar2 Stores A property reference A local axis vector Pin flags Offset vectors Optional orientation nodes Bar3 Property reference Local axis vector Pin flags Offset vectors Optional orientation nodes Gap Joint Property reference Property reference Supports gap elements. Supports complex beams. Note: bar3s contain a third node designed to supported second order beams. Purpose Supports complex beams.
Supports kinematic joint definitions supplied with Safety Analysis Optional orientation nodes or system Codes. (s) A reference to two nodes A degree of freedom at each node Weight at each node Supports display type elements. Supports NASTRAN RBE3 elements.
Plot RBE3
Rigid link
A degree of freedom code One independent node Multiple dependent nodes
Supports rigid elements with multiple nodes.
Rigid Rod
A degree of freedom code A property reference
Supports rigid elements. Supports simple beams.
Altair Engineering

Spring
A property reference A degree of freedom code An optional orientation vector
Supports springs or damper.
Weld
A degree of freedom code
Supports weld elements.
Note:
The 1-D element-building panels are located on the 1D page of the default main menu. Plot elements are generated in the edit element, line mesh, elem offset, edges, or features panel.

Altair Engineering
Surface Meshing
A surface mesh or "shell mesh" represents model parts that are relatively two-dimensional, such as sheet metal or a hollow plastic cowl or case. In addition, surface meshes placed on the outer faces of solid objects are used as a baseline mapping point when creating more complex 3-D meshes (the quality of a 3-D mesh largely depends on the quality of the 2-D mesh from which it is generated). Three-noded trias, four-noded quads, six-noded trias, and eight-noded quads can all be built in HyperMesh. These two-dimensional elements can be built in any of the following panels: automesh shrink wrap cones drag edit element elem offset line drag planes ruled spheres spin spline torus Builds elements on surfaces according to user specifications. Builds 2D (optionally 3D) simplified meshes of existing complex models. Builds elements on conic or cylindrical surfaces. Builds elements by dragging a line, row of nodes, or group of elements along a vector. Builds elements by hand. Builds elements by offsetting a group of elements in the direction of their normals. Builds elements by dragging a line or group of elements along or about a control line. Builds elements on square or trimmed planar surfaces. Builds elements between two rows of nodes, a row of nodes and a line, or two lines. Builds elements on spherical surfaces. Builds elements by spinning a line, row of nodes, or group of elements about a vector. Builds elements that lie on a surface defined by lines. Builds elements on toroidal surfaces.
Note :
By default, first order linear elements are generated when the functions in these panels are executed, but second order parabolic elements may be generated by changing the element order in the mesh sub-panel of the options panel.
Altair Engineering

Automatic Mesh Generation

HyperMesh has a centralized plate and shell mesh generation tool called the Automeshing secondary panel. Most of the element creation panels use this module, which supplies as much automated assistance as possible. You can adjust interactively a wide variety of parameters and choose from a suite of algorithms. HyperMesh responds with immediate feedback on the effects of the changes, until you are satisfied with the resulting mesh. There are two approaches to the Automeshing secondary panel, depending on whether or not you use surfaces as the basis for the operation. If you use surfaces, you may choose from a greater variety of algorithms, have more flexibility in specifying the algorithm parameters, and employ the mesh-smoothing operation to improve element quality. If you do not use surfaces, the meshing process is usually faster and uses less memory. Most of the functions are still available and operate in the same way. Furthermore, there are situations in which it is not possible or not desirable to create a surface. For either method, the module operates the same. You control interactively the number of elements on each edge or side and can determine immediately the nodes that are used to create the mesh. You can adjust the node biasing on each edge to force more elements to be created near one end than near the other, which allows you to see immediately the locations of the new nodes. You can also specify whether the new elements should be quads, trias, or mixed and whether they should be first or second order elements. The created mesh can be previewed, which allows you to evaluate it for element quality before choosing to store it in the database. While you are in the meshing module, you can use any of viewing tools on the visual options menu to simplify the visualization of complex structures in your model. If you use surfaces, you can specify the mesh generation and visualization options to use on each individual surface. You may choose from several mesh generation algorithms. Mesh smoothing is also available and you may select the algorithm for that operation as well.
A solid model created by dragging automeshed plate elements.

Altair Engineering
The automeshing secondary panel can make second order elements for boundary element solutions.
Altair Engineering

Element Biasing
The automeshing process allows you to bias the placement of nodes so that their intervals are not uniform in size. You can designate that the smaller intervals go near the start of the edge, near the end of the edge, near both ends with larger intervals in the middle, or near the middle of the edge. Within the automesher, you may want to use biasing to improve element quality when transitioning from smaller to larger element sizes. When you use the Drag and Solid Offset panels, you can use biasing to cluster several layers of elements near the surface of a solid. In linear solids, the mesh at one end could be scaled several times larger than at the other end. Element biasing allows you to moderate the changes in aspect ratio from the start to the end. There are three methods you can use to calculate the biasing of node positions: Linear Exponential biasing Bellcurve
Use biasing to preserve element quality in complex regions.

Altair Engineering
Linear Biasing
In linear biasing, the biasing intensity corresponds to the positive slope of a straight line over the interval [0,1] of the Real Line. This interval is uniformly divided into as many subintervals as specified by the element density and they are mapped along the edge so that the length of the image interval is proportional to the height of the line over the midpoint of the source interval. Each image interval corresponds to the side of an element.
Specifically, let n be the element density and let
We want a node placement function x(s) taking values in [0,1] with x(0) = 0 and x(1) = 1 . If m is the slope of the line, and b is its y-intercept, then:
Using x(0) = 0, and x(1) = 1, we find:
so,
. For this, m is the absolute value of the biasing intensity. If the biasing intensity is negative, the nodes are placed according to 1 - x(s). Thus, a positive biasing intensity puts small elements at the start of the interval. We can use b to scale the behavior of the function so that convenient values are in the range [0,20]. The value used is b = 1.5 .
Altair Engineering

Exponential Biasing
In exponential biasing, the sizes of the intervals grow geometrically, progressing along the edge, with each successive interval being a constant factor larger than the previous. That factor is 1.0 plus 1/10 of the absolute value of the biasing intensity. This formula was chosen so that an intensity of zero will still represent no biasing, and convenient values will fall in the range [0,20]. Negative biasing intensities just reverse the edge, placing the smaller elements at the end instead of the beginning.
Specifically, let n be the element density and let
We want a node placement function x(s) taking values in [0,1] with x(0) = 0 and x(1) =1 .
Let
be the geometric growth factor.
We need a function
so that:
Let
then:
which gives the proper interval lengths,
then x(s) scales them to the range of [0,1]. Thus,

Altair Engineering
Bellcurve Biasing
In bellcurve biasing, nodes are distributed long the edge in a pattern that is symmetric across the midpoint of the edge. If the biasing intensity is positive, the smaller intervals are placed at the beginning and end of the edge, and if it is negative, they are placed at the middle of the edge.
Specifically, let n be the element density and
We need
so that
takes values in [0,1] with x(0) = 0 , x(1) = 1 , and has the behavior noted above. If we use:
for positive biasing intensity r, then x(s) becomes:
where erf() is the statistical error function,
Altair Engineering

Linked or Locked Edges

Most of the surface-less mesh generation algorithms require that some edges have exactly the same element density and biasing values as other edges. Those edges are automatically linked together so that they stay balanced. Any change to one of the edges is immediately applied to all others that are linked to it. Some of the surface creation panels allow you to use a node list to define one or more sides of a surface. In these circumstances, those nodes are used directly to make elements within the Automeshing secondary panel. The resulting edge is locked and you cannot change the element density or biasing. If you try to adjust the element density numbers corresponding to these locked edges, it has no effect. The error message, "The value of this number cannot be changed" is displayed.
Use the automeshing secondary panel to prepare input for solid offset.

Altair Engineering
Smoothing Algorithms
Three smoothing algorithms are available: Autodecide By default, the perimeter of the region is traversed looking for variations in element edge length and choose between size-correcting and shapecorrecting smoothing algorithms. The size-corrected smoothing algorithm attempts to even out the sizes of the elements at the cost of some element quality, usually in the form of worsened aspect ratios from the stretching of elements. A modified Laplacian over-relaxation that can correctly handle mixtures of quads and trias is used. If the element spacing around the perimeter is roughly uniform, this choice usually gives the best results. The shape-correcting smoothing algorithm attempts to correct the elements shapes, allowing variation in element size. HyperMesh uses a modified isoparametric-centroidal over-relaxation that can correctly handle mixtures of quads and trias. If there is a transition from small elements to large elements in the region, this choice usually gives the best results.
Size Corrected
Shape Corrected
Altair Engineering

Mesh Generation Algorithms

The mesh generation algorithms are divided into two types: those that require the presence of a surface to provide a context of operation, or those working entirely from node and/or line data. The mesh generation algorithms include: Autodecide If you are meshing a surface, the default mesh generation algorithm is Autodecide. In this case, the geometry of each face and the element densities specified for each edge is analyzed, and the algorithm that will give the best results is selected. For most configurations, the Free algorithm is chosen. The Free meshing algorithm is a general-purpose formula that works for most meshing conditions. The surface can have interior holes or edges and any number of sides. If quads or trias is the selected element type, an advancing front algorithm is used. If mixed is the element type, a sub-mapping algorithm is used. The advancing front algorithm uses the following process: Traverses the perimeter of the region, placing elements along the edges as it proceeds. Each site where an element could be placed is measured and one of several possible elements is chosen. Eventually the entire region is filled with elements. Examines the groups of elements to see if a local change in the connectivity might improve element quality. Applies repeatedly the selected smoothing algorithm until no node is moved farther than the specified smoothing tolerance. If quads is the selected element type for the current face, HyperMesh attempts to produce an all-quads mesh, but there are some situations in which one or more trias are included: If the total number of elements specified for the perimeter of the face is odd, at least one tria always needed. If there is a tight corner on the boundary that would require a poor quality quad, a single tria is used. Sometimes two or more trias are needed because of the particular order in which the elements were generated; if that is the case, you can usually eliminate them by changing some of the meshing parameters and then remeshing the region.
Free

Altair Engineering
If quads only is the selected element type, a mesh is created consisting entirely of quads; no trias will be used. Note that this method is more likely to fail to mesh than the quads option.
If trias is the selected element type, a streamlined version of this algorithm that is optimized for the different shape and connectivity requirements of tria elements is used. Map as Triangle, If the region is free from internal holes and the boundary is clearly triangular, Rectangle, or rectangular, or pentagonal in shape, the best choice of algorithm is usually to Pentagon map a standard mesh onto the region using transfinite interpolation. Such an operation is exceedingly fast, and where applicable, gives quality results rapidly. A standard template based on the element densities around the perimeter of the region is chosen. Ignoring rotations, more than 18 different configurations requiring distinct templates are recognized. To make tria elements, first a quads mesh is created and then each element is divided along its shortest diagonal. Map without Surface If you are creating a mesh entirely from line and/or node data, with no surface, the mesh generation algorithm is decided by the tool that was used to describe the desired operation. If you use the Drag panel, the algorithm is to drag. If you use the Spin panel, the algorithm is to spin, and if you use the Spheres panel, the algorithm is to map a sphere-covering mesh. You can still use the density and biasing manipulation tools but some edges will be linked together, so that the configuration always satisfies the balancing requirements of the intended mapping.
Altair Engineering

Using the Automeshing Secondary Panel

The functions of the automeshing secondary panel are divided into six sub-panels. You can switch freely between the sub-panels; the screen display changes to present only the information applicable to the current operation. density sub-panel type sub-panel biasing sub-panel checks sub-panel Each automeshing sub-panel has the mesh, reject, smooth, undo, abort, and return functions (see automeshing secondary panel in the Panels section), as well as the local view pop-up menu.

Altair Engineering
Shrink Wrap Meshing

Shrink wrap meshing is a method to create a simplified mesh of a complex model when high-precision models are not necessary, as is the case for powertrain components during crash analysis. The model's size, mass, and general shape remains, but the surface features and details are simplified, which can result in faster analysis computation. You can determine the level of detail retained by determining the mesh size to use, among other options.
You can shrink wrap elements, components, surfaces, solids, node clouds, or point clouds. The shrink wrap allows for wrapping of multiple components if they are selected. The selection provides the option to wrap all nodes, elements, components, surfaces, points, or solids, or only a certain portion of the model if desired. The input to the shrink wrap (that is, the model parts that you wish to wrap) can consist of 2d or 3d elements along with surfaces or solids. One use case for shrink wrapping is when you need to convert an .stl representation of a model into a tria/quad mesh; using shrink wrap provides a quick and efficient way of achieving this. Similarly, crash analysis does not require a highly-detailed powertrain model; in such cases you can use the shrink wrap mesh to quickly generate a simplified approximation of a detailed powertrain model. Crash analysts can then use that coarser shrink wrap representation within the crash simulation model. Other reasons to use the shrink wrap include being able to stitch over very bad geometry to generate an enclosed volume mesh for tetra-meshing. The shrink wrap tool can work from elements (whether 2d or 3d) or geometry. Thus, in the case of an "unclean" geometry model with many released (free) edges, you can either generate any arbitrary mesh on the unclean geometry using the automesh functionality beforehand and then creating shrink wrap or you can simply select the surface or solid without meshing the geometry first; either of these steps will yield good output mesh. (The key in such cases is to ensure that the element size used for the shrink wrap is large enough to stitch over the unclean surface edge splits so that an enclosed volume can be created.) Shrink wrap mesh can be generated as a surface mesh (using a loose or tight wrapping), or as a full-volume hex mesh by use of the Shrink Wrap panel. The distinction between surface or volume mesh is an option labeled generate solid mesh.
Altair Engineering

Loose Shrink Wrap Mesh

Loose wrap wraps the selected elements or components, surfaces, or solids with the target element size specified, and outputs an outer-volume mesh which approximately adheres to the original FE topology. A smaller element size generates a shrink wrap mesh that more closely approximates the original FE representation and adheres to more features; a larger element size produces a more basic mesh which ignores more features. The loose wrap does not project the nodes of the shrink wrap mesh to the original mesh, and typically the shrink wrap mesh will have an offset from the original mesh again, the offset is dependant on the target element size used. Once the shrink wrap meshing process has completed the new elements will be created in the current component. For every new run of the shrink wrap mesh (both loose and tight) it may be necessary to create a new component collector if you wish the elements to be placed in another collector other than the current component collector. In the example below, an .stl model is wrapped with a couple of different element sizes to show the differing output that can be achieved.
Original Model
Comparing the effect of varying mesh size (shell output):

2 mm mesh 5mm mesh

Altair Engineering
Comparing the effects of altering the jacobian value for solid mesh generation:
Within both tight and loose wrap algorithms there is an option to generate solid mesh. This will generate an all Hexa mesh on completion of the shrink wrap. When the generate solid mesh checkbox is active it will expose a minimum jacobian input, this option essentially will hexa mesh the part with this element quality critieria defined, it controls the hexa quality which is directly linked to the adherence to the topological features of the original component. The jacobian value must be between 0 and 1. The nearer the value is to 1 the cruder the output will appear, the mesh will be more heavily voxelised. When the value is closer to 0, you are allowing the shrink wrap solid mesh algorithm to smooth and adhere to more features while maintaining the solid mesh minimum jacobian element quality. By default the minimum jacobian value is 0.3. 2mm solid mesh, jacobian=1.0 2mm solid mesh, jacobian=0.3
Altair Engineering

With Features option

An additional option allows you to manually define features which will be adhered to during the meshing process. Typically, when using the shrink wrap the mesh attempts to follow features, but has some freedom to break away from original edges of the part. However, when the features are manually selected within the panel the resultant shrink wrap mesh will follow the chosen features. This can be important when defining a face of a component that may be in contact with other parts, or there may just be a feature that needs to be recognized and adhered to and cannot be approximated for whatever reason. The diagrams below show an example of the tight shrink wrap with feature output. Tight Wrap with and without feature recognition 2mm

Altair Engineering
Altair Engineering

Comparing the effects of using global system and local system for mesh orientation:
There is also an advanced option to control the mesh orientation. If you have a non-uniform part and you want to re-orientate the mesh so that it follows the features of the original component better then you can use this option. By default the mesh orientation always adheres to the global system, however, you can generate a local co-ordinate system and override the default behavior. In the example below, you can see the original mesh, the default shrink wrap mesh using the global system, and the new re-orientated mesh using the local co-ordinate system (note that rows of elements in the reoriented mesh run along the tubes rather than at angles across them). Original .stl input Shrink wrap output using global system Shrink wrap output using local system

Altair Engineering
Tight Shrink Wrap Mesh

Tight wrap creates a wrapped surface mesh which adheres as closely as possible to the original FE topology representation, automatically detecting and following the surface features of the model. The accuracy of the output is dictated by the element size: the larger the element size the less detail, the smaller the element size the more detail. This algorithm works differently than the loose wrap in that it projects the nodes of the shrink wrap to the original mesh, hence it is able to more accurately capture features. Notice in the images below the differences between tight and loose meshing, especially in the pulleys on the front of the engine and the resulting width of the individual cylinder exhaust pipes: Original Model
Tight Wrap 2mm
Loose wrap - 2mm
Altair Engineering

Within both tight and loose wrap algorithms there is an option to generate solid mesh. This will generate an all Hexa mesh on completion of the shrink wrap. When the generate solid mesh checkbox is active it will expose a minimum jacobian input, this option essentially will hexa mesh the part with this element quality critieria defined, it controls the hexa quality which is directly linked to the adherence to the topological features of the original component. The jacobian value must be between 0 and 1. The nearer the value is to 1 the cruder the output will appear, the mesh will be more heavily voxelised. When the value is closer to 0, you are allowing the shrink wrap solid mesh algorithm to smooth and adhere to more features while maintaining the solid mesh minimum jacobian element quality. By default the minimum jacobian value is 0.3. 2mm solid mesh, jacobian=1.0 2mm solid mesh, jacobian=0.3
With Features option

An additional option allows you to manually define features which will be adhered to during the meshing process. Typically, when using the shrink wrap the mesh attempts to follow features, but has some freedom to break away from original edges of the part. However, when the features are manually selected within the panel the resultant shrink wrap mesh will follow the chosen features. This can be important when defining a face of a component that may be in contact with other parts, or there may just be a feature that needs to be recognized and adhered to and cannot be approximated for whatever reason. The diagrams below show an example of the tight shrink wrap with feature output. Tight Wrap with and without feature recognition 2mm

Altair Engineering
Altair Engineering

Comparing the effects of using global system and local system for mesh orientation:
There is also an advanced option to control the mesh orientation. If you have a non-uniform part and you want to re-orientate the mesh so that it follows the features of the original component better then you can use this option. By default the mesh orientation always adheres to the global system, however, you can generate a local co-ordinate system and override the default behavior. In the example below, you can see the original mesh, the default shrink wrap mesh using the global system, and the new re-orientated mesh using the local co-ordinate system (note that the reoriented mesh runs along the tubes rather than across them). Original .stl input Shrink wrap output using global system Shrink wrap output using local system

Altair Engineering
Generate 2D BL Mesh
The Generate 2D BL Mesh utility allows you to generate 2D meshes with or without boundary layers on planar sections defined by sets/groups of edges defining closed loops. A region is considered closed if it is entirely bounded by edge elements (edge elements should be of type PLOTEL). Element configurations generated by this utility are linear quadrilateral (quad4) and triangular (tria3). To access this utility, from within the CFD user profile, on the Utility Menu, click the Generate 2D BL Mesh button. The following options allow you to create a 2D mesh with or without boundary layers from groups of edges defining closed and non-intersecting loops. Number of Boundary Layers Specifies the number of boundary layers to be generated from all the elements in components with type Wall. No boundary layers will be generated from components with type Wall if the value of the number of boundary layers is set to 0. Desired thickness for the first layer of elements. Boundary layer thickness growth rate from layer to layer. When Bound Type is set to Wall, boundary layers are generated along the component edges. No boundary layers are generated when Bound Type is set to far-field, inlet, outlet and symmetry. Note that edge elements in collectors having Bound Type defined as far-field, inlet, outlet and symmetry will be used to define the geometry, but they will not dictate element size/density. Used to select collectors with edge elements that define the boundaries of the domain. Selected collectors are populated in the Components Table with the default values set for 1st Layer Thickness, Growth Rate and Bound Type. Used to remove the selected collectors from the Components list. Used to assign the default values for 1st Layer Thickness, Growth Rate and Bound Type. Option to refine the boundary edges to generate boundary layer type meshes with the maximum desired element aspect ratio. Option to move boundary nodes to generate boundary layer type meshes with the maximum desired element aspect ratio. Used to refine the boundary edges (inserting nodes and/or moving nodes) to meet the specified aspect ratio. Generate the mesh with the selected edges and associated settings. Deletes the generated mesh.
1st Layer Thickness Growth Rate Bound Type
Add Collectors
Remove Set defaults
Allow Boundary Node Insertion Allow Boundary Node Movement Max Perimeter Element Aspect Ratio Generate 2D BL Mesh Reject
Altair Engineering

How do I.... Mesh a 2D Planar Area with Boundary Layers for CFD
See also An Alphabetical List of HyperMesh Panels

Altair Engineering
Meshing a 2D Planar Area with Boundary Layers

1. 2. 3. Select Generate 2D BL Mesh from the CFD Mesh section in the Utility Menu. Set the default values that apply to most components, i.e. 1st Layer Thickness, Growth Rate and Bound Type. Use the Add collector field to select or add components containing edge elements (elem type PLOTEL) that define the boundaries of the 2D section. Default values (1st Layer Thickness, Growth Rate and Bound Type ) are assigned to the selected components.
Altair Engineering

4. 5. 6.
Use Remove to remove collectors from the Component list. For fast component selection, use the options All, Reverse and None. Use Set defaults to reset the values of 1st Layer Thickness, Growth Rate and Bound Type for the selected components. Set the Bound type field to wall for all the collectors on which you want to generate boundary layers. No boundary layers will be generated on collectors having Bound type set as far-field, inlet, outlet and symmetry.

Altair Engineering
7. 8.
Set the number of boundary layers to be generated in Number of boundary layers. The checkbox Allow boundary node insertion is used to control the aspect ratio of boundary layer elements by refining the edges to generate boundary layer elements that satisfy the Max perimeter element aspect ratio value.
9.
The checkbox Allow boundary node movement is used to control the aspect ratio of boundary layer elements by boundary node movement so that generate boundary layer elements will satisfy the Max perimeter element aspect ratio value.
Altair Engineering

10. The checkbox Retain node seeding on edge w/o BL is used to ensure that nodes along the boundary layer edge are not modified. 11. Click Generate 2D BL Mesh to generate the mesh:

Altair Engineering
12. Click Reject to undo/delete the generated mesh.
See also
Altair Engineering

Generate 2D BL Mesh

Altair Engineering
Volume Meshing
Volume mesh or "solid meshing" uses 3-dimensional elements to represent fully 3-D objects, such as solid parts or sheets of material that have enough thickness and surface variety that solid meshing makes more sense than 2-D shell meshing. HyperMesh builds 4- and 10-noded tetras, 6- and 15-noded pentas, and 8- and 20-noded hexa elements. Tetras can be built in the edit element panel by hand or by using the tetramesh panel. Pentas and hexas can be built in any of the following panels: drag Drags a group of two-dimensional elements along a vector to create solids.
edit element Builds elements by hand. line drag linear solid solid map solid mesh elem offset spin split tetramesh Drags a group of two-dimensional elements along a line. Creates solid elements between two-dimensional elements. Builds solid elements between nodes, lines, and surfaces. Builds solid elements between a variable number of lines. Creates solid elements by offsetting a group of two-dimensional elements normal to the surface formed by the group of two-dimensional elements Spins a group of two-dimensional elements about a vector to create solids. Propagates split hexas. Fills with tetra elements a volume that is enclosed by tria elements or surfaces.
Note :
By default, first order linear elements are generated when the functions in these panels are executed, but second order parabolic elements may be generated by changing the element order in the mesh sub-panel of the options panel.
Altair Engineering

Solid Meshing Practices

Solid (3D) meshing can be done automatically, just like 2D shell meshing, but often requires that complex parts be partitioned into groups of smaller, simpler, connected solids instead of one large complex sold.
Partitioning is accomplished via the Geom page's Solids panel.

Altair Engineering
Partitioning Solids for Mappability

When using the Solid Map multi-solid feature it is recommended that the "Mappable" visualization mode is active from the visualization toolbar. The Mappable mode color codes the solids within the model according to whether the solids are solid meshable. The color coding for the mappable state can be user-defined by accessing the options panel's colors subpanel. The ignored map, not mappable, 1 directional map, and 3 directional map all relate to the mappable state of the solids. The goal is to ensure that the solids have been partitioned so that they are either 1 directional or 3 directional mappable. Only then can the Solid Map multi solids subpanel be used to solid mesh the model. Note : Even when all partitioned sections of the solid are mappable, this doesn't necessarily mean that they can all be meshed at once. In some cases they may need to be meshed a few at a time--or even individually in extreme cases. Mappability only ensures that the partitioned section can be meshed.
The example below steps through the complete process: When reading in a new model with solids, the model will be displayed in the blue color after you activate the Mappable visualization mode. This indicates that the mappability is currently being ignored. It is then necessary to partition the model so that the state of the solids changes to 1 directional or 3 directional. Note : If the model does not include any solids, (e.g. only surfaces are present), you can use the solids panel (on the Geom page) to create solids from the surfaces.
It's also worth noting that if some partitioning has already occurred from a previous session when the .hm file has been read in with the Mappable visualization mode already active, it will still be displayed as "ignored" map. To invoke the mappable algorithm calculation, simply change to another visualization mode, such as By Topo and then change back to Mappable again. This recalculates the state of all solids within the model.
With the Mappable visualization mode active, any solid edit operation will update the display of the solid entities automatically. The picture below shows that one trim of the model by a single surface (the top surface of the rectangular shaft, in this case) has created two additional solids within the model. One solid remains in the ignored map state (blue), one is now not mappable (orange) and one is 1-directional mappable (yellow - transparent).
Altair Engineering

After additional partitioning the model using the tools found in the Solid Edit panel, the model has transformed from having an ignored map and non-mappable states to having only 1-directional and 3directional mappable states. The model below has one 3-directional mappable solid (as indicated by the green transparent solid at the base of the shaft where it joins the part's main body).
Now that the partitioning is successful, the meshing can commence. Accessing the multi-solids subpanel and selecting all of the solids, plus the required meshing options, yields a complete 3D mesh for the entire complex part:

Altair Engineering
Selecting and masking a section of the elements confirms that the mesh is a complete 3D mesh, as opposed to just a surface mesh:
See also Mappable" visualization mode colors subpanel solids panel solid edit panel multi-solids subpanel
Altair Engineering

Solid Map Meshing

In solid meshing, the ability to be meshed is referred to as mappability. Mappability is directional and can be likened to putting a surface mesh on one face of the solid, then extending that mesh along a vector through the solid volume. So, for example, a perfect cylinder is mappable in one direction (the axis between its top and bottom faces) while a perfect cube is mappable in three (the axes between each pair of its identical faces). However, a combustion engine's cylinder head consisting of two cylinders of different radius joined together into a single solid entity would need to be partitioned to divide the two cylinders. Once partitioned, each cylinder would become mappable in one direction. Any given volume can have one of four states, which are color-coded when using the mappable view option on the visualization toolbar. Although the colors can be customized, the default settings are: Blue indicates a solid that has not been edited at all and therefore isn't evaluated for mappability. Orange indicates a solid that has been edited, but remains completely unmappable (further partitioning may enable mapping). Yellow indicates a solid that is mappable in 1 direction. Green indicates a solid that is mappable in three directions (this is very rare).
The first cube is mappable in 3 directions, but if a corner is split off it becomes mappable in only 1 direction--and the corner is not mappable w ithout further partitioning.
The Solid Map panel is used for solid-map meshing, and this panel includes several sub-panels. The general, line drag, linear solid, and ends only subpanels all draw from the same set of input controls (the more specialized panels simply filter out the controls that do not apply to their mapping techniques). Note that all of these subpanels depend on an existing 2D mesh, which is then extrapolated into a 3D mesh based on the parameters you input. The one volume and multi solids subpanels, however, can automatically create 3D mesh directly on solids as long as the solids you select are already mappable. Use the general subpanel to access all of the possible entry controls for maximum flexibility. Use the line drag subpanel to select a 2D mesh, and then select a line from the model geometry to use as the mapping direction. Use the linear solid subpanel to select two existing 2D meshes and extrapolate a 3D mesh that connects them. Use the ends only subpanel to select two opposing surfaces and one 2D mesh, then extrapolate the mesh between the surfaces. Use the one volume subpanel to select a single mappable solid volume and create a new 3D mesh

Altair Engineering
for it. Use the multi solids subpanel to select multiple mappable solids and create 3D meshes for them.
Solid Map Meshing Multiple Solids

You can select multiple solids for solid map meshing provided that each individual solid is in fact mappable. However, the meshing engine cannot always mesh every selected solid in a single operation, even when all the selected solids display as mappable. This may happen if the mappable constraints from different solids within the selection contradict each other. For example, one type of mappable constraint is that certain surfaces (along faces) of a mappable solid must be of the map-mesh type. When such constraints are in conflict, faces that caused meshing to fail are marked with a red square icon:
In this example both solids can be map-meshed individually, but solid #1 (the triangular one) must have all of the marked faces (5, 6, and 9) map-meshed. This, however, causes a conflict for solid #2, which can only be map-meshed by using the shared surface (6) as a destination. This conflicts since this shared surface must match the meshes on surfaces 4 and 8 in order to mesh solid #2. In such a case, you can mesh the remaining solids by deselecting the ones that are marked with the red icon but retaining the others in your selection. This either allows you to mesh the unmarked solids in a single action, or helps you further diagnose the problem. The remaining solids, unfortunately, will require individual meshing or further partitioning before they can be solid-map meshed as a group.
Altair Engineering

Tetra Meshing
The Tetramesh panel allows you to fill an enclosed volume with first or second order tetrahedral elements. A region is considered enclosed if it is entirely bounded by a shell mesh (tria and/or quad elements). Other element configurations generated in this panel are: hexahedral, wedge, and pyramids. These elements are typically generated when the user needs boundary layer type meshes on certain areas of the volume surface. Different sub-panels exist for different types of tetra meshing: tetra mesh subpanel allows you to fill an arbitrary volume, defined by its surface using tria/quad elements, with tetrahedral elements regenerates the mesh for a single volume of tetrahedral elements This allows you to automatically generate meshes with boundary layer type elements (pyramids and hexas) from selected boundary regions/elements, and fill the remaining core volume with tetrahedral elements. For fixed with boundary layer, select the components or elements from which you want to build the boundary layers. Select the remaining surface elements that form the enclosed volume as float w/o boundary layer. Given a solid entity or a set of surfaces representing a closed volume, this meshing option generates a shell mesh and fills the enclosed volume with solid elements. You can choose to create a shell mesh (2-D) using quads, trias, or mixed elements and a solid mesh (3-D) using tetrahedral elements only or mixed (tetras and penta) elements. In addition, you can use proximity meshing, which refines the mesh in areas where the features are small and closer together. See the following examples.
tetra remesh subpanel CFD mesh subpanel
volume tetra subpanel
You can also use surface curvature as a function of element density as shown below. This option creates finer mesh in areas of high surface curvature.

Altair Engineering
When you select quads or mixed as your 2-D element type, HyperMesh creates quad elements and splits them diagonally into two trias during tetra face creation. This can create tetra elements whose triangular faces are right triangles (90-45-45 angles) instead of equilateral triangles (60-60-60 angles).
Note :
Sometimes the meshing may fail to correctly interpolate from the surface mesh; when this occurs, the shell elements are cleaned up according to the same settings used in the Quick TetraMesh macro on the Utility Menu, and a second attempt is made. This means that some of the features in a model may be smoothed over.
Tetramesh Parameters
Sets general qualities of the tetrameshing engine, such as a maximum element size, growth rate, the balance between speed and element quality, or whether to perform smoothing operations after initial meshing. Lets you define a specific box-shaped volume within an existing teramesh in which to generate finer mesh.
Refinement Box
You can specify some elements to be fixed, and others to be floatable. A fixed tria-quad element is one that must be exactly represented as a face of a tetra/penta-pyramid/hexa element in the final mesh. A floatable element is one whose nodes locations are used, but the exact connectivity of those nodes can be modified if it produces a better mesh. Unless you need a special mesh type (e.g. surface layers of pentas/hexas), you should select as fixed only those elements that must match a pre-existing mesh, leaving the rest floatable. If the bounding surface contains quad elements, and if these quad elements are defined as fixed elements,
Altair Engineering

then a first layer of elements is generated on the boundary, and pyramid elements are generated from the quad faces. However, when quad elements are defined as float elements, they are split into two trias, and the tetra meshing proceeds normally. You can also specify various growth options in order to control the tradeoff between the number of tetras generated and their quality. Higher, more aggressive growth rates produce fewer elements, but they may be of poorer quality. The Tetramesh panel allows you to choose from three different mesh generation priorities. The generate mesh normally option applies in most cases, but if your solver is particularly sensitive to element quality, use the optimize element quality option. This directs the tetramesher to spend more time trying to generate better quality elements. In particular, it employs the volumetric ratio (CFD "skew") measurement for rating potential tetras. For some applications, element quality considerations are less important than mesh generation time. In those cases, choose the optimize meshing speed option.

Altair Engineering
CFD Meshing in HyperMesh

The following images illustrate how the Tetramesh panel is used for CFD Meshing:
Altair Engineering

Boundary Layers
The CFD mesh sub-panel enables users to generate quality boundary layer meshes for CFD simulations.
Options for elements fixed with boundary layer: There are three options to define the boundary layer thickness: Total boundary layer thickness Total thickness/element size Number of layers In addition, each of the above options has two data entries: First layer thickness Growth rate When the base surface mesh contains quad elements, and such elements are used to generate hexa elements in the boundary layer, then a transition layer is necessary to bridge the quad faces from the boundary layer hexas to the core tetrahedral elements. There are three options for the BL Transition: smooth pyramid simple pyramid all prism
The smooth pyramid option generates a transition layer composed of pyramid and tetrahedral elements. The thickness of this layer is controlled by the parameter smooth transition ratio, which represents the ratio between the transition layer thickness and the characteristic size of the base quads. The simple pyramid option generates a transition layer composed of a single pyramid for each quad of the base surface mesh. The height of these pyramids is controlled by simple transition ratio parameter, which represents the ratio between the transition pyramid height and the characteristic size of the base quad.

Altair Engineering
The all prism option generates only pentas/prisms on the boundary layer, thus avoiding the need for a transition layer because all base surface for the core tetramesh phase are trias. If the original enclosing surface has any quads, these quads are split into two trias thus all the base surface elements are always trias.
Options for float w/o boundary layer "Floating" elements are base surface elements defining areas that do not require boundary layer elements growing from them (e.g. far-field, inlet, outlet, symmetry planes). The way these elements or components are dealt with depends on the option: morph w/o remesh remesh
The morph w/o remesh option is used to keep the topology of the base surface mesh intact. These regions are morphed if they are in contact with boundary layer regions, as illustrated in the above figure for an inlet and symmetry plane. The top figure shows the starting surface mesh, the symmetry plane is blue, and the inlet area is green. The figure below shows the boundary layer elements in violet, and the inner core tetrahedral elements in brown. The remesh option is used when the user has no desire to maintain the topology of the base mesh. The last figure above illustrates an inlet and a symmetry plane that have been remeshed, and the resulting mesh can be compared with the morph w/o remesh option above.
Altair Engineering

Tetramesh Process Panel

This panel guides you through certain steps to create tetra-meshes efficiently and effectively. Not every step in the process is mandatory; you can follow the entire process or just a few steps, based on your requirements. (This is standard for Process Manager functionality.) Using the process-based approach provides several benefits: A step by step process to help you navigate through the different steps necessary to create a high quality tetramesh quickly. Note that effective tetrameshing requires a standard surface mesh to use as a base from which the 3-D tetras are built, so the first several steps of the process revolve around achieving quality surface meshes. Specific geometry cleanup and meshing algorithms are implemented in the Tetramesh Process Manager template to handle complex parts efficiently. A specific Tetramesh Process instance can be saved so its parameters can be reused later on similar parts--allowing for increased efficiency and implementation standards. The Tetramesh Process template can be used for automated geometry and element cleanup (Batch Mesher). When you first select Tetramesh Process from the menu, you are given two options: Create New starts new process with default settings; provide a session name and location where the template and related files will be saved. Load Existing opens a file browser so that you can load a previously saved process manager template file (*.pmi). The Tetramesh Process Manager template guides you through some basic steps necessary for tetra meshing complex parts:
At the same time it allows you to go back and forth between template panels and core panels to take advantage of core functionality. This feature is accessed by right-clicking the will allow you to dock or un-dock the Process Manager panel. icon. Clicking the icon

Altair Engineering
The Tetramesh Process Manager template helps in four major areas: geometry clean up, meshing, mesh cleanup, and model checking. These steps can be executed independent of each other as long as required information is available. Critical steps in the tetrameshing process of a complex part are automated to increase efficiency and effectiveness. Note: Please execute steps only once, unless a reject option is available within the current step. If you are not sure about the outcome of the next step; save the process before going further! Refer to Process Manager help to learn more about different options available for general Process Manager templates.
Altair Engineering

Geometry Import Panel - Tetramesh Process Manager

This panel allows for the import of new geometry or an existing model file. It contains several entry fields to let you fine-tune the import:
Import type: Select Geometry or HM file to specify the type of model that you plan to import. The following file formats are supported: HyperMesh database files CATIA IGES STEP DXF STL PDGS The File Type list box allows you to specify the translator to use, or you can leave it set on "auto detect" to allow HyperMesh to pick the translator based on the filename extension of the file that you import. Note that different selections may enable or disable other options on the panel. Import file name: Click the open file icon to browse for and select the desired file. VDAFS HM ASCII UG PRO/E ACIS PARASOLID
When importing a CAD file, you can automatically save it as a HyperMesh file after the import completes by checking the Save HM File After Import checkbox. You can also specify a scale factor if the imported model is in a spatial scale other than what you want to work with. You can use this feature to convert a model's measurements between metric and English units, for example. Note, however, that only spatial units are affected--mass and similar qualities are not. You can also choose between letting HyperMesh perform some automatic cleanup of the imported geometry based on the global cleanup tolerance specified on the Options panel's geometry subpanel; or you can choose to specify your own tolerance. The Import blanked (no show) components option allows you to control the presence of a blanked component in the translator. When checked, all entities marked as blank are moved to a special component. When unchecked, the translator ignores all the blank flags in the file. If you chose Catia for the File Type, then you may wish to enable the Name components by layer checkbox. This sorts the imported layers into separate components, creating new components for each

Altair Engineering
layer in the imported Catia data. The Import button begins the import process. Once import is complete, click Next to continue to the next step in the process. You can also click on a specific task in the Process Manager to the appropriate panel.
Other import options are standard, as described in the import panel.
Altair Engineering

Geometry Cleanup Panel - Tetramesh Process Manager

This panel assist you in performing cleanup tasks on the geometry that you plan to tetramesh. It includes separate tabs for equivalencing free edges, and for displaying free edges and creating filler surfaces to remove them.
The Free Edges tab includes a field to specify the tolerance that you want to use--the maximum distance across which surfaces can be made equivalent. Surfaces with a gap between them greater than this value will not be made equivalent. Once you pick a tolerance, the cleanup process is automatic--simply click Equivalence to combine edges and other features that fall within the tolerance value of each other. The Edge Tools tab includes more detailed options. Free Edges Filler Surfaces: You can generate filler surfaces for all the free edge loops by clicking this option; this helps to eliminate issues caused by missing surfaces by creating the closed volumes necessary for tetrameshing. Display Surfaces by Edge Type: You can display only the surfaces attached to selected edge types (Free Edges and T-junctions) by clicking Isolate. Click Display All to remove the mask and view all surfaces again. You can back up to the Import panel by clicking Previous. When finished cleaning up your geometry, click either Accept or Next to continue. You can also click on a specific task in the Process Manager to go to the appropriate panel.

Altair Engineering
Cleanup & Organize Holes Panel - Tetramesh Process Manager

This panel helps you isolate holes based on diameter ranges. Isolating and meshing holes separately from other geometry features is a very important step during tetra meshing; failing to do so can drastically affect the overall mesh quality. You may also wish to use this step even when there are no specific meshing requirements for holes just to organize your model.
Much of the functionality in this panel comes in the form of a table; individual cells within the table are a mix of display-only information and entry fields. Once organized, each table row has a color button on its left which corresponds to the HyperMesh component holding hole surfaces. Clicking one of these buttons selects the entire row, making it the "active" row. To deselect an active row, click the colorless button at the very top-left corner of the table (the one in the header row along with the column names). Use the entry fields in the active columns to specify how holes are located and meshed: Dr< The tool automatically selects holes with diameters of less than the value you specify. If you add multiple lines to the table, HyperMesh generates nonoverlapping ranges from them. Note : If you have no specific requirements for hole meshing, you can use a single diameter value that is larger than the largest holes in the model, in order to select all of the holes.
Number Circumference This determines the number of elements that you wish placed around the Elems circumference of any holes of the specified diameter range. Higher numbers result in a smoother mesh that better approximates a hole's shape and curvature, but could impact tetramesh quality if they result in smaller elements around the hole's edges than the enforced element size for other surfaces. If you have no specific requirements for hole meshing, Altair recommends using at least 6 elements for each hole's circumference. Longitudinal element size Add or Remove rows (+ and - buttons) The desired element size in the longitudinal direction--that is, traveling along the depth of the hole. If you have no specific requirements for hole meshing, it's best to use the same element size as the rest of the model. Use the (+ ) button to add another row to the table if you require multiple sets of hole criteria. Conversely, you can remove the active row with the (-) button to remove unneeded criteria sets. Note : Auto-Organize there is no way to undo the removal of a row! If you accidentally remove the wrong row, you will need to add a new row and recreate it.
This automatically organizes the holes into separate components based on the input parameters (diameter, etc.), so you get one component for each row in the table and the holes are placed into the components that their diameter and other criteria match. The model holes (and corresponding table rows) are color-coded
Altair Engineering

according to the component that they've been sorted into.
Organize
This allows you to manually organize any holes that were missed by the AutoOrganize routine into components using the Organize panel. Note : This option only becomes available after using Auto-Organize.
You can click the Prev button to return to the Geometry Cleanup panel, or click Next to continue. You can also click on a specific task in the Process Manager to go to the appropriate panel.

Altair Engineering
Mesh Holes Panel - Tetramesh Process Manager

This panel allows you to mesh the holes that you organized in the previous panel. It uses the same table, but now all of the organization criteria are read-only and cannot be changed. However, in this panel the Mesh Type column is active so that you can select the mesh type that you want to use when meshing the holes. There are two mesh type options in this panel: standard right-angle trias, and "union jack" right-angle trias.
Standard R-Tria
Union Jack R-Tria
As in the previous panel, each table row has a color button on its left which corresponds to the HyperMesh component holding hole surfaces. Clicking one of these buttons selects the entire row, making it the "active" row.
Here, the orange row is active.
To deselect an active row, click the colorless button at the very top-left corner of the table (the one in the header row along with the column names). You can mesh a single group of holes by clicking the row in the table that contains the hole diameter range that you wish to mesh, and then clicking the Mesh button. Alternatively, you can mesh all holes simultaneously by clicking Mesh All.
Altair Engineering

Similarly, you can use the Delete Mesh button by selecting an active row and then clicking the button. Note that there is no "delete all" functionality. You can back up to the Cleanup & Organize Holes panel by clicking Previous. When finished meshing, click either Accept or Next to continue. You can also click on a specific task in the Process Manager to go to the appropriate panel.

Altair Engineering
User Defined Features - Tetramesh Process Manager

This step helps you locate and organize miscellaneous features such as water jackets, inlets, outlets, contact surfaces, and so on. These features are listed in a table on the panel, so you can add or remove components by clicking the appropriate buttons. As with other tables in the Process Manager, each entry is color coded and you can select specific table entries by clicking on the colored box at the beginning of its row.
+ (button)
In order to create a feature, you must create a component to represent it and then add the relevant model surfaces to the component. Clicking this button opens a prompt that allows you to specify a new component name; click OK to create the new component. You can then add surfaces to that component, using the surfs collector that displays in the panel area.
As you click surfaces in the graphics window, HyperMesh automatically adds surfaces "by face" to the selection, so all of the surfaces associated with the same face in the model are added en masse. Click the proceed button in the panel area once you have collected some surfaces associated with the feature. This opens the Organize panel, where you can verify the surface selection and add or remove surfaces from the component. Clicking return in the Organize panel returns to the process manager's User Defined Feature Parameters Table . The features are now sorted into color-coded components and the corresponding table rows are colored to match as shown above. Auto Cleanup Click a table row to make it active, then click this button to open the Autocleanup panel. There, you can perform automated geometry cleanup operations on the geometry contained in the selected component. The Autocleanup panel performs cleanup operations based on the criteria set in the BatchMesher criteria file. Cleanup operations include equivalencing free edges, fixing of small surfaces (relative to the element size), and detection of features such as beads. It also performs specified surface editing/defeaturing operations like removal of pinholes below a specified size, removal of edge fillets, and the addition of a layer of washer
Altair Engineering

elements around holes. The Autocleanup panel performs the entire geometry cleanup portion of the BatchMesher. Since it performs a variety of geometry cleanup tasks, the results will not be instantaneous and can take a few minutes for large models. Cleanup criteria is determined by the BatchMesher parameter and element quality criteria files, both of which can be edited from within this panel using the BatchMesher Parameter Editor. - (button) This button removes the currently active row from the table, deleting the corresponding component. HyperMesh returns all related surfaces to their original components. Note that there is no way to undo this removal--if you accidentally remove a component you will need to recreate it.
You can back up to the Mesh Holes panel by clicking Previous. When finished cleaning up fillets click either Accept or Next to continue. You can also click on a specific task in the Process Manager to go to the appropriate panel.
See also BatchMesher criteria file BatchMesher Parameter Editor

Altair Engineering
Fillets Organize & Cleanup - Tetramesh Process Manager

This step in the process allows you to defeature fillets, replacing the rounded corner where two lines comer together with a point. HyperMesh calculates tangents at the beginning and at the end of each fillet, then intersects those tangents to create a corner.
The Surface Fillet Midline Split panel includes the following controls: Min Radius This lets you specify a cutoff point for the fillet size/radius. Any fillets in the model with radii of less than this value will be ignored, while fillets with radii greater than this will be cleaned up (removed so that the relevant lines meet at a sharp corner.) Max Radius Similar to Min Radius, this sets a boundary to limit which fillets are affected. In this case, fillets with radii greater than this value will be ignored and remain. Suppress Fillet Tangent Edges Cleanup Because fillets are removed by generating tangent lines to replace them, these lines often result in extra edges in model geometry. This option suppresses such edges after the fillet removal process. This button executes the fillet midline split routine based on what you have specified for the radius range and tangent suppression.
With suppress fillet tangent edges Without suppress fillet tangent edges
You can back up to User Defined Features by clicking Previous. When finished cleaning up fillets click either Accept or Next to continue. You can also click on a specific task in the Process Manager to go to
Altair Engineering

the appropriate panel.

Altair Engineering
Mesh User Defined Features - Tetramesh Process Manager

This step uses the same table as the User Defined Features panel, but allows you to mesh the userdefined features that you organized in the that panel. You can specify both the mesh type and the element size individually for each feature listed in the table.
On this panel, you can click the table entries for Mesh Type and Elem size to specify the values you want. Available element types are right triangle, and "Union Jack" right-triangle.
Standard R-Tria
Union Jack R-Tria
To create mesh for the selected/active row, click Mesh To create mesh for all rows click Mesh All To delete the mesh from a specific component, select the desired row and click Delete Mesh. You can back up to Fillets Organize & Cleanup by clicking Previous. When finished creating user-defined features, click either Accept or Next to continue. You can also click on a specific task in the Process Manager to go to the appropriate panel.
Altair Engineering

Global Organize & Cleanup - Tetramesh Process Manager

This panel allows you to organize and and clean up all remaining global surfaces -- that is, surfaces that were not already covered by holes and user-defined features.
You can also specify a minimum element size for all such components to prevent the autocleanup process from accidentally suppressing very small surfaces (smaller values result in more aggressive geometry cleanup, but could potentially result in loss of some features). If necessary, you can access the Organize panel to organize remaining surfaces into appropriate components, although this is optional. To clean all remaining surfaces, click the Auto Cleanup button. This opens the Autocleanup panel. Click prev to return to the Mesh User Defined Features panel, or click ACCEPT or Next to continue. You can also click on a specific task in the Process Manager to go to the appropriate panel.

Altair Engineering
Global Mesh - Tetramesh Process Manager

This panel is a continuation of the Global Organize & Cleanup panel, but allows you to mesh the remaining "global" geometry that wasn't covered by any of the previous meshing panels.
On this panel, you can specify the element size that you want to use when meshing all of the remaining global geometry. You can also choose the type of element that you wish to use; trias are the default. Clicking Mesh creates a mesh using the specified element size and type on all remaining "global" geometry. If you do not like the results, clicking Delete Mesh removes mesh from all such geometry, without affecting the specific items already meshed in previous stages (such as holes or user-defined features). Click Prev to return to the Global Organize & Cleanup panel, or click ACCEPT or Next to continue. You can also click on a specific task in the Process Manager to go to the appropriate panel.
Altair Engineering

Element Cleanup - Tetramesh Process Manager

This stage in the process focuses on optimizing the quality of the elements created during each of the previous meshing stages. The panel includes two tabs: one for automated cleanup, and one for manual cleanup. From this stage, clicking Accept or Next continues to the Tetramesh panel. Clicking prev returns to the Global Mesh stage.
Auto-Cleanup
The Autocleanup tab includes controls to specify the minimum size that is acceptable for any given element, the minimum feature angle that will be preserved, and the normals angle.
Note that the nodes of features (such as ridges) will not be preserved if their angle is less than the specified minimum angle. In addition, element quality requirements may override feature angle preservation regardless of the angle specified.
Minimum feature angle (low value)
Minimum feature angle (high value)
In addition, the Normals Angle specifies the maximum allowable angle between the normals of adjacent elements. When possible, adjacent elements whose normals exceed this angle will be split into multiple smaller elements with less-extreme normal angles. When you click the Auto Cleanup button, the mesh is examined within each component individually, removing elements of poor quality and stitching the mesh together to fill the resulting gaps. Cleaning up the mesh on a per-component basis prevents mesh overlap between adjacent surfaces that belong to different components.

Altair Engineering
Before Element Cleanup note "sliver" elements along midline
After Element Cleanup small / sliver elements are removed
Manual Cleanup
This tab includes a toggle to choose between finding free edges (which are associated with only 1 surface) and T-connections (which are associated with three edges) and a button to perform the find. In addition, another button allows you to display normals as vectors in the graphics area.
After you find edges, you can choose to clean them using specific tolerance value. HyperMesh will use this tolerance value identify nodes associated with free edges and try to stitch them, leaving nodes outside the tolerance unchanged. Click on Fix to fix free edges.. Similarly, checking the normals opens the Normals panel. Completing it returns to the Manual Cleanup tab.
Tetrameshing
Once you have finished with mesh cleanup, and all of the relevant previous stages are complete, clicking Accept or Next continues to the Tetramesh panel, where you can generate the 3-D mesh from the existing surface meshes.
Altair Engineering

For instructions on using the Tetramesh panel, refer to its specific panel help. Note : by default, all elements belonging to holes and user-defined features will be set to tetramesh as fixed trias/quads, while the rest of the model will be meshed using the "floatable" method.
You can also click on a specific task in the Process Manager to backtrack to the appropriate panel.
See also tetramesh panel

Altair Engineering
Volume Shrink Wrap

Within the Shrink Wrap panel there is an option to generate solid mesh this will produce an all-hexa or all-tetra mesh based on the selected elements or geometry. The shrink wrap can thus be used as a quick mechanism to generate solid meshes. Note that when generating such a mesh, the Jacobian value has a large effect on the coarseness of the resulting volume mesh, as described below. Using the shrink wrap mesh to achieve improved FE output from OptiStruct topology runs has also provided very good results which allow for quick tetra-meshing and, therefore, quick re-analysis after the optimization run.
Within both tight and loose wrap algorithms there is an option to generate solid mesh. This will generate an all hexa mesh on completion of the shrink wrap. When the generate solid mesh checkbox is active it will expose a minimum jacobian input, this option essentially will hexa mesh the part with this element quality critieria defined, it controls the hexa quality which is directly linked to the adherence to the topological features of the original component. The jacobian value must be between 0 and 1. The nearer the value is to 1 the cruder the output will appear, the mesh will be more heavily voxelised. When the value is closer to 0, you are allowing the shrink wrap solid mesh algorithm to smooth and adhere to more features while maintaining the solid mesh minimum jacobian element quality. By default the minimum jacobian value is 0.3. 2mm solid mesh, jacobian=1.0 2mm solid mesh, jacobian=0.3
Altair Engineering

Acoustic Cavity Meshing

Acoustic Cavity meshing generates a fluid volume mesh used to calculate the acoustic modes (or standing waves) inside the air spaces of a vehicle or similarly enclosed structural model. This is primarily used by Noise, Vibration, and Handling (NVH) engineers to design quieter interiors.
Acoustic Cavity meshing begins with the Acoustic Cavity Mesh panel. This panel accepts the necessary base input data to generate a voxelated preview mesh for one or more acoustic cavities. Once the preview mesh exists, however, the Acoustic Cavity tab displays in the tab area; this tool allows you to modify element quality checks, select specific volumes that have a preview mesh, and create the computational mesh for each selected cavity. Acoustic cavity meshing can be a CPU-intensive process, especially with fine and/or complex meshes, but this can be offset by additional CPU cores. the Acoustic Cavity Mesher is multithreaded to take advantage of multi-core environments.
How cavities are identified

Hole and gap patching is a critical part of defining cavities enclosed in the structure model. The process refers to patching over inconsequential gaps and holes that inevitably exist in the structure model, such as speaker holes. Gaps are defined as elongated openings based on their longest dimensions. Holes are openings defined by the radius of a sphere that can pass through them. By specifying the size of the hole and gap patches, you can control how the cavities are defined through auto search Typically, a cavity model is intended to be meshed right up to the outer body panel. Plastic and fiber trim panels are often included in a trimmed body model, but not meant to be used for cavity meshing. However, if the trim panels are selected during the AC meshing process they can be confused as outer body panels, leading to incorrect cavity definition. Therefore, it is important to ensure that only the exterior body panels are selected as the structure components to be included in the auto cavity search. Some typical types of cavities that users may wish to model include: Door cavity: most users prefer to include the cavity between the inner and outer door panels as a part of the interior. To make this happen, you must specify a hole patch size smaller than that of the largest opening in the inner panel, so that the opening is not patched. This allows interior mesh to flow into the door cavity. Instrument Panel (IP) cavity: to model the cavity behind the Instrument Panel as a part of the

Altair Engineering
interior cavity, you must exclude the IP parts from the structure component selection during auto cavity search. This forces the auto cavity search to ignore the existence of the sealed IP cluster when determining the interior volume of the passenger compartment. If the IP panel needs to be treated as a radiating source, a fluid boundary needs to be created at the location of the IP, similar to the how a package tray can be included as a structure part. Pillar Cavity: To included large pillar cavities (such as a D pillar cavity) as a part of the interior cavity, you must ensure that the gap and hole patch size specified are smaller than that of the largest opening. This prevents the opening from being patched and allows interior mesh to flow into the pillar cavity. Under seat cavity: To ensure the under-seat spaces are meshed, you must specify an element size smaller than the smallest dimension of the space, thus allowing the interior mesh to fill the cavity. Trim component cavity: special functionalities are required to mesh these cavities.
Factors that influence cavity meshing

The ability to model the acoustic cavity and predict acoustic response inside it is a critical part of NVH analysis, as noise level and quality become key product quality differentiators in the marketplace. A number of factors need to be considered when meshing an acoustic cavity model: Adequate Mesh Size. A rule of thumb is that at least 6 elements are needed per acoustic wavelength. Based on this rule, the minimum acoustic element sizes at various frequencies are: 500 Hz: 1000 Hz: 114 mm 57 mm
Smaller elements mean a more complex cavity model, which takes longer to run and generates a larger output file--particularly when fluid grid participation output is requested. Recall, however, that the mesher is multithreaded to take advantage of multiple CPU cores. Mesh size can also affect whether smaller cavity areas, such as the cavities underneath seats, get filled. Mesh size should be selected by considering the size of the smallest cavity that needs to be filled. Mesh quality as defined by Jacobian value, Tetra Collapse, and similar measures. Poor mesh quality may cause problems when submitted to the solver, or lead to less-accurate results. How closely the cavity shape matches the actual structure. This impacts how accurately the cavity model captures acoustic modes, and how difficult it is to obtain good coupling between the fluid and structure. It is important to define the structure panels intended to be coupled to the cavity. Aesthetics of the Cavity Mesh. The model may appear too jagged if the cavity mesh matches the structure closely. Some users prefer a smooth looking mesh for presentation purposes, but care must be taken so that this does not adversely affect the modes calculated or the quality of coupling generated when default ACMODL search parameters are used. Interior Response definition. Interior response points need to be defined so that they become a part of the mesh definition when cavity mesh is generated.
Altair Engineering

Seat Foam Cavity definition and coupling. Seat foams are typically modeled as denser air cavities. Their geometry definition can come in either as CAD data or existing FE mesh. Some seat models contain detailed foam curvature definition, while others may just be blocky boxes. The acoustic mesher can generate a new seat foam mesh and use congruent grids to connect to the interior cavity elements, or generate fluid MPCs to connect grids on a existing foam cavity mesh to the interior cavity mesh. Trunk Cavity separated from the Interior Cavity. For passenger sedans, the trunk cavity is typically modeled as a separate cavity from the interior, separated by the rear seat back foam cavity. Package Tray properly coupled to both interior and trunk cavities. For passenger sedans, the "package tray" or "parcel shelf" is situated behind the rear seat backs, between the interior cavity on the top and the trunk cavity below. Its vibration should be coupled into both cavities. This means a boundary (or gap) needs to exist in the cavity model where the package tray is located. This is typically accomplished by the two cavities not sharing grids at the boundary. Once generated, fluid cavities must be coupled to the structure. Radioss (Bulk Data) creates this coupling automatically during solver analysis, storing the information in the ACMODL card. In addition, Radioss generates an .interface file which can be loaded into HyperMesh to verify fluid surface and structure wetted surfaces:
See also acoustic cavity mesh panel Model Browser

Altair Engineering
Acoustic Cavity Tab

Once you've created a preview mesh in the Acoustic Cavity Mesh panel, the Acoustic Cavity tab opens. This tab allows you to specify element quality criteria and select individual volumes for refinement into final, computational volume meshes.
The tab includes three major sections: the tool buttons along the top, the browser tree, and the meshing controls at the bottom.
Tool Buttons
Opens the acoustic cavity tab's Options window. This window allows you to:
Altair Engineering

Set quality requirements for jacobian values at the volume hexa element corners and tetra collapse. Choose between displaying all of the volumes, or merely the largest ones (a number of your choosing, such as the 2 largest or 3 largest). This affects not only the graphics area, but also the browser tree. Note that changes to this value do not take effect until you mesh or remesh the existing cavities, or re-run the preview (see next button below). Choose whether or not to create fluid-structure faces. When checked, HyperMesh will create a surface skin of 2D shell elements to enclose each volume. Re-generates the preview. This is helpful if you change the element quality criteria or similar settings in the Options window, or alter the mesh type or response points. Displays only the acoustic cavities, hiding all other model geometry and mesh. Displays not only the cavities, but also the body elements that were used to generate them.
Browser tree
The tree displays each cavity mesh generated (up to the limit, if any, specified in the Options window). The cavities are segregated into separate groups for Structural Cavities, such as air spaces, and Seat Cavities, which are modeled as self-contained internal cavities. Each cavity has view options controlled in fashion similar to the Model Browser. A checkbox lets you choose whether or not to obtain a computational mesh for the cavity; right-clicking the color box lets you change the color that each cavity displays in; and rightclicking the mesh type icon allows you to pick between several display options: wireframe, solid, solid with feature lines, solid with mesh lines (which is the default), and semitransparent. In addition, right-clicking a cavity brings up options to rename it, show/hide/isolate/isolate only, expand or collapse the tree nodes, change which columns display in the browser, or access the Acoustic Cavity tab's Options window.
Meshing tools
The collection of list boxes and command buttons at the bottom of the tab allow you to create the computational mesh from a preview mesh, or to remesh an existing cavity. Mesh type: this list box lets you pick between a mixed non-conformal mesh of tetrahedral and hexahedral elements, or a mesh of all-tetrahedral elements. The mixed (hexa-tetrahedra) option is the default. Response points: response points can be used to specify test microphone locations--usually to simulate the passenger's ears. You can either pick nodes in your model to be the response points, or you can load them from an existing file. If you choose Read from file, you must use the browse button (...) to located and select the file containing the response points. Such files must be in the proper format, and should be commaseparate value (CSV) files. This image shows an example of the format:

Altair Engineering
In this example, A1 is the number of response points (4); row s 2-5 contain the X, Y, and Z coordinates of each point, ending w ith the point's name in column D.
Mesh: this button generates a new, computational mesh based on the mesh type and Options you've set. If your initial mesh is unacceptable due to quality requirements, response point placement, mesh type, or any other setting that originates from the Acoustic Cavity tab (rather than the Acoustic Cavity Mesh panel), you must use the re-run button ( ) to create a new preview using the updated settings. Do not click Reject, as this will reject the preview as well as the computational mesh, and will close the tab! You can pause the meshing process by clicking and holding the right mouse button. A dialog opens, asking if you wish to stop the meshing; if you choose yes, the mesh will be only partially generated and quality will most likely suffer. Reject: this button rejects the mesh completely--including the preview mesh--and closes the tab. Note, however, that as long as the Acoustic Cavity Mesh panel is open when you reject, your original input re-populates the component and seat collectors. This allows you to quickly change one or two settings, such as mesh or patch sizes, and then re-generate a preview without having to re-select all of the relevant components. On the other hand, if you exit the panel and then click reject, returning to the panel will not restore your previously-chosen entities. Note also that when you Reject the mesh, the components labeled ac_structural and ac_seats (which are created when you generate your preview mesh) are deleted. You can, however, retain these on a case-by-case basis by renaming them before you reject the mesh. Close: Closes the tab, but retains the current cavity meshes. This also clears all input from the Acoustic Cavity Mesh panel.
See also acoustic cavity mesh panel Model Browser
Altair Engineering

Voxel meshing
Available for the OptiStruct and Radioss (Bulk) user profiles on Windows, LINUX, IRIX, HPUX, SUN. Fills an enclose volume with voxels (hexas) of a predefined size. This type of mesh is only useful in topology optimization. It does not give meaningful results in a stress analysis. To work properly, the volume must be enclosed completely by shell elements (quads and trias) without TConnections or free edges. The normals of these elements should point inwards. The voxels (hexa elements) are stored in the component, hexas.
To generate a voxelmesh:
1. On the Opti page of the utility menu, under Topology: click Voxelmesh. A comps collector displays in the panel area. 2. 3. Select components that contain shell elements enclosing one volume. (If more than one volume is selected, normals should be adjusted manually). Click proceed. The Voxelmesh dialog is launched. 4. Check the relevant boxes: Perform element check: Checks for T-connections and free edges. If some are found, the results are stored in collectors of the corresponding names. Adjust normals: Automatic adjustment of normals (to inward). This works if the selection is one connected volume only. The volume may contain internal voids. Fill undercuts: Areas that are hidden in each coordinate direction are filled even if they are not touching the enclosed volume. These elements are stored in the component, hexasfill. One component for each number of inner nodes: The voxels created are stored in nine components (hexas0, hexas1...) depending on the number of nodes that are inside the volume. Note: Zero inner nodes may occur if one edge of the volume intersects the center of a hexa-face. Use local coordinates: Allows selecting a coordinate system along which to align the mesh. If no selection is made, the global (basic, screen) coordinate system is used. Edge size for hexa elements: Choose from Cubes or Rectangles. For cubes, enter a single value for the edge size; for rectangles enter x, y, and z edge lengths. Keep in mind that a grid of nodes is created for the box wrapping the

Altair Engineering
volume. So the memory usage may be high for unreasonably small values. 3. 4. Click Start. If you checked the Use local coordinates box, you will be prompted to select a coordinate system. Select the system and click proceed. The voxelmesh is generated.
Altair Engineering

Checking & Editing Mesh

There are several different ways of checking mesh. Many of these are based around determining mesh quality, but others check for mesh penetration, detect holes, and locate edges or features. See the following topics for greater detail: Element Quality Hole Detection tool Penetration check
See also Mesh Penetration

Altair Engineering
Element Quality
After you build your model, you can use the check elems panel to verify the quality of the elements in the model. You can check your model for connectivity and duplicate elements. The 1-d subpanel allows you to: Check one-dimensional elements for free ends Determine if a group of rigid elements form a loop Check weld and rigid elements for double dependency Check all elements for a minimum length of a side The 2-d subpanel allows you to: Check elements for warpage, aspect ratio, skew, and jacobian ratio Check the maximum and minimum interior angles of quad and tria elements Check all elements for a minimum length of a side Check a mesh of elements for its maximum chordal deviation from a real or inferred surface The 3-d subpanel allows you to: Check elements for warpage, aspect ratio, skew, and jacobian ratio Check the maximum and minimum interior angles of quad and tria elements Check all elements for a minimum length of a side Check tetra elements for collapse, CFD-style volumetric skew, and NASTRAN-style aspect ratio
The time sub-panel allows you to check for elements whose small size might cause problems for an explicit solver. The group sub-panel provides a tool to check for and eliminate group or interface elements whose underlying structural element has changed and left them detached. The user sub-panel allows you to verify element quality by using a template file that checks for user-specified conditions.
Altair Engineering

How Element Quality is Calculated

The quality of elements in a mesh can be gauged in many ways, and the methods used often depend not only on the element type, but also on the individual solver used. When possible, the most common or standard methods are used, but there is no truly standardized set of element quality checks. The different methods of calculating element quality are broken down here by solver (such as Nastran). Each applicationspecific topic includes information for both 2-D and 3-D element quality checks, as appropriate. However, only the checks actually used within HyperMesh by that solver are described in the following topics; when a solver does not support a specific check within HyperMesh, HyperMesh uses its own method to perform the check. This means that, for example, when using the NASTRAN checks, many of the checks that you see on the Check Elements panel are described in the Element Quality Checks: HyperMesh topic rather than the Element Quality Checks: Nastran topic. Click the links to learn how each application calculates element quality. Element Quality Calculation: HyperMesh Element Quality Calculation: HyperMesh-Alt Element Quality Calculation: OptiStruct Element Quality Calculation - Radioss (BulkData) Element Quality Calculation: Abaqus Element Quality Calculation: Ansys Element Quality Calculation: I-DEAS Element Quality Calculation: Medina Element Quality Calculation: Moldflow Element Quality Calculation: Nastran Element Quality Calculation: Patran
How Do I Change element check settings
See also check elements panel

Altair Engineering
Element Quality Calculation: HyperMesh

When possible, HyperMesh checks strive to maintain compatibility with popular solvers. Checks used for both 2-D and 3-D elements These checks apply to both types of elements, but when applied to 3-D elements they are generally applied to each face of the element. The value of the worst face is reported as the 3-D elements overall quality value. Aspect Ratio This is the ratio of the longest edge of an element to either its shortest edge or the shortest distance from a corner node to the opposing edge ("minimal normalized height"). HyperMesh uses the same method used for length (min) described below. For 3-D elements, each face of the element is treated as a 2-D element and its aspect ratio determined. The largest aspect ratio among these faces is returned as the 3-D elements aspect ratio. Aspect ratios should rarely exceed 5:1 Chordal Deviation Curved surfaces can be approximated by using many short lines instead of a true curve.
Chordal deviation is the perpendicular distance between the actual curve and the approximating line segments. Interior Angles These maximum and minimum values are evaluated independently for triangles and quadrilaterals. This measures the deviation of an element from its ideal or "perfect" shape, such as a triangles deviation from equilateral. The Jacobian value ranges from 0.0 to 1.0, where 1.0 represents a perfectly shaped element. The determinant of the Jacobian relates the local stretching of the parametric space which is required to fit it onto the global coordinate space. HyperMesh evaluates the determinant of the Jacobian matrix at each of the elements integration points (also called Gauss points) or at the elements corner nodes, and reports the ratio between the smallest and the largest. In the case of Jacobian evaluation at the Gauss points, values of 0.7 and above are generally acceptable. You can select which method of evaluation to use (Gauss point or corner node) from the Check Element Settings window.
Jacobian
Altair Engineering

Length (min.)
Minimum element lengths are calculated using one of two methods: The shortest edge of the element. This method is used for non-tetrahedral 3-D elements. The shortest distance from a corner node to its opposing edge (or face, in the case of tetra elements); referred to as "minimal normalized height".
You can choose which method to use in the Check Element Settings window. Note that this setting also affects the calculation of Aspect Ratio. Minimum Length / Size HyperMesh uses three methods to calculate the minimum element size: the shortest edge (in which the length of the shortest edge of each element is used), the minimal normalized height (which is more accurate, but more complex), and the minimal height (which is the same as same as minimal normalized height but without a scaling factor). minimal normalized height (MNH) is calculated differently for different element types. For triangular elements:
For each corner node (i) HyperMesh calculates the closest (perpendicular) distance to the ray including the opposite leg of the triangle, h(i). MNH = min(hi) * 2/ sqrt(3.0). The scaling factor 2/sqrt(3.0) ensures that for equilateral triangles, the MNH is the length of the minimum side. For quadrilateral elements:

Altair Engineering
For each corner node, HM calculates the closest (perpendicular) distances to the rays containing the legs of the quadrilateral that do not include this node. The figure above depicts these lengths as red lines. minimal normalized height is taken to be the minimum of all eight lines and the four edge lengths (thus, the minimum of 12 possible lengths). Skew Skew of triangular elements is calculated by finding the minimum angle between the vector from each node to the opposing mid-side, and the vector between the two adjacent mid-sides at each node of the element.
The minimum angle found is subtracted from ninety degrees and reported as the elements skew. Taper Taper ratio for the quadrilateral element is defined by first finding the area of the triangle formed at each corner grid point:
These areas are then compared to one half of the area of the quadrilateral. HyperMesh then finds the smallest ratio of each of these triangular areas to the quad elements total area (in the diagram above, "a" is smallest). The resulting value is subtracted from 1, and the result reported as the element taper. This means that as the taper approaches 0, the shape approaches a rectangle.
taper
Atri 0.5 Aquad
min .
Altair Engineering

Triangles are assigned a value of 0, in order to prevent HyperMesh from mistaking them for highly-tapered quadrilaterals and reporting them as "failed". Warpage This is the amount by which an element (or in the case of solid elements, an element face) deviates from being planar. Since three points define a plane, this check only applies to quads. The quad is divided into two trias along its diagonal, and the angle between the trias normals is measured.
Warpage of up to five degrees is generally acceptable.
Checks Used Only for 3-D Elements These additional checks only apply to 3-D elements. Minimum Length / Size HyperMesh uses 2 methods to calculate the minimum element size: the shortest edge (in which the length of the shortest edge of each element is used) and the minimal normalized height (which is more accurate, but more complex). In the minimal normalized height method, HyperMesh calculates the closest (perpendicular) distances to the planes formed by the opposite faces for each corner node.
The resulting minimum length/size is the minimum of all such measured distances. Tetra Collapse The height of the tetra element is measured from each of the four nodes to its opposite face, and then divided by the square root of the faces area.

Altair Engineering
The minimum of the four resulting values (one per node) is then normalized by dividing it by 1.24. As the tetra collapses, the value approaches 0.0, while a perfect tetra has a value of 1.0. Non-tetrahedral elements are given values of 1 so that HyperMesh wont mistake them for bad tetra elements. Vol. Aspect Ratio HyperMesh evaluates Tetrahedral elements by finding the longest edge length and dividing it by the shortest height (measured from a node to its opposing face). Other 3-D elements, such as hex elements, are evaluated based on the ratio of their longest edge to their shortest edge. This check applies only to tetrahedral elements; all others are assigned values of zero. Volume Skew is defined as 1-shape factor, so a skew of 0 is perfect and a skew of 1 is the worst possible value. The shape factor for a tetrahedral element is determined by dividing the elements volume by the volume of an ideal (equilateral) tetrahedron of the same circumradius. In the case of tetrahedral elements, the circumradius is the radius of a sphere passing through the four vertices of the tetrahedron.
Volume Skew
See also How Element Quality is Calculated Element Quality Calculation: HyperMesh-Alt
Altair Engineering

Element Quality Calculation: HyperMesh-Alt

HyperMesh includes some alternate methods of calculating certain element types. These apply only to quads or rectangular faces of solids, and only include alternate checks for Aspect Ratio, Skew, Taper, and Warpage. Note : because these methods apply only to certain quality checks, in order to use them you must choose the set individually option in the Check Element Settings window.
Aspect Ratio
ratio1 = V1/H1 ratio2 = V2/H2 Skew value is larger of ratio1 or ratio2.
Skew
First, HyperMesh constructs lines connecting the midpoints of each edge of the quad (dotted in the picture below). Next, HyperMesh constructs a third line (green in the picture below) perpendicular to one of the initial lines, then finds the angle between this third line and the remaining initial line--with which is it most likely not perpendicular, unless the quad is a perfect rectangle.

Altair Engineering
is the skew (angle) value.
Taper
First, the quads nodes are projected to plane defined by the orthonormal vectors UV found as follows: Z = X Y V = Z X U=X
For each corner node, determine a vector from itself to the center of the quadrilateral. These vectors are along the plane formed U-V. Consider the vertical sides: Calculate vectors along these sides by subtracting the red dashed vector from that directly above it. This forms the two blue vectors. Find the angle between these blue vectors. Now, do likewise for the horizontal sides. The taper is the largest of these angles.
Altair Engineering

Warpage
This check applies only to quads or rectangular faces of solids.
Warpage = 100 * h / max { Li }, where h is the minimum distance between the diagonals.
See also How Element Quality is Calculated Element Quality Calculation: HyperMesh Check Element Settings Window

Altair Engineering
Element Quality Calculation: OptiStruct

For the most part, OptiStruct uses the same checks as HyperMesh. However, OptiStruct uses its own method of calculating Aspect Ratio, and it does not support 3-D element checks. Aspect Ratio OptiStruct defines aspect ratio as the ratio between the minimum and maximum side lengths. 3-D elements are evaluated by treating each face of the element as a 2-D element, finding the aspect ratio of each face, and then returning the most extreme aspect ratio found. Curved surfaces can be approximated by using many short lines instead of a true curve.
Chordal Deviation
Chordal deviation is the perpendicular distance between the actual curve and the approximating line segments. Interior Angles These maximum and minimum values are evaluated independently for triangles and quadrilaterals. This measures the deviation of an element from its ideal or "perfect" shape, such as a triangles deviation from equilateral. The Jacobian value ranges from 0.0 to 1.0, where 1.0 represents a perfectly shaped element. The determinant of the Jacobian relates the local stretching of the parametric space which is required to fit it onto the global coordinate space. HyperMesh evaluates the determinant of the Jacobian matrix at each of the elements integration points (also called Gauss points) or at the elements corner nodes, and reports the ratio between the smallest and the largest. In the case of Jacobian evaluation at the Gauss points, values of 0.7 and above are generally acceptable. You can select which method of evaluation to use (Gauss point or corner node) from the Check Element Settings window. Length (min.) Minimum element lengths are calculated using one of two methods: The shortest edge of the element. This method is used for non-tetrahedral 3-D elements. The shortest distance from a corner node to its opposing edge (or face, in the case of tetra elements); referred to as "minimal normalized height".
Jacobian
Altair Engineering

Skew
Skew of triangular elements is calculated by finding the minimum angle between the vector from each node to the opposing mid-side, and the vector between the two adjacent mid-sides at each node of the element.
The minimum angle found is subtracted from ninety degrees and reported as its skew. Warpage This is the amount by which an element (or in the case of solid elements, an element face) deviates from being planar. Since three points define a plane, this check only applies to quads. The quad is divided into two trias along its diagonal, and the angle between the trias normals is measured.
See also How Element Quality is Calculated Element Quality Calculation: HyperMesh

Altair Engineering
Element Quality Calculation: Radioss (BulkData)

For the most part, RADIOSS (Bulk Data Format) uses the same checks as HyperMesh. However, RADIOSS (Bulk Data Format) uses its own method of calculating Aspect Ratio, and it does not support 3-D element checks. Aspect Ratio RADIOSS (Bulk Data Format) defines aspect ratio as the ratio between the minimum and maximum side lengths. 3-D elements are evaluated by treating each face of the element as a 2-D element, finding the aspect ratio of each face, and then returning the most extreme aspect ratio found. Curved surfaces can be approximated by using many short lines instead of a true curve.
Chordal Deviation
Chordal deviation is the perpendicular distance between the actual curve and the approximating line segments. Interior Angles These maximum and minimum values are evaluated independently for triangles and quadrilaterals. This measures the deviation of an element from its ideal or "perfect" shape, such as a triangles deviation from equilateral. The Jacobian value ranges from 0.0 to 1.0, where 1.0 represents a perfectly shaped element. The determinant of the Jacobian relates the local stretching of the parametric space which is required to fit it onto the global coordinate space. HyperMesh evaluates the determinant of the Jacobian matrix at each of the elements integration points (also called Gauss points) or at the elements corner nodes, and reports the ratio between the smallest and the largest. In the case of Jacobian evaluation at the Gauss points, values of 0.7 and above are generally acceptable. You can select which method of evaluation to use (Gauss point or corner node) from the Check Element Settings window. Length (min.) Minimum element lengths are calculated using one of two methods: The shortest edge of the element. This method is used for non-tetrahedral 3-D elements. The shortest distance from a corner node to its opposing edge (or face, in the case of tetra elements); referred to as "minimal normalized height".
Jacobian
Altair Engineering

Skew
Skew of triangular elements is calculated by finding the minimum angle between the vector from each node to the opposing mid-side, and the vector between the two adjacent mid-sides at each node of the element.
The minimum angle found is subtracted from ninety degrees and reported as its skew. Warpage This is the amount by which an element (or in the case of solid elements, an element face) deviates from being planar. Since three points define a plane, this check only applies to quads. The quad is divided into two trias along its diagonal, and the angle between the trias normals is measured.

Altair Engineering
Element Quality Calculation: Abaqus

These checks apply to both types of elements, but when applied to 3-D elements they are generally applied to each face of the element. The value of the worst face is reported as the 3-D elements overall quality value. Additional element checks not listed here are not part of the solvers normal set of checks, and therefore use HyperMesh check methods. Aspect Ratio This is the ratio of the longest edge of an element to its shortest edge. When applied to 3-D elements, the same method is used (longest edge divided by shortest edge) rather than evaluating each face individually and taking the worst face result. Interior Angles These maximum and minimum values are evaluated independently for triangles and quadrilaterals. This measures the deviation of an element from its ideal or "perfect" shape, such as a triangles deviation from equilateral. The Jacobian value ranges from 0.0 to 1.0, where 1.0 represents a perfectly shaped element. The determinant of the Jacobian relates the local stretching of the parametric space which is required to fit it onto the global coordinate space. HyperMesh evaluates the determinant of the Jacobian matrix at each of the elements integration points (also called Gauss points) or at the elements corner nodes, and reports the ratio between the smallest and the largest. In the case of Jacobian evaluation at the Gauss points, values of 0.7 and above are generally acceptable. You can select which method of evaluation to use (Gauss point or corner node) from the Check Element Settings window. Length (min.) Minimum element lengths are calculated using one of two methods: The shortest edge of the element. This method is used for non-tetrahedral 3-D elements. The shortest distance from a corner node to its opposing edge (or face, in the case of tetra elements); referred to as "minimal normalized height".
Jacobian
Skew (tria only)
Defined by shape factor. Abaqus determines triangular element shape factor by dividing the elements area by the area of an ideally shaped element. The ideally shaped element is defined as an equilateral triangle with the same circumradius the radius of a circle that passes through the three vertices of the triangleas the element.
Altair Engineering

This shape factor converts to skew by subtracting it from 1. Thus, a perfect equilateral tria element has a skew of 0 and the worst tria has a value of 1.0. Quadrilaterals are simply assigned a value of 0.
Checks Used Only for 3-D Elements These additional checks only apply to 3-D elements. Volume Skew This check applies only to tetrahedral elements; all others are assigned values of zero. Volume Skew is defined as 1 minus the shape factor, so a skew of 0 is perfect and a skew of 1 is the worst possible value. The shape factor for a tetrahedral element is determined by dividing the elements volume by the volume of an ideal (equilateral) tetrahedron of the same circumradius. In the case of tetrahedral elements, the circumradius is the radius of a sphere passing through the four vertices of the tetrahedron.

Altair Engineering
Element Quality Calculation: ANSYS

These checks apply to both types of elements, but when applied to 3-D elements they are generally applied to each face of the element. The value of the worst face is reported as the 3-D elements overall quality value. Additional element checks not listed here are not part of the solvers normal set of checks, and therefore use HyperMesh check methods. Aspect Ratio (tria) For tria elements, a line is drawn from one node to the midpoint of the opposite edge. Next, another line is drawn between the midpoints of the remaining two sides. These lines are typically not perpendicular to each other or to any of the element edges, but provide four points (three midpoints plus the vertex).
Then, a rectangle is created for each of these two lines, such that one line perpendicularly meets the midpoints of two opposing edges of the rectangle, and the remaining edges of the rectangle pass through the end points of the remaining line. This results in two rectangles, one perpendicular to each of the two lines:
Third, this process is repeated for each of the remaining two nodes of the tria element, resulting in the construction of four additional rectangles (six in total). Finally, each rectangle is examined to find the ratio of its longest side to its shortest side. Of these six valuesone for each rectanglethe most extreme value is then divided by the square root of three to produce the tria aspect ratio. The best aspect ratio (an equilateral tria) is 1. Higher numbers indicate greater deviation from equilateral. Aspect Ratio (quad) If the element isnt flat, its projected to a plane which is based on the average of the elements corner normals. All subsequent calculations are based on this projected element rather than the original (curved) element. Next, two lines are created which bisect opposite edges of the element. These lines are
Altair Engineering

typically not perpendicular to each other or to any of the element edges, but they provide four midpoints.
Third, a rectangle is created for each line, such that the line perpendicularly bisects two opposing edges of the created rectangle, and the remaining two edges of the rectangle pass through the remaining lines endpoints. This creates two rectanglesone perpendicular to each line.
Finally, the rectangles are compared to find the one with the greatest length ratio of longest side to shortest side. This value is reported as the quads aspect ratio. A value of 1 indicates a perfectly equilateral element, while higher numbers indicate increasingly greater deviation from equilateral. Interior Angles These maximum and minimum values are evaluated independently for triangles and quadrilaterals. Jacobian This measures the deviation of an element from its ideal or "perfect" shape, such as a triangles deviation from equilateral. The Jacobian value ranges from 0.0 to 1.0, where 1.0 represents a perfectly shaped element. The determinant of the Jacobian relates the local stretching of the parametric space which is required to fit it onto the global coordinate space. HyperMesh evaluates the determinant of the Jacobian matrix at each of the elements integration points (also called Gauss points) or at the elements corner nodes, and reports the ratio between the smallest and the largest. In the case of Jacobian evaluation at the Gauss points, values of 0.7 and above are generally acceptable. You can select which method of evaluation to use (Gauss point or corner node) from the Check Element Settings window. Length (min.) Minimum element lengths are calculated using one of two methods: The shortest edge of the element. This method is used for non-tetrahedral 3-D elements. The shortest distance from a corner node to its opposing edge (or face, in the

Altair Engineering
case of tetra elements); referred to as "minimal normalized height".
Angle Deviation (Skew)
This check only applies to quadrilateral elements, and relies upon the angles between adjacent legs at each corner node (e.g. the interior angles at each corner). Each angle is compared to a base of 90 degrees, and the one with the largest deviation from 90 is reported as the angle deviation. Triangular elements are given a value of zero.
Warping Factor This test applies to quadrilateral elements as well as the quadrilateral faces of 3-D bricks, wedges, and pyramids. Warping Factor is calculated by creating a normal from the vector product of the elements two diagonals. Next, the elements area is projected to a plane through the average normal. Finally, the difference in height is measured between each node of the original element and its corresponding node on the projection. For flat elements, this is always zero, but for warped elements one or more nodes will deviate from the plane. The greater the difference, the more warped the element is.
The warping factor is calculated as the edge height difference divided by the square root of the projected area. Checks Used Only for 3-D Elements Ansys does not use any exclusively 3-D checks within HyperMesh, but HyperMesh does use its own when Ansys is set as the solver. See the topic on Element Quality Calculation: HyperMesh for details on the 3-D checks.
See also How Element Quality is Calculated Element Quality Calculation: HyperMesh Check Element Settings window
Altair Engineering


Altair Engineering
Element Quality Calculation: I-DEAS

Additional element checks not listed here are not part of the solvers normal set of checks, and therefore use HyperMesh check methods. Checks used for both 2-D and 3-D elements These checks apply to both types of elements, but when applied to 3-D elements they are generally applied to each face of the element. The value of the worst face is reported as the 3-D elements overall quality value. Stretch (Aspect Ratio) Stretch is evaluated differently depending on whether the element is triangular or quadrilateral: For trias: the radius of the largest circle that fits within the element is divided by the longest edge, then multiplied by the square root of 12.
For quads: the minimum edge length is divided by the maximum diagonal length. The result is multiplied by the square root of 2. Note : the inverse of stretch displays on-screen in HyperMesh as the aspect. Chordal Deviation Curved surfaces can be approximated by using many short lines instead of a true curve.
Chordal deviation is the perpendicular distance between the actual curve and the approximating line segments. Jacobian This measures the deviation of an element from its ideal or "perfect" shape, such as a triangles deviation from equilateral. The Jacobian value ranges from 0.0 to 1.0, where 1.0 represents a perfectly shaped element. The determinant of the Jacobian relates the local stretching of the parametric space which is required to fit it onto the global coordinate space.
Altair Engineering

HyperMesh evaluates the determinant of the Jacobian matrix at each of the elements integration points (also called Gauss points) or at the elements corner nodes, and reports the ratio between the smallest and the largest. In the case of Jacobian evaluation at the Gauss points, values of 0.7 and above are generally acceptable. You can select which method of evaluation to use (Gauss point or corner node) from the Check Element Settings window. Length (min.) Minimum element lengths are calculated using one of two methods: The shortest edge of the element. This method is used for non-tetrahedral 3-D elements. The shortest distance from a corner node to its opposing edge (or face, in the case of tetra elements); referred to as "minimal normalized height".
Skew
This check measures the deviation of an elements corners from 90 degrees (for quads) or 60 degrees (for trias). The check calculates skew by finding:
for quadrilaterals, or
for triangular elements Where alpha is the angle of each corner. An ideal/equilateral element has a skew of zero, as none of its corners deviate from the target (90 or 60 degrees). Taper Taper ratio for the quadrilateral element is defined by first finding the area of the triangle formed at each corner grid point:
These areas are then compared to one half of the area of the quadrilateral. HyperMesh then finds the smallest ratio of each of these triangular areas to the quad elements total area (in the diagram above, "a" is smallest). The resulting value is subtracted from 1, and the result reported as the element taper. This means that as the taper approaches 0, the shape approaches a rectangle.

Altair Engineering
Triangles are assigned a value of 0, in order to prevent HyperMesh from mistaking them for highly-tapered quadrilaterals and reporting them as "failed". Warpage The amount by which an element (or in the case of solid elements, an element face) deviates from being planar. Since three points define a plane, this check only applies to quads. The quad is divided into two trias along its diagonal, and the angle between the trias normals is measured.
Checks Used Only for 3-D Elements These additional checks only apply to 3-D elements. Stretch (volume aspect ratio) Stretch is evaluated differently depending on whether the element is a tetrahedron, Wedge, Brick, or Pyramid: For tetras: the radius of the largest sphere that fits within the element is divided by the longest edge. This value is then multiplied by the square root of 24. For wedges: each face is evaluated for its 2-D stretch, and the worst value is reported. This means that the value reported for vol AR should always be the same as that reported for aspect. For bricks: the minimum edge length is divided by the maximum diagonal length. The result is multiplied by the square root of 3. For pyramids: no check is defined, so HyperMesh performs its standard check in which each face is evaluated as a 2-D object and the worst result reported.
Altair Engineering

Element Quality Calculation: Medina

Additional element checks not listed here are not part of the solvers normal set of checks, and therefore use HyperMesh check methods. Checks used for both 2-D and 3-D elements These checks apply to both types of elements, but when applied to 3-D elements they are generally applied to each face of the element. The value of the worst face is reported as the 3-D elements overall quality value. Aspect Ratio (Edge Ratio) The Edge Ratio is calculated as the ratio between an elements shortest edge and its longest edge; For the sake of consistency, HyperMesh inverts this result (effectively making it the ratio of longest to shortest) and reports the result as the elements aspect ratio. These maximum and minimum values are evaluated independently for triangles and quadrilaterals. This measures the deviation of an element from its ideal or "perfect" shape, such as a triangles deviation from equilateral. The Jacobian value ranges from 0.0 to 1.0, where 1.0 represents a perfectly shaped element. The determinant of the Jacobian relates the local stretching of the parametric space which is required to fit it onto the global coordinate space. HyperMesh evaluates the determinant of the Jacobian matrix at each of the elements integration points (also called Gauss points) or at the elements corner nodes, and reports the ratio between the smallest and the largest. In the case of Jacobian evaluation at the Gauss points, values of 0.7 and above are generally acceptable. You can select which method of evaluation to use (Gauss point or corner node) from the Check Element Settings window. Length (min.) Minimum element lengths are calculated using one of two methods: The shortest edge of the element. This method is used for non-tetrahedral 3-D elements. The shortest distance from a corner node to its opposing edge (or face, in the case of tetra elements); referred to as "minimal normalized height".
Interior Angles
Jacobian
Maximum Angle Minimum Angle Skew
The largest angle between adjacent edges of the element is reported. The smallest angle between adjacent edges of the element is reported. The elements interior corner angles are compared to 90 degrees (for quads) or 60

Altair Engineering
degrees (for trias). The absolute values of these deviations are summed and reported. Taper Quadrilateral elements are split into two triangles.
The area of the smaller of the two triangles is compared to the total area of the quadrilateral. In the example above, Note : To improve consistency with other taper checks, HyperMesh displays a value of 0.5 minus this value so that 0 implies no taper. However, this is not completely consistent with other taper checks, because in this case taper ranges from 0 (no taper) to 0.5 (full taper), whereas HyperMeshs own taper check reports a 1.0 for full taper.
Warpage
Elements with more than three nodes are split into triangles. The largest angle between the normals of triangle pairs is reported as the warpage.
Checks Used Only for 3-D Elements Medina does not use any 3-D specific checks. HyperMesh uses its own checks instead.
Altair Engineering

Element Quality Calculation: Moldflow

Additional element checks not listed here are not part of the solvers normal set of checks, and therefore use HyperMesh check methods. Checks used for both 2-D and 3-D elements These checks apply to both types of elements, but when applied to 3-D elements they are generally applied to each face of the element. The value of the worst face is reported as the 3-D elements overall quality value. Aspect Ratio This check is only applied to triangles, with quadrilaterals given a value of:
This is the same value obtained from an equilateral triangle, and is assigned to quads to prevent HyperMesh from misinterpreting a quad as a badly formed triangular element. MoldFlow calculates a triangles aspect ratio by squaring the longest edge of the triangle, and dividing the result by twice the triangles area. 1.0 denotes a perfect equilateral triangle. When applied to 3-D elements, the aspect ratio is the ratio between the longest and shortest edges of the tetrahedral element. Checks Used Only for 3-D Elements These additional checks only apply to 3-D elements. Vol. Aspect Ratio The volume aspect ratio is defined by finding the perpendicular height h of each node, and then dividing the longest edge length L by the shortest height h and multiplying by the square root of 1.5:
This results in an equilateral tetrahedron having a volume aspect ratio of 1.5. Nontetrahedral elements are assigned a value of 1.0.

Altair Engineering
Element Quality Calculation: Nastran

Additional element checks not listed here are not part of the solvers normal set of checks, and therefore use HyperMesh check methods. Interior Angles These maximum and minimum values are evaluated independently for triangles and quadrilaterals. This measures the deviation of an element from its ideal or "perfect" shape, such as a triangles deviation from equilateral. The Jacobian value ranges from 0.0 to 1.0, where 1.0 represents a perfectly shaped element. The determinant of the Jacobian relates the local stretching of the parametric space which is required to fit it onto the global coordinate space. HyperMesh evaluates the determinant of the Jacobian matrix at each of the elements integration points (also called Gauss points) or at the elements corner nodes, and reports the ratio between the smallest and the largest. In the case of Jacobian evaluation at the Gauss points, values of 0.7 and above are generally acceptable. You can select which method of evaluation to use (Gauss point or corner node) from the Check Element Settings window. Skew Nastran creates lines between the midpoints of opposite sides of the element, then measures the angles between these lines. The angle with the greatest deviation from the ideal value is used to determine skew. Nastran finds the taper of quadrilateral elements by treating each node as the corner of a triangle (e.g. using one of the quads diagonals as the triangles third leg). The areas of each of these four "virtual" triangles are compared to one half of the total area of the quadrilateral element to produce a ratio; the largest of these ratios is then compared to the tolerance value. A value of 1.0 is a perfect quadrilateral, and higher numbers denote greater taper. However, for the sake of consistency within HyperMesh, an equivalent taper is reported instead. This means that the smallest area ratio found (instead of the largest ratio) is subtracted from 1, so that 0 represents a perfect quadrilateral element instead of 1.0, and greater deviation from 0 indicates greater taper. Triangle elements are simply assigned a value of 0 to prevent HyperMesh from incorrectly identifying them as failed (highly-tapered) quads. Warpage First, Nastran constructs a plane based on the mean of the quads four points. This means that the corner points of a warped quad are alternately H units above and below the constructed plane. This value is then used along with the length of the elements diagonals in the following equation: WC = H / 2(D1+D2) Where WC is the Warping Coefficient, H is the "height" or distance of the nodes from the constructed plane, and D1 and D2 are the lengths of the diagonals. Thus, a perfect quad has a WC of zero.
Jacobian
Taper
Altair Engineering

Checks Used Only for 3-D Elements These additional checks only apply to 3-D elements. Vol. Aspect Ratio Nastran evaluates Tetrahedral elements by finding the longest edge length and dividing it by the shortest height (measured from a node to its opposing face). Other 3-D elements (such as hex elements) are evaluated based on the ratio of their longest edge to their shortest edge.

Altair Engineering
Element Quality Calculation: Patran

Additional element checks not listed here are not part of the solvers normal set of checks, and therefore use HyperMesh check methods. Checks used for both 2-D and 3-D elements These checks apply to both types of elements, but when applied to 3-D elements they are generally applied to each face of the element. The value of the worst face is reported as the 3-D elements overall quality value. Aspect Ratio (triangle) For triangles, the length of a side is divided by the height of the triangle from that side to its opposite node, then multiplied by of the square root of 3. In a perfect equilateral triangle, this formula produces a value of 1. The process is performed for each of the three sides, and the largest value of the three is reported as the aspect ratio.
Aspect Ratio (quad)
If the element isnt flat, its projected to a plane which is based on the average of the elements corner normals. All subsequent calculations are based on this projected element rather than the original (curved) element. Next, two lines are created which bisect opposite edges of the element. These lines are typically not perpendicular to each other or to any of the element edges, but they provide four midpoints. Third, a rectangle is created for each line, such that the line perpendicularly bisects two opposing edges of the created rectangle, and the remaining two edges of the rectangle pass through the remaining lines endpoints. This creates two rectangles one perpendicular to each line.
Altair Engineering

Finally, the rectangles are compared to find the one with the greatest length ratio of longest side to shortest side. This value is reported as the quads aspect ratio. A value of 1 indicates a perfectly equilateral element, while higher numbers indicate increasingly greater deviation from equilateral. Interior Angles These maximum and minimum values are evaluated independently for triangles and quadrilaterals. This measures the deviation of an element from its ideal or "perfect" shape, such as a triangles deviation from equilateral. The Jacobian value ranges from 0.0 to 1.0, where 1.0 represents a perfectly shaped element. The determinant of the Jacobian relates the local stretching of the parametric space which is required to fit it onto the global coordinate space. HyperMesh evaluates the determinant of the Jacobian matrix at each of the elements integration points (also called Gauss points) or at the elements corner nodes, and reports the ratio between the smallest and the largest. In the case of Jacobian evaluation at the Gauss points, values of 0.7 and above are generally acceptable. You can select which method of evaluation to use (Gauss point or corner node) from the Check Element Settings window. Length (min.) Minimum element lengths are calculated using one of two methods: The shortest edge of the element. This method is used for non-tetrahedral 3D elements. The shortest distance from a corner node to its opposing edge (or face, in the case of tetra elements); referred to as "minimal normalized height".
Jacobian
Skew (triangle)
Patran evaluates triangular skew by constructing a line from one of the triangles nodes to the midpoint of its opposite side, and another line connecting the midpoints of the remaining two sides.
An angle between these created lines is compared to 90 degrees to find its deviation from square. This process is then repeated for each of the remaining two nodes, and

Altair Engineering
the largest of the three computed angle deviations is reported as the elements skew. Skew (Quad) The skew test begins by bisecting the four element edges. This creates an origin at the vector average of the four corners, with the x-axis extending from the origin to the bisector on edge 2. Next, finding the cross-product of the x-axis and the vector that stretches from the origin to the midpoint of edge 3 defines the z-axis. With the x and z axes defined, their cross-product defines the y-axis.
Finally, subtracting the angle (located between the y axis and the line bisecting edges 1 and 3) from 90 degrees reveals the element skew. Taper Patran calculates taper by first averaging the corner nodes to find the element center, and creating lines between this center and the corner nodes to split the element into four triangles.
The taper calculation is simply the smallest triangles area divided by the average of all the triangle areasor, put another way, the taper is quadruple the area of the smallest triangle, divided by the sum of the areas of all four triangles:
Note :
For the sake of display compatibility, HyperMesh reports an equivalent value for Taper. Taper is determined as above, but is then subtracted from 1 to produce a number between zero and one. Thus, as the element taper
Altair Engineering

decreases, the reported value approaches zero (a perfect square). Triangles are assigned a value of zero to prevent them from showing up as failed quads. Warpage The warpage test bisects the element edges, creating a point at the vector average of the element corners. This point serves as the base node for a plane, with the planes x-axis extending from the base node to the bisector on edge 2 of the element. The plane normal (z-axis) is in the direction of the cross-product of this x-axis and the vector from the origin to the bisector of edge 3. Each corner of the quad is then the same distance, h, from the plane.
Next, Patran measures the length of each half-edge, and calculates the arcsine of the ratio of h to the shortest half-edge length (L):
Checks Used Only for 3-D Elements These additional checks only apply to 3-D elements. Vol. Aspect Ratio (Tetrahedron) Patran finds the aspect ratio of Tetra elements by finding the ratio between a vertex height and the area of the opposing face. This process is repeated for each vertex, and the largest ratio found.

Altair Engineering
Next, Patran multiplies the largest ratio found by 0.805927 (the corresponding ratio of an equilateral tetrahedron). The result is reported as the elements aspect ratio, with a value of 1 representing a perfect equilateral tetrahedron. Vol. Aspect Ratio (pyramid) Vol. Aspect Ratio (wedge) The Aspect Ratio of a pyramid element is simply the ratio of the elements longest edge length to its shortest edge length. This test begins by averaging the triangular faces of the element to create a triangular mid-surface. Next, it finds the aspect ratio of the mid-surface (as for a tria element). Then it compares the average height (h1) of the wedge element to the mid-surfaces maximum edge length (h2).
If the wedge height h1 exceeds the edge length h2, the wedges aspect ratio equals the mid-surface aspect ratio multiplied by h2, then divided by the average distance between the triangular faces (h3). If the wedge height h1 is less than the edge length h2, the wedge aspect ratio equals either the mid-surface aspect ratio, or the maximum edge length h2 divided by the average distance between the triangular faces (h3), whichever is greater.
Vol. Aspect Ratio (hexahedron)
Each face of the hex element is treated as a warped quadrilateral, and its center point found. The volume aspect ratio is simply the ratio of the largest distance h between the center points of any two opposing faces, to the smallest such distance:
Altair Engineering


Altair Engineering
Hole Detection tool

Location: Mesh menu, under Checks -> components -> hole detection. The Hole Detection tool enables you to locate many holes in a model--and potentially all of them--define them, and add those holes as geometry to a new component or the current one. You can specify many types of criteria to define specific types of holes that you wish to find. The tool includes three tabs: Preparation, 2D Holes, and 3D Holes.
Preparation Tab
This tab allows you to select the components that you wish to scan for holes, select the types of elements (2D, 3D, or both) in which to find holes, and specify a feature angle for 3D solid holes.
Holes in 3D solids are assumed to have an opening on one or more faces of the solid. You can base detection on each hole's feature angle--that is, the angle at which the hole deviates from the face in which its opening appears:
Altair Engineering

The 3D solid hole feature detection list box allows you to pick between two methods of specifying the feature angle: By specified angle: this option includes a single numeric text box, so that you can specify the exact angle of holes you wish to detect. Auto using angle range: this option displays two additional numeric boxes, allowing you to specify the upper and lower limits of hole angles that you wish to detect. Holes with feature angles beyond either of these numbers will be ignored. In either case the values must be more than zero (zero would be perfectly collinear with the face) but no greater than 90 degrees (which represents a hole that runs perfectly perpendicular to the face). Once you select entities and determine the element types and feature angles to search for, you must click run to perform the scan. Once the scan is complete, the 2D Holes and 3D Holes tabs become usable; otherwise they are disabled.
2D Holes Tab
This tab allows you to refine the types of holes you wish to find in 2D mesh.
The hole type refers to the 2D shape of the opening: circular (including ovals), square, or rectangular. The general option includes all shapes. Minimum and Maximum dimension refers to the width of the hole, regardless of shape. If set at or below zero, these checks are not run.

Altair Engineering
Offset plane deviation checks each node on the edge of a hole, relative to the plane that best approximates all of the nodes on the hole's edge. This is a distance measurement; any nodes further than this distance from the midplane of the bounding box will cause the tool to ignore the hole. If this value is set to zero or less, the check is not run at all on any holes.
In this image, the raised node might invalidate the hole.
The Hole organization options control which component the found holes are placed into: by default they are added to a new component called êdges_holes_shell. However, you can force them all to be placed into the current component instead. Once you're satisfied with your settings, click Find. All 2D holes matching the criteria are located.
3D Tab
This tab allows you to refine the types of holes you wish to find in 3D mesh to greater detail.
Altair Engineering

The hole type refers to the shape of the opening: circular, square, or rectangular. The general option includes all shapes. Minimum and Maximum dimension refers to the width of the hole's openings, regardless of shape, and carries over from the 2D page because the openings themselves are 2D edges. If set at or below zero, these checks are not run.
Minimum and Maximum height refers to the depth of the hole, regardless of shape. If set at or below zero, these checks are not run.

Altair Engineering
Offset plane deviation checks each node on the edge of a hole, relative to the best-fit bounding box that encompasses all of the nodes on the hole's edge. This is a distance measurement; any nodes further than this distance from the midplane of the bounding box will cause the tool to ignore the hole. If this value is set to zero or less, the check is not run at all on any holes.
With very low plane deviation, the red node might invalidate this hole.
Cone angle allows you to specifically search for tapered holes; this is the maximum angle between the hole's sides, and a planar cross-section that is perpendicular to its length.
Thus, a value of 90 represents a hole that does not taper at all. Holes with a taper at or below the specified angle (that is, tapers sharper than the specified angle) will be found, while tapers above it (that is, closer to being a straight shaft) will be ignored. The default value is 80.0 degrees; if less than or equal to 0.0 the cone angle check is not run. The Hole organization options control which component the found holes are placed into: by default they are added to a new component called êdges_faces_solid. However, you can force the shell hole elements to be placed into the current component instead. If you activate the Create edges option, the tool will generate elements around the perimeter of the hole edge these new elements are organized into a component called êdges_holes_shell. Use Hole handling to determine whether to find Open holes, Capped holes, or All holes.
Altair Engineering

Once you're satisfied with your settings, click Find. All 3D holes matching the criteria are located.
See also Checking & Editing Mesh

Altair Engineering
Penetration check
Penetration is defined as the overlap of the material thickness of shell elements, while Intersection is defined as elements that actually pass completely through one another:
These diagrams illustrate the concepts of penetration and intersection.
Penetration checking is supported by all of the impact solver interfaces such as LS-DYNA, RADIOSS and PAMCRASH, and works best with a user profile that supports thickness data for modeled shell elements. Note that the default HyperMesh user profile does not support modeled element thickness, but the penetration checking tools allow you to specify a uniform thickness when performing a check. Notes The penetration panel only allows you to set up and initiate the check; the majority of the checking tool actually resides in a special tab that opens in the tab area. However, this tab only displays after you complete the panel and run an initial check. When the penetration check runs, it automatically masks (hides) everything in your model except for the penetrating or intersecting elements. It then fits the view to these elements components. You can show or hide additional elements using toolbar buttons located in the penetration tab, and you can make other entity types (such as ellipsoids) visible again via the display panel or the mask panel. Solid entities never register penetrations between each other; instead, any overlap between solids registers as intersections, because one or more of each the solids faces intersect. A solid that is completely contained within another solid will not be detected as an intersection or penetration, because its faces will not intersect any of the larger (containing) solids faces. In addition, only surface elements register penetrations; the tool cannot find penetrations between internal (e.g. tetraor hexa-) elements.
Intersection w ould be found in the left image, but not in the right.
Solids can register penetrations with respect to adjacent shell elements, based on the thickness of the shell elements.
Altair Engineering


Altair Engineering
Mesh Coarsening
Location: Mesh menu > create sub-menu Sometimes an existing mesh is finer and more complex than your simulation requires. This can result in the simulation--or other utilities that depend on existing elements--taking an unnecessarily long time to run, especially when your goal is to view real-time animations for NVH (Noise, Vibration, and Handling) or similar analyses. In such cases, you can use the Coarsen Mesh utility to simplify the mesh by combining many small elements into a smaller number of larger ones.
A model before coarsening (mesh size 30).
The same model after coarsening (mesh size 200).
When a mesh is coarsened like this, it's important to note that every node in the coarse mesh corresponds exactly to one of the nodes in the original mesh--although many nodes are removed, the ones that remain are still the same nodes from the original model. No locations or qualities are changed. Similarly, any nodes or points with special information (such as comments) in the 10th column of their deck will be preserved.
Altair Engineering

As the example above indicates, it is best to filter out components that are not relevant to your analysis--in this case, the wheels and suspension were removed from consideration.
The Coarsen Mesh utility

This utility opens in a free-floating dialog window.
This dialog allows you to pick the components that you wish to simplify, any hard points (such as those defining a hole or ridge) that must be preserved, a new Element size , and a Mesh type (mixed or trias-only). In both cases, you must click the selector twice, as if you were accessing its extended endtity selection menu; however, the second click opens a temporary panel in the panel area. This panel allows you to select the desired components or nodes, and then proceed in order to close the panel and return to the Coarsen Mesh dialog. In addition, you can specify several options (note that are only accessible by clicking the double down-arrow next to Advanced options): A Feature angle . Features with angles smaller than this may be eliminated and meshed over, while features with angles greater than this will be preserved so that mesh aligns with the feature line rather than allowing elements to cross over it. The coarsening process uses two stages; if the first stage fails on some elements, the second stage is run. The feature angle setting only applies to the second stage; it is irrelevant to the initial stage.

Altair Engineering
A Minimum hole diameter. Holes smaller than this will be meshed over, but holes at least this size will be preserved. Delete 1Ds before meshing: Any 1D elements that are part of the input selection are considered for this operation. If those 1D elements are attached to a hard point or are part of a 1D path back to the 2D/3D structure, those elements are not deleted. Any other 1D elements that are part of the input selection are deleted. Delete free 1Ds after meshing: The coarsening operation itself includes making sure the relevant rigidlink/RBE3 elements are connected back to the structure accordingly. For this option rigidlink/ RBE3 elements are considered free only if all legs are free after coarsening/reconnection is complete. Delete free rigidlink/RBE3 legs after coarsening: This deletes any free legs after coarsening and reconnection are complete. As mentioned above, a rigidlink/RBE3 element is only free if all legs are free for the purpose of this tool. Create PLOTEL: Once all of the above rules have been completed, any remaining 1D elements that were part of the input selection are converted to PLOTEL. This includes all legs of rigidlink/RBE3 elements. Every leg of these elements needs to be converted to a separate PLOTEL (e.g. a 10 leg RBE3 will be 10 PLOTELs). Create PLOTEL 3/4: This option will convert all Tria and Quad elements to PLOTEL3 or PLOTEL4 element types configurations. This option is only available in Radioss Bulk and OptiStruct user profiles. Once you set the desired options, you can Mesh the selected components. If the results are not satisfactory, you can reject the new coarse mesh, change the options, and try again.
Altair Engineering

BatchMesher
Altair's BatchMesher is a tool that can perform geometry feature recognition, cleanup and automatic meshing (in batch mode) for given CAD files. Consult the following topics for more details:
About BatchMesher BatchMesher Setup Batch Mesh Tab Configurations Tab Run Status Tab User Procedures Tab BatchMesher Customization User-registered Procedures BatchMesher Parameter Editor hw_batchmesh tcl command BatchMesher Error Codes Grid Computing with BatchMesher

Altair Engineering
About BatchMesher
BatchMesher is a tool that can perform geometry feature recognition, cleanup and automatic meshing (in batch mode) for given CAD files. The BatchMesher can read a geometry file using the specified CAD translator, and perform a variety of geometry cleanup operations to facilitate better mesh creation for the selected element size and type. Cleanup operations include equivalencing free (red) edges, fixing small surfaces (relative to the element size), and detecting features such as beads, fillets, flanges etc. BatchMesher also performs specified surface editing/defeaturing operations like removing of pinholes smaller than a specified size, removing edge fillets, or adding layers of washer elements around holes. The BatchMesher also uses criteria set by the user to determine the quality index (QI) of a model, uses this QI rating to assess the potential value of each geometry cleanup and meshing tool, and then applies the tools accordingly. QI optimized meshing and node placement optimization are performed to obtain the best quality meshing. Final results are stored in a HyperMesh database file containing both the cleaned-up geometry and the finite element mesh. The required input (element size, quality requirements, etc.), are set within a parameter file and a criteria file. The parameter file contains the average element size and type (quads or trias) as well as any special handling of geometry features. The criteria file contains the target element quality requirements for tests like Jacobian, warpage, etc.
Input to BatchMesher
Geometry data file Any CAD format that can be imported into standard HyperMesh or a HyperMesh database file can be used. Contains average element size, type of elements to be generated (quads or trias), and various options for geometry cleanup. Contains all element quality requirements, such as Jacobian and warpage. You can export this file from the QI panel in HyperMesh after you update the settings to your requirements. Note: as of version 8.0, the Parameter file and Criteria file are both modified by using the BatchMesher Parameter Editor.
Parameter file
Criteria file
Output from BatchMesher

The BatchMesher creates a unique directory for each run in the results directory where it stores output files. The directory is named bm_date_001 (002), etc. For each CAD input file: Inputgeometryfilename_ criteriafilename_ paramfilename.hm This HyperMesh file is the main output of the BatchMesher and contains the geometry (as cleaned up by BatchMesher) and the final mesh.
Altair Engineering

Inputgeometryfilename_ criteriafilename_ paramfilename_res.txt
This is a text file that reports the progress and status of the BatchMesher at various steps in the batch meshing process. It reports information such as the number of surfaces (total, unmeshable, etc.), number of elements, percentage of trias, quality index value, etc. COMPLETE at the end of this file indicates successful completion of the BatchMesher process.
For each run: run_results.txt This is a text file that reports the progress and status of the jobs (CAD files) submitted to the batch meshing process. It reports number of jobs submitted, waiting in the queue, complete etc. For completed jobs it provides summary information such as time taken to complete the job, number of surfaces in the model, number of elements created etc. Maintains a log of submitted runs. This log file can be loaded back into the Batchmesh GUI to review the results at a later time
RunView.log
In addition to the files mentioned above, additional output files may be created due to customization procedures performed at various stages of the batchmeshing process (pre-geometry load, post-batchmesh etc). How do I Start BatchMesher on a PC Start BatchMesher in UNIX

Altair Engineering
To start BatchMesh on a PC:

On a PC, the BatchMesher module can be accessed via the Start menu (Start=>programs=>Altair HyperWorks=> BatchMesher), or from a command line by typing hw_batchmesh with the full path ( ~altairhome\hm\batchmesh\hw_batchmesh). Examples: C:\altair\hm\batchmesh\hw_batchmesh\hw_batchmesh or C:\altair\hm\batchmesh\hw_batchmesh\hw_batchmesh nogui -cad_translator <name of cad translator> -cad_model_dir <directory with path> -cad_model_ext *.<cad model extension> -criteria_file <criteria file path> -param_file <param file path>
Altair Engineering

To start BatchMesh in UNIX:

You can type the hw_batchmesh command to invoke the user interface or hw_batchmesh -nogui to perform the batch mesh without a user interface.

Altair Engineering
BatchMesher Setup
The following steps outline the setup of a batch mesh run. 1. Create a mesh type (Configuration tab): The mesh type consists of a Criteria File and a Parameter File. In the Configurations tab, you can add a new mesh type by clicking: (add new entry) Specify a name, and select the criteria and parameter files (browse to select the criteria and parameter files). Choose the models to batch mesh: Click on the Batch Mesh tab in the interface and choose the Input model directory the directory containing your source files. Click the open-folder icon in the Input model directory: text box, and browse to & select the desired directory (not the files themselves). This sets your default directory when adding files. After choosing the directory, click: (select files ) After the new browser window opens, select the files you want to mesh from the chosen directory, as well as the desired CAD geometry type. Either click the desired files, or use the all or none buttons. You can also click directory to browse to a new folder and select additional model files. Once you have highlighted all of the desired model files, click the select button to close the browser and add the files to the list in the batch mesh tab. Set the mesh type for each model: The selected geometry files displayed in the table along with their geometry type. The same geometry file can be added twice, allowing you to mesh the same file with different mesh types. For each of the geometry files in the table, you choose the mesh type from a dropdown list by clicking the cell for that files mesh type.
2.
3.
4.
5. 6.
For ease of use, you can apply the same mesh type to all files above and/or below the current one by right-clicking and choosing Propagate Up or Propagate Down. This also applies to a blank entry so that you can remove the mesh type by propagating a blank mesh type. Choose an Output directory: Near the bottom of the tab you can choose an optional directory where the BatchMesher will save all results. If no output directory is specified, the results will be saved to the current working (input) directory. Start BatchMesher run: Click Submit. Check run status: Go to the Run Status tab. All runs are listed, along with the status next to each one. Each batch mesh run (which can contain multiple model files) creates a unique directory inside of the output directory, where it stores its meshed results. This unique directory name displays on the Run Status tab. You can obtain the details of a highlighted job within a run that is "complete" or "working", or a summary of the details of all of the jobs within a highlighted run that is "complete" or "working", by clicking on the Details button. You can also cancel or pause runs individually when a job is highlighted, or cancel or pause all of the jobs in a run if the run is highlighted. Paused jobs can be restarted (resumed) immediately (Resume
Altair Engineering

Now) or at a specified later time (Resume At:). Note: A report is automatically generated for all jobs submitted from the BatchMesher user interface and saved in the output directory as run_results.txt.
See also

Altair Engineering
Batch Mesh Tab

This tab or panel allows you to select the geometry files and their corresponding mesh types that you want to mesh.
Geometry source directory:
Enter the directory that contains the geometry/CAD files required for batch meshing or click to use the file browser to pick a directory. Note that you need to select the directory containing the CAD files and not the CAD files themselves. You can choose to select the CAD files in all the subfolders of the selected directory. Once the source directory is specified, click here to select the individual files in the directory to be batch meshed. Use the Shift and control (Ctrl) keys to select or deselect geometry files from the list. Once your selection is complete, click Select to add the highlighted files to the geometry list.
Altair Engineering

All files (of the chosen geometry file type) in the source directory are selected by default. You can repeat the process to add more files from different directories or to add the same files multiple times to generate different sizes/types of mesh. You can also choose a new directory and select the geometry file from that. Allows you to add a new row to the geometry file list (to be batch meshed). You can then select a new geometry file either by selecting it from the source directory or by entering the complete path of the geometry/CAD file. Allows you to remove a row from the geometry file list (to be batch meshed). Result directory: Enter the directory where the BatchMesher result files should be saved or click to use the file browser to pick a directory. The results of the run are saved in a sub-directory named bm_<date>_<run> within the result directory specified on the Batch Mesh tab. For example, a first run on December 15, 2005 will be named bm_051215_001. The next run on the same day would be bm_051215_002. Once the setup is complete, click here to start the BatchMesher run. It automatically takes you to the Run Status tab. You can also choose to start your run at a later time (see next item below). Click here to start the BatchMesher run at a later, specified time. The GUI automatically takes you to Run Status tab. The job status becomes "Waiting" until the specified time, when the run starts. For each geometry file selected to be batch meshed, a Mesh Type can be chosen from a drop down list of mesh types set in the Configurations tab. Left-click in the files Mesh Type cell to invoke the drop-down list. If you wish to mesh all of the geometry files with the same mesh type, you can right-click in the Mesh Type cell and choose either Propagate Up or Propagate Down to apply the same mesh type to all of the preceding or following geometry files. You can also customize the BatchMesher by creating user specific procedures and registering them in the User Procedures tab. Once they are registered, these procedures can then be selected to be performed at one of the three stages of the batch mesh process:
Pre-geometry load:
Before the CAD geometry is imported

Altair Engineering
Pre-batch mesh:
After the CAD geometry is imported but before any geometry editing or meshing. After the batch mesh process is complete.
Post-batch mesh:
Select the user procedures from the drop down list of the corresponding cells. The drop down list is generated from the procedures registered in the User Procedures tab.
Altair Engineering

Configurations Tab
This tab allows you to configure BatchMesher with the CAD translator and mesh types to be used. A mesh type is a name given to a set composed of one criteria file and one parameter file.
Mesh Type
A mesh type is a name given to a set including one criteria file and one parameter file. several different mesh types are available by default: 8mm auto 8mm user Average element size of 8 with one layer of washer elements around holes whose width is determined by the batchmesher Average element size of 8 with multiple layers of washer elements around different size holes and width of individual washer layers is specified by the user
10mm auto Average element size of 10 with one layer of washer elements around holes whose width is determined by the batchmesher 10mm user Average element size of 10 with multiple layers of washer elements around different size holes and width of individual washer layers is specified by the user 12mm auto Average element size of 12 with one layer of washer elements around holes whose width is determined by the batchmesher 12mm user Average element size of 12 with multiple layers of washer elements around different size holes and width of individual washer layers is specified by the user 15mm auto Average element size of 15 with one layer of washer elements around holes whose width is determined by the batchmesher 20mm auto Average element size of 20 with one layer of washer elements

Altair Engineering
around holes whose width is determined by the batchmesher File browser that can be used to select a new criteria or parameter file.
Allows you to add a new mesh type. You can give the new mesh type a name and browse for a criteria or parameter file. You can also enter the complete path of these files in the corresponding fields. Allows you to remove a mesh type from the list.
Invokes a BatchMesher Parameter Editor which allows you to set various options available in the criteria file and parameter file. Note that you may not be allowed to change the default parameter and criteria files from the installation due to write permissions.
Altair Engineering

Run Status Tab

Once the run is initiated in BatchMesher, this tab allows you to obtain the status of the run. Each run is listed as a sub-directory in a tree, along with the exact path of the results location. Each geometry file is listed in the subdirectory along with its mesh type and the status of the run.
The Status can be posted as one of the following: Working Pending Batch meshing is currently being performed on this CAD model. This model is currently in the queue and has not started the BatchMesher process yet. The models in the status can be canceled if necessary. The job will begin automatically at a user-specified date and time. The batch meshing process is complete, and results can be reviewed.
Waiting Done
The following tasks can be performed in the Run Status tab: LoadMesh Click here after highlighting/selecting the appropriate model row to review the mesh generated by the BatchMesher. This function can only be performed on models that show a status of Done (complete). This function invokes interactive HyperMesh with the final batch meshed model. It also loads the appropriate criteria file in the QI panel so that when the users check the quality of the model it represents their meshing requirements set in the BatchMesher.

Altair Engineering
Details
Click here after highlighting/selecting the appropriate model row to obtain more details on the status of the BatchMesher job. This will display a results text file for the appropriate model.
The details shown include: Complete path of the CAD/Geometry model file(s). Complete path of corresponding criteria and parameter files. Element size. A table containing the number of surfaces (faces, splines), elements, number of surfaces that failed to mesh, number of surfaces with a poor quality mesh (bad mesh), number of elements that failed quality index (QI) and the QI value of the model. All of the above parameters are written at certain steps in the batch mesh process. Current step in the BatchMesher process (allows you to Refresh the details to obtain the latest status). Final status of the run. COMPLETE or ERROR at the end of the details indicates either a successful completion or the errors that caused a failure. Checking the Auto Refresh option will repeatedly update the details window with the latest step details while the job is running. Run Details Provides a summary of the status of all the jobs in the selected run, as well as: The number of jobs completed, in process and waiting. For completed jobs, it lists each one of them with statistics such as time required to complete that job, final number of faces/surfaces/elems, and the quality index.
Altair Engineering

Pause
Click here to pause the jobs that are pending.
Resume Now Starts jobs that have been previously paused. Resume At Cancel Allows you to set a specific date and time for selected, paused jobs to resume. Highlight the intended run (file) and click Cancel to remove it from the list of runs the BatchMesherwill perform. You can cancel runs that are Pending or Working.

Altair Engineering
User Procedures Tab

This tab allows you to customize the BatchMesher by registering user-specific topiclinks (TCL) in three different stages (Pre-geometry load:, Pre-batch mesh:, and Post-batch mesh:) for each model/job and two stages per run. A user procedure can be registered by giving a name and the corresponding tcl file that contains the procedure (TCL topiclink).
Name
A name given to the topiclink or user procedure. A nastran export procedure which is run as a Post-batch mesh: operation is available by default. File browser that can be used to select a new tcl file contains the procedure or topiclink.
TCL Procedure
Once a TCL file is loaded, a drop down list of all of the procedures in that file is provided to choose the required procedure. This allows you to add a new procedure.
Allows you to remove a procedure from the list.
Pre-geometry load:
Select from drop down list of procedure names to choose to run as soon as the BatchMesher is invoked and before loading the CAD geometry.
Altair Engineering

Pre-batch mesh:
Select from drop down list of procedure names to choose to run as just before the BatchMesher starts to mesh the loaded CAD geometry. Select from drop down list of procedure names to choose to run after the BatchMesher complete the meshing and just before you exit the BatchMesher. Use the drop-down list to pick a procedure name to be executed before the first model/job starts. Use the drop-down list to pick a procedure name to be executed after the last model/job completes batchmeshing.
Post-batch mesh:
Pre-run
Post-run

Altair Engineering
BatchMesher Customization
The BatchMesher can be customized, through TCL procedures, to meet your specific needs. See the User Procedures Tab for more information. For example, the customization of BatchMesher could allow you to: Export a mesh in solver format. Generate the midsurface of a thin solid geometry. Perform a surface offset to move the sheet geometry to a midplane location. Name and number parts to user-specific requirements. The BatchMesher has built in provisions to perform user-specified procedures at the following steps for each job: Pre-geometry load: This procedure will be run right after the batch meshing process begins, before the selected model is imported. This procedure will be run right after the selected geometry model is imported (a midsurfacing procedure or surface offset can be performed at this point). This procedure will be run after the batch mesh is complete. Examples include creating solver-specific property cards, or exporting the mesh in a solver format.
Post-geometry load:
Post-batch mesh:
Customization can also be performed at the run level. This enables users to perform operations such as reading all the batch-meshed parts into a single model, creating properties, materials etc, or creating connections such as welds between the parts. Customization options at the run level can be set to execute at two points in the batch mesh process: Pre-run Post-run This procedure will be executed before the first model/job starts. This procedure will be executed after the last model/job completes batchmeshing.
Example post-mesh user procedure: This example exports the generated mesh to a NASTRAN model. The NASTRAN output file created is named Input_geometry_filename.dat. # args from BatchMesh is input file name proc nastranexport {args} { set modelName " batchmesh_nastranoutput"; if {[llength $args]>0} { set modelName [lindex $args 0]; } set template_dir [ hm_info -appinfo SPECIFIEDPATH TEMPLATES_DIR] set template [file join $template_dir "feoutput" "nastran" "general"]
Altair Engineering

*feoutput "$template" ${modelName}.dat 1 1 1 }

Altair Engineering
User-registered Procedures
User-registered procedures can be invoked using two different methods. The first method is via an additional Tcl script. This method is compatible with 7.0. 1. Create a temp file (e.g. /tmp/driver.tcl). The file should contain: set userproc(<event name>) {"<tcl file name> " "<procedure name>"} For example: set userproc(POST_BATCHMESH) {"/usr/bm/userproc.tcl " "myproc"} 2. Add the following command line argument: -user_proc_file <Tcl file> For example: hw_batchmesh nogui cad_translator catia criteria_file /data/mycriteria. txt param_file /data/myparams.txt cad_model_dir /data/ -cad_model_ext "model" -user_proc_file /tmp/driver.tcl
The second method does not require creating an additional Tcl script. Instead, all of the required parameters are included in the -user_procedure option of the hw_batchmesh command: -user_procedure <proc_type> Specifies the type of user-registered procedure. Valid values for include: PRE_GEOMETRY_LOAD PRE_BATCHMESH POST_BATCHMESH The complete path to the Tcl script file containing the user specified <proc_name> procedure. The name of user-registered procedure. The list of additional arguments to pass to <proc_name>. This can be empty if no additional arguments are needed. Quotes must be used if the list contains more than one argument.
<file_path> <proc_name> <args>
The -user_procedure option can be used multiple times in in one hw_batchmesh command, once for each proc_type. For example: hw_batchmesh nogui cad_translator catia criteria_file /data/mycriteria. criteria param_file /data/myparams.param cad_model /data/mymodel.model user_procedure PRE_GEOMETRY_LOAD /data/mytcl.tcl myprocedure "myarg1 myarg2" -user_procedure POST_BATCHMESH /data/NastranOutput.tcl nastranexport The following model-specific variables can also be used within user-registered procedures: Variable Name Description
Altair Engineering

::hwbm::gVarArray(modelpath) ::hmbm::gVarArray(modelname) ::hmbm::gVarArray(cadtype) ::hmbm::gVarArray(criterpath) ::hmbm::gVarArray(critername) ::hmbm::gVarArray(parampath) ::hmbm::gVarArray(paramname) ::hmbm::gVarArray(outpath)
Contains the complete path to the input CAD file. Contains the name of the input CAD file. Contains the type of CAD file. Contains the complete path to the criteria input file. Contains the criteria input file name. Contains the complete path to the parameter input file. Contains the parameter input file name. Contains the complete path to the directory with all output files. It is the same directory as specified if the work_dir option is used. Contains the output result file name.
::hmbm::gVarArray(resfilename)
::hwbm::gVarArray(outmodelname) Contains the output CAD file name.
It is important to remember to save the model after running user procedures, as this is not done automatically. For example: hm_answernext "yes" *writefile "$::hmbm::gVarArray(outmodelname)" 0

Altair Engineering
BatchMesher Parameter Editor

Criteria and parameter files allow users to set the appropriate parameters/options to obtain the desired mesh from the Batchmesher. The Parameter and Criteria Editor is an easy-to-use interface that allows you to create and modify parameter files as well as geometry cleanup criteria. Access the editor in BatchMesher from the Configuration tab by clicking the entry of the configuration you wish to modify and then clicking the edit file button. HyperMesh uses the same editor for both types of file, but the editors layout changes depending on whether you are working on a parameter file or a criteria file. See Editing Criteria Files and Editing Parameter Files for details.
Altair Engineering

Editing Parameter Files

The criteria & parameter editor displays all parameters on one tab, with drop-down/expanding frames for each class of parameters. In the image below, these sections are fully expanded.

Altair Engineering
Altair Engineering

For descriptions of the options in this editor window, consult the following topics: Basic Options: Target Element Size, Import Model Tolerance, Extract Midsurface Geometry Cleanup Options Create Mesh Options Special Component Selection Options

Altair Engineering
Basic Options: Target Element Size, Import Model Tolerance, Extract Midsurface
Target element size The desired element size for meshing and optimization. Note: The element size set here should match the ideal value for min length and max length criteria set in the criteria file. If it doesnt match, the BatchMesher may not be able to produce meshes that adhere to the target quality requirements
Import model tolerance The tolerance value to be used while importing the CAD model. Set this to auto to let the Batchmesher choose the tolerance based on the type and dimensions of the model imported. Extract midsurface Turn on this option if your model uses thin solid geometry to represent sheet metal parts, and you want Batchmesher to detect such parts and create midsurface geometry. The resulting midsurface geometry will be batch meshed, while solid geometry will be ignored. Batchmesher generates midsurface geometry by offsetting one of the sides of the solid. Thus, this functionality is only appropriate for stamped partsnot for machined or molded parts or castings. When active, this option enables another one: sheet metal only. Activating this second checkbox enables several more parameters specific to sheet metal midsurface extractions: Maximum thin solid thickness to width ratio: This is the maximum ratio between the approximate thickness of the thin solid part (shortest dimension) and its approximate width (2nd shortest dimension). This parameter is used to limit the midsurface extraction to parts for which the thickness is clearly smaller than the length and width Maximum thin solid thickness: Midsurface extraction ignores thin solids with thickness less than this value. Minimum feature angle between the solids edge and its faces: The minimum angle used to distinguish top and bottom faces of a thin solid from its sides. Angles less than this will be treated as if they were flat for purposes of midsurface extraction.
Altair Engineering

Geometry Cleanup Options

Geometry Cleanup allows the Batchmesher to perform a variety of geometry feature recognition and preparation tasks. This is one of the main functions of Batchmesher and should be turned on by default. You can choose to turn off this option if you have already performed manual geometry cleanup and only wish to mesh the part. You can turn on/ off cleanup of individual features such as holes, fillets etc. The individual options available in geometry cleanup are:
surf hole recognition
When this option is turned on, you can distinguish holes of different sizes and treat them appropriately. You can add radius ranges in the table and choose one of the following: Remove the holes Maintain a node at center (mark) Add a tag on one of the nodes of the hole Force a minimum number of nodes around the holes (for finer mesh) Add one or two layers of washers to be created Specify width of the washer as a constant value or a scale of the holes radius, or let Batchmesher determine the width Set higher priority to one range of radii over others. For example, if you wish to ensure all bolt holes (radius 10-15) have correct washers but other holes arent critical, holes with radii 10-15 will receive higher priority than others. This ensures that if two holes close to each other in the model have overlapping/conflicting washers, the hole with higher priority gets the washer while the other does not.
use file for holes
Sometimes certain holes need special treatment. This option allows users to provide a file with X, Y, Z locations of these special holes. The Batchmesher compares these locations to the holes in the jobs models, and prioritizes the holes that match. All the options for surface hole treatment are available for these holes. This option is valid for parts that form an enclosed volume. The cylindrical surfaces that form holes in these solids are recognized and treated as follows: Remove the holes Maintain node at center (mark) Add tag on one of the nodes of the hole Force a minimum number of nodes around the holes
solid hole recognition

Altair Engineering
surface fillet recognition
When this option is turned on fillet surfaces are recognized to be able to perform on or more of the following options: Prevent the main (long) edges of the fillets from being suppressed and also prevent the nodes of those edges from moving while fixing element quality Specify the number of elements across the width of the fillets for given fillet radii Specify the chordal deviation to be achieved while meshing
flange recognition
This option allows users to recognize geometry that represent flanges on sheet metal parts. Users can specify the minimum number of elements to be created along the width of the flange, and provide the minimum and maximum width of the flanges in their design process to recognize flanges correctly. Turns on bead recognition and provides the option to suppress any beads with heights less than a specified value.
suppress beads
preserve rounded bead Enforces node placement along the midline of a rounded bead. midline suppress flanged holes When active, holes with small downward flanges will be recognized and those whose height is less than the specified value can be eliminated. edge fillets This option allows users to remove any fillets/rounded edges located on free edges and having radii below a specified value. Small geometric features with specified size that represent company logos can be removed with this option.
remove logos
Altair Engineering

Create Mesh Options

This option allows the Batchmesher to generate mesh on the cleaned-up model geometry. This is one of the main functions of Batchmesher and should be turned on by default. You can choose to turn off this option if you only want to perform geometry feature recognition and cleanup, and will mesh the model manually later. When this option is turned on the following parameters need to be set: element type mesh flow:align mesh flow:size Type of elements to be created mixed, quad or tria. Produces a more orthogonal quad dominated mesh. Enforces the global mesh element size with minimal min/max element size variation. Choose whether to create First or second order elements. Newly created elements can be placed in either the current component or original surfaces component. After the surfaces are appropriately meshed, the nodes are optimized to improve element quality while maintaining geometry features. the smoothing options available are: None (no smoothing). Smooth only nodes that are within surfaces. The nodes on the edges of the surfaces are not moved. Smooth nodes along edges. This option also smoothes nodes within a surface. Nodes on the edges of surfaces are allowed to move along the edge to improve element quality. Smooth nodes across edges. This option also smoothes nodes within a surface. Nodes on the edges of surfaces are allowed to move along the edge, and across the edge to the neighboring surface if needed, to improve element quality correct features: move across shared edges, max dist correct features: move across free edges,max dist correct warped elements: offset nodes from surfs, max dist correct warped Allows the nodes to move a certain distance across or away from the geometry shared edge by less than the predefined distance
element order place elements in
optimized smoothing
Allows the nodes to move a certain distance across or away from the geometry free edge by less than the predefined distance
Allows the nodes to move off the surface to meet the warpage criteria defined in the criteria file. The distance specified is the max distance the nodes can move off the surface. Allows quads to be split into trias to meet certain element criteria as

Altair Engineering
elements: divide quads into trias feature angle
defined in the criteria file.
The minimum angle to be maintained (rather than flattened) while performing element cleanup. Elements whose angle exceeds this value are considered folded over, and Batchmesher attempts to clean them up.
folding angle
Altair Engineering

Special Component Selection Options

This option is used to handle two types of situations: 1. When the model contains multiple parts of which not all are to be batch meshed. In that situation the names of the components that must be exempt from geometry cleanup should be listed, with this option turned on. The Batchmesher will still mesh those components but will not perform any geometry cleanup before meshing. The remaining components that are not specially listed will be batch meshed with the normal process, including geometry cleanup. 2. When a user prefers to mesh his parts with multiple element sizes but still wants to maintain the transition at the common edges of the different sizes. In this case users should batchmesh one component with one parameter file, with this option turned on. Then, they should batchmesh the other component with a second mesh type, again with this option turned on. For example: imagine you have a model in which you have two componentsfront_10 and rear_20which share common surface edges, and you intend to mesh front_10 with element size 10 and rear_20 with element size 20. You can accomplish this by performing these steps: 1. First create two sets of parameter/criteria files: One with target element size of 10 and the appropriate parameters. In this parameter file turn on the special component selection option Mesh selected components while maintaining connectivity to external mesh, and list front_10 in your component list. A second file with target element size of 20 and the appropriate parameters. Turn on the same special component selection option in this second parameter file, and list rear_20 in the component list. 2. Secondly, create a mesh type (name it varyingsize) and assign the first set of criteria and parameter files. Create a second mesh type with the same name (varyingsize) and assign the second set of criteria and parameter files. Third, choose the geometry file to be batch meshed, assign it the varyingsize mesh type, and submit the job. This will mesh front_10 first with the first mesh type, and then take the results of this and mesh rear_20 with the second mesh type, while maintaining connectivity with the mesh created on front_10 by the first run.
3.

Altair Engineering
Editing Criteria Files

This window allows you to load and save Quality Index criteria files, as well as view and modify their contents. Note this editor is the same feature found in HyperMesh on the 2D page, quality index panel page 3, edit criteria button.
The editor is a completely separate window from the rest of the HyperMesh environment, floating above the rest of the interface.
The active criteria files details display in a table format Use the file menu inside the criteria file editor window to: load a different criteria file save changes to the current criteria file save the current settings as a new criteria file exit (close) the editor The criteria file editor organizes quality criteria in a table format, with each check displayed in a vertical list and the controls and values associated with it listed to its left.
Altair Engineering

You can edit each of the numerical values displayed in the editor. You can also choose whether or not to use each check for element quality criteria by checking or clearing the checkboxes for each quality check listed. Click advanced criteria table to access more settings for each check, including the different quality levels ("good", "pass", "fail", etc.) Finally, you can choose different solvers calculation methods for some of the checks such as aspect ratio or warpage, simply by picking the desired solvers from the list boxes. Note, however, that in order to use more than one solvers methods, you must select individual methods from the list box on the checks line of the table. Different solvers methods are described in the topic How Element Quality is Calculated. Use the command buttons at the bottom of the window when finished editing: Click Apply to make HyperMesh start using the current criteria settings (including any changes that you have made). Click OK to make HyperMesh start using the current settings and close the editor. Click Cancel to close the editor, discarding any changes you made to the criteria.
Element Check Settings window quality index panel

Altair Engineering
hw_batchmesh
The hw_batchmesh program provides an interface for the HyperMesh BatchMesher features. You can call this program directly in graphical user interface mode, or in batch mode using the nogui option. Syntax Arguments hw_batchmesh arguments -cad_translator <type> Specifies the CAD file type. Legal values for "type" include: ug | catia | iges | hm | hma | proe | step. Complete path to the criteria input file. Complete path to the parameter input file. Complete path to a single CAD input file. Complete path to a directory where files of the given CAD type exist. File extension to use when scanning the cad_model_dir for CAD input files. OPTIONAL - The boolean flag that specifies to get geometry files from sub-directories of the given cad_model_dir. Default is false. OPTIONAL - The tcl file with procedure specified in run_tcl_proc. NOTE: If run_tcl_file option is given then all other options except run_tcl_proc are ignored. This option will invoke tcl procedure specified in run_tcl_proc option. -run_tcl_proc <proc_name> OPTIONAL - The name of tcl procedure from file specified in run_tcl_file option. NOTE: The run_tcl_proc option is required if run_tcl_file option is selected. -user_proc_file <file_path> OPTIONAL - The tcl file with set of command to specifying user-registred procedures. This option is deprecated and not recommended for new development. The user_procedure option may be used for user-registered procedures invoking. See User-registered Procedures.
-criteria_file <file_path> -param_file <file_path> -cad_model_file <file_path> -cad_model_dir <dir_path>
-cad_model_ext <file_ext>
-recurse
-run_tcl_file <file_path>
Altair Engineering

-user_procedure <proce_type> OPTIONAL List of parameters: <file_path> <proc_name> <proc_type> - Specifies the type of user<args> registered procedure. Legal values for "proc_type " include: PRE_GEOMETRY_LOAD | PRE_BATCHMESH | POST_BATCHMESH. <file_path> - Complete path to tcl script file with user specified procedure. <proc_name> - The name of user-registered procedure. <args> - The list of arguments for userregistered procedure. Can be empty. Use back quotes if list contains more then one argument. The user_procedure option can be repeatedly used in one hw_batchmesh command. (one time for each proc_type). Also see User-registered Procedures. -work_dir <file_path> OPTIONAL - The directory where the BatchMesher will run. If not specified, the current working directory is selected. OPTIONAL - If not specified, the user interface of the BatchMesher is launched. OPTIONAL - Display usage information.
-nogui
-help Returns Examples 0 on success, "other" on failure.
hw_batchmesh nogui cad_translator catia criteria_file / data/mycriteria.txt param_file /data/myparams.txt cad_model_file /data/fender.model Runs the BatchMesher (without any user interface) on the CATIA geometry in file/ data/fender.model using specified parameter and criteria files. hw_batchmesh nogui cad_translator catia criteria_file / data/mycriteria.txt param_file /data/myparams.txt cad_model_dir /data/ -cad_model_ext "model" Runs the BatchMesher (without any user interface) on all the CATIA geometry in files with the extension .model in the /data/ directory using specified parameter and criteria files. hw_batchmesh

Altair Engineering
Invokes the BatchMesher user interface where you can set up the required entries interactively. hw_batchmesh nogui cad_translator iges criteria_file / data/mycriteria.txt param_file /data/myparams.txt cad_model_dir /data/ -cad_model_ext igs recurse true Runs the BatchMesher (without any user interface) on all the IGES geometry in files with the extension .igs in the /data/ directory (and all of the subdirectories inside of it) using the specified parameter and criteria files. Comments The cad_model_file option cannot be used with the cad_model_dir and -cad_model_ext options. The cad_model_dir and -cad_model_ext options must be used together.
Altair Engineering

BatchMesher Error Codes

The following error codes may be encountered in BatchMesher: Code 101 102 103 Description Wrong count of arguments for the hw_batchmesh script. Used only in the command line. Missing major arguments for hw_batchmesh script. Used only in the command line. The specified output directory does not exist. (See work_dir option in hw_batchmesh hw_batchmesh). Used only in the command line. Undefined major environment variable. The specified input directory contains no model files (see -cad_model_dir in hw_batchmeshhw_batchmesh). Used only in the command line. The custom pre/post-run tcl script contains an error. At least three critical errors occurred during the meshing of one model. HyperMesh executable file (hmopengl) is in the wrong path or inaccessible. Wrong input geometry file path or file inaccessible during running hw_batchmesh script. Wrong criteria file path or file inaccessible during running hw_batchmesh script. Wrong parameters file path or file inaccessible during running hw_batchmesh script. Either the time_limit.txt or result (*_res.txt) file was not created after the specified timeout (10 minutes by default). Result file (*_res.txt) not found. Error while reading the time_limit.txt file. Abnormal termination of HyperMesh (hmopengl) process (possibly crashed). The HyperMesh (hmopengl) process is frozen (possibly waiting for user input). Wrong input geometry file path or file inaccessible from HyperMesh (hmopengl) process. Wrong criteria file path or file inaccessible from HyperMesh (hmopengl) process. Wrong parameters file path or file inaccessible from HyperMesh (hmopengl) process. Error in HyperMesh geometry file or wrong file (see *readfile command)
104 105
106 107 111 112 113 114 121
132 133 134 135 141 142 143 144

Altair Engineering
145 146 147
Error while importing of geometry file, or wrong file (see *feinput command) Error reading the criteria file (see *readqualitycriteria command) Error while running hw_batchmesh command. (See hw_batchmesh command and required arguments.) Custom (Pre-Geom, Pre-Mesh, Post-Mesh) script error. Licensing error (the feature you are trying to access is not supported by your license).
148 151
Altair Engineering

Grid Computing with BatchMesher

BatchMesher supports grid-based computing; the default grid is "PBS Pro". The "Grid" option is disabled by default in the BatchMeshers base configuration (loaded from the hw_batchmesh.cfg file). To enable BatchMesher grid computing, select Load Config from the File menu and load the file hw_batchmesh_grid.cfg. This file is installed in the path: InstallationRootPath/altair/hwX.X/hm/batchmesh (for UNIX), or InstallationRootPath\altair\hwX.X\hm\batchmesh (for Windows) Where "X.X" is a number representing your HyperWorks version number (e.g. 7.1, 8.0, etc). After loading hw_batchmesh_grid.cfg, the Grid option displays alongside local in the File menus Run Options sub-menu. Once this option is activated, it will remain even if you load one or more subsequent different configuration files. To use the Grid option, you also need to modify/configure three default scripts: qsub.tcl, qstat.tcl, and qdel. tcl (all of which can be found in the same directory mentioned above). The exact script configuration depends on the grid system you use, and requires detailed knowledge of your current grid system. The three default scripts (qsub.tcl, qstat.tcl, qdel.tcl) were created for use with Unix PBS Pro clusters and will work without modification if your cluster configuration is similar to the default configuration. These scripts are described below:
Qsub.tcl
This script creates a node-side script and submits the job to the computing grid. Format: qs ub. t c l - bat c h_ar gs { BATCHARGS} - wor k _di r W ORKDI R BATCHARGS is a command line for one batchmesh job contained in curly braces. This line is created by BMGUI, and has to be written to the node-side script). WORKDIR is the path for all result files. If an error is encountered at job submission, this script returns the word "error". Otherwise, it returns the unique JobID for the submitted job. Command: qs ub. t c l - bat c h_ar gs { / hom es / x s er v e1c / u/ us er nam e/ hw8. 0/ al t ai r / s c r i pt s / hw_bat c hm es h - nogui - c ad_t r ans l at or hm c r i t er i a_f i l e / hom es / x s er v e1c / u/ us er nam e/ Conf i gs / nv h10. c r i t er i a - par am _f i l e / hom es / x s er v e1c / u/ us er nam e/ Conf i gs / nv h10. par am - c ad_m odel _f i l e / hom es / x s er v e1c / u/ us er nam e/ M odel s / m odel . hm - nobg } - wor k _di r / hom es / x s er v e1c / u/ us er nam e/ Bat c hm es hRes ul t s / bm _060209_001/
Returns:
Example:

Altair Engineering
Return: server1.1234
Qstat.tcl
This script gets status information for jobs with specified JobIDs Format: qs t at . t c l J OBI Dl i s t
Where JOBIDlist is list of unique JobIDs for submitted jobs. Returns: A list of JobIds paired with Status mnemonics: "R" job is running "Q" job is queued, eligible to run "E" job is exiting after having run "W" job is waiting for idle resource "U" status undefined (if status not one of "R", "Q", "E" or "W") "none" information about job with JOBID was not found on GRID server. Example: Command: qs t at . t c l Return: 1234 none 1235 R 1236 R 1239 Q 1234 1235 1236 1239
Qdel.tcl
This script terminates jobs with specified JobID's. Format: qdel . t c l J OBI Dl i s t
Where JOBIDlist is a list of JobIDs for the submitted jobs Returns: 0 if the jobs terminated without errors, or
Altair Engineering

"none" if jobs can not be terminated (or termination error) Example: Command: qdel . t c l 1236 1248
Return: 0

Altair Engineering
Connectors
Connectors are special entities that define how different components or assemblies in the model are fastened to each other, including the connectors' degrees of motion and structural strength.
For more detail, see: Connector Entity Connector Definition Connector Terminology Connector Location Connector Realization Connector Rules Connector State Link Entity State Link Entity Number of Layers Re-connect Rules Connector Review Connectors User Control Mode Master Connectors File Multiple Weld File Format Spotweld Interface Import Templates FE Configuration File FE Definition Examples
Altair Engineering

Connector Entity
Connectors are geometric entities (not FE) used to create connections between components. Connectors are used to realize FE idealizations of the physical connection. Just as you create an FE mesh on a surface, you create FE connections by realizing a connector. The characteristics of connector entities can be divided into four categories: Connector Terminology Connector Definition Connector Realization Connector Review
Connectors are created and modified within the Connectors Module.

Altair Engineering
Connector Definition
The connector is simply a database of information defining a specific request for connection at a specific location. A connector definition describes the connector between multiple entities at a specific location. Entities that are to be connected are referred to as link entities. The connector location can be defined as a node or node list, a geometric point, a line or line list, a surface, or even as elements. In the following example, there are two components (Top and Bottom) that are to be connected at the location of a point (with an id of 10). In this case, both components are considered to be link entities, since they are to be linked together. The point defines the location of the connector.
After a connector is created, the connector icon is placed at point 10, and components 1 and 2 are incorporated into the request for connection. The following diagram shows the connector after it is created (with an id of 7) at the location of point 10 (point 10 is not visible).
Altair Engineering

In this example, connector 7 has been defined and no welds have been created. The connector stores the following information: Which link entities the request for connection is to connect (Comp 1 and Comp 2) The thickness of the realization (Thickness = 2) Where to connect the link entities (the connector's current location) HyperMesh entities currently supported as link entities include ASSEMS, COMPS, ELEMS, SURFS, NODES, and TAGS. Any number of link entities of differing types can be added to a connector in any order. The connector sets the order of link entities during the realization process. The example above is a simple case where we have added two link entities of the same type (COMPS) to a single connector. For more detailed cases of connecting assemblies, see Example of Connecting Assemblies. Note: An element-to-tag-to-component connector is possible, as is any other combination of the supported link entities.

Altair Engineering
Example of Connecting Assemblies

The projection behavior is illustrated with the following example. Suppose we have two assemblies [Assem 1 and Assem 2] each having two components [Assem 1 having Comp 1 and Comp 2, Assem 2 contains Comp 3 and Comp 4] in the model file. Create a Connector with the Links as [Assem 1 and Assem 2] with number of layers set to 3. (This case creates a a 3T connection with 2 links.) During Realization the closest found components residing inside the 2 assemblies will be retained as the component links. Inside each assembly a closest component to the connector is determined to satisfy a 2T connection and for the third layer (3T) the closest component to the connector in either of the assembly links is utilized.
Altair Engineering

Connector Terminology
Connector Location Connector Realization Connector Rules Connector State Link Entity State Link Entity Number of Layers Re-connect Rules

Altair Engineering
Connector Location
This is the position in space at which a connector entity is created. The valid entities that can be used to define the connector location depend on the connector type, as shown below:
Spots
nodes The connector icon is created at the node location. The connector icon is created at the point location. The connector icon is created at the center of the selected line. Only one connector is created for each line, but the line may be split into multiple projection locations as specified by the offset, spacing, and density values. The nodelist can be considered as to be a line. The treatment is absolutely the same.
points
lines
nodelist
Bolts
nodes The connector icon is created at the node location. The connector icon is created at the point location. The connector icon is created at the center of the selected line. Only one connector is created for each line, but the line may be split into multiple projection locations as specified by the offset, spacing, and density values. This connector is only used for repetitive holes in a certain, constant distance along the selected line.
points
lines
Seams
lines, linelist The connector icon is created at the center of the
Altair Engineering

selected line. Only one connector is created for each line, but the line may be split into multiple projection locations as specified by the offset, spacing, and density values. nodelist The nodelist can be considered as to be a line. The treatment is absolutely the same.
Areas
elems The connector icon is created at the elements location. Only one connector is created for each group of elements, but the area may be subdivided into multiple projection locations as specified by the nodes of the selected elements. The area can be remeshed to get different projection locations. surfs The connector icon is created at the surface location. Only one connector is created for each surface, but the area may be subdivided into multiple projection locations as specified by the mesh type and element size values. The area can be remeshed to get different projection locations. linelists One connector icon is created for each line. The line is extruded to an area considering the width and the offset values. The area may be subdivided into multiple projection locations as specified by the mesh type and element size values. The area can be remeshed to get different projection locations. nodepath The nodelist can be considered as to be a linelist. The treatment is absolutely the same.
Masses
nodes The connector icon is created at the node location.

Altair Engineering
points
The connector icon is created at the point location.
Altair Engineering

Connector Realization
During connector realization, welds are created using the connector definition. Note: In HyperMesh, the only form of realization currently supported is fe realization (weld creation). For successful realization, the connector must be populated with all the relevant details required for its realization type. For example, fe realization requires the connector to be populated with a projection tolerance and an FE configuration type.
The following diagram shows connector 7 realized with a valid tolerance value, and a config value of type 70 (acm detached).
One advantage of separating weld FE realization from the connector definition, is that a connector can be rerealized as a weld of a different configuration (or possibly, a user-defined weld) without having to redefine the connector. If you edit the connector definition (i.e. add or delete a link entity from the connector), the connector removes the welds it created, and reverts back to an unrealized state. The connector is unrealized only if its user-control mode is turned off. By default, the connector mode is off but it can be turned on by registering custom FE with a connector. Connectors store all FE information that they create, allowing advanced find, mask, delete, and organizational functionality in a number of common panels. If the weld creation is unsuccessful (due to low tolerance, insufficient link entities, etc.) the connector icon is displayed as failed (red). An unrealized connector is yellow, a realized connector is green, and a failed connector is red. Realization can happen by more than one method; see How Realization is Determined for details.

Altair Engineering
How HyperMesh determines realization

Once the connector exists and is ready for realization, HyperMesh offers different routines how the realizations should occur. These different routines primarily affect the spot and seam connector realizations. Not all routines are available in every case; this depends on the selected realization type. The following tree shows a three-stage process used to select the best routine.
In stage 1, the type of realization is considered. If its a realization which doesnt need any node connection and the connection is primarily defined via a solver-specific card, then use the mesh independent option (e. g. CWELDs for Nastran). This option also applies to realizations that use spider elements (e.g. RBE3s) for the head and the tail of the connection (e.g. ACMs in Nastran). In all other cases the mesh dependent option should be used. If the mesh dependent realization is selected, it must be decided in stage 2 whether or not to adjust the mesh or the realization. Adjust mesh means that the projection is done in a perpendicular way, and the mesh has to be adapted to the projection points. Adjust realization means that the mesh will not be modified, at the expense of non-normal or incomplete realizations. In stage 3, decide how the adjustment should take place. The following examples illustrate and explain the different options for realization methods.
Mesh independent:
Altair Engineering

Mesh dependent adjust mesh quad transition:
The quad transition option creates perfectly shaped quad elements around the projection points. This also works for seam connectors. In the examples below, the generated quads are in a medium-blue shade:

Altair Engineering
Mesh dependent adjust mesh remesh:
Altair Engineering

The remesh option takes the projection points into account and performs a pure remesh around these points.
Mesh dependent adjust realization find nearest nodes:

Altair Engineering
The find nearest node option doesnt do any projection and searches for the nearest nodes within the given tolerance only. This makes it possible to easily connect t-joints and similar areas. Its also very useful in situations where the connectors arent positioned perfectly. The realizations are allowed to be non-normal.
Mesh dependent adjust realization project and find nodes:
The project and find nodes option also allows non-normal realizations, but the projection has to be done in the first step. The nodes closest to the projection points will be used for the connection. If the projection is not possible, the realization fails as shown in the second example, where some connectors realized (green) but others did not (red) because they were outside the tolerance.
Mesh dependent adjust realization ensure projection:
The ensure projection option is comparable to the older use shell node option, which is no longer available . When using this option, the minimum condition for the realization is a possible projection. The realization will be performed in the direction from one projection point to the next. If the projection point is coincident with a shell node they will be equivalenced. Note that the difference between this option and the project and find nodes option above is that in this case, the realization passes directly through the connector while the project and find nodes option allows it to merely pass near the connector.
Altair Engineering

HiLock Realization
The HiLock realization can be used for any more or less parallel combination of PSHELL and PCOMP elements. It creates a 1D element construct existing out of RBAR, CBAR and CBUSH elements.
The outer extensions represent the thicknesses of the outer shell elements. The inner nodes of the RBAR element are connected to the shell elements whereas the inner nodes of the CBAR elements are coincident to the shell nodes. Between the appropriate connected and coincident nodes CBUSHes are created. Each outer node connects one CBAR and one RBAR. Each HiLock connection gets an own coordinate system with the z-axis collinear to the HiLock direction. All affected nodes are assigned to this coordinate system, which is taken into account for the DOF definition of the CBAR elements, the stiffness calculation of the CBUSH elements, and the DOF of the node constraint. This realization uses the shell properties and materials (PSHELL or PCOMP) and a predefined HiLock material to calculate the exact position of the outer nodes and the stiffnesses of the PBUSH elements.
Details and Requirements

Certain conditions must be met for reliable realization: The joined shells should be parallel to each other and planar. The fastener should be perpendicular to the shells.

Altair Engineering
The z-axis of the element system, the material system, and the fastener system should be collinear. Stiffness is calculated assuming that the shells are perfectly planar and parallel. Small deviations will produce insignificant changes in predicted stiffness, but larger ones would require a system transformation. The shell elements which share a node with the HiLock (separate for each layer) should have the same properties, same materials, same material orientations, and similar sizes. The attributes of the element upon which the projection falls is assumed to be the same as the other surrounding elements (no averaging method is used.) If attributes necessary for the stiffness calculation are missing, the connector fails and an error message displays in the status bar. The realization requires available nodes near the connector position. If there arent sufficient nodes available, the elements are split at the position of the projection points. However, material orientation is lost when elements are split, so this results in a failed connector in the case of PCOMP elements. Thus, you must define or check the material orientation of any new nodes in this region; once this is complete, a second realization attempt should succeed.
Organization and Definition of HiLock Realization

All HiLock elements (RBARs, CBARs, CBUSHs) created during the realization process are organized into a component named HiLock. The following property collectors are created: HiLock_PBAR_<diameter> : This property collector is created with the PBAR card associated with it. The RBAR elements reference this property. The attributes are calculated depending on the diameter specified in the spot panel during realization. HiLock_PBUSH_<translational stiffness>_<rotational stiffness> : These property collectors are created with the PBUSH card associated with them. The CBUSH elements reference this property. The attributes are calculated depending on a predefined HiLock material and the properties and materials of the connected shells (PSHELL and/or PCOMP). The following load collector will be created: HiLock_SPC6: the SPCs which are created for each HiLock are moved into it. The following system collector will be created: HiLock: the systems created during the realizations will be moved into this collector. If this system collector already exists, any newly created systems will be moved into the same collector. The following material will be created: HiLock_MAT1: This material will be assigned to the PBAR cards. The material is predefined in the HiLock property script: . . . \hm\scripts\connectors\prop_opt_nas_hilock.tcl The predefined values are:
Altair Engineering

set E 1.6e+07 set G 4.7e+04 set NU 0.330 set RHO 8.9e-09 set A 1.7e-05
Calculation of Stiffness in Composite Parts

After summation of bearing stiffness of plies where n = number of plies in the composite plate:
Combined translational bearing stiffness of the joint at ply i location in directions x and y:
Transformed reduced stiffness in x and y-direction for ply i:

Altair Engineering
Where
(theta = angle of orientation for ply i)
And nonzero components of the reduced stiffness matrix for ply i are:
Rotational bearing stiffness in plate-fastener contact:
Altair Engineering

Combined translational bearing stiffness at metallic plate with fastener contact:
Where t = thickness of metallic part E = elastic compression modulus of metallic (isotropic) part v = Poisson's ratio
Rotational bearing stiffness at metallic plate with fastener contact:
Where t = thickness of metallic part E = elastic compression modulus of metallic (isotropic) part

Altair Engineering
v = Poisson's ratio
Altair Engineering

Connector Rules
Connector Rules shape the definition of a connector entity. none The connector is created with no link entities and no thickness defined. In this state, the connector must first be updated with more information before it can be successfully realized. This option requires link entities to be specified before the connector is created. The link entities are added to the connector based on the usersupplied criteria. For this option, the connector only remembers what type of link entity it is to connect, rather than a specific link entity. During the fe realize process, the connector searches the HyperMesh database to generate the best (usually the closest) link entity it can using the supplied information.
now
at fe realize
Note:
The connector rules (connect when:) option is set when creating the connector, or on add links panel.

Altair Engineering
Connector State
The connector state is defined as one of the following types: unrealized The initial definition of the connector entity after it is created. The connector is displayed in yellow. The connector is considered realized only if weld creation at the connector was successful. The connector is displayed in green. The connector is considered failed if the weld creation at the connector was not successful. The connector is displayed in red. The color code provides an easier way to visualize and filter connectors based on their state.
realized
failed
Note:
A connector that was realized can revert back to being unrealized if, for example, a link entity is suppressed from its definition, or the weld element is deleted.
Altair Engineering

Link Entity State

Specifies if the entity referenced by the link entity is meshed or unmeshed. geom Specifies that the entity needs to be connected (welded) using its geometry (connect surfaces only). Specifies that the entity needs to be connected (welded) using its mesh. Both states are applicable to assemblies, components and surfaces only. The elems option connects the mesh on the assembly, component or surface and the geom option connects the geometry on the assembly, component or surface. For all other link entities only the elems state is applicable. The states are added to the connector entity.
elems
Note:
The link entity state options for assemblies, components and surfaces are set when creating the connector, or on the add links panel. The state can be edited/updated in the lower part of the connector browser as well. Therefore the extended information has to be activated in the browser configuration.

Altair Engineering
Link Entity
A reference to a separate entity that can be added to a connector. The entities to which the link entities refer are welded together during realization. The following entities are supported. assemblies Assemblies can be used to connect elements or surfaces. A group of parts that needs to be welded is often represented as an assembly. Components can be used to connect elements or surfaces. A part that needs to be welded is often represented as a component. An element facilitates a patch-patch weld connector. Surfaces can be used to create welds to connect geometry before meshing; the welds create fixed points for the mesh. The connected surfaces may be either meshed or unmeshed. A node facilitates a node-node weld connector. The tag entity can be used to define a weld connector for a node or an element that it holds. Only nodes, tags, elements, surfaces, components and assemblies can be added to connectors. The connectors can hold a single entity or a combination of these entities. The link entity options are set when creating the connector, or on the add links panel. The link entity can be edited/updated in the lower part of the connector browser as well.
components
elements surfaces
nodes tags
Note:
Altair Engineering

Number of Layers
The total number of thicknesses (layers) to connect at the connector. total T Sets the number of thickness to connect (2T/3T/4T/nT) for spots and bolts. This value influences the number of welds or bolts created at a connector, and defaults to "2" for all seam and area connectors. For apply mass connectors a limit for entities can be set, but this is optional. Sets the total number of link entities that can be added to the connector. The number of link entities added to a connector is always less than or equal to the total thickness.
Note:
The number of layers option is set when creating the connector, or on add links panels. The number of layers can be edited/updated in the lower part of the connector browser as well.

Altair Engineering
Re-connect Rules
Defines how a connector should protect its link entity information. none If a link entity references a entity that is removed from the database, the link entity is then removed from the connector. If a link entity references a entity that is removed from the database, the link entity retains the ID of the entity. The link entity remains in the connector. Same as the by id rule except that the entity name is retained. These rules are useful for applications such as part replacement. A part can be added to a connector with the use id or use name reconnect rule and can be replaced with a redesigned part with the same ID or name, without having to change the connector definition.
by id
by name
Note:
The re-connect rule options are set when creating the connector, or on the add links panel. The re-connect rule can be edited/updated in the lower part of the connector browser as well; therefore the extended information has to be activated in the browser configuration.
Altair Engineering

Connector Review
There are many advantages to the way connectors store information. Not only does this local storage allow you to edit the connector definition, it also allows you to review connector details and the quality of the realization. There are a number of tools that can be useful in the review process. The connector visualization controls allow you to update the visual appearance of a connector based on its state, thickness (number of layers), style (connector types), or the component in which it is located. In addition, the visualization controls also allow you to filter the displayed connectors by various criteria (such as thickness). This filter can then be used store the "displayed" connectors for use in other functions. HyperMesh also includes a Connector Browser that contains a list of all connectors and their definitions, as well as a list of connector links . The quality panel allows you to check the quality of welds created from the connectors. The connector database can also be queried through Tcl functions.

Altair Engineering
Connectors User Control Mode

Each individual connector can be placed in a user control mode using either the *CE_SetSpecificDetailById or *CE_SetSpecificDetail commands. This user control mode is most useful for automated Tcl scripts. Once in user control mode, the following procedures are possible for a given connector: Pre-existing FE can be registered as a given connectors realization by using the *CE_FE_Register command. Connectors can be edited without automatically unrealizing (as happens most notably when a link is added or removed from a connector, or when an FE realization entity is deleted). A connectors state can be manually changed from realized to failed, or from failed to realized by using either the *CE_SetSpecificDetailById or *CE_SetSpecificDetail commands. A connectors state will not change to or from the unrealized state using this method. Once a connector is placed into the user control mode, the user control mode remains active until an unrealize command is called (such as *CE_Unrealize), an already realized connector is re-realized, or the user control mode is manually turned off with either the *CE_SetSpecificDetailById or *CE_SetSpecificDetail commands. While a given connector is in user control mode, it may not behave the same as a normal connector. Specifically, there are a number of scenarios where a usercontrolled connector will not auto unrealize in response to database changes that would cause a normal connector to auto unrealize. Note: It is strongly recommended that when FE is registered to a user-controlled connector, that the connector links and other necessary details should also be set with a given connector (so that the connector can properly re-realize if a user interactively requests it to). At the bare minimum, connectors should know which links they are to connect.
Altair Engineering

Master Connectors File

Most of the information stored in the connector entity can be exported to a master connectors file. This file contains connector entity information such as location, link entity, link entity state, link entity rules (see Connector Terminology). The exported file may also contain metadata information stored in the connector. The master connectors file contains welding information at a given location and also assists in the weld automation process. An exported master connectors file can be re-imported using the connectors reader to re-create connectors. The master connectors file is exported in a single format. Master connectors files can have comments beginning with the characters # or $, or there can be blank lines in between. The format of the file is fixed and the order of heading definitions cannot be changed. The column information is includes: Index (ID) Number of Layers X coordinate Y coordinate Z coordinate FE Config FE Type Number of Links Link Type Link ID & Link Name Link State Link Rule METADATA
Notes: The header at the beginning of the file specifies information about the column data. Number of layers defines the thickness to connect at the specified location (X, Y, Z). The data between the brackets are repeated for each link entity. For standard FE types such as ACM and CWELD, the FE Config will have a number of 1001, which defines the user-defined type number specified in FE Config File. The FE Type will be the number defined in the FE Config File (for CWELD it is 72). For a detailed explanation of custom FE Configurations see FE Configuration File. The data between the brackets (link entity information) in the table are repeated for the number of links (NumLinks). The NumLinks variable must be equal to the number of link entities. Metadata is an attribute type that can be stored on a entity. User-defined information (such as Station ID or Gun ID) can be stored on the connector entity as Metadata. The Metadata is defined

Altair Engineering
by a name-value pair and is supported for multiple data types (int, double, string, etc.). The Metadata name is written to the master connectors file in the following format ~<Struct><DataType>Name. <Struct> represents whether the value associated is a single variable or an array. <DataType> represents the type of data stored in the value. For example, a Metadata of name Assembly containing an array of integers is written out as ~AIAssembly. The only delimiter supported in the entire file is the double semicolon "::". The entire column of data in the file should be of the same type. The connectors reader uses the templex template to read the master connectors file. See weld templates for more information. By default, the file is read through the HMIN function call, HMIN_CE_CreateDefined. The connector entity is created with the information specified in the master connectors file and displayed as unrealized (yellow).
Altair Engineering

Multiple Weld File Format

In addition to the master connectors file, the connectors reader also supports master weld file formats previously supported by the spotweld reader.

Altair Engineering
Spotweld Interface
The spotweld feinput translator reads weld information from an ASCII file, such as a Master Weld File. HyperMesh supports multiple formats for master weld files through weld templates. The weld template is specific for a given format. The spotweld translator registers the template through a spotweld configuration file. The currently supported master weld file format templates and the configuration file can be found in the spotweld_format directory. In order to use a different format you must create a weld template and add its name and path to the configuration file. Existing weld templates can be copied and modified to support the new format. The outline of a generic master weld file is provided below: Point ID Layer information (the number of thickness it connects 2T/3T/4T. Max layers supported 4T) Spotweld location (X, Y, Z) Connector part IDs (HyperMesh Component/Part IDs) The delimiter between fields can be ":", ",", " ". ASCII files can have comments beginning with the characters # or $, or there can be blank lines in between. The spotweld translator reads information from the master weld file and stores it in the database. At each of the weld locations, an HM_POINT is created.
Weld Template and Master Weld File Example

The example below helps create a weld template for specific formats. Master Weld File: #Weld format 1. #Point Id:: 1:: Weld Template:
int num header { type "SPOTWELDS" set mark find "[0-9]+::" rewind set num = 0 if { do 1000000 { if
T::
X:: 2::
Y::
Z::
PID1:: 3.000::
PID2:: 4.000: :
PID3:: 12:: 14:: 20::
2.000::
Altair Engineering

{ isdigit } then { set num = sum(num, 1) } readln null } } set numrecords = num set numrequests = 9 requests "ID/T/X/Y/Z/PID1/PID2/PID3/PID4" set numcomponents = 1 components "Value" } record if { do 1000000 { if { isdigit } then isalpha } readln null } } read request // ID qfind "::" set mark read request //T rewind read num qfind "::" read request // X qfind "::" read request // Y qfind "::" read request // Z do num { qfind "::" read request // PID } set num = diff(4, num) do num { read constant 0 // fake PID } readln null }

Altair Engineering
FE Configuration File
The FE configuration file (feconfig.cfg) is used to define custom welds such as ACM (Area Contact Method) and other special types. The weld definition is solver dependant (NASTRAN, LS-DYNA, etc.). The weld definition in the file includes the type of weld to create and the surrounding connector to shells. The specific solver template for the type of weld must be loaded before the welds can be created using a connector entity. By default, the feconfig.cfg file from the <install_directory>/hm/bin directory is loaded in each of the panels related to each connector type (e.g. Spot, Seam, Area, etc). The FE configuration file has a pre-defined format that must be used to define different weld configurations. See FE Configuration Examples for information regarding the format and options for custom weld definition.
Weld Definition Template The weld definition template is shown below:
CFG <SOLVER> <USER_FE_TYPE> <USER_FE_NAME> *filter <FILTER_TYPE > [<FILTER_TYPE>] *style < STYLE_TYPE> <STYLE_NUM> *head <HM_FE_CONFIG> <HM_FE_TYPE> <RIGID_FLAG> *body <BODY_FLAG> <HM_FE_CONFIG> <HM_FE_TYPE> <LENGTH_LOCATION_FLAG> [<DOFS>] [<HM_FE_CONFIG> <HM_FE_TYPE> <LENGTH_LOCATION_FLAG> [<DOFS>]] *post <POST_SCRIPT_NAME>
The template key words and their parameters are defined below.
CFG SOLVER
The key word to start a custom weld definition. The solver template for which FE needs to be created. Supported solvers are: Abaqus, Ansys, LS-DYNA, Nastran, OptiStruct, PAMCRASH, or PAM-CRASH 2G. A unique (with respect to a solver) user defined configuration type id. Customer-defined CFGs should use numbers greater than 10,000 to ensure no collisions with future native HM CFGs. The user-specified name for the FE configuration. The specified
USER_FE_TYPE
USER_FE_NAME
Altair Engineering

name is saved and displayed in the Connector Browser. Note : This should be the first line in the custom weld definition.
*filter
This option can be used to allow only the specified connector types to realize the configuration. For example, *FILTER spot seam indicates that this configuration can be realized only by the spot and seam connector types. In addition, this option is used as a filter when displaying FE configurations in the type = field of respective realize panels. *filter lines also set which panel the CFG is visible in. CE_TYPE The connector type--Spot, Bolt, Seam, Area, etc.
*style
This option indicates that the configurations have specific behaviors associated during realization, and that they are native types. Note: The style definition line for these configurations must not be edited.
For example, *style bolt 1 indicates that this is a bolt connection of type 1 that creates a specific bolted connection between the parts. STYLE_TYPE The connector style name, such as "adhesive", "bolt", "acm", "quad", "continuous", etc. The connector style number: Adhesive: "1" Mesh independent adhesive nodes tie to shells with RBE3/RBE2. "2" Forces shell gap length on. Adhesive (HEXA element) shares nodes with shell at co-incident locations. Bolt: "0" normal bolt: "wagon wheels" in the holes. "1" symmetrical spider bolt. "2" unsymmetrical spider bolt: the middle node is biased towards one hole. "3" cylinder bolt: ties together all nodes within virtual cylinder. ACM:
STYLE_NUM

Altair Engineering
"1" The nodes of HEXA element are shared for consecutive layers (> 2T) and the length of HEXA is average of part thickness. "2" The HEXA elements in consecutive layers have unique nodes and the length of HEXA is average of part thickness. "3" The nodes of HEXA element are shared for consecutive layers and the length of HEXA is the gap distance b/w parts. Quad: "1" Two sets of QUAD4 elements are created, first along projection direction and second at an orientation determined by average part thickness. "2" One set of QUAD4 elements are created at an orientation determined by average part thickness.
*head
The string head is required to specify that a rigid is to be created to connect the weld node to the surrounding shell element. *head lines must be followed with at most one HM_FE_CONFIG line. HM_FE_CONFIG The config for the rigid currently supported. The various types supported are "bar2", "bar3", "equations", "gap", "hex8"(3D), "plot", "mass"(0D), "rigid", "rigidlink", "rbe3", "rod", "spring", "weld", "quad4"(2D seam only), or "penta6"(3D adhesive only). A unique (with respect to a solver) user defined configuration type id defined in the solver template. Defines the number and arrangement of rigids. 0 1 2 3 a single rigid. multiple rigids. multiple rigids to outer shell nodes (for 2D bolt washers only). multiple rigids to outer alternate shell nodes (for 2D bolt washers only).
HM_FE_TYPE
RIGID_FLAG
10 multiple rigids with a 0 length leg connecting with body (for bolt only). 12 multiple rigids to inner and outer shell nodes (for 2D bolt washers only). 13 multiple rigids to inner and outer alternate shell nodes (for 2D bolt washers only).
Altair Engineering

DOFS
The degrees of freedom of the rigid (1-6). This parameter is optional.
*body
The string body is required to specify that a weld is to be created to connect the link entities added to the connector. *body lines may be followed by one or more HM_FE_CONFIG lines BODY_FLAG The body flag is used to calculate the length of the weld. If the body flag = 0, the length is calculated based on the distance between the connecting layers (link entities). If the body flag = 1, the length is calculated based on the average thickness of the connecting layers (link entities). The config for the rigid currently supported. The various types supported are "bar2", "bar3", "equations", "gap", "hex8"(3D), "plot", "mass"(0D), "rigid", "rigidlink", "rbe3", "rod", "spring", "weld", "quad4"(2D seam only), or "penta6"(3D adhesive only). The solver defined type for the HyperMesh config. For example, CBUSH is of config spring and type 6. The type number is defined in respective solver templates and differs, based on the solver.
HM_FE_CONFIG
HM_FE_TYPE
LENGTH_LOCATION_ 0D Element Details: supported values = 0, 1, or 2 FLAG "0" places the 0D element along the proposed 1D element path. If this 0D element is the only config given in the *body, then it is placed at the center of the proposed 1D element path. "1" has the same behavior as "0" except only a single 0D element is created even if multiple bodies are created (as happens in >2T welds). "2" places the 0D element at the connector location. 1D Element Details: supported values = from 0 to 1 (inclusive), 2, 3 "0" forces zero length welds. >"0" but <"1" (such as 0.33 or 0.5) denote a percentage of the distance between shells the length of a given weld should be. To create series welds, all the PERCENT_LENGTH_FLAG variables for a given *body must add up less than or equal to 1.0. "1" forces each body weld to have a length equal to the distance between the shells (which can be used for parallel welds). "2" places the 1D element at the connector location (with both nodes coincident).

Altair Engineering
"3" places multiple (thickness-1) 1D elements at the connector location connected end-to-end (with all nodes coincident). 3D Element Details: supported values = 0 and 1 "0" forces a floating hexa element to have a length equal to half the distance specified by the BODY_FLAG. "1" forces the hexa element's length to be equal to the full distance specified by the BODY_FLAG. DOFS The degrees of freedom (1-6) of the rigid. This parameter is optional.
*post
*post lines are optional, but if specified it must be followed by the name (excluding path) of a valid TCL script with a .tcl extension. This TCL script must be located in the current working directory, the users home directory (UNIX only), or the "scripts/connectors/" directory. This post script will be automatically executed post FE realization and it can be used to edit weld properties, attributes, and other solver specific details.
FE Specification Rules
Each solver will have a specific definition so the same user-defined types can be repeated for each solver. The head and the body definition must begin with a "*" to define rigid and weld definitions. Multiple solid element combinations are not currently supported. Therefore, an ACM can have only one hexa weld element specified in the definition. 1D and 3D element combinations are not supported. The total length of series welds cannot exceed 1.0 (100%). Hence there cannot be three welds specified in series having a length factor of 0.5 (50%) each. Series and parallel weld element combinations are not supported. Series welds are not supported where the link entities are coincident. Series welds are not created when the distance between the connecting link entities is zero. User comments should start with a hash character "#".
Altair Engineering

FE Configuration Examples
Washers CFG nastran 56 bolts *filter bolt *style bolt 0 *head rigidlink 1 1 dofs=123 rigidlink 1 3 *body 0 rigid 1 1 dofs=456
ACM Welds CFG nastran 71 acm *head rbe3 0 0 *body 1 hex8 1 1
The above definition creates ACMs with HEXA8 solid elements as welds and RBE3 elements as rigids. The length of the hexa is equal to the distance between the connecting shell elements. Series Welds CFG nastran 101 series *head plot 0 0 *body 0 spring 6 0.5 spring 6 0.5
The two series welds are created with a length equal to half the distance between the link entities. Series Welds

Altair Engineering
CFG nastran 101 series *head plot 0 0 *body 0 spring 6 0.5
The series weld is created at the center with length equal to half the distance between the link entities. Parallel Welds CFG dyna 101 parallel *head plot 0 0 *body 0 bar2 1 1 bar2 1 1
The bar elements are created at the same location and connect the same link entities. 0-D Welds CFG pamcrash2g 1 plink (ce loc) *head plot 0 0 *body 0 mass 5 2 plot 0 1 *post prop_plink.tcl Supported values for the length location flag are "0", "1", or "2". The behavior for each value is as follows, "0" places the 0-D element along the proposed 1-D element path. If this 0-D element is the only config given in the *body, then it is placed at the center of the proposed 1-D element path. "1" has the same behavior as "0" except only a single 0-D element is created even if multiple bodies are created (as happens in >2T welds) and "2" places the 0-D element at the connector location.
Altair Engineering

Abaqus Connector Types

Abaqus fastener
CFG abaqus 3 fastener *filter spot *head *body 0 rod 13 3 *post prop_fastener.tcl Description: Creates a CONN3D2 element. This realization also the prop_fastener.tcl property script. This script is used while creating Abaqus Fasteners in the spot weld panel. It does the following tasks. Organizes the realized weld elements into their respective components, based upon the link they are connected to. Thus, if a weld is created between comp_1(1) and comp_2(2), the script creates a component collector with the name HM_C_<id> and organizes all the welds created as links between these two components into this collector. This collector is later referenced as the element set while creating the Groups (Interfaces). Creates the following properties/materials collectors: HM_M_<id> : This material collector is created with the *CONNECTOR BEHAVIOR card associated with it. HM_C_<id> : This properties collector is created with the CONNECTOR SECTION card associated with it. It has the above created weld component [HM_C_1_2] associated with it as its Element set, and has the HM_M_<id> material collector associated with it as a weld behavior. HM_P_<id> : This property collector is created with the *FASTENER PROPERTY card associated with it. It has the RADIUS and the DOF values of the fastener inside it. This property is associated to the Fastener Group at a later stage.
Creates Groups (interfaces) with the name HM_G_<id> and with the *FASTENER card associated with it. This interface has its Reference set to the above created element set (HM_C_1_2) and the property associated with it will be HM_P_<id> . It can also show the link elements to which the weld elements are linked via the Automatic_Surface_from_components option. If any System option (Single System ,1- System per layer or 2- Systems per layer) is used in the spot weld panel during realization, this script also creates ORIENTATION systems in the current collector with the name HM_ORI<weld_id>_n<node_id>, organizes the systems created during realization into the respective system collectors, and updates some attributes of each system card. Theses system collectors are then referenced in the above created property collector [HM_C_<id> ].

Altair Engineering
Abaqus acm (equivalenced-(T1+T2)/2)

CFG abaqus 4 acm (equivalenced-(T1+T2)/2) *filter spot *style acm 1 *head rbe3 1 0 *body 0 hex8 1 1 *post prop_abaqus_acm.tcl Description: Creates hexa element with DCOUP3D elements projecting and connecting to the surrounding shell elements. This realization uses the shell thickness to calculate the hexa offset from the shell elements. In the case where the model is a 3T connection, the acm (equivalenced-(T1+T2)/2) realization will join the hexa elements. This realization uses the prop_abaqus_acm.tcl property script. This script is used while creating acm (equivalenced-(T1+T2)/2) / (detached-(T1+T2)/2) /shell gap in the spot weld panel and adhesives in the area panel. It does the following tasks. Organizes the realized weld elements [acm Equivalence-(T1+T2/2)] into the respective components based upon the *HEAD and the *BODY information of the weld. During realization of this configuration type a solid hexa element [C3D8] is connected to the shell elements by the rbe3 elements [DCOUP3D ]. A collector with the name C3D8_comp_<id> is created with the SOLIDSECTION card image associated with it. This component contains all of the solid C3D8 elements which are created during realization. A collector with the name DCOUP3D_comp_<id> is created, containing all of the DCOUP3D elements created as the heads to the weld element.
If this script is called during the realization of adhesives in the Area panel, this script creates the above two components by different names: hexa_comp_<id> for the Hexa elements rbe2_comp_<id> for the rbe elements The script also creates a property collector named prop_<id> , with the SOLIDSECTION card image associated to it. This property collector is referenced to the component containing the Hexa elements created during realization process (i.e. C3D8_comp_<id> in the case of spots, or hexa_comp_<id> in the case of adhesives).
Altair Engineering

Abaqus acm (detached-(T1+T2)/2)

CFG abaqus 70 acm (detached(T1+T2)/2) *filter spot *style acm 2 *head rbe3 1 0 *body 1 hex8 1 1 *post prop_abaqus_acm.tcl Description: Creates hexa element with DCOUP3D elements projecting and connecting to the surrounding shell elements. This realization uses the shell thickness to calculate the hexa offset from the shell elements. In the case where the model is a 3T connection, the acm (detached-(T1+T2)/2) realization will not join the hexa elements. This realization uses the prop_abaqus_acm.tcl property script. This script is used while creating acm (equivalenced-(T1+T2)/2) / (detached-(T1+T2)/2) /shell gap in the spot weld panel and adhesives in the area panel. It does the following tasks. Organizes the realized weld elements [acm Equivalence-(T1+T2/2)] into the respective components based upon the *HEAD and the *BODY information of the weld. During realization of this configuration type a solid hexa element [C3D8] is connected to the shell elements by the rbe3 elements [DCOUP3D ]. A collector with the name C3D8_comp_<id> is created with the SOLIDSECTION card image associated with it. This component contains all of the solid C3D8 elements which are created during realization. A collector with the name DCOUP3D_comp_<id> is created, containing all of the DCOUP3D elements created as the heads to the weld element.
If this script is called during the realization of adhesives in the Area panel, this script creates the above two components by different names: hexa_comp_<id> for the Hexa elements rbe2_comp_<id> for the rbe elements The script also creates a property collector named prop_<id> , with the SOLIDSECTION card image associated to it. This property collector is referenced to the component containing the Hexa elements created during realization process (ie C3D8_comp_<id> in the case of spots, or hexa_comp_<id> in

Altair Engineering
the case of adhesives).
Abaqus acm (shell gap)

CFG abaqus 71 acm (shell gap) *filter spot *style acm 3 *head rbe3 1 0 *body 0 hex8 1 1 *post prop_abaqus_acm.tcl Description: Creates hexa element with DCOUP3D elements projecting and connecting to the surrounding shell elements. This realization does not use the shell thickness to calculate the hexa offset, therefore the hexa will project and be touching the shell elements. This realization uses the prop_abaqus_acm.tcl property script. This script is used while creating acm (equivalenced-(T1+T2)/2) / (detached-(T1+T2)/2) /shell gap in the spot weld panel and adhesives in the area panel. It does the following tasks. Organizes the realized weld elements [acm Equivalence-(T1+T2/2)] into the respective components based upon the *HEAD and the *BODY information of the weld. During realization of this configuration type a solid hexa element [C3D8] is connected to the shell elements by the rbe3 elements [DCOUP3D ]. A collector with the name C3D8_comp_<id> is created with the SOLIDSECTION card image associated with it. This component contains all of the solid C3D8 elements which are created during realization. A collector with the name DCOUP3D_comp_<id> is created, containing all of the DCOUP3D elements created as the heads to the weld element.
If this script is called during the realization of adhesives in the area panel, this script creates the above two components by different names: hexa_comp_<id> for the Hexa elements rbe2_comp_<id> for the rbe elements The script also creates a property collector named prop_<id> , with the SOLIDSECTION card image associated to it. This property collector is referenced to the component containing the Hexa elements created during realization process (ie C3D8_comp_<id> in the case of spots, or hexa_comp_<id> in
Altair Engineering

the case of adhesives).
Abaqus sealing
CFG abaqus 5 sealing *filter spot *head rbe3 1 0 *body 0 rod 13 1
Description: Creates DCOUP3D elements for the head and element for the body. The head elements project and connect to the nodes of the adjoining shell elements.
Abaqus bush
CFG abaqus 6 bush *filter spot *head rigidlink 1 1 *body 0 rod 13 1 Description: Creates KINCOUP elements for the head and element for the body. The head elements project and connect to the nodes of the adjoining shell elements.
Abaqus bolt (b31)

Altair Engineering
CFG abaqus 7 bolt (b31) *filter bolt *style bolt 0 *head rigidlink 1 12 *body 0 bar2 9 1 *post prop_abaqus_b31.tcl
Description: Creates KINCOUP elements for the head and B31 element for the body. The head elements project and connect to the nodes of the adjoining shell elements that form the hole, and also to the second row of nodes to form the washer layer. The connector location can be on the edge of the hole, center of the hole, midpoint in between the two, holes or on the second row of nodes which form the washer layer. This connector also uses the script prop_abaqus_b31.tcl. This script updates the direction nodes of a group of bar elements created during realization to use the y axis. The *bardirectionupdate command is called to update the orientation node of bar element along Y-axis.
Abaqus hinge (b31)

CFG abaqus 8 hinge (b31) *filter bolt *style bolt 0 *head rigidlink 1 12 *body 0 bar2 9 1 dofs=4 *post prop_abaqus_b31.tcl
Description: Creates KINCOUP elements for the head and B31 element for the body. The rot x degree of freedom is constrained. The head elements project and connect to the nodes of the adjoining shell elements that form the hole, and also to the second row of nodes to form the washer layer. The connector location can be on the edge of the hole, center of the hole, midpoint in between the two holes, or on the second row
Altair Engineering

of nodes which form the washer layer. This connector also uses the script prop_abaqus_b31.tcl. This script updates the direction nodes of a group of bar elements created during realization to use the y axis. The *bardirectionupdate command is called to update the orientation node of bar element along Y-axis.
Abaqus clip
CFG abaqus 50 clip *filter bolt *style bolt 1 *head *body 0 rigidlink 1 2
Description: Creates a KINCOUP element. The element projects and connects to the nodes of the adjoining shell elements that form the hole, and also the nodes that form the washer layer. The connector location can either be on the edge of the hole, center of the hole, midpoint in between the two holes, or on the second row of nodes which form the washer layer.
Abaqus adhesives

Altair Engineering
CFG abaqus 9 adhesives *filter area *style adhesive 1 *head rbe3 1 0 rigid 1 0 *body 1 hex8 1 1 penta6 1 1 *post prop_abaqus_acm.tcl Description: Creates a row of hexa/penta elements for the body and numerous DCOUP3D/KINCOUP elements for the head. The head elements project and connect to the nodes of the adjoining shell elements. If there is a direct normal projection then a KINCOUP element will be used, if there are only non-normal projections then DCOUP3D elements will be created. The hexa/penta elements are projected so that they touch the shell elements of the connecting components. This realization uses the prop_abaqus_acm.tcl property script. This script is used while creating acm (equivalenced-(T1+T2)/2) / (detached-(T1+T2)/2) /shell gap in the spot weld panel and adhesives in the area panel. It does the following tasks. Organizes the realized weld elements [acm Equivalence-(T1+T2/2)] into the respective components based upon the *HEAD and the *BODY information of the weld. During realization of this configuration type a solid hexa element [C3D8] is connected to the shell elements by the rbe3 elements [DCOUP3D ]. A collector with the name C3D8_comp_<id> is created with the SOLIDSECTION card image associated with it. This component contains all of the solid C3D8 elements which are created during realization. A collector with the name DCOUP3D_comp_<id> is created, containing all of the DCOUP3D elements created as the heads to the weld element.
If this script is called during the realization of adhesives in the area panel, this script creates the above two components by different names: hexa_comp_<id> for the Hexa elements rbe2_comp_<id> for the rbe elements The script also creates a property collector named prop_<id> , with the SOLIDSECTION card image associated to it. This property collector is referenced to the component containing the Hexa elements created during realization process (ie C3D8_comp_<id> in the case of spots, or hexa_comp_<id> in the case of adhesives).
Altair Engineering

Abaqus rbe3 (load transfer)

CFG abaqus 31 rbe3 (load transfer) *filter spot *style mpc 1 *head *body 0 rbe3 1 1 dofs=123 Description: Creates DCOUP3D elements for the body. The degrees of freedom are constrained in the x, y, and z axes for the dependant nodes.

Altair Engineering
LS-DYNA Connector Types

dyna rigid (crbody)
CFG dyna 5 rigid (crbody) *filter spot *head *body 0 rigid 2 1 *post prop_rigid_crbody.tcl Description: Creates a RgdBody element for the body. This realization also uses the prop_rigid_crbody.tcl property script. This script updates mesh-dependent rigid welds > 2T into rigidlinks sharing a node. This is a requirement for the LS-DYNA *CONSTRAINED_NODAL_RIGID_BODY definition.
dyna ConNode (spider)

CFG dyna 56 ConNode (spider) *filter bolt *style bolt 2 *head *body 0 rigidlink 1 1 Description: Creates a ConNode rigidlink element for the body. It connects to the nearest node to the connector position and then projects to the nearest nodes on the adjoining elements of the connected components.
dyna RgdBody (spider)
Altair Engineering

CFG dyna 57 RgdBody (spider) *filter bolt *style bolt 2 *head *body 0 rigidlink 2 1
Description: Creates a RgdBody rigidlink element for the body. It connects to the nearest node to the connector position and then projects to the nearest nodes on the adjoining elements of the connected components. If holes are detected the nodes on the edges are connected.
dyna RgdBody (spider+washer)

CFG dyna 57 RgdBody (spider+washer) *filter bolt *style bolt 21 *head *body 0 rigidlink 2 1
Description: Creates a RgdBody rigidlink element for the body. It connects to the nearest node to the connector position and then projects to the nearest nodes on the adjoining elements of the connected components. If holes are detected the nodes on the edges and the washer nodes are connected.

Altair Engineering
dyna adhesive (shell gap)

CFG dyna 121 adhesive (shell gap) *filter area *style adhesive 2 *head *body 1 hex8 1 1 penta6 1 1 Description: Creates a row of hexa/penta elements. The hexa/penta elements are projected so that they touch the shell elements of the connecting components.
dyna mat100
CFG dyna 100 mat100 *filter spot *head *body 0 bar2 1 1 *post prop_dyna_matnum.tcl Description: Creates a BEAM element for the body and plot elements for the head, the plot elements are created for visualization purposes and find operations. This realization also uses the prop_dyna_matnum.tcl property script. This script is used while creation of mat100/mat100 (hexa)/mat196 custom config welds in the spot weld panel. It does the following tasks. Organizes the realized weld elements to the respective components based upon the link they are connected to and based upon the realization used. If a weld is created as mat100 between comp_1(id1) and comp_2(id2), it will create a component collector with the name C_^_<id1_id2>_BEAM_100 and organize all of the welds created as links between these two components into this collector.
Altair Engineering

If a weld is created as mat100 between the three components comp_1(id1), comp_2(id2) and comp_3 (id3), it will create two component collectors, C_^_1W_<id1_id2>_BEAM_100 and C_^_1W_<id2_id3>_BEAM_100. The suffix is based on the realization type: Mat100: _BEAM_100 Mat100 (hexa): _SOLID Mat196: _BEAM_196 This collector is later referenced as the weld element set while creating the groups (contact) definition. This script will create the following properties/materials collectors: M_^<id1_id2>_< MAT100 or MAT196> or M_^_1W_<id1_id2_id3>_<MAT100 or MAT196> : These material collectors are created upon the selection of the configuration type by the user with the MAT100 or the MAT196 card. The values for the cards are read from the *.ini file. These material collectors are referenced in the above created appropriate components. #MATERIAL STRENGTH LOOKUP TABLE # FIRST NUMBER INDICATES NUMBER OF LEVELS # SECOND NUMBER INDICATES MULTIPLIER FOR SIGY OF NUGGET #MIN #LAST LINE: # MIN *SIGY 0 0.20 0.40 0.80 MAX 4 0.20 0.40 0.80 0.90 k 1.85 4.0000 4.2000 4.5000 4.7000 1.9000 1.9500 1.9500 1.9900 10.5000 12.000 14.200 16.500 -4.000 -3.000 -2.000 -1.0000 9.00 n a b NUMBER MAX k n a b
P_^<id1_id2>_<BEAM or SOLID> or P_^_1W<id1_id2_id3>_<BEAM or SOLID> : These

Altair Engineering
property collectors are created with the *SECTION_BEAM or *SECTION_SOLID card associated with them. These property collectors are referenced in the above created appropriate components. # SAMPLE MATERIAL THICKNESS LOOKUP TABLE: # NUMBER INDICATES NUMBER OF LEVELS #LAST LINE: *THICKN ESS 0 5
0.1
0.1 2 5
0.1
0.5
0.2 5
0.5
1.0
0.7 5
1.0
1.5
1.2 5
1.5
2.0
17. 7 5
2.0
This script also creates the necessary group (contact) definition upon the selection of the configuration type. For mat100 and mat196 a group named C_Contact_Spotweld_<group id> and/or for mat100 (hexa) a group named C_Contact_Tied_Shell_Edge_To_Surface_<group id> is/are created. These interfaces are defined with the appropriate solver cards and reference the following master (MSID) and slave (SSID) sets: For the *CONTACT_SPOTWELD_ID card the following FS and FD are set to 0.1. For the *CONTACT_TIED_SHELL_EDGE_TO_SURFACE_ID card FS and FD are set to 0.1 as well. Additionally the values for variable SST and MST in the card image are set to 0.010. These values will override the thickness and establish the tied connection.
The script creates sets by the name C_S_^Part_<set id>_Contact_<group id> and C_S_^Weld_<set id>_Contact_<group id> . The configuration types mat100 and mat196 share the same sets, while the configuration type mat100 (hexa) gets a different pair of sets. The former set contains the parts to which the welds are connected and the latter contains the weld components created during realization process. The part sets is defined as master in the appropriate contact definition, the weld set as slave. In addition, for the mat100 (hexa) realization a set for each hexa cluster is created and named CE_HEXSW_<set id> . All these sets get a card *DEFINE_HEX_SPOTWELD_ASSEMBLY_<# hexa> associated with them.
Altair Engineering

Note :
This script is called if the CFG type is mat100/mat100 (hexa)/mat196
dyna mat100 (hexa)

CFG dyna 101 mat100 (hexa) *filter spot *head *body 0 hex8 1 1 *post prop_dyna_matnum.tcl Description: Creates hexa element with plot elements projecting and connecting to the surrounding shell elements. This realization does not use the shell thickness to calculate the hexa offset, therefore the hexa will project and be touching the shell elements. This realization also uses the prop_dyna_matnum.tcl property script. Organizes the realized weld elements to the respective components based upon the link they are connected to and based upon the realization used. If a weld is created as mat100 between comp_1(id1) and comp_2(id2), it will create a component collector with the name C_^_<id1_id2>_BEAM_100 and organize all of the welds created as links between these two components into this collector. If a weld is created as mat100 between the three components comp_1(id1), comp_2(id2) and comp_3 (id3), it will create two component collectors, C_^_1W_<id1_id2>_BEAM_100 and C_^_1W_<id2_id3>_BEAM_100. The suffix is based on the realization type: Mat100: _BEAM_100 Mat100 (hexa): _SOLID Mat196: _BEAM_196 This collector is later referenced as the weld element set while creating the groups (contact) definition. This script will create the following properties/materials collectors: M_^<id1_id2>_< MAT100 or MAT196> or M_^_1W_<id1_id2_id3>_<MAT100 or MAT196> : These material collectors are created upon the selection of the configuration type by the user with the MAT100 or the MAT196 card. The values for the cards are read from the *.ini file. These material collectors are referenced in the above created appropriate components. #MATERIAL STRENGTH LOOKUP TABLE

Altair Engineering
# FIRST NUMBER INDICATES NUMBER OF LEVELS # SECOND NUMBER INDICATES MULTIPLIER FOR SIGY OF NUGGET #MIN #LAST LINE: # MIN *SIGY 0 0.20 0.40 0.80 MAX 4 0.20 0.40 0.80 0.90 k 1.85 4.0000 4.2000 4.5000 4.7000 1.9000 1.9500 1.9500 1.9900 10.5000 12.000 14.200 16.500 -4.000 -3.000 -2.000 -1.0000 9.00 n a b NUMBER MAX k n a b
P_^<id1_id2>_<BEAM or SOLID> or P_^_1W<id1_id2_id3>_<BEAM or SOLID> : These property collectors are created with the *SECTION_BEAM or *SECTION_SOLID card associated with them. These property collectors are referenced in the above created appropriate components. # SAMPLE MATERIAL THICKNESS LOOKUP TABLE: # NUMBER INDICATES NUMBER OF LEVELS #LAST LINE: *THICKN ESS 0 5
0.1
0.1 2 5
0.1
0.5
0.2 5
Altair Engineering

0.5
1.0
0.7 5
1.0
1.5
1.2 5
1.5
2.0
17. 7 5
2.0
This script also creates the necessary group (contact) definition upon the selection of the configuration type. For mat100 and mat196 a group named C_Contact_Spotweld_<group id> and/or for mat100 (hexa) a group named C_Contact_Tied_Shell_Edge_To_Surface_<group id> is/are created. These interfaces are defined with the appropriate solver cards and reference the following master (MSID) and slave (SSID) sets: For the *CONTACT_SPOTWELD_ID card the following FS and FD are set to 0.1. For the *CONTACT_TIED_SHELL_EDGE_TO_SURFACE_ID card FS and FD are set to 0.1 as well. Additionally the values for variable SST and MST in the card image are set to 0.010. These values will override the thickness and establish the tied connection.
Note :
dyna mat196
CFG dyna 102 mat196 *filter spot *head *body 0 bar2 1 1

Altair Engineering
*post prop_dyna_matnum.tcl Description: Creates a BEAM element for the body and plot elements for the head, the plot elements are created for visualization purposes and find operations. This realization is the same as the CFG dyna 100 mat100 realization except it uses Mat196 as opposed to Mat100. This realization also uses the prop_dyna_matnum.tcl property script. This script is used while creation of mat100/mat100 (hexa)/mat196 custom config welds in the spot weld panel. It does the following tasks. Organizes the realized weld elements to the respective components based upon the link they are connected to and based upon the realization used. If a weld is created as mat100 between comp_1(id1) and comp_2(id2), it will create a component collector with the name C_^_<id1_id2>_BEAM_100 and organize all of the welds created as links between these two components into this collector. If a weld is created as mat100 between the three components comp_1(id1), comp_2(id2) and comp_3 (id3), it will create two component collectors, C_^_1W_<id1_id2>_BEAM_100 and C_^_1W_<id2_id3>_BEAM_100. The suffix is based on the realization type: Mat100: _BEAM_100 Mat100 (hexa): _SOLID Mat196: _BEAM_196 This collector is later referenced as the weld element set while creating the groups (contact) definition. This script will create the following properties/materials collectors: M_^<id1_id2>_< MAT100 or MAT196> or M_^_1W_<id1_id2_id3>_<MAT100 or MAT196> : These material collectors are created upon the selection of the configuration type by the user with the MAT100 or the MAT196 card. The values for the cards are read from the *.ini file. These material collectors are referenced in the above created appropriate components. #MATERIAL STRENGTH LOOKUP TABLE # FIRST NUMBER INDICATES NUMBER OF LEVELS # SECOND NUMBER INDICATES MULTIPLIER FOR SIGY OF NUGGET #MIN #LAST LINE: # MIN *SIGY 0 MAX 4 0.20 k 1.85 4.0000 1.9000 10.5000 -4.000 n a b NUMBER MAX k n a b
Altair Engineering

0.20 0.40 0.80
0.40 0.80 0.90
4.2000 4.5000 4.7000
1.9500 1.9500 1.9900
12.000 14.200 16.500
-3.000 -2.000 -1.0000 9.00
P_^<id1_id2>_<BEAM or SOLID> or P_^_1W<id1_id2_id3>_<BEAM or SOLID> : These property collectors are created with the *SECTION_BEAM or *SECTION_SOLID card associated with them. These property collectors are referenced in the above created appropriate components. # SAMPLE MATERIAL THICKNESS LOOKUP TABLE: # NUMBER INDICATES NUMBER OF LEVELS #LAST LINE: *THICKN ESS 0 5
0.1
0.1 2 5
0.1
0.5
0.2 5
0.5
1.0
0.7 5
1.0
1.5
1.2 5
1.5
2.0
17. 7 5
2.0
This script also creates the necessary group (contact) definition upon the selection of the configuration type. For mat100 and mat196 a group named C_Contact_Spotweld_<group id> and/or for mat100 (hexa) a group named C_Contact_Tied_Shell_Edge_To_Surface_<group id> is/are created. These interfaces are defined with the appropriate solver cards and reference the following master (MSID) and slave (SSID) sets: For the *CONTACT_SPOTWELD_ID card the following FS and FD are set to 0.1.

Altair Engineering
For the *CONTACT_TIED_SHELL_EDGE_TO_SURFACE_ID card FS and FD are set to 0.1 as well. Additionally the values for variable SST and MST in the card image are set to 0.010. These values will override the thickness and establish the tied connection.
Note :
dyna hexa (adhesive - shell gap)

CFG dyna 106 hexa (adhesive shell gap) *filter seam *style continuous 2 *head rbe3 1 0 rigid 1 0 *body 0 hex8 1 1 Description: Creates a row of hexa elements for the body and numerous RBE3 elements for the head. The head elements project and connect to the nodes of the adjoining shell elements. The hexa elements are projected so that they touch the shell elements of the connecting components.
Altair Engineering

Nastran Connector Types

Nastran sealing
CFG nastran 5 sealing *filter spot *head rbe3 1 0 *body 0 spring 6 1 Description: Creates RBE3 elements for the head and CBUSH element for the body. The head elements project and connect to the nodes of the adjoining shell elements.
Nastran bush
CFG nastran 6 bush *filter spot *head rigidlink 1 1 *body 0 spring 6 1 Description: Creates RBE2 elements for the head and CBUSH element for the body. The head elements project and connect to the nodes of the adjoining shell elements.
Nastran rbe3 (load transfer)

CFG nastran 31 rbe3 (load transfer) *filter spot *style mpc 1 *head *body 0

Altair Engineering
rbe3 1 1 dofs=123
Description: Creates RBE3 elements for the body. The degrees of freedom are constrained in the x, y, z for the dependant nodes.
Nastran bolt (general)

CFG nastran 52 bolt (general) *filter bolt *style bolt 0 *head rigidlink 1 1 *body 0 rigid 1 1
Description: Creates RBE2 elements for the head and the body. The head elements project and connect to the nodes of the adjoining shell elements which form the hole. The connector location can either be on the edge of the hole, center of the hole, midpoint in between the two holes or on the second row of nodes which form the washer layer.
Nastran bolt (CBAR)

CFG nastran 53 bolt (CBAR) *filter bolt *style bolt 0 *head rigid 1 1 *body 0 bar2 1 1
Altair Engineering

Description: Creates RBE2 elements for the head and CBAR element for the body. The head elements project and connect to the nodes of the adjoining shell elements which form the hole. The connector location can either be on the edge of the hole, center of the hole, midpoint in between the two holes or on the second row of nodes which form the washer layer.
Nastran clip
CFG nastran 50 clip *filter bolt *style bolt 1 *head *body 0 rigidlink 1 2
Description: Creates a single RBE2 element for the body. The element projects and connect to the nodes of the adjoining shell elements which form the hole and also the nodes which form the washer layer. The connector location can either be on the edge of the hole, center of the hole, midpoint in between the two holes or on the second row of nodes which form the washer layer.
Nastran bolt (spider)

CFG nastran 54 bolt (spider) *filter bolt *style bolt 1 *head *body 0 rigid 1 1
Description: Creates a many individual RBE2 elements. The element projects and connect to the nodes of

Altair Engineering
the adjoining shell elements which form the hole, the RBE2 elements are joined at the midpoint of the bolted connection. The connector location can either be on the edge of the hole, center of the hole, midpoint in between the two holes or on the second row of nodes which form the washer layer.
Nastran bolt (washer 1)

CFG nastran 57 bolt (washer 1) *filter bolt *style bolt 0 *head rigidlink 1 12 *body 0 rigid 1 1
Description: Creates RBE2 elements for the head and body. The head elements project and connect to the nodes of the adjoining shell elements which form the hole and also the second row of nodes which form the washer layer. The connector location can either be on the edge of the hole, center of the hole, midpoint in between the two holes or on the second row of nodes which form the washer layer.
Nastran bolt (washer 1 alt)

CFG nastran 58 bolt (washer 1 alt) *filter bolt *style bolt 0 *head rigidlink 1 13 *body 0 rigid 1 1
Description: Creates RBE2 elements for the head and body. The head elements project and connect to the nodes of the adjoining shell elements which form the hole and also the second row of nodes which form the
Altair Engineering

washer layer. The head only connects to every other node on the washer layer. The connector location can either be on the edge of the hole, center of the hole, midpoint in between the two holes or on the second row of nodes which form the washer layer.
Nastran bolt (washer 1) cbar

CFG nastran 51 bolt (washer 1) cbar *filter bolt *style bolt 0 *head rigidlink 1 12 *body 0 bar2 1 1
Description: Creates RBE2 elements for the head and CBAR element for the body. The head elements project and connect to the nodes of the adjoining shell elements which form the hole and also the second row of nodes which form the washer layer. The connector location can either be on the edge of the hole, center of the hole, midpoint in between the two holes or on the second row of nodes which form the washer layer.
Nastran bolt (washer 2)

CFG nastran 55 bolt (washer 2) *filter bolt *style bolt 0 *head rigidlink 1 1 rigidlink 1 2 *body 0 rigid 1 1 Description: Creates RBE2 elements for the head and the body. There are two individual RBE2 elements at

Altair Engineering
the head of the connection, one to connect to the inner row of nodes, the other to connect to the washer layer nodes. The connector location can either be on the edge of the hole, center of the hole, midpoint in between the two holes or on the second row of nodes which form the washer layer.
Nastran bolt (washer 2 alt)

CFG nastran 56 bolt (washer 2 alt) *filter bolt *style bolt 0 *head rigidlink 1 1 rigidlink 1 3 *body 0 rigid 1 1 Description: Creates RBE2 elements for the head and the body. There are two individual RBE2 elements at the head of the connection, one to connect to the inner row of nodes, the other to connect to the washer layer nodes. The RBE2 head element that connects to the washer layer nodes only connects to every other node on the washer layer. The connector location can either be on the edge of the hole, center of the hole, midpoint in between the two holes or on the second row of nodes which form the washer layer.
Nastran hinge
CFG nastran 59 hinge *filter bolt *style bolt 0 *head rigidlink 1 1 *body 0 rigid 1 1 dofs=12356 *post prop_hinge.tcl Description: Creates RBE2 elements for the head and the body. The head elements project and connect to
Altair Engineering

the nodes of the adjoining shell elements which form the hole. The connector location can either be on the edge of the hole, center of the hole, midpoint in between the two holes or on the second row of nodes which form the washer layer. The degrees of freedom are constrained in the x, y, z, rot x, rot z for the dependant nodes. This realization also uses the prop_hinge.tcl property script. This script is called while creation of HINGE custom config welds in the connector bolts panel. This script performs the tasks when the Systems option is active in the connector Bolts panel (i.e. Single System ,1- System per layer or 2- Systems per layer). This Script Assigns both reference and analysis systems ID to weld element nodes of each Bolt (Hinge) created during realization process.
Nastran acm (equivalenced-(T1+T2)/2)

CFG nastran 69 acm (equivalenced(T1+T2)/2) *filter spot *style acm 1 *head rbe3 1 0 *body 0 hex8 1 1 *post prop_nastran_acm.tcl Description: Creates hexa element with RBE3 elements projecting and connecting to the surrounding shell elements. This realization uses the shell thickness to calculate the hexa offset from the shell elements. In the case where the model is a 3T connection, the acm (equivalenced-(T1+T2)/2) realization will join the hexa elements. This realization also uses the prop_nastran_acm.tcl property script. This script is used while creation of acm equivalence/detached (T1+T2)/2 and shell gap custom config welds in the spot weld panel from the Nastran and OptiStruct user profile. It does the following tasks. Organizes the realized Solid Hexa weld elements created during realization process into hexa_comp_<id> components and the connected RBEs created as the *HEAD type are organized into the rbe3_comp_<id> components. This script will create the following properties collectors: Prop_<id1> : This property collector is created with the PSOLID card associated with it. This property collector is referenced in the above created component containing the Solid Hexa weld

Altair Engineering
elements hexa_comp_<id> . Apart from the above this script also updates the weights of any RBE3 that is almost zero, because weight factors close to 0.0 cause Nastran and OptiStruct solvers to generate incorrect results. This script is also called from the area connectors panel with the adhesives configuration type. It performs tasks similar to those described above, organizing the solids and the RBEs into their respective components. Note : This script is called if the CFG type is acm equivalence/detached (T1+T2)/2, shell gap and adhesives custom config welds for the Nastran and OptiStruct user profile.
Nastran acm (detached-(T1+T2)/2)

CFG nastran 70 acm (detached-(T1 +T2)/2) *filter spot *style acm 2 *head rbe3 1 0 *body 1 hex8 1 1 *post prop_nastran_acm.tcl Description: Creates hexa element with RBE3 elements projecting and connecting to the surrounding shell elements. This realization uses the shell thickness to calculate the hexa offset from the shell elements. In the case where the model is a 3T connection, the acm (detached-(T1+T2)/2) realization will not join the hexa elements. This realization also uses the prop_nastran_acm.tcl property script. This script is used while creation of acm equivalence/detached (T1+T2)/2 and shell gap custom config welds in the spot weld panel from the Nastran and OptiStruct user profile. It does the following tasks. Organizes the realized Solid Hexa weld elements created during realization process into hexa_comp_<id> components and the connected RBEs created as the *HEAD type are organized into the rbe3_comp_<id> components. This script will create the following properties collectors: Prop_<id1> : This property collector is created with the PSOLID card associated with it. This property collector is referenced in the above created component containing the Solid Hexa weld elements hexa_comp_<id> .
Apart from the above this script also updates the weights of any RBE3 that is almost zero, because
Altair Engineering

weight factors close to 0.0 cause Nastran and OptiStruct solvers to generate incorrect results. This script is also called from the area connectors panel with the adhesives configuration type. It performs tasks similar to those described above, organizing the solids and the RBEs into their respective components. Note : This script is called if the CFG type is acm equivalence/detached (T1+T2)/2, shell gap and adhesives custom config welds for Nastran and OptiStruct user profile.
Nastran acm (shell gap)

CFG nastran 71 acm (shell gap) *filter spot *style acm 3 *head rbe3 1 0 *body 0 hex8 1 1 *post prop_nastran_acm.tcl Description: Creates hexa element with RBE3 elements projecting and connecting to the surrounding shell elements. This realization does not use the shell thickness to calculate the hexa offset, therefore the hexa will project and be touching the shell elements. This realization also uses the prop_nastran_acm.tcl property script. This script is used while creation of acm equivalence/detached (T1+T2)/2 and shell gap custom config welds in the spot weld panel from the Nastran and OptiStruct user profile. It does the following tasks. Organizes the realized Solid Hexa weld elements created during realization process into hexa_comp_<id> components and the connected RBEs created as the *HEAD type are organized into the rbe3_comp_<id> components. This script will create the following properties collectors: Prop_<id1> : This property collector is created with the PSOLID card associated with it. This property collector is referenced in the above created component containing the Solid Hexa weld elements hexa_comp_<id> .
Apart from the above this script also updates the weights of any RBE3 that is almost zero, because weight factors close to 0.0 cause Nastran and OptiStruct solvers to generate incorrect results. This script is also called from the area connectors panel with the adhesives configuration type. It performs tasks similar to those described above, organizing the solids and the rbes into their respective components.

Altair Engineering
Note :
This script is called if the CFG type is acm equivalence/detached (T1+T2)/2, shell gap and adhesives custom config welds for Nastran and OptiStruct user profile.
Nastran penta (mig)

CFG nastran 75 penta (mig) *filter spot *head rbe3 1 0 *body 0 penta6 1 1
Description: Creates penta element with RBE3 elements projecting and connecting to the surrounding shell elements. This realization supports many different use cases, including T-joint, angled T-joint, lap joint and butt joint.
Nastran cweld (GA-GB PARTPAT)

CFG nastran 80 cweld (GA-GB PARTPAT) *filter spot *head *body 0 rod 4 1 *post prop_cweld.tcl Description: Creates 1D CWELD element via GA-GB PARTPAT. This realization also uses the prop_cweld.tcl property script. This script is called while creation of all the CWELD GA-GB and GS custom config welds in the spot weld panel. Theses include PARTPAT, ELPAT, ELEMID, GRIDID, ALIGN. It performs the following tasks: Assigns the attributes to the CWELD weld element created during the realization process, which is
Altair Engineering

either a rod element [GA-GB] or mass Element [GS] of the types PARTPAT, ELPAT, ELEMID, GRIDID or ALIGN. Creates the property collector with the name prop_<id> with the PWELD card associated with it. This property is referenced to the CWELD element created during realization. This script also updates the weld radius value in the CWELD card. The diameter value is either defined by the user on the spot weld panel, or is taken from the dvst (diameter versus thickness) file. Note : This script is called if the CWELD GA-GB and GS custom config welds and shell gap custom config welds across Nastran and OptiStruct user profiles.
Nastran cweld (GS PARTPAT)

CFG nastran 81 cweld (GS PARTPAT) *filter spot *head *body 0 mass 11 0 *post prop_cweld.tcl Description: Creates 0D CWELD element via GS PARTPAT. This realization also uses the prop_cweld.tcl property script. This script is called while creation of all the CWELD GA-GB and GS custom config welds in the spot weld panel. Theses include PARTPAT, ELPAT, ELEMID, GRIDID, ALIGN. It performs the following tasks: Assigns the attributes to the CWELD weld element created during the realization process, which is either a rod element [GA-GB] or mass Element [GS] of the types PARTPAT, ELPAT, ELEMID, GRIDID or ALIGN. Creates the property collector with the name prop_<id> with the PWELD card associated with it. This property is referenced to the CWELD element created during realization. This script also updates the weld radius value in the CWELD card. The diameter value is either defined by the user on the spot weld panel, or is taken from the dvst (diameter versus thickness) file. Note : This script is called if the CWELD GA-GB and GS custom config welds and shell gap custom config welds across Nastran and OptiStruct user profiles.

Altair Engineering
Nastran cweld (GA-GB ELPAT)

CFG nastran 82 cweld (GA-GB ELPAT) *filter spot *head *body 0 rod 4 1 *post prop_cweld.tcl Description: Creates 1D CWELD element via GA-GB ELPAT. This realization also uses the prop_cweld.tcl property script. This script is called while creation of all the CWELD GA-GB and GS custom config welds in the spot weld panel. Theses include PARTPAT, ELPAT, ELEMID, GRIDID, ALIGN. It performs the following tasks: Assigns the attributes to the CWELD weld element created during the realization process, which is either a rod element [GA-GB] or mass Element [GS] of the types PARTPAT, ELPAT, ELEMID, GRIDID or ALIGN. Creates the property collector with the name prop_<id> with the PWELD card associated with it. This property is referenced to the CWELD element created during realization. This script also updates the weld radius value in the CWELD card. The diameter value is either defined by the user on the spot weld panel, or is taken from the dvst (diameter versus thickness) file. Note : This script is called if the CWELD GA-GB and GS custom config welds and shell gap custom config welds across Nastran and OptiStruct user profiles.
Nastran cweld (GS ELPAT)

CFG nastran 83 cweld (GS ELPAT) *filter spot *head *body 0 mass 11 0 *post prop_cweld.tcl
Altair Engineering

Description: Creates 0D CWELD element via GS ELPAT. This realization also uses the prop_cweld.tcl property script. This script is called while creation of all the CWELD GA-GB and GS custom config welds in the spot weld panel. Theses include PARTPAT, ELPAT, ELEMID, GRIDID, ALIGN. It performs the following tasks: Assigns the attributes to the CWELD weld element created during the realization process, which is either a rod element [GA-GB] or mass Element [GS] of the types PARTPAT, ELPAT, ELEMID, GRIDID or ALIGN. Creates the property collector with the name prop_<id> with the PWELD card associated with it. This property is referenced to the CWELD element created during realization. This script also updates the weld radius value in the CWELD card. The diameter value is either defined by the user on the spot weld panel, or is taken from the dvst (diameter versus thickness) file. Note : This script is called if the CWELD GA-GB and GS custom config welds and shell gap custom config welds across Nastran and OptiStruct user profiles.
Nastran cweld (GA-GB ELEMID)

CFG nastran 84 cweld (GA-GB ELEMID) *filter spot *head *body 0 rod 4 1 *post prop_cweld.tcl Description: Creates 1D CWELD element via GA-GB ELEMID. This realization also uses the prop_cweld.tcl property script. This script is called while creation of all the CWELD GA-GB and GS custom config welds in the spot weld panel. Theses include PARTPAT, ELPAT, ELEMID, GRIDID, ALIGN. It performs the following tasks: Assigns the attributes to the CWELD weld element created during the realization process, which is either a rod element [GA-GB] or mass Element [GS] of the types PARTPAT, ELPAT, ELEMID, GRIDID or ALIGN. Creates the property collector with the name prop_<id> with the PWELD card associated with it. This property is referenced to the CWELD element created during realization. This script also updates the weld radius value in the CWELD card. The diameter value is either

Altair Engineering
defined by the user on the spot weld panel, or is taken from the dvst (diameter versus thickness) file. Note : This script is called if the CWELD GA-GB and GS custom config welds and shell gap custom config welds across Nastran and OptiStruct user profiles.
Nastran cweld (GS ELEMID)

CFG nastran 85 cweld (GS ELEMID) *filter spot *head *body 0 mass 11 0 *post prop_cweld.tcl
Description: Creates 0D CWELD element via GS ELEMID. This realization also uses the prop_cweld.tcl property script. This script is called while creation of all the CWELD GA-GB and GS custom config welds in the spot weld panel. Theses include PARTPAT, ELPAT, ELEMID, GRIDID, ALIGN. It performs the following tasks: Assigns the attributes to the CWELD weld element created during the realization process, which is either a rod element [GA-GB] or mass Element [GS] of the types PARTPAT, ELPAT, ELEMID, GRIDID or ALIGN. Creates the property collector with the name prop_<id> with the PWELD card associated with it. This property is referenced to the CWELD element created during realization. This script also updates the weld radius value in the CWELD card. The diameter value is either defined by the user on the spot weld panel, or is taken from the dvst (diameter versus thickness) file. Note : This script is called if the CWELD GA-GB and GS custom config welds and shell gap custom config welds across Nastran and OptiStruct user profiles.
Nastran cweld (GA-GB GRIDID)
Altair Engineering

CFG nastran 86 cweld (GA-GB GRIDID) *filter spot *head *body 0 rod 4 1 *post prop_cweld.tcl Description: Creates 1D CWELD element via GA-GB GRIDID. This realization also uses the prop_cweld.tcl property script. This script is called while creation of all the CWELD GA-GB and GS custom config welds in the spot weld panel. Theses include PARTPAT, ELPAT, ELEMID, GRIDID, ALIGN. It performs the following tasks: Assigns the attributes to the CWELD weld element created during the realization process, which is either a rod element [GA-GB] or mass Element [GS] of the types PARTPAT, ELPAT, ELEMID, GRIDID or ALIGN. Creates the property collector with the name prop_<id> with the PWELD card associated with it. This property is referenced to the CWELD element created during realization. This script also updates the weld radius value in the CWELD card. The diameter value is either defined by the user on the spot weld panel, or is taken from the dvst (diameter versus thickness) file. Note : This script is called if the CWELD GA-GB and GS custom config welds and shell gap custom config welds across Nastran and OptiStruct user profiles.
Nastran cweld (GS GRIDID)

CFG nastran 87 cweld (GS GRIDID) *filter spot *head *body 0 mass 11 0 *post prop_cweld.tcl Description: Creates 0D CWELD element via GS GRIDID. This realization also uses the prop_cweld.tcl property script.

Altair Engineering
This script is called while creation of all the CWELD GA-GB and GS custom config welds in the spot weld panel. Theses include PARTPAT, ELPAT, ELEMID, GRIDID, ALIGN. It performs the following tasks: Assigns the attributes to the CWELD weld element created during the realization process, which is either a rod element [GA-GB] or mass Element [GS] of the types PARTPAT, ELPAT, ELEMID, GRIDID or ALIGN. Creates the property collector with the name prop_<id> with the PWELD card associated with it. This property is referenced to the CWELD element created during realization. This script also updates the weld radius value in the CWELD card. The diameter value is either defined by the user on the spot weld panel, or is taken from the dvst (diameter versus thickness) file. Note : This script is called if the CWELD GA-GB and GS custom config welds and shell gap custom config welds across Nastran and OptiStruct user profiles.
Nastran cweld (GA-GB ALIGN)

CFG nastran 88 cweld (GA-GB ALIGN) *filter spot *head *body 0 rod 4 1 *post prop_cweld.tcl Description: Creates 1D CWELD element via GA-GB ALIGN. This realization also uses the prop_cweld.tcl property script. This script is called while creation of all the CWELD GA-GB and GS custom config welds in the spot weld panel. Theses include PARTPAT, ELPAT, ELEMID, GRIDID, ALIGN. It performs the following tasks: Assigns the attributes to the CWELD weld element created during the realization process, which is either a rod element [GA-GB] or mass Element [GS] of the types PARTPAT, ELPAT, ELEMID, GRIDID or ALIGN. Creates the property collector with the name prop_<id> with the PWELD card associated with it. This property is referenced to the CWELD element created during realization. This script also updates the weld radius value in the CWELD card. The diameter value is either defined by the user on the spot weld panel, or is taken from the dvst (diameter versus thickness) file. Note : This script is called if the CWELD GA-GB and GS custom config welds and shell gap custom
Altair Engineering

config welds across Nastran and OptiStruct user profiles.
Nastran rbe3-celas1-rbe3
CFG nastran 89 rbe3-celas1-rbe3 *filter spot *head rbe3 1 0 dofs=123456 *body 0 spring 1 0 Description: Creates RBE3 element for the head and zero length CELAS1 element for the body. The head elements project and connect to the nodes of the adjoining shell elements. The degrees of freedom are constrained in the x, y, z, rot x, rot y, rot z for the dependant nodes.
Nastran adhesives
CFG nastran 121 adhesives *filter area *style adhesive 1 *head rbe3 1 0 rigid 1 0 *body 1 hex8 1 1 penta6 1 1 *post prop_nastran_acm.tcl Description: This realization also uses the prop_nastran_acm.tcl property script. This script is used while creation of acm equivalence/detached (T1+T2)/2 and shell gap custom config welds in the spot weld panel from the Nastran and OptiStruct user profiles. It does the following tasks.

Altair Engineering
Organizes the realized Solid Hexa weld elements created during realization process into hexa_comp_<id> components and the connected RBEs created as the *HEAD type are organized into the rbe3_comp_<id> components. This script will create the following properties collectors: Prop_<id1> : This property collector is created with the PSOLID card associated with it. This property collector is referenced in the above created component containing the Solid Hexa weld elements hexa_comp_<id> .
Apart from the above this script also updates the weights of any RBE3 that is almost zero, because weight factors close to 0.0 cause Nastran and OptiStruct solvers to generate incorrect results. This script is also called from the area connectors panel with the adhesives configuration type. It performs tasks similar to those described above, organizing the solids and the rbes into their respective components. Note : This script is called if the CFG type is acm equivalence/detached (T1+T2)/2, shell gap and adhesives custom config welds for Nastran and OptiStruct user profiles.
Nastran hemming
CFG nastran 122 hemming *filter area *style adhesive 1 *head *body 0 rbe3 1 1
Description: Creates RBE3 elements for the body, the head elements project and connect to the nodes of the adjoining shell elements.
Nastran seam-quad (vertical+angled)
Altair Engineering

CFG nastran 103 seam-quad (vertical+angled) *filter seam *style quad 1 *head *body 0 quad4 1 1
Description: Creates vertical and angled shell elements and projects to the adjoining shell elements. The angle can be specified in the seam panel. If the angle is set to 0.0 the thicknesses of the components are required as they are used to calculate the angle of the welds under those circumstances. This realization is intended for use with the quad transition option.
Nastran seam-quad (angled)

CFG nastran 104 seam-quad (angled) *filter seam *style quad 2 *head *body 0 quad4 1 1
Description: Creates angled shell elements and projects to the adjoining shell elements. The angle can be specified in the seam panel. If the angle is set to 0.0 the thicknesses of the components are required as they are used to calculate the angle of the welds under those circumstances. This realization is intended for use with the quad transition option.
Nastran penta (mig)

Altair Engineering
CFG nastran 105 penta (mig) *filter seam *style continuous 3 *head rbe3 1 0 *body 0 penta6 1 1
Description: Creates penta elements with RBE3 elements projecting and connecting to the surrounding shell elements. This realization supports many different use cases, including T-joint, angled T-joint, lap joint and butt joint.
Nastran hexa (adhesive)

CFG nastran 106 hexa (adhesive) *filter seam *style continuous 3 *head rbe3 1 0 rigid 1 0 *body 0 hex8 1 1 Description: Creates a row of hexa elements for the body and numerous RBE2/RBE3 elements for the head. The head elements project and connect to the nodes of the adjoining shell elements. If there is a direct normal project then an RBE2 elements will be used, if there are only non-normal projections then RBE3 elements will be created. The hexa elements are projected so that they touch the shell elements of the connecting components.
Nastran cfast_elem (GA-GB)
Altair Engineering

CFG nastran 107 cfast_elem (GAGB) *filter spot *head *body 0 rod 7 1 *post prop_opt_nas_cfast.tcl Description: Creates 1D CFAST element of type ELEM. This realization also uses the prop_opt_nas_cfast.tcl property script. This script is called while creation of all the CFAST GA-GB and GS custom config welds in the spot weld panel. Theses include ELEM , and PROP. It performs the following tasks: Assigns the attributes to the CFAST weld element created during the realization process, which is either a rod element [GA-GB] or mass Element [GS] of the types ELEM or PROP. Creates the property collector with the name PFAST_<diameter> with the PFAST card associated with it. This property is referenced to the CFAST element created during realization. This script also updates the weld diameter value in the CFAST card. The diameter value is either defined by the user on the spot weld panel, or is taken from the dvst (diameter versus thickness) file. Note: This script is called for the CFAST GA-GB and GS custom config welds across Nastran and OptiStruct user profiles.
Nastran cfast_elem (GS)

CFG nastran 108 cfast_elem (GS) *filter spot *head *body 0 mass 23 0 *post prop_opt_nas_cfast.tcl Description: Creates 0D CFAST element of type ELEM. This realization also uses the prop_opt_nas_cfast.tcl property script. This script is called while creation of all the CFAST GA-GB and GS custom config welds in the spot weld

Altair Engineering
panel. Theses include ELEM , and PROP. It performs the following tasks: Assigns the attributes to the CFAST weld element created during the realization process, which is either a rod element [GA-GB] or mass Element [GS] of the types ELEM or PROP. Creates the property collector with the name PFAST_<diameter> with the PFAST card associated with it. This property is referenced to the CFAST element created during realization. This script also updates the weld diameter value in the CFAST card. The diameter value is either defined by the user on the spot weld panel, or is taken from the dvst (diameter versus thickness) file. Note: This script is called for the CFAST GA-GB and GS custom config welds across Nastran and OptiStruct user profiles.
Nastran cfast_prop (GA-GB)

CFG nastran 109 cfast_prop (GAGB) *filter spot *head *body 0 rod 7 1 *post prop_opt_nas_cfast.tcl Description: Creates 1D CFAST element of type PROP. This realization also uses the prop_opt_nas_cfast.tcl property script. This script is called while creation of all the CFAST GA-GB and GS custom config welds in the spot weld panel. Theses include ELEM , and PROP. It performs the following tasks: Assigns the attributes to the CFAST weld element created during the realization process, which is either a rod element [GA-GB] or mass Element [GS] of the types ELEM or PROP. Creates the property collector with the name PFAST_<diameter> with the PFAST card associated with it. This property is referenced to the CFAST element created during realization. This script also updates the weld diameter value in the CFAST card. The diameter value is either defined by the user on the spot weld panel, or is taken from the dvst (diameter versus thickness) file. Note: This script is called for the CFAST GA-GB and GS custom config welds across Nastran and OptiStruct user profiles.
Altair Engineering

Nastran cfast_prop (GS)

CFG nastran 110 cfast_prop (GS) *filter spot *head *body 0 mass 23 0 *post prop_opt_nas_cfast.tcl Description: Creates 0D CFAST element of type PROP. This realization also uses the prop_opt_nas_cfast.tcl property script. This script is called while creation of all the CFAST GA-GB and GS custom config welds in the spot weld panel. Theses include ELEM , and PROP. It performs the following tasks: Assigns the attributes to the CFAST weld element created during the realization process, which is either a rod element [GA-GB] or mass Element [GS] of the types ELEM or PROP. Creates the property collector with the name PFAST_<diameter> with the PFAST card associated with it. This property is referenced to the CFAST element created during realization. This script also updates the weld diameter value in the CFAST card. The diameter value is either defined by the user on the spot weld panel, or is taken from the dvst (diameter versus thickness) file. Note: This script is called for the CFAST GA-GB and GS custom config welds across Nastran and OptiStruct user profiles.
Nastran HILOCK

Altair Engineering
CFG nastran 111 HILOCK *filter spot *style fastener 1 *head *bodyext 0 bar2 1 1 weld 1 1 dofs=1456 *body 0 spring 6 0 dofs=2356 bar2 1 1 weld 1 1 dofs=156 spring 6 0 dofs=2356 *post prop_opt_nas_hilock.tcl Description: Creates 1D element construct existing out of RBAR, CBAR and CBUSH elements. The outer extensions represent the thicknesses of the outer shell elements. The inner nodes of the RBAR element are connected to the shell elements whereas the inner nodes of the CBAR elements are coincident to the shell nodes only. Between the appropriate connected and coincident nodes CBUSHes are created. Each outer node connects one CBAR and one RBAR. Each HILOCK connection gets an own coordinate system which z-axis is collinear to the HILOCK direction. All affected nodes are assigned to this coordinate system. This coordinate system is taken into account for the DOF definition of the CBAR elements, for the stiffness calculation of the CBUSH elements and for the DOF of the node constraint. This realization uses the shell properties and materials (PSHELL or PCOMP) and a predefined HILOCK material to calculate the exact position of the outer nodes and the stiffness of the PBUSH elements. If the realization requires a local remesh of the shell elements because there arent any shell nodes at the position of the connector projection, the connector realization will fail. This realization also uses the prop_opt_nas_hilock.tcl property script. This script is used while creation of HILOCK custom config welds in the spot weld panel from the Nastran and OptiStruct user profile. It does the following tasks. 1. 2. Organizes the realized 1D weld elements (RBAR, CBAR, CBUSH) created during realization process into a component named HiLock components. This script will create the following property collectors: HiLock_PBAR_<diameter> : This property collector is created with the PBAR card associated with it. The RBAR elements reference to this property. The attributes are calculated depending on the used diameter in the spot panel during realization. HiLock_PBUSH_<translational stiffness>_<rotational stiffness> : These property collectors are created with the PBUSH card associated with them. The CBUSH elements reference to this
Altair Engineering

property. The attributes are calculated depending on a predefined HILOCK material and the properties and materials of the connected shells (PSHELL and/or PCOMP). 3. This script will create the following load collector: HiLock_SPC6: This load collector is created and the SPCs, which are created for each HiLock will be moved into this collector. 4. This script will create the following system collector: HiLock : This system collector is created and the systems created during the realizations will be moved into this collector. If the system collector exists already the new created systems will be moved into the same collector. 5. This script will create the following material: HiLock_MAT1: This material will be assigned to the PBAR cards. The material is predefined in the script. Note: This script is called if the realization CFG nastran 111 HILOCK or CFG optistruct 111 HILOCK is used.

Altair Engineering
OptiStruct Connector Types

OptiStruct sealing
CFG optistruct 5 sealing *filter spot *head rbe3 1 0 *body 0 spring 6 1 Description: Creates RBE3 elements for the head and CBUSH element for the body. The head elements project and connect to the nodes of the adjoining shell elements.
OptiStruct bush
CFG optistruct 6 bush *filter spot *head rigidlink 1 1 *body 0 spring 6 1 Description: Creates RBE2 elements for the head and CBUSH element for the body. The head elements project and connect to the nodes of the adjoining shell elements.
OptiStruct rbe3 (load transfer)

CFG optistruct 31 rbe3 (load transfer) *filter spot *style mpc 1 *head *body 0
Altair Engineering

rbe3 1 1 dofs=123
Description: Creates RBE3 elements for the body. The degrees of freedom are constrained in the x, y, z for the dependant nodes.
OptiStruct bolt (general)

CFG optistruct 52 bolt (general) *filter bolt *style bolt 0 *head rigidlink 1 1 *body 0 rigid 1 1
Description: Creates RBE2 elements for the head and the body. The head elements project and connect to the nodes of the adjoining shell elements which form the hole. The connector location can either be on the edge of the hole, center of the hole, midpoint in between the two holes or on the second row of nodes which form the washer layer.
OptiStruct bolt (CBAR)

Altair Engineering
CFG optistruct 53 bolt (CBAR) *filter bolt *style bolt 0 *head rigid 1 1 *body 0 bar2 1 1
Description: Creates RBE2 elements for the head and CBAR element for the body. The head elements project and connect to the nodes of the adjoining shell elements which form the hole. The connector location can either be on the edge of the hole, center of the hole, midpoint in between the two holes or on the second row of nodes which form the washer layer.
OptiStruct clip
CFG optistruct 50 clip *filter bolt *style bolt 1 *head *body 0 rigidlink 1 2
Description: Creates a single RBE2 element for the body. The element projects and connect to the nodes of the adjoining shell elements which form the hole and also the nodes which form the washer layer. The connector location can either be on the edge of the hole, center of the hole, midpoint in between the two holes or on the second row of nodes which form the washer layer.
OptiStruct bolt (spider)
Altair Engineering

CFG optistruct 54 bolt (spider) *filter bolt *style bolt 1 *head *body 0 rigid 1 1
Description: Creates a many individual RBE2 elements. The element projects and connect to the nodes of the adjoining shell elements which form the hole, the RBE2 elements are joined at the midpoint of the bolted connection. The connector location can either be on the edge of the hole, center of the hole, midpoint in between the two holes or on the second row of nodes which form the washer layer.
OptiStruct bolt (washer 1)

CFG optistruct 57 bolt (washer 1) *filter bolt *style bolt 0 *head rigidlink 1 12 *body 0 rigid 1 1
Description: Creates RBE2 elements for the head and body. The head elements project and connect to the nodes of the adjoining shell elements which form the hole and also the second row of nodes which form the washer layer. The connector location can either be on the edge of the hole, center of the hole, midpoint in between the two holes or on the second row of nodes which form the washer layer.
OptiStruct bolt (washer 1 alt)

Altair Engineering
CFG optistruct 58 bolt (washer 1 alt) *filter bolt *style bolt 0 *head rigidlink 1 13 *body 0 rigid 1 1
Description: Creates RBE2 elements for the head and body. The head elements project and connect to the nodes of the adjoining shell elements which form the hole and also the second row of nodes which form the washer layer. The head only connects to every other node on the washer layer. The connector location can either be on the edge of the hole, center of the hole, midpoint in between the two holes or on the second row of nodes which form the washer layer.
OptiStruct bolt (washer 1) cbar

CFG optistruct 51 bolt (washer 1) cbar *filter bolt *style bolt 0 *head rigidlink 1 12 *body 0 bar2 1 1
Description: Creates RBE2 elements for the head and CBAR element for the body. The head elements project and connect to the nodes of the adjoining shell elements which form the hole and also the second row of nodes which form the washer layer. The connector location can either be on the edge of the hole, center of the hole, midpoint in between the two holes or on the second row of nodes which form the washer layer.
Altair Engineering

OptiStruct bolt (washer 2)

CFG optistruct 55 bolt (washer 2) *filter bolt *style bolt 0 *head rigidlink 1 1 rigidlink 1 2 *body 0 rigid 1 1
Description: Creates RBE2 elements for the head and the body. There are two individual RBE2 elements at the head of the connection, one to connect to the inner row of nodes, the other to connect to the washer layer nodes. The connector location can either be on the edge of the hole, center of the hole, midpoint in between the two holes or on the second row of nodes which form the washer layer.
OptiStruct bolt (washer 2 alt)

CFG optistruct 56 bolt (washer 2 alt) *filter bolt *style bolt 0 *head rigidlink 1 1 rigidlink 1 3 *body 0 rigid 1 1
Description: Creates RBE2 elements for the head and the body. There are two individual RBE2 elements at the head of the connection, one to connect to the inner row of nodes, the other to connect to the washer layer nodes. The RBE2 head element that connects to the washer layer nodes only connects to every other node on the washer layer. The connector location can either be on the edge of the hole, center of the hole, midpoint in between the two holes or on the second row of nodes which form the washer layer.

Altair Engineering
OptiStruct hinge
CFG optistruct 59 hinge *filter bolt *style bolt 0 *head rigidlink 1 1 *body 0 rigid 1 1 dofs=12356 *post prop_hinge.tcl
Description: Creates RBE2 elements for the head and the body. The head elements project and connect to the nodes of the adjoining shell elements which form the hole. The connector location can either be on the edge of the hole, center of the hole, midpoint in between the two holes or on the second row of nodes which form the washer layer. The degrees of freedom are constrained in the x, y, z, rot x, rot z for the dependant nodes. This realization also uses the prop_hinge.tcl property script. This script is called while creation of HINGE custom config welds in the connector bolts panel. This script performs the tasks when the Systems option is active in the connector bolts panel (i.e. Single System ,1- System per layer or 2- Systems per layer). This script assigns both reference and analysis systems ID to weld element nodes of each Bolt (Hinge) created during realization process.
OptiStruct acm (equivalenced-(T1+T2)/2)
Altair Engineering

CFG optistruct 69 acm (equivalenced-(T1+T2)/2) *filter spot *style acm 1 *head rbe3 1 0 *body 0 hex8 1 1 *post prop_nastran_acm.tcl Description: Creates hexa element with RBE3 elements projecting and connecting to the surrounding shell elements. This realization uses the shell thickness to calculate the hexa offset from the shell elements. In the case where the model is a 3T connection, the acm (equivalenced-(T1+T2)/2) realization will join the hexa elements. This realization also uses the prop_nastran_acm.tcl property script. This script is used while creation of acm equivalence/detached (T1+T2)/2 and shell gap custom config welds in the spot weld panel from Nastran and OptiStruct user profiles. It does the following tasks. Organizes the realized solid hexa weld elements created during realization process into hexa_comp_<id> components and the connected RBEs created as the *HEAD type are organized into the rbe3_comp_<id> components. This script will create the following properties collectors: Prop_<id1> : This property collector is created with the PSOLID card associated with it. This property collector is referenced in the above created component containing the Solid Hexa weld elements hexa_comp_<id> .
Apart from the above this script also updates the weights of any RBE3 that is almost zero, because weight factors close to 0.0 cause Nastran and OptiStruct solvers to generate incorrect results. This script is also called from the area connectors panel with the adhesives configuration type. It performs tasks similar to those described above, organizing the solids and the RBEs into their respective components. Note : This script is called if the CFG type is acm equivalence/detached (T1+T2)/2, shell gap and adhesives custom config welds for Nastran and OptiStruct user profiles.
OptiStruct acm (detached-(T1+T2)/2)

Altair Engineering
CFG optistruct 70 acm (detached-(T1+T2)/2) *filter spot *style acm 2 *head rbe3 1 0 *body 1 hex8 1 1 *post prop_nastran_acm.tcl Description: Creates hexa element with RBE3 elements projecting and connecting to the surrounding shell elements. This realization uses the shell thickness to calculate the hexa offset from the shell elements. In the case where the model is a 3T connection, the acm (detached-(T1+T2)/2) realization will not join the hexa elements. This realization also uses the prop_nastran_acm.tcl property script. This script is used while creation of acm equivalence/detached (T1+T2)/2 and shell gap custom config welds in the spot weld panel from Nastran and OptiStruct user profiles. It does the following tasks. Organizes the realized solid hexa weld elements created during realization process into hexa_comp_<id> components and the connected RBEs created as the *HEAD type are organized into the rbe3_comp_<id> components. This script will create the following properties collectors: Prop_<id1> : This property collector is created with the PSOLID card associated with it. This property collector is referenced in the above created component containing the Solid Hexa weld elements hexa_comp_<id> .
Apart from the above this script also updates the weights of any RBE3 that is almost zero, because weight factors close to 0.0 cause Nastran and OptiStruct solvers to generate incorrect results. This script is also called from the area connectors panel with the adhesives configuration type. It performs tasks similar to those described above, organizing the solids and the RBEs into their respective components. Note : This script is called if the CFG type is acm equivalence/detached (T1+T2)/2, shell gap and adhesives custom config welds for Nastran and OptiStruct user profiles.
OptiStruct acm (shell gap)
Altair Engineering

CFG optistruct 71 acm (shell gap) *filter spot *style acm 3 *head rbe3 1 0 *body 0 hex8 1 1 *post prop_nastran_acm.tcl Description: Creates hexa element with RBE3 elements projecting and connecting to the surrounding shell elements. This realization does not use the shell thickness to calculate the hexa offset, therefore the hexa will project and be touching the shell elements. This realization also uses the prop_nastran_acm.tcl property script. This script is used while creation of acm equivalence/detached (T1+T2)/2 and shell gap custom config welds in the spot weld panel from Nastran and OptiStruct user profiles. It does the following tasks. Organizes the realized solid hexa weld elements created during realization process into hexa_comp_<id> components and the connected RBEs created as the *HEAD type are organized into the rbe3_comp_<id> components. This script will create the following properties collectors: Prop_<id1> : This property collector is created with the PSOLID card associated with it. This property collector is referenced in the above created component containing the Solid Hexa weld elements hexa_comp_<id> .
OptiStruct penta (mig)

Altair Engineering
CFG optistruct 75 penta (mig) *filter spot *head rbe3 1 0 *body 0 penta6 1 1
Description: Creates penta element with RBE3 elements projecting and connecting to the surrounding shell elements. This realization supports many different use cases, including T-joint, angled T-joint, lap joint and butt joint.
OptiStruct cweld (GA-GB PARTPAT)

CFG optistruct 80 cweld (GAGB PARTPAT) *filter spot *head *body 0 rod 4 1 *post prop_cweld.tcl Description: Creates 1d CWELD element via GA-GB PARTPAT. This realization also uses the prop_cweld.tcl property script. This script is called while creation of all the CWELD GA-GB and GS custom config welds in the spot weld panel. Theses include PARTPAT, ELPAT, ELEMID, GRIDID, ALIGN. It performs the following tasks: Assigns the attributes to the CWELD weld element created during the realization process, which is either a rod element [GA-GB] or mass Element [GS] of the types PARTPAT, ELPAT, ELEMID, GRIDID or ALIGN. Creates the property collector with the name prop_<id> with the PWELD card associated with it. This property is referenced to the CWELD element created during realization. This script also updates the weld radius value in the CWELD card. The diameter value is either defined by the user on the spot weld panel, or is taken from the dvst (diameter versus thickness)
Altair Engineering

file. Note : This script is called if the CWELD GA-GB and GS custom config welds and shell gap custom config welds across Nastran and OptiStruct user profiles.
OptiStruct cweld (GS PARTPAT)

CFG optistruct 81 cweld (GS PARTPAT) *filter spot *head *body 0 mass 11 0 *post prop_cweld.tcl Description: Creates 0D CWELD element via GS PARTPAT. This realization also uses the prop_cweld.tcl property script. This script is called while creation of all the CWELD GA-GB and GS custom config welds in the spot weld panel. Theses include PARTPAT, ELPAT, ELEMID, GRIDID, ALIGN. It performs the following tasks: Assigns the attributes to the CWELD weld element created during the realization process, which is either a rod element [GA-GB] or mass element [GS] of the types PARTPAT, ELPAT, ELEMID, GRIDID or ALIGN. Creates the property collector with the name prop_<id> with the PWELD card associated with it. This property is referenced to the CWELD element created during realization. This script also updates the weld radius value in the CWELD card. The diameter value is either defined by the user on the spot weld panel, or is taken from the dvst (diameter versus thickness) file. Note : This script is called if the CWELD GA-GB and GS custom config welds and shell gap custom config welds across Nastran and OptiStruct user profiles.
OptiStruct cweld (GA-GB ELPAT)

Altair Engineering
CFG optistruct 82 cweld (GAGB ELPAT) *filter spot *head *body 0 rod 4 1 *post prop_cweld.tcl Description: Creates 1D CWELD element via GA-GB ELPAT. This realization also uses the prop_cweld.tcl property script. This script is called while creation of all the CWELD GA-GB and GS custom config welds in the spot weld panel. Theses include PARTPAT, ELPAT, ELEMID, GRIDID, ALIGN. It performs the following tasks: Assigns the attributes to the CWELD weld element created during the realization process, which is either a rod element [GA-GB] or mass Element [GS] of the types PARTPAT, ELPAT, ELEMID, GRIDID or ALIGN. Creates the property collector with the name prop_<id> with the PWELD card associated with it. This property is referenced to the CWELD element created during realization. This script also updates the weld radius value in the CWELD card. The diameter value is either defined by the user on the spot weld panel, or is taken from the dvst (diameter versus thickness) file. Note : This script is called if the CWELD GA-GB and GS custom config welds and shell gap custom config welds across Nastran and OptiStruct user profiles.
OptiStruct cweld (GS ELPAT)

CFG optistruct 83 cweld (GS ELPAT) *filter spot *head *body 0 mass 11 0 *post prop_cweld.tcl Description: Creates 0D CWELD element via GS ELPAT. This realization also uses the prop_cweld.tcl property script.
Altair Engineering

This script is called while creation of all the CWELD GA-GB and GS custom config welds in the spot weld panel. Theses include PARTPAT, ELPAT, ELEMID, GRIDID, ALIGN. It performs the following tasks: Assigns the attributes to the CWELD weld element created during the realization process, which is either a rod element [GA-GB] or mass element [GS] of the types PARTPAT, ELPAT, ELEMID, GRIDID or ALIGN. Creates the property collector with the name prop_<id> with the PWELD card associated with it. This property is referenced to the CWELD element created during realization. This script also updates the weld radius value in the CWELD card. The diameter value is either defined by the user on the spot weld panel, or is taken from the dvst (diameter versus thickness) file. Note : This script is called if the CWELD GA-GB and GS custom config welds and shell gap custom config welds across Nastran and OptiStruct user profiles.
OptiStruct cweld (GA-GB ELEMID)

CFG optistruct 84 cweld (GAGB ELEMID) *filter spot *head *body 0 rod 4 1 *post prop_cweld.tcl Description: Creates 1D CWELD element via GA-GB ELEMID. This realization also uses the prop_cweld.tcl property script. This script is called while creation of all the CWELD GA-GB and GS custom config welds in the spot weld panel. Theses include PARTPAT, ELPAT, ELEMID, GRIDID, ALIGN. It performs the following tasks: Assigns the attributes to the CWELD weld element created during the realization process, which is either a rod element [GA-GB] or mass element [GS] of the types PARTPAT, ELPAT, ELEMID, GRIDID or ALIGN. Creates the property collector with the name prop_<id> with the PWELD card associated with it. This property is referenced to the CWELD element created during realization. This script also updates the weld radius value in the CWELD card. The diameter value is either defined by the user on the spot weld panel, or is taken from the dvst (diameter versus thickness) file. Note : This script is called if the CWELD GA-GB and GS custom config welds and shell gap custom

Altair Engineering
config welds across Nastran and OptiStruct user profiles.
OptiStruct cweld (GS ELEMID)

CFG optistruct 85 cweld (GS ELEMID) *filter spot *head *body 0 mass 11 0 *post prop_cweld.tcl
Description: Creates 0D CWELD element via GS ELEMID. This realization also uses the prop_cweld.tcl property script. This script is called while creation of all the CWELD GA-GB and GS custom config welds in the spot weld panel. Theses include PARTPAT, ELPAT, ELEMID, GRIDID, ALIGN. It performs the following tasks: Assigns the attributes to the CWELD weld element created during the realization process, which is either a rod element [GA-GB] or mass element [GS] of the types PARTPAT, ELPAT, ELEMID, GRIDID or ALIGN. Creates the property collector with the name prop_<id> with the PWELD card associated with it. This property is referenced to the CWELD element created during realization. This script also updates the weld radius value in the CWELD card. The diameter value is either defined by the user on the spot weld panel, or is taken from the dvst (diameter versus thickness) file. Note : This script is called if the CWELD GA-GB and GS custom config welds and shell gap custom config welds across Nastran and OptiStruct user profiles.
OptiStruct cweld (GA-GB GRIDID)
Altair Engineering

CFG optistruct 86 cweld (GAGB GRIDID) *filter spot *head *body 0 rod 4 1 *post prop_cweld.tcl
Description: Creates 1D CWELD element via GA-GB GRIDID. This realization also uses the prop_cweld.tcl property script. This script is called while creation of all the CWELD GA-GB and GS custom config welds in the spot weld panel. Theses include PARTPAT, ELPAT, ELEMID, GRIDID, ALIGN. It performs the following tasks: Assigns the attributes to the CWELD weld element created during the realization process, which is either a rod element [GA-GB] or mass element [GS] of the types PARTPAT, ELPAT, ELEMID, GRIDID or ALIGN. Creates the property collector with the name prop_<id> with the PWELD card associated with it. This property is referenced to the CWELD element created during realization. This script also updates the weld radius value in the CWELD card. The diameter value is either defined by the user on the spot weld panel, or is taken from the dvst (diameter versus thickness) file. Note : This script is called if the CWELD GA-GB and GS custom config welds and shell gap custom config welds across Nastran and OptiStruct user profiles.
OptiStruct cweld (GS GRIDID)

Altair Engineering
CFG optistruct 87 cweld (GS GRIDID) *filter spot *head *body 0 mass 11 0 *post prop_cweld.tcl
Description: Creates 0D CWELD element via GS GRIDID. This realization also uses the prop_cweld.tcl property script. This script is called while creation of all the CWELD GA-GB and GS custom config welds in the spot weld panel. Theses include PARTPAT, ELPAT, ELEMID, GRIDID, ALIGN. It performs the following tasks: Assigns the attributes to the CWELD weld element created during the realization process, which is either a rod element [GA-GB] or mass element [GS] of the types PARTPAT, ELPAT, ELEMID, GRIDID or ALIGN. Creates the property collector with the name prop_<id> with the PWELD card associated with it. This property is referenced to the CWELD element created during realization. This script also updates the weld radius value in the CWELD card. The diameter value is either defined by the user on the spot weld panel, or is taken from the dvst (diameter versus thickness) file. Note : This script is called if the CWELD GA-GB and GS custom config welds and shell gap custom config welds across Nastran and OptiStruct user profiles.
OptiStruct cweld (GA-GB ALIGN)
Altair Engineering

CFG optistruct 88 cweld (GAGB ALIGN) *filter spot *head *body 0 rod 4 1 *post prop_cweld.tcl
Description: Creates 1D CWELD element via GA-GB ALIGN. This realization also uses a property script, please see prop_cweld.tcl for further details. This realization also uses the prop_cweld.tcl property script. This script is called while creation of all the CWELD GA-GB and GS custom config welds in the spot weld panel. Theses include PARTPAT, ELPAT, ELEMID, GRIDID, ALIGN. It performs the following tasks: Assigns the attributes to the CWELD weld element created during the realization process, which is either a rod element [GA-GB] or mass element [GS] of the types PARTPAT, ELPAT, ELEMID, GRIDID or ALIGN. Creates the property collector with the name prop_<id> with the PWELD card associated with it. This property is referenced to the CWELD element created during realization. This script also updates the weld radius value in the CWELD card. The diameter value is either defined by the user on the spot weld panel, or is taken from the dvst (diameter versus thickness) file. Note : This script is called if the CWELD GA-GB and GS custom config welds and shell gap custom config welds across Nastran and OptiStruct user profiles.
OptiStruct rbe3-celas1-rbe3

Altair Engineering
CFG optistruct 89 rbe3celas1-rbe3 *filter spot *head rbe3 1 0 dofs=123456 *body 0 spring 1 0
Description: Creates RBE3 element for the head and zero length CELAS1 element for the body. The head elements project and connect to the nodes of the adjoining shell elements. The degrees of freedom are constrained in the x, y, z, rot x, rot y, rot z for the dependant nodes.
OptiStruct adhesives
CFG optistruct 121 adhesives *filter area *style adhesive 1 *head rbe3 1 0 rigid 1 0 *body 1 hex8 1 1 penta6 1 1 *post prop_nastran_acm.tcl Description: Creates a row of hexa/penta elements for the body and numerous RBE2/RBE3 elements for the head. The head elements project and connect to the nodes of the adjoining shell elements. If there is significant curvature in the area connector then penta elements will be created, otherwise hexa elements will normally be created. If there is a direct normal project then an RBE2 elements will be used, if there are only non-normal projections then RBE3 elements will be created. This realization also uses the prop_Nastran_acm.tcl property script. This script is used while creation of acm equivalence/detached (T1+T2)/2 and shell gap custom config
Altair Engineering

welds in the spot weld panel from the Nastran and OptiStruct user profiles. It does the following tasks. Organizes the realized solid hexa weld elements created during realization process into hexa_comp_<id> components and the connected RBEs created as the *HEAD type are organized into the rbe3_comp_<id> components. This script will create the following properties collectors: Prop_<id1> : This property collector is created with the PSOLID card associated with it. This property collector is referenced in the above created component containing the solid hexa weld elements hexa_comp_<id> .
OptiStruct hemming
CFG OptiStruct 122 hemming *filter area *style adhesive 1 *head *body 0 rbe3 1 1
Description: Creates RBE3 elements for the body, the head elements project and connect to the nodes of the adjoining shell elements.
OptiStruct seam-quad (vertical+angled)

Altair Engineering
CFG OptiStruct 103 seam-quad (vertical+angled) *filter seam *style quad 1 *head *body 0 quad4 1 1
Description: Creates vertical and angled shell elements and projects to the adjoining shell elements. The thickness of the components are required as this is used to calculate the angle of the welds.
OptiStruct seam-quad (angled)

CFG OptiStruct 104 seam-quad (angled) *filter seam *style quad 2 *head *body 0 quad4 1 1
Description: Creates vertical shell elements and projects to the adjoining shell elements.
OptiStruct penta (mig)
Altair Engineering

CFG OptiStruct 105 penta (mig) *filter seam *style continuous 3 *head rbe3 1 0 *body 0 penta6 1 1
Description: Creates penta elements with RBE3 elements projecting and connecting to the surrounding shell elements. This realization supports many different use cases, including T-joint, angled T-joint, lap joint and butt joint.
OptiStruct hexa (adhesive)

CFG OptiStruct 106 hexa (adhesive) *filter seam *style continuous 3 *head rbe3 1 0 rigid 1 0 *body 0 hex8 1 1 Description: Creates a row of hexa elements for the body and numerous RBE2/RBE3 elements for the head. The head elements project and connect to the nodes of the adjoining shell elements. If there is a direct normal project then an RBE2 elements will be used, if there are only non-normal projections then RBE3 elements will be created. The hexa elements are projected so that they touch the shell elements of the connecting components.
OptiStruct HILOCK

Altair Engineering
CFG optistruct 111 HILOCK *filter spot *style fastener 1 *head *bodyext 0 bar2 1 1 weld 1 1 dofs=1456 *body 0 spring 6 0 dofs=2356 bar2 1 1 weld 1 1 dofs=156 spring 6 0 dofs=2356 *post prop_opt_nas_hilock.tcl Description: Creates 1D element construct existing out of RBAR, CBAR and CBUSH elements. The outer extensions represent the thicknesses of the outer shell elements. The inner nodes of the RBAR element are connected to the shell elements whereas the inner nodes of the CBAR elements are coincident to the shell nodes only. Between the appropriate connected and coincident nodes CBUSHes are created. Each outer node connects one CBAR and one RBAR. Each HILOCK connection gets an own coordinate system which z-axis is collinear to the HILOCK direction. All affected nodes are assigned to this coordinate system. This coordinate system is taken into account for the DOF definition of the CBAR elements, for the stiffness calculation of the CBUSH elements and for the DOF of the node constraint. This realization uses the shell properties and materials (PSHELL or PCOMP) and a predefined HILOCK material to calculate the exact position of the outer nodes and the stiffnesses of the PBUSH elements. If the realization requires a local remesh of the shell elements because there arent any shell nodes at the position of the connector projection, the connector realization will fail. This realization also uses the prop_opt_nas_hilock.tcl property script. This script is used while creation of HILOCK custom config welds in the spot weld panel from the Nastran and OptiStruct user profile. It does the following tasks. 1. 2. Organizes the realized 1D weld elements (RBAR, CBAR, CBUSH) created during realization process into a component named HiLock components. This script will create the following property collectors: HiLock_PBAR_<diameter> : This property collector is created with the PBAR card associated with it. The RBAR elements reference to this property. The attributes are calculated depending on the used diameter in the spot panel during realization. HiLock_PBUSH_<translational stiffness>_<rotational stiffness> : These property collectors are created with the PBUSH card associated with them. The CBUSH elements reference to this
Altair Engineering

property. The attributes are calculated depending on a predefined HILOCK material and the properties and materials of the connected shells (PSHELL and/or PCOMP). 3. This script will create the following load collector: HiLock_SPC6: This load collector is created and the SPCs, which are created for each HiLock will be moved into this collector. 4. This script will create the following system collector: HiLock : This system collector is created and the systems created during the realizations will be moved into this collector. If the system collector exists already the new created systems will be moved into the same collector. 5. This script will create the following material: HiLock_MAT1: This material will be assigned to the PBAR cards. The material is predefined in the script. Note: This script is called if the realization CFG nastran 111 HILOCK or CFG optistruct 111 HILOCK is used.

Altair Engineering
PAM-CRASH Connector Types

PAM-CRASH 2G plink (connector position)
CFG pamcrash2g 1 plink (connector position) *filter spot *head *body 0 mass 5 2 *post prop_plink.tcl Description: Creates a PLINK element. The PLINK is created at the connector location. This realization also uses the prop_plink.tcl property script. This script is called while creation of PLINK custom config welds in the spot weld panel inside PAMCRASH user interface. This script does the following tasks: Organizes the PLINK weld elements created during realization process into C_PLINK_PSCRIPT_<id1_id2> component with the PART_LINK card image associated to it. The id1 and id2 shown above refers to the ids of the link components with which the connector is connected to. Creates the M_PLINK_PSCRIPT_<id1_id2> material collector, with the MAT_LINK card image associated with it. This material collector is referenced in the above created component containing the PLINK weld elements. Updates the various attributes to the above created material/ property cards.
PAM-CRASH 2G plink (middle of the gap)

CFG pamcrash2g 2 plink (middle of the gap) *filter spot *head *body 0 mass 5 1 *post prop_plink.tcl Description: Creates a PLINK element. The PLINK is created at the center location between the two
Altair Engineering

components and is offset from the connector location. This realization also uses the prop_plink.tcl property script. This script is called while creation of PLINK custom config welds in the spot weld panel inside PAMCRASH user interface. This script does the following tasks: Organizes the PLINK weld elements created during realization process into C_PLINK_PSCRIPT_<id1_id2> component with the PART_LINK card image associated to it. The id1 and id2 shown above refers to the ids of the link components with which the connector is connected to. Creates the M_PLINK_PSCRIPT_<id1_id2> material collector, with the MAT_LINK card image associated with it. This material collector is referenced in the above created component containing the PLINK weld elements. Updates the various attributes to the above created material/ property cards.
PAM-CRASH 2G bolt (spider)

CFG pamcrash2g 54 bolt (spider) *filter bolt *style bolt 1 *head *body 0 rigidlink 1 1 Description: Creates an RBODY element. The body element projects and connect to the nodes of the adjoining shell elements.

Altair Engineering
RADIOSS Connector Types

RADIOSS type2 (spring)
CFG radioss 2 type2 (spring) *filter spot *head plot 1 0 *body 0 spring 1 1 *post prop_type2.tcl
Description: Creates a SPRING2N element for the body and plot elements for the head, the plot elements are created for visualization purposes and find operations. This realization also uses the prop_type2.tcl property script. This script is used while creation of Radioss [Type2 Spring] in the spot weld panel. It does the following tasks. Organizes the realized weld elements to the respective components based upon the link they are connected to. E.g. if a weld is created between comp_1(1) and comp_2(2) it creates a component collector with the name RW^^_<id1_id2> and organizes all the welds created as links between these two components into this collector. Creates the following properties collectors: RW^^_<id1_id2>: This properties collector with the P13_SPR_BEAM incase of R-BLOCK and SectBemSpr in case of R-FIX solver subtype is associated with it as the card image.
Creates sets in the following order: I1_M_<id1_id2> : This contains the master as the FIRST link component id to which the weld is connected to. I1_S_<id1_id2> : This set contains the node id of the projected spring element to the above component link as the slave node N1. I2_M_<id1_id2> : This contains the master as the SECOND link component id to which the weld is connected to. I2_S_<id1_id2> : This set contains the node id of the projected spring element to the above component link as the slave node N2.
Creates two interfaces Groups (interfaces) for the spring weld elements created between the same component links by the name RW^^1_<id1_id2> : This references the above created sets that contain the ids of first node NI and
Altair Engineering

first component Link C1. RW^^1_<id1_id2> : This references the above created sets that contain the ids of second node N2 and second component Link C2.
Creates a plot named Shear_Normal_Force_Plot with two curves from the Normal Force Function [named RW^^FN_1.0] and Shear Force Function [named RW^^FS_2.5], the values of which are read from the Radiossweld_config.ini file.
RADIOSS bolt (general)

CFG radioss 52 bolt (general) *filter bolt *style bolt 0 *head rigidlink 1 10 *body 0 spring 1 1 *post prop_radioss_rigidupdate. tcl Description: Creates RBODY elements for the head and SPRING2N body. The head elements project and connect to the nodes of the adjoining shell elements which form the hole. The connector location can either be on the edge of the hole, center of the hole, midpoint in between the two holes or on the second row of nodes which form the washer layer. This realization also the prop_radioss_rigidupdate.tcl property script. This script is run for all the rigid/rigidlink weld configurations in the Radioss user profile. It creates the sets of all the slave node ids of the rbodies created during the realization process, and assigns the GRNOD card image to them. It also updates some attributes of these cards.
RADIOSS hinge

Altair Engineering
CFG radioss 53 hinge *filter bolt *style bolt 0 *head rigidlink 1 10 *body 0 spring 1 1 dofs=4 *post prop_radioss_rigidupdate. tcl Description: Creates RBODY elements for the head and SPRING2N body. The rot x degree of freedom is released so that the RBODY can rotate. The head elements project and connect to the nodes of the adjoining shell elements which form the hole. The connector location can either be on the edge of the hole, center of the hole, midpoint in between the two holes or on the second row of nodes which form the washer layer. This realization also the prop_radioss_rigidupdate.tcl property script. This script is run for all the rigid/rigidlink weld configurations in the Radioss user profile. It creates the sets of all the slave node ids of the rbodies created during the realization process, and assigns the GRNOD card image to them. It also updates some attributes of these cards.
RADIOSS bolt (spider)

CFG radioss 54 bolt (spider) *filter bolt *style bolt 1 *head *body 0 rigidlink 1 1 *post prop_radioss_rigidupdate. tcl
Description: Creates an RBODY element. The element projects and connect to the nodes of the adjoining shell elements which form the hole, the RBODY element is joined at the midpoint of the bolted connection.
Altair Engineering

The connector location can either be on the edge of the hole, center of the hole, midpoint in between the two holes or on the second row of nodes which form the washer layer. This realization also the prop_radioss_rigidupdate.tcl property script. This script is run for all the rigid/rigidlink weld configurations in the Radioss user profile. It creates the sets of all the slave node ids of the RBODYs created during the realization process, and assigns the GRNOD card image to them. It also updates some attributes of these cards.
RADIOSS bolt (cylinder rigid)

CFG radioss 60 bolt (cylinder rigid) *filter bolt *style bolt 3 *head *body 0 rigidlink 1 1 *post prop_radioss_rigidupdate. tcl Description: Creates an RBODY element. Please reference Cylinder Bolt help for further details. This realization also the prop_radioss_rigidupdate.tcl property script. This script is run for all the rigid/rigidlink weld configurations in the Radioss user profile. It creates the sets of all the slave node ids of the RBODYs created during the realization process, and assigns the GRNOD card image to them. It also updates some attributes of these cards.
RADIOSS bolt (cylinder spring)

CFG radioss 61 bolt (cylinder spring) *filter bolt *style bolt 3 *head rigidlink 1 1

Altair Engineering
*body 0 spring 1 1 *post prop_radioss_rigidupdate. tcl Description: Creates an RBODY elements and a zero length SPRING2N element. Please reference Cylinder Bolt help for further details. This realization also the prop_radioss_rigidupdate.tcl property script. This script is run for all the rigid/rigidlink weld configurations in the Radioss user profile. It creates the sets of all the slave node ids of the RBODYs created during the realization process, and assigns the GRNOD card image to them. It also updates some attributes of these cards.
RADIOSS type2 (adhesive-spring)

CFG radioss 62 type2 (adhesivespring) *filter area *head plot 1 0 *body 0 spring 1 1 *post prop_type2.tcl Description: Creates multiple SPRING2N elements for the body and plot elements for the head, the plot elements are created for visualization purposes and find operations. This realization also uses the prop_type2.tcl property script. This script is used while creation of Radioss [Type2 Spring] in the spot weld panel. It does the following tasks. Organizes the realized weld elements to the respective components based upon the link they are connected to. E.g. if a weld is created between comp_1(1) and comp_2(2) it creates a component collector with the name RW^^_<id1_id2> and organizes all the welds created as links between these two components into this collector. Creates the following properties collectors: RW^^_<id1_id2>: This properties collector with the P13_SPR_BEAM incase of R-BLOCK and SectBemSpr in case of R-FIX solver subtype is associated with it as the card image.
Altair Engineering

Creates sets in the following order: I1_M_<id1_id2> : This contains the master as the FIRST link component id to which the weld is connected to. I1_S_<id1_id2> : This set contains the node id of the projected spring element to the above component link as the slave node N1. I2_M_<id1_id2> : This contains the master as the SECOND link component id to which the weld is connected to. I2_S_<id1_id2> : This set contains the node id of the projected spring element to the above component link as the slave node N2.
Creates two interfaces Groups (interfaces) for the spring weld elements created between the same component links by the name RW^^1_<id1_id2> : This references the above created sets that contain the ids of first node NI and first component Link C1. RW^^1_<id1_id2> : This references the above created sets that contain the ids of second node N2 and second component Link C2.
Creates a plot named Shear_Normal_Force_Plot with two curves from the Normal Force Function [named RW^^FN_1.0] and Shear Force Function [named RW^^FS_2.5], the values of which are read from the Radiossweld_config.ini file.

Altair Engineering
Model Setup
This section describes how to build a finite element model. In general, the following building process is used: Create collectors Obtain line and surface geometry from an external file, or hand digitize the data Reconcile conflicts in the geometry and prepare it for use Build the model by using element-building panels Verify the quality of the model Create boundary conditions and systems
The following building processes are described: Importing geometry Creating Collectors Creating Geometry Data Temporary Nodes Picking Surfaces Editing Surfaces Associativity Geometry Cleanup Applying Loads Creating Systems Control Cards Boundary Conditions
Altair Engineering

Properties
This section contains information regarding regarding HyperLaminate, the Laminate Browser, and the HyperLaminate Solver, as well as HyperBeam and the HyperBeam environment.

Altair Engineering
HyperLaminate
HyperLaminate is a HyperMesh module that facilitates the creation, review and edition of composite laminates. In support of this process certain materials and design variables are also supported by the HyperLaminate module. The HyperLaminate Solver (HLS), which is accessed through the HyperLaminate module, uses classical laminated plate theory for simple in-plane analysis of composite laminates. The current HyperMesh database is only updated with information from the current HyperLaminate session on exit from HyperLaminate (except with Abaqus materials, which are updated simultaneously in HyperMesh and HyperLaminate), so while it is possible to work in HyperMesh while HyperLaminate is running, this is not advisable. Any changes made to those entities which HyperLaminate touches (materials, component collectors and design variables) may result in synchronization problems and loss of data. HyperLaminate is launched from within HyperMesh either from the HyperLaminate button on the 2D page of the main menu, or by selecting HyperLaminate from the Materials or Properties pull-down menus. The HyperLaminate module is supported for the OptiStruct, Nastran, Ansys and Abaqus user profiles.
See also HyperLaminate Environment HyperLaminate Menus HyperLaminate Toolbar Laminate Browser Define/Edit Pane Review Pane HyperLaminate Solver
Altair Engineering

Environment
The HyperLaminate environment consists of five general areas, as shown here:
Menus
The HyperLaminate menu bar contains five menus that allow you to manage files, edit materials, laminates, HLS loadcases and design variables, change views, and access on-line help. The HyperLaminate toolbar contains five tools that allow you to generate new materials, laminates, HLS loadcases or design variables, and to cut, copy, paste, and delete entries in text boxes. This browser, located on the left side of the HyperLaminate window, provides a vertical tree view of materials, laminates, HLS loadcases and size design variables in your model. Left-clicking on an entity populates the Define/Edit and Review panes with details of that branch. Right-clicking on a branch offers context-sensitive operations for that branch.
Toolbar
Laminate Browser
Define/Edit Pane
This is the central pane of the HyperLaminate module. Here users may enter or change data related to a material, laminate, HLS loadcase or design variable definition (depending on the selected branch in the laminate browser).

Altair Engineering
Review Pane
This is the right-hand pane of the HyperLaminate module. The Review/ Results pane has a number of tabs that display the current state of the selected branch.
Altair Engineering

Menus
The HyperLaminate menu bar contains five menus.
The following chart lists each menu option. File New Generates a new entity, depending on the selected sub-topic in the Laminate Browser. Exports material and laminate information to a text file. This text file can be printed. Exit HyperLaminate. At this point the current HyperMesh database is updated with the information in the current HyperLaminate session. Edit Cut Removes the selected data from an entry field and places it on the clipboard for pasting. Can also remove rows from a ply lay-up order table and place these on the clipboard for pasting. Copy Places selected data from an entry field on the clipboard for pasting. Can also place rows from a ply lay-up order table on the clipboard for pasting. Paste Pastes data from the clipboard in selected entry fields. Can also paste rows from the clipboard above selected rows on a ply lay-up order table. Delete When the cursor is active in the Laminate Browser, this deletes the selected entity from the Laminate Browser. (A dialogue is displayed to confirm the deletion.) When the cursor is active in the Define/Edit pane, this deletes the selected text from a text box or the selected rows from a ply lay-up order table. Tools Laminate Options Displays the Laminate Options dialog.
Export to File
Exit

Altair Engineering
This dialog allows you to select defaults for new Laminates for: color convention repetitions ply thickness common thickness HLS Options Displays the HLS Options dialog.
This allows you to retain the input and result files for the HyperLaminate Solver. Youcan also choose the location these files are written to. The default behaviour is to delete these files once HLS is run. View Toolbar Status Bar Display/hide toolbar. Display/hide status bar.
Altair Engineering

Help
About HyperLaminate Help Topics
Displays version, contact, and copyright information.
Activates the HyperLaminate online help.

Altair Engineering
Toolbar
The HyperLaminate toolbar is located below the menu bar and its display is controlled by the Toolbar option under the View pull-down menu. The toolbar is shown and described here.
Icon
Name New
Function Generates a new entity, depending on the selected sub-topic in the Laminate Browser. Removes the selected data from an entry field and places it on the clipboard for pasting. Can also remove rows from a ply lay-up order table and place these on the clipboard for pasting.
Cut
Copy
Places selected data from an entry field on the clipboard for pasting. Can also place rows from a ply lay-up order table on the clipboard for pasting.
Paste
Pastes data from the clipboard in selected entry fields. Can also paste rows from the clipboard above selected rows on a ply lay-up order table.
Delete
When the cursor is active in the Laminate Browser, this deletes the selected entity from the Laminate Browser. (A dialogue is displayed to confirm the deletion.) When the cursor is active in the Define/Edit pane, this deletes the selected text from a text box or the selected rows from a ply lay-up order table.
Altair Engineering

Laminate Browser
The Laminate browser, located on the left side of the HyperLaminate window, provides a vertical tree view of the materials, laminates, and HLS loadcases in your model. For the OptiStruct and Nastran user profiles the browser also includes size design variables. On launching HyperLaminate, the Laminate Browser is populated with all the relevant materials, laminate definitions, HLS loadcases, and size design variables existing in the HyperMesh database, for the active user profile. The data is presented in a slightly different format for the various user profiles as shown here:
OptiStruct & Nastran
Ansys
Abaqus
The Laminate Browser is organized in a three-level hierarchy: 1. 2. At the highest level are the entity types: Materials, Laminates, HLS loadcases, and Design Variables. At the intermediate level are the entity sub-types or card images. These are: a. for OptiStruct and Nastran: i. Materials: MAT1, MAT2 and MAT8
ii. Laminates: PCOMP and PCOMPG iii HLS loadcases: In-plane loads and In-plane strains

Altair Engineering
iv. Design variables: DESVAR b. for Ansys: i. ii. Materials: MATERIAL and MPDATA Laminates: SHELL91, SHELL99, SOLID46 and SOLID 191
iii HLS loadcases: In-plane loads and In-plane strains c. for Abaqus: i. Materials: ABAQUS_MATERIAL
ii. Laminates: SOLIDSECTION, SHELLSECTION and SHELLGENERALSECTION iii HLS loadcases: In-plane loads and In-plane strains 3. At the lowest level are the entities, displayed with the names as defined by you.
Left- or right-clicking on a branch in the browser selects that branch and it becomes highlighted. When an entity (lowest level branch in the tree hierarchy) is selected, the Define/Edit and Review/Results panes are populated with details related to that entity. It is then possible to alter and update the entity definition. Right-clicking on an already selected (highlighted) branch offers context-sensitive operations for that branch. At the highest level (entity types) no operations are available. At the intermediate level (entity sub-types) only one operation is available: New, which will create a new entity of the selected sub-type. For example, if MAT1 is selected and you right-click it and choose New; a new MAT1 entity is created. At the lowest level (entities) three operations are available; Rename, which allows the entity to be renamed; Duplicate, which creates a copy of the selected entity; and Delete, which will delete the selected entity. For Laminates a fourth operation is available: to export HLS results for the selected laminate to a file. From the Laminate Browser it is possible to: Create entities Review entities Update entities Rename entities Duplicate entities Delete Entities
Altair Engineering

Create Entities
There are three options for creating new entities in HyperLaminate: 1. 2. Select an intermediate level branch (an entity sub-type or card image) from the browser tree. Right-click selected entity sub-type. A context-sensitive menu appears with one option: New 3. Click New. A new entity appears under the selected branch. Or 1. 2. Select an intermediate level branch (an entity sub-type or card image) from the browser tree. Select New from the File pull-down menu. A new entity appears under the selected branch. Or 1. 2. Select an intermediate level branch (an entity sub-type or card image) from the browser tree. Click the New icon, , on the toolbar.
A new entity appears under the selected branch. A default name and ID are assigned to each newly created entity.

Altair Engineering
Review and Update Entities

1. Right-or left-click an entity (lowest level in tree hierarchy) in the Laminate Browser tree to select it. The selected entity is highlighted. The Define/Edit and Review/Results panes are populated with details of that entity. 2. Make the desired changes to the entity definition in the Define/Edit pane and click Apply or Update Laminate to update the entity.
Altair Engineering

Rename Entities
1. 2. Right- or left-click an entity (lowest level in tree hierarchy) in the Laminate Browser tree to select it. Right-click the selected entity. A context-sensitive menu appears with three options: Rename, Duplicate, and Delete. 3. Click Rename. The name of the selected entity in the Laminate Browser switches to a text box. 4. Enter the desired new name in the text box. You can also rename an entity by altering the relevant field in the Define/Edit pane and then clicking Apply or Update Laminate.

Altair Engineering
Duplicate Entities
1. 2. Right- or left-click an entity (lowest level in tree hierarchy) in the Laminate Browser tree to select it. Right-click the selected entity. A context sensitive menu appears with several options. 3. Click Duplicate. A duplicate of the entity is created and appears in the Laminate Browser.
Altair Engineering

Delete Entities
There are three options for deleting entities in HyperLaminate: 1. 2. Right- or left-click an entity (lowest level in tree hierarchy) in the Laminate Browser tree to select it. Right-click the selected entity. A context-sensitive menu appears with several options. 3. Click Delete. A confirmation dialog is displayed. 4. Click Yes. The entity is deleted and disappears from the Laminate Browser. Or 1. 2. Right-or left-click an entity (lowest level in tree hierarchy) in the Laminate Browser tree to select it. Select Delete from the Edit pull-down menu. A confirmation dialog is displayed. 3. Click Yes. The entity is deleted and disappears from the Laminate Browser. Or 1. 2. Right- or left-click an entity (lowest level in tree hierarchy) in the Laminate Browser tree to select it. Click the Delete icon, , on the toolbar.
A confirmation dialog is displayed. 3. Click Yes. The entity is deleted and disappears from the Laminate Browser. Note : Abaqus materials that are created but not defined (they appear in a red font in Laminate Browser) may not be deleted, as they do not really exist. To delete these undefined materials, either complete their definition (by clicking Edit which takes you to the HyperMesh material card previewer) or exit and restart HyperLaminate (in which case the undefined materials are purged).

Altair Engineering
HyperLaminate Solver
The HyperLaminate Solver (HLS) uses classical laminated plate theory to analyze composite laminates subject to various in-plane and thermal loading conditions. The solver is integrated into the HyperLaminate module of HyperMesh. The following functionality is provided: 1. 2. 3. 4. 5. to define and edit HLS loadcases to select a subset of HLS loadcases for analysis for each laminate to perform the analysis to review the results of the analysis for each laminate to export the results to an external file
When a laminate is selected from the Laminate browser, an Assign LoadCases button is present in the lower left corner of the Define/Edit pane. This button launches the LoadCase Definition GUI, allowing the user to select which HLS loadcases the current laminate will be analyzed for.
The LoadCase Definition dialog allow s you to select loadcases for the current laminate.
Once the desired loadcases are selected, the analysis can be performed for the current laminate by clicking the Calculate button. Once the analysis is complete several results tabs will appear in the Review/Results pane, namely: Stiffness/Material Matrix Mid-Plane Results Global System Results Material System Results Principal Results Invariant Results These results will remain so long as the laminate is not updated. Once a laminate is updated, the results will no longer be valid and therefore the results tabs are removed. Clicking the Calculate button will re-launch the HyperLaminate Solver and populate the results tabs for the updated laminate definition.
Altair Engineering


Altair Engineering
To Select HLS loadcases for the current laminate

1. Click Assign LoadCases button. The LoadCase Definition dialog opens. 2. 3. 4. Check the boxes corresponding to the loadcases to be selected. Click Assign to save the information. Click Close to close the dialog.
Altair Engineering

Define/Edit Pane
The Define/Edit Pane, the central pane of the HyperLaminate window, allows you to edit the definition of the selected entity. On selecting an entity in the Laminate Browser the Define/Edit pane is populated with the current definition. The configuration of the Define/Edit pane differs for different user profiles and sub-types (card images). Materials For OptiStruct, Nastran and Ansys materials, all material property information for the selected material may be edited in the Define/Edit pane. Once the desired changes have been made, clicking Apply will save those changes for the current HyperLaminate session (it is important to remember that the HyperMesh database is only updated on exit from HyperLaminate). To reset all material property fields to zero you can click the Clear button. Below are screenshots showing the Define/Edit pane for an OptiStruct MAT8 definition and an Ansys MATERIAL definition:
OptiStruct Materials MAT8
Ansys Materials MATERIAL
For Abaqus materials, you may rename or redefine the color of the material in the Define/Edit pane, but to fully define the material properties you must click the Edit button. Clicking the Edit button takes you to the material card previewer in the HyperMesh GUI, where you can review and alter the definition of the selected material. Once you have finished reviewing/editing the material, clicking return will return you to the HyperLaminate GUI. As with the other user profiles, to reset all material property fields to zero you can click the Clear button. A screenshot of the Define/Edit pane for an Abaqus material is shown here:

Altair Engineering
Abaqus Materials ABAQUS_MATERIAL
Laminates For laminates, the Define/Edit pane allows the laminate name, HyperMesh entity color, stacking sequence convention, and the ply lay-up order to be edited. In addition, HLS loadcases may be selected (through the Assign LoadCases button) and solved (through the Calculate button) for the current laminate. This is for all supported user profiles and laminate sub-types. An example of the Define/Edit pane for an Abaqus SOLIDSECTION laminate is shown here:
Altair Engineering

Abaqus Laminates SOLIDSECTION
There are a number of options for Convention for the stacking sequence: a. b. Total: The Ply lay-up order table describes the laminate in its entirety. Symmetric: The Ply lay-up order table describes the bottom half of the laminate. The top half of the laminate is the mirror image of the bottom half. The ply angles used for the top half are the same as the ply angles used in the bottom half. Antisymmetric: The Ply lay-up order table describes the bottom half of the laminate. The top half of the laminate is the mirror image of the bottom half. The ply angles used for the top half have the opposite sign to the ply angles used in the bottom half (but 0, 90, 180, 270, and 360 remain as 0, 90, 180, 270, and 360, respectively). Symmetric-Midlayer: The Ply lay-up order table describes the bottom half of the laminate and a midlayer (or core). The midlayer is the last ply defined in the table. The top half of the laminate is the mirror image of the bottom half. The midlayer is not reflected. The ply angles used for the top half are the same as the ply angles used in the bottom half. Due to the midlayer, the total number of plies is always odd. Antisymmetric-Midlayer: The Ply lay-up order table describes the bottom half of the laminate and
c.
d.
e.

Altair Engineering
a midlayer (or core). The midlayer is the last ply defined in the table. The top half of the laminate is the mirror image of the bottom half. The midlayer is not reflected. The ply angles used for the top half have the opposite sign to the ply angles used in the bottom half (but 0, 90, 180, 270, and 360 remain as 0, 90, 180, 270, and 360, respectively). Due to the midlayer, the total number of plies is always odd. f. Repeat: The Ply lay-up order table describes a single sub-laminate which is repeated a number of times. The number of repetitions is determined by the number entered in the Repetitions: field (which is activated when this Convention is chosen).
It is possible to choose between constant and variable ply thickness for certain user profiles; variable ply thickness allows up to four nodal thicknesses to be defined for each ply. An example of the Define/Edit pane for an Ansys SHELL99 laminate with variable ply thickness is shown, following:
Ansys Laminates SHELL99
It is also possible to choose a common thickness for all plies. Common thickness gives every ply in the laminate the same thickness. The Ply lay-up order table describes the laminate from the bottom ply (most negative Z) moving upwards (increasing in positive Z direction). Each row of the table defines the material, ply thickness and ply orientation for a number of plies (defined by the No. of repetitions field and based on the selected Convention). The number of integration points for each ply (or group of plies) is also provided in the table.
Altair Engineering

This number is used by the HyperLaminate Solver, as well as the external FEA solver when applicable. Rows are added to the table by completing the Add/Update plies: entry fields and clicking the Add New Ply button. Rows may be inserted in the table, either above or below selected rows (choose from the Above Selected or Below Selected radio buttons), by clicking the Insert New Ply button. Rows may be cut, copied from, pasted to, or deleted from the table using the toolbar, pull-down Edit menu, or CTRL+X, CTRL+C, CTRL+V, and CTRL+D respectively. Select multiple rows by selecting one row and then, with the CTRL key held down, selecting other rows (alternatively, multiple rows may be selected with the SHIFT key held down; this will retain the current selection and add all the rows between the current selection and the newly selected row). Rows are always pasted above the selected rows when multiple rows are selected the clipboard contents are pasted above each selected row. All fields in the Ply lay-up order table may be edited. It is also possible to edit multiple rows at once. Select multiple rows as described in the previous paragraph. When multiple rows are selected, the Add/Update plies: fields are populated with the information common to the selected rows. Blank fields indicate that not all of the selected rows contain the same values for that field. Changes can be made to the Add/Update plies: fields and Update Selection can be clicked to update the selected rows with the updated information (no changes occur to the selected rows for blank fields). For the OptiStruct and Nastran user profiles it is possible to request stress and failure theory output. Each row of the Ply lay-up order table has an SOUT field, which when set to YES includes the plies described by that row in the stress output and the failure theory calculation. It is possible to set the SOUT field individually for each row, or for all rows at once through the Output ply stress results: field under the Stress and failure theory output: heading. Once one or more SOUT fields are set to YES it is possible to activate failure theory calculation, by checking the Failure Theory check-box, selecting a theory from the pull-down list and defining an Interlaminar shear allowable: value. An example of the Define/Edit pane for an OptiStruct PCOMPG laminate is shown below:

Altair Engineering
OptiStruct Laminates PCOMPG
The Ply lay-up order table for the OptiStruct and Nastran PCOMPG laminate sub-type is different from other laminate sub-types in that it has a GPLYID field. This field is used to assign a global ply ID to a ply definition (the global ply ID is a post-processing aid). As this ID should not be repeated within the same laminate, the No. of repetitions field is not available for PCOMPG. For PCOMPG each row in the Ply lay-up order table should represent a single ply so only the Total stacking convention should be used for PCOMPG, but this is not enforced in the GUI. For the OptiStruct and Nastran user profiles it is possible to assign a design variable to a thickness or orientation field in the Ply lay-up order table. Checking the Optimization check-box expands the Ply lay-up order table, adding extra fields to the right of the Thickness T1 and Orientation 0 fields. Design variables may be selected in these extra fields. Selecting a design variable to the right of a thickness or orientation assigns the selected design variable to that thickness or orientation. Click Update Laminate to apply all the changes for the current HyperLaminate session (it is important to remember that the HyperMesh database is only updated on exit from HyperLaminate). The Define/Edit pane for Laminates also provides access to the HyperLaminate Solver. A number of
Altair Engineering

inplane loading scenarios (HLS loadcases) may be solved for a given laminate. The HLS loadcases are selected on the LoadCase Definition dialog, which is launched by clicking on the Assign LoadCases button.
LoadCase Definition GUI
HLS loadcases with a check in the Active column are selected for the current laminate. Different HLS loadcases may be selected for different laminates. Having selected the appropriate loadcases, click Apply and then Close to exit the dialog. Once the loadcases are selected, clicking on the Calculate button launches the HyperLaminate Solver. The Review/Results pane is then populated with several tabs containing the HyperLaminate Solver results. As shown here:

Altair Engineering
Hyperlaminte Solver results
HLS loadcases For all user profiles the HLS loadcases branch allows various in-plane loading scenarios to be defined and stored. The loading scenarios can be either load based or strain based. All information for the selected HLS loadcase may be edited in the Define/Edit pane. Once the desired changes have been made, clicking Apply will save those changes for the current HyperLaminate session (it is important to remember that the HyperMesh database is only updated on exit from HyperLaminate). To reset all fields for the selected HLS loadcase to zero, you can click the Clear button.
Altair Engineering

Design Variables For the OptiStruct and Nastran user profiles, the DESVAR design variable card is supported in HyperLaminate. All information for the selected design variable may be edited in the Define/Edit pane. Once the desired changes have been made, clicking Apply will save those changes for the current HyperLaminate session (it is important to remember that the HyperMesh database is only updated on exit from HyperLaminate). To reset all fields for the selected design variable to their default values, you can click the Clear button.

Altair Engineering
To Define a new HyperLaminate Solver loadcase

1. Use one of the following three methods to create a new HLS loadcase in HyperLaminate: Method 1: 1. Select a sub-type under the HLS loadcases branch of the Laminate browser. 2. Right-click the selected sub-type. A context-sensitive menu appears with one option: New. 3. Click New. A new loadcase appears under the selected branch. Method 2: 1. 2. Select a sub-type under the HLS loadcases branch of the Laminate browser. Select New from the File pull-down menu. A new loadcase appears under the selected branch. Method 3: 1. 2. Select a sub-type under the HLS loadcases branch of the Laminate browser. Click the new icon, , on the toolbar.
A new loadcase appears under the selected branch. A default name and ID are assigned to newly created HLS loadcases. 2. 3. 4. 5. The newly created loadcase is automatically selected in the Laminate browser and the Define/Edit pane takes on the appropriate configuration. If desired, a new name for the laminate may be entered in the Loadcase: field. Provide the loadcase definition by filling in the entry fields in the Define/Edit pane. Click Apply to save the changes for the current HyperLaminate session. (It is important to remember that the HyperMesh database is only updated on exit from HyperLaminate.)
Altair Engineering

To Review or modify an existing HL Solver loadcase

1. Select the loadcase to be edited from the Laminate Browser. The Define/Edit and Review/Results panes are populated with the selected loadcase definition. 2. Edit the data fields in the Define/Edit pane. Data may be cut, copied from, pasted to, or deleted from the data fields using the toolbar, pull-down Edit menu, or CTRL+X, CTRL+C, CTRL+V, and CTRL+D respectively. Clicking Clear will reset all fields to zero. Each change is reflected in the Review/Results pane. 3. 4. If desired, a new name for the loadcase may be entered in the Loadcase: field Click Apply to save the changes for the current HyperLaminate session. (It is important to remember that the HyperMesh database is only updated on exit from HyperLaminate.) The final loadcase definition is displayed on the Review tab.

Altair Engineering
Review/Results Pane
The Review/Results pane (the right-hand pane of the HyperLaminate window) allows you to review the information pertaining to the selected entity as well as displaying HyperLaminate Solver results for laminates. On selecting an entity in the Laminate Browser, the Review/Results pane displays the current definition of that entity. Materials For OptiStruct, Nastran and Ansys materials, all material property information for the selected material is displayed in the Review/Results pane. This information is updated as the definitions are altered in the Define/Edit pane. For Abaqus materials, no information is displayed in the Review/Results pane. Laminates For laminate definitions for all user profiles, the Review/Results pane a Review tab and several results tabs: Stiffness/Material Matrix Mid-Plane Results Global System Results Material System Results Principal Results Invariant Results Information displayed on these results tabs is for the saved laminate definition, and is removed when the Update Laminate button is clicked. The results tabs reappear if you run the HyperLaminate Solver for the updated definition by clicking the Calculate button. The Review tab is headed by the laminate name, the total number of plies in the laminate, and the total thickness of the laminate. This is followed by a description of the laminate, listing the plies in order from the bottom ply (most negative z), showing a graphical representation of each plys orientation and listing the referenced material, thickness, and orientation. The Stiffness/Material Matrix tab provides the two sets of matrices. The first set of matrices are the composite shell stiffness matrices, more commonly referred to as the ABD matrices. The second set of matrices are the equivalent material matrices. These are used by many finite element solvers to represent the laminated composite as a homogenized shell. The remaining results tabs present results of the HyperLaminate Solver. HLS loadcases For all user profiles, information for the selected HLS loadcase is displayed in the Review/Results pane. This information is updated as the definitions are altered in the Define/Edit pane. Design Variables For OptiStruct and Nastran user profiles, information for the selected design variable is displayed in the Review pane. This information is updated as the definitions are altered in the Define/Edit pane.
Altair Engineering


Altair Engineering
Define a New Material:

1. Use one of the following three methods to create a new material in HyperLaminate: Method 1: 1. 2. Select a sub-type under the material branch of the Laminate browser. Right-click the selected material sub-type. A context sensitive menu appears with one option: New 3. Click New. A new material appears under the selected branch. Method 2: 1. 2. Select a sub-type under the material branch of the Laminate browser. Select New from the File pull-down menu. A new material appears under the selected branch. Method 3: 1. 2. Select a sub-type under the material branch of the Laminate browser. Click the new icon, , on the toolbar.
A new material appears under the selected branch. A default name and ID are assigned to newly created materials. 2. The newly created material is automatically selected in the Laminate browser and the Define/Edit pane takes on the appropriate configuration for the selected material sub-type.
For the OptiStruct, Nastran and Ansys user profiles 3. 4. 5. If desired, a new name for the material may be entered in the Material: field or the material color may be altered by clicking the color swatch and selecting a new color from the pop-up color palette. Provide the material definition by filling in the entry fields in the Define/Edit pane. Click Apply to save the changes for the current HyperLaminate session. (It is important to remember that the HyperMesh database is only updated on exit from HyperLaminate.)
For the Abaqus user profile: 3. 4. Click Edit and provide the material definition in the HyperMesh card previewer. Click return. This returns you to the HyperLaminate GUI 5. 6. If desired, a new name for the material may be entered in the Material: field or the material color may be altered by clicking the color swatch and selecting a new color from the pop-up color palette. Click Apply to save the changes. Note: It is not possible to rename an Abaqus material until after it has been defined (edited). Also it is not possible to create a new Abaqus material if an undefined material definition already
Altair Engineering

exists (appears in a red font in Laminate Browser).

Altair Engineering
Review or Modify an Existing Material

1. Select the material to be edited from the Laminate Browser. The Define/Edit and Review/Results panes are populated with the selected material definition. For the OptiStruct, Nastran and Ansys user profiles: 2. Edit the data fields in the Define/Edit pane. Data may be cut, copied from, pasted to, or deleted from the data fields using the toolbar, pull-down Edit menu, or CTRL+X, CTRL+C, CTRL+V, and CTRL+D respectively. Clicking Clear will reset all fields to zero. Each change is reflected in the Review/Results pane. 3. 4. If desired, a new name for the material may be entered in the Material: field, or the material color may be altered by clicking the color swatch and selecting a new color from the pop-up color palette. Click Apply to save the changes for the current HyperLaminate session. (It is important to remember that the HyperMesh database is only updated on exit from HyperLaminate.) The final material definition is displayed in the Review tab. For the Abaqus user profile: 2. 3. 4. Click Edit to see the material definition in the HyperMesh card previewer. Make all desired changes to the material definition in the card previewer. Click return. This returns you to the HyperLaminate GUI. 5. 6. If desired, a new name for the material may be entered in the Material: field or the material color may be altered by clicking the color swatch and selecting a new color from the pop-up color palette. Click Apply to save the changes.
Altair Engineering

Define a New Laminate

1. Use one of the following three methods to create a new laminate in HyperLaminate: Method 1: 1. 2. Select a sub-type under the laminates branch of the Laminate Browser. Right-click the selected sub-type. A context-sensitive menu appears with one option: New 3. Click New. A new laminate appears under the selected branch. Method 2: 1. Select a sub-type under the laminates branch of the Laminate browser. 2. Select New from the File pull-down menu. A new laminate appears under the selected branch. Method 3: 1. 2. Select a sub-type under the laminates branch of the Laminate browser. Click the new icon, , on the toolbar.
A new laminate appears under the selected branch. A default name and ID are assigned to newly created laminates. 2. 3. The newly created laminate is automatically selected in the Laminate browser and the Define/Edit pane takes on the appropriate configuration for the selected laminate sub-type. If desired, a new name for the laminate may be entered in the Laminate name: field or the component color may be altered by clicking the color swatch and selecting a new color from the pop-up color palette. For OptiStruct and Nastran user profiles, define the Stress and failure theory output: information as desired. For all user profiles, define the Stacking sequence convention: information. a) For Convention:, select one of the following stacking sequence conventions. Total Symmetric Antisymmetric Symmetric-Midlayer Antisymmetric-Midlayer Repeat If you select Repeat, specify how many times you want to repeat the entire block of entry rows. b) For Ply thickness:, select Constant or Variable.
4. 5.

Altair Engineering
Note :
The option to switch between constant or variable thickness is only available for certain laminate sub-types.
If Constant is selected, the Ply lay-up order table includes a single thickness column: Thickness T1 If Variable is selected, the Ply lay-up order table includes multiple thickness columns: Thickness T1 Thickness T2 Thickness T3 Thickness T4 c) For Constant ply thickness, you can check the Common Thickness box and specify a thickness to be used by all the entry rows. Having checked the Common Thickness box and entered a common thickness value, if you now uncheck the box, the thickness fields retain the common thickness value, but are now editable. 6. Complete the Ply lay-up order table. Add/insert rows by completing the Add/Update plies: fields and clicking Add New Ply or Insert New Ply (for Insert New Ply, it is possible to choose to insert the ply above or below the selected rows). Note : The number of rows in the table is not the number of plies. This is governed by the stacking convention and the number of repetitions.
Data may be cut, copied from, pasted to, or deleted from selected fields using the toolbar, pull-down Edit menu or CTRL+X, CTRL+C, CTRL+V and CTRL+D, respectively. Table rows may also be cut, copied from, pasted to, or deleted from, using the toolbar, pull-down Edit menu or CTRL+X, CTRL+C, CTRL+V, and CTRL+D, respectively. Note : Note: Rows are always pasted above selected rows. When multiple non-sequential rows are copied and then pasted, they will be pasted as sequential rows. For example, if rows 1 and 3 are copied and pasted at row 7, row 1 will be pasted as row 7, row 3 will be pasted as row 8, and what was row 7 will now be row 9.
7. 8.
For the OptiStruct and Nastran user profiles it is possible to define thickness and orientation fields in the Ply lay-up order table as designable and to assign design variables to them. Click Update Laminate to save the changes for the current HyperLaminate session. (It is important to remember that the HyperMesh database is only updated on exit from HyperLaminate.)
Altair Engineering

Review and Modify an Existing Laminate

1. Select the laminate to be edited from the Laminate Browser. The Define/Edit and Review/Results panes are populated with the selected laminate definition. 2. 3. The laminate definition may be modified in the Define/Edit pane in a manner similar to defining a new laminate. (See Define a New Laminate.) Click Update Laminate to save the changes for the current HyperLaminate session. (It is important to remember that the HyperMesh database is only updated on exit from HyperLaminate.)

Altair Engineering
Define a New Design Variable

Design variables are only supported for the OptiStruct and Nastran user profiles. 1. Use one of the following three methods to create a new design variable in HyperLaminate: Method 1: 1. 2. Select a sub-type under the design variable branch of the Laminate browser (only sub-type available is DESVAR). Right-click the selected sub-type. A context-sensitive menu appears with one option: New. 3. Click New. A new design variable appears under the selected branch. Method 2: 1. 2. Select a sub-type under the design variable branch of the Laminate browser (only sub-type available is DESVAR). Select New from the File pull-down menu. A new design variable appears under the selected branch. Method 3: 1. Select a sub-type under the design variable branch of the Laminate browser (only sub-type available is DESVAR). Click the new icon, , on the toolbar.
2.
A new design variable appears under the selected branch. A default name and ID are assigned to newly created design variables. 2. 3. 4. 5. 6. 7. The newly created design variable is automatically selected in the Laminate browser and the Define/ Edit pane takes on the appropriate configuration. If desired, a new name for the laminate may be entered in the Desvar: field. Initial, lower bound, and upper bound values for the design variable can be entered in the appropriate data fields. Checking the Move limit box activates the Move limit field, where a move limit value other than the default of 0.5 may be entered. Checking the Ddval ID box activates the Ddval ID field, where the ID of a discrete value list may be entered. Click Apply to save the changes for the current HyperLaminate session. (It is important to remember that the HyperMesh database is only updated on exit from HyperLaminate.)
Altair Engineering

Review and Modify an Existing Design Variable

1. Select the design variable to be edited from the Laminate browser. The Define/Edit and Review panes are populated with the selected design variable definition. 2. Edit the data fields in the Define/Edit pane. Data may be cut, copied from, pasted to, or deleted from the data fields using the toolbar, pull-down Edit menu or CTRL+X, CTRL+C, CTRL+V, and CTRL+D, respectively. Clicking Clear will reset all fields to their default values. Each change is reflected in the Review pane. 3. Click Apply to save the changes for the current HyperLaminate session. (It is important to remember that the HyperMesh database is only updated on exit from HyperLaminate.)
The final design variable definition is displayed in the Review tab.

Altair Engineering
HyperBeam
HyperBeam is a tool within HyperMesh that allows you to visualize and control 2-D beam cross sections. These beamsections can be defined using geometry and element data from HyperMesh or can be chosen from our selection of solver libraries. Once defined these beamsections calculate and maintain cross section results that can be used in HyperMesh to create one-dimensional element property data for an FEA model.
The grey elements in the image to the left represent a structure w e w ould like to stiffen by adding I-beams dow n the length of it. The image to the right is the 3D visualization of 1D bar elements running along 5 separate node paths.
References
The following sources were used in the creation of HyperBeam documentation: 1. 2. 3. 4. W.D. Pilkey, Analysis and Design of Elastic Beams, Wiley & Sons, New York, 2002. H. Gldner, ed., Lehrbuch Hhere Festigkeitslehre, Fachbuchverlag, Leipzig, 1979. A. Gjelsvik, The Theory of Thin Walled Bars, Wiley & Sons, New York, 1981. U. Schramm, V. Rubenchik, and W.D. Pilkey, Beam Stiffness Matrix based on the Elasticity Equations, International Journal for Numerical Methods in Engineering 40 (1997) 211-232.
See also HM4450: Introduction to HyperBeam HM4020: Obtaining and Assigning Beam Cross-Section Properties using HyperBeam HyperBeam panel
Altair Engineering

HyperBeam View
The HyperBeam View allows you to create and control HyperBeam beamsection data within HyperMesh. It is the view located furthest to the right in the Model Browser ( ). HyperBeam View can be divided into the following sections: Section Browser & Parameter Definition, Graphics Window , Results Pane and the Toolbar. To exit HyperBeam View and return to HyperMesh either click another view in the model browser or select Exit from the File menu.

Altair Engineering
Section Browser and Parameter Definition

The Section Browser presents a hierarchical view of all of the beamsections and beamsection collectors in your database. HyperBeam displays this hierarchy in a standard tree structure of beamsections residing inside of beamsection collectors. You can use the Section Browser to find a particular section of your model for displaying or editing. By clicking on a beamsection in the Section Browser it becomes highlighted and the results are displayed in the Results Pane. Additionally, the parameters are listed and available for editing in the Parameter Definition Window . Note: Only standard and shell sections have editable parameters in the Parameter Definition Window. Generic sections must be edited in the Results Pane itself, and solid sections dont have editable parameters.
The beamsections and beamsection collectors can be sorted alphabetically, by ID or by the config column. The config column lists the type of section: Shell, Solid, Generic and various types of standard sections including Channel, I-Sect, L-Sect, and so on. Known limitations: Dragging, dropping, copying and pasting have not been implemented yet in our new browser. Please use HyperMesh to organize your beamsections.
Altair Engineering

Context Menu
The context-sensitive menu available in the HyperBeam View contains options for creating and editing beamsections.
The Create option allows you to create beam collectors, standard beamsections and generic beam sections. Note that the only standard section libraries listed are those of the current HyperMesh user profile and the HyperMesh general standard section library. Delete, Rename, Collapse All, and Expand All follow general HyperMesh procedures. Make Current is only available for beamsection collectors and allows user to control in which collector new beamsections will be created. There are two options in the context sensitive menu that are only available for shell sections: Edit and Export CSV. Edit allows you to control the thickness and naming of each part in the beamsection. The

Altair Engineering
connectivity order simply lists the vertices that define the highlighted part.
Export CSV allows you to capture the beamsection name, each part within the section, its thickness, and each vertex number and position in a CSV file. Multiple shell sections can be selected and exported using <ctrl>+<left-click>. Known limitations: Breaking, merging and advanced shell section editing isnt available yet in HyperBeam View. Please use the shell section subpanel of the hyperbeam panel in HyperMesh to appropriately define shell and solid sections.
Parameter Definition
The Parameter Definition window is located below the section browser.
Altair Engineering

The Parameter Definition window serves two functions in the HyperBeam View: it allows you to edit the dimensions of supported standard beamsections, and it allows you to edit the Y and Z values for vertices of shell sections. The Graphics Window is updated and the dimension values are automatically saved upon each entry. Use <tab> and <shift+tab> to quickly navigate through the parameters.

Altair Engineering
HyperBeam View Toolbar

The toolbar in HyperBeam View allows you to control two options.
The first option is a simple background grid on/off control. The grid allows you to quickly resolve the relative size of each section. The second option, represented by four buttons, allows you to control the orientation with respect to the local origin of a standard section in the HyperBeam standard section library. Standard sections within the solver libraries already have a set orientation that maps to the solver, so this option is not available for any sections other than those defined in the HyperBeam library.
Altair Engineering

Graphics Window
The graphics window displays a representation of the geometric layout of the section. All sections have the following display items:
Local origin of the beamsection
Section Centroid Shear Center Standard sections display the geometric representation of the section based on the parameter values, which are also listed on the screen.

Altair Engineering
For shell sections each part is drawn with lines connecting the dots that show the section's vertices.
Altair Engineering

Solid sections arent editable in the HyperBeam View, but the mesh that is used for the section calculations is shown.

Altair Engineering
Since generic sections dont inherently have any shape, only a grey box is shown. To modify a generic section, you can type in the results pane. The centroid and shear center graphics location will update.
Altair Engineering


Altair Engineering
HyperBeam Results Pane

Whenever HyperBeam computes the section properties of the current section, it displays them in the results pane. You cannot edit the text in this portion of the window for standard, shell and solid sections, but you can select it and copy/paste it into another application. Note that the only way to change the parameters of a generic section is to edit the values in the results pane.
Altair Engineering


Altair Engineering
HyperBeam Sections
The following sections can be defined in HyperBeam: 1. Standard Section: Standard sections allow you to automatically define solver supported sections. Each supported solver has a library of supported sections, and section type and dimensions can be edited in HyperBeam. 3-D visualization is available in HyperMesh.
2.
Shell Section: Shell sections allow you to define thin cross-sections with geometric lines or 1-D elements. Once the cross-section is initially selected in HyperMesh, you can create the section and edit it in HyperBeam. 3-D visualization is available in HyperMesh.
3.
Solid Section: Solid sections allow you to define solid beam cross-sections with continuous 2-D elements, connecting lines that have a closed loop, and continuous surfaces. Once the solid section is initially selected in HyperMesh it cannot be edited in HyperBeam. 3-D visualization is available in HyperMesh.
4.
Generic Section: Generic sections allow you to define sections without defining actual cross-section geometry. Areas, inertias, centroids, and other coefficients are supported. No 3-D visualization is available in HyperMesh.
Altair Engineering

Example: Creating and Assigning a Standard Section

This example illustrates how HyperBeam can be used to create and assign a standard section to a Radioss Bulk, OptiStruct PBARL property. It assumes that the Radioss Bulk or OptiStruct user profile is loaded and uses the file standard_section.hm from <installation_directory>\tutorials\hm.
The grey elements in the image to the left represent a structure we would like to stiffen by adding I-beams down the length of it. The image to the right is the 3D visualization of 1D bar elements running along 5 separate node paths.
HyperBeam View is the furthest view to the right in the model browser ( ). Standard sections can be created by right-clicking on the browser and selecting the appropriate section. In this case we will be using an Radioss Bulk, OptiStruct I section with the parameters specified below.

Altair Engineering
Once HyperBeam solves the cross sectional properties, it is necessary to attach the beam section to a PBAR card image. This can be done in the Property tab of the Create Component dialog in the Model Browser.
Altair Engineering

After the new component and property are created with the beamsection attached, the bar element can be defined in the bars panel in the 1D menu-page.

Altair Engineering
Bar element alignment using HyperBeam sections is very straightforward since standard sections are defined using an absolute y-direction. The direction specified in the Bars panel defines the alignment of the beamsections y-direction. In this case, the positive z-direction in the Bars panel will align with the y-direction of the HyperBeam section. Since the centerline of a 1D beam element is defined about the sections shear center, elemental offsets are frequently required. In this case, we have added z-offsets at both ends of each element to align the I-beams flush with the plate. To fully visualize the 1D element in HyperMesh, find the display option in the visualization toolbar ( ).
Altair Engineering

Example: Creating and Assigning a Shell Section

This example illustrates how HyperBeam can be used to create and assign a shell section to a Radioss Bulk, OptiStruct PBAR property. It assumes that the Radioss Bulk or OptiStruct user profile is loaded and uses the file shell_section.hm from <installation_directory>\tutorials\hm.
The blue lines are plot elements denoting the beam section. Elements or lines can be used to describe a beam cross section. The purple lines are plot elements used to align the section within HyperBeam. The shell section subpanel is selected from the hyperbeam panel in the 1D menu-page. The selector type is set to elems and the blue plot elements are selected. Under cross section plane: project to plane is then selected.
N1, N2, and N3 locations are selected as shown in the following figure. The plane base node, or origin, is set to the shear center.

Altair Engineering
The vector created by N1 to N2 describes the local y-axis used in HyperBeam. N3 describes the positive sense of the z-axis. It is important to note the alignment of the local axes at this point. Later, it will be necessary to know this when the beam section is aligned for bar elements. HyperBeam View is invoked when you click create.
Altair Engineering

Once HyperBeam solves the cross sectional properties, it is necessary to attach the beam section to a PBAR card image. This can be done in the Property tab of the Create Component dialog in the Model Browser.

Altair Engineering
After the new component and property are created with the beamsection attached, the bar element can be defined in the bars panel in the 1D menu-page.
Altair Engineering

Bar element alignment using HyperBeam sections is very straightforward if the section has been defined using an absolute y-direction. The direction specified in the Bars panel defines the alignment of the beamsections y-direction. In this case, the positive y-direction in the Bars panel will align with the y-direction of the HyperBeam section. To fully visualize the 1D element in HyperMesh, find the display option in the visualization toolbar ( ).

Altair Engineering
Cross Sectional Properties Calculated by HyperBeam

The beam cross section is always defined in a y,z plane. The x-axis is defined along the beam axis. The coordinate system defined by the user is called the local coordinate system ; the system parallel to the local coordinate system with the origin in the centroid is called the centroidal coordinate system ; the system referring to the principal bending axes is called the principal coordinate system . For shell sections, only the theory of thin walled bars is used. This means that for the calculation of the moments and product of inertia, terms of higher order of the shell thickness t are neglected. Thickness warping is also neglected.
Area
Area Moments of Inertia
Area Product of Inertia
Radius of Gyration
Elastic Section Modulus
Max Coordinate Extension
Altair Engineering

Plastic Section Modulus
Torsional Constant
Solid
(see below for warping function) Shell open
Shell closed
Elastic Torsion Modulus
Solid
Shell open
Shell closed
Shear Center

Altair Engineering
Warping Constant (normalized to the shear center)
Shear deformation coefficients
Shear stiffness factors
Shear stiffness
Warping Function
For solid sections, the warping function is computed using a finite element formulation. This may lead to un-physically high stresses in geometric singularities (sharp corners) that get worse with mesh refinement. This may cause problems computing the
Altair Engineering

elastic torsion modulus.
Nastran Type Notation

Altair Engineering
Working with Beamsections in HyperMesh

Beamsections are handled slightly differently in each HyperMesh user profile, although certain features remain constant.
Components, Properties, Elements and Beamsections

HyperMesh offers a great number of ways to organize a FEA model. Understanding the connection between components, properties, elements and beamsections is important for 1D beam modeling. The Model Browser allows you to create a component, property and material all at once and verifies that everything is appropriately assigned. It also allows you to assign an existing beamsection to the property. This is probably the simplest way to create and organize components for 1D modeling.
Clicking the Create property button in the Create component dialog accesses the property card for the component.
Altair Engineering

Every element, including beam, bar and rod elements, must exist within a component. A property can be assigned to a component, or to an individual element. If there is a conflict with properties assigned directly to elements and properties assigned to components, direct element property assignment takes precedence. 1D properties hold the section information such as areas, inertias or even specific dimensions in the case of standard sections. 1D elements hold the orientation and connectivity information. Beamsections hold section geometry information and section calculation data (just the same as a 1D property). In fact when a beamsection is assigned to a property, it will automatically take over the property and fill in the necessary fields. The 3D visualization operates based on the beamsections stored geometric data. To disassociate a beamsection from a property, right click the beamsection selector in the property card image.

Altair Engineering
Importing and Exporting HyperBeam Comments

Importing
On import of an FEA model, the default behavior for HyperMesh is to automatically create beamsections for all bar, beam, and rod properties that dont already have beamsections defined. These beam sections automatically populate bar, beam, and rod property cards and the cross-section should be edited with HyperBeam. 3-D visualization of beams in HyperMesh is only made possible through HyperBeam beamsections and their association to properties.
In order to import an FEA model without HyperMesh automatically creating beamsections for each 1D property, use the custom import feature with beamsections and beamsection collectors unchecked. The section information on the actual property cards will remain intact, but the geometric and section calculation data will be missing.
Exporting
Exporting a FEA deck in HyperMesh operates in a similar fashion. HyperBeam comments are written out by default (as are all HyperMesh comments).
Altair Engineering

In order to suppress HyperBeam comments from being exported, you must use the custom export feature or the option to turn off all comments is available. Beamsections are stored as HyperBeam comments in an exported deck.

Altair Engineering
Example: Importing and Automatic Beamsection Creation

This example illustrates the automatic creation of beam sections on import and the visualization of these rods, bars, and beams in HyperMesh. The Radioss Bulk or OptiStruct user profile will be used, along with the pbeaml.fem input file from <installation_directory>\tutorials\hm. Use a text editor to inspect the following file: pbeaml.fem.
There are no beam sections or HyperBeam comments defined in this input file. When imported, HyperMesh automatically creates beam sections which allow you to visualize the sections in 3-D. Import pbeaml.fem into HyperMesh and make sure the beam visualization ( ) is turned on.
Altair Engineering

Importing Geometry
The standard CAD translators interface in the Import tab. This is where advanced CAD translator import options can be set.
1.
From the File menu, click Import or click the Import icon This will open up the Import tab.
on the standard toolbar.
2. 3.
In the Import Type: drop down list, select Geometry. In the File type: drop down list, select the file type youd like to import. You can choose the Auto Detect option to select an input translator automatically. Click the Select File icon to choose the file to import. Selected files are displayed in the File and Remove All icons to quickly
4.
Selection window. You can use the Remove Selection remove files from the window. 5.
To set advanced import options, click Import Options to expand the panel. If accepting the default import settings, click Import to import your file.
Advanced Import Options 1. 2. Set the scale factor in the field. This is useful when converting a model created in English units to Metric, for example. Make a selection in the Cleanup tol: field. The cleanup tolerance is used to determine if two surface edges are the same and if two surface vertices are the same. The cleanup tol toggle controls the following items: if two surface edges are close enough to be automatically combined to shared edges (green edges) if a surface is degenerate and should be removed. If you use the automatic cleanup tol option, the complexity of the surface and edge geometries are taken into account and a tolerance to maximize shared edges (green edges) is selected. The automatic cleanup tolerance value defaults to 100 times what is used internally by the translator. If you want to specify a different value, use the manual cleanup tol option, which must be greater than the default value. The translator modifies data only if the data stays within the original data tolerance. Increasing the tolerance can cause serious problems. When this value is set, any features equal to or less than the tolerance are eliminated. The translator does not include any edge less than tolerance long; if there are edges present that are important to the surface, that surface will be distorted, or will fail to trim properly. Surfaces smaller than the tolerance may not be imported. If the file you have read has many very short edges, it may be worthwhile to reread the file using a larger tolerance. The same holds true if surfaces appear to be "inside out" when surface lines are displayed. The tolerance value should not be set to a value greater than the node tolerance set in the options panel to be used for your element mesh. If you are reading a Catia file, you may need to override the tolerance in the file; in our experience, the

Altair Engineering
tolerance in the file is almost always too small (by at least an order of magnitude). The Automatic option takes the complexity of the surfaces and edge geometries into account and a tolerance to maximize shared edges (green edges) is selected. The Manual option allows you to set a specific tolerance in the field. 3. The Import blanked (no show) components checkbox allows you to control if blanked components in the IGES translator will be imported, as well as components containing NO SHOW entities from the Catia translator. Place a check in the Name components by layer option to activate this option. This option is valid for Catia V4 and Catia V5. For Catia V4, the option is enabled by default, and cant be disabled. For Catia V5, the option is disabled by default and can be enabled. If this option is enabled, Catia objects from the same layer are grouped into the same component. 5. Click Apply to import the geometry.
4.
Altair Engineering

Import Error Messages

When an external input translator is used to import data, a file for messages is created in the directory in which the program was started. This file is named translator.msg, where translator is the name of the translation program being used. This file contains errors, warnings and useful information about the import process. The translators also create a second file that contains extra data from the file being imported. This file is named importfile.hmx, where importfile is the name of the file being imported. This extra data could contain FEA data and keywords not supported and/or generic comments about the data. If the Display Import Errors checkbox is selected on the Import tab, any error messages will display in the Import Process Messages pop-up window. From this window you can choose to display the .hmx file, save the message file or delete the message file. Clicking Close will close the pop up window, but will not remove the message file from your directory.
See also Importing and Exporting Data

Altair Engineering
Creating Collectors
All entities in an HM database are stored in collectors. Based on the assigned template, each collector may use a dictionary or card image to define the attributes assigned to the collector. The definitions contained in the dictionaries or card image are used to translate models to external analysis codes. The various collector panels allows you to create and update collectors and assign and edit card images or dictionaries.
To create a collector:
1. 2. 3. From the Collectors menu, select Create and select the type of collector you'd like to create. Click name = and enter a name for the collector. Click the switch under creation method:. 4. Select no card image if you do not want to assign a card image. Select card image and then click card image = to select the card image from a list. Select same as and then click same as = to select the collector whose type and card image information you want to copy from an existing collector.
Fill in the rest of the fields and click create to create the collector, or click create/edit to create the collector and immediately edit the card image.
Altair Engineering

Changing the Current Component Collector

There are multiple ways to change the current component collector:
If you know the name of the component collector:

Method 1: 1. 2. 3. On the Model Browser, expand the list of component collectors. Right-click on the component collector you wish to set as current. Choose Make Current from the menu that appears.
Method 2: 1. 2. The name of the current component collector displays on the status bar; click on that name. A list of all component collectors appears. Select the component collector to make current by clicking on its name.
If you dont know the name of the component collector:

Method 1: 1. 2. 3. 4. On the Model Browser, expand the list of component collectors. Click on the Selector icon and select the component collector in the graphics area. The selected component collector becomes highlighted in the Model Browser. Right-click on the highlighted component collector. Choose Make Current from the menu that appears.
Method 2: 1. 2. The name of the current component collector displays on the status bar; click on that name. A list of all component collectors appears. Click in the graphics area to specify the component collector to make current.

Altair Engineering
Changing the Current Load Collector

There are multiple ways to change the current load collector:
If you know the name of the load collector:

Method 1: 1. 2. 3. On the Model Browser, expand the list of load collectors. Right-click on the load collector you wish to set as current. Choose Make Current from the menu that appears.
Method 2: 1. 2. The name of the current load collector displays on the status bar; click on that name. A list of all load collectors appears. Select the load collector to make current by clicking on its name.
If you dont know the name of the load collector:

Method 1: 1. 2. 3. 4. On the Model Browser, expand the list of load collectors. Click on the Selector icon and select the load collector in the graphics area. The selected load collector becomes highlighted in the Model Browser. Right-click on the highlighted load collector. Choose Make Current from the menu that appears.
Method 2: 1. 2. The name of the current load collector displays on the status bar; click on that name. A list of all load collectors appears. Click in the graphics area to specify the load collector to make current.
Altair Engineering

Creating Geometry Data

If geometry is not available from a CAD system, you can create or edit geometry using the line and surface builders. The panels used in this process are listed below: lines creation and editing panels Lines Create lines in a variety of methods, including: from points, at tangents, and at the intersection of other geometry. Edit existing lines in a variety of methods such as combine, split, smooth, or extend. Create circles or arcs.
Line Edit Circles
surfaces creation and editing panels Surfaces Create surfaces from existing lines or nodes by different methods, such as spline, drag, or spin. Create standard shaped surfaces or solid entities, including squares, spheres, cones, and cylinders. Edit existing surfaces by trimming, extending, or shrinking. Edit existing surfaces by removing individual features such as holes or fillets.
Primitives
Surface Edit Defeature
point/node creation and editing panels Nodes Temp Nodes Create new nodes. Several methods are available. Add or remove nodes used only for geometry creation or editing.
Creating NURBS surfaces

A NURBS (non-uniform rational B-spline) surface is a parametric surface defined by control points, knots and weights. The ruled, spline/filler, and drag/spin subpanels of the Surfaces panel can be used to create NURBS surfaces. The spline option creates a surface through 3-D lines. If you select a set of lines that do not form a closed loop, HyperMesh will connect the disconnected lines with straight lines, and create a spline surface and/or mesh in the enclosed area. There is no limit on the number of lines used to create a mesh/surface.

Altair Engineering
These lines form one path because they intersect at four points.
These lines form more than one path and cause an error.
The tolerance setting on the Options panel is used to determine the intersections between lines. If the tolerance is too small and an intersection cannot be found, HyperMesh reports an error when you attempt to create the surface. Lines that contain sharp edges can cause problems when you create a surface. These lines result in a more complex surface, which takes longer to create, and slows the automeshing process. These sharp edges are sometimes the result of data created on other CAD/CAM systems and brought into HyperMesh via a translator. These lines may need to be "smoothed" by using the line edit panel or replaced with a new, smooth, line by using the lines panel.
Creating a surface w ith these lines results in a relatively complex surface.
Altair Engineering

The "circular" shaped line has been replaced w ith a smooth line, w hich results in a much simpler surface. In some cases the sharp edges are required to represent the model and should not be smoothed.
The skin option can create a skinned surface through a set of lines.
Lines used to define a skinned surface.
A skinned surface created from the lines.
The ruled option can create a ruled surface between two lines.
Lines used to create a ruled surface.

Altair Engineering
A ruled surface created from the lines.
Altair Engineering

Temporary Nodes
A temporary node list retains nodes that are not attached to an element, protecting them from automatic removal by the database management (except for some panels that automatically clear all temporary nodes, i.e., edges, faces, edit elements). There may be times when you wish to use an unattached node later in the modeling process. The Temp Nodes panel allows you to modify the temporary node list. In the Temp Nodes panel, there are three functions: add clear clear all Adds selected individual nodes to the temporary node list. Removes selected individual nodes from the temporary node list. Removes all the temporary nodes from the database.

Altair Engineering
Picking Surfaces
You can display surfaces in wireframe mode or in shaded mode. In wireframe mode, the easiest method of selecting a surface is to pick the surface near its edges or surface visualization lines. If several surfaces share an edge, you can select any one of them by clicking on the edge, and while holding the mouse button down, moving the mouse slightly from side to side. Each surface highlights as selected. Release the mouse button when the desired surface is highlighted. In shaded mode, click anywhere on the surface to select it. Similar to wireframe mode, you can hold the left mouse button down until the surface of interest is highlighted, and release it to confirm the selection. Surface edges may be used in the same way as lines in any surface creation panel, where appropriate. If you use any surface edge lines in the Line Edit panel, duplicates of the lines are created and the operation is applied to the duplicates.
See also Line Edit panel General Process for Building Models
Altair Engineering

Editing Surfaces
Each surface contains one or more faces. It is usually preferable to combine multiple faces into one surface entity before you use the meshing tools. This allows them to be meshed at the same time. You can use the Surface Edit panel to modify surface geometry when it is necessary to make changes before you generate a mesh. For example, to trim a surface with a line, use the trim with line subpanel of the surface edit panel. You must select the surface and the line and specify a direction vector. The surface is trimmed by sweeping the line along the vector and intersecting the surface with the sweep. If the sweep does not intersect the surface, the surface is not trimmed. The Edit Element panel has a cleanup subpanel, which contains surface editing tools.
A circle and a surface (represented w ith surface lines) before trimming.
After the circle is used to trim the surface, tw o new surfaces are created (show n highlighted) and the original surface is trimmed.
To trim one surface with another, use the trim with surf subpanel.

Altair Engineering
Tw o surfaces before trimming.
The smaller surface is split into tw o surfaces after it is trimmed w ith the larger surface.
Altair Engineering

Associativity
Nodes and elements can be associated to surfaces. When you create a mesh with the automesher, the nodes are automatically associated to the surface. When nodes are associated to a surface, you can use the Smooth panel to smooth elements on the surface and the Node Edit panel to move the nodes along the surface. Associated nodes and elements can be selected by surface, which allows you to select all the nodes and/or elements associated to a surface. Some operations break associativity. If you transform, such as translate, a surface, node, or element, associativity is broken. However, if you transform a component that contains both a surface and its associated nodes/elements, the associativity is not broken. Associativity is also broken if you trim a surface. To re-associate a node to a surface, use the Node Edit or Project panel. Note: Re-associating nodes to a surface is usually a time consuming task.
See also Smooth panel Node Edit panel Project panel General Process for Building Models

Altair Engineering
Geometry Cleanup
When designers create CAD geometry, their priorities are different from those of analysts trying to use the data. A single smooth surface is typically split into smaller patches, each a separate mathematical face. The juncture between two surfaces often contains gaps, overlaps, or other misalignments. To make the geometry more appropriate for meshing, analysts need to combine a number of faces into a single smooth surface. This allows the elements to be created on the entire region at once, and prevents unnecessary artificial or accidental edges from being present in the final mesh. The Quick Edit, Edge Edit, Point Edit, and Autocleanup panels contain tools to help you prepare surface geometry for meshing.
The initial CAD geometry often contains gaps, misalignments, or pinholes.
These features can distort the elements or demand a finer mesh.
With the tools of the geometry cleanup panels, you can close the gaps betw een surfaces, combine surfaces into large meshing regions, and eliminate pinholes.
Altair Engineering

Using the simpler, cleaner geometry, you can easily build a much better mesh.

Altair Engineering
Applying Loads
The final step in the model building process is to apply constraints and forces and to create or assign coordinate systems. Before you apply loads, create a load collector. Loads are displayed in the color assigned to the load collector. The size of loads and constraints is based on model units and can be modified from within the boundary condition panels. HyperMesh stores and displays all loads in the global coordinate system. Depending on the analysis code being used to calculate results, HyperMesh transforms the loads appropriately to any local nodal output coordinate system. HyperMesh currently supports the following load types: accelerations Applies an acceleration at a node. Accelerations are displayed as a singleheaded arrow with an optional label, A. The label may also display the magnitude of the acceleration. Applies a constraint or enforced displacement at a node. Constraints are displayed as a triangle with an optional label that displays the degrees of freedom effected by the constraint. Applies a general equation constraint between nodes. Equations are displayed with the label, EQ. Applies a flux load at a node. Fluxes are displayed as a thick arrow with an optional label, flux . The label may include the magnitude of the flux. Applies a concentrated force along any user-defined vector at a node. Forces are displayed as a single-headed arrow with an optional label F. The label may include the magnitude of the force. Linear interpolation input files for forces require 6 values with a space in between, as follows:
<X location> <Y location> <Z location> <X component> <Y component > <Z component >
constraints
equations
fluxes
forces
moments
Applies a concentrated moment about a user-defined vector at a node. Moments are displayed as a double-headed arrow with an optional label, M. The label may include the magnitude of the moment. Linear interpolation input files for moments require 6 values with a space in between, as follows:
<X location> <Y location> <Z location> <X component> <Y component > <Z component >
pressures
Applies a pressure on an element or geometry. Pressures are displayed as a single-headed arrow with an optional label, P. The label may include the magnitude of the pressure. Linear Interpolation input files for Pressures require 4 values with a space in
Altair Engineering

between, as follows:
<X location> <Y location> <Z location> <magnitude>
temperatures
Applies a temperature constraint at a node. Temperatures are displayed as a straight line starting at the node at which the temperature is applied extending upward, with an optional label, T. Linear Interpolation input files for Temperatures require 4 values with a space in between, as follows:
<X location> <Y location> <Z location> <magnitude>
velocities
Applies a velocity at a node. Velocities are displayed as a single-headed arrow with an optional label, V. The label may include the magnitude of the velocity.
Note :
Refer to the specific panel for detailed information about creating, reviewing, and updating loads and constraints.

Altair Engineering
Creating Systems
Systems are referred to as coordinate systems and may be rectangular, cylindrical, or spherical. Reference and analysis systems are supported. Reference systems transform geometric location or input vectors from the global system to a local system. Nodes, mass elements, forces, and other systems are eligible entities for a reference system. Analysis systems transform the output system of a node entity. Systems are built and referenced in the Systems panel. Note : System collectors collect system entities. A system collector must exist and be current in order to build a system.
Altair Engineering

Control Cards
Control cards allow you to add input and output parameters to a model, including location and names of the input, output and scratch files; the type of run (analysis, check or restart); overall running of the analysis or optimization; and type, format and frequency of the output. Control cards are assigned to your model from within the Control Cards panel. This panel lists all of the control cards defined for the solver/user profile that you currently have loaded; you can disable, enable, or delete cards as desired.
See also Using the Card Previewer

Altair Engineering
Using the Card Previewer

A control card may be in one of three states: State Undefined Defined (See note.) Inactive Color Gray Green Explanation The control card was either never created or has been deleted. Any control card viewed in the card previewer is activated.
Red
A card that has been defined may be disabled. The attributes for that card remain; however, the control card is not output.
Note:
Those control cards that are defined (green in the control card editor) are output.
Default values for attributes are common throughout the card previewer. A default value field has two states: State Default = ON Description In this state, the field label color is yellow and no data entry is allowed. To override a default value field, pick the yellow field label. When you override a default value field, the label text color changes to cyan and allows you to enter data in the field.
Default = OVERRIDDEN
Altair Engineering

Boundary Conditions
Boundary Conditions define limits as well as loads on geometry and mesh.

Altair Engineering
Loads on Geometry
You can apply loads to geometrical entities and map them to the FE mesh using the Load on Geom panel. One advantage is that you can remesh a model without deleting complicated loads or boundary conditions. After remeshing, loads or boundary conditions that have been applied to geometrical entities can be remapped to the new mesh. You can apply loads to geometry by using the following panels: Forces, Moments, Constraints, Pressures, Temperatures, Flux , Velocities, and Accels. These are the same panels used to apply loads to a mesh. There are two ways to map loads on geometry to the mesh associated with this geometry (loads on mesh): Manually, using the Load on Geom panel. Automatically, by exporting the FE deck, using the Export tab. The Model Browser allows separate or simultaneous visualization of loads on mesh and loads on geometry. To visualize loads on mesh and/or loads on geometry, in the Model Browser, right-click on the load. From the toolbar, select the Elements/Geometry icon. This icon determines what the other buttons act on; right-click the button (or left-click the small triangular downward arrow) to reveal a drop-down menu of options. You can select Elements, Geometry, or both. When Elements is selected, you control the display of loads applied to elements. When Geometry is selected, you control the display of loads applied to geometric entities. Both means that you can control the display of both types of loads independently, and load collectors may contain one type or both types simultaneously. Use the none, all and reverse buttons to assist in selecting which loadcols should be displayed. Comments Loads on mesh and loads on geometry can be displayed together (similar to the simultaneous display of both elements and geometry belonging to a specific component). A geometrical entity can be associated with one mesh or multiple meshes (component or components) and/or with one load collector or multiple load collectors. One load collector stores both loads on geometry and loads on mesh. The mesh (or multiple meshes) is associated with the geometrical entities to which the loads on geometry have been applied. Each load type is stored in a dedicated section of the same load collector.
Altair Engineering

Terminology and Definitions

geometrical entities loads on geometry or geometry loads loads on mesh or mesh loads A point, a line, or a surface. Loads applied to geometrical entities.
Loads applied to mesh (nodes or element). Loads can be applied directly to mesh or applied by mapping them from loads on geometry. The process of mapping geometrical loads to mesh loads. The loads are mapped from the geometrical entities (to which the geometrical loads are applied) to the mesh that is associated with the geometrical entities.
load mapping
See also Introduction to Loads on Geometry Application of Loads to Geometry Exporting Loads Visualization of Loads on Geometry and on Mesh Working with Loads on Geometry - HM-4040

Altair Engineering
Application of Loads to Geometry

You can apply loads to geometrical entities in a way similar to the manner in which loads are applied to mesh. The process includes two basic steps. 1. 2. Creating a load collector by using the Collector panel Applying loads to the geometry using one of the following panels on the Analysis page: Forces, Moments, Constraints, Pressures, Temperatures, Flux , Velocities, and Accels
To apply a load to a geometrical entity, first create a load collector in which the loads applied to geometrical entities will be stored. Next, access a HyperMesh load panel (e.g. Forces, Constraints, etc.) located on the Analysis page, and choose the create subpanel. Third, select a geometrical entity on which the loads will be applied (points, lines, or surfaces) using the panel selection box, define the load or boundary condition parameters in the same way you would for the application of the load or boundary condition on a FE mesh entity (e.g. node), and click create. HyperMesh stores the loads/boundary conditions in the database and displays them in the graphical window. The following chart specifies the geometrical entities to which loads can be applied, in each of the load application panels listed above. Panel Accels Constraints Flux Forces Moments Pressures Geometrical Entities points, lines and surfaces. points, lines and surfaces. points points points surfaces nodes on edge: lines (for 2-D solid elements) nodes on face: surfaces (for 3-D solid elements) points, lines and surfaces. points, lines and surfaces.
Temperatures Velocities Note:
Refer to the specific panel for detailed information about creating, reviewing, and updating loads and constraints.
Altair Engineering

Exporting Loads
Sessions can contain loads on geometry, loads on mesh that have been applied directly to mesh, and loads on mesh that have been mapped from loads on geometry. When saving the model as an HM database, all load types are saved and are retrieved when you open the . hm file. When exporting the model using an export template, only the loads on mesh are exported. The loads on mesh that are exported may have been applied directly to mesh, mapped from geometry to mesh, or both. The all/displayed option on the Export tab allows you to determine which loads are exported. If all is selected, all the loads on geometry that have not been mapped (if any), are mapped to loads on mesh and all the loads on mesh are exported. If displayed is selected, all the displayed loads on mesh are exported. All the loads on mesh (both displayed and hidden) that are associated with the displayed loads on geometry are exported as well. If any loads on geometry are displayed and have not been mapped, they will automatically be mapped to loads on mesh and exported as well.

Altair Engineering
Visualization of Loads on Geometry and on Mesh

The Display panel allows you to visualize loads on mesh and loads on geometry either individually or together by setting the collector type to loadcols and using the toggle between elems and geoms. elems controls the display of loads on mesh and geom controls the display of loads on geometry. A simultaneous display is similar to the display of both elements and geometry belonging to a specific component. Note: A major graphical display difference between loads on geometry and loads on mesh is the density of the arrows. Multiple arrows represent loads on mesh (one arrow per node or element); a single arrow for each geometrical entity represents loads on geometry. The basic length of the arrow also differs. For the same arrow magnitude percentage setting or uniform size setting within the load application panels, an arrow that represents a load on geometry is longer than arrows representing loads on mesh.
Altair Engineering

Creating Load Collectors

1. 2. 3. 4. In the Model Browser, right-click on the white area and select Create > Load Collectors. Enter a load collector name after name = . Click color and select a color from the pop-up menu. If creating a generic load collector: - Click the switch and select no card image. - Click create. - Click return. 5. If creating a specific load collector: - Click the switch and select card image. - Click card image = and select the card image type. - Click create/edit. - Enter the relevant data in the card image. - Click return.
See also Loads on Geometry

Altair Engineering
Transformation Manager
The Transformation Manager manages the definition of transformation applied on the nodes and elements in order to easily position the entity using a combination of scale, rotate, and translate and symmetry functions. These operations are usually applied on standard parts such as dummies, barriers, etc. for positioning in different crash setups. Also they can be used for repositioning components with strain history between multiple steps of simulation. The Transformation Manager is available for RADIOSS (Block Format), LS-DYNA and PAM- CRASH 2G user profiles. The Transformation Manager has two basic folders/sections: Transformation Definition, and Transformation Repository. Transformation Definition lists the transformations defined in the model in a tree structure detailing the cross referencing between the entity and the transformation. Transformation Repository holds the candidates on which the transformations can be applied which is solver dependent. In the RADIOSS (Block Format) and PAM-CRASH 2G user profiles, the repository contains all the node sets defined in the model. In the LS DYNA user profile, the repository contains node sets and include files organized in two different folders.
Toolbars
The Transformation Manager include toolbars and a context-sensitive menu. Toolbars provide the ability to switch between the two views, show or hide entities on which transformation is applied within the model, and activate or deactivate the transformation applied on a entity. The context-sensitive menu provide basic functions such as the creation, addition of entities, activation/inactivation of transformation, deletion, card edit, manipulating the sequence of transformation, display control, and review. Icon Function Activate the selected transformation. If none are selected, activate all the transformations defined. Inactive the selected transformation. If none are selected, inactivate all the transformations defined. Active or inactive state depending in its current state for the selected transformation. If none is selected, it is applied on all the transformations defined. Isolate the selected entity Show/Hide the selected entity Review the selected entity Switches to transformation entity view Switches to entity transformation view
Altair Engineering

Icon
Function Close the transformation manager

A context-sensitive menu is available for any selected item in the Transformation Manager tree. To view the context menu, right-click on an entity folder, an individual entity, or in an empty space in the browser. Clicking in the empty space provides options applicable to all the entities in the transformation definition. The functions vary depending on whether it is performed on entity in the transformation repository or in transformation definition. Also there are subtle differences in functions performed depending on the view.
Transformation definition
Entity- Transformation view Item Create new: Definition Creates new entity on which transformation will be applied. Includes node sets for the RADIOSS, PAM-CRASH 2G user profiles. Includes node sets and include files for the LS-DYNA user profile. Allows you to edit the entity on which transformation is defined. Available only on entity. Opens the corresponding solver card image panel. Available on both entity and transformation. Deletes the selected entity. Available on both entity and transformation. Creates a new transformation and applies it on the selected entity. If transformation already exists for the entity, it appends to it. Available on the entity. Renames the selected entity/ transformation. Available on both entity and transformation.
Add entity:
Card edit:
Delete: Transform:
Rename:
Show, Hide, Similar to Model Browser functions. Available for both transformation and entity. Isolate, Show all, Review, Reset review:
Move UP:
Swaps the ID of the selected transformation with the next smaller ID that is attached to the same entity Swaps the ID of the selected transformation with the next higher ID that is attached to the same entity
Move up:

Altair Engineering
Item
Definition
Collapse All: Closes all of the folders in the tree structure, so that only the top-most level of items displays. Expand All : Opens all of the folders in the entire tree structure, exposing every item nested at every level.
Transformation - Entity view Item Create new: Add entity: Definition Creates new transformation Allows to add a new entity on to the selected transformation. If the entity is selected, you can edit the content. Available on both entity and transformation. Opens the corresponding solver card image panel. Available on both entity and transformation. Deletes the selected entity. Available on both entity and transformation. Appends the defined transformation on the selected transformation. Available only on the transformation. Renames the selected entity. Available on both entity and transformation.
Card edit:
Delete: Transform:
Rename:
Show, Hide, Similar to Model Browser functions. Available for both transformation and entity. Isolate, Show all, Review, Reset review:
Move Up:
Swaps the ID of the selected transformation with the next smaller ID that is attached to the same entity Swaps the ID of the selected transformation with the next higher ID that is attached to the same entity
Move Down:
Collapse All: Closes all of the folders in the tree structure, so that only the top-most level of items displays. Expand All : Opens all of the folders in the entire tree structure, exposing every item nested at every level.
Altair Engineering

Transformation repository
Item Transform Definition Creates new transformation on the selected entity . The transformation and the entity show up in the transformation definition folder. Opens the corresponding solver Card Image panel. Renames the selected entity.
Card Edit: Rename:
Show, Hide, Similar to Model Browser functions. Isolate, Review, Reset review:
Supported solver keywords

RADIOSS TRANSFORM/TRANSLATE TRANSFORM/ROTATE TRANSFORM/SCALE TRANSFORM/SYMMETRY LS DYNA NODE_TRANSFORM INCLUDE_TRANSFORM PAM CRASH TRSFM _/_ 2 G

Altair Engineering
Morphing
HyperMorph is a tool used to morph the shape of a finite element model in ways that are useful, logical and intuitive. It enables rapid shape changes on the FE mesh without severely sacrificing the mesh quality. During the morphing process, HyperMorph also allows for the creation of shapes which can be used for subsequent design optimization studies.
Overview: The Three Basic Approaches to Morphing The Domains and Handles Concept The Morph Volume Concept The Freehand Concept
The Domains and Handles Concept Global Domain and Global Handles Local Domains and Handles Partitioning Dependent Handles Working with Shapes Setting Up Optimization
The Morph Volume Concept
The Freehand Concept
Space Frame Model Strategies Creating Handles and Domains Matching a Mesh or Line or Surface Data Making Parametric Changes Controlling Global Morphing with Handle Placement Mirror Images: Using 1-Plane Symmetry Reducing 3D to 2D: Using Linear Symmetry Reducing 3D to 1D: Using Planar Symmetry
Altair Engineering

Shell Model Strategies Creating Handles and Domains Morphing on Local Domains Morphing Global Handles Using Constraints Using Biasing
Solid Model Strategies Creating Handles and Domains Viewing Solid Models Morphing on Local Domains Morphing Global Handles Using Constraints Using Biasing

Altair Engineering
Approaches to Morphing
HyperMorph contains a wide array of functionality for morphing the shape of FE models. HyperMorph utilizes six exclusive HyperMesh morphing entities; domains, handles, morph constraints, morph volumes, shapes, and symmetries. While all the entities and functions are fully compatible, and may be used in a complementary fashion, they can be divided into three basic approaches to morphing; the domains and handles concept, the morph volume concept, and the freehand concept. Each approach has its own strengths and weaknesses when dealing with the numerous applications of morphing and you are advised to gain a basic understanding of each approach so that you can decide which approach is best for your needs. The morphing chapter is intended to illustrate the capabilities of HyperMorph and introduce you to both the basic and advanced functionality to help you get the most out of the tool. The basics of the three concepts are summarized below:
The Domains and Handles Concept

This approach involves dividing the mesh into domains containing elements or nodes and placing handles at the corners of those domains. HyperMorph can automatically divide the mesh into logical domains or you can manually define your own domains and handles. When the handles are moved, the shape of the mesh changes according to the domain boundaries. The domains and handles approach also allows for parametric morphing of lengths, angles, radii, and arc angles as well as morphing the mesh to match geometric data and other meshes. The domains and handles approach is the most difficult approach to learn but it is also the most powerful. This approach is most useful for making detailed changes to any mesh (local domains) as well as general changes to space frame type meshes (global domains).

This approach involves surrounding the mesh with one or more morph volumes, which are highly deformable six-sided prisms. A number of methods exist to create the morph volumes, including single and matrix creation as well as the interactive on-screen method. Morph volumes support tangency between adjoining edges and allow for multiple control points along their edges. Handles placed at the corners and along the edges of the morph volumes allow for the morphing of the morph volumes which in turn morphs the mesh inside the morph volumes. The morph volume approach is quick and intuitive and is most useful for making large scale changes to complex meshes.

This approach involves morphing by moving the nodes directly without the need to create any HyperMesh morphing entities. You define the nodes which will move, the nodes which will stay fixed, and the affected elements, which manually allows for rapid changes to any mesh. You have great flexibility in how the moving nodes are moved, such as translation, rotation, and projection to geometry as well as using a tool to "sculpt" the mesh into the desired shape. You are also able to turn node manipulations made in any panel, such as scaling or node projection, into morphs using the record sub-panel. The freehand approach is an ideal introduction to HyperMorph since it allows morphing without the creation of any HyperMesh morphing entities while employing the concepts of domains and handles. The freehand approach also allows for "customized" morphing, allowing the user to do virtually any kind of morphing.
Altair Engineering


Altair Engineering
The Domains and Handles Concept

When using the domains and handles approach, the model is divided into domains. Handles are then used to control the domains shape. When the handles associated with a domain move, the shape of the domain changes, which in turn changes the positions of the nodes inside those domains. During the morphing process the mesh morphs in a logical way with nodes near the moving handles moving more and nodes near the stationary handles moving less. In the areas between the handles, the mesh is stretched or compressed to match the desired shape. The amount each node moves with respect to each handle is relative to an internally calculated influence coefficient. The process for calculating the influence coefficients is somewhat time consuming, but once they are calculated they can be stored and applied rapidly. Thus, when handles and domains are initially set up or edited, HyperMorph spends an amount of time (proportional to the size of the new domains) calculating the handle influences. However, when handles are moved to morph the model, no calculations are necessary and the actual morphing occurs quickly. The advantage of this approach is that it makes morphing an interactive process, even for large models. For very large domains, calculating influence coefficients can be time consuming. For domains that have more than 50,000 elements (although you can change this default limit) the large domain solver is used. The large domain solver is that it is faster for morphing large domains, but the drawback is that it must be invoked every time you wish to morph, thus making morphing slower. However, for very large domains, the process of calculating influences can be too slow or too memory intensive--so the large domain solver makes it possible to morph such domains. Domains and handles are divided into two basic groups, global domains and local domains. Each global domain is associated with any number of global handles. Global handles will only influence the nodes contained within their associated global domains. Global domains and handles are best for making large scale shape changes to the model. There are five types of local domains: 1D domains, 2D domains, 3D domains, edge domains, and general domains. Each local domain is associated with any number of local handles. Local handles will only influence nodes contained within their associated local domains. Local handles are intended to be used to make small scale, parametric changes to the model. A model can contain both global and local handles and domains, which allows for both large and small scale morphs. It is not necessary to have both types of domains and handles in a model.
Global Domains and Handles Local Domains and Handles Partitioning Dependent Handles Working with Shapes Setting Up Optimization
Altair Engineering

Global Domains and Handles

Global domains are represented by a cube made up of dashed lines. Global domains are located at the centroid of the nodes which make up the global domain. Global handles are the largest handles in the model. Global handles are red if they are not dependent on other handles. Global handles are yellow, cyan, or violet if they are dependent on other handles, the color indicating their level of dependency. Dependent global handles are also smaller than the handles on which they are dependent. The base size of all the handles in the model can be set on the morphing visualization dialog accessed by using the visualization options icon on the visualization toolbar. The size given is used as the radius for the independent global handles. You cannot edit the color of the handles nor the relative size between the dependent and independent handles. However, you can edit the color of the domains in the morphing visualization dialog.
The Domains panel is used to create, edit, and organize global domains. When a global domain is created with the create handles option turned on HyperMorph generates several global handles. Global handles are generated at each of the eight corners of a box surrounding the model laid out along the global axes. These global handles are named corner followed by a number from one to eight. HyperMorph also places at least one global handle within the global domain box in areas of peak nodal density within the model. HyperMorph generally creates no more than about 30 global handles within the global domain box. These handles are named global followed by a number. The automatic global handle generation works particularly well for space frame models such as full car models. If the handles are not generated in the positions where you

Altair Engineering
want them to be, you can always delete them, reposition them, or create new handles using the Handles panel.
Example of a model with a global domain and global handles Eight handles are placed at the corners of a box enclosing the model. By moving the handles you can stretch or deform the model along all three axes.
Altair Engineering

A space frame with six manually created global handles When the handles are moved, the space frame morphs in a way such that the bars run between the handles.
There are three options for determining how global handles associated with global domains influence the mesh: the hierarchical method, the direct method, and the mixed method. In the hierarchical method, global handles influence the local handles found at nodes inside the global domain, which in turn influence nodes within the local domains. In the direct method, global handles influence the nodes in the model directly even if the nodes are not in a local domain. In the mixed method, global handles will influence every node inside the global domain using the hierarchical method if the node is inside a local domain, or the direct method if the node is not in a local domain. The method used can be selected in the global subpanel of the Morph Options panel. The default method is the direct method method. There are subtle differences in how the global handles influence the nodes for each method with the main difference being that the parts of the model defined by local edge domains have their shape preserved when using the hierarchical method. Straight edges will remain straight and circular holes will remain circular for the hierarchical method, while the direct method may bend or warp these features into curved edges and elliptical holes. You should select which method is right for the type of morphing that you want to perform. If you wish to preserve the local geometry, choose the hierarchical or mixed method. If you are willing to accept distortions in the local geometry, choose the direct method.

Altair Engineering
An exam ple of global m orphing using the hierarchical m ethod When the highlighted (w hite) handle is moved to the right, it moves the local handles, w hich move the mesh. Note how the straight edge remains straight and the circle remains round.
An exam ple of global m orphing using the direct m ethod When the highlighted (w hite) handle is moved to the right, the mesh is affected directly. Note the resulting distortion of the edge and circle.
Altair Engineering

An exam ple of global m orphing using the direct m ethod and biasing factors By increasing the biasing factor for the highlighted (w hite) handle, the angular shape of the morph becomes rounded.
The influences between the global handles and local handles using the hierarchical method or nodes using the direct method can be calculated using either the spatial method or the geometric method. Both methods attempt to determine how a global handle affects nodes or local handles in the space surrounding it. The spatial method is the default, and is the fastest and most robust method for generating global influences based on a spatial formulation for the entire model. The geometric method can be slow for large models or large numbers of global handles, but may produce more desirable influences. The geometric method is the method that was originally used in HyperMesh and generates influences based on the geometric relationship between a given node or local handle and the surrounding global handles. The method used can be selected in the global subpanel of the Morph Options panel.

Altair Engineering
Local Domains and Handles

Local domains are represented by a single rectangle for 1D domains, two joined rectangles for 2D domains, a cube for 3D domains, four joined rectangles for general domains, and a line for edge domains. Local handles are orange if they are not dependent on other handles. Local handles are green, blue, or pink if they are dependent on other handles, the color indicating their level of dependency. The base size of all the handles in the model can be set on the morphing visualization dialog accessed by using the visualization options icon on the visualization toolbar. The size given is used as the diameter for the independent local handles. You cannot edit the color of the handles nor the relative size between the dependent and independent handles. However, you can edit the color of the domains in the morphing visualization dialog.
Local domains can be created individually by selecting nodes or elements in the create subpanel of the Domains panel. When local domains are created, HyperMorph automatically places local handles at the ends of all edge domains. These local handles are named local followed by a number. The placement of local handles depends on the type of domain created and the partitioning options, if partitioning is selected.
Altair Engineering

Example of a model w ith local domains and local handles w ith partitioning.
In the example above, the rigid elements have been placed in a 1D domain with the center node having an independent (orange) handle and the other nodes having dependent (green) handles. The shell elements have been placed in two 2D domains separated at the bend line due to partitioning. The solid elements have been placed in a 3D domain. Note that shell elements have been created on the faces of the 3D domain. These elements are placed in a component named ^morphface. Also note that 2D domains have been created on the faces of the 3D domain and that edge domains have been created on the edges of all the 2D domains. Finally, handles have been placed at the ends of all the edge domains.
1D Domains Domains made up of 1D elements, such as bars and rigid elements, are called 1D domains. When automatically creating local 1D domains, 1D elements that share common nodes are grouped together into 1D domains. An independent local handle is placed at the centermost node of the 1D domain and dependent local handles are placed at every other node of the elements in the 1D domain. The independent handle is larger and orange, while the dependent handles are smaller and green. All the dependent handles in a given 1D domain are directly dependent on the independent handle. This dependency relationship means that moving the independent handle also results in moving the dependent handles the same amount in the same direction. This is done to preserve the unique relationship established for groups of 1D elements. Additionally, the bias factors for the dependent handles for a 1D domain are given an initial value of 3. All other handles in the model are given a biasing factor of 1. A higher biasing factor means that a given handle will have greater influence over the surrounding mesh than the others. The higher biasing factor given to dependent handles on 1D domains is intended to prevent mesh distortion when the 1D elements connect to nodes in 2D and 3D domains.

Altair Engineering
A rigid spider becom es a 1D dom ain An independent local handle (orange) is placed at the centroid of the 1D domain and dependent handles (green) are placed at each node. By moving the orange handle, the entire spider is moved, maintaining the proper shape and connectivity for the rigid spider .
2D Domains Domains made up of shell elements are called 2D domains. When automatically creating local 2D domains, shell elements that share common nodes are grouped together into 2D domains. If partitioning has been selected, these domains are subdivided into smaller domains along break angles and curvature changes according to the partitioning parameters. Edge domains are placed along the edges of the 2D domains and are also partitioned. Local handles are placed at the ends of all the edge domains. In general, the local handles are placed at the corners of the 2D domains and at other useful positions. The intent is to make it faster and easier for you to apply parametric changes to the model. Since you morph the model by moving handles, it helps to have handles already at the positions where you want them. HyperMorph tries to predict where the handles should be placed to reduce the amount of time it takes to prepare your model for morphing. If the handles or domains are not laid out in the positions where you want them to be, you can delete them, edit them, or create new ones. Also, even though the generated local handles are associated with the edge domains, they will influence the nodes in any domain that shares the node at which it is placed. This is true even if the handle is associated with the 2D domain. A handle associated with any domain will always influence the nodes in domains that it is touching. Note that it is possible to create a handle on a node that is not touching the domain to which it is associated. This allows you to place a handle outside of a domain, such as floating in space near the domain, and have it influence the nodes within its domain.
Altair Engineering

Tw o 2D dom ains w ith edge dom ains and handles The model on the left show s the initial handle positions. The model on the right show s the addition of four new handles. Handles can be placed anyw here, even at nodes not on the associated domain.
3D Domains Domains made up of solid elements are called 3D domains. When automatically creating local 3D domains, solid elements that share common nodes are grouped together into 3D domains. Shell elements are created on the faces of each 3D domain and placed into a component called ^morphface. It is recommended that you do not delete or edit these elements nor rename or delete the ^morphface component. However, if you do, these elements and their 2D domains will be regenerated the next time you enter or exit a HyperMorph panel or the delete panel. The shell elements on the face of each 3D domain are placed into a 2D domain that is then partitioned if the partitioning option is active. Edge elements are placed around each 2D domain and local handles are created at the ends of each edge domain. In cases where shell elements that are attached to the faces of solid elements are present in the model, HyperMorph will not create ^morphface elements coincident with the existing elements. The color of the ^morphface component can be changed on the morphing visualization dialog accessed by using the visualization options icon on the visualization toolbar. Note that the face elements in the ^morphface component will not be written out to any FEM formatted deck since the component name begins with a "^".

Altair Engineering
A block of solid elem ents is m ade into a 3D dom ain The gray shell elements on the face of the 3D domain are the ^morphface component. The ^morphface component has been partitioned into 2D domains. Handles are created at the corners of the 2D domains.
Edge Domains Domains made up of a list of nodes are called edge domains. When automatically creating local edge domains, edge domains are placed around the edges of all 2D domains. When you are selecting domains and are holding the mouse button down while placing the mouse over the icon of a 2D or 3D domain (or an element in the domain), HyperMesh will highlight both the domain icon and the surrounding edge domains. This makes it easier for you to tell which domain you are selecting. When you release the mouse button, only the icon for the domain remains highlighted. Edge domains and 2D domains on the faces of 3D domains play an important function in determining the influences for the handles over a given domain. Nodes on edge domains will only move as a function of the handles touching the edge domain. No other handles will affect the nodes on the edges. Similarly, nodes in a 2D domain on the face of a 3D domain will only move as a function of the handles touching the 2D domain. This preserves the boundaries of 2D and 3D domains such that straight edges remain straight, flat surfaces remain flat, and curved edges retain their curvature. It allows you to move handles within a 2D or 3D domain without affecting the edges. If you do not want to have the boundaries of a domain preserved you can delete the edges for a given domain, or choose to create the domain as a general domain instead. Also, nonreflective symmetries allow the influences of handles to extend through edges and faces depending on the type of symmetry. For domains that have non-reflective symmetry types, the boundaries may not be preserved during morphing.
Exam ples of edge dom ains Edge domains are placed around the edges of 2D domains. In the model at the right an edge domain has been created inside a 2D domain. Note that w hen an edge domain is created, it is partitioned and handles are placed at the ends and joints.
Altair Engineering

How edge dom ains affect m orphing In the top tw o frames tw o handles inside a 2D domain are created and moved. In the bottom frames, tw o handles connected by an edge domain are created and moved. Note that the edge domain remains straight, preserving the shape of the feature.
General Domains General domains can be made up of any combination of 1D, 2D, and 3D elements. General domains are not automatically created when automatically generating local domains. Like all other domains, the elements within a single general domain must touch one another. When a general domain is created, no 2D domains are created on the faces of any 3D elements and no edge domains are created either, thus no handles are created for the domain. However, general domains respect all neighboring edge domains and 2D domains and thus if you create 2D and edge domains for your general domains they will impose restrictions on handle influences for the general domain. Otherwise, handles on a general domain freely influence all of the nodes inside the general domain, allowing it to stretch and deform in an unbounded manner with morphing extending across differences in element type. General domains are very useful for realized connectors which are often represented as clusters of different element types. Another use is for meshes where precise changes are required for one section, where 1D, 2D, and 3D domains are used, but the rest of the mesh (where a general domain is used) can simply follow along.

Altair Engineering
Exam ple of interaction betw een a general dom ain and 2D dom ains In the top frame, tw o 2D domains are created for parts of tw o shell meshes and a general domain is creating from the remaining rigid, shell, and solid elements. Tw o handles have been placed w ithin the general domain at the ends of the rigid spiders. In the bottom frame the tw o handles inside the general domain are translated. Note how the shell elements in the general domain morph, bounded only by the edge of the 2D domains w ith the other edges free to follow the handles .
Altair Engineering

Partitioning
Partitioning can be applied directly to 2D domains and indirectly to 3D domains (3D domains are created with 2D domains on their faces). Partitioning is a method of dividing 2D domains into smaller 2D domains at logical places, such as at the edges of surfaces associated with the mesh, or where the angle between elements exceeds a certain value, or where the domain changes from flat to curved. Partitioning allows you to prepare your model for morphing more quickly and easily since it divides your model into sections where parametric changes can be applied. You can invoke partitioning when creating 2D or 3D domains by activating the partition 2D domains check box on the Domains panel. If there are no surfaces in the model, or the use geometry option in the partitioning subpanel of the Domains panel is unchecked, partitioning will ideally divide your model such that every radius and straight or flat section is placed into a separate domain. However, partitioning is not an exact science and there will be areas where elements are not placed into the desired domains. If you are unsatisfied with the partitioning, you may change the partitioning parameters in the partitioning subpanel of the Domains panel and try again (using the redo last button), or edit the domains by hand using the create and organize subpanels in the Domains panel.
Exam ple of partitioning For the model on the left, the 2D domain w as created w ithout partitioning. For the model on the right, partitioning w as used. Note how the 2D domains are divided along angle and curvature change boundaries. Also note that the edge domains are partitioned regardless of w hether the partitioning option is on or off.
There are two algorithms you can use to partition, element-based and node-based. These can be set individually for quad/mixed meshes and for tria/tetra meshes. Each algorithm has its strengths and weaknesses, so if one method is not producing the partitions that you desire, the other method might work better. In general, the element-based algorithm works better for quad/mixed meshes and second order meshes, while the node-based algorithm works better for tria/tetra meshes. There are also several parameters that govern the creation of domains for either algorithm. They are found in the partitioning subpanel of the Domains panel. If you have selected use geometry, all elements whose nodes are associated to surfaces in the model will be partitioned along the edges of the surfaces. All other elements will be partitioned using one of the partitioning algorithms. If you have also selected add to geometry, then any partitions created outside of the surfaces will be added to the partitions created using the surfaces if the partitioning algorithm does not find a break along the edges or the surfaces. This option is helpful when surface data is incomplete of some of the nodes have been moved away from their surfaces.

Altair Engineering
Partitioning can be angle-based or curvature-based. In either case, the domain angle controls the break angle along which a partitioning break is made. If the angle between the normal vectors between two elements is greater than this value, a new domain is created with an edge running between the two elements. When using curvature-based partitioning, the curve tolerance controls the angle of which values less than it are considered straight for curvature measuring purposes. If the angle between the normal vectors between two elements is less than this value, they are considered flat, otherwise they are considered to be curved. If the curvature changes from straight to curved, changes direction, or changes curvature by more than the curvature tolerance, a new domain is created with an edge running between the two elements. Note that in order for a new partition to be created, a break due to angle or curvature must be found along its entire edge. For the node based method, domain angle and curve tolerance have a roughly similar meaning as the element based method. The node based method tends to create fewer partitions than the element based method, although exact performance for each method depends heavily on the features in your model. For instance, the node based method seems to work better on first order tria and tetra meshes while the element based method seems to work better on mixed quad and tria meshes.
Altair Engineering

Dependent Handles
You can make a handle dependent on one or more other handles, and then make those handles dependent on one or more other handles, and so on. This system allows you to create any number of dependency layers. Handles that are dependent on other handles appear smaller and in a color different from the handles on which they are dependent. The review button in the update subpanel of the Handles panel allows you to view the handles on which a specific handle is dependent. Making a handle dependent has no affect on the way it influences nodes.
Global handles, independent (red) and dependent (yellow , cyan, and violet)
Local handles, independent (orange) and dependent (green, blue, and pink)
The conditions for handle dependency are as follows: A handle that is dependent on another handle inherits the movements applied to the higher level handle. If a handle is dependent on only one other handle, it inherits the full movement of the higher level handle. If a handle is dependent on more than one handle, it will inherit a percentage of the movements applied to each higher level handle. The percentage is based on the distance between the dependent and independent handles. A handle may be dependent on any number of handles, but dependency loops are not allowed. A dependent handle can be moved independently of the handles on which it is dependent. This means that movements applied to the dependent handle are not applied to the independent handles. This allows you to add the movements of dependent and independent handles in a logical manner. In the hierarchical method, all local handles are dependent on global handles. These dependencies are calculated internally and cannot be modified manually, biasing will affect them.
Handle dependencies are useful for several different applications. Transparent control of domain edges and faces You can create a dependent handle on an edge domain that is dependent on the handles at the ends of the domain. When the dependent handle is moved, the shape of the edge can be changed.

Altair Engineering
When the handle at either end of the edge domain is moved, the dependent handle moves along as if it was not there. This allows you to combine the changes easily without having to apply separate perturbations for all of the handles. Grouping features together to move as a unit You can make all the handles at one cross section of a beam dependent on a single handle. This allows you to move an entire cross section while only having to select one handle. Linking several domains together You can make all of the handles within several domains dependent on a few at the corners of the domain. This allows you to stretch all of the domains uniformly by moving the independent handles, in essence, performing localized "global" morphing.
Altair Engineering

Dependencies - exam ple 1 The center global handle is dependent on the tw o outer global handles. When the highlighted handle on the left is moved (center frame), the center handle follow s along. In the low er frame, the center handle is moved independently.
Dependencies - exam ple 2 In the model on the left, the three green handles on the top are dependent on the orange handle on the top. The bottom has similar dependencies. The top and bottom halves of the cross sections are controlled by just tw o handles. In the model on the right, all of the green handles are dependent on the orange handle. The entire cross section is controlled by one handle. Note that the dependencies can extend beyond the 2D domain boundaries.
Dependencies - exam ple 3

Altair Engineering
An independent handle w as created betw een the tw o holes and the handles governing the positions of the holes are made dependent on it. When the independent handle is moved, both holes move w ith it. Also, each hole can be positioned separately by moving the dependent handle associated w ith it.
Using dependencies to reduce m esh distortion In this example tw o dependent handles w ere created on the edges of the part near the center hole. The dependent handles w ere constrained along vectors parallel to the sides of the part. When the handle at the hole is moved dow nw ard, the dependent handles follow and reduce mesh distortion by spreading the morph across the entire part instead of only around the hole.
Altair Engineering

Working with Shapes

Shapes are collections of handle and/or node perturbations from the initial configuration of the FE mesh before the morph. When you morph your model, HyperMorph stores the morph internally as a collection of perturbations which you can then undo or redo. When you create a shape using the save shape sub-panel on the Morph panel or Freehand panels, the handle and/or node perturbations are stored in the new shape entity along with biasing factors for the handle perturbations and details such as the biasing style. HyperMorph takes the difference between the initial state of the model and the current state of the model when creating a new shape. If you save the model using the save each morph step option in the Shapes panel, each morph on the undo/redo list will be saved as a separate shape. To get to the current state of the model from the initial state, all of these shapes must be applied. Creating shapes allows you to generate shape variables for optimization and store model changes for parametric studies. For many morphing operations, the morph consists only of handle perturbations. However, if constraints are being used, or the morph is a mapping or radius changing operation, node perturbations are required to fully describe the shape. In the case of freehand morphing, the morph consists only of node perturbations. When you create a shape, vectors are drawn for each handle and node perturbation for the shape. The vectors are drawn the exact length of the perturbation and the vectors for the handle perturbations are drawn with thicker lines to denote that they are different from node perturbations. Note that while shapes with handle perturbations will move nodes when they are applied, those shapes do not contain node perturbations and thus vectors are not drawn at those nodes. When you are saving a shape, you can select whether to save it as handle perturbations or node perturbations. If you select handle perturbations, the shape will be saved as either handle perturbations only, or a combination of handle and node perturbations if node perturbations are required to describe the shape. If you select node perturbations, the shape will be saved as node perturbations only. The difference between the two types comes into play if you change the handles or domains in your model. Shapes saved as node perturbations are not affected by changes to domains and handles, while shapes saved as handle perturbations will differ from shapes that have been saved with changes to the handle influences. Whenever you make a change to your model, HyperMorph will ask you if you want to preserve any existing shapes saved as handle perturbations by converting them to node perturbations. If you plan to make changes to domains and handles, you should save shapes as node perturbations. If not, save shapes as handle perturbations and they will require less memory and disk space. If you later decide that you want to change a shape from node perturbations to handle perturbations or vice versa you can do so in the convert subpanel of the Shapes panel. Once a shape is saved, you can apply it to your model with any given scaling factor. Applying a shape in this way is like any other morphing operation and can be undone, redone, or saved as part of another shape.
To convert shapes saved with handle perturbations to shapes saved with node perturbations, or vice-versa:
1. 2. 3. 4. 5. From the HyperMorph module, select the shapes panel. Select the convert subpanel. Select the type of conversion that you wish to perform. Select the shapes to be converted. Click convert.
The shape is converted.

Altair Engineering
Altair Engineering

Setting Up Optimization
Morphing can be used to create shape variables for optimization. Note: A shape is not a shape variable, but by adding a desvar which points to the shape, it becomes a shape variable.
To create shape variables for an optimization run:

1. 2. 3. 4. 5. 6. 7. 8. 9. Morph your model into the shape of the first shape variable. From the HyperMorph module, select the morph panel. Select the save shape subpanel. Save your morph as a shape. Click undo all to return to your base model shape. Repeat steps 1 through 4 for each shape variable you want to create. From the optimization module, select the shape panel. Set the toggle to multiple desvars. Select the shapes for which you want to create shape variables.
10. Click create. A desvar for each shape is created with the initial value and bounds in the panel. Each desvar is given a unique name. 11. Animate the shape variables: Click undo morphing if you did not click undo all after saving the last shape. Click animate. The Deformed panel displays, allowing you to view each shape variable by animating it. Once you have created shape variables for your shapes, you can set up the rest of your optimization problem within the optimization module.

Altair Engineering

Morph Volume strategies are still being created; this help system will be updated in a service pack release to include Morph Volume concepts and strategies.
Altair Engineering


Freehand strategies are still being created; this help system will be updated in a service pack release to include Freehand concepts and strategies.

Altair Engineering
Space Frame Model Strategies

Space frames are models that have a sparse distribution of elements, such as a car body. Space frame models can generally have element counts in the hundreds of thousands, but their basic structure is rather simple. Often the desired shape changes are general, such as making it smaller, shorter, wider, or altering the basic positions of components within the frame. In many instances, these changes can be performed by placing a handle at each joint in the frame and moving those handles to the desired locations. For these types of models, all that is necessary is to create a global domain and global handles. Local handles are not required since local changes to the frame components are not necessary. Since local handles and domains for large models can consume a great deal of resources, you should avoid creating them unless it is necessary.
Creating Handles and Domains Matching a Mesh, Line, or Surface Data Making Parametric Changes Controlling Global Morphing with Handle Placement Mirror Images - Using 1-Plane Symmetry Reducing 3D to 2D - Using Linear Symmetry Reducing 3D to 1D - Using Planar Symmetry
Altair Engineering

Creating Handles and Domains - Space Frame Model

1. 2. 3. 4. 5. 6. 7. Open the HyperMorph module. Select the Domains panel. Select create. Set the selector to global domain. Set the toggle to all nodes. Set the toggle to create handles. Click create. A global domain and global handles are created at useful positions throughout the space frame. In many cases, these handles will be where you want them to be. If not, delete them and add global handles elsewhere: Press F2 or go to the Delete panel. Delete any unwanted handles. From the HyperMorph module, select the Handles panel. Type in a name. Select an xyz position or any number of nodes where you want global handles. Click create.
A new global handle is created at each node or at the specified xyz location. If more than one handle is created at a time, the handles will each be given a unique name by appending a number after the name you have given. You should place global handles both in areas where you want to apply perturbations and in areas that you want to stay fixed. You can also use morph constraints to fix nodes in place during global morphing but if you want them to affect the surrounding mesh you must select the stretch mesh around nodes option when creating the morph constraint. If you want a part of your model to move as a rigid body, such as a wheel or the engine block, use a cluster type morph constraint.

Altair Engineering
A global domain and global handles for a full car model
Exiting any panel in the HyperMorph module or the Delete panel automatically triggers HyperMorph to refresh the handle influences, if necessary. Adding, editing, or deleting handles, domains, or symmetries makes it necessary for HyperMorph to refresh the handle influences. For large models or large changes, this can be time consuming, so you will want to make all the changes you desire within each panel before exiting. There are many options available for moving the handles. The best one to use depends on the results that you want to achieve.
Altair Engineering


Altair Engineering
Matching a Mesh, Line, or Surface Data

The basic approach for HyperMorph is to move the handles into positions that change the shape of the model to match the mesh or geometry data. If you are going to match a mesh you need to make sure that the mesh does not get morphed when you are moving the handles. This can be accomplished by constraining the nodes on the target mesh.
To constrain the nodes on the target mesh:

1. 2. 3. 4. 5. 6. From the HyperMorph module, select the Morph Constraints panel. Select the create/update subpanel. Select the nodes on the target mesh. Switch the selector to fixed. Make sure that the stretch mesh around nodes option is unchecked. Click create. All the nodes in the target mesh are constrained to remain fixed during morphing operations as long as the constraint is active and the use constraints box is checked (see the Morph Options panel). Note that if you check the stretch mesh around nodes option, the nodes between the constrained nodes and the handles will be affected regardless of whether the mesh is continuous between them One of the most enjoyable ways to morph is interactively. As you drag a handle across the screen and you can watch the mesh move along with it. For large models it may be too slow to morph interactively in real time. But you can still morph interactively with any size model by setting HyperMorph to perform the morphing after you move the handle and release the mouse button.
To morph interactively by moving the handle and releasing the mouse button:
1. 2. 3. 4. 5. 6. 7. 8. 9. From the HyperMorph module, select the Morph panel. Select move handles. Change the upper middle selector to interactive . Change the rightmost toggle from real time to on release. Change the lower middle selector from on domains to along vector. Select a vector. Click morph. Select a handle on the screen and hold the mouse button down. Move the handle to the new location and release the mouse button. As you drag the mouse, the handle follows along the selected vector. Since on release was selected, only the graphics for the handle are updated, which leaves a dark trail through the mesh. When you
Altair Engineering

release the mouse button, the morph is applied to the model and the graphics are updated for the entire model. If the handle position needs to be changed again, repeat steps 7 through 9. 10. Move more than one handle at the same time: Before clicking morph, select several handles on the screen. Perform steps 7 through 9. When you release the mouse, all of the selected handles are moved the same distance in the same direction.
Morphing to a profile line

Altair Engineering
In the top frame, the global handles on either side of top of the w indshield are selected. In the middle frame they are interactively moved upw ards along a vector to a point matching w ith the profile line. In the bottom frame the process has been repeated for the other handles on the roof. The result is a morphed vehicle model that closely matches the profile line.
Morphing to a profile line

A handle is added to the center of the rear w indshield and is moved to better match the profile line. Handles may alw ays be added or deleted from a model w ithout affecting the current morphed state of the model. How ever, any shapes saved as handle perturbations may not yield the same morphed shape after handles have been added or deleted. If you intend to add or delete handles in your model, save your shapes as node perturbations. HyperMorph w ill give you the option of converting existing shapes from handle perturbations to node perturbations automatically after you add, edit, or delete any morphing entities.
You can also select other features to drag the handle along such as a line, a plane, or a surface. HyperMorph uses the position of the mouse on the screen to figure out where you want to move the handle. You can use this feature to position a handle anywhere you want line or surface data. To match a target mesh or geometric data by moving the handles to a specified node location: 1. 2. 3. Change the upper middle selector from interactive to move to node. Select a handle. Select a node. The handle is moved to the position where the node was prior to morphing and the rest of the mesh morphs accordingly.
Altair Engineering

To create nodes on the fly on lines and surfaces: 1. 2. Hold the mouse button down and drag the mouse over a line or surface until it is highlighted. Click on the line or surface where you want the node. A node will be created and the handle will immediately be moved to the node.

Altair Engineering
Making Parametric Changes

Dimensions such as distance and angle can be changed easily in HyperMorph. One way to do this is by translating or rotating handles. To translate or rotate handles: 1. Translate the handles. Change the upper middle selector from move to node to translate. Select a few handles. Select a vector and distance. Or Select the desired xyz translation. Click translate. The handles move the specified distance in the specified direction and the model morphs accordingly. 2. Rotate the handles. Change the upper middle selector from translate to rotate. Select a few handles. Select an axis of rotation. Set the rotation angle. Click rotate. The handles rotate about the axis the specified angle and the model morph accordingly. 3. Specify dimensions more precisely in the alter dimensions sub-panel. From the HyperMorph module, select the morph panel. Select alter dimensions. Set the upper left selector to distance. Change the middle left selector to nodes and handles. Select node a and node b at nodes whose distance you want to change Select follower handles for node a that are near node a. Select follower handles for node b that are near node b. Change the distance value. Click morph. HyperMorph moves the follower handles for node a as a group and the follower handles for node b as a group either towards each other or away from each other so that the new distance between node a and node b is equal to the specified distance. If the left selector is set to hold end a, node a will not move (same for node b). If the left selector is set to hold middle, both node a and node b will move the same distance.
Altair Engineering

Morphing by altering the distance between two nodes

The w idth of the car is found by placing node a (green dot) on the right hand door and node b (blue dot) on the left hand door. The handles on the right side of the model are selected as follow ers for node a and the handles on the left side of the model are selected as follow ers for node b. The distance is changed and the model morphs.
To change the angle: 1. 2. 3. 4. 5. 6. 7. Set the upper left selector to angle. Change the middle left selector to nodes and handles. Select node a, vertex, and node b at nodes whose angle you want to change. Select follower handles for node a that are near node a. Select follower handles for node b that are near node b. Change the angle value. Click morph. HyperMorph moves the follower handles for each end in a way so that the new angle between node a, the vertex, and node b are the specified angle. If necessary, HyperMorph will iterate to achieve the desired angle, or at least get close. If node a and node b are selected coincident with one of the follower handles, iteratation is not necessary.

Altair Engineering
Morphing by altering the angle formed by three nodes

The slope of the w indshield is altered by defining an angle using three nodes (green, blue, and red), selecting tw o handles at the front of the car as follow ers for node a (green), and selecting tw o handles on either side of the w indshield as follow ers for node b (red node). The angle is changed from 160 degrees to 150 degrees. Note that the handles on either side of the w indshield w ere constrained to move along the x-axis (front to back) thus maintaining the height of the roof.
Altair Engineering

Controlling Global Morphing with Handle Placement

Global morphing differs from local morphing in that there are no definite boundaries between the handles that restrict their zones of influence. When you perform global morphing operations, the parts of the model that are morphed are those that lie between the handles that are moving and those that are not. For the general space frame cases, positioning handles at the joints between the members of the space frame restricts the handle influences to the parts of the frame that they are touching. However, for cases where you are trying to morph a mesh that covers a wide area, you will need to place several handles across both of sides of the zone of influence. You can visualize the handles as places on a sheet of rubber where you are placing your fingers. If you place three fingers on one side and two on the other and try to stretch the sheet, the space between your fingers on the two finger side will be pulled towards the three finger side. By placing three fingers on each side, you allow for even stretching to occur between each set of fingers. In morphing this is accomplished by placing handles evenly along both sides of the mesh to be stretched.
Controlling global morphing with handles part 1

The handle on the roof is moved upw ards and the center section of the car is morphed along w ith it.

Altair Engineering
Controlling global morphing with handles part 2

A handle is added directly below the handle on the roof near the center of the car. Now w hen the handle on the roof is moved upw ards, only the part of the car betw een the roof and the handles along the midline of the car is stretched.
Altair Engineering


Altair Engineering
Adding handles to control global morphing

Using several handles on either side, the fender of the model is morphed. Note that dependent handles are used to simplify the morphing operation. Also note that in cases w here detailed shape changes are required, morph volumes w ill usually yield better results.
Altair Engineering

Mirror Images - Using 1-Plane Symmetry

If your space frame is symmetric, you can create a plane of symmetry at the center of your space frame and have your morphs applied in a symmetric fashion. To set up a plane of symmetry: 1. 2. 3. 4. 5. 6. 7. 8. 9. From the HyperMorph module, select the Systems panel. Create a system at a node where the plane of symmetry is to be located and have the x-axis pointing normal to the plane to be created. Return to the HyperMorph module, select the Symmetry panel. Enter a name. Select the global domain icon. Switch the selector from none to 1 plane. Select the system you created. Select x-axis as the axis to align the symmetry Change the left toggle from approximate to enforced.
10. Click create. A plane of symmetry is created at the origin of the system and based perpendicular to the x-axis. The icon for a 1-plane symmetry is a rectangle positioned like a small mirror for the symmetry system. HyperMorph also links any handles that it finds that are reflections of the other. Since enforced was selected, HyperMorph creates new handles that are reflections of ones that are not linked to any others and creates a symmetric link between them. When handles are created or deleted, the enforced option will automatically create or delete handles on the other side of the symmetric link in order to enforce symmetry of the handles. The mesh itself does not need to be symmetric to use the symmetry options. The symmetry will be applied to the handles and handle perturbations that will influence the mesh in a symmetric fashion. If you want to add handles to one side of the plane of symmetry and not the other, yet still have symmetry active for the symmetric handles, use the approximate option instead.

Altair Engineering
System and 1-plane symmetry

The plane of symmetry is positioned at the origin of the system and perpendicular to the x-axis. The perturbations applied to handles on one side of the plane of symmetry w ill be mirrored on to the other side.
Now when you perform a morphing operation you only need to move the handles on one side of the plane of symmetry. If you have the symmetry links check box activated, HyperMorph automatically applies the handle movements to the handles on the other side of the plane of symmetry through the symmetry link. As a result, the model maintains symmetry across the symmetry plane.
Altair Engineering

Using 1-plane symmetry

Three handles on the right hand side of the roof are selected and moved tow ards the centerline. HyperMorph automatically moves the corresponding nodes on the left hand side of the roof in a symmetric fashion.

Altair Engineering
Reducing 3D to 2D - Using Linear Symmetry

You can use linear symmetry to apply morphs to the model in such a way that the model is essentially reduced to two dimensions. To create a linear symmetry: 1. 2. 3. 4. 5. 6. 7. 8. 9. From the HyperMorph module, select the Systems panel. Create a system with the x-axis pointing along the dimension to be reduced. Return to the HyperMorph module, select the Symmetry panel. Select create. Enter a name. Select the global domain icon. Switch the selector from 1 plane to linear. Select the system you created. Select x-axis as the axis to align the symmetry.
10. Click create. A linear symmetry is created along the x-axis of the system. The icon for a linear symmetry consists of two parallel lines along the dimension to be reduced. The origin of the system is irrelevant. Now each handle acts on the mesh as if it were a line extending along the system x-axis. If two handles lie along a line parallel to the system x-axis, they will be linked through symmetry. When you move a handle, all the nodes and handles with the same y and z coordinates will move along with it. Note: Since linear is a non-reflective type of symmetry, leaving symlinks unchecked will not prevent the handles from having linear influences. However, it will stop movements from one handle from being applied to others that are linked via the symmetry. If you wish to turn the symmetry off for a given morphing operation, make the symmetry inactive in the Morph Options panel.
Altair Engineering

System and linear symmetry

The linear symmetry icon consists of tw o parallel lines along the system x-axis. Note that the placement of a linear symmetry system does not matter, the effect of the linear symmetry system is determined only by the direction of the x-axis.
Applying a linear symmetry is very useful for making profile changes to a space frame model. It does not matter where the handles are placed along the x-axis, greatly simplifying the model set up. You only need to look at the model from one view to set up the handles and to morph the model. For models with a large number of elements this can save a great deal of time.

Altair Engineering
Using linear symmetry

The handle on the rear part of the roof is selected and the entire rear portion of the roof is morphed along w ith it. With linear symmetry you only need to place handles on one side of the model to affect the entire profile.
Altair Engineering

Reducing 3D to 1D - Using Planar Symmetry

Planar symmetry is similar to linear symmetry accept that it reduces two dimensions instead of one. This enables you to morph your model along a single axis with only two or more handles. To create a planar symmetry: 1. 2. 3. 4. 5. 6. 7. 8. 9. From the HyperMorph module, select the Systems panel. Create a system with the x-axis pointing along the dimension to be retained. Return to the HyperMorph module, select the Symmetry panel. Select create. Enter a name. Select the global domain icon. Switch the selector from linear to planar. Select the system you created. Select x-axis as the axis to align the symmetry.
10. Click create. 11. Return to the HyperMorph module. 12. Select the Symmetry panel. 13. Select update by domain. 14. Select the global domain. 15. Select the planar symmetry. 16. Click update. A planar symmetry is created and the other two symmetries from the global domain are removed. You are allowed to have any number of symmetries associated with a domain and all will apply, but combining linear and planar symmetry in the same direction results in an unrealistic situation and poor influence calculations. The planar symmetry icon is displayed as a filled-in rectangle perpendicular to the system x-axis. Now each handle acts on the mesh as if it were a plane perpendicular to the x-axis. If two handles lie in a plane perpendicular to the system x-axis, they will be linked through symmetry. When you move a handle, all the nodes and handles with the same x coordinates will move along with it. Note: Since planar is a non-reflective type of symmetry, leaving symlinks unchecked will not prevent the handles from having linear influences. However, it will stop movements from one handle from being applied to others. If you wish to turn the symmetry off for a given morphing operation, make the symmetry inactive in the morph options panel.

Altair Engineering
System and planar symmetry

The planar symmetry icon is a plane perpendicular to the system x-axis. Note that the placement of a planar symmetry system does not matter, the effect of the planar symmetry system is determined only by the direction of the x-axis.
Applying a planar symmetry greatly simplifies a model. Essentially, it reduces the model to a lying along single axis. This symmetry type is very useful for changing dimensions along one axis through the entire model.
Altair Engineering

Using planar symmetry

The handle at the rear of the model is selected and the entire trunk of the car is morphed. With planar symmetry you only need a row of handles lying roughly along the planar symmetry system x-axis.

Altair Engineering
Shell Model Strategies

Shell models are models that are made up primarily of shell elements, namely, quads, and trias. In general, a shell model represents many parts, each with numerous features such as holes and edges, and connected together using 1D elements such as bars and rigids. HyperMorph is designed to make it easy to change the size and shapes of the shell model features. This is done using one of the following methods: Moving the handles on the part to new locations Moving the global handles around the parts to new locations Altering the radius or curvature of curved edges of the parts, or mapping the nodes of a part to line or surface data For most models you only need to create 2D domains for the entire part, but you can also add a global domain and global handles for shape alterations of a general nature.
Creating Handles and Domains Morphing on Local Domains Morphing Global Handles Using Constraints Using Biasing
Altair Engineering

Creating Handles and Domains - shell model

1. 2. 3. 4. 5. From the HyperMorph module, select the Domains panel. Select create. Set the selector to 2D domains. Change the toggle to all elements or select all the elements in the model. Click create. A 2D domain is created for each group of continuous shell elements. Parts joined by 1D or 3D elements are separated into different domains. If partition domains is checked, the 2D domains will be partitioned according to the settings selected in the partitioning subpanel of the Domains panel. Once partitioned, edge domains are placed around the 2D domains and handles are placed at the ends of the edge domains. All of this is automatic, but 1D and 3D elements will not be placed into 1D and 3D domains unless you set the selector to local domains instead of 2D domains. In many cases, the domains and handles will be generated where you want them to be. If not you can always add, edit, or delete the handles and domains to meet your needs.
A shell model is partitioned into 2D domains
6.
If you wish to generate a global domain as well as local domains for your model with a single button click, either change the selector to global and local and click create, or to auto functions and click generate.
In the case of the generate auto function, if there are any domains or handles in the model, HyperMorph will first ask if you want to delete all the current morphing entities. If you say "yes", or if there are no morphing entities in the model, HyperMorph automatically generates 1D, 2D, 3D, and edge domains for the entire model and a global domain and handles as well. For tria meshes which lack underlying geometry, both the node-based and element based partitioning algorithms may prove unsatisfactory. In these cases you may find it more effective to ignore curvature when partitioning. To accomplish this, go to the partitioning subpanel, select element based as the algorithm for tria/tetra meshes, and change the uppermost toggle from curvature based to angle based. You may also want to lower the domain angle to 30 degrees. HyperMorph will then only make partitions along edges in the model where the domain angle is exceeded. You can then go in and manually divide the 2D domains where the curvature breaks should go. This method is almost mandatory for meshes that began as first order meshes but were transformed into second order meshes. For these meshes, HyperMorph will detect a curvature break at every element along a curve if the midpoint nodes of the elements have not been modified to capture the curvature. The result will be a domain for every element on a curve which makes morphing impractical.

Altair Engineering
Solving the influence coefficients for 2D domains which contain more than 20,000 elements can become very time consuming even though it is only done after domain editing and during morphing operations such as radius change and map to geom. In these cases you may want to divide the large domains into multiple domains or lower the limit for the large domain solver. The large domain solver limit can be found in the global subpanel of the Morph Options panel. However, even though influence calculations for large domains are more rapid, morphing using the large domain solver can be time consuming, and thus subdividing 2D domains can often be the best solution for efficient morphing. To divide your shell model, do this: 1. 2. 3. 4. 5. From the HyperMorph module, select the Domains panel. Select create. Set the selector to 2D domains. Select the elements to be placed into a new 2D domain. Click create. When selecting the elements for the new domain you do not need to select only shell elements. HyperMorph automatically removes any other elements before creating the domain. It does not matter if the elements selected are already in a 2D domain. When the new domain is created, the elements are moved from the old domains to the new domain. Handle influences need to be recalculated every time handles, domains, or symmetries are added, edited, or deleted. They are also recalculated during radius changes and geometry mapping. These calculations occur when you enter or leave any HyperMorph panel or when you leave the Delete panel. Thus, for models with large domains you will want to make all of your domain changes before exiting the Domains panel. HyperMorph only recalculates the handle influences for handles in regions that have been edited. If the domains are not created exactly how you want them to be, you can edit them in the Domains panel. The create subpanel allows you to create new domains. The organize subpanel allows you to edit domains by adding and removing elements to or from a domain and by grouping domains together. The edit edges subpanel allows you to split, merge, and place handles along edge domains. It is suggested that you create and edit all the 2D domains, then create and edit the edge domains. This order works better since creating or editing 2D domains will result in the regeneration of the surrounding edge domains with the previous modifications to those edge domains being discarded. Sometimes partitioning does not divide the mesh in the ways that would be most useful to you. Occasionally, elements end up in domains adjacent to where you want them or placed in their own domain. Partitioning is not an exact science, so some cleanup is sometimes required. To move elements from one domain to another: 1. 2. 3. 4. 5. From the HyperMorph module, select the Domains panel. Select organize. Change the selector to add nodes/elems. Change the toggle to local domain. Select the elements to be moved.
Altair Engineering

6. 7.
Select the target domain. Click organize. This will move the elements from the domain that they are currently in to the selected domain. HyperMorph also refreshes the edge domains around both domains as well as the edge domains at the interface. New handles may also be created during this process, and if retain handles is not checked, handles may be deleted. It is suggested that you keep retain handles unchecked unless you have created shapes for the model that use the handles on the domains that you are editing.
Partitioning problems The model on the left shows problems that partitioning can encounter for some meshes. The model on the right has been corrected using the organize sub-panel of the domains panel. For this example the retain handles option was left unchecked resulting in the elimination of handles that are no longer on the corners of the 2D domains. Note that the edge domains are always partitioned for any new domain and handles are placed at the end of the edge domains. For the example above, a handle was created in a new location due to the edge partitioning being different for the two domain configurations.
When you hold the mouse button down and the mouse is either over the icon for a 2D domain or over an element inside a domain, the edge domains surrounding the domain are highlighted as well. This allows you to better visualize the domain that you are selecting. The domain icon is placed at the centroid of the domain, and some domains can end up away from the elements of the domain and near other domain icons. Having the edges for the domain highlighted during selection is often necessary to tell which icon goes with which group of elements. To group two or more domains together: 1. 2. 3. 4. 5. From the HyperMorph module, select the Domains panel. Select organize. Change the selector to combine domains. Select the domains to be grouped together. Click organize. The selected domains are combined into a single domain and the surrounding domains and handles are updated.

Altair Engineering
Two domains are organized into one
Edge domains are automatically partitioned when they are created. They are also updated whenever a change occurs for a domain of which they are on the edge. This is why any editing of the edge domains should come after the editing of the other domains. If you do your edge editing first, your changes may be erased when you edit the 2D domains. Edge domains are used to make radius changes, so it is important to make sure that any radius in the model that you intend to change be captured correctly by edge domains. HyperMorph tries to partition edge domains where curvature begins and ends, but in some cases it may not identify the proper starting and ending points. You may need to correct this by hand. To split edge domains: 1. 2. 3. 4. 5. 6. From the HyperMorph module, select the Domains panel. Select edit edges. Change the selector to split. Select an edge domain. Select a node on that domain that is not on the edge. Click split. The selected edge domain is split into two edge domains at the selected node. A handle is created at the selected node.
Altair Engineering

Splitting an edge domain - a circular edge domain is divided into two half circles A handle was created at the joint to allow you to manipulate the edges.
To merge edge domains: 1. 2. 3. 4. 5. From the HyperMorph module, select the Domains panel. Select edit edges. Change the selector to merge. Select any number of connected edge domains. Click merge. The two edge domains are merged into one edge domain. This function only allows you to merge edge domains that lie end to end such that the resultant edge domain is a continuous series of nodes. Note that you can also merge edge domains in the organize subpanel.

Altair Engineering
Merging two edge domains The two half circles are merged into a single domain. Since retain handles was unchecked, the handle at the joint was deleted.
You may also create dependent handles along an edge domain. This feature is quite useful for saving time when you are changing the radius for the edge domain. If the domain containing the radius to be changed is very large you may find it more efficient to place dependent handles on the edge domains whose radii you wish the change before you go into the morph panel. To place dependent handles on the edge domains whose radii you wish the change: 1. 2. 3. 4. 5. From the HyperMorph module, select the Domains panel. Select edit edges. Change the selector to add handles. Select one or more domains. Click create. The dependent handles are created on the selected edge domains. These handles are dependent on the independent handles to either side of them along the edge domain.
Altair Engineering

Creating handles on an edge domain A dependent handle is created on each node of the edge domain.
Creating dependent handles in this way has two significant effects. The first is that since they are dependent, movements applied to any of the independent handles on the edge will be transparently applied to the dependent handles. It will be as if they were not there. Secondly, when you make a radius change to an edge domain that has a handle at each of its nodes, the influences do not need to be recalculated, which makes the radius change process much faster for large models. 6. When you are satisfied with your domains, click return. HyperMorph calculates the influences for the handles and you are ready to begin morphing. During influence calculation you might run out of available memory. This generally happens when a given domain is too large and it contains too many handles. In these cases you should divide large domains, delete unnecessary handles, or lower the limit of the large domain solver.

Altair Engineering
Morphing on Local Domains

You can change the shape of a model with local domains and handles using one or more of the following methods: Moving the local handles Changing a distance or angle Changing the radius, curvature, or arc angle of an edge domain Mapping nodes to a line, plane, surface, or mesh Using section mapping, line and surface difference, and element offset Using freehand morphing capabilities such as move nodes, record, and sculpting There are six ways to move handles in the move handles subpanel of the Morph panel: interactive This option allows you to move handles interactively by dragging the mouse across the screen. You select an entity such as a vector, line, plane, surface, or domains, to orient the mouse location in 3D space, and move a handle by clicking on it and dragging it to a new location. Interactive morphing is most effective for visualizing how the mesh will react when a handle is moved and for making approximate shape changes. If you want to move a handle a specific distance or to a specific position, it is better to use a non-interactive option. This option allows you to translate handles along a vector or element normals. This option allows you to rotate handles about an axis. This option allows you to position handles at specific XYZ locations or place them on lines, surfaces, or another mesh. These options allow you to position handles at specific node or point locations, or place them on lines, surfaces, or another mesh.
translate
rotate move to XYZ
move to node, move to point
Altair Engineering

Morphing by translating handles: By selecting the two handles along the edge of the flange and translating them along a vector defined at the end of the section (green and blue nodes), the length of the flange is reduced.

Altair Engineering
Morphing by translating handles: By selecting the three handles and translating them along a vector defined at the end of the section, the width of the channel is increased.
Morphing by translating handles: By selecting the handles at the bottom of the part and translating them upwards, the thickness of the lower section is reduced.
Altair Engineering

Morphing by translating handles: By selecting all the handles around the bolt boss and translating them horizontally, the position of the bolt boss is modified.
Morphing by rotating handles - constant: By selecting all the handles at the end of the section and rotating them about a point (violet node), the end angle of the section is modified.
Morphing by rotating handles - constant: The right end of the block is given a constant rotation.

Altair Engineering
Morphing by rotating handles - linear: The entire block is given a linear rotation. Note how the magnitude of the twist increases linearly with the distance from the base (purple) node.
When applying handle perturbations to your model, it is important to note that the nodes in the model follow the movements of the handles according to the influence coefficients. This concept comes into play when you are using the rotate function. After rotating handles you may find areas in the model (particularly those defined by curved edges) that are not rotated the same as the neighboring handles. This is because the nodes have followed the handles instead of being rotated about the axis. To correct this situation, check the true rotation checkbox. This will cause the nodes to be rotated as well as the handles with the amount of rotation being equal to the influence coefficient. Although it could be argued that true rotation is the "correct" way to morph via rotation of the handles, not all morphing applications are best done using true rotation.
Morphing by rotating handles - normal: Although the highlighted handles are rotated, the circle at the center of the model remains on the same plane as before.
Altair Engineering

Morphing by rotating handles - true rotation: During "true rotation" the nodes rotate along with the handles.
While morphing a model, the following message may be displayed: "Some handles selected are dependent on others. Would you lik e to ignore dependencies for this operation?". This occurs when both a dependent handle and the handle on which it is dependent are selected to be morphed. If you click yes the given perturbation is applied to each handle and the dependent handles are not given an additional perturbation inherited from another handle. If you click no, the given perturbation and any inherited perturbation is applied to each dependent node. For most cases you will want to click yes. The alter dimensions subpanel of the Morph panel allows you to change one of the parameters in the model, such as the distance between nodes, the angle between nodes, or the radius or curvature of an edge domain. The basic concept is as follows: Select two nodes (node a and node b). Select handles corresponding to those nodes. The handles selected are the ones that will move to make the distance between node a and node b (or angle with a vertex selected) equal the specified value. You must select at least one handle for each end and the handle may be coincident with one of the nodes. For solid models, controlling a particular dimension often involves moving more than one handle for each end.

Altair Engineering
Morphing by altering dimensions - distance: By selecting the width of the bottom of the channel as the desired distance to alter (green and blue nodes) and by selecting the handles on the left (highlighted) to follow the green node and the handles on the right (shown as gray) to follow the blue node, the width of the bottom of the channel can be changed from 60 to 30 with the rest of the channel changing along with it.
Morphing by altering dimensions - distance: By selecting the thickness of the block as the desired distance to alter (green and blue nodes) and by selecting the handles on the radius (shown as gray) to follow the green node and the handles on the back face (highlighted) to follow the blue node, the thickness of the block between the radius and the back face is altered from 15 to 25 by moving the entire back face.
Altair Engineering

Morphing by altering dimensions - angle: By selecting the angle of the left side of the channel (green, blue, and red nodes) and by selecting the handle at the bottom right of the channel (shown as gray) to follow the green node and the handle at the red node (highlighted) to follow the red node, the angle of the left side of the section is changed from 110 degrees to 90 degrees.
Morphing by altering dimensions - angle: By selecting the angle between two faces of the block (green, blue, and red nodes) and by selecting the handles at and directly below the green node (shown as gray) to follow the green node and the handles at, near, and below the red node (highlighted) to follow the red node, the angle is altered from 126 degrees to 90 degrees.
The radius, curvature, and arc angle options are used as follows. You select any number of curved edge or 2D domains, select the center calculation and style options, set the new radius, curvature multiplication, or

Altair Engineering
arc angle factor for them, and click morph. All the domains are changed simultaneously. Note: The curvature tool scales your radius by a factor rather than a set radius, so if you want to change a radius from 5.0 to 8.0, you need to set the curve ratio to 1.6. The curvature tool is intended for domains that do not have constant curvature. Note: Making the bias factor retroactive does not work for radius changes.
Morphing by altering dimensions radius center: By selecting the edge domain around the edge of the hole, the radius is changed from 3 to 1.5.
Morphing by altering dimensions - radius - fillet: By selecting the edge domain at the corner of the part and selecting the fillet option, the radius is changed from 5 to 2.5 and kept in line with the edges at either end.
Altair Engineering

Morphing by altering dimensions - radius - hold ends: By selecting the edge domain at the corner of the part and selecting the hold ends option, the radius is changed from 5 to 10 with the ends held in place.
Morphing by altering dimensions - radius - hold end: By selecting the edge domain at the corner of the part, selecting the hold end option, and selecting a node at the end of the edge domain, the radius is changed from 5 to 8 while the held end remains in place.

Altair Engineering
Morphing by altering dimensions - radius - fillet: By selecting all of the edge domains that form the fillet between the flat sections and the round section and changing them simultaneously, the fillet is reduced from 20 to 8.
Morphing by altering dimensions - radius: The radius is changed in three different ways. At the top right, the hold center option is used. At the lower left, the hold ends option is used. At the lower right, the fillet option is used. In all cases, both the top and bottom edge domains were selected as well as the 2D domain and the by normals option was used for center calculation. This option will directly calculate the radii for the nodes on the 2D domain instead of inferring them from the edge domains which makes this approach more accurate for 2D domains as well as more reliable for non-uniform meshes.
Altair Engineering

Morphing by altering dimensions - arc angle: The arc angle of the mesh is changed from 60 to 90 degrees using by axis (the vertical axis and violet base node) to calculate the center of curvature.
Morphing by altering dimensions - arc angle: The arc angle of the fillet is changed from 90 to 180 degrees using by normals to calculate the center of curvature.
There are five methods available for calculating the center of curvature for the selected domains: by normals - this method is the default and uses the element normals to approximate where the center of curvature is for each node in the selected domains. This method is not always accurate, but often gives good results for regular meshes. by axis - you may select an axis which will serve as the center of curvature. by line - you may select a line which will serve as the center of curvature. by node - you may select a node which will serve as the center of curvature. by edges - this method uses the edge domains to calculate the center of curvature with the center lying in the plane of the edge domains. The symmetry option refers to how the morphing of the edge domains is applied to neighboring 2D domains. The auto-symmetry option was the default for HyperMorph prior to version 8.0. In 8.0 you may choose to turn off symmetry when using this option. For auto-symmetry, the changes in the radii of the edge domains are applied to any 2D domain, depending on the number of edge domains you change for the 2D domains. If you change only one edge domain for a

Altair Engineering
given 2D domain, the radius change will not be applied linearly across the 2D domain. If you change the radii of two edges for any given 2D domain, either a linear or planar temporary symmetry is created between the two edge domains for the 2D domain that will apply radius changes more linearly across the 2D domain. This works best if the mesh is regular. If you are changing only one edge for a 2D domain, you can increase the bias factor of any handles on an edge domain to yield a more even distribution. Mapping an edge domain to a line or a 2D mesh to a plane, surface, or mesh is done using the map to geom panel. This option is very effective for fitting a mesh to new geometric data. When mapping a domain to a geometric feature, all the nodes in neighboring domains are stretched along with it, minimizing mesh distortion. You have several options for determining how the nodes for the mapped domain are placed on the geometry. When mapping an edge domain or node list the nodes can be moved normal to the line, along a vector to the line, or distributed along the full length of the line. When mapping a 2D domain or selection of nodes to a plane, surface, or mesh, the nodes can be moved normal to the target, normal to the elements of the 2D domain or selected nodes, or along a vector. If you wish to fit a mesh to a surface, there is no option to do this automatically, however, with multiple mapping operations, or using the user control option you can fit a 2D domain to a surface. Furthermore, you have the option of creating a morph constraint between the nodes and the map target automatically after mapping. This constraint will allow you to do further morphing operations while maintaining the constrained nodes on the geometry. . The map to geom panel is also effective for solid model meshing. You can create a block of solid elements roughly in the shape of the geometry that you are trying to mesh, and then use map to surface to morph the faces of the block to the geometry.
Morphing by mapping to line - automap - normal to geom: The edge domain is mapped to a line by moving the nodes normal to the line.
Altair Engineering

Morphing by mapping to line - automap - fit to line: The edge domain is mapped to the line by fitting them along the line. Any proportional spacing between the nodes will be maintained after mapping.
Morphing by mapping to surface: By selecting the 2D domain on the top of the solid block to be mapped to the surface, the entire solid block is morphed to match the surface.

Altair Engineering
Morphing by mapping to surface: A rectangular C-section is mapped to a curved surface.
Morphing by mapping to surface - user control: This example shows the user-control approach to mapping a mesh onto a surface. The surface and 2D domain are selected and the user control button is clicked. This brings up a new panel which allows you to place handles or map edges prior to the surface mapping operation. One by one each edge domain is placed on one of the lines around the target surface using the fit to line option. This stretches the 2D domain to match the surface more closely than before. When the map button is clicked, the domain is the mapped to the surface, fitting it perfectly to the geometry.
Altair Engineering


Altair Engineering
Morphing Global Handles

Global handles are most effective when used to make general shape changes for a model, such as changing the basic shape of a model, stretching parts of a model, or making changes that involve the movement of many local handles. There are three methods available for affecting the way global handles influence the model, the direct method, the hierarchical method, and the mixed method. The default is the direct method, where the global handles move the nodes directly. In the hierarchical method, the global handles move the local handles which in turn move the nodes, but if any nodes lie outside of local domains they will be unaffected. In the mixed method, the hierarchical method is used for all nodes in local domains and the direct method is used for all other nodes. The hierarchical method maintains the shape of edge domains in the model, but if local handles are not evenly placed throughout the model, some parts will become distorted. The direct method gives you what you expect but often distorts the shape of the edge domains. For shell and solid models, better morphing is more likely to occur if you use the hierarchical method, and place local handles in areas where there is distortion.
Altair Engineering

Using Constraints
Morph constraints are a powerful tool that can be used to restrict the movement of nodes during morphing operations. The following types of constraints can be applied to any node: fixed, cluster, along vector, on plane, along line, on surface, and on elements. Whenever a handle is moved that influences a node which is constrained, the node is moved according to the handle perturbation and is then projected back onto the feature to which it is constrained. This allows the nodes to slide across vectors, lines, planes, surfaces, and meshes, to remain fixed when handles are moved, or to move as a cluster along with other nodes. You may also constrain nodes where handles are located which, in effect, constrains the handles. When a perturbation is applied to a constrained handle, the handle are moved along the constraint feature regardless of the applied perturbation. This means that if you apply a translation in the x direction on a handle that is constrained along a vector x - y = 0, the handle moves along both the x and y axes. There are also morph constraints that can be applied to domains, such as the smooth constraint, which applies spline-based smoothing along the constrained edge domains, and model constraints, which allow you to set a given parametric target (such as length, angle, mass, etc.) and have HyperMorph adjust the model to meet that target. These constraints as well as bounded and set distance options for the node constraints are described more fully in the panel help. Morph constraints can be very useful for morphing a mesh that has been mapped to, projected to, or created upon a surface. Note that the map to geom operation allows you to have a morph constraint automatically created after mapping. Once you have done so, the nodes will remain on the surface during morphing operations. Note: Although morph constraints can keep nodes on a curved line or surface during morphing operations, when morphs are saved as shapes and then turned into shape variables for optimization, the nodes will not stay on the line or surface during optimization. This is because optimization is a linear process and the shapes will be treated as linear, meaning that the nodes will move directly from their original point to their maximally perturbed point without moving along any constraint.
Controlling handle positions with morph constraints The angle of the lower right corner is changed from 74 to 90 degrees using the alter dimensions (angle) operation. The middle frame shows the result with no constraints. The frame on the right shows the result with the node in the upper right corner constrained to move along a vector that lies along the top edge.

Altair Engineering
Nodes tracking a line during morphing The nodes along the right edge domain are constrained to the line. When the handle is moved, it and the other constrained nodes move along the line.
Morphing after mapping to surface All mapped nodes are automatically constrained to the surface. When the handles are translated, the nodes are moved along the surface a distance corresponding to the applied handle perturbations. If the handles were also part of the map to geom operation, they too will be moved along the surface regardless of the applied perturbation. In this example, the handles were translated linearly. HyperMorph automatically placed the handles back on the surfaces after applying the translation so that the constraint was obeyed.
Altair Engineering

Using Biasing
Biasing allows you to control the shape of a mesh when applying handle perturbations. Biasing increases or decreases the influence of a handle over the nodes within its area of influence. If the biasing values for all of the handles are equal to 1.000, which is the default value for all handles except for dependent handles on 1D domains, the morphing between the handles is linear, provided both handles are global handles or they are located on edge domains. Higher biasing values generate a smooth curvature near the handles, while lower biasing values generate harsh corners near the handles. To smoothly change the shape of a domain it is recommended that you use a biasing factor of 1.000 at the corners, 2.000 at the edges, and 3.000 in the middle.
Biasing for a 2D domain The model at the upper left has all five handles with the default biasing value of 1.000. The model at the upper right shows the four corner handles with a biasing value of 1.000, and the mid-edge handle with a biasing value of 2.000. The model at the lower left has all five handles with the default biasing value of 2.000. The model at the upper right shows the four corner handles with a biasing value of 1.000 and the mid-edge handle with a biasing value of 0.500.

Altair Engineering
Biasing to reduce mesh distortion When the hole is moved downward with a biasing factor of 1.000 for the handle at the hole, the mesh folds over due to the influences of the other handles (middle frame). When the biasing value of the handle at the hole is increased to 3.000, the mesh unfolds (right frame).
Biasing can be applied retroactively after a morphing operation. After applying a morph, you can change the biasing value by activating the make retroactive check box, and have the current list of applied morphs updated to reflect the new biasing values. This is useful in selecting a good biasing value to apply for a given morph. Apply the morphs and change the biasing values retroactively until you get the shape that you want.
Altair Engineering

Solid Model Strategies

Solid models are models that are made up of solid elements, namely, tetras, pentas, and hexas. In general, a solid model represents a single part with numerous features such as holes, edges, bosses, flanges, and ribs. HyperMorph is designed to make it easy to change the size and shape of features in a solid model. This is done using one of the following methods: Moving the handles on the part to new locations Moving the global handles around the part to new locations Altering the radius or curvature of curved edges of the part Mapping the nodes of the part to line or surface data. For solid models, it is only necessary to create a single 3D domain for the entire part. You can also add a global domain and global handles for shape alterations of a general nature.
Creating Handles and Domains - solid model Viewing Solid Models Morphing on Local Domains Morphing Global Handles Using Constraints Using Biasing

Altair Engineering
Creating Handles and Domains - solid model

You can create a single 3D domain consisting of all the elements in a model. If the model is made up of more than one part, each part is placed in its own 3D domain. The surfaces of each 3D domain are covered with shell elements that are placed in a component named ^morphface. The elements in ^morphface covering each 3D domain are placed into 2D domains. If partition 2D domains is checked, these 2D domains are partitioned according to the settings selected in the parameter sub-panel of the domains panel. Once partitioned, edge domains are placed around the 2D domains and handles are placed at the ends of the edge domains. This procedure is automatic. In many cases, the domains and handles are generated where you want them to be. If they are not, you can add, edit, or delete the handles and domains to meet specific needs. To create a single 3D domain consisting of all the elements in the model: 1. 2. 3. 4. 5. From the HyperMorph module, select the Domains panel. Select create. Set the selector to 3D domains. Change the toggle to all elements, or manually select all of the elements in the model. Click create.
A 3D domain is created for a solid model Note the automatic creation and partitioning of 2D domains on the face of the solid and the creation of edge domains and handles for the 2D domains.
To create a 3D domain along with a global domain and global handles to your model: 1. 2. 3. 4. From the HyperMorph module, select the Domains panel. Select create. Set the selector to auto functions. Click generate. If there are any domains or handles in the model, you are asked if you want to delete all the current morphing entities. If you click yes, or if there are no morphing entities in the model, 1D, 2D, and 3D domains are automatically generated for the entire model, as well as a global domain and handles.
Altair Engineering

Automatic generation of domains on a solid model Note the addition of a global domain, global handles, and 1D domain, which produces dependent (green) handles.
If you do not select partition 2D domains when you generate a 3D domain, the 2D domain made up of the elements on the surface of the 3D domain will not have edge domains and thus no handles will be generated for it. Without handles, morphing cannot be performed. However, this approach will give you a "blank slate" 2D domain that you can partition by hand. For meshes on which the automatic partitioning does not work well, such as first order tetra meshes, you may find it easier to start with a blank slate rather than editing the automatically created domains. Be sure to try both methods of partitioning, element based and node based, before deciding to partition by hand. Note: The element based method sometimes works better on second order tetras since it accounts for element curvature. However, if the second order tetras are converted first order tetras and thus have no curvature, the node based partitioning will work better.
Also, for first order tetra meshes, you may find it more effective to ignore curvature when automatically partitioning. To do this, in the parameters sub-panel, change the uppermost toggle from curvature based to angle based. You may also want to lower the domain angle to 30 degrees. Partitions will be made only along edges in the model where the domain angle is exceeded. You can then manually divide the 2D domains where the curvature breaks should be located. This method is very helpful for meshes that began as first order tetra meshes but then were then transformed into second order meshes. For these meshes, a curvature break is detected at every element along a curve if the midpoint nodes of the elements have not been modified to capture the curvature. This results in a domain for every element on a curve which makes morphing impractical. Solving the influence coefficients for 3D domains which contain more than 20,000 elements can become very time consuming even though it is only done after domain editing and during morphing operations such as radius change and map to geom. In these cases you may want to divide the domain into multiple domains using the subdivide 3D function in the update sub-panel of the domains panel, or lower the limit for the large domain solver. The large domain solver limit can be found in the global subpanel of the morph options panel. However, even though influence calculations for large domains are more rapid, morphing using the large domain solver can be time consuming, and thus subdividing 3D domains can often be the best solution for efficient morphing. Additionally, if you are only going to morph a part of your 3D mesh, you only need to create domains for that part.

Altair Engineering
To subdivide your solid model: 1. 2. 3. 4. 5. 6. From the HyperMorph module, select the Domains panel. Select update. Set the selector to subdivide 3D. Select the 3D domains to be subdivided. Select any 2D domains on the surface of the 3D domain that are permissible for HyperMorph to split into more than one 2D domain. Click subdivide. HyperMorph automatically subdivides the 3D domains into one or more 3D domains while leaving the 2D domains not selected as being divisible unchanged. Not that in some cases HyperMorph will not be able to subdivide a 3D domain without dividing an indivisible 2D domain. In these cases the 3D domain will be left undivided. To divide your solid model manually: 1. 2. 3. 4. 5. From the HyperMorph module, select the Domains panel. Select create. Set the selector to 3D domains. Select the elements to be placed into a new 3D domain. Click create. When selecting elements for the new domain, you do not need to select only solid elements, other elements are automatically removed before the domain is created. Therefore, you do not need to be concerned about selecting the morphface elements. Also, it does not matter if the selected elements are already in a 3D domain. When the new domain is created, the elements are moved from the old domains to the new domain. Morphface elements are placed at the internal interface between the new domain and the other domains and create a 2D domain for the interface, but it will not partition the interface. This better accommodates the division of tetra meshes that cannot be divided along flat or curved internal faces and thus would be partitioned into many domains. Note: When you divide a 3D domain into parts, it has the effect of partitioning the surface of the original 3D domain along seams where the divisions were made. So when you divide your model into 3D domains, make sure that you divide it along lines where you want your 2D domains on the surface to be.
Dividing a 3D domain into many 3D domains can be very useful for controlling the movement of nodes within the domain when the handles on the surface are moved. When some meshes are morphed, the internal elements can become distorted. This is generally caused by handle influences extending too far through the 3D domain. You can divide your 3D domains to restrict the handle influences and control mesh distortion.
Altair Engineering

A single 3D domain is split into four 3D domains The influences of the handles will not extend across the boundaries between the domains.
Influences must be recalculated every time handles, domains, or symmetries are added, edited, or deleted. They are also recalculated during radius changes and geometry mapping. These calculations occur when you enter or leave a HyperMorph panel or when you leave the delete panel. For large models you will want to make all of your domain changes before exiting the domains panel. The influences for handles are only recalculated in regions that have been edited. If the domains are not created exactly the way you want them, you can edit them in the domains panel. The create sub-panel allows you to create new domains. The organize sub-panel allows you to edit domains by adding and removing elements to or from a domain and by grouping domains together. The edit edges sub-panel allows you to split, merge, and place handles along edge domains. Since creating or editing 3D domains results in the creation of 2D and edge domains, and creating or editing 2D domains results in the creation and deletion of edge domains, you should perform the tasks in the following order: 1. 2. 3. Create and edit all the 3D domains that you want first. Create and edit the 2D domains. Create and edit the edge domains. Automatic partitioning does not always divide a mesh in the most useful ways. Occasionally, elements end up in domains adjacent to where you want them or placed in their own domain. Some cleanup may be required. To move elements from one domain to another: 1. 2. 3. 4. 5. 6. From the HyperMorph module, select the Domains panel. Select organize. Change the selector to add nodes/elements. Select the elements to be moved. Select the target domain. Click organize. The elements are moved from their current domain to the selected domain. The edge domains around both domains are refreshed, as well as the 2D domains at the interface if solid elements are being organized. New handles may also be created during this process, and if retain handles is not checked,

Altair Engineering
handles may be deleted. You should keep retain handles unchecked unless you have created shapes for the model that use the handles on the domains that you are editing.
The model on the left shows problems that partitioning can encounter for some meshes. The model on the right has been corrected using the organize subpanel of the Domains panel. For this example, the retain handles option was left unchecked, resulting in the elimination of handles that are no longer on the corners of the 2D domains.
Note:
Holding the mouse button down when the mouse is either over the icon for a 2D or 3D domain or over an element inside a domain, will highlight the edge domains surrounding the domain. This allows you to visualize the domain that you are selecting. The domain icon is placed at the centroid of the domain, and for some domains it can end up away from the elements of the domain and near other domain icons. Having the edges for the domain highlighted during selection is often necessary to tell which icon goes with which group of elements.
To group two or more domains: 1. 2. 3. 4. 5. From the HyperMorph module, select the Domains panel. Select organize. Change the selector to combine domains. Select the domains to be grouped. Click organize. The selected domains are combined into a single domain, and the surrounding domains and handles are updated. Edge domains are automatically partitioned when they are created. They are also updated whenever a change occurs for a domain of which they are on the edge. This is why you should edit the edge domains after the other domains have been edited. If you perform edge editing first, your changes may be erased when you edit the 2D and 3D domains. Edge domains are used to make radius changes, so it is important to make sure that any radius in the
Altair Engineering

model that you intend to change be captured correctly by edge domains. HyperMorph attempts to partition edge domains where curvature begins and ends, but in some cases, it will not identify the proper starting and ending points. You will need to correct this by hand. To split edge domains: 1. 2. 3. 4. 5. 6. From the HyperMorph module, select the Domains panel. Select edit edges. Change the selector to split. Select an edge domain. Select a node on that domain that is not on the edge. Click split. The selected edge domain is split into two edge domains at the selected node. A handle is created at the selected node.
The lower edge domain has been split at the gray node (left model), which becomes a handle (right model). Now the radius of each new edge domain may be modified independently of the other.
To merge edge domains: 1. 2. 3. 4. 5. From the HyperMorph module, select the Domains panel. Select edit edges. Change the selector to merge. Select any number of edge domains. Click merge. The two edge domains are merged into one edge domain. This function only allows you to merge edge domains that lie end-to-end such that the resultant merged edge domain is a continuous series of nodes. You may also create dependent handles along an edge domain. This feature helps save time when you are changing the radius for the edge domain. If a model is very large, you may find it more efficient to place dependent handles on the edge domains whose radii you wish to change before you enter the morphing panel.

Altair Engineering
Note that you can also merge edge domains in the organize subpanel. To create dependent handles along an edge domain: 1. 2. 3. 4. 5. From the HyperMorph module, select the Domains panel. Select edit edges. Change the selector to add handles. Select one or more domains. Click create. Dependent handles are created on the selected edge domains. These handles are dependent on the independent handles to either side of them along the edge domain.
Dependent handles created using the handles on edge feature
Creating dependent handles in this way has two significant effects. The first is that since they are dependent, movements applied to any of the independent handles on the edge are transparently applied to the dependent handles. It will be as if they were not there. Secondly, when you make a radius change to an edge domain that has a handle at each of its nodes, the influences do not need to be recalculated, which makes the radius change process much faster for large models. 6. When you are satisfied with your domains, click return. The influences for the handles is calculated and you are ready to begin morphing. Note: During influence calculation for large models you might run out of available memory. This generally happens when a given domain is too large and it contains too many handles. In these cases, you should divide large domains, delete unnecessary handles, or lower the limit of the large domain solver.
Altair Engineering

Viewing Solid Models

The HyperMesh graphics engine supports different visual options for viewing models as you work on them. surface-only wire frame In this default mode, your model is displayed as a wire frame, but only the surface elements are drawn because in a solid model, a full wire frame can make it very difficult to visualize the model because every element in the model is displayed. Since HyperMorph creates a component called ^morphface, which contains shell elements on the surface of the 3D domains, the default setting is to display only that componentthus showing only the outer surface of your model and making it easier to work on. However, since the viewing mode is still wire frame, you will see the two sides of your model superimposed over each other.
solid fill
The option produces a display that is similar to what you see when you perform a fill plot in the Hidden Line panel. You only see the side of the model that is facing you (as if your model was a real part). You can still display the surface mesh, if desired (as shown).
You can also view a solid model for morphing by turning off all the components and looking at only the domains and handles. This is similar to looking at the model in a meshless wire frame mode. Partitioning generally captures all the features on the surface of a solid, so by viewing only the domains you can visualize the model with minimal clutter.

Altair Engineering
Altair Engineering

Optimization
HyperMesh Optimization technology is supported by Altair OptiStruct. OptiStruct is a finite element and multi-body dynamics software application which can be used to design and optimize structures and mechanical systems. OptiStruct uses the analysis capabilities of RADIOSS and MotionSolve to compute responses for optimization. Note that OptiStruct has its own, complete help system which you can consult for greater detail; this chapter of the HyperMesh User's Guide is only an overview of the concepts involved.
Structural Design and Optimization

Structural design tools include topology, topography, and free-size optimization. Sizing, shape and free shape optimization are available for structural optimization. In the formulation of design and optimization problems, the following responses can be applied as the objective or as constraints: compliance, frequency, volume, mass, moment of inertia, center of gravity, displacement, velocity, acceleration, buckling factor, stress, strain, composite failure, force, synthetic response, and external (user defined) functions. Static, inertia relief, nonlinear gap, normal modes, buckling, and frequency response solutions can be included in a multi-disciplinary optimization setup.
Setting up Optimization in HM
All of your optimization entities can be managed through 3 different ways; the Model Browser's Optimization View, the Menu Bar, or the Panels. The first thing you should do is start with a running model of your analysis type supported by RADIOSS or MotionSolve. From here the optimization setup in HM is very simple process, called DRCO. Each letter is a stage in the process: defining or creating your Design space, creating your Responses, defining your Constraints and define your Objective.
See Also OptiStruct OptiStruct Tutorials

Altair Engineering
Model Browser Optimization View

See the Browsers chapter for more detail on the Model Browser and its Optimization View.
Altair Engineering

The Menu Bar

The Optimization Menu exists in the HyperMesh Menu Bar.

Altair Engineering
The Panels
Optimization panels are located inside of the Optimization module, which is part of the Analysis page.
Altair Engineering

Conversion between Solver Formats

Finite element models defined for a particular card image solver generally cannot exchange information with other card image or dictionary format solvers without manipulation of the data. Finite element models defined in a particular user profile cannot be converted to another solver format by just changing the user profile. There are two methods available to convert data from one user profile to another. You can either use the Conversion framework or the Convert panel. Both are accessible through the menu bar by clicking Tools > Convert.
Conversion Tools
The functionality to convert model files from one solver format to another is supported. 1. 2. Load your model. From the Tools menu, select Convert. Select the solver format you'd like to convert from, and then select the solver format that you are converting to.
3. 4.
A window appears asking if you want to load the chosen solver's user profile to continue. Select Yes, and the Conversion tab appears. In the Destination template field, select the appropriate template for your destination solver.

Altair Engineering
5. 6.
The Configuration File field is automatically populated. The default file, ConfigurationFile.txt provides a valid mapping scheme for the conversion. The entities window displays all the entities identified in the model. The color status bar illustrates the conversion status of each entity. Clicking on an entity name will display information regarding that entity in the lower portion of the tab. In addition, you can right-click on an entity name to open the Card Edit panel for that entity. Click Convert to convert the file. A window appears, informing you of the status of the conversion. Note that the user profile is automatically updated to the selected solver's format. Click Close to close the status window.
7. 8.
Conversion Framework
When launching the conversion framework (Tools > Convert), a browser opens up showing model contents. When expanding folders you can see individual solver cards listed. Each of them is color coded green, orange or red to highlight to which extent the card is converted to the targeted solver. Clicking on an individual card will provide more detailed information in the lower window of the browser. There you can check to see which card the current entity is mapped to, as well as which parameters are translated. Right-click to display the context sensitive menu, and select Edit Card for direct access to the card image of the solver card.
Using the Convert Panel

The Convert panel offers very limited conversion capabilities only and is no longer recommended for use. See the Convert panel for more information.
Note :
See the Convert panel for more information.
See also Abaqus Conversion Tools ANSYS Conversion Tools LS-DYNA Conversion Tools Nastran Conversion Tools PAM-CRASH 2G to RADIOSS (Block Format) Conversion RADIOSS Conversion Tools Interfacing with Finite Element Solvers
Altair Engineering

Abaqus Conversion Tools

The following conversions are possible when in the Abaqus user profile:
Abaqus to Nastran conversion Abaqus to RADIOSS (Bulk Data Format) conversion Abaqus to RADIOSS (Block Format) conversion

Altair Engineering
Abaqus to Nastran Conversion

The Abaqus to Nastran conversion tool uses an open conversion scheme; you can specify different mappings in the configuration file. Care has to be taken so that the element and property mappings are consistent. We provided a valid mapping scheme in the ConfigurationFile.txt. This document explains the scope and limitations of the mapping scheme.
Elements
HM elements have two basic attributes configuration (or config) and type . The "config" defines the basic geometrical shape of an element. For example, tria3 configuration is a 3 node triangular element and hexa8 is an 8-node hexahedral element. The "type" defines the solver specific element type of a particular configuration. For example, the 4-node quadrilateral (quad4) element in Abaqus can be any of the following types: S4, S4R, M3D4, R3D4 etc. The Element Types panel shows all supported element configurations and their types for a user profile. For a specific configuration, you can map any supported Abaqus element type to any supported Nastran element type, or vice versa. For example, for an Abaqus to Nastran direction, several 2-noded element configurations such as spring, rigid, bar2, rid, etc., are supported. Because all of them are 2-noded elements, conversion across these configurations is also allowed for some element types. For example, CBUSH is of "spring" configuration in the Nastran user profile and CONN3D2 is of rod" configuration in the Abaqus user profile. It is possible to map a CBUSH to CONN3D2 even though their configurations are different. The element mapping scheme must be under the *ElemTypeConversion block in the ConfigurationFile.txt file. You need to provide both configuration and type information to specify the element mapping scheme as shown for the Abaqus to Nastran direction below:
HM configuration, Abaqus type tria3, S3 tria3, S3R quad4, S4 quad4, S4R quad4, M3D4 tetra4, C3D4 penta6, C3D6 hex8, C3D8 tria6, STRI65 quad8, S8R
HM configuration, Nastran type tria3, CTRIA3 tria3, CTRIAR quad4, CQUAD4 quad4, CQUADR quad4, CSHEAR tetra4, CTETRA penta6, CPENTA hex8, CHEXA tria6, CTRIA6 quad8, CQUAD8
Altair Engineering

tetra10, C3D10 penta15, C3D15 hex20, C3D20 mass, MASS mass, SPRING1 mass, SPRING1 rigid, COUP_KIN rigidlink, COUP_KIN rbe3, DCOUP3D spring, SPRING2 spring, SPRING2 spring, DASHPOT2 spring, DASHPOT2 rod, CONN3D2 bar2, B31 bar2, B31 rod, T3D2 rod, T3D2 gap, GAPUNI rigid, KINCOUP
tetra10, CTETRA penta15, CPENTA hex20, CHEXA mass, CONM2 mass, CELAS1 mass, CELAS2 rigid, RBE2 rigidlink, RBE2 rbe3, RBE3 spring, CELAS1 spring, CELAS2 spring, CDAMP1 spring, CDAMP2 spring, CBUSH bar2, CBEAM bar2, CBAR rod, CROD rod, CONROD gap, CGAP weld, RBAR
You can take advantage of a simplified conversion of Abaqus connectors (CONN3D2) to rbe2 elements when modifying ConfigurationFile.txt in the following way (change the entry for rod element type configuration: rod,CONN3D2 rigid,rbe2 CONN3D2 elements will now be converted to RBE2 elements. Depending on the connection type set in the CONNECTOR SECTION (e.g. AXIAL or HINGE), degrees of freedom will be set for the RBE2 element. If

Altair Engineering
systems are associated to the connector elemental nodes they will be assigned to the nodes of the RBE2 as well. Not all connection types are supported. If a system is ignored by a particular CONNECTOR SECTION, it will not be assigned to the nodes of the RBE2 either. These connector types are currently considered in conversion: AXIAL, JOIN, LINK, SLIDE-PLANE, SLOT, ALIGN, REVOLUTE, BEAM, CYLINDRICAL, HINGE, PLANAR, TRANSLATOR, WELD.
Sectional properties
The table below shows supported sectional property mapping between Abaqus and Nastran. Some of the properties in one solver can be converted to two different sections in the other solver. For an Abaqus to Nastran conversion, for example, *DASHPOT can be converted to *PELAS or PDAMP. The property mapping scheme can be edited under the *PropertyConversion block in the ConfigurationFile.txt file. Please note that the property conversion scheme and corresponding element conversion scheme must be consistent. For example, if you define *CONNECTOR SECTION to PBUSH at the property mapping scheme, the corresponding element CONN3D2 must map to CBUSH in the element mapping scheme. For SOLID SECTION the converter will always convert to PSOLID unless the property has a data line indicating a crossectional area for a truss element. In this case conversion results in a PROD property. For BEAM (GENERAL) SECTION the algorithm decides automatically which property to convert to depending on the element type chosen in the ElementTypeConversion section of the ConfigurationFile.txt. For example, if you want to convert B31 elements to CBAR, that means that the beam property will get converted to a PBAR or PBARL property. If you choose to convert B31 elements to CBEAM, then the converter creates PBEAM or PBEAML properties accordingly. The same logic applies to B32 elements; the difference is that they are changed to first order beam elements first on conversion. Abaqus to Nastran HM configuration, Abaqus type *SOLID SECTION *SHELL SECTION *SHELL GENERAL SECTION *MEMBRANE SECTION *BEAM SECTION *BEAM GENERAL SECTION *CONNECTOR SECTION *MASS *ROTARY INERTIA HM configuration, Nastran type PROD or PSOLID PSHELL PSHELL PSHELL PBEAML or PBARL PBEAM, PBAR, PBEAML or PBARL PELAS or PBUSH CONM2 CONM2
Altair Engineering

*SPRING *DASHPOT *GAP
PELAS PELAS OR PDAMP PGAP
Materials
The table below shows supported material mapping between Abaqus and Nastran. The material mapping scheme can be edited under *PropertyConversion block in the ConfigurationFile.txt file. Abaqus to Nastran HM configuration, Abaqus type *MATERIAL HM configuration, Nastran type MAT1 Note: Density, Young's modulus, Poisson's ratio, thermal expansion coefficient, reference temperature *CONNECTOR BEHAVIOR PBUSH or PELAS
Loads
HM loads have two basic attributes configuration (or config) and type . The supported load "configs" are: force, moment, constraint, pressure, temperature, flux, velocity, acceleration and equation. The load "type" defines the solver specific type of a particular configuration. For example, pressure load can be any of the following Nastran types: PLOAD, PLOAD2 or PLOAD4. The Load Types panel shows all supported load configurations and their types for a user profile. For a specific configuration, you can map any supported Abaqus load type to any supported Nastran load type. The conversion tool does not support conversion across load configurations. The load mapping scheme can be edited under the *BCsTypeConversion block in the ConfigurationFile.txt file. You need to provide both configuration and type information to specify the mapping scheme as shown below:
HM configuration, Abaqus type force, CLOAD moment, CLOAD const, BOUNDARY
HM configuration, Nastran type force, FORCE moment, MOMENT const, SPC

Altair Engineering
const, VELOCITY const, BOUNDARY pressure, DLOAD pressure, DLOAD pressure, DLOAD temp, TEMPERATURE equation, *EQUATION
const, SPCD const, SUPORT pressure, PLOAD pressure, PLOAD2 pressure, PLOAD4 temp, TEMP equation, MPC
Load steps and analysis type

The conversion tool maps between Abaqus steps and Nastran subcases. It does not convert Abaqus analysis type to the solution type. You must define it manually using the Load Step Browser.
See also Abaqus Conversion Tools
Altair Engineering

Abaqus to RADIOSS (Block Format) Conversion

You can use the Conversion tool to convert a Abaqus explicit file to a RADIOSS (BLOCK) file. 1. 2. 3. Load the Abaqus Explicit user profile. Import a Abaqus Explicit model. Run the conversion macro by clicking Tools > Convert > ABAQUS > To RADIOSS (BLOCK). The Conversion tab will appear at the left side the graphics area. 4. 5. 6. In the Source Abaqus template field, set it as Explicit. In the Destination RADIOSS Template field, select the destination solver version. Click Convert to start the conversion. After conversion, the selected version of the RADIOSS (BLOCK) user profile is automatically loaded 7. Review and export the deck using the RADIOSS (BLOCK) user profile.
Some of the keywords in the Abaqus (explicit) deck are converted to the RADIOSS (BLOCK) deck as per the following table:
Element Mapping
HM configuration, Abaqus (Explicit) type HM configuration, RADIOSS (Block Format), type /BRICK /BRICK /BRICK /BRICK /SH3N /SHELL /BRICK /PENTA6 /SH3N + /RBODY /SHELL + /RBODY /ADMAS
C3D10M C3D4 C3D6 C3D8R S3R S4R SC8R SC6R R3D3 R3D4 MASS

Altair Engineering
Property Mapping
HM configuration, Abaqus (Explicit) type HM configuration, RADIOSS (Block Format), type *SOLID_SECTION and *CONTROL_SECTION *SHELL_SECTION and *CONTROL_SECTION *RIGIDBODY *MASS /PROP/SOLID
/PROP/SHELL or PROP/TSHELL
PROP/SHELL or /PROP/SOLID /ADMAS
Material Mapping
HM configuration, Abaqus (Explicit) type HM configuration, RADIOSS (Block Format), type ELASTIC, ISOTROPIC PLASTIC, ISOTROPIC Hyperelastic, Mooney, Rivlin Hyperelastic, Ogden /MAT/ELASTIC /MAT/PLAS_TAB MAT/OGDEN MAT/OGDEN
Function Mapping
HM configuration, Abaqus (Explicit) type HM configuration, RADIOSS (Block Format), type *AMPLITUDE /FUNCT, /MOVE_FUNCT
Group Mapping
HM configuration, Abaqus (Explicit) type HM configuration, RADIOSS (Block Format), type
Altair Engineering

*NSET *ELSET *SURFACE
/GRNOD /GSHEL, /GRSH3N, /GRBRIC /GRNOD, /SURF
Load Mapping
HM configuration, Abaqus (Explicit) type HM configuration, RADIOSS (Block Format), type *BOUNDARY *INITIAL CONDITION *CLOAD *DLOAD /IMPDISP, /IMPVEL, /IMPACC, /BCS /INIVEL /CLOAD /GRAV, /PLOAD
Contact Mapping
HM configuration, Abaqus (Explicit) type HM configuration, RADIOSS (Block Format), type *TIED, *CONTACT_CLEARANCE, *SURFACE_INTERACTION *GENERAL_CONTACT, *CONTACT_CLEARANCE, *SURFACE_INTERACTION /INTER/TYPE2
/INTER/TYPE7
Constraints Mapping
HM configuration, Abaqus (Explicit) type HM configuration, RADIOSS (Block Format), type *COUPLING KINEMATIC, *COUPLING DYNAMIC *MPC BEAM /RBE2, /RBE3 /RBODY

Altair Engineering
Altair Engineering

Abaqus to RADIOSS (Bulk Data Format), OptiStruct Conversion

The Abaqus to RADIOSS (Bulk Data Format), OptiStruct conversion tool uses an open conversion scheme; you can specify different mappings in the configuration file. Care has to be taken so that the element and property mappings are consistent. A valid mapping scheme is provided in the ConfigurationFile.txt. This document explains the scope and limitations of the mapping scheme.
Elements
HM elements have two basic attributes configuration (or config) and type . The "config" defines the basic geometrical shape of an element. For example, tria3 configuration is a 3 node triangular element and hexa8 is an 8-node hexahedral element. The "type" defines the solver specific element type of a particular configuration. For example, the 4-node quadrilateral (quad4) element in Abaqus can be any of the following types: S4, S4R, M3D4, R3D4 etc. The Element Types panel shows all supported element configurations and their types for a user profile. For a specific configuration, you can map any supported RADIOSS (Bulk Data Format), OptiStruct element type to any supported Abaqus element type, or vice versa. For example, for a RADIOSS (Bulk Data Format), OptiStruct to Abaqus direction, several 2-noded element configurations such as spring, rigid, bar2, rid, etc., are supported. Because all of them are 2-noded elements, conversion across these configurations is also allowed for some element types. For example, CBUSH is of "spring" configuration in the RADIOSS (Bulk Data Format), OptiStruct user profile and CONN3D2 is of rod" configuration in the Abaqus user profile. It is possible to map a CBUSH to CONN3D2 even though their configurations are different. The element mapping scheme must be under the *ElemTypeConversion block in the ConfigurationFile.txt file. You need to provide both configuration and type information to specify the element mapping scheme as shown for the RADIOSS (Bulk Data Format), OptiStruct to Abaqus direction below: HM configuration, Abaqus type tria3, S3 tria3, S3R quad4, S4 quad4, S4R quad4, M3D4 tetra4, C3D4 penta6, C3D6 hex8, C3D8 tria6, STRI65 quad8, S8R HM configuration, RADIOSS (Bulk Data Format), OptiStruct type tria3, CTRIA3 tria3, CTRIAR quad4, CQUAD4 quad4, CQUADR quad4, CSHEAR tetra4, CTETRA penta6, CPENTA hex8, CHEXA tria6, CTRIA6 quad8, CQUAD8

Altair Engineering
You can take advantage of a simplified conversion of Abaqus connectors (CONN3D2) to rbe2 elements when modifying ConfigurationFile.txt in the following way (change the entry for rod element type configuration: rod,CONN3D2 rigid,rbe2 CONN3D2 elements will now be converted to RBE2 elements. Depending on the connection type set in the CONNECTOR SECTION (e.g. AXIAL or HINGE), degrees of freedom will be set for the RBE2 element. If systems are associated to the connector elemental nodes they will be assigned to the nodes of the RBE2 as
Altair Engineering

well. Not all connection types are supported. If a system is ignored by a particular CONNECTOR SECTION, it will not be assigned to the nodes of the RBE2 either. These connector types are currently considered in conversion: AXIAL, JOIN, LINK, SLIDE-PLANE, SLOT, ALIGN, REVOLUTE, BEAM, CYLINDRICAL, HINGE, PLANAR, TRANSLATOR, WELD.
The table below shows supported sectional property mapping between Abaqus and RADIOSS (Bulk Data Format), OptiStruct. Some of the properties in one solver can be converted to two different Abaqus sections in the other solver. For an Abaqus to RADIOSS (Bulk Data Format), OptiStruct conversion, for example, *DASHPOT can be converted to PELAS or PDAMP. The property mapping scheme can be edited under the *PropertyConversion block in the ConfigurationFile.txt file. Please not that the property conversion scheme and corresponding element conversion scheme must be consistent. For example, if you define *CONNECTOR SECTION to PBUSH at the property mapping scheme, the corresponding element CONN3D2 must map to CBUSH in the element mapping scheme. For SOLID SECTION the converter will always convert to PSOLID unless the property has a data line indicating a cross-sectional area for a truss element. In this case conversion results in a PROD property. For BEAM (GENERAL) SECTION the algorithm decides automatically which property to convert to depending on the element type chosen in the ElementTypeConversion section of the ConfigurationFile.txt. For example, if you want to convert B31 elements to CBAR, that means that the beam property will get converted to a PBAR or PBARL property. If you choose to convert B31 elements to CBEAM, then the converter creates PBEAM or PBEAML properties accordingly. The same logic applies to B32 elements; the difference is that they are changed to first order beam elements first on conversion. Composite sections SHELL and SHELL GENERAL SECTION can be converted to Radioss(Bulk)/Nastran. Depending on the setting in ConfigurationFile.txt they will be converted to PCOMP or PCOMPG. Besides individual layers, the conversion takes care of system assignments, offsets, symmetric and other parameters simplifying the sections, such as e.g. BENDING ONLY. If sections are converted to PCOMPG, a global ply ID (GPLYID) is assigned depending on the name used in the Abaqus section. Abaqus to RADIOSS (Bulk Data Format), OptiStruct HM configuration, RADIOSS (Bulk Data Format), OptiStruct type PROD or PSOLID PSHELL PCOMP or PCOMPG PSHELL
HM configuration, Abaqus type *SOLID SECTION *SHELL SECTION *SHELL SECTION, COMPOSITE *SHELL GENERAL SECTION
*SHELL GENERAL SECTION, COMPOSITE PCOMP of PCOMPG *MEMBRANE SECTION PSHELL

Altair Engineering
*BEAM SECTION *BEAM GENERAL SECTION *CONNECTOR SECTION MASS *ROTARY INERTIA *SPRING *DASHPOT *GAP
PBEAML or PBARL PBEAM, PBAR, PBEAML or PBARL PELAS or PBUSH CONM2 CONM2 PELAS2 PELAS2 or PDAMP PGAP
Materials
The table below shows supported material mapping between Abaqus and RADIOSS (Bulk Data Format), OptiStruct. The material mapping scheme can be edited under *PropertyConversion block in the ConfigurationFile.txt file. Abaqus to RADIOSS (Bulk Data Format), OptiStruct HM configuration, Abaqus type HM configuration, RADIOSS (Bulk Data Format), OptiStruct type MAT1 Note: Density, Young's modulus, Poisson's ratio, thermal expansion coefficient, reference temperature *CONNECTOR BEHAVIOR PBUSH or PELAS
*MATERIAL
Loads
HM loads have two basic attributes configuration (or config) and type . The supported load "configs" are: force, moment, constraint, pressure, temperature, flux, velocity, acceleration and equation. The load "type" defines the solver specific type of a particular configuration. For example, pressure load can be any of the following RADIOSS (Bulk Data Format) types: PLOAD, PLOAD2, or PLOAD4. The Load Types panel shows all supported load configurations in HyperMesh and their types for a user profile. For a specific configuration, you can map any supported Abaqus load type to any supported RADIOSS (Bulk Data Format), OptiStruct load type. The conversion tool does not support conversion across load configurations. The load mapping scheme can bed edited under the *BCsTypeConversion block in the
Altair Engineering

ConfigurationFile.txt file. You need to provide both configuration and type information to specify the mapping scheme as shown below: HM configuration, RADIOSS (Bulk Data Format), OptiStruct type force, FORCE moment, MOMENT const, SPC const, SPCD const, SUPORT pressure, PLOAD pressure, PLOAD2 pressure, PLOAD4 temp, TEMP equation, MPC
HM configuration, Abaqus type force, CLOAD moment, CLOAD const, BOUNDARY const, VELOCITY const, BOUNDARY pressure, DLOAD pressure, DLOAD pressure, DLOAD temp, TEMPERATURE equation, *EQUATION

The conversion tool maps between Abaqus steps and RADIOSS (Bulk Data Format), OptiStruct subcases. It does not convert Abaqus analysis type to the solution type. You must define it manually using the RADIOSS (Bulk Data Format), OptiStruct Load Step Browser.

Altair Engineering
ANSYS Conversion Tools

The following conversions are possible when in the ANSYS user profile:
ANSYS to Nastran Conversion ANSYS to RADIOSS (Bulk Data Format) Conversion ANSYS to Abaqus Conversion
Altair Engineering

ANSYS to Abaqus Conversion

You can use the Conversion tool to convert an ANSYS file to an Abaqus file. 1. 2. 3. Load the ANSYS user profile. Import an ANSYS model. Run the Conversion macro by clicking Tools > Convert > ANSYS > To Abaqus. The Conversion tab will appear at the left side the graphics area. 4. Click convert and conversion starts. After conversion, the Abaqus user profile is automatically loaded. 5. Review and export the deck in an Abaqus deck.
Some of the keywords in the ANSY deck are converted to the Abaqus deck as per the following tables.
Materials:
Modulus of Elasticity, Poisson's ratio and density are mapped.
Elements:
ANSYS type MASS21 COMBI14 BEAM4 LINK8 SHELL43, SHELL63, SHELL181 SHELL43, SHELL63, SHELL181 SHELL93 SHELL93 SOLID45, SOLID62, SOLID64, SOLID69, SOLID70, SOLID96, SOLID97, SOLID164, SOLID185 Abaqus type MASS SPRING2 B31 T3D2 S3 HM Configuration Mass Spring Bar2 Rod Tria3
S4
Quad4
STRI65 S8R C3D4
Tria6 Quad8 Tetra4

Altair Engineering
SOLID62, SOLID70, SOLID96, SOLID97, SOLID164 SOLID5, SOLID45, SOLID62, SOLID64, SOLID69, SOLID70, SOLID96, SOLID97, SOLID164, SOLID185 SOLID5, SOLID45, SOLID62, SOLID64, SOLID69, SOLID70, SOLID96, SOLID97, SOLID164, SOLID185 SOLID87, SOLID90, SOLID92, SOLID95, SOLID98, SOLID117, SOLID148, SOLID168, SOLID186, SOLID187, SOLID191 SOLID90, SOLID95, SOLID117, SOLID186 SOLID90, SOLID95, SOLID117, SOLID147, SOLID186, SOLID191 SOLID90, SOLID95, SOLID117, SOLID147, SOLID186, SOLID191
C3D8
Pyramid5
C3D6
Penta6
C3D81
Hex8
C3D10
Tetra10
C3D20
Pyramid13
C3D15
Penta15
C3D20
Hex20
Properties
ANSYS type MASS21p COMBI14p BEAM4p, LINK8p SHELL43p, SHELL63p, SHELL93p Abaqus type MASS SPRING BEAMSECTION SHELLSECTION Convert Parameters none none none Shell Thickness
Altair Engineering

SOLID45p, SOLID70p, SOLID95p, SOLID117p, SOLID191p Notes:
SOLIDSECTION
none
If ANSYS solid elements do not have a property, then one SOLIDSECTION property will be created by using this conversion tool. Loads and Boundary conditions: Loads and boundary conditions will not be converted on using this conversion tool.
See also Ansys Conversion Tools

Altair Engineering
ANSYS to Nastran Conversion

You can use the Conversion tool to convert an ANSYS file to a Nastran file. 1. 2. 3. Load the ANSYS user profile. Import an ANSYS model. Run the Conversion macro by clicking Tools > Convert > ANSYS > To Nastran. The Conversion tab will appear at the left side the graphics area. 4. Click convert and conversion starts. After conversion, the Nastran user profile is automatically loaded. 5. Review and export the deck in Nastran deck.
Conversion Notes:
All ANSYS solid and shell elements that are currently supported are included in the conversion tool. Material properties Thermal Conductivity, specific heat, thermal expansion co-efficient can be now converted. Temperature dependant isometric material properties can now be converted using the conversion tool. Orthotropic properties of E, NU and K can be converted. COMBIN14 elements are now converted to CELAS1 if key option2 for COMBIN14 in ANSYS is defined. ANSYS BEAM188 converts to CBEAM now [please note section properties defined using SECDATA card in ANSYS are not yet converted]. Forces, Moments, Pressures, Temperatures and Constraints are automatically converted. MODOPT (control cards) will be mapped to EIRGL. ACEL (Control Cards) will be converted to GRAV. Assumptions: The macro will convert only entities imported by the ANSYS FE input reader. For shell elements, constant thickness parts are assumed. Analysis types assumed: Static gravity, forces, pressures and constraints, Modal.
Conversion Mapping:
ANSYS Type Shell43, Shell93 Beam4 Nastran Type CTRIA3, CQUAD4 CBEAM
Altair Engineering

Mass21 Combin14 Pipe16 Shell181 Shell63 Link8 Solid 92 Solid45 Beam44 Rbe3 CE -> CERIG CP Solid95 MODOPT ACEL BEAM188
CONM2 CBUSH (damping will be ignored) CBEAM CTRIA3, CQUAD4 CTRIA3, CQUAD4 CROD CTETRA CTETRA, CPENTA, CHEXA CBEAM RBE3 MPC MPC CPENTA, CHEXA EIGRL GRAV CBEAM
Note: If components or properties do not have a material associated to them, on conversion MID = 1 will be associated On conversion, model will be cleaned by removing unused sets, ET types and contact elements

Altair Engineering
ANSYS to RADIOSS (Bulk Data Format) Conversion

You can use the Conversion tool to convert an ANSYS file to a RADIOSS (Bulk Data Format) file. 1. 2. 3. Load the ANSYS user profile. Import an ANSYS model. Run the Conversion macro by clicking Tools > Convert > ANSYS > To Radioss (Bulk data format). The Conversion tab will appear at the left side the graphics area. Click convert and conversion starts. After conversion, the OptiStruct user profile is automatically loaded. 4. Review and export the deck in OptiStruct deck.
Conversion Notes:
All ANSYS solid and shell elements that are currently supported are included in the conversion tool. Material properties Thermal Conductivity, specific heat, thermal expansion co-efficient can be now converted. Temperature dependant isometric material properties can now be converted using the conversion tool. Orthotropic properties of E, NU and K can be converted. COMBIN14 elements are now converted to CELAS1 if key option2 for COMBIN14 in ANSYS is defined. ANSYS BEAM188 converts to CBEAM now [please note section properties defined using SECDATA card in ANSYS are not yet converted]. Forces, Moments, Pressures, Temperatures and Constraints are automatically converted. MODOPT (control cards) will be mapped to EIRGL. ACEL (Control Cards) will be converted to GRAV.
Assumptions: The macro will convert only entities imported by the ANSYS FE input reader. For shell elements, constant thickness parts are assumed. Analysis types assumed: Static gravity, forces, pressures and constraints, Modal.
Conversion Mapping:
ANSYS Type Shell43, Shell98 Beam4 OptiStruct Type CTRIA3, CQUAD4 CBEAM
Altair Engineering

Mass21 Combin14 Pipe16 Shell181 Shell63 Link8 Solid92 Solid45 Beam44 Rbe3 CE -> CERIG CP Solid95 MODOPT ACEL
CONM2 CBUSH (damping will be ignored) CBEAM CTRIA3, CQUAD4 CTRIA3, CQUAD4 CROD CTETRA CTETRA, CPENTA, CHEXA CBEAM RBE3 MPC MPC CPENTA, CHEXA EIGRL GRAV

Altair Engineering
LS-DYNA Conversion Tools

The following conversions are possible when in the LS-DYNA user profile:
LS-DYNA to Nastran Conversion LS-DYNA to RADIOSS (Block Format) Conversion LS-DYNA to RADIOSS (Bulk Data Format) Conversion
Altair Engineering

LS-DYNA to Nastran Conversion

You can use the Conversion tool to convert an LS-DYNA file to a Nastran file. 1. 2. 3. Load the LS-DYNA user profile. Import a LS-DYNA model. Run the conversion macro by clicking Tools > Convert > LS-DYNA > To NASTRAN. The Conversion tab will appear at the left side the graphics area. 4. 5. In the Destination NASTRAN Template field, select the destination solver version. Click Convert to start the conversion. After conversion, the Nastran user profile is automatically loaded. 6. Review and export the deck using the Nastran user profile.
Some of the keywords in the LS-DYNA deck are converted to the Nastran deck as per the following table:
Element Mapping
LSDYNA type *ELEMENT_MASS *ELEMENT_BEAM *ELEMENT_SHELL *ELEMENT_SOLID *CONSTRAINED_SPOTWELD *ELEMENT_PLOTEL *CONSTRAINED_INTERPOLATION *CONSTRAINED_NODE_SET *ELEMENT_DISCRETE NASTRAN type CONM2 CBAR CTRIA3,CQUAD4, CQUAD8, CTRIA6 CTETRA4/CHEXA8/CPENTA6 RBAR PLOTEL RBE3 RBE2 CELAS1
Property Mapping
LSDYNA type NASTRAN type

Altair Engineering
*SECTION_SOLID *SECTION_SHELL
PSOLID PSHELL
Material Mapping
All the LSDYNA materials are mapped MAT1 in NASTRAN
Boundary conditions Mapping

LSDYNA type *BOUNDARY_SPC *LOAD_NODE_POINT *LOAD_SEGMENT *INITIAL_TEMP Nastran type SPC FORCE, MOMENT PLOAD4 TEMP
Coordinate system Mapping

LSDYNA type *DEFINE_COORDINATE_NODE *DEFINE_COORDINATE_SYSTEM Nastran type CORD1R CORD2R
See also LS-DYNA Conversion Tools
Altair Engineering

LS-DYNA to RADIOSS (Block Format) Conversion

You can use the Conversion tool to convert an LS-DYNA file to a RADIOSS (Block Format) file. 1. 2. 3. Load the LS-DYNA user profile. Import an LS-DYNA model. Run the conversion macro by clicking Tools > Convert > LsDyna > To RADIOSS (Block format). The Conversion tab will appear at the left side the graphics area. 4. Click Convert. After conversion, the RADIOSS (Block Format) user profile is automatically loaded. 5. Review and export the deck in the RADIOSS (Block Format) user profile.
Some of the keywords in the LS-DYNA deck are converted to the RADIOSS deck as per the following tables:
Element Mapping
HM configuration, LS-DYNA type *ELEMENT_SHELL *ELEMENT_SOLID *ELEMENT_MASS *ELEMENT_BEAM *ELEMENT_DISCRETE *ELEMENT_SEATBELT_ACCELEROMETER HM configuration, RADIOSS (Block Format) type SHELL, SH3N BRICK, TETRA44 ADMAS BEAM SPRING2N ACCEL
Load Mapping
HM configuration, LS-DYNA 2G type *BOUNDARY_SPC_NODE/SET *LOAD_NODE_POINT/SET *INITIAL_VELOCITY_NODE/GENERATION/ RIGID BODY HM configuration, RADIOSS (Block Format) type BCS CLOAD
INIVEL

Altair Engineering
System Mapping
HM configuration, LS-DYNA type *DEFINE_COORDINATE_NODES *DEFINE_COORDINATE_SYSTEM HM configuration, RADIOSS (Block Format) type SKEW/MOVE/ SKEW/FIXED
Material Mapping
HM configuration, LS-DYNA type *MAT_ELASTIC *MAT_PLASTIC_KINEMATIC *MAT_NULL HM configuration, RADIOSS (Block Format) type M1_ELASTIC M36_PLASTIC_TAB M0_VOID M1_ELASTIC (nodes of material defined as /RBODY) M36_PLAS_TAB M2_PLAS_JOHNS_ZERIL
*MAT_RIGID *MAT_PIECEWISE_LINEAR_PLASTICITY *MAT_SIMPLIFIED_JOHNSON_COOK
Properties Mapping
HM configuration, LS-DYNA type *SECTION_BEAM *SECTION_DISCRETE *SECTION_SHELL *SECTION_SOLID HM configuration, RADIOSS (Block Format) type P3_BEAM P4_SPRING P1_SHELL P14_SOLID
Altair Engineering

Curve Mapping
HM configuration, LS-DYNA type *DEFINE_CURVE HM configuration, RADIOSS (Block Format) type FUNCT
Control Cards Mapping

HM configuration, LS-DYNA type *CONTROL_ADAPTIVE HM configuration, RADIOSS (Block Format) type ADMESH_GLOBAL, ADMESH_SET
Component Mapping
HM configuration, LS-DYNA type *DAMPING_PARTS_OPTIONS *PART_OPTIONS *INCLUDE_STAMPED_PART HM configuration, RADIOSS (Block Format) type PART PART PART
Contact Interface Mapping

HM configuration, LS-DYNA type *CONTACT_AUTOMATIC_GENERAL HM configuration, RADIOSS (Block Format) type INTER/TYPE7
*CONTACT_AUTOMATIC_GENERAL_INTERIOR INTER/TYPE7 *CONTACT_AUTOMATIC_NODES_TO_SURFA CE
INTER/TYPE7
*CONTACT_AUTOMATIC_ONE_WAY_SURFAC E_TO_SURFACE INTER/TYPE7 *CONTACT_AUTOMATIC_SINGLE_SURFACE INTER/TYPE7

Altair Engineering
*CONTACT_AUTOMATIC_SURFACE_TO_SURF ACE INTER/TYPE7
Rigid Wall Mapping

HM configuration, LS-DYNA type *RIGIDWALL_GEOMETRIC_FLAT_OPTIONS *RIGIDWALL_PLANAR_OPTIONS HM configuration, RADIOSS (Block Format) type RWALL RWALL
Time History Definition Mapping

HM configuration, LS-DYNA type *DATABASE_HISTORY_BEAM *DATABASE_HISTORY_NODE *DATABASE_HISTORY_SHELL *DATABASE_HISTORY_SOLID *DATABASE_HISTORY_TSHELL HM configuration, RADIOSS (Block Format) type TH/BEAM TH/NODE TH/SHEL TH/BRIC TH/THSH
The attributes converted in each KEYWORD is explained in the Conversion dialog (see below). Each keyword is associated with a color to distinguish it better. GREEN All the attributes of the KEYWORD are converted to equivalent in RADIOSS ORANGE Only some the attributes of the KEYWORD are converted to equivalent in RADIOSS RED None the attributes of the KEYWORD are converted to equivalent in RADIOSS. Basically conversion of this keyword is not supported by the conversion tool
Altair Engineering


Altair Engineering
Altair Engineering

LS-DYNA to RADIOSS (Bulk Data Format) Conversion

You can use the Conversion tool to convert an LS-DYNA file to a Nastran file. 1. 2. 3. Load the LS-DYNA user profile. Import a LS-DYNA model. Run the conversion macro by clicking Tools > Convert > LS-DYNA > To RADIOSS BULK. The Conversion tab will appear at the left side the graphics area. 4. 5. In the Destination RADIOSS BULK Template field, select the destination solver version. Click Convert to start the conversion. After conversion, the Nastran user profile is automatically loaded. 6. Review and export the deck using the Nastran user profile.
Some of the keywords in the LS-DYNA deck are converted to the Nastran deck as per the following table:
Element Mapping
LSDYNA type *ELEMENT_MASS *ELEMENT_BEAM *ELEMENT_SHELL *ELEMENT_SOLID *CONSTRAINED_SPOTWELD *ELEMENT_PLOTEL *CONSTRAINED_INTERPOLATION *CONSTRAINED_NODE_SET *ELEMENT_DISCRETE RADIOSS BULK type CONM2 CBAR CTRIA3,CQUAD4, CQUAD8, CTRIA6 CTETRA4/CHEXA8/CPENTA6 RBAR PLOTEL RBE3 RBE2 CELAS1
Property Mapping
LSDYNA type RADIOSS BULK type

Altair Engineering
*SECTION_SOLID *SECTION_SHELL
PSOLID PSHELL
Material Mapping
All the LSDYNA materials are mapped MAT1 in NASTRAN
Boundary conditions Mapping

LSDYNA type *BOUNDARY_SPC *LOAD_NODE_POINT *LOAD_SEGMENT *INITIAL_TEMP RADIOSS BULK type SPC FORCE, MOMENT PLOAD4 TEMP
Coordinate system Mapping

LSDYNA type *DEFINE_COORDINATE_NODE *DEFINE_COORDINATE_ SYSTEM RADIOSS BULK type CORD1R
CORD2R
Altair Engineering

Nastran Conversion Tools

The following conversions are possible when in the NASTRAN user profile:
Nastran to LS-DYNA Conversion Nastran to RADIOSS (Block Format) Conversion Nastran to Abaqus Mapping Nastran to ANSYS Conversion

Altair Engineering
Nastran to Abaqus Conversion

The Nastran To Abaqus tool uses an open conversion scheme; you can specify different mappings in the configuration file. Care has to be taken so that the element and property mappings are consistent. We provided a valid mapping scheme in the ConfigurationFile.txt. This document explains the scope and limitations of the mapping scheme.
Elements
HM elements have two basic attributes configuration (or config) and type . The "config" defines the basic geometrical shape of an element. For example, tria3 configuration is a 3 node triangular element and hexa8 is an 8-node hexahedral element. The "type" defines the solver specific element type of a particular configuration. For example, the 4-node quadrilateral (quad4) element in Abaqus can be any of the following types: S4, S4R, M3D4, R3D4 etc. The Elem Types panel shows all supported element config and their types for a user profile. For a specific configuration, you can map any supported Nastran element type to any supported Abaqus element type. Several 2-noded element configurations such as spring, rigid, bar2, rid, etc., are supported. Because all of them are 2-noded elements, conversion across these configurations is also allowed for some element types. For example, CBUSH is of "spring" config in the Nastran user profile and CONN3D2 is of rod" config in the Abaqus user profile. It is possible to map a CBUSH to CONN3D2 even though their configs are different. The element mapping scheme must be under the *ElemTypeConversion block in the ConfigurationFile.txt file. You need to provide both config and type information to specify the element mapping scheme as shown below:
HM configuration, Nastran type tria3, CTRIA3 tria3, CTRIAR quad4, CQUAD4 quad4, CQUADR quad4, CSHEAR tetra4, CTETRA penta6, CPENTA hex8, CHEXA tria6, CTRIA6 quad8, CQUAD8
HM configuration, Abaqus type tria3, S3 tria3, S3R quad4, S4 quad4, S4R quad4, M3D4 tetra4, C3D4 penta6, C3D6 hex8, C3D8 tria6, STRI65 quad8, S8R
Altair Engineering

Notes: The CELAS1 or CELAS2 elements in Nastran have both spring stiffness and damping attributes. If both spring and damping values are present and the mapping scheme is CELAS1 to SPRING1, the conversion tool will automatically create an extra DASHPOT element.

Altair Engineering
Similarly, the CONM2 elements in Nastran have both translational and rotational mass values. If both translational and rotational values are present and the mapping scheme is CONM2 to MASS, the conversion tool will automatically create an extra ROTARY1 element.
The table below shows supported sectional property mapping between Nastran and Abaqus. Some of the properties in one solver can be converted to two different Abaqus sections in the other solver. For a Nastran to Abaqus conversion, for example, PSHELL can be converted to *SHELL SECTION or *SHELL GENERAL SECTION. In the mapping scheme, you must select one of them. The property mapping scheme must be under the *PropertyConversion block in the ConfigurationFile.txt file. Abaqus beam section axes are defined at element level in Nastran. They are in the sectional property level in Abaqus unless the beam axis is defined by a third node in element connectivity. This means that several elements with different beam axis direction can point to the same PBEAM, PBEAML, PBAR or PBARL property in Nastran. But in Abaqus, all elements under a *BEAM SECTION or *BEAM GENERAL SECTION property have one beam axis orientation. If a third node is used to define the beam axis, even Abaqus beams with a different axis can belong to a single *BEAM SECTION property. The conversion tool allows you to select an extra (1 or 0) argument to define the beam axis conversion mechanism. If the argument is 0 (or not defined), the conversion tool will take the beam axis direction of the first element corresponding to a PBEAM, PBEAML, PBAR or PBARL property and map that to the corresponding *BEAM SECTION or *BEAM GENERAL SECTION card. The beam axis vectors of other elements with the same property will be ignored. If the argument is 1, the conversion tool will create a third node for each element to define the equivalent beam axis vector. As a result, the axis direction for each element will be maintained after the conversion. Because this option updates each element, the conversion process might take a considerable amount of time for models with a large number of beams. The system for CELAS1 or CELAS2 elements is sitting on the grid nodes. Thus, every element can have a different system. Ideally, on conversion one *SPRING (and *DASHPOT) or *CONNECTOR SECTION per element needs to be created. For large models this can be time-consuming. Therefore for CELAS1 two options can be set in the ConfigurationFile.txt (1 or 0). If the option is 1, one property per element will be created (default). If the flag is set to 0, one property per PELAS card will be created. In this case, the settings of the first element found on this property will be translated. From CELAS2 elements you always create a *SPRING and *DASHPOT or *CONNECTOR SECTION property per element.
Nastran PSOLID PSHELL PBEAM PBEAML
Abaqus *SOLID SECTION *SHELL SECTION or *SHELL GENERAL SECTION *BEAM GENERAL SECTION *BEAM SECTION
Beam axis option
1 or 0 1 or 0
Altair Engineering

PBAR PBARL PROD PBUSH PELAS PDAMP CELAS2 CDAMP2 CONM2
*BEAM GENERAL SECTION *BEAM SECTION *SOLID SECTION *CONNECTOR SECTION (*SPRING + *DASHPOT) or *CONNECTOR SECTION *DASHPOT or *CONNECTOR SECTION (*SPRING + *DASHPOT) or *CONNECTOR SECTION *DASHPOT or *CONNECTOR SECTION (*MASS +*ROTARY INERTIA)
1 or 0 1 or 0
1 or 0
Notes: CELAS2, CDAMP2 and CONM2 are elements in Nastran, but they are sectional properties in Abaqus. Therefore, the mapping for them must also be defined under *PropertyConversion. The PELAS or CELAS2 in Nastran have both spring stiffness and damping attributes. If both spring and damping values are present and they are mapped to *SPRING, the conversion tool will automatically create an extra *DASHPOT property. The elements will both be kept in the same component and the property will be directly assigned to the *SPRING or *DASHPOT element. Similarly, the CONM2 in Nastran has both translational and rotational mass values. If both translational and rotational values are present and it is mapped to *MASS, the conversion tool will automatically create an extra *ROTARY INERTIA component. The property conversion scheme and corresponding element conversion scheme must be consistent. For example, if you define PBUSH to *CONNECTOR SECTION at the property mapping scheme, the corresponding element CBUSH must map to CONN3D2 in the element mapping scheme.
Materials
The table below shows supported material mapping between Nastran and Abaqus. The material mapping scheme must be defined under *PropertyConversion block in the ConfigurationFile.txt file. Nastran MAT1 Abaqus *MATERIAL *ELASTIC, TYPE=ISO; *EXPANSION, TYPE=ISO; and *DENSITY (G is used only for *BEAM GENERAL SECTION)

Altair Engineering
MAT2
*MATERIAL
When used alone in a PSHELL, MAT2 is translated to *ELASTIC, TYPE=LAMINA or *ELASTIC, TYPE=ANISOTROPIC ELASTIC, TYPE=LAMINA; *EXPANSION, TYPE=ORTHO; and *DENSITY *ELASTIC, TYPE=ANISOTROPIC unless the data are found to be orthotropic, in which case the data are analyzed to create *ELASTIC, TYPE=ENGINEERING CONSTANTS. Also *DENSITY; and *EXPANSION, TYPE=ANISO or ORTHO.
MAT8
*MATERIAL
MAT9
*MATERIAL
Note :
If a PBEAM or PBAR is mapped to a *BEAM GENERAL SECTION, the material properties defined in the corresponding Nastran material are mapped to the *BEAM GENERAL SECTION card. No *Material is created in this case.
Loads
HM loads have two basic attributes configuration (or config) and type . The supported load "configs" are: force, moment, constraint, pressure, temperature, flux, velocity, acceleration and equation. The load "type" defines the solver specific type of a particular configuration. For example, pressure load can be any of the following Abaqus types: DLOAD, FILM, DFLUX etc. The Load Types panel shows all supported load configurations and their types for a user profile. For a specific configuration, you can map any supported Nastran load type to any supported Abaqus load type. The conversion tool does not support conversion across load configurations. The load mapping scheme is valid for either direction and must be under the *BCsTypeConversion block in the ConfigurationFile. txt file. You need to provide both configuration and type information to specify the mapping scheme as shown below: HM configuration, Nastran type force, FORCE moment, MOMENT const, SPC const, SPCD const, SUPORT pressure, PLOAD HM configuration, Abaqus type force, CLOAD moment, CLOAD const, BOUNDARY const, VELOCITY const, BOUNDARY pressure, DLOAD
Altair Engineering

pressure, PLOAD2 pressure, PLOAD4 temp, TEMP equation, MPC
pressure, DLOAD pressure, DLOAD temp, TEMPERATURE equation, *EQUATION
In addition to the above load types, the conversion tool also converts Nastran Dload (with corresponding Rload1, Rload2, DAREA, TABLED1, TABLED2, TABLED3) to Abaqus *BOUNDARY or *CLOAD (with corresponding *AMPLITUDE curve). No mapping scheme needs to be specified for this conversion; the conversion is done automatically if present in the model.

The conversion tool maps between Nastran subcases and Abaqus steps. It does not convert the solution types to/from any Abaqus analysis type. You must define them manually using the Abaqus Step Manager or the Load Step Browser.
Systems and mass

The conversion tool converts Nastran system types into the corresponding Abaqus system (*SYSTEM, *TRANSFORM or *ORIENTATION). It also converts the NSM into *NONSTRUCTURAL MASS and assigns them to the relevant properties. The mapping can be summarized as: Nastran NSM NSM1 NSML NSML1 NSMADD GRID CORD1R CORD1C CORD1S *NODE and *SYSTEM *SYSTEM for nodes *TRANSFORM if referred to on GRID *ORIENTATION for elements Abaqus *NONSTRUCTURAL MASS

Altair Engineering
CORD2R CORD2C CORD2S
WTMASS
If the WTMASS parameter is defined in the Nastran model, it is used to modify density, mass, and inertia values during conversion.
See also Nastran Conversion Tools
Altair Engineering

Nastran to ANSYS Conversion

You can use the Conversion tool to convert a Nastran file to an ANSYS file. 1. 2. 3. Load the Nastran user profile. Import a Nastran model. Run the conversion macro by clicking Tools > Convert > NASTRAN > To ANSYS. The Conversion tab will appear at the left side the graphics area. 4. Click Convert to start the conversion. After conversion, the ANSYS user profile is automatically loaded. 5. Review and export the deck using the ANSYS user profile.
Some of the keywords in the Nastran deck are converted to the ANSYS deck as per the following tables.
Materials
Nastran type MAT1 ANSYS type MATERIAL Convert Parameters Modulus of Elasticity, poisson's ratio and density density density
MAT2 MAT4
MATERIAL MATERIAL
Elements
Nastran type CONM2 CELAS1 CBAR, CBEAM CROD CTRIA3, CTRIAR CQUAD4, CQUADR, CSHEAR ANSYS type MASS21 COMBI14 BEAM44 LINK8 SHELL63 SHELL63 HM Configuration Mass Spring Bar2 Rod Tria3 Quad4

Altair Engineering
CTRIA6 CQUAD8 CTETRA CTETRA CHEXA CHEXA CPENTA CPENTA
SHELL93 SHELL93 SOLID45 SOLID95 SOLID45 SOLID95 SOLID45 SOLID95
Tria6 Quad8 Tetra4 Tetra10 Hex8 Hex20 Penta6 Penta15
Properties
Nastran type PBAR, PBARL, PBEAM, PBEAML PROD ANSYS type BEAM44p Convert Parameters none
LINK8p
none Shell Thickness
PSHELL, PSHEAR (tria3, SHELL63p quad4) PSHELL, PSHEAR (tria6, SHELL93p quad8) PSOLID (tetra4, penta6, hex8) PSOLID (tetra10, penta15, hex20) SOLID45p
Shell Thickness
none
SOLID95p
none
ETType of Ansys: If the model contains Nastran elements which were mapped to MASS21, LINK8, COMBI14, BEAM44, SHELL63, SHELL93, SOLID45 and SOLID95 elements, respective ETTYPES will be created and assigned to the component. Key options of ETTYPE will not be updated. Components:
Altair Engineering

If the component collector contains different type of configuration of elements, new components will be created for the respective configurations and those elements will be moved into the new component. ETTYPE, material and realset IDs will be assigned to the new component. Loads and Boundary Conditions: Loads and boundary conditions will not be converted by using this conversion tool.

Altair Engineering
Nastran to LS-DYNA Conversion

You can use the Conversion tool to convert a Nastran file to a LS-DYNA file. 1. 2. 3. Load the Nastran user profile. Import a Nastran model. Run the conversion macro by clicking Tools > Convert > NASTRAN >To LS-DYNA. The Conversion tab will appear at the left side the graphics area. 4. Click Convert to start the conversion. After conversion, the selected version of the LS-DYNA user profile is automatically loaded. 5. Review and export the deck using the LS-DYNA user profile.
Some of the keywords in the Nastran deck are converted to the LS-DYNA deck as per the following table:
Element Mapping
Nastran type CONM2 LS-DYNA type *ELEMENT_MASS Meshless weld CWELD CELAS1/CELAS2/CBUSH CDAMP1/CDAMP2/CBUSH1D (0 length) PLOTEL RBAR/RBE2/RJOINT RBE3 CBAR/CBEAM/CROD/CTUBE CONROD CTRIA3/CTRIAR CQUAD4, CQUADR, CSHEAR CQUAD8, CTRIA6 (Change to 1st order then convert) *ELEMENT_PLOTEL *CONSTRAINED_NODAL_RIGID_BODY *CONSTRAINED_INTERPOLATION *ELEMENT_BEAM *ELEMENT_BEAM and *SECTION_BEAM *ELEMENT_SHELL (feabsorb, fe realize using HEXA) *ELEMENT_DISCRETE (card edit for ground option check box)
Altair Engineering

CTETRA4/CHEXA8/CPENTA6 CTETRA10/CHEXA20/CPENTA15 (Change to 1st order then convert)
*ELEMENT_SOLID
Property Mapping
Nastran type PBAR/PBEAM/PROD (Only single section PBEAM is supported) PBARL/PBEAML (ROD, TUBE, BAR) PDAMP/PELAS PSHELL/PSHEAR PSOLID *SECTION_DESCRETE *SECTION_SHELL *SECTION_SOLID *PART_COMPOSITE +*ELEMENT_SHELL with angle option; all materials referred in PCOMP, PCOMPG converted to *MAT_ORTHOTROPIC_THERMAL *SECTION_BEAM LS-DYNA type *SECTION_BEAM
PCOMP PCOMPG
Material Mapping
Nastran type MAT1 MAT2 MAT4 MAT8 MAT9 LS-DYNA type *MAT_ELASTIC *MAT_PIECEWISE_LINEAR _PLASTICITY *MAT_PIECEWISE_LINEAR _PLASTICITY *MAT_ORTHOTROPIC_ELASTIC *MAT_ANISOTROPIC_ELASTIC

Altair Engineering
Coordinate system mapping

Nastran type CORD1R CORD2R LS-DYNA type *DEFINE_COORDINATE_NODE *DEFINE_COORDINATE_SYSTEM
Load mapping
Nastran type SPC FORCE MOMENT PLOAD4 TEMP LSDYNA type *BOUNDARY_SPC *LOAD_NODE_POINT *LOAD_NODE_POINT *LOAD_SEGMENT *INITIAL_TEMP
Altair Engineering

Nastran to RADIOSS (Block Format) Conversion

You can use the Conversion tool to convert a Nastran file to a RADIOSS (Block Format) file. 1. 2. 3. Load the Nastran user profile. Import a Nastran model. Run the conversion macro by clicking Tools > Convert > NASTRAN > To RADIOSS (Block). The Conversion tab will appear at the left side the graphics area. 4. Click Convert to start the conversion. After conversion, the selected version of the RADIOSS (Block Format) user profile is automatically loaded. 5. Review and export the deck using the RADIOSS (Block Format) user profile.
Some of the keywords in the Nastran deck are converted to the RADIOSS (Block Format) deck as per the following table:
Element Mapping
Nastran type CONM2 RADIOSS (Block Format) type /ADMAS Mesh less weld CWELD CELAS1/CELAS2 CDAMP1/CDAMP2 (0 length) PLOTEL RBAR RBE2/RBE3 RJOINT CBUSH (When using vector) CBUSH1D / SPRING3N /SPRING2N Plot element /RIVET /RBODY /RLINK (feabsord, fe realize using HEXA) /SPRING

Altair Engineering
CBAR/CBEAM/CBEND CROD CONROD CTRIA3/CTRIAR CTRIA6 (Change to 1st order before convert) CQUAD4, CQUADR, CSHEAR CQUAD8 (Change to 1st order then convert) CTETRA4 CTETRA10 (Change to 1st order then convert) CHEXA8/ CPENTA6 CHEXA20/ CPENTA15 (Change to 1st order then convert)
BEAM TRUSS TRUSS and /PROP/TRUSS
/SH3N
/SHELL
/TETRA4
/BRICK
Property Mapping
Nastran type PBAR/PBEAM (Only single section PBEAM is supported) PBUSH PBUSH1D/PDAMP/PELAS PROD PSHELL/PSHEAR PSOLID /PROP/BEAM /PROP/SPR_GENE /PROP/SPRING /PROP/TRUSS /PROP/SHELL /PROP/SOLID RADIOSS (Block Format) type
Altair Engineering

Material Mapping
Nastran type MAT1 MAT8 RADIOSS (Block Format) type /MAT/ELASTIC /MAT/LAW19

Altair Engineering
PAM-CRASH 2G to RADIOSS (Block Format) Conversion

You can use the Conversion tool to convert a PAM-CRASH 2G file to a RADIOSS (Block Format) file. 1. 2. 3. Load the PAM-CRASH 2G user profile. Import a PAM-CRASH 2G model. Run the conversion macro by clicking Tools > Convert > Pam Crash > To RADIOSS (Block Format). The Conversion tab will appear at the left side the graphics area. 4. 5. In the Destination RADIOSS Template field, select the destination solver version. Click Convert to start the conversion. After conversion, the RADIOSS (Block Format) user profile is automatically loaded. 6. Review and export the deck using the RADIOSS (Block Format) user profile.
Upon conversion, some of the keywords in the PAM-CRASH 2G deck are converted to the RADIOSS (Block Format) deck as per the following table:
Elements
HM configuration, PAM-CRASH 2G type BAR BEAM SPRING SPRBM MEMBR SHELL SOLID TETRA44 MASS PLINK KJOIN HM configuration, RADIOSS (Block Format) type TRUSS BEAM SPRING SPRING+PROP/SPR_BEAM (TYPE 13) SH3N, SHELL SH3N, SHELL BRICK TETRA44 ADMAS SPRING+INTER/TYPE2 SPRING+PROP/KJOINT(TYPE33)
Altair Engineering

Boundary Conditions
HM configuration, PAM-CRASH 2G type INIVEL BOUNC CONLO HM configuration, RADIOSS (Block Format) type INIVEL BCS CLOAD
System Mapping
HM configuration, PAM-CRASH 2G type FRAME HM configuration, RADIOSS (Block Format) type FRAME
Material Mapping
HM configuration, PAM-CRASH 2G type MAT_1D TYPE 201 MAT_1D TYPE 220 MAT_1D TYPE 223 MAT_2D TYPE 100 MAT_2D TYPE 101 MAT_2D TYPE 102 MAT_2D TYPE 103 HM configuration, RADIOSS (Block Format) type M1_ELASTIC /PROP/SPRING /PROP/SPR_BEAM M0_VOID M1_ELASTIC M36_PLAS_TAB M36_PLAS_TAB, M44_, COWPER M2_PLAS_JOHNS

Altair Engineering
Curve Mapping
HM configuration, PAM-CRASH 2G type FUNCT HM configuration, RADIOSS (Block Format) type FUNCT

HM configuration, PAM-CRASH 2G type TITLE OCTRL/ DSYOUPUT THPOUTPUT /ANIM/DT /TFILE HM configuration, RADIOSS (Block Format) type TITLE
Component Mapping
HM configuration, PAM-CRASH 2G type PART HM configuration, RADIOSS (Block Format) type PART

HM configuration, PAM-CRASH 2G type CNTAC36 HM configuration, RADIOSS (Block Format) type INTER/TYPE7
Rigid Wall Mapping

HM configuration, PAM-CRASH 2G type HM configuration, RADIOSS (Block Format) type
Altair Engineering

RWALL
RWALL

HM configuration, PAM-CRASH 2G type THELE THNODE THLOC HM configuration, RADIOSS (Block Format) type TH/SHEL, SH3N, SPRING, BRIC TH/NODE TH/FRAME/ACCELEROMETER
Section Definition Mapping

HM configuration, PAM-CRASH 2G type SECFO HM configuration, RADIOSS (Block Format) type SECT
Group Definition Mapping

HM configuration, PAM-CRASH 2G type GROUP HM configuration, RADIOSS (Block Format) type GRNOD
Airbag Definition Mapping

HM configuration, PAM-CRASH 2G type BAGIN HM configuration, RADIOSS (Block Format) type MONVOL
The attributes converted in each KEYWORD is explained in the Conversion dialog (see below). Each keyword is associated with a color to distinguish it better. GREEN All the attributes of the KEYWORD are converted to equivalent in RADIOSS

Altair Engineering
ORANGE Only some the attributes of the KEYWORD are converted to equivalent in RADIOSS RED None the attributes of the KEYWORD are converted to equivalent in RADIOSS. Basically conversion of this keyword is not supported by the conversion tool
Altair Engineering


Altair Engineering
Altair Engineering

RADIOSS Conversion Tools

The following conversions are possible when in the RADIOSS user profile:
RADIOSS (Bulk Data Format), OptiStruct to Abaqus Conversion RADIOSS (Block Format) to PAM-CRASH 2G Conversion RADIOSS (Bulk Data Format) to ANSYS Conversion

Altair Engineering
RADIOSS (Bulk Data Format), OptiStruct to Abaqus Conversion

The RADIOSS (Bulk Data Format) to Abaqus conversion tool uses an open conversion scheme; you can specify different mappings in the configuration file. Care has to be taken so that the element and property mappings are consistent. We provided a valid mapping scheme in the ConfigurationFile.txt. This document explains the scope and limitations of the mapping scheme.
Elements
HM elements have two basic attributes configuration (or config) and type . The "config" defines the basic geometrical shape of an element. For example, tria3 configuration is a 3 node triangular element and hexa8 is an 8-node hexahedral element. The "type" defines the solver specific element type of a particular configuration. For example, the 4-node quadrilateral (quad4) element in Abaqus can be any of the following types: S4, S4R, M3D4, R3D4 etc. The Element Types panel shows all supported element configurations and their types for a user profile. For a specific configuration, you can map any supported Nastran element type to any supported Abaqus element type. For example, for a RADIOSS (Bulk Data Format) to Abaqus direction, several 2-noded element configurations such as spring, rigid, bar2, rid, etc are supported. Because all of them are 2-noded elements, conversion across these configurations is also allowed for some element types. For example, CBUSH is of "spring" configuration in the RADIOSS (Bulk Data Format) user profile and CONN3D2 is of rod" configuration in the Abaqus user profile. It is possible to map a CBUSH to CONN3D2 even though their configurations are different. The element mapping scheme must be under the *ElemTypeConversion block in the ConfigurationFile.txt file. You need to provide both configuration and type information to specify the element mapping scheme as shown for the RADIOSS (Bulk Data Format) conversion:
HM configuration, RADIOSS (Bulk Data Format) type tria3, CTRIA3 tria3, CTRIAR quad4, CQUAD4 quad4, CQUADR quad4, CSHEAR tetra4, CTETRA penta6, CPENTA hex8, CHEXA tria6, CTRIA6
HM configuration, Abaqus type tria3, S3 tria3, S3R quad4, S4 quad4, S4R quad4, M3D4 tetra4, C3D4 penta6, C3D6 hex8, C3D8 tria6, STRI65
Altair Engineering

quad8, CQUAD8 tetra10, CTETRA penta15, CPENTA hex20, CHEXA mass, CONM2 mass, CELAS1 mass, CELAS2 rigid, RBE2 rigidlink, RBE2 rbe3, RBE3 spring, CELAS1 spring, CELAS2 spring, CDAMP1 spring, CDAMP2 spring, CBUSH bar2, CBEAM bar2, CBAR rod, CROD rod, CONROD gap, CGAP weld, RBAR
quad8, S8R tetra10, C3D10 penta15, C3D15 hex20, C3D20 mass, MASS mass, SPRING1 mass, SPRING1 rigid, COUP_KIN rigidlink, COUP_KIN rbe3, DCOUP3D spring, SPRING2 spring, SPRING2 spring, DASHPOT2 spring, DASHPOT2 rod, CONN3D2 bar2, B31 bar2, B31 rod, T3D2 rod, T3D2 gap, GAPUNI rigid, KINCOUP
Notes: The CELAS1 or CELAS2 elements in RADIOSS (Bulk Data Format) have both spring stiffness and damping attributes. If both spring and damping values are present and the mapping scheme is

Altair Engineering
CELAS1 to SPRING1, the conversion tool will automatically create an extra DASHPOT element. Similarly, the CONM2 elements in RADIOSS (Bulk Data Format), OptiStruct have both translational and rotational mass values. If both translational and rotational values are present and the mapping scheme is CONM2 to MASS, the conversion tool will automatically create an extra ROTARY1 element.
The table below shows supported sectional property mapping between RADIOSS (Bulk Data Format) and Abaqus. Some of the properties in one solver can be converted to two different Abaqus sections in the other solver. For a RADIOSS (Bulk Data Format), OptiStruct to Abaqus conversion, for example, PSHELL can be converted to *SHELL SECTION or *SHELL GENERAL SECTION. In the mapping scheme, you must select one of them. The property mapping scheme must be under the *PropertyConversion block in the ConfigurationFile.txt file. Abaqus beam section axes are defined at element level in RADIOSS (Bulk Data Format).They are in the sectional property level in Abaqus unless the beam axis is defined by a third node in element connectivity. This means that several elements with different beam axis direction can point to the same PBEAM, PBEAML, PBAR or PBARL property in RADIOSS (Bulk Data Format), OptiStruct. But in Abaqus, all elements under a *BEAM SECTION or *BEAM GENERAL SECTION property have one beam axis orientation. If a third node is used to define the beam axis, even Abaqus beams with a different axis can belong to a single *BEAM SECTION property. The conversion tool allows you to select an extra (1 or 0) argument to define the beam axis conversion mechanism. If the argument is 0 (or not defined), the conversion tool will take the beam axis direction of the first element corresponding to a PBEAM, PBEAML, PBAR or PBARL property and map that to the corresponding *BEAM SECTION or *BEAM GENERAL SECTION card. The beam axis vectors of other elements with the same property will be ignored. If the argument is 1, the conversion tool will create a third node for each element to define the equivalent beam axis vector. As a result, the axis direction for each element will be maintained after the conversion. Because this option updates each element, the conversion process might take a considerable amount of time for models with a large number of beams. The system for CELAS1 or CELAS2 elements is sitting on the grid nodes. Thus, every element can have a different system. Ideally, on conversion one *SPRING (and *DASHPOT) or *CONNECTOR SECTION per element needs to be created. For large models this can be time-consuming. Therefore for CELAS1 two options can be set in the ConfigurationFile.txt (1 or 0). If the option is 1, one property per element will be created (default). If the flag is set to 0, one property per PELAS card will be created. In this case, the settings of the first element found on this property will be translated. From CELAS2 elements you always create a *SPRING and *DASHPOT or *CONNECTOR SECTION property per element. Composite sections PCOMP and PCOMPG can be converted to Abaqus as well. From ConfigurationFile.txt a user can select to convert to SHELL SECTION or SHELL GENERAL SECTION properties. Besides individual layers, the conversion takes care of system assignments, offsets, SYM, BEND and other similar parameters. In PCOMPG a global ply id (GPLYID) number is honored in the ply name in Abaqus user profile after conversion.
Altair Engineering

RADIOSS (Bulk Data Format) PSOLID PSHELL
Abaqus
Beam axis/property option
*SOLID SECTION *SHELL SECTION or *SHELL GENERAL SECTION *SHELL SECTION or *SHELL GENERAL SECTION (COMPOSITE) *BEAM GENERAL SECTION *BEAM SECTION *BEAM GENERAL SECTION *BEAM SECTION *SOLID SECTION *CONNECTOR SECTION (*SPRING + *DASHPOT) or *CONNECTOR SECTION *DASHPOT or *CONNECTOR SECTION (*SPRING + *DASHPOT) or *CONNECTOR SECTION *DASHPOT or *CONNECTOR SECTION (*MASS + *ROTARY INERTIA) 1 or 0 1 or 0 1 or 0 1 or 0 1 or 0
PCOMP(G)
PBEAM PBEAML PBAR PBARL PROD PBUSH PELAS
PDAMP CELAS2
CDAMP2 CONM2
Notes: CELAS2, CDAMP2 and CONM2 are elements in RADIOSS (Bulk Data Format) but they are sectional properties in Abaqus. Therefore, the mapping for them must also be defined under *PropertyConversion The PELAS or CELAS2 in RADIOSS (Bulk Data Format) both spring stiffness and damping attributes. If both spring and damping values are present and they are mapped to *SPRING, the conversion tool will automatically create an extra *DASHPOT property. The elements will both be kept in the same component and the property will be directly assigned to the *SPRING or *DASHPOT element. Similarly, the CONM2 in RADIOSS (Bulk Data Format) has both translational and rotational mass values. If both translational and rotational values are present and it is mapped to *MASS, the conversion tool will automatically create an extra *ROTARY INERTIA component.

Altair Engineering
The property conversion scheme and corresponding element conversion scheme must be consistent. For example, if you define PBUSH to *CONNECTOR SECTION at the property mapping scheme, the corresponding element CBUSH must map to CONN3D2 in the element mapping scheme.
Materials
The table below shows supported material mapping between RADIOSS (Bulk Data Format) and Abaqus. The material mapping scheme must be defined under *PropertyConversion block in the ConfigurationFile. txt file. RADIOSS (Bulk Data Format), OptiStruct MAT1 Abaqus Notes
*MATERIAL
*ELASTIC, TYPE=ISO; *EXPANSION, TYPE=ISO; and *DENSITY (G is used only for *BEAM GENERAL SECTION) When used alone in a PSHELL, MAT2 is translated to *ELASTIC, TYPE=LAMINA or *ELASTIC, TYPE=ANISOTROPIC ELASTIC, TYPE=LAMINA; *EXPANSION, TYPE=ORTHO; and *DENSITY *ELASTIC, TYPE=ANISOTROPIC unless the data are found to be orthotropic, in which case the data are analyzed to create *ELASTIC, TYPE=ENGINEERING CONSTANTS. Also *DENSITY; and *EXPANSION, TYPE=ANISO or ORTHO.
MAT2
*MATERIAL
MAT8
*MATERIAL
MAT9
*MATERIAL
Note:
If a PBEAM or PBAR is mapped to a *BEAM GENERAL SECTION, the material properties defined in the corresponding RADIOSS (Bulk Data Format), OptiStruct material are mapped to the *BEAM GENERAL SECTION card. No *Material is created in this case.
Loads
HM loads have two basic attributes configuration (or config) and type . The supported load "config" are: force, moment, constraint, pressure, temperature, flux, velocity, acceleration and equation. The load "type" defines the solver specific type of a particular configuration. For example, pressure load can be any of the following Abaqus types: DLOAD, FILM, DFLUX etc. The Load Types panel shows all supported load configurations and their types for a user profile. For a specific configuration, you can map any supported RADIOSS (Bulk Data Format), OptiStruct load type to any supported Abaqus load type. The conversion tool does not support conversion across load configurations. The load mapping scheme is valid for either direction and must be under the *BCsTypeConversion block in the ConfigurationFile.txt file. You need to provide both configuration and type information to specify the mapping scheme as shown below:
Altair Engineering

HM configuration, RADIOSS type force, FORCE moment, MOMENT const, SPC const, SPCD const, SUPORT pressure, PLOAD pressure, PLOAD2 pressure, PLOAD4 temp, TEMP equation, MPC
HM configuration, Abaqus type force, CLOAD moment, CLOAD const, BOUNDARY const, VELOCITY const, BOUNDARY pressure, DLOAD pressure, DLOAD pressure, DLOAD temp, TEMPERATURE equation, *EQUATION
In addition to the above load types, the conversion tool also converts RADIOSS (Bulk Data Format), OptiStruct Dload (with corresponding Rload1, Rload2, DAREA, TABLED1, TABLED2, TABLED3) to Abaqus *BOUNDARY or *CLOAD (with corresponding *AMPLITUDE curve). No mapping scheme needs to be specified for this conversion; the conversion is done automatically if present in the model.

The conversion tool maps between RADIOSS (Bulk Data Format), OptiStruct subcases and Abaqus steps. It does not convert the solution type from/to any Abaqus analysis type. You must define it manually using the Abaqus Step Manager or the RADIOSS (Bulk Data Format), OptiStruct Load Step Browser.
Systems and mass

The conversion tool converts RADIOSS (Bulk Data Format), OptiStruct system types into the corresponding Abaqus system (*SYSTEM, *TRANSFORM or *ORIENTATION). It also converts the NSM into *NONSTRUCTURAL MASS and assigns them to the relevant properties. The mapping can be summarized as: HM configuration, RADIOSS type NSM NSM1 HM configuration, Abaqus type *NONSTRUCTURAL MASS

Altair Engineering
NSML NSML1 NSMADD GRID CORD1R CORD1C CORD1S CORD2R CORD2C CORD2S *NODE AND *SYSTEM *SYSTEM for nodes *TRANSFORM if referred to on GRID *ORIENTATION for elements
WTMASS
If the WTMASS parameter is defined in the RADIOSS (Bulk Data Format), OptiStruct model, it is used to modify density, mass, and inertia values during conversion.
See also Radioss Conversion Tools
Altair Engineering

RADIOSS (Bulk Data Format) to ANSYS Conversion

You can use the Conversion tool to convert a RADIOSS (Bulk Data Format) file to an ANSYS file. 1. 2. 3. Load the RADIOSS (Bulk Data Format) user profile. Import a RADIOSS (Bulk Data Format) model. Run the conversion macro by clicking Tools > Convert > RADIOSS (Bulk Data Format) > To ANSYS. The Conversion tab will appear at the left side the graphics area. 4. Click Convert to start the conversion. After conversion, the ANSYS user profile is automatically loaded. 5. Review and export the deck using the ANSYS user profile.
Some of the keywords in the RADIOSS (Bulk Data Format) deck are converted to the ANSYS deck as per the following tables.
Materials
RADIOSS (Bulk Data Format) type MAT1 ANSYS type MATERIAL Convert Parameters Modulus of Elasticity, poisson's ratio and density density density
MAT2 MAT4
MATERIAL MATERIAL
Elements
RADIOSS (Bulk Data Format) type CONM2 CELAS1 CBAR, CBEAM CROD CTRIA3, CTRIAR ANSYS type MASS21 COMBI14 BEAM44 LINK8 SHELL63 HM Configuration Mass Spring Bar2 Rod Tria3

Altair Engineering
CQUAD4, CQUADR, CSHEAR CTRIA6 CQUAD8 CTETRA CTETRA CHEXA CHEXA CPENTA CPENTA
SHELL63
Quad4
SHELL93 SHELL93 SOLID45 SOLID95 SOLID45 SOLID95 SOLID45 SOLID95
Tria6 Quad8 Tetra4 Tetra10 Hex8 Hex20 Penta6 Penta15
Properties
RADIOSS (Bulk Data Format) type PBAR, PBARL, PBEAM, PBEAML PROD ANSYS type BEAM44p Convert Parameters none
LINK8p
none Shell Thickness
PSHELL, PSHEAR (tria3, SHELL63p quad4) PSHELL, PSHEAR (tria6, SHELL93p quad8) PSOLID (tetra4, penta6, hex8) PSOLID (tetra10, penta15, hex20) SOLID45p
Shell Thickness
none
SOLID95p
none
ETType of Ansys: If the model contains RADIOSS (Bulk Data Format) elements which were mapped to MASS21, LINK8,
Altair Engineering

COMBI14, BEAM44, SHELL63, SHELL93, SOLID45 and SOLID95 elements, respective ETTYPES will be created and assigned to the component. Key options of ETTYPE are not updated. Components: If the component collector contains different type of configuration of elements, new components will be created for the respective configurations and those elements will be moved into the new component. ETTYPE, material and realset IDs will be assigned to the new component. Loads and Boundary Conditions: Loads and boundary conditions will not be converted by using this conversion tool.
See also Radioss Conversion Tools

Altair Engineering
RADIOSS (Block Format) to PAM-CRASH 2G Conversion

You can use the Conversion tool to convert a RADIOSS (Block Format) file to a PAM-CRASH 2G file. 1. After loading the RADIOSS (Block Format) user profile and importing a RADIOSS (Block Format) model into the session, run the conversion macro by clicking Tools > Convert > RADIOSS (Block Format) > To Pam-Crash. The Conversion tab will appear at the left side the graphics area. 2. 3. In the Destination Pam-Crash Template field, select the destination solver version. Click Convert to start the conversion. After conversion, the selected version of the PAM-CRASH 2G user profile is automatically loaded. 4. Review and export the deck using the PAM-CRASH 2G user profile.
Some of the keywords in the RADIOSS (Block Format) deck are converted to the PAM-CRASH 2G deck as per the following table:
Element Mapping
HM configuration, RADIOSS (Block Format) type TRUSS BEAM SPRING SPRING+PROP/SPR_BEAM (TYPE 13) SH3N SHELL BRICK TETRA44 ADMAS SPRING+INTER/TYPE2 SPRING+PROP/KJOINT(TYPE33) HM configuration, PAM-CRASH 2G type BAR BEAM SPRING SPRBM SHELL SHELL SOLID TETRA44 MASS PLINK KJOIN
Altair Engineering

RBODY
RBODY
Boundary Conditions Mapping

HM configuration, RADIOSS (Block Format) type INIVEL BCS CLOAD HM configuration, PAM-CRASH 2G type INVEL BOUNC CONLO
System Mapping
HM configuration, RADIOSS (Block Format) type FRAME/FIX SKEW/MOV SKEW/FIX HM configuration, PAM-CRASH 2G type FRAME FRAME FRAME
Material Mapping
HM configuration, RADIOSS (Block Format) type M1_ELASTIC /PROP/SPRING /PROP/SPR_BEAM M0_VOID M36_PLAS_TAB M44_COWPER HM configuration, PAM-CRASH 2G type MAT_1D TYPE 201, MAT_2D TYPE 101 MAT_1D TYPE 220 MAT_1D TYPE 223 MAT_2D TYPE 100 MAT_2D TYPE 102/103 MAT_2D TYPE 102/103

Altair Engineering
M2_PLAS_JOHNS
MAT_2D TYPE 102/103
Property Mapping
HM configuration, RADIOSS (Block Format) type PROP/BEAM PROP/KJOINT PROP/SHELL PROP/SOLID PROP/SPRING PROP/SPR_BEAM PROP/SPR_GENE PROP/TRUSS HM configuration, PAM-CRASH 2G type PART, TYPE= BEAM PART, TYPE = KJOIN PART, TYPE = SHELL PART, TYPE = SOLID PART, TYPE = SPRING PART, TYPE = SPRING PART, TYPE = SPRING PART, TYPE = BAR
Curve Mapping
HM configuration, RADIOSS (Block Format) type FUNCT HM configuration, PAM-CRASH 2G type FUNCT

HM configuration, RADIOSS (Block Format) type TITLE OCTRL/ DSYOUPUT /ANIM/DT HM configuration, PAM-CRASH 2G type TITLE
Altair Engineering

THPOUTPUT
/TFILE
Component Mapping
HM configuration, RADIOSS (Block Format) type PART HM configuration, PAM-CRASH 2G type PART

HM configuration, RADIOSS (Block Format) type CNTAC36 HM configuration, PAM-CRASH 2G type INTER/TYPE7
Rigid Wall Mapping

HM configuration, RADIOSS (Block Format) type RWALL HM configuration, PAM-CRASH 2G type RWALL

HM configuration, RADIOSS (Block Format) type TH/SPRING TH/NODE TH/FRAME HM configuration, PAM-CRASH 2G type THELE THNODE THLOC
Section Definition Mapping

Altair Engineering
HM configuration, RADIOSS (Block Format) type SECT
HM configuration, PAM-CRASH 2G type SECFO
Group Definition Mapping

HM configuration, RADIOSS (Block Format) type GRNOD/NODE GRNOD/GENE GRNOD/SUBSET GRNOD/PART GRNOD/MAT GRNOD/PROP GRNOD/GRNOD GRNOD/SURF GRNOD/GRSHEL GRNOD/GRBRIC GRNOD/GRSPRI GRNOD/GRSH3N GRNOD/GRTRUS GRNOD/GRBEAM GENOD/NODENS GRNOD/FORMULA HM configuration, PAM-CRASH 2G type GROUP GROUP GROUP GROUP GROUP GROUP GROUP GROUP GROUP GROUP GROUP GROUP GROUP GROUP GROUP GROUP
Altair Engineering

Airbag Definition Mapping

HM configuration, RADIOSS (Block Format) type BAGIN HM configuration, PAM-CRASH 2G type MONVOL
The attributes converted in each KEYWORD is explained in the conversion dialog (see below). Each keyword is associated with a color to distinguish better. GREEN All the attributes of the KEYWORD are converted to equivalent in PAM-CRASH 2G ORANGE Only some the attributes of the KEYWORD are converted to equivalent in PAM-CRASH 2G RED None the attributes of the KEYWORD are converted to equivalent in PAM-CRASH 2G. Basically conversion of this keyword is not supported by the conversion tool

Altair Engineering
See also
Altair Engineering

Radioss Conversion Tools

Altair Engineering
XY Plotting
The functions in the XY Plots module allow you to study the relationships between data vectors in results files. This section introduces the functions that are available. Information about xy plots is stored in plot collectors, which are referred to as plots. Plots maintain a list of pointers to curves that are to be displayed on the plot. The plot may contain any number of curves. There is no limit to the number of plot collectors that an HM database may contain. Information about curves is stored in curve collectors, which are referred to as curves. To display a curve, you must assign the curve collector to a plot. A curve may appear on more than one plot at a time and there is no limit to the number of curves that an HM database may contain. You can create standard plots or dual plots that show real /imaginary or phase/magnitude data. Procedures for creating and editing xy plots and curves include: Creating an XY Plot Modifying XY Plots Working with Multiple XY Plots Modifying Multiple XY Plots Creating Curves on XY Plots Reading Curves from an ASCII File Creating Analysis Based Curves Creating Curves using Simple Math Operators Creating Curves from Files or Math Expressions Modifying Curve Attributes Displaying Selected Curves on Plots In addition, you can use the Curve Editor to view and modify curves already defined in your HyperMesh model.
Altair Engineering

XY Plots Module
The XY Plots module is a group of panels that perform operations on plots and the curves displayed on those plots. To access the XY Plots module, select the XY Plots drop down menu. The xy plotting panels are described below: Axis Labels The Axis Labels panel allows you to modify the x and y axes titles and labels. You can also change the color and font size used to display these entities. The Axis Scaling panel allows you to modify the starting and ending values of the plot axes. You can set the values explicitly or implicitly by using the panel functions such as find curves, circle zoom , and zoom out. The Border panel allows you to change the thickness and color of the border around the plot. You may also specify whether the border is displayed and the size of the margin between the border and the plot. The Curve Attribs panel allows you to change the color, marker style (used to indicate the point location), thickness, and the line style (solid, dashed, etc.). You can apply a scaling factor to the original data points. You can also change the curve title that appears in the legend. Creates and modifies the curves in the database. This panel allows you to read data vectors from files as well as perform advanced mathematical operations on curves. The Grid Attribs panel allows you to change the color, line style, thickness of the grid lines, and the margin displayed around the grid lines. The Grid Labels panel allows you to change the color, font, and number of significant places in the labels. Grid labels appear along the x and y axes in the plot (tick marks). Calculates and displays the integral of a curve. The Legend panel allows you to change the location and the font used to display the legend. The Plot Titles panel allows you to change the plot title, subtitle, and label. In addition, you can change the color and font size used to display these entities. Allows you to create an xy plot and assign curves to the xy plot. Allows you to determine the coordinate values of points in a curve. Reads curves from an ASCII file.
Axis Scaling
Border
Curve Attribs
Edit Curves
Grid Attribs
Grid Labels
Integrate Legend
Plot Titles
Plots Query Curves Read Curves

Altair Engineering
Rename Results Curves Simple Math
Allows you to rename curves. Generates a curve from the currently-selected results file. Allows you to perform simple mathematical calculations on a curve.
In addition, you can use the Curve Editor to view and modify curves already defined in your HyperMesh model.
Altair Engineering

Creating an XY Plot
Each xy plot window is assigned a name when you create it. Plot attributes include the title, subtitle, and labels, and also the margin and border around the xy plot. These attributes can be adjusted before or after you add curves to the plot. The first step in the process of creating an xy plot is to use the Plots panel to name and create an xy plot collector. Default values are initially assigned to the xy plot attributes.

Altair Engineering
Modifying an XY Plot
After you create an xy plot, you can change the color, thickness, or width of the border, the grid labels and grid attributes, or add a title to the plot. To modify an xy plot, select the panel that applies to the attribute you want to change, select the plot you want to change, and change the attribute in the panel. After each change, the update is immediately displayed. Each time a panel in the XY Plots module is accessed, the existing values of the current xy plot (the plot listed after plot = ) is displayed in the data entry fields in the panel. Every time you change the current xy plot, the panels in the XY Plots module are updated to reflect the change. This process also applies to curves.
Altair Engineering

Working with Multiple XY Plots

Every xy plot is placed within a window. This allows you to control multiple plots by resizing and moving plots around the screen. XY plot window placement is controlled with the Windows panel. Access this panel by pressing the w key.

Altair Engineering
Modifying Multiple XY Plots

When several plots are contained within a database, you may wish to modify one of the values on all of the plots. For example, you may wish to change the axis titles so that they are all the same. You can modify one plot so that it has the desired values, and then apply those modifications to the other plots, or a subset of the plots, in one step. When you modify xy plots using the panels of the xy plots module, the plot = field allows you to select one plot and the plots entity selector allows you to select multiple plots.
Altair Engineering

Creating Curves on XY Plots

You can create curves using four different methods: Read curves from an ASCII file Extract a curve directly from a results database Create curves by using a few simple math operators Read single curves from files as well as generate curves by using mathematical expressions

Altair Engineering
Reading Curves from an ASCII File

Curves are read from an ASCII file with the Read Curves panel. The format of the input file is assumed is as follows:
XYDATA,TITLE X1, Y1 X2, Y2 . . . ENDDATA XYDATA,TITLE X1, Y1 X2, Y2 . . . ENDDATA
Each curve in the file is defined in a block format. The block begins with the statement, XYDATA. After XYDATA, the title assigned to the curve, which is displayed in the legend, follows on the same line. Point data follows with a set of (x, y) data pairs on each line. The block ends with an ENDDATA statement. In the above example, there are two blocks of data, which define two curves.
Altair Engineering

Creating Analysis Based Curves

Analysis-based curves are generated from the HyperMesh binary results file. When you create an analysis curve, you select entities of interest in your model, and then select a data type for the x axis data points and a data type for the y axis data points. After this information has been supplied, the required data is read from the results file and generates the appropriate curve. Analysis-based curves are generated in the Results Curves panel.
Return to XY Plotting

Altair Engineering
Creating Curves Using Simple Math Operators

Curves can be created using simple math operators in the Simple Math panel. You can combine two curves, transform a curve, or export the curve. For every operation, you can specify that the x or y values of the curve remain fixed. You can also apply external filters to curves in this panel. Examples of external filters are in the filters subdirectory that is provided when this option is selected. Essentially, filters exchange data with HyperMesh, using the standard HyperMesh curve data file format.
Altair Engineering

Creating Curves from Files or Math Expressions

The Edit Curves panel allows you to create new curves or edit existing ones. Each vector of a curve can be defined using either a data vector in a data file or a math expression. For example, the data source for the x vector could be a file, and the data source for the y vector could be a math expression. The data sources for the x and y vectors are displayed in the x = and y = fields. To edit the x and y vectors of a math curve, you must indicate the curve number and the x or y vector, in the format curve number.vector: For example: c1.x c1.y To reference the x vector of curve 1. To reference the y vector of curve 1.
When you modify a curve, the curves are recalculated in the proper order, based on what has been modified. The y vector can be a function of x or the x vector can be a function of y. New data can be selected from a source file or mathematically defined. Source file data is divided into type, request, and component. Type Data files can consist of different types of data. Available data types depend on the data file. Once the data type has been selected, the data request set needs to be selected. After the data request set has been selected, the component must be selected.
Request
Component
Note :
For more information about math expressions, refer to the Altair Math Reference Guide.

Altair Engineering
Modifying Curve Attributes

Modifying curves is very similar to modifying plots. The following curve attributes may be changed in the Curve Attribs panel. curve title curve width The curve title is displayed in the legend. The width of line used when the curve is drawn. HyperMesh currently supports either thick or thin lines. The style of line used to draw the curve. HyperMesh currently supports a solid line, no line at all, and four different patterns. The color used to draw the curve. HyperMesh currently supports 15 standard colors. Determines the markers drawn around each data point in the curve, when the curve is displayed. HyperMesh currently supports circular, triangular, and square markers. The curve may also be displayed with no markers shown. This scale factor is used to scale the x values in a curve. This scale factor is used to scale the y values in a curve.
curve style
curve color curve marker
x scale factor y scale factor
Altair Engineering

Displaying Selected Curves on Plots

After you have read or created curves, you can select which curves in the database you want to display on an xy plot. To select curves for a plot, select the Plots panel and click select curves. A list of the available curves in the database are displayed. The names of the curves that are already displayed on the current xy plot are highlighted. Modify the list by selecting the curves by name and removing or adding the curves to the current plot as desired and click return.

Altair Engineering
Curve Editor
Access the curve editor from HyperMeshs XY plots pull-down menu. The Curve Editor is a user interface that allows you to view and modify graphed curves in a more intuitive and holistic way than the individual xy plots panels provide. The Curve Editor contains four main areas, outlined with colored boxes in the image below: the curve list (green), curve attributes (blue), graph area (red), and graph attributes (cyan).
Its important to be aware that the Curve Editor is not completely symmetrical with HyperMesh, in the sense that changes made in the Curve Editor are automatically sent back to HyperMesh, but changes made in a HyperMesh panel do not automatically get sent to the Curve Editor. For this reason, if you leave the Curve Editor open while making changes within the HyperMesh XY plotting module, you must use the update button in the Curve Editor to import the changes. To summarize: Changes made in the Curve Editor immediately affect HyperMesh. Changes made in HyperMesh do not immediately affect the curve editor, and must be imported by use of the update button. To quit the Curve Editor, click the close command button. Note that any changes you make in the Curve Editor will be retained, because they are automatically applied as you make them.
Altair Engineering

How do I Display curves in the graph area Change a curves attributes Change the graphs attributes Create a new curve Delete a curve Rename a curve
See also XY Plotting

Altair Engineering
To create a new curve:

1. Click the New command button in the Curve Editor window. HyperMesh temporarily supplants the Curve Editor and prompts you to specify a name for the new curve. 2. 3. Type in a name for the new curve. Click proceed. HyperMesh returns you to the Curve Editor. 4. Click the new curve in the curve list and modify its attributes as needed. For example, type in the X and Y coordinates for each data point in the curve.
Altair Engineering

To display curves in the graph area:

1. Click the desired curve in the curve list. The curves attributes fill in the fields in the curve attributes area. 2. 3. Modify the curve attributes if needed. Click the display checkbox in the curve attributes area. The curve displays in the graph area.

Altair Engineering
To change the graph's attributes:

1. In the graph attributes area, modify the fields inside the X-axis frame: Type in a new label to change the graphs X-axis label. For example, you could change it from "X" to "Acceleration". Select a precision to change the number of decimal places that display in the numbers on this axis. Choose a min and max to restrict the graph to a specific range of values. For example, even if your data included accelerations ranging from 0 up to 10 m/s2, you could restrict the X axis to only graph accelerations from 1 to 5 m/s2. Change the number of Tics and Grids per tic to control how fine the grid behind the curves is drawn. The number of Tics indicates how many evenly-spaced, numbered increments display between the beginning and end of the axis. For example, if your data ranges from values of 0 to 2.0, setting Tics to "3" produces three increments (at 0.5, 1.0, and 1.5). The Grids per tic sub-divides each tic, making a finer grid, but these grid lines are not numbered (much like the fractional markings on a ruler). 2. Modify the fields inside the Y-axis frame: Type in a new label to change the graphs Y-axis label. For example, you could change it from "Y" to "time". Select a precision to change the number of decimal places that display in the numbers on this axis. Choose a min and max to restrict the graph to a specific range of values. For example, even if your data included accelerations from 0 seconds to 60 seconds, but you only wish to graph the accelerations that occur between 30 and 35 seconds, you could restrict the range by typing "20" into the min and "35" into the max. Change the number of Tics and Grids per tic to control how fine the grid behind the curves is drawn. The number of Tics indicates how many evenly-spaced, numbered increments display between the beginning and end of the axis. For example, if your data ranges from values of 0 to 2.0, setting Tics to "3" produces three increments (at 0.5, 1.0, and 1.5). The Grids per tic sub-divides each tic, making a finer grid, but these grid lines are not numbered (much like the fractional markings on a ruler). 3. Modify the fields inside the Legends frame: Select a location to determine where the legend displays in the graph area. Click the hide checkbox to toggle the display of the legend on and off.
Altair Engineering

To change a curve's attributes:

1. Click the curve that you wish to modify Or 2. Click the curve in the graph area, if it is already set to Display. Either click the curve in the curve list
Make any desired changes to the curves attributes: Modify each X and/or Y value by clicking it, pressing the <delete> key to erase the current value, and then typing in a new value. Change the Color by clicking the colored box.
A list of available colors displays; click the desired color to select it. Click the display checkbox to toggle the display of the curve in the graph area . To place a marker symbol at each point on the curve, select a symbol from the list box. To change the symbol spacing, select a number from the every: list box.
For example, if you choose "3" then only every third point will display as a symbol. Select a Line style to change the curves line from solid to dotted, or show no line at all. Note: if you choose no line , the lines symbol points will still display. To draw the curve in a thicker line, click the thick line checkbox.

Altair Engineering
To delete a curve:
1. 2. In the curve list, click the curve that you wish to delete. Click the Delete command button. A confirmation window displays. 3. Click Yes to confirm the deletion, or No to keep the curve.
Undo You cannot undo a deletion; once you delete a curve, you cannot recover it.
Altair Engineering

To rename a curve:
1. Click the desired curve in the curve list. HyperMesh temporarily supplants the curve editor and prompts you to specify a new name for the chosen curve. 2. 3. Type in a new name for the curve. Click proceed. HyperMesh returns you to the curve editor, which now uses the curves new name.

Altair Engineering
Post-processing Analysis
The post-processing functions allow you to review the results files and databases generated by external codes. Results files can be translated into HyperMesh results databases which are then read into HyperMesh for post-processing. This translation is done using result translators; for more information, refer to the individual translators in the Interface help system. This section describes the structure of a HyperMesh results database and explains how to use the postprocessing functions to create contour, assigned, deformed, and vector plots. Post-processing functions include: Specifying the Results File Creating Deformed Geometry Plots Creating Animations Creating Vector Plots Creating Contour Plots Creating Assigned Plots Adding Plot Identification - Legends and Titles Inspecting the Results
Altair Engineering

HyperMesh Results Database

The structure of a results database allows you to access results by a method similar to that of the analysis code. A results database is divided into sections called simulations . Each simulation stores the results for a model as it responds to a loading condition. For example, if you run a linear statics problem and apply three different loading conditions to your model, the results file generated by the translator contains three simulations. If you run a nonlinear job, each load step (the response of the model to each incremental amount of load applied) translates to a simulation. Each simulation in the results database is further subdivided into data types. Each data type found in a simulation contains a group of results of the same type. For example, each simulation in a results file may contain two data types: displacements and von Mises stress. A data type may contain only one type of result. Data types are one of the forms described below: nodal displacement Stores three floating point values at a node. This form of data type is usually used to store displacements or a vector quantity. Stores one floating point value at a node. This form of data type is used to store stress quantities or other types of results where a single value is needed at a node. Stores one floating point value at an element. This form of data type is used to store stress quantities or other types of results where a single value is needed at an element. Stores a complex value (magnitude and phase) at a node. This form of data type is usually used to store displacements or a vector quantity. Stores a complex value (magnitude and phase) at a node. Stores a complex value (magnitude and phase) at an element.
nodal value
element value
complex nodal displacement complex nodal value complex element value
complex nodal von Mises Stores a complex von Mises value (magnitude, phase, offset) at a node. complex element von Mises Stores a complex von Mises value (magnitude, phase, offset) at an element.
Data types are not required to contain results for every node or element in the model, and may contain a subset of the total model, if this is appropriate. If this occurs, a message is printed indicating that results for some of the entities requested were not found in the database. In order to complete the post-processing function being executed, HyperMesh sets the results values needed for that function to zero for all of the nodes or elements that are missing.

Altair Engineering
Results Translation
See the following topics regarding Results Translation:
hmabaqus Results Translation Post-processing Actran Results hmansys Results Translation MADYMO Results Translation hmnast Results Translation hmnast Utility hmpam Results Translation PERMAS Results Translation RADIOSS (Fixed Format) Results Translation
Altair Engineering

hmabaqus Results Translation

hmabaqus translates a binary or ASCII Abaqus (.fil) results file into a HyperMesh binary results file. The syntax to run the translator is: hmabaqus [options] <inputfile> <outputfile> <modelfile>
To run hmabaqus from Hypermesh:

1. 2. 3. 4. 5. 6. 7. 8. On the Analysis page, select the Solver panel. Click the translator toggle and select hmabaqus. For input file:, click browse... and select the .fil file. Click Open. For output file:, click browse... and write down the output file name. Click Save. Enter the options. To create an h3d file for a specific result, add h3d after the options. Click solve.
One or more of the following options can be used. Use the command hmabaqus-u to obtain a list of these options. Flag -d -rot -v -a -nflux -nflxrot -von -tr -hydropr -tsi -pstrs Meaning Displacements Rotations Velocities Accelerations NFLUX nflux rotations von Mises Tresca Hydrostatic Pressure Third Stress Invariant Principal Stresses

Altair Engineering
-shstrs -sed -temp -sinktemp -filmcoef -ecursmag -ncursmag -recurmag -ecdmag -ecd1 -ecd2 -ecd3 -resflux -conflux -intflux -fluxs -nodetemp -ts -ls -ns -ps -es -cs -ths -pstrn -pnomsn
Shear Stresses Strain Energy Density Temperature Sink Temperature Film Coefficient ECURS magnitude NCURS magnitude RECUR magnitude ECD magnitude ECD1 ECD2 ECD3 Residual Flux Concentrated flux Internal Flux FLUXS Nodal Temperatures Total Strains Logarithmic Strains Nominal Strains Plastic Strains Elastic Strains Creep Strains Thermal Strains Principal Strains Principal Nominal Strains
Altair Engineering

-plogsn -pps -pes -pths -stress -rmsstrs -rmsstrn -rf -rm -pl -thick -sinv -s1 -s2 -cr -epot -por -ps1v -ps2v -ps3v -sh1v -sh2v -sv1 -sv2 -svn -sv20
Principal Logarithmic Strains Principal Plastic Strains Principal Elastic Strains Principal Thermal Strains Stresses RMS Stresses RMS Strains Reaction Forces Reaction Moments Point Loads Shell Thickness Maximums (default off) First Surface (default off) Second Surface (default off) Contact Results Electrical Potential Pore or Acoustic Pressure (default off) Principal Stress 1 (Vector) Principal Stress 2 (Vector) Principal Stress 3 (Vector) Shear Stress 1 (Vector) Shear Stress 2 (Vector) State Variable 1 (default off) State Variable 2 (default off) State Variable n (default off) State Variable 20 (default off)

Altair Engineering
-notrans -pc56 -maxsim -step -inc -freq -disk -size -file -h3d
Do not convert local displacements into global (default off) Read results for v5.6 on PC (default off) Max simulations (default 999) (default off) For specific STEP results (default off) For specific ITERATION results (default off) For specific frequency of ITERATION results (default off) Translation is performed on disk Number of entities (10000 default) Scratch file name Outputs file to an H3D file instead of to an hmresults file. The file includes model and results information that was translated. The model must contain geometry for it to be output to an H3D file. (default off) Turns off all processing of element integration point values. If you ask Abaqus to average values to element centroids, this option makes a considerable difference in the amount of memory needed. If you also specify a result type that is found on element integration points, and the translator comes across such a result during processing, it reports an error. (default off) State variables were being treated differently for some element groups from others. For some element types, they were always included, and, for others, they were processed only if specifically listed, with the default listing all of them. Now, all are uniform. They are translated only if you requests them to be translated. Also, the translator used to allocate memory to process all 20 allowable state variables whether you asked for any or not. Now, you can turn them on individually, and use just the minimum memory necessary, or you can turn on the first N of them using -nsdv. (default off) Turns on the first <number> state variables (max of 20). If you list both individual state variables and also the -nsdv option, the listed ones are the only ones processed. You can get complete compatibility with older versions by using "-nsdv 20". (default off)
-noip
-sv1, -sv2,..., -sv20
-nsdv <number>
Note:
hmabaqus supports results for a range of increments and steps. It also supports results with a specific frequency. For example, "hmabaqus -inc steps. 10 12 14 40 55" gives results for increments 10 12 14 40 55 for all
"hmabaqus -step 1 5 6 19" gives results for all increments in steps 1, 5, 6 and 19.
Altair Engineering

"hmabaqus -step 1 5 6 19 -inc 10 15 26 31 55" gives results for increments 10, 15, 26, 31, 55 in steps 1, 5, 6 and 19. "hmabaqus -step 1 5 6 19 -freq 2" give results for 1st, 3rd, 5th, 7th, 9th .... last increments in steps 1, 5, 6 and 19. In addition, the following parameters are also available when the results translation is not performed on the analysis platform and when the results file is binary. One of these parameters may need to be specified to indicate the platform where the analysis result file was created.
Parameter -cray -dec -decalpha -hp -ibm -pc -sgi -sun
Analysis File Created On Cray Dec 5000 Dec Alpha Hewlett Packard. IBM RS\6000 PC SGI Sun.
See also Abaqus Interface Overview Supported Data Types Translating Complex Results Translating Element Results for Different Positions

Altair Engineering
Translating Complex Results

Hmabaqus supports real and imaginary results for *STEADY STATE DYNAMICS analysis. If the results are in the form of real and imaginary numbers, hmabaqus calculates the corresponding magnitude and phase. If the magnitude and phases are available from the .fil file, hmabaqus calculates the corresponding real and imaginary values. All complex data type names will have (c) postfix. In addition, data types without the (c) will contain the magnitude of the result. HyperMesh always uses magnitude and phase values to contour plot the complex results. Each result would be obtained using the following equation:
You can choose the value of when viewing the result by specifying the angle on the Contour or Deformed panel on the Post page. When you plot the contour for a complex data type and click on a node/element, both real/imaginary and magnitude/phase pairs are shown.
Altair Engineering

Translating Element Results for Different Positions

There are four options for the POSITION parameter in the *EL FILE keyword in Abaqus. They are CENTROIDAL, AVERAGED AT NODES, INTEGRATION POINTS (default), and NODES. However, in HyperMesh there are only two ways results can be presented: (a) unique value at the center of each element and (b) unique value at each node. Therefore, Hmabaqus must manipulate results from the .fil file to some extent to fit the HyperMesh architecture as follows: 1. For POSITION = CENTROIDAL Hmabaqus reads these values directly and assigns them to the center of each element. An assign plot reflects exactly what is given in the .fil file. A contour plot contributes the same value to each of the element's nodes and for each node, values coming in from all adjacent elements are averaged to create the smooth contour image. 2. For POSITION = AVERAGED AT NODES Hmabaqus reads these values directly and assigns them to each node. A contour plot shows the exact values that were read from the .fil file at nodes. For boundaries between components with material or thickness difference, there may be multiple values for a node in the .fil file. In this case, HyperMesh considers the last value for each node. As a result, you may see a blending of color at nodes along these boundaries. An assign plot averages the result coming from nodes of an element and assigns them to the centroid of the element. 3. For POSITION = INTEGRATION POINTS This is the default option in Abaqus. Hmabaqus averages the values from each integration point to the centroid of an element. For example, for an element with four integration points, Hmabaqus reads the values at each integration point, adds them, and then divides them by 4. This usually gives an answer very close to POSITION = CENTROIDAL. An assign plot reflects these averaged values at elements. A contour plot contributes the same value to each of the element's nodes and for each node, values coming in from all adjacent elements are averaged to create the smooth contour image. 4. For POSITION = NODES Hmabaqus does not currently support this option.

Altair Engineering
Supported Result Types

The following records in the Abaqus .fil results file are supported:
Abaqus/Standard Record Keys 1 2 4 5 10 11 12 14 21 22 23 25 27 33 48 62 Element Header Temperature Distributed Flux Solution-dependent state variables Nodal Flux Stresses Stress Invariants Energy Densities Total Strain Plastic Strains Creep Strains Elastic Strains Shell Thickness Film Coefficients Transverse shear stresses Magnitude and phase angle of stress components RMS values of stress Magnitude and phase angle of strain components RMS values of strain Thermal Strains Logarithmic Strains
Abaqus/Standard Output Request Identifier <none> TEMP FLUX5 SDV NFLUX S SINV ENER E PE CE EE STH FILM TSHR PHS
63 65
RS PHE
66 88 89
RE THE LE
Altair Engineering

90 101 102 103 104 105 106 108 111
Nominal Strains Displacements Velocities Accelerations Reaction Forces Electrical Potential Point, Loads, Moments, Fluxes Pore or Acoustic Pressure Magnitude and phase angle of displacement Electrical Reaction Current Nodal Temperatures Residual Flux Concentrated Flux Internal Flux Principal Stresses Principal Strains Principal Nominal Strains Principal Logarithmic Strains Principal Elastic Strains Principal Thermal Strains Principal Plastic Strains Electrical Current Density Distributed Electrical Current Density Nodal Current Output Request Definition Node Header
NE U V A RF EPOT CF POR PU
138 201 204 206 214 401 403 404 405 408 410 411 425 426 427 1503 1504
RECUR NT RFL CFL RFLE SP EP NEP LEP EEP THEP PEP ECD ECURS NCURS <none> <none>

Altair Engineering
1511 1521 1900 1901 1902 1911 1921 1980 2000 2001
Contact Tractions Contact Clearances Element Definitions Nodal Definitions Active Degrees of Freedom Output Request Definition Abaqus Version Modal Results Increment Start Record Increment End Record
CSTRESS (CPRESS, CSHEAR) CDISP (COPEN, CSLIP) <none> <none> <none> <none> <none> <none> <none> <none>
Abaqus/Explicit Record Keys 1 2 5 11 14 21 22 27 48 73 75 89 90 101 Element Header Temperature Solution-dependent state variables Stresses Energy Densities Infinitesimal Strains Plastic Strains Shell Thickness Transverse Shear Stresses Equivalent Plastic Strain Mises equivalent stress Logarithmic Strains Nominal Strains Displacements
Abaqus/Explicit Output Request Identifier <none> TEMP SDV S ENER E PE STH TSHR PEEQ MISES LE NE U
Altair Engineering

102 103 104 201 204 401 403 404 405 1900 1901 1902 1911 1921 2000 2001
Velocities Accelerations Reaction Forces Nodal Temperatures Reaction Flux Principal Stresses Principal Infinitesimal Strains Principal Nominal Strains Principal Logarithmic Strains Element Definitions Nodal Definitions Active Degrees of Freedom Output Request Definition Abaqus Version Increment Start Record Increment End Record
V A RF NT RFL SP EP NEP LEP <none> <none> <none> <none> <none> <none> <none>
See also Abaqus Interface Overview Results Translation
See also Abaqus Interface Overview Results Translation

Altair Engineering
Post-processing Actran Results

The Actran color map solutions can be displayed in HyperMesh. The generation of the color maps is achieved by two steps: 1. 2. Actran will create color map files in a Patran format (.nod format). Convert the .nod file with the act2hm translator. The syntax to use the translator is: act2hm results.nod results.res where: results.nod is the color map results file in Patran format. This file is generated by Actran. results.res is the name of the new HyperMesh color map results file generated by act2hm.
To post-process the color maps:

1. 2. 3. 4. 5. 6. 7. 8. 9. Click File > Load > Results File. Browse to select the results.res file. Click Open. Click contour on the Post page. Click simulation and choose a simulation result. Click datatype and select a result type. Click contour to generate the color map. You can change the angle to see results for different phases. Note that you must click contour each time you change the angle. Click return to go back to the Post page. Click deformed.
10. Define the simulation and datatype as described in steps 6 and 7 above. 11. Click modal to view an animation of the color map. 12. Click the mode switch to select hidden line. 13. Click the color switch to select contour. 14. Click return twice to go back to the Post page.
The following Actran post-processing features are supported in HyperMesh: OUTPUT_MAP OUTPUT_FRF FIELD_POINT
Altair Engineering


Altair Engineering
hmansys Results Translation

hmansys translates a binary ANSYS results file into a HyperMesh binary results file. You can view results in HyperMesh from the *.rst and *.rth files. Please note that hmansys supports results file up to ANSYS version 8.1. Beyond ANSYS 8.1, results can be post processed in Hyperview. The syntax to run the translator is: hmansys [options] <inputfile> <outputfile> <modelfile> One or more of the following options can be used. Use the command hmansys u to obtain these options. Flag -d -rf -rm -sx1 -sy1 -sz1 -sxy1 -syz1 -sxz1 -sx2 -sy2 -sz2 -sxy2 -syz2 -sxz2 -sx -sy -sz Meaning Displacements Reaction Forces Reaction Moments X Stress (T) Y Stress (T) Z Stress (T) XY Stress (T) YZ Stress (T) XZ Stress (T) X Stress (B) Y Stress (B) Z Stress (B) XY Stress (B) YZ Stress (B) XZ Stress (B) X Stress (max(T,B)) Y Stress (max(T,B)) Z Stress (max(T,B))
Altair Engineering

-sxy -syz -sxz -ntemp -vonmises1 -vonmises2 -vonmises -ps1t -ps2t -ps3t -ps1b -ps2b -ps3b -ps1 -ps2 -ps3 -snx1 -sny1 -snz1 -snxy1 -snyz1 -snxz1 -snx2 -sny2
XY Stress (max(T,B)) YZ Stress (max(T,B)) XZ Stress (max(T,B)) Nodal Temperatures von Mises Stress (T) von Mises Stress (B) von Mises Stress (max(T,B)) Principal Stress 1 (T) Principal Stress 2 (T) Principal Stress 3 (T) Principal Stress 1 (B) Principal Stress 2 (B) Principal Stress 3 (B) Principal Stress 1 (max(T,B)) Principal Stress 2 (max(T,B)) Principal Stress 3 (max(T,B)) X Strain (T) Y Strain (T) Z Strain (T) XY Strain (T) YZ Strain (T) XZ Strain (T) X Strain (B) Y Strain (B)

Altair Engineering
-snz2 -snxy2 -snyz2 -snxz2 -snx -sny -snz -snxy -snyz -snxz -psn1t -psn2t -psn3t -psn1b -psn2b -psn3b -psn1 -psn2 -psn3 -psnvp1 -psnvp2 -psnvp3 -psvp1 -psvp2
Z Strain (B) XY Strain (B) YZ Strain (B) XZ Strain (B) X Strain (max(T,B)) Y Strain (max(T,B)) Z Strain (max(T,B)) XY Strain (max(T,B)) YZ Strain (max(T,B)) XZ Strain (max(T,B)) Principal Strain 1 (T) Principal Strain 2 (T) Principal Strain 3 (T) Principal Strain 1 (B) Principal Strain 2 (B) Principal Strain 3 (B) Principal Strain 1 (max(T,B)) Principal Strain 2 (max(T,B)) Principal Strain 3 (max(T,B)) Principal Strain1(vec.mode) Principal Strain2(vec.mode) Principal Strain3(vec.mode) Principal Stress1(vec.mode) Principal Stress2(vec.mode)
Altair Engineering

-psvp3 -snpx1 -snpy1 -snpz1 -snpxy1 -snpyz1 -snpxz1 -snpx2 -snpy2 -snpz2 -snpxy2 -snpyz2 -snpxz2 -snpx -snpy -snpz -snpxy -snpyz -snpxz -psnp1t -psnp2t -psnp3t -psnp1b -psnp2b
Principal Stress3(vec.mode) X Plastic Strain (T) Y Plastic Strain (T) Z Plastic Strain (T) XY Plastic Strain (T) YZ Plastic Strain (T) XZ Plastic Strain (T) X Plastic Strain (B) Y Plastic Strain (B) Z Plastic Strain (B) XY Plastic Strain (B) YZ Plastic Strain (B) XZ Plastic Strain (B) X Plastic Strain (max(T,B)) Y Plastic Strain (max(T,B)) Z Plastic Strain (max(T,B)) XY Plastic Strain (max(T,B)) YZ Plastic Strain (max(T,B)) XZ Plastic Strain (max(T,B)) Principal Pl. Strain 1 (T) Principal Pl. Strain 2 (T) Principal Pl. Strain 3 (T) Principal Pl. Strain 1 (B) Principal Pl. Strain 2 (B)

Altair Engineering
-psnp3b -psnp1 -psnp2 -psnp3 -sntx1 -snty1 -sntz1 -sntxy1 -sntyz1 -sntxz1 -sntx2 -snty2 -sntz2 -sntxy2 -sntyz2 -sntxz2 -sntx -snty -sntz -sntxy -sntyz -sntxz -psnt1t -psnt2t
Principal Pl. Strain 3 (B) Prin. Pl. Strain 1 (max(T,B)) Prin. Pl. Strain 2 (max(T,B)) Prin. Pl. Strain 3 (max(T,B)) X Thermal Strain (T) Y Thermal Strain (T) Z Thermal Strain (T) XY Thermal Strain (T) YZ Thermal Strain (T) XZ Thermal Strain (T) X Thermal Strain (B) Y Thermal Strain (B) Z Thermal Strain (B) XY Thermal Strain (B) YZ Thermal Strain (B) XZ Thermal Strain (B) X Thermal Strain (max(T,B)) Y Thermal Strain (max(T,B)) Z Thermal Strain (max(T,B)) XY Thermal Strain (max(T,B)) YZ Thermal Strain (max(T,B)) XZ Thermal Strain (max(T,B)) Principal Th. Strain 1 (T) Principal Th. Strain 2 (T)
Altair Engineering

-psnt3t -psnt1b -psnt2b -psnt3b -psnt1 -psnt2 -psnt3 -swstrain -epeq1 -epeq2 -epeq -altids -noconv -v53 -disk -size -file -h3d
Principal Th. Strain 3 (T) Principal Th. Strain 1 (B) Principal Th. Strain 2 (B) Principal Th. Strain 3 (B) Prin. Th. Strain 1 (max(T,B)) Prin. Th. Strain 2 (max(T,B)) Prin. Th. Strain 3 (max(T,B)) Swelling strain Av. Eq. Plastic Strain (T) Av. Eq. Plastic Strain (B) Av. Eq. Pl. Strain (max(T,B)) Use alternate element ids. Do not transform to global (default off) (default off)
Translate version5.3 rst file (default off) Translation is performed on disk (default off). Number of entities (10000 default). Scratch file name (default off). Outputs file to an H3D file instead of to an hmresults file. The file includes model and results information that was translated. The model must contain geometry for it to be output to an H3D file.
If the size of the binary file is too large for hmansys to use, use the following option: hmansys -disk -size 10000 -file /tmp/scratch.tmp In addition, the following parameters are also available when the results translation is not performed on the analysis machine and when the results file is binary. One of these parameters may need to be specifed to indicate where the analysis result file was created: Parameter Analysis File Created On

Altair Engineering
-cray -dec -decalpha -hp -Ibm -pc -sgi -sun
Cray Dec 5000 Dec Alpha Hewlett Packard. IBM RS\6000 PC SGI Sun
Altair Engineering

MADYMO Results Translation

Post-processing can be done in HyperView using both Kinematic and FEMANI files. Refer to the HyperView online help for information about viewing MADYMO results.
Results Supported for Elements

Damages Hydrostatic pressure Pressure Principal stresses Strains Stresses Thickness
Results Supported for Nodes

Displacements Internal force vector Internal reaction force vector Internal reaction moment force vector Ellipsoid data Elliptical cylinder data Triangular plane data Quadrangular plane data Kelvin element data Belt segment data Maxwell element data Marker data Accelerometer data Null system data Point restraint data Gas jet data (only coordinates and gas flow data)

Altair Engineering
Muscle data (only coordinates)
Altair Engineering

hmnast Results Translation

You can view the result files from the Contour, Deformed, Hidden Line , and Transient panels.
hmnast hmnasto2 hmnastf06 hmnastopt
See also Viewing the result files Nastran Interface Overview

Altair Engineering
hmnast Utility
hmnast translates Nastran ASCII punch files into HyperMesh binary results files. hmnast can be executed either independently or directly from HyperMesh. To run hmnast independently, use the following syntax: hmnast [arguments] <inputfile> <outputfile> where [arguments] are optional arguments. Arguments such as displacements, stresses and strains are on by default. To obtain these arguments, use the command hmnast -u.
To run hmnast from Hypermesh:

1. 2. 3. 4. 5. 6. 7. Open the Solver panel. Click the translator toggle and select hmnast. For input file:, click browse... and select the punch file. Click Open. For output file:, click browse... and select the output file location and name. Click Open. Enter the options. To create an h3d file for a specific result, add h3d after the first option. For example, to create an h3d file of the displacement, the option should be -d h3d Click solve.
8.
The following options are off by default: Flag -m -minimums -iter -trans -corner -bulk -noconv -nolabels Meaning Displacements and maximums Minimums instead of maximums Nonlinear iterations (from SOL 106) Transient thermal Corner stresses (for CQUAD4 and solid elements) Reads element connectivity from the bulk file (for use with the corner option) Do not convert local displacements into global coordinates Do not use subcase labels
Altair Engineering

-title -subtitle -disk -size -file -csa -1Dforce -1Dstress -2Dforce -repR -h3d
Use title for simulation name Use subtitle for simulation name Translation is performed on disk Number of entities (10000 = default) Scratch file name Translates CSA/Nastran Reads all forces for 1-D elements Reads all stresses for 1-D elements Reads all forces for 2-D elements Replaces R/NaN/nan fields with 0.0 (found in strain energy data types) Outputs file to an H3D file instead of an hmresults file. The hmresult file includes translated model and results information. The punch file must contain geometry for it to be output to an H3D file. If there is no geometry in the punch file, use bulk <filename> in addition to h3d. Example: hmnast -h3d -bulk myFile.dat myFile.pch myFile.h3d H3D files can be created either by using hmnast or from HyperMesh.
hmnast supports the following data types: Displacements, rotations, velocities, and accelerations SPC forces and SPC moments Grid Point Force Balance (totals block only) Real element forces Element name codes: 1, 2, 10, 11, 12, 33, 34, 74, 100 Real stresses Element name codes: 1, 2, 4, 10, 33, 34, 39, 64, 67, 68, 70, 74, 75, 82, 85, 88, 90, 91, 93, 144 Real strains Element name codes: 4, 33, 39, 64, 67, 68, 70, 74, 75, 82, 85, 88, 90, 91, 93, 144 Complex stresses Element name codes: 33, 39, 64, 67, 68, 70, 74, 75, 82 Complex strains Element name codes: 33, 39, 64, 67, 68, 70, 74, 75, 82

Altair Engineering
Temperatures Flux Strain energies Time Eigenvectors Frequency How HyperMesh displays displacement results translated by hmnast: When hmnast reads displacement results, a flag is set to 1. The -noconv option sets this flag to 0. When HyperMesh reads the results file translated by hmnast, it checks the value of the flag. If the value is 1, HyperMesh translates the nodal displacement into basic* coordinate using the system attached to the node, in the case where no system is attached to the node, HyperMesh performs no further translation. If the value of the flag is 0, HyperMesh performs no further translation. As defined by MSC-Nastran.
NOTES To extract displacements and maximum von Mises stresses from the punch file, use the option -d von_max. To extract only the maximum values of the data types, specify the option -m. For iterative solutions encountered in SOL 106, use the option -iter. For transient solutions encountered in SOL 159, use the option -trans. For nonlinear transient solutions encountered in SOL 129, use the options -trans -iter. Corner stresses: Use -corner option when STRESS(CORNER) or STRESS(BILIN) is used in the data file. When using -corner option, hmnast requires the bulk data information. This can be done by using ECHO=PUNCH during analysis. Otherwise, use the -bulk <bulkfilename> option. When using STRESS(CORNER), Nastran gives corner stresses on a per-element basis. However, hmnast averages the corner stresses at the nodes for adjacent elements. HyperMesh converts the nodal displacements into global coordinates if there are non-zero values in the CD field of the GRID cards. To display the results in HyperMesh as they are reported in the punch file, use the option -noconv Simulation names: hmnast organizes the punch file results into a series of simulation names and data types. The simulation names correspond to the LABEL card of the punch file for SOL101. To create a simulation name, the first 27 characters from the LABEL card are appended with the SUBCASE ID. The corresponding data types are Displacements, von Mises Stress, and so on. If the option -
Altair Engineering

nolabels is selected, the simulation name corresponds to the SUBCASE ID number. Use -title to use the TITLE card of your punch file as the simulation name. Use -subtitle to use the SUBTITLE card of your punch file as the simulation name. The simulation name for SOL106 is SUBCASE # Iter #. For modal frequency response problems, the simulation name is Mode # f #Hz. For modal frequency response problems where the complex part of the eigenvalue is used (SOL 107 and SOL 110), the simulation name is Mode # f #Hz. For direct frequency response, the simulation name is Subcase # f #. For transient problems (SOL159, SOL129), the simulation name is Time #. Do not use -nolabels for SOL106, SOL159, and SOL129. If the size of the punch file is too large, use the option -disk -size n -file /temp/ scratch.tmp, where n corresponds to the maximum number of nodes/elements in the model and scratch.tmp is the scratch file name that hmnast creates in the /tmp/ directory. hmnast supports punch files for the following solutions: SOL 101, 103, 105, 106, 107, 108, 109, 110, 111, 112, 129, 153 and 159 To extract only selected modes from a punch file, use the option -selmodes <selmodesfile>, where selmodesfile contains the mode numbers that need to be extracted. These numbers must have spaces separating them. Any number of lines can be entered. A line cannot exceed 256 characters. To extract only a selected number of subcases, use the option -selsubc <selsubcfile>.
How do I... Post process Nastran results in HyperMesh Create an h3d file from HyperMesh
See also Splitting punch files Translating Complex Results hmnasto2 hmnastf06 hmnastopt Nastran Interface Overview

Altair Engineering
Splitting Punch Files

Since punch files tend to be very large, especially true files for dynamic analysis, you may occasionally receive a message such as, out of memory or cannot read from file. When this situation occurs, you can translate the file by splitting it into several punch files. The number of smaller files needed can be determined by observing the size of the punch file, the number of simulations, and what is inside each simulation. Once smaller files are created, use hmnast to translate each file. Name the first results file name.res (extension optional), the second results file name1.res, the third results file name2.res, etc. Punch files have a header recursive format, for example: $TITLE =
$SUBTITLE= $LABEL =
$DISPLACEMENTS $REAL-IMAGINARY OUTPUT $SUBCASE ID = $FREQUENCY = . displacement for each nodes . $TITLE = 1 0.1
$SUBTITLE= $LABEL =
$DISPLACEMENTS $REAL-IMAGINARY OUTPUT $SUBCASE ID = $FREQUENCY = . displacement for each nodes 1 0.2
Altair Engineering

If there is more than one subcase, the number in $SUBCASE ID = and the data changes while everything else remains the same. If there is more than one data type, for example DISP and STRESS, the header for DISPLACEMENT and STRESS will be the same. There are three ways to split a punch file: Along SUBCASES Along DATA TYPES (same subcase) Among the same DATA TYPE
How do I... To split a punch file along SUBCASES To split a punch file along DATA TYPES (same subcase) To split a punch file amid the same DATA TYPE To split a punch file in UNIX To load or append multiple results files into a single HyperMesh session

Altair Engineering
To split a punch file along SUBCASES

Store from $TITLE = to the end of data for a single subcase into one file and the other subcase into another file. Example: The initial punch file: $TITLE =
$SUBTITLE=
$LABEL
$DISPLACEMENTS
$REAL-IMAGINARY OUTPUT
$SUBCASE ID =
$FREQUENCY =
0.1
displacement for each node $TITLE =
$SUBTITLE=
$LABEL
$DISPLACEMENTS
$SUBCASE ID =
$FREQUENCY =
0.1
displacement for each node New punch files: One.pch $TITLE = $SUBTITLE= Two.pch $TITLE = $SUBTITLE=
Altair Engineering

$LABEL = $DISPLACEMENTS $REAL-IMAGINARY OUTPUT $SUBCASE ID = 1 $FREQUENCY = 0.1 displacement for each node
$LABEL = $DISPLACEMENTS $REAL-IMAGINARY OUTPUT $SUBCASE ID = 2 $FREQUENCY = 0.1 displacement for each node

Altair Engineering
To split a punch file along DATA TYPES (same subcase)

Store from $TITLE = to the end of one DATA TYPE (i.e., DISP) in one file and the other DATA TYPE (i.e., STRESS) in another file. Be sure to change the SUBCASE number in the second file to a number different from the one in the first file. Example: Initial punch file: =
$TITLE
$SUBTITLE=
$LABEL
$DISPLACEMENTS
$SUBCASE ID =
$FREQUENCY =
0.1
displacement for each nodes $TITLE =
$SUBTITLE=
$LABEL
$STRESS $REAL-IMAGINARY OUTPUT
$SUBCASE ID =
$FREQUENCY =
0.1
stress for each element New punch files: One.pch $TITLE = Two.pch $TITLE =
Altair Engineering

$SUBTITLE= $LABEL =
$SUBTITLE= $LABEL $STRESS $REAL-IMAGINARY OUTPUT 1 0.1 $SUBCASE ID = $FREQUENCY = 0.1 2 =
$DISPLACEMENTS $REAL-IMAGINARY OUTPUT $SUBCASE ID = $FREQUENCY =
displacement for each node
stress for each element

Altair Engineering
To split a punch file among the same DATA TYPE

Store from $TITLE = to the end of one section into one file and the other into another file. In this case, since the DATA TYPE is the same, the SUBCASE number can stay the same. Example: $TITLE Initial punch file: =
$SUBTITLE=
$LABEL
$DISPLACEMENTS
$SUBCASE ID =
$FREQUENCY =
0.1
displacement for each node $TITLE =
$SUBTITLE=
$LABEL
$DISPLACEMENTS
$SUBCASE ID =
$FREQUENCY =
0.2
displacement for each node New punch files One.pch $TITLE = Two.pch $TITLE =
Altair Engineering

$SUBTITLE= $LABEL = $DISPLACEMENTS $REAL-IMAGINARY OUTPUT $SUBCASE ID = 1 $FREQUENCY = 0.1 displacement for each node
$SUBTITLE= $LABEL = $DISPLACEMENTS $REAL-IMAGINARY OUTPUT $SUBCASE ID = 1 $FREQUENCY = 0.2 displacement for each node

Altair Engineering
To split a punch file in UNIX

The quickest way to split a file is in UNIX using the Vi text editor. In this example, the file s11p1s1disp2001.pch is used. It has only one SUBCASE containing DISPLACEMENT and STRESS results. 1. Know where (what line) to split. At the prompt, use the less command: less s111p1s1disp2001.pch The file is loaded one buffer at a time, eliminating problems related to large file size. 2. Use the /STRESS command to locate the first STRESS. In this example, the file will be split between DISPLACEMENT and STRESS.
The result from the above command is
3.
In the screen shown above, the STRESS data begins at line 9277. Using the head and tail commands, split s111p1s1disp2001.pch into dispall.pch (DISPLACEMENT only) and stressall.pch (STRESS only). Use the following command to create dispall.pch: head 9276 s111p1s1disp2001.pch > dispall.pch Line 1 to line 9276 of file s11p1s1disp2001.pch is copied into dispall.pch.
Altair Engineering

Use the following command to create stressall.pch: tail +9277 s111p1s1disp2001.pch > stressall.pch Line 9277 to the end of file s11p1s1disp2001.pch is copied into stressall.pch. 4. The SUBCASE numbers in dispall.pch and stressall.pch are both 1. Therefore, the SUBCASE number in stressall.pch file should be changed to 2 (or anything other than 1).

Altair Engineering
To load or append multiple results files into a single HyperMesh session

1. 2. From the File drop down menu, select Load and select Results File. Browse to the file name.res and click Open.
HyperMesh reads name.res, name1.res, name2.res, and so on.
Altair Engineering

To translate two punch files and read them in HyperMesh:

1. Translate the first punch file and name the results file name.res (extension optional). The results file, result.res, is created. 2. Translate the second punch file and name the results file name1.res (extension optional). Observe the number following name. The results file, result1.res, is created. 3. 4. Read both result files in HyperMesh. Select the result.res file and all your results files are read into HyperMesh (result1.res, result2.res, and so on). Keep in mind that in the initial punch file, both DISPLACEMENT and STRESS are in SUBCASE 1 but, now DISPLACEMENT is in SUBCASE1 and STRESS is in SUBCASE2.
Note:

Altair Engineering
hmnasto2 Utility
hmnasto2 translates OUTPUT2 Nastran binary results into HyperMesh binary results files. hmnasto2 can be executed either independently or directly from HyperMesh. To run hmnast02 independently, use the following syntax: hmnasto2 [arguments] <inputfile> <outputfile> where [arguments] are optional arguments. Arguments such as displacements, stresses, and strains are on by default. To obtain those arguments, use the command hmnasto2 -u.
To run hmnasto2 from Hypermesh:

1. 2. 3. 4. 5. Open the Solver panel. Click the translator toggle and select hmnasto2. Click input file = and select the op2 file location and name. Click output file = and select the output file location and name. Enter the options. The first option should be the machine used to generate the Nastran binary results file. To create an h3d file for a specific result, add h3d after the second option. For example, to create an h3d file of the displacement result that was created from SGI computer, the option would be: -sgi -d h3d The following options are off by default: Flag -m -iter -nolabels -corner -csa -subcman -cray -dec -decalpha -hp Meaning Displacements and maxs Nonlinear iterations Do not use subcase labels Corner stresses Translate CSA/Nastran Subcase manager Cray Dec 5000 Dec Alpha Hewlett Packard
Altair Engineering

-ibm -pc -sgi -sun -linux -h3d
IBM RS\6000 PC SGI Sun Linux Outputs file to an H3D file instead of an hmresults file. The file includes translated model and results information. The model must contain geometry for it to be output to an H3D file. If there is no geometry in the op2 file, use bulk <filename> in addition to h3d. Example: hmnasto2 -h3d -bulk myFile. dat myFile.op2 myFile.h3d H3D files can be created either by using hmnast or from HyperMesh.
When you use hmnasto2, specify the machine used to generate the Nastran binary results file (-cray, sgi or -pc, and so on). hmnasto2 supports the following data types: Displacements, rotations, velocities and accelerations Eigenvectors Grid Point Stress Nonlinear Stress and Strain Element Name Codes: 90, 88, 85, 91, 93 Real and complex stresses Element Name Codes: 4, 33, 39, 64, 67, 68, 74, 75, 144 Real strains Element Name Codes: 4, 33, 39, 64, 67, 68, 74, 75, 144 Strain energies Shear Flux
How displacement results translated by hmnasto2 are displayed:

Altair Engineering
MSC-Nastran writes displacement results into different data blocks based on selected parameters. When hmnasto2 reads these data blocks, a flag is set to 0 if it reads displacement results in basic* coordinate or 1 if it reads displacement result in global* coordinate. The -noconv option sets this flag to 0. When HyperMesh reads the results file translated by hmnasto2, it checks the value of the flag. If the value is 1, HyperMesh translates the nodal displacement into basic* coordinate using the system attached to the node. If the value of the flag is 0, HyperMesh performs no further translation. As defined by MSC-Nastran. Notes There are two ways to extract models (without result) from an op2 file: To extract a model in HMASCII format, use the following syntax: hmnasto2 -<machine use to generate op2 file> <modelfile> <inputfile> <outputfile>
The model can be imported into HyperMesh using the HMASCII reader, which can be invoked from the import tab. Or To extract a model in h3d format, use the following syntax: hmnasto2 -<machine use to generate op2 file> <modelfile> The model can be imported into HyperView using the h3d reader. To extract displacements and maximum von Mises stresses from the OUTPUT2 file, use the option -d von_max. To extract only the maximum values of the data types, use the option -m. For iterative solutions encountered in SOL 106, use the option -iter. Simulation names: hmnasto2 organizes the punch file results into series of simulation names and data types. The simulation names correspond to the LABEL card for SOL101. The corresponding data types are displacements and von Mises stress, for example. If the option -nolabels is selected, the simulation name corresponds to the SUBCASE ID number. The simulation name for SOL106 is SUBCASE # Iter #. For modal frequency response problems, the simulation name is Mode # f #Hz. For modal frequency response problems where the complex part of the eigenvalue is used (SOL 107 and SOL 110), the simulation name is Mode # f #Hz. For direct frequency response, the simulation name is Subcase #f #. -h3d model <inputfile>
Altair Engineering

Do not use -nolabels for SOL106. Corner options: Use -corner option when STRESS(CORNER) or STRESS(BILIN) is used in the data file. Note that when STRESS(CORNER) is used, Nastran gives corner stresses on a per-element basis. However, hmnasto2 averages the corner stresses at the nodes for adjacent elements. If there is no geometry information in the op2 file, use an additional bulk <bulkfilename> option. In general, geometry information is written into the op2 file if PARAM,POST,-2 is used in the input file. For more information regarding geometry information in an op2 file, see Nastran documentation. If the size of the punch file is too large, use the option -disk -size n -file /temp/scratch.tmp, where n corresponds to the maximum number of nodes/elements in the model and scratch.tmp is the scratch file name that hmnasto2 creates in the / temp/ directory. hmnasto2 supports OUTPUT2 files for the following solutions: SOL 101, 103, 105, 106, 107, 108, 109, 110, 111 and 153. hmnasto2 supports the following data block names for PARAM,POST,-1: OQG1, OUGV1, OES1, OEF1, OSTR1, ONRGY1, OES1X and OPG1. hmnasto2 supports the following data block names for PARAM,POST,-2: OQG1, BOUGV1, BOPHIG, OUGV1, OES1, OEF1, OSTR1, ONRGY1, ONRGY2 and OES1X. Use -nosubcman for SOL103 OUTPUT2 files when the HMNASTO2 default is unsatisfactory. To extract only a selected set of modes and subcases, use the option -selsubc <selsubcfile> or selmodes <selmodesfile>, where selmodesfile contains the mode numbers and selsubcfile contains the subcase numbers that need to be extracted.
How do I... Post-process Nastran results in HyperMesh Create an h3d file from HyperMesh Create a model file from an op2 file and load the model file Translating Complex Results
See also hmnast

Altair Engineering
hmnastf06 hmnastopt Nastran Interface Overview
Altair Engineering

To create a model file from an op2 file and load the model file
Create a model file: From the command line, type: hmnasto2 [arguments] <input file> <output file> <model file>
Load the model file: 1. 2. 3. 4. 5. From the File menu, select Import.... Set the Import type: field to FE Model. Set the File type: field to HMASCII. In the File: field, browse to select the file to open. Click Apply.

Altair Engineering
hmnastf06 Utility
hmnastf06 translates Nastran *.f06 ASCII files into HyperMesh binary results files. hmnastf06 reads only the GPSTRESS output from the .f06 file for SOL101 analyses. The syntax to run the translator is: hmnastf06 [arguments] <inputfile> <outputfile> where [arguments] are the optional arguments. To obtain the arguments, use the command hmnastf06 -u. hmnastf06 arguments are on by default. Notes: hmnastf06 requires that FIBRE ALL is used in the SURFACE command during analysis hmnastf06 organizes the GPSTRESS results into simulations based on subcase ID and surface ID/ volume ID
Altair Engineering

hmnastop Utility
hmnastopt translates Nastran SOL 200 punch files into HyperMesh binary results files. hmnastopt requires the following options in the dat file: DISPLACEMENT(PUNCH) = ALL STRESS(PUNCH) = ALL ANALYSIS = STATICS ANALYSIS = MODES PARAM, DESPCH>0 The syntax to run the translator is: hmnastopt [options] <inputfile> <outputfile> Notes Use the command hmnastopt -u to obtain information about the options. The h3d flag outputs file to an H3D file instead of to an hmresults file. The file includes model and results information that was translated. The model must contain geometry for it to be output to an H3D file. If the punch file contains the keywords GRID and DESVAR, the option -bulk <bulkfile>must be provided To generate HyperMesh compatible x-y plot data (design cycle number vs. thickness), use the option plot <plotfile>

Altair Engineering
Translating Complex Results

Magnitude and phase values are always used to contour plot the complex results. Therefore, if the Nastran output is in the form of real and imaginary numbers, hmnast and hmnasto2 will calculate the corresponding magnitude and phase. The results will then be obtained using the following equation:
result
magnitude * cos t
phase
You can choose the value of t when viewing the result by specifying the angle on the Contour or Deformed panel.
Altair Engineering

To post-process NASTRAN results in HyperMesh:

Before viewing the result file, make sure that the model is loaded. The model can be loaded prior to or after translating the result file.
To translate Nastran results: 1. 2. 3. Click File > Load > Results File. Browse to select the binary results file generated by the hmnast, hmnast02, or hmnastf06 translator. Click Open.
To view the contour result: 1. 2. 3. 4. Open the Contour panel. Click simulation= to choose simulation title. Click data type= to choose the data to be simulated. Click contour to view the smooth transition result. Or Click assign to view the border line result.
To view the deformed result: 1. 2. 3. 4. Open the Deformed panel. Click simulation= to choose simulation title. Click data type= to choose the data to be simulated. Click deform to view deformation in static condition. Or Click linear to view deformation in dynamic condition.
To view the transient result: 1. 2. 3. 4. 5. Open the Transient panel. Click start with= to choose the beginning of the transient simulation. Click end with= to choose the end of the transient simulation. Click data type= to choose the data to be simulated. Click transient.

Altair Engineering
Note:
This is applicable for time dependent analysis such as modal analysis (sol 103), etc.
Altair Engineering

hmpam Results Translation

PAM-CRASH Results Translation PAM-CRASH 2G Results Translation

Altair Engineering
PAM-CRASH Results Translation

Hmpam no longer requires a license for ESI DSYLIB. hmpam translates information from a PAM-CRASH results file (.DSY file) to a HyperMesh binary results file or to a Hyper3D (.h3d) file. The syntax to run the translator is: hmpam [-h3d] [arguments] <input file> <output file> [model file] [-options<Filename>] If the -h3d option is selected, the output file is written in the h3d format and contains model data and results in one file. The selection of the option [model file] is not allowed in this case. hmpam can also translate a model from a PAM-CRASH .THP file. In this case, only the model will be output (no results). In addition, hmpam can also read PAM-CRASH 2G result files. The option [-options<Filename>] can be repeated, but it must be used as the last option. [arguments] can be any of the following: Flag -d -v -a -sxx -syy -szz -sxy -syz -szx -3S1 -3S2 -3S3 -mxx -myy Meaning Displacements Velocities Accelerations SXX SYY SZZ SXY SYZ SZX Minimum Principal Stress 3-D (for solids only) Maximum Principal Stress 3-D (for solids only) Second Principal Stress 3-D (for solids only) Local bending moment about r-axis Local bending moment about s-axis
Altair Engineering

Flag -mxy -m1 -m2 -nxx -nyy -nxy -n1 -n2 -eple -epma -epmi -epsi -sigm -thic -thin -esma -esmi -faxi -fssh -ftsh -mtor -msn1 -mtn1
Meaning Local twist bending moment Max Principal bending moment Min Principal bending moment Local membrane stress resultant in r-direction Local membrane stress resultant in s-direction Local in-plane shear membrane stress resultant Max. Principal membrane stress resultant Min. Principal membrane stress resultant Equivalent Plastic Strain Maximum plastic strain over thickness Minimum plastic strain over thickness Lower and upper surface strain tensors Lower and upper and middle surface stress tensors Resultant Shell Thickness Resultant Shell Thinning Maximum equivalent stress over thickness Minimum equivalent stress over thickness Force in local R-direction Force in local S-direction Force in local T-direction Flexion bending moment about local u-direction Directional dependency function for flexion moment Torsion bending moment about local T-direction

Altair Engineering
Flag -msn2 -mtn2 -daxi -rtor -rsn1 -rtn1 -rsn2 -rtn2 -stepN -disk -file -options
Meaning Resultant damping moment Resultant friction moment Axial elongation in R direction Torsion angle about local r axis Bending rotation angle about local S-axis at node 1 Bending rotation angle about local T-axis at node 1 Bending rotation angle about local S-axis at node 2 Bending rotation angle about local T-axis at node 2 Step increment N, where N is a positive integer. (default N=1) Translation is performed on disk Scratch file name [Filename] gives the file name for the options file. Syntax is described below. Outputs file to an H3D file instead of to an hmresults file. The file includes model and results information that was translated. The model must contain geometry for it to be output to an H3D file.
-h3d
The following options can also be used: Flag -disk -size -file -u Meaning Translation is performed on disk (default off) Number of entities (1000 default) Scratch file name (default off) Usage, gives this help
The following parameters are also available when the results translation is not performed on the analysis
Altair Engineering

machine. You may need to specify one of these parameters to indicate where the analysis result file was created: Parameter -cray -dec -decalpha -hp -ibm -pc -sgi -sun Analysis File Created On Cray Dec 5000 Dec Alpha Hewlett Packard IBM RS\6000 PC SGI Sun
The supported results include the following: nodal Displacements Velocities Accelerations
bricks Sigma - xx Sigma - yy Sigma - zz Sigma - xy Sigma - yz Sigma - zx Minimum Principal Stresss 3-D Maximum Principal Stress 3-D Second Principal Stress 3-D

Altair Engineering
EPLE: Equivalent Plastic Strain
beams (the definitions of the following variables depend on the material type) FAXI FSSH FTSH MTOR MSN1 MTN1 MSN2 MTN2 DAXI RTOR RSN1 RTN1 RSN2 RTN2
tools Thickness
shells MXX - Local bending moment about r-axis MYY - Local bending moment about s-axis MXY - Local twist bending moment M1 - Maximum Principal bending moment M2 - Minimum Principal bending moment NXX - Local membrane stress resultant in r-direction NYY - Local membrane stress resultant in s-direction NXY - Local in-plane shear membrane stress resultant N1 - Maximum Principal membrane stress resultant
Altair Engineering

N2 - Minimum. Principal membrane stress resultant EPMA - Maximum plastic strain over thickness EPMI - Minimum plastic strain over thickness THIC - Resultant shell thickness THIN - Resultant shell thinning (for stamp only) ESMA - Maximum equivalent stress over thickness (von Mises) ESMI - Minimum equivalent stress over thickness (von Mises) EPLE - Equivalent plastic strain EPSI - Lower and Upper surface strain tensors SIGM- Lower, Upper, and Middle surface stress tensors

Altair Engineering
Viewing the Results

If the model file option is selected, an ASCII model file is created. You can use this ASCII model file to view the model in HyperMesh. After importing the model file, you can view the results by clicking on the Post page, which contains the Contour and the Transient panels. The results can be viewed as a contour or an assign plot, or as a transient animation.
How do I... Import the model file
See also PAM-CRASH Interface Overview Results Translation
Altair Engineering

Reading XY-Plotting Data from the THP (DSY) File

External readers, hgthp.exe and hgdaisy.exe, no longer require a license for ESI DSYLIB. These readers can also read result files (.DSY and .THP) generated by PAM-CRASH 2G. The following entities are supported: In PAM 2000, the PAM-CRASH and PAM-SAFE options For solid elements, only the first seven variables of table A in the PAM 2000 Notes Manual, Plot Output 5, (output qualifiers SXYZ and EPLE) For shell and membrane elements, only the first fourteen variables of table A in the PAM 2000 Notes Manual, Plot Output 7, (output qualifiers MXYZ to STRA) New reader, hgdaisy, can read dsy files The following entities are not supported: In PAM 2000, the PAM-STAMP option
See also PAM-CRASH Interface Overview

Altair Engineering
hgthp.exe
hgthp external reader reads PAM-CRASH THP files (time history files generated by the solver) into HyperGraph. It can also be run from command prompt for converting PAM-CRASH THP files into Altair binary files (abf). In addition this reader can also read ASCII files generated by exporting curves from PAMVIEW. An ESI license is not required for this reader. Usage Running from the command prompt Running in HyperGraph thpfile outfile By default this reader is registered. If it is not, register it before reading THP files. It is located in HWDIR\externalreaders\bin\$PLATFORM\plot. When the reader is registered, you can read THP files or PAMVIEW ASCII files directly into HyperGraph.
The following entities are supported: In PAM 2000, the PAM-CRASH and PAM-SAFE options For solid elements, only the first seven variables of table A in the PAM 2000 Notes Manual, Plot Output 5, (output qualifiers SXYZ and EPLE) For shell and membrane elements, only the first fourteen variables of table A in the PAM 2000 Notes Manual, Plot Output 7, (output qualifiers MXYZ to STRA) For beam and bar elements, only the first fourteen variables of table A in the PAM 2000 Notes Manual, Plot Output 13, (output qualifiers FAXI to RTN2) Results for nodal time histories, transmission sections, airbags, airbag chambers, airbag walls, materials, contacts, and rigid walls are also supported.
The following entities are not supported: In PAM 2000, the PAM-STAMP option
Altair Engineering

hgdaisy.exe
The hgdaisy external reader reads PAM-CRASH DSY files (result files generated by the solver) into HyperGraph. It can also be run from the command prompt for converting PAM-CRASH DSY files into Altair binary files (.abf). An ESI license is not required for this reader.
Usage Running from the command prompt Running in HyperGraph hgdaisy dsyfile outfile
By default this reader is registered. If it is not, register it before reading DSY files. It is located in HWDIR\externalreaders\bin\$PLATFORM\plot. When the reader is registered, you can read DSY files directly into HyperGraph.
For NODES the following results are supported: Displacements Velocities Accelerations For BEAMS and BARS the following results are supported: FAXI-Axial force FSSH-Transverse S Shear force FTSH-Transverse T shear force MTOR-Torsion moment MSN1-S moment at n1 MTN1-T moment at n1 MSN2-S moment at n2 MTN2-T moment at n2 For SHELLS the following results are supported: MXX- Local bending moment about x-axis MYY- Local bending moment about y-axis MXY- Local twisting moment in xy plane EPMA- Maximum plastic strain over thickness

Altair Engineering
EPMI- Minimum plastic strain over thickness NXX- Local membrane stress resultant in x-direction NYY- Local membrane stress resultant in y-direction NXY- Local in-plane shear membrane stress resultant THIC-Resultant shell thickness For SOLIDS the following results are supported: SXX-Stress in X-direction SYY-Stress in Y-direction SZZ-Stress in Z-direction SXY-Shear stress in XY-direction SYZ-Shear stress in YZ-direction SZX-Shear stress in ZX-direction EPLE-Equivalent plastic strain For TOOLS the following results are supported: THIC- Resultant shell thickness Note:: Stamp options are not currently supported.
Altair Engineering

PAM-CRASH 2G Results Translation

hmpam no longer requires a license for ESI DSYLIB. hmpam translates information from a PAM-CRASH 2G results file (.DSY file) to a HyperMesh binary results file or to a Hyper3D (.h3d) file. The syntax to run the translator is: hmpam [-h3d] [arguments] <input file> <output file> [model file] [-options<Filename>] If the -h3d option is selected, the output file is written in the h3d format and contains model data and results in one file. The selection of the option [model file] is not allowed in this case. hmpam can also translate a model from a PAM-CRASH 2G THP file. In this case, only the model is output (no results). hmpam can also read dsy/thp files from PAM-CRASH 2003/2004 version. The option [-options<Filename>] can be repeated, but it must be used as the last option. [arguments] can be any of the following: Flag -d -v -a -sxx -syy -szz -sxy -syz -szx -3S1 -3S2 -3S3 -mxx Meaning Displacements Velocities Accelerations SXX SYY SZZ SXY SYZ SZX Minimum Principal Stress 3-D (for solids only) Maximum Principal Stress 3-D (for solids only) Second Principal Stress 3-D (for solids only) Local bending moment about r-axis

Altair Engineering
Flag -myy -mxy -m1 -m2 -nxx -nyy -nxy -n1 -n2 -eple -epma -epmi -epsi -sigm -thic -thin -esma -esmi -faxi -fssh -ftsh -mtor
Meaning Local bending moment about s-axis Local twist bending moment Maximum Principal bending moment Minimum Principal bending moment Local membrane stress resultant in r-direction Local membrane stress resultant in s-direction Local in-plane shear membrane stress resultant Maximum Principal membrane stress resultant Minimum Principal membrane stress resultant Equivalent Plastic Strain Maximum plastic strain over thickness Minimum plastic strain over thickness Lower and upper surface strain tensors Lower and upper and middle surface stress tensors Resultant Shell Thickness Resultant Shell Thinning Maximum equivalent stress over thickness Minimum equivalent stress over thickness Force in local R-direction Force in local S-direction Force in local T-direction Flexion bending moment about local u-direction
Altair Engineering

Flag -msn1 -mtn1 -msn2 -mtn2 -stepN -disk -file -options
Meaning Directional dependency function for flexion moment Torsion bending moment about local T-direction Resultant damping moment Resultant friction moment Step increment N, where N is a positive integer (default N=1) Translation is performed on disk Scratch file name [Filename] gives the filename for the options file. Syntax is described below. Outputs file to an H3D file instead of an hmresults file. The file includes model and results information that was translated. The model must contain geometry for it to be output to an H3D file.
-h3d
The following options can also be used: Flag -disk -size -file -u Meaning Translation is performed on disk (default off) Number of entities (10000 default) Scratch file name (default off) Usage, gives this help
The following parameters are also available when the results translation is not performed on the analysis machine. You may need to specify one of these parameters to indicate where the analysis result file was created. Parameter -cray Analysis File Created On Cray

Altair Engineering
-dec -decalpha -hp -ibm -pc -sgi -sun
Dec 5000 Dec Alpha Hewlett Packard IBM RS\6000 PC SGI Sun
The supported results include the following: nodal Displacements Velocities Accelerations
bricks Sigma - xx Sigma - yy Sigma - zz Sigma - xy Sigma - yz Sigma - zx Minimum Principal Stresss 3-D Maximum Principal Stress 3-D Second Principal Stress 3-D EPLE: Equivalent Plastic Strain
beams (the definitions of the following variables depend on the material type) FAXI FSSH
Altair Engineering

FTSH MTOR MSN1 MTN1 MSN2 MTN2 DAXI RTOR RSN1 RTN1 RSN2 RTN2
tools Thickness
shells MXX - Local bending moment about r-axis MYY - Local bending moment about s-axis MXY - Local twist bending moment M1 - Maximum Principal bending moment M2 - Minimum Principal bending moment NXX - Local membrane stress resultant in r-direction NYY - Local membrane stress resultant in s-direction NXY - Local in-plane shear membrane stress resultant N1 - Maximum Principal membrane stress resultant N2 - Minimum. Principal membrane stress resultant EPMA - Maximum plastic strain over thickness EPMI - Minimum plastic strain over thickness THIC - Resultant shell thickness THIN - Resultant shell thinning (for stamp only)

Altair Engineering
ESMA - Maximum equivalent stress over thickness (von Mises) ESMI - Minimum equivalent stress over thickness (von Mises) EPLE - Equivalent plastic strain EPSI - Lower and Upper surface strain tensors SIGM- Lower, Upper, and Middle surface stress tensors
See also Selection of components and timesteps
Altair Engineering

Viewing the Results

If the model file option is selected while translating results using hmpam translator, an ASCII model file is also created. You can use this ASCII model file to view the model in HyperMesh. After importing the model file, you can view the results by clicking on the Post page, which contains the Contour and the Transient panels. The results can be viewed as a contour or an assign plot, or as a transient animation.
How do I... Import the model file
See also PAM-CRASH 2G Interface Overview Results Translation

Altair Engineering
Reading XY-Plotting Data from the THP (DSY) File

External readers, hgthp.exe and hgdaisy.exe, no longer require a license for ESI DSYLIB. The following entities are supported: PAM-CRASH 2G and PAM-SAFE options For solid elements, only the first seven variables of table A in the PAM2G Notes Manual, Plot Output 5, (output qualifiers SXYZ and EPLE) For shell and membrane elements, only the first 14 variables of table A in the PAM2G Notes Manual, Plot Output 7, (output qualifiers MXYZ to STRA) Hgthp and hgdaisy readers can also read result files from PAM-CRASH 2003/2004 version. The following entities are not supported: PAM-STAMP option
See also PAM-CRASH 2G Interface Overview
Altair Engineering

hgthp.exe
The hgdaisy external reader reads PAM-CRASH 2G DSY files (result files generated by the solver) into HyperGraph. You can also run it from the command prompt to convert PAM-CRASH 2G DSY files into Altair binary files (.abf). An ESI license is not required for this reader. Usage Running from the command prompt Running in HyperGraph hgdaisy dsyfile outfile
By default, this reader is registered. If it is not, register it before reading DSY files. It is located in HWDIR\externalreaders\bin\$PLAFORM\plot. When the reader is registered, you can read DSY files directly into HyperGraph.
For NODES, the following results are supported: Displacements Velocities Accelerations
For BEAMS and BARS, the following results are supported: FAXI-Axial force FSSH-Transverse S Shear force FTSH-Transverse T shear force MTOR-Torsion moment MSN1-S moment at n1 MTN1-T moment at n1 MSN2-S moment at n2 MTN2-T moment at n2
For SHELLS, the following results are supported: MXX- Local bending moment about x-axis MYY- Local bending moment about y-axis MXY- Local twisting moment in xy plane

Altair Engineering
EPMA- Maximum plastic strain over thickness EPMI- Minimum plastic strain over thickness NXX- Local membrane stress resultant in x-direction NYY- Local membrane stress resultant in y-direction NXY- Local in-plane shear membrane stress resultant THIC-Resultant shell thickness
For SOLIDS, the following results are supported: SXX-Stress in X-direction SYY-Stress in Y-direction SZZ-Stress in Z-direction SXY-Shear stress in XY-direction SYZ-Shear stress in YZ-direction SZX-Shear stress in ZX-direction EPLE-Equivalent plastic strain
For TOOLS, the following results are supported THIC- Resultant shell thickness
Note:
Stamp options are not currently supported.
Altair Engineering

hgdaisy.exe
The hgdaisy external reader reads PAM-CRASH 2G DSY files (result files generated by the solver) into HyperGraph. You can also run it from the command prompt to convert PAM-CRASH 2G DSY files into Altair binary files (.abf). An ESI license is not required for this reader. Usage Running from the command prompt Running in HyperGraph hgdaisy dsyfile outfile
By default, this reader is registered. If it is not, register it before reading DSY files. It is located in HWDIR\externalreaders\bin\$PLAFORM\plot. When the reader is registered, you can read DSY files directly into HyperGraph.
For NODES, the following results are supported: Displacements Velocities Accelerations
For BEAMS and BARS, the following results are supported: FAXI-Axial force FSSH-Transverse S Shear force FTSH-Transverse T shear force MTOR-Torsion moment MSN1-S moment at n1 MTN1-T moment at n1 MSN2-S moment at n2 MTN2-T moment at n2
For SHELLS, the following results are supported: MXX- Local bending moment about x-axis MYY- Local bending moment about y-axis MXY- Local twisting moment in xy plane

Altair Engineering
EPMA- Maximum plastic strain over thickness EPMI- Minimum plastic strain over thickness NXX- Local membrane stress resultant in x-direction NYY- Local membrane stress resultant in y-direction NXY- Local in-plane shear membrane stress resultant THIC-Resultant shell thickness
For SOLIDS, the following results are supported: SXX-Stress in X-direction SYY-Stress in Y-direction SZZ-Stress in Z-direction SXY-Shear stress in XY-direction SYZ-Shear stress in YZ-direction SZX-Shear stress in ZX-direction EPLE-Equivalent plastic strain
For TOOLS, the following results are supported THIC- Resultant shell thickness
Note:
Stamp options are not currently supported.
Altair Engineering

PERMAS Results Translation

Because PERMAS can write out a HyperView .h3d file, there is no need to perform result translation in HyperMesh for PERMAS analyses. Refer to the HyperView online help for more information about postprocessing.

Altair Engineering
RADIOSS (Fixed Format) Results Translation

Results translation is the process of translating data contained in a results file into a HyperMesh binary results database. HyperMesh contains an external results translator for each of the supported analysis codes. The external results translator reads data from a solver results file and writes a HyperMesh binary results file. Results translation is performed at the operating system prompt, outside of HyperMesh. The HyperMesh results translators have a UNIX-style interface. This interface allows the translator to use features found in the UNIX and MS-DOS operating systems. You can start a results translator by two methods: through the Solver panel in HyperMesh or at a command prompt. To start a translator in HyperMesh, click solver from the Checks menu to open the Solver panel. Input values in the fields and click solve to start the translator. To start a translator at a command prompt, use the following syntax: <HyperMesh translator> [arguments] <inputfile> <outputfile> <modelfile> Where: <HyperMesh translator> <arguments> The name of the HyperMesh translator to run. A list of arguments that modify the execution of the translator. This list is specific to each of the translators. For a list of the available arguments, type in the translator name with the -u option. The file containing the results in the analysis code format. The file containing the results in HyperMesh format. The file that is created and contains the model found in the results database. This feature is available on some of the HyperMesh translators. To find those translators, use the -u option.
<inputfile> <outputfile> <modelfile>
If the input filename and output filename are not specified, the translator translates the results file from standard input to standard output. This is useful when the results file to be translated is compressed. You can uncompress the results file and send it to the translator, which outputs the results into a file. This is illustrated below: filepress run1.prs | hmnast > run1.res
Other Conversion Tools

There are two additional conversion tools available in the following location in the HyperWorks installation directory: \io\translators\bin\WIN32\
Altair Engineering

hmresdmp.exe converts an existing HyperMesh binary .res file into ASCII data hmgenres.exe converts a basic ASCII-formatted results file into a binary .res file. Refer to these tools online help topics for more information.
See also Mass Calculation Output Translation Standard Arguments hmgenres hmresdmp

Altair Engineering
Analysis Results Files

HyperMesh does not read analysis results files directly. External translators are provided to convert the analysis-specific results into HyperMesh results format. You can also create your own specialized results translators with the tools provided. The following table lists the supported analysis code results files and their corresponding results translators: Analysis Code Analysis Filenames or Extensions .fil, .fin .rst, .rth d3plot prefix00 .pch Output2, .op2 .pch .dsy FILE12 prefix.D00 any hmasl hmmovie hmnast hmnasto2 hmnastopt hmpam hmansys Results Translator
Abaqus (BINARY OR ASCII) ANSYS LS-DYNA3D RADIOSS (MOVIE BYU) MSC/Nastran (ASCII) MSC/Nastran (BINARY) MSC/Nastran (SOL 200) PAMCRASH ANSYS RADIOSS GENERIC/USER
hmabaqus hmansys
Note:
Results translators can be used in HyperMesh or at the command line.
Altair Engineering

RADIOSS (Bulk Data Format) Results Translation

RADIOSS (Bulk Data), OptiStruct can output HyperMesh binary results file directly when the HyperMesh output format is chosen. RADIOSS (Bulk Data), OptiStruct can also output results in the Nastran punch (.pch) and output2 (.op2) formats. These results can be translated to the HyperMesh results format using the hmnast and hmnasto2 translators, respectively.
See also RADIOSS (Bulk Data), OptiStruct Interface

Altair Engineering
Specifying the Results File

In order to perform post-processing functions, you must first specify the name and location of the results database. There are two ways to select a results file: Click File > Load Results File icon and select the .res file. In the Global panel, for results file:, enter the path and name of the results file or click browse... to select a file using the browser.
Altair Engineering

Creating Deformed Geometry Plots

The Deformed panel allows you to display the deformed geometry of your model statically, in either wire frame or hidden line mode. The selected simulation must have a data type in it that contains nodal displacement records. It is from the data contained with the nodal displacement records that allows the calculation of the deformed geometry of the structure.

Altair Engineering
Creating Animations
The animation functions allow you to view your model structure in motion. The three types of animation include linear, modal, and transient. Linear Linear animation creates and displays an animation sequence that starts with the original position of the structure and ends with the fully deformed position of the structure. An appropriate number of frames are linearly interpolated between the first and the last positions. Linear animation is usually selected when results are from a static analysis. Linear animation sequences are generated in the Deformed panel. Modal animation creates and displays an animation sequence that starts and ends with the original position of the structure. The deforming frames are calculated based on a sinusoidal function. Modal animation is most useful for displaying mode shapes. Modal animation sequences are generated in the Deformed panel. Transient animation displays the structure in its timestep positions as calculated by the analysis code. Transient animation is used to animate the transient response of a structure. Transient animation sequences are generated in the Transient panel.
Modal
Transient
The selected simulations must include a data type that contains nodal displacement records in order to create an animation sequence. HyperMesh calculates the deformed geometry of the structure from the data contained within the nodal displacement records. For linear and modal animation, HyperMesh uses only one simulation and this simulation must include a data type that contains nodal displacement records. For transient animation, HyperMesh uses a range of simulations. In this case, each of the simulations used in the animation sequence must include a data type that contains nodal displacement records.
Altair Engineering

Creating Vector Plots

A vector plot displays the model with a vector at each node that has a result-based direction and magnitude. Vector plots are used to determine the direction of movement and allow you to verify the location of the center of rotation of a model. See the Vector Plot panel for more information.

Altair Engineering
Creating Contour Plots

The contour function in the Contour panel generates color bands on a model, based on the values found in the results file. The bands of color are created by calculating a value for each node in the model and then interpolating across each element. The results file must include a simulation that contains one of the three forms of data types. Each data type is handled differently when it is used to generate a contour plot. When a contour function is performed, the objective is to take all of the results and place them at the nodes of the elements. In order to accomplish this, HyperMesh may have to average results before it can display the contour plot. nodal values and displacements The results are stored at the nodes. HyperMesh can create the contour plot without modifying any of the values in the results file. The values are located at the centroid of the element. HyperMesh averages the centroidal element values to the nodes of the elements. You should be aware that averaging is taking place when element centroid values are used to create a contour plot.
element values
Altair Engineering

Creating Assigned Plots

The assign function in the Contour panel assigns a color to each element in the model, based on the values in the results file. The elements are then displayed in the solid color assigned to them. This allows you to display elements that have values within a specified range. The results file must include a simulation that contains one of the three forms of data types. Each data type is handled differently when it is used to generate a contour plot. When the assign function is performed, the objective is to take all of the results and place them at the centroid of the elements. In order to accomplish this, HyperMesh may have to average results before it can display the assigned plot. element values The results are already stored at the centroid of the element, so no further calculations are required. HyperMesh averages the results at the nodes to the centroid of the elements. For each element, this is accomplished by adding the results at each node and dividing by the number of nodes on the element. You should be aware that averaging is taking place when nodal values or nodal displacements are being used to create an assigned plot.
nodal values and displacements

Altair Engineering
Adding Plot Identification

After you create a results-based plot, you can add titles, modify the colors used in the legend, and relocate the legend and the descriptor. Temporary titles can be added to each type of plot by entering a title in the title = field in the Contour panel. After you enter the title and create the plot, the temporary title is displayed on the upper left side of the screen. HyperMesh creates the "descriptor" in order to display the simulation and data type that were used to create the plot. By default, the descriptor is located in the upper left-hand corner of the plot above the legend. To modify the descriptor, click within the descriptor to access the Title Edit panel, click color to change the color of the text of the descriptor, click font and select the size font you want to use in the descriptor. HyperMesh plots a legend if the results-based plot created requires it. To modify a legend, click within the displayed legend to access the Legend Edit panel. Functions on this panel allow you to move the legend to a different location on the screen, change the color of the text in the legend, reverse the colors of the legend, change the font size, and also change the colors used in the legend that correspond to the model.
Altair Engineering

Inspecting the Results

A contour or assigned plot provides a fast, convenient way of viewing the results of a large number of elements. When you want to determine the actual value that an analysis code has calculated for a node or element, you can select the node or element after the results-based plot has been created. The ID, simulation and data type, and value of the node or element are displayed in the menu area.

Altair Engineering
Free Body Diagrams

Location: Results menu, Free Body Diagram sub-menu (to access the tools) Tool menu (to access the Set Browser only) Tab Area (for the tools themselves)
You can create or edit Free Body Diagrams (FBD) using several tools that display in the tab area. Each FBD tool displays on a separate tab, which opens when you activate that tool. Free Body Diagram (FBD) utilities facilitate the extraction and post-processing of Grid Point Force (GPFORCE) results. FBD extractions are typically utilized for breakout and/or sub-modeling analysis schemes, where balanced "free body" sub-cases are extracted from a coarse grid model and applied to a fine grid sub-model for eventual optimization and/or analysis. FBD is also used to extract cross-sectional resultant forces and moments (typically at the centroid of a cross-section) for use in traditional strength calculations.
This coarse grid model is typical for FBD extractions.
Typical FBD Forces output on a w ing rib
Typical Result Force and Moment output on a floor beam
Altair Engineering

Each tool has a separate entry in the menu. Click the links below for details on the use of each tool: Displacements Forces Cross-section manager Resultant Force and Moment Results Manager Export Manager

Altair Engineering
FBD Displacements
Location: Post menu, Free Body Diagram sub-menu (to access the tool). Tab Area (for the tool itself)
The FBD Displacements utility extracts displacement data for user defined node set(s), and is useful for doing breakout modeling within a sub-modeling scheme. After you define an element set with an associated node set, all appropriate displacements and rotations are extracted. Results can be output to load collectors for graphical review, a text summary table, and a formatted .csv file which can be loaded into traditional spreadsheet software packages.
Altair Engineering

To extract displacement data for a user-defined node set

1. From the Post pull-down menu, select Free Body, then Displacements. The FBD Displacements tab displays in the tab area. 2. Use the .op2/.odb file: field to specify the full path and filename of the results file containing the displacement output for the current model. Clicking on the folder icon opens the standard file selection dialog window for browsing files. Once an results file is selected, loadstep names and IDs with displacement output are saved with the rest of the HyperMesh database for use with all FBD utilities. If a new results file is required, or if the original results file changes, you must load the new results file into the database (overwriting the previously selected one). 3. Select a loadstep. This lets you specify from which loadstep(s) to extract displacement information. Only loadsteps with displacement results from the currently selected results file display for selection. You can select multiple loadsteps by ctrl-clicking or shift-clicking. Filter buttons allow for additional selection control, including a name filter that uses standard HyperMesh filtering syntax. The loadstep display can be switched between ID and Name (ID). The ID option lists the loadsteps as "SUB-CASE #". The Name (ID) option lists the loadstep as "SUBTITLE - LABEL(ID)". If no SUBTITLE exists, only the LABEL is used. See the OptiStruct online reference guide for more information regarding SUBTITLE and LABEL loadstep information cards. 4. Select entities. The entity selection section allows you to select and/or create the appropriate entities required to execute the FBD Displacements utility. There are several options: The Element Set selector defines the elements that contain the nodes at which displacement data will be extracted. The Set Browser utility on the Tools menu can be used to create the necessary element sets. The Node Set selector defines the nodes at which displacement data will be extracted. Only the nodes contained within the selected node set will be part of the extraction. If a node set is not selected, then all nodes within the element set are used. The Auto find interface nodes option automatically finds the nodes attached to elements that are not contained within the currently selected element set. This procedure selects the nodes interfacing with the remainder of the structure. You will be prompted to give the newly created node set a name. Additional nodes may be added to the node set once it is created by clicking the Node Set selector and picking additional nodes. The Show model checkbox is a graphical review option that, when checked, automatically displays the entire model in transparency mode and highlights the currently selected element and node sets. This functionality allows you to verify which element and node sets are currently selected. 5. Choose Output options: The Output options section contains various options to review and display results of FBD Displacement extractions. The Coordinate System selector determines the coordinate system used to display the nodal

Altair Engineering
coordinates (x,y,z) in the summary table and .csv file output options. Displacement data (Ux, Uy, ) is always output in the system that the results are stored with in the results file format. Results coordinate system transformations are not performed on displacement data. The FBD Displacement utility extracts and applies the displacement and rotation results from the results file in the output coordinate system without any further coordinate system transformations. It is assumed that the output coordinate system assigned to each node in the HyperMesh database matches that used to run the analysis and generate the results file. Output coordinate systems are defined in HyperMesh by accessing the Systems panel. On the Setup menu, click Coordinate Systems, and toggle to the assign sub-panel, select the required nodes and a coordinate system, and click Set Analysis. In OptiStruct and Nastran this operation sets the CD field on the GRID card (s). See the OptiStruct online reference guide for more information regarding the GRID bulk data card. If the output coordinate systems for each node in the HyperMesh database does not match those used to run the analysis then the extracted values will be incorrect. Situations when this behavior could occur include modification of nodal output system within HyperMesh without rerunning the analysis and/or loading a results file that does not match the currently loaded model. If a coordinate system is not specified, the HyperMesh "base" system is used by default. The Zero Tolerance entry defines the cut-off point below which a result quantity is considered zero. All calculations are done with float point precision and the zero tolerance value is only used for controlling the output of results to the various formats. The option helps to eliminate "relatively small" values from being output to the result formats. To maintain float precision the default is set to 1.0e-6, otherwise modify the value as desired. The Create Load Collectors option will extract the specified displacement data and display it in organized load collectors within HyperMesh for graphical visualization within the model window5. A single load collector, for the current element and node set, is created for each loadstep. The load collector name format is FBDD_E(#)_N(#)_S(#)_Disp. For example, FBDD_E(1)_N(1)_S(1)_Disp would be created for element set 1, node set 1 and loadstep 1. The loads in this load collector are created with the SPC load type. This collector can be referenced as the SPC in the loadstep panel. The Create SPCD option will additionally create a load collector with the name "FBDD_E(#)_N(#)_S (#)_SPCD". Loads in this collector are created with the SPCD load type. This collector can be referenced as the LOAD in the loadstep panel. The Color option allows you to choose a color for all created load collectors. This color can be modified later using either the HyperMesh interface or the FBD Results Manager utility. The Show summary table option outputs the results to a popup window for instant review. The table contains information about the loadsteps, element and node set(s), and detailed displacement data at each node. A sample window with partial output is shown below.
Altair Engineering

The Create .csv file option creates a .csv file that contains the same information as the summary table, but in a comma-separated file. You may select a new file or an existing file. If an existing file is selected there are several items to note: If the data you are extracting already exists in the file (based on element set, node set and loadstep IDs), the existing block will be overwritten with the new data. If it does not exist, it will be appended to the end of the file. In any case, you will be warned that the file already exists and asked if you want to replace it. Selecting yes will not overwrite the file; it will append/replace the data.

Altair Engineering
FBD Forces
Location: Results menu, Free Body Diagram sub-menu (to access the tool). Tab Area (for the tool itself)
The FBD Forces utility extracts grid point force (GPFORCE) data (including forces and moments) for a userdefined element set, and is useful for doing breakout modeling within a sub-modeling scheme. Results can be output to load collectors for graphical review, a text summary table, and/or a formatted Comma-Separated Values (.csv) file which can be loaded into traditional spreadsheet software packages. The FBD Forces utility is broken down into three major sections, each of which corresponds with the process order of using the tool.
Altair Engineering

To select a results file

Click on the folder icon inside of the op2/.odb file field. This opens the standard file selection dialog window; use this to browse to and select the desired results file. The op2/.odb file field accepts the full path and filename of the results file that contains the GPFORCE output for the current model. Once youve selected an results file, loadstep names and IDs with GPFORCE output are saved to the database for use with all FBD utilities. The loadstep name and ID information is retained within the HyperMesh database once saved. If a new results file is required (or if the original results file changes) you must load the new results file into the database, overwriting the previously selected.

Altair Engineering
To select a sub-case
The loadstep section lets you specify from which loadstep(s) to extract GPFORCE information. Loadsteps with GPFORCE results from the currently selected.results file are displayed for selection only. Multiple loadsteps can be selected via Ctrl-click or Shift-click functionality. Filter buttons allow for additional selection control as shown including a name filter that uses standard filtering syntax. The loadstep list can be switched between ID and Name (ID). The ID option lists the loadsteps in the format SUBCASE #. The Name (ID) option lists the loadstep in the format SUBTITLE LABEL (ID). If no SUBTITLE exists, only the LABEL is used. See the OptiStruct online reference guide for more information regarding SUBTITLE and LABEL loadstep information cards.
Altair Engineering

To select entities
1. Use the Element Set selector to define the elements that make up the free body and contain the nodes at which GPFORCE data will be extracted. The Set Browser tool can be used to create the necessary element sets. 2. Use the Result System selector to define the coordinate system into which the grid point force and moment result vectors are transformed and output. If a results system is not specified, the HyperMesh "base" system is used by default. The FBD Forces utility extracts grid point force and moment results from an results file in the output coordinate system in which the solver output these results. HyperMesh assumes that the output coordinate system assigned to each node in the HyperMesh database matches that used to run the analysis and generate the results file. Output coordinate systems are defined in HyperMesh by accessing the Systems panel. On the assign subpanel, select the required nodes and a coordinate system, and click Set Analysis. In OptiStruct and Nastran this operation sets the CD field on the GRID card(s). (See the OptiStruct online reference guide for more information regarding the GRID bulk data card.) If the output coordinate systems for each node in the HyperMesh database do not match those used to run the analysis, the extracted values will be incorrect. This could occur when modifying a nodal output system within HyperMesh without rerunning the analysis and, or when loading a results file that does not match the currently loaded model. In addition, results coming from, or output to, cylindrical or spherical result coordinate systems should be inspected for validity near the origin and along principal axes. 3. Use the Summation Node selector to define the node about which the GPFORCE data is summed for the selected element set. This is useful for verifying free body behavior through zero-sum values for all force and moment components about any node. It is also useful for calculating the result of applied or reaction forces about any node. If a node is not selected, the HyperMesh origin (0,0,0) is used by default. 4. Activate the Show Model checkbox to automatically display the entire model in transparency mode while highlighting the currently selected element set, result system and summation node. This allows you to verify which element sets is currently selected.

Altair Engineering
To specify output options

1. Use the FBD type selector to determine the grid point force and moment data to extract and utilize for FBD calculations for each node in the selected element set. Available options include All Loads, Applied Loads Only, and Reaction Loads Only. All Loads extracts and utilizes all element contribution, applied, SPC, and supported MPC grid point data for FBD calculations on the nodes in the selected element set. Applied Loads Only extracts and utilizes only the applied loads grid point data for FBD calculations on the nodes in the selected element set. Reaction Loads Only extracts and utilizes only SPC and supported MPC grid point data for FBD calculations on nodes in the selected set. MPC force and moment data are properly extracted for the following MPC constraint types: RBE2, RBE3, Rigidlink, RJOINT, RROD, and RBAR. 2. Use the Zero Tolerance entry field to define the cut-off point below which a result quantity is considered zero. All calculations are performed with floating point precision and the zero tolerance value is only used to control the output of results to the various formats. This option helps to prevent relatively small values from being output to the result formats. To maintain floating-point precision the default is set to 1.0e-6; modify the value as desired. 3. Use the Create Load Collectors option to extract the specified grid point data and display it in organized load collectors for visualization in the model window. Multiple load collectors are created one for each force and moment component for each selected loadstep of the current element set. The load collector name format is "FBDF_E(#)_S(#)_(compID)". For example FBDF_E(1)_S(1)_Fx would be created for element set 1, loadstep 1, and component Fx. In addition a load collector with the Nastran/OptiStruct LOAD card is also created, referencing the component force and moment load collectors. This load collector is named "FBDF_E(#)_S(#)_C" and can be referenced in the loadstep panel as the LOAD entry for the various loadstep definitions. The Color option allows you to choose a color for all created load collectors. This color can be modified later using either the interface or the FBD Results Manager utility. The FBD Results Manager can be used to review the load collectors generated from FBD Forces utility. When you save the database, all FBD Forces load collectors are saved to the database. This allows FBD information to be reviewed and utilized in the future without having to rerun the tool. Renumbering element or node sets after running the tool invalidates the link between the load collector names and the associated sets; therefore it is important to avoid renumbering any element or node sets for which FBD result must be retained as load collectors in HyperMesh. 4. To output the results to a popup window for instant review, activate the Show summary table option. The table contains information about the loadsteps, element set(s), and detailed data from the grid point extraction at each node. A sample window with partial output is shown below.
Altair Engineering

5.
Use the Create .csv file option to create a .csv file that contains the same information as the summary table, but in a comma-separated file. You may select a new file or an existing file. If an existing file is selected, it is appended to, and there are several items to note: If the data you are extracting already exists in the file (based on element set, loadstep IDs), the existing block will be overwritten with the new data. If it does not exist, it will be appended to the end of the file. You are asked if you wish to replace the existing file. However, selecting yes will not overwrite the file it will append/replace the data as described above.

Altair Engineering
FBD Cross-section manager

The FBD Cross-section Manager (CSM) utility creates and manages cross-section definitions that are used within the Resultant Force & Moment utility. This utility contains tools for defining cross-sections, which are defined by an element set, node set, summation node, and a local result coordinate system. It also features semi-automatic generation of element and node sets for defining cross-sections. The FBD Cross-section Manager interface has two creation methods available for cross-section definition: manual and (semi-) automatic. The Advanced options section provides the means to semi-automatically create cross-section element and node sets for beam-like structures with regular meshes. This auto-create cross-section capability requires a continuous mesh with rows of nodes (of any orientation) to work properly. The mesh shouldnt have any discontinuities (holes, gaps, etc) and must have identifiable rows of nodes, starting from the selected nodes and progressing along the length of the selected elements.
Altair Engineering

To define a cross-section manually

1. Use the Element Set selector to specify the elements containing the nodes that define the crosssection. The Set Browser can be used to create the necessary element sets. If multiple element sets are selected, each set is added to the table as a separate cross-section definition which can be modified later by selection. 2. Use the Node Set selector to define the nodes in each currently selected element set at which grid point data will be extracted and summed from. Only the nodes contained within the selected node set will be part of the grid point extraction. Use the Set Browser to create the necessary node sets. If multiple node sets are selected for a single element set, HyperMesh adds separate cross-section definitions to the table with the original element set and each selected node set. 3. Use the Summation Node selector to define the node about which the grid point data will be summed. If no node is selected, the utility defaults to "Centroid". This option calculates the nodal averaged centroid of the coordinates of all of the nodes in the node set and creates a temporary node at that location. When using the "Centroid" option, a temporary node is created. If this node is deleted from the model, the loads associated with that node are also deleted. 4. Use the Result System selector to define the coordinate system into which the grid point vector results will be transformed and output. If a results system is not specified, the HyperMesh "base" system is used by default. 5. The Display sections checkbox is a graphical review option that, when checked, displays the element set, node set, result system and summation node which define the cross-section in the graphics display area. Optional: activate the Show model checkbox. This displays the entire model in transparency mode, highlighting the currently selected element set, node set, result system and summation node. This allows you to verify a cross-section definition. 7. Optional: use the filter buttons on the top of the spreadsheet to select which cross-sections are required. Standard Ctrl/Shiftclick functionality can be used to select cross-sections. Selected cross-sections can also be deleted from the database by using the Remove selection button on the right end of the filter buttons.
6.
Comments Each time a cross-section is created, modified, or deleted, the cross-section data is saved to the database. When the database is saved, all cross-section definitions are also saved. Therefore, cross-section definitions only need to be defined once and stored in the database. Cross-Sections can then be accessed from within the Resultant Force and Moment utility, which utilizes the cross-section definitions to perform these

Altair Engineering
calculations. Renumbering element or node sets after running the tool invalidates the link between the cross-section names and the associated sets. Therefore, it is important to avoid renumbering any element or node sets for which cross-sections are to be retained within the database.
Altair Engineering

To define a cross-section automatically

1. 2. Use the Elements selector to choose the elements that define the entire "beam-like" component from which cross-sections will be generated. Use the Nodes selector to pick nodes for the first node set (i.e. first cross-section). These nodes should be at one end of the beam. 3. 4. Optional: activate the Show model checkbox to automatically display the entire model in transparency mode, highlighting the currently selected elements and nodes. Type a prefix for the name of each generated element set into the Element set prefix field. For example, you type in "ESET" each element set will be named ESET [#], where "#" increases with each new set generated. 5. Type a prefix for the name of each generated node set into the Node set prefix field. For example, you type in "NSET" each element set will be named NSET [#], where "#" increases with each new set generated. 6. Type a Numbering offset into the text box. This is the offset value for generated set names. By default, the offset value is zero and HyperMesh generates numbered set names starting with one. If the offset value is set to a value greater than zero, the generated set names are numbered starting from that value. 7. Optional: activate the sets accumulate option This determines whether each progressive set also contains the elements from the previous set, or only the new "row" of elements. If checked, each element set will contain the elements from the previous set.

Altair Engineering
FBD Resultant Force and Moment

The Resultant Force and Moment (RF&M) utility extracts grid point force (GPFORCE) data for user defined cross-sections created via the Cross-section Manager. The Resultant Force and Moment utility generates input data for shear and moment (VMT) diagrams and/ or to perform load-case screening with Potato plots in HyperView. Two utilities available within HyperGraph also interact with data generated from the Resultant Force and Moment utility. Results can be output to load collectors for graphical review, a text summary table, and/or a formatted .csv file which can be loaded into traditional spreadsheet software packages.
Altair Engineering

To select a results file

Use the .op2/.odb file field to specify the full path and filename of the results file containing the desired GPFORCE output for the current model. Clicking on the folder icon opens the standard file selection dialog window for browsing files. When a results file is selected, loadstep names and IDs with GPFORCE output are saved to the database for use with all FBD utilities. The loadstep name and ID information is retained within the database once saved. If a new results file is required, or if the original results file changes, you must load the new results file into the database, overwriting the previously selected.

Altair Engineering
To select a sub-case
Select the desired loadstep(s) from the list in the loadstep section. The loadstep section lets you specify from which loadstep(s) to extract GPFORCE information. Loadsteps with GPFORCE results from the currently selected results file display for selection only. Multiple loadsteps can be selected by Ctrl-clicking and Shift-clicking. The list can be filtered using the buttons provided, including a name filter that uses standard HyperMesh filtering syntax. The loadstep list can be organized by ID or Name (ID). The ID option lists the loadsteps as "SUBCASE #". The Name (ID) option lists the loadstep as "SUBTITLE LABEL (ID)". If no SUBTITLE exists, only the LABEL is used. See the OptiStruct online reference guide for more information regarding SUBTITLEand LABEL loadstep information cards.
Altair Engineering

To select a cross-section
Pick the desired cross-sections from the list in the cross-sections area of the tab. The Cross-sections section lets you specify the cross-sections from which you wish to calculate resultant force and moment results for each selected loadstep. Cross-sections are created using the Cross-section Manager. Multiple cross-sections can be selected by Ctrl-clicking and Shift-clicking. The list can be filtered using the buttons provided, including a name filter that uses standard HyperMesh filtering syntax.

Altair Engineering
To specify output options

The Output Options section contains various options to review and display the results of Resultant Force and Moment extractions.
1.
Use the Coordinate System selector to determine the coordinate system used to output the nodal coordinates (x,y,z) in the summary table, .csv file, and .fbd file output options. Resultant force and moment vector results are always output in the result coordinate system defined for each cross-section. Result coordinate systems for cross-sections are defined using the Cross-section Manager. If a coordinate system is not specified, the HyperMesh "base" system is used by default. The Resultant Force and Moment utility extracts grid point force and moment results from the results file in the output coordinate system in which the solver output these results. It is assumed that the output coordinate system assigned to each node in the database matches that used to run the analysis and generate the results file. Output coordinate systems are defined by accessing the Systems panel. (On the assign subpanel, select the required nodes and a coordinate system, and click Set Analysis. In OptiStruct and Nastran this operation sets the CD field on the GRID cards). If the output coordinate systems for each node in the database do not match those used to run the analysis, the extracted values will be incorrect. This can occur when modifying nodal output system without rerunning the analysis, and/or loading a results file that does not match the currently loaded model. In addition, results coming from or output to cylindrical or spherical result coordinate systems should be inspected for validity near the origin and along principal axes. MPC force and moment data are properly extracted for the following MPC constraint types: RBE2, RBE3, Rigidlink, RJOINT, RROD, RBAR.
2.
Use the Zero Tolerance field to specify the cut-off point below which a result quantity is considered zero. All calculations are done with float point precision and the zero tolerance value is only used to control the output of results to the various formats. The option helps to eliminate relatively small values from being output. To maintain float precision the default is set to 1.0e-6, otherwise modify the value as desired.
3.
Activate the Create Load Collectors checkbox to extract the specified grid point data and display it in organized load collectors for graphical visualization within the model window. Multiple load collectors are created one for each force and moment component for each selected loadstep of the current cross-section, each made up of an element set and node set. The load collector name format is "RF&M_E(#)_N(#)_S(#)_(compID)". For example RF&M_E(1)_N(1)_S(1)_Fx would be created for element set 1, node set 1, loadstep 1, and component Fx. The "Color" option allows you to choose a color for all created load collectors. This color can be modified later using either the interface or the FBD Results Manager. You can also use the FBD Results Manager to review the load collectors generated from the Resultant Force and Moment utility. When the database is saved, all resultant force and moment load collectors are saved in the database. This allows resultant force and moment information to be reviewed and utilized in the future without having to rerun the tool. Renumbering element or node sets after running the tool invalidates the link between the load collector names and the associated sets and therefore it is important to not renumber any element or node sets for which resultant force and moment result are to
Altair Engineering

be retained as load collectors in HyperMesh. 4. Activate the Show summary table option to output the results to a popup window for instant review. The table contains information about the loadsteps and cross-sections, and detailed data from the grid point extraction at each node. 5. Activate the Create .csv file option to create a .csv file containing the same information as the summary table, but in a comma separated file. You may select a new file or an existing file. If an existing file is selected, it is appended to. 6. Activate the Create .fbd file option to create a file that can be read into HyperGraph using the "Shear and Moment Plot" and "Potato Plot" utilities. You may select a new file or an existing file. Comments When saving over existing .csv or .fbd file, there are several items to note: If the data you are extracting already exists in the file (based on element set, loadstep IDs), the existing block will be overwritten with the new data. If it does not exist, it will be appended to the end of the file. You are asked if you wish to replace the existing file. However, selecting yes will not overwrite the file; it will append/replace the data into the file as described above. Two utilities available within HyperGraph interact with data generated from the Resultant Force and Moment utility: Shear and Moment Diagrams (VMT Plots) and Potato Plot. These utilities are accessed from the Free Body Diagrams item within the HyperGraph Utilities menu.

Altair Engineering
FBD Results Manager

Use the FBD Results Manager to graphically review and manage the load collectors generated from all FBD and Resultant Force and Moment utilities.
Altair Engineering

To review and manage FBD load collectors

1. Select one or more Element sets. The Entity selection section allows you to select the element set for which to review FBD, Displacement, or Resultant Force and Moment load collector output. You must choose an existing element set for which you wish to the review the FBD, Displacement, and Resultant Force and Moment load collector output. The optional Show model checkbox, when checked, displays the entire model in transparency mode and highlights the currently selected element set. 2. Pick the desired Results type . The Results selection section lets you select the FBD result type to review. Valid types include FBD Displacements, FBD Forces (All Loads), FBD Forces (Applied Loads), FBD Forces (Reaction Loads), and Resultant Force and Moment. Selecting an FBD result type scans the HyperMesh database and updates the loadsteps list with available loadsteps for the currently selected element set and result type. 3. Select the desired loadsteps by clicking on them. Multiple loadsteps can be selected using standard Ctrl/Shift click functionality. Filter buttons allow for additional selection control as shown including a name filter that uses standard HyperMesh filtering syntax. For FBD Displacements and Resultant Force and Moment Result types, the Results selection interface is modified to include a Node sets selector. This selector lists all of the node sets associated with the currently selected element set and loadsteps. If multiple loadsteps are selected, only the node sets that are common to all of them will be listed. 4. Specify any desired Display options: The Display options section allows you to decide which force and moment components display in the graphics area for the current selection. The Fx, Fy, Fz checkboxes determine which component/resultant vectors display when you click the Accept button. Grayed-out checkboxes indicate force and moment components or results that cant display for the currently selected element set/loadstep/node sets. These checkboxes are disabled for the FBD Displacements Result type. The Update load collector color option will recolor the load collectors associated with the current selection to the color selected in the Color option. Click the Color box to pick a different color, if desired. 5. Click one of the command buttons at the bottom of the tab: The Accept button displays the selected result vectors on in the graphics area. The Delete button deletes the load collectors associated with the current selection. A popup warning tells you what will be deleted and requires you to confirm the deletion. The Reset button clears the graphics area of all result vectors and resets all of the FBD Results Manager entry fields.

Altair Engineering
The Close button closes the FBD Results Manager, removing it from the tab area without displaying any results in the graphics area.
Altair Engineering

FBD Export Manager

The FBD Export Manager exports FBD, Displacement, and/or Resultant Force and Moment load collectors generated by other FBD utilities. After export, the exported data can be used for breakout modeling within a sub-modeling scheme.

Altair Engineering
To export FBD, Displacement, or Resultant Force & Moment collectors

1. 2. 3. Use the Element set selector to specify the set for which you wish to export data. Optional: activate the show model checkbox to display the entire model in transparency mode, highlighting the currently selected element set for review. Choose the results type that you wish to export from the list box. This populates the list of loadsteps. Click the one(s) that you wish to export to highlight them; use <ctrl>-click or <shift>-click to select multiple results. If you choose FBD Displacements or Resultant Force and Moment as the result type , an additional list of node sets displays. Select the desired node sets in the same fashion as the loadsteps. 4. 5. Click add to export to add the highlighted results to the export batch. Specify Export options: If you wish to create loadsteps upon export, click the Create appropriate loadsteps checkbox and then click the open-folder button in the Output file text box. This opens a standard file browser window that you can use to browse to the desired destination directory and either select an existing file, or type in a name for a new one. This option will also create SUBTITLE and LABEL cards if they are available from the loadstep information within the currently selected results file. In addition, the Results type affects how loadsteps are created: For FBD Forces All Loads; a SUBCASE will be created with LOAD = assigned to the "FBDF_E(#)_S (#)_C" load collector which references the LOAD card pointing to each component "FBDF_E(#)_S(#)_ (compID)" load collector for the selected loadstep. For FBD Displacements; a SUBCASE will be created with SPC = assigned to the "FBDD_E(#)_N(#)_S (#)_Disp" load collector for the selected loadstep. If the SPCD option was enabled when creating FBD Displacement loads, LOAD = will also be assigned to the "FBDD_E(#)_N(#)_S(#)_SPCD" load collector for the selected loadstep. If multiple node sets are selected for export the following will occur: An SPCADD load collector will be created and the appropriate "FBDD_E(#)_N(#)_S(#)_Disp" load collectors will be assigned to it. The SPC = will reference the newly created SPCADD load collector. If the SPCD option was enabled when creating the FBD Displacement loads, a LOAD load collector will be created and the appropriate "FBDD_E(#)_N(#)_S(#)_SPCD" load collectors will be assigned to it. The LOAD = will reference the newly created LOAD load collector. If FBD Force and FBD Displacement load collectors from the same loadstep are selected for export, you are prompted to select one or the other from which to create the loadstep. 6. Click the appropriate command button at the bottom of the tab: Export executes the export process, meaning that clicking it: Turns off the display of all currently displayed elements,
Altair Engineering

Creates temporary mass elements on the nodes where the selected FBD, Displacement, and/or Resultant Force and Moment loads are displayed, Exports the model with the "displayed" option, Deletes the temporary mass elements from the current model, and Removes unnecessary header information from the output file. Reset clears all of the export criteria so that you can start over. Close closes the tab, removing it from the tab area.

Altair Engineering
FBD Grid Point Force Balance

The Grid Point Force Balance table is the data around which all FBD-Forces and Resultant Force and Moment utility calculations are performed. See the OptiStruct online reference guide for more information regarding GPFORCE option cards. Shown below is a sample model which will be used to demonstrate the grid point force calculations that FBD utilities perform.
This model consists of tw o elements, a fixed support on the left end, and a point load on the right end.
The complete GPFORCE table for the above cantilever beam model is presented below. Note that for any given node within the GPFORCE table, several types of entries are possible depending on the forces acting at that node, including: Applied forces and moments SPC forces and moments MPC forces and moments Element forces and moments from elements attached to the node Total summed values for each node, which in turn must sum to zero for the complete GPFORCE table.
Altair Engineering

Process The FBD Forces and Resultant Force and Moment utilities use element and node set definitions to define what information to extract and sum from the GPFORCE table. This information is then used to produce free bodies and/or resultant force and moments. FBD Forces The FBD Forces utility uses an element set to define the values to extract from the GPFORCE table. The

Altair Engineering
element set serves several purposes: The FBD Forces utility uses an element set to define which values to extract from the GPFORCE table. This serves several purposes: Any nodes in the element set that have Applied loads will have those values extracted. Any nodes in the element set that have SPC loads will have those values extracted. Any nodes in the element set that have MPC loads will have those values extracted. Any nodes in the element set attached to one or more elements not in the element set will have the appropriate element forces extracted. The following example of FBD-Forces extraction uses element 1 from the same 2-element image shown at the beginning of this topic: The element set contains only element 1. Element 1 has nodes 1, 2, 3 and 4. X-Force Node 1 is only attached to element 1 and has an SPC constraint. Since element 1 is in the element set, its force contributions are not considered. From the GPFORCE table, the x-force value that is extracted for node 1 is the SPC force 2.121e+03. Node 2 is only attached to element 1 and has an SPC constraint. Since element 1 is in the element set, its force contributions are not considered. From the GPFORCE table, the x-force value that is extracted for node 2 is the SPC force -2.121e+03. Node 3 is attached to elements 1 and 2. Since element 1 is in the element set, its force contributions are not considered. Since element 2 is not in the element set, its force contributions will be considered. From the GPFORCE table, the x-force value that is extracted for node 3 is the element 2 force -1.085e+03. Node 4 is attached to elements 1 and 2. Since element 1 is in the element set, its force contributions are not considered. Since element 2 is not in the element set, its force contributions will be considered. From the GPFORCE table, the x-force value that is extracted for node 4 is the element 2 force 1.085e+03. These values sum to 0. Y-Force All values are zero in this model. Z-Force Node 1 is only attached to element 1 and has an SPC constraint. Since element 1 is in the element set, its force contributions are not considered. From the GPFORCE table, the x-force value that is extracted for node 1 is the SPC force -4.332e+02. Node 2 is only attached to element 1 and has an SPC constraint. Since element 1 is in the element set, its force contributions are not considered. From the GPFORCE table, the x-force value that is extracted for node 2 is the SPC force -5.668e+02. Node 3 is attached to elements 1 and 2. Since element 1 is in the element set, its force contributions are not considered. Since element 2 is not in the element set, its force contributions will be considered. From the GPFORCE table, the x-force value that is extracted for node 3 is the element 2 force 6.426e+02.
Altair Engineering

Node 4 is attached to elements 1 and 2. Since element 1 is in the element set, its force contributions are not considered. Since element 2 is not in the element set, its force contributions will be considered. From the GPFORCE table, the x-force value that is extracted for node 4 is the element 2 force 3.574e+02. These values sum to 0. X-Moment All values are zero in this model. Y-Moment Node 1 is only attached to element 1 and has an SPC constraint. Since element 1 is in the element set, its moment contributions are not considered. From the GPFORCE table, the y-moment value that is extracted for node 1 is the SPC moment 2.370e+01. Node 2 is only attached to element 1 and has an SPC constraint. Since element 1 is in the element set, its moment contributions are not considered. From the GPFORCE table, the y-moment value that is extracted for node 2 is the SPC moment 2.277e+01. Node 3 is attached to elements 1 and 2. Since element 1 is in the element set, its moment contributions are not considered. Since element 2 is not in the element set, its moment contributions will be considered. From the GPFORCE table, the y-moment value that is extracted for node 3 is the element 2 moment -8.871e+00. Node 4 is attached to elements 1 and 2. Since element 1 is in the element set, its moment contributions are not considered. Since element 2 is not in the element set, its moment contributions will be considered. From the GPFORCE table, the y-moment value that is extracted for node 4 is the element 2 moment -1.024e+01. Additionally, the cross-product of all the forces about the Y axis need to be considered. Selecting node 1 as the summation node (any node in the model can be selected) and performing rXF (all element edge lengths are 0.166) the following is obtained: Node 1 Node 2 Node 3 Node 4 no additional rXF contributions since it is the sum point -0.166*Fx + 0*Fz = -0.166*-2.121e+03 + 0*-2.121e+03 = 3.535e+02 0*Fx + -0.166*Fz = 0*-1.085e+03 + -0.166*6.426e+02 = -1.071e+02 -0.166*Fx + -0.166*Fz = -0.166*1.085e+03 + -0.166*3.547e+02 = -2.400e+02
These values sum to about 0. Since there are only 4 significant digits in the GPFORCE table, the precision of the calculated moments are compromised. In the actual FBD utilities, the full result and machine precisions are used. Z-Moment All values are zero in this model. Here is a sample output table from the FBD Forces utility for element 1 (element set) with node 1 used as the summation point:

Altair Engineering
Resultant Force and Moment The Resultant Force and Moment utility uses an element set and a node set (cross-section definition) define the values to extract from the GPFORCE table. The cross-section definition serves several purposes: All nodes in the node set must be attached to one or more elements in the element set. All nodes in the node set that have Applied loads will be extracted and utilized in Resultant Force and Moment calculations. All nodes in the node set that have SPC loads will be extracted and utilized in Resultant Force and Moment calculations. All nodes in the node set that have MPC loads will be extracted and utilized in Resultant Force and Moment calculations. For all nodes in the node set, Element contributions from only those elements which are not a part of the element set of the cross-section definition will be extracted and utilized in the Resultant Force and Moment calculations. The following example of Resultant Force and Moment extraction uses element 1 and nodes 3 & 4 from the same example as the previous FBD Forces. The node set contains nodes 3 and 4; the element set contains only element 1. X-Force: Node 3 is attached to elements 1 and 2. Since element 1 is in the element set, its force contributions are not considered. Since element 2 is not in the element set, its force contributions will be considered. From the GPFORCE table, the x-force value that is extracted for node 3 is the element 2 force -1.085e+03. Node 4 is attached to elements 1 and 2. Since element 1 is in the element set, its force contributions are not considered. Since element 2 is not in the element set, its force contributions will be considered. From the GPFORCE table, the x-force value that is extracted for node 4 is the element 2 force 1.085e+03. These values sum to 0. Y-Force: All values are zero in this model.
Altair Engineering

Z-Force: Node 3 is attached to elements 1 and 2. Since element 1 is in the element set, its force contributions are not considered. Since element 2 is not in the element set, its force contributions will be considered. From the GPFORCE table, the x-force value that is extracted for node 3 is the element 2 force 6.426e+02. Node 4 is attached to elements 1 and 2. Since element 1 is in the element set, its force contributions are not considered. Since element 2 is not in the element set, its force contributions will be considered. From the GPFORCE table, the x-force value that is extracted for node 4 is the element 2 force 3.574e+02. These values sum to 1.000e+03. X-Moment: All values are zero in this model. Y-Moment: Node 3 is attached to elements 1 and 2. Since element 1 is in the element set, its moment contributions are not considered. Since element 2 is not in the element set, its moment contributions will be considered. From the GPFORCE table, the y-moment value that is extracted for node 3 is the element 2 moment -8.871e+00. Node 4 is attached to elements 1 and 2. Since element 1 is in the element set, its moment contributions are not considered. Since element 2 is not in the element set, its moment contributions will be considered. From the GPFORCE table, the y-moment value that is extracted for node 4 is the element 2 moment -1.024e+01. Additionally, the cross-product of all the forces about the Y axis need to be considered. Selecting node 3 as the summation node (any node in the model can be selected) and performing rXF (all element edge lengths are 0.166) the following is obtained: Node 3 Node 4 no additional rXF contributions since it is the sum point -0.166*Fx + 0*Fz = -0.166*1.085e+03 + 0*3.547e+02 = -1.808e+02
These values sum to -2.000e+02. Since there are only 4 significant digits in the GPFORCE table, the precision of the calculated moments are compromised. In the actual FBD utilities, the full result and machine precisions are used. Z-Moment: All values are zero in this model. Below is a sample output table from the Resultant Force and Moment utility for element 1 (element set) and nodes 3 and 4 (node set) with node 3 used as the summation point:

Altair Engineering
FBD Displacements The FBD Displacements utility uses an element set and a node set to define the values to extract from the Displacement table. The element and node sets serve several purposes: All nodes in the node set will have displacement and rotation values extracted. The element set is for visualization and breakout modeling purposes only.
Additional Information: Recommended practice is to output GPFORCE data for the element set(s) of interest only. This procedure reduces the size of the .op2 file and helps speed up the FBD Forces extractions. Additionally, for Nastran and OptiStruct, consider using STRESS = NONE and/or DISPLACEMENT = NONE options to further reduce the size of the .op2 file. See the OptiStruct online reference guide for more information regarding STRESS and DISPLACEMENT io option cards. MPC forces and moments are properly extracted for the following MPC constraint types: RBE2 RBE3 Rigidlink RJOINT RROD RBAR
The GPFORCE and Displacement results are extracted from the .op2 file in float point precision in binary format. This maintains the integrity of the calculations as well as enhances the performance of the utilities.
Altair Engineering

FBD Solver Interfacing

The Free Body Diagram utilities behave differently depending on the solver that you interface with in HyperMesh. Consult these topics for details:
Abaqus Ansys Nastran Radioss (Bulk Data) and OptiStruct
See also FBD Overview Tab area

Altair Engineering
Abaqus - Free Body Diagrams

Results are supported through the .odb output file. The installation of the HyperView Abaqus ODB API is required to support Abaqus FBD results in HyperMesh. Grid Point Forces (GPF) results are requested with the following .odb file output requests: *NODE OUTPUT RF CF *ELEMENT OUTPUT NFORC Displacement results are requested with the following .odb file output request: *NODE OUTPUT U It is recommended practice to output data for only the node/element set(s) of interest. This procedure reduces the size of the solver results file and helps speed up the FBD extractions. Abaqus rigid elements, *Rigid bodies, *Coupling constraints, *MPC, *Fastener and *Equations do not export forces and moments. If any of these are attached to the element set of interest, all elements attached to them must be included in the element set to insure the GPF balance is correct. If they are not included, an imbalance will occur. Refer to the Abaqus documentation to determine these elements/bodies. Make sure to check the validity of all GPF results when any of these are present in the model. The FBD Export Manager is currently not supported for Abaqus.
Altair Engineering

Ansys - Free Body Diagrams

Currently only supported for Win32 and Win64 platforms. Results are supported through the .rst output file. The installation of HyperView is required to support Ansys FBD results in HyperMesh. Grid Point Forces (GPF) results are requested with the following .rst file output requests: OUTRES,ALL,ALL or OUTRES,NSOL,ALL OUTRES,RSOL,ALL Displacement results are requested with the following .rst file output requests: OUTRES,ALL,ALL or OUTRES,NSOL,ALL OUTRES,RSOL,ALL The FBD Export Manager is currently not supported for Ansys.

Altair Engineering
Nastran - Free Body Diagrams

Results are supported through the .op2 output file. Grid Point Forces (GPF) results are requested with the GPFORCE .op2 output request. Displacement results are requested with the DISPLACEMENT .op2 output request. It is recommended practice to output data for only the node set(s) of interest. This procedure reduces the size of the solver results file and helps speed up the FBD extractions. Consider using STRESS=NONE and STRAIN=NONE to further reduce the size of the results file. MPC forces and moments are properly extracted for the following MPC constraint types: RBE2 RBE3 RigidLink RJOINT RROD RBAR
Altair Engineering

Radioss (Bulk Data) and OptiStruct - Free Body Diagrams

Results are supported through the .op2 output file. Grid Point Forces (GPF) results are requested with the GPFORCE .op2 output request. Displacement results are requested with the DISPLACEMENT .op2 output request. It is recommended practice to output data for only the node set(s) of interest. This procedure reduces the size of the solver results file and helps speed up the FBD extractions. Consider using STRESS=NONE and STRAIN=NONE to further reduce the size of the results file. You may consider using the NOMODEL option on the OUTPUT,OP2 output format request. MPC forces and moments are properly extracted for the following MPC constraint types: RBE2 RBE3 RigidLink RJOINT RROD RBAR

Altair Engineering
H3D Writer
The following topics are explored in the H3D Writer help: Creating an H3D file from HyperMesh Embedding a HyperView Player Object in HTML Documentation Sharing H3D Files H3D FAQ
Altair Engineering

Creating an H3D file from HyperMesh

Using an H3D file, you can save 3-D animations from HyperMesh in the .h3d format for viewing with the HyperView Player. HyperView Player is an Internet browser plug-in for visualizing 3-D Computer Aided Engineering (CAE) models and results. Using product data in Altair's compact .h3d format allows you to incorporate animated images in an HTML document for presentation or engineering reports. Simulation results can be sent by e-mail or placed on the web for others to open and review. Note: In order to enable the option to create H3D files, you must activate the checkbox labeled launch HV after H3D creation in the Options panel.
HyperView Player is available as a free download on Altair's Web site at http://www.altair.com.
See also H3D File FAQ

Altair Engineering
Create an H3D file from HyperMesh:

Note: In order to enable the option to create H3D files, you must activate the checkbox labeled launch HV after H3D creation in the Options panel.
1. 2.
Select one of the following panels: Contour, Deformed, Hidden Line , Transient, or Geom Cleanup. To control the display attributes for your model: Specify your desired display attributes using visual options or the visual panel.
3.
Click the Hyper3d button. Or H3D>HV. Two files are created. One is an H3D file, using anim#.h3d as the file name. The symbol # is automatically assigned to the H3D file. The other is a sample HTML file including an <EMBED> statement for the corresponding H3D file. H3D>HV loads the newly created H3D file into HyperView. You can define this option in the Options panel under modeling.
4.
To review the model in a Web browser: Double-click the HTML file to launch a browser. Or Click H3D to activate the standalone HyperView Player. You can customize the external HTML template, h3d_template.html, located in the altair/hm/ html directory, to suit your needs.
Note:
In the HyperMesh Geom Cleanup panel, the Hyper3D button is displayed when you select the shaded option in the Visual options subpanel.
Altair Engineering

Embedding a HyperView Player Object in HTML Documentation

The following section defines the arguments and provides an example for embedding statements in an HTML document in order to view a HyperView Player graphic object. Note the following updates to HyperView Player: Simplified HTML File Statement Since the H3D file created from HyperView and HyperMesh includes scene information, the arguments in the old statements for model readers and result readers are no longer needed. The HTML statements have been simplified in this release. However, the HTML files created for HyperView Player 3.1 are still supported. HyperView Player only supports H3D direct readers. You can create an H3D file using: HyperView HyperMesh HyperMesh result translators, such as hmnast, hmnasto2, hmradioss, hmpam, hmansys, and hmabaqus OptiStruct Note: You may need to modify your HTML files created for HyperView Player 3.1 if you were using direct readers other than h3d.dll, such as adams.dll, gfile.dll, lsdyna.dll, and madymo.dll, since those readers are no longer supported in HyperView Player.
Direct Readers
To embed a HyperView Player object, the <EMBED> statement in HTML is used. All arguments are case insensitive. General Arguments for EMBED Statements type width/height SRC="URL" Application/x-h3d Measured in pixels The location of the plug-in data file as indicated by its URL.
Embedded Statement Example <EMBED type="application/x-h3d" width=450 height=400 src="HTTP:\\www.altair.com\h3d\bumper.h3d">
<EMBED
type="application/x-h3d" width=450 height=400 src="../bumper.h3d">

Altair Engineering
More examples can be found in the HyperView Player demo directory and at our Web site (http://www.altair. com).
See also How to share .h3d files The HyperView Player demo directory and Web site (http://www.altair.com) for more examples.
Altair Engineering

Sharing H3D Files

Using an HTML File
You can use HyperView Player to share information by embedding it in an HTML file. You can use either a relative path or a standard Uniform Resource Locator (URL) to specify the path for the H3D file in the <EMBED> statement. There are three different ways to define file transfer protocol: FILE, HTTP and FTP. This section describes how to select a protocol for file transfer using the files, anim1.html and anim1.h3d, as examples. Embedded mode FILE:// Example: <EMBED type="application/x-h3d" width=450 height=400 SRC="File://c:\Altair\demos\hvp\anim1.h3d"> An absolute path is required for File:// and the H3D file must reside in the specified path. When you distribute the files, you may need to modify the HTML file for the path. HTTP:// Example: <EMBED type="application/x-h3d" width=450 height=400 SRC="http://www:8080/~John/anim1.h3d> Others can access your public web area on the Internet. When sharing an H3D file, you can place the anim1.html and anim1.h3d files in your public HTML directory and send the link to others in the company by email. The link could be, for example, http://www:8080/~John/anim1.html. By doing this, you do not need to distribute the H3D file and can guarantee the path is working correctly. If you have HyperView Player installed and you click the link in the email, the model will be displayed. FTP:// Example: <EMBED type="application/x-h3d" width=450 height=400 SRC="FTP://ftp.altair.com/pub/outgoing/HVP/anim1.html> You can place the anim1.html and anim1.h3d files on your FTP site. If you have HyperView Player installed and you click ftp://ftp.altair.com/pub/outgoing/HVP/anim1.html, the model is displayed. Relative path Example: <EMBED type="application/x-h3d" width=450 height=400 SRC="../anim/.h3d> Using a relative path allows you to distribute an HTML file easily. You can create a folder with the necessary HTML and h3d files for distribution. Full page mode

Altair Engineering
In an HTML file, you can easily hyperlink a string to an H3D file. When you click the hyperlink, the plug-in loads a model in full-page mode.
Using E-mail
You can attach an H3D file to an e-mail message. If the recipient is using a PC, he or she can click the attachment and the H3D file will load automatically. You can also save the H3D file and at a later time double-click the file to invoke the standalone version of HyperView Player. Another available option is to drag the H3D file and drop it into a browser to view the model in a full window.
Altair Engineering

H3D FAQ
How can I view a model with shaded display in HyperView Player? The model display settings are recorded during H3D creation. Set up the desired model display, with such options as mesh lines and feature lines, in the Vis panel under the Performance Graphics mode in HyperMesh. Why doesnt the legend setting in HyperView player reflect the setting in HyperMesh? HyperView Player only supports default settings for the legend display from HyperMesh. The specified Max and Min values in HyperMesh are not recorded in the H3D file of this version. Can I view complex result animation in HyperView player? No, the H3D writer does not support complex result data. What types of element are not supported in the H3D file? Second order elements, rigidlinks, and RBE3s are not supported in this version. The mid-side node of a second order element is ignored when it is read into HyperView Player. How can I change the window size for viewing HyperView Player in the browser? You can modify the width and height values in the <EMBED> statement in the HTML file. (For example, width = 600, height = 600)
Return to Creating an H3D file from HyperMesh

Altair Engineering
HyperMesh Interfacing with External Products

This section gives you a basic overview for each solver interface supported by HyperMesh. Each chapter lists available user profiles and supported solver versions. You find specific information and procedures for each interface.
FE Model Import FE Model Export Conversion between Solver Formats Abaqus Solver Interface Actran Solver Interface ANSYS Solver Interface LS-DYNA Solver Interface MADYMO Solver Interface Nastran Solver Interface MARC Solver Interface PAM-CRASH 2G Solver Interface PERMAS Solver Interface RADIOSS (Block Format) Interface Overview RADIOSS (Bulk Data), OptiStruct Interface Samcef Interface
Altair Engineering

Abaqus Solver Interface

This section describes the Abaqus input translator, the output template, summary templates, and the result translator in HyperMesh. By selecting the Abaqus user profile, you can work with pre-defined panels that are more specific to Abaqus usage. The User Profiles dialog is launched by default when HyperMesh is started the first time. Three user profiles (and templates) are available for the Abaqus interface:
Standard.2d
Generates a deck for two-dimensional models containing planar or axisymmetric elements for use with Abaqus Standard. Generates a deck for three-dimensional models containing bar, shell, and solid elements for use with Abaqus Standard. Generates a deck for use with Abaqus Explicit.
Standard.3d
Explicit
These are some general comments about HyperMesh interface with Abaqus:
Import and Export
The Abaqus interface supports Abaqus version 6.10 HyperMesh places all elements into separate components, based on sectional property. Each component is written out from HyperMesh as element set in the Abaqus input deck. Although HyperMesh supports 160 characters in entity names, Abaqus output files are truncated at 80 characters to match the Abaqus name support level. The loads and constraints are organized under load collectors in HyperMesh. These load collectors need to be added to a load step for the *STEP card in Abaqus history definition. If loads are applied to node or element sets there is a solver option provided in the Import panel under Import options. The option Expand loads on sets allows the user to resolve these sets to individual nodes or elements. The output options are organized under output blocks in HyperMesh. These output blocks also need to be added to load steps. Solver options in the Import panel (see Import options) allows the user to resolve sets into nodes or elements which are defined using the GENERATE parameter. This is useful when nodes/elements are renumbered due to ID conflicts during import.
Syntax
HyperMesh supports some abbreviated key words and parameters. All Abaqus keywords and parameters supported in HyperMesh are not case insensitive.

Altair Engineering
HyperMesh ignores spaces in keyword lines. HyperMesh supports quotation marks around component (ELSET with sectional properties) names, which is especially useful for names that begin with a number. HyperMesh Operations Warnings and error messages are written to a file named abaqus.msg. Unrecognized lines are written to a *.hmx file. These files are created in the same directory from where HyperMesh is launched. Step time calculations can differ between HyperMesh and Abaqus (Explicit analyses), so you may find differences between reported values in the Abaqus status (.sta) file and the time subpanel of the Check Elems panel. The values reported by HyperMesh are close estimates of the step time; refer to the Abaqus documentation to learn more about the factors that Abaqus/ Explicit uses to reach the final result.
See also Importing Files Exporting Files Model Browser Solver Browser Connector Browser Include Files Using the Abaqus Utility Menu Supported Abaqus Keywords Unsupported Abaqus Keywords Solver Conversion
Altair Engineering

Actran Solver Interface

HyperMesh includes an Actran user profile and template for specifying Actran properties on a HyperMesh model and outputting an Actran input deck. An Actran model is defined in HyperMesh by the following steps: 1. 2. 3. 4. 5. 6. Create materials Create components Create mesh on the appropriate components Define boundary conditions, both node-related and element face-related Define the control card properties Create the Actran input deck file
Four types of materials can be defined: fluid, visco-elastic, porous, and viscothermal fluid.
See also Importing Files Exporting Files Model Browser Supported Actran Keywords

Altair Engineering
ANSYS Solver Interface

The HyperMesh ANSYS interface allows you to: Read an ANSYS ASCII database Create and edit an ANSYS ASCII database from within HyperMesh Preview and edit ANSYS cards after they are created Summarize ANSYS elements, loads, and properties Output an ANSYS ASCII database Convert an ANSYS binary results file into a HyperMesh binary results file that can be read into HyperMesh for post-processing Assign macro commands to modify HyperMeshs default ANSYS output HyperMesh treats ANSYS as a card image code. HyperMesh supports ANSYS element types for STATIC STRUCTURAL, THERMAL, and MODAL analyses using ANSYS versions 12.1, and earlier version. ANSYS 12.1 .rst, .rmg and .rth files can be read in HyperView. HyperMesh can read .rst, .rmg and .rth files from ANSYS 8.1 or earlier versions. To read result files later than 8.1, use HyperView. Warnings and error messages are written to a file called ansys. msg. Unrecognized lines are written to a *.hmx file. These files are created in the directory from which HyperMesh is launched. The ANSYS interface is only available once you have loaded the ANSYS user profile.
See also Importing Files Exporting Files Model Browser Solver Browser Connector Browser Using the Ansys Utility Menu Supported Ansys Keywords Solver Conversion
Altair Engineering

RBE3 Elements
In ANSYS, the purpose of an RBE3 card is to distribute the force/moment applied at the master node to a set of slave nodes, taking into account the geometry of the slave nodes as well as weighting factors. In HyperMesh, RBE3 is created using the RBE3 panel (1D page). It is a HyperMesh element that includes multiple 1-D elements, which are defined between a single dependent (master) node and one or more independent (slave) nodes. ANSYS RBE3 elements are different from Nastran RBE3 elements. In ANSYS, the RBE3 card is used to distribute the force/moments from the master node to a set of slave nodes. Whereas in Nastran, these elements define the rigid body motion. In HyperMesh, the ANSYS RBE3 card is mapped as an RBE3 element. Therefore, when creating the RBE3 elements in HyperMesh for the ANSYS template, the following points should be noted. 1. 2. When an RBE3 element is created in HyperMesh, the DOFs are defined for the master as well as for the slave nodes. However, since the slave node DOFs are not applicable in ANSYS, they are not exported. By default, when an RBE3 element is created in HyperMesh, the same weight factor that is applied at the master node is also applied on all the slave nodes. The update subpanel on the RBE3 panel allows you to modify the weight factors for the individual slave nodes. Since the master node weight factor is not applicable in ANSYS, it is not exported. The RBE3 elements created in HyperMesh using other solver templates, such as Nastran, are exported according to ANSYS template terminology.
3.
Exporting HyperMesh RBE3 Elements

Two parameter arrays are exported for each RBE3 element. The first array contains slave node IDs and the second array contains slave node weights. These arrays appear in the beginning of the exported file. Exportation of the SLAVE# array: *DIM,SLAVE#,ARRAY, *SET,SLAVE#( *SET,SLAVE#( *SET,SLAVE#( . . . *SET,SLAVE#( Where: NS, 1, 1), ID_NS 1, 2, 3, NS, 1, 1, 1, 1, 1), 1), 1), 1 ID_1 ID_2 ID_3
# is the HyperMesh element ID of the RBE3. NS is the number of slave nodes within the RBE3. ID_1, ID_2, ID_3,,ID_NS are the IDs of the slave nodes.
Exportation of the WEIGHT# array: *DIM,WEIGHT#,ARRAY, NS, 1, 1

Altair Engineering
*SET,WEIGHT#( *SET,WEIGHT#( *SET,WEIGHT#( . . . *SET,WEIGHT#( Where:
1, 2, 3,
1, 1, 1,
1), 1), 1),
WF_1 WF_2 WF_3
NS,
1,
1),
WF_NS
# is the HyperMesh element ID of the RBE3. NS is the number of slave nodes within the RBE3. WF_1, WF_2, WF_3,,WF_NS are the weighting factors corresponding to each slave node.
Each RBE3 element is written using an RBE3 card with the following format: RBE3, Master_ID, DOF, SLAVE#, WEIGHT# Where: Master_ID is the ID of the master node. DOF is the degrees of freedom checked in the RBE3 panel for RBE3 element with ID #. The DOF is exported as follows: U UY UZ ROTX ROTY ROTZ UXYZ RXYZ ALL if ux is checked if uy is checked if uz is checked if rotx is checked if roty is checked if rotz is checked if ux, uy, and uz are checked if rotx, roty, and rotz are checked if all are checked
If a combination of DOFs not listed above is checked, several RBE3 cards will be exported for the same element. For example, if ux, uy, and roty are checked, three RBE3 cards will be exported as follows: RBE3, Master_ID, UX, SLAVE#, WEIGHT# RBE3, Master_ID, UY, SLAVE#, WEIGHT# RBE3, Master_ID, ROTY, SLAVE#, WEIGHT#
Altair Engineering

SLAVE# is the name of the slave node ID array as described in step 1. WEIGHT# is the name of the weighting factor array as described in step 1. Where # is the RBE3 element ID. The exportation location is the CP or CERIG elements.
ANSYS FE input Translator Support for RBE3

Importing the ANSYS exported files In ANSYS, RBE3 is not an element; it is created by a command called RBE3. ANSYS does not export these RBE3s as an RBE3 card, but rather as a set of constraint equations (CE). The HyperMesh-ANSYS FE input translator imports CE equations as CE equations only, and not as RBE3 elements. Importing the HyperMesh exported files Since HyperMesh writes out RBE3 elements using RBE3 cards, the H_ANSYS FE input translator imports the HyperMesh exported RBE3 cards as RBE3 elements.

Altair Engineering
Tips and Techniques

The operations performed in HyperMesh can also be saved as a compact HyperMesh binary file using the File - Save As option. Bolt simulation configuration files are now available for ANSYS profile. In the bolt panel, you can create general bolt, bolt with one or two washers, bolt with spider option and clips under the Ansys profile. To determine the mass of your finite element model, use the Mass Calc panel on the Tool page. Select the ansys.tpl template file through the Import tab. The mass calculation is supported for the following element type numbers: 1, 2, 3, 4, 5, 8, 10, 13, 16, 18, 20, 21, 23, 24, 25, 28, 31, 32, 33, 41, 42, 43, 44, 45, 46, 51, 53, 54, 55, 57, 58, 60, 61, 62, 63, 64, 67, 69, 70, 71, 75, 77, 78, 80, 82, 83, 87, 90, 91, 92, 93, 95, 96, 97, 98, 99, 107, 116, 117, 118, 119, 120, 121, 143, 145, 147, 148, 150, 152, 153, 154, 157, 162, 163, 164, 173, 174, 180, 181, 182, 183, 185, 186, 187, 191 Each operation in HyperMesh results in an ASCII command that is added to a command.cmf file. This file is useful if your computer shuts down while working in HyperMesh. You can restore your previous work by reading this file with the command function, which can by found by clicking File Run - Command File. You can delete this file if it requires too much disk space. The command.cmf file can also be used to store repetitive HyperMesh operations. If you deal with the same set of geometrical and material properties, you can record the creation of these collectors (steel plate, foam solids, aluminum rods, and so on) into series of command files and read them as needed. The ANSYS template is associated with the Composites panel. Using this panel for laminated elements, such as SHELL99, enables the following: Element orientation by two methods: By system - assigns a system to the element (set ESYS for the element) By vector - projects a vector on the element plane. A coordinate system, in which the x-axis is parallel to the defined vector, is created and assigned to the element as ESYS. The by system axis and by angle options are not available for this template. Visualization of the element orientation Visualization of the ply direction on a layer-by-layer basis. Visualizes the angles defined in the R card with respect to the element orientation. If you change KEYOPT3 for MASS21 and KEYOPT6 for BEAM23 elements, make sure you do so on comp as well as on prop collector. When you click on the card image button while creating a prop collector, the GENERALp card is shown at the end of the list. This card is used to card edit the properties that are not used by any element. The ANSYS connectivity for a second order (3-node) line element (such as BEAM189 or SURF153), is as follows: End-node-I, End-node-J and Mid-node-K. However, for creation of a bar3 element in HyperMesh (using the bar panel/bar3 subpanel), pick node A, node B, and node C in the following order: End-node-I, Mid-node-K and End-node-J, respectively. The ANSYS template will export the bar3 element using the ANSYS connectivity. There are two ways to apply loads in local coordinate systems (ANSYS NROTAT card) using
Altair Engineering

HyperMesh: The Forces panel and the Moments panel allow you to apply loads in a local coordinate system by using the local system option. The set analysis option in the Systems panel - assign subpanel can be used to assign a node to a coordinate system. A load applied to that node would be displayed correctly after exportation and importation of the ANSYS deck. If both options of applying loads in local coordinate systems are used for the same node, the first method (via the Forces and Moments panels) takes precedence.

Altair Engineering
Pressure Load on Beam Elements

HyperMesh 11.0 supports pressure load on bar and rod elements, which means you can now import the pressure load [SFBEAM] applied on ANSYS BEAM elements. The following items are supported under this feature: Import pressure load applied on BEAM3, BEAM4, BEAM23, BEAM44 elements. Import restrictions are explained below. Use the Pressure panel to apply SFBEAM load on beam elements. Export pressure load applied on BEAM elements in HyperMesh as SFBEAM load in ANSYS solver deck. The Export feature is explained in detail below. Importing pressure load: SFBEAM is the key word command in ANSYS decks to apply pressure load on BEAM elements. This command line has following arguments: SFBEAM,ELEM,LKEY,Lab,R5.0,DIOFFST,DJOFFST ELEM is element ID and Lab is always pres(pressure). LKEY is load key number which determines the face of the beam where the pressure load is applied. You need to refer to the ANSYS solver documentation to know the face of the beam and corresponding LKEY number as it changes from BEAM to BEAM.
Restrictions: 1. The HyperMesh-ANSYS interface presently supports following LKEY values for each BEAM element. You can import SFBEAM load with these LKEYs. ELEMENT TYPE BEAM3 BEAM4 BEAM23 BEAM24 BEAM44 BEAM54 BEAM188 BEAM189 SUPPORTED LKEYs 1, 3, 4 1, 2, 4, 5 1, 3, 4 1, 2, 4, 5 1, 2, 4, 5 1, 3, 4 1, 2, 4, 5 1, 2, 4, 5
2.
In the above arguments, DIOFFST, DJOFFST which define offset values for pressure value at node I and J
Altair Engineering

are not supported in HyperMesh. 3. SFLOAD also allows you to apply pressure load that varies across the length of the beam. But this type of load is not supported in HyperMesh 9.0. Only pressure load with constant value can be imported.
Applying pressure on BEAM elements in HyperMesh for the ANSYS interface: You can apply pressure load in HyperMesh on any bar2, bar3 and rod, elements. But you can export only those pressure loads which are applied on BEAM element types that have been mentioned earlier as supported elements. By default if no option for direction is selected, pressure is applied on element y direction. You can use different options available in pressure load panel to specify the direction of the load. The ANSYS solver allows pressure on beam elements in only specified faces of the elements (as mentioned by LKEYS). In other words, pressure on beam elements is applied in element co-ordinate system. You should keep this in mind before determining the direction of the pressure. You cannot apply pressure load that varies across the length of the BEAM even though it is allowed in the ANSYS Solver. Load offsets at node I and J are not supported. Exporting pressure load on BEAM elements from HM for Ansys interface: Pressure on Beams is exported as SFBEAM cards. Pressure only applied on BEAM3, BEAM4, BEAM23, BEAM44, BEAM54, BEAM188, BEAM189 elements will be exported. Pressure applied in any arbitrary directions is resolved in to corresponding element systems and relevant LKEYs will be assigned while exporting. Hence when you import the deck back to HyperMesh, you will see resolved loads.

Altair Engineering
FE Input Enhancement
Starting in HyperMesh 10.0SA1-130, decks from Moldex 3D Mesh 9.1 software can now be read in HyperMesh.
Altair Engineering

LS-DYNA Solver Interface

This section describes the HyperMesh LS-DYNA interface. HyperMesh provides a complete pre-processing environment for preparing LS-DYNA data decks for analysis. HyperMesh can read existing LS-DYNA decks, create a model, display and edit LS-DYNA cards as they will look in the deck, and write a deck for analysis. Although HyperMesh also offers limited post-processing capabilities in results translation you are strongly encouraged to exclusively use HyperView. To create LS-DYNA decks in HyperMesh, you must load the LsDyna user profile with the appropriate template to access the full pre-processing capability. The following are the general comments about the HyperMesh Interface for LSDYNA Import and Export The LSDYNA interface supports LSDYNA version 971 R 4.2.1 The LSDYNA input translator supports reading both free and fixed formats, however, the export template writes all cards in fixed format. Solver specific import options are available during import in the solver options tab. The LSDYNA input translator can read DUMMIES with the tree structure in Primer format or in HyperMesh format but exports the tree structure only in HyperMesh format. The LSDYNA input translator allows reading multiple instances of same include file using *INCLUDE_TRANSFORM. They are read in but duplicated as independent includes inside HyperMesh. The duplicate instances of same include are tagged as not exportable thus limits the support to I/O only. Although majority of LSDYNA keywords are supported, unsupported material and property if it exists in the deck are read into HyperMesh and exported maintaining the associvity. All other unsupported portion of deck is mapped to unsupported cards in HM and appended at the end of deck during export. Most of IDs in the solver deck is preserved with introduction of ID pool concepts in HyperMesh. However solver cards mapped to Load collectors, Groups, Sensor, Airbag are renumbered if there is a conflict of ID among the keywords mapped to a HyperMesh entity. The new IDs are posted during the import process.
Duplicate IDs
Several LSDYNA keywords are mapped to one HM entity in some instances. By default HyperMesh LSDYNA interface doesnt allow duplicate ID within same HM entity with exception of elements while LSDYNA allows duplicate IDs across cards mapped to one HM entity. In HyperMesh ID flexibility similar to LSDYNA can be enabled by switching on Duplicate ID option in Preferences pull down.
Mass Calculations
The mass of each element is calculated by density * volume. Density is retrieved from the material associated with the elements component. Several assumptions are made in mass calculation based on LSDYNA solver. Mass supplied by *PART_INTERIA card is used instead of calculating the

Altair Engineering
mass based on the individual elements. Also, mass calculations include the mass supplied on the *CONSTRAINED_NODAL_RIGID_BODY_INERTIA cards. Shell element thickness for volume calculation is one of the following: the thickness on the first node for uniform thickness shells the average thickness at three or four nodes for non-uniform thickness shells The thickness values come from the *SECTION_SHELL card, unless a *ELEMENT_SHELL_THICKNESS card is defined for an element. If an *ELEMENT_SHELL_THICKNESS card is defined, its thickness values override the thickness values from the *SECTION_SHELL. Integrated beams have an area equal to the average of the two end areas. Resultant beams use the area entered on the *SECTION_BEAM card. The volume is calculated by multiplying the length of the beam with the *SECTION_BEAM card area. Discrete beams use the volume supplied by the *SECTION_BEAM card. In all cases, if an *ELEMENT_BEAM_THICKNESS card is defined for an element, then the element values override the *SECTION_BEAM values. Only element masses are considered. Other mass specifications, such as on a rigid wall card, are ignored.
See also Importing Files Exporting Files Model Browser Solver Browser Connector Browser Include Files Using the LS-DYNA Utility Menu Supported LS-DYNA Keywords Unsupported LS-DYNA Keywords Solver Conversion
Altair Engineering

Recommended Process
Editing an LS-DYNA model to add cards not supported
Even though most LS-DYNA cards used by the majority of users are supported, some cards are not. In order to use unsupported cards with the LS-DYNA model, you can add them in HyperMesh (no need to use a text editor). Select unsupp_cards in the Control Cards panel. You can then enter the cards in the pop-up text editor. You should exercise caution regarding formatting and card validity. Care should also be taken if any of the cards point to entities (such as cards pointing to sets, parts, etc.). These cards are stored as text and pointers are not considered. When importing an LS-DYNA mode, any cards that are encountered that are not supported are written in this section, thus they are exported along with the remaining model.
Blanks
In the card editor, all the attribute fields are supported as Blanks. You must click on the field and input the value.

Altair Engineering
Mass Calculation
The mass of each element is calculated by density * volume. Density is retrieved from the material associated with the elements component. Several assumptions are made in mass calculation. Mass supplied by *PART_INERTIA card is used instead of calculating the mass based on the individual elements. Also, mass calculations include the mass supplied on the *CONSTRAINED_NODAL_RIGID_BODY_INERTIA cards. Shell element thickness for volume calculation is one of the following: the thickness on the first node for uniform thickness shells the average thickness at three or four nodes for non-uniform thickness shells The thickness values come from the *SECTION_SHELL card, unless a *ELEMENT_SHELL_THICKNESS card is defined for an element. If an *ELEMENT_SHELL_THICKNESS card is defined, its thickness values override the thickness values from the *SECTION_SHELL. Integrated beams have an area equal to the average of the two end areas. Resultant beams use the area entered on the *SECTION_BEAM card. The volume is calculated by multiplying the length of the beam with the *SECTION_BEAM card area. Discrete beams use the volume supplied by the *SECTION_BEAM card. In all cases, if an *ELEMENT_BEAM_THICKNESS card is defined for an element, then the element values override the *SECTION_BEAM values. Only element masses are considered. Other mass specifications, such as on a rigid wall card, are ignored. Mass calculation also includes structural nodal mass defined for beam and shell elements.
See also LS-DYNA Interface Overview
Altair Engineering

Exporting Decks
The following LS-DYNA files can be output: LS-DYNA v971, v970 and v960 input files in Keyword format By default, the LS-DYNA user profile outputs v971 .key files. Two templates are also provided to output the defined curves in the database: To output curves in Keyword format, use the curves.key template To output curves in Structured format, use the curves.seq template
See also To Export an FE Model LS-DYNA Interface Overview

Altair Engineering
MADYMO Solver Interface

The MADYMO interface supports both the import and export of MADYMO files. A MADYMO XML file can be read using the Import tab. The model will be displayed. The model can be altered and the finished model can be written using the Export tab.
User Profiles
The MADYMO interface has two user profiles - Madymo63 and Madymo70. Make your selection in the User Profile dialog using the drop down menus.
Importing a MADYMO Model

The MADYMO input file is based on XML and must be converted to be used in HyperMesh. If HyperMesh supports the equivalent MADYMO entities, the mapping is straightforward. If HyperMesh does not provide the entity, a transformation rule is used. Several MADYMO entities are mapped on the same type of HyperMesh entities; e.g. ACTUATOR, CONTROLLER, OPERATOR, SENSOR, SIGNAL, STATE and SWITCH are all mapped on sensor. This puts a restriction on the use of names for these entities; all names of the MADYMO entities mapped on the same HyperMesh entity must be unique, for example, a MADYMO SENSOR cannot have the same name as a MADYMO CONTROLLER. During the FE import process HyperMesh will rename the entities as required to avoid duplicate names.
Exporting MADYMO Models

During export only the nodes that are in use according to MADYMO are exported. HyperMesh temporary nodes are not exported even if they are used in a node set or a MADYMO node LIST. It is advised to remove all temporary nodes before exporting the model. In general, the IDs of entities in the HyperMesh model correspond with the IDs in the MADYMO XML file after exporting the model. There is one exception to this rule: PLANES in MADYMO are a subtype of the entity SURFACE that contains also the subtypes CYLINDER and ELLIPSOID. The IDs must be unique within the SURFACE type. In HyperMesh these entities are mapped onto two different entities (mbplanes and ellipsoids) with their own unique numbering. Therefore, during export the mbplanes are renumbered to get unique MADYMO IDs for the PLANEs.
The following tutorials are also available: HM-4900: Creating a MADYMO Model HM-4910: Setting up a MADYMO Occupant Safety Analysis
See also Importing Files Exporting Files
Altair Engineering

Model Browser Solver Browser Connector Browser Include Files Using the MADYMO Utility Menu Supported MADYMO Keywords

Altair Engineering
MARC Solver Interface

Follow these guidelines when creating a model for use with the HyperMesh MARC interface. HyperMesh treats MARC as a card image code. The MARC interface is based on MARC version 12; 2008r1 release. The current interface supports linear and nonlinear static analysis. For 2-D models, use the template stress2d.tpl. For 3-D models, use the template stress3d.tpl. 2-D and 3-D models cannot be combined. 2-D models should use the xy-plane. Warnings and error messages are written to a file called marc.msg. Unrecognized cards are written to an *.hmx file. These files are created in the same directory from where HyperMesh is launched. Any data which is currently not supported in HyperMesh is stored as unsupported data and is added to the model if the model is exported from HyperMesh. The MARC solver interface supports PATRAN exported in MARC format.
See also Importing Files Exporting Files Model Browser Supported MARC Keywords
Altair Engineering

Nastran Solver Interface

This section describes the HyperMesh Nastran input translator, output template, results translator, and summary templates. Nastran is treated as a card image code. Follow these guidelines when creating a model for use with the Nastran interface: The Nastran interface is based on MSC/Nastran version 2007. During input, the Nastran interface assumes that the continuation line always follows the line before, therefore no continuation cards are needed in the input file. During export, to ensure that the continuation line follows the reference card, HyperMesh writes "+" or "*" as a continuation card. Warnings and error messages are written to an open text file for user review. You can save this file. All the lines in the input file that are unrecognized by the translator are written to unsupported cards, which can be edited. The Nastran input translator supports single, double, free, and fixed formats. Two templates are available for export and viewing (editing) Nastran cards. The nastran/general template outputs all cards in single precision, fixed format. The nastran/generallf template outputs systems, grid, 1-D property, PSHELL, PSOLID and material cards in fixed, double precision format with all other cards in fixed, single precision format. By selecting the Nastran user profile, you can work with pre-defined panels that are more specific to Nastran usage. Note: Before exporting or editing Nastran cards, a Nastran template must be loaded. Setting the user profile to Nastran automatically loads the Nastran template. HyperMesh reads and writes certain HyperMesh commands in the Nastran bulk data file as comments. These comment cards enable HyperMesh to preserve pre-defined preferences across sessions. It is strongly suggested that users do not hand edit these cards.
See also Importing Files Exporting Files Model Browser Solver Browser Connector Browser Include Files Using the Nastran Utility Menu Supported Nastran Keywords Unsupported Nastran Keywords Solver Conversion

Altair Engineering
PAM-CRASH 2G Solver Interface

This section describes the HyperMesh PAMCRASH2G interface. HyperMesh provides a complete preprocessing environment for preparing PAMCRASH2G data decks for analysis. HyperMesh can read existing PAMCRASH2G decks, create a model, display and edit PMACRASH2G cards as they will look in the deck, and write a deck for analysis. Although HyperMesh also offers limited post-processing capabilities in results translation you are strongly encouraged to exclusively use HyperView. To create PAMCRASH2G decks in HyperMesh, you must load the PAMCRASH2G user profile with the appropriate template to access the full pre-processing capability.
The following are the general comments about HyperMesh Interface for PAMCRASH2G: Import and Export The PAMCRASH2G supports PAMCRASH2G version 2005 - 2008 The PAMCRASH2G input translator also supports reading older PAMCRASH2G files 2002 -2004 and map into the loaded template. PAMCRASH and PAMCRASH2G 2002 2005 templates are available in the installation and can be loaded by user. However they are no longer maintained. During import all the GES associated with the solver keywords are mapped to entity sets in HM and associated with the solver entity. They are exported back as GES during export. In addition to the custom export options available in the export browser, several templates are available to export specific solver entities only as explained below. Template Name control_modeldoc ctrlvol groups_nsmas groups_rigwa groups_slint groups_secfo load materials property sensor Description Exports only the model documentation. Exports only the airbag and chamber definitions. Exports only the non-structural mass cards. Exports only the rigid wall cards. Exports only the sliding interface cards. Exports only the cross section cards. Exports only the load and load collector cards. Exports only the material cards. Exports only the property cards. Exports only the sensor cards.
Altair Engineering

sets curves parts
Exports only the PAM-CRASH 2G groups. Exports only the function cards. Exports only the part cards. PAM-CRASH 2G FE input reader cannot read input files prepared according to previous versions PAMCRASH. You must convert old files to the new format using the converter supplied by ESI.
Mass Calculations
The mass of each element is calculated by density * volume. Density is retrieved from the material associated with the elements component. Several assumptions are made in mass calculation based on PAMCRASH2G solver. For rigid bodies (RBODY) of type 3 with a user-imposed center of gravity and mass and inertia properties, the structural mass of the PART components are replaced by the rigid body mass. All other keywords besides the PART keyword are neglected in the RBODY type 3 mass calculation. Non-structural masses are not considered in the mass calculation panel (only structural masses are calculated). The following table summarizes how each supported element except shells and solid in the HyperMesh PAM-CRASH 2G interface performs these calculations: PAM-CRASH 2G Keyword MASS / SLIPR / RETRA / SENPT / PLINK / RBODY / NODCO / RBODY / NODCO / RBODY / SPRING / SPRGBM / 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 $RBODY_MASS 0 $RBODY_MASS 0 $RBODY_MASS Rigid body type 3 Material type 220. Material type 223. Rigid body type 3. Rigid body type 3. Area Volume Mass Notes

Altair Engineering
BAR /
Material types 200, 201, 202, 203, 204, and 205. 0 0 0 0
JOINT / KJOIN /
0 0
See also Importing Files Exporting Files Model Browser Solver Browser Connector Browser Include Files Using the Pam-Crash 2G Utility Menu Supported Pam-Crash 2G Keywords Unsupported Pam-Crash 2G Keywords Solver Conversion
Altair Engineering

PERMAS Solver Interface

The HyperMesh PERMAS interface enables you to: read in a PERMAS .dat file specify linear, nonlinear static and frequency analyses preview and edit PERMAS cards output a HyperView .h3d file for post-processing HyperMesh supports PERMAS .dat files for direct import. PERMAS .uci command files are not supported. The Permas interface supports names up to 40 characters in length. To import a PERMAS data file, see Importing an FE Model File in the HyperMesh documentation.
MPC ID Pools
The HyperMesh PERMAS Interface allows multipoint constraints (MPC) to use the same the ID as other elements, such as beams, shells or solids within HyperMesh. In other words, it can be said that selected elements and MPCs can use different ID pools. Some restrictions apply. To explain, a list of MPC types and which HyperMesh entity they are mapped to is provided: HyperMesh entity rigid MPC type RIGID SAME JOIN rbe3 equation group WLSCON GENERAL ISURFACE WLSSURFACE WLDSURFACE
While rigid and rbe3 elements use the same ID pool in HyperMesh, equations and groups have separate ones. Thus, it is possible to create duplicate IDs for MPCs as well. To resolve this, during export a solver option is available in the Export tab to renumber MPCs if duplicate IDs are present (Renumber MPCs if IDs are duplicated). This option will check for the highest rigid/rbe3 ID and renumber equation entities

Altair Engineering
accordingly. Groups are not included in the renumbering functionality as contact IDs would be affected by renumbering. Due to the mapping scheme explained above, it is possible to import MPCs with duplicate IDs; for example, MPC JOIN and GENERAL equation and groups although PERMAS does not allow it. Before working with your model, ensure that the PERMAS user profile is loaded. The user profile provides a customized HyperMesh environment for working with PERMAS.
See also Importing Files Exporting Files Model Browser Solver Browser Using the Permas Utility Menu Supported Permas Keywords
Altair Engineering

RADIOSS (Bulk Data), OptiStruct Interface

This section describes the RADIOSS (Bulk Data Format) and OptiStruct user profiles with the input translator, output template, and summary templates. RADIOSS and OptiStruct write result files directly. No result translator is needed. RADIOSS (Bulk Data Format) and OptiStruct are treated as a card image code. Follow these guidelines when creating a model for use with the RADIOSS (Bulk Data Format) and OptiStruct user profiles: Both the RADIOSS (Bulk Data Format) and OptiStruct user profiles are designed to support Altair RADIOSS and Altair OptiStruct, version 10.0, although several entries are unsupported. Elements of different types (solids, shells, bars, etc.) should be organized into separate components. This is most important for shell and solid elements where the component card image contains the referenced property definition. On importing an input file: The interface requires that continuation cards follow the referencing card. An error message is issued if the continuation card does not follow the referencing card. Warnings and error messages are displayed in an Import Process Messages pop-up window and are also written to a file in the current run directory called optistruct.msg. If a line in the input file that is not a continuation line and starts with a keyword that is not recognized or supported, then the entire card gets written to the appropriate unsupported card section (CTRL_UNSUPPORTED_CARD, SUBCASE_UNSUPPORTED or BULK_UNSUPPORTED_CARD). Also, if the name of a PARAM or DOPTPRM entry is unrecognized, it is stored as an UNSUPPORTED_PARAM or UNSUPPORTED_DOPTPRM, respectively. If the continuation line for a supported card is formatted incorrectly or if a certain feature for a recognized keyword is not supported, then the corresponding line gets written to the .hmx file. The bulk data input translator supports free, fixed and large field formats. Two templates are available for export and viewing (editing) RADIOSS (Bulk Data Format), OptiStruct data. The optistruct template outputs all cards in fixed format. The optistructlf template outputs certain cards in large field format with all other cards in fixed format (see Supported Cards for a list of those cards that are supported in large field format). HyperMesh reads and writes certain HyperMesh commands to the RADIOSS and OptiStruct input files as comments. These comment cards enable the preservation of pre-defined preferences across sessions. It is strongly suggested that users do not hand edit these cards. All settings necessary to interface with RADIOSS (Bulk Data Format) and OptiStruct can be loaded by their respective user profiles.
See also Importing Files Exporting Files

Altair Engineering
Model Browser Solver Browser Connector Browser Include Files Using the Radioss (Bulk) Utility Menu Supported Radioss (Bulk) Keywords Solver Conversion
Altair Engineering

RADIOSS (Block Format) Interface Overview

This section describes the HyperMesh RADIOSS (BLOCK) interface. HyperMesh provides a complete preprocessing environment for preparing RADIOSS (BLOCK) data decks for analysis. HyperMesh can read existing RADIOSS (BLOCK) decks, create a model, display and edit RADIOSS (BLOCK) cards as they will look in the deck, and write a deck for analysis. Although HyperMesh also offers limited post-processing capabilities in results translation you are strongly encouraged to exclusively use HyperView. To create RADIOSS (BLOCK) decks in HyperMesh, you must load the RADIOSS (BLOCK) user profile with the appropriate template to access the full pre-processing capability. The following are general comments about the HyperMesh Interface for RADIOSS(BLOCK) Import and Export The RADIOSS (BLOCK) interface supports RADIOSS (BLOCK) version 110
The RADIOSS (BLOCK) input translator can read solver decks with separate starter and engine file in the same folder or both starter and engine in one file. Also it can read separately starter and engine files. Use the solver options tab in the input browser to enable reading both engine and starter information placed in separate files. During the export the starter and engine files can be exported separately or merged as one file turning on corresponding check box in the export browser. Export The RADIOSS (BLOCK) interface in HM do not support RBODY definitions that are defined using GRNOD/BOX. Therefore, upon import they will be realized into sets GRNOD/NODE and exported with corresponding set.
Although majority of RADIOSS(BLOCK) keywords are supported, unsupported material and property if it exists in the deck are read into HyperMesh and exported maintaining its associative. All other unsupported portion of deck is mapped to unsupported cards in HM and appended at the end of deck during export. Most of IDs in the solver deck is preserved with introduction of ID pool concepts in HyperMesh. However solver cards mapped to Load collectors, Groups, Sensor, Airbag are renumbered if there is a conflict of ID among the keywords mapped to a HyperMesh entity. The new IDs are posted during the import process. RADIOSS(BLOCK) keywords GRNOD,GRSHEL, GRSH3N,GRBRIC,GRBEAM, GRTRUSS, GRSPRING are mapped across two HM entities Entity sets and Block. To avoid duplicate IDs in the deck. Keywords mapped to BLOCK HM entity are renumbered during export. RADIOSS (BLOCK) solver interface does not support positioning of dummies. Duplicate IDs Several RADIOSS (BLOCK) keywords are mapped to one HM entity in some

Altair Engineering
instances. By default HyperMesh RADIOSS (BLOCK) interface doesnt allow duplicate ID within same HM entity with exception of elements. While RADIOSS (BLOCK) allows duplicate IDs across cards mapped to one HM entity. In HyperMesh, ID flexibility similar to RADIOSS(BLOCK) can be enabled by switching on Duplicate ID option in Preferences pull down. Rigid body management RBODY created with less than 10000 slave nodes are shown with the spider connecting the master node to the slave nodes.If the RBODY has more than 10000 slave nodes then it is shown with a single link connecting master node to one of the slave node. All other options are similar for both.
Mass calculation
The mass of each element is calculated by density * volume. Density is retrieved from the material associated with the elements component. Currently mass calculation for RBODY, RBE3, RBE2 not supported.
See also Importing Files Exporting Files Model Browser Solver Browser Connector Browser Include Files Using the Radioss (Block) Utility Menu Supported Radioss (Block) Keywords Unsupported Radioss (Block) Keywords Solver Conversion
Altair Engineering

Supported Cards
The following cards are supported in RADIOSS (Block Format) 5.1, 9.0, 10.0 and 11.0:
Supported STARTER Cards in RADIOSS (Block Format) Supported ENGINE Cards in RADIOSS (Block Format)
See also Unsupported STARTER Cards in RADIOSS (Block Format) Unsupported ENGINE Cards in RADIOSS (Block Format)

Altair Engineering
Supported ENGINE Cards in RADIOSS (Block Format)

The supported RADIOSS D01 cards in RADIOSS (Block Format) 5.1, 9.0 and 10.0 are listed below. You can create these cards with the D01 macro in the RADIOSS (Block Format) Utility Menu.
/@ATFILE /ANIM /ANIM/BRICK/TENS /ANIM/BRICK/TENS/STRAIN /ANIM/BRICK/TENS/STRESS /ANIM/COMP /ANIM/DT /ANIM/Eltyp/FORC /ANIM/GZIP /ANIM/KEEPD /ANIM/MASS /ANIM/MAT /ANIM/NODA /ANIM/SENSOR /ANIM/SHELL/EPSP /ANIM/SHELL/TENS /ANIM/VECT /ANIM/VERS /ATFILE /BCS/ROT /BCS/TRA /BCSR/ROT /BCSR/TRA /DEL /DELINT /DEL/INTER /DT
Altair Engineering

/DT/Eltyp/lflag /DT/Eltyp/Keyword3/lflag /DT/SHELL /DT1/SHELL /DTIX /FUNCT /INIV/ROT /INIV/ROT/Keyword3/1 /INIV/TRA /INIV/TRA/Keyword3/1 /INTER /KEREL /KEREL/1 /KILL /MADYMO /MON /PARITH /PATRAN /PRINT /PROC /RBODY/ON /RBODY/OFF /RFILE /RUN /RUN/Run Name/Run Number/Restart Letter /STOP /TFILE /TITLE /VEL/ROT /VEL/TRA /VERS

Altair Engineering
Altair Engineering

Unsupported ENGINE Cards in RADIOSS (Block Format) 5.1, 9.0 and 10.0
The following D01 cards are not supported for RADIOSS (Block Format) 5.1, 9.0 and 10.0:
/ALE /ALE2 /ALE3 /ALE4 /ALESUB /ANIM/CUT/1 /ANIM/CUT/2 /ANIM/CUT/3 /ANIM/Eltyp/Restype /BCS/ALE /BCS/LAG /BCSR/ALE /BCSR/LAG /DAMP /DEL/Eltyp/1 /DT/SHNOD or /DT/SHNOD/CST /DT/SPHCEL /DYREL /DYREL/1 /FXINP /IMPL /IMPL/BUCK /IMPL/CHECK /IMPL/DT/1 /IMPL/DT/2 /IMPL/DT/STOP /IMPL/DTINI /IMPL/DYNA/1 IMPL/DYNA/2 /IMPL/INTER/KCOMP

Altair Engineering
/IMPL/LBFGS/L /IMPL/LINEAR /IMPL/LINEAR/INTER /IMPL/MONVOL/OFF /IMPL/NONLIN /IMPL/PREPAT /IMPL/PRINT/LINEAR /IMPL/PRINT/NONLIN /IMPL/QSTAT /IMPL/QSTAT/DTSCAL /IMPL/RREF /IMPL/SINIT /IMPL/SOLVER /IMPL/SPRING /IMPL/SPRBACK /INCMP /OUTP /RERUN /RIFLE/n /SHSUB /SHVER/V51 /STATE/DT /STATE/SHELL/AUX/FULL /STATE/SHELL/EPSP/FULL /STATE/SHELL/STRAIN/FULL /STATE/SHELL/STRESS/FULL /@TFILE /@TFILE/Keyword2 /TH/VERS /UPWM/SUPG /UPWM/TG /VEL/ALE
Altair Engineering

Samcef Interface
The Samcef interface enables you to : Samcef .sdb files are not supported Specify linear analysis (module ASEF) Export a .dat file. Warnings and error messages are written to a file named samcef.msg. Unrecognized lines are written to a *.hmx file. These files are created in the same directory from where HyperMesh is launched. The following commands are supported: Nodes (.NOE) Elements (.MAI) Property (.PHP, .BPR) Material (.MAT) Loads (.CLM) System (.FRA) Output request (.SAI) Hypothesis (.HYP) Entity Set (.SEL NOE, .SEL MAI) Contactsurfs (.SEL FACE) Composite definition (.PLI, .LAM, .ETA) Contact definition (.MCT, .STI)
See also Importing Files Exporting Files Model Browser Supported Samcef Keywords

Altair Engineering
Contact .MCT
The following table explains the link between the HyperMesh keywords and the parameters of the Samcef contact. If you need the complete definition of the card .MCT, please refer to the Samcef help. 1.
Selection of contact resolution method [Option_number] a) Uncoupled by default; write OPT 3 b) Coupled; write OPT 2.
2.
Sliding magnitude. [Contact_characteristics] The user can control this option by 2 choices: a) Moderate by default; nothing to write on MCT Card. b) Large ; NLIM -1 must be written on the MCT definition
3.
Initial gap Contact_characteristics . The user can control this option by 2 choices: a) As mesh is by default; nothing to write on the MCT definition b) No initial gap : UN3 1 must be written on the card definition.
4.
Contact offset Contact_characteristics . The user can control this option by 2 choices: a) As mesh is by default ; nothing to write on the MCT definition b) Contact offset user must enter a value XX ; DMIN XX must be written on the card definition.
5.
Kind of contact Contact_characteristics . The user can control this option by 2 choices : a) Standard by default ; nothing to write on the MCT definition
Altair Engineering

b) Normal direction glue : OPCO 2 must be written on the card definition.
Selection of Curvature smoothing contact faces [Smoothing_characteristics] a) Non activated by default. Nothing is written by default on MCT card b) Activated , write KSMO 1 on MCT card
Blank text line Additionnal_user_text. Enter free text on the current panel, on the Samcef MCT card. The text is saved with the contact definition in HyperMesh. Examples : .MCT I 10 GROUP 17 GTAR 23 OPT 3 ! Contact default .MCT I 20 GROUP 65 GTAR 12 OPT 2 NLIM -1 UN3 1 DMIN -0.0245 KSMO 1 ! Advanced contact .MCT I 30 GROUP 45 GTAR 75 OPT 2 UN3 1 OCPO 2 KSMO 1 ! Glue contact

Altair Engineering
Contact .STI
The following table explains the link between the HyperMesh keywords and the parameters of the Samcef contact. If you need the complete definition of the card .STI, please refer to the Samcef help. 1.
Selection of Node project [Option_number] a) Non activated by default ; write PROJ 0 b) Activated; nothing to write on STI card
Examples: .STI I 1 GROUP 17 23 PROJ 0 ! Glue default .STI I 2 GROUP 35 64 ! Advanced glue
Altair Engineering


HyperMesh 11.0 User Guide

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

HyperMesh 11.0 User Guide

Uploaded by

Copyright:

Available Formats

HyperWorks 11.

0 HyperMesh User Guide

Altair Engineering Contact Information

support@altairengineering.it support@altairjp.co.jp help@altair.co.kr support@altair.se support@uk.altair.com br_support@altair.com.br anzsupport@altair.com anzsupport@altair.com

Trademark and Registered Trademark Acknowledgments

Altair HyperMesh User's Guide

Altair HyperMesh User's Guide

Altair HyperMesh User's Guide

Altair HyperMesh User's Guide

Altair HyperMesh User's Guide

Altair HyperMesh User's Guide

Altair HyperMesh User's Guide

Altair HyperMesh User's Guide

Altair HyperMesh User's Guide

Altair HyperMesh User's Guide

Altair HyperMesh User's Guide

Altair HyperMesh User's Guide

Altair HyperMesh User's Guide

Altair HyperMesh User's Guide

Altair HyperMesh User's Guide

Altair HyperMesh User's Guide

Altair HyperMesh User's Guide

Altair HyperMesh User's Guide

Graphical User Interface

Altair HyperMesh User's Guide

Toolbar/Panel Changes in HyperMesh 11.0

Altair HyperMesh User's Guide

Standard Toolbar Changes

New 11.0 Location

Alternate Location (Pull down menus)

New File Model Session

Standard Toolbar Standard Toolbar Standard Toolbar

Standard Toolbar Standard Toolbar Standard Toolbar

Standard Toolbar Standard Toolbar Standard Toolbar

Standard Toolbar Standard Toolbar Standard Toolbar Standard Toolbar

Altair HyperMesh User's Guide

Pull-Down Only Pull-Down Only

Altair HyperMesh User's Guide

Standard Views Toolbar Changes

New 11.0 Location

Alternate Location (Pull down menus)

Standard Views Toolbar Standard Views Toolbar Standard Views Toolbar

Standard Views Toolbar Standard Views Toolbar

Altair HyperMesh User's Guide

Visualization Toolbar Changes

New 11.0 Location

Geometry Color Wireframe Geometry

Visualization Toolbar None Visualization Toolbar None

Visualization Toolbar None

Visualization Toolbar None

Visualization Toolbar None

Element Color Mode Wireframe Elements (skin only) Wireframe Elements

Visualization Toolbar None Visualization Toolbar None

Visualization Toolbar None

Visualization Toolbar None

Visualization Toolbar None

Visualization Toolbar None

Transparency Geom/Mesh Styles n/a

Altair HyperMesh User's Guide

has been removed.

to change styles for each component.

Shrink Elements Visualization Options

Visualization Toolbar None Visualization Toolbar None

Altair HyperMesh User's Guide