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 dad7fbf31f §4 slice 3: hot_water_baths_monthly_l_per_day (line (42b)m) 
Appendix J equations J6, J7, J8. Daily hot water for bath fills depends
on N, presence of bath and/or shower, and monthly Tcold:

  N_bath  = 0                if no bath but a shower exists
          = 0.13×N + 0.19    if bath + shower
          = 0.35×N + 0.50    otherwise
  V_d,bath[m] = N_bath × 73 × J5_fbeh[m] × (42−Tcold[m])/(52−Tcold[m])

Tables J1 (mains + header tank Tcold) and J5 (behavioural factor) are
exported as module constants for reuse by (42a)m showers next.

Validated against the Elmhurst non-RR fixtures, both with bath + shower
and "Cold Water Source: From mains":
  - 000490 N=2.1468 → Jan V_d,bath = 27.3868
  - 000474 N=1.8896 → Jan V_d,bath = 25.4345

Also covers the zero-bath branch and the 5% low-water-use reduction.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
2026-05-20 15:48:26 +00:00
..
domain §4 slice 3: hot_water_baths_monthly_l_per_day (line (42b)m) 2026-05-20 15:48:26 +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/.