HyperMesh 8.0 User's Guide

HyperMesh 8.
0 User's Guide
HyperWorks
Altair Engineering Contact Information

Web site FTP site www.altair.com Address: ftp.altair.com or ftp2.altair.com or http://ftp.altair.com/ftp Login: ftp Password: <your e-mail address>
Location
North America China France Germany India
Telephone
248.614.2425 86.21.5393.0011 33.1.4133.0990 49.7031.6208.22 91.80.6629.4500 1.800.425.0234 (toll free) 39.800.905.595 81.3.5396.1341 81.3.5396.2881 82.31.716.4321 46.46.286.2052 44.1926.468.600 55.11.4223.5733 64.9.413.7981 64.9.413.7981
e-mail
hwsupport@altair.com support@altair.com.cn francesupport@altair.com hwsupport@altair.de support@india.altair.com
Italy Japan Korea Scandinavia United Kingdom Brazil Australia New Zealand
support@altairtorino.it support@altairjp.co.jp support@altair.co.kr support@altair.se support@uk.altair.com br_support@altair.com anzsupport@altair.com anzsupport@altair.com
The following countries have distributors for Altair Engineering: Mexico, Romania, Russia, South Korea, Singapore, Spain, Taiwan and Turkey. See www.altair.com for complete contact information. 2007 Altair Engineering, Inc. All rights reserved. No part of this publication may be reproduced, transmitted, transcribed, stored in a retrieval system, or translated to another language without the written permission of Altair Engineering, Inc. To obtain this permission, write to the attention Altair Engineering legal department at: 1820 E. Big Beaver, Troy, Michigan, USA, or call +1-248-614-2400.
Trademark and Registered Trademark Acknowledgments

Listed below are Altair HyperWorks applications. Copyright Altair Engineering Inc., All Rights Reserved for: HyperMesh 1990-2006; HyperView 1999-2006; OptiStruct 1996-2006; HyperStudy 1999-2006; HyperGraph 1995-2006; HyperGraph 3D 2005-2006; MotionView 1993-2006; MotionSolve 2002-2006; HyperForm 1998-2006; HyperXtrude 1999-2006; HyperOpt 1996-2006; HyperView Player 2001-2006; Process Manager 2003-2006; HyperWeb 2002-2004; Data Manager 2005-2006; Templex 19902006; Manufacturing Solutions 2005-2006 All other trademarks and registered trademarks are the property of their respective owners.

HyperMesh 8.0 Users Guide

Starting and Configuring HyperMesh
Hardware and Operating Systems ......................................................................................1 Starting HyperMesh .............................................................................................................2 Starting HyperMesh Batch Version .....................................................................................5 Start-up Options ...................................................................................................................6 Configuring HyperMesh.......................................................................................................7 Configuration File Commands .............................................................................................9 Start-up Files ......................................................................................................................21 Specifying a Temporary File Directory ..............................................................................21
HyperMesh Database and Environment

HyperMesh Database Design............................................................................................22 Database Names ...............................................................................................................22 Using and Saving a Database...........................................................................................22 Nodes .................................................................................................................................22 Fixed Points .......................................................................................................................22 Free Points .........................................................................................................................22 Collectors ...........................................................................................................................23 Elements ............................................................................................................................27 Lines ...................................................................................................................................30 Surfaces and Faces...........................................................................................................32 Systems..............................................................................................................................33 Loads..................................................................................................................................33 Cards..................................................................................................................................33 Vectors ...............................................................................................................................33 Title.....................................................................................................................................34 HyperMesh Environment ...................................................................................................35 Pull-Down menus...............................................................................................................37 Graphics Area ....................................................................................................................39 Toolbar Area ......................................................................................................................40 Header Bar .........................................................................................................................44 Main Menu Area.................................................................................................................46 Page Menu .........................................................................................................................46
Altair Engineering
Proprietary Information of Altair Engineering
HyperMesh 8.0 Users Guide i
Tab Area.............................................................................................................................47 Model Browser ...................................................................................................................48 Include Browser .................................................................................................................57 Modules ..............................................................................................................................63 Loadsteps Browser............................................................................................................64 Loadsteps Browser: Optistruct & Nastran profiles ............................................................65 Panels ................................................................................................................................69 Sub-panels .........................................................................................................................70 Input Controls.....................................................................................................................71 File Browser .......................................................................................................................77 The Mouse .........................................................................................................................79 Rapid Menu ........................................................................................................................81 Keyboard ............................................................................................................................82 Secondary Menu ................................................................................................................86 Utility Menu ........................................................................................................................87 BOM comparison tool ........................................................................................................95 Quick TetraMesh..............................................................................................................112
User Profiles
User Profiles.....................................................................................................................127 HyperMesh User Profile...................................................................................................128
Using HyperMesh
Using HyperMesh ............................................................................................................128 Retrieving and Saving a HyperMesh Database ..............................................................129 Picking Entities on the Screen .........................................................................................130 Picking Nodes on Geometry or Elements .......................................................................132 Using the Extended Entity Selection Menu .....................................................................133 Viewing Models ................................................................................................................137 Using the disp (display) Panel .........................................................................................140 Setting View Options........................................................................................................142 Setting Tolerances ...........................................................................................................145 Setting Global Parameters...............................................................................................145 Importing and Exporting Data ..........................................................................................146 Printing Screen Images ...................................................................................................148 Using the Card Previewer................................................................................................150
ii HyperMesh 8.0 Users Guide
Altair Engineering
Building Models
General Process for Building Models ..............................................................................151 Creating Collectors ..........................................................................................................152 Reading Geometry...........................................................................................................153 Creating Geometry Data ..................................................................................................154 Temporary Nodes ............................................................................................................158 Picking Surfaces ..............................................................................................................158 Editing Surfaces ...............................................................................................................159 Associativity .....................................................................................................................161 Geometry Cleanup ...........................................................................................................162 Building Elements ............................................................................................................164 Checking Model Quality ...................................................................................................167 Applying Loads.................................................................................................................168 Creating Systems.............................................................................................................169
Automatic 2-D Mesh Generation

Automatic Mesh Generation ............................................................................................170 Using the Automeshing Secondary Panel.......................................................................172 Mesh Generation Algorithms ...........................................................................................173 Smoothing Algorithms......................................................................................................175 Element Biasing ...............................................................................................................176 Linked or Locked Edges ..................................................................................................179
Connectors
Connector Entity...............................................................................................................180 Connector Terminology ...................................................................................................181 Connector Definition ........................................................................................................185 Connector Realization......................................................................................................187 Connector Review............................................................................................................188 Connectors User Control Mode .......................................................................................188 Master Connectors File....................................................................................................189 Multiple Weld File Format ................................................................................................190 Import Templates .............................................................................................................191 FE Configuration File .......................................................................................................193 FE Definition Examples ...................................................................................................197
Altair Engineering
HyperMesh 8.0 Users Guide iii
HyperMorph and Morphing Strategies

HyperMorph Strategies ....................................................................................................199 The Three Basic Approaches to Morphing......................................................................201 Space Frame Model Strategies using Global Domains ..................................................220 Shell Model Strategies using Local Domains ..................................................................237 Solid Model Strategies using Local Domains ..................................................................263
Calculating Beam Properties

HyperBeam Module .........................................................................................................272 Example of the Three-Step Process................................................................................274 Cross-sectional Properties as Calculated by HyperBeam ..............................................279 HyperBeam Environment.................................................................................................282 Section Browser...............................................................................................................283 Shell Section Graphics Pane...........................................................................................284 Results/Spreadsheet Pane..............................................................................................285 HyperBeam Menu Bar .....................................................................................................287 HyperBeam Toolbar .........................................................................................................294 Beam Cross Section Property Solver ..............................................................................296 Describing Cross Section Planes, Axes, and Elements..................................................297 Defining a Cross Section .................................................................................................298 Post-Processing of Beam Cross Sections: Applying Calculated Properties .................300 Defining a Prop/Comp Card for a Solver .........................................................................301 Beam Cross Section Questions and Answers ................................................................303
HyperLaminate and Composites

HyperLaminate Module....................................................................................................304 HyperLaminate Environment ...........................................................................................305 HyperLaminate Menus .....................................................................................................306 HyperLaminate Toolbar ...................................................................................................308 Laminate Browser............................................................................................................309 Define/Edit Pane ..............................................................................................................313 Review Pane ....................................................................................................................323
iv HyperMesh 8.0 Users Guide

Altair Engineering
Finite Difference Module

Finite Difference Module ..................................................................................................324 Creating a Finite Difference Block...................................................................................324 Creating a Structured Mesh.............................................................................................325
Boundary Conditions
Loads on Geometry .........................................................................................................327 Terminology and Definitions ............................................................................................328 Application of Loads to Geometry ...................................................................................329 Exporting Loads ...............................................................................................................330 Visualization of Loads on Geometry and Loads on Mesh ..............................................330 Distributed Load Mapper .................................................................................................331 Load an input file containing CFD analysis results .........................................................333 Load a structural analysis model (in OPTISTRUCT, NASTRAN, ABAQUS, or ANSYS input file format) ...............................................................................................................334 Select a data type and a mapping method......................................................................334 Set the scale factor ..........................................................................................................334 Set the mapping algorithm ...............................................................................................335 Mathematical Loading......................................................................................................336
Post-Processing and XY Plots

Post-Processing Analysis ................................................................................................338 HyperMesh Results Database.........................................................................................338 Specifying the Results File ..............................................................................................339 Creating Deformed Geometry Plots ................................................................................339 Creating Animations.........................................................................................................339 Creating Vector Plots .......................................................................................................340 Creating Contour Plots.....................................................................................................340 Creating Assigned Plots ..................................................................................................340 Adding Plot Identification .................................................................................................341 Inspecting the Results......................................................................................................341 XY Plotting .......................................................................................................................342 XY Plots Module...............................................................................................................343 Creating an XY Plot .........................................................................................................344 Modifying an XY Plot........................................................................................................344 Working with Multiple XY Plots ........................................................................................344
Altair Engineering
HyperMesh 8.0 Users Guide v
Modifying Multiple XY Plots .............................................................................................344 Creating Curves on XY Plots ...........................................................................................345 Modifying Curve Attributes...............................................................................................347 Displaying Selected Curves on Plots ..............................................................................347 Using the Curve Editor.....................................................................................................348
AutoDV
AutoDV Introduction .........................................................................................................351 Generation of Perturbation Vectors.................................................................................352 Manual Perturbation.........................................................................................................352 Polynomial Perturbation Vectors .....................................................................................353 Primary Domain Model ....................................................................................................353 Primary Domain Node Sets .............................................................................................354 Control Perturbations .......................................................................................................355 Secondary Domain Models and Node Sets ....................................................................357 Harmonic Perturbation Vectors .......................................................................................359 Generation of Variable Loads ..........................................................................................361 Running AutoDV Stand-alone .........................................................................................363
H3D Writer
Creating an H3D File from HyperMesh ...........................................................................365 H3D FAQ's .......................................................................................................................369
Free Body Diagrams

Free Body Diagrams........................................................................................................370 FBD Set Manager ............................................................................................................371 FBD Displacements .........................................................................................................375 FBD Forces ......................................................................................................................378 FBD Cross-section manager ...........................................................................................381 FBD Resultant Force and Moment ..................................................................................383 FBD Results Manager......................................................................................................386 FBD Export Manager .......................................................................................................388 FBD Grid Point Force Balance ........................................................................................390
vi HyperMesh 8.0 Users Guide

Altair Engineering
Hardware and Operating Systems

HyperMesh is not tied to a specific set of computer hardware or operating system and presents the same appearance on all platforms. Most of the HyperMesh source code is independent and can be compiled on various systems. However, a small portion of source code that controls the graphically oriented operations, such as drawing a line on the screen, needs to be "ported" to each hardware platform on which HyperMesh runs. The following hardware platforms are currently supported: Pentium-based PC or compatible running Windows WIN NT 4.0, WIN 2000/XP. IBM running AIX 4.3.3, 5.1, or 5.2. HP-PARISC (HPUX) running 11.0 or 11.11. HP-ITANIUM (HPUX_IA32) running 11.23. Silicon Graphics family of workstations running IRIX 6.5.11 m and IRIX 6.5.13 m. SUN workstations running Solaris 2.8. LINUX running RH 7.3 or RH 8.0.
For more specific information concerning your hardware/software configuration, or information concerning future platforms, please contact your HyperMesh sales representative. In general, HyperMesh has an identical appearance and behavior on all platforms. Some platforms may have limitations or extensions, depending on their level of sophistication. All UNIX ports are built around OpenGL.
Notes for PC Users

If you are running Windows NT (depending on model size or processor speed) you may wish to turn the full drag option off, which prevents HyperMesh from redrawing immediately when a destructive windowing operation is performed. This option is found in the Desktop icon in the Control Panel group.
Altair Engineering
HyperMesh 8.0 Users Guide 1
Starting HyperMesh
This section explains how to start HyperMesh on UNIX, Windows 2000, and Windows XP platforms. You can create a start-up file or alter the HyperMesh configuration file, hm.cfg, to have HyperMesh start and run according to the standards and preferences of your particular work site. Note: For more information about creating and using start-up files, see Start-up Files. For more information about the hm.cfg configuration file, see Configuring HyperMesh.
Starting HyperMesh in UNIX

This section contains the instructions and optional arguments for starting HyperMesh on a UNIX workstation. To start HyperMesh: 1. 2. Go to the directory from which you want to run HyperMesh. At the operating system prompt, enter the full path of the HyperMesh script (e.g., <altair_home>/altair/scripts/hm) and press the ENTER key. Or Create an alias for HyperMesh in the user .alias or .cshrc file in the user home directory. For example, add the following line in the .alias or .cshrc file: alias hm /homes/applications/hm8.0/altair/script/hm Once an alias is created, enter hm at the command prompt to invoke HyperMesh. Note: See Startup Options for more information about the startup arguments you can use.
2 HyperMesh 8.0 Users Guide

Altair Engineering
Starting HyperMesh on PC
During installation, an Altair HyperWorks group is created in Programs on the Start menu. The default working directory specified by the HyperMesh icon is the Windows default My Documents directory. Since HyperMesh creates user files, you may wish to change this directory. Note: See Startup Options for more information about the startup arguments you can use.
To start HyperMesh: 1. 2. From the Start menu, click Start and choose Programs. From the Altair HyperWorks group: select HyperMesh. or Click the HyperMesh icon on the desktop.
HyperMesh starts and the main menu is displayed on the screen. 3. By default, a window opens prompting you to choose a user profile.
The user profiles window is also accessible from the view pull-down menu. Uncheck always show at startup to prevent this window from opening each time you load HyperMesh. 4. Choose the desired user profile and then click OK. User profiles affect the HyperMesh layout as well as features such as element quality checks. 5. To exit HyperMesh, click quit. The quit button is located on the upper right-hand corner of the panel area on any of the main menu pages.
Altair Engineering
To change the working directory: 1. Right -click the HyperMesh icon on the desktop. or Locate and right-click the HyperMesh executable file in the altair/hm/bin directory. 2. 3. 4. Select Properties. Select the Shortcut tab. After Start in:, enter the name and path of the directory in which you want to run HyperMesh. Your user files, command.cmf and hmmenu.set, are created in this directory. To change/use startup options: 1. Right -click the HyperMesh icon on the desktop. or Locate and right-click the HyperMesh executable file in the altair/hm/bin directory. 2. 3. Select Properties. Select the Shortcut tab. The path to the HyperMesh executable displays after Target:. 4. Append the startup options to the path listed in Target:. For example, if you do not want HyperMesh to write a command file, enter -nocommand after the HyperMesh path. 5. Click Apply.

Altair Engineering
Starting HyperMesh Batch Version

HyperMesh batch version (hmbatch) allows you to invoke HyperMesh in batch mode at the command line and run a command file. Since this batch version does not have graphical display, HyperMesh commands that require display (e.g. plot, fit, create, postscript, etc.) are ignored. To start HyperMesh batch version on UNIX: 1. 2. Go to the directory from which you want to run HyperMesh. At the operating system prompt, type hmbatch ccommand.cmf and press ENTER. command.cmf contains the HyperMesh commands to be executed. To start HyperMesh batch version on PC: 1. 2. 3. 4. 5. 6. Right -click on the hmbatch icon on the desktop. Locate and right-click on the hmbatch(.com) executable file in the /hm/bin directory. Select Properties. Select the programs tab. After Cmd line:, the path to the hmbatch executable is displayed. Append the option, ccommand.cmf, to this path. Click Apply. Note: See Start-up Options for more information about the start-up arguments you can use. hmbatch terminates when it reaches the end of the command file or when it encounters *quit( ) in the command file.
Altair Engineering
Start-up Options
You can enter arguments after the hm command that allow you to specify which command file to run, pre-set export paths, change screen resolutions, or to print messages. The format of the command is: hm [ -version ] [-h] [-m] where: -version -h -m Display the current version. Print this message. Write the mouse commands to a mouse.msf file
Other options that can be specified after the start-up command allow you to specify model or results files or run command or mouse files. These options include: fl.hm -c<filename> -continue Read the HyperMesh file, fl.hm. Automatically run the specified command file. Always continue on error when processing a command file. Do not prompt via a pop-up box. Set the text input field in the export panel to the specified file. Automatically load the specified HyperMesh binary file. Plays back the mouse commands in the mouse.msf file. Forces HyperMesh to run in the foreground. Prevents HyperMesh from creating or writing to the command.cmf file. Causes HyperMesh to draw nodes to the PostScript file as circles. Otherwise, nodes are not drawn. Sets the name of the HyperMesh results file database to either the input filename with a .res suffix, or the specified file. Use the results file, res (-r alone specifies the file fl.res). Opens the application in a window of the specified width and height in pixels (PC only). Allows Templex within command files. Sets the global template file to the specified file. Causes HyperMesh to pause on the title splash screen until you press a key on the keyboard. Start HyperMesh under a specific user profile: for example, -uAnsys to start HyperMesh under the Ansys user profile. Allows you to write a master hmmenu.set file to replace the installed hmmenu.set.
-e<filename> <filename> -mmouse.msf -nobg -nocommand -psdhm
-r[filename]
-rres -s<width><height>
-templex -t<filename> -titlepause
-u<profile>
-writemastermenu

Altair Engineering
Configuring HyperMesh
HyperMesh has a default configuration file named hm.cfg, which is read on start-up and is located in the <install_directory>/hm/bin/ directory. The hm.cfg file controls certain aspects of how HyperMesh runs at your particular site. You can edit the commands in the hm.cfg file to save your preferences. Each of the hm.cfg commands begins with an asterisk and is followed by a set of parentheses that enclose a variable number of arguments. A command can be turned into a comment by removing the asterisk (*) preceding the command. The commands are not sensitive to location in the file. They may begin in any column, with each command occupying one line, or all of the commands may be on one line. The following commands are an example of a partial hm.cfg file: *menufont(2) *titlefont(3) *graphicfont(1) Note: HyperMesh accesses the configuration file, hm.cfg, only on start -up. If the hm.cfg file exists in multiple directories, HyperMesh uses the following order of precedence: PC customization path current (local) directory installation directory
UNIX current (local) directory home directory installation directory All running copies of HyperMesh must be restarted before any changes to the hm.cfg file are acknowledged. The commands in the hm.cfg file allow you to: Specify an absolute pointing deviceabsolutepointer_configuration_command>Config Enable buttonbuttons_configuration_command>Config and dialdials_configuration_command>Config input Specify default translatorsfeinput_default_configuration_command>Config and templatesfeoutput_default_configuration_command>Config Specify the default solversregistersolver_configuration_command>Config Specify default graphicsgraphicfont_configuration_command>Config, menumenufont_configuration_command>Config, and titlestitlefont_configuration_command>Config fonts Specify the default legend colorlegendcolorfile_configuration_command>Config Specify a color to use for entities with no resultsnoresultcolor_configuration_command>Config Change cursor sizebigcursors_configuration_command>Config Turn element and geom handlesnopickhandles_configuration_command>Config off by default Indicate to HyperMesh the method for sending PostScript files to a PostScript printerpostcopy_configuration_command>Config Indicate to HyperMesh the method for sending black and white PostScript filespostcopyblackandwhite_configuration_command>Config to a PostScript printer
Altair Engineering
Note:
Indicate to HyperMesh the method for sending ASCII files to a PostScript printerprintfile_configuration_command>Config Specify how to create a PostScript file of the screenpostfile_configuration_command>Config that can be viewed later or sent to a hard copy device Specify how to create a bitmap file of the screenscreenfile_configuration_command>Config that can be viewed later or sent to a hard copy device Indicate to HyperMesh the method for creating bitmap files Set reverse video when your printer cannot be set to reverse black and white. Set the screen size Specify the colormap version Set the default graphics simplification mode Tells HyperMesh to load the 3D Writer Specify the input translator and component format Specifies which font should be used from the X Lib fonts available on your system Display the Utility menu when HyperMesh starts Include intermediate (not just the final choice) rotation commands There is another configuration file stored in "My Documents" on the Windows platform and in ~/.altair on Unix and Linux, called hmsettings.tcl. HyperMesh uses this file to record various GUI settings for each user, such as tab locations (left/right/both/none), tabs which are visible (e.g. model or include browser), key bindings, recent files imported and recent files loaded. HyperMesh creates this file automatically when upon exiting the program. Hmsettings.tcl should not be edited and its format will change between releases. However, deleting this file can restore your HyperMesh settings to the default state if you encounter problems within the HyperMesh user interface that you cannot rectify by any other means.
Customization paths
You can store configuration files in a file path other than the ones to which they are installed by default. This prevents them from being overwritten when you install a new HyperWorks update. However, in order to use configuration files stored in a different file path, administrators must set up an environment variable called HW_CONFIG_PATH to specify the path. Multiple paths can be specified as variable values within this variable name. The configuration files which can be used in conjunction with customization paths are: hm.cfg file userpage.mac file hmmenu.set file Cadreader.ini files, such as catia.ini, iges.ini, or ug.ini Fatigue.cfg file hmexec file feconfig.cfg file hyperlaminate,cfg file Any printer settings (which may also exist in hm.cfg). hmcustom.tcl file

Altair Engineering
Configuration File Commands

The following is a list of the configuration commands that you can use to control how HyperMesh runs at your particular site: *absolutepointer() Use this command if you have a digitizing tablet or any other type of absolute pointing device. (An absolute pointer usually has six buttons.)
*bigcursors() Informs HyperMesh that pointing cursors should be double-sized when they are displayed on the screen. You can also change the cursor size by selecting large or standard under cursor size: on the menu config sub-panel in the options panel. *boldmenufont () Description Syntax To force the menu font to bold on windows. *boldmenufont(state) state 1 = bold 0 = use current value
Comments
The menu system in HyperMesh, under Windows, uses the font that is specified for the desktop icon text. This command allows you to force the menu system to use a bold font.
Altair Engineering
*buttons() Informs HyperMesh that your system is equipped with buttons that are used to perform viewing rotations or translations in 3-D mode. This command is currently used only by the Silicon Graphics and HP 700 family of workstations. In this case, if the *buttons() command is not added to the configuration file, HyperMesh does not respond to button input. Dynamic rotations and translations are always available in the menu. *controlkeyviewmode() Specify whether display listing should be done during control key assisted viewing. Syntax *controlkeyviewmode(mode) mode Note: 0 = immediate mode 1 = use display listing (default)
When display listing is used, there may be a delay in the operation while the display list is being built, but the operation will have a higher frame rate (faster). Immediate mode results in a faster initial response time, but a lower frame rate (slower).
*ce_fe_orientaxis() This command is called from the HyperMesh configuration file to specify the axis of the system that needs to be aligned in the direction of FE during connector realization. A value of 1 (default) to the function aligns the Y-axis of the coordinate system in the direction of FE and a value of 0 defines Xaxis and a value 2 defines Z-axis. See *CE_FE_SetDetailsandRealize() for information on creating a coordinate system during realization. *dials() This command informs HyperMesh that your system is equipped with dials that are used to perform viewing rotations or translations in 3-D mode. This command is currently used only by the Silicon Graphics and HP 700 family of workstations. In this case, if the *dials() command is not added to the configuration file, HyperMesh does not respond to dial input. Dynamic rotations and translations are always available in the menu (See *buttons()). *dynamicrotatemode() Sets mode for output of intermediate rotation commands. Syntax Arguments Example *dynamicrotatemode(mode) mode Set to 1 or 0.
When mode is set to 1, the following output is generated: *dynamicviewbegin() *quatrotate(-0.00785649346,-5.7397916e005,0.00228960797,0.999966514) *quatrotate(0.00994070323,0.00170778765,0.0047803938,0.999937705) *quatrotate(-0.00529684395,0.000673180986,0.000802068982,0.999985423)

Altair Engineering
*quatrotate(0.000230328525,0.00100703597,0.00106667981,0.9 99998898) *quatrotate(-0.00263644785,0.000327769044,0.000395387048,0.999996393) *dynamicviewend()
When mode is set to 0, the following output is generated: *viewset(-0.722177, -0.299006, 0.657815, -0.575689, 0.213868, -3.756111, -8.703590, Comments 0.761037, 0.623743, 0.485656, 0.612440, 0.000000, 0.000000, 0.000000, 1.000000, 8.621393)
5.964252, -3.030465, 2.583235, 0.886445,
When the mode is set to 1, intermediate *quadrotate() rotation commands are output to the command file. Otherwise, only the finial position is output, reducing the size of the command file.
*enablemacromenu() This specifies whether or not the macro Utility Menu should display when the program loads. By default, the Utility menu is displayed. 0 = off; 1 = on (default). You can display or hide the utility menu from within HyperMesh by selecting Utility Menu from the View pull-down menu. *feinputdefault() Informs HyperMesh which translator in the import/CUSTOM sub-panel is the default. Syntax *feinputdefault(filename)
Arguments
entity_type
The name of any file found in the feinput directory, or a symbolic name for the translator.
Comments
A symbolic name begins with a '#' character followed by the specification of the translator. The specification contains two parts separated with a '\'. The first part is the type of translator and the second part is a specific version of the translator. The symbolic name for each translator is listed below:
Altair Engineering
FE: #abaqus\abaqus #ansys\ansys #cmold\cmold #moldflow\moldflow #nastran\nastran #patran\patran #marc\marc #optistruct\optistruct #ls-dyna\dynakey #ls-dyna\\dynaseq #pamcrash\pamcrash #ideas\ideas #autodv\autodv #stl\stl #hmascii\hmascii GEOM: #catia\catia #iges\iges #ug\ug_16 #ug\ug_15 #stl\stl #vdafs\vdafs #hmascii\hmascii
WELD: #spotweld\spotweld *feoutputdefault() Informs HyperMesh which template is the default. This command requires one argument which can be set to the name of any file found in the template/feoutput directory.

Altair Engineering
*forceoldmenufonts () To force the menu font to the old style. Syntax Note: *forceoldmenufonts() The menu system in HyperMesh, under Windows, uses the font that is specified for the desktop icon text. This command allows you to force the menu system to use the historical fonts.
*graphicengine() Sets the default graphics mode. This option can also be set using the engine: toggle in the graphics sub-panel of the options panel. Syntax *graphicengine(mode) mode 0 = standard graphics 1 = performance graphics
*graphicfont() Informs HyperMesh which size font should be used to display numbers, element handles, and legends in the graphics area. This command requires one parameter ranging from 1 to 4 where 1 is the smallest font available and 4 is the largest font available (default = 2). The font size may also be changed during a HyperMesh session using the menu config sub-panel in the options panel. *graphicsimplificationmode() Sets the default simplification mode for performance graphics. Syntax *graphicsimplificationmode(mode, style, curComp) mode 0 = none 1 = automatic (default) 2 = Ctrl-Shift 0 1 2 3 4 5 = no simplification = feature lines (default) = bounding box = node cloud = element centroid = simplified shading
style
curComp 0 = do not simplify current component (default) 1 = simplify current component Note: If mode = 0, style and curComp are not required. The default simplification mode for performance graphics can also be set in the graphics subpanel in the options panel, where: mode is set using view acceleration and when view acceleration is set to automatic or Ctrl-Shift, style is set using the simplification style switch and curComp is set using the simplify current comp check box.
Altair Engineering
*legendcolorfile() Informs HyperMesh which legend color file should be the default. This command requires one argument that can be set to the name of any file found in the <install_directory>/hm/colors directory. Syntax legendcolorfile(file)
*legendsetbordercolor() Allows you to set the border color. Syntax *legendsetbordercolor(color) Comments *menufont() Informs HyperMesh which size font should be used to display the menu. This command requires one parameter ranging from 1 to 4 where 1 is the smallest font available and 4 is the largest font available (default = 2). The font size may also be changed in the menu config sub-panel in the options panel. *nopickhandles() Informs HyperMesh that you wish to have element and geometry pick handles off by default. Pick handles will be turned off when HyperMesh is started and turned off whenever a new file is loaded, if this command is specified. This improves graphic performance; however, 0-D elements (such as contact slave elements and mass elements) cannot be seen easily. The element and geometry pick handles can be set in the modeling sub-panel of the options panel. *noresultcolor() Elements or nodes for which no results were found are assigned a color (default = gray) to distinguish them from an actual 0 result. The color assigned to these no result entities is specified in the hm.cfg file. You can copy this file into your home directory and customize many of the default settings. The default color is specified with *noresultcolor(R,G,B), where R, G, and B are the intensity values for Red, Green and Blue. The default gray color values are *noresultcolor(80,80,80). Other colors include: dark blue (0,0,128), black (0,0,0), white (255,255,255), or khaki (210,175,100). You can experiment with the values in the color sub-panel of the options panel. *postcopy() Informs HyperMesh how to send a PostScript file to a PostScript capable printer. This command links the PostScript capability of HyperMesh and allows plots of the currently displayed screen to be printed directly from HyperMesh. The command requires one parameter, a character string closed in double quotes "". The string is sent to the operating system and should be the standard command which you would use to send a PostScript file to a PostScript capable printer. For example, if you want to send a file named junk to the printer using the command postprt junk, then you would use *postcopy("postprt junk"). The only information unknown at startup is the name of the file. To circumvent this, HyperMesh provides a way to access the name of the file when printing. Before sending the string parameter provided in the *postcopy() command to the operating system, it replaces the characters *filename with the appropriate name. The complete *postcopy() command of the above example is *postfile("postprt *filename"). Note that the file name junk was replaced with the characters *filename. If your system requires several commands to send a file to the printer, you may use a script file in UNIX or a batch file in DOS with the name of the file as a parameter to perform printing. For testing purposes, *postcopy() is invoked when you press CTRL-F3. The color must be between 1 and 64, inclusively

Altair Engineering
*postcopyblackandwhite() Identical to the *postcopy() command, but allows you to use a different command to send a black and white PostScript file to a printer. For testing purposes, *postcopyblackandwhite() is invoked when you press CTRL-F5. *postfile() Sends the currently displayed screen to a PostScript file. Provided for consistency with the *screenfile() and *screencopy() commands. In general, the string parameter required is set to a zero length string. *printfile() Informs HyperMesh how to send an ASCII file to a printer. This command requires one parameter, a character string closed in double quotes, "". The string provided is sent to the operating system and should be the command which you normally use to send a file to a printer. If you want to send a file named junk to the printer using the command print_it junk, use *printfile("print_it junk"). The only information unknown at start-up is the name of the file. To circumvent this, HyperMesh provides a way to access the name of the file when printing. Before sending the string parameter provided in the *printfile() command to the operating system, it replaces the characters *filename with the appropriate name. The complete *printfile() command of the above example is *printfile("print_it *filename"). Note that the file name junk was replaced with the characters *filename. If your system requires several commands to send a file to the printer, you may use a script file in UNIX or a batch file in DOS with the name of the file as a parameter to perform printing. For testing purposes, *printfile() is invoked in the summary panel on the Post page. *rapidmenus() The rapid menu functionality for the middle mouse button may be turned off with this command. Syntax Argument *rapidmenus(mode) mode 0 1 Comments Disable rapid menus. Enable rapid menus.
This command is only used in the command file. By default, rapid menu functionality is enabled. Disabling it may be desirable if you use the middle mouse button for other (e.g. O.S./non-HyperMesh) tasks.
*register3dwriter() Tells HyperMesh to activate the H3D writer. PC Users: *register3dwriter({bin_dir+"/hm3dwriter31.dll"},"Hyper3Dwrite","Hyper3D") UNIX Users: *register3dwriter({bindir+"/hm3dwriter3.1"},"Hyper3Dwrite", "Hyper3D")
Altair Engineering
*registersolver() Informs HyperMesh which solvers are available and how to invoke them. This command allows you to set up and customize the solver panel in HyperMesh. This command takes several arguments: Syntax *registersolver({solver},"{home}\ {solver}","*solver *input file *output file *options","infile:input file","outfile:output file","value:options") solver The name that you want to appear on the toggle in the solver panel. The name of the solver executable file. A character string that is passed to the operating system to invoke the solver, after substituting the user-input parameters. A character string that is of type file or value, depending on the expected input. Each character string represents an input field. The number of strings is identical to the substitutable fields in the third argument. Example *registersolver(OPTISTRUCT, optistruct, "*solver *input.fem *memory in MB, > *output.out", "file:input", "value:memory in MB", "file:output")
Arguments
This command creates a solver panel with four user-input fields; one for the solver executable, one for the input file name, one for the memory in MB, which is a value, and one for the output file name. The third parameter undergoes the substitution with the user-input values. *solver is replaced by the solver executable name. *input is replaced by the input file (the extension is always .fem.) *memory in MB is replaced by the value. *output is replaced with the user-selected output file (the extension for output file is always .out). A maximum of six fields are allowed per solver. The solver field can be of type value or file. *reversevideo() Informs HyperMesh that before the strings provided as parameters in the *screencopy() and *screenfile() commands are sent to the operating system, the colors representing black and white should be reversed. This command is necessary only if the hard copy device on your system is not reverse video capable. Reverse video can also be set in the postscript sub-panel of the options panel. *screencopy() Tells HyperMesh how to create a temporary bitmap file of the screen and send it to a hard copy device. A file named sliden.sdp is created by HyperMesh, where n is an incremental number provided for file name uniqueness. Functionally, it is very similar to the *printfile() command. On UNIX platforms, a site-specific operating system utility is called to create and spool the image to the printing device. By default, a file is created but not spooled to the print device (the CTRL-F1 and CTRL-F2 keys function identically) and you must click the active HyperMesh window to trigger the screen capture. The status bar indicates when the screen grab is complete. For more information on spooling bitmapped files directly to the printer, contact your systems administrator.

Altair Engineering
*screenfile() Informs HyperMesh how to create a bitmap file of the screen that can be viewed later or sent to a hard copy device (such as a printer). A file named sliden.sdf is created by HyperMesh, where n is an incremental number provided for file name uniqueness. Functionally, it is very similar to the *printfile() command. On the PC, HyperMesh generates a *.bmp file that can be read into wordprocessing programs. On UNIX platforms, a bitmap file is generated using the utility defined in the *screenfile() function (typically xwd) and output to a unique file using the same process as above. After you press CTRL-F2, you must select the HyperMesh window to indicate which window to capture. A message on the status bar indicates when the screen capture is complete. The name of the file can be accessed with the characters *filename. For more information about creating bitmap screen images, contact your system administrator. *screensize() Informs HyperMesh of the physical size of your monitor. The command requires two parameters in real format separated by a comma. The first parameter is the horizontal (x) dimension of the screen. To determine this value, measure the horizontal dimension of the usable portion of the screen excluding any borders in the default window that HyperMesh creates (or the entire screen if your system does not use windows). The second parameter is the vertical (y) dimension of the screen. To find this value, follow the same method as described above and measure the vertical dimension of the screen. The units used are not important but must be consistent. The *screensize() option changes the aspect ratio of the images drawn in the graphics area. If you use a wide aspect ratio screen, the length/width ratio of the objects may be distorted. Circles may look like ovals. When *screensize(14.75,8.30) is implemented, although the look of HyperMesh doesnt change, the proportions of the objects is corrected. The numbers are physical measurements of the display area of the screen (width, height). Note: in some cases, even after specifying the screen measurements the display can still appear distorted. In such cases, change the two values to any numbers that have the same aspect ratio of the screen resolution that you use. For example, if your desktop runs at a resolution of 1920 x 1200 pixels (an aspect ratio of 1.6), *screensize(1200,1920) should allow HyperMesh to render undistorted images. Remember that the command parameters represent height and width respectively, while screen resolutions are typically listed width by height; thus, its important to remember to use the correct order for the command (e.g. height, width). *setcolor() Set a colormap entry for each of the entity colors. Syntax *setcolor(index, red, green, blue) index red green blue Specifies the color location. (1 through 64) The colors red component. (0 through 255) The colors green component. (0 through 255) The colors blue component. (0 through 255)
Altair Engineering
*setcomponentformat() The first parameter of this command specifies which feinput translator you would like to use, while the second parameter specifies the format you want your components to follow when importing them to HyperMesh. Currently, only the ANSYS feinput translator supports this command. Example: *setcomponentformat(ansys, "TYPE%t-MAT%m-REAL%r<-SECID%s>-ESYS%e") %t %m %r % <> %e Place the type number here. Place the material number here. Place the real number here. Place the section ID number here. Symbols mean that everything encapsulated between the two symbols is displayed only if the element uses a section ID. Place the element coordinate system number here.
Here are some examples of what the component above will show: TYPE3-MAT2 -REAL2-ESYS2 TYPE1-MAT1 -REAL1-ESYS0 TYPE2-MAT2 -REAL3-SECID1-ESYS0 The following characters can be used to customize the name of the components: A-Z, a-z, 0-9, spaces, and the following: ~ ! @ # $ % ^ & * - ( ) _ = + \ | [ ] } ; : / ? . , *setlightsource() Set direction of the global light source. Syntax *setlightsource(x, y, z) x y z Comments X axis location, horizontal direction of screen. Y axis location, vertical direction of screen. Z axis location, in/out of screen.
This command may be used in either the hm.cfg file or from a command file. The default setting is 0.0, 0.0, 1.0, which represents lighting the model as you are looking at it.

Altair Engineering
*setperformancenormalmode() Set the performance graphics normal mode. Syntax *setperformancenormalmode(mode) mode Comments 0 = flat normals (default) 1 = smooth normals
This command can only be used in the configuration file.
*setspecularity() Set the global specular highlight values for performance graphics mode. Syntax *setspecularity(red, green, blue, shininess) red green blue The red component of the reflected light (range 0.0 1.0) The green component of the reflected light (range 0.0 1.0) The blue component of the reflected light (range 0.0 1.0) The shininess value. The higher the value, the smaller and brighter the highlight (range 0 128)
shininess
Comments
This command may be used in either the hm.cfg file, or from a command file. Specular reflection from an object produces highlights. The amount of specular reflection seen depends on the location of the viewpoint. It is brightest along direct angle of reflection.
Example
Settings may be used to simulate different materials: Glass *setspecularity(1.0,1.0,1.0,128)
Plastic *setspecularity(0.7,0.7,0.7,64) Lead *shadingquality() Shaded geometry visualization sometimes does not follow the actual geometry; this usually occurs in models that are large in one direction, but small in another direction. Add or modify the *shadingquality(N) command in the hm.cfg file (where N is a number between 1 and 10; 5 is the default). Raising or decreasing shading quality by 1 roughly doubles or halves the quality. Note, however, that N does not need to be an integerdecimal values are acceptable. After altering this value you must restart HyperMesh to see the changes. *setspecularity(0.5,0.5,0.5,32)
Altair Engineering
*sharedcolormap() Informs HyperMesh which colormap method should be used in the X version. The X version of HyperMesh requires a 256 color palette. On some platforms, the system colormap does not have 256 colors available. With a shared colormap, some colors in HyperMesh may not be available and appear as black. A non-shared colormap can be used, but may cause the rest of the systems colors to change when the HyperMesh window is active and HyperMeshs colors to change when the window is not active. *titlefont() Informs HyperMesh which font size should be used to display titles. This command requires one parameter ranging from 1 to 4 where 1 is the smallest font available and 4 is the largest font available (default = 2). Note that the font size may also be changed in the titles panel on the Post page. *xfontname() Informs HyperMesh which font should be used from the X Lib fonts available on your system. In general, the configuration file should have the appropriate fonts for your system. However, if your system is unique or if HyperMesh warns about one of the default fonts, the *xfontname() command must be modified. This command requires two parameters. The first parameter indicates which of the four HyperMesh fonts is being assigned. This parameter may range from 1 to 4. The second parameter is a string which locates the X Lib font which you want to assign to the HyperMesh font. This string may contain wild card, *, characters in the name. To assist you in determining the best X Lib font to assign to HyperMesh, the X Lib utilities are usually distributed with a program called xfontsel. This program, or a similar one, displays the possible X Lib font sets interactively.

Altair Engineering
Start-up Files
HyperMesh allows you to create a start-up file that can be used to either execute a series of commands or to define global parameters. The file must be a HyperMesh command file and is named .hmexec on UNIX systems and hmexec on Windows systems. When HyperMesh is invoked, it looks for this file and then processes the commands within the file. The directories searched include your customization path (if one is set up), the directory where HyperMesh is installed, your home directory (where your home directory is assumed to be specified in the environment variable, HOME), and the directory from which HyperMesh was invoked. Start-up files allow you to automatically define global parameters for the current session of HyperMesh. To create a start-up file: 1. 2. 3. 4. 5. Delete the command.cmf file, if it exists. Start HyperMesh. Execute any task that you want the start-up file to automatically perform when HyperMesh opens. After you have generated all of the necessary commands, quit HyperMesh. Rename command.cmf to the file name particular to your system, .hmexec or hmexec.
Although start-up files may contain any of the commands considered valid in a command file, be aware that if you create entities in the start-up file, problems may arise if you later want to rerun the command.cmf file created during your HyperMesh session. All commands executed by the HyperMesh command processor are written to the command file command.cmf, including those generated by your start-up file. If you rerun the command.cmf file when HyperMesh is started, it generates the entities specified in the start-up file, and then generates the same entities as specified by the command.cmf file, the commands which were written when the start-up file was executed initially. To avoid this problem, you can either not generate any entities in the start-up file, or delete the start-up file commands in command.cmf before you run it.
Specifying a Temporary File Directory

You can set the environment variable to control where temporary HyperMesh files are created. If the environment variable is set, then the temporary files are created with an HM prefix in the referenced directory. To set the environment variable in UNIX: SETENV TMPDIR <directory path> To set the environment variable in Windows: 1. 2. 3. 4. 5. On the Control panel, double click the System folder. Select the Environment tab. Click the TMP line under User variables for ... Edit the text after Value: to specify the correct path to the directory in which you want temporary files created. Click OK.
Altair Engineering
HyperMesh Database Design

A HyperMesh database stores information about many different entity types. All HyperMesh entities, including nodes, points, lines, elements, loads, and systems, are organized within collectors. There are several types of collectors and each collector stores the model data relative to its type. Note: See Database Names for more information about naming conventions. See Using and Saving a Database for more information about saving HyperMesh files.
HyperMesh entities include:
Database Names
There are no restrictions placed on HyperMesh database names other than those imposed by the operating system. However, at Altair we use the extension .hm for all HyperMesh binary databases. This convention allows you to determine easily which of the files in a directory are HyperMesh databases.
Using and Saving a Database

While you work on a model, HyperMesh copies the database into system memory. The original database does not change until you save the model. If you exit HyperMesh without saving the current database, all the changes that you have made during your work session are lost. HyperMesh prompts you for confirmation before you exit, if the current database has been modified but not saved.
Nodes
The node is the most basic finite element entity. Nodes represent physical positions on the structure being modeled and are used by the element entity to define the location and shape of the element. Nodes are considered "used" if they are part of an element, vector, or group, or are referenced by a card image. HyperMesh automatically deletes from the database unused nodes and any loads that were attached to the unused nodes. Nodes contain a pointer to a surface and are therefore associated to a surface. This allows you to select nodes and elements by surface.
Fixed Points
A point is a zero-dimensional geometry entity. A fixed point is associated with a surface and is labeled with a small "o". Fixed points may appear anywhere on a surface. The automesher always places nodes at fixed points. Vertices along the edges of a surface are always marked by fixed points. Fixed points are displayed in the same color as the surface to which they belong.
Free Points
A point is a zero-dimensional geometry entity. Free points are not associated with a surface and are labeled with a small "x." 22 HyperMesh 8.0 Users Guide
Altair Engineering
Collectors
A collector gathers related data and allows you to handle the data as one unit. All entities within HyperMesh must belong to a collector. HyperMesh automatically creates a collector for new entities if you do not create a collector first. Entities can belong to only one collector; for example, an element cannot exist in two different collectors. Collectors can be modified and the entities within them can be reorganized. You can quickly change the active collector by clicking the current collector information in the header bar. This opens a menu that displays the currently selected collector of each type, and includes buttons that allow you to choose a new collector:
The buttons next to the collector names access a selection menu. Note: Collector names are limited to 160 characters. For more information about reorganizing collectors, see the organize panel. Note: Use the display panel to control the screen display of the collectors in your model.
Component Collectors Components are collectors that contain element, line, and surface data. This allows you to organize geometry data into units that can be translated, rotated, assigned colors, or deleted. Operations performed on a component affect all the elements, lines, and surfaces that belong to the component. Component collectors also retain property and material information about the entities that belong to it. All the elements in a component collector are assigned the same properties and materials except when the elements have a property reference. In this case, the elements are assigned properties from the property which they reference. Lines, elements, and surfaces cannot exist unless a component collector exists. If you have not created a component first, HyperMesh automatically creates a component, auto1, for those entities. You can use the collectors panel to modify the attributes of the auto1 component and the rename panel to change the name. Group Collectors Groups are collectors that are restricted to certain types of elements. This restricted access lets HyperMesh translate special collections of entities as a unit and allows it to support advanced features of analysis codes. Configurations 1-4 are created in the interfaces panel. Configuration 5 is created in the rigid wall panel.
Altair Engineering
Assembly Collectors Assemblies are collectors that contain several components organized into a single logical unit. After an assembly is created, you can select and display all the components that belong to it by selecting the assembly. Operations performed on an assembly do not affect the components in the assembly. For example, if you delete an assembly, the components in the assembly are not deleted. Components can belong to more than one assembly. Entity Information Collectors These collectors maintain information about the entities assigned to them: Property Property collectors contain property information about 1-D elements and are required only when a model contains one or more of the following elements: bar2 bar3 gap joint masses rod spring
After you create a property collector, you can assign the specified properties to new 1-D elements by entering the collector name after property = when you create or update the elements. Properties for all other element types, 2-D or 3-D, are assigned by the component to which the elements belong. Material Material collectors contain information about the materials in a HyperMesh model. If a model contains any non-rigid elements, then the model should have at least one material collector. You can set a component or property to the correct material collector by entering the collector name after material =. A plot collector contains information associated with an xy plot. One plot collector is created for each plot in the database. Plot collectors contain pointers to curve collectors. Curve collectors contain information about the curves of an xy plot. This information includes the name and color of the curve and the line style used to display the curve. A curve is referenced by selecting the plot collector. Block collectors contain information relating to a finite difference block, including its walls and cells. See the Finite Difference Module section for more information.
Plot
Curve
Block

Altair Engineering
System Collectors System collectors allow you to organize local coordinate systems. A system collector can hold any number of systems, which allows you to access a group of systems as a unit. Note: A system cannot exist unless a system collector exists. A system can belong to only one system collector. If no collector has been created prior to the creation of systems, then HyperMesh creates one called auto1.
Load Collectors Load collectors allow you to organize loads. Typically, a load collector contains loads that are to be applied at the same time, simulating a system loading condition. The method by which loads are organized may depend on the analysis code that is used to solve the problem. Note: A load cannot exist unless a load collector exists. A load can belong to only one load collector. If no collector has been created prior to the creation of loads, then HyperMesh creates one called auto1.
Vector Collectors Vector collectors allow you to organize vectors. A vector collector can hold any number of vectors, which allows you to access them as a unit. Note: If no collector has been created prior to the creation of vectors, then HyperMesh creates a collector called auto1.
Sets Collectors Set collectors contain lists of entity IDs, which can be composed of specified elements, nodes, or components (each set can contain only one type of entity). Additional information that can be included in sets are the name of the set and the type of entity contained within the set. Output Blocks Some solvers allow you to request output results for specific nodes or elements. The output blocks entity is used to store these nodes, elements, components, systems, groups, or materials. Load Steps The load steps entity allows you to select a set of load collectors. Typically, the set of load collectors represents a system loading condition.
Multibody Collectors
Setting collector type to multibodies in the collectors panel provides functionality for the creation and modification of multibody collectors. Multibody collectors serve multiple purposes: Organizing HyperMeshs ellipsoids, mbplanes, and mbjoints entities. Hold and define rigid body properties for multi-body analysis. Provide the rigid body reference for ellipsoids, cylinders, and planes.
Altair Engineering
Create a Multibody Collector

The create sub-panel is used for creating multibody collectors. create provides four data blocks for defining: the collectors name, card image type, center of gravity, and the bodys local coordinate system. Moments of inertia and other rigid body properties are defined in the multibody collectors card image, which is access through the card panel after the multibody collector has been created. The name= text field is provided for specifying a name for the multibody collector being created and for reviewing the names of already existing multibodies. The name= field supports names up to 160 characters in length. 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 in the global panel. 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 to be assigned at the time of creation but one can be assigned later in the card image sub-panel. 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 within HyperMesh and only effect data being exported. 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 HyperMesh. 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 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, 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 sub-panel (options panel) allows you to display the center of gravity for multibody collectors and text labels for 1D elements.
body local system: defines the body local coordinate system of the created body by assigning a local coordinate system entity to the multibody collector. There are three ways to define the bodys orientation. body system assigns a copy of the local coordinate system assigned to the current multibody collector specified in the global panel. duplicate system ensures a unique coordinate system is assigned to the created body by creating a duplicate of the selected coordinate system and assigning this duplicated coordinate system to the created body. use system assigns the selected system to the created body.
Update a Multibody Collector

The update sub-panel is provided to modify the bodys local coordinate system and center of gravity. The same fields and options available in the create sub-panel are also available in the update subpanel. To modify the name of a multibody collector, the rename panel is available in the far left column of every HyperMesh page.
Define, Change, Review, and Reset a Multibody Collector

The card image sub-panel is used to define, change, review and reset the multibody collector type. The multibody types available are based on the template loaded in the global panel.

Altair Engineering
Elements
Each element entity performs a specific task to facilitate a controlled and complete interface between HyperMesh and the analysis codes. If a model uses only the basic element types, i.e., trias, quads, and rigids, HyperMesh can transfer the model to several different analysis codes. In modeling situations where specific analysis codes are used because of their unique capabilities, the model is not considered generic and does not transfer between analysis codes. Each element has two associated variables: an element configuration and an element type. The element configuration tells HyperMesh how to draw, store, and work with the element. The element type allows you to define multiple analysis elements for each HyperMesh element.
Element Configuration
The element configuration defines the physical geometry (i.e., quad, hex) of the element. Element configurations include:
Altair Engineering
Element Type
Defines the category of the element, which allows the template, or output translator, to distinguish between the different types. Examples of different types of quads within ABAQUS are S4R and S4R5. The template file HyperMesh uses to write the analysis deck recognizes the different element types and outputs them as configured. For example, if an analysis code has two different quad elements and you wish to use both in a model, assign type1 to the first type of quad element and type 2 to the second type of quad element. Note: For more specific information about using the HyperMesh templates, refer to Template Design.
Supported Element Types

HyperMesh supports the following element configurations: Bar2 Bar3 Gap Hex20 Hex8 Joint 2-noded bar element with property reference, local vector, or orientation node, offsets, and pin flags (configuration 60). 3-noded bar element with property reference, local vector, or orientation node, offsets, and pin flags (configuration 63). 2-noded gap element with property reference and vector (configuration 70). 20-noded brick solid element (configuration 220). 8-noded brick solid element (configuration 208). 2-, 4-, or 6-noded element with 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 (configuration 22). Type 1 2 3 4 5 6 7 Mass Master3 Master4 Penta15 Penta6 Pyramid5 Type Name Spherical Revolute Cylindrical Planar Universal Translational Locking # nodes 2 4 4 4 4 6 6 Orientation none/systems/nodes none/systems none/systems none/systems none/systems none/systems none/systems
1-noded mass element (configuration 1). 3-noded master interface element (configuration 123). (Must be Type 1.) 4-noded master interface element (configuration 124). (Must be Type 1.) 15-noded wedge solid element (configuration 215). 6-noded wedge solid element (configuration 206). 5-noded pyramid solid element (configuration 205).

Altair Engineering
Pyramid13 Plot Quad4 Quad8 RBE3
13-noded pyramid solid element (configuration 213) 2-noded plot element used for display purposes (configuration 2). 4-noded quadrilateral shell element (configuration 104). 8-noded quadrilateral shell element (configuration 108). Multi-noded element with one dependent node and a variable number of independent nodes. Each node contains a coefficient (weighting factor) and a user-defined degrees of freedom (configuration 56). 2-noded rigid element with user-defined degrees of freedom (configuration 5). Multi-noded element with one independent node and a variable number of dependent nodes. The independent node has user-defined degrees of freedom (configuration 55). 2-noded beam element with property reference (configuration 61). 1-noded slave interface element (configuration 135). (Must be Type 1.) 3-noded slave interface element (configuration 133). (Must be Type 1.) 4-noded slave interface element (configuration 134). (Must be Type 1.) 2-noded spring element with user-defined degrees of freedom, an orientation vector, and a property reference (configuration 21). 10-noded tetrahedral solid element (configuration 210). 4-noded tetrahedral solid element (configuration 204). 3-noded triangular shell element (configuration 103). 6-noded triangular shell element (configuration 106). 2-noded rigid element (configuration 3).
Rigid Rigidlink
Rod Slave1 Slave3 Slave4 Spring Tetra10 Tetra4 Tria3 Tria6 Weld
Altair Engineering
Lines
The line entity in HyperMesh represents the geometry associated with a physical part. A line can be composed of a single line type or multiple 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 from CAD data are not attached to surfaces, and their color is determined by the status of the component. Under certain conditions, such as when you are working within the spline , ruled, or line drag panels, you can use surface edges as free lines. However, their color is determined by the surfaces to which they belong. All lines in HyperMesh are represented mathematically with the following formulations: straight elliptical NURBS Note: Used to represent a straight line between two points in space. Used to represent conics such as a circle, ellipse, or parabola. Used to represent lines that are not straight or elliptical. NURBS (non-uniform rational B-spline) may also be used to represent a straight or elliptical line, but are then less efficient. NURBS can exactly represent the piecewise parametric cubic splines they replace, as well as many other types of curves. By using elliptical segments or NURBS segments, circles can be represented exactly in HyperMesh.
An edge is a trim line of a surface. You can use surface edges as a line in most panels. Surface edges include: Free A free edge (displayed red) is a surface edge that belongs to a single surface which does not have other surfaces aligned with it within the specified cleanup tolerance. A shared edge (displayed green) is a surface edge that is shared between exactly 2 surfaces. Nodes are placed along this edge during automeshing and recognized during meshing of bordering surfaces. A shared edge cannot be changed back to a free edge. Suppressed edges (displayed blue dotted) are the internal face edges within a surface. Suppressed edges allow the mesh to flow across or over these boundaries. No nodes are placed along a suppressed edge. A suppressed edge can be changed back to a shared edge. These edges (displayed yellow) are shared by more than two surfaces. These edges usually indicate a collapsed or very thin surface or a fully or partially duplicated surface. Non-manifold edges can be turned into shared edges by deleting one of the attached surfaces.
Shared
Suppressed
Non-Manifold /Duplicate

Altair Engineering
The following panels can be used to create lines: circles fillets intersect lines section surface tangents
The following panels can be used to change lines: delete line permute position project reflect reparam rotate scale translate
Altair Engineering
Surfaces and Faces

The surface entity in HyperMesh represents the geometry associated with a physical part. Surfaces define 2-D regions that may be used in automatic mesh generation. All surfaces in HyperMesh are represented mathematically with the following formulations: plane cylinder/cone sphere torus NURBS Used to represent a planar surface. Used to represent cylindrical or conical surfaces. Used to represent a spherical surface. Used to represent a toroidal surface. Used to represent surfaces which are not definable by the above surface types. NURBS may also be used to represent the above surface types but they are not as efficient.
A HyperMesh surface can be made of a single surface type or of multiple surface types. Multiple types are used for more complex surfaces that contain sharp corners or highly complex shapes. Each surface type is referred to as a face. 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. The following panels can be us ed to create surface entities: surfaces primitives midsurface
The following panels can be us ed to change surface entities: defeature permute position reflect rotate scale surface translate

Altair Engineering
Systems
The system entity, commonly called a coordinate system, may be rectangular, cylindrical, or spherical. Several systems may be nested. In HyperMesh, a reference system is used to define the geometric positions of entities, and an analysis system is used to transform the nodal coordinate system. Note: A system may be a reference system, an analysis system, or both.
Entities that have a reference system are systems, nodal points, loads, and mass elements. By default, each of these entities is defined in the global system with an ID of zero. You can use the systems panel to modify the reference coordinate system of an entity. Entities are always displayed in the transformed global system. HyperMesh allows you to modify the analysis system of an entity when you define the analysis system. The only entity that may be defined in an analysis system is a node. Analysis systems are typically used to transform element degrees of freedom or constrained degrees of freedom from the global system to a local system. If you delete a system, all the entities that were defined in that system are transferred to the global system. When a reference system is deleted, the position of the entity is maintained relative to the global system in the transformation process. For example, if you define a cylindrical structure in a cylindrical coordinate system, and then delete the system in which the nodes are defined, the model retains its cylindrical shape and also its location in space. When you delete an analysis system, you must set the proper orientation for element degrees of freedom or constrained degrees of freedom, as HyperMesh does not maintain these in the transfer from the local system to the global system.
Loads
The load entity allows you to add forces and constraints to the database. Loads are applied in the global system except when the reference system has been modified. A constraint, applied at a node, is placed in the global system only if a system does not exist at that node. If a system does exist, the orientation of the constraint is dictated by the local system. After a constraint has been applied, HyperMesh does not maintain the proper orientation for the constraint when you create or delete local systems at the node where the constraint resides. Constraints, concentrated forces, concentrated moments, concentrated fluxes, temperatures, velocities, accelerations, and pressures are currently supported.
Cards
The card entity allows you to create control cards such as CPU limits or Title cards. Control cards are defined within templates and are specific to one FE solver.
Vectors
The vector entity allows you to define a three dimensional vector in the database. Vectors are created in the global system unless a local coordinate system is defined. Additionally, vectors can be created between two nodes and can change magnitude and direction as those nodes move through analysis. Vectors can be used for orientation of spring and gap elements or to specify a direction during selection.
Altair Engineering
Title
Title collectors contain title information, including the name of the title, the color of the title, and the text displayed in the title.

Altair Engineering
HyperMesh Environment
There are several main areas in the HyperMesh window:
These areas are described below: title bar Located at the top of the HyperMesh window, this displays the current HyperMesh version. It also displays the path and name of the file currently open in the active HyperMesh session. A current file is determined with the following rules: Pull-down menus The last HyperMesh (.hm) file retrieved or saved in the active session FE or CAD import does not affect the current file Delete model clears the current file If no .hm model is retrieved or saved in the active session the current file field is empty
Located just under the title bar. Like the pull-down menus in many graphical user interface applications, these menus "drop down" a list of options when clicked. Use these options to access different areas of HyperMesh functionality.
Altair Engineering
Tab Area
Located on the left, right, or both sides of the graphics area, these sidebars display additional tools, such as the Utility menu or Include browser, in a tabbed format. Tab Area sidebars can be toggled on or off by use of the View pull-down menu, Tab Location sub-menu. Individual items (tabs) can be added to or removed from the Tab Area by selecting the item from the View pull-down menu. You can click-and-drag tabs to move them between the left and right Tab Area sidebars.
Graphics area Toolbar Area
Located above the tool bar(s): the graphics display area is where model geometry and mesh displays. Located just under the graphics area, these buttons provide quick access to commonly-used functions, such as changing display options. Depending on your display resolution and the number of buttons, this area may contain one toolbar, or two toolbars stacked vertically.
Header bar
Located between the main menu area and the toolbar area. It displays the name of the current panel and user profile, and model status information. Located across the bottom of the window. The main menu is divided into the panel area and the page list. You can type HyperMesh commands directly into this text box and execute them instead of using the HyperMesh Graphical User Interface. Secondary menus can be accessed by using keyboard shortcuts. The secondary menu allows you to use panels that add information necessary to complete the currently active panel.
Main menu Command Window secondary menu

Altair Engineering
Pull-Down menus
The pull-down menus, 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 File) "pulls down" a list of the options available in that menu:
Notice that there are two lists of options displayed in this screen shot; this is because some menu items have sub-menus of additional options. This approach sub-groups similar features together, rather than presenting every option in a single list (which could result in very long lists). Menu items can work in several different ways: Sub-Menu heading These items are marked with a triangular arrow. Selecting a submenu heading opens a sub-menu of options related to the submenu heading. This method allows similar commands to be grouped logically, and helps prevent any single menu list from becoming excessively long. When clicked, these items are marked with a checkbox and activate or deactivate a feature. One example is the solver browser item found in the view menu; clicking it alternates between showing and hiding the solver browser in one of the Tab Area sidebars. Most menu items simply execute a command when selected, such as accessing a specific HyperMesh panel.
Toggle
Command
Altair Engineering
There are multiple ways to select a pull-down menu or a menu item within it: Mouse Keyboard (menu) Click the menu or menu item with the mouse. First, press the alt key to activate the menu area. Then: Use the keyboard key indicated by the menu or item; these keys are underlined (as the "F" in the File menu).
or Use the left and right arrow keys to move among the menu headings, and the up and down arrow keys to open a menu and navigate among its options.
Keyboard (menu item)
Menu items can be selected with the keyboard in two ways: or Use the arrow keys to move among list of options, and press enter to select a highlighted option. Use the keyboard key indicated by the menu item; these keys are underlined (as the "O" in the Open).
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 load. To add extra models to your workspace, use import. To import multiple files, use the multiple files option in the import sub-menu.
Edit View Organize Geometry Mesh BCs Setup Checks Tools Applications Results Preferences Help
Tools for masking, deleting, or finding entities. Change the angle of view on the model, lighting, or visibility and location of tab area items, among other options. Tools for creating and renaming collectors, assemblies, etc. Tools for geometry editing and cleanup. Meshing tools, such as automesh, tetramesh, solid map, element edit, etc. Boundary Conditions such as forces, pressures, moments, or constraints. Model properties such as materials, connectors, and contact surfaces. Model quality checks, including element check settings. Morph, Rotate, Translate, Reflect, or Scale entities, among other options. Quickly access other HyperWorks programs, such as OptiStruct. View results of solved simulations (contour or vector plots, for example). HyperMesh preferences such as User Profiles, global options, and keyboard configuration. Access the on-line Help system.

Altair Engineering
Graphics Area
The graphics area occupies the upper portion of the screen. Models, geometry, and plots are displayed in this area. Entities on the screen are selected for use in functions by clicking the desired entity with the mouse.
The graphics area dominates the HyperMesh environment and is framed by all of the other interface areas. Note: See Entity Selection for more information about picking entities.
Altair Engineering
Toolbar Area
The functions on the toolbar allow you to manipulate the view of the model, control which collectors are displayed in the graphics region, set global modeling parameters, and edit solver-specific data. Note: In versions of HyperMesh prior to release 8.0, many of these functions were contained in the permanent menu. Users already familiar with earlier HyperMesh releases will find the same functionality that the permanent menu offered now located in the toolbars.
The toolbar uses two different groups of visual icons to represent different HyperMesh functions. Notice that the toolbar may display in one or two rows; the two-row configuration is shown above. Normally all of the buttons display on a single row, but when the toolbar is too narrow to hold all of the buttons, a group of buttons automatically moves to the second row. The toolbar buttons perform the following functions: Load, save, or import files. This accesses the files panel. Access the collectors panel. Right-click (or click the down-arrow) to access other collector functions: Create or update material collectors. Create or update property collectors. Create or update load collectors. Edit solver-specific data in card format. This only applies when a valid template file has been specified in the global panel. Turn the display of collectors on and off. This button accesses the display panel. Access the visual attributes panel. Use this panel to individually determine how each component of your model displays its FE mesh. Selects the element color style. For example, if you select "by comp", the model elements colors change based on the components that contain them. Other options include: By Prop: colors the elements based on their assigned properties; the property assigned varies based on the solver used. For example, the property color of shell elements (quads and trias) in a NASTRAN model is the same as the component, thus the shell elements are colored in component color even in this mode. But for 1D elements such as bars and springs, the property (PBEAM, etc) is assigned directly to the element. use the colors panel to change the colors of properties
Note:

Altair Engineering
By Mat: colors the elements based on the material assigned to the elements. In most cases, materials are assigned to elements via their components. Some exceptions apply. use the colors panel to change the colors of materials. 1D/2D/3D: colors 1D, 2D and 3D elements differently. All the 1D elements are colored in green, 2D shell elements in blue and 3D solid elements in red. By Config: colors elements based on their configurationbeam, bar, quad, trias etc. The individual colors given to each configuration (such as spring or hexa) can be seen and changed in the element types panel.
Note:
Switches the mesh rendering mode to wire-frame mode. Right-click (or click the down-arrow) to choose between skin-only and full wire frame (including internal lines). , Switches the mesh rendering mode to a shaded mode. Right-click (or click the down-arrow) to choose between mesh lines, feature lines, and no lines. Determines how geometry features are colored. For example, if you select "by component", then each piece of geometry is re-colored based on the component that contains it. Other coloring options include: Auto: In this mode the geometry coloring changes based on the panel you open. In panels geometry creation and editing panels (e.g. surface edit, automesh), geometry is colored based on topology. In the remaining panels (such as translate or delete), the geometry is colored based on its corresponding component. By Comp: Surfaces, lines, etc. are colored according to the components that they belong to. By Topo: In this mode, all the surface and solid edges are colored based on their topology: shared edges drawn in green, free edges in red, suppressed edges in blue, etc. If geometry shading is turned on, the faces of solids are also colored based on their topology: exterior bounding faces in transparent green, internal partition faces in yellow, etc. Surfaces that arent part of a solid are shaded in gray. By 2D Topo: In this mode, 2-dimensional geometry (i.e. surfaces) that is not part of a solid is colored based on its topology. The topology of 3D solid geometry is ignored (drawn in a single color that can be changed in the options panel). This helps you focus on 2D geometry in models that include both 2D and 3D entities. By 3D Topo: In this mode, 3-dimensional geometry (i.e. solid faces and their edges) is colored based on its topology. The topology of 2D geometry is ignored and drawn in a single color that can be changed in the options panel. This helps you focus on 3D geometry in models that include both 2D and 3D entities.
Altair Engineering
Mixed: This mode behaves similarly to Topology mode in that all the surface and solid edges are colored based on their topology, (shared edges in green, free edges in red, etc.) In addition, in shaded mode surfaces and solid faces are shaded in their components color.
, ,
Draws model geometry as a wire-frame. Click the downward arrow to choose between excluding and including surface lines. Draws model geometry in shaded mode. Click the downward arrow for options: with edges or without them. Opens the visualization pop-up panel. Returns to the previous view. This allows you to (for example) perform a free rotation on a model and then quickly return it to its original orientation, or to alternate between two different views. Resizes the model view (by zooming in or out and panning the view as needed) in order to fit the model to the graphics area. Modal Zoom; this works in one of two different ways: Left-clicking activates the circle zoom feature. Circle zoom deactivates after zooming once, or when you click either button while the pointer is in the graphics area. Right -clicking activates the dynamic zoom feature. Once active, right-click and drag in the graphics area to zoom in/out. Left-click to deactivate.
Either mode also deactivates when you move the mouse pointer outside of the graphics area. Zoom incrementally; left-click to zoom in, right-click to zoom out. Rotate modes: this functions in one of two different ways: Left-click to activate dynamic rotate mode. Once active, click-and-drag in the graphics area to rotate the model. Right -click to deactivate. Right -click to activate dynamic spin mode. Once active, right-click in the graphics area and hold the mouse button down to make the model spin. Left-click to deactivate.
Either mode also deactivates when you move the mouse pointer outside of the graphics area. Pan modes: this functions in one of two different ways: Left-click to activate pan mode. Once active, click-and-drag in the graphics area to pan the model view. Right-click to deactivate. Right -click to activate center mode. Once active, right-click in the graphics area to change the graphics area center. Left-click to deactivate.
Either mode also deactivates when you move the mouse pointer outside of the graphics area. 42 HyperMesh 8.0 Users Guide
Altair Engineering
Rotate Left or Right: this is similar to pressing the left and right arrow keys on the keyboard. Click the left mouse button to rotate the model leftward, and the right button to rotate it rightward. Rotate Up or Down: this is similar to pressing the up and down arrow keys on the keyboard. Click the left mouse button to rotate the model upward, and the right button to rotate it downward Spherical clipping: accesses the spherical clipping panel. Use spherical clipping to isolate portions of the model regardless of component or collector. Open a pop-up menu used to save and retrieve user-defined or standard views. Notes: See Viewing Models for more information about the viewing options available on the toolbar. You can use keyboard hot keys to access the same viewing options. See Keyboard for more information.
Altair Engineering
Header Bar
The header bar is located between the main menu area and the toolbar area. It displays information pertaining to the currently loaded model as well as descriptions of the main menu pages and panels. When you are on one of the main menu pages (not within a panel), the current include and current component (comp), along with the current menu page name (i.e., Geometry) are displayed.
You can quickly change the active collector by clicking the current collector information (e.g., comp:) in the message bar. This opens a menu that displays the currently selected collector of each type, and includes buttons that allow you to choose a new collector:
The buttons next to the collector names access a selection menu. The header bar also displays a brief description of the panel when you hold down the left mouse button on the panel button (see below).
When you are in a panel, the header bar displays the current panel title and model status. Panel titles display on the left side of the bar. If you access a panel by using a function key, the bar displays the current panel name on the left (in black) and the original panel name to the right (in gray). The current component and load collector names are displayed on the right side of the bar.
Messages also appear on the header bar and temporarily override the title and status information.

Altair Engineering
Messages posted on the header bar are color-coded: red green/gray Error messages. Miscellaneous messages, such as status updates or completed operations. You can also obtain a brief description of a panels function if you hold down the left mouse button over a panel button. These messages appear in green when using HyperMesh classic dark menu colors and they appear in gray when using Windows light menu colors
Click a mouse button to remove a message from the header bar.
Altair Engineering
Main Menu Area

HyperMesh functionality is organized according into pages, each containing a list of panels and modules. Most panels are further divided into sub-panels. Modules contain a collection of panels that are grouped according to functionality. A secondary menu can be accessed by using keyboard keys. The secondary menu allows you to use panels that add information necessary to complete the currently active panel.
Page Menu
HyperMesh panels are grouped by function on several pages. HyperMesh presents these pages in the page menu, which is located on the right-hand edge of the main menu area.
The page menu. Each of these pages contain panels related to the page name: Geom 1D 2D 3D Analysis Tool Post Creation and editing functions for geometry such as points, lines, or surfaces 1-D element creation, such as bars, masses, and spot welds Creation and editing functions for 2-D surfaces and elements Creation and editing functions for 3-D surfaces and elements Boundary conditions, coordinate system, and load creation functions. Model editing, utility functions, model checking functions, and informational functions. Post-processing and xy plotting functions.
To change main menu pages: Note: Click the radio button before the main menu page. If you are not using the default HyperMesh menu system, then the menu items described above may not appear on the appropriate pages. To correct this condition, quit HyperMesh, delete the file hmmenu.set from the directory you are working in (provided you are not working in the directory where HyperMesh is installed), and then start HyperMesh once again.

Altair Engineering
Tab Area
This area of the HyperMesh environment is actually two separate sidebars which flank the Graphics Area. However, each sidebar can be toggled on and off separately, so you might only see oneor even noneat a time. Turn the Tab Area sidebars on and off by selecting left side, right side, both, or none from the Tab Locations sub-menu of the view pull-down menu. Each Tab Area sidebar can contain multiple complex features, such as the utility menu, model browser, and/or the solver browser. To maximize available space, multiple features are organized onto tabs; click a tab heading to bring it to the forefront.
Altair Engineering
Model Browser
The model browser resides on a tab in a Tab Area sidebar and allows you to view the HyperMesh model structure by organizing assemblies, components, multibodies, properties, materials, entity sets, groups, load collectors, system collectors, vector collectors, and beamsectcols 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.
This screenshot shows all of the entities that can display in the browser.

Altair Engineering
Multiple entities of the same type are collected into folders in the tree structure. Each folder can be expanded or collapsed to display or hide its contents. Assemblies can also have sub-folders within the main Assembly folder, so that the items related to each assembly appear within that assemblys folder in the Assembly Hierarchy. Materials, properties, entity sets, groups, load cols, system cols, vector cols, and beamsectcols cannot be organized into assemblies and are all placed at the top level of the tree, each in their corresponding folder (for example all sets are placed as a flat list in the Sets folder). Components and Assemblies may appear in multiple places in the tree; for example, a specific component might appear under Components and again as a sub-item of a specific Assembly. When appropriate, the color and display style of entities also display in the model browser.
Check Boxes
Items are displayed or hidden by toggling the corresponding check boxes. The following rules apply: Checked entities (components, multibodies, groups, etc.) display; unchecked entities are hidden. Assemblies containing components or multibodies are considered displayed only when all of the contents are displayed. Activating an assemblys checkbox displays all of its contents. Activating an assemblys checkbox displays all its components and multibodies. Deactivating the check box for an assembly hides all of its components and multibodies. Deactivating the check box for an item hides all of its parent assemblies. Deactivating the check box for an item does not affect the state of its parent assembly. An empty assembly never displays; therefore it does not have a check box, and its state does not affect the state of its ancestors.
Colors
Assemblies, Components, Load Collectors, Materials, Properties, and System Collectors can all be colored individually, and the model browser allows you to set each entitys color without using the color panel. The currently assigned color displays in the column. To change an entitys color, right-click on the current color in the model browser. In this instance, the right-click menu contains only a single option: color. Select this to open the same color picker used throughout HyperMesh, 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.
Altair Engineering
Display Mode
Components, assemblies, and load cols 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 popup menu from which you can choose the new style. Depending on which option you select, the entity displays differently: Only a wireframe mesh displays. Only shaded topology displays (no mesh). Shaded topology displays with mesh lines. Shaded topology displays with feature lines, but no mesh. Transparent shaded topology displays without mesh. Multibodies, groups, system cols, and vector cols have only one display state and will be shown only in element mode.
Global Switches
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 (displaying the hidden and hiding the displayed) of all components, multibodies (not assemblies), groups, system cols, load cols, and vector cols; assemblies are unchecked only as needed. Since these functions work in combination with the filters, only the items displayed in the tree are affected. Note: These buttons only affect the display state. They do not actually remove entities from the modelonly show or hide them.
Global Sorting
You can sort the entities in a folder by clicking on the heading of the tree structure. 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.
Filtering
You can filter the entity types that appear in the browsers tree structure by using special buttons provided in the model browsers own toolbar. The first set of filters let you restrict the tree structure to display mesh entities, geometry entities, or both: Include mesh entities in tree structure. Click a second time to remove them. Include geometry entities in tree structure. Click a second time to remove them.

Altair Engineering
The next filtering tool is represented by a funnel icon ( ). This feature allows you to determine which categories of entity appear in the browsers tree structure. Clicking this icon adds a new list box to the browser, named Show: and located just below the browsers toolbar. Click this list box to open a list of all the entity types that HyperMesh can display in the tree structure. Each entity type in the list has a checkbox next to it; click the checkboxes to toggle the display of that entity type as a folder in the browsers tree structure. For example, the Components folder only displays in the tree structure if Components is checked in this list. In this way, you can make the tree structure shorter and easier to navigate by removing entity types from the browser list that you do not need to work with. Notice that the list of available entity types includes its own mini-toolbar, with the same buttons for Display All, Display None, and Reverse Display as described under global switches above. However, in this case they are used for Select All, Select None, and Reverse Selection. In addition, the list contains buttons labeled OK and Cancel. When you are satisfied with your selection of entity types, click OK to close the list. Otherwise, click Cancel to discard your changes and close the list without altering the model browsers tree structure. You can also select groups of entities based on a wildcard search. Accomplish this via the matching: combo text/list box. For example, if you type *collector into this combo box and press <enter>, then all entity types ending with collector will be checked and display in the list. Fine-tune the search/selection by choosing an option from the ( ) button:
Match case only selects tree items that match the entered text exactly, including upper/lower case letters. Whole name only selects tree items whose entire name matches the specified text. For example, typing pillar in the matching field when using the whole name option will not locate a component named CH-A-PILLAR-B-I-L.
Finding Entities
You can locate an entity by clicking the find icon, . This opens a new line of toolbar buttons in the model browser, composed of a combination text/list Find: box, an up-arrow button, a down-arrow button, and Options for searching (represented by a downward-facing double arrow).
Altair Engineering
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. HyperMesh will only find entities whose complete name matches what you typed into the Find: box, rather than only part of the name. In other words, if you type chassis into the Find: box, HyperMesh will ignore entities labeled chassis1, FrontChassis, or RearChassis1. Wildcards allow you to search for any items that partially match the text you are searching for. For instance, you could search for *pillar and find components named A-Pillar and B-Pillar. Note that using wildcards is generally not compatible with searching for whole names! By ID Using this option allows you to type an entity ID into the Find: box instead of a text-based name.
Whole Names
Use Wildcards
Note that these options are on/off toggles; clicking one activates it (represented by a checkbox in the list). To deactivate the option, select it again to remove the checkbox. In this way you can combine the search options, such as searching for whole names with matching case. To find entities matching your specified string and options, click the up or down arrow buttons to search upward or downward through the browsers tree. In this way, you can continue searching by repeat clicks of these buttons; for example, after clicking the down-arrow and finding the first match, you can find the next match by clicking the down-arrow again. When the find function reaches the bottom of the tree it will start over again from the top, until it has performed a single full loop from its starting point. So, for instance, if the tree contains three entities matching your search string, clicking the down-arrow button finds match #1; clicking again finds match #2; clicking third time finds match #3; clicking a fourth time reaches the end of the tree and starts over from the top, finding match #1 again. 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 (see Filtering above).
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 move or copy an item to the new location. If an assembly is moved or copied, all the items in the assembly are moved to the new location (items that are not seen in the tree due to filters are also moved). You can drag and drop multiple items at any time using the standard shift and ctrl keys. Note: If an item is dragged out of the tree and dropped onto empty space, it is deleted in all its parent assemblies and placed at the top level of the tree. A dragged item is added to the bottom of the list in an assembly.

Altair Engineering
Context Menu
Clicking the right mouse button on a folder or entity within the browsers tree structure allows you to change a variety of options. The options available depend on the entity that you right -click on. Options selected in an empty space apply to the entire model.
Option New
Available for: Assemblies, Components, Load Collectors, Materials, Plots, Properties.
Description A new assembly, component, or multibody can be created inside an assembly (activate the menu over 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, component, multibody, material, property, group, set, system col, load col, vector col, or beamsectcol can be created at the top level. 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.
Delete
All except the top-level of Assemblies
Rename
All
Any item can be renamed by entering a new name in the name text box. The new name must be unique. All instances of the renamed item will be automatically updated. You can cancel the rename operation by pressing ESCAPE or clicking anywhere outside the entry box before editing the existing name. Folders that contain materials, properties, sets, beamsectcols, system cols, load cols, vector cols, and groups cannot be renamed.
Altair Engineering
Edit Card
All
Any single item can be card edited. The card image of that entity for the solver template loaded will be displayed. If a template is not loaded or if the entity does not have any card images associated to the loaded template, the card editor is not invoked and the appropriate message is displayed. A component, card, multibody, or beamsectcol can be made current using the pop-up menu. The current component is designated with bold font. Closes all of the folders in the tree structure, so that only the top-most level of items displays. Opens all of the folders in the entire tree structure, exposing every item nested at every level. Display the item in the graphics area. This selects each affected items checkbox. You can also use this on the entire branch of groups, load collectors, components, materials, plots, and properties. In such cases, this shows all of the items within that branch (e.g. all groups, all materials, etc.)
Make Current
components, cards, multibody, beamsectcol All All Assemblies, components, groups, load collectors, plots, materials, properties, system collectors. Assemblies, components, groups, load collectors, plots, materials, properties, system collectors. Assemblies, components, groups, load collectors, plots, materials, properties, system collectors. All
Collapse all Expand all Show
Hide
Un-checks the items checkbox, so that the item no longer displays in the graphics area. You can also use this on the entire branch of groups, load collectors, components, materials, plots, and properties. In such cases, this hides all of the items within that branch (e.g. all groups, all materials, etc.)
Show Only
Deactivates the checkboxes of all items in the entire model browser except for this single item, so that only this item displays in the graphics area. Used to quickly and easily isolate single entities. You can also use this on the entire branch of groups, load collectors, components, materials, plots, and properties. In such cases, this hides everything except for the items within that branch. Opens the Model Browsers Browser Configuration window, which allows you to determine what entities display in the tree as well as the columns that the browser displays.
Configure Browser

Altair Engineering
Model Browser Configuration window

This window opens when you select the configure browser option from the Model Browsers context menu. Use this window to change the columns and entity types that display in the model browser.
Separate tabs organize entities and columns.
Entities Tab
To show all of the entity types that the currently-loaded model possesses, choose the radio button marked select all entity types in the current model. To select entity types manually, click the Entity types: radio button, and then activate the checkboxes next to each desired entity type. A checkmark indicates that the entity type will display in the browser. You can also use the select all, select none, and select reverse buttons in this mode.
Altair Engineering
Columns tab
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.
Command buttons
Once you finish configuring the browser, click one of the command buttons to close the window and return to HyperMesh: 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.

Altair Engineering
Include Browser
The include browser can be accessed by selecting include browser from the view pull-down menu. 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 browser is shown below.
The Master Model is at the top level of the include browser. 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. For example, in the above example, the include named dummy.dyn contains 55 vectors, 55 system collectors, 55 systems, 116 sets, 296 properties, etc. 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.
Altair Engineering
Global Switches
The Display All , Display None , and Reverse Display 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 (displaying the hidden and hiding the displayed) of all components, multibodies (not assemblies), groups, system cols, load cols, and vector cols; assemblies are unchecked only as needed. Since these functions work in combination with the filters, only the items displayed in the tree are affected. Note: These buttons only affect the display state. They do not actually remove entities from the modelonly show or hide them.
Global Sorting
You can sort the entities in a folder by clicking on the heading of the tree structure. Click the Entities heading to sort alphabetically by name. Multiple clicks toggle between ascending and descending order.
Filtering
You can filter the entity types that appear in the include browsers tree structure by using special buttons provided in the browsers own toolbar. The filtering tool is represented by a funnel icon ( ). This feature allows you to determine which categories of entity appear in the browsers tree structure. Clicking this icon adds a new list box to the browser, named Show: and located just below the browsers toolbar. Click this list box to open a list of all the entity types that HyperMesh can display in the tree structure. Each entity type in the list has a checkbox next to it; click the checkboxes to toggle the display of that entity type as a folder in the browsers tree structure. For example, the Components folder only displays in the tree structure if Components is checked in this list. In this way, you can make the tree structure shorter and easier to navigate by removing entity types from the browser list that you do not need to work with. Notice that the list of available entity types includes its own mini-toolbar, with the same buttons for Display All, Display None, and Reverse Display as described under Global Switches above. However, in this case they are used for Select All, Select None, and Reverse Selection. In addition, the list contains buttons labeled OK and Cancel. When you are 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 include browsers tree structure.
Finding Entities
You can locate an entity by clicking the find icon, . This opens a new line of toolbar buttons in the include browser, composed of a combination text/list Find: box, an up-arrow button, a down-arrow button, and Options for searching (represented by a downward-facing double arrow).

Altair Engineering
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. HyperMesh will only find entities whose complete name matches what you typed into the Find: box, rather than only part of the name. In other words, if you type chassis into the Find: box, HyperMesh will ignore entities labeled chassis1, FrontChassis, or RearChassis1. Wildcards allow you to search for any items that partially match the text you are searching for. For instance, you could search for *pillar and find components named A-Pillar and B-Pillar. Note that using wildcards is generally not compatible with searching for whole names! By ID Using this option allows you to type an entity ID into the Find: box instead of a text-based name.
Whole Names
Use Wildcards
Note that these options are on/off toggles; clicking one activates it (represented by a checkbox in the list). To deactivate the option, select it again to remove the checkbox. In this way you can combine the search options, such as searching for whole names with matching case. To find entities matching your specified string and options, click the up or down arrow buttons to search upward or downward through the browsers tree. In this way, you can continue searching by repeat clicks of these buttons; for example, after clicking the down-arrow and finding the first match, you can find the next match by clicking the down-arrow again. When the find function reaches the bottom of the tree it will start over again from the top, until it has performed a single full loop from its starting point. So, for instance, if the tree contains three entities matching your search string, clicking the down-arrow button finds match #1; clicking again finds match #2; clicking third time finds match #3; clicking a fourth time reaches the end of the tree and starts over from the top, finding match #1 again. Once the entity that matches the entered string is found, it is highlighted in the include 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 (see Filtering above).
Altair Engineering
Context Menu
A context sensitive pop-up menu provides many other include browser functionalities. Right click in the browser to invoke the following pop-up menu.
Function New
When function is active Permanently
Description Creates a new include. If a specific include is selected (highlighted), the new include is created within it. The new include is created at the top level inside the master model when no include file is highlighted while selecting this option. Deletes the selected include. Prompts the user with two choices: Delete the include file The first option moves all the contents of the include file into its parent include and deletes the include file. Delete the include file and its contents The second option deletes all the contents within the selected include along with the include itself.
Delete
When an include is selected
Rename
Converts the name of the include into an editable text box ready for the new name to be entered. Clicking on the selected (highlighted) include a second time also has the same effect. Makes the selected include "current". Thus any new entities created in HyperMesh such as new elements, contacts, components, etc. are automatically placed in the current include.
Make current

Altair Engineering
Move to current
When entities are selected
Moves all the selected entities (individual entities, the entire set of entities of a specific type, or an entire include) into the include that is marked as current. Allows you to set the various options for a selected include. The available options are: name file name to be exported (absolute path or path relative to its parent include) 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. Flag representing the section of the input deck that the include belongs in. This flag is specific to some solvers 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.
Include file options
Import include
Imports the content of a file into the selected include. Option prompts you to select a name and browse for the file to be imported. The contents of the chosen file are imported into include. Exports the contents of the selected include into the chosen file name. Exports all the includes with their corresponding content (not the master model only the includes). Collapses all the branches of the tree structure for the selected include. Expands all the branches of the includes tree structure along with the various entity type folders (such as comps, mats, etc.). Clears the graphics region of any previous display and displays all the entities that belong to the selected include.
Export an include Export all includes Collapse Include Expand include
When an include is selected Permanently
Permanently Permanently
Display only
When an include (or master model) is selected
Altair Engineering
Configure browser
Permanently
Opens a window that allows you to select which types of entities should be shown in the include browser. Two options are available: Select all entity types available in current model Displays all the entity types available in the current model (default). User selected entity types Allows you to select the entities that you want to display in the browser. Select from a list of all entities (except nodes and elements) in HyperMesh.
Edit card Enable/Disable
When a control card is selected When a control card is selected
Invokes the card image of the control card in the HyperMesh window. Allows users to enable (turn on and export) control cards that have been disabled and vice versa.

Altair Engineering
Modules
Panels that are used to perform related functions are sometimes grouped together in modules. For example, the module, xy plots located on the Post page, contains panels that allow you to read curves, edit curves, perform simple math on curves, and scale the axis of plots. A module may contain panels that are also found on the main pages, and are grouped to provide easy panel access without unnecessary navigational clicks. To select a module, locate the module button on one of the main menu pages and click the module button. Note: HyperMesh does not make any special distinction between modules and panels. The main difference between the module and a panel is the additional menu layer.
Altair Engineering
Loadsteps Browser
The Loadsteps Browser is used to create, manage and display HyperMesh 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. Note: For the 8.0SR1 release, OptiStruct (OS) and Nastran are supported within this framework. More profiles will be added in future versions of HyperMesh.
The Loadsteps Browser displays in its own tab in the tab area, but may not be active by default. Select it from the BCs Pull-Down menu to display its tab in the tab area.
Display Options
The display options lie in a toolbar at the top of the browser tab, and control the way that the data displays in HyperMesh (which is the default behavior) or exports (when the Export state button is active). Each control has its own function: Select all, select none, reverse selection Use these to select the items in the tree. You can also select individual items by clicking on them, or select multiple items by shiftclicking or control-clicking. Note that this changes the loadsteps export states, but not their visibility in the HM graphics area. This button acts as a toggle; it can be turned on and off. When activated, the display settings apply to export of loadsteps. When inactive, the settings apply only to the current display. For large models, keeping the browser in sinc with an actions taken within the rest of HyperMesh can require considerable processing time. To alleviate this, the Loadstep Browser does not automatically sync itself with the HM database. Instead, the Sync button becomes active whenever you make changes to the current HM database. This allows you to perform many operations inside HM without performance issues, and then sync the browser with one click. Filter buttons allow for additional selection control, including a name filter that uses HyperMesh standard filtering syntax. Use this feature to limit the tree to display only loadsteps whose names match a specific text stringeither partly or completely.
Export state
Sync browser
Filter
The main functionality of the Loadstep Browser varies depending on the active HyperMesh 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.

Altair Engineering
Loadsteps Browser: Optistruct & Nastran profiles

The browsers tree structure lists relevant control cards and loadstep information, organized into folders. There are many functions available, accessed by right-clicking on the tree background or on individual or multiple items. For the OptiStruct and Nastran profiles, these options include: New subcase Edit options Edit card Delete Rename Renumber BCs Contour Loads Summary Collapse all/selection Expand all/selection Auto-manage load references Create a new subcase, either from scratch or by creating an exact copy of an existing subcase. Depending on the entity selected, this will bring up an appropriate GUI for editing of the loadstep or control card information. Review the selected entity in the HM card editor. Delete the selected entity or entities. Rename the selected entity. Renumber the selected entity. This launches the BCs Contour utility and automatically selects the loadcols associated with the selected loadstep. This launches the Loads Summary utility and automatically selects the loadcols associated with the selected loadstep. Collapses all selected folders and subfolders, or all folders if none are selected. Expands all selected folders and subfolders, or all folders if none are selected. This option is for users who wish to have existing DLOAD, LOAD, MLOAD, MOTION, MPCADD and SPCADD cards auto-managed. This option creates a copy of loadcols with these card images and converts them into an auto-managed naming convention for easy editing/reviewing inside the Edit options popup. Opens the OptiStruct panel in HyperMesh.
OptiStruct
In addition, every loadstep listed in the tree has a small checkbox next to it as well as an export state indicator. You can click these to toggle them back and forth: The loadcols in the loadstep display in the HyperMesh graphics area. The loadcols in the loadstep do not display in the HyperMesh graphics area. This loadstep will not be exported. This loadstep will be exported. Note: When you first open the loadstep browser, all of the loadsteps in the model default to the blank (unchecked) state.
Altair Engineering
To create a new subcase: 1. Right -click anywhere in the Loadstep Browser and select New subcase. A pop-up window opens, allowing you to: 2. Type in a subcase name Select the same as option, then pick an existing subcase to base the new one on. When this option is active, the new subcase is an exact copy of the existing one.
Click create. Another pop-up window opens, allowing you to edit the subcase.
To edit a subcase: 1. Right -click on the desired subcase folder, or any subfolder in the Loadstep Browser, and select Edit options. Note: This step is skipped when you create a new subcase!
A popup window opens, allowing you to edit the subcase. The popup has several tabs to gather the relevant information. 2. 3. To activate an option, check the box next to the desired option and fill in the required fields. Depending on the Subcase Type, the list of appropriate Load References will change accordingly. 4. A tree structure lists the load references that are available for the selected subcase type. A bold reference signifies that the load reference is defined. A red indicator signifies that a load reference is mandatory for the subcase type and requires attention. A green indicator signifies that a load reference is mandatory for the subcase type and is defined.
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. Name filtering is available by using standard HyperMesh filtering syntax.
5.
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 HM database, a warning message appears to notify you. When importing a model into HyperMesh, it is possible that the subcase may reference loadcols that have not been imported (they are in a separate include file). In order to support this, the Add <unavailable> load reference ID option is available. This allows users to modify a subcase and add in references to loadcols that do not exist in the current model. These references are also listed in the right table with a warning message to notify you that the loadcol doesnt exist in the database

Altair Engineering
6. 7. 8. 9.
To remove a loadcol from the load reference, select the loadcol in the right table and use the left arrow to remove the loadcol. To select multiple loadcols, use the all/none/reverse buttons where appropriate. These buttons select loadcols from the currently active table. To remove a loadcol from the load reference, select the loadcol in the right table and use the left arrow to remove the loadcol. Right -click options allow for additional functionality depending on the current selection. The Add <unavailable> load reference ID option allows you to add a reference to a loadcol ID that does not currently exist in the HM database (as described in step 5).
To display a subcase: 1. 2. Check/uncheck the display checkbox next to the subcase of interest. Additional control is also available at both the Global Options and Subcase Load References level:
3.
Click the Display button at the bottom of the Loadstep Browser GUI. 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 subcase. You must determine the appropriate loadcols to check on/off depending on the subcase type. You can also launch the BCs Contour and Loads Summary utilities from the Loadstep Browser. The selected utility launches with the loadcols associated with the selected subcase automatically selected.
Note:
To rename, renumber, delete, or edit the card of a subcase: Right click on the appropriate subcase or loadcol. 1. 2. Select the desired option from the popup menu. For renaming and renumbering, an entry box appears so that you can enter the appropriate information in the browser.
To edit the Global Options of a subcase: Editing Global Options works exactly like editing a subcase, 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 subcases folder or sub-folder.
Altair Engineering
Loadsteps: Auto-manage load references This option is recommended for all users. In HyperMesh, 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 HyperMesh 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 subcase and at each load reference. If the load reference points to a loadcol with one of the card images indicated above, it will: Create a copy of that loadcol and assign it a new name, based on a fixed naming convention (auto<CARD IMAGE NAME>_#). For example, if a load reference pointed to an SPCADD loadcol, a new copy would be created and named autoSPCADD_1. Assign that new loadcol to the original load reference. (The original loadcol is not deleted or modified in any way.)
2.
Inside the Edit options popup, if a load reference points to a loadcol with one of the card images above and that loadcol has not been converted to the auto-managed naming convention, the loadcol will not be expanded or editable inside the GUI. The only way to modify the loadcol is via the card editor (right-click option from the editor GUI). Inside the Edit options popup, if a load reference points to a loadcol with one of the card images above and that loadcol has been converted to the auto-managed naming convention, the loadcol is expanded and editable inside the GUI.
If the loadcol selected for the load reference already has the card image assigned (for users wishing to manually manage their loadcols and point to an existing loadcol with one of the card images listed above) no additional action takes place. However, when appropriate, a loadcol is automatically created and assigned the correct card image when any of these conditions are met: More than one loadcol is selected for the load reference One loadcol is selected and the local scale factor is not 1.0 (DLOAD and LOAD) The global scale factor is not 1.0 (DLOAD and LOAD)

Altair Engineering
Panels
HyperMesh panels allow you to perform specific tasks by selecting options and entering variable data. Each panel has a unique title that describes the main function of the panel. Some panels contain several functions that perform similar tasks. Panels with multiple functions have sub-panels that display only those menu items that are relevant to the current operation. To select a panel, locate and click the panel button on one of the main menu pages. Note: To display a brief description of the function of a panel in the header bar, hold the mouse button down while the cursor is over the panel name. Release the mouse button to access the panel.
Each panel contains menu items that allow you to enter necessary information for the procedures you wish to perform. Note: Once a panel is active, press the "H" key or select HyperMesh and OptiStruct from the Help pull-down menu to display the help topic for the current panel. A description of the panel as well as instructions on how to use it display. If you press a function button and the data is incorrect or required information is missing, a message is displayed stating the error. You can also use the middle mouse click to advance through input collectors (yellow) or entry fields and then proceed to a function (green) or return (red). This behavior is called rapid menu. Using the middle mouse button allows you to make the required selections in the graphics region, advance to the next selection, and continue selecting or complete the operation, thus reducing mouse movement. You can press the ESC key or click return to exit a panel. Returning out of a panel means accepting what was performed on the model while using the panel. This cannot be rejected once the panel is exited.
Altair Engineering
Sub-panels
Sub-panel names are listed on the left side of the panel. Only one sub-panel may be selected at a time. For example, on the collectors panel there are three sub-panels: create, update, and card image or dictionary.
Collectors - create sub-panel.

Collectors - update sub-panel.
Collectors - card image sub-panel. To select a sub-panel, click the radio button next to the sub-panel name on the left side of the panel. Each sub-panel contains menu items that allow you to enter necessary information for the procedures you wish to perform.

Altair Engineering
Input Controls
The menu items on each panel indicate the information that is needed to correctly perform the panels function. Each panel contains input collectors, plane collectors, data entry fields, and function buttons. Most panels also have toggles and switches that allow you to alternate between choices or select options from a list. Menu items include: Menu Buttons The color of the menu button corresponds to its purpose: green yellow red Functions or executable items Collectors Return or abort
Toggles and Switches Toggles and switches appear on many HyperMesh panels. When you click a toggle, the menu item following it alternates between choices. When you click a switch, a list of options is displayed.
toggle
switch
In some cases, the list of options presented by a switch can be very long:
In these cases, HyperMesh breaks the options up into multiple pages within the switchs pop-up menu. The green arrow buttons on the right-hand edge of the pop-up menu advance or back-track through the list of options: << < > >> Go directly to the first page of the list. Step backward one page toward the beginning of the list. Advance one page toward the end of the list Go directly to the last page of the list
Altair Engineering
Input Collectors Input collectors allow you to indicate which entities are to be modified when a function is performed. An input collector contains a switch or toggle, a data type button, and a reset (|< ) button. An input collector is active when the data type button is enclosed in a blue rectangle.
Input Collector To change the data type, click the input collector switch to access the pop-up menu of possible data types, and select the type you want to use. In addition to selecting one entity at a time on the screen, you can select multiple entities via quick window selection (hold down the SHIFT key and drag your mouse to create a window. See The Mouse for more details). The extended entity selection window allows you to choose various methods of selecting entities of a specified data type. To access the options: Click the data type button.
The extended entity selection window opens, displaying a list of available selection methods.
Extended entity selection window. These selection options display for all of the entity types in HyperMesh. Selections that are not valid for the current entity type are grayed out. Note: For more information about the extended entity options, see Using the Extended Entity Selection Menu.
If you want to reset the entity selections, click the reset to deselect all selected entities. Note: If the data type is a line list, click the data type of the input collector to see the selected entities in the order in which they were selected. If the data type is a node list, you can click on the collector to access a pop-up with the selections by list, by path, show node order, or by window. by list by path Allows you to pick the nodes individually from the node list. Allows you to select a few nodes that form a path and HyperMesh selects all the displayed nodes that lie in the shortest path of the nodes selected. If you select nodes on the edges of a part, the function tries to find the closest path along the edges of that part. by path follows the connectivity of the elements between the nodes selected. Therefore, if the nodes selected are not connected by elements, this function does not apply. Allows you to view the nodes currently stored in the nodelist collector by numbering the nodes in the sequence of their selection. Allows you to select nodes by window and internally the order of the nodes selected is determined based on its spatial location and element connectivity (if connecting elements exist).
show node order by window

Altair Engineering
The linelist collector provides the following extended selection options: by list by path Allows you to select lines or surface edges individually in the desired sequence. Allows you to pick surface edges (two or more) and selects all the surface edges that fall in the closest path connecting the selected edges. If you select two free (red) edges, the function tries to find the closest path along the free surface edges. Since this function uses the connectivity of the surfaces, it only works with surface edges and not with free unconnected geometric lines.
Plane and Vector Selector Several HyperMesh panels require that you define a plane or a vector (direction) to perform a certain function. For example, the translate panel requires that you define the direction of translation, while the reflect panel requires a plane for the creation of the mirror images of the entities selected. HyperMesh takes advantage of the following principle: a plane can be defined with a vector (the plane is normal to the vector specified), just as a vector can be defined with a plane (the vector is normal to the plane specified). Either can be defined via the plane and vector selectora group of buttons that work in concert to define planes or vectors, as needed:
The Plane and vector selector. This selector is broken down into the following items. Note, however, that not every item appears at all times; only the items necessary for the current HyperMesh function will display. switch The switch is used to select the method for defining the plane or vector. The options available are:
Use x-axis, y-axis, and z-axis to define the first, second or third axis respectively of a coordinate system in your model. This coordinate system may be the global coordinate system, or a local system when one can be explicitly specified. Local systems may be rectangular, cylindrical or spherical. Choose vector to specify a vector entity (created in the vectors panel). This includes vectors defining coordinate systems, and loads as well. Use N1, N2, N3 to define a vector (N1,N2), or plane (N1,N2,N3). When defining a plane, the resulting vector is normal to this plane following the right hand rule, and passes through either N1 or the base node (if one is specified). Double-click a nodes button (N1, N2, or N3, or B) to type in coordinates rather than selecting existing nodes in your model.
Altair Engineering
B (base node)
Use this selector to define the base nodethe point in space where the vector or plane is located. For example, selecting a plane of projection using the x-axis does not define the location of the plane entirely. A base node provides the extra information. Note that when using the N1, N2, N3 option, HyperMesh uses N1 as a default base node if no other base node is specified.
reset Note:
Allows you to clear your selection (vector, N1,N2,N3 and base). Some selectors may resemble the plane and vector selector, but serve a different purpose. For example, the following selector displays in the position and linear solid panels:
This selector is used in these panels to map entities from one location to another. To define a vector: 1. 2. 3. Select the x-, y-, or z-axis. Select two nodes, N1 and N2. Select three nodes, N1, N2, and N3. The vector is the normal of the plane defi ned by the three nodes. N1 (or the base node, if selected) is the point on the plane through which the vector passes. Select a model vector (i.e., arrows that represent a local coordinate system vector or load vector).
4.
To define a plane: 1. 2. 3. 4. Select the x-, y-, or z-axis and a base node. The base node locates a plane normal to the chosen axis. Select two nodes, N1 and N2. The resulting plane is normal to the N1-N2 vector and passes through N1 (or the base node, if selected). Select three nodes, N1, N2, N3. A parallel plane can be specified by selecting a base point elsewhere in the model. Select a model vector (i.e., local coordinate system vectors or load vectors). The resulting plane is normal to the vector.

Altair Engineering
Input Fields Input fields are used to enter text or numerical values. A description of the type of input precedes the field. After you click either the input field or the description, the text currently in the input field is highlighted, signifying that the input field in ready for editing. You can cut and paste text from one data field to another within HyperMesh and also from data fields in HyperMesh to a command window (except in OpenGL versions).
Input field. You can enter characters and numbers from the keyboard to modify the value, or click the input field a second time to access the HyperMesh calculator. When you type an alphanumeric character with the keyboard, the value previously assigned to the field is erased, and the new character is placed at the far left of the input field. If you want to edit the existing data, press a right or left arrow key ( or ) before pressing any other keys. In edit mode, the following keys perform the corresponding functions: ESC Restores the initial text or value displayed upon entering edit mode. Press the ESC key while the field is still active to restore the initial text or value to the input field. Move the cursor in the input field to the left and right, respectively. After positioning the cursor in the input field, characters can be inserted or deleted at the proper location. Deletes the character to the left of the cursor and moves the cursor one space to the left. Moves the cursor to the beginning of the input field. Moves the cursor to the end of the input field. Deletes the character which is above the cursor. Moves the input cursor from field to field on the panel.
and
BACKSPACE HOME END DELETE TAB
To exit edit mode, press the ENTER key, select another menu item, or press a function key. Character String Input To enter a character string, click the corresponding menu item or input field (the menu item is placed in edit modea), and use the keyboard to enter text until the proper information is displayed. The first character in a string cannot be a space; HyperMesh removes any leading spaces contained in a character string. Note: If you need to specify the name of a collector for a data input field (i.e., comp =, plot =, title =), click the menu item or input field a second time to select the name from a list of the existing collectors.
To cut and paste character strings, use the mouse cursor to select the text you want to copy, press CTRL-c, move the cursor to the location where you want to insert the text, and press CTRL-v. Note: You can cut and paste from one input field to another or to a command line in another window (except in OpenGL.).
Altair Engineering
Numeric Data Input Numerical values are specified as real numbers or integers. HyperMesh displays integer values without a decimal point. Real numbers are displayed with a decimal point or in scientific notation. If a real number contains three or more leading zeros after the decimal, HyperMesh automatically displays the value in scientific notation. To enter numeric data, click the corresponding menu item or input field and enter the value using the keyboard. You can also use the HyperMesh calculator to enter the value. To use the calculator, click the menu item or input field a second time (the first click allows you to enter edit mode, the second click gives you access to the calculator), click numeric and function buttons on the calculator using HP-style reverse notation, and click exit to close the calculator.
Calculator pop-up. In edit mode, HyperMesh discards input characters that are not valid numbers and subsequent numbers. For example, if you type 123e+1q1, HyperMesh interprets it as 1230.000. If HyperMesh expects an integer value and you enter 123.45, HyperMesh truncates the number to eliminate the decimal point. To cut and paste numeric data, use the mouse cursor to select the text you want to copy, press CTRL-c, move the cursor to the location where you want to insert the text, and press CTRL-v. Note: You can cut and paste from one input field to another or to a command line in another window (except in OpenGL.).
Pop-ups Pop-up menus are displayed when there are seve ral options from which to choose. When the pop-up menu appears, the mouse cursor is centered in the menu and the menu is made active. Some pop-ups are displayed with a border around the menu box and some have no border. If the pop-up menu has a border, you must make a selection before you can proceed. If the pop-up does not have a border, you can either select a menu item on the pop-up menu or move the mouse outside the bounds of the menu. Some pop-up menus allow multiple selections. For example, the view pop-up menu (view on the Toolbar Area) allows you to make multiple selections. HyperMesh immediately processes the selection you have made on the pop-up menu and then waits for you to make more selections. The pop-up menu remains on the screen until you move the mouse outside the bounds of the box.

Altair Engineering
File Browser
When you open or save a file using save as..., retrieve, import, load, write as, browse, etc, you use the standard Windows file browser. The file browser enables you to navigate through the directories on your network to locate files.
Look in/Save in
This drop-down menu contains the overall directory structure, as well as the contents of the open directory. You can open new directories from this list. Folders and/or file names within the selected directory are listed below the Look in/Save in text box, based on the search criteria used. This field allows you to enter the name of the file you wish to locate. It also displays the file that has been selected from the list. This field allows you to select the type of file you want to locate. Click Open (or Save) to load (or save) the file shown in the File name field. Click Cancel to close the file browser.
File name Files of type Open (Save) Cancel
Displays the folder at the previous level. Creates a new folder within the current directory. Lists only the file name. Lists the file name, type, and last date modified.
Altair Engineering
To search for a particular file extension: 1. 2. For Look in/ Save in, specify the search directory. In the File name field, type *.ext where ext is the extension of the file type you wish to locate. For example, *.hm searches for all the HyperMesh database files (files with an .hm extension) in the specified directory. You can also type *.hm* for all HyperMesh database files with extensions hm4, hm5, hm6, etc. Type *.* to search for all files in the directory. Or For Files of Type, select the file type from the drop-down menu. 3. Press ENTER. All files ending with the specified extension are displayed. To search for a particular filename: 1. 2. 3. For Look in/Save in, specify the directory to search. For File name, type filename* where filename is any portion of the name of the file you wish to locate. Press ENTER. All files beginning with the specified characters are displayed in the files list.

Altair Engineering
The Mouse
The mouse attached to your system is integral to HyperMesh and can be used in almost every aspect of user input. Some operations require pressing a keyboard key in addition to using the mouse. Rapid menu allows you to use the middle mouse button to quickly perform common operations without frequently moving the mouse between the graphics region and the panel region. Keyboard Left mouse Middle mouse Right mouse
Single click and release. Performs selection operations on single entities.
Single click and release. Acts as advance (proceed) function after entity selection in most panels. Selects a new center of rotation in the rotate (r) and arc dynamic motion (a) modes.
Single click and release. Deselects an entity in the graphics area. Aborts graphics operations.
Single click and hold. Aborts intensive processes, such as Penetration Checks.
Click and move. Pre-highlight the entities as the mouse travels, thus allowing you to view the entity that will be selected. If you release the mouse, the pre-highlighted entity is selected Dynamic rotation in the rotate (r) and arc dynamic motion (a) modes.
Click and move. Pre-highlight the entities as the mouse travels, thus allowing you to view the entity that will be deselected (removed from selection). If you release the mouse, the pre-highlighted entity is deselected.
CTRL
Single click and release. Selects a new center of rotation.
Single click and release. Fit the displayed model to the screen.
Altair Engineering
CTRL
Click and move. Dynamically rotates the model.
Click and move. Zooms into an area of the model.
Click and move. Pans the model.
SHIFT
Single click and release. In entity selection mode choose one of the four quick window selection modes from a pop-up menu:
Single click and release. Acts as advance (proceed) function after entity selection in most panels.
Single click and release. In entity selection mode choose one of the four quick window selection modes from a pop-up menu:
Entities inside a rectangular window Entities outside a rectangular window Entities inside a polygon window Entities outside a polygon window
Entities inside a rectangular window Entities outside a rectangular window Entities inside a polygon window Entities outside a polygon window
SHIFT
Click and move. In entity selection mode quick window selection of entities. In display panel turn off collectors that are inside/outside the window.
Click and move. In entity selection mode - quick window deselection of entities. In display panel turn on collectors that are inside/outside the window.

Altair Engineering
Rapid Menu
Rapid menu is a feature that uses the middle mouse button (a single click for each step) to move through a panel along a predetermined path. This allows advanced users to perform common operations without frequently moving the mouse between the graphics region and the panel region, thus reducing "mouse miles". The function button that is assigned to rapid menu is outlined in black. For example: in the hidden line panel shown below, HyperMesh performs the fill plot action when you click the middle mouse button.
The rapid menu function is predetermined and varies between panels. In panels that contain multiple function buttons, rapid menu is assigned to the most commonly used function. The rapid menu function can also vary within a panel. For example, when you enter the lines panel, return is assigned to the rapid menu. But once you pick a node to create the line, create becomes the rapid menu function. In most panels, the middle mouse button returns you out of the panel if the active input collector (yellow collector with a blue outline) is empty. In panels where there is a defined sequence of selections (input collectors), rapid menu advances to the next collector. For example in the ruled panel, select a few nodes for your first node list or line list, and then click the middle mouse button to advance to the second node list so that you can begin picking more nodes. In panels where there is no clear sequence of selections, the middle mouse button may activate a function for which there is insufficient data, resulting in an error message. For example, when you try to move nodes using the N1, N2, N3 vector option in the translate panel. If you click the middle mouse button after you select the required nodes, an attempt to perform translate + is executed. Since you do not have N1, N2 and N3 selected or may not have a magnitude value entered, an error message results. Some panels do not have function buttons and are repetitive. In such cases, using the middle mouse button returns you out of the panel. For example, in the replace panel, if you pick two nodes, it replaces one with the other and proceeds to repeat the operation with the new selection. In some panels, the entities in the input collector are not cleared, allowing you to use the same entities to repeat the operation. In these panels, the middle mouse button repeats the chosen function as long as the entity collector is not reset to empty. For example, in the translate or rotate panels once you selected some elements/nodes/comps and direction and distance of translation, clicking the middle mouse button a second time repeats the translate + or rotate + function, thus translating/rotating the same nodes again. In panels that have pre-filled defaults, a middle mouse click performs the operation with the defaults. For example, collectors/create panel with a preset collector name creates a collector when you click the middle mouse button.
Altair Engineering
Keyboard
Although most HyperMesh operations are performed with the mouse, you must use the keyboard to enter new file or component names or title information. In addition, there are several keyboard hot keys that you can use to access the viewing functions available on the Toolbar Area. The hot keys are the same as the letters on the menu. You can also use the arrow keys on the keyboard to rotate your model. The secondary menu uses various combinations of the function keys, SHIFT key, and CTRL key to access panels. Rotate by increments
Ctrl
Incremental counterclockwise, clockwise, and reverse view Zoom by increments. Note that "+" is actually shift = on the main keyboard, but simply + on the numeric keypad. Arc rotate Return to a previous view Center (spherical) clipping panel display panel Fill/fit model to window. global panel Open the Help. When a panel is active, this opens help for that panel; from the main page menu, it opens the Helps table of contents. Turn off the menus and display only the graphics window. Press "m" again to bring the menus back. options panel Plot Rotate Dynamically zooms in and out when you move the mouse up and down True view transparent components panel User View pop-up menu Windows panel Circle-zoom When you use the +, -, or arrow keys, press the key once and wait for HyperMesh to redraw the model before pressing the key again. You can press ESC instead of clicking return to exit a panel.
+,a b c <ctrl>+<c> d f g h m o p r s t <ctrl>+<t> v w z Notes:

Altair Engineering
Mapping Keyboard Shortcuts

Keyboard shortcuts can be used to map HyperMesh functions to keys or key combinations, so that you can quickly execute tasks that you use frequently simply by pressing one or more keys on the keyboard. One example of this is the default mapping of the <f> keywhich, when pressed, zooms and pans the graphics area view to fit the currently displayed model to the screen. You can customize the default shortcut mappings to create your own shortcuts for a variety of tasks. Examples include: Jumping to a specific HyperMesh panel Automatically performing a task using HyperMesh *commands Executing a macro
The following keys are usable when defining shortcuts: Letter and number keys ("standard" keys) <ctrl> plus another "standard" key <shift> plus another "standard" key <ctrl> plus <shift> plus another "standard" key
You can assign or remove a shortcut by selecting keyboard from the Preferences pull-down menu.
The keyboard option opens a free-standing window with a keyboard display.
Altair Engineering
Keys display in the Key-Command Mappings window with colors based on their mapping:
To map a function to a shortcut key, select the appropriate key by clicking in the keyboard menu or holding down that key on your keyboard. The selected key highlights in blue. Next, enter the appropriate command(s) and if necessary the file name (for a tcl script) in the table area of the menu located below the keyboard diagram. Notes Some special-function keys, such as tab, shift, esc, ctrl, alt, backspace etc, cannot be mapped. Those keys are identified with a different color: Use the hm_pushpanelitem command in a shortcut to jump to a specific sub-panel of a panel. For example, to enter the combine sub-panel in the element edit panel, use hm_pushpanelitem {element edit} {combine} This will take you to the last used sub-panel in the specified panel. Any HyperMesh command file commands can be mapped to a shortcut key. Some keyboard shortcuts are mapped by default during installation, and some utilize functions which are only accessible via shortcut keys. Remapping such keys to new functionality results in loss of original functionality. Examples of such shortcuts are: Incremental rotate left, up, right, and down respectively. Ctrl + Ctrl + F1 Ctrl + F2 Ctrl + F3 Ctrl + F4 Ctrl + F5 Ctrl + F6 Incremental clockwise, counterclockwise and reverse view Creates bitmap file of the screen and spools it to the printer. Creates a bitmap file of the screen and writes it to disk. Creates PostScript file of the screen and spools it to printer. Creates a PostScript file of the screen and writes it to disk. Creates a black and white PostScript file of the screen and spools it to the printer. Generates a *.jpg screen capture or animation file.

Altair Engineering
shortcut mapping examples To create a shortcut key "e" that deletes all the elements in the model, enter the following commands in the command field next to the key "E": *createmark elements 1 "all"; *deletemark elements 1; To create a shortcut key "L" that accesses the lines panel, enter the following in the command field next to the key "L": hm_pushpanel {lines}; To create a shortcut key "J" that runs a macro to find all the elements with jacobian < 0.7: this macro already exists in the QA page of the Utility menu. To call the same macro, enter the following in the command field next to the key "J": *evaltclstring "macroElementJacobian 0.7" 0 To create a shortcut key "shift + K" that runs a macro to check whether any beam/bar elements exist in the model and display them only: Create a findbeams.tcl file with following commands: Proc displayonlybeams {} { *createmark elements 2 "by config" 60 63 set beams [hm_getmark elements 2] *clearmark elements 2 if { ![Null beams]} { *displaycollectorwithfilter(comps, eval *createmark elements 1 $beams; *findmark elements 1 0 1 elements 0 2; } else { hm_usermessage "No beam elements in this model" } } In the Key-Command Mappings window, select shift from the Shortcut Key pull-down menu. Enter the following in the command field next to the key "K". *evaltclstring displayonlybeams In the file field, click the "" button to browse to and select the findbeams.tcl file. "none", "", 1, 1);
Altair Engineering
Secondary Menu
The secondary menu is a list of panels that can be accessed by using the function keys F1 through F12, or in combination with the SHIFT or CTRL keys. The secondary menu allows you to use panels that add information necessary to complete the currently active panel. When you use the secondary menu, it interrupts the active panel and allows you to perform a function in the secondary panel, and upon completion, to continue using the initial panel. Entities selected while in the secondary panel are still selected when you return to the initial panel. The default secondary panels are as follows: Key F1 F2 F3 F4 F5 F6 F7 F8 F9 F10 F11 F12 Note: Function key only hidden line delete replace distance mask element edit align node create node line edit check element geometry quick edit automesh plus SHIFT key color temp nodes edges translate find split project node edit surf edit normals organize smooth plus CTRL key print slide slide file print eps create eps file print b/w eps create JPEG file
Function keys may be reassigned to different panels by using the build menu panel.

Altair Engineering
Utility Menu
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 timeselecting a button de-selects all of the other buttons in the group. A macro file (hm.mac) controls the display and available operations of the utility menu. Attributes that you can change include: The utility menu page on which the operations appear Text to be displayed on each control Location and size of the menu The help string to be displayed on the menu bar The macro to call when each control is used, with optional arguments to pass
The page number allows you to create multiple pages, so that you can group the macros by type of operation. Macros may contain any valid command file command, and are enclosed by the *beginmacro() and *endmacro() commands. Macros may accept variable arguments, passed to them from a control, by using the arguments $1, $2, etc. to specify where the arguments should be substituted. The *callmacro() command allows you to call a macro from within another one, which allows you to create groups of standard reusable macros. When HyperMesh starts, it looks for a macro file named hm.mac in the current directory, HOME directory (UNIX only), or the applications base directory. If it finds this macro, HyperMesh runs it automatically to define the attributes and contents of the utility menu. You may also select and run a macro file after HyperMesh starts from within the options panel. The default hm.mac file sources the following additional macro files: disppage.mac geommeshpage.mac globalpage.mac qamodelpage.mac userpage.mac Populates the Display page of the utility menu. Populates the Geom/Mesh page of the utility menu. Creates the button group that allows you to switch pages. Populates the QA/Model page of the utility menu. Populates the User page of the utility menu.
A userpage.mac file may exist in the installation directory for HyperMesh or in the directory from which HyperMesh launches. When HyperMesh starts, it first looks for the userpage.mac file in the directory from 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.
Altair Engineering
By default, the Utility menu displays when HyperMesh starts, but display of the menu is controlled by a command in the HyperMesh Configuration. If you want to remove the Utility menu from the default screen display, delete the * before the *enablemacromenu() command in the hm.cfg file. 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.
Default Utility menu

The utility menu is normally located on the left side of the graphics region, in the Tab area pane. However, it can also be dragged-and-dropped to the right -side explorer pane, if that pane is open. It contains page selection buttons at the bottom of the menu, with the current pages button depressed. The different pages of the utility menu are: Geom/Mesh (macros related to model geometry and FE mesh) Disp (Options related to the graphical display of entities) QA/Model (macros related to element quality and loads) User (user-created macros only)
The utility menu displays by default, although it may be obscured by another tab such as the model browser or include browser. You can turn the utility menu off completely (removing its tab from the tab area) by un-checking it in the view pull-down 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-and-dragging the tab to the HyperMesh 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.
Disp Utility menu

The Disp utility menu contains a variety of macros that allow you to modify the graphical display of HyperMesh entities in several different ways. Chief among these is the ability to turn the display of individual entity types on and offfor example, showing or hiding all 2-D elements. You can also isolate only a specific entity type, turning off the display of everything except entities of type. Then, if you wish, you can turn the display of individual types back on as desired, until only the desired subset of entity types displays. You can also mask and unmask portions of your model, and save additional model views. By combining these features, you can restrict HyperMesh to only drawing a small sub-set of the entities in your model. See the descriptions below for help with each type of macro.

Altair Engineering
Scene macros:
These controls allow you to save and retrieve up to three additional views of your model. These views function just like the custom views that you can save and retrieve via the user views function (accessed from the HyperMesh toolbar). These views function in addition to the user views, however, and always include any masks that you may have applied to the model. Scene (1, 2, 3) Save Scene (1,2,3) Retrieve These buttons save the current view of the model in slot 1, slot 2, or slot 3. These buttons retrieve views of the model that you have previously saved via the scene (1, 2, 3) save macros.
Display macros:
These controls form the bulk of the menu, and allow you to turn the display of different types of entities on or off, or isolate the display of an entity type. There are different categories of entities whose display you can turn on and off. Broad categories, such as geometry, control an array of several related entities (such as points, lines, surfs, and solids). This allows you to turn the display of entire classes of entity on or off in one click. These broad categories have buttons labeled All or none. The largest group possible is labeled Everything. The All and none buttons for this category literally affect every entity in the model, regardless of entity type. In other words, clicking none hides the entire model, including its boundary conditions. Smaller sub-types of entity, such as 2-D elements or geometry points, are more restrictive. Toggling the display of these does not affect other entities within the same broad category. So, for example, if you turn off the display of lines, other geometry types (such as points) do not turn off. This enables you to turn off certain entities while retaining others, even within the same broad category. These sub-types have buttons labeled on or off. Each broad category or sub-type has a text label on the menu, followed by 2-3 buttons. These buttons perform the actual display macro functions: All These buttons only exist for broad categories of entity type, such as elements or geometry. Clicking All turns on the display of all of the entities indicated by the label. For example, clicking all next to the elements label turns on the display of every element type in your model. These buttons only exist for broad categories of entity type, such as elements or geometry. Clicking none turns off the display of all of the entities indicated by the label. For example, clicking none next to the elements label turns off the display of every element type in your model. These buttons only exist for sub-types of entity, such as 2-D elements or lines. Clicking On turns on the display of all of the entities indicated by the label. For example, clicking all next to the 2-D label turns on the display of every 2-D element in your model, but does not affect the display of 0, 1, or 3-D elements. These buttons only exist for sub-types of entity, such as 2-D elements or lines. Clicking Off turns off the display of all of the entities indicated by the label. For example, clicking Off next to the 2-D label turns off the display of every 2-D element in your model, but does not affect the display of 0, 1, or 3-D elements.
none
On
Off
Altair Engineering
Only
These buttons may appear for broad categories of entity or sub-types. Clicking only isolates the entity type indicated by the label by hiding every other entity type in the model, so that only the specified entity type remains visible. For example, clicking Only next to the 2-D label turns off the display of every entity in the model except for 2-D elements, so that only 2-D elements remain visible.
Note that these functions are accumulative; turning off all geometry, then turning on lines, results in only the lines (plus FE elements, boundary conditions, etc.) displaying. Similarly, if you choose to show only 2-D elements, you can then add other entities to the view by turning them On one-by-one. The only exception to this accumulative usage is repeated use of the only option: since it always hides everything except the chosen entity type, multiple only commands do not work accumulatively. Comments Handle (located under the Elements category) refers to the text labels that appear on some elements, such as rbe3 elements. Labels (located under the BCs category), refers to the text labels for boundary conditions such as pressures and forces. The By Edge macro (under Geometry Surfs) allows you to turn off all surfaces attached to one or more edge lines. Clicking one of the buttons for this option causes HyperMesh to display a lines selector. Select the desired lines and click proceed to show, hide, or isolate the surfaces touching those lines. To exit the macro, either click proceed again without selecting any lines, or press the <esc> key.
Mask and Node macros:

The final set of controls concern masking and unmasking entities, as well as removing temporary nodes. Like the display controls, masking allows you to reduce the number of entities drawn onscreen; however, masking is based on entity location rather than entity type. Mask Out This macro automatically applies a mask to hide every entity in the model that does not currently display in the graphics area. Note, however, that entities cant be partially hiddenso while some of the mesh elements on a surface may be masked out, the surface itself will not be unless it is completely outside of the graphics display area. Unmask All Clear Temp Nodes This macro removes any and all masks that you have applied to the model, either by way of the mask out macro or the mask panel. Temporary nodes are any nodes that users create during a HyperMorph session. These nodes are redundant because they must be created on existing geometry; for this reason, they should be deleted before the model is sent to a solver. Click Clear Temp Nodes to automatically remove all temporary nodes from the model. This macro reveals one or more rows of elements adjacent to the entities currently displayed. For example, if you isolated a models geometry lines, then clicked show adjacent elems any mesh along , those lines would be revealedbut only a single row of elements. This allows you to view only the adjoining mesh, rather than all of the mesh for an entire component.
Show Adjacent Elems

Altair Engineering
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 Project points Prevents specific edges from being suppressed during autocleanup or batchmeshing. Projects free points to surface edges. Depending on the tolerance you specify, points may even project to multiple edges. This can be helpful to achieve uniform meshing with regard to weld points. Isolates either an inner or an outer surface layer (based on the user selected surface) from a 3D model. This macro works only on the surfaces attached to the selected surface. The other layers and thickness are then placed in a temp directory and masked. Extracts a midsurface from a thin solid representation of sheet metal stamped parts, by offsetting one side surfaced to midplane. You select a line whose length represents the solid thickness and a surface, which is part of either the inner or outer side of the solid. The macro also creates the corresponding property card and updates the thickness. This macro is intended to be used with sheet metal parts with uniform thickness and does not work for molded solid parts, etc. with ribs (T junctions). Scales a copy of a selected circular line to 1.5 times its original size, and then trims this new line into the surface. This allows a higher quality mesh around circular holes. Places four additional fixed points on an inner line, and then projects those points to a concentric line, creating a higher quality mesh.
Isolate Surface
ThinSolid=>Midsurf
Washer
Adj Circ Pts The mesh macros are: Auto Connectors Midsurf Thickness
A pop-up menu that allows you to automatically create connectors and FE realize them from a master connection file. Assigns the thickness of a midsurface geometry to FE nodes or elements. Its primary use cases are solid parts with varying thickness. You can also review the thickness as a contour plot on the elements. Quickly creates an automatic tetrahedral mesh while meeting the requirements for minimum element angle and element size. Improves element quality by moving the mid-edge nodes of second order elements. Creates a layer of washer elements around a circular hole in the mesh. You select a node along the hole, the macro determines the radius of the hole, and displays a menu for entering the width of the washer. Two other options available are: 1) Create a rigid spider along the hole and 2) Enforce a minimum number of nodes around the hole. The macro then creates a layer of washer elements around the hole and remeshes the surrounding elements to maintain mesh connectivity.
Quick Tetramesh Fix 2nd Order Midnodes Add Washer
Altair Engineering
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. Fills the selected hole and remeshes the surrounding mesh to maintain connectivity. This macro does not remove any rigid spiders that fill the hole; if necessary, delete the rigid spider before using this macro. Trims the model along user-defined trim lines. This is useful for reducing the model size by taking advantage of symmetry etc. Creates a bead of a given height and width along the selected two nodes and connects to the surrounding mesh.
Fill Hole
Box Trim Bead
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 HyperMeshand can be indirectly adjusted by changing the settings on the check elements panel.
Tools
There are eight tools to isolate elements that fail certain element check criteria. Length This macro checks all the displayed elements against the minimum length criteria. If any elements fail the criteria, it displays the failed elements and masks the remaining elements. If none of the displayed elements fail the criteria, it displays a message and leaves the model display unchanged This macro checks all the displayed elements against the maximum Jacobian value. If any elements fail the criteria, it displays the failed elements and masks the remaining elements. If none of the displayed elements fail the criteria, it displays a message and leaves the display unchanged This macro checks all the displayed elements for their warpage. If any elements fail the warpage test, it displays the failed elements and masks the remaining elements. If none of the displayed elements fail the criteria, it displays a message and leaves the display unchanged This macro checks all the displayed elements for their aspect ratio. If any elements fail the criteria, it displays the failed elements and masks the remaining elements. If none of the displayed elements fail the criteria, it displays a message and leaves the display unchanged This macro checks all the displayed quad elements against the maximum internal angle. If any elements fail the criteria, it displays the failed elements and masks the remaining elements. If none of the displayed elements fail the criteria, it displays a message and leaves the display unchanged
Jacob (Jacobian)
Warp (warpage)
Aspect (aspect ratio)
Max ang: Q (quad)

Altair Engineering
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 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 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
Min ang: Q (quad)
Min ang: T (tria)
You can use the following macros to quickly modify any elements that fail the element checks. Split Warped Checks all displayed quad elements for warp exceeding the acceptable value. Each element failing this criterion is then split along its diagonal to form two tria elements instead of the original quad. Finds all of the elements attached to the displayed elements. Allows you to remesh the selected elements plus one, two, or three attached layers of elements (one button for each). The remesh uses the current size, does not break connectivity, and uses the mixed element type. Allows you to apply the smoothing algorithm to the selected elements plus one, two, or three attached layers of elements (one button for each). Brings up a user interface that allows you to set the various quality values and check the quality of all the 2D elements in the model. The results are shown as the number of elements and percentage of elements failing each criterion. You can also export the results to a text file using save as. Note: Changing the criteria on this report interface does not change the settings in the check elements panel. They only affect the report.
Find Attached Remesh
Smooth Quality Report
Model Tour
Allows you to review (tour) the selected components individually. This macro displays the component name, number of elements in that component and their ID range. It also displays a dialog that allows you to review the free edges of the component and any elements attached to the component. Reads a generic Bill Of Materials file and provides an interface to manipulate data in the BOM as well as the corresponding FE model.
BOM Comparison Tool
Altair Engineering
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 indicatorsit does not change the load magnitudes. Find Elems>>Loads Find Comps>>Loads Find Loads>>Comps Find Elems>>Connectors Automatically finds all elements directly attached to any and all load indicators. If masked, these elements are un-masked. Automatically finds all components directly attached to any and all load indicators. If masked, these comps are un-masked. Automatically finds all loads directly attached to a selected component. If masked, these loads are un-masked. Automatically finds all elements directly attached to any and all connectors. If masked, these elements are un-masked.

Altair Engineering
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

Note: The BOM Comparison Tool only applies to the Nastran, LS-Dyna, Radioss-Block, and Abaqus user profiles.
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
Altair Engineering
BOM Comparison Tool GUI

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

Altair Engineering
BOM Comparison Tool Control Section

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

Altair Engineering
BOM Comparison Tool Tree Section

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

Altair Engineering
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:
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
BOM Comparison Tool Metadata Display Section

You can create, update and delete metadata using some of the menu items on the BOM display table. Metadata information contains all the attributes for a part in the model. The metadata display section contains four display options in the form of a combo box. After selecting a row in the BOM Display table, and then use this combo box to select the type of information displayed in the metadata display table: None Metadata related to BOM All metadata Differences between BOM/metadata clear the table if already some data exists display BOM related metadata for the selected row in the BOM display table display all the metadata for the selected row in the BOM display table display two rows of info in the metadata table. First row corresponds to BOM info, second row corresponds to metadata associated with the model
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 out-of-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. 102 HyperMesh 8.0 Users Guide
Altair Engineering
Preserve Edges
Both the batch mesher 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 lines or select comps. Thus, picking a new set of lines starts over instead of adding to the selection. Clicking this button returns focus to HyperMesh and displays a line selector in the HyperMesh panel area. Use the lines selector to choose the lines you wish preserved. Click this button to highlight the lines already marked for preservation. When active, this checkbox prevents HyperMesh auto-cleanup from equivalencing the boundaries between adjacent components. Clicking this button returns focus to HyperMesh and displays a component selector in the HyperMesh 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 componentsonly the outer boundary edge. Removes all lines from the preservation list. Saves the preservation state, so that autocleanup and batch mesher will know which lines must be preserved.
Select Lines
Show Preserved Comps selection boundary Select comps
Clear all lines Save preserved
Altair Engineering
Reset highlights
After clicking the show preserved button, use this button to remove the highlight from the preserved lines. The lines remain preserved; only the visual highlighting effect is removed (until you click show preserved again).
OK Cancel
Accepts any changes youve made and closes the pop-up window. Discards any changes youve made and closes the pop-up window.
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 HyperMesh panel area; use this to select the surfaces whose edges you wish to project points to. After selecting surfs and clicking proceed, HyperMesh displays a target element size field. 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.
Midsurf Thickness
Geometric surfaces that represent the mid-plane of a solid part, if extracted using the HyperMesh midsurface function, have thickness information stored in their definition. 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. When you click the Midusrf thickness menu button, the controls for this macro display in a new tab in the tab area.

Altair Engineering
The following options are available in the Midsurf thickness... macro: Apply thickness to You can choose to assign or view the thickness values at the nodes or on elements. The nodes option is valid for only LS-DYNA and ANSYS solvers. Use the Nodes/Elements option to assign the thickness and Z-offset values directly to the element cards. For each User profile, the values will be updated on the element card for that solver. (For example, CQUAD4 T1-T4 and Zoff fields will be populated for OptiStruct and Nastran). Refer to the User profile section for more details on the unique behavior of the Midsurf Thickness utility for each User profile. Use the Components option to group elements that fall within userspecified thickness intervals into common components, then assign the thickness value to the component property card image for each User Profile. (For example, the PSHELL T field will be populated for OptiStruct and Nastran). 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 component named t0 must be defined. The t0 component definition will be used for all created components based on the Range Interval specified in the Component Organization Method section described below. The components option performs the following generic steps for each User profile: 1. Creates components with name t[thickness value] by copying the properties of the base component t0 and assigning the appropriate thickness based on the value of the Range Interval or Gage File options. Groups the elements that have thickness values within the specified ranges into the new component based on the Range Interval or Gage File options. Assigns appropriate thickness values to the Component.
2.
3. Z-Offset Values
Activate this checkbox to take z-offsets into account. HyperMesh uses Z-offsets when midsurfacing parts that have variable thickness; the zoffset (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:
To assign Z-offset values to the element cards for supported solvers, check the Z-offset values checkbox. This option is only valid for OptiStruct and Nastran User profiles.
Altair Engineering
Thickness calculation method
This option is valid only while applying the thickness to elements. You can obtain the thickness value from the surface at: Average the average of the elements nodes. Centroid the elements centroid (interpolated from its nodes) Max the maximum value of the elements nodal thicknesses. Min the minimum value of the elements nodal thicknesses.
Component Organization method
This option specifies the thickness range intervals used when grouping the elements into components based on their thickness values. HyperMesh groups elements having thickness values within the specified range intervals into appropriately created components with the appropriate thickness values assigned to the component. You can specify thickness range intervals by two methods: 1. Gauge You must specify the thickness range intervals in a Gage File. Click here for details on the format of the gauge file. If the Assigned Value is not specified, then the average of the upper and lower limits will be used as Assigned Value. 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 ) Upper limit = (tolerance / 2) + (tolerance* (i + 1)) Assigned value = tolerance*(i+1)
Where i = 0n, n is determined by the maximum thickness in model divided by the user specified tolerance and then rounding to up to the next integer. Assign Contour Assigns the thickness from the surface definition to the nodes or elements chosen. Creates a contour plot of the thicknesses on the selected elements/nodes. This step does not assign the thickness to the nodes or elements; it is a review/display function only. This option is very useful for visualizing and verifying the results of the Midsurf Thickness utility before applying the midsurf thickness mapping operation. Closes the tab.
Close

Altair Engineering
To Assign Thickness and Z-Offset Values using Nodes/Elements Option: 1. 2. 3. 4. 5. 6. 7. 8. Change to your preferred User Profile. Load the desired model file. Access the Midsurf thickness utility from the Geom/Mesh page of the Utility tab. Select the Nodes/Elements option. Optional: use the Z-Offset check box to assign both thickness and Z-offset values. Leave the checkbox blank to assign only the thickness values. Click the Assign button to open the element selection panel. Select the elements to map midsurface thickness onto. Click the Proceed button to perform the thickness mapping.
To Assign Thickness and Z-Offset Values using Components Option: 1. 2. 3. 4. 5. 6. 7. 8. 9. Change to your preferred User Profile. Load the desired model file. Create the base component t0, assign the base property card image, and enter any default values for this card. Access the Midsurf thickness utility from the Geom/Mesh page of the Utility tab. Select the Components option. Optional: use the Z-Offset check box to assign both thickness and Z-offset values. Leave the checkbox blank to assign only the thickness values. Select a Thickness Calculation method. Select a Component Organization method and either select a file or enter a tolerance based on the method. Click the Assign button to open the element selection panel.
10. Select the elements to map midsurface thickness onto. 11. Click the Proceed button to perform the thickness mapping To Contour Thickness for Node/Element Option: 1. 2. 3. 4. 5. 6. 7. Change to your preferred User Profile. Load the desired model file. Access the Midsurf thickness utility from the Geom/Mesh page of the Utility tab. Select the Nodes/Elements option. Click the Contour button to open the node selection panel. Pick the desired nodes. Click the Proceed button. The utility opens the Contour Panel and shows the distribution of thickness for the Node/Element option.
Altair Engineering
To Contour Z-offset for Node/Element Option: 1. 2. 3. 4. 5. 6. 7. 8. Change to your preferred User Profile. Load the desired model file. Access the Midsurf thickness utility from the Geom/Mesh page of the Utility tab. Select the Nodes/Elements option. Activate the Z-Offset check box. Click the contour button to open the node selection panel. Select the desired nodes. Click Proceed. The utility opens the Contour Panel and shows the distribution of the z-offset for the Node/Element option.
To Contour Thickness for Components Option: 1. 2. 3. 4. 5. 6. 7. 8. 9. Change to your preferred User Profile. Load the desired model file. Access the Midsurf thickness utility from the Geom/Mesh page of the Utility tab. Select the Components option. Select a Thickness Calculation Method. Click the Contour button to open the node selection panel. Select the desired nodes. Click Proceed to open the element selection panel. Select the desired elements.
10. Click the Proceed button. The utility opens the Contour Panel and shows the distribution of the thickness for the components option. To Contour Z-offset for Components Option: 1. 2. 3. 4. 5. 6. 7. 8. 9. Change to your preferred User Profile. Load the desired model file. Access the Midsurf thickness utility from the Geom/Mesh page of the Utility tab. Select the Components option. Activate the Z-Offset check box. Select a Thickness Calculation Method. Click the Contour button to open the node selection panel. Select the desired nodes. Click Proceed to open the element selection panel.
10. Select the desired elements. 11. Click the Proceed button. The utility opens the Contour Panel and shows the distribution of the z-offset for the components option. 108 HyperMesh 8.0 Users Guide
Altair Engineering
Gauge file example

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

Abaqus 1. Nodes/Elements Option 2. Unsupported
Components Option Creates components named t[assigned thickness]. Assigns thickness value to created component based on Component Organization Method option. Organizes elements into the created components based on element thickness value calculated using the Thickness Calculation Method option and the Component Organization Method.
3.
Z-Offset value Unsupported
Altair Engineering
Ansys The only difference between the nodes/elements and components options are that the nodes/ elements option will group the elements which match only exact thickness values. The components option will group the elements with thickness intervals. 1. Nodes/Elements 2. 3. Creates the component Creates Real Set property Assigns the thickness value to property Assigns the property to Component
Components Creates the component Creates Real Set property Assigns the thickness value to property Assigns the property to Component Group the elements to the Component
Z-offset Value Unsupported
OptiStruct and Nastran 1. Nodes/Elements Option 2. Assigns the Thickness and Z-Offset values to the Element Card based on the user selection
Components Option Creates components named t[assigned thickness]. Assigns thickness value to created component based on Component Organization Method option. Organizes elements into the created components based on element thickness value calculated using the Thickness Calculation Method option and the Component Organization Method.
3.
Z-Offset value If Z-Offset is checked on Z-offset values from the midsuface will be retrieved and assigned to the elements associated to that midsurface.

Altair Engineering
Ls-Dyna 1. Nodes/Elements 2. 3. Assigns the thickness values to the Element card
Components Creates the component Creates the property card Assigns the thickness value to property Assigns the property to Component Group the elements to the Component
PamCrash 1. Nodes/Elements 2. 3. Assigns the thickness values to the Element card
Components Creates the component Creates the property card Assigns the thickness value to property Assigns the property to Component Group the elements to the Component
Radioss 1. Nodes/Elements 2. 3. Assigns the thickness values to the Element card
Components Creates the component Assigns the thickness value to Component Group the elements to the Component
Altair Engineering
Quick TetraMesh
The Quick TetraMesh macro quickly creates a tetramesh of an enclosed volume defined by geometry and/or elements. Its main objective is to quickly and automatically create a tetramesh that meets the minimum interior angle and minimum element size. During the process of quick tetramesh, the mesh may deviate from the underlying geometry in order to maintain good quality elements. To alleviate this, you can select sacred elements so that the tetmeshing function closely follows the original geometry. This macro is accessed on the Geom/Mesh utility menu located on the standard utility menu, and displays in a new tab in the tab area.
The following options are available in the Quick TetraMesh macro: Volume Complist Double-click components and use the comps collector that displays in the panel area to select comps representing the geometry of the solid to be tetra meshed. Surfaces and/or elements can be used to define the volume. Click proceed to finalize the selection. The surface trias from which the tetramesh will be extrapolated will be generated with angles that measure at least this many degrees. Use this control to limit how acute the resulting elements will be. The maximum feature angle protects nodes on corners with a feature angle greater than the value specified, helping to better maintain the geometry. This applies only to cases where you can maintain features while fixing minimum element size. For example, if two nodes of an element share different features (as in thin steps), the features may not be maintained as they do not pass minimum element criteria. Altair Engineering
Minimum Tria Angle
Maximum feature angle

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. Average element size of the mesh to be created. No single edge of any generated element will be shorter than this. Minimum allowable area for any element. When HyperMesh tries to move element nodes 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! 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 size Minimum Edge Size Minimum Elem Size Sacred surface
Sacred elements
Mesh type Mesh Density
The mesh type options are Trias Only and Mixed. With the Mixed mesh type, both trias and quads may be created. Choose between chordal deviation and uniform. Chordal deviation uses smaller elements along curves, feature lines, and edges to improve accuracy, but requires more computing time. Uniform uses identically-sized elements throughout the mesh, but may produce lowquality elements along such locations. Choose floating, in which the quick tetramesher is free to move nodes in a surface tria mesh to achieve better tetra elements based on them, or fixed, in which the mesher must keep the tria mesh unchanged. Choose between automesh and batch. This determines the meshing engine used: the one used by the automesh panel, or the one used by the batch mesher. The Batch mesher generally produces better results, but does not currently support sacred surfaces or elements, ignores/replaces existing elements, and always uses uniform density. When this option is checked, no tetra elements are created and the macro simply goes through the cleanup steps for the shell mesh. Some of the cleanup operations performed are: the suppression of free edges, correction of sliver elements, splitting of elements, and projections onto the original geometry. All the cleanup steps are designed to improve the mesh quality. Opens a pop-up window with basic information about each control that displays on the tab.
Tet from
Mesher
Perform mesh cleanup only
Help
Altair Engineering
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. Closes the tab. A series of tools that help you located problem areas which can cause poor meshing: Find Holes Find T-Con Dihedrals Attached Try TetraMesh Locate holes in your model. Locate T-connections in the model. Locate features in the model that have feature angles greater than 150 degrees. Locate entities attached to the selected components. After making adjustments, click this to re-run the meshing operation on the same components.
Close Debug Surface Mesh
The Quick Tetramesh macro meshes the unmeshed surfaces in the model using chordal deviation and fixes all the elements that fail the criteria provided. You can manually mesh some critical geometry and select those elements as sacred elements. These sacred elements need to be trias. As a part of the cleanup, the tool heals small cracks in the model. Suggested process to effectively use quick tetramesh: 1. 2. Load the geometry. For critical areas where you want to control the mesh such as bolt holes, manually mesh using chordal deviation. Select these elements as sacred elements. This helps to obtain the desired mesh in critical areas. Launch the Quick Tetramesh macro. Run with the desired mesh size. Identify problem areas, if any (e.g. any surfaces edges that were ignored, or if mesh in certain areas is not satisfactory). Use the delete panel to delete the tetras then, manually mesh problem areas. Re-launch the Quick Tetramesh macro and select sacred elements to protect.
3. 4. 5. 6.
Fix 2nd order midnodes

This macro, located on the Geom/Mesh utility menu, improves element quality by moving the midedge 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 HyperMesh. In addition, moved midnodes lose any preexistent association with the underlying geometry.

Altair Engineering
Typical usage of this utility begins with use of the check elems panel to identify poorly-formed nd elements, and using that panels save failed option. From that point onward, you use the Fix 2 Order Midnodes utility: 1. Click the Fix 2
nd
Order Midnodes button on the geom/mesh Utility Menu.
An element selector and proceed button display in the panel area. 2. 3. Click the elems selector and select retrieve to load the saved failed elements. Click proceed. The Fix 2 Order Midnodes window opens. This pop-up window exists independently of the rest of the HyperMesh environment, so you can click-and-drag it to any desired location.
nd
The Fix 2 4.
nd
Order Midnodes window.

nd
In the Fix 2
Order Midnodes window, 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 ratio of minimum and maximum length for the segments of the midnodebearing edges. A value of 1 represents perfectly equal segment length, while a length of 0 would mean that the shorter segment might not existso this value must be greater than 0, but no greater than 1. Remember that this is a minimum length, so a value of 0.5 would allow the shorter segment to be half as long as the longer segment, or longerbut not shorter than half the length of the longer segment. Specify a minimum Jacobian value, and use the radio buttons to determine whether HyperMesh should evaluate each elements Jacobian at the corner nodes or the integration points. HyperMesh 8.0 Users Guide 115
Altair Engineering
5.
Click one of the command buttons to finalize: 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 2
nd
Order Midnodes window.
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
After clicking Apply

Altair Engineering
Trim Hole Macro

This macro, located on the Geom/Mesh utility menu, 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 the Trim Hole button opens a special, temporary panel in the HyperMesh panel area, with a nodes selector and a proceed button. Pick nodes on your model for the centers of each hole that you wish to create, then click proceed. A new window opens:
The options in the Mesh Trimming with Circular Holes window determine the type of hole that HyperMesh creates at each chosen node: Hole radius Number of layers Uniform/Varying Each node will receive a hole of this radius, measured from the node. This is the number of layers of washer mesh elements that you want to surround each hole. This toggle only applies when the number of layers is more than zero, and specifies whether you want mesh layers to all be the same width, or to vary from one another. 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.
Altair Engineering
Scale/Width
Determines the width of the washer layers. Scale: you can specify each layers scale relative to the Hole radius. For example, use 0.5 for a washer layer thats half as wide as the hole radius. Width: specify a fixed width for each layer.
Value Create rigid spider along the hole
The scale factor or width of the layer(s). This checkbox tells HyperMesh to create a rigid spider in each of the new holes created, 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 Trim Reject
This determines the mesh density around the new hole(s). Each new hole will be created with at least the number of nodes that you specify in the density field, evenly spaced around its circumference. Click this button to create the new hole(s). If you dont like the results of the last trim operation, click this button to undo it. Note that this only undoes a single click of the trim button, so it can only undo multiple holes if they were created simultaneously during a single trim operation. Close the Mesh Trimming with Circular Holes window.
Close
Fill Hole Macro

This macro, located on the Geom/Mesh utility menu, 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 click the Fill Hole button in the utility menu, a new window opens:

Altair Engineering
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 window temporarily minimzes, returning you to the main HyperMesh environment with a nodes selector active in the panel area. Select nodes on the edges of the holes that you wish to fill. Click proceed in t he panel area. The Filling holes with mesh window returns, with the Select Nodes button now green to indicate that nodes have been chosen. Click the Fill button to fill the selected holes with mesh.
2. 3.
4. Automatic
Use this option to let HyperMesh select holes automatically based on size. Type a value into the entry field labeled Fill circular holes with radius smaller than:. HyperMesh will automatically scan you model for holes smaller than this value, and attempt to fill them with mesh. Click this button to perform the fill operation, whether you chose to select your holes manually or automatically. If you dont like the results of the last fill operation, click this button to undo it. Note that this only undoes a single click of the fill button, so it can only undo multiple fills if they were created simultaneously during a single fill operation. Close the Filling holes with mesh window.
Fill Reject
Close
Box Trim Macro

The Box Trim macro, located on the Geom/Mesh utility menu, 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 right front rear frontleft frontright rearleft rearright Split the model along global Y=ymiddle and save the model between Y=ymin and Y= ymiddle (ymiddle =(ymin+ymax)/2). Split the model along global Y=ymiddle and save the model between Y= ymiddle and Y=ymax. Split the model along global X=value (selected value) and save the model between X=xmin and X=value. Split the model along global X=value (selected value) and save the model between X=value and X=xmax. Split the model along global Y=ymiddle and X=value (selected value) and save the model between Y=ymin and Y=ymiddle, and X=xmin and X=value. Split the model along global Y=0.0 and X=value (selected value) and save the model between Y=0.0 and Y=ymax, and X=xmin and X=value. Split the model along global Y=0.0 and X=value (selected value), and save the model between Y=ymin and Y=0.0, and X=value and X=xmax. Split the model along global Y=0.0 and X=value (selected value) and save the model between Y=0.0 and Y=ymax, and X=value and X=xmax.
Altair Engineering
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 automotiv industry. e
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.

Altair Engineering
To box trim a model: 1. 2. From the Geom/Mesh utility menu, click Box Trim. Using the extended entity selection, select the elements you would like to trim and click proceed or the middle mouse button. 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, the outer X, Y and Z bounds of the box.
, and select the two corner nodes that define
If you select Distance from center, click the icon, , and select the center node. Then enter Delta X, Delta Y and Delta Z values which is the distance from the center node to the outer bounds of the box in global X, Y and Z directions. 4. You can turn on the option of creating constraints (SPCs) for all the nodes along the face of the box. The nodes are constrained in the appropriate directions depending on the trim axes and are stored in the specified load collector (SPC collector). If no load collector is specified, the constraints are created in the current load collector. You can also specify a Box collector. A large hexa element that represents the box will be created for visualization in the specified collector. Click Trim. (Reject will undo all the above.)
5. 6.
Altair Engineering
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
Automated Connector Creation and Fe Realization dialog - user-defined option Input requirements for connector entity creation and FE realization are: Note: Master connectors/weld file FE config Projection tolerance In the case of a user-defined FE config, the user-defined FE type-t o-realize is required. The user-defined FE type definitions can be found in the appropriate feconfig.cfg file. This script automatically reads the default HyperMesh 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: Build systems Snap to node Attach to shells
Altair Engineering
Master Weld Files

The Master Weld File provides the weld location and parts to be connected. A format example is shown below. PointId 12:: 23:: 1t/2t/3t 2:: 3:: X 2.25: 3.05:: Y 2.25:: 3.25:: Z 1.0:: 0.25:: PartId1 2:: 2:: PartId2 3:: 3:: 5:: PartId3
The syntax is the same as used for spotweld.exe feinput translator. For additional supported formats, see Spotweld Interface Overview.
Diameter vs. Thickness Files

DvsT file (diameter vs thickness ) contains a table that associates the thickness of components and the nugget diameter of the weld. The equivalent area is taken to determine the side of the hexa. The file format includes thickness range and the corresponding diameter of the weld nugget. Minimum thickness 1.4 2.0 Maximum thickness 1.9 3.0 Nugget diameter 7 8
The nugget diameter is 7.0 for the thickness range of 1.4 to 1.99.
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. Th e solid element is created at the exact weld location independent of the shell elements that represent the sheet metal parts. These solid elements are connected to the corresponding components using RBE3 elements. The size of the solid element is determined using the DvsT file. The nugget diameter corresponding to the minimum thickness of the connecting parts is obtained from the DvsT file. The size of the hexa is calculated to match the cross-sectional area of the weld nugget. The length of the weld element is calculated using one of the following methods: (T1+T2)/2 This creates the Hexa elements with a length equal to the average component thickness it is connecting. T1 and T2 are the component thicknesses. The first figure below shows the ACM weld created using this method. This creates the Hexa elements between the component/element shell surface. The length of the Hexa element will be equal to the actual distance between the two connecting components/elements. The second figure below shows the ACM weld created using this method.
Project to shell

Altair Engineering
The figures below show ACM created using the two currently available methods.
ACM creation using (T1+T2)/2.0 option
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.
Altair Engineering
ACM welds can be created and managed in HyperMesh using connectors. Once a connector is created, they can be realized as ACM spotwelds as follows: 1. 2. 3. 4. 5. Load the Nastran user profile from the user prof panel in Geom or Tools page. Make sure that the connectors are created at each of the weld locations along with connecting parts information. Make sure all the connecting parts have PSHELL cards with correct thicknesses. Select the connectors to be realized as ACMs in the fe realize panel of the connectors module on the 1D page. Choose custom element config and select type = Nastran 70 ACM((T1+T2)/2) or type = Nastran 71 ACM (Shell Gap) per your requirements. The appropriate property script is automatically loaded for the selected type. Set the appropriate tolerance (proj tol=) value. Make sure the attach to shell and snap to node options are turned off in fe options. Select a DvsT file, which determines the size of the hexa based on the thicknesses of the components being connected. If no DvsT file is selected, hexas are created with weld nugget diameter =1.0. Click realize.
6. 7. 8.
9.
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
User Profiles
The HyperMesh user interface can be configured according to your specific needs and saved as a user profile. The configuration can include loading a specific template, loading a specific Utility menu, renaming panels, removing unused panels or sub-panels, and removing, moving, or renaming panel options. A set of standard user profiles is included in the HyperMesh installation. They include Abaqus, Actran, Ansys, HyperMesh, LsDyna, Madymo, Moldflow, Nastran, OptiStruct, Pamcrash, Permas, Radioss, and an interface customized for CFD uses. Note that the user profiles change the appearance of a panel - they do not affect the internal behavior of each function. They may, however, add functions to (or remove them from) a panel. Note: Ensure that items required for a specific function are not removed from the interface.
Select User Profiles from the Preferences pull-down menu. Once you choose a standard user profile, the appropriate template and Utility menu load (you can return to the standard HyperMesh GUI by selecting the HyperMesh profile). The current user profile displays on the header bar. The hmmenu.set file keeps track of which user profile was last loaded. User profiles for the following products are included: HyperMesh OptiStruct ABAQUS ACTRAN ANSYS LS-DYNA MADYMO NASTRAN PAM-CRASH & PAM-CRASH2G PERMAS RADIOSS CFD
Altair Engineering
HyperMesh User Profile

Template: None/Unchanged This user profile does not load a template. If a template file exists before loading the profile, the template remains the same. Utility menu: Panel changes: The standard HyperMesh Utility menu is loaded. None
The HyperMesh user profile does not load a template. If a template file exists before loading the profile, the template remains the same. The standard HyperMesh Utility menu (hm.mac) is loaded.
Using HyperMesh
This section explains how to use a typical HyperMesh panel by description and example. It contains information about: Retrieving and Saving a HyperMesh Database Input Collectors Viewing Models Using the Display Panel Setting View Options Setting Tolerances Setting Global Parameters Importing and Exporting Data Printing Screen Images Using the Card Previewer

Altair Engineering
Retrieving and Saving a HyperMesh Database

Using the File pull-down menu The simplest way to open or save a HyperMesh model database is to use the Open, Save, and Save As options located in the Files pull-down menu. Open and Save As both invoke browsers so that you can navigate to the desired file directory and either select a file to open, or type in a name for the file to be saved. Save simply saves the current model under its current name, updating/overwriting its older version each time you Save. Using the Files Panel However, you can also use the hm file sub-panel on the files panel to save and retrieve HyperMesh binary databases. This process is familiar for users of HyperMesh 7.0 and earlier, but can be less efficient than using the File menu. To retrieve a binary HyperMesh database, open the files panel by clicking the files toolbar button, and then select the hm file sub-panel. Next, click retrieve..., select a file using the Open file... dialog, and click Open. To save a database, open the files panel by clicking the files toolbar button, and then select the hm file sub-panel. Next, click save. You can also click save as..., select a path and file name, and click Save. If the file being saved already exists, HyperMesh asks for confirmation before overwriting the file.
Altair Engineering
Picking Entities on the Screen

After you select the correct data type, you can use the mouse to pick the desired entities in the graphics area of the screen. Each type of entity has a pick handle that allows you to select the entity. Note: For more information about picking entities, see Entity Selection. You can set the default mode for the graphics mode you wish to use by activating/deactivating the *graphicengine(mode) command in the hm.cfg command file. You may need to change the command if the default has been changed by a prior user. The following list indicates the pick handle locations for each type of entity: Nodes The pick handle for a node is located at the node. To select a node, move the mouse to the location on the screen where the node resides. If you need to select nodes on geometry or on an element where nodes do not currently exist, see Picking Nodes on Geometry or Elements. Elements Shell and solid element pick handles are displayed as pixels at the centroid of the element. 1-D element pick handles are displayed as letters at the centroid of the elements: K M BAR2 BAR3 R RL W RBE3 J ROD GAP spring masses bar2 bar3 rigid rigid link weld rbe3 joint rod gap
Click the element handles check box on the modeling sub-panel on the options panel to switch on or off the display of element handles. Element handles can be selected whether or not they are displayed. Lines Each segment of a line has pick handles along its length. Each pick handle is displayed as a small "+." If there are many pick handles, a "+" is displayed at only some of the pick handles. Click geom handle on the modeling sub-panel on the options subpanel to switch on or off the display of line handles. Line handles can be selected whether or not they are displayed. Surfaces Components Surfaces do not have pick handles. Surfaces can be selected along their edges or on interior UV lines (also known as surface lines). Components do not have pick handles. A component can be selected by picking an element, line, or surface within that component. The pick handle for a coordinate system is located at the origin of the system.
Systems

Altair Engineering
System Collectors Loads Load Collectors Plots Blocks
System collectors do not have pick handles. To select a system collector, simply select a system within that system collector. The pick handle for a load is located at the pick handle of the entity to which the load is applied. Load collectors do not have pick handles. To select a load collector, simply select a load within that system collector. A plot can be selected by picking within its border. Blocks do not have pick handles. Blocks are drawn in shaded mode with transparency and can be selected by picking anywhere on the entity.
Titles Vectors Curves Note
A title can be selected by picking within its bounding box. Vector pick handles are located at the arrow tip of the vector. A curve can be selected by clicking anywhere along the curve. To facilitate the selection of graphical entities such as nodes, elements, or loads, when several of them are coincident (present at the same location), you can turn on the coincident picking option from the modeling sub-panel of the options panel (accessed from the toolbar).
Altair Engineering
Picking Nodes on Geometry or Elements

Node and node list input collectors allow you to not only pick existing nodes in the model; they also allow you to create new nodes on geometry or on elements. You can create a node on geometry by holding the left mouse button down along the geometry handle until the cursor becomes a square and then selecting the geometry (lines, edges, surfaces) on which you would like to place a node. Then move your cursor to the exact location on the geometry where you would like the node to be placed and click the left mouse button to place a node. You can create nodes on elements by holding the left mouse button down on an element handle until the cursor becomes a square and selecting the element. Then move the cursor to the exact location on the elements of that component and click the left mouse button to place the node. To select new nodes on geometry: 1. Position the cursor on a node and press the left mouse button. The cursor becomes a small white box 2. 3. 4. .
Continue to hold the left mouse button down and use the mouse to move this special cursor box close to the desired geometry entity. While the line/surface is highlighted, release the left mouse button to select it. While the line or surface is highlighted in this manner, you can select nodes at the desired location(s) on the geometry.
You can create temporary nodes on an element (similar to creating a node on the fly on a line or surface). This function can be accessed from any node collector in any panel. This function allows you to create welds at locations that do not have pre-existing nodes. To select new nodes on elements: 1. When you are in a node collection mode, position the cursor on an element handle and hold the left mouse button down. The cursor becomes a small white box and the element is highlighted. 2. 3. Release the left mouse button. Move your cursor to the exact location on the element where you want to add a node and click the left mouse button. A temporary node is created at that location and is selected in the node collection for the panel.

Altair Engineering
Using the Extended Entity Selection Menu

The extended entity selection menu provides a number of entity selection options. To access the extended selection menu, click the data type button on the current input collector.
Input Collector
Extended entity selection menu. You can then select an option from the extended entity selection menu. These selection options are displayed for all of the entity types in HyperMesh. Selections that are not valid for the current entity type are displayed in dimmed text. Extended selection techniques are described in the following table: all Allows you to select all entities of the specified type. When you select all, the set to be added to the user mark includes entities displayed and those not displayed. Allows you to select entities adjacent to the entities already selected. When you select by adjacent, HyperMesh includes the entities that are adjacent to the entities already selected. Allows you to select entities by assembly. When you select by assems, HyperMesh displays a list of the available assemblies. You may select multiple assemblies from this list. Allows you to select entities by specifying an entity among a large group of continuously connected elements. When you select by attached, HyperMesh includes the entities currently displayed that are attached to the entities already selected. Entities that are not displayed will not be selected although they may be attached to the entity selected. Allows you to select elements, lines, surfaces, loads, coordinate systems, vectors, equations, and points by collector. When you select by collector, HyperMesh displays a list of the available collectors. You may select multiple collectors from this list. If you select component collectors in regard to elements or lines, the elements or lines contained in the selected components are selected. With all other entities, the entities selected by this operation are those attached to the selected component.
by adjacent
by assems
by attached
by collector
Altair Engineering
by config
Allows you to select elements by configuration and type. When you select by config, HyperMesh displays a panel for specifying an element configuration and type for selection. The element type is dependent on the template file specified in the global panel. Allows you to select entities by surface face. It finds surfaces and elements that are attached to each other without crossing a feature line. The feature angle parameter in the options panels modeling sub-panel determines the feature lines. Attached, adjacent surfaces or elements are progressively selected when the angle between them is less than or equal to the specified feature angle. Allows you to select entities by group. When you select by group, HyperMesh displays a list of the available groups. You may select multiple groups from this list. Allows you to select entities by typing in their ID numbers. When you select by id, a pop-up window prompts you to type ID numbers or ranges of ID numbers. You can use keywords to specify a range that determines which entities are selected. The standard format is: <start number> - <end number> by <increment value> "through", "thru", or "t" may be substituted for the dash (-), and the letter "b" may be substituted for "by" when you specify the range. Examples of valid by id expressions: 127 127 722 300 through 600 300 thru 600 300 t 600 1000 - 2000 by 100 1000 - 2000 b 100 You can also use a comma to separate individual entities or entity ranges. Examples of valid lists of by id expressions: 1, 3, 4, 5, 100 3, 5, 8 - 10, 800, 850 1 - 100 by 2, 77, 400 t 500 b 3
by face
by group
by id
by include
Allows you to select FE entities such as elements, loads, groups etc. that belong to selected include. When you select by include, HyperMesh displays a list of the available includes that you may select. Note: Includes created via the include browser are only valid for solvers that support them.
by output block
Allows you to select the nodes, elements, comps, systs, groups and mats within an outputblock. When you select by output block, HyperMesh displays a list of the available output blocks from which you may select. Output blocks are created in the output blocks panel.

Altair Engineering
by path
Allows you to pick multiple nodes or lines, and selects all the nodes/lines that fall in the closest path connecting the selected ones. If you select two nodes on a free edge of some elements, the function tries to find the closest path along that free edge. This function uses the connectivity of the elements between the nodes, and thus requires the selected nodes to be part of a continuous shell mesh. Similarly, by path for lines uses the connectivity of surfaces/solids and thus requires the selected lines to be surface/solid edges. Allows you to select the entities within a set. When you select by sets, HyperMesh displays a list of the available sets from which you may select. Sets are created in the entity sets panel. Allows you to select the entities which are associated to a surface. When you select by surface, HyperMesh displays a panel from which you may select one or more surfaces. Once the surfaces have been selected, click select and HyperMesh selects the entities which are associated to the surfaces. You can associate entities to a surface in the node edit panel. Allows you to select entities inside a user-defined multiple-sided polygon in the plane of the screen. Selecting by window activates the build window panel. Select points in the graphics area to define a window enclosing the pick handles of the desired entities. Click select entities to highlight the enclosed entities. Alternatively, click reject entities to deselect enclosed entities that were previously highlighted. Allows you to select surfaces by width, either by picking a sample surface or by specifying a range of values for the width. Allows you to select all of the entities currently displayed on the screen. When disp is selected, all entities within collectors that are active in the disp (display) panel are selected. Allows you to duplicate the currently selected elements, lines, surfaces, or points. When you select duplicate, a pop-up window allows you to choose a component for the newly created duplicate entities. Select current to place the new entities in the currently active component collector, as shown in the global panel. Select original to place the new entities in the same component collectors as the original entities. The initially selected entities are deselected when the duplicate elements are created and selected. This can be very useful when you use the reflect function on a model (only available for elements and lines). Allows you to select a group of entities whose pick handles reside on a plane. This is useful when you want to apply constraints to a plane. Allows you to retrieve previously saved entities from the user mark. Entities can be saved to the user mark by selecting save in this popup window, or by selecting save failed in the check elems panel.
by sets
by surface
by window
by width displayed
duplicate
on plane
retrieve
Altair Engineering
reverse
Allows for a Boolean "not" to be performed on the currently displayed elements. When reverse is selected, all selected elements are removed from the mark; all elements which are not on the mark and are currently active are selected. Allows you to save the currently selected entities to a holding area known as the user mark. Some panels in HyperMesh require only a single entity to collect; for example, origin in the systems panel requires only one node. The extended entity selection menu is not displayed in such situations. Some collectors, such as nodelist and linelist must remember the sequence in which the entities are selected. Thus their extended entity selection menu is different from that of the standard extended selection menu. The nodelist collector displays the following extended selection options:
save Notes:
by list by path
Allows you to select nodes individually in the desired sequence. Allows you to pick nodes (two or more) and selects all the nodes that fall in the closest path connecting the selected nodes. If you select two nodes on the free edge of the elements, the function tries to find the closest path along the free edge. This function uses the connectivity of the elements between the nodes and thus requires the selected nodes to be part of a continuous shell mesh. Allows you to review the nodes currently stored in the nodelist collector by numbering the nodes in the sequence of their selection. Allows you to select nodes by window and internally, the order of the nodes selected is determined based on its spatial location and element connectivity (if connecting elements exist).
show node order by window
The linelist collector provides the following extended selection options: by list by path Allows you to select lines or surface edges individually in the desired sequence. Allows you to pick surface edges (two or more) and selects all the surface edges that fall in the closest path connecting the selected edges. If you select two free (red) edges, the function tries to find the closest path along the free surface edges. Since this function uses the connectivity of the surfaces, it only works with surface edges and not free unconnected geometric lines.

Altair Engineering
Viewing Models
The functions on the Toolbar Area allow you to control the view of your model. The view commands are accessible even when you are using other panels. The viewing functions allow you to:
Setting Basic Views

The view pop-up menu allows you to display your model in several basic views, reverse the view, or rotate the model in clockwise or counterclockwise directions. The save and restore options allow you to save, identify, and restore different views of your model.
View pop-up menu.
Using View Rotation

There are multiple methods you can use to rotate a displayed model. Use the left, right, up, and down arrow keys to rotate the model incrementally. Hold down the ctrl key, then click-and-drag on the model in the graphics area. Click the user view button in the Toolbar Area to access the view menu; then click cw (clockwise) or ccw (counterclockwise).
The view menu
Changing the Window

The window viewing options allow you to zoom in and out of the currently displayed window, specify an area to see in closer detail, fill the window with the model, and refresh the screen. The following window viewing options are included as default keyboard shortcuts: z + and f p s Circle zoom: click-and-drag the mouse to draw a circle. The view zooms to that circle when you release the mouse button. (Numeric keypad) Current Window Zoom Fit to screen Plot (refreshes the rendering in the Graphics Area). Slide zoom; click-and-drag the mouse to zoom in and out. Release the mouse button to stop zooming.
Altair Engineering
CTRL - right click allows you to drag the model. To use the mouse to zoom in and out: 1. 2. 3. Press the s key. Click and hold the mouse button. Slide the mouse: or 4. down to zoom in up to zoom out
Release the mouse button to end the zoom function.
To perform a circle zoom: 1. Press Z on the keyboard. HyperMesh displays a message requesting you to circle the area of the model to be more closely investigated. 2. Move the mouse to the appropriate area on the screen and hold the left mouse button down. With the mouse button still depressed, move the mouse to circle the area to be zoomed in on. A trailer line appears wherever the mouse is moved. The area circled is used to recalculate the window when the mouse button is released. 3. Release the mouse button.
To zoom in and out of the current window: 1. 2. Press + on the numeric keypad to zoom in. Press - on the numeric keypad to zoom out.
These two functions increase or decrease the current window by the user-defined factor specified on the modeling sub-panel on the options panel. To drag the model: 1. Simultaneously press and hold the CTRL key and the right mouse button. The cursor changes to dynamic center mode. 2. Use the mouse to drag the model to the desired position on the screen.
To fit the entire model on the screen: Press F on the keyboard.
Automatic full screen refreshes are kept to a minimum. If the screen appears messy or inaccurate after entities have been plotted and erased, press the p key or the plot refresh toolbar button to refresh the screen. The model and/or the window are not resized when you refresh the screen. To refresh the screen: Click the plot refresh toolbar button or press P on the keyboard.

Altair Engineering
Performing View Translation

Translation of the model, also called panning, is performed by selecting a new center for the current window. To change the screen center: 1. 2. Press C on the keyboard. Move the mouse into the graphics area. The current center is indicated by a small white box. 3. 4. Move the mouse to the point where you want the new center located and click the left mouse button. The center relocates. Exit by moving the mouse into the menu area, by clicking the right mouse button, or by pressing any key.
Return to the Previous View

To return to the previous view of your model, click the previous view button in the Toolbar Area or press b on the keyboard. This returns the screen graphic to the view before a rotation, zoom, center, or other viewing manipulation was performed. You can toggle between two views of a model by clicking (or pressing) repeatedly.
Altair Engineering
Using the disp (display) Panel

The disp (display) panel, located on the permanent menu, allows you to select which components and collectors are displayed on the screen. Access it by clicking the display button in the Toolbar Area or selecting Display > Collectors from the View pull-down menu. Components can be turned on and off by selecting the check boxes of the components in the display list. The colors of each component display next to the component names. In the default mode of the display panel, the switches (on the right-hand side of the panel) are set to comps and elems. At this setting, the elements in the selected components are displayed if the component (on the left-hand side of the panel) is selected. To change to another collector type: 1. 2. Click the upper switch. Select the type of collector you want to display.
To turn a collector off: 1. 2. Click the upper switch. Select the type of collector you want to remove from the screen display. A list of the collectors of the selected type is displayed on the left side of the panel. 3. Use the right mouse button to click the check box of the collector you want removed. Collectors can also be turned off by moving the mouse to the graphics region and picking an entity which they collect. To turn a collector on: 1. 2. Click the upper switch. Select the type of collector you want to display. A list of the collectors of the selected type is displayed on the left side of the panel. 3. Use the left mouse button to click the check box of the collector you want added to the display.
To turn on all the collectors of a specified type: 1. 2. Select the collector type. Click all.
To turn all the collectors off: Click none.
To change the collector list to display names, IDs, or both: 1. Click the lower switch and select (id) to display the collectors ID number instead of the name. The ID of the collector is displayed in parenthesis on the left side of the page. 2. Click the lower switch and select name (id) to display the name and the collectors ID number. The name and ID of the collector are displayed on the left side of the page. 3. Click the lower switch and select name to display the collectors name. The name of the collector is displayed on the left side of the page.

Altair Engineering
To reverse the selection: Click reverse to toggle between having all the selected components on or off.
To display geometry: Click the toggle and select geoms to display the surfaces and lines in a component.
To use a filter: 1. 2. Click the leftmost toggle to filter =. Enter the character string to use for the filter. You can use the asterisk (*) for a wildcard.
Altair Engineering
Setting View Options

The modeling sub-panel on the options panel (accessible via to toolbar or the Tools pull-down menu) allows you to define several viewing options. This sub-panel also allows you to specify node and cleanup tolerances; for more information see Setting Tolerances. Viewing option settings include: rotate angle The rotate angle specifies the number of degrees that your model rotates when you use the arrow keys. Increasing or decreasing the angle makes the model appear to rotate faster or slower. For smaller models, setting the rotation angle to a lower value allows a smooth transition from frame to frame. The pick tolerance specifies the maximum distance, in pixels, that the cursor can be from the pick handle of a graphical entity in order to select it. When the pick tolerance is increased, it is easier to pick an entity. The zoom factor specifies the multiplication factor that is used to increase or decrease the scale of the current view when you press the + and keys on the numeric keypad. The surf lines parameter specifies the default number of u-v lines to draw on new surfaces when they are created. Displaying surface lines can help you to visualize a surface better, but it can slow down the redraw speed of a large model. The number of surface lines on existing surfaces can be changed by using the surf lines panel. The element handles option specifies whether or not to draw element handles. An element handle is a single-pixel dot at the centroid of an element. Turning off pick handles can speed up the redraw time. The element handles option also allows you to display the center of gravity for multibody collectors and text labels for 1D elements. fixed points The fixed points option allows you to specify whether or not to display fixed points. This does not affect the display of free points. Fixed points can also be turned on and off from vis opts in the geometry cleanup panel. The geom handles option allows you to specify whether or not to display line and surface handles. The coincident picking option allows you to graphically select a desired entity from a stack of coincident entities when there are multiple entities at the same location. For example, if multiple loads are detected at the same location, a circular insert pops up containing various loads displayed separately with their IDs turned on. You can then pick the appropriate load. This function is activated by turning on coincident picking in the options panel. The entities supported for coincident picking are nodes, elements, loads and systems. This option allows you to display the element labels as template names or HyperMesh names.
pick tol
zoom factor
surf lines
element handle
geom handle coincident picking
template labels/ HM labels

Altair Engineering
Shrink
The shrink option controls the shrink factor to be used when drawing elements. If no shrink is selected, each element is drawn so that its corners directly connect to its nodes. If a shrink value is applied, the element is scaled by the specified value about its centroid, so that its corners do not appear to touch its nodes. The shrink value must be between 0 and 1. Shrinking elements is a convenient way to detect holes in a mesh and to improve wireframe element picking.
Component Display The graphics engine treats each HyperMesh component as an independent unit. This feature allows you to assign a set of display attributes to each component of your model that determines how each component is displayed. The display attributes that you can assign to each component are: Wireframe Element edges display with lines.
Hidden Line
The element displays as a filled polygon.
Hidden Line with Mesh Lines
The element displays as a filled polygon with the edges drawn in mesh line color.
Hidden Line with Feature Lines
The element displays as a filled polygon with the "feature" edges drawn in mesh line color.
Transparent
The element displays as a filled transparent polygon.
Display attributes can be applied to all components by using the wireframe elements and shaded elements toolbar buttons. They can be applied to individual components or sets of components through the Visual Attributes panel. Access this panel by opening the View pull-down menu, then selecting FE Styles. Entity Selection The graphics engine allows you to select entities by moving the mouse anywhere along the entity of interest. For lines and surfaces, it is much easier to work when you are zoomed in on a particular area, as you are not required to have a pick handle on the screen in order to pick the entity. Another key feature in the graphics engine is the method by which nodes are selected. To select a node, select the element to which the node of interest is attached. HyperMesh selects the node closest to the point where the element was selected. The benefit of this feature is that it allows you to create zero length elements between two coincident nodes in a mesh. For nodes that are not attached to any elements, HyperMesh allows you to select the node by picking the "node sphere" on the screen.
Altair Engineering
User Features of the Graphics engine When you are post-processing, the graphics engine offers advanced and powerful features: Cutting plane Cutting plane functions have been expanded to allow three planes to be active simultaneously. Cutting plane control is more interactive and is controlled by selecting any of the active planes with the mouse and then dragging the plane across the model. The cutting plane feature can be found in the hidden line, contour, and animation panels. The isosurfaces sub-panel is available on the contour and animation panels. Isosurfaces can be displayed on a model in either a legendbased mode in which each of the legend colors generates an isosurface, or as a value-based surface in which you specify a value that indicates where an isosurface should be displayed. If one or more of the components in a model are set to a display style besides wireframe, then HyperMesh draws the whole model in hidden line. To perform this task, HyperMesh relies on the zbuffer found on your graphics device. The zbuffer allows HyperMesh to render your model in hidden line, with the elements in back eliminated from the display. There are some limitations to using a zbuffer and some display output differences of which you should be aware. One problem with using the zbuffer technology is that if two entities lie in the same location in space, or nearly the same location in space, the zbuffer may have difficulty deciding which entity to display. If this situation occurs, you might see a "dotting" or "stitching" effect where the zbuffer considers one entity to be closer to you at one pointer, and then another entity closer to you at another. Potential areas of zbuffer stitching are in the features, edges, and faces panels. Here, since HyperMesh is creating entities that reside in the same location in space as another entity, the display lines which represent the edges (for example) might be partially or completely blocked out by the original entity in the database. If this occurs, you can turn the zbuffer off by making all of the components in your model wireframe. In some cases, it may help to use the shrink option (modeling sub-panel on the options panel). When a component is set to hidden line, the interior is filled with solid color. This can make it very difficult to see a node. To correct this situation, the graphics engine draws all selected or temporary nodes as spheres when one or more components are set to a display attribute other than wireframe. Optimization The graphics engine optimizes the display of your finite element model. One of the optimizations is the removal of interior solid faces. If you have solid elements in your model, HyperMesh calculates where the external faces are in your model, and displays these instead of displaying all of the faces. HyperMesh graphics use some memory. If swapping occurs while you are running HyperMesh, this could seriously affect performance. If you encounter this problem, you should obtain more system memory.
Isosurfaces
Hidden components
Memory usage

Altair Engineering
Setting Tolerances
The modeling sub-panel is located on the Options panel, which is accessible from the toolbar or from the Tools pull-down menu. This sub-tab allows you to define tolerance values. These tolerance values include: node tol Node tolerance is essentially the resolution to which HyperMesh maintains the finite element data in the model. When you specify a node tolerance, HyperMesh considers any two nodes to be coincident if the distance between them is less than the value. "Cleaning up" refers to cleaning up the CAD geometry data by equivalencing edges, deleting fillets, and eliminating extraneous vertices. The cleanup tolerance value specifies how much HyperMesh is allowed to modify the geometry in the course of "cleaning" it. Since you will approximate the geometry with a finite element mesh, you need to work with a cleanup tolerance that is less than the node tolerance used in the mesh generation.
cleanup tol
Since the objective is to make a finite element mesh for the geometry, the tolerance values are determined by the demands for that mesh. You need to approximate the size of the elements that make up the smallest feature of importance in your model. HyperMesh attempts to make a reasonable guess at this value when you import a CAD file, and initializes the tolerances as appropriate, but without additional input it uses a cautious estimate. Element size Node tolerance min max 0.1 1.0 10.0 100.0 1e-4 0.01 1e-3 0.1 0.01 1.0 0.1 10.0 Cleanup tolerance min...max 1e-4 0.01 1e-3 0.1 0.01 1.0 0.1 10.0
Setting Global Parameters

The global panel, accessed by selecting Global Parameters from the Model pull-down menu, controls model parameters that are accessed by several different panels. These parameters remain constant until changed. Use this panel or the template sub-panel on the files panel to specify the template file you want to use. The global panel controls which components or collectors are active; any entities created are stored in the active collectors. Elements are designated as first order elements by default. If you want to create second order elements, click the toggle after element order: to second.
Altair Engineering
Importing and Exporting Data

The import sub-panel on the files panel allows you to input external CAD line and surface data or finite element models. The CAD formats currently supported are IGES, PDGS, DXF, VDAFS, CATIA, UG, STL, HM ASCII, PRO/E, and STEP. You can also import/merge HyperMesh model files (.hm) into the current model session. The FE formats we support are Optistruct, Abaqus, Ansys, Cmold, Moldflow, Nastran, Patran, Marc, Ls-Dyna, Pamcrash, Radioss, HyperMesh ascii, and Ideas. The CUSTOM interface allows you to import models using your own custom-built translation package. The custom option can be used to import models using a translator provided with the HyperMesh installation but cannot be accessed via the pop-up menu. The export sub-panel on the files panel allows you to write information from a HyperMesh database to many finite element formats. Geometry data can be written in IGES format. HyperMesh uses templates to create the analysis input decks for finite element solvers. You can modify the existing templates to support a desired feature or create a new template to support another analysis code. The HyperMesh templates can be used to create model summaries and perform some analysis calculations. You can also use the templates to perform complex editing or data manipulation tasks. To import multiple files: 1. 2. 3. 4. 5. 6. 7. Click the file pull-down menu. Click import to open the import sub-menu. Click multiple files. The Multiple File Import window opens. Click the open folder icon in the directory field to open a browser. Browse to and select the directory that contains the models you wish to import. Select the desired file type. Select the desired file extension to limit the files that display in the files to import list. Select the desired files in the files to import list: Left-click to select a single file. <ctrl>-click to select multiple files one at a time. Click the button to select all of the files in the list.
Click the button to invert the selection (deselect any currently selected files and select any currently non-selected ones). This is useful in cases when you want to choose most of the files in the list, but not all; you can select the ones you dont want and then invert the selection. Click the button to deselect all of the files in the list.
Selected files are highlighted to indicate their selection. 8. Click Import to import the selected files. The window minimizes during the import process, and a secondary window opens to show the import progress and any errors that may occur. Click Close to close the Multiple File Import window. Altair Engineering
9.

To read data using a standard translator: 1. 2. 3. 4. Select the import sub-panel on the files panel. Select the FE option. Select the data format that corresponds to your input data from the pop-up menu. For file:, click import... and use the browser to select the file containing the data.
To read data using a custom translator: 1. 2. 3. 4. Select the import sub-panel on the files panel. Select the CUSTOM option. For translator:, click browse and choose the translator required to read the file. For file:, click import... and use the browser to select a file.
To write geometry data in IGES format: 1. 2. 3. 4. Select the export sub-panel on the files panel. Select IGES. Click write as... and enter the name of the output file or select. Select IGES. A column of switches and toggles appears on the right, if they are not already present. 5. 6. 7. 8. 9. Click the upper switch and select the plane format of the data. Click the toggle and choose either outer loop optional or outer loop mandatory. Click the lower switch and select layers, groups, or layers & groups. Click the toggle to select all or displayed to specify whether you want all your model data to be exported or only the entities that are currently displayed. Click write. (Note that the IGES interface exports geometry only.)
To create an analysis deck via an external translator: 1. 2. 3. 4. 5. 6. Select the export sub-panel on the files panel. Click filename = and enter the name of the output file. Select EXTERNAL. A new input field, template = appears if it is not already present. Click template = and specify the file name of the template file. Click the toggle to select all or displayed to specify whether you want all your model data to be exported or only the entities that are currently displayed. Click write.
Altair Engineering
Printing Screen Images

The postscript sub-panel on the options panel allows you to modify the default print specifications before you create a PostScript file. To create a PostScript file: 1. 2. Open the File pull-down menu. Select Image > PostScript. A PostScript file with the name post?.* is generated. The ? is a number provided for file uniqueness, and * is an extension (either eps for a PostScript file whose destination is the hard disk, or psp for a PostScript file whose destination is the printer). To change PostScript settings file: 1. 2. 3. Select Options from the Tools pull-down menu. Select the PostScript sub-panel. Set the options to your print specifications.
To print an imported encapsulated PostScript image in MS Word, you must have a PostScript capable printer installed. You can check this by selecting Print from the File menu to show the print dialog box and pressing the Properties button next to the printer name. If the printer selected is capable of printing PostScript, a PostScript tab is present in the properties dialog. To set MS Word to send the imported file as a PostScript image to the printer, press the Options button in the print dialog. Make sure the option Print PostScript over text is selected. If it is not selected, the PostScript preview or file information is printed instead of the actual PostScript image. The following options are available in the options panel, postscript sub-panel: color checkbox Activate the color checkbox to print in color. Deactivate the color checkbox to print in black and white. The color checkbox is active by default. reverse video generate bitmaps fill to page fill model bitmap preview Select reverse video to indicate that your printer cannot produce reverse video images. Select generate bitmaps to generate a bitmap PostScript file. Select fill to page to fill the PostScript image to the specified page dimensions. Select fill model to expand the model to its maximum size within the graphics area of the PostScript page. Select bitmap preview to generate an image that can be viewed when you view the file in another document. The generate bitmaps option must be off if you select this option. Select plot optimize to decrease the size of the PostScript file generated. This requires processing time to optimize the image output. Click page length = and enter the new size to alter the page length. The standard page length is 11.0 inches.
plot optimize page length =

Altair Engineering
page width = image size = line width = print it standard/enhanced
Click page width = and enter the new size to alter the page width. The standard page width is 8.5 inches. Click image size = and enter the new size to scale the image on the page to your specifications. Select line width = and enter the new width to alter the line width. Select print it to send a copy of the file to the printer when you generate the PostScript file. Click the toggle to standard/enhanced to change the postscript file resolution to print blended contours. The enhanced option allows you to print blended contours (not discrete). It creates a smaller PS file, but takes longer to generate. If you select enhanced, a slider bar is displayed. The slider controls the smoothness of the gradient fill of the blended contour. The resolution is displayed in the header bar.
Printing Screen Images Using Keyboard Commands

You can also use the following function keys in combination with the CTRL key to print and/or save screen images without accessing the postscript sub-panel. CTRL-F1 Creates a bitmap file of the screen and spools it to the printer. This command executes the operating system command in the *screenfile() function as set up in the HyperMesh configuration file, hm.cfg. On UNIX platforms, the default installation does not spool the bitmap file to the printer. CTRL-F2 Creates a bitmap file of the screen and writes it to disk. This command executes the operating system command in the *screenfile() function as set up in the HyperMesh configuration file, hm.cfg. Creates a PostScript file of the screen and spools it to the printer. This command executes the operating system command in the *postcopy() function as set up in the HyperMesh configuration file, hm.cfg. (Note: This works only in UNIX.) Creates a PostScript file of the screen and writes it to disk. Creates a black and white PostScript file of the screen and spools it to the printer. Generates a *.jpg screen capture or animation file. In order for the functions to work correctly, your systems administrator must configure these functions for your system. If the functions do not create output, please contact your systems administrator.
CTRL-F3
CTRL-F4 CTRL-F5 CTRL-F6 Note:
Altair Engineering
Using the Card Previewer

A control card may be in one of three states: State Undefined Defined (See note.) Inactive Note: Color Gray Green Red Explanation The control card was either never created or has been deleted. Any control card viewed in the card previewer is activated. A card that has been defined may be disabled. The attributes for that card remain; however, the control card is not output.
Those control cards that are defined (green in the control card editor) are output.
Default values for attributes are common throughout the card previewer. A default value field has two states: State Default = ON Default = OVERRIDDEN Description In this state, the field label color is yellow and no data entry is allowed. To override a default value field, pick the yellow field label. When you override a default value field, the label text color changes to cyan, and allows you to enter data in the field.

Altair Engineering
General Process for Building Models

This section describes how to build a finite element model in HyperMesh. In general, the following building process is used: Create collectors Obtain line and surface geometry from an external file, or hand digitize the data Reconcile conflicts in the geometry and prepare it for use Build the model by using element-building panels Verify the quality of the model Create boundary conditions and systems
Altair Engineering
Creating Collectors
All entities in a HyperMesh database are stored in collectors. Based on the assigned template, each collector may use a dictionary or card image to define the attributes assigned to the collector. HyperMesh uses the definitions contained in the dictionaries or card image to translate models to external analysis codes. Note: For more information about the types of collectors used in HyperMesh, refer to Collectors in Database Design.
The collectors panel allows you to create and update collectors and assign and edit card images or dictionaries. Before you build a model in HyperMesh, create a component collector for the lines and surfaces. To create a collector: 1. 2. 3. 4. 5. Select the collectors panel. Select the create sub-panel. For collector type:, click the switch and select the type of collector that you want to create. Click name = and enter a name for the collector. Click the switch under creation method:.

Select no dictionary or no card image if you do not want to assign a dictionary or card image. Select dictionary or card image and then click dictionary = or card image = to select the dictionary or card image from a list. Select same as and then click same as = to select the collector whose type and dictionary or card image information you want to copy from an existing collector.
6.
If you are creating a component or property collector, select material = and enter a name for the material, if desired. You are not required to provide a material name when you create a component or property. If you choose not to, HyperMesh automatically creates a material for you and gives it the same name as the component or property. Where available, click color and select the desired color for the component from the pop-up menu. Click create.
7. 8.
To create a component: 1. 2. 3. 4. 5. 6. 7. Select the collectors panel. Select the create sub-panel. Click the upper switch and select comps. Click name= and enter comp1. Click the switch under creation method: and select no card image. Click create. Click return.

Altair Engineering
Reading Geometry
HyperMesh imports CAD geometry (such as lines, surface data, and point data) in the following formats: CATIA (V4 and V5), Unigraphics, PDGS, VDAFS, IGES, DXF, Pro/E, Parasolid, ACIS and STEP. The types of geometric entities and organizational information imported vary for different formats; please review the individual CAD translator topics for additional information. To import geometry: 1. 2. 3. 4. 5. Select the import sub-panel on the files panel. Select the Geom option. Select the appropriate file format to be imported from the pop-up menu. Click import to invoke the file browser and select the file that contains your geometry data. Click Open to import the model into HyperMesh.
Using the toggle, select use automatic cleanup tol to use the cleanup tolerance associated with the geometry of the imported file, or select cleanup tol and enter a tolerance value. Using the toggle, select create blanked component or no blanked component. Blanked components are geometric data that exists in the CAD file but is marked as not displayed or turned on.
When the geometry is read into the current database, HyperMesh creates a new component if an active component does not already exist.
Altair Engineering
Creating Geometry Data

If geometry is not available from a CAD system, you can create or edit geometry using the line and surface builders. The panels used in this process are listed below: lines creation and editing panels lines line edit circles Create lines in a variety of methods, including: from points, at tangents, and at the intersection of other geometry. Edit existing lines in a variety of methods such as combine, split, smooth, or extend. Create circles or arcs.
surfaces creation and editing panels surfaces primitives surface edit defeature Create surfaces from existing lines or nodes by different methods, such as spline, drag, or spin. Create standard shaped surfaces or solid entities, including squares, spheres, cones, and cylinders. Edit existing surfaces by trimming, extending, or shrinking. Edit existing surfaces by removing individual features such as holes or fillets.
point/node creation and editing panels nodes temp nodes Create new nodes. Several methods are available. Add or remove nodes used only for geometry creation or editing.
Creating NURBS surfaces

A NURBS (non-uniform rational B-spline) surface is a parametric surface defined by control points, knots and weights. The ruled, spline/filler, and drag/spin sub-panels of the surfaces panel can be used to create NURBS surfaces. The spline option creates a surface through 3-D lines. If you select a set of lines that do not form a closed loop, HyperMesh will connect the disconnected lines with straight lines, and create a spline surface and/or mesh in the enclosed area. There is no limit on the number of lines used to create a mesh/surface.
These lines form one path because they intersect at four points.

Altair Engineering
These lines form more than one path and cause an error. The tolerance setting on the options panel is used to determine the intersections between lines. If the tolerance is too small and an intersection cannot be found, HyperMesh reports an error when you attempt to create the surface. Lines that contain sharp edges can cause problems when you create a surface. These lines result in a more complex surface, which takes longer to create, and slows the automeshing process. These sharp edges are sometimes the result of data created on other CAD/CAM systems and brought into HyperMesh via a translator. These lines may need to be "smoothed" by using the line edit panel or replaced with a new, smooth, line by using the lines panel.
Creating a surface with these lines results in a relatively complex surface.
Altair Engineering
The "circular" shaped line has been replaced with a smooth line, which results in a much simpler surface. In some cases the sharp edges are required to represent the model and should not be smoothed. The skin option can create a skinned surface through a set of lines.
Lines used to define a skinned surface.
A skinned surface created from the lines.

Altair Engineering
The ruled option can create a ruled surface between two lines.
Lines used to create a ruled surface.
A ruled surface created from the lines.
Altair Engineering
Temporary Nodes
A temporary node list retains nodes that are not attached to an element, protecting them from automatic removal by HyperMeshs database management (except for some panels that automatically clear all temporary nodes, i.e., edges, faces, edit elements). There may be times when you wish to use an unattached node later in the modeling process. The temp nodes panel allows you to modify the temporary node list. In the temp nodes panel, there are three functions: add clear clear all Adds selected individual nodes to the temporary node list. Removes selected individual nodes from the temporary node list. Removes all the temporary nodes from the database.
Picking Surfaces
In HyperMesh, you can display surfaces in wireframe mode or in shaded mode. In wireframe mode, the easiest method of selecting a surface is to pick the surface near its edges or surface visualization lines. If several surfaces share an edge, you can select any one of them by clicking on the edge, and while holding the mouse button down, moving the mouse slightly from side to side. Each surface highlights as selected. Release the mouse button when the desired surface is highlighted. In shaded mode, click anywhere on the surface to select it. Similar to wireframe mode, you can hold the left mouse button down until the surface of interest is highlighted, and release it to confirm the selection. Surface edges may be used in the same way as lines in any surface creation panel, where appropriate. If you use any surface edge lines in the line edit panel, duplicates of the lines are created and the operation is applied to the duplicates.

Altair Engineering
Editing Surfaces
Each HyperMesh surface contains one or more faces. It is usually preferable to combine multiple faces into one surface entity before you use the meshing tools. This allows them to be meshed at the same time. You can use the surface edit panel to modify surface geometry when it is necessary to make changes before you generate a mesh. For example, to trim a surface with a line, use the trim with line sub-panel of the surface edit panel. You must select the surface and the line and specify a direction vector. The surface is trimmed by sweeping the line along the vector and intersecting the surface with the sweep. If the sweep does not intersect the surface, the surface is not trimmed. The features and automesh panels have a cleanup sub-panel, which contain surface editing tools.
A circle and a surface (represented with surface lines) before trimming.
After the circle is used to trim the surface, two new surfaces are created (shown highlighted) and the original surface is trimmed.
Altair Engineering
To trim one surface with another, use the trim with surf sub-panel.
Two surfaces before trimming.
The smaller surface is split into two surfaces after it is trimmed with the larger surface.

Altair Engineering
Associativity
Nodes and elements can be associated to surfaces. When you create a mesh with the automesher, the nodes are automatically associated to the surface. When nodes are associated to a surface, you can use the smooth panel to smooth elements on the surface and the node edit panel to move the nodes along the surface. Associated nodes and elements can be selected by surface, which allows you to select all the nodes and/or elements associated to a surface. Some operations break associativity. If you transform, such as translate, a surface, node, or element, associativity is broken. However, if you transform a component that contains both a surface and its associated nodes/elements, the associativity is not broken. Associativity is also broken if you trim a surface. To re-associate a node to a surface, use the node edit or project panel. Note: Re-associating nodes to a surface is usually a time consuming task.
Altair Engineering
Geometry Cleanup
When designers create CAD geometry, their priorities are different from those of analysts trying to use the data. A single smooth surface is typically split into smaller patches, each a separate mathematical face. The juncture between two surfaces often contains gaps, overlaps, or other misalignments. To make the geometry more appropriate for meshing, analysts need to combine a number of faces into a single smooth surface. This allows the elements to be created on the entire region at once, and prevents unnecessary artificial or accidental edges from being present in the final mesh. The quick edit, edge edit, point edit, and autocleanup panels contain tools to help you prepare surface geometry for meshing.
The initial CAD geometry often contains gaps, misalignments, or pinholes.
These features can distort the elements or demand a finer mesh.

Altair Engineering
With the tools of the geometry cleanup panels, you can close the gaps between surfaces, combine surfaces into large meshing regions, and eliminate pinholes.
Using the simpler, cleaner geometry, you can easily build a much better mesh.
Altair Engineering
Building Elements
After you create or obtain geometry data, you can build elements directly on the geometry. This section describes the element types and indicates which panels you can use to build the elements.
Building 0-D Elements

The 0-D elements currently supported in HyperMesh are masses. Masses have the ability to store one node, a value of mass, and a property reference. Masses can be created in the masses panel.

One-dimensional elements currently supported in HyperMesh include bar2s, bar3s, rigid links, rbe3s, plots, rigids, rods, springs, welds, gaps, and joints. The following list indicates the storage capabilities and purpose of each of the 1-D elements. 1-D Element Bar2 Stores A property reference A local axis vector Pin flags Offset vectors Optional orientation nodes Bar3 Property reference Local axis vector Pin flags Offset vectors Optional orientation nodes Gap Joint Property reference Property reference Optional orientation nodes or system(s) Plot RBE3 Rigid link A reference to two nodes A degree of freedom at each node Weight at each node A degree of freedom code One independent node Multiple dependent nodes Rigid Rod Spring A degree of freedom code A property reference A property reference A degree of freedom code An optional orientation vector A degree of freedom code Supports rigid elements. Supports simple beams. Supports springs or damper. Supports rigid elements with multiple nodes. Supports gap elements. Supports kinematic joint definitions supplied with Safety Analysis Codes. Supports display type elements. Supports NASTRAN RBE3 elements. Supports complex beams. Note: bar3s contain a third node designed to supported second order beams. Purpose Supports complex beams.
Weld Note:
Supports weld elements.
The 1-D element-building panels are located on the 1D page of the default main menu. Plot elements are generated in the edit element, line mesh, elem offset, edges, or features panel. Altair Engineering


Three-noded trias, four-noded quads, six-noded trias, and eight-noded quads can all be built in HyperMesh. These two-dimensional elements can be built in any of the following panels: automesh cones drag edit element elem offset line drag planes ruled spheres spin spline torus Note: Builds elements on surfaces according to user specifications. Builds elements on conic or cylindrical surfaces. Builds elements by dragging a line, row of nodes, or group of elements along a vector. Builds elements by hand. Builds elements by offsetting a group of elements in the direction of their normals. Builds elements by dragging a line or group of elements along or about a control line. Builds elements on square or trimmed planar surfaces. Builds elements between two rows of nodes, a row of nodes and a line, or two lines. Builds elements on spherical surfaces. Builds elements by spinning a line, row of nodes, or group of elements about a vector. Builds elements that lie on a surface defined by lines. Builds elements on toroidal surfaces. By default, first order linear elements are generated when the functions in these panels are executed, but second order parabolic elements may be generated by changing the element order in the global panel.
Altair Engineering

HyperMesh builds 4- and 10-noded tetras, 6- and 15-noded pentas, and 8- and 20-noded hexa elements. Tetras can be built in the edit element panel by hand or by using the tetramesh panel. Pentas and hexas can be built in any of the following panels: drag edit element line drag linear solid solid map solid mesh elem offset spin split tetramesh Note: Drags a group of two-dimensional elements along a vector to create solids. Builds elements by hand. Drags a group of two-dimensional elements along a line. Creates solid elements between two-dimensional elements. Builds solid elements between nodes, lines, and surfaces. Builds solid elements between a variable number of lines. Creates solid elements by offsetting a group of two-dimensional elements normal to the surface formed by the group of two-dimensional elements. Spins a group of two-dimensional elements about a vector to create solids. Propagates split hexas. Fills with tetra elements a volume that is enclosed by tria elements or surfaces.
By default, first order elements are generated when the functions in these panels are executed, but second order solids may be generated by switching the element order in the global panel.

Altair Engineering
Checking Model Quality

After you build your model, you can use the check elems panel to verify the geometric quality of the elements in the model. You can check your model for connectivity and duplicate elements. The 1-d sub-panel allows you to: Check one-dimensional elements for free ends Determine if a group of rigid elements form a loop Check weld and rigid elements for double dependency Check all elements for a minimum length of a side
The 2-d sub-panel allows you to: Check elements for warpage, aspect ratio, skew, and jacobian ratio Check the maximum and minimum interior angles of quad and tria elements Check all elements for a minimum length of a side Check a mesh of elements for its maximum chordal deviation from a real or inferred surface
The 3-d sub-panel allows you to: Check elements for warpage, aspect ratio, skew, and jacobian ratio Check the maximum and minimum interior angles of quad and tria elements Check all elements for a minimum length of a side Check tetra elements for collapse, CFD-style volumetric skew, and NASTRAN-style aspect ratio
The time sub-panel allows you to check for elements whose small size might cause problems for an explicit solver. The group sub-panel provides a tool to check for and eliminate group or interface elements whose underlying structural element has changed and left them detached. The user sub-panel allows you to verify element quality by using a template file that checks for userspecified conditions.
Altair Engineering
Applying Loads
The final step in the model building process is to apply constraints and forces and to create or assign coordinate systems. Before you apply loads, create a load collector. Loads are displayed in the color assigned to the load collector. The size of loads and constraints is based on model units and can be modified from within the boundary condition panels. HyperMesh stores and displays all loads in the global coordinate system. Depending on the analysis code being used to calculate results, HyperMesh transforms the loads appropriately to any local nodal output coordinate system. HyperMesh currently supports the following load types: accelerations Applies an acceleration at a node. Accelerations are displayed as a single-headed arrow with an optional label, A. The label may also display the magnitude of the acceleration. Applies a constraint or enforced displacement at a node. Constraints are displayed as a triangle with an optional label that displays the degrees of freedom effected by the constraint. Applies a general equation constraint between nodes. Equations are displayed with the label, EQ. Applies a flux load at a node. Fluxes are displayed as a thick arrow with an optional label, flux. The label may include the magnitude of the flux. Applies a concentrated force along any user-defined vector at a node. Forces are displayed as a single-headed arrow with an optional label F. The label may include the magnitude of the force. Applies a concentrated moment about a user-defined vector at a node. Moments are displayed as a double-headed arrow with an optional label, M. The label may include the magnitude of the moment. Applies a pressure on an element or geometry. Pressures are displayed as a single-headed arrow with an optional label, P. The label may include the magnitude of the pressure. Applies a temperature constraint at a node. Temperatures are displayed as a straight line starting at the node at which the temperature is applied extending upward, with an optional label, T. Applies a velocity at a node. Velocities are displayed as a singleheaded arrow with an optional label, V. The label may include the magnitude of the velocity.
constraints
equations fluxes
forces
moments
pressures
temperatures
velocities
Note:
Refer to the specific panel for detailed information about creating, reviewing, and updating loads and constraints.

Altair Engineering
Creating Systems
Systems in HyperMesh are referred to as coordinate systems and may be rectangular, cylindrical, or spherical. HyperMesh supports reference and analysis systems. Reference systems transform geometric location or input vectors from the global system to a local system. Nodes, mass elements, forces, and other systems are eligible entities for a reference system. Analysis systems transform the output system of a node entity. Systems are built and referenced in the systems panel. Note: System collectors collect system entities. A system collector must exist and be current in order to build a system.
Altair Engineering
Automatic Mesh Generation

HyperMesh has a centralized plate and shell mesh generation tool called the automeshing secondary panel. Most of the element creation panels use this module, which supplies as much automated assistance as possible. You can adjust interactively a wide variety of parameters and choose from a suite of algorithms. HyperMesh responds with immediate feedback on the effects of the changes, until you are satisfied with the resulting mesh. There are two approaches to the automeshing secondary panel, depending on whether or not you use surfaces as the basis for the operation. If you use surfaces, you may choose from a greater variety of algorithms, have more flexibility in specifying the algorithm parameters, and employ the mesh-smoothing operation to improve element quality. If you do not use surfaces, the meshing process is usually faster and uses less memory. Most of the functions are still available and operate in the same way. Furthermore, there are situations in which it is not possible or not desirable to create a surface.
For either method, the module operates the same. You control interactively the number of elements on each edge or side and can determine immediately the nodes that are used to create the mesh. You can adjust the node biasing on each edge to force more elements to be created near one end than near the other, which allows you to see immediately the locations of the new nodes. You can also specify whether the new elements should be quads, trias, or mixed and whether they should be first or second order elements. The created mesh can be previewed, which allows you to evaluate it for element quality before choosing to store it in the HyperMesh database. While you are in the meshing module, you can use any of viewing tools on the visual options menu to simplify the visualization of complex structures in your model. If you use surfaces, you can specify the mesh generation and visualization options to use on each individual surface. You may choose from several mesh generation algorithms. Mesh smoothing is also available and you may select the algorithm for that operation as well.
A solid model created by dragging automeshed plate elements.

Altair Engineering
The automeshing secondary panel can make second order elements for boundary element solutions.
Altair Engineering
Using the Automeshing Secondary Panel

The functions of the automeshing secondary panel are divided into six sub-panels. You can switch freely between the sub-panels; the screen display changes to present only the information applicable to the current operation. density algorithm type biasing details checks Each automeshing sub-panel has the mesh, reject, smooth, undo, abort, and return functions (see Automeshing Secondary Panel in the Panels section), as well as the local view pop-up menu.

Altair Engineering
Mesh Generation Algorithms

The mesh generation algorithms are divided into two types: those that require the presence of a surface to provide a context of operation, or those working entirely from node and/or line data. The mesh generation algorithms include: Autodecide If you are meshing a surface, the default mesh generation algorithm is Autodecide. In this case, HyperMesh analyzes the geometry of each face and the element densities specified for each edge, and chooses the algorithm that will give the best results. For most configurations, it chooses the Free algorithm. The Free meshing algorithm is a general-purpose formula that works for most meshing conditions. The surface can have interior holes or edges and any number of sides. If quads or trias is the selected element type, an advancing front algorithm is used. If mixed is the element type, a submapping algorithm is used. The advancing front algorithm uses the following process: Traverses the perimeter of the region, placing elements along the edges as it proceeds. Each site where an element could be placed is measured and one of several possible elements is chosen. Eventually the entire region is filled with elements. Examines the groups of elements to see if a local change in the connectivity might improve element quality. Applies repeatedly the selected smoothing algorithm until no node is moved farther than the specified smoothing tolerance.
Free
If quads is the selected element type for the current face, HyperMesh attempts to produce an all-quads mesh, but there are some situations in which one or more trias are included: If the total number of elements specified for the perimeter of the face is odd, at least one tria always needed. If there is a tight corner on the boundary that would require a poor quality quad, HyperMesh uses a single tria. Sometimes two or more trias are needed because of the particular order in which the elements were generated; if that is the case, you can usually eliminate them by changing some of the meshing parameters and then remeshing the region.
If trias is the selected element type, HyperMesh uses a streamlined version of this algorithm that is optimized for the different shape and connectivity requirements of tria elements. Map as Triangle, Rectangle, or Pentagon If the region is free from internal holes and the boundary is clearly triangular, rectangular, or pentagonal in shape, the best choice of algorithm is usually to map a standard mesh onto the region using transfinite interpolation. Such an operation is exceedingly fast, and where applicable, gives quality results rapidly. HyperMesh chooses a standard template based on the element densities around the perimeter of the region. Ignoring rotations, HyperMesh recognizes more than 18 different configurations requiring distinct templates. To make tria elements, HyperMesh first creates a quads mesh and then divides each element along its shortest diagonal.
Altair Engineering
Map without Surface
If you are creating a mesh entirely from line and/or node data, with no surface, the mesh generation algorithm is decided by the tool that was used to describe the desired operation. If you use the drag panel, the algorithm is to drag. If you use the spin panel, the algorithm is to spin, and if you use the spheres panel, the algorithm is to map a sphere-covering mesh. You can still use the density and biasing manipulation tools but some edges will be linked together, so that the configuration always satisfies the balancing requirements of the intended mapping.

Altair Engineering
Smoothing Algorithms
There are three smoothing algorithms used by HyperMesh: Autodecide By default, HyperMesh traverses the perimeter of the region looking for variations in element edge length and choose between size-correcting and shape-correcting smoothing algorithms. The size-corrected smoothing algorithm attempts to even out the sizes of the elements at the cost of some element quality, usually in the form of worsened aspect ratios from the stretching of elements. HyperMesh uses a modified Laplacian over-relaxation that can correctly handle mixtures of quads and trias. If the element spacing around the perimeter is roughly uniform, this choice usually gives the best results. The shape-correcting smoothing algorithm attempts to correct the elements shapes, allowing variation in element size. HyperMesh uses a modified isoparametric-centroidal over-relaxation that can correctly handle mixtures of quads and trias. If there is a transition from small elements to large elements in the region, this choice usually gives the best results.
Size Corrected
Shape Corrected
Altair Engineering
Element Biasing
The automeshing process allows you to bias the placement of nodes so that their intervals are not uniform in size. You can designate that the smaller intervals go near the start of the edge, near the end of the edge, near both ends with larger intervals in the middle, or near the middle of the edge. Within the automesher, you may want to use biasing to improve element quality when transitioning from smaller to larger element sizes. When you use the drag and solid offset panels, you can use biasing to cluster several layers of elements near the surface of a solid. In linear solids, the mesh at one end could be scaled several times larger than at the other end. Element biasing allows you to moderate the changes in aspect ratio from the start to the end. There are three methods you can use to calculate the biasing of node positions:
Use biasing to preserve element quality in complex regions.
Linear Biasing
In linear biasing, the biasing intensity corresponds to the positive slope of a straight line over the interval [0,1] of the Real Line. This interval is uniformly divided into as many subintervals as specified by the element density and they are mapped along the edge so that the length of the image interval is proportional to the height of the line over the midpoint of the source interval. Each image interval corresponds to the side of an element.
Specifically, let n be the element density and let
We want a node placement function x(s) taking values in [0,1] with x(0) = 0 and x(1) = 1. If m is the slope of the line, and b is its y-intercept, then:

Altair Engineering
Using x(0) = 0, and x(1) = 1, we find:
so,
. For this, m is the absolute value of the biasing intensity. If the biasing intensity is negative, the nodes are placed according to 1 - x(s). Thus, a positiv biasing intensity puts small elements at the start of e the interval. We can use b to scale the behavior of the function so that convenient values are in the range [0,20]. The value used is b = 1.5.
Exponential Biasing
In exponential biasing, the sizes of the intervals grow geometrically, progressing along the edge, with each successive interval being a constant factor larger than the previous. That factor is 1.0 plus 1/10 of the absolute value of the biasing intensity. This formula was chosen so that an intensity of zero will still represent no biasing, and convenient values will fall in the range [0,20]. Negative biasing intensities just reverse the edge, placing the smaller elements at the end instead of the beginning.
Specifically, let n be the element density and let
We want a node placement function x(s) taking values in [0,1] with x(0) = 0 and x(1) =1. Let be the geometric growth factor.
We need a function Let then:
so that:
which gives the proper interval lengths,
then x(s) scales them to the range of [0,1]. Thus,
Altair Engineering
Bellcurve Biasing
In bellcurve biasing, nodes are distributed long the edge in a pattern that is symmetric across the midpoint of the edge. If the biasing intensity is positive, the smaller intervals are placed at the beginning and end of the edge, and if it is negative, they are placed at the middle of the edge.
Specifically, let n be the element density and
We need
so that
takes values in [0,1] with x(0) = 0, x(1) = 1, and has the behavior noted above. If we use: for positive biasing intensity r, then x(s) becomes:
where erf() is the statistical error function,

Altair Engineering
Linked or Locked Edges

Most of the surface-less mesh generation algorithms requires that some edges have exactly the same element density and biasing values as other edges. HyperMesh automatically links those edges together so that they stay balanced. Any change to one of the edges is immediately applied to all others that are linked to it. Some of the surface creation panels allow you to use a node list to define one or more sides of a surface. In these circumstances, HyperMesh uses those nodes directly to make elements within the automeshing secondary panel. The resulting edge is locked and you cannot change the element density or biasing. If you try to adjust the element density numbers corresponding to these locked edges, it has no effect. The error message, "The value of this number cannot be changed" is displayed.
Use the automeshing secondary panel to prepare input for solid offset.
Altair Engineering
Connector Entity
Connectors are geometric entities (not FE) primarily used to create welds. Just as you can create an FE shell mesh by meshing a surface, you can create an FE weld by realizing a connector. The characteristics of connector entities can be divided into four categories: Connector Terminology Connector Definition Connector Realization Connector Review

Altair Engineering
Connector Terminology
Connector State
The connector state is defined as one of the following types: unrealized The initial definition of the connector entity after it is created. The connector is displayed in yellow. The connector is considered realized only if weld creation at the connector was successful. The connector is displayed in green. The connector is considered failed if the weld creation at the connector was not successful. The connector is displayed in red. The color code provides an easier way to visualize and filter connectors based on their state. A connector that was realized can revert back to being unrealized if, for example, a link entity is suppressed from its definition, or the weld element is deleted.
realized
failed
Note:
Connector Location
The position in space at which a connector entity is created. nodes points lines The connector is created at the node location. The connector is created at the point location. The connector icon is created at the center of the selected line. Only one connector is created for each line, but the line may be split into multiple projection locations as specified by the offset, spacing, and density values. Only nodes, points, and lines can be used to define connector location. The connector location option is set in the create panel.
Note:
Altair Engineering
Link Entity
A reference to a separate HyperMesh entity that can be added to a connector. The HyperMesh entities to which the link entities refer are welded together during realization. The following entities are supported. components Components can be used to connect elements or surfaces. A part that needs to be welded is often represented as a component. An element facilitates a patch-patch weld connector. Surfaces can be used to create welds to connect geometry before meshing. The welds create fixed points for the mesh. The surfaces can be either meshed or unmeshed. A node facilitates a node-node weld connector. The tag entity can be used to define a weld connector to either a node, or an element that it holds. Only nodes, tags, elements, surfaces, and components can be added to connectors. The connectors can hold a single entity or a combination of these entities. The link entity options are set in the create and add links panels.
elements surfaces
nodes tags
Note:
Link Entity State

Specifies if the HyperMesh entity referenced by the link entity is meshed or unmeshed. geom Specifies that the entity needs to be connected (welded) using its geometry (connect surfaces only). Specifies that the entity needs to be connected (welded) using its mesh. The above states are applicable to only surfaces and components added to the connector entity. The elems option connects the mesh on the component or surface and the geom option connects the geometry on the component or surface. The link entity state options are set in the create and add Links panels.
elems Note:

Altair Engineering
Re-connect Rules
Defines how a connector should protect its link entity information. none If a link entity references a HyperMesh entity that is removed from the HyperMesh database, the link entity is then removed from the connector. If a link entity references a HyperMesh entity that is removed from the HyperMesh database, the link entity retains the ID of the HyperMesh entity. The link entity remains in the connector. Same as the by id rule except that the entity name is retained.
by id
by name Note:
These rules are useful for applications such as part replacement. A part can be added to a connector ith the use id or use name reconnect rule and can be replaced with a redesigned part with the same ID or name, without having to change the connector definition. The re-connect rule options are set in the create and add links panels.
Number of Layers
The total number of thicknesses (layers) to connect at the connector. total T Sets the number of thickness to connect (2T/3T/4T/nT). This influences the number of welds created at a connector. Sets the total number of link entities that can be added to the connector. The number of link entities added to a connector is always less than or equal to the total thickness. The number of layers option is set in the create and add links panels.
Note:
Altair Engineering
Connector Rules
Shapes the definition of a connector entity. none The connector is created with no link entities and no thickness defined. In this state, the connector must first be updated with more information before it can be successfully realized. This option requires link entities to be specified before the connector is created. The link entities are added to the connector based on the user-supplied criteria. For this option, the connector only remembers what type of link entity it is to connect, rather than a specific link entity. During the fe realize process, the connector searches the HyperMesh database to generate the best (usually the closest) link entity it can using the supplied information.
now
at fe realize
Note:
The connector rules (connect when:) option is set in the Create and Add Links panels.
Connector Realization
Creating welds at a connector. fe realize The process of creating welds (FE) to connect the HyperMesh entities referenced by the link entities added to a connector.
Note:
The connector entity can be used to create only welds at this time.
Request for Connection

A set of parameters used during realization to create a physical connection between link entities.

Altair Engineering
Connector Definition
The connector is simply a database of information defining a specific request for connection at a specific location. A connector definition describes the connector between multiple HyperMesh entities at a specific location. Entities that are to be connected are referred to as link entities. The connector location is defined as a node, a geometric point, or a geometric line. In the following example, there are two components (Top and Bottom) that are to be connected at the location of a point (with an id of 10). In this case, both components are considered to be link entities, since they are to be linked together. The point defines the location of the connector.
After a connector is created, the connector icon is placed at point 10, and components 1 and 2 are incorporated into the request for connection. The following diagram shows the connector after it is created (with an id of 7) at the location of point 10 (point 10 is not visible).
In this example, connector 7 has been defined and no welds have been created. The connector stores the following information: Which link entities the request for connection is to connect (Comp 1 and Comp 2) The thickness of the realization (Thickness = 2) Where to connect the link entities (the connectors current location)
Altair Engineering
HyperMesh entities currently supported as link entities include COMPS, ELEMS, SURFS, NODES, and TAGS. Any number of link entities of differing types can be added to a connector in any order. The connector sets the order of link entities during the realization process. The example above is a simple case where we have added two link entities of the same type (COMPS) to a single connector. Note: An element-to-tag-t o-component connector is possible, as is any other combination of the supported link entities.

Altair Engineering
Connector Realization
During connector realization, welds are created using the connector definition. Note: In HyperMesh, the only form of realization currently supported is fe realization (weld creation). For successful realization, the connector must be populated with all the relevant details required for its realization type. For example, fe realization requires the connector to be populated with a projection tolerance and an FE configuration type.
The following diagram shows connector 7 realized with a valid tolerance value, and a config value of type 21 (spring).
One advantage of separating weld fe realization from the connector definition, is that a connector can be re-realized as a weld of a different configuration (or possibly, a user-defined weld) without having to redefine the connector. If you edit the connector definition (i.e. add or delete a link entity from the connector), the connector removes the welds it created, and reverts back to an unrealized state. The connector is unrealized only if its user-control mode is turned off. By default, the connector mode is off but it can be turned on by registering custom FE with a connector. Connectors store all FE information that they create, allowing advanced find, mask, delete, and organizational functionality in a number of common HyperMesh panels. If the weld creation is unsuccessful (due to low tolerance, insufficient link entities, etc.) the connector icon is displayed as failed (red). An unrealized connector is yellow, a realized connector is green, and a failed connector is red.
Altair Engineering
Connector Review
There are many advantages to the way connectors store information. Not only does this local storage allow you to edit the connector definition, it also allows you to review connector details and the quality of the realization. There are a number of tools that can be useful in the review process. The visualization pop-up allows you to update the visual appearance of a connector based on its state, thickness (number of layers), or the component in which it is located. In addition, the vis opts panel also allows you to filter the displayed connectors by various criteria (such as thickness). This filter can then be used for displayed mark creation. HyperMesh includes a connector information table that creates a table of connector definitions from a mark and allows you to delete link entities. The quality panel allows you to check the quality of welds created from the connectors. The connector database can also be queried through Tcl functions.
Connectors User Control Mode

Each individual connector can be placed in a user control mode using either the *CE_SetSpecificDetailById or *CE_SetSpecificDetail commands. This user control mode is most useful for automated Tcl scripts. Once in user control mode, the following procedures are possible for a given connector: Pre-existing FE can be registered as a given connectors realization by using the *CE_FE_Register command. Connectors can be edited without automatically unrealizing (as happens most notably when a link is added or removed from a connector, or when an FE realization entity is deleted). A connectors state can be manually changed from realized to failed, or from failed to realized by using either the *CE_SetSpecificDetailById or *CE_SetSpecificDetail commands. A connectors state will not change to or from the unrealized state using this method.
Once a connector is placed into the user control mode, the user control mode remains active until an unrealize command is called (such as *CE_Unrealize), an already realized connector is rerealized, or the user control mode is manually turned off with either the *CE_SetSpecificDetailById or *CE_SetSpecificDetail commands. While a given connector is in user control mode, it may not behave the same as a normal connector. Specifically, there are a number of scenarios where a user-controlled connector will not auto unrealize in response to database changes that would cause a normal connector to auto unrealize. Note: It is strongly recommended that when FE is registered to a user-controlled connector, that the connector links and other necessary details should also be set with a given connector (so that the connector can properly re-realize if a user interactively requests it to). At the bare minimum, connectors should know which links they are to connect.

Altair Engineering
Master Connectors File

Most of the information stored in the connector entity can be exported to a master connectors file. This file contains connector entity information such as location, link entity, link entity state, link entity rules (see Connector Terminology). The exported file may also contain metadata information stored in the connector. The master connectors file contains welding information at a given location and also assists in the weld automation process. An exported master connectors file can be re-imported using the connectors reader to re-create connectors. The master connectors file is exported in a single format. The outline of a generic HyperMesh master connectors file is provided below: Master connectors files can have comments beginning with the characters # or $, or there can be blank lines in between. The format of the file is fixed and the order of heading definitions cannot be changed. The column information is shown below:
Notes: The header at the beginning of the file specifies information about the column data. Number of layers defines the thickness to connect at the specified location (X, Y, Z). The data between the brackets are repeated for each link entity. For standard HyperMesh FE types such as ACM and CWELD, the FE Config will have a number of 1001, which defines the user-defined type number specified in FE Config File. The FE Type will be the number defined in the FE Config File (for CWELD it is 72). For a detailed explanation of custom FE Configurations see FE Configuration File. The data between the brackets (link entity information) in the table are repeated for the number of links (NumLinks). The NumLinks variable must be equal to the number of link entities.
Altair Engineering
Metadata is an attribute type that can be stored on a HyperMesh entity. User-defined information (such as Station Id or Gun Id) can be stored on the connector entity as metadata. The Metadata is defined by a name-value pair and is supported for multiple data types (int, double, string, etc.). Please see the HyperMesh on-line help for more information on Metadata. The Metadata name is written to the master connectors file in the following format ~<Sturct><DataType>Name. <Struct> represents whether the value associated is a single variable or an array. <DataType> represents the type of data stored in the value. For example, a Metadata of name Assembly containing an array of integers is written out as ~AIAssembly. The only delimiter supported in the entire file is the double semicolon ::. The entire column of data in the file should be of the same type. The connectors reader uses the templex template to read the master connectors file. See weld templates for more information. By default, the file is read into HyperMesh through the HMIN function call, HMIN_CE_CreateDefined.
The connector entity is created with the information specified in the master connectors file and displayed as unrealized (yellow). To realize the connectors as welds, the fe realize panel must be used.
Multiple Weld File Format

In addition to the master connectors file, the connectors reader also supports master weld file formats previously supported by the spotweld reader.

Altair Engineering
Import Templates
Templates work with the connectors reader to import multiple file formats. The templates are stored in the <install_directory>/hm/bin/feinput/spotweld_format and are registered in the spotweld.cfg file under the same directory. The spotweld.cfg file must contain only the names of all the registered weld templates. Each template works on only one specific format file. For custom templates, a spotweld_format directory must exist in the same location as the master weld file. To read in metadata, the required headings must be added to the template requests and record blocks. The following example shows the template for a simple format file with two semi colons as delimiters. An example for a specific master weld file format is shown below: # Index::T::X::Y::Z::EID1:: EID2:: EID3:: 1:: 3:: 48.4375:: 9.375 Weld Template :: 2.0 :: 3:: 2:: 1::
int num header { type "CONNECTORS" set mark find "[0-9]+::" rewind
set num = 0 if { do 1000000 { if { isdigit } then { set num = sum(num, 1) } readln null } } set numrecords = num set numrequests = 9
Altair Engineering
requests "ID/T/X/Y/Z/EID1/EID2/EID3/EID4" set numcomponents = 1 components "Value" } record { read request // ID qfind "::" set mark read request rewind read num qfind "::" read request // X qfind "::" read request // Y qfind "::" read request // Z do num { qfind "::" read request // EID } set num = diff(4, num) do num { read constant 0 // fake EID } readln null } //T

Altair Engineering
FE Configuration File
The FE configuration file (feconfig.cfg) is used to define custom welds such as ACM (Area Contact Method) and other special types. The weld definition is solver dependant (NASTRAN, LSDYNA, etc.). The weld definition in the file includes the type of weld to create and the surrounding connector to shells. The specific solver template for the type of weld must be loaded in HyperMesh before the welds can be created using a connector entity. By default, the feconfig.cfg file from the <install_directory>/hm/bin directory is loaded in each of the panels related to each connector type (e.g. Spot, Seam, Area, etc). The FE configuration file has a pre-defined format that must be used to define different weld configurations. The data can be separated using a space. See FE Definition Examples for information regarding the format and options for FE definition.
FE Definition Template
The FE definition template is shown below:
CFG <SOLVER> <USER_FE_TYPE> <USER_FE_NAME> *filter <filter_type1> <filter_type2> <etc.> *style <style_type> *head <HM_FE_CONFIG> <HM_FE_TYPE> <RIGID_FLAG> *body <BODY_FLAG> <HM_FE_CONFIG> <HM_FE_TYPE> <LENGTH_LOCATION_FLAG> [<HM_FE_CONFIG> <HM_FE_TYPE> <LENGTH_LOCATION_FLAG>] *post <POST_SCRIPT_NAME>
The template parameters are defined below. SOLVER The solver template for which FE needs to be created. Supported solvers are: abaqus, ansys, dyna, marc, nastran, optistruct, pamcrash, and pamcrash2g. The user-defined number for the FE combination. This is input in the fe realize template as FE Type. The user-specified name for the FE combination. The specified name is saved and displayed in the info table during connector review process.
USER_FE_TYPE USER_FE_NAME
Note:
This should be the first line in the user FE definition.
Altair Engineering
*FILTER
This option can be used to allow only the specified connector types to realize the configuration. For example, *FILTER spot seam indicates that this configuration can be realized only by the spot and seam connector types. In addition, this option is used as a filter when displaying FE configurations in the type = field of respective realize panels.
Note: *STYLE
A * is required in the beginning of the line to specify that this is a definition and not a comment. This option indicates that the configurations have specific behaviors associated during realization, and that they are native types. Note: The style definition line for these configurations must not be edited.
For example, *style bolts 1 indicates that this is a bolt connection of type 1 that creates a specific bolted connection between the parts. Note: *HEAD Note: A * is required in the beginning of the line to specify that this is a definition and not a comment. The string head is required to specify that a rigid is to be created to connect the weld node to the surrounding shell element. A * is required in the beginning of the line to specify that this is a definition and not a comment. HM_FE_CONFIG The config for the rigid currently supported by HyperMesh. The various types supported for rigids are equation, plot, rbe3, rigidlink, etc. The solver defined type for the HyperMesh config. If the type is not defined, a zero should be input. For example, equation and rbe3 do not have a type defined, so the type field should be zero. Defines how the weld node is to be connected to the surrounding shell element. If rigid flag = 0, the weld node is connected to only one of the shell element vertex using the rigid. If the rigid flag = 1, the weld node is connected to all the vertices of the shell elements using rigid to form a spider. This option is not applicable to equation and rbe3.
HM_FE_CONFIG
HM_FE_TYPE
HM_FE_TYPE
RIGID_FLAG
CONNECT_FLAG

Altair Engineering
*BODY BODY_FLAG
The string body is required to specify that a weld is to be created to connect the link entities added to the connector. The body flag is used to calculate the length of the weld. If the body flag = 0, the length is calculated based on the distance between the connecting layers (link entities). If the body flag = 1, the length is calculated based on the average thickness of the connecting layers (link entities).
Note:
A * is required in the beginning of the line to specify that this is a definition and not a comment. The config for the weld currently supported by HyperMesh. The various types supported for welds are, spring, plot, hexa8, rod, etc. The solver defined type for the HyperMesh config. For example, CBUSH is of config spring and type 6. The type number is defined in respective solver templates and differs, based on the solver. The length location flag is used to specify if the weld created should be of type series or parallel. The series weld definition has more than one weld between the link entities. If the length location flag is >= 0 and < 1, a series weld is created. There can be more than one weld in a series. The flag specifies the length factor to be used for series welds. If the length location flag = 1, welds are created in parallel.
HM_FE_CONFIG
HM_FE_TYPE
LENGTH_LOCATION_FLAG
Note: *POST
A * is required in the beginning of the line to specify that this is a definition and not a comment. The *post lines are optional, but if specified it must be followed by the name (excluding path) of a valid Tcl script with a .tcl extension. This Tcl script must be located in the current working directory, the users home directory (UNIX only), or the scripts/connectors/ directory. This postscript will be automatically executed post FE realization and it can be used to edit weld properties, attributes, and other solver specific details. Starting with HyperMesh 8.0, this option can also be used to specify a property script for the configuration. This allows HyperMesh to parse the CFG file for configuration instead of relying on metadata saved individually with each connector (as was done prior to 8.0). Note, however, that metadata is still created and saved if you do not use POST to assign a property script (for example, if you choose to type in a property script instead of specifying a CFG file in the connectors generation panel.
Altair Engineering
FE Specification Rules
Each solver will have a specific definition so the same user-defined types can be repeated for each solver. The head and the body definition must begin with a * to define rigid and weld definitions. Multiple solid element combinations are not currently supported. Therefore, an ACM can have only one hexa weld element specified in the definition. 1D and 3D element combinations are not supported. The total length of series welds cannot exceed 1.0 (100%). Hence there cannot be three welds specified in series having a length factor of 0.5 (50%) each. Series and parallel weld element combinations are not supported. Series welds are not supported where the link entities are coincident. Series welds are not created when the distance between the connecting link entities is zero. User comments should start with a hash character #.

Altair Engineering
FE Definition Examples
Washers CFG nastran 56 bolts *filter bolt *style bolt 0 *head rigidlink 1 1 dofs=123 rigidlink 1 3 *body 0 rigid 1 1 dofs=456 ACM Welds CFG nastran 71 acm *head rbe3 0 0 *body 1 hex8 1 1
The above definition creates ACMs with HEXA8 solid elements as welds and RBE3 elements as rigids. The length of the hexa is equal to the distance between the connecting shell elements. Series Welds CFG nastran 101 series *head plot 0 0 *body 0 spring 6 0.5 spring 6 0.5
The two series welds are created with a length equal to half the distance between the link entities. Series Welds CFG nastran 101 series *head plot 0 0 *body 0 spring 6 0.5
The series weld is created at the center with length equal to half the distance between the link entities.
Altair Engineering
Parallel Welds CFG dyna 101 parallel *head plot 0 0 *body 0 bar2 1 1 bar2 1 1
The bar elements are created at the same location and connect the same link entities. 0-D Welds CFG pamcrash2g 1 plink (ce loc) *head plot 0 0 *body 0 mass 5 2 plot 0 1 *post prop_plink.tcl Supported values for the length location flag are "0", "1", or "2". The behavior for each value is as follows, "0" places the 0-D element along the proposed 1-D element path. If this 0-D element is the only config given in the *body, then it is placed at the center of the proposed 1-D element path. "1" has the same behavior as "0" except only a single 0-D element is created even if multiple bodies are created (as happens in >2T welds) and "2" places the 0-D element at the connector location.

Altair Engineering
HyperMorph Strategies
HyperMorph is a tool in HyperMesh to morph the shape of a finite element model in ways that are useful, logical and intuitive. It enables rapid shape changes on the finite element mesh without severely sacrificing the mesh quality. During the morphing process, HyperMorph also allows the creation of shape variables, which can be used for subsequent design optimization studies. Overview: The Three Basic Approaches to Morphing The Domains and Handles Concept The Morph Volume Concept The Freehand Concept Global Domain and Global Handles Local Domains and Handles Partitioning Dependent Handles Working with Shapes Setting Up Optimization Creating morph volumes Registering nodes Altering Morph Volumes Tangency Morphing by Moving Nodes Morphing by Using Other Panels Sculpting
The Domains and Handles Concept
The Morph Volume Concept
The Freehand Concept
Space Frame Model Strategies Creating Handles and Domains Matching a Mesh or Line or Surface Data Making Parametric Changes Controlling Global Morphing with Handle Placement Mirror Images: Using 1-Plane Symmetry Reducing 3D to 2D: Using Linear Symmetry Reducing 3D to 1D: Using Planar Symmetry
Altair Engineering
Shell Model Strategies Creating Handles and Domains Morphing on Local Domains Section Mapping Morphing Global Handles Using Constraints Using Biasing
Solid Model Strategies Creating Handles and Domains Viewing Solid Models Morphing on Local Domains Morphing Global Handles Using Constraints Using Biasing

Altair Engineering
The Three Basic Approaches to Morphing

HyperMorph contains six exclusive entity types and a wide array of functionality. 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 HyperMorph Strategy Guide is intended illustrate the capabilities of HyperMorph and introduce you to both the basic and advanced functionality to help you get the most out of the tool. The basics of the three concepts are summarized below:

This approach involves dividing the mesh into domains made up of elements or nodes and placing handles at the corners of those domains. HyperMorph can do this automatically, dividing the mesh into logical domains, or you can define your own domains and handles. When the handles are moved, the shape of the mesh changes according to the domain boundaries. The domains and handles approach also allows parametric morphing of distances, angles, radii, and arc angles as well as morphing the mesh to match geometric data and other meshes. The domains and handles approach is the most difficult approach to learn but it is also the most powerful. This approach is most useful for making detailed changes to any mesh (local domains) as well as general changes to space frame type meshes (global domains).

This approach involves surrounding the mesh with one or more morph volumes, which are highly deformable six-sided prisms. A number of methods exist to create the morph volumes including single and matrix creation as well as the interactive, on-screen method. Morph volumes support tangency between adjoining edges and allow for multiple control points along the 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 morph the mesh inside the morph volumes. The morph volume approach is quick and intuitive and is most useful for making large scale changes to complex meshes.

This approach involves morphing by moving the nodes directly without needing to create any HyperMorph entities. You define the nodes which will move, the nodes which will stay fixed, and the affected elements manually, allowing for rapid changes to any mesh. You have great flexibility in how the moving nodes are moved, such as translation, rotation, and projection to geometry as well as using a "tool" to "sculpt" the mesh into the desired shape. You are also able to turn node manipulations made in any panel, such as scaling or node projection, into morphs using the record sub-panel. The freehand approach is an ideal introduction to HyperMorph since it allows morphing without the creation of new entities while implying the concepts of domains and handles. The freehand approach also allows for "customized" morphing, allowing the user to do virtually any kind of morphing.
Altair Engineering

When using the domains and handles approach, the model is divided into domains where handles are used to control its shapes. When the handles are moved, the shape of the domains touching those handles change, which in turn, changes the positions of the nodes inside those domains. During the morphing process the mesh morphs in a logical way with nodes near the moving handles moving more and nodes near the stationary handles moving less. In the areas between the handles, the mesh is stretched or compressed to match the desired shape. Domains consist of nodes, in the case of global domains, or elements, in the case of 1D, 2D, 3D, edge, and general domains. The nodes in each domain move as a function of the handles that are either associated with the domain or are touching the domain. The amount each node moves with respect to each handle is relative to an internally calculated influence coefficient. The process for calculating the influence coefficients is somewhat time consuming, but once they are calculated they can be stored and applied rapidly. Thus, when handles and domains are initially set up or edited, HyperMorph spends an amount of time proportional to the size of the new or edited domains calculating the handle influences, but when handles are moved in order to morph the model no calculations are necessary. Therefore, the actual morphing occurs quickly. The advantage of this approach is that it makes morphing an interactive process, even for large models. For very large domains, calculating influence coefficients is too time-consuming. For domains that have more than 50,000 elements (although you can change this default limit) the large domain solver is used. The advantage of the large domain solver is that it is faster for morphing large domains but the drawback is that it must be invoked every time you wish to morph, thus making morphing slower. However, for very large domains, the process of calculating influences can be too slow or too memory intensive and so the large domain solver makes it possible to morph such domains. Domains and handles are divided into two basic groups, global and local. The global group consists of global domains, each of which is associated with a number of global handles. Global handles will only influence the nodes in the global domain to which they are associated. Global handles and domains are best for making large scale shape changes to the model. The local group consists of five types of local domains: 1D domains, 2D domains, 3D domains, edge domains, and general domains. Each domain is associated with any number of local handles. These local handles can only influence nodes contained in any domains that they are either associated with or are touching. Local handles are intended to be used to make small scale, parametric changes to the model. A model can contain both global and local handles and domains, which allows you to make both large and small scale morphs and have them combine logically, but it is not necessary to have both types of domains and handles in a model.
Global Domains and Global Handles

Global domains are represented by a cube made up of dashed lines. It is located at the centroid of the nodes selected when you create the global domain. Global handles are the largest handles in the model and they are red if they are not dependent on other handles, or yellow, cyan, or violet if they are dependent on other handles, the color indicating their level of dependency. Dependent global handles are also smaller than the handles on which they are dependent. You can adjust the base size of all the handles in the model in the parameters sub-panel of the domains or morph options panels or in the handles panel. The size given is used as the radius for the independent global handles as well as the diameter of the independent local handles. You cannot edit the color of the handles nor the relative size between the dependent and independent handles. However, you can edit the color of the domains in the parameters sub-panel of the domains or morph options panels.

Altair Engineering
When a global domain and handles are generated automatically, such as when you create a global domain with the create handles option turned on, or use the generate auto-function, HyperMorph generates a number of global handles. HyperMorph creates a global handle at each of the eight corners of a box surrounding the model laid out along the global axes. These global handles are named corner followed by a number from one to eight. HyperMorph also places at least one global handle within the box in areas of peak nodal density within the model. HyperMorph generally creates no more than about 30 global handles for models of any size. These handles are named handle followed by a number. The automatic global handle generation works particularly well for space frame models such as full car models. If the handles are not generated in the positions where you want them to be, you can always delete them, reposition them, or create new handles.
Example of a model with a global domain and global handles Eight handles are placed at the corners of a box enclosing the model. By movi ng the handles you can stretch or deform the model along all three axes.
Altair Engineering
A space frame with six manually created global handles When the handles are moved, the space frame morphs in a way such that the bars run between the handles. There are three options for determining how global handles in global domains influence the mesh: the hierarchical method, the direct method, and the mixed method. In the hierarchical method, global handles influence the local handles found at nodes inside the global domain, which in turn influence nodes. In the direct method, global handles influence the nodes in the model directly. In the mixed method, global handles will influence every node inside the global domain using the hierarchical method if the node is inside a local domain, or the direct method if the node is not in a local domain The method used can be selected in the global sub-panel of the morph options panel and the parameters sub-panel in the domains panel with the default being the direct method. There are subtle differences in how the global handles influence the nodes for each method with the main difference being that the parts of the model defined by local edge domains have their shape preserved when using the hierarchical method. Straight edges will remain straight and circular holes will remain circular for the hierarchical method, while the direct method may bend or warp these features into curved edges and elliptical holes. You should select which method is right for the type of morphing that you want to perform. If you wish to preserve the local geometry, choose the hierarchical or mixed method. If you are willing to accept distortions in the local geometry, choose the direct method.

Altair Engineering
An example of global morphing using the hierarchical method When the highlighted (white) handle is moved to the right, it moves the local handles, which move the mesh. Note how the straight edge remains straight and the circle remains round.
An example of global morphing using the direct method When the highlighted (white) handle is moved to the right, the mesh is affected directly. Note the resulting distortion of the edge and circle.
Altair Engineering
An example of global morphing using the direct method and biasing factors By increasing the biasing factor for the highlighted (white) handle, the angular shape of the morph becomes rounded. The influences between the global handles and local handles (using the hierarchical method) or nodes (using the direct method) can be calculated using either the spatial method or the geometric method. Both methods attempt to determine how a global handle affects nodes or local handles in the space surrounding it. The spatial method is the default, and is the fastest and most robust method for generating global influences based on a spatial formulation for the entire model. The geometric method can be slow for large models or large numbers of global handles, but may produce more desirable influences. The geometric method is the method that was originally used for the Tcl/Tk interface of HyperMorph and HyperMesh and generates influences based on the geometric relationship between a given node or local handle and the surrounding global handles.
Local Domains and Handles

Local domains are represented by a single rectangle for 1D domains, two joined rectangles for 2D domains, a cube for 3D domains, four joined rectangles for general domains, and a line for edge domains. Independent local handles are orange and have a radius of one half the value of the handle size parameter. Dependent local handles are smaller than the independent local handles and are different colors depending on the level of their dependency. The colors of the handles cannot be changed. The color of the domains can be changed in the parameters sub-panel of the domains panel. Local domains can be created individually by selecting nodes or elements in the create sub-panel of the domains panel, or for the entire model by using the generate auto-function.. When local domains are created, HyperMorph automatically places local handles at the ends of all edge domains. These local handles are named local followed by a number. The placement of local handles depends on the type of domain created and the partitioning options if partitioning is selected.

Altair Engineering
Example of a model with local domains and local handles with partitioning. In the example above, the rigid elements have been placed in a 1D domain with the center node having an independent (orange) handle and the other nodes having dependent (green) handles. The shell elements have been placed in two 2D domains separated at the bend line due to partitioning. The solid elements have been placed in a 3D domain. Note that shell elements have been created on the faces of the 3D domain. These elements are placed in a component named ^morphface. Also note that 2D domains have been created on the faces of the 3D domain and that edge domains have been create on the edges of all the 2D domains. Finally, handles have been placed at the ends of all the edge domains. Domains made up of 1D elements, such as bars and rigid elements, are called 1D domains. When creating local domains or using the generate auto-function, 1D elements that share common nodes are grouped together into 1D domains. An independent local handle is placed at the centermost node of the 1D domain and dependent local handles are placed at every other node of the elements in the 1D domain. The independent handle is larger and orange, while the dependent handles are smaller and green. All the dependent handles in a given 1D domain are directly dependent on the independent handle. This dependency relationship means that moving the independent handle also results in moving the dependent handles the same amount in the same direction. This is done to preserve the unique relationship established for groups of 1D elements. Additionally, the bias factors for the dependent handles for a 1D domain are given an initial value of 3. All other handles in the model are given a biasing factor of 1. A higher biasing factor means that a given handle will have greater influence over the surrounding mesh than the others. The higher biasing factor given to dependent handles on 1D domains is intended to prevent mesh distortion when the 1D elements connect to nodes in 2D and 3D domains.
Altair Engineering
A rigid spider becomes a 1D domain An independent local handle (orange) is placed at the centroid of the 1D domain and dependent handles (green) are placed at each node. By moving the orange handle, the entire spider is moved, maintaining the proper shape and connectivity for the rigid spider. Domains made up of shell elements are called 2D domains. When creating local domains or using the generate auto-function, shell elements that share common nodes are grouped together into 2D domains. If partitioning has been selected, these domains are subdivided into smaller domains along break angles and curvature changes according to the partitioning parameters. Edge domains are placed along the edges of the 2D domains and are also partitioned. Local handles are placed at the ends of all the edge domains. In general, the local handles are placed at the corners of the 2D domains and at other useful positions. The intent is to make it faster and easier for you to apply parametric changes to the model. Since you morph the model by moving handles, it helps to have handles already at the positions where you want them. HyperMorph tries to predict where the handles should be placed to reduce the amount of time it takes to prepare your model for morphing. If the handles or domains are not laid out in the positions where you want them to be, you can delete them, edit them, or create new ones. Also, even though the generated local handles are associated with the edge domains, they will influence the nodes in any domain that shares the node at which it is placed. This is true even if the handle is associated with the 2D domain. A handle associated with any domain will always influence the nodes in domains that it is touching. Note that it is possible to create a handle on a node that is not touching the domain to which it is associated. This allows you to place a handle outside of a domain, such as floating in space near the domain, and have it influence the nodes within its domain.

Altair Engineering
Two 2D domains with edge domains and handles The model on the left shows the initial handle positions. The model on the right shows the addition of four new handles. Handles can be placed anywhere, even at nodes not on the associated domain. Domains made up of solid elements are called 3D domains. When creating local domains or using the generate auto-function, solid elements that share common nodes are grouped together into 3D domains. Elements are created on the faces of each 3D domain and placed into a component called ^morphface. It is recommended that you do not delete or edit these elements nor rename or delete the ^morphface component. However, if you do, these elements and their 2D domains will be regenerated the next time you enter or exit a HyperMorph panel or the delete panel. The elements on the face of each 3D domain are placed into a 2D domain that is then partitioned if the partitioning option is active. Edge elements are placed around each 2D domain and local handles are created at the ends of each edge domain. In cases where shell elements that are attached to the faces of solid elements are present in the model, HyperMorph will not create ^morphface elements coincident with the existing elements. The color of the ^morphface component can be changed in the parameters sub-panel of the domains panel. Note that these elements will not be written out to any FEM formatted deck since the component name begins with a ^.
A block of solid elements is made into a 3D domain The gray shell elements on the face of the 3D domain are the ^morphface component. The ^morphface component has been partitioned into 2D domains. Handles are created at the corners of the 2D domains.
Altair Engineering
Domains made up of a list of nodes are called edge domains. When creating local domains or using the generate aut o-function, edge domains are placed around the edges of all 2D domains. When you are selecting domains and are holding the mouse button down while placing the mouse over the icon of a 2D or 3D domain (or an element in the domain), HyperMesh will highlight both the domain icon and the surrounding edge domains. This makes it easier for you to tell which domain you are selecting. When you release the mouse button, only the icon for the domain remains highlighted. Edge domains and 2D domains on the faces of 3D domains play an important function in determining the influences for the handles over a given domain. Nodes on edge domains will only move as a function of the handles touching the edge domain. No other handles will affect the nodes on the edges. Similarly, nodes in a 2D domain on the face of a 3D domain will only move as a function of the handles touching the 2D domain. This preserves the boundaries of 2D and 3D domains such that straight edges remain straight, flat surfaces remain flat, and curved edges retain their curvature. It allows you to move handles within a 2D or 3D domain without affecting the edges. If you do not want to have the boundaries of a domain preserved you can delete the edges for a given domain, or choose to create the domain as a general domain instead. Also, non-reflective symmetries allow the influences of handles to extend through edges and faces depending on the type of symmetry. For domains that have non-reflective symmetry types, the boundaries may not be preserved during morphing.
Examples of edge domains Edge domains are placed around the edges of 2D domains. In the model at the right an edge domain has been created inside a 2D domain. Note that when an edge domain is created, it is partitioned and handles are placed at the ends and joints.

Altair Engineering
How edge domains affect morphing In the top two frames two handles inside a 2D domain are created and moved. In the bottom frames, two handles connected by an edge domain are created and moved. Note that the edge domain remains straight, preserving the shape of the feature. General domains can be made up of any combination of 1D, 2D, and 3D elements. General domains are not automatically created when generating local domains or using the generate auto-function. Like all other domains, the elements within a single general domain must touch one another. When a general domain is created, no 2D domains are created on the faces of any 3D elements and no edge domains are created either, thus no handles are created for the domain. However, general domains respect all neighboring edge domains and 2D domains and thus if you create 2D and edge domains for your general domains they will impose restrictions on handle influences for the general domain. Otherwise, handles on a general domain freely influence all of the nodes inside the general domain, allowing it to stretch and deform in an unbounded manner with morphing extending across differences in element type. General domains are very useful for realized connectors which are often represented as clusters of different element types. Another use is for meshes where precise changes are required for one section, where 1D, 2D, and 3D domains are used, but the rest of the mesh (where a general domain is used) can simply follow along.
Altair Engineering
Example of interaction between a general domain and 2D domains In the top frame, two 2D domains are created for parts of two shell meshes and a general domain is creating from the remaining rigid, shell, and solid elements. Two handles have been placed within the general domain at the ends of the rigid spiders. In the bottom frame the two handles inside the general domain are translated. Note how the shell elements in the general domain morph, bounded only by the edge of the 2D domains with the other edges free to follow the handles
Partitioning
Partitioning can be applied directly to 2D domains and indirectly to 3D domains (3D domains are created with 2D domains on their faces). Partitioning is a method of dividing 2D domains into smaller 2D domains at logical places, such as at the edges of surfaces associated with the mesh, or where the angle between elements exceeds a certain value, or where the domain changes from flat to curved. Partitioning allows you to prepare your model for morphing more quickly and easily since it divides your model into sections where parametric changes can be applied. You can invoke partitioning when creating 2D or 3D domains by activating the partition 2D domains check box. If there are no surfaces in the model, or the use geometry option in the partitioning sub-panel is unchecked, partitioning will ideally divide your model such that every radius and straight or flat section is placed into a separate domain. However, partitioning is not an exact science and there will be areas where elements are not placed into the desired domains. If you are unsatisfied with the partitioning, you may change the partitioning parameters in the partitioning sub-panel of the domains panel and try again (using the redo last button), or edit the domains by hand using the create and organize sub-panels in the domains panel.

Altair Engineering
Example of partitioning For the model on the left, the 2D domain was created without partitioning. For the model on the right, partitioning was used. Note how the 2D domains are divided along angle and curvature change boundaries. Also note that the edge domains are partitioned regardless of whether the partitioning option is on or off. There are two algorithms you can use to partition, element-based and node-based. These can be set individually for quad/mixed meshes and for tria/tetra meshes. Each algorithm has its strengths and weaknesses, so if one method is not producing the partitions that you desire, the other method might work better. In general, the element-based algorithm works better for quad/mixed meshes and second order meshes, while the node-based algorithm works better for tria/tetra meshes. There are also several parameters that govern the creation of domains for either algorithm. They are found in the partitioning sub-panel of the domains panel. If you have selected use geometry, all elements whose nodes are associated to surfaces in the model will be partitioned along the edges of the surfaces. All other elements will be partitioned using one of the partitioning algorithms. If you have also selected add to geometry, then any partitions created outside of the surfaces will be added to the partitions created using the surfaces if the partitioning algorithm does not find a break along the edges or the surfaces. This option is helpful when surface data is incomplete of some of the nodes have been moved away from their surfaces. Partitioning can be angle-based or curvature-based. In either case, the domain angle controls the break angle along which a partitioning break is made. If the angle between the normal vectors between two elements is greater than this value, a new domain is created with an edge running between the two elements. When using curvature-based partitioning, the curve tolerance controls the angle of which values less than it are considered straight for curvature measuring purposes. If the angle between the normal vectors between two elements is less than this value, they are considered flat, otherwise they are considered to be curved. If the curvature changes from straight to curved, changes direction, or changes curvature by more than the curvature tolerance, a new domain is created with an edge running between the two elements. Note that in order for a new partition to be created, a break due to angle or curvature must be found along its entire edge. For the node based method, domain angle and curve tolerance have a roughly similar meaning as the element based method. The node based method tends to create fewer partitions than the element based method, although exact performance for each method depends heavily on the features in your model. For instance, the node based method seems to work better on first order tria and tetra meshes while the element based method seems to work better on mixed quad and tria meshes.
Altair Engineering
Dependent Handles
You can make a handle dependent on one or more other handles, and then make those handles dependent on one or more other handles, and so on. This system allows you to create any number of dependency layers. Handles that are dependent on other handles appear smaller and in a color different from the handles on which they are dependent. The review button in the update sub-panel of the handles panel allows you to view the handles on which a specific handle is dependent. Making a handle dependent has no affect on the way it influences nodes.
Global handles, independent (red) and dependent (yellow, cyan, and violet)
Local handles, independent (orange) and dependent (green, blue, and pink) The conditions for handle dependency are as follows: A handle that is dependent on another handle inherits the movements applied to the higher level handle. If a handle is dependent on only one other handle, it inherits the full movement of the higher level handle. If a handle is dependent on more than one handle, it will inherit a percentage of the movements applied to each higher level handle. The percentage is based on the distance between the dependent and independent handles. A handle may be dependent on any number of handles, but dependency loops are not allowed. A dependent handle can be moved independently of the handles on which it is dependent. This means that movements applied to the dependent handle are not applied to the independent handles. This allows you to add the movements of dependent and independent handles in a logical manner. In the hierarchical method, all local handles are dependent on global handles. These dependencies are calculated internally and cannot be modified manually, biasing will affect them.
Handle dependencies are useful for several different applications. Transparent control of domain edges and faces You can create a dependent handle on an edge domain that is dependent on the handles at the ends of the domain. When the dependent handle is moved, the shape of the edge can be changed. When the handle at either end of the edge domain is moved, the dependent handle moves along as if it was not there. This allows you to combine the changes easily without having to apply separate perturbations for all of the handles.

Altair Engineering
Grouping features together to move as a unit You can make all the handles at one cross section of a beam dependent on a single handle. This allows you to move an entire cross section while only having to select one handle. Linking several domains together You can make all of the handles within several domains dependent on a few at the corners of the domain. This allows you to stretch all of the domains uniformly by moving the independent handles, in essence, performing localized global morphing.
Dependencies - example 1 The center global handle is dependent on the two outer global handles. When the highlighted handle on the left is moved (center frame), the center handle follows along. In the lower frame, the center handle is moved independently.
Altair Engineering
Dependencies - example 2 In the model on the left, the three green handles on the top are dependent on the orange handle on the top. The bottom has similar dependencies. The top and bottom halves of the cross sections are controlled by just two handles. In the model on the right, all of the green handles are dependent on the orange handle. The entire cross section is controlled by one handle. Note that the dependencies can extend beyond the 2D domain boundaries.
Dependencies - example 3 An independent handle was created between the two holes and the handles governing the positions of the holes are made dependent on it. When the independent handle is moved, both holes move with it. Also, each hole can be positioned separately by moving the dependent handle associated with it.

Altair Engineering
Using dependencies to reduce mesh distortion In this example two dependent handles were created on the edges of the part near the center hole. The dependent handles were constrained along vectors parallel to the sides of the part. When the handle at the hole is moved downward, the dependent handles follow and reduce mesh distortion by spreading the morph across the entire part instead of only around the hole.
Working with Shapes

Shapes are collections of handle and/or node perturbations. When you morph your model, HyperMorph stores the morph internally as a collection of perturbations which you can then undo or redo. When you create a shape using the save as shape or save shape sub-panels, the handle and/or node perturbations are stored in the new shape entity along with biasing factors for the handle perturbations and details such as the biasing style. If you create a shape in either the morph or freehand panels, or create a shape in the shapes panel with the save current state option turned on, HyperMorph takes the difference between the initial state of the model and the current state of the model when creating a new shape. If you save the model using the save each morph step option in the shapes panel, each morph on the undo/redo list will be saved as a separate shape. To get to the current state of the model from the initial state, all of these shapes must be applied. Creating shapes allows you to generate shape variables for optimization and store model changes for parametric studies. For many morphing operations, the morph consists only of handle perturbations. However, if constraints are being used, or the morph is a mapping or radius changing operation, node perturbations are required to fully describe the shape. In the case of freehand morphing, the morph consists only of node perturbations. When you create a shape, vectors are drawn for each handle and node perturbation for the shape. The vectors are drawn the exact length of the perturbation and the vectors for the handle perturbations are drawn with thicker lines to denote that they are different from node perturbations. Note that while shapes with handle perturbations will move nodes when they are applied, those shapes do not contain node perturbations and thus vectors are not drawn at those nodes.
Altair Engineering
When you are saving a shape, you can select whether to save it as handle perturbations or node perturbations. If you select handle perturbations, the shape will be saved as either handle perturbations only, or a combination of handle and node perturbations if node perturbations are required to describe the shape. If you select node perturbations, the shape will be saved as node perturbations only. The difference between the two types comes into play if you change the handles or domains in your model. Shapes saved as node perturbations are not affected by changes to domains and handles, while shapes saved as handle perturbations will differ from shapes that have been saved with changes to the handle influences. Whenever you make a change to your model, HyperMorph will ask you if you want to preserve any existing shapes saved as handle perturbations by converting them to node perturbations. If you plan to make changes to domains and handles, you should save shapes as node perturbations. If not, save shapes as handle perturbations and they will require less memory and disk space. If you later decide that you want to change a shape from node perturbations to handle perturbations or vice versa you can do so in the convert sub-panel of the shapes panel. Once a shape is saved, you can apply it to your model with any given scaling factor. Applying a shape in this way is like any other morphing operation and can be undone, redone, or saved as part of another shape. To convert shapes saved with handle perturbations to shapes saved with node perturbations, or vice-versa: 1. 2. 3. 4. 5. From the HyperMorph module on the Tools page, select the shapes panel. Select the convert sub-panel. Select the type of conversion that you wish to perform. Select the shapes to be converted. Click convert.
The shape is converted.
Setting Up Optimization
Morphing can be used to create shape variables for optimization. Note: A shape is not a shape variable, but by adding a desvar which points to the shape, it becomes a shape variable.
To create shape variables for an optimization run: 1. 2. 3. 4. 5. 6. 7. 8. 9. Morph your model into the shape of the first shape variable. From the HyperMorph module on the Tools page, select the morph panel. Select the save shape sub-panel. Save your morph as a shape. Click undo all to return to your base model shape. Repeat steps 1 through 4 for each shape variable you want to create. From the BCs page, optimization module, select the shape panel. Set the toggle to multiple desvars. Select the shapes for which you want to create shape variables.
10. Click create. A desvar for each shape is created with the initial value and bounds in the panel. Each desvar is given a unique name. 218 HyperMesh 8.0 Users Guide
Altair Engineering
11. Animate the shape variables: Click undo morphing if you did not click undo all after saving the last shape. Click animate. The deformed panel displays, allowing you to view each shape variable by animating it. Once you have created shape variables for your shapes, you can set up the rest of your optimization problem within the optimization module.

Morph Volume strategies are still being created; this help system will be updated in a service pack release to include Morph Volume concepts and strategies.

Freehand strategies are still being created; this help system will be updated in a service pack release to include Freehand concepts and strategies.
Altair Engineering
Space Frame Model Strategies using Global Domains

Space frames are models that have a sparse distribution of elements, such as a car body. Space frame models can generally have element counts in the hundreds of thousands, but their basic structure is rather simple. Often the desired shape changes are general, such as making it smaller, shorter, wider, or altering the basic positions of components within the frame. In many instances, these changes can be performed by placing a handle at each joint in the frame and moving those handles to the desired locations. For these types of models, all that is necessary is to create a global domain and global handles. Local handles are not required since local changes to the frame components are not necessary. Since local handles and domains for large models can consume a great deal of resources, you should avoid creating them unless it is necessary.
Creating Handles and Domains - space frame model

1. 2. 3. 4. 5. 6. 7. From the Tool page, select the HyperMorph module. Select the domains panel. Select create. Set the selector to global domain. Set the toggle to all nodes. Set the toggle to create handles. Click create. A global domain and global handles are created at useful positions throughout the space frame. In many cases, these handles will be where you want them to be. If not, delete them and add global handles elsewhere: Press F2 or go to the delete panel. Delete any unwanted handles. From the HyperMorph module, select the handles panel. Type in a name. Select an xyz position or any number of nodes where you want global handles. Click create.
A new global handle is created at each node or at the specified xyz location. If more than one handle is created at a time, the handles will each be given a unique name by appending a number after the name you have given. You should place global handles both in areas where you want to apply perturbations and in areas that you want to stay fixed. You can also use morph constraints to fix nodes in place during global morphing but if you want them to affect the surrounding mesh you must select the stretch mesh around nodes option when creating the morph constraint. If you want a part of your model to move as a rigid body, such as a wheel or the engine block, use a cluster type morph constraint.

Altair Engineering
A global domain and global handles for a full car model Exiting any panel in the HyperMorph module or the delete panel automatically triggers HyperMorph to refresh the handle influences, if necessary. Adding, editing, or deleting handles, domains, or symmetries, makes it necessary for HyperMorph to refresh the handle influences. For large models or large changes, this can be time consuming, so you will want to make all the changes you desire within each panel before exiting. There are many options available for moving the handles. The best one to use depends on the results that you want to achieve:
Altair Engineering
Matching a Mesh, Line, or Surface Data

The basic approach for HyperMorph is to move the handles into positions that change the shape of the model to match the mesh or geometry data. If you are going to match a mesh you need to make sure that the mesh does not get morphed when you are moving the handles. This can be accomplished by constraining the nodes on the target mesh. To constrain the nodes on the target mesh: 1. 2. 3. 4. 5. 6. From the HyperMorph module, select the morph constraints panel. Select the create/update sub-panel. Select the nodes on the target mesh. Switch the selector to fixed. Make sure that the stretch mesh around nodes option is unchecked. Click create. All the nodes in the target mesh are constrained to remain fixed during morphing operations as long as the constraint is active and the use constraints box is checked (see the morph options panel). Note that if you check the stretch mesh around nodes option, the nodes between the constrained nodes and the handles will be affected regardless of whether the mesh is continuous between them.
One of the most enjoyable ways to morph is interactively. As you drag a handle across the screen and you can watch the mesh move along with it. For large models it may be too slow to morph interactively in real time. But you can still morph interactively with any size model by setting HyperMorph to perform the morphing after you move the handle and release the mouse button. To morph interactively by moving the handle and releasing the mouse button: 1. 2. 3. 4. 5. 6. 7. 8. 9. From the HyperMorph module, select the morph panel. Select move handles. Change the upper middle selector to interactive. Change the rightmost toggle from real time to on release. Change the lower middle selector from on domains to along vector. Select a vector. Click morph. Select a handle on the screen and hold the mouse button down. Move the handle to the new location and release the mouse button. As you drag the mouse, the handle follows along the selected vector. Since on release was selected, only the graphics for the handle are updated, which leaves a dark trail through the mesh. When you release the mouse button, the morph is applied to the model and the graphics are updated for the entire model. If the handle position needs to be changed again, repeat steps 7 through 9.

Altair Engineering
10. Move more than one handle at the same time: Before clicking morph, select several handles on the screen. Perform steps 7 through 9. When you release the mouse, all of the selected handles are moved the same distance in the same direction.
Morphing to a profile line In the top frame, the global handles on either side of top of the windshield are selected. In the middle frame they are interactively moved upwards along a vector to a point matching with the profile line. In the bottom frame the process has been repeated for the other handles on the roof. The result is a morphed vehicle model that closely matches the profile line.
Altair Engineering
Morphing to a profile line A handle is added to the center of the rear windshield and is moved to better match the profile line. Handles may always be added or deleted from a model without affecting the current morphed state of the model. However, any shapes saved as handle perturbations may not yield the same morphed shape after handles have been added or deleted. If you intend to add or delete handles in your model, save your shapes as node perturbations. HyperMorph will give you the option of converting existing shapes from handle perturbations to node perturbations automatically after you add, edit, or delete any morphing entities. You can also select other features to drag the handle along such as a line, a plane, or a surface. HyperMorph uses the position of the mouse on the screen to figure out where you want to move the handle. You can use this feature to position a handle anywhere you want line or surface data. To match a target mesh or geometric data by moving the handles to a specified node location: 1. 2. 3. Change the upper middle selector from interactive to move to node. Select a handle. Select a node. The handle is moved to the position where the node was prior to morphing and the rest of the mesh morphs accordingly.
To create nodes on the fly on lines and surfaces: 1. 2. Hold the mouse button down and drag the mouse over a line or surface until it is highlighted. Click on the line or surface where you want the node. A node will be created and the handle will immediately be moved to the node. Altair Engineering

Making Parametric Changes

Dimensions such as distance and angle can be changed easily in HyperMorph. One way to do this is by translating or rotating handles. To translate or rotate handles: 1. Translate the handles. Change the upper middle selector from move to node to translate. Select a few handles. Select a vector and distance. Or Select the desired xyz translation. Click translate. The handles move the specified distance in the specified direction and the model morphs accordingly. 2. Rotate the handles. Change the upper middle selector from translate to rotate. Select a few handles. Select an axis of rotation. Set the rotation angle. Click rotate.
The handles rotate about the axis the specified angle and the model morph accordingly. 3. Specify dimensions more precisely in the alter dimensions sub-panel. From the HyperMorph module, select the morph panel. Select alter dimensions. Set the upper left selector to distance. Change the middle left selector to nodes and handles. Select node a and node b at nodes whose distance you want to change. Select follower handles for node a that are near node a. Select follower handles for node b that are near node b. Change the distance value. Click morph. HyperMorph moves the follower handles for node a as a group and the follower handles for node b as a group either towards each other or away from each other so that the new distance between node a and node b is equal to the specified distance. If the left selector is set to hold end a, node a will not move (same for node b). If the left selector is set to hold middle, both node a and node b will move the same distance.
Altair Engineering
Morphing by altering the distance between two nodes The width of the car is found by placing node a (green dot) on the right hand door and node b (blue dot) on the left hand door. The handles on the right side of the model are selected as followers for node a and the handles on the left side of the model are selected as followers for node b. The distance is changed and the model morphs. To change the angle: 1. 2. 3. 4. 5. 6. 7. Set the upper left selector to angle. Change the middle left selector to nodes and handles. Select node a, vertex, and node b at nodes whose angle you want to change. Select follower handles for node a that are near node a. Select follower handles for node b that are near node b. Change the angle value. Click morph. HyperMorph moves the follower handles for each end in a way so that the new angle between node a, the vertex, and node b are the specified angle. If necessary, HyperMorph will iterate to achieve the desired angle, or at least get close. If node a and node b are selected coincident with one of the follower handles, iterattion is not necessary.

Altair Engineering
Morphing by altering the angle formed by three nodes The slope of the windshield is altered by defining an angle using three nodes (green, blue, and red), selecting two handles at the front of the car as followers for node a (green), and selecting two handles on either side of the windshield as followers for node b (red node). The angle is changed from 160 degrees to 150 degrees. Note that the handles on either side of the windshield were constrained to move along the x-axis (front to back) thus maintaining the height of the roof.
Controlling Global Morphing with Handle Placement

Global morphing differs from local morphing in that there are no definite boundaries between the handles that restrict their zones of influence. When you perform global morphing operations, the parts of the model that are morphed are those that lie between the handles that are moving and those that are not. For the general space frame cases, positioning handles at the joints between the members of the space frame restricts the handle influences to the parts of the frame that they are touching. However, for cases where you are trying to morph a mesh that covers a wide area, you will need to place several handles across both of sides of the zone of influence. You can visualize the handles as places on a sheet of rubber where you are placing your fingers. If you place three fingers on one side and two on the other and try to stretch the sheet, the space between your fingers on the two finger side will be pulled towards the three finger side. By placing three fingers on each side, you allow for even stretching to occur between each set of fingers. In morphing this is accomplished by placing handles evenly along both sides of the mesh to be stretched.
Altair Engineering
Controlling global morphing with handles part 1 The handle on the roof is moved upwards and the center section of the car is morphed along with it.
Controlling global morphing with handles part 2 A handle is added directly below the handle on the roof near the center of the car. Now when the handle on the roof is moved upwards, only the part of the car between the roof and the handles along the midline of the car is stretched.

Altair Engineering
Altair Engineering
Adding handles to control global morphing Using several handles on either side, the fender of the model is morphed. Note that dependent handles are used to simplify the morphing operation. Also note that in cases where detailed shape changes are required, morph volumes will usually yield better results.
Mirror Images - Using 1-Plane Symmetry

If your space frame is symmetric, you can create a plane of symmetry at the center of your space frame and have your morphs applied in a symmetric fashion. To set up a plane of symmetry: 1. 2. 3. 4. 5. 6. 7. 8. 9. From the HyperMorph module, select the systems panel. Create a system at a node where the plane of symmetry is to be located and have the x-axis pointing normal to the plane to be created. Return to the HyperMorph module, select the symmetry panel. Enter a name. Select the global domain icon. Switch the selector from none to 1 plane. Select the system you created. Select x-axis as the axis to align the symmetry. Change the left toggle from approximate to enforced.

Altair Engineering
10. Click create. A plane of symmetry is created at the origin of the system and based perpendicular to the x-axis. The icon for a 1-plane symmetry is a rectangle positioned like a small mirror for the symmetry system. HyperMorph also links any handles that it finds that are reflections of the other. Since enforced was selected, HyperMorph creates new handles that are reflections of ones that are not linked to any others and creates a symmetric link between them. When handles are created or deleted, the enforced option will automatically create or delete handles on the other side of the symmetric link in order to enforce symmetry of the handles. The mesh itself does not need to be symmetric to use the symmetry options. The symmetry will be applied to the handles and handle perturbations that will influence the mesh in a symmetric fashion. If you want to add handles to one side of the plane of symmetry and not the other, yet still have symmetry active for the symmetric handles, use the approximate option instead.
System and 1-plane symmetry The plane of symmetry is positioned at the origin of the system and perpendicular to the x-axis. The perturbations applied to handles on one side of the plane of symmetry will be mirrored on to the other side. Now when you perform a morphing operation you only need to move the handles on one side of the plane of symmetry. If you have the symmetry links check box activated, HyperMorph automatically applies the handle movements to the handles on the other side of the plane of symmetry through the symmetry link. As a result, the model maintains symmetry across the symmetry plane.
Altair Engineering
Using 1-plane symmetry Three handles on the right hand side of the roof are selected and moved towards the centerline. HyperMorph automatically moves the corresponding nodes on the left hand side of the roof in a symmetric fashion.
Reducing 3D to 2D - Using Linear Symmetry

You can use linear symmetry to apply morphs to the model in such a way that the model is essentially reduced to two dimensions. To create a linear symmetry: 1. 2. 3. 4. 5. 6. 7. 8. From the HyperMorph module, select the systems panel. Create a system with the x-axis pointing along the dimension to be reduced. Return to the HyperMorph module, select the symmetry panel. Select create. Enter a name. Select the global domain icon. Switch the selector from 1 plane to linear. Select the system you created.

Altair Engineering
9.
Select x-axis as the axis to align the symmetry.
10. Click create. A linear symmetry is created along the x-axis of the system. The icon for a linear symmetry consists of two parallel lines along the dimension to be reduced. The origin of the system is irrelevant. Now each handle acts on the mesh as if it were a line extending along the system xaxis. If two handles lie along a line parallel to the system x-axis, they will be linked through symmetry. When you move a handle, all the nodes and handles with the same y and z coordinates will move along with it. Note: Since linear is a non-reflective type of symmetry, leaving symlinks unchecked will not prevent the handles from having linear influences. However, it will stop movements from one handle from being applied to others that are linked via the symmetry. If you wish to turn the symmetry off for a given morphing operation, make the symmetry inactive in the morph options panel.
System and linear symmetry The linear symmetry icon consists of two parallel lines along the system x-axis. Note that the placement of a linear symmetry system does not matter; the effect of the linear symmetry system is determined only by the direction of the x-axis. Applying a linear symmetry is very useful for making profile changes to a space frame model. It does not matter where the handles are placed along the x-axis, greatly simplifying the model set up. You only need to look at the model from one view to set up the handles and to morph the model. For models with a large number of elements this can save a great deal of time.
Altair Engineering
Using linear symmetry The handle on the rear part of the roof is selected and the entire rear portion of the roof is morphed along with it. With linear symmetry you only need to place handles on one side of the model to affect the entire profile.
Reducing 3D to 1D - Using Planar Symmetry

Planar symmetry is similar to linear symmetry accept that it reduces two dimensions instead of one. This enables you to morph your model along a single axis with only two or more handles. To create a planar symmetry: 1. 2. 3. 4. 5. 6. 7. 8. 9. From the HyperMorph module, select the systems panel. Create a system with the x-axis pointing along the dimension to be retained. Return to the HyperMorph module, select the symmetry panel. Select create. Enter a name. Select the global domain icon. Switch the selector from linear to planar. Select the system you created. Select x-axis as the axis to align the symmetry.
10. Click create. 234 HyperMesh 8.0 Users Guide

Altair Engineering
11. Return to the HyperMorph module. 12. Select the symmetry panel. 13. Select update by domain. 14. Select the global domain. 15. Select the planar symmetry. 16. Click update. A planar symmetry is created and the other two symmetries from the global domain are removed. You are allowed to have any number of symmetries associated with a domain and all will apply, but combining linear and planar symmetry in the same direction results in an unrealistic situation and poor influence calculations. The planar symmetry icon is displayed as a filled-in rectangle perpendicular to the system x-axis. Now each handle acts on the mesh as if it were a plane perpendicular to the x-axis. If two handles lie in a plane perpendicular to the system x-axis, they will be linked through symmetry. When you move a handle, all the nodes and handles with the same x coordinates will move along with it. Note: Since planar is a non-reflective type of symmetry, leaving symlinks unchecked will not prevent the handles from having linear influences. However, it will stop movements from one handle from being applied to others. If you wish to turn the symmetry off for a given morphing operation, make the symmetry inactive in the morph options panel.
System and planar symmetry The planar symmetry icon is a plane perpendicular to the system x-axis. Note that the placement of a planar symmetry system does not matter, the effect of the planar symmetry system is determined only by the direction of the x-axis. Applying a planar symmetry greatly simplifies a model. Essentially, it reduces the model to a lying along single axis. This symmetry type is very useful for changing dimensions along one axis through the entire model.
Altair Engineering
Using planar symmetry The handle at the rear of the model is selected and the entire trunk of the car is morphed. With planar symmetry you only need a row of handles lying roughly along the planar symmetry system x-axis.

Altair Engineering
Shell Model Strategies using Local Domains

Shell models are models that are made up primarily of shell elements, namely, quads, and trias. In general, a shell model represents many parts, each with numerous features such as holes and edges, and connected together using 1D elements such as bars and rigids. HyperMorph is designed to make it easy to change the size and shapes of the shell model features. This is done using one of the following methods: Moving the handles on the part to new locations Moving the global handles around the parts to new locations Altering the radius or curvature of curved edges of the parts, or mapping the nodes of a part to line or surface data
For most models you only need to create 2D domains for the entire part, but you can also add a global domain and global handles for shape alterations of a general nature.
Creating Handles and Domains - shell model

1. 2. 3. 4. 5. From the HyperMorph module, select the domains panel. Select create. Set the selector to 2D domains. Change the toggle to all elements or select all the elements in the model. Click create. A 2D domain is created for each group of continuous shell elements. Parts joined by 1D or 3D elements are separated into different domains. If partition domains is checked, the 2D domains will be partitioned according to the settings selected in the partitioning sub-panel of the domains panel. Once partitioned, edge domains are placed around the 2D domains and handles are placed at the ends of the edge domains. All of this is automatic, but 1D and 3D elements will not be placed into 1D and 3D domains unless you set the selector to local domains instead of 2D domains. In many cases, the domains and handles will be generated where you want them to be. If not you can always add, edit, or delete the handles and domains to meet your needs.
A shell model is partitioned into 2D domains 6. If you wish to generate a global domain as well as local domains for your model with a single button click, either change the selector to global and local and click create, or to auto functions and click generate.
In the case of the generate auto function, if there are any domains or handles in the model, HyperMorph will first ask if you want to delete all the current morphing entities. If you say yes, or if there are no morphing entities in the model, HyperMorph automatically generates 1D, 2D, 3D, and edge domains for the entire model and a global domain and handles as well.
Altair Engineering
For tria meshes which lack underlying geometry, both the node-based and element based partitioning algorithms may prove unsatisfactory. In these cases you may find it more effective to ignore curvature when partitioning. To accomplish this, go to the partitioning sub-panel, select element based as the algorithm for tria/tetra meshes, and change the uppermost toggle from curvature based to angle based. You may also want to lower the domain angle to 30 degrees. HyperMorph will then only make partitions along edges in the model where the domain angle is exceeded. You can then go in and manually divide the 2D domains where the curvature breaks should go. This method is almost mandatory for meshes that began as first order meshes but were transformed into second order meshes. For these meshes, HyperMorph will detect a curvature break at every element along a curve if the midpoint nodes of the elements have not been modified to capture the curvature. The result will be a domain for every element on a curve which makes morphing impractical. Solving the influence coefficients for 2D domains which contain more than 20,000 elements can become very time consuming even though it is only done after domain editing and during morphing operations such as radius change and map to geom. In these cases you may want to divide the large domains into multiple domains or lower the limit for the large domain solver. The large domain solver limit can be found in the global sub-panel of the morph options panel. However, even though influence calculations for large domains are more rapid, morphing using the large domain solver can be time consuming, and thus subdividing 2D domains can often be the best solution for efficient morphing. To divide your shell model, do this: 1. 2. 3. 4. 5. From the HyperMorph module, select the domains panel. Select create. Set the selector to 2D domains. Select the elements to be placed into a new 2D domain. Click create. When selecting the elements for the new domain you do not need to select only shell elements. HyperMorph automatically removes any other elements before creating the domain. It does not matter if the elements selected are already in a 2D domain. When the new domain is created, the elements are moved from the old domains to the new domain. Handle influences need to be recalculated every time handles, domains, or symmetries are added, edited, or deleted. They are also recalculated during radius changes and geometry mapping. These calculations occur when you enter or leave any HyperMorph panel or when you leave the delete panel. Thus, for models with large domains you will want to make all of your domain changes before exiting the domains panel. HyperMorph only recalculates the handle influences for handles in regions that have been edited. If the domains are not created exactly how you want them to be, you can edit them in the domains panel. The create sub-panel allows you to create new domains. The organize subpanel allows you to edit domains by adding and removing elements to or from a domain and by grouping domains together. The edit edges sub-panel allows you to split, merge, and place handles along edge domains. It is suggested that you create and edit all the 2D domains, then create and edit the edge domains. This order works better since creating or editing 2D domains will result in the regeneration of the surrounding edge domains with the previous modifications to those edge domains being discarded. Sometimes partitioning does not divide the mesh in the ways that would be most useful to you. Occasionally, elements end up in domains adjacent to where you want them or placed in their own domain. Partitioning is not an exact science, so some cleanup is sometimes required.

Altair Engineering
To move elements from one domain to another: 1. 2. 3. 4. 5. 6. 7. From the HyperMorph module, select the domains panel. Select organize. Change the selector to add nodes/elems . Change the toggle to local domain. Select the elements to be moved. Select the target domain. Click organize. This will move the elements from the domain that they are currently in to the selected domain. HyperMorph also refreshes the edge domains around both domains as well as the edge domains at the interface. New handles may also be created during this process, and if retain handles is not checked, handles may be deleted. It is suggested that you keep retain handles unchecked unless you have created shapes for the model that use the handles on the domains that you are editing.
Partitioning problems The model on the left shows problems that partitioning can encounter for some meshes. The model on the right has been corrected using the organize sub-panel of the domains panel. For this example the retain handles option was left unchecked resulting in the elimination of handles that are no longer on the corners of the 2D domains. Note that the edge domains are always partitioned for any new domain and handles are placed at the end of the edge domains. For the example above, a handle was created in a new location due to the edge partitioning being different for the two domain configurations. When you hold the mouse button down and the mouse is either over the icon for a 2D domain or over an element inside a domain, the edge domains surrounding the domain are highlighted as well. This allows you to better visualize the domain that you are selecting. The domain icon is placed at the centroid of the domain, and some domains can end up away from the elements of the domain and near other domain icons. Having the edges for the domain highlighted during selection is often necessary to tell which icon goes with which group of elements.
Altair Engineering
To group two or more domains together: 1. 2. 3. 4. 5. From the HyperMorph module, select the domains panel. Select organize. Change the selector to combine domains. Select the domains to be grouped together. Click organize. The selected domains are combined into a single domain and the surrounding domains and handles are updated.
Two domains are organized into one Edge domains are automatically partitioned when they are created. They are also updated whenever a change occurs for a domain of which they are on the edge. This is why any editing of the edge domains should come after the editing of the other domains. If you do your edge editing first, your changes may be erased when you edit the 2D domains. Edge domains are used to make radius changes, so it is important to make sure that any radius in the model that you intend to change be captured correctly by edge domains. HyperMorph tries to partition edge domains where curvature begins and ends, but in some cases it may not identify the proper starting and ending points. You may need to correct this by hand.

Altair Engineering
To split edge domains: 1. 2. 3. 4. 5. 6. From the HyperMorph module, select the domains panel. Select edit edges. Change the selector to split. Select an edge domain. Select a node on that domain that is not on the edge. Click split. The selected edge domain is split into two edge domains at the selected node. A handle is created at the selected node.
Splitting an edge domain - a circular edge domain is divided into two half circles A handle was created at the joint to allow you to manipulate the edges. To merge edge domains: 1. 2. 3. 4. 5. From the HyperMorph module, select the domains panel. Select edit edges. Change the selector to merge. Select any number of connected edge domains. Click merge. The two edge domains are merged into one edge domain. This function only allows you to merge edge domains that lie end to end such that the resultant edge domain is a continuous series of nodes. Note that you can also merge edge domains in the organize sub-panel.
Altair Engineering
Merging two edge domains The two half circles are merged into a single domain. Since retain handles was unchecked, the handle at the joint was deleted. You may also create dependent handles along an edge domain. This feature is quite useful for saving time when you are changing the radius for the edge domain. If the domain containing the radius to be changed is very large you may find it more efficient to place dependent handles on the edge domains whose radii you wish the change before you go into the morph panel. To place dependent handles on the edge domains whose radii you wish the change: 1. 2. 3. 4. 5. From the HyperMorph module, select the domains panel. Select edit edges. Change the selector to add handles. Select one or more domains. Click create. The dependent handles are created on the selected edge domains. These handles are dependent on the independent handles to either side of them along the edge domain.

Altair Engineering
Creating handles on an edge domain A dependent handle is created on each node of the edge domain. Creating dependent handles in this way has two significant effects. The first is that since they are dependent, movements applied to any of the independent handles on the edge will be transparently applied to the dependent handles. It will be as if they were not there. Secondly, when you make a radius change to an edge domain that has a handle at each of its nodes, the influences do not need to be recalculated, which makes the radius change process much faster for large models. - When you are satisfied with your domains, click return. HyperMorph calculates the influences for the handles and you are ready to begin morphing. During influence calculation you might run out of available memory. This generally happens when a given domain is too large and it contains too many handles. In these cases you should divide large domains, delete unnecessary handles, or lower the limit of the large domain solver.
Morphing on Local Domains

You can change the shape of a model with local domains and handles using one or more of the following methods: Moving the local handles Changing a distance or angle Changing the radius, curvature, or arc angle of an edge domain Mapping nodes to a line, plane, surface, or mesh Using section mapping, line and surface difference, and element offset Using freehand morphing capabilities such as move nodes, record, and sculpting
Altair Engineering
There are six ways to move handles in the move handles sub-panel of the morph panel: interactive This option allows you to move handles interactively by dragging the mouse across the screen. You select an entity such as a vector, line, plane, surface, or domains, to orient the mouse location in 3D space, and move a handle by clicking on it and dragging it to a new location. Interactive morphing is most effective for visualizing how the mesh will react when a handle is moved and for making approximate shape changes. If you want to move a handle a specific distance or to a specific position, it is better to use a non-interactive option. This option allows you to translate handles along a vector or element normals. This option allows you to rotate handles about an axis. This option allows you to position handles at specific XYZ locations or place them on lines, surfaces, or another mesh. These options allow you to position handles at specific node or point locations, or place them on lines, surfaces, or another mesh.
translate rotate move to XYZ move to node, move to point

Altair Engineering
Morphing by translating handles By selecting the two handles along the edge of the flange and translating them along a vector defined at the end of the section (green and blue nodes), the length of the flange is reduced.
Altair Engineering
Morphing by translating handles By selecting the three handles and translating them along a vector defined at the end of the section, the width of the channel is increased.
Morphing by translating handles By selecting the handles at the bottom of the part and translating them upwards, the thickness of the lower section is reduced.

Altair Engineering
Morphing by translating handles By selecting all the handles around the bolt boss and translating them horizontally, the position of the bolt boss is modified.
Morphing by rotating handles - constant By selecting all the handles at the end of the section and rotating them about a point (violet node), the end angle of the section is modified.
Morphing by rotating handles - constant The right end of the block is given a constant rotation.
Altair Engineering
Morphing by rotating handles - linear The entire block is given a linear rotation. Note how the magnitude of the twist increases linearly with the distance from the base (purple) node. When applying handle perturbations to your model, it is important to note that the nodes in the model follow the movements of the handles according to the influence coefficients. This concept comes into play when you are using the rotate function. After rotating handles you may find areas in the model (particularly those defined by curved edges) that are not rotated the same as the neighboring handles. This is because the nodes have followed the handles instead of being rotated about the axis. To correct this situation, check the true rotation checkbox. This will cause the nodes to be rotated as well as the handles with the amount of rotation being equal to the influence coefficient. Although it could be argued that true rotation is the "correct" way to morph via rotation of the handles, not all morphing applications are best done using true rotation.
Morphing by rotating handles - normal Although the highlighted handles are rotated, the circle at the center of the model remains on the same plane as before.

Altair Engineering
Morphing by rotating handles - true rotation During "true rotation" the nodes rotate along with the handles. While morphing a model, the following message may be displayed: Some handles selected are dependent on others. Would you like to ignore dependencies for this operation?. This occurs when both a dependent handle and the handle on which it is dependent are selected to be morphed. If you click yes the given perturbation is applied to each handle and the dependent handles are not given an additional perturbation inherited from another handle. If you click no, the given perturbation and any inherited perturbation is applied to each dependent node. For most cases you will want to click yes. The alter dimensions sub-panel of the morph panel allows you to change one of the parameters in the model, such as the distance between nodes, the angle between nodes, or the radius or curvature of an edge domain. The basic concept is as follows: Select two nodes (node a and node b). Select handles corresponding to those nodes. The handles selected are the ones that will move to make the distance between node a and node b (or angle with a vertex selected) equal the specified value. You must select at least one handle for each end and the handle may be coincident with one of the nodes. For solid models, controlling a particular dimension often involves moving more than one handle for each end.
Altair Engineering
Morphing by altering dimensions - distance By selecting the width of the bottom of the channel as the desired distance to alter (green and blue nodes) and by selecting the handles on the left (highlighted) to follow the green node and the handles on the right (shown as gray) to follow the blue node, the width of the bottom of the channel can be changed from 60 to 30 with the rest of the channel changing along with it.
Morphing by altering dimensions - distance By selecting the thickness of the block as the desired distance to alter (green and blue nodes) and by selecting the handles on the radius (shown as gray) to follow the green node and the handles on the back face (highlighted) to follow the blue node, the thickness of the block between the radius and the back face is altered from 15 to 25 by moving the entire back face.

Altair Engineering
Morphing by altering dimensions - angle By selecting the angle of the left side of the channel (green, blue, and red nodes) and by selecting the handle at the bottom right of the channel (shown as gray) to follow the green node and the handle at the red node (highlighted) to follow the red node, the angle of the left side of the section is changed from 110 degrees to 90 degrees.
Morphing by altering dimensions - angle By selecting the angle between two faces of the block (green, blue, and red nodes) and by selecting the handles at and directly below the green node (shown as gray) to follow the green node and the handles at, near, and below the red node (highlighted) to follow the red node, the angle is altered from 126 degrees to 90 degrees.
Altair Engineering
The radius, curvature, and arc angle options are used as follows. You select any number of curved edge or 2D domains, select the center calculation and style options, set the new radius, curvature multiplication, or arc angle factor for them, and click morph. All the domains are changed simultaneously. Note: The curvature tool scales your radius by a factor rather than a set radius, so if you want to change a radius from 5.0 to 8.0, you need to set the curve ratio to 1.6. The curvature tool is intended for domains that do not have constant curvature. Making the bias factor retroactive does not work for radius changes.
Note:
Morphing by altering dimensions radius center By selecting the edge domain around the edge of the hole, the radius is changed from 3 to 1.5.
Morphing by altering dimensions - radius - fillet By selecting the edge domain at the corner of the part and selecting the fillet option, the radius is changed from 5 to 2.5 and kept in line with the edges at either end.

Altair Engineering
Morphing by altering dimensions - radius - hold ends By selecting the edge domain at the corner of the part and selecting the hold ends option, the radius is changed from 5 to 10 with the ends held in place.
Morphing by altering dimensions - radius - hold end By selecting the edge domain at the corner of the part, selecting the hold end option, and selecting a node at the end of the edge domain, the radius is changed from 5 to 8 while the held end remains in place.
Altair Engineering
Morphing by altering dimensions - radius - fillet By selecting all of the edge domains that form the fillet between the flat sections and the round section and changing them simultaneously, the fillet is reduced from 20 to 8.
Morphing by altering dimensions - radius The radius is changed in three different ways. At the top right, the hold center option is used. At the lower left, the hold ends option is used. At the lower right, the fillet option is used. In all cases, both the top and bottom edge domains were selected as well as the 2D domain and the by normals option was used for center calculation. This option will directly calculate the radii for the nodes on the 2D domain instead of inferring them from the edge domains which makes this approach more accurate for 2D domains as well as more reliable for non-uniform meshes.

Altair Engineering
Morphing by altering dimensions - arc angle The arc angle of the mesh is changed from 60 to 90 degrees using by axis (the vertical axis and violet base node) to calculate the center of curvature.
Morphing by altering dimensions - arc angle The arc angle of the fillet is changed from 90 to 180 degrees using by normals to calculate the center of curvature. There are five methods available for calculating the center of curvature for the selected domains: by normals - this method is the default and uses the element normals to approximate where the center of curvature is for each node in the selected domains. This method is not always accurate, but often gives good results for regular meshes. by axis - you may select an axis which will serve as the center of curvature. by line - you may select a line which will serve as the center of curvature. by node - you may select a node which will serve as the center of curvature. by edges - this method uses the edge domains to calculate the center of curvature with the center lying in the plane of the edge domains. The symmetry option refers to how the morphing of the edge domains is applied to neighboring 2D domains. The auto-symmetry option was the default for HyperMorph prior to version 8.0. In 8.0 you may choose to turn off symmetry when using this option.
Altair Engineering
For auto-symmetry, the changes in the radii of the edge domains are applied to any 2D domain, depending on the number of edge domains you change for the 2D domains. If you change only one edge domain for a given 2D domain, the radius change will not be applied linearly across the 2D domain. If you change the radii of two edges for any given 2D domain, either a linear or planar temporary symmetry is created between the two edge domains for the 2D domain that will apply radius changes more linearly across the 2D domain. This works best if the mesh is regular. If you are changing only one edge for a 2D domain, you can increase the bias factor of any handles on an edge domain to yield a more even distribution. Mapping an edge domain to a line or a 2D mesh to a plane, surface, or mesh is done using the map to geom panel. This option is very effective for fitting a mesh to new geometric data. When mapping a domain to a geometric feature, all the nodes in neighboring domains are stretched along with it, minimizing mesh distortion. You have several options for determining how the nodes for the mapped domain are placed on the geometry. When mapping an edge domain or node list the nodes can be moved normal to the line, along a vector to the line, or distributed along the full length of the line. When mapping a 2D domain or selection of nodes to a plane, surface, or mesh, the nodes can be moved normal to the target, normal to the elements of the 2D domain or selected nodes, or along a vector. If you wish to fit a mesh to a surface, there is no option to do this automatically, however, with multiple mapping operations, or using the user control option you can fit a 2D domain to a surface. Furthermore, you have the option of creating a morph constraint between the nodes and the map target automatically after mapping. This constraint will allow you to do further morphing operations while maintaining the constrained nodes on the geometry. The map to geom panel is also effective for solid model meshing. You can create a block of solid elements roughly in the shape of the geometry that you are trying to mesh, and then use map to surface to morph the faces of the block to the geometry.
Morphing by mapping to line - automap - normal to geom The edge domain is mapped to a line by moving the nodes normal to the line.

Altair Engineering
Morphing by mapping to line - automap - fit to line The edge domain is mapped to the line by fitting them along the line. Any proportional spacing between the nodes will be maintained after mapping.
Morphing by mapping to surface By selecting the 2D domain on the top of the solid block to be mapped to the surface, the entire solid block is morphed to match the surface.
Altair Engineering
Morphing by mapping to surface A rectangular C-section is mapped to a curved surface.
Morphing by mapping to surface - user control This example shows the user-control approach to mapping a mesh onto a surface. The surface and 2D domain are selected and the user control button is clicked. This brings up a new panel which allows you to place handles or map edges prior to the surface mapping operation. One by one each edge domain is placed on one of the lines around the target surface using the fit to line option. This stretches the 2D domain to match the surface more closely than before. When the map button is clicked, the domain is the mapped to the surface, fitting it perfectly to the geometry.

Altair Engineering
Morphing Global Handles

Global handles are most effective when used to make general shape changes for a model, such as changing the basic shape of a model, stretching parts of a model, or making changes that involve the movement of many local handles. There are three methods available for affecting the way global handles influence the model, the direct method, the hierarchical method, and the mixed method. The default is the direct method, where the global handles move the nodes directly. In the hierarchical method, the global handles move the local handles which in turn move the nodes, but if any nodes lie outside of local domains they will be unaffected. In the mixed method, the hierarchical method is used for all nodes in local domains and the direct method is used for all other nodes. The hierarchical method maintains the shape of edge domains in the model, but if local handles are not evenly placed throughout the model, some parts will become distorted. The direct method gives you what you expect but often distorts the shape of the edge domains. For shell and solid models, better morphing is more likely to occur if you use the hierarchical method, and place local handles in areas where there is distortion.
Using Constraints
Morph constraints are a powerful tool that can be used to restrict the movement of nodes during morphing operations. The following types of constraints can be applied to any node: fixed, cluster, along vector, on plane, along line, on surface, and on elements. Whenever a handle is moved that influences a node, which is constrained, the node is moved according to the handle perturbation and is then projected back onto the feature to which it is constrained. This allows the nodes to slide across vectors, lines, planes, surfaces, and meshes, to remain fixed when handles are moved, or to move as a cluster along with other nodes. You may also constrain nodes where handles are located which, in effect, constrains the handles. When a perturbation is applied to a constrained handle, the handle are moved along the constraint feature regardless of the applied perturbation. This means that if you apply a translation in the x direction on a handle that is constrained along a vector x - y = 0, the handle moves along both the x and y axes. There are also morph constraints that can be applied to domains, such as the smooth constraint, which applies spline-based smoothing along the constrained edge domains, and model constraints, which allow you to set a given parametric target (such as length, angle, mass, etc.) and have HyperMorph adjust the model to meet that target. These constraints as well as bounded and set distance options for the node constraints are described more fully in the panel help. Morph constraints can be very useful for morphing a mesh that has been mapped to, projected to, or created upon a surface. Note that the map to geom operation allows you to have a morph constraint automatically created after mapping. Once you have done so, the nodes will remain on the surface during morphing operations. Note: Although morph constraints can keep nodes on a curved line or surface during morphing operations, when morphs are saved as shapes and then turned into shape variables for optimization, the nodes will not stay on the line or surface during optimization. This is because optimization is a linear process and the shapes will be treated as linear, meaning that the nodes will move directly from their original point to their maximally perturbed point without moving along any constraint.
Altair Engineering
Controlling handle positions with morph constraints The angle of the lower right corner is changed from 74 to 90 degrees using the alter dimensions (angle) operation. The middle frame shows the result with no constraints. The frame on the right shows the result with the node in the upper right corner constrained to move along a vector that lies along the top edge.
Nodes tracking a line during morphing The nodes along the right edge domain are constrained to the line. When the handle is moved, it and the other constrained nodes move along the line.

Altair Engineering
Morphing after mapping to surface All mapped nodes are automatically constrained to the surface. When the handles are translated, the nodes are moved along the surface a distance corresponding to the applied handle perturbations. If the handles were also part of the map to geom operation, they too will be moved along the surface regardless of the applied perturbation. In this example, the handles were translated linearly. HyperMorph automatically placed the handles back on the surfaces after applying the translation so that the constraint was obeyed.
Using Biasing
Biasing allows you to control the shape of a mesh when applying handle perturbations. Biasing increases or decreases the influence of a handle over the nodes within its area of influence. If the biasing values for all of the handles are equal to 1.000, which is the default value for all handles except for dependent handles on 1D domains, the morphing between the handles is linear, provided both handles are global handles or they are located on edge domains. Higher biasing values generate a smooth curvature near the handles, while lower biasing values generate harsh corners near the handles. To smoothly change the shape of a domain it is recommended that you use a biasing factor of 1.000 at the corners, 2.000 at the edges, and 3.000 in the middle.
Altair Engineering
Biasing for a 2D domain The model at the upper left has all five handles with the default biasing value of 1.000. The model at the upper right shows the four corner handles with a biasing value of 1.000, and the mid-edge handle with a biasing value of 2.000. The model at the lower left has all five handles with the default biasing value of 2.000. The model at the upper right shows the four corner handles with a biasing value of 1.000 and the mid-edge handle with a biasing value of 0.500.
Biasing to reduce mesh distortion When the hole is moved downward with a biasing factor of 1.000 for the handle at the hole, the mesh folds over due to the influences of the other handles (middle frame). When the biasing value of the handle at the hole is increased to 3.000, the mesh unfolds (right frame). Biasing can be applied retroactively after a morphing operation. After applying a morph, you can change the biasing value by activating the make retroactive check box, and have the current list of applied morphs updated to reflect the new biasing values. This is useful in selecting a good biasing value to apply for a given morph. Apply the morphs and change the biasing values retroactively until you get the shape that you want.

Altair Engineering
Solid Model Strategies using Local Domains

Solid models are models that are made up of solid elements, namely, tetras, pentas, and hexas. In general, a solid model represents a single part with numerous features such as holes, edges, bosses, flanges, and ribs. HyperMorph is designed to make it easy to change the size and shape of features in a solid model. This is done using one of the following methods: Moving the handles on the part to new locations Moving the global handles around the part to new locations Altering the radius or curvature of curved edges of the part Mapping the nodes of the part to line or surface data.
For solid models, it is only necessary to create a single 3D domain for the entire part. You can also add a global domain and global handles for shape alterations of a general nature.
Creating Handles and Domains - solid model

You can create a single 3D domain consisting of all the elements in a model. If the model is made up of more than one part, each part is placed in its own 3D domain. The surfaces of each 3D domain are covered with shell elements that are placed in a component named ^morphface. The elements in ^morphface covering each 3D domain are placed into 2D domains. If partition 2D domains is checked, these 2D domains are partitioned according to the settings selected in the parameter subpanel of the domains panel. Once partitioned, edge domains are placed around the 2D domains and handles are placed at the ends of the edge domains. This procedure is automatic. In many cases, the domains and handles are generated where you want them to be. If they are not, you can add, edit, or delete the handles and domains to meet specific needs. To create a single 3D domain consisting of all the elements in the model: 1. 2. 3. 4. 5. From the HyperMorph module, select the domains panel. Select create. Set the selector to 3D domains. Change the toggle to all elements, or manually select all of the elements in the model. Click create.
A 3D domain is created for a solid model Note the automatic creation and partitioning of 2D domains on the face of the solid and the creation of edge domains and handles for the 2D domains.
Altair Engineering
To create a 3D domain along with a global domain and global handles to your model: 1. 2. 3. 4. From the HyperMorph module, select the domains panel. Select create. Set the selector to auto functions. Click generate. If there are any domains or handles in the model, you are asked if you want to delete all the current morphing entities. If you click yes, or if there are no morphing entities in the model, 1D, 2D, and 3D domains are automatically generated for the entire model, as well as a global domain and handles.
Automatic generation of domains on a solid model Note the addition of a global domain, global handles, and 1D domain, which produces dependent (green) handles. If you do not select partition 2D domains when you generate a 3D domain, the 2D domain made up of the elements on the surface of the 3D domain will not have edge domains and thus no handles will be generated for it. Without handles, morphing cannot be performed. However, this approach will give you a blank slate 2D domain that you can partition by hand. For meshes on which the automatic partitioning does not work well, such as first order tetra meshes, you may find it easier to start with a blank slate rather than editing the automatically created domains. Be sure to try both methods of partitioning, element based and node based, before deciding to partition by hand. Note: The element based method sometimes works better on second order tetras since it accounts for element curvature. However, if the second order tetras are converted first order tetras and thus have no curvature, the node based partitioning will work better.

Altair Engineering
Also, for first order tetra meshes, you may find it more effective to ignore curvature when automatically partitioning. To do this, in the parameters sub-panel, change the uppermost toggle from curvature based to angle based. You may also want to lower the domain angle to 30 degrees. Partitions will be made only along edges in the model where the domain angle is exceeded. You can then manually divide the 2D domains where the curvature breaks should be located. This method is very helpful for meshes that began as first order tetra meshes but then were then transformed into second order meshes. For these meshes, a curvature break is detected at every element along a curve if the midpoint nodes of the elements have not been modified to capture the curvature. This results in a domain for every element on a curve which makes morphing impractical. Solving the influence coefficients for 3D domains which contain more than 20,000 elements can become very time consuming even though it is only done after domain editing and during morphing operations such as radius change and map to geom. In these cases you may want to divide the domain into multiple domains using the subdivide 3D function in the update sub-panel of the domains panel, or lower the limit for the large domain solver. The large domain solver limit can be found in the global sub-panel of the morph options panel. However, even though influence calculations for large domains are more rapid, morphing using the large domain solver can be time consuming, and thus subdividing 3D domains can often be the best solution for efficient morphing. Additionally, if you are only going to morph a part of your 3D mesh, you only need to create domains for that part. To subdivide your solid model: 1. 2. 3. 4. 5. 6. From the HyperMorph module, select the domains panel. Select update. Set the selector to subdivide 3D. Select the 3D domains to be subdivided. Select any 2D domains on the surface of the 3D domain that are permissible for HyperMorph to split into more than one 2D domain. Click subdivide. HyperMorph automatically subdivides the 3D domains into one or more 3D domains while leaving the 2D domains not selected as being divisible unchanged. Not that in some cases HyperMorph will not be able to subdivide a 3D domain without dividing an indivisible 2D domain. In these cases the 3D domain will be left undivided.
To divide your solid model manually: 1. 2. 3. 4. 5. From the HyperMorph module, select the domains panel. Select create. Set the selector to 3D domains. Select the elements to be placed into a new 3D domain. Click create. When selecting elements for the new domain, you do not need to select only solid elements, other elements are automatically removed before the domain is created. Therefore, you do not need to be concerned about selecting the morphface elements. Also, it does not matter if the selected elements are already in a 3D domain. When the new domain is created, the elements are moved from the old domains to the new domain. Morphface elements are placed at the internal interface between the new domain and the other domains and create a 2D domain for the interface, but it will not partition the interface. This better accommodates the division of tetra meshes that cannot be divided along flat or curved internal faces and thus would be partitioned into many domains.
Altair Engineering
Note:
When you divide a 3D domain into parts, it has the effect of partitioning the surface of the original 3D domain along seams where the divisions were made. So when you divide your model into 3D domains, make sure that you divide it along lines where you want your 2D domains on the surface to be.
Dividing a 3D domain into many 3D domains can be very useful for controlling the movement of nodes within the domain when the handles on the surface are moved. When some meshes are morphed, the internal elements can become distorted. This is generally caused by handle influences extending too far through the 3D domain. You can divide your 3D domains to restrict the handle influences and control mesh distortion.
A single 3D domain is split into four 3D domains The influences of the handles will not extend across the boundaries between the domains. Influences must be recalculated every time handles, domains, or symmetries are added, edited, or deleted. They are also recalculated during radius changes and geometry mapping. These calculations occur when you enter or leave a HyperMorph panel or when you leave the delete panel. For large models you will want to make all of your domain changes before exiting the domains panel. The influences for handles are only recalculated in regions that have been edited. If the domains are not created exactly the way you want them, you can edit them in the domains panel. The create sub-panel allows you to create new domains. The organize sub-panel allows you to edit domains by adding and removing elements to or from a domain and by grouping domains together. The edit edges sub-panel allows you to split, merge, and place handles along edge domains. Since creating or editing 3D domains results in the creation of 2D and edge domains, and creating or editing 2D domains results in the creation and deletion of edge domains, you should perform the tasks in the following order: Create and edit all the 3D domains that you want first. Create and edit the 2D domains. Create and edit the edge domains.
Automatic partitioning does not always divide a mesh in the most useful ways. Occasionally, elements end up in domains adjacent to where you want them or placed in their own domain. Some cleanup may be required.

Altair Engineering
To move elements from one domain to another: 1. 2. 3. 4. 5. 6. From the HyperMorph module, select the domains panel. Select organize. Change the selector to add nodes/elements. Select the elements to be moved. Select the target domain. Click organize. The elements are moved from their current domain to the selected domain. The edge domains around both domains are refreshed, as well as the 2D domains at the interface if solid elements are being organized. New handles may also be created during this process, and if retain handles is not checked, handles may be deleted. You should keep retain handles unchecked unless you have created shapes for the model that use the handles on the domains that you are editing.
The model on the left shows problems that partitioning can encounter for some meshes. The model on the right has been corrected using the organize sub-panel of the domains panel. For this example, the retain handles option was left unchecked, resulting in the elimination of handles that are no longer on the corners of the 2D domains. Note: Holding the mouse button down when the mouse is either over the icon for a 2D or 3D domain or over an element inside a domain, will highlight the edge domains surrounding the domain. This allows you to visualize the domain that you are selecting. The domain icon is placed at the centroid of the domain, and for some domains it can end up away from the elements of the domain and near other domain icons. Having the edges for the domain highlighted during selection is often necessary to tell which icon goes with which group of elements.
Altair Engineering
To group two or more domains: 1. 2. 3. 4. 5. From the HyperMorph module, select the domains panel. Select organize. Change the selector to combine domains. Select the domains to be grouped. Click organize. The selected domains are combined into a single domain, and the surrounding domains and handles are updated. Edge domains are automatically partitioned when they are created. They are also updated whenever a change occurs for a domain of which they are on the edge. This is why you should edit the edge domains after the other domains have been edited. If you perform edge editing first, your changes may be erased when you edit the 2D and 3D domains. Edge domains are used to make radius changes, so it is important to make sure that any radius in the model that you intend to change be captured correctly by edge domains. HyperMorph attempts to partition edge domains where curvature begins and ends, but in some cases, it will not identify the proper starting and ending points. You will need to correct this by hand. To split edge domains: 1. 2. 3. 4. 5. 6. From the HyperMorph module, select the domains panel. Select edit edges. Change the selector to split. Select an edge domain. Select a node on that domain that is not on the edge. Click split. The selected edge domain is split into two edge domains at the selected node. A handle is created at the selected node.
The lower edge domain has been split at the gray node (left model), which becomes a handle (right model). Now the radius of each new edge domain may be modified independently of the other.

Altair Engineering
To merge edge domains: 1. 2. 3. 4. 5. From the HyperMorph module, select the domains panel. Select edit edges. Change the selector to merge. Select any number of edge domains. Click merge. The two edge domains are merged into one edge domain. This function only allows you to merge edge domains that lie end-to-end such that the resultant merged edge domain is a continuous series of nodes. You may also create dependent handles along an edge domain. This feature helps save time when you are changing the radius for the edge domain. If a model is very large, you may find it more efficient to place dependent handles on the edge domains whose radii you wish to change before you enter the morphing panel. Note that you can also merge edge domains in the organize sub-panel.
To create dependent handles along an edge domain: 1. 2. 3. 4. 5. From the HyperMorph module, select the domains panel. Select edit edges. Change the selector to add handles. Select one or more domains. Click create. Dependent handles are created on the selected edge domains. These handles are dependent on the independent handles to either side of them along the edge domain.
Dependent handles created using the handles on edge feature Creating dependent handles in this way has two significant effects. The first is that since they are dependent, movements applied to any of the independent handles on the edge are transparently applied to the dependent handles. It will be as if they were not there. Secondly, when you make a radius change to an edge domain that has a handle at each of its nodes, the influences do not need to be recalculated, which makes the radius change process much faster for large models.
Altair Engineering
6.
When you are satisfied with your domains, click return. The influences for the handles is calculated and you are ready to begin morphing. Note: During influence calculation for large models you might run out of available memory. This generally happens when a given domain is too large and it contains too many handles. In these cases, you should divide large domains, delete unnecessary handles, or lower the limit of the large domain solver.
Viewing Solid Models - solid model

The HyperMesh graphics engine supports different visual options for viewing models as you work on them. surface-only wire frame In this default mode, your model is displayed as a wire frame, but only the surface elements are drawn because in a solid model, a full wire frame can make it very difficult to visualize the model because every element in the model is displayed. Since HyperMorph creates a component called ^morphface, which contains shell elements on the surface of the 3D domains, the default setting is to display only that componentthus showing only the outer surface of your model and making it easier to work on. However, since the viewing mode is still wire frame, you will see the two sides of your model superimposed over each other.
solid fill
The option produces a display that is similar to what you see when you perform a fill plot in the hidden line panel. You only see the side of the model that is facing you (as if your model was a real part). You can still display the surface mesh, if desired (as shown).

Altair Engineering
You can also view a solid model for morphing by turning off all the components and looking at only the domains and handles. This is similar to looking at the model in a meshless wire frame mode. Partitioning generally captures all the features on the surface of a solid, so by viewing only the domains you can visualize the model with minimal clutter.
Altair Engineering
HyperBeam Module
The HyperBeam module allows you to calculate general beam section properties from geometry or element data. This data can be imported into the HyperMesh finite element pre-processor and used to create one-dimensional (bar, beam, rod) element property data for an FEA model. It is a threestep process; steps one and three are performed within HyperMesh and step two is performed in the HyperBeam module. Step One Step Two Step Three Beam section definition from line, surface, or element data takes place in the HyperBeam panel within HyperMesh. Beam section manipulation and property calculation takes place in the HyperBeam module. Beam section properties are imported back into HyperMesh and applied to element property cards.
Each step is described in more detail below.
Step 1: Beam Section Definition.

The HyperBeam panel in HyperMesh allows you to: Define the beam cross sectional plane via the existing HyperMesh vector definition methods. Select the lines, elements or surfaces that represent the beam cross section. Transfer the data into the HyperBeam module. Access previously defined beam cross sections for editing in the HyperBeam module.
Step 2: Beam Section Manipulation.

The HyperBeam module allows you to: View the beam section, its local coordinate system, and any beam section properties calculated, as dictated by the beam section template. Edit the beam section graphically via mouse clicks and drags. Operations that can be done this way include: Editing section thickness Creating, moving, and deleting vertices Editing line segments, including splitting and joining operations Selecting vertex coordinates when the spreadsheet display is active
Edit the beam section manually via dialogs and a spreadsheet containing the vertex 2-D coordinates. Operations that can be accomplished in this way include: Hand editing of vertex coordinate geometry and connectivity Editing section thickness Creating parts Editing part to vertex associativity Parameterizing the beam section for optimization via a spreadsheet containing the vertex 2-D coordinates Organizing HyperBeam sections into a single level structure of HyperBeam collectors

Altair Engineering
Step 3: Beam Property Import.

You can import beam section properties into HyperMesh that have been defined in HyperBeam by using the collectors panel with the properties entity selected. The beam section characteristics are displayed in the card image of the property collector but must be edited from within the HyperBeam module.
Altair Engineering
Example of the Three-Step Process

This example illustrates how HyperBeam can be used to attach beam section properties to a OptiStruct PBAR card image. It assumes that the OptiStruct user profile is loaded.
The blue lines are plot elements denoting the beam section. Elements or lines can be used to describe a beam section. The purple line is a plot element created in the global y-direction. This plot element will be used to align the section within HyperBeam. The shell section subpanel is selected from the HyperBeam panel. The selector type is set to elems and the blue plot elements are selected. project to plane is then selected under cross section plane:.
N1, N2 and N3 locations are selected as shown in the figure below. And the plane base node is chosen (change option to specify node) at N1 also.

Altair Engineering
The vector created by N1 to N2 describes the local y-axis used in HyperBeam. N3 describes the positive sense of the z-axis. It is important to note the alignment of the local axes at this point. Later we will need to know this when the beam section is aligned for bar elements. HyperBeam is invoked when you click create.
Altair Engineering
If the node selection was performed differently, and N3 was reversed (essentially the z-direction was flipped), HyperBeam would yield different results as shown below.

Altair Engineering
Once HyperBeam solves the cross sectional properties, it is necessary to attach the beam section to the PBAR card image. This can be done in the collectors panel.
After the card image is created, the PBAR card image must be attached to the 1-D element in question. This operation is performed in the bars panel.
Bar element alignment using HyperBeam sections is very straightforward if the section was defined using an absolute y-direction. The direction specified within the bars panel defines the alignment along the y-direction. In this case, the y-direction within the bars panel will align with the y-direction of the HyperBeam section. If there were a 1 within the Z comp, the z-direction within the bars panel will align with the y-direction of the HyperBeam section. The figure below illustrates the alignment of the global axis, the HyperBeam alignment axis, and the local bar element alignment axis.
Altair Engineering
The beam cross section can also be attached to the beam to visually inspect the alignment. This option can be found in the review sections subpanel in the HyperBeam panel.

Altair Engineering
Cross-sectional Properties as Calculated by HyperBeam

The beam cross section is always defined in a y,z plane. The x axis is defined along the beam axis. The coordinate system defined by the user is called the local coordinate system; the system parallel to the local coordinate system with the origin in the centroid is called the centroidal coordinate system; the system referring to the principal bending axes is called the principal coordinate system. For shell sections, only the theory of thin walled bars is used. This means that for the calculation of the moments and product of inertia terms of higher order of the shell thickness t are neglected. Thickness warping is also neglected. Area
Area Moments of Inertia
Area Product of Inertia
Radius of Gyration
Elastic Section Modulus
Max Coordinate Extension
Plastic Section Modulus
Altair Engineering
Torsional Constant
Solid
Shell open
Shell closed
Elastic Torsion Modulus
Solid
Shell open Shell closed
Warping Constant (normalized to the shear center)
Shear deformation coefficients

Altair Engineering
Shear stiffness factors
Shear stiffness
Nastran Type Notation
References
W.D. Pilkey and W. Wunderlich, Structural Mechanics Variational and Computational Methods, CRC Press, Boca Raton, FL, 1993. H. Goeldner, ed., Lehrbuch Hoehere Festigkeitslehre, Fachbuchverlag, Leipzig, 1979. A. Gjelsvik, The Theory of Thin Walled Bars, Wiley & Sons, 1981. U. Schramm, V. Rubenchik, and W.D. Pilkey, Beam Stiffness Matrix based on the Elasticity Equations, International Journal for Numerical Methods in Engineering 40 (1997) 211-232.
Altair Engineering
HyperBeam Environment
HyperBeam has three main panes: the section browser, shell section graphics pane, and results/spreadsheet sections. It also has a menu bar, toolbar, and status bar. Click each section of the HyperBeam window below to access detailed information about the menu areas.

Altair Engineering
Section Browser
This section browser presents a hierarchical view of all of the beam sections and section collectors on your database. At the highest level is the model. Below that are all of the collectors followed by the beam sections at the lowest level. HyperBeam displays this hierarchy in a standard tree structure. You can use the section browser to find a particular section of your model for displaying or editing. You can also reorganize the database by moving sections between collectors, copying sections, and renaming sections and section collectors. Section types are identified by icons, as listed below: Shell Solid Standard Generic You can perform the following tasks in the section browser: To rename a section or section collector, click once on the item to select it, click again to indicate that you want to rename it, and enter the new name. To copy a section, select the section, select Copy from the Edit menu, select the collector where you want the section to appear, and select Paste from the Edit menu. To move a section, select the section, select Cut from the Edit menu, select the collector where you want the section to appear, and select Paste from the Edit menu. There are two ways to "drag and drop": Move a section to another collector by selecting the section you want to move, and dragging and dropping it into the collector where you want it to be located Copy a section to another collector by selecting the section you want to move, holding down the control key, and dragging it to the collector where you want it to be located.
To export sections to an external file, select a section by left-clicking on it, select multiple sections by holding down the control key and left-clicking on multiple sections, right-click in the section browser pane, choose Export Section from the pop-up menu, give a filename and location in the Save As window (it is recommended to use the .bm extension to save beam section files), click Save. To view thumbnail images of the sections in a section collector, select the collector branch in the section browser window, thumbnail images of all the sections are shown in the graphics pane. To view thumbnails of selected sections, select the desired sections or section collectors in the section browser (hold down the control key to select multiple items), right-click in the section browser pane, choose Create Thumbnails from the pop-up menu, until you create thumbnail images for a different selection of sections, the thumbnail images that were just created may be viewed in the graphics pane by selecting Model in the section browser tree.
Altair Engineering
The Importance of Flanges

When HyperBeam computes the properties for the section, the metal thickness used for a flange is the sum of the thicknesses of all the parts that share it. If you accidentally omit those vertices from the connectivity for a part, then HyperBeam underestimates the stiffness of a section.
Shell Section Graphics Pane

The graphics pane displays a representation of the geometric layout of the section. For shell sections, each sheet metal part is drawn by lines connecting the dots that show the section's vertices. Each part is also marked with a slider bar that you can use to adjust the part's thickness. The bar is labeled with the part's number in the section and the current numerical value of the thickness, separated by a colon. Each vertex may or may not be labeled by its ID, depending on if you have the toggle set on the toolbar or the view menu. The section's torsion and warping factor are displayed in the lower left corner of the pane, if you have them enabled on the view menu. The section's local coordinate system and its principle coordinate system (at its centroid) are displayed, if you have them enabled on the view menu. You can modify the section itself with the shell section editing tools. The centroid appears as a plus with a circle around it. The shear center appears as an x with a circle around it. The section axis is always drawn with its y-axis pointing to the right. You have control (on the preferences dialog) over whether the z-axis points up or down, or equivalently, if the section's x-axis points into or out of the monitor. The preferences dialog allows you to set the font and background color to use in the text graphics pane. The color of the lines for each part is selected on the section's properties dialog.

Altair Engineering
Results/Spreadsheet Pane
Section Properties Results
Whenever HyperBeam computes the section properties of the current section, it displays them in the results pane. You cannot edit the text in this portion of the window, but you can select it and copy it to paste it into another application such as a word processor. You will find controls for the actual format and layout of the text and results in two locations. You can change the display of text and values by editing the scripts file. If there are computed values that are not necessary, you can delete them from the template so that they are not displayed. Also, there are more results computed than are displayed in the default template, so you may choose to add additional values to the template. You can specify a new results template by selecting the Results tab on the Edit/Preferences dialog. To see the list of all the results available, consult the documentation for the results output template. You specify the text font, text color, and background color on the Results tab on the Edit/Preferences dialog. The section results pane shares screen space with the section definition spreadsheets, to toggle between them, you can use the spreadsheet button on the toolbar. If the results are not available, such as when you have edited the section definition and dynamic update is disabled, then HyperBeam displays the message, "No results to display."
Standard Section Spreadsheet

For a standard section, the spreadsheet pane displays a list of the section's variables and their current values. If the section has been designated an optimization section on the properties dialog, then the spreadsheet additionally displays optimization bounds for each variable. The spreadsheet pane supports export to other applications. If you select Copy from the Edit menu, you can switch to a word processor or spreadsheet program and paste the contents into another document. You can toggle this region of the window between results display and spreadsheet display by using the button on the toolbar.
Shell Section Spreadsheet (non-optimization version)

For a shell section, the spreadsheet pane displays a list of the section's vertices and their coordinates. You can type a new value into any of the coordinates, and the associated vertex moves to the new location. If this section has been designated an optimization section on the properties dialog, then the spreadsheet displays equations, variables, and optimization bounds for the section. The spreadsheet pane supports export to other applications. If you select Copy from the Edit menu, you can switch to a word processor or spreadsheet program and paste the contents into another document. You can toggle this region of the window between results display and spreadsheet display by using the button on the toolbar.
Altair Engineering
Optimization Shell Section Spreadsheet

If the shell section has been designated an optimization section on the Properties dialog, then the shell-section spreadsheet expands to display the rest of the necessary information. Each vertex coordinate now has three values: an initial value, a lower bound, and an upper bound. If all three values are equal, it is assumed the optimizer treats that coordinate as fixed. Alternatively, a vertex coordinate can be defined using an equation. Click the coordinate and it will appear as the dependent vertex. Next, click the right-hand side of the equation and enter the formula. In the equation, you can use other vertex coordinates, variables, arithmetic functions, or trigonometric functions, with a few restrictions. A vertex that is defined by an equation may not appear on the right-hand side of another equation. The equation is passed to the optimization solver, so it must be formatted as appropriate for that solver. (For example, blank spaces may be prohibited.) To delete an equation, click the vertex coordinate to make it active and delete the text of the equation. The coordinate will be set equal to the last value it had calculated. To define a variable for use in an equation, use the right mouse button to select the variable's section. A menu is displayed that allows you to choose between adding or deleting a variable. If you choose add, a new blank line appears, into which you can enter the variable's name, initial value, and optimization bounds. To delete a variable, click the variable with the right mouse button. A menu is displayed. Select delete variable on the menu.

Altair Engineering
HyperBeam Menu Bar

The HyperBeam menu bar allows you to perform a wide variety of operations using drop-down menus. Some operations such as importing and exporting are accomplished only from the menu bar. Other operations can be performed using either the menu bar or the corresponding tool button.
File Menu
New Save Import Section Export Section Export Results Print Print Preview Print Setup Exit Create a new section collector, standard section, or generic section. Save the beam cross-section. Opens a file browser so you can import a beam cross-section. Opens a file browser so you can export a beam cross-section. Options are provided to export all sections, or only selected sections. Opens a file browser so you can export the results for the selected section to a text file. Prints the currently displayed beam cross section and the section analysis results. Displays a print preview. Allows you to set up printer preferences. Exit the HyperBeam module and return to HyperMesh.
Edit Menu
Undo Redo Cut Copy Paste Delete Preferences Undo the last procedure. Redo the last procedure. Copies and removes the selected text or entity. Copies the selected text or entity. Paste the selected text or entity into the location of the cursor. Delete the currently selected text or entity. Set the graphics and results preferences. The Preferences dialog allows you to specify the appearance and behavior of HyperBeam. On the Edit menu, select Preferences. There are controls for the results/spreadsheet window and controls for the section graphics window available. The Graphics and Results tabs in the Preferences dialog allow you to set preferences for the section graphics window and the results/spreadsheet window. From the Edit window, select Preferences to display the tabs.
Setting the Section Graphics Options

The Graphics tab allows you to set the following options: Background color Specifies the main background color for the section graphics region.
Altair Engineering
Font Background effects
Displays the font dialog box, which allows you to choose which font and face to use for section graphics window. Allows you to specify a bitmap or second color for a gradient to display as the background of the section graphics window. Allows you to specify whether HyperBeam should display the section with the x-axis coming out of the page (so z axis goes up) or going into the page (so the z-axis goes down). Allows you to display a grid behind the section image. The distance entry field allows the distance between nodes of the grid to be adjusted. The Scale Thumbnails checkbox allows thumbnail images to be displayed, so that their sizes are relative to one another.
x-axis direction
Grid
Thumbnails
Specifying the Results/Spreadsheet Display

The Results tab allows you to set the following options: Background color Font Select the background color for the results display. Displays the font dialog box, which allows you to choose which font and face to use for the results display. It is recommended that you use a fixed-width font, such as courier, for best formatting. Results output templates The computed results for a section are formatted using a user-specified TEMPLEX scripts. See the Templex Reference On-line Help for additional details. Each section type can have its own custom script, so it can display just those values known to be relevant. You may substitute your own solver to compute values for thin Shell sections. Contact Altair for technical details on exchange file formats and return codes.
External solver for thin shell sections

Altair Engineering
View Menu
Toolbar Status Bar Circle zoom Zoom in Zoom out Pan Fit to screen Update Results Dynamic update Systems Torsion Factor Warping Factor Spreadsheets Vertex Ids Turns on and off the display of the toolbar. Turns on and off the display of the status bar. Allows you to specify the section that you want to zoom in on to examine in greater detail. Magnifies the graphic in the graphics pane. Reduces the size of the graphic in the graphics pane. Moves the model in the selected direction. Scales the graphic so that it exactly fits the active window. When selected, updates results. If selected, automatically updates the display when you make changes. Turns on and off the display of the system coordinate axes. Turns on and off the display of the Torsion Factor. Turns on and off the display of the Warping Factor. Switches the display in the Results/Spreadsheet pane. Turns on and off the display of the Vertex IDs.
Tools Menu
Break a Segment Join Segments Create a New Part Move Vertices Reorient Shell Section... Part Editor... Properties... Allows you to break a segment so that you can add a new vertex. Allows you to delete a vertex to join two segments. Allows you to add a new sheet metal part to the current section. Allows you to move vertices. Allows you to change the local coordinate system that defines the beam cross section. Allows you to rearrange parts in a section, rearrange vertices in a part, or add or remove vertices from a part's definition. Allows you to modify the properties of the beam cross-sections.
Altair Engineering
Reorient Shell Section

The reorient shell section dialog allows you to change the local coordinate system that defines the beam cross section.
To specify a new coordinate system, you must specify the location of its origin relative to the vertices and the direction of the y-axis. Specifying the Origin You can designate a vertex, the current shear center, or the current centroid to be the new origin. You can also move the origin by a fixed amount by defining y and z offsets. Note that, if you subsequently move that vertex, the origin for the section does not follow it. Likewise, if the shear center or centroid changes because of any changes to the section properties, the origin will not move with it. Specifying the y-axis You can specify the direction for the for the y-axis of the local coordinate system using vertices, the current principle axes, or at an angle offset from the current y axis. If you move a defi ning vertex, or the principle axes change, this coordinate system does not adjust with them. reverse x-axis Activate the check box to flip the section over, reflecting it about the y-axis.

Altair Engineering
Part Editor
Parts of thin-shell sections can be edited by selecting Part Editor... on the Tools menu and entering data in the Edit Parts dialog.
A part in this context is an individual piece of sheet metal that is typically welded to other parts along flanges. The part features that you need to control are its thickness and the connectivity of its vertices. When you use the part editor tools for, the currently selected part of the section is highlighted. You can use the up and down arrows to review any part. To set a new thickness, enter a value in the appropriate field. (You can also adjust thickness by using the graphic tools.) If you are currently in an optimization section, you can set upper and lower bounds for the optimization of the section's sheet metal thicknesses. The part editor also allows you to review and edit part vertex connectivities. There is list of the vertex IDs at the bottom of the list. You can add or remove vertices to change the part. To designate a segment between two vertices and a flange, include those vertices in more than one part. For example, in the section illustrated below, the segment between vertices 1 and 2 is a flange, so the connectivity of the top part is 1, 2, 3, 4, 5, and the connectivity of the bottom flange is 1, 2, 12, 13, 14, 15
Altair Engineering
Properties
Properties for beam cross-sections are specified by selecting Properties on the Tools menu and entering data in the Thin-Shell Section Properties dialog.
HyperBeam recognizes four types of beam cross-sections. The properties that can be specified differ for each type of section. See the HyperBeam panel for more information on beam cross-sections types. Thin Shell Section Properties The Thin Shell Section Properties dialog allows you to specify details pertaining to a single shell section. Torsion factor Warping Factor Line color Set the torsion factor. Set the warping factor. Choose the color to use for displaying the lines and vertices of the section in the graphics plane. You can activate this option if you need to specify optimization parameters for this section, such as upper and lower bound on thicknesses, or vertex coordinates, or equations tying coordinates together. This operation cannot be undone.
Optimization
Solid Section Properties
The Solid Section Properties dialog allows you to specify the line color of a solid section. Line color Choose the color to use for displaying the lines and vertices of the section in the graphics plane.
Standard Section Properties
The Standard Section Properties dialog allows you to specify details pertaining to a single standard section. On the Tools menu, select properties. Fill color Choose the color to use for displaying the material portion of the section in the graphics pane. Specify the shape out of the available choices to use for the standard section.
Section type

Altair Engineering
Generic Section Properties
The Generic Section Properties dialog allows you to specify the line color of a generic section. Line color Choose the color to use for displaying the lines and vertices of the section in the graphics plane.
Altair Engineering
HyperBeam Toolbar
The toolbar allows you to quickly access some of the more commonly used functions.
View Controls
The view controls are available on the View menu and the toolbar. They control how the section is displayed in the graphics pane and the results/spreadsheet pane. Circle zoom Zoom in Zoom out Pan Fit Show/hide Ids Update results Show/hide spreadsheet Properties Zoom in on area of the beam section by using the mouse to draw a circle around the area of interest. Enlarge the view in the graphics pane while maintaining the same center. Zoom out on the view in the graphics pane while maintaining the same center. Specify a new center for the graphics display. Resize the display to fit the pane. Turn on and off the display of vertex IDs in shell sections. Bring the section results up to date, if you have turned off the auto-update of section results. Alternate between displaying results or the spreadsheet. Pops-up the properties dialog
Shell Section Editing Tools

There are five tools to modify the basic definition of a shell section: Break segment If you want to add a new vertex between two existing vertices, activate this tool and click at approximately the place you want it to appear. If you want to delete a vertex, activate this tool and click on the vertex. To add a new sheet metal part to the current section, activate this tool and then click in the graphics area the sequence of vertices. To finish the part, double-click the last vertex, or deactivate the tool by toggling its button on the toolbar. You can use any mixture of existing or new vertices in creating the part.
Join two segments/ eliminate vertex Create a new part

Altair Engineering
Move vertex Part-editor
To reposition a vertex, activate this tool, and click and hold on the vertex to move and drag it to its new location. Allows you to rearrange parts in a section, rearrange vertices in a part, or add or remove vertices from a part's definition.
General Tools
There are eight tools that allow you to manage a HyperBeam session: Save Undo Redo Cut Copy Paste Print On-line Help Save the session. Undo the last action performed. Redo the last action performed. Cut an item and hold it in memory for pasting. Copy an item. Paste a copied or cut item. Open the print dialog. Open the HyperBeam on-line help.
Status Bar
The HyperBeam status bar displays messages and information about the interface. If you place the cursor over a toolbar icon, a short description of the action performed when you click the icon is displayed in the status bar.
Altair Engineering
Beam Cross Section Property Solver

The beam cross section property solver allows you to define a beam cross section, calculate its properties, and apply those properties to a HyperMesh model. This process is performed in the beam xsect panel. The properties that HyperMesh calculates include cross sectional area, center of gravity, principal axes, moments of inertia, shear center, and torsion and warping constants. The tools on the beam xsect panel can help you complete the necessary property cards for finite element analysis using HyperMesh bar2 elements. The panel functions also facilitate the creation of bar2 elements. HyperMesh uses a finite element methodology to calculate the properties for the cross section. Note: For design reasons, the beam cross section functions favor NASTRAN analysis in nomenclature and bar offset calculations.

Altair Engineering
Describing Cross Section Planes, Axes, and Elements

The following factors relating to the cross section plane, the coordinate system, and the element order can be defined in the beam xsect panel. Planes In order for properties to be calculated correctly, the cross section must be planar. HyperMesh uses one of two methods to define the plane. If you use the default method, HyperMesh calculates the plane for you; in this case, the plane is determined by a "best fit" from the data provided. Linear weighting of the points on the selected lines, surfaces, or elements is used. You may specify any existing HyperMesh node as the base point of the plane, or have it calculated for you. If you do not specify a base point, HyperMesh defines the plane base at the Center of Gravity of the cross section. If you define the base point by picking a node, this node can be referenced as an end of a bar2 element created with the panel. If you create the bar2 element by using this method, offset values are calculated for you, using NASTRAN conventions. These specifications are applied by using the toggles under cross section plane: or plane base node:. You can also use the standard HyperMesh plane collector to define the plane. All properties are calculated on the plane. Local Axes Many of the properties are defined relative to a local coordinate system. The system is the same as the coordinate system for the plane. If HyperMesh calculates the plane, the Y- and Z-axes are defined to be the principal axes of the cross section. If you define the plane, your N1 and N2 selections are used to define the positive Y-axis, and the Z-axis is the cross product of the X and Y axis. These options are specified by using the toggle under plane base node:. In all cases the planar normal is defined as the positive X axis. 1 versus 2 Order Element Analysis
st nd
For beam cross sections that were fully defined by lines or surfaces, you may choose to have the properties calculated using first or second order elements. If you are using offset sections, second order elements are always used. When you pick elements, the order of the selected HyperMesh element is used. This option is specified by using the toggle under analysis type: on the pick geom sub-panel. The save elements option allows you to save the elements defining the cross section as part of the HyperMesh model. These elements are placed in a newly created component for each calculation. The name of the component is preceded by a caret (^). This tells HyperMesh to ignore the contents of the component when exporting a model. Unless you change the name of the component, these elements are not output when you use the export subpanel on the files panel. The save element option is located on the pick geom sub-panel on the beam xsect panel. If you use the offset lines sub-panel, secondary panels called define offset parameters are opened. Note: The save element option has no effect when you define sections by elements.
Save Elements
Altair Engineering
Defining a Cross Section

There are two methods you can use to describe a cross-section for analysis: by offsetting HyperMesh lines or by selecting a fully enclosed area. With either method, the section must be a contiguous area. Holes are allowed in the section but all portions of it must touch all other portions. Note: If you define a cross section with elements and use the intersect panel to cut elements, use the combine lines option and specify a break angle. Although you can use the line segments option, it is best to use fewer lines with the property calculator.
Offset Sections
The offset sections method is designed to support thin-walled cross sections manufactured from sheet metal. The beam cross section is described by a set of lines, thicknesses, and weld points. When this method is used in the offset lines sub-panel of the beam xsect panel, an offset of each line is created. The offset direction is user-specified, based upon the line data in the model. By default, the offset direction is centered, with the line as the center of the sheet metal piece. Each HyperMesh line in the set can be assigned a thickness. The initial definition of the cross section uses the user-defined nominal thickness for each line. After nominal = for initial thickness is defined, you can define any or all line thicknesses using the thickness = option. Any continuous set of HyperMesh lines (as determined by HyperMesh) is considered to be a single piece of sheet metal. After the initial cross section is defined, you may change any or all of the line thicknesses. The thickness used is considered to be the total thickness of the sheet metal piece. You can change the thickness of lines interactively by using the mouse cursor or you can enter a value and apply it to specific lines or all of the lines. You can also change the offset direction after the initial cross section definition. The choices are centered, normal to the line, or reverse normal to the line. The line sets may be changed one at a time by selecting the graphical toggle and picking the line set or all sets may be changed at once by clicking the toggle sides button. An arrow is displayed that indicates the offset direction. When you use this method, you can also specify weld points for the cross section. Weld points are used to join separate pieces of sheet metal at a point. Any number of lines may be selected to be part of a weld point, provided they are used in the definition of the cross section. The weld point is located a given distance from a fixed point; HyperMesh allows this point to be chosen at any end or joint of a selected line. The distance from the point and the diameter of the weld may be changed graphically, or by entering the desired values. When you define a weld point, HyperMesh attempts to join four nodes per line per weld to a corresponding set of four nodes on another line. HyperMesh first looks for coincident node pairs to join. Then it looks for nodes within tolerance of each other. The tolerance is defined as 15% of the largest distance between the weld areas on the lines minus the offset distances. If weld points are not defined for offset sections, the section is considered fully open and no correlation will exist between nodes on different sets of lines.

Altair Engineering
Fully Defined Sections

For this method of beam cross section definition, you can use the pick geom sub-panel of the beam xsect panel to select any set of elements, lines, or surfaces that describe a fully closed area. If the section is defined using elements, those elements are considered to be the section. No alterations are made to those elements, aside from projecting to a common plane. When lines or surfaces are chosen, the area is automeshed to generate elements for the cross section. Defining the section using lines or surfaces in this manner creates a fully closed section. If you select by elements, HyperMesh uses the connectivity provided by the elements. Note: This means that all nodes along common boundaries are taken as the same and the solver does not consider moving them independently.
Altair Engineering
Post-Processing of Beam Cross Sections: Applying Calculated Properties

After you select the solve function in the beam xsect panel, the properties are calculated. The following symbols are displayed at the Center of Gravity and the Shear Center:
Center of Gravity symbol
Shear Center symbol
The local axes of the beam are also displayed. Temporary nodes are also created at the Center of Gravity and Shear Center. The post-processing panel is displayed, with which you can apply the calculated properties to the HyperMesh model. The post-processing panel displays only the menu items necessary for the current operation. At any time you can click apply results to perform all the currently specified options. Otherwise, individual menu items are displayed that perform only the sub-set of desired operations. The following postprocessing options can be performed in any combination desired and are not exclusive of other functions.

Altair Engineering
Defining a Prop/Comp Card for a Solver

In order to relate the calculated properties to a card for your desired output solver, use the FEA solver: switch to select the solver. If you already have a card image template specified in the global panel, that solver is automatically selected. Otherwise, you may select NASTRAN, OPTISTRUCT, ABAQUS, ANSYS, LS-DYNA, RADIOSS, MARC, or PAM-CRASH. After you select the solver, you can specify the already created HyperMesh properties or components to which to apply the results as a card image. This function does not work for dictionary solvers. For more information, see Creating Collectors. When you apply the results to the properties or components, HyperMesh checks to see if data already exists for the currently chosen solver on that property/component. If data exists, you are prompted to confirm that you wish to overwrite the data on that property/component. All of the solver data of the property/component is deleted if you answer yes, and replaced by the newly calculated data or default data for that property/component. HyperMesh material data associated with the property/component is not affected. Solver NASTRAN/ OPTISTRUCT NASTRAN/ OPTISTRUCT ABAQUS Comp/Prop Property Property Component Card Name PBAR PBEAM (end A) BEAMGENERAL, CENTROID, SHEAR CENTER R SECTION_BEAM, elform 2 Matl type 202 geometry Data A, I1, I2, I12, J, K1, K2 A, I1, I2, I12, J, K1, K2, CW, N1, N2 A, I1, I2, I22, J, w, Centroid x1 and x2, Shear Center x1 and x2 Area, Izz, Iyy A, Iss, Itt, Irr, SA A, As, Is, It, Ist, Ir A, Izz, Iyy, principal Y axis unit VECTOR
ANSYS LS-DYNA/ RADIOSS PAM-CRASH MARC
Property Property Component Component
Torsion and Warping Factors

torsion factors and warping factors are the only fields common to all operations of the postprocessing panel. These constants provide a means to apply empirical "fudge factors" to the results. These factors, independently developed over many years, relate fully welded sections to partially welded sections, and the spacing between welds. If these factors remain at the default value of 1.0, no changes are made to the calculated value. A non unit Torsion factor will modify the value of the Torsional Constant, J. Similarly non 1.0 warping factor modifies the Warping Constant. The changes are applied to all HyperMesh properties and/or components. The values that are saved in summary files or displayed on the screen show the factor, the original value, and the modified value. For more information, see Save and Display Results.
Display Size
You can control the size of the Center of Gravity and Shear Center symbols and the local Coordinate system with the draw size = field. The size determination is for user-viewing preference only and does not affect any of the actual values.
Altair Engineering
Creating a Bar Element

Another option is to create a HyperMesh BAR2 element by specifying two nodes and optionally choosing a direction vector or node and property for the element. The cross section may be chosen as either end A or end B of the bar. The node for this end of the bar is either the centroid of the section or the user-selected base node. The other end of the bar may be defined by picking a node or specifying a distance along the x axis of the cross section. The sign of the distance is the direction along the x axis. The element is created in the currently active component. Note: If you create a BAR2 element and it does not show on the screen, use the disp (display) panel to confirm that the elements of the current component are selected for display.
If any properties (not components) are selected when you build a BAR2 element, you are asked if you want each property associated with the newly created bar element. You are asked about each selected property until you answer "yes" to the question presented. If only one property is selected, that property is automatically assigned to the new BAR2 element. If the solver for which you are defining a model uses components, check to make sure the desired component is currently active, or move the bar element to that component by using the organize panel. The BAR2 element that you are creating can also be assigned an orientation. You may use the cross sections local Y or Z axis, either as a vector or by letting HyperMesh create a node along the axis, to describe the bars orientation. If you use a vector orientation, it applies a global unit vector to the bar created. If you use a nodal orientation, it creates a new node, 10% of the length of the element away from the existing node, that is referenced by the bar element.
Coordinate Systems/Vectors
A HyperMesh coordinate system may be created to save the orientation of the cross section. The system is created identical to the one displayed on the screen. You may also create a HyperMesh vector in either the local Y or Z direction of the cross section. This option is provided to aid in understanding the orientation of the cross section relative to the overall model. Manipulating them does not change the property values that may be saved and referenced by the created bar element.
Save and Display Results

All of the calculated properties may be viewed or saved to an ASCII text file. There are many properties calculated that are not assigned to solver cards. If you want to save these, you can select the summary file option and specify a file name in the field after summary file. The properties can also be viewed on the screen in the same manner as summary templates. If you want a permanent record of the calculations you have just performed, you must save the results as an ASCII file. Whether you choose to save a summary file and/or display it on the screen, the information includes a named list of the properties/components, if any, to which the calculated properties were assigned. This feature works only with apply results, and not with summary alone.

Altair Engineering
Beam Cross Section Questions and Answers

This section provides answers for common questions about using the beam cross section process: How do I change the number of lines on which I can define a thickness? Change the number of HyperMesh lines you are selecting. Use the line edit panel on the Geom page to either split or combine existing lines. Each HyperMesh line has a different thickness. How do I define a weld point at a different location? Use the graphical controls to change its location on the line. If you need a different reference point, split the HyperMesh line at the desired point and then choose the new point at the split. How do I obtain lines from a shell element model to use as my offset lines? Use the hidden line panel on the Post page and choose line plot as the desired output. Select those lines as your section definition.
Altair Engineering
HyperLaminate Module
HyperLaminate is a HyperMesh module that facilitates the creation, review and edition of composite laminates. In support of this process certain materials and design variables are also supported by in the HyperLaminate module. The current HyperMesh database is only updated with information from the current HyperLaminate session on exit from HyperLaminate (an exception to this rule are Abaqus materials, which are updated simultaneously in HyperMesh and HyperLaminate), so while it is possible to work in HyperMesh while HyperLaminate is running, this is not advisable. Any changes made to those entities which HyperLaminate touches (materials, component collectors and design variables) may result in synchronization problems and loss of data. HyperLaminate is launched from within HyperMesh either from the HyperLaminate button on the 2D page of the main menu, or by selecting HyperLaminate from the Setup pull-down menu. The HyperLaminate module is supported for the OptiStruct, Nastran, Ansys and Abaqus user profiles.

Altair Engineering
HyperLaminate Environment
The HyperLaminate environment consists of five general areas, as shown here:
Menus
The HyperLaminate menu bar contains five menus that allow you to manage files, edit materials, laminates and design variables, change views, and access on-line help. The HyperLaminate toolbar contains five tools that allow you to generate new materials, laminates or design variables, and to cut, copy, paste, and delete entries in text boxes. This browser, located on the left side of the HyperLaminate window, provides a vertical tree view of materials, laminates and size design variables in your model. Left clicking on an entity populates the Define/Edit and Review panes with details of that branch. Right clicking on a branch offers context sensitive operations for that branch.
Toolbar
Laminate Browser
Define/Edit Pane
This is the central pane of the HyperLaminate module. Here users may enter or change data related to a material, laminate or design variable definition (depending on the selected branch in the laminate browser). This is the right hand pane of the HyperLaminate module. The review pane has a number of tabs that display the current state of the selected branch.
Review Pane
Altair Engineering
HyperLaminate Menus
The HyperLaminate menu bar contains five menus.
The following chart lists each menu option. File New Export to File Exit Generates a new entity, depending on the selected sub-topic in the Laminate Browser. Exports material and laminate information to a text file. This text file can be printed. Exit HyperLaminate. At this point the current HyperMesh database is updated with the information in the current HyperLaminate session. Edit Cut Removes the selected data from an entry field and places it on the clipboard for pasting. Can also remove rows from a ply lay-up order table and place these on the clipboard for pasting. Copy Places selected data from an entry field on the clipboard for pasting. Can also place rows from a ply lay-up order table on the clipboard for pasting. Paste Pastes data from the clipboard in selected entry fields. Can also paste rows from the clipboard above selected rows on a ply lay-up order table. Delete When the cursor is active in the Laminate Browser, this deletes the selected entity from the Laminate Browser. (a dialogue is displayed to confirm the deletion). When the cursor is active in the Define/Edit pane, this deletes the selected text from a text box or the selected rows from a ply lay-up order table.

Altair Engineering
Tools
Ply lay-up options
Displays the Ply lay-up Options dialog.
Allows you to select defaults for new Laminates for: View Toolbar Status Bar Help About HyperLaminate Help Topics color convention repetitions ply thickness common thickness
Display/hide toolbar. Display/hide status bar. Displays version, contact, and copyright information. Activates the HyperLaminate on-line help.
Altair Engineering
HyperLaminate Toolbar
The HyperLaminate toolbar is located below the menu bar and its display is controlled by the Toolbar option under the View pull-down menu. The toolbar is shown and described here.
Icon
Name New
Function Generates a new entity, depending on the selected sub-topic in the Laminate Browser. Removes the selected data from an entry field and places it on the clipboard for pasting. Can also remove rows from a ply lay-up order table and place these on the clipboard for pasting.
Cut
Copy
Places selected data from an entry field on the clipboard for pasting. Can also place rows from a ply lay-up order table on the clipboard for pasting.
Paste
Pastes data from the clipboard in selected entry fields. Can also paste rows from the clipboard above selected rows on a ply lay-up order table.
Delete
When the cursor is active in the Laminate Browser, this deletes the selected entity from the Laminate Browser. (a dialogue is displayed to confirm the deletion). When the cursor is active in the Define/Edit pane, this deletes the selected text from a text box or the selected rows from a ply lay-up order table.

Altair Engineering
Laminate Browser
The Laminate browser, located on the left side of the HyperLaminate window, provides a vertical tree view of the materials, and laminates in your model. For the OptiStruct and Nastran user profiles the browser also includes size design variables. On launching HyperLaminate, the Laminate Browser is populated with all the relevant materials, laminate definitions and size design variables existing in the HyperMesh database, for the active user profile. The data is presented in a slightly different format for the various user profiles as shown here:
OptiStruct & Nastran
Ansys
Abaqus
The Laminate Browser is organized in a three level hierarchy: 1. 2. At the highest level are the entity types: Materials, Laminates and Design Variables. At the intermediate level are the entity subtypes or card images. These are: a. for OptiStruct and Nastran: i. Materials: MAT1, MAT2 and MAT8 ii. Laminates: PCOMP and PCOMPG iii. Design Variables: DESVAR b. for Ansys: i. Materials: MATERIAL and MPDATA ii. Laminates: SHELL91, SHELL99, SOLID46 and SOLID 191 c. for Abaqus: i. Materials: ABAQUS_MATERIAL ii. Laminates: SOLIDSECTION, SHELLSECTION and SHELLGENERALSECTION
Altair Engineering
3.
At the lowest level are the entities, displayed with the names as defined by you.
Left or right clicking on a branch in the browser selects that branch and it becomes highlighted. When an entity (lowest level branch in the tree hierarchy) is selected, the Define/Edit and Review panes are populated with details of that entity. It is then possible to alter and update the entity definition. Right clicking on an already selected (highlighted) branch offers context sensitive operations for that branch. At the highest level (entity types) no operations are available. At the intermediate level (entity sub-types) only one operation is available: New which will create a new entity of the selected sub-type. i.e. if MAT1 is selected and we right click on it and choose New; a new MAT1 entity is created. At the lowest level (entities) three operations are available; Rename - which allows the entity to be renamed; Duplicate which creates a copy of the selected entity; and Delete which will delete the selected entity.
From the Laminate Browser it is possible to: To create entities: There are three options for creating new entities in HyperLaminate: 1. 2. 3. Select an intermediate level branch (an entity sub-type or card image) of the browser tree. Right click on selected entity sub-type. A context sensitive menu appears with one option: New. Click New. A new entity appears under the selected branch. Or 1. 2. Select an intermediate level branch (an entity sub-type or card image) of the browser tree. Select New from the File pull-down menu. A new entity appears under the selected branch. Or 1. 2. Select an intermediate level branch (an entity sub-type or card image) of the browser tree. Click the New icon, , on the toolbar. A new entity appears under the selected branch
A default name and id are assigned to each newly created entity. To review and update entities: 1. Right or Left click on an entity (lowest level in tree hierarchy) in the Laminate Browser tree to select it. The selected entity is highlighted. The Define/Edit and Review panes are populated with details of that entity. 2. Make the desired changes to the entity definition in the Define/Edit pane and click apply or update laminate to update the entity.

Altair Engineering
To rename entities: 1. 2. 3. 4. Right or Left click on an entity (lowest level in tree hierarchy) in the Laminate Browser tree to select it. Right click on the selected entity. A context sensitive menu appears with three options: Rename, Duplicate, and Delete. Click Rename. The name of the selected entity, in the Laminate Browser, switches to a text box. Enter the desired new name in the text box. You can also rename an entity by altering the relevant field in the Define/Edit pane and then clicking on Apply or Update Laminate. To duplicate entities: 1. 2. 3. Right or Left click on an entity (lowest level in tree hierarchy) in the Laminate Browser tree to select it. Right click on selected entity. A context sensitive menu appears with three options: Rename, Duplicate, and Delete. Click Duplicate. A duplicate of the entity is created and appears in the Laminate Browser.
To delete entities: There are three options for deleting entities in HyperLaminate: 1. 2. 3. 4. Right or Left click on an entity (lowest level in tree hierarchy) in the Laminate Browser tree to select it. Right click on the selected entity. A context sensitive menu appears with three options: Rename, Duplicate, and Delete. Click Delete. A confirmation dialog is displayed. Click Yes. The entity is deleted and disappears from the Laminate Browser. Or 5. 6. 7. Right or Left click on an entity (lowest level in tree hierarchy) in the Laminate Browser tree to select it. Select Delete from the Edit pull-down menu. A confirmation dialog is displayed. Click Yes. The entity is deleted and disappears from the Laminate Browser. Or
Altair Engineering
8. 9.
Right or Left click on an entity (lowest level in tree hierarchy) in the Laminate Browser tree to select it. Click the Delete icon, , on the toolbar. A confirmation dialog is displayed.
10. Click Yes. The entity is deleted and disappears from the Laminate Browser. Note: Abaqus materials that are created but not defined (they appear in a red font in Laminate Browser) may not be deleted, as they do not really exist. To delete these undefined materials, either complete their definition (by clicking Edit which takes you to the HyperMesh material card previewer) or exit and restart HyperLaminate (in which case the undefined materials are purged).

Altair Engineering
Define/Edit Pane
The Define/Edit Pane, the central pane of the HyperLaminate window, allows you to edit the definition of the selected entity. On selecting an entity in the Laminate Browser the Define/Edit pane is populated with the current definitions. The configuration of the Define/Edit pane differs for different user profiles and sub-types (card images). Materials For OptiStruct, Nastran and Ansys materials, all material property information for the selected material may be edited in the Define/Edit pane. Once the desired changes have been made, clicking Apply will save those changes for the current HyperLaminate session (it is important to remember that the HyperMesh database is only updated on exit from HyperLaminate). To reset all material property fields to zero you can click the Clear button. Below are screenshots showing the Define/Edit pane for an OptiStruct MAT8 definition and an Ansys MATERIAL definition:
OptiStruct Materials MAT8
Ansys Materials MATERIAL
Altair Engineering
For Abaqus materials users may rename or redefine the color of the material in the Define/Edit pane, but to fully define the material properties they must click the Edit button. Clicking the Edit button takes you to the material card previewer in the HyperMesh GUI, where you can review and alter the definition of the selected material. Once you has finished reviewing/editing the material, clicking return will return you to the HyperLaminate GUI. As with the other user profiles, to reset all material property fields to zero you can click the Clear button. A screenshot of the Define/Edit pane for an Abaqus material is shown here:
Abaqus Materials ABAQUS_MATERIAL Laminates For Laminates, the Define/Edit pane allows the laminate name, HyperMesh component color, stacking sequence convention and the ply lay-up order to be edited. This is for all supported user profiles and laminate sub-types. A screenshot of the Define/Edit pane for an Abaqus SOLIDSECTION laminate is shown here:
Abaqus Laminates SOLIDSECTION 314 HyperMesh 8.0 Users Guide

Altair Engineering
There are a number of options for Convention for the stacking sequence: a. b. Total: The Ply lay-up order table describes the laminate in its entirety. Symmetric: The Ply lay-up order table describes the bottom half of the laminate. The top half of the laminate is the mirror image of the bottom half. The ply angles used for the top half are the same as the ply angles used in the bottom half. Antisymmetric: The Ply lay-up order table describes the bottom half of the laminate. The top half of the laminate is the mirror image of the bottom half. The ply angles used for the top half have the opposite sign to the ply angles used in the bottom half (but 0, 90, 180, 270 and 360 remain as 0, 90, 180, 270 and 360 respectively). Symmetric-Midlayer: The Ply lay-up order table describes the bottom half of the laminate and a midlayer (or core). The midlayer is the last ply defined in the table. The top half of the laminate is the mirror image of the bottom half. The midlayer is not reflected. The ply angles used for the top half are the same as the ply angles used in the bottom half. Due to the midlayer, the total number of plies is always odd. Antisymmetric-Midlayer: The Ply lay-up order table describes the bottom half of the laminate and a midlayer (or core). The midlayer is the last ply defined in the table. The top half of the laminate is the mirror image of the bottom half. The midlayer is not reflected. The ply angles used for the top half have the opposite sign to the ply angles used in the bottom half (but 0, 90, 180, 270 and 360 remain as 0, 90, 180, 270 and 360 respectively). Due to the midlayer, the total number of plies is always odd. Repeat: The Ply lay-up order table describes a single sub-laminate which is repeated a number of times. The number of repetitions is given by the Repetitions: field (which is activated when this Convention is chosen).
c.
d.
e.
f.
It is possible to choose between constant and variable ply thickness for certain user profiles; variable ply thickness allows up to 4 nodal thicknesses to be defined for each ply. A screenshot of the Define/Edit pane for an Ansys SHELL99 laminate with variable ply thickness is shown here:
Ansys Laminates SHELL99 Altair Engineering

It is also possible to choose a common thickness for all plies; common thickness gives every ply in the laminate the same thickness. The Ply lay-up order table describes the laminate from the bottom ply (most negative Z) moving upwards (increasing in positive Z direction). Each row of the table defines the material, ply thickness and ply orientation for a number of plies (defined by the No. or repetitions field and based on the selected Convention). Rows are added to the table by completing the Add/Update plies: entry fields and clicking the Add New Ply button. Rows may be inserted in the table, either above or below selected rows (choose from the Above Selected or Below Selected radio buttons), by clicking the Insert New Ply button. Rows may be cut, copied, pasted or deleted to/from the table, using the toolbar, pull-down Edit menu or Ctrl+x, Ctrl+c, Ctrl+v and Ctrl+d respectively. Select multiple rows by selecting one row and then, with the Ctrl key held down, select other rows (alternatively multiple rows may be selected with the Shift key held down; this will keep the current selection and add all the rows between the current selection and the newly selected row). Rows are always pasted above the selected rows, when multiple rows are selected the clipboard contents are pasted above each selected row. All fields in the Ply lay-up order table may be edited. It is also possible to edit multiple rows at once. Select multiple rows as described in the previous paragraph. When multiple rows are selected, the Add/Update plies: fields are populated with the information common to the selected rows. Blank fields indicate that not all of the selected rows contain the same values for that field. Changes can be made to the Add/Update plies: fields and Update Selection can be clicked to update the selected rows with the updated information (no changes occur to the selected rows for blank fields). For the OptiStruct and Nastran user profiles it is possible to request stress and failure theory output. Each row of the Ply lay-up order table has an SOUT field, which when set to YES includes the plies described by that row in the stress output and the failure theory calculation. It is possible to set the SOUT field individually for each row, or for all rows at once through the Output ply stress results: field under the Stress and failure theory output: heading. Once one or more SOUT fields are set to YES it is possible to activate failure theory calculation, by checking the Failure Theory check-box, selecting a theory from the pull-down list and defining an Interlaminar shear allowable: value. A screenshot of the Define/Edit pane for an OptiStruct PCOMPG laminate is shown below:
OptiStruct Laminates PCOMPG 316 HyperMesh 8.0 Users Guide

Altair Engineering
The Ply lay-up order table for the OptiStruct and Nastran PCOMPG laminate sub-type is different from other laminate subtypes in that it has a GPLYID field. This field is used to assign a global ply id to a ply definition (the global ply id is a post-processing aid). As this id should not be repeated within the same laminate, the No. of repetitions field is not available for PCOMPG. For PCOMPG each row in the Ply lay-up order table should represent a single ply so only the Total stacking convention should be used for PCOMPG, but this is not enforced in the GUI. For the OptiStruct and Nastran user profiles it is possible to assign a design variable to a thickness or orientation field in the Ply lay-up order table. Checking the Optimization check-box expands the Ply 0 lay-up order table, adding extra fields to the right of the Thickness T1 and Orientation fields. Design variables may be selected in these extra fields. Selecting a design variable to the right of a thickness or orientation assigns the selected design variable to that thickness or orientation. Click Update Laminate to apply all the changes for the current HyperLaminate session (it is important to remember that the HyperMesh database is only updated on exit from HyperLaminate). Design Variables For the OptiStruct and Nastran user profiles the DESVAR design variable card is supported in HyperLaminate. All information for the selected design variable may be edited in the Define/Edit pane. Once the desired changes have been made, clicking Apply will save those changes for the current HyperLaminate session (it is important to remember that the HyperMesh database is only updated on exit from HyperLaminate). To reset all design variable fields to their default values, you can click the Clear button. To define a new material: 1. Use one of the following three methods to create a new material in HyperLaminate: a) Select a sub-type under the material branch of the Laminate browser. b) Right click on selected material sub-type. A context sensitive menu appears with one option: New. c) Click New. A new material appears under the selected branch. Or a) Select a sub-type under the material branch of the Laminate browser. b) Select New from the File pull-down menu. A new material appears under the selected branch. Or a) Select a sub-type under the material branch of the Laminate browser. b) Click the new icon, , on the toolbar.
A new material appears under the selected branch. A default name and id are assigned to newly created materials. 2. The newly created material is automatically selected in the Laminate browser and the Define/Edit pane takes on the appropriate configuration for the selected material sub-type.
Altair Engineering
For the OptiStruct, Nastran and Ansys user profiles: 1. If desired a new name for the material may be entered in the Material: field or the material color may be altered by clicking on the color swatch and selecting a new color from the pop-up color palette. Provide the material definition by filling in the entry fields in the Define/Edit pane. Click Apply to save the changes for the current HyperLaminate session (It is important to remember that the HyperMesh database is only updated on exit from HyperLaminate).
2. 3.
For the Abaqus user profile: 1. 2. 3. 4. Click on Edit and provide the material definition in the HyperMesh card previewer. Click return. This returns you to the HyperLaminate GUI. If desired a new name for the material may be entered in the Material: field or the material color may be altered by clicking on the color swatch and selecting a new color from the pop-up color palette. Click Apply to save the changes. Note: It is not possible to rename an Abaqus material until after it has been defined (edited). Also it is not possible to create a new Abaqus material if an undefined material definition already exists (appears in a red font in Laminate Browser).
5.
To review or modify an existing material: 1. Select the material to be edited from the Laminate Browser. The Define/Edit and Review panes are populated with the selected material definition. For the OptiStruct, Nastran and Ansys user profiles: 1. Edit the data fields in the Define/Edit pane. Data may be cut, copied, pasted or deleted to/from the data fields, using the toolbar, pull-down Edit menu or Ctrl+x, Ctrl+c, Ctrl+v and Ctrl+d respectively. Clicking Clear will reset all fields to zero. Each change is reflected in the Review pane. 2. If desired a new name for the material may be entered in the Material: field or the material color may be altered by clicking on the color swatch and selecting a new color from the pop-up color palette. Click Apply to save the changes for the current HyperLaminate session (It is important to remember that the HyperMesh database is only updated on exit from HyperLaminate). The final material definition is displayed in the Review tab.
3.

Altair Engineering
For the Abaqus user profile: 1. 2. 3. 4. 5. Click on Edit to see the material definition in the HyperMesh card previewer. Make all desired changes to the material definition in the card previewer. Click return. This returns you to the HyperLaminate GUI. If desired a new name for the material may be entered in the Material: field or the material color may be altered by clicking on the color swatch and selecting a new color from the pop-up color palette. Click Apply to save the changes.
6.
To define a new laminate: 1. Use one of the following three methods to create a new laminate in HyperLaminate: a) Select a sub-type under the laminates branch of the Laminate Browser. b) Right click on the selected sub-type. A context sensitive menu appears with one option: New. c) Click New. A new laminate appears under the selected branch. Or a) Select a sub-type under the laminates branch of the Laminate browser. b) Select New from the File pull-down menu. A new laminate appears under the selected branch. Or a) Select a sub-type under the laminates branch of the Laminate browser. b) Click the new icon, , on the toolbar.
A new laminate appears under the selected branch. A default name and id are assigned to newly created laminates. 2. 3. The newly created laminate is automatically selected in the Laminate browser and the Define/Edit pane takes on the appropriate configuration for the selected laminate sub-type. If desired a new name for the laminate may be entered in the Laminate name: field or the component color may be altered by clicking on the color swatch and selecting a new color from the pop-up color palette. For OptiStruct and Nastran user profiles define the Stress and failure theory output: information as desired.
4.
Altair Engineering
5.
For all user profiles define the Stacking sequence convention: information. a) For Convention:, select one of the following stacking sequence conventions. Total Symmetric Antisymmetric Symmetric-Midlayer Antisymmetric-Midlayer Repeat If you select Repeat, specify how many times you want to repeat the entire block of entry rows. b) For Ply thickness:, select Constant or Variable. Note: The option to switch between constant or variable thickness is only available for certain laminate sub-types.
If Constant is selected, the Ply lay-up order table includes a single thickness column: Thickness T1 If Variable is selected, the Ply lay-up order table includes multiple thickness columns: Thickness Thickness Thickness Thickness T1 T2 T3 T4
c) For Constant ply thickness, you can check the Common Thickness box and specify a thickness to be used by all the entry rows. Having checked the Common Thickness box and entered a common thickness value, if you now uncheck the box, the thickness fields retain the common thickness value, but are now editable. 6. Complete the Ply lay-up order table. Add/Insert rows by completing the Add/Update plies: fields and clicking Add New Ply or Insert New Ply (for Insert New Ply it is possible to choose to insert the ply above or below the selected rows). Note: 7. 8. The number of rows in the table is not the number of plies. This is governed by the stacking convention and the number of repetitions.
Data may be cut, copied, pasted or deleted to/from selected fields, using the toolbar, pull-down Edit menu or Ctrl+x, Ctrl+c, Ctrl+v and Ctrl+d respectively. Table rows may also be cut, copied, pasted or deleted, using the toolbar, pull-down Edit menu or Ctrl+x, Ctrl+c, Ctrl+v and Ctrl+d respectively. Note: Note: Rows are always pasted above selected rows. When multiple non-sequential rows are copied and then pasted, they will be pasted as sequential rows. Eg. If rows 1 and 3 are copied and pasted at row 7, row 1 will be pasted as row 7, row 3 will be pasted as row 8, and what was row 7 will now be row 9.
9.
For the OptiStruct and Nastran user profiles it is possible to define thickness and orientation fields in the Ply lay-up order table as designable and to assign design variables to them.
10. Click Update Laminate to save the changes for the current HyperLaminate session (It is important to remember that the HyperMesh database is only updated on exit from HyperLaminate).

Altair Engineering
To review and modify an existing laminate: 1. Select the laminate to be edited from the Laminate Browser. The Define/Edit and Review panes are populated with the selected laminate definition. 2. 3. The laminate definition may be modified in the Define/Edit pane in a manner similar to defining a new laminate. (See To define a new laminate). Click Update Laminate to save the changes for the current HyperLaminate session (It is important to remember that the HyperMesh database is only updated on exit from HyperLaminate).
To define a new design variable: Design variables are only supported for the OptiStruct and Nastran user profiles. 1. Use one of the following three methods to create a new design variable in HyperLaminate: a) Select a sub-type under the design variable branch of the Laminate Browser. (only subtype available is DESVAR). b) Right click on the selected sub-type. A context sensitive menu appears with one option: New. c) Click New. A new design varaible appears under the selected branch. Or a) Select a sub-type under the design variable branch of the Laminate browser. (only subtype available is DESVAR). b) Select New from the File pull-down menu. A new design variable appears under the selected branch. Or a) Select a sub-type under the design variable branch of the Laminate browser. (only subtype available is DESVAR). b) Click the new icon, , on the toolbar.
A new design variable appears under the selected branch. A default name and id are assigned to newly created design variables. 2. 3. 4. 5. 6. 7. The newly created design variable is automatically selected in the Laminate browser and the Define/Edit pane takes on the appropriate configuration. If desired a new name for the laminate may be entered in the Desvar: field. Initial, lower bound and upper bound values for the design variable can be entered in the appropriate data fields. Checking the Move limit box activates the Move limit field, where a move limit value other than the default of 0.5 may be entered. Checking the Ddval ID box activates the Ddval ID field, where the id of a discrete value list may be entered. Click Apply to save the changes for the current HyperLaminate session (It is important to remember that the HyperMesh database is only updated on exit from HyperLaminate).
Altair Engineering
To review and modify an existing design variable: 1. 2. Select the design variable to be edited from the Laminate Browser. The Define/Edit and Review panes are populated with the selected design variable definition. Edit the data fields in the Define/Edit pane. Data may be cut, copied, pasted or deleted to/from the data fields, using the toolbar, pull-down Edit menu or Ctrl+x, Ctrl+c, Ctrl+v and Ctrl+d respectively. Clicking Clear will reset all fields to their default values. Each change is reflected in the Review pane. 3. Click Apply to save the changes for the current HyperLaminate session (It is important to remember that the HyperMesh database is only updated on exit from HyperLaminate).
The final design variable definition is displayed in the Review tab.

Altair Engineering
Review Pane
The Review Pane, the right-hand pane of the HyperLaminate window, allows you to review the information pertaining to the selected entity. On selecting an entity in the Laminate Browser the Review pane is displays the current definition of that entity. Materials For OptiStruct, Nastran and Ansys materials, all material property information for the selected material is displayed in the Review pane. This information is updated as the definitions are altered in the Define/Edit pane. For Abaqus materials, no information is displayed in the Review pane. Laminates For laminate definitions for all user profiles, the review pane has two tabs; a Review tab and a Stiffness/Material Matrix tab. Information displayed on these tabs is only for the saved laminate definition, so this information is only updated when the Update Laminates button is clicked. The Review tab is headed by the laminate name, the total number of plies in the laminate and the total thickness of the laminate. This is followed by a description of the laminate, listing the plies in order from the bottom ply (most negative z), showing a graphical representation each plys orientation and listing the referenced material, thickness and orientation. The Stiffness/Material Matrix tab provides the two sets of matrices. The first set of matrices are the composite shell stiffness matrices, more commonly referred to as the ABD matrices. The second set of matrices are the equivalent material matrices, these are used by many finite element solvers to represent the laminated composite as a homogenized shell. Design Variables For OptiStruct and Nastran user profiles, information for the selected design variable is displayed in the Review pane. This information is updated as the definitions are altered in the Define/Edit pane.
Altair Engineering
Finite Difference Module

The Finite Difference module allows you to perform heat transfer, fluid flow, chemical reaction, and solidification processes by creating an orthogonal, three-dimensional, structured mesh in a cubic volume around your model. The panels in this module allow you to intersect your finite element shell model with a finite difference block, creating "dead cells." All of these dead cells are placed in walls, and a block may contain multiple walls of dead cells. After you create a finite difference block, you can export the grid, wall, and dead cell information as an analysis input deck by using the HyperMesh template system. Finite difference blocks are built performing the following steps:
Creating a Finite Difference Block

The first step in creating a finite difference block is to create the block, the outer boundary of the volume. If a finite element model is currently loaded, the block is created with a default size of ten percent larger than the model in each direction (the size of a model is determined by its nodes). Otherwise, the block is created with the default bounds of -10.0 and 110.0 in each direction. You can adjust the size of the block by using the functions on the FD blocks panel. Always finalize the size of your block before beginning the next phase. You cannot change the shape of the finite difference block after you create the structured mesh without destroying all the grid lines. Note: The color of a block may be modified at any time by using the update function on the FD blocks panel.
When the block is displayed, a small set of coordinate axes is displayed at the corner of the block. These axes serve as a reminder of the i, j, and k directions of the block. Cylindrical and spherical volumes are not supported in the current release.

Altair Engineering
Creating a Structured Mesh

After you create a block, you create a structured mesh in the block by creating grid lines in the i, j, and k directions. Grid lines are created in one direction at a time, based on whether i nodes, j nodes, or k nodes has been selected. After you create a mesh, you can verify the aspect ratio or expansion ratio limits, depending upon the restrictions enforced by the analysis code being used. See the FD nodes panel for more information.
Intersecting Elements with Cells

The intersection of grid lines in the i, j, and k directions creates a large number of small cubic volumes called cells. Initially, each cell within a block is live, meaning that the cell does not alter the flow being studied. Cells that alter the flow are known as dead cells. HyperMesh allows you to automatically intersect a finite element model with the cells in a finite difference block, which creates dead cells wherever a one- or two-dimensional element intersects any part of a cell. The intersection and modification of live and dead cells is done in the FD walls panel, which also contains all the functions you can use to manipulate walls. Solid elements are currently not supported in the interse ction operation. You must create a wall before you create dead cells. The wall functions are described below: create delete update delete all display Creates a new wall with the name and color specified in wall = and color. Deletes the specified wall. Asks for confirmation before proceeding. Updates the color of an existing wall. Deletes all existing walls. Asks for confirmation before proceeding. Displays a list of all walls in the block. You may then select which walls to display and turn off by using the left or right mouse button, respectively.
After you create a wall, all or part of the finite element model may be intersected with the cells in the finite difference block. A cell may exist in only one wall. To intersect the model with the cells, select the desired elements and click intersect. All the one-and two-dimensional elements selected are intersected with the cells in the current block. Cells that intersect an element are placed into the current wall, marked as dead, and displayed in the current wall color. Note: Before any wall operation is begun, the block must be selected by using the block = menu item.
Altair Engineering
Modifying Cells
Cells may be changed from live to dead or dead to live individually, by volumes, or by planes. The FD walls panel allows you to edit cells. Cells do not have a visible pick handle and must be selected at the corner closest to the origin of the block, where the block coordinate axes are located, and i, j, and k are at their minimum values. When cells are selected, they are highlighted. The edit cells function allows you to add individual cells to the current wall and mark them as dead, or remove cells from the current wall and mark the cells as live. After edit cells is selected, use the cursor to select the cells to add or remove. Click the left mouse button to add cells and the right mouse button to remove cells from a wall. If the block is displayed in planar mode, then only cells in the currently displayed plane(s) may be edited. Otherwise, you can edit any cell in the block.
Creating Finite Difference Hidden Line Plots

Hidden line plots of cells in a finite difference block are useful in the verification phase of a finite difference model. Because cells have no visible pick handle, it is easier to see which cells are dead, since only dead cells are plotted. When the entire block is plotted, all dead cells are displayed in the color of the wall to which they belong. However, if planar mode is used to display one or more of the planes of cells, the color menu items in the i, j, and k directions must be modified to provide the plotting color for cells in each plane. If you change the color of a plane, you must click hidden line again to display the new color. It is possible to step through the model, plane-by-plane, by using the next and prev menu functions.

Altair Engineering
Loads on Geometry
HyperMesh allows you to apply loads to geometrical entities and map them to the FE mesh using the load on geom panel on the Analysis Page. One advantage is that you can remesh a model without deleting complicated loads or boundary conditions. After remeshing, loads or boundary conditions that have been applied to geometrical entities can be remapped to the new mesh. You can apply loads to geometry by using the following panels on the Analysis Page: forces, moments, constraints, pressures, temperatures, flux, velocities, and accels. These are the same panels used to apply loads to a mesh. There are two ways to map loads on geometry to the mesh associated with this geometry (loads on mesh): Manually, using the load on geom panel. Automatically, by exporting the FE deck, using the files panel/export sub-panel. See Exporting Loads for more information.
The disp (display) panel allows separate or simultaneous visualization of loads on mesh and loads on geometry. To visualize loads on mesh and/or loads on geometry, from the display panel (accessed via the toolbar) select loadcols from the switch, and click the toggle to select elems or geoms. When elems is selected, you control the display of loads applied to elements. When geoms is selected, you control the display of loads applied to geometric entities. This means that you can control the display of both types of loads independently, and load collectors may contain one type or both types simultaneously. Use the none, all and reverse buttons to assist in selecting which loadcols should be displayed. Comments Loads on mesh and loads on geometry can be displayed together (similar to the simultaneous display of both elements and geometry belonging to a specific component). A geometrical entity can be associated with one mesh or multiple meshes (HyperMesh component or components) and/or with one load collector or multiple load collectors. One load collector stores both loads on geometry and loads on mesh. The mesh (or multiple meshes) is associated with the geometrical entities to which the loads on geometry have been applied. Each load type is stored in a dedicated section of the same load collector.
Altair Engineering
Terminology and Definitions

geometrical entities loads on geometry or geometry loads loads on mesh or mesh loads A point, a line, or a surface. Loads applied to geometrical entities. Loads applied to mesh (nodes or element). Loads can be applied directly to mesh or applied by mapping them from loads on geometry. The process of mapping geometrical loads to mesh loads. The loads are mapped from the geometrical entities (to which the geometrical loads are applied) to the mesh that is associated with the geometrical entities.
load mapping

Altair Engineering
Application of Loads to Geometry

You can apply loads to geometrical entities in a way similar to the manner in which loads are applied to mesh. The process includes two basic steps. 1. 2. Creating a load collector by using the collector panel. Applying loads to the geometry using one of the following panels on the Analysis Page: forces, moments, constraints, pressures, temperatures, flux, velocities, and accels.
To apply a load to a geometrical entity, first create a load collector in which the loads applied to geometrical entities will be stored. Next, access a HyperMesh load panel (e.g. forces, constraints, etc.) located on the Analysis Page, and choose the create sub-panel. Third, select a geometrical entity on which the loads will be applied (points, lines, or surfaces) using the panel selection box, define the load or boundary condition parameters in the same way you would for the application of the load or boundary condition on a FE mesh entity (e.g. node), and click create. HyperMesh stores the loads/boundary conditions in the database and displays them in the graphical window. The following chart specifies the geometrical entities to which loads can be applied, in each of the load application panels listed above. Panel accels constraints flux forces moments pressures Geometrical Entities points, lines and surfaces. points, lines and surfaces. points points points surfaces nodes on edge: lines (for 2-D solid elements) nodes on face: surfaces (for 3-D solid elements) points, lines and surfaces. points, lines and surfaces.
temperatures velocities Note:
Refer to the specific panel for detailed information about creating, reviewing, and updating loads and constraints.
Altair Engineering
Exporting Loads
HyperMesh sessions can contain loads on geometry, loads on mesh that have been applied directly to mesh, and loads on mesh that have been mapped from loads on geometry. When saving the model as a HyperMesh database, all load types are saved and are retrieved when you open the .hm file. When exporting the model using an export template, only the loads on mesh are exported. The loads on mesh that are exported may have been applied directly to mesh, mapped from geometry to mesh, or both. The all/displayed toggle on the export sub-panel on the file panel allows you to determine which loads are exported. If all is selected, all the loads on geometry that have not been mapped (if any), are mapped to loads on mesh and all the loads on mesh are exported. If displayed is selected, all the displayed loads on mesh are exported. All the loads on mesh (both displayed and hidden) that are associated with the displayed loads on geometry are exported as well. If any loads on geometry are displayed and have not been mapped, they will automatically be mapped to loads on mesh and exported as well.
Visualization of Loads on Geometry and Loads on Mesh

The disp (display) panel allows you to visualize loads on mesh and loads on geometry either individually or together by setting the collector type to loadcols and using the toggle between elems and geoms. elems controls the display of loads on mesh and geom controls the display of loads on geometry. A simultaneous display is similar to the display of both elements and geometry belonging to a specific component. Note: A major graphical display difference between loads on geometry and loads on mesh is the density of the arrows. Multiple arrows represent loads on mesh (one arrow per node or element); a single arrow for each geometrical entity represents loads on geometry. The basic length of the arrow also differs. For the same arrow magnitude percentage setting or uniform size setting within the load application panels, an arrow that represents a load on geometry is longer than arrows representing loads on mesh.

Altair Engineering
Distributed Load Mapper

The Distributed Load Mapper (DLM) macro enables you to perform structural finite element analyses by incorporating the results of a Computational Fluid Dynamic (CFD) analysis. Aerodynamic pressure loading and temperatures computed in a CFD analysis and written out either in TECPLOT 4.0 format or at spatial coordinates is mapped to a structural analysis mesh in OPTISTRUCT, NASTRAN, ABAQUS, or ANSYS format. The Distributed Load Mapper macro is added to the macro menu when you select menu config from the HyperMesh options panel and load the file, dlm.mac, from the <install_directory>\hm\scripts\dlm directory. The Distributed Load Mapper dialog is displayed when you click DLM... on the macro menu. When you enter data in the dialog you should begin with the first field and proceed, in order, to the next field below, until all data has been entered.
Entering data in the Distributed Load Mapper dialog requires the following steps: Load an input file containing CFD analysis results Load a structural analysis model (in OPTISTRUCT, NASTRAN, ABAQUS, or ANSYS input file format) Select a data type and a mapping method Set the scale factors Set the mapping algorithm
Altair Engineering
Assumptions Regarding the DLM Interface and Mapping Process

In order to map effectively, the CFD base model and the structural finite element model must exist in the same position in coordinate space. The only exception to this is when some of the DLM transformation functions are used correctly and appropriately through their selection in the DLM interface. A valid HyperWorks/HyperMesh license must be available on the local system or network for the DLM mapping algorithms to run. The element normals of both the CFD mesh and the structural analysis mesh must be consistent in that all the elements should be aligned and pointing in a common direction. For instance, if you are mapping a pressure loading on a wing structure, one of the following conditions must exist: The element normals of both the CFD model and the structural model must both be pointing outward from the wings outer surface. The element normals of both the CFD model and the structural model must both be pointing inward from the wings outer surface.
DLM Input and Output Files

It is useful to understand the input and output files related to a DLM session. Examples of Typical Input Files Computational fluid dynamics results database file, for example, D:\dlm_map_files\wing_cfd_model.dat Structural analysis model file, for example, D:\dlm_map_files\structural_model.dat Examples of Typical Output Files A DLM specific file, used to post-process in Altair HyperView. This file is related to the base CFD model. wing_cfd_model_dynain A DLM specific file, used to post-process in Altair HyperView. This file is related to the structural input model. structural_model_dynain A Tecplot 4.0 format file related to the structural input model. structural_model_tecplot.dat One file containing all the mapping parameters and selections detailed in the DLM interface. These files are always called hmimp.

Altair Engineering
Load an input file containing CFD analysis results

1. 2. For Computational fluid dynamics results database file:, click Browse... . Use the browser to locate a file. Click Open. Note: DLM accepts three input file formats:
Tecplot 4.0 BLOCK and POINT data formats DLM specific input file format (files which end filename_dynain) Measured pressure or temperature at xyz coordinates If the selected file is not in a DLM appropriate format, a warning message is displayed. If the CFD file is in a Tecplot format, a DLM specific file is created so that the data being mapped can be visualized in Altair HyperView. The file is placed in the same directory as the CFD database and takes its name from the parent file, i.e. filename_dynain. The pressure or temperature data at spatial coordinates must be distributed densely enough to have approximately one data point for each element of the structural model. The data must be prescribed in a fixed format. Each row should show the x, y, and z coordinates first, followed by the pressure or temperature value each data occupying 16 characters and a space separating them. The file also must have a header and footer as shown below: #XYZDATA #pressure 1.970389962E+00 4.548135996E-01-8.854129910E-02 1.098905325E+00 1.960631967E+00 4.357369840E-01-8.926119655E-02 1.105462790E+00 1.960968852E+00 4.356568158E-01-8.452460170E-02 1.095489740E+00 . . . #ENDDATA
Altair Engineering
Load a structural analysis model (in OPTISTRUCT, NASTRAN, ABAQUS, or ANSYS input file format)
1. 2. 3. For Structural analysis model file:, click Browse... . Use the browser to locate a file. Click Open. Once the data is mapped, it is appended to the structural model input file in the form of PLOAD or TEMP cards appended to the end of the OPTISTRUCT, NASTRAN, ABAQUS, or ANSYS input deck. A DLM-specific formatted file is written out for post-processing in Altair HyperView. The file is placed in the same directory as the structural model database and takes its name from the parent file, i.e. filename_dynain. Note: The data from the base CFD model is superimposed onto this model through the mapping process.
Select a data type and a mapping method

1. For Data parameter mapped:, select the data type to be mapped. The base CFD model file may contain up to seven different data types. These data parameters are read into the interface when you load the base CFD model file (Load an input file containing CFD analysis results). The data type is read from the information in the header block of the base CFD file. For Mapping method:, select Element nodes or Element centroids. The mapped data written to structural analysis model files can relate to two different locations on the finite elements of the model. The data can either be mapped and related to the nodes of each element in the structural model, or to the element centroids of each quadrilateral or triangular element in the structural mesh. The PLOAD card output to the structural model files is altered appropriately to the selected nodal or elemental configuration.
2.
Set the scale factor

1. For CFD result scaling:, enter a scale factor by which to increase or decrease the results. For example, if the CFD result scale factor is 1.500, all the data mapped during the DLM session is multiplied by a factor of 1.500. These scaled values are output to the structural model data file in the PLOAD card section. This could be used to apply a safety factor to the results, or to simply investigate the effects of scaling the load upon the model. The default value is 1.00 (no scaling). 2. For CFD model scaling:, enter a scale factor to physically scale the base CFD analysis model, if dimensional reduction/scaling was used in the actual CFD analysis. For example, if the XYZ dimensions of the model were scaled to 1/200 of the actual size and submitted for analysis. If a value of 200 is entered for CFD model scaling:, the X, Y, and Z coordinates of all the nodal locations in the base CFD model is scaled. This would ensure that the base CFD model would match and be positioned in the same Cartesian space as the structural analysis model. The default is 1.000, which would leave the coordinates of the base CFD model unchanged prior to mapping.

Altair Engineering
Set the mapping algorithm

1. For Mapping algorithm:, select one of the following options: Averaged Takes the data and average for data points captured in the proximity of the structural data position being mapped to. Selects the maximum value captured in the proximity of the data point being mapped to. Selects the minimum value captured in the proximity of the data point being mapped to. Accepts whichever is larger in magnitude, for instance, the Modulus value of the data points captured in the vicinity of the element/nodal location being mapped to. Takes the maximum and minimum of the data points captured in the proximity of the data location being mapped to, and takes an average of these two values. The default mapping algorithm.
Maxima Minima Extrema
Averaged extrema
Delaunay-OC 2. Click OK.
The mapping algorithms are accessed, the mapping process runs, and the DLM dialog closes upon completion of the mapping process.
Altair Engineering
Mathematical Loading
Distributed pressure loads can be created at nodes via mathematical loading functions using the Mathematical Loading macro. The Mathematical Loading macro is added to the macro menu when you select menu config from the HyperMesh options panel and load the file, dlm.mac, from the <install_directory>\hm\scripts\dlm directory. The Mathematical Loading dialog is displayed when you click Math... on the macro menu.
Mathematical Loading dialog The Mathematical Loading macro requires the following input: Structural analysis model file: Equation string fn(x,y,z) = The browser allows you to select the structural model in NASTRAN format on which to apply a mathematical function. This field allows you to enter an equation string using standard spreadsheet inputs for the various operators and operands. The operators for which the algorithms are programmed are listed below: Programmed Operators: Unary minus ^ Power of ln Natural Log log Log to the base 10 sin sine cos cosine tan tangent asin arcsine acos arccosine atan arctangent exp Exponential / division * Multiplication + Addition Subtraction Acceptable 1 1.0 10e-01 336 HyperMesh 8.0 Users Guide
operands may be input in the following forms: corresponds to 1.0 corresponds to 1.0 corresponds to 1.0 Altair Engineering
0.1e+01 corresponds to 1.0 x corresponds to the coordinate position x of the nodes of the model y corresponds to the coordinate position y of the nodes of the model z corresponds to the coordinate position z of the nodes of the model The following input rules apply: Equation strings should always have balanced parentheses to ensure that the logic of the math expression is maintained. The dialog informs you when there is an error in this instance. Spaces and a mixture of uppercase and lower case letters are acceptable. However unrecognized characters and functions will cause the loading to yield unacceptable results.
Note:
To create pressure loads at element centroids via mathematical functions, use the Field Loads macro on the Geom/Mesh macro menu.
Altair Engineering
Post-Processing Analysis
The HyperMesh post-processing functions allow you to review the results files and databases generated by external codes. Results files can be translated into HyperMesh results databases which are then read into HyperMesh for post-processing. This translation is done using result translators; for more information, refer to the individual translators in the Interface help system. This section describes the structure of a HyperMesh results database and explains how to use the post-processing functions to create contour, assigned, deformed, and vector plots.
HyperMesh Results Database

The structure of a results database allows you to access results by a method similar to that of the analysis code. A results database is divided into sections called simulations. Each simulation stores the results for a model as it responds to a loading condition. For example, if you run a linear statics problem and apply three different loading conditions to your model, the results file generated by the translator contains three simulations. If you run a nonlinear job, each load step (the response of the model to each incremental amount of load applied) translates to a simulation. Each simulation in the results database is further subdivided into data types. Each data type found in a simulation contains a group of results of the same type. For example, each simulation in a results file may contain two data types: displacements and von Mises stress. A data type may contain only one type of result. Data types are one of the forms described below: nodal displacement nodal value Stores three floating point values at a node. This form of data type is usually used to store displacements or a vector quantity. Stores one floating point value at a node. This form of data type is used to store stress quantities or other types of results where a single value is needed at a node. Stores one floating point value at an element. This form of data type is used to store stress quantities or other types of results where a single value is needed at an element. Stores a complex value (magnitude and phase) at a node. This form of data type is usually used to store displacements or a vector quantity. Stores a complex value (magnitude and phase) at a node. Stores a complex value (magnitude and phase) at an element. Stores a complex von Mises value (magnitude, phase, offset) at a node. Stores a complex von Mises value (magnitude, phase, offset) at an element.
element value
complex nodal displacement complex nodal value complex element value complex nodal von Mises complex element von Mises
Data types are not required to contain results for every node or element in the model, and may contain a subset of the total model, if this is appropriate. If this occurs, HyperMesh prints a message indicating that results for some of the entities requested were not found in the database. In order to complete the post-processing function being executed, HyperMesh sets the results values needed for that function to zero for all of the nodes or elements that are missing.

Altair Engineering
Specifying the Results File

In order to perform post-processing functions, you must first specify the name and location of the HyperMesh results database. There are two ways to select a results file: From the files panel, select the results sub-panel, and for file:, enter the path and name of the results file or click browse... to select a file using the browser. In the global panel, for results file:, enter the path and name of the results file or click browse... to select a file using the browser.
Creating Deformed Geometry Plots

The deformed panel allows you to display the deformed geometry of your model statically, in either wire frame or hidden line mode. The selected simulation must have a data type in it that contains nodal displacement records. It is from the data contained with the nodal displacement records that HyperMesh is able to calculate the deformed geometry of the structure.
Creating Animations
The HyperMesh animation functions allow you to view your model structure in motion. The three types of animation include linear, modal, and transient. Linear Linear animation creates and displays an animation sequence that starts with the original position of the structure and ends with the fully deformed position of the structure. An appropriate number of frames are linearly interpolated between the first and the last positions. Linear animation is usually selected when results are from a static analysis. Linear animation sequences are generated in the deformed panel. Modal animation creates and displays an animation sequence that starts and ends with the original position of the structure. The deforming frames are calculated based on a sinusoidal function. Modal animation is most useful for displaying mode shapes. Modal animation sequences are generated in the deformed panel. Transient animation displays the structure in its timestep positions as calculated by the analysis code. Transient animation is used to animate the transient response of a structure. Transient animation sequences are generated in the transient panel.
Modal
Transient
The selected simulations must include a data type that contains nodal displacement records in order for HyperMesh to create an animation sequence. HyperMesh calculates the deformed geometry of the structure from the data contained within the nodal displacement records. For linear and modal animation, HyperMesh uses only one simulation and this simulation must include a data type that contains nodal displacement records. For transient animation, HyperMesh uses a range of simulations. In this case, each of the simulations used in the animation sequence must include a data type that contains nodal displacement records.
Altair Engineering
Creating Vector Plots

A vector plot displays the model with a vector at each node that has a result-based direction and magnitude. Vector plots are used to determine the direction of movement and allow you to verify the location of the center of rotation of a model. See the vector plot panel for more information.
Creating Contour Plots

The contour function in the contour panel generates color bands on a model, based on the values found in the results file. The bands of color are created by calculating a value for each node in the model and then interpolating across each element. The results file must include a simulation that contains one of the three forms of data types. Each data type is handled differently when it is used to generate a contour plot. When a contour function is performed, the objective is to take all of the results and place them at the nodes of the elements. In order to accomplish this, HyperMesh may have to average results before it can display the contour plot. nodal values and displacements The results are stored at the nodes. HyperMesh can create the contour plot without modifying any of the values in the results file. The values are located at the centroid of the element. HyperMesh averages the centroidal element values to the nodes of the elements. You should be aware that averaging is taking place when element centroid values are used to create a contour plot.
element values1
Creating Assigned Plots

The assign function in the contour panel assigns a color to each element in the model, based on the values in the results file. The elements are then displayed in the solid color assigned to them. This allows you to display elements that have values within a specified range. The results file must include a simulation that contains one of the three forms of data types. Each data type is handled differently when it is used to generate a contour plot. When the assign function is performed, the objective is to take all of the results and place them at the centroid of the elements. In order to accomplish this, HyperMesh may have to average results before it can display the assigned plot. element values The results are already stored at the centroid of the element, so no further calculations are required. HyperMesh averages the results at the nodes to the centroid of the elements. For each element, this is accomplished by adding the results at each node and dividing by the number of nodes on the element. You should be aware that averaging is taking place when nodal values or nodal displacements are being used to create an assigned plot.
nodal values and displacements

Altair Engineering
Adding Plot Identification

After you create a results-based plot, you can add titles, modify the colors used in the legend, and relocate the legend and the descriptor. Temporary titles can be added to each type of plot by entering a title in the title = field in the contour panel. After you enter the title and create the plot, the temporary title is displayed on the upper left side of the screen. HyperMesh creates the "descriptor" in order to display the simulation and data type that were used to create the plot. By default, the descriptor is located in the upper left-hand corner of the plot above the legend. To modify the descriptor, click within the descriptor to access the title edit panel, click color to change the color of the text of the descriptor, click font and select the size font you want to use in the descriptor. HyperMesh plots a legend if the results-based plot created requires it. To modify a legend, click within the displayed legend to access the legend edit panel. Functions on this panel allow you to move the legend to a different location on the screen, change the color of the text in the legend, reverse the colors of the legend, change the font size, and also change the colors used in the legend that correspond to the model.
Inspecting the Results

A contour or assigned plot provides a fast, convenient way of viewing the results of a large number of elements. When you want to determine the actual value that an analysis code has calculated for a node or element, you can select the node or element after the results-based plot has been created. The ID, simulation and data type, and value of the node or element are displayed in the menu area.
Altair Engineering
XY Plotting
The functions in the xy plots module allow you to study the relationships between data vectors in results files. This section introduces the functions that are available in the xy plots module. Information about xy plots is stored in plot collectors, which are referred to as plots. Plots maintain a list of pointers to curves that are to be displayed on the plot. The plot may contain any number of curves. There is no limit to the number of plot collectors that a HyperMesh database may contain. Information about curves is stored in curve collectors, which are referred to as curves. To display a curve, you must assign the curve collector to a plot. A curve may appear on more than one plot at a time and there is no limit to the number of curves that a HyperMesh database may contain. You can create standard plots or dual plots that show real /imaginary or phase/magnitude data. Procedures for creating and editing xy plots and curves include: Creating an XY Plot Modifying XY Plots Working with Multiple XY Plots Modifying Multiple XY Plots Creating Curves on XY Plots Reading Curves from an ASCII File Creating Analysis Based Curves Creating Curves using Simple Math Operators Creating Curves from Files or Math Expressions Modifying Curve Attributes Displaying Selected Curves on Plots
In addition, you can use the curve editor to view and modify curves already defined in your HyperMesh model.

Altair Engineering
XY Plots Module
The xy plots module is a group of panels that perform operations on plots and the curves displayed on those plots. To access the xy plots module, select xy plots on the Post page of the main menu. The xy plotting panels are described below: axis labels The axis labels panel allows you to modify the x and y axes titles and labels. You can also change the color and font size used to display these entities. The axis scaling panel allows you to modify the starting and ending values of the plot axes. You can set the values explicitly or implicitly by using the panel functions such as find curves, circle zoom, and zoom out. The border panel allows you to change the thickness and color of the border around the plot. You may also specify whether the border is displayed and the size of the margin between the border and the plot. The curve attribs panel allows you to change the color, marker style (used to indicate the point location), thickness, and the line style (solid, dashed, etc.). You can apply a scaling factor to the original data points. You can also change the curve title that appears in the legend. Creates and modifies the curves in the database. This panel allows you to read data vectors from files as well as perform advanced mathematical operations on curves. The grid attribs panel allows you to change the color, line style, thickness of the grid lines, and the margin displayed around the grid lines. The grid labels panel allows you to change the color, font, and number of significant places in the labels. Grid labels appear along the x and y axes in the plot (tick marks). Calculates and displays the integral of a curve. The legend panel allows you to change the location and the font used to display the legend. The plot titles panel allows you to change the plot title, subtitle, and label. In addition, you can change the color and font size used to display these entities. Allows you to create an xy plot and assign curves to the xy plot. Allows you to determine the coordinate values of points in a curve. Reads curves from an ASCII file. Allows you to rename curves. Generates a curve from the currently-selected results file. Allows you to perform simple mathematical calculations on a curve.
axis scaling
border
curve attribs
edit curves
grid attribs grid labels
integrate legend plot titles
plots query curves read curves rename results curves simple math
In addition, you can use the curve editor to view and modify curves already defined in your HyperMesh model.
Altair Engineering
Creating an XY Plot
Each xy plot window is assigned a name when you create it. Plot attributes include the title, subtitle, and labels, and also the margin and border around the xy plot. These attributes can be adjusted before or after you add curves to the plot. The first step in the process of creating an xy plot is to use the plots panel to name and create an xy plot collector. HyperMesh initially assigns default values to the xy plot attributes.
Modifying an XY Plot
After you create an xy plot, you can change the color, thickness, or width of the border, the grid labels and grid attributes, or add a title to the plot. To modify an xy plot, select the panel that applies to the attribute you want to change, select the plot you want to change, and change the attribute in the panel. After each change, HyperMesh immediately displays the update. Each time a panel in the xy plots module is accessed, HyperMesh displays the existing values of the current xy plot (the plot listed after plot =) in the data entry fields in the panel. Every time you change the current xy plot, the panels in the xy plots module are updated to reflect the change. This process also applies to curves.
Working with Multiple XY Plots

HyperMesh places every xy plot within a window. This allows you to control multiple plots by resizing and moving plots around the screen. XY plot window placement is controlled with the Windows panel. Access this panel by pressing the w key.
Modifying Multiple XY Plots

When several plots are contained within a database, you may wish to modify one of the values on all of the plots. For example, you may wish to change the axis titles so that they are all the same. You can modify one plot so that it has the desired values, and then apply those modifications to the other plots, or a subset of the plots, in one step. When you modify xy plots using the panels of the xy plots module, the plot = field allows you to select one plot and the plots entity selector allows you to select multiple plots.

Altair Engineering
Creating Curves on XY Plots

You can create curves using four different methods: Read curves from an ASCII file Extract a curve directly from a results database Create curves by using a few simple math operators Read single curves from files as well as generate curves by using mathematical expressions
Reading Curves from an ASCII file

When HyperMesh reads curves from an ASCII file with the read curves panel, it assumes that the format of the input file is as follows: XYDATA,TITLE X1, Y1 X2, Y2 . . . ENDDATA XYDATA,TITLE X1, Y1 X2, Y2 . . . ENDDATA Each curve in the file is defined in a block format. The block begins with the statement, XYDATA. After XYDATA, the title assigned to the curve, which is displayed in the legend, follows on the same line. Point data follows with a set of (x, y) data pairs on each line. The block ends with an ENDDATA statement. In the above example, there are two blocks of data, which define two curves.
Creating Analysis-Based Curves

Analysis-based curves are generated from the HyperMesh binary results file. When you create an analysis curve, you select entities of interest in your model, and then select a data type for the x axis data points and a data type for the y axis data points. After this information has been supplied, HyperMesh reads the required data from the results file and generates the appropriate curve. Analysis-based curves are generated in the results curves panel.
Creating Curves using Simple Math Operators

Curves can be created using simple math operators in the simple math panel. You can combine two curves, transform a curve, or export the curve. For every operation, you can specify that the x or y values of the curve remain fixed. You can also apply external filters to curves in this panel. Examples of external filters are in the filters subdirectory that is provided when this option is selected. Essentially, filters exchange data with HyperMesh, using the standard HyperMesh curve data file format.
Altair Engineering
Creating Curves from Files or Math Expressions

The edit curves panel allows you to create new curves or edit existing ones. Each vector of a curve can be defined using either a data vector in a data file or a math expression. For example, the data source for the x vector could be a file, and the data source for the y vector could be a math expression. The data sources for the x and y vectors are displayed in the x = and y = fields. To edit the x and y vectors of a math curve, you must indicate the curve number and the x or y vector, in the format curve number.vector: For example: c1.x c1.y To reference the x vector of curve 1. To reference the y vector of curve 1.
When you modify a curve, HyperMesh recalculates the curves in the proper order, based on what has been modified. The y vector can be a function of x or the x vector can be a function of y. New data can be selected from a source file or mathematically defined. Source file data is divided into type, request, and component. Type Request Component Note: Data files can consist of different types of data. Available data types depend on the data file. Once the data type has been selected, the data request set needs to be selected. After the data request set has been selected, the component must be selected.
For more information about math expressions, refer to the Altair Math Reference.

Altair Engineering
Modifying Curve Attributes

Modifying curves is very similar to modifying plots. The following curve attributes may be changed in the curve attribs panel. curve title curve width curve style curve color curve marker The curve title is displayed in the legend. The width of line used when the curve is drawn. HyperMesh currently supports either thick or thin lines. The style of line used to draw the curve. HyperMesh currently supports a solid line, no line at all, and four different patterns. The color used to draw the curve. HyperMesh currently supports 15 standard colors. Determines the markers drawn around each data point in the curve, when the curve is displayed. HyperMesh currently supports circular, triangular, and square markers. The curve may also be displayed with no markers shown. This scale factor is used to scale the x values in a curve. This scale factor is used to scale the y values in a curve.
x scale factor y scale factor
Displaying Selected Curves on Plots

After you have read or created curves, you can select which curves in the database you want to display on an xy plot. To select curves for a plot, select the plots panel and click select curves. HyperMesh displays a list of the available curves in the database. The names of the curves that are already displayed on the current xy plot are highlighted. Modify the list by selecting the curves by name and removing or adding the curves to the current plot as desired and click return.
Altair Engineering
Using the Curve Editor

The curve editor is a pop-up window that allows you to view and modify graphed curves in a more intuitive and holistic way than the individual xy plots panels provide. Access the curve editor from HyperMeshs Setup pull-down menu. The curve editor contains four main areas, outlined with colored boxes in the image below: the curve list (green), curve attributes (blue), graph area (red), and graph attributes (cyan).
Its important to be aware that the curve editor is not completely symmetrical with HyperMesh, in the sense that changes made in the curve editor are automatically sent back to HyperMesh, but changes made in a HyperMesh panel do not automatically get sent to the curve editor. For this reason, if you leave the curve editor open while making changes within the HyperMesh XY plotting module, you must use the update button in the curve editor to import the changes. To summarize: Changes made in the curve editor immediately affect HyperMesh. Changes made in HyperMesh do not immediately affect the curve editor, and must be imported by use of the update button.
To quit the curve editor, click the close command button. Note that any changes you make in the curve editor will be retained, because they are automatically applied as you make them. To display curves in the graph area: 1. Click the desired curve in the curve list. The curves attributes fill in the fields in the curve attributes area. 2. 3. Modify the curve attributes if needed. Click the display checkbox in the curve atributes area. The curve displays in the graph area. 348 HyperMesh 8.0 Users Guide
Altair Engineering
To change a curve's attributes: 1. Click the curve that you wish to modify. Either click the curve in the curve list. Or 2. Click the curve in the graph area, if it is already set to Display.
Make any desired changes to the curves attributes: Modify each X and/or Y value by clicking it, pressing the <delete> key to erase the current value, and then typing in a new value. Change the Color by clicking the colored box. A list of available colors displays; click the desired color to select it. Click the display checkbox to toggle the display of the curve in the graph area. To place a marker symbol at each point on the curve, select a symbol from the list box. To change the symbol spacing, select a number from the every: list box. For example, if you choose 3 then only every third point will display as a symbol. Select a Line style to change the curves line from solid to dotted, or show no line at all. Note: If you choose no line, the lines symbol points will still display.
To draw the curve in a thicker line, click the thick line checkbox.
To change the graph's attributes: 1. In the graph attributes area, modify the fields inside the X-axi s frame: Type in a new label to change the graphs X -axis label. For example, you could change it from X to Acceleration. Select a precision to change the number of decimal places that display in the numbers on this axis. Choose a min and max to restrict the graph to a specific range of values. For example, even if your data included accelerations ranging from 0 up to 10 m/s , you could 2 restrict the X axis to only graph accelerations from 1 to 5 m/s . Change the number of Tics and Grids per tic to control how fine the grid behind the curves is drawn. The number of Tics indicates how many evenly-spaced, numbered increments display between the beginning and end of the axis. For example, if your data ranges from values of 0 to 2.0, setting Tics to 3 produces three increments (at 0.5, 1.0, and 1.5). The Grids per tic sub-divides each tic, making a finer grid, but these grid lines are not numbered (much like the fractional markings on a ruler). 2. Modify the fields inside the Y-axis frame: Type in a new label to change the graphs Y-axis label. For example, you could change it from Y to time. Select a precision to change the number of decimal places that display in the numbers on this axis.
2
Altair Engineering
Choose a min and max to restrict the graph to a specific range of values. For example, even if your data included accelerations from 0 seconds to 60 seconds, but you only wish to graph the accelerations that occur between 30 and 35 seconds, you could restrict the range by typing 20 into the min and 35 into the max.
Change the number of Tics and Grids per tic to control how fine the grid behind the curves is drawn. The number of Tics indicates how many evenly-spaced, numbered increments display between the beginning and end of the axis. For example, if your data ranges from values of 0 to 2.0, setting Tics to 3 produces three increments (at 0.5, 1.0, and 1.5). The Grids per tic sub-divides each tic, making a finer grid, but these grid lines are not numbered (much like the fractional markings on a ruler).
3.
Modify the fields inside the Legends frame: Select a location to determine where the legend displays in the graph area. Click the hide checkbox to toggle the display of the legend on and off.
To create a new curve: 1. Click the New command button in the curve editor window. HyperMesh temporarily supplants the curve editor and prompts you to specify a name for the new curve. 2. 3. Type in a name for the new curve. Click proceed. HyperMesh returns you to the curve editor. 4. Click the new curve in the curve list and modify its attributes as needed. For example, type in the X and Y coordinates for each data point in the curve. To delete a curve: 1. 2. In the curve list, click the curve that you wish to delete. Click the Delete command button. A confirmation window displays. 3. Click Yes to confirm the deletion, or No to keep the curve.
Undo You cannot undo a deletion; once you delete a curve, you cannot recover it. To rename a curve: 1. Click the desired curve in the curve list. HyperMesh temporarily supplants the curve editor and prompts you to specify a new name for the chosen curve. 2. 3. Type in a new name for the curve. Click proceed. HyperMesh returns you to the curve editor, which now uses the curves new name.

Altair Engineering
AutoDV Introduction
AutoDV is utility developed for the generation of perturbation vectors for shape optimization in optimization packages such as Altair OptiStruct, Altair HyperStudy, Nastran, Genesis, Altair HyperOpt, and Templex. AutoDV can also be used to generate distributed loads. In the past, AutoDV has been stand-alone software. Starting with HyperWorks 6.0, most of AutoDVs capability to create perturbation vectors using control perturbations is fully integrated in HyperMesh. The stand-alone solver is still available and can be used for the generation of manual perturbations. The function of creating harmonic shape functions for 2D problems only works with AutoDV. Further, AutoDV is now complemented by HyperMorph, a more flexible tool to set-up and generate shape perturbations. AutoDV interfaces with HyperMesh thru the AutoDV template for export and AutoDV reader for import. Before importing AutoDV data, a finite element model must be loaded into HyperMesh.
Shape Optimization
The type of design variables that are used distinguishes different types of structural optimization. In topology optimization, usually density-related values that define the material distribution are the design variables. In size optimization, input parameters of a model, such as beam section properties, the shell thickness, and spring properties are design variables. In shape optimization, the design variables define the boundary shape of the part to be optimized. In finite elements, the shape of the structure is defined by the vector of nodal coordinates, x. The boundary shape changes must be translated into changes of the interior of the mesh to avoid mesh distortions due to shape changes. There are different approaches used to define the shape in an optimization setup. The two most commonly used in commercial software packages like OptiStruct, HyperStudy, HyperOpt, Nastran, and Genesis, are the basis vector approach and the perturbation vector approach. Both approaches refer to the definition of the structural shape as a linear combination of vectors. Using the basis vector approach, the structural shape is defined as a linear combination of basis vectors. The basis vectors define nodal locations.
x = DVi BVi
x is the vector of nodal coordinates, BVi variable DVi .

where
is the basis vector associated to the design
Using the perturbation vector approach, the structural shape change is defined as a linear combination of perturbation vectors. The perturbation vectors define changes of nodal locations with respect to the original finite element mesh.
x = x 0 + DVi PVi
where
x 0 is the vector of nodal coordinates of the initial design, PVi is the perturbation vector associated to the design variable DVi .
is the vector of nodal coordinates, AutoDV generates perturbation vectors. If there is a choice in the optimization code, the perturbation vector approach must be selected. Altair OptiStruct and Altair HyperStudy use the perturbation vector approach. Altair HyperOpt provides both, with the perturbation vector approach as the default setting.
Note:
Altair Engineering
Generation of Perturbation Vectors

Perturbation vectors can be generated in one of three ways: 1. 2. 3. Manual perturbation of grids in HyperMesh. Polynomial perturbation vectors using design domains. Harmonic perturbation vectors using design domains.
Before these methods can be applied, a finite element model representing the baseline shape of the structure must be developed.
Manual Perturbation
To generate perturbation vectors by the manual perturbation method: 1. 2. Write a <prefix>.base file using the baseline model of the structure using the OptiStruct template supplied in the distribution. In HyperMesh, move the grids to define the perturbed shape. Do not save the perturbed model. 3. 4. 5. 6. 7. Write out a perturbation file <prefix>.pert<nnn>, where nnn is the design variable ID, using the AutoDV template. Example: mymodel.pert006. To generate another perturbation vector, retrieve the baseline HyperMesh database and complete steps 2 and 3, giving the *.pert file a different ID. Select the solver panel. Click the switch and select AutoDV as your solver. Run AutoDV through the solver panel using the appropriate options.
AutoDV compares all <prefix>.pert<nnn> models with the <prefix>.base model, identifies the perturbed grids, and generates the corresponding perturbation vector. AutoDV requires that the <prefix>.pert<nnn> files contain data only for the perturbed grid points. However, the files generated by HyperMesh contain the entire model. AutoDV creates condensed <prefix>.pert<nnn> files that contain only the perturbed grids.

Altair Engineering
Polynomial Perturbation Vectors

To create polynomial perturbation vectors: 1. 2. 3. 4. 5. 6. 7. Define primary domain model elements and domain node sets. Define shapes and control perturbations. If needed, build a secondary domain model and define secondary node sets. Output a bulk data file using the HyperMesh template for AutoDV. Assign shapes to design variables. Output a bulk data file using the HyperMesh template for AutoDV. Use the solver panel to run AutoDV.
Primary Domain Model

This example shows how to create a primary domain model over the finite element model using the following first order 2-D and 3-D domain elements. 2-D elements 3-D elements DQUAD4, DTRIA3 DHEXA8, DPENTA6, DTETRA4
These element types are generated using the AutoDV template provided in the distribution. To create a domain element: 1. 2. 3. 4. 5. On the BCs page, select the optimization panel. Select the perturbations panel. Select the domain subpanel. Select the type of domain element. Pick the nodes that form the domain element. Each domain element generally encompasses a large number of finite elements. The Domain model must encompass those finite element grids of the model that need to be perturbed. All domain elements may be organized in more than one domain component. However, none of the domain components should include finite elements. It is recommended, but not necessary, that you organize 2-D and 3-D domain elements in separate components.
Altair Engineering
Primary Domain Node Sets

Node sets constitute the primary entities for generating perturbation vectors. All nodes in a given node set are perturbed using mathematical relationships based on the control perturbations applied on the Domain Model. There should be exactly one domain element related to each node set; i.e., all corner nodes of that element must belong to that node set. This relationship is not explicitly defined by the user; it is identified by AutoDV. However, you must implicitly ensure that relationship while creating domain elements and node sets by making sure that all the nodes that need to be perturbed as a shape variable are completely encompassed or parameterized by the domain model. A given node may belong to more than one node set. This generally happens at the common edges and corners between domain elements. Domain node sets can be created automatically when the domain element is created, or they can be created manually. To manually create a domain node set for an existing domain element: 1. 2. 3. 4. 5. 6. 7. 8. On the BCs page, select the optimization panel. Select the perturbations panel. Select the domain subpanel. Select update. Toggle nodeset to manual. Pick the domain element from the graphic display. Select the nodes for the domain node set. Click add.

Altair Engineering
Control Perturbations
Perturbation vectors are generated by interpolating control perturbations defined at selected control points. The corner points of a domain element and mid-side nodes of the corresponding node sets constitute control points (e.g., a DQUAD4 domain has 8 control points). Control perturbations are defined by creating vectors at control points. To define control perturbations: 1. Create shape design variables:

Select the optimization panel on the BCs page. Select the perturbations panel. Select perturbations using the toggle. Enter a name (max. 8 characters) in shape =. Click create shape.
2.
Create a control perturbation at a control point:

Define vectors on corners or edges of domain elements. Click create vector to create the vectors. They are automatically added to the shape specified in shape =.
3.
Animate the shape design variable:
Click animate. The deformed panel is displayed so you can animate the design variable to validate your definition. Click return to return to the perturbations panel.
AutoDV computes perturbations of all structural grids by interpolating control perturbations. For 2-D domains, the interpolation function is a product of two functions: P(x,y) = Px(x) Py(y) For 3-D domains, the interpolation function is a product of three functions: P(x,y) = Px(x) Py(y) Pz(z) where P x, Py, and Pz are polynomial interpolation functions of up to quadratic order. The interpolations are performed as follows. The order of interpolation is based on the presence of mid-side control perturbations. On a given edge, the interpolation is parabolic if a mid-side control perturbation is defined; otherwise it is linear. A linear interpolation uses control perturbation at the corners. A quadratic interpolation would use the corner as well as the mid-side control perturbations. In order to generate a quadratic perturbation, you do not need to create a second order domain element. Instead, place the control perturbation on a mid-side node on an edge of the domain node set. That mid-side control point does not have to lie on the edge of the domain element. AutoDV identifies the mid-side perturbations and internally changes the corresponding edge of a domain element from linear to quadratic (curvilinear edge element). For corner control points, defining a zero magnitude vector is the same as placing no vector. In either case, AutoDV assigns a control perturbation of magnitude zero to the corner point.
Altair Engineering
For mid-side control points, defining zero magnitude vector is not the same as placing no vector. Whereas the absence of a mid-side control perturbation yields a linear interpolation on that edge, the presence yields a quadratic interpolation. In the case of a zero magnitude mid-side perturbation, the interpolation is quadratic with the value of zero for the mid-side node. AutoDV computes the perturbation vectors for shape variables in the following order: Identifies all domain elements and node sets attached to vector belonging to a given shape variable. Generates the corresponding list of grids to be perturbed in that variable. Computes perturbation of each grid in the list by interpolation using the related control point perturbations.

Altair Engineering
Secondary Domain Models and Node Sets

A secondary domain model allows computation of perturbation vectors for grids on 1-D elements connecting two different components. You may use the secondary domain model where two nodes belonging to the primary domain are connected using several 1-D elements in a series. Secondary domain is not required if the nodes are connected using a single 1-D element. For example, consider the two sheet metal components connected using gum-drops, illustrated below. The gum-drops are modeled using a rigid (R1)-spring (K)-rigid (R2) representation. The domain model for each plate contains one element each. The perturbation vectors are also shown in the illustration. Here, grid points G2 and G3 are generally coincident.
With only primary domain, the perturbation vector for this model is as shown in the illustration below. Here, the control perturbation causes grids G1 and G4 to be perturbed as shown. However, because grids G2 and G3 are not part of any node set, they remain unperturbed. This problem is solved using a secondary domain model as follows: Create one rigid element (type DRBE2) between the two end nodes (G1 and G4 in this example). Move the end nodes as well as all intermediate nodes into an independent node set.
AutoDV responds by: Computing pert urbations on the primary domain model using the control perturbations. Identifying perturbations of the end nodes of the secondary domains. Interpolating those perturbations linearly to all the grids of the secondary domain.
Altair Engineering
Using the example illustrated above, this yields the perturbation shown below.
Note:
A DRBE2 element does not have to be connected to a control point, and no control perturbations are required at the two nodes of the DRBE2 element.

Altair Engineering
Harmonic Perturbation Vectors

Harmonic shape variables are defined using a process similar to that for polynomial shape variables. However, modeling requirements for generating harmonic variables are very stringent. Harmonic variables are defined only on DQUAD4 domains, one DQUAD4 element at a time. Each harmonic shape variable component must contain exactly four vectors, one at each corner point of the DQUAD4. Each vector may have a different length and orientation. The harmonic shape variables are computed using a product of the following two functions: V(x,y) = P (x,y) T (x, y) Where P is the polynomial function described in the previous section, and T is the harmonic function given by: T(x, y) = Xm(x) Yn(y) Where Xm(x) = cos (m*x/2) = sin (m*x/2) =1 and Yn(x) = cos (n*y/2) = sin (n*y/2) =1 for odd values of n for even values of n for n = 0 for odd values of m for even values of m for m = 0
For m = n = 0, the harmonic component of the shape variable has a value of 1. Then the shape variable is reduced to the polynomial shape variable. The orders m and n of harmonic functions are user-controlled. These are part of the vector collector card. To define harmonic perturbation vectors: 1. 2. Generate domain elements and node sets as described in the previous section. Select the DQUAD4 element on which harmonic perturbation vectors are desired and create a shape with exactly four vectors - one at each corner control point of that element. Each vector may have a different length and orientation. There should be no other vector in that shape. In the shape panel, create a design variable using that shape. The design variable label should not have more than four characters. 3. 4. Select the design variable in the card pre-viewer in the permanent menu. Edit X_ORDER, X_TYPE, Y_ORDER, and Y_TYPE: Card image X_ORDER Y_ORDER Symbol m n Default 0 0
Altair Engineering
You have the option of generating all, odd, or even harmonics by entering the appropriate harmonics types in the vector collector. Accordingly, modify the setting in the harmonic subpanel. Card image X_TYPE Y_TYPE Options all, odd, even all, odd, even Default all all
For given values of m and n, AutoDV generates a series of independent perturbation vectors. It generates shape variable names by appending the x and y orders to the component name. Examples of the naming procedure follow:
Example 1:
X_ORDER = 2 Y_ORDER = 1 Shape Variable m n Name 1 0 0 dv01 2 0 1 dv010001 X_TYPE = all Y_TYPE = all 3 1 0 dv010100 4 1 1 dv010101 5 2 0 dv010200 6 2 1 dv010201 desvar name = dv01
Example 2:
X_ORDER = 2 Y_ORDER = 1 Shape Variable m n Name 1 0 0 dv02 X_TYPE = even Y_TYPE = all 2 0 1 dv020001 3 2 0 dv020200 4 2 1 dv020201 desvar name = dv02
Example 3:
X_ORDER = 2 Y_ORDER = 1 Shape Variable m n Name 1 0 0 dv03 X_TYPE = odd Y_TYPE = all 2 0 1 dv030001 3 1 0 dv030100 4 1 1 dv030101 desvar name = dv03

Altair Engineering
Generation of Variable Loads

Generating variable loads with AutoDV is similar to generating perturbation vectors. Variable loads are generated by interpolating control vectors defined at selected control points. The control points can be the corner points of a domain element or the mid-side nodes along the edge of domain elements. Variable loading can be generated for forces, moments and temperatures. Domain elements and domain node sets for the domain where the load is applied must be created before you can generate a variable load. To generate a variable load: 1. Create control perturbations to define the characteristic of the variable load:

Select the optimization panel on the BCs page. Select the perturbations panel. Select desvar using the toggle. Enter a name (max. 8 characters) in desvar =. Click create.
2.
Create a control perturbation at a control point:

Select perturbations using the toggle. Define vectors on corners or edges of domain elements. Click create to create the vectors. They are automatically added to the design variable specified in desvar =. AutoDV computes the variable loads on each structural grid by interpolating the control perturbations defined on control points. Creating control perturbations at the corner nodes of the domain element yields a linear interpolation. A quadratic interpolation can be generated by creating control vectors either on the mid-side control points or on both, the corner and mid-side control points.
3.
Run AutoDV to generate the variable loads: Before you run AutoDV, you must write an AutoDV input deck using the AutoDV template.

On the BCs page, select the solver panel. Select AUTODV as the solver. Click name = and enter the name of the AutoDV input deck. Click solve to create the interpolated variable loads.
4.
Apply the variable loads:

On the files panel, select the results subpanel. Click file = and enter the result file with the .dv.animate suffix. On the Post page, select the apply result panel. Click simulation = and select the variable loading condition wants to apply. Select the create load subpanel. Select all the displayed nodes and set mult = to 1. Click apply to apply the variable loads.
Altair Engineering
Examples:

Altair Engineering
Running AutoDV Stand-alone

To run AutoDV, select AUTODV as the solver in the solver panel and then give the prefix of the input file name along with the options. The input file name should be prefix.base. autodv -file <prefix> -inp opt1 -ent opt2 -code opt3
The valid entries and default values for options are given in the following table. Note that these parameters could be given in any order. Entity <prefix> Valid Options Prefix of the input file name, or input file name. OPTISTRUCT, NASTRAN, GENESIS, HYPERSTUDY, TEMPLEX, HYPEROPT FORC, MOMT, TEMP, LONG OPTISTRUCT, HYPERFORM, NASTRAN, DYNAKEY, DYNASEQ, PAMCRASH, RADIOSS, ABAQUS, ABAQUS2D, MARC, ANSYS, MADYMO OPTISTRUCT Default Value Solver Panel input file =
Opt1
analysis code =
Opt2 Opt3
NONE NONE
component = subcode type =
The interdependency of options on each other is explained in the following table. For example, for a given opt1, it gives the possible values for opt2 and opt3. Opt1 OPTISTRUCT, NASTRAN, GENESIS OPTISTRUCT, NASTRAN, GENESIS HYPERSTUDY TEMPLEX Opt2 None Long Opt3 Ignored Remarks For shape optimization None Standard format Long Long format For variable loading
FORC, MOMT, TEMP Ignored
Ignored
OPTISTRUCT, HYPERFORM, NASTRAN, DYNAKEY, DYNASEQ, RADIOSS, PAMCRASH, MARC, ANSYS, ABAQUS, ABAQUS2D, MADYMO OPTISTRUCT, ABAQUS, NASTRAN
For shape optimization with HyperOpt/Generic and HyperStudy
HYPEROPT
Ignored
For shape optimization with HyperOpt/OPTISTRUCT, HyperOpt/ABAQUS, and HyperOpt/NASTRAN
Altair Engineering
After AutoDV runs, it creates the following files: prefix.dat A bulk data file that contains the DVGRID and LOAD information, respectively depending on opt2. A bulk data file for the perturbed model corresponding to the shape variable nnn. This file originally contained the manually generated perturbed file. After the program runs, this file contains only the GRID data for all perturbed grid points. This file contains the shape design variables in the HyperMesh results format. This file can be loaded to HyperMesh and results can be viewed. Note: The animation should be used only as a check for the shape of the perturbation vector. It will not display the upper and lower bounds for the shape variable. The file prefix.dat becomes part of an input file for the respective native analysis package. Note: If you create a perturbed model file, prefix.pertnnn, and also a set of control perturbations with an identical shape variable ID, nnn, the resultant perturbation vector from AutoDV is a union of the manual as well as the interpolated grid perturbations. For the common nodes in the two sets, the manual grid perturbations given in prefix.pertnnn override those generated by using interpolation. prefix.subcode.node.tpl Templex template to replace the nodal coordinates in the original input deck. Generated if opt1 = HYPERSTUDY, or TEMPLEX. Contains nodal coordinates and perturbation vectors for use in the file, prefix.subcode.node.tpl. Generated if opt1 = HYPERSTUDY, or TEMPLEX.
prefix.autonnn
prefix.dv.animate
prefix.shp

Altair Engineering
Creating an H3D File from HyperMesh

Using an H3D file, you can save 3-D animations from HyperMesh in the .h3d format for viewing with the HyperView Player. HyperView Player is an Internet browser plug-in for visualizing 3-D Computer Aided Engineering (CAE) models and results. Using product data in Altair's compact .h3d format allows you to incorporate animated images in an HTML document for presentation or engineering reports. Simulation results can be sent by e-mail, or placed on the web for others to open and review. HyperView Player is available as a free download on Altair's Web site at http://www.altair.com. To create an H3D file from HyperMesh: 1. 2. Select one of the following panels: contour, deformed, hidden line, transient, or geom cleanup. To control the display attributes for your model: 3. Specify your desired display attributes using visual options or the visual panel.
Click the Hyper3d button or H3D>HV. Two files are created. One is an H3D file, using anim#.h3d as the file name. The symbol # is automatically assigned to the H3D file. The other is a sample HTML file including an <EMBED> statement for the corresponding H3D file. H3D>HV loads the newly created H3D file into HyperView. You can define this option in the options panel under modeling.
4.
To review the model in a web browser: Double click the HTML file to launch a browser. or Click H3D to activate the standalone HyperView Player.
You can customize the external HTML template, h3d_template.html, located in the altair/hm/html directory, to suit your needs. Note: In the HyperMesh geom cleanup panel, the Hyper3D button is displayed when you select the shaded option in the visual options subpanel.
Altair Engineering
Embedding a HyperView Player Object in HTML Documentation The following section defines the arguments and provides an example for embedding statements in an HTML document in order to view a HyperView Player graphic object. Note the following updates to HyperView Player: Simplified HTML File Statement Since the H3D file created from HyperView, and HyperMesh includes scene information, the arguments in the old statements for model readers and result readers are no longer needed. The HTML statements have been simplified in this release. However, the HTML files created for HyperView Player 3.1 are still supported. HyperView Player only supports H3D direct readers. You can create an H3D file using: Note HyperView HyperMesh HyperMesh result translators, such as hmnast, hmnasto2, hmdyna, hmradioss, hmpam, hmansys, and hmabaqus OptiStruct You may need to modify your HTM L files created for HyperView Player 3.1 if you were using direct readers other that h3d.dll, such as adams.dll, gfile.dll, lsdyna.dll, and madymo.dll, since those readers are no longer supported in HyperView Player.
Direct Readers
To embed a HyperView Player object, the <EMBED> statement in HTML is used. All arguments are case insensitive.
General Arguments for EMBED Statements

type width/height SRC="URL" Application/x-h3d Measured in pixels The location of the plug-in data file as indicated by its URL.
Embedded Statement Example

<EMBED type="application/x-h3d" width=450 height=400 src="HTTP:\\www.altair.com\h3d\bumper.h3d"> <EMBED type="application/x-h3d" width=450 height=400 src="../bumper.h3d">
More examples can be found in the HyperView Player demo directory, and our Web site, http://www.altair.com.

Altair Engineering
Using an HTML File

You can use HyperView Player to share information by embedding it in an HTML file. You can use either a relative path or a standard Uniform Resource Locator (URL) to specify the path for the H3D file in the <EMBED> statement. There are three different ways to define file transfer protocol: FILE, HTTP and FTP. This section describes how to select a protocol for file transfer using files, anim1.html and anim1.h3d as examples.
Embedded Mode
FILE://
Example: <EMBED type="application/x-h3d" width=450 height=400 SRC="File://c:\Altair\demos\hvp\anim1.h3d"> An absolute path is required for File:// and the H3D file must reside in the specified path. When you distribute the files, you may need to modify the HTML file for the path.
HTTP://
Example: <EMBED type="application/x-h3d" width=450 height=400 SRC="http://www:8080/~John/anim1.h3d> Others can access your public web area on the Internet. When sharing an H3D file, you can place the anim1.html and anim1.h3d files in your public HTML directory and send the link to others in the company by email. The link can be, for example, http://www:8080/~John/anim1.html. By doing this, you do not need to distribute the H3D file and can guarantee the path is working correctly. If you have HyperView Player installed, and you click the link in the email, the model will be displayed.
FTP://
Example: <EMBED type="application/x-h3d" width=450 height=400 SRC="FTP://ftp.altair.com/pub/outgoing/HVP/anim1.html> You can place the anim1.html and anim1.h3d files on your FTP site. If you have HyperView Player installed, and you click ftp://ftp.altair.com/pub/outgoing/HVP/anim1.html, the model is displayed.
Relative Path
Example: <EMBED type="application/x-h3d" width=450 height=400 SRC="../anim/.h3d> Using a relative path allows you to distribute an HTML file easily. You can create a folder with the necessary HTML and h3d files for distribution.
Altair Engineering
Full page mode

In an HTML file, you can easily hyperlink a string to an H3D file. When you click the hyperlink, the plug-in loads a model in full-page mode.
Using E-mail
You can attach an H3D file to an email. If the recipient is using a PC, he or she can click the attachment and the H3D file will load automatically. You can also save the H3D file and at a later time, double-click the file to invoke the standalone version of HyperView Player. Another available option is to drag the H3D file and drop it into a browser to view the model in a full window.

Altair Engineering
H3D FAQ's
How can I view a model with shaded display in HyperView Player? The model display settings are recorded during H3D creation. Set up the desired model display, with such options as mesh lines and feature lines, in the Vis panel under the Performance Graphics mode in HyperMesh.
Why doesnt the legend setting in HyperView player reflect the setting in HyperMesh? HyperView Player only supports default settings for the legend display from HyperMesh. The specified Max and Min values in HyperMesh are not recorded in the H3D file of this version.
Can I view complex result animation in HyperView player? No, the H3D writer does not support complex result data.
What types of element are not supported in the H3D file? Second order elements, rigidlinks, and RBE3s are not supported in this version. The mid-side node of a second order element is ignored when it is read into HyperView Player.
How can I change the window size for viewing HyperView Player in the browser? You can modify the width and height values in the <EMBED> statement in the HTML file. (For example, width = 600, height = 600)
Altair Engineering
Free Body Diagrams

HyperMesh allows you to create or edit Free Body Diagrams (FBD) using several tools that display in the tab area. Each FBD tool displays on a separate tab, which opens when you activate that tool. Location: Results menu, Free Body Diagram sub-menu (to access the tools) Tool menu (to access the FBD Set Manager only) Tab Area (for the tools themselves)
Free Body Diagram (FBD) utilities facilitate the extraction and post-processing of Grid Point Force (GPFORCE) results. FBD utilities currently support OptiStruct and Nastran .op2 files, and are only available in the OptiStruct or Nastran user profiles. FBD extractions are typically utilized for breakout and/or sub-modeling analysis schemes, where balanced free body sub-cases are extracted from a coarse grid model and applied to a fine grid sub-model for eventual optimization and/or analysis. FBD is also used to extract cross-sectional resultant forces and moments (typically at the centroid of a cross-section) for use in traditional strength calculations. Each tool has a separate entry in the menu. In addition, see the overview on Grid Point Force Balance tables to gain further understanding of FBD operations within HyperMesh, while the Set Manager utility assists in generating the element and node sets which the FBD utilities analyze.
This coarse grid model is typical for FBD extractions.
Typical FBD Forces output on a wing rib
Typical Result Force and Moment output on a floor beam

Altair Engineering
FBD Set Manager

Use the Set Manager tool to automate the grouping and display of model components through HyperMesh entity set functionality. Location: Tools menu (to access the Set Manager) Tab Area (to use the Set Manager)
The Set Manager 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. The Set Manager utility is currently supported in the OptiStruct, Nastran, and ABAQUS user profiles. To set display options for the Set Manager: 1. 2. Ensure that you are using the OptiStruct, Nastran, or Abaqus user profile. From the Tools pull-down menu, select Set Manager. The set manager displays in the tab area. 3. Use the toolbar buttons in the Set Manager tab to manipulate the display options, as desired:
Use <ctrl>-click and <shift>-click to select multiple items in the tree structure. The filter buttons allow for additional selection control, including a name filter that uses standard HyperMesh filtering syntax. The selection type options allow you to control the entities (elements, geometry, or export state) that the filter buttons apply to. The sync button synchronizes the entity set display states with the current HyperMesh display. See To synch the Set Manager with the HyperMesh display for details.
Altair Engineering
To use the Set Manager right-click functionality: 1. 2. Ensure that you are using the OptiStruct, Nastran, or Abaqus user profile. From the Tools pull-down menu, select Set Manager. The set manager displays in the tab area. Its tree structure lists all entity set currently existing in the model, grouped in folders by type. 3. 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. The graphic above shows all of the available options, including: New: Create a new entity set of the specified type. HyperMesh prompts you to type in a name for the set or accept a default name. Supported entity set types are shown above. Delete: Deletes the currently selected set(s). Multiple sets may be selected by using standard Ctrl/Shift-click functionality. Rename: Rename the selected set. Delete Reference: Removes a set reference from a entity set type of sets. Collapse All: Collapses all branches of the tree. Expand All: Expands all branches of the tree. Add Entities to Set: Adds entities into the currently selected set. This operation brings up an entity selector in HyperMesh used to select entities to add to the set.

Altair Engineering
Remove Entities from Set: Removes entities from the currently selected set. This operation brings up an entity selector in HyperMesh used to select entities to remove from the set. Show: This operation adds the entities contained in the selected set(s) to the HyperMesh display. Hide: This operation removes the entities contained in the selected set(s) from the HyperMesh display. Show Only: This operation turns off (masks) all currently displayed entities, and then displays only the currently selected set(s) in the HyperMesh display. Display Options: Determines how the sets display in the Set Manager tree. Available options are shown above. 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 HyperMesh entity sets.
To change the Set Manager's display and export states: 1. 2. Ensure that you are using the OptiStruct, Nastran, or Abaqus user profile. From the Tools pull-down menu, select Set Manager. The set manager displays in the tab area. Its tree structure lists all entity set currently existing in the model, grouped in folders by type. 3. The display and export states of entity sets are controlled by clicking on/off the display and export icons located next to each entity set in the tree, or by using the display options icons in the toolbar. The display and export icons associated with each entity set are described below: The display toggle determines whether the entities contained within the entity set are displayed in HyperMesh, and is only available for component and element sets. Once a display toggle is changed, click the Synch toolbar button to update the HyperMesh display with the current selection. For component sets there are two toggles: one for elements (first check box) and one for geometry (second check box), which control the display of each of these entities separately. The Checked State signifies that all entities in the entity set are currently displayed, after clicking either the display or sync buttons. The Blank State signifies that one or more of the entities in that entity set are not displayed, after clicking either the display or sync buttons. The export toggle determines whether the entity set definition is to be exported when the model deck is written. The export state of each entity set is stored in the HyperMesh database. When switching between supported solvers, this information is automatically converted to the new solver format when Set Manager is opened. The Checked State signifies that the entity set will not be exported. The Blank State signifies that the entity set will be exported.
Altair Engineering
To synch the Set Manager with the HyperMesh display: The Set Manager 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 HyperMesh display can introduce performance issues. To remedy these occurrences, the Set Manager utility does not automatically synchronize the display states of entity sets with the current HyperMesh display. Instead, the Display button at the bottom of the Set Manager allows you to update HyperMesh to match the Set Manager settings, while the Synch button in the Set Manager toolbar allows you to update the set manager to match the current state of the HyperMesh display. Export states synch automatically, but display states always default to the unchecked state on startup. In addition, the Display button can be used to update the HyperMesh display to the current Set Manager selection, in which case the Set Manager and the HyperMesh display are synchronized until another selection is made within the Set Manager. The Synch button resides in the toolbar described by the topic To set display options for the Set Manager.

Altair Engineering
FBD Displacements
The FBD Displacements utility extracts displacement data for user defined node set(s), and is useful for doing breakout modeling within a sub-modeling scheme. Location: Results menu, Free Body Diagram sub-menu (to access the tool). Tab Area (for the tool itself)
After you define an element set with an associated node set, all appropriate displacements and rotations are extracted. Results can be output to load collectors in HyperMesh for graphical review, a text summary table within HyperMesh, and a formatted .csv file which can be loaded into traditional spreadsheet software packages. The tool also supports .op2 files containing displacement data from OptiStruct and Nastran. Note: Recommended practice is to output displacement data for the node set(s) of interest only. This procedure reduces the size of the .op2 file and helps speed up the FBD Displacement extractions. Additionally, for Nastran and OptiStruct, consider using STRESS = NONE to further reduce the size of the .op2 file. See the OptiStruct online reference guide for more information regarding STRESS io option card
The FBD Displacement utility is currently supported in the OptiStruct and Nastran user profiles. To extract displacement data for a user-defined node set: 1. 2. Ensure that you are using the OptiStruct or Nastran user profile. From the Results pull-down menu, select Free Body Diagram, then FBD Displacements. The FBD Displacements tab displays in the tab area. 3. Use the .op2 file: field to specify the full path and filename of the .op2 file containing the displacement output for the current model. Clicking on the folder icon opens the standard file selection dialog window for browsing files. Once an .op2 file is selected, sub-case names and IDs with displacement output are saved with the rest of the HyperMesh database for use with all FBD utilities. If a new .op2 file is required, or if the original .op2 file changes, you must load the new .op2 file into the database (overwriting the previously selected one).
4.
Select a sub-case. This lets you specify from which sub-case(s) to extract displacement information. Only sub-cases with displacement results from the currently selected.op2 file display for selection. You can select multiple sub-cases by ctrl-clicking or shift-clicking. Filter buttons allow for additional selection control, including a name filter that uses standard HyperMesh filtering syntax. The sub-case display can be switched between ID and Name (ID). The ID option lists the sub-cases as SUB-CASE #. The Name (ID) option lists the sub-case as SUBTITLE - LABEL(ID). If no SUBTITLE exists, only the LABEL is used. See the OptiStruct online reference guide for more information regarding SUBTITLE and LABEL sub-case information cards.
Altair Engineering
5.
Select entities. The entity selection section allows you to select and/or create the appropriate entities required to execute the FBD Displacements utility. There are several options: The Element Set selector defines the elements that contain the nodes at which displacement data will be extracted. The Set Manager utility on the Tools menu can be used to create the necessary element sets. The Node Set selector defines the nodes at which displacement data will be extracted. Only the nodes contained within the selected node set will be part of the extraction. If a node set is not selected, then all nodes within the element set are used. The Auto find interface nodes option automatically finds the nodes attached to elements that are not contained within the currently selected element set. This procedure selects the nodes interfacing with the remainder of the structure. You will be prompted to give the newly created node set a name. Additional nodes may be added to the node set once it is created by clicking the Node Set selector and picking additional nodes. The Show model checkbox is a graphical review option that, when checked, automatically displays the entire model in transparency mode and highlights the currently selected element and node sets. This functionality allows you to verify which element and node sets are currently selected.
6.
Choose Output options: The Output options section contains various options to review and display results of FBD Displacement extractions. The Coordinate System selector determines the coordinate system used to display the nodal coordinates (x,y,z) in the summary table and .csv file output options. Displacement data (Ux, Uy,) is always output in the system that the results are stored with in the .op2 file format. Results coordinate system transformations are not performed on displacement data. The FBD Displacement utility extracts and applies the displacement and rotation results from the .op2 file in the output coordinate system without any further coordinate system transformations. It is assumed that the output coordinate system assigned to each node in the HyperMesh database matches that used to run the analysis and generate the .op2 file. Output coordinate systems are defined in HyperMesh by accessing the Systems panel. On the Setup menu, click Coordinate Systems, and toggle to the assign sub-panel, select the required nodes and a coordinate system, and click Set Analysis. In OptiStruct and Nastran this operation sets the CD field on the GRID card(s). See the OptiStruct online reference guide for more information regarding the GRID bulk data card. If the output coordinate systems for each node in the HyperMesh database does not match those used to run the analysis then the extracted values will be incorrect. Situations when this behavior could occur include modification of nodal output system within HyperMesh without rerunning the analysis and/or loading a results file that does not match the currently loaded model. If a coordinate system is not specified, the HyperMesh base system is used by default. The Zero Tolerance entry defines the cut-off point below which a result quantity is considered zero. All calculations are done with float point precision and the zero tolerance value is only used for controlling the output of results to the various formats. The option helps to eliminate relatively small values from being output to the result formats. To maintain float precision the default is set to 1.0e-6, otherwise modify the value as desired.

Altair Engineering
The Create Load Collectors option will extract the specified displacement data and display it in organized load collectors within HyperMesh for graphical visualization within the model window5. A single load collector, for the current element and node set, is created for each sub-case. The load collector name format is FBDD_E(#)_N(#)_S(#)_Disp. For example, FBDD_E(1)_N(1)_S(1)_Disp would be created for element set 1, node set 1 and sub-case 1. The loads in this load collector are created with the SPC load type. This collector can be referenced as the SPC in the sub-case panel. The Create SPCD option will additionally create a load collector with the name FBDD_E(#)_N(#)_S(#)_SPCD. Loads in this collector are created with the SPCD load type. This collector can be referenced as the LOAD in the sub-case panel. The Color option allows you to choose a color for all created load collectors. This color can be modified later using either the HyperMesh interface or the FBD Results Manager utility.
The Show summary table option outputs the results to a popup window for instant review. The table contains information about the sub-cases, element and node set(s), and detailed displacement data at each node. A sample window with partial output is shown below.
The Create .csv file option creates a .csv file that contains the same information as the summary table, but in a comma-separated file. You may select a new file or an existing file. If an existing file is selected there are several items to note: If the data you are extracting already exists in the file (based on element set, node set and sub-case IDs), the existing block will be overwritten with the new data. If it does not exist, it will be appended to the end of the file. IN any case, you will be warned that the File already exists and asked if you want to replace it. Selecting yes will not overwrite the file; it will append/replace the data.
Altair Engineering
FBD Forces
The FBD Forces utility extracts grid point force (GPFORCE) data (including forces and moments) for a user-defined element set, and is useful for doing breakout modeling within a sub-modeling scheme. Location: Results menu, Free Body Diagram sub-menu (to access the tool). Tab Area (for the tool itself)
Results can be output to load collectors in HyperMesh for graphical review, a text summary table within HyperMesh, and/or a formatted Comma-Separated Values (.csv) file which can be loaded into traditional spreadsheet software packages. The tool supports .op2 files containing GPFORCE data from OptiStruct and Nastran. The FBD Forces utility is currently supported by OptiStruct and Nastran user profiles Note: Recommended practice is to output GPFORCE data for the element set(s) of interest only. This procedure reduces the size of the .op2 file and helps speed up the FBD Forces extractions. Additionally, for Nastran and OptiStruct, consider using STRESS = NONE and/or DISPLACEMENT = NONE options to further reduce the size of the .op2 file. See the OptiStruct online reference guide for more information regarding STRESS and DISPLACEMENT io option cards
The FBD Forces utility is broken down into three major sections, each of which corresponds with the process order of using the tool. To select a results file: Click on the folder icon inside of the op2 file field. This opens the standard file selection dialog window; use this to browse to and select the desired .op2 file. The op2 file field accepts the full path and filename of the .op2 file that contains the GPFORCE output for the current model. Once youve selected an op2 file, sub-case names and IDs with GPFORCE output are saved to the HyperMesh database for use with all FBD utilities. The sub-case name and ID information is retained within the HyperMesh database once saved. If a new .op2 file is required (or if the original .op2 file changes) you must load the new .op2 file into the database, overwriting the previously selected. To select a sub-case: The Sub-case section lets you specify from which sub-case(s) to extract GPFORCE information. Sub-cases with GPFORCE results from the currently selected.op2 file are displayed for selection only. Multiple sub-cases can be selected via Ctrl-click or Shift-click functionality. Filter buttons allow for additional selection control as shown including a name filter that uses standard HyperMesh filtering syntax. The sub-case list can be switched between ID and Name (ID). The ID option lists the sub-cases in the format SUBCASE #. The Name (ID) option lists the sub-case in the format SUBTITLE LABEL (ID). If no SUBTITLE exists, only the LABEL is used. See the OptiStruct online reference guide for more information regarding SUBTITLE and LABEL sub-case information cards.

Altair Engineering
To select entities: 1. Use the Element Set selector to define the elements that make up the free body and contain the nodes at which GPFORCE data will be extracted. The Set Manager tool on the Tools menu can be used to create the necessary element sets. 2. Use the Result System selector to define the coordinate system into which the grid point force and moment result vectors are transformed and output. If a results system is not specified, the HyperMesh base system is used by default. The FBD Forces utility extracts grid point force and moment results from an .op2 file in the output coordinate system in which the solver output these results. HyperMesh assumes that the output coordinate system assigned to each node in the HyperMesh database matches that used to run the analysis and generate the .op2 file. Output coordinate systems are defined in HyperMesh by accessing the Systems panel. On the assign sub-panel, select the required nodes and a coordinate system, and click Set Analysis In OptiStruct and Nastran this operation . sets the CD field on the GRID card(s). (See the OptiStruct online reference guide for more information regarding the GRID bulk data card.) If the output coordinate systems for each node in the HyperMesh database do not match those used to run the analysis, the extracted values will be incorrect. This could occur when modifying a nodal output system within HyperMesh without rerunning the analysis and, or when loading a results file that does not match the currently loaded model. In addition, results coming from, or output to, cylindrical or spherical result coordinate systems should be inspected for validity near the origin and along principal axes. 3. Use the Summation Node selector to define the node about which the GPFORCE data is summed for the selected element set. This is useful for verifying free body behavior through zero-sum values for all force and moment components about any node. It is also useful for calculating the result of applied or reaction forces about any node. If a node is not selected, the HyperMesh origin (0,0,0) is used by default. 4. Activate the Show Model checkbox to automatically display the entire model in transparency mode while highlighting the currently selected element set, result system and summation node. This allows you to verify which element sets is currently selected.
To specify output options: 1. Use the FBD type selector to determine the grid point force and moment data to extract and utilize for FBD calculations for each node in the selected element set. Available options include All Loads, Applied Loads Only, and Reaction Loads Only. All Loads extracts and utilizes all element contribution, applied, SPC, and supported MPC grid point data for FBD calculations on the nodes in the selected element set. Applied Loads Only extracts and utilizes only the applied loads grid point data for FBD calculations on the nodes in the selected element set. Reaction Loads Only extracts and utilizes only SPC and supported MPC grid point data for FBD calculations on nodes in the selected set.
MPC force and moment data are properly extracted for the following MPC constraint types: RBE2, RBE3, Rigidlink, RJOINT, RROD, and RBAR.
Altair Engineering
2.
Use the Zero Tolerance entry field to define the cut-off point below which a result quantity is considered zero. All calculations are performed with floating point precision and the zero tolerance value is only used to control the output of results to the various formats. This option helps to prevent relatively small values from being output to the result formats. To maintain floating-point precision the default is set to 1.0e-6; modify the value as desired.
3.
Use the Create Load Collectors option to extract the specified grid point data and display it in organized load collectors within HyperMesh for visualization in the model window. HyperMesh creates multiple load collectorsone for each force and moment componentfor each selected sub-case of the current element set. The load collector name format is FBDF_E(#)_S(#)_(compID). For example FBDF_E(1)_S(1)_Fx would be created for element set 1, sub-case 1, and component Fx. In addition a load collector with the Nastran/OptiStruct LOAD card is also created, referencing the component force and moment load collectors. This load collector is named FBDF_E(#)_S(#)_C and can be referenced in the sub-case panel as the LOAD entry for the various sub-case definitions. The Color option allows you to choose a color for all created load collectors. This color can be modified later using either the HyperMesh interface or the FBD Results Manager utility.
The FBD Results Manager tool can be used to review the load collectors generated from FBD Forces utility. When you save the HyperMesh database, all FBD Forces load collectors are saved to the database. This allows FBD information to be reviewed and utilized in the future without having to rerun the tool. Renumbering element or node sets after running the tool invalidates the link between the load collector names and the associated sets; therefore it is important to avoid renumbering any element or node sets for which FBD result must be retained as load collectors in HyperMesh 4. To output the results to a popup window for instant review, activate the Show summary table option. The table contains information about the sub-cases, element set(s), and detailed data from the grid point extraction at each node. A sample window with partial output is shown below.
5.
Use the Create .csv file option to create a .csv file that contains the same information as the summary table, but in a comma-separated file. You may select a new file or an existing file. If an existing file is selected, it is appended to, and there are several items to note: If the data you are extracting already exists in the file (based on element set, sub-case IDs), the existing block will be overwritten with the new data. If it does not exist, it will be appended to the end of the file. HyperMesh will ask if you wish to replace the existing file. However, selecting yes will not overwrite the fileit will append/replace the data as described above. Altair Engineering

FBD Cross-section manager

The FBD Cross-section Manager (CSM) utility creates and manages cross-section definitions that are used within the Resultant Force & Moment utility. Location: Results menu, Free Body Diagram sub-menu (to access the tool). Tab Area (for the tool itself)
This utility contains tools for defining cross-sections, which are defined by an element set, node set, summation node, and a local result coordinate system. It also features semi-automatic generation of element and node sets for defining cross-sections. The FBD Cross-section Manager utility is currently supported by the OptiStruct and Nastran user profiles. The FBD Cross-section Manager interface has two creation methods available for cross-section definition: manual and (semi-) automatic. The Advanced options section provides the means to semi-automatically create cross-section element and node sets for beam-like structures with regular meshes. This auto-create cross-section capability requires a continuous mesh with rows of nodes (of any orientation) to work properly. The mesh shouldnt have any discontinuities (holes, gaps, etc) and must have identifiable rows of nodes, starting from the selected nodes and progressing along the length of the selected elements. To define a cross-section manually: 1. Use the Element Set selector to specify the elements containing the nodes that define the crosssection. The Set Manager tool on the Tools menu can be used to create the necessary element sets. If multiple element sets are selected, each set is added to the table as a separate cross-section definition which can be modified later by selection. 2. Use the Node Set selector to define the nodes in each currently selected element set at which grid point data will be extracted and summed from. Only the nodes contained within the selected node set will be part of the grid point extraction. Use the Set Manager tool on the Tools menu to create the necessary node sets. If multiple node sets are selected for a single element set, HyperMesh adds separate crosssection definitions to the table with the original element set and each selected node set. 3. Use the Summation Node selector to define the node about which the grid point data will be summed. If no node is selected, the utility defaults to Centroid. This option calculates the nodal averaged centroid of the coordinates of all of the nodes in the node set and creates a temporary node at that location. When using the Centroid option, a temporary node is created. If this node is deleted from the model, the loads associated with that node are also deleted. 4. Use the Result System selector to define the coordinate system into which the grid point vector results will be transformed and output. If a results system is not specified, the HyperMesh base system is used by default. 5. The Display sections checkbox is a graphical review option that, when checked, displays the element set, node set, result system and summation node which define the cross-section in the graphics display area.
Altair Engineering
6.
Optional: activate the Show model checkbox. This displays the entire model in transparency mode, highlighting the currently selected element set, node set, result system and summation node. This allows you to verify a cross-section definition.
7.
Optional: use the filter buttons on the top of the spreadsheet to select which cross-sections are required. Standard Ctrl/Shift click functionality can be used to select cross-sections. Selected crosssections can also be deleted from the database by using the Remove selection button on the right end of the filter buttons.
Comments Each time a cross-section is created, modified, or deleted, the cross-section data is saved to the HyperMesh database. When the HyperMesh database is saved, all cross-section definitions are also saved. Therefore, cross-section definitions only need to be defined once and stored in the HyperMesh database. Cross-Sections can then be accessed from within the Resultant Force and Moment utility, which utilizes the cross-section definitions to perform these calculations. Renumbering element or node sets after running the tool invalidates the link between the crosssection names and the associated sets. Therefore, it is important to avoid renumbering any element or node sets for which cross-sections are to be retained within HyperMesh database. To define a cross-section automatically: 1. 2. Use the Elements selector to choose the elements that define the entire beam-like component from which cross-sections will be generated. Use the Nodes selector to pick nodes for the first node set (i.e. first cross-section). These nodes should be at one end of the beam. 3. 4. Optional: activate the Show model checkbox to automatically display the entire model in transparency mode, highlighting the currently selected elements and nodes. Type a prefix for the name of each generated element set into the Element set prefix field. For example, you type in ESET each element set will be named ESET [#], where # increases with each new set generated. 5. Type a prefix for the name of each generated node set into the Node set prefix field. For example, you type in NSET each element set will be named NSET [#], where # increases with each new set generated. 6. Type a Numbering offset into the text box. This is the offset value for generated set names. By default, the offset value is zero and HyperMesh generates numbered set names starting with one. If the offset value is set to a value greater than zero, the generated set names are numbered starting from that value. 7. Optional: activate the sets accumulate option This determines whether each progressive set also contains the elements from the previous set, or only the new row of elements. If checked, each element set will contain the elements from the previous set.

Altair Engineering
FBD Resultant Force and Moment

The Resultant Force and Moment (RF&M) utility extracts grid point force (GPFORCE) data for user defined cross-sections created via the Cross-section Manager. Location: Results menu, Free Body Diagram sub-menu (to access the tool). Tab Area (for the tool itself)
The resultant force and moment utility generates input data for shear and moment (VMT) diagrams and/or to perform load-case screening with Potato plots in HyperView. Two utilities available within HyperGraph also interact with data generated from the Resultant Force and Moment utility. Results can be output to load collectors in HyperMesh for graphical review, a text summary table within HyperMesh, and/or a formatted .csv file which can be loaded into traditional spreadsheet software packages. The tool supports .op2 files containing grid point force data from OptiStruct and Nastran. Note: Recommended practice is to output GPFORCE data for the element set(s) of interest only. This procedure reduces the size of the .op2 file and helps speed up the Resultant Force and Moment extractions. Additionally, for Nastran and OptiStruct, consider using STRESS = NONE and/or DISPLACEMENT = NONE options to further reduce the size of the .op2 file. See the OptiStruct online reference guide for more information regarding STRESS and DISPLACEMENT io option cards.
The Resultant Force and Moment utility is currently supported by the OptiStruct and Nastran user profiles. To select a results file: Use the .op2 file field to specify the full path and filename of the .op2 file containing the desired GPFORCE output for the current model. Clicking on the folder icon opens the standard file selection dialog window for browsing files. When an .op2 file is selected, sub-case names and IDs with GPFORCE output are saved to the HyperMesh database for use with all FBD utilities. The sub-case name and ID information is retained within the HyperMesh database once saved. If a new .op2 file is required, or if the original .op2 file changes, you must load the new .op2 file into the database, overwriting the previously selected. To select a sub-case: Select the desired sub-case(s) from the list in the sub-case section. The sub-case section lets you specify from which sub-case(s) to extract GPFORCE information. Sub-cases with GPFORCE results from the currently selected.op2 file display for selection only. Multiple sub-cases can be selected by Ctrl-clicking and Shift-clicking. The list can be filtered using the buttons provided, including a name filter that uses standard HyperMesh filtering syntax. The subcase list can be organized by ID or Name (ID). The ID option lists the sub-cases as SUBCASE #. The Name (ID) option lists the sub-case as SUBTITLE LABEL (ID). If no SUBTITLE exists, only the LABEL is used. See the OptiStruct online reference guide for more information regarding SUBTITLE and LABEL sub-case information cards.
Altair Engineering
To select a cross-section: Pick the desired cross-sections from the list in the cross-sections area of the tab. The Cross-sections section lets you specify the cross-sections from which you wish to calculate resultant force and moment results for each selected sub-case. Cross-sections are created using the Cross-section Manager. Multiple cross-sections can be selected by Ctrl-clicking and Shift-clicking. The list can be filtered using the buttons provided, including a name filter that uses standard HyperMesh filtering syntax. To specify output options: The Output Options section contains various options to review and display the results of Resultant Force and Moment extractions. 1. Use the Coordinate System selector to determine the coordinate system used to output the nodal coordinates (x,y,z) in the summary table, .csv file, and .fbd file output options. Resultant force and moment vector results are always output in the result coordinate system defined for each cross-section. Result coordinate systems for cross-sections are defined using the Cross-section Manager. If a coordinate system is not specified, the HyperMesh base system is used by default. The Resultant Force and Moment utility extracts grid point force and moment results from the .op2 file in the output coordinate system in which the solver output these results. HyperMesh assumes that the output coordinate system assigned to each node in the HyperMesh database matches that used to run the analysis and generate the .op2 file. Output coordinate systems are defined in HyperMesh by accessing the Systems panel. (On the assign sub-panel, select the required nodes and a coordinate system, and click Set Analysis In OptiStruct and Nastran this . operation sets the CD field on the GRID cards). If the output coordinate systems for each node in the HyperMesh database do not match those used to run the analysis, the extracted values will be incorrect. This can occur when modifying nodal output system within HyperMesh without rerunning the analysis, and/or loading a results file that does not match the currently loaded model. In addition, results coming from or output to cylindrical or spherical result coordinate systems should be inspected for validity near the origin and along principal axes. MPC force and moment data are properly extracted for the following MPC constraint types: RBE2, RBE3, Rigidlink, RJOINT, RROD, RBAR. 2. Use the Zero Tolerance field to specify the cut-off point below which a result quantity is considered zero. All calculations are done with float point precision and the zero tolerance value is only used to control the output of results to the various formats. The option helps to eliminate relatively small values from being output. To maintain float precision the default is set to 1.0e-6, otherwise modify the value as desired. 3. Activate the Create Load Collectors checkbox to extract the specified grid point data and display it in organized load collectors within HyperMesh for graphical visualization within the model window. HyperMesh creates multiple load collectorsone for each force and moment componentfor each selected sub-case of the current cross-section, each made up of an element set and node set. The load collector name format is RF&M_E(#)_N(#)_S(#)_(compID). For example RF&M_E(1)_N(1)_S(1)_Fx would be created for element set 1, node set 1, sub-case 1, and component Fx.

Altair Engineering
The Color option allows you to choose a color for all created load collectors. This color can be modified later using either the HyperMesh interface or the FBD Results Manager. You can also use the FBD Results Manager to review the load collectors generated from the Resultant Force and Moment utility. When the HyperMesh database is saved, all resultant force and moment load collectors are saved in the database. This allows resultant force and moment information to be reviewed and utilized in the future without having to rerun the tool. Renumbering element or node sets after running the tool invalidates the link between the load collector names and the associated sets and therefore it is important to not renumber any element or node sets for which resultant force and moment result are to be retained as load collectors in HyperMesh. 4. Activate the Show summary table option to output the results to a popup window for instant review. The table contains information about the sub-cases and cross-sections, and detailed data from the grid point extraction at each node. 5. Activate the Create .csv file option to create a .csv file containing the same information as the summary table, but in a comma separated file. You may select a new file or an existing file. If an existing file is selected, it is appended to. 6. Activate the Create .fbd file option to create a file that can be read into HyperGraph using the Shear and Moment Plot and Potato Plot utilities. You may select a new file or an existing file. If an existing file is selected, it is appended to. Comments When saving over existing .csv or .fbd file, there are several items to note: If the data you are extracting already exists in the file (based on element set, sub-case IDs), the existing block will be overwritten with the new data. If it does not exist, it will be appended to the end of the file. HyperMesh will ask if you wish to replace the existing file. However, selecting yes will not overwrite the file; it will append/replace the data into the file as described above. Two utilities available within HyperGraph interact with data generated from the Resultant Force and Moment utility: Shear and Moment Diagrams (VMT Plots) and Potato Plot. These utilities are accessed from the Free Body Diagrams item within the HyperGraph Utilities menu.
Altair Engineering
FBD Results Manager

Use the FBD Results Manager to graphically review and manage the load collectors generated from all FBD and Resultant Force and Moment utilities. Location: Results menu, Free Body Diagram sub-menu (to access the tool). Tab Area (for the tool itself)
The FBD Results Manager utility is currently supported by the OptiStruct and Nastran user profiles. To review and manage FBD load collectors: 1. Select one or more Element sets. The Entity selection section allows you to select the element set for which to review FBD, Displacement, or Resultant Force and Moment load collector output. You must choose an existing element set for which you wish to the review the FBD, Displacement, and Resultant Force and Moment load collector output. The optional Show model checkbox, when checked, displays the entire model in transparency mode and highlights the currently selected element set. 2. Pick the desired Results type. The Results selection section lets you select the FBD result type to review. Valid types include FBD Displacements, FBD Forces (All Loads), FBD Forces (Applied Loads), FBD Forces (Reaction Loads), and Resultant Force and Moment. Selecting an FBD result type scans the HyperMesh database and updates the Subcases list with available sub-cases for the currently selected element set and result type. 3. Select the desired Sub-cases by clicking on them. Multiple subcases can be selected using standard Ctrl/Shift click functionality. Filter buttons allow for additional selection control as shown including a name filter that uses standard HyperMesh filtering syntax. For FBD Displacements and Resultant Force and Moment Result types, the Results selection interface is modified to include a Node sets selector. This selector lists all of the node sets associated with the currently selected element set and sub-cases. If multiple sub-cases are selected, only the node sets that are common to all of them will be listed. 4. Specify any desired Display options: The Display options section allows you to decide which force and moment components display in the graphics area for the current selection. The Fx, Fy, Fzcheckboxes determine which component/resultant vectors display when you click the Accept button. Grayed-out checkboxes indicate force and moment components or results that cant display for the currently selected element set/sub-case/node sets. These checkboxes are disabled for the FBD Displacements Result type. The Load handles option determines whether to display the load handles. The Label loads option determines whether to display the load labels (vector magnitude values as text next to the vector).

Altair Engineering
The Vector size option allows you to control the display size of the result vectors. Two options are available, Magnitude % or Uniform size, each of which requires a numeric value. Note that these values do not affect the vector magnitudeonly their screen size. The Update load collector color option will recolor the load collectors associated with the current selection to the color selected in the Color option. Click the Color box to pick a different color, if desired.
5.
Click one of the command buttons at the bottom of the tab: The Accept button displays the selected result vectors on in the graphics area. The Delete button deletes the load collectors associated with the current selection. A popup warning tells you what will be deleted and requires you to confirm the deletion. The Reset button clears the graphics area of all result vectors and resets all of the FBD Results Manager entry fields. The Close button closes the FBD Results Manager, removing it from the tab area without displaying any results in the graphics area.
Altair Engineering
FBD Export Manager

The FBD Export Manager exports FBD, Displacement, and/or Resultant Force and Moment load collectors generated by other FBD utilities. After export, the exported data can be used for breakout modeling within a sub-modeling scheme. Location: Results menu, Free Body Diagram sub-menu (to access the tool). Tab Area (for the tool itself)
The FBD Export Manager is currently supported in the OptiStruct and Nastran user profiles. To export FBD, Displacement, or Resultant Force & Moment collectors: 1. 2. 3. Use the Element set selector to specify the set for which you wish to export data. Optional: activate the show model checkbox to display the entire model in transparency mode, highlighting the currently selected element set for review. Choose the results type that you wish to export from the list box. This populates the list of subcases. Click the one(s) that you wish to export to highlight them; use <ctrl>-click or <shift>-click to select multiple results. If you choose FBD Displacements or Resultant Force and Moment as the result type, an additional list of node sets displays. Select the desired node sets in the same fashion as the subcases. 4. 5. Click add to export to add the highlighted results to the export batch. Specify Export options:. If you wish to create sub-cases upon export, click the Create appropriate subcases checkbox and then click the open-folder button in the Output file text box. This opens a standard file browser window that you can use to browse to the desired destination directory and either select an existing file, or type in a name for a new one. This option will also create SUBTITLE and LABEL cards if they are available from the sub-case information within the currently selected .op2 file. In addition, the Results type affects how HyperMesh creates sub-cases: For FBD Forces All Loads; a SUBCASE will be created with LOAD = assigned to the FBDF_E(#)_S(#)_C load collector which references the LOAD card pointing to each component FBDF_E(#)_S(#)_(compID) load collector for the selected sub-case. For FBD Displacements; a SUBCASE will be created with SPC = assigned to the FBDD_E(#)_N(#)_S(#)_Disp load collector for the selected sub-case. If the SPCD option was enabled when creating FBD Displacement loads, LOAD = will also be assigned to the FBDD_E(#)_N(#)_S(#)_SPCD load collector for the selected sub-case. If multiple node sets are selected for export the following will occur: An SPCADD load collector will be created and the appropriate FBDD_E(#)_N(#)_S(#)_Disp load collectors will be assigned to it. The SPC = will reference the newly created SPCADD load collector. If the SPCD option was enabled when creating the FBD Displacement loads, a LOAD load collector will be created and the appropriate FBDD_E(#)_N(#)_S(#)_SPCD load collectors will be assigned to it. The LOAD = will reference the newly created LOAD load collector. If FBD Force and FBD Displacement load collectors from the same sub-case are selected for export, HyperMesh prompts you to select one or the other from which to create the sub-case.

Altair Engineering
6.
Click the appropriate command button at the bottom of the tab: Export executes the export process, meaning that clicking it: Turns off the display of all currently displayed elements, Creates temporary mass elements on the nodes where the selected FBD, Displacement, and/or Resultant Force and Moment loads are displayed, Exports the model with the displayed option, Deletes the temporary mass elements from the current model, and Removes unnecessary header information from the output file.
Reset clears all of the export criteria so that you can start over. Close closes the tab, removing it from the tab area.
Altair Engineering
FBD Grid Point Force Balance

The Grid Point Force Balance table, output from OptiStruct and Nastran with the GPFORCE io options command, is the data around which all FBD-Forces and Resultant Force and Moment utility calculations are performed. See the OptiStruct online reference guide for more information regarding GPFORCE io option cards. Location: Results menu, Free Body Diagram sub-menu (to access the tool). Tab Area (for the tool itself)
Shown below is a sample model which will be used to demonstrate the grid point force calculations that HyperMesh FBD utilities perform.
This model cons ists of two elements, a fixed support on the left end, and a point load on the right end.
The complete GPFORCE table for the above cantilever beam model is presented below. Note that for any given node within the GPFORCE table, several types of entries are possible depending on the forces acting at that node, including: Applied forces and moments SPC forces and moments MPC forces and moments Element forces and moments from elements attached to the node Total summed values for each node, which in turn must sum to zero for the complete GPFORCE table.

Altair Engineering
Altair Engineering
Process The FBD Forces and Resultant Force and Moment utilities use element and node set definitions to define what information to extract and sum from the GPFORCE table. This information is then used to produce free bodies and/or resultant force and moments. FBD Forces The FBD Forces utility uses an element set to define the values to extract from the GPFORCE table. The element set serves several purposes: 1. For FBD types All loads and Applied loads only, all nodes connected to the elements in the element set that have Applied loads will be extracted and utilized in FBD calculations. For FBD type Reaction loads only, applied loads are neither extracted nor utilized in FBD calculations. For FBD types All loads and Reaction loads only, all nodes connected to elements in the element set that have SPC loads will be extracted and utilized in FBD calculations. For FBD types Applied loads only, SPC loads are neither extracted nor utilized in FBD calculations. For FBD types All loads and Reaction loads only, all nodes connected to elements in the element set that have MPC loads will be extracted and utilized in FBD calculations. For FBD types 2 Applied loads only, MPC loads are neither extracted nor utilized in FBD calculations. For all nodes connected to elements in the element set, Element contributions from only those elements which are not a part of the element set will be extracted and utilized in the FBD calculations. Therefore, for any given node, if all element contributions are from elements from within the defined element set, then the node is an internal node and element contributions are not extracted or utilized in FBD calculations. Furthermore, for any given node, if any element contribution is not from one of the defined elements within the element set, then the node is an interface node and element contributions from the elements not a part of the element set are extracted and utilized in FBD calculations.
2.
3.
4.
The following example of FBD-Forces extraction uses an element set defined with only element: The element set contains only element 1. Element 1 has nodes 1, 2, 3 and 4. Fx calculation, looping through all the nodes attached to elements in the element set: a. Node 1 i. Applied loads: Zero ii. SPC loads: Fx component exists (2.121e+03) and is extracted iii. MPC loads: Zero iv. Element contributions: element 1 is the only element contribution to node 1 and element 1 exists in element set so Fx contribution is not considered. v. Total FBD Value at Node 1 = 2.121e+03 b. Node 2 i. Applied loads: Zero ii. SPC loads: Fx component exists (-2.121e+03) and is extracted iii. MPC loads: Zero iv. Element contributions: element 1 is the only element contribution to node 2 and element 1 exists in element set so Fx contribution is not condered. v. Total FBD Value at Node 2 = -2.121e+03

Altair Engineering
c.
Node 3 i. ii. iii. iv.
d.
v. Node 4 i. ii. iii. iv.
Applied loads: Zero SPC loads: Zero MPC loads:Zero Element contibutions: element 1 and 2 contribution to node 3. Since only element 2 is not in the element set, only element 2 Fx component is extracted (-1.085e+03) Total Fx Value at Node 3 = -1.085e+03
e.
Applied loads: Zero SPC loads: Zero MPC loads:Zero Element contibutions: elements 1 and 2 contribute to node 4. Since only element 2 is not in the element set, only element 2 Fx component is extracted (1.085e+03) v. Total Fx Value at Node 4 = 1.085e+03 Sum all nodes in Fx = 0.0 (ie. Fx component satisfies free body requirements)
Fy, Fz, Mx, My, Mz calculations follow similar procedures. The final FBD-Forces results are presented in the summary table output from the FBD-Forces utility, illustrated in the screenshot below. Notice that the sum of all components is zero about any point in the model. This verifies that the FBD-Forces extraction is indeed a free body. Note that the sum of the moment components (Mx, My, Mz) is not the direct sum of all nodes as the (rXF) terms for the force resultant vector about the sum point must also be added to each moment component appropriately. The sum of the forces components (Fx, Fy, Fz) for each node, however, is the simple sum.
Altair Engineering
Resultant Force and Moment The Resultant Force and Moment utility uses an element set and a node set (cross-section definition) define the values to extract from the GPFORCE table. The cross-section definition serves several purposes: 1. 2. 3. 4. 5. All nodes in the node set must be attached to one or more elements in the element set. All nodes in the node set that have Applied loads will be extracted and utilized in Resultant Force and Moment calculations. All nodes in the node set that have SPC loads will be extracted and utilized in Resultant Force and Moment calculations. All nodes in the node set that have MPC loads will be extracted and utilized in Resultant Force 2 and Moment calculations . For all nodes in the node set, Element contributions from only those elements which are not a part of the element set of the cross-section definition will be extracted and utilized in the Resultant Force and Moment calculations.
The following example of Resultant Force and Moment extraction uses a cross-section definition given by an element set defined with only element 1, a node set defined with nodes 3 and 4, summation node set to node 3, and result coordinate system as the HyperMesh base system: The element set contains only element 1. The node set contains nodes 3 and 4. Fx calculation, looping through all the nodes in the node set: a. Node 3 i. Applied loads: Zero ii. SPC loads: Zero iii. MPC loads:Zero iv. Element contibutions: element 1 and 2 contribution to node 3. Since only element 2 is not in the element set, only element 2 Fx component is extracted (-1.085e+03) v. Total Fx Value at Node 3 = -1.085e+03 b. Node 4 vi. Applied loads: Zero vii. SPC loads: Zero viii. MPC loads:Zero ix. Element contibutions: elements 1 and 2 contribute to node 4. Since only element 2 is not in the element set, only element 2 Fx component is extracted (1.085e+03) x. Total Fx Value at Node 4 = 1.085e+03 c. Sum nodes in node set in Fx = 0.0 Fy calculation, looping through all the nodes in the node set: a. All values are zero in this model.

Altair Engineering
Fz calculation looping through all the nodes in the node set: a. Node 3 xi. Applied loads: Zero xii. SPC loads: Zero xiii. MPC loads:Zero xiv. Element contibutions: element 1 and 2 contribution to node 3. Since only element 2 is not in the element set, only element 2 Fz component is extracted (6.426e+02) xv. Total Fz Value at Node 3 = 6.426e+02 b. Node 4 xvi. Applied loads: Zero xvii. SPC loads: Zero xviii. MPC loads:Zero xix. Element contibutions: elements 1 and 2 contribute to node 4. Since only element 2 is not in the element set, only element 2 Fz component is extracted (3.574e+02) xx. Total Fz Value at Node 4 = 3.574e+02 c. Sum nodes in node set in Fz = 1.000e+03 (The value of the applied shear) Mx calculation, looping through all the nodes in the node set: a. All values are zero in this model. My calculation, looking through all the nodes in the node set: a. Node 3 xxi. Applied loads: Zero xxii. SPC loads: Zero xxiii. MPC loads:Zero xxiv. Element contibutions: element 1 and 2 contribution to node 3. Since only element 2 is not in the element set, only element 2 Fz component is extracted (-8.871e+00) xxv. Total My Value at Node 3 = -8.871e+00 b. Node 4 xxvi. Applied loads: Zero xxvii. SPC loads: Zero xxviii. MPC loads:Zero xxix. Element contibutions: elements 1 and 2 contribute to node 4. Since only element 2 is not in the element set, only element 2 Fz component is extracted (-1.024e+00) xxx. Total Fz Value at Node 4 = -1.024e+00 c. Calculate the cross-product of all the forces about the Y-axis at node 3. Selecting node 3 as the summation node (any node in the model can be selected) and performing rXF (all element edge lengths are 0.166) the following is obtained: xxxi. Node 3: no additional rXF contributions since it is the sum point xxxii. Node 4: rXF for My component equates to the following equation (rz*Fx) + (rx*Fz) = (-0.166*1.085e+03) + (0.0*3.574e+02) = -1.808e+02 xxxiii. Total rXF Value summed at Node 3 = -1.808e+02 d. Sum nodes in node set and all rXF terms in My = -2.000e+02.
Altair Engineering
Mz calculation, looping through all the nodes in the node set a. All values are zero in this model.
The final Resultant Force and Moment results are presented in the graphic below, which is the summary table output from the Resultant Force and Moment utility, for a cross-section defined with element 1 (element set), nodes 3 and 4 (node set), summation node set to node 3, and result coordinate system as the HyperMesh base system.
FBD Displacements The FBD Displacements utility uses an element set and a node set to define the values to extract from the Displacement table. The element and node sets serve several purposes: 1. 2. All nodes in the node set will have displacement and rotation values extracted. The element set is for visualization and breakout modeling purposes only.
Additional Information: Recommended practice is to output GPFORCE data for the element set(s) of interest only. This procedure reduces the size of the .op2 file and helps speed up the FBD Forces extractions. Additionally, for Nastran and OptiStruct, consider using STRESS = NONE and/or DISPLACEMENT = NONE options to further reduce the size of the .op2 file. See the OptiStruct online reference guide for more information regarding STRESS and DISPLACEMENT io option cards. MPC forces and moments are properly extracted for the following MPC constraint types: o RBE2 o RBE3 o Rigidlink o RJOINT o RROD o RBAR The GPFORCE and Displacement results are extracted of the .op2 file in float point precision in binary format. This maintains the integrity of the calculations as well as enhances the performance of the utilities.

Altair Engineering

HyperMesh 8.0 User&#39;s Guide

Cargado por

Información del documento

Derechos de autor

Formatos disponibles

Compartir este documento

Compartir o incrustar documentos

Opciones para compartir

¿Le pareció útil este documento?

¿Este contenido es inapropiado?

Copyright:

Formatos disponibles

HyperMesh 8.0 User&#39;s Guide

Cargado por

Copyright:

Formatos disponibles

HyperMesh 8.

Altair Engineering Contact Information

support@altairtorino.it support@altairjp.co.jp support@altair.co.kr support@altair.se support@uk.altair.com br_support@altair.com anzsupport@altair.com anzsupport@altair.com

Trademark and Registered Trademark Acknowledgments

HyperMesh 8.0 Users Guide

HyperMesh Database and Environment

HyperMesh 8.0 Users Guide i

Automatic 2-D Mesh Generation

HyperMesh 8.0 Users Guide iii

HyperMorph and Morphing Strategies

Calculating Beam Properties

HyperLaminate and Composites

iv HyperMesh 8.0 Users Guide

Finite Difference Module

Post-Processing and XY Plots

HyperMesh 8.0 Users Guide v

Free Body Diagrams

vi HyperMesh 8.0 Users Guide

Hardware and Operating Systems

Notes for PC Users

HyperMesh 8.0 Users Guide 1

Starting HyperMesh in UNIX

2 HyperMesh 8.0 Users Guide

HyperMesh 8.0 Users Guide 3

4 HyperMesh 8.0 Users Guide

Starting HyperMesh Batch Version

HyperMesh 8.0 Users Guide 5

-e<filename> <filename> -mmouse.msf -nobg -nocommand -psdhm

-templex -t<filename> -titlepause

6 HyperMesh 8.0 Users Guide

HyperMesh 8.0 Users Guide 7

8 HyperMesh 8.0 Users Guide

Configuration File Commands

HyperMesh 8.0 Users Guide 9

10 HyperMesh 8.0 Users Guide

*quatrotate(0.000230328525,0.00100703597,0.00106667981,0.9 99998898) *quatrotate(-0.00263644785,0.000327769044,0.000395387048,0.999996393) *dynamicviewend()

5.964252, -3.030465, 2.583235, 0.886445,

HyperMesh 8.0 Users Guide 11

12 HyperMesh 8.0 Users Guide

HyperMesh 8.0 Users Guide 13

14 HyperMesh 8.0 Users Guide

HyperMesh 8.0 Users Guide 15

16 HyperMesh 8.0 Users Guide

HyperMesh 8.0 Users Guide 17

18 HyperMesh 8.0 Users Guide

This command can only be used in the configuration file.

Settings may be used to simulate different materials: Glass *setspecularity(1.0,1.0,1.0,128)

HyperMesh 8.0 Users Guide 19

20 HyperMesh 8.0 Users Guide

Specifying a Temporary File Directory

HyperMesh 8.0 Users Guide 21

HyperMesh Database Design

HyperMesh entities include:

Using and Saving a Database

HyperMesh 8.0 Users Guide 23

24 HyperMesh 8.0 Users Guide

HyperMesh 8.0 Users Guide 25

Create a Multibody Collector

Update a Multibody Collector

Define, Change, Review, and Reset a Multibody Collector

26 HyperMesh 8.0 Users Guide

HyperMesh 8.0 Users Guide 27

Supported Element Types

28 HyperMesh 8.0 Users Guide

HyperMesh 8.0 User's Guide

HyperMesh 8.0 User's Guide

quatrotate(0.000230328525,0.00100703597,0.00106667981,0.9 99998898) quatrotate(-0.00263644785,0.000327769044,0.000395387048,0.999996393) *dynamicviewend()