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:
from paraview import util self.GetExecutive().SetExtentTranslator(self.GetExecutive().GetOutputInformation(0), vtk.vtkExtentTranslator()) -berk On Tue, Feb 10, 2009 at 5:54 AM, Jean Favre <[email protected]> wrote: > > I have a python programmable source which mimics an already working C++ > Reader. The Reader works in parallel and correctly gets the Update > Extent assigning to each proc, a different sub-region of the whole. The > Python prog. source works fine in serial mode. > > When run in parallel, *all* procs receive the same Update Extent equal > to the Whole Extent, as if the Extent Translator ignores the > parallelism. I get the following printed for the Update Extent: > > Process id: 0 >> (0, 63, 0, 31, 0, 24) > Process id: 3 >> (0, 63, 0, 31, 0, 24) > Process id: 2 >> (0, 63, 0, 31, 0, 24) > Process id: 1 >> (0, 63, 0, 31, 0, 24) > > Have other been successful with Programmable Source running in parallel? > > My script is atached. > > Jean -- > Swiss National Supercomputing Center > > > _______________________________________________ > 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 > > Follow this link to subscribe/unsubscribe: > http://www.paraview.org/mailman/listinfo/paraview > > _______________________________________________ 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 Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview
