Evaluate Localization Accuracy and Timing Under Faults and Overload

未關閉
#765 0 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

維護者通常 2 天內回覆

還沒有人認領這個 Issue。

評估

難度
5/5
預估耗時
一週以上
新手友好度
12/100
Issue 類型
功能
描述清晰度
需要釐清
活躍度
活躍
技術堆疊
rust

研究方向

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.

由索引模型根據 Issue 內容生成。

描述

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.

主要語言
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 摘要。