Reference Evaluation A Informative Reference Document

Hypothetical Physics-Derived Motion Platform

Step-by-step evaluation of a hypothetical six-axis system where all motion is driven directly from the real-time vehicle physics engine

Educational demonstration only. No real products, manufacturers, or organizations are referenced. This hypothetical system was constructed to illustrate what an In-the-Loop classification looks like from the inside.

Classification Result
In-the-Loop
Criterion A: Pass Criterion B: Pass Criterion C: Pass

Educational reference only. This evaluation is a hypothetical demonstration. The system described does not exist and is not based on any real product. The classification shown here does not apply to any real simulation system. For the evaluation methodology this demonstration is based on, see Evaluation Process.

System Description


Reference System A is a hypothetical six-axis motion platform intended to represent the class of systems where all motion output is causatively derived from the real-time vehicle physics simulation. It was constructed to demonstrate what the evidence package and criterion review look like for a system that fully satisfies the In-the-Loop structural requirements.

System Configuration Summary

Platform Type Six-axis electric motion platform
Axes of Motion Surge, sway, heave, roll, pitch, yaw
Motion Source Direct output from real-time vehicle dynamics engine
Axis Control Architecture Independent closed-loop actuator per axis
Reference Point Vehicle center of mass (enforced in software)
Synchronization Motion and visual share single physics clock
Post-Processing None between physics output and actuator command
Documentation Available Architecture, actuator specification, telemetry logs

The defining architectural feature of this system is the absence of any transformation layer between the physics model output and the actuator command signal. When the vehicle physics model calculates a yaw moment, that calculation produces the actuator command directly. There is no washout filter, no motion cueing algorithm, and no approximation applied before the signal reaches the actuators.

Five Required Inputs Reviewed


Every SFR evaluation begins with a review of five required evidence inputs. The table below shows what was reviewed for Reference System A, the evidence tier assigned to each input, and a summary of what that input established.

Evidence tiers: Tier 1 = measured telemetry (highest quality); Tier 2 = verified system documentation; Tier 3 = manufacturer-provided specification; Tier 4 = unverified manufacturer claim (lowest).

Input Description Tier Finding
R1
Motion Telemetry
Time-stamped actuator command logs cross-referenced with physics model force outputs during reference motion events Tier 1 Actuator commands correspond directly to physics outputs within measurement precision. No transformation artifacts detected.
R2
Physics Architecture
System architecture documentation showing signal path from physics engine to motion controller Tier 2 Documentation confirms direct causal chain. Physics engine output feeds motion controller input without intermediate processing stage.
R3
Actuator Specification
Engineering specification for each of the six axes, covering control loop architecture and command interface Tier 2 Each axis operates on an independent closed-loop control system. No shared actuator path, no cross-axis coupling at the control level. Center-of-mass reference coordinate enforced in motion controller configuration.
R4
Synchronization Data
Timing logs for motion command issuance relative to visual frame render and audio output during four reference motion events Tier 1 Motion, visual, and audio outputs confirmed to share a single physics clock. Timing relationships measured within the required synchronization window across all reference events.
R5
Control Telemetry
Logs tracing participant control inputs (steering, throttle, brake) through physics state changes to resulting motion commands Tier 1 Control inputs demonstrably affect physics state. Physics state changes produce corresponding motion commands in the expected direction and magnitude. Causal chain from input to motion output is intact and traceable.

All five required inputs were available. Three inputs were Tier 1 (measured telemetry); two were Tier 2 (verified documentation). No Tier 3 or Tier 4 evidence was relied upon for any criterion. The evidence package is complete and of high quality.

Three Criteria, Assessed in Sequence


Each criterion is assessed independently using the evidence collected. The result for each criterion is Pass, Fail, or Insufficient Data. All three criteria must pass for an In-the-Loop classification.

Criterion A — Physics-Driven Motion
Does the actuator command originate from the physics model output at time of generation, without transformation that would alter its causal relationship to the vehicle state?
Pass

Evidence Reviewed

