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
[ENH] refactor _predict_moving_cutoff
and bugfix, outer update_predict_single
should be called
#2466
Conversation
@aiwalter, @GuzalBulatova, I think I finally found out what was causing all those The default implementation of Would appreciate your review on this. |
PS: discovered by debugging this PR #2458, a refactor of a composite estimator. It seems, in hindsight, that this would always break |
…ict_in_sample of _BaseWindowForecaster
oh nice! Then I can try to get rid of |
Your optimism is inspiring, as always. |
_predict_moving_cutoff
_predict_moving_cutoff
and bugfix, outer update_predict_single
should be called
* upstream/main: [ENH] more forecaster scenarios for testing: using `X` (sktime#2462) less uncertainty samples (sktime#2497) [ENH] remove error message on exogeneous X from DirRec reducer (sktime#2463) [BUG] fix accidental overwrite of default method/arg sequences in test scenarios (sktime#2457) changed references to fit-in-transform to fit_is_empty (sktime#2494) [MNT] loosen strict upper bound on `scipy` to 1.9.0 (sktime#2474) [DOC] Added clustering module to API docs (sktime#2429) [ENH] Add prediction intervals for `UnobservedComponets` forecaster (sktime#2454) [BUG] remove `alpha` arg from `_boxcox`, remove private method dependencies, ensure scipy 1.8.0 compatibility (sktime#2468) [BUG] removed metric integration notebook (sktime#2476) [ENH] refactor `_predict_moving_cutoff` and bugfix, outer `update_predict_single` should be called (sktime#2466) [ENH, BUG] Distance refactor and bug fix (sktime#2268) [ENH] add new argument return_tags to all_estimators (sktime#2410)
…refactor (#2470) Post #2466, there were dead args and functions, i.e., not called resp used by anything anymore. Both occurrences are in private locations, so can be removed without any adverse effect. * `return_pred_int` args in `_predict_moving_cutoff` - would raise a `NotImplementedError`, which is moved upwards into the `_BaseWindowForecaster` * `_format_moving_cutoff_prediction` in `_sktime.py` is an older version of the one in the base module, and not called anywhere.
This PR carries out a small refactor on
_predict_moving_cutoff
:return_pred_int=True
, these were never reached_update_predict_single
call toupdate_predict_single
, this was a bug, since this causes the cutoff to not be updated in_update_predict