Establish Differential Testing Against an Autoware Reference

Aberta
#752 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
cpp, rust

Direção de pesquisa

The issue names no existing files, tests or entry points, so locate the Awkernel preprocessing (crop box, voxel grid) and NDT code first, and read the pinned Autoware reference's equivalent filters for parameter meaning. This is design-heavy: agree on the tolerance and comparison rules with maintainers before coding. Done means both pipelines run on shared inputs and a deliberately injected mismatch is reported in the machine-readable summary.

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

Descrição

Build a reproducible comparison workflow between the Awkernel preprocessing-to-NDT pipeline and a fixed Autoware reference implementation using identical inputs and equivalent algorithm parameters.

Scope:

  • Pin the Autoware commit, relevant dependencies, build configuration, and parameter files
  • Prepare shared test datasets, point cloud maps, coordinate transforms, timestamps, and per-scan initial pose estimates
  • Compare intermediate outputs after crop box filtering and voxel grid downsampling
  • Compare final NDT poses, convergence outcomes, and iteration counts
  • Define numerical tolerances and comparison rules for point ordering, point fields, and floating-point differences
  • Generate machine-readable results and a summary of mismatches
  • Implement Point Cloud Replay and Validate the Preprocessing-to-NDT Pipeline

Acceptance criteria:

  • Both implementations process the same scans, maps, and initial pose estimates without independently evolving their inputs.
  • Parameter mappings and any unavoidable implementation differences are documented.
  • Intermediate point clouds are compared using an order-independent method where ordering is not part of the interface contract.
  • Position and orientation differences are evaluated against predefined tolerances.
  • Convergence-status differences and iteration-count differences are reported; exact iteration-count equality is required only where explicitly justified.
  • The comparison detects deliberately introduced output mismatches.
  • Test data identifiers, commands, configurations, and results are sufficient to reproduce each comparison.

Out of scope:

Performance benchmarking, scheduler evaluation, EKF integration, and proof of correctness against ground truth.

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.