Port LiDAR Motion Distortion Correction to Awkernel

Aberta
#760 0 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 2 dias

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
5/5
Tempo estimado
Mais de uma semana
Facilidade para iniciantes
15/100
Tipo de issue
Funcionalidade
Clareza
Razoavelmente clara
Status de atividade
Ativa
Stack de tecnologia
rust
Domínio
robotics

Direção de pesquisa

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.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

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.

Linguagem predominante
Rust
Estrelas
282
Forks
12
Merge médio
2d 9h
PRs com merge (30d)
28

Preparar o ambiente

Este projeto não oferece contêiner de desenvolvimento, Dockerfile nem guia de contribuição, então a configuração fica por sua conta: comece pelo README e veja nosso guia da primeira contribuição para os passos gerais.

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de tier4/awkernel

Todas as issues de tier4/awkernel

Issues semelhantes

Mais issues de Rust

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.