Nathan Sheffield

I figured it out. Pypiper automatically adds results for `Time` and `Success`. If those aren't in your output schema, it fails. So you have to add this to the output...

I made a more informative error message in pipestat to address this here: https://github.com/pepkit/pipestat/commit/0d511b5960d460b4dda701379f6a982e3f407a0c This at least solves the immediate issue, but going forward: - [ ] pypiper should add...

sounds like a good candidate for a context manager :)

I don't understand the problem, sorry. Can you clarify?

You are right that pypiper is really intended to run sequentially. Our mode of operating is to parallelize *by sample*, rather than by task within a pipeline. This has lots...

And to directly answer your question: I am not planning to add parallelizing by task like this. But if you want to add it, I would consider a PR, as...

Can you clarify exactly what you're doing that's producing the error?

I don't think the attribute was changed.

in this example, processes 22, 23, and 24 were run simultaneously. 26,27,28 likewise. they were piped streams. these two commands are getting triple counted, hence the almost tripled report of...

what about hashing the actually pipeline run as well? you could has the `time` value in seconds since unix epoch... that way, you'd know if two commands were run in...