Mccalluc/trivial example

[mccalluc]

Trivial CWL that just lists outputs, plus test machinery for travis: I'd suggest that all the directories have the same naming convention and organization to keep things simple.

• Does this pattern seem ok to you?
• If I wanted something like this to actually be run, would I just tell you, either in the PR, or Slack?
• There are different kinds of processing... On submission from users, or on completion of an earlier workflow; For every kind of file set, or just for particular file types: Do we know yet how those kind of conditions would be expressed?

[mccalluc]

@pdblood : Anything I can do to move this along?

[pdblood]

We'll be refining and debugging the best practices for adding workflows and getting them running, but let's try this out and see how it goes.

[pdblood]

Trivial CWL that just lists outputs, plus test machinery for travis: I'd suggest that all the directories have the same naming convention and organization to keep things simple.

* Does this pattern seem ok to you?

* If I wanted something like this to actually be run, would I just tell you, either in the PR, or Slack?

* There are different kinds of processing... On submission from users, or on completion of an earlier workflow; For every kind of file set, or just for particular file types: Do we know yet how those kind of conditions would be expressed?

Matt Rufflalo created the Airflow Python DAG to run his CWL workflow (based on existing DAGs in the repo) and submitted a pull request for that DAG. We can also create a DAG based on a workflow, but frankly we still need to sort out what the best practices should be. We'll start with internal developers and then consider how to support workflows submitted by external users.

A mechanism I'd like to try is for CWL workflows to be published in Dockstore and then pulled from Dockstore in the Airflow python DAG.