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

reading announcement for issue 693 / pull 816 (normative language references)
by Jeff Hammond 21 Aug '23

21 Aug '23

I am not sure what the exact deadline is, but I will read this one virtually in Bristol. https://github.com/mpi-forum/mpi-standard/pull/816, which addresses https://github.com/mpi-forum/mpi-issues/issues/693. Jeff -- Jeff Hammond jeff.science(a)gmail.com http://jeffhammond.github.io/

1 0

September 2023 Meeting Registration
by Wes Bland 14 Aug '23

14 Aug '23

Hi all, Registration for the EuroMPI 2023 conference and MPI Forum meeting is now open. You can find that link here: https://www.eventbrite.co.uk/e/iwomp-2023-eurompi-and-mpi-forum-tickets-666… If you plan to attend only the MPI Forum portion of the meeting (even remotely), you need to register at the link above. If you plan to attend the MPI Forum meeting at all, please also register at the link below so we can gather the appropriate information for our voting rules and demographics that we provide to Women in HPC. https://forms.gle/EMHZgSq7nSJ7gFwk6 Thanks, Wes

1 0

Re: [Mpi-forum] MPI 4.1 Author Names and Institutions
by Wes Bland 14 Aug '23

14 Aug '23

Thanks for pointing that out Jeff. I’ll see if I can put something together for the GitHub folks. For the WG Zooms, I do need help from the WGs themselves to know who’s active. If you have someone in your WG that doesn’t attend the main meetings, please let me know and I can add them. Thanks, Wes > On Aug 14, 2023, at 4:26 AM, Jeff Hammond <jeff.science(a)gmail.com> wrote: > > Given that we do most of the work on Zoom, GitHub and Slack now, I wonder if we need a more expansive filter. > > For example, the following contributed to https://github.com/mpi-forum/mpi-standard/pull/767 in some form. > > Simon Byrne - California Institute of Technology > Lisandro Dalcin - KAUST > > Jeff > > On Wed, Aug 9, 2023 at 7:33 PM Wes Bland via mpi-forum <mpi-forum(a)lists.mpi-forum.org <mailto:[email protected]>> wrote: > > > > Hi all, > > > > I just generated an updated list of author names and institutions as they would be published in MPI 4.1. I’ve previously sent out a link with all of the author names, but I forgot to include the institutions that time. Please take a look at this PDF to make sure your information and that of the places you’ve represented in the MPI 4.1 cycle is accurate. I’ve only included the relevant 4 pages. > > > > https://github.com/mpi-forum/mpi-standard/files/12304747/mpi41-report.pdf > > > > Thanks, > > Wes > > _______________________________________________ > > mpi-forum mailing list > > mpi-forum(a)lists.mpi-forum.org <mailto:[email protected]> > > https://lists.mpi-forum.org/mailman/listinfo/mpi-forum > > > > -- > Jeff Hammond > jeff.science(a)gmail.com <mailto:[email protected]> > http://jeffhammond.github.io/

1 0

Re: [Mpi-forum] MPI 4.1 Author Names and Institutions
by Jeff Hammond 14 Aug '23

14 Aug '23

Given that we do most of the work on Zoom, GitHub and Slack now, I wonder if we need a more expansive filter. For example, the following contributed to https://github.com/mpi-forum/mpi-standard/pull/767 in some form. Simon Byrne - California Institute of Technology Lisandro Dalcin - KAUST Jeff On Wed, Aug 9, 2023 at 7:33 PM Wes Bland via mpi-forum < mpi-forum(a)lists.mpi-forum.org> wrote: > > Hi all, > > I just generated an updated list of author names and institutions as they would be published in MPI 4.1. I’ve previously sent out a link with all of the author names, but I forgot to include the institutions that time. Please take a look at this PDF to make sure your information and that of the places you’ve represented in the MPI 4.1 cycle is accurate. I’ve only included the relevant 4 pages. > > https://github.com/mpi-forum/mpi-standard/files/12304747/mpi41-report.pdf > > Thanks, > Wes > _______________________________________________ > mpi-forum mailing list > mpi-forum(a)lists.mpi-forum.org > https://lists.mpi-forum.org/mailman/listinfo/mpi-forum -- Jeff Hammond jeff.science(a)gmail.com http://jeffhammond.github.io/

