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:
1 parent
9c7f77f66b
commit
070ecd2a78
13 files changed
+81
-75
No files matched your search
+5
-4
@@ -68,10 +68,11 @@ a headline accuracy claim.
|
||||
|
||||
The seasonal-naive row reproduces the mission reference exactly
|
||||
(5.40 / 44.7% / 0.462), and the day-ahead weather row matches 3.36 / 27.8%. The
|
||||
production model is slightly better than the reference because `lag_week` uses
|
||||
the previous *observed* same weekday/hour across sensor gaps, while the baseline
|
||||
uses the exact 168-row lag. R² differs slightly from the reference 0.779
|
||||
(0.777 here) because of that feature choice.
|
||||
production 7-day model edges that day-ahead reference on MAE and WAPE
|
||||
(3.32 / 27.5%) but is slightly lower on R² (0.777 vs 0.779). The two use
|
||||
different features; `lag_week` uses the previous *observed* same weekday/hour
|
||||
across sensor gaps, while the seasonal-naive baseline uses the exact 168-row
|
||||
lag.
|
||||
|
||||
Per-sensor holdout MAE improves over each sensor's own seasonal naive by
|
||||
27.7%–43.9%; the full table, figures, and provenance are in
|
||||
|
||||
Reference in new issue
Block a user