AI & ML
A posteriori error estimation for coarse or distorted meshes
arXiv cs.NA0 views
arXiv:2610.12088v1 Announce Type: new Abstract: Finite element simulations carried out on meshes issued from real-world geometries - patient-specific anatomies, scanned industrial parts, fractured media - almost never satisfy the shape-regularity assumptions under which classical a posteriori error analysis is written. Practitioners are therefore left without a quantitative answer to a very legitimate question: how wrong is my simulation when my mesh is coarse and contains badly shaped elements? In this work, we study to which extent equilibrated flux estimators can provide such an answer. Indeed, they deliver a guaranteed and fully computable upper bound of the energy-norm discretization error, with a constant equal to one; and, crucially for the present study, its derivation uses no shape-regularity, quasi-uniformity or angle condition. The only geometric ingredient is the Poincar\'e constant on a single cell, which Payne and Weinberger showed to be at most hK /pi on any convex cell K, however distorted (hK being the cell size). Mesh quality affects the local efficiency - the sharpness of the estimator - but never its reliability, so that the failure mode under distortion is pessimism rather than false confidence.
Source:https://arxiv.org/abs/2610.12088PreviousModel Order Reduction for Parametric Dissipative Quantum SystemsNextVariational Derivation of the Weak Form for Viscous Flows Involving Free Surfaces with Implications for Geodynamic Simulations
Related posts
How to Turn a Process Document Into a Working App With AI
0dev.to Machine Learning
Which AI subscription should I buy?
0dev.to Machine Learning
Your Classifier Says 0.97. Six Ways That Number Lies in .NET 10
0dev.to Machine Learning
Which AI song generator fits a lyrics-first workflow?
0dev.to Tutorial
Anima 2.9B in ComfyUI: Six Workflows, From Official T2I to Tiled Redraw and Smart Img2Img
0dev.to Tutorial
How to calculate how many cartons fit on a pallet (with a worked example)
0dev.to Tutorial