Pymc3 getting stuck after initialization

In general yes. The thing is that you need to be able to debug the error that happens in the spawn. Try to read through this question thread to see how to be able to read the actual exception being raised while the multiprocessing spawns are being built. We found that if you try to run your script as a batch file (save the script in your_script.py and then run it from a command prompt as python.exe your_script.py, do not run it from Spyder or pycharm as these may use an ipython kernel), you should be able to see the full traceback of your spawns errors (usually the last error that is printed to the prompt is a broken pipe error which happens in the main process and is not the real reason the script failed). Try that, see if you can find the traceback to your true error and then post it here so we can help you.