September 2023 - mpi-forum - mailman3.cels.anl.gov

October 2023 MPI Forum Meeting Registration
by Wes Bland 27 Sep '23

27 Sep '23

Hi all, Registration for the October (Final Ratification) meeting is now open. Please register ASAP before you forget about it. https://forms.gle/DYMyFaknKrTXszjB8 September 2023 MPI Forum Meeting Registration forms.gle This meeting will be fully remote and the meeting information will be in the usual place on the website under the logistics page: https://www.mpi-forum.org/meetings/2023/10/logistics Thanks, Wes

1 0

MPI Forum Officer Nominations & October Reading Announcements
by Wes Bland 26 Sep '23

26 Sep '23

Hi all, Another reminder that nominations for MPI Forum officers opened at the end of the last meeting and will stay open until October 17th. I’ll post them on the agenda page for the upcoming meeting as I get them. https://www.mpi-forum.org/meetings/2023/10/agenda Please send nominations to this mailing list. I’ll go ahead and point to the nominations that Jeff Hammond posted on the Slack channel for the current slate of officers to continue in their positions. Those have already been put on the website. If you’d like to familiarize yourself with the job descriptions, you can find them in the procedures doc (https://www.mpi-forum.org/docs/other/procedures-34.pdf) or reach out to the current office holders for more details. In addition, I’m going to help out a bit with reading announcements for the October meeting. Because there are going to be a large number of relatively small issues/PRs for this meeting and we’re dealing with them a little differently by merging them early, I’m going ahead and adding them to the agenda as they are merged. Therefore, if you have an issue for the MPI 4.1 RC, you don’t need to announce it as long as you see it on the agenda page above (and everyone should consider anything on that page as having been announced). If anyone has readings that aren’t based on MPI 4.1 fixes (things for 4.2 or 5.0), please announce them as usual. I would imagine that we’ll have time to do additional readings after we finish our MPI 4.1 business. Thanks, Wes

1 0

Re: [Mpi-forum] Complete RC open issues list from MPI Forum RCM
by Joseph Schuchart 21 Sep '23

21 Sep '23

Martin, all, I went through the issues grouped under the RMA chapter (Chapter 12) and found that some of them are issues in the I/O chapter: rows 228-259 (except for row 239) seem relevant for the I/O chapter and not the RMA chapter. I guess there has been some confusion about document and PDF numbers. I don't want to mess with the excel sheet but wanted to raise this here so that the I/O CC can take a look at these points. Cheers Joseph On 9/17/23 10:30, Martin Schulz via mpi-forum wrote: > > Hi all, > > First of all, thank all for a very productive and focused meeting last > week on our path to MPI 4.1 – both to those attending in person in > Bristol and to those online at often quite unfortunate hours! > > As discussed, I compiled a list of all open points and consolidated > this into a single spreadsheet, which is here: > > https://docs.google.com/spreadsheets/d/1ZpsyVTnfNHv85K9Mzi_3niNXdmQ67yV2iwS… > > There is a total of 380 points that we collected that we think should > be still addressed somehow. I placed them into five categories: > > * MPI 4.1: This is more or less the default category and should at > the end contain all small changes that we still want to apply the > standard (and which will be voted on). For all items in these > categories, we will need Pull requests and Issue created. > * Editor changes: Small changes and formatting changes that Bill > will apply directly – no separate PR or Issue is necessary. Once > an item is in this category, please do not touch it (unless Bill > pushes it back to one of the other categories) > * Flow: Items covering bad page breaks, strange spacing, etc., which > do not change the contents of the document and which need to be > addressed at the very end during layout – Bill will go over them > at the end and these items are mainly meant as hints for him to > pay attention to > * MPI 4.2: Items we think are too big and which should be pushed to > the next version of the standard or separate erratas. For those, > we will eventually also need PRs and Issues and we could > technically start reading them in the next meeting if there is time. > * Reject: items we decided to drop > > Note: this list all points individually as we recorded them – multiple > of them can of course (and should) be grouped into a single PR or Issue. > > ACTION ITEMS: > > * If you reviewed parts of the standard, please check the list and > make sure comments are properly recorded (if you noticed mistakes > in the page numbers, please let me know, as this means updates in > hidden parts of the spreadsheet) > * CC chairs: please take a look at all comments for your chapter and > ensure that they are consolidated correctly. By default you are > responsible for completing or shepherding all items in your chapter. > * If you have created PRs and Issues (or if you do so from now on), > please place them into the appropriate columns, so we can track it > and place yourself into the owner category. > * If the PR/Issue is complete and ready for review, please mark this > in the column “DONE”. > * If you think an MPI 4.1 issue should be moved to one of the other > categories, please move the checkmark and note the reason for the > decision in the “Comments” column at the end (together with your > name). > > As Wes noted on Friday, we have a short time line here – all items we > want for 4.1 must be in the DONE column by September 26. > > I hope this all makes sense and covers all steps forward – if you have > any questions, comments or concerns, please let me know. > > Thanks! > > Martin > > PS: This is a shared spreadsheet, so please be careful when editing > and please do not change anything structural. Also, mark any > decisions, observations or comments in the last column together with > your name, so we have a track record for the discussions next time. > Thanks! > > -- > > 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 > > > _______________________________________________ > mpi-forum mailing list > mpi-forum(a)lists.mpi-forum.org > https://lists.mpi-forum.org/mailman/listinfo/mpi-forum

