Gambit

2000 UGM Gambit: Tips & Tricks
June 12, 2000 Shyam Kishor Roman Tomaszewski
UGM 2000
Company Confidential
Copyright 2000 Fluent Inc. All rights reserved. 1
Outline-1
Geometry
w
Data exchange with other CAD/CAE systems

Direct options Standard-based options Importing meshes and faceted geometry CAD-to-Gambit flowchart summaries
w w w w
Check geometry/topology Converting non real geometry to real Healing real geometry Construction and clean-up strategies

Using virtual geometry for cleanup Construction tips
UGM 2000
Outline-2
Meshing
w w w w
Cooper tool Boundary layers Stairstep meshing Meshing tips Parametric modeling
Gambit Tools
w
UGM 2000
Geometry

Checking geometry/topology Healing real geometry Converting non real geometry to real Construction and cleanup strategies
UGM 2000
Data exchange with other CAD/CAE systems-1

Direct Options
w
ACIS-based CAD programs: e.g., AutoCAD, Cadkey, TurboCad Can export ACIS files (.sat or .sab) which can be imported into Gambit. ACIS version compatibility
Gambit typically employs recent ACIS rev. (ACIS 6.1 for Gambit 1.3) Gambit can import and export older versions of ACIS.
Parasolid -based CAD programs: e.g., Unigraphics, SolidWorks, Solid Edge, PATRAN, ANSYS Can export Parasolid files (.x_t & .xmt_txt) which can be imported into Gambit Parasolid version compatibility
Gambit can import and export most versions up through 11.1
UGM 2000
Data exchange with other CAD/CAE systems-2

