[Paraview] Two issues with time-dependent data

[Schuld, Heinrich]

Thanks Cory for your idea. The problem is, that I would have to set the end of the TIME_RANGE dependently on the timesteps requested by ParaView. Otherwise the delta t between timesteps will not be equal. I could modify my filter so that the user has to select the number of timesteps in it. But I was hoping to use the already present functionalities of ParaView.

Cheers,
Heinrich


-----Ursprüngliche Nachricht-----
Von: Cory Quammen [mailto:cory.quammen at kitware.com] 
Gesendet: Donnerstag, 6. Juli 2017 21:54
An: Schuld, Heinrich <Schuld at ist.rwth-aachen.de>
Cc: paraview at paraview.org
Betreff: Re: [Paraview] Two issues with time-dependent data

[snip]
> 1.       In RequestInformation of the filter, we provide the pipeline just
> with a TIME_RANGE. This is so far working without problem, we can go through
> the range by Sequence or Real Time. When running the Animation as a loop
> though, we encounter the issue that the beginning and the end of the time
> range are both displayed. Since our data is periodic and the TIME_RANGE is a
> cycle duration, these two steps are identical. As you can guess, it is not
> desired to see the same step two times right behind each other. Is there a
> way to prevent this behaviour?

Can you just set the upper end of the TIME_RANGE to one timestep
before what you have now? In other words, instead of having the first
and last timesteps provide the same data, end the TIME_RANGE earlier
by one timestep. That will prevent the doubling of the timestep when
the animation resets.

> 2.       When we save the filter in a state file and load it afterwards with
> a different dataset, the displayed time range in ParaView shows the wrong
> data. Although in RequestInformation the correct TIME_RANGE of the new
> dataset is set to the pipeline, ParaView/the Animation View still shows the
> time data of the state file. It only changes, if after loading the state
> file, a different TIME_RANGE with different values is set in
> RequestInformation. We can live with this issue, but maybe it is a bug that
> is easy to fix.

I'm not sure about this one. Maybe someone else can chime in.

Thanks,
Cory

>
>
> We will be grateful for any advice or suggestion!
>
>
>
> Thanks in advance and cheers,
>
> Heinrich
>
>
>
> --
>
> Dipl.-Ing. Heinrich Schuld
>
> Institute of Jet Propulsion and Turbomachinery
>
> RWTH Aachen
>
> Templergraben 55
>
> 52062 Aachen
>
> Germany
>
>
>
> Tel:         +49 241 80 99652
>
> Fax:        +49 241 80 92229
>
> E-Mail:   schuld at ist.rwth-aachen.de
>
> www:     http://www.ist.rwth-aachen.de
>
>
>
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview
>



-- 
Cory Quammen
Staff R&D Engineer
Kitware, Inc.