VisTrails Home


From VisTrailsWiki

(Difference between revisions)
Jump to: navigation, search
m (Added afront to base package list)
Line 102: Line 102:
| Modules to run some of [ Afront]'s functionality.
| Modules to run some of [ Afront]'s functionality.
| afront
| afront
* pylab
| Provides plotting functionality through [ pylab and matplotlib].
| pylab

Revision as of 17:44, 12 March 2007


Latest Release

Revision 502 (2007-03-09 16:00) Documents2.png View Notes Size Architecture Type
62571080 i586 .zip (32-bit Windows)
941311 all Source .tar.gz
  • If you have problems downloading from our repository, we keep mirror copies at sourceforge VisTrails@SourceForge.

See all releases

Mailing Lists

Information on joining mailing lists is available here.

Experimental Ubuntu Packages

Carlos Scheidegger is experimenting with Ubuntu (debian) packages and is currently making them available at They can be installed in Ubuntu with

sudo dpkg -i vistrails-<version>.deb

These will install VisTrails on /usr/local. They currently perform no dependency checking, though this will be done in the future, together with a VisTrails apt repository. Please check back often or email him at


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/ file required to load the package.

Core Packages as of Mar. 12 2007 Description Package Name
  • Basic Modules
Basic module types. These modules consist of value placeholders (Float, Integer, etc) and general workflow manipulation (stdout, File Writing, etc) Automatically Included
  • VTK
Kitware's Visualization ToolKit wrapped for use in VisTrails vtk
  • Spreadsheet
Spreadsheet modules for use in visualization workflows. spreadsheet
  • HTTP
Modules capable of accessing files via HTTP and using them as if they were locally stored. HTTP
  • Python Calculator
A basic set of modules intended to demonstrate how to create new packages for use in VisTrails pythonCalc
  • SciPy
Modules wrapping some of the functionality provided by the Scientific Python package. As this package is large, it is not yet fully wrapped. SciPy
  • Image Magick
Modules utilizing the Image Magick command-line tools. ImageMagick
  • Web Services
Modules capable of taking advantage of existing web services used outside the VisTrails environment webServices
  • afront
Modules to run some of Afront's functionality. afront
  • pylab
Provides plotting functionality through pylab and matplotlib. pylab

Please note that the packages below are created and maintained outside of the VisTrails repository. Installation of them requires extracting them to the appropriate userpackages directory. Many of the packages listed below are incomplete or works in progress. Please take that into consideration during their use.

User Packages Description Package Name Primary Contact Download
  • Protein Data Bank
Package allowing simple processing of Protein Databank files (.pdb) to extract mundane statistics ProteinDataBank Erik Anderson - eranders 'at'
  • ITK
Wrapping of the Insight ToolKit available from KitWare. This is an incomplete set of packages and work is being done to incorporate more of the ITK functionality into the wrappers. DICOM reading is now supported through ITK's GDCMReader module set. This requires CableSWIG and WrapITK. itk Erik Anderson - eranders 'at'
  • Matlab
Modules allowing access to a local Matlab engine and interpreter. This is an incomplete set of packages and work is being done to incorporate more functionality into the wrappers. This requires Matlab and MLabWrap. Matlab Erik Anderson - eranders 'at'
  • Trimesh2
Modules allowing access to the trimesh2 library. It requires access to the trimesh2 executables (notably, mesh_filter). trimesh2 Carlos Scheidegger - cscheid 'at'
Personal tools