Skip to research
Vraelis Research
All researchVraelis Imprint / Reference note and proposed protocol

Define the simulation input contract

Turn code, models and device inputs into a bounded, inspectable experiment.

Research note · November 14, 2026

Research question

What must be specified before a proposed operating environment can produce an interpretable result?

Method

  1. Define the system boundary and list the inputs the model consumes: commands, sensor values, environmental parameters and initial state. Give each a type, unit, valid range and timing convention.
  2. Separate fixed parameters from values that change during a run. Record whether an input is measured, replayed, generated or chosen by the experimenter.
  3. Create invalid-input cases for missing values, wrong units and unsupported ranges. Require explicit rejection or a documented conversion instead of silent coercion.

Records to retain

  • Input schema and units
  • Source of each input
  • Initial state and parameter values
  • Rejected and converted inputs

Source basis

FMI defines interfaces and variable semantics for exchanging models, while ROS REP 103 documents unit conventions. Together they illustrate why a connection is insufficient without a shared interpretation of values.

Interpretation & limits

This is an Imprint design protocol, not an implemented universal importer. A valid input contract does not establish physical fidelity or support for every device, SDK or API.

Next experiments

  • Specify one controller-and-plant input contract.
  • Test malformed and out-of-range inputs before adding more connectors.

References

  1. Functional Mock-up Interface 3.0
  2. ROS REP 103 source

Technical reference

Implementation details supporting this note, drawn directly from the maintained documentation. These are technical references, not additional papers or new experimental results. Expand a topic to inspect its method, fields and limits.

Related notes