Hi,
I'm writing a python script for the Programmable Filter of ParaView to
do some analysis on my simulation results. The simulations results are
transient and hence the analysis has to be done over time steps (perhaps
similar to integrate over time filter). All bits of my script are
working fine.
Hi,
I've been experiencing a very weird seg faults in various versions of
ParaView (4.1.x, 4.2.0, 4.3.x) when running an animation (streaming over
time) of my Programmable Filter. I'm not even sure this is a ParaView
issue, but I'll still share my story in case someone has any insights
that they
)
# SetCells of the output with only the selected analyzed cells
output.SetCells(cellTypes, cellArray)
The last line above seg faults on one of my computers but not on the
other one, both using Linux Mint 15 OS, and similar versions of
ParaView. Any thoughts?
On 15-01-28 07:27 PM, Omid Mahabadi
,
Omid
On 14-12-16 05:26 PM, Utkarsh Ayachit wrote:
Check this blog: http://www.kitware.com/blog/home/post/783
It should give you information on what you need to put in the Scripts
for various passes of the filter.
Utkarsh
On Tue, Dec 16, 2014 at 5:12 PM, Omid Mahabadi
omid.mahab
Hi,
I use ParaView to visualize data of our simulations using the Unstructured
Grid data format. Up until ParaView 4.x everything worked fine: we
typically visualize one set of data files as Surfaces and another as
Wireframe. The Wireframe dataset refers to "fracture lines" in our
simulations.
a closer to the camera. Click the broken_joint object and
> add the Transform filter. Change the Translate parameter to 0, 0, 1 and
> apply. That should shift the wireframe forward enough to see it properly.
>
>
>
> -Ken
>
>
>
> *From:* ParaView [mailto:paravi
Thanks Ken. I will try this on other machines. BTW I have version 3.0 of
OpenGL:
$ glxinfo | grep "OpenGL version"
OpenGL version string: 3.0 Mesa 10.5.9
Best regards,
Omid
--
Omid Mahabadi, Ph.D., P.Eng.
President & Geomechanics Specialist
Geomechanica Inc
Suite 900 – 390 Bay S
ing line issue you
> describe. There might be other display/rendering parameters that cause
> issues. But the defaults should be fine, so unless you have done some
> tinkering you should be OK.
>
>
>
> -Ken
>
>
>
> *From:* Omid Mahabadi [mailto:omid.mahab...@geomec
