Integrate Motion Distortion Correction Before Voxel Grid Downsampling

Aperta
#761 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
25/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
rust
Ambito
robotics

Direzione di ricerca

Start by tracing the existing preprocessing pipeline stages (crop box, voxel grid downsampling, NDT input) and how per-point timestamps and frame metadata flow between them; the payload names no specific files. Add a pipeline dependency so motion distortion correction runs before voxel grid downsampling, with explicit failure handling. Done means the acceptance criteria hold: timing is preserved through earlier filters, the output metadata records the reference time and frame, and tests compare against a correction-then-downsampling reference, including with crop box enabled and disabled.

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

Descrizione

Integrate LiDAR motion distortion correction into the Awkernel preprocessing pipeline before downsampling stages that discard or aggregate per-point timing information. Ensure that NDT receives downsampled points expressed in a consistent scan reference frame.

Scope:

  • Connect motion distortion correction upstream of voxel grid downsampling
  • Preserve per-point timestamps and other required fields through all stages preceding correction
  • Define the scan reference time, coordinate frame, and metadata passed between stages
  • Integrate motion-data availability checks and the correction component’s failure policy
  • Prevent duplicate correction and accidental bypass of correction during normal operation

Acceptance criteria:

  • Pipeline dependencies enforce correction before voxel grid downsampling.
  • Tests verify that preceding filters preserve the original timing information of retained points.
  • Downsampling operates on corrected coordinates, and its output metadata identifies the common reference time and frame.
  • Invalid inputs or failed correction cannot silently proceed as successfully corrected data.
  • Integrated outputs match an explicit correction-then-downsampling reference sequence within predefined tolerances.
  • Tests include moving-sensor scans for which reversing the processing order produces a detectable difference.
  • Regression tests confirm correct behavior when crop box filtering is enabled or disabled.
  • Pipeline configuration, data contracts, and reproduction steps are documented.

Out of scope:

Changes to the distortion-correction or downsampling algorithms, reconstruction of timestamps already lost by earlier processing, and full NDT accuracy or performance benchmarking.

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.