Overview
Geometry cleanup is one of the most time-consuming stages of any simulation workflow. CAD models built for manufacturing are dense with features that are irrelevant to simulation — small fillets, logo embossments, thin slivers, fastener detail — and imported geometry from suppliers often arrives with translation artefacts: gaps, duplicate faces, non-manifold edges, and missing surfaces. Nexus can carry out geometry cleanup directly inside your simulation pre-processor, working through an inspection-and-repair loop that mirrors what an experienced analyst would do manually — but faster and without the repetitive overhead. Nexus is particularly effective in Ansys Discovery and Ansys SpaceClaim, both of which expose a rich set of programmatic geometry operations that the agent can drive precisely and repeatably.What Nexus is good at
Rules-based defeaturing
Many cleanup tasks follow a clear rule: “remove all fillets below 2mm”, “suppress all holes smaller than M4”, “delete cosmetic features on exterior faces”. Nexus excels at this class of task because the rule can be stated once and applied systematically across the entire model — including assemblies with dozens of bodies — without the analyst touching each feature individually. This is the highest-value use of Nexus in cleanup: tasks that are conceptually simple but manually expensive due to repetition.Geometry healing
Imported STEP, IGES, and Parasolid files frequently carry translation defects. Nexus can run a structured inspection, categorise the issues it finds, and apply targeted fixes:- Gap closure — stitch open edges where faces don’t meet within tolerance
- Missing face repair — reconstruct faces that failed to translate
- Duplicate geometry removal — collapse coincident faces or bodies that cause solver errors
- Normal consistency — flip reversed face normals on surface models
Small face and sliver removal
Short edges, needle-shaped triangular faces, and sliver surfaces cause poor mesh quality and often force the mesher to generate extremely small elements at localised regions — degrading solve time and solution accuracy. Nexus can identify these features by size threshold and remove or merge them automatically.Idealisations
For thin-walled structures, Nexus can extract mid-surfaces and replace the solid geometry with shell representations suitable for structural or thermal analysis. It can also create beam idealisations from cylindrical features such as pipes or struts.Repair validation
After cleanup, Nexus will confirm that the geometry is watertight, manifold, and free of the issues it targeted — giving you a structured report to review before handing off to the mesher.Supported environments
Geometry cleanup with Nexus runs natively inside:| Platform | Notes |
|---|---|
| Ansys Discovery | Full geometry kernel access; rules-based cleanup, healing, mid-surface extraction |
| Ansys SpaceClaim | Same geometry kernel as Discovery; also used as the geometry stage in Ansys Mechanical workflows |
| Ansys Mechanical (SpaceClaim geometry stage) | Cleanup applied to the geometry component before meshing |
Example prompts
Defeaturing by rule
Defeaturing by rule
Translation healing
Translation healing
Small face cleanup
Small face cleanup
Mid-surface extraction
Mid-surface extraction
Pre-mesh inspection report
Pre-mesh inspection report
Assembly-level cleanup
Assembly-level cleanup
Cleanup before meshing: a typical workflow
A structured cleanup sequence that works well as a Nexus prompt chain:Import and inspect
Start with a full geometry report before making any changes. This gives you a baseline and prevents unnecessary operations.
Heal translation defects
Fix structural issues first — these are blockers that can prevent defeaturing tools from working correctly.
Tips for geometry cleanup prompts
- Set size thresholds explicitly — “remove fillets below 1mm” is actionable; “remove small fillets” is ambiguous. Give Nexus a number to work to.
- Protect important faces — Tell Nexus which faces must not change: load application surfaces, mounting interfaces, datum references. This avoids unintended simplification at critical regions.
- Separate inspection from repair — Ask for a report first, review it, then instruct cleanup. This gives you control over what gets changed and prevents unwanted modifications.
- State the target mesh size — Cleanup thresholds are relative to mesh size. Telling Nexus “my target mesh size is 2mm” lets it calibrate what counts as a problematic small feature.
- Use rules for assemblies — Rules-based prompts scale much better than feature-by-feature instructions on assemblies with many bodies. “Remove all features below X” across the whole assembly is more reliable than targeting each body individually.
- Validate before handing off — Always ask Nexus to run a final health check before passing geometry to the mesher. A watertight, manifold solid is the minimum bar.