The parallel example is based on medical1.cxx from the vtk 2.x distribution. The code includes a regular Performer application as well as a pfCAVE application. The example demonstrates how vtkActorToPF can be used to make VTK more interactive.
The example application makes use of a modified vtkActorToPFTranslator class called vtkActorToPFTranslatorParallel. The translator objects are instantiated from shared memory so that both the Performer and the VTK processes can access them. On the VTK side, the translator continually calls Update() on the vtkActor. If there are any changes in the VTK pipeline, they will propogate to the end of the pipeline which will cause the translator to re-execute and store the new geometry. On the Performer side, before each rendering, the translator checks to see if new geometry is available. If so , the translator plugs the new geometry into the scenegraph, replacing the old geometry.
Split 3 times (8 VTK pipelines)
This example is now part of the overall vtkActorToPF distribution. See the code section.
Thanks to Jan Ehrhardt for a fix to a X problem that was happening on Onyxs!
When running this example, you should notice two things:
- If you have multiple CPUs, the isosurface generation will speedup.
- You should be able to interact with the scene while a new isosurface is being computed.