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
A SDV public user trained a synthesizer in SDV 1.11, saved the model PKL file, and then tried to import it into SDV 1.12. During import, SDV was trying to load specific Faker classes and this caused an error because of the delta in Faker versions.
Instead of saving this much object state and trying to recreate it on load, we could just save the model weights and load those. That honestly better represents the context needed for the model itself and could lead to less errors of this type that the user ran into.
The text was updated successfully, but these errors were encountered:
I want to be able to call CTGAN models from my C++ code. Using the synthesizer PKL files doesn't work because of all the Python context that's included.
Potential Solution
Provide a way to export just the model weights as something more standalone to use.
srinify
changed the title
Idea: Save only the model weights in the model PKL file instead of all the classes and other object properties
I want to be able to use synthesizer models in a standalone way
May 21, 2024
srinify
changed the title
I want to be able to use synthesizer models in a standalone way
I want to be able to use synthesizer models in a standalone way (just the model weights)
May 21, 2024
Problem Description
A SDV public user trained a synthesizer in SDV 1.11, saved the model PKL file, and then tried to import it into SDV 1.12. During import, SDV was trying to load specific Faker classes and this caused an error because of the delta in Faker versions.
See full context here: #1959
Potential Solution
Instead of saving this much object state and trying to recreate it on load, we could just save the model weights and load those. That honestly better represents the context needed for the model itself and could lead to less errors of this type that the user ran into.
The text was updated successfully, but these errors were encountered: