History health reads NO DATA for units with no temperature (gyro, encoders)

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

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
3/5
预计耗时
1-2 天
新手友好度
55/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
活跃
技术栈
python
领域
backend

调研方向

Start with the lifetime-trends spec section “Device table and summary tiles” and find the health rule for temperature limits and open anomalies. Check how it distinguishes units that should report temperature from gyro and CANcoder models that have no temperature signal. Done when those models no longer show NO DATA while units expected to report temperature still do.

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

描述

bug

Split out of IgniteRobotics/flashpoint-private#39 (kept out of the sparkline change, history-shared-sparkline-scale).

Problem

History's health column is temperature limits plus open anomalies. Units that report no temperature at all (the gyro, CANcoders) read NO DATA, which looks like a fault rather than "not applicable".

Possible direction

Show N/A (or health from anomalies alone) when the unit's model has no temperature signal, and leave NO DATA for units that should report temperature but don't.

Scope: lifetime-trends spec, "Device table and summary tiles" (the health rule).

🤖 Generated with Claude Code

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