-
Notifications
You must be signed in to change notification settings - Fork 754
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
Error with MQCNNEstimator in benchmark_m4 examples #1405
Comments
Hey @pbruneau thanks for submitting this! One note:
This is not necessarily an issue, since |
Hi @lostella, thank you for the timely answer and explanation! After checking the final result, the metrics eventually obtained do not look absurd indeed. I guess only the main issue of NaN loss values showing up with |
hey @pbruneau I'm sorry to get back to this so late: I could reproduce the issue on gluonts Could you confirm? |
Yes, it looks all right now, thanks for the feedback @lostella! I'm closing the issue. |
Hi, I am facing same issue even if I used MQCNNEstimator with Here is the trainer and estimator parameters:
I also tried with hybridize/scaling True and False and with various learning rates. I am still getting this error:
Thanks in advance! |
I am having the same issue, any help is appreciated! |
If this happens when |
Description
Using
m4_weekly
, for example,MQCNNEstimator
yields NaN loss for each batch:On epoch end, the program crashes with the error:
With
hybridize=False
, these errors do not show up anymore, but training exhibits funny loss values (in the range of a few hundreds). As a reference,DeepAREstimator
yields consistent loss values (in a range less that 10), independently ofhybridize
being True or False.On a side note, I wonder to which extent this bug is related to #833 .
To Reproduce
A simplified and adapted version of benchmark_m4 is in this gist.
Error message or code output
Environment
The text was updated successfully, but these errors were encountered: