mirror of https://github.com/Hestia-Homes/Model.git synced 2026-06-08 11:17:27 +00:00

History

Khalim Conn-Kowlessar 8cfeba8e2a Slice 35: Plumb postcode climate through cert_to_inputs (demand cascade) Adds an optional `postcode_climate: Optional[PostcodeClimate]` parameter to every cert→inputs section helper that touches climate: - `cert_to_inputs(epc, postcode_climate=...)` - `ventilation_from_cert` (overrides UK-avg wind tuple) - `mean_internal_temperature_section_from_cert` - `space_heating_section_from_cert` - `space_cooling_section_from_cert` - `solar_gains_section_from_cert` - `energy_requirements_section_from_cert` - `fuel_cost_section_from_cert` - `environmental_section_from_cert` `_climate_source(postcode_climate)` returns `int \| PostcodeClimate` (region 0 = UK-avg fallback). The four Appendix U lookup functions (`external_temperature_c`, `wind_speed_m_per_s`, `horizontal_solar_ irradiance_w_per_m2`, `_latitude_deg`) now accept the union and dispatch on isinstance — region path is unchanged, postcode path reads directly from `PostcodeClimate`. CalculatorInputs gains `monthly_external_temp_c_override` so the calculator's per-month solve uses the postcode tuple computed in cert_to_inputs instead of looking up `external_temperature_c(region, m)` (which would always be UK-avg). Adds two public helpers: - `local_climate_for_cert(epc)` — postcode lookup with None fallback - `cert_to_demand_inputs(epc)` — convenience: cert_to_inputs with postcode climate from the cert's postcode field Verification (000474 with postcode "bd3 8aq" injected — fixtures currently lodge placeholder "A1 1AA"; real postcodes land in slice 36): Rating main_1_fuel = 11964.8924 (PDF Block 1: 11964.8924 ✓) Demand main_1_fuel = 12288.0014 (PDF Block 2: 12288.0014 ✓ EXACT) Rating ext_temp Jan = 4.3°C (UK-avg) Demand ext_temp Jan = 4.2°C (BD3) 840/840 existing pins still pass — refactor is backward-compatible. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>		2026-05-24 09:40:03 +00:00
..
src/domain	Slice 35: Plumb postcode climate through cert_to_inputs (demand cascade)	2026-05-24 09:40:03 +00:00
pyproject.toml	slice 13: to_rows(properties) returns pd.DataFrame	2026-05-16 16:43:28 +00:00
README.md	added potential file scaffolding:	2026-05-15 10:56:53 +00:00

README.md

domna-domain

Shared domain types — Property, Properties, BaselinePerformance, Plan, PlanPhase, Scenario, ScenarioPhase, ScenarioSnapshot, Recommendation, OptimisedPackage, EpcPropertyData, etc.

Boundary: types only. No persistence, no IO, no business logic. Other packages and services depend on domna-domain; this package depends on nothing internal.

Domain definitions live in ../../CONTEXT.md. New types added here must match the glossary terms.

Layout

src/domain/
├── __init__.py
├── property.py             # Property, Properties, PropertyIdentity
├── site_notes.py
├── landlord_overrides.py
├── baseline_performance.py # lodged + effective pair (ADR-0004)
├── plan.py                 # Plan, PlanPhase, OptimisedPackage
├── scenario.py             # Scenario, ScenarioPhase, ScenarioSnapshot (ADR-0005)
├── recommendation.py
├── geospatial.py
├── solar.py
├── anomaly_flags.py
└── ml/
    ├── __init__.py
    ├── transform.py        # EpcMlTransform (versioned per §8.3)
    └── schema.py

When datatypes/epc/domain/ folds in, the EPC schema types move under src/domain/epc/.