aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
-rw-r--r--paper.tex6
1 files changed, 3 insertions, 3 deletions
diff --git a/paper.tex b/paper.tex
index 41a856c..b1ebb9d 100644
--- a/paper.tex
+++ b/paper.tex
@@ -265,12 +265,12 @@ Automatic verification of inputs is commonly implemented, but the outputs are mu
No project is done in a single/first attempt.
Projects evolve as they are being completed.
It is natural that earlier phases of a project are redesigned/optimized only after later phases have been completed.
-This is often seen in scientific papers, with statements like ``\emph{we [first] tried method [or parameter] X, but Y is used here because it showed to have better precision [or less bias, or etc]}''.
+This is often seen in exploratory research papers, with statements like ``\emph{we [first] tried method [or parameter] X, but Y is used here because it gave lower random error}''.
A project's ``history'' is thus as scientifically relevant as the final, or published version.
-\emph{Comparison with existing:} The systems above that are implemented with version control usually support this principle.
+\emph{Comparison with existing:} The solutions above that are implemented with version control usually support this principle.
However, because the systems as a whole are rarely complete (see \ref{principle:complete}), their histories are also incomplete.
-IPOL fails here because only the final snapshot is published.
+IPOL fails here, because only the final snapshot is published.
\item \label{principle:scalable}\textbf{Scalability:}
A project should be scalable to arbitrarily large and/or complex projects.