Import status view

Open
  • Is something wrong?
#19 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
python
Domain
analytics, data

Research direction

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.

Written by the indexing model from the issue text.

Description

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.

Dominant language
Python
Stars
0
Forks
1
Avg merge
18h 37m
Merged PRs (30d)
15

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from IgniteRobotics/flashpoint

All issues in IgniteRobotics/flashpoint

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.