[Paraview] python programmable source not parallel?

[Berk Geveci]

> As per the motivation of the ParaView developpers to do that, besides
> providing an exercise for the more adventurous folks?

This was left from the days when charts expected rectilinear grid
input. Consider the case where you are applying a programmable filter
to an unstructured grid which computed a histogram. In that case, you
don't want to produce a portion of the output in each process but
rather produce the whole output and accumulate the result somehow.
Since we now use tables for charts, that can probably go away. I will
think a bit more before I remove it.

-berk

On Tue, Feb 10, 2009 at 9:31 AM, Jean Favre <jfavre at cscs.ch> wrote:
> Berk Geveci wrote:
>> This is a "feature" rather than a bug. The programmable source sets
>> the extent translator to be a vtkOnePieceExtentTranslator. To override
>> this behavior, add the following to your RequestInformations script:
>>
> The thought never crossed my mind this could be a bug, but it sure
> defied my understanding of parallelism. Made me doubt for a while.
>
> As per the motivation of the ParaView developpers to do that, besides
> providing an exercise for the more adventurous folks?
>
> N.B. I added the code in my Update Script, not in the RequestInformation
> Script as suggested, because it would cause the server to crash. (PV 3.4.0)
>
> Thanks for the tip.
> Jean
>