mirror of
https://github.com/Hestia-Homes/Model.git
synced 2026-07-12 13:29:04 +00:00
e80be44fd1
A predicted Property (no lodged EPC) got a Plan but nothing else: the synthesised EPC was never written to epc_property, and Baseline Performance was skipped — so property 729529 (portfolio 796 / scenario 1268), predicted from its DA16 1QZ cohort, was "missed" with no predicted-EPC row and no baseline row. Persist the synthesised EPC in the predicted slot (uow.epc.save(..., source= "predicted"), ADR-0031) inside the Plan UoW, then run the Baseline orchestrator for predicted Properties too — it re-hydrates the predicted EPC and establishes the baseline from it. The earlier "lodged only" guard is dropped: by the write block the Property always has a persisted EPC (lodged or predicted); one that could be neither fetched nor predicted raised earlier. Verified against the DB by invoking the real handler for 729529: predicted epc_property rows 0->1 and property_baseline_performance rows 0->1. Baseline on the predicted picture builds cleanly (RHI present, reason pre_sap10). Tests updated: prediction + broadening paths now assert the predicted-slot epc.save and the baseline run. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| applications | ||
| datatypes | ||
| domain | ||
| e2e | ||
| fixtures/epc_prediction | ||
| harness | ||
| infrastructure | ||
| lambdas | ||
| magic_plan | ||
| orchestration | ||
| repositories | ||
| scripts | ||
| utilities | ||
| __init__.py | ||
| conftest.py | ||
| test_lambda_packaging.py | ||