Ducttape seeks to address the following issues from LoonyBin:
- Long edit, recompile, regenerate, copy, re-run cycles
- Confusing Python->Bash code generation
- GUI testing/support/development headache
- Relocatable workflows (no absolute symlinks)
- SSH spamming (no remote workflows, for now)
- Multi-pass post-analysys (workflows can now be re-analyzed using "Summaries" long after the workflow was originally written)
- Share status pages via a central web server
- Mediate complexity with subworkflows and groups
- Multiple levels of escaping with bash/python/SSH/heredocs are gone
- Using workflows as templates via config files
- Collaborative workflows vai reading an upstream workflow as a type of subworkflow (future work)
- Scriptable via CLI
- Realizatoin/file globbing
- Simple one-off experiments can be added in a single line
- Software versioning via Git/SVN and file versioning via SHA1/MD5
- "Local build and copy" pattern for obstinant remote build environments (e.g. cluster workers vs gateways, or just bad gateways)
- Parameter dependencies don't affect temporal ordering
-
The overall design now uses a multi-pass strategy rather than a single pass strategy.
-
TODO: How would we handle a factored translation setup?