<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">
Hi Jeff,
<div class=""><br class="">
</div>
<div class="">The (potential) new “Partitioned Communication” chapter should be included in the Google spreadsheet, without a chapter number, between chapters 7 and 8 (its most likely insertion position). FYI - Ryan is Chair of that (speculative) Chapter Committee.</div>
<div class=""><br class="">
</div>
<div class="">First set wording - fine.</div>
<div class=""><br class="">
</div>
<div class="">Second set wording - there are two purposes for this part of the review</div>
<div class="">1) does compiling the non-Embiggened(tm) version of the Pythonised source render the document sufficiently similarly to the document rendered by compiling the pre-Embiggening(tm) version of the pure-Latex source?</div>
<div class="">2) does compiling the post-Embiggening(tm) version of the Pythonised source render the document in a manner consistent with the application of the rules/expectations, i.e. in accordance with the text changes read (rejected via no-no-vote veto)
at the ABQ meeting?</div>
<div class=""><br class="">
</div>
<div class="">Both of the purposes motivating the review of the second set are important and should be completed before the T-2 deadline for the next face-to-face meeting (at the latest). This permits a full reading of all components for The Embiggening(tm),
including all the new bindings, to happen at the Portland meeting with the blessing (hopefully) of all of the chapter committees (except George's, I guess). This resets the MPI voting procedure clock, but it can happen concurrently with bringing forward additional
no-no votes (one for the text changes, another for the bindings) and a 1st vote for the hopefully-amended-by-no-no-votes BigCount ticket. When one or both of the no-no votes fail(s), we can pull the 1st vote and rely on the reading instead. The Jun meeting
will see either a 2nd vote (unlikely) or a 1st vote (more likely). The Jun meeting is also the point at which MartinS announces a release candidate that targets MPI-4.0 at SC20 (or doesn’t delaying it, e.g. until ISC21).</div>
<div class=""><br class="">
</div>
<div class="">Style - sufficiently lurid, except I suggest that the red deadline text should be embiggened.</div>
<div class="">
<div class="">
<div dir="auto" style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">
<div dir="auto" style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">
<div style="color: rgb(0, 0, 0); letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">
<div style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">
<br class="Apple-interchange-newline">
Cheers,</div>
<div style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">
Dan.</div>
<div style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">
—<br class="">
Dr Daniel Holmes PhD<br class="">
Architect (HPC Research)<br class="">
<a href="mailto:d.holmes@epcc.ed.ac.uk" class="">d.holmes@epcc.ed.ac.uk</a><br class="">
Phone: +44 (0) 131 651 3465<br class="">
Mobile: +44 (0) 7940 524 088<br class="">
Address: Room 2.09, Bayes Centre, 47 Potterrow, Central Area, Edinburgh, EH8 9BT</div>
<div style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">
—</div>
<div style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">
The University of Edinburgh is a charitable body, registered in Scotland, with registration number SC005336.</div>
<div style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">
—</div>
</div>
</div>
</div>
</div>
<div><br class="">
<blockquote type="cite" class="">
<div class="">On 17 Dec 2019, at 15:08, Jeff Squyres (jsquyres) via mpiwg-large-counts <<a href="mailto:mpiwg-large-counts@lists.mpi-forum.org" class="">mpiwg-large-counts@lists.mpi-forum.org</a>> wrote:</div>
<br class="Apple-interchange-newline">
<div class="">
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">
This is a DRAFT of what I'd like to send to the Forum to get all Chapter Committees to review the document-wide stuff that we need reviewed. Please send comments / suggestions to me. Thanks!
<div class=""><br class="">
</div>
<div class="">(Last week, I accidentally sent this to the wrong WG -- I am [finally] re-sending it to the large count WG for proofing before I sent this out to the entire Forum mailing list / chapter chairs)<br class="">
<br class="">
-----------------------------------------<br class="">
<br class="">
We need Chapter Committees to review their chapters in 2 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>. This will let us track what has been done / what still needs to be done:<br class="">
<br class="">
</div>
<div class=""><span style="font-size: 36px;" class=""><b class=""><u class=""><font color="#ffff02" class="">FIRST SET</font><br class="">
</u></b></span><br 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:<br class="">
<br class="">
1a. "Ticket 0 changes for MPI-4.x"<br class="">
<a href="https://github.com/mpi-forum/mpi-standard/pull/145" class="">https://github.com/mpi-forum/mpi-standard/pull/145</a><br class="">
1b. "Uniform style for Fortran code"<br class="">
<a href="https://github.com/mpi-forum/mpi-standard/pull/151" class="">https://github.com/mpi-forum/mpi-standard/pull/151</a><br class="">
<br class="">
<font color="#ff0000" class="">Deadline: Jan 7, 2020</font></div>
<div class=""> (Yes, that's an early deadline, but we need time to merge this and fix conflicts with the second set)</div>
<div class=""><br class="">
<b class=""><u style="font-size: 36px;" class=""><font color="#ffff02" class="">SECOND SET</font><br class="">
</u></b><br 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 (at least) the MPI-3.1 document -- or, better yet, to the head
of the mpi-4.x branch.<br class="">
<br class="">
See this wiki page for instructions: <a href="https://github.com/mpiwg-large-count/large-count-" class="">https://github.com/mpiwg-large-count/large-count-</a>issues/wiki/pythonizing-initial-review<br class="">
<br class="">
Also please <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>.</div>
<div class=""><br class="">
<font color="#ff0000" class="">Deadline: 21 Jan, 2020<br class="">
</font> This gives us time to finalize everything before the T-2 week deadline for the Portland Forum meeting.</div>
<div class=""><br class="">
NOTE: 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.<br class="">
<div class=""><br class="">
-- <br class="">
Jeff Squyres<br class="">
<a href="mailto:jsquyres@cisco.com" class="">jsquyres@cisco.com</a></div>
<br class="">
</div>
</div>
_______________________________________________<br class="">
mpiwg-large-counts mailing list<br class="">
<a href="mailto:mpiwg-large-counts@lists.mpi-forum.org" class="">mpiwg-large-counts@lists.mpi-forum.org</a><br class="">
https://lists.mpi-forum.org/mailman/listinfo/mpiwg-large-counts<br class="">
</div>
</blockquote>
</div>
<br class="">
</div>
</body>
</html>