<div>vtkExtractVOI gives different results on vtkContourFilter and vtkVolumeRayCastMapper.</div>
<div>especially the SetVOI </div>
<div> </div>
<div>SetVOI carries arguments in a manner as below:</div>
<div> </div>
<div>SetVOI a b c d e f ( a...f = integer)</div>
<div> </div>
<div>the "a" actually affect the output.</div>
<div> </div>
<div>in vtkContourFilter, when the part was "cut" off, the postion of the cut-off part will be reserve</div>
<div> </div>
<div>however in vtkVolumeRayCastMapper, it does not reserve the space of the cut-off part, and pushes the whole object to left (simply because the left cut-off part is no more there ) </div>
<div> </div>
<div>so it make the volumn rendering content can not "register" with iso-surface rendering. i know the cause of the problem, but i haven't find the solution yet.... maybe there are some other implementation on this....
</div>
<div> </div>
<div>thank you for your advice.</div>
<div> </div>
<div>regards</div>
<div> </div>
<div>Yours</div><span>
<div>Pan</div></span><br><br>
<div><span class="gmail_quote">On 9/6/05, <b class="gmail_sendername">Day, Robert</b> <<a href="mailto:Robert.Day@health.wa.gov.au">Robert.Day@health.wa.gov.au</a>> wrote:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Its only a guess, based on looking at the picture and no code, and I don't use volumes much.<br><br>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.
<br><br>It would be easier to guess with some code...<br><br>Rob.<br>--<br>Robert Day ph +61 8 9224 3227<br>Project Bioengineer fax +61 8 9224 1138<br>Royal Perth Hospital <a href="mailto:robert.day@health.wa.gov.au">
robert.day@health.wa.gov.au</a><br><br>> -----Original Message-----<br>> From: Peter [mailto:<a href="mailto:meancity@gmail.com">meancity@gmail.com</a>]<br>> Sent: Saturday, 27 August 2005 2:19 PM<br>> To: <a href="mailto:vtkusers@vtk.org">
vtkusers@vtk.org</a><br>> Subject: [vtkusers] volume rendering content does not fit into the<br>> isosurface<br>><br>><br>> Dear All,<br>><br>> i have a question, i am doing some rending for a 3D object.
<br>><br>> first i did isosurface rendering for the objects.<br>> then i did volume rendering.<br>><br>> these two rending process in same file, but when i run the script,<br>> the volume rendering content does not fit into the isosurface, i tried
<br>> to find the problem, but i still can't figure it out by far. i suppose<br>> the volume rendering content should exactly fit into the isosurface.<br>> but the result showed that there are just some part of<br>
> overlapping.....<br>><br>> so can someone out there to help me out on this issue...<br>><br>> thank you in advance,<br>><br>> Yours<br>> Pan<br><snip><br></blockquote></div><br>