Implement Localization Accuracy and Real-Time Metrics
维护者通常 2 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 15/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- rust
调研方向
The issue names no files, tests or entry points, so start by finding the existing localization pipeline and its task scheduling code in the repository. Decide the measurement boundaries and clock mappings before adding any instrumentation, since the issue requires each metric to have a documented definition, unit and clock domain. Done means synthetic traces with known delays and deadline misses produce the expected metric values, and the summaries can be reproduced from machine-readable output. This is design-heavy work, so discuss the approach with maintainers before writing code.
由索引模型根据 Issue 内容生成。
描述
Implement consistent instrumentation and reporting for localization accuracy, scheduling delay, deadline misses, end-to-end latency, and input data age in the integrated Awkernel localization pipeline. Provide reusable metrics for concurrent replay evaluation and subsequent robustness experiments.
Scope:
- Define measurement boundaries and clock mappings for all metrics
- Measure position and orientation errors against timestamp-aligned ground truth where available
- Measure scheduling delay from task readiness to execution start, distinguishing it from input-release delay and dependency waiting
- Detect deadline misses using explicitly defined release times, deadlines, and completion events
- Measure per-scan latency from pipeline input availability to the associated NDT result
- Track when NDT and gyro odometry measurements are incorporated into EKF outputs
- Measure the age of each consumed input from its measurement timestamp to consumption time
- Export per-event records and aggregated summaries
Acceptance criteria:
- Each metric has a documented definition, unit, clock domain, and applicable task or output.
- Trace identifiers associate scans, task executions, measurements, and outputs without relying solely on timestamp proximity.
- EKF output latency and freshness are reported separately for relevant input streams rather than attributed to an arbitrary latest scan.
- Deadline reports include miss counts, evaluated-job counts, miss ratios, and tardiness; dropped or unfinished jobs are reported separately.
- Timing summaries include median, tail percentiles, and maximum observed values with sample counts.
- Accuracy reports distinguish ground-truth errors from differences against a reference implementation.
- Synthetic traces with known delays and deadline violations validate the metric calculations.
- Instrumentation overhead is measured and reported.
- Machine-readable results and analysis commands are sufficient to reproduce the summaries.
Out of scope:
Replay workload generation, changes to localization algorithms or scheduling policies, and formal worst-case timing guarantees.
- 主要语言
- Rust
- 星标
- 282
- 派生
- 12
- 平均合并
- 2 天 9 小时
- 30 天内合并 PR
- 28
环境准备
这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
tier4/awkernel 的其他 Issue
-
难度 1/5 1 小时以内 新手友好度 88/100
维护者通常 2 天内回复
-
难度 2/5 1-3 小时 新手友好度 75/100
维护者通常 2 天内回复
-
难度 4/5 3-5 天 新手友好度 48/100
维护者通常 2 天内回复
-
难度 4/5 3-5 天 新手友好度 48/100
维护者通常 2 天内回复
-
难度 4/5 3-5 天 新手友好度 25/100
维护者通常 2 天内回复
相似的 Issue
-
marketing
难度 2/5 1-3 小时 新手友好度 82/100
维护者通常 1 天内回复
-
难度 1/5 1 小时以内 新手友好度 88/100
flashbots/panetiere#46 · 1 条评论 ·
维护者通常 5 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100
jlcodes99/cockpit-tools#3190 ·
维护者通常 4 天内回复
-
难度 2/5 1-3 小时 新手友好度 72/100
Feyisara2108/stellargive#1376 ·
维护者通常 1 天内回复
-
area:post bug effort:medium P7 source:agent
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 1 天内回复