Earlier quoted context omitted.
> I'm sorry I don't have time to answer in full. We're not getting anywhere. Just give me goddamn examples! :) Please! Examples! > I can see this is really really hard to grok if you're basing everything on the idea of a DAG, and so many tools are that it's very natural to think you couldn't do it any other way. There is no other way . BPipe is based on the idea of a DAG. You just don't see it. > In Bpipe the user de…
> There is no other way. BPipe is based on the idea of a DAG. You just don't see it. So if you think Bpipe uses a DAG, then I wonder how you would think it deals with: run { fix_names + fix_names + fix_names } In terms of the pipeline stages that run this is cyclic, so it cannot be a DAG. On the other hand the files created do usually form a DAG dependency relationship, but even there, in the most general case, it's…
fix_names()
...
_
Is there any difference between Bpipe's version and Drake's version that I am failing to see?> I'm much more interested in getting my job done than being pure about things.
It's funny coming from someone who I have been BEGGING for examples but getting abstract philosophical reasoning in return.
I repeat. Give me an example. So far you haven't given me one example of what Bpipe can do that Drake couldn't do in the same way or better, and yet you continue claiming philosophical differences.
If we concentrate on examples and discuss how they would work, whether there are differences, and what these differences are, I guarantee you, we'll make progress. But then again, I'm repeating myself.
Artem.