<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">
<div dir="auto" style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">
<div class="" style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);">Chapter Committees / Chairs --</div>
<div class="" style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);"><br class="">
</div>
<div class="" style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);">We need Chapter Committees to review their chapters in three sets of upcoming document-wide changes that are slated to be merged "soon".<br class="">
<br class="">
After you complete a review, please put an "X" in the corresponding row/column for your chapter and the specified PR <a href="https://docs.google.com/spreadsheets/d/1qPAREYgeuSCMtU-EQniDilrHIYb8W0-f6Qzjp-UtnH8/edit?folder=1_LOwR_QeX_bwIe_eptiy0OxWaOvPQ8W8#gid=0" class="">in
this Google spreadsheet</a> (including an un-numbered chapter for partitioned communication). This will let us track what has been done / what still needs to be done.<br class="">
<br class="">
</div>
<div class="" style="caret-color: rgb(0, 0, 0);"><span class=""><b class=""><u class=""><font class="" color="#ff8700">FIRST SET</font><br class="">
</u></b></span><br class="">
<font color="#000000" class="">Bill Gropp (the MPI Standard document Editor) has two PRs with "ticket 0" changes. However, the changes are pervasive and touch a LOT of the document. We therefore need Chapter Committees to review their chapters in the following
two PRs:</font><br class="">
<br class="">
<font color="#000000" class="">1a. "Ticket 0 changes for MPI-4.x"</font><br class="">
<font color="#000000" style="caret-color: rgb(255, 255, 255);" class=""> </font><a href="https://github.com/mpi-forum/mpi-standard/pull/151" style="caret-color: rgb(255, 255, 255);" class=""><font color="#429cff" class="">https://github.com/mpi-forum/mpi-standard/pull/151</font></a><br class="" style="caret-color: rgb(255, 255, 255); color: rgb(0, 0, 0);">
<font color="#000000" class="">1b. "Uniform style for Fortran code"</font><br class="">
<font color="#000000" style="caret-color: rgb(255, 255, 255);" class=""> </font><font color="#429cff" style="caret-color: rgb(255, 255, 255);" class=""><a href="https://github.com/mpi-forum/mpi-standard/pull/145" class="" style="caret-color: rgb(255, 255, 255);">https://github.com/mpi-forum/mpi-standard/pull/145</a></font></div>
<div class="" style="caret-color: rgb(0, 0, 0);"><font color="#429cff" class=""><br class="" style="caret-color: rgb(255, 255, 255);">
</font><font class="" style="font-size: 36px;" color="#ff1f00">Deadline: Jan 7, 2020</font></div>
<div class="" style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);"> (Yes, that's an early deadline, but we need time to merge these PRs and fix conflicts with the second set)</div>
<div class="" style="caret-color: rgb(0, 0, 0);"><br class="">
<b class=""><u class=""><font class="" color="#ff8700">SECOND SET</font><br class="">
</u></b><br class="">
<font color="#000000" class="">The Pythonization group has Pythonized the bindings in the entire document. We've completed a first correctness pass over the work, but we need more eyes to compare the end result of our work to the (non-Pythonized) head of the
mpi-4.x branch.</font></div>
<div class="" style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);"><br class="">
</div>
<div class="" style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);">To be clear: this review does not include Embiggening. It is more-or-less the "MPI-3.1" style of function bindings.<br class="">
<br class="">
<a href="https://github.com/mpiwg-large-count/large-count-issues/wiki/pythonizing-initial-review" class="">See this wiki page for instructions</a>.<br class="">
<br class="">
For additional information, also <a href="https://docs.google.com/presentation/d/1QZyh6TbjDMu7mEcNqBFfe9fFOltaCtxgZ2ZODzdtDpI/edit#slide=id.g5d01a902fe_0_69" class="">see the Pythonization slides presented at the Forum last week</a>. If you have any questions
or problems, let us know in the Embiggening WG.</div>
<div class="" style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);"><br class="">
</div>
<div class="" style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);">If you just want to compare the rendered PDF:</div>
<div class="" style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);"><br class="">
</div>
<div class="">
<ul class="MailOutline">
<li class=""><font color="#000000" class=""><span style="caret-color: rgb(0, 0, 0);" class=""><a href="https://aws.open-mpi.org/~jsquyres/forum-unofficial/mpi-report-mpi4xhead-d8ad059.pdf" class="">Here's a PDF from the head of the mpi-4.x branch</a> (i.e.,
old/original LaTeX)</span></font></li><li class=""><font color="#000000" class=""><a href="https://aws.open-mpi.org/~jsquyres/forum-unofficial/mpi-report-d8ad059-pythonized-NOT-embiggened.pdf" class="">Here's a PDF from the head of the Pythonization branch</a> <i class=""><u class="">with no Embiggening</u></i>
(i.e,. new/Python-rendered LaTeX)</font></li></ul>
</div>
<div class="" style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);"><br class="">
<font color="#ff0000" class=""><span style="font-size: 36px;" class="">Deadline: 21 Jan, 2020</span><br class="">
</font> This gives us time to finalize everything before the T-2 week deadline for the Portland Forum meeting.</div>
<div class="" style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);"><br class="">
<b class=""><u class="">NOTE:</u></b> At the ABQ Forum meeting, I asked you to commit/PR your approvals.json file that resulted from running the tool. This is no longer necessary -- please just mark the google spreadsheet as described above.</div>
<div class=""><br class="webkit-block-placeholder">
</div>
<div class=""><b class="" style="caret-color: rgb(0, 0, 0);"><u class=""><font class="" color="#ff8700">THIRD SET</font></u></b></div>
<div class=""><br class="webkit-block-placeholder">
</div>
<div class="">After Pythonization comes Embiggening. We need Chapter Committees to review their chapters to ensure that API parameters were embiggened properly.</div>
<div class=""><br class="">
</div>
<div class="">You can do this by finding all "POLY" kinds in the Pythonized LaTeX bindings, and you can see 2xC bindings and 2xF08 bindings in the rendered PDF in your chapter. <span style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);" class="">If you have
any questions or problems, let us know in the Embiggening WG.</span></div>
<div class=""><span style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);" class=""><br class="">
</span></div>
<div class=""><span style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);" class="">Also check that the existing MPI-3.1 "_x" functions -- and their corresponding non-"_x" versions -- are all rendered correctly.</span></div>
<div class=""><br class="">
</div>
<div class="">
<div class="" style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);">If you just want to compare the rendered PDF:</div>
<div class="" style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);"><br class="">
</div>
<div class="">
<ul class="MailOutline">
<li class=""><font color="#000000" class=""><a href="https://aws.open-mpi.org/~jsquyres/forum-unofficial/mpi-report-mpi4xhead-d8ad059.pdf" class="">Here's a PDF from the head of the mpi-4.x branch</a> (i.e., old/original LaTeX)</font></li><li class=""><font color="#000000" class=""><a href="https://aws.open-mpi.org/~jsquyres/forum-unofficial/mpi-report-d8ad059-pythonized-and-EMBIGGENED.pdf" class="">Here's a PDF from the head of the Pythonization branch</a> <i class=""><span style="font-size: 36px;" class=""><u class="">with
Embiggening enabled</u></span></i> (i.e,. new/Python-rendered LaTeX)</font></li></ul>
</div>
</div>
<div class=""><br class="webkit-block-placeholder">
</div>
<div class="">
<div class="" style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);"><font color="#ff0000" class=""><span style="font-size: 36px;" class="">Deadline: 21 Jan, 2020</span><br class="">
</font> You can probably review the second and third sets in a single pass through the text.</div>
<div class=""><br class="">
</div>
-- <br class="">
Jeff Squyres<br class="">
<a href="mailto:jsquyres@cisco.com" class="">jsquyres@cisco.com</a></div>
<br class="">
</div>
</body>
</html>