[vtk-developers] Pipeline connections that pull information but not data

David Gobbi david.gobbi at gmail.com
Fri Nov 19 15:29:19 EST 2010


It was crashing in AllocateData for vtkImageData.  As long as you
think that the empty extent solution is fine, then I can find out why
it isn't working and then post a fix on Gerrit for you to review.  I'm
hoping that only minor changes will be required, but that remains to
be seen.

  David


On Fri, Nov 19, 2010 at 12:35 PM, Berk Geveci <berk.geveci at kitware.com> wrote:
> I'd say that we should make it possible to ask for an empty extent. Where is
> it crashing?
>
> On Thu, Nov 18, 2010 at 12:25 PM, David Gobbi <david.gobbi at gmail.com> wrote:
>>
>> Hi All,
>>
>> I'm working on a difficult problem, and would appreciate any pointers
>> that the pipeline experts can give me.  Some of the classes that I
>> contributed to VTK way back before the VTK 5 release still use some
>> VTK 4 pipeline mechanisms.  I've been gradually converting them to the
>> new executive, but I've a wall.
>>
>> In vtkImageReslice there is a method called SetInformationInput(),
>> that allows the primary input image to be resampled to match the
>> "information input" image.  I implemented this by calling
>> UpdateInformation() on the InformationInput, so that I can pull just
>> the information from that input and not the data.
>>
>> In the VTK 5 executive, there does not seem to be any way to establish
>> a pipeline connection that only pulls information.  When REQUEST_DATA
>> goes to the executive it is always forwarded to all inputs.  I've
>> tried the obvious thing, which is to set an empty UPDATE_EXTENT on the
>> input that I don't want any data from, but this causes a segfault.
>>
>> Any ideas?
>>
>>  David
>> _______________________________________________
>> Powered by www.kitware.com
>>
>> Visit other Kitware open-source projects at
>> http://www.kitware.com/opensource/opensource.html
>>
>> Follow this link to subscribe/unsubscribe:
>> http://www.vtk.org/mailman/listinfo/vtk-developers
>>
>
>



More information about the vtk-developers mailing list