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
History
Khalim Conn-Kowlessar 1f078af7db §8 slice 2: 6 Elmhurst fixtures conform on (95)..(99) 
Adds LINE_95_M_USEFUL_GAINS_W, LINE_97_M_HEAT_LOSS_RATE_W,
LINE_98A_M_SPACE_HEATING_KWH, LINE_98C_M_TOTAL_SPACE_HEATING_KWH,
LINE_98C_ANNUAL_KWH, LINE_99_PER_M2_KWH to each
_elmhurst_worksheet_*.py fixture, plus an ALL_FIXTURES-parametrised
end-to-end test.

Tolerances vary by line ref per §5's per-line precedent:
  - (95) η × G          → 5e-2 W per month
  - (97) H × ΔT         → 5e-2 W per month
  - (98a)/(98c)         → 1e-1 kWh per month
  - ∑(98c) annual       → 1e-1 kWh
  - (99) per-m²         → 5e-3 kWh

Looser than §6/§7's flat 5e-3 W budget because §8 inputs (LINE_93,
LINE_94, LINE_84) carry 4-d.p. display rounding from upstream worksheets,
and §8's 0.024·31·(L−ηG) amplifies that rounding into the per-month kWh
band. The orchestrator computes in full precision; tolerances reflect
the fixture-pin precision floor, not physics error.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
2026-05-20 22:35:12 +00:00
..
domain §8 slice 2: 6 Elmhurst fixtures conform on (95)..(99) 2026-05-20 22:35:12 +00:00
fetchers added potential file scaffolding: 2026-05-15 10:56:53 +00:00
repos added potential file scaffolding: 2026-05-15 10:56:53 +00:00
utils added potential file scaffolding: 2026-05-15 10:56:53 +00:00
README.md added potential file scaffolding: 2026-05-15 10:56:53 +00:00

README.md

Shared packages

Workspace packages consumed by services/*. Each package is its own Python distribution with its own pyproject.toml; services import via the workspace dependency mechanism ({ workspace = true }).

Package Purpose
domain/ Shared domain types — Property, BaselinePerformance, Plan, Scenario, EpcPropertyData, etc. No persistence, no IO, no business logic.
repos/ Persistence layer — one repo per aggregate. Owns the SQL. Depends on domain.
fetchers/ External API clients (gov EPC, Ofgem, Google Solar, etc.). Depend on domain for response shapes.
utils/ Cross-cutting infra — logging, S3, CloudWatch URL builders, SQS task helpers.

Adding a new shared package

Only when a real second consumer materialises. Don't pre-shatter (repos-epc, repos-property, ...) — split when a deployment needs to drop a dep, not before.

See ../ara_backend_design.md §11 for the broader monorepo layout and ../CONTEXT.md for the domain glossary that names the types living in domain/.