These are chat archives for dereneaton/ipyrad
ip.__init__to create a unique profile id, to allow for the possibility that someone can run more than one notebook at a time? Otherwise when you shut down one notebook it would kill both...
ip.__init__needs to ask (1) is a controller already running with this profile-id? (2) If no, I'll use it. But if yes, then I'll create a new profile... The problem with this is that we need some way for Engines to know that they are Engines so they do not create new profiles too.
ipcluster stopat shutdown to ensure we don't leave it hanging, since it's daemonized. Unless there's some smarter way to do that.
Makes me think we might have jumped the gun on switching to ipyparallel. My main reason for doing so was that
multiprocessing really doesn't work well in notebooks.
Using ipyparallel is forward thinking, but will probably require some kludges early on. We'll just have to keep an eye on ipyparallel and update our code as it improves. For now, I'm fine with leaving ipcluster launch inside
Assembly.__init__, since I can't see a way to get it to work otherwise yet, and I've spent quite a lot of time trying. But you are welcome to try out the profiles biz, maybe there's something I've missed about it.