[Paraview] parallel run filter operate on plane source

[Bam Ting]

I look more at how the distribute stream tracer work and learnt that it work
by setting: UPDATE_PIECE_NUMBER() to 0 and UPDATE_NUMBER_OF_PIECES to 1.
Apparently this cause data from process 0 to be transfer across network to
other process. I make a guess here, is that correct?



On Fri, Aug 7, 2009 at 12:45 PM, Bam Ting <bampingting at gmail.com> wrote:

> Forgive my misconception before! I am baffelt by how this work!
>
> I looked closer. I see plane source on my imput is empty! bounds 1 -1 ...
> on all process except 0... so that answer something! before this I suppose
> that the source must be duplicate on all process, because the class doc for
> vtkPStreamTracer say thaat this must be so. Now I will like to know how does
> filter such as distributed stream tracer work in this case (plane source is
> empty on all imput except 0)? Web doc day seed points must be the same
> across on all process? Can we explain how paraview works here?
>
>
>
>
>
> On Fri, Aug 7, 2009 at 11:22 AM, Bam Ting <bampingting at gmail.com> wrote:
>
>> Have some issue with a filter that operate on plane source when run with
>> more than a single process. Plane source on imput seem to be duplicated
>> identical on all processes (no problem), then my filter run and make a
>> shallow copy of the source and pass to output (problem start!). In the
>> spreadsheet view I see more points than I should in the output, + I add
>> point data I see more point data as well, I explore with spreadsheet view
>> show that unexpected point data all duplicate of expected.
>>
>> My question, how paraview handle source duplicated on all process? How
>> paraview can know that the data is duplicate for plane source? How does it
>> render such duplicate data? I seek to add some point data to plane source
>> and provide on the output. What I need to do in the filter to avoid the
>> issue?
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.paraview.org/pipermail/paraview/attachments/20090807/ae8809b8/attachment.htm>