User Guide to the optimization code OptistructFull description
pipesimDescripción completa
rwetrkjhgFull description
VodiaFull description
Wastewater Network Analysis and Design Software Product. SewerGEMS is a fully dynamic, multi-platform, sanitary and combined sewer modeling solution. Engineers can analyze sanitary or combi…Description complète
Descripción completa
C:\AVEVA\Plant\PDMS12.0.SP6\Manuals\Docs
This is the official instruction manual for the Motorola-brand Model GM 338 Professional Mobile Radio for Conventional System. This version of the manual was published in 2010, and was scanned f...Full description
SaludosFull description
For inspiration to conduct investigationsFull description
Descrição: rwetrkjhg
Fibersim 15 userguide
EclipseDeskripsi lengkap
User guide for installing Liaison Dsc System.Full description
panduan sevima go feederFull description
Introduction to an excellent program for editing ones scans and PDFs.
HyperWorks 11.0 HyperMesh User Guide
Altair Engineering Contact Information Web site
www.altair.com
FTP site
Address: ftp.altair.com or ftp2.altair.com or http://ftp.altair.com/ftp Login: ftp Password:
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..............................................................................................................................37 and ply visualization HyperMesh tabs ...........................................................................................................................................40 HyperMesh Calculator ...........................................................................................................................................41 Browsers Basic...........................................................................................................................................44 Browser Operations 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
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
i
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..............................................................................................................................163 a Loadstep To Display a Loadstep ..............................................................................................................................165 To Rename, Renumber, Delete, or Edit the Card of a Loadstep ..............................................................................................................................166 To Edit..............................................................................................................................167 the Global Options of a Loadstep 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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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..............................................................................................................................205 Points Auto Connectors Macro ..............................................................................................................................206 Master..........................................................................................................................209 Weld Files Diameter vs. Thickness Files ..........................................................................................................................210 ACM Welds ..........................................................................................................................211 CWELD Elements ..........................................................................................................................214 Midsurf..............................................................................................................................215 Thickness 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..............................................................................................................................239 Order Midnodes 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
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
iii
Interface Tab ..........................................................................................................................263 Surface Tab ..........................................................................................................................290 Surface Interaction Tab ..........................................................................................................................330 Dummy..............................................................................................................................341 Positioning Process Manager 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..........................................................................................................................438 a Component Card 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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Altair Engineering
Part Replacement ..............................................................................................................................486 To use..............................................................................................................................492 the Convert To Rigid macro Convert..............................................................................................................................493 To Rigid Flow Chart 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..........................................................................................................................541 Create Nastran2 Page ..............................................................................................................................543 Convert Shells ..........................................................................................................................544 Display..........................................................................................................................545 SETs Tag on..........................................................................................................................546 Nodes 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
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
v
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..............................................................................................................................584 Groups 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..........................................................................................................................599 File Tool 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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Altair Engineering
RADIOSS (Bulk Data Format) Model Checker ..........................................................................................................................660 Opti Page ..............................................................................................................................663 Voxelmesh ..........................................................................................................................665 Matfrac..........................................................................................................................667 Reg. Volfrac ..........................................................................................................................668 PBAR,..........................................................................................................................669 PROD Opti. CBAR,..........................................................................................................................670 CROD Opti. Design..........................................................................................................................672 Variables Design..........................................................................................................................675 Constraints 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
Altair HyperMesh User's Guide Proprietary Inform ation of 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..........................................................................................................................1534 Reader Support SolidWorks Reader Support ..........................................................................................................................1535 STEP..........................................................................................................................1536 Reader Support Tribon..........................................................................................................................1537 Reader Support UG Reader Support ..........................................................................................................................1540 VDAFS Reader Support ..........................................................................................................................1543 CAD ..............................................................................................................................1544 Import Options
x
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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..........................................................................................................................1578 Import Options SolidWorks Import Options ..........................................................................................................................1583 STEP..........................................................................................................................1587 Import Options Tribon..........................................................................................................................1592 Import Options 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...........................................................................................................................................1642 Elements 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..........................................................................................................................1656 Biasing Exponential Biasing ..........................................................................................................................1657 Bellcurve Biasing ..........................................................................................................................1658
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of 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..............................................................................................................................1665 Shrink Wrap Mesh 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..............................................................................................................................1706 Organize & Cleanup - Tetramesh Process Manager Mesh..............................................................................................................................1708 User Defined Features - Tetramesh Process Manager Global..............................................................................................................................1709 Organize & Cleanup - Tetramesh Process Manager Global..............................................................................................................................1710 Mesh - Tetramesh Process Manager 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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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..........................................................................................................................1794 Options: Target Element Size, Import Model Tolerance, Extract Midsurface 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
Altair HyperMesh User's Guide Proprietary Inform ation of 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...........................................................................................................................................0 Templates FE...........................................................................................................................................1844 Configuration File 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..............................................................................................................................1960 a New Material: Review or Modify an Existing Material ..............................................................................................................................1962 Define..............................................................................................................................1963 a New Laminate Review and Modify an Existing Laminate ..............................................................................................................................1965 Define..............................................................................................................................1966 a New Design Variable Review and Modify an Existing Design Variable ..............................................................................................................................1967 HyperBeam ...........................................................................................................................................1968
xiv
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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..............................................................................................................................2039 Domains and Handles Local..............................................................................................................................2044 Domains and Handles Partitioning ..............................................................................................................................2051 Dependent Handles ..............................................................................................................................2053 Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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...........................................................................................................................................2209 Plots Module 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
Altair HyperMesh User's Guide Proprietary Inform ation of 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 Proprietary Inform ation of Altair Engineering
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..............................................................................................................................2357 - Free Body Diagrams 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
Altair HyperMesh User's Guide Proprietary Inform ation of 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
1
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
2
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 Location
Alternate Location (Pull down menus)
Standard Toolbar
File > New
Model
Standard Toolbar
File > New > Model
Session
Standard Toolbar
File > New > Session
Standard Toolbar
File > Open
Model
Standard Toolbar
File > Open > Model
Session
Standard Toolbar
File > Open > Session
Standard Toolbar
File > Save
Model
Standard Toolbar
File > Save > Model
Session
Standard Toolbar
File > Save > Session
Standard Toolbar
File > Import
Session
Standard Toolbar
File > Import > Session
Model
Standard Toolbar
File > Import > Model
Solver Deck
Standard Toolbar
File > Import > Solver Deck
New File
(varies)
Open File
(varies)
Save File
(varies)
Import
3
New 11.0
(varies)
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Altair Engineering
Geometry
Standard Toolbar
File > Import > Geometry
Connectors
Standard Toolbar
File > Import > Connectors
Standard Toolbar
File > Export
Model
Standard Toolbar
File > Export > Model
Solver Deck
Standard Toolbar
File > Export > Solver Deck
Geometry
Standard Toolbar
File > Export > Geometry
Connectors
Standard Toolbar
File > Export > Connectors
Curves
Standard Toolbar
File > Export > Curves
Standard Toolbar
File > Load > User Profile
Standard Toolbar
File > Load
Standard Toolbar
File > Load > Results
Export
(varies)
User Profile Load File
----
(varies)
Load Results Load Preference
----
Standard Toolbar
File > Load > Preference
Load Solver Template
----
Standard Toolbar
File > Load > Solver Template
Run Tcl/TK Script
----
Pull-Down Only
File > Run > Tcl/TK Script
Command File
----
Pull-Down Only
File > Run > Command File
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
4
Standard Views Toolbar Changes
Function
New 11.0 Location
Alternate Location (Pull down menus)
Previous View
Standard Views Toolbar
None
Fit Model
Standard Views Toolbar
None
Refresh Graphics Area (Plot Refresh)
Standard Views Toolbar
None
XY Top Plane View
Standard Views Toolbar
None
XY Bottom Plane View
Standard Views Toolbar
None
XZ Left Plane View
Standard Views Toolbar
None
XZ Right Plane View
Standard Views Toolbar
None
YZ Rear Plane View
Standard Views Toolbar
None
YZ Front Plane View
Standard Views Toolbar
None
Isometric View
Standard Views Toolbar
None
Reverse View
Standard Views Toolbar
None
User View/True View
Standard Views Toolbar
Model Browser Context Menu (Create > View)
5
Old 10.0
New 11.0
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Visualization Toolbar None
Wireframe Geometry
Visualization Toolbar None
Wireframe Geometry and Surface Lines
Visualization Toolbar None
Shaded Geometry and Surface Edges
Visualization Toolbar None
Shaded Geometry
Visualization Toolbar None
Element Color Mode
Visualization Toolbar None
Wireframe Elements (skin only)
Visualization Toolbar None
Wireframe Elements
Visualization Toolbar None
Shaded Elements and Mesh Lines
Visualization Toolbar None
Shaded Elements and Feature Lines
Visualization Toolbar None
Shaded Elements
Visualization Toolbar None
Transparency
Visualization Toolbar None
Geom/Mesh Styles
Altair Engineering
n/a
None: this legacy feature from pre-10.0
Use the Model Browser's optional FEStyle and GeomStyle columns
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
6
has been removed.
to change styles for each component.
Shrink Elements
Visualization Toolbar None
Visualization Options
Visualization Toolbar None
7
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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.
Geometry > Create > Nodes > Interpolate on Surface
On Geometry (plane)
Geometry > Create > Nodes > On Geometry
On Plane
Altair Engineering
New Icon
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
8
10.0 Lines Panel
Subpanels
New Icon
New 11.0 Name
Alternate Location (Pull down menus)
Linear Nodes
Geometry > Create > Lines > Linear Nodes
Standard Nodes
Geometry > Create > Lines > Standard Nodes
Smooth Nodes
Geometry > Create > Lines > Smooth Nodes
Controlled Nodes
Geometry > Create > Lines > Controlled Nodes
Offset
Geometry > Create > Lines > Offset
Midline
Geometry > Create > Lines > Midline
From Surf Edges
Extract edge
Geometry > Create > Lines > Extract Edge
From Features
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
From Nodes
Offset
10.0 Circles Panel Note:
9
The Circles panel no longer exists. Its features have been moved entirely into the Lines, Nodes, and new Free Points panels.
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Altair Engineering
Subpanels
New Icon
New 11.0 Name
Alternate Location (Pull down menus)
Lines Panel > Arc Center and Radius
Geometry > Create > Lines > Arc Center and Radius
Lines Panel > Circle Center and Radius
Geometry > Create > Lines > Circle Center and Radius
Lines Panel > Arc Nodes and Vector
Geometry > Create > Lines > Arc Nodes and Vector
Lines Panel > Circle Nodes and Vector
Geometry > Create > Lines > Circle Nodes and Vector
Lines Panel > Arc Three Nodes
Geometry > Create > Lines > Arc Three Nodes
Lines Panel > Circle Three Nodes
Geometry > Create > Lines > Circle Three Nodes
Nodes Panel > Arc Center
Geometry > Create > Nodes > Arc Center
Points Panel > Arc Center
Geometry > Create > Free Points > Arc Center
New 11.0 Name
Alternate Location (Pull down menus)
Ruled
Ruled
Geometry > Create > Surfaces > Ruled
Spline/Filler
Spline/Filler
Geometry > Create > Surfaces > Spline/Filler
Skin
Skin
Geometry > Create > Surfaces > Skin
Center & Radius
Points & Vector
Three Points
Find Center
10.0 Surfaces Panel
Subpanels
Altair Engineering
New Icon
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
10
Drag/Spin
Drag along Vector
Geometry > Create > Surfaces > Drag Along Vector
Drag Along Line
Geometry > Create > Surfaces > Drag Along Line
Drag Along Normal
Geometry > Create > Surfaces > Drag Along Normal
Spin
Geometry > Create > Surfaces > Spin
From FE
From FE
Geometry > Create > Surfaces > From FE
Fillets
Fillet
Geometry > Create > Surfaces > Fillet
New 11.0 Name
Alternate Location (Pull down menus)
Bounding Surfs
Bounding Surfaces
Geometry > Create > Solids > Bounding Surfaces
Drag Along Vector
Drag Along Vector
Geometry > Create > Solids > Drag Along Vector
Drag Along Normal
Drag Along Normal
Geometry > Create > Solids > Drag Along Normal
Drag Along Line
Drag Along Line
Geometry > Create > Solids > Drag Along Line
Spin
Spin
Geometry > Create > Solids > Spin
10.0 Solids Panel
Subpanels
New Icon
10.0 Primitives Panel Note:
11
The Primitives panel no longer exists; its functions have been entirely migrated to the Surfaces and Solids panels.
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Altair Engineering
Subpanels
Square/Block
Cylinder/Cone
Sphere
New Icon
New 11.0 Name
Alternate Location (Pull down menus)
Surfaces > Square
Geometry > Create > Surfaces > Square
Solids > Block
Geometry > Create > Solids > Block
Surfaces > Cylinder Full
Geometry > Create > Surfaces > Cylinder Full
Surfaces > Cylinder Partial
Geometry > Create > Surfaces > Cylinder Partial
Surfaces > Cone Full
Geometry > Create > Surfaces > Cone Full
Surfaces > Cone Partial
Geometry > Create > Surfaces > Cone Partial
Solids > Cylinder Full
Geometry > Create > Solids > Cylinder Full
Solids > Cylinder Partial
Geometry > Create > Solids > Cylinder Partial
Solids > Cone Full
Geometry > Create > Solids > Cone Full
Solids > Cone Partial
Geometry > Create > Solids > Cone Partial
Surfaces > Sphere Center and Radius
Geometry > Create > Surfaces > Sphere Center and Radius
Surfaces > Sphere Four Nodes
Geometry > Create > Surfaces > Sphere Four Nodes
Surfaces > Sphere Partial
Geometry > Create > Surfaces > Sphere Partial
Solids > Sphere Center Geometry > Create > Solids > Sphere Center and Radius and Raidus
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
12
Torus
Solids > Sphere Four Nodes
Geometry > Create > Solids > Sphere Four Nodes
Surfaces > Torus Center and Radius
Geometry > Create > Surfaces > Torus Center and Radius
Surfaces > Torus Three Geometry > Create > Surfaces > Torus Three Nodes Nodes
13
Surfaces > Torus Partial
Geometry > Create > Surfaces > Torus Partial
Solids > Torus Center and Radius
Geometry > Create > Solids > Torus Center and Radius
Solids > Torus three Nodes
Geometry > Create > Solids > Torus Three Nodes
Solids > Torus Partial
Geometry > Create > Solids > Torus Partial
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Edges of surfaces that do not connect to any other surfaces.
shared edges
Edges of surfaces that connect to one other surface.
suppressed edges
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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
Fin faces are surfaces that split a 3D solid entity, but only partway through-they do not actually extend through the entire entity.
bounding faces
The outer faces of solid entity.
full partition faces
The faces of adjoined solids
2d faces (topo)
When using the by 2D topo visualization mode, this is the color of 2D faces that aren't part of a solid.
ignored (topo)
The color of 2D faces when using the by 2D topo visualization mode.
edges (comp)
Mesh edges when coloring mesh with the by comp visualization mode.
by mappable display control (solids) 1 dir. map
Visualization for solids that can be mapped (for 3D meshing) in one direction.
3 dir. map
Visualization for solids that can be mapped (for 3D meshing) in three directions.
ignored map
Default visualization for solids that require partitioning to become mappable.
not 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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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
19
These items are marked with a triangular arrow. Selecting a submenu heading opens a sub-menu of options related to the sub-
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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.
Command
Most menu items simply execute a command when selected, such as accessing a specific HyperMesh panel.
There are multiple ways to select a pull-down menu or a menu item within it: Mouse
Click the menu or menu item with the mouse.
Keyboard (menu)
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
Tools for masking, deleting, or finding entities.
View
Change the angle of view on the model, lighting, or visibility and location of tab area items, among other options.
Collectors
Tools for creating and renaming collectors, assemblies, etc.
Geometry
Tools for geometry editing and cleanup.
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
20
Mesh
Meshing tools, such as automesh, tetramesh, solid map, element edit, etc.
Connectors
Create, edit, realize/unrealize, and manipulate various types of connectors.
Materials
Create, edit, and assign Material cards to components.
Properties
Create, edit, and assign Property cards to components.
BCs
Boundary Conditions such as forces, pressures, moments, or constraints.
Setup
Model properties such as materials, connectors, and contact surfaces.
Tools
Morph, Rotate, Translate, Reflect, or Scale entities, among other options.
Morphing
Create, edit, and manipulate mesh-morphing entities with HyperMorph.
Post
View results of solved simulations (contour or vector plots, for example).
XY Plots
Create plots (graphs) of simulation qualities and/or results.
Preferences
HyperMesh preferences such as User Profiles, global options, and keyboard configuration.
Applications
Quickly access other HyperWorks programs, such as OptiStruct.
Help
Access the on-line Help system.
21
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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
Assemblies
Left-click to open the Assemblies panel.
Same
Component s
Left-click to open the Components panel.
Same
Materials
Left-click to open the Materials panel.
Same
Properties
Left-click to open the Properties panel.
Same
Load Collectors
Left-click to open the Load Collectors panel
Same
System Collectors
Left-click to open the System Collector, Vector Collector, BeamSection Collector, or MultiBody panels.
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 icon’s left-click behavior. arrow
Left-click to open the Delete panel.
Same
Vector Collectors
BeamSectio n Collectors
MultiBodies Delete
23
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Altair Engineering
Card Edit
Left-click to open the Card Edit panel.
Same
Organize
Left-click to open the Organize panel.
Same
Renumber
Left-click to open the Renumber panel.
Same
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of 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
25
Left-click
LEFT Behavior
Right-click RIGHT Behavior
Distance
Opens the Distance panel
Same
Length
Opens the Length panel
Same
Mass/Area Calc
Opens the Mass Calc panel
Same
Edges
Opens the Edges panel
Same
Features
Opens the Features panel
Same
Faces
Opens the Faces panel
Same
Normals
Opens the Normals panel
Same
Penetration/ Opens the Penetration panel Intersection Check
Same
Check Elements
Opens the Check Elements panel
Same
Model Summary
Opens the Summary panel
Same
Loads Summation
Opens the Loads Summary tab
Same
Count
Opens the Count panel
Same
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Altair Engineering
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of 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
27
Left-click
LEFT Behavior
Right-click RIGHT Behavior
Mask
Opens the Mask panel
Same
Reverse Elements
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 Adjacent
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
Unmask all entities (elements, loads, etc…) in currently displayed collectors.
Mask Not Shown
Mask all entities (elements, Unmask loads, etc…) located outside of Shown the graphics area but in currently displayed collectors.
Same
Unmask all entities (elements, loads, etc…) located outside of the graphics area but in currently
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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.
Same
Find
Open the Find panel
Same
Display Numbers
Open the Numbers panel
Same
Display Element Handles
Toggle element handles on/off. The same operation can be performed from the Graphics subpanel located in the Preferences > Graphics menu.
Same
Display Load Handles
Toggle load handles on/off. The same operation can be performed from the Graphics subpanel located in the Preferences > Graphics menu.
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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 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.
29
Same
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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.
Same
Arrow (lower-right): Select option from menu
Shaded Button: set geometry mode to shaded. Geome Arrow (lower-right): Select option from try menu Wirefra me Geome try with Surface s Lines
Altair Engineering
Same
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
Same
Transp arency
Opens the Transparency panel
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 HyperMesh User's Guide Proprietary Inform ation of 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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Altair Engineering
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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
32
set new current icon and perform icon’s 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.
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.
33
Right-click to expand Options Menu; Left-click an icon to set new current icon and perform icon’s left behavior.
Select option from menu
Right-click to expand Options Menu; Left-click an icon to set new current icon and perform icon’s left behavior.
Select option from menu
Right-click to expand Options Menu; Left-click an icon to set new current icon and perform icon’s left behavior.
Select option from
Right-click to expand Options
Left-click the lower right arrow to expand the Options Menu.
Shaded Set current element visual mode to Elemen shaded. Elements are shaded, but no ts lines display.
Wirefra me Elemen ts (skin only)
Select option from menu
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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 icon’s left behavior.
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.
Select option from menu
Right-click to expand Options Menu; Left-click an icon to set new current icon and perform icon’s left behavior.
Traditio Display only the simple elements for nal 2D beams and similar entities. Elemen t Repres entatio n
Select option from menu
Right-click to expand Options Menu; Left-click an icon to set new current icon and perform icon’s left behavior.
3D Elemen t Repres entatio n
Select option from menu
Right-click to expand Options Menu; Left-click an icon to set new current icon and perform icon’s left behavior.
Select
Right-click
Left-click the lower right arrow to expand the Options Menu.
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,
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of 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 icon’s left behavior.
Layers off
Ply layers are not displayed.
Select option from menu
Right-click to expand Options Menu; Left-click an icon to set new current icon and perform the icon’s left behavior.
Select option from menu
Right-click to expand Options Menu; Left-click an icon to set new current icon and perform the icon’s left behavior.
Select option from menu
Right-click to expand Options Menu; Left-click an icon to set new current icon and perform
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
35
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Altair Engineering
button. See Element and ply visualization for details.
the icon’s 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
Altair Engineering
Left-click the tool button to open Visualization Controls tab.
Same
Altair HyperMesh User's Guide Proprietary Inform ation of 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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Altair Engineering
3D element Representation:
Layers off
Composite Layers
Layers w ith fiber direction
Traditional and 3D Representation:
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
38
Layers off
Composite Layers
Layers w ith fiber direction
39
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
46
Filtering Entities You can filter the entity types that appear in the browser’s 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 browser’s 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 browser’s 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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Altair Engineering
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of 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 Browser’s 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 , 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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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".
Whole Names
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.
Use Wildcards
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
Altair Engineering
Using this option allows you to type an entity ID into the Find: box instead
Altair HyperMesh User's Guide Proprietary Inform ation of 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 browser’s 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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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 -click and -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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Effect
1st link entity
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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
61
When this option is active, all realizations belonging to the determined linked connector entities will be taken into account for
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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
Left-Click behavior
Right-Click behavior
Show/Hide
Show connectors between the selected entities.
Hide connectors between the selected entities.
Isolate/ Isolate Only
Isolate the selected entities and the connectors between them.
Isolate only the connectors between the selected entities.
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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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 -click and -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.
Find Between / Find Between with FE
is active, Find Attached changes to Find Attached
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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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.
Hide
Works exactly like the action button Hide. All view option button settings are considered.
Isolate
Works exactly like the action button Isolate. All view option button settings are considered.
Isolate Only
Works exactly like the action button Isolate Only. All view option button settings are considered.
Show find / Hide find
Reveals or hides the Find box described in Finding Entities under Basic Browser Operations.
Configure Browser
Opens the Link Entity Browser configuration window.
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of 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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Altair Engineering
The following connector details are displayed as column data in the browser tree: Entities
Layer
ID of the connector and an image that represents the respective connector’s 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).
Tolerance
The realization tolerance of the connector. You can change this by right-clicking the field and typing in a new value, then pressing .
Component
The name of the component to which the connector belongs (this column is not displayed in default view).
Link(Number)
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 entity’s 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.
If you left-click and hold the mouse button on a link, the relevant component (part) highlights in the model:
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of 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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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 doesn’t 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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Left-Click behavior
Right-Click behavior
Show/Hide
Show twin connectors.
Hide twin connectors.
Isolate/ Isolate Only
Isolate 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
Altair HyperMesh User's Guide Proprietary Inform ation of 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:
83
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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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.
Delete
This accesses a sub-menu with options to delete connectors or connectors and their related FE elements.
Renumber
Allows a single connector to be renumbered; the change is permanently recorded in the database and the browser.
Update layer
Opens a dialog to input the layer value that you wish to assign to the selected connectors (this function works for multiple selections).
Simply type the desired number of layers into the text box and press . 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
85
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.
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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.
Remove Links
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.
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 an HM connector panel.
Unrealize
Altair Engineering
Unrealizes the selected connectors.
Altair HyperMesh User's Guide Proprietary Inform ation of 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.
Hide
Works exactly like the action button Hide. All view option button settings are considered.
Isolate
Works exactly like the action button Isolate. All view option button settings are considered.
Isolate Only
Works exactly like the action button Isolate Only. All view option button settings are considered.
Show find / Hide find
Activates a new tool set used to perform searches. This works exactly the same as described in Finding Entities.
Collapse All
This option closes all the expanded folders in the browser.
Expand All
This option expands all the folders to display all the connectors. This operation may take some time for folders that contain thousands of connectors.
Configure Browser
Opens the Connector Entity Browser configuration window which contains options to configure the Connector Browser's list display and button behavior.
See also *CE_Realize FE Absorb Connectors panel
87
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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:
89
-
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.
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
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.
Link ID/name
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.
Link Rule
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 link’s 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.
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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.
4.
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.
5.
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.
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of 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.
95
Click the Add button to acknowledge and execute the operation.
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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.
Open the default context menu by right-clicking in the Entities column of the tree list.
3.
Select the Remove Links option to confirm and execute the operation.
To remove specific links from connectors 1.
Select the link that needs to be removed
2.
Right-click a link (not a connector) in the tree list to bring up the remove link context menu.
3.
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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 link’s 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.
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.
2.
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.
Right-click to open the context menu, and select update link.
4.
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.
5.
Click on the Update button and acknowledge.
Notes: The link column for the selected connectors will now display the modified information. The connector’s state remains unchanged.
Example The following screenshots illustrate a link rule modification.
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of 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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Altair Engineering
The new ly replaced link rule is underlined in blue.
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of 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.
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.
1.
Open the Configure Browser window (browser context menu) and select view extended link information.
2.
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.
Right-click to open the context menu, and select update link.
4.
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.
5.
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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
104
The new ly replaced link state is underlined in blue.
105
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
106
2.
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.
107
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.
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Altair Engineering
See also *CE Realize FE Absorb Utility connector panel
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of 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.
If the realized welds of the connectors also need to be displayed in graphics then activate the 2.
button.
Either: -
Ensure that the Show/Hide button ( entity,
) is active in Show mode, and then click the desired link
or -
use the selector
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.
111
button.
Use the Link Entity Browser Advanced Action Buttons to show or isolate the shared connectors.
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Altair Engineering
Find Connectors from Realizations 1.
Select the desired link entites from the link entity browser list or the graphics area.
2.
Click the button in the utility tool set (at the bottom of the Connector Browser) to open an elements selection panel.
3.
Click proceed in the panel.
4.
The connectors that contain the selected elements as their realized welds will be highlight in the browser.
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of 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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Available for:
Description
Set Active
Permanently
Sets the currently selected entities in the browser to the active state.
Set Active Only
Permanently
Sets the entities currently selected in each folder to the active state and sets the remaining entities in those folders to the inactive state.
Set Inactive
Permanently
Sets the currently selected entities in the browser to the inactive state.
Set Inactive Only
Permanently
Sets the entities currently selected in each folder to the inactive state and sets the remaining entities in those folders to the active state.
Set Export
Permanently
Sets the currently selected entities in the browser to the export state.
Set Export Only
Permanently
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.
Set Do Not Export
Permanently
Sets the currently selected entities in the browser to the do not export state.
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of 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.
Collapse All
All
Closes all of the folders in the tree structure, so that only the top-most level of items displays.
Expand All
All
Opens all of the folders in the entire tree structure, exposing every item nested at every level.
Show Find
All
Turns the browser Find on/off functionality – see Find section for more information
Show Filter
All
Turns the browser Filter functionality on/off – see Filter section for more information
Columns
All
This allows you to hide or show the various columns in the tree control.
Configure Browser…
All
Opens the Entity State Browser’s Browser Configuration window, which allows you to determine what entities display in the tree as well as which columns the browser displays.
117
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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 assembly’s 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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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 and 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
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
120
See also Model Browser Configuration window HyperMesh Environment Tab Area
121
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Altair Engineering
Property View: Both
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
136
Property View: Indirect only
137
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Altair Engineering
Property View: Direct only
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
138
See Also Direct/Indirect Property Assignment Model Browser Views
139
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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:
141
These buttons only affect the display state. They do not actually remove entities from the model, but only show or hide them.
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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 assembly’s display control icon displays all of its contents. Activating an assembly’s 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 entity’s color without using the Color panel. The currently assigned color displays in the
column.
To change an entity’s 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
Altair HyperMesh User's Guide Proprietary Inform ation of 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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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. + left-click to use window selection to highlight or select multiple entities. Right-click an entity to deselect it. + 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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Altair Engineering
Left-click to select & highlight an entity in the browser – the entity is also highlighted in graphics area. + 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. + 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
Altair HyperMesh User's Guide Proprietary Inform ation of 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. -clicks and -clicks are supported in the browser list; window selections (+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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Altair Engineering
browser (use the local entity controls found inside the browser's tree structure for browser display control). Note:
When using window selection (-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
+ left-click-and-drag uses window selection to turn on multiple entities in the display.
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
148
+ 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:
149
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
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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. + 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. + 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
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
150
Note:
When using window selection (+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. + 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 + left-clicking on them a second time. + 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 -clicks or -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:
151
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.
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Altair Engineering
Context-Sensitive Menu Clicking the right mouse button on a folder or entity within the browser’s 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.
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
Assembly, Beamsection Collector,
Opens the Edit dialog, containing the selected entities' information so that you can make any necessary changes.
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Opens a dialog used to assign properties and materials to the selected components.
Organize
Components, Materials, Properties
Moves the selected entities to the current include, component, or load collector as appropriate.
Delete
All except the toplevel of Assemblies
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.
Rename
All
Any item can be renamed by entering a new name in the name text field and pressing , 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 . The high-level entity folders are non-editable, but folders containing the assembly hierarchy can be renamed.
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.
Show
All
Displays the item in the graphics area. This selection affects each item’s 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
153
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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 item’s 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.
Isolate Only
All
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).
Remove
Components
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.
Collapse All
All
Closes all of the folders in the tree structure, so that only the topmost level of items displays.
Expand All
All
Opens all of the folders in the entire tree structure, exposing every item nested at every level.
Show Find
All
Turns the Browser Find on/off functionality – see Find section for more information.
Show Filter
All
Turns the Browser Filter functionality on/off – see Filter section for more information.
Include File Options...
(Include View only)
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
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of 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
(Include View only)
Exports the contents of the selected include into the chosen file name.
Export All Includes
(Include View only)
Exports all the includes with their corresponding content (not the master model - only the includes)
Columns
All
This allows you to hide or show the Color, FE Styles, and Geometry Styles columns in the tree control.
Configure Browser…
All
Opens the Model Browser’s Browser Configuration window, which allows you to determine what entities display in the tree as well as which columns the browser displays.
155
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Altair Engineering
Configuring the Model Browser This window opens when you select the Configure Browser… option from the Model Browser’s 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
Altair HyperMesh User's Guide Proprietary Inform ation of 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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
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.
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
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
158
Tab Area
159
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Altair Engineering
Loadsteps Browser: OptiStruct & Nastran Profiles The browser’s 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.
Edit options
Depending on the entity selected, this will bring up an appropriate GUI for editing of the loadstep or control card information.
Edit card
Review the selected entity in the HM card editor.
Delete
Delete the selected entity or entities.
Rename
Rename the selected entity.
Renumber
Renumber the selected entity.
Summary table
Generates a summary table of the selected loadsteps.
BCs Contour
This launches the BCs Contour utility and automatically selects the loadcols associated with the selected loadstep.
Loads Summary
This launches the Loads Summary utility and automatically selects the loadcols associated with the selected loadstep.
Collapse all/selection
Collapses all selected folders and subfolders, or all folders if none are selected.
Expand all/selection
Expands all selected folders and subfolders, or all folders if none are selected.
Auto-manage load references
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.
OptiStruct
Opens the OptiStruct panel in HyperMesh.
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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:
161
When you first open the Loadsteps Browser, all of the loadsteps in the model default to the blank (unchecked) state.
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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 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 doesn’t exist in the database
5.
To remove a loadcol from the load reference, select the loadcol in the right table and use the left arrow to remove the loadcol.
6.
To select multiple loadcols, use the all/none/reverse buttons where appropriate. These buttons select loadcols from the currently active table.
7.
Right-click options allow for additional functionality depending on the current selection.
163
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Altair Engineering
The Add 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
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
164
To Display a Loadstep 1.
Check/uncheck the display checkbox next to the loadstep of interest.
2.
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:
165
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.
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Altair Engineering
To Rename, Renumber, Delete, or Edit the Card of a Loadstep 1.
Right click on the appropriate loadstep or loadcol.
2.
Select the desired option from the popup menu.
3.
For renaming and renumbering, an entry box appears so that you can enter the appropriate information in the browser.
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of 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 loadstep’s folder or sub-folder.
167
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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_#). 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
Altair HyperMesh User's Guide Proprietary Inform ation of 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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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
Available for:
Description
Collapse All
All
Closes all of the folders in the tree structure, so that only the top-most level of items displays.
Expand All
All
Opens all of the folders in the entire tree structure, exposing every item nested at every level.
Morph operates on all elements / Morph operates on displayed elements
All
Determines whether the masking operations for morph entities apply to all/displayed elements.
171
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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 -click and -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 . 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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Altair Engineering
Context Sensitive Menu 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
Altair HyperMesh User's Guide Proprietary Inform ation of 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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Altair Engineering
See also Browsers HyperMesh Entities and Solver Support Interfacing with External Products
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of 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 application’s 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
Populates the Display page of the Utility Menu.
geommeshpage.mac
Populates the Geom/Mesh page of the Utility Menu.
globalpage.mac
Creates the button group that allows you to switch pages.
qamodelpage.mac
Populates the QA/Model page of the Utility Menu.
userpage.mac
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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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 page’s 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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Jacob (Jacobian)
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
Warp (warpage)
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
Aspect (aspect ratio)
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
Max ang: Q (quad)
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
Max ang: T (tria)
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
Min ang: Q (quad)
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
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of 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.
Find Attached
Finds all of the elements attached to the displayed elements.
Remesh
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.
Smooth
Allows you to apply the smoothing algorithm to the selected elements plus one, two, or three attached layers of elements (one button for each).
Quality Report
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.
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.
BOM Comparison Tool
Reads a generic Bill Of Materials file and provides an interface to manipulate data in the BOM as well as the corresponding FE model.
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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Altair Engineering
Find Elems>>Loads
Automatically finds all elements directly attached to any and all load indicators. If masked, these elements are un-masked.
Find Comps>>Loads
Automatically finds all components directly attached to any and all load indicators. If masked, these comps are un-masked.
Find Loads>>Comps
Automatically finds all loads directly attached to a selected component. If masked, these loads are un-masked.
Find Elems>>Connectors
Automatically finds all elements directly attached to any and all connectors. If masked, these elements are un-masked.
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of 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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Altair Engineering
BOM Comparison Tool GUI The BOM Comparison Tool’s 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.
Tree section:
Contains a tree structure displaying part names and IDs.
Master column:
Contains master column selection.
BOM display section:
This section contains a table to display BOM info as it is seen in the actual BOM file.
Metadata display section:
Contains options for metadata management.
Failed records section:
Displays failed records from a loaded BOM file.
Display filter section:
Contains filtering options for displaying tree and table info; part of the tree section.
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
188
189
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Altair Engineering
BOM Comparison Tool Control Section This portion of the interface contains drop-down menus and the toolbar. File menu
New
Create a new session
Open
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.
Edit menu
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 Section’s table. Invalid records can be edited to form valid data and can be moved to the BOM Display table.
Save and Export
Save and export the current information shown in the BOM Display section as a new BOM csv file in a user selected location.
Exit
Close the BOM Comparison Tool.
Update Model
Update the model attributes to match the BOM.
Complete BOM
Sometimes the BOM doesn’t 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
Altair Engineering
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).
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
190
View menu
BOM View
Display section displays BOM info as it appears in the BOM file.
Compare View
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.
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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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 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:
(Select All)
Displays all the branches in the tree and the associated data in the BOM display table
(Select None)
Switch off all the branches in the tree and delete all the data in the BOM display table
(Reverse selection)
Switch on all the "off" branches in the tree and vice versa. Data associated with switched-on branches displays in the BOM display table
(Show displayed)
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
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
192
193
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
196
197
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Clear the table if already some data exists
Metadata related to BOM
Display BOM related metadata for the selected row in the BOM display table
All metadata
Display all the metadata for the selected row in the BOM display table
Differences between BOM/metadata
Display two rows of info in the metadata table. First row corresponds to BOM info, second row corresponds to metadata associated with the model
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of 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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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.
Project points
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.
Isolate Surface
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.
ThinSolid=>Midsurf
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.
Adj Circ Pts
Places four additional fixed points on an inner line, and then projects those points to a concentric line, creating a higher quality mesh.
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.
Midsurf Thickness
Assigns the thickness of a midsurface geometry to FE properties or elements. Its primary use cases are solid parts with varying thickness.
201
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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.
Fix 2nd Order Midnodes
Improves element quality by moving the mid-edge nodes of second order elements.
Fix Sliver Tetra 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.
Add Washer
Creates a layer of washer elements around a circular hole in the mesh.
Trim Hole
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.
Fill 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.
Box Trim
Trims the model along user-defined trim lines. This is useful for reducing the model size by taking advantage of symmetry etc.
Bead
Creates a bead of a given height and width along the selected two nodes and connects to the surrounding mesh.
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of 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.
Select Edges
Clicking this button displays a line selector in the panel area. Use the lines selector to choose the edges you wish preserved.
Show Preserved
Click this button to highlight the lines already marked for preservation.
Comps selection boundary
When active, this checkbox prevents the auto-cleanup function from equivalencing the boundaries between adjacent components.
Select comps
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.
Clear all edges
Removes all edges from the preservation list.
Save preserved
Saves the preservation state, so that autocleanup and BatchMesher will know which lines must be preserved.
203
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Accepts any changes you’ve made and closes the pop-up window.
Cancel
Discards any changes you’ve made and closes the pop-up window.
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of 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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Altair Engineering
Build systems Snap to node Attach to shells
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of 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
1t/2t/3t
X
Y
Z
PartId1
PartId2
12::
2::
2.25:
2.25::
1.0::
2::
3::
23::
3::
3.05::
3.25::
0.25::
2::
3::
209
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
PartId3
5::
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
Maximum thickness
Nugget diameter
1.4
1.9
7
2.0
3.0
8
The nugget diameter is 7.0 for the thickness range of 1.4 to 1.99.
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of 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.
Project to shell
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.
The figures below show ACM created using the two currently available methods.
ACM creation using (T1+T2)/2.0 option
211
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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.
Make sure that the connectors are created at each of the weld locations along with connecting parts information.
2.
Make sure all the connecting parts have PSHELL cards with correct thicknesses.
3.
Select the connectors to be realized as ACMs in the FE Realize panel of the Connectors module.
4.
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.
5.
Set the appropriate tolerance (proj tol=) value.
6.
Make sure the attach to shell and snap to node options are turned off in fe options….
7.
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
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
212
8.
213
Click realize.
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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.
2.
Assigns to the elements that have thickness values within the specified ranges, based on the value of the Organization Method, the relevant property.
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.
2.
Assigns to property to its corresponding component.
3.
Removes any property assignments to the elements.
4.
Organizes the elements that have thickness values within the specified ranges into the new components based on the value of the Organization Method.
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
Altair Engineering
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 HyperMesh User's Guide Proprietary Inform ation of 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.
Gauge file – You must specify the thickness range intervals in a Gauge File. Click here for details on the format of the gauge file.
2.
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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Altair Engineering
Upper limit = (tolerance / 2) + (tolerance* (i + 1)) Assigned value = tolerance*(i+1) Where i = 0……n, 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.
Contour
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
Altair Engineering
Closes the tab.
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
218
To assign thickness and z-offset values using the Elements option 1.
Change to your preferred user profile.
2.
Load the desired model file.
3.
Access the Midsurf thickness… utility from the Geom/Mesh page of the Utility Menu.
4.
Select the Elements option.
5.
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.
6.
Click the Assign button to open the element selection panel.
7.
Select the elements to map the midsurface thickness onto.
8.
Click the proceed button to perform the thickness mapping.
219
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Altair Engineering
To assign thickness and z-offset values using the Properties on Components option 1.
Change to your preferred user profile.
2.
Load the desired model file.
3.
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.
4.
Access the Midsurf thickness… utility from the Geom/Mesh page of the Utility Menu.
5.
Select the Properties on components option.
6.
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.
7.
Select a Thickness calculation method.
8.
Select a Component organization method and either select a file or enter a tolerance based on the method.
9.
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
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
220
To assign thickness and z-offset values using the Properties on Elements option 1.
Change to your preferred user profile.
2.
Load the desired model file.
3.
Create the base property "t0" and assign the base property the relevant card image. Enter any default values for this card.
4.
Access the Midsurf thickness… utility from the Geom/Mesh page of the Utility Menu.
5.
Select the Properties on elements option.
6.
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.
7.
Select a Thickness calculation method.
8.
Select a Component organization method and either select a file or enter a tolerance based on the method.
9.
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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Altair Engineering
To organize elements using the Organize Only option 1.
Change to your preferred user profile.
2.
Load the desired model file.
3.
Create the base component "t0".
4.
Access the Midsurf thickness… utility from the Geom/Mesh page of the Utility Menu.
5.
Select the Organize only option.
6.
Click the Assign button to open the element selection panel.
7.
Select the elements to organize.
8.
Click the proceed button to perform the organization.
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
222
To contour thickness and z-offset values using the Elements option 1.
Change to your preferred user profile.
2.
Load the desired model file.
3.
Access the Midsurf thickness… utility from the Geom/Mesh page of the Utility Menu.
4.
Select the Elements option.
5.
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.
6.
Click the Contour button to open the node selection panel.
7.
Optional: Select nodes to generate the midsurface thickness contour.
8.
Click the proceed button to open the element selection panel.
9.
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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Altair Engineering
To contour thickness and z-offset values using the Properties on Components option 1.
Change to your preferred user profile.
2.
Load the desired model file.
3.
Access the Midsurf thickness… utility from the Geom/Mesh page of the Utility Menu.
4.
Select the Properties on components option.
5.
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.
6.
Select a Thickness calculation method.
7.
Select a Component organization method and either select a file or enter a tolerance based on the method.
8.
Click the Contour button to open the node selection panel.
9.
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
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
224
To contour thickness and z-offset values using the Properties on Elements option 1.
Change to your preferred user profile.
2.
Load the desired model file.
3.
Access the Midsurf thickness… utility from the Geom/Mesh page of the Utility Menu.
4.
Select the Properties on elements option.
5.
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.
6.
Select a Thickness calculation method.
7.
Select a Component organization method and either select a file or enter a tolerance based on the method.
8.
Click the Contour button to open the node selection panel.
9.
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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Altair Engineering
Gauge File Format & Example The Gauge file uses the following format:
Number of Gauges [Number of Gauge Data Lines] Gauges Begin
End
Assigned Value
[min Thk]
[max Thk]
[Assigned 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:
Number of Gauges 4
Gauges Begin
End
Assigned Value
0.0
0.05
0.05
0.05
0.1
0.1
0.1
0.15
0.15
0.15
0.2
0.2
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of 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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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: -
229
For tria3 elements, uses attributes:
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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.
-
For tria3 elements, uses z-offset attributes [if requested]: CTRIA3_ZOFFS ZOFFS
-
For quad4 elements, uses z-offset attributes [if requested]: CQUAD4_ZOFFS ZOFFS
Assigns the properties to the corresponding elements.
OptiStruct/RADIOSS (Bulk Data Format) Elements Assigns multiple thicknesses to each element, based on the nodal thickness values for that element: -
For quad4 elements, uses attributes: CQUAD4_T1T2T3T4 CQUAD4_T1 CQUAD4_T2 CQUAD4_T3 CQUAD4_T4
231
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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.
-
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.
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.
-
For tria3 elements, uses z-offset attributes [if requested]: CTRIA3_ZOFFS ZOFFS
-
For quad4 elements, uses z-offset attributes [if requested]: CQUAD4_ZOFFS ZOFFS
Assigns the properties to the corresponding elements.
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of 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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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
235
Double-click components and use the comps collector that displays in the panel area to select comps representing the geometry of the solid to
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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.
Maximum feature angle
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.
Maximum reverse angle
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.
Mesh size
Average element size of the mesh to be created.
Minimum edge size
No single edge of any generated element will be shorter than this.
Minimum elem size
Minimum allowable area for any element.
Sacred surface
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.
Mesh density
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.
Tet from
Choose floating, in which the quick tetramesher is free to move nodes in
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of 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.
Perform mesh cleanup only
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.
Mesh
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
Locate holes in your model.
Find T-Con
Locate T-connections in the model.
Dihedrals
Locate features in the model that have feature angles greater than 150 degrees.
Attached
Locate entities attached to the selected components.
Try TetraMesh
After making adjustments, click this to re-run the meshing operation on the same components.
Help
Opens a pop-up window with basic information about each control that displays on the tab.
Close
Closes the tab.
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.
Load the geometry.
2.
For critical areas where you want to control the mesh such as bolt holes, manually mesh using chordal
237
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Altair Engineering
deviation. Select these elements as sacred elements. This helps to obtain the desired mesh in critical areas. 3.
Launch the Quick Tetramesh macro. Run with the desired mesh size.
4.
Identify problem areas, if any (e.g. any surfaces edges that were ignored, or if mesh in certain areas is not satisfactory).
5.
Use the Delete panel to delete the tetras, then manually mesh problem areas.
6.
Re-launch the Quick Tetramesh macro and select sacred elements to protect.
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of 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 panel’s 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.
Click the elems selector and select retrieve to load the saved failed elements.
3.
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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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 element’s Jacobian at the corner nodes or the integration points.
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of 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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Altair Engineering
After clicking Apply
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of 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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Each node will receive a hole of this radius, measured from the node.
Number of layers
This is the number of layers of washer mesh elements that you want to surround each hole.
Uniform/Varying
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.
No.
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.
Scale/Width
Determines the width of the washer layers.
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
246
Scale: you can specify each layer’s scale relative to the Hole radius. For example, use "0.5" for a washer layer that’s 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.
Trim
Click this button to create the new hole(s).
Reject
If you don’t 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
Close the Mesh Trimming with Circular Holes dialog.
247
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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.
Click the yellow Select Nodes button. The panel area is once again displayed, with a nodes selector active.
2.
Select nodes on the edges of the holes that you wish to fill.
3.
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.
4.
Click the Fill button to fill the selected holes with mesh.
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.
Fill
Click this button to perform the fill operation, whether you choose to select your holes manually or automatically.
Reject
If you don’t 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
Close the Filling holes with mesh dialog.
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
248
249
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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).
right
Split the model along global Y=ymiddle and save the model between Y= ymiddle and Y=ymax.
front
Split the model along global X=value (selected value) and save the model between X=xmin and X=value.
rear
Split the model along global X=value (selected value) and save the model between X=value and X=xmax.
frontleft
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.
frontright
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.
rearleft
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.
rearright
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.
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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.
Open the Box Trim function.
2.
Using the extended entity selection, select the elements you would like to trim and click proceed or the middle mouse button.
251
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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.
5.
You can also specify a Box collector. A large hexa element that represents the box will be created for visualization in the specified collector.
6.
Click Trim. (Reject will undo all the above.)
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of 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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
If left unselected, slivers will not be fixed.
fix wedge tetras
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
This option moves boundary nodes of each element to improve quality, and may result in deviations from the base geometry features.
boundary nodes: permit adding/deleting
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
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
256
Aspect Ratio
The ratio of the longest edge of an element to its shortest edge.
Tet collapse
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.
Vol Skew
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
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.
Warpage
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.
Min Interior Angle
The minimum allowable interior angle for the tria face of a tetra element.
Max Interior Angle
The maximum allowable interior angle for the tria face of a tetra element.
Jacobian
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 element’s integration points (also called Gauss points), and reports the ratio between the smallest and the largest.
Time Limit (minutes)
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).
Edit Criteria
Access the Criteria File Editor to change the element quality requirements.
257
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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.
Fix
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.
Reject
If the results of the fixes are unacceptable, click this to revert the mesh to its pre-fixed state. Note
Close
Altair Engineering
You can only undo one fix operation this way--you cannot "back up" more than one step!
Close the Fix Sliver Tetra Elements tool.
Altair HyperMesh User's Guide Proprietary Inform ation of 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
Description
Solid Face Alignment
Applies to templates: Standard3D, Explicit
Align Faces
Determines the default stack or thickness direction for Abaqus composite solid, gasket and continuum shell elements.
Review
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.
Reset
The Reset button deletes the stack (or thickness) direction arrows.
Dummy
Applies to templates: Explicit
Positioning Process Manager
Tool that guides you through a workflow of positioning a dummy in a seat.
Tools
Applies to templates: Standard2D, Standard3D, Explicit
Step Manager
Activates the Abaqus Step Manager, which allows you to define Abaqus history (*STEP) information in HyperMesh.
Contact Manager
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
259
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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.
Load the Abaqus user profile.
2.
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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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:
263
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.
Interface Type
The interface types. The currently supported types are contact pair, tie, pre-tension section, general contact, and shell to solid coupling.
Slave
The names of the slave surfaces in Abaqus Standard (or the first surface in Abaqus Explicit).
Master
The names of the master surfaces in Abaqus Standard (or the second surface in Abaqus Explicit).
Surface Interaction
The names of the surface interaction properties.
Slave display
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.
Master display
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.
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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.
New ...
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.
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
264
Edit ...
Opens the corresponding dialog for editing the selected interface, surface, or surface interaction.
Review
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.
265
Delete
Deletes the selected interfaces, surfaces, or surface interactions. You can delete single or multiple selections from the table.
Rename
Rename the selected interface, surface, or surface interaction.
Sync
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.
Close
Closes the Contact Manager.
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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.
Apply
Updates the HyperMesh database with the changes without closing the Contact Pair dialog.
Cancel
Closes the Contact Pair dialog without updates.
See also Pre-Tension Section Tie Auto Contact Element Based Surface Node Based Surface
267
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Altair Engineering
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 HyperMesh User's Guide Proprietary Inform ation of 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
269
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.
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Altair Engineering
For Explicit template
Altair Engineering
Mechanical constraint, CPSET, OP, Weight, and Small sliding. See the Abaqus Online Documentation for a detailed description of these parameters.
Altair HyperMesh User's Guide Proprietary Inform ation of 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
Updates the HyperMesh database with the changes and closes the Tie dialog.
Apply
Updates the HyperMesh database with the changes without closing the Tie dialog.
Cancel
Closes the Tie dialog without updates.
See also Contact Pair Pre-Tension Section Auto Contact Element Based Surface Node Based Surface
271
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Altair Engineering
Standard2D/Standard3D:
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of 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.
275
Review Set button
The Review Set button reviews the selected node set by highlighting it in the HyperMesh window.
Create/Edit Set button
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.
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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.
Apply
Updates the HyperMesh database with the changes without closing the Pretension Section dialog.
Cancel
Closes the Pre-tension Section dialog without updates.
See also Contact Pair Tie
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of 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
277
Pick Node allows you to pick a node graphically, or you can enter a node number in the text box.
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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:
279
The NSET parameter is currently only supported on the card image.
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Updates the database with the changes and closes the dialog.
Apply
Updates the database with the changes without closing the dialog.
Cancel
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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 <
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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Altair Engineering
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 HyperMesh User's Guide Proprietary Inform ation of 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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Searches the model for interacting components.
Cancel
Closes the Contact Pair dialog without updates.
Remove Selection icon
Removes selected components from the table. You can use the CTRL and Shift key to select multiple items in the table.
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of 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.
Load the Abaqus user profile and select either the 2D or 3D template.
2.
Click Contact Manager in the Abaqus Utility Menu.
3.
Click Auto. This opens the Auto Contact dialog.
4.
Select the type of interface to create in the Type of Interface: field.
5.
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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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.
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.
9.
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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):
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
Type of contact pair created.
Color
Color assigned to the interaction and surfaces
Surface Interaction
Opens the Auto Contact online help.
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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Altair Engineering
Highlight 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 Elements icon
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
Automatically zooms in to the elements stored in the currently selected items.
Display All Elements icon
In combination with the Highlight Elements or the Review Elements option, current contents remain unchanged on the screen.
Display Components with Elements icon
Highlights or reviews the elements referred by an interaction or surfaces and shows the components they belong to. All other components will be masked.
Display Only Elements icon
Only elements are highlighted or reviewed. The rest of the component and other components will be masked.
Select Elements Manually icon
Opens the element selection panel so that individual elements can be added/removed manually. Click proceed when finished.
Add by Adjacent icon
Adds the elements adjacent to the surface to the selected surface.
Add by Face icon
Adds the adjacent face to the selected surface.
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.
Right-click to undo one time.
Right-click to undo one time.
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 Auto Contact To Set Up an Auto Contact Run Modifying Auto Contact Entities
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of 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
Rename an existing entry.
Delete
Delete items from the browser.
Swap Master Slave
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.)
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.
Add by Adjacent
Adds adjacent elements to the selected surface.
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
Reverses the current selections in the Accept column.
Expand All/ Collapse
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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
The name of surfaces in the HyperMesh database.
Type
The types of surfaces. Currently supported types are ELEMENT, NODE, and ANALYTICAL RIGID (SEGMENTS, CYLINDER or REVOLUTION).
Display
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.
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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:
291
Auto
Launches the Auto Contact dialog that allows you to quickly and easily create interactions between several parts of your model.
New ...
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.
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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.
Review
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.
Delete
Deletes selected surfaces. You can delete single or multiple selections from the Surface table.
Rename
Rename the selected surface.
Sync
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.
Close
Closes the Contact Manager.
Display All
Displays all surfaces in the graphic area.
Display None
Hides all surfaces in the graphic area.
Display Reverse
Displays all unchecked surfaces and hides all checked surfaces in the graphic area.
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of 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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Changes the color of the current surface in the display.
Review
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.
Close
Updates the HyperMesh database with the optional parameters specified and closes the Element Based Surface window.
See also Contact Pair Pre-Tension Section Tie General Contact
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of 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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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:
Reject
Altair Engineering
The Delete Face tab contains tools to find and delete duplicate faces in the current surface.
Rejects the recently added faces.
Altair HyperMesh User's Guide Proprietary Inform ation of 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:
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:
Reject
Several three-node or two-corner-node sets can be selected at the same time to define faces in different solids.
The Delete Face tab contains tools to find and delete duplicate faces in the current surface.
Rejects the recently added faces.
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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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.
Add
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:
Reject
The Delete Face tab contains tools to find and delete duplicate faces in the current surface.
Rejects the recently added faces.
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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
Nodes
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:
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:
299
Several three-node or two-corner-node sets can be selected at the same time to define faces in different elements.
You cannot add duplicate contactsurfaces for the same element in HyperMesh. Therefore, the Add button does not check for duplicates
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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.
Nodes
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.
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
300
Note:
Add
Several two-node sets can be selected at the same time to define edges in different elements.
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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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.
Nodes
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:
Add
Several node pairs can be selected at the same time to define edges in different element.
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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.
Add
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.
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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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.
Update
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.
After selecting an element set, click the arrow keys to move the set into table on the right. Once an elset
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of 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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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.
Reverse
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.
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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.
Delete
Deletes the selected faces or contactsurfaces from the selected 2-D solid, axisymmetric, gasket, beam, pipe, truss elements.
(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.
Delete
Deletes the highlighted duplicate faces found. Note:
307
Duplicate contactsurfaces cannot be added to the same
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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.
Close
Updates the HyperMesh database with the optional parameters specified and closes the Node Based Surface window.
See also Contact Pair Pre-Tension Section Tie General Contact Auto Contact
309
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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.
Add
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.
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:
311
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.
Create/Edit Set...
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
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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:
Update
In HyperMesh, the cross-sectional area data item is supported only for surfaces defined by node sets.
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
Altair Engineering
Opens the element selector panel for you to select SurfaceNodes elements from the graphic area. The corresponding Reset button resets the selected elements.
Altair HyperMesh User's Guide Proprietary Inform ation of 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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Changes the color of the current surface in the display.
Review
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.
Close
Updates the HyperMesh database with the optional parameters that you
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of 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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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:
Altair Engineering
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.
Create/Edit System...
Click to create new coordinate systems using the Systems panel.
Altair HyperMesh User's Guide Proprietary Inform ation of 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.
Pick Lines…
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:
319
In HyperMesh, the sequence of node1 and node2 for lines can be visualized from the Line Edit/Extend Line panel.
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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:
Altair Engineering
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 HyperMesh User's Guide Proprietary Inform ation of 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.
Create/Edit System...
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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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.
Pick Lines…
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:
Sweep Distance
In HyperMesh, the sequence of node1 and node2 for lines can be visualized from the Line Edit/Extend Line panel.
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.
Click the Update button to update the HyperMesh database with your settings.
See also SEGMENTS Option REVOLUTION Option Analytical Rigid Surface Abaqus Contact Manager
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of 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.
Pick System...
323
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.
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Altair Engineering
Create/Edit System...
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:
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 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.
Pick Lines…
Click to pick a line from the HyperMesh model. When you click proceed, the coordinate values in terms of the defined
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
324
plane and line types for the selected lines will appear in the table. Note:
Revolution angle:
The sequence of node1 and node2 for lines can be visualized from the Line Edit /Extend Line panel.
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.
Click the Update button to update the HyperMesh database with your settings.
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.
Reverse normals:
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.
325
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Altair Engineering
See also Analytical Rigid Surface Abaqus Contact Manager
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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.
Reference Node:
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.)
Line mesh density:
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).
327
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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.
Max ratio
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.
Scale thickness
Select to scale all of the surface facets by a single factor. Then type the scaling factor in the adjacent field.
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of 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.
No offset
Select for the surface to ignore midplane offsets.
No thickness
Select for the surface to ignore thicknesses. Do not select this option if the surface will be double-sided or a self-contact surface.
Fillet radius
Select to define a radius of curvature to smooth discontinuities between segments. Then type a length in the adjacent field.
See also Analytical Rigid Surface Abaqus Contact Manager
329
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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.
New...
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.
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
330
Edit ...
Opens the Surface Interaction dialog for editing the selected surface interaction.
Review
Not active on this tab.
Delete
Deletes single or multiple surface interactions from the Surface Interaction table.
Rename
Rename the selected surface interaction.
Sync
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.
Close
Closes the Contact Manager.
See also Surface Interaction Abaqus Contact Manager
331
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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.
Apply
Updates the HyperMesh database with the changes without closing the Surface Interaction window.
Cancel
Closes the Surface Interaction window without any update.
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of 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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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).
Linear
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.
Tabular
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
335
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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:
337
The friction type User is not supported in the Contact Manager. However, it is supported in HyperMesh in the *SURFACE INTERACTION card image.
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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, you’ll 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.
In the Abaqus Explicit template, open the Utility Menu and click the button PositioningProcess.
2.
Click Create/Open to start a new ProcessManager instance.
3.
In the panel area, select the Interactive positioning radio button and select Apply.
4.
Click the file browser icon to browse for the dummy input file (*.inp) to open.
5.
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.
Note:
6.
341
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.
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).
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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.
8.
Once the dummy is positioned in the H-point, click on the Incremental subpanel. Make your changes and click return.
9.
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.
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. You’ll 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
Altair HyperMesh User's Guide Proprietary Inform ation of 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.
Review
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.
Reset
The Reset button deletes the stack (or thickness) direction arrows.
See also Abaqus Utility Menu
343
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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:
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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.
Review
Highlights the selected entity in the model.
Sort
Lists the entities in alphabetical order. Click again to reverse the order.
OK
Selects an entity for the field on the dialog.
Cancel
Closes the Entity Browser without making a selection.
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of 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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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.
Name
The name of the load step.
Analysis Type
The analysis type of the load step.
Load Collector The list of load collectors in the load step. Output Block
The list of output blocks in the load step.
Interface Controls
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.
Display
Turns the load step display on/off.
The Step tab contains the following buttons:
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of 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...
Opens the load step editing dialog for the selected load step.
Review
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.
Text
Reviews the selected load step in a text window.
Rename
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.
Delete
Deletes the selected load steps.
Sync
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.
Close
Closes the Step Manager. Moves the selected load steps up one row.
Moves the selected load steps down one row.
See also
351
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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.
middle section
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.
right-most 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.
The Load Step dialog contains the following general buttons: Review
353
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
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Altair Engineering
elements are highlighted. Right-click on the Review button to clear the highlighted selections. Text...
Reviews the current load step in a text window
Synchronize
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.
Close
Closes the Load Step window and opens the Step Manager window.
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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.
Name
The name of the load collector. The load collector names are for internal use only. The Abaqus input file does not need them.
Display
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.
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...
Altair Engineering
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 HyperMesh User's Guide Proprietary Inform ation of 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.
Organize...
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.
Label...
Opens the corresponding panel where you can turn on/off load labels or update the label size.
Delete
Opens the Delete panel where you can delete load collectors. When you are finished, click return to update the Load collector table.
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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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.
See also Abaqus Step Manager: Load Step Dialog Abaqus Step Manager Overview
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:
Altair Engineering
Parameter:
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
358
*FREQUENCY
PROPERTY EVALUATION, EIGENSOLVER = {SUBSPACE, LANCZOS, AMS}, NORMALIZATION = {MASS, DISPLACEMENT}, RESIDUAL MODES, ACOUSTIC COUPLING, NUMBER INTERVAL, BIAS, USER BOUNDARIES
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
*STEADY STATE DYNAMICS
DIRECT, SUBSPACE PROJECTION = {ALL FREQUENCIES, CONSTANT, EIGENFREQUENCY, PROPERTY CHANGE}, FREQUENCY SCALE, INTERVAL, REAL ONLY, DAMPING CHANGE, STIFFNESS CHANGE
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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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.
See also Abaqus Step Manager: Load Step Dialog Abaqus Step Manager Overview
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Altair Engineering
Nset
The name of the node sets. Node sets can only be added or deleted from this column using the
1st dof
or
buttons, respectively.
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
The last degree of freedom.
Magnitude
The magnitude.
Load Id
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.
Create/Edit Set
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.
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.
Display/Review from panel
Opens the appropriate HyperMesh panel. Use the Review button to expand the loads and constraints on the sets for visualization purposes.
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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.
All 'Boundary' in current collector
The Delete button deletes only *BOUNDARY loads from the current 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.
See also Load Step: Boundary
The Parameter tab allows you to define optional parameters for the *BOUNDARY card. The supported parameters are:
365
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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 CLOAD–Force 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
Altair HyperMesh User's Guide Proprietary Inform ation of 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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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
or
, respectively. Comp_x
369
The component in x direction. The x-direction indicates dof 1 for force and dof 4 for moment.
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Altair Engineering
Comp_y
The component in y direction. The y-direction indicates dof 2 for force and dof 5 for moment.
Comp_z
The component in z direction. The x-direction indicates dof 3 for force and dof 6 for moment.
Magnitude
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.
Load Id
The ID of the load collector.
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.
Create/Edit Set..
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.
Display/Review from panel
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.
Create/Edit vector..
Opens the vectors panel in HyperMesh. When you finish creating/editing the vector, click return.
Review
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.
Update
Updates the HyperMesh database with the data lines defined in the table. By default, HyperMesh does not display loads defined with sets.
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of 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.
All 'CLOAD' in current collector
The Delete button deletes only *CLOAD loads from the current 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.
See also Load Step: CLOAD
371
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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.
See also Load Step: CLOAD
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
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
372
See also Load Collector Abaqus Step Manager: Load Step Dialog Abaqus Step Manager Overview
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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Altair Engineering
Nodeset
The name of the node sets. Node sets are added or removed using respectively.
Area
The area associated with the nodes.
Sink temp
Reference sink temperature.
Film coef
Reference film coefficient.
or
,
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.
Create/Edit Set..
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.
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: 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.
All 'CFILM' in current collector
The Delete button deletes only *CFILM loads from the current
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of 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.
See also Load Step: CFILM
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.
See also Load Step: CFILM
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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
See also Load Collector Abaqus Step Manager: Load Step Dialog Abaqus Step Manager Overview
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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
or
, respectively.
Label
The labels of pressure load. The available labels are: P1, P2, P3, P4, P5, P6, and P.
Magnitude
The magnitude of the load.
Load Id
The ID of the load collector.
For Centrifugal type: Elset
The name of the element sets. Element sets are added and deleted in this column using
or
, respectively.
Label
The labels of centrifugal loads and Coriolis forces. The available labels are: CENTRIF, CENT, and CORIO.
Magnitude
The magnitude of the load.
Coord1
Coordinate 1 of a point on the axis of rotation.
Coord2
Coordinate 2 of a point on the axis of rotation.
Coord3
Coordinate 3 of a point on the axis of rotation.
DirCos1
1-component of the direction cosine of the axis of rotation.
DirCos2
2-component of the direction cosine of the axis of rotation.
DirCos3
3-component of the direction cosine of the axis of rotation.
Load Id
The ID of the load collector.
For Rotary acceleration type:
379
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Altair Engineering
Elset
The name of the element sets. Element sets are added and deleted in this column using
or
, respectively.
Label
The labels of the DLOAD type. The available labels are: ROTA.
Magnitude
The magnitude of the load.
Coord1
Coordinate 1 of a point on the axis of rotary acceleration.
Coord2
Coordinate 2 of a point on the axis of rotary acceleration.
Coord3
Coordinate 3 of a point on the axis of rotary acceleration.
DirCos1
1-component of the direction cosine of the axis of rotary acceleration.
DirCos2
2-component of the direction cosine of the axis of rotary acceleration.
DirCos3
3-component of the direction cosine of the axis of rotary acceleration.
Load Id
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
or
, respectively.
Label
The labels of the DLOAD type. The available labels are: GRAV.
Magnitude
The magnitude of the load.
Comp1
1-component of the gravity vector.
Comp2
2-component of the gravity vector.
Comp3
3-component of the gravity vector.
Load Id
The ID of the load collector.
For pressure in pipe/elbow type:
Elset
The name of the element sets. Element sets are added and deleted in this column using
Altair Engineering
or
, respectively.
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
380
Label
The labels of the pressure in pipe/elbow elements. The available labels are: PE, PI, PENU, and PINU.
Magnitude
The magnitude of the load.
Diameter
The effective inner or outer diameter.
Condition
The end loading condition: CLOSE (default) or OPEN.
Load Id
The ID of the load collector.
For hydro pressure type: The name of the element sets. Element sets are added and deleted in this Elset column using
or
, respectively.
Label
The labels of the hydrostatic pressure. The available labels are: HP.
Magnitude
The magnitude of the load.
Zero press
Z-coordinate of zero pressure level in three-dimensional or axisymmetric cases; Y-coordinate of zero pressure level in two-dimensional cases.
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.
Load Id
The ID of the load collector.
For hydro pressure in pipe/elbow type:
Elset
The name of the element sets. Element sets are added and deleted in this column using
381
or
, respectively.
Label
The labels of the hydrostatic pressure in pipe.elbow elements. The available labels are: HPE, and HPI.
Magnitude
The magnitude of the load.
Zero press
Z-coordinate of zero pressure level in three-dimensional or axisymmetric cases; Y-coordinate of zero pressure level in two-dimensional cases.
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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.
Diameter
The effective inner or outer diameter.
Condition
The end loading condition: CLOSE (default) or OPEN.
Load Id
The ID of the load collector.
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.
Create/Edit Set
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.
Display/Review from panel
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 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
Altair Engineering
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 HyperMesh User's Guide Proprietary Inform ation of 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.
For tips on entering information and navigating in the Define tab, see Step Manager Tab Environment.
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.
All 'Distributed loads' in current collector
The Delete button deletes all distributed (*DLOAD, *FILM) loads from the current 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.
383
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Altair Engineering
See also Load Step: DLOAD
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
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
384
See also Load Step: DLOAD
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
See also Load Collector Abaqus Step Manager: Load Step Dialog Abaqus Step Manager Overview
There are two options for defining film coefficient on FILM created on individual elements or geometry: By selection
385
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.
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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.
See also Load Step: FILM
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of 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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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.
See also Load Step: FILM
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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
or
, respectively.
Label
The labels of FILM load. The available labels are: F1, F2, F3, F4, F5, F6, FPOS, and FNEG.
Sink Temp
The reference sink temperature.
Film coeff
The reference film coefficient.
Load Id
The ID of the load collector.
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.
Create/Edit Set
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.
Display/Review from Panel
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
389
Creates special review FILM loads in HyperMesh graphics for the selected set. Right-click Review to clear the special review loads and highlighting.
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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.
For tips on entering information and navigating in the Define tab, see Step Manager Tab Environment.
See also Load Step: FILM
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.
All 'Distributed loads' in current collector
The Delete button deletes all distributed (*DLOAD, *FILM) loads from the current 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.
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
390
See also Load Step: FILM
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.
See also Load Step: FILM
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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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
or
, respectively.
Label
The labels of pressure load. The available labels are P, PNU, and VP.
Magnitude
The magnitude of the load.
hydro pressure type:
Surface
The name of the Abaqus surface. Surfaces are added and deleted in this column using
393
or
, respectively.
Label
The labels of the hydrostatic pressure. The available label is HP.
Magnitude
The magnitude of the load.
Zero press
Z-coordinate of zero pressure level in three-dimensional or axisymmetric cases; Y-coordinate of zero pressure level in two-dimensional cases.
Press point
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.
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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.
Create/Edit Surface..
Opens a message with information about surface definition in HyperMesh.
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.
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.
For tips on entering information and navigating in the Define tab, see Step Manager Tab Environment.
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
The Delete button deletes all the loads from the current load collector.
All 'DSLOAD' in current collector
The Delete button deletes only *DSLOAD loads from the current 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.
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
394
See also Load Step: DSLOAD
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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Altair Engineering
See also Load Step: DSLOAD
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.
See also Load Collector Abaqus Step Manager: Load Step Dialog Abaqus Step Manager Overview
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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
, respectively.
Label
The SFILM labels. The available labels are F and FNU.
Sink temp
Reference sink temperature.
Film coef
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.
Create/Edit Surface..
Opens a message with information about surface definition in HyperMesh
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.
397
Review
Reviews the selected surface in the data line table. Right-click on the Review button to clear the highlighted selections.
Update
Updates the HyperMesh database with the data lines defined in the table. By
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Altair Engineering
default, HyperMesh does not create a display for loads defined with sets.
For tips on entering information and navigating in the Define tab, see Step Manager Tab Environment.
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
The Delete button deletes all the loads from the current load collector.
All 'SFILM' in current collector
The Delete button deletes only *SFILM loads from the current 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.
See also Load Step: SFILM
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.
See also Load Step: SFILM
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of 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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Altair Engineering
Nset
The name of the node sets. Node sets are added and deleted in this column using
or
, respectively.
Temperature
Reference temperature value.
Gradient1
Temperature gradient in the n2-direction for beams or temperature gradient through the thickness for shells.
Gradient2
Temperature gradient in the n1-direction for beams.
Load Id
The ID of the load collector.
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.
Create/Edit Set
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.
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.
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.
For tips on entering information and navigating in the Define tab, see Step Manager Tab Environment.
See also Load Step: Temperature Define Tab
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of 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
The Delete button deletes all the loads from the current load collector.
All 'Temperature' in current collector
The Delete button deletes only *TEMPERATURE loads from the current 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.
See also Load Step: Temperature
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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Altair Engineering
See also Load Step: Temperature
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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
Integer list of degrees of freedom identifying the free directions
Reference points
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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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.
Name
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.
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:
407
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.
Edit
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
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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.
See also Abaqus Step Manager: Load Step Dialog Abaqus Step Manager Overview
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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.
Review
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.
Delete
Opens the HyperMesh delete panel to delete output blocks. When you are finished, click return and the Output block table will be updated.
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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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.
See also Output request Abaqus Step Manager Overview
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:
411
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.
Review
Reviews the selected node sets by highlighting them in the HyperMesh graphics. Right-click on the Review button to clear the review selections.
Update
Updates the HyperMesh database with the data lines defined in the table and the parameters.
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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.
Review
Reviews the selected element sets by highlighting them in the HyperMesh graphics. Right-click on the Review button to clear the review selections.
Update
Updates the HyperMesh database with the data lines defined in the table and the parameters.
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
412
See also Output request Abaqus Step Manager Overview
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.
Review
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.
Update
Updates the HyperMesh database with the data lines defined in the table and the parameters.
See also
413
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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.
Review
Reviews the selected element sets by highlighting them in the HyperMesh graphics. Right-click on the Review button to clear the review selections.
Update
Updates the HyperMesh database with the data lines defined in the table and the parameters.
See also Output Request Abaqus Step Manager Overview
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of 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
See also Output Request Abaqus Step Manager Overview
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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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.
Review
Reviews the selected node sets by highlighting them in the HyperMesh graphics. Right-click on the Review button to clear the review selections.
Update
Updates the HyperMesh database with the data lines defined in the table and the parameters.
See also Output Request Abaqus Step Manager Overview
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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.
Review
Reviews the selected element sets by highlighting them in the HyperMesh graphics. Right-click on the Review button to clear the review selections.
Update
Updates the HyperMesh database with the data lines defined in the table and the parameters.
See also Output Request Abaqus Step Manager Overview
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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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.
Review
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.
Update
Updates the HyperMesh database with the data lines defined in the table and the parameters.
See also Output Request Abaqus Step Manager Overview
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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.
Review
Reviews the selected element sets by highlighting them in the HyperMesh graphics. Right-click on the Review button to clear the review selections.
Update
Updates the HyperMesh database with the data lines defined in the table and the parameters.
See also Output Request Abaqus Step Manager Overview
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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Altair Engineering
Contact Print Energy Print
See also Output Request Abaqus Step Manager Overview
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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.
Review
Reviews the selected node sets by highlighting them in the HyperMesh graphics. Right-click on the Review button to clear the review selections.
Update
Updates the HyperMesh database with the data lines defined in the table and the parameters.
See also Output Request Abaqus Step Manager Overview
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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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.
Review
Reviews the selected element sets by highlighting them in the HyperMesh graphics. Right-click on the Review button to clear the review selections.
Update
Updates the HyperMesh database with the data lines defined in the table and the parameters.
See also Output Request Abaqus Step Manager Overview
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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.
Review
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.
Update
Updates the HyperMesh database with the data lines defined in the table and the parameters.
See also Output Request Abaqus Step Manager Overview
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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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.
Review
Reviews the selected element sets by highlighting them in the HyperMesh graphics. Right-click on the Review button to clear the review selections.
Update
Updates the HyperMesh database with the data lines defined in the table and the parameters.
See also Output Request Abaqus Step Manager Overview
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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.
Update
Updates the HyperMesh database with the data lines defined in the table and the parameters.
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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Altair Engineering
See also Abaqus Step Manager Step Tab Abaqus Step Manager: Load Step Dialog Abaqus Step Manager Overview
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
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
426
See also Abaqus Step Manager Step Tab Abaqus Step Manager: Load Step Dialog Abaqus Step Manager Overview
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.
See also Abaqus Step Manager Step Tab Abaqus Step Manager: Load Step Dialog Abaqus Step Manager Overview
The Restart write option in the tree allows you to define the *RESTART, WRITE card.
427
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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.
See also Abaqus Step Manager Step Tab Abaqus Step Manager: Load Step Dialog Abaqus Step Manager Overview
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.
See also Abaqus Step Manager Step Tab Abaqus Step Manager: Load Step Dialog Abaqus Step Manager Overview
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
428
429
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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.
Edit...
Opens the Load Step Editing dialog for the selected load step.
Review
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.
Text
Reviews the selected load step in a text window.
Rename
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.
Delete
Deletes the selected load steps.
Sync
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.
Close
Closes the Step Manager.
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of 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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Displays components and attributes in an interactive table.
Material
Creates and defines material cards.
Section
Creates and defines section cards.
Real Sets
Creates property card images for elements defined with the ET Type macro.
ET Type
Creates HyperMesh card images for ANSYS element types.
Contact Manager
Creates new contact pairs and manages existing contact pairs.
Convert to Spl. 2nd Order
Converts a first-order meshed part to a special second-order meshed part.
Update Pre-8.0 HM Model
Updates older model files.
Ansys to OptiStruct Convert
Converts ANSYS decks to OptiStruct
Ansys to Nastran Convert
Converts ANSYS deck to Nastran
Modal Analysis Tool
Set the modal analysis
See also ANSYS Interface Overview
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of 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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
434
To Create a Component Collector
To use the Component Manager to create a component collector: 1.
In the ANSYS Utility Menu, click Component Manager. The Components dialog appears, listing all components.
2.
From the Action menu, select Create New.... The Create Component dialog appears.
3.
Type a name for the component in the Component name field.
4.
In the Element reference number field, select the number of the element type you wish to associate in the component.
5.
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.
6.
In the Material reference number field, select a material property card from the pull-down menu.
7.
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.
8.
Click the color block in the Color field to choose a color to assign to the component.
9.
Click Apply to create the component. Click Close to close the Create Component dialog.
To use HyperMesh panels to create a component collector: 1.
Click the button to open the collectors panel, or click Collectors, then click Create and Component.
2.
Type a name for the component in the comp name = box.
3.
Choose a color for the component collector.
4.
Click card image = to select the only available card image, HM_COMP.
5.
Click property = to select an existing property.
6.
Click the material = button to select an existing material.
7.
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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Altair Engineering
8.
Click return to exit the component card image.
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of 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.
Type a name for the component in the Component name field.
3.
Select an element type in the Element reference number field.
4.
Select a real set in the Real set number field.
5.
Select a material in the Material reference number field.
6.
Select a section in the Section reference number field.
7.
Click the button in the Color field to select a color for the component that will be used in HyperMesh.
8.
Click Create. Click Close to go back to the Component Manager.
437
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Altair Engineering
To Edit a Component Card 1.
Click anywhere in the component’s row in the Component Manager table to select it.
2.
If not already in Edit mode, click Table and Editable.
3.
In the Assign Values drop-down, select a field to modify.
4.
In the adjacent field, type or select the new value.
5.
Click the Set button. The new value appears in the table.
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of 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
Provides information about the macro.
New…
Opens the Create Material dialog, from which you can specify parameters for a new material and create it.
Edit…
Opens the Edit Material dialog, from which you can review and change parameters for an existing material that is selected in the table.
Refresh
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.
Delete
Deletes the material that is selected in the table.
Close
Closes the Material macro dialog.
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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Altair Engineering
See also ANSYS Utility Menu ANSYS Interface Overview
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of 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 material’s properties.
441
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.
Material Name
Type a name to identify the material.
Material Type
Select MP or MPDATA depending on the material card you want to use.
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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 material’s 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.
Material Name
This field is initially populated with the current name of the material. You can modify the name of the material.
Material Type
You can change the card image type.
If you make changes to a material, you must click Update to reflect the changes in the card image.
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of 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
Provides information about the macro.
New…
Opens the Create Section Dialog, from which you can specify parameters for a new section and create it.
Edit…
Opens the Edit Section Dialog, from which you can review and change parameters for an existing material that is selected in the table.
Refresh
Refreshes the HyperMesh database with changes you made through the Material macro.
Delete
Deletes the section card(s) that is selected in the table.
Close
Closes the Section macro dialog.
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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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.
Section Name
Type a name for the section.
Section Type
Select the type of section to create: Beam, Taper, Shell or Pretension .
Sub Type
(This selection only applies to beam sections.) Choose a subtype from the drop-down list.
Define by HyperBeam
(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.
When you are in the HyperBeam application, it is possible to create
445
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Altair Engineering
multiple HyperBeam sections. However, only the most recently created section is attached the section card.
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of 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 section’s 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.
Section name:
This field is initially populated with the current name of the section. You can modify the name of the section.
Section type:
You can change the type of section to create.
Sub type:
(This selection only applies to beam sections.) You can select another subtype from the drop-down list.
Define by HyperBeam
(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.
447
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Altair Engineering
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of 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.
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.
4.
Type the name for the section card in the Section name field.
5.
Select the type of section you want to create: Beam or Shell.
6.
If you chose Beam in step 5, then select a Sub type from the pull down menu. Shell sections do not have subtypes.
7.
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.
8.
To use a HyperBeam section, select Define by HyperBeam.
9.
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
449
HREC Beam
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Altair Engineering
T Beam
L Beam
Z Beam
CHAN Beam
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
450
451
CTUBE Beam
CSOLID Beam
QUAD Beam
RECT Beam
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Altair Engineering
HATS Beam
11. In the Section dialog, click Close to return to HyperMesh.
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of 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
Provides information about the macro.
New…
Opens the Create Real Sets dialog, from which you can specify parameters for a new real set and create it.
Edit…
Opens the Edit Real dialog, from which you can review and change parameters for an existing real set that is selected in the table.
Export...
Allows you to export the table in .csv format
Refresh
Refreshes the HyperMesh database with changes you made through the Real Sets macro.
Delete
Deletes the real set(s) that is selected in the table.
Close
Closes the Real Sets macro dialog.
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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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.
See also ANSYS Utility Menu ANSYS Interface Overview
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of 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.
455
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.
Element Type
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.
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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.
Element Type
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.
If you make changes to a real set, you must click Update to reflect the changes in the card image.
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of 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
Provides information about the macro.
New…
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.
Edit…
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.
Export...
Allows you to export the table in .csv format
Refresh
Refreshes the HyperMesh database with changes you made through the HyperMesh panels.
Delete
Deletes the element type(s) that is selected in the table.
Close
Closes the ET Type macro dialog.
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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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.
See also ANSYS Utility Menu ANSYS Interface Overview
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of 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.
459
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.
Element Type
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.
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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.
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.
If you make changes to an ET Type, you must click Update to reflect the changes in the card image.
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of 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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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.
Mesh the part for first-order with hexa or penta elements. Place these elements in a collector with the correct element type (SOLID45).
2.
Mesh the mating volume with second-order tetra elements. Place this mesh in a separate component with the correct element type (SOLID95 or SOLID92).
3.
Ensure that the two mesh patterns have a common layer with shared edges between.
4.
From the ANSYS Tools page of the Utility Menu, click the Convert to Special 2nd Order macro.
5.
Select the first-order component from the drop-down menu that shares a common face with the secondorder meshed component.
6.
Select the second-order meshed component in the next drop-down menu and click apply. The special order elements are generated.
7.
Export the file. Read it in the solver and check the elements.
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
462
The following images show examples of proper meshing for the above procedure.
463
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
464
3.
Under Creation method: select either Flexible or Pilot node.
4.
In the Contact type: field, select 2D or 3D.
5.
In the Create from: section, select whether to create a surface to surface contact pair or a point to surface contact pair.
6.
Under Symmetric Contact, select Yes or No.
7.
To select the target body components, click the Pick Target… button. The component selector panel opens.
8.
Click the yellow comps button and select the components that belong to the target component elements.
9.
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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Altair Engineering
See also Auto Contact - ANSYS Interface To Set Up an Auto Contact Run Auto Contact Browser Modifying Auto Contact Entities
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of 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 Manager’s 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:
469
Find
Searches the model for interacting components
Cancel
Closes the Contact Pair dialog without updates
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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.
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 ANSYS Contact Manager To Set Up an Auto Contact Run Auto Contact Browser Modifying Auto Contact Entities
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
470
To Set Up an Auto Contact Run 1.
Load the Ansys user profile.
2.
Click Contact Manager in the ANSYS Utility Menu.
3.
Click Auto. This opens the Auto Contact dialog.
4.
In the Contact Type: field, select the type of contact pair to create.
5.
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.
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.
7.
Click Find. The status bar activates and the Auto Contact Browser opens.
8.
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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Altair Engineering
Auto Contact Browser Modifying Auto Contact Entities
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of 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
Color assigned to the interaction and surfaces
ET Type
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.
473
Highlight 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
Review of elements stored in the selected entities. Elements are highlighted
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Automatically zooms in to the elements stored in the currently selected items.
Display All Elements icon
In combination with the Highlight Elements or the Review Elements option, current contents remain unchanged on the screen.
Display Components with Elements icon
Highlights or reviews the elements referred by an interaction or surfaces and shows the components they belong to. All other components will be masked.
Display Only Elements icon
Only elements are highlighted or reviewed. The rest of the component and other components will be masked.
Select Elements Manually icon
Opens the Element selection panel so that individual elements can be added/ removed manually. Click proceed when finished.
Add by Adjacent icon
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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
Rename an existing entry.
Delete
Delete items from the browser.
Swap Master - Slave
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.
Add by Adjacent
Adds adjacent elements to the selected surface.
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
Reverses the current selections in the Accept column.
Expand All/ Collapse
Expands or collapses folders in the Auto Contact Browser.
See also ANSYS Contact Manger Auto Contact - ANSYS Interface To Set Up an Auto Contact Run Auto Contact Browser
475
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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
Checks the LS-DYNA data deck for errors.
Part Info
Displays statistics of a selected part.
Name Mapping
Converts differing part names to either the HyperMesh name or the LSDYNA name.
Clone Part
Creates a new part from the properties of an existing part.
Create Part
Creates a new component quickly.
Part Replacement
This macro allows you to replace the elements in an existing component (*PART) with new elements.
Convert To Rigid
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
477
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.
Find Fix Free
Finds the welds, rigids, and rigidlinks that are free as described above (
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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.
Component Table
Displays a tabular list of all the components that exist in the model along with their properties and materials.
Material Table
Allows you to easily create and edit materials.
C-Interfto50
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.
See also HyperMesh Tab Area
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of 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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
480
481
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Altair Engineering
Part Info The Part Info macro summarizes a part’s statistics in a dialog. 1.
To start the macro, click Part Info on the Utility Menu.
2.
Click component on the main menu area to select a component or click a component in the graphics area to select it.
3.
Click proceed. The Part Information dialog appears, which lists the part ID, name, thickness, and material type.
4.
To view additional statistics about the part, click the More Details tab.
5.
To display statistics for a different part, select the part in the graphics area or the components selector and click proceed again.
Tip
Click the middle mouse button instead of the proceed button to quickly select components.
See also LS-DYNA Utility Menu
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of 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.
See also LS-DYNA Utility Menu
483
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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.
See also LS-DYNA Utility Menu
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of 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.
See also LS-DYNA Utility Menu
485
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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.
See also LS-DYNA Utility Menu
491
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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.
Click Tools in the Utility Menu.
2.
Click Convert To Rigid.
3.
Select the elements to convert to rigid and click proceed.
4.
Select an existing rigid component in the model for merging the newly created rigid body and Click Proceed.
5.
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.
2.
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.
3.
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.
4.
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.
5.
A check is performed to detect joints located partially or entirely within the window. Detected joints are deleted.
6.
A check is performed to detect springs located partially or entirely within the window. Detected springs are deleted.
7.
A check is performed to detect seatbelt elements (seatbelt elements, Retractor, Pretensioner) located partially or entirely within the window. Detected seatbelt elements are deleted.
8.
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).
9.
A message is displayed when the conversion is complete.
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
492
Convert To Rigid Flow Chart
493
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Regenerates the table with all the parts in the model
Editable
Sets the table mode to editable mode, allowing you to change values for the
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
494
selected components Filter
Enables the filtering GUI
Configure
Allows you to specify the number and type of columns listed in the table
Save
Saves the information listed in the table in CSV or HTML format
Quit
Quit the table function.
Selection All
Selects all rows or parts
None
Selects none or deselects parts/rows that were previously selected
Reverse
Reverses the selection
Displayed
Selects the rows or the displayed parts
User
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.
495
All
Displays all the components in the model
None
Turns off every component displayed
Reverse
Reverses the display of the part
Show selection
Displays the components of the selected rows
Show only Selection
Displays only the components of the selected rows
Hide selection
Hides the components of the selected rows from the display
By Material
Displays components sorted by material
By Properties
Displays components sorted by properties
By Thickness
Displays components sorted by thickness values
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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.
Refresh Material List
Updates the list of available materials in the Component Table.
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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:
497
Title
Description
Vis
Visualization status. 1 = display on, 0 = display off
Part name
HyperMesh name of the component (maximum 32 characters)
Part id
HyperMesh ID of the component
Material name
Material name associated with the component
Material id
Material ID associated with the component
Material type
Material type associated with the component
Thickness
Thickness of elements specified in *section_shell
Section name
*Section name associated with the component
Section id
*Section ID associated with the component
Section type
Type of the *Section associated with the component
Color
Component color
Int points
Number of integration points specified for the *Section_shell
HGID
Hourglass ID associated with component
Elem form
Element formulation for the *section of the component
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Altair Engineering
Elems
Number of elements in the component
Nodes
Number of nodes in the component
Mass
Total mass of the component
cg_x
Center of gravity for the x coordinate
cg_y
Center of gravity for the y coordinate
cg_z
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Altair Engineering
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of 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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Altair Engineering
Export data from the Material Table
See also Creating, Editing, and Loading Materials Managing Materials LS-DYNA Material Table
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of 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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Altair Engineering
Sort Materials 1.
Click the column heading of the criteria by which you want to sort.
2.
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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.
Click Create/Load and select New… from the menu. New fields appear at the bottom of the Material Table.
2.
Type a name for the material in the New Material Name field.
3.
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.
4.
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.
5.
Click return to exit the Create/Load mode.
To create a new material based on an existing material: 1.
Select a material in the table that you want to use as the basis for a new material.
2.
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.
3.
Type a name for the material in the New Material Name field.
4.
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.
5.
Click return to exit the Create/Load mode.
507
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Altair Engineering
Edit a Material's Properties 1.
Select a material in the table that you want to edit.
2.
Click the Edit button. The card image for the material appears and, if applicable, the load curve appears in a pop-up window.
3.
Modify values in the card image and click return to go back to the Material Table.
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
508
Merge Materials 1.
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.)
2.
Click Merge As. The Material Table expands to include new fields for merging materials.
3.
Select the material ID to use as the new material in the Retain material(id) field.
4.
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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Altair Engineering
Find Duplicate Materials 1.
Ensure that ALL is selected in the Material type field.
2.
Click the Check duplicates button. The Material Table expands to include new fields for handling duplicate materials.
3.
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 group’s list of duplicate materials appears in the table.
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
510
See the Load Curve for a Material 1.
Select a material in the table for which a load curve ID has been defined.
2.
Click the Edit button. The load curve appears in a pop-up window.
511
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Altair Engineering
Export Data from the Material Table 1.
Select a material type or ALL from the Material type field to export only materials of a particular type or all materials, respectively.
2.
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.
3.
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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
Turns on and off all ellipsoids, planes, cylinders, and joints.
Elems
Turns on and off all FE elements.
Triads
Turns on and off all coordinate systems.
Shading
Set to visualization mode for the entire model. Four modes are available: 0
Performance graphics wireframe
1
Shaded
2
Shaded with mesh lines
3
Shaded with feature lines
Only Comps/MBs
Turns off all entities except elements, ellipsoids, planes, cylinders, and joints.
Clear Temp Nodes
Removes all temporary nodes (a.k.a. 3-D location markers)
Work in Meters
Reduces display size of coordinate system and boundary conditions for modeling in meters.
Autocolor
Colors all ellipsoids, planes, cylinders, and joints based on their rigid body reference. Also colors FE elements by part card.
The Tools page contains a series of utilities and tools:
513
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.
Elems to Ellipsoids
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.
Rotate Systems
Used to rotate coordinate systems about their axes.
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Altair Engineering
Resize Ellipsoids
Expands/shrinks ellipsoids about their individual axes.
Mesh Ellipsoids
Used to mesh ellipsoids. Mesh is created to represent the actual geometry of the ellipsoid.
Display Syst IDs
Turns on numerical ID display for specified coordinate systems. Useful for seeing which coordinate system is selected when selecting coincident coordinate systems.
Apply JNTPOS…
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.
Body Properties…
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.
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.
Parallel Local
Creates new coordinate systems at specified nodes. The created systems are oriented parallel to a specified local coordinate system.
From 3 Nodes
Opens the HyperMesh systems panel for created coordinate systems in any orientation by specifying three nodes or temporary nodes.
The New loc marker: options allow you to create new temporary nodes, which are used as location markers throughout HyperMesh. At Coord System
Creates a new marker at specified coordinate systems.
At Ellipsoids
Creates new markers at specified ellipsoids’ centers and axis.
Cover Ellipsoids
Covers ellipsoids with new markers.
At Body COGs
Creates new markers at specified rigid bodies’ center of gravities.
At Other
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
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
514
See also MADYMO Interface Overview
515
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
516
Nastran1 Page The following macros are available on the Nastran1 macro menu: Auto Property Creation
Auto Property Creation
Analysis Setup Load Steps Browser
517
If two or more components points to single property this utility will create a separate property for each component.
Generate Nastran subcase definitions.
BCTABLE Manager
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
Create, review, and edit components
Property Table
Create, review and edit properties
Material Table
Review and edit MAT1.
Miscellaneous RSSCON Create
Create a transition element between solids and shells.
RSPLINE Create
Create RSPLINE elements as bulk unsupported cards.
TABLE Create
Create a tabular function card.
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Synchronize the settings in the BCTABLE tool and the database.
Delete
Delete the selected BCTABLE.
Create
Create a new BCTABLE.
Close
Exit the BCTABLE Manager.
Contact Elems tab
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of 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
Add a row/contact element.
Delete
Delete the selected contact element.
Close
Exit the BCTABLE Manager.
Parameters tab
519
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Set to default values.
Update
Update the values.
Close
Close the tool.
Click the Slave and Master buttons to see all the BCBODYs.
See also Nastran Utility Menu
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of 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.)
2.
In the New part field, select a part (sub-model) to import. Click Import....
3.
(optional) Clear the Delete old part check box to save the old part at the end of the replacement procedure.
4.
(optional) Click View log… at any time to open the Part Replacement macro’s log file.
5.
Click Next. The following dialog appears:
521
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Altair Engineering
6.
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.
7.
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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.
See also Nastran Utility Menu
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of 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.
Select the component where the spider is needed. Click the … button to access a list of all available components.
3.
Select the Spider type: Normal or Washer. If you select Washer, an additional field appears on the dialog.
4.
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.
5.
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.
6.
Click Generate. The tool redraws the component chosen in step 2 using plotel elements around the holes and component perimeter.
7.
Pick a plotel element around the hole where the spider is needed.
8.
Click proceed.
See also Nastran Utility Menu
525
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Altair Engineering
PartInfo The PartInfo macro summarizes a part’s statistics in a dialog. 1.
To start the macro, click PartInfo on the Utility Menu.
2.
Click component in the main menu area to select a component or click a component in the graphics area to select it.
3.
Click proceed. The Part Information dialog appears, which lists the part ID, name, thickness, and material type.
4.
To view additional statistics about the part, click the More Details tab.
5.
To display statistics for a different part, select the part in the graphics area or the components selector and click proceed again.
Tip
Click the middle mouse button instead of the proceed button to quickly select components.
See also Nastran Utility Menu
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of 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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Altair Engineering
To Create a New Component 1.
From the Table menu of the Component Table, select New. The Component Create dialog opens.
2.
Type a name in the Component Name = field.
3.
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.)
4.
Click the Properties button to assign a property, or click the adjacent New button to define a new property and select it.
5.
Click Create.
6.
A panel opens, on which you must confirm the component creation. Click return. The new component appears in the Component Table.
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of 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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Altair Engineering
To Assign a Value to Multiple Components 1.
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.
2.
Select the column type you want to change from the Assign Values drop-down field.
3.
Type the new value in the adjacent field.
4.
Click Assign. The selected column types are updated to the new value you specified.
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of 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.
From the Table pull-down menu, select Filter…. The Filter dialog opens.
2.
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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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.
From the Table menu, select Configure and Columns… The Configure dialog opens.
2.
The Configure dialog contains a list of column types that are available. Select the check boxes for the data you want to view.
3.
Click OK.
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
532
To Export Data in CSV or HTML Format 1.
From the Table menu, click Save and then either CSV or HTML, depending on which type of data file you prefer.
2.
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.
3.
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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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.
From the Table pull-down menu, select Filter…. The Filter dialog opens.
2.
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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Altair Engineering
To Create a New Property 1.
From the Table menu of the Property Table, select New. The Property Create dialog opens.
2.
Type a name in the Property Name = field.
3.
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.)
4.
Select the type of property (PBAR, PBEAM, etc.)
5.
Click Create.
6.
A panel opens, on which you must confirm the property creation. Click return.
The new property appears in the Property Table.
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
536
To Assign a Value to Multiple Properties 1.
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.
2.
Select the column type you want to change from the Assign Values drop-down field.
3.
Type the new value in the adjacent field.
4.
Click Set. The selected column types are updated to the new value you specified.
537
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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.
From the Nastran Utility Menu, click Material Table.
2.
Click Create Mat1....
3.
The following dialog is displayed.
4.
Fill in the necessary fields.
5.
Click Create. The material is created and added to the Material Table.
To delete MAT1: 1.
From the Nastran Utility Menu, click Material Table.
2.
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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.
Click the RSSCON Create macro.
2.
Pick the elements to be connected in the model.
3.
Click proceed.
Note:
539
When you renumber element or node IDs, RSSCON elements are not also updated because they are supported only as text.
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Altair Engineering
RSPLINE Create The RSPLINE Create macro creates RSPLINE elements as bulk unsupported cards.
To create an RSPLINE element: 1.
Click the RSPLINE create macro.
2.
Select nodes on the model.
3.
Click proceed.
The default value for the third field of this card is 0.1.
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of 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.
Type values in the XY table for the XY pairs you want to include in the table.
3.
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.
Click Apply.
5.
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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Altair Engineering
2.
In the File field, specify an XY data file. This file must be either .csv or .txt format.
3.
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.
Click Apply.
5.
Click Exit.
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
542
Nastran2 Page The following macros are available on the Nastran2 macro menu: Miscellaneous Convert Shells
543
Convert degenerate second order shells into first order shells.
Display Sets
Review and expand (before renumber) SETs.
Tag on Nodes
Create a tag on every node that has a comment in its 10th field.
SPOINT
Create SPOINT.
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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.
Select the file for which the second order shell elements are to be converted.
2.
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.
See also Nastran Utility Menu
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of 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.
Choose the SETs from the Selection column.
2.
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.
See also Nastran Utility Menu
545
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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.
Choose the color of the tags.
2.
Click create.
See also Nastran Utility Menu
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of 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
2.
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.
See also Nastran Utility Menu
547
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
548
Tool Menu The Tool menu options allow you to simplify safety tasks. The following macros are included: View Manager
Allows you to save and restore different view of the model.
Dummy Positioning Tool Start …
Starts process manager and loads the Pamcrash2G_DummyPos template in preparation for dummy positioning.
DummyPosPanel
Opens the dummy positioning panel in HyperMesh and sets the radio button to incremental positioning.
Update Jt Angles
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 …
Creates and modifies substructures.
RBODY Manager
Displays information about rigid bodies in the model.
Part Replacement …
Replaces an existing part with a new part.
Part Info
Displays statistics of a selected part.
Organize Xlinks
Organize LINK-type elements among components.
MASS Manager
Displays information about masses in the model.
Apply Initial Metric
Apply an initial metric to the model.
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.
By Name
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.
Resolve include
549
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Altair Engineering
Resolve…
Resolves the include files with the INCLU / card recursively. You must give the original file name and the target file name.
Edit…
Allows you to edit the target file from the Resolve macro.
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.
All
Displays the result file containing information related to all the entities of the model.
Dis
Displays information related to the entities currently displayed on the screen. Only the result file is displayed. Input Fields in the User Interface
Protocol file Show
Displays the user message box.
Clear
Clears the user message box.
Hmx file Show
Displays the recent .hmx file for the imported FE input model.
Delete…
Deletes the recent .hmx file for the imported FE input model.
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.
Show
Displays the help file using the configuration created with the Define macro, described above.
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.
Overwrite
Overwrites the Model Documentation card from the Imported Documentation card.
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of 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.
Component Table
Displays components and their associated attributes in an interactive table. This macro appears on all Utility sub-menus.
See also Conn Card Find M1 M2 Sum Tool
551
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Action
Configure Process:
Select either Interactive positioning or Automatic positioning. Depending on the selection, the process tree will change.
Interactive Positioning:
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.
LoadNoDummyFiles
Allows you to import other parts of the model, which may be required in order to position the dummy correctly.
SelectJoints
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.
CreateTransformation
Once finished with the positioning of the dummy, you can save this information into a transformation file.
CreateDocumentation
This enables you to update the model documentation as well as create HTML documentation of the process. You can also
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of 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.
Automatic Positioning:
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.
LoadOnlyDummy
Same as LoadDummy.
ExecuteTransformatio You can select a transformation file, which will n be executed automatically to position the dummy.
Note:
Documentation
Same as CreateDocumentation.
ExportDummy
Same as ExportFiles.
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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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 ( -270°C to +270°C ) 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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
558
Part Info Macro The Part Info macro summarizes a part’s statistics in a dialog. 1.
To start the macro, click Part Info on the Utility Menu.
2.
Click component on the main menu area to select a component or click a component in the graphics area to select it.
3.
Click proceed. The Part Information dialog appears, which lists the part ID, name, thickness, and material type.
4.
To view additional statistics about the part, click More Detail>>.
5.
To display statistics for a different part, select the part in the graphics area or the components selector and click proceed again.
Tip
Click the middle mouse button instead of the proceed button to quickly select components.
See also Tool Macro Menu
559
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
The name of the substructure
IDEF
Indicates the definition type of the substructure: 0: Only via elements 1: Via elements and boundary nodes 2: Only via boundary nodes
DTSUB
Specifies the time intervals for the boundary node displacement time histories
Elements
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.
Boundary Nodes
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.
Filename SUBRUN
Name of the file that contains the definition of the substructure and its boundary node displacements
Time Factor
Time unit scaling factor
Length Factor
Length unit scaling factor
See also Tool Macro Menu
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of 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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Description
Disp
Indicates whether the rigid body is displayed in the graphics area.
ID
The ID number of the rigid body.
Title
The descriptive name of the rigid body.
Master Node
The ID of the node that serves as the master node of the rigid body.
Type
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
Action
Review Options
Customize the way the selected rigid bodies are displayed. Options include transparency and auto-review selections.
Review
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.
Find Attached
Highlights the elements that are attached to the selected rigid body.
Edit
Modify the definition of the rigid body through the rigid panel.
Card Edit
Opens the RBODY card in the card editor.
Delete
Deletes the selected rigid body.
Refresh
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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.
See also Tool Macro Menu
563
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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.
See also Tool Macro Menu
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of 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:
Select the element type you want to work with.
Prefix:
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.
Click the component button to select a component to which you want to add the selected elements.
3.
Click Apply. The selected elements are added to the selected component.
See also Tool Macro Menu
565
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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.
See also Tool Macro Menu
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
566
Input Fields in the Show ID Ranges User Interface
Input Fields in the User Interface:
567
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.
Maximum Number of Ranges
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.
Display Id’s Type
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.
Display Entity 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.
Overview Type
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.
Id Info for Entities
Allows you to specify whether you want the information for all the entities in the model or only for the entities currently displayed.
Comment String for Solver
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.
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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
Shows the 1D, 2D, and 3D PART cards of the displayed components in a viewer.
MATER
Shows the 1D, 2D, and 3D MATER cards of the displayed components in a viewer.
NSM
Shows the NSM cards of the displayed groups in a viewer.
CNTAC
Shows the CNTAC cards of the displayed groups in a viewer.
SECFO
Shows the SECFO cards of the displayed groups in a viewer.
RWALL
Shows the RWALL cards of the displayed groups in a viewer.
GROUP
Shows the GROUP cards of the displayed sets in a viewer.
HM entities: Properties
Shows all properties cards of the displayed properties in a viewer.
Sensors
Shows all SENSOR cards of the displayed sensors in a viewer.
Loads
Shows all loads and load collectors cards of the displayed loads and load collectors in a viewer.
Curves
Shows all FUNCT cards of the model in a viewer.
Airbags
Shows all BAGIN and CHAMBER cards of the displayed control volumes in a viewer.
See also Conn Find M1 M2 Sum Tool
569
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Altair Engineering
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of 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.
Materials All/Dis
Execute the materials_txt summary and show the results for the complete/displayed model in a viewer.
Elements All/Dis
Execute the elements_txt summary and show the results for the complete/displayed model in a viewer.
Center Of Gravity All/Dis
Execute the ctr_of_gravity_txt summary and show the results for the complete/displayed model in a viewer.
Moment Of Inertia All/Dis
Execute the moment_of_inertia_txt summary and show the results for the complete/displayed model in a viewer.
Interfaces All/Dis
Execute the groups_txt summary and show the results for the complete/displayed model in a viewer.
Non Struct Masses All/Dis
Execute the nsmas_txt summary and show the results for the complete/displayed model in a viewer.
Property ALL
Execute the property_txt summary and show the results for the complete/displayed model in a viewer.
Sensors ALL
Execute the sensors_txt summary and show the results for the complete/displayed model in a viewer.
See also Conn Card Find M1 M2 Sum Tool
571
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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.
PLY_DATA
Enters the components panel, selects the mats collector, and sets the correct dictionary.
Mass elements: MASS
Sets the element type mass = to MASS and enters the mass panel.
NSMAS
Enters the interfaces panel and sets the card image to nsmas.
Constraints: RBODY
Sets the element type rigid = to RBODY and enters the rigids panel.
NODCO
Sets the element type rigid = to NODCO and enters the rigids panel.
RWALL
Enters the rigid walls panel and set the card image = to RWALL.
CNTAC
Enters the interfaces panel and sets the card image = to CNTAC.
TIED
Enters the interfaces panel and sets the card image = to TIED.
Elements: BAR
Sets the element type 1dele = to BAR and enters the 1d elems panel.
BEAM
Sets the element type beam = to BEAM and enters the beams panel.
KJOINT
Sets the element type 1dele = to KJOIN and enters the 1d elems panel.
JOINT
Sets the element type 1dele = to JOINT and enters the 1d elems panel.
SPRING
Sets the element type spring = to SPRING and enters the springs panel.
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
572
SHELL
Sets the element type tria3 = and quad4 = to SHELL.
MEMBR
Sets the element type tria3 = and quad4 = to SHELL.
TRIA_C
Sets the element type tria3 = TRIA_C.
SOLID
Sets the element type tetra4, pyramid5, penta6, and hex8 = to SOLID.
BSHEL
Sets the element type hex8 = to BSHEL.
Link elements: PLINK
Sets the element type mass = to PLINK and enters the mass panel.
ELINK
Sets the element type 1dele = to ELINK and enters the 1d elems panel.
LLINK
Sets the element type 1dele = to LLINK and enters the 1d elems panel.
SLINK
Sets the element type tria3 = and quad4 = to SLINK.
See also Conn Card Find M2 Sum Tool
573
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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.
RUPMO
Enters the components panel, selects the props collector, and sets card image = to RUPTURE_MODEL.
SENSO
Enters the sensors panel.
CURVES
Enters the edit curves panel and set the radio button to modify.
Safety: SLIPR
Sets element type mass = to SLIPRING and enters the mass panel.
RETRA
Sets element type mass = to RETRACTR and enters the mass panel.
BAGIN
Enters the airbag panel and sets the card image to BAGIN.
CHAMB
Enters the airbag panel and sets the card image to CHAMBER.
GASPC
Enters the components panel, selects the props collector, and sets card image = to GASPEC.
Plot output: THNOD
Enters the output blocks panel and changes the type to nodes.
THELE
Enters the output blocks panel and changes the type to elements.
SENPT
Sets element type mass = to SENPT and enters the mass panel.
SECFO_SECTION
Enters the interfaces panel and sets card image = to SECFO_SECTION.
SECFO_SUPPORT
Enters the interfaces panel and sets card image = to SECFO_SUPPORT.
SECFO_VOLFRAC
Enters the interfaces panel and sets card image = to SECFO_VOLFRAC .
SECFO_PLANE
Enters the rigid walls panel and sets card image = to SECFO_PLANE.
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
574
Nodals: FRAME
Enters the systems panel.
NODE
Enters the nodes panel.
INVEL
Sets load type velocity = to INVEL and enters the velocity panel.
VEL3D
Sets load type velocity = to VEL3D and enters the velocity panel.
RVE3D
Sets load type velocity = to RVE3D and enters the velocity panel.
ACC3D
Sets load type acceleration = to ACC3D and enters the acceleration panel.
RDV3D
Sets load type velocity = to RDV3D and enters the velocity panel.
RDA3D
Sets load type acceleration = to RDA3D and enters the acceleration panel.
RAC3D
Sets load type acceleration = to RAC3D and enters the acceleration panel.
BOUNC
Sets load type constraint = to BOUNC and enters the constraints panel.
DIS3D
Sets load type constraint = to DIS3D and enters the constraints panel.
DIS3DX
Sets load type constraint = to DIS3DX and enters the constraints panel.
DIS3DM
Sets load type constraint= to DIS3DM and enters the constraints panel.
RAN3D
Sets load type constraint= to RAN3D and enters the constraints panel.
RDD3D
Sets load type constraint= to RDD3D and enters the constraints panel.
CONLO
Sets load type force= to CONLO and enters the forces panel.
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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Altair Engineering
Find M1 Sum Tool
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of 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
Organizes the connectors by the parts of the associated Plink elements.
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
Enters the connectors panel, and then fe absorb/quality/fe realize panel, depending on the selected macro.
Find att to P(X)LINKs
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
Finds entities attached to the displayed components.
Find/Mask
Finds/Masks the entities depending upon the selected macros.
See also Card Find M1 M2 Sum Tool
577
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Altair Engineering
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of 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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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.
See also Conn Card Find M1 M2 Sum Tool
581
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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.
See also Conn Card Find M1 M2 Sum Tool
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of 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:
583
Convert Groups
Convert element-based surfaces that were created in Abaqus to PERMAS surfaces
PLOT NLLOAD
Macro plotting NLLOAD cards
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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.
Place a check next to NLLOAD.
3.
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.
Enter a value in the NoOfLPATS field. This determines the number of load patterns (load collectors) you want to add to the NLLOAD card.
5.
Enter the value in the TimeSteps field in the upper part of the card image.
6.
For each TIME/STEP pattern created, enter values in the TIME fields to set the starting value and the increment values.
7.
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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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.
Click return to close the Card Editor.
9.
Click return to close the Load Steps panel.
Note:
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.
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.
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.
3.
Use the Display checkbox to turn the display of particular load steps on and off.
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
586
587
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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.
From the Preferences menu, select the User Profile option.
2.
Select the RADIOSS Block profile.
3.
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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
Creates a new component quickly.
Clone Part
Creates a new part from the properties of an existing part.
Part Info
Displays statistics of a selected part.
Material Table...
Allows you to easily create materials for RADIOSS (Block Format).
Component Table
Opens the Components and Properties table, displaying a tabular list of the \PARTs (components) in the model.
Relative Displacement
Helps create the TH/SPRING card, which supports time histories with spring output.
RBODY Manager
Displays information about rigid bodies in the model.
BCs Manager
Creates boundary conditions of any load collector type other than ACTIV.
ADMAS Manager
Displays information about masses in the model.
Accelerometer
Creates and edits time history ACCEL cards to track accelerometer output requests.
Welds
Creates meshless welding using the RADIOSS (Block Format) interface type 2 and springs.
Delete Dup Elems
Identifies and removes duplicate master and slave elements from Interface and Rigidwall.
Engine File Tool
Exports cards with runtime options in D01 format.
Model Check
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.
See also RADIOSS (Block Format) Utility Menu
589
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Altair Engineering
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of 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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Altair Engineering
master node ID, and type is shown. Column
Description
Disp
Indicates whether the rigid body is displayed in the graphics area.
ID
The ID number of the rigid body.
Title
The descriptive name of the rigid body.
Master Node
The ID of the node that serves as the master node of the rigid body.
Type
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
Action
Review Options
Customize the way the selected rigid bodies are displayed. Options include transparency and auto-review selections.
Review
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.
Find Attached
Highlights the elements that are attached to the selected rigid body.
Edit
Modify the definition of the rigid body through the Rigid panel.
Card Edit
Opens the RBODY card in the Card Editor.
Delete
Deletes the selected rigid body.
Refresh
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Altair Engineering
Part Info The Part Info macro summarizes a part’s statistics in a dialog. 1.
To start the macro, click Part Info on the Utility Menu.
2.
Click component on the main menu area to select a component or click a component in the graphics area to select it.
3.
Click proceed. The Part Information dialog appears, which lists the part ID, name, thickness, and material type.
4.
To view additional statistics about the part, click More Detail>>.
5.
To display statistics for a different part, select the part in the graphics area or the components selector and click proceed again.
Tip
Click the middle mouse button instead of the proceed button to quickly select components.
See also Tools Menu RADIOSS (Block Format) Utility Menu
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of 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.
See also Tools Menu RADIOSS (Block Format) Utility Menu
595
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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.
See also Tools Menu RADIOSS (Block Format) Utility Menu
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of 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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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 tool’s 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.
599
GENERAL
Contains fields for several basic keywords. The /RUN and /VERS fields are required.
ANIM
Contains animation-related options.
BC
Contains boundary condition-related options.
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Altair Engineering
DEL
Contains deletion-related options including interfaces and elements.
DT
Contains options related to time step defaults.
FUNCT
Contains the keyword for redefining the function number Ifunc.
INTER
Contains the keyword for activation and deactivation of interfaces.
RBODY
Contains options for rigid body activation and deactivation.
MISC
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.
INIV
Contains options to set initial rotational and translational velocities for single or multiple sets of nodes.
VEL
Contains options to set rotational and translational velocities.
UNSUP
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.
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.
Clear
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).
Undo
Deletes data on the current tab that has been entered since the last time the database was refreshed with the Apply button.
Export
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.
Close
Closes the Engine File Tool macro.
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
600
See also Tools Menu RADIOSS (Block Format) Utility Menu
601
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
604
605
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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.
2.
Select the spring property file.
3.
Specify the Spring FE config and an appropriate weld research tolerance.
4.
Click create.
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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
0.002 0.1
K1
100.0
K2
500.0
K3
500.0
K4
5000.0
K5
5000.0
K6
5000.0
Delmin1
-1.25
Delmax1
1.25
Delmin2
-1.25
Delmax2
1.25
Delmin3
-1.25
Delmax3
1.25
Delmin4
0.0
Delmax4
0.0
Delmin5
0.0
Delmax5
0.0
Delmin6
0.0
Delmax6
0.0
End
615
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Altair Engineering
# Normal Force Function CVID1
9 -100.0
0.0
-1.26
0.0
-1.25
-Fn
-0.125
-Fn
0.0
0.0
0.125
Fn
1.25
Fn
1.26
0.0
100.0
0.0
# End Normal Force Function
# Shear Force Function CVID2
9 -100.0
0.0
-1.26
0.0
-1.25
-Fs
-0.125
-Fs
0.0
0.0
0.125
Fs
1.25
Fs
1.26
0.0
100.0
0.0
# End Shear Force Function
Generic Spot Weld Failure Force Table Sheet metal gauge in mm T > Steel
Altair Engineering
Shear force
T =<
Fs[kN]
Normal force Fn[kN]
YS < 120 MPa
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
616
~
0.6
2.7
0.9
0.6
0.8
3.6
1.2
0.8
0.9
4.4
1.5
0.9
1.0
5.3
1.9
1.0
1.1
6.2
2.2
1.1
1.3
7.1
2.5
1.3
1.4
8.0
2.8
1.4
1.5
9.1
3.2
1.5
1.8
11.1
3.9
1.8
2.0
12.5
4.4
2.0
2.3
15.1
5.3
2.3
2.7
18.2
6.4
2.7
~
21.8
7.6
Steel1
617
YS = 120to220 MPa ~
0.6
2.7
0.9
0.6
0.8
3.6
1.2
0.8
0.9
4.4
1.5
0.9
1.0
5.3
1.9
1.0
1.1
6.2
2.2
1.1
1.3
7.1
2.5
1.3
1.4
8.0
2.8
1.4
1.5
9.1
3.2
1.5
1.8
11.1
3.9
1.8
2.0
12.5
4.4
2.0
2.3
15.1
5.3
2.3
2.7
18.2
6.4
2.7
~
21.8
7.6
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Altair Engineering
Steel3
YS = 221to500 MPa ~
0.6
4.9
1.7
0.6
0.8
6.7
2.3
0.8
0.9
8.5
3.0
0.9
1.0
10.2
3.6
1.0
1.1
12.0
4.2
1.1
1.3
13.8
4.8
1.3
1.4
15.6
5.5
1.4
1.5
17.8
6.2
1.5
1.8
21.8
7.6
1.8
2.0
25.0
8.8
2.0
2.3
31.1
10.9
2.3
2.7
38.7
13.5
2.7
~
44.5
15.6
Steel4
YS > 500 MPa ~
0.6
4.9
1.7
0.6
0.8
6.7
2.3
0.8
0.9
8.5
3.0
0.9
1.0
10.2
3.6
1.0
1.1
12.0
4.2
1.1
1.3
13.8
4.8
1.3
1.4
15.6
5.5
1.4
1.5
17.8
6.2
1.5
1.8
21.8
7.6
1.8
2.0
25.0
8.8
2.0
2.3
31.1
10.9
2.3
2.7
38.7
13.5
2.7
~
44.5
15.6
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of 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.
See also Tools Menu RADIOSS (Block Format) Utility Menu
619
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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.
Select the Tools macro page.
2.
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.
Enter a name for the new material in the New Material Name: field.
2.
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.
Altair Engineering
Input the appropriate values as necessary for the material in the card image.
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
620
Same as
4.
After you input the values, click return to exit from the panel.
5.
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.
Left click on the material row that you want to duplicate.
2.
Click Create/Load.
3.
Click Same as...
4.
Specify a name for the new material in the New Material Name: field.
5.
Click create/edit to display the card image.
6.
Specify the appropriate values and click return on the panel.
7.
Click Return in the material table.
Note:
The E, Nu, and Rho columns are populated only if the fields are available in the material card.
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.
Edit...
1.
Left click on the material row that you want to edit.
2.
Click Create/Load.
3.
Make a selection in the Material Type: field.
4.
Click the Load/edit button.
5.
Specify the appropriate values and click return on the panel.
Displays the card image, where you can input values.
Merge As Check Duplicates
621
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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.
Review the threshold settings in the Options menu. Set values that are meaningful for your model.
3.
Review the model check tool settings from the Interrogator Settings option of the Options menu.
4.
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.
5.
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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
623
Refresh
Regenerates the table with all the parts in the model
Editable
Sets the table mode to editable mode, allowing you to change values for the selected components
Filter
Enables the filtering GUI
Configure
Allows you to specify the number and type of columns listed in the table
Save
Saves the information listed in the table in CSV or HTML format
Quit
Quit the table function.
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Altair Engineering
Selection All
Selects all rows or parts
None
Selects none or deselects parts/rows that were previously selected
Reverse
Reverses the selection
Displayed
Selects the rows or the displayed parts
User
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
Displays all the components in the model
None
Turns off every component displayed
Reverse
Reverses the display of the part
Show selection
Displays the components of the selected rows
Show only Selection
Displays only the components of the selected rows
Hide selection
Hides the components of the selected rows from the display
By Material
Displays components sorted by material
By Properties
Displays components sorted by properties
By Thickness
Displays components sorted by thickness values
Action Delete Selection
Deletes selected rows (parts) from the model
Create Part
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
624
User Set MatDB Path…
Opens a dialog on which you can set the location of an external database of material definitions.
Refresh Material List
Updates the list of available materials in the Component Table.
See also Editable Mode Filter Configure Columns All or Displayed Mode
625
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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.
See also Component Table RADIOSS (Block Format) Utility Menu
627
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Description
Vis
Visualization status. 1 = display on, 0 = display off
Part Title
Title of the part
Part id
HyperMesh ID of the component
Prop name
HyperMesh name of the property
Prop id
HyperMesh ID of the property
Prop Type
Property type associated with the component
Material name
Material name associated with the component
Material id
Material ID associated with the component
Material type
Material type associated with the component
Thick
Thickness of elements specified in *section_shell
Elems
Number of elements in the component
Nodes
Number of nodes in the component
Color
Component color
SigY Harden_Param(b) Mass
Total mass of the component
cg_x
Center of gravity for the x coordinate
cg_y
Center of gravity for the y coordinate
cg_z
Center of gravity for the z coordinate
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
628
See also Component Table RADIOSS (Block Format) Utility Menu
629
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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.
See also Component Table RADIOSS (Block Format) Utility Menu
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
630
Other Tools The following tools are also available:
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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 accelerometer’s 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 tool’s 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
Altair HyperMesh User's Guide Proprietary Inform ation of 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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Altair Engineering
2.
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.
3.
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.
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.
2.
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Altair Engineering
Creating New Boundary Conditions
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
636
1.
To begin creating a new boundary condition, select the type of boundary condition you want to create in the Select type: field.
2.
In the Name field, type a name for the load collector .
3.
Select the type from the drop down menu in the Select type field. Based on the type selected, the options that display may change.
4.
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.
5.
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
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.
637
Highlight a boundary condition in the list to display its properties. This opens the editing mode of the dialog, as shown below.
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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.
3.
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
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of 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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Altair Engineering
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of 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
Convert from I-DEAS to RADIOSS (Bulk Data Format)
Export in MDL
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
Create, review and edit materials
Component Table
Create, review and edit components
1D Property Table
Create, review and edit properties
Load Collector Table
Review and edit load collectors
Curve Editor
Launches the Curve Editor
TABLE Create
Create a tabular function card.
Loadsteps Browser
Generate RADIOSS (Bulk Data Format) subcase definitions.
Buckling
Create a linear buckling subcase and referenced static subcase.
Tools
LoadSteps
Fatigue Process
Create New Load Existing
Solution
643
Model Checker
Model checker
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Altair Engineering
Altair Engineering
Radioss
Shortcut to the Radioss panel.
OptiStruct
Shortcut to the OptiStruct panel.
Altair HyperMesh User's Guide Proprietary Inform ation of 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.
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.
2.
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.
3.
Click Convert.
645
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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.
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.
2.
Click Accept to export body and joint definitions to an MDL file.
and, on the Save
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.
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of 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.)
3.
In the New part field, select a part (sub-model) to import. Click Import....
4.
(optional) Clear the Delete old part check box to save the old part at the end of the replacement procedure.
5.
(optional) Click View log… at any time to open the Part Replacement macro’s log file.
6.
Click Next.
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.
8.
Click Next. The following dialog appears:
647
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Altair Engineering
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of 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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Altair Engineering
Assign Values drop-down, type the new value in the adjacent field, and click Set.
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of 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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Altair Engineering
See also Utility Menu
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
658
Buckling The Buckling utility allows a buckling subcase to be defined simultaneously with its referenced static subcase.
1.
Enter name.
2.
Provide data for V1, V2 (upper and lower limits for eigenvalue calculation) and/or ND (number of modes to be calculated).
3.
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.
See also Utility Menu
659
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Options
Save Report
Allows you to select a file name and location to save the information in the report window to a text file.
Clear Report Window
Deletes everything from the report window.
Close
Exit and close the Model Checker.
Open Settings
Allows you to retrieve settings from a data file.
Save Settings
Allows you to save the current settings to a data file.
1D Element Quality Settings…
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…
Altair Engineering
Allows you to alter settings for 3-D element checks. The settings which can be altered are:
Altair HyperMesh User's Guide Proprietary Inform ation of 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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Altair Engineering
Output % failed - element quality (Default = yes) Output warning/error count for property checks (Default = no)
Run
Settings to defaults (all)
Reset all settings to defaults.
Select Tests
Allows you to check which tests to perform from the list: Property Checks Material Checks Element Checks Loadstep Checks Default (all)
Help
Run Model Checker
Performs model checking and populates the report window with the results.
Help
Provides operation instructions.
About
Provides information about version and developer.
See also Utility Menu
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
662
Opti Page The following macros are available on the Opti page of the Nastran Utility Menu:
Topology
Del All Opt Entities
Deletes all DesignVariable, OptimizationResponse, DesignVariablePropertyRelationship, OptimizationConstraint, Objective, ObjectiveReference, OptimizationTableEntry, OptimizationEquation, DesignVariableLink, OptimizationControl, and OptimizationConstraintScreening entities.
Voxelmesh
Creates voxels (hexa elements) from closed shell meshes.
Hex-core Design Space
Shortcut to the Topology panel.
Matfrac
Setup a material fraction topology optimization.
Reg. Volfrac
Create regional volfrac responses combining several components, properties or materials
Topography
Design Space
Shortcut to the Topography panel.
Shape
Create Shapes
Shortcut to the HyperMorph panels.
Shape Variables
Shortcut to the Shape panel.
Size Variables
Shortcut to the Size panel.
PBAR, PROD Opti
Define size optimization for multiple PBAR or PROD sections.
CBAR, CROD Opti
Define size optimization for multiple CBAR or CROD elements with circular section.
Design Variables
Create, review and edit Size (including Gauge) and Shape Design Variables.
Design Constraints
Review and edit optimization constraints.
Size
Optimization Info
663
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Altair Engineering
Solution
OptiStruct
Shortcut to the OptiStruct panel.
OSSmooth
Shortcut to the OSSmooth panel.
OSSmooth Volume
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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.
Select components that contain shell elements enclosing one volume. (If more than one volume is selected, normals should be adjusted manually).
3.
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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Altair Engineering
volume. So the memory usage may be high for unreasonably small values. 3.
Click Start.
4.
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.
See also Utility Menu
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of 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.
Click Matfrac.
2.
Enter a matfrac value.
3.
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.
See also Utility Menu
667
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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.
See also Utility Menu
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of 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.
Select properties.
3.
Select either a PBAR or a PROD card and a section type.
4.
Enter initial values and bounds.
5.
Click calculate. Depending on the cross section, a number of design variables, equations, and DVPREL2 cards are generated.
See also Utility Menu
669
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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.
Select elements.
3.
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.
See also Utility Menu
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
670
671
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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.
In the table, click on the Initial Value, Lower Bound, or Upper Bound field of a design variable.
2.
Replace the current value with the desired value.
3.
Hit the Enter key. The design variable is updated.
To create a design variable: 1.
Click
.
The following dialog is displayed.
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
672
2.
Fill in the fields as desired.
3.
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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Altair Engineering
See also Utility Menu
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of 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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Altair Engineering
See also Utility Menu
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of 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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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)
(2)
(3)
(4)
(5)
(6)
(7)
(8)
(9)
MAT1
MID
E
G
NU
RHO
A
TREF
GE
ST
SC
SS
(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
Altair HyperMesh User's Guide Proprietary Inform ation of 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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
680
681
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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
60000.0 0.0
0.33
0.101 1.20E-050.0
0.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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
684
Morphing Entities Optimization Entities Solver Templates FE Input and Result Readers
685
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Altair Engineering
Example Template Code Example Template Code ([Install Directory]\hm\examples\templates\ExampleTemplate.tpl) * c odename( Ex ampl eTempl at e, 100) / / MAT1 At t r i but es * def i neat t r i but e( MAT1, 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) / / Mat er i al s Named Ent i t y - MAT1 Car d I mage and Ex por t For mat * mat er i al s ( MAT1) / / MAT1 Car d I mage * begi nmenu( ) * menus t r i ng( " MAT1
")
* menuf i el d( " I D" , i nt eger , i d, 8) * menuf i el d( " E" , r eal , $E, 8) * menuf i el d( " G" , r eal , $G, 8) * menuf i el d( " NU" , r eal , $NU, 8) * menuf i el d( " RHO" , r eal , $RHO, 8) * menuf i el d( " A" , r eal , $A, 8) * menuf i el d( " TREF" , r eal , $TREF, 8) * menuf i el d( " GE" , r eal , $GE, 8) * menul i neend( ) * menus t r i ng( "
")
* menuf i el d( " ST" , r eal , $ST, 8) * menuf i el d( " SC" , r eal , $SC, 8)
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
686
* menuf i el d( " SS" , r eal , $SS, 8) * menul i neend( ) * endmenu( ) / / MAT1 Ex por t For mat * f or mat ( ) * s t r i ng( " MAT1
")
* 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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Altair Engineering
Example FE-Input Code Example FE-Input Code ([Install Directory]\hm\examples\feinput\ExampleFEInput.cxx) #i nc l ude #i nc l ude #i nc l ude #i nc l ude " hml i b. h" #i nc l ude " hmi nl i b. h" us i ng names pac e s t d; / / Mat er i al Dat a St r uc t ur e i nt nummat er i al s ; s t r uc t mat er i al s { c har name[ 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; } mat 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 Mat er i al s ( ) ; i nt mai n( i nt ar gc , c har * ar gv [ ] ) { / * The mai 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 Mes h, s et s t he s ol v er t o 100 ( t he s ame number def i ned in t he t empl at e) , r eads t he model and pas s es mat er i al dat a s t r uc t ur es t o Hy per Mes 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 HMI HMI HMI HMI
_dat a( ar gv [ 1] ) ; N_i ni t ( " Ex ampl eFEI nput " , " 10. 0" , ar gc , ar gv ) ; N_s et s ol v er ( 100) ; N_r eadmodel ( 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 gument on t he
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
688
i nput l i ne and r eads t he s ol v er dec k f or MAT1 c ar ds .
I f a MAT1 c ar d i s
f ound t hen t he MAT1 s ol v er c ar d i s r ead and a mat er i al popul at ed. * /
dat a s t r uc t ur e i s
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) ; / / Read Sol v er Dec k f or MAT1 Sol v er Car ds and Popul at e Mat er i al Dat a St r uc t ur e nummat 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 ( s t r c mp( t ok en, " MAT1 " ) == 0) { / / Name s t r c py _s ( mat er i al [ nummat er i al s ] . name, " mat er i al " ) ; //id i nf i l e. get ( t ok en, 9) ; mat er i al [ nummat er i al s ] . i d = at oi ( t ok en) ; //E i nf i l e. get ( t ok en, 9) ; mat er i al [ nummat er i al s ] . E = at of ( t ok en) ; //G i nf i l e. get ( t ok en, 9) ; mat er i al [ nummat er i al s ] . G = at of ( t ok en) ; / / NU i nf i l e. get ( t ok en, 9) ; mat er i al [ nummat er i al s ] . NU = at of ( t ok en) ; / / RHO i nf i l e. get ( t ok en, 9) ; mat er i al [ nummat er i al s ] . RHO = at of ( t ok en) ; //A i nf i l e. get ( t ok en, 9) ; mat er i al [ nummat er i al s ] . A = at of ( t ok en) ; / / TREF i nf i l e. get ( t ok en, 9) ; mat er i al [ nummat er i al s ] . TREF = at of ( t ok en) ; / / GE i nf i l e. get ( t ok en, 9) ; mat er i al [ nummat 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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Altair Engineering
mat er i al [ nummat er i / / SC i nf i l e. get ( t ok en, mat er i al [ nummat er i / / SS i nf i l e. get ( t ok en, mat er i al [ nummat er i i nf i l e. get ( ) ; nummat er i al s ++;
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) ;
} el s e 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 hmi us ed by hmi 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 mat 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, mus t r et ur n NULL. * /
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
s wi t c h ( f unc t i on) { c as e HMI N_OPENFUNCTI ON: br eak ; c as e HMI N_ENTI TYOPENFUNCTI ON: br eak ; c as e HMI 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_MATS: r et ur n( HM_get Mat er i al s ) ; c as e HM_ENTI TYTYPE_PROPS: br eak ; c as e HM_ENTI TYTYPE_COMPS:
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of 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 ;
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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 ;
} br eak ; c as e HMI N_ENTI TYCLOSEFUNCTI ON: br eak ; c as e HMI N_NAMEFUNCTI ON: br eak ; c as e HMI N_MOVEFUNCTI ON:
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
692
br eak ; c as e HMI N_COLORFUNCTI ON: br eak ; c as e HMI N_ASSOCI ATEFUNCTI ON: br eak ; c as e HMI N_CEDATAFUNCTI ON: br eak ; c as e HMI N_METADATAFUNCTI ON: br eak ; c as e HMI N_CLOSEFUNCTI ON: br eak ; } r et ur n( NULL) ; } i nt HM_get Mat er i al s ( ) { / * Thi s f unc t i on wr i t es eac h mat er i al */
dat a s t r uc t ur e t o Hy per Mes h.
i nt i ; / / Wr i t e eac h mat er i al dat a s t r uc t ur e t o Hy per Mes h f or ( i =0; i
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_MATS, mat er i al [ i ] . i d, 2, t r i but e_doubl e( HM_ENTI TYTYPE_MATS, mat er i al [ i ] . i d, 3, t r i but e_doubl e( HM_ENTI TYTYPE_MATS, mat er i al [ i ] . i d, 4, t r i but e_doubl e( HM_ENTI TYTYPE_MATS, mat er i al [ i ] . i d, 5, t r i but e_doubl e( HM_ENTI TYTYPE_MATS, mat er i al [ i ] . i d, 6, t r i but e_doubl e( HM_ENTI TYTYPE_MATS, mat er i al [ i ] . i d, 7, t r i but e_doubl e( HM_ENTI TYTYPE_MATS, mat er i al [ i ] . i d, 8, t r i but e_doubl e( HM_ENTI TYTYPE_MATS, mat er i al [ i ] . i d, 9, t r i but e_doubl e( HM_ENTI TYTYPE_MATS, mat er i al [ i ] . i d, 10, t r i but e_doubl e( HM_ENTI TYTYPE_MATS, mat er i al [ i ] . i d, 11,
r et ur n( 0) ; }
693
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Altair Engineering
See also HyperMesh Entities & Solver Interfaces
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of 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:
695
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.
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Altair Engineering
See also HyperMesh Entities & Solver Interfaces
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of 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.
skip includes
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.
merge includes
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.
697
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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.
o
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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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.
o
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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 # = 1…n and shown in the include browser. These will not be exported unless the user changes the Instance option check box off.
701
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
RADIOSS (Block Format)
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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.
Exported in large field format by optistructlf template.
SPOINT
Defines a scalar point.
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
Notes
*NODE
Specify nodal coordinates
NSET and SYSTEM
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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Altair Engineering
Actran
Supported Cards
Solver Description
Supported Parameters
Notes
Supported Cards
Solver Description
Supported Parameters
Notes
N
Defines a node
NODE, X, Y, Z, THXY, THYZ, THZX
N
Defines a node
R5.1, Type, NODE, SOLID, VAL1, VAL2, VAL3
N
Defines a node
R5.3, LOC, NODE, SOLID, NODLOC, VAL1, VAL2, VAL3
NBLOCK
Nodal block
ID, SOLIDFLG, LINELOC, X, Y, Z
Supported Cards
Solver Description
Supported Parameters
*NODE
Define a node and it's coordinates in the global coordinate system.
NODE
ANSYS
LS-DYNA
Notes
Card can be previewed, but not edited
*NODE_RIGID_SURF Define a rigid node and it's ACE coordinates in the global coordinate system.
Card can be previewed, but not edited
MADYMO
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
704
Supported Cards
Solver Description
Supported Parameters
Notes
COORDINATE. CARTESIAN
Nodal coordinate definition in a Cartesian coordinate system
X, Y, Z coordinates
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.
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
NAME can be entered on the card image.
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.
POINT_OBJECT_1_F E
Defines a point associated with, and located relative to, a body or the reference space.
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
Defined through the parent element.
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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Altair Engineering
Supported Cards
Solver Description
Supported Parameters
Notes
relative to, a body or the reference space.
Nastran
Supported Cards
Solver Description
Supported Parameters
Notes
GRID
Defines the location of a geometric grid point, the directions of its displacement, and its permanent single-point constraints.
PS
Permanent single point constraint field supported for feinput only. On export, equivalent SPC cards are output.
Defines scalar points.
n/a
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.
Supported Cards
Solver Description
Supported Parameters
Notes
CNODE /
Common node definition
NODE /
Node definition
SPOINT
SPOINT CD-1 GRID_COMMENT
PAM-CRASH 2G
Altair Engineering
In the card previewer, the toggle button Common_Node allows you to change between NODE and CNODE.
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
706
Supported Cards
Note:
Solver Description
Supported Parameters
Notes
Use the find_cnodes summary template to highlight all CNODE nodes as temporary nodes.
PERMAS
Supported Cards
Solver Description
$COOR
Definition of nodal points and their coordinates
Supported Parameters
Notes
Samcef
The following cards are supported in the HyperMesh Samcef interface: Supported Cards
Solver Description
Supported Parameters
.NOE
Allows the entry of the coordinates of the nodes of the structure.
NODEID, X, Y, Z
Notes
See also Browsers HyperMesh Entities & Solver Interfaces Geometry Meshing Model Setup
707
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
710
See also Browsers HyperMesh Entities & Solver Interfaces Model Setup
711
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
712
Solver Card Support for Assemblies RADIOSS (Block Format)
Supported Cards
Solver Description
Supported Parameters
/SUBSET
Describes the subsets.
n/a
HyperMesh Notes
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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
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
CONTROL_AIRBAG
Parameters to control airbag model behaviour.
THERMC, BLOCK_FLOW, AMBIENT_PRES, AMBIENT_TEMP, AMBIENT_DAMP_CO EF
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.
HyperMesh Notes
Defined on the card of the parent FE_MODEL.
Defined on the MADYMO card.
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.
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
CONTROL_FE_MOD EL
Defines Rayleigh damping and mass lumping method for the parent FE 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
Comps and multibodies should be left empty.
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.
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
716
MARC
Supported Cards
Solver Description
ASSEMBLIES
Supported Parameters
HyperMesh Notes
n/a
PAM-CRASH 2G
Supported Cards
Solver Description
Supported Parameters
MBSYS /
Describes an assembly of multibodies
TITLE
HyperMesh Notes
H_POINT
See also Browsers HyperMesh Entities & Solver Interfaces Include Files Components
717
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
718
Solver Card Support for Components RADIOSS (Block Format)
719
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
/PART
Defines a part.
Prop_ID, Mat_ID, Subset_ID, Thick
Notes
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.
FIELD_POINT_SURF ACE FINITE_FLUID
Name, ID
Corresponds to the finite elements used to model acoustic media.
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.
INFINITE_FLUID
Corresponds to the infinite elements used to model acoustic free field.
INFINITE_MESH
Altair Engineering
Name, ID
Name, ID, POWER EVALUATION
Name, ID
Order ORIGIN, VECTOR
The INFINITE MESH data block is made of two subsections INFINITE_DOMAIN and
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
720
Supported Cards
Solver Description
Supported Parameters
Notes
INFINITE_ELEMENT MODAL_BASIS
Defines the modal content of the sound field in a modal component
MODAL_SURFACE
Defines the coupling surface between modal components and the acoustic finite element model
POROUS_UP
Corresponds to finite elements used to model poro-elastic media.
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.
HEADING, ELFORM, SHRF, NLOC, MAREA, HGID, ADPOPT, MID, THICK, B
Allows part based contact parameters to be use with the automatic contact types a3, 4,
HEADING, ELFORM, SHRF, NLOC, MAREA, HGID,
ContactOption Number_of_Plies
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Altair Engineering
Supported Cards
Solver Description
Supported Parameters
a5, a10, 13, 15 and 26.
ADPOPT, FS, FD, DC, VC, OPTT, SFT, SSF
Notes
Number_of_Plies *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, 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.
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)
*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.
This is the root element for defining belt models.
POINT_OBJECT_1. REF
BELT_FUSE
Fuse belts can model the tearing of seat belt stitches, which is used as a load limiting device.
Defined on the card of parent BELT_SEGMENT
BELT_RETRACTOR
Retractor with webbing grabber.
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.
Reference to parent BELT.
Altair Engineering
Notes
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
726
Supported Cards
Solver Description
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.
CONSTRAINT. RIGID_FE
Rigid elements and rigid parts that form one rigid FE entity.
Supported Parameters
Notes
Reference to parent BELT.
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.
CONTROL_SYSTEM
Control module for multi-body systems.
ID, NAME
PART
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, PROPERTY, MATERIAL
Supported Cards
Solver Description
Supported Parameters
PART /
Part_3D
SOLID, BSHEL, TETRA
PART /
Part_2D
TSHEL, SHELL, MEMBR
Type the number of CONTACTs in the CONTACT_LIST and select the desired CONTACT.MB_MBs .
PAM-CRASH 2G
727
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Notes
Altair Engineering
Supported Cards
Solver Description
Supported Parameters
PART /
Part_1D
BAR, BEAM, SPRING, JOINT, KJOIN, MBSPR, MBKJN, SPRGBM
PART /
PART_LINK
TIED, SLINK, ELINK, PLINK, LLINK
Supported Cards
Solver Description
Supported Parameters
$ELPROP
Assignment of geometrical data Mass/Springs and material to elements
Notes
PERMAS
Notes
See also Browsers HyperMesh Entities & Solver Interfaces Include Files Assemblies
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of 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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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.
See also Geometry Terminology CAD Interfacing Geometry Functionality Include Files Assemblies Components
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of 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.
See also Geometry Terminology CAD Interfacing Geometry Functionality Include Files Assemblies Components
731
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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.
See also Geometry Terminology CAD Interfacing Geometry Functionality Include Files Assemblies Components
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of 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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Solver Card Support for Elements RADIOSS (Block Format)
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
/ADMAS
Describes the added masses.
Mass
/BEAM
Describes the beam elements.
Bar
/BRIC20
Describes 3D solid elements.
Hex20
/BRICK
Defines a Hexahedral Solid Element and Thick Shell Element with 8 nodes.
Hex8, Penta6, Pyramid5, Tetra4
/CYL_JOINT
Describes the cylindrical joints.
Rigid
/QUAD
Describes the 2D solid elements.
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
Notes
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
734
Supported Cards
Solver Description
Supported Elem Types
/RBE3
Ties degree of freedom of one node to multiple nodes.
RBE3
/RBODY
Describes the rigid bodies.
Rigid
/RIVET
Describes the rivet or spotweld.
Weld
/RLINK
Describes the rigid links.
Rigid
/SHELL
Describes the 4 node shell elements.
Quad4
/SH3N
Describes the 3 node shell elements
Tria3
/SPHCEL
Describes the SPH cells.
Mass
/SPRING
Describes the spring elements.
Spring
/TETRA4
Describes the 4-noded tetra elements
Tetra4
/TETRA10
Describes the 10-noded tetra elements
Tetra10
/TRUSS
Describes the truss elements.
Rod
Notes
RADIOSS (Bulk Data Format), OptiStruct
Most RADIOSS (Bulk Data Format), OptiStruct structural elements used in finite element analysis solution sequences are supported as elements in the interface.
735
Supported Cards
Solver Description
Supported Elem Types
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.
Tria3
Notes
Quad4
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Altair Engineering
Supported Cards
Solver Description
Supported Elem Types
CAABSF
Defines a frequency-dependent Mass acoustic absorber element in coupled fluid-structural analysis. Rod
Notes
Tria3 Quad4 CBAR
Defines a simple beam element.
CBEAM
Defines a beam element Bar2 (BEAM) of the structural model.
CBUSH
Defines a generalized springdamper structural element.
Spring
CBUSH1D
Defines a one-dimensional spring-damper structural element.
Mass
Defines a scalar damper element.
Spring
Defines a scalar damper element, without reference to a property.
Spring
Defines a scalar damper element that is connected only to scalar points.
Spring
Defines a scalar damper element that is connected only to scalar points and is without reference to a material or property entry.
Spring
CDAMP1
CDAMP2
CDAMP3
CDAMP4
Altair Engineering
Bar2
Spring Represented as a spring element type or as a mass element type (grounded CDAMP1).
Mass
Represented as a spring element type or as a mass element type (grounded CDAMP2).
Mass
Represented as a spring element type or as a mass element type (when a coordinate is constrained).
Mass
Represented as a spring element type or as a mass element type (when a coordinate is constrained).
Mass
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
736
Supported Cards
Solver Description
Supported Elem Types
Notes
CELAS1
Defines a scalar spring element of the structural model.
Spring
Represented as a spring element type or as a mass element type (grounded CELAS1).
Defines a scalar spring element of the structural model without reference to a property entry.
Spring
CELAS2
Mass
Mass
Represented as a spring element type or as a mass element type (grounded CELAS2). Exported in large field format by optistructlf template.
CELAS3
737
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).
CELAS4
Defines a scalar spring element Spring that is connected only to scalar Mass points without reference to a property entry.
Represented as a spring element type or as a mass element type (when a coordinate is constrained).
CGAP
Defines a gap or friction element.
Gap
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.
CGAPG
Defines a node-to-obstacle gap element. The obstacle may be an element face or a patch of nodes.
Gap
The type of gap elements (either CGAP or CGAPG) is automatically determined based on whether the element
Mass
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Altair Engineering
Supported Cards
Solver Description
Supported Elem Types
Notes
is node-to-node or node-to-elem. CHACAB
Defines the acoustic absorber element in coupled fluidstructural analysis
Hex8
CHBDYE
Defines a surface element for application of thermal boundary condition.
Slave1
CHEXA (8-noded)
Defines a first order solid element, composed of 6 quadrilateral faces.
Hex8
CHEXA (20-noded)
Defines a second order solid element, composed of 6 quadrilateral faces.
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.
CMASS1
Defines a scalar mass element. Spring
Represented as a spring element type or as a mass element type (grounded CMASS1).
Defined using the Interfaces panel with the CONDUCTION or CONVECTION type.
Mass
CMASS2
CMASS3
Altair Engineering
Defines a scalar mass element without reference to a property entry.
Spring Mass
Represented as a spring element type or as a mass element type (grounded CMASS2).
Defines a scalar mass element
Spring
Represented as a
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
738
Supported Cards
739
Solver Description
Supported Elem Types
Notes
that is connected only to scalar Mass points.
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.
Represented as a spring element type or as a mass element type (when a coordinate is constrained).
CMBEAM
Defines a beam element for Bar2 multi-body dynamics solution sequence without reference to a property entry.
CMSPDP
Defines a spring damper element without reference to a property entry for multi-body solution sequence.
Spring
CONM1
Defines a 6x6 mass matrix at a geometric grid point.
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.
Rod
CONV
Specifies a free convection boundary condition for heat transfer analysis.
Slave1
CPENTA (6-noded)
Defines a first order solid element, composed of 3 quadrilateral and 2 triangular faces.
Penta6
CPENTA (15-noded)
Defines a second order solid
Penta15
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Exported in large field format by optistructlf template.
Represented as a continuation to CHBDYE slave element card.
A second order
Altair Engineering
Supported Cards
Solver Description
Supported Elem Types
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.
CPYRA (5-noded)
Defines a first order solid element, composed of 1 quadrilateral and 4 triangular faces.
Pyramid5
CPYRA (13-noded)
Defines a second order solid element, composed of 1 quadrilateral and 4 triangular faces.
Pyramid13
CQUAD4
Defines a quadrilateral plate element (QUAD4) of the structural model.
Quad4
CQUAD8
Defines a curved quadrilateral shell element with eight grid points.
Quad8
Altair Engineering
Notes
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.
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
740
741
Supported Cards
Solver Description
Supported Elem Types
CROD
Defines a tension-compression element (ROD) of the structural model.
Rod
CSHEAR
Defines a shear panel element.
Quad4
CTETRA (4-noded)
Defines a first order solid element, composed of 4 triangular faces.
Tetra4
CTETRA (10-noded)
Defines a second order solid element, composed of 4 triangular faces.
Tetra10
CTRIA3
Defines a triangular plate element (TRIA3) of the structural model.
Tria3
CTRIA6
Defines a second order triangular element.
Tria6
CTUBE
Defines a tension-compression- Rod torsion element (TUBE) of the structural model.
CVISC
Defines a viscous damper element.
CWELD
Defines a weld or fastener Mass connecting two surface patches Rod or points.
Spring
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Notes
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.
Represented as a spring element type. Represented as a rod element type.
Altair Engineering
Supported Cards
Solver Description
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.
JOINT
Defines a joint used in multibody dynamics.
Joint
PLOTEL
Defines a one-dimensional dummy element for use in plotting.
Plot
PLOTEL3
Defines a three-noded, twoTria dimensional dummy element for Quad4 use in plotting.
PLOTEL4
Defines a four-noded, twoTria dimensional dummy element for Quad4 use in plotting.
QBDY1
Defines a uniform heat flux for CHBDYE elements.
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.
RBE3
Defines the motion at a Rbe3 "reference" grid point as the weighted average of the motions at a set of other grid points.
RROD
Defines a pin-ended rod that is
Altair Engineering
Supported Elem Types
Notes
Flux
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.
Rod
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
742
Supported Cards
Solver Description
Supported Elem Types
Notes
rigid in extension.
RADIOSS (Fixed Format)
Abaqus
Standard.2d Template
Supported Cards
Solver Description
Supported Elem Types
Supported Parameters
*COUPLING
Define a surface-based coupling constraint where the *SURFACE card points to nodes.
Rigid
COUP_KIN
*ELEMENT
743
*COUPLING with element-based *SURFACE cards are defined as groups
Release rotational degrees of Bar2/Bar3 freedom at one or both ends of a beam element
See Note**
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:
751
HyperMesh dof Code
Abaqus Release Combination Code
4
T
5
M2
45
M2-T
6
M1
46
M1-T
56
M1-M2
456
ALLM
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Altair Engineering
Note:
For 2-D problems, only dof6 (M1) is active.
Actran
The following Actran element types are supported: Supported Cards
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Altair Engineering
Supported Cards
Solver Description
Supported Elem Types
Notes
Quad8 PRETS179
Define a 2-D or 3-D pretension section within a meshed structure
Bar2
RBE3
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.
Rbe3
SHELL28
Shear/Twist Panel
Quad4
Config 104, Type 12
SHELL41
Membrane Shell
Tria3
Config 103, Type 19
Quad4
Config 104, Type 19
4-Node Plastic Large Strain Shell
Tria3
Config 103, Type 2
Quad4
Config 104, Type 2
SHELL51
Axisymmetric Structural Shell
Bar2
Config 60, Type 14
SHELL57
Thermal Shell
Tria3
Config 103, Type 7
Quad4
Config 104, Type 7
SHELL43
Config 60, Type 17
SHELL61
Axisymmetric-Harmonic Structural Shell
Bar2
Config 60, Type 15
SHELL63
Elastic Shell
Tria3
Config 103, Type 1
Quad4
Config 104, Type 1
Nonlinear Layered Structural Shell
Tria6
Config 106, Type 6
Quad8
Config 108, Type 6
8-Node Structural Shell
Tria6
Config 106, Type 4
Quad8
Config 108, Type 4
Tria6
Config 106, Type 5
SHELL91
SHELL93
SHELL99
Altair Engineering
Linear Layered Structural Shell
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
758
Supported Cards
SHELL131
SHELL132
SHELL143
SHELL150
SHELL157
SHELL163
SHELL181
Solver Description
Supported Elem Types
Notes
Quad8
Config 108, Type 5
Tria3
Config 103, Type 25
Quad4
Config 104, Type 25
Tria6
Config 106, Type 24
Quad8
Config 108, Type 24
4-Node Plastic Small Strain Shell
Tria3
Config 103, Type 10
Quad4
Config 104, Type 10
8-Node Structural Shell pElement
Tria6
Config 106, Type 20
Quad8
Config 108, Type 20
Thermal-Electric Shell
Tria3
Config 103, Type 20
Quad4
Config 104, Type 20
Tria3
Config 103, Type 17
Quad4
Config 104, Type 17
Tria3
Config 103, Type 11
Quad4
Config 104, Type 11
4-Node Layered Thermal Shell
8-Node Layered Thermal Shell
Explicit Thin Structural Shell
4-Node Finite Strain Shell
SHELL208
2-Node Finite Strain Axisymmetric Shell
Bar2
SHELL209
3-Node Finite Strain Axisymmetric Shell
Bar2
SHELL281
8-Node Finite Strain Shell
Tria6 Quad8
SOLID5
SOLID45
759
3-D Coupled-Field Solid
3-D Structural Solid
Penta6
Config 206, Type 2
Hex8
Config 208, Type 2
Tetra4
Config 204, Type 1
Penta6
Config 206, Type 1
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Altair Engineering
Supported Cards
SOLID46
SOLID62
SOLID64
SOLID69
SOLID70
Solver Description
3-D 8-Node Layered Structural Solid
3-D Magneto-Structural Solid
Supported Elem Types
Notes
Hex8
Config 208, Type 1
Tetra4
Config 204, Type 6
Penta6
Config 206, Type 6
Hex8
Config 208, Type 6
Tetra4
Config 204, Type 15
Pyramid5
Config 205, Type 15
Penta6
Config 206, Type 15
Hex8
Config 208, Type 15
3-D Anisotropic Structural Solid Tetra4
3-D Coupled Thermal-Electric Solid
3-D Thermal Solid
Config 204, Type 7
Penta6
Config 206, Type 7
Hex8
Config 208, Type 7
Tetra4
Config 204, Type 4
Penta6
Config 206, Type 4
Hex8
Config 208, Type 4
Tetra4
Config 204, Type 3
Penta6
Config 206, Type 3
Hex8
Config 208, Type 3
SOLID72
Tetra4
SOLID73
Tetra4 Penta6 Hex8
SOLID87
3-D 10-Node Tetrahedral Thermal Solid
Tetra10
Config 210, Type 5
SOLID90
3-D 20-Node Thermal Solid
Tetra10
Config 210, Type 2
Pyramid13
Config 213, Type 2
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
760
Supported Cards
Solver Description
Supported Elem Types
Notes
Penta15 Hex20 SOLID92
3-D 10-Node Tetrahedral Structural Solid
Tetra10
Config 210, Type 3
SOLID95
3-D 20-Node Structural Solid
Tetra10
Config 210, Type 1
Pyramid13
Config 213, Type 1
Penta15
Config 215, Type 1
Hex20
Config 220, Type 1
Tetra4
Config 204, Type 5
Pyramid5
Config 205, Type 5
Penta6
Config 206, Type 5
Hex8
Config 208, Type 5
Tetra4
Config 204, Type 8
Pyramid5
Config 205, Type 8
Penta6
Config 206, Type 8
Hex8
Config 208, Type 8
SOLID96
SOLID97
3-D Magnetic Solid
SOLID98
Tetrahedral Coupled-Field Solid
Tetra10
Config 210, Type 4
SOLID117
3-D 20-Node Magnetic Solid
Tetra10
Config 210, Type 8
Pyramid13
Config 213, Type 8
Penta15
Config 215, Type 8
Hex20
Config 220, Type 8
SOLID147
SOLID148
761
3-D Magnetic Scalar Solid
3-D Brick Structural Solid pElement
Penta15
3-D Tetrahedral Structural Solid p-Element
Penta15
Config 215, Type 9
Tetra10
Config 210, Type 9
Hex20
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Altair Engineering
Supported Cards
SOLID164
Solver Description
Explicit 3-D Structural Solid
Supported Elem Types
Notes
Hex20
Config 220, Type 9
Tetra4
Config 204, Type 14
Pyramid5
Config 205, Type 14
Penta6
Config 206, Type 14
Hex8
Config 208, Type 14
SOLID168
Explicit 3-D 10-Node Tetrahedral Structural Solid
Tetra10
SOLID185
3-D 8-Node Structural Solid
Tetra4
Config 204, Type 13
Penta6
Config 206, Type 13
Hex8
Config 208, Type 13
Tetra10
Config 210, Type 7
Pyramid13
Config 213, Type 7
Penta15
Config 215, Type 7
Hex20
Config 220, Type 7
SOLID186
3-D 20-Node Structural Solid
SOLID187
3-D 10-Node Tetrahedral Structural Solid
Tetra10
Config 210, Type 6
SOLID191
3-D 20-Node Layered Structural Solid
Tetra10
Config 210, Type 10
Penta15
Config 215, Type 10
Hex20
Config 220, Type 10
SOLID226
3-D 20-Node Coupled-Field Solid
Tetra10 Pyramid13 Penta15 Hex20
SOLID227
Altair Engineering
3-D 10-Node Coupled-Field Solid
Tetra10
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
762
Supported Cards
Solver Description
Supported Elem Types
Notes
SOLSH190
3-D 8-Node Layered Solid Shell
Penta6
Config 206
Hex8
Config 208, Type 17
SURF151
2-D Thermal Surface Effect
Bar2
Config 60, Type 12
SURF152
3-D Thermal Surface Effect
Quad4
Config 104, Type 14
Quad8
Config 108, Type 14
Tria6 SURF153
SURF154
2-D Structural Surface Effect
3-D Structural Surface Effect
Bar2
Config 60, Type 16
Bar3
Config 63, Type 16
Quad4
Config 104, Type 18
Quad8
Config 108, Type 18
Tria6 SURF156
3-D Structural Surface Line Load Effect
Bar3
TARGE169
2-D Target Segment
Mass
Config 1, Type 13
Bar2
Config 60, Type 9
Bar3
Config 63, Type 16
Mass
Config 103, Type 16
TARGE170
3-D Target Segment
Tria3
VISCO88
2-D 8-Node Viscoelastic Solid
Quad4
Config 104, Type 16
Tria6
Config 106, Type 16
Quad8
Config 108, Type 16
Tria6 Quad8
VISCO107
763
3-D 8-Node Viscoplastic Solid
Tetra4
Config 204, Type 16
Penta6
Config 206, Type 16
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Altair Engineering
Supported Cards
Solver Description
Supported Elem Types
Notes
Hex8
Config 208, Type 16
LS-DYNA
Supported Cards
Solver Description
*CONSTRAINED_ Define the butt type of weld. GENERALIZED_WEL D_ BUTT_(ID)
Supported Elem Types
Notes
Rigid
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)
Rigid
*CONSTRAINED_ Define the spot type of weld. GENERALIZED_WEL D_ SPOT_(ID)
Rigid
*CONSTRAINED_ INTERPOLATION
Define an interpolation constrain.
RBE3
*CONSTRAINED_JOI NT_
Define a joint between two rigid bodies.
Joint
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
*CONSTRAINED_NO Used when inertial properties DAL_ are defined rather than RIGID_BODY_INERTI computed. A
Rigid
*CONSTRAINED_NO DAL_ RIGID_BODY_INERTI A (2Noded)
Rigid
*CONSTRAINED_NO DAL_ RIGID_BODY_INERTI A _SPC
Rigid
*CONSTRAINED_NO DAL_ RIGID_BODY_INERTI A _SPC (2-Noded)
Rigid
*CONSTRAINED_NO DAL_ RIGID_BODY_SPC
Rigid
*CONSTRAINED_NO DAL_ RIGID_BODY_SPC (2Noded)
Rigid
*CONSTRAINED_NO
Altair Engineering
Define nodal constraint sets for
Rigid
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
768
Supported Cards
Solver Description
DE_ SET
translational motion in global coordinates.
Supported Elem Types
*CONSTRAINED_NO DE_ SET (2-Noded)
Rigid
*CONSTRAINED_NO DE_ SET_ID
Rigid
Notes
*CONSTRAINED_RIV Define massless rivets between Weld ET non-contiguous nodal pairs. *CONSTRAINED_SH ELL_ TO_SOLID
Define a tie between a shell edge and solid elements.
Rigid
*CONSTRAINED_ SPOTWELD_ID
Define massless spot welds between non-contiguous nodal pairs.
Weld
*CONSTRAINED_ SPOTWELD_FILTER ED_ FORCE_ID
*ELEMENT_BEAM
769
Normal and shear failure values can be edited.
Weld
Define two node elements including 3D beams, trusses, 2D axisymmetric shells and 2D plane strain beam elements.
Bar
*ELEMENT_BEAM_ OFFSET
Bar
*ELEMENT_BEAM_ OFFSET_PID
Bar
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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.
Altair Engineering
*ELEMENT_BEAM
Define two node elements including 3D beams, trusses, 2D axisymmetric shells and 2D plane strain beam elements.
Bar
*ELEMENT_BEAM_ OFFSET_THICKNES S
Bar
*ELEMENT_BEAM_ ORIENTATION
Bar
*ELEMENT_BEAM_P ID
Bar
*ELEMENT_BEAM_P ID_ ORIENTATION
Bar
*ELEMENT_BEAM_P ID_ SCALAR
Bar
*ELEMENT_BEAM_ SCALAR
Bar
*ELEMENT_BEAM_ SCALAR_ORIENTATI ON
Bar
*ELEMENT_BEAM_ SECTION
Bar
*ELEMENT_BEAM_ SECTION_ORIENTAT ION
Bar
*ELEMENT_BEAM_ SECTION_PID
Bar
*ELEMENT_BEAM_ THICKNESS
Bar
Altair Engineering
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.
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
770
*ELEMENT_BEAM
Define two node elements including 3D beams, trusses, 2D axisymmetric shells and 2D plane strain beam elements.
*ELEMENT_BEAM_ THICKNESS_ORIENT ATION
Bar
*ELEMENT_BEAM_ THICKNESS_PID
Bar
*ELEMENT_BEAM_ THICKNESS_SCALA R
Bar
*ELEMENT_DISCRET Define a discrete (spring or E damper) element between two nodes or a node and ground.
Spring
*ELEMENT_INERTIA
Mass
Define a lumped inertia element assigned to a nodal point.
*ELEMENT_INERTIA _ OFFSET
771
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.
Scale factor, printing flags, and offset values can be edited.
Mass
*ELEMENT_MASS
Define a lumped mass element assigned to a nodal point or equally distributed to the nodes of a node set.
Mass
*ELEMENT_MASS_ NODE_SET
Mass elements defined on node Mass set
*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.
Mass
*ELEMENT_MASS_ PART_SET
Mass
Mass elements defined on part set.
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Altair Engineering
*ELEMENT_BEAM
Define two node elements including 3D beams, trusses, 2D axisymmetric shells and 2D plane strain beam elements.
Bar
*ELEMENT_PLOTEL
Define a null beam element for visualization.
Plot
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_SEATBE Define a seat belt element. LT
Rod
*ELEMENT_SEATBE Define a seat belt LT_ accelerometer. ACCELEROMETER
Tria3
*ELEMENT_SEATBE Define seat belt pretensioner. LT_ PRETENSIONER
Mass
*ELEMENT_SEATBE Define seat belt retractor. LT_ RETRACTOR
Mass
*ELEMENT_SEATBE Define seat belt sensor. LT_ SENSOR
Sensors
*ELEMENT_SEATBE Define seat belt slip ring. LT_ SLIPRING
Mass
*ELEMENT_SHELL
Tria3, Quad4
*ELEMENT_SHELL_ BETA
Altair Engineering
Define three, four, six and eight node elements including 3D shells, membranes, 2D plane stress, plane strain, and axisymmetric solids.
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.
Tria3, Quad4
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
772
*ELEMENT_BEAM
773
Define two node elements including 3D beams, trusses, 2D axisymmetric shells and 2D plane strain beam elements.
Bar
*ELEMENT_SHELL_ BETA_ OFFSET
Tria3, Quad4
*ELEMENT_SHELL_ DOF
Tria3, Quad4
*ELEMENT_SHELL_ MCID
Tria3, Quad4
*ELEMENT_SHELL_ MCID_ OFFSET
Tria3, Quad4
*ELEMENT_SHELL_ OFFSET
Tria3, Quad4
*ELEMENT_SHELL_ THICKNESS
Tria3, Quad4
*ELEMENT_SHELL_ THICKNESS_BETA
Tria3, Quad4
*ELEMENT_SHELL_ THICKNESS_BETA_ OFFSET
Tria3, Quad4
*ELEMENT_SHELL_ THICKNESS_MCID
Tria3, Quad4
*ELEMENT_SHELL_ THICKNESS_MCID_ OFFSET
Tria3, Quad4
*ELEMENT_SHELL_ THICKNESS_OFFSE T
Tria3, Quad4
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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.
Altair Engineering
*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_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
Define a lumped mass element assigned to a nodal point
Mass
*ELEMENT_TSHELL
Define an eight node thick shell element which is available with either fully reduced or selectively reduced integration rules.
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.
This is supported as an attribute to an element to maintain its associativity with element inside HM
*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
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of 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.
This is supported as an attribute to an element to maintain its associativity with element inside HM
previous analysis/step carried forward to next analysis/step.
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.
This is supported as an attribute to an element to maintain its associativity with element inside HM
*INITIAL_STRESS_S HELL
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.
This is supported as an attribute to an element to maintain its associativity with element inside HM
*INITIAL_STRESS_S OLID
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.
This is supported as an attribute to an element to maintain its associativity with element inside HM
Supported Cards
Solver Description
Supported Elem Types
Notes
COMP_SIX_DOF
Component for six degree of freedom restraint (for internal use only).
Rod
Defined on the card of the parent RESTRAINT.
CONNECT_N2
Spotweld connection between 2 Rigid nodes.
Defined when creating the parent SPOTWELD.
CONNECT_N3
Spotweld connection between 3 Rigid nodes.
Defined when creating the parent SPOTWELD.
MADYMO
775
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
nodes = N1 mass = MASS property and system are not used ASSEMBLY = reference to the parent FE_MODEL
MODE
Flexible body deformation mode Rigid shape
MODE_SHAPE
Nodal displacements define a deformable body 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.
Rigid
Defined on the card of the parent MODE.
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
Altair Engineering
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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
776
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
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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Altair Engineering
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 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
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
778
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 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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Altair Engineering
Three node spotweld.
Rigid
Select an independent node + 2 dependent nodes (these are used in NODE_3 of the
Altair HyperMesh User's Guide Proprietary Inform ation of 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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Altair Engineering
Massless linear tension-only spring between two nodes.
Spring
Choose no vector and select: first node = N1 second node = N2
Altair HyperMesh User's Guide Proprietary Inform ation of 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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Notes
Altair Engineering
Supported Cards
Solver Description
Supported Elem Types
E_128
Incompressible, six-node triangle.
Tria6
E_129
Incompressible, six-node triangle.
Tria6
E_130
Incompressible, ten-node tetrahedron.
Tetra10
E_134
Four-node, tetrahedral.
Tetra4
E_138
Three node, thin shell.
Tria3
E_139
Four-node, thin shell.
Quad4
E_140
Four-node, thick shell, reduced integration with hourglass control.
Quad4
E_149
Notes
Hex8
E_157
4+1-node, three dimensional, Tetra4 low order, tetrahedron, Hermann formulations.
E-195
Spring Mass
MASSES
Mass
RBE2
Rigid
RBE3
RBE3
SPRING
Spring
TYING
Rigid
tying100
Rigid
Nastran
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
796
Supported Cards
Solver Description
Supported Elem Types
CAABSF
Defines a frequency-dependent Mass acoustic absorber element in coupled fluid-structural analysis. Rod
Notes
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.
CAERO2
Defines aerodynamic slender body and interference elements for Doublet-Lattice aerodynamics.
CBAR
Defines a simple beam element. Bar
CBEAM
Defines a beam element.
Bar
CBEND
Defines a curved beam, curved pipe, or elbow element.
Bar
CBUSH
Defines a generalized springand-damper structural element that may be nonlinear or frequency dependent.
Mass
Defines the connectivity of a one-dimensional spring and viscous damper element.
Mass
Defines a scalar damper element.
Mass
Defines a scalar damper element without reference to a
Mass
CBUSH1D
CDAMP1
CDAMP2
797
Rod
Spring
Spring
Spring
Spring
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Both elements with grounded terminals are supported
Both elements with grounded terminals are supported Elements CDAMP1 and CDAMP2 with grounded terminals are not supported. Elements CDAMP1 and CDAMP2 with
Altair Engineering
Supported Cards
Solver Description
Supported Elem Types
material or property entry.
CDAMP3
CDAMP4
CELAS1
grounded terminals are not supported.
Defines a scalar damper element that is connected only to scalar points.
Mass
Defines a scalar damper element that connected only to scalar points and without reference to a material or property entry.
Mass
Elements CDAMP1 and CDAMP2 with grounded terminals are not supported.
Spring
Elements CDAMP1 and CDAMP2 with grounded terminals are not supported.
Spring
Defines a scalar spring element. Mass
Elements CDAMP1 and CDAMP2 with grounded terminals are not supported.
Spring
CELAS2
CELAS3
Notes
Defines a scalar spring element without reference to a property entry.
Mass
Defines a scalar spring element that connects only to scalar points.
Mass
Elements CDAMP1 and CDAMP2 with grounded terminals are not supported.
Spring
Spring
Elements CDAMP1 and CDAMP2 with grounded terminals are not supported.
CELAS4
Defines a scalar spring element Mass that is connected only to scalar Spring points, without reference to a property entry.
Elements CDAMP1 and CDAMP2 with grounded terminals are not supported
CFAST
Defines a fastener with material orientation connecting two surface patches.
Mass
CGAP
Defines a gap or friction element.
Gap
CHACAB
Defines the acoustic absorber element in coupled fluidstructural analysis.
Hex8
Altair Engineering
Rod
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
798
Supported Cards
Solver Description
Supported Elem Types
CHBDYE
Defines a boundary condition surface element with reference to a heat conduction element.
CHEXA (20-noded)
Defines a second order solid element, composed of 6 quadrilateral faces.
Hex20
CHEXA (8-noded)
Defines a first order solid element, composed of 6 quadrilateral faces.
Hex8
CMASS1
Defines a scalar mass element. Mass
Notes
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.
Spring CMASS2
799
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.
CMASS4
Defines a scalar mass element Mass that is connected only to scalar Spring points, without reference to a property entry.
CONM1
Defines a 6 x 6 symmetric Mass mass matrix at a geometric grid point.
CONM2
Defines a concentrated mass at Mass
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Altair Engineering
Supported Cards
Solver Description
Supported Elem Types
Notes
a grid point. CONROD
Defines a rod element without reference to a property entry.
Rod
CPENTA (6-noded)
Defines the connections of a five-sided solid element with six to fifteen grid points.
Penta6
CPENTA (15-noded)
Defines the connections of a five-sided solid element with six to fifteen grid points.
Penta15
CQUAD4
Defines an isoparametric membrane-bending or plane strain quadrilateral plate element.
Quad4
CQUAD8
Defines a curved quadrilateral shell or plane strain element with eight grid points.
Quad8
CQUADR
Defines an isoparametric
Quad4
Altair Engineering
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.
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.
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
800
Supported Cards
Solver Description
Supported Elem Types
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 Poisson’s ratio than the CQUAD4 element. It is a companion to the CTRIAR element. CROD
Defines a tension-compression- Rod torsion element.
CSHEAR
Defines a shear panel element.
CSEAM
801
Quad4 Rod
CTETRA (4-noded)
Defines the connections of the four-sided solid element with four grid points.
Tetra4
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.
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 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.
Tria3
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
In Nastran, you can define a second order element with missing
Altair Engineering
Supported Cards
Solver Description
Supported Elem Types
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.
CTUBE
Defines a tension-compression- Rod torsion tube element.
CVISC
Defines a viscous damper element.
CWELD
Defines a weld or fastener Mass connecting two surface patches Rod or points.
Altair Engineering
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
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
802
Supported Cards
Solver Description
Supported Elem Types
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.
803
GENEL
Defines a general element.
RBE3
HM_SPRING
Defines a spring element, which Spring is converted to Nastran entities on export, in a manner similar to that explained in Using HM_ELAS.
MBOLT
Defines a bolt for use in SOL 600 in countries outside the USA.
Mass
MBOLTUS
Defines a bolt for use only in SOL 600 and only in the USA.
Mass
PLOTEL
Defines a one-dimensional dummy element for use in plotting.
Plot
RBAR
Defines a rigid bar with six Weld degrees-of-freedom at each end.
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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.
Altair Engineering
Supported Cards
Solver Description
Supported Elem Types
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.
RBE3
Defines the motion at a RBE3 reference grid point as the weighted average of the motions at a set of other grid points.
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.
RJOINT
Defines a rigid joint element connecting two coinciding grid points.
RBE2
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
ASSOCIATE
Defines entities to be converted from deformable to rigid.
Rigids
Altair Engineering
Notes
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
804
BAR /
Bar element.
Rod
BASE_BODY
Rigid bodies on which the boundary conditions are defined, used in Multibody systems.
Rigid
BEAM /
Beam element.
Bar2
BSHEL /
8-noded brick shell element.
Hex8
EDG
805
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.
Rod
ELINK /
Link element.
Rod
The element must be edited in the card previewer to define the connections.
JOINT /
Joint element.
Rod
The element must be edited in the card previewer to define element orientation.
KJOIN /
Kinematic joint element.
Rod
The element must be edited in the card previewer to define element orientation.
LLINK /
Link element.
Rod
The element must be edited in the card previewer to define the connections.
MASS
Added mass.
Mass
MEMBR /
Membrane element.
Tria3
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Altair Engineering
MEMBR /
Quad4
MTOCO
Rigid element.
Rigid
NODCO /
Nodal constraint definition.
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.
PLINK /
Plink element.
Mass
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.
PLINK_VI
Rod
These elements are created during connector realization to show the actual connections. They are not exported.
RETRA /
Mass
The element must be edited in the card previewer. Mass value is ignored.
Weld
When created, the default value for rigid body type is 1.
Rigid
This configuration allows you to create rigid bodies via entity sets. The element
RBODY /
RBODY /
Altair Engineering
Rigid body with 2 nodes.
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
806
must be edited in the card previewer. Degrees of freedom are ignored. SEG
Tria3
SEG
Quad4
SENPT /
Mass
SHELL /
Shell element.
SHELL /
The elements are used in entity selection. With this keyword, only nodes of these elements are output along with SEG keyword.
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.
Tria3
The default behavior for tria3 elements is Coo triangles. To output standard triangles (N3 = N4).
807
SHELL /
Quad4
SLINK /
Tria3
SLINK /
Quad4
SLIPR /
Mass
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
The element must be edited in the card previewer to define the connections. The element must be edited in the card
Altair Engineering
previewer. Mass value is ignored. SOLID /
8-noded brick element.
Tetra4
SOLID /
Pyramid5
SOLID /
Penta6
SOLID /
Hex8
SPH /
Mass
SPRING /
Spring element.
Spring
The element must be edited in the card previewer to define element orientation.
SPRGBM /
Spring beam element.
Spring
The element must be edited in the card previewer to define element orientation.
TETRA /
10-noded tetra element.
Tetra10
Local frame definition
TETR4 /
4-noded tetra element.
Tetra4
TSHEL /
4-noded thick shell element.
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
BEAM2
2 noded straight general beam.
Bar2
BECOC
2 noded straight thin-walled tube.
Bar2
Altair Engineering
Notes
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
808
809
Supported Cards
Solver Description
Supported Elem Types
BECOS
2 noded straight solid beam.
Bar2
CONA3
3 noded triangular surface convection and radiation element.
Tria3
CONA4
4 noded quadrilateral surface convection and radiation element.
Quad4
CONA6
6 noded triangular surface convection and radiation element.
Tria6
CONA8
8 noded quadrilateral surface convection and radiation element.
Quad8
CONS3
3 noded triangular shell surface convection and radiation element.
Tria3
CONS4
4 noded quadrilateral shell Quad4 surface convection and radiation element.
CONS6
6 noded triangular shell surface convection and radiation element.
CONS8
8 noded quadrilateral shell Quad8 surface convection and radiation element.
DAMP1
Translational viscous damper.
Spring
DAMP3
Viscous damper for three degrees of freedom.
Spring
DAMP6
Viscous damper for six degrees Spring of freedom.
FLA2
2 noded straight flange (rod).
Notes
Tria6
Rod
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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.
See also Include Files Assemblies Components Elements
817
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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.
See also Include Files Assemblies Components Elements
819
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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.
See also Include Files Assemblies Components Elements
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of 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
Type Name
# nodes
Orientation
1
Spherical
2
none/systems/nodes
2
Revolute
4
none/systems
3
Cylindrical
4
none/systems
4
Planar
4
none/systems
5
Universal
4
none/systems
6
Translational
6
none/systems
7
Locking
6
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.
See also Include Files Assemblies Components Elements Connectors
821
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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.
See also Include Files Assemblies Components Elements Connectors
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of 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.
See also Include Files Assemblies Components Elements
823
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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.
See also Include Files Assemblies Components Elements
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of 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.
See also Include Files Assemblies Components Elements
825
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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.
See also Include Files Assemblies Components Elements
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of 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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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.
See also Include Files Assemblies Components Elements
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of 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.
See also Include Files Assemblies Components Elements
829
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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.
See also Include Files Assemblies Components Elements
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
830
831
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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.
See also Include Files Assemblies Components Elements
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of 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.
See also Include Files Assemblies Components Elements
833
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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.
See also Include Files Assemblies Components Elements
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of 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.
See also Include Files Assemblies Components Elements
835
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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.
See also Include Files Assemblies Components Elements
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of 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.
See also Include Files Assemblies Components Elements
837
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Altair Engineering
Slave3 Slave3 elements are slave interface elements with 3 node. (Must be Type 1) The following panels can be used to create and edit slave3 elements: Interfaces
The data names associated with slave3 elements can be found in the data names section of the HyperMesh Reference Guide.
See also Include Files Assemblies Components Elements
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
838
Slave4 Slave4 elements are slave interface elements with 1 node. (Must be Type 1) The following panels can be used to create and edit slave4 elements: Interfaces
The data names associated with slave4 elements can be found in the data names section of the HyperMesh Reference Guide.
See also Include Files Assemblies Components Elements
839
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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.
See also Include Files Assemblies Components Elements
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of 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.
See also Include Files Assemblies Components Elements
841
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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.
See also Include Files Assemblies Components Elements
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of 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.
See also Include Files Assemblies Components Elements
843
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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.
See also Include Files Assemblies Components Elements
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of 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.
See also Include Files Assemblies Components Elements
845
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Altair Engineering
Solver Card Support for Load Collectors RADIOSS (Block Format)
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
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
848
Supported Cards
Solver Description
/ACTIV
Describes the deactivation/ activation of element groups.
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Altair Engineering
Supported Cards
Solver Description
Supported Parameters
Notes
_FLAG /IMPDISP
Describes the imposed displacements.
/IMPTEMP
Defines imposed temperatures on a group of nodes.
/IMPVEL
Describes the imposed velocities.
/INITEMP
Describes the initial nodal temperature.
/INIVEL
Describes the initial velocities.
/INIVEL/AXIS
Describes the initial velocities around the axis.
/PLOAD
Describes the pressure loads.
/SPHBCS
Describes the SPH symmetry conditions.
/SPH/INOUT
Describes the SPH inlet/outlet conditions.
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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
ACSRCE
Defines acoustic source as a function of power vs. frequency.
DELAY_OPTION
Notes
DPHASE_OPTION
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.
DLOAD
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.
DTI_SPECSEL
Correlates spectra lines specified on TABLED1 entries with damping values.
EIGC
Defines data needed to perform complex eigenvalue analysis.
EIGRL
Defines data needed to perform real eigenvalue analysis (vibration or buckling) with the Lanczos Method.
FATDEF
Defines elements, and associated fatigue properties, for consideration in a fatigue analysis.
ELSET PSHELL PSOLID XELSET
851
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Altair Engineering
Supported Cards
Solver Description
Supported Parameters
Notes
XELEM FATEVNT
Defines loading events for fatigue analysis.
FATLOAD
Defines fatigue loading parameters.
FATPARM
Defines fatigue analysis parameters.
FATSEQ
Defines a loading sequence for fatigue analysis.
FATSEQ_NUM
FREQ
Defines a set of frequencies to be used in the solution of frequency response problems.
FREQ
FATEVNT_NUM_FLOA D
FREQ1 - FREQ5
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.
Defined using FREQi
FREQ2
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.
Defined using FREQi
FREQ3
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.
Defined using FREQi
FREQ4
Frequency List, Alternate Form 4. Defines a set of frequencies
Defined using FREQi
Altair Engineering
FREQ
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
852
Supported Cards
Solver Description
Supported Parameters
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.
GRAV
Defines the gravity vectors for use in determining gravity loading for the structural model.
INVELB
Defines initial velocity in a multibody situation.
LOAD
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.
MBACT
Defines the entity/set to be activated in the multi-body system for the subsequent simulation.
THRU
Defines the entity/set to be deactivated in the multi-body system for the subsequent simulation.
THRU
MBDEACT
MBLIN
853
Defined using FREQi
MBACT_NUMIDS
MBEACT_NUMIDS
Defines the parameters for a multi-body system linear analysis.
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Altair Engineering
Supported Cards
Solver Description
Supported Parameters
MBSEQ
Defines the simulation sequence for the multi-body solver.
MBSEQ_NUM_ID
MBSIM
Defines the parameters for a multi-body simulation.
Simulation Type (Transient, Static, Quasi-static)
MBSIMP
Parameters for subsequent multi-body simulation.
MLOAD
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.
MOTION
Defines a multi-body as a combination of motion sets defined via MOTNJ, MOTNJC, MOTNJE, MOTNG, MOTNGC, MOTNGE
MOTION_Num_Set
MPCADD
Multi-point constraint set combination.
Number_Of_Sets
NLOAD
Defines a loading condition for NLOAD_NUM nonlinear problems as a linear combination of load sets defined via NLOAD1.
NLOAD1
Defines a time-dependent load or enforced motion for use in geometric nonlinear analysis.
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
854
Supported Cards
Solver Description
Supported Parameters
Notes
LSTOL, MAXBIS, MAXR, RTOLB NLPCI NSMADD
Defines non-structural mass as the sum of the sets listed.
PFAT
Defines element properties for fatigue analysis
FINISH_REAL
RANDPS
Power Spectral Density Specification
RANDT1
RFORCE
Defines a static loading condition due to a centrifugal force field.
RLOAD1
Defines a frequency-dependent dynamic load for use in frequency response problems.
DELAY_OPTION
Defines a frequency-dependent dynamic load for use in frequency response problems.
DELAY_OPTION
RLOAD2
855
TREATMENT_REAL
DPHASE_OPTION
DPHASE_OPTION
RSPEC
Defines a directional combination method, modal combination method, excitation direction(s), response spectra and scale factors for response spectrum analysis.
RWALADD
Defines a rigid wall set as a union of rigid walls defined via RWALL entries.
SOLVTYP
Defines the solver to be used for Solver Type (PCG) static analysis.
RWALADD_Num_set
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Altair Engineering
Supported Cards
Solver Description
Supported Parameters
SPCADD
Single-point constraint set combination.
SPCADD_Num_Set
TABDMP1
Defines modal damping as a tabular function of natural frequency.
TABDMP1_NUM
TABLED1
Defines a tabular function for use in generating frequencydependent and time-dependent dynamic loads.
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.
TABLED3
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.
TABLED4
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.
TABLEFAT
Defines y values of each point on the loading time history.
TABLEM1
Defines a tabular function for use in generating temperaturedependent material properties.
Altair Engineering
Notes
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
856
Supported Cards
Solver Description
Supported Parameters
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.
TABLEM3
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.
TABLEM4
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.
TABLES1
Defines a tabular function for use as stress-strain curve in one-step stamping material property MATHF
TABLES1_NUM
TABRND1
Defines power spectral density as a tabular function of frequency for use in random analysis.
TABRND1_NUM
TEMPD
Defines a temperature value for all grid points of the structural model that have not been given a temperature on a TEMP entry.
TLOAD1
Defines a time-dependent dynamic load or enforced motion of the form:
Notes
for use in transient response analysis.
857
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Altair Engineering
Supported Cards
Solver Description
TLOAD2
Defines a time-dependent dynamic excitation or enforced motion of the form:
Supported Parameters
Notes
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.
XHISADD
Defines a time history output set as a union of time history outputs defined via XHIST entries.
XHISADD_Num_set
XSTEP
Defines explicit analysis control.
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.
Supported Card
Solver Description
Supported Parameters
Notes
*CFILM
Define film coefficients and
AMPLITUDE, FILM
Only in HISTORY
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
858
associated sink temperatures at one or more nodes or vertices
AMPLITUDE, REGION card image TYPE = {LAGRANGIAN/ SLIDING, EULEREIAN}, OP
*CONNECTOR LOAD Specify loads for available components of relative motion in connector elements
AMPLITUDE, LOAD CASE, OP
Only in HISTORY card image
*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
*DSLOAD
Specify distributed surface loads
AMPLITUDE, LOAD CASE, CYLIC MODE, OP
Only in HISTORY card image
*INERTIA RELIEF
Apply inertia-based load balancing
FIXED, ORIENTATION, REMOVE
Only in HISTORY card image of Standard template
*INITIAL_CONDITION Specifies initial pressures for S hydrostatic fluid filled cavities.
TYPE = FLUID PRESSURE
*INITIAL_CONDITION Specifies initial temperatures S for heat transfer analysis.
TYPE= TEMPERATURE
*INITIAL_CONDITION Specifies initial velocities for S dynamic analysis.
TYPE=VELOCITY
*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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
*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.
*BOUNDARY_NON_ REFLECTING
Define a non-reflecting boundary.
SSID, AD, AS
*BOUNDARY_NON_ REFLECTING_2D
Define a non-reflecting boundary.
NSID
*BOUNDARY_ PRESCRIBED_MOTI ON_ RIGID
Define an imposed nodal motion (velocity, acceleration, or displacement) on a node or a set of nodes.
PID, DOF, VAD, LCID, RIGID_LOCAL and SF, VID, DEATH, _SET options are BIRTH supported.
*BOUNDARY_ PRESCRIBED_MOTI ON_ RIGID_ID
Define an imposed nodal motion (velocity, acceleration, or displacement) on a node or a set of nodes.
Dyna_Name NSID, CID, DOFX, DOFY, DOFZ, DOFRX, DOFRY, DOFRZ Define temperature boundary conditions for a thermal or coupled thermal/structural analysis.
*CONSTRAINED_RIG Stops the motion based on a ID_ time dependent constraint. The BODY_STOPPERS stopper overrides prescribed motion boundary conditions
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Altair Engineering
Supported Cards
*DEFINE_CURVE_ FEEDBACK
Solver Description
Supported Parameters
(except relative displacement) operating in the same direction for both the master and slaved rigid bodies.
LCMAX_as_displacme nt
Notes
LCMIN_as_displacem ent
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
*DEFORMABLE_TO_ Define materials to be switched ArrayCount RIGID to rigid at the start of the PSID, MRB calculation. DeformToRigidHelp
Select an arraycount for the PSID and MRB pairs.
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.
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.
PID, XC, YC, ZC, TM, IXX, IXY, IXZ, IYY, IYZ, IZZ
*INITIAL_AXIAL_FOR Initialize axial force in the beam BSID, LCID CE_ for modeling bolt BEAM
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
862
Supported Cards
Solver Description
Supported Parameters
*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.
PID, X, Y, Z, LT
*INITIAL_STRESS_ SECTION
CSID, LCID, PSID, VID
Initialize stress in solid sections
Notes
PartOption
*INITIAL_TEMPERAT Define initial nodal point URE_ temperatures using nodal set SET IDs or node numbers.
NSID, TEMP, LOC
*INITIAL_VEHICLE_ KINEMATICS
Define initial kinematical information for a vehicle.
This card changes the INITV definition on Control Card 11. Only the first card defined is valid for Structured.
Options (NONE, Generation, Rigidbody) *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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Altair Engineering
Supported Cards
Solver Description
Supported Parameters
*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.
PSID, NSHV, FTYPE
Notes
Option1 (NONE, LSDYNA, NASTRAN, SEAMLESS) Option2 (None, THICKNESS, NO THICKNESS)
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Select component set.
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
Altair Engineering
Supported Cards
Solver Description
Supported Parameters
Notes
for Structured. *LOAD_BODY_Z
Card 41 LCID, SF, LCIDDR, CID
*LOAD_BODY_RX
Define body force loads due to a prescribed angular velocity using global axes directions
*LOAD_BODY_RY
Card 42 LCID, SF, LCIDDR, XC, YC, ZC, CID
Card 43 LCID, SF, LCIDDR, XC, YC, ZC, CID
*LOAD_BODY_RZ
Card 44 LCID, SF, LCIDDR, XC, YC, ZC, CID
*LOAD_BRODE
Define Brode function for application of pressure loads due to explosion.
Apply a concentrated nodal force to a node or a set of nodes.
NSID, DOFX, LCID, SF, CID
*LOAD_RIGID_BODY
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.
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
866
Supported Cards
Solver Description
Supported Parameters
*LOAD_SEGMENT_ SET
Apply the distributed pressure load over each segment in a segment set.
SSID, LCID, SF, AT
*LOAD_SHELL_SET
Apply the distributed pressure load over one shell element or shell element set.
ESID, LCID, SF, AT
*LOAD_SUPERELAS TIC_ FORMING
*LOAD_THERMAL_ CONSTANT
LCIDoption
LCIDoption
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.
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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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 collector’s 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
ACSRCE
Defines the power versus frequency curve for a simple acoustic source.
EXCITEID, DELAY, DPHASE, TP, RHO, B
Notes
DELAY_OPTION DPHASE_OPTION
AEFACT
Defines real numbers for aeroelastic analysis.
Total_Number
BCPARA
Defines contact parameters.
PARAM, VALUE BCPARA_NUM
BMFACE DELAY
Defines the time delay term in the equations of the dynamic loading function
Supported as constraints
DLOAD
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
DTI SPECSEL
Defines table data blocks
SPECSEL, RECNO, TYPE, TID, DAMP DTI_TID_NUM
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
868
Supported Cards
Solver Description
Supported Parameters
EIGB
Defines data needed to perform buckling analysis
contOpt
EIGC
Defines data needed to perform complex eigenvalue analysis
Cont
EIGP
Defines poles that are used in n/a complex eigenvalue extraction by the Determinant method
EIGR
Defines data needed to perform real eigenvalue analysis
EIGRL
Defines data needed to n/a perform real eigenvalue (vibration or buckling) analysis with the Lanczos method
FLFACT
Used to specify density ratios, Mach numbers, reduced frequencies, and velocities for flutter analysis.
FORMAT (IDS, THRU_FORMAT)
FLUTTER
Defines data needed to perform flutter analysis.
n/a
FREQ
Defines a set of frequencies to n/a be used in the solution of frequency response problems.
FREQ1
FREQ2
869
contOpt
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
Notes
FREQ FREQ1 - FREQ5
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Defined using FREQi.
Defined using FREQi.
Defined using FREQi.
Altair Engineering
Supported Cards
Solver Description
Supported Parameters
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.
Defined using FREQi.
FREQ4
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.
Defined using FREQi.
FREQ5
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.
Defined using FREQi.
GRAV
Defines acceleration vectors for gravity or other acceleration loading
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
n/a
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
870
Supported Cards
Solver Description
Supported Parameters
LSEQ
Defines a sequence of static load sets.
EXCITE, LID, TID
MARCOUT
Selects output to be saved on WHERE, IO the Marc t16 end/or t19 file(s) MARCOUT_MAX used in SOL 600 only.
MPCADD
Defines a multipoint constraint Number_Of_Sets set as a union of multipoint constraint sets defined via MPC entries.
NLAUTO
Defines parameters for automatic or fixed load/time stepping used in SOL 600 only.
NLDAMP
Defines damping constants for EID1, EID2, ALPHA, nonlinear analysis when Marc BETA, GAMMA is executed from SOL 600 only.
NLPARM
Defines a set of parameters for nonlinear static analysis iteration strategy
Defines a nonlinear radial (circular) gap for transient response or nonlinear harmonic response.
ID, GA, GB, PLANE, TABK, TABG, TABU, RADIUS
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Altair Engineering
Supported Cards
Solver Description
Supported Parameters
NLSTRAT
Defines strategy parameters for nonlinear structural analysis used in SOL 600 only.
PARAM, VALUE
NSMADD
Defines non structural mass as the sum of the sets listed.
S
NTHICK
Defines nodal thickness values for beams, plates and/ or shells.
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
n/a
RLOAD1
Defines a frequencydependent dynamic load of the form
DELAY_OPTION
Notes
ID options (1, 0, User)
DPHASE_OPTION
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
Altair Engineering
Defines a directional combination method, modal combination method,
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
872
Supported Cards
Solver Description
Supported Parameters
Notes
excitation direction(s), response spectra and scale factors for response spectrum analysis.
873
SPCADD
Defines a single-point constraint set as a union of single-point constraint sets defined on SPC or SPC1 entries
SPCADD_Num_Set
TABDMP1
Defines modal damping as a tabular function of natural frequency
TABDMP1_NUM
TABLED1
Defines a tabular function for use in generating frequencydependent and timedependent dynamic loads
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
TABLED3
Defines a tabular function for TABLED3_NUM use in generating frequencydependent and timedependent dynamic loads. Also contains parametric data for use with the table
TABLED4
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
TABLEM1
Defines a tabular function for use in generating
TABLEM1_NUM
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Altair Engineering
Supported Cards
Solver Description
Supported Parameters
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.
TABLEM2_NUM
TABLEM3
Defines a tabular function for use in generating temperature-dependent material properties. Also contains parametric data for use with the table.
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.
TABLES1
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).
TABLEST
Specifies the material TABLEST_NUM property tables for nonlinear elastic temperature-dependent materials
TABRND1
Defines power spectral TABRND1_NUM density as a tabular function of frequency for use in random analysis. Referenced by the RANDPS entry.
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
874
Supported Cards
Solver Description
Supported Parameters
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.
TIC
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.
TLOAD1
Defines a time-dependent dynamic load or enforced motion of the form
Notes
DELAY_OPTION
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
875
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.
TSTEP
Defines time step intervals at
TSTEP_NUM
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Altair Engineering
Supported Cards
Solver Description
Supported Parameters
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.
Definition of static mode shapes DOFTYPE to be added to the set of RSYS eigenmodes used for SOURCE transformation to modal space.
PERMAS
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
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
878
Supported Cards
Solver Description
Supported Parameters
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.
$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.
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.
See also Status Bar Model Browser Entity State Browser Entities & Solver Interfaces Include Files
879
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Altair Engineering
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of 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 RADIOSS (Bulk Data Format), OptiStruct
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.
881
Supported Card
Solver Description
Supported Load Types
ASET
Defines the boundary degrees of Constraints freedom of a superelement assembly for matrix reduction.
ASET1
Defines the boundary degrees of Constraints freedom of a superelement assembly for matrix reduction.
DAREA
Defines scale (area) factors for dynamic loads.
Constraints
DELAY
Defines the time delay term tau in the equations of the dynamic loading function.
Constraints
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Notes
Altair Engineering
DEFORM
Defines enforced axial Flux deformation for one-dimensional elements for use in statics problems.
DPHASE
Defines the phase lead term lower theta in the equation of the dynamic loading function.
Constraints
FORCE
Defines a static force at a grid point by specifying a vector.
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.
MBMNT
Defines a constant moment at a Moment grid point by specifying a vector.
MBMNTC
Defines a curve moment at a Moment grid point by specifying a vector.
MOMENT
Defines a static moment at a Moment grid point by specifying a vector.
MOMENT1
Defines a static moment by Moment specification of a value and two grid points, which determine the direction.
MOTNG
Defines a constant grid point motion.
Constraint
MOTNGC
Defines a grid point motion vs. time by specifying a curve.
Constraint
PLOAD
Defines a static pressure load on a triangular or quadrilateral element.
Pressure
PLOAD1
Defines concentrated, uniformly distributed, or linearly distributed applied loads to the CBAR or CBEAM elements at
Pressure
Altair Engineering
Force
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
882
user-chosen points along the axis.
883
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.
PLOAD4
Defines a load on a face of a HEXA, PENTA, TETRA, PYRA, TRIA3, or QUAD4 element.
Pressure
QBDY1
Defines a uniform heat flux for CHBDYE elements.
Flux
QVOL
Rate of volumetric heat addition for a conduction element.
Flux
SPC
Defines sets of single-point constraints and enforced displacements.
Constraint
SPCD
Defines an enforced displacement value for static analysis, which is requested as a LOAD.
Constraint
SUPORT
Defines determinate reaction degrees of freedom in a free body.
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.
TEMP
Defines temperature at grid points for determination of Thermal Loading and Stress recovery.
Temperature
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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.
Constraint
USET
Set of Degrees of Freedom for Residual Vector Calculation.
Constraint
USET1
Alternate Form of 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.
Specify nodes and weighting for distributing coupling elements
See Elements.
MASS
*DLOAD
Specifies distributed loads
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
Altair Engineering
Define a kinematic coupling constraint
Multi-point Constraints
Altair HyperMesh User's Guide Proprietary Inform ation of 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
Multi-point Constraints ORIENTATION
*MPC
Define multi-point constraints
Multi-point Constraints BEAM LINK See Elements. PIN
See Elements.
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
887
Supported Card
Solver Description
Supported Load Types
ACCELERATION
Boundary conditions
Face BC
ADMITTANCE
Boundary conditions
Face BC
DISPLACEMENT
Boundary conditions
Displacement
DISTRIBUTED_LOAD Boundary conditions
Face BC
DISTRIBUTED_PRES Boundary conditions
Face BC
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Notes
Altair Engineering
SURE DIV_TOTAL
Boundary conditions
Face BC
INFINITE ADMITTANCE
Boundary conditions
Face BC
POINT_LOAD
Boundary conditions
Load
PRESSURE
Boundary conditions
Pressure
VELOCITY
Boundary conditions
Face BC
Supported Card
Solver Description
Supported Load Types
BF
Defines a nodal body force load. Flux
ANSYS
Notes
FLUE and HGEN labels are
BF_FLUE
Flux
Supported under the Flux panel.
BF_HGEN
Flux
Supported under the Flux panel.
BF_TEMP
Temperatures
(Structural temperatures) label is supported under the Temperatures panel.
BFE_FLUE
Defines an element body force load
Flux
BFE_HGEN
Flux
BFE_TEMP
Flux
ConvBulkTe
Pressure
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
888
ConvFilmCo D_CONSTRNT
Pressure Defines DOF constraints at nodes.
Constraint
D_TEMP
Temperature
D_VOLT
Constraint
F_FLOW
Specifies force loads at nodes.
F_HEAT FLOTRAN
Flux Flux
Specifies "FLOTRAN data settings" as the subsequent status topic.
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.
FORCE2
Moment
HFLUX
Pressure
IC_CONSTRN
Specifies initial conditions at nodes.
Constraint
IC_TEMP
Temperature
IC_VOLT
Constraint
PRESSURE
Pressure
SFE
Defines elemental surface load
Pressure, Convection, Heatflux
Structural, thermal and Fluid labels are covered
SFE
Surface load
Structural, thermal, and fluid
Structural label: PRES Thermal label: CONV, HLFUX
889
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
*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
*BOUNDARY_ PRESCRIBED_MOTI ON_ NODE
Define an imposed nodal motion Velocity (velocity, acceleration, or Type 1; Card 26; displacement) on a node or a VAD = 0 set of nodes.
*BOUNDARY_ PRESCRIBED_MOTI ON_ NODE
Define an imposed nodal motion Acceleration (velocity, acceleration, or Type 1 displacement) on a node or a set of nodes. Card 26 VAD = 1
*BOUNDARY_ PRESCRIBED_MOTI ON_ NODE_(ID)
Velocity
*BOUNDARY_ PRESCRIBED_MOTI ON_ NODE_(ID)
Constraints
Notes
DOF 4, -4, 8, -8, 9, 9, 10, -10, 11, -11 are not supported
DOF 4, -4, 8, -8, 9, 9, 10, -10, 11, -11 are not supported
DOF 4, -4, 8, -8, 9, 9, 10, -10, 11, -11 are not supported
Type 2; Card 26, VAD =2 dynaName, DEATH, BIRTH
*BOUNDARY_SPC_ NODE
Altair Engineering
Define nodal single point constraint
Constraints
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
890
Type 1; Card 13 SPC CID *BOUNDARY_SPC_ NODE_ (ID)
Constraints
*BOUNDARY_ Define temperature boundary TEMPERATURE_NO conditions for a thermal or DE coupled thermal/structural analysis.
Temperature
*CONSTRAINED_GL OBAL
Constraints
Define a global boundary constraint plane.
LCID, LOC
*INITIAL_TEMPERAT Define initial nodal point URE_ temperatures using nodal set NODE IDs or node number.s
Temperatures
*INITIAL_VELOCITY
Type 2
Define initial nodal point translational velocities using nodal set IDs.
LOC
Card 30 INITV = 3
*INITIAL_VELOCITY_ Define initial nodal point NODE velocities for a node.
Rotation
*LOAD_BEAM_ELE MENT
Defines load on beam elements
Pressure
*LOAD_MASK
Apply a distributed pressure load over a three-dimensional shell part
n/a
*LOAD_NODE_POIN T
Apply a concentrated nodal force to a node or a set of nodes.
Force
*LOAD_NODE_POIN
891
dynaName, CID
Apply a concentrated nodal
Type 1; Card 23; Point Loads
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.
LS-DYNA Load Configs 1, 2, 3 and 4
FollowerForce
A load curve can be selected for these loads.
Moment
LS-DYNA Load
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Altair Engineering
T
force to a node or a set of nodes.
Type 1
Configs 5, 6 7 and 8.
Card 23 Point Loads
*LOAD_SEGMENT
Apply the distributed pressure Pressure load over one triangular or quadrilateral segment defined by LCID, AT four, six or eight nodes.
*LOAD_SEGMENT_I D
Apply the distributed pressure Pressure load over one triangular or quadrilateral segment defined by LCID, AT four, six or eight nodes.
*LOAD_SHELL_ELE MENT
Apply the distributed pressure load over one shell element or shell element set.
Pressure
*LOAD_SHELL_ELE MENT_ ID
Apply the distributed pressure load over one shell element or shell element set.
Pressure
*LOAD_SHELL_ PRESSURE
Apply the distributed pressure load over one shell element or shell element set.
Pressure
AT, LCIDoption
LCID, AT
Type 2 Card 24 Pressure BC
*LOAD_THERMAL_ CONSTANT_NODE
Define nodal sets giving the temperature that remains constant for the duration of the calculation.
Temperature
*LOAD_THERMAL_ VARIABLE_NODE
Define nodal temperature that is Temperature variable during the calculation. TS, LCID
n/a
MADYMO
Supported Card
Solver Description
Supported Load Types
CONSTRAINT. LINEAR
Linear constraint for FE nodes
Equation
Altair Engineering
Notes
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
892
EDGE
Force Moment
ELEMENT_AC
Pressure
INITIAL.NODE_DISP
Initial nodal displacement
Constraints
INITIAL.NODE_VEL
Initial nodal velocity
Constraints
LOAD
Defined on the card of the applicable load type.
MOTION. NODE_DISP
Prescribed nodal displacement.
Constraints
MOTION.NODE_VEL
Prescribed nodal velocity.
Constraints
NODE
Time dependent point loads Force (forces and moments) applied to Moment nodes.
PRES SUPPORT
Defined on the card of the referenced JOINT.
Pressure Define which degrees of Constraints freedom of nodes are constrained, by supporting them on a rigid body or the reference space.
MARC
Supported Card
893
Solver Description
Supported Load Types
Disp_chang
Constraints
DIST_LOADS
Pressure
Fixed_Acce
Constraints
Fixed_Disp
Constraints
Fixed_Pres
Constraints
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Notes
Altair Engineering
FOUNDATION
Pressure
Init_Disp
Constraints
INITIAL_vel
Velocity
MOMENT
Moment
POINT_LOAD
Constraints
Nastran
Supported Card
Solver Description
Supported Load Types
ASET
Defines degrees-of-freedom in the analysis set (a-set)
Constraints
ASET1
Defines degrees-of-freedom in the analysis set (a-set)
Constraints
BNDFIX1
Constraints
BSET1
Defines analysis set (a-set) degrees-of-freedom to be fixed (b-set) during generalized dynamic reduction or component mode synthesis calculations.
CSET1
Defines analysis set (a-set) Constraints degrees-of-freedom to be free (c-set) during generalized dynamic reduction or component modes calculations.
DAREA
Defines scale (area) factors for static and dynamic loads. In dynamic analysis, DAREA is used in conjunction with RLOADi and TLOADi entries.
DEFORM
Defines enforced axial Flux deformation for one-dimensional elements for use in statics
Altair Engineering
Notes
Constraints
Constraints
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
894
problems. FORCE
Requests the form and type of element force output or particle velocity output in coupled fluidstructural analysis.
Force
MOMENT
Defines a static concentrated moment at a grid point by specifying a scale factor and a vector that determines the direction.
Moment
OMIT1
Defines degrees-of-freedom to be excluded (o-set) from the analysis set (a-set).
Constraints
PLOAD
Defines a uniform static pressure load on a triangular or quadrilateral surface comprised of surface elements and/or the faces of solid elements.
Pressure
PLOAD1
Defines concentrated, uniformly distributed, or linearly distributed applied loads to the CBAR or CBEAM elements at user-chosen points along the axis.
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.
PLOAD4
Defines a pressure load on a face of a CHEXA, CPENTA, CTETRA, CTRIA3, CTRIA6, CTRIAR, CQUAD4, CQUAD8, or CQUADR element.
The THRU field is supported for feinput only. On export, additional pressure cards for the range specified are written.
Pressure
Unequal nodal pressures are now supported. The average pressure
895
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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.
Flux
QSET1
Defines generalized degrees-offreedom (q-set) to be used for generalized dynamic reduction or component mode synthesis.
Constraints
QVOL
Volume Heat Addition - Defines a rate of volumetric heat addition in a conduction element.
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.
SPC1
Defines a set of single-point constraints.
Supported for feinput only. On export, equivalent SPC cards are written. Alternate format with THRU in the fifth field is supported.
Altair Engineering
Constraints
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
896
SPCD
Defines an enforced displacement value for static analysis and an enforced motion value (displacement, velocity or acceleration) in dynamic analysis.
Constraints
SUPORT
Defines determinate reaction degrees-of-freedom in a free body.
Constraints
SUPORT1
Defines determinate reaction degrees-of-freedom (r-set) in a free body-analysis. SUPORT1 must be requested by the SUPORT1 Case Control command.
Constraints
TIC(D)
Transient Initial Condition Defines values for the initial conditions of variables used in structural transient analysis.
Constraints
TIC(V)
Transient Initial Condition Defines values for the initial conditions of variables used in structural transient analysis.
Constraints
TEMP
Defines temperature at grid points for determination of thermal loading, temperaturedependent material properties, or stress recovery.
Temperatures
USET
Defines a degree-of-freedom set.
Constraints
USET1
Defines a degrees-of-freedom set.
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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Altair Engineering
Supported Card
Solver Description
Supported Load Types
Notes
ACC3D /
Imposed accelerations
Acceleration
Acceleration type can be specified in the Acceleration panel.
BOUNC /
Define boundary condition
Constraints
CONLO /
Concentrated nodal load
Force(1)
DIS3D /
Imposed displacement
Constraints
DIS3DM /
Imposed minimum displacement
Constraints
DIS3DX /
Imposed maximum displacement
Constraints
INVEL /
Define initial velocity
Velocity
PREFA /
Pressure on shells
Pressure(1)
RAC3D /
Imposed rotational acceleration
Acceleration
RAN3D /
Imposed angular rotations
Constraints
RDA3D /
Radial 3D boundary conditions
Acceleration
RDD3D /
Acceleration type can be specified in the Acceleration panel.
Acceleration type can be specified in the Acceleration panel.
Constraints
RDV3D /
Radial 3D boundary conditions
Velocity
RVE3D /
Imposed rotational velocities
Velocity
RWALL /
Rigid wall definition
SECFO_PLANE /
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
898
VEL3D /
Imposed velocities
Velocity
Supported Card
Solver Description
Supported Load Types
Notes
$ADDMODES
Definition of static mode shapes to be added to the set of eigenmodes used for transformation to modal space.
Constraints
If static mode shapes will be added directly to nodes or nodesets (SOURCE=INPUT), the $ADDMODES can be created through the Constraints panel.
PERMAS
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.
899
$ADDMODES
Definition of static mode shapes to be added to the set of eigenmodes used for transformation to modal space.
Pressure
$CONLOAD
Definition of concentrated loads Force at nodal point degrees of freedom.
$CONLOAD
Definition of concentrated loads Moment at nodal point degrees of freedom.
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
If mode shapes will be applied based on the natural deformation of elements (SOURCE=INPUT) the $ADDMODES keyword needs to be created here.
Altair Engineering
$DISLOAD PRESS
Definition of pressure loads for elements, where loads are given for elements or element sets.
Pressure
$DISLOAD TEMP
Nodal temperatures defined on elements or element sets.
Pressure
$DISLOAD TEMPFILM
Surrounding temperatures for Pressure convective heat transfer applied on elements or element sets.
$DISLOADN TEMP
Nodal temperatures definition applied on nodes or node sets
$DISLOADN TEMPFILM
Surrounding temperatures for Temperature convective heat transfer applied on nodes or node sets.
$INIVAL
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.
$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.
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.
$INERTIAX
Definition of inertia forces acting Pressure on entire axisymmetric component or element sets.
Only ACCELERATION and GRAVITY are
Altair Engineering
Temperature
Altair HyperMesh User's Guide Proprietary Inform ation of 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.
$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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Altair Engineering
Supported Cards
Solver Description
Supported Load Types
.CLM FIX
Defines a set of single-point constraints
CONSTRAINT
.CLM DEP
Defines sets of enforced displacements
CONSTRAINT
.CLM CHA COMP 123
Defines a static force at a grid FORCE point by specifying a vector and a value.
Notes
.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.
.CLM FOL COMP 456 Defines a follower moment by specifying a vector and a value
MOMENT
.CLM PRESSURE
PRESSURE
Defines a static pressure load on any elements type
See also Include Files Load Collectors
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of 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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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.
See also Include Files Load Collectors Loads
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of 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.
See also Include Files Load Collectors Loads
905
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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.
See also Include Files Load Collectors Loads
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of 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.
See also Include Files Load Collectors Loads
907
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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.
See also Include Files Load Collectors Loads
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of 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.
See also Include Files Load Collectors Loads
909
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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.
See also Include Files Load Collectors Loads
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of 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 RADIOSS (Bulk Data Format), OptiStruct
Supported Card
Solver Description
Supported Load Types
MPC
Defines a multipoint constraint equation of the form.
Equation
Notes
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:
911
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
Supported Parameters
*EQUATION
Define linear multi-point constraints
Equations
Explicit node IDs are supported. Node sets
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Supported Load Types
CE
Defines a constraint equation relating to degrees of freedom.
Equation
Notes
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
*CONSTRAINED_LIN EAR
Define linear constraint equations between displacements and rotations, which can be defined in a local coordinate system.
Equations
*CONSTRAINED_LIN EAR_ GLOBAL
Define linear constraint equations between displacements and rotations, which can be defined in global
Equations
Altair Engineering
Notes
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
In the Element Types panel, select CONSTRAINT for element type = rigid.
dof1 = dof2 = dof3 = dof4 = dof5 = dof6 = EQUATION.MASTER Dependent part of linear constraint equation (eliminated degree of freedom).
DOF_DX DOF_DY DOF_DZ DOF_RX DOF_RY DOF_RZ
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
Select set all DOFs of MASTER NODE equal to the corresponding DOFs of the SLAVE NODE(s) for DIRECTION = ALL.
w = FACTOR EQUATION.SLAVE
Independent part linear constraint equation (retained degrees of freedom).
Equations nodes = NODE_ID Select: dof1 for DIRECTION = D1 dof2 for DIRECTION =
913
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Select set all DOFs of MASTER NODE equal to the corresponding DOFs of the SLAVE NODE(s) for DIRECTION = ALL.
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
Supported Load Types
Notes
MPC
Defines a multipoint constraint equation of the form.
Equation
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
Supported Load Types
Notes
MPC GENERAL
General linear constraint equation
Equation
For more information on MPC cards and using duplicate ID pools, see the Permas Interface
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
914
Overview topic.
See also Include Files Load Collectors
915
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
916
Solver Card Support for System Collectors RADIOSS (Block Format)
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
917
Solver Description
Supported Parameters
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Notes
Altair Engineering
/TRANSFORM/ROT
Defines rotational transformation on the node set.
/TRANSFORM/TRA
Defines translational transformation on the node set.
/TRANSFORM/SCA
Defines scaling transformation on the node set.
/TRANSFORM/SYM
Defines symmetry transformation on the node set.
LS-DYNA
The system collector cards can be previewed, but not edited. Supported Card
Solver Description
Supported Parameters
*DEFINE_ Define a transformation for the OPTION (SCALE, ROTATE, TRANSL) TRANSFORMATION INCLUDE_TRANSFORM keyword option. A1, A2, A3 Title
Notes
Transformations can be created using the Transformation Manager .
NumDatalines *INCLUDE_TRANSF Include file that supports ORM offset on its content IDs and transforms on its contents.
FILENAME
*NODE_TRANSFOR Transformation defined on M node set
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
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
918
Title
Transformation Manager .
Supported Parameters
Notes
PAM-CRASH 2G
Supported Card
Solver Description
TRANSFORMATION /
NAME, Selection, Keyword, D, X, Y, Z, N1, N2 NumDatalines
See also Model Browser Organize panel Entity State Browser HyperMesh Entities & Solver Interfaces Include Files
919
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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 RADIOSS (Block Format)
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
/FRAME/FIX
Describes the frames.
/FRAME/MOV
Describes the moving frames. Relative motion with respect to a reference frame.
/FRAME/MOV2
System definition with Z axis and YZ plane.
Altair Engineering
Supported Parameters
Notes
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
920
/FRAME/NOD
Describes the node defined moving frame.
/SKEW/FIX
Describes the fixed skew frames.
/SKEW/MOV
Describes the moving skew frames.
/SKEW/MOV2
System definition with Z axis and YZ plane.
RADIOSS (Bulk Data Format), OptiStruct
The Systems panel offers two methods to create local coordinate systems, working with the RADIOSS (Bulk Data), OptiStruct user profile as follows:
921
Supported Card
Solver Description
Supported Parameters
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.
This type of system is created from the create by node reference subpanel when cylindrical is the chosen type.
CORD1R
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.
This type of system is created from the create by node reference subpanel when rectangular is the chosen type.
CORD1S
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.
This type of system is created from the create by node reference subpanel when spherical is the chosen type.
CORD2C
Defines a cylindrical
This type of system is
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Notes
Altair Engineering
CORD2R
CORD2S
CORD3R
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.
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.
This type of system is created from the create by axis direction subpanel when rectangular is the chosen type.
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.
This type of system is created from the create by axis direction subpanel when spherical is the chosen type.
Defines a rectangular coordinate system by
This type of system is created from the create
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.
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.
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.
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
922
CORD4R
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.
by node reference subpanel when rectangular is the chosen type.
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.
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)
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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
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
LOCAL DIRECTIONS
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.
NAME SYSTEM DEFINITION = COORDINATES /NODES
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
*TRANSFORM
Specify a local coordinate system at nodes.
Altair Engineering
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
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
NSET
Altair HyperMesh User's Guide Proprietary Inform ation of 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
Notes
LOCAL
Defines a local coordinate system by location and orientation.
Defines a local coordinate system by location and orientation.
R5.0, Type, NCSY, CSYTYP, VAL1, VAL2, VAL3
Type = PRM not supported
Supported Parameters
Notes
LS-DYNA
The systems cards can be previewed, but not edited. Supported Card
Solver Description
*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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Altair Engineering
Supported Card
Solver Description
FE_CRDSYS
Coordinate system for FE elements.
ORIENTATION. MATRIX
Orientation defined by the direction cosine matrix.
ORIENTATION. SCREW_AXIS
Orientation defined by a screw axis and a rotation angle.
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.
ORIENTATION. Orientation defined by up to SUCCESSIVE_ROT three successive rotations.
Altair Engineering
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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
927
Supported Card
Solver Description
Supported Parameters
CORD1R
Defines a rectangular coordinate system using three grid points.
N/A
CORD2R
Defines a rectangular coordinate system using the coordinates of three points.
N/A
CORD1C
Defines a cylindrical coordinate system using three grid points.
N/A
CORD2C
Defines a cylindrical coordinate system using the
N/A
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Notes
Altair Engineering
coordinates of three points . CORD1S
Defines a spherical coordinate N/A system by reference to three grid points.
CORD2S
Defines a spherical coordinate N/A system using the coordinates of three points.
PAM-CRASH
Supported Card
Solver Description
Supported Parameters
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
FRAME /
Local frame definition system collectors
Altair Engineering
Supported Parameters
Notes
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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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.
Select elements and nodes subject to transformation
NAME, Selection, Keyword, D, X, Y, Z, N1, N2 NumDatalines
PERMAS
Supported Card
Solver Description
Supported Parameters
Notes
$RSYS
Reference system
{CART|CYL| SPHERE}
Assign the system to nodes to write the RSYS parameter in to the nodal coordinates card $COORD
$ROTB
Analysis or displacement system assigned to nodes
RSYS
Assign a system as displacement system to nodes to receive this card.
Samcef
The following cards are supported in the Samcef interface:
929
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Altair Engineering
Supported Cards
Solver Description
Supported Parameters
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Altair Engineering
Solver Card Support for Vector Collectors MADYMO
Supported Card
Solver Description
INFLATOR
card image = INFLATOR
Altair Engineering
Supported Parameters
Notes
AIRBAG_CHAMBER = reference to the parent element.
Altair HyperMesh User's Guide Proprietary Inform ation of 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
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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.
JET
Gas jet type
ID, NAME, AIRBAG_CHAMBER , INFLATOR_CHAR, SWITCH
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
SNORM
Defines a surface normal vector at a grid point for CQUAD4, CQUADR, CTRIA3, and CTRIAR shell elements.
Supported Parameters
Notes
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
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
See also Model Browser Organize panel Entity State Browser HyperMesh Entities & Solver Interfaces Include Files
935
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Supported Parameters
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Altair Engineering
Solver Card Support for Beamsection Collectors ANSYS
Supported Card
Solver Description
Supported Parameters
SECCONTROLS
Overrides program calculated properties.
VAL1, VAL2, VAL3, VAL4, VAL5, VAL6, VAL7
Altair Engineering
Notes
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
938
SECDATA
Describes the geometry of a section
Geometrical data for the section types supported by SECTYPE.
SECOFFSET
Defines the section offset for cross sections.
CENT, SHRC, ORIGIN, or USER.
SECTYPE
Associates section type information with a section ID number.
Output activation and format/ file selection for kinematic animation output.
EXTENDED, WRITE_COG_MARK ER, WRITE_FORMAT
COUPLING_BODY
Data of MADYMO bodies to be transferred to the external coupled program for contact evaluation by the external program.
EXTERNAL_REF, BODY, EXTERNAL_DATA
COUPLING_SURFA CE
Data of planes, hyperEXTERNAL_REF, ellipsoids and hyper-cylinders SURFACE to be transferred. ELLIPSOID, EXTERNAL_DATA, SURFACE type
MADYMO
Notes
NR_OF_EXTERNAL_DAT A_S = array size of EXTERNAL_DATA
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
939
Activation of structural motion FE_MODEL output. elements in MOTION_STRUCT_ OUTPUT_LIST (ALL, NONE, SELECT)
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Altair Engineering
PRINT_MARKER
Activation of writing marker data to the KIN3 file.
PRINT_OUTPUT_FE Activates output for a certain FE model.
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)
Altair Engineering
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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.
943
TIME_DURATION_IN File and format selection for JURY duration injury signals.
ID, NAME, SYSTEM, WRITE_FORMAT
TIME_HISTORY_CO Activates time history output NTACT for certain contacts.
ID, NAME
TIME_HISTORY_EN Activates time history output ERGY for energy.
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.
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
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Altair Engineering
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 HyperMesh User's Guide Proprietary Inform ation of 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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
TIME_HISTORY_MB Activates time history output for a particular multi-body system.
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
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
946
SELECT)
leaving the elements in the BELT_OUTPUT_LIST to be NONE.
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)
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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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.
TIME_HISTORY_TIM Output activation and format/ E_ file selection for time-step. STEP
ID, NAME, WRITE_FORMAT
PAM-CRASH 2G
Supported Card
Solver Description
Supported Parameters
BELTS /
Output activation and format/ file selection for kinematic animation output.
Ftol, TITLE, StartPt, Ns, Ni, FRICPR, TOLSLP, EndPt, Ne
Notes
NUM_SLIPRG
See also Model Browser Organize panel Entity State Browser
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
950
HyperMesh Entities & Solver Interfaces Include Files HyperBeam
951
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
952
953
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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 body’s local coordinate system. Moments of inertia and other rigid body properties are defined in the multibody collector’s 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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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 body’s 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 body’s 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
Notes
BODY. DEFORMABLE
Deformable body.
FE_MODEL, MODAL_STIF, MODAL_DAMP, LOAD.BODY_ACC
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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.
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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Altair Engineering
Ellipsoids Solver Card Support for Ellipsoids Currently no solver support is available.
See also Include Files Multibodies
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
960
Multibody Planes Solver Card Support for Multibody Planes MADYMO
Supported Card
Solver Description
SURFACE.PLANE
Rectangular plane
Supported Parameters
Notes
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.
See also Include Files Multibodies
961
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Altair Engineering
Multibody Joints Solver Card Support for Multibody Joints MADYMO
Supported Card
Solver Description
Supported Parameters
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.
JOINT.CYLI
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
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 = FREE
The syst and multibody to be specified at parent
card image = FREE
JOINT.FREE
JOINT. FREE_BRYANT
Altair Engineering
D1 and R1 can not be changed, because they are defined by the position and orientation of the systems connected by the JOINT.
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.
D1 through D3, R1 through R3 and ORIENT can not
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
962
963
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.
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.
card image = FREE
JOINT. FREE_ROT_DISP
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 = FREE_BRYANT
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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.
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
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
JOINT.REVO
JOINT.REVO_TRAN
JOINT.SPHE
Altair Engineering
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
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 = REVO
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 = REVO_TRAN
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
R1, D2 and D3 can not be changed, because they are defined by the position and orientation of the systems connected by the JOINT.
R1 can not be changed, because it is defined by the position and orientation of the systems connected by the JOINT.
D1 and R2 can not be changed, because they are defined by the position and orientation of the systems connected by the JOINT.
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
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
964
values will be exported. JOINT. SPHE_BRYANT
JOINT. SPHE_EULER
JOINT.TRAN
JOINT.TRAN_REVO
JOINT.TRAN_UNIV
965
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
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_EULER
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 = TRAN
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 = TRAN_REVO
The syst and multibody to be specified at parent and child refer to the CRDSYS_OBJECT_1 and CRDSYS_OBJECT_2 related
card image = TRAN_UNIV
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
R1 through R3 can not be changed, because they are defined by the position and orientation of the systems connected by the JOINT.
R1 through R3 can not be changed, because they are defined by the position and orientation of the systems connected by the JOINT.
D1 can not be changed, because it is defined by the position and orientation of the systems connected by the JOINT.
D1 and R2 can not be changed, because they are defined by the position and orientation of the systems connected by the JOINT.
D1, R2 and R3 can not be changed, because they are defined by the position and orientation of the systems connected by the JOINT.
Altair Engineering
JOINT.UNIV
JOINT.UNIV_TRAN
JOINT.USER
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
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_TRAN
R1 and R2 can not be changed, because they are defined by the position and orientation of the systems connected by the JOINT.
D1, R2 and R3 can not be changed, because they are defined by the position and orientation of the systems connected by the JOINT.
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.
See also Include Files Multibodies
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of 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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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.
See also Include Files Bags Collector and Collected Entities Named Entities
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of 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.
See also Include Files Bags Collector and Collected Entities Named Entities
973
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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.
See also Include Files Bags Collector and Collected Entities Named Entities
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of 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.
See also Include Files Bags Collector and Collected Entities Named Entities
975
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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.
See also Include Files Bags Collector and Collected Entities Named Entities
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of 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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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 RADIOSS (Block Format)
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.
981
Supported Card
Solver Description
/GRBEAM/BOX
Describes the beam groups box
/GRBEAM/BOX2
Describes the beam groups box
/GRBRIC/BOX
Describes the brick groups box
/GRBRIC/BOX2
Describes the brick groups box
/GRNOD/BOX
Describes the node groups box
/GRQUAD/BOX
Describes the quad groups box
/GRQUAD/BOX2
Describes the quad groups box
/GRSH3N/BOX
Describes the 3 node shell groups - box
Supported Parameters
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Notes
Altair Engineering
/GRSH3N/BOX2
Describes the 3 node shell groups - box
/GRSHEL/BOX
Describes the shell groups box
/GRSHEL/BOX2
Describes the shell groups box
/GRSPRI/BOX
Describes the spring groups box
/GRSPRI/BOX2
Describes the spring groups box
/GRTRUS/BOX
Describes the truss groups box
/GRTRUS/BOX2
Describes the truss groups box
/LINE/BOX
Definition of the line - box
/LINE/BOX2
Definition of the line - box
/SURF/BOX
Describes the surface definition on shell elements by box.
/SURF/BOX2
Describes the surface definition on shell elements by box.
/SURF/BOX/ALL
Describes the surfaced definition on solid elements both interior and exterior face by box.
/SURF/BOX/EXT
Describes the surface definition on solid elements exterior face by box.
LS-DYNA
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
982
Supported Card
Solver Description
*DEFINE_BOX
Defines a box to select entities in the model
Supported Parameters
Notes
See also Model Browser Entity State Browser HyperMesh Entities & Solver Interfaces Include Files
983
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
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 RADIOSS (Block Format)
Supported Card
Solver Description
/FUNCT
Input formats to define the function
/MOVE_FUNC
Describes the function scale and shift
Supported Parameters
Notes
Supported Parameters
Notes
RADIOSS (Bulk Data Format), OptiStruct
Multi-body dynamics curves are represented as curves. Supported Card
Solver Description
MBCRV
Defines a data curve for use in multi-body dynamics simulations.
Supported as a curve entity. Defined through the Curve Editor utility.
RADIOSS (Fixed Format)
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
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
986
Supported Card
Solver Description
Supported Parameters
Notes
*AMPLITUDE
Define an amplitude curve
NAME
Standard, Explicit
DEFINITION = TABULAR,
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:
987
Supported Card
Solver Description
Supported Parameters
*DEFINE_CURVE
Define a curve
SIDR, SFA, SFO, OFFA, OFFO, DATTYP
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Notes
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
Supported Card
Solver Description
Supported Parameters
FUNCTION.XY
Provides a definition of a n/a function, described as a series of X-Y pairs.
MADYMO
Altair Engineering
Notes
Curves can be created by different methods; refer to the online help. Curves are always exported as a
Altair HyperMesh User's Guide Proprietary Inform ation of 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
FUNCT /
Definition of curves
Supported Parameters
Notes
The FUNCT toggle can switch output to a LOCUR card.
LOCUR /
The FUNCT toggle can switch output to a FUNCT card.
PAM-CRASH 2G
Supported Card
Solver Description
Supported Parameters
FUNCT /
Definition of curves
n/a
Note:
Notes
Curve definition can be modified using the card previewer.
PERMAS
The following cards are supported in the PERMAS interface:
989
Supported Card
Solver Description
$FUNCTION
Function definition
Supported Parameters
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Notes
Altair Engineering
See also Model Browser Entity State Browser HyperMesh Entities & Solver Interfaces Include Files Plots Model Setup XY Plotting
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of 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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Altair Engineering
The following panels can be used to create and edit contact surfaces: Contactsurfs
Solver Card Support for Contact Surfaces RADIOSS (Block Format)
Supported Card
Solver Description
/LEVSET
Definition of the levelset.
/LINE/SEG/
Definition of the line -
Altair Engineering
Supported Parameters
Notes
Altair HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
992
segments /SURF/SEG/
Describes the surface definition - segments
RADIOSS (Bulk Data Format), OptiStruct
Master Slave contact is represented using contact surfaces. Supported Card
Solver Description
SURF
Defines a surface used in a contact definition.
Supported Parameters
Notes
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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Altair Engineering
Supported Card
Solver Description
*SET_SEGMENT
Definition segements on element faces.
Supported Parameters
Notes
Notes
PERMAS
Supported Card
Solver Description
Supported Parameters
$SURFACE
Surface definition
ELEMENTS, SURFID, SYSTEM, MAXSMOOTH
Supported Card
Solver Description
Supported Parameters
.SEL FACE
Defines a set of faces of 3D elements
GROUP, NOM, MAILLE, FACE
Samcef
Notes
See also Browsers HyperMesh Entities & Solver Interfaces Include Files Model Setup
Altair Engineering
Altair HyperMesh User's Guide Proprietary Inform ation of 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 HyperMesh User's Guide Proprietary Inform ation of Altair Engineering
Altair Engineering
The following panels can be used to create and edit control volumes: Control Vol
Solver Card Support for Control Volumes RADIOSS (Block Format)
Supported Card
Solver Description
Supported Parameters
/MONVOL
Describes the monitored volume types
/MONVOL/AIRBAG
Describes the airbag monitored volume type.
/MONVOL/ AIRBAG1
Defines the airbag using standard gas
SelectsurfBox
/MONVOL/AREA
Describes the monitored volume type AREA.
SelectsurfBox
/MONVOL/COMMU Describes the airbag with communications monitored volume type.
SelectsurfBox
/MONOVOL/ FVMBAG
Describes the airbag with FVMBAG type.
SelectsurfBox
/MONVOL/GAS
Describes the perfect gas monitored volume type.
SelectsurfBox
/MONVOL/PRES
Describes the pressure load curve monitored volume type.
SelectsurfBox
REFSTA
Describes the reference state (stress free state) of elements
Notes
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
Altair HyperMesh User's Guide Proprietary Inform ation of 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
*AIRBAG_ADIABAT Define an airbag or control IC_GAS volume _MODEL_ID
*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_
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)
*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
Supported Parameters
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
Notes
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.
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.
GAS_MIXTURE
Gas mixture with a fixed composition.
Defined on the same card as its parent GAS_MIXTURE (_VARIABLE). N2, MOL_FRACTION
Defined on the card of the parent.
GAS_MIXTURE_VA Gas mixture at a fixed time RIABLE after inflator triggering.
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.
This interface simulates impacts between an hyperellipsoidal rigid master surface and a list of slave nodes.
/INTER/TYPE15
This interface is a penalty contact interface without damping.
/INTER/TYPE18
Describes the Euler/Lagrange or ALE/Lagrange.
/INTER/TYPE19
This is a combination of interface Type 7 and Type 11, with common input based on the same slave / master surfaces.
/INTER/TYPE20
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.
INTER/TYPE21
Specific interface between a non-deformable master surface and a slave surface designed for stamping.
boundary condition properties for heat transfer analysis.
interfaces panel
PFBODY
Defines a flexible body for multi-body dynamics simulation.
Defined using the bodies panel
PRBODY
Defines a rigid body for multibody dynamics simulation.
Defined using the bodies panel
RWALL
Defines a rigid wall of the following types: Infinite Plane, Infinite Cylinder, Sphere and Parallelogram.
Defined using the rigid walls panel.
SECT
Defines a section for force output in geometric nonlinear analysis.
Defined using the interfaces panel.
TIE
Defines a kinematic tied contact used in geometric non-linear analysis.
Defined using the interfaces panel.
XDAMP
Defines damping used in geometric non-linear analysis.
Defined using the interfaces panel.
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
This card is a sub-option in the *COUPLING card image.
ADJUST ORIENTATION
The *FASTENER PROPERTY card is defined from the Property panel.
ATTACHMENT METHOD
It is also supported as COUP_DIS type rbe3 elements.
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}
*FIXED MASS SCALING
Specify mass scaling at the beginning of the step
DT ELSET TYPE= {BELOW MIN, UNIFORM, SET EQUAL DT}
Explicit template only
Explicit template only. Must be added to a load step (*STEP).
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
*PRE-TENSION SECTION
Associate a pre-tension node with a pre-tension section
The Standard template only. Must be added to a load step (*STEP).
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
The EDGE BASED surfaces can be created from the Contact Manager.
POSITION TOLERANCE *SURFACE
Define a surface or region in a model
NAME
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} TRIM
CROP COMBINE = {UNION, INTERSECTION, DIFFERENCE} Type Material *SURFACE BEHAVIOR
Define alternative pressureoverclosure relationships for contact
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
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.
CYCLIC SYMMETRY NO ROTATION TYPE NO THICKNESS CYCLIC SYMMETRY CONSTRAIN RATIO *VARIABLE MASS SCALING
Specify mass scaling during the step
DT
Explicit template only.
ELSET TYPE= {BELOW MIN, UNIFORM, SET EQUAL DT, ROLLING}
Must be added to a load step (*STEP).
FREQUENCY NUMBER INTERVAL CROSS SECTION NODES EXTRUDED LENGTH
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/ RBE2’s. 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
Holds master and slave elements.
Config 2
Holds master elements and slave nodes.
Config 3
Holds slave elements.
Config 4
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 group’s ID. NAME is 16 characters, starting in Column 9. ID field is 8 characters, starting in Column 35.
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
Option
Keyword *CONTACT_ Structured
SlidingOnly
Defines a *CONTACT_SLIDING_ONLY_option card. Off
Type 1
On
PENALTY
Type p1
SurfaceToSurfa Defines a *CONTACT_option_SURFACE_TO_SURFACE card. ce None
Type 3
Automatic
AUTOMATIC_
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
ONE_WAY_
Type 10
Automatic and OneWay
AUTOMATIC_ONE_W AY_
Type a10
Constraint
CONSTRAINT_
Type 17
Eroding
ERODING_
Type 14
TieBreak
TIEBREAK_
Type 9
Tied
TIED
Type 2
Tied and offset
TIED_OFFSET
Tiedshell
TIED_SHELL_EDGE
Tiedshell and offset
TIED_SHELL_EDGE_ OFFSET
The Tied option has an additional option to define OFFSET.
NodesToSurfac Defines a *CONTACT_option_NODES_TO_SURFACE card. e
ContactSpotwel Defines a *CONTACT_SPOTWELD card d none Torsion
WITH_TORSION
ContactSIngEd Defines a *CONTACT_SINGLE_EDGE card ge
Supported Card
Solver Description
Supported Parameters
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.
NodeCount
*ALE_REFERENCE Allows many choices of the _ reference system types for SYSTEM_SWITCH any ALE geometric entity.
T1 - T7
*ALE_SMOOTHING Smoothing constraint that keeps a node at its initial parametric location along a line between two other nodes.
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.
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
*CONTACT_AIRBA Define a contact interface. G_ SINGLE_SURFACE (ID)
Used to output information about certain coupled Lagrangian surfaces.
PSID TBD
*DATABASE_NOD AL_ FORCE_GROUP
Define a nodal force group for output into ASCII file NODFOR and the binary file XTFILE.
CID
*ELEMENT_TRIM
Define a part subset to be trimmed by *DEFINE_CURVE_TRIM
*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.
MMGID
*INITIAL_VOID (PART and SET)
n/a
Define initial voided part set IDs or part numbers.
TEMP PSID TBD RO1 - RO8
*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
*INTERFACE_ Define an interface for linking COMPONENT_NOD calculations. E
n/a
*INTERFACE_ Define an interface for linking COMPONENT_SEG calculations. MENT
*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
Name, exclude, BOXID, BIRTH, DEATH, Fric
Define a rigid wall with an analytically described form.
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
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_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.
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. .
Non-symmetric node-tosegment contact with edge treatment and zero contact thickness
MASS_GES / NSMAS /
Non structural mass
SECFO_CONTACT / SECFO_PLANE
Section definition for force output
IFRA TITLE R
SECFO_SECTION /
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.
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.
The following panels can be used to create and edit load steps: Load Steps
Solver Card Support for Load Steps RADIOSS (Bulk Data Format), OptiStruct
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
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
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.
ANALYSIS
Define a solution sequence for individual subcases.
Select a subcase (loadstep) and click edit. Check the box next to ANALYSIS and then select an analysis type.
CMSMETH
Defines the method, frequency upper limit, and number of modes to be used in component mode synthesis for flexibly-body preparation solution sequence.
Select a component mode synthesis method definition for use in a subcase.
CSTRAIN
Control ply strain results output for composites on a subcase level.
Select a subcase (loadstep) and click edit. Check the box next to Output and then the one next to Cstrain.
CSTRESS
Control ply stress results output for composites on a subcase level.
Select a subcase (loadstep) and click edit. Check the box next to Output and then the one next to Cstress.
DESOBJ
Define a subcase specific objective.
Part of the optimization problem setup, created in the Objectives panel.
Check the box next to CMSMETH and select a load collector with a CMSMETH card image.
Altair Engineering
DESSUB
Define a subcase specific design constraint.
Part of the optimization problem setup, created in the Dconstraints panel.
DISPLACEMENT
Control displacement 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 Displacement.
DLOAD
Select dynamic loading information for a subcase.
Check the box next to DLOAD and select a load collector with dynamic loading information (DLOAD, RLOAD1, RLOAD2, TLOAD1, TLOAD2).
EIGVRETRIEVE
Retrieve eigenvalue and eigenvector results from a normal modes analysis from an external data file.
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.
EIGVSAVE
Output eigenvalue and eigenvector results from a normal modes analysis to an external data file.
Select a subcase (loadstep) and click edit. Check the box next to EIGVSAVE, and enter an integer value in the card previewer.
ELFORCE
Control elemental force 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 Elforce.
ESE
Control element strain energy 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 Ese.
EXCLUDE
Select a set of properties to be excluded from a linear
Select a subcase (loadstep) and click edit. Check the box next to LABEL and enter a label in the card previewer.
LOAD
Select static loading information for a subcase.
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).
MBSIM
Select a multi-body dynamics simulation definition for a subcase.
Check the box next to MBSIM and select the load collector with an MBLIN, MBSEQ or MBSIM card image.
METHOD
Select eigenvalue extraction information for a subcase.
Check the box next to METHOD(STRUCT) or METHOD(FLUID) and select a load collector with an EIGRL card image.
MLOAD
Select multi-body dynamics loading information for a subcase.
Check the box next to MLOAD and select a load collector containing multibody dynamics loads (GRAV, MBFRC, MBFRCC, MBMNT, MBMNTC, MLOAD).
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.
Part of the optimization problem setup, created in the Responses panel.
MOTION
Select multi-body dynamics motion information for a subcase.
Check the box next to MOTION and select a load collector containing multi-
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.
MPCFORCE
Control MPC force 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 Mpcforce.
NLPARM
Select non-linear static analysis settings for use in a subcase.
Check the box next to NLPARM and select a load collector with an NLPARM card image.
NSM
Select non-structural mass input for entire model.
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.
OFREQUENCY
Define a set of frequencies for output requests for a subcase.
Select a subcase (loadstep) and click edit. Check the box next to Output and then the one next to Ofrequency.
OLOAD
Request the output of applied loads for a subcase.
Select a subcase (loadstep) and click edit. Check the box next to Output and then the one next to Oload.
OMODES
Define a set of modes for output requests for a normal modes or linear buckling subcase.
Select a subcase (loadstep) and click edit. Check the box next to Output and then the one next to Omodes.
RESVEC
Control the calculation of modal acceleration vectors.
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.
SUBCASE
Define a subcase.
Created automatically, when a new subcase is created. The subcase ID matches the ID of the HyperMesh loadstep entity.
SUBTITLE
Provide a subtitle for a loadstep.
Select a subcase (loadstep) and click edit. Check the box next to SUBTITLE and enter a subtitle in the card previewer.
SUPORT1
Select fictitious supports for use in a subcase.
Check the box next to SUPORT1 and select a load collector containing SUPORT1 loads.
TEMP
Select thermal loading information for a subcase.
Check the box next to TEMP and select a load collector containing TEMP loads or a load collector with the TEMPD card image.
TSTEP
Select integration and time step information for a transient analysis subcase.
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.
TTERM
Define the termination time of a geometric non-linear subcase
Check the box next to TTERM and input a real value for the termination
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.
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.
Part of the optimization problem setup, created in the Responses panel.
XHIST
Select time history output for geometric non-linear analysis
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
FREQUENCY SCALE INTERVAL REAL ONLY STIFFNESS CHANGE SUBSPACE PROJECTION = {ALL FREQUENCIES, CONSTANT, EIGENFREQUENCY , PROPERTY CHANGE, RANGE}
*STEP
Begin a step
CONVERT SDI INCREMENT
Parameters are defined in the load step card image.
NAME NLGEOM PERTURBATION UNSYMMETRIC AMPLITUDE=STEP, RAMP EXTRAPOLATION =LINEAR, PARABOLIC, NO *VISCO
Note:
Transient, static, stress/ displacement analysis with time-dependent material response (creep, swelling, and viscoelasticity)
CETOL CREEP
Defined in the load step card image.
FACTOR STABILIZE
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.
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
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
SUBCASE
Supported Parameters
Notes
LABEL, ANALYSIS, IC, BCONTACT, TRIM, OUTPUT
PERMAS
The following cards are supported in the PERMAS interface: Supported Card
Solver Description
Supported Parameters
Notes
$CONSTRAINTS
Constraint variant bracket header line
NAME
Create a loadstep and open its card image. Set the Analysis Procedure to CONSTRAINTS.
$FREQLOAD
Definition of frequency dependent dynamic loads for use in frequency response analysis.
DOFTYPE
The AnalysisProcedure toggle must be set to LOADING in the card image.
$LOADING
Loading variant bracket header line
NAME
$NLLOAD
Define a nonlinear static load history.
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
$TRANSLOAD
Definition of time dependent dynamic loads for use in transient response analysis.
Open the loadstep and set the AnalysisProcedure to SITUATION
AMPLITUDE BOUNDS DELAY
The TRANSLOAD card and FREQLOAD cards are mutually exclusive.
DOFTYPE FUNCTION PHASE
See also Browsers HyperMesh Entities & Solver Interfaces Include Files Element Property and Material Assignment Rules Model Setup
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.
Solver Card Support for Materials RADIOSS (Block Format)
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
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
Prony series input for Visco elastic plastic piesewise linear material MAT/LAW66
RADIOSS (Bulk Data Format), OptiStruct
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
MAT1
Defines the material properties MATS1 for linear, temperatureMATT1 independent, isotropic MAT4 materials. MAT5
Notes
Exported in large field format by optistructlf template.
Exported in large field format by optistructlf template.
Altair Engineering
MATT9
dependent material properties on MAT8 entry fields via TABLEMi entries.
extension to the MAT8 material.
Specifies temperaturedependent material properties on MAT9 entry fields via TABLEMk entries.
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
*BIAXIAL TEST DATA
Used to provide biaxial test data (compression and/or tension).
NStress, NStrain, NLStrain
*COMBINED TEST DATA
Specify simultaneously the normalized shear and bulk compliance or relaxation moduli as functions of time.
SHRINF
Altair Engineering
Notes
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.
Specify Mullins effect material parameters for elastomers
BETA DEPENDENCIES M
This card is a sub-option in the ABAQUS_MATERIAL card image.
PROPERTIES R TEST DATA INPUT USER
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
This card is a sub-option in the ABAQUS_MATERIAL card image.
DEPENDENCIES *SHEAR FAILURE
Specify a shear failure model and criterion
TYPE= {TABULAR, JOHNSON COOK} ELEMENT DELETION = {YES, NO}
This card is a sub-option in the ABAQUS_MATERIAL card image in the Explicit template.
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.
*SPECIFIC HEAT
Define specific heat
DEPENDENCIES
This card is a sub-option in the ABAQUS_MATERIAL card image.
*UNIXIAL TEST DATA
Used to provide uniaxial test data (compression and/or tension).
Nstress
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.
Nstrain Nlstrain
*USER MATERIAL
Define material constants for use in subroutine UMAT, UMATHT, or VUMAT
CONSTANTS TYPE= {MECHANICAL, THERMAL}
This card is a sub-option in the ABAQUS_MATERIAL card image.
This card is a sub-option in both the ABAQUS_MATERIAL and *GASKET MATERIAL card images.
*VISCOELASTIC
Specify dissipative behavior for use with elasticity
ERRTOL
This card is a sub-option in the ABAQUS_MATERIAL card image.
NMAX FREQUENCY=FOR MULA, TABULAR TIME= CREEP TEST DATA, RELAXATION TEST DATA, PRONY
Sub-options supported: *COMBINED TEST DATA *SHEAR TEST DATA *VOLUMETRIC TEST DATA For the sub-options, the parameters SHRINF and VOLINF are supported.
*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
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.
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
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.
Title 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.
Allows the modeling of temperature and rate dependent plasticity with a fairly complex model that has many input parameters.
Rho, E, PR, T, HC, C1 - C18, A1-A6, KAPPA,
Extension of model 51 which includes the modeling of damage.
Rho, E, PR, T, HC, Material Type 52 C1-18, A1-A6, N, D0, FS
Material Type 51
Title
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.
*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
*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.
RO, ROFLG, INTFAIL, ET, EN, FN_FAIL
An orthotropic material with optional brittle failure for composites can be defined.
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
Material Type 136
Title Anisotropy axis definition (0, 1, 2, 3, 4, by system) *MAT_CRUSHABLE Used to model crushable _FOAM foam with optional damping and tension cutoff.
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)
*MAT_DAMPER_ Used for discrete springs and NONLINEAR_VISCU dampers. OUS
LCDR
*MAT_DAMPER_VI SCOUS
DC
Used for discrete springs and dampers.
Material Type SD-5.
Title
Material Type SD-2.
Title
*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
*MAT_ELASTIC
Rho, E, Nu, DA, DB, Material Type 1. K
Isotropic elastic material that is available for beam, shell and solid elements.
Title
Fluid_Option Title
*MAT_ELASTIC_FL UID
*MAT_ELASTIC_PL ASTIC_ HYDRO
Isotropic elastic material available for beam, shell and solid elements.
Rho, E, Nu, DA, DB, Material Type 1. K, VC, CP
Allows the modeling of an elastic-plastic hydrodynamic material.
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.
*MAT_ENHANCED_ Enhanced versions of the COMPOSITE_DAM composite model Material AGE Type 22.
Title LCID_leakCoeff LCID_areaCoeff LCID_effLeakArea LCID_tensileStressC urve *MAT_FINITE_ELAS TIC_ STRAIN_PLASTICIT Y
*MAT_FLD_ TRANSVERSELY_ ANISOTROPIC
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
Used for simulating sheet forming processes with anisotropic material.
Rho, E, PR, SIGY, ETAN, R, HLCID, LCIDFLD
Material Type 112.
Title Material Type 39.
Title *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,
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.
Rho, DOF, TYPE, K, Material Type 196. D, CDF, TDF, FLCID, HLCID, C1, C2, DLE, GLCID
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.
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
Material Type 101.
Title *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
Special purpose element represents a combined hydraulic and gas-filled damper which has a variable orifice coefficient.
*MAT_HYPERELAS Provides a general TIC_ hyperelastic rubber model RUBBER combined optionally with linear viscoelasticity.
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
*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
*MAT_INELASTIC_6 Defined for simulating the DOF_ effects of nonlinear inelastic SPRING_DISCRETE and nonlinear viscous beams
by using six springs each acting about one of the six local degrees of freedom.
Title
*MAT_ISOTROPIC_ ELASTIC_FAILURE
Non-iterative plasticity with simple plastic strain failure model.
Rho, G, SIGY, ETAN, BULK, EPF, PRF, REM, TREM
Material Type 13.
Title *MAT_ISOTROPIC_ ELASTIC_PLASTIC
Very low cost isotropic plasticity model for threedimensional solids.
*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, SIGY, ETAN, BULK
Material Type 12.
Title
Rho, G, E, Nu, DTF, VP, RATEOP, A, B, N, C, M, TM, TR, EPSO, CP, PC, SPALL, IT, D1 - D5, C2/P
Material Type 15.
Title
*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
Material Type 110.
Title *MAT_KELVINUsed for modeling MAXWELL_VISCOE viscoelastic bodies, e.g., LASTIC foams.
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
*MAT_LAYERED_LI Layered elastoplastic material NEAR_ with an arbitrary stress versus PLASTICITY strain curve and an arbitrary strain rate dependency can be defined.
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.
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.
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.
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.
Rho, LCIDTR, Material Type 67. LCIDTS, LCIDTT, LCIDRR, LCIDRS, LCIDRT, LCIDTDR, LCIDTDS, LCIDTDT, LCIDRDR, LCIDRDS, LCIDRDT, FOR FOS, FOT, MOR MOS, MOT Title
*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.
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.
Title *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
*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.
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
Title *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
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
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.
*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
Title
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
*MAT_POWER_LA W_ PLASTICITY
This is an isotropic plasticity model with rate effects which uses a power law hardening rule.
reinforced concrete structures A1F, B1, PER, ER, subjected to impulsive PRR, SIGY, ETAN, loadings. LCP, LCR, X1- X16, YS1-YS16 Title
*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.
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
Material Type 170.
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
Material Type 28.
Title
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
*MAT_SAMP-1
Uses an isotropic C-1 smooth yield surface for the description of non-reinforced plastics.
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
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.
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.
Rho, E, Nu, Material Type 30. SIG_ASS, SIG_ASF, SIG_SAS, SIG_SAF, EPSL, ALPHA, YMRT
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.
Implemented with multiple through thickness integration points. Extension of Model 98 to include orthotropic damage as a means of treating failure in aluminum panels.
*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.
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
Material Type 181.
With-Failure Title *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.
RHO, K, MU, G, Material Type 183. SIGF, SGL, SW, ST, LCLD, TENSION, RTYPE, AVGOPT, LCUNLD
*MAT_SOIL_AND_F OAM
Rho, G, BULK, A0 A2, PC, VCR, REF, EPS, P
Simple model that works in some ways like a fluid.
Title
Material Type 5.
Title *MAT_SOIL_AND_F OAM_ FAILURE
*MAT_SPOTWELD
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.
Rho, G, BULK, A0 A2, PC, VCR, REF, EPS, P
Applies to beam elements Type 9 and to solid elements Type 1 with Type 6 hourglass controls.
Rho, E, PR, SIGY, ET, DT, TFAIL, EFAIL, NRR, NRS, MRR, MSS, MTT, NF
*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
Material Type 100.
Title *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.
K
Material Type SD-1.
Title
*MAT_SPRING_ ELASTOPLASTIC
Used for discrete springs and K, KT, FY dampers. Provides an Title elastoplastic translational or rotational spring with isotropic hardening located between two nodes.
Material Type SD-3.
*MAT_SPRING_GE NERAL_ NONLINEAR
Used for discrete springs and dampers. Provides a general nonlinear translational or rotational spring with arbitrary loading and unloading definitions.
LCDL, LCDU, BETA, Material Type SD-6. TYI, CYI
*MAT_SPRING_INE LASTIC
Used for discrete springs and dampers. Provides an inelastic tension or compression only, translational or rotational spring.
LCFD, KU, CTF
*MAT_SPRING_MA XWELL
Used for discrete springs and dampers. Provides a three Parameter Maxwell Viscoelastic translational or rotational spring.
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.
*MAT_STEINBERG
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.
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
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)
*MAT_TRANSVERS This model is for simulating ELY_ sheet forming processes with ANISOTROPIC_ELA anisotropic material. STIC_ PLASTIC
RO, E, PR, SIGY, ETAN, R, HLCID
*MAT_TRANSVERS This model is for simulating ELY_ sheet forming processes with ANISOTROPIC_ELA anisotropic material. STIC_ PLASTIC_ECHANG E
RO, E, PR, SIGY, ETAN, R, HLCID, IDSCALE, EA, COE
*MAT_TRIP
Material Type 37.
Echange_Option Title Material Type 37.
Title
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
Rho, K, N, MU, Material Type 178. LCID1, FITTYPE, LCSR, LCVE, NT, GSTART, C1-C8, B1B8, ArrayCount, GI, beta
Title
Title *MAT_VISCOUS_F OAM
*MAT_WINFRITH_ CONCRETE
Used to represent the Confor Foam on the ribs of EuroSID side impact dummy.
Rho, E1, N1, V2, E2, Material Type 62. N2, Nu
Only Type 84 includes rate effects. Model is a smeared crack, smeared rebar model implemented in the 8-node single integration point continuum element.
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
Material Type 146.
Title
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
COMPONENT
Material component used for definition of layered materials.
Supported Parameters
Defined on the card of the parent MATERIAL.
DAMAGE
MATERIAL.ANISO
Altair Engineering
Notes
Defined on the card of the parent MATERIAL. Linear elastic anisotropic material model.
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.
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
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.
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
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.
COMMENT MATERIAL.HYSISO Elastic isotropic material model with hysteresis.
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.
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
Rigid material
COMMENT
MATERIAL. SANDWICH
Linear elastic orthotropic sandwich material.
COMMENT
MATERIAL.STRAP
Tension-only perfect elasticplastic material model with failure for straps.
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.
Altair Engineering
with rupture. MATERIAL.USER
User defined material model
COMMENT
MATERIAL. VISCO_NL
Non-linear visco-elastic isotropic material
COMMENT
PERMEABILITY
Defined on the card of the parent MATERIAL.
RATE
Defined on the card of the parent MATERIAL.
RUPTURE THREAD
Definition of material properties via a characteristic specification for a thread (FABRIC material).
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
MAT1
Defines the material properties for linear isotropic materials.
MATS1
Notes
MATEP MATT1 MAT4 MAT5
MAT2
Defines the material properties for linear anisotropic materials for twodimensional elements.
MATEP MATT2 MAT4 MAT5
MAT4
Altair Engineering
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.
Defines the thermal material properties for anisotropic materials
KXX, KYY, KXZ, KYY, KYZ, KZZ, CP, RHO, HGEN
MAT8
Defines the material property for an orthotropic material for isoparametric shell elements.
MATT8
Defines the material properties for linear, temperature-independent, anisotropic materials for solid isoparametric elements.
MATEP
MAT9
MAT4 MAT5
MATT9 MAT4 MAT5
MAT10
Defines material properties for MAT4 fluid elements in coupled fluidMAT5 structural analysis.
MATHE
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.
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
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,
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)
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,
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.
Strain rate Model (no strain rate, CowperSymonds, JohnsonCook, ModifiedJones, Left Shifted, KrupKowsky) GRUC Option (DMG, THIC, NONE) TYPE 132
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.
Strain rate Model (no strain rate, CowperSymonds, JohnsonCook, ModifiedJones, Left Shifted, KrupKowsky) GRUC Option (DMG,
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-
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)
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)
Card fields vary depending upon the element type selected. Post-Yield behavior - defined by Yield Stress list box.
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 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)
Force-deflection curve specification requires existence of curves in the database.
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
Eo, Mu, E1, Eu) Strain rate Model (No strain rate, Cowper-Symonds, Johnson-Cook, Modified-Jones, Left Shifted, KrupKowsky)
depend on the value of NLOAD.
Hysteresis Model Flag for unloading/ reloading (Model A, B, or C) TYPE 212
Elastic-Plastic for Beam Elements
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
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.
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 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)
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
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
Altair Engineering
Flexion Torsion Joint Elements density, NINT, ISHG, Curves must exist in the IFROZ, QVISC, model before specifying THERDATASETNUM curve fields. , TITLE, MLOADU,
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
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)
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
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)
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
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
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.
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.
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.
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.
The following panels can be used to create and edit output blocks: Output Block
Solver Card Support for Output Blocks RADIOSS (Block Format)
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.
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
*CONTACT FILE
Define results file requests for contact 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
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
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
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).
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
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 /
Sensor point output definition
SENPTG /
Sensor point output definition
SUPPORT THELE /
Element time history
TITLE
THLOC /
Local frame definition for node output
IFRAM
Uses element output Definition Mode (Use block. EntityId List, Define Using General Entity Selection)
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.
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
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.
Solver Card Support for Plies RADIOSS (Bulk Data Format)
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
PLY
Defines the properties of a ply used in ply-based composite definition.
Supported Parameters
Notes
Can only be created and edited in the Ply Editor from the Model Browser.
See also Browsers HyperMesh Entities & Solver Interfaces
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.
Solver Card Support for Properties RADIOSS (Block Format)
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
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
/ACCEL
Defines accelerometers.
/ADMESH/SET
Describes the adaptive meshing.
/FAIL
Describes the failure models.
/FAIL/CHANG
Describes the Chang failure model.
/FAIL/CONNECT
Failure for solid elements used to model welds.
/FAIL/ENERGY
Describes the specific energy failure model.
/FAIL/FLD
Describes the forming limit.
/FAIL/HASHIN
Describes the Hashin failure model.
/FAIL/JOHNSON
Describes the failure criteria by Johnson-Cook failure model.
/FAIL/LAD_DAMA
Describes the Ladeveze failure model
/FAIL/PUCK
Describes the Puck failure model
/FAIL/SPALLING
Describes the Spalling and Johnson-Cook failure model.
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.
/PROP/TYPE19
This property set is used to define the ply property set used in ply-based composite definition.
/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
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
PAABSF
Defines the properties of a frequency-dependent acoustic absorber element.
PACABS
Defines the properties of the acoustic absorber element.
PBAR
Defines the properties of a simple beam (bar), which is used to create bar elements via the CBAR entry.
Supported Parameters
Notes
CONT1 PBARX
PBARL
Defines the properties of a PBARX simple beam (bar) by crosssectional dimensions, which is used to create bar elements via the CBAR entry.
PBEAM
Defines the properties of a beam that is used to create beam elements via the CBEAM entry.
Exported in large field format by optistructlf template.
CONTINUATION LINE 2 CONTINUATION LINE 5
Exported in large field format by optistructlf template.
CONTINUATION LINE 6 PBEAMX PBEAML
Defines the properties of a PBEAMX beam element by crosssectional dimensions that are used to create beam elements via the CBEAM entry.
PBUSH
Defines the nominal property values for a generalized spring-and-damper structural element.
Exported in large field format by optistructlf template.
rod, which is referenced by the CROD entry. PSHEAR
Defines the properties of a shear panel.
PSHELL
Defines the membrane, bending, transverse shear, and membrane-bending coupling of shell elements.
format by optistructlf template.
MID2_opts MID3_opts CONT
Exported in large field format by optistructlf template.
PSHELLX PSOLID
Defines the properties of solid PSOLIDX elements. Referenced by CHEXA, CPENTA, CPYRA and CTETRA entries.
PTUBE
Defines the properties of a thin-walled cylindrical tube element. Referenced by the CTUBE entry.
PVISC
Defines properties of a onedimensional viscous damping element (CVISC entry).
PWELD
Defines properties of connector (CWELD) elements.
HM_ELAS
Defines properties for a HM_Spring element, as explained in Using HM_ELAS.
DOF GE S
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
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.
ELSET, MATERIAL, SECTION
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,
Define viscous damping between contacting surfaces.
DEFINITION=DAMPI This card is a sub-option NG COEFFICIENT in the *SURFACE INTERACTION card image.
*DASHPOT
Define dashpot behavior.
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.
OFFSET
*ELEMENT PROPERTIES
ORIENTATION THICKNESS
*EULERIAN SECTION
Define properties of Eulerian ELSET continuum elements, including the list of materials that may occupy the elements.
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
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
*FLUID PROPERTY Define properties for hydrostatic fluid elements.
ELSET REF NODE TYPE AMBIENT
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.
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).
ROUGH TAUMAX USER *GAP
Altair Engineering
Specify clearance and local geometry for GAP-type elements.
ELSET
Only one *GAP card is output per component. Therefore, the gap
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
*MEMBRANE SECTION
Specify section properties for membrane elements.
ELSET MATERIAL
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.
ORIENTATION NODAL THICKNESS POISSON CONTROLS *NONSTRUCTURAL Specify mass contribution to
UNITS = {TOTAL MASS, MASS PER VOLUME, MASS PER AREA, MASS PER LENGTH}
template only
DISTRIBUTION = {MASS PROPORTIONAL, VOLUME PROPORTIONAL} *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
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.
POSITION DENSITY NODAL THICKNESS OFFSET *ROTARY INERTIA (no longer listed on panel)
Define rigid body rotary inertia. ELSET ALPHA COMPOSITE ORIENTATION
*SECTION CONTROLS
Specify section controls.
Only one *ROTARY INERTIA card is output per component. Therefore, the ROTARY1 elements in each component must have the same properties.
NAME WEIGHT FACTOR SECOND ORDER ACCURACY DISTORTION CONTROL
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.
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.
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
Specify section properties for surface elements.
ELSET
*SURFACE SMOOTHING
Create a surface smoothing NAME definition for contact interactions. It must be used in conjunction with the *CONTACT PAIR option.
*TRANSVERSE SHEAR STIFFNESS
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.
Supported Card
Solver Description
Supported Parameters
Notes
*CONSTRAINED_J OINT_ STIFFNESS_FLEXI ON-
Define optional rotational and translational joint stiffness for joints.
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.
*EOS_LINEAR_ Equation of state Form 6. POLYNOMIAL_WIT H_ ENERGY_LEAK (EOS 6)
C0 - C6, E0, V0, LCID
*EOS_PROPELLAN Equation of state Form 10. T_ Added to model airbag DEFLAGRATION propellants. (EOS 10)
*EOS_SACK_TUES Equation of state Form 3. DAY (EOS 3)
A1, A2, A3, B1, B2, E0, V0
*EOS_TABULATED Equation of state Form 9. (EOS 9)
GAMA, E0, V0, EV1- EV10, C1 C10, T1 - T10
Title
Title *EOS_TABULATED Equation of state Form 8. _ COMPACTION (EOS 8)
E0, V0, EV1 - EV10, C1 - C10, T1 - T10, K1 - K10
*EOS_TENSOR_P ORE_ COLLAPSE (EOS 11)
Equation of state Form 11.
NLD, NCR, MU1, MU2, IE0, EC0
*HOURGLASS
Define hourglass and bulk viscosity properties which are referenced via HGID in the *PART command.
Title
Title IHQ, QM, IBQ, Q1, Q2, QB, QW Title
*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
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.
Provides the inlet boundary condition for single gas flow (inflation potential) via a set of point source(s).
Title
MIXTURE, Title *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.
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:
As shown above, the single spring element writes a group of rigids and springs. On export, the following occurs: 1.
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.
2.
An RBE2 element is created, with 6 DOFS fixed, between Node 1 and Node 3.
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.
Note:
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.
Supported Card
Solver Description
Supported Parameters
PAABSF
Defines the properties of a frequency-dependent acoustic absorber element.
Defines the properties of a thin-walled cylindrical tube element (CTUBE entry).
beamsec
PVISC
Defines properties of a onedimensional viscous damping element (CVISC entry).
CE1, CR1
PWELD
beamsec Defines the properties of connector (CWELD) elements. D, MSET, TYPE
PTUBE
OD, T, NSM, OD2
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
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 /
FOR DEFINING INERTIA PROPERTIES) PHP BEAM DEGRE .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
.PHP SHELL
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.
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
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:
calculations on the logical signal from sensor logic.
Number of Switch
Supported Card
Solver Description
Supported Parameters
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.
TYPE (BODY, BODY_REL, JOINT_BRAKE, JOINT_POS)
_ CALC-LOGIC
Switch 1 Option
MADYMO
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)
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.
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
Supported Parameters
Notes
SENSO /
Definition of a sensor
Types 2 and 4 are not supported.
SENSOR/
Definition of a sensor
Types 2 and 4 are not supported.
See also Browsers HyperMesh Entities & Solver Interfaces Include Files Model Setup
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.
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
MBDCRV
Defines an ordered list of grids as a Multi-body Deformable Curve.
MBDSRF
Defines a Multi-body Deformable Surface.
MBPCRV
Defines a Multi-body Parametric Curve using node sets.
PANEL
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.
n/a
SET
Defines a set of grids, elements, design variables, MBD entities, mode numbers, frequencies or times for reference by other input definitions.
SET_DESVAR Contains design variables
Notes
Sets of integer and real values are supported as entity sets.
SET_ELEM Contains elements, properties, blocks or materials. SET_FREQ Contains real values. SET_GRID Contains nodes or
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
Notes
CMGRP
Groups components and assemblies into an assembly.
Name
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
*DEFINE_HEX_SPO Assembly of elements that TWELD describes a spotweld. _ASSEMBLY
DA1 - DA4 Generate a block of part IDs between a starting part ID NBEG, NEND number and an ending part ID Title number.
*SET_SEGMENT_ GENERAL
Definition of contact surface from parts, elements, box.
n/a
*SET_SHELL_ADD
Define a shell set by combining shell sets.
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.
Defines one or more panels by referencing sets of grid points, elements or properties.
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.
SEBSET1
Defines boundary degrees-of- SEID, C freedom to be fixed (b-set) during generalized dynamic reduction or component mode calculations.
SECSET1
Defines boundary degrees-of- SEID, C freedom to be free (c-set) ALL during generalized dynamic reduction or component mode synthesis calculations.
SEQSET1
Defines the generalized SEID, C degrees-of-freedom of the superelement to be used in generalized dynamic reduction or component mode synthesis.
SESET
Defines interior grid points for a superelement.
SEID
SET
Defines a set of element or grid point numbers to be plotted.
ID
SET1
Defines a list of structural grid ID points or element SKIN identification numbers.
Node and element sets supported with the THRU option.
Altair Engineering
SEUSET1
Note:
Defines a degree-of-freedom set for a superelement.
SEID, SNAME, C
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
Supported Parameters
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
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
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.
NAME DESCRIPTION
ESETBIN
Definition of element set bins. NAME An element set bin is defined DESCRIPTION by a list of element set names.
NSET
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.
NSETBIN
Definition of node set bins. A node set bin is defined by a list of node set names.
SFSET
Notes
NAME DESCRIPTION
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.
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.
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.
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.
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
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
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
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
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
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
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.
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
Solver Card Support for Design Variables RADIOSS (Bulk Data Format)
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.
Defined in the Composite Size panel.
DESVAR
Design variable definition. Supported as a designvariable entity.
Explicitly defined in the Size panel. Also defined automatically by the Gauge panel and the Shape panel.
DSHAPE
Free-shape design variable definition. Supported as a designvariable entity.
Defined in the Free Shape panel.
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.
Defined in the Composite Shuffle panel.
DSIZE
Free-size design variable definition. Supported as a designvariable entity.
Defined in the Free Size panel.
PCOMP, PCOMPG, and PSHELL components may be selected as free-size design regions.
Topography design variable definition. Supported as a designvariable entity.
Defined in the Topography panel.
PSHELL, PCOMP and PCOMPG components as well as predefined shape design variables may be selected as topography design regions. DTPL
Topology design variable definition. Supported as a designvariable entity.
Defined in the Topology panel.
PBAR, PBUSH, PCOMP, PCOMPG, PROD, PSHELL, PSOLID, PWELD can be selected. 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.
Exported in large field format by both the optistruct and optistructlf templates.
Defined in the shape panel.
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
DESVAR
Defines a design variable for design optimization.
Design variable definition
DLINK
Relates one design variable to one or more other design variables.
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 RADIOSS (Bulk Data Format)
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.
Design variable link. Supported as a designvariablelink entity.
designvariablelink
Defined in the Desvar Link panel.
Used to define links between DESVARs. 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
DLINK
Relates one design variable to one or more other design variables.
Supported Parameters
Notes
Design variable link
DLINK2
See also Optimization Browser View Entity State Browser Browsers HyperMesh Entities & Solver Interfaces Include Files Optimization
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 RADIOSS (Bulk Data Format)
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. Supported Card
Solver Description
DVCREL1
Generic design variable to connectivity property relationship. Supported as a designvariablepropertyrelation ship entity.
Supported Parameters
Notes
Defined in the generic relationship subpanel of the Size panel.
CBAR, CELAS2, CELAS4, CMASS2, CMASS4, CDAMP2, CDAMP4, CONM1, CONM2, CONROD, CQUAD4, CTRIA3, CQUAD8, CTRIA6 elements can be selected. DVCREL2
Generic design variable to connectivity property relationship. Supported as a designvariablepropertyrelation ship entity.
Defined in the function relationship subpanel of the Size panel.
CBAR, CELAS2, CELAS4, CMASS2, CMASS4, CDAMP2, CDAMP4, CONM1, CONM2, CONROD, CQUAD4, CTRIA3, CQUAD8, CTRIA6 elements can be selected. DVMREL1
Generic design variable to material relationship. Supported as a designvariablepropertyrelation ship entity.
Defined in the generic relationship subpanel of the Size panel.
MAT1, MAT2, MAT8 and MAT9 materials can be selected. DVMREL2
Altair Engineering
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.
MAT1, MAT2, MAT8 and MAT9 materials can be selected. DVPREL1
DVPREL2
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.
Defined in the generic relationship subpanel of the Size panel.
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 function relationship subpanel of the Size panel. Requires a dequation definition.
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.
* For PCOMPG, either global plies or property specific plies may be selected
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
DVCREL1
Defines the relation between a connectivity property and design variables.
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 RADIOSS (Bulk Data Format)
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.
Discrete design variable value lists. Supported as a ddval entity.
Notes
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
DDVAL
Solver Description
Supported Parameters
Notes
Define real, discrete design variable values for discrete variable optimization. Supported as a ddval entity.
Defined in the Discrete DVSpanel.
See also Optimization Browser View Entity State Browser Browsers HyperMesh Entities & Solver Interfaces Include Files Optimization
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 RADIOSS (Bulk Data Format)
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.
Supported Card
Solver Description
Supported Parameters
Notes
DRESP1
Generic response. Supported as a response entity.
Defined in the Responses panel. (All response types except function).
DRESP2
Function response. Supported as a response entity.
Defined in the Responses panel. (Use function response type).
DSYSID
Design objective for target optimization
Defined in the Responses panel.
MODEWEIGHT
The weighting applied to modes for response types WFREQ, COMB. Automatically created within relevant subcase definitions on export.
Defined in the Responses panel for WFREQ and COMB response types
WEIGHT
The weighting applied to compliances for response types WCOMP, COMB. Automatically created within relevant subcase definitions on export.
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.
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.
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
DCONADD
Collects constraints. DCONADD do not exist within the database, they are created automatically on export for opticonstraint entities.
DCONSTR
A constraint definition, defining lower and/or upper bounds for a response. Supported as an opticonstraint entity.
Defined in the Dconstraints panel.
DESGLB
Global constraint selection. Automatically created on export for opticonstraints that do not require a loadstep (subcase) selection.
opticonstraints are defined in the Dconstraints panel.
DESSUB
Subcase dependent constraint selection. Automatically created on export when a loadstep (subcase) is selected in an opticonstraint definition.
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.
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 RADIOSS (Bulk Data Format)
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.
Equations referenced on DRESP2, DVPREL2. Supported as an optimizationequation entity.
Supported Parameters
Notes
Defined in the Dequations 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
DEQATN
Defines one or more equations for use in design sensitivity or pelement analysis.
Supported Parameters
Notes
Equations referenced on DRESP2, DVPREL2
See also Optimization Browser View Entity State Browser Browsers HyperMesh Entities & Solver Interfaces Include Files Optimization
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 RADIOSS (Bulk Data Format)
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.
Table entries referenced on DRESP2, DVPREL2. Supported as a optimizationtableentries entity.
Supported Parameters
Notes
Defined in the Table Entries 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
DTABLE
Defines a table of real constants that are used in equations (see DEQATN entry).
Supported Parameters
Notes
Table entries referenced on DRESP2, DVPREL2
See also Optimization Browser View Entity State Browser Browsers HyperMesh Entities & Solver Interfaces Include Files Optimization
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 RADIOSS (Bulk Data Format)
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.
Supported Card
Solver Description
Supported Parameters
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
Defined in the Objective panel.
MINMAX MAXMIN
Objective functions for minmax (maxmin) problems. Supported as an objective.
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
DESOBJ
Selects the DRESP1 or DRESP2 entry to be used as the design objective.
MAXMIN
Objective functions for maxmin problems.
MINMAX
Objective functions for minmax problems.
Altair Engineering
Supported Parameters
Notes
Objective function, can be in or out of the load step; Belongs in the subcase section
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 RADIOSS (Bulk Data Format)
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.
Supported Card
Solver Description
DOBJREF
Reference definition for minmax (maxmin) optimization problems. Supported as an objectivereference.
Supported Parameters
Notes
Defined in the Obj Reference panel.
See also Optimization Browser View Entity State Browser Browsers HyperMesh Entities & Solver Interfaces Include Files Optimization
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 RADIOSS (Bulk Data Format, OptiStruct)
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.
Supported Card
Solver Description
DSCREEN
Constraint screening. Supported as an optimizationconstraintscreenin g entity.
Supported Parameters
Notes
Defined in the Constr Screen 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
DSCREEN
Defines screening data for constraint deletion.
Supported Parameters
Notes
Constraint screening
See also Optimization Browser View Entity State Browser Browsers HyperMesh Entities & Solver Interfaces Include Files Optimization
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 RADIOSS (Bulk Data Format, OptiStruct)
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.
Optimization control card. Supported as an optimizationcontrol entity.
optimizationcontrol
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
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
DOPTPRM
Overrides default values of parameters used in design optimization.
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 RADIOSS (Block Format)
Supported Card
Solver Description
Supported Parameters
Notes
/ADMESH/GLOBAL Defines the global parameters. /ALE/DISP
Improvement of error messages for stamping applications
/TITLE
Describes the title.
/UNIT
Describes the local unit system.
/UPWIND
Describes the upwind coefficient.
RADIOSS (Bulk Data Format), OptiStruct
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
ACCELERATION
Controls the output of acceleration results
Supported Parameters
Notes
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.)
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.
CONTF
Subcase information for explicit analysis
Found under GLOBAL_OUPUT_REQU EST.
CSTRAIN
Controls the output of strain results for composite shells.
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.)
CSTRESS
Controls the output of stress results for composite shells.
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.)
DAMAGE
Controls the output of fatigue damage 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.)
Controls the output of density results from a topology or freesize optimization.
DENSRES
Controls the output of density results from a topology or freesize optimization.
DESHIS
Controls the creation of the . hgdata file.
DISPLACEMENT
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.)
DMIGNAME
Defines the name given to the reduced matrices written to an external data file.
ECHO
Controls the echo of input data to the .out or .echo files.
EIGVNAME
Defines the prefix to be used for the saving and retrieval of external eigenvalue data files.
ELFORCE
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.)
Supported as an output option on the subcase definition when it appears within a subcase. (Use the edit button in the Loadsteps panel.)
Controls the gradient and flux 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.)
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.)
GPSTRESS
Controls the output of grid point stress results (available for PSOLID components only).
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.)
When using the two-file setup, INFILE indicates the prefix of the file containing the bulk data information.
Its extension must be . fem.
LIFE
Controls the output of fatigue life 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.)
LOADLIB
Defines the libraries to be loaded for external responses (DRESP3).
MBFORCE
Requests force output for a set of joints and/or force elements from multi-body dynamics subcases.
Found under GLOBAL_OUPUT_REQU EST.
MODEL
Requests output for all formats for only a subset of the model and results.
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.
MPCFORCES
Controls the output of MPC 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.)
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.
TYPE (ERROR, WARNING) VALUE (OFF, NONE) TYPE_ID VALUE_INT
Defines a set of frequencies at which results are output for frequency response 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.)
OLOAD
Controls the output of applied 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.)
OTIME
Defines a set of times at which results are output for transient analysis.
OUTFILE
Defines the path to, and the prefix of, the results files output by RADIOSS (Bulk Data), OptiStruct.
OUTPUT
Controls the frequency and format of results output by RADIOSS (Bulk Data), OptiStruct.
PFGRID
Can be used in the I/O Options section to request output of acoustic grid participation factors for all frequency response subcases.
Altair Engineering
Found under GLOBAL_OUPUT_REQU EST.
GRIDS (SETG_SID) GRIDF (SETFL_SID) FREQUENCY (SETF_SID)
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.
RESPRINT
Controls the output of unretained optimization constraints.
RESTART
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.
Controls the frequency of output of analytical results during an optimization.
SACCELERATION
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.)
SDISPLACEMENT
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 appears within a subcase. (Use the edit button in the Loadsteps panel.)
SCREEN
Controls the information echoed to the screen during a run.
SENSITIVITY
Controls the output of responses and sensitivities for size and shape design variables to a Microsoft Excel spreadsheet.
SENSOUT
Controls the frequency of output of responses and sensitivities to a Microsoft Excel spreadsheet.
SHAPE
Controls the output of shape optimization results from a shape, topography or freeshape optimization.
SHRES
Controls the frequency of output of the state files (.sh and .grid).
SPCFORCES
Controls the output of singlepoint force of constraint
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.
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.)
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.
SYSSETTING
Run control
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.
THIN
Can be used in the I/O Options or Subcase Information sections to request thinning and thickness output for all
geometric nonlinear analysis subcases or individual geometric nonlinear analysis subcases respectively. TITLE
Defines a title for a RADIOSS (Bulk Data), OptiStruct model.
TMPDIR
Defines a temporary directory where scratch files will be written.
UNITS
Defines a system of units for the model.
VELOCITY
Controls the output of velocity results.
RADIOSS (Bulk Data), OptiStruct allows multiple TMPDIR entries, but only one instance is currently supported.
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.)
XSHLPRM
Defines default shell element parameters for geometric nonlinear analysis.
XSOLPRM
Defines default SOLID properties for geometric nonlinear analysis.
The following Global Matrix Selectors are supported as control cards: Global Matrix Selector
Solver Description
B2GG
Identifies a DMIG bulk data entry as a viscous damping matrix.
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.
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
BULK_UNSUPPOR TED_ CARDS
Altair Engineering
Notes
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,
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.
through the use of 'debug, , ' 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.
INCLUDE_CTRL
This control card is retained to support old database files.
Model Documentation
$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
Some special diagnostic information can be processed through the use of 'osdiag, , , , ' 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
*CONSTRAINT CONTROLS
Reset overconstraint checking controls
NO CHECKS
Notes
NO CHANGES DELETE SLAVE
*DEPVAR
Specify solution-dependent state variables
svcount
*HEADING
Print a heading on the output
Title MultipleLines
*PREPRINT
Select printout for the analysis CONTACT input file processor. ECHO HISTORY MASS PROPERTY MODEL
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
Notes
Analysis
Specify options about the analysis
Type of analysis (Frequency, Modal Extraction, Time Response, External Matrices)
Specify:
Solver (KRYLOV, SPARSE, SUPERLU, CG_ILU)
Frequency or modal analysis Frequency range and/or number of modes The solver
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
The excitation must be defined in two files: a mesh file and a results file defining the vibration on each node.
RESULTS format, type, file name Dimension
Define the dimension of the problem.
Dimension (3D, 2D, 2D AXI)
2D, 3D, or axisymmetric
Interface
Define interfaces for incompatible meshes.
n_interfaces
Optional. Each interface must be linked with two coupling surfaces.
LIGHTHILL
Use for predicting broadband aero-acoustic noise
HDF File name
Include a file containing the FLOW data block.
FLOW FORMAT (ACTRAN, HDF)
MEAN_FLOW
Altair Engineering
num_hdf_la Used for further convected acoustic simulations
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).
SUPER_ELEMENT
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
Optional
Description
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
*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
Color
Explanation
Undefined
Gray
The control card was either never created or was deleted.
Defined (See Note)
Green
Any control card viewed in the card previewer is activated.
Inactive
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 one of the following states: State
Description
Default = ON
In this state, the field label color is yellow and no data entry is allowed.
Default = OVERRIDDEN
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.
The following keywords are supported: Supported Card
Solver Description
*CONTROL_ACCURA CY
Define control parameters that can OSU, INN, PIDOSU improve the accuracy of the calculation.
*CONTROL_ADAPST EP
Define control parameters for contact interface force update during each adaptive cycle.
*CONTROL_DYNAMIC Initialize stresses and deformation NRCYCK, DRTOL, _ in a model to simulate a preload. DRFCTR, DRTERM, TSSFDR, IRELAL, RELAXATION EDTTL, IRDFLG
*CONTROL_IMPLICIT_ Allows analysis of linear static INERTIA_RELIEF problems that have rigid body modes.
IRFLAG THRESH
*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
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.
IAS, SCALE, TSTART, TEND, SCALE_Option
*CONTROL_IMPLICIT_ Specify termination criteria for TERMINATION implicit transient simulations.
DELTAU
*CONTROL_MPP_ DECOMPOSITION_ AUTOMATIC
Instructs the program to apply a simple heuristic to try to determine the proper decomposition for the simulation.
n/a
*CONTROL_MPP_ DECOMPOSITION_C HECK _SPEED
Modifies the decomposition n/a depending on the relative speed of the processors involved.
*CONTROL_MPP_ DECOMPOSITION_ CONTACT_DISTRIBUT E
Ensures that the indicated contact ID1 - ID5 interfaces are distributed across all processors, which can lead to better load balance for large contact interfaces.
*CONTROL_MPP_ DECOMPOSITION_ CONTACT_ISOLATE
Ensures that the indicated contact ID1 - ID5 interferences are isolated on a single processor, which can lead to decreased communication.
Allow for pre-decomposition and a Name subsequent run or runs without having to do the decomposition.
*CONTROL_MPP_ DECOMPOSITION_ METHOD
Specify the decomposition method to use.
Name
*CONTROL_MPP_ DECOMPOSITION_ NUMPROC
Specify the number of processors for decomposition.
N
*CONTROL_MPP_ DECOMPOSITION_S HOW
Allows display of the final decomposition.
n/a
*CONTROL_MPP_ DECOMPOSITION_ TRANSFORMATION
Specifies transformations to apply TYPE(1) to modify the decomposition. VAL(1)
*CONTROL_MPP_IO_ Suppress the output of all dump NOD3DUMP files.
n/a
*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.
*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.
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.
n/a
*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.
n/a
*CONTROL_SUBCYC LE
n/a
Control time step subcycling.
*CONTROL_TERMINA Stop the job. TION
ENDTIM, ENDCYC, DTMIN, ENDENG, ENDMASS
*CONTROL_THERMA L_ NONLINEAR
REFMAX, TOL, DCP, LUMPBC, THLSTL,
Set parameters for a nonlinear thermal or coupled structural/ thermal analysis.
Provides approximately constant damping over a range of frequencies.
CDAMP, FLOW, FHIGH, PSID
*DAMPING_GLOBAL
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 Dt for time history data of element DT, LCDT _ subsets. D3THDT *DATABASE_BINARY Binary output restart files. Define _ output frequency in cycles. D3DUMP
*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
*DATABASE_MOVIE
Specify time interval for movie output
*DATABASE_MPGS
Specify time interval for MPGS
*DATABASE_NCFOR C
Specify time interval and file type for nodal interface forces time history file output
*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_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.
*DATABASE_SECFO RC
Specify time interval and file type for cross section forces time history file output
*DATABASE_SLEOU T
Specify time interval and file type for sliding interface energy time history file output
*DATABASE_SPCFO RC
Specify time interval and file type for SPC reaction forces time history file output
*DATABASE_SPHOU Specify time interval and file type T for SPH element data time history file output
*DATABASE_SPRING Create spring forward nodal force _ file. FORWARD
IFLAG
*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.
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.
*DATABASE_TRHIST
Tracer particle history information
*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
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.
CASEUNSUPPORTED_ CARD
n/a
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.
CEND
n/a
When the model is created from HyperMesh, this card is on by default.
DIAG
ENDDATA
Designates the end of the Case Control Section and/or the beginning of a Bulk Data Section.
Requests diagnostic output or special options.
DIAG DIAGIDLEN
Designates the end of the Bulk n/a Data Section.
When the model is created from HyperMesh, this card is on by default.
EXEC_UNSUPPOR TED_ CARDS
n/a
GLOBAL CASE
LABEL, ANALYSIS, AUTOSPC,
Altair Engineering
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.
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
setid, SET_realList
Only real number sets can be created using control
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.
NA
Model Documentation
n/a
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.
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.
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 /
Title
TITLE
UNIT
Unit System
Length, Mass, Time, Temperature
Unsupported Cards
All unsupported information found in the input deck is imported in this card. You can edit this card.
PERMAS
The following cards are supported in the PERMAS interface:
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.
2.
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.
3.
If there is no property assigned to the component, then the element has no property assignment.
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.
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.
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
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.
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
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
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
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
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
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
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
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
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 aren’t 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.
For example, consider the DTPL card shown above with a new field that isn’t 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
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.
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
$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
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
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.
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.
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.
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.
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
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
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
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
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
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
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
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
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
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
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.
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.
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).
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
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
CAD Reader Support Latest CAD Version CAD Format Supported ACIS
r19
Platforms1
x86
Windows x86_64
Linux x86
x86_64
Y
Y
Y
Y
Y
Y
Y
Y
DXF
v4 v5r20 AutoCAD 12
Y
Y
Y
Y
IGES
v6 JAMA-IS
Y
Y
Y
Y
JT
9.4
Y
Y
Y
Y
Parasolid
v19
Y
Y
Y
Y
PDGS
v26
Y
Y
Y
Y
Pro E
Wildfire 5
Y
Y
Y
Y
SolidWorks
2010
Y
Y
Y
Y
STEP
AP203 AP214
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
N
Y2
Y
Y
Y
Y
CATIA
Tribon
UG VDAFS
TXHSTL-R Tribon XML Export v1.3 NX5 NX6 NX7 v2
1
Refer to the official HyperWorks platform support list for full details.
2
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
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)
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)
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)
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)
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
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.
STEP Reader Support The following entities are supported by the STEP reader: Free points Free curves Surfaces Quilt bodies Solid bodies Facets/triangles Assemblies
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.
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 don’t 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.
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
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
This must point to the UG installation directory 2.
UGII_ROOT_DIR
This must point to the UG installation UGII directory 2.
PATH
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
This must point to the UG installation directory 2.
UGII_ROOT_DIR
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
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. 2
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
ACIS Import Options The ACIS reader uses the ct_reader.ini file with the following available options:
@ColorsAsMetadata Value
Description
on
Read color attributes of geometric entities as metadata. COLOR_RGB
off
Do not read color attributes (default).
@DensityAsMetadata Value
Description
on
Read density value as metadata (default). DENSITY
off
Do not read density value.
@ImportForVisualizationOnly Value
Description
on
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.
off
Import the model in the normal fashion (default).
@ImportFreeCurves Value
Description
on
Import free curves (wireframe entities) into the model (default).
CATIA Import Options The CATIA v4 and CATIA v5 readers use the ct_reader.ini file with the following available options:
@ColorsAsMetadata Value
Description
on
Read color attributes of geometric entities as metadata. COLOR_RGB
off
Do not read color attributes (default).
@DensityAsMetadata Value
Description
on
Read density value as metadata (default). DENSITY
off
Do not read density value.
@FullNameAsMetadata Value
Description
on
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
Description
on
Import of invisible (blanked/NO SHOW) components is enabled. This option, when used, takes priority over any other similar options/settings.
Import of invisible (blanked/NO SHOW) components is disabled (default). This option, when used, takes priority over any other similar options/settings.
@ImportForVisualizationOnly Value
Description
on
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.
off
Import the model in the normal fashion (default).
@ImportFreeCurves Value
Description
on
Import free curves (wireframe entities) into the model (default).
off
Do not import free curves.
@ImportFreePoints Value
Description
on
Import free points into the model (default).
off
Do not import free points.
@MetadataPrefix Value
Description
string
The string is prefixed to all metadata names. No prefix is used by default. See CAD Metadata Naming for more details.
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
Description
on
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).
off
The faceting is not checked and only the normal cleanup is applied.
@ColorsAsMetadata Value
Description
on
Read color attributes of geometric entities as metadata. COLOR_RGB
off
Do not read color attributes (default).
@ImportForVisualizationOnly Value
Description
on
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 free curves (wireframe entities) into the model (default).
off
Do not import free curves.
@ImportFreePoints Value
Description
on
Import free points into the model (default).
off
Do not import free points.
@ImportLayers Value
Description
Layers to skip
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
Description
ASSEMBLY
An assembly tree corresponding to the one contained in the file is generated (default).
LAYERS_ONLY
The components are created depending on the layer (=level) structure of the file.
LAYERS_AND_GROUPS The components are created corresponding to layers and groups contained in the file.
@MetadataPrefix Value
Description
string
The string is prefixed to all metadata names. No prefix is used by default.
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. 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"
@TagsAsMetadata Value
Description
on
Read tags of supported entities as metadata (default). TAG
off
Do not read tags.
@Transform402form16 Value
Description
on
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.
The reader attempts to traverse group entities (default).
off
References to entities within a group are ignored.
@TrimRevolvedWithModelSpaceCurves Value
Description
on
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).
off
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).
@TrimWithModelSpaceCurves Value
Description
on
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.
off
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).
@TrimWithPreferredRepresentation Value
Description
on
The reader attempts to create the boundary definition using 2D or 3D curves, based on the preferred representation provided by entity type #142. This
option can be overridden by either @TrimRevolvedWithModelSpaceCurves = on or @TrimWithModelSpaceCurves = on. off
(default)
@UseAnsys128Format Value
Description
on
The reader attempts to read Ansys NURBS surface format.
off
(default)
@vendors Value
Description
List of vendor names
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: @.