[Mpi-forum] Reminder: MPI Virtual Meeting THIS Wednesday Oct. 17.

[HOLMES Daniel]

I can do 10am Eastern on 31st Oct or any time on 2nd Nov but not 9am Eastern on 31st Oct.

Cheers,
Dan.
—
Dr Daniel Holmes PhD
Applications Consultant in HPC Research
d.holmes at epcc.ed.ac.uk<mailto:d.holmes at epcc.ed.ac.uk>
Phone: +44 (0) 131 651 3465
Mobile: +44 (0) 7940 524 088
Address: Room 2.09, Bayes Centre, 47 Potterrow, Central Area, Edinburgh, EH8 9BT
—
The University of Edinburgh is a charitable body, registered in Scotland, with registration number SC005336.
—

On 24 Oct 2018, at 19:07, Wesley Bland via mpi-forum <mpi-forum at lists.mpi-forum.org<mailto:mpi-forum at lists.mpi-forum.org>> wrote:

I prefer the Halloween horror. :)

On Oct 24, 2018, at 11:24 AM, Anthony Skjellum via mpi-forum <mpi-forum at lists.mpi-forum.org<mailto:mpi-forum at lists.mpi-forum.org>> wrote:

Dear Forum Members:

We would like to schedule a meeting about "new language bindings"  as an action item from our virtual last meeting (just ended).

This covers this topic with sub-topics raised in the Virtual Meeting (plus more):

"MPI object that contains an entire language binding" ... which is due to Jeff Squyres :-)

With these questions (among others to be answered)
--- How to descrtibe this, such as with a normative header, from C, C++, Fortran
--- How to guarantee that a given library (e.g., MPI-4) can also allow internal and layered components (e.g., MPI3) to work.
[Imagine an MPI-3 based library receiving a communicator from an MPI-4 main program in this way]
--- How this approach can alleviate the need for the following
a) _X Big MPI APIs, because the MPI.fn() [maybe MPI->fn() in C] provides the old and new APIs either through multiplicity
of APIs, or through compile-time polymorphism
b) Explanation of how this is strongly typed at compile time
c) Explanation of how this works with PMPI and tools (or what changes it may imply)
d) DIscussion of how this could interact with
--- eliminating MPI_COMM_WORLD and new MPI_Init() variants
--- Sessions and Topological groups
--- Subset APIs
--- Fault Tolerance
[others?]
e) Timing of such a proposal once we agree to formalize it.  Probably December.  TBD.


Right now, I am proposing 9am US Eastern on October 31, 2018 (Halloween in the US and elsewhere), since some of you may find this to be a scary conversation.    This is 2 hours before our next virtual meeting (11am Eastern on 10/31).  Alt time: 10am Same day.    Third alternative, November 2 @ 8am eastern.

AGAIN:
9am Eastern, 10/31
10am Eastern, 10/31 (right before Virtual Meeting)
8am Eastern, 11/1 ,

Of those of you who would actually attend, do these possible times work :-) .   [Let me know -- if you can make and can't make, and I'll try to intersect the data.]

If all time fails, I will do a formal doodle poll.

Thanks,
Tony




On Wed, Oct 17, 2018 at 5:10 AM Martin Schulz via mpi-forum <mpi-forum at lists.mpi-forum.org<mailto:mpi-forum at lists.mpi-forum.org>> wrote:
Hi all,

Just as a reminder, today (i.e., THIS Wednesday) we will have our next virtual meeting in this quarter. The webex information can be reached via

https://www.mpi-forum.org/meetings/

The topic will be “MPI_T Events” and Marc-Andre will lead the discussion.

Thanks,
Martin

—
Prof. Dr. Martin Schulz, Chair of Computer Architecture and Parallel Systems
Department of Informatics, TU-Munich, Boltzmannstraße 3, D-85748 Garching
Email: schulzm at in.tum.de<mailto:schulzm at in.tum.de>





_______________________________________________
mpi-forum mailing list
mpi-forum at lists.mpi-forum.org<mailto:mpi-forum at lists.mpi-forum.org>
https://lists.mpi-forum.org/mailman/listinfo/mpi-forum


--
Anthony Skjellum, PhD
skjellum at gmail.com<mailto:skjellum at gmail.com>
Cell: +1-205-807-4968


_______________________________________________
mpi-forum mailing list
mpi-forum at lists.mpi-forum.org<mailto:mpi-forum at lists.mpi-forum.org>
https://lists.mpi-forum.org/mailman/listinfo/mpi-forum

_______________________________________________
mpi-forum mailing list
mpi-forum at lists.mpi-forum.org<mailto:mpi-forum at lists.mpi-forum.org>
https://lists.mpi-forum.org/mailman/listinfo/mpi-forum

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mpi-forum.org/pipermail/mpi-forum/attachments/20181024/0b455a91/attachment-0001.html>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: not available
URL: <http://lists.mpi-forum.org/pipermail/mpi-forum/attachments/20181024/0b455a91/attachment-0001.ksh>