Skip to content

Define and Validate Localization Data Interface Conventions #756

Open

Description

@ytakano

Define and implement consistent timestamp, coordinate-frame, and covariance conventions across the NDT, gyro odometry, and EKF interfaces in Awkernel. Ensure that measurements retain their physical meaning when exchanged between components.

Scope:

  • Define measurement, arrival, and publication timestamps, including clock domains and units
  • Specify timestamp ordering, buffering, and permitted interpolation or extrapolation
  • Define map, vehicle, and sensor frames, transform directions, and sensor extrinsics
  • Implement required pose and twist transformations using documented reference points
  • Define covariance layouts, units, and transformation rules consistent with the selected state representation
  • Validate incoming data and document handling of missing transforms, invalid covariance, and unsupported timestamps

Acceptance criteria:

  • Interface documentation specifies frames, timestamps, units, covariance ordering, and validity requirements for each input and output.
  • Measurement timestamps are preserved through processing rather than replaced by arrival or publication times.
  • Transform tests cover identity transforms, known translations and rotations, inverse transformations, and non-identity sensor extrinsics.
  • Twist transformations account for reference-point changes where required, rather than applying rotation alone indiscriminately.
  • Covariance transformations use the appropriate Jacobian for the defined representation and preserve relevant cross-covariance terms.
  • Tests cover delayed and out-of-order measurements, unavailable transforms, and invalid covariance values.
  • Integration tests confirm that NDT pose and gyro odometry twist are interpreted consistently by the EKF.
  • Any deviations from the selected Autoware reference conventions are documented.

Out of scope:

Sensor calibration estimation, hardware clock synchronization, changes to the NDT or EKF algorithms, and full-pipeline performance benchmarking.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions