Measure Localization Accuracy and Pipeline Performance

Abierto
#753 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 2 días

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
22/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
rust

Línea de trabajo

The issue names no files, so start by finding the preprocessing-to-NDT pipeline in the repository and noting its stages: crop box filtering, voxel grid downsampling and NDT scan matching. Check whether any timing or memory hooks already exist. Done means a documented metric and timing-boundary definition, plus a machine-readable export with sample counts and a reproducible command. Confirm the scope with maintainers first, since the work is large and design-heavy.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

Establish a reproducible evaluation workflow for localization accuracy, execution time, end-to-end latency, and memory usage of the Awkernel preprocessing-to-NDT pipeline.

Scope:

  • Evaluate position and orientation errors against timestamp-aligned ground-truth poses where available
  • Measure execution time for crop box filtering, voxel grid downsampling, and NDT scan matching
  • Measure end-to-end latency from scan availability at the pipeline input to publication of the corresponding localization result
  • Distinguish processing time from queueing, scheduling, and data-transfer delays
  • Measure peak memory usage, separating map preparation, persistent map storage, and per-scan processing
  • Record workload characteristics, including point counts, NDT iteration counts, and convergence outcomes

Acceptance criteria:

  • Metric definitions, timing boundaries, coordinate frames, and measurement methods are documented.
  • Accuracy results include position and orientation error distributions, with ground-truth sources and alignment procedures specified.
  • Datasets without ground truth are explicitly identified; reference-output differences are not reported as ground-truth accuracy.
  • Timing results include median, tail percentiles, and maximum observed values, together with sample counts.
  • Failed, non-converged, and dropped scans are reported rather than silently excluded.
  • Peak memory measurements identify which allocations and buffers are included.
  • Hardware, software versions, parameters, replay rate, warm-up procedure, and instrumentation overhead are recorded.
  • Results are exported in a machine-readable format with reproducible evaluation commands.

Out of scope:

Formal worst-case execution-time guarantees, EKF integration, vehicle-control evaluation, and broad scheduler comparisons.

Lenguaje dominante
Rust
Estrellas
282
Forks
12
Merge medio
2 d 9 h
PR fusionados (30 d)
28

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de tier4/awkernel

Todos los issues de tier4/awkernel

Issues similares

Más issues de Rust

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.