Dave Akers (dla)
Thu, 20 Jan 2000 14:52:49 -0800
It's true that the way Volumizer handles boundary conditions in 3-D
texturing mode causes a division-by-zero when one of the dimensions of
your data is exactly 1. (It is as if your volume was infinitely thin,
having only 1 slice of data.) Try setting the "overlap" parameter to "0"
and then set the brick size explicitly after the call to
voAppearanceActions::getBestParameters().. and you should see your data,
although you'll get some weird artifacts from the slicing. May I ask why
you're wanting to generate volume renderings of data that's only 1-slice
thick? Seems to me that there are better ways of doing this.. (e.g.
simply applying a texture to a polygon..) ;)
-Dave
On Thu, 6 Jan 2000, Mark Davey wrote:
> Hi..
>
> I have noticed that the demos do not run if there is only one slice
> present in the data set.
> I get an error message
>
> Trace/BPT trap (core dumped)
>
> if I attempt to load just 1 slice. Does anyone know why this is?
>
> The error occurs at the new voBrickSetCollection call..
>
> Mark
>
>
>
> --
> From: Mark Davey
> Dept. of Medical Physics, UCL.
>
> TEL: +44 (0)171 915 1673.
> FAX: +44 (0)171 837 9279.
>
> Institute of Laryngology and Otology,
> 330 Gray's Inn Road,
> London.
> WC1X 8GE.
>
>
>
This archive was generated by hypermail 2.0b2 on Thu Jan 20 2000 - 15:24:03 PST