December 2019 - mpiwg-large-counts - mailman3.cels.anl.gov

Re: [Mpiwg-large-counts] Regular meeting tomorrow?
by Jeff Squyres (jsquyres) 18 Dec '19

18 Dec '19

I’ll be there. Sent from my phone. No type good. On Dec 17, 2019, at 7:34 PM, Martin Ruefenacht <m.a.ruefenacht(a)gmail.com> wrote: I am available. AndI think it would be useful before releasing to the Forum. Martin On Tue, 17 Dec 2019 at 21:51, Jeff Squyres (jsquyres) via mpiwg-large-counts <mpiwg-large-counts(a)lists.mpi-forum.org<mailto:[email protected]>> wrote: Are we having our regular Pythonization/Embiggening WG Zoom tomorrow morning (Wed, Dec 18, 9am US Eastern)? I ask because I know Dan is out for the rest of the year on vacation. -- Jeff Squyres jsquyres(a)cisco.com<mailto:[email protected]> _______________________________________________ mpiwg-large-counts mailing list mpiwg-large-counts(a)lists.mpi-forum.org<mailto:[email protected]> https://lists.mpi-forum.org/mailman/listinfo/mpiwg-large-counts -- Martin

1 0

Re: [Mpiwg-large-counts] Regular meeting tomorrow?
by Martin Ruefenacht 17 Dec '19

17 Dec '19

I am available. AndI think it would be useful before releasing to the Forum. Martin On Tue, 17 Dec 2019 at 21:51, Jeff Squyres (jsquyres) via mpiwg-large-counts <mpiwg-large-counts(a)lists.mpi-forum.org> wrote: > Are we having our regular Pythonization/Embiggening WG Zoom tomorrow > morning (Wed, Dec 18, 9am US Eastern)? > > I ask because I know Dan is out for the rest of the year on vacation. > > -- > Jeff Squyres > jsquyres(a)cisco.com > > _______________________________________________ > mpiwg-large-counts mailing list > mpiwg-large-counts(a)lists.mpi-forum.org > https://lists.mpi-forum.org/mailman/listinfo/mpiwg-large-counts > -- Martin

1 0

Re: [Mpiwg-large-counts] DRAFT: Chapter Committees ACTION NEEDED
by Jeff Squyres (jsquyres) 17 Dec '19

17 Dec '19

Dan -- Good points; many thanks. On Dec 17, 2019, at 1:31 PM, HOLMES Daniel <d.holmes(a)epcc.ed.ac.uk<mailto:[email protected]>> 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(a)epcc.ed.ac.uk<mailto:[email protected]> 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(a)lists.mpi-forum.org<mailto:[email protected]>> 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-f6Qz…>. 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-in… Also please see the Pythonization slides presented at the Forum last week<https://docs.google.com/presentation/d/1QZyh6TbjDMu7mEcNqBFfe9fFOltaCtxgZ2Z…>. 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(a)cisco.com<mailto:[email protected]> _______________________________________________ mpiwg-large-counts mailing list mpiwg-large-counts(a)lists.mpi-forum.org<mailto:[email protected]> https://lists.mpi-forum.org/mailman/listinfo/mpiwg-large-counts -- Jeff Squyres jsquyres(a)cisco.com<mailto:[email protected]>

1 0

Regular meeting tomorrow?
by Jeff Squyres (jsquyres) 17 Dec '19

17 Dec '19

Are we having our regular Pythonization/Embiggening WG Zoom tomorrow morning (Wed, Dec 18, 9am US Eastern)? I ask because I know Dan is out for the rest of the year on vacation. -- Jeff Squyres jsquyres(a)cisco.com

1 0

Re: [Mpiwg-large-counts] DRAFT: Chapter Committees ACTION NEEDED
by Jeff Hammond 17 Dec '19

17 Dec '19

