aboutsummaryrefslogtreecommitdiff
path: root/paper.tex
diff options
context:
space:
mode:
Diffstat (limited to 'paper.tex')
-rw-r--r--paper.tex22
1 files changed, 8 insertions, 14 deletions
diff --git a/paper.tex b/paper.tex
index 45cead1..778cb19 100644
--- a/paper.tex
+++ b/paper.tex
@@ -86,7 +86,7 @@
\vspace{2.5mm}
\emph{Appendices} ---
Two comprehensive appendices that review existing solutions; available
-\ifdefined\noappendix
+\ifdefined\separatesupplement
at \href{https://arxiv.org/abs/\projectarxivid}{\texttt{arXiv:\projectarxivid}} or \href{https://doi.org/10.5281/zenodo.\projectzenodoid}{\texttt{zenodo.\projectzenodoid}}.
\else
at the end (Appendices \ref{appendix:existingtools} and \ref{appendix:existingsolutions}).
@@ -155,7 +155,7 @@ To highlight the necessity, a short review of commonly-used tools is provided be
(3) job management (like shell scripts or Make);
(4) notebooks (like Jupyter).
\new{A comprehensive review of existing tools and solutions is available in the
- \ifdefined\noappendix
+ \ifdefined\separatesupplement
\href{https://doi.org/10.5281/zenodo.\projectzenodoid}{appendices}.%
\else%
appendices (\ref{appendix:existingsolutions}).%
@@ -169,7 +169,7 @@ We will focus on Docker here because it is currently the most common.
\new{It is hypothetically possible to precisely identify the used Docker ``images'' with their checksums (or ``digest'') to re-create an identical OS image later.
However, that is rarely done.}
Usually images are imported with operating system (OS) names; e.g., \cite{mesnard20}
-\ifdefined\noappendix
+\ifdefined\separatesupplement
\new{(more examples in the \href{https://doi.org/10.5281/zenodo.\projectzenodoid}{appendices})}%
\else%
\new{(more examples: see the appendices (\ref{appendix:existingtools}))}%
@@ -332,7 +332,7 @@ Acting as a link, the macro files build the core skeleton of Maneage.
For example, during the software building phase, each software package is identified by a \LaTeX{} file, containing its official name, version and possible citation.
These are combined at the end to generate precise software \new{acknowledgement} and citation that is shown in the
\new{
- \ifdefined\noappendix
+ \ifdefined\separatesupplement
\href{https://doi.org/10.5281/zenodo.\projectzenodoid}{appendices}.%
\else%
appendices (\ref{appendix:software}).%
@@ -683,21 +683,15 @@ The Pozna\'n Supercomputing and Networking Center (PSNC) computational grant 314
-%% Appendix (only build if 'noappendix' has not been given). So in default,
-%% the appendix is built.
-\ifdefined\noappendix
+%% Appendix (only build if 'separatesupplement' has not been given): by
+%% default, the appendices are built.
+\ifdefined\separatesupplement
\else
\clearpage
\appendices
\input{tex/src/appendix-existing-tools.tex}
\input{tex/src/appendix-existing-solutions.tex}
-
-%% Mention all used software in an appendix.
-\section{Software acknowledgement}
-\label{appendix:software}
-\input{tex/build/macros/dependencies.tex}
-
-%% Bibliography of appendix
+\input{tex/src/appendix-used-software.tex}
\bibliographystyleappendix{IEEEtran_openaccess}
\bibliographyappendix{IEEEabrv,references}
\fi