Papers › A solver for subsonic flow around airfoils based on physics-informed neural networks...

A solver for subsonic flow around airfoils based on physics-informed neural networks and mesh transformation

15 Jan 2024arXiv:2401.08705links table onlyarchive 2025-07-28

Wenbo Cao, Jiahao Song, Weiwei Zhang

The archive published only this paper's code-link row. Authors, date and abstract are from arXiv's metadata (CC0), read from the Kaggle arXiv metadata snapshot of 2026-09-12 where its title matched the archive's; the title is the archive's.

Physics-informed neural networks (PINNs) have recently become a new popular method for solving forward and inverse problems governed by partial differential equations (PDEs). However, in the flow around airfoils, the fluid is greatly accelerated near the leading edge, resulting in a local sharper transition, which is difficult to capture by PINNs. Therefore, PINNs are still rarely used to solve the flow around airfoils. In this study, we combine physical-informed neural networks with mesh transformation, using neural network to learn the flow in the uniform computational space instead of physical space. Mesh transformation avoids the network from capturing the local sharper transition and learning flow with internal boundary (wall boundary). We successfully solve inviscid flow and provide an open-source subsonic flow solver for arbitrary airfoils. Our results show that the solver exhibits higher-order attributes, achieving nearly an order of magnitude error reduction over second-order finite volume methods (FVM) on very sparse meshes. Limited by the learning ability and optimization difficulties of neural network, the accuracy of this solver will not improve significantly with mesh refinement. Nevertheless, it achieves comparable accuracy and efficiency to second-order FVM on fine meshes. Finally, we highlight the significant advantage of the solver in solving parametric problems, as it can efficiently obtain solutions in the continuous parameter space about the angle of attack.

Code

Repository list and official/mentioned flags are the archive's, frozen 2025-07-28. Reachability, where shown, is from one Syntology probe window (2026-09-16 to 2026-09-18); repositories not probed show nothing. GitHub stars are not tracked.

Code Syntology ran Syntology

6 samples harvested; 4 ran; 0 honoured the contract we drafted; 2 have no recorded run. Read from Syntology's graph 2026-09-24; that is when this build read the record, not when the samples ran.

Licence: 6 of the 6 samples are pointer only, meaning Syntology does not serve that copy's text. This page shows no code text for any sample; each one links to its file in the repository.

Harvested from cao-wenbo/nnfoil. “Ran” means the sample executed on a synthesized input. It does not mean the output is correct, and nothing here reproduces the paper's results. “Honoured” and “violated” refer to a contract Syntology drafted from the code itself; “our draft was wrong” and “fixture could not drive it” are failures of Syntology's instrument, not of the code.

Each sample ends with its code_sha256, Syntology's identity for that exact code. An agent fetches the stored sample with Syntology's MCP tool get_code(code_sha256="…") (how to connect); click an identity to copy that call.

Repository labels, per sample. official repository: The archive marks this repository official for the paper. named in the paper: The archive records that the paper mentions this repository; it is not marked official. community (archive-listed): In the archive's code links for this paper, not marked official and not recorded as mentioned in the paper. found in paper text by Syntology: Syntology found this repository in the paper's own text; whether it is the authors' implementation is not asserted. community: Not in the archive's code links for this paper; a community repository Syntology harvested. Samples from a repository marked official are listed first. Licence labels name the repository's licence as recorded at harvest. “Pointer only” means Syntology does not serve that copy's text, for one of four reasons: no licence file was found; the licence was not identified; the licence is recorded as permissive but that copy's record is not marked cleared; or the licence is outside the permissive list Syntology serves text under (MIT, Apache-2.0, BSD and similar). Some licences outside that list permit redistribution, such as WTFPL, and GPL-3.0 under its conditions; they are simply not on the list. Hover a licence label for the reason. File links open the file on GitHub at the default branch, which may have changed since the harvest.

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

Report a problem or propose a change · a person checks every report against the paper or source before anything changes; decisions are listed on /corrections