We would like to bump VTK's minimum ffmpeg version from 0.6.5 to something
more recent. This will simplify the vtkFFMPEGWriter class and related cmake
script that we used to support ancient and modern versions of FFMPEG.
Are there any objections? Any suggestions for what minimum version to
choose?
Hi,
With today's gatekeeper review, the way reader and writer plugins are
handled in ParaView has changed. Now, they only need to be specified on the
server through the server manager XML. The Hints section of the XML
specifies what extensions to associate with the reader or the writer. The
advant
Hi Mark,
The adaptor is meant to convert a simulation code's data structures into
something that derives from vtkDataObject. So the adaptor could have a RAW
binary file passed in and produce a vtkImageData for your case. As far as
the Catalyst Python script is concerned, all it is expecting at for
Hello, is there a way to set up a coprocessing adaptor to work with RAW binary
files? What I've done in the past is to first load a RAW binary in the GUI and
export a coprocessing script to save a vti, run the simulation a single
timestep writing the vti, then load that and save another script t
Hi Andy and Utkarsh,
Okay, so for the time being I decided to work with a fully blown Catalyst out
of the ParaView src until I get my head around making editions. This allowed me
to get the GitHub F90 example. However, with the original simulation, I have a
different issue, which I'll start in
Hi everyone,
I built ParaView locally from the current source tree (4.0.1) with
PARAVIEW_ENABLE_PYTHON set to ON in CMake. When calling pvpython in the build
directory, importing paraview.simple works fine. However, this is not the case
after running make install and calling pvpython from the
