STAR-CCM+ / PRE-PROCESSING

Surface Repair in STAR-CCM+: diagnose before you mesh.

Surface Repair is most useful when imported or tessellated geometry contains defects that can break wrapping, region extraction or volume meshing. The efficient workflow is diagnose → localize → repair → re-diagnose.

SHORT ANSWER

Use Surface Repair when the geometry itself—not the physics setup—is preventing a clean CFD topology. Typical targets are leaks, free edges, intersecting or duplicate surfaces, small holes, non-manifold topology and local defects that would later create poor cells or an incorrect fluid domain.

01

When Surface Repair is the right tool

Not every geometry problem should be repaired inside STAR-CCM+. If the original CAD model can be corrected cleanly upstream, that is often better because the change remains part of the design source. Surface Repair becomes valuable when you receive difficult third-party CAD, STL/tessellated data, legacy geometry, or a model where direct CAD repair would be slower than local CFD-oriented cleanup.

Good use

Closing local leaks, correcting topology, cleaning small defects and preparing problematic surfaces for wrapping or meshing.

Better upstream

Large design changes, dimensional corrections and features that should remain parametrically connected to the product CAD.

02

Run diagnostics before manually selecting faces

Geometry repair becomes inefficient when you inspect the model visually without knowing what type of defect exists. Start with the diagnostic tools and use their classifications to locate suspicious regions. Siemens describes Surface Repair as a way to identify and fix common geometry errors such as holes, overlapping/intersecting faces, missing or duplicate faces and non-manifold topology.

The useful question is not “does the CAD look okay?” but “is the topology watertight and suitable for the next operation?” A visually tiny gap can be more important to the fluid-domain extraction than a large cosmetic feature.

Practical check:

After every meaningful repair operation, rerun the diagnostic. A repair can remove one defect while creating or revealing another.

03

Choose the repair operation from the defect geometry

Several repair approaches may lead to a closed model, but the best one preserves the intended shape with the least topological damage. Typical logic includes:

  • Free-edge pairs: sew/zip edges when two nearby boundaries should represent one continuous surface.
  • Planar or simple openings: fill a hole or create a replacement patch.
  • Small corner defects: collapse or merge local entities only when the geometric intent is clear.
  • Misclassified patches: regroup or reclassify surfaces so downstream boundary assignment remains meaningful.
  • Face-normal inconsistency: correct orientation before relying on signed reports or region extraction.

The exact menu names vary with STAR-CCM+ release, so the page should be treated as workflow guidance rather than a version-specific click sequence.

04

Recommended repair workflow

  1. Keep an untouched geometry copy.

    Repair work is easier to judge when you can compare against the original import.

  2. Run geometry diagnostics.

    Classify free edges, intersections, topology errors and open surfaces.

  3. Fix the errors that affect domain closure first.

    Leaks and non-manifold conditions matter more than cosmetic details.

  4. Protect important geometric features.

    Do not remove a small gap, edge or hole if it controls the actual flow.

  5. Re-run diagnostics.

    Confirm that the model is improving rather than simply changing.

  6. Test the next operation early.

    Run the intended wrapper, surface remesher or region extraction on a test basis before spending hours perfecting irrelevant details.

Turn geometry features into a mesh plan

Use the Abecator Mesh Advisor after geometry repair to decide where curvature, gaps, wakes and prism layers need explicit resolution.

Mesh Advisor →
05

Common mistakes

  • Repairing every geometric detail even when the surface wrapper will intentionally defeature it.
  • Closing a gap that is physically part of the flow path.
  • Doing extensive non-pipelined repair and then later replacing the original CAD without documenting the changes.
  • Judging success only from appearance instead of diagnostics and region closure.
  • Waiting until volume meshing to discover surface defects that could have been found earlier.
AUTHORITY

Surface repair: quantify whether a tiny leak can matter

This section turns the workflow into a quantitative engineering check and an original visual model that can be reused during setup review.

diagnose / preserve physical feature
The priority of a geometry defect comes from its effect on domain closure, flow paths, interfaces or mesh—not from visual size alone.
ENGINEERING RELATION

ṁ = ρAU

  • ṁ = mass flow through an unintended opening
  • ρ = density
  • A = leak area
  • U = characteristic leak velocity
Worked example:

A 1 mm × 20 mm unintended opening carrying air at 10 m/s gives A = 2×10⁻⁵ m² and ṁ ≈ 2.4×10⁻⁴ kg/s. In a small-flow device, that can be large enough to corrupt a balance even though the gap looks visually tiny.

Decision table

Topology defect changes domain closure

Repair first.

Re-run diagnostics and region extraction.
Cosmetic CAD defect

Do not spend effort unless it affects wrapping/meshing.

Test the next operation early.
Feature may be physical

Do not close it until intent is verified.

Compare with drawings/measurement/model objective.

Primary / official references

Exact model names and menu locations can change by STAR-CCM+ release; use the official documentation for the installed version when reproducing software steps.

AI Assistance
Contact
TGTelegram