Development Branches

Main branches

master

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.

v2.1

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, ...).

v2.0

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.

uvcdat-*

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, listed below.

dat

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.

dont-use-modules-as-data

Tries to not pass Module subclasses on connections, and to not use 'self' as an output port.

See issue 804.

fixes-module-flags

vistrails_module:Module objects have a lot of flags (ran, had_error, computed, upToDate, suspended). issue 766 is about documenting and fixing them.

job-info

Work in progress, Extends support for running remote jobs.

• Save state to disk DONE
• Run from command line DONE

logger-rewrite

Right now the logger has special cases to detect modules that trigger a nested execution, such as Group, Map, and While. It then pushes these special module's execution to an interpreter-global stack, which is incompatible with multithreaded-interpreter.

This branches attempts to make this both more natural (and extensible), and compatible with multithreaded-interpreter.

See issue 774

madagascar

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

matplotlib-figure-creation

Attempt at fixing issue 685, which makes matplotlib incompatible with the multithreaded-interpreter work.

unicode

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.

multithreaded-interpreter

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.

multithreaded-interpreter-target-selection

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.

multithreaded-interpreter-responsive

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.

new-matplotlib-pkg

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.

optimize-vtk-startup

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

parameter-configuration-api

Improves the widgets API to allow module developers to choose custom widgets for the ports of their modules (see issue 699).

Currently, it is only possible to provide a widget for a type (all ports of that type will have that widget) or to do limited configuration with entry_type. This branch makes it more extensible.

persistent_archive

Work on a new package to replace persistence.

See issue 755 and the file_archive tool.

pyside-compatibility

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

python3

Python 3 port of VisTrails. Work in progress.

See issue 674.

rename-api

Renames some methods from CamelCaseNames to python_style_names.

resume-suspended-pipelines

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.

rewrite-startup

Rewrites the startup logic (configuration and command-line option parsing).

richtextcell-xml-xsl

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

See issue 292.

scripting-support

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

See issue 732

use-uuid

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

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.

To be deleted?

• tuple-fixes: merged (removes the Tuple type and accept tuples in TupleToList, issue 224)
• for-module: merged (adds a For module, issue 282)
• richtextcell-rtf-support: merged (adds RTF support in addition to HTML to RichTextCell, issue 789)
• remove-lockmethod: merged (removes the unused interpreter mutex, issue 791)
• remove-socket: merged (removes stall single-instance sockets, issue 793)
• feature-examples: rebased as e6cd0ecf (makes examples clickable in the users guide)
• testsuite-tempdir: merged (fixes theuse a different temporary and dotvistrails directories for the testsuite, issue 732)

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.

DAT

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 vgc.poly.edu:src/dat.git. The changes it requires on VisTrails have not been fully merged in and are in the dat branch.

file_archive

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.