The new available version of VisTrails is v2.0.2, a bugfix release for VisTrails 2.0. For the the complete list of enhancements and fixes in this release, please see the release notes.
Source, Binaries and Users' Guide
|2.0.3 build a6ad79347667 (2013-08-05) Known Issues View Notes|
|120.5 MB||i586||.zip (32-bit Windows)|
|166.0 MB||i586||.zip (64-bit Windows)|
|242.4 MB||Mac OS X 10.6+ x64||.dmg (Mac bundle)|
|20.7 MB||all||Source .tar.gz|
|1.7 build 51517a6cdab6 (2011-06-30) Known Issues View Notes|
|111.9 MB||i586||.zip (32-bit Windows)|
|211.5 MB||Mac OS X 10.5+ x86||.dmg (Mac bundle)|
|19 MB||all||Source .tar.gz|
Every night a tarball with the source trunk of vistrails is generated. Beware that this version can be very unstable.
|18 MB||all||Source .tar.gz|
Data files for Examples
If you download the source release you might want to download the data files (they are already included in the binary releases). Just decompress the package to the examples folder.
Building from Source
Instructions are available for building VisTrails from source for all supported platforms.
Sam Preston wrote us warning that there may be issues with the current BLAS, LAPACK and numpy rpms available through YaST on SuSE 10.2:
I have run into another problem not directly related to VisTrails, though. I installed blas, lapack, and numpy from Yast in OpenSUSE 10.2, and got some errors when trying to build scipy. After looking at a couple of discussions, it seems that these packages are broken in 10.2:
VisTrails includes integrated support for checking and installing required packages on Ubuntu. See installing VisTrails on Ubuntu for more information.
VisTrails Module Packages
VisTrails makes use of packages of Modules to define and form valid workflows. Some packages are maintained and distributed with the VisTrails itself and are considered part of the core functionality. However, work has also been done on developing user-made and maintained Module Packages. Below are a current list of packages maintained by VisTrails and user packages maintained outside the core source repository. The Package Name field describes the name required by the addPackage() directive in the .vistrails/startup.py file required to load the package.
Web Services Demos
Some Bioinformatics workflows examples are available here.
Join the VisTrails mailing list to receive release announcements as well as post questions.