[Paraview] TemporalParticlesToPathlines filter missing scalar

[Berk Geveci]

It was indeed a bug. Thanks for reporting it Bill. A fix is in the
pipeline. It will probably take until next week for it to make into
ParaView master.

Best,
-berk


On Wed, Jul 2, 2014 at 10:22 AM, Bill Sherman <shermanw at indiana.edu> wrote:

> A followup to my question.
>
> Presuming this is a bug, which means it might require some time to
> fix, I went ahead and figured out a work-around.
>
> I just bring up a "Calculator" filter and duplicate the problematic
> field ("mass") as "massdup", and then put that through the
> TemporalParticlesToPathlines filter.  And now I have access to
> the data of interest.
>
> Curiously, it's the "massdup" field that is now replaced by "TrailId".
>
>         Bill
>
>
>
> On 07/01/2014 12:54 PM, Bill Sherman wrote:
>
>> On 07/01/2014 10:46 AM, Berk Geveci wrote:
>>
>>> Sounds like a bug. Do you have data/pipeline to reproduce it?
>>>
>>
>> Sure. I put a tar file at:
>> http://iq-station.org/downloads/Part2Path_debug.tar.gz
>>
>> I included the first 9 steps of the data.
>>
>>  -berk
>>>
>>
>> Thanks,
>> Bill
>>
>>
>>>
>>> On Mon, Jun 30, 2014 at 11:48 PM, Bill Sherman <shermanw at indiana.edu
>>> <mailto:shermanw at indiana.edu>> wrote:
>>>
>>> Hello,
>>>
>>> I am confused by something that the TemporalParticlesToPathlines
>>> filter seems to be doing. It seems to be deleting or replacing
>>> one of the scalar fields in the "Pathlines" output.
>>>
>>> I have a rather simple pipeline:
>>>
>>> Data
>>> TemporalInterpolator
>>> TemporalParticlesToPathlines
>>> Pathlines
>>> Tube
>>> Particles
>>> Glyph
>>>
>>> So the data has a handful of scalar values:
>>> * density
>>> * id
>>> * mass
>>> * type
>>> * velocity (okay, not a scalar)
>>> * vphi
>>>
>>> And all the filters offer these as available to color the data
>>> by -- except! Except under the Pathlines (and Tube), the "mass"
>>> data is replaced by "TrailId".
>>>
>>> Of course, I'm trying to color the pathlines by the value of the
>>> particle "mass", so this is a problem for me.
>>>
>>> And I'm using the "id" field to make sure the particles are properly
>>> associated with their past selves in the "TemporalParticlesToPathlines"
>>> filter.
>>>
>>> Any thoughts? Didn't find anything via Google (though I limited the
>>> search to the past year).
>>>
>>> Oh, and I tried this both with ParaView versions 4.0.1 and 4.1.0.
>>>
>>> Thank you,
>>> Bill
>>>
>>> --
>>> Bill Sherman
>>> Sr. Technology Advisor
>>> Advanced Visualization Lab
>>> Pervasive Technology Inst
>>> Indiana University
>>> shermanw at indiana.edu <mailto:shermanw at indiana.edu>
>>> _________________________________________________
>>> Powered by www.kitware.com <http://www.kitware.com>
>>>
>>> Visit other Kitware open-source projects at
>>> http://www.kitware.com/__opensource/opensource.html
>>> <http://www.kitware.com/opensource/opensource.html>
>>>
>>> Please keep messages on-topic and check the ParaView Wiki at:
>>> http://paraview.org/Wiki/__ParaView <http://paraview.org/Wiki/ParaView>
>>>
>>> Follow this link to subscribe/unsubscribe:
>>> http://public.kitware.com/__mailman/listinfo/paraview
>>> <http://public.kitware.com/mailman/listinfo/paraview>
>>>
>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140703/9b4d2067/attachment-0001.html>