Evaluate Localization Accuracy and Timing Under Faults and Overload

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

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

Personne n'a encore pris cette issue.

Évaluation

Difficulté
5/5
Temps estimé
Plus d'une semaine
Accessibilité débutants
12/100
Type d'issue
Fonctionnalité
Clarté
À clarifier
Activité
Active
Stack technique
rust

Piste de recherche

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.

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

Description

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.

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.