Difference between revisions of "ParaView Plugin"
Jump to navigation
Jump to search
m (Initial outlining) |
|||
| Line 1: | Line 1: | ||
==Installation== | ==Installation== | ||
* ParaView patch | There are three components to the VisTrails plugin for ParaView. First, a patch to the ParaView source code is required, since ParaView does not provide the necessary access to its undo stack by default. Second, there is a standard ParaView plugin that will capture the actions that the user performs. Third, there is a plugin version of VisTrails. | ||
==== ParaView patch ==== | |||
ParaView must be compiled from source for the VisTrails plugin to work. The source code can be downloaded from [http://www.paraview.org/paraview/resources/software.html here]. | |||
Since there has been development on the undo stack in ParaView between the latest release (3.4) and the current cvs development version, there are two patches available. | |||
* [http://link.to.patch 3.4.0 release] | |||
* [http://link.to.patch cvs development version] | |||
These patches can be installed with: | |||
cd ParaView3 | |||
patch -p0 < ParaView.patch | |||
** BULID_SHARED_LIBS on | ** BULID_SHARED_LIBS on | ||
* ParaView plugin | * ParaView plugin | ||
| Line 6: | Line 18: | ||
* plugin paths | * plugin paths | ||
==Usage== | ==Usage== | ||
Revision as of 22:03, 6 January 2009
Installation
There are three components to the VisTrails plugin for ParaView. First, a patch to the ParaView source code is required, since ParaView does not provide the necessary access to its undo stack by default. Second, there is a standard ParaView plugin that will capture the actions that the user performs. Third, there is a plugin version of VisTrails.
ParaView patch
ParaView must be compiled from source for the VisTrails plugin to work. The source code can be downloaded from here. Since there has been development on the undo stack in ParaView between the latest release (3.4) and the current cvs development version, there are two patches available.
These patches can be installed with:
cd ParaView3 patch -p0 < ParaView.patch
- BULID_SHARED_LIBS on
- ParaView plugin
- VisTrails plugin version
- plugin paths
Usage
- Data and state files are absolute - they must exist in the same location to replay any VisTrail operations
How it works
- Types of operations:
- Generic changes that get put on the undo stack.
- State file load.
- Must be replayed from version 0 since these cannot be undone.
- Anything else that doesn't get put on the undo stack will not be captured and therefore not replay correctly!
- ParaView / VisTrails message loops.
Known issues
- Has only been tested with local ParaView server configuration.
- Has only been tested on Windows.
- Loading ParaView with VisTrails already running.
- VisTrails captures some initialization of ParaView.
- Haven't seen this happen when the ParaView plugin spawns the VisTrails process itself.