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

Offen
#758 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 2 Tagen

@nokosaaan arbeitet bereits daran.

Seit 08.5.2026.

  • #690 von @nokosaaan — offen

Bewertung

Schwierigkeit
5/5
Geschätzter Aufwand
Über eine Woche
Anfängerfreundlichkeit
18/100
Issue-Typ
Feature
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Tech-Stack
rust

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

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.

Vorherrschende Sprache
Rust
Sterne
282
Forks
12
Ø Merge
2 T. 9 Std.
Gemergte PRs (30 T.)
28

Entwicklungsumgebung

Dieses Projekt bietet weder Dev-Container noch Dockerfile noch Beitragsleitfaden – die Einrichtung liegt bei Ihnen. Beginnen Sie mit der README; die allgemeinen Schritte stehen in unserem Leitfaden für den ersten Beitrag.

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus tier4/awkernel

Alle Issues in tier4/awkernel

Ähnliche Issues

Weitere Issues zu Rust

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.