feat(forecasting): seasonal demand normalization module (#979) #1039
No reviewers
Labels
No labels
admin
analytics
auth
automation
bug
business
chore
ci
compliance
data
data-moat
docs
duplicate
dx
enhancement
Fable 5 ревью
feedback/max
generative
GG-форсайт
needs-discussion
needs-human
observability
pause-bots
performance
priority/p0
priority/p1
priority/p2
priority/p3
scope/backend
scope/db
scope/devops
scope/frontend
scope/qa
scrapers
security
site-finder
stage/1
stage/2
status/blocked
status/done
status/needs-analysis
status/needs-fix
status/qa
status/ready
status/review
status/wip
tech-debt
tradein
ux
week ревью 1
wontfix
вторичка
ИРД
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: lekss361/gendesign#1039
Loading…
Add table
Reference in a new issue
No description provided.
Delete branch "fix/979-seasonal-normalize"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
REOPENED #979 — normalize.py was never created (only rate-regime discount existed).
New backend/app/services/forecasting/normalize.py: normalize_demand(series) does multiplicative month-of-year deseasonalization of the raw monthly demand SalesSeries (§9.4). Pure; min-data guard (factor=1.0 on <2yr/empty-month/overall<=0). Synthetic test: seasonality removed, flat/thin/empty/all-zero safe. 793 forecasting tests green.
DoD (module+doc+test) MET. HONEST CAVEAT: production wiring into rate_sensitivity DEFERRED (documented TODO) — deseasonalizing the short rate-driven series perturbs recovered β/lag on current data; needs points-per-month gate + backtest before wiring. Leaving issue OPEN for that wiring follow-up rather than claiming full done. Refs #979