in my application I have to access the voxel data
for additional tasks apart from the visual rendering.
As accessing the data by "getVoxelAddr" is not very
efficient, I would like to maintain my own voxel data
management. I would be glad, if you could tell me, what
the best approach to this problem is.
From my point of view, I need the following steps:
* Load the 3D data into my own memory structure
(probably a long one-dimensional array). The data
should be stored in x,y,z order.
* Use Volumizer to determine the correct brick sizes, etc.
* To get the pointer to the data, replace in the function
"myReadBrickIfl" the line
with my own code, that finds the pointer to the requested
data in my memory structure. Unfortunately, there might
be a problem, if the brick requests sizes, which are only
a part of the full x,y length.
Do you think, this is the right approach? Is Volumizer
internally changing any of the data that is sent to a brick
or can I still use it for my other calculations?
Any input you could give me on this issue is greatly
appreciated.
Thank you,
Matthias Harders
--
---------------------------------------------------------------------
Matthias Harders M. Sc. Computer Science
Gloriastrasse 35, Room F81 Communication Technology Lab
CH-8092 Zuerich Image Science Group
Switzerland ETH Zuerich
Tel. ++ 41 1 632 52 79 Fax ++ 41 1 632 11 99
---------------------------------------------------------------------
