VistrailsWiki - User contributions [en]

Main Page

2008-08-08T16:54:02Z

Draperg: /* Looking for the Maya® plugin? */

* [[#VisTrails Overview|VisTrails Overview]]
* [[downloads|Download]]
* [[Documentation]]
** [[Documentation#Screen Shots|Screen Shots]]
** [[Users_Guide|User's Guide]]
** [[FAQ]]
* [[MailingLists|Mailing Lists]]
* [[Publications and Presentations]]
* [[People]]
* [[#Sponsors|Sponsors]]

== VisTrails Overview ==

Recently, workflows have been emerging as a paradigm for representing and managing complex
computations. Workflows can capture complex analyses processes at various levels of detail and
provide the provenance information necessary for reproducibility, result publication and result
sharing among collaborators. Because of the formalism they provide and the automation they
support, workflows have the potential to accelerate and transform the information analysis
process. Workflows are rapidly replacing primitive shell scripts as evidenced by the release of
Apple’s Mac OS X Automator, Microsoft Windows Workflow Foundation, and the SGI
Scientific Workflow Solution.

[[Image:Mesh_example.png|512px|right]]
VisTrails is a new scientific workflow management system developed at the University of Utah that
provides support for data exploration and visualization. Whereas workflows have been
traditionally used to automate repetitive tasks, for applications that are exploratory in nature, very
little is repeated---change is the norm. As an engineer or scientist generates and evaluates
hypotheses about data under study, a series of different, albeit related, workflows are created
while a workflow is adjusted in an interactive process. VisTrails was designed to manage these
rapidly-evolving workflows. VisTrails streamlines the creation, execution and sharing of complex
visualizations, data mining or other large-scale data analysis applications. By automatically
managing the data, metadata, and the data exploration process, VisTrails allows users to focus on
the task at hand and relieves them from tedious and time-consuming tasks involved in organizing
the vast volumes of data they manipulate. VisTrails provides infrastructure that can be combined
with and enhance existing visualization and workflow systems.

Although VisTrails was originally built to address the needs of exploratory scientific applications,
the infrastructure it provides is very general. This became clear as the system was demoed to
people from different domains, both from industry and academia. VisTrails has the potential to
reduce the time to insight in virtually any exploratory task.

== Sponsors ==

This work has been partially supported by the National Science Foundation under grants
[http://www.nsf.gov/awardsearch/showAward.do?AwardNumber=0513692 IIS-0513692],
[http://www.nsf.gov/awardsearch/showAward.do?AwardNumber=0401498 CCF-0401498],
[http://www.nsf.gov/awardsearch/showAward.do?AwardNumber=0541560 CNS-0541560], [http://www.nsf.gov/awardsearch/showAward.do?AwardNumber=0405402 OISE-0405402],
[http://www.nsf.gov/awardsearch/showAward.do?AwardNumber=0424602 OCE-0424602],
[http://www.nsf.gov/awardsearch/showAward.do?AwardNumber=0524096 CNS-0524096],
[http://www.nsf.gov/awardsearch/showAward.do?AwardNumber=0534628 IIS-0534628],
the Department of Energy under the SciDAC program
([http://www.scidac.org/compsci/SDM.html SDM]
and
[http://www.scidac.org/viz/VACET.html VACET]),
IBM Faculty Awards (2005 and 2006) and a University of Utah Seed Grant.

== Looking for the Maya® plugin? ==
'''NOTE:''' This website is about the open source edition of VisTrails for scientific visualization. For information about the commercial plugin for Maya®, please see the [http://www.vistrails.com VisTrails, Inc.] website.

Main Page

2008-08-08T16:51:28Z

Draperg: Added a link to the VisTrails Inc website.

* [[#VisTrails Overview|VisTrails Overview]]
* [[downloads|Download]]
* [[Documentation]]
** [[Documentation#Screen Shots|Screen Shots]]
** [[Users_Guide|User's Guide]]
** [[FAQ]]
* [[MailingLists|Mailing Lists]]
* [[Publications and Presentations]]
* [[People]]
* [[#Sponsors|Sponsors]]

== VisTrails Overview ==

Recently, workflows have been emerging as a paradigm for representing and managing complex
computations. Workflows can capture complex analyses processes at various levels of detail and
provide the provenance information necessary for reproducibility, result publication and result
sharing among collaborators. Because of the formalism they provide and the automation they
support, workflows have the potential to accelerate and transform the information analysis
process. Workflows are rapidly replacing primitive shell scripts as evidenced by the release of
Apple’s Mac OS X Automator, Microsoft Windows Workflow Foundation, and the SGI
Scientific Workflow Solution.

[[Image:Mesh_example.png|512px|right]]
VisTrails is a new scientific workflow management system developed at the University of Utah that
provides support for data exploration and visualization. Whereas workflows have been
traditionally used to automate repetitive tasks, for applications that are exploratory in nature, very
little is repeated---change is the norm. As an engineer or scientist generates and evaluates
hypotheses about data under study, a series of different, albeit related, workflows are created
while a workflow is adjusted in an interactive process. VisTrails was designed to manage these
rapidly-evolving workflows. VisTrails streamlines the creation, execution and sharing of complex
visualizations, data mining or other large-scale data analysis applications. By automatically
managing the data, metadata, and the data exploration process, VisTrails allows users to focus on
the task at hand and relieves them from tedious and time-consuming tasks involved in organizing
the vast volumes of data they manipulate. VisTrails provides infrastructure that can be combined
with and enhance existing visualization and workflow systems.

Although VisTrails was originally built to address the needs of exploratory scientific applications,
the infrastructure it provides is very general. This became clear as the system was demoed to
people from different domains, both from industry and academia. VisTrails has the potential to
reduce the time to insight in virtually any exploratory task.

== Sponsors ==

This work has been partially supported by the National Science Foundation under grants
[http://www.nsf.gov/awardsearch/showAward.do?AwardNumber=0513692 IIS-0513692],
[http://www.nsf.gov/awardsearch/showAward.do?AwardNumber=0401498 CCF-0401498],
[http://www.nsf.gov/awardsearch/showAward.do?AwardNumber=0541560 CNS-0541560], [http://www.nsf.gov/awardsearch/showAward.do?AwardNumber=0405402 OISE-0405402],
[http://www.nsf.gov/awardsearch/showAward.do?AwardNumber=0424602 OCE-0424602],
[http://www.nsf.gov/awardsearch/showAward.do?AwardNumber=0524096 CNS-0524096],
[http://www.nsf.gov/awardsearch/showAward.do?AwardNumber=0534628 IIS-0534628],
the Department of Energy under the SciDAC program
([http://www.scidac.org/compsci/SDM.html SDM]
and
[http://www.scidac.org/viz/VACET.html VACET]),
IBM Faculty Awards (2005 and 2006) and a University of Utah Seed Grant.

== Looking for the Maya® plugin? ==
'''NOTE:''' This website is about the open source edition of VisTrails for scientific visualization. For information about the commercial plugin for Maya®, see the [http://www.vistrails.com VisTrails, Inc.] website.

Known issues

2008-07-17T18:28:35Z

Draperg: /* Command-Line Switches */ Removing "not working" message for -s and -x switches, per resolution of ticket 211.

Check this page for known issues with VisTrails Releases and how to work around them.

==Command-Line Switches==
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.

<table border=1>
<tr>
<th>Short form</th><th>Long form</th><th>Description</th>
</tr>
<tr>
<td>-h</td><td>--help</td><td>Print a help message and exit.</td>
</tr>
<tr>
<td>-S ''/path''</td><td>--startup=''/path''</td><td>Set user configuration directory (default is ~/.vistrails). '''NOT WORKING'''. See ticket #213.</td>
</tr>
<tr>
<td>-?</td><td> </td><td>Print a help message and exit.</td>
</tr>
<tr>
<td>-v</td><td>--version</td><td>Print version information and exit.</td>
</tr>
<tr>
<td>-V ''num''</td><td>--verbose=''num''</td><td>Set verboseness level (0–2, default=0,
higher means more verbose). '''MORE TESTING NEEDED.''' I haven't yet found a use case where this makes a difference.</td>
</tr>
<tr>
<td>-b</td><td>--noninteractive</td><td>Run in non-interactive (batch) mode.</td>
</tr>
<tr>
<td>-n</td><td>--nosplash</td><td>Do not display splash screen on startup.</td>
</tr>
<tr>
<td>-c ''num''</td><td>--cache=''num''</td><td>Enable/disable caching (0 to disable,
nonzero to enable. Default is enabled).</td>
</tr>
<tr>
<td>-m ''num''</td><td>--movies=''num''</td><td>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. This switch is more for the Spreadsheet than for VisTrails proper, but we'll keep it for now.</td>
</tr>
<tr>
<td>-s</td><td>--multiheads</td><td>Display the Builder and Spreadsheet on
different screens (if available).</td>
</tr>
<tr>
<td>-x</td><td>--maximized</td><td>Maximize Builder and Spreadsheet windows at startup.</td>
</tr>
<tr>
<td>-l</td><td>--nologger</td><td>Disable logging. '''NOT WORKING.''' Known issues.</td>
</tr>
<tr>
<td>-d</td><td>--debugsignals</td><td>Debug Qt signals. '''NOT USED.''' To be removed.</td>
</tr>
<tr>
<td>-a ''params''</td><td>--parameters=''params''</td><td>Set workflow parameters (non-interactive mode only). '''WORKING, BUT''' this option will eventually be superseded by the Medley functionality.</td>
</tr>
<tr>
<td>-t ''host''</td><td>--host=''host''</td><td>Set hostname or IP address of database
server.</td>
</tr>
<tr>
<td>-r ''port''</td><td>--port=''port''</td><td>Set database port.</td>
</tr>
<tr>
<td>-f ''dbName''</td><td>--db=''dbName''</td><td>Set database name.</td>
</tr>
<tr>
<td>-u ''userName''</td><td>--user=''userName''</td><td>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.</td>
</tr>
</table>

==Rev 674==
On Linux machines using PyQt4.2, there is a bug that causes vtk pipelines not to show on the spreadsheet.
Solution: edit the file <code>path_to_vistrails_src/vistrails/packages/vtk/vtkcell.py</code>

in the import section (around line 27), add
import sip
replace line 244:
vp = '_%s_void_p' % (hex(int(QtGui.QX11Info.display()))[2:])

by
<code>
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:])
</code>

==Rev 559==
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 <code>path_to_vistrails_install/vistrails</code> 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 <code>bookmarks.xml</code> inside <code>~/.vistrails</code> folder. On Windows XP it's located on <code>C:\Documents and Settings\your_username\.vistrails</code>. On Windows Vista, it's located at <code>C:\Users\your_username\.vistrails</code>.

Known issues

2008-07-01T15:41:37Z

Draperg: /* Command-Line Switches */

Check this page for known issues with VisTrails Releases and how to work around them.

==Command-Line Switches==
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.

<table border=1>
<tr>
<th>Short form</th><th>Long form</th><th>Description</th>
</tr>
<tr>
<td>-h</td><td>--help</td><td>Print a help message and exit.</td>
</tr>
<tr>
<td>-S ''/path''</td><td>--startup=''/path''</td><td>Set user configuration directory (default is ~/.vistrails). '''NOT WORKING'''. See ticket #213.</td>
</tr>
<tr>
<td>-?</td><td> </td><td>Print a help message and exit.</td>
</tr>
<tr>
<td>-v</td><td>--version</td><td>Print version information and exit.</td>
</tr>
<tr>
<td>-V ''num''</td><td>--verbose=''num''</td><td>Set verboseness level (0–2, default=0,
higher means more verbose). '''MORE TESTING NEEDED.''' I haven't yet found a use case where this makes a difference.</td>
</tr>
<tr>
<td>-b</td><td>--noninteractive</td><td>Run in non-interactive (batch) mode.</td>
</tr>
<tr>
<td>-n</td><td>--nosplash</td><td>Do not display splash screen on startup.</td>
</tr>
<tr>
<td>-c ''num''</td><td>--cache=''num''</td><td>Enable/disable caching (0 to disable,
nonzero to enable. Default is enabled).</td>
</tr>
<tr>
<td>-m ''num''</td><td>--movies=''num''</td><td>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. This switch is more for the Spreadsheet than for VisTrails proper, but we'll keep it for now.</td>
</tr>
<tr>
<td>-s</td><td>--multiheads</td><td>Display the Builder and Spreadsheet on
different screens (if available). '''NOT WORKING.''' See Ticket #211.</td>
</tr>
<tr>
<td>-x</td><td>--maximized</td><td>Maximize Builder and Spreadsheet windows at startup. '''NOT WORKING.''' See Ticket #211.</td>
</tr>
<tr>
<td>-l</td><td>--nologger</td><td>Disable logging. '''NOT WORKING.''' Known issues.</td>
</tr>
<tr>
<td>-d</td><td>--debugsignals</td><td>Debug Qt signals. '''NOT USED.''' To be removed.</td>
</tr>
<tr>
<td>-a ''params''</td><td>--parameters=''params''</td><td>Set workflow parameters (non-interactive mode only). '''WORKING, BUT''' this option will eventually be superseded by the Medley functionality.</td>
</tr>
<tr>
<td>-t ''host''</td><td>--host=''host''</td><td>Set hostname or IP address of database
server.</td>
</tr>
<tr>
<td>-r ''port''</td><td>--port=''port''</td><td>Set database port.</td>
</tr>
<tr>
<td>-f ''dbName''</td><td>--db=''dbName''</td><td>Set database name.</td>
</tr>
<tr>
<td>-u ''userName''</td><td>--user=''userName''</td><td>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.</td>
</tr>
</table>

==Rev 674==
On Linux machines using PyQt4.2, there is a bug that causes vtk pipelines not to show on the spreadsheet.
Solution: edit the file <code>path_to_vistrails_src/vistrails/packages/vtk/vtkcell.py</code>

in the import section (around line 27), add
import sip
replace line 244:
vp = '_%s_void_p' % (hex(int(QtGui.QX11Info.display()))[2:])

by
<code>
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:])
</code>

==Rev 559==
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 <code>path_to_vistrails_install/vistrails</code> 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 <code>bookmarks.xml</code> inside <code>~/.vistrails</code> folder. On Windows XP it's located on <code>C:\Documents and Settings\your_username\.vistrails</code>. On Windows Vista, it's located at <code>C:\Users\your_username\.vistrails</code>.

Known issues

2008-06-27T18:16:11Z

Draperg: /* Updated comments on command-Line switches table based on feedback from 27 June dev meeting.*/

Check this page for known issues with VisTrails Releases and how to work around them.

==Command-Line Switches==
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.

<table border=1>
<tr>
<th>Short form</th><th>Long form</th><th>Description</th>
</tr>
<tr>
<td>-h</td><td>--help</td><td>Print a help message and exit.</td>
</tr>
<tr>
<td>-S ''/path''</td><td>--startup=''/path''</td><td>Set user configuration directory (default is ~/.vistrails). '''NOT WORKING'''. See ticket #213.</td>
</tr>
<tr>
<td>-?</td><td> </td><td>Print a help message and exit.</td>
</tr>
<tr>
<td>-v</td><td>--version</td><td>Print version information and exit.</td>
</tr>
<tr>
<td>-V ''num''</td><td>--verbose=''num''</td><td>Set verboseness level (0–2, default=0,
higher means more verbose). '''MORE TESTING NEEDED.''' I haven't yet found a use case where this makes a difference.</td>
</tr>
<tr>
<td>-b</td><td>--noninteractive</td><td>Run in non-interactive (batch) mode.</td>
</tr>
<tr>
<td>-n</td><td>--nosplash</td><td>Do not display splash screen on startup. '''NOT WORKING'''. May possibly be related to Ticket #211. Otherwise, there is a simple one-line code fix to workaround this issue.</td>
</tr>
<tr>
<td>-c ''num''</td><td>--cache=''num''</td><td>Enable/disable caching (0 to disable,
nonzero to enable. Default is enabled).</td>
</tr>
<tr>
<td>-m ''num''</td><td>--movies=''num''</td><td>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. This switch is more for the Spreadsheet than for VisTrails proper, but we'll keep it for now.</td>
</tr>
<tr>
<td>-s</td><td>--multiheads</td><td>Display the Builder and Spreadsheet on
different screens (if available). '''NOT WORKING.''' See Ticket #211.</td>
</tr>
<tr>
<td>-x</td><td>--maximized</td><td>Maximize Builder and Spreadsheet windows at startup. '''NOT WORKING.''' See Ticket #211.</td>
</tr>
<tr>
<td>-l</td><td>--nologger</td><td>Disable logging. '''NOT WORKING.''' Known issues.</td>
</tr>
<tr>
<td>-d</td><td>--debugsignals</td><td>Debug Qt signals. '''NOT USED.''' To be removed.</td>
</tr>
<tr>
<td>-a ''params''</td><td>--parameters=''params''</td><td>Set workflow parameters (non-interactive mode only). '''WORKING, BUT''' this option will eventually be superseded by the Medley functionality.</td>
</tr>
<tr>
<td>-t ''host''</td><td>--host=''host''</td><td>Set hostname or IP address of database
server.</td>
</tr>
<tr>
<td>-r ''port''</td><td>--port=''port''</td><td>Set database port.</td>
</tr>
<tr>
<td>-f ''dbName''</td><td>--db=''dbName''</td><td>Set database name.</td>
</tr>
<tr>
<td>-u ''userName''</td><td>--user=''userName''</td><td>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.</td>
</tr>
</table>

==Rev 674==
On Linux machines using PyQt4.2, there is a bug that causes vtk pipelines not to show on the spreadsheet.
Solution: edit the file <code>path_to_vistrails_src/vistrails/packages/vtk/vtkcell.py</code>

in the import section (around line 27), add
import sip
replace line 244:
vp = '_%s_void_p' % (hex(int(QtGui.QX11Info.display()))[2:])

by
<code>
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:])
</code>

==Rev 559==
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 <code>path_to_vistrails_install/vistrails</code> 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 <code>bookmarks.xml</code> inside <code>~/.vistrails</code> folder. On Windows XP it's located on <code>C:\Documents and Settings\your_username\.vistrails</code>. On Windows Vista, it's located at <code>C:\Users\your_username\.vistrails</code>.

Known issues

2008-06-27T16:10:47Z

Draperg: Added a table detailing the status of the command-line arguments.

Check this page for known issues with VisTrails Releases and how to work around them.

==Command-Line Switches==
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.

<table border=1>
<tr>
<th>Short form</th><th>Long form</th><th>Description</th>
</tr>
<tr>
<td>-h</td><td>--help</td><td>Print a help message and exit.</td>
</tr>
<tr>
<td>-S ''/path''</td><td>--startup=''/path''</td><td>Set user configuration directory (default is ~/.vistrails). '''NOT WORKING'''. See ticket #213.</td>
</tr>
<tr>
<td>-?</td><td> </td><td>Print a help message and exit.</td>
</tr>
<tr>
<td>-v</td><td>--version</td><td>Print version information and exit.</td>
</tr>
<tr>
<td>-V ''num''</td><td>--verbose=''num''</td><td>Set verboseness level (0–2, default=0,
higher means more verbose). '''NOT WORKING.''' I cannot tell whether this option makes any difference.</td>
</tr>
<tr>
<td>-b</td><td>--noninteractive</td><td>Run in non-interactive (batch) mode.</td>
</tr>
<tr>
<td>-n</td><td>--nosplash</td><td>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.</td>
</tr>
<tr>
<td>-c ''num''</td><td>--cache=''num''</td><td>Enable/disable caching (0 to disable,
nonzero to enable. Default is enabled). '''UNTESTED.''' Not sure how to verify this.</td>
</tr>
<tr>
<td>-m ''num''</td><td>--movies=''num''</td><td>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.</td>
</tr>
<tr>
<td>-s</td><td>--multiheads</td><td>Display the Builder and Spreadsheet on
different screens (if available). '''NOT WORKING.''' See Ticket #211.</td>
</tr>
<tr>
<td>-x</td><td>--maximized</td><td>Maximize Builder and Spreadsheet windows at startup. '''NOT WORKING.''' See Ticket #211.</td>
</tr>
<tr>
<td>-l</td><td>--nologger</td><td>Disable logging. '''NOT WORKING.''' This is a weird one. I've experimented a bit with the code, but cannot get the logging flag to behave predictably.</td>
</tr>
<tr>
<td>-d</td><td>--debugsignals</td><td>Debug Qt signals. '''NOT WORKING.''' As far as I can tell, this option is never exercised in the code.</td>
</tr>
<tr>
<td>-a ''params''</td><td>--parameters=''params''</td><td>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.</td>
</tr>
<tr>
<td>-t ''host''</td><td>--host=''host''</td><td>Set hostname or IP address of database
server.</td>
</tr>
<tr>
<td>-r ''port''</td><td>--port=''port''</td><td>Set database port.</td>
</tr>
<tr>
<td>-f ''dbName''</td><td>--db=''dbName''</td><td>Set database name.</td>
</tr>
<tr>
<td>-u ''userName''</td><td>--user=''userName''</td><td>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.</td>
</tr>
</table>

==Rev 674==
On Linux machines using PyQt4.2, there is a bug that causes vtk pipelines not to show on the spreadsheet.
Solution: edit the file <code>path_to_vistrails_src/vistrails/packages/vtk/vtkcell.py</code>

in the import section (around line 27), add
import sip
replace line 244:
vp = '_%s_void_p' % (hex(int(QtGui.QX11Info.display()))[2:])

by
<code>
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:])
</code>

==Rev 559==
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 <code>path_to_vistrails_install/vistrails</code> 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 <code>bookmarks.xml</code> inside <code>~/.vistrails</code> folder. On Windows XP it's located on <code>C:\Documents and Settings\your_username\.vistrails</code>. On Windows Vista, it's located at <code>C:\Users\your_username\.vistrails</code>.

Known issues

2008-06-23T21:45:38Z

Draperg: /* Rev 559 */

Check this page for known issues with VisTrails Releases and how to work around them.
==Rev 674==
On Linux machines using PyQt4.2, there is a bug that causes vtk pipelines not to show on the spreadsheet.
Solution: edit the file <code>path_to_vistrails_src/vistrails/packages/vtk/vtkcell.py</code>

in the import section (around line 27), add
import sip
replace line 244:
vp = '_%s_void_p' % (hex(int(QtGui.QX11Info.display()))[2:])

by
<code>
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:])
</code>

==Rev 559==
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 <code>path_to_vistrails_install/vistrails</code> 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 <code>bookmarks.xml</code> inside <code>~/.vistrails</code> folder. On Windows XP it's located on <code>C:\Documents and Settings\your_username\.vistrails</code>. On Windows Vista, it's located at <code>C:\Users\your_username\.vistrails</code>.

People

2008-05-19T21:05:32Z

Draperg: /* Current Team */

== Principal Investigators ==

* Dr. [http://www.cs.utah.edu/~juliana Juliana Freire]
* Dr. Claudio Silva -- Page on wiki: [[User:Csilva]]

== Current Team ==

* [http://www.sci.utah.edu/~eranders Erik Anderson]
* Jason Callahan
* [http://www.sci.utah.edu/~stevec Steven P. Callahan]
* [http://www.sci.utah.edu/cgi-bin/SCIpersonnel.pl?username=lcarlo Lorena Carlo]
* [http://www.cs.utah.edu/~dakoop David Koop]
* Lauro Lins
* [http://www.sci.utah.edu/~emanuele Emanuele Santos]
* [http://www.sci.utah.edu/~cscheid Carlos E. Scheidegger]
* [http://www.sci.utah.edu/~hvo Huy T. Vo]
* [http://www.cs.utah.edu/~draperg Geoff Draper]

== Previous Members ==

* Louis Bavoil
* Marcelo Nery dos Santos
* Nathan Smith
* Wayne Tyler