[mpiwg-tools] Ticket 383: Variables with the same name ticket

[Schulz Martin]

Hi Kathryn,

The text misses the INOUT/OUT instead of just OUT on page 34, line 10,
otherwise this looks good to me.

Thanks!

Martin

________________________________________________________________________
Martin Schulz, schulzm at llnl.gov, http://scalability.llnl.gov/
CASC @ Lawrence Livermore National Laboratory, Livermore, USA





On 8/30/14, 4:44 PM, "Kathryn Mohror" <kathryn at llnl.gov> wrote:

>Hi Martin,
>
>Thanks for the feedback. I incorporated it and attached the new copy.
>
>Anyone else have comments?
>
>Thanks!
>Kathryn
>_________________________________________________________________
>Kathryn Mohror, kathryn at llnl.gov, http://scalability.llnl.gov/
>Scalability Team @ Lawrence Livermore National Laboratory, Livermore, CA,
>USA
>
>
>
>
>
>
>On 8/30/14, 1:22 AM, "Schulz Martin" <schulzm at llnl.gov> wrote:
>
>>Hi Kathryn, all,
>>
>>Thanks for putting this together. I think, this looks almost right. Just
>>the string returns are not quite right, I think. What about adding the
>>following:
>>
>>
>>Page 15:
>>	
>>		
>>		
>>	
>>	
>>		
>>			
>>				
>>					If the name of a control variable is the same across connected
>>processes, the following OUT parameters must be identical: verbosity,
>>datatype, enumtype, desc, desc_len, bind, scope.
>>->
>>If the name of a control variable is the same across connected processes,
>>the following INOUT/OUT parameters must be identical: verbosity,
>>datatype,
>>enumtype, desc, desc_len, bind, scope (assuming identical values are
>>passed in desc_len).
>>
>>
>>
>>Same on page 24:
>>If the name and class of a performance variable are the same across
>>connected processes,
>>the following OUT parameters must be identical: verbosity, varclass,
>>datatype, enumtype,
>>desc, desc_len, bind, readonly, continuous, atomic.
>>->
>>				
>>			
>>		
>>	
>>If the name and class of a performance variable are the same across
>>connected processes,
>>the following INOUT/OUT parameters must be identical: verbosity,
>>varclass,
>>datatype, enumtype,
>>desc, desc_len, bind, readonly, continuous, atomic (assuming identical
>>values are passed in desc_len).
>>
>>
>>Same on page 34
>>
>>	
>>		
>>		
>>	
>>	
>>		
>>			
>>				
>>					If the name of a category is the same across connected processes,
>>the
>>following OUT
>>parameters must be identical: desc, desc_len.
>>->
>>If the name of a category is the same across connected processes, the
>>following INOUT/OUT
>>parameters must be identical: desc, desc_len (assuming identical values
>>are passed in desc_len).
>>
>>
>>Martin
>>
>>
>>				
>>			
>>		
>>	
>>
>>
>>				
>>			
>>		
>>	
>>
>>
>>
>>				
>>			
>>		
>>	
>>
>>
>>
>>
>>
>>
>>				
>>			
>>		
>>	
>>
>>
>>________________________________________________________________________
>>Martin Schulz, schulzm at llnl.gov, http://scalability.llnl.gov/
>>CASC @ Lawrence Livermore National Laboratory, Livermore, USA
>>
>>
>>
>>
>>
>>On 8/29/14, 6:10 PM, "Kathryn Mohror" <kathryn at llnl.gov> wrote:
>>
>>>Hi all,
>>>
>>>Here¹s a draft of the tools chapter with changes for ticket #383 based
>>>on
>>>our last discussion. Let¹s see if we can get this nailed down to read in
>>>Japan.
>>>
>>>Please see the attached, and keep in mind that the due date for ticket
>>>announcements is MONDAY!
>>>
>>>Thanks,
>>>Kathryn
>>>
>>>
>>>
>>>_________________________________________________________________
>>>Kathryn Mohror, kathryn at llnl.gov, http://scalability.llnl.gov/
>>>Scalability Team @ Lawrence Livermore National Laboratory, Livermore,
>>>CA,
>>>USA
>>>
>>>
>>>
>>>
>>
>>
>>_______________________________________________
>>mpiwg-tools mailing list
>>mpiwg-tools at lists.mpi-forum.org
>>http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-tools
>