Chronos 2

[abaranov25]

Resolve #662
Adding Chronos-2 as a new pipeline on Orion

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.

---

AllenBaranov seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[sarahmish]

@abaranov25 seems like Chronos2 pipeline did not work well on S-1 example, do you have an idea why? I'm curious if you use S-1-test would you get different results?

[sarahmish]

I'm curious why 256? Orion pipelines that are forecast based are usually set to 250. For timesfm, it was set to 256 because it needs to be a multiple of 32 according to their docs.

[sarahmish]

We typically set the example to interval=21600 since our example code uses NASA signals (MSL and SMAP)

[sarahmish]

If chronos works on python 3.9+ remove this comment completely

[sarahmish]

add chronos to setup.py under the pretrained_requires section, then remove the try-catch since it will always be installed using pip install orion[pretrained]

[sarahmish]

Delete

[sarahmish]

@abaranov25 It would be nice to run the notebook locally then commit it so that the output is rendered into the notebook , then users can look at the github and immediately see the results of Chronos 2

[sarahmish]

This line needs to be updated

approved by mistake