Live & Pit views

未关闭
#18 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
25/100
Issue 类型
功能
描述清晰度
需要澄清
活跃度
活跃
技术栈
python
领域
full-stack

调研方向

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.

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

描述

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.

主要语言
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 摘要。