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

Update from the MPI Forum: Next MPI Meetings
by Martin Schulz 10 Dec '21

10 Dec '21

Hi all, Thanks to all for a quite productive (and at times intense) meeting last week. I think we made good progress on several issues. For those who were not there at the end, we also covered next meetings - Wesley already put them on the website (thanks!), but here is a summary as well: - We decided to make the next meeting virtual again - it will be in the week of Feb. 28. The exact number of days and the timing will be decided again closer to the meeting, depending on the agenda. Expect a 9am CT start, though, and likely 3 or 4 hours for each day (as we had it up to now as well) - The May meeting will be in the week of May 23rd (after the OpenMP F2F, before ISC and IPDPS) - this meeting will either be virtual or hybrid, with a preference of hybrid if we can make it work safely. In this case, we are still looking for organizations that can host us and that have a good setup for hybrid meetings. If you would be willing to be a host, please let Wesley and me know. Until the Feb/Mar meeting, we will have a series of virtual meetings in our usual 2h slot at 10am CT on Wednesdays (starting in January after the holidays). To make things more easily accessible, we already specified the topics: 12 January, 10:00 - 12:00 - RMA Terms (Joseph S) 19 January, 10:00 - 12:00 - Logical Concurrency (Dan H) 26 January, 10:00 - 12:00 - HW Topologies (Guillaume M) 2 February, 10:00 - 12:00 - Tools WG Topics (Marc-Andre H) 9 February, 10:00 - 12:00 - Continuations (Joseph S) 16 February, 10:00 - 12:00 - Hybrid / Accelerators Discussions (Jim D) 23 February, 10:00 - 12:00 - Logical Concurrency (Dan H) No Meetings anymore in December With that, happy holidays to all of you and see you all in the new year! 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-Forum Dec. 21: No Meeting Wednesday, Next Meeting Thursday, Remaining Agenda
by Martin Schulz 07 Dec '21

07 Dec '21

Hi all, As discussed during the meeting today, we will skip tomorrow's MPI Forum meeting and we will continue on Thursday in the usual time-slot 9am CT. Here is the remaining agenda: - Strawpoll on next steps for the "logical concurrency" issue discussed today - Dan has sent the slides from today around, please take a look at them before the meeting on Thursday (we don't plan a long discussion, just the strawpoll after everyone had some time to think about it) - Bill's discussion on "Feedback on proposed changes to the appearance of the code and examples" - Joseph's two discussions on RMA topics (Issue 407 and Issue 6) - Scheduling of the virtual meetings in the coming weeks (please let me know if you have any topics that you would like to lead/present/see) - I would like to go back to scheduling them ahead of time, for more predictable schedule planning - Discussion on the next forum dates and locations. In June we had tentatively decided on 2/28-3/4 and 5/23-27 based on various constraints and conflicts, but we left the actual decision open on whether we want Virtual, Hybrid or In-Person (and in the last two options) where? 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

December 2021 Meeting Voting Block
by Wesley Bland 06 Dec '21

06 Dec '21

Hi all, I just wanted to update folks so it’s clear when we’ll have our voting block this meeting. We did not use the voting block today, but we do plan to use tomorrow’s time slot (11:00am - 11:15am US Central <https://time.is/1100AM_6_December_2021_in_CT>) as our one and only voting block for this meeting. That means that if you missed the meeting today, you still have time to attend tomorrow before that time and be eligible to vote. My capture of those who were present today is on the attendance page <https://www.mpi-forum.org/meetings/2021/12/attendance>, Please double check that I have your attendance correct there. We will vote on two items tomorrow: * Errata - •#449 - Fix wrong term "Cartesian process group" in section 8.5.6 * No-no - •#525 - Add new error class MPI_ERR_ERRHANDLER Item #511 was withdrawn from this meeting. Full details can be found on the agenda page: https://www.mpi-forum.org/meetings/2021/12/agenda <https://www.mpi-forum.org/meetings/2021/12/agenda> Thanks, Wes

1 0

Re: [Mpi-forum] Questions on MPI Standard formatting
by Jeff Squyres (jsquyres) 06 Dec '21

06 Dec '21

I re-state what I sent on 9/4: I think the PDFs sent around on 9/2 were great. I'd love to see that kind of stuff incorporated into the doc. -- Jeff Squyres jsquyres(a)cisco.com ________________________________________ From: mpi-forum <mpi-forum-bounces(a)lists.mpi-forum.org> on behalf of William Gropp via mpi-forum <mpi-forum(a)lists.mpi-forum.org> Sent: Monday, December 6, 2021 9:51 AM To: Main MPI Forum mailing list Cc: William Gropp Subject: Re: [Mpi-forum] Questions on MPI Standard formatting Thanks. However, I haven’t gotten much other feedback on this direction; it seems that the Forum prefers the original, unhighlighted version. Bill William Gropp Director, NCSA Thomas M. Siebel Chair in Computer Science University of Illinois Urbana-Champaign IEEE-CS President-Elect On Dec 6, 2021, at 8:48 AM, Benson Muite via mpi-forum <mpi-forum(a)lists.mpi-forum.org<mailto:[email protected]>> wrote: If Python will be required, Minted[1] and Pythontex[2] and are open source and maintained by a Geoffrey Poore[3]. They could probably be adapted a little if required. Color syntax highlighting might be nice for an online PDF version, though the current color scheme seems better suited for printing. [1]https://urldefense.com/v3/__https://github.com/gpoore/minted__;!!DZ3fjg!u… [2]https://urldefense.com/v3/__https://github.com/gpoore/pythontex/__;!!DZ3f… [3]https://urldefense.com/v3/__https://www.uu.edu/employee/profile.cfm?emp=g… On 9/8/21 9:49 PM, Gropp, William D via mpi-forum wrote: Todd, Thanks for reminding me of inconsolata. Attached is the same page, using that font. Bill William Gropp Director, NCSA Thomas M. Siebel Chair in Computer Science University of Illinois Urbana-Champaign IEEE-CS President-Elect On Sep 6, 2021, at 11:22 PM, Gamblin, Todd <gamblin2(a)llnl.gov<mailto:[email protected]> <mailto:[email protected]>> wrote: I’ll second this just to put in a plug for minted (the LaTeX package that uses pygmentize) as a great replacement for listings, assuming you’re already requiring python. It’s got much more customizable syntax highlighting, mainly because the highlighting isn’t done in pure LaTeX — it’s offloaded to a much more widely used code highlighting package. IMO it looks better, too. Overleaf has some examples here: https://urldefense.com/v3/__https://www.overleaf.com/learn/latex/Code_Highl… <https://urldefense.com/v3/__https://www.overleaf.com/learn/latex/Code_Highl…> One other suggestion for readability would be to use a font other than courier/typewriter for the monospace code blocks. The Inconsolata package comes with most TeX distributions these days: \usepackage{inconsolata} More on the font: https://urldefense.com/v3/__https://en.wikipedia.org/wiki/Inconsolata__;!!D… <https://urldefense.com/v3/__https://en.wikipedia.org/wiki/Inconsolata__;!!D…> — it’s sans-serif and designed for code examples, terminals, etc. -Todd On Sep 6, 2021, at 7:53 AM, Michael Klemm via mpi-forum <mpi-forum(a)lists.mpi-forum.org<mailto:[email protected]> <mailto:[email protected]>> wrote: Hi Bill, That would call for something like Pygments. Especially, if we already require a Python installation, Pygments can be a powerful replacement for listings. Kind regards, -michael *From:*mpi-forum <mpi-forum-bounces(a)lists.mpi-forum.org<mailto:[email protected]> <mailto:[email protected]>>*On Behalf Of*William Gropp via mpi-forum *Sent:*Montag, 6. September 2021 16:51 *To:*Main MPI Forum mailing list <mpi-forum(a)lists.mpi-forum.org<mailto:[email protected]> <mailto:[email protected]>> *Cc:*William Gropp <wgropp(a)illinois.edu<mailto:[email protected]> <mailto:[email protected]>> *Subject:*Re: [Mpi-forum] Questions on MPI Standard formatting On the MPI_Waitsome/MPI_Wait - this is a bug in the lstlisting package. We had lots of trouble with this in the Using MPI books when we switched, but were usually able to get it to work through various hacks. Long term, it might be better to move the highlighting out of LaTeX and process it as part of the “render” step. Bill William Gropp Director, NCSA Thomas M. Siebel Chair in Computer Science University of Illinois Urbana-Champaign IEEE-CS President-Elect On Sep 5, 2021, at 3:23 AM, Martin Schulz via mpi-forum <mpi-forum(a)lists.mpi-forum.org<mailto:[email protected]> <mailto:[email protected]>> wrote: Hi Bill, all, I also agree with what has been said so far and I also agree with the statement that if we don’t find a good solution for tables, leaving it off there is not a big problem (lines should be easily identified there. As for the syntax highlighting – I personally don’t mind it sticking out, but I can also see Joseph’s point – perhaps something between the two version would work. One question, though: in the example that goes over two pages, the “MPI_Waitsome” call is only bold for “MPI_Wait” and not bold for “some” – is this an annotation bug or a problem with the package of not detecting prefixes correctly? 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:[email protected]<mailto:[email protected]> <mailto:[email protected]> *From:*mpi-forum <mpi-forum-bounces(a)lists.mpi-forum.org<mailto:[email protected]> <mailto:[email protected]>> on behalf of "Jeff Squyres (jsquyres) via mpi-forum" <mpi-forum(a)lists.mpi-forum.org<mailto:[email protected]> <mailto:[email protected]>> *Reply-To:*Main MPI Forum mailing list <mpi-forum(a)lists.mpi-forum.org<mailto:[email protected]> <mailto:[email protected]>> *Date:*Saturday, 4. September 2021 at 19:33 *To:*MPI Forum list <mpi-forum(a)lists.mpi-forum.org<mailto:[email protected]> <mailto:[email protected]>> *Cc:*"Jeff Squyres (jsquyres)" <jsquyres(a)cisco.com<mailto:[email protected]> <mailto:[email protected]>> *Subject:*Re: [Mpi-forum] Questions on MPI Standard formatting I am in agreement with all that has been said so far -- generally, this is great. Minor tweaks (already cited by George and Joseph) would be nice improvements. On Sep 3, 2021, at 5:46 PM, Gropp, William D via mpi-forum <mpi-forum(a)lists.mpi-forum.org<mailto:[email protected]> <mailto:[email protected]>> wrote: One option is to use a different font; the one I used in the first examples has a strong bold. Here’s the same page with a different font with a less bold look. In some ways, this may go too far in the other direction - the bold text is a little heavier, but the difference is slight. One advantage of this choice is that the code text is not quite as wide as with the font choice for the previous example, which works better with the current code examples. Let me know your preference. It is easy to change, modulo the issue of needing to wrap a few lines of code. Bill William Gropp Director, NCSA Thomas M. Siebel Chair in Computer Science University of Illinois Urbana-Champaign IEEE-CS President-Elect On Sep 3, 2021, at 1:40 PM, Joseph Schuchart via mpi-forum <mpi-forum(a)lists.mpi-forum.org<mailto:[email protected]> <mailto:[email protected]>> wrote: I am OK with leaving out line numbers in tables. Maybe that will be solved in the future. One comment I had was on the code formatting. While I definitely prefer the lstlistings formatting over the verbatim we have so far, I find the bold highlighting somewhat distracting. I find it hard to focus on the surrounding code pieces. Would it be possible to tone down the highlighting somewhat (slightly thinner, maybe grey)? Thanks Joseph On 9/3/21 2:36 PM, William Gropp via mpi-forum wrote: Thanks, George. On the line numbering, unfortunately, this is very difficult to fix (and is a known problem). My proposal instead is to not use the line numbers in these cases; in the rare cases where we need to identify the location, we can count rows in the table or otherwise identify the line. There are some alternatives, but they are awkward and IMHO ugly, and don’t add much. Bill William Gropp Director, NCSA Thomas M. Siebel Chair in Computer Science University of Illinois Urbana-Champaign IEEE-CS President-Elect On Sep 3, 2021, at 12:19 PM, George Bosilca <bosilca(a)icl.utk.edu<mailto:[email protected]> <mailto:[email protected]><mailto:[email protected] <mailto:[email protected]>>> wrote: Bill, These PDFs looks great, a clear leap forward in improving the readability and cleanness of the MPI standard. The only issue I noticed (and that was pinpointed in your email) was about the multi-page tabular where the numbering is done consecutively for the entire tabular environment despite the fact that the table is split across multiple pages, and the numbers are placed on the same side as the first page on all pages. If we can fix this to have the line numbers per page and on the correct side for all environments, that would be great. Thanks, George. On Thu, Sep 2, 2021 at 11:03 Gropp, William D via mpi-forum <mpi-forum(a)lists.mpi-forum.org<mailto:[email protected]> <mailto:[email protected]><mailto:[email protected] <mailto:[email protected]>>> wrote: I’ve been experimenting with updating the MPI Forum document formatting, and in particular, modernizing the use of LaTeX and reducing the custom LaTeX in the document. Attached are a few pages from my tests. These show: 1) Use of the lineno package to label each line of text - this replaces the ruler currently used, and means that text is more accurately labeled, but “boxes”, including tables, figures, and captions may not have line numbers. All of the attached pages show the line numbers in the margins. 2) Use of the lstlisting package, with syntax and MPI routine highlighting. This also sets a background to gray to help the code examples standout. The approach used in MPI 4.0 creates a box with a border; because of the box, in that approach, the individual lines of code are not numbered. Hence this change in how code examples are marked off. The attached examples show both one page and a code example that spans two pages. 3) There is a way to include numbering for tabular environments (and some others). However, this can lead to some odd labeling, because of how the labeling is implemented within the various LaTeX packages. I’ve included some examples which show both the expected behavior (consecutive numbering) and the unexpected (and nearly impossible to fix) non-consecutive numbering. 4) I’ve also switched from the book to the srcbook document class. This is a more modern and powerful document class, and has allowed me to remove some of the custom LaTeX code. I’d like feedback on these. I’d like to adopt some of these for the next version. In particular: 1) Use srcbook instead of book 2) Use lstlisting in code examples as shown here 3) For tabular environments, do NOT use line numbers for tabular environments used within a table (or other floating) environment. This is where the weird line numbering can happen (e.g., see the attached page 32). For inline tabular environments, use edtable to get line numbers (this is what was used in these examples, and it has worked well in other parts of the document) If you have suggestions for improvements or alternatives, please let me know. Bill William Gropp Director, NCSA Thomas M. Siebel Chair in Computer Science University of Illinois Urbana-Champaign IEEE-CS President-Elect _______________________________________________ mpi-forum mailing list mpi-forum(a)lists.mpi-forum.org<mailto:[email protected]> <mailto:[email protected]><mailto:[email protected] <mailto:[email protected]>> https://urldefense.com/v3/__https://lists.mpi-forum.org/mailman/listinfo/mp… <https://urldefense.com/v3/__https:/lists.mpi-forum.org/mailman/listinfo/mpi…> <https://urldefense.com/v3/__https://lists.mpi-forum.org/mailman/listinfo/mp… <https://urldefense.com/v3/__https:/lists.mpi-forum.org/mailman/listinfo/mpi…>> _______________________________________________ mpi-forum mailing list mpi-forum(a)lists.mpi-forum.org<mailto:[email protected]> <mailto:[email protected]> https://urldefense.com/v3/__https://lists.mpi-forum.org/mailman/listinfo/mp… <https://urldefense.com/v3/__https:/lists.mpi-forum.org/mailman/listinfo/mpi…> _______________________________________________ mpi-forum mailing list mpi-forum(a)lists.mpi-forum.org<mailto:[email protected]> <mailto:[email protected]> https://urldefense.com/v3/__https://lists.mpi-forum.org/mailman/listinfo/mp… <https://urldefense.com/v3/__https:/lists.mpi-forum.org/mailman/listinfo/mpi…> <mpi40-report-9-3-code.pdf>_______________________________________________ mpi-forum mailing list mpi-forum(a)lists.mpi-forum.org<mailto:[email protected]> <mailto:[email protected]> https://urldefense.com/v3/__https://lists.mpi-forum.org/mailman/listinfo/mp… <https://urldefense.com/v3/__https:/lists.mpi-forum.org/mailman/listinfo/mpi…> -- Jeff Squyres jsquyres(a)cisco.com<mailto:[email protected]> <mailto:[email protected]> _______________________________________________ mpi-forum mailing list mpi-forum(a)lists.mpi-forum.org<mailto:[email protected]> <mailto:[email protected]> https://urldefense.com/v3/__https://lists.mpi-forum.org/mailman/listinfo/mp… <https://urldefense.com/v3/__https:/lists.mpi-forum.org/mailman/listinfo/mpi…> _______________________________________________ mpi-forum mailing list mpi-forum(a)lists.mpi-forum.org<mailto:[email protected]> <mailto:[email protected]> https://urldefense.com/v3/__https://lists.mpi-forum.org/mailman/listinfo/mp… <https://urldefense.com/v3/__https://lists.mpi-forum.org/mailman/listinfo/mp…> _______________________________________________ mpi-forum mailing list mpi-forum(a)lists.mpi-forum.org<mailto:[email protected]> https://urldefense.com/v3/__https://lists.mpi-forum.org/mailman/listinfo/mp… _______________________________________________ mpi-forum mailing list mpi-forum(a)lists.mpi-forum.org<mailto:[email protected]> https://urldefense.com/v3/__https://lists.mpi-forum.org/mailman/listinfo/mp…

1 0

Re: [Mpi-forum] Questions on MPI Standard formatting
by William Gropp 06 Dec '21

06 Dec '21

Thanks. However, I haven’t gotten much other feedback on this direction; it seems that the Forum prefers the original, unhighlighted version. Bill William Gropp Director, NCSA Thomas M. Siebel Chair in Computer Science University of Illinois Urbana-Champaign IEEE-CS President-Elect > On Dec 6, 2021, at 8:48 AM, Benson Muite via mpi-forum <mpi-forum(a)lists.mpi-forum.org> wrote: > > If Python will be required, Minted[1] and Pythontex[2] and are open source and maintained by a Geoffrey Poore[3]. They could probably be adapted a little if required. Color syntax highlighting might be nice for an online PDF version, though the current color scheme seems better suited for printing. > > [1]https://urldefense.com/v3/__https://github.com/gpoore/minted__;!!DZ3fjg!u… [2]https://urldefense.com/v3/__https://github.com/gpoore/pythontex/__;!!DZ3f… [3]https://urldefense.com/v3/__https://www.uu.edu/employee/profile.cfm?emp=g… > On 9/8/21 9:49 PM, Gropp, William D via mpi-forum wrote: >> Todd, >> Thanks for reminding me of inconsolata. Attached is the same page, using that font. >> Bill >> William Gropp >> Director, NCSA >> Thomas M. Siebel Chair in Computer Science >> University of Illinois Urbana-Champaign >> IEEE-CS President-Elect >>> On Sep 6, 2021, at 11:22 PM, Gamblin, Todd <gamblin2(a)llnl.gov <mailto:[email protected]>> wrote: >>> >>> I’ll second this just to put in a plug for minted (the LaTeX package that uses pygmentize) as a great replacement for listings, assuming you’re already requiring python. It’s got much more customizable syntax highlighting, mainly because the highlighting isn’t done in pure LaTeX — it’s offloaded to a much more widely used code highlighting package. IMO it looks better, too. >>> >>> Overleaf has some examples here: >>> https://urldefense.com/v3/__https://www.overleaf.com/learn/latex/Code_Highl… <https://urldefense.com/v3/__https://www.overleaf.com/learn/latex/Code_Highl…> >>> >>> One other suggestion for readability would be to use a font other than courier/typewriter for the monospace code blocks. The Inconsolata package comes with most TeX distributions these days: >>> >>> \usepackage{inconsolata} >>> >>> More on the font: https://urldefense.com/v3/__https://en.wikipedia.org/wiki/Inconsolata__;!!D… <https://urldefense.com/v3/__https://en.wikipedia.org/wiki/Inconsolata__;!!D…> — it’s sans-serif and designed for code examples, terminals, etc. >>> >>> -Todd >>> >>> >>>> On Sep 6, 2021, at 7:53 AM, Michael Klemm via mpi-forum <mpi-forum(a)lists.mpi-forum.org <mailto:[email protected]>> wrote: >>>> >>>> Hi Bill, >>>> That would call for something like Pygments. Especially, if we already require a Python installation, Pygments can be a powerful replacement for listings. >>>> Kind regards, >>>> -michael >>>> *From:*mpi-forum <mpi-forum-bounces(a)lists.mpi-forum.org <mailto:[email protected]>>*On Behalf Of*William Gropp via mpi-forum >>>> *Sent:*Montag, 6. September 2021 16:51 >>>> *To:*Main MPI Forum mailing list <mpi-forum(a)lists.mpi-forum.org <mailto:[email protected]>> >>>> *Cc:*William Gropp <wgropp(a)illinois.edu <mailto:[email protected]>> >>>> *Subject:*Re: [Mpi-forum] Questions on MPI Standard formatting >>>> On the MPI_Waitsome/MPI_Wait - this is a bug in the lstlisting package. We had lots of trouble with this in the Using MPI books when we switched, but were usually able to get it to work through various hacks. Long term, it might be better to move the highlighting out of LaTeX and process it as part of the “render” step. >>>> Bill >>>> William Gropp >>>> Director, NCSA >>>> Thomas M. Siebel Chair in Computer Science >>>> University of Illinois Urbana-Champaign >>>> IEEE-CS President-Elect >>>> >>>> >>>> >>>> On Sep 5, 2021, at 3:23 AM, Martin Schulz via mpi-forum >>>> <mpi-forum(a)lists.mpi-forum.org >>>> <mailto:[email protected]>> wrote: >>>> Hi Bill, all, >>>> I also agree with what has been said so far and I also agree with >>>> the statement that if we don’t find a good solution for tables, >>>> leaving it off there is not a big problem (lines should be easily >>>> identified there. >>>> As for the syntax highlighting – I personally don’t mind it >>>> sticking out, but I can also see Joseph’s point – perhaps >>>> something between the two version would work. >>>> One question, though: in the example that goes over two pages, >>>> the “MPI_Waitsome” call is only bold for “MPI_Wait” and not bold >>>> for “some” – is this an annotation bug or a problem with the >>>> package of not detecting prefixes correctly? >>>> 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:[email protected] <mailto:[email protected]> >>>> *From:*mpi-forum <mpi-forum-bounces(a)lists.mpi-forum.org >>>> <mailto:[email protected]>> on behalf of >>>> "Jeff Squyres (jsquyres) via mpi-forum" >>>> <mpi-forum(a)lists.mpi-forum.org >>>> <mailto:[email protected]>> >>>> *Reply-To:*Main MPI Forum mailing list >>>> <mpi-forum(a)lists.mpi-forum.org >>>> <mailto:[email protected]>> >>>> *Date:*Saturday, 4. September 2021 at 19:33 >>>> *To:*MPI Forum list <mpi-forum(a)lists.mpi-forum.org >>>> <mailto:[email protected]>> >>>> *Cc:*"Jeff Squyres (jsquyres)" <jsquyres(a)cisco.com >>>> <mailto:[email protected]>> >>>> *Subject:*Re: [Mpi-forum] Questions on MPI Standard formatting >>>> I am in agreement with all that has been said so far -- >>>> generally, this is great. Minor tweaks (already cited by George >>>> and Joseph) would be nice improvements. >>>> >>>> >>>> >>>> On Sep 3, 2021, at 5:46 PM, Gropp, William D via mpi-forum >>>> <mpi-forum(a)lists.mpi-forum.org >>>> <mailto:[email protected]>> wrote: >>>> One option is to use a different font; the one I used in the >>>> first examples has a strong bold. Here’s the same page with >>>> a different font with a less bold look. In some ways, this >>>> may go too far in the other direction - the bold text is a >>>> little heavier, but the difference is slight. >>>> One advantage of this choice is that the code text is not >>>> quite as wide as with the font choice for the previous >>>> example, which works better with the current code examples. >>>> Let me know your preference. It is easy to change, modulo >>>> the issue of needing to wrap a few lines of code. >>>> Bill >>>> William Gropp >>>> Director, NCSA >>>> Thomas M. Siebel Chair in Computer Science >>>> University of Illinois Urbana-Champaign >>>> IEEE-CS President-Elect >>>> >>>> >>>> >>>> >>>> On Sep 3, 2021, at 1:40 PM, Joseph Schuchart via >>>> mpi-forum <mpi-forum(a)lists.mpi-forum.org >>>> <mailto:[email protected]>> wrote: >>>> I am OK with leaving out line numbers in tables. Maybe >>>> that will be solved in the future. >>>> >>>> One comment I had was on the code formatting. While I >>>> definitely prefer the lstlistings formatting over the >>>> verbatim we have so far, I find the bold highlighting >>>> somewhat distracting. I find it hard to focus on the >>>> surrounding code pieces. Would it be possible to tone >>>> down the highlighting somewhat (slightly thinner, maybe >>>> grey)? >>>> >>>> Thanks >>>> Joseph >>>> >>>> On 9/3/21 2:36 PM, William Gropp via mpi-forum wrote: >>>> >>>> >>>> Thanks, George. On the line numbering, >>>> unfortunately, this is very difficult to fix (and is >>>> a known problem). My proposal instead is to not use >>>> the line numbers in these cases; in the rare cases >>>> where we need to identify the location, we can count >>>> rows in the table or otherwise identify the line. >>>> There are some alternatives, but they are awkward and >>>> IMHO ugly, and don’t add much. >>>> >>>> Bill >>>> >>>> William Gropp >>>> Director, NCSA >>>> Thomas M. Siebel Chair in Computer Science >>>> University of Illinois Urbana-Champaign >>>> IEEE-CS President-Elect >>>> >>>> >>>> >>>> >>>> >>>> >>>> On Sep 3, 2021, at 12:19 PM, George Bosilca >>>> <bosilca(a)icl.utk.edu >>>> <mailto:[email protected]><mailto:[email protected] >>>> <mailto:[email protected]>>> wrote: >>>> >>>> Bill, >>>> >>>> These PDFs looks great, a clear leap forward in >>>> improving the readability and cleanness of the >>>> MPI standard. >>>> >>>> The only issue I noticed (and that was pinpointed >>>> in your email) was about the multi-page tabular >>>> where the numbering is done consecutively for the >>>> entire tabular environment despite the fact that >>>> the table is split across multiple pages, and the >>>> numbers are placed on the same side as the first >>>> page on all pages. If we can fix this to have the >>>> line numbers per page and on the correct side for >>>> all environments, that would be great. >>>> >>>> Thanks, >>>> George. >>>> >>>> On Thu, Sep 2, 2021 at 11:03 Gropp, William D via >>>> mpi-forum <mpi-forum(a)lists.mpi-forum.org >>>> <mailto:[email protected]><mailto:[email protected] >>>> <mailto:[email protected]>>> wrote: >>>> >>>> I’ve been experimenting with updating the MPI >>>> Forum document >>>> formatting, and in particular, modernizing the >>>> use of LaTeX and >>>> reducing the custom LaTeX in the document. >>>> Attached are a few >>>> pages from my tests. These show: >>>> >>>> 1) Use of the lineno package to label each >>>> line of text - this >>>> replaces the ruler currently used, and means >>>> that text is more >>>> accurately labeled, but “boxes”, including >>>> tables, figures, and >>>> captions may not have line numbers. All of the >>>> attached pages >>>> show the line numbers in the margins. >>>> 2) Use of the lstlisting package, with syntax >>>> and MPI routine >>>> highlighting. This also sets a background to >>>> gray to help the >>>> code examples standout. The approach used in >>>> MPI 4.0 creates a >>>> box with a border; because of the box, in that >>>> approach, the >>>> individual lines of code are not numbered. Hence this change in >>>> how code examples are marked off. The attached >>>> examples show both >>>> one page and a code example that spans two pages. >>>> 3) There is a way to include numbering for >>>> tabular environments >>>> (and some others). However, this can lead to >>>> some odd labeling, >>>> because of how the labeling is implemented >>>> within the various >>>> LaTeX packages. I’ve included some examples >>>> which show both the >>>> expected behavior (consecutive numbering) and >>>> the unexpected (and >>>> nearly impossible to fix) non-consecutive >>>> numbering. >>>> 4) I’ve also switched from the book to the >>>> srcbook document >>>> class. This is a more modern and powerful >>>> document class, and has >>>> allowed me to remove some of the custom LaTeX >>>> code. >>>> >>>> I’d like feedback on these. I’d like to adopt >>>> some of these for >>>> the next version. In particular: >>>> >>>> 1) Use srcbook instead of book >>>> 2) Use lstlisting in code examples as shown here >>>> 3) For tabular environments, do NOT use line >>>> numbers for tabular >>>> environments used within a table (or other >>>> floating) environment. >>>> This is where the weird line numbering can >>>> happen (e.g., see the >>>> attached page 32). For inline tabular >>>> environments, use edtable >>>> to get line numbers (this is what was used in >>>> these examples, and >>>> it has worked well in other parts of the document) >>>> >>>> If you have suggestions for improvements or >>>> alternatives, please >>>> let me know. >>>> >>>> Bill >>>> >>>> >>>> William Gropp >>>> Director, NCSA >>>> Thomas M. Siebel Chair in Computer Science >>>> University of Illinois Urbana-Champaign >>>> IEEE-CS President-Elect >>>> >>>> >>>> >>>> >>>> _______________________________________________ >>>> mpi-forum mailing list >>>> mpi-forum(a)lists.mpi-forum.org >>>> <mailto:[email protected]><mailto:[email protected] >>>> <mailto:[email protected]>> >>>> https://urldefense.com/v3/__https://lists.mpi-forum.org/mailman/listinfo/mp… >>>> <https://urldefense.com/v3/__https:/lists.mpi-forum.org/mailman/listinfo/mpi…> <https://urldefense.com/v3/__https://lists.mpi-forum.org/mailman/listinfo/mp… >>>> <https://urldefense.com/v3/__https:/lists.mpi-forum.org/mailman/listinfo/mpi…>> >>>> >>>> >>>> >>>> _______________________________________________ >>>> mpi-forum mailing list >>>> mpi-forum(a)lists.mpi-forum.org >>>> <mailto:[email protected]> >>>> https://urldefense.com/v3/__https://lists.mpi-forum.org/mailman/listinfo/mp… >>>> <https://urldefense.com/v3/__https:/lists.mpi-forum.org/mailman/listinfo/mpi…> >>>> >>>> >>>> _______________________________________________ >>>> mpi-forum mailing list >>>> mpi-forum(a)lists.mpi-forum.org >>>> <mailto:[email protected]> >>>> https://urldefense.com/v3/__https://lists.mpi-forum.org/mailman/listinfo/mp… >>>> <https://urldefense.com/v3/__https:/lists.mpi-forum.org/mailman/listinfo/mpi…> >>>> >>>> <mpi40-report-9-3-code.pdf>_______________________________________________ >>>> mpi-forum mailing list >>>> mpi-forum(a)lists.mpi-forum.org >>>> <mailto:[email protected]> >>>> https://urldefense.com/v3/__https://lists.mpi-forum.org/mailman/listinfo/mp… <https://urldefense.com/v3/__https:/lists.mpi-forum.org/mailman/listinfo/mpi…> >>>> >>>> >>>> -- Jeff Squyres >>>> jsquyres(a)cisco.com <mailto:[email protected]> >>>> _______________________________________________ >>>> mpi-forum mailing list >>>> mpi-forum(a)lists.mpi-forum.org <mailto:[email protected]> >>>> https://urldefense.com/v3/__https://lists.mpi-forum.org/mailman/listinfo/mp… >>>> <https://urldefense.com/v3/__https:/lists.mpi-forum.org/mailman/listinfo/mpi…> >>>> >>>> _______________________________________________ >>>> mpi-forum mailing list >>>> mpi-forum(a)lists.mpi-forum.org <mailto:[email protected]> >>>> https://urldefense.com/v3/__https://lists.mpi-forum.org/mailman/listinfo/mp… <https://urldefense.com/v3/__https://lists.mpi-forum.org/mailman/listinfo/mp…> >>> >> _______________________________________________ >> mpi-forum mailing list >> mpi-forum(a)lists.mpi-forum.org >> https://urldefense.com/v3/__https://lists.mpi-forum.org/mailman/listinfo/mp… > > _______________________________________________ > mpi-forum mailing list > mpi-forum(a)lists.mpi-forum.org > https://urldefense.com/v3/__https://lists.mpi-forum.org/mailman/listinfo/mp…

1 0

Re: [Mpi-forum] Questions on MPI Standard formatting
by Benson Muite 06 Dec '21

06 Dec '21

If Python will be required, Minted[1] and Pythontex[2] and are open source and maintained by a Geoffrey Poore[3]. They could probably be adapted a little if required. Color syntax highlighting might be nice for an online PDF version, though the current color scheme seems better suited for printing. [1]https://github.com/gpoore/minted [2]https://github.com/gpoore/pythontex/ [3]https://www.uu.edu/employee/profile.cfm?emp=gpoore On 9/8/21 9:49 PM, Gropp, William D via mpi-forum wrote: > Todd, > > Thanks for reminding me of inconsolata. Attached is the same page, > using that font. > > Bill > > William Gropp > Director, NCSA > Thomas M. Siebel Chair in Computer Science > University of Illinois Urbana-Champaign > IEEE-CS President-Elect > > > > >> On Sep 6, 2021, at 11:22 PM, Gamblin, Todd <gamblin2(a)llnl.gov >> <mailto:[email protected]>> wrote: >> >> I’ll second this just to put in a plug for minted (the LaTeX package >> that uses pygmentize) as a great replacement for listings, assuming >> you’re already requiring python. It’s got much more customizable >> syntax highlighting, mainly because the highlighting isn’t done in >> pure LaTeX — it’s offloaded to a much more widely used code >> highlighting package. IMO it looks better, too. >> >> Overleaf has some examples here: >> https://www.overleaf.com/learn/latex/Code_Highlighting_with_minted >> <https://urldefense.com/v3/__https://www.overleaf.com/learn/latex/Code_Highl…> >> >> One other suggestion for readability would be to use a font other than >> courier/typewriter for the monospace code blocks. The Inconsolata >> package comes with most TeX distributions these days: >> >> \usepackage{inconsolata} >> >> More on the font: https://en.wikipedia.org/wiki/Inconsolata >> <https://urldefense.com/v3/__https://en.wikipedia.org/wiki/Inconsolata__;!!D…> >> — it’s sans-serif and designed for code examples, terminals, etc. >> >> -Todd >> >> >>> On Sep 6, 2021, at 7:53 AM, Michael Klemm via mpi-forum >>> <mpi-forum(a)lists.mpi-forum.org >>> <mailto:[email protected]>> wrote: >>> >>> Hi Bill, >>> That would call for something like Pygments. Especially, if we >>> already require a Python installation, Pygments can be a powerful >>> replacement for listings. >>> Kind regards, >>> -michael >>> *From:*mpi-forum <mpi-forum-bounces(a)lists.mpi-forum.org >>> <mailto:[email protected]>>*On Behalf Of*William >>> Gropp via mpi-forum >>> *Sent:*Montag, 6. September 2021 16:51 >>> *To:*Main MPI Forum mailing list <mpi-forum(a)lists.mpi-forum.org >>> <mailto:[email protected]>> >>> *Cc:*William Gropp <wgropp(a)illinois.edu <mailto:[email protected]>> >>> *Subject:*Re: [Mpi-forum] Questions on MPI Standard formatting >>> On the MPI_Waitsome/MPI_Wait - this is a bug in the lstlisting >>> package. We had lots of trouble with this in the Using MPI books >>> when we switched, but were usually able to get it to work through >>> various hacks. Long term, it might be better to move the highlighting >>> out of LaTeX and process it as part of the “render” step. >>> Bill >>> William Gropp >>> Director, NCSA >>> Thomas M. Siebel Chair in Computer Science >>> University of Illinois Urbana-Champaign >>> IEEE-CS President-Elect >>> >>> >>> >>> On Sep 5, 2021, at 3:23 AM, Martin Schulz via mpi-forum >>> <mpi-forum(a)lists.mpi-forum.org >>> <mailto:[email protected]>> wrote: >>> Hi Bill, all, >>> I also agree with what has been said so far and I also agree with >>> the statement that if we don’t find a good solution for tables, >>> leaving it off there is not a big problem (lines should be easily >>> identified there. >>> As for the syntax highlighting – I personally don’t mind it >>> sticking out, but I can also see Joseph’s point – perhaps >>> something between the two version would work. >>> One question, though: in the example that goes over two pages, >>> the “MPI_Waitsome” call is only bold for “MPI_Wait” and not bold >>> for “some” – is this an annotation bug or a problem with the >>> package of not detecting prefixes correctly? >>> 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:[email protected] <mailto:[email protected]> >>> *From:*mpi-forum <mpi-forum-bounces(a)lists.mpi-forum.org >>> <mailto:[email protected]>> on behalf of >>> "Jeff Squyres (jsquyres) via mpi-forum" >>> <mpi-forum(a)lists.mpi-forum.org >>> <mailto:[email protected]>> >>> *Reply-To:*Main MPI Forum mailing list >>> <mpi-forum(a)lists.mpi-forum.org >>> <mailto:[email protected]>> >>> *Date:*Saturday, 4. September 2021 at 19:33 >>> *To:*MPI Forum list <mpi-forum(a)lists.mpi-forum.org >>> <mailto:[email protected]>> >>> *Cc:*"Jeff Squyres (jsquyres)" <jsquyres(a)cisco.com >>> <mailto:[email protected]>> >>> *Subject:*Re: [Mpi-forum] Questions on MPI Standard formatting >>> I am in agreement with all that has been said so far -- >>> generally, this is great. Minor tweaks (already cited by George >>> and Joseph) would be nice improvements. >>> >>> >>> >>> On Sep 3, 2021, at 5:46 PM, Gropp, William D via mpi-forum >>> <mpi-forum(a)lists.mpi-forum.org >>> <mailto:[email protected]>> wrote: >>> One option is to use a different font; the one I used in the >>> first examples has a strong bold. Here’s the same page with >>> a different font with a less bold look. In some ways, this >>> may go too far in the other direction - the bold text is a >>> little heavier, but the difference is slight. >>> One advantage of this choice is that the code text is not >>> quite as wide as with the font choice for the previous >>> example, which works better with the current code examples. >>> Let me know your preference. It is easy to change, modulo >>> the issue of needing to wrap a few lines of code. >>> Bill >>> William Gropp >>> Director, NCSA >>> Thomas M. Siebel Chair in Computer Science >>> University of Illinois Urbana-Champaign >>> IEEE-CS President-Elect >>> >>> >>> >>> >>> On Sep 3, 2021, at 1:40 PM, Joseph Schuchart via >>> mpi-forum <mpi-forum(a)lists.mpi-forum.org >>> <mailto:[email protected]>> wrote: >>> I am OK with leaving out line numbers in tables. Maybe >>> that will be solved in the future. >>> >>> One comment I had was on the code formatting. While I >>> definitely prefer the lstlistings formatting over the >>> verbatim we have so far, I find the bold highlighting >>> somewhat distracting. I find it hard to focus on the >>> surrounding code pieces. Would it be possible to tone >>> down the highlighting somewhat (slightly thinner, maybe >>> grey)? >>> >>> Thanks >>> Joseph >>> >>> On 9/3/21 2:36 PM, William Gropp via mpi-forum wrote: >>> >>> >>> Thanks, George. On the line numbering, >>> unfortunately, this is very difficult to fix (and is >>> a known problem). My proposal instead is to not use >>> the line numbers in these cases; in the rare cases >>> where we need to identify the location, we can count >>> rows in the table or otherwise identify the line. >>> There are some alternatives, but they are awkward and >>> IMHO ugly, and don’t add much. >>> >>> Bill >>> >>> William Gropp >>> Director, NCSA >>> Thomas M. Siebel Chair in Computer Science >>> University of Illinois Urbana-Champaign >>> IEEE-CS President-Elect >>> >>> >>> >>> >>> >>> >>> On Sep 3, 2021, at 12:19 PM, George Bosilca >>> <bosilca(a)icl.utk.edu >>> <mailto:[email protected]><mailto:[email protected] >>> <mailto:[email protected]>>> wrote: >>> >>> Bill, >>> >>> These PDFs looks great, a clear leap forward in >>> improving the readability and cleanness of the >>> MPI standard. >>> >>> The only issue I noticed (and that was pinpointed >>> in your email) was about the multi-page tabular >>> where the numbering is done consecutively for the >>> entire tabular environment despite the fact that >>> the table is split across multiple pages, and the >>> numbers are placed on the same side as the first >>> page on all pages. If we can fix this to have the >>> line numbers per page and on the correct side for >>> all environments, that would be great. >>> >>> Thanks, >>> George. >>> >>> On Thu, Sep 2, 2021 at 11:03 Gropp, William D via >>> mpi-forum <mpi-forum(a)lists.mpi-forum.org >>> <mailto:[email protected]><mailto:[email protected] >>> <mailto:[email protected]>>> wrote: >>> >>> I’ve been experimenting with updating the MPI >>> Forum document >>> formatting, and in particular, modernizing the >>> use of LaTeX and >>> reducing the custom LaTeX in the document. >>> Attached are a few >>> pages from my tests. These show: >>> >>> 1) Use of the lineno package to label each >>> line of text - this >>> replaces the ruler currently used, and means >>> that text is more >>> accurately labeled, but “boxes”, including >>> tables, figures, and >>> captions may not have line numbers. All of the >>> attached pages >>> show the line numbers in the margins. >>> 2) Use of the lstlisting package, with syntax >>> and MPI routine >>> highlighting. This also sets a background to >>> gray to help the >>> code examples standout. The approach used in >>> MPI 4.0 creates a >>> box with a border; because of the box, in that >>> approach, the >>> individual lines of code are not numbered. >>> Hence this change in >>> how code examples are marked off. The attached >>> examples show both >>> one page and a code example that spans two pages. >>> 3) There is a way to include numbering for >>> tabular environments >>> (and some others). However, this can lead to >>> some odd labeling, >>> because of how the labeling is implemented >>> within the various >>> LaTeX packages. I’ve included some examples >>> which show both the >>> expected behavior (consecutive numbering) and >>> the unexpected (and >>> nearly impossible to fix) non-consecutive >>> numbering. >>> 4) I’ve also switched from the book to the >>> srcbook document >>> class. This is a more modern and powerful >>> document class, and has >>> allowed me to remove some of the custom LaTeX >>> code. >>> >>> I’d like feedback on these. I’d like to adopt >>> some of these for >>> the next version. In particular: >>> >>> 1) Use srcbook instead of book >>> 2) Use lstlisting in code examples as shown here >>> 3) For tabular environments, do NOT use line >>> numbers for tabular >>> environments used within a table (or other >>> floating) environment. >>> This is where the weird line numbering can >>> happen (e.g., see the >>> attached page 32). For inline tabular >>> environments, use edtable >>> to get line numbers (this is what was used in >>> these examples, and >>> it has worked well in other parts of the document) >>> >>> If you have suggestions for improvements or >>> alternatives, please >>> let me know. >>> >>> Bill >>> >>> >>> William Gropp >>> Director, NCSA >>> Thomas M. Siebel Chair in Computer Science >>> University of Illinois Urbana-Champaign >>> IEEE-CS President-Elect >>> >>> >>> >>> >>> _______________________________________________ >>> mpi-forum mailing list >>> mpi-forum(a)lists.mpi-forum.org >>> <mailto:[email protected]><mailto:[email protected] >>> <mailto:[email protected]>> >>> https://urldefense.com/v3/__https://lists.mpi-forum.org/mailman/listinfo/mp… >>> <https://urldefense.com/v3/__https:/lists.mpi-forum.org/mailman/listinfo/mpi…> <https://urldefense.com/v3/__https://lists.mpi-forum.org/mailman/listinfo/mp… >>> <https://urldefense.com/v3/__https:/lists.mpi-forum.org/mailman/listinfo/mpi…>> >>> >>> >>> >>> _______________________________________________ >>> mpi-forum mailing list >>> mpi-forum(a)lists.mpi-forum.org >>> <mailto:[email protected]> >>> https://urldefense.com/v3/__https://lists.mpi-forum.org/mailman/listinfo/mp… >>> <https://urldefense.com/v3/__https:/lists.mpi-forum.org/mailman/listinfo/mpi…> >>> >>> >>> _______________________________________________ >>> mpi-forum mailing list >>> mpi-forum(a)lists.mpi-forum.org >>> <mailto:[email protected]> >>> https://urldefense.com/v3/__https://lists.mpi-forum.org/mailman/listinfo/mp… >>> <https://urldefense.com/v3/__https:/lists.mpi-forum.org/mailman/listinfo/mpi…> >>> >>> <mpi40-report-9-3-code.pdf>_______________________________________________ >>> mpi-forum mailing list >>> mpi-forum(a)lists.mpi-forum.org >>> <mailto:[email protected]> >>> https://lists.mpi-forum.org/mailman/listinfo/mpi-forum >>> <https://urldefense.com/v3/__https:/lists.mpi-forum.org/mailman/listinfo/mpi…> >>> >>> >>> -- >>> Jeff Squyres >>> jsquyres(a)cisco.com <mailto:[email protected]> >>> _______________________________________________ >>> mpi-forum mailing list >>> mpi-forum(a)lists.mpi-forum.org <mailto:[email protected]> >>> https://urldefense.com/v3/__https://lists.mpi-forum.org/mailman/listinfo/mp… >>> <https://urldefense.com/v3/__https:/lists.mpi-forum.org/mailman/listinfo/mpi…> >>> >>> _______________________________________________ >>> mpi-forum mailing list >>> mpi-forum(a)lists.mpi-forum.org <mailto:[email protected]> >>> https://lists.mpi-forum.org/mailman/listinfo/mpi-forum >>> <https://urldefense.com/v3/__https://lists.mpi-forum.org/mailman/listinfo/mp…> >> > > > _______________________________________________ > mpi-forum mailing list > mpi-forum(a)lists.mpi-forum.org > https://lists.mpi-forum.org/mailman/listinfo/mpi-forum >

1 0

Re: [Mpi-forum] December MPI Forum Meeting Registration Posted / Call For Topics
by Dan Holmes 01 Dec '21

01 Dec '21

Hi Wesley, On behalf of the HACC WG, I would like to reserve some time for a presentation of the recent progress and a discussion of the way(s) forward regarding the “logically concurrent” ambiguity, issue #117 (https://github.com/mpi-forum/mpi-issues/issues/117 <https://github.com/mpi-forum/mpi-issues/issues/117>). Cheers, Dan. — Dr Daniel Holmes PhD Executive Director Chief Technology Officer CHI Ltd danholmes(a)chi.scot > On 11 Nov 2021, at 15:54, Wesley Bland via mpi-forum <mpi-forum(a)lists.mpi-forum.org> wrote: > > Hi all, > > The registration page for the December 2021 meeting from December 6 - 9, 2021 is now posted. Please register here: > > https://forms.gle/FYUSaHSqaL1uwEEv8 <https://forms.gle/FYUSaHSqaL1uwEEv8> > > If you have topics for votes, plenaries, readings, etc., please announce them to this mailing list ASAP. The deadline for those announcements is November 22nd, which is the week of Thanksgiving in the US so many folks may be on vacation that week. > > Thanks, > Wes > _______________________________________________ > mpi-forum mailing list > mpi-forum(a)lists.mpi-forum.org > https://lists.mpi-forum.org/mailman/listinfo/mpi-forum

1 0

Re: [Mpi-forum] December MPI Forum Meeting Registration Posted / Call For Topics
by Joseph Schuchart 01 Dec '21

01 Dec '21

Hi Wesley, If there is still time, I would like to give a high-level overview of MPI Continuations (preferably towards the end of the meeting). I will prepare a couple of slides to introduce the topic, hoping for some early feedback from the broader forum. Thanks Joseph On 11/26/21 2:48 PM, Wesley Bland via mpi-forum wrote: > Hi all, > > As a reminder, we’re about a week away from the December 2021 meeting > and a number of you have still not registered. Please do so at this link: > > https://forms.gle/FYUSaHSqaL1uwEEv8 <https://forms.gle/FYUSaHSqaL1uwEEv8> > > Thanks, > Wes > >> On Nov 11, 2021, at 10:54 AM, Wesley Bland <work(a)wesbland.com >> <mailto:[email protected]>> wrote: >> >> Hi all, >> >> The registration page for the December 2021 meeting from December 6 - >> 9, 2021 is now posted. Please register here: >> >> https://forms.gle/FYUSaHSqaL1uwEEv8 <https://forms.gle/FYUSaHSqaL1uwEEv8> >> >> If you have topics for votes, plenaries, readings, etc., please >> announce them to this mailing list ASAP. The deadline for those >> announcements is November 22nd, which is the week of Thanksgiving in >> the US so many folks may be on vacation that week. >> >> Thanks, >> Wes > > > _______________________________________________ > mpi-forum mailing list > mpi-forum(a)lists.mpi-forum.org > https://lists.mpi-forum.org/mailman/listinfo/mpi-forum

1 0