RE [Paraview] StreamTracing Tester/Guinea Pig(s) wanted

Berk Geveci berk.geveci at kitware.com
Fri Feb 29 15:59:40 EST 2008


Tools -> Timer Log is your friend. It should tell you how long it took
to execute each filter on each processor.

-berk


On 2/29/08, John Biddiscombe <biddisco at cscs.ch> wrote:
>
>  Stephane
>
>
>
> Do you have an easy way to measure the performance in ParaView ? (is there a
> way to set up a timer? )
>  By the way, I had another question on stream tracing : do you know why
> can't we use cell-based velocity field for stream tracing ?
>
>  I'm not really sure how reliable the render timing on the help menu would
> be, to display this. We could add a timer.start and timer.elapsed call at
> the begining and end of RequestData in vtkStreamtracer which will output the
> time in the output window of paraview, but that would mean temporarily
> adding this to cvs. No real problem there. I was hoping someone else would
> know a good way.
>
>  Cell based velocity is not used because the interpolated value of velocity
> remains constant within the cell, so you'd get small line segments that were
> straight as the particle moved through the cell and into the next. It could
> be changed to find the neighbour cells and do a kind of on the fly
> cell-point interpolation and use those values, but frankly it'd be
> inefficient and a bit messy and life is too short when you can use
> cell-point filter before hand...
>
>  JB
>
>
> _______________________________________________
>  ParaView mailing list
>  ParaView at paraview.org
>  http://www.paraview.org/mailman/listinfo/paraview
>
>


More information about the ParaView mailing list