Hi all,
I am trying to import paraview.simple from an external Python
interpreter. I am trying to use the ParaView 3.8.0 binary distribution
and I have all my paths setup properly, but I'm getting the following error:
import paraview.simple
Traceback (most recent call last):
File stdin,
Hi,
As I am likely to require customized GUI controls in the near future, I
decided to look at the example in the Paraview documentation:
http://www.paraview.org/Wiki/Plugin_HowTo#Adding_an_object_panel
I am finding that the plugin generated by this example compiles fine,
and appears
I've run the data through the EnSight tool ens_checker and the dataset
passes correctly.But, there's clearly something that the ParaView
reader doesn't like about the Pressure dataset. Is the EnSight
reader in Paraview using the VTK reader?The reason I ask is that I
am able to
On Mon, Aug 2, 2010 at 12:03 PM, owen.arn...@stfc.ac.uk wrote:
Hi,
As I am likely to require customized GUI controls in the near future, I
decided to look at the example in the Paraview documentation:
http://www.paraview.org/Wiki/Plugin_HowTo#Adding_an_object_panel
I am finding
Hi,
I have one simple question - is it possible to somehow produce the
annotations for the mesh nodes to show their ID in Paraview?
I'm aware of the fact, that I can look this up in the table view, but doing
it for each node I'm interested in is not exactly the most efficient way.
Regards
Open the selection inspector ('view' menu) and take the selection tool
(the one which selects nodes, not cells). Then select the part you're
interested in, go to the 'Point label' tab in the selction tool (all
the way to the bottom), and tick the 'visible' thing. The dropdown box
will let you
Hi,
Thanks a lot, this was exactly what I needed. Somehow I kept looking for
annotations instead of labels and couldn't find what I wanted ;-)
Regards
Josef
-Original Message-
From: Ivo Roghair [mailto:ivorogh...@gmail.com]
Sent: Monday, August 02, 2010 8:54 PM
To: Josef Dubsky
Cc:
Klaus,
I've tracked this issue down. It was indeed due to byte ordering. The
version number was being read incorrectly. Attached is a patch for
the fix. It have been committed to git master. I'll ensure that it
gets into the 3.8.1 release as well.
Utkarsh
On Fri, Jul 30, 2010 at 10:22 AM,
The EnSight reader that VisIt uses is a fork of the VTK reader from 5
years ago or so. So, they either fixed a bug and not contributed it back
or there has been a regression in the VTK reader since then.
-berk
On Mon, Aug 2, 2010 at 1:15 PM, Rick Angelini rick.angel...@us.army.mil wrote:
I've
Most probably. The only way to get around this (and other similar problems)
is to build ParaView from source using the same version of Python and Qt
as yours. Otherwise, you'll get conflicts. Also, make sure that your Mac
target is the same as your Python when building. I forgot the CMake variable
CMAKE_MACOSX_DEPLOYMENT_TARGET
On Mon, Aug 2, 2010 at 8:07 PM, Berk Geveci berk.gev...@kitware.com wrote:
Most probably. The only way to get around this (and other similar problems)
is to build ParaView from source using the same version of Python and Qt
as yours. Otherwise, you'll get
11 matches
Mail list logo