1 0

We need new dates for the March 2024 meeting
by Martin Schulz 09 Aug '23

09 Aug '23

Hi all, We are planning to hold the March 2024 meeting in the Chicago area – U of I graciously has offered space in the Big Ten Center close to O’Hare airport. Unfortunately, the dates we originally had in mind will not work. Here are the alternate dates currently held for us: Option 1: reduce to 2 days (Feb 27/28) only Option 2: March 4-8 , note this conflicts with SIAM-PP in Baltimore Option 3: March 18-22 (a bit later than usual) Are there any particular preferences or major conflicts? How big is the conflict with SIAM? Please let me know in the next few days. 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

MPI 4.1 Author Names and Institutions
by Wes Bland 09 Aug '23

09 Aug '23

Hi all, I just generated an updated list of author names and institutions as they would be published in MPI 4.1. I’ve previously sent out a link with all of the author names, but I forgot to include the institutions that time. Please take a look at this PDF to make sure your information and that of the places you’ve represented in the MPI 4.1 cycle is accurate. I’ve only included the relevant 4 pages. https://github.com/mpi-forum/mpi-standard/files/12304747/mpi41-report.pdf Thanks, Wes

1 0

Re: [Mpi-forum] Question about MPI activities text in in mpi-4.x branch
by Gropp, William D 04 Aug '23

04 Aug '23

Here’s the rule on index entries: They can’t have any TeX/LaTeX commands in them, because of how the indexing software sorts them. The indexing package provides a workaround – you can create an index item with Text with no commands for indexing@Text with commands for display. E.g., \index{decoupled MPI activities@decoupled \MPI/ activities} Unfortunately, I didn’t make the \mpiterm etc. macros fancy enough to do this decoding. So Howard is correct – the longer form with separate mpitermni and mpitermindex is the correct solution. I could add a macro to make this a little easier – e.g., \mpitermsp{index key for sorting}{index name for display} (sp for special); e.g., \mpitermsp{decoupled MPI activities}{decoupled \MPI/ activities} This would only work for one level index entries, but that is most of them. Bill William Gropp Director, NCSA Thomas M. Siebel Chair in Computer Science University of Illinois Urbana-Champaign From: mpi-forum <mpi-forum-bounces(a)lists.mpi-forum.org> on behalf of Pritchard Jr., Howard via mpi-forum <mpi-forum(a)lists.mpi-forum.org> Date: Friday, August 4, 2023 at 9:45 AM To: mpi-forum <mpi-forum(a)lists.mpi-forum.org> Subject: [Mpi-forum] Question about MPI activities text in in mpi-4.x branch Hi, So I’m reviewing dynamic process chapter in preparation for the RC meeting. I’m noticing some funny text decoupled MPI activities@decoupled MPI activities scattered throughout the text. It looks like this is at least partially associated with e9cba2e0. It appears to me that what we are actually wanting to use is this? \mpitermni{decoupled \MPI/ activities}\mpitermindex{decoupled MPI activities@decoupled \MPI/ activities} as opposed to this \mpiterm{decoupled MPI activities@decoupled \MPI/ activities} ? If we agreed to have funny text with activities@decoupled scattered around then that’s that and I’ll not make a change in the dynamic process chapter. Howard — [signature_61897647] Howard Pritchard Research Scientist HPC-ENV Los Alamos National Laboratory howardp(a)lanl.gov [signature_1861916597]<https://urldefense.com/v3/__https:/www.instagram.com/losalamosnatlab/__;!!D…>[signature_158311116]<https://urldefense.com/v3/__https:/twitter.com/LosAlamosNatLab__;!!DZ3fjg!4…>[signature_3567039719]<https://urldefense.com/v3/__https:/www.linkedin.com/company/los-alamos-nati…>[signature_1636699240]<https://urldefense.com/v3/__https:/www.facebook.com/LosAlamosNationalLab/__…>

1 0

Question about MPI activities text in in mpi-4.x branch
by Pritchard Jr., Howard 04 Aug '23

