mirror of
https://github.com/ChuckBuilds/LEDMatrix.git
synced 2026-08-21 10:29:06 +00:00
ChuckBuildsandClaude Opus 5
a4290e8a28
Two Vegas telemetry lines were 37% of a running rig's entire log volume: "Vegas FPS" every five seconds and "Scroll progress" on its own five-second timer, 712 lines in half an hour, every one a journal write to an SD card. The FPS line is the interesting one, because almost none of it was news. Measured over two hours on that rig: 1410 samples, 98.5% of them within 10% of target. What the other 1.5% contained was a reading of 8.6fps against a target of 60 -- a real stall, sitting invisible inside 1389 lines that read "59.6". So it now reports at INFO when the frame rate falls short of target, when it recovers from a shortfall, and on a five-minute heartbeat so a healthy marquee still shows a pulse. Everything else drops to debug. Replaying the same two hours of real samples through the committed logic: 1410 -> 53 INFO lines, a 96% reduction, and all 21 degraded samples are retained, worst reading included. The signal survives; the wall of "fine" does not. Scroll progress is demoted outright. It reports how far along a marquee is, which is what you turn debug on to watch, not something an operator needs in the journal on a device that scrolls all day. 543 vegas and scroll tests pass. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01STMbQE4YctTacQXfbYqKuW