Skip to content

Validate Temporal and Spatial Consistency for Motion Distortion Correction #762

Open

Description

@ytakano

Validate that LiDAR point timestamps, coordinate transforms, and available vehicle motion data are consistent throughout motion distortion correction in Awkernel. Verify the interface conventions defined in M2 using scan-level integration tests.

Scope:

  • Verify the relationship between per-point timestamps, scan timestamps, and the correction reference time
  • Check clock-domain mappings, timestamp units, and coverage of the scan acquisition interval
  • Validate sensor extrinsics, transform directions, and the reference points used for motion estimates
  • Verify that motion samples support the required interpolation or prediction within configured limits
  • Test handling of unavailable transforms, incomplete motion history, and stale inputs

Acceptance criteria:

  • Tests detect incorrect timestamp units, offsets, and clock-domain mappings rather than silently producing corrected output.
  • Every corrected point is supported by motion data or an explicitly permitted prediction within the configured limits.
  • Tests cover motion-history gaps, scan-boundary timestamps, delayed arrivals, and out-of-order samples.
  • Known-motion tests with non-identity sensor extrinsics verify transform direction and reference-point handling.
  • Replay uses only motion data available at the correction decision time; any waiting policy and its latency are explicit.
  • Missing transforms or insufficient motion data trigger the documented rejection or flagged fallback policy.
  • Diagnostics identify the affected scan, failure reason, and relevant timestamp or coverage interval.
  • Test fixtures, expected outcomes, and reproduction steps are documented.

Out of scope:

Redefining the M2 interface conventions, implementing the distortion-correction algorithm, hardware clock synchronization, and broad fault-injection campaigns.

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