Plugins
xfea finds its plugins through Python entry points, declared in each plugin’s pyproject.toml.
Meshing, results database, viewer and results reader plugins
Section titled “Meshing, results database, viewer and results reader plugins”These are open: anyone can write one, and the contracts are in the core.
| Plugin | Entry point group | Contract |
|---|---|---|
| Meshing | xfea.meshing |
xfea.meshing (Mesher, MeshResult) |
| Results database | xfea.results_databases |
xfea.results.database |
| Viewer | xfea.viewers |
xfea.viewers (Scene, SceneContext, ViewerSettings) |
| Results reader | xfea.results_readers |
xfea.results.readers (ResultsReader, Numbering) |
The plugins that ship with xfea (xfea_gmsh, xfea_sqlite, xfea_view) are working examples of the first
three, and the results reader in xfea’s repository of the fourth.
Solver plugins
Section titled “Solver plugins”A solver plugin turns an xfea model into one solver’s input: the conversion. It is xfea’s own, not an open plugin type: users subscribe to the plugins for their solvers on their account, and they run on xfea’s service; a firm that can’t use the service can have one licensed for its own server, by agreement (see What’s free, what needs an account).
To bring xfea to a solver it doesn’t support yet, such as an in-house code, write to us through the contact form.
© 2026 Francesco Ranaudo · Text and pictures CC BY 4.0 · Code Elastic License 2.0 · how to reuse them