Tech editor inputs

Author: tmdelellis

.latexmkrc

@@ -0,0 +1,15 @@
+add_cus_dep('glo', 'gls', 0, 'makeglo2gls');
+sub makeglo2gls {
+    system("makeindex -s '$_[0]'.ist -t '$_[0]'.glg -o '$_[0]'.gls '$_[0]'.glo");
+}
+
+add_cus_dep('acn', 'acr', 0, 'makeacn2acr');
+sub makeacn2acr {
+    system("makeindex -s '$_[0]'.ist -t '$_[0]'.alg -o '$_[0]'.acr '$_[0]'.acn");
+}
+
+@default_files = ('ECP-ST-CAR.tex');
+
+$pdflatex = 'pdflatex  %O  --shell-escape %S';
+
+$clean_ext = "cut glsdefs cut ist xml run.xml ucf ist acn acr alg bbl glo snm nav vrb listing lol";

Deliverables-Overview.tex

@@ -1,9 +1,9 @@
 \begin{wrapfigure}{r}{0.5\textwidth}
 	\begin{mdframed}
-		\large{ECP ST contributes to the HPC software ecosystem through direct product development, contributions to industry and \textit{de facto} standards, and shaping the requirements, design and prototyping of products delivery by vendors and other third parties.}
+		\large{ECP ST contributes to the HPC software ecosystem through direct product development, contributions to industry and de facto standards, and shaping the requirements, design, and prototyping of products delivery by vendors and other third parties.}
 	\end{mdframed}
 \end{wrapfigure}
-ECP ST efforts contribute to the HPC software ecosystem in a variety of ways.  Most tangible are the contributions to software products, many of which are already widely deployed and being transformed for use with Exascale systems.  However, ECP ST contributes to industry and \textit{de facto} standards efforts.  Finally, some ECP ST efforts contribute to the upstream processes of requirements, analysis, design and prototyping that informs the implementation of vendor and other third-party software products.  While they do not receive the most attention, these upstream efforts are very impactful and low cost, without a product to support.
+ECP ST efforts contribute to the HPC software ecosystem in a variety of ways. The most tangible way was to include contributions to software products, many of which are already widely deployed and being transformed for use with exascale systems.  However, the ECP ST contributes to industry and de facto standards efforts.  Finally, some ECP ST efforts contribute to the upstream processes of requirements, analysis, design, and prototyping that inform the implementation of vendor and other third-party software products.  Although they do not receive the most attention, these upstream efforts are very impactful and low cost without a product to support.
 
 %\begin{figure}[htb]
 %	\begin{center}

Design.tex

@@ -1,21 +1,22 @@
 \subsection{Contributions to External Software Products}\label{subsection:external-contributions}
-While much of ECP ST efforts and focus are on the product that we develop and support, it is important to note that some of our important work, and certainly some of our most sustainable and highly leveraged work, is done by providing requirements, analysis, design and prototype capabilities for vendor and other third party software.  Many software studies have shown that 70 to 80\% of the cost of a successful software product goes into post-delivery maintenance. Our effort summarized in Table~\ref{table:externalproducts} expressly eliminate this large cost for DOE because the product is developed and supported outside of DOE.
+Although many ECP ST efforts focus on the product that it will develop and support, some of the important work---and certainly some of the most sustainable and highly leveraged work---is done by providing requirements, analysis, design, and prototype capabilities to vendor and other third-party software.  Many software studies have shown that 70--80\% of the cost of a successful software product goes into post-delivery maintenance. The effort summarized in Table~\ref{table:externalproducts} expressly eliminates this large cost for DOE because the product is developed and supported outside DOE.
 
 
 \begin{table}
 	\begin{tabular}{|L{1.5in}|L{4in}|}\hline
 			\rowcolor{LightCyan}
 			Product & Contribution\\\hline
