<html>
<font size=3>Hi Felix,<br><br>
Firstly you can resample ( vtkImageResample, vtkImageShrink3D ) the
dataset down, this may depend on whether or not you really need to see
everything at full scale when you are looking at the entire
dataset. <br>
After rendering a subsampled complete dataset, you could then extract
regions of interest ( vtkImageThreshold, vtkExtractVOI, vtkImageReslice )
and render those at full scale.<br>
Secondly, you can render it with texturemapping
(vtkVolumeTextureMapper2D) instead of raycasting
(vtkVolumeRayCastMapper), this will get you a bit more performance on the
interaction/rendering.<br><br>
Also, you can degrade the precision of the rendering if you are bogging
down you machine by changing the number of texture planes actually
rendered:<br>
vtkVolumeTextureMapper2D->SetMaximumNumberOfPlanes( 20 );<br>
or ray casting sampling:<br>
vtkVolumeRayCastMapper->SetImageSampleDistance( 2.0 );<br><br>
Budd.<br><br>
At 05:01 PM 5/16/2003 +0200, you wrote:<br>
<blockquote type=cite class=cite cite>i'm having micro-CT data that is
pretty large (100 MB).<br>
has anyone information or some hints on how to best <br>
render such large data on an average workstation unsing vtk?<br>
(2GHz, 1GB RAM, Geforce4)<br><br>
TIA,<br>
felix schwenk<br><br>
_______________________________________________<br>
This is the private VTK discussion list. <br>
Please keep messages on-topic. Check the FAQ at:
<<a href="http://public.kitware.com/cgi-bin/vtkfaq" eudora="autourl">http://public.kitware.com/cgi-bin/vtkfaq</a>><br>
Follow this link to subscribe/unsubscribe:<br>
<a href="http://public.kitware.com/mailman/listinfo/vtkusers" eudora="autourl">http://public.kitware.com/mailman/listinfo/vtkusers</a>
</font></blockquote></html>