January 2020 - mpi-forum - mailman3.cels.anl.gov

MPI VM Meeting Cancelled / Reminder Action Items
by schulzm＠in.tum.de 15 Jan '20

15 Jan '20

Hi all, The MPI Forum Virtual Meeting for today is cancelled, as there are no particular news on BigCount at the moment. However, please take a look at the reminded that Jeff Squyres sent yesterday - it is important that we complete the review by next week (Jan. 21). Thanks! Martin — Prof. Dr. Martin Schulz, Chair of Computer Architecture and Parallel Systems Department of Informatics, TU-Munich, Boltzmannstraße 3, D-85748 Garching Member of the Board of Directors at the Leibniz Supercomputing Centre (LRZ) Email: schulzm(a)in.tum.de

1 0

Re: [Mpi-forum] Gentle reminder: Chapter Committees action needed by next week (21 Jan 2020)
by George Bosilca 14 Jan '20

14 Jan '20

Jeff, I found several issues, mainly in the error handler definition (loss of * in the errorhandler function) and datatypes creation functions (addition of "non-negative" for addresses and displacements). I have attached the output of the validation tool for all the functions I noticed. Let me know if you want it in a different format. George. On Tue, Jan 14, 2020 at 11:52 AM Jeff Squyres (jsquyres) via mpi-forum < mpi-forum(a)lists.mpi-forum.org> wrote: > 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. > > Some of you have already done your review. Thank you!! > > To be clear: this review does not include Embiggening. It is more-or-less > the "MPI-3.1" style of function bindings. > > See this wiki page for instructions > <https://github.com/mpiwg-large-count/large-count-issues/wiki/pythonizing-in…> > . > > For additional information, also see the Pythonization slides presented > at the Forum in December > <https://docs.google.com/presentation/d/1QZyh6TbjDMu7mEcNqBFfe9fFOltaCtxgZ2Z…>. > If you have any questions or problems, let us know in the Embiggening WG. > > If you just want to compare the rendered PDF: > > > - Here's a PDF from the head of the mpi-4.x branch > <https://aws.open-mpi.org/~jsquyres/forum-unofficial/mpi-report-mpi4xhead-d8…> (i.e., > old/original LaTeX) > - Here's a PDF from the head of the Pythonization branch > <https://aws.open-mpi.org/~jsquyres/forum-unofficial/mpi-report-15b96e7-pyth…> > *with no Embiggening* (i.e,. new/Python-rendered LaTeX) -- updated 14 > Jan 2020 > > > 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 in the > wiki. > > -- > Jeff Squyres > jsquyres(a)cisco.com > > _______________________________________________ > mpi-forum mailing list > mpi-forum(a)lists.mpi-forum.org > https://lists.mpi-forum.org/mailman/listinfo/mpi-forum >

1 0

Gentle reminder: Chapter Committees action needed by next week (21 Jan 2020)
by Jeff Squyres (jsquyres) 14 Jan '20

14 Jan '20

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. Some of you have already done your review. Thank you!! To be clear: this review does not include Embiggening. It is more-or-less the "MPI-3.1" style of function bindings. See this wiki page for instructions<https://github.com/mpiwg-large-count/large-count-issues/wiki/pythonizing-in…>. For additional information, also see the Pythonization slides presented at the Forum in December<https://docs.google.com/presentation/d/1QZyh6TbjDMu7mEcNqBFfe9fFOltaCtxgZ2Z…>. If you have any questions or problems, let us know in the Embiggening WG. If you just want to compare the rendered PDF: * Here's a PDF from the head of the mpi-4.x branch<https://aws.open-mpi.org/~jsquyres/forum-unofficial/mpi-report-mpi4xhead-d8…> (i.e., old/original LaTeX) * Here's a PDF from the head of the Pythonization branch<https://aws.open-mpi.org/~jsquyres/forum-unofficial/mpi-report-15b96e7-pyth…> with no Embiggening (i.e,. new/Python-rendered LaTeX) -- updated 14 Jan 2020 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 in the wiki. -- Jeff Squyres jsquyres(a)cisco.com<mailto:[email protected]>

1 0

Virtual Meeting Today
by Wesley Bland 08 Jan '20

08 Jan '20

Hi all, As a reminder, there is a virtual meeting scheduled for today at 10:00 AM Central US (1.5 hours from now). The topic is the Pythonization / Standard Cleanup Discussion and Q&A with Jeff and Bill to prepare for the upcoming review deadlines for both the general cleanup that Bill is doing as well as the Pythonization of the language bindings being done by Jeff, Martin, and others. I believe these will be heavily focused on Q&A so please come with questions from your review and if you are on a chapter committee, make sure you’ve finished your review of the various changes. As always, the virtual meeting information can be found here: https://www.mpi-forum.org/virtual_meetings/ <https://www.mpi-forum.org/virtual_meetings/> A calendar with all MPI Forum events is here: https://calendar.google.com/calendar/ical/g5ms8r3iaj3u3un3cjndqmjbc0%40grou… <https://calendar.google.com/calendar/ical/g5ms8r3iaj3u3un3cjndqmjbc0@group.…> And the information to join the WebEx for the virtual meeting is here: https://github.com/mpi-forum/mpi-standard/wiki/Virtual-Forum-Meeting-Inform… <https://github.com/mpi-forum/mpi-standard/wiki/Virtual-Forum-Meeting-Inform…> (a new WebEx is still being set up so the information will change between now and the start time). Thanks, Wesley

