You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Noticed that the uppermost value in the scale is always missing.
For example, in the screenshot below, the peak graph value is 3216W, yet the y-axis scale stops at 2000W instead of 3000W.
The mean average of the feed value between 14:33 & 14:44 was 3080W.
Just noticed this.
Related:
Y axis should have enabled as an option, lines on the background so the graph is more readable.
I simple can't know the low, night time energy usage through this app, because I can't match up the graphing to an actual value :/
A more significant defect with the y axis, from an data visualisation good practice point of view, is the way 0 is not at the bottom. The filled area beneath the curve absolutely should not extend to negative values, as it does now. It should be easy to see, for example, that a period of 400W consumption next to a 200W period is twice as high; there should be a proportionality between the visual height and the power consumption for optimal interpretability.
I contend this is really a defect, not an enhancement.
Noticed that the uppermost value in the scale is always missing.
For example, in the screenshot below, the peak graph value is 3216W, yet the y-axis scale stops at 2000W instead of 3000W.
The mean average of the feed value between 14:33 & 14:44 was 3080W.
Also apparent with @glynhudson screenprint;
What is the peak value??
The text was updated successfully, but these errors were encountered: