Hi all,
We have our usual FTWG con call today. Here’s the planned agenda:
* Continue discussion of abort issues (PR: mpi-forum/mpi-standard#1<https://github.com/mpi-forum/mpi-standard/pull/1>, Issues: mpi-forum/mpi-issues#1<https://github.com/mpi-forum/mpi-issues/issues/1> & mpi-forum/mpi-issues#3<https://github.com/mpi-forum/mpi-issues/issues/3>) if George can attend
* Go over slides for plenaries / readings
* Discuss error handler rework to unify error handler types (started discussion at December 2015 F2F meeting)
Last week we used Lync for the call. After everyone got their plugins working, I think it was helpful to have the ability to share screens. I’d like to propose that we continue to use that in the future. The new dial in information is below:
Join Lync Meeting
https://meet.intel.com/wesley.bland/RY9P4QJ0
Join by phone
+1(916)356-2663 (or your local bridge access #) Choose bridge 5.
Find a local number<https://dial.intel.com/>
Conference ID: 61030263
Thanks,
Wesley
I know that it’s late to change the call-in details, but I think it would be helpful to be able to have a visual discussion this time. I’d like to be able to present some slides / web pages. Since I don’t work for Cisco and can’t set up a WebEx, I propose we use the thing I do have easy access to: Lync. This will require that everyone get a browser plug-in (or just call in via the phone as usual), which I know is a pain, but it will make it easier to have the discussion. If it works well, we can use this long term.
Here’s the new call-in info / link:
.........................................................................................................................................
Join online meeting<https://meet.intel.com/wesley.bland/2S3CZL00>
https://meet.intel.com/wesley.bland/2S3CZL00
Join by Phone
+1(916)356-2663 Choose bridge 5.
Conference ID: 7880460400
Forgot your dial-in PIN? <https://dial.intel.com> | First online meeting?<http://r.office.microsoft.com/r/rlidOC10?clid=1033&p1=4&p2=1041&pc=oc&ver=4…>
………………………………………………………………………………………………………………………..
From: Wesley Bland <wesley.bland(a)intel.com<mailto:[email protected]>>
Date: Tuesday, February 2, 2016 at 8:50 AM
To: FTWG <mpiwg-ft(a)lists.mpi-forum.org<mailto:[email protected]>>
Subject: Con Call Today
Hi all,
We have our usual con call TODAY at 3:00 PM Eastern.
Dial-in information:
Phone: 712-432-0360
Code: 623998#
Agenda:
* Run through each issue that we plan to read in Chicago to make sure they’re ready
* https://github.com/mpi-forum/mpi-issues/issues?q=is%3Aissue+is%3Aopen+label…
* #28 - Add Catastrophic and Noncatastrophic Error Codes
* #1 - Clarify MPI_ERRORS_ARE_FATAL scope of abort
* #3 - Define new MPI Error handler for subcommunicator abort
* #20 - User-Level Failure Mitigation
* #21 - User-Level Failure Mitigation: RMA
* #22 - User-Level Failure Mitigation: Files
* One item for a vote:
* #7 - Cleanup Advice and Definition of MPI_COMM_FREE
* Discuss Planned Plenary
* ULFM + Fenix – Marc Gamell
This is the last telecon that we’ll have before the two week deadline so we need to make sure that any issues we plan to read are ready to go. We won’t necessarily read all of ULFM on the call, but we might read through the others quickly.
Thanks,
Wesley
Hi all,
We have our usual con call TODAY at 3:00 PM Eastern.
Dial-in information:
Phone: 712-432-0360
Code: 623998#
Agenda:
* Run through each issue that we plan to read in Chicago to make sure they’re ready
* https://github.com/mpi-forum/mpi-issues/issues?q=is%3Aissue+is%3Aopen+label…
* #28 - Add Catastrophic and Noncatastrophic Error Codes
* #1 - Clarify MPI_ERRORS_ARE_FATAL scope of abort
* #3 - Define new MPI Error handler for subcommunicator abort
* #20 - User-Level Failure Mitigation
* #21 - User-Level Failure Mitigation: RMA
* #22 - User-Level Failure Mitigation: Files
* One item for a vote:
* #7 - Cleanup Advice and Definition of MPI_COMM_FREE
* Discuss Planned Plenary
* ULFM + Fenix – Marc Gamell
This is the last telecon that we’ll have before the two week deadline so we need to make sure that any issues we plan to read are ready to go. We won’t necessarily read all of ULFM on the call, but we might read through the others quickly.
Thanks,
Wesley