create a Job class about qiime2 HOT 5 CLOSED

👍 It could also hold the expected filepaths of the completed artifacts.

from qiime2.

+1

Sent from my phone, please excuse typos and brevity.
On Mar 9, 2016 6:59 PM, "Evan Bolyen" [email protected] wrote:

[image: 👍] It could also hold the expected filepaths of the completed
artifacts.

—
Reply to this email directly or view it on GitHub
#23 (comment).

from qiime2.

Parent or child relationships?
On Mar 9, 2016 7:14 PM, "Greg Caporaso" [email protected] wrote:

+1

Sent from my phone, please excuse typos and brevity.
On Mar 9, 2016 6:59 PM, "Evan Bolyen" [email protected] wrote:

[image: 👍] It could also hold the expected filepaths of the completed
artifacts.

—
Reply to this email directly or view it on GitHub
#23 (comment).

—
Reply to this email directly or view it on GitHub
#23 (comment).

from qiime2.

@wasade, not sure I understand your question. This would likely just be a simple struct-like object. If you are talking about workflows calling other workflows (and tracking it), the execution model isn't that sophisticated. We leave those decisions to super-systems (like Qiita).

from qiime2.

Ah, okay. Just wondering if a job knew it's relationships. For instance, I
imagine a workflow might trigger a series of serial jobs, or a map/reduce
pattern.
On Mar 9, 2016 7:31 PM, "Evan Bolyen" [email protected] wrote:

@wasade https://github.com/wasade, not sure I understand your question.
This would likely just be a simple struct-like object. If you are talking
about workflows calling other workflows (and tracking it), the execution
model isn't that sophisticated. We leave those decisions to super-systems
(like Qiita).

—
Reply to this email directly or view it on GitHub
#23 (comment).

from qiime2.