Here's what I found:
1. Make sure you set "Array Association" on "Python Calculator" to "Cell Data".
2. The volume() code internally uses vtkCellQuality filter. Now, when
I debugged into it, I see that is doesn;t support voxel cell types --
the cells produced by vtkImageData. Now is there are
And at a more basic level, how do I find the volume of cells in my dataset?
Thanks,
Alan
From: ParaView [mailto:paraview-boun...@paraview.org] On Behalf Of Scott, W Alan
Sent: Thursday, June 16, 2016 7:30 PM
To: paraview@paraview.org
Subject: [EXTERNAL] [Paraview] python calculator confusion
I'm trying to figure out the volume of each cell of a dataset. I am trying to
use the Python Calculator. However, frankly, the data doesn't make sense. So,
I tried something really, really simple. And things still aren't making sense.
Here is what I did:
* ParaView 5.0.1, local
Steve,
I worry it sounds a bit like a bug.
Can you provide us with a toy dataset (or non-toy, if necessary) that
replicates the issue? Also, really, really good directions (+Y, roll mouse
wheel in 4 times)?
Alan
-Original Message-
From: ParaView
I'm using Paraview v5.0.1 to visualize some geophysical data, but I'm
running into a rendering issue. When I zoom in to my data sets, data in
the background randomly jumps in front of cross-sections in the
foreground.
I'm running into a similar issue.
I have three cross sections, along the
Hello all,
I'm using Paraview v5.0.1 to visualize some geophysical data, but I'm
running into a rendering issue. When I zoom in to my data sets, data in the
background randomly jumps in front of cross-sections in the foreground.
Here's a video link showing an example of this issue:
Peter,
In ParaView's collaboration support there's the notion of a master and
everyone else. The first client that connects to the pvserver is the
"master" by default. The master is the only one that should create new
proxies. This doesn't preclude the other clients from not creating new
proxies,
Visualization Showcase
--
Important Dates:
February 16, 2016: *Submissions open*
July 31, 2016: *Submissions deadline*
September 1, 2016: *Notifications sent*
--
*A new format for 2016!*
SC16’s Visualization and Data Analytics Showcase
Paul,
I looked at a few of the bugs listed below.
I replicated 15944, this would impact my users. It's on Sandia's list.
13802 works correctly on 5.0.1. Note that you are creating 2.6 billion cells,
and from what I can tell, you are running out of memory on your server side. I
was able
Hello again,
I have a follow-up question concerning my attempts to create a
collaborative standalone client. The attached example connects to a
pvserver running on localhost (with --multi-clients option) and creates a
SphereSource together with its representation. Depending on whether
"USEVIEW" is
> but I always wondered about the development process of VTK/ParaView with
> respect to bug
> reports. There seem to be a huge number of reported bugs for ParaView (and a
> few for VTK), ranging from crashes to incorrect functionality to feature
> requests.
Bugs often get prioritized by several
Hi,
On 15-06-16 16:18, Berk Geveci wrote:
I believe that the main differentiator between ParaView and other vis
tools out there is the broad functionality _and_ the code quality.
Having the two together is really tough but our community managed this
with a heavy emphasis on code review and code
12 matches
Mail list logo
