Runtime and provenance¶
Last changes: Documentation changelog
FullMag presents one launcher and one control room even when implementation uses managed runtime packs. Lightweight CPU paths may be bundled; CUDA FDM and MFEM, hypre and libCEED FEM paths may require managed runtimes.
Two-Plane Transport and Live Python Integration¶
Runtime interaction splits cleanly into two planes served over OpenAPI v2 and companion HTTP/WS channels:
JSON Control Plane & WebSocket Invalidation: Session lifecycle, authoring mutations fenced by
scene_revision, readiness checks, solver command queues, and capability/provenance metadata travel as lightweight revisioned JSON resources (ControlRoomApi).RealtimeClientandRealtimeInvalidationBridgeemit compact invalidation notifications on state changes without pushing dense field arrays over WebSockets.Binary Data Plane: Spatial vector/scalar fields (
FMVP), FEM topology connectivity and markers (FMMT), FDM active/region masks (FMRM,FMBM), 2D cross-section payloads (FMCS,FMQS), mesh quality distributions (FMMQ), periodic facet maps (FMPP), and sampled chart tables (FMTB) stream over HTTP range/binary endpoints with typedArrayBuffervalidation.Live Python Client Presence (
fullmag.live): Interactive scripts usingfm.connect()share the same session API viaLiveSession(packages/fullmag-py/src/fullmag/live/_session.py). Each live script registers a uniquepython-<hex>client_idand transmits10 spresence heartbeats to/v2/sessions/current/clients/{client_id}(30 sAPI expiry TTL), keeping browser tabs and Python scripts synchronized on the active session.
Every published result must make these values inspectable:
requested backend and runtime,
resolved backend and runtime,
capability and qualification status,
precision and mesh or grid identity,
device identity when GPU execution is claimed,
artifact revision and reproducibility metadata.
Compilation on a host is not proof of executed GPU work. Public pages use the strongest evidence available and label lower-tier evidence explicitly.
Control Room crosswalk¶
This architecture page exposes session/runtime provenance via RuntimeResourceInspectorPanel (Model Explorer -> Runtime), StudyInspectorPanel, StatusBarModule, and the Footer Dock (Telemetry, Engine, Operations, Problems) as inspection-only surfaces; runtime targets follow explicit requested intent (auto vs. pinned cpu/gpu, with no silent CPU fallback when GPU is forced). See Control Room capability register.
Python/API crosswalk¶
This page documents architecture rather than a standalone Python callable. Exact constructors, arguments, validation, and examples belong to the linked Python API pages; do not infer a public function from an internal architecture term.
Physics and bibliography scope¶
No independent physical model is introduced here. Scientific equations are owned by the applicable physics or numerical-methods page. Bibliography: not applicable to this architecture overview; implementation ownership is recorded in the source-code references on the terminal page.
Source-code index¶
Repository path |
Stable symbol |
Responsibility |
|---|---|---|
|
|
launcher entry point and script-mode dispatch |
|
|
stage capture lowering and launcher metadata |
|
|
resolved plan and provenance representation |