From 1d281bffd44fbe3ff43439b3ab3357953f523728 Mon Sep 17 00:00:00 2001 From: Boud Roukema Date: Sun, 19 Apr 2020 17:30:14 +0200 Subject: Principles - P5 History and temporal provenance Reduction by 5 words. The term "exploratory research" is intended in the specific sense listed at en.Wikipedia: https://en.wikipedia.org/wiki/Exploratory_research to distinguish it from hypothesis testing. The final phases of clinical (medical) research, for example, to test whether a candidate SARS-CoV-2 vaccine is (i) effective and (ii) safe in homo sapiens, cannot accept the exploratory methods that are acceptable in astronomy, or in other exploratory research (which is acceptable in the early stages of medical research). Clinical trial registration is aimed at *preventing* scientists from modifying their methods in a given project: https://en.wikipedia.org/wiki/Clinical_trial_registration --- paper.tex | 6 +++--- 1 file 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. -- cgit v1.2.1