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
Operating System: Linux, environment is a Colab Notebook
Error Description
In a Colab Notebook environment, I am unable to get results for custom synthesizers if I supply a timeout value. The synthesizer shows up in the results DataFrame, but all the associated values for it are NaN (even the ones for dataset size, initialization, etc.). All of the other, pre-defined synthesizers produce values.
This problem goes away if I remove the time out value, or run the script on my local machine instead. So it is the combination of following that is causing the issue:
(a) running on a Colab notebook (or likely any interactive environment), and
(b) adding a custom synthesizer to the benchmark, and
(c) adding a timeout
Steps to reproduce
The code below creates a custom synthesizer that is just a variant of GaussianCopula (setting marginals to uniform). Then it tries to run the benchmark for it.
npatki
changed the title
Unable to use a custom synthesize with a timeout on a Colab Notebook
Unable to use a custom synthesizer with a timeout on a Colab Notebook
Dec 11, 2024
Environment Details
Error Description
In a Colab Notebook environment, I am unable to get results for custom synthesizers if I supply a timeout value. The synthesizer shows up in the results DataFrame, but all the associated values for it are NaN (even the ones for dataset size, initialization, etc.). All of the other, pre-defined synthesizers produce values.
This problem goes away if I remove the time out value, or run the script on my local machine instead. So it is the combination of following that is causing the issue:
Steps to reproduce
The code below creates a custom synthesizer that is just a variant of GaussianCopula (setting marginals to uniform). Then it tries to run the benchmark for it.
This script works as expected on a terminal. But if I run it on a Colab Notebook, I see NaN values produced:
Additional Context
According to @frances-h: We ran into a similar issue when working on this PR.
The text was updated successfully, but these errors were encountered: