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.
sktime support
Added an adapter in timecopilot/models that can be used to work with sktime models using TimeCopilot.
Adding an SKTime forecaster currently requires the adapter be wrapped around a BaseForecaster (the abstract class sktime forecasters inherit from) by the user before passing it in a model list to a TimeCopilot agent. Setup for sktime models is currently being left to users as those arguments may vary according to the model and data. BaseForecaster can be added as a type hint if sktime is added to the requirements.
Alias currently defaults to
"SKTimeAdapter", should it be a required argument?There currently is not support for levels and quantiles via the sktime adapter. It doesn't look like those are available for every sktime forecaster, so a decision on how to handle those cases should be made before supporting those features.
Exogenous data could be supported, and would also be a next step to take for sktime support. Exogenous data may have similar constraints to quantiles/levels.
Where should the sktime notebook be placed in the list of example notebooks?