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 f81e744b02 §5 slice 9: internal_gains_from_cert orchestrator + lookalike tracer test 
Wires all §5 leaf functions into a single from_cert orchestrator that
chains (66) → (67) → (68) → (69) → (70) → (71) → (72) → (73) and
returns an InternalGainsResult. The caller provides §4 (65)m heat
gains (the only non-cert input) and overshading defaults to AVERAGE.

Cert derivations:
  - Occupancy via Appendix J Table 1b from TFA
  - Lighting: RdSAP §12-1 per-lamp-type bulb defaults aggregated to
    C_L,fixed + ε_fixed; C_daylight via L2a from sap_windows × Z_L
    from Table 6d. L5b + L8c fallbacks when no bulb/window data lodged.
  - Pumps/fans: maps central_heating_pump_age_str on the first
    MainHeatingDetail to PumpDateCategory. Liquid-fuel / warm-air / PIV
    / MV / HIU branches deferred (reachable via leaf fns; currently
    return 0 in the orchestrator for the combi-gas-natural-vent
    population that covers all 6 Elmhurst fixtures).

Slice 9 tracer test hand-builds a 000490-lookalike EPC rather than
mutating `_elmhurst_worksheet_000490.build_epc()` — keeps the existing
e2e SAP-score regression test pinned. Slice 10 will extend the fixture
proper and parametrize over ALL_FIXTURES.

Also: extends make_minimal_sap10_epc with low_energy_fixed_lighting_bulbs_count
since the existing builder only exposed CFL/LED/incandescent separately.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
2026-05-20 18:50:40 +00:00
..
src/domain §5 slice 9: internal_gains_from_cert orchestrator + lookalike tracer test 2026-05-20 18:50:40 +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/.