VisIt 1.3.3 Release Notes

Welcome to VisIt's release notes page. This page describes the important enhancements and bug-fixes that were added to this release.

Features added in version 1.3.3

- VisIt can now pick on slices of Boundary plots.
- VisIt's Slice operator now uses interval trees when slicing by a percent so it is much faster for large multi-domain databases.
- VisIt now supports ghost nodes, which allow for geometry for adjacent internal domains to be removed from the visualization without costly parallel communication. The Exodus database reader plugin supports ghost nodes.
- VisIt's BoxLib database reader plugins are now more tolerant of errors in data files.
- VisIt's configure script now builds VisIt optimized by default if no CXXFLAGS are specified.
- The file selection filter in the File Selection Window is now global to all hosts.
- The Vector plot's vectors are now positioned at the tail by default.
- VisIt's Mili database reader plugin now reports materials as beginning at index 1.
- VisIt now supports quads that were stored as degenerate hexes.
- The Boundary and FilledBoundary plots no longer will plot domain subsets since they are primarily for plotting materials.
- The "screen capture" toggle button is disabled in the Set Save Options window when the output format is for polygonal geometry.
- VisIt's FAQ has been updated to include a table of all of VisIt's supported database plugins along with the platforms and specific computers where each is built by default.

Bugs fixed in version 1.3.3

- Plots disappear when parallel, remote compute engines die in scalable rendering mode.
- VisIt can get into a bad state in scalable rendering mode where plots disappear and cannot be recovered.
- VisIt issues an error message when you turn off the "Clean zones only" toggle in the FilledBoundary plot after having used that toggle once.
- Some help files are not distributed in the binary UNIX versions of VisIt due to a flaw in the visit-bin-dist script.
- VisIt's parallel compute engine does not build on riptide.
- Opening monochrome images with VisIt is slow.
- Multi-part EnSight data files crash VisIt's compute engine.
- VisIt displayed the "plot yielded no data" warning message when it should not have done so.
- VisIt's automatic mesh scaling has been disabled.
- Reediting an uncompleted host profile causes a crash.
- The vector plot always colors by the local maximum.
- Slicing by a zone does not work when slicing a Boundary plot.
- Time queries sometimes cause VisIt to issue warning messages when used with expressions.
- Scaled databases sometimes result in an invisible plot.
- VisIt's Ensight database reader plugin does not correctly parse some case files.
- Performing a query over time can cause the parallel compute engine to fail when processing data from the Mili database reader plugin.
- A Mesh plot of rotated 2D data causes the compute engine to crash.
- Contour plots look very bad if materials have been removed because of interpolation of internal nodal data that should never be interpolated.
- The last time state of certain Mili files is not valid.
- The MinMax query gives results over deleted values.
- Vectors seemed to be colored by a processor's maximum value when in scalable rendering mode.
- Material selecting a variable leaves zeros in the ghost zones.
- Material selection may not create zones for all materials in a zone.
- Using the IsoSurface operator with multiple variables causes VisIt to become confused about the variable extents.
- Software volume rendering fails in parallel when the number of domains is less than the number of processors.
- VisIt's new clipping code does not handle unstructured voxels.
- Mili files should use "processor" instead of "domain" in the SIL.
- The Reflect operator does not handle vector data well.
- The metadata server should be switched back to using the lightweight VTK libraries.
- The Vista database reader plugin should not be required.
- The compute engine crashes when reopening STL files.
- VisIt's xml2java program does not generate correct code for enum constants defined in an XML file.
- The ImageFileFormat database reader plugin won't load in the mdserver without the heavyweight VTK libraries.
- The Time curve for the Variable Sum query of the matvf expression is wrong.
- The Displace operator is incorrectly issuing a warning message.
- Mysterious lines appear when the IsoSurface operator is applied to a Boundary plot.
- VisIt's launch script should have /usr/local/lib in the LD_LIBRARY_PATH to avoid strange launch problems on some Solaris computers..
- Some plugin source code files are compiled too many times.
- Slicing by percent after rotating a 2D plot into 3D does not work.
- The lib directory's Makefile contains links for Mili and HDF5 on MacOS X even when those libraries are not used.

Click the following link to view the release notes for the previous version of VisIt: VisIt 1.3.2 Release Notes.

Click the following link to view the release notes for the next version of VisIt: VisIt 1.3.4 Release Notes.