[Feature request] Allow specifying `changepoint_ds_lower` and `changepoint_ds_upper` · facebook/prophet#1987

(2 评论) (0 反应) (0 负责人)Python (17,686 star) (4,451 fork)batch import

enhancementgood first issue

描述

Do we think it would be useful to allow end users to specify the changepoint range in terms of the dates of the data, rather than the percentage of history (the existing changepoint_range)?

I think the default value of changepoint_range can have a huge impact on the forecast (e.g. when the time series shows recent growth), but goes largely unnoticed (e.g. as we collect more historical data, the first 80% of history becomes less relevant). Setting a percentage seems a bit more confusing compared to setting specific dates.

We would add these arguments directly to the Prophet.__init__ method, and make the required changes to Prophet.set_changepoints(). I understand that the __init__ method is already super bloated as is though, so keen to know if people think the added convenience of this feature is worth it.

贡献者指南

技术栈: python
领域: data
议题类型: feature
难度: 3
预计时间: 1-2 days
活动状态: stale
清晰度: clear
前置要求: PythonProphet library basics
新手友好度: 45
研究方向: Look at the Prophet class ` init ` method in `/python/prophet/forecaster.py` to understand existing parameters like `changepoint range`. Then examine `set changepoints()` to see how changepoints are determined. The discussion in the issue suggests adding `changepoint ds lower` and `changepoint ds upper` parameters. Also consider that the ` init ` is already large, so refactoring might be needed. No linked PRs, but comments indicate interest.