4 Commits

Include renames

Author	SHA1	Message	Date
Claude	5d27f8496f	SAFETY-78: maintenance drain at N=2 no longer stalls ... At two inverters the drain pins its pack and the site target is split around the pin. Below the pin the other pack had to charge, the allocator refused the opposite directions, and the site sat at 0 W with an ARBITER line every cycle (house below or above the drain rate, or a grid charge). main.py now files a site limit `drain` (lo = what the pin places, at P_MAINTENANCE) at N>=2 while a pack drains, so the other pack only adds power in the same direction. A drain that cannot give power waits with one log line. With battery modes on, no grid charge while a pack drains, and the other battery's card says why. N=1 is byte-identical. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-09-29 19:52:51 +02:00
Claude dev agent	902524ae5e	OPT-11 P3: price runs per battery ... Cheap and expensive hours as runs of consecutive firm price slots (priceruns.py); each battery's role per tick from its mode (modetrade.py): grid charging for Leftover solar / Cheap hours only, never Solar first; holding for the expensive runs; selling per battery (pack_sell) above the spread and the floor. The site trade is sized inside the modes (loop bound) and the peak guard's headroom; a run edge reseeds the loop. Cheap hours only and selling are enabled on the Batteries screen and in the HA select (appended). The site Why row no longer says "held back" when the peak limit pushes power up (F2). Modes off: byte-identical to 7a00f12 on the trade path. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-09-29 02:37:44 +02:00
glenn schrooyenandClaude Opus 5.5	ffc9a4d721	OPT-11 P1 review: a mode never beats the peak floor; SAFETY-03 kept at the rail ... - arbiter: a mode now gives way only as far as a site limit above P_MODE needs (_unit_modes at N>1, _site_mode at N=1). Before, the modes were released only when the peak floor bound S, so a trade won above the floor kept them and placed less than the floor (an Off battery at N=1 went to 0 W under a 2000 W floor), and a capped grid charge released an Off battery. While released, held batteries weigh 0 and carry only the shortfall. - control: a side of the loop bound that reaches the rail is left to the rail, so SAFETY-03's i_clamped still fires with every battery on. - opt11_identity: add maintenance scenarios and a 6000-case arbiter digest (peak floor, trades, maintenance, refusals); a5dddad digests pinned. - tests: test_arbiter part 11, test_control (g), test_modes (0/1 refused, loop bound counts live units only). DOCS and DECISIONS say the new rule. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01UBtqPrG1mDLXzTEBnhEkkV	2026-09-28 19:41:36 +02:00
Claude dev agent	d69fd8fbfd	OPT-11 P1: per-battery mode limits, on/off, solar order ... A battery's mode is a soft unit limit (source `mode`, P_MODE 35) kept apart from the hard limits in pre_resolve(). The allocator applies it only while the site target is decided at or below 35 (new Resolution.deciding_priority), so the peak floor releases it and a mode `hi` never meets the site `lo`. At N=1 resolve() applies the same rule to the site target after stage 2. A mode range without 0 W is dropped as a software fault, so REFUSE_SIGN stays unreachable from a mode. compute() gets the loop bound (sum over live units of hard limits with modes applied), so the loop never asks for watts no battery may give and the saturation freeze never parks on them. While charging, Leftover solar weighs 0 so Solar first fills first. Store keys pack_use and pack_mode per battery, set by two new /action values; Off stops and skips maintenance with a log line. Minimal Batteries cards (EN/NL). Off by default (battery_modes_enabled); off, commands are byte-identical to a5dddad at N=1 and N=2 (test_modes.py part 1). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-09-28 18:51:29 +02:00