November 2016 - mpiwg-ft - mailman3.cels.anl.gov

FTWG Con Call Today
by Bland, Wesley 22 Nov '16

22 Nov '16

The Fault Tolerance Working Group’s biweekly con call is today at 3:00 PM Eastern. Today's agenda: * Go over updated issues to be read at December meeting * Make plan for FTWG face-to-face at December meeting Thanks, Wesley ......................................................................................................................................... Join online meeting <https://meet.intel.com/wesley.bland/GHHKQ79Y> https://meet.intel.com/wesley.bland/GHHKQ79Y 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: 757343533 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…> ......................................................................................................................................... _______________________________________________ mpiwg-ft mailing list mpiwg-ft(a)lists.mpi-forum.org https://lists.mpi-forum.org/mailman/listinfo/mpiwg-ft

1 0

FTWG Readings for December 2016 Meeting
by Bland, Wesley 21 Nov '16

21 Nov '16

Hi all, The FTWG would like to read 3 items at the December 2016 meeting. Issues #1<https://github.com/mpi-forum/mpi-issues/issues/1> and #3<https://github.com/mpi-forum/mpi-issues/issues/3> (read together): Error Handler Rework (PR: mpi-forum/mpi-standard#1<https://github.com/mpi-forum/mpi-standard/pull/1>) * Change default communicator for error handling to MPI_COMM_SELF * Better define MPI_ERRORS_ARE_FATAL to say that all processes are aborted * Create new error handler (MPI_ERRORS_ABORT) to have similar semantics to MPI_ABORT * General text cleanup around error handlers PDF<https://github.com/mpi-forum/mpi-issues/files/604636/errhandler_cleanup.pdf> PDF with markup<https://github.com/mpi-forum/mpi-issues/files/604635/errhandler_cleanup-wit…> Issue #28<https://github.com/mpi-forum/mpi-issues/issues/28>: Catastrophic Errors (PR: mpi-forum/mpi-standard#9<https://github.com/mpi-forum/mpi-standard/pull/9>) * Define a new API function to get the current state of MPI * Current possible values are MPI_IS_OK and MPI_IS_CATASTROPHIC PDF<https://github.com/mpi-forum/mpi-issues/files/604640/catastrophic.pdf> PDF with highlighting<https://github.com/mpi-forum/mpi-issues/files/604654/catastrophic-with-mark…> Issues #20<https://github.com/mpi-forum/mpi-issues/issues/20>, #21<https://github.com/mpi-forum/mpi-issues/issues/21>, #22<https://github.com/mpi-forum/mpi-issues/issues/22>: ULFM (PR: mpi-forum/mpi-standard#13<https://github.com/mpi-forum/mpi-standard/pull/13>) * Addition of fault tolerance chapter to the MPI Standard * Adds functionality for cleaning up the state of MPI after a process failure Updated PDF to be posted soon on issue #20 Thanks, Wesley _______________________________________________ mpiwg-ft mailing list mpiwg-ft(a)lists.mpi-forum.org https://lists.mpi-forum.org/mailman/listinfo/mpiwg-ft

1 0

No Call Today
by Bland, Wesley 08 Nov '16

08 Nov '16

Sorry folks. I'm not going to be able to make the call today. If others want to have it without me, that's fine. I made a few tweaks on the PR for Catastrophic errors. You can see the latest version on the pull request here: https://github.com/mpi-forum/mpi-standard/pull/9. Thanks, Wesley _______________________________________________ mpiwg-ft mailing list mpiwg-ft(a)lists.mpi-forum.org https://lists.mpi-forum.org/mailman/listinfo/mpiwg-ft

1 0