015144361a
§3 cascade pins now close at abs=1e-4 for all 6 fixtures (was 5 of 6 with
000487 the holdout). Five spec-grounded changes:
1. SapRoomInRoofSurface gains optional `u_value` override + new kind
`gable_wall_external` per RdSAP10 Table 4 (p.22) row 1 (exposed gable,
U "as common wall" with assessor-lodged override). Routes to (29a)
walls + LINE_31 external area.
2. SapAlternativeWall gains optional `u_value` override — assessor-lodged
measured U bypasses the Table 6 cascade. 000487 Ext1 has a 9-mm
TimberWallOneLayer at U=1.90 outside the Table 6 buckets.
3. _part_geometry uses MAX of floor areas (not top) for roof area, per
RdSAP10 §3.8 (p.20): "Roof area is the greatest of the floor areas
on each level". Fixes 000487 Ext1 where ground=7.13 m² > first=5.63.
4. Replace Python `round()` (banker's) with `_round_half_up` for §15
element-area rounding. Banker's rounds 17.125 → 17.12; SAP convention
rounds half-up → 17.13. Boundary case appears in 000487 Ext1 party
wall area (party_length 6.25 × height 2.74 = 17.125).
5. 000487 fixture lodges 5 detailed RR surfaces (party gable, external
gable @ U=0.86, flat ceiling, stud wall, slope), roof_insulation_
thickness=300 (both parts → U=0.14), is_exposed_floor=True on Ext1
floor 0, and u_value=1.90 on the Ext1 alt wall.
§3 cascade per-fixture:
field | 474 | 477 | 480 | 487 | 490 | 516
LINE_31 | ✓ | ✓ | ✓ | ✓ | ✓ | ✓
LINE_33 | ✓ | ✓ | ✓ | ✓ | ✓ | ✓
LINE_36 | ✓ | ✓ | ✓ | ✓ | ✓ | ✓
LINE_37 | ✓ | ✓ | ✓ | ✓ | ✓ | ✓
Scoreboard:
section_cascade_pins: 274 → 279 PASS (+5: §3 +4 for 000487, §7 +1
cascade)
e2e SapResult: 32 → 32 PASS (unchanged — downstream §8-§12
pins not yet asserted)
§4 (000487) deferred to slice 25b — needs has_electric_shower routing
through the §4 cascade so Nbath uses the "0.13N+0.19" branch when only
electric showers are present.
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