04 Aug '23

Hi, So I’m reviewing dynamic process chapter in preparation for the RC meeting. I’m noticing some funny text decoupled MPI activities@decoupled MPI activities scattered throughout the text. It looks like this is at least partially associated with e9cba2e0. It appears to me that what we are actually wanting to use is this? \mpitermni{decoupled \MPI/ activities}\mpitermindex{decoupled MPI activities@decoupled \MPI/ activities} as opposed to this \mpiterm{decoupled MPI activities@decoupled \MPI/ activities} ? If we agreed to have funny text with activities@decoupled scattered around then that’s that and I’ll not make a change in the dynamic process chapter. Howard — [signature_61897647] Howard Pritchard Research Scientist HPC-ENV Los Alamos National Laboratory howardp(a)lanl.gov [signature_1861916597]<https://www.instagram.com/losalamosnatlab/>[signature_158311116]<https://twitter.com/LosAlamosNatLab>[signature_3567039719]<https://www.linkedin.com/company/los-alamos-national-laboratory/>[signature_1636699240]<https://www.facebook.com/LosAlamosNationalLab/>

1 0

MPI Forum VOTING BLOCK open until 1pm US CT
by Martin Schulz 12 Jul '23

12 Jul '23

Hi all, Just as a reminder – we will not meet anymore today or tomorrow for the MPI forum meeting, as we (almost) concluded yesterday. However, one item is still open – if you haven’t done so, please remember to vote for the remaining outstanding errata votes. If you are eligible you should have gotten an email with the voting link yesterday. The voting block will stay open until 1pm US CT, i.e., for about the next 4 hours. 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

July 2023 MPI Forum Meeting Wrap Up
by Wes Bland 11 Jul '23

11 Jul '23

Hi all, A few things to wrap up the July meeting: Today’s voting results are now posted on the website: https://www.mpi-forum.org/meetings/2023/07/votes All of the ballots passed. This means we will not meet synchronously tomorrow, though we will have the votes for the remaining errata items. You’ll receive another email to vote on that shortly. The slides that I presented today about the next steps toward MPI 4.1 are available online: Google Slides <https://docs.google.com/presentation/d/1hCgTAz8WP4uRKSTX06t9CM9tUO1dkeWzoW5…> PDF <https://github.com/mpi-forum/mpi-forum.github.io/blob/master/slides/2023/07…> Here’s the immediate action items for folks from that slide deck: Chapter committees have from now through the end of July to make last minute changes before we stop accepting changes for the MPI 4.1 release candidate. Create any PRs ASAP. The list of remaining items is here: https://github.com/orgs/mpi-forum/projects/1/views/9 Chapter committees need to be updated as there is a non-trivial amount of work that we will need from each of you for the next few months. If you’re not active in the MPI Forum anymore or can’t be active for the next couple of months, it’s probably best to step aside from the committee. If you’re not on a committee and would like to be (or vice versa), reach out to the chair of that committee. If you’re a chair of a committee and don’t want to be, reach out to Martin and I. More instructions for what the CCs need to do are in the slides. Everyone should review their name in my list of MPI 4.1 authors. You can find it here: https://docs.google.com/spreadsheets/d/16o1Zf0YGGEIHIn9ULp9IodBok2TF2YNKEFH… Leave a comment (or email me) if you would like a change. This list is everyone who has attended a voting meeting since MPI 4.0. If you feel there is someone else who should be on the list, please let me know (e.g., active in a working group). There’s another list in there for RCM reviewers. Please ignore that for now as the page numbers will be changed once the RC document is ready to go. If you’d like to be a reviewer and aren’t on that least, let me know. I’ve included everyone who has been active in the forum over the last year (3 of the last 5 meetings). Officer nominations will open at the next meeting for the next MPI Standard release cycle. Please consider now if you would like to nominate someone or be nominated. There was some discussion of creating co-officer positions or deputy officer positions to set up succession. If this is something you’d be interested in, please let me know and I can think about what tweaks we might need to make to the rules to formalize. We can also do this informally. That’s all for now. Thanks for a productive meeting this week and I’m looking forward to finishing MPI 4.1. Thanks, Wes

1 0