Dave Akers (dla)
Tue, 7 Dec 1999 11:59:29 -0800
I can see how adding a format specifier to the voxel modification
routines could be useful. Of course, you are trading speed for memory
conservation if you expect to do conversions on every "set" operation..
the routines in 1.2 are optimized for the case where no conversion is
necessary. Nevertheless, I will put in an RFE for this new feature..
-Dave
On Tue, 7 Dec 1999, Mark Davey wrote:
> Hi...
> I have just read Dave Akers' comments regarding the new voxel
> modification routines.
>
> I feel that it is a shame that the data to be re-loaded into brick
> memory should be in the brick data format. Take for example an image
> processing application. Data is copied in disk format to RAM. From RAM
> it is copied into brick memory for the purpose of visualisation with any
> format conversions being carried out. Image processing is performed on
> the RAM copy and the results are re-loaded into brick memory. If the
> disk and brick formats are different then am I right in things that the
> conversion will still need to be done by the user of Volumizer. The
> other option is to do the image processing on a copy of the data that is
> in the brick(external) format. However this may mean dealing with 4
> times as much data as is necessary (i.e. BYTE-LUMINANCE disk format and
> RGBA external format). This doesnt seem very efficient does it?
>
> Would it be useful to add a variable to the new routines specifying the
> format of the data to be copied into and out of brick memory?
>
> Regards
> 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 Tue Dec 07 1999 - 15:25:13 PST