Release Notes for VisIt 2.8.1

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

Bugs fixed in version 2.8.1

  • Eliminated a problem-sized memory leak introduced in VisIt 2.8 that affected many of VisIt's filters.
  • Corrected a bug with Python callbacks failing for viewer RPC's with no arguments.
  • Corrected a bug with the multipass CSG discretization method where it created incorrect results in regions where one or more boundaries was referenced multiple times and the total number of boundaries in the mesh was greater than 512.
  • Corrected a bug where Pick, Query and the Onion Peel operator would return inconsistent results when using the same zone or node ids, when the database supplied ghost zones.
  • Mesh plots of arbitrary polyhedra now display properly when the Onion Peel operator has been applied.
  • NumZones and NumNodes queries now return the correct count for arbitary polyhedral data when using the original data.
  • The VisIt GUI no longer crashes when opening the Preferences window.

Enhancements in version 2.8.1

  • Several enhancements were made to the BOUT reader. These include:
    • The ability to read variables containing ghost zones.
    • Being more tolerant of data type variations in the files, such as allowing a "short", "int" or "long" for scalar integer values.
    • Adding more error checks for bad values.
  • Upgraded to Silo version 4.10.1
  • VisIt now uses the same version for all components when the user specifies a version number with a minor version number. For example, if the user specifies "visit -v 2.7.1" it will use version 2.7.1 for all the components. If the user specifies a version number without a minor version number then it will behave as before and launch the latest version in that series.

Changes for VisIt developers in version 2.8.1

  • The build_visit script was modified so that it will use the equivalent of --svn-anon in the absence of any svn related flags when using the trunk version of build_visit. This will avoid the situation of using a specific visit release of the source code with the trunk version of build_visit, which may not be compatible with any releases.

For any additional questions, send e-mail to visit-users [at] (VisIt Users).