aboutsummaryrefslogtreecommitdiff
path: root/paper.tex
diff options
context:
space:
mode:
authorMohammad Akhlaghi <mohammad@akhlaghi.org>2020-05-01 12:52:22 +0100
committerMohammad Akhlaghi <mohammad@akhlaghi.org>2020-05-01 12:52:22 +0100
commit8f0ce4a1edae4db08853c80ce9fdbc18598a0c43 (patch)
tree71d83d1d03886fc20a1f331979ed1b3866fca0b8 /paper.tex
parentbff9cb568f7442951e8cac501cc035f443d7d2f0 (diff)
parent43816863335cc44714448d8e51dd0f83b3e2b12e (diff)
Merged David's suggestions, further edited to be more clear
It is also slightly shorter with this commit, without loosing anything substantial.
Diffstat (limited to 'paper.tex')
-rw-r--r--paper.tex12
1 files changed, 5 insertions, 7 deletions
diff --git a/paper.tex b/paper.tex
index cb3afdd..fcd23cf 100644
--- a/paper.tex
+++ b/paper.tex
@@ -53,19 +53,17 @@
%% Abstract % max 250 words for CiSE
{\noindent\mpregular
%% CONTEXT
- Many reproducible workflow solutions have been proposed during recent decades.
- Most use the high-level technologies that were popular when they were created, providing an immediate solution that is not sustainable in the long-term.
- However, decades later, scientists lack the resources to rewrite their projects, while still being accountable for their results.
+ Many reproducible workflow solutions have been proposed over the recent decades.
+ Most use the high-level technologies that were popular when they were created, providing an immediate solution which is unlikely to be sustainable in the long term.
+ Decades later, scientists lack the resources to rewrite their projects, while still being accountable for their results.
This creates generational gaps, which, together with technological obsolescence, impede reproducibility and building upon previous work.
%% AIM
We aim to introduce a set of criteria to address this problem and to demonstrate their practicality.
%% METHOD
- The criteria are: completeness (no dependency beyond a POSIX-compatible operating system, no administrator privileges, no network connection and storage primarily in plain-text); modular design; linking analysis with narrative, temporal provenance; scalability; and free-and-open-source software.
+ The criteria have been tested in several research publications and can be summarized as: completeness (no dependency beyond a POSIX-compatible operating system, no administrator privileges, no network connection and storage primarily in plain-text); modular design; linking analysis with narrative, temporal provenance; scalability; and free-and-open-source software.
%% RESULTS
- The criteria's usefulness is tested through an implementation: "Maneage" (managing+lineage).
- This is stored in machine-actionable and human-readable plain-text, enabling version-control, cheap archiving, automatic parsing to extract data provenance, and peer-reviewable verification.
+ Through an implementation, called "Maneage" (managing+lineage), we find that storing the project in machine-actionable and human-readable plain-text, enables version-control, cheap archiving, automatic parsing to extract data provenance, and peer-reviewable verification.
Furthermore, we show that these criteria are not limited to long-term reproducibility but also provide immediate, fast short-term reproducibility.
- The example implementation has been tested in several research publications including the present one.
%%CONCLUSION
We conclude that requiring longevity from solutions is realistic.
We discuss the benefits of these criteria for scientific progress.