Integrate EKF-Based Initial Pose Estimation for NDT

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

Mantenedores costumam responder em até 2 dias

@nokosaaan já está trabalhando nisso.

Desde 13/11/2026.

  • #796 de @nokosaaan — aberto

Avaliação

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

Direção de pesquisa

The payload names no files, tests or entry points, so start by finding the existing NDT scan-matching and EKF pose code in the repository and reading how poses and timestamps flow between them. This is design work: the interpolation limits, fallback policy and reset behavior are undecided, so agree on them with maintainers before coding. Done means the listed acceptance criteria hold, with tests for rate mismatch, delayed outputs, missing history, excess horizons and resets.

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

Descrição

Use previously available EKF pose estimates or predictions to initialize subsequent NDT scans in Awkernel. Establish a timestamp-aware feedback path without introducing circular waits between NDT and EKF processing.

Scope:

  • Maintain a bounded history of EKF pose estimates with timestamps and validity information
  • Select or derive an initial pose at the reference timestamp of each NDT scan
  • Define permitted interpolation and prediction methods, including maximum time gaps and prediction horizons
  • Apply the coordinate transforms required by the NDT initial-pose interface
  • Define startup, stale-estimate, missing-history, and estimator-reset behavior
  • Record which EKF estimates were used to initialize each scan

Acceptance criteria:

  • Each NDT scan receives an initial pose corresponding to its reference timestamp within the defined temporal limits.
  • Only EKF outputs available when the initial pose is selected are used; offline replay does not access outputs unavailable at the corresponding replay time.
  • NDT does not wait for an EKF update that depends on the result of that same scan.
  • Tests cover different NDT/EKF rates, delayed EKF outputs, missing history, excessive prediction horizons, and resets.
  • Startup uses an explicitly supplied initial pose until valid EKF estimates become available.
  • Invalid or stale estimates trigger the documented fallback or scan-rejection policy rather than being used silently.
  • Selected source timestamps, interpolation or prediction intervals, and fallback decisions are logged for reproducibility.
  • Integrated replay tests verify NDT convergence and localization error against predefined criteria.

Out of scope:

Changes to the NDT optimization algorithm or EKF state model, GNSS-based automatic initialization, and global relocalization.

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.