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.6.2
- When VisIt's compute engine was built without support for offscreen software rendering it could crash when drawing plots if the DISPLAY environment variable was not set. The compute engine will now issue a warning message when it needs the DISPLAY environment variable set instead of crashing. This only affects VisIt builds that do not include Mesa.
- A threading error that surfaced when running PySide applications using -pysideviewer was removed from the Python interface. The threading error could cause the PySide application to lock up. This happened mostly on Windows.
- VisIt's frontendlauncher script was fixed so it can be launched from a symbolic link.
- A memory error was corrected in the Silo database reader that sometimes caused plots that involved materials to fail.
- Fixed the filter string for loading/saving Python expressions so that files matching the filter will be displayed.
- The Gadget reader was fixed such that opening a large number of files in a virtual database no longer fails on reopen.
- A bug was fixed that caused a viewer crash when logical coords were selected for output.
- Several problems were fixed with Nameschemes in Silo multi-block objects including using relative paths to reference external arrays.
- Several problems were fixed with build_visit when it was used to build Silo with Silo's Qt-dependenent Silex tool enabled.
- A bug was fixed so that -nopty is no longer required to run client/server from clients running on Red Hat Enterprise Linux 6 systems.
- Importing the VisIt Python module (import visit) in a system Python interpreter works again on UNIX-based platforms.
- The EnSight reader now handles files with trailing spaces in EnSight case files written from FORTAN codes.
- An unnecessary gradient calculation is no longer performed when using the Volume plot with raycasting integration.
- A crash was fixed in the Silo reader when reading a future format that supports packed local domain boundary info.
- Using the -sessionfile command line argument to restore session files could result in a race condition that caused other user settings to be applied after the session file was read, causing restored plots to be deleted.
- A bug was fixed with the UNIC file reader for doing CMFE operations.
Enhancements in version 2.6.2
- A Python interpreter is now installed with VisIt when VisIt is built with Python support.
- A number of changes were made to VisIt's frontendlauncher script in an attempt to resolve Python-related startup errors:
- The shell and Python portions of the script have been separated, which means that VisIt no longer needs to write temporary script files on startup.
- The shell portion of the script now attempts to locate a suitable Python interpreter within the current or most recent VisIt installations. If a suitable Python interpreter is located within VisIt's installations then that interpreter is used to execute VisIt's launch scripts. Otherwise, the system Python interpreter is used as before.
- The Python portion of the script checks the Python interpreter version and quits with an error message when Python 3 is detected.
- If the -X argument is given in the SSH arguments in a host profile, the -X argument will also be passed to the ssh command for gateway computers.
- The Silo reader now reads species names when avalaible in Silo multispecies and species objects. The specified names are added to the end of the species name string shown in VisIt's Subset window.
- The visit_utils module now includes a PySide based module (visit_utils.qannote) for rendering annotations on images.
- The serial paraDIS reader now decomposes higher energy arms into low energy type 111 arms before analyzing the network.
Changes for VisIt developers in version 2.6.2
- The paraDIS reader now requires boost 1.36.0 or later to build.
- The build_visit script now builds Silo 4.9.1. The reader will still work with Silo 4.9, but some of the bugs fixes mentioned above require Silo 4.9.1.