Implement Localization Accuracy and Real-Time Metrics

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

Maintainer antworten meist innerhalb von 2 Tagen

Dieses Issue hat noch niemand übernommen.

Bewertung

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

Rechercherichtung

The issue names no files, tests or entry points, so start by finding the existing localization pipeline and its task scheduling code in the repository. Decide the measurement boundaries and clock mappings before adding any instrumentation, since the issue requires each metric to have a documented definition, unit and clock domain. Done means synthetic traces with known delays and deadline misses produce the expected metric values, and the summaries can be reproduced from machine-readable output. This is design-heavy work, so discuss the approach with maintainers before writing code.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

Implement consistent instrumentation and reporting for localization accuracy, scheduling delay, deadline misses, end-to-end latency, and input data age in the integrated Awkernel localization pipeline. Provide reusable metrics for concurrent replay evaluation and subsequent robustness experiments.

Scope:

  • Define measurement boundaries and clock mappings for all metrics
  • Measure position and orientation errors against timestamp-aligned ground truth where available
  • Measure scheduling delay from task readiness to execution start, distinguishing it from input-release delay and dependency waiting
  • Detect deadline misses using explicitly defined release times, deadlines, and completion events
  • Measure per-scan latency from pipeline input availability to the associated NDT result
  • Track when NDT and gyro odometry measurements are incorporated into EKF outputs
  • Measure the age of each consumed input from its measurement timestamp to consumption time
  • Export per-event records and aggregated summaries

Acceptance criteria:

  • Each metric has a documented definition, unit, clock domain, and applicable task or output.
  • Trace identifiers associate scans, task executions, measurements, and outputs without relying solely on timestamp proximity.
  • EKF output latency and freshness are reported separately for relevant input streams rather than attributed to an arbitrary latest scan.
  • Deadline reports include miss counts, evaluated-job counts, miss ratios, and tardiness; dropped or unfinished jobs are reported separately.
  • Timing summaries include median, tail percentiles, and maximum observed values with sample counts.
  • Accuracy reports distinguish ground-truth errors from differences against a reference implementation.
  • Synthetic traces with known delays and deadline violations validate the metric calculations.
  • Instrumentation overhead is measured and reported.
  • Machine-readable results and analysis commands are sufficient to reproduce the summaries.

Out of scope:

Replay workload generation, changes to localization algorithms or scheduling policies, and formal worst-case timing guarantees.

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.