1 0

Guillaume/Pythonization: Chapter Committees ACTION NEEDED
by Jeff Squyres (jsquyres) 06 Jan '20

06 Jan '20

Thanks Guillaume! Some of those things -- particularly the widow/orphan stuff -- likely won't be handled until the near-completion of the MPI-4 doc. But it sounds like barring your minor fixes cited below, we Pythonized chapter 6 correctly. Thanks! > On Jan 6, 2020, at 3:10 AM, Guillaume Mercier via mpi-forum <mpi-forum(a)lists.mpi-forum.org> wrote: > > > Hello Jeff, > > I did complete my review for Pythonization in chapter 6. > > Here are my comments: > > 1- for the function MPI_Group_range_incl: > - missing space in ranges(3,n) (p262, l20) => should be ranges(3, n) > > 2-for the function MPI_Group_range_excl: > - missing space in ranges(3,n) (p263, l20/21) => should be ranges(3, n) > > 3- for the function MPI_Comm_rank: > the word "of" is missing (p265, l39) > "in the group comm" should be "in the group OF comm" in the description of the parameter > > 4- for the function MPI_Intercomm_create: > - no hyphen for newintercomm param (p293, l1/2) > - for F binding: NEWINTERCOMM should be under LOCAL_COMM (p293,l 31) > > 5- For the function MPI_Intercomm_merge: > position of Figure 6.3 is not optimal (p 294) > > 6- for the function MPI_Comm_create_keyval: > - no hyphen for extra_state param (p299, l11/12) > > 7- for the function MPI_Win_create_keyval: > - put "C binding" on the next page (p304, l48) > > 8- for the function MPI_Win_set_attr: > - put "F08 binding" on the next page (p306, l48) > > 9- for the function MPI_Type_free_keyval: > - put "C binding" on the next page (p309, l48) > > > I don't know if sending you this message is the right way to do this. > > Best > Guillaume > > > > > _______________________________________________ > mpi-forum mailing list > mpi-forum(a)lists.mpi-forum.org > https://lists.mpi-forum.org/mailman/listinfo/mpi-forum -- Jeff Squyres jsquyres(a)cisco.com

1 0

REMINDER: Chapter Committees ACTION NEEDED BY TOMORROW (7 Jan 2020)
by Jeff Squyres (jsquyres) 06 Jan '20

06 Jan '20

Gentle reminder that we need Chapter Committee reviews TOMORROW (7 Jan 2020) for Bill Gropp's proposed ticket 0 changes. According to the Google spreadsheet, 20 out of 23 chapters are not yet complete. 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…> (including an un-numbered chapter for partitioned communication). This will let us track what has been done / what still needs to be done. Please review ASAP. Thank you. On Dec 18, 2019, at 2:47 PM, Jeff Squyres (jsquyres) via mpi-forum <mpi-forum(a)lists.mpi-forum.org<mailto:[email protected]>> wrote: 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/151 1b. "Uniform style for Fortran code" https://github.com/mpi-forum/mpi-standard/pull/145 Deadline: Jan 7, 2020 -- Jeff Squyres jsquyres(a)cisco.com<mailto:[email protected]>

1 0

Re: [Mpi-forum] Chapter Committees ACTION NEEDED
by Guillaume Mercier 06 Jan '20

06 Jan '20

Hello Jeff, I did complete my review for Pythonization in chapter 6. Here are my comments: 1- for the function MPI_Group_range_incl: - missing space in ranges(3,n) (p262, l20) => should be ranges(3, n) 2-for the function MPI_Group_range_excl: - missing space in ranges(3,n) (p263, l20/21) => should be ranges(3, n) 3- for the function MPI_Comm_rank: the word "of" is missing (p265, l39) "in the group comm" should be "in the group OF comm" in the description of the parameter 4- for the function MPI_Intercomm_create: - no hyphen for newintercomm param (p293, l1/2) - for F binding: NEWINTERCOMM should be under LOCAL_COMM (p293,l 31) 5- For the function MPI_Intercomm_merge: position of Figure 6.3 is not optimal (p 294) 6- for the function MPI_Comm_create_keyval: - no hyphen for extra_state param (p299, l11/12) 7- for the function MPI_Win_create_keyval: - put "C binding" on the next page (p304, l48) 8- for the function MPI_Win_set_attr: - put "F08 binding" on the next page (p306, l48) 9- for the function MPI_Type_free_keyval: - put "C binding" on the next page (p309, l48) I don't know if sending you this message is the right way to do this. Best Guillaume

1 0