Hi all,
today I had to reconfigure ParaView for a multiscreen CAVE, and i run
into a problem with the VRPlugin. ParaView compiles and builds properly
with it activated (VRPN and VRUI already tested on the system), but once
i load the plugin comes the problem.
The menu to select the
Emiliano,
Can you send us the SHA of ParaView you are using? We will be doing
some testing today.
Thanks.
- Aashish
On Thu, Mar 21, 2013 at 4:55 AM, Emiliano Pastorelli
hoganc...@gmail.com wrote:
Hi all,
today I had to reconfigure ParaView for a multiscreen CAVE, and i run into a
problem
Hi Aashish,
it's the f59dd55b295c804aa3bb75c6ab19b323ef80d861, the last downloadable
source from the website before the nightly build (that i didn't try yet).
Thanks again,
Best,
Emiliano
Il 21/03/13 14:53, Aashish Chaudhary ha scritto:
Emiliano,
Can you send us the SHA of ParaView you
Hi Emiliano,
I did a quick test and it is working for me. What version of Qt you
are using? Also what OS?
Thanks,
On Thu, Mar 21, 2013 at 9:05 AM, Emiliano Pastorelli
hoganc...@gmail.com wrote:
Hi Aashish,
it's the f59dd55b295c804aa3bb75c6ab19b323ef80d861, the last downloadable
source from
Hi Aashish,
actually it happened on both the actual operating system (Debian Weezy)
and the older one that I still have on another hard disk (Ubuntu 12.10),
and both of them with Qt 4.8.2
Best,
Emiliano
Il 21/03/13 16:07, Aashish Chaudhary ha scritto:
Hi Emiliano,
I did a quick test and
I recently tried using paraview (3.98.0 and 3.98.1) on a new iMac running
mountain lion (10.8.2 originally, now 10.8.3) and the graphics performance is
slower than my old macbook pro laptop (running mac os x 10.7). I tested the
same data file (ply format) on both machines, and the laptop
Hello,
I built Paraview server version 3.14.1 on a HPC cluster with all
co-processing-related flags turned on including enabling co-processing, all
adaptors, and plugins, etc., and built Paraview client/server with no MPI on a
local linux machine with co-processing enabled as well. Then I
On Thu, Mar 21, 2013 at 12:55 PM, Aashish Chaudhary
aashish.chaudh...@kitware.com wrote:
On Thu, Mar 21, 2013 at 11:00 AM, Emiliano Pastorelli
emiliano.pastore...@gmail.com wrote:
Hi Aashish,
actually it happened on both the actual operating system (Debian Weezy)
and
the older one
Thanks Aashish,
on the ubuntu 12.10 system i had temporary solved the problem loading
the VR plugin from a slightly older paraview build i had around, it
worked, but that means that i was still not using all the fixes you made
in the VR plugin, that i would be really interested to test.
Hi
On Thu, Mar 21, 2013 at 11:00 AM, Emiliano Pastorelli
emiliano.pastore...@gmail.com wrote:
Hi Aashish,
actually it happened on both the actual operating system (Debian Weezy) and
the older one that I still have on another hard disk (Ubuntu 12.10), and
both of them with Qt 4.8.2
I see. Let
On Thu, Mar 21, 2013 at 1:01 PM, Emiliano Pastorelli hoganc...@gmail.comwrote:
Thanks Aashish,
on the ubuntu 12.10 system i had temporary solved the problem loading
the VR plugin from a slightly older paraview build i had around, it worked,
but that means that i was still not using all the
I think the problem is that:
Clip1 = Clip( guiName=Clip1, InsideOut=0, Scalars=['POINTS', ''],
Value=95.0, UseValueAsOffset=0, Crinkleclip=0, ClipType=Scalar )
Should probably have the name of the point data field set in it. Do this
with (assuming psi01 is the name of the field you want to clip
Hi Hong,
The live data source that was done with ParaView 3.14 really was just a
demo. It's evolved and has been improved for ParaView 3.98. Not it's in the
Tools-Connect to Catalyst GUI menu.
Catalyst is indeed the evolution of what we called the co-processing tools
in older versions of
Hi Andy,
Changing to Scalars=['POINTS','psi01'] did not change anything. I still get the
same error and blank image.
I tried adding the XMLPImageDataWriter command, but no file 'fullgrid.pvti' was
produced so I can't tell what is being populated into the grid.
I hardwired the C++ adaptor to
Hi Andy,
Many thanks for the useful information. This confirms my suspicion on the live
data source after I see information on catalyst, so I'll just go ahead to
upgrade my development environment to the latest Paraview version 3.98.1 to be
able to leverage catalyst co-processing library for
Did you also include the w.UpdatePipeline() part after the writer was
created? It won't create the file unless that's in there.
Andy
On Thu, Mar 21, 2013 at 3:17 PM, Pettey . Lucas lpet...@drc.com wrote:
Hi Andy,
Changing to Scalars=['POINTS','psi01'] did not change anything. I still
get
I'm working on a Catalyst Users Guide that should cover everything you
need. It will probably be ready in a couple of weeks. I'll post to the
paraview list when it's ready and where to download at.
Andy
On Thu, Mar 21, 2013 at 3:17 PM, Hong Yi hon...@renci.org wrote:
Hi Andy,
** **
Yes I did. I have attached the latest script.
Thank you for your valiant efforts in trying to solve this problem.
Lucas
From: Andy Bauer [andy.ba...@kitware.com]
Sent: Thursday, March 21, 2013 2:22 PM
To: Pettey . Lucas
Cc: paraview [paraview@paraview.org]
Hmm, how about trying replacing those two lines with:
ParallelImageDataWriter1 = CreateCPWriter( XMLPImageDataWriter,
fullgrid_%t.pvti, 1, cp_writers )
Let me know how that goes.
If not, I think we'll need to put some print statements in there.
Andy
On Thu, Mar 21, 2013 at 3:31 PM, Pettey
Sorry, Andy, that didn't seem to work either.
Let me know what information would be useful to print.
Thanks
Lucas
From: Andy Bauer [andy.ba...@kitware.com]
Sent: Thursday, March 21, 2013 2:36 PM
To: Pettey . Lucas
Cc: paraview [paraview@paraview.org]
Subject:
How about trying:
psi01_.UpdatePipeline()
print psi01_.GetDataInformation().DataInformation.GetNumberOfPoints()
right about where the writer was created. This will give print out the
number of points in the data set that you have.
Andy
On Thu, Mar 21, 2013 at 3:47 PM, Pettey . Lucas
Nothing printed at all.
Does anything special have to be done during the compile/link steps for the
python script to work properly?
Thanks,
Lucas
From: Andy Bauer [andy.ba...@kitware.com]
Sent: Thursday, March 21, 2013 3:00 PM
To: Pettey . Lucas
Cc: paraview
Dear list,
Forgive me being obtuse. I am attempting to integrate a scalar variable,
defined on an unstructed mesh, over a volume. I'm aware of the limitations
of the present IntegrateVariables filter: it can only integrate over lines
and surfaces, not volumes.
However, it seems that VTK has a
Also something weird that I have noted.
The Initialize Helper Script line prints twice when I run the Fortran code
and no print statements anywhere in my Python script execute (not even if they
are at the top).
When I run the C++ example located here:
Hi,
I have numpy installed installed on Python 2.7.3. for Mac OS 10.8.3. I
compiled against the same python while building ParaView 3.98.1 64-bit, but
when I create a Python programmable filter in ParaView, I cannot import
numpy -- I get a message that says ImportError: No module named numpy.
Run python from terminal and import numpy. Does that work? If so,
import sys and print sys.path. Now try the same in Python shell from
ParaView. Does that work? If not, compare the sys.path from python and
ParaView's Python shell. Any differences?
On Thu, Mar 21, 2013 at 8:53 PM, Sohail Shafii
Hi,
So I got python2.7 working and I set all the variables correctly like you
advised but I still get errors. When I try to run a saved trace using
python, I get the following errors.
b8-8d-12-38-84-40:Python chukwudichukwudozie$ python trace.py
Traceback (most recent call last):
File
Importing numpy into python works. Same with import sys.path.
What's interesting is that ParaView uses python stored in /usr/local/ while
the version of Python that I use (i.e. default python from the terminal)
resides in /Library/Frameworks. The one in /usr/local does not have numpy.
I didn't
28 matches
Mail list logo
