FEM Airbox Mesh Panel¶
Last changes: Documentation changelog
The airbox panel edits the universe-owned exterior geometry and air-mesh policy. Its typed draft is
defined in airboxMeshPolicyDraft.ts; the UI is implemented by
AirboxMeshParametersPanel.tsx.
Canonical controls¶
UI field |
Backend key |
Unit |
|---|---|---|
Domain mode |
|
1 |
Padding X/Y/Z |
|
m |
Size X/Y/Z |
|
m |
Center X/Y/Z |
|
m |
Maximum / minimum element size |
|
m |
Maximum element growth rate |
|
1 |
Element grading |
|
|
Curvature factor |
|
1 |
Narrow-region resolution |
|
1 |
Advanced JSON |
complete universe policy |
mixed |
Curvature factor and narrow-region resolution refine only the air (next to curved magnet
surfaces and across narrow air gaps) and require the maximum element size. They are
exported to Python as study.universe.mesh(curvature_factor=..., narrow_region_resolution=...).
Exact-layer, swept and mixed air routes reject them.
For FDM, FEM-only air-mesh keys are filtered; the panel exposes only structured-domain geometry.
For FEM, Apply Airbox Policy stores authored intent and makes the realized shared-domain mesh
stale. Apply & Build Shared-Domain Mesh then executes mesh.build-shared-domain.
The read-only effective section comes from backend effective_config; it must not be inferred from
the current text fields.
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¶
Repository path |
Stable symbol |
Responsibility |
|---|---|---|
|
|
Controls and explicit Apply/build transaction |
|
|
Typed/JSON policy merge and FDM filtering |