Implement Controlled Fault Injection for Localization Replay

Offen
#763 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
18/100
Issue-Typ
Feature
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Tech-Stack
rust
Bereich
testing

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

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.

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.