Mesh Quality Metrics and What They Do Not Tell You — Troubleshooting Guide
By Sitemap
My Mesh Quality Metrics simulation is giving me unexpected results — convergence issues, maybe. How do I diagnose this systematically?
Mesh Quality Metrics troubleshooting follows patterns once you know what to look for. Most issues fall into three buckets: convergence failures, accuracy problems, and result misinterpretation. Let me give you a systematic diagnostic framework rather than a list of random fixes.
That framing helps. Before we dive in — what's the single most common mistake engineers make with Mesh Quality Metrics?
Honestly, it's skipping the sanity checks. Engineers set up a Mesh Quality Metrics model, it converges, and they trust the result without verifying it against a hand calculation or a known benchmark. The solver gives you an answer regardless of whether your model is physically correct. Always run a simplified version first.
Here are the main quality metrics, paired with what really goes wrong when each one is bad.
| Metric | What it measures | What a bad value causes | Practical guide |
|---|---|---|---|
| Aspect ratio | How elongated an element is | Poor gradient resolution along the long direction; ill-conditioned matrices | General regions < 5-10 (boundary layers are the exception, see below) |
| Skewness (distortion) | Angular distortion away from the ideal shape | Larger errors in gradient reconstruction and flux evaluation | < 0.85 (FV codes); angles within 20°-160° (FE codes) |
| Jacobian (ratio) | Collapse or inversion of the mapping | Negative values make the computation impossible; small values degrade integration accuracy | > 0.3, never negative |
| Orthogonality | Misalignment between the face normal and the cell-centre line | More work for non-orthogonal correction; worse convergence (FV) | Minimum > 0.1-0.2 |
| Growth rate and size jump | Volume ratio between neighbouring elements | Wave reflection, local error, time-step restrictions | Neighbour ratio < 1.2-1.5 |
| Warpage (non-planarity) | Twist of a quadrilateral face | Formulation error in shells and hexahedra | < 10-15° |
The essential point is where these sit: they are necessary conditions confirming that the discretization is not broken, not a measure of whether the solution is right. Miss that distinction and you walk straight into the maze of Symptoms 1 and 2 below.
My mesh check is green on every item. The solution still disagrees with the experiment and convergence is slow. What are quality metrics even for?
Quality metrics are the blood-pressure reading at a medical check-up — abnormal means there is definitely a problem, but normal is no guarantee of health. There are three things the metrics never look at. ① Resolution — a nicely shaped element still cannot capture a gradient if it is coarse (that is the job of a mesh convergence study). ② Placement — are elements actually allocated to the boundary layer, the separation, the stress concentration (the job of solution adaptation)? ③ Direction — is the long axis of an anisotropic element aligned with the isosurfaces of the solution? Once you clear the quality gate, the next step is convergence verification — the metrics are the entry ticket, not the diploma.
Driving the worst value to zero on a mesh of several million elements is a cost-benefit decision.
This is normal, because the definition of each metric differs from tool to tool. Skewness alone circulates in several definitions — normalized equiangular skew, normalized volume ratio, angle-based — and it is not unusual for the same element to score 0.6 in one and 0.9 in another. The Jacobian likewise changes depending on whether it is the min/max ratio of the corner values or an evaluation at the Gauss points. Two rules apply in practice: ① state a quality criterion together with "in which tool, under which definition" (write the defining formula into your in-house standard), and ② align the mesher's pass criteria with the solver's own check criteria (so you never get the twist of "mesher passes, solver warns"). Give up on absolute comparison of the numbers and manage relative values within a single definition, and the confusion disappears.
This is the classic warning you are meant to leave alone. The solution in a wall boundary layer varies steeply along the wall normal and gently along the flow, so flat elements with aspect ratios in the hundreds or thousands are in fact optimal (meeting a y+ requirement with isotropic elements gives an unrealistic element count). The correct way to handle it in quality management is to ① separate the boundary layer zone from the quality statistics and manage it not by aspect ratio but by continuity in the normal direction (collapsed or punched-through layers) and growth rate, and ② count its warnings separately from the aspect ratio warnings in the general regions. There are exceptions, though: flat elements near a separation point or crossing a shock become an error source through directional mismatch — judge those case by case on the principle that "anisotropy is only justified when it is aligned with the anisotropy of the solution".
When no amount of tuning in the mesher settings fixes it, the root cause is almost always in the geometry data.
Here is the recommended structure for systematizing quality management. ① Automatic gate (mandatory): zero negative Jacobians, a worst-case skewness threshold, layer continuity in the boundary layer — any mesh that breaks these is rejected unconditionally. ② Statistical report: output histograms of the metrics and the location (coordinates) of the worst values, so that a review can see where the bad elements are. ③ Contextual judgement: strict quality in the evaluated region, looser far away — zone-specific criteria rather than one uniform bar. ④ Connection to the convergence study: passing the gate is the starting line, and quality assurance is completed by confirming mesh convergence of the quantity of interest (GCI). With those four stages you avoid both "the criteria are so strict that no work gets done" and "they are so loose that we have an accident".
So, in one sentence, what is the right way to live with quality metrics?
"Automate the rejection at the door with metrics, and do the quality assurance after admission with a convergence study" — that division of labour. Metrics are the best filter there is for throwing out a broken mesh instantly, but they guarantee nothing about a good solution. A convergence study, conversely, is the strongest guarantee available, and a complete waste of time on a broken mesh. Combining the two in the right order is the whole picture of mesh quality management. And if you have time to fight bad elements that refuse to disappear, spend that time on geometry clean-up instead — that is usually where the root is.
Related: GCI troubleshooting, h-refinement, checking and diagnosing solver convergence.