Hi.
I have a ParaView macro which sets up a CSVReader, and a PlotData of
that. The variable names and legend names and series colors are all
filled in automatically by ParaView.
What I would like to do is, from the python macro, iterate through all
series in a chart and make specific ones v
Hi Greg,
If you look at Plugins/pvblot/tplot.py you'll find some code that does
exactly this. You may find some other useful chart code in there too.
For your example, you could do:
series_names = [name for name in d.GetProperty("SeriesNamesInfo")]
Pat
On Wed, Oct 5, 2011 at 8:19 PM, Greg Sc
On 10/06/2011 07:33 AM, pat marion wrote:
series_names = [name for name in d.GetProperty("SeriesNamesInfo")]
Hi, Pat.
Thanks for the helpful pointers.
After setting everything up in ParaView (3.10.1, 64-bit), I'm not
getting results. Here is what I did from the ParaView Python Shell:
>>
Are you sure that the chart view is the active view when you call
GetDisplayProperties(p)? If the render view is active, you'll get the
wrong representation. I verified that this works for Wavelet --> Plot Data
filter using PV 3.10.1.
Pat
On Thu, Oct 6, 2011 at 2:03 PM, Greg Schussman
wrote:
Hi, Pat.
In the Pipeline Browser, PlotData1 is visible (non-greyed out eye next
to it), and selected (white text on blue background). There's a blue
border around the displayed chart (and not around the 3d view next to it).
When I say
rep.Visibility = 0
Render()
the plot window goes al
Hi, Pat.
I tried plotting directly from the CSVReader, and then it all works.
But when my programmable filter is in between, there's a problem. When
I apply the plot filter (via ParaView's GUI) to my programmable filter,
the plot works fine in the gui, but the GetProperty("SeriesNameInfo")
Hi Greg,
I think I found a bug, or else I don't quite understand what is happening.
It seems that under certain circumstances the python layer fails to wrap all
the properties of a proxy. I look into this, but for now you can work
around the issue by accessing the c++ api:
>>> p = rep.SMProxy.G
Hi, Pat.
On further checking, there's still some sort of problem.
When I use your example below, it works in ParaView's Python Shell, if
the PlotData filter was created via the ParaView gui. However, if it
was created in the macro (using the text from a python trace of how it
was created vi
Hi, Pat.
Here is an example that recreates the problem. Using this as a CSV file:
AAA,BBB,CCC,DDD
0.0,1.0,2.0,3.0
0.0,2.0,4.0,8.0
0.0,3.5,2.5,1.5
and this (modified python trace) as a script run from the python shell
in paraview:
--
Thanks Greg. I can reproduce this. I'm observing the same thing- if the
chart is created by hand, things are ok, but when created via python
commands, not working correctly. I'll investigate the problem. Hopefully
I'll find an easy work around too so that you don't have to wait for the
next rel
10 matches
Mail list logo
