Professional Documents
Culture Documents
0 User's Guide
HyperWorks
Altair Engineering Contact Information
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.
All other trademarks and registered trademarks are the property of their respective owners.
HyperMesh 8.0 User’s Guide
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
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
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
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
To start HyperMesh:
1. Go to the directory from which you want to run HyperMesh.
2. 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.
To start HyperMesh:
1. From the Start menu, click Start and choose Programs.
2. 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.
where:
-version Display the current version.
-h Print this message.
-rres Use the results file, res (-r alone specifies the file fl.res).
-s<width><height> Opens the application in a window of the specified width and height in
pixels (PC only).
-templex Allows Templex within command files.
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:
Cadreader.ini files, such as catia.ini, Any printer settings (which may also exist in
iges.ini, or ug.ini hm.cfg).
*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 ()
Syntax *boldmenufont(state)
state 1 = bold
0 = use current value
*controlkeyviewmode()
Specify whether display listing should be done during control key assisted viewing.
Syntax *controlkeyviewmode(mode)
mode 0 = immediate mode
1 = use display listing (default)
*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 X-
axis 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 *dynamicrotatemode(mode)
*dynamicviewbegin()
*quatrotate(-0.00785649346,-5.7397916e-
005,0.00228960797,0.999966514)
*quatrotate(-
0.00994070323,0.00170778765,0.0047803938,0.999937705)
*quatrotate(-0.00529684395,-
0.000673180986,0.000802068982,0.999985423)
*quatrotate(-0.00263644785,-
0.000327769044,0.000395387048,0.999996393)
*dynamicviewend()
*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)
#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.
Syntax *forceoldmenufonts()
Note: 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
style 0 = no simplification
1 = feature lines (default)
2 = bounding box
3 = node cloud
4 = element centroid
5 = simplified shading
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 sub-
panel 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.
*legendsetbordercolor()
Allows you to set the border color.
Syntax *legendsetbordercolor(color)
Comments The color must be between 1 and 64, inclusively
*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 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 *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.
*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 *rapidmenus(mode)
Comments 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")
Syntax *registersolver({solver},"{home}\
{solver}","*solver *input file *output file
*options","infile:input file","outfile:output
file","value:options")
Arguments solver The name that you want to appear on the toggle in
the solver panel.
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.
*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
doesn’t 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, it’s 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.
Example:
*setcomponentformat(ansys, "TYPE%t-MAT%m-REAL%r<-SECID%s>-ESYS%e")
<> Symbols mean that everything encapsulated between the two symbols is displayed only if the
element uses a section ID.
*setlightsource()
Set direction of the global light source.
Syntax *setlightsource(x, y, z)
x X axis location, horizontal direction of
screen.
y Y axis location, vertical direction of
screen.
z Z axis location, in/out of screen.
Syntax *setperformancenormalmode(mode)
mode 0 = flat normals (default)
1 = smooth normals
*setspecularity()
Set the global specular highlight values for performance graphics mode.
*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 integer—decimal values are acceptable.
After altering this value you must restart HyperMesh to see the changes.
*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.
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.
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."
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.
bar2 masses
bar3 rod
gap spring
joint
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 HyperMesh’s 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.
Element Configuration
The element configuration defines the physical geometry (i.e., quad, hex) of the element. Element
configurations include:
Bar2 2-noded bar element with property reference, local vector, or orientation node,
offsets, and pin flags (configuration 60).
Bar3 3-noded bar element with property reference, local vector, or orientation node,
offsets, and pin flags (configuration 63).
Gap 2-noded gap element with property reference and vector (configuration 70).
Joint 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 Type Name # nodes Orientation
1 Spherical 2 none/systems/nodes
2 Revolute 4 none/systems
3 Cylindrical 4 none/systems
4 Planar 4 none/systems
5 Universal 4 none/systems
6 Translational 6 none/systems
7 Locking 6 none/systems
Mass 1-noded mass element (configuration 1).
Plot 2-noded plot element used for display purposes (configuration 2).
RBE3 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).
Rigid 2-noded rigid element with user-defined degrees of freedom (configuration 5).
Rigidlink 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).
An edge is a trim line of a surface. You can use surface edges as a line in most panels. Surface
edges include:
Suppressed 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.
Non-Manifold /Duplicate 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.
NURBS 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
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.
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:
• 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
Pull-down menus 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.
Graphics area Located above the tool bar(s): the graphics display area is where model
geometry and mesh displays.
Toolbar Area 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.
Main menu Located across the bottom of the window. The main menu is divided into
the panel area and the page list.
Command Window You can type HyperMesh commands directly into this text box and
execute them instead of using the HyperMesh Graphical User Interface.
secondary menu 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.
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 sub-
menu heading opens a sub-menu of options related to the sub-
menu heading. This method allows similar commands to be
grouped logically, and helps prevent any single menu list from
becoming excessively long.
Toggle When clicked, these items are marked with a checkbox and
activate or deactivate a feature. One example is the solver
browser item found in the view menu; clicking it alternates
between showing and hiding the solver browser in one of the Tab
Area sidebars.
Command Most menu items simply execute a command when selected, such
as accessing a specific HyperMesh panel.
Keyboard (menu) First, press the alt key to activate the menu area. Then:
- Use the keyboard key indicated by the menu or item;
these keys are underlined (as the "F" in the File
menu).
or
- Use the left and right arrow keys to move among the
menu headings, and the up and down arrow keys to
open a menu and navigate among its options.
Keyboard (menu item) Menu items can be selected with the keyboard in two ways:
- Use the keyboard key indicated by the menu item;
these keys are underlined (as the "O" in the Open).
or
- Use the arrow keys to move among list of options, and
press enter to select a highlighted option.
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.
View Change the angle of view on the model, lighting, or visibility and location
of tab area items, among other options.
Mesh Meshing tools, such as automesh, tetramesh, solid map, element edit,
etc.
Tools Morph, Rotate, Translate, Reflect, or Scale entities, among other options.
Results View results of solved simulations (contour or vector plots, for example).
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.
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:
Turn the display of collectors on and off. This button accesses the
display panel.
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.
Note: use the colors panel to change the colors of properties
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.
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.
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 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.
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.
This screenshot shows all of the entities that can display in the 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 assembly’s checkbox displays all of its contents.
• Activating an assembly’s 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 entity’s color without using the
color panel. The currently assigned color displays in the column.
To change an entity’s color, right-click on the current color in the model browser. In this instance, the
right-click menu contains only a single option: color. Select this to open the 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.
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
model—only 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 browser’s tree structure by using special buttons
provided in the model browser’s 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.
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).
Match Case Only entities whose names contain the search string with upper/lower
case matching what you typed into the Find: box. For example, with
this option active, a search for “chassis” will ignore an entity called
“Chassis”.
Whole Names 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”.
Use Wildcards Wildcards allow you to search for any items that partially match the text
you are searching for. For instance, you could search for “*pillar” and
find components named “A-Pillar” and “B-Pillar”.
Note that using wildcards is generally not compatible with searching for
whole names!
By ID Using this option allows you to type an entity ID into the Find: box
instead of a text-based name.
Note that these options are on/off toggles; clicking one activates it (represented by a checkbox in the
list). To deactivate the option, select it again to remove the checkbox. In this way you can combine
the search options, such as searching for whole names with matching case.
To find entities matching your specified string and options, click the up or down arrow buttons to
search upward or downward through the browser’s tree. In this way, you can continue searching by
repeat clicks of these buttons; for example, after clicking the down-arrow and finding the first match,
you can find the next match by clicking the down-arrow again. When the find function reaches the
bottom of the tree it will start over again from the top, until it has performed a single full loop from its
starting point. So, for instance, if the tree contains three entities matching your search string, clicking
the down-arrow button finds match #1; clicking again finds match #2; clicking third time finds match
#3; clicking a fourth time reaches the end of the tree and starts over from the top, finding match #1
again.
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).
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.
Collapse all All Closes all of the folders in the tree structure, so that only
the top-most level of items displays.
Expand all All Opens all of the folders in the entire tree structure,
exposing every item nested at every level.
Show Assemblies, Display the item in the graphics area. This selects each
components, affected item’s checkbox.
groups, load
You can also use this on the entire branch of groups,
collectors, plots,
load collectors, components, materials, plots, and
materials,
properties. In such cases, this shows all of the items
properties,
within that branch (e.g. all groups, all materials, etc.)
system
collectors.
Show Only Assemblies, Deactivates the checkboxes of all items in the entire
components, model browser except for this single item, so that only
groups, load this item displays in the graphics area. Used to quickly
collectors, plots, and easily isolate single entities.
materials,
You can also use this on the entire branch of groups,
properties,
load collectors, components, materials, plots, and
system
properties. In such cases, this hides everything except
collectors.
for the items within that branch.
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.
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.
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.
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 browser’s tree structure by using special
buttons provided in the browser’s own toolbar.
The filtering tool is represented by a funnel icon ( ). This feature allows you to determine which
categories of entity appear in the browser’s tree structure. Clicking this icon adds a new list box to
the browser, named Show: and located just below the browser’s 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 browser’s tree structure. For example, the Components folder only displays in the tree structure
if Components is checked in this list. In this way, you can make the tree structure shorter and easier
to navigate by removing entity types from the browser list that you do not need to work with.
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 browser’s 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).
Match Case Only entities whose names contain the search string with upper/lower
case matching what you typed into the Find: box. For example, with
this option active, a search for “chassis” will ignore an entity called
“Chassis”.
Whole Names 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”.
Use Wildcards Wildcards allow you to search for any items that partially match the text
you are searching for. For instance, you could search for “*pillar” and
find components named “A-Pillar” and “B-Pillar”.
Note that using wildcards is generally not compatible with searching for
whole names!
By ID Using this option allows you to type an entity ID into the Find: box
instead of a text-based name.
Note that these options are on/off toggles; clicking one activates it (represented by a checkbox in the
list). To deactivate the option, select it again to remove the checkbox. In this way you can combine
the search options, such as searching for whole names with matching case.
To find entities matching your specified string and options, click the up or down arrow buttons to
search upward or downward through the browser’s tree. In this way, you can continue searching by
repeat clicks of these buttons; for example, after clicking the down-arrow and finding the first match,
you can find the next match by clicking the down-arrow again. When the find function reaches the
bottom of the tree it will start over again from the top, until it has performed a single full loop from its
starting point. So, for instance, if the tree contains three entities matching your search string, clicking
the down-arrow button finds match #1; clicking again finds match #2; clicking third time finds match
#3; clicking a fourth time reaches the end of the tree and starts over from the top, finding match #1
again.
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).
Delete When an include is Deletes the selected include. Prompts the user
selected 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.
Make current When an include is Makes the selected include "current". Thus
selected any new entities created in HyperMesh such as
new elements, contacts, components, etc. are
automatically placed in the current include.
Include file When an include is Allows you to set the various options for a
options… selected 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.
Import include… When an include is Imports the content of a file into the selected
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.
Collapse Include Permanently Collapses all the branches of the tree structure
for the selected include.
Expand include Permanently Expands all the branches of the include’s tree
structure along with the various entity type
folders (such as comps, mats, etc.).
Display only When an include (or master Clears the graphics region of any previous
model) is selected display and displays all the entities that belong
to the selected include.
Edit card When a control card is Invokes the card image of the control card in
selected the HyperMesh window.
Enable/Disable When a control card is Allows users to enable (turn on and export)
selected control cards that have been disabled and vice
versa.
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).
Export state 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.
Sync browser 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 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 string—either partly or completely.
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.
New subcase Create a new subcase, either from scratch or by creating an exact
copy of an existing subcase.
Edit options Depending on the entity selected, this will bring up an appropriate GUI
for editing of the loadstep or control card information.
BCs Contour This launches the BCs Contour utility and automatically selects the
loadcols associated with the selected loadstep.
Loads Summary This launches the Loads Summary utility and automatically selects the
loadcols associated with the selected loadstep.
Collapse all/selection Collapses all selected folders and subfolders, or all folders if none are
selected.
Expand all/selection Expands all selected folders and subfolders, or all folders if none are
selected.
Auto-manage load This option is for users who wish to have existing DLOAD, LOAD,
references 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.
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 do not display in the HyperMesh graphics area.
Note: When you first open the loadstep browser, all of the loadsteps in the model default to the
blank (unchecked) state.
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. To activate an option, check the box next to the desired option and fill in the required fields.
3. Depending on the Subcase Type, the list of appropriate Load References will change accordingly.
• 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.
4. 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 doesn’t exist in the database
To display a subcase:
1. Check/uncheck the display checkbox next to the subcase of interest.
2. 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.
Note: 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.
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)
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.
Menu Buttons
The color of the menu button corresponds to its purpose:
yellow Collectors
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 switch’s 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:
< Step backward one page toward the beginning of the list.
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.
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 Allows you to pick the nodes individually from the node list.
by path 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.
show node order Allows you to view the nodes currently stored in the nodelist collector by
numbering the nodes in the sequence of their selection.
by window 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).
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.
The switch is used to select the method for defining the plane or vector.
switch 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 node’s button (N1, N2, or N3, or B) to type in
coordinates rather than selecting existing nodes in your model.
Note: 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. Select the x-, y-, or z-axis.
2. Select two nodes, N1 and N2.
3. 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.
4. Select a model vector (i.e., arrows that represent a local coordinate system vector or load vector).
To define a plane:
1. Select the x-, y-, or z-axis and a base node. The base node locates a plane normal to the chosen
axis.
2. 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).
3. Select three nodes, N1, N2, N3. A parallel plane can be specified by selecting a base point
elsewhere in the model.
4. Select a model vector (i.e., local coordinate system vectors or load vectors). The resulting plane
is normal to the vector.
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.
and 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.
BACKSPACE Deletes the character to the left of the cursor and moves the cursor one
space to the left.
HOME Moves the cursor to the beginning of the input field.
END Moves the cursor to the end of the input field.
DELETE Deletes the character which is above the cursor.
TAB Moves the input cursor from field to field on the panel.
To exit edit mode, press the ENTER key, select another menu item, or press a function key.
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.
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.
File name 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.
Files of type This field allows you to select the type of file you want to locate.
Open (Save) Click Open (or Save) to load (or save) the file shown in the File name
field.
Single click and release. Single click and Single click and
release. release.
Performs selection
operations on single Acts as advance Deselects an entity in
entities. (proceed) function after the graphics area.
entity selection in most Aborts graphics
panels. Selects a new operations.
center of rotation in the
rotate (r) and arc dynamic
motion (a) modes.
SHIFT Single click and release. Single click and Single click and
release. release.
In entity selection mode –
choose one of the four Acts as advance In entity selection mode
quick window selection (proceed) function after – choose one of the
modes from a pop-up entity selection in most four quick window
menu: panels. selection modes from a
pop-up menu:
• Entities inside a
rectangular window • Entities inside a
rectangular window
• Entities outside a
rectangular window • Entities outside a
• Entities inside a rectangular window
polygon window • Entities inside a
• Entities outside a polygon window
polygon window • Entities outside a
polygon window
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.
Rotate by increments
+,- Zoom by increments. Note that "+" is actually shift = on the main
keyboard, but simply + on the numeric keypad.
a Arc rotate
c Center
d display panel
g global panel
h Open the Help. When a panel is active, this opens help for that panel;
from the main page menu, it opens the Help’s table of contents.
m Turn off the menus and display only the graphics window. Press "m"
again to bring the menus back.
o options panel
p Plot
r Rotate
s Dynamically zooms in and out when you move the mouse up and down
t True view
w Windows panel
z Circle-zoom
Notes: When you use the +, -, or arrow keys, press the key once and wait for HyperMesh to
redraw the model before pressing the key again.
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:
Ctrl + F1 Creates bitmap file of the screen and spools it to the printer.
Ctrl + F5 Creates a black and white PostScript file of the screen and spools it
to the printer.
Key Function key only plus SHIFT key plus CTRL key
F1 hidden line color print slide
F2 delete temp nodes slide file
F3 replace edges print eps
F4 distance translate create eps file
F5 mask find print b/w eps
F6 element edit split create JPEG file
F7 align node project
F8 create node node edit
F9 line edit surf edit
F10 check element normals
F11 geometry quick edit organize
F12 automesh smooth
Note: Function keys may be reassigned to different panels by using the build menu panel.
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.
Scene (1, 2, 3) Save These buttons save the current view of the model in slot 1, slot
2, or slot 3.
Scene (1,2,3) Retrieve 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.
none 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.
On 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.
Off 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.
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 BC’s 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 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 can’t be partially hidden—so 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 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.
Clear Temp Nodes 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.
Show Adjacent Elems This macro reveals one or more rows of elements adjacent to the
entities currently displayed. For example, if you isolated a model’s
geometry lines, then clicked show adjacent elems, any mesh along
those lines would be revealed—but 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.
Preserve edges Prevents specific edges from being suppressed during autocleanup or
batchmeshing.
Project points Projects free points to surface edges. Depending on the tolerance you
specify, points may even project to multiple edges. This can be helpful
to achieve uniform meshing with regard to weld points.
Isolate Surface Isolates either an inner or an outer surface layer (based on the user
selected surface) from a 3D model. This macro works only on the
surfaces attached to the selected surface. The other layers and
thickness are then placed in a temp directory and masked.
Washer Scales a copy of a selected circular line to 1.5 times its original size,
and then trims this new line into the surface. This allows a higher
quality mesh around circular holes.
Adj Circ Pts Places four additional fixed points on an inner line, and then projects
those points to a concentric line, creating a higher quality mesh.
Auto Connectors A pop-up menu that allows you to automatically create connectors and FE
realize them from a master connection file.
Quick Tetramesh Quickly creates an automatic tetrahedral mesh while meeting the
requirements for minimum element angle and element size.
Fix 2nd Order Improves element quality by moving the mid-edge nodes of second order
Midnodes elements.
Add Washer 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.
Fill Hole Fills the selected hole and remeshes the surrounding mesh to maintain
connectivity. This macro does not remove any rigid spiders that fill the
hole; if necessary, delete the rigid spider before using this macro.
Box Trim Trims the model along user-defined trim lines. This is useful for reducing
the model size by taking advantage of symmetry etc.
Bead Creates a bead of a given height and width along the selected two nodes
and connects to the surrounding mesh.
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
Jacob (Jacobian) This macro checks all the displayed elements against the maximum
Jacobian value. If any elements fail the criteria, it displays the failed
elements and masks the remaining elements. If none of the displayed
elements fail the criteria, it displays a message and leaves the display
unchanged
Warp (warpage) This macro checks all the displayed elements for their warpage. If any
elements fail the warpage test, it displays the failed elements and
masks the remaining elements. If none of the displayed elements fail
the criteria, it displays a message and leaves the display unchanged
Aspect (aspect ratio) This macro checks all the displayed elements for their aspect ratio. If
any elements fail the criteria, it displays the failed elements and masks
the remaining elements. If none of the displayed elements fail the
criteria, it displays a message and leaves the display unchanged
Max ang: Q (quad) This macro checks all the displayed quad elements against the
maximum internal angle. If any elements fail the criteria, it displays the
failed elements and masks the remaining elements. If none of the
displayed elements fail the criteria, it displays a message and leaves
the display unchanged
Min ang: Q (quad) This macro checks all the displayed quad elements against the
minimum internal angle. If any elements fail the criteria, it displays the
failed elements and masks the remaining elements. If none of the
displayed elements fail the criteria, it displays a message and leaves
the display unchanged
Min ang: T (tria) This macro checks all the displayed tria elements against the
minimum internal angle. If any elements fail the criteria, it displays the
failed elements and masks the remaining elements. If none of the
displayed elements fail the criteria, it displays a message and leaves
the display unchanged
You can use the following macros to quickly modify any elements that fail the element checks.
Split Warped Checks all displayed quad elements for warp exceeding the acceptable
value. Each element failing this criterion is then split along its diagonal to
form two tria elements instead of the original quad.
Find Attached Finds all of the elements attached to the displayed elements.
Remesh Allows you to remesh the selected elements plus one, two, or three
attached layers of elements (one button for each). The remesh uses the
current size, does not break connectivity, and uses the mixed element type.
Smooth Allows you to apply the smoothing algorithm to the selected elements plus
one, two, or three attached layers of elements (one button for each).
Quality Report Brings up a user interface that allows you to set the various quality values
and check the quality of all the 2D elements in the model. The results are
shown as the number of elements and percentage of elements failing each
criterion. You can also export the results to a text file using save as.
Note: Changing the criteria on this report interface does not change the
settings in the check elements panel. They only affect the
report.
Model Tour Allows you to review (tour) the selected components individually. This
macro displays the component name, number of elements in that
component and their ID range. It also displays a dialog that allows you to
review the free edges of the component and any elements attached to the
component.
BOM Comparison Reads a generic Bill Of Materials file and provides an interface to
Tool manipulate data in the BOM as well as the corresponding FE model.
Load Size These numbered buttons represent different display sizes for
load indicators: 0 is the smallest, while 3 is the largest. Since
these buttons affect all loads, including forces, pressures,
constraints, and so on, the numbers do not directly correspond
to any specific values or ratios.
Note that this only affects the graphical display of load
indicators—it does not change the load magnitudes.
Find Elems>>Loads Automatically finds all elements directly attached to any and all
load indicators. If masked, these elements are un-masked.
Find Comps>>Loads Automatically finds all components directly attached to any and
all load indicators. If masked, these comps are un-masked.
Find Elems>>Connectors Automatically finds all elements directly attached to any and all
connectors. If masked, these elements are un-masked.
Tree section: Contains a tree structure displaying part names and ids.
BOM display section: This section contains a table to display BOM info as it is seen
in the actual BOM file.
Failed records section: Displays failed records from a loaded BOM file.
Display filter section: Contains filtering options for displaying tree and table info;
part of the tree section.
Show Failed Display all the invalid records that the tool
encounters while reading a BOM file in a table. Only
valid records from a BOM file display in the BOM
Display Section’s table. Invalid records can be
edited to form valid data and can be moved to the
BOM Display table.
Save and Export Save and export the current information shown in the
BOM Display section as a new BOM csv file in a
user selected location.
Edit menu Update Model Update the model attributes to match the BOM.
Complete BOM Sometimes the BOM doesn’t contain all of the data
you want. If the corresponding model contains the
missing data, you can complete the BOM data by
querying the 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).
You can enter a string in the combo box, select the desired header in the options menu, and press
the <return> key to display the desired information in the tree and BOM display table. The combo
box remembers previously entered strings until you quit the tool, and can be used to filter the BOM
info anytime in the session.
Apart from this there are filter buttons each one of which is explained below:
Displays all the branches in the tree and the associated data
(Select All) in the BOM display table
Switch off all the branches in the tree and delete all the data
(Select None) in the BOM display table
Switch on all the “off” branches in the tree and vice versa.
(Reverse selection)
Data associated with switched-on branches displays in the
BOM display table
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.
Metadata related to BOM display BOM related metadata for the selected row
in the BOM display table
All metadata display all the metadata for the selected row in the
BOM display table
Differences between BOM/metadata display two rows of info in the metadata table.
First row corresponds to BOM info, second row
corresponds to metadata associated with the model
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.
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.
Select Lines 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.
Show Preserved Click this button to highlight the lines already marked for preservation.
Comps selection When active, this checkbox prevents HyperMesh auto-cleanup from
boundary equivalencing the boundaries between adjacent components.
Select comps 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
components—only the outer boundary edge.
Clear all lines Removes all lines from the preservation list.
Save preserved Saves the preservation state, so that autocleanup and batch mesher
will know which lines must be preserved.
OK Accepts any changes you’ve made and closes the pop-up window.
Cancel Discards any changes you’ve made and closes the pop-up window.
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.
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 user-
specified 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.
2. Groups the elements that have thickness values within the specified
ranges into the new component based on the Range Interval or
Gage File options.
3. Assigns appropriate thickness values to the Component.
Z-Offset Values Activate this checkbox to take z-offsets into account. HyperMesh uses
Z-offsets when midsurfacing parts that have variable thickness; the z-
offset (which is saved as part of the midsurface data) tells a solver how
much of a positive-normal offset exists between the actual part surface
and the midsurface:
Component This option specifies the thickness range intervals used when grouping
Organization method 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 = 0……n, n is determined by the maximum thickness in
model divided by the user specified tolerance and then rounding to
up to the next integer.
Assign Assigns the thickness from the surface definition to the nodes or
elements chosen.
Gauges
Begin End Assigned Value
0.0 0.05 0.05
0.05 0.1 0.1
0.1 0.15 0.15
0.15 0.2 0.2
PamCrash
1. Nodes/Elements
• Assigns the thickness values to the Element card
2. 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
3. Z-offset Value
• Unsupported
Radioss
1. Nodes/Elements
• Assigns the thickness values to the Element card
2. Components
• Creates the component
• Assigns the thickness value to Component
• Group the elements to the Component
3. Z-offset Value
• Unsupported
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.
Minimum Tria Angle The surface trias from which the tetramesh will be extrapolated will be
generated with angles that measure at least this many degrees. Use
this control to limit how acute the resulting elements will be.
Maximum feature The maximum feature angle protects nodes on corners with a feature
angle 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.
Minimum Edge Size No single edge of any generated element will be shorter than this.
Sacred surface 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!
Sacred elements These are existing trias that you have created according to your
requirements and wish to maintain while tetrameshing the part. This is
useful in ensuring that a particular feature is captured exactly the way
you want it to be. The tetramesher will not move the nodes of these
elements, even if doing so would improve element quality.
Note that this setting overrides the float setting in the tet from option,
but only for the elements selected as sacred.
Mesh type The mesh type options are Trias Only and Mixed. With the Mixed
mesh type, both trias and quads may be created.
Mesh Density Choose between chordal deviation and uniform. Chordal deviation
uses smaller elements along curves, feature lines, and edges to
improve accuracy, but requires more computing time. Uniform uses
identically-sized elements throughout the mesh, but may produce low-
quality elements along such locations.
Tet from Choose floating, in which the quick tetramesher is free to move nodes
in a surface tria mesh to achieve better tetra elements based on them,
or fixed, in which the mesher must keep the tria mesh unchanged.
Mesher Choose between automesh and batch. This determines the meshing
engine used: the one used by the automesh panel, or the one used by
the 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.
Perform mesh When this option is checked, no tetra elements are created and the
cleanup only 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.
Help Opens a pop-up window with basic information about each control that
displays on the tab.
Debug Surface Mesh A series of tools that help you located problem areas which can cause
poor meshing:
The Quick Tetramesh macro meshes the unmeshed surfaces in the model using chordal deviation
and fixes all the elements that fail the criteria provided. You can manually mesh some critical
geometry and select those elements as sacred elements. These sacred elements need to be trias.
As a part of the cleanup, the tool heals small cracks in the model.
Suggested process to effectively use quick tetramesh:
1. Load the geometry.
2. For critical areas where you want to control the mesh such as bolt holes, manually mesh using
chordal deviation. Select these elements as sacred elements. This helps to obtain the desired
mesh in critical areas.
3. Launch the Quick Tetramesh macro. Run with the desired mesh size.
4. Identify problem areas, if any (e.g. any surfaces edges that were ignored, or if mesh in certain
areas is not satisfactory).
5. Use the delete panel to delete the tetras then, manually mesh problem areas.
6. Re-launch the Quick Tetramesh macro and select sacred elements to protect.
nd
The Fix 2 Order Midnodes window.
nd
4. 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 midnode-
bearing edges. A value of 1 represents perfectly equal segment length, while a length of 0
would mean that the shorter segment might not exist—so this value must be greater than 0,
but no greater than 1. Remember that this is a minimum length, so a value of 0.5 would
allow the shorter segment to be half as long as the longer segment, or longer—but not
shorter than half the length of the longer segment.
• Specify a minimum Jacobian value, and use the radio buttons to determine whether
HyperMesh should evaluate each element’s Jacobian at the corner nodes or the integration
points.
The options in the Mesh Trimming with Circular Holes window determine the type of hole that
HyperMesh creates at each chosen node:
Hole radius Each node will receive a hole of this radius, measured from the
node.
Number of layers This is the number of layers of washer mesh elements that you want
to surround each hole.
Uniform/Varying This toggle only applies when the number of layers is more than
zero, and specifies whether you want mesh layers to all be the same
width, or to vary from one another.
No. The number of a specific washer layer. If you chose varying width
for the layers, the table displays one row for each of the number of
layers that you specified. Otherwise, only one row displays
because all layers will be set to the same values.
Create rigid spider This checkbox tells HyperMesh to create a rigid spider in each of the
along the hole 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 This determines the mesh density around the new hole(s). Each
nodes around the new hole will be created with at least the number of nodes that you
hole specify in the density field, evenly spaced around its circumference.
Reject If you don’t like the results of the last trim operation, click this button
to undo it. Note that this only undoes a single click of the trim
button, so it can only undo multiple holes if they were created
simultaneously during a single trim operation.
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.
2. Select nodes on the edges of the holes that you wish to fill.
3. 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.
4. Click the Fill button to fill the selected holes with mesh.
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.
Fill Click this button to perform the fill operation, whether you chose to select
your holes manually or automatically.
Reject If you don’t like the results of the last fill operation, click this button to undo
it. Note that this only undoes a single click of the fill button, so it can only
undo multiple fills if they were created simultaneously during a single fill
operation.
left Split the model along global Y=ymiddle and save the model between Y=ymin and
Y= ymiddle (ymiddle =(ymin+ymax)/2).
right Split the model along global Y=ymiddle and save the model between Y= ymiddle
and Y=ymax.
front Split the model along global X=value (selected value) and save the model between
X=xmin and X=value.
rear Split the model along global X=value (selected value) and save the model between
X=value and X=xmax.
frontleft Split the model along global Y=ymiddle and X=value (selected value) and save the
model between Y=ymin and Y=ymiddle, and X=xmin and X=value.
frontright Split the model along global Y=0.0 and X=value (selected value) and save the
model between Y=0.0 and Y=ymax, and X=xmin and X=value.
rearleft Split the model along global Y=0.0 and X=value (selected value), and save the
model between Y=ymin and Y=0.0, and X=value and X=xmax.
rearright Split the model along global Y=0.0 and X=value (selected value) and save the
model between Y=0.0 and Y=ymax, and X=value and X=xmax.
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.
If you select Corners, click the icon, , and select the two corner nodes that define
the outer X, Y and Z bounds of the box.
If you select Distance from center, click the icon, , and select the center node.
Then enter Delta X, Delta Y and Delta Z values which is the distance from the center
node to the outer bounds of the box in global X, Y and Z directions.
4. You can turn on the option of creating constraints (SPCs) for all the nodes along the face of the
box. The nodes are constrained in the appropriate directions depending on the trim axes and are
stored in the specified load collector (SPC collector). If no load collector is specified, the
constraints are created in the current load collector.
5. You can also specify a Box collector. A large hexa element that represents the box will be
created for visualization in the specified collector.
6. Click Trim. (Reject will undo all the above.)
The syntax is the same as used for spotweld.exe feinput translator. For additional supported
formats, see Spotweld Interface Overview.
1.4 1.9 7
2.0 3.0 8
The nugget diameter is 7.0 for the thickness range of 1.4 to 1.99.
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.
Project to shell This creates the Hexa elements between the component/element shell
surface. The length of the Hexa element will be equal to the actual distance
between the two connecting components/elements. The second figure
below shows the ACM weld created using this method.
The 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.
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.
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.
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
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 spring
M masses
BAR2 bar2
BAR3 bar3
R rigid
RL rigid link
W weld
RBE3 rbe3
J joint
ROD rod
GAP 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 sub-
panel to switch on or off the display of line handles. Line handles
can be selected whether or not they are displayed.
Surfaces Surfaces do not have pick handles. Surfaces can be selected along
their edges or on interior UV lines (also known as surface lines).
Components Components do not have pick handles. A component can be
selected by picking an element, line, or surface within that
component.
Systems The pick handle for a coordinate system is located at the origin of the
system.
Input Collector
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.
by face 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 panel’s 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.
by group 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.
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.
by sets 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.
by surface 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.
displayed 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.
on plane 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.
retrieve Allows you to retrieve previously saved entities from the user mark.
Entities can be saved to the user mark by selecting save in this pop-
up window, or by selecting save failed in the check elems panel.
save Allows you to save the currently selected entities to a holding area
known as the user mark.
Notes: 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.
f Fit to screen
To display geometry:
• Click the toggle and select geoms to display the surfaces and lines in a component.
To use a filter:
1. Click the leftmost toggle to filter =.
2. Enter the character string to use for the filter.
You can use the asterisk (*) for a wildcard.
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.
pick tol 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.
zoom factor 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.
surf lines 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.
element handle 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.
geom handle The geom handles option allows you to specify whether or not to display
line and surface handles.
coincident picking 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.
template labels/ HM This option allows you to display the element labels as template names
labels or HyperMesh names.
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:
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.
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.
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.
Hidden components 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.
Memory usage 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.
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.
cleanup tol "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.
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.
• 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 don’t want and then invert the
selection.
reverse video Select reverse video to indicate that your printer cannot produce
reverse video images.
fill to page Select fill to page to fill the PostScript image to the specified page
dimensions.
fill model Select fill model to expand the model to its maximum size within the
graphics area of the PostScript page.
bitmap preview 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.
plot optimize Select plot optimize to decrease the size of the PostScript file
generated. This requires processing time to optimize the image output.
page length = Click page length = and enter the new size to alter the page length.
The standard page length is 11.0 inches.
image size = Click image size = and enter the new size to scale the image on the
page to your specifications.
line width = Select line width = and enter the new width to alter the line width.
print it Select print it to send a copy of the file to the printer when you
generate the PostScript file.
Note: Those control cards that are defined (green in the control card editor) are output.
Default values for attributes are common throughout the card previewer. A default value field has two
states:
State Description
Default = ON In this state, the field label color is yellow and no data entry is
allowed.
Default = OVERRIDDEN To override a default value field, pick the yellow field label. When
you override a default value field, the label text color changes to
cyan, and allows you to enter data in the field.
To create a collector:
1. Select the collectors panel.
2. Select the create sub-panel.
3. For collector type:, click the switch and select the type of collector that you want to create.
4. Click name = and enter a name for the collector.
5. 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.
7. Where available, click color and select the desired color for the component from the pop-up
menu.
8. Click create.
To create a component:
1. Select the collectors panel.
2. Select the create sub-panel.
3. Click the upper switch and select comps.
4. Click name= and enter comp1.
5. Click the switch under creation method: and select no card image.
6. Click create.
7. Click return.
To import geometry:
1. Select the import sub-panel on the files panel.
2. Select the Geom option.
3. Select the appropriate file format to be imported from the pop-up menu.
4. Click import… to invoke the file browser and select the file that contains your geometry data.
5. 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.
lines Create lines in a variety of methods, including: from points, at tangents, and
at the intersection of other geometry.
line edit Edit existing lines in a variety of methods such as combine, split, smooth, or
extend.
surfaces Create surfaces from existing lines or nodes by different methods, such as
spline, drag, or spin.
defeature Edit existing surfaces by removing individual features such as holes or fillets.
temp nodes Add or remove nodes used only for geometry creation or editing.
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.
The skin option can create a skinned surface through a set of lines.
• clear • Removes selected individual nodes from the temporary node list.
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.
The quick edit, edge edit, point edit, and autocleanup panels contain tools to help you prepare
surface geometry for meshing.
Note: Refer to the specific panel for detailed information about creating, reviewing, and updating
loads and constraints.
Note: System collectors collect system entities. A system collector must exist and be current in
order to build a system.
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.
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.
Free 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.
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 If the region is free from internal holes and the boundary is clearly triangular,
Triangle, rectangular, or pentagonal in shape, the best choice of algorithm is usually to
Rectangle, or map a standard mesh onto the region using transfinite interpolation. Such an
Pentagon 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.
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.
Size Corrected 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.
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.
.
For this, m is the absolute value of the biasing intensity. If the biasing intensity is negative, the nodes
are placed according to 1 - x(s). Thus, a positive biasing intensity puts small elements at the start of
the interval.
We can use b to scale the behavior of the function so that convenient values are in the range [0,20].
The value used is b = 1.5.
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.
Let then:
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:
Use the automeshing secondary panel to prepare input for solid offset.
Note: 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.
Connector Location
The position in space at which a connector entity is created.
Note: Only nodes, points, and lines can be used to define connector location.
Note: 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.
Note: 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.
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.
Note: 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: The connector rules (connect when:) option is set in the Create and Add Links panels.
Connector Realization
Creating welds at a connector.
Note: The connector entity can be used to create only welds at this time.
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)
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.
• 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 connector’s 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 connector’s state will not change to or from the unrealized state using this
method.
Once a connector is placed into the user control mode, the user control mode remains active until an
unrealize command is called (such as *CE_Unrealize), an already realized connector is re-
realized, or the user control mode is manually turned off with either the
*CE_SetSpecificDetailById or *CE_SetSpecificDetail commands. While a given
connector is in user control mode, it may not behave the same as a normal connector. Specifically,
there are a number of scenarios where a 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.
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.
Weld Template
int num
header
type "CONNECTORS"
set mark
find "[0-9]+::"
rewind
set num = 0
if
do 1000000
readln null
set numrequests = 9
set numcomponents = 1
components "Value"
record
read request // ID
qfind "::"
set mark
rewind
read num
qfind "::"
read request // X
qfind "::"
read request // Y
qfind "::"
read request // Z
do num
qfind "::"
do num
readln null
FE Definition Template
The FE definition template is shown below:
*style <style_type>
*head
*body <BODY_FLAG>
USER_FE_NAME The user-specified name for the FE combination. The specified name
is saved and displayed in the info table during connector review
process.
Note: A “*” is required in the beginning of the line to specify that this is a definition and not a
comment.
*STYLE This option indicates that the configurations have specific behaviors
associated during realization, and that they are native types.
Note: The style definition line for these configurations must not be
edited.
For example, *style bolts 1 indicates that this is a bolt connection of type
1 that creates a specific bolted connection between the parts.
Note: A “*” is required in the beginning of the line to specify that this is a definition and not a
comment.
Note: A “*” is required in the beginning of the line to specify that this is a definition and not a
comment.
HM_FE_TYPE HM_FE_TYPE 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.
BODY_FLAG The body flag is used to calculate the length of the weld. If the body flag =
0, the length is calculated based on the distance between the connecting
layers (link entities). If the body flag = 1, the length is calculated based on
the average thickness of the connecting layers (link entities).
Note: 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 weld currently supported by HyperMesh. The
various types supported for welds are, spring, plot, hexa8, rod,
etc.
HM_FE_TYPE 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.
LENGTH_LOCATION_FLAG 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.
Note: A “*” is required in the beginning of the line to specify that this is a definition and not a
comment.
*POST 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 connector’s
generation panel.
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.
The bar elements are created at the same location and connect the same link entities.
0-D Welds
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.
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.
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.
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.
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.
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 “^”.
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.
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.
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.
Global handles, independent (red) and dependent (yellow, cyan, and violet)
Local handles, independent (orange) and dependent (green, blue, and pink)
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.
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.
To convert shapes saved with handle perturbations to shapes saved with node perturbations,
or vice-versa:
1. From the HyperMorph module on the Tools page, select the shapes panel.
2. Select the convert sub-panel.
3. Select the type of conversion that you wish to perform.
4. Select the shapes to be converted.
5. 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.
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:
To morph interactively by moving the handle and releasing the mouse button:
1. From the HyperMorph module, select the morph panel.
2. Select move handles.
3. Change the upper middle selector to interactive.
4. Change the rightmost toggle from real time to on release.
5. Change the lower middle selector from on domains to along vector.
6. Select a vector.
7. Click morph.
8. Select a handle on the screen and hold the mouse button down.
9. 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.
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. Change the upper middle selector from interactive to move to node.
2. Select a handle.
3. 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.
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.
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.
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.
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.
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.
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.
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.
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. From the HyperMorph module, select the domains panel.
2. Select edit edges.
3. Change the selector to add handles.
4. Select one or more domains.
5. 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.
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.
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.
translate This option allows you to translate handles along a vector or element
normals.
move to XYZ This option allows you to position handles at specific XYZ locations or
place them on lines, surfaces, or another mesh.
move to node, These options allow you to position handles at specific node or point
move to point locations, or place them on lines, surfaces, or another mesh.
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.
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.
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.
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.
Using Biasing
Biasing allows you to control the shape of a mesh when applying handle perturbations. Biasing
increases or decreases the influence of a handle over the nodes within its area of influence. If the
biasing values for all of the handles are equal to 1.000, which is the default value for all handles
except for dependent handles on 1D domains, the morphing between the handles is linear, provided
both handles are global handles or they are located on edge domains. Higher biasing values
generate a smooth curvature near the handles, while lower biasing values generate harsh corners
near the handles. To smoothly change the shape of a domain it is recommended that you use a
biasing factor of 1.000 at the corners, 2.000 at the edges, and 3.000 in the middle.
Biasing 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.
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.
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.
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.
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.
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.
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 component—thus 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).
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.
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.
Area
Radius of Gyration
Shell open
Shell closed
Shell open
Shell closed
Shear stiffness
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.
Shell
Solid
Standard
Generic
File Menu
New Create a new section collector, standard section, or generic section.
Save Save the beam cross-section.
Import Section Opens a file browser so you can import a beam cross-section.
Export Section Opens a file browser so you can export a beam cross-section. Options are
provided to export all sections, or only selected sections.
Export Results Opens a file browser so you can export the results for the selected section to
a text file.
Print Prints the currently displayed beam cross section and the section analysis
results.
Print Preview Displays a print preview.
Print Setup Allows you to set up printer preferences.
Exit Exit the HyperBeam module and return to HyperMesh.
Edit Menu
Undo Undo the last procedure.
Paste Paste the selected text or entity into the location of the cursor.
Background color Specifies the main background color for the section
graphics region.
Background color Select the background color for the results display.
Font 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 The computed results for a section are formatted using a
templates 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.
External solver for You may substitute your own solver to compute values
thin shell sections for thin Shell sections. Contact Altair for technical
details on exchange file formats and return codes.
Tools Menu
Break a Segment Allows you to break a segment so that you can add a new vertex.
Join Segments Allows you to delete a vertex to join two segments.
Create a New Part Allows you to add a new sheet metal part to the current section.
Move Vertices Allows you to move vertices.
Reorient Shell Section... Allows you to change the local coordinate system that defines the
beam cross section.
Part Editor... Allows you to rearrange parts in a section, rearrange vertices in a
part, or add or remove vertices from a part's definition.
Properties... Allows you to modify the properties of the beam cross-sections.
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.
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 …
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 Set the torsion factor.
Warping Factor Set the warping factor.
Line color Choose the color to use for displaying the
lines and vertices of the section in the
graphics plane.
Optimization 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.
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.
Section type Specify the shape out of the available
choices to use for the standard section.
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 on area of the beam section by using the mouse
to draw a circle around the area of interest.
Zoom out Zoom out on the view in the graphics pane while
maintaining the same center.
Show/hide Ids Turn on and off the display of vertex IDs in shell sections.
Update results Bring the section results up to date, if you have turned off
the auto-update of section results.
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.
Join two segments/ If you want to delete a vertex, activate this tool and click on
eliminate vertex the vertex.
Create a new part 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.
General Tools
There are eight tools that allow you to manage a HyperBeam session:
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.
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.
st nd
1 versus 2 For beam cross sections that were fully defined by lines or surfaces, you may
Order Element choose to have the properties calculated using first or second order elements.
Analysis 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.
Save Elements 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 sub-
panel 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.
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.
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 post-
processing options can be performed in any combination desired and are not exclusive of other
functions.
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.
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.
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.
Toolbar 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.
Laminate Browser 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.
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).
Review Pane 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.
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.
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.
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.
To create entities:
There are three options for creating new entities in HyperLaminate:
1. Select an intermediate level branch (an entity sub-type or card image) of the browser tree.
2. Right click on selected entity sub-type.
A context sensitive menu appears with one option: New.
3. Click New.
A new entity appears under the selected branch.
Or
1. Select an intermediate level branch (an entity sub-type or card image) of the browser tree.
2. Select New from the File pull-down menu.
A new entity appears under the selected branch.
Or
1. Select an intermediate level branch (an entity sub-type or card image) of the browser tree.
To duplicate entities:
1. Right or Left click on an entity (lowest level in tree hierarchy) in the Laminate Browser tree to
select it.
2. Right click on selected entity.
A context sensitive menu appears with three options: Rename, Duplicate, and Delete.
3. 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. Right or Left click on an entity (lowest level in tree hierarchy) in the Laminate Browser tree to
select it.
2. Right click on the selected entity.
A context sensitive menu appears with three options: Rename, Duplicate, and Delete.
3. Click Delete.
A confirmation dialog is displayed.
4. Click Yes.
The entity is deleted and disappears from the Laminate Browser.
Or
5. Right or Left click on an entity (lowest level in tree hierarchy) in the Laminate Browser tree to
select it.
6. Select Delete from the Edit pull-down menu.
A confirmation dialog is displayed.
7. Click Yes.
The entity is deleted and disappears from the Laminate Browser.
Or
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:
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:
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.
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 ply’s 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.
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.
load mapping 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.
flux points
forces points
moments points
pressures surfaces
nodes on edge: lines (for 2-D solid elements)
nodes on face: surfaces (for 3-D solid elements)
Note: Refer to the specific panel for detailed information about creating, reviewing, and updating
loads and constraints.
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
#XYZDATA
#pressure
#ENDDATA
2. Click OK.
The mapping algorithms are accessed, the mapping process runs, and the DLM dialog closes
upon completion of the mapping process.
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.
Structural analysis model file: The browser allows you to select the structural model in
NASTRAN format on which to apply a mathematical function.
Equation string fn(x,y,z) = 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
Note: To create pressure loads at element centroids via mathematical functions, use the Field
Loads macro on the Geom/Mesh macro menu.
nodal displacement Stores three floating point values at a node. This form of data type is
usually used to store displacements or a vector quantity.
nodal value 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.
element value 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.
complex nodal Stores a complex value (magnitude and phase) at a node. This form
displacement of data type is usually used to store displacements or a vector
quantity.
complex nodal value Stores a complex value (magnitude and phase) at a node.
complex element value Stores a complex value (magnitude and phase) at an element.
complex nodal von Stores a complex von Mises value (magnitude, phase, offset) at a
Mises node.
complex element von Stores a complex von Mises value (magnitude, phase, offset) at an
Mises element.
Data types are not required to contain results for every node or element in the model, and may
contain a subset of the total model, if this is appropriate. If this occurs, 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.
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 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.
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.
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.
nodal values and displacements 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.
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.
axis scaling 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.
border 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.
curve attribs 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.
edit curves 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.
grid attribs 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.
grid labels 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).
legend The legend panel allows you to change the location and the font used to
display the legend.
plot titles 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.
plots Allows you to create an xy plot and assign curves to the xy plot.
query curves Allows you to determine the coordinate values of points in a curve.
In addition, you can use the curve editor to view and modify curves already defined in your
HyperMesh model.
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.
Type Data files can consist of different types of data. Available data types depend
on the data file.
Request Once the data type has been selected, the data request set needs to be
selected.
Component After the data request set has been selected, the component must be
selected.
Note: For more information about math expressions, refer to the Altair Math Reference.
It’s 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 delete a curve:
1. In the curve list, click the curve that you wish to delete.
2. 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. Type in a new name for the curve.
3. Click proceed.
HyperMesh returns you to the curve editor, which now uses the curve’s new name.
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
where x is the vector of nodal coordinates, BVi is the basis vector associated to the design
variable DVi .
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 x 0 is the vector of nodal coordinates of the initial design,
is the vector of nodal coordinates,
PVi is the perturbation vector associated to the design variable DVi .
Note: 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.
Manual Perturbation
To generate perturbation vectors by the manual perturbation method:
1. Write a <prefix>.base file using the baseline model of the structure using the OptiStruct
template supplied in the distribution.
2. In HyperMesh, move the grids to define the perturbed shape.
Do not save the perturbed model.
3. Write out a perturbation file <prefix>.pert<nnn>, where nnn is the design variable ID, using
the AutoDV template. Example: mymodel.pert006.
4. To generate another perturbation vector, retrieve the baseline HyperMesh database and
complete steps 2 and 3, giving the *.pert file a different ID.
5. Select the solver panel.
6. Click the switch and select AutoDV as your solver.
7. 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.
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.
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.
=1 for m = 0
and
=1 for n = 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.
Example 1:
X_ORDER = 2 X_TYPE = all desvar name = dv01
Shape Variable 1 2 3 4 5 6
m 0 0 1 1 2 2
n 0 1 0 1 0 1
Example 2:
X_ORDER = 2 X_TYPE = even desvar name = dv02
m 0 0 2 2
n 0 1 0 1
Example 3:
X_ORDER = 2 X_TYPE = odd desvar name = dv03
m 0 0 1 1
n 0 1 0 1
<prefix> Prefix of the input file name, or input file input file =
name.
prefix.dat A bulk data file that contains the DVGRID and LOAD information,
respectively depending on opt2.
prefix.autonnn 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.
prefix.dv.animate This file contains the shape design variables in the HyperMesh
results format. This file can be loaded to HyperMesh and results
can be viewed.
Simplified HTML File Since the H3D file created from HyperView, and HyperMesh
Statement 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.
Direct Readers HyperView Player only supports H3D direct readers. You can
create an H3D file using:
• HyperView
• HyperMesh
• HyperMesh result translators, such as hmnast, hmnasto2,
hmdyna, hmradioss, hmpam, hmansys, and hmabaqus
• OptiStruct
Note 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.
SRC="URL" The location of the plug-in data file as indicated by its URL.
<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.
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.
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.
Why doesn’t 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.
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)
• 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.
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.
The Blank State signifies that the entity set will be exported.
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.
• 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.
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 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.
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 file—it will append/replace the data as described above.
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 cross-
section names and the associated sets. Therefore, it is important to avoid renumbering any element
or node sets for which cross-sections are to be retained within HyperMesh database.
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 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 sub-
case 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.
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 collectors—one for each force and moment component—for
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.
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.
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.
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.
2. 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.
3. 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.
4. 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.
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
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. All nodes in the node set will have displacement and rotation values extracted.
2. 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.