help > Cube "intersection"
Showing 1-6 of 6 posts
Display:
Results per page:
Jul 15, 2010  10:07 AM | Aurelien Lucchi
Cube "intersection"
Hello,
I have 2 cubes : one contains the raw data (biomedical images) and the other cube contains a series of black and white images (mask images). I would like to visualize the raw data for which the corresponding mask data has a certain value. Is there already a way to do that in v3d ? I f not, I guess a plugin can easily be implemented...
Jul 17, 2010  01:07 AM | Hanchuan Peng
RE: Cube "intersection"
why not just use the "link-out" and "linked" function in the tri-view main window?

another way is that use the surface generating function in the 3d viewer to produce a surface mesh for the mask image, and then overlay the surface mesh on top of the 3d rendered grayscale image.

Originally posted by Aurelien Lucchi:
Hello,
I have 2 cubes : one contains the raw data (biomedical images) and the other cube contains a series of black and white images (mask images). I would like to visualize the raw data for which the corresponding mask data has a certain value. Is there already a way to do that in v3d ? I f not, I guess a plugin can easily be implemented...[/userquote]
Jul 19, 2010  05:07 AM | Aurelien Lucchi
RE: Cube "intersection"
I actually ended up writing a plugin, which only took 20 minutes :-)
Generating a surface would work too but I guess the rendering would be slowed down. By the way, are those surfaces handled as openGL display lists ? What about landmarks ?

Cheers
Jul 19, 2010  01:07 PM | Hanchuan Peng
RE: Cube "intersection"
good to know your plugin works!

The surface is also handled by OpenGL. During the up-coming v3d hackathon next week we may optimize the surface display.

The landmarks are another type of surface objects, and are handled by opengl as well.

To make the rendering not delayed by a plugin, we can re-generate the plugin interface to allow it use threads. This will also be interesting topic during the hackathon.

-h

Originally posted by Aurelien Lucchi:
I actually ended up writing a plugin, which only took 20 minutes :-)
Generating a surface would work too but I guess the rendering would be slowed down. By the way, are those surfaces handled as openGL display lists ? What about landmarks ?

Cheers[/userquote]
Jul 19, 2010  03:07 PM | Aurelien Lucchi
RE: Cube "intersection"
Originally posted by Hanchuan Peng:

To make the rendering not delayed by a plugin, we can re-generate the plugin interface to allow it use threads. This will also be interesting topic during the hackathon.
[/userquote]

This is indeed a very important topic of discussions. Users should be able to access the graphics capabilities of v3d from the plugin interface. Threading will only be useful for the computation part. You also need something to allow users to insert some content in the OpenGL rendering loop. I guess you could have a virtual function in the V3dPluginInterface class that is called by the rendering loop.
Another way would be to create display lists (see http://www.lighthouse3d.com/opengl/displ... for an example)...
Jul 19, 2010  05:07 PM | Hanchuan Peng
RE: Cube "intersection"
indeed it is in our to-do-list to let a user be able to control all behaviors of the 3d viewer through the plugin interface. we should continue discussing this next week.