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.

Sign up for GitHub

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

Jump to bottom

Finish server-based execution engine #37

Closed
jeffbaumes opened this issue Feb 10, 2014 · 3 comments
Closed

Finish server-based execution engine #37

jeffbaumes opened this issue Feb 10, 2014 · 3 comments
Assignees
@curtislisle
Milestone
Milestone 2: Full...

Comments

@jeffbaumes
Copy link
Member

No description provided.

@jeffbaumes jeffbaumes added this to the Milestone 1: Ready to Use milestone Feb 10, 2014
@curtislisle
Copy link
Member

Current state is that workflow construction and serialization to the database is working. Execution is beginning to work and should be complete soon.

@curtislisle
Copy link
Member

Execution works on my system, including both builtin steps (dataset queries) and rpy worksteps. Leaving this open, though, because an R source file has to be in just the right place, so this work isn't repeatable yet. See arborworkflows/ProjectManager#6

@curtislisle
Copy link
Member

celery-based workers for R and python are working nicely. Tested during the hackathon. They may require a bit of maturing, but working well enougjh to close this item.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@curtislisle curtislisle

Labels
None yet
Projects
None yet
Milestone
Milestone 2: Fully Editable Workflows
Development

No branches or pull requests
2 participants
@jeffbaumes @curtislisle