a21d2cc579
Closes #1684. `_main_2_space_heating_fuel_cost_gbp_per_kwh` billed an electric Main 2 at Main 1's space-heating rate. That was a no-op on a homogeneous off-peak cohort (storage+storage, direct+direct → equal rates) but mis-billed the HETEROGENEOUS case: an off-peak STORAGE Main 1 (5.5 p/kWh low) + an on-peak DIRECT-ACTING panel Main 2 (15.29 p/kWh high) rode the storage low rate, under-costing the panel half and over-rating SAP. Flip it to bill Main 2 at its OWN Table 12a Grid 1 SH row, the same per-system resolution Main 1 and a non-electric Main 2 already use — and the same one `_main_2_high_rate_fraction` already applies, so the scalar cost and the high-rate split are now consistent. The docstring's "regresses certs 13/34 (Parkers Hill / Dunley Road)" warning was stale: those names appear nowhere but that docstring, and the full guard suite shows zero new regressions (only the two pre-existing `test_heating_systems_corpus` fails on main). LRHA WAVE 3 fixture 497655371974 (storage+panel) moves +15.3 → -2.5 vs PasHub; cohort MAE 0.799 → 0.675 (ratchet re-baselined 0.80 → 0.68). within-0.5 holds at 55.3% — the -2.5 residual is PasHub-vs-Elmhurst divergence, not a bug, so the fixture stays out of the within-0.5 pin. A ground-truth Elmhurst pin is queued (see docs/HANDOVER_1684_ELMHURST_INPUTS_497655371974.md). 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 | ||
| modelling_audit.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