ci: fix Gitea runner setup and tighten docs
ci / check (push) Successful in 1m12s

Replace setup-python with setup-uv: the self-hosted Gitea runner lacks the
toolcache and lsb_release dependency, so the job failed before any project
step. uv installs its own Python 3.12; the checks are unchanged.

Align the README and docs with the committed artifacts: quick start serves
from baked artifacts, rebuild steps are separate, and the reference-model
comparison no longer overstates the result. Drop stale external-doc
references and comments that restated the code.
This commit is contained in:
Noel Sabia committed 2026-11-14 09:10:47 +01:00
1 parent 9c7f77f66b
commit 070ecd2a78
13 files changed
+81 -75

No files matched your search

+3 -5
View File
@@ -1,10 +1,8 @@
# Small model — busy-hour classifier
This is the small, fast, explainable model that powers the "train new data"
demo and the "I coded an AI" artifact. It is deliberately separate from the
production 7-day forecaster: six cheap features, a linear model, a time-based
split, and under a second of fitting. It is not the model behind the dashboard
forecast.
A logistic regression that labels an hour `busy` when footfall exceeds that
sensor's p75. It powers the `model=small` retraining demo, not the dashboard
forecast: six cheap features, a time-based split, and under a second to fit.
Every number below comes from the baked artifact
`artifacts/small_metrics.json` (version `logit-20261114-052723`, trained