Info-Volumizer Mailing List Archives: Extraction of data from b
Extraction of data from bricks
Mark Davey (mkd@medphys.ucl.ac.uk)
Mon, 16 Aug 1999 16:23:13 -0700
Hi,
I wish to implement some filters on the data that has been loaded into
volumizer. I guess the simplest way of doing this is to copy the entire
data set from bricks into a contiguous chunk of memory, perform the
filter and reload the bricks.
I have a number of reasons why I do not wish to keep multiple copies of
the same data set in memory so I want to create a temporary copy used
just during the filtering process.
However, how does volumeOptimise affect things if INTERLEAVE_2WAY has
happened as part of the optimisation process?
The question really then is as follows: Can I UnOptimise the
bricksetcollection before attempting to extract the data. After
reloading the bricks can I then volumeOptimise as I did when first
loading the data into volumizer?
Finally, does anyone have any code segments demonstrating an efficient
way of handling data when it could be in a number of different formats
and bytes per channel. I would be looking to write code within which the
format etc. of the data was kept as transparent as possible.
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 Mon Nov 01 1999 - 14:21:40 PST
|
