[Paraview] replacement for ProbeLocationOverTime filter?

[Berk Geveci]

Cool. I am glad it worked.

On Wed, Jun 4, 2008 at 9:28 PM, Julian Cummings
<cummings at cacr.caltech.edu> wrote:
> Hi Berk,
>
> Actually, I think it is working properly for me now.  When I select
> certain points with ProbeSelectionOverTime, it seems to read through the
> files and extract the selected points *without* trying to also render
> each frame as it reads through.  That's what was happening before with
> ProbeLocationOverTime, but now it seems much faster.  And I was able to
> append the initial radial location as calculated from my time=0 data
> file to the full time series dataset with AppendAttribute, and then
> calculate the normalized radial displacement from the initial value and
> plot that over time at selected locations with PlotSelectionOverTime.
> Hurray!!
>
> -- Julian C.
>
>
> On Wed, 2008-06-04 at 16:33 -0400, Berk Geveci wrote:
>> Hmmm. That's tricky.  There is no random access to an element or point
>> in the legacy formats so it has to read the whole file to get even a
>> single value. If this is a big deal, you may want to consider
>> switching to Exodus.
>>
>> -berk
>>
>> On Wed, Jun 4, 2008 at 4:15 PM, Julian Cummings
>> <cummings at cacr.caltech.edu> wrote:
>> > This is unstructured data on a tetrahedral mesh.
>> > -- Julian C.
>> >
>> >
>> > On Wed, 2008-06-04 at 15:23 -0400, Berk Geveci wrote:
>> >> On Wed, Jun 4, 2008 at 2:51 PM, Julian Cummings
>> >> <cummings at cacr.caltech.edu> wrote:
>> >> > On Wed, 2008-06-04 at 09:21 -0400, Berk Geveci wrote:
>> >> >> > There used to be a ProbeLocationOverTime filter in Paraview 3.2.1 that
>> >> >> > could produce an XY plot of a variable value at a selected location
>> >> >> > versus time, but this is gone in the development version of Paraview
>> >> >> > 3.3.0.  Is there a simple way to reproduce this capability in 3.3.0?
>> >> >> > (I recall that the ProbeLocationOverTime was very, very slow because
>> >> >> > ParaView would try to render the data for the entire domain and each
>> >> >> > frame in the time sequence, instead of just reading and storing the
>> >> >> > single data value at the selected location from each time dump.)
>> >> >>
>> >> >> There is a "fast-path" option for doing reading only the selected
>> >> >> element/point attributes but the reader has to support it. Currently,
>> >> >> only the Exodus reader supports this feature. If you have your own
>> >> >> reader or you are using Exodus, I can give you more information.
>> >>
>> >> Unstructured or structured data?
>> >>
>> >
>> >
>>
> --
> Dr. Julian C. Cummings                       E-mail: cummings at cacr.caltech.edu
> California Institute of Technology           Phone:  626-395-2543
> 1200 E. California Blvd., Mail Code 158-79   Fax:    626-584-5917
> Pasadena, CA 91125                           Office: 125 Powell-Booth
>
>