ParaView Catalyst User’s Guide
Figure 2.4: ParaView GUI pipeline for live connection.
simulation run state to signify the status of the simulation. The icons for this are:
• indicates the simulation is running with no breakpoint set.
• indicates that the simulation has reached a breakpoint.
• indicates that a breakpoint has been set but not yet reached.
A demonstration of this functionality is at www.kitware.com/blog/home/post/722.
2.4 Cinema
Cinema is an image-based approach to in situ analysis and visualization. The concept is that by saving an organized set
of images into a Cinema database, an analyst can perform post hoc analysis and visualization directly from the generated
images. ParaView Catalyst can be used to create a Cinema database and the specification of the Cinema output can be done
through the ParaView GUI’s Catalyst Script Generator. Figure 2.5 shows the expanded options when Output to Cinema is
enabled. These options are:
• Export Type – This option specifies how the view’s camera should be manipulated when generating the images.
Current options include None, Static and Spherical. None indicates that no Cinema output is requested for this view
and Static indicates that the camera need not be moved. Spherical will rotate the camera around the view’s center at
the given Phi and Theta angles.
• Cinema Track Selection – This option allows changing filter parameters and what field data to pseudo-color with.
By selecting the pipeline object in the left pane, users can specify the arrays to pseudo-color by in the right pane’s
Arrays tab or the filter’s parameters in the right pane’s Filter Values tab. Note that currently only Slice, Contour and
Cut filters have been enabled for modifying filter values.
See www.cinemascience.org or Ahrens, et. al.
[1]
for detailed information on Cinema.
2.5 Avoiding Data Explosion
A key point to keep in mind when creating Catalyst pipelines is that the choice and order of filters can make a dramatic
difference in the performance of Catalyst (this is true with ParaView as well). Often, the source of performance degradation
is when dealing with very large amounts of data. For memory-limited machines like today’s supercomputers, poor decisions
when creating a pipeline can cause the executable to crash due to insufficient memory. The worst case scenario is creating
11