Best practices#

This page is the practical companion to How GeometryAI works: how to get a first GeometryAI mesh, what to change when it is not what you wanted, how to run a refinement study, and how to tell the mesher which region is the fluid for each common type of case.

Your first GeometryAI mesh#

The mesher always returns a valid surface, so you do not have to get everything right before the first run. Decide how big the mesh is allowed to be, mesh with the defaults, then fix what you see.

  1. Set the size budget before you mesh. Use Target surface node count as the single lever for how big the surface mesh is, and leave Surface max edge length generous so it does not silently dominate (see Surface mesh density). Deciding this first is what protects you from the expensive mistake: a mesh that comes out too coarse is quick to spot and quick to fix, whereas length scales entered far finer than intended, or in the wrong unit, produce an enormous mesh and very long meshing times before anything is there to look at.

  2. Keep the other defaults and generate a mesh. Geometry accuracy is set automatically when GeometryAI is enabled and is a sensible baseline for the bulk of the geometry.

  3. Read the process log. It tells you whether the mesher stopped early before reaching the requested accuracy, and it lists the refinements it found. If it reports early termination, coarsen the global accuracy or move the fine accuracy into a local refinement.

  4. Look at the surface and fix things locally. A lost trailing edge, a smoothed-over fillet or an open gap is a job for a local Geometry Refinement on those faces, not for a finer global value (see Local refinements: tightening only where it matters). To check the shape as a whole rather than feature by feature, colour the mesh by GAI Deviation Distance in the Surface Mesh Diagnostics tool: it is the distance from each mesh node to the input geometry, so it shows at a glance where and by how much the rebuilt surface moved away from your CAD.

  5. Check the fluid region. Make sure the mesh encloses the region you meant to simulate: outside the model for external aerodynamics, inside the cavity for internal flow, the gap between model and tunnel for a wind-tunnel case. Defining the fluid domain below explains the three controls that decide this.

Only once the mesh resolves the geometry you care about is it worth tuning the individual density controls, and then a refinement study tells you whether the answer still depends on the mesh (see Running a mesh refinement study).

What to reach for when something looks wrong#

What you see

What to do

The CAD has gaps, leaks or small holes you want closed

Set Sealing size to the largest opening you want sealed, or override it locally on the affected faces; prefer this over manual CAD repair. See Sealing gaps and holes.

A hole or slot you wanted open has been sealed

Lower Sealing size below that opening, or set it to zero on those faces through a Geometry Refinement.

A trailing edge, fin or thin wall has disappeared

Turn on Preserve thin geometry on those parts through a Geometry Refinement, or give them a finer local Geometry accuracy. See Preserving thin features.

Internal parts the flow never sees are being meshed

Turn on Remove hidden geometry; adjust Min passage size if a region is wrongly kept or wrongly removed. See Removing hidden geometry.

A small feature is smoothed over

Add a Geometry Refinement with a finer Geometry accuracy on those faces, or in a Box around the feature, rather than lowering the global value. See Local refinements: tightening only where it matters.

The mesh is far larger, or meshing far slower, than expected

Check the unit of Geometry accuracy and the other input lengths first. Then coarsen the global Geometry accuracy and keep fine values local, and check whether Surface max edge length is binding. See Geometry accuracy: how faithfully the geometry is captured and Surface mesh density.

The node count overshoots Target surface node count

Surface max edge length is the binding constraint; make it more generous. See Surface mesh density.

The mesh stopped at a coarser accuracy than requested

Resource limits were hit. Coarsen the global Geometry accuracy or move the fine accuracy into a local refinement. See Geometry accuracy: how faithfully the geometry is captured.

The wrong region was meshed (inside instead of outside, or the tunnel was ignored)

Check Mesh exterior on each body and where the seed point sits. See Defining the fluid domain.

Running a mesh refinement study#

To study mesh convergence you want each level to be a uniformly finer version of the last, not a mesh where one constraint quietly took over. Use Target surface node count as the single driver and keep Surface max edge length in step with it:

  • Multiply Target surface node count by a refinement factor x (for example 2 for a finer level, 0.5 for a coarser one).

  • Scale Surface max edge length by 1 / sqrt(x) at the same time. Node density on a surface scales with the inverse square of the edge length, so this keeps the edge-length cap consistent with the requested node count and prevents it from binding unexpectedly between levels.

Keeping the two in step means the curvature scaling continues to drive the mesh at every level, so successive meshes differ by a controlled, roughly uniform factor. If Surface max edge length is left fixed while only the node count changes, it eventually becomes the binding constraint and the meshes stop refining as expected (see Surface mesh density).

Where to set them: WebUI mesh parameters · target_surface_node_count · surface_max_edge_length.

Defining the fluid domain#

A surface mesh alone does not say which side of it the air is on. For a car in free air the fluid is outside the body; for a duct it is inside; for a car in a wind tunnel it is the gap between the two. When the GeometryAI workflow meshes an assembly it has to make that decision for every body, and three independent controls drive it:

  • Mesh exterior, set per body group, declares which side of a body the fluid is on (outside or inside).

  • Remove hidden geometry, a single global toggle, decides whether occluded interior faces are discarded.

  • Seed point volumes select which connected region is the fluid; the flood starts from them.

This section explains what each control does, how they combine, and which combination to use for the common simulation scenarios. The mechanics of generating the zones themselves (custom volumes, custom zones, the flood-fill workflow) are covered in Volume Mesher; this section is about choosing the settings that delimit the domain.

Note

