Closed mharradon closed 7 years ago
Glad you found that setting...that was not a helpful error message haha.
On the to-do list is to re-work this part to communicate the needed information using the ZeroMQ component rather than pre-allocated multiprocessing arrays, so this won't even be a thing. It is leftover from before I had any of the ZeroMQ part.
For posterity.
I was able to solve by calling synk.fork with a larger value for 'max_n_var' keyword argument - current default is 100 variables. Possibly could catch that exception and print a better error message? That one's a real head scratcher to look at - the code looks like this: