[Paraview] Not understanding large memory use

[Mike Jackson]

Thanks for the hint. I am now using an ExtractVOI to look at the sub  
volumes that I want. The only downside to this is that I can not look  
at "off angles". I can only compare the orthogonal axis.. which may  
be fine for now but at least I can now bring in my meshed surface and  
do a comparison of how well the mesh conformed to the original images.

On a related note. I have a 16 node AMD64 Linux Cluster at my  
disposal. Sadly it is just acting as a CVS server at the moment..  
what a waste. Each node has 2GB of RAM. How involved is it getting  
Paraview running so that I can distribute the rendering to all the  
nodes? And would this help me out in this situation?

Thanks.

On Jan 5, 2007, at 9:24 AM, Berk Geveci wrote:

> Kent is right. Clip generates an unstructured grid and it would
> significantly increase the memory usage due to the creation of
> explicit geometry (cells and points). Unfortunately, there is no way
> of "clipping" an image to produce another image in VTK. Depending on
> what you are trying to accomplish, a combination of clipping the
> surface (generated with extract surface) and cutting may be what you
> want.
>
> -berk
>
> On 1/5/07, Kent Eschenberg <eschenbe at psc.edu> wrote:
>> Mike,
>>
>> I think that clip first turns everything into tetrahedrals.
>>
>> Kent
>> Pittsburgh Supercomputer Center
>>
>>
>
>
> -- 
> Berk Geveci
> Kitware Inc.



-- 
Mike Jackson   Senior Research Engineer
Innovative Management & Technology Services