-			Kokkos and RAJA & ECP efforts to provide portable on-node parallel programming and execution environments have led to new features in C++ standards \\\hline
-			MPI Forum & ECP ST staff maintain several chapters of the MPI Forum, effort that require a constant involvement with the other authors, as well as participation to the online discussions related to the chapter and regular attendance of the MPI Forum face-to-face activities.\\\hline
-			Flang & ECP funds development of the new open source Fortran compiler front end called Flang. Flang provides Fortran language support for LLVM backends, in a similar way as Clang provides support for C and C++.\\\hline 
-			All \tools work & Starting in FY20, our \tools\ efforts are organized around delivering capabilities into the LLVM ecosystem.  \\\hline
-			SWIG (www.swig.org) & The ECP ST ForTrilinos efforts contributes the capability to generate automatic Fortran bindings from C++ code.\\\hline
-			TotalView debugger & ECP ST staff are engaged in co-design of OMPD, the new debugging interface for OpenMP programs, along with RogueWave engineers. This effort helps RogueWave improve their main debugging product, TotalView, by making it aware and compatible with recent advances in OpenMP debugging.\\\hline
-			LLVM &  An ECP ST staff member is co-leading design discussions around the parallel IR and loop-optimization infrastructure.\\\hline
-			SLATE & ECP ST math libraries efforts inform the design, implementation, and optimization of dense numerical linear algebra routines on most vendor platforms\\\hline
-			Cray MPICH MPI-IO & As part of the ExaHDF5 ECP project, the ALCF worked with Cray MPI-IO developers to merge the upstream ROMIO code into the downstream proprietary Cray MPICH MPI-IO, leveraging Cray’s extensive suite of IO performance tests and further tuning the algorithm.  Cray is currently targeting its deployment in an experimental release.\\\hline
-			OpenHPC & An ECP ST staff member serves on the OpenHPC Technical Steering Committee as a Component Development representative.\\\hline
+			Kokkos and RAJA & ECP efforts to provide portable on-node parallel programming and execution environments have led to new features in C++ standards. \\\hline
+			MPI Forum & ECP ST staff maintain several chapters of the MPI Forum, an effort that requires constant involvement with the other authors, as well as participation in the online discussions related to the chapter and regular attendance of the MPI Forum's face-to-face activities.\\\hline
+			Flang & ECP funds the development of the new open-source Fortran compiler front end called Flang. Flang provides Fortran language support for LLVM back ends in a way similar to how Clang provides support for C and C++.\\\hline 
+			All \tools work & Starting in FY20, the \tools\ efforts are organized around delivering capabilities into the LLVM ecosystem.  \\\hline
+			SWIG (www.swig.org) & The ECP ST ForTrilinos efforts contribute the capability to generate automatic Fortran bindings from C++ code.\\\hline
+			TotalView debugger & ECP ST staff, along with RogueWave engineers, are engaged in the co-design of OMPD, the new debugging interface for OpenMP programs. This effort helps RogueWave improve its main debugging product, TotalView, by making it aware and compatible with recent advances in OpenMP debugging.\\\hline
+			LLVM &  An ECP ST staff member is co-leading design discussions around the parallel intermediate representation (IR) and loop-optimization infrastructure.\\\hline
+			SLATE & ECP ST Mathematical Library efforts inform the design, implementation, and optimization of dense numerical linear algebra routines on most vendor platforms.\\\hline
+			Cray MPICH MPI-IO & As part of the ExaHDF5 ECP project, the ALCF worked with Cray MPI-IO developers to merge the upstream ROMIO code into the downstream proprietary Cray MPICH MPI-IO, leveraging Cray’s extensive suite of I/O performance tests and further tuning the algorithm.  Cray is currently targeting its deployment in an experimental release.\\\hline
+			OpenHPC & An ECP ST staff member serves on the OpenHPC Technical Steering Committee as a component development representative.\\\hline
 		\end{tabular}
-		\caption{\label{table:externalproducts} External products to which ECP ST activities contribute.  Participation in requirements, analysis, design and prototyping activities for third-party products is some of the most effective software work we can do.}
+		\centering
+		\caption{\label{table:externalproducts} External products to which ECP ST activities contribute.  Participation in requirements, analysis, design, and prototyping activities for third-party products is some of the most effective software work that can be done.}
 	\end{table}

ECP-ST-CAR.tex

@@ -5,6 +5,8 @@
 \usepackage{subfig}
 \usepackage{xcolor,colortbl}
 \usepackage{array}
