diff options
| -rw-r--r-- | paper.tex | 6 |
1 files changed, 3 insertions, 3 deletions
@@ -419,7 +419,7 @@ Therefore, each project has to identify its high-level software in the \inlineco Maneage contains the full list of built software for each project, their versions and their configuration options, but this information is buried deep into each project's source. Therefore Maneage also prints a distilled fraction of this information in the project's final report, blended into the narrative, as seen in the Acknowledgments of this paper. Furthermore, when the software is associated with a published paper, that paper's Bib\TeX{} entry is also added to the final report and is duly cited with the software's name and version. -This paper uses basic tools that don't have a paper, for software citation examples see \citet{akhlaghi19} and \citet{infante20}. +This paper uses basic tools that do not have a paper, for software citation examples see \citet{akhlaghi19} and \citet{infante20}. This is particularly important in the case for research software, where citation is critical to justify continued development. One notable example that nicely highlights this issue is GNU Parallel \citep{tange18}: every time it is run, it prints the citation information before it starts. @@ -453,7 +453,7 @@ Maneage is thus designed to encourage and facilitate modularity by distributing In the rest of this paper these modular, or lower-level, Makefiles will be called \emph{subMakefiles}. When run with the \inlinecode{make} argument, the \inlinecode{project} script (Section \ref{sec:maneage}), calls \inlinecode{top-make.mk} which loads the subMakefiles with a certain order. They are loaded using Make's \inlinecode{include} feature (so Make sees everything as one file in one instance of Make). -By default Maneage doesn't use recursion (where one instance of Make, calls another instance of Make within itself) to comply with minimal complexity principle (\ref{principle:complexity}) and keep the code's logic clear and simple. +By default Maneage does not use recursion (where one instance of Make, calls another instance of Make within itself) to comply with minimal complexity principle (\ref{principle:complexity}) and keep the code's logic clear and simple. All the analysis Makefiles are in \inlinecode{re\-produce\-/anal\-ysis\-/make} (see Figure \ref{fig:files}) and Figure \ref{fig:datalineage} shows their inter-relation with the target/built files that they manage. \begin{figure}[t] @@ -549,7 +549,7 @@ Note that their location after the standard starting subMakefiles (initializatio To enhance the original plot, Figure \ref{fig:toolsperyear} also shows the number of papers that were studied each year. Furthermore, its horizontal axis shows the full range of the data (starting from \menkefirstyear), while the original starts from 1997. -This was probably because they didn't have sufficient data for older papers, for example, in \menkenumpapersdemoyear, they only had \menkenumpapersdemocount{} papers. +This was probably because they did not have sufficient data for older papers, for example, in \menkenumpapersdemoyear, they only had \menkenumpapersdemocount{} papers. Note that both the numbers of the previous sentence (\menkenumpapersdemoyear{} and \menkenumpapersdemocount), and the dataset's oldest year (mentioned above: \menkefirstyear) are automatically generated \LaTeX{} macros, see Section \ref{sec:valuesintext}. They are \emph{not} typeset manually in this narrative explanation. This step (generating the macros) is shown schematically in Figure \ref{fig:datalineage} with the arrow from \inlinecode{tools-per-year.txt} to \inlinecode{demo-plot.tex}. |