Physics reference¶
Last changes: Documentation changelog
Each public physics page follows the same chain:
physical problem → continuous equations → FDM and FEM interpretations → implementation → test → reproducible example.
Explore the physics library¶
The library is grouped by purpose so you can open only the branch you need. The complete Sphinx navigation remains available in the site sidebar and inside each section page.
Publication rule¶
A public physics page must state equations, symbols, SI units, assumptions, backend interpretations, API and ProblemIR impact, validation strategy, known limits and deferred work. Source code or a synthetic oracle alone is not enough to call a backend qualified.
Each physical interaction has one canonical scientific owner. FDM, FEM, CPU, and GPU realizations are separated inside that interaction documentation whenever their implementation, support, or qualification differs.
Control Room crosswalk¶
This is a navigation page; the selected interaction or foundation is configured by its linked Python API and object/stage editor. The category itself has no standalone control. frontend support is not implemented applies to physical parameters without a matching control. See {doc}/frontend/capability-register; do not infer UI support from backend or Python availability.
Python/API crosswalk¶
The linked Python API page is authoritative for exact functions, arguments, units, and failure semantics. If this page is a foundation or category overview, runnable Python is ot applicable here and must be taken from the terminal API page.
Bibliography and source scope¶
Use the scientific bibliography and source-code index on the linked terminal page. This block adds no new equation or unverified implementation claim.
Source-code index¶
This is a navigation page and introduces no standalone implementation symbol. The exact source-code index is maintained by the selected terminal page.