Control Room¶
Last changes: Documentation changelog
The Control Room (apps/control-room) is the active unified browser workspace for FullMag. It keeps
one semantic workspace model, one viewport layout model, and one typed client architecture across
FDM and FEM problems. Its core authoring invariant is explicit transactions: form edits create an
isolated draft, Apply commits canonical authored policy with scene_revision checks, and a
separate build or study command materializes backend resources.
Shell Routing, Theming, and Multi-Instance Tabs¶
Routes (
tabRoutes.ts):/homeoverlays the non-blocking Start Screen hub while preserving any open session;/session/<slug>opens the workspace for the local backend instance;/session/<slug>?port=<port>and/instance/<port>attach sibling Control Room tabs on the same host (for parallel runs or separate Docker Compose development groups) without interrupting local sessions.Mocha & Latte Themes (
theme.css,ThemeSwitcher): Central--fm-*design tokens drive both Catppuccin Mocha (data-theme="dark") and Catppuccin Latte (data-theme="light") palettes, switchable directly from theAppMenuBar.
Workspace Ownership¶
Area |
Responsibility |
|---|---|
|
Launch tiles (FDM/FEM/Template/Import/Script), checkpoint resume, active sessions, sibling instances |
|
File/Edit/View/Simulation/Tools/Help menus, quick Save/Apply/Undo/Redo, transport controls, |
|
Discretization- and lane-aware tabs ( |
|
Five semantic dock tabs: |
|
Context-routed semantic property panels with draft isolation and validation |
|
Unified 3D WebGL scene, 2D planar probe map, live ECharts traces, dispersion/FMR plots, and saved playback |
|
|
Script export |
|
The implementation lives in apps/control-room/src/modules, with API, resource, selection, and
layout controllers in apps/control-room/src/kernel. Screenshots illustrate the interface; they are
not runtime or physics qualification evidence.
Control Room crosswalk¶
This page is the Control Room surface itself. The status is partial unless every listed field has a named inspector and transaction. Fields not present in the cited component are TODO: frontend support; runtime/result-only views are inspection-only. See Control Room capability register.
Python/API crosswalk¶
Python remains the authoritative authoring contract. Use the linked Python API pages for exact constructors, functions, arguments, units, and failure semantics; this page must not invent a Python signature.
Physics and bibliography scope¶
This UI page introduces no independent physical model. It presents controls for an existing backend contract. Bibliography: not applicable unless a terminal page below introduces a scientific model; implementation references are the cited frontend component and linked API page.
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.