[Mpiwg-large-counts] DRAFT: Chapter Committees ACTION NEEDED

Tue Dec 17 16:06:38 CST 2019

Dan --

Good points; many thanks.

On Dec 17, 2019, at 1:31 PM, HOLMES Daniel <d.holmes at epcc.ed.ac.uk<mailto:d.holmes at epcc.ed.ac.uk>> wrote:

Hi Jeff,

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.

First set wording - fine.

Second set wording - there are two purposes for this part of the review
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?
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?

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).

Style - sufficiently lurid, except I suggest that the red deadline text should be embiggened.

Cheers,
Dan.
—
Dr Daniel Holmes PhD
Architect (HPC Research)
d.holmes at epcc.ed.ac.uk<mailto:d.holmes at epcc.ed.ac.uk>
Phone: +44 (0) 131 651 3465
Mobile: +44 (0) 7940 524 088
Address: Room 2.09, Bayes Centre, 47 Potterrow, Central Area, Edinburgh, EH8 9BT
—
The University of Edinburgh is a charitable body, registered in Scotland, with registration number SC005336.
—

On 17 Dec 2019, at 15:08, Jeff Squyres (jsquyres) via mpiwg-large-counts <mpiwg-large-counts at lists.mpi-forum.org<mailto:mpiwg-large-counts at lists.mpi-forum.org>> wrote:

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!

(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)

-----------------------------------------

We need Chapter Committees to review their chapters in 2 sets of upcoming document-wide changes that are slated to be merged "soon".

After you complete a review, please put an "X" in the corresponding row/column for your chapter and the specified PR in this Google spreadsheet<https://docs.google.com/spreadsheets/d/1qPAREYgeuSCMtU-EQniDilrHIYb8W0-f6Qzjp-UtnH8/edit?folder=1_LOwR_QeX_bwIe_eptiy0OxWaOvPQ8W8#gid=0>.  This will let us track what has been done / what still needs to be done:

FIRST SET

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:

1a. "Ticket 0 changes for MPI-4.x"
   https://github.com/mpi-forum/mpi-standard/pull/145
1b. "Uniform style for Fortran code"
   https://github.com/mpi-forum/mpi-standard/pull/151

Deadline: Jan 7, 2020
    (Yes, that's an early deadline, but we need time to merge this and fix conflicts with the second set)

SECOND SET

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.

See this wiki page for instructions: https://github.com/mpiwg-large-count/large-count-issues/wiki/pythonizing-initial-review

Also please see the Pythonization slides presented at the Forum last week<https://docs.google.com/presentation/d/1QZyh6TbjDMu7mEcNqBFfe9fFOltaCtxgZ2ZODzdtDpI/edit#slide=id.g5d01a902fe_0_69>.

Deadline: 21 Jan, 2020
    This gives us time to finalize everything before the T-2 week deadline for the Portland Forum meeting.

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.

--
Jeff Squyres
jsquyres at cisco.com<mailto:jsquyres at cisco.com>

_______________________________________________
mpiwg-large-counts mailing list
mpiwg-large-counts at lists.mpi-forum.org<mailto:mpiwg-large-counts at lists.mpi-forum.org>
https://lists.mpi-forum.org/mailman/listinfo/mpiwg-large-counts

--
Jeff Squyres
jsquyres at cisco.com<mailto:jsquyres at cisco.com>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mpi-forum.org/pipermail/mpiwg-large-counts/attachments/20191217/154e3a3f/attachment-0001.html>