760e25dea9
Closes the dominant ~92% of the 000474 HW kWh +14.4% residual that the post-§10a Table 32 cost-side fix exposed (pre-§10a wrong prices had been masking it). 000474 HW fuel kWh tightens 2622 → 2320 (+1.2% over PDF 2292); remaining +1.2% closes when slice 2 (Eq D1 monthly cascade) lands. 000490 unaffected — PCDB 10328 lodges separate_dhw_ tests=0 (no Table 3b/3c data), falls through to existing Table 3a default. - tables/pcdb/parser.py: GasOilBoilerRecord gains 7 typed fields per BRE PCDF Spec v1.0 §7.11 — subsidiary_type (field 16), store_type (field 39), separate_dhw_tests (field 48), rejected_energy_ proportion_r1 (field 51), loss_factor_f1_kwh_per_day (field 52), loss_factor_f2_kwh_per_day (field 56), rejected_factor_f3_per_ litre (field 57). Field positions cross-verified against PDF Σ(61) = 337.27 vs 000474 worksheet pin 337.19 (Δ 0.02%). - worksheet/water_heating.py: combi_loss_monthly_kwh_table_3b_row_1_ instantaneous(r1, F1, energy_content (45)m, daily HW (44)m) — SAP10.2 Appendix J Table 3b row 1 formula (61)m = (45)m × r1 × fu + F1 × n_m. Other Table 3b rows (storage variants) and Table 3c (two-profile) deferred until a fixture exercises. - rdsap/cert_to_inputs.py: _pcdb_table_3b_combi_loss_override builds the (61)m override from the PCDB record when separate_dhw_tests=1 + subsidiary=0 + store_type=0 (instantaneous non-storage path). _hot_water_fuel_kwh_per_yr threaded with pcdb_record kwarg; calls water_heating_from_cert with the override when present. - docs/sap-spec/pcdb_table_105_gas_oil_boilers.jsonl: regenerated via the ETL to surface the new typed fields alongside the existing efficiency columns. 484 tests passing (was 479). e2e ceilings hold: 000474 SAP delta 4 → 3 (within current ceiling of 4 — will tighten further after slice 2 Eq D1 cascade lands). Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> |
||
|---|---|---|
| .devcontainer | ||
| .github/workflows | ||
| .idea | ||
| .vscode | ||
| asset_list | ||
| backend | ||
| backlog | ||
| datatypes | ||
| docs | ||
| epr_data_exports | ||
| etl | ||
| infrastructure/terraform | ||
| model_data/requirements | ||
| packages | ||
| recommendations | ||
| scripts | ||
| services | ||
| sfr/principal_pitch | ||
| survey_report | ||
| utils | ||
| .coveragerc | ||
| .dockerignore | ||
| .gitignore | ||
| __init__.py | ||
| AGENTS.md | ||
| 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_backlog.sh | ||
| 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