Hello,
Sorry for the delay: too much work!
Le 05/10/2011 00:46, Greg Schussman claviota:
Would you have any idea how to set the focus from python?
Hm, not really. I'll see if I can figure it out, I'll keep you
informed. Not in the coming days, I'm afraid, I'm just about to leave
for a
Hi, Pierre.
Thanks for responding, especially considering your workload.
Best of luck on your mission.
I'll keep looking at this, and will post if I find something or figure
something out.
Greg
On 10/06/2011 01:28 AM, Pierre Chevalier Géologue wrote:
Hello,
Sorry for the delay: too much
Hi Greg,
I may be out of touch with some recent paraview developments, but I have
never seen this behavior before, it sounds like a bug to me. Output from
code that is executed in the python console, which includes python macros,
should always be routed to the python console, not paraview's
For starters, the going to infinity thing in the plot is weird. There should
just be gaps in the curve. You may have hit a bug.
As far as why you are getting nans in the first place I'm not sure. I can't
really tell from your screenshots, but it looks your geometry might be a bunch
of polygons
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:
p =
Hi, Pat.
You're right. When the print comes from inside a programmable filter,
the output goes to the Output Messages, and when I print from the macro,
the output goes to the Python Shell.
I had thought that, within a programmable filter,
print something
was going to the Output
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
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, 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
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
11 matches
Mail list logo
