Backend
High-Order Regularization for Singular and Nearly Singular Laplace and Stokes Layer Potentials in Two Dimensions
arXiv cs.NA0 views
arXiv:2611.21991v1 Announce Type: new Abstract: Layer potentials represent the solutions of many elliptic boundary value problems, but their kernels have the singularity of the fundamental solution, so standard quadrature loses accuracy at targets on or near the boundary. In two dimensions, Gaussian regularization of the logarithmic kernel gives a smooth kernel involving the exponential integral $E_1$, but for the single layer its regularization error is only first order in the smoothing radius $\delta$. We construct modified kernels for two-dimensional Laplace and Stokes single- and double-layer potentials that achieve regularization error $O(\delta^p)$, $p=3,5,7$, uniformly for targets on and near the curve. The resulting method is both high-order accurate and easy to implement: the integrals are evaluated directly by the periodic trapezoidal rule on a single fixed set of boundary nodes for all targets. Choosing $\delta=c h^q$ with $q<1$, where $h$ is the node spacing, keeps the discretization error smaller than the regularization error as $h\to0$, and numerical experiments confirm the predicted $O(h^{pq})$ convergence. Finally, we combine the near-curve evaluation with a fast Poisson solver to compute the potentials on the entire Cartesian grid.
Source:https://arxiv.org/abs/2611.21991PreviousConvergence of discrete exterior calculus for the Hodge-Dirac and Hodge-Laplace problems on surfacesNextA nonlinear multigrid method for the preconditioned lattice Boltzmann equation
Related posts
Driving the Style: Velocity-Conditioned Whole-Body Control from Motion Demonstrations
0arXiv cs.RO
sqrtVINS-Based 360 Visual-Inertial SLAM Systems: Hilti-Trimble SLAM Challenge 2026 Entry
0arXiv cs.RO
Ontology-Compiled Control Barrier Functions for Heterogeneous Robot Teams
0arXiv cs.RO
I Used to Get Attached to My Code. I Don't Anymore.
0dev.to AI
Securing MCP Servers: Preventing Shadow Tool Declarations and JSON-RPC Parameter Poisoning
0dev.to AI
How do I find out why users abandon conversations with my AI agent?
0dev.to AI