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 99e5c2cd44 §5 slice 10: extract LINE_66..LINE_73 + ALL_FIXTURES e2e conformance 
Adds SECTION_5_BULB_COUNT_LEL, SECTION_5_WINDOW_AREAS_M2,
SECTION_5_PUMP_AGE_STR and LINE_66..LINE_73 expected outputs to every
Elmhurst fixture (000474, 000477, 000480, 000487, 000490, 000516).
Constants extracted from the U985-0001-NNNNNN worksheets supplied
2026-05-20. All six fixtures share the same shape: all-LEL bulb
lighting, gas combi pump with unknown install date, average overshading.

Adds an ALL_FIXTURES-parametrized test in test_internal_gains.py that
composes a §5 EPC from the fixture's constants and drives
internal_gains_from_cert. Tolerances: ≤1e-3 W on the linear-in-N rows
(66/69/71), ≤2e-1 W on (67) lighting (worksheet-rounded N + rooflight
Z_L=1.0 approximated by AVERAGE Z_L=0.83), ≤5e-2 W on (68) appliances,
≤3e-1 W on (73) sum. Result: 26 tests pass; six fixtures conform to
≤0.6% lighting bias end-to-end.

The fixture's base build_epc() is unchanged — §5 EPC composition lives
in a test helper so the existing e2e SAP-score regression (000490, 000474)
remains pinned for the upcoming calc.py wiring slice.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
2026-05-20 19:06:34 +00:00
..
domain §5 slice 10: extract LINE_66..LINE_73 + ALL_FIXTURES e2e conformance 2026-05-20 19:06:34 +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/.