Follow-up to the §2 MV-kind slice. Once MEV dwellings stopped under-stating their ventilation HEAT loss, a +0.9 SAP over-rate residual remained — the MEV FAN ELECTRICITY (§5 Table 4f line (230a), `SFPav × 1.22 × V`, PCDB Tables 322 decentralised-MEV + 329 in-use factors). `_mev_decentralised_kwh_per_yr_from_cert` already composes it, but reads `epc.mechanical_ventilation_index_number` + `epc.mechanical_vent_duct_type`, and the API builder (`from_rdsap_schema_21_0_1`) never set either — so `pcdf_id is None` short-circuited the fan energy to 0 on every API cert (the Summary/ Elmhurst path set them, so cert 000565 already billed it). Wire both schema fields through the 21.0.1 API construction (the corpus schema). Eval: the 9 MEV certs carrying a PCDB index closed +0.90 -> +0.13 signed (fan electricity now billed); headline within-0.5 55.01% -> 55.12%, mean|err| 1.233 -> 1.232, 909 computed / 0 raises. Only those 9 certs move (clean diff). The 11 index-less MEV certs still sit at +1.36 — they need the SAP Table 4h DEFAULT specific fan power (no PCDB record), a separate slice. New end-to-end test + fixture (cert 1300, Titon-class dMEV index 500777, Flexible duct): from_api_response preserves the index + duct type and (230a) resolves to a positive fan-energy contribution. Goldens + full calc/epc regression green; pyright net-zero. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> |
||
|---|---|---|
| .devcontainer | ||
| .github/workflows | ||
| .idea | ||
| .vscode | ||
| applications | ||
| asset_list | ||
| backend | ||
| backlog | ||
| datatypes | ||
| deployment/terraform | ||
| docs | ||
| domain | ||
| epr_data_exports | ||
| etl | ||
| 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 | ||
| package-lock.json | ||
| package.json | ||
| pyproject.toml | ||
| pyrightconfig.json | ||
| pytest.ini | ||
| README.md | ||
| run_lambda_local.sh | ||
| serverless.yml | ||
| 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