Section 19Platform and Delivery

Editor and Viewer requirements

Defines authoring, inspection, visualization, plotting, diagnostics, requirements navigation, and recorded-state playback.

Section relationships
IDNamePriorityRequirementVerification
UI-001Optional UIMVPThe Editor and Viewer SHALL be optional for headless execution and SHALL not own authoritative simulation state.Test
UI-002Project browserMVPThe UI SHALL display projects, robots, worlds, experiments, runs, and referenced assets in a navigable hierarchy.Demonstration
UI-003Three-dimensional viewportMVPThe UI SHALL display visual geometry, transforms, cameras, and robot motion for the reference projects.Demonstration
UI-004Entity selectionMVPA user SHALL be able to select a visible or hierarchical entity and inspect its canonical identity and properties.Demonstration
UI-005Unit-aware property displayMVPEvery displayed physical numeric property SHALL show its unit and preserve canonical meaning during display-unit conversion.Test
UI-006Simulation controlsMVPThe UI SHALL provide run, pause, single-step, reset, stop, and playback controls with current virtual time and execution mode.Demonstration
UI-007Time and performance displayMVPThe UI SHALL display virtual time, wall time, real-time factor, frame rate, and selected subsystem timings.Demonstration
UI-008Debug geometryBetaThe UI SHALL visualize selected collision shapes, contact points and normals, joint frames, centers of mass, inertia orientation, sensor frames, and force vectors.Demonstration
UI-009Diagnostic panelMVPCompile and runtime diagnostics SHALL be filterable by severity and SHALL navigate to the responsible object where possible.Demonstration
UI-010Telemetry plotBetaThe UI SHALL plot selected scalar time-series channels with units and aligned virtual time.Demonstration
UI-011Run comparison viewBetaThe UI SHALL compare selected metrics and time-series data from at least two runs.Demonstration
UI-012Fidelity card viewBetaThe UI SHALL display the pre-run fidelity preview and completed-run fidelity card.Demonstration
UI-013Conversion report viewBetaThe UI SHALL display import and export losses grouped by source asset and severity.Demonstration
UI-014Environment visualizationBetaThe UI SHALL visualize selected wind, precipitation, visibility, wetness, temperature, and terrain-material fields without affecting simulation state.Demonstration
UI-015Interactive transform editingBetaA user SHALL be able to edit permitted transforms with snapping, numeric input, frames, units, and validation.Demonstration
UI-016Experiment editorBetaA user SHALL be able to edit parameter sweeps, distributions, seeds, stop conditions, metrics, and execution settings graphically.Demonstration
UI-017Device connection viewBetaThe UI SHALL visualize and validate power, signal, controller, and physical device-port connections.Demonstration
UI-018Undo and redoBetaAuthoring changes SHALL support bounded undo and redo without changing completed run artifacts.Test
UI-019Read-only live inspectionBetaA user SHALL be able to inspect selected committed state while running without mutating the simulation.Test
UI-020Playback separationMVPRecorded-State Playback SHALL not require, invoke, or advance any simulation solver or backend.Test
UI-021User-selectable unit conversionMVPA user SHALL be able to convert a displayed physical quantity among documented dimensionally compatible SI and non-SI engineering units without changing its canonical SI meaning.Demonstration
UI-022Robot bring-up workbenchBetaThe UI SHALL combine the canonical hierarchy, readiness report, conversion diagnostics, frames, inertial properties, joint limits and drives, collision geometry, device connections, and sensor fields of view into a navigable robot bring-up view.Demonstration
UI-023Synthetic-data authoring and previewBetaThe UI SHALL let a user configure labels and capture products and preview aligned sensor output and ground-truth annotations without changing authoritative simulation state.Demonstration
UI-024Motion-planning inspectionBetaThe UI SHALL display a planning request's start and goal states, constraints, collision environment, returned candidate trajectories, feasibility status, and diagnostics before the user selects a trajectory for execution.Demonstration
UI-025Frame-history inspectorBetaA user SHALL be able to query and display the transform chain, source identities, authority, and update times between two supported frames at a selected virtual time.Demonstration

Change rationale (UI-020): The previous wording protected only the original mechanics backend. The canonical definition of Recorded-State Playback excludes rerunning any solver, so UI-020 now applies that separation consistently to every simulation solver and backend.

Change rationale (UI-021): MODEL-002 establishes canonical SI storage and UI-005 preserves canonical meaning during display conversion, but neither explicitly guarantees that a user can select and perform a compatible unit conversion. UI-021 makes that interaction mandatory.

Change rationale (UI-022UI-025): These views turn the new Beta contracts into inspectable engineering workflows. They reuse authoritative compiler, sensor, planner, and frame data rather than creating UI-owned simulation semantics.

Generated from the canonical specification. Edit section metadata or prose in docs/requirements.md; the website rebuilds this page and its relationships automatically.