 /**
 * @page ToolsIvPerf ivPerf tool
 *
 * @B ivPerf @b reads in an Open Inventor scene graph and analyzes its rendering performance.
 *
 * @H3 SYNOPSIS: @h3
 *    @B ivperf [-b] [-f N] [-w X,Y] inputfile @b
 *
 * @H3 DESCRIPTION: @h3
 * @B ivPerf @b reads in an Open Inventor scene graph and analyzes its rendering performance. 
 * If you know that caches at certain separators will be invalidated because your application 
 * changes data under them, name these separators "NoCache" (i.e. DEF NoCache ...). ivperf 
 * will then correctly simulate the autocaching behavior on the scene graph.
 *
 * Running ivperf without any arguments will list the usage message.
 *
 * ivperf's output can be graphically displayed in the form of a bar chart. The first bar (red)
 * is the total time taken to render a frame, and the other bars (yellow) are the approximate 
 * times spent in each rendering stage. They are (in order):
 *
 * @UL
 * @LI Clearing the graphics window @li
 * @LI Traversing the Open Inventor scene graph @li
 * @LI Changing material state @li
 * @LI Changing the GL transformation matrix @li
 * @LI Texture mapping @li
 * @LI Texture management @li
 * @LI Lighting @li
 * @LI Transforming vertices in the pipeline @li
 * @LI Filling polygons @li
 * @ul
 *
 * @SEE_ALSO
 * "Open Inventor Porting and Performance Tips" for more information on using ivperf.
 *
 * @H3 USAGE: @h3
 * The following command line options are allowed:
 *
 * @TABLE_1B
 * @TR -b       @TD display results as bar chart.
 * @TR -f N     @TD render N frames for each test.
 * @TR -w X,Y   @TD	make window size X by Y pixels.
 * @TABLE_END
 *
 * @H3 EXAMPLES @h3
 *
 * @code
 *   ivPerf inputfile.iv
 * @endcode
 *
 *
 * @FILE_LIST
 * @UL
 * @LI tools/source/ivPerf/ivPerf.cxx      @li
 * @LI tools/source/ivPerf/getopt/getopt.c @li
 * @LI tools/source/ivPerf/getopt/getopt.h @li
 * @ul
 *
 */