1 0

Complete RC open issues list from MPI Forum RCM
by Martin Schulz 17 Sep '23

17 Sep '23

Hi all, First of all, thank all for a very productive and focused meeting last week on our path to MPI 4.1 – both to those attending in person in Bristol and to those online at often quite unfortunate hours! As discussed, I compiled a list of all open points and consolidated this into a single spreadsheet, which is here: https://docs.google.com/spreadsheets/d/1ZpsyVTnfNHv85K9Mzi_3niNXdmQ67yV2iwS… There is a total of 380 points that we collected that we think should be still addressed somehow. I placed them into five categories: MPI 4.1: This is more or less the default category and should at the end contain all small changes that we still want to apply the standard (and which will be voted on). For all items in these categories, we will need Pull requests and Issue created. Editor changes: Small changes and formatting changes that Bill will apply directly – no separate PR or Issue is necessary. Once an item is in this category, please do not touch it (unless Bill pushes it back to one of the other categories) Flow: Items covering bad page breaks, strange spacing, etc., which do not change the contents of the document and which need to be addressed at the very end during layout – Bill will go over them at the end and these items are mainly meant as hints for him to pay attention to MPI 4.2: Items we think are too big and which should be pushed to the next version of the standard or separate erratas. For those, we will eventually also need PRs and Issues and we could technically start reading them in the next meeting if there is time. Reject: items we decided to drop Note: this list all points individually as we recorded them – multiple of them can of course (and should) be grouped into a single PR or Issue. ACTION ITEMS: If you reviewed parts of the standard, please check the list and make sure comments are properly recorded (if you noticed mistakes in the page numbers, please let me know, as this means updates in hidden parts of the spreadsheet) CC chairs: please take a look at all comments for your chapter and ensure that they are consolidated correctly. By default you are responsible for completing or shepherding all items in your chapter. If you have created PRs and Issues (or if you do so from now on), please place them into the appropriate columns, so we can track it and place yourself into the owner category. If the PR/Issue is complete and ready for review, please mark this in the column “DONE”. If you think an MPI 4.1 issue should be moved to one of the other categories, please move the checkmark and note the reason for the decision in the “Comments” column at the end (together with your name). As Wes noted on Friday, we have a short time line here – all items we want for 4.1 must be in the DONE column by September 26. I hope this all makes sense and covers all steps forward – if you have any questions, comments or concerns, please let me know. Thanks! Martin PS: This is a shared spreadsheet, so please be careful when editing and please do not change anything structural. Also, mark any decisions, observations or comments in the last column together with your name, so we have a track record for the discussions next time. Thanks! -- 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

MPI Forum Starting Tomorrow / Wednesday: Missing Reviews / Chapter Readings
by Martin Schulz 12 Sep '23

12 Sep '23

