Open dmitra79 opened 2 years ago
I am aware of https://github.com/awslabs/gluon-ts/issues/1570 but it doesn't provide a solution
Thanks for raising the issue!
What's weird is that we define loss_name
as a property here:
Maybe it has to do with multiprocessing
. Can you try rerun the code with Evaluator(num_workers=None, ...)
?
@jaheba Thanks! It ran fine with num_workers=None
. That is weird, also somewhat annoying if one can't use multiple CPUs for evaluation.
Thanks for confirming that it works that way.
The issue seems to be related to using notebooks and how they are setup. On my local machine the notebook runs fine, so we would need to investigate what causes the failure.
I've tried some more, but still can't replicate the issue.
My guess is that something went missing during pickling/un-pickling. Quantile
is defined as a NamedTuple
and the attributes appear to work -- value
is accessed before loss_name
without issues.
Maybe there is some optimisation for named-tuples at work, or there can be an entirely different reason.
We could try and use a dataclass
instead to check whether that changes anything.
@dmitra79 Can you tell a bit more about how you run the code? Is it a notebook and is there anything "special" about yours setup?
It is a notebook, running in a cloud session. There may be some package incompatibilities in the environment (I am limited in what packages/versions I have access to in that session), and some proprietory packages. I am using conda for package management. I realize this makes it impossible to replicate exactly.
I wonder if #2047 would fix this.
Description
I get this error trying to run a simple evaluation as described in: https://ts.gluon.ai/tutorials/forecasting/extended_tutorial.html
Error message or code output
(Paste the complete error message, including stack trace, or the undesired output that the above snippet produces.)
Environment