Occasionally, some actions are not captured by the plugin.A simple workaround for this issue is to simply restart ParaView before loading a VisTrail file. The result is that when a number of actions have been performed, there may be errors if a different. Resetting the ParaView state often does not perform a complete reset.vt file, you may need to 'Zoom To Data' for a good view. Most view state changes are not recorded by the plugin. State files can also be saved from ParaView, and loaded into instances that do not have the VisTrails plugin loaded. vt files can be saved and loaded from the Provenance Recorder window, which will include the current state, as well as all previous states that have been explored. Like data files, the absolute path of state files are stored by VisTrails, so replaying of the state load requires that the file remains in the same place and unchanged. When a pipeline that is higher in the version tree is selected, playback must begin at the root, which may be slow. The user may load ParaView state files, but state loads cannot be undone. Therefore, whenever the pipeline is replayed, all of the data files must be available in the same location. Currently, when data files are loaded in ParaView, VisTrails records the absolute filename. ParaView pipelines can be loaded simply by clicking on the desired version. As the user performs actions, they are recorded by VisTrails in the Provenance Recorder window. With the VisTrails plugin loaded, ParaView may be used as normal. The ParaView directory structure may look like this on Windows: No compiling is necessary, though the 'vistrails' directory must be copied from the distribution directory to the ParaView 'plugins' directory so the plugin can find it. Python 2.5 or 2.6, QT, and PyQT are required to run VisTrails. These can be loaded manually from within ParaView, or it can be copied to the ParaView plugins directory so it automatically gets loaded on startup.Ī version of VisTrails that has been adapted to run along side ParaView is located in the 'vistrails' subdirectory of the distribution. The plugin can then be compiled, which creates 'VisTrailsPlugin.dll' on Windows, a 'libVisTrailsPlugin.so' on Linux, or a 'libVisTrailsPlugin.dylib' on Mac. You may need to set the ParaView_DIR CMake variable to point to your ParaView build directory. The plugin, like ParaView itself, uses CMake to generate Visual Studio project files and make files. The source code to the ParaView plugin is located in the 'plugins' subdirectory of the source distribution. The BUILD_SHARED_LIBS CMake variable must be set to ON, and ParaView can then be compiled as normal. Make sure to set the correct version of the python executable and libs. Check the Auto Load checkbox if you want the plugin to initialize automatically with ParaView (see Figure below).Select VisTrailsPlugin in the Local Plugins Panel.The installers for Mac and Windows contain both components and they will replace the current installation of the plugin in ParaView.Īfter installing ParaView 3.8.0, the plugin should start automatically. Second, there is a version of VisTrails that has been adapted to interface with the ParaView plugin. First, there is a plugin for ParaView that will capture the actions that the user performs. There are two components to the VisTrails plugin for ParaView. Platform independent source code (version 1.0-beta)Ī Users guide is also available for download.The files are available for download from SourceForge under the GPL v2 and the instructions are below: On Linux, you have to install it from source. Please direct questions and bug reports to packages for Mac and Windows are already included in ParaView-3.8.0 for Mac (10.5+) and Windows (32bit and 64bit). This allows navigation of all of the pipeline versions that have previously been explored. All of the actions a user performs while building and modifying a pipeline in ParaView are captured by the plugin. The VisTrails plugin for ParaView incorporates the provenance management capabilities of VisTrails into ParaView.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |