New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] SeasonalityACF nlags
is not inclusive
#4169
Comments
oh, you are right. I've been writing python for a while now and still sometimes get confused with the plus/minus one thing... |
also, general feedback about the parameter estimator module is appreciated! It's still a bit experimental, e.g., is the pipelining/plugin functionality useful? |
This is indeed a very nice piece of functionality. We have incorporated it into pycaret now for auto seasonal detection. We add a wrapper before this to detrend the series if needed before passing to One difference is that we detect the seasonality upfront (since it is sometimes hard to explain from a business perspective why seasonality is changing from fold to fold). Hence we are not using this in the forecasting pipeline for now. We just detect the SP upfront and set it to the same value for all folds. |
You can just pipeline it outside, i.e., |
We could, but the flow in pycaret separates out the setup/EDA from model developent. The SP detection falls in the setup/EDA section so we have to do it upfront before doing model development. Moreover, since the SP detection step is common to all models, it should not be repeated in training (adds extra time). from pycaret.time_series import TSForecastingExperiment
exp = TSForecastingExperiment()
exp.setup(data) # SP detection happens here
# Uses SP detected in setup unless user passes SP explicitly through arguments here.
model1 = exp.create_model("arima")
model2 = exp.create_model("ets") |
I see - interesting point where one parameter is plugged into multiple models. What happens to those models then - are they being benchmarked? Or do you select them, like in a multiplexer forecaster? |
Yes similar to the multiplexer, we have a wrapper called An example can be found here: https://nbviewer.org/github/pycaret/pycaret/blob/master/examples/time_series/forecasting/time_series_103.ipynb |
Describe the bug
SeasonalityACF does not consider lags upto nlags but up to nlags - 1. This is because of this statement.
sktime/sktime/param_est/seasonality.py
Line 143 in daf5f81
I think this should be increased by 1 to allows
nlags
to be inclusive.To Reproduce
Expected behavior
Would have expected nlags to be inclusive per the documentation.
sktime/sktime/param_est/seasonality.py
Lines 36 to 38 in daf5f81
Additional context
Versions
sktime == 0.15.0
The text was updated successfully, but these errors were encountered: