Live & Pit views

Open
#18 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
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Active
Tech stack
python
Domain
full-stack

Research direction

Start with the rewrite roadmap in docs/rewrite/06-roadmap.md and the P4 shell views under web/static/views/; the issue also points to docs/rewrite/references.md and docs/rewrite/03-pitfalls-and-performance.md. Resolve the listed dependencies, identify data sources for pit spin-test current, fault counts, firmware events, and batteries, and settle whether views may write. Done means Live and Pit views are integrated in the P4 shell with the required data and checks.

Written by the indexing model from the issue text.

Description

roadmap

Size: M · Depends on: IgniteRobotics/flashpoint#17, IgniteRobotics/flashpoint-private#71, IgniteRobotics/flashpoint#22

2026-10-19: live CAN health (the NT client, relay and a Live CAN view for shake and drive tests) is split out as its own change in IgniteRobotics/flashpoint#22. This issue keeps the rest of Live and the Pit board, which can consume IgniteRobotics/flashpoint#22's results.

Scope

The canvas's Live and Pit boards read the robot, not the lake, so P4 left them out. They become one change after P4 and P3:

  • an NT4 client (or a small relay so one robot connection serves many viewers) feeding Live at about 2 Hz;
  • the Pit board's checks and GO / DECIDE / NO-GO verdict;
  • both as views in the P4 shell: one file in web/static/views/ and one FP.view call each, no restyling.
  • Needs first: data sources for pit spin-test current, fault counts, firmware events, and batteries (none are logged today), and a decision on whether views may write (notes, swaps, pit tasks); P4 views are read-only.

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.