Hi Seb!
I found out that the following works without having the need to access the C++
API explicitly and this is what I am using now:
from paraview.simple import *
LoadPlugin(libSurfaceLIC.so,ns=globals())
[...]
view = GetRenderView()
source = GetActiveSource()
rep = Show(source,view)
On 7/26/2012 10:56 AM, Karl König wrote:
Apply three subsequent calculators that turn the coords vector by means
of the following formulas
into three additional data arrays. Then apply the Threshold filter
subsequently using the calculated x-, y- and z-coordinate data arrays to
clip your data
Thank you for this clarification!
Matthias
-Ursprüngliche Nachricht-
Von: David E DeMarle [mailto:dave.dema...@kitware.com]
Gesendet: Donnerstag, 26. Juli 2012 17:12
An: Zenker, Dr. Matthias
Cc: paraview@paraview.org
Betreff: Re: [Paraview] Data saving in vtr format and compression
On
I have a Cartesian volume grid consisting of hex cells of varying size
in VTK legacy unstructured format. When I do a (Cartesian) slice
through the grid, the result is displayed as a triangulated surface
instead of the expected surface of quads. Is that just a result of
the slicing process
Michael,
Yes, it is. If you want to keep the hex/quad structure, you can resort
to the Threshold filter, thresholding based on coordinate values. See
yesterday's posting http://markmail.org/message/wooi4pdb7j4h6z36 on how
to get coordinates as additional data arrays. Note, though, that with
the
Michael,
in the same manner if you are using ParaView/master, you can use the
crinkle option in the slice that will do exactly the same thing as
Karl was explaining but with a simpler interaction. It will basically
keep the full cells along the slice.
Or if you are not on master, you can achieve
Hi,
Did you ever get the Matlab writing of the binary VTK files to work? I'm
having problems with them too: PV crashes when reading the binary files.
Thanks,
--
Petr Krysl
University of California, San Diego
Skype: Petr.Krysl.UCSD.EDU
http://hogwarts.ucsd.edu/~pkrysl/
hi!
I want to get Paraview installed on an SGI system with MPT. I ran into
this thread.
http://article.gmane.org/gmane.comp.science.paraview.user/11954/match=sgi+mpt
Could some one please tell me where I can change the settings to link using
-lmpi and also the the compile flags that Pratik
Hi Ganesh,
Here are the settings that worked on an SGI Altix UV. You may want to
add export MPI_TYPE_MAX=100 to your run script as well.
Burlen
#!/bin/bash
BUILD_TYPE=Release
CC_PATH=/opt/intel/Compiler/11.1/038
MPI_PATH=/opt/sgi/mpt/mpt-2.04
MESA_PATH=$OSMESA_ROOT
Hi Utkarsh,
I'm noticing a that custom panels derived from
pqAutoGeneratedObjectPanel don't respect the new panel_visibility
attribute, however they still honor the property show hint. Is this
going to change for the next release?
Also having some weird issues in custom panels derived from
Burlen,
Kyle can give you more details, but the theme is that
pqAutoGeneratedObjectPanel and related classes are going to be
deprecated. For backwards compatibility sake, these will be around for
the next release and when a custom-panel is provided using the past
mechanisms, ParaView will indeed
11 matches
Mail list logo