4 ms·
I'm currently building a visualization app(with medical data) using WebGL (and google's O3D framework) and it's working great. I strongly suggest looking at O3D
by nkassis 16y ago
I'm currently building a visualization app(with medical data) using WebGL (and google's O3D framework) and it's working great. I strongly suggest looking at O3D even if it's a little rough right now since they transitioned from a plugin to webgl. The doc hasn't yet been updated.
We already have users using it in work settings using firefox 4 beta and chrome builds.
The worse problem I'm hitting with this stuff is getting the browser to fetch the data needed quickly and efficiently. I'm trying to figure out if I can use the BinaryBlob interface in the new javascript FileAPI spec to see if that could be used. Right now I'm parsing plain text data (gzipped server side) and it's slow.
- okusoko 16y agoYes! I've seen a demo of WebGL used in medical imaging: http://imaging.robarts.ca/~dcantor/?p=133 http://imaging.robarts.ca/~dcantor/?p=133 3D medical data sets, from PET scans and such, are indeed huge in size. Typically GB's of voxel data. The sort of thing that requires an overnight download unfortunately. One possible optimization is to recreate the 3D vertex set from a series of 2D texture images, by interpolating vertex positions between frames. Surprisingly only a small subset of images is needed to recreate the resulting 3D geometry, but the tessellation calculations are pretty math intensive.
- nkassis 16y agoWow, I didn't know someone at Robarts was doing this stuff( I work for McGill another University in Canada ;p) I'll have to communicate with him. I've managed to get some full volumes loaded in my app. It was a scan of my brain. That work ok (slow and takes a few minutes to load) but when I loaded the brain or a rat, my app totally crashed. To be fair the rats brain was at a higher resolution :)