Hi all, We will be starting tomorrow afternoon (local time) with our MPI Forum RC Meeting. The core will be the reading of the changes made to all chapters, as well as the creation of a list of all outstanding issues. For this, we are still missing a few reviews of the MPI standard – the procedure is laid out below in a previous email by Wesley. If you haven’t had the chance to do this, yet, please complete your section as soon as possible, so that we can get a complete overview. If you would like to volunteer for an open section, please let us know as well. Also, just a reminder for all chapter committee chairs: please let us know if you won’t be reading your chapter diffs who from your committee you have designated to do so. Thanks and see you tomorrow (in Bristol or online), 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 From: Wes Bland <work(a)wesbland.com> Date: Wednesday, 23. August 2023 at 17:36 To: Amit Ruhela <aruhela(a)tacc.utexas.edu>, Aurelien Bouteiller <bouteill(a)icl.utk.edu>, "benson.muite(a)kichakatokizito.solutions" <benson.muite(a)kichakatokizito.solutions>, William Williams <william.williams(a)mailbox.tu-dresden.de>, "bsmith(a)cornelisnetworks.com" <bsmith(a)cornelisnetworks.com>, Christoph Niethammer <niethammer(a)hlrs.de>, Claudia Blaas-Schenner <claudia.blaas-schenner(a)tuwien.ac.at>, Dan Holmes <daniel.john.holmes(a)intel.com>, "dschafer1(a)unm.edu" <dschafer1(a)unm.edu>, "edgar.gabriel(a)gmail.com" <edgar.gabriel(a)gmail.com>, "mercier(a)labri.fr" <mercier(a)labri.fr>, "Howard Pritchard Jr." <howardp(a)lanl.gov>, Hugo Taboada <Hugo.TABOADA(a)cea.fr>, Ignacio Laguna <ilaguna(a)llnl.gov>, "jbbesnard(a)paratools.com" <jbbesnard(a)paratools.com>, James Dinan <jdinan(a)nvidia.com>, Joseph Schuchart <schuchart(a)icl.utk.edu>, "Julien.JAEGER(a)cea.fr" <Julien.JAEGER(a)cea.fr>, "raffenet(a)anl.gov" <raffenet(a)anl.gov>, "capelli.ludovic(a)gmail.com" <capelli.ludovic(a)gmail.com>, Marc-André Hermanns <hermanns(a)itc.rwth-aachen.de>, Maria Garzaran <maria.garzaran(a)intel.com>, Martin Rüefenacht <m.a.ruefenacht(a)gmail.com>, "martin.schreiber(a)univ-grenoble-alpes.fr" <martin.schreiber(a)univ-grenoble-alpes.fr>, Martin Schulz <schulzm(a)in.tum.de>, Matthew Dosanjh <mdosanj(a)sandia.gov>, "michael.klemm(a)amd.com" <michael.klemm(a)amd.com>, "m.knobloch(a)fz-juelich.de" <m.knobloch(a)fz-juelich.de>, "shineman.5(a)osu.edu" <shineman.5(a)osu.edu>, "jnysal(a)in.ibm.com" <jnysal(a)in.ibm.com>, Puri Bangalore <pvbangalore(a)ua.edu>, Quincey Koziol <qkoziol(a)amazon.com>, "Shipley, Riley Prescott" <riley-shipley(a)utc.edu>, Ryan Grant <ryan.grant(a)queensu.ca>, "sumimoto(a)cc.u-tokyo.ac.jp" <sumimoto(a)cc.u-tokyo.ac.jp>, Thomas Naughton <naughtont(a)ornl.gov>, Tobias Haas <tobias.haas(a)hlrs.de>, "eijkhout(a)tacc.utexas.edu" <eijkhout(a)tacc.utexas.edu>, Wes Bland <work(a)wesbland.com>, William Gropp <wgropp(a)illinois.edu> Subject: Re: Action Required -- MPI 4.1 RC Review Hi folks, I’m sorry that I left out the detail about the page numbers. A couple of you have already asked about this. The document essentially has two sets of page numbers. The first is the one that your PDF reader will likely give and starts at 1. The second is what is printed in the document and starts at i (lowercase “eye”). The original numbers in the sheet were the first set, but I’ve now added another set of columns with the second as well. So you can hopefully decipher which ones are assigned to you from that. When you fill out the form with your response, please use the first set of numbers. Thanks, Wes On Aug 23, 2023, at 10:57 AM, Wes Bland <work(a)wesbland.com> wrote: Hi all, Thanks to each of you for being an active participant in the MPI Forum this year. As we come to the end of the MPI 4.1 ratification process, we have one more ask for each of you who have been most involved. As we discussed during the July 2023 meeting now is the time that we will collectively review the MPI 4.1 RC Document before we go through the final steps for ratification. Each of you who have been active participants over the last year have been assigned a chunk of the document (each chunk is 30 pages). Your assignments can be found on this Google Sheet: https://docs.google.com/spreadsheets/d/16o1Zf0YGGEIHIn9ULp9IodBok2TF2YNKEFH… You can find the document itself here: https://github.com/mpi-forum/mpi-forum.github.io/raw/master/docs/mpi-4.1/mp… As you are reviewing, these are the guidelines for things you should be looking for: 1. Formatting and whitespace problems 2. Spelling errors or other typos 3. Logical inconsistencies in the overall document 4. Problems with the way approved changes were applied You are welcome to note any other issues you see as well. As you finish your review, please use this form (https://forms.gle/93hXANvVkp3MhrCD9) to provide your feedback. I’ll be able to triage issues from there. If you have no notes, please still fill out that form and mention that so we know each chunk has been covered. These reviews must be completed by September 8th (there are no review deadline extensions 😀) so we can discuss them at the meeting the following week. If you cannot complete your assignment by then, please let Martin and I know as soon as possible so we can try to find someone else who is willing to take over your section. If you are willing to look through an extra section, please let us know that too so we can line up extra reviewers just in case. If you have any questions, feel free to reach out to us for clarification. Thanks, Wes

1 0

September 2023 MPI Forum Registration
by Wes Bland 10 Sep '23

10 Sep '23

Hi all, As of now, we still haven’t met quorum yet for the September meeting. I’m sure this is largely because of the confusion of having two registration pages for this meeting. Please double check if you’ve registered for the meeting here: https://www.mpi-forum.org/meetings/2023/09/attendance If you haven’t registered, please do so ASAP here: https://forms.gle/sEeNtbyXxnJndGrU9 Thanks, Wes

1 0