Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

pymc-learn: RuntimeError in JupterLab 1.2.6 #41

Open
ZhiqiangZhangCUGB opened this issue Jul 29, 2020 · 0 comments
Open

pymc-learn: RuntimeError in JupterLab 1.2.6 #41

ZhiqiangZhangCUGB opened this issue Jul 29, 2020 · 0 comments

Comments

@ZhiqiangZhangCUGB
Copy link

I am learning to use pymc-learn. However, whenever I try to run an MCMC simulation with pymc-learn in JupterLab 1.2.6 , I get the following RuntimeError:
RuntimeError: The communication pipe between the main process and its spawned children is broken.

In Windows OS, this usually means that the child process raised an exception while it was being spawned, before it was setup to communicate to the main process.
The exceptions raised by the child process while spawning cannot be caught or handled from the main process, and when running from an IPython or jupyter notebook interactive kernel, the child's exception and traceback appears to be lost.
A known way to see the child's error, and try to fix or handle it, is to run the problematic code as a batch script from a system's Command Prompt. The child's exception will be printed to the Command Promt's stderr, and it should be visible above this error and traceback.
Note that if running a jupyter notebook that was invoked from a Command Prompt, the child's exception should have been printed to the Command Prompt on which the notebook is running.

As an example, I am using a copy-paste from the 'LinearRegression' example of the pymc-learn:
model2 = LinearRegression()
model2.fit(X_train, y_train, inference_type='nuts')

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant