Hello,
my previous mail was wrong. The present problem is not related to those
other bugs.
Here, when using ExtractSubset the extent for cell data in miscalculated
if i==imax or j==jmax or k == kmax.
in vtkExtractGrid.cxx: we have the call
this-Internal-CopyCellData(inExt,outExt,cd,outCD);
Hello,
As an update to this issue (not being able to set tab as field delimiter
character for the csv reader in the gui - it works only copypasting or setting
the field delimiter in python shell), I just found out that this setting is
also not loaded from the .pvsm file in paraview 4.3.1, while
Hi,
I was using the writer from the gui in Paraview. I created a very simple
programmable source (with output type vtkTable) with a column and a field data
array, then clicked File-Save Data from the menu.
In the case of a table, the writer window doesn’t allow to specify the
association
Hi Masaaki,
You don't have to wait. Simply download the latest nightly binary and the
go to Tools - Manage Plugins. There you should see the CGNS plugin. Load
it. After that, when you open the CGNS file, it will give you an option to
use the plugin based reader.
Best,
-berk
On Tue, Mar 24, 2015
Dear ParaView experts,
I'm visualizing paths of neutrons in some media.
Now I prepared the data as point data with displacement
vector to the next point attached to each point, and
visualize them using the Glyph filter with the following
setting:
Glyph Type: Arrow
Orientation: Orient
Scale
Dear David,
Thanks for your response. I'll give it a try.
Kazuyoshi
From: David Thompson david.thomp...@kitware.com
Subject: Re: [Paraview] how not to scale the thickness of the Arrow Glyph?
Date: Wed, 25 Mar 2015 23:01:51 -0400
Hi Kazuyoshi,
I do not think the glyph filter will do what
Hi Kazuyoshi,
I do not think the glyph filter will do what you want it to. You might use a
Python programmable filter[1] to turn each point into a line segment (i.e., a
line from (x,y,z) to (x+dx, y+dy, z+dz)). Then run Cell Centers on the
resulting line segment data and add oriented, unscaled
Hi Matthew,
Settings have been revamped since version 2.4. While some still are stored
in the usual .ini file, most are now stored in a JSON file which is
described on this blog post:
http://www.kitware.com/blog/home/post/672
While the blog post focuses on setting custom defaults, the general
Livia,
It seems reasonable that you should be able to save field data stored in a
vtkTable. Would you mind writing up a feature request at
http://www.paraview.org/Bug/view_all_bug_page.php?
Thanks,
Cory
On Wed, Mar 25, 2015 at 9:47 AM, livia.barazze...@istb.unibe.ch wrote:
Hi,
I was using
