AI & ML
A characteristic mapping method for dissipative evolution equations
arXiv cs.NA0 views
arXiv:2611.08261v1 Announce Type: new Abstract: The Characteristic Mapping (CM) method is a transport scheme which discretizes the Lagrangian flow map as a composition of spatial interpolants. This adaptive approximation technique has demonstrated novel resolution properties and the ability to efficiently simulate the fine scales of inviscid turbulent flows. In this work, we construct an extension of this approach to the solution of dissipative problems, including the Navier-Stokes equations. The extension lifts a general scalar evolution equation to a path in a group of diffeomorphisms, where the semigroup approach of the CM method can be exploited. We give an interpretation of this lift through the geometric framework of optimal transport. We then introduce a semidirect product evolution technique to perform the time stepping of the map components. The map is evolved based on the semi-Lagrangian CM approach, and its log-Jacobian is evolved explicitly by an exponential integrator. The numerical scheme is demonstrated to be high-order accurate and is tested on a range of canonical nonlinear dissipative equations. By retaining the resolution properties of the CM method, the approach shows a promising ability to simulate turbulent fluid flows across all Reynolds numbers.
Source:https://arxiv.org/abs/2611.08261PreviousUniversal Dimension Formula for Planar $C^r$ Splines at Degree $3r+1$NextVariably saturated flow on polygonal and cut meshes using a mass-conservative hybrid virtual element
Related posts
Global stocks tumble as AI panic grips markets after Democrats' midterm success
0Hacker News
Turning GPT GIFs into a cat film: what smoothing fixed, and what it didn’t
0dev.to AI
I Stopped Writing a New API Client for Every AI Model
0dev.to AI
The smallest feature we shipped started a war (the friendly kind)
0dev.to AI
Authorized is not proven: what the FDA's AI device list does and doesn't tell you
0dev.to AI

Moved Your Repo Folder? Every Agent Worktree Broke. git worktree repair Fixes It
0dev.to AI