Jerome, The VTK class has the trick to override the extent-translator which is what does-what-it-does in ParaView. ParaView by default overrides the extent translator with vtkPVExtentTranslator which uses the original data exetent information for partitioning and that's what messes such fancy pipelines up. The filer can explicitly override ParaView's behavior. So to answer, no, there's nothing on ParaView side that needs to be added to support changing of extents it is in the pipeline.
Utkarsh On Thu, Jun 3, 2010 at 2:24 PM, Jérôme <[email protected]> wrote: > Hi Utkarsh, > > Thanks for your tips. I will take a look around this class. Though I have > a question: This is a VTK class, and I don't have problem in stand-alone > VTK applications. If I have to change something in VTK classes, it means > that I will have duplicated filters, the native VTK ones and the modified > of mine... Don't you think there something on ParaView-side to do? > > Thanks again and best regards, > Jerome > > 2010/6/3 Utkarsh Ayachit <[email protected]>: >> Jerome, >> >> You may want to look at VTK/Hybrid/vtkImageDataLIC2D.cxx to see how it >> plays tricks with the extent-translator to generate images with larger >> extent when magnification > 1. >> >> Utkarsh >> >> On Thu, Jun 3, 2010 at 5:02 AM, Jérôme <[email protected]> wrote: >>> Finally, I found a bug opened 6 months ago: >>> http://www.paraview.org/Bug/view.php?id=10125 >>> I added a note. I hope that it will interest some PV gurus >>> >>> Jerome >>> >>> 2010/6/2 Jérôme <[email protected]>: >>>> Dear all, >>>> >>>> I fill very surprised that *nobody* has to resample some data inside >>>> ParaView. Several threads deal with enabling some VTK filters in >>>> ParaView that actually change the extent of the input image (just as >>>> vtkImageResample), but when the output extent is higher that input, >>>> there is a strange behaviour. Sorry for being lazy: the problem was >>>> described in the following threads. >>>> http://www.paraview.org/pipermail/paraview/2010-May/017309.html >>>> http://www.paraview.org/pipermail/paraview/2009-October/014306.html >>>> http://www.paraview.org/pipermail/paraview/2009-April/011945.html >>>> >>>> Please, tell me if I am doing something wrong in the XML, if I am >>>> stupid, if this is a known limitation of ParaView, if I am not sending >>>> to the right mailing list, if [put your own proposition]. >>>> >>>> Thanks for all, and best regards. >>>> Jerome >>>> >>>> PS: you can find the incriminated XML files here: >>>> http://github.com/jeromevelut/Peavip . Beware of the Spline Filter, >>>> another pending request has been sent. >>>> >>> _______________________________________________ >>> 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
