2017
DOI: 10.1016/j.procs.2017.05.116
|View full text |Cite
|
Sign up to set email alerts
|

Facilitating the Reproducibility of Scientific Workflows with Execution Environment Specifications

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1

Citation Types

0
7
0

Year Published

2019
2019
2024
2024

Publication Types

Select...
5
3

Relationship

0
8

Authors

Journals

citations
Cited by 14 publications
(7 citation statements)
references
References 13 publications
0
7
0
Order By: Relevance
“…Full reproducibility and reusability of scientific results requires not only the data and code, but also the whole software environment in which the code was executed. There are several solutions to achieve reproducible execution environments 8 . We adopted incremental Reproducible Execution Environment Specifications (REES) to build a reproducible environment for the Atlas repository.…”
Section: Resultsmentioning
confidence: 99%
“…Full reproducibility and reusability of scientific results requires not only the data and code, but also the whole software environment in which the code was executed. There are several solutions to achieve reproducible execution environments 8 . We adopted incremental Reproducible Execution Environment Specifications (REES) to build a reproducible environment for the Atlas repository.…”
Section: Resultsmentioning
confidence: 99%
“…We emphasize the importance of generating workflows 3,26 , not only for tracing provenance of data and making them transparent to the community 27 , but also in order to explain in a detailed and compact way the scientific strategies used in the paper; these may then be used for training purposes for students or investigators interested in joining a specific project related to the paper, or for collaborations. In the future, the generation of the workflow can be automated by enabling Qresp to read the metadata produced by workflow management tools, e.g.…”
Section: Resultsmentioning
confidence: 99%
“…Annotating a workflow execution with the provenance of its components has been previously used for traceability, reproducibility, and explaining results. Related work for collecting and preserving the provenance of a workflow at the system level include developing custom file systems tracking provenance such as the Lineage File System (LinFS) [11], PASTA in PASS (Provenance-Aware Storage Systems) [8], and Parrot [12]; encapsulating workflows through ad hoc packages such as CDE [13], ReproZip [14], Umbrella [15], and Occam [16] [17]; and encapsulating workflows through existing container technologies such as Pachyderm [9], RE-ANA [10], and Science Capsule [41]. The use of custom file systems and custom ad hoc packages limits the portability and usability of their solutions across systems.…”
Section: Related Workmentioning
confidence: 99%
“…Second, scientists track provenance with custom systems that do not offer portability across heterogeneous platforms. For example, work in [8], [11], [12] builds on custom file systems, and work in [13], [14], [15], [16], [17] builds on custom software packaging. Containers offer a lightweight solution to track provenance across platforms by encapsulating applications and dependencies into an isolated environment [18], [19], [20], [21].…”
mentioning
confidence: 99%