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
Date issues related to monthly prediction #1595
Comments
Hi @shubhashish1 it's very hard to understand from the screenshot where the error may be coming from. Could you please provide a running example, possibly with fake data, to reproduce the issue? |
@shubhashish1 It seems like that your frequency is misspecified, or that your date format is ambiguous and not aligned with the gluonts supported frequencies. Also note that, currently, gluonts only supports |
Hi, I am having exactly the same problem: when training on data from 2017 to 2021 I get the error: gluonts.core.exception.GluonTSDateBoundsError: Out of bounds nanosecond timestamp: 3230-03-31 00:00:00. |
@mliuzzi-amorelie Can you provide a code snipped that produces the error? Thank you! |
@mbohlkeschneider
And this is the function that produces the error:
|
And the entrypoint script 'blog_train_algos.py' is this:
|
@shubhashish1 did you manage to solve this problem for your data? |
Discussed in #1577
Originally posted by shubhashish1 June 21, 2021
Hi,
I am doing a monthly predictions for a list of items and the dates of each month available is the first date of the month i. e 1-1-2017 . But while training the same in the first date of every month I am getting the following error:
GluonTSDateBoundsError: Out of bounds nanosecond timestamp: 9043-01-31 00:00:00
The text was updated successfully, but these errors were encountered: