3 Commits

Include renames

Author	SHA1	Message	Date
glenn schrooyenandClaude	f095ca9268	OPT-27 round 2: a kept tomorrow figure is bounded on both sides ... Hold.stand_in(): day0 <= now < day0 + 3 h. A tomorrow sensor is asked with day0 = the next midnight, so the upper bound alone was true all day and a figure stood in at any hour. test_opt27.py covers daytime tomorrow outages. Co-Authored-By: Claude <noreply@anthropic.com>	2026-10-29 23:11:44 +01:00
glenn schrooyenandClaude	1eb572f513	OPT-27: test_modes_p4 says what a covered sensor does; test_opt27 guards ... test_modes_p4.py: 'the forecast is lost mid-run' now loses it for good (a hold that never covers); a second scenario is the same loss with the hold, which keeps Leftover solar charging. test_opt27.py: a failing check no longer hides the ones after it. Co-Authored-By: Claude <noreply@anthropic.com>	2026-10-29 21:59:21 +01:00
glenn schrooyenandClaude	cdcbe7dbb6	OPT-27: the night plan keeps the last fresh solar forecast ... Forecast.Solar's sensors stop updating in the evening, so at night every such site had no forecast: the night cheap run needed 1.5x the cycle cost and Leftover solar planned nothing. One missed poll also dropped it at once. solarfc.Hold keeps the last fresh reading of each sensor, for the day it is for. A missing or stale sensor is covered by it for up to FRESH_S (a short outage), and from the end of the bell (20:00) until local midnight + 3 h however old. A tomorrow figure is tomorrow's until midnight and then today's; a today figure is only today's. Stored in the controller's store (solar_fc_hold), so an evening restart keeps it. The forecast line says 'Solar forecast read 17:05, used for tonight's plan.' (EN, NL). test_tariff24_weather.py runs with a hold that never covers: it tests what the plan does when the forecast IS lost. Co-Authored-By: Claude <noreply@anthropic.com>	2026-10-29 21:06:09 +01:00