-
Notifications
You must be signed in to change notification settings - Fork 6
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
Add strategy description to Pipeline
docs
#372
Comments
Thank you for you suggestion!
In contrast in
If underlying model is autoregressive, the forecasting with If underlying model is regressive (sklearn-like), then |
Thanks for the detailed answer! I think we should specify all of the above in the As a possible option, I suggest the documentation descriptions below: Pipeline AutoRegressivePipeline I think the same information should be added to the documentation of the forecast method for I'm interested in contributing to this issue as a first-time contributor. Therefore, I would like to know if it is possible to update the documentation in accordance with the option I have proposed. |
It isn't really convenient to add this information into It could also be possible to add "See also" block in If you are going to take this issue:
|
1) Wrap step param into double `` in the AutoRegressivePipeline docs. 2) Fix problem with linting. 3) Add a link to the pull request in the CHANGELOG.md
🚀 Feature Request
You should add in the api references a mention in the
Pipeline
documentation (link) that this class implements a direct forecasting strategy. And also, perhaps, you should add a reference toAutoRegressivePipeline
, which implements recursive strategy.Proposal
New documentation for the
Pipeline
class, which contains a reference to the implementation of a direct strategy and a link to theAutoRegressivePipeline
.An example of a new possible description:
Pipeline of transforms with a final estimator, which implements direct forecasting strategy. If you are looking for recursive strategy implementation please see
AutoRegressivePipeline
.Test cases
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: