main.tex

%%
%% This is file `sample-acmsmall.tex',
%% generated with the docstrip utility.
%%
%% The original source files were:
%%
%% samples.dtx  (with options: `acmsmall')
%% 
%% IMPORTANT NOTICE:
%% 
%% For the copyright see the source file.
%% 
%% Any modified versions of this file must be renamed
%% with new filenames distinct from sample-acmsmall.tex.
%% 
%% For distribution of the original source see the terms
%% for copying and modification in the file samples.dtx.
%% 
%% This generated file may be distributed as long as the
%% original source files, as listed above, are part of the
%% same distribution. (The sources need not necessarily be
%% in the same archive or directory.)
%%
%%
%% Commands for TeXCount
%TC:macro \cite [option:text,text]
%TC:macro \citep [option:text,text]
%TC:macro \citet [option:text,text]
%TC:envir table 0 1
%TC:envir table* 0 1
%TC:envir tabular [ignore] word
%TC:envir displaymath 0 word
%TC:envir math 0 word
%TC:envir comment 0 0
%%
%%
%% The first command in your LaTeX source must be the \documentclass
%% command.
%%
%% For submission and review of your manuscript please change the
%% command to \documentclass[manuscript, screen, review]{acmart}.
%%
%% When submitting camera ready or to TAPS, please change the command
%% to \documentclass[sigconf]{acmart} or whichever template is required
%% for your publication.
%%
%%
\documentclass[acmsmall]{acmart}

%%
%% \BibTeX command to typeset BibTeX logo in the docs
\AtBeginDocument{%
  \providecommand\BibTeX{{%
    Bib\TeX}}}

%% Rights management information.  This information is sent to you
%% when you complete the rights form.  These commands have SAMPLE
%% values in them; it is your responsibility as an author to replace
%% the commands and values with those provided to you when you
%% complete the rights form.
\setcopyright{acmcopyright}
\copyrightyear{2023}
\acmYear{2023}
\acmDOI{XXXXXXX.XXXXXXX}

\usepackage{color}

