Intel® Trace Analyzer User's Reference Guide

Intel® Trace Analyzer User's Reference Guide
Examples of Advanced Usage of the Grammar
This section includes several examples of manually using the filter expression
grammar and how it provides advanced capabilities in filtering trace data and
speeding up the process of selecting exactly what the user would like to be
analyzed.
For the first example, consider a parenthesized structure that can not be built by
the point and click interface as easily (messages sent by process 0 and starting
or ending between 70000 and 80000 ticks):
p2pfilter( sender( 0 ) && ( start( 70000:80000 ) ||
end( 70000:80000 ) ) )
The following example uses the predicate sr, which is not available in the point
and click interface, to efficiently filter out all messages between processes 0 and
1:
p2pfilter( ! sr( 0:1; 0:1 ) )
Finally, consider the following scenario. With the point and click interface, a
complicated filter is specified for a certain filter class with a large number of
predicates and Boolean operators (both AND and OR, the latter added by using
the Add New Clause button). Now, to negate everything that has been specified
so far (that is, to get exactly the trace data that was previously being filtered out),
use ! in front of the whole expression when in the manual mode. For example,
the filter below specifies MPI_Barrier collective operations that last no longer than
2000 ticks, plus all collective operations with process 0 as the root:
collfilter( type( MPI_Barrier ) && duration( 0:2000 ) || root( 0 ) )
while this filter specifies all the collective operations that do not match the
description above:
collfilter( ! ( type( MPI_Barrier ) && duration( 0:2000 ) ||
root( 0 ) ) )
Filter Expressions in Comparison Mode
In Comparison mode (see Chapter 7, Comparison of two Trace Files) the dialog
is extended by a label and a combo box that allows to apply the chosen filter
expression to the other trace file shown in the View. Choosing the option "If
expression is valid in other file." will check if the resulting expression is valid in
the name space of the other file and if so then apply the expression as if you
had manually typed it in the other file's filter dialog. Any previous input in the
target dialog will be overwritten.
The Tagging Dialog
For an explanation of the filtering concept refer to the section called “Tagging
and Filtering”. The usage of this dialog box is as for the Filtering dialog box and
described in the section called “The Filtering Dialog”.
The only difference is that the default Filtering dialog box lets all events pass
while the default Tagging dialog box does not tag any event at all.
Document number: 318120-002 70