Thank you all!
Turning on shared libs solved the problem for CMake. However, when I compile
ParaView I get an error related to xdmf.dll which is not built because of
external linker problem:
Bibliothek C:\ParaView-3.14.0\bin\bin\Release\Xdmf.lib und Objekt
might just be that libxml+xdmf didn't rebuild themselves when you turned on
shared libs. Try wiping the build parts of those projects and rerunning cmake
then build again.
JB
From: Boettcher, Prof. Dr. Peter
[mailto:boettc...@kleintierklinik.uni-leipzig.de]
Sent: 26 March 2012 11:27
To:
Thank you, that works!
On 03/21/2012 09:37 PM, Andy Bauer wrote:
To get rid of those points you can use the Threshold filter and then
view that. Some grid types support blanking (soon all of them should)
that could be put into your writer to specify that but I think the
Threshold filter is
Hi.
I'm considering to generate developed surface view on ParaView.
My VTK data contains cylindrical surfaces (defined on theta-z spaces),
and I want to convert them to flat planes (defined on x-y planes).
One idea is re-writing VTK file, but it's pretty troublesome.
Are there any ideas to do it
Hi,
is there an easy way to customize the filter toolbar? For example, the Plot
selection over time I filter is the one I use all the time. I would like to
have a button on the toolbar, like there are buttons for the calculator,
contour plot, clip, ...
How do I do it?
Thanks,
Matthias
In the past I have used the calculator filter to convert polar coordinates
to cartesian or vice versa.
-Ken
On 3/26/12 7:08 AM, Magician f_magic...@mac.com wrote:
Hi.
I'm considering to generate developed surface view on ParaView.
My VTK data contains cylindrical surfaces (defined on theta-z
On Fri, Mar 23, 2012 at 6:13 PM, Lorenzo lovecraf...@gmail.com wrote:
I've tied that, thank you.
Now, my questions are:
1. once I've saved a trace, how I run it in paraview?
Tools-Python Shell-Run Script
Better still, if you choose to save the trace as a macro (or just put
it into
You can record a trace in which you just apply that filter, and then
save the trace as a macro. It won't be in the common filters toolbar,
but it will be in the macros toolbar which is by default right next to
it.
If you are building from source you can add the filter to the Common
group in
Hi David,
thank you for the hints. Unfortunately it doesn't work for me that way. The
macro I get is
-
try: paraview.simple
except: from paraview.simple import *
paraview.simple._DisableFirstRenderCameraReset()
my_file_pvd = GetActiveSource()
The 2004 edition described ParaView 2.x. The 2007 edition described
ParaView 3.x.
Either would be fine to cite.
David E DeMarle
Kitware, Inc.
RD Engineer
21 Corporate Drive
Clifton Park, NY 12065-8662
Phone: 518-881-4909
On Tue, Mar 20, 2012 at 11:39 PM, Tristan Chaplin
Thank you David;
I think I also found something:
http://www.cfd-online.com/Forums/openfoam-post-processing/94538-separate-vtk-files-openfoam-fields-synchronous-time.html#post332912
http://www.cacr.caltech.edu/~slombey/asci/vtk/
I think in the latter it says that you may link many vtp files
pvd files can not point to the older style vtk files, they can only
point to the newer xml based vt? (vtu/vtp/vti etc) files.
A script to convert between them build a two element pipeline
consisting of a vtkDataSetReader connected to a vtkXMLPolyDataWriter.
Set the FileNames on both and call
Dear Paraview users,
I'm using Paraview.3.14. What I tried is to use camera path or
Interpolate camera locations to zoom in or out of the object. But so
far it is only possible to rotate the object. No matter what values the
camera position gets the object doesn't goes away or near from the
13 matches
Mail list logo
