Welcome to VisIt's release notes page. This page describes the important enhancements and bug-fixes that were added to this release.
Images can consist of RGB pixel images and composite images that enable VisIt to bring together multiple plots independently in the Cinema viewer. Cinema databases can be created using the Save Cinema wizard, accessible by selecting Save to Cinema... from the File pulldown menu on the main control panel.
To enable OSPRay rendering bring up the Rendering options window by selecting Rendering... from the Options pulldown menu, switch to the Advanced tab and select OSPRay rendering at the bottom of the tab. All plots except for the Volume will use OSPRay for 3D rendering when enabled through the Rendering options. OSPRay rendering for the Volume plot is enabled through the Volume plot attributes window by setting the Rendering Method to Ray casting: OSPRay.
Note that panning and zooming doesn't currently work with OSPRay rendering.
When using the graphical user interface, bring up the Preferences window by selecting Preferences... from the Options menu and change the Parallel Computation Library: to VTKm. This setting will be directly below the Floating point precision: setting and will only be visible if VisIt has been built with VTK-m support.
When using the Python scripting interface, make the following call:
When VTK-m support is enabled, VisIt will use VTK-m for all operations that support it. The following operators currently support VTK-m.
VTK-m functionality is currently enabled for 3D rectilinear, curvilinear and unstructured grids with only hexahedral elements. VTK-m supports both single block and multi-block grids.
In order for VTK-m filters to perform better than VTK filters the number of cells in a block must be fairly large, typically at least 1 million cells. Furthermore, there is some overhead in converting between VTK and VTK-m representations that will impact performance. Lastly, checks have been put in to make sure that the data sets being processed are supported by VTK-m and these can impact performance as well. Checking if a variable is node centered or 3D is inexpensive, whereas checking if an unstructured grid contains only hexahedra is expensive.
For any additional questions, send e-mail to VisIt Users.