Add chronos-forecasting as a library

[abdulfatir]

Adding chronos-forecasting as a library as suggested by @NielsRogge here: amazon-science/chronos-forecasting#339

[Wauplin]

Thanks for opening this PR and congrats on the release of chronos-2! 🤗

I've left some minor comments but otherwise looks good to me. Let me know if you have any questions

[Wauplin]

Suggested change

	prettyLabel: "Chronos",
	repoName: "chronos-forecasting",
	prettyLabel: "Chronos Forecasting",
	repoName: "Chronos Forecasting",

We are in the process of merging these 2 fields. Is Chronos Forecasting ok for you?

[abdulfatir]

Chronos Forecasting works but I would slightly prefer just Chronos. Would that be okay?

[Wauplin]

yes ofc!

[Wauplin]

Thanks for the quick update! I'll merge it now. Expect 2-3 days before getting it live on the Hub 🤗

[abdulfatir]

@Wauplin what's the way to check if this change was deployed to HF?

[Wauplin]

Hey @abdulfatir, it should be deployed tomorrow :)
You'll see a "Chronos" section in the "use this model" sidebar.

[abdulfatir]

@Wauplin Thank you! It's now live on HF. The Chronos snippet shows up correctly but the UI still shows an option for Transformers. However, since transformers does not really natively support Chronos yet, the snippet is incorrect. Is there a way to disable this and only show Chronos?

[Wauplin]

Hi @abdulfatir, this is because the model is tagged as transformers in the model card. Removing the tag would remove the snippet in the "use this model" section. I opened a PR directly on the repo to do that, you just have to merge it 🤗
https://huggingface.co/amazon/chronos-2/discussions/2

[abdulfatir]

@Wauplin Merged, thank you!

Sorry, but looks like there's another issue: the download counter has stopped since this PR's changes went live and I changed the library_name. My understanding is that the count changes every day but it did not change today. Should I open a PR and add the following back?

countDownloads: `path:"config.json"`,

[Wauplin]

No need for it no. Let's wait for a few days to see how it evolves. Everything should be good now :)

1-day delays can happen from time to time due to failed jobs on our end. Data is recovered on the next trigger.

[abdulfatir]

@Wauplin sounds good. Thank you for the clarification.

[abdulfatir]

@Wauplin it works. Thank you! 🎉

[Wauplin]

Great to hear that!