<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:Helvetica;
panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
{font-family:Helvetica;
panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>This sounds a lot like the focus of the SWP4XS workshop taking place in January. How is the goal for this document not basically the scope of the workshop? I would guess the workshop will have a broader scope however.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>-Ross<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><div style='border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt'><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> petsc-trilinos-discussion-bounces@lists.mcs.anl.gov [mailto:petsc-trilinos-discussion-bounces@lists.mcs.anl.gov] <b>On Behalf Of </b>Lois Curfman McInnes<br><b>Sent:</b> Monday, November 25, 2013 5:44 PM<br><b>To:</b> Heroux, Michael A<br><b>Cc:</b> Pawlowski, Roger P; petsc-trilinos-discussion@lists.mcs.anl.gov<br><b>Subject:</b> Re: [Petsc-trilinos-discussion] Status update, summary remarks<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal><o:p> </o:p></p></div><p class=MsoNormal>My take-aways from today's chat with Thomas:<o:p></o:p></p><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>The main deliverable that ASCR wants from us in this current project is a (short) document that provides a long-term vision for interoperable use of a variety of high-performance scientific software. ASCR's primary concern is for us to develop a document that could be used as a starting point for engaging the broader DOE/HPC community in determining approach that would enable the combined use of lots of different HPC software over the long term. To get started, Mike and I will iterate with Thomas to come up with a set of basic requirements/principles at a sufficiently abstract level to help nail down the scope more specifically. And then we can further evolve this and all contribute to fleshing out long-term vision ideas.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>The recent discussions about concrete issues in the combined use of PETSc and Trilinos are indeed a valuable exchange of information --- useful for at a practical level for existing apps and future plans. However, tackling current interoperability challenges in existing codes and other near-term issues is not ASCR's priority in this particular assignment (though of course those issues inform the vision -- and we might want to pursue that to some extent as a separate activity outside the scope of the longer-term vision project).<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Best,<o:p></o:p></p></div><div><p class=MsoNormal>Lois<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p><div><div><p class=MsoNormal>On Nov 25, 2013, at 11:43 AM, "Heroux, Michael A" <<a href="mailto:maherou@sandia.gov">maherou@sandia.gov</a>> wrote:<o:p></o:p></p></div><p class=MsoNormal><br><br><o:p></o:p></p><p class=MsoNormal><span style='font-size:13.5pt;font-family:"Helvetica","sans-serif"'>Lois McInnes and I are talking with Thomas Ndousse-Fetter today to see if<br>we can get a better sense of what he wants from these discussions. He has<br>some app teams (unnamed) who are apparently driving the request for easier<br>access to DOE library capabilities. Lois and I are arguing that we need<br>direct access to these people in order to make sure we are focusing on the<br>right issues.</span><o:p></o:p></p></div><p class=MsoNormal><o:p> </o:p></p></div></div></div></body></html>