Port LiDAR Motion Distortion Correction to Awkernel

Aperta
#760 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à
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
15/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
rust
Ambito
robotics

Direzione di ricerca

The issue names no files, tests or entry points, so begin by settling the open questions: which Autoware reference implementation and correction mode to match, the unit of the per-point timestamps, and the output timestamp semantics. Work through the scope list in order. Done means the acceptance criteria pass: the stationary case leaves coordinates unchanged, and synthetic trajectory tests cover translation, rotation, extrinsics and rejection of insufficient motion data.

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

Descrizione

Implement LiDAR motion distortion correction in Awkernel using per-point timestamps and vehicle motion estimates. Transform points acquired at different times into a common scan reference frame, matching the behavior of the selected Autoware reference implementation and correction mode.

Scope:

  • Interpret per-point timestamps, including their units and relationship to the scan timestamp
  • Buffer timestamped vehicle twist estimates and IMU angular velocity when required by the selected correction mode
  • Estimate relative motion between each point’s acquisition time and the scan reference time
  • Apply sensor extrinsics and motion compensation consistently with the defined coordinate-frame conventions
  • Preserve required point fields and document output timestamp semantics
  • Define behavior for insufficient motion-history coverage, invalid timestamps, and excessive interpolation or extrapolation gaps

Acceptance criteria:

  • Corrected point coordinates match the reference implementation within predefined tolerances under identical inputs and configuration.
  • Tests cover stationary conditions, constant translation, constant rotation, and combined motion.
  • Synthetic tests with known trajectories verify correction direction, reference time, and sensor extrinsic handling.
  • The stationary case leaves point coordinates unchanged within numerical tolerance.
  • Tests cover non-identity sensor extrinsics, scan-boundary timestamps, and missing or stale motion estimates.
  • Unsupported or insufficient motion data triggers a documented rejection or explicitly flagged fallback rather than silent correction.
  • Execution time and memory usage are measured across representative point counts and motion-input rates.
  • Test datasets, parameters, and reproduction steps are documented.

Out of scope:

Sensor calibration estimation, IMU bias estimation, changes to gyro odometry or EKF algorithms, and full-pipeline accuracy evaluation.

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.