[Neuroimaging] Nipype with Taverna (or similar)?

[Satrajit Ghosh]

hi john,

considered yes, but more closely discussed things like provenance with
carole, daniel, and others from the taverna world. taverna was too
web-based for us when we started. but these days we are keeping a close eye
on CWL (https://common-workflow-language.github.io/), which carries many of
nipype's semantics as a way to integrate with a broader workflow base. when
nipype started, you either had to be in the cloud, or local, or on an HPC
cluster for the existing workflow systems to work. we needed to be able to
do all of those, given our user-base, so nipype's plugin architecture
focused on providing that flexibility, first through ipython and then
through more native plugins.

one constraint that nipype still has is a shared directory space. we will
be moving away from this constraint in the next year as we integrate with
CWL, but that has limited some of the things. the constraint was fine for
neuroimaging, because files are big, you don't want to move or replicate
them. but as nipype gets used for other things, the constraint is
constraining!

cheers,

satra

On Tue, Aug 25, 2015 at 12:35 PM, John Pellman <pellman.john at gmail.com>
wrote:

> Odd question, but has the nipype team ever considered integrating nipype
> with a more general workflow management system such as Taverna
> <http://www.taverna.org.uk/> ?
>
> _______________________________________________
> Neuroimaging mailing list
> Neuroimaging at python.org
> https://mail.python.org/mailman/listinfo/neuroimaging
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/neuroimaging/attachments/20150825/84bb5760/attachment.html>