[vtkusers] volume rendering content does not fit into the isosurface

Day, Robert Robert.Day at health.wa.gov.au
Mon Sep 5 23:03:46 EDT 2005


Its only a guess, based on looking at the picture and no code, and I don't use volumes much.

I'd say the origin for the volume data set is not the same as the surface.  As I recall, volumes have the origin at one corner, whereas the CT may well have the origin at the isocentre of the scanner.  So the surface polydata will inherit this origin, but the volume may well have its origin at the corner.

It would be easier to guess with some code...

Rob.
--
Robert Day            ph  +61 8 9224 3227
Project Bioengineer   fax +61 8 9224 1138
Royal Perth Hospital  robert.day at health.wa.gov.au

> -----Original Message-----
> From: Peter [mailto:meancity at gmail.com]
> Sent: Saturday, 27 August 2005 2:19 PM
> To: vtkusers at vtk.org
> Subject: [vtkusers] volume rendering content does not fit into the
> isosurface
> 
> 
> Dear All,
> 
> i have a question, i am doing some rending for a 3D object.
> 
> first i did isosurface rendering for the objects.
> then i did volume rendering.
> 
> these two rending process in same file, but when i run the script,
> the volume rendering content does not fit into the isosurface, i tried
> to find the problem, but i still can't figure it out by far. i suppose
> the volume rendering content should exactly fit into the isosurface.
> but the result showed that there are just some part of
> overlapping.....
> 
> so can someone out there to help me out on this issue...
> 
> thank you in advance,
> 
> Yours
> Pan
<snip>



More information about the vtkusers mailing list