Refactoring Stacking, Multiplexer, Ensembler and TransformedTarget Forecasters#977
Refactoring Stacking, Multiplexer, Ensembler and TransformedTarget Forecasters#977fkiraly merged 16 commits intosktime:mainfrom
Conversation
|
looks like checks are all fine, so do you want to convert to "proper" PR and request reviews? |
|
and you may want to close #955 of which this is now a duplicate |
There was a problem hiding this comment.
This is great, thanks for your work!
Although the tests pass, I have some questions about the right tags, and the potential to dynamically attach tags based on components, to @mloning, @aiwalter, @koralturkk, see above.
Further, I think the pre-refactor mixins for MultiplexForecaster and EnsembleForecaster were incorrect, fh could be required in fit if the components do require it. Why did the tests not catch this?
This is not an issue with your refactor, @thayeylolu, but I just noticed it in looking at the code. We should perhaps fix these before at this opportunity.
|
I'm not really sure what the best solution is. A few thoughts:
Either way, I think this is a separate issue. I created one here: #981. |
|
ok, agreed - let's split off the larger tags discussion, and just do a "safe" refactoring here.
|
thayeylolu
left a comment
There was a problem hiding this comment.
I have made the necessary changes and I would I to convert the draft for review
|
the test examples are now failing - they ran before. |
|
I think it's the multiplexer - the tutorial notebook passes the |
|
I'd suggest:
What do you think, @mloning? |
|
@fkiraly Setting |
You mean, to |
|
pinging @ninamiolane |
mloning
left a comment
There was a problem hiding this comment.
Hi @thayeylolu, you need to check the update methods again, I think some of the code can still be removed there. Otherwise looks good to me!
…into refactor-stmultiplex merge with updates
|
@mloning this I ready for review :) |
fkiraly
left a comment
There was a problem hiding this comment.
Looks good to me - the earlier request is partly related to tags and will be addressed separately.
Updated from main and let's wait for tests to pass.
Reference : #955
-- This is a copy of 965 without changes to reducer.py (a time when there was no bug)
We need to slowly re-factor all forecasters to be compliant with the new interface (see PR #912). i.e., no overrides of fit etc and descendant classes only implementing core logic, while the BaseForecaster implements check etc logic.
Currently this is running due to various downwards compatibility workarounds, which should be removed once all forecasters are ready (in "no-override" state)
The forecasters that still need a downstream refactor are: