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

Workflow execution: in-place v.s. containerized #22

Open
OliverEvans96 opened this issue Aug 9, 2017 · 0 comments
Open

Workflow execution: in-place v.s. containerized #22

OliverEvans96 opened this issue Aug 9, 2017 · 0 comments

Comments

@OliverEvans96
Copy link
Collaborator

It seems that workflow engines (Toil, CWL, Fireworks) tend to assume that your workflow should be executed with a newly created folder as the working directory. I've figured out how to circumvent this with Fireworks, but the prevalence of this pattern is making me wonder: should we also be insisting that workflows be executed in new folders? It seems that placing as few restrictions on the user as possible is preferable. While there are clear advantages to having a separate working directory for each run of a workflow, sometimes it makes more sense to execute commands within an existing directory.

Other thoughts or links are appreciated.

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

1 participant