Hi Pat,
Maybe you could back up a bit and explain what you're trying to
accomplish? Maybe we can suggest another approach that will work while
avoiding the incompatibilities vtk version requirements of dolfin and
paraview.
Of course! Apologies that I didn't explain this in more detail
Hi Max,
Maybe you could back up a bit and explain what you're trying to
accomplish? Maybe we can suggest another approach that will work while
avoiding the incompatibilities vtk version requirements of dolfin and
paraview.
Have you tried running your script using 'pvpython' as the interpreter
Hi Pat!
[Apologies for sending you this twice, I accidentally didn't hit 'reply
all'.]
Many thanks for the detailed reply! Indeed, I'm suspecting a conflict
between different vtk versions, but I don't know which ones could be the
culprits. I'm not sure the issue is actually related to the FEniCS
See, if you can import vtk, then you're probably importing a version of
the vtk libraries that are different than the ones ParaView uses. What
version of ParaView are you using and how did you install ParaView? Did
you build from source, install the binaries from paraview.org, or apt-get
Hi,
apologies for bumping my own message, but looking at the thread view
[1] of the mailing list archives I just realised that strangely my
email was filed under a completely unrelated thread (even though I
hadn't replied to any messages) and maybe this is why it got lost in
people's inboxes.
So
Hi,
It sounds like you probably have multiple versions of the vtk libraries
installed someplace in your path. Maybe the FEniCS package ships it's own
version of the vtk libraries? If FEniCS imports a different version of
vtk, then paraview won't be able to import vtk within the same memory
