aboutsummaryrefslogtreecommitdiff
path: root/paper.tex
diff options
context:
space:
mode:
authorBoud Roukema <boud@cosmo.torun.pl>2020-05-01 15:01:00 +0200
committerBoud Roukema <boud@cosmo.torun.pl>2020-05-01 15:01:00 +0200
commita6f5fcd6177b8f6319ffccddda1627f8b1dad415 (patch)
treeb0e58d645356bc4f476d1471a0b367bc972594b5 /paper.tex
parent8f0ce4a1edae4db08853c80ce9fdbc18598a0c43 (diff)
Abstract: three minor language edits
The difference between `that` and `which` is not strictly required, but it helps clarify the difference in meaning, which is important in science and software :). This is best shown by an example: * Maneage provides reproducibility, which is a good thing. The sentence would make sense if we drop `, which is a good thing.` The last part of the sentence is a comment rather than a necessary part of the sentence. * Maneage provides a quality of reproducibility that is missing from other implementations. The sentence would not quite make sense if we drop `that is ...`, since we would not know what sort of quality is provided. The fact that the quality is missing is key to the intended meaning of the sentence.
Diffstat (limited to 'paper.tex')
-rw-r--r--paper.tex8
1 files changed, 4 insertions, 4 deletions
diff --git a/paper.tex b/paper.tex
index fcd23cf..43f35c8 100644
--- a/paper.tex
+++ b/paper.tex
@@ -53,18 +53,18 @@
%% Abstract % max 250 words for CiSE
{\noindent\mpregular
%% CONTEXT
- 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.
+ Many reproducible workflow solutions have been proposed over recent decades.
+ Most use the high-level technologies that were popular when they were created, providing an immediate solution that 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 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.
+ 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
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.
- %%CONCLUSION
+ %% CONCLUSION
We conclude that requiring longevity from solutions is realistic.
We discuss the benefits of these criteria for scientific progress.