#Paraview plugin install#
#Paraview plugin zip file#

The plugin can be installed in your home folder Note this can also be done on the commandline to ccmake but I cant remember the exact requirements.

If it does not work you will probably need to change the first statemetn in the CMakeLists.txt file to, point to the location of the development paraview installation. If this works then you should be able to compile the plugin with

(fairly cryptic erros messages can help solve problems) In the folder containing the plugin source files create a Build folder. Once you have a full development installation (which will include a number of libraries, c++ compilers, cmake etc), create your own folder (anywhere you like) with the plugin unzipped/untared in it.

#Paraview plugin install#

Otherwise you need to download and compile and install your own version. Depending on the source for your version or paraview will determine if you can do that. To compile the plugin you need a full development install of the paraview system. I debugged this newest version on paraview 4.4.0. The plugin needs to be compiled for the version of paraview you are running. Not sure what system you are working from (looks like linux) and I can only advise for linux. Both seem to be used sometimes in the same document. I have only Linux for testing - other systems need other developers (probably a problem will arise for specifying int64)!Īn important question - is the file format SERAFIN or SELAFIN. Please try the code and pass on the experience. This current work could not have come about without the initial work provided in creating the origianl plugin.

#Paraview plugin zip file#

For now here is a zip file of the source. When Opentelemac transfers to a flexible code management system (eg git. I have built my version on Linux (Fedora) using g++ v5.3. This is a character of the paraview build process and does not allow compilation of out of source plugins without a full build system existing. The plugin code has been packaged as source code for compilation in its own location, with a reference to where the paraview source built code is located.

Definitely need to add in support for double precision floats ie SERAFIND. Some implemented improvements include caching of XY coords rather than re-reading each render. With a functioning plugin, I am now looking at some improvements on the original. Some coding needed to be changed, new api! Other parts needed cleanups, and inparticular the read functions needed to use int64 for keeping sync with file positioning (its the same problem as I found in the telemac v7 code). Based on the original plugin which only worked on paraview 3.x, I have converted the code into a working plugin for V4.4 (current version).