a plethora of evolving options
- which packages should I use?
- why should I use these packages?
- how do they differ?
- how should I use these packages?
- which package(s) should I develop for?
- how do I disseminate my software?
How do we:
Coming at it from a developer's perspective, we needed something
Can be quick to do, and powerful, but application specific scalability, and not easy to port across different architectures.
Similar in concept to workflow execution in Nipype, but again limited by the need for command line tools and flexibility in terms of scaling across hardware architectures (although see makeflow).
Integration with other tools is ad hoc (i.e., system call) and dataflow is managed at a programmatic level. However, see PSOM which offers a very nice alternative to some aspects of Nipype for Octave/Matlab users.
Graphical options: (e.g., LONI pipeline)
Adding or reusing components across different projects require XML manipulation or subscribing to some specific databases.
- development and distribution
- scientific computing
- brain imaging
You just need to know 1 language to do almost everything !