Development Branches

From VistrailsWiki
Jump to navigation Jump to search

This page has been deprecated. We should now use pull requests on github to track branches. Everything still on this page should be moved to github.

Main branches


This is the development branch of VisTrails. It's where the features are merged for the next release and tested/bugfixed for a future public version.


This is the upcoming version, currently in beta. No more features should be added here, and once we think no more bug fixing is required, it will become the new stable version. Bug fixes will still happen on this branch, and would lead to the release of minor versions (2.1.1, 2.1.2, ...).


This is the current stable version. No more features are to be added here. We add there the occasional bugfix, but this should slow down once 2.1 is released.

The list of features that are not present in 2.0 is available on the page New features.


These branches are used by the UV-CDAT project. They were forked from VisTrails long ago (Feb. 2012) and there is not intention to merge back, although they live in the same repository.

Development branches

master itself is an integration branch and is not generally stable. However development of complex features happen in their own branches, based off master or a release branch, which are listed below.


This effort is about having Map work better with the cache and with ModuleSuspended/JobSubmission.

controlflow-fake-signatures builds fake signatures for the looped module in FoldWithModule. This still doesn't use the cache but makes these signatures unique. Merged into master.

jobs-use-signature uses the subpipeline signature as the job identifier. Checking for an existing job happens earlier, which allows a module with an already-submitted job to suspend again or finish without running its upstream at all (like persistence does once the file is cached). Merged into master.

jobs-use-signature_/connect-folded-module tries to make FoldWithModule build an actual runtime pipeline (a set of vistrails_module:Module and ModuleConnector objects, not vistrail.module:Module and Connection).

Next thing to try: make FoldWithModule instanciate a full-fledged pipeline an pass it through the interpreter (like what Group does, except that pipeline would be dynamically generated, and executed several times). There are issues here with logging, since we want to have a LoopExec with the global module IDs in the log, not a WorkflowExec and different (from the dynamic pipeline generation) module IDs.


Work on exporting and importing workflows as Python scripts (using RedBaron)


This branch has changes needed by the DAT tool, and that generally makes VisTrails more customizable and useful when used as a library. These changes are intended to be merged back in the main line of development someday.


Work in progress on modifying the vt bundle structure to be extensible. Adds serializer objects to facilitate the serialization of specific pieces of the bundle.


Port of the java packages from the 'java' branch. Work in progress.


Alternative method to create a Mac OS X app bundle for VisTrails. Doesn't use py2app, builds Python as a framework, installs required packages and relinks Qt and vtk using install_name_tool.

TODO: move from shell script to Makefile or Python, make relinking more automatic.


Contains a package wrapping madagascar. Basic modules are working but more work is needed.


Improvements to both the matplotlib package and a start at a general framework for semi-automated package generation.


This changes the interpreter part of VisTrails to use a task system instead of relying on each module running its upstream counterparts recursively. It allows the use of multithreading at the module level (i.e. running different modules in parallel) and provides this via different schemes. The branch has schemes for threading and multiprocessing (through concurrent.futures) as well as IPython (which replaces the ParallelFlow package).

This is a legacy branch that is still relevant and functional, but is superseeded by multithreaded-interpreter-target-selection which provides more options.

More information is available on its specific page: multithreaded-interpreter.


It's a variant of the previous branch that changes the way schemes work. There can be different instances of each scheme (named targets), configured by the user, and each module can be assigned to a specific target, allowing fine-grained control of where each module should execute.

It also revamps the XML log and adds an XML configuration file for remote execution.


This brings in background-interpreter, except that it works. The interpreter runs in a different thread, although modules that don't use the @parallelizable decorator will be run synchronously on the UI thread (thus blocking the UI for a time).

See issue 701.

It is probably required for further work in stopping/resuming workflows, but is a bit complex.


Rewrites vistrails.core.api as a nice, pythonic, user-friendly API for VisTrails, abstracting away internals.


New 'matplotlib' package, that replaces 'pylab'. Has been merged in v2.1 and released. The branch is still used by Sunitha Menon who is making more examples.


Profiles and tries to shorten the loading time of the VTK package.


Work to make it possible to track the order of connections. This would allow a ConcatenateStrings module to have a single port that took multiple connections and have the ordering be well-defined and modifiable.


Enables VisTrails to load packages from different Python packages, through the setuptools entry_points mechanism. This would allow to distribute packages outside of VisTrails easily.


Work on a new package to replace persistence.

See issue 755 and the file_archive tool.


This branch aims at making VisTrails compatible with both PyQt4 and PySide. PySide currently crashes.


Python 3 support. This branch is archaic (used 2to3) but contain useful information. See issue 674.

Proper compatibility will have to wait for unicode to be supported, and __future__ imports to be in place.


Adds __future__ imports to work towards Python 3 compatibility. Adds the script to automatically enable these imports.


Tries to make VisTrails unicode-safe. This means eliminating bytestrings from the code where unicode strings were meant (PyQt4 already uses unicode). Work in progress.

See issue 673.


Adds a button to stretch the spreadsheet cells. Intended as a fix for 2.1 until the resizing code is fixed.

Currently missing an icon.

See issue 833.


Changes the interpreter to not clean not-cacheable modules from the persisted pipeline if the execution was suspended. This means that the next execution will resume close to where the last one stopped.

Obviously doesn't work across sessions.


Adds an XSLCell module that shows a XML document formatted via an XSLT stylesheet.

See issue 292.


Work attempting to make it possible to convert from scripts to workflows and vice versa. Based off rename-api.

See issue 732


Work to move to the database layer to something more abstract that can support multiple relational backends instead of being coded for mysql or another system.


Use UUIDs for identifiers instead of incrementing integers. This would make things like merging vistrails or dealing with distributed versions of the same vistrail much easier (e.g. crowdLabs, subworkflows).

See ticket 355


Adds back the --version flag which disappeared with the rewrite-startup effort.

Unknown branches (fixme?)

easy-install (2012-11-21)

Emanuele's branch trying to get easy-install to work on both user/system installations. We have now moved to using "pip" but some of this may still be relevant.

fernando (2010-03-28)

matplotlib-add-helpers (2014-01-28)




v2.0-with-layout (2012-08-22)

To be deleted?

(cleaned 2014-09-78)

Related projects

These are projects part of the VisTrails effort that we are working on, but that are not technically a part of the VisTrails repository.


The Data Analysis Tool is inspired by UV-CDAT. It has a similar interface meant to create visualizations from Plots and Variables connected together by drag and drop, generating the VisTrails workflows on-the-fly. It lives in The changes it requires on VisTrails have not been fully merged in and are in the dat branch.


This is a file store with metadata that is meant to replace Git as the backend of the persistence package. It is developed as a stand-alone tool and library, allowing to search for and get files that were generated from VisTrails without having to go through its UI. An initial design document is on the Archive page.

See the Github project, issue 755 and branch persistent_archive.