Define and Validate Localization Data Interface Conventions

Aberta
#756 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
18/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, so start by locating the existing NDT, gyro odometry, and EKF interface and test modules in the repository and reading their current timestamp, frame, and covariance handling. Use the acceptance criteria as the checklist: document conventions, preserve measurement timestamps, add transform and covariance tests, and validate delayed/out-of-order data and missing transforms. Done means the documented interfaces and tests cover each acceptance criterion, with deviations from Autoware conventions recorded.

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

Descrição

Define and implement consistent timestamp, coordinate-frame, and covariance conventions across the NDT, gyro odometry, and EKF interfaces in Awkernel. Ensure that measurements retain their physical meaning when exchanged between components.

Scope:

  • Define measurement, arrival, and publication timestamps, including clock domains and units
  • Specify timestamp ordering, buffering, and permitted interpolation or extrapolation
  • Define map, vehicle, and sensor frames, transform directions, and sensor extrinsics
  • Implement required pose and twist transformations using documented reference points
  • Define covariance layouts, units, and transformation rules consistent with the selected state representation
  • Validate incoming data and document handling of missing transforms, invalid covariance, and unsupported timestamps

Acceptance criteria:

  • Interface documentation specifies frames, timestamps, units, covariance ordering, and validity requirements for each input and output.
  • Measurement timestamps are preserved through processing rather than replaced by arrival or publication times.
  • Transform tests cover identity transforms, known translations and rotations, inverse transformations, and non-identity sensor extrinsics.
  • Twist transformations account for reference-point changes where required, rather than applying rotation alone indiscriminately.
  • Covariance transformations use the appropriate Jacobian for the defined representation and preserve relevant cross-covariance terms.
  • Tests cover delayed and out-of-order measurements, unavailable transforms, and invalid covariance values.
  • Integration tests confirm that NDT pose and gyro odometry twist are interpreted consistently by the EKF.
  • Any deviations from the selected Autoware reference conventions are documented.

Out of scope:

Sensor calibration estimation, hardware clock synchronization, changes to the NDT or EKF algorithms, and full-pipeline performance benchmarking.

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.