+\usepackage{float} %added to wrangle tables and figures
+\usepackage{todonotes} %added todonotes for hardcopy notes and to span repos -STC
 \newcolumntype{L}[1]{>{\raggedright\let\newline\\\arraybackslash\hspace{0pt}}m{#1}}
 \definecolor{Gray}{gray}{0.85}
 \definecolor{LightCyan}{rgb}{0.88,1,1}
@@ -22,7 +24,7 @@
 \newcommand{\tools}{Development Tools}
 \newcommand{\mathlibs}{Mathematical Libraries}
 \newcommand{\dataviz}{Data \& Visualization}
-\newcommand{\ecosystem}{SW Ecosystem \& Delivery}
+\newcommand{\ecosystem}{Software Ecosystem \& Delivery} %changed SW to ``software'' per Julia.
 \newcommand{\nnsa}{NNSA ST}
 \newcommand{\stid}[1]{{\texttt{WBS 2.3.{#1}}}}
 \newcommand{\zfp}{\textsc{zfp}}
@@ -61,7 +63,7 @@
 \title{ECP Software Technology Capability Assessment Report--Internal}
 \fi
 %\date{\today}
-\date{November 19, 2020}
+\date{November 19, 2020 \todo[inline]{Update date}}
 %\wbs{2.3}
 \ifpublic
 \id{ECP-RPT-ST-0002-2020--Public}
@@ -140,13 +142,14 @@ \section{ECP ST Deliverables}\label{sect:deliverables}
 \section{ECP ST Technical Areas}\label{sect:project-summaries}
 %\section{ECP ST Project Summaries}\label{sect:project-summaries}
 
-ECP ST is composed of six Level-3 Technical Areas (see Figure~\ref{fig:l3-overview}).  In this section of the ECP ST Capabilities Assessment Report we provide an overview of each Level-3 Technical Area and two-page summaries of each funded project within the technical area.  For each L3 area, we discuss scope and requirements, assumptions and feasibility, objectives, plans, risks and mitigations and future trends.  For each Level-4 subproject, we provide a project overview and summarizes the key challenges, solution strategy, recent progress and next steps for the project.
+ECP ST is composed of six L3 technical areas (Figure~\ref{fig:l3-overview}).  This section of the report provides an overview of each L3 technical area and two-page summaries of each funded project within the technical area.  For each L3 area, the report discusses scope and requirements, assumptions and feasibility, objectives, plans, risks and mitigations, and future trends.  For each L4 subproject, a project overview is provided and the key challenges, solution strategy, recent progress, and next steps for the project are summarized.
 \
-\begin{figure}
+\begin{figure}[H]
 	\centering
 	\fbox{\includegraphics[width=0.9\linewidth]{L3-Overview}}
-	\caption{ECP ST is composed of 6 Level-3 Technical Areas.  The first four areas are organized around functionality development themes.  The fifth is focused on technology for packaging and delivery of capabilities.  The sixth is organized around per-lab open source development at the three DOE NNSA laboratories, LANL, LLNL and SNL.  }
+	\caption{ECP ST is composed of six L3 technical areas.  The first four areas are organized around functionality development themes.  The fifth is focused on technology for packaging and delivering capabilities.  The sixth is organized around per-lab open-source development at the three DOE NNSA laboratories: LANL, LLNL, and SNL.  }
 	\label{fig:l3-overview}
+	\todo[inline]{Please add a higher resolution version of this figure without the spell check underlines.}
 \end{figure}
 
 \newpage
@@ -274,7 +277,7 @@ \section{ECP ST Technical Areas}\label{sect:project-summaries}
 
 \section{Conclusion}
 
-ECP ST is providing a collection of essential software capabilities necessary for successful results from Exascale computing platforms, while also delivery a suite of products that can be sustained into the future.  This Capabilities Assessment Report and subsequent versions will provide a periodic summary of capabilities, plans, and challenges as the Exascale Computing Project proceeds.
+ECP ST is providing a collection of essential software capabilities necessary for successful results from Exascale computing platforms, while also delivery a suite of products that can be sustained into the future.  This Capabilities Assessment Report and subsequent versions will provide a periodic summary of capabilities, plans, and challenges as the ECP proceeds.
 %%---------------------------------------------------------------------------%%
 \newpage
 \section*{Acknowledgments}