I get:
Delivery to the following recipient failed permanently:
paraview@paraview.org
Technical details of permanent failure:
Google tried to deliver your message, but it was rejected by the relay
outbounds200.obsmtp.com by ou
tbounds200.obsmtp.com. [207.126.147.11].
The error that the
Hi Josh,
I've noticed that the default programmable filters does not advertise that
it handle time. To properly do that you can use the attached XML plugin.
Let us know if that fix the problem.
Seb
On Tue, Oct 28, 2014 at 8:48 PM, Joshua Murphy
joshua.mur...@lasp.colorado.edu wrote:
Hi all,
The Programmable Filter can handle time but it has to be done explicitly.
You'll need to do the proper calls in RequestUpdateExtentScript,
RequestInformationScript and Script. (i.e. RequestData). You can use inInfo
and outInfo to set the required information objections like
UPDATE_TIME_STEP,
Simon,
I am joining a little late to this conversation -- is this addressed yet?
Utkarsh
On Mon, Oct 20, 2014 at 11:57 AM, Su, Simon M CTR USARMY ARL (US)
simon.m.su@mail.mil wrote:
Ben,
Unfortunately, when I checked the CMakeCache.txt in the directory
paraview/src/paraview-build after
That'd work. You can use the benchmark module [1] too to give you info
at a finer granularity.
Utkarsh
[1]
http://www.paraview.org/ParaView3/Doc/Nightly/www/py-doc/paraview.benchmark.html
On Mon, Oct 27, 2014 at 12:12 PM, R C Bording cbord...@ivec.org wrote:
Hi,
Is there a rendering model
Hi Utkarsh,
unfortunately I am still not able to pass both argument into ParaView
superbuild cmake line using the -DPV_EXTRA_CMAKE_ARGS option that Ben
suggested. Any help on this is much appreciated
thanks
-simon
From: Utkarsh Ayachit
Hi all,
I started using Paraview (4.2.0) about a couple months ago and it was working
normally. I don't know exactly when this problem begin because I don't use
Paraview everyday but now when I double click on Paraview.exe, no window pops
up anymore. Using process monitor, I could see that
Try removing your paraview settings.
On windows this should be at:
%APPDATA%\ParaView\ParaView4.2.0.ini
Elsewhere it is at:
~/.config/Paraview/ParaView4.2.0.ini
David E DeMarle
Kitware, Inc.
RD Engineer
21 Corporate Drive
Clifton Park, NY 12065-8662
Phone: 518-881-4909
On Wed, Oct 29, 2014 at
On Mon, Oct 20, 2014 at 15:57:26 +, Su, Simon M CTR USARMY ARL (US) wrote:
Unfortunately, when I checked the CMakeCache.txt in the directory
paraview/src/paraview-build after the cmake ran, I am still finding
Sorry, this email went under my radar.
//Request building vtkIOXdmf3
Thanks for the response, David.
What you suggested did change the symptom a bit. After I remove the ini file, I
was able to see the Paraview logo appear after I execute it, which I did not
see prior to the removal.
However, the window still doesn't show up. Is there anything else I can do?
On Wed, Oct 29, 2014 at 12:36:35 +, Anton Shterenlikht wrote:
Delivery to the following recipient failed permanently:
paraview@paraview.org
Technical details of permanent failure:
Google tried to deliver your message, but it was rejected by the relay
outbounds200.obsmtp.com by ou
Hi.
I have not been able to get PV 4.2.0 to work in stereo interlace mode on my
Windows 7 64 bit system. Default mode seems to be red-blue, and that works
fine, but I get this error on startup when I specify -stereo-type=Interlace
ERROR: In
In ParaView 4.2.0, I have found a few cases where the color legend disappears,
and I can't get it back. Has anyone else seen this, and found a way to
replicate it? Mind passing the voodoo on how to replicate this bug?
Thanks,
Alan
___
Powered by
Jean,
I just tried with PV 4.2.0, Linux Mesa (local server), Linux hardware
rendering, and my local Windows 7 box (Kitware download), and they all worked
with -stereo-type=Interlaced. At least I believe they worked, nothing crashed
and the image looked good. (Note that the command is
David,
The problem is now solved. It appears that ParaView does not work with Python
3? Is this true?
While I tried calling ParaView from Maltab, I got error message like this:
File C:\Python34\Lib\site.py, line 176
file = sys.stderr)
^
SyntaxError:
Glad you got it working.
And yes it is true that ParaView does not yet support Python 3.
David E DeMarle
Kitware, Inc.
RD Engineer
21 Corporate Drive
Clifton Park, NY 12065-8662
Phone: 518-881-4909
On Wed, Oct 29, 2014 at 10:27 PM, Joe chaoy...@yahoo.com wrote:
David,
The problem is now
HI Burlen,
Thanks again. Is there and easy way to verify that Paraview is using the GPU
ours are TESLA C2075?
Should I need to change the MOD(?) setting so it is rendering rather than
compute?
R. Christopher Bording
Supercomputing Team-iVEC@UWA
E: cbord...@ivec.org
T: +61 8 6488 6905
26
Hi Utkarsh,
Is there simple way to see if my installation of ParaView done using the
ParaViewSuperbuild is configure with the correct gl libs to run on the GPUs.
Should I need to install a version with Mesa to benchmark against or is there a
way to that without installing a second version?
18 matches
Mail list logo