Evaluate Concurrent NDT, Gyro Odometry, and EKF Processing with Replay

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

Los mantenedores suelen responder en 2 días

@nokosaaan ya está trabajando en esto.

Desde el 8/5/2026.

  • #690 de @nokosaaan — abierto

Evaluación

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

Línea de trabajo

The payload names no files or tests, so start by locating the existing replay/benchmark harness and the documented task/CPU assignments for NDT, gyro odometry, and EKF in the Awkernel tree. Read the timing and trace configuration first, then identify how input release, queues, and output publication are currently instrumented. Done means a documented replay configuration with reproducible traces and metrics for scheduling delay, dropped inputs, convergence, and localization error against a low-interference baseline.

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

Descripción

Establish a reproducible replay-based evaluation of the integrated Awkernel localization pipeline, with NDT, gyro odometry, and EKF processing active concurrently. Evaluate scheduling interference, temporal correctness, and localization behavior under representative workloads.

Scope:

  • Replay timestamped LiDAR, IMU, and vehicle velocity data while preserving their relative timing and input rates
  • Run NDT, gyro odometry, and periodic EKF processing concurrently using documented task and CPU assignments
  • Include the EKF-to-NDT initial-pose feedback path with causal data availability
  • Compare a low-interference baseline with concurrent execution under increasing NDT workloads
  • Trace input release, task readiness, execution, measurement consumption, and output publication
  • Record queue occupancy, dropped inputs, convergence outcomes, and localization results

Acceptance criteria:

  • Replay datasets, clock mapping, playback rate, task periods, deadlines, priorities, and CPU assignments are documented.
  • Input release is independent of processing completion, so slow processing does not silently reduce the offered workload.
  • Input and task traces confirm that the intended concurrent workload is exercised.
  • Buffering and overflow policies are explicit, and delayed or dropped inputs remain visible in the results.
  • Scheduling delay, execution time, deadline misses, output latency, and consumed-input age are measured with defined timing boundaries.
  • Localization error and NDT convergence are evaluated alongside timing metrics, using ground truth where available.
  • Repeated runs report variability and retain sufficient configuration and trace data for reproduction.
  • Any differences from a reference run are analyzed with respect to both numerical behavior and measurement-consumption timing.

Out of scope:

Live sensor integration, closed-loop vehicle control, exhaustive scheduler comparisons, and systematic fault injection reserved for M3.

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.