Import status view

Abierto
  • ¿Algo no está bien?
#19 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
35/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
python
Área
analytics, data

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.

Lenguaje dominante
Python
Estrellas
0
Forks
1
Merge medio
18 h 37 min
PR fusionados (30 d)
15

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de IgniteRobotics/flashpoint

Todos los issues de IgniteRobotics/flashpoint

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.