Hi Andy,
I can create XMLPPolyDataWriter in pvpython without errors. With a normal
ParaView build as well as with the Rendering-Base-Python edition it works but I
wanted to have a small custom edition.
I am using the next branch from yesterday (79f7fdc).
Best,
Lars
Am 18.08.2014 um 20:39 schr
I just wont to give a feedback about this problem and how I solved it: I've
donwloaded and installed more recent versions:
Mesa-10.2.2 (MesaLib-10.2.2.tar.gz) and ParaView-v4.1.0
(ParaView-v4.1.0-source.tar.gz)
It has requested an update of llvm on my server:
llvm-devel-3.4-10.el6.x86_64
llvm-
Thanks for posting back. Highly appreciated.
Utkarsh
On Tue, Aug 19, 2014 at 3:28 AM, Patrick Begou
wrote:
> I just wont to give a feedback about this problem and how I solved it: I've
> donwloaded and installed more recent versions:
> Mesa-10.2.2 (MesaLib-10.2.2.tar.gz) and ParaView-v4.1.0
> (
Yup, this indeed points to the issue I was alluding do. Andy, feel
free to stop by if you need more info.
Utkarsh
On Tue, Aug 19, 2014 at 3:02 AM, Lars Bilke wrote:
> Hi Andy,
>
> I can create XMLPPolyDataWriter in pvpython without errors. With a normal
> ParaView build as well as with the Rend
Hi guys,
it's probably a simple question, but I can't find any information on the
web (or I don't know where to look for). How do I write (time-dependent)
data in netcdf-4 such that paraview recognizes it as a vector field. I
tried to write it in a single 5-dimensional dataset and also tried t
Hi Lars,
When you tried pvpython and creating an XMLPPolyDataWriter, did you do that
with the pvpython that was built with your custom edition? That's what I
meant before even though I didn't state the explicitly.
Is there a reason you're using the next branch for this? In general you
should use
Hi Andy,
thanks for your efforts!
> When you tried pvpython and creating an XMLPPolyDataWriter, did you do that
> with the pvpython that was built with your custom edition?
Yes.
> Is there a reason you're using the next branch for this?
I also tried the master branch before.
> Another questi
Hi Lars,
Thanks for sticking with this. The Catalyst editions are a bit tricky and
we haven't had enough people testing them out so there's a lot of space for
mistakes so it takes me a bit of effort to try and figure out how to narrow
down where the problem could be. I think I have enough informat
Matthias,
There are several netCDF readers. I think the one most relevant to you is
the one that reads the CF convention, which is the most general. This is
listed as "NetCDF files generic and CF conventions".
Unfortunately, it looks like the CF convention does not specify a
mechanism for definin
Is there a way to get bounding box information via Python? I'd like to
determine the min/max extents of different parts via a script.
Thanks,
Alan
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/op
One thing to be aware of is the additional overhead of ssh compared to
something like ncat or portfwd. ssh encrypts/unencrypts it's data which
adds unnecessary overhead. I ran the 2 ssh tunnel solution at nersc for
a while on Hopper. The performance was noticeably better with ncat which
pipes d
dataInfo = proxy.GetDataInformation()
bounds = dataInfo.DataInformation.GetBounds()
On Tue, Aug 19, 2014 at 12:55 PM, Scott, W Alan wrote:
> Is there a way to get bounding box information via Python? I'd like to
> determine the min/max extents of different parts via a script.
>
> Thanks,
>
> A
>From a user:
I'm trying to create a Python script which will loop through a set of Exodus
block IDs and will output an image for each block. I started the trace and
tried to use the "Zoom to Data" button, but this didn't translate well into the
python script - instead I got a discrete camera v
Thanks, I believe that was what my user is looking for!
Alan
From: Sebastien Jourdain [mailto:sebastien.jourd...@kitware.com]
Sent: Tuesday, August 19, 2014 1:17 PM
To: Scott, W Alan
Cc: paraview@paraview.org
Subject: [EXTERNAL] Re: [Paraview] Bounding box information with python
dataInfo = prox
Alan,
With git/master, it translates to something like this:
renderView1.ResetCamera(-10.0, 10.0, -10.0, 10.0, -10.0, 10.0)
Where the values are indeed the current data bounds. But I think we
can add API to "ZoomTOData" in Python using a data source rather that
current bounds. Feel free to add a
Thanks for the reply, I will let my user know and add a bug.
Alan
-Original Message-
From: Utkarsh Ayachit [mailto:utkarsh.ayac...@kitware.com]
Sent: Tuesday, August 19, 2014 1:56 PM
To: Scott, W Alan
Cc: paraview@paraview.org
Subject: [EXTERNAL] Re: [Paraview] Zoom to data is not correc
I see in coprocessing.py it does:
if view.IsA("vtkSMRenderViewProxy") == True:
view.ResetCamera()
elif view.IsA("vtkSMContextViewProxy") == True:
view.ResetDisplay()
The first is for standard 2D and 3D views an
Thanks!
Sure, you can link it.
Just tell me if you spot some improvements.
Our stand-alone pvsc file does some more automated and rather "dark
magic" to build the described the tunnels up with one click. Its linked
there too.
Axel
On 19.08.2014 05:56, Utkarsh Ayachit wrote:
> Very cool! Thanks
18 matches
Mail list logo