ParaView/Users Guide/Parallel Rendering Intro

From KitwarePublic
< ParaView
Revision as of 22:13, 14 February 2011 by 192.168.1.74 (talk) (spew text to link the sections together)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigationJump to search

One of ParaView's strengths is its ability to offload the often demanding rendering task. By offload, we mean that ParaView allows you to connect to a remote machine, ideally one that is closer to the data and to high-end rendering hardware, do the rendering on that machine and still interact with the data from a convenient location, such as the desktop or laptop in your office.

Abstracting away the location where rendering takes place opens up many possibilities. First, it opens up the possibility to parallelize the job of rendering to make it possible to render huge data sets at interactive rates. Rendering is done in the parallel Render Server component, which may be part of or separate from the parallel Data Server component. In the next section we describe how parallel rendering works and explain the controls you have over it. Second, huge datasets often require high resolution displays to view the intricate details within while maintaining a high level view to maintain context. In the following section we explain how ParaView can be used to drive tile display walls. Lastly, with the number of displays free to vary, it becomes possible to use ParaView to drive multi-display Virtual Reality systems. That is described in the final section of this chapter.