8520a52ee9
Fixed a single-character spec adherence bug: SAP10.2 Table 3c (p.162)
specifies the M+L profile's DVF lower bound as `V_d,m < 100.2`, not
`< 100.0`. The 0.2 L/day window matters when V_d,m sits between 100.0
and 100.2 — exactly where 000477's May lodgement lands (100.16 L/day).
For V_d,m = 100.16:
Spec: DVF = 0 → (61) = E × r1 × fu = 134.84 × 0.015 × 1.0 = 2.0225 ✓
Buggy: DVF = 100.2 - 100.16 = 0.04 → (61) = 2.0233 (off by 0.0008)
The cascade through the missing 0.0008 W on May LINE_61 propagated to
LINE_62/64/65 and then §5 LINE_72/73 + §6 LINE_84 — clearing one
constant unblocks the entire 000477 §4-§6 cluster.
Per-fixture cluster status (was/now):
§3 24/24 → 24/24
§4 46/54 → 53/54 (only 000487 LINE_65 remains)
§5 50/54 → 52/54 (only 000487 LINE_72/73)
§6 10/12 → 11/12 (only 000487 LINE_84)
All remaining cascade failures cluster on 000487 (slice 25d — derive
LINE_64A electric-shower kWh from cert per Appendix J step 8) plus §7
LINE_92/93 marginal residuals on 4 fixtures (precision artefact).
Scoreboard:
section_cascade_pins: 286 → 293 PASS (+7)
e2e SapResult: 32 → 32 PASS (still cascade-blocked by 000487
LINE_65 + downstream §8-§12 pins not yet asserted)
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