-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
[ENH] Interfacing chronos-bolt
in sktime
#7680
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
Comments
I would like to work on this issue, @fkiraly. |
Sure! Quick question, is this simply a different checkpoint that can be run with the current architecture, or does it require also different code? A link to the hf weights would be appreciated. |
This is the one currently being interfaced: The one I plan to interface: |
Do you know the answer to this?
|
No, it is not a checkpoint. It seems to have a slightly different architecture over the original |
Hi, before I proceed with a PR, I wanted to confirm whether I should interface |
From the documentation amazon-science/chronos-forecasting we know that |
) #### Reference Issues/PRs Fixes #7680 #### What does this implement/fix? Explain your changes. The PR extends the existing `ChronosForecaster` class to support the latest `chronos-bolt` family of models, which operators upon the same `BaseChronosPipeline` as `chronos`. Links: [Chronos-Bolt-Tiny](https://huggingface.co/amazon/chronos-bolt-tiny) --------- Co-authored-by: PranavBhatP <pranavbhat2004@gmai.com> Co-authored-by: Armaghan Shakir <raoarmaghanshakir040@gmail.com>
…time#7718) #### Reference Issues/PRs Fixes sktime#7680 #### What does this implement/fix? Explain your changes. The PR extends the existing `ChronosForecaster` class to support the latest `chronos-bolt` family of models, which operators upon the same `BaseChronosPipeline` as `chronos`. Links: [Chronos-Bolt-Tiny](https://huggingface.co/amazon/chronos-bolt-tiny) --------- Co-authored-by: PranavBhatP <pranavbhat2004@gmai.com> Co-authored-by: Armaghan Shakir <raoarmaghanshakir040@gmail.com>
Is your feature request related to a problem? Please describe.
The
Chronos
model has already been implemented insktime
asChronosForecaster
. Recently, an improved version ofChronos
was developed namelyChronos-Bolt
. The model has been to proven to have faster inference and better efficiency than the pre-exisitingChronos
model.Refer blog
Describe the solution you'd like
Interfacing
Chronos-Bolt
seems to be a good option, although I'm not sure about whether this would be mean replacing the pre-exisitingChronosForecaster
or a standalone implementation?Additional context
The need for the same was also expressed in the conversation linked to the below message.
Reference issue: #1736
sktime/pytorch-forecasting#1736 (comment)
The text was updated successfully, but these errors were encountered: