Check this page for known issues with VisTrails Releases and how to work around them.
The VisTrails development team is refactoring the implementation of many of the command-line switches supported by VisTrails. Please refer to the table below for a summary of which switches work and which ones don't, and their status.
|Short form||Long form||Description|
|-h||--help||Print a help message and exit.|
|-S /path||--startup=/path||Set user configuration directory (default is ~/.vistrails).
NOT WORKING. See ticket #213.
|-?||Print a help message and exit.|
|-v||--version||Print version information and exit.|
|-V num||--verbose=num||Set verboseness level (0–2, default=0,
higher means more verbose).
NOT WORKING. I cannot tell whether this option makes any difference.
|-b||--noninteractive||Run in non-interactive (batch) mode.|
|-n||--nosplash||Do not display splash screen on startup.
NOT WORKING. It's a one-line code fix, but I'm waiting for my Qt license before I check it in.
|-c num||--cache=num||Enable/disable caching (0 to disable,
nonzero to enable. Default is enabled).
UNTESTED. Not sure how to verify this.
|-m num||--movies=num||Set automatic movie creation on spreadsheet
(0 or 1, default=1). Set this to zero to work around VTK bug with offscreen renderer and OpenGL texture3D mappers.
UNTESTED. Actually, I'm not completely sure what this is supposed to do.
|-s||--multiheads||Display the Builder and Spreadsheet on
different screens (if available).
NOT WORKING. See Ticket #211.
|-x||--maximized||Maximize Builder and Spreadsheet windows at startup.
NOT WORKING. See Ticket #211.
NOT WORKING. This is a weird one. I've experimented a bit with the code, but cannot get the logging flag to behave predictably.
|-d||--debugsignals||Debug Qt signals.
NOT WORKING. As far as I can tell, this option is never exercised in the code.
|-a params||--parameters=params||Set workflow parameters (non-interactive mode only).
WORKING, BUT this option depends on the ability to create parameter aliases, and I'm not sure whether aliases are a feature we want to support in the long term.
|-t host||--host=host||Set hostname or IP address of database server.|
|-r port||--port=port||Set database port.|
|-f dbName||--db=dbName||Set database name.|
|-u userName||--user=userName||Set database username.
NOT SURE if this works as advertised. Sometimes the username is not automatically populated in the Open Database Connection dialog, while the other fields are.
On Linux machines using PyQt4.2, there is a bug that causes vtk pipelines not to show on the spreadsheet.
Solution: edit the file
in the import section (around line 27), add
replace line 244:
vp = '_%s_void_p' % (hex(int(QtGui.QX11Info.display()))[2:])
try: vp = '_%s_void_p' % (hex(int(QtGui.QX11Info.display()))[2:]) except TypeError: #This was changed for PyQT4.2 if isinstance(QtGui.QX11Info.display(),QtGui.Display): display = sip.unwrapinstance(QtGui.QX11Info.display()) vp = '_%s_void_p' % (hex(display)[2:])
There are two issues with the binary version of this release.
1. When the current directory is not on the PATH. This causes VisTrails to raise a Requirements not fulfilled exception.
Solution: Adding '.' or
path_to_vistrails_install/vistrails to the PATH solves this problem.
2. When installing on a non-english system or on a custom directory, VisTrails won't start. This is due to absolute paths inside the bookmarks file.
Solution: Remove file
~/.vistrails folder. On Windows XP it's located on
C:\Documents and Settings\your_username\.vistrails. On Windows Vista, it's located at