Repository navigation

test(replay): replay a Predbat log forwards from a debug yaml - exact and simulated, with a plan timeline - #5363

Draft

chalfontchubby wants to merge 33 commits into

feat/log-replay-inputsfrom

tools/debug-replay-forward

Commits on Oct 7, 2026
- test(replay): replay a Predbat log forwards from a debug yaml
  
  chalfontchubby
  and
  claude
  committed
  de96526
- test(replay): rescan the candidate rate windows on every replayed re-plan
  
  chalfontchubby
  and
  claude
  committed
  2ea3b57
- test(replay): chart a replay - actual SoC against live and replayed export targets
  
  chalfontchubby
  and
  claude
  committed
  4ca258d
- test(replay): simulated mode, and date-aware plan windows
  
  chalfontchubby
  and
  claude
  committed
  2772ff6
- test(replay): use the logged load divergence on every replayed re-plan
  
  chalfontchubby
  and
  claude
  committed
  9e7005a
- feat(dummy_inverter): simulated inverter and battery component; replay SoC RMS error
  
  chalfontchubby
  and
  claude
  committed
  ffc530e
- test(replay): compare like with like, and replay the inputs fetch rebuilds each run
  
  chalfontchubby
  and
  claude
  committed
  077c98f
- test(replay): stop at a logged version change
  
  chalfontchubby
  and
  claude
  committed
  14d008e
- test(replay): mark a logged version change rather than stopping at it
  
  chalfontchubby
  and
  claude
  committed
  d521e0c
- test(replay): use the logged PV and load forecasts when the log has them
  
  chalfontchubby
  and
  claude
  committed
  8287c0c
- test(replay): --replay_set name=value overrides a setting for what-if replays
  
  chalfontchubby
  and
  claude
  committed
  f5f4015
- test(replay): rename --replay_set to --override and apply it to single debug replays too
  
  chalfontchubby
  and
  claude
  committed
  7c893dc
- docs(debug-journal): forward log replay traps - single day, Replay input lines, the 8-hourly config refresh re-plan
  
  chalfontchubby
  and
  claude
  committed
  64dc533
- test(replay): rescan the rate min/max and forward rate curves from now on every replayed re-plan
  
  chalfontchubby
  and
  claude
  committed
  ece1184
- test(replay): start each re-plan from the SoC the live plan used, not the one logged after executing it
  
  chalfontchubby
  and
  claude
  committed
  3ebf58c
- test(replay): carry a log replay across midnight
  
  chalfontchubby
  and
  claude
  committed
  6fd3422
- test(replay): follow a live re-plan of an invalid plan
  
  chalfontchubby
  and
  claude
  committed
  86e566d
- test(replay): clear the p90 guard's signatures every run, as fetch does; mark each replayed run in the replay's log
  
  chalfontchubby
  and
  claude
  committed
  316d98c
- test(replay): read the exact state and rates lines from the log
  
  chalfontchubby
  and
  claude
  committed
  3b6e8e5
- test(replay): tell a sensor-triggered recompute from an invalid plan
  
  chalfontchubby
  and
  claude
  committed
  4d3a560
- test(replay): read the exact load forecast line
  
  chalfontchubby
  and
  claude
  committed
  14f136b
- test(replay): read the exact PV forecast line
  
  chalfontchubby
  and
  claude
  committed
  b5e0734
- test(replay): refresh the load forecast every run, as live does, not only on re-plans
  
  chalfontchubby
  and
  claude
  committed
  ccc8ca6
- test(replay): read the logged car state
  
  chalfontchubby
  and
  claude
  committed
  61a84c7
- test(replay): read the logged inverter state, the rates in force and the exact load divergence
  
  chalfontchubby
  and
  claude
  committed
  89b5b79
- test(replay): read the compact load forecast line, and the battery temperature from the state line
  
  chalfontchubby
  and
  claude
  committed
  060340f
- test(replay): chart a full plan timeline - charge, hold, freeze, export and car - for live and replay
  
  chalfontchubby
  and
  claude
  committed
  378108d
- test(replay): model a car charging now outside its plan every run, as dynamic_load() does live
  
  chalfontchubby
  and
  claude
  committed
  3c69a8d
- docs(replay): list the inputs the replay now reads, and describe the plan timeline chart
  
  chalfontchubby
  and
  claude
  committed
  98254ca
- test(replay): read a logged load divergence of None, as the plan now logs it when divergence is off
  
  chalfontchubby
  and
  claude
  committed
  07a1416
- test(replay): replay logs from before the "Replay input:" lines, approximately, back to v8.8
  
  chalfontchubby
  and
  claude
  committed
  9ea72cb
Commits on Oct 8, 2026
- test(replay): total the SoC across inverters when a log has no totals line
  
  chalfontchubby
  and
  claude
  committed
  b90658d
Commits on Oct 9, 2026
- docs(debug-journal): when to use the forward log replay, and its current traps
  
  chalfontchubby
  and
  claude
  committed
  eee66f1

Navigation Menu

Repository navigation

test(replay): replay a Predbat log forwards from a debug yaml - exact and simulated, with a plan timeline - #5363

test(replay): replay a Predbat log forwards from a debug yaml - exact and simulated, with a plan timeline#5363
chalfontchubby wants to merge 33 commits into
feat/log-replay-inputsfrom
tools/debug-replay-forward

Commits on Oct 7, 2026

test(replay): replay a Predbat log forwards from a debug yaml

test(replay): rescan the candidate rate windows on every replayed re-plan

test(replay): chart a replay - actual SoC against live and replayed export targets

test(replay): simulated mode, and date-aware plan windows

test(replay): use the logged load divergence on every replayed re-plan

feat(dummy_inverter): simulated inverter and battery component; replay SoC RMS error

test(replay): compare like with like, and replay the inputs fetch rebuilds each run

test(replay): stop at a logged version change

test(replay): mark a logged version change rather than stopping at it

test(replay): use the logged PV and load forecasts when the log has them

test(replay): --replay_set name=value overrides a setting for what-if replays

test(replay): rename --replay_set to --override and apply it to single debug replays too

docs(debug-journal): forward log replay traps - single day, Replay input lines, the 8-hourly config refresh re-plan

test(replay): rescan the rate min/max and forward rate curves from now on every replayed re-plan

test(replay): start each re-plan from the SoC the live plan used, not the one logged after executing it

test(replay): carry a log replay across midnight

test(replay): follow a live re-plan of an invalid plan

test(replay): clear the p90 guard's signatures every run, as fetch does; mark each replayed run in the replay's log

test(replay): read the exact state and rates lines from the log

test(replay): tell a sensor-triggered recompute from an invalid plan

test(replay): read the exact load forecast line

test(replay): read the exact PV forecast line

test(replay): refresh the load forecast every run, as live does, not only on re-plans

test(replay): read the logged car state

test(replay): read the logged inverter state, the rates in force and the exact load divergence

test(replay): read the compact load forecast line, and the battery temperature from the state line

test(replay): chart a full plan timeline - charge, hold, freeze, export and car - for live and replay

test(replay): model a car charging now outside its plan every run, as dynamic_load() does live

docs(replay): list the inputs the replay now reads, and describe the plan timeline chart

test(replay): read a logged load divergence of None, as the plan now logs it when divergence is off

test(replay): replay logs from before the "Replay input:" lines, approximately, back to v8.8

Commits on Oct 8, 2026

test(replay): total the SoC across inverters when a log has no totals line

Commits on Oct 9, 2026

docs(debug-journal): when to use the forward log replay, and its current traps