aboutsummaryrefslogtreecommitdiff
path: root/paper.tex
diff options
context:
space:
mode:
authorMohammad Akhlaghi <mohammad@akhlaghi.org>2020-06-04 04:09:21 +0100
committerMohammad Akhlaghi <mohammad@akhlaghi.org>2020-06-04 04:09:21 +0100
commite3bdc607a7fca8ebd876e1fa6002e679ad32f2c4 (patch)
treebac9de2e3f4f13db09ece9228674a1d546b7f62f /paper.tex
parentd85dfdf8d7b0f2769d824fd4994eccec55db963a (diff)
Verification activated, README added, Proper metadata in plot data
All the steps following the to-be-added (in 'README-hacking.md') publication checklist prior to the final check from new clone have been added: - 'README.md' file has been set. - "Reproducible supplement" was added just above the keywords, pointing to Zenodo. - A link to the to-be-uploaded data underlying the plot was added in the caption of the tools-per-year plot. - A new meta-data configuration file was added to store basic project metadata to be used throughout the project. This will later be taken into Maneage. For examle the project title is now stored here and written into the paper's LaTeX source and output datasets automatically. - Verification was activated and plot's data and LaTeX macro files are now automatically verified. - A complete metadata was added for the data underlying the plot. - A generic function was added in 'initialize.mk' that will automatically write project info and copyright in all plain-text outputs.
Diffstat (limited to 'paper.tex')
-rw-r--r--paper.tex10
1 files changed, 8 insertions, 2 deletions
diff --git a/paper.tex b/paper.tex
index 685849f..fff0e41 100644
--- a/paper.tex
+++ b/paper.tex
@@ -27,7 +27,7 @@
\input{tex/src/preamble-pgfplots.tex}
%% Title and author names.
-\title{Towards Long-term and Archivable Reproducibility}
+\title{\projecttitle}
\author{
Mohammad~Akhlaghi,
Ra\'ul Infante-Sainz,
@@ -70,9 +70,12 @@
%% CONCLUSION
We show that requiring longevity of a reproducible workflow solution is realistic, and discuss the benefits of the criteria for scientific progress, but also immediate benefits for short-term reproducibility.
This paper has itself been written in Maneage, with snapshot \projectversion.
+
+ \vspace{3mm}
+ \emph{Reproducible supplement} --- \href{https://doi.org/10.5281/zenodo.3872248}{\texttt{Zenodo.3872248}}.
\end{abstract}
-% Note that keywords are not normally used for peerreview papers.
+% Note that keywords are not normally used for peer-review papers.
\begin{IEEEkeywords}
Data Lineage, Provenance, Reproducibility, Scientific Pipelines, Workflows
\end{IEEEkeywords}
@@ -82,6 +85,8 @@ Data Lineage, Provenance, Reproducibility, Scientific Pipelines, Workflows
+
+
% For peer review papers, you can put extra information on the cover
% page as needed:
% \ifCLASSOPTIONpeerreview
@@ -293,6 +298,7 @@ Figure \ref{fig:datalineage} (bottom) is the data lineage graph that produced it
For example, \inlinecode{paper.pdf} depends on \inlinecode{project.tex} (in the build directory; generated automatically) and \inlinecode{paper.tex} (in the source directory; written manually).
The solid arrows and full-opacity built boxes correspond to this paper.
The dashed arrows and low-opacity built boxes show the scalability by adding hypothetical steps to the project.
+ The underlying data of the top plot is available at \href{https://zenodo.org/record/3872248/files/tools-per-year.txt}{zenodo.3872248/tools-per-year.txt}.
}
\end{figure*}