Import status view

オープン
  • 何か問題がありますか？
#19 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
5/5
見積もり時間
1週間以上
初心者へのやさしさ
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分
マージ済み PR（30日）
15

環境構築

このプロジェクトには開発コンテナ、Dockerfile、コントリビューションガイドがありません。まず README を読み、一般的な手順ははじめてのコントリビューションガイドを参照してください。

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

IgniteRobotics/flashpoint のほかの issue

IgniteRobotics/flashpoint の issue をすべて見る

似ている issue

Python の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。