aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorBoud Roukema <boud@cosmo.torun.pl>2020-04-22 19:09:49 +0200
committerBoud Roukema <boud@cosmo.torun.pl>2020-04-22 19:09:49 +0200
commitc9d64927224fd627c7a3459c8eaaddc34574090a (patch)
treef61fa05739e604aa93a3080c4ac77946fb123df4
parent085141f5359926c54b5ad524b24b0c1878226738 (diff)
4.3.3 Project analysis - verification
Reduction by 4 words. Minor rewording; removal of "Note that" and "simply" (the opposite of "complicatedly"). If a checksum is simple for a given user, then s/he already knows that; if s/he doesn't yet know what a checksum is, then stating that it's simple doesn't help very much. :)
-rw-r--r--paper.tex12
1 files changed, 6 insertions, 6 deletions
diff --git a/paper.tex b/paper.tex
index 77ac564..16c3eb6 100644
--- a/paper.tex
+++ b/paper.tex
@@ -517,12 +517,12 @@ These \LaTeX{} macro files form the core skeleton of a Maneage project: as shown
\subsubsection{Verification of outputs (\inlinecode{verify.mk})}
\label{sec:outputverification}
-Before the modular \LaTeX{} macro files of Section \ref{sec:valuesintext} are merged into the single \inlinecode{project.tex} file, they need to pass through the verification filter, which is another core principle of Maneage (\ref{principle:verify}).
-Note that simply confirming the checksum of the final PDF, or figures and datasets is not generally possible: many tools write the creation date into the produced files.
-To avoid such cases the raw data must be verified, independent of metadata like date.
-Some standards include such features, for example, the \inlinecode{DATASUM} keyword in the FITS format \citep{pence10}.
-To facilitate output verification, Maneage has the \inlinecode{verify.mk} subMakefile that is the boundary between the analytical phase of the paper, and the production of the report (see Figure \ref{fig:datalineage}).
-It has some tests on pre-defined formats, and other formats can easily be added.
+Before the modular \LaTeX{} macro files of Section \ref{sec:valuesintext} are merged into the single \inlinecode{project.tex} file, they need to pass through the verification filter, which implements another core principle of Maneage (\ref{principle:verify}).
+Confirming the checksum of the final PDF or of figures and datasets is not generally useful: many tools write the creation date into the produced files.
+To avoid this, the raw data must be verified independent of metadata like dates.
+Some standards include such date-independent verification features, for example, the \inlinecode{DATASUM} keyword in the FITS format \citep{pence10}.
+To facilitate output verification, Maneage has the \inlinecode{verify.mk} subMakefile that separates the analytical phase of the paper from the production of the report (see Figure \ref{fig:datalineage}).
+This file implements some tests on pre-defined formats. Other formats can easily be added.
\subsubsection{The analysis}
\label{sec:analysis}