Here my probably faulty python code:
slice = vtk.vtkCutter()
plane = vtk.vtkPlane()
plane.SetOrigin(0,0,0)
plane.SetNormal(0,1,0)
slice.SetCutFunction(plane)
slice.SetInput(field)
slice.Update()
out.SetFieldData(slice.GetFieldData())
The result is an empty Output Window popping up along
On Fri, Feb 19, 2010 at 09:32:00AM -0500, Utkarsh Ayachit wrote:
YOu may have to do a clean build.
Jacob, a clean build typically means make clean or
make distclean before you build again with shared libs.
If these targets are not available, you may need to
remove the whole of the paraview build
Hi,
I have compiled the representation plugin in the CVS and I have the problem
that I cannot change the colour for the Special Mapper in the Object
Inspector's Display panel. This seems to be due to the display properties
being for the surface representation rather than the wireframe (it shows
I am using one mesh that is deforming in time. So node1.mesh2 is the the
same node as node1.mesh1, just in a different location in space.
But your point is well made that if I were using unrelated meshes (i.e.
roughly similar geometry but with a different number of nodes in each mesh)
finding
Hello everyone,
I am trying to write a VTK reader to read custom volumetric data into Paraview.
I started with the example vtkImageAlgorithm
(http://www.itk.org/Wiki/VTK_Examples_vtkImageAlgorithm_Filter) and
changed it so the Filter doesn't take any input and output a
vtkImageData.
To
One solution is to share common properties with the
SurfaceRepresentation sub-proxy using the ShareProperties tag. You
can add exceptions (you will have to add exceptions for Input,
Representation properties at the least).
Utkarsh
On Mon, Feb 22, 2010 at 7:48 AM, Paul Edwards
I can't see how this is possible through the SharedProperties as the color
combo box that is displayed in the Display Properties is chosen from the
result of pqPipelineRepresentation::getRepresentationType() (from the call
in pqDisplayProxyEditor.cxx line 695). This will default to
Pulled the latest CVS Head from GitHub? Is that really the latest?
When I tried to configure ParaView with my plugins using
PARAVIEW_EXTRA_EXTERNAL_MODULES I get the following error:
-- Plugin: IPFFilter enabled
CMake Error: File /Components/pqObjectPanelImplementation.h.in does
not
I have some custom filters that I have developed. I use the
PARAVIEW_EXTRA_EXTERNAL_MODULES to compile them directly into
ParaView. I know they are getting compiled as I can see the compile
command go by on the command line. The problem is that they do not
show up when I run ParaView in
Utkarsh,
I was able to pull the latest CVS HEAD for ParaView and compiled
that against the Qt 4.6.1 Cocoa build that I have and it seems that
what ever was changed on CVS HEAD fixed the problem.
Thanks for the heads up.
___
Mike
Hi
I have time series data. I want to isosurface the data with different value
for each time step - but not those in the animation which linearly
interpolates the isosurface value over time.
I want to isosurface based on max-min of the data at each time step.
How would i do it?
thanks
Gowri
I just moved the definition of ParaView_QT_DIR to be just before including
ParaViewCommon. Give it a shot and let me know if it doesn't fix your
problem.
On Mon, Feb 22, 2010 at 12:04 PM, Michael Jackson
mike.jack...@bluequartz.net wrote:
Pulled the latest CVS Head from GitHub? Is that really
One other question:
If I take this one step further, is it possible to send the data at the
current time step to the PPF?
For example I have a mesh deforming in time (ob1) that is being compared to
a baseline with no time data (ob2). All of the nodes are similar. After
looking at some of the
That seems to have fixed that problem.
Would also be nice if the macro paraview_build_optional_plugin was
in the ParaViewPlugins.cmake file as I have to recreate it in each of
my Plugins CMake files because the macro is located in ParaView/
Plugins/CMakeLists.txt
Thanks
I can probably fix that. I'll add it to my todo list.
On Mon, Feb 22, 2010 at 2:36 PM, Michael Jackson
mike.jack...@bluequartz.net wrote:
That seems to have fixed that problem.
Would also be nice if the macro paraview_build_optional_plugin was in the
ParaViewPlugins.cmake file as I have to
Done.
http://www.paraview.org/Bug/view.php?id=10317
I also submitted a bug on saving as Xdmf. I did not fill out the target
version. I didn't know if you wanted to shoot for 3.8 on that one.
http://www.paraview.org/Bug/view.php?id=10318
-Ken
On 2/19/10 6:59 PM, Berk Geveci
On Fri, Feb 19, 2010 at 9:40 PM, David Doria daviddo...@gmail.com wrote:
On Fri, Feb 19, 2010 at 8:48 PM, Berk Geveci berk.gev...@kitware.comwrote:
Can you send instructions to reproduce with sources maybe? Or send two
files?
It is working properly at home... I'll send instructions/files
I can repeat it with sources.
I think it might just be an opengl aliasing effect. The points only seem to
move by 1 pixel (but when they all move at once, you definitely see the
wiggle). If you another object to the scene, like a cone source, it
doesn't move at all.
To repeat:
create point
Actually, the wiggle much more extreme the more the radii vary. Try with
radius 10 and radius 10,000, produces a really big jump.
Pat
On Mon, Feb 22, 2010 at 6:28 PM, pat marion pat.mar...@kitware.com wrote:
I can repeat it with sources.
I think it might just be an opengl aliasing effect.
I am in the early stages of designing a new filter that is supposed to
color triangles based on their normal where the normal is used as an
input to the filter and a unique color is output for each triangle.
My questions are:
Where should I store the color information? As a new set of
** Reply Requested When Convenient **
Hello !
It's good to hear that 3.6.2 supports CAVE enviroment, does anybody of
you ever implement trackíng in the Cave.
thank you
christian
-- Johannes Kepler Universitaet
-- Christian Wohlschlager
-- Altenbergerstr.69
-- 4040 Linz Austria
--
21 matches
Mail list logo
