aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMohammad Akhlaghi <mohammad@akhlaghi.org>2021-06-15 15:36:49 +0100
committerMohammad Akhlaghi <mohammad@akhlaghi.org>2021-06-15 15:40:06 +0100
commit1cfb83e01b9ab6375727da5afd89bb3e744b9894 (patch)
tree50ff944e8761912bac8d66a21320cf972dd3651b
parentccce0fb9f9229d015e942b00073f39fc16130dc7 (diff)
Main body: corrected mistakenly written "bottom" --> "right"
In the old versions of this paper, the two components of Figure 1 were under each other, so we referred to them as "top" and "bottom"! However, we later put them beside each other (by shrinking the data graph), so they became "left" and "right". I just noticed that within the main body of the text, in one place, we were still mistakenly saying "bottom"! So with this commit, it has been changed to "right". Unfortunately this has gone into the final publication on CiSE, but it is important to fix such minor issues anyway (the good thing with having a Git history!), we also haven't yet put the final upload on arXiv.
-rw-r--r--paper.tex2
1 files changed, 1 insertions, 1 deletions
diff --git a/paper.tex b/paper.tex
index 4518954..c06bcce 100644
--- a/paper.tex
+++ b/paper.tex
@@ -431,7 +431,7 @@ For example, see \inlinecode{\small verify-parameter-statistically.sh}\footnote{
To further minimize complexity, the low-level implementation can be further separated from the high-level execution through configuration files.
By convention in Maneage, the subMakefiles (and the programs they call for number crunching) do not contain any fixed numbers, settings, or parameters.
Parameters are set as Make variables in ``configuration files'' (with a \inlinecode{.conf} suffix) and passed to the respective program by Make.
-For example, in Figure \ref{fig:datalineage} (bottom), \inlinecode{INPUTS.conf} contains URLs and checksums for all imported datasets, thereby enabling exact verification before usage.
+For example, in Figure \ref{fig:datalineage} (right), \inlinecode{INPUTS.conf} contains URLs and checksums for all imported datasets, thereby enabling exact verification before usage.
To illustrate this, we report that Menke et al.\cite{menke20} studied $\menkenumpapersdemocount$ papers in $\menkenumpapersdemoyear$ (which is not in their original plot).
The number \inlinecode{\menkenumpapersdemoyear} is stored in \inlinecode{demo-year.conf} and the result (\inlinecode{\menkenumpapersdemocount}) was calculated after generating \inlinecode{tools-per-year.txt}.
Both numbers are expanded as \LaTeX{} macros when creating this PDF file.