[Paraview] Issues with ParticlePath filter

[Andy Bauer]

Hi Evan,

I just tried replicating those issues with PV 5.0 and didn't see the crash
with either case 1 or 2. If you can share a data set and pv state file that
replicates the issue with 5.0 I can take a deeper look at this.

As for starting pathlines from a specific point in time instead of the
initial one, two quick thoughts here:

   1. Can you avoid loading in time steps?
   2. You could set the reinjection frequency such that particles get
   reinjected at your specific time and then use threshold on the particle
   InjectionStepId to get rid of particles you don't want. It may be a bit of
   wasted computation but easy to get results this way.

Cheers,

Andy

On Mon, Mar 7, 2016 at 1:38 PM, Evan Kao <tossin at gmail.com> wrote:

> Hello all,
>
> Version: Paraview 4.4 64-bit on Windows 8 installed from binaries
>
> I've been playing around with the ParticlePath filter and it's been a bit
> of a frustrating experience because it seems to crash all the time.  I
> think I've identified two sources of the crashing:
>
> 1) It crashes when there are no particles left.  I tested this by setting
> the Force Injection parameter to zero and nonzero values.  This is an
> issue, since sometimes I just want to follow an initial set of particles
> without cluttering it with new particles.  So in order to do that now, I
> would have to carefully step the end time until it crashes, and then reload
> the state.
>
> 2) It crashes if the end time is beyond what Paraview *thinks* is the
> last time step.  This is an issue because I use the Temporal Interpolator
> to create periodic data with multiple cycles and for some reason it seems
> like ParticlePath does not take the periodicity into account.  I tested
> this by first using ParticlePath directly after Temporal Interpolator and
> then using ParticlePath after exporting the interpolated data and importing
> it into a new session.  In the first case, it will crash after the end of
> the first cycle.  In the second case, it will (usually) make it through
> both cycles without crashing.
>
> So there are workarounds both issues, but the workflow seems more
> cumbersome than it should be.  So I guess my question is, is there a
> better/smarter way to use the ParticlePath filter than the way I'm using
> it?  Maybe a "best practices" guide?
>
> Additionally, is there way to start the pathlines from a specific time
> point instead of the initial one?
>
> Thanks,
> Evan Kao
>
> _______________________________________________
> 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
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160308/7bddd593/attachment.html>