\newcommand{\todo}[1]{\textcolor{orange}{TODO: #1}}
\DeclareMathOperator*{\argmin}{\arg\!\min}


\usepackage{listings}
\lstset{language=C}


%%
%% These commands are for a JOURNAL article.
\acmJournal{JACM}
\acmVolume{37}
\acmNumber{4}
\acmArticle{111}
\acmMonth{8}

%%
%% Submission ID.
%% Use this when submitting an article to a sponsored event. You'll
%% receive a unique submission ID from the organizers
%% of the event, and this ID should be used as the parameter to this command.
%%\acmSubmissionID{123-A56-BU3}

%%
%% For managing citations, it is recommended to use bibliography
%% files in BibTeX format.
%%
%% You can then either use BibTeX with the ACM-Reference-Format style,
%% or BibLaTeX with the acmnumeric or acmauthoryear sytles, that include
%% support for advanced citation of software artefact from the
%% biblatex-software package, also separately available on CTAN.
%%
%% Look at the sample-*-biblatex.tex files for templates showcasing
%% the biblatex styles.
%%

%%
%% The majority of ACM publications use numbered citations and
%% references.  The command \citestyle{authoryear} switches to the
%% "author year" style.
%%


%%
%% end of the preamble, start of the body of the document source.
\begin{document}

%%
%% The "title" command has an optional parameter,
%% allowing the author to define a "short title" to be used in page headers.
\title{An Update to the Overview of the Trilinos Library}

%%
%% The "author" command and its associated commands are used to define
%% the authors and their affiliations.
%% Of note is the shared affiliation of the first two authors, and the
%% "authornote" and "authornotemark" commands
%% used to denote shared contribution to the research.
\author{Sivasankaran Rajamanickam}
\email{srajama@sandia.gov}
\orcid{1234-5678-9012}
\author{Michael Heroux}
\email{maherou@sandia.gov}
\author{Kim Liegeois}
\email{knliege@sandia.gov}
\orcid{0000-0002-1182-4078}
\author{Roger Pawlowski}
\email{rppawlo@sandia.gov}
\author{Eric Phipps}
\email{etphipp@sandia.gov}
\author{Mauro Perego}
\email{mperego@sandia.gov}
\author{Luc Berger-Vergiat}
\email{lberge@sandia.gov}
\orcid{0000-0001-5550-3527}
\author{Christopher M. Siefert}
\email{csiefer@sandia.gov}
\author{Christian Glusa}
\email{caglusa@sandia.gov}
\author{Jonathan Hu}
\email{jhu@sandia.gov}
\author{Graham Harper}
\email{gbharpe@sandia.gov}
\author{Paul Kuberry}
\email{pakuber@sandia.gov}
\orcid{0000-0002-2426-4591}
\author{Curtis C. Ober}
\email{ccober@sandia.gov}
\author{Heidi K. Thornquist}
\email{hkthorn@sandia.gov}
\author{James M. Willenbring}
\email{jmwille@sandia.gov}
\orcid{0000-0002-0418-9264}
\author{Roscoe A. Bartlett}
\email{rabartl@sandia.gov}
\orcid{0000-0002-3831-8060}
\author{Denis Ridzal}
\email{dridzal@sandia.gov}
\author{Drew P. Kouri}
\email{dpkouri@sandia.gov}
\author{Ichitaro Yamazaki}
\email{iyamaza@sandia.gov}
\author{Nathan V. Roberts}
\email{nvrober@sandia.gov}
\orcid{0000-0003-1536-0749}
\author{Michael M. Wolf}
\email{mmwolf@sandia.gov}

\author{New Sandia Author}
\email{TBD@sandia.gov}

\affiliation{%
  \institution{Sandia National Laboratories}
  \streetaddress{1515, Eubank Blvd SE}
  \city{Albuquerque}
  \state{New Mexico}
  \country{USA}
  \postcode{87123}
}

\author{Alexander Heinlein}
\affiliation{%
  \institution{Delft University of Technology}
  \streetaddress{Mekelweg 4}
  \postcode{2628CD}
  \city{Delft}
  \country{Netherlands}
}
\email{a.heinlein@tudelft.nl}
\orcid{0000-0003-1578-8104}

\author{Matthias Mayr}
\affiliation{%
  \institution{University of the Bundeswehr Munich}
  \streetaddress{Werner-Heisenberg-Weg 39}
  \city{85577 Neubiberg}
  \country{Germany}}
\email{matthias.mayr@unibw.de}
\orcid{0000-0002-2780-1233}

\author{New Non Sandia Author}
\affiliation{%
  \institution{TBD}
  \city{TBD}
  \country{TBD}
}





%%
%% By default, the full list of authors will be used in the page
%% headers. Often, this list is too long, and will overlap
%% other information printed in the page headers. This command allows
%% the author to define a more concise list
%% of authors' names for this purpose.
\renewcommand{\shortauthors}{Developer et al.}

%%
%% The abstract is a short summary of the work to be presented in the
%% article.
\begin{abstract}
Trilinos is a community-developed, open source software framework that facilitates building large-scale, complex, multiscale, multiphysics engineering and scientific problems.
Since the Trilinos framework has undergone substantial changes to support new applications and new hardware architectures,
this document is an update to ``An Overview of the Trilinos project'' by Heroux et al. (ACM Transactions on Mathematical Software, 31(3):397–423, 2005).
It describes the design of Trilinos, introduces its new organization in product areas,
and highlights established and new features available in Trilinos.
Particular focus is put on the modernized software stack based on the Kokkos ecosystem to deliver performance portability across heterogeneous hardware architectures.
Notes on the Trilinos community and possibilities to contribute aim at onboarding interested users.
\end{abstract}

%%
%% The code below is generated by the tool at http://dl.acm.org/ccs.cfm.
%% Please copy and paste the code instead of the example below.
%%
%\begin{CCSXML}
%<ccs2012>
% <concept>
%  <concept_id>10010520.10010553.10010562</concept_id>
%  <concept_desc>Computer systems organization~Embedded systems</concept_desc>
%  <concept_significance>500</concept_significance>
% </concept>
% <concept>
%  <concept_id>10010520.10010575.10010755</concept_id>
%  <concept_desc>Computer systems organization~Redundancy</concept_desc>
%  <concept_significance>300</concept_significance>
% </concept>
% <concept>
%  <concept_id>10010520.10010553.10010554</concept_id>
%  <concept_desc>Computer systems organization~Robotics</concept_desc>
%  <concept_significance>100</concept_significance>
% </concept>
% <concept>
%  <concept_id>10003033.10003083.10003095</concept_id>
%  <concept_desc>Networks~Network reliability</concept_desc>
%  <concept_significance>100</concept_significance>
% </concept>
%</ccs2012>
%\end{CCSXML}

%\ccsdesc[500]{Computer systems organization~Embedded systems}
%\ccsdesc[300]{Computer systems organization~Redundancy}
%\ccsdesc{Computer systems organization~Robotics}
%\ccsdesc[100]{Networks~Network reliability}

%%
%% Keywords. The author(s) should pick words that accurately describe
%% the work being presented. Separate the keywords with commas.
\keywords{Scientific Software Frameworks}

\received{15 April 2023}
%\received[revised]{12 March 2009}
%\received[accepted]{5 June 2009}

%%
%% This command processes the author and affiliation and title
%% information and builds the first part of the formatted document.
\maketitle

\section{Introduction}
\input{introduction}

\section{Trilinos Core}
\label{sec:data_services}
\input{data_services}

\section{Linear Solvers and Preconditioners}
\label{sec:lin_solve}
\input{linear_solvers}

\section{Nonlinear Solvers and Analysis Tools}
\label{sec:nonlin_solve}
\input{nonlinear_solvers}

\section{Discretizations}
\label{sec:discretization}
\input{discretization}

\section{Trilinos Framework}
\label{sec:framework}
\input{framework}

\section{Trilinos Community}
\label{sec:community}
\input{community}


\section{Discussion}


\section{Acknowledgment}


%%
%% The next two lines define the bibliography style to be used, and
%% the bibliography file.
\bibliographystyle{ACM-Reference-Format}
\bibliography{bibliography}

\end{document}
\endinput
%%
%% End of file `sample-acmsmall.tex'.