3 ms·
There's actually a subfield called 'scientific workflow systems' (SWS). An example of such a system is Kepler [1]. What the author(s) ask at the end of the arti
by markhollis 9y ago
There's actually a subfield called 'scientific workflow systems' (SWS). An example of such a system is Kepler [1]. What the author(s) ask at the end of the article seems to me basically that they want process provenance. This is a fairly well studied problem.
[1]: https://en.wikipedia.org/wiki/Kepler_scientific_workflow_system https://en.wikipedia.org/wiki/Kepler_scientific_workflow_sys...
- myxie 9y ago+1 to this comment. It is a reasonably sized body of research, too. On top of this, scientific workflow scheduling maps to the classic scheduling problem, which is known to be NP-hard - the fact that the authors infer that automating the traversal is all that is necessary suggests that they have an incomplete understanding of the problem at hand. For those interested, a nice list of workflow managers, engines, and even languages can be found at https://github.com/pditommaso/awesome-pipeline https://github.com/pditommaso/awesome-pipeline.