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> |
||
|---|---|---|
| .claude/skills | ||
| .devcontainer | ||
| .github/workflows | ||
| .idea | ||
| .vscode | ||
| applications | ||
| asset_list | ||
| backend | ||
| backlog | ||
| datatypes | ||
| deployment/terraform | ||
| docs | ||
| domain | ||
| epr_data_exports | ||
| etl | ||
| harness | ||
| infrastructure | ||
| model_data/requirements | ||
| orchestration | ||
| recommendations | ||
| repositories | ||
| sap worksheets | ||
| scripts | ||
| sfr/principal_pitch | ||
| survey_report | ||
| tests | ||
| utilities | ||
| utils | ||
| .coveragerc | ||
| .dockerignore | ||
| .gitignore | ||
| __init__.py | ||
| ara_backend_design.md | ||
| BaseUtility.py | ||
| CLAUDE.md | ||
| conftest.py | ||
| CONTEXT.md | ||
| devcontainer.sh | ||
| Dockerfile.test | ||
| Dockerfile.test.dockerignore | ||
| Makefile | ||
| MEMORY.md | ||
| next_claude_prompt.txt | ||
| P960-0001-001431-2.pdf | ||
| package-lock.json | ||
| package.json | ||
| playground.py.local-backup | ||
| pyproject.toml | ||
| pyrightconfig.json | ||
| pytest.ini | ||
| README.md | ||
| run_lambda_local.sh | ||
| serverless.yml | ||
| Summary_001431-3.pdf | ||
| test.requirements.txt | ||
| tox.ini | ||
| UBIQUITOUS_LANGUAGE.md | ||
Model Repository
This repository contains the code pertaining to the development of the data science and machine learning products being utilised by Hestia.
The different folders in this repository relate to services that can be used independently, or can be imported and used as part of a larger application
Getting Started
Prerequisites
Dev Container Setup
This repo uses a Docker Compose-based dev container. The model-backend service joins a shared-dev Docker network so it can communicate with other local services (e.g. a frontend container) running on your machine.
VS Code users: The initializeCommand in devcontainer.json creates the shared-dev network automatically before the container starts. No manual step required — just open the repo and select Reopen in Container.
Non-VS Code / CI workflows: Run the following once before starting the container:
make dev-setup
This is idempotent and safe to re-run if the network already exists.
Folders
backend/
This folder contains the code for the fastapi backend service, which provides an interface to much of the functionality in this repository, for the frontend
model_data/
This folder contains related to the reading and preparation of assessment model data, including pulling out epc attributes
Testing
All tests can be run, against the configuration in pytest.ini running
pytest
This will run the complete panel of tests and report on coverage in the locations specified by the pytest.ini file.
To run tests in a specific service, e.g. inside of model_data, simply run
pytest --cov-config=model_data/.coveragerc --cov=model_data
This will produce the test results and coverage reports