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][BUG] clean up Detrender
and implement correct multivariate behaviour
#4053
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
fkiraly
added
module:forecasting
forecasting module: forecasting, incl probabilistic and hierarchical forecasting
module:transformations
transformations module: time series transformation, feature extraction, pre-/post-processing
bugfix
Fixes a known bug or removes unintended behavior
enhancement
Adding new functionality
labels
Jan 3, 2023
FYI @mloning, @SveaMeyer13, @KishManani, would appreciate a look as you have worked on the detrender before. |
This was referenced Jan 3, 2023
KishManani
reviewed
Jan 5, 2023
klam-data
pushed a commit
to CodeSmithDSMLProjects/sktime
that referenced
this pull request
Jan 18, 2023
…haviour (sktime#4053) This PR improves the `Detrender`: * it fixes sktime#4051 and also simplifies the logic in the `Detrender`. As the `BaseForecasting` interface supports loop over hierarchy instances and variables natively, all the case distinctions internally can go, and with it goes the incorrect multivariate implementation. * adds support for detrending with hierarchical forecasters * adds support for detrending with forecasters that require `fh` in `fit` already (this was not possible previously) As a consequence, the test `test_polynomial_detrending` had to be updated since the internal mtype of the `Detrender` changed, from `pd.Series` based to `pd.DataFrame` based (requiring a minor change in how objects are being compared).
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
bugfix
Fixes a known bug or removes unintended behavior
enhancement
Adding new functionality
module:forecasting
forecasting module: forecasting, incl probabilistic and hierarchical forecasting
module:transformations
transformations module: time series transformation, feature extraction, pre-/post-processing
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR improves the
Detrender
:Detrender
#4051 and also simplifies the logic in theDetrender
. As theBaseForecasting
interface supports loop over hierarchy instances and variables natively, all the case distinctions internally can go, and with it goes the incorrect multivariate implementation.fh
infit
already (this was not possible previously)As a consequence, the test
test_polynomial_detrending
had to be updated since the internal mtype of theDetrender
changed, frompd.Series
based topd.DataFrame
based (requiring a minor change in how objects are being compared).