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

Support dynamic process creation #4

Open
joestubbs opened this issue May 12, 2015 · 1 comment
Open

Support dynamic process creation #4

joestubbs opened this issue May 12, 2015 · 1 comment

Comments

@joestubbs
Copy link
Owner

A very common pattern is to spawn a number of processes ("workers") dependent on the "size" of the output from a previous step (e.g., a dynamic version of the pi approximation wf). There are a number of ways this could work from the client/api perspective. Nextflow has several examples. We should first document what we could pull off using doit. There may be some limitations around using doit with multiprocessing and actions defined using closures.

@deardooley
Copy link

Really like a launcher port/alternative here. If we can replicate launcher with service discovery over serfnode, we have MPI in sight as well.

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

No branches or pull requests

2 participants