Robotics evidence guide · automated editorial preparation, not expert review

Separate perception evidence from task completion

A completed movement does not prove the robot perceived the scene correctly. Record what the perception system estimated, what reference established the object state and how that reference was obtained.

Evidence and interpretation

For Maha’s proposed intake, separate the sensor observation, the estimated object pose, the downstream action and the outcome judgement. This lets a reviewer ask whether a successful grasp depended on accurate localization, a forgiving fixture or intervention. Calibration and reference error belong in the evidence, not in a footnote asserting perfect ground truth. A missing stream should produce an explicit observation gap. It should not be replaced by an inference from the final image.

Proposed evidence workflow

  1. Identify sensor configuration, frame, timestamp and calibration revision.
  2. Distinguish measured reference values from labels inferred by the same model being tested.
  3. Retain missed detections and unusable observations with their attempt IDs.

Worked illustration

A supplied target coordinate lets our toy controller navigate without detecting an object. That is privileged simulator state. The example therefore cannot be scored as a perception benchmark, even when its transfer succeeds.

Limits

NIST identifies perception as an evaluation component. These intake checks are Maha’s proposed method; they do not prove sensor accuracy or remove the need for independent measurement.

Sources and review

NIST: Performance Assessment Framework for Robotic Systems

Locator: Summary; Description: Framework, Capability Models and Test Methods

The completed project decomposes assembly performance into perception, mobility, dexterity and safety-related components.

Boundary: A research-program description, not evidence of Maha performance or an operational safety approval.

Inspection and reuse basis

Selected sections inspected 2026-09-14. Link and original paraphrase only; no third-party images or publication copied. This is not independent expert review of this article.

ROS REP 103: Units and coordinate conventions

Locator: Units; Coordinate Frame Conventions; Axis Orientation; Suffix Frames

ROS specifies SI units and right-handed coordinate conventions, with explicitly different optical-frame axes.

Boundary: A software convention; choosing it does not calibrate a sensor or establish positioning accuracy.

Inspection and reuse basis

Selected sections inspected 2026-09-14. Original explanation and link; no source redistribution. This is not independent expert review of this article.

Continue reading