Re: [Mpi-forum] Virtual Meeting Information Moving

Hi Wesley, I'm not sure that I did it before, so can you add me? my Github email address is merc...@labri.fr Thanks, Guillaume On 3/27/19 8:19 PM, Wesley Bland via mpi-forum wrote: Hi folks, As you'll have noticed recently, the bots have become a major problem for our WebEx calls. Jeff an

[Mpi-forum] Announce of hardware topologies working group readings (May 2019, Chicago)

Hello, I would like to announce two readings for the May meeting in Chicago: First, the introduction of a new split_type value in MPI_Comm_split: Issue - https://github.com/mpi-forum/mpi-issues/issues/132 Pull Request - https://github.com/mpi-forum/mpi-standard/pull/111 Second, the interface

Re: [Mpi-forum] Last day to announce readings and ballots for May MPI forum meeting

Hi Martin, The hardware topologies WG is likely to use some meeting time. I'll arrive on Monday, so anytime from Tuesday will do. Thanks, Guillaume On 5/14/19 6:47 AM, Martin Schulz via mpi-forum wrote: Hi all, Thanks to all who have already sent out reading and ballot announcements. Just

Re: [Mpi-forum] Planning for the September Forum Meeting

Hello Martin, A- we would like some WG time during the meeting. At least 2 hours (and probably more) would be great. B- the plan is to read again: - issue #132/PR #111 (MPI_Comm_split_type stuff) - issue #120/PR #98 (Topology aware Cartesian communicators). Guillaume On 7/23/19 4:00 PM, Marti

[Mpi-forum] Announce of hardware topologies working group readings (September 2019, Zürich)

Hello, I would like to announce two readings for the September meeting in Zürich: First, the introduction of a new split_type value in MPI_Comm_split: Issue - https://github.com/mpi-forum/mpi-issues/issues/132 Pull Request - https://github.com/mpi-forum/mpi-standard/pull/111 Second, the inter

Re: [Mpi-forum] Preliminary MPI Forum Agenda posted

Hi Martin, Thanks for the agenda, it's fine with me. Guillaume On 8/22/19 7:50 PM, Martin Schulz via mpi-forum wrote: Hi all, The preliminary agenda for the forum meeting is posted - please take a look and let me know if I forgot anything. I did get only very few WG requests, so I shorten

[Mpi-forum] Hardware Topologies WG meeting tomorrow

Hi all, A Telecon for the Hardware Topologies Working Group is scheduled tomorrow at 10am/GMT+2. Connection details are available on the WG's wiki: https://github.com/mpiwg-hw-topology/hw-topology-issues/wiki (see the link at the top of page). We'll mainly discuss the text for the guided mode

[Mpi-forum] Readings Announcement: issues #132, #154 and #156

Dear all, The following items will be read at the next physical meeting in Albuquerque : Hardware communicators, guided mode: Issue #132: https://github.com/mpi-forum/mpi-issues/issues/132 PR#142: https://github.com/mpi-forum/mpi-standard/pull/142 Query routines for hardware resource types

Re: [Mpi-forum] Chapter Committees ACTION NEEDED

Hello Jeff, I followed your instructions, but I'm stuck with the make cleandoc command in your Git repo: make rendered-backend BINDING_RENDER_VERSION=3.1 make[1]: Entering directory '/home/mercierg/Developpement/Git/A_RELIRE/mpi-pythonization' Traceback (most recent call last): File "bi

Re: [Mpi-forum] Chapter Committees ACTION NEEDED

