Validate Temporal and Spatial Consistency for Motion Distortion Correction

Aperta
#762 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 2 giorni

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
30/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
rust

Direzione di ricerca

The issue names no source files, so start by locating the M2 interface conventions it refers to and the existing motion distortion correction code in the awkernel repository. Write scan-level integration tests covering timestamp units, clock-domain mapping, transform direction with non-identity extrinsics, motion-history gaps and out-of-order samples. Done means each failure case produces a diagnostic naming the scan, reason and interval rather than silent output.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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.

Lingua principale
Rust
Stelle
282
Fork
12
Merge medio
2g 9h
PR unite (30g)
28

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di tier4/awkernel

Tutte le issue di tier4/awkernel

Issue simili

Altre issue su Rust

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.