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 bfba610b70 §4 slice 7: combi loss (Table 3a time clock) + (62)m total demand 
Two new public functions:

  combi_loss_monthly_kwh_table_3a_keep_hot_time_clock()
    Table 3a row "Instantaneous, with keep-hot facility controlled by
    time clock" → 600 × n_m / 365 kWh/month (flat 600 kWh/year prorated
    by month length, no fu adjustment).

  total_water_heating_demand_monthly_kwh(...)
    Spec formula (62)m = 0.85 × (45)m + (46)m + (57)m + (59)m + (61)m.
    (56)m storage loss is intentionally absent — folded into storage-
    system efficiency at the (64)m stage. (46)m distribution loss
    appears here AND in (65)m heat gains (weight 0.8), per spec.

000490 close end-to-end through (62)m: combi with time-clock keep-hot,
no storage, no solar, no primary loss → Jan = 0.85×187.86 + 28.18 + 0 +
0 + 50.96 = 238.82 matching the worksheet to 1e-3.

000474 deferred: its PCDF-listed Vaillant boiler uses Table 3b (tested
to EN 13203-2) which needs PCDB-backed r1 + F1 parameters. The (61)m
implementation for that branch lands in a future slice along with the
PCDB stub plumbing.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
2026-05-20 16:06:05 +00:00
..
domain §4 slice 7: combi loss (Table 3a time clock) + (62)m total demand 2026-05-20 16:06:05 +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/.