w
Direct (single-stage) translators for native CAD systems e.g., Pro-E/ACIS, Catia/ACIS Available from various vendors (see http://www.spatial.com for full listing)
Standard - based options

w
Use of neutral file format to exchange data STEP IGES
UGM 2000
Data exchange via STEP

STEP (STandard for the Exchange of Product model data) :
w w
International standard that defines a neutral file format for the exchange of geometric, topologic, and annotation data. Most CAD programs include STEP export

Pro/ENGINEER at no additional cost Most others as an add on
w w
Both STEP AP203 and STEP AP214 are supported by Gambit Better than IGES

STEP supports solid models
Creates real Gambit (ACIS) volumes after import.
Topology/connectivity-related information is maintained Exports real geometry, including solid volumes
STEP export
UGM 2000
Data exchange via IGES

IGES (Initial Graphics Exchange Specification) Files:
w
Most CAD programs can export IGES files. Topology/connectivity information is lost when CAD programs export IGES surface data only. Some CAD packages export IGES-solids as well as IGES-surfaces.
I-DEAS and CADDS Topology/connectivity information maintained.
Gambit provides two options for IGES import Spatial

Creates real geometry Supports IGES-solids (MSBO)
Native
Creates virtual geometry for trimmed surfaces Supports surfaces only Use only as a fallback when Spatial translator fails
IGES export
Exports real geometry Supports IGES solids (MSBO)
UGM 2000
STEP/Parasolid-to-Gambit Flowchart
STEP/ Parasolid
Geometry Import Check Geometry
Okay? Yes
No
Heal
Check Geometry
Better? Yes
No (undo)
Real Geometry
Yes Connected? No
Heal
Connected? Yes
No
Use Virtual Geometry

UGM 2000
IGES-to-Gambit Flowchart
IGES
Spatial Translator Check Geometry
Okay? Yes
No
Native Translator
Okay? Yes
No
Heal
Check Geometry
Better? Yes
No (undo)
Real Geometry
Yes Connected? No
Heal
Connected? Yes
No
Use Virtual Geometry

UGM 2000
Data exchange via Mesh/Faceted Geometry-1

w
Import of mesh or faceted geometry files results in faceted geometry Supported Mesh Formats

Faceted Geometry Formats

I-DEAS FTL l Optegra Visualizer l STL
l
FLUENT4 FLUENT5 TGRID FIDAP GAMBIT I-DEAS UNV (Universal format) ANSYS PLOT3D (Formatted) NASTRAN PATRAN HYPERMESH
UGM 2000
Data exchange via Mesh/Faceted Geometry-2

w
PLOT3D files with Iblanking and/or of binary type

Use tfilter fe2ram from an operating system command prompt to first convert it to a Fluent/Fidap mesh file Import the resulting mesh in Gambit.
w w
Import of Mesh with hanging nodes is not supported Mesh Files

Boundary types are not preserved during import. Generates faceted geometry from surface or volume mesh import. Use Virtual Geometry operations to work with entities. Convert virtual geometry to real if needed. Similar to mesh but defining triangles unsuitable for meshing STL lacks zone grouping

Faceted Geometry Files

Use Feature Angle to separate faces Works well for well-defined edges; otherwise use as last resort.
Company Confidential Copyright 2000 Fluent Inc. All rights reserved. 12
UGM 2000
CAD-to-Gambit Flowchart Summaries

In general, translation options listed in order of decreasing preference (left to right). Some options require third party translator software. Best translation path depends on quality of CAD data (model).
UGM 2000
Pro/E-to-Gambit Flowchart
Pro/Engineer
STEP
ProSAT Translator
Direct (STEP)
Optegra Visualizer
Mesh
STL
IGES*
ACIS
(faceted geometry)
(real geometry)
Gambit UGM 2000

*IGES native may produce virtual geometry

Catia-to-Gambit Flowchart
Catia
STEP
Catia-ACIS Translator
IGES Solids
(AIX only)
IGES Surfaces *
Mesh
STL
(faceted geometry) ACIS
(real geometry)
Gambit UGM 2000


I-DEAS-to-Gambit Flowchart
I-DEAS
STEP
IGES* MSBO
Faceted Part File (FTL)
Mesh
STL
(faceted geometry)
(real geometry)
Gambit UGM 2000


Unigraphics-to-Gambit Flowchart
Unigraphics
Parasolid
UnigraphicsACIS Trans.
STEP
IGES*
Mesh
STL
ACIS (faceted geometry)
(real geometry)
Gambit
UGM 2000
SolidWorks-to-Gambit Flowchart
SolidWorks
Parasolid Direct ACIS Export
STEP
IGES*
Mesh
STL
(faceted geometry) ACIS
(real geometry)
Gambit
UGM 2000
CADDS-to-Gambit Flowchart
CADDS
STEP
CADDS-ACIS Translator
IGES*
Mesh
STL
ACIS (faceted geometry)
(real geometry)
Gambit UGM 2000


Translator Vendors
Pro/E ACIS
w w
Marchetti Engineering; (http://www.marchettieng.com) Spatial Technology; (http://www.3dshare.com) Theorem Solutions Ltd.; (http://www.theorem.co.uk) CORETECH International; (http://www.coretech-int.com) Spatial Technology; (http://www.3dshare.com) Theorem Solutions Ltd.; (http://www.theorem.co.uk) Theorem Solutions Ltd.; (http://www.theorem.co.uk)
Catia ACIS
w w w
Unigraphics ACIS
w
CADDS ACIS
w
UGM 2000
Geometry
Checking geometry/topology
Healing real geometry Converting non real geometry to real Construction and cleanup strategies
UGM 2000
Check Real Geometry

Checks for geometrical and topological inconsistencies.
w w
Topology problems must be fixed before meshing Geometry not C1, C2, G1or G2

Indicates lack of parametric/geometric continuity Operations like real booleans, splits and sweeps may fail
Use virtual splits as fallback
Do not prevent meshing
w w
Fix real geometry problems by healing and/or by regenerating entities Fix topology and virtual/faceted geometry problems by deleting (hiding) and reconstructing entities
UGM 2000
Geometry
Data exchange with other CAD/CAE systems Checking geometry/topology
Healing real geometry

Converting non real geometry to real Construction and cleanup strategies
UGM 2000
Healing Real Geometry-1

Healing is designed to detect and correct accuracy problems in ACIS models ACIS (geometry kernel of Gambit), a high precision modeler, needs all entities to satisfy stringent data integrity checks Geometry imported from other CAD systems often lacks the required accuracy & precision due to:
w
Inherent numerical limitations in the original CAD system w Limitations of data transfer through neutral file formats w Differences in tolerance settings between the original CAD system and Gambit
Three phases of Healing process:

w
Geometry simplification w Stitching w Geometry building
UGM 2000

Geometry simplification
w
Converts spline surfaces to corresponding analytic forms (e.g., planes, cylinders, circular cones etc.) wherever possible w Results in a reduction of data size & speed improvements in geometric operations.
w
Geometry simplification tolerance With tighter tolerance, only spline surfaces which are exact analytic surfaces get simplified With relaxed tolerance, approximate analytic fits to spline surfaces are obtained. It may increase the gap between surfaces and healing in subsequent operations would be more difficult The default tolerance of 0.0001 should provide very good approximation in most cases w For some cases, overall results may be better if simplification is disabled
UGM 2000

Stitching
w w
Stitch together the loose faces. Similar to volume stitch but can handle the gaps and does some geometry cleaning on the stitched data to handle small edges occurring in the body. Main Characteristics : Handles varying gaps Resolves multiple vertices Handles small edges Split edges appropriately Ensure consistent face normals Stitching tolerances: Incremental stitching. Starts with minimum tolerance and increases in steps towards maximum tolerance Minimum tolerance must always be smaller than the length of the smallest edge in the model Maximum tolerance denotes the largest gap in the model. The result of stitching could give one or more acis volumes.
UGM 2000

Stitching
UGM 2000

Geometry Building
w w w
Builds the geometry as necessary to correct the gaps & inaccuracies in the model. Improve precision of face, edge, and vertex data Recalculate the bad curves and points by recomputing intersections.
Transversal Intersections : Gaps are filled by extending the adjoining surfaces and recomputing the intersection
UGM 2000

Geometry Building
Tangential Intersection of Analytic Surfaces : Surfaces are snapped to each other using linear transformations
Tangential Intersection of Spline Surfaces: Correction via control points modification
UGM 2000
Import of Point Data

w
ICEM Input Allows import of curves & surfaces that are defined by rows of points w Vertex Data Allows to import large number of vertices
w
File Format :
where, Npc = number of points per curve, Nc = number of curves, n = total number of points.
Npc Nc X1 Y1 Z1 X2 Y2 Z2 .......... Xn Yn Zn
w
For vertex data import Curve specific information is not needed
UGM 2000
Importing a GeoMesh meshed model-1

w
Read the mesh file into GAMBIT using mesh import

Enable the angle-based edge splitting option during mesh import. Set MESH.MODIFY.EDGE_SPLIT = 1 Specify a feature angle
Conversion of mesh faces/edges to topological faces/edges based on feature angle & boundary information.
Feature angle = 0, conversion based on boundary information alone
Adjust topology using the mesh modify forms (volume/face)

Unclick the Keep Original Edge toggle to remove existing edges Adjust the angle slider to minimize local edits Fine tune the edge designation by

Adding individual mesh edges by picking Deleting individual mesh edges by picking Removing spurs using the spur picker
UGM 2000
Importing a GeoMesh meshed model-2
Geometry converted is non real (faceted) For real specific operations (e.g., booleans, sweep etc.)

Use Modify Meshed Geometry/Split Meshed Face to split the submapped faces into faces with map mesh. Use Convert Faces/volumes to convert the non real geometry to real
UGM 2000
Geometry
Data exchange with other CAD/CAE systems Checking geometry/topology Healing real geometry
Converting non real geometry to real

Construction and cleanup strategies
UGM 2000
Conversion of Non-Real Geometry to Real-1

Vertex Conversion
w w
A non-real (faceted/virtual) vertex is converted to a real vertex The topology and mesh (if it exists) is preserved
Edge Conversion
w w w w w
Convert a faceted/virtual edge to a real edge The topology and mesh (if it exists) is preserved Lower topology (vertices) is converted as necessary A real spline is fit through number of sampling points on the virtual edge The number of sampling points can be changed through Edit Defaults :
GEOMETRY.EDGE.VIRTUAL_NUM_SAMPLING_POINTS
UGM 2000

Face Conversion
w w w w w
Convert a non real face with mapped mesh to a real face Topology and mesh are preserved Lower topology (edges) is converted first A net surface is created using the real boundary edges and temporary acis edges generated along the grid lines The existing mesh is projected onto the new geometry
Limitation
w w
The non real face must have a mapped mesh on it In case of hosted virtual, the host entities become visible
Boolean/splits and sweep operation can be performed Can be used to replace invalid/corrupt face in the model
UGM 2000

Volume Conversion
w w w
Convert a non real volume to a real volume Topology and mesh are preserved Lower topology (faces) is converted first
Limitation
w w w w
All lower topology must be capable of conversion In case of hosted virtual, the host entities become visible A volume with void can not be converted A volume with a virtual guest can not be converted
Can be used to create a real volume from an imported structured mesh

UGM 2000
Geometry
Data exchange with other CAD/CAE systems Checking geometry/topology Healing real geometry Converting non real geometry to real
Construction and cleanup strategies
UGM 2000
Cleanup Strategies: Virtual Geometry

More accurately described as Virtual Topology
w
Modifying size and shape of boundary surfaces while constrained by underlying (real) geometry definition.
Can be created or derived from real, virtual, and faceted entities Cannot be used for Boolean operations, sweeps (except edge), etc.
Two objects that share the same underlying geometry but different topologies.
UGM 2000
Typical Cleanup Procedure for Imported Data

w w w w w w w w w w w
Delete unnecessary geometry Check validity of the geometry (visual + check commands) Correct invalid geometry (Healing and/or reconstruction) Check connectivity by color coding Eliminate short edges Check connectivity Create additional geometry and form volume Simplify/edit edges, faces, volumes Decompose volume, if necessary Mesh the geometry Plan ahead

Some operations will not work with virtual geometry (booleans, sweeps except edges, revolves, certain splits) Postpone operations that create virtual entities.
UGM 2000
Delete Unnecessary Geometry and Check Connectivity

Delete all unnecessary geometry
w w
Extra geometry added in CAD generation process Deleting virtual geometry typically will not remove hosts or lower entities.
It may be simpler to hide virtual objects by assigning them to a group and hiding the group through the Specify Display Attributes form.
Check connectivity by color coding the entities

w
Start by changing the color to show the connected and unconnected entities
Colors are for edges and vertices

White - Stand-alone entities Orange - Unconnected entities (e.g., edge connected to one face) Dark Blue - Connected entities (e.g., edge connected to two faces) Light Blue - Multiple connections (e.g., internal face)
UGM 2000
Eliminate Short Edges

Identify shortest edges using Highlight shortest edge button on Edge Connect form. These edges may cause problems in Edge Connect and T-junction operations. Merge shortest edges with adjacent edges when possible

May require a face merge first (merges require common upper topology) Face merge may require some other edge connect operation.
Connect vertices (collapsing short edge between)

w w
Eliminate multiple vertices occupying same location. Two vertices defining a short edge can be (force) connected together.
Default parameter GEOMETRY.VERTEX.CONNECT_REMOVE_SHORT_EDGE must be set true. Company Confidential Copyright 2000 Fluent Inc. All rights reserved. UGM 2000 41
Connect Edges
Connecting edges provides connectivity between faces. This enables faces to be stitched together to form volume.
w
New option to preserve first edge shape during virtual edge connect Typical Procedure: Specify Real and Virtual Connect
Real connects attempted first. Specify initial Tolerance or Shortest Edge % Connect on all edges.
Repeat above step with successively larger tolerances. Include T-junction option as final step.
Invoking too early may result in very small edges.
Force Connect remaining disconnected edges. w Failure to stitch together volume will result in error message identifying problem edges.
UGM 2000
Connect Edges: Tolerances

Tolerances used for connect should be much less than mesh size.
w
Mesh within the tolerance region gets pushed back to edge.

For faces separated by a large gap, create new face to fill the gap. For faces that overlap by large amount, split each face with the intruding edge and form new face in center.
Faces overlapping
Faces with gap
Faces connected
Tolerance used to connect edges to create two connected virtual faces.
UGM 2000
Connect Edges: T-Connect Option

Using T-Connect Option with relatively low tolerance can generate unwanted small edges.
w w
Use Highlight Shortest Edge to check length before and after operation. Can pick which vertices are to be involved in edge splits in Vertex list box (default is all).
Small edges formed as a result of improper use of T-Connect Option.
Tolerance used to connect edges will account for small gaps but not the larger ones.
UGM 2000
Create Geometry and Form the Volume

You may need to create additional geometry (outlet extensions, bounding volumes, etc.)
w
w w w
Some of this (except edge sweeps) may need to be done before Virtual Edge Connects so that you can perform real operations on the geometry Bridge real and virtual geometry together with virtual geometry Face/face splits can be done with real geometry to trim surfaces Additional geometry for future decomposition may be created now Watch for error messages when creating the volume--they should indicate where a problem may be occurring
Use face stitch command to generate virtual volume

w
UGM 2000
Simplify/Edit faces
w
Eliminate sliver faces

Merge face with neighbor
Avoid merging together connected faces that form a sharp angle ( 90).
Merge remaining edges Split the face to isolate the bad angle Merge the new face to an adjacent face Merge the edges Merge for similar faces and sliver faces Collapse for symmetry, blends, fillets, etc. (collapse adds extra layer of topological information)
Eliminate sharp corners and angles

Collapse versus merge

If tolerance is larger than element size, or if element size is smaller than faces that were merged/collapsed, meshing may fail on merged surfaces
UGM 2000
Decompose Geometry
If necessary, decompose various entities for desired mesh When decomposing a virtual volume
w
Gambit 1.2.4 and higher allow a virtual volume to be split by multiple faces

All split tool faces must be connected together Must share boundary edges with volume boundary Delete the volume or just make it invisible (keep lower topology visible). Stitch desired volumes together separately
If volume is complex enough, volume split may fail. If so:

UGM 2000
Virtual Cleanup During IGES Import

Attempts virtual cleanup through automated sequence of Connects/Merges.
w w
w w w
w w
Merges edges based on length. Using merge tolerance. Merges edges based on angle. geometry.edge.VIRTUAL_MERGE_MIN_AN GLE Real connects of vertices, edges, faces. Virtual connects of vertices, edges, faces. Using connect tolerance. Edge connects with T-Option. If any changes are made, repeats Virtual connect of edges, faces. Attempts volume-stitch-virtual. Can also be used after import
Open the IGES Import form Clear the File Name field Click Virtual Cleanup checkbox Click Accept
UGM 2000
Boolean Operations & Imprinting-1

Boolean operations involving connected geometry can sometimes produce unexpected results as a result of imprinting.
Begin with two separate volumes and a face connected at edges A & B. Boolean subtract results in two separate volumes and an elliptical face (next slide). Disconnecting edges A & B prior to subtract produces expected result.
UGM 2000
Boolean Operations & Imprinting-2

Imprinting involves taking the result of the boolean operation and creating new volumes based on resulting faces in addition to any connected faces such that boundary information is preserved (nonregularized unite).
Subtract operation results in cube with cylindrical void. The bounding faces of this object can form new volumes by utilizing the connected interior face. Nonregularized unite is invoked since a connected face is recognized as internal. Boundary information (includes connected interior face) is preserved. Result is two volumes and an elliptical face. UGM 2000
NURBS Surfaces and Boolean Operations

Be aware of issues involving general NURBS surfaces and analytic surfaces (e.g., cylinders)
w
NURBS surfaces do not represent cylinders or spheres exactly
Example: a swept toroidal surface does not lie on a cylinder or conic surface
w w w
The NURBS surface is not coincident within the tolerance - it cannot mathematically be such Booleans between coincident analytic and NURBS surfaces will be unpredictable Adjust the analytic surface in/out appropriately to obtain the desired result
UGM 2000
Real Geometry: Construction Tips-1

w
If a particular boolean/split operation fails to work
Could be due to complexity/quality of the model or due to difficulty in finding imprints of connected entities

Disconnect the face/volume with adjacent entities by copying it Delete the original face/volume Perform the boolean/split on the copied entity Connect them back before meshing
Use alternative operations

w
e.g., an alternative to a split is:

Get intersection of tool and the target while retaining the target Subtract the result (intersection) from the target while retaining the tool Do a connect
If the tool is enclosed by the target, intersection of the two is not needed.
UGM 2000

Gambit 1.2.0 & higher support booleans of multiple entities (faces/volumes) in one step
w
Use intersection/subtraction option to split one entity with multiple entities
Occasionally, real volume stitch may produce unwanted edge splits

w w w w w
ACIS-specific problem (incorrect topology being generated) Use Heal Faces in place of volume stitch command to create the volume May need to disconnect the faces if connected to other entities Reconnect them before meshing Virtual volume stitch can also be used
UGM 2000

w w w w w
To create real face by wireframe on noncoplanar surface, use a set of 3 or 4 edges per face Use alternative methods of face creation (e.g., net surface) wherever applicable New face creation methods and face primitives are available with Gambit 1.2.0 and higher Combine primitives, booleans and bottom-up tools for faster model building Addition of new bottom-up geometry creation tools includes
Edge-Edge Intersections

For both real and virtual Option to specify a tolerance For both real and virtual
Edge Projection on face
Planar Arc Creation

UGM 2000

w
Additional face creation tools:

Rectangle primitive Circle primitive Ellipse primitive Polygon face from vertices Circular face from vertices Elliptical face from vertices
rectangle
circle
ellipse
Polygon face from vertices
Projection of Edge on the surface
UGM 2000

If view manipulation is too slow
w w
Turn visibility of the silhouette off using display attribute form Turn off the silhouette flag off for new faces by using the default GRAPHICS.GENERAL.ADD_SILHOUETTES_AT_FACE_CO NSTRUCTION
UGM 2000
Meshing
Cooper Tool
Stairstep Meshing Boundary Layers Meshing Tips
UGM 2000
Cooper Tool: Cooperable Geometry

A Cooperable geometry must have at least two end caps
w w
Defined at logical ends of volume For example, a torus needs to be split into two halves before it can be meshed using the Cooper Tool If more than one face forms an end cap, the faces should have nearly 180 degree angles between them Sharp angles will reduce the quality of the mesh
Multiple faces may form a single end cap

w w
All end caps must be logically parallel along the logical axis direction All source faces must be connected by valid side faces All side faces must be submappable
UGM 2000
Automatic Classification of Geometry

GAMBIT will first try to classify geometry as Mappable or Submappable before attempting to classify it as Cooperable. Attempting to classify a geometry as Cooperable:

Uses angles between faces to search for logical source faces. Will find multiple source faces to be used as single cap if angle between faces is appropriate. Remaining faces will be used as side faces and must be submappable. Source faces must be specified GAMBIT will attempt to force a submap scheme on all other faces

To force GAMBIT to use the Cooper tool:

If this fails, reconsider source face selection or vertex settings of side faces The Cooper process may still fail if forced submap is poor.
Some geometric decomposition may be necessary

UGM 2000
Decomposing Geometry for Cooper Tool

Find logical axis directions Decompose into volumes following logical axis directions
w w w
All cutting faces must be submapped. Use real or virtual operator. Ensure two end caps (no toroidal volumes). Only one volume can be meshed at a time. When the faces of a volume are meshed, they do not take into account the meshing schemes or requirements of adjoining volumes . Make sure that the face meshes from one volume can be used by another volume that shares those faces.

Watch for imprint issues on cut faces

w w
Add split for exact matches.
Split Meshed Face can be useful here.
Further decompose for complex imprints. Company Confidential UGM 2000
Current Imprinting Limitations-1

w w
Splitting of meshed sources:
Existing mesh concerns. Loop on one end, two faces on opposing end. Cooper tool doesnt know which face should have the loop imprint. Similar to inner loop placement problem. Cooper tool is unable to determine where or even if inner loops intersect. Linked sources have duplicate meshes which can conflict with need to imprint nodes on source faces. If there is no imprint involved, linked sources are not a problem.
Inner loop placement:

Inner loop to inner loop intersections:

Linked sources:

UGM 2000
Current Imprinting Limitations-2

Impossible to create a logical cylinder the barrel of which is mappable Can not imprint on a source face with an existing mesh
Cooper-able volume with internal edge loops Dual enclosed loops on source faces
Can not imprint the mesh of face A on face B as they are linked together
UGM 2000
Location of Interior Nodes

w w
Side face nodes are used to define a least square fit transformation to get interior nodes. Boundary weighting default in cooper area used to help control interior node placement.

Generally ranges from 0.5 to 3. Higher value (3) pushes distortion inward.
In some case transformation anomaly (noise in transformation) may result in having inverted elements
Use MESH.COOPER.TRANSFORMATION_TYPE default to fix it. If set to 1, transformation is based on translation vector between gravity centers of opposing node loops
Cells of negative volumes may also be created in a volume with a highly concave source face. To fix it
Use Equipotential volume smoothing
UGM 2000
Guiding Interior Node Placement

Split with judicially placed side faces.
w w w
Additional side faces provide additional exterior nodes for control of interior node creation. Capture concavities or shape changes. Add consistent twist controls.
Boundary_Weighting default can control how nodes are pushed away from boundaries (toward interior of volume). Eliminate sharp side angles by splitting into side/cap face combinations.
UGM 2000
Meshing
Cooper Tool
Stairstep Meshing
Boundary Layers Meshing Tips
UGM 2000
Stairstep Algorithm-1
w w w w w w
Base mesh is trimmed to the geometry No decomposition needed A new faceted volume results after meshing Stairstep surface along the boundaries which are not aligned with the base mesh Volume with voids can be meshed Local mesh refinement possible
Presence of hanging nodes in transition region
Can be controlled by edit defaults (STAIRSTEP_MESH_TYPE)
Option to use a simplified template mesh for initial overlay grid

Template volume should completely surround the volume being meshed Greatly improves the desired density and elements quality of the mesh.
UGM 2000
Stairstep meshing: original volume
Stairstep meshing: faceted volume
UGM 2000
Option for Closer Surface Approximation

Removes surface elements whose centers are outside the volume Controlled through Edit default: MESH.GOCARTS.CLOSER_SURFACE_APPROXIMATION
Should be turned off to speed up the meshing process
Limitations
w w w w w
Topological connectivity with adjacent geometry is not maintained Does not match existing meshes on adjacent boundaries Internal faces are not supported Existing mesh on any portion of the geometry is not allowed Boundary layers are not honored
UGM 2000
Edge Mesh Form

A new toggle button of Use first edge settings
w w w
When ON, first edge in the pick list is used to update the form Removal of any edge from the list does not change settings of the form Can be used to copy the settings from a meshed edge to unmeshed edges
Deactivate the Remove old mesh option or deselect the first picked edges before Apply, if the meshed edge is part of a meshed face
If the toggle button is off, each newlyadded edge updates the form
UGM 2000
Meshing
Cooper Tool Stairstep Meshing
Boundary Layers
Meshing Tips
UGM 2000
Boundary Layer Overview-1

Boundary Layers are rows of elements growing out from a boundary into the domain They are used to locally refine the mesh in the normal direction from a face or an edge Boundary Layers are essential for most fully-automatic meshing schemes, but they can also be used in schemes based on mapping or primitives A single Boundary Layer can be attached to several face/edge pairs and/or volume/face pairs
UGM 2000
Boundary Layers: Overview-2

Speed/ Robustness greatly improved in GAMBIT 1.3.0
w w
BL display can be turned off New defaults for speed improvements:

QUICK_N_DIRTY: skips projection during graphics presentation Temporary display may look less accurate USE_FACET_EVALS: option to use faceted evaluation in place of exact evaluation
Significant speed improvements while attaching boundary layers to complex NURBS surfaces
UGM 2000
Boundary Layer Overview-3

w w w w
Temporary BL mesh created Made permanent on accept Goes through meshing code for visibility--sometimes slow Turn off visibility in Display Attributes form or use Edit Default
BOUNDARY_LAYER_VISIBILITY_AT_CONSTRUCTION BL attachments are still indicated by arrows For a face/edge attachment, the arrow starts from the middle point of the edge and points towards the label (ID) of the face For a volume/face attachment, the arrow starts from the center of the face and points towards the label (ID) of the volume
If visibility is off

UGM 2000

Internal Continuity
w w
Allows boundary layers to be formed with no crossover regions (vertices become sides) Must be ON for tet/hybrid meshing
Internal Continuity ON UGM 2000

Internal Continuity OFF


Wedge Corner Shape:
w w
Applicable at corner or reversal vertex ON => Wedge shape, OFF => Block shape
UGM 2000
BL & Vertex Types: End Case

BL mesh butts up against adjoining edge BL mesh utilizes adjoining edges mesh If BL is attached to adjoining edge on a face, a block of overlap elements is created where the two BL meshes meet
UGM 2000
BL & Vertex Types: Side Case

Angle at vertex is bisected Set of nodes is created along bisection vector These nodes are used by BL mesh above the edge in the BL attachment If BL is attached to both edges, BL meshes share the nodes created along bisection vector
UGM 2000
BL & Vertex Types: Corner Case

Nodes are created along vector defined by one-third of the angle between the edges BL mesh uses this set of nodes If BL is attached to adjoining edge,
w w w
Second set of nodes projected along vector defined by twothirds of the angle between the edges BL mesh above adjoining edge uses these elements Specialized mesh region created to connect the two BL regions created above the individual edges (choice of two patterns, block shape & wedge shape)
UGM 2000
BL & Vertex Types: Reversal Case

Nodes are created along vector defined by one-fourth of the angle between the edges BL mesh uses this set of nodes If BL is attached to adjoining edge,
w w w
Second set of nodes projected along vector defined by three-fourths of the angle between the edges BL mesh above adjoining edge uses these elements Two specialized mesh regions created to connect the two BL regions created above the edges
UGM 2000
BL & Vertex Types: for BL only

Vertex types may be changed for Boundary Layers only Allows desired BL creation in regions near vertices while maintaining desired face or volume meshing scheme
Example : Meshing a circular face with Map (square topology) and boundary layers
Vertex types = End, for mesh scheme Vertex types = Side, for boundary layers
UGM 2000
Meshing
Cooper Tool Stairstep Meshing Boundary Layers
Meshing Tips
UGM 2000
Meshing Tips-1
Meshing geometry of repeated pattern (Periodic)
w w w w w w w
Mesh one of the identical sections Use copy with mesh option to complete the model It creates a hard link (to copy mesh) Faces at the interface are not connected Connect would not work until faces are unlinked, which would also delete the mesh Export the mesh with unconnected region Fuse the faces at the interface in Fluent 5 solver to have proper connectivity. Geometric operations are not allowed on mesh-linked entities
Use Mesh link at the end, just prior to meshing

w
UGM 2000
Meshing Tips-2
w
Mesh with periodic boundary condition for Fluent 5

Tfilter fe2ram is used to convert Gambit mesh file into Fluent 5 mesh file Fluent 5 requires both face pairing as well as node pairing for periodic bc Gambit mesh file with periodic bc maintains both face and node pairing However, tfilter fe2ram does not always ensure node pairing In such cases, Fluent 5 fails to recognize the periodic bc correctly A native Fluent 5 export from Gambit (planned for later this year) will resolve this

The recommended procedure for now is:

Hard link the periodic faces in Gambit to ensure identical mesh Define the bc type to be wall instead of periodic in Gambit Export the mesh and use make periodic command in Fluent 5 to assign a periodic bc Make sure to check the axis of rotation in Fluent 5, before using make periodic for rotational periodic cases
UGM 2000
Meshing Tips-3
Poor mesh by mapper on highly curved surface Projection to the surface distorts the mesh Limitation of algorithm UGM 2000
Smooth the face mesh by

winslow to fix it
Meshing Tips-4
Final exact projection of mesh on the surface

May take long time or produce skewed elements on complex/bad spline surfaces Should be turned off (using the default MESH.FACE.PROJECT_TO_SURFACE) Check the mesh to ensure desired accuracy of geometry representation
Meshing fails with sizing function message

Indicate large variation of mesh size over the domain Adjust the edge meshing Splitting of the face may be needed to reduce the mesh size variation.
UGM 2000
Meshing Tips-5
Exporting a surface mesh for Tgrid

Change the export behavior using the default FILE_IO.FLUENT5.EXPORT_SURFACE_MESH_ONLY Export the surface mesh for faces with user specified boundary conditions To export mesh for large number of faces without specified bc :

Change the solver to generic and export a Gambit neutral file Import the neutral file in Tgrid
2-D Mesh export for Fluent

w
Ensure the model to be in xy plane (z = 0).
UGM 2000
Meshing Tips-6
Mesh export fails due to lack of memory
w
Export a neutral file from Gambit w It can be imported directly in Fluent 5, or w Use tfilter fe2ram from outside the Gambit to convert it into Fluent5 format
Number of triangles on a single face exceed the default limit (100,000)

w
Increase the limit using the default MESH.TRIMESH.MAX_FACES w A value of -1 indicate no restriction
If there is a resource constraint

w w w w w
Mesh the whole model in several parts Mesh one part, export the mesh and then delete it but keep the surface mesh at the interface (for conformal mesh) Do the same for each part. Merge all the meshes with tfilter tmerge3d or by reading them in Tgrid Duplicate nodes at the interface can be merged together either in Fluent 5 by fusing the zones or in Tgrid by merging the nodes.
UGM 2000
Gambit Tools
Parametric modeling
UGM 2000
Defining Parameters
Parameters can be defined through command line or Edit parameter Parameters:
w w w
Scalar or array Numeric or string Defined by: $param = value Must start with $ Is not case sensitive ($length same as $LENGTH)
Name of parameter
w w
Can be defined any time prior to use Do loops and IFTHEN-ELSE blocks are supported
UGM 2000
Important String & Database Functions

NTOS(exp) convert number to string Example: If $i = 1: wall.+ NTOS ($i) = wall.1 ID of last-created entity, tag = ve_id or 1 (vertex) ed_id or 2 (edge) fa_id or 3 (face) vo_id or 4 (volume) gr_id or 5 (group) cs_id or 6 (coordinate system) bl_id or 7 (boundary layer) Example: If five vertices has been created: LASTID(ve_id) or LASTID(1) = 5 UGM 2000
LASTID(tag)
Current Limitations
Parameter definition in the Edit - Parameters form does not produce journal commands. Parameters and expressions can not be used within the GUI. Parameters cannot be defined inside DO loops or IFTHEN-ELSE blocks. Journals produced by GAMBIT contain the values of parameters and expressions, not the parameters/expressions themselves.
UGM 2000
Journal Files for Parameterization

Build initial model with GUI
w w w
First use a set of basic numerical values. Mesh model and attach zones. Save journal file with unique name. Define key parameters at the top of the file and include comments. Replace values with parameters throughout. Replay the journal to make sure that parameters were defined and used correctly. List of all parameters and their current values can be checked:

Editing the journal file:

w w
Check the journal file:

w w
The parameter list - command The Parameter form

UGM 2000
Parametric Study
Test the model for the most extreme values first. Advanced parameterization might be needed to avoid bad cell aspect ratio/skewness.
w
Example: Edge mesh density as a function of distance intervals (4 + (INT($fact*($h2 - $h1)))))
UGM 2000
Parameterization: Tips
Use mapped mesh when parameters have large variation span, since mesh can be stretched without severe distortion (compared to paved mesh). Use different journal files for different parameter combinations.
w
Example: Pipe junction
Pipe intersection
These are two topologically different models (3 faces, 8 edges vs. 2 faces, 5 edges)
Do not use virtual mesh splits, since these are nodenumber dependent.
UGM 2000

Gambit

Enviado por

Dados do documento

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

Gambit

Enviado por

Direitos autorais:

Formatos disponíveis

2000 UGM Gambit: Tips & Tricks

June 12, 2000 Shyam Kishor Roman Tomaszewski

Copyright 2000 Fluent Inc. All rights reserved. 1

Data exchange with other CAD/CAE systems

Using virtual geometry for cleanup Construction tips

Copyright 2000 Fluent Inc. All rights reserved. 2

Copyright 2000 Fluent Inc. All rights reserved. 3

Data exchange with other CAD/CAE systems

Copyright 2000 Fluent Inc. All rights reserved. 4

Data exchange with other CAD/CAE systems-1

Copyright 2000 Fluent Inc. All rights reserved. 5

Data exchange with other CAD/CAE systems-2

Standard - based options

Use of neutral file format to exchange data STEP IGES

Copyright 2000 Fluent Inc. All rights reserved. 6

Data exchange via STEP

Pro/ENGINEER at no additional cost Most others as an add on

STEP supports solid models

Creates real Gambit (ACIS) volumes after import.

Topology/connectivity-related information is maintained Exports real geometry, including solid volumes

Copyright 2000 Fluent Inc. All rights reserved. 7

Data exchange via IGES

Gambit provides two options for IGES import Spatial

Copyright 2000 Fluent Inc. All rights reserved. 8

Geometry Import Check Geometry

Use Virtual Geometry

Spatial Translator Check Geometry

Use Virtual Geometry

Data exchange via Mesh/Faceted Geometry-1

Faceted Geometry Formats

Copyright 2000 Fluent Inc. All rights reserved. 11

Data exchange via Mesh/Faceted Geometry-2

PLOT3D files with Iblanking and/or of binary type

Import of Mesh with hanging nodes is not supported Mesh Files

Faceted Geometry Files

CAD-to-Gambit Flowchart Summaries

Copyright 2000 Fluent Inc. All rights reserved. 13

Gambit UGM 2000

*IGES native may produce virtual geometry

(faceted geometry) ACIS

Gambit UGM 2000

*IGES native may produce virtual geometry

Faceted Part File (FTL)

Gambit UGM 2000

*IGES native may produce virtual geometry

ACIS (faceted geometry)

Parasolid Direct ACIS Export

(faceted geometry) ACIS

ACIS (faceted geometry)

Gambit UGM 2000

*IGES native may produce virtual geometry

Copyright 2000 Fluent Inc. All rights reserved. 20

Data exchange with other CAD/CAE systems

Copyright 2000 Fluent Inc. All rights reserved. 21

Check Real Geometry

Use virtual splits as fallback

Do not prevent meshing

Copyright 2000 Fluent Inc. All rights reserved. 22

Data exchange with other CAD/CAE systems Checking geometry/topology

Healing real geometry

Copyright 2000 Fluent Inc. All rights reserved. 23

Healing Real Geometry-1

Three phases of Healing process:

Geometry simplification w Stitching w Geometry building