ac68cf88a0
Mirrors S16a for 000516 — the second Simplified-Type-1 fallback fixture in the cohort. PDF lodges detailed §3.10 RR + exposed Main floor + 2 doors; fixture previously lodged only `SapRoomInRoof( floor_area=19.02)` Simplified fallback + `is_exposed_floor=False` + `door_count=1`. Lodgement changes: - `detailed_surfaces` on the Main RR: 7 surfaces per PDF §3 lines (30)/(32) — 1 flat ceiling 3.56 m² uninsulated, 2 stud walls 3.88 m² @ 100mm mineral_wool (Table 17 col 3a → U=0.36), 2 slopes 6.41 m² uninsulated (U=2.30), 2 gable walls 13.11 m² treated as party at U=0.25. - `is_exposed_floor=True` on Main floor=0 (28b "Exposed floor Main 35.76 × U=1.20"). Floor sits over an unheated space, not earth. - `roof_insulation_thickness=0` on Main — PDF (30) "External roof Main 15.56 × U=2.30" UNINSULATED Table 16 "none" row. - `door_count` 1 → 2 to match PDF (26) total area 3.70 m² = 2 × 1.85. Impact on §3 cascade pins: pin | before slice 23 | after slice 23 ----------|-----------------|--------------- LINE_31 | +20.37 m² Δ | +0.0025 m² Δ (sub-display) LINE_33 | -6.75 W/K Δ | -0.82 W/K Δ (rooflight gap, slice 25) LINE_36 | +3.06 W/K Δ | +0.0004 W/K Δ (sub-display) LINE_37 | -6.75 W/K Δ | -0.82 W/K Δ Remaining 0.82 W/K LINE_33 gap is the rooflight: PDF lodges a 1.18 m² roof window on line (27a) at U_eff=2.9930 (Table 24 metal-frame pre-2002 raw 3.4 + curtain). Our §3 cascade doesn't yet incorporate roof windows — they're defined in SECTION_6_ROOF_WINDOWS for solar gains but not in the heat-transmission path. Slice 25 will add (27a) line-ref handling. §3 cascade pin count unchanged at 23 FAIL / 1 PASS — the 000516 residuals dropped 10× but still > abs=1e-4. The downstream §4-§12 cascade for 000516 likely tightens once §3 closes. 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