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

Ouverte
#758 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 2 jours

@nokosaaan y travaille déjà.

Depuis le 8/5/2026.

  • #690 par @nokosaaan — ouverte

Évaluation

Difficulté
5/5
Temps estimé
Plus d'une semaine
Accessibilité débutants
18/100
Type d'issue
Fonctionnalité
Clarté
Plutôt claire
Activité
Active
Stack technique
rust

Piste de recherche

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.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

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.

Langage dominant
Rust
Étoiles
282
Forks
12
Merge moyen
2 j 9 h
PR mergées (30 j)
28

Préparer son environnement

Ce projet ne fournit ni conteneur de développement, ni Dockerfile, ni guide de contribution : l'installation est à votre charge. Commencez par son README, et consultez notre guide de la première contribution pour les étapes générales.

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de tier4/awkernel

Toutes les issues de tier4/awkernel

Issues similaires

Plus d'issues Rust

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.