From: Salmon on
isosurface is used to create surface from a volume. For example, an MRI dataset could be 512x512x400. This is 104 MB in uint8. However, the isosurface can only take double, which is
838MB memory space, which immediately overflows. Even if downsample the dataset to 256x256x200, that's still a very large dataset if using "double".

I tried to use isosurface on the subset of the volume set, and combine the generated patches. However, I found this is not easy to do, and has to rely a lot on human interaction.

"Jose " <jirey(a)mail.usf.edu> wrote in message <hmp5vc$ar5$1(a)fred.mathworks.com>...
> Isosurface is a great function, I am taking advantage of it too.... But, I also have a large dataset, and this function eats up a LOT of memory, and is the bottleneck in my code.
>
> I downsample my surfaces using the reducepatch() which I believe tries to reduce the number of vertices but still keeps the shape, so it has to move vertices around. If you can affort to move vertices around, then this might be something worth working with.
> hworks.com>...
From: Ravi on
Hi,

I just wanted to point out that MATLAB isosurface function has a lot of problems for complex data.

I have created a program that renders exact error-free surfaces from 3-D voxel data, such as from MRI, CT Scan.

The following is the link to the discussion thread

http://www.mathworks.com/matlabcentral/newsreader/view_thread/268226#755017

You can download the program from

http://www.hermesacademy.com/products

Ravi


"Salmon" <yourfellow(a)yahoo.com> wrote in message <htj8j7$v8$1(a)fred.mathworks.com>...
> isosurface is used to create surface from a volume. For example, an MRI dataset could be 512x512x400. This is 104 MB in uint8. However, the isosurface can only take double, which is
> 838MB memory space, which immediately overflows. Even if downsample the dataset to 256x256x200, that's still a very large dataset if using "double".
>
> I tried to use isosurface on the subset of the volume set, and combine the generated patches. However, I found this is not easy to do, and has to rely a lot on human interaction.
>
> "Jose " <jirey(a)mail.usf.edu> wrote in message <hmp5vc$ar5$1(a)fred.mathworks.com>...
> > Isosurface is a great function, I am taking advantage of it too.... But, I also have a large dataset, and this function eats up a LOT of memory, and is the bottleneck in my code.
> >
> > I downsample my surfaces using the reducepatch() which I believe tries to reduce the number of vertices but still keeps the shape, so it has to move vertices around. If you can affort to move vertices around, then this might be something worth working with.
> > hworks.com>...