Import status view

未关闭
  • 哪里不对？
#19 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

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

调研方向

Start by reading the P4 shell views and the ledger schema for session_hoots, files, logs, hoot_logs, and match_phases; the issue names the fields the view must surface but does not identify their files. Check the dependencies and Live import updates (#23) to understand the available data and table patterns. Done means a read-only per-event, per-match audit view shows missing logs, import warnings, and suspect timing, with drill-through to Replay and AdvantageScope.

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

描述

roadmap

Size: M · Depends on: IgniteRobotics/flashpoint-private#70, IgniteRobotics/flashpoint-private#71, IgniteRobotics/flashpoint#23

2026-10-19: the problem list (import and data problems) and the live feed come from Live import updates (#23). This view builds the per-event audit table on the same list.

Scope

A view in the P4 shell that answers three questions about the lake: are we missing logs, did they all import clean, and do the clocks line up? Most of the data is already in the ledger. Little of it is visible today outside flashpoint doctor and SQL.

  • Missing logs:
    • per session: expected buses (from the robot config) against the hoots actually grouped in session_hoots, so a session with a wpilog but no CANivore hoot stands out;
    • per event: gaps in the match sequence (Q1…Qn from FMS info or filenames). The Blue Alliance schedule fills in the expected list when online, which stays optional;
    • files seen by acquire (pulls) that never reached success.
  • Clean import:
    • files.stage, reason and warnings (quarantined, incomplete-read, short-coverage);
    • logs.truncated_bytes and orphan_records, hoot_logs.read_status and integrity;
    • unmapped_devices and logs with no CAN inventory (legacy epochs);
    • new: record when owlet exports of a hoot differed in size (#4 tail loss). Today that is only a log line, so it can't be counted.
  • Timing:
    • per hoot: session_hoots.offset_us, method, confidence, spread_us, bus_agreement_us, with low-confidence or disagreeing alignments flagged;
    • per wpilog: anchor_source and utc_offset_us, flagging logs anchored by fallback instead of systemTime;
    • framing: matches whose match_phases came from a fallback source.
  • Shape: a table per event, one row per match, a status light per check, and drill-through to Replay and AdvantageScope. It is read-only, like the other P4 views. Re-ingest or re-derive stays on the CLI.
  • Exit: after an event, a student can see in one screen which matches are missing logs, which imported with warnings, and which have suspect clock alignment, without SQL.

Moved from the rewrite roadmap on 2026-10-19. That doc keeps the dependency graph, migration, quality gates and risks. Status lives here. Author-year citations are in references.md. pitfall N refers to 03-pitfalls-and-performance.md.

主要语言
Python
星标
0
派生
1
平均合并
18 小时 37 分钟
30 天内合并 PR
15

环境准备

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

从这里开始

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

IgniteRobotics/flashpoint 的其他 Issue

查看 IgniteRobotics/flashpoint 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

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