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 f77229e4b4 §5 slice 7: (70) pumps_fans_monthly_w — Table 5a 9-row dispatch 
Implements Table 5a row-by-row leaf functions:
  central_heating_pump_w     pump install-date bucket (3/7/10 W)
  liquid_fuel_boiler_pump_w  10 W when oil-fuel pump inside dwelling
  liquid_fuel_warm_air_pump_w  10 W for liquid-fuel warm-air systems
  warm_air_heating_fan_w     SFP × 0.04 × V (heating-season)
  piv_fan_w                  IUF × SFP × 0.12 × V (year-round)
  balanced_mv_no_hr_fan_w    IUF × SFP × 0.06 × V (year-round)
  heat_interface_unit_w      PCDB kWh/day × 1000 / 24 (year-round)

Plus pumps_fans_monthly_w(heating_season_w, year_round_w) which applies
the Table 5a footnote-a seasonal mask (Jun-Sep = 0 W heating-season
contribution per Elmhurst worksheet convention).

PumpDateCategory enum maps from EpcPropertyData.central_heating_pump_age_str
("Pre 2013" / "Post 2013" / "Unknown" / etc.) at the orchestrator layer.

MVHR and MEV systems intentionally have no leaf fn — gains are zero per
Table 5a notes (MVHR effect is in MVHR efficiency; MEV simply omitted).

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
2026-05-20 18:37:14 +00:00
..
domain §5 slice 7: (70) pumps_fans_monthly_w — Table 5a 9-row dispatch 2026-05-20 18:37:14 +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/.