I see the problem. The second argument of MPI_T_pvar_get_index is not
the binding. It is the variable class. Change it to:
err = MPI_T_pvar_get_index(name, varClass, &pvar_idx);
and it works as expected.
-Nathan
On Fri, Aug 14, 2015 at 03:08:42PM -0400, George Bosilca wrote:
>Another issue
That is interesting. Let me look at the logic and see if I can determine
what is going wrong.
It could be a naming issues. ie. opal_btl_vader_flags vs
btl_vader_flags. Both are valid names for the same variable but the
search may only be succeeding for one. Should be simple enought to
fix if that
This one does seem like a bug. I'll open an issue.
> On Aug 14, 2015, at 3:08 PM, George Bosilca wrote:
>
> Another issue, maybe a little bit more unsettling.
>
> If I iterate over the existing pvars, and for each after retrieving their
> name I use the name to search for the associated index
On Aug 15, 2015, at 8:05 AM, Jeff Squyres (jsquyres) wrote:
>
> 2. The current implementation says that the cvar's *value* should not be
> returned, but perhaps we should be returning its *info* (even after the cvar
> is no longer available). That's a good point -- we might need to fix that.
On Aug 14, 2015, at 2:36 PM, George Bosilca wrote:
>
> For this particular test I used the current master (022a9d8).
>
> I reread the MPI_T chapter and [as usual] there might be something that
> cautions the current behavior (aka. returning MPI_T_ERR_INVALID_INDEX for an
> index smaller than t
Another issue, maybe a little bit more unsettling.
If I iterate over the existing pvars, and for each after retrieving their
name I use the name to search for the associated index I get an error. A
short example is below.
George.
err = MPI_T_pvar_get_num(&numPvar);
if(err) MPI_Abort(M
For this particular test I used the current master (022a9d8).
I reread the MPI_T chapter and [as usual] there might be something that
cautions the current behavior (aka. returning MPI_T_ERR_INVALID_INDEX for
an index smaller than the number of cvars returned by MPI_T_cvar_get_num).
This is indicat
George: what OMPI version did you test?
> On Aug 14, 2015, at 2:14 PM, George Bosilca wrote:
>
> This user email requires special attention, as it highlighted some issues
> with our MPI_T variables.
>
> I wrote a short application to list all pvar and cvar available.
> Unexpectedly, listing t