o:jsquy...@cisco.com>> wrote: The key is in the output: raise RuntimeError('This python installation is too old! ' RuntimeError: This python installation is too old! Use Python 3.7 or later You need at least Python 3.7. On Dec 22, 2019, at 4:11 PM, Guillaume Mercier via mpi

Re: [Mpi-forum] Chapter Committees ACTION NEEDED

Hello Santa, On 12/25/19 3:40 PM, Jeff Squyres (jsquyres) wrote: On Dec 24, 2019, at 9:08 PM, Guillaume Mercier via mpi-forum wrote: I did just that: make PYTHON=/usr/bin/python3.8 cleandoc But the result is the same: Yes, that does not work right now -- we'd have to add that.

Re: [Mpi-forum] Chapter Committees ACTION NEEDED

Hello Jeff, I did complete my review for Pythonization in chapter 6. Here are my comments: 1- for the function MPI_Group_range_incl: - missing space in ranges(3,n) (p262, l20) => should be ranges(3, n) 2-for the function MPI_Group_range_excl: - missing space in ranges(3,n) (p263, l20/21) =>

Re: [Mpi-forum] Planing for the MPI Forum Meeting in February

Hi all, The Hardware Topologies Working Group would like to request the first vote for the following items: - Hardware split, guided mode * Issue: https://github.com/mpi-forum/mpi-issues/issues/132 * PR: https://github.com/mpi-forum/mpi-standard/pull/142 * PDF: https://github.com/mpi-forum/mpi

[Mpi-forum] Hardware Topologies Working Group Announcements for the June Meeting

Hi all, I'd like to make a couple of announcements for the upcoming Voting Meeting (aka Exceptional Virtual Meeting) : *second votes for: -PR1#42 (https://github.com/mpi-forum/mpi-standard/pull/142) : Guided Mode for Hardware Communicators Creation -PR#148 (https://github.com/mpi-forum/mpi-stan

Re: [Mpi-forum] Final Reminder: Deadline for Ballots, Readings, ... for the August MPI Forum Meeting is Tomorrow/Monday

Hi all, I'd like to read an errata dealing with MPI_Comm_split_type Issue is here: https://github.com/mpi-forum/mpi-issues/issues/301 PR is here: https://github.com/mpi-forum/mpi-standard/pull/263 Thanks, Guillaume On 8/2/20 4:14 PM, Martin Schulz via mpi-forum wrote: > Hi all, > > Just as th

Re: [Mpi-forum] Final Reminder: Deadline for Ballots, Readings, ... for the August MPI Forum Meeting is Tomorrow/Monday

Hi all, The Hardware Topologies Working Group wants to announce the first vote for the MPI_Cart_create_weighted / Topology aware Cartesian communicators: Annotated pdf as read in the June 2020 meeting: https://github.com/mpi-forum/mpi-issues/files/4823780/mpi-report-issue120-topol-2020-06-14-anno

Re: [Mpi-forum] No Virtual Meeting Tomorrow (Wed) / August Agenda Online

Hi Martin, My errata reading seems to be missing from the agenda. Guillaume On 8/4/20 9:32 PM, Martin Schulz via mpi-forum wrote: > Hi all, > > The virtual meeting tomorrow (Wed 8/5) is - as expected - cancelled. > > Also, based on the input I have gotten, I published a first agenda for the

[Mpi-forum] Announcing Erratum (Ticket #301) for Reading for the September Meeting

Dear all, The Hardware Topologies Working Group would like to read the following erratum at the next meeting in September, dealing with MPI_Comm_split_type and MPI_COMM_TYPE_SHARED: Issue: https://github.com/mpi-forum/mpi-issues/issues/301 PR: https://github.com/mpi-forum/mpi-standard/pull/263 T

Re: [Mpi-forum] Feb 2021 MPI Forum Meeting Plan

Hi Martin, Just tio let you know: I won't be available for the meetings during the first hour or so. I'll attend after that. So, anything related to chapter 7 should be handled from 5pm unless it's straightforward and does not require my presence. Best Guillaume On 2/22/21 6:57 AM, Martin Schu

Re: [Mpi-forum] Next Virtual MPI Forum Meeting Next Week - Request for MPI 4.1 issues/topics

Hello Martin, Sorry to answer your message so late. There are a couple of things I'd like to address for 4.1 1- all the clean-up stuff w.r.t (now) chapter 7, as I presented during my reading in the last ratification meeting. This include (see attached document): * Add process topology functions

[Mpi-forum] Errata reading announcement for Sept. 2021 Meeting

Dear fellow Forum members, I'm announcing the reading of an errata, in order to correct a couple of examples in the partitioned communications chapter. Here is the issue: https://github.com/mpi-forum/mpi-issues/issues/509 And here is the related PR: https://github.com/mpi-forum/mpi-standard/

Re: [Mpi-forum] EuroMPI Starts Today, MPI-Forum starts Thursday, Joint Session on Wednesday

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, th

[Mpi-forum] [MPI Forum] Readings announcements

Hi All, I'd like to announce two readings: PR#634 (https://github.com/mpi-forum/mpi-standard/pull/634), that addresses issue #496: https://github.com/mpi-forum/mpi-issues/issues/496 And PR#636 that partially addresses issue #474. PR is here: https://github.com/mpi-forum/mpi-standard/pull/63

Re: [Mpi-forum] Agenda items for May 2022 Meeting / deadline Monday (tomorrow)

Hi Martin, I'd like a 2h slot for the Topologies WG. thanks. Guillaume On 5/8/22 12:07 PM, Martin Schulz via mpi-forum wrote: Hi all, Time is flying and our next voting meeting is coming up quickly on May 23-26. As discussed in February, we will hold this meeting again fully virtual in the

[Mpi-forum] [MPI Forum] Reading announcements

Hello all, As the Chapter Committee Chair for the Context Chapter (a.k.a Chapter7), I'd like to read the following items at the next meeting: - Issue #474: https://github.com/mpi-forum/mpi-issues/issues/474 - PR: https://github.com/mpi-forum/mpi-standard/pull/710 - Issue #496: https://github.

Re: [Mpi-forum] [EXTERNAL] Virtual MPI Forum Meeting tomorrow (Wed. Oct. 19th)

it's that link : https://tum-conf.zoom.us/j/67455795817 On 19/10/2022 17:06, Pritchard Jr., Howard via mpi-forum wrote: Are we using the link at the top of https://github.com/mpi-forum/mpi-standard/wiki/Virtual-Forum-Meeting-Information

[Mpi-forum] Readings announcements for the December meeting of the MPI Forum

Dear all, I'd like to make the following readings on behalf of the Topologies working Group: 1- Allow pset names to guide splitting in MPI_Comm_split_type Issue: https://github.com/mpi-forum/mpi-issues/issues/538 PR: https://github.com/mpi-forum/mpi-standard/pull/761 2- New functions to query

Re: [Mpi-forum] December Meeting Draft Agenda Posted

Hi Wes, Should this item: https://github.com/mpi-forum/mpi-issues/issues/474 https://github.com/mpi-forum/mpi-standard/pull/710 be added to the list of items to (first) vote on? Guillaume On 22/11/2022 15:29, Wes Bland via mpi-forum wrote: Hi all, After the slew of announcements yesterday,

Re: [Mpi-forum] ABI working group is live

Hello Jeff, Could you add me to the group? My github id is GuillaumeMercier My email address is guillaume.merc...@u-bordeaux.fr Thanks Guillaume On 09/12/2022 07:31, Jeff Hammond via mpi-forum wrote: The MPI ABI workgroup was approved.  You can sign up for the mailing list now: https://lists

[Mpi-forum] Readings announcements for the March meeting of the MPI Forum

Dear all, The Topologies working Group would like to make the following readings: 1- Deprecate MPI_HOST Issue : https://github.com/mpi-forum/mpi-issues/issues/57 PR : https://github.com/mpi-forum/mpi-standard/pull/790 2- New interface to query hardware resource info Issue: https://github.com/mp

[Mpi-forum] Vote announcement for the March meeting of the MPI Forum

Dear all, On behalf of The Topologies working Group, I would like to make the following announcement: First, I'd like a "no-no" vote for issue #154 (New interface to query hardware resource info) -Issue: https://github.com/mpi-forum/mpi-issues/issues/154 -PR: https://github.com/mpi-forum/mp

[Mpi-forum] Vote announcement

Dear all, I'd like to announce the following vote for the March meeting : * 2nd vote on issue #538: Allow pset names to guide splitting in MPI_Comm_split_type Issue: https://github.com/mpi-forum/mpi-issues/issues/538 PR: https://github.com/mpi-forum/mpi-standard/pull/761 Thanks, Guillaume

[Mpi-forum] Ballots for May MPI Forum Meeting

Hello all, I would like to announce the following ballot for the May meeting: 2nd vote: * Issue #154 (PR #762): New interface to query hardware resource info - Issue: https://github.com/mpi-forum/mpi-issues/issues/154 - PR: https://github.com/mpi-forum/mpi-standard/pull/762 Thanks, Guillaume

Re: [Mpi-forum] Question about MPI-4.1's MPI_Get_hw_resources_info()

Hello Jeff, This procedure is the missing companion of the original hardware communicators proposal introduced in MPI 4.0 (i.e MPI_COMM_TYPE_HW_GUIDED) On 16/11/2023 03:09, Jeff Squyres (jsquyres) via mpi-forum wrote: 1. I'm not quite sure what the "true" and "false" values mean. 1. E.

Re: [Mpi-forum] Question about MPI-4.1's MPI_Get_hw_resources_info()

Hi Jeff, Let me revise my first answer and be more specific on a couple of points you raise in your message. Remember that until MPI 4.1, there was no standard way to provide a value to the "mpi_hw_resource_type" info key that can guide the splitting of communicators on hardware-basis (i.e. wi

[Mpi-forum] Readings announcements for Topologies WG

Hello All, On behalf on the Toplogies WG, I'd like to read the following items at the next MPI Forum Meeting: 1- Title: Make examples use URI format as described in MPI_GET_HW_RESOURCE_INFO Issue: https://github.com/mpi-forum/mpi-issues/issues/823 PR: https://github.com/mpi-forum/mpi-standard/

Re: [Mpi-forum] Reminder: MPI-Forum Deadline for Announcements on September 9th

Hello, On behalf of the Topologies Working Group, I'd like to request no-no votes for the following items during the next MPI Forum meeting: 1- Text for MPI_GET_HW_RESOURCE_INFO needs clarification Issue #838 https://github.com/mpi-forum/mpi-issues/issues/838 PR #964 https://github.com/mpi-foru