mirror of
https://github.com/Hestia-Homes/Model.git
synced 2026-07-12 13:29:04 +00:00
34cbd7d66c
MVHR (24a) heat-recovery support, part 1: the PCDB data layer. PCDB Table 323 (PCDF Spec Rev 6b §A.18, Format 426; pcdb10.dat carries Format 431, header `$323,431,...`) holds the per-wet-room SFP + heat- exchanger efficiency for centralised MEV / MVHR units. Added `MvhrRecord` / `MvhrDataPoint`, `parse_centralised_mv_row` / `parse_table_323`, the ETL step, the committed jsonl, and the `mvhr_record(pcdb_id)` runtime lookup (mirrors Table 322). SAP 10.2 §2.6.4/§2.6.6: "MVHR ... SFP is a single value depending on the number of wet rooms" — each test group's leading field is the wet-room count; callers select the group matching the dwelling lodgement. Worksheet-proven on simulated case 49 (000565, 2 wet rooms, Vent Axia Sentinel Kinetic B 500140 → flow 21.0, SFP 0.88, efficiency 91%). Also decoded the MVHR heat-recovery efficiency in-use factor from Table 329 (Format 432): system_type 3 ducts-inside-envelope = 0.90 (case-49 (23c) = 91 × 0.90 = 81.9%), cross-checked against system_type 10 = 0.70 (= SAP 10.2 Table 4g default heat-recovery in-use factor). "Table 4h is no longer used – data now stored in the PCDB" (SAP 10.2 p.176). The outside-envelope efficiency columns + with-scheme SFP blocks are preserved verbatim in `raw` (no fixture exercises them yet). Note: pyright strict type gate not run locally (pyright not installed). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| addresses | ||
| billing | ||
| data_transformation | ||
| epc | ||
| epc_prediction | ||
| fuel_rates | ||
| geospatial | ||
| magicplan | ||
| modelling | ||
| property | ||
| property_baseline | ||
| sap10_calculator | ||
| sap10_ml | ||
| tasks | ||
| building_geometry.py | ||
| postcode.py | ||