I run Pumas all the time, suggest use log scale for power use

[cw1nte]

Since power is often way lower than peak I'm tempted to fork code and add log scale rather than linear for power use. 90% or more of time the Packager power usage history is blank (90mW vs 10W peak) but could show relative changes in the lower power ranges at the cost of seeing small actual differences in higher power levels.
I think a log scale would be much more informative overall... once the code is there I'd try it for all of the power/usage displays?
Ideally some tick mark y-scale might fit, or 4 or 5 maxima labelled scroll across the screen with display to help read values?

Thought I'd suggest it first since it would be the best way for everyone to get the benefit of the idea.

...and THANKS

[graelo]

Hi, I love that idea.

I'm currently preparing a full refactor of the UI code: I'll drop ratatui (served me well for years, but too static) in favor of iocraft. This will allow flow layout, selecting which graphs are displayed and their config like time & value scales, controlled with a config file.

Since the UI refactor is in the works, one pragmatic approach for your idea would be adding a CLI flag for logarithmic scale (--log-scale power) while keeping the current rendering code. Would that work for you?

PS: Basically this means your PR would not implement your full vision yet (tick marks, etc), but it would be useful enough on a daily basis in the meantime.