ParaView/Users Guide/Parallel Rendering Intro: Difference between revisions

From KitwarePublic
Jump to navigationJump to search
No edit summary
(Replaced content with "{{ParaView/Template/DeprecatedUsersGuide}}")
 
(One intermediate revision by the same user not shown)
Line 1: Line 1:
One of ParaView's strengths is its ability to off-load 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, to do the rendering on that machine and still interact with the data from a convenient location.
{{ParaView/Template/DeprecatedUsersGuide}}
 
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.

Latest revision as of 18:41, 14 January 2015

PAGE DELETED
The Users Guide has been moved from the Wiki to The ParaView Guide. Please use the history if you want to access the old version of this document.