Ok, I'll fill the a bug report. On Tue, Nov 29, 2011 at 4:18 PM, Biddiscombe, John A. <[email protected]> wrote: > If you're developing an algorithm that changes the dimensions of an image and > you want it to work inside paraview, then you'd best just give up and instead > throw yourself from a tall building. Especially so if you convert images to > meshes or vice versa (or back again to images later). The way structured > extents are handled in paraview is so dreadfully poor that even when you get > it right, you'll have great trouble if you try to run in parallel. (Some > filters will add a ghost level to the information and allow the executives to > extend the update extent, others will manually change the update extent > inside RequestUpdateExtent and there is no consistency in behaviour). > > As you correctly point out, if your pipeline doesn't know the size of the > extent until execution time due to some algorithmic twist, life becomes very > hard indeed. I would say that getting extents to work wastes more of my time > than any other task in paraview development. To avoid modifying the extent inside the algorithm, I was thinking whether combining my filter with vtkExtractVOI (passing the new extent via an exposed property) could work out. What do you think?
> One thing that has changed is that one of the extent translators gets > replaced early in the pipeline (when you use an image reader I think), and > there's an option in the gui under setting to "use strict load balancing" - > if you switch this on/off and try again, do you get any better results? Well, I saw this tweak in some post, but as I don't use the default Paraview application, my workflow is a bit different. However, I found the relevant bits inside the Paraview source and locally modified it and recompiled all the libraries. It didn't work. > JB > > -----Original Message----- > From: [email protected] [mailto:[email protected]] On > Behalf Of David E DeMarle > Sent: 29 November 2011 15:49 > To: Jorge Gerardo Peña Pastor; Fred Fred > Cc: [email protected] > Subject: Re: [Paraview] Problem after updating from Paraview 3.8.1 to > Paraview 3.12 > > Can one of you report this on the bug tracker? Ideally with example code that > replicates the problem. There were a handful of changes to > VTK/Filtering/vtkStreamingDemandDrivenPipeline that could have caused this. > > If the problem is on the bug tracker we are less likely to loose it. > > David E DeMarle > Kitware, Inc. > R&D Engineer > 21 Corporate Drive > Clifton Park, NY 12065-8662 > Phone: 518-881-4909 > > > > 2011/11/15 Jorge Gerardo Peña Pastor <[email protected]>: >> Hello, >> >> I've managed to run a Paraview based application created with Paraview >> 3.8.1 using Paraview 3.12, but one of my filters is reporting an error >> it didn't before. >> >> My vtkAlgorithm is a sub-class of vtkImageAlgorithm, which as a result >> of processing the input data generates a new vtkImageData which is >> smaller than the original one. >> Before, I managed to use that filter in my application, but now I get >> the following error: >> ERROR: >> src/ParaView-3.12.0/VTK/Filtering/vtkStreamingDemandDrivenPipeline.cxx >> , >> line 1009 >> vtkPVCompositeDataPipeline (0x4c3dca0): The update extent specified in >> the information for output port 0 on algorithm >> vtkConnectedThresholdImageFilter(0x4c3c8d0) is 0 698 0 535 0 114, >> which is outside the whole extent 408 421 86 106 0 1. >> >> Inside my RequestData I've tried changing all possible combinations of >> whole extent, update extent and extent for both output and >> outputInformation without success. >> >> I've found several threads talking about changing >> StreamDrivenPipeline::WHOLE_EXTENT inside RequestUpdateExtent, but in >> order to change the value there I need to execute before at least one >> time my algorithm because the extent depends on the result of the >> algorithm. >> >> Could someone point me in the right direction to make this work with >> Paraview 3.12? >> >> Thank you for your help. >> _______________________________________________ >> 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 _______________________________________________ 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
