0f79de7a35
A gov-API flat can lodge dwelling_type="Mid-floor flat" while carrying its own exposed roof — a top-floor flat mislabelled mid-floor. _dwelling_exposure keyed roof exposure on the dwelling_type label alone, dropping the roof heat-loss term: space-heating demand under-read ~32%, SAP over-read +7. Fix: when the main building part lodges a *determined* roof_insulation_location (an RdSAP integer code, not the "ND" Not-Defined party-ceiling sentinel), expose the roof regardless of a contradictory label. Structured field, not a description string and not roof_construction (which the gov-API lodges building-wide on every unit, so it is not a per-unit signal). On the RdSAP-21.0.1 corpus roof_insulation_location separates the classes with zero disagreement: all 190 party-ceiling flats lodge "ND"; the 4 mid/ground flats this exposes all move toward lodged, 0 away. within-0.5 73.3% -> 73.6%, MAE 0.774 -> 0.761 (ratchets tightened). Verified end-to-end on the same block: 715363 (location 6, RHI 2694) 81 -> 74 = lodged; genuine mid-floor sibling 715395 (location ND, RHI 1024) stays party at 83 = lodged. The override is additive (only ever exposes a label-dropped roof) and reads the main part, so multi-part flats with a party main ceiling stay party. 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