aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorzahra sharbaf <samaeh.sharbaf2@yahoo.com>2020-04-08 09:51:31 +0430
committerzahra sharbaf <samaeh.sharbaf2@yahoo.com>2020-04-08 10:00:43 +0430
commit29f1313a45910e1199d812a41d4461a8c0baa221 (patch)
tree12ed6cb92485e3fb36d1ea42aa14767b6e0a6eb3
parent0129b7368b4d7ec89ffd85b47360f581d8100da1 (diff)
Reproducibility in the abstract
Because one of the most important properties of Manaege is reproducibility. I think is it better to say something about it in the abstract, like the thing that you do in your speech. With this commit, I noted something about it in the abstract.
-rw-r--r--paper.tex9
1 files changed, 7 insertions, 2 deletions
diff --git a/paper.tex b/paper.tex
index a91e86f..f4895b0 100644
--- a/paper.tex
+++ b/paper.tex
@@ -45,8 +45,12 @@
%% Abstract
{\noindent\mpregular
- The era of big data has also ushered an era of big responsability.
- Without it, the integrity of the result will be a subject of perpetual debate.
+ The era of big data has also ushered an era of big responsability.Without it, the integrity of the result will be a subject of perpetual debate.
+\tonote{
+Because one of the most important properties of Maneage is reproducibility. I think is it better to say something about it in the abstract, like the thing that you do in your speech.
+Something like this:
+Reproducibility (as a test on sufficiently conveying the data lineage) is necessary for other scientists to study, check and build-upon each other’s work ( I got this sentence from the introduction). According to a U.S. National Science Foundation (NSF), the definition of reproducibility is “reproducibility refers to the ability of a researcher to duplicate the results of a prior study using the same materials as were used by the original investigator. That is, a second researcher might use the same raw data to build the same analysis files and implement the same statistical analysis in an attempt to yield the same results…. Reproducibility is a minimum necessary condition for a finding to be believable and informative.”(K. Bollen, J. T. Cacioppo, R. Kaplan, J. Krosnick, J. L. Olds, Social, Behavioral, and Economic Sciences Perspectives on Robust and Reliable Science (National Science Foundation, Arlington, VA, 2015)).
+}
In this paper Maneage is introduced as a low-level solution to this problem.
Maneage (management + lineage) is an executable workflow for project authors and readers in the sciences or the industry.
It is designed following principles: complete (e.g., not requiring anything beyond a POSIX-compatible system, administrator previlages or a network connection), modular, fully in plain-text, minimal complexity in design, verifiable inputs and outputs, temporal lineage/provenance, and free software (in scientific applications).
@@ -149,6 +153,7 @@ However, this is not a practical solution because software updates are necessary
Generally, software is not a secular component of projects, where one software can easily be swapped with another.
Projects are built around specific software technologies, and research in software methods and implementations is itself a vibrant research topic in many domains \citep{dicosmo19}.
+
This paper introduces Maneage as a solution to these important issues.
Section \ref{sec:definitions} defines the necessay concepts and terminology used in this paper leading to a discussion of the necessary guiding principles in Section \ref{sec:principles}.
Section \ref{sec:maneage} introduces the implementation of Maneage, going into lower-level details in some cases.