R1 (motion telemetry) shows that actuator commands correspond directly to physics model force and moment outputs. R2 (architecture documentation) confirms no intermediate processing stage between physics output and motion controller input.

Finding

The motion delivered to the participant originates from the vehicle physics model output at the moment of generation. When the physics model calculates a lateral acceleration event, that calculation produces the corresponding actuator command. No washout filter, motion cueing algorithm, or post-processing layer modifies the signal before it reaches the actuators. The causal relationship between vehicle physics state and participant motion input is direct and unbroken.

Primary evidence: R1 (Tier 1), R2 (Tier 2)

Criterion B — Structural Independence
Do all axes of motion operate independently, and is the center of mass used as the reference point for rotational and translational calculations?
Pass

Evidence Reviewed

R3 (actuator specification) documents independent closed-loop control for each of the six axes. Architecture documentation confirms center-of-mass reference is enforced in the motion controller configuration. No shared actuator path or cross-axis coupling identified at the control level.

Finding

Each of the six axes (surge, sway, heave, roll, pitch, yaw) operates through an independent control loop. A command issued to the yaw axis does not affect the heave or surge axis through any shared mechanical or computational path. Axis independence holds at both the control level and the mechanical level. The reference coordinate used for all rotational and translational calculations is the vehicle center of mass, as specified in the motion controller configuration and confirmed in the architecture documentation.

Primary evidence: R3 (Tier 2)

Criterion C — Human Response Relevance
Are the motion characteristics delivered to the participant consistent with expected physiological detection parameters for the vehicle events depicted?
Pass

Evidence Reviewed

R1 (motion telemetry) provides motion magnitude and timing data during four reference motion events. R4 (synchronization data) confirms timing relationships between motion and visual output. R5 (control telemetry) confirms the motion outputs correspond to the vehicle events being depicted.

Finding

Motion magnitudes and onset timing measured during the four reference motion events (steady-state lateral, transient yaw onset, combined axis, limit-state threshold) are consistent with expected inner-ear stimulus parameters for the depicted vehicle dynamics. Because motion is physics-derived and unmodified (established in Criterion A), the timing and magnitude relationships reflect the actual vehicle physics state. No evidence of systematic magnitude attenuation or timing distortion that would prevent the inner ear from receiving a valid motion signal was identified.

Primary evidence: R1 (Tier 1), R4 (Tier 1), R5 (Tier 1)

Classification Result


Reference System A is classified as
In-the-Loop

All three structural criteria were met. Motion is causatively derived from the vehicle physics model, delivered through independent axes referenced to the vehicle center of mass, with timing and magnitude characteristics consistent with valid physiological stimulation for the depicted vehicle events. The evidence quality is high: three Tier 1 inputs and two Tier 2 inputs. No criterion returned Fail or Insufficient Data.

What This Evaluation Demonstrates


This reference evaluation illustrates several features of the In-the-Loop classification that are worth understanding clearly.

The classification follows from the architecture, not the appearance. Nothing about the size, cost, or visual immersion of the system was assessed. The classification is entirely determined by how motion is generated, how it is delivered, and what evidence documents that chain.
The absence of a transformation layer is the critical factor. The defining architectural feature that produced an In-the-Loop classification is that no washout filter, motion cueing algorithm, or approximation step was applied between the physics model output and the actuator command. That one structural property is what separates this system from Reference System B.
High-quality evidence simplifies the criterion assessment. With three Tier 1 (measured telemetry) inputs available, there was no ambiguity in any criterion. Lower-quality evidence would not have changed the result here, but it would have increased uncertainty and potentially returned Insufficient Data on criteria where direct measurement was not available.
All six axes must be independent. Criterion B requires independence across all six degrees of freedom. A system that has five independent axes but one coupled axis does not pass Criterion B. Independence must be architecturally complete, not partial.
Center-of-mass reference is a specific, verifiable requirement. It is not enough that the system produces rotation — the rotational calculations must be referenced to the vehicle center of mass. This is a documented configuration requirement, not an inferred one. It must appear in verifiable documentation.