These controls apply to the GAI surface mesher workflow. See Meshing for how the beta mesher and GAI toggles select each workflow.

Mesh exterior#

Mesh exterior, written mesh_exterior in the body-group settings, is a per-body-group flag (true by default) that declares which side of a body the fluid is on:

  • true (the default): the fluid is outside the body. The body is a solid the flow passes around, such as the object of study (a car, an aircraft, a building).

  • false: the fluid is inside the body. The body is an enclosure whose interior is meshed and whose faces bound the domain from the outside, such as a wind tunnel or a user-defined farfield.

The fluid domain is the region that is outside every mesh_exterior=true body and inside every mesh_exterior=false body. For a car inside a wind tunnel, that is exactly the gap between them: outside the car and inside the tunnel.

Because it defaults to true, most cases never set it explicitly: an external-aerodynamics model, and the walls that bound an internal-flow cavity, all keep the default. You only set false on a body that should contain the fluid, such as an enclosing wind tunnel or user-defined farfield. Setting such an enclosing body to true instead would tell the mesher the fluid is outside it, which is not what you want, and a seed point cannot make up for it (see the seed does not replace the flag below).

Where to set it: per body group in the geometry browser, see GUI Guide: Geometry. mesh_exterior is a beta feature and its interface may change.

Remove hidden geometry#

Remove hidden geometry is a single global toggle (off by default, GAI surface mesher only). When it is on, face classification runs on the mesh_exterior=true bodies and drops the faces that the flow can never reach, for example the seats inside a closed car body or the components inside an engine bay. Bodies set to mesh_exterior=false are not classified and are therefore unaffected.

With the toggle off you still obtain a valid mesh, but the occluded interior surfaces are retained, which adds elements that do not contribute to the external solution. Turn it on when the geometry carries interior parts that are hidden from the flow.

The setup reports three messages around this toggle:

  • With more than one body meshed as exterior and the toggle off, it recommends turning the toggle on; the recommendation is advisory and the mesh still runs.

  • Min passage size, Baffle face treatment and the baffle thicken extents require the toggle: in the meshing defaults they are rejected, in GeometryRefinement they are accepted but have no effect.

  • Hidden-geometry removal is not fully supported when the case generates more than one farfield, custom or seed point volume zone. The mesh still runs.

The parameter itself, together with Min passage size, Baffle face treatment and the baffle thicken extents, is described under Cleaning up imperfect CAD.

Where to set it: WebUI mesh parameters · remove_hidden_geometry · min_passage_size · baffle_face_treatment · baffle_thicken_outward · baffle_thicken_inward.

Seed points and flooding#

Within the fluid side defined by mesh_exterior, the mesher picks the connected region to mesh by flooding it from one or more seed points. When no seed point is supplied, the default seeds are the corners of the geometry bounding box, which is what makes ordinary external-aerodynamics cases work without any explicit seeding.

The seed selects and orients the fluid region; it does not change which side of a body is fluid. Place the seed outside the object for external aerodynamics, inside the enclosed region for internal flow (for example the cabin of an HVAC model), and in the gap between the model and an enclosing wind tunnel.

Important

A seed point is not a substitute for mesh_exterior. Seeding inside a body that is left at mesh_exterior=true does not turn its interior into the fluid domain; the flag, not the seed, decides which side of each body is fluid. An enclosing wind tunnel must therefore be mesh_exterior=false regardless of where the seed is placed.

Seed points describe a single fluid zone with GeometryAI, however many seed point volumes and points are defined; Zones produced by each definition covers that and how several zones are obtained instead.

Where to set it: WebUI seed point volume · SeedpointVolume (point_in_mesh); on the Python side the workflow is described in Volume Mesher.

Choosing settings per scenario#

The table below summarises the typical combination for each common scenario. Default seeding means the bounding-box corner seeds, with no explicit seed point.

Scenario

Mesh exterior

Remove hidden geometry

Seeding

External aerodynamics (car, aircraft) with an automated farfield

true on the model

On if the model has hidden interior parts; otherwise off

Default seeding (outside the model)

Internal flow (HVAC, duct, manifold)

true on the bodies bounding the cavity

Usually on, to discard surfaces outside the cavity

Seed point inside the cavity

Wind tunnel or user-defined farfield enclosing a model

false on the tunnel/farfield body, true on the model inside it

As needed on the model

Seed point in the gap between the model and the enclosure

Porous media

true on the model

As needed

Seed so the porous medium lies inside the meshed domain

../../../_images/gai_fluid_domain_scenarios.svg

Fluid-domain classification for the common scenarios. mesh_exterior sets which side of each body is fluid (outside a true body, inside a false body), and the seed selects the connected region to mesh.#

See also

Comparison with a standard wrapper#

The comparisons below show the input geometry, the result of a standard wrapper, and the GeometryAI surface for the same detailed regions. The red arrows highlight regions where the standard wrapper produces defects (intersections or non-manifold elements) that GeometryAI avoids.

Wing mirror and A-pillar: input geometry, a standard wrapper, and GeometryAI.#

Input geometry

Standard wrapper

GeometryAI

../../../_images/gai_mirror_input.png ../../../_images/gai_mirror_wrapper.png ../../../_images/gai_mirror_geometryai.png
Engine bay: input geometry, a standard wrapper, and GeometryAI.#

Input geometry

Standard wrapper

GeometryAI

../../../_images/gai_enginebay_input.png ../../../_images/gai_enginebay_wrapper.png ../../../_images/gai_enginebay_geometryai.png