Difference between revisions of "Known issues"
(Added a table detailing the status of the command-line arguments.) |
|||
(13 intermediate revisions by 4 users not shown) | |||
Line 1: | Line 1: | ||
Check this page for known issues with VisTrails Releases and how to work around them. | Check this page for known issues with VisTrails Releases and how to work around them. | ||
== Version 2.1.3 == | |||
The mac binary contains the wrong usersguide. Please use [http://www.vistrails.org/usersguide/v2.1/html/VisTrails.pdf this one]. | |||
== Version 2.1 == | |||
The server doesn't start because of an import problem. This can be fixed by replacing vistrails/gui/application_server.py with [http://pastebin.com/raw.php?i=Ye5jEBkP this file]. | |||
Parameter Explorations does not work. Parameters are cleared before being executed. This can be fixed by replacing vistrails/gui/paramexplore/pe_view.py with [[media:pe_view.zip]]. | |||
== Version 2.0 == | |||
=== Ubuntu 10.04 === | |||
The version of PyQt shipped with Ubuntu 10.04 is not supported by VisTrails. A new version can be downloaded here: | |||
http://www.riverbankcomputing.co.uk/software/pyqt/download/ | |||
== Version 1.4.2 rev1728 == | |||
=== Web Services package fails to load === | |||
This is because of the new way packages are structured (see [http://www.vistrails.org/index.php/UsersGuideVisTrailsPackages#How_to_make_you_package_reloadable UsersGuideVisTrailsPackages]). As the web services package serializes information to disk for caching purposes, the stored information became inconsistent. So, if you see the error | |||
('Error loading configuration file: ', '~/.vistrails/webServices/modules.conf') | |||
Just remove your ~/.vistrails/webServices and enable the package again. | |||
We are preparing a fix for this that will be available in the next release. | |||
===VisTrails fails to start on Ubuntu/Fedora=== | |||
The changes in the apt-get interface have not been reflected in this VisTrails version. Please use the [http://www.vistrails.org/index.php/Downloads#Nightly_build nightly build] as the fix was already ported to VisTrails trunk. | |||
== Version 1.2.1 rev1337 == | |||
=== VisTrails does not finish properly when executed in batch mode === | |||
In your VisTrails installation, edit the file located at VisTrails/vistrails/vistrails.py as follows: | |||
Change lines 46-48 | |||
if (app.temp_configuration.interactiveMode or | |||
not app.temp_configuration.check('spreadsheetDumpCells')): | |||
v = app.exec_() | |||
by: | |||
if (app.temp_configuration.interactiveMode): | |||
v = app.exec_() | |||
else: | |||
app.finishSession() | |||
==Command-Line Switches== | ==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. | 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. | ||
Line 22: | Line 58: | ||
<tr> | <tr> | ||
<td>-V ''num''</td><td>--verbose=''num''</td><td>Set verboseness level (0–2, default=0, | <td>-V ''num''</td><td>--verbose=''num''</td><td>Set verboseness level (0–2, default=0, | ||
higher means more verbose).<br> <font color="RED">''' | higher means more verbose).<br> <font color="RED">'''MORE TESTING NEEDED.''' I haven't yet found a use case where this makes a difference.</font></td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
Line 28: | Line 64: | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>-n</td><td>--nosplash</td><td>Do not display splash screen on startup. | <td>-n</td><td>--nosplash</td><td>Do not display splash screen on startup.</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>-c ''num''</td><td>--cache=''num''</td><td>Enable/disable caching (0 to disable, | <td>-c ''num''</td><td>--cache=''num''</td><td>Enable/disable caching (0 to disable, | ||
nonzero to enable. Default is enabled). | nonzero to enable. Default is enabled).</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>-m ''num''</td><td>--movies=''num''</td><td>Set automatic movie creation on spreadsheet | <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. <br><font color="RED"> | (0 or 1, default=1). Set this to zero to work around VTK bug with offscreen renderer and OpenGL texture3D mappers. <br><font color="RED">This switch is more for the Spreadsheet than for VisTrails proper, but we'll keep it for now.</font></td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>-s</td><td>--multiheads</td><td>Display the Builder and Spreadsheet on | <td>-s</td><td>--multiheads</td><td>Display the Builder and Spreadsheet on | ||
different screens (if available). | different screens (if available).</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>-x</td><td>--maximized</td><td>Maximize Builder and Spreadsheet windows at startup. | <td>-x</td><td>--maximized</td><td>Maximize Builder and Spreadsheet windows at startup.</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>-l</td><td>--nologger</td><td>Disable logging. <br><font color="RED">'''NOT WORKING.''' | <td>-l</td><td>--nologger</td><td>Disable logging. <br><font color="RED">'''NOT WORKING.''' Known issues.</font></td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>-d</td><td>--debugsignals</td><td>Debug Qt signals. <br><font color="RED">'''NOT | <td>-d</td><td>--debugsignals</td><td>Debug Qt signals. <br><font color="RED">'''NOT USED.''' To be removed.</font></td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>-a ''params''</td><td>--parameters=''params''</td><td>Set workflow parameters (non-interactive mode only). <br><font color="RED">'''WORKING, BUT''' this option | <td>-a ''params''</td><td>--parameters=''params''</td><td>Set workflow parameters (non-interactive mode only). <br><font color="RED">'''WORKING, BUT''' this option will eventually be superseded by the Medley functionality.</font></td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
Line 68: | Line 104: | ||
</tr> | </tr> | ||
</table> | </table> | ||
==Rev 674== | ==Rev 674== |
Latest revision as of 17:20, 6 August 2014
Check this page for known issues with VisTrails Releases and how to work around them.
Version 2.1.3
The mac binary contains the wrong usersguide. Please use this one.
Version 2.1
The server doesn't start because of an import problem. This can be fixed by replacing vistrails/gui/application_server.py with this file.
Parameter Explorations does not work. Parameters are cleared before being executed. This can be fixed by replacing vistrails/gui/paramexplore/pe_view.py with media:pe_view.zip.
Version 2.0
Ubuntu 10.04
The version of PyQt shipped with Ubuntu 10.04 is not supported by VisTrails. A new version can be downloaded here: http://www.riverbankcomputing.co.uk/software/pyqt/download/
Version 1.4.2 rev1728
Web Services package fails to load
This is because of the new way packages are structured (see UsersGuideVisTrailsPackages). As the web services package serializes information to disk for caching purposes, the stored information became inconsistent. So, if you see the error
('Error loading configuration file: ', '~/.vistrails/webServices/modules.conf')
Just remove your ~/.vistrails/webServices and enable the package again. We are preparing a fix for this that will be available in the next release.
VisTrails fails to start on Ubuntu/Fedora
The changes in the apt-get interface have not been reflected in this VisTrails version. Please use the nightly build as the fix was already ported to VisTrails trunk.
Version 1.2.1 rev1337
VisTrails does not finish properly when executed in batch mode
In your VisTrails installation, edit the file located at VisTrails/vistrails/vistrails.py as follows:
Change lines 46-48
if (app.temp_configuration.interactiveMode or not app.temp_configuration.check('spreadsheetDumpCells')): v = app.exec_()
by:
if (app.temp_configuration.interactiveMode): v = app.exec_() else: app.finishSession()
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.
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). MORE TESTING NEEDED. I haven't yet found a use case where this makes a difference. |
-b | --noninteractive | Run in non-interactive (batch) mode. |
-n | --nosplash | Do not display splash screen on startup. |
-c num | --cache=num | Enable/disable caching (0 to disable, nonzero to enable. Default is enabled). |
-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. This switch is more for the Spreadsheet than for VisTrails proper, but we'll keep it for now. |
-s | --multiheads | Display the Builder and Spreadsheet on different screens (if available). |
-x | --maximized | Maximize Builder and Spreadsheet windows at startup. |
-l | --nologger | Disable logging. NOT WORKING. Known issues. |
-d | --debugsignals | Debug Qt signals. NOT USED. To be removed. |
-a params | --parameters=params | Set workflow parameters (non-interactive mode only). WORKING, BUT this option will eventually be superseded by the Medley functionality. |
-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. |
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 path_to_vistrails_src/vistrails/packages/vtk/vtkcell.py
in the import section (around line 27), add
import sip
replace line 244:
vp = '_%s_void_p' % (hex(int(QtGui.QX11Info.display()))[2:])
by
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:])
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 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 bookmarks.xml
inside ~/.vistrails
folder. On Windows XP it's located on C:\Documents and Settings\your_username\.vistrails
. On Windows Vista, it's located at C:\Users\your_username\.vistrails
.