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
---------------------------------------------------------------------------ValueErrorTraceback (mostrecentcalllast)
CellIn[21], line31fromsdv.single_tableimportCTGANSynthesizer---->3synthesizer=CTGANSynthesizer.load(
4filepath='synthesizer.pkl'5 )
Fileopt/project/venv/lib/python3.10/site-packages/sdv/single_table/base.py:568, inBaseSynthesizer.load(cls, filepath)
566withopen(filepath, 'rb') asf:
567try:
-->568synthesizer=cloudpickle.load(f)
569exceptRuntimeErrorase:
570err_msg= (
571'Attempting to deserialize object on a CUDA device but '572'torch.cuda.is_available() is False. If you are running on a CPU-only machine,'573" please use torch.load with map_location=torch.device('cpu') "574'to map your storages to the CPU.'575 )
Fileopt/project/venv/lib/python3.10/site-packages/numpy/random/_pickle.py:34, in__bit_generator_ctor(bit_generator_name)
32bit_generator=BitGenerators[bit_generator_name]
33else:
--->34raiseValueError(str(bit_generator_name) +' is not a known '35'BitGenerator module.')
37returnbit_generator()
ValueError: <class'numpy.random._mt19937.MT19937'>isnotaknownBitGeneratormodule.
Based on the error message, there might be something different about the environment used to train (and export) the synthesizer and the environment used to load and utilize the synthesizer. Specifically, it seems like the NumPy versions may be different in some incompatible way.
First, I'm curious if the environments were in fact different or if I'm wrong :)
If so - do you mind sharing the differences in library versions? If you use pip, you can use pip frezee to get a list of libraries and their versions in both environments.
Is there any chance the model was trained on a device with a GPU but is now being used on a device without a GPU? Some of the error output seems to suggest that might be some difference here in CUDA availability or actual hardware difference between environments.
Environment Details
Error Description
Steps to reproduce
The text was updated successfully, but these errors were encountered: