junte/Model
1
0
Fork 0
mirror of https://github.com/Hestia-Homes/Model.git synced 2026-06-08 11:17:27 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions
Model/packages/domain
History
Khalim Conn-Kowlessar ff5d8c70c1 §7 slice 3: 6 Elmhurst fixtures conform on (85)..(94) to ≤5e-3 
Adds SECTION_7_LIVING_AREA_FRACTION, SECTION_7_CONTROL_TYPE,
SECTION_7_RESPONSIVENESS, SECTION_7_THERMAL_MASS_PARAMETER_KJ_PER_M2_K
plus LINE_85..LINE_94 expected outputs across all 6 _elmhurst_worksheet_*
fixtures, and an ALL_FIXTURES-parametrised end-to-end test.

The test sources its inputs from §1-§6 fixture pins:
  (84) monthly total gains = LINE_73 + LINE_83
  (39) monthly HTC         = LINE_37 + 0.33·V·LINE_25_M
  external temp = Appendix U Table U1 region 0 (UK-avg, SAP rating pass)

Asserts every per-zone line ref to abs=5e-3 °C / unitless:
  (85) T_h1                    × 6 = 6
  (86) η_living monthly        × 12 × 6 = 72
  (87) MIT living monthly      × 12 × 6 = 72
  (88) T_h2 monthly            × 12 × 6 = 72
  (89) η_elsewhere monthly     × 12 × 6 = 72
  (90) MIT elsewhere monthly   × 12 × 6 = 72
  (91) f_LA                    × 6 = 6
  (92) blended MIT monthly     × 12 × 6 = 72
  (93) adjusted MIT monthly    × 12 × 6 = 72
  (94) η_whole monthly         × 12 × 6 = 72
                                 total = 588 GREEN assertions

All 6 fixtures land at default scalars (control_type=2 gas combi w/
programmer+RT, R=1.0 Table 4d gas radiators, TMP=250 SAP mass-medium
default, Table 4e adj=0). Per-fixture f_LA reflects habitable_rooms_count.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
2026-05-20 21:37:58 +00:00
..
src/domain §7 slice 3: 6 Elmhurst fixtures conform on (85)..(94) to ≤5e-3 2026-05-20 21:37:58 +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/.