mirror of
https://github.com/Hestia-Homes/Model.git
synced 2026-07-12 13:29:04 +00:00
645789456e
Walked the water-heating worksheet section: assumed occupancy (42) matched exactly (2.4234 both sides), but (43) average daily hot water use was 117.41 L/day (Elmhurst) vs 110.73 L/day (ours) — same occupancy, different shower/bath demand. Root cause: the cert's shower_outlets field is genuinely unlodged, which the mapper correctly maps to 0 mixer showers per its documented, already-validated "no entry = no shower" convention. Elmhurst's build shows a "Non-electric shower" fixture anyway — its UI silently defaults one when the build script doesn't explicitly configure "0 showers" to match the cert. Verified: a single 7 L/min vented mixer reproduces Elmhurst's (42a) monthly series exactly (4 d.p., all 12 months) and closes hot water to 2616.04 vs Elmhurst's 2616.03. Corpus-wide check across 170 certs sharing this "bath present, no shower data" pattern shows no systematic bias (mean dSAP +0.12, median -0.04) — confirms the mapper convention is correct on average; this is a build-entry artifact on this one cert, not a mapper bug (no code change warranted). Combining all three found causes (window orientation, Table 11, shower default): SAP 72.4567 vs Elmhurst's precise 72.0681 — residual 0.39, ~91% of the original 4.26-point gap now precisely explained. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| addresses | ||
| billing | ||
| data_transformation | ||
| epc | ||
| epc_prediction | ||
| fuel_rates | ||
| magicplan | ||
| modelling | ||
| property | ||
| property_baseline | ||
| sap10_calculator | ||
| tasks | ||
| __init__.py | ||
| test_building_geometry.py | ||
| test_postcode.py | ||