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

Coordinate frames at system boundaries

Record axis conventions and transforms when connecting models and sensor inputs.

Research note · November 14, 2026

Research question

How can correct numeric values become incorrect after crossing a coordinate-frame boundary?

Method

  1. Define a world frame, body frame and sensor frame for a small fixture. Record handedness, axis directions and the transform convention used between them.
  2. Apply known translations and rotations to basis vectors. Verify the transformed directions before using the same transform on a large mesh or a recorded trajectory.
  3. Test a camera optical frame separately from a body frame. Preserve source frame identifiers so a consumer cannot silently reinterpret a value as world coordinates.

Records to retain

  • Frame names and handedness
  • Transform direction and composition order
  • Basis-vector test results
  • Sensor and body-frame conventions

Source basis

ROS REP 103 distinguishes body axes from optical-frame conventions, and REP 105 defines relationships among common mobile-robot frames. The numeric components of a vector are incomplete without their frame.

Interpretation & limits

A valid rigid transform does not correct sensor calibration errors or deformable geometry. This proposed protocol does not claim an Imprint robotics integration.

Next experiments

  • Create a frame-swap fixture with an obvious expected direction.
  • Test transform composition and inverse operations on the same fixture.

References

  1. ROS REP 103 source
  2. ROS REP 105 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