[vtkusers] Problem with allocating memory for huge vtkImage and memory-fragmentation ?

[David E DeMarle]

Not sure about directly rendering image data.

As Kevin hinted at, assuming you go the image->filters->polydata
route, there is vtkPolyDataMapper::SetPiece/NumberOfPieces to do the
partitioning manually, and/or SetNumberOfSubPieces to have the mapper
iterate.

You should also pay close attention to the vtkExtentTranslator to make
sure the image decomposition suites your use case.

David E DeMarle
Kitware, Inc.
R&D Engineer
28 Corporate Drive
Clifton Park, NY 12065-8662
Phone: 518-371-3971 x109



On Fri, Apr 8, 2011 at 9:50 AM, Kevin H. Hobbs <hobbsk at ohio.edu> wrote:
> On 04/08/2011 05:42 AM, David Gobbi wrote:
>> There is a class called vtkImageDataStreamer that will pull the data
>> through the pipeline in smallish chunks, but it still stores the
>> result as a big, contiguous block.  That's just the way that
>> vtkImageData stores images.
>>
>
> vtkImageDataStreamer only streams the "upstream" filters.
>
> To get end to end streaming you need to do the streaming at the end of
> the pipeline by SetNumberOfPieces on the writer.
>
> I believe there's something similar to render in pieces as well.
>
>
> _______________________________________________
> 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 VTK FAQ at: http://www.vtk.org/Wiki/VTK_FAQ
>
> Follow this link to subscribe/unsubscribe:
> http://www.vtk.org/mailman/listinfo/vtkusers
>
>