Implement Controlled Fault Injection for Localization Replay

未关闭
#763 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 2 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
18/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
rust
领域
testing

调研方向

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.

由索引模型根据 Issue 内容生成。

描述

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.

主要语言
Rust
星标
282
派生
12
平均合并
2 天 9 小时
30 天内合并 PR
28

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

tier4/awkernel 的其他 Issue

查看 tier4/awkernel 的全部 Issue

相似的 Issue

更多 Rust Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。