63dd69ff8b
Extend the gas-boiler-upgrade Option to combi (no-cylinder) dwellings and add the controls upgrade shared by both boiler shapes. A dwelling has a cylinder or it does not, so the one `gas_boiler_upgrade` Option is shaped per dwelling: - no cylinder -> a gas condensing combi (Table 4b code 104), no cylinder fields touched; - a cylinder -> a regular boiler (code 102) heating it, with the conditional cylinder jacket/thermostat (slice 1). Controls: bring an inadequate boiler control up to full programmer + room thermostat + TRVs (SAP 10.2 Table 4e Group 1 code 2106). "Inadequate" = the Group-1 codes with NO room thermostat (2101, 2102, 2107, 2108, 2109, 2111) — these lack boiler interlock (Table 4c(2) / footnote c) p.171), so adding a room thermostat genuinely improves SAP. Room-thermostatted (2103/2104/2105/2106/2113) or better zone controls (2110/2112) are left unchanged — never downgraded, so no phantom uplift. The with-cylinder cert (control 2106) is therefore untouched and its pin still holds at delta 0. Validated by the combi before/after re-lodgement (cert 001431, gas boiler upgrade - no cylinder): control 2111 "TRVs and bypass" -> 2106, fan flue False->True, SAP code 112 -> 104. Cascade-pinned delta 0 (SAP/CO2/PE). Removed the slice-1 placeholder test asserting no boiler Option fires without a cylinder (the combi Option now correctly fires there). 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 | ||
| 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