I am allowed to do more than my minimum obligations, am I not? Jeff Sent from my iPhone > On Dec 17, 2019, at 11:13 AM, HOLMES Daniel <d.holmes(a)epcc.ed.ac.uk> wrote: > > Hi JeffH, > > You are not currently a member of any chapter committee - you are completely off this particular hook. > > Part of the review is to examine the Latex/Python to verify that the rendering is correct *for the correct reason*. I think this necessarily involves obtaining the source git branch. > > +1 for providing detailed instructions, possibly in the form of a Python script. > > Cheers, > Dan. > — > Dr Daniel Holmes PhD > Architect (HPC Research) > d.holmes(a)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 18:58, Jeff Hammond via mpiwg-large-counts <mpiwg-large-counts(a)lists.mpi-forum.org> wrote: >> >> please attach PDF of spec in any email like this. i do not want to have to do all the git+latex gymnastics for this if i can avoid it. >> >>> On Tue, Dec 17, 2019 at 7:09 AM Jeff Squyres (jsquyres) via mpiwg-large-counts <mpiwg-large-counts(a)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. 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-in… >>> >>> Also please see the Pythonization slides presented at the Forum last week. >>> >>> 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(a)cisco.com >>> >>> _______________________________________________ >>> mpiwg-large-counts mailing list >>> mpiwg-large-counts(a)lists.mpi-forum.org >>> https://lists.mpi-forum.org/mailman/listinfo/mpiwg-large-counts >> >> >> -- >> Jeff Hammond >> jeff.science(a)gmail.com >> http://jeffhammond.github.io/ >> _______________________________________________ >> mpiwg-large-counts mailing list >> mpiwg-large-counts(a)lists.mpi-forum.org >> https://lists.mpi-forum.org/mailman/listinfo/mpiwg-large-counts >

1 0

Re: [Mpiwg-large-counts] DRAFT: Chapter Committees ACTION NEEDED
by HOLMES Daniel 17 Dec '19

17 Dec '19

Hi JeffH, You are not currently a member of any chapter committee - you are completely off this particular hook. Part of the review is to examine the Latex/Python to verify that the rendering is correct *for the correct reason*. I think this necessarily involves obtaining the source git branch. +1 for providing detailed instructions, possibly in the form of a Python script. Cheers, Dan. — Dr Daniel Holmes PhD Architect (HPC Research) d.holmes(a)epcc.ed.ac.uk<mailto:[email protected]> 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 18:58, Jeff Hammond via mpiwg-large-counts <mpiwg-large-counts(a)lists.mpi-forum.org<mailto:[email protected]>> wrote: please attach PDF of spec in any email like this. i do not want to have to do all the git+latex gymnastics for this if i can avoid it. On Tue, Dec 17, 2019 at 7:09 AM Jeff Squyres (jsquyres) via mpiwg-large-counts <mpiwg-large-counts(a)lists.mpi-forum.org<mailto:[email protected]>> 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-f6Qz…>. 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-in… Also please see the Pythonization slides presented at the Forum last week<https://docs.google.com/presentation/d/1QZyh6TbjDMu7mEcNqBFfe9fFOltaCtxgZ2Z…>. 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(a)cisco.com<mailto:[email protected]> _______________________________________________ mpiwg-large-counts mailing list mpiwg-large-counts(a)lists.mpi-forum.org<mailto:[email protected]> https://lists.mpi-forum.org/mailman/listinfo/mpiwg-large-counts -- Jeff Hammond jeff.science(a)gmail.com<mailto:[email protected]> http://jeffhammond.github.io/ _______________________________________________ mpiwg-large-counts mailing list mpiwg-large-counts(a)lists.mpi-forum.org<mailto:[email protected]> https://lists.mpi-forum.org/mailman/listinfo/mpiwg-large-counts

1 0

Re: [Mpiwg-large-counts] DRAFT: Chapter Committees ACTION NEEDED
by Jeff Hammond 17 Dec '19

17 Dec '19

please attach PDF of spec in any email like this. i do not want to have to do all the git+latex gymnastics for this if i can avoid it. On Tue, Dec 17, 2019 at 7:09 AM Jeff Squyres (jsquyres) via mpiwg-large-counts <mpiwg-large-counts(a)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-f6Qz…>. > 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/1QZyh6TbjDMu7mEcNqBFfe9fFOltaCtxgZ2Z…> > . > > 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(a)cisco.com > > _______________________________________________ > mpiwg-large-counts mailing list > mpiwg-large-counts(a)lists.mpi-forum.org > https://lists.mpi-forum.org/mailman/listinfo/mpiwg-large-counts > -- Jeff Hammond jeff.science(a)gmail.com http://jeffhammond.github.io/

1 0

Re: [Mpiwg-large-counts] DRAFT: Chapter Committees ACTION NEEDED
by HOLMES Daniel 17 Dec '19

17 Dec '19

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(a)epcc.ed.ac.uk<mailto:[email protected]> 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(a)lists.mpi-forum.org<mailto:[email protected]>> 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-f6Qz…>. 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-in… Also please see the Pythonization slides presented at the Forum last week<https://docs.google.com/presentation/d/1QZyh6TbjDMu7mEcNqBFfe9fFOltaCtxgZ2Z…>. 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(a)cisco.com<mailto:[email protected]> _______________________________________________ mpiwg-large-counts mailing list mpiwg-large-counts(a)lists.mpi-forum.org<mailto:[email protected]> https://lists.mpi-forum.org/mailman/listinfo/mpiwg-large-counts

1 0

DRAFT: Chapter Committees ACTION NEEDED
by Jeff Squyres (jsquyres) 17 Dec '19

17 Dec '19

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-f6Qz…>. 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-in… Also please see the Pythonization slides presented at the Forum last week<https://docs.google.com/presentation/d/1QZyh6TbjDMu7mEcNqBFfe9fFOltaCtxgZ2Z…>. 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(a)cisco.com<mailto:[email protected]>

1 0

Puri: embiggening instructions
by Jeff Squyres (jsquyres) 07 Dec '19

07 Dec '19

Puri -- Per our discussion earlier this week, you're going to embiggen the collective chapter so that we can show it in ABQ this week. Here's what you need to know: 1. Clone Martin's fork: https://github.com/martinruefenacht/mpi-standard 2. Check out the feat-modern-lang-bindings branch 3. Edit the collective .tex: 3a. Per the embiggening text and https://docs.google.com/presentation/d/13X_4moTKxIHB0YJI-bBlJ5V3bF2WywB1DfO…, selectively embiggen arguments 3b. You embiggen types by changing the 2nd arg to parameter() to a "POLY" type. Here's the POLY types that we have defined: - POLYDISPLACEMENT - POLYDTYPE_NUM_ELEM -- used in the datatype chapter; we might need to revisit this one...? - POLYNUM_BYTES -- ditto (datatype chap/might need to revisit) - POLYXFER_NUM_ELEM I'm guessing you'll use POLYDISPLACEMENT and/or POLYXFER_NUM_ELEM. I used POLYXFER_NUM_ELEM in the pt2pt chapter (e.g., for MPI_SEND and MPI_RECV and friends). If you need old POLY types, let us know. ----- You can "make 4cleandoc" at the top level to make an mpi-report.pdf in the MPI-4 / embiggened style. For any function with POLY types, you should see a 2nd "_l" C binding, and 2 x MPIF08 bindings (with no "_l" suffix). "make 3cleandoc" (or just "make cleandoc") will make mph-report.pdf in the MPI-3 / not-embiggened style. You can do the same thing in the chapter directory, but you'll need to edit Makefile.chap and change RENDER_MODE = 3.1 to RENDER_MODE = 4.0 Then you can cd chap-coll make To make just the collectives chapter PDF (coll.pdf). It's probably a LOT quicker than building the entire cleandoc. In case you need it, wiki for the regular Pythonizing directions (which doesn't really say anything about Embiggening yet) is here: https://github.com/mpiwg-large-count/large-count-issues/wiki/pythonizing -- Jeff Squyres jsquyres(a)cisco.com

1 0