Hi all,
I switched from Paraview 3.12.0 to 3.14.1 Linux 64-bit and have the following
error:
Traceback (most recent call last):
File string, line 6, in module
TypeError: 'GradientOfUnstructuredDataSet' object is not callable
when I try to take the gradients of the velocity by calling:
Sorry, in the e-mail I misspelled it. I do use:
GradientOfUnstructuredDataSet()
as the error indicates; it is not related to the spelling. After I sent out the
first e-mail I tried Paraview 3.14.0 Linux 64-bit and it works, so for what I
need this is fine. I think it is a bug that needs to be
In general to access the real data, use the python programmable
filter, which executes on the server where the data exists, to access
the data array contents. See the wiki for examples.
If the data is small, use servermanager.Fetch in the python shell to
copy the data from the server to the
See http://markmail.org/thread/cs2uogvlpz7gaewx for a discussion of
the lack of infovis capabilities and ParaView.
The short story is that no, there are no plans, but Sandia is working
on a project called OpenView which most likely will have this and
other new infovis views in it.
David E
Hi,
I have modified the git-next version of the CTH reader to be smarter when
trying to compute derived variables. If no materials exist it will not
generate a derived density property.
On Tue, Aug 7, 2012 at 5:21 PM, B A bra...@gatech.edu wrote:
That did the trick. Thank you.
Bradya
On
Thanks Burlen. It turned out that VTK_USE_X was still ON. It worked fine
otherwise. I'm now able to execute a script file with pvpython offscreen.
ganesh
On Tue, Aug 7, 2012 at 1:49 PM, Burlen Loring blor...@lbl.gov wrote:
**
Hi Ganesh,
your error log indicates that x11 support is being
hi!
I recently installed paraview 3.12 with offscreen mesa on a SGI cluster
with intel compilers and SGI MPT. Using the same version of paraview on my
local computer I recorded a script in the qt version using python trace. I
was able to execute the same script just fine on the cluster on a
John,
I have been having difficulty finding anyone who knows much about POE
here. But looking at the error, it looks like pvserver is failing to
opening up a server-socket to which the paraview clients are expected
to connect and this is independent of MPI. Try using pvbatch/pvpython.
Do they
Hi Ganesh,
Sig 9 usually means your job was killed by the system. Is it possible
that you have exhausted the available ram or hit some artificial limit
that is imposed by your batch system?
Burlen
On 08/08/2012 01:15 PM, Ganesh Vijayakumar wrote:
hi!
I recently installed paraview 3.12
On Wed, Aug 8, 2012 at 5:02 PM, Burlen Loring blor...@lbl.gov wrote:
**
Hi Ganesh,
Sig 9 usually means your job was killed by the system. Is it possible that
you have exhausted the available ram or hit some artificial limit that is
imposed by your batch system?
I can't think of any right
assuming that you've already examined all the output, and there's no
other info, you could do a couple of things: put some print statements
in your python script to see how far it makes it. Also you could use MPT
specific environment variables that tell mpt to print a stack trace, see
man mpi.
On Aug 8, 2012, at 2:18 PM, Utkarsh Ayachit wrote:
John,
I have been having difficulty finding anyone who knows much about POE
here. But looking at the error, it looks like pvserver is failing to
opening up a server-socket to which the paraview clients are expected
to connect and this is
12 matches
Mail list logo
