Representations and Views: Difference between revisions

From KitwarePublic
Jump to navigationJump to search
mNo edit summary
No edit summary
Line 1: Line 1:
A description can be found here: [[Media:Pv_pipelines.pdf]]
ParaView's display pipeline supports a large number of rendering modes and options. The output of every filter can be displayed in one or many windows, with a variety of modalities and rendering characterstics. Depending on ParaView's configuration that data can be generated rendered and displayed on different machines, in parallel, or it can be generated rendered and delivered within a single process. It will display multiple views locally or in a cave or on tile display walls. Run time data size checks determine if the data is rendered on the server and images are delivered to the client or if the data itself is rendered and delivered locally. During camera manipulation, the data and image may be downsampled to maintain interactivity or full resolution images may be generated. Finally the rendering architecture is extensible via plugins.
 
ParaView's display architecture is necessarily complex to support all of these requirements. We also periodically make improvements to it.
 
The architecture of ParaView's display for ParaView 2.x is explained in:
The ParaView user's guide version 1.8 Chapter 22.
 
 
The architecture of ParaView's display for ParaView 3.0-3.8 is diagrammed here:
 
[[Media:Pv_pipelines.pdf]]
 
 
The architecture of ParaView's display for ParaView 3.10 and beyond is diagrammed here:
 
[[Media:Pv_pipelines2.pdf]]

Revision as of 17:43, 20 December 2010

ParaView's display pipeline supports a large number of rendering modes and options. The output of every filter can be displayed in one or many windows, with a variety of modalities and rendering characterstics. Depending on ParaView's configuration that data can be generated rendered and displayed on different machines, in parallel, or it can be generated rendered and delivered within a single process. It will display multiple views locally or in a cave or on tile display walls. Run time data size checks determine if the data is rendered on the server and images are delivered to the client or if the data itself is rendered and delivered locally. During camera manipulation, the data and image may be downsampled to maintain interactivity or full resolution images may be generated. Finally the rendering architecture is extensible via plugins.

ParaView's display architecture is necessarily complex to support all of these requirements. We also periodically make improvements to it.


The architecture of ParaView's display for ParaView 2.x is explained in: The ParaView user's guide version 1.8 Chapter 22.


The architecture of ParaView's display for ParaView 3.0-3.8 is diagrammed here:

Media:Pv_pipelines.pdf


The architecture of ParaView's display for ParaView 3.10 and beyond is diagrammed here:

Media:Pv_pipelines2.pdf