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 960419a901 Cohort residual slice 5: 000477 build_epc lodgement (partial — Table 3c blocker) 
Lodges the missing cert fields on 000477 build_epc to match U985 PDF:
  - sap_windows = SECTION_6_VERTICAL_WINDOWS (was empty)
  - low_energy_fixed_lighting_bulbs_count = 9 (was None)
  - sap_heating.main_heating_details with PCDF index 18118 (was default)
  - sap_heating.secondary_heating_type = 691 (was None)
  - sap_heating.number_baths = 0 (PDF lodges 0 baths; was None → defaulted to "has bath"=True)

`make_sap_heating` accepts a new `number_baths` kwarg to surface that
field — it lives on SapHeating but wasn't exposed before.

Impact: 000477 SAP integer 71 → 66 (PDF 65, Δ +6 → +1); cost £599 →
£707 vs PDF £732 (Δ -22% → -3.5%); useful 9059 → 10067 vs PDF 10111
(matches to <0.5%).

Remaining +1 SAP integer delta is the **Table 3c two-profile combi-
loss override** — not yet implemented. PCDB 18118 (Vaillant ecoTEC
sustain 24) lodges separate_dhw_tests=2 → spec Appendix J §J3 uses
both Profile M (F1, R1) and Profile L (F2, R2) loss factors. Our
override gate (`_pcdb_table_3b_combi_loss_override`) only accepts
separate_dhw_tests==1 → falls back to Table 3a keep-hot time-clock
600 kWh/yr default = 25x overshoot vs the fixture-pinned ~24 kWh/yr.

The same gap blocks 000480 (PCDB 16839 — but actually wait, 16839 is
in 000490 too and that already closes — needs checking), 000487 (PCDB
18119), and 000516 (PCDB 18118).

Test pin `test_elmhurst_000477_end_to_end_sap_score_matches_pdf`
xfail (strict) with rationale pointing at Table 3c. Re-enables when
the override implements.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
2026-05-22 12:04:24 +00:00
..
domain Cohort residual slice 5: 000477 build_epc lodgement (partial — Table 3c blocker) 2026-05-22 12:04:24 +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/.