Implement Controlled Fault Injection for Localization Replay

Ouverte
#763 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
18/100
Type d'issue
Fonctionnalité
Clarté
Plutôt claire
Activité
Active
Stack technique
rust
Domaine
testing

Piste de recherche

No files or tests are named in the payload. Start by locating Awkernel's localization replay pipeline and its scenario/configuration entry points, then identify where input streams, timestamps, message delivery, logging, and competing tasks are handled. Done means reproducible fault scenarios with recorded configuration/events, tests checking injected events against their specification, and documented seeds/reproduction commands.

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

Description

Implement reproducible injection of input delays, timestamp offsets, dropped messages, and computational overload into localization replay experiments on Awkernel. Exercise the integrated pipeline under controlled abnormal conditions without modifying the original datasets.

Scope:

  • Inject configurable delivery delays and jitter into selected input streams
  • Apply timestamp offsets independently of delivery timing
  • Drop individual messages or configurable bursts using deterministic rules or seeded randomness
  • Introduce controlled computational load through configurable competing tasks
  • Support isolated faults and explicitly defined combinations
  • Record the injection configuration and actual events observed during each run

Acceptance criteria:

  • Each scenario specifies the target stream or task, injection point, start time, duration, and magnitude.
  • Delivery-delay injection preserves measurement timestamps unless timestamp modification is explicitly enabled.
  • Timestamp-offset injection changes only the configured timestamp fields and documents how per-point times are affected.
  • Drop patterns are reproducible, and injected losses are distinguishable from pipeline overflow or processing failures.
  • Computational-load scenarios specify workload, CPU affinity, priority, and activation pattern, with actual interference measured.
  • Replay continues to offer inputs at the configured rate rather than slowing down to match processing completion.
  • Fault-free control runs use the same datasets and baseline configuration.
  • Tests verify that injected events match their specification; deviations caused by scheduling are recorded.
  • Logs retain original and modified timing information, message identifiers, and injection decisions.
  • Scenarios, seeds, configurations, and reproduction commands are documented.

Out of scope:

Defining recovery policies, modifying localization algorithms, physical sensor faults, and vehicle-level safety validation.

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.