| voxel_proj and array type [message #42196] |
Tue, 04 January 2005 11:28  |
edwardg
Messages: 5
Registered: August 2003
|
Junior Member |
|
|
Hi all,
I'm working on a GUI to display and analyze medical images, and have
incorporated a maximum intensity projection (MIP) utility using
VOXEL_PROJ and T3D. Typically i'm using either int or float arrays, and i
convert them to byte by window/levelling after pulling out the slice i
want.
I'd like to do the MIP before converting to byte so i don't have to
reproject every time the user changes the window/level settings. However,
VOXEL_PROJ seems to insist on working on byte data arrays. Does anyone
have any ideas on how to get around this problem?
Thanks!
Ted
|
|
|
|
| Re: voxel_proj and array type [message #42347 is a reply to message #42196] |
Fri, 28 January 2005 10:53  |
Mike Miller
Messages: 3
Registered: January 2002
|
Junior Member |
|
|
Edward Graves wrote:
> I'm working on a GUI to display and analyze medical images, and have
> incorporated a maximum intensity projection (MIP) utility using
> VOXEL_PROJ and T3D. Typically i'm using either int or float arrays,
and i
> convert them to byte by window/levelling after pulling out the slice
i
> want.
> I'd like to do the MIP before converting to byte so i don't have to
> reproject every time the user changes the window/level settings.
However,
> VOXEL_PROJ seems to insist on working on byte data arrays. Does
anyone
> have any ideas on how to get around this problem?
I have done this by rotating a 3D image volume and projecting it with
the
total (for projections, as in img = max(vol, dimension=1))) or max (for
MIPs,
as in img = total(vol, 2)) functions. This works fine with any data
type and
the resulting images can be byte scaled and tv'd, or decomposed and
tv'd or
whatever.
Mike
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
