Repository navigation
openpaso 1.2.0 — first release on PyPI
openPASO 1.2.0 — first release on PyPI
pip install "openpaso[skfem]" # the server plus the easiest solver to start with
openpaso # starts the MCP server on stdioPoint your AI app at the openpaso command (Claude Code: claude mcp add openpaso -- openpaso;
Claude Desktop / Cursor: "command": "openpaso" in the MCP configuration) and it can prepare,
run, couple and verify simulations in the nine supported codes. The pip-installable solvers come
as extras ([skfem], [ngsolve], [kratos], [dune], [all-solvers]); 4C, deal.II, FEniCSx,
FEBio and SPARTA are found on the machine as before. The same install is importable as
openpaso for scripts.
The project now lives at https://github.com/open-PASO/openPASO (moved from Hereon-InstituteMS;
the old URL redirects). Documentation: https://open-paso.github.io/openPASO/
Since 1.1.0
- Every solver survey prints verdict lines: a reference the run never saw, the measured value, a
tolerance, PASS or FAIL — and each verdict kind has been shown to fail on a planted wrong answer. - Coverage is reported against each backend's own declared surface (every FE class, space,
element, registry entry, command) in four states: not attemptable, failed, ran, verified. - Corrections found by those verdicts: the scikit-fem survey's boundary treatment for
Hermite-type elements, its mixed-element quadrature mismatch, the FEniCSx Hermite
interpolation text, DUNE element counts after refinement, an advertised scikit-fem row that
could not be served, and a Kratos interpreter that was auditioned rather than used. - The verification gate no longer marks every 4C VTK run unverified; the 4C FSI deck no longer
writes an unfillable pressure; the equation check judges cell midpoints only and carries the
reaction term; the coupling audit computes it per side; a level that never coupled is not
counted as converged; a verified coupling is judged before its record is shortened. - An installed package writes its state (session journal, discovery cache, build logs,
community submissions) to the user's state directory, never into site-packages.