Update current progress

ulrikeyang · Nov 25, 2019 · e6f3e79 · e6f3e79
1 parent 4e34936
commit e6f3e79
Show file tree

Hide file tree

Showing 12 changed files with 8 additions and 7 deletions.
diff --git a/ConfluenceProductDictionaryExample.png b/ConfluenceProductDictionaryExample.png
diff --git a/Deliverables-Overview.tex b/Deliverables-Overview.tex
@@ -9,6 +9,6 @@
 	\begin{center}
 		\includegraphics[width=0.7\textwidth]{ProductsOverview}
 
-		\caption{\label{fig:productsoverview}{\small{The 54 ECP ST Projects contribute to 89 unique products.   ECP ST products are delivered to users via many mechanisms. Provides experience we can leverage across projects.  Building via Spack is required for participating in ECP ST releases: 48\% of products already support Spack.   24\% have Spack support in progress.  Use of Spack and the ECP ST SDKs will greatly improve builds from source. 81 of 89 packages support users via source builds.}}}
+		\caption{\label{fig:productsoverview}{\small{The 33 ECP ST Projects contribute to 70 user-facing software product suites.   ECP ST products are delivered to users via many mechanisms. Provides experience we can leverage across projects.  Building via Spack is required for participating in ECP ST releases: 50 of the 70 ST product suites are available in the Extreme-scale Scientific Software Stack (E4S) V1.0, release in November 2019.}}}
 	\end{center}
 \end{figure}
diff --git a/DependencyDashboard-EditPanel.png b/DependencyDashboard-EditPanel.png
diff --git a/Design.tex b/Design.tex
@@ -1,19 +1,21 @@
 \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 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.
+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.
 
 
 \begin{table}
 	\begin{tabular}{|L{1.5in}|L{4in}|}\hline
 			\rowcolor{LightCyan}
 			Product & Contribution\\\hline
-			MAGMA & ECP ST math libraries efforts inform the design, implementation, and optimization of numerical linear algebra routines on NVIDIA GPUs\\\hline
-			Compilers and runtime & The Validation and Verification Suite (on-going effort) for the SOLLVE project has helped uncover bugs in OpenMP implementations provided by Cray, LLVM and XL.\\\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
-			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. An ECP ST staff member belongs to several working group related to scalability and resilience where, in addition to the discussions, implements proof-of-concept features in OpenMPI.\\\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 it’s 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
-			LLVM &  An ECP ST staff member is co-leading design discussions around the parallel IR and loop-optimization infrastructure.\\\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.}
 	\end{table}
diff --git a/E4S-AWS-public-image.png b/E4S-AWS-public-image.png
diff --git a/E4S-Build-Cache-Binaries.png b/E4S-Build-Cache-Binaries.png
diff --git a/E4S-Summary.png b/E4S-Summary.png
diff --git a/PETSc-TAO-Dependencies.png b/PETSc-TAO-Dependencies.png
diff --git a/ProductDictionaryOverview.png b/ProductDictionaryOverview.png
diff --git a/ProductDocumentationGitHub.png b/ProductDocumentationGitHub.png
diff --git a/ProductDocumentationGoals.png b/ProductDocumentationGoals.png
diff --git a/Products.tex b/Products.tex
@@ -65,7 +65,6 @@ \subsection{ECP ST Products}\label{subsect:products}
 \end{table}
 
 
-
 \begin{table}
 \begin{tabular}{|l|l|l|}\hline
 		\rowcolor{LightCyan}