mirror of
https://github.com/Hestia-Homes/Model.git
synced 2026-06-08 11:17:27 +00:00
2b1afa7339
Prerequisite for the SAP 10.2 p.186 two-systems-different-parts MIT. When two main systems heat different parts of a dwelling, §14.1 Main Heating2 lodges its OWN "Heat Emitter" + "Main Heating Controls Sap" (simulated case 6: Main 1 radiators / control 2106 serving the living area, Main 2 underfloor / control 2110 serving elsewhere). The extractor + mapper dropped both — `MainHeatingDetail.heat_emitter_type` and `main_heating_control` came through as empty-string sentinels, so the cascade saw system 2 as having no responsiveness (defaulted R=1.0) and no control type. - `MainHeating2` datatype gains `heat_emitter` + `heating_controls_sap`. - The extractor reads them from the §14.1 block. - `_map_elmhurst_main_heating_2` maps them via the same helpers as Main 1 (`_elmhurst_heat_emitter_int` → underfloor-in-screed = emitter 2, Table 4d R=0.75; `_elmhurst_sap_control_code` → 2110, Table 4e type 3), threading the dwelling floor + age band for the underfloor subtype. Empty-string fallback preserved for the legacy DHW-only Main 2 (cert 000565 §14.1 omits emitter/control). No cascade output changes yet — the MIT consumer lands in S0380.205. Full suite 2358 pass + 0 fail. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| domain | ||
| loaders | ||
| schema | ||
| search | ||
| surveys | ||
| __init__.py | ||
| construction_age_band.py | ||
| efficiency.py | ||
| floor.py | ||
| fuel.py | ||
| heating_controls.py | ||
| hotwater.py | ||
| main_heating.py | ||
| property_type_built_form.py | ||
| roof.py | ||
| walls.py | ||
| windows.py | ||