e7177a8bd4
A "No system present: electric heaters assumed" lodging carries SAP Table 4a code 699 (electric room heaters) but RdSAP main_heating_category 1, NOT 10. `_table_12a_system_for_main` keyed the direct-acting-electric routing on category==10 only, so the category-1 form fell through to None and `_space_heating_fuel_cost_gbp_per_kwh` billed space heating 100% at the off-peak LOW rate — as if direct-acting room heaters charged overnight like storage. Per RdSAP 10 §12 Rule 3 (PDF p.62) electric room heaters (691-694, 699) route to the 10-hour tariff, and SAP 10.2 Table 12a Grid 1 (PDF p.191) gives the "other direct-acting electric" row a 0.50 high-rate fraction at 10-hour (1.00 at 7-hour). Route those SAP codes — the same set §12 Rule 3 already uses — to OTHER_DIRECT_ACTING_ELECTRIC alongside the category-10 gate. Found via the PE/CO2-vs-cost split on the worst over-rater in the /tmp sample: cert 2958 PE +0% / CO2 -1% (energy correct) but SAP +32.2 — a pure cost-side bug. Space rate 7.50 -> 11.09 p/kWh; cert 2958 +32.2 -> +14.7. The committed corpus gauge is unchanged (its 3 non-category-10 code-699 certs are all on Single meters -> STANDARD tariff, so this split never applies to them); the win is on the unbiased /tmp population's single worst cert. 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 | ||
| 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 | ||
| 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