docs(mission): add weather and holiday context
release-please / release-please (push) Failing after 3s
release-please / release-please (push) Failing after 3s
This commit is contained in:
1 parent
8afb767585
commit
1ff3bc8290
8 files changed
+109
-25
No files matched your search
+10
-6
@@ -21,10 +21,10 @@ If those six are clear, it is halfway good. Novelty is a bonus, not a requiremen
|
||||
|---|---:|---|
|
||||
| Abstract | 150–200 words | Problem, data, method, headline result, deployment. |
|
||||
| 1. Introduction | 0.5 page | The decision gap; why a dashboard is not enough; three contributions. |
|
||||
| 2. Data | 0.75 page | PAX counters, 8 sensors, 5 months, 15 min, 580 m, coverage/gaps, device-penetration bias, privacy. |
|
||||
| 3. Method | 1 page | Preprocessing, features, global HistGB, weather fusion, horizons, time-based split, staffing heuristic. |
|
||||
| 2. Data | 0.75 page | PAX counters, 8 sensors, 5 months, 15 min, 580 m, coverage/gaps, device-penetration bias, privacy, Open-Meteo weather, Baden-Württemberg holidays. |
|
||||
| 3. Method | 1 page | Preprocessing, features (time, lags, weather, holiday), global HistGB, horizons, time-based split, staffing heuristic. |
|
||||
| 4. System | 0.75 page | Nuxt SSR, Go API/SSE, FastAPI, Cloudflare Tunnel, SKE namespace-only, build-time batch, cached fallback. |
|
||||
| 5. Evaluation | 1 page | Baseline comparison, weather ablation, per-sensor errors, plan latency, 120-client load test. |
|
||||
| 5. Evaluation | 1 page | Baseline comparison, weather ablation, holiday effect, per-sensor errors, plan latency, 120-client load test. |
|
||||
| 6. Discussion & limitations | 0.5 page | 8 sensors, 5 months, observed weather, no POS/labor data, single replica, no auth. |
|
||||
| 7. Related work | 0.25 page | PAX counters/privacy, pedestrian forecasting, gradient boosting, smart-city dashboards. |
|
||||
| 8. Conclusion & future work | 0.25 page | More sensors, POS/event data, multi-store, city operations. |
|
||||
@@ -36,7 +36,7 @@ If those six are clear, it is halfway good. Novelty is a bonus, not a requiremen
|
||||
|
||||
1. Sensor map of the 580 m cluster (8 points; label the sensor names).
|
||||
2. Hourly and weekday footfall profile (the "pulse").
|
||||
3. Forecast vs actual for one sensor over the 28-day test (with uncertainty band).
|
||||
3. Forecast vs actual for one sensor over the 28-day test (with uncertainty band), with weather/holiday context markers.
|
||||
4. Architecture diagram (three services + Cloudflare Tunnel + SKE).
|
||||
5. The staffing plan screen (or a table if the screenshot is weak).
|
||||
|
||||
@@ -44,7 +44,7 @@ If those six are clear, it is halfway good. Novelty is a bonus, not a requiremen
|
||||
|
||||
1. Data coverage per sensor: readings, mean, p95, max, max gap.
|
||||
2. Model comparison: seasonal naive vs no-weather vs weather, MAE/WAPE/R².
|
||||
3. Ablation: weather on/off; per-sensor MAE.
|
||||
3. Ablation: weather on/off, holiday on/off; per-sensor MAE.
|
||||
4. System metrics: plan generation latency, 120 SSE clients, image sizes, deployment time.
|
||||
|
||||
## Facts and numbers to use (do not invent)
|
||||
@@ -61,6 +61,8 @@ If those six are clear, it is halfway good. Novelty is a bonus, not a requiremen
|
||||
- **With temperature/rain:** MAE **3.36**, WAPE **27.8%**, R² **0.779**.
|
||||
- **7-day:** MAE 4.37, WAPE 36.2%, R² 0.672.
|
||||
- **Caveat:** weather is observed, not forecast; no event data; 4-week test; values are device estimates, not people.
|
||||
- **Weather:** Open-Meteo historical archive for training; forecast API for the dashboard. Temp/rain are the useful features; cloud/wind did not improve the short test.
|
||||
- **Holidays:** German/Baden-Württemberg public holidays 2025–2026; `is_holiday` feature + dashboard badges. The holiday-only feature added little in the 28-day test (4.15 vs 4.20 without weather; 3.44 vs 3.36 with weather). Report honestly.
|
||||
- **System:** 3 Deployments + `cloudflared`; no Ingress, no cert-manager, no Jobs; build-time batch; Cloudflare Tunnel; SSE + polling fallback; Go cache; plan < 2 s.
|
||||
- **Load test:** fill in after k6; do not claim a number you did not measure.
|
||||
|
||||
@@ -82,6 +84,7 @@ Facts:
|
||||
- 8-sensor window 2026-06-12 to 2026-11-07; ~15-min cadence; 580 m cluster.
|
||||
- Values are estimated devices, not people; device penetration unknown.
|
||||
- Peak 18:00–21:00 local; Saturday busiest.
|
||||
- Weather from Open-Meteo; German/Baden-Württemberg holidays as context features.
|
||||
- Global HistGradientBoostingRegressor; time-based holdout of 28 days.
|
||||
- Seasonal naive: MAE 5.40, WAPE 44.7%, R2 0.462.
|
||||
- No weather: MAE 4.20, WAPE 34.8%, R2 0.678.
|
||||
@@ -106,7 +109,8 @@ real sources you are confident exist; otherwise write "[CITATION TODO]".
|
||||
|
||||
- [ ] Every number matches `mission/data.md` or a measured result.
|
||||
- [ ] The baseline table is present; the model is compared to seasonal naive, not only to itself.
|
||||
- [ ] Weather is described as observed, not forecast.
|
||||
- [ ] Weather is described as observed for training, forecast/current for the dashboard.
|
||||
- [ ] Holidays are described as context/feature, not as a large accuracy lift.
|
||||
- [ ] The 8-sensor/5-month/580 m limitation is explicit.
|
||||
- [ ] "Devices, not people" appears at least once.
|
||||
- [ ] No claim of live sensor data; replay/nowcast is labeled.
|
||||
|
||||
Reference in new issue
Block a user