You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After the change to using the diffusers library for the scheduler in the TimeGrad model in version 0.7.0 the serialization of models has been broken. The scheduler is unable to be serialized by GluonTS.
predictor.serialize(Path("./model"))
Results in the following runtime error:
RuntimeError: Cannot serialize type diffusers.schedulers.scheduling_deis_multistep.DEISMultistepScheduler. See the documentation of the `encode` and
`validate` functions at
http://gluon-ts.mxnet.io/api/gluonts/gluonts.html
and the Python documentation of the `__getnewargs_ex__` magic method at
https://docs.python.org/3/library/pickle.html#object.__getnewargs_ex__
for more information how to make this type serializable
Based off of the HuggingFace documentation there does appear to be a way to serialize the scheduler but this is separate from how GluonTS saves its models.
A solution to this problem could involve unassigning the scheduler when it is time to save the model but this does not seem like an appropriate solution. I am also unsure how to unassign this in the predictor as it does not seem we are able to access this. Any suggestions on how to serialize the model would be appreciated.
The text was updated successfully, but these errors were encountered:
After the change to using the diffusers library for the scheduler in the TimeGrad model in version 0.7.0 the serialization of models has been broken. The scheduler is unable to be serialized by GluonTS.
Results in the following runtime error:
Based off of the HuggingFace documentation there does appear to be a way to serialize the scheduler but this is separate from how GluonTS saves its models.
This can then be loaded in again, but you require to know the scheduler you want
A solution to this problem could involve unassigning the scheduler when it is time to save the model but this does not seem like an appropriate solution. I am also unsure how to unassign this in the predictor as it does not seem we are able to access this. Any suggestions on how to serialize the model would be appreciated.
The text was updated successfully, but these errors were encountered: