Repository navigation
Grid price chart: show forecast prices differently from published prices #35505
Strike1988
started this conversation in
Ideas
Replies: 2 comments 3 replies
3 replies
|
Update after running G on my own instance with real data (Tibber + The dashed line turns choppy on a step chart. With 15-minute slots a step is only a few pixels wide, about the length of a dash, so small price changes either fall into a gap or show up as stray fragments. The battery forecast does not have this problem because it is a continuous line. The mockup above hid this. So I take back part of my preference for G. The hatched area still marks the forecast clearly, the dash pattern is what does not carry over. A solid line on top of the hatching (close to D) or a longer dash pattern may work better, I have not tried either yet. Any preference from your side before I go on? |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment



Uh oh!
There was an error while loading. Please reload this page.
Picking up on #35208 (comment) ("If you have an idea how we could make this 'stacked' story easier to digest happy to discuss"):
With a
mergedtariff (e.g. Tibber +epex-predictor) the forecast page draws published day-ahead prices and predicted prices exactly the same way. In the example below everything from Friday 0:00 is a prediction, but nothing in the chart says so, and the min/max labels or a tooltip value look just as certain as the real prices.Proposal
Draw the part of the series that comes from the secondary tariff differently. All mockups use the same real data (Tibber up to Thursday 24:00,
epex-predictorafter that).A: pale

B: dashed

C: gray

D: hatched area

E: background band and label

F: combined (pale + dashed + label, tooltip says "forecast")

My preference is F: dashed and pale is the common way to draw a forecast, it works in dark mode and does not rely on color alone. Gray (C) clashes with grid lines and axes, which are gray already.
Implementation sketch
api.Rategets an optionalForecast bool(json:"forecast,omitempty").mergedsets it on the rates appended from the secondary tariff. Planner and optimizer ignore it.forecastRatesappends a fourth element1to those slots ([start, end, value, 1]), so older UIs keep working.PriceChart.vuesplits the series at the first forecast slot and styles the second part; the tooltip adds "forecast" (new i18n key).mergedproduces such rates today, so nothing changes for anyone without it.Open questions:
Happy to send a PR once there is a direction.
All reactions