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

No Virtual MPI Forum Meeting today
by Martin Schulz 29 Sep '21

29 Sep '21

Hi all, We'll have no virtual MPI Forum meeting today - so far, no forum wide discussions are ready from the side of the WGs and there wasn't much progress in direction of MPI 4.1, yet. For the latter, please take a look at the project board and see if you have an issue assigned to you and/or if there is something in a WG you are part of that should be pushed forward. Here is a link to the board: https://github.com/mpi-forum/mpi-issues/projects/3 In particular, it would be great of all Chapter Committee leads could look at the issues labeled "All CCs Must Check" https://github.com/mpi-forum/mpi-issues/projects/3?card_filter_query=label%… and see if the changes for the respective chapter is still missing for that issue. 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

No Meeting Today
by Martin Schulz 22 Sep '21

22 Sep '21

Hi all, Since I noticed some logins into Zoom: after the last full voting meeting, we said that we would skip for 2 weeks and then pick up again (at least I thought/hope we did). Sorry if there was any confusion. If there any particular topics for next week, please let Wesley and me know - otherwise, we'll use next week to continue to push on MPI 4.1 (or pick up left-over topics from the last meeting). 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] EuroMPI Starts Today, MPI-Forum starts Thursday, Joint Session on Wednesday
by Wesley Bland 08 Sep '21

08 Sep '21

I just want to remind people one last time to register for the MPI Forum that begins tomorrow (Thursday). There’s still a few more orgs that I’m expecting to attend, but haven’t heard from. Remember that you must have registered and attended the meeting before the first voting block, which is scheduled for Thursday at 12:30pm US Central. If you register and the join the meeting right at that moment, so please do so ASAP. Logistical information is available on the website: https://www.mpi-forum.org/meetings/2021/09/logistics <https://www.mpi-forum.org/meetings/2021/09/logistics> Thanks, Wes > On Sep 6, 2021, at 11:34 PM, Martin Schulz via mpi-forum <mpi-forum(a)lists.mpi-forum.org> wrote: > > Hi all, > > Just as a quick reminder, EuroMPI and the MPI Forum will be this week, with a joint session between the two on Wednesday (more below). If you haven't registered, yet, please do so at https://www.eurompi21.lrz.de/ - registration is free! > > > EuroMPI 2021 > ============ > > EuroMPI 2021 starts today with a keynote by Olga Pearce and several paper presentations plus a poster/open discussion session. Tomorrow (Wednesday) we will have two topical sessions on RMA and MPI Sessions where we will look into the future of these two important concepts - more on this below. The conference will run 9am to 1pm US CT each day. > > > September MPI Forum > =================== > > Starting Thursday we will transition into the MPI Forum starting on Thursday with plenary discussions, mainly focusing on MPI 4.1 - the agenda is at https://www.mpi-forum.org/meetings/2021/09/agenda. The forum will run 9am to 1pm US CT each day. > > > Joint Session on Wendesday > ======================= > > In the spirit of bringing EuroMPI closer to the activities of the MPI Forum, we will use the second day of EuroMPI to discuss perspectives on two important topics for MPI 5.0: RMA and Sessions - for each topic we will have a separate session starting with a vision talk by Bill Gropp for RMA and Dan Holmes for Session, followed by three paper presentations on these topics, and then an interactive panel discussion. While officially part of EuroMPI, this will also guide discussions in the forum - therefore, we also invite all Forum participants to join us in this session (please register for the conference to get the link - it is free!) > > > Looking forward to seeing/hearing you all this week! > > Best regards, > > 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 > > > > > _______________________________________________ > 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] Questions on MPI Standard formatting
by Gropp, William D 08 Sep '21

08 Sep '21

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: schulzm(a)in.tum.de<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]>> 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]>> 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]> 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…>

1 0

Re: [Mpi-forum] EuroMPI Starts Today, MPI-Forum starts Thursday, Joint Session on Wednesday
by Guillaume Mercier 07 Sep '21

07 Sep '21

Hi Martin, I won't be available on Thursday, but I'll be here on Friday (for sure) and probably tomorrow. I've got a very simple errata to read regarding wrong examples in the partitioned comms chapter. Since it's very straightforward, I think anybody could do it or if you want me to do it, then this reading should be programmed on thursday I guess. Thanks Guillaume On 9/7/21 6:34 AM, Martin Schulz via mpi-forum wrote: > Hi all, > > Just as a quick reminder, EuroMPI and the MPI Forum will be this week, with a joint session between the two on Wednesday (more below). If you haven't registered, yet, please do so at https://www.eurompi21.lrz.de/ - registration is free! > > > EuroMPI 2021 > ============ > > EuroMPI 2021 starts today with a keynote by Olga Pearce and several paper presentations plus a poster/open discussion session. Tomorrow (Wednesday) we will have two topical sessions on RMA and MPI Sessions where we will look into the future of these two important concepts - more on this below. The conference will run 9am to 1pm US CT each day. > > > September MPI Forum > =================== > > Starting Thursday we will transition into the MPI Forum starting on Thursday with plenary discussions, mainly focusing on MPI 4.1 - the agenda is at https://www.mpi-forum.org/meetings/2021/09/agenda. The forum will run 9am to 1pm US CT each day. > > > Joint Session on Wendesday > ======================= > > In the spirit of bringing EuroMPI closer to the activities of the MPI Forum, we will use the second day of EuroMPI to discuss perspectives on two important topics for MPI 5.0: RMA and Sessions - for each topic we will have a separate session starting with a vision talk by Bill Gropp for RMA and Dan Holmes for Session, followed by three paper presentations on these topics, and then an interactive panel discussion. While officially part of EuroMPI, this will also guide discussions in the forum - therefore, we also invite all Forum participants to join us in this session (please register for the conference to get the link - it is free!) > > > Looking forward to seeing/hearing you all this week! > > Best regards, > > Martin > > >

1 0

EuroMPI Starts Today, MPI-Forum starts Thursday, Joint Session on Wednesday
by Martin Schulz 06 Sep '21

06 Sep '21

Hi all, Just as a quick reminder, EuroMPI and the MPI Forum will be this week, with a joint session between the two on Wednesday (more below). If you haven't registered, yet, please do so at https://www.eurompi21.lrz.de/ - registration is free! EuroMPI 2021 ============ EuroMPI 2021 starts today with a keynote by Olga Pearce and several paper presentations plus a poster/open discussion session. Tomorrow (Wednesday) we will have two topical sessions on RMA and MPI Sessions where we will look into the future of these two important concepts - more on this below. The conference will run 9am to 1pm US CT each day. September MPI Forum =================== Starting Thursday we will transition into the MPI Forum starting on Thursday with plenary discussions, mainly focusing on MPI 4.1 - the agenda is at https://www.mpi-forum.org/meetings/2021/09/agenda. The forum will run 9am to 1pm US CT each day. Joint Session on Wendesday ======================= In the spirit of bringing EuroMPI closer to the activities of the MPI Forum, we will use the second day of EuroMPI to discuss perspectives on two important topics for MPI 5.0: RMA and Sessions - for each topic we will have a separate session starting with a vision talk by Bill Gropp for RMA and Dan Holmes for Session, followed by three paper presentations on these topics, and then an interactive panel discussion. While officially part of EuroMPI, this will also guide discussions in the forum - therefore, we also invite all Forum participants to join us in this session (please register for the conference to get the link - it is free!) Looking forward to seeing/hearing you all this week! Best regards, 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] Questions on MPI Standard formatting
by Michael Klemm 06 Sep '21

06 Sep '21

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> 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> Cc: William Gropp <wgropp(a)illinois.edu> 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: schulzm(a)in.tum.de <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]>> 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]>> 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]> 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 <mailto:[email protected]> mpi-forum(a)lists.mpi-forum.org <https://urldefense.com/v3/__https:/lists.mpi-forum.org/mailman/listinfo/mpi…> 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 Sep '21

06 Sep '21

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> 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: schulzm(a)in.tum.de <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/mp…> > > > -- > 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/mp…>

1 0

Re: [Mpi-forum] Questions on MPI Standard formatting
by Joseph Schuchart 05 Sep '21

05 Sep '21

I definitely prefer the second (less bold) version over the first (bold) version. Would you mind sharing the branch containing the changes? I'd like to play around with the fonts myself to see what is and isn't possible. Thanks Joseph On 9/3/21 5:46 PM, Gropp, William D 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/mp…> >>>> <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 Martin Schulz 05 Sep '21

05 Sep '21

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: schulzm(a)in.tum.de From: mpi-forum <mpi-forum-bounces(a)lists.mpi-forum.org> on behalf of "Jeff Squyres (jsquyres) via mpi-forum" <mpi-forum(a)lists.mpi-forum.org> Reply-To: Main MPI Forum mailing list <mpi-forum(a)lists.mpi-forum.org> Date: Saturday, 4. September 2021 at 19:33 To: MPI Forum list <mpi-forum(a)lists.mpi-forum.org> Cc: "Jeff Squyres (jsquyres)" <jsquyres(a)cisco.com> 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> 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> 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]>> 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]>> 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]> 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… <mpi40-report-9-3-code.pdf>_______________________________________________ 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