Good suggestions.
Since Jim asked about cvars, it would probably be good to add a slide or two reminding the Forum about them. I’m comfortable with them (I wrote the first real test cvar and pvar program for MPICH), so I don’t need much detail to work from.
Bill
On Feb 20, 2015, at 8:29 PM, Schulz Martin <schulzm(a)llnl.gov> wrote:
> The slides themselves are fine with me – the only comment I would have is that the second bullet on the first proposal is a general statement, we want that in any case. Any other solution, including the CVar, would have to adhere to the same requirements. Perhaps it would make more sense to put that before the “Why not Info keys” slide and generally describe what we want to accomplish and then just say for this one idea, we have two API proposals (not proposals for different concepts).
>
> Since Bill will present them, I guess the question is for him: do you want any more details on the CVars on should we just have this as part of the discussions?
>
> Martin
>
>
> From: Jim Dinan <james.dinan(a)gmail.com>
> Date: Friday, February 20, 2015 at 6:00 PM
> To: MPI WG Point To Point Communications working group <mpiwg-p2p(a)lists.mpi-forum.org>
> Cc: Schulz Martin <schulzm(a)llnl.gov>, Bill Gropp <wgropp(a)uiuc.edu>
> Subject: Communicator assertions
>
> Hi All,
>
> I would like to raise communicator assertions (was communicator info keys) for discussion again at the upcoming meeting. I have attached a rough sketch of two possible directions for the proposal.
>
> The goal with these slides is to create an outline that can be used for discussion in the P2P WG meeting. Please send feedback, rotten tomatoes, or questions.
>
> Cheers,
> ~Jim.
