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

MPI implementations slide
by Balaji, Pavan 14 Nov '15

14 Nov '15

All, Here is the final version of the MPI implementations slide. For the cells that were marked as Q3 '15, for which I didn't get any updates, I've changed it to "no plan to support". We can still change it, as I get updates. But I'm sending this out as people need to finalize their talks for SC. I've added one more MPI implementation (MPC), per the developers' request, so the fonts had to be squeezed a bit. I've gotten a request for another MPI implementation as well, and I told them that this is open for all MPI implementations. But I haven't received the data for it, so it's not included as yet. Martin, can you add this to the Forum website? Thanks, -- Pavan

1 0

Re: [Mpi-forum] MPI Forum Trac now in read-only mode
by Bland, Wesley 13 Nov '15

13 Nov '15

As a reminder, you can still access the old Trac page. What it does mean, is that if you have an issue (ticket) that you want to read/vote on/whatever in San Jose, you should make sure that you’ve moved it over to GitHub before the deadline (a week from Monday) when you send your announcement to the list. If you want some examples, there's quite a few of them in GitHub now that you can use as a template. The wiki is also your friend here. Thanks, Wesley -----Original Message----- From: mpi-forum <mpi-forum-bounces(a)lists.mpi-forum.org> on behalf of Jeff Squyres <jsquyres(a)cisco.com> Reply-To: MPI Forum <mpi-forum(a)lists.mpi-forum.org> Date: Friday, November 13, 2015 at 11:21 AM To: MPI Forum <mpi-forum(a)lists.mpi-forum.org> Subject: [Mpi-forum] MPI Forum Trac now in read-only mode Per https://github.com/mpi-forum/mpi-issues/wiki/Timeline-for-the-Migration, the MPI Forum Trac is now in read-only mode. Viva la GitHub! If you haven't read up on what you're supposed to do yet, the wiki is a great place to start: https://github.com/mpi-forum/mpi-issues/wiki There's a lot of good stuff there for both Git and GitHub newbies. Enjoy! -- Jeff Squyres jsquyres(a)cisco.com For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/ _______________________________________________ mpi-forum mailing list mpi-forum(a)lists.mpi-forum.org http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi-forum

1 0

MPI Forum Trac now in read-only mode
by Jeff Squyres (jsquyres) 13 Nov '15

13 Nov '15

Per https://github.com/mpi-forum/mpi-issues/wiki/Timeline-for-the-Migration, the MPI Forum Trac is now in read-only mode. Viva la GitHub! If you haven't read up on what you're supposed to do yet, the wiki is a great place to start: https://github.com/mpi-forum/mpi-issues/wiki There's a lot of good stuff there for both Git and GitHub newbies. Enjoy! -- Jeff Squyres jsquyres(a)cisco.com For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/

1 0

Initial Agenda for the December Meeting
by Schulz Martin 12 Nov '15

12 Nov '15

Hi all, I put together a first agenda draft for the December meeting (12/7-12/10) in San Jose. It¹s on the webpage at: http://meetings.mpi-forum.org/secretary/2015/12/agenda.php It follows the usual format (Monday 2pm to Thursday noon) with WGs the first part followed by plenaries and votes on Thursday morning. I had a bit more requests for WGs as usual and not so many plenary requests and so the WG time spilled a bit into Thursday morning. Let me know if I missed any major conflicts or agenda items and I¹ll try my best to accommodate everything. Also, please note that official readings, errata proposals, and votes have to be announced by Monday 11/23 (2 weeks before the meeting) and must be associated with an issue number on the new github system. Thanks! Martin ________________________________________________________________________ Martin Schulz, schulzm(a)llnl.gov, http://scalability.llnl.gov/ CASC @ Lawrence Livermore National Laboratory, Livermore, USA

1 0

FTWG Readings for San Jose
by Bland, Wesley 12 Nov '15

12 Nov '15

Hi Forum, The Fault Tolerance Working Group will be reading the following three issues in San Jose: #1 - Clarify MPI_ERRORS_ARE_FATAL scope of abort<https://github.com/mpi-forum/mpi-issues/issues/1> #3 - Define new MPI Error handler for subcommunicator abort<https://github.com/mpi-forum/mpi-issues/issues/3> #7 - Cleanup Advice and Definition of MPI_COMM_FREE<https://github.com/mpi-forum/mpi-issues/issues/7> These links will take you to the mpi-forum/mpi-issues page for each issue. From there, you can find the accompanying pull requests. The first two issues go together and cover the conversions about error handlers (defaults, inheritance, etc.) that was discussed in Bordeaux. The last issue is small and only covers removing some advice to users about MPI_COMM_FREE. Thanks, Wesley

1 0

MPI-3.1 implementation updates slides
by Balaji, Pavan 10 Nov '15

10 Nov '15

Folks, It's the time of the year again when we update the MPI-3.1 status of the various MPI implementations. Can you please update the attached slide with your MPI implementation and send it to me? We'll put this up on the Forum website, and ask people to use the latest version in all their talks. It's especially important to update all the boxes that say Q3 '15 (there are quite a few of them). You should either mark that as done (if it's done) or change it to another date that would be your current guess of when the feature would be available. Please send me the updated slide by the end of this week (Friday). We want to put it up by this Saturday. Regards, -- Pavan

1 0

Re: [Mpi-forum] Github GitHub GITHUB!
by Bland, Wesley 09 Nov '15

09 Nov '15

We set it up that way by default because there are times where a WG might want to publicize an internal issue for external opinions. That being said, there’s certainly no requirement to keep things that way. We just set up WG repositories the same way to be consistent and easier to get started. If you want to change the way things work for the groups you’re involved in, you’re welcome to do so. The only thing that needs to stay the way it is is the main mpi-forum org. All of the WGs are welcome to run themselves however they like. We weren’t trying to change the system we had in place with Trac, just augment it with more options for WGs that wanted to publicize their work. You can think of this more like the WG Trac pages (which have always been public). From: mpi-forum on behalf of Jeff Hammond Reply-To: MPI Forum Date: Monday, November 9, 2015 at 9:05 AM To: MPI Forum Subject: Re: [Mpi-forum] Github GitHub GITHUB! If that's true, then why do all the WG have separate repos for issues to make them public? If WG issues are only for internal discussion, then why can't they just be issues on the WG's fork of the spec? It seems that the public visibility of https://github.com/mpi-forum/mpi-issues alone accomplishes what we had before we Trac. Jeff On Mon, Nov 9, 2015 at 6:33 AM, Bland, Wesley <wesley.bland(a)intel.com<mailto:[email protected]>> wrote: Trac Tickets == mpi-forum/mpi-issues If you have an issue that was already in the old Trac system, then it probably belongs in mpi-forum/mpi-issues. Working group issues are just internal things for the working groups to discuss. From: mpi-forum on behalf of Jeff Hammond Reply-To: MPI Forum Date: Monday, November 9, 2015 at 7:40 AM To: MPI Forum Subject: Re: [Mpi-forum] Github GitHub GITHUB! Where do issues migrate if they have no associated working group? For example, https://svn.mpi-forum.org/trac/mpi-forum-web/ticket/318 is important to me, but we do not have a datatypes working group, just a chapter committee. Because of the similarity between large-count and extended precision plus my interest in both, I am inlined to migrate that issue into https://github.com/mpiwg-large-count/large-count-issues, but this may not work for all of them. Because of the ambiguity in the migration process for some issues, I propose that we defer making Trac readonly until the end of the year. Jeff On Thu, Oct 22, 2015 at 11:24 AM, Jeff Squyres (jsquyres) <jsquyres(a)cisco.com<mailto:[email protected]><mailto:[email protected]<mailto:[email protected]>>> wrote: If you didn't read Wesley's detailed email (YOU SHOULD! ...but I know not everyone will :-( ), here's the executive summary: 1. Read Wesley's email: http://lists.mpi-forum.org/mpi-forum/2015/10/3112.php 2. Send Wesley/Jeff your Github ID. 3. Start moving any still-open Trac tickets to Github. 4. SVN is already read-only. Everything has been moved to Git repos on GitHub. 5. Trac goes read-only on Fri, 13 Nov 2015 6. Lots of good information is on our wiki: https://github.com/mpi-forum/mpi-issues/wiki - There's info for Git newbies - There's info for GitHub newbies - There's info about how the Forum uses GitHub 7. The Dec 2015 MPI Forum meeting will only accept Github Issue agenda items (not Trac tickets). 8. Read Wesley's email: http://lists.mpi-forum.org/mpi-forum/2015/10/3112.php -- Jeff Squyres jsquyres(a)cisco.com<mailto:[email protected]><mailto:[email protected]<mailto:[email protected]>> For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/ _______________________________________________ mpi-forum mailing list mpi-forum(a)lists.mpi-forum.org<mailto:[email protected]><mailto:[email protected]<mailto:[email protected]>> http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi-forum -- Jeff Hammond jeff.science(a)gmail.com<mailto:[email protected]><mailto:[email protected]<mailto:[email protected]>> http://jeffhammond.github.io/ _______________________________________________ mpi-forum mailing list mpi-forum(a)lists.mpi-forum.org<mailto:[email protected]> http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi-forum -- Jeff Hammond jeff.science(a)gmail.com<mailto:[email protected]> http://jeffhammond.github.io/

1 0

Re: [Mpi-forum] Github GitHub GITHUB!
by Jeff Hammond 09 Nov '15

09 Nov '15

If that's true, then why do all the WG have separate repos for issues to make them public? If WG issues are only for internal discussion, then why can't they just be issues on the WG's fork of the spec? It seems that the public visibility of https://github.com/mpi-forum/mpi-issues alone accomplishes what we had before we Trac. Jeff On Mon, Nov 9, 2015 at 6:33 AM, Bland, Wesley <wesley.bland(a)intel.com> wrote: > Trac Tickets == mpi-forum/mpi-issues > > If you have an issue that was already in the old Trac system, then it > probably belongs in mpi-forum/mpi-issues. Working group issues are just > internal things for the working groups to discuss. > > From: mpi-forum on behalf of Jeff Hammond > Reply-To: MPI Forum > Date: Monday, November 9, 2015 at 7:40 AM > To: MPI Forum > Subject: Re: [Mpi-forum] Github GitHub GITHUB! > > Where do issues migrate if they have no associated working group? For > example, https://svn.mpi-forum.org/trac/mpi-forum-web/ticket/318 is > important to me, but we do not have a datatypes working group, just a > chapter committee. > > Because of the similarity between large-count and extended precision plus > my interest in both, I am inlined to migrate that issue into > https://github.com/mpiwg-large-count/large-count-issues, but this may not > work for all of them. > > Because of the ambiguity in the migration process for some issues, I > propose that we defer making Trac readonly until the end of the year. > > Jeff > > On Thu, Oct 22, 2015 at 11:24 AM, Jeff Squyres (jsquyres) < > jsquyres(a)cisco.com<mailto:[email protected]>> wrote: > If you didn't read Wesley's detailed email (YOU SHOULD! ...but I know not > everyone will :-( ), here's the executive summary: > > 1. Read Wesley's email: > http://lists.mpi-forum.org/mpi-forum/2015/10/3112.php > > 2. Send Wesley/Jeff your Github ID. > > 3. Start moving any still-open Trac tickets to Github. > > 4. SVN is already read-only. Everything has been moved to Git repos on > GitHub. > > 5. Trac goes read-only on Fri, 13 Nov 2015 > > 6. Lots of good information is on our wiki: > https://github.com/mpi-forum/mpi-issues/wiki > - There's info for Git newbies > - There's info for GitHub newbies > - There's info about how the Forum uses GitHub > > 7. The Dec 2015 MPI Forum meeting will only accept Github Issue agenda > items (not Trac tickets). > > 8. Read Wesley's email: > http://lists.mpi-forum.org/mpi-forum/2015/10/3112.php > > -- > Jeff Squyres > jsquyres(a)cisco.com<mailto:[email protected]> > For corporate legal information go to: > http://www.cisco.com/web/about/doing_business/legal/cri/ > > _______________________________________________ > mpi-forum mailing list > mpi-forum(a)lists.mpi-forum.org<mailto:[email protected]> > http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi-forum > > > > -- > Jeff Hammond > jeff.science(a)gmail.com<mailto:[email protected]> > http://jeffhammond.github.io/ > _______________________________________________ > mpi-forum mailing list > mpi-forum(a)lists.mpi-forum.org > http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi-forum > -- Jeff Hammond jeff.science(a)gmail.com http://jeffhammond.github.io/

1 0

Re: [Mpi-forum] Github GitHub GITHUB!
by Bland, Wesley 09 Nov '15

09 Nov '15

Trac Tickets == mpi-forum/mpi-issues If you have an issue that was already in the old Trac system, then it probably belongs in mpi-forum/mpi-issues. Working group issues are just internal things for the working groups to discuss. From: mpi-forum on behalf of Jeff Hammond Reply-To: MPI Forum Date: Monday, November 9, 2015 at 7:40 AM To: MPI Forum Subject: Re: [Mpi-forum] Github GitHub GITHUB! Where do issues migrate if they have no associated working group? For example, https://svn.mpi-forum.org/trac/mpi-forum-web/ticket/318 is important to me, but we do not have a datatypes working group, just a chapter committee. Because of the similarity between large-count and extended precision plus my interest in both, I am inlined to migrate that issue into https://github.com/mpiwg-large-count/large-count-issues, but this may not work for all of them. Because of the ambiguity in the migration process for some issues, I propose that we defer making Trac readonly until the end of the year. Jeff On Thu, Oct 22, 2015 at 11:24 AM, Jeff Squyres (jsquyres) <jsquyres(a)cisco.com<mailto:[email protected]>> wrote: If you didn't read Wesley's detailed email (YOU SHOULD! ...but I know not everyone will :-( ), here's the executive summary: 1. Read Wesley's email: http://lists.mpi-forum.org/mpi-forum/2015/10/3112.php 2. Send Wesley/Jeff your Github ID. 3. Start moving any still-open Trac tickets to Github. 4. SVN is already read-only. Everything has been moved to Git repos on GitHub. 5. Trac goes read-only on Fri, 13 Nov 2015 6. Lots of good information is on our wiki: https://github.com/mpi-forum/mpi-issues/wiki - There's info for Git newbies - There's info for GitHub newbies - There's info about how the Forum uses GitHub 7. The Dec 2015 MPI Forum meeting will only accept Github Issue agenda items (not Trac tickets). 8. Read Wesley's email: http://lists.mpi-forum.org/mpi-forum/2015/10/3112.php -- Jeff Squyres jsquyres(a)cisco.com<mailto:[email protected]> For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/ _______________________________________________ mpi-forum mailing list mpi-forum(a)lists.mpi-forum.org<mailto:[email protected]> http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi-forum -- Jeff Hammond jeff.science(a)gmail.com<mailto:[email protected]> http://jeffhammond.github.io/

1 0

Re: [Mpi-forum] Github GitHub GITHUB!
by Jeff Hammond 09 Nov '15

09 Nov '15

Where do issues migrate if they have no associated working group? For example, https://svn.mpi-forum.org/trac/mpi-forum-web/ticket/318 is important to me, but we do not have a datatypes working group, just a chapter committee. Because of the similarity between large-count and extended precision plus my interest in both, I am inlined to migrate that issue into https://github.com/mpiwg-large-count/large-count-issues, but this may not work for all of them. Because of the ambiguity in the migration process for some issues, I propose that we defer making Trac readonly until the end of the year. Jeff On Thu, Oct 22, 2015 at 11:24 AM, Jeff Squyres (jsquyres) < jsquyres(a)cisco.com> wrote: > If you didn't read Wesley's detailed email (YOU SHOULD! ...but I know not > everyone will :-( ), here's the executive summary: > > 1. Read Wesley's email: > http://lists.mpi-forum.org/mpi-forum/2015/10/3112.php > > 2. Send Wesley/Jeff your Github ID. > > 3. Start moving any still-open Trac tickets to Github. > > 4. SVN is already read-only. Everything has been moved to Git repos on > GitHub. > > 5. Trac goes read-only on Fri, 13 Nov 2015 > > 6. Lots of good information is on our wiki: > https://github.com/mpi-forum/mpi-issues/wiki > - There's info for Git newbies > - There's info for GitHub newbies > - There's info about how the Forum uses GitHub > > 7. The Dec 2015 MPI Forum meeting will only accept Github Issue agenda > items (not Trac tickets). > > 8. Read Wesley's email: > http://lists.mpi-forum.org/mpi-forum/2015/10/3112.php > > -- > Jeff Squyres > jsquyres(a)cisco.com > For corporate legal information go to: > http://www.cisco.com/web/about/doing_business/legal/cri/ > > _______________________________________________ > mpi-forum mailing list > mpi-forum(a)lists.mpi-forum.org > http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi-forum > -- Jeff Hammond jeff.science(a)gmail.com http://jeffhammond.github.io/

1 0