Evaluate Localization Accuracy and Timing Under Faults and Overload

Aperta
#765 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 2 giorni

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
12/100
Tipo di issue
Funzionalità
Chiarezza
Da chiarire
Stato di attività
Attiva
Stack tecnologico
rust

Direzione di ricerca

The issue names no source files or tests. Start by locating the M2 instrumentation and the input and overload policy definitions it refers to, then the localization pipeline entry point. Done means fault-free baseline and fault scenario runs that report accuracy, latency, freshness, deadline misses and data loss, with machine-readable results and reproduction commands.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Evaluate the integrated Awkernel localization pipeline under controlled input faults and computational overload. Reuse the M2 instrumentation to quantify localization accuracy, end-to-end latency, input data age, deadline misses, and dropped-data rates, including recovery after abnormal conditions end.

Scope:

  • Establish a fault-free baseline with motion distortion correction enabled
  • Run documented scenarios involving delivery delays, timestamp offsets, message loss, and computational overload
  • Evaluate individual faults and selected combinations using the defined input and overload policies
  • Measure accuracy, latency, freshness, deadline behavior, and data loss throughout each run
  • Analyze recovery behavior and accuracy–timing trade-offs

Acceptance criteria:

  • Each experiment records its dataset, ground-truth source where available, configuration, fault schedule, workload, and policy settings.
  • Position and orientation errors are measured against aligned ground truth; reference-output differences are reported separately.
  • Timing summaries include median, tail percentiles, maximum observed values, and sample counts.
  • Input age is reported per relevant stream; timestamp-offset experiments distinguish apparent age from age derived from the preserved original timeline.
  • Deadline-miss ratios use documented job populations, with unfinished or cancelled jobs accounted for explicitly.
  • Dropped-data rates specify their denominator and distinguish injected loss, buffer overflow, stale-input rejection, and discarded late results without double counting.
  • Missing outputs and prediction-only intervals remain visible rather than being excluded from accuracy and latency summaries.
  • Recovery time and any persistent degradation after fault removal are reported using predefined criteria.
  • Repeated runs quantify variability, and machine-readable results and reproduction commands are retained.

Out of scope:

New instrumentation or fault-injection frameworks, changes to localization algorithms or scheduling policies, and formal safety or worst-case timing guarantees.

Lingua principale
Rust
Stelle
282
Fork
12
Merge medio
2g 9h
PR unite (30g)
28

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di tier4/awkernel

Tutte le issue di tier4/awkernel

Issue simili

Altre issue su Rust

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.