2008
DOI: 10.1007/978-3-540-89965-5_9
|View full text |Cite
|
Sign up to set email alerts
|

Kepler/pPOD: Scientific Workflow and Provenance Support for Assembling the Tree of Life

Abstract: Abstract. The complexity of scientific workflows for analyzing biological data creates a number of challenges for current workflow and provenance systems. This complexity is due in part to the nature of scientific data (e.g., heterogeneous, nested data collections) and the programming constructs required for automation (e.g., nested workflows, looping, pipeline parallelism). We present an extended version of the Kepler scientific workflow system to address these challenges, tailored for the systematics communi… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1

Citation Types

0
40
0

Year Published

2009
2009
2017
2017

Publication Types

Select...
7
3

Relationship

3
7

Authors

Journals

citations
Cited by 47 publications
(40 citation statements)
references
References 11 publications
0
40
0
Order By: Relevance
“…Despite treating the representation of parameter values, AWARD does not handle parameter values as data elements in its relational representation, which prevents the management of the dataflow at the logical level. There are some SWMS with dataflow management support at the logical level, such as Kepler [24], Panda [25] and Chiron [12]. SWMS typically register dataflow as workflow provenance.…”
Section: Raw Data and Workflowsmentioning
confidence: 99%
“…Despite treating the representation of parameter values, AWARD does not handle parameter values as data elements in its relational representation, which prevents the management of the dataflow at the logical level. There are some SWMS with dataflow management support at the logical level, such as Kepler [24], Panda [25] and Chiron [12]. SWMS typically register dataflow as workflow provenance.…”
Section: Raw Data and Workflowsmentioning
confidence: 99%
“…Scientific workflow systems are being used in many scientific domains, and many approaches have been proposed recently for representing and storing workflow provenance [5,6]. However, most of the existing provenance approaches store provenance for a single runs, and do not capture or maintain associations across runs [22,23,24,25]. The framework described in [7] records associations between multiple related workflow runs.…”
Section: Related Workmentioning
confidence: 99%
“…Provenance techniques have since been studied in the context of databases [9,29], scientific workflow systems [43,7], operating systems [48], and inference systems [38] (including recent interest in the Semantic Web community, culminating in a W3C Working Group on Provenance [27,47]). In each of these contexts, there is a large design space for provenance mechanisms, yet at the same time there is not a clear consensus on the requirements or policies that these mechanisms ought to satisfy.…”
Section: Introductionmentioning
confidence: 99%