From rajphysics.mon at gmail.com  Fri Apr  1 00:27:59 2016
From: rajphysics.mon at gmail.com (Raj Kumar Manna)
Date: Fri, 1 Apr 2016 09:57:59 +0530
Subject: [Paraview] Paraview ray tracing plugin | OSPray
Message-ID: <CANt3wQuxvUbiOLOu9pyMqvp2XduM31yKFth_bv2bFOCWGMPMCQ@mail.gmail.com>

Dear All,

I came to know the ray tracing plugin for Paraview -OSPray. Is there any
documentation for this plugin, like we have one for Surface-LIC
<http://www.paraview.org/Wiki/ParaView/Line_Integral_Convolution>? I can
load the plugin in my paraview 5.0 but could not figure out how to use it.

Thanks your help.
Raj



-- 
##################################################################
Raj Kumar Manna
Complex Fluid & Biological Physics Lab
IIT Madras

Ph. No. 8144637401

alternate email: raj at physics.iitm.ac.in <rajphysics.mon at gmail.com>
####################################################################
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160401/02902534/attachment.html>

From antech777 at gmail.com  Fri Apr  1 02:01:26 2016
From: antech777 at gmail.com (Andrew)
Date: Fri, 1 Apr 2016 09:01:26 +0300
Subject: [Paraview] paraview quits when run through Windows Remote
	Desktop
In-Reply-To: <CADHSJjDgDR7Wp006eXeBamYyS1N094DDkpSf3Y8YcyYS4tGk+w@mail.gmail.com>
References: <20160401004358.Horde.hmhDoSJ9zYqRq2y_Z57pWw1@192.168.1.14>
 <CADHSJjDgDR7Wp006eXeBamYyS1N094DDkpSf3Y8YcyYS4tGk+w@mail.gmail.com>
Message-ID: <CANMVBVzQ_GSuYm3__9cF4toYZaiszwVhU+K=ogk-cPFK=Q_Kpw@mail.gmail.com>

Sorry for small offtopic, but I didn't notice any remote access issues with
ParaView 5.0.1 RC2 on Windows 7 x64, but I use Linux client (FreeRDP 1.0.2).

2016-04-01 4:58 GMT+03:00 Utkarsh Ayachit <utkarsh.ayachit at kitware.com>:

> You cannot use ParaVIew 5.0 or later over remote desktop anymore.
> ParaView now needs newer OpenGL (3.2 or later) and remote desktop uses
> software OpenGL implementation that only supports OpenGL 1.1. It may
> be possible to build Mesa3D (http://www.mesa3d.org/) on Windows, but I
> personally don't have much experience with Mesa3D on Windows. Maybe
> someone else can chime in.
>
> Utkarsh
>
> On Thu, Mar 31, 2016 at 8:43 PM, Chris Fisichella
> <chris at communityrenewables.com> wrote:
> > Hi,
> >
> > Paraview "started crashing" recently. It was because I switched to
> trying to
> > use it over Windows remote desktop.
> >
> > FYI,
> > Chris
> >
> >
> > _______________________________________________
> > Powered by www.kitware.com
> >
> > Visit other Kitware open-source projects at
> > http://www.kitware.com/opensource/opensource.html
> >
> > Please keep messages on-topic and check the ParaView Wiki at:
> > http://paraview.org/Wiki/ParaView
> >
> > Search the list archives at: http://markmail.org/search/?q=ParaView
> >
> > Follow this link to subscribe/unsubscribe:
> > http://public.kitware.com/mailman/listinfo/paraview
> >
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160401/0d71c57e/attachment.html>

From cindy.castro at uvsq.fr  Fri Apr  1 04:06:04 2016
From: cindy.castro at uvsq.fr (Cindy Castro)
Date: Fri, 1 Apr 2016 10:06:04 +0200
Subject: [Paraview] Background in 3D mode
In-Reply-To: <56EADA83.6050104@uvsq.fr>
References: <56EADA83.6050104@uvsq.fr>
Message-ID: <56FE2BEC.2030702@uvsq.fr>

Hello,

I am using ParaView in client/server mode with stereo. I have a cluster 
with 4 nodes, 1 GPU each (NVIDIA K5000) and 8 screens for display.

My problem is I can not find how to span a background over my 8 screens. 
The background is displayed on each screen. 3D models are well displayed 
in 3D (no problem with that).

The server is run with the command:
mpirun -np 8 -machinefile 
/opt/software/ParaView/PVscripts/server_machinefile.txt 
/opt/software/ParaView/ParaView-5.0.0-bin/bin/pvserver -rc 
--client-host=mire-pc /opt/software/ParaView/PVresources/wall_config.pvx

I tried tiles mode but the display is not in the right order...

Can you help me ? Is it possible to span a background over several 
screens in 3D mode ? I is really useful when rendering.

Regards,

-- 
Cindy CASTRO
Responsable plateforme DIGISCOPE-MIRE
Plateforme d'Int?gration et de Tests (PIT)
-- 
Observatoire de Versailles Saint-Quentin-en-Yvelines (OVSQ)
Quartier des Garennes
11 Boulevard d'Alembert
78280 Guyancourt
-- 
B?timent principal - RDC - Bureau 215
T?l : +33 (0)1 80 28 51 03
Salle MIRE : +33 (0)1 80 28 54 93


---
L'absence de virus dans ce courrier ?lectronique a ?t? v?rifi?e par le logiciel antivirus Avast.
https://www.avast.com/antivirus


From utkarsh.ayachit at kitware.com  Fri Apr  1 08:15:08 2016
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Fri, 1 Apr 2016 08:15:08 -0400
Subject: [Paraview] paraview quits when run through Windows Remote
	Desktop
In-Reply-To: <CANMVBVzQ_GSuYm3__9cF4toYZaiszwVhU+K=ogk-cPFK=Q_Kpw@mail.gmail.com>
References: <20160401004358.Horde.hmhDoSJ9zYqRq2y_Z57pWw1@192.168.1.14>
 <CADHSJjDgDR7Wp006eXeBamYyS1N094DDkpSf3Y8YcyYS4tGk+w@mail.gmail.com>
 <CANMVBVzQ_GSuYm3__9cF4toYZaiszwVhU+K=ogk-cPFK=Q_Kpw@mail.gmail.com>
Message-ID: <CADHSJjDpu6639afJiH6asijnofO3osMGMMLsjh9aaWtsksep+w@mail.gmail.com>

> Sorry for small offtopic, but I didn't notice any remote access issues with
> ParaView 5.0.1 RC2 on Windows 7 x64, but I use Linux client (FreeRDP 1.0.2).

That's curious. Can you post the OpenGL information the About dialog reports?

From antech777 at gmail.com  Fri Apr  1 08:28:52 2016
From: antech777 at gmail.com (Andrew)
Date: Fri, 1 Apr 2016 15:28:52 +0300
Subject: [Paraview] paraview quits when run through Windows Remote
	Desktop
In-Reply-To: <CADHSJjDpu6639afJiH6asijnofO3osMGMMLsjh9aaWtsksep+w@mail.gmail.com>
References: <20160401004358.Horde.hmhDoSJ9zYqRq2y_Z57pWw1@192.168.1.14>
 <CADHSJjDgDR7Wp006eXeBamYyS1N094DDkpSf3Y8YcyYS4tGk+w@mail.gmail.com>
 <CANMVBVzQ_GSuYm3__9cF4toYZaiszwVhU+K=ogk-cPFK=Q_Kpw@mail.gmail.com>
 <CADHSJjDpu6639afJiH6asijnofO3osMGMMLsjh9aaWtsksep+w@mail.gmail.com>
Message-ID: <CANMVBVzvq_Xfxq_wZJP_hV8jxLVDvmKbqgn=nc04WFDpmniJBA@mail.gmail.com>

Yes, I hope this is what you want.

2016-04-01 15:15 GMT+03:00 Utkarsh Ayachit <utkarsh.ayachit at kitware.com>:

> > Sorry for small offtopic, but I didn't notice any remote access issues
> with
> > ParaView 5.0.1 RC2 on Windows 7 x64, but I use Linux client (FreeRDP
> 1.0.2).
>
> That's curious. Can you post the OpenGL information the About dialog
> reports?
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160401/f396831e/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ParaViewOpenGL.png
Type: image/png
Size: 13290 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160401/f396831e/attachment.png>

From lloyd_brown at byu.edu  Fri Apr  1 10:14:51 2016
From: lloyd_brown at byu.edu (Lloyd Brown)
Date: Fri, 1 Apr 2016 08:14:51 -0600
Subject: [Paraview] [EXTERNAL] BadAlloc Error
In-Reply-To: <CAMaOp+H5cTeuzX2Knkp74EwgJgcRUm9uY=31HjMqnVRuHLKZcw@mail.gmail.com>
References: <56FC2AC3.80005@byu.edu>
 <08f4db1652984533ae06c4a99664e7d2@ES01AMSNLNT.srn.sandia.gov>
 <56FD35D3.8030904@byu.edu>
 <CADHSJjCjsfLpLk1htOnAZ7HBC4Jx2AiEabNRS9a7wKvUWtft+g@mail.gmail.com>
 <CAMaOp+H5cTeuzX2Knkp74EwgJgcRUm9uY=31HjMqnVRuHLKZcw@mail.gmail.com>
Message-ID: <56FE825B.1070600@byu.edu>

I'll forward this on to our software guy.  I know he's built a previous
version using OSMesa, but I think he was trying to avoid it this time. 

Thanks for hte information.

On 03/31/2016 09:10 PM, Andy Bauer wrote:
> Hi Lloyd,
>
> If you've built ParaView yourself in the past then doing it with EGL
> support shouldn't be any more difficult. The link that Utkarsh sent
> out covers most if not all of the necessary information. I'll
> highlight the fact though that you'll need to update your NVIDIA
> drivers to at least 355.11. The dashboard that's testing ParaView with
> EGL is running 358.13.
>
> If you're building 5.0 or 5.0.1 it may not have the newest stuff for
> easily finding EGL libraries. For reference, on our EGL dashboard
> machine the location that the default NVIDIA driver install puts the
> EGL libraries and header files are:
>  EGL_INCLUDE_DIR                  /usr/include
>  EGL_LIBRARY                      /usr/lib/x86_64-linux-gnu/libEGL.so
>  EGL_gldispatch_LIBRARY          
> /usr/lib/x86_64-linux-gnu/libGLdispatch.so.0
>  EGL_opengl_LIBRARY               /usr/lib/x86_64-linux-gnu/libOpenGL.so
>
> Please let us know if you have any problems.
>
> Best,
> Andy
>
> On Thu, Mar 31, 2016 at 4:51 PM, Utkarsh Ayachit
> <utkarsh.ayachit at kitware.com <mailto:utkarsh.ayachit at kitware.com>> wrote:
>
>     Lloyd,
>
>     For a headless server with K80s, you cannot use binaries distributed
>     from paraview.org <http://paraview.org>. I'd suggesting building
>     ParaView from source with
>     EGL support (refer to
>     https://blog.kitware.com/off-screen-rendering-through-the-native-platform-interface-egl/).
>
>     Andy, can you point Lloyd to any addition ParaVIew + EGL build
>     information that may be useful? Thanks
>
>     Utkarsh
>
>
>     On Thu, Mar 31, 2016 at 10:36 AM, Lloyd Brown <lloyd_brown at byu.edu
>     <mailto:lloyd_brown at byu.edu>> wrote:
>     > Well....not exactly.  Just for clarification, this is running
>     pvserver,
>     > with a completely headless Xorg instance.  I'm then connecting my
>     > desktop's Paraview frontend instance to it over (presumably) a TCP
>     > socket.  I'm not actually using SSH x11 forwarding, in this case.
>     >
>     > But to answer your other question, here's the similar info from
>     my setup:
>     >
>     >> bash-4.1$ DISPLAY=:0.0 glxinfo | grep OpenGL
>     >> OpenGL vendor string: NVIDIA Corporation
>     >> OpenGL renderer string: Tesla K80/PCIe/SSE2
>     >> OpenGL version string: 4.5.0 NVIDIA 352.79
>     >> OpenGL shading language version string: 4.50 NVIDIA
>     >> OpenGL extensions:
>     >> bash-4.1$
>     >
>     > So, if I'm interpreting that right, I should be able up to
>     handle OpenGL
>     > v4.5.0.
>     >
>     > Lloyd
>     >
>     >
>     > On 03/30/2016 08:25 PM, Scott, W Alan wrote:
>     >> Lloyd,
>     >> I see the same thing,  ... um ... sort of.  Mine occurs when
>     ssh -X'ing into a remote blade.  New ParaView (i.e., 5.0.0 and
>     later) needs OpenGL 3.2.  I suspect that X forwarding isn't
>     supporting OpenGL 3.2.
>     >>
>     >> If I log onto the blade directly, the OGL version is
>     sufficient.  But, when ssh -X'ing into it, if I do a "glxinfo |
>     grep OpenGL", three of the lines will say
>     >>
>     >> OpenGL vendor string: NVIDIA Corporation
>     >> OpenGL renderer string: Quadro 3000M/PCIe/SSE2
>     >> OpenGL version string: 2.1.2 NVIDIA 337.25
>     >>
>     >> I wonder if you aren't seeing the same thing?
>     >>
>     >>
>     >> -----Original Message-----
>     >> From: ParaView [mailto:paraview-bounces at paraview.org
>     <mailto:paraview-bounces at paraview.org>] On Behalf Of Lloyd Brown
>     >> Sent: Wednesday, March 30, 2016 1:37 PM
>     >> To: paraview at paraview.org <mailto:paraview at paraview.org>
>     >> Subject: [EXTERNAL] [Paraview] BadAlloc Error
>     >>
>     >> Hi, all.
>     >>
>     >> I'm trying to get Paraview 5.0 to interact well with the Tesla
>     k80 GPUs in my HPC lab, and I'm encountering an interesting
>     error.  I'm hoping that someone can point me in the right
>     direction to diagnose it.
>     >>
>     >> So, on an HPC node, with some k80s installed, I'm launching
>     Xorg (example config attached) as root, then launching pvserver
>     >> ("DISPLAY=:0.0 pvserver") as my user.  Then when I try to
>     connect from the Paraview frontend on my desktop, pvserver exits
>     with this error:
>     >>
>     >>> Waiting for client...
>     >>> Connection URL: cs://m8g-1-5:11111
>     >>> Accepting connection(s): m8g-1-5:11111 Client connected.
>     >>> X Error of failed request:  BadAlloc (insufficient resources for
>     >>> operation)
>     >>>   Major opcode of failed request:  135 (GLX)
>     >>>   Minor opcode of failed request:  34 ()
>     >>>   Serial number of failed request:  26
>     >>>   Current serial number in output stream:  27
>     >> Now, according to the guys on the xorg users list
>     (https://lists.x.org/archives/xorg/2016-March/057984.html), this
>     is occurring as a result of the glXCreateContextAttribsARB call
>     getting denied resources somehow, which lines up with the
>     backtrace from gdb (also attached).
>     >>
>     >> Now, under the assumption that pvserver was somehow running out
>     of memory, I've verified that the problem still occurs when my HPC
>     job requests 64GB (which means the cgroup will limit me to that).
>     >>
>     >> Since both the client and server are precompiled 5.0 binaries
>     from paraview.org <http://paraview.org>, I'm not entirely sure
>     where to go here.  Can anyone shed any insight on what might be
>     going on?  A misconfiguration in my Xorg config?  Some software
>     package I'm missing?
>     >>
>     >> It's worth noting that several GLX-based benchmarks (eg.
>     glxgears, glxspheres64, glmark2) and utilities (eg. glxinfo,
>     glewinfo) seem to be able to interact with the Xorg just fine.
>     >>
>     >> Thanks,
>     >>
>     >> --
>     >> Lloyd Brown
>     >> Systems Administrator
>     >> Fulton Supercomputing Lab
>     >> Brigham Young University
>     >> http://marylou.byu.edu
>     >>
>     >
>     > --
>     > Lloyd Brown
>     > Systems Administrator
>     > Fulton Supercomputing Lab
>     > Brigham Young University
>     > http://marylou.byu.edu
>     >
>     > _______________________________________________
>     > Powered by www.kitware.com <http://www.kitware.com>
>     >
>     > Visit other Kitware open-source projects at
>     http://www.kitware.com/opensource/opensource.html
>     >
>     > Please keep messages on-topic and check the ParaView Wiki at:
>     http://paraview.org/Wiki/ParaView
>     >
>     > Search the list archives at: http://markmail.org/search/?q=ParaView
>     >
>     > Follow this link to subscribe/unsubscribe:
>     > http://public.kitware.com/mailman/listinfo/paraview
>
>

-- 
Lloyd Brown
Systems Administrator
Fulton Supercomputing Lab
Brigham Young University
http://marylou.byu.edu

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160401/f9417e1b/attachment.html>

From lloyd_brown at byu.edu  Fri Apr  1 10:21:35 2016
From: lloyd_brown at byu.edu (Lloyd Brown)
Date: Fri, 1 Apr 2016 08:21:35 -0600
Subject: [Paraview] [EXTERNAL] BadAlloc Error
In-Reply-To: <CAMaOp+H5cTeuzX2Knkp74EwgJgcRUm9uY=31HjMqnVRuHLKZcw@mail.gmail.com>
References: <56FC2AC3.80005@byu.edu>
 <08f4db1652984533ae06c4a99664e7d2@ES01AMSNLNT.srn.sandia.gov>
 <56FD35D3.8030904@byu.edu>
 <CADHSJjCjsfLpLk1htOnAZ7HBC4Jx2AiEabNRS9a7wKvUWtft+g@mail.gmail.com>
 <CAMaOp+H5cTeuzX2Knkp74EwgJgcRUm9uY=31HjMqnVRuHLKZcw@mail.gmail.com>
Message-ID: <56FE83EF.2040808@byu.edu>

On 03/31/2016 09:10 PM, Andy Bauer wrote:
> I'll highlight the fact though that you'll need to update your NVIDIA
> drivers to at least 355.11. The dashboard that's testing ParaView with
> EGL is running 358.13.

When I go to nvidia.com, and search for Linux drivers for the k80, it's
showing me v352.79.  Are these other versions testing/beta releases or
something?



-- 
Lloyd Brown
Systems Administrator
Fulton Supercomputing Lab
Brigham Young University
http://marylou.byu.edu


From andy.bauer at kitware.com  Fri Apr  1 11:02:06 2016
From: andy.bauer at kitware.com (Andy Bauer)
Date: Fri, 1 Apr 2016 11:02:06 -0400
Subject: [Paraview] [EXTERNAL] BadAlloc Error
In-Reply-To: <56FE83EF.2040808@byu.edu>
References: <56FC2AC3.80005@byu.edu>
 <08f4db1652984533ae06c4a99664e7d2@ES01AMSNLNT.srn.sandia.gov>
 <56FD35D3.8030904@byu.edu>
 <CADHSJjCjsfLpLk1htOnAZ7HBC4Jx2AiEabNRS9a7wKvUWtft+g@mail.gmail.com>
 <CAMaOp+H5cTeuzX2Knkp74EwgJgcRUm9uY=31HjMqnVRuHLKZcw@mail.gmail.com>
 <56FE83EF.2040808@byu.edu>
Message-ID: <CAMaOp+F=7w7G6geEnGGOVapR52kjOMH7jAcBnQtQuq0HK-oeTg@mail.gmail.com>

Hi Lloyd,


Based on feedback from NVIDIA regarding the driver: they suggest you wait
until mid next week, some things will change significantly.

It _looks_ like the 361 version should become a Tesla driver. NVIDIA does a
significant amount of testing on the Tesla drivers so their release cycle
isn't quite as often as their regular GPU cards. I think it was the 358.16
drivers that I've tried on the K40P cards and didn't have any issues but I
don't know how your sys-admins feel about installing drivers which aren't
officially supported on the K80s. If you don't use them, you'll then want
361.33 or newer driver.


Best,

Andy

On Fri, Apr 1, 2016 at 10:21 AM, Lloyd Brown <lloyd_brown at byu.edu> wrote:

> On 03/31/2016 09:10 PM, Andy Bauer wrote:
> > I'll highlight the fact though that you'll need to update your NVIDIA
> > drivers to at least 355.11. The dashboard that's testing ParaView with
> > EGL is running 358.13.
>
> When I go to nvidia.com, and search for Linux drivers for the k80, it's
> showing me v352.79.  Are these other versions testing/beta releases or
> something?
>
>
>
> --
> Lloyd Brown
> Systems Administrator
> Fulton Supercomputing Lab
> Brigham Young University
> http://marylou.byu.edu
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160401/db43f7cb/attachment.html>

From joachim.pouderoux at kitware.com  Fri Apr  1 11:10:15 2016
From: joachim.pouderoux at kitware.com (Joachim Pouderoux)
Date: Fri, 1 Apr 2016 17:10:15 +0200
Subject: [Paraview] Background in 3D mode
In-Reply-To: <56FE2BEC.2030702@uvsq.fr>
References: <56EADA83.6050104@uvsq.fr> <56FE2BEC.2030702@uvsq.fr>
Message-ID: <CACJ=gTjTvHLnGvd7w3LVY4zPufCauj_ZDKv1-aZSRr=qJfC3wA@mail.gmail.com>

Hi Cindy,

Not totally sure to understand - are you trying to apply an Image or
Gradient background and would like it to be correctly split over the
different screen? If so, I am afraid this feature is not supported.

Best,
Joachim

*Joachim Pouderoux*

*PhD, Technical Expert*
*Kitware SAS <http://www.kitware.fr>*


2016-04-01 10:06 GMT+02:00 Cindy Castro <cindy.castro at uvsq.fr>:

> Hello,
>
> I am using ParaView in client/server mode with stereo. I have a cluster
> with 4 nodes, 1 GPU each (NVIDIA K5000) and 8 screens for display.
>
> My problem is I can not find how to span a background over my 8 screens.
> The background is displayed on each screen. 3D models are well displayed in
> 3D (no problem with that).
>
> The server is run with the command:
> mpirun -np 8 -machinefile
> /opt/software/ParaView/PVscripts/server_machinefile.txt
> /opt/software/ParaView/ParaView-5.0.0-bin/bin/pvserver -rc
> --client-host=mire-pc /opt/software/ParaView/PVresources/wall_config.pvx
>
> I tried tiles mode but the display is not in the right order...
>
> Can you help me ? Is it possible to span a background over several screens
> in 3D mode ? I is really useful when rendering.
>
> Regards,
>
> --
> Cindy CASTRO
> Responsable plateforme DIGISCOPE-MIRE
> Plateforme d'Int?gration et de Tests (PIT)
> --
> Observatoire de Versailles Saint-Quentin-en-Yvelines (OVSQ)
> Quartier des Garennes
> 11 Boulevard d'Alembert
> 78280 Guyancourt
> --
> B?timent principal - RDC - Bureau 215
> T?l : +33 (0)1 80 28 51 03
> Salle MIRE : +33 (0)1 80 28 54 93
>
>
> ---
> L'absence de virus dans ce courrier ?lectronique a ?t? v?rifi?e par le
> logiciel antivirus Avast.
> https://www.avast.com/antivirus
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160401/d69b5c11/attachment.html>

From lloyd_brown at byu.edu  Fri Apr  1 11:31:37 2016
From: lloyd_brown at byu.edu (Lloyd Brown)
Date: Fri, 1 Apr 2016 09:31:37 -0600
Subject: [Paraview] [EXTERNAL] BadAlloc Error
In-Reply-To: <CAMaOp+F=7w7G6geEnGGOVapR52kjOMH7jAcBnQtQuq0HK-oeTg@mail.gmail.com>
References: <56FC2AC3.80005@byu.edu>
 <08f4db1652984533ae06c4a99664e7d2@ES01AMSNLNT.srn.sandia.gov>
 <56FD35D3.8030904@byu.edu>
 <CADHSJjCjsfLpLk1htOnAZ7HBC4Jx2AiEabNRS9a7wKvUWtft+g@mail.gmail.com>
 <CAMaOp+H5cTeuzX2Knkp74EwgJgcRUm9uY=31HjMqnVRuHLKZcw@mail.gmail.com>
 <56FE83EF.2040808@byu.edu>
 <CAMaOp+F=7w7G6geEnGGOVapR52kjOMH7jAcBnQtQuq0HK-oeTg@mail.gmail.com>
Message-ID: <56FE9459.8000005@byu.edu>

Well, I am the SysAdmin.  I do generally try to avoid non-certified
drivers for things as specialized as GPUs, but there should be no
problem waiting until next week.

Thanks,

Lloyd

On 04/01/2016 09:02 AM, Andy Bauer wrote:
>
> Hi Lloyd,
>
>
> Based on feedback from NVIDIA regarding the driver: they suggest you
> wait until mid next week, some things will change significantly.
>
> It _looks_ like the 361 version should become a Tesla driver. NVIDIA
> does a significant amount of testing on the Tesla drivers so their
> release cycle isn't quite as often as their regular GPU cards. I think
> it was the 358.16 drivers that I've tried on the K40P cards and didn't
> have any issues but I don't know how your sys-admins feel about
> installing drivers which aren't officially supported on the K80s. If
> you don't use them, you'll then want  361.33 or newer driver.
>
>
> Best,
>
> Andy
>
>
> On Fri, Apr 1, 2016 at 10:21 AM, Lloyd Brown <lloyd_brown at byu.edu
> <mailto:lloyd_brown at byu.edu>> wrote:
>
>     On 03/31/2016 09:10 PM, Andy Bauer wrote:
>     > I'll highlight the fact though that you'll need to update your NVIDIA
>     > drivers to at least 355.11. The dashboard that's testing
>     ParaView with
>     > EGL is running 358.13.
>
>     When I go to nvidia.com <http://nvidia.com>, and search for Linux
>     drivers for the k80, it's
>     showing me v352.79.  Are these other versions testing/beta releases or
>     something?
>
>
>
>     --
>     Lloyd Brown
>     Systems Administrator
>     Fulton Supercomputing Lab
>     Brigham Young University
>     http://marylou.byu.edu
>
>

-- 
Lloyd Brown
Systems Administrator
Fulton Supercomputing Lab
Brigham Young University
http://marylou.byu.edu

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160401/d4c73642/attachment.html>

From dave.demarle at kitware.com  Fri Apr  1 11:55:25 2016
From: dave.demarle at kitware.com (David E DeMarle)
Date: Fri, 1 Apr 2016 11:55:25 -0400
Subject: [Paraview] Background in 3D mode
In-Reply-To: <CACJ=gTjTvHLnGvd7w3LVY4zPufCauj_ZDKv1-aZSRr=qJfC3wA@mail.gmail.com>
References: <56EADA83.6050104@uvsq.fr> <56FE2BEC.2030702@uvsq.fr>
 <CACJ=gTjTvHLnGvd7w3LVY4zPufCauj_ZDKv1-aZSRr=qJfC3wA@mail.gmail.com>
Message-ID: <CANjZAi9xRGmn=PJPfAn_Ne4+S1fhfw3WAY2-FDg13wOP9Jzu4w@mail.gmail.com>

Cindy,

I can't remember which mode, tile or cave, doesn't support tile and
gradient background. But from what you and Joachim say it must be cave.

You should aim for tile mode then. You can enforce and thus correct the
ordering problem you see  with tile mode with your mpirun command and the
your cave.pvx file. Can you share your
/opt/software/ParaView/PVresources/wall_config.pvx? So I can suggest a fix?

thanks


David E DeMarle
Kitware, Inc.
R&D Engineer
21 Corporate Drive
Clifton Park, NY 12065-8662
Phone: 518-881-4909

On Fri, Apr 1, 2016 at 11:10 AM, Joachim Pouderoux <
joachim.pouderoux at kitware.com> wrote:

> Hi Cindy,
>
> Not totally sure to understand - are you trying to apply an Image or
> Gradient background and would like it to be correctly split over the
> different screen? If so, I am afraid this feature is not supported.
>
> Best,
> Joachim
>
> *Joachim Pouderoux*
>
> *PhD, Technical Expert*
> *Kitware SAS <http://www.kitware.fr>*
>
>
> 2016-04-01 10:06 GMT+02:00 Cindy Castro <cindy.castro at uvsq.fr>:
>
>> Hello,
>>
>> I am using ParaView in client/server mode with stereo. I have a cluster
>> with 4 nodes, 1 GPU each (NVIDIA K5000) and 8 screens for display.
>>
>> My problem is I can not find how to span a background over my 8 screens.
>> The background is displayed on each screen. 3D models are well displayed in
>> 3D (no problem with that).
>>
>> The server is run with the command:
>> mpirun -np 8 -machinefile
>> /opt/software/ParaView/PVscripts/server_machinefile.txt
>> /opt/software/ParaView/ParaView-5.0.0-bin/bin/pvserver -rc
>> --client-host=mire-pc /opt/software/ParaView/PVresources/wall_config.pvx
>>
>> I tried tiles mode but the display is not in the right order...
>>
>> Can you help me ? Is it possible to span a background over several
>> screens in 3D mode ? I is really useful when rendering.
>>
>> Regards,
>>
>> --
>> Cindy CASTRO
>> Responsable plateforme DIGISCOPE-MIRE
>> Plateforme d'Int?gration et de Tests (PIT)
>> --
>> Observatoire de Versailles Saint-Quentin-en-Yvelines (OVSQ)
>> Quartier des Garennes
>> 11 Boulevard d'Alembert
>> 78280 Guyancourt
>> --
>> B?timent principal - RDC - Bureau 215
>> T?l : +33 (0)1 80 28 51 03
>> Salle MIRE : +33 (0)1 80 28 54 93
>>
>>
>> ---
>> L'absence de virus dans ce courrier ?lectronique a ?t? v?rifi?e par le
>> logiciel antivirus Avast.
>> https://www.avast.com/antivirus
>>
>> _______________________________________________
>> Powered by www.kitware.com
>>
>> Visit other Kitware open-source projects at
>> http://www.kitware.com/opensource/opensource.html
>>
>> Please keep messages on-topic and check the ParaView Wiki at:
>> http://paraview.org/Wiki/ParaView
>>
>> Search the list archives at: http://markmail.org/search/?q=ParaView
>>
>> Follow this link to subscribe/unsubscribe:
>> http://public.kitware.com/mailman/listinfo/paraview
>>
>
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160401/e6498f21/attachment.html>

From dave.demarle at kitware.com  Fri Apr  1 12:20:36 2016
From: dave.demarle at kitware.com (David E DeMarle)
Date: Fri, 1 Apr 2016 12:20:36 -0400
Subject: [Paraview] Paraview ray tracing plugin | OSPray
In-Reply-To: <CANt3wQuxvUbiOLOu9pyMqvp2XduM31yKFth_bv2bFOCWGMPMCQ@mail.gmail.com>
References: <CANt3wQuxvUbiOLOu9pyMqvp2XduM31yKFth_bv2bFOCWGMPMCQ@mail.gmail.com>
Message-ID: <CANjZAi8ZOSdY=rT=d_bjHroFDUr5vDe_1r2EbFXQxsEkzf81dQ@mail.gmail.com>

Raj,

Once you load the plugin, close (or create a new) RenderView window. In the
menu that results, choose the pvOSPRay view. Hit the eye icon in the
pipeline browser to make things visible in the new window. It should work
more or less the same as a standard RenderView, except that the rendering
is done in Intel's OSPRay ray tracing engine instead of rasterization in
OpenGL. There are a handful of OSPRay specific controls on the Display
section of the Properties Tab. Hit the gear icon if you can't find them at
first.

For more information head over to the developer's (TACC) pages:
http://tacc.github.io/pvOSPRay/

cheers

David E DeMarle
Kitware, Inc.
R&D Engineer
21 Corporate Drive
Clifton Park, NY 12065-8662
Phone: 518-881-4909

On Fri, Apr 1, 2016 at 12:27 AM, Raj Kumar Manna <rajphysics.mon at gmail.com>
wrote:

> Dear All,
>
> I came to know the ray tracing plugin for Paraview -OSPray. Is there any
> documentation for this plugin, like we have one for Surface-LIC
> <http://www.paraview.org/Wiki/ParaView/Line_Integral_Convolution>? I can
> load the plugin in my paraview 5.0 but could not figure out how to use it.
>
> Thanks your help.
> Raj
>
>
>
> --
> ##################################################################
> Raj Kumar Manna
> Complex Fluid & Biological Physics Lab
> IIT Madras
>
> Ph. No. 8144637401
>
> alternate email: raj at physics.iitm.ac.in <rajphysics.mon at gmail.com>
> ####################################################################
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160401/4ce9eff2/attachment.html>

From Jim.Eliot at awe.co.uk  Fri Apr  1 12:41:30 2016
From: Jim.Eliot at awe.co.uk (Jim.Eliot at awe.co.uk)
Date: Fri, 1 Apr 2016 16:41:30 +0000
Subject: [Paraview] EXTERNAL: Re: EXTERNAL: Re: CxxOverlappingAMRExample
 with Catalyst Live
In-Reply-To: <CAMaOp+GaW9p=mB1vCeGCAHRQLfssqAd5tEOh0E3g1RBS45+D6w@mail.gmail.com>
References: <201603311343.u2VDhxw3006257@msw1.awe.co.uk>
 <CAMaOp+E2RNEmixMDDN6D0wmirQGP4O5zmagiAXkAeoA3ag-Qgw@mail.gmail.com>
 <201603311604.u2VG4lXk030041@msw1.awe.co.uk>
 <CAMaOp+GaW9p=mB1vCeGCAHRQLfssqAd5tEOh0E3g1RBS45+D6w@mail.gmail.com>
Message-ID: <201604011640.u31GenL9028104@msw1.awe.co.uk>

Hi Andy,

Thank you for all the help that you have provided.

I feel like I don?t quite understand how Catalyst handles the simulation data. If I use ParaView Catalyst for large parallel simulations, and I try to fetch the entire dataset, does all the data in the problem get sent to the client on my workstation?

If I am running pvserver in parallel, would that be able to distribute the data between the processes? How do I tell Catalyst to connect to the pvservers and the pvservers to connect to the client? I guess I can use ?client-host and ?server-port on the pvservers and point them to the paraview client but how do I make the Catalyst -> pvserver connection?

Thank you for the information regarding AMR grids ? it sounds like this approach will work for my application.

Kind regards,
Jim


From: Andy Bauer [mailto:andy.bauer at kitware.com]
Sent: 31 March 2016 20:18
To: Eliot Jim AWE <Jim.Eliot at awe1.awe.co.uk>
Cc: paraview at paraview.org
Subject: EXTERNAL: Re: EXTERNAL: Re: [Paraview] CxxOverlappingAMRExample with Catalyst Live

Hi Jim,
Yes, you can have a Catalyst instrumented code connect to something running pvserver and have the pvserver connect to the client. At the end of the Python generated scripts there should be a line that looks like:
    coprocessor.DoLiveVisualization(datadescription, "localhost", 22222)
Here you just have to edit it to point to something other than localhost.

As for overlapping structured grids, there's no convenient composite/multiblock data set for that like there is for Cartesian grids. What you would need to do is use vtkStructuredGrids with blanking done manually and then just add them in as blocks in a vtkMultiBlockDataSet. It won't have the structure that the AMR specific composite data sets have so it may be a bit slower for some filters but it should work pretty much like you want for most stuff. Please let us know if you try this out and get unexpected/undesired behaviour.
Best,
Andy

On Thu, Mar 31, 2016 at 12:05 PM, <Jim.Eliot at awe.co.uk<mailto:Jim.Eliot at awe.co.uk>> wrote:
Hi Andy,

Thanks for your reply. Currently I am looking at the small examples but I would like to be able to fetch larger geometries in future. Is it possible for the simulation to connect to a parallel pvserver which will send images back to the client?

Putting interactive usage to one side for a moment, is non-uniform AMR supported in Catalyst batch? I.e. overlapping structured grids . I couldn?t find any references to non-uniform AMR in ParaView while researching.

Kind regards,
Jim

From: Andy Bauer [mailto:andy.bauer at kitware.com<mailto:andy.bauer at kitware.com>]
Sent: 31 March 2016 16:08
To: Eliot Jim AWE <Jim.Eliot at awe1.awe.co.uk<mailto:Jim.Eliot at awe1.awe.co.uk>>
Cc: paraview at paraview.org<mailto:paraview at paraview.org>
Subject: EXTERNAL: Re: [Paraview] CxxOverlappingAMRExample with Catalyst Live

Hi Jim,
Yes, currently Overlapping AMR data sets are not supported by Catalyst Live. This is because VTK doesn't support sending that data object. That would have to be changed in vtkCommunicator::Send(vtkDataObject* data, int remoteHandle, int tag).
A workaround would be to use a Threshold filter to convert to a multiblock of unstructured grids, use the merge blocks filter and then extract this output to the client. You'll get some warnings about the data set not being a polydata (think about running a large simulation and trying to transfer all of that to a separate server or client). I'm assuming since you're trying to fetch the entire data set that the use case isn't for an overly large data set.
Cheers,
Andy

On Thu, Mar 31, 2016 at 9:44 AM, <Jim.Eliot at awe.co.uk<mailto:Jim.Eliot at awe.co.uk>> wrote:

Good afternoon,

I have been trying to use Catalyst Live with the CxxOverlappingAMRExample from the ParaView Catalyst Example Code repository [1] but I see an error when I try to visualise the data from a ParaView client. The client connects to the simulation successfully and PVTrivialProducer1 appears in the Pipeline Browser. The Information tab shows it as an Overlapping AMR Dataset with 3 levels. However, when I click on the PVTrivialProducer1 icon, ParaView prints an error then segfaults. The error is something like:

    Warning: In <src-dir>/VTK/Parallel/Core/vtkCommunicator.cxx, line 394
    vtkSocketCommunicator (?): Cannot receive vtkOverlappingAMR

I have tried this with both ParaView 4.4.0 and 5.0.0 with the same results. The example works fine when I am using non-Live Catalyst (i.e. it writes out a bunch of vtm files that I can read into ParaView).

So I am wondering, are AMR meshes not supported by Catalyst Live? Do I have to handle AMR meshes differently when using Catalyst interactively?

Many thanks,
Jim

[1] https://github.com/Kitware/ParaViewCatalystExampleCode

Jim Eliot
High Performance Computing Group
AWE, Aldermaston, Reading, RG7 4PR


The information in this email and in any attachment(s) is commercial in confidence. If you are not the named addressee(s) or if you receive this email in error then any distribution, copying or use of this communication or the information in it is strictly prohibited. Please notify us immediately by email at admin.internet(at)awe.co.uk<http://awe.co.uk>, and then delete this message from your computer. While attachments are virus checked, AWE plc does not accept any liability in respect of any virus which is not detected. AWE Plc Registered in England and Wales Registration No 02763902 AWE, Aldermaston, Reading, RG7 4PR

_______________________________________________
Powered by www.kitware.com<http://www.kitware.com>

Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView

Search the list archives at: http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview

The information in this email and in any attachment(s) is commercial in confidence. If you are not the named addressee(s) or if you receive this email in error then any distribution, copying or use of this communication or the information in it is strictly prohibited. Please notify us immediately by email at admin.internet(at)awe.co.uk<http://awe.co.uk>, and then delete this message from your computer. While attachments are virus checked, AWE plc does not accept any liability in respect of any virus which is not detected. AWE Plc Registered in England and Wales Registration No 02763902 AWE, Aldermaston, Reading, RG7 4PR



The information in this email and in any attachment(s) is 
commercial in confidence. If you are not the named addressee(s) 
or 
if you receive this email in error then any distribution, copying or 
use of this communication or the information in it is strictly 
prohibited. Please notify us immediately by email at 
admin.internet(at)awe.co.uk, and then delete this message from 
your computer. While attachments are virus checked, AWE plc 
does not accept any liability in respect of any virus which is not 
detected.

AWE Plc
Registered in England and Wales
Registration No 02763902
AWE, Aldermaston, Reading, RG7 4PR

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160401/d5942fcd/attachment.html>

From rajphysics.mon at gmail.com  Fri Apr  1 12:57:52 2016
From: rajphysics.mon at gmail.com (Raj Kumar Manna)
Date: Fri, 1 Apr 2016 22:27:52 +0530
Subject: [Paraview] Paraview ray tracing plugin | OSPray
In-Reply-To: <CANjZAi8ZOSdY=rT=d_bjHroFDUr5vDe_1r2EbFXQxsEkzf81dQ@mail.gmail.com>
References: <CANt3wQuxvUbiOLOu9pyMqvp2XduM31yKFth_bv2bFOCWGMPMCQ@mail.gmail.com>
 <CANjZAi8ZOSdY=rT=d_bjHroFDUr5vDe_1r2EbFXQxsEkzf81dQ@mail.gmail.com>
Message-ID: <CANt3wQsphpyv3MmB9G3F_6W0kMiPiRVQJWBXZNbNQnNHtheN8A@mail.gmail.com>

Thanks. It works but very slow. Even a simple sphere rendering hangs my
machine. I am using Paraview 5.0 on Intel(R) Xeon(R) CPU E3-1226 v3 @
3.30GHz with 16 GB memory.


Raj

On Fri, Apr 1, 2016 at 9:50 PM, David E DeMarle <dave.demarle at kitware.com>
wrote:

> Raj,
>
> Once you load the plugin, close (or create a new) RenderView window. In
> the menu that results, choose the pvOSPRay view. Hit the eye icon in the
> pipeline browser to make things visible in the new window. It should work
> more or less the same as a standard RenderView, except that the rendering
> is done in Intel's OSPRay ray tracing engine instead of rasterization in
> OpenGL. There are a handful of OSPRay specific controls on the Display
> section of the Properties Tab. Hit the gear icon if you can't find them at
> first.
>
> For more information head over to the developer's (TACC) pages:
> http://tacc.github.io/pvOSPRay/
>
> cheers
>
> David E DeMarle
> Kitware, Inc.
> R&D Engineer
> 21 Corporate Drive
> Clifton Park, NY 12065-8662
> Phone: 518-881-4909
>
> On Fri, Apr 1, 2016 at 12:27 AM, Raj Kumar Manna <rajphysics.mon at gmail.com
> > wrote:
>
>> Dear All,
>>
>> I came to know the ray tracing plugin for Paraview -OSPray. Is there any
>> documentation for this plugin, like we have one for Surface-LIC
>> <http://www.paraview.org/Wiki/ParaView/Line_Integral_Convolution>? I can
>> load the plugin in my paraview 5.0 but could not figure out how to use it.
>>
>> Thanks your help.
>> Raj
>>
>>
>>
>> --
>> ##################################################################
>> Raj Kumar Manna
>> Complex Fluid & Biological Physics Lab
>> IIT Madras
>>
>> Ph. No. 8144637401
>>
>> alternate email: raj at physics.iitm.ac.in <rajphysics.mon at gmail.com>
>> ####################################################################
>>
>> _______________________________________________
>> Powered by www.kitware.com
>>
>> Visit other Kitware open-source projects at
>> http://www.kitware.com/opensource/opensource.html
>>
>> Please keep messages on-topic and check the ParaView Wiki at:
>> http://paraview.org/Wiki/ParaView
>>
>> Search the list archives at: http://markmail.org/search/?q=ParaView
>>
>> Follow this link to subscribe/unsubscribe:
>> http://public.kitware.com/mailman/listinfo/paraview
>>
>>
>


-- 
##################################################################
Raj Kumar Manna
Complex Fluid & Biological Physics Lab
IIT Madras

Ph. No. 8144637401

alternate email: raj at physics.iitm.ac.in <rajphysics.mon at gmail.com>
####################################################################
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160401/8dadeab9/attachment.html>

From cindy.castro at uvsq.fr  Fri Apr  1 13:06:17 2016
From: cindy.castro at uvsq.fr (Cindy Castro)
Date: Fri, 1 Apr 2016 19:06:17 +0200
Subject: [Paraview] Background in 3D mode
In-Reply-To: <CANjZAi9xRGmn=PJPfAn_Ne4+S1fhfw3WAY2-FDg13wOP9Jzu4w@mail.gmail.com>
References: <56EADA83.6050104@uvsq.fr> <56FE2BEC.2030702@uvsq.fr>
 <CACJ=gTjTvHLnGvd7w3LVY4zPufCauj_ZDKv1-aZSRr=qJfC3wA@mail.gmail.com>
 <CANjZAi9xRGmn=PJPfAn_Ne4+S1fhfw3WAY2-FDg13wOP9Jzu4w@mail.gmail.com>
Message-ID: <56FEAA89.2010102@uvsq.fr>

H Joachim and David,

Thank you for answering. I tried to apply an Image AND Gradient 
background and it was not correctly split over the different screens. I 
think it is cave mode actually. I have tested tile mode but the display 
is not well ordered. I tried to correct it with mpirun (-tdx=2, -tdy=4) 
but I may have missed something in the command line.

Here is my pvx file :

<?xml version="1.0" ?>
<pvx>
  <Process Type="client" />
  <Process Type="server">
  <EyeSeparation Value="0.060"/>
   <Machine Name="node1-1"
            Environment="DISPLAY=:0.0"
            FullScreen="0"
            ShowBorders="0"
            Geometry="1920x1080+0+0"
            LowerLeft=" -2.593 0.992 -2.593"
            LowerRight="-1.497 0.993 -3.689"
            UpperRight="-1.497 1.865 -3.689" />
   <Machine Name="node1-2"
            Environment="DISPLAY=:0.0"
            FullScreen="0"
            ShowBorders="0"
            Geometry="1920x1080+1920+0"
            LowerLeft=" -1.497 0.993 -3.689"
            LowerRight=" 0.000 0.997 -4.090"
            UpperRight=" 0.000 1.869 -4.090" />
   <Machine Name="node2-1"
            Environment="DISPLAY=:0.0"
            FullScreen="0"
            ShowBorders="0"
            Geometry="1920x1080+0+0"
            LowerLeft="  0.000 0.997 -4.090"
            LowerRight=" 1.497 1.007 -3.689"
            UpperRight=" 1.497 1.879 -3.689"/>
   <Machine Name="node2-2"
            Environment="DISPLAY=:0.0"
            FullScreen="0"
            ShowBorders="0"
            Geometry="1920x1080+1920+0"
        LowerLeft="  1.497 1.007 -3.689"
            LowerRight=" 2.593 0.997 -2.593"
            UpperRight=" 2.593 1.869 -2.593"/>
   <Machine Name="node3-1"
            Environment="DISPLAY=:0.0"
            FullScreen="0"
            ShowBorders="0"
            Geometry="1920x1080+0+0"
            LowerLeft=" -2.593 0.120 -2.593"
            LowerRight="-1.497 0.121 -3.689"
            UpperRight="-1.497 0.993 -3.689" />
   <Machine Name="node3-2"
            Environment="DISPLAY=:0.0"
            FullScreen="0"
            ShowBorders="0"
            Geometry="1920x1080+1920+0"
            LowerLeft=" -1.497 0.121 -3.689"
            LowerRight=" 0.000 0.125 -4.090"
            UpperRight=" 0.000 0.997 -4.090" />
   <Machine Name="node4-1"
            Environment="DISPLAY=:0.0"
            FullScreen="0"
            ShowBorders="0"
            Geometry="1920x1080+0+0"
            LowerLeft="  0.000 0.125 -4.090"
            LowerRight=" 1.497 0.135 -3.689"
            UpperRight=" 1.497 1.007 -3.689"/>
   <Machine Name="node4-2"
            Environment="DISPLAY=:0.0"
            FullScreen="0"
            ShowBorders="0"
            Geometry="1920x1080+1920+0"
            LowerLeft="  1.497 0.135 -3.689"
            LowerRight=" 2.593 0.125 -2.593"
            UpperRight=" 2.593 0.997 -2.593"/>
   </Process>

</pvx>

Regards,

Cindy

Le 01/04/2016 17:55, David E DeMarle a ?crit :
> Cindy,
>
> I can't remember which mode, tile or cave, doesn't support tile and 
> gradient background. But from what you and Joachim say it must be cave.
>
> You should aim for tile mode then. You can enforce and thus correct 
> the ordering problem you see  with tile mode with your mpirun command 
> and the your cave.pvx file. Can you share your 
> /opt/software/ParaView/PVresources/wall_config.pvx? So I can suggest a 
> fix?
>
> thanks
>
>
> David E DeMarle
> Kitware, Inc.
> R&D Engineer
> 21 Corporate Drive
> Clifton Park, NY 12065-8662
> Phone: 518-881-4909
>
> On Fri, Apr 1, 2016 at 11:10 AM, Joachim Pouderoux 
> <joachim.pouderoux at kitware.com <mailto:joachim.pouderoux at kitware.com>> 
> wrote:
>
>     Hi Cindy,
>
>     Not totally sure to understand - are you trying to apply an Image
>     or Gradient background and would like it to be correctly split
>     over the different screen? If so, I am afraid this feature is not
>     supported.
>
>     Best,
>     Joachim
>
>     *Joachim Pouderoux*
>
>         /PhD, Technical Expert/
>         *Kitware SAS <http://www.kitware.fr>*
>
>
>     2016-04-01 10:06 GMT+02:00 Cindy Castro <cindy.castro at uvsq.fr
>     <mailto:cindy.castro at uvsq.fr>>:
>
>         Hello,
>
>         I am using ParaView in client/server mode with stereo. I have
>         a cluster with 4 nodes, 1 GPU each (NVIDIA K5000) and 8
>         screens for display.
>
>         My problem is I can not find how to span a background over my
>         8 screens. The background is displayed on each screen. 3D
>         models are well displayed in 3D (no problem with that).
>
>         The server is run with the command:
>         mpirun -np 8 -machinefile
>         /opt/software/ParaView/PVscripts/server_machinefile.txt
>         /opt/software/ParaView/ParaView-5.0.0-bin/bin/pvserver -rc
>         --client-host=mire-pc
>         /opt/software/ParaView/PVresources/wall_config.pvx
>
>         I tried tiles mode but the display is not in the right order...
>
>         Can you help me ? Is it possible to span a background over
>         several screens in 3D mode ? I is really useful when rendering.
>
>         Regards,
>
>         -- 
>         Cindy CASTRO
>         Responsable plateforme DIGISCOPE-MIRE
>         Plateforme d'Int?gration et de Tests (PIT)
>         -- 
>         Observatoire de Versailles Saint-Quentin-en-Yvelines (OVSQ)
>         Quartier des Garennes
>         11 Boulevard d'Alembert
>         78280 Guyancourt
>         -- 
>         B?timent principal - RDC - Bureau 215
>         T?l : +33 (0)1 80 28 51 03
>         <tel:%2B33%20%280%291%2080%2028%2051%2003>
>         Salle MIRE : +33 (0)1 80 28 54 93
>         <tel:%2B33%20%280%291%2080%2028%2054%2093>
>
>
>         ---
>         L'absence de virus dans ce courrier ?lectronique a ?t?
>         v?rifi?e par le logiciel antivirus Avast.
>         https://www.avast.com/antivirus
>
>         _______________________________________________
>         Powered by www.kitware.com <http://www.kitware.com>
>
>         Visit other Kitware open-source projects at
>         http://www.kitware.com/opensource/opensource.html
>
>         Please keep messages on-topic and check the ParaView Wiki at:
>         http://paraview.org/Wiki/ParaView
>
>         Search the list archives at:
>         http://markmail.org/search/?q=ParaView
>
>         Follow this link to subscribe/unsubscribe:
>         http://public.kitware.com/mailman/listinfo/paraview
>
>
>
>     _______________________________________________
>     Powered by www.kitware.com <http://www.kitware.com>
>
>     Visit other Kitware open-source projects at
>     http://www.kitware.com/opensource/opensource.html
>
>     Please keep messages on-topic and check the ParaView Wiki at:
>     http://paraview.org/Wiki/ParaView
>
>     Search the list archives at: http://markmail.org/search/?q=ParaView
>
>     Follow this link to subscribe/unsubscribe:
>     http://public.kitware.com/mailman/listinfo/paraview
>
>

-- 
Cindy CASTRO
Responsable plateforme DIGISCOPE-MIRE
Plateforme d'Int?gration et de Tests (PIT)
-- 
Observatoire de Versailles Saint-Quentin-en-Yvelines (OVSQ)
Quartier des Garennes
11 Boulevard d'Alembert
78280 Guyancourt
-- 
B?timent principal - RDC - Bureau 215
T?l : +33 (0)1 80 28 51 03
Salle MIRE : +33 (0)1 80 28 54 93



---
L'absence de virus dans ce courrier ?lectronique a ?t? v?rifi?e par le logiciel antivirus Avast.
https://www.avast.com/antivirus
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160401/e59703ca/attachment.html>

From dave.demarle at kitware.com  Fri Apr  1 13:11:16 2016
From: dave.demarle at kitware.com (David E DeMarle)
Date: Fri, 1 Apr 2016 13:11:16 -0400
Subject: [Paraview] Paraview ray tracing plugin | OSPray
In-Reply-To: <CANt3wQsphpyv3MmB9G3F_6W0kMiPiRVQJWBXZNbNQnNHtheN8A@mail.gmail.com>
References: <CANt3wQuxvUbiOLOu9pyMqvp2XduM31yKFth_bv2bFOCWGMPMCQ@mail.gmail.com>
 <CANjZAi8ZOSdY=rT=d_bjHroFDUr5vDe_1r2EbFXQxsEkzf81dQ@mail.gmail.com>
 <CANt3wQsphpyv3MmB9G3F_6W0kMiPiRVQJWBXZNbNQnNHtheN8A@mail.gmail.com>
Message-ID: <CANjZAi-39s9PBjobG5Ad+RMc6HXpi=BERn=YJ3sk5ML_zirQCQ@mail.gmail.com>

Definitely shouldn't do that. The rendering speed should typically be about
the same as you get with OpenGL but there are many dependent factors to
that of course.

Is that with the 5.0.0 binary or the recently released 5.0.1 binary? We
fixed a bug in between 5.0.0 and 5.0.1 that is the likely cause. Other
things you can try are to disable Progressive Refinement and to build
ParaView from source. All three have been helpful to others on the list.

thanks



David E DeMarle
Kitware, Inc.
R&D Engineer
21 Corporate Drive
Clifton Park, NY 12065-8662
Phone: 518-881-4909

On Fri, Apr 1, 2016 at 12:57 PM, Raj Kumar Manna <rajphysics.mon at gmail.com>
wrote:

> Thanks. It works but very slow. Even a simple sphere rendering hangs my
> machine. I am using Paraview 5.0 on Intel(R) Xeon(R) CPU E3-1226 v3 @
> 3.30GHz with 16 GB memory.
>
>
> Raj
>
> On Fri, Apr 1, 2016 at 9:50 PM, David E DeMarle <dave.demarle at kitware.com>
> wrote:
>
>> Raj,
>>
>> Once you load the plugin, close (or create a new) RenderView window. In
>> the menu that results, choose the pvOSPRay view. Hit the eye icon in the
>> pipeline browser to make things visible in the new window. It should work
>> more or less the same as a standard RenderView, except that the rendering
>> is done in Intel's OSPRay ray tracing engine instead of rasterization in
>> OpenGL. There are a handful of OSPRay specific controls on the Display
>> section of the Properties Tab. Hit the gear icon if you can't find them at
>> first.
>>
>> For more information head over to the developer's (TACC) pages:
>> http://tacc.github.io/pvOSPRay/
>>
>> cheers
>>
>> David E DeMarle
>> Kitware, Inc.
>> R&D Engineer
>> 21 Corporate Drive
>> Clifton Park, NY 12065-8662
>> Phone: 518-881-4909
>>
>> On Fri, Apr 1, 2016 at 12:27 AM, Raj Kumar Manna <
>> rajphysics.mon at gmail.com> wrote:
>>
>>> Dear All,
>>>
>>> I came to know the ray tracing plugin for Paraview -OSPray. Is there any
>>> documentation for this plugin, like we have one for Surface-LIC
>>> <http://www.paraview.org/Wiki/ParaView/Line_Integral_Convolution>? I
>>> can load the plugin in my paraview 5.0 but could not figure out how to use
>>> it.
>>>
>>> Thanks your help.
>>> Raj
>>>
>>>
>>>
>>> --
>>> ##################################################################
>>> Raj Kumar Manna
>>> Complex Fluid & Biological Physics Lab
>>> IIT Madras
>>>
>>> Ph. No. 8144637401
>>>
>>> alternate email: raj at physics.iitm.ac.in <rajphysics.mon at gmail.com>
>>> ####################################################################
>>>
>>> _______________________________________________
>>> Powered by www.kitware.com
>>>
>>> Visit other Kitware open-source projects at
>>> http://www.kitware.com/opensource/opensource.html
>>>
>>> Please keep messages on-topic and check the ParaView Wiki at:
>>> http://paraview.org/Wiki/ParaView
>>>
>>> Search the list archives at: http://markmail.org/search/?q=ParaView
>>>
>>> Follow this link to subscribe/unsubscribe:
>>> http://public.kitware.com/mailman/listinfo/paraview
>>>
>>>
>>
>
>
> --
> ##################################################################
> Raj Kumar Manna
> Complex Fluid & Biological Physics Lab
> IIT Madras
>
> Ph. No. 8144637401
>
> alternate email: raj at physics.iitm.ac.in <rajphysics.mon at gmail.com>
> ####################################################################
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160401/c42c1a3c/attachment.html>

From dave.demarle at kitware.com  Fri Apr  1 13:45:03 2016
From: dave.demarle at kitware.com (David E DeMarle)
Date: Fri, 1 Apr 2016 13:45:03 -0400
Subject: [Paraview] Background in 3D mode
In-Reply-To: <56FEAA89.2010102@uvsq.fr>
References: <56EADA83.6050104@uvsq.fr> <56FE2BEC.2030702@uvsq.fr>
 <CACJ=gTjTvHLnGvd7w3LVY4zPufCauj_ZDKv1-aZSRr=qJfC3wA@mail.gmail.com>
 <CANjZAi9xRGmn=PJPfAn_Ne4+S1fhfw3WAY2-FDg13wOP9Jzu4w@mail.gmail.com>
 <56FEAA89.2010102@uvsq.fr>
Message-ID: <CANjZAi8nnN_pSZcm9d-iJ0pDj_8=b5H0Q1gJVRFQFWkpYbGvyg@mail.gmail.com>

Aiming for this right?
-------------------
|1-1|1-2|2-1|2-2|
-------------------
|3-1|3-2|4-1|4-2|
-------------------


-tdx=3 -tdy=2
machinefile.txt that you pass to mpi should be (syntax depends on your mpi)
node1
node1
node2
node2
node3
node3
node4
node4
The point being that you want them to start up in the same order that you
have in your pvx file. Use > mpirun ... /bin/uname (and xterm -r "uname -a"
-hold) to work out the details.

Lastly you don't need the LowerLeft, LowerRight and UpperRight for tile
mode, but it will be useful for stereoscopic display so keep it handy.





David E DeMarle
Kitware, Inc.
R&D Engineer
21 Corporate Drive
Clifton Park, NY 12065-8662
Phone: 518-881-4909

On Fri, Apr 1, 2016 at 1:06 PM, Cindy Castro <cindy.castro at uvsq.fr> wrote:

> H Joachim and David,
>
> Thank you for answering. I tried to apply an Image AND Gradient background
> and it was not correctly split over the different screens. I think it is
> cave mode actually. I have tested tile mode but the display is not well
> ordered. I tried to correct it with mpirun (-tdx=2, -tdy=4) but I may have
> missed something in the command line.
>
> Here is my pvx file :
>
> <?xml version="1.0" ?>
> <pvx>
>  <Process Type="client" />
>  <Process Type="server">
>  <EyeSeparation Value="0.060"/>
>   <Machine Name="node1-1"
>            Environment="DISPLAY=:0.0"
>            FullScreen="0"
>            ShowBorders="0"
>            Geometry="1920x1080+0+0"
>            LowerLeft=" -2.593 0.992 -2.593"
>            LowerRight="-1.497 0.993 -3.689"
>            UpperRight="-1.497 1.865 -3.689" />
>   <Machine Name="node1-2"
>            Environment="DISPLAY=:0.0"
>            FullScreen="0"
>            ShowBorders="0"
>            Geometry="1920x1080+1920+0"
>            LowerLeft=" -1.497 0.993 -3.689"
>            LowerRight=" 0.000 0.997 -4.090"
>            UpperRight=" 0.000 1.869 -4.090" />
>   <Machine Name="node2-1"
>            Environment="DISPLAY=:0.0"
>            FullScreen="0"
>            ShowBorders="0"
>            Geometry="1920x1080+0+0"
>            LowerLeft="  0.000 0.997 -4.090"
>            LowerRight=" 1.497 1.007 -3.689"
>            UpperRight=" 1.497 1.879 -3.689"/>
>   <Machine Name="node2-2"
>            Environment="DISPLAY=:0.0"
>            FullScreen="0"
>            ShowBorders="0"
>            Geometry="1920x1080+1920+0"
>        LowerLeft="  1.497 1.007 -3.689"
>            LowerRight=" 2.593 0.997 -2.593"
>            UpperRight=" 2.593 1.869 -2.593"/>
>   <Machine Name="node3-1"
>            Environment="DISPLAY=:0.0"
>            FullScreen="0"
>            ShowBorders="0"
>            Geometry="1920x1080+0+0"
>            LowerLeft=" -2.593 0.120 -2.593"
>            LowerRight="-1.497 0.121 -3.689"
>            UpperRight="-1.497 0.993 -3.689" />
>   <Machine Name="node3-2"
>            Environment="DISPLAY=:0.0"
>            FullScreen="0"
>            ShowBorders="0"
>            Geometry="1920x1080+1920+0"
>            LowerLeft=" -1.497 0.121 -3.689"
>            LowerRight=" 0.000 0.125 -4.090"
>            UpperRight=" 0.000 0.997 -4.090" />
>   <Machine Name="node4-1"
>            Environment="DISPLAY=:0.0"
>            FullScreen="0"
>            ShowBorders="0"
>            Geometry="1920x1080+0+0"
>            LowerLeft="  0.000 0.125 -4.090"
>            LowerRight=" 1.497 0.135 -3.689"
>            UpperRight=" 1.497 1.007 -3.689"/>
>   <Machine Name="node4-2"
>            Environment="DISPLAY=:0.0"
>            FullScreen="0"
>            ShowBorders="0"
>            Geometry="1920x1080+1920+0"
>            LowerLeft="  1.497 0.135 -3.689"
>            LowerRight=" 2.593 0.125 -2.593"
>            UpperRight=" 2.593 0.997 -2.593"/>
>   </Process>
>
> </pvx>
>
> Regards,
>
> Cindy
>
>
> Le 01/04/2016 17:55, David E DeMarle a ?crit :
>
> Cindy,
>
> I can't remember which mode, tile or cave, doesn't support tile and
> gradient background. But from what you and Joachim say it must be cave.
>
> You should aim for tile mode then. You can enforce and thus correct the
> ordering problem you see  with tile mode with your mpirun command and the
> your cave.pvx file. Can you share your
> /opt/software/ParaView/PVresources/wall_config.pvx? So I can suggest a fix?
>
> thanks
>
>
> David E DeMarle
> Kitware, Inc.
> R&D Engineer
> 21 Corporate Drive
> Clifton Park, NY 12065-8662
> Phone: 518-881-4909
>
> On Fri, Apr 1, 2016 at 11:10 AM, Joachim Pouderoux <
> <joachim.pouderoux at kitware.com>joachim.pouderoux at kitware.com> wrote:
>
>> Hi Cindy,
>>
>> Not totally sure to understand - are you trying to apply an Image or
>> Gradient background and would like it to be correctly split over the
>> different screen? If so, I am afraid this feature is not supported.
>>
>> Best,
>> Joachim
>>
>> *Joachim Pouderoux*
>>
>> *PhD, Technical Expert*
>> *Kitware SAS <http://www.kitware.fr>*
>>
>>
>> 2016-04-01 10:06 GMT+02:00 Cindy Castro < <cindy.castro at uvsq.fr>
>> cindy.castro at uvsq.fr>:
>>
>>> Hello,
>>>
>>> I am using ParaView in client/server mode with stereo. I have a cluster
>>> with 4 nodes, 1 GPU each (NVIDIA K5000) and 8 screens for display.
>>>
>>> My problem is I can not find how to span a background over my 8 screens.
>>> The background is displayed on each screen. 3D models are well displayed in
>>> 3D (no problem with that).
>>>
>>> The server is run with the command:
>>> mpirun -np 8 -machinefile
>>> /opt/software/ParaView/PVscripts/server_machinefile.txt
>>> /opt/software/ParaView/ParaView-5.0.0-bin/bin/pvserver -rc
>>> --client-host=mire-pc /opt/software/ParaView/PVresources/wall_config.pvx
>>>
>>> I tried tiles mode but the display is not in the right order...
>>>
>>> Can you help me ? Is it possible to span a background over several
>>> screens in 3D mode ? I is really useful when rendering.
>>>
>>> Regards,
>>>
>>> --
>>> Cindy CASTRO
>>> Responsable plateforme DIGISCOPE-MIRE
>>> Plateforme d'Int?gration et de Tests (PIT)
>>> --
>>> Observatoire de Versailles Saint-Quentin-en-Yvelines (OVSQ)
>>> Quartier des Garennes
>>> 11 Boulevard d'Alembert
>>> 78280 Guyancourt
>>> --
>>> B?timent principal - RDC - Bureau 215
>>> T?l : +33 (0)1 80 28 51 03 <%2B33%20%280%291%2080%2028%2051%2003>
>>> Salle MIRE : +33 (0)1 80 28 54 93 <%2B33%20%280%291%2080%2028%2054%2093>
>>>
>>>
>>> ---
>>> L'absence de virus dans ce courrier ?lectronique a ?t? v?rifi?e par le
>>> logiciel antivirus Avast.
>>> https://www.avast.com/antivirus
>>>
>>> _______________________________________________
>>> Powered by www.kitware.com
>>>
>>> Visit other Kitware open-source projects at
>>> <http://www.kitware.com/opensource/opensource.html>
>>> http://www.kitware.com/opensource/opensource.html
>>>
>>> Please keep messages on-topic and check the ParaView Wiki at:
>>> http://paraview.org/Wiki/ParaView
>>>
>>> Search the list archives at: <http://markmail.org/search/?q=ParaView>
>>> http://markmail.org/search/?q=ParaView
>>>
>>> Follow this link to subscribe/unsubscribe:
>>> http://public.kitware.com/mailman/listinfo/paraview
>>>
>>
>>
>> _______________________________________________
>> Powered by www.kitware.com
>>
>> Visit other Kitware open-source projects at
>> <http://www.kitware.com/opensource/opensource.html>
>> http://www.kitware.com/opensource/opensource.html
>>
>> Please keep messages on-topic and check the ParaView Wiki at:
>> http://paraview.org/Wiki/ParaView
>>
>> Search the list archives at: http://markmail.org/search/?q=ParaView
>>
>> Follow this link to subscribe/unsubscribe:
>> http://public.kitware.com/mailman/listinfo/paraview
>>
>>
>
> --
> Cindy CASTRO
> Responsable plateforme DIGISCOPE-MIRE
> Plateforme d'Int?gration et de Tests (PIT)
> --
> Observatoire de Versailles Saint-Quentin-en-Yvelines (OVSQ)
> Quartier des Garennes
> 11 Boulevard d'Alembert
> 78280 Guyancourt
> --
> B?timent principal - RDC - Bureau 215
> T?l : +33 (0)1 80 28 51 03
> Salle MIRE : +33 (0)1 80 28 54 93
>
>
> Cet e-mail a ?t? envoy? depuis un ordinateur prot?g? par Avast.
> www.avast.com
> <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160401/5fe48698/attachment.html>

From dave.demarle at kitware.com  Fri Apr  1 14:03:23 2016
From: dave.demarle at kitware.com (David E DeMarle)
Date: Fri, 1 Apr 2016 14:03:23 -0400
Subject: [Paraview] Background in 3D mode
In-Reply-To: <CANjZAi8nnN_pSZcm9d-iJ0pDj_8=b5H0Q1gJVRFQFWkpYbGvyg@mail.gmail.com>
References: <56EADA83.6050104@uvsq.fr> <56FE2BEC.2030702@uvsq.fr>
 <CACJ=gTjTvHLnGvd7w3LVY4zPufCauj_ZDKv1-aZSRr=qJfC3wA@mail.gmail.com>
 <CANjZAi9xRGmn=PJPfAn_Ne4+S1fhfw3WAY2-FDg13wOP9Jzu4w@mail.gmail.com>
 <56FEAA89.2010102@uvsq.fr>
 <CANjZAi8nnN_pSZcm9d-iJ0pDj_8=b5H0Q1gJVRFQFWkpYbGvyg@mail.gmail.com>
Message-ID: <CANjZAi9VwZVXvu1-cAAzoEme6-bs7tLHbhj02WdVFfou4h0S9g@mail.gmail.com>

And of course I just now realized that you are asking for 3D ie
stereoscopic mode and remembered that tiled display does not (yet) support
Crystal Eyes active stereo.

apologies


David E DeMarle
Kitware, Inc.
R&D Engineer
21 Corporate Drive
Clifton Park, NY 12065-8662
Phone: 518-881-4909

On Fri, Apr 1, 2016 at 1:45 PM, David E DeMarle <dave.demarle at kitware.com>
wrote:

> Aiming for this right?
> -------------------
> |1-1|1-2|2-1|2-2|
> -------------------
> |3-1|3-2|4-1|4-2|
> -------------------
>
>
> -tdx=3 -tdy=2
> machinefile.txt that you pass to mpi should be (syntax depends on your mpi)
> node1
> node1
> node2
> node2
> node3
> node3
> node4
> node4
> The point being that you want them to start up in the same order that you
> have in your pvx file. Use > mpirun ... /bin/uname (and xterm -r "uname -a"
> -hold) to work out the details.
>
> Lastly you don't need the LowerLeft, LowerRight and UpperRight for tile
> mode, but it will be useful for stereoscopic display so keep it handy.
>
>
>
>
>
> David E DeMarle
> Kitware, Inc.
> R&D Engineer
> 21 Corporate Drive
> Clifton Park, NY 12065-8662
> Phone: 518-881-4909
>
> On Fri, Apr 1, 2016 at 1:06 PM, Cindy Castro <cindy.castro at uvsq.fr> wrote:
>
>> H Joachim and David,
>>
>> Thank you for answering. I tried to apply an Image AND Gradient
>> background and it was not correctly split over the different screens. I
>> think it is cave mode actually. I have tested tile mode but the display is
>> not well ordered. I tried to correct it with mpirun (-tdx=2, -tdy=4) but I
>> may have missed something in the command line.
>>
>> Here is my pvx file :
>>
>> <?xml version="1.0" ?>
>> <pvx>
>>  <Process Type="client" />
>>  <Process Type="server">
>>  <EyeSeparation Value="0.060"/>
>>   <Machine Name="node1-1"
>>            Environment="DISPLAY=:0.0"
>>            FullScreen="0"
>>            ShowBorders="0"
>>            Geometry="1920x1080+0+0"
>>            LowerLeft=" -2.593 0.992 -2.593"
>>            LowerRight="-1.497 0.993 -3.689"
>>            UpperRight="-1.497 1.865 -3.689" />
>>   <Machine Name="node1-2"
>>            Environment="DISPLAY=:0.0"
>>            FullScreen="0"
>>            ShowBorders="0"
>>            Geometry="1920x1080+1920+0"
>>            LowerLeft=" -1.497 0.993 -3.689"
>>            LowerRight=" 0.000 0.997 -4.090"
>>            UpperRight=" 0.000 1.869 -4.090" />
>>   <Machine Name="node2-1"
>>            Environment="DISPLAY=:0.0"
>>            FullScreen="0"
>>            ShowBorders="0"
>>            Geometry="1920x1080+0+0"
>>            LowerLeft="  0.000 0.997 -4.090"
>>            LowerRight=" 1.497 1.007 -3.689"
>>            UpperRight=" 1.497 1.879 -3.689"/>
>>   <Machine Name="node2-2"
>>            Environment="DISPLAY=:0.0"
>>            FullScreen="0"
>>            ShowBorders="0"
>>            Geometry="1920x1080+1920+0"
>>        LowerLeft="  1.497 1.007 -3.689"
>>            LowerRight=" 2.593 0.997 -2.593"
>>            UpperRight=" 2.593 1.869 -2.593"/>
>>   <Machine Name="node3-1"
>>            Environment="DISPLAY=:0.0"
>>            FullScreen="0"
>>            ShowBorders="0"
>>            Geometry="1920x1080+0+0"
>>            LowerLeft=" -2.593 0.120 -2.593"
>>            LowerRight="-1.497 0.121 -3.689"
>>            UpperRight="-1.497 0.993 -3.689" />
>>   <Machine Name="node3-2"
>>            Environment="DISPLAY=:0.0"
>>            FullScreen="0"
>>            ShowBorders="0"
>>            Geometry="1920x1080+1920+0"
>>            LowerLeft=" -1.497 0.121 -3.689"
>>            LowerRight=" 0.000 0.125 -4.090"
>>            UpperRight=" 0.000 0.997 -4.090" />
>>   <Machine Name="node4-1"
>>            Environment="DISPLAY=:0.0"
>>            FullScreen="0"
>>            ShowBorders="0"
>>            Geometry="1920x1080+0+0"
>>            LowerLeft="  0.000 0.125 -4.090"
>>            LowerRight=" 1.497 0.135 -3.689"
>>            UpperRight=" 1.497 1.007 -3.689"/>
>>   <Machine Name="node4-2"
>>            Environment="DISPLAY=:0.0"
>>            FullScreen="0"
>>            ShowBorders="0"
>>            Geometry="1920x1080+1920+0"
>>            LowerLeft="  1.497 0.135 -3.689"
>>            LowerRight=" 2.593 0.125 -2.593"
>>            UpperRight=" 2.593 0.997 -2.593"/>
>>   </Process>
>>
>> </pvx>
>>
>> Regards,
>>
>> Cindy
>>
>>
>> Le 01/04/2016 17:55, David E DeMarle a ?crit :
>>
>> Cindy,
>>
>> I can't remember which mode, tile or cave, doesn't support tile and
>> gradient background. But from what you and Joachim say it must be cave.
>>
>> You should aim for tile mode then. You can enforce and thus correct the
>> ordering problem you see  with tile mode with your mpirun command and the
>> your cave.pvx file. Can you share your
>> /opt/software/ParaView/PVresources/wall_config.pvx? So I can suggest a fix?
>>
>> thanks
>>
>>
>> David E DeMarle
>> Kitware, Inc.
>> R&D Engineer
>> 21 Corporate Drive
>> Clifton Park, NY 12065-8662
>> Phone: 518-881-4909
>>
>> On Fri, Apr 1, 2016 at 11:10 AM, Joachim Pouderoux <
>> <joachim.pouderoux at kitware.com>joachim.pouderoux at kitware.com> wrote:
>>
>>> Hi Cindy,
>>>
>>> Not totally sure to understand - are you trying to apply an Image or
>>> Gradient background and would like it to be correctly split over the
>>> different screen? If so, I am afraid this feature is not supported.
>>>
>>> Best,
>>> Joachim
>>>
>>> *Joachim Pouderoux*
>>>
>>> *PhD, Technical Expert*
>>> *Kitware SAS <http://www.kitware.fr>*
>>>
>>>
>>> 2016-04-01 10:06 GMT+02:00 Cindy Castro < <cindy.castro at uvsq.fr>
>>> cindy.castro at uvsq.fr>:
>>>
>>>> Hello,
>>>>
>>>> I am using ParaView in client/server mode with stereo. I have a cluster
>>>> with 4 nodes, 1 GPU each (NVIDIA K5000) and 8 screens for display.
>>>>
>>>> My problem is I can not find how to span a background over my 8
>>>> screens. The background is displayed on each screen. 3D models are well
>>>> displayed in 3D (no problem with that).
>>>>
>>>> The server is run with the command:
>>>> mpirun -np 8 -machinefile
>>>> /opt/software/ParaView/PVscripts/server_machinefile.txt
>>>> /opt/software/ParaView/ParaView-5.0.0-bin/bin/pvserver -rc
>>>> --client-host=mire-pc /opt/software/ParaView/PVresources/wall_config.pvx
>>>>
>>>> I tried tiles mode but the display is not in the right order...
>>>>
>>>> Can you help me ? Is it possible to span a background over several
>>>> screens in 3D mode ? I is really useful when rendering.
>>>>
>>>> Regards,
>>>>
>>>> --
>>>> Cindy CASTRO
>>>> Responsable plateforme DIGISCOPE-MIRE
>>>> Plateforme d'Int?gration et de Tests (PIT)
>>>> --
>>>> Observatoire de Versailles Saint-Quentin-en-Yvelines (OVSQ)
>>>> Quartier des Garennes
>>>> 11 Boulevard d'Alembert
>>>> 78280 Guyancourt
>>>> --
>>>> B?timent principal - RDC - Bureau 215
>>>> T?l : +33 (0)1 80 28 51 03 <%2B33%20%280%291%2080%2028%2051%2003>
>>>> Salle MIRE : +33 (0)1 80 28 54 93
>>>> <%2B33%20%280%291%2080%2028%2054%2093>
>>>>
>>>>
>>>> ---
>>>> L'absence de virus dans ce courrier ?lectronique a ?t? v?rifi?e par le
>>>> logiciel antivirus Avast.
>>>> https://www.avast.com/antivirus
>>>>
>>>> _______________________________________________
>>>> Powered by www.kitware.com
>>>>
>>>> Visit other Kitware open-source projects at
>>>> <http://www.kitware.com/opensource/opensource.html>
>>>> http://www.kitware.com/opensource/opensource.html
>>>>
>>>> Please keep messages on-topic and check the ParaView Wiki at:
>>>> http://paraview.org/Wiki/ParaView
>>>>
>>>> Search the list archives at: <http://markmail.org/search/?q=ParaView>
>>>> http://markmail.org/search/?q=ParaView
>>>>
>>>> Follow this link to subscribe/unsubscribe:
>>>> http://public.kitware.com/mailman/listinfo/paraview
>>>>
>>>
>>>
>>> _______________________________________________
>>> Powered by www.kitware.com
>>>
>>> Visit other Kitware open-source projects at
>>> <http://www.kitware.com/opensource/opensource.html>
>>> http://www.kitware.com/opensource/opensource.html
>>>
>>> Please keep messages on-topic and check the ParaView Wiki at:
>>> http://paraview.org/Wiki/ParaView
>>>
>>> Search the list archives at: http://markmail.org/search/?q=ParaView
>>>
>>> Follow this link to subscribe/unsubscribe:
>>> http://public.kitware.com/mailman/listinfo/paraview
>>>
>>>
>>
>> --
>> Cindy CASTRO
>> Responsable plateforme DIGISCOPE-MIRE
>> Plateforme d'Int?gration et de Tests (PIT)
>> --
>> Observatoire de Versailles Saint-Quentin-en-Yvelines (OVSQ)
>> Quartier des Garennes
>> 11 Boulevard d'Alembert
>> 78280 Guyancourt
>> --
>> B?timent principal - RDC - Bureau 215
>> T?l : +33 (0)1 80 28 51 03
>> Salle MIRE : +33 (0)1 80 28 54 93
>>
>>
>> Cet e-mail a ?t? envoy? depuis un ordinateur prot?g? par Avast.
>> www.avast.com
>> <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160401/99a0bcb5/attachment.html>

From rajphysics.mon at gmail.com  Sat Apr  2 00:03:07 2016
From: rajphysics.mon at gmail.com (Raj Kumar Manna)
Date: Sat, 2 Apr 2016 09:33:07 +0530
Subject: [Paraview] Paraview ray tracing plugin | OSPray
In-Reply-To: <CANjZAi-39s9PBjobG5Ad+RMc6HXpi=BERn=YJ3sk5ML_zirQCQ@mail.gmail.com>
References: <CANt3wQuxvUbiOLOu9pyMqvp2XduM31yKFth_bv2bFOCWGMPMCQ@mail.gmail.com>
 <CANjZAi8ZOSdY=rT=d_bjHroFDUr5vDe_1r2EbFXQxsEkzf81dQ@mail.gmail.com>
 <CANt3wQsphpyv3MmB9G3F_6W0kMiPiRVQJWBXZNbNQnNHtheN8A@mail.gmail.com>
 <CANjZAi-39s9PBjobG5Ad+RMc6HXpi=BERn=YJ3sk5ML_zirQCQ@mail.gmail.com>
Message-ID: <CANt3wQt_bdyHqCHWkCxr-s3M6N8RG4ar6Mf4Ft3sppn3-pjA2A@mail.gmail.com>

Thanks David. It works well with Paraview 5.0.1 binary.

Raj

On Fri, Apr 1, 2016 at 10:41 PM, David E DeMarle <dave.demarle at kitware.com>
wrote:

> Definitely shouldn't do that. The rendering speed should typically be
> about the same as you get with OpenGL but there are many dependent factors
> to that of course.
>
> Is that with the 5.0.0 binary or the recently released 5.0.1 binary? We
> fixed a bug in between 5.0.0 and 5.0.1 that is the likely cause. Other
> things you can try are to disable Progressive Refinement and to build
> ParaView from source. All three have been helpful to others on the list.
>
> thanks
>
>
>
> David E DeMarle
> Kitware, Inc.
> R&D Engineer
> 21 Corporate Drive
> Clifton Park, NY 12065-8662
> Phone: 518-881-4909
>
> On Fri, Apr 1, 2016 at 12:57 PM, Raj Kumar Manna <rajphysics.mon at gmail.com
> > wrote:
>
>> Thanks. It works but very slow. Even a simple sphere rendering hangs my
>> machine. I am using Paraview 5.0 on Intel(R) Xeon(R) CPU E3-1226 v3 @
>> 3.30GHz with 16 GB memory.
>>
>>
>> Raj
>>
>> On Fri, Apr 1, 2016 at 9:50 PM, David E DeMarle <dave.demarle at kitware.com
>> > wrote:
>>
>>> Raj,
>>>
>>> Once you load the plugin, close (or create a new) RenderView window. In
>>> the menu that results, choose the pvOSPRay view. Hit the eye icon in the
>>> pipeline browser to make things visible in the new window. It should work
>>> more or less the same as a standard RenderView, except that the rendering
>>> is done in Intel's OSPRay ray tracing engine instead of rasterization in
>>> OpenGL. There are a handful of OSPRay specific controls on the Display
>>> section of the Properties Tab. Hit the gear icon if you can't find them at
>>> first.
>>>
>>> For more information head over to the developer's (TACC) pages:
>>> http://tacc.github.io/pvOSPRay/
>>>
>>> cheers
>>>
>>> David E DeMarle
>>> Kitware, Inc.
>>> R&D Engineer
>>> 21 Corporate Drive
>>> Clifton Park, NY 12065-8662
>>> Phone: 518-881-4909
>>>
>>> On Fri, Apr 1, 2016 at 12:27 AM, Raj Kumar Manna <
>>> rajphysics.mon at gmail.com> wrote:
>>>
>>>> Dear All,
>>>>
>>>> I came to know the ray tracing plugin for Paraview -OSPray. Is there
>>>> any documentation for this plugin, like we have one for Surface-LIC
>>>> <http://www.paraview.org/Wiki/ParaView/Line_Integral_Convolution>? I
>>>> can load the plugin in my paraview 5.0 but could not figure out how to use
>>>> it.
>>>>
>>>> Thanks your help.
>>>> Raj
>>>>
>>>>
>>>>
>>>> --
>>>> ##################################################################
>>>> Raj Kumar Manna
>>>> Complex Fluid & Biological Physics Lab
>>>> IIT Madras
>>>>
>>>> Ph. No. 8144637401
>>>>
>>>> alternate email: raj at physics.iitm.ac.in <rajphysics.mon at gmail.com>
>>>> ####################################################################
>>>>
>>>> _______________________________________________
>>>> Powered by www.kitware.com
>>>>
>>>> Visit other Kitware open-source projects at
>>>> http://www.kitware.com/opensource/opensource.html
>>>>
>>>> Please keep messages on-topic and check the ParaView Wiki at:
>>>> http://paraview.org/Wiki/ParaView
>>>>
>>>> Search the list archives at: http://markmail.org/search/?q=ParaView
>>>>
>>>> Follow this link to subscribe/unsubscribe:
>>>> http://public.kitware.com/mailman/listinfo/paraview
>>>>
>>>>
>>>
>>
>>
>> --
>> ##################################################################
>> Raj Kumar Manna
>> Complex Fluid & Biological Physics Lab
>> IIT Madras
>>
>> Ph. No. 8144637401
>>
>> alternate email: raj at physics.iitm.ac.in <rajphysics.mon at gmail.com>
>> ####################################################################
>>
>
>


-- 
##################################################################
Raj Kumar Manna
Complex Fluid & Biological Physics Lab
IIT Madras

Ph. No. 8144637401

alternate email: raj at physics.iitm.ac.in <rajphysics.mon at gmail.com>
####################################################################
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160402/b6e2cdce/attachment.html>

From andy.bauer at kitware.com  Sat Apr  2 10:51:14 2016
From: andy.bauer at kitware.com (Andy Bauer)
Date: Sat, 2 Apr 2016 10:51:14 -0400
Subject: [Paraview] EXTERNAL: Re: EXTERNAL: Re: CxxOverlappingAMRExample
 with Catalyst Live
In-Reply-To: <201604011640.u31GenL9028104@msw1.awe.co.uk>
References: <201603311343.u2VDhxw3006257@msw1.awe.co.uk>
 <CAMaOp+E2RNEmixMDDN6D0wmirQGP4O5zmagiAXkAeoA3ag-Qgw@mail.gmail.com>
 <201603311604.u2VG4lXk030041@msw1.awe.co.uk>
 <CAMaOp+GaW9p=mB1vCeGCAHRQLfssqAd5tEOh0E3g1RBS45+D6w@mail.gmail.com>
 <201604011640.u31GenL9028104@msw1.awe.co.uk>
Message-ID: <CAMaOp+GkS71E3dEfV9CiYoY+vBsHEuC8X4v-ONXpy694RLRq1Q@mail.gmail.com>

Hi Jim,

I inlined some response below...

Best,
Andy

On Fri, Apr 1, 2016 at 12:41 PM, <Jim.Eliot at awe.co.uk> wrote:

> Hi Andy,
>
>
>
> Thank you for all the help that you have provided.
>
>
>
> I feel like I don?t quite understand how Catalyst handles the simulation
> data. If I use ParaView Catalyst for large parallel simulations, and I try
> to fetch the entire dataset, does all the data in the problem get sent to
> the client on my workstation?
>

The way it works now is that when you click on the icon next to a filter,
it fetches that data set to whichever pvserver it's connected to, including
the built-in server. So yes, in this case it would try to fetch all of the
data to your client. We've done some work on generating images through
Catalyst and then sending that image to the client. That was done with PyFR.


>
>
> If I am running pvserver in parallel, would that be able to distribute the
> data between the processes? How do I tell Catalyst to connect to the
> pvservers and the pvservers to connect to the client? I guess I can use
> ?client-host and ?server-port on the pvservers and point them to the
> paraview client but how do I make the Catalyst -> pvserver connection?
>

Yes, that should attempt some form of partitioning when it's sent from the
sim/Catalyst to the parallel pvserver. The way to do the connection in this
case is to tell the Catalyst Python script to link to where pvserver is
running ( coprocessor.DoLiveVisualization(datadescription, "localhost",
22222)). Then, run the simulation, pvserver and the GUI client, have the
client connect to pvserver and then in the GUI go through the
Catalyst->Connect... point to where the simulation is running. This should
connect pvserver to the sim. If there's firewalls then it may be a bit more
complex connection. I don't know to what level/size data this has been
pushed to.


>
>
> Thank you for the information regarding AMR grids ? it sounds like this
> approach will work for my application.
>
>
>
> Kind regards,
>
> Jim
>
>
>
>
>
> *From:* Andy Bauer [mailto:andy.bauer at kitware.com]
> *Sent:* 31 March 2016 20:18
> *To:* Eliot Jim AWE <Jim.Eliot at awe1.awe.co.uk>
> *Cc:* paraview at paraview.org
> *Subject:* EXTERNAL: Re: EXTERNAL: Re: [Paraview]
> CxxOverlappingAMRExample with Catalyst Live
>
>
>
> Hi Jim,
>
> Yes, you can have a Catalyst instrumented code connect to something
> running pvserver and have the pvserver connect to the client. At the end of
> the Python generated scripts there should be a line that looks like:
>     coprocessor.DoLiveVisualization(datadescription, "localhost", 22222)
>
> Here you just have to edit it to point to something other than localhost.
>
>
>
> As for overlapping structured grids, there's no convenient
> composite/multiblock data set for that like there is for Cartesian grids.
> What you would need to do is use vtkStructuredGrids with blanking done
> manually and then just add them in as blocks in a vtkMultiBlockDataSet. It
> won't have the structure that the AMR specific composite data sets have so
> it may be a bit slower for some filters but it should work pretty much like
> you want for most stuff. Please let us know if you try this out and get
> unexpected/undesired behaviour.
>
> Best,
>
> Andy
>
>
>
> On Thu, Mar 31, 2016 at 12:05 PM, <Jim.Eliot at awe.co.uk> wrote:
>
> Hi Andy,
>
>
>
> Thanks for your reply. Currently I am looking at the small examples but I
> would like to be able to fetch larger geometries in future. Is it possible
> for the simulation to connect to a parallel pvserver which will send images
> back to the client?
>
>
>
> Putting interactive usage to one side for a moment, is non-uniform AMR
> supported in Catalyst batch? I.e. overlapping structured grids . I couldn?t
> find any references to non-uniform AMR in ParaView while researching.
>
>
>
> Kind regards,
>
> Jim
>
>
>
> *From:* Andy Bauer [mailto:andy.bauer at kitware.com]
> *Sent:* 31 March 2016 16:08
> *To:* Eliot Jim AWE <Jim.Eliot at awe1.awe.co.uk>
> *Cc:* paraview at paraview.org
> *Subject:* EXTERNAL: Re: [Paraview] CxxOverlappingAMRExample with
> Catalyst Live
>
>
>
> Hi Jim,
>
> Yes, currently Overlapping AMR data sets are not supported by Catalyst
> Live. This is because VTK doesn't support sending that data object. That
> would have to be changed in vtkCommunicator::Send(vtkDataObject* data, int
> remoteHandle, int tag).
>
> A workaround would be to use a Threshold filter to convert to a multiblock
> of unstructured grids, use the merge blocks filter and then extract this
> output to the client. You'll get some warnings about the data set not being
> a polydata (think about running a large simulation and trying to transfer
> all of that to a separate server or client). I'm assuming since you're
> trying to fetch the entire data set that the use case isn't for an overly
> large data set.
>
> Cheers,
>
> Andy
>
>
>
> On Thu, Mar 31, 2016 at 9:44 AM, <Jim.Eliot at awe.co.uk> wrote:
>
>
>
> Good afternoon,
>
>
>
> I have been trying to use Catalyst Live with the CxxOverlappingAMRExample
> from the ParaView Catalyst Example Code repository [1] but I see an error
> when I try to visualise the data from a ParaView client. The client
> connects to the simulation successfully and PVTrivialProducer1 appears in
> the Pipeline Browser. The Information tab shows it as an Overlapping AMR
> Dataset with 3 levels. However, when I click on the PVTrivialProducer1
> icon, ParaView prints an error then segfaults. The error is something like:
>
>
>
>     Warning: In <src-dir>/VTK/Parallel/Core/vtkCommunicator.cxx, line 394
>
>     vtkSocketCommunicator (?): Cannot receive vtkOverlappingAMR
>
>
>
> I have tried this with both ParaView 4.4.0 and 5.0.0 with the same
> results. The example works fine when I am using non-Live Catalyst (i.e. it
> writes out a bunch of vtm files that I can read into ParaView).
>
>
>
> So I am wondering, are AMR meshes not supported by Catalyst Live? Do I
> have to handle AMR meshes differently when using Catalyst interactively?
>
>
>
> Many thanks,
>
> Jim
>
>
>
> [1] https://github.com/Kitware/ParaViewCatalystExampleCode
>
>
>
> *Jim Eliot*
>
> *High Performance Computing Group*
>
> AWE, Aldermaston, Reading, RG7 4PR
>
>
>
> The information in this email and in any attachment(s) is commercial in
> confidence. If you are not the named addressee(s) or if you receive this
> email in error then any distribution, copying or use of this communication
> or the information in it is strictly prohibited. Please notify us
> immediately by email at admin.internet(at)awe.co.uk, and then delete this
> message from your computer. While attachments are virus checked, AWE plc
> does not accept any liability in respect of any virus which is not
> detected. AWE Plc Registered in England and Wales Registration No 02763902
> AWE, Aldermaston, Reading, RG7 4PR
>
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview
>
>
>
> The information in this email and in any attachment(s) is commercial in
> confidence. If you are not the named addressee(s) or if you receive this
> email in error then any distribution, copying or use of this communication
> or the information in it is strictly prohibited. Please notify us
> immediately by email at admin.internet(at)awe.co.uk, and then delete this
> message from your computer. While attachments are virus checked, AWE plc
> does not accept any liability in respect of any virus which is not
> detected. AWE Plc Registered in England and Wales Registration No 02763902
> AWE, Aldermaston, Reading, RG7 4PR
>
>
> The information in this email and in any attachment(s) is commercial in
> confidence. If you are not the named addressee(s) or if you receive this
> email in error then any distribution, copying or use of this communication
> or the information in it is strictly prohibited. Please notify us
> immediately by email at admin.internet(at)awe.co.uk, and then delete this
> message from your computer. While attachments are virus checked, AWE plc
> does not accept any liability in respect of any virus which is not
> detected. AWE Plc Registered in England and Wales Registration No 02763902
> AWE, Aldermaston, Reading, RG7 4PR
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160402/a98a9ada/attachment.html>

From nenadus at gmail.com  Sun Apr  3 07:15:35 2016
From: nenadus at gmail.com (Nenad Vujicic)
Date: Sun, 3 Apr 2016 13:15:35 +0200
Subject: [Paraview] ParaView v5 recipes
Message-ID: <CAOr-WQs3n9++g81ZdR2jqc7+e+6rBeaPR2ObRwYS2PgRqqt9Zw@mail.gmail.com>

Hello everyone,

Which one Visual Studio and CMake were used for preparing ParaView v5.0.1
binaries from http://www.paraview.org/download/? It would be great if you
could update page http://www.paraview.org/Wiki/ParaView/Binaries with data
for v5 versions.

I tried to build ParaViewSuperbuild v5.0/v5.0.1 using VS2013 x64 and cmake
v3.4.1 and I got errors for zlib / boost (at least).

Btw, when I inspected your ParaViewSuperbuild v5.0.1 package, I figured out
that zlib (and some others) dependency is build using VS2008 and paraview
using VS2013 (using dumpbin /dependents filename and looking at visual
studio dependents)!? Is this possible? Did you use system zlib for creating
your packages?

Thanks,
Nenad.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160403/392d8e81/attachment.html>

From andrealphus at gmail.com  Sun Apr  3 17:08:01 2016
From: andrealphus at gmail.com (andrealphus)
Date: Sun, 3 Apr 2016 17:08:01 -0400
Subject: [Paraview] threshold animation
Message-ID: <CAHhX17f6EWwuqfwQMuX4boDVF=KKSNeUrKGTYWo01aVkUSV+9Q@mail.gmail.com>

If I want to create an animation where I keep the minimum threshold
constant but vary the maxiun threshold value, what would be the proper
input?

Threshold range(0) ?
Threshold range(1) ?

Ive tried both, neither gives output as expected...

Do I put in a range in the Animation keyframe parameter? Proper syntax?

Thanks!

From mahagras at ucdavis.edu  Mon Apr  4 04:56:00 2016
From: mahagras at ucdavis.edu (Muhammad Hagras)
Date: Mon, 4 Apr 2016 01:56:00 -0700
Subject: [Paraview] Paraview Artwork Usage!
Message-ID: <CAMyF=6TuObUfkS9gGi=XyESauP7NbZ7tR=2LciQ==HVzs9LN3w@mail.gmail.com>

Hi everyone,

I have developed an extensive program for electron tunneling and basically
I render them in a similar way to Paraview,

My question is that can I use the paraview icons in my program which I
intend to distribute it in the future for free ?

Thanks.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160404/d22116e8/attachment.html>

From utkarsh.ayachit at kitware.com  Mon Apr  4 08:52:47 2016
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Mon, 4 Apr 2016 08:52:47 -0400
Subject: [Paraview] Paraview Artwork Usage!
In-Reply-To: <CAMyF=6TuObUfkS9gGi=XyESauP7NbZ7tR=2LciQ==HVzs9LN3w@mail.gmail.com>
References: <CAMyF=6TuObUfkS9gGi=XyESauP7NbZ7tR=2LciQ==HVzs9LN3w@mail.gmail.com>
Message-ID: <CADHSJjD7TtAsVuq4ehNkjNB7vnDZ-nTkYjGC1Xzdr1AzC6CabA@mail.gmail.com>

All artwork in ParaView repository is released under the same
licensing terms as the code i.e with BSD 3-clause license [1].


[1] https://gitlab.kitware.com/paraview/paraview/blob/master/Copyright.txt

On Mon, Apr 4, 2016 at 4:56 AM, Muhammad Hagras <mahagras at ucdavis.edu> wrote:
> Hi everyone,
>
> I have developed an extensive program for electron tunneling and basically I
> render them in a similar way to Paraview,
>
> My question is that can I use the paraview icons in my program which I
> intend to distribute it in the future for free ?
>
> Thanks.
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview
>

From Sean.Ziegeler at engilitycorp.com  Mon Apr  4 11:21:03 2016
From: Sean.Ziegeler at engilitycorp.com (Sean.Ziegeler at engilitycorp.com)
Date: Mon, 4 Apr 2016 15:21:03 +0000
Subject: [Paraview] PVD for Sharing Mesh among Time Steps
In-Reply-To: <57015B02.1070305@bresnan.net>
References: <FEBA4B4A0B6E9A4FA7967C7D9FE897CF50FFCFE0@VACH-MX2.EGL.ENGILITYCORP.COM>,
 <57015B02.1070305@bresnan.net>
Message-ID: <FEBA4B4A0B6E9A4FA7967C7D9FE897CF50FFE914@VACH-MX2.EGL.ENGILITYCORP.COM>

Hi Samuel,
Thanks for the suggestions and the example file.  I'll hang on to that example in case I ever need the multi-part capability!

The potential "mesh sharing" capability for time steps was mentioned in an old mail list post that I ran across when Googling for this feature:
https://cmake.org/pipermail/paraview/2008-February/007118.html
However, perhaps it was done on a branch of ParaView and maybe not ever incorporated into the mainline distributions.

It does mention Ensight Gold format in that mail list thread, which does at least not have any library dependencies.  I'll think about using that, though I'd have to bite the bullet and start from scratch.  The vtu/pvtu format is easier right now because I already have code that writes those out.

Thanks,
Sean

________________________________
From: Samuel Key [samuelkey at bresnan.net]
Sent: Sunday, April 03, 2016 1:03 PM
To: Ziegeler, Sean @ EngilityCorp; Simons, Don @ EngilityCorp
Subject: Re: [Paraview] PVD for Sharing Mesh among Time Steps

Sean,

To my knowledge, *.vtu files all have "a fresh copy" of the nodal point coordinates and connectivity. Hence, when you have time steps (or load steps) you get a lot of files and if the mesh is large (for example, 100x100x100). the files are large. Up to know, the only simulation results format of which I am aware that has a one-time (t=0.0) coordinate and connectivity model data is the ExodusII format.

It is possible to have a single *.pvd file that references both the "parts" and "time steps." I have attached an example.

Hope this helps,

Samuel Key
FMA Development, LLC
1005 39th Ave NE
Great Falls, Montana 59404

On 3/30/2016 6:09 PM, Sean.Ziegeler at engilitycorp.com<mailto:Sean.Ziegeler at engilitycorp.com> wrote:
Hi all,
A few old posts indicate that the PVD format could be used to specify a single mesh (unstructured, in my case) for all time steps without having to repeat the mesh in every vtu/pvtu file.  I can't seem to find any docs or examples on that approach.  I can't seem to generate it from ParaView either.  Does anyone have an example of such a PVD file?

I'll look in the writer source code if I have to, but if an example is readily available, it sure would save me some time.  I know there are other output options too, but I'd like to stick with one that is straightforward and has no dependencies (HDF5, Silo, etc.).

Thanks,
Sean




_______________________________________________
Powered by www.kitware.com<http://www.kitware.com>

Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView

Search the list archives at: http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160404/cd5ac2db/attachment.html>

From wascott at sandia.gov  Mon Apr  4 13:38:03 2016
From: wascott at sandia.gov (Scott, W Alan)
Date: Mon, 4 Apr 2016 17:38:03 +0000
Subject: [Paraview] Surface LIC plugin
Message-ID: <c9a451ac63fe473c8a1d5010e1c1fa8b@ES01AMSNLNT.srn.sandia.gov>

I just tried the Surface LIC plugin, and got totally confused.  Does anyone have any directions on how to make pretty pictures using one of the Sources, or disk_out_ref.exo or the can.exo?

Thanks,

Alan


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160404/bd332aca/attachment.html>

From kmorel at sandia.gov  Mon Apr  4 14:16:50 2016
From: kmorel at sandia.gov (Moreland, Kenneth)
Date: Mon, 4 Apr 2016 18:16:50 +0000
Subject: [Paraview] Surface LIC plugin
Message-ID: <9A01353A-D10A-4143-B8BB-EAE58D37BBBF@sandia.gov>

1. Load disk_out_ref. All variables on. Apply.
2. Add clip plane. Apply.
3. Change representation to ?Surface LIC?

The default options for Surface LIC should pick up the velocity vectors in disk_out_ref. For some reason the surface LIC is not working on the external surface of disk_out_ref. I don?t know why.

-Ken


From: ParaView <paraview-bounces at paraview.org> on behalf of Walter Scott <wascott at sandia.gov>
Date: Monday, April 4, 2016 at 11:38 AM
To: "paraview at paraview.org" <paraview at paraview.org>
Subject: [EXTERNAL] [Paraview] Surface LIC plugin

I just tried the Surface LIC plugin, and got totally confused.  Does anyone have any directions on how to make pretty pictures using one of the Sources, or disk_out_ref.exo or the can.exo?

Thanks,

Alan


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160404/501870d1/attachment.html>

From utkarsh.ayachit at kitware.com  Mon Apr  4 14:21:38 2016
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Mon, 4 Apr 2016 14:21:38 -0400
Subject: [Paraview] Surface LIC plugin
In-Reply-To: <9A01353A-D10A-4143-B8BB-EAE58D37BBBF@sandia.gov>
References: <9A01353A-D10A-4143-B8BB-EAE58D37BBBF@sandia.gov>
Message-ID: <CADHSJjBNsVPEAwu+v2aNpHKv9FJC_V9dH_G8vsEeOX5+oOUp-A@mail.gmail.com>

> For some reason the surface LIC is not working on the external
> surface of disk_out_ref. I don?t know why.

It worked as expected on my Linux box even for just the external
surface of disk_out_ref.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Screenshot from 2016-04-04 14:20:55.png
Type: image/png
Size: 277500 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160404/dd8d5949/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Screenshot from 2016-04-04 14:21:28.png
Type: image/png
Size: 28508 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160404/dd8d5949/attachment-0003.png>

From kmorel at sandia.gov  Mon Apr  4 14:31:15 2016
From: kmorel at sandia.gov (Moreland, Kenneth)
Date: Mon, 4 Apr 2016 18:31:15 +0000
Subject: [Paraview] [EXTERNAL] Re:  Surface LIC plugin
In-Reply-To: <CADHSJjBNsVPEAwu+v2aNpHKv9FJC_V9dH_G8vsEeOX5+oOUp-A@mail.gmail.com>
References: <9A01353A-D10A-4143-B8BB-EAE58D37BBBF@sandia.gov>
 <CADHSJjBNsVPEAwu+v2aNpHKv9FJC_V9dH_G8vsEeOX5+oOUp-A@mail.gmail.com>
Message-ID: <B46D24B0-EE51-4B90-9E00-3A98174EA1A5@sandia.gov>

To specify further, I get the same results on my Mac. I do see the LIC on the surface inside that hole. I was refering to the outside part of the cylinder. But looking more closely at the data, I see that the velocity is 0 there, so that would explain why the LIC is not showing anything there.

-Ken

On 4/4/16, 12:21 PM, "Utkarsh Ayachit" <utkarsh.ayachit at kitware.com> wrote:

>> For some reason the surface LIC is not working on the external
>> surface of disk_out_ref. I don?t know why.
>
>It worked as expected on my Linux box even for just the external
>surface of disk_out_ref.


From utkarsh.ayachit at kitware.com  Mon Apr  4 14:34:01 2016
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Mon, 4 Apr 2016 14:34:01 -0400
Subject: [Paraview] [EXTERNAL] Re:  Surface LIC plugin
In-Reply-To: <B46D24B0-EE51-4B90-9E00-3A98174EA1A5@sandia.gov>
References: <9A01353A-D10A-4143-B8BB-EAE58D37BBBF@sandia.gov>
 <CADHSJjBNsVPEAwu+v2aNpHKv9FJC_V9dH_G8vsEeOX5+oOUp-A@mail.gmail.com>
 <B46D24B0-EE51-4B90-9E00-3A98174EA1A5@sandia.gov>
Message-ID: <CADHSJjCf-0+Ffx2v3a2hzP23_u=CnF5wTJ6CKBrf5mBhO4hRMg@mail.gmail.com>

On Mon, Apr 4, 2016 at 2:31 PM, Moreland, Kenneth <kmorel at sandia.gov> wrote:
> To specify further, I get the same results on my Mac. I do see the LIC on the surface inside that hole. I was refering to the outside part of the cylinder. But looking more closely at the data, I see that the velocity is 0 there, so that would explain why the LIC is not showing anything there.

Ah, yes, that's correct. That was changed a long time ago to just mask
out regions with zero velocity rather than showing noise, which I
believe it did in its initial incarnations.

From kevin.dean at decisionsciencescorp.com  Mon Apr  4 15:46:30 2016
From: kevin.dean at decisionsciencescorp.com (Dean, Kevin)
Date: Mon, 4 Apr 2016 12:46:30 -0700
Subject: [Paraview] ParaView numpy interface question
Message-ID: <CAFvyM3RY9WP2iW5t98YFB1Qeg0nzCrBuRwnOwmbtwHzkOsruSQ@mail.gmail.com>

Hey all,

I have a quick question about setting scalar values with the python macro
inside paraview.

So I have two images that I want to do scalar manipulation with.

*example code:*

from paraview import simple

from vtk.util import numpy_support as npvtk


import vtk.numpy_interface.dataset_adapter as dsa
import pandas as pd

import vtk


scaling_vti = simple.XMLImageDataReader(FileName=[scaling_filename])

scaling_rawData = simple.servermanager.Fetch(scaling_vti)

scaling_data = dsa.WrapDataObject(scaling_rawData)

scaling_array =
pd.DataFrame(npvtk.vtk_to_numpy(data.GetPointData().GetScalars()),
columns=
['scaling_error'])

humans_vti = simple.FindSource(humans_filename)
humans_vti.PointArrayStatus = ['Scattering Density']
humans_rawData = simple.servermanager.Fetch(humans_vti)
humans_data = dsa.WrapDataObject(humans_rawData)
humans_array = pd.DataFrame(npvtk.vtk_to_numpy(humans_data.GetPointData().GetScalars()),
columns=['scalar_intensity'])

new_scalars = pd.DataFrame(humans_array.scalar_intensity * scaling_array.
scaling_error)

data.GetPointData().SetScalars(npvtk.numpy_to_vtk(new_scalars))


After I do this, I can bypass the pipeline (because I haven't figure
out how to use it yet) by

writing this image to a new file then load it again to render it.

Is there a way I can set the paraview image with the new scalar values
and have it render without
having to write it to a file first?

Or, is there a way to convert the
vtk.numpy_interface.dataset_adapter.DataSetAttributes type back
to paraview.servermanager.FieldDataInformation?

Thanks,

Kevin E. Dean

-- 
This email and its contents are confidential. If you are not the intended 
recipient, please do not disclose or use the information within this email 
or its attachments. If you have received this email in error, please report 
the error to the sender by return email and delete this communication from 
your records.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160404/01d9c528/attachment.html>

From tim.gallagher at gatech.edu  Mon Apr  4 14:21:20 2016
From: tim.gallagher at gatech.edu (Gallagher, Timothy P)
Date: Mon, 4 Apr 2016 18:21:20 +0000
Subject: [Paraview] Surface LIC plugin
In-Reply-To: <9A01353A-D10A-4143-B8BB-EAE58D37BBBF@sandia.gov>
References: <9A01353A-D10A-4143-B8BB-EAE58D37BBBF@sandia.gov>
Message-ID: <CO2PR07MB255100EE51848258CC3F7B5F9D9D0@CO2PR07MB2551.namprd07.prod.outlook.com>

Alan,


If you are working on your own data, the LIC plugin expects velocity to be point centered rather than cell centered. If you do it on cell centered data, you'll get just uniform streaks without anything interesting happening.


Tim


________________________________
From: ParaView <paraview-bounces at paraview.org> on behalf of Moreland, Kenneth <kmorel at sandia.gov>
Sent: Monday, April 4, 2016 2:16 PM
To: Scott, W Alan; paraview at paraview.org
Subject: Re: [Paraview] Surface LIC plugin


1. Load disk_out_ref. All variables on. Apply.

2. Add clip plane. Apply.

3. Change representation to "Surface LIC"



The default options for Surface LIC should pick up the velocity vectors in disk_out_ref. For some reason the surface LIC is not working on the external surface of disk_out_ref. I don't know why.



-Ken





From: ParaView <paraview-bounces at paraview.org> on behalf of Walter Scott <wascott at sandia.gov>
Date: Monday, April 4, 2016 at 11:38 AM
To: "paraview at paraview.org" <paraview at paraview.org>
Subject: [EXTERNAL] [Paraview] Surface LIC plugin



I just tried the Surface LIC plugin, and got totally confused.  Does anyone have any directions on how to make pretty pictures using one of the Sources, or disk_out_ref.exo or the can.exo?



Thanks,



Alan




-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160404/825978e9/attachment.html>

From wascott at sandia.gov  Mon Apr  4 16:57:38 2016
From: wascott at sandia.gov (Scott, W Alan)
Date: Mon, 4 Apr 2016 20:57:38 +0000
Subject: [Paraview] [EXTERNAL] Re:  Surface LIC plugin
In-Reply-To: <CADHSJjCf-0+Ffx2v3a2hzP23_u=CnF5wTJ6CKBrf5mBhO4hRMg@mail.gmail.com>
References: <9A01353A-D10A-4143-B8BB-EAE58D37BBBF@sandia.gov>
 <CADHSJjBNsVPEAwu+v2aNpHKv9FJC_V9dH_G8vsEeOX5+oOUp-A@mail.gmail.com>
 <B46D24B0-EE51-4B90-9E00-3A98174EA1A5@sandia.gov>
 <CADHSJjCf-0+Ffx2v3a2hzP23_u=CnF5wTJ6CKBrf5mBhO4hRMg@mail.gmail.com>
Message-ID: <b903e1fbe2224edeaab470203fb5f402@ES01AMSNLNT.srn.sandia.gov>

OK, with all of the very good, simple explanations, I get it.  Nice feature.  Why isn't it enabled by default?  I.e., why do you need to load the optional plugin?

Here is an image I created with the help of Surface LIC.


Alan



-----Original Message-----
From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] 
Sent: Monday, April 04, 2016 12:34 PM
To: Moreland, Kenneth
Cc: Scott, W Alan; paraview at paraview.org
Subject: Re: [EXTERNAL] Re: [Paraview] Surface LIC plugin

On Mon, Apr 4, 2016 at 2:31 PM, Moreland, Kenneth <kmorel at sandia.gov> wrote:
> To specify further, I get the same results on my Mac. I do see the LIC on the surface inside that hole. I was refering to the outside part of the cylinder. But looking more closely at the data, I see that the velocity is 0 there, so that would explain why the LIC is not showing anything there.

Ah, yes, that's correct. That was changed a long time ago to just mask out regions with zero velocity rather than showing noise, which I believe it did in its initial incarnations.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: screenshot80.jpg
Type: image/jpeg
Size: 165530 bytes
Desc: screenshot80.jpg
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160404/d8a7f808/attachment.jpg>

From houssen at ipgp.fr  Tue Apr  5 04:13:42 2016
From: houssen at ipgp.fr (houssen)
Date: Tue, 05 Apr 2016 10:13:42 +0200
Subject: [Paraview] =?utf-8?q?How_to_activate_=28selectively_if_possible_?=
 =?utf-8?q?=3F=29_debug_traces_when_using_ParaView_=3F?=
Message-ID: <bb30f99df3280e88b64d44219535f1cd@imap.ipgp.fr>

How to activate (selectively if possible ?) debug traces when using 
ParaView ?

I am in the process of creating new couples of HDF5 / XDMF files : for 
now, it is bugged, so the XDMF reader crashes when I open it in 
ParaView. I need to "see" why ParaView crashes : that is, I need to 
understand "where and/or why" my HDF5 / XDMF are bugged (and trigger 
later on a crash in ParaView). Ideally, I would need to activate only 
debug traces for xdmf reader.

First, I tried to find (Google search) if a variabe like PARAVIEW_DEBUG 
could be set before running ParaView but it seems no such variable 
exists (this->DebugOn() only helps if you have a problem in one of your 
own filter - this is not the case here). Then, I looked in the GUI 
(menu, options, settings) but I didn't find any way to turn on traces. I 
also tried to get info from gdb but I get a low level of informations 
(stack and some relevant infos but no messages on problems before 
crashing) as my ParaView is built from source in RelWithDebInfo mode 
(I'd like to avoid to recompile in debug : it would take hours...). I 
looked around 
ParaView-v5.0.0-source/VTK/ThirdParty/xdmf2/vtkxdmf2/libsrc/XdmfObject.h 
and 
ParaView-v5.0.0-source/VTK/ThirdParty/xdmf2/vtkxdmf2/libsrc/XdmfObject.cxx 
(XdmfObject::GetGlobalDebug) but it doesn't help really at first glance 
: GetGlobalDebug is not implemented like I would have imagined (thats is 
in a getenv("PARAVIEW_DEBUG")-like way).

More generally, is it possible to activate debug / warning / info 
traces according to "what I would like to do" ? (for instance, 
activating only shrink filter traces but not xdmf reader traces, or the 
opposite ?) This would help understanding / locating problems when they 
occur. It would be a convenient feature.

FH

From Jim.Eliot at awe.co.uk  Tue Apr  5 13:21:31 2016
From: Jim.Eliot at awe.co.uk (Jim.Eliot at awe.co.uk)
Date: Tue, 5 Apr 2016 17:21:31 +0000
Subject: [Paraview] EXTERNAL: Re: EXTERNAL: Re: EXTERNAL: Re:
 CxxOverlappingAMRExample with Catalyst Live
In-Reply-To: <CAMaOp+GkS71E3dEfV9CiYoY+vBsHEuC8X4v-ONXpy694RLRq1Q@mail.gmail.com>
References: <201603311343.u2VDhxw3006257@msw1.awe.co.uk>
 <CAMaOp+E2RNEmixMDDN6D0wmirQGP4O5zmagiAXkAeoA3ag-Qgw@mail.gmail.com>
 <201603311604.u2VG4lXk030041@msw1.awe.co.uk>
 <CAMaOp+GaW9p=mB1vCeGCAHRQLfssqAd5tEOh0E3g1RBS45+D6w@mail.gmail.com>
 <201604011640.u31GenL9028104@msw1.awe.co.uk>
 <CAMaOp+GkS71E3dEfV9CiYoY+vBsHEuC8X4v-ONXpy694RLRq1Q@mail.gmail.com>
Message-ID: <201604051720.u35HKUuP015230@msw1.awe.co.uk>

Hi Andy,

Your explanation made it a lot clearer for me. I tested it out with multiple pvservers running on a single node and I was able to connect with my simulation. Success!

However, when I tried running pvservers across more than one node, the Catalyst connection failed. I saw a bunch of error messages that look like this:

ERROR: In <src_dir>/VTK/Common/System/vtkSocket.cxx, line 481
vtkClientSocket (?): Socket error in call to connect. Connection refused.

ERROR: In <src_dir>/VTK/Common/System/vtkClientSocket.cxx, line 53
vtkClientSocket (?): Failed to connect to server localhost:22228

ERROR: In <src_dir>/VTK/Parallel/Core/vtkSocketCommunicator.cxx, line 714
vtkSocketCommunicator (?): Can not connect to localhost on port 22228

There were a bunch more of these with various socket numbers.

Do you have any idea what might be causing this problem?

In my coproc.py file I have a line that looks like this:

    coprocess.DoLiveVisualization(datadescription, ?localhost?, 22222)

Do I have to call DoLiveVisualization differently when running across multiple nodes? Do I need to set the host differently maybe? Or is the problem more likely to be at my end?

Many thanks

Kind regards,
Jim

From: Andy Bauer [mailto:andy.bauer at kitware.com]
Sent: 02 April 2016 15:51
To: Eliot Jim AWE <Jim.Eliot at awe1.awe.co.uk>
Cc: paraview at paraview.org
Subject: EXTERNAL: Re: EXTERNAL: Re: EXTERNAL: Re: [Paraview] CxxOverlappingAMRExample with Catalyst Live

Hi Jim,
I inlined some response below...
Best,
Andy

On Fri, Apr 1, 2016 at 12:41 PM, <Jim.Eliot at awe.co.uk<mailto:Jim.Eliot at awe.co.uk>> wrote:
Hi Andy,

Thank you for all the help that you have provided.

I feel like I don?t quite understand how Catalyst handles the simulation data. If I use ParaView Catalyst for large parallel simulations, and I try to fetch the entire dataset, does all the data in the problem get sent to the client on my workstation?

The way it works now is that when you click on the icon next to a filter, it fetches that data set to whichever pvserver it's connected to, including the built-in server. So yes, in this case it would try to fetch all of the data to your client. We've done some work on generating images through Catalyst and then sending that image to the client. That was done with PyFR.


If I am running pvserver in parallel, would that be able to distribute the data between the processes? How do I tell Catalyst to connect to the pvservers and the pvservers to connect to the client? I guess I can use ?client-host and ?server-port on the pvservers and point them to the paraview client but how do I make the Catalyst -> pvserver connection?

Yes, that should attempt some form of partitioning when it's sent from the sim/Catalyst to the parallel pvserver. The way to do the connection in this case is to tell the Catalyst Python script to link to where pvserver is running ( coprocessor.DoLiveVisualization(datadescription, "localhost", 22222)). Then, run the simulation, pvserver and the GUI client, have the client connect to pvserver and then in the GUI go through the Catalyst->Connect... point to where the simulation is running. This should connect pvserver to the sim. If there's firewalls then it may be a bit more complex connection. I don't know to what level/size data this has been pushed to.


Thank you for the information regarding AMR grids ? it sounds like this approach will work for my application.

Kind regards,
Jim


From: Andy Bauer [mailto:andy.bauer at kitware.com<mailto:andy.bauer at kitware.com>]
Sent: 31 March 2016 20:18
To: Eliot Jim AWE <Jim.Eliot at awe1.awe.co.uk<mailto:Jim.Eliot at awe1.awe.co.uk>>
Cc: paraview at paraview.org<mailto:paraview at paraview.org>
Subject: EXTERNAL: Re: EXTERNAL: Re: [Paraview] CxxOverlappingAMRExample with Catalyst Live

Hi Jim,
Yes, you can have a Catalyst instrumented code connect to something running pvserver and have the pvserver connect to the client. At the end of the Python generated scripts there should be a line that looks like:
    coprocessor.DoLiveVisualization(datadescription, "localhost", 22222)
Here you just have to edit it to point to something other than localhost.

As for overlapping structured grids, there's no convenient composite/multiblock data set for that like there is for Cartesian grids. What you would need to do is use vtkStructuredGrids with blanking done manually and then just add them in as blocks in a vtkMultiBlockDataSet. It won't have the structure that the AMR specific composite data sets have so it may be a bit slower for some filters but it should work pretty much like you want for most stuff. Please let us know if you try this out and get unexpected/undesired behaviour.
Best,
Andy

On Thu, Mar 31, 2016 at 12:05 PM, <Jim.Eliot at awe.co.uk<mailto:Jim.Eliot at awe.co.uk>> wrote:
Hi Andy,

Thanks for your reply. Currently I am looking at the small examples but I would like to be able to fetch larger geometries in future. Is it possible for the simulation to connect to a parallel pvserver which will send images back to the client?

Putting interactive usage to one side for a moment, is non-uniform AMR supported in Catalyst batch? I.e. overlapping structured grids . I couldn?t find any references to non-uniform AMR in ParaView while researching.

Kind regards,
Jim

From: Andy Bauer [mailto:andy.bauer at kitware.com<mailto:andy.bauer at kitware.com>]
Sent: 31 March 2016 16:08
To: Eliot Jim AWE <Jim.Eliot at awe1.awe.co.uk<mailto:Jim.Eliot at awe1.awe.co.uk>>
Cc: paraview at paraview.org<mailto:paraview at paraview.org>
Subject: EXTERNAL: Re: [Paraview] CxxOverlappingAMRExample with Catalyst Live

Hi Jim,
Yes, currently Overlapping AMR data sets are not supported by Catalyst Live. This is because VTK doesn't support sending that data object. That would have to be changed in vtkCommunicator::Send(vtkDataObject* data, int remoteHandle, int tag).
A workaround would be to use a Threshold filter to convert to a multiblock of unstructured grids, use the merge blocks filter and then extract this output to the client. You'll get some warnings about the data set not being a polydata (think about running a large simulation and trying to transfer all of that to a separate server or client). I'm assuming since you're trying to fetch the entire data set that the use case isn't for an overly large data set.
Cheers,
Andy

On Thu, Mar 31, 2016 at 9:44 AM, <Jim.Eliot at awe.co.uk<mailto:Jim.Eliot at awe.co.uk>> wrote:

Good afternoon,

I have been trying to use Catalyst Live with the CxxOverlappingAMRExample from the ParaView Catalyst Example Code repository [1] but I see an error when I try to visualise the data from a ParaView client. The client connects to the simulation successfully and PVTrivialProducer1 appears in the Pipeline Browser. The Information tab shows it as an Overlapping AMR Dataset with 3 levels. However, when I click on the PVTrivialProducer1 icon, ParaView prints an error then segfaults. The error is something like:

    Warning: In <src-dir>/VTK/Parallel/Core/vtkCommunicator.cxx, line 394
    vtkSocketCommunicator (?): Cannot receive vtkOverlappingAMR

I have tried this with both ParaView 4.4.0 and 5.0.0 with the same results. The example works fine when I am using non-Live Catalyst (i.e. it writes out a bunch of vtm files that I can read into ParaView).

So I am wondering, are AMR meshes not supported by Catalyst Live? Do I have to handle AMR meshes differently when using Catalyst interactively?

Many thanks,
Jim

[1] https://github.com/Kitware/ParaViewCatalystExampleCode

Jim Eliot
High Performance Computing Group
AWE, Aldermaston, Reading, RG7 4PR


The information in this email and in any attachment(s) is commercial in confidence. If you are not the named addressee(s) or if you receive this email in error then any distribution, copying or use of this communication or the information in it is strictly prohibited. Please notify us immediately by email at admin.internet(at)awe.co.uk<http://awe.co.uk>, and then delete this message from your computer. While attachments are virus checked, AWE plc does not accept any liability in respect of any virus which is not detected. AWE Plc Registered in England and Wales Registration No 02763902 AWE, Aldermaston, Reading, RG7 4PR

_______________________________________________
Powered by www.kitware.com<http://www.kitware.com>

Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView

Search the list archives at: http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview

The information in this email and in any attachment(s) is commercial in confidence. If you are not the named addressee(s) or if you receive this email in error then any distribution, copying or use of this communication or the information in it is strictly prohibited. Please notify us immediately by email at admin.internet(at)awe.co.uk<http://awe.co.uk>, and then delete this message from your computer. While attachments are virus checked, AWE plc does not accept any liability in respect of any virus which is not detected. AWE Plc Registered in England and Wales Registration No 02763902 AWE, Aldermaston, Reading, RG7 4PR

The information in this email and in any attachment(s) is commercial in confidence. If you are not the named addressee(s) or if you receive this email in error then any distribution, copying or use of this communication or the information in it is strictly prohibited. Please notify us immediately by email at admin.internet(at)awe.co.uk<http://awe.co.uk>, and then delete this message from your computer. While attachments are virus checked, AWE plc does not accept any liability in respect of any virus which is not detected. AWE Plc Registered in England and Wales Registration No 02763902 AWE, Aldermaston, Reading, RG7 4PR



The information in this email and in any attachment(s) is 
commercial in confidence. If you are not the named addressee(s) 
or 
if you receive this email in error then any distribution, copying or 
use of this communication or the information in it is strictly 
prohibited. Please notify us immediately by email at 
admin.internet(at)awe.co.uk, and then delete this message from 
your computer. While attachments are virus checked, AWE plc 
does not accept any liability in respect of any virus which is not 
detected.

AWE Plc
Registered in England and Wales
Registration No 02763902
AWE, Aldermaston, Reading, RG7 4PR

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160405/7469d2d5/attachment.html>

From ecoon at lanl.gov  Tue Apr  5 14:41:39 2016
From: ecoon at lanl.gov (Coon, Ethan)
Date: Tue, 5 Apr 2016 18:41:39 +0000
Subject: [Paraview] bug in ExodusII reader for general polyhedral meshes
Message-ID: <D3296301.B7F2%ecoon@lanl.gov>

Hello,

After discussion with a lot of meshing people, and especially Greg Sjaardema at SNL, the ExodusII lead, I believe there is a bug in the ExodusII reader for the case of arbitrary polyhedra.

Below is an extremely detailed description of the issue, along with a response by Greg explaining what is correct for Exodus.   Effectively the current reader expects that there are the same number of face blocks as element blocks in the arbitrary polyhedral format, and this is not the correct data layout of an ExodusII file.  I?ve attached two files ? example_layout1.exo which is incorrect ExodusII format but works in Paraview, and example_layout2.exo which is correct ExodusII but crashes Paraview.

How/where should this be fixed?

Thanks,

Ethan



?
--------------------------------------------------------------
Ethan Coon
Research Scientist
Computational Earth Sciences -- EES-16
Los Alamos National Laboratory
505-665-8289

http://www.lanl.gov/expertise/profiles/view/ethan-coon<https://mymail.lanl.gov/ecp/Customize/redir.aspx?C=EYTyoFLRN0KpSCb8HNnAI5EfC_Qfws8Iuxxx4BGy4Wbt7_iUuRifrnA1vyJbHgXsVlp18WCFniw.&URL=http%3a%2f%2fwww.ldeo.columbia.edu%2f%7eecoon%2f>
--------------------------------------------------------------




On 03/16/16 12:08, Sjaardema, Gregory D wrote:

The correct representation is closeer to layout 2.  The faces are referenced
in a ?file implicit? id?basically the same way that elements are referenced
in sideset definitions.  (This is what you refer to as ?global? numbering,
but I typically use global ids to refer to the ids generated by the maps;
the implicit ordering is the 1..num_entity based on the definition order in
the file). The implicit id relies on the order of the face blocks in the
file and the order of the faces within the blocks.

The primary difference from your layout 2 is that you can have multiple face
blocks.  For example, you could define a face block with QUAD faces and then
another face block with your 5-gons (NSIDED) and then your element blocks
could refer to faces from either of the face blocks. You can also have
multiple arbitrary-polygon face blocks.

You are correct that the layout 1 causes invalid meshes due to ?duplicated?
faces on the interface between contiguous element blocks. However, exodus
won?t recognize them as duplicated and instead it will refer to two
coincident but distinct faces.

I think much of the confusion comes from the scarcity of documentation on
the exodus arbitrary polyhedra capabilty and that there is typically only a
single test mesh in the test suite and it only has a single element block.
I will try to get some time to generate some additional polyhedra tests and
the documentation, but not sure when I can get to it.

If anyone sees a reason why the multi-face-block-layout-2 does not make
sense, let me know.
..Greg

--
"A supercomputer is a device for turning compute-bound problems into
I/O-bound problems?

From: "Coon, Ethan" <ecoon at lanl.gov<mailto:ecoon at lanl.gov>>
Date: Wednesday, March 16, 2016 at 10:52 AM
To: "Sjaardema, Gregory D" <gdsjaar at sandia.gov<mailto:gdsjaar at sandia.gov>>
Cc: "Garimella, Rao Veerabhadra (LANL)" <rao at lanl.gov<mailto:rao at lanl.gov>>, "Vijay S. Mahadevan
[vijay.m at gmail.com<mailto:vijay.m at gmail.com>]" <vijay.m at gmail.com<mailto:vijay.m at gmail.com>>, "Grindeanu, Iulian R.
[iulian at mcs.anl.gov<mailto:iulian at mcs.anl.gov>]" <iulian at mcs.anl.gov<mailto:iulian at mcs.anl.gov>>, "markmiller at llnl.gov<mailto:markmiller at llnl.gov>"
<markmiller at llnl.gov<mailto:markmiller at llnl.gov>>
Subject: [EXTERNAL] ExodusII and arbitrary polyhedra

Hi all, and especially Greg,

I've been working on a project that needs multi-material, arbitrary
polyhedral meshes. After significant discussions with multiple people, I've
discovered a few inconsistencies between how various software packages
assume ExodusII files lay out these types of meshes. Clarification would be
helpful so that these tools can work together!


Throughout I will use the motivating example, for which I've attached two
ExodusII files, one in each layout:
- 2 pentagonal-prisms (i.e. a 7-faced object, where the top and bottom faces
are 5-gons, and all other faces are 4-gons, see
https://en.wikipedia.org/wiki/Pentagonal_prism)
- 2 materials (one prism in each)


ExodusII file layout 1 (format assumed by Paraview/VisIt readers, which I
believe are the same code?  Maybe written/maintained by Mark?):

- two element blocks
- two face blocks
- each element block uses a "face id" that is implied by a block-local
numbering of the faces in its face block. So in element block 2, we have:

facconn1 = 1, 2, 3, 4, 5, 6, 7 ;
facconn2 = 1, 2, 3, 4, 5, 6, 7 ;

fbepecnt1 = 5, 5, 4, 4, 4, 4, 4 ;
fbepecnt2= 5, 5, 4, 4, 4, 4, 4 ;

Effectively each of these are indices into their BLOCK list of faces.

ExodusII file layout 2 (format assumed by MSTK, written/maintained by Rao):

- two element blocks
- one or more face blocks
- each element block uses a "face id" that is implied by a global numbering
of the faces in all face blocks.  So, in element block 2 we have:

  facconn1 = 1, 2, 4, 6, 8, 10, 12 ;
  facconn2 = 2, 3, 5, 7, 9, 11, 13 ;

  fbepecnt1 = 5, 5, 5, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4 ;

with one and only one face_blk.

This is often just one and only one face block, where all element block face
lists refer to that same face block.



Note that these two are mutually exclusive -- meshes built in layout 1 crash
MSTK and meshes built in layout 2 crash Paraview/VisIt.

I have a bit of an opinion here.  The former may seem natural, in the sense
that each element block has its own faces, but I think it results in
not-well-posed meshes.  In the former, the shared face at the interface of
the two materials is listed twice -- it must exist in both face blocks.  To
me, the former is a specification for two independent (non-connected) meshes
that share a boundary -- the boundary face is duplicated.  It should be
valid Exodus, but it should not refer to a topologically connected mesh.  It
is geometrically, but not topologically, degenerate.  This is useful for
things like fault modeling, where the domain really is a "punctured" domain
and boundary conditions may be applied on both faces, independently.  This
should be distinguished from the typical case, where these are two layers in
the same mesh, and there is only one face on the interface.

The second recognizes that faces, like nodes, which are globally listed in a
single block, are the interface between blocks, and they do not belong to
either material 1 or material 2.  It is both topologically and geometrically
"degenerate" in the sense that both elements point to the same face.

Greg, can you weigh in here with your thoughts on which, or neither, is
"correct?"  And can a decision be made so that MOAB, Paraview, MSTK, and
VisIt can all work with the same format?  Anyone else have comments/thoughts
on this?  Is there anyone else that might care about this answer?

Thanks,

Ethan




-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160405/8e4c21b0/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: example_layout2.exo
Type: application/octet-stream
Size: 3140 bytes
Desc: example_layout2.exo
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160405/8e4c21b0/attachment.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: example_layout1.exo
Type: application/octet-stream
Size: 3440 bytes
Desc: example_layout1.exo
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160405/8e4c21b0/attachment-0001.obj>

From wascott at sandia.gov  Tue Apr  5 16:59:58 2016
From: wascott at sandia.gov (Scott, W Alan)
Date: Tue, 5 Apr 2016 20:59:58 +0000
Subject: [Paraview] [EXTERNAL] bug in ExodusII reader for general
 polyhedral meshes
In-Reply-To: <D3296301.B7F2%ecoon@lanl.gov>
References: <D3296301.B7F2%ecoon@lanl.gov>
Message-ID: <dbc09787d09e48909eaf56cee7e56066@ES01AMSNLNT.srn.sandia.gov>

Ethan/ all,
Good catch, good research.  Since this is an Exodus bug, and thus will affect Sandia, I wrote it up in the bug tracker.  I also took it as a Sandia bug.  Unless things change, it is scheduled to be fixed for the next release - version 5.1.

You can keep up with this bug here:  http://www.paraview.org/Bug/view.php?id=16062.

Alan

From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Coon, Ethan
Sent: Tuesday, April 05, 2016 12:42 PM
To: paraview at paraview.org
Subject: [EXTERNAL] [Paraview] bug in ExodusII reader for general polyhedral meshes

Hello,

After discussion with a lot of meshing people, and especially Greg Sjaardema at SNL, the ExodusII lead, I believe there is a bug in the ExodusII reader for the case of arbitrary polyhedra.

Below is an extremely detailed description of the issue, along with a response by Greg explaining what is correct for Exodus.   Effectively the current reader expects that there are the same number of face blocks as element blocks in the arbitrary polyhedral format, and this is not the correct data layout of an ExodusII file.  I've attached two files - example_layout1.exo which is incorrect ExodusII format but works in Paraview, and example_layout2.exo which is correct ExodusII but crashes Paraview.

How/where should this be fixed?

Thanks,

Ethan



-
--------------------------------------------------------------
Ethan Coon
Research Scientist
Computational Earth Sciences -- EES-16
Los Alamos National Laboratory
505-665-8289

http://www.lanl.gov/expertise/profiles/view/ethan-coon
--------------------------------------------------------------




On 03/16/16 12:08, Sjaardema, Gregory D wrote:

The correct representation is closeer to layout 2.  The faces are referenced
in a "file implicit" id-basically the same way that elements are referenced
in sideset definitions.  (This is what you refer to as "global" numbering,
but I typically use global ids to refer to the ids generated by the maps;
the implicit ordering is the 1..num_entity based on the definition order in
the file). The implicit id relies on the order of the face blocks in the
file and the order of the faces within the blocks.

The primary difference from your layout 2 is that you can have multiple face
blocks.  For example, you could define a face block with QUAD faces and then
another face block with your 5-gons (NSIDED) and then your element blocks
could refer to faces from either of the face blocks. You can also have
multiple arbitrary-polygon face blocks.

You are correct that the layout 1 causes invalid meshes due to "duplicated"
faces on the interface between contiguous element blocks. However, exodus
won't recognize them as duplicated and instead it will refer to two
coincident but distinct faces.

I think much of the confusion comes from the scarcity of documentation on
the exodus arbitrary polyhedra capabilty and that there is typically only a
single test mesh in the test suite and it only has a single element block.
I will try to get some time to generate some additional polyhedra tests and
the documentation, but not sure when I can get to it.

If anyone sees a reason why the multi-face-block-layout-2 does not make
sense, let me know.
..Greg

--
"A supercomputer is a device for turning compute-bound problems into
I/O-bound problems"

From: "Coon, Ethan" <ecoon at lanl.gov<mailto:ecoon at lanl.gov>>
Date: Wednesday, March 16, 2016 at 10:52 AM
To: "Sjaardema, Gregory D" <gdsjaar at sandia.gov<mailto:gdsjaar at sandia.gov>>
Cc: "Garimella, Rao Veerabhadra (LANL)" <rao at lanl.gov<mailto:rao at lanl.gov>>, "Vijay S. Mahadevan
[vijay.m at gmail.com<mailto:vijay.m at gmail.com>]" <vijay.m at gmail.com<mailto:vijay.m at gmail.com>>, "Grindeanu, Iulian R.
[iulian at mcs.anl.gov<mailto:iulian at mcs.anl.gov>]" <iulian at mcs.anl.gov<mailto:iulian at mcs.anl.gov>>, "markmiller at llnl.gov<mailto:markmiller at llnl.gov>"
<markmiller at llnl.gov<mailto:markmiller at llnl.gov>>
Subject: [EXTERNAL] ExodusII and arbitrary polyhedra

Hi all, and especially Greg,

I've been working on a project that needs multi-material, arbitrary
polyhedral meshes. After significant discussions with multiple people, I've
discovered a few inconsistencies between how various software packages
assume ExodusII files lay out these types of meshes. Clarification would be
helpful so that these tools can work together!


Throughout I will use the motivating example, for which I've attached two
ExodusII files, one in each layout:
- 2 pentagonal-prisms (i.e. a 7-faced object, where the top and bottom faces
are 5-gons, and all other faces are 4-gons, see
https://en.wikipedia.org/wiki/Pentagonal_prism)
- 2 materials (one prism in each)


ExodusII file layout 1 (format assumed by Paraview/VisIt readers, which I
believe are the same code?  Maybe written/maintained by Mark?):

- two element blocks
- two face blocks
- each element block uses a "face id" that is implied by a block-local
numbering of the faces in its face block. So in element block 2, we have:

facconn1 = 1, 2, 3, 4, 5, 6, 7 ;
facconn2 = 1, 2, 3, 4, 5, 6, 7 ;

fbepecnt1 = 5, 5, 4, 4, 4, 4, 4 ;
fbepecnt2= 5, 5, 4, 4, 4, 4, 4 ;

Effectively each of these are indices into their BLOCK list of faces.

ExodusII file layout 2 (format assumed by MSTK, written/maintained by Rao):

- two element blocks
- one or more face blocks
- each element block uses a "face id" that is implied by a global numbering
of the faces in all face blocks.  So, in element block 2 we have:

  facconn1 = 1, 2, 4, 6, 8, 10, 12 ;
  facconn2 = 2, 3, 5, 7, 9, 11, 13 ;

  fbepecnt1 = 5, 5, 5, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4 ;

with one and only one face_blk.

This is often just one and only one face block, where all element block face
lists refer to that same face block.



Note that these two are mutually exclusive -- meshes built in layout 1 crash
MSTK and meshes built in layout 2 crash Paraview/VisIt.

I have a bit of an opinion here.  The former may seem natural, in the sense
that each element block has its own faces, but I think it results in
not-well-posed meshes.  In the former, the shared face at the interface of
the two materials is listed twice -- it must exist in both face blocks.  To
me, the former is a specification for two independent (non-connected) meshes
that share a boundary -- the boundary face is duplicated.  It should be
valid Exodus, but it should not refer to a topologically connected mesh.  It
is geometrically, but not topologically, degenerate.  This is useful for
things like fault modeling, where the domain really is a "punctured" domain
and boundary conditions may be applied on both faces, independently.  This
should be distinguished from the typical case, where these are two layers in
the same mesh, and there is only one face on the interface.

The second recognizes that faces, like nodes, which are globally listed in a
single block, are the interface between blocks, and they do not belong to
either material 1 or material 2.  It is both topologically and geometrically
"degenerate" in the sense that both elements point to the same face.

Greg, can you weigh in here with your thoughts on which, or neither, is
"correct?"  And can a decision be made so that MOAB, Paraview, MSTK, and
VisIt can all work with the same format?  Anyone else have comments/thoughts
on this?  Is there anyone else that might care about this answer?

Thanks,

Ethan




-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160405/dab836f9/attachment.html>

From M.Deij at marin.nl  Wed Apr  6 04:23:20 2016
From: M.Deij at marin.nl (Deij-van Rijswijk, Menno)
Date: Wed, 6 Apr 2016 08:23:20 +0000
Subject: [Paraview] Superbuild RPM error (python bytecode compile)
Message-ID: <354d8e64cbad4679ac0055d0df2687a5@MAR190n2.marin.local>

Hi all,

I?m trying to build ParaView using the super build. Everything works, except the creation of an RPM.

When I say everything works, I mean:
* I am able to install ParaView to a location in my user directory (~Programs/) and run ParaView from there.
* I can package a tar.gz using cpack -G TGZ - this gives me the .tar.gz file as expected.

I would like, however, to get an RPM, and that is not successful. Looking at the rpmbuild.out and .err (attached), I see that it stops when byte-compiling Python. It seems to choke on the py3_test_grammar.py

The problem seems very similar to this https://github.com/nmilford/rpm-python27/issues/6
and the solution they suggest is to add

%global _python_bytecompile_errors_terminate_build 0

On top of the RPM SPEC file. The problem is, however, that the SPEC file is generated by CPack, so I'm at a loss how to fix this.

Any suggestions are welcome!

Thanks and best wishes,


Menno Deij - van Rijswijk



dr. ir. Menno A. Deij-van Rijswijk  | Researcher / Software Engineer | Maritime Simulation & Software Group
MARIN | T +31 317 49 35 06 | mailto:M.Deij at marin.nl | http://www.marin.nl

MARIN news: http://www.marin.nl/web/News/News-items/Software-Seminar-in-Houston-October-4.htm

-------------- next part --------------
A non-text attachment was scrubbed...
Name: rpmbuild.err
Type: application/octet-stream
Size: 1849 bytes
Desc: rpmbuild.err
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160406/11ef645f/attachment.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: rpmbuild.out
Type: application/octet-stream
Size: 4598 bytes
Desc: rpmbuild.out
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160406/11ef645f/attachment-0001.obj>

From rajphysics.mon at gmail.com  Wed Apr  6 08:52:22 2016
From: rajphysics.mon at gmail.com (Raj Kumar Manna)
Date: Wed, 6 Apr 2016 18:22:22 +0530
Subject: [Paraview] Povray exporter : color map
Message-ID: <CANt3wQtmqMfYenDDRCidvrHEbUODwVG3Zzz5PhzrNGhf2mU5Tw@mail.gmail.com>

Dear All,

Is it possible to export scene to povray with color map? As suggested by
this thread <https://cmake.org/pipermail/paraview/2010-March/016327.html>,
I have  tried without "vtkMapper::InterpolateScalarsBeforeMapping" in
Paraview 5.0.0. It does not export to povray with color map but only export
meshes with a single white color.

Thanks for you help.

Raj

-- 
##################################################################
Raj Kumar Manna
Complex Fluid & Biological Physics Lab
IIT Madras

Ph. No. 8144637401

alternate email: raj at physics.iitm.ac.in <rajphysics.mon at gmail.com>
####################################################################
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160406/d6658068/attachment.html>

From zeus_7hc at yahoo.de  Wed Apr  6 13:52:27 2016
From: zeus_7hc at yahoo.de (Thomas Engels)
Date: Wed, 6 Apr 2016 19:52:27 +0200
Subject: [Paraview] eyedomelightning in paraview 5?
Message-ID: <57054CDB.8090608@yahoo.de>

Hello,

I used to use the EyeDomeLightning plugin ( see e.g.,
https://blog.kitware.com/eye-dome-lighting-a-non-photorealistic-shading-technique/ 
)
However, support for it seems to be dropped in the newest paraview
versions (>5.0).
Is it planned to re-include the plugin? Can it somehow still be used?
I found it a very helpful tool to create appealing visualizations.

Best regards
Thomas Engels

-- Thomas Engels, Ph.D. Postdoctoral Researcher AIFIT Project (Flying
insects in turbulence) Institut f?r Str?mungsmechanik und Technische
Akustik FG Numerische Fluiddynamik (MB123) M?ller-Breslau-Strasse 8
10623 Berlin Germany +49 30 314 22849 ?cole normale sup?rieure
Laboratoire de M?t?orologie Dynamique 24, Rue Lhomond 75231 Paris Cedex
05 France

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160406/e88822bb/attachment.html>

From megdich_islem at yahoo.fr  Wed Apr  6 15:21:46 2016
From: megdich_islem at yahoo.fr (Megdich Islem)
Date: Wed, 6 Apr 2016 19:21:46 +0000 (UTC)
Subject: [Paraview] question-filter
In-Reply-To: <961645139.3117877.1459266210514.JavaMail.yahoo@mail.yahoo.com>
References: <961645139.3117877.1459266210514.JavaMail.yahoo@mail.yahoo.com>
Message-ID: <326952444.783104.1459970506204.JavaMail.yahoo@mail.yahoo.com>

Hi,
Can I ask if there is any update with the filter problem giving negative volume. I get stuck !!!
Regards,Islem 

    Le Mardi 29 mars 2016 16h46, Megdich Islem via ParaView <paraview at paraview.org> a ?crit :
 

 Hi,
Thank you, I tried volume(inputs[0]), I got no error and no result in the renderview. But, I got a data called result in the information panel, the data range is [-1, 1.544e-06]. Is this what I normally need to get ? Does the data range mean that the cells are of negative volume.I attached picture that show information panel before and after applying the pythonCalculator.
Regards,Islem 

    Le Mardi 29 mars 2016 14h06, Utkarsh Ayachit <utkarsh.ayachit at kitware.com> a ?crit :
 

 > Thank you for your email. I used volume(input) expression for my case and
> for the sphere from the the sources but again I got an error in both of
> cases which is AttributeError: 'builtin_function_or_method' object has no
> attribute 'NewInstance'. See picture attached.

Use "inputs[0]" instead of "input" e.g. volume(inputs[0]).


   
_______________________________________________
Powered by www.kitware.com

Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView

Search the list archives at: http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview


  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160406/f61d57ef/attachment.html>

From ruggiero.guida at gmail.com  Thu Apr  7 08:16:24 2016
From: ruggiero.guida at gmail.com (Ruggiero Guida)
Date: Thu, 07 Apr 2016 12:16:24 +0000
Subject: [Paraview] Non-uniform colormaps in Paraview
Message-ID: <CA+U776A4TQKxj45CRVWgR19NYk=HKcz-EPtVu73q-3DMiv-Fjw@mail.gmail.com>

Hi,

I am trying to create a non-uniform colormap in Paraview 4.4 (OSX).

The final goal is to generate a contour with discrete bands based on the
colours in this image

http://james-ramsden.com/wp-content/uploads/2015/07/UTCI_scale.png

My current colormap file is

<ColorMaps>
    <ColorMap name="UTCILabels" space="RGB">
        <Point x="-99.0" o="1.0" r="0.011765" g="0.090196" b="0.564706"/>
        <Point x="-40.0" o="1.0" r="0.023529" g="0.141176" b="0.792157"/>
        <Point x="-27.0" o="1.0" r="0.035294" g="0.188235" b="0.984314"/>
        <Point x="-13.0" o="1.0" r="0.000000" g="0.474510" b="1.000000"/>
        <Point x="0.0" o="1.0" r="0.000000" g="0.792157" b="1.000000"/>
        <Point x="9.0" o="1.0" r="0.000000" g="0.772549" b="0.000000"/>
        <Point x="26.0" o="1.0" r="1.000000" g="0.568627" b="0.000000"/>
        <Point x="32.0" o="1.0" r="0.996078" g="0.152941" b="0.000000"/>
        <Point x="38.0" o="1.0" r="0.800000" g="0.113725" b="0.000000"/>
        <Point x="46.0" o="1.0" r="0.576471" g="0.066667" b="0.000000"/>
        <Point x="99.0" o="1.0" r="0.576471" g="0.066667" b="0.000000"/>
    </ColorMap>
</ColorMaps>

I am struggling as is seems that PV keeps adding datapoints in the wrong
place. Also, the band above 26 becomes one single color.
I should note that I am using the 'Color Discretization' Option with 11
colors.

Is it possible to do this? The other alternative that I see is to create an
additional output from my code with the actual labels and then use
'Interpret Values As Categories'.

Thanks
Ruggiero
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160407/9e7f5d9f/attachment.html>

From ken.martin at kitware.com  Thu Apr  7 08:48:37 2016
From: ken.martin at kitware.com (Ken Martin)
Date: Thu, 7 Apr 2016 08:48:37 -0400
Subject: [Paraview] eyedomelightning in paraview 5?
In-Reply-To: <57054CDB.8090608@yahoo.de>
References: <57054CDB.8090608@yahoo.de>
Message-ID: <CANXz0Sbc=Oz+grBmrVp1tNn97UUdSRfhpa7s-HVJvLabFpa0ng@mail.gmail.com>

The Eye Dome Lighting code has been added to newer versions of VTK (as a
render pass in OpenGL2) so in the future we should not need a plugin for
it. Right now I think it is a matter of exposing it in the PV gui somehow
when PV is built with OpenGL2.

Ken

On Wed, Apr 6, 2016 at 1:52 PM, Thomas Engels via ParaView <
paraview at paraview.org> wrote:

> Hello,
>
> I used to use the EyeDomeLightning plugin ( see e.g.,https://blog.kitware.com/eye-dome-lighting-a-non-photorealistic-shading-technique/
> )
> However, support for it seems to be dropped in the newest paraview
> versions (>5.0).
> Is it planned to re-include the plugin? Can it somehow still be used?
> I found it a very helpful tool to create appealing visualizations.
>
> Best regards
> Thomas Engels
>
> --
> Thomas Engels, Ph.D.
> Postdoctoral Researcher
> AIFIT Project (Flying insects in turbulence)
>
> Institut f?r Str?mungsmechanik und Technische Akustik
> FG Numerische Fluiddynamik (MB123)
> M?ller-Breslau-Strasse 8
> 10623 Berlin
> Germany+49 30 314 22849
>
> ?cole normale sup?rieure
> Laboratoire de M?t?orologie Dynamique
> 24, Rue Lhomond
> 75231 Paris Cedex 05
> France
>
>
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview
>
>


-- 
Ken Martin PhD
Chairman & CFO
Kitware Inc.
28 Corporate Drive
Clifton Park NY 12065
518 371 3971

This communication, including all attachments, contains confidential and
legally privileged information, and it is intended only for the use of the
addressee.  Access to this email by anyone else is unauthorized. If you are
not the intended recipient, any disclosure, copying, distribution or any
action taken in reliance on it is prohibited and may be unlawful. If you
received this communication in error please notify us immediately and
destroy the original message.  Thank you.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160407/26dd66c0/attachment.html>

From jfavre at cscs.ch  Thu Apr  7 10:23:19 2016
From: jfavre at cscs.ch (Favre  Jean)
Date: Thu, 7 Apr 2016 14:23:19 +0000
Subject: [Paraview] question-filter
In-Reply-To: <326952444.783104.1459970506204.JavaMail.yahoo@mail.yahoo.com>
References: <961645139.3117877.1459266210514.JavaMail.yahoo@mail.yahoo.com>,
 <326952444.783104.1459970506204.JavaMail.yahoo@mail.yahoo.com>
Message-ID: <0EB9B6375711A04B820E6B6F5CCA9F68435CAC06@MBX111.d.ethz.ch>

I recommend using the IntegrateVariables filter which will give the correct answer for wedges and pyramids. The output is put into an unstructured mesh with a single vertex cell, holding the "Volume" in its Cell Data. The implemented is in vtkIntegrateAttributes which triangulates the non-trivial cells into tetrahedra, performing the sum of all volumes within the cell.

The reason you get a -1 using the python calculator can be linked to the implementation of vtkCellQuality returning this->GetUnsupportedGeometry() (equal to -1) for wedges and pyramids.

-----------------
Jean
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160407/ed84e695/attachment.html>

From cindy.castro at uvsq.fr  Thu Apr  7 11:47:49 2016
From: cindy.castro at uvsq.fr (Cindy Castro)
Date: Thu, 7 Apr 2016 17:47:49 +0200
Subject: [Paraview] Background in 3D mode
In-Reply-To: <CANjZAi9VwZVXvu1-cAAzoEme6-bs7tLHbhj02WdVFfou4h0S9g@mail.gmail.com>
References: <56EADA83.6050104@uvsq.fr> <56FE2BEC.2030702@uvsq.fr>
 <CACJ=gTjTvHLnGvd7w3LVY4zPufCauj_ZDKv1-aZSRr=qJfC3wA@mail.gmail.com>
 <CANjZAi9xRGmn=PJPfAn_Ne4+S1fhfw3WAY2-FDg13wOP9Jzu4w@mail.gmail.com>
 <56FEAA89.2010102@uvsq.fr>
 <CANjZAi8nnN_pSZcm9d-iJ0pDj_8=b5H0Q1gJVRFQFWkpYbGvyg@mail.gmail.com>
 <CANjZAi9VwZVXvu1-cAAzoEme6-bs7tLHbhj02WdVFfou4h0S9g@mail.gmail.com>
Message-ID: <57068125.7020203@uvsq.fr>

In fact :( I already tried tiled display but the backgroup is not 
correctly split. And yes, I am asking for stereoscopic mode and Cristal 
Eyes active stereo.

  Do you know if this feature is going to be supported in a next release 
of ParaView ?

I did not understand the command "/bin/uname (and xterm -r "uname -a" 
-hold)". Do you mean I have to run
 > mpirun -np 8 -machinefile 
/opt/software/ParaView/PVscripts/server_machinefile.txt 
/opt/software/ParaView/ParaView-5.0.0-bin/bin/pvserver -rc 
--client-host=mire-pc /opt/software/ParaView/PVresources/wall_config.pvx 
/bin/uname ???

Regards,

Cindy

Le 01/04/2016 20:03, David E DeMarle a ?crit :
> And of course I just now realized that you are asking for 3D ie 
> stereoscopic mode and remembered that tiled display does not (yet) 
> support Crystal Eyes active stereo.
>
> apologies
>
>
> David E DeMarle
> Kitware, Inc.
> R&D Engineer
> 21 Corporate Drive
> Clifton Park, NY 12065-8662
> Phone: 518-881-4909
>
> On Fri, Apr 1, 2016 at 1:45 PM, David E DeMarle 
> <dave.demarle at kitware.com <mailto:dave.demarle at kitware.com>> wrote:
>
>     Aiming for this right?
>     -------------------
>     |1-1|1-2|2-1|2-2|
>     -------------------
>     |3-1|3-2|4-1|4-2|
>     -------------------
>
>
>     -tdx=3 -tdy=2
>     machinefile.txt that you pass to mpi should be (syntax depends on
>     your mpi)
>     node1
>     node1
>     node2
>     node2
>     node3
>     node3
>     node4
>     node4
>     The point being that you want them to start up in the same order
>     that you have in your pvx file. Use > mpirun ... /bin/uname (and
>     xterm -r "uname -a" -hold) to work out the details.
>
>     Lastly you don't need the LowerLeft, LowerRight and UpperRight for
>     tile mode, but it will be useful for stereoscopic display so keep
>     it handy.
>
>
>
>
>
>     David E DeMarle
>     Kitware, Inc.
>     R&D Engineer
>     21 Corporate Drive
>     Clifton Park, NY 12065-8662
>     Phone: 518-881-4909 <tel:518-881-4909>
>
>     On Fri, Apr 1, 2016 at 1:06 PM, Cindy Castro <cindy.castro at uvsq.fr
>     <mailto:cindy.castro at uvsq.fr>> wrote:
>
>         H Joachim and David,
>
>         Thank you for answering. I tried to apply an Image AND
>         Gradient background and it was not correctly split over the
>         different screens. I think it is cave mode actually. I have
>         tested tile mode but the display is not well ordered. I tried
>         to correct it with mpirun (-tdx=2, -tdy=4) but I may have
>         missed something in the command line.
>
>         Here is my pvx file :
>
>         <?xml version="1.0" ?>
>         <pvx>
>          <Process Type="client" />
>          <Process Type="server">
>          <EyeSeparation Value="0.060"/>
>           <Machine Name="node1-1"
>                    Environment="DISPLAY=:0.0"
>                    FullScreen="0"
>                    ShowBorders="0"
>                    Geometry="1920x1080+0+0"
>                    LowerLeft=" -2.593 0.992 -2.593"
>                    LowerRight="-1.497 0.993 -3.689"
>                    UpperRight="-1.497 1.865 -3.689" />
>           <Machine Name="node1-2"
>                    Environment="DISPLAY=:0.0"
>                    FullScreen="0"
>                    ShowBorders="0"
>                    Geometry="1920x1080+1920+0"
>                    LowerLeft=" -1.497 0.993 -3.689"
>                    LowerRight=" 0.000 0.997 -4.090"
>                    UpperRight=" 0.000 1.869 -4.090" />
>           <Machine Name="node2-1"
>                    Environment="DISPLAY=:0.0"
>                    FullScreen="0"
>                    ShowBorders="0"
>                    Geometry="1920x1080+0+0"
>                    LowerLeft="  0.000 0.997 -4.090"
>                    LowerRight=" 1.497 1.007 -3.689"
>                    UpperRight=" 1.497 1.879 -3.689"/>
>           <Machine Name="node2-2"
>                    Environment="DISPLAY=:0.0"
>                    FullScreen="0"
>                    ShowBorders="0"
>                    Geometry="1920x1080+1920+0"
>                LowerLeft="  1.497 1.007 -3.689"
>                    LowerRight=" 2.593 0.997 -2.593"
>                    UpperRight=" 2.593 1.869 -2.593"/>
>           <Machine Name="node3-1"
>                    Environment="DISPLAY=:0.0"
>                    FullScreen="0"
>                    ShowBorders="0"
>                    Geometry="1920x1080+0+0"
>                    LowerLeft=" -2.593 0.120 -2.593"
>                    LowerRight="-1.497 0.121 -3.689"
>                    UpperRight="-1.497 0.993 -3.689" />
>           <Machine Name="node3-2"
>                    Environment="DISPLAY=:0.0"
>                    FullScreen="0"
>                    ShowBorders="0"
>                    Geometry="1920x1080+1920+0"
>                    LowerLeft=" -1.497 0.121 -3.689"
>                    LowerRight=" 0.000 0.125 -4.090"
>                    UpperRight=" 0.000 0.997 -4.090" />
>           <Machine Name="node4-1"
>                    Environment="DISPLAY=:0.0"
>                    FullScreen="0"
>                    ShowBorders="0"
>                    Geometry="1920x1080+0+0"
>                    LowerLeft="  0.000 0.125 -4.090"
>                    LowerRight=" 1.497 0.135 -3.689"
>                    UpperRight=" 1.497 1.007 -3.689"/>
>           <Machine Name="node4-2"
>                    Environment="DISPLAY=:0.0"
>                    FullScreen="0"
>                    ShowBorders="0"
>                    Geometry="1920x1080+1920+0"
>                    LowerLeft="  1.497 0.135 -3.689"
>                    LowerRight=" 2.593 0.125 -2.593"
>                    UpperRight=" 2.593 0.997 -2.593"/>
>           </Process>
>
>         </pvx>
>
>         Regards,
>
>         Cindy
>
>
>         Le 01/04/2016 17:55, David E DeMarle a ?crit :
>>         Cindy,
>>
>>         I can't remember which mode, tile or cave, doesn't support
>>         tile and gradient background. But from what you and Joachim
>>         say it must be cave.
>>
>>         You should aim for tile mode then. You can enforce and thus
>>         correct the ordering problem you see  with tile mode with
>>         your mpirun command and the your cave.pvx file. Can you share
>>         your /opt/software/ParaView/PVresources/wall_config.pvx? So I
>>         can suggest a fix?
>>
>>         thanks
>>
>>
>>         David E DeMarle
>>         Kitware, Inc.
>>         R&D Engineer
>>         21 Corporate Drive
>>         Clifton Park, NY 12065-8662
>>         Phone: 518-881-4909 <tel:518-881-4909>
>>
>>         On Fri, Apr 1, 2016 at 11:10 AM, Joachim Pouderoux
>>         <joachim.pouderoux at kitware.com
>>         <mailto:joachim.pouderoux at kitware.com>> wrote:
>>
>>             Hi Cindy,
>>
>>             Not totally sure to understand - are you trying to apply
>>             an Image or Gradient background and would like it to be
>>             correctly split over the different screen? If so, I am
>>             afraid this feature is not supported.
>>
>>             Best,
>>             Joachim
>>
>>             *Joachim Pouderoux*
>>
>>                 /PhD, Technical Expert/
>>                 *Kitware SAS <http://www.kitware.fr>*
>>
>>
>>             2016-04-01 10:06 GMT+02:00 Cindy Castro
>>             <cindy.castro at uvsq.fr <mailto:cindy.castro at uvsq.fr>>:
>>
>>                 Hello,
>>
>>                 I am using ParaView in client/server mode with
>>                 stereo. I have a cluster with 4 nodes, 1 GPU each
>>                 (NVIDIA K5000) and 8 screens for display.
>>
>>                 My problem is I can not find how to span a background
>>                 over my 8 screens. The background is displayed on
>>                 each screen. 3D models are well displayed in 3D (no
>>                 problem with that).
>>
>>                 The server is run with the command:
>>                 mpirun -np 8 -machinefile
>>                 /opt/software/ParaView/PVscripts/server_machinefile.txt
>>                 /opt/software/ParaView/ParaView-5.0.0-bin/bin/pvserver -rc
>>                 --client-host=mire-pc
>>                 /opt/software/ParaView/PVresources/wall_config.pvx
>>
>>                 I tried tiles mode but the display is not in the
>>                 right order...
>>
>>                 Can you help me ? Is it possible to span a background
>>                 over several screens in 3D mode ? I is really useful
>>                 when rendering.
>>
>>                 Regards,
>>
>>                 -- 
>>                 Cindy CASTRO
>>                 Responsable plateforme DIGISCOPE-MIRE
>>                 Plateforme d'Int?gration et de Tests (PIT)
>>                 -- 
>>                 Observatoire de Versailles Saint-Quentin-en-Yvelines
>>                 (OVSQ)
>>                 Quartier des Garennes
>>                 11 Boulevard d'Alembert
>>                 78280 Guyancourt
>>                 -- 
>>                 B?timent principal - RDC - Bureau 215
>>                 T?l : +33 (0)1 80 28 51 03
>>                 <tel:%2B33%20%280%291%2080%2028%2051%2003>
>>                 Salle MIRE : +33 (0)1 80 28 54 93
>>                 <tel:%2B33%20%280%291%2080%2028%2054%2093>
>>
>>
>>                 ---
>>                 L'absence de virus dans ce courrier ?lectronique a
>>                 ?t? v?rifi?e par le logiciel antivirus Avast.
>>                 https://www.avast.com/antivirus
>>
>>                 _______________________________________________
>>                 Powered by www.kitware.com <http://www.kitware.com>
>>
>>                 Visit other Kitware open-source projects at
>>                 http://www.kitware.com/opensource/opensource.html
>>
>>                 Please keep messages on-topic and check the ParaView
>>                 Wiki at: http://paraview.org/Wiki/ParaView
>>
>>                 Search the list archives at:
>>                 http://markmail.org/search/?q=ParaView
>>
>>                 Follow this link to subscribe/unsubscribe:
>>                 http://public.kitware.com/mailman/listinfo/paraview
>>
>>
>>
>>             _______________________________________________
>>             Powered by www.kitware.com <http://www.kitware.com>
>>
>>             Visit other Kitware open-source projects at
>>             http://www.kitware.com/opensource/opensource.html
>>
>>             Please keep messages on-topic and check the ParaView Wiki
>>             at: http://paraview.org/Wiki/ParaView
>>
>>             Search the list archives at:
>>             http://markmail.org/search/?q=ParaView
>>
>>             Follow this link to subscribe/unsubscribe:
>>             http://public.kitware.com/mailman/listinfo/paraview
>>
>>
>
>         -- 
>         Cindy CASTRO
>         Responsable plateforme DIGISCOPE-MIRE
>         Plateforme d'Int?gration et de Tests (PIT)
>         -- 
>         Observatoire de Versailles Saint-Quentin-en-Yvelines (OVSQ)
>         Quartier des Garennes
>         11 Boulevard d'Alembert
>         78280 Guyancourt
>         -- 
>         B?timent principal - RDC - Bureau 215
>         T?l :+33 (0)1 80 28 51 03 <tel:%2B33%20%280%291%2080%2028%2051%2003>
>         Salle MIRE :+33 (0)1 80 28 54 93 <tel:%2B33%20%280%291%2080%2028%2054%2093>
>
>
>         Cet e-mail a ?t? envoy? depuis un ordinateur prot?g? par Avast.
>         www.avast.com
>         <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>
>
>
>
>

-- 
Cindy CASTRO
Responsable plateforme DIGISCOPE-MIRE
Plateforme d'Int?gration et de Tests (PIT)
-- 
Observatoire de Versailles Saint-Quentin-en-Yvelines (OVSQ)
Quartier des Garennes
11 Boulevard d'Alembert
78280 Guyancourt
-- 
B?timent principal - RDC - Bureau 215
T?l : +33 (0)1 80 28 51 03
Salle MIRE : +33 (0)1 80 28 54 93



---
L'absence de virus dans ce courrier ?lectronique a ?t? v?rifi?e par le logiciel antivirus Avast.
https://www.avast.com/antivirus
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160407/55f757f6/attachment.html>

From adlinds3 at ncsu.edu  Thu Apr  7 12:46:20 2016
From: adlinds3 at ncsu.edu (Alex Lindsay)
Date: Thu, 7 Apr 2016 12:46:20 -0400
Subject: [Paraview] exodus refresh error
Message-ID: <57068EDC.2070904@ncsu.edu>

Hi all,

I switched to Paraview 5.0.1-RC2 from 4.1.0. I am now getting the 
following error when I try and refresh an exodus file (e.g. get new time 
steps):



No problems with refresh in 4.1.0. Any suggestions?

Alex
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160407/31321fae/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: hjadefbi.png
Type: image/png
Size: 97723 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160407/31321fae/attachment.png>

From utkarsh.ayachit at kitware.com  Thu Apr  7 13:26:44 2016
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Thu, 7 Apr 2016 13:26:44 -0400
Subject: [Paraview] exodus refresh error
In-Reply-To: <57068EDC.2070904@ncsu.edu>
References: <57068EDC.2070904@ncsu.edu>
Message-ID: <CADHSJjDQc9s6Dg-h2KE07a9OWcryU7NddOdB=aP8hJBZMBMrng@mail.gmail.com>

Alex,

This is a known issue: http://www.paraview.org/Bug/view.php?id=15716

We'll address it in the next release of ParaView.

Utkasrh

On Thu, Apr 7, 2016 at 12:46 PM, Alex Lindsay <adlinds3 at ncsu.edu> wrote:

> Hi all,
>
> I switched to Paraview 5.0.1-RC2 from 4.1.0. I am now getting the
> following error when I try and refresh an exodus file (e.g. get new time
> steps):
>
>
>
> No problems with refresh in 4.1.0. Any suggestions?
>
> Alex
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160407/2b2b74c4/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: hjadefbi.png
Type: image/png
Size: 97723 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160407/2b2b74c4/attachment-0001.png>

From andy.bauer at kitware.com  Thu Apr  7 13:36:11 2016
From: andy.bauer at kitware.com (Andy Bauer)
Date: Thu, 7 Apr 2016 13:36:11 -0400
Subject: [Paraview] EXTERNAL: Re: EXTERNAL: Re: EXTERNAL: Re:
 CxxOverlappingAMRExample with Catalyst Live
In-Reply-To: <201604051720.u35HKUuP015230@msw1.awe.co.uk>
References: <201603311343.u2VDhxw3006257@msw1.awe.co.uk>
 <CAMaOp+E2RNEmixMDDN6D0wmirQGP4O5zmagiAXkAeoA3ag-Qgw@mail.gmail.com>
 <201603311604.u2VG4lXk030041@msw1.awe.co.uk>
 <CAMaOp+GaW9p=mB1vCeGCAHRQLfssqAd5tEOh0E3g1RBS45+D6w@mail.gmail.com>
 <201604011640.u31GenL9028104@msw1.awe.co.uk>
 <CAMaOp+GkS71E3dEfV9CiYoY+vBsHEuC8X4v-ONXpy694RLRq1Q@mail.gmail.com>
 <201604051720.u35HKUuP015230@msw1.awe.co.uk>
Message-ID: <CAMaOp+FJMd-ffcZDSwZ-S07Z7Q5e6EcgSjj0v5UhQNPsYyq65Q@mail.gmail.com>

Hi Jim,

I haven't encountered this problem myself. Unfortunately I'm not that
familiar with the connection routines from Catalyst to a pvserver. If you
add in a bug report at http://www.paraview.org/Bug/my_view_page.php it will
help keep track of this issue. Unfortunately I won't be able to look at
this issue for a bit though.

Best,
Andy

On Tue, Apr 5, 2016 at 1:21 PM, <Jim.Eliot at awe.co.uk> wrote:

> Hi Andy,
>
>
>
> Your explanation made it a lot clearer for me. I tested it out with
> multiple pvservers running on a single node and I was able to connect with
> my simulation. Success!
>
>
>
> However, when I tried running pvservers across more than one node, the
> Catalyst connection failed. I saw a bunch of error messages that look like
> this:
>
>
>
> ERROR: In <src_dir>/VTK/Common/System/vtkSocket.cxx, line 481
>
> vtkClientSocket (?): Socket error in call to connect. Connection refused.
>
>
>
> ERROR: In <src_dir>/VTK/Common/System/vtkClientSocket.cxx, line 53
>
> vtkClientSocket (?): Failed to connect to server localhost:22228
>
>
>
> ERROR: In <src_dir>/VTK/Parallel/Core/vtkSocketCommunicator.cxx, line 714
>
> vtkSocketCommunicator (?): Can not connect to localhost on port 22228
>
>
>
> There were a bunch more of these with various socket numbers.
>
>
>
> Do you have any idea what might be causing this problem?
>
>
>
> In my coproc.py file I have a line that looks like this:
>
>
>
>     coprocess.DoLiveVisualization(datadescription, ?localhost?, 22222)
>
>
>
> Do I have to call DoLiveVisualization differently when running across
> multiple nodes? Do I need to set the host differently maybe? Or is the
> problem more likely to be at my end?
>
>
>
> Many thanks
>
>
>
> Kind regards,
>
> Jim
>
>
>
> *From:* Andy Bauer [mailto:andy.bauer at kitware.com]
> *Sent:* 02 April 2016 15:51
> *To:* Eliot Jim AWE <Jim.Eliot at awe1.awe.co.uk>
> *Cc:* paraview at paraview.org
> *Subject:* EXTERNAL: Re: EXTERNAL: Re: EXTERNAL: Re: [Paraview]
> CxxOverlappingAMRExample with Catalyst Live
>
>
>
> Hi Jim,
>
> I inlined some response below...
>
> Best,
>
> Andy
>
>
>
> On Fri, Apr 1, 2016 at 12:41 PM, <Jim.Eliot at awe.co.uk> wrote:
>
> Hi Andy,
>
>
>
> Thank you for all the help that you have provided.
>
>
>
> I feel like I don?t quite understand how Catalyst handles the simulation
> data. If I use ParaView Catalyst for large parallel simulations, and I try
> to fetch the entire dataset, does all the data in the problem get sent to
> the client on my workstation?
>
>
>
> The way it works now is that when you click on the icon next to a filter,
> it fetches that data set to whichever pvserver it's connected to, including
> the built-in server. So yes, in this case it would try to fetch all of the
> data to your client. We've done some work on generating images through
> Catalyst and then sending that image to the client. That was done with PyFR.
>
>
>
>
>
> If I am running pvserver in parallel, would that be able to distribute the
> data between the processes? How do I tell Catalyst to connect to the
> pvservers and the pvservers to connect to the client? I guess I can use
> ?client-host and ?server-port on the pvservers and point them to the
> paraview client but how do I make the Catalyst -> pvserver connection?
>
>
>
> Yes, that should attempt some form of partitioning when it's sent from the
> sim/Catalyst to the parallel pvserver. The way to do the connection in this
> case is to tell the Catalyst Python script to link to where pvserver is
> running ( coprocessor.DoLiveVisualization(datadescription, "localhost",
> 22222)). Then, run the simulation, pvserver and the GUI client, have the
> client connect to pvserver and then in the GUI go through the
> Catalyst->Connect... point to where the simulation is running. This should
> connect pvserver to the sim. If there's firewalls then it may be a bit more
> complex connection. I don't know to what level/size data this has been
> pushed to.
>
>
>
>
>
> Thank you for the information regarding AMR grids ? it sounds like this
> approach will work for my application.
>
>
>
> Kind regards,
>
> Jim
>
>
>
>
>
> *From:* Andy Bauer [mailto:andy.bauer at kitware.com]
> *Sent:* 31 March 2016 20:18
> *To:* Eliot Jim AWE <Jim.Eliot at awe1.awe.co.uk>
> *Cc:* paraview at paraview.org
> *Subject:* EXTERNAL: Re: EXTERNAL: Re: [Paraview]
> CxxOverlappingAMRExample with Catalyst Live
>
>
>
> Hi Jim,
>
> Yes, you can have a Catalyst instrumented code connect to something
> running pvserver and have the pvserver connect to the client. At the end of
> the Python generated scripts there should be a line that looks like:
>     coprocessor.DoLiveVisualization(datadescription, "localhost", 22222)
>
> Here you just have to edit it to point to something other than localhost.
>
>
>
> As for overlapping structured grids, there's no convenient
> composite/multiblock data set for that like there is for Cartesian grids.
> What you would need to do is use vtkStructuredGrids with blanking done
> manually and then just add them in as blocks in a vtkMultiBlockDataSet. It
> won't have the structure that the AMR specific composite data sets have so
> it may be a bit slower for some filters but it should work pretty much like
> you want for most stuff. Please let us know if you try this out and get
> unexpected/undesired behaviour.
>
> Best,
>
> Andy
>
>
>
> On Thu, Mar 31, 2016 at 12:05 PM, <Jim.Eliot at awe.co.uk> wrote:
>
> Hi Andy,
>
>
>
> Thanks for your reply. Currently I am looking at the small examples but I
> would like to be able to fetch larger geometries in future. Is it possible
> for the simulation to connect to a parallel pvserver which will send images
> back to the client?
>
>
>
> Putting interactive usage to one side for a moment, is non-uniform AMR
> supported in Catalyst batch? I.e. overlapping structured grids . I couldn?t
> find any references to non-uniform AMR in ParaView while researching.
>
>
>
> Kind regards,
>
> Jim
>
>
>
> *From:* Andy Bauer [mailto:andy.bauer at kitware.com]
> *Sent:* 31 March 2016 16:08
> *To:* Eliot Jim AWE <Jim.Eliot at awe1.awe.co.uk>
> *Cc:* paraview at paraview.org
> *Subject:* EXTERNAL: Re: [Paraview] CxxOverlappingAMRExample with
> Catalyst Live
>
>
>
> Hi Jim,
>
> Yes, currently Overlapping AMR data sets are not supported by Catalyst
> Live. This is because VTK doesn't support sending that data object. That
> would have to be changed in vtkCommunicator::Send(vtkDataObject* data, int
> remoteHandle, int tag).
>
> A workaround would be to use a Threshold filter to convert to a multiblock
> of unstructured grids, use the merge blocks filter and then extract this
> output to the client. You'll get some warnings about the data set not being
> a polydata (think about running a large simulation and trying to transfer
> all of that to a separate server or client). I'm assuming since you're
> trying to fetch the entire data set that the use case isn't for an overly
> large data set.
>
> Cheers,
>
> Andy
>
>
>
> On Thu, Mar 31, 2016 at 9:44 AM, <Jim.Eliot at awe.co.uk> wrote:
>
>
>
> Good afternoon,
>
>
>
> I have been trying to use Catalyst Live with the CxxOverlappingAMRExample
> from the ParaView Catalyst Example Code repository [1] but I see an error
> when I try to visualise the data from a ParaView client. The client
> connects to the simulation successfully and PVTrivialProducer1 appears in
> the Pipeline Browser. The Information tab shows it as an Overlapping AMR
> Dataset with 3 levels. However, when I click on the PVTrivialProducer1
> icon, ParaView prints an error then segfaults. The error is something like:
>
>
>
>     Warning: In <src-dir>/VTK/Parallel/Core/vtkCommunicator.cxx, line 394
>
>     vtkSocketCommunicator (?): Cannot receive vtkOverlappingAMR
>
>
>
> I have tried this with both ParaView 4.4.0 and 5.0.0 with the same
> results. The example works fine when I am using non-Live Catalyst (i.e. it
> writes out a bunch of vtm files that I can read into ParaView).
>
>
>
> So I am wondering, are AMR meshes not supported by Catalyst Live? Do I
> have to handle AMR meshes differently when using Catalyst interactively?
>
>
>
> Many thanks,
>
> Jim
>
>
>
> [1] https://github.com/Kitware/ParaViewCatalystExampleCode
>
>
>
> *Jim Eliot*
>
> *High Performance Computing Group*
>
> AWE, Aldermaston, Reading, RG7 4PR
>
>
>
> The information in this email and in any attachment(s) is commercial in
> confidence. If you are not the named addressee(s) or if you receive this
> email in error then any distribution, copying or use of this communication
> or the information in it is strictly prohibited. Please notify us
> immediately by email at admin.internet(at)awe.co.uk, and then delete this
> message from your computer. While attachments are virus checked, AWE plc
> does not accept any liability in respect of any virus which is not
> detected. AWE Plc Registered in England and Wales Registration No 02763902
> AWE, Aldermaston, Reading, RG7 4PR
>
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview
>
>
>
> The information in this email and in any attachment(s) is commercial in
> confidence. If you are not the named addressee(s) or if you receive this
> email in error then any distribution, copying or use of this communication
> or the information in it is strictly prohibited. Please notify us
> immediately by email at admin.internet(at)awe.co.uk, and then delete this
> message from your computer. While attachments are virus checked, AWE plc
> does not accept any liability in respect of any virus which is not
> detected. AWE Plc Registered in England and Wales Registration No 02763902
> AWE, Aldermaston, Reading, RG7 4PR
>
>
>
> The information in this email and in any attachment(s) is commercial in
> confidence. If you are not the named addressee(s) or if you receive this
> email in error then any distribution, copying or use of this communication
> or the information in it is strictly prohibited. Please notify us
> immediately by email at admin.internet(at)awe.co.uk, and then delete this
> message from your computer. While attachments are virus checked, AWE plc
> does not accept any liability in respect of any virus which is not
> detected. AWE Plc Registered in England and Wales Registration No 02763902
> AWE, Aldermaston, Reading, RG7 4PR
>
>
> The information in this email and in any attachment(s) is commercial in
> confidence. If you are not the named addressee(s) or if you receive this
> email in error then any distribution, copying or use of this communication
> or the information in it is strictly prohibited. Please notify us
> immediately by email at admin.internet(at)awe.co.uk, and then delete this
> message from your computer. While attachments are virus checked, AWE plc
> does not accept any liability in respect of any virus which is not
> detected. AWE Plc Registered in England and Wales Registration No 02763902
> AWE, Aldermaston, Reading, RG7 4PR
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160407/32550af2/attachment.html>

From dennis_conklin at goodyear.com  Thu Apr  7 15:01:48 2016
From: dennis_conklin at goodyear.com (Dennis Conklin)
Date: Thu, 7 Apr 2016 19:01:48 +0000
Subject: [Paraview] Non-uniform colormaps in Paraview
Message-ID: <CY1PR07MB2506FC462166E677378D6D859F900@CY1PR07MB2506.namprd07.prod.outlook.com>

Ruggiero,

I think your problem is that it will always linearly interpolate between specified values so you need to specify zones of constant color with very small transitions.   I have attached a colormap which I use to implement a 16 color spectrum.   See it for an example.

Hope this helps

Dennis
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160407/44274884/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: patran.json
Type: application/octet-stream
Size: 1929 bytes
Desc: patran.json
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160407/44274884/attachment.obj>

From harald at klimachs.de  Fri Apr  8 03:20:18 2016
From: harald at klimachs.de (Harald Klimach)
Date: Fri, 8 Apr 2016 09:20:18 +0200
Subject: [Paraview] Segfault with OpenGL2
Message-ID: <84D39543-ADC1-4210-A8D8-7D230A61D6AC@klimachs.de>

Hi there,

I try to use the OpenGL2 Rendering backend in Paraview 5.0.1 on Archlinux with an nvidia graphics card.
The setup involves running paraview with VirtualGL in a x2go session, and I always get the following error:

???
ERROR: In /home/gk772/abs/paraview/src/ParaView-v5.0.1-source/VTK/Rendering/OpenGL2/vtkOpenGLRenderWindow.cxx, line 575
vtkXOpenGLRenderWindow (0x42e8540): GLEW could not be initialized.


ERROR: In /home/gk772/abs/paraview/src/ParaView-v5.0.1-source/VTK/Rendering/OpenGL2/vtkShaderProgram.cxx, line 399
vtkShaderProgram (0x42d9dc0): Shader object was not initialized, cannot attach it.


Segmentation fault (core dumped)
???

I found the following thread referring to such an issue: http://vtk.1045678.n5.nabble.com/segfault-with-Opengl2-in-6-3-0-rc2-td5733742.html
But it seems to be not exactly the problem I am facing.
Another thing refers to EGL: https://www.mail-archive.com/paraview at paraview.org/msg25773.html, which again seems to be not really the
same problem.

This problem already arose in 5.0.0, but persists in 5.0.1. With the legacy rendering backend paraview continues to work in my setup.

Can anybody give me some hints on how to investigate this further, or is there already a solution?

Thanks a lot,
Harald

From cyndyb at email.arizona.edu  Fri Apr  8 16:44:58 2016
From: cyndyb at email.arizona.edu (Hart, Cynthia Joyce - (cyndyb))
Date: Fri, 8 Apr 2016 20:44:58 +0000
Subject: [Paraview] building Paraview with OSMesa from source on Linux
Message-ID: <8AFBD0F7-898A-4410-8C2C-DBC68F158901@email.arizona.edu>

I am attempting to build Paraview with OSMesa support, for use with ?headless? rendering on my Universities? HPC cluster.  Needless to say, I don?t have root access.  But I do have a ?nice big space? with which to work on.  I set up a install directory in a directory I have permissions on.  I?m 99% of the way ?there? to a build , but I fail on ?make install?.  It looks like a permissions issue.. Is there some way around this, without permissions?  Here?s where I get stuck:


-- Install configuration: "Release"

CMake Error at cmake_install.cmake:36 (FILE):

  file cannot create directory:

  /rsgrps/rc/cyndyb/ParaView/install/share/paraview-4.3.  Maybe need

  administrative privileges.


I have tried, by the way, creating the above directory beforehand ? no help.  I don?t know very much (at all) about cmake, and the documentations? a bit ?weighty?.  Can somemone tell me what I can do to get past this error, or direct me to precisely where I can learn what I need to know, here?

Thanks,

Cynthia

Scientific Visualization Specialist
University of Arizona


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160408/50aed2d4/attachment.html>

From sebastien.jourdain at kitware.com  Fri Apr  8 20:29:36 2016
From: sebastien.jourdain at kitware.com (Sebastien Jourdain)
Date: Sat, 9 Apr 2016 09:29:36 +0900
Subject: [Paraview] building Paraview with OSMesa from source on Linux
In-Reply-To: <8AFBD0F7-898A-4410-8C2C-DBC68F158901@email.arizona.edu>
References: <8AFBD0F7-898A-4410-8C2C-DBC68F158901@email.arizona.edu>
Message-ID: <CABObKxdM1FYJXiOMMoZP6bZ29hJDBEPnwe0QPpdcEEb=33rZgw@mail.gmail.com>

What did you set in CMake for your install path? Maybe you let the default
be /usr/local or something like that which you don't have access to? If
that's the case, just set the path to be something else where you can write.

Seb

On Sat, Apr 9, 2016 at 5:44 AM, Hart, Cynthia Joyce - (cyndyb) <
cyndyb at email.arizona.edu> wrote:

> I am attempting to build Paraview with OSMesa support, for use with
> ?headless? rendering on my Universities? HPC cluster.  Needless to say, I
> don?t have root access.  But I do have a ?nice big space? with which to
> work on.  I set up a install directory in a directory I have permissions
> on.  I?m 99% of the way ?there? to a build , but I fail on ?make install?.
> It looks like a permissions issue.. Is there some way around this, without
> permissions?  Here?s where I get stuck:
>
> -- Install configuration: "Release"
>
> CMake Error at cmake_install.cmake:36 (FILE):
>
>   file cannot create directory:
>
>   /rsgrps/rc/cyndyb/ParaView/install/share/paraview-4.3.  Maybe need
>
>   administrative privileges.
>
>
> I have tried, by the way, creating the above directory beforehand ? no
> help.  I don?t know very much (at all) about cmake, and the documentations?
> a bit ?weighty?.  Can somemone tell me what I can do to get past this
> error, or direct me to precisely where I can learn what I need to know,
> here?
>
> Thanks,
>
> Cynthia
>
> Scientific Visualization Specialist
> University of Arizona
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160409/f537465f/attachment.html>

From nenadus at gmail.com  Sat Apr  9 09:15:19 2016
From: nenadus at gmail.com (Nenad Vujicic)
Date: Sat, 9 Apr 2016 15:15:19 +0200
Subject: [Paraview] ParaView v5 vs2008 or vs20013?
Message-ID: <CAOr-WQtyG+8scQN_15Wsnqmb7PhrOgPUAevM1UDHNwHkfNVD1A@mail.gmail.com>

Hello everyone,

Which Visual Studio and CMake were used for preparing ParaView v5 binaries
from http://www.paraview.org/download/ <http://www.paraview.org/download/?> ?
I tried to build ParaViewSuperbuild using VS2013 / VS2012 and CMake
2.8.11.2 / 3.4.1, but, didn't have success. Here is what I did:

1) Downloaded currently the latest Superbuild sources (from master branch),
2) create build inside of Superbuild, run cmake-gui ..,
3) I turned OFF using ParaView git sources, turned ON most of packages
under ENABLE (except mpi, manta, libxml2, etc) and hit Configure /
Generate, I used system Qt v4 (everything is x64),
4) Opened generated solution from VS IDE, tried first to build zlib project
and nothing happened, only reported:

1>------ Rebuild All started: Project: zlib, Configuration: Release x64
------
1>  Building Custom Rule C:/Projects/PVdev/Superbuild/CMakeLists.txt
1>  CMake does not need to re-run because
C:\Projects\PVdev\Superbuild\build\CMakeFiles\generate.stamp is up-to-date.
1>  Creating directories for 'zlib'
1>  No download step for 'zlib'
1>  No update step for 'zlib'
1>  No patch step for 'zlib'
1>  No configure step for 'zlib'
1>  No build step for 'zlib'
1>  No install step for 'zlib'
1>  Completed 'zlib'
========== Rebuild All: 1 succeeded, 0 failed, 0 skipped ==========

5) Btw, if I turn on mpi during cmake phase, I get a lot of errors (like
missing MPI_CXX_COMPILER) during Configuring. I cannot even come to
generating building files.

Can someone shed more light on building process of PV v5, please?

Thanks in advance,
Nenad.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160409/a3f49de3/attachment.html>

From utkarsh.ayachit at kitware.com  Sat Apr  9 09:44:16 2016
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Sat, 9 Apr 2016 09:44:16 -0400
Subject: [Paraview] paraview quits when run through Windows Remote
	Desktop
In-Reply-To: <CANMVBVzvq_Xfxq_wZJP_hV8jxLVDvmKbqgn=nc04WFDpmniJBA@mail.gmail.com>
References: <20160401004358.Horde.hmhDoSJ9zYqRq2y_Z57pWw1@192.168.1.14>
 <CADHSJjDgDR7Wp006eXeBamYyS1N094DDkpSf3Y8YcyYS4tGk+w@mail.gmail.com>
 <CANMVBVzQ_GSuYm3__9cF4toYZaiszwVhU+K=ogk-cPFK=Q_Kpw@mail.gmail.com>
 <CADHSJjDpu6639afJiH6asijnofO3osMGMMLsjh9aaWtsksep+w@mail.gmail.com>
 <CANMVBVzvq_Xfxq_wZJP_hV8jxLVDvmKbqgn=nc04WFDpmniJBA@mail.gmail.com>
Message-ID: <CADHSJjBfbYnrhhM1UFLh+=CKHT4P=GB-KS4MPd2pSqHT5LpFTA@mail.gmail.com>

Curious indeed. I suppose it depends on the drivers on your system
then. May be someone with a better understanding of remote desktop &
Windows/OpenGL can comment on this.

Utkarsh

On Fri, Apr 1, 2016 at 8:28 AM, Andrew <antech777 at gmail.com> wrote:
> Yes, I hope this is what you want.
>
> 2016-04-01 15:15 GMT+03:00 Utkarsh Ayachit <utkarsh.ayachit at kitware.com>:
>>
>> > Sorry for small offtopic, but I didn't notice any remote access issues
>> > with
>> > ParaView 5.0.1 RC2 on Windows 7 x64, but I use Linux client (FreeRDP
>> > 1.0.2).
>>
>> That's curious. Can you post the OpenGL information the About dialog
>> reports?
>
>
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview
>

From utkarsh.ayachit at kitware.com  Sat Apr  9 09:51:44 2016
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Sat, 9 Apr 2016 09:51:44 -0400
Subject: [Paraview] ParaView v5 vs2008 or vs20013?
In-Reply-To: <CAOr-WQtyG+8scQN_15Wsnqmb7PhrOgPUAevM1UDHNwHkfNVD1A@mail.gmail.com>
References: <CAOr-WQtyG+8scQN_15Wsnqmb7PhrOgPUAevM1UDHNwHkfNVD1A@mail.gmail.com>
Message-ID: <CADHSJjCKL+k+zzrLaaYBvy90OTAKiDk0zXcGs2Og9g4mGdOo5Q@mail.gmail.com>

Nenad,

1. The ParaView binaries for 5.0/5.0.1 are built using Visual Studio
12 2013 (MSVC 18.0.31101.0).
2. For Windows, we only test ParaVIew superbuild using "Ninja"
generator, and not VS IDE. Thus, run the CMake GUI from an appropriate
Visual Studio Command prompt and choose the Ninja generator. You'll
need to install Ninja (https://ninja-build.org/) before doing that.
3. Enable Qt4 if you want to build GUI, and not Qt5 yet.

Here are the CMakeCache files for out 64 bit MPI [1] and NO-MPI builds [2].

Hope that helps,
Utkarsh

[1] https://open.cdash.org/viewNotes.php?buildid=4313885##note4
[2] https://open.cdash.org/viewNotes.php?buildid=4313982##note4

On Sat, Apr 9, 2016 at 9:15 AM, Nenad Vujicic <nenadus at gmail.com> wrote:
> Hello everyone,
>
> Which Visual Studio and CMake were used for preparing ParaView v5 binaries
> from http://www.paraview.org/download/ ? I tried to build ParaViewSuperbuild
> using VS2013 / VS2012 and CMake 2.8.11.2 / 3.4.1, but, didn't have success.
> Here is what I did:
>
> 1) Downloaded currently the latest Superbuild sources (from master branch),
> 2) create build inside of Superbuild, run cmake-gui ..,
> 3) I turned OFF using ParaView git sources, turned ON most of packages under
> ENABLE (except mpi, manta, libxml2, etc) and hit Configure / Generate, I
> used system Qt v4 (everything is x64),
> 4) Opened generated solution from VS IDE, tried first to build zlib project
> and nothing happened, only reported:
>
> 1>------ Rebuild All started: Project: zlib, Configuration: Release x64
> ------
> 1>  Building Custom Rule C:/Projects/PVdev/Superbuild/CMakeLists.txt
> 1>  CMake does not need to re-run because
> C:\Projects\PVdev\Superbuild\build\CMakeFiles\generate.stamp is up-to-date.
> 1>  Creating directories for 'zlib'
> 1>  No download step for 'zlib'
> 1>  No update step for 'zlib'
> 1>  No patch step for 'zlib'
> 1>  No configure step for 'zlib'
> 1>  No build step for 'zlib'
> 1>  No install step for 'zlib'
> 1>  Completed 'zlib'
> ========== Rebuild All: 1 succeeded, 0 failed, 0 skipped ==========
>
> 5) Btw, if I turn on mpi during cmake phase, I get a lot of errors (like
> missing MPI_CXX_COMPILER) during Configuring. I cannot even come to
> generating building files.
>
> Can someone shed more light on building process of PV v5, please?
>
> Thanks in advance,
> Nenad.
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview
>

From utkarsh.ayachit at kitware.com  Sat Apr  9 10:18:28 2016
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Sat, 9 Apr 2016 10:18:28 -0400
Subject: [Paraview] [EXTERNAL] Re:  Surface LIC plugin
In-Reply-To: <b903e1fbe2224edeaab470203fb5f402@ES01AMSNLNT.srn.sandia.gov>
References: <9A01353A-D10A-4143-B8BB-EAE58D37BBBF@sandia.gov>
 <CADHSJjBNsVPEAwu+v2aNpHKv9FJC_V9dH_G8vsEeOX5+oOUp-A@mail.gmail.com>
 <B46D24B0-EE51-4B90-9E00-3A98174EA1A5@sandia.gov>
 <CADHSJjCf-0+Ffx2v3a2hzP23_u=CnF5wTJ6CKBrf5mBhO4hRMg@mail.gmail.com>
 <b903e1fbe2224edeaab470203fb5f402@ES01AMSNLNT.srn.sandia.gov>
Message-ID: <CADHSJjC1D=6m_=nwnJ0RsiaF--MyyrtJXYHoGmMEE-8c-2+dYg@mail.gmail.com>

Alan,

It's optional since it doesn't necessarily work on all supported OpenGL
drivers -- at least that used to be the case in OpenGL1 days. I need to
check if that's still true.

On Mon, Apr 4, 2016 at 4:57 PM, Scott, W Alan <wascott at sandia.gov> wrote:

> OK, with all of the very good, simple explanations, I get it.  Nice
> feature.  Why isn't it enabled by default?  I.e., why do you need to load
> the optional plugin?
>
> Here is an image I created with the help of Surface LIC.
>
>
> Alan
>
>
>
> -----Original Message-----
> From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com]
> Sent: Monday, April 04, 2016 12:34 PM
> To: Moreland, Kenneth
> Cc: Scott, W Alan; paraview at paraview.org
> Subject: Re: [EXTERNAL] Re: [Paraview] Surface LIC plugin
>
> On Mon, Apr 4, 2016 at 2:31 PM, Moreland, Kenneth <kmorel at sandia.gov>
> wrote:
> > To specify further, I get the same results on my Mac. I do see the LIC
> on the surface inside that hole. I was refering to the outside part of the
> cylinder. But looking more closely at the data, I see that the velocity is
> 0 there, so that would explain why the LIC is not showing anything there.
>
> Ah, yes, that's correct. That was changed a long time ago to just mask out
> regions with zero velocity rather than showing noise, which I believe it
> did in its initial incarnations.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160409/f7e52a27/attachment.html>

From nenadus at gmail.com  Sat Apr  9 12:50:46 2016
From: nenadus at gmail.com (Nenad Vujicic)
Date: Sat, 9 Apr 2016 18:50:46 +0200
Subject: [Paraview] ParaView v5 vs2008 or vs20013?
In-Reply-To: <CADHSJjCKL+k+zzrLaaYBvy90OTAKiDk0zXcGs2Og9g4mGdOo5Q@mail.gmail.com>
References: <CAOr-WQtyG+8scQN_15Wsnqmb7PhrOgPUAevM1UDHNwHkfNVD1A@mail.gmail.com>
 <CADHSJjCKL+k+zzrLaaYBvy90OTAKiDk0zXcGs2Og9g4mGdOo5Q@mail.gmail.com>
Message-ID: <CAOr-WQsjefS-EoWhPYgVvXbP+mN4ThinDUr8TN-mZGQjGSRJKw@mail.gmail.com>

Utkarsh,

As always, your comments were successful :-).

Thank you very much!!

Nenad.

On Sat, Apr 9, 2016 at 3:51 PM, Utkarsh Ayachit <utkarsh.ayachit at kitware.com
> wrote:

> Nenad,
>
> 1. The ParaView binaries for 5.0/5.0.1 are built using Visual Studio
> 12 2013 (MSVC 18.0.31101.0).
> 2. For Windows, we only test ParaVIew superbuild using "Ninja"
> generator, and not VS IDE. Thus, run the CMake GUI from an appropriate
> Visual Studio Command prompt and choose the Ninja generator. You'll
> need to install Ninja (https://ninja-build.org/) before doing that.
> 3. Enable Qt4 if you want to build GUI, and not Qt5 yet.
>
> Here are the CMakeCache files for out 64 bit MPI [1] and NO-MPI builds [2].
>
> Hope that helps,
> Utkarsh
>
> [1] https://open.cdash.org/viewNotes.php?buildid=4313885##note4
> [2] https://open.cdash.org/viewNotes.php?buildid=4313982##note4
>
> On Sat, Apr 9, 2016 at 9:15 AM, Nenad Vujicic <nenadus at gmail.com> wrote:
> > Hello everyone,
> >
> > Which Visual Studio and CMake were used for preparing ParaView v5
> binaries
> > from http://www.paraview.org/download/ ? I tried to build
> ParaViewSuperbuild
> > using VS2013 / VS2012 and CMake 2.8.11.2 / 3.4.1, but, didn't have
> success.
> > Here is what I did:
> >
> > 1) Downloaded currently the latest Superbuild sources (from master
> branch),
> > 2) create build inside of Superbuild, run cmake-gui ..,
> > 3) I turned OFF using ParaView git sources, turned ON most of packages
> under
> > ENABLE (except mpi, manta, libxml2, etc) and hit Configure / Generate, I
> > used system Qt v4 (everything is x64),
> > 4) Opened generated solution from VS IDE, tried first to build zlib
> project
> > and nothing happened, only reported:
> >
> > 1>------ Rebuild All started: Project: zlib, Configuration: Release x64
> > ------
> > 1>  Building Custom Rule C:/Projects/PVdev/Superbuild/CMakeLists.txt
> > 1>  CMake does not need to re-run because
> > C:\Projects\PVdev\Superbuild\build\CMakeFiles\generate.stamp is
> up-to-date.
> > 1>  Creating directories for 'zlib'
> > 1>  No download step for 'zlib'
> > 1>  No update step for 'zlib'
> > 1>  No patch step for 'zlib'
> > 1>  No configure step for 'zlib'
> > 1>  No build step for 'zlib'
> > 1>  No install step for 'zlib'
> > 1>  Completed 'zlib'
> > ========== Rebuild All: 1 succeeded, 0 failed, 0 skipped ==========
> >
> > 5) Btw, if I turn on mpi during cmake phase, I get a lot of errors (like
> > missing MPI_CXX_COMPILER) during Configuring. I cannot even come to
> > generating building files.
> >
> > Can someone shed more light on building process of PV v5, please?
> >
> > Thanks in advance,
> > Nenad.
> >
> > _______________________________________________
> > Powered by www.kitware.com
> >
> > Visit other Kitware open-source projects at
> > http://www.kitware.com/opensource/opensource.html
> >
> > Please keep messages on-topic and check the ParaView Wiki at:
> > http://paraview.org/Wiki/ParaView
> >
> > Search the list archives at: http://markmail.org/search/?q=ParaView
> >
> > Follow this link to subscribe/unsubscribe:
> > http://public.kitware.com/mailman/listinfo/paraview
> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160409/51ac4bf1/attachment.html>

From arsh840 at gmail.com  Mon Apr 11 00:43:50 2016
From: arsh840 at gmail.com (Arshpreet Singh)
Date: Mon, 11 Apr 2016 10:13:50 +0530
Subject: [Paraview] Change arrow tip and twil direction
Message-ID: <CAAstK2HiPt+9Ow3aYD1tmbHXpVm=L8tNiw_WO45kG37ww+mmoA@mail.gmail.com>

I want to change the direction of arrow tip or tail, I am able to use
Invert method present in Arrow() class.
a=Arrow ()
a.Invert =10 #this reverse the direction of arrow

But can I use Invert to rotate arrow all the directions needed?

-- 

Thanks
Arshpreet Singh

I am Sikh boy, Learning by doing and Learning by teaching is my religion.
------------------------------------------------------------------------------
Slashdot TV.
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160411/17a375b4/attachment.html>

From Thomas.Jung at iisb.fraunhofer.de  Mon Apr 11 06:05:55 2016
From: Thomas.Jung at iisb.fraunhofer.de (Jung Thomas)
Date: Mon, 11 Apr 2016 10:05:55 +0000
Subject: [Paraview] no glyphs when using renderserver...
Message-ID: <5EB8727F81F2DC4093C7370FDCB6EA3E099996ED@IISB-SMS01.iisb.local>

Dear all,

I am new to using pvserver, the problem I describe appears with ParaView-5.0.1-Qt4-OpenGL2-MPI-Linux-64bit, but also with elder versions I compiled myself.

Everything seemed to be fine at first, but then I realized there is something wrong with stream tracers and glyps(arrows), I believe on the client side.
Stream tracers do show when I press left mouse button and move it, then they dissappear again.
3D glyps don't show up at all.
Scalar fields, meshes are being displayed o.k. however.
Using local rendering however everything is fine. I have the vague idea it could be related to some local refresh mechanism, but not enough knowledge to figure that out.

Thank you for any hint, and have a nice day!



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160411/9e8376a6/attachment.html>

From ken.martin at kitware.com  Mon Apr 11 09:56:30 2016
From: ken.martin at kitware.com (Ken Martin)
Date: Mon, 11 Apr 2016 09:56:30 -0400
Subject: [Paraview] Segfault with OpenGL2
In-Reply-To: <84D39543-ADC1-4210-A8D8-7D230A61D6AC@klimachs.de>
References: <84D39543-ADC1-4210-A8D8-7D230A61D6AC@klimachs.de>
Message-ID: <CANXz0SYsU8YyTSjKZiF3DuNSLnBOq9h9UQwp7CTgmg-8o8vjQA@mail.gmail.com>

As I understand it VirtualGL should transparently forward OpenGL/GLX/etc
calls from the server to the client so that the client GPU is used. So my
guess would be to first try running PV on the client and see if it works.
If that seems to work fine then you know your client graphics supports PVs
use of OpenGL and the issue could be in VirtualGL or some PV/VirtualGL
interaction.

Ken



On Fri, Apr 8, 2016 at 3:20 AM, Harald Klimach <harald at klimachs.de> wrote:

> Hi there,
>
> I try to use the OpenGL2 Rendering backend in Paraview 5.0.1 on Archlinux
> with an nvidia graphics card.
> The setup involves running paraview with VirtualGL in a x2go session, and
> I always get the following error:
>
> ???
> ERROR: In
> /home/gk772/abs/paraview/src/ParaView-v5.0.1-source/VTK/Rendering/OpenGL2/vtkOpenGLRenderWindow.cxx,
> line 575
> vtkXOpenGLRenderWindow (0x42e8540): GLEW could not be initialized.
>
>
> ERROR: In
> /home/gk772/abs/paraview/src/ParaView-v5.0.1-source/VTK/Rendering/OpenGL2/vtkShaderProgram.cxx,
> line 399
> vtkShaderProgram (0x42d9dc0): Shader object was not initialized, cannot
> attach it.
>
>
> Segmentation fault (core dumped)
> ???
>
> I found the following thread referring to such an issue:
> http://vtk.1045678.n5.nabble.com/segfault-with-Opengl2-in-6-3-0-rc2-td5733742.html
> But it seems to be not exactly the problem I am facing.
> Another thing refers to EGL:
> https://www.mail-archive.com/paraview at paraview.org/msg25773.html, which
> again seems to be not really the
> same problem.
>
> This problem already arose in 5.0.0, but persists in 5.0.1. With the
> legacy rendering backend paraview continues to work in my setup.
>
> Can anybody give me some hints on how to investigate this further, or is
> there already a solution?
>
> Thanks a lot,
> Harald
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview
>



-- 
Ken Martin PhD
Chairman & CFO
Kitware Inc.
28 Corporate Drive
Clifton Park NY 12065
518 371 3971

This communication, including all attachments, contains confidential and
legally privileged information, and it is intended only for the use of the
addressee.  Access to this email by anyone else is unauthorized. If you are
not the intended recipient, any disclosure, copying, distribution or any
action taken in reliance on it is prohibited and may be unlawful. If you
received this communication in error please notify us immediately and
destroy the original message.  Thank you.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160411/556e4df5/attachment.html>

From arsh840 at gmail.com  Mon Apr 11 10:05:53 2016
From: arsh840 at gmail.com (Arshpreet Singh)
Date: Mon, 11 Apr 2016 19:35:53 +0530
Subject: [Paraview] Change arrow tip and twil direction
In-Reply-To: <CAAstK2HiPt+9Ow3aYD1tmbHXpVm=L8tNiw_WO45kG37ww+mmoA@mail.gmail.com>
References: <CAAstK2HiPt+9Ow3aYD1tmbHXpVm=L8tNiw_WO45kG37ww+mmoA@mail.gmail.com>
Message-ID: <CAAstK2F=PMUMASxJoNkMMc53sD-Ox7Y3aVrXb_Nmpv+6pYOhcw@mail.gmail.com>

On Monday, April 11, 2016, Arshpreet Singh <arsh840 at gmail.com> wrote:
> I want to change the direction of arrow tip or tail, I am able to use
Invert method present in Arrow() class.
> a=Arrow ()
> a.Invert =10 #this reverse the direction of arrow

Thanks I solved it as follows:
P=simple.GetDisplayProperties()
P.Orientation=(10, 2, 20) #(x, y, z)

> But can I use Invert to rotate arrow all the directions needed?
>
> --
>
> Thanks
> Arshpreet Singh
>
> I am Sikh boy, Learning by doing and Learning by teaching is my religion.
>
------------------------------------------------------------------------------
> Slashdot TV.
> Video for Nerds.  Stuff that matters.
> http://tv.slashdot.org/
>

-- 

Thanks
Arshpreet Singh

I am Sikh boy, Learning by doing and Learning by teaching is my religion.
------------------------------------------------------------------------------
Slashdot TV.
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160411/965bbf9f/attachment.html>

From chuck.atkins at kitware.com  Mon Apr 11 10:25:48 2016
From: chuck.atkins at kitware.com (Chuck Atkins)
Date: Mon, 11 Apr 2016 10:25:48 -0400
Subject: [Paraview] Segfault with OpenGL2
In-Reply-To: <CANXz0SYsU8YyTSjKZiF3DuNSLnBOq9h9UQwp7CTgmg-8o8vjQA@mail.gmail.com>
References: <84D39543-ADC1-4210-A8D8-7D230A61D6AC@klimachs.de>
 <CANXz0SYsU8YyTSjKZiF3DuNSLnBOq9h9UQwp7CTgmg-8o8vjQA@mail.gmail.com>
Message-ID: <CAOXZzG72H0LfFw6V1WztJC30eHjMhPY0JBeP7shQHbfDW7jbZg@mail.gmail.com>

I've had similar issues with VirtulGL and VTK in the past.  The "Shader
object was not initialized, cannot attach it." error is often the result of
some sort of required OpenGL version support for a specific call is
lacking.  A few questions:

   - Are you able to run on the actual machine without Virtual GL?
   - What does the output of glxinfo running in the x2go+VirtualGL
   environment look like?


- Chuck

On Mon, Apr 11, 2016 at 9:56 AM, Ken Martin <ken.martin at kitware.com> wrote:

> As I understand it VirtualGL should transparently forward OpenGL/GLX/etc
> calls from the server to the client so that the client GPU is used. So my
> guess would be to first try running PV on the client and see if it works.
> If that seems to work fine then you know your client graphics supports PVs
> use of OpenGL and the issue could be in VirtualGL or some PV/VirtualGL
> interaction.
>
> Ken
>
>
>
> On Fri, Apr 8, 2016 at 3:20 AM, Harald Klimach <harald at klimachs.de> wrote:
>
>> Hi there,
>>
>> I try to use the OpenGL2 Rendering backend in Paraview 5.0.1 on Archlinux
>> with an nvidia graphics card.
>> The setup involves running paraview with VirtualGL in a x2go session, and
>> I always get the following error:
>>
>> ???
>> ERROR: In
>> /home/gk772/abs/paraview/src/ParaView-v5.0.1-source/VTK/Rendering/OpenGL2/vtkOpenGLRenderWindow.cxx,
>> line 575
>> vtkXOpenGLRenderWindow (0x42e8540): GLEW could not be initialized.
>>
>>
>> ERROR: In
>> /home/gk772/abs/paraview/src/ParaView-v5.0.1-source/VTK/Rendering/OpenGL2/vtkShaderProgram.cxx,
>> line 399
>> vtkShaderProgram (0x42d9dc0): Shader object was not initialized, cannot
>> attach it.
>>
>>
>> Segmentation fault (core dumped)
>> ???
>>
>> I found the following thread referring to such an issue:
>> http://vtk.1045678.n5.nabble.com/segfault-with-Opengl2-in-6-3-0-rc2-td5733742.html
>> But it seems to be not exactly the problem I am facing.
>> Another thing refers to EGL:
>> https://www.mail-archive.com/paraview at paraview.org/msg25773.html, which
>> again seems to be not really the
>> same problem.
>>
>> This problem already arose in 5.0.0, but persists in 5.0.1. With the
>> legacy rendering backend paraview continues to work in my setup.
>>
>> Can anybody give me some hints on how to investigate this further, or is
>> there already a solution?
>>
>> Thanks a lot,
>> Harald
>> _______________________________________________
>> Powered by www.kitware.com
>>
>> Visit other Kitware open-source projects at
>> http://www.kitware.com/opensource/opensource.html
>>
>> Please keep messages on-topic and check the ParaView Wiki at:
>> http://paraview.org/Wiki/ParaView
>>
>> Search the list archives at: http://markmail.org/search/?q=ParaView
>>
>> Follow this link to subscribe/unsubscribe:
>> http://public.kitware.com/mailman/listinfo/paraview
>>
>
>
>
> --
> Ken Martin PhD
> Chairman & CFO
> Kitware Inc.
> 28 Corporate Drive
> Clifton Park NY 12065
> 518 371 3971
>
> This communication, including all attachments, contains confidential and
> legally privileged information, and it is intended only for the use of the
> addressee.  Access to this email by anyone else is unauthorized. If you are
> not the intended recipient, any disclosure, copying, distribution or any
> action taken in reliance on it is prohibited and may be unlawful. If you
> received this communication in error please notify us immediately and
> destroy the original message.  Thank you.
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160411/44e96512/attachment.html>

From harald at klimachs.de  Mon Apr 11 13:07:45 2016
From: harald at klimachs.de (Harald Klimach)
Date: Mon, 11 Apr 2016 19:07:45 +0200
Subject: [Paraview] Segfault with OpenGL2
In-Reply-To: <CAOXZzG72H0LfFw6V1WztJC30eHjMhPY0JBeP7shQHbfDW7jbZg@mail.gmail.com>
References: <84D39543-ADC1-4210-A8D8-7D230A61D6AC@klimachs.de>
 <CANXz0SYsU8YyTSjKZiF3DuNSLnBOq9h9UQwp7CTgmg-8o8vjQA@mail.gmail.com>
 <CAOXZzG72H0LfFw6V1WztJC30eHjMhPY0JBeP7shQHbfDW7jbZg@mail.gmail.com>
Message-ID: <53626D34-B441-4AB5-ABEC-90F12DB91A03@klimachs.de>

Dear Chuck, dear Ken,

thanks for the replies.

> I've had similar issues with VirtulGL and VTK in the past.  The "Shader object was not initialized, cannot attach it." error is often the result of some sort of required OpenGL version support for a specific call is lacking.  A few questions:
> 	? Are you able to run on the actual machine without Virtual GL?
the machine is a headless server down in our machine room, and I can not easily access it.

> 	? What does the output of glxinfo running in the x2go+VirtualGL environment look like?
Here is how it looks like:
$ vglrun glxinfo
name of display: :55
display: :55  screen: 0
direct rendering: Yes
server glx vendor string: VirtualGL
server glx version string: 1.4
server glx extensions:
    GLX_ARB_create_context, GLX_ARB_create_context_profile, 
    GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_swap_control, 
    GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, GLX_EXT_visual_rating, 
    GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGI_make_current_read, 
    GLX_SGI_swap_control, GLX_SUN_get_transparent_index
client glx vendor string: VirtualGL
client glx version string: 1.4
client glx extensions:
    GLX_ARB_create_context, GLX_ARB_create_context_profile, 
    GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_swap_control, 
    GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, GLX_EXT_visual_rating, 
    GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGI_make_current_read, 
    GLX_SGI_swap_control, GLX_SUN_get_transparent_index
GLX version: 1.4
GLX extensions:
    GLX_ARB_create_context, GLX_ARB_create_context_profile, 
    GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_swap_control, 
    GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, GLX_EXT_visual_rating, 
    GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGI_make_current_read, 
    GLX_SGI_swap_control, GLX_SUN_get_transparent_index
OpenGL vendor string: NVIDIA Corporation
OpenGL renderer string: Tesla M2075/PCIe/SSE2
OpenGL core profile version string: 4.5.0 NVIDIA 361.28
OpenGL core profile shading language version string: 4.50 NVIDIA
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
?
lots of extensions
?
OpenGL version string: 4.5.0 NVIDIA 361.28
OpenGL shading language version string: 4.50 NVIDIA
OpenGL context flags: (none)
OpenGL profile mask: (none)


---
Without vglrun I get:

$ glxinfo
name of display: :55
display: :55  screen: 0
direct rendering: No (If you want to find out why, try setting LIBGL_DEBUG=verbose)
server glx vendor string: SGI
server glx version string: 1.2
server glx extensions:
    GLX_ARB_multisample, GLX_EXT_import_context, GLX_EXT_visual_info, 
    GLX_EXT_visual_rating, GLX_OML_swap_method, GLX_SGIS_multisample, 
    GLX_SGIX_fbconfig, GLX_SGIX_hyperpipe, GLX_SGIX_swap_barrier, 
    GLX_SGI_make_current_read
client glx vendor string: NVIDIA Corporation
client glx version string: 1.4
client glx extensions:
    GLX_ARB_context_flush_control, GLX_ARB_create_context, 
    GLX_ARB_create_context_profile, GLX_ARB_create_context_robustness, 
    GLX_ARB_fbconfig_float, GLX_ARB_get_proc_address, GLX_ARB_multisample, 
    GLX_EXT_buffer_age, GLX_EXT_create_context_es2_profile, 
    GLX_EXT_create_context_es_profile, GLX_EXT_fbconfig_packed_float, 
    GLX_EXT_framebuffer_sRGB, GLX_EXT_import_context, GLX_EXT_stereo_tree, 
    GLX_EXT_swap_control, GLX_EXT_swap_control_tear, 
    GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, GLX_EXT_visual_rating, 
    GLX_NV_copy_buffer, GLX_NV_copy_image, GLX_NV_delay_before_swap, 
    GLX_NV_float_buffer, GLX_NV_multisample_coverage, GLX_NV_present_video, 
    GLX_NV_swap_group, GLX_NV_video_capture, GLX_NV_video_out, 
    GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGI_swap_control, 
    GLX_SGI_video_sync
GLX version: 1.2
GLX extensions:
    GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_import_context, 
    GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_SGIX_fbconfig
OpenGL vendor string: Mesa project: www.mesa3d.org
OpenGL renderer string: Mesa GLX Indirect
OpenGL version string: 1.2 (1.5 Mesa 6.4.1)


---
On my local box, I get:

$ glxinfo
name of display: /private/tmp/com.apple.launchd.vDdJxiOxqs/org.macosforge.xquartz:0
display: /private/tmp/com.apple.launchd.vDdJxiOxqs/org.macosforge.xquartz:0  screen: 0
direct rendering: Yes
server glx vendor string: SGI
server glx version string: 1.4
server glx extensions:
    GLX_ARB_multisample, GLX_EXT_import_context, GLX_EXT_visual_info, 
    GLX_EXT_visual_rating, GLX_OML_swap_method, GLX_SGIS_multisample, 
    GLX_SGIX_fbconfig
client glx vendor string: Mesa Project and SGI
client glx version string: 1.4
client glx extensions:
    GLX_ARB_create_context, GLX_ARB_create_context_profile, 
    GLX_ARB_create_context_robustness, GLX_ARB_fbconfig_float, 
    GLX_ARB_framebuffer_sRGB, GLX_ARB_get_proc_address, GLX_ARB_multisample, 
    GLX_EXT_buffer_age, GLX_EXT_create_context_es2_profile, 
    GLX_EXT_fbconfig_packed_float, GLX_EXT_framebuffer_sRGB, 
    GLX_EXT_import_context, GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, 
    GLX_EXT_visual_rating, GLX_INTEL_swap_event, GLX_MESA_copy_sub_buffer, 
    GLX_MESA_multithread_makecurrent, GLX_MESA_query_renderer, 
    GLX_MESA_swap_control, GLX_OML_swap_method, GLX_OML_sync_control, 
    GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, 
    GLX_SGIX_visual_select_group, GLX_SGI_make_current_read, 
    GLX_SGI_swap_control, GLX_SGI_video_sync
GLX version: 1.4
GLX extensions:
    GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_import_context, 
    GLX_EXT_visual_info, GLX_EXT_visual_rating, 
    GLX_MESA_multithread_makecurrent, GLX_OML_swap_method, 
    GLX_SGIS_multisample, GLX_SGIX_fbconfig
OpenGL vendor string: Intel
OpenGL renderer string: Intel(R) Iris(TM) Graphics 6100
OpenGL version string: 2.1 INTEL-10.6.33
OpenGL shading language version string: 1.20

Paraview 5.0.0 works on my local Mac, but I am not 100% sure, whether it is using OpenGL2.
Somehow the paraview.org website is not responding right now, so I can?t download 5.0.1 and
give it another try.

---
I also get a segmentation fault if I run with just X-Forwarding in a regular SSH connection, without
any further information:
$ paraview
Segmentation fault (core dumped)

---
If I run in a x2go session, I get:
$ paraview
failed to get the current screen resources
QXcbConnection: XCB error: 172 (Unknown), sequence: 166, resource id: 163, major code: 149 (Unknown), minor code: 20
Segmentation fault (core dumped)

(Where I believe the XCB error is unrelated.)

---
If I run paraview in a vglconnect session without x2go, I get the same error as within the x2go session:

$ vglrun paraview
ERROR: In /home/gk772/abs/paraview/src/ParaView-v5.0.1-source/VTK/Rendering/OpenGL2/vtkOpenGLRenderWindow.cxx, line 575
vtkXOpenGLRenderWindow (0x3673960): GLEW could not be initialized.


ERROR: In /home/gk772/abs/paraview/src/ParaView-v5.0.1-source/VTK/Rendering/OpenGL2/vtkShaderProgram.cxx, line 399
vtkShaderProgram (0x36651f0): Shader object was not initialized, cannot attach it.


Segmentation fault (core dumped)


> On Mon, Apr 11, 2016 at 9:56 AM, Ken Martin <ken.martin at kitware.com> wrote:
> As I understand it VirtualGL should transparently forward OpenGL/GLX/etc calls from the server to the client so that the client GPU is used. So my guess would be to first try running PV on the client and see if it works. If that seems to work fine then you know your client graphics supports PVs use of OpenGL and the issue could be in VirtualGL or some PV/VirtualGL interaction.
I am always confused with this server and client terminology in the X context.
The remote machine, where I try to run paraview on has a relatively strong nVidia graphics card,
which we would like to utilize via the virtualgl mechanism.
With the x2go we also try to keep the X-server on that box as much as possible, thus we have both,
the X-server and the paraview application running there. As far as I understand it, the graphics
capabilities of my local laptop should not really matter that much in this scenario.
I probably should try and run paraview on the box itself, but as I said above, it is not that easily
accessible.

Thanks a lot!
Harald

From chuck.atkins at kitware.com  Mon Apr 11 14:54:19 2016
From: chuck.atkins at kitware.com (Chuck Atkins)
Date: Mon, 11 Apr 2016 14:54:19 -0400
Subject: [Paraview] Segfault with OpenGL2
In-Reply-To: <53626D34-B441-4AB5-ABEC-90F12DB91A03@klimachs.de>
References: <84D39543-ADC1-4210-A8D8-7D230A61D6AC@klimachs.de>
 <CANXz0SYsU8YyTSjKZiF3DuNSLnBOq9h9UQwp7CTgmg-8o8vjQA@mail.gmail.com>
 <CAOXZzG72H0LfFw6V1WztJC30eHjMhPY0JBeP7shQHbfDW7jbZg@mail.gmail.com>
 <53626D34-B441-4AB5-ABEC-90F12DB91A03@klimachs.de>
Message-ID: <CAOXZzG7p56p9Nn57RXTs+yXMjDKVZEJoj--0VkK77tog+7Sdew@mail.gmail.com>

Hi Harald,

I don't have an answer to your VGL problem yet, but in the mean time, are
you tied to having to use it that way?  If not, you also have the option of
running ParaView in client / server mode which may actually be more ideal
for your situation: i.e. with pvserver running on the headless server and
the ParaView GUI client on your local machine (workstation / desktop /
laptop, etc.) and connecting to the remote server.  Doing so, you can
actually bypass vgl and likely get much better performance.  If you're
running an X server on the remote machine, you can do this by setting your
DISPLAY variable to the local x server:

ssh foo at bigserver
[foo at bigserver ~]$ DISPLAY=:0.0 pvserver
Waiting for client...
Connection URL: cs://bigserver.supercooldomain.com:11111
Accepting connection(s): bigserver.supercooldomain.com:11111

Then in the client you select [Conenct] -> [Add Server] to create the
connection to the remote machine.

Or I also noticed that you're running a very recent version of the NVidia
driver.  I believe this actually has EGL support, which will allow you to
build ParaView configured to use the GPU for off screen rendering with no X
server necessary at all.  To do this, configure ParaView with the following
CMake options:

   - -DVTK_RENDERING_BACKEND=OpenGL2
   - -DVTK_USE_OFFSCREEN_EGL=ON

You would then run pvserver on the remote machine with no need for an X
server and connect to it with the GUI client in the same way.

- Chuck

On Mon, Apr 11, 2016 at 1:07 PM, Harald Klimach <harald at klimachs.de> wrote:

> Dear Chuck, dear Ken,
>
> thanks for the replies.
>
> > I've had similar issues with VirtulGL and VTK in the past.  The "Shader
> object was not initialized, cannot attach it." error is often the result of
> some sort of required OpenGL version support for a specific call is
> lacking.  A few questions:
> >       ? Are you able to run on the actual machine without Virtual GL?
> the machine is a headless server down in our machine room, and I can not
> easily access it.
>
> >       ? What does the output of glxinfo running in the x2go+VirtualGL
> environment look like?
> Here is how it looks like:
> $ vglrun glxinfo
> name of display: :55
> display: :55  screen: 0
> direct rendering: Yes
> server glx vendor string: VirtualGL
> server glx version string: 1.4
> server glx extensions:
>     GLX_ARB_create_context, GLX_ARB_create_context_profile,
>     GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_swap_control,
>     GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info,
> GLX_EXT_visual_rating,
>     GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGI_make_current_read,
>     GLX_SGI_swap_control, GLX_SUN_get_transparent_index
> client glx vendor string: VirtualGL
> client glx version string: 1.4
> client glx extensions:
>     GLX_ARB_create_context, GLX_ARB_create_context_profile,
>     GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_swap_control,
>     GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info,
> GLX_EXT_visual_rating,
>     GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGI_make_current_read,
>     GLX_SGI_swap_control, GLX_SUN_get_transparent_index
> GLX version: 1.4
> GLX extensions:
>     GLX_ARB_create_context, GLX_ARB_create_context_profile,
>     GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_swap_control,
>     GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info,
> GLX_EXT_visual_rating,
>     GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGI_make_current_read,
>     GLX_SGI_swap_control, GLX_SUN_get_transparent_index
> OpenGL vendor string: NVIDIA Corporation
> OpenGL renderer string: Tesla M2075/PCIe/SSE2
> OpenGL core profile version string: 4.5.0 NVIDIA 361.28
> OpenGL core profile shading language version string: 4.50 NVIDIA
> OpenGL core profile context flags: (none)
> OpenGL core profile profile mask: core profile
> ?
> lots of extensions
> ?
> OpenGL version string: 4.5.0 NVIDIA 361.28
> OpenGL shading language version string: 4.50 NVIDIA
> OpenGL context flags: (none)
> OpenGL profile mask: (none)
>
>
> ---
> Without vglrun I get:
>
> $ glxinfo
> name of display: :55
> display: :55  screen: 0
> direct rendering: No (If you want to find out why, try setting
> LIBGL_DEBUG=verbose)
> server glx vendor string: SGI
> server glx version string: 1.2
> server glx extensions:
>     GLX_ARB_multisample, GLX_EXT_import_context, GLX_EXT_visual_info,
>     GLX_EXT_visual_rating, GLX_OML_swap_method, GLX_SGIS_multisample,
>     GLX_SGIX_fbconfig, GLX_SGIX_hyperpipe, GLX_SGIX_swap_barrier,
>     GLX_SGI_make_current_read
> client glx vendor string: NVIDIA Corporation
> client glx version string: 1.4
> client glx extensions:
>     GLX_ARB_context_flush_control, GLX_ARB_create_context,
>     GLX_ARB_create_context_profile, GLX_ARB_create_context_robustness,
>     GLX_ARB_fbconfig_float, GLX_ARB_get_proc_address, GLX_ARB_multisample,
>     GLX_EXT_buffer_age, GLX_EXT_create_context_es2_profile,
>     GLX_EXT_create_context_es_profile, GLX_EXT_fbconfig_packed_float,
>     GLX_EXT_framebuffer_sRGB, GLX_EXT_import_context, GLX_EXT_stereo_tree,
>     GLX_EXT_swap_control, GLX_EXT_swap_control_tear,
>     GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info,
> GLX_EXT_visual_rating,
>     GLX_NV_copy_buffer, GLX_NV_copy_image, GLX_NV_delay_before_swap,
>     GLX_NV_float_buffer, GLX_NV_multisample_coverage, GLX_NV_present_video,
>     GLX_NV_swap_group, GLX_NV_video_capture, GLX_NV_video_out,
>     GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGI_swap_control,
>     GLX_SGI_video_sync
> GLX version: 1.2
> GLX extensions:
>     GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_import_context,
>     GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_SGIX_fbconfig
> OpenGL vendor string: Mesa project: www.mesa3d.org
> OpenGL renderer string: Mesa GLX Indirect
> OpenGL version string: 1.2 (1.5 Mesa 6.4.1)
>
>
> ---
> On my local box, I get:
>
> $ glxinfo
> name of display:
> /private/tmp/com.apple.launchd.vDdJxiOxqs/org.macosforge.xquartz:0
> display:
> /private/tmp/com.apple.launchd.vDdJxiOxqs/org.macosforge.xquartz:0  screen:
> 0
> direct rendering: Yes
> server glx vendor string: SGI
> server glx version string: 1.4
> server glx extensions:
>     GLX_ARB_multisample, GLX_EXT_import_context, GLX_EXT_visual_info,
>     GLX_EXT_visual_rating, GLX_OML_swap_method, GLX_SGIS_multisample,
>     GLX_SGIX_fbconfig
> client glx vendor string: Mesa Project and SGI
> client glx version string: 1.4
> client glx extensions:
>     GLX_ARB_create_context, GLX_ARB_create_context_profile,
>     GLX_ARB_create_context_robustness, GLX_ARB_fbconfig_float,
>     GLX_ARB_framebuffer_sRGB, GLX_ARB_get_proc_address,
> GLX_ARB_multisample,
>     GLX_EXT_buffer_age, GLX_EXT_create_context_es2_profile,
>     GLX_EXT_fbconfig_packed_float, GLX_EXT_framebuffer_sRGB,
>     GLX_EXT_import_context, GLX_EXT_texture_from_pixmap,
> GLX_EXT_visual_info,
>     GLX_EXT_visual_rating, GLX_INTEL_swap_event, GLX_MESA_copy_sub_buffer,
>     GLX_MESA_multithread_makecurrent, GLX_MESA_query_renderer,
>     GLX_MESA_swap_control, GLX_OML_swap_method, GLX_OML_sync_control,
>     GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer,
>     GLX_SGIX_visual_select_group, GLX_SGI_make_current_read,
>     GLX_SGI_swap_control, GLX_SGI_video_sync
> GLX version: 1.4
> GLX extensions:
>     GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_import_context,
>     GLX_EXT_visual_info, GLX_EXT_visual_rating,
>     GLX_MESA_multithread_makecurrent, GLX_OML_swap_method,
>     GLX_SGIS_multisample, GLX_SGIX_fbconfig
> OpenGL vendor string: Intel
> OpenGL renderer string: Intel(R) Iris(TM) Graphics 6100
> OpenGL version string: 2.1 INTEL-10.6.33
> OpenGL shading language version string: 1.20
>
> Paraview 5.0.0 works on my local Mac, but I am not 100% sure, whether it
> is using OpenGL2.
> Somehow the paraview.org website is not responding right now, so I can?t
> download 5.0.1 and
> give it another try.
>
> ---
> I also get a segmentation fault if I run with just X-Forwarding in a
> regular SSH connection, without
> any further information:
> $ paraview
> Segmentation fault (core dumped)
>
> ---
> If I run in a x2go session, I get:
> $ paraview
> failed to get the current screen resources
> QXcbConnection: XCB error: 172 (Unknown), sequence: 166, resource id: 163,
> major code: 149 (Unknown), minor code: 20
> Segmentation fault (core dumped)
>
> (Where I believe the XCB error is unrelated.)
>
> ---
> If I run paraview in a vglconnect session without x2go, I get the same
> error as within the x2go session:
>
> $ vglrun paraview
> ERROR: In
> /home/gk772/abs/paraview/src/ParaView-v5.0.1-source/VTK/Rendering/OpenGL2/vtkOpenGLRenderWindow.cxx,
> line 575
> vtkXOpenGLRenderWindow (0x3673960): GLEW could not be initialized.
>
>
> ERROR: In
> /home/gk772/abs/paraview/src/ParaView-v5.0.1-source/VTK/Rendering/OpenGL2/vtkShaderProgram.cxx,
> line 399
> vtkShaderProgram (0x36651f0): Shader object was not initialized, cannot
> attach it.
>
>
> Segmentation fault (core dumped)
>
>
> > On Mon, Apr 11, 2016 at 9:56 AM, Ken Martin <ken.martin at kitware.com>
> wrote:
> > As I understand it VirtualGL should transparently forward OpenGL/GLX/etc
> calls from the server to the client so that the client GPU is used. So my
> guess would be to first try running PV on the client and see if it works.
> If that seems to work fine then you know your client graphics supports PVs
> use of OpenGL and the issue could be in VirtualGL or some PV/VirtualGL
> interaction.
> I am always confused with this server and client terminology in the X
> context.
> The remote machine, where I try to run paraview on has a relatively strong
> nVidia graphics card,
> which we would like to utilize via the virtualgl mechanism.
> With the x2go we also try to keep the X-server on that box as much as
> possible, thus we have both,
> the X-server and the paraview application running there. As far as I
> understand it, the graphics
> capabilities of my local laptop should not really matter that much in this
> scenario.
> I probably should try and run paraview on the box itself, but as I said
> above, it is not that easily
> accessible.
>
> Thanks a lot!
> Harald
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160411/1a464ab7/attachment.html>

From harald at klimachs.de  Mon Apr 11 15:20:59 2016
From: harald at klimachs.de (Harald Klimach)
Date: Mon, 11 Apr 2016 21:20:59 +0200
Subject: [Paraview] Segfault with OpenGL2
In-Reply-To: <CAOXZzG7p56p9Nn57RXTs+yXMjDKVZEJoj--0VkK77tog+7Sdew@mail.gmail.com>
References: <84D39543-ADC1-4210-A8D8-7D230A61D6AC@klimachs.de>
 <CANXz0SYsU8YyTSjKZiF3DuNSLnBOq9h9UQwp7CTgmg-8o8vjQA@mail.gmail.com>
 <CAOXZzG72H0LfFw6V1WztJC30eHjMhPY0JBeP7shQHbfDW7jbZg@mail.gmail.com>
 <53626D34-B441-4AB5-ABEC-90F12DB91A03@klimachs.de>
 <CAOXZzG7p56p9Nn57RXTs+yXMjDKVZEJoj--0VkK77tog+7Sdew@mail.gmail.com>
Message-ID: <CDDA51C7-D41A-454A-807C-4E3ECC75E457@klimachs.de>

Dear Chuck,

thanks a lot for this suggestion. I never thought about this approach for this setup!
That would probably really be a great solution. I?ll give this tomorrow a try.

Thank you!
Harald

> Am 11.04.2016 um 20:54 schrieb Chuck Atkins <chuck.atkins at kitware.com>:
> 
> Hi Harald,
> 
> I don't have an answer to your VGL problem yet, but in the mean time, are you tied to having to use it that way?  If not, you also have the option of running ParaView in client / server mode which may actually be more ideal for your situation: i.e. with pvserver running on the headless server and the ParaView GUI client on your local machine (workstation / desktop / laptop, etc.) and connecting to the remote server.  Doing so, you can actually bypass vgl and likely get much better performance.  If you're running an X server on the remote machine, you can do this by setting your DISPLAY variable to the local x server:
> 
> ssh foo at bigserver
> [foo at bigserver ~]$ DISPLAY=:0.0 pvserver
> Waiting for client...
> Connection URL: cs://bigserver.supercooldomain.com:11111
> Accepting connection(s): bigserver.supercooldomain.com:11111
> 
> Then in the client you select [Conenct] -> [Add Server] to create the connection to the remote machine.
> 
> Or I also noticed that you're running a very recent version of the NVidia driver.  I believe this actually has EGL support, which will allow you to build ParaView configured to use the GPU for off screen rendering with no X server necessary at all.  To do this, configure ParaView with the following CMake options:
> 	? -DVTK_RENDERING_BACKEND=OpenGL2
> 	? -DVTK_USE_OFFSCREEN_EGL=ON
> You would then run pvserver on the remote machine with no need for an X server and connect to it with the GUI client in the same way.
> 
> 
> - Chuck
> 
> On Mon, Apr 11, 2016 at 1:07 PM, Harald Klimach <harald at klimachs.de> wrote:
> Dear Chuck, dear Ken,
> 
> thanks for the replies.
> 
> > I've had similar issues with VirtulGL and VTK in the past.  The "Shader object was not initialized, cannot attach it." error is often the result of some sort of required OpenGL version support for a specific call is lacking.  A few questions:
> >       ? Are you able to run on the actual machine without Virtual GL?
> the machine is a headless server down in our machine room, and I can not easily access it.
> 
> >       ? What does the output of glxinfo running in the x2go+VirtualGL environment look like?
> Here is how it looks like:
> $ vglrun glxinfo
> name of display: :55
> display: :55  screen: 0
> direct rendering: Yes
> server glx vendor string: VirtualGL
> server glx version string: 1.4
> server glx extensions:
>     GLX_ARB_create_context, GLX_ARB_create_context_profile,
>     GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_swap_control,
>     GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, GLX_EXT_visual_rating,
>     GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGI_make_current_read,
>     GLX_SGI_swap_control, GLX_SUN_get_transparent_index
> client glx vendor string: VirtualGL
> client glx version string: 1.4
> client glx extensions:
>     GLX_ARB_create_context, GLX_ARB_create_context_profile,
>     GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_swap_control,
>     GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, GLX_EXT_visual_rating,
>     GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGI_make_current_read,
>     GLX_SGI_swap_control, GLX_SUN_get_transparent_index
> GLX version: 1.4
> GLX extensions:
>     GLX_ARB_create_context, GLX_ARB_create_context_profile,
>     GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_swap_control,
>     GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, GLX_EXT_visual_rating,
>     GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGI_make_current_read,
>     GLX_SGI_swap_control, GLX_SUN_get_transparent_index
> OpenGL vendor string: NVIDIA Corporation
> OpenGL renderer string: Tesla M2075/PCIe/SSE2
> OpenGL core profile version string: 4.5.0 NVIDIA 361.28
> OpenGL core profile shading language version string: 4.50 NVIDIA
> OpenGL core profile context flags: (none)
> OpenGL core profile profile mask: core profile
> ?
> lots of extensions
> ?
> OpenGL version string: 4.5.0 NVIDIA 361.28
> OpenGL shading language version string: 4.50 NVIDIA
> OpenGL context flags: (none)
> OpenGL profile mask: (none)
> 
> 
> ---
> Without vglrun I get:
> 
> $ glxinfo
> name of display: :55
> display: :55  screen: 0
> direct rendering: No (If you want to find out why, try setting LIBGL_DEBUG=verbose)
> server glx vendor string: SGI
> server glx version string: 1.2
> server glx extensions:
>     GLX_ARB_multisample, GLX_EXT_import_context, GLX_EXT_visual_info,
>     GLX_EXT_visual_rating, GLX_OML_swap_method, GLX_SGIS_multisample,
>     GLX_SGIX_fbconfig, GLX_SGIX_hyperpipe, GLX_SGIX_swap_barrier,
>     GLX_SGI_make_current_read
> client glx vendor string: NVIDIA Corporation
> client glx version string: 1.4
> client glx extensions:
>     GLX_ARB_context_flush_control, GLX_ARB_create_context,
>     GLX_ARB_create_context_profile, GLX_ARB_create_context_robustness,
>     GLX_ARB_fbconfig_float, GLX_ARB_get_proc_address, GLX_ARB_multisample,
>     GLX_EXT_buffer_age, GLX_EXT_create_context_es2_profile,
>     GLX_EXT_create_context_es_profile, GLX_EXT_fbconfig_packed_float,
>     GLX_EXT_framebuffer_sRGB, GLX_EXT_import_context, GLX_EXT_stereo_tree,
>     GLX_EXT_swap_control, GLX_EXT_swap_control_tear,
>     GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, GLX_EXT_visual_rating,
>     GLX_NV_copy_buffer, GLX_NV_copy_image, GLX_NV_delay_before_swap,
>     GLX_NV_float_buffer, GLX_NV_multisample_coverage, GLX_NV_present_video,
>     GLX_NV_swap_group, GLX_NV_video_capture, GLX_NV_video_out,
>     GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGI_swap_control,
>     GLX_SGI_video_sync
> GLX version: 1.2
> GLX extensions:
>     GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_import_context,
>     GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_SGIX_fbconfig
> OpenGL vendor string: Mesa project: www.mesa3d.org
> OpenGL renderer string: Mesa GLX Indirect
> OpenGL version string: 1.2 (1.5 Mesa 6.4.1)
> 
> 
> ---
> On my local box, I get:
> 
> $ glxinfo
> name of display: /private/tmp/com.apple.launchd.vDdJxiOxqs/org.macosforge.xquartz:0
> display: /private/tmp/com.apple.launchd.vDdJxiOxqs/org.macosforge.xquartz:0  screen: 0
> direct rendering: Yes
> server glx vendor string: SGI
> server glx version string: 1.4
> server glx extensions:
>     GLX_ARB_multisample, GLX_EXT_import_context, GLX_EXT_visual_info,
>     GLX_EXT_visual_rating, GLX_OML_swap_method, GLX_SGIS_multisample,
>     GLX_SGIX_fbconfig
> client glx vendor string: Mesa Project and SGI
> client glx version string: 1.4
> client glx extensions:
>     GLX_ARB_create_context, GLX_ARB_create_context_profile,
>     GLX_ARB_create_context_robustness, GLX_ARB_fbconfig_float,
>     GLX_ARB_framebuffer_sRGB, GLX_ARB_get_proc_address, GLX_ARB_multisample,
>     GLX_EXT_buffer_age, GLX_EXT_create_context_es2_profile,
>     GLX_EXT_fbconfig_packed_float, GLX_EXT_framebuffer_sRGB,
>     GLX_EXT_import_context, GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info,
>     GLX_EXT_visual_rating, GLX_INTEL_swap_event, GLX_MESA_copy_sub_buffer,
>     GLX_MESA_multithread_makecurrent, GLX_MESA_query_renderer,
>     GLX_MESA_swap_control, GLX_OML_swap_method, GLX_OML_sync_control,
>     GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer,
>     GLX_SGIX_visual_select_group, GLX_SGI_make_current_read,
>     GLX_SGI_swap_control, GLX_SGI_video_sync
> GLX version: 1.4
> GLX extensions:
>     GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_import_context,
>     GLX_EXT_visual_info, GLX_EXT_visual_rating,
>     GLX_MESA_multithread_makecurrent, GLX_OML_swap_method,
>     GLX_SGIS_multisample, GLX_SGIX_fbconfig
> OpenGL vendor string: Intel
> OpenGL renderer string: Intel(R) Iris(TM) Graphics 6100
> OpenGL version string: 2.1 INTEL-10.6.33
> OpenGL shading language version string: 1.20
> 
> Paraview 5.0.0 works on my local Mac, but I am not 100% sure, whether it is using OpenGL2.
> Somehow the paraview.org website is not responding right now, so I can?t download 5.0.1 and
> give it another try.
> 
> ---
> I also get a segmentation fault if I run with just X-Forwarding in a regular SSH connection, without
> any further information:
> $ paraview
> Segmentation fault (core dumped)
> 
> ---
> If I run in a x2go session, I get:
> $ paraview
> failed to get the current screen resources
> QXcbConnection: XCB error: 172 (Unknown), sequence: 166, resource id: 163, major code: 149 (Unknown), minor code: 20
> Segmentation fault (core dumped)
> 
> (Where I believe the XCB error is unrelated.)
> 
> ---
> If I run paraview in a vglconnect session without x2go, I get the same error as within the x2go session:
> 
> $ vglrun paraview
> ERROR: In /home/gk772/abs/paraview/src/ParaView-v5.0.1-source/VTK/Rendering/OpenGL2/vtkOpenGLRenderWindow.cxx, line 575
> vtkXOpenGLRenderWindow (0x3673960): GLEW could not be initialized.
> 
> 
> ERROR: In /home/gk772/abs/paraview/src/ParaView-v5.0.1-source/VTK/Rendering/OpenGL2/vtkShaderProgram.cxx, line 399
> vtkShaderProgram (0x36651f0): Shader object was not initialized, cannot attach it.
> 
> 
> Segmentation fault (core dumped)
> 
> 
> > On Mon, Apr 11, 2016 at 9:56 AM, Ken Martin <ken.martin at kitware.com> wrote:
> > As I understand it VirtualGL should transparently forward OpenGL/GLX/etc calls from the server to the client so that the client GPU is used. So my guess would be to first try running PV on the client and see if it works. If that seems to work fine then you know your client graphics supports PVs use of OpenGL and the issue could be in VirtualGL or some PV/VirtualGL interaction.
> I am always confused with this server and client terminology in the X context.
> The remote machine, where I try to run paraview on has a relatively strong nVidia graphics card,
> which we would like to utilize via the virtualgl mechanism.
> With the x2go we also try to keep the X-server on that box as much as possible, thus we have both,
> the X-server and the paraview application running there. As far as I understand it, the graphics
> capabilities of my local laptop should not really matter that much in this scenario.
> I probably should try and run paraview on the box itself, but as I said above, it is not that easily
> accessible.
> 
> Thanks a lot!
> Harald
> 


From read.sean62 at gmail.com  Tue Apr 12 05:53:36 2016
From: read.sean62 at gmail.com (sean read)
Date: Tue, 12 Apr 2016 09:53:36 +0000
Subject: [Paraview] python error when importing paraview.simple with
	paraview 5.0
Message-ID: <CABt37mLbZQnUGS2CmaFHewaJRKASW_4AMjnmbugPF0iqbDaubQ@mail.gmail.com>

So I've downloaded paraview5.0 from the website
http://www.paraview.org/download/nload/ <http://www.paraview.org/download/>,
and set my python path as

:/home/sean/bin/ParaView-5.0.1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.0:/home/sean/bin/ParaView-5.0.1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.0/site-packages/vtk:/home/sean/bin/ParaView-5.0.1-Qt4-OpenGL2-MPI-Linux-64bit/bin:/home/sean/bin/ParaView-5.0.1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.0/site-packages

When I import paraview.simple in python I get the error message

ImportError: libvtkCommonCorePython27D-pv5.0.so.1: cannot open shared
object file: No such file or directory

but libvtkCommonCorePython27D-pv5.0.so.1 is in
/home/sean/bin/ParaView-5.0.1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.0,
which is in my python path.

PV python is functioning as normal

I am running linux mint 17.3

Any suggestions?
-- 
Sean Read
Level 1 Yantra Yoga Instructor
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160412/b929b422/attachment.html>

From utkarsh.ayachit at kitware.com  Tue Apr 12 08:12:16 2016
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Tue, 12 Apr 2016 08:12:16 -0400
Subject: [Paraview] python error when importing paraview.simple with
 paraview 5.0
In-Reply-To: <CABt37mLbZQnUGS2CmaFHewaJRKASW_4AMjnmbugPF0iqbDaubQ@mail.gmail.com>
References: <CABt37mLbZQnUGS2CmaFHewaJRKASW_4AMjnmbugPF0iqbDaubQ@mail.gmail.com>
Message-ID: <CADHSJjBOj3ac0oty5h9Vrvv8HtS9iDPFgmKc2TmvHM+XS0CkuA@mail.gmail.com>

Try setting your LD_LIBRARY_PATH to include the ".../lib/paraview-5.0"
directory.

On Tue, Apr 12, 2016 at 5:53 AM, sean read <read.sean62 at gmail.com> wrote:
> So I've downloaded paraview5.0 from the website
> http://www.paraview.org/download/nload/, and set my python path as
>
> :/home/sean/bin/ParaView-5.0.1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.0:/home/sean/bin/ParaView-5.0.1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.0/site-packages/vtk:/home/sean/bin/ParaView-5.0.1-Qt4-OpenGL2-MPI-Linux-64bit/bin:/home/sean/bin/ParaView-5.0.1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.0/site-packages
>
> When I import paraview.simple in python I get the error message
>
> ImportError: libvtkCommonCorePython27D-pv5.0.so.1: cannot open shared object
> file: No such file or directory
>
> but libvtkCommonCorePython27D-pv5.0.so.1 is in
> /home/sean/bin/ParaView-5.0.1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.0,
> which is in my python path.
>
> PV python is functioning as normal
>
> I am running linux mint 17.3
>
> Any suggestions?
> --
> Sean Read
> Level 1 Yantra Yoga Instructor
>
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview
>

From read.sean62 at gmail.com  Tue Apr 12 08:18:44 2016
From: read.sean62 at gmail.com (sean read)
Date: Tue, 12 Apr 2016 12:18:44 +0000
Subject: [Paraview] python error when importing paraview.simple with
 paraview 5.0
In-Reply-To: <CADHSJjBOj3ac0oty5h9Vrvv8HtS9iDPFgmKc2TmvHM+XS0CkuA@mail.gmail.com>
References: <CABt37mLbZQnUGS2CmaFHewaJRKASW_4AMjnmbugPF0iqbDaubQ@mail.gmail.com>
 <CADHSJjBOj3ac0oty5h9Vrvv8HtS9iDPFgmKc2TmvHM+XS0CkuA@mail.gmail.com>
Message-ID: <CABt37m+NYaX5QMZgotZ_-O0ndZfce_SeXasL1+7NVuoUQoRsUg@mail.gmail.com>

Great! that fixed the problem, now everything is working perfectly

On Tue, 12 Apr 2016 at 22:12 Utkarsh Ayachit <utkarsh.ayachit at kitware.com>
wrote:

> Try setting your LD_LIBRARY_PATH to include the ".../lib/paraview-5.0"
> directory.
>
> On Tue, Apr 12, 2016 at 5:53 AM, sean read <read.sean62 at gmail.com> wrote:
> > So I've downloaded paraview5.0 from the website
> > http://www.paraview.org/download/nload/, and set my python path as
> >
> >
> :/home/sean/bin/ParaView-5.0.1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.0:/home/sean/bin/ParaView-5.0.1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.0/site-packages/vtk:/home/sean/bin/ParaView-5.0.1-Qt4-OpenGL2-MPI-Linux-64bit/bin:/home/sean/bin/ParaView-5.0.1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.0/site-packages
> >
> > When I import paraview.simple in python I get the error message
> >
> > ImportError: libvtkCommonCorePython27D-pv5.0.so.1: cannot open shared
> object
> > file: No such file or directory
> >
> > but libvtkCommonCorePython27D-pv5.0.so.1 is in
> >
> /home/sean/bin/ParaView-5.0.1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.0,
> > which is in my python path.
> >
> > PV python is functioning as normal
> >
> > I am running linux mint 17.3
> >
> > Any suggestions?
> > --
> > Sean Read
> > Level 1 Yantra Yoga Instructor
> >
> >
> > _______________________________________________
> > Powered by www.kitware.com
> >
> > Visit other Kitware open-source projects at
> > http://www.kitware.com/opensource/opensource.html
> >
> > Please keep messages on-topic and check the ParaView Wiki at:
> > http://paraview.org/Wiki/ParaView
> >
> > Search the list archives at: http://markmail.org/search/?q=ParaView
> >
> > Follow this link to subscribe/unsubscribe:
> > http://public.kitware.com/mailman/listinfo/paraview
> >
>
-- 
Sean Read
Level 1 Yantra Yoga Instructor
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160412/db1fd809/attachment.html>

From lukasz.paluszek at airbus.com  Tue Apr 12 08:24:11 2016
From: lukasz.paluszek at airbus.com (Paluszek, Lukasz)
Date: Tue, 12 Apr 2016 12:24:11 +0000
Subject: [Paraview] Re-render when hovering over color legend
Message-ID: <32652_1460463863_570CE8F7_32652_8920_2_0303b4a172ea46449c52322768aa7f26@DE0-03DAG13-P03.central.mail.corp>

Hello,

I noticed that Paraview redraws a scene whenever the mouse cursor passes over the color legend or a text source. This is especially noticeable when one performs volume rendering on unstructured grids which takes some time to render. Each time I accidentally cross the color legend or a text source with the cursor, Paraview redraws the scene twice, wasting a lot of time.

To reproduce you need to volume render an unstructured data set which is big enough to take a few seconds on your machine. In my case I generated a wavelet source with the following extents:
-100 10
-100 10
-100 10

Thresholded the whole RTData extent to convert into an unstructured grid and volume rendered the Threshold. Once you see the volume render hover the mouse cursor over the color legend and your scene will be re-rendered.

Regards,
Lukasz



[Beschreibung: Beschreibung: Description?: cid:image001.png at 01CF0B8F.DB7831F0]
?ukasz Paluszek
Airbus Helicopters
Aerodynamics Department (ETGA)
86607 Donauw?rth
Germany
Tel.: +49 (90) 671 8231
Fax.: +49 (90) 671 9122
Lukasz.Paluszek at airbus.com<mailto:Lukasz.Paluszek at airbus.com>


AIRBUS HELICOPTERS DEUTSCHLAND GmbH

Sitz der Gesellschaft / Registered Office: Donauw?rth

Registergericht / Registration Court: Amtsgericht Augsburg HRB 16508

Vorsitzender des Aufsichtsrates / Chairman of the Supervisory Board: Guillaume Faury

Gesch?ftsf?hrung / Board of Management: Dr. Wolfgang Schoder, Vorsitzender / CEO; Johannes Kleidorfer; Dr. Klaus Przemeck; Martin Sch?bel; Stefan Thom?

<html><head></head><body><font color="black" face="arial" size="2">
The information in this e-mail is confidential. The contents may not be disclosed or used by anyone other than the addressee. Access to this e-mail by anyone else is unauthorised.
If you are not the intended recipient, please notify Airbus immediately and delete this e-mail.
Airbus cannot accept any responsibility for the accuracy or completeness of this e-mail as it has been sent over public networks. If you have any concerns over the content of this message or its Accuracy or Integrity, please contact Airbus immediately.
All outgoing e-mails from Airbus are checked using regularly updated virus scanning software but you should take whatever measures you deem to be appropriate to ensure that this message and any attachments are virus free.
</font>
</body>
</html>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160412/f7a79a80/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 16151 bytes
Desc: image001.png
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160412/f7a79a80/attachment.png>

From harald at klimachs.de  Tue Apr 12 09:39:52 2016
From: harald at klimachs.de (Harald Klimach)
Date: Tue, 12 Apr 2016 15:39:52 +0200
Subject: [Paraview] setup pvserver with remote rendering,
	was Segfault with OpenGL2
In-Reply-To: <CAOXZzG7p56p9Nn57RXTs+yXMjDKVZEJoj--0VkK77tog+7Sdew@mail.gmail.com>
References: <84D39543-ADC1-4210-A8D8-7D230A61D6AC@klimachs.de>
 <CANXz0SYsU8YyTSjKZiF3DuNSLnBOq9h9UQwp7CTgmg-8o8vjQA@mail.gmail.com>
 <CAOXZzG72H0LfFw6V1WztJC30eHjMhPY0JBeP7shQHbfDW7jbZg@mail.gmail.com>
 <53626D34-B441-4AB5-ABEC-90F12DB91A03@klimachs.de>
 <CAOXZzG7p56p9Nn57RXTs+yXMjDKVZEJoj--0VkK77tog+7Sdew@mail.gmail.com>
Message-ID: <B260134F-4D99-420D-878C-3A1565632527@klimachs.de>

Hi,

> Or I also noticed that you're running a very recent version of the NVidia driver.  I believe this actually has EGL support, which will allow you to build ParaView configured to use the GPU for off screen rendering with no X server necessary at all.  To do this, configure ParaView with the following CMake options:
> 	? -DVTK_RENDERING_BACKEND=OpenGL2
> 	? -DVTK_USE_OFFSCREEN_EGL=ON
> You would then run pvserver on the remote machine with no need for an X server and connect to it with the GUI client in the same way.

I gave this a try.

But it results in an error box with:

OpenGL drivers on the server side don't support
required OpenGL features for basic rendering.
Remote rendering will be disabled.

OpenGL Vendor: NVIDIA Corporation
OpenGL Version: 4.5.0 NVIDIA 361.28
OpenGL Renderer: Tesla M2075/PCIe/SSE2

What am I doing wrong?
How can I enable the remote rendering. Are there other compilation flags I need to take care of?

Also, this only works if I set this up manually (run pvserver on the remote box) and then create a ssh-tunnel
to connect to it.
If I use a command in the pvserver configuration of the client gui, to create the ssh tunnel and start the
pvserver on the remote box, I get:

OpenGL Vendor: Information Unavailable
OpenGL Version: Information Unavailable
OpenGL Renderer: Information Unavailable


I guess, I am doing something wrong here, too:

I have: Server Type = Client/Server
Host=localhost
Port=11772
Command:  ssh -L 11772:remote-box:11772 user at remote-box pvserver --server-port=11772



And if I do this command manually, and afterwards try to connect to the server, I get::

ERROR: In /home/user/abs/paraview/src/ParaView-v5.0.1-source/VTK/Rendering/OpenGL2/vtkEGLRenderWindow.cxx, line 315
vtkEGLRenderWindow (0x1660940): Only EGL 1.4 and greater allows OpenGL as client API. See eglBindAPI for more information.

ERROR: In /home/user/abs/paraview/src/ParaView-v5.0.1-source/VTK/Rendering/OpenGL2/vtkOpenGLRenderWindow.cxx, line 575
vtkEGLRenderWindow (0x1660940): GLEW could not be initialized.

[shu:09048] *** Process received signal ***
[shu:09048] Signal: Segmentation fault (11)
[shu:09048] Signal code: Address not mapped (1)
[shu:09048] Failing at address: (nil)
[shu:09048] [ 0] /usr/lib/libc.so.6(+0x33330)[0x7f0c77394330]
[shu:09048] *** End of error message ***

Maybe this is due to a different environment in the tunneled login over the interactive login?
Some settings that are available in the interactive shell, but not in the tunneled command:
SSH_TTY
ETS_TOOLKIT

If I set DISPLAY=:0.0 in tunneling command, I get the same error as in the manual setup.
Maybe, my compilation with EGL did not succeed?

I used these flags:
   -DVTK_USE_X:BOOL=OFF \                                                       
   -DVTK_RENDERING_BACKEND:STRING=OpenGL2 \                                     
   -DVTK_USE_OFFSCREEN_EGL=ON \                                                 

Thanks for your kind support!
Harald

From utkarsh.ayachit at kitware.com  Tue Apr 12 09:35:00 2016
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Tue, 12 Apr 2016 09:35:00 -0400
Subject: [Paraview] no glyphs when using renderserver...
In-Reply-To: <5EB8727F81F2DC4093C7370FDCB6EA3E099996ED@IISB-SMS01.iisb.local>
References: <5EB8727F81F2DC4093C7370FDCB6EA3E099996ED@IISB-SMS01.iisb.local>
Message-ID: <CADHSJjD3Li8HR=d=10Q-bWw1ctcqPzqHy_pMDj_dkzr5NqMi1g@mail.gmail.com>

Seems to be some issue on rendering remotely, period. Can you look at
the About dialog and see what OpenGL version it reports for client and
server sides?

On Mon, Apr 11, 2016 at 6:05 AM, Jung Thomas
<Thomas.Jung at iisb.fraunhofer.de> wrote:
> Dear all,
>
> I am new to using pvserver, the problem I describe appears with
> ParaView-5.0.1-Qt4-OpenGL2-MPI-Linux-64bit, but also with elder versions I
> compiled myself.
>
> Everything seemed to be fine at first, but then I realized there is
> something wrong with stream tracers and glyps(arrows), I believe on the
> client side.
> Stream tracers do show when I press left mouse button and move it, then they
> dissappear again.
> 3D glyps don't show up at all.
> Scalar fields, meshes are being displayed o.k. however.
> Using local rendering however everything is fine. I have the vague idea it
> could be related to some local refresh mechanism, but not enough knowledge
> to figure that out.
>
> Thank you for any hint, and have a nice day!
>
>
>
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview
>

From chuck.atkins at kitware.com  Tue Apr 12 12:34:28 2016
From: chuck.atkins at kitware.com (Chuck Atkins)
Date: Tue, 12 Apr 2016 12:34:28 -0400
Subject: [Paraview] setup pvserver with remote rendering,
 was Segfault with OpenGL2
In-Reply-To: <B260134F-4D99-420D-878C-3A1565632527@klimachs.de>
References: <84D39543-ADC1-4210-A8D8-7D230A61D6AC@klimachs.de>
 <CANXz0SYsU8YyTSjKZiF3DuNSLnBOq9h9UQwp7CTgmg-8o8vjQA@mail.gmail.com>
 <CAOXZzG72H0LfFw6V1WztJC30eHjMhPY0JBeP7shQHbfDW7jbZg@mail.gmail.com>
 <53626D34-B441-4AB5-ABEC-90F12DB91A03@klimachs.de>
 <CAOXZzG7p56p9Nn57RXTs+yXMjDKVZEJoj--0VkK77tog+7Sdew@mail.gmail.com>
 <B260134F-4D99-420D-878C-3A1565632527@klimachs.de>
Message-ID: <CAOXZzG7+xiS1qnRsqZyEvGxsVooWD9T5JW8pWEVP5AszHCbSgA@mail.gmail.com>

What do the EGL settings in your CMakeCache look like?  You can find them
from the build directory:

$ grep '^EGL[^-]*=' CMakeCache.txt
EGL_INCLUDE_DIR:PATH=/usr/include
EGL_LIBRARY:FILEPATH=/usr/lib64/libEGL.so
EGL_gldispatch_LIBRARY:FILEPATH=/usr/lib64/libGLdispatch.so
EGL_opengl_LIBRARY:FILEPATH=/usr/lib64/libOpenGL.so

Your output will likely use different paths as this is from a Fedora
installation.

- Chuck

On Tue, Apr 12, 2016 at 9:39 AM, Harald Klimach <harald at klimachs.de> wrote:

> Hi,
>
> > Or I also noticed that you're running a very recent version of the
> NVidia driver.  I believe this actually has EGL support, which will allow
> you to build ParaView configured to use the GPU for off screen rendering
> with no X server necessary at all.  To do this, configure ParaView with the
> following CMake options:
> >       ? -DVTK_RENDERING_BACKEND=OpenGL2
> >       ? -DVTK_USE_OFFSCREEN_EGL=ON
> > You would then run pvserver on the remote machine with no need for an X
> server and connect to it with the GUI client in the same way.
>
> I gave this a try.
>
> But it results in an error box with:
>
> OpenGL drivers on the server side don't support
> required OpenGL features for basic rendering.
> Remote rendering will be disabled.
>
> OpenGL Vendor: NVIDIA Corporation
> OpenGL Version: 4.5.0 NVIDIA 361.28
> OpenGL Renderer: Tesla M2075/PCIe/SSE2
>
> What am I doing wrong?
> How can I enable the remote rendering. Are there other compilation flags I
> need to take care of?
>
> Also, this only works if I set this up manually (run pvserver on the
> remote box) and then create a ssh-tunnel
> to connect to it.
> If I use a command in the pvserver configuration of the client gui, to
> create the ssh tunnel and start the
> pvserver on the remote box, I get:
>
> OpenGL Vendor: Information Unavailable
> OpenGL Version: Information Unavailable
> OpenGL Renderer: Information Unavailable
>
>
> I guess, I am doing something wrong here, too:
>
> I have: Server Type = Client/Server
> Host=localhost
> Port=11772
> Command:  ssh -L 11772:remote-box:11772 user at remote-box pvserver
> --server-port=11772
>
>
>
> And if I do this command manually, and afterwards try to connect to the
> server, I get::
>
> ERROR: In
> /home/user/abs/paraview/src/ParaView-v5.0.1-source/VTK/Rendering/OpenGL2/vtkEGLRenderWindow.cxx,
> line 315
> vtkEGLRenderWindow (0x1660940): Only EGL 1.4 and greater allows OpenGL as
> client API. See eglBindAPI for more information.
>
> ERROR: In
> /home/user/abs/paraview/src/ParaView-v5.0.1-source/VTK/Rendering/OpenGL2/vtkOpenGLRenderWindow.cxx,
> line 575
> vtkEGLRenderWindow (0x1660940): GLEW could not be initialized.
>
> [shu:09048] *** Process received signal ***
> [shu:09048] Signal: Segmentation fault (11)
> [shu:09048] Signal code: Address not mapped (1)
> [shu:09048] Failing at address: (nil)
> [shu:09048] [ 0] /usr/lib/libc.so.6(+0x33330)[0x7f0c77394330]
> [shu:09048] *** End of error message ***
>
> Maybe this is due to a different environment in the tunneled login over
> the interactive login?
> Some settings that are available in the interactive shell, but not in the
> tunneled command:
> SSH_TTY
> ETS_TOOLKIT
>
> If I set DISPLAY=:0.0 in tunneling command, I get the same error as in the
> manual setup.
> Maybe, my compilation with EGL did not succeed?
>
> I used these flags:
>    -DVTK_USE_X:BOOL=OFF \
>    -DVTK_RENDERING_BACKEND:STRING=OpenGL2 \
>    -DVTK_USE_OFFSCREEN_EGL=ON \
>
> Thanks for your kind support!
> Harald
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160412/58c971a5/attachment.html>

From harald at klimachs.de  Tue Apr 12 13:11:41 2016
From: harald at klimachs.de (Harald Klimach)
Date: Tue, 12 Apr 2016 19:11:41 +0200
Subject: [Paraview] setup pvserver with remote rendering,
	was Segfault with OpenGL2
In-Reply-To: <CAOXZzG7+xiS1qnRsqZyEvGxsVooWD9T5JW8pWEVP5AszHCbSgA@mail.gmail.com>
References: <84D39543-ADC1-4210-A8D8-7D230A61D6AC@klimachs.de>
 <CANXz0SYsU8YyTSjKZiF3DuNSLnBOq9h9UQwp7CTgmg-8o8vjQA@mail.gmail.com>
 <CAOXZzG72H0LfFw6V1WztJC30eHjMhPY0JBeP7shQHbfDW7jbZg@mail.gmail.com>
 <53626D34-B441-4AB5-ABEC-90F12DB91A03@klimachs.de>
 <CAOXZzG7p56p9Nn57RXTs+yXMjDKVZEJoj--0VkK77tog+7Sdew@mail.gmail.com>
 <B260134F-4D99-420D-878C-3A1565632527@klimachs.de>
 <CAOXZzG7+xiS1qnRsqZyEvGxsVooWD9T5JW8pWEVP5AszHCbSgA@mail.gmail.com>
Message-ID: <E2493324-6524-4A3A-87C8-36129EE28661@klimachs.de>

> What do the EGL settings in your CMakeCache look like?  You can find them from the build directory:

Here is what I have:

$ grep '^EGL[^-]*=' CMakeCache.txt
EGL_INCLUDE_DIR:PATH=/usr/include
EGL_LIBRARY:FILEPATH=/usr/lib64/libEGL.so
EGL_gldispatch_LIBRARY:FILEPATH=/usr/lib64/libGLdispatch.so
EGL_opengl_LIBRARY:FILEPATH=/usr/lib64/libOpenGL.so


$ ls /usr/include/EGL/
eglextchromium.h  eglext.h  egl.h  eglmesaext.h  eglplatform.h


The EGL library has been installed by the nvidia package:

$ pacman -Qo /usr/lib64/libEGL.so
/usr/lib/libEGL.so is owned by nvidia-libgl 361.28-5


> 
> $ grep '^EGL[^-]*=' CMakeCache.txt 
> EGL_INCLUDE_DIR:PATH=/usr/include
> EGL_LIBRARY:FILEPATH=/usr/lib64/libEGL.so
> EGL_gldispatch_LIBRARY:FILEPATH=/usr/lib64/libGLdispatch.so
> EGL_opengl_LIBRARY:FILEPATH=/usr/lib64/libOpenGL.so
> 
> Your output will likely use different paths as this is from a Fedora installation.


From harald at klimachs.de  Tue Apr 12 13:55:30 2016
From: harald at klimachs.de (Harald Klimach)
Date: Tue, 12 Apr 2016 19:55:30 +0200
Subject: [Paraview] Segfault with OpenGL2
In-Reply-To: <CAOXZzG7p56p9Nn57RXTs+yXMjDKVZEJoj--0VkK77tog+7Sdew@mail.gmail.com>
References: <84D39543-ADC1-4210-A8D8-7D230A61D6AC@klimachs.de>
 <CANXz0SYsU8YyTSjKZiF3DuNSLnBOq9h9UQwp7CTgmg-8o8vjQA@mail.gmail.com>
 <CAOXZzG72H0LfFw6V1WztJC30eHjMhPY0JBeP7shQHbfDW7jbZg@mail.gmail.com>
 <53626D34-B441-4AB5-ABEC-90F12DB91A03@klimachs.de>
 <CAOXZzG7p56p9Nn57RXTs+yXMjDKVZEJoj--0VkK77tog+7Sdew@mail.gmail.com>
Message-ID: <F18A2721-CB6F-492B-B542-5A747FE0FFD2@klimachs.de>

If I use this option via the X-server on the remote machine:

> I don't have an answer to your VGL problem yet, but in the mean time, are you tied to having to use it that way?  If not, you also have the option of running ParaView in client / server mode which may actually be more ideal for your situation: i.e. with pvserver running on the headless server and the ParaView GUI client on your local machine (workstation / desktop / laptop, etc.) and connecting to the remote server.  Doing so, you can actually bypass vgl and likely get much better performance.  If you're running an X server on the remote machine, you can do this by setting your DISPLAY variable to the local x server:
> 
> ssh foo at bigserver
> [foo at bigserver ~]$ DISPLAY=:0.0 pvserver
> Waiting for client...
> Connection URL: cs://bigserver.supercooldomain.com:11111
> Accepting connection(s): bigserver.supercooldomain.com:11111

I don?t get the error message box.
But, one thing I noticed now, is that in this case the Connection information in About Paraview shows me
a different OpenGL version string in the OpenGL2 compiled pvserver than in the one without OpenGL2
support.

with OpenGL2 the OpenGL-Version is: 3.2.0 NVIDIA 361.28
without, the OpenGL-Version is: 4.5.0 NVIDIA 361.28

Now I am somewhat confused, as the EGL built pvserver with OpenGL2 backend also complained about
OpenGL-Version 4.5.0 NVIDIA 361.28.

So, with legacy OpenGL rendering backend I have 4.5.0.
With OpenGL2, but no EGL I have 3.2.0.
With OpenGL2 and EGL I again have 4.5.0.

legacy OpenGL works via VirtualGL,
OpenGL2 works as a pvserver using the X display on the remote machine without any error message boxes
(I guess this is the option I?ll deploy now),
OpenGL2 and EGL works as pvserver, but somehow still requires me to set the DISPLAY=:0.0, if I am not mistaken,
and it has the reported error message pop-up, saying that remote rendering is disabled.


From chuck.atkins at kitware.com  Tue Apr 12 14:08:44 2016
From: chuck.atkins at kitware.com (Chuck Atkins)
Date: Tue, 12 Apr 2016 14:08:44 -0400
Subject: [Paraview] setup pvserver with remote rendering,
 was Segfault with OpenGL2
In-Reply-To: <B260134F-4D99-420D-878C-3A1565632527@klimachs.de>
References: <84D39543-ADC1-4210-A8D8-7D230A61D6AC@klimachs.de>
 <CANXz0SYsU8YyTSjKZiF3DuNSLnBOq9h9UQwp7CTgmg-8o8vjQA@mail.gmail.com>
 <CAOXZzG72H0LfFw6V1WztJC30eHjMhPY0JBeP7shQHbfDW7jbZg@mail.gmail.com>
 <53626D34-B441-4AB5-ABEC-90F12DB91A03@klimachs.de>
 <CAOXZzG7p56p9Nn57RXTs+yXMjDKVZEJoj--0VkK77tog+7Sdew@mail.gmail.com>
 <B260134F-4D99-420D-878C-3A1565632527@klimachs.de>
Message-ID: <CAOXZzG7QNqBwDWvNpmnvfutyFTCWRRTqM_yzNsbr4DmuhhQz-w@mail.gmail.com>

>
> I have: Server Type = Client/Server
> Host=localhost
> Port=11772
> Command:  ssh -L 11772:remote-box:11772 user at remote-box pvserver
> --server-port=11772
>

When remotely launching a pvserver in this sort of configuration (i.e. egl
+ directly via an ssh command), a few things make this easier / more
reliable:

   - Disable OpenGL version testing.
      - This works around an issue with EGL in pvserver at the moment with
      remote rendering.
      - Use reverse port forwarding instead.
      - Basically the client listens and the server initiates a connection
      back through the tunnel.
   - Run the connection command within an xterm to be able to easily see
   pvserver output and to enter any necessary credentials via stdin (if you
   can't do key based authentication, for example).
      - Not necessary but a nice to have

Combining both of these, try the following settings:

   - Server Type = Client / Server (reverse connection)
   - Port: 11772
   - Command:

   xterm -e ssh -R 11772:localhost:11772 user at remotebox
   /path/to/install/bin/pvserver --disable-xdisplay-test --reverse-connection
   --client-host=localhost --server-port=11772



> If I set DISPLAY=:0.0 in tunneling command, I get the same error as in the
> manual setup.
>

When using EGL, there is no X server interaction so the DISPLAY variable
isn't used.



> Maybe, my compilation with EGL did not succeed?
>

Try with the above mentioned connection configuration and we'll go from
there.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160412/685f04ca/attachment.html>

From chuck.atkins at kitware.com  Tue Apr 12 14:12:20 2016
From: chuck.atkins at kitware.com (Chuck Atkins)
Date: Tue, 12 Apr 2016 14:12:20 -0400
Subject: [Paraview] setup pvserver with remote rendering,
 was Segfault with OpenGL2
In-Reply-To: <CAOXZzG7QNqBwDWvNpmnvfutyFTCWRRTqM_yzNsbr4DmuhhQz-w@mail.gmail.com>
References: <84D39543-ADC1-4210-A8D8-7D230A61D6AC@klimachs.de>
 <CANXz0SYsU8YyTSjKZiF3DuNSLnBOq9h9UQwp7CTgmg-8o8vjQA@mail.gmail.com>
 <CAOXZzG72H0LfFw6V1WztJC30eHjMhPY0JBeP7shQHbfDW7jbZg@mail.gmail.com>
 <53626D34-B441-4AB5-ABEC-90F12DB91A03@klimachs.de>
 <CAOXZzG7p56p9Nn57RXTs+yXMjDKVZEJoj--0VkK77tog+7Sdew@mail.gmail.com>
 <B260134F-4D99-420D-878C-3A1565632527@klimachs.de>
 <CAOXZzG7QNqBwDWvNpmnvfutyFTCWRRTqM_yzNsbr4DmuhhQz-w@mail.gmail.com>
Message-ID: <CAOXZzG7Pr3OAbDLXFuv5ONjYJa708sPHAa6rn5yehfEEdAvD_A@mail.gmail.com>

Let's drop this thread and resume further discussion on the original thread
for consistency.  I'll copy and repost this message on the original thread.

- Chuck

On Tue, Apr 12, 2016 at 2:08 PM, Chuck Atkins <chuck.atkins at kitware.com>
wrote:

> I have: Server Type = Client/Server
>> Host=localhost
>> Port=11772
>> Command:  ssh -L 11772:remote-box:11772 user at remote-box pvserver
>> --server-port=11772
>>
>
> When remotely launching a pvserver in this sort of configuration (i.e. egl
> + directly via an ssh command), a few things make this easier / more
> reliable:
>
>    - Disable OpenGL version testing.
>       - This works around an issue with EGL in pvserver at the moment
>       with remote rendering.
>       - Use reverse port forwarding instead.
>       - Basically the client listens and the server initiates a
>       connection back through the tunnel.
>    - Run the connection command within an xterm to be able to easily see
>    pvserver output and to enter any necessary credentials via stdin (if you
>    can't do key based authentication, for example).
>       - Not necessary but a nice to have
>
> Combining both of these, try the following settings:
>
>    - Server Type = Client / Server (reverse connection)
>    - Port: 11772
>    - Command:
>
>    xterm -e ssh -R 11772:localhost:11772 user at remotebox
>    /path/to/install/bin/pvserver --disable-xdisplay-test --reverse-connection
>    --client-host=localhost --server-port=11772
>
>
>
>> If I set DISPLAY=:0.0 in tunneling command, I get the same error as in
>> the manual setup.
>>
>
> When using EGL, there is no X server interaction so the DISPLAY variable
> isn't used.
>
>
>
>> Maybe, my compilation with EGL did not succeed?
>>
>
> Try with the above mentioned connection configuration and we'll go from
> there.
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160412/4f1b7ee6/attachment.html>

From chuck.atkins at kitware.com  Tue Apr 12 14:14:43 2016
From: chuck.atkins at kitware.com (Chuck Atkins)
Date: Tue, 12 Apr 2016 14:14:43 -0400
Subject: [Paraview] Segfault with OpenGL2
In-Reply-To: <F18A2721-CB6F-492B-B542-5A747FE0FFD2@klimachs.de>
References: <84D39543-ADC1-4210-A8D8-7D230A61D6AC@klimachs.de>
 <CANXz0SYsU8YyTSjKZiF3DuNSLnBOq9h9UQwp7CTgmg-8o8vjQA@mail.gmail.com>
 <CAOXZzG72H0LfFw6V1WztJC30eHjMhPY0JBeP7shQHbfDW7jbZg@mail.gmail.com>
 <53626D34-B441-4AB5-ABEC-90F12DB91A03@klimachs.de>
 <CAOXZzG7p56p9Nn57RXTs+yXMjDKVZEJoj--0VkK77tog+7Sdew@mail.gmail.com>
 <F18A2721-CB6F-492B-B542-5A747FE0FFD2@klimachs.de>
Message-ID: <CAOXZzG4jytRe=p0nWZDzwPeUr4QFkv_c=Mac_0MY8xD3wQV0sA@mail.gmail.com>

>
> I have: Server Type = Client/Server
> Host=localhost
> Port=11772
> Command:  ssh -L 11772:remote-box:11772 user at remote-box pvserver
> --server-port=11772
>

When remotely launching a pvserver in this sort of configuration (i.e. egl
+ directly via an ssh command), a few things make this easier / more
reliable:

   - Disable OpenGL version testing.
      - This works around an issue with EGL in pvserver at the moment with
      remote rendering.
      - Use reverse port forwarding instead.
      - Basically the client listens and the server initiates a connection
      back through the tunnel.
   - Run the connection command within an xterm to be able to easily see
   pvserver output and to enter any necessary credentials via stdin (if you
   can't do key based authentication, for example).
      - Not necessary but a nice to have

Combining both of these, try the following settings:

   - Server Type = Client / Server (reverse connection)
   - Port: 11772
   - Command:

   xterm -e ssh -R 11772:localhost:11772 user at remotebox
   /path/to/install/bin/pvserver --disable-xdisplay-test --reverse-connection
   --client-host=localhost --server-port=11772



> If I set DISPLAY=:0.0 in tunneling command, I get the same error as in the
> manual setup.
>

When using EGL, there is no X server interaction so the DISPLAY variable
isn't used.



> Maybe, my compilation with EGL did not succeed?
>

Try with the above mentioned connection configuration and we'll go from
there.  I definitely suggest trying to stick with the new OpenGL back-end
if we can get the issues worked out as it's typically ~ 20x - 100x faster
for geometry rendering and 2x - 10x faster for volume rendering.

- Chuck

On Tue, Apr 12, 2016 at 1:55 PM, Harald Klimach <harald at klimachs.de> wrote:

> If I use this option via the X-server on the remote machine:
>
> > I don't have an answer to your VGL problem yet, but in the mean time,
> are you tied to having to use it that way?  If not, you also have the
> option of running ParaView in client / server mode which may actually be
> more ideal for your situation: i.e. with pvserver running on the headless
> server and the ParaView GUI client on your local machine (workstation /
> desktop / laptop, etc.) and connecting to the remote server.  Doing so, you
> can actually bypass vgl and likely get much better performance.  If you're
> running an X server on the remote machine, you can do this by setting your
> DISPLAY variable to the local x server:
> >
> > ssh foo at bigserver
> > [foo at bigserver ~]$ DISPLAY=:0.0 pvserver
> > Waiting for client...
> > Connection URL: cs://bigserver.supercooldomain.com:11111
> > Accepting connection(s): bigserver.supercooldomain.com:11111
>
> I don?t get the error message box.
> But, one thing I noticed now, is that in this case the Connection
> information in About Paraview shows me
> a different OpenGL version string in the OpenGL2 compiled pvserver than in
> the one without OpenGL2
> support.
>
> with OpenGL2 the OpenGL-Version is: 3.2.0 NVIDIA 361.28
> without, the OpenGL-Version is: 4.5.0 NVIDIA 361.28
>
> Now I am somewhat confused, as the EGL built pvserver with OpenGL2 backend
> also complained about
> OpenGL-Version 4.5.0 NVIDIA 361.28.
>
> So, with legacy OpenGL rendering backend I have 4.5.0.
> With OpenGL2, but no EGL I have 3.2.0.
> With OpenGL2 and EGL I again have 4.5.0.
>
> legacy OpenGL works via VirtualGL,
> OpenGL2 works as a pvserver using the X display on the remote machine
> without any error message boxes
> (I guess this is the option I?ll deploy now),
> OpenGL2 and EGL works as pvserver, but somehow still requires me to set
> the DISPLAY=:0.0, if I am not mistaken,
> and it has the reported error message pop-up, saying that remote rendering
> is disabled.
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160412/49d4a6a3/attachment.html>

From harald at klimachs.de  Tue Apr 12 14:27:31 2016
From: harald at klimachs.de (Harald Klimach)
Date: Tue, 12 Apr 2016 20:27:31 +0200
Subject: [Paraview] Segfault with OpenGL2
In-Reply-To: <CAOXZzG4jytRe=p0nWZDzwPeUr4QFkv_c=Mac_0MY8xD3wQV0sA@mail.gmail.com>
References: <84D39543-ADC1-4210-A8D8-7D230A61D6AC@klimachs.de>
 <CANXz0SYsU8YyTSjKZiF3DuNSLnBOq9h9UQwp7CTgmg-8o8vjQA@mail.gmail.com>
 <CAOXZzG72H0LfFw6V1WztJC30eHjMhPY0JBeP7shQHbfDW7jbZg@mail.gmail.com>
 <53626D34-B441-4AB5-ABEC-90F12DB91A03@klimachs.de>
 <CAOXZzG7p56p9Nn57RXTs+yXMjDKVZEJoj--0VkK77tog+7Sdew@mail.gmail.com>
 <F18A2721-CB6F-492B-B542-5A747FE0FFD2@klimachs.de>
 <CAOXZzG4jytRe=p0nWZDzwPeUr4QFkv_c=Mac_0MY8xD3wQV0sA@mail.gmail.com>
Message-ID: <E844436F-0040-47CD-8DC4-40785908B0B0@klimachs.de>

Dear Chuck,

thanks a lot for your continued support.

> 	? Server Type = Client / Server (reverse connection)
> 	? Port: 11772
> 	? Command:
> xterm -e ssh -R 11772:localhost:11772 user at remotebox /path/to/install/bin/pvserver --disable-xdisplay-test --reverse-connection --client-host=localhost --server-port=11772

First, this seemed to do the trick, but then I tried to open the Paraview about menu and got the segfault again.
The xterm tracked the error messages:

Connecting to client (reverse connection requested)...
Connection URL: csrc://localhost:11772
Client connected.
ERROR: In /home/user/abs/paraview/src/ParaView-v5.0.1-source/VTK/Rendering/OpenGL2/vtkEGLRenderWindow.cxx, line 315
vtkEGLRenderWindow (0x1b10e40): Only EGL 1.4 and greater allows OpenGL as client API. See eglBindAPI for more information.

ERROR: In /home/user/abs/paraview/src/ParaView-v5.0.1-source/VTK/Rendering/OpenGL2/vtkOpenGLRenderWindow.cxx, line 575
vtkEGLRenderWindow (0x1b10e40): GLEW could not be initialized.

[remote:08935] *** Process received signal ***
[remote:08935] Signal: Segmentation fault (11)
[remote:08935] Signal code: Address not mapped (1)
[remote:08935] Failing at address: (nil)
[remote:08935] [ 0] /usr/lib/libc.so.6(+0x33330)[0x7f15692d2330]
[remote:08935] *** End of error message ***

Best,
Harald

From dennis_conklin at goodyear.com  Tue Apr 12 16:02:18 2016
From: dennis_conklin at goodyear.com (Dennis Conklin)
Date: Tue, 12 Apr 2016 20:02:18 +0000
Subject: [Paraview] v5.0.1 & RealVNC
Message-ID: <CY1PR07MB2506A851C555D9491B6D73279F950@CY1PR07MB2506.namprd07.prod.outlook.com>

All,

So I started testing Paraview v5.0.1 Linux and it doesn't work with RealVNC v4, or v5.1.1 or v5.3 (dies with Segmentation fault without even displaying a screen).   Earlier versions of Paraview work but not 5.0.1.  I am not very familiar with VNC.   Are there graphics or other options in VNC that need to be tuned that I could refer to my sysops?

Thanks for any hints.

Dennis
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160412/13464b96/attachment.html>

From chuck.atkins at kitware.com  Tue Apr 12 16:23:26 2016
From: chuck.atkins at kitware.com (Chuck Atkins)
Date: Tue, 12 Apr 2016 16:23:26 -0400
Subject: [Paraview] Segfault with OpenGL2
In-Reply-To: <E844436F-0040-47CD-8DC4-40785908B0B0@klimachs.de>
References: <84D39543-ADC1-4210-A8D8-7D230A61D6AC@klimachs.de>
 <CANXz0SYsU8YyTSjKZiF3DuNSLnBOq9h9UQwp7CTgmg-8o8vjQA@mail.gmail.com>
 <CAOXZzG72H0LfFw6V1WztJC30eHjMhPY0JBeP7shQHbfDW7jbZg@mail.gmail.com>
 <53626D34-B441-4AB5-ABEC-90F12DB91A03@klimachs.de>
 <CAOXZzG7p56p9Nn57RXTs+yXMjDKVZEJoj--0VkK77tog+7Sdew@mail.gmail.com>
 <F18A2721-CB6F-492B-B542-5A747FE0FFD2@klimachs.de>
 <CAOXZzG4jytRe=p0nWZDzwPeUr4QFkv_c=Mac_0MY8xD3wQV0sA@mail.gmail.com>
 <E844436F-0040-47CD-8DC4-40785908B0B0@klimachs.de>
Message-ID: <CAOXZzG4o0us2L14MMJMJO6iUL8zWXOMaSeLbGe3Vr9jE478jGQ@mail.gmail.com>

Unfortunately I suspect this is an issue with NVIDIA driver. Their EGL
support is still brand new and currently seems to be fairly brittle between
driver releases so perhaps best to wait until it settles a bit and just
stick with X for now :-(.  Are you able to use the X+OpenGL2 (i.e. no egl)
pvserver for remote rendering?

- Chuck

On Tue, Apr 12, 2016 at 2:27 PM, Harald Klimach <harald at klimachs.de> wrote:

> Dear Chuck,
>
> thanks a lot for your continued support.
>
> >       ? Server Type = Client / Server (reverse connection)
> >       ? Port: 11772
> >       ? Command:
> > xterm -e ssh -R 11772:localhost:11772 user at remotebox
> /path/to/install/bin/pvserver --disable-xdisplay-test --reverse-connection
> --client-host=localhost --server-port=11772
>
> First, this seemed to do the trick, but then I tried to open the Paraview
> about menu and got the segfault again.
> The xterm tracked the error messages:
>
> Connecting to client (reverse connection requested)...
> Connection URL: csrc://localhost:11772
> Client connected.
> ERROR: In
> /home/user/abs/paraview/src/ParaView-v5.0.1-source/VTK/Rendering/OpenGL2/vtkEGLRenderWindow.cxx,
> line 315
> vtkEGLRenderWindow (0x1b10e40): Only EGL 1.4 and greater allows OpenGL as
> client API. See eglBindAPI for more information.
>
> ERROR: In
> /home/user/abs/paraview/src/ParaView-v5.0.1-source/VTK/Rendering/OpenGL2/vtkOpenGLRenderWindow.cxx,
> line 575
> vtkEGLRenderWindow (0x1b10e40): GLEW could not be initialized.
>
> [remote:08935] *** Process received signal ***
> [remote:08935] Signal: Segmentation fault (11)
> [remote:08935] Signal code: Address not mapped (1)
> [remote:08935] Failing at address: (nil)
> [remote:08935] [ 0] /usr/lib/libc.so.6(+0x33330)[0x7f15692d2330]
> [remote:08935] *** End of error message ***
>
> Best,
> Harald
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160412/23533e13/attachment.html>

From harald at klimachs.de  Tue Apr 12 16:42:02 2016
From: harald at klimachs.de (Harald Klimach)
Date: Tue, 12 Apr 2016 22:42:02 +0200
Subject: [Paraview] Segfault with OpenGL2
In-Reply-To: <CAOXZzG4o0us2L14MMJMJO6iUL8zWXOMaSeLbGe3Vr9jE478jGQ@mail.gmail.com>
References: <84D39543-ADC1-4210-A8D8-7D230A61D6AC@klimachs.de>
 <CANXz0SYsU8YyTSjKZiF3DuNSLnBOq9h9UQwp7CTgmg-8o8vjQA@mail.gmail.com>
 <CAOXZzG72H0LfFw6V1WztJC30eHjMhPY0JBeP7shQHbfDW7jbZg@mail.gmail.com>
 <53626D34-B441-4AB5-ABEC-90F12DB91A03@klimachs.de>
 <CAOXZzG7p56p9Nn57RXTs+yXMjDKVZEJoj--0VkK77tog+7Sdew@mail.gmail.com>
 <F18A2721-CB6F-492B-B542-5A747FE0FFD2@klimachs.de>
 <CAOXZzG4jytRe=p0nWZDzwPeUr4QFkv_c=Mac_0MY8xD3wQV0sA@mail.gmail.com>
 <E844436F-0040-47CD-8DC4-40785908B0B0@klimachs.de>
 <CAOXZzG4o0us2L14MMJMJO6iUL8zWXOMaSeLbGe3Vr9jE478jGQ@mail.gmail.com>
Message-ID: <CD101372-6D18-45C0-B5F3-F752897AF032@klimachs.de>

> Unfortunately I suspect this is an issue with NVIDIA driver. Their EGL support is still brand new and currently seems to be fairly brittle between driver releases so perhaps best to wait until it settles a bit and just stick with X for now :-(.  Are you able to use the X+OpenGL2 (i.e. no egl)  pvserver for remote rendering?

Yes, as reported in http://paraview.markmail.org/thread/c46ycyk3db4spov4, this
option seems to work. One weird thing I observed is the different OpenGL version
strings reported when using OpenGL2+EGL.

X+OpenGL2 is perfectly fine, I?ll test this a little more extensively.
Thanks a lot for bearing with me!

Harald

From chuck.atkins at kitware.com  Tue Apr 12 18:05:21 2016
From: chuck.atkins at kitware.com (Chuck Atkins)
Date: Tue, 12 Apr 2016 18:05:21 -0400
Subject: [Paraview] v5.0.1 & RealVNC
In-Reply-To: <CY1PR07MB2506A851C555D9491B6D73279F950@CY1PR07MB2506.namprd07.prod.outlook.com>
References: <CY1PR07MB2506A851C555D9491B6D73279F950@CY1PR07MB2506.namprd07.prod.outlook.com>
Message-ID: <CAOXZzG6iyK=Vm21eBJRMoipvN7Hs7gDPUw0bA8iPRHKtM=a9og@mail.gmail.com>

Sorry, forgot to cc the list.

Hi Dennis, a few questions:

Are you using the binaries from paraview.org or did you build it yourself?
Does the machine with the vnc server have a GPU you're trying use?
You said previous versions of paraview worked.  Does that include 5.0 and
4.x or just 4.x?
On Apr 12, 2016 4:04 PM, "Dennis Conklin" <dennis_conklin at goodyear.com>
wrote:

> All,
>
>
>
> So I started testing Paraview v5.0.1 Linux and it doesn?t work with
> RealVNC v4, or v5.1.1 or v5.3 (dies with Segmentation fault without even
> displaying a screen).   Earlier versions of Paraview work but not 5.0.1.  I
> am not very familiar with VNC.   Are there graphics or other options in VNC
> that need to be tuned that I could refer to my sysops?
>
>
>
> Thanks for any hints.
>
>
>
> Dennis
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160412/c7ea2a43/attachment.html>

From read.sean62 at gmail.com  Tue Apr 12 22:04:35 2016
From: read.sean62 at gmail.com (sean read)
Date: Wed, 13 Apr 2016 02:04:35 +0000
Subject: [Paraview] python error when importing paraview.simple with
 paraview 5.0
In-Reply-To: <CABt37m+NYaX5QMZgotZ_-O0ndZfce_SeXasL1+7NVuoUQoRsUg@mail.gmail.com>
References: <CABt37mLbZQnUGS2CmaFHewaJRKASW_4AMjnmbugPF0iqbDaubQ@mail.gmail.com>
 <CADHSJjBOj3ac0oty5h9Vrvv8HtS9iDPFgmKc2TmvHM+XS0CkuA@mail.gmail.com>
 <CABt37m+NYaX5QMZgotZ_-O0ndZfce_SeXasL1+7NVuoUQoRsUg@mail.gmail.com>
Message-ID: <CABt37mJ0mVHg8mLn1TiaTa6g+AGxmqAZFG5dEK-RJaXE5YkynQ@mail.gmail.com>

Wait, check that, so adding  ".../lib/paraview-5.0" did fix the problem
with python, but it has had other negative side effects. Now when I open
certain filetypes in vim (so far that I've checked, .py, .tex, .bib, which
are all types for which I have customised options) the terminal window
shows strange text. For example:

 "exim.py" 258L, 6565CTraceback (most recent call last):
                                                         File
"/usr/lib/python2.7/site.py", line 563, in <module>

                                         main()

                                                 File
"/usr/lib/python2.7/site.py", line 545, in main


                             known_paths = addusersitepackages(known_paths)



 File "/usr/lib/python2.7/site.py", line 272, in addusersitepackages
                                                               user_site =
getusersitepackages())



After this it becomes unresponsive and I have to close the terminal. I am
not entirely familiar with the use of the LD_LIBRARY_PATH, is there any
reason that this alteration would effect the operation of vim?


On Tue, 12 Apr 2016 at 22:18 sean read <read.sean62 at gmail.com> wrote:

> Great! that fixed the problem, now everything is working perfectly
>
> On Tue, 12 Apr 2016 at 22:12 Utkarsh Ayachit <utkarsh.ayachit at kitware.com>
> wrote:
>
>> Try setting your LD_LIBRARY_PATH to include the ".../lib/paraview-5.0"
>> directory.
>>
>> On Tue, Apr 12, 2016 at 5:53 AM, sean read <read.sean62 at gmail.com> wrote:
>> > So I've downloaded paraview5.0 from the website
>> > http://www.paraview.org/download/nload/, and set my python path as
>> >
>> >
>> :/home/sean/bin/ParaView-5.0.1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.0:/home/sean/bin/ParaView-5.0.1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.0/site-packages/vtk:/home/sean/bin/ParaView-5.0.1-Qt4-OpenGL2-MPI-Linux-64bit/bin:/home/sean/bin/ParaView-5.0.1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.0/site-packages
>> >
>> > When I import paraview.simple in python I get the error message
>> >
>> > ImportError: libvtkCommonCorePython27D-pv5.0.so.1: cannot open shared
>> object
>> > file: No such file or directory
>> >
>> > but libvtkCommonCorePython27D-pv5.0.so.1 is in
>> >
>> /home/sean/bin/ParaView-5.0.1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.0,
>> > which is in my python path.
>> >
>> > PV python is functioning as normal
>> >
>> > I am running linux mint 17.3
>> >
>> > Any suggestions?
>> > --
>> > Sean Read
>> > Level 1 Yantra Yoga Instructor
>> >
>> >
>> > _______________________________________________
>> > Powered by www.kitware.com
>> >
>> > Visit other Kitware open-source projects at
>> > http://www.kitware.com/opensource/opensource.html
>> >
>> > Please keep messages on-topic and check the ParaView Wiki at:
>> > http://paraview.org/Wiki/ParaView
>> >
>> > Search the list archives at: http://markmail.org/search/?q=ParaView
>> >
>> > Follow this link to subscribe/unsubscribe:
>> > http://public.kitware.com/mailman/listinfo/paraview
>> >
>>
> --
> Sean Read
> Level 1 Yantra Yoga Instructor
>
> --
Sean Read
Level 1 Yantra Yoga Instructor
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160413/608f45b7/attachment.html>

From pmopanhx at gmail.com  Wed Apr 13 00:05:25 2016
From: pmopanhx at gmail.com (hengxing pan)
Date: Wed, 13 Apr 2016 12:05:25 +0800
Subject: [Paraview] How to smooth a polygonal line ?
Message-ID: <CAFJvLTaTW45GSihsR066vx5uEdJj-oE31uw9uYKTxVv1aFyE=Q@mail.gmail.com>

Hi, all
As the title says, I'm wondering if there is a filter smoothing a polygonal
line (vtk format), since there is a filter named as ''smooth' which only
can be applied to the surface data type. I think I have to do a curve
fitting in Paraview, but I dont know how to do it exactly. Does anyone have
a idea about that ?  Thank you in advance !
The attached is a ploygonal line.vtk I wrote.
Hengxing
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160413/fdf45959/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: line.vtk
Type: application/octet-stream
Size: 814 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160413/fdf45959/attachment.obj>

From Thomas.Jung at iisb.fraunhofer.de  Wed Apr 13 06:30:59 2016
From: Thomas.Jung at iisb.fraunhofer.de (Jung Thomas)
Date: Wed, 13 Apr 2016 10:30:59 +0000
Subject: [Paraview]  no glyphs when using renderserver...
Message-ID: <5EB8727F81F2DC4093C7370FDCB6EA3E0999A7BA@IISB-SMS01.iisb.local>


Message: 9
Date: Tue, 12 Apr 2016 09:35:00 -0400
From: Utkarsh Ayachit <utkarsh.ayachit at kitware.com>
To: Jung Thomas <Thomas.Jung at iisb.fraunhofer.de>
Cc: "paraview at paraview.org" <paraview at paraview.org>
Subject: Re: [Paraview] no glyphs when using renderserver...
Message-ID:
        <CADHSJjD3Li8HR=d=10Q-bWw1ctcqPzqHy_pMDj_dkzr5NqMi1g at mail.gmail.com>
Content-Type: text/plain; charset=UTF-8

Seems to be some issue on rendering remotely, period. Can you look at
the About dialog and see what OpenGL version it reports for client and
server sides?

On Mon, Apr 11, 2016 at 6:05 AM, Jung Thomas
<Thomas.Jung at iisb.fraunhofer.de> wrote:
> Dear all,
>
> I am new to using pvserver, the problem I describe appears with
> ParaView-5.0.1-Qt4-OpenGL2-MPI-Linux-64bit, but also with elder versions I
> compiled myself.
>
> Everything seemed to be fine at first, but then I realized there is
> something wrong with stream tracers and glyps(arrows), I believe on the
> client side.
> Stream tracers do show when I press left mouse button and move it, then they
> dissappear again.
> 3D glyps don't show up at all.
> Scalar fields, meshes are being displayed o.k. however.
> Using local rendering however everything is fine. I have the vague idea it
> could be related to some local refresh mechanism, but not enough knowledge
> to figure that out.
>
> Thank you for any hint, and have a nice day!
>
>


I am new to this list and did not find another way to answers as copying this part from the daily digest and resending it to paraview at paraview.org.
If that is not the correct way, would you please let me know how to do that?

I could not figure out how to copy the text from the About dialog, could not even mark or select it, so I attach the client and connection part as screenshots.
The OpenGL-Versions are 3.2.0 NVIDIA 340.65 on the client and 3.2.0 NVIDIA 352.79 in the connection tab.

Thank you!
-------------- next part --------------
A non-text attachment was scrubbed...
Name: client.png
Type: image/png
Size: 53315 bytes
Desc: client.png
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160413/636e86f3/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: connection.png
Type: image/png
Size: 54328 bytes
Desc: connection.png
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160413/636e86f3/attachment-0001.png>

From harald at klimachs.de  Wed Apr 13 06:44:11 2016
From: harald at klimachs.de (Harald Klimach)
Date: Wed, 13 Apr 2016 12:44:11 +0200
Subject: [Paraview] Segfault with OpenGL2
In-Reply-To: <CD101372-6D18-45C0-B5F3-F752897AF032@klimachs.de>
References: <84D39543-ADC1-4210-A8D8-7D230A61D6AC@klimachs.de>
 <CANXz0SYsU8YyTSjKZiF3DuNSLnBOq9h9UQwp7CTgmg-8o8vjQA@mail.gmail.com>
 <CAOXZzG72H0LfFw6V1WztJC30eHjMhPY0JBeP7shQHbfDW7jbZg@mail.gmail.com>
 <53626D34-B441-4AB5-ABEC-90F12DB91A03@klimachs.de>
 <CAOXZzG7p56p9Nn57RXTs+yXMjDKVZEJoj--0VkK77tog+7Sdew@mail.gmail.com>
 <F18A2721-CB6F-492B-B542-5A747FE0FFD2@klimachs.de>
 <CAOXZzG4jytRe=p0nWZDzwPeUr4QFkv_c=Mac_0MY8xD3wQV0sA@mail.gmail.com>
 <E844436F-0040-47CD-8DC4-40785908B0B0@klimachs.de>
 <CAOXZzG4o0us2L14MMJMJO6iUL8zWXOMaSeLbGe3Vr9jE478jGQ@mail.gmail.com>
 <CD101372-6D18-45C0-B5F3-F752897AF032@klimachs.de>
Message-ID: <B4D4E337-E9DA-42E1-A6E9-DFCCB500E61A@klimachs.de>

The X+OpenGL2 via pvserver works fine for me now.
However, my colleagues with older local laptops do have some trouble.

My local system uses:
OpenGL Version 4.1 INTEL-10.6.33
OpenGL Renderer Intel Iris Graphics 6100

This works nicely.

With an older graphics card like:
OpenGL Version 3.3 INTEL-10.0.40
OpenGL Renderer Intel HD Graphics 3000 OpenGL Engine

There is only a small 3D screen section that is actually usable, the rest of the screen has garbled output.
The Legend can be displayed correctly on top of the garbled 3D content, and when rotating or moving the
geometry also the complete scenery is correctly shown. As soon as the 3D scenery is still, there are
parts of the screen garbled.

When going back to the legacy OpenGL backend on the server, both kinds of clients
die when trying to render a 3D object.

> Am 12.04.2016 um 22:42 schrieb Harald Klimach <harald at klimachs.de>:
> 
>> Unfortunately I suspect this is an issue with NVIDIA driver. Their EGL support is still brand new and currently seems to be fairly brittle between driver releases so perhaps best to wait until it settles a bit and just stick with X for now :-(.  Are you able to use the X+OpenGL2 (i.e. no egl)  pvserver for remote rendering?
> 
> Yes, as reported in http://paraview.markmail.org/thread/c46ycyk3db4spov4, this
> option seems to work. One weird thing I observed is the different OpenGL version
> strings reported when using OpenGL2+EGL.
> 
> X+OpenGL2 is perfectly fine, I?ll test this a little more extensively.
> Thanks a lot for bearing with me!
> 
> Harald
> _______________________________________________
> Powered by www.kitware.com
> 
> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html
> 
> Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView
> 
> Search the list archives at: http://markmail.org/search/?q=ParaView
> 
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 496 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160413/416d0dbe/attachment.sig>

From padamsen at grundfos.com  Wed Apr 13 07:38:52 2016
From: padamsen at grundfos.com (Per Adamsen)
Date: Wed, 13 Apr 2016 11:38:52 +0000
Subject: [Paraview] Specifying camera movement using points from a file
Message-ID: <AM4PR03MB1457B8D640B86CF4CB158BADA4960@AM4PR03MB1457.eurprd03.prod.outlook.com>

Hi,

I have been playing with the camera animations in PV5.0 and was wondering if there was an easier way to specify the camera path than manually adding and dragging points.

Is it possible to copy paste camera coordinates from a file to obtain e.g. a helical path?

Thank you in advance.

Regards,
Per
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160413/258253ac/attachment.html>

From dennis_conklin at goodyear.com  Wed Apr 13 07:43:43 2016
From: dennis_conklin at goodyear.com (Dennis Conklin)
Date: Wed, 13 Apr 2016 11:43:43 +0000
Subject: [Paraview] [EXT] Re:  v5.0.1 & RealVNC
In-Reply-To: <CAOXZzG6iyK=Vm21eBJRMoipvN7Hs7gDPUw0bA8iPRHKtM=a9og@mail.gmail.com>
References: <CY1PR07MB2506A851C555D9491B6D73279F950@CY1PR07MB2506.namprd07.prod.outlook.com>
 <CAOXZzG6iyK=Vm21eBJRMoipvN7Hs7gDPUw0bA8iPRHKtM=a9og@mail.gmail.com>
Message-ID: <CY1PR07MB2506481270A05C7450F55FFC9F960@CY1PR07MB2506.namprd07.prod.outlook.com>

Chuck,

We are using the binaries from paraview.org.

Paraview 5.0 did not work either but we never made that Production here (timid about the re-write until the first bug fix).

We are running on a single machine (no cluster).   I?m not very knowledgeable about vnc (never use it myself, but everyone else does), so I have queried my sysadmins, but I don?t think we are trying to access a GPU on the vnc server machine ? I think we are running on the Linux box we vnc into, but I?m not 100% sure of that until they get back to me.

Thanks

Dennis



From: Chuck Atkins [mailto:chuck.atkins at kitware.com]
Sent: Tuesday, April 12, 2016 6:05 PM
To: Dennis Conklin <dennis_conklin at goodyear.com>
Cc: ParaView Mailing List <paraview at paraview.org>
Subject: [EXT] Re: [Paraview] v5.0.1 & RealVNC


Sorry, forgot to cc the list.

Hi Dennis, a few questions:

Are you using the binaries from paraview.org<http://paraview.org/> or did you build it yourself?
Does the machine with the vnc server have a GPU you're trying use?
You said previous versions of paraview worked.  Does that include 5.0 and 4.x or just 4.x?
On Apr 12, 2016 4:04 PM, "Dennis Conklin" <dennis_conklin at goodyear.com<mailto:dennis_conklin at goodyear.com>> wrote:
All,

So I started testing Paraview v5.0.1 Linux and it doesn?t work with RealVNC v4, or v5.1.1 or v5.3 (dies with Segmentation fault without even displaying a screen).   Earlier versions of Paraview work but not 5.0.1.  I am not very familiar with VNC.   Are there graphics or other options in VNC that need to be tuned that I could refer to my sysops?

Thanks for any hints.

Dennis

_______________________________________________
Powered by www.kitware.com<http://www.kitware.com>

Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView

Search the list archives at: http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160413/09951bca/attachment.html>

From u.utku.turuncoglu at be.itu.edu.tr  Wed Apr 13 08:44:16 2016
From: u.utku.turuncoglu at be.itu.edu.tr (Ufuk Utku Turuncoglu (BE))
Date: Wed, 13 Apr 2016 15:44:16 +0300
Subject: [Paraview] couple of issues related with co-processing ...
Message-ID: <570E3F20.3000602@be.itu.edu.tr>

Hi,

I am using co-processing (Catalyst) and i have couple of issues about 
the behavior of the co-processing module.

1 - If i send multiple 2d variable or single 3d variable to the 
co-processor, my custom code is working without any problem and produces 
desired output. On the other hand, the code hangs with multiple 3d 
variable (it basically opens a square white window and waits, see the 
attached screenshot). I have no idea about the problem because the 
terminal does not produces any output. I could install the ParaView in 
debug mode and it might help?

2 - The axis names (edited by Edit Axes Grid section in Properties 
window) are not written to the produced png file when the visualization 
pipeline is driven by co-processing but it looks fine under ParaView.

3 - When i trying to use volume rendering (single 3d field) along with 
co-processing, the code gives following error

ERROR: In 
/opt/progs/paraview-5.0.0/src/VTK/Common/ExecutionModel/vtkCompositeDataPipeline.cxx, 
line 171
vtkPVDataRepresentationPipeline (0x7fea05244010): Can not execute simple 
alorithm without output ports
...
...
ERROR: In 
/opt/progs/paraview-5.0.0/src/VTK/Filters/Parallel/vtkPKdTree.cxx, line 296
vtkPKdTree (0x7fea04f42840): (process 0) NumberOfDatasets = 0, cannot 
determine volume bounds.

I could produce iso-surface with same code without any problem. The 
volume rendering is also working under ParaView.

The last question might be related with the grid definition in the 
co-processing because i am using single netcdf dataset to create 
visualization scripts (python) under ParaView but in the model code 
(co-processing) the dataset is defined as MultiBlockDataSet due to the 
parallel nature of the simulation code.

Regards,

--ufuk
-------------- next part --------------
A non-text attachment was scrubbed...
Name: screen.png
Type: image/png
Size: 365002 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160413/f399742f/attachment-0001.png>

From dennis_conklin at goodyear.com  Wed Apr 13 09:05:41 2016
From: dennis_conklin at goodyear.com (Dennis Conklin)
Date: Wed, 13 Apr 2016 13:05:41 +0000
Subject: [Paraview] [EXT] Re:  v5.0.1 & RealVNC
In-Reply-To: <CAOXZzG6iyK=Vm21eBJRMoipvN7Hs7gDPUw0bA8iPRHKtM=a9og@mail.gmail.com>
References: <CY1PR07MB2506A851C555D9491B6D73279F950@CY1PR07MB2506.namprd07.prod.outlook.com>
 <CAOXZzG6iyK=Vm21eBJRMoipvN7Hs7gDPUw0bA8iPRHKtM=a9og@mail.gmail.com>
Message-ID: <CY1PR07MB25065991E3E09EC820BE40B99F960@CY1PR07MB2506.namprd07.prod.outlook.com>

Chuck,

My sysadmins respond with ?we have no GPUs?.   So, forgive my ignorance, but is it possible to configure VNC so that the rendering is done on different machines, like on the workstation you attach to versus on the VNC server machine?

Dennis

From: Chuck Atkins [mailto:chuck.atkins at kitware.com]
Sent: Tuesday, April 12, 2016 6:05 PM
To: Dennis Conklin <dennis_conklin at goodyear.com>
Cc: ParaView Mailing List <paraview at paraview.org>
Subject: [EXT] Re: [Paraview] v5.0.1 & RealVNC


Sorry, forgot to cc the list.

Hi Dennis, a few questions:

Are you using the binaries from paraview.org<http://paraview.org/> or did you build it yourself?
Does the machine with the vnc server have a GPU you're trying use?
You said previous versions of paraview worked.  Does that include 5.0 and 4.x or just 4.x?
On Apr 12, 2016 4:04 PM, "Dennis Conklin" <dennis_conklin at goodyear.com<mailto:dennis_conklin at goodyear.com>> wrote:
All,

So I started testing Paraview v5.0.1 Linux and it doesn?t work with RealVNC v4, or v5.1.1 or v5.3 (dies with Segmentation fault without even displaying a screen).   Earlier versions of Paraview work but not 5.0.1.  I am not very familiar with VNC.   Are there graphics or other options in VNC that need to be tuned that I could refer to my sysops?

Thanks for any hints.

Dennis

_______________________________________________
Powered by www.kitware.com<http://www.kitware.com>

Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView

Search the list archives at: http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160413/9344d0a4/attachment.html>

From andy.bauer at kitware.com  Wed Apr 13 09:24:08 2016
From: andy.bauer at kitware.com (Andy Bauer)
Date: Wed, 13 Apr 2016 09:24:08 -0400
Subject: [Paraview] couple of issues related with co-processing ...
In-Reply-To: <570E3F20.3000602@be.itu.edu.tr>
References: <570E3F20.3000602@be.itu.edu.tr>
Message-ID: <CAMaOp+EOZ_cXDB4H9haAzpfMBJuJ5r83Az4Aii7EKBWj=OCH2A@mail.gmail.com>

Hi Ufuk,

I would suggest testing out some of the Catalyst examples which are in the
source code under the Examples/Catalyst subdirectory. I would also suggest
creating Catalyst scripts from data sets generated through Catalyst output
instead of the NetCDF files. There are two example scripts for this in
Examples/Catalyst/SampleScripts that you can use for this.

As for the grid names for the axes, this may be a bug in ParaView. I'll
look into that.

Best,
Andy

On Wed, Apr 13, 2016 at 8:44 AM, Ufuk Utku Turuncoglu (BE) <
u.utku.turuncoglu at be.itu.edu.tr> wrote:

> Hi,
>
> I am using co-processing (Catalyst) and i have couple of issues about the
> behavior of the co-processing module.
>
> 1 - If i send multiple 2d variable or single 3d variable to the
> co-processor, my custom code is working without any problem and produces
> desired output. On the other hand, the code hangs with multiple 3d variable
> (it basically opens a square white window and waits, see the attached
> screenshot). I have no idea about the problem because the terminal does not
> produces any output. I could install the ParaView in debug mode and it
> might help?
>
> 2 - The axis names (edited by Edit Axes Grid section in Properties window)
> are not written to the produced png file when the visualization pipeline is
> driven by co-processing but it looks fine under ParaView.
>
> 3 - When i trying to use volume rendering (single 3d field) along with
> co-processing, the code gives following error
>
> ERROR: In
> /opt/progs/paraview-5.0.0/src/VTK/Common/ExecutionModel/vtkCompositeDataPipeline.cxx,
> line 171
> vtkPVDataRepresentationPipeline (0x7fea05244010): Can not execute simple
> alorithm without output ports
> ...
> ...
> ERROR: In
> /opt/progs/paraview-5.0.0/src/VTK/Filters/Parallel/vtkPKdTree.cxx, line 296
> vtkPKdTree (0x7fea04f42840): (process 0) NumberOfDatasets = 0, cannot
> determine volume bounds.
>
> I could produce iso-surface with same code without any problem. The volume
> rendering is also working under ParaView.
>
> The last question might be related with the grid definition in the
> co-processing because i am using single netcdf dataset to create
> visualization scripts (python) under ParaView but in the model code
> (co-processing) the dataset is defined as MultiBlockDataSet due to the
> parallel nature of the simulation code.
>
> Regards,
>
> --ufuk
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160413/da149e07/attachment.html>

From dennis_conklin at goodyear.com  Wed Apr 13 09:58:34 2016
From: dennis_conklin at goodyear.com (Dennis Conklin)
Date: Wed, 13 Apr 2016 13:58:34 +0000
Subject: [Paraview] [EXT] Re:  v5.0.1 & RealVNC
In-Reply-To: <CAOXZzG6iyK=Vm21eBJRMoipvN7Hs7gDPUw0bA8iPRHKtM=a9og@mail.gmail.com>
References: <CY1PR07MB2506A851C555D9491B6D73279F950@CY1PR07MB2506.namprd07.prod.outlook.com>
 <CAOXZzG6iyK=Vm21eBJRMoipvN7Hs7gDPUw0bA8iPRHKtM=a9og@mail.gmail.com>
Message-ID: <CY1PR07MB250638B049611478865878C59F960@CY1PR07MB2506.namprd07.prod.outlook.com>

Chuck,

Sorry, got additional details from the sysops.

We have GPUs in our workstations ? he was referring that we don?t have GPU clusters for computation.    I understand that the VNC server is running on the workstation that I attach to, and yes, we are using the GPU on that workstation to render.

FYI,  the workstations have Nvidia K4000 cards and we are running realVNC ? any chance this is part of your test suite?

Thanks again, sorry for the confusion, but I am NOT a Linux or VNC guru!!

Dennis

From: Chuck Atkins [mailto:chuck.atkins at kitware.com]
Sent: Tuesday, April 12, 2016 6:05 PM
To: Dennis Conklin <dennis_conklin at goodyear.com>
Cc: ParaView Mailing List <paraview at paraview.org>
Subject: [EXT] Re: [Paraview] v5.0.1 & RealVNC


Sorry, forgot to cc the list.

Hi Dennis, a few questions:

Are you using the binaries from paraview.org<http://paraview.org/> or did you build it yourself?
Does the machine with the vnc server have a GPU you're trying use?
You said previous versions of paraview worked.  Does that include 5.0 and 4.x or just 4.x?
On Apr 12, 2016 4:04 PM, "Dennis Conklin" <dennis_conklin at goodyear.com<mailto:dennis_conklin at goodyear.com>> wrote:
All,

So I started testing Paraview v5.0.1 Linux and it doesn?t work with RealVNC v4, or v5.1.1 or v5.3 (dies with Segmentation fault without even displaying a screen).   Earlier versions of Paraview work but not 5.0.1.  I am not very familiar with VNC.   Are there graphics or other options in VNC that need to be tuned that I could refer to my sysops?

Thanks for any hints.

Dennis

_______________________________________________
Powered by www.kitware.com<http://www.kitware.com>

Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView

Search the list archives at: http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160413/f89884bb/attachment.html>

From cory.quammen at kitware.com  Wed Apr 13 10:02:35 2016
From: cory.quammen at kitware.com (Cory Quammen)
Date: Wed, 13 Apr 2016 10:02:35 -0400
Subject: [Paraview] Specifying camera movement using points from a file
In-Reply-To: <AM4PR03MB1457B8D640B86CF4CB158BADA4960@AM4PR03MB1457.eurprd03.prod.outlook.com>
References: <AM4PR03MB1457B8D640B86CF4CB158BADA4960@AM4PR03MB1457.eurprd03.prod.outlook.com>
Message-ID: <CAB5Fpx7RmTTV=8RtgWS5Ryfihm0-6e3=QRD71X0QHtQbxDcPLw@mail.gmail.com>

Per,

You can do this with Python scripting in the Python console.

# get active view
renderView1 = GetActiveViewOrCreate('RenderView')

# uncomment following to set a specific view size
# renderView1.ViewSize = [689, 340]

# get camera animation track for the view
cameraAnimationCue1 = GetCameraTrack(view=renderView1)

# create keyframes for this animation track
# create a key frame
keyFrame4737 = CameraKeyFrame()
keyFrame4737.Position = [0.0, 0.0, 6.69]
keyFrame4737.ParallelScale = 1.73

keyFrame4737.PositionPathPoints = [0.0, 0.0, 5.0, 2.938926261462365,
0.0, 4.045084971874736, 4.755282581475766, 0.0, 1.545084971874737,
4.755282581475766, 0.0, -1.5450849718747361, 2.938926261462365, 0.0,
-4.045084971874735, 1.3322676295501878e-15, 0.0, -4.9999999999999964,
-2.9389262614623624, 0.0, -4.045084971874735, -4.755282581475763, 0.0,
-1.5450849718747368, -4.755282581475763, 0.0, 1.5450849718747341,
-2.9389262614623632, 0.0, 4.045084971874731]

keyFrame4737.FocalPathPoints = [0.0, 0.0, 0.0]
keyFrame4737.ClosedPositionPath = 1

# create a key frame
keyFrame4738 = CameraKeyFrame()
keyFrame4738.KeyTime = 1.0
keyFrame4738.Position = [0.0, 0.0, 6.69]
keyFrame4738.ParallelScale = 1.73

# initialize the animation track
cameraAnimationCue1.Mode = 'Path-based'
cameraAnimationCue1.KeyFrames = [keyFrame4737, keyFrame4738]

# get animation scene
animationScene1 = GetAnimationScene()

animationScene1.Play()

Just modify the keyFrame4737.PositionPathPoints. They are ordered [x,
y, z, x, y, z ...].

HTH,
Cory


On Wed, Apr 13, 2016 at 7:38 AM, Per Adamsen <padamsen at grundfos.com> wrote:
> Hi,
>
>
>
> I have been playing with the camera animations in PV5.0 and was wondering if
> there was an easier way to specify the camera path than manually adding and
> dragging points.
>
>
>
> Is it possible to copy paste camera coordinates from a file to obtain e.g. a
> helical path?
>
>
>
> Thank you in advance.
>
>
>
> Regards,
>
> Per
>
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview
>



-- 
Cory Quammen
R&D Engineer
Kitware, Inc.

From chuck.atkins at kitware.com  Wed Apr 13 11:56:20 2016
From: chuck.atkins at kitware.com (Chuck Atkins)
Date: Wed, 13 Apr 2016 11:56:20 -0400
Subject: [Paraview] [EXT] Re:  v5.0.1 & RealVNC
In-Reply-To: <CY1PR07MB250638B049611478865878C59F960@CY1PR07MB2506.namprd07.prod.outlook.com>
References: <CY1PR07MB2506A851C555D9491B6D73279F950@CY1PR07MB2506.namprd07.prod.outlook.com>
 <CAOXZzG6iyK=Vm21eBJRMoipvN7Hs7gDPUw0bA8iPRHKtM=a9og@mail.gmail.com>
 <CY1PR07MB250638B049611478865878C59F960@CY1PR07MB2506.namprd07.prod.outlook.com>
Message-ID: <CAOXZzG6BcGvWOxAc_UZdDMHWPicTFqYdt+g9iJj=7LM0tPbVgQ@mail.gmail.com>

Hi Dennis,

I suspect the GPU is not getting used by the VNC server and thus falling
back to a software OpenGL implementation with older mesa and not a new
enough OpenGL support.  Different VNC servers on Linux have different
capabilities, with some able to reach their underlying GPU and some not.
>From your VNC session, can you open up a terminal and run: glxinfo | grep
'^OpenGL' ?  That should be more telling.

- Chuck

On Wed, Apr 13, 2016 at 9:58 AM, Dennis Conklin <dennis_conklin at goodyear.com
> wrote:

> Chuck,
>
>
>
> Sorry, got additional details from the sysops.
>
>
>
> We have GPUs in our workstations ? he was referring that we don?t have GPU
> clusters for computation.    I understand that the VNC server is running on
> the workstation that I attach to, and yes, we are using the GPU on that
> workstation to render.
>
>
>
> FYI,  the workstations have Nvidia K4000 cards and we are running realVNC
> ? any chance this is part of your test suite?
>
>
>
> Thanks again, sorry for the confusion, but I am NOT a Linux or VNC guru!!
>
>
>
> Dennis
>
>
>
> *From:* Chuck Atkins [mailto:chuck.atkins at kitware.com]
> *Sent:* Tuesday, April 12, 2016 6:05 PM
> *To:* Dennis Conklin <dennis_conklin at goodyear.com>
> *Cc:* ParaView Mailing List <paraview at paraview.org>
> *Subject:* [EXT] Re: [Paraview] v5.0.1 & RealVNC
>
>
>
> Sorry, forgot to cc the list.
>
> Hi Dennis, a few questions:
>
> Are you using the binaries from paraview.org or did you build it yourself?
> Does the machine with the vnc server have a GPU you're trying use?
> You said previous versions of paraview worked.  Does that include 5.0 and
> 4.x or just 4.x?
>
> On Apr 12, 2016 4:04 PM, "Dennis Conklin" <dennis_conklin at goodyear.com>
> wrote:
>
> All,
>
>
>
> So I started testing Paraview v5.0.1 Linux and it doesn?t work with
> RealVNC v4, or v5.1.1 or v5.3 (dies with Segmentation fault without even
> displaying a screen).   Earlier versions of Paraview work but not 5.0.1.  I
> am not very familiar with VNC.   Are there graphics or other options in VNC
> that need to be tuned that I could refer to my sysops?
>
>
>
> Thanks for any hints.
>
>
>
> Dennis
>
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160413/1bef1be6/attachment.html>

From dennis_conklin at goodyear.com  Wed Apr 13 12:12:50 2016
From: dennis_conklin at goodyear.com (Dennis Conklin)
Date: Wed, 13 Apr 2016 16:12:50 +0000
Subject: [Paraview] [EXT] Re:  v5.0.1 & RealVNC
In-Reply-To: <CAOXZzG6BcGvWOxAc_UZdDMHWPicTFqYdt+g9iJj=7LM0tPbVgQ@mail.gmail.com>
References: <CY1PR07MB2506A851C555D9491B6D73279F950@CY1PR07MB2506.namprd07.prod.outlook.com>
 <CAOXZzG6iyK=Vm21eBJRMoipvN7Hs7gDPUw0bA8iPRHKtM=a9og@mail.gmail.com>
 <CY1PR07MB250638B049611478865878C59F960@CY1PR07MB2506.namprd07.prod.outlook.com>
 <CAOXZzG6BcGvWOxAc_UZdDMHWPicTFqYdt+g9iJj=7LM0tPbVgQ@mail.gmail.com>
Message-ID: <CY1PR07MB25062AA439DD5903F9C65F3A9F960@CY1PR07MB2506.namprd07.prod.outlook.com>

Chuck,

This is what I get ? none of this means anything to me!

Dennis


Xlib:  extension "NV-GLX" missing on display "alnx031:15.0".
OpenGL vendor string: Mesa project: www.mesa3d.org
OpenGL renderer string: Mesa GLX Indirect
OpenGL version string: 1.2 (1.5 Mesa 6.4.1)
OpenGL extensions:

From: Chuck Atkins [mailto:chuck.atkins at kitware.com]
Sent: Wednesday, April 13, 2016 11:56 AM
To: Dennis Conklin <dennis_conklin at goodyear.com>
Cc: ParaView Mailing List <paraview at paraview.org>
Subject: Re: [EXT] Re: [Paraview] v5.0.1 & RealVNC

Hi Dennis,
I suspect the GPU is not getting used by the VNC server and thus falling back to a software OpenGL implementation with older mesa and not a new enough OpenGL support.  Different VNC servers on Linux have different capabilities, with some able to reach their underlying GPU and some not.  From your VNC session, can you open up a terminal and run: glxinfo | grep '^OpenGL' ?  That should be more telling.

- Chuck

On Wed, Apr 13, 2016 at 9:58 AM, Dennis Conklin <dennis_conklin at goodyear.com<mailto:dennis_conklin at goodyear.com>> wrote:
Chuck,

Sorry, got additional details from the sysops.

We have GPUs in our workstations ? he was referring that we don?t have GPU clusters for computation.    I understand that the VNC server is running on the workstation that I attach to, and yes, we are using the GPU on that workstation to render.

FYI,  the workstations have Nvidia K4000 cards and we are running realVNC ? any chance this is part of your test suite?

Thanks again, sorry for the confusion, but I am NOT a Linux or VNC guru!!

Dennis

From: Chuck Atkins [mailto:chuck.atkins at kitware.com<mailto:chuck.atkins at kitware.com>]
Sent: Tuesday, April 12, 2016 6:05 PM
To: Dennis Conklin <dennis_conklin at goodyear.com<mailto:dennis_conklin at goodyear.com>>
Cc: ParaView Mailing List <paraview at paraview.org<mailto:paraview at paraview.org>>
Subject: [EXT] Re: [Paraview] v5.0.1 & RealVNC


Sorry, forgot to cc the list.

Hi Dennis, a few questions:

Are you using the binaries from paraview.org<http://paraview.org/> or did you build it yourself?
Does the machine with the vnc server have a GPU you're trying use?
You said previous versions of paraview worked.  Does that include 5.0 and 4.x or just 4.x?
On Apr 12, 2016 4:04 PM, "Dennis Conklin" <dennis_conklin at goodyear.com<mailto:dennis_conklin at goodyear.com>> wrote:
All,

So I started testing Paraview v5.0.1 Linux and it doesn?t work with RealVNC v4, or v5.1.1 or v5.3 (dies with Segmentation fault without even displaying a screen).   Earlier versions of Paraview work but not 5.0.1.  I am not very familiar with VNC.   Are there graphics or other options in VNC that need to be tuned that I could refer to my sysops?

Thanks for any hints.

Dennis

_______________________________________________
Powered by www.kitware.com<http://www.kitware.com>

Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView

Search the list archives at: http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160413/f0618034/attachment.html>

From utkarsh.ayachit at kitware.com  Wed Apr 13 14:19:44 2016
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Wed, 13 Apr 2016 14:19:44 -0400
Subject: [Paraview] [EXT] Re: v5.0.1 & RealVNC
In-Reply-To: <CY1PR07MB25062AA439DD5903F9C65F3A9F960@CY1PR07MB2506.namprd07.prod.outlook.com>
References: <CY1PR07MB2506A851C555D9491B6D73279F950@CY1PR07MB2506.namprd07.prod.outlook.com>
 <CAOXZzG6iyK=Vm21eBJRMoipvN7Hs7gDPUw0bA8iPRHKtM=a9og@mail.gmail.com>
 <CY1PR07MB250638B049611478865878C59F960@CY1PR07MB2506.namprd07.prod.outlook.com>
 <CAOXZzG6BcGvWOxAc_UZdDMHWPicTFqYdt+g9iJj=7LM0tPbVgQ@mail.gmail.com>
 <CY1PR07MB25062AA439DD5903F9C65F3A9F960@CY1PR07MB2506.namprd07.prod.outlook.com>
Message-ID: <CADHSJjBcnC8qydQ_Z++FzvXOp6FKPzm6fg1UhCGSGa42=a324g@mail.gmail.com>

Dennis,

Don't mean to distract this conversation -- I'll let Chuck follow  up
on the VNC thing -- but a a small sidetrack:

Can you trying running paraview as:

> paraview --mesa-llvm

Does that work?

Utkarsh

On Wed, Apr 13, 2016 at 12:12 PM, Dennis Conklin
<dennis_conklin at goodyear.com> wrote:
> Chuck,
>
>
>
> This is what I get ? none of this means anything to me!
>
>
>
> Dennis
>
>
>
>
>
> Xlib:  extension "NV-GLX" missing on display "alnx031:15.0".
>
> OpenGL vendor string: Mesa project: www.mesa3d.org
>
> OpenGL renderer string: Mesa GLX Indirect
>
> OpenGL version string: 1.2 (1.5 Mesa 6.4.1)
>
> OpenGL extensions:
>
>
>
> From: Chuck Atkins [mailto:chuck.atkins at kitware.com]
> Sent: Wednesday, April 13, 2016 11:56 AM
> To: Dennis Conklin <dennis_conklin at goodyear.com>
> Cc: ParaView Mailing List <paraview at paraview.org>
> Subject: Re: [EXT] Re: [Paraview] v5.0.1 & RealVNC
>
>
>
> Hi Dennis,
>
> I suspect the GPU is not getting used by the VNC server and thus falling
> back to a software OpenGL implementation with older mesa and not a new
> enough OpenGL support.  Different VNC servers on Linux have different
> capabilities, with some able to reach their underlying GPU and some not.
> From your VNC session, can you open up a terminal and run: glxinfo | grep
> '^OpenGL' ?  That should be more telling.
>
>
> - Chuck
>
>
>
> On Wed, Apr 13, 2016 at 9:58 AM, Dennis Conklin
> <dennis_conklin at goodyear.com> wrote:
>
> Chuck,
>
>
>
> Sorry, got additional details from the sysops.
>
>
>
> We have GPUs in our workstations ? he was referring that we don?t have GPU
> clusters for computation.    I understand that the VNC server is running on
> the workstation that I attach to, and yes, we are using the GPU on that
> workstation to render.
>
>
>
> FYI,  the workstations have Nvidia K4000 cards and we are running realVNC ?
> any chance this is part of your test suite?
>
>
>
> Thanks again, sorry for the confusion, but I am NOT a Linux or VNC guru!!
>
>
>
> Dennis
>
>
>
> From: Chuck Atkins [mailto:chuck.atkins at kitware.com]
> Sent: Tuesday, April 12, 2016 6:05 PM
> To: Dennis Conklin <dennis_conklin at goodyear.com>
> Cc: ParaView Mailing List <paraview at paraview.org>
> Subject: [EXT] Re: [Paraview] v5.0.1 & RealVNC
>
>
>
> Sorry, forgot to cc the list.
>
> Hi Dennis, a few questions:
>
> Are you using the binaries from paraview.org or did you build it yourself?
> Does the machine with the vnc server have a GPU you're trying use?
> You said previous versions of paraview worked.  Does that include 5.0 and
> 4.x or just 4.x?
>
> On Apr 12, 2016 4:04 PM, "Dennis Conklin" <dennis_conklin at goodyear.com>
> wrote:
>
> All,
>
>
>
> So I started testing Paraview v5.0.1 Linux and it doesn?t work with RealVNC
> v4, or v5.1.1 or v5.3 (dies with Segmentation fault without even displaying
> a screen).   Earlier versions of Paraview work but not 5.0.1.  I am not very
> familiar with VNC.   Are there graphics or other options in VNC that need to
> be tuned that I could refer to my sysops?
>
>
>
> Thanks for any hints.
>
>
>
> Dennis
>
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview
>
>
>
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview
>

From chuck.atkins at kitware.com  Wed Apr 13 14:38:25 2016
From: chuck.atkins at kitware.com (Chuck Atkins)
Date: Wed, 13 Apr 2016 14:38:25 -0400
Subject: [Paraview] [EXT] Re: v5.0.1 & RealVNC
In-Reply-To: <CADHSJjBcnC8qydQ_Z++FzvXOp6FKPzm6fg1UhCGSGa42=a324g@mail.gmail.com>
References: <CY1PR07MB2506A851C555D9491B6D73279F950@CY1PR07MB2506.namprd07.prod.outlook.com>
 <CAOXZzG6iyK=Vm21eBJRMoipvN7Hs7gDPUw0bA8iPRHKtM=a9og@mail.gmail.com>
 <CY1PR07MB250638B049611478865878C59F960@CY1PR07MB2506.namprd07.prod.outlook.com>
 <CAOXZzG6BcGvWOxAc_UZdDMHWPicTFqYdt+g9iJj=7LM0tPbVgQ@mail.gmail.com>
 <CY1PR07MB25062AA439DD5903F9C65F3A9F960@CY1PR07MB2506.namprd07.prod.outlook.com>
 <CADHSJjBcnC8qydQ_Z++FzvXOp6FKPzm6fg1UhCGSGa42=a324g@mail.gmail.com>
Message-ID: <CAOXZzG5XsjYdHnD3dgJYue42G0gd9AgBTsmwe5NJP1cup=JxDA@mail.gmail.com>

Hi Dennis,


> Xlib:  extension "NV-GLX" missing on display "alnx031:15.0".
>
> OpenGL vendor string: Mesa project: www.mesa3d.org
>
> OpenGL renderer string: Mesa GLX Indirect
>
> OpenGL version string: 1.2 (1.5 Mesa 6.4.1)
>
> OpenGL extensions:
>

As I suspected, this is telling us is that the VNC server does not have
access to the GPU on the machine it's running on and is falling back to the
Mesa software driver, which does not support the version of OpenGL that
ParaView requires.  Older versions of ParaView (4.x) used a much older
OpenGL stack while the newer 5.x releases have a completely overhauled
rendering backend but it requires support for newer OpenGL versions. So,
even though older ParaView versions worked, they still were not able to use
the GPU and likely had fairly poor performance.  Given that, there are 2
options:

   - Ideal:
      - See if your sysadmins can "fix" or configure the VNC server on the
      workstation to work with the GPU.
   - Workable:
      - Run ParaView using a newer version of Mesa.
         - You can probably use the binaries packaged with Paraview as
         Utkarsh mentioned by adding --mesa-llvm.
         - If this doesn't work, the mesa binaries we ship with ParaView
         are probably incompatible with the Linux distro the server
runs.  Which
         distro does the server run?  We may have a new version
already built that
         you can try to use.
         - Not ideal since it's still using software rendering but better
         than nothing if your admins can't get the VNC server working
with the GPU.

- Chuck

- Chuck

On Wed, Apr 13, 2016 at 2:19 PM, Utkarsh Ayachit <
utkarsh.ayachit at kitware.com> wrote:

> Dennis,
>
> Don't mean to distract this conversation -- I'll let Chuck follow  up
> on the VNC thing -- but a a small sidetrack:
>
> Can you trying running paraview as:
>
> > paraview --mesa-llvm
>
> Does that work?
>
> Utkarsh
>
> On Wed, Apr 13, 2016 at 12:12 PM, Dennis Conklin
> <dennis_conklin at goodyear.com> wrote:
> > Chuck,
> >
> >
> >
> > This is what I get ? none of this means anything to me!
> >
> >
> >
> > Dennis
> >
> >
> >
> >
> >
> > Xlib:  extension "NV-GLX" missing on display "alnx031:15.0".
> >
> > OpenGL vendor string: Mesa project: www.mesa3d.org
> >
> > OpenGL renderer string: Mesa GLX Indirect
> >
> > OpenGL version string: 1.2 (1.5 Mesa 6.4.1)
> >
> > OpenGL extensions:
> >
> >
> >
> > From: Chuck Atkins [mailto:chuck.atkins at kitware.com]
> > Sent: Wednesday, April 13, 2016 11:56 AM
> > To: Dennis Conklin <dennis_conklin at goodyear.com>
> > Cc: ParaView Mailing List <paraview at paraview.org>
> > Subject: Re: [EXT] Re: [Paraview] v5.0.1 & RealVNC
> >
> >
> >
> > Hi Dennis,
> >
> > I suspect the GPU is not getting used by the VNC server and thus falling
> > back to a software OpenGL implementation with older mesa and not a new
> > enough OpenGL support.  Different VNC servers on Linux have different
> > capabilities, with some able to reach their underlying GPU and some not.
> > From your VNC session, can you open up a terminal and run: glxinfo | grep
> > '^OpenGL' ?  That should be more telling.
> >
> >
> > - Chuck
> >
> >
> >
> > On Wed, Apr 13, 2016 at 9:58 AM, Dennis Conklin
> > <dennis_conklin at goodyear.com> wrote:
> >
> > Chuck,
> >
> >
> >
> > Sorry, got additional details from the sysops.
> >
> >
> >
> > We have GPUs in our workstations ? he was referring that we don?t have
> GPU
> > clusters for computation.    I understand that the VNC server is running
> on
> > the workstation that I attach to, and yes, we are using the GPU on that
> > workstation to render.
> >
> >
> >
> > FYI,  the workstations have Nvidia K4000 cards and we are running
> realVNC ?
> > any chance this is part of your test suite?
> >
> >
> >
> > Thanks again, sorry for the confusion, but I am NOT a Linux or VNC guru!!
> >
> >
> >
> > Dennis
> >
> >
> >
> > From: Chuck Atkins [mailto:chuck.atkins at kitware.com]
> > Sent: Tuesday, April 12, 2016 6:05 PM
> > To: Dennis Conklin <dennis_conklin at goodyear.com>
> > Cc: ParaView Mailing List <paraview at paraview.org>
> > Subject: [EXT] Re: [Paraview] v5.0.1 & RealVNC
> >
> >
> >
> > Sorry, forgot to cc the list.
> >
> > Hi Dennis, a few questions:
> >
> > Are you using the binaries from paraview.org or did you build it
> yourself?
> > Does the machine with the vnc server have a GPU you're trying use?
> > You said previous versions of paraview worked.  Does that include 5.0 and
> > 4.x or just 4.x?
> >
> > On Apr 12, 2016 4:04 PM, "Dennis Conklin" <dennis_conklin at goodyear.com>
> > wrote:
> >
> > All,
> >
> >
> >
> > So I started testing Paraview v5.0.1 Linux and it doesn?t work with
> RealVNC
> > v4, or v5.1.1 or v5.3 (dies with Segmentation fault without even
> displaying
> > a screen).   Earlier versions of Paraview work but not 5.0.1.  I am not
> very
> > familiar with VNC.   Are there graphics or other options in VNC that
> need to
> > be tuned that I could refer to my sysops?
> >
> >
> >
> > Thanks for any hints.
> >
> >
> >
> > Dennis
> >
> >
> > _______________________________________________
> > Powered by www.kitware.com
> >
> > Visit other Kitware open-source projects at
> > http://www.kitware.com/opensource/opensource.html
> >
> > Please keep messages on-topic and check the ParaView Wiki at:
> > http://paraview.org/Wiki/ParaView
> >
> > Search the list archives at: http://markmail.org/search/?q=ParaView
> >
> > Follow this link to subscribe/unsubscribe:
> > http://public.kitware.com/mailman/listinfo/paraview
> >
> >
> >
> >
> > _______________________________________________
> > Powered by www.kitware.com
> >
> > Visit other Kitware open-source projects at
> > http://www.kitware.com/opensource/opensource.html
> >
> > Please keep messages on-topic and check the ParaView Wiki at:
> > http://paraview.org/Wiki/ParaView
> >
> > Search the list archives at: http://markmail.org/search/?q=ParaView
> >
> > Follow this link to subscribe/unsubscribe:
> > http://public.kitware.com/mailman/listinfo/paraview
> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160413/2107abfb/attachment.html>

From roeber at dkrz.de  Wed Apr 13 16:32:30 2016
From: roeber at dkrz.de (=?UTF-8?Q?Niklas_R=c3=b6ber?=)
Date: Wed, 13 Apr 2016 22:32:30 +0200
Subject: [Paraview] [EXT] Re: v5.0.1 & RealVNC
In-Reply-To: <CY1PR07MB25062AA439DD5903F9C65F3A9F960@CY1PR07MB2506.namprd07.prod.outlook.com>
References: <CY1PR07MB2506A851C555D9491B6D73279F950@CY1PR07MB2506.namprd07.prod.outlook.com>
 <CAOXZzG6iyK=Vm21eBJRMoipvN7Hs7gDPUw0bA8iPRHKtM=a9og@mail.gmail.com>
 <CY1PR07MB250638B049611478865878C59F960@CY1PR07MB2506.namprd07.prod.outlook.com>
 <CAOXZzG6BcGvWOxAc_UZdDMHWPicTFqYdt+g9iJj=7LM0tPbVgQ@mail.gmail.com>
 <CY1PR07MB25062AA439DD5903F9C65F3A9F960@CY1PR07MB2506.namprd07.prod.outlook.com>
Message-ID: <570EACDE.6060507@dkrz.de>

Hi,

haven't read the entire thread, but if you want remote visualization and
HAVE GPUs, why don't you use VirtualGL? Then you would start it with
"vglrun paraview", and ParaView would get a GPU buffer for direct
rendering. It is very easy to setup, just google for VirtualGL, and if
something does not work, email me...

Cheers...
Niklas
  
>
> Chuck,
>
>  
>
> This is what I get ? none of this means anything to me!
>
>  
>
> Dennis
>
>  
>
>  
>
> Xlib:  extension "NV-GLX" missing on display "alnx031:15.0".
>
> OpenGL vendor string: Mesa project: www.mesa3d.org
>
> OpenGL renderer string: Mesa GLX Indirect
>
> OpenGL version string: 1.2 (1.5 Mesa 6.4.1)
>
> OpenGL extensions:
>
>  
>
> *From:*Chuck Atkins [mailto:chuck.atkins at kitware.com]
> *Sent:* Wednesday, April 13, 2016 11:56 AM
> *To:* Dennis Conklin <dennis_conklin at goodyear.com>
> *Cc:* ParaView Mailing List <paraview at paraview.org>
> *Subject:* Re: [EXT] Re: [Paraview] v5.0.1 & RealVNC
>
>  
>
> Hi Dennis,
>
> I suspect the GPU is not getting used by the VNC server and thus
> falling back to a software OpenGL implementation with older mesa and
> not a new enough OpenGL support.  Different VNC servers on Linux have
> different capabilities, with some able to reach their underlying GPU
> and some not.  From your VNC session, can you open up a terminal and
> run: glxinfo | grep '^OpenGL' ?  That should be more telling.
>
>
> - Chuck
>
>  
>
> On Wed, Apr 13, 2016 at 9:58 AM, Dennis Conklin
> <dennis_conklin at goodyear.com <mailto:dennis_conklin at goodyear.com>> wrote:
>
>     Chuck,
>
>      
>
>     Sorry, got additional details from the sysops.
>
>      
>
>     We have GPUs in our workstations ? he was referring that we don?t
>     have GPU clusters for computation.    I understand that the VNC
>     server is running on the workstation that I attach to, and yes, we
>     are using the GPU on that workstation to render.
>
>      
>
>     FYI,  the workstations have Nvidia K4000 cards and we are running
>     realVNC ? any chance this is part of your test suite?
>
>      
>
>     Thanks again, sorry for the confusion, but I am NOT a Linux or VNC
>     guru!!
>
>      
>
>     Dennis
>
>      
>
>     *From:*Chuck Atkins [mailto:chuck.atkins at kitware.com
>     <mailto:chuck.atkins at kitware.com>]
>     *Sent:* Tuesday, April 12, 2016 6:05 PM
>     *To:* Dennis Conklin <dennis_conklin at goodyear.com
>     <mailto:dennis_conklin at goodyear.com>>
>     *Cc:* ParaView Mailing List <paraview at paraview.org
>     <mailto:paraview at paraview.org>>
>     *Subject:* [EXT] Re: [Paraview] v5.0.1 & RealVNC
>
>      
>
>     Sorry, forgot to cc the list.
>
>     Hi Dennis, a few questions:
>
>     Are you using the binaries from paraview.org
>     <http://paraview.org/> or did you build it yourself?
>     Does the machine with the vnc server have a GPU you're trying use?
>     You said previous versions of paraview worked.  Does that include
>     5.0 and 4.x or just 4.x?
>
>     On Apr 12, 2016 4:04 PM, "Dennis Conklin"
>     <dennis_conklin at goodyear.com <mailto:dennis_conklin at goodyear.com>>
>     wrote:
>
>         All,
>
>          
>
>         So I started testing Paraview v5.0.1 Linux and it doesn?t work
>         with RealVNC v4, or v5.1.1 or v5.3 (dies with Segmentation
>         fault without even displaying a screen).   Earlier versions of
>         Paraview work but not 5.0.1.  I am not very familiar with
>         VNC.   Are there graphics or other options in VNC that need to
>         be tuned that I could refer to my sysops?
>
>          
>
>         Thanks for any hints.
>
>          
>
>         Dennis
>
>
>         _______________________________________________
>         Powered by www.kitware.com <http://www.kitware.com>
>
>         Visit other Kitware open-source projects at
>         http://www.kitware.com/opensource/opensource.html
>
>         Please keep messages on-topic and check the ParaView Wiki at:
>         http://paraview.org/Wiki/ParaView
>         <http://paraview.org/Wiki/ParaView>
>
>         Search the list archives at:
>         http://markmail.org/search/?q=ParaView
>         <http://markmail.org/search/?q=ParaView>
>
>         Follow this link to subscribe/unsubscribe:
>         http://public.kitware.com/mailman/listinfo/paraview
>
>  
>
>
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview


-- 
______________________________________________ 

Dr. Niklas R?ber
Visualisierung
Abteilung Anwendungen

Deutsches Klimarechenzentrum GmbH (DKRZ)
Bundesstra?e 45 a ? D-20146 Hamburg ? Germany

email: roeber at dkrz.de
phone: +49 (0)40 460094 283
  fax: +49 (0)40 460094 270
  web: http://www.dkrz.de/

Gesch?ftsf?hrer: Prof. Dr. Thomas Ludwig
Sitz der Gesellschaft: Hamburg
Amtsgericht Hamburg HRB 39784 
______________________________________________ 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160413/829a23bb/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4916 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160413/829a23bb/attachment.bin>

From dave.demarle at kitware.com  Wed Apr 13 17:15:41 2016
From: dave.demarle at kitware.com (David E DeMarle)
Date: Wed, 13 Apr 2016 17:15:41 -0400
Subject: [Paraview] Background in 3D mode
In-Reply-To: <57068125.7020203@uvsq.fr>
References: <56EADA83.6050104@uvsq.fr> <56FE2BEC.2030702@uvsq.fr>
 <CACJ=gTjTvHLnGvd7w3LVY4zPufCauj_ZDKv1-aZSRr=qJfC3wA@mail.gmail.com>
 <CANjZAi9xRGmn=PJPfAn_Ne4+S1fhfw3WAY2-FDg13wOP9Jzu4w@mail.gmail.com>
 <56FEAA89.2010102@uvsq.fr>
 <CANjZAi8nnN_pSZcm9d-iJ0pDj_8=b5H0Q1gJVRFQFWkpYbGvyg@mail.gmail.com>
 <CANjZAi9VwZVXvu1-cAAzoEme6-bs7tLHbhj02WdVFfou4h0S9g@mail.gmail.com>
 <57068125.7020203@uvsq.fr>
Message-ID: <CANjZAi9-LydGGh+f6ZCtQSHZyX5WEMJ3yYRr-dZ0=em73vAZMA@mail.gmail.com>

On Thu, Apr 7, 2016 at 11:47 AM, Cindy Castro <cindy.castro at uvsq.fr> wrote:

> In fact :( I already tried tiled display but the backgroup is not
> correctly split. And yes, I am asking for stereoscopic mode and Cristal
> Eyes active stereo.
>
>  Do you know if this feature is going to be supported in a next release of
> ParaView ?
>
>
No firm plans to fix it that I am aware of.


> I did not understand the command "/bin/uname (and xterm -r "uname -a"
> -hold)". Do you mean I have to run
> > mpirun -np 8 -machinefile
> /opt/software/ParaView/PVscripts/server_machinefile.txt
> /opt/software/ParaView/ParaView-5.0.0-bin/bin/pvserver -rc
> --client-host=mire-pc /opt/software/ParaView/PVresources/wall_config.pvx
> /bin/uname ???
>
>
Nope, don't mix that into the pvserver invocation.

I was suggesting a way that you could debug tile mode. Since you said the
displays were not well ordered what you need to do is ensure that the
machines start up in the right order.


> Regards,
>
> Cindy
>
>
> Le 01/04/2016 20:03, David E DeMarle a ?crit :
>
> And of course I just now realized that you are asking for 3D ie
> stereoscopic mode and remembered that tiled display does not (yet) support
> Crystal Eyes active stereo.
>
> apologies
>
>
> David E DeMarle
> Kitware, Inc.
> R&D Engineer
> 21 Corporate Drive
> Clifton Park, NY 12065-8662
> Phone: 518-881-4909
>
> On Fri, Apr 1, 2016 at 1:45 PM, David E DeMarle <dave.demarle at kitware.com>
> wrote:
>
>> Aiming for this right?
>> -------------------
>> |1-1|1-2|2-1|2-2|
>> -------------------
>> |3-1|3-2|4-1|4-2|
>> -------------------
>>
>>
>> -tdx=3 -tdy=2
>> machinefile.txt that you pass to mpi should be (syntax depends on your
>> mpi)
>> node1
>> node1
>> node2
>> node2
>> node3
>> node3
>> node4
>> node4
>> The point being that you want them to start up in the same order that you
>> have in your pvx file. Use > mpirun ... /bin/uname (and xterm -r "uname -a"
>> -hold) to work out the details.
>>
>> Lastly you don't need the LowerLeft, LowerRight and UpperRight for tile
>> mode, but it will be useful for stereoscopic display so keep it handy.
>>
>>
>>
>>
>>
>> David E DeMarle
>> Kitware, Inc.
>> R&D Engineer
>> 21 Corporate Drive
>> Clifton Park, NY 12065-8662
>> Phone: 518-881-4909
>>
>> On Fri, Apr 1, 2016 at 1:06 PM, Cindy Castro < <cindy.castro at uvsq.fr>
>> cindy.castro at uvsq.fr> wrote:
>>
>>> H Joachim and David,
>>>
>>> Thank you for answering. I tried to apply an Image AND Gradient
>>> background and it was not correctly split over the different screens. I
>>> think it is cave mode actually. I have tested tile mode but the display is
>>> not well ordered. I tried to correct it with mpirun (-tdx=2, -tdy=4) but I
>>> may have missed something in the command line.
>>>
>>> Here is my pvx file :
>>>
>>> <?xml version="1.0" ?>
>>> <pvx>
>>>  <Process Type="client" />
>>>  <Process Type="server">
>>>  <EyeSeparation Value="0.060"/>
>>>   <Machine Name="node1-1"
>>>            Environment="DISPLAY=:0.0"
>>>            FullScreen="0"
>>>            ShowBorders="0"
>>>            Geometry="1920x1080+0+0"
>>>            LowerLeft=" -2.593 0.992 -2.593"
>>>            LowerRight="-1.497 0.993 -3.689"
>>>            UpperRight="-1.497 1.865 -3.689" />
>>>   <Machine Name="node1-2"
>>>            Environment="DISPLAY=:0.0"
>>>            FullScreen="0"
>>>            ShowBorders="0"
>>>            Geometry="1920x1080+1920+0"
>>>            LowerLeft=" -1.497 0.993 -3.689"
>>>            LowerRight=" 0.000 0.997 -4.090"
>>>            UpperRight=" 0.000 1.869 -4.090" />
>>>   <Machine Name="node2-1"
>>>            Environment="DISPLAY=:0.0"
>>>            FullScreen="0"
>>>            ShowBorders="0"
>>>            Geometry="1920x1080+0+0"
>>>            LowerLeft="  0.000 0.997 -4.090"
>>>            LowerRight=" 1.497 1.007 -3.689"
>>>            UpperRight=" 1.497 1.879 -3.689"/>
>>>   <Machine Name="node2-2"
>>>            Environment="DISPLAY=:0.0"
>>>            FullScreen="0"
>>>            ShowBorders="0"
>>>            Geometry="1920x1080+1920+0"
>>>        LowerLeft="  1.497 1.007 -3.689"
>>>            LowerRight=" 2.593 0.997 -2.593"
>>>            UpperRight=" 2.593 1.869 -2.593"/>
>>>   <Machine Name="node3-1"
>>>            Environment="DISPLAY=:0.0"
>>>            FullScreen="0"
>>>            ShowBorders="0"
>>>            Geometry="1920x1080+0+0"
>>>            LowerLeft=" -2.593 0.120 -2.593"
>>>            LowerRight="-1.497 0.121 -3.689"
>>>            UpperRight="-1.497 0.993 -3.689" />
>>>   <Machine Name="node3-2"
>>>            Environment="DISPLAY=:0.0"
>>>            FullScreen="0"
>>>            ShowBorders="0"
>>>            Geometry="1920x1080+1920+0"
>>>            LowerLeft=" -1.497 0.121 -3.689"
>>>            LowerRight=" 0.000 0.125 -4.090"
>>>            UpperRight=" 0.000 0.997 -4.090" />
>>>   <Machine Name="node4-1"
>>>            Environment="DISPLAY=:0.0"
>>>            FullScreen="0"
>>>            ShowBorders="0"
>>>            Geometry="1920x1080+0+0"
>>>            LowerLeft="  0.000 0.125 -4.090"
>>>            LowerRight=" 1.497 0.135 -3.689"
>>>            UpperRight=" 1.497 1.007 -3.689"/>
>>>   <Machine Name="node4-2"
>>>            Environment="DISPLAY=:0.0"
>>>            FullScreen="0"
>>>            ShowBorders="0"
>>>            Geometry="1920x1080+1920+0"
>>>            LowerLeft="  1.497 0.135 -3.689"
>>>            LowerRight=" 2.593 0.125 -2.593"
>>>            UpperRight=" 2.593 0.997 -2.593"/>
>>>   </Process>
>>>
>>> </pvx>
>>>
>>> Regards,
>>>
>>> Cindy
>>>
>>>
>>> Le 01/04/2016 17:55, David E DeMarle a ?crit :
>>>
>>> Cindy,
>>>
>>> I can't remember which mode, tile or cave, doesn't support tile and
>>> gradient background. But from what you and Joachim say it must be cave.
>>>
>>> You should aim for tile mode then. You can enforce and thus correct the
>>> ordering problem you see  with tile mode with your mpirun command and the
>>> your cave.pvx file. Can you share your
>>> /opt/software/ParaView/PVresources/wall_config.pvx? So I can suggest a fix?
>>>
>>> thanks
>>>
>>>
>>> David E DeMarle
>>> Kitware, Inc.
>>> R&D Engineer
>>> 21 Corporate Drive
>>> Clifton Park, NY 12065-8662
>>> Phone: 518-881-4909
>>>
>>> On Fri, Apr 1, 2016 at 11:10 AM, Joachim Pouderoux <
>>> <joachim.pouderoux at kitware.com>joachim.pouderoux at kitware.com> wrote:
>>>
>>>> Hi Cindy,
>>>>
>>>> Not totally sure to understand - are you trying to apply an Image or
>>>> Gradient background and would like it to be correctly split over the
>>>> different screen? If so, I am afraid this feature is not supported.
>>>>
>>>> Best,
>>>> Joachim
>>>>
>>>> *Joachim Pouderoux*
>>>>
>>>> *PhD, Technical Expert*
>>>> *Kitware SAS <http://www.kitware.fr>*
>>>>
>>>>
>>>> 2016-04-01 10:06 GMT+02:00 Cindy Castro < <cindy.castro at uvsq.fr>
>>>> cindy.castro at uvsq.fr>:
>>>>
>>>>> Hello,
>>>>>
>>>>> I am using ParaView in client/server mode with stereo. I have a
>>>>> cluster with 4 nodes, 1 GPU each (NVIDIA K5000) and 8 screens for display.
>>>>>
>>>>> My problem is I can not find how to span a background over my 8
>>>>> screens. The background is displayed on each screen. 3D models are well
>>>>> displayed in 3D (no problem with that).
>>>>>
>>>>> The server is run with the command:
>>>>> mpirun -np 8 -machinefile
>>>>> /opt/software/ParaView/PVscripts/server_machinefile.txt
>>>>> /opt/software/ParaView/ParaView-5.0.0-bin/bin/pvserver -rc
>>>>> --client-host=mire-pc /opt/software/ParaView/PVresources/wall_config.pvx
>>>>>
>>>>> I tried tiles mode but the display is not in the right order...
>>>>>
>>>>> Can you help me ? Is it possible to span a background over several
>>>>> screens in 3D mode ? I is really useful when rendering.
>>>>>
>>>>> Regards,
>>>>>
>>>>> --
>>>>> Cindy CASTRO
>>>>> Responsable plateforme DIGISCOPE-MIRE
>>>>> Plateforme d'Int?gration et de Tests (PIT)
>>>>> --
>>>>> Observatoire de Versailles Saint-Quentin-en-Yvelines (OVSQ)
>>>>> Quartier des Garennes
>>>>> 11 Boulevard d'Alembert
>>>>> 78280 Guyancourt
>>>>> --
>>>>> B?timent principal - RDC - Bureau 215
>>>>> T?l : +33 (0)1 80 28 51 03 <%2B33%20%280%291%2080%2028%2051%2003>
>>>>> Salle MIRE : +33 (0)1 80 28 54 93
>>>>> <%2B33%20%280%291%2080%2028%2054%2093>
>>>>>
>>>>>
>>>>> ---
>>>>> L'absence de virus dans ce courrier ?lectronique a ?t? v?rifi?e par le
>>>>> logiciel antivirus Avast.
>>>>> https://www.avast.com/antivirus
>>>>>
>>>>> _______________________________________________
>>>>> Powered by <http://www.kitware.com>www.kitware.com
>>>>>
>>>>> Visit other Kitware open-source projects at
>>>>> <http://www.kitware.com/opensource/opensource.html>
>>>>> http://www.kitware.com/opensource/opensource.html
>>>>>
>>>>> Please keep messages on-topic and check the ParaView Wiki at:
>>>>> <http://paraview.org/Wiki/ParaView>http://paraview.org/Wiki/ParaView
>>>>>
>>>>> Search the list archives at: <http://markmail.org/search/?q=ParaView>
>>>>> http://markmail.org/search/?q=ParaView
>>>>>
>>>>> Follow this link to subscribe/unsubscribe:
>>>>> http://public.kitware.com/mailman/listinfo/paraview
>>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> Powered by <http://www.kitware.com>www.kitware.com
>>>>
>>>> Visit other Kitware open-source projects at
>>>> <http://www.kitware.com/opensource/opensource.html>
>>>> http://www.kitware.com/opensource/opensource.html
>>>>
>>>> Please keep messages on-topic and check the ParaView Wiki at:
>>>> <http://paraview.org/Wiki/ParaView>http://paraview.org/Wiki/ParaView
>>>>
>>>> Search the list archives at: <http://markmail.org/search/?q=ParaView>
>>>> http://markmail.org/search/?q=ParaView
>>>>
>>>> Follow this link to subscribe/unsubscribe:
>>>> http://public.kitware.com/mailman/listinfo/paraview
>>>>
>>>>
>>>
>>> --
>>> Cindy CASTRO
>>> Responsable plateforme DIGISCOPE-MIRE
>>> Plateforme d'Int?gration et de Tests (PIT)
>>> --
>>> Observatoire de Versailles Saint-Quentin-en-Yvelines (OVSQ)
>>> Quartier des Garennes
>>> 11 Boulevard d'Alembert
>>> 78280 Guyancourt
>>> --
>>> B?timent principal - RDC - Bureau 215
>>> T?l : +33 (0)1 80 28 51 03
>>> Salle MIRE : +33 (0)1 80 28 54 93
>>>
>>>
>>> Cet e-mail a ?t? envoy? depuis un ordinateur prot?g? par Avast.
>>> www.avast.com
>>> <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>
>>>
>>
>>
>
> --
> Cindy CASTRO
> Responsable plateforme DIGISCOPE-MIRE
> Plateforme d'Int?gration et de Tests (PIT)
> --
> Observatoire de Versailles Saint-Quentin-en-Yvelines (OVSQ)
> Quartier des Garennes
> 11 Boulevard d'Alembert
> 78280 Guyancourt
> --
> B?timent principal - RDC - Bureau 215
> T?l : +33 (0)1 80 28 51 03
> Salle MIRE : +33 (0)1 80 28 54 93
>
>
>
> <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient> Garanti
> sans virus. www.avast.com
> <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160413/8d2dd8c2/attachment.html>

From wascott at sandia.gov  Wed Apr 13 19:29:13 2016
From: wascott at sandia.gov (Scott, W Alan)
Date: Wed, 13 Apr 2016 23:29:13 +0000
Subject: [Paraview] [EXTERNAL] Re:  [EXT] Re: v5.0.1 & RealVNC
In-Reply-To: <CADHSJjBcnC8qydQ_Z++FzvXOp6FKPzm6fg1UhCGSGa42=a324g@mail.gmail.com>
References: <CY1PR07MB2506A851C555D9491B6D73279F950@CY1PR07MB2506.namprd07.prod.outlook.com>
 <CAOXZzG6iyK=Vm21eBJRMoipvN7Hs7gDPUw0bA8iPRHKtM=a9og@mail.gmail.com>
 <CY1PR07MB250638B049611478865878C59F960@CY1PR07MB2506.namprd07.prod.outlook.com>
 <CAOXZzG6BcGvWOxAc_UZdDMHWPicTFqYdt+g9iJj=7LM0tPbVgQ@mail.gmail.com>
 <CY1PR07MB25062AA439DD5903F9C65F3A9F960@CY1PR07MB2506.namprd07.prod.outlook.com>
 <CADHSJjBcnC8qydQ_Z++FzvXOp6FKPzm6fg1UhCGSGa42=a324g@mail.gmail.com>
Message-ID: <aee634acda5c49f2985c5a73a7b8a7bd@ES01AMSNLNT.srn.sandia.gov>

I just tried, and have the following error:

./paraview --mesa-llvm
.../lib/paraview-5.0/paraview: error while loading shared libraries: libatomic.so.1: cannot open shared object file: No such file or directory

Ideas?

Thanks,

Alan


-----Original Message-----
From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Utkarsh Ayachit
Sent: Wednesday, April 13, 2016 12:20 PM
To: Dennis Conklin <dennis_conklin at goodyear.com>
Cc: ParaView Mailing List <paraview at paraview.org>
Subject: [EXTERNAL] Re: [Paraview] [EXT] Re: v5.0.1 & RealVNC

Dennis,

Don't mean to distract this conversation -- I'll let Chuck follow  up on the VNC thing -- but a a small sidetrack:

Can you trying running paraview as:

> paraview --mesa-llvm

Does that work?

Utkarsh

On Wed, Apr 13, 2016 at 12:12 PM, Dennis Conklin <dennis_conklin at goodyear.com> wrote:
> Chuck,
>
>
>
> This is what I get ? none of this means anything to me!
>
>
>
> Dennis
>
>
>
>
>
> Xlib:  extension "NV-GLX" missing on display "alnx031:15.0".
>
> OpenGL vendor string: Mesa project: www.mesa3d.org
>
> OpenGL renderer string: Mesa GLX Indirect
>
> OpenGL version string: 1.2 (1.5 Mesa 6.4.1)
>
> OpenGL extensions:
>
>
>
> From: Chuck Atkins [mailto:chuck.atkins at kitware.com]
> Sent: Wednesday, April 13, 2016 11:56 AM
> To: Dennis Conklin <dennis_conklin at goodyear.com>
> Cc: ParaView Mailing List <paraview at paraview.org>
> Subject: Re: [EXT] Re: [Paraview] v5.0.1 & RealVNC
>
>
>
> Hi Dennis,
>
> I suspect the GPU is not getting used by the VNC server and thus 
> falling back to a software OpenGL implementation with older mesa and 
> not a new enough OpenGL support.  Different VNC servers on Linux have 
> different capabilities, with some able to reach their underlying GPU and some not.
> From your VNC session, can you open up a terminal and run: glxinfo | 
> grep '^OpenGL' ?  That should be more telling.
>
>
> - Chuck
>
>
>
> On Wed, Apr 13, 2016 at 9:58 AM, Dennis Conklin 
> <dennis_conklin at goodyear.com> wrote:
>
> Chuck,
>
>
>
> Sorry, got additional details from the sysops.
>
>
>
> We have GPUs in our workstations ? he was referring that we don?t have GPU
> clusters for computation.    I understand that the VNC server is running on
> the workstation that I attach to, and yes, we are using the GPU on 
> that workstation to render.
>
>
>
> FYI,  the workstations have Nvidia K4000 cards and we are running 
> realVNC ? any chance this is part of your test suite?
>
>
>
> Thanks again, sorry for the confusion, but I am NOT a Linux or VNC guru!!
>
>
>
> Dennis
>
>
>
> From: Chuck Atkins [mailto:chuck.atkins at kitware.com]
> Sent: Tuesday, April 12, 2016 6:05 PM
> To: Dennis Conklin <dennis_conklin at goodyear.com>
> Cc: ParaView Mailing List <paraview at paraview.org>
> Subject: [EXT] Re: [Paraview] v5.0.1 & RealVNC
>
>
>
> Sorry, forgot to cc the list.
>
> Hi Dennis, a few questions:
>
> Are you using the binaries from paraview.org or did you build it yourself?
> Does the machine with the vnc server have a GPU you're trying use?
> You said previous versions of paraview worked.  Does that include 5.0 
> and 4.x or just 4.x?
>
> On Apr 12, 2016 4:04 PM, "Dennis Conklin" 
> <dennis_conklin at goodyear.com>
> wrote:
>
> All,
>
>
>
> So I started testing Paraview v5.0.1 Linux and it doesn?t work with 
> RealVNC v4, or v5.1.1 or v5.3 (dies with Segmentation fault without even displaying
> a screen).   Earlier versions of Paraview work but not 5.0.1.  I am not very
> familiar with VNC.   Are there graphics or other options in VNC that need to
> be tuned that I could refer to my sysops?
>
>
>
> Thanks for any hints.
>
>
>
> Dennis
>
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at 
> http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview
>
>
>
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at 
> http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview
>
_______________________________________________
Powered by www.kitware.com

Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView

Search the list archives at: http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview

From padamsen at grundfos.com  Thu Apr 14 01:45:21 2016
From: padamsen at grundfos.com (Per Adamsen)
Date: Thu, 14 Apr 2016 05:45:21 +0000
Subject: [Paraview] Specifying camera movement using points from a file
In-Reply-To: <CAB5Fpx7RmTTV=8RtgWS5Ryfihm0-6e3=QRD71X0QHtQbxDcPLw@mail.gmail.com>
References: <AM4PR03MB1457B8D640B86CF4CB158BADA4960@AM4PR03MB1457.eurprd03.prod.outlook.com>
 <CAB5Fpx7RmTTV=8RtgWS5Ryfihm0-6e3=QRD71X0QHtQbxDcPLw@mail.gmail.com>
Message-ID: <AM4PR03MB1457F775D7FA628601E49EEAA4970@AM4PR03MB1457.eurprd03.prod.outlook.com>

Hi Cory,

Thanks for your feedback.

Of course this can be handled with a Python script - sometimes the answer is so obvious ;-)

I will follow your advice and let you know if I encounter any problems.

Regards,
Per

-----Original Message-----
From: Cory Quammen [mailto:cory.quammen at kitware.com] 
Sent: 13. april 2016 16:03
To: Per Adamsen <padamsen at grundfos.com>
Cc: paraview at paraview.org
Subject: Re: [Paraview] Specifying camera movement using points from a file

Per,

You can do this with Python scripting in the Python console.

# get active view
renderView1 = GetActiveViewOrCreate('RenderView')

# uncomment following to set a specific view size # renderView1.ViewSize = [689, 340]

# get camera animation track for the view
cameraAnimationCue1 = GetCameraTrack(view=renderView1)

# create keyframes for this animation track # create a key frame
keyFrame4737 = CameraKeyFrame()
keyFrame4737.Position = [0.0, 0.0, 6.69] keyFrame4737.ParallelScale = 1.73

keyFrame4737.PositionPathPoints = [0.0, 0.0, 5.0, 2.938926261462365, 0.0, 4.045084971874736, 4.755282581475766, 0.0, 1.545084971874737, 4.755282581475766, 0.0, -1.5450849718747361, 2.938926261462365, 0.0, -4.045084971874735, 1.3322676295501878e-15, 0.0, -4.9999999999999964, -2.9389262614623624, 0.0, -4.045084971874735, -4.755282581475763, 0.0, -1.5450849718747368, -4.755282581475763, 0.0, 1.5450849718747341, -2.9389262614623632, 0.0, 4.045084971874731]

keyFrame4737.FocalPathPoints = [0.0, 0.0, 0.0] keyFrame4737.ClosedPositionPath = 1

# create a key frame
keyFrame4738 = CameraKeyFrame()
keyFrame4738.KeyTime = 1.0
keyFrame4738.Position = [0.0, 0.0, 6.69] keyFrame4738.ParallelScale = 1.73

# initialize the animation track
cameraAnimationCue1.Mode = 'Path-based'
cameraAnimationCue1.KeyFrames = [keyFrame4737, keyFrame4738]

# get animation scene
animationScene1 = GetAnimationScene()

animationScene1.Play()

Just modify the keyFrame4737.PositionPathPoints. They are ordered [x, y, z, x, y, z ...].

HTH,
Cory


On Wed, Apr 13, 2016 at 7:38 AM, Per Adamsen <padamsen at grundfos.com> wrote:
> Hi,
>
>
>
> I have been playing with the camera animations in PV5.0 and was 
> wondering if there was an easier way to specify the camera path than 
> manually adding and dragging points.
>
>
>
> Is it possible to copy paste camera coordinates from a file to obtain 
> e.g. a helical path?
>
>
>
> Thank you in advance.
>
>
>
> Regards,
>
> Per
>
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at 
> http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview
>



--
Cory Quammen
R&D Engineer
Kitware, Inc.

From u.utku.turuncoglu at be.itu.edu.tr  Thu Apr 14 04:05:30 2016
From: u.utku.turuncoglu at be.itu.edu.tr (Ufuk Utku Turuncoglu (BE))
Date: Thu, 14 Apr 2016 11:05:30 +0300
Subject: [Paraview] couple of issues related with co-processing ...
In-Reply-To: <CAMaOp+EOZ_cXDB4H9haAzpfMBJuJ5r83Az4Aii7EKBWj=OCH2A@mail.gmail.com>
References: <570E3F20.3000602@be.itu.edu.tr>
 <CAMaOp+EOZ_cXDB4H9haAzpfMBJuJ5r83Az4Aii7EKBWj=OCH2A@mail.gmail.com>
Message-ID: <570F4F4A.3000807@be.itu.edu.tr>

Thanks. I'll look at those scripts to generate similar data to the 
co-processing.  By the way, i had a problem in the calculator filter and 
it was not working in co-processing but again it might be related with 
the data representation. I'll try it again when i create the multiblock 
dataset.

Regards,

--ufuk

On 13/04/16 16:24, Andy Bauer wrote:
> Hi Ufuk,
>
> I would suggest testing out some of the Catalyst examples which are in 
> the source code under the Examples/Catalyst subdirectory. I would also 
> suggest creating Catalyst scripts from data sets generated through 
> Catalyst output instead of the NetCDF files. There are two example 
> scripts for this in Examples/Catalyst/SampleScripts that you can use 
> for this.
>
> As for the grid names for the axes, this may be a bug in ParaView. 
> I'll look into that.
>
> Best,
> Andy
>
> On Wed, Apr 13, 2016 at 8:44 AM, Ufuk Utku Turuncoglu (BE) 
> <u.utku.turuncoglu at be.itu.edu.tr 
> <mailto:u.utku.turuncoglu at be.itu.edu.tr>> wrote:
>
>     Hi,
>
>     I am using co-processing (Catalyst) and i have couple of issues
>     about the behavior of the co-processing module.
>
>     1 - If i send multiple 2d variable or single 3d variable to the
>     co-processor, my custom code is working without any problem and
>     produces desired output. On the other hand, the code hangs with
>     multiple 3d variable (it basically opens a square white window and
>     waits, see the attached screenshot). I have no idea about the
>     problem because the terminal does not produces any output. I could
>     install the ParaView in debug mode and it might help?
>
>     2 - The axis names (edited by Edit Axes Grid section in Properties
>     window) are not written to the produced png file when the
>     visualization pipeline is driven by co-processing but it looks
>     fine under ParaView.
>
>     3 - When i trying to use volume rendering (single 3d field) along
>     with co-processing, the code gives following error
>
>     ERROR: In
>     /opt/progs/paraview-5.0.0/src/VTK/Common/ExecutionModel/vtkCompositeDataPipeline.cxx,
>     line 171
>     vtkPVDataRepresentationPipeline (0x7fea05244010): Can not execute
>     simple alorithm without output ports
>     ...
>     ...
>     ERROR: In
>     /opt/progs/paraview-5.0.0/src/VTK/Filters/Parallel/vtkPKdTree.cxx,
>     line 296
>     vtkPKdTree (0x7fea04f42840): (process 0) NumberOfDatasets = 0,
>     cannot determine volume bounds.
>
>     I could produce iso-surface with same code without any problem.
>     The volume rendering is also working under ParaView.
>
>     The last question might be related with the grid definition in the
>     co-processing because i am using single netcdf dataset to create
>     visualization scripts (python) under ParaView but in the model
>     code (co-processing) the dataset is defined as MultiBlockDataSet
>     due to the parallel nature of the simulation code.
>
>     Regards,
>
>     --ufuk
>
>     _______________________________________________
>     Powered by www.kitware.com <http://www.kitware.com>
>
>     Visit other Kitware open-source projects at
>     http://www.kitware.com/opensource/opensource.html
>
>     Please keep messages on-topic and check the ParaView Wiki at:
>     http://paraview.org/Wiki/ParaView
>
>     Search the list archives at: http://markmail.org/search/?q=ParaView
>
>     Follow this link to subscribe/unsubscribe:
>     http://public.kitware.com/mailman/listinfo/paraview
>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160414/fe553585/attachment.html>

From dennis_conklin at goodyear.com  Thu Apr 14 07:53:32 2016
From: dennis_conklin at goodyear.com (Dennis Conklin)
Date: Thu, 14 Apr 2016 11:53:32 +0000
Subject: [Paraview] [EXT] Re: v5.0.1 & RealVNC
In-Reply-To: <CAOXZzG5XsjYdHnD3dgJYue42G0gd9AgBTsmwe5NJP1cup=JxDA@mail.gmail.com>
References: <CY1PR07MB2506A851C555D9491B6D73279F950@CY1PR07MB2506.namprd07.prod.outlook.com>
 <CAOXZzG6iyK=Vm21eBJRMoipvN7Hs7gDPUw0bA8iPRHKtM=a9og@mail.gmail.com>
 <CY1PR07MB250638B049611478865878C59F960@CY1PR07MB2506.namprd07.prod.outlook.com>
 <CAOXZzG6BcGvWOxAc_UZdDMHWPicTFqYdt+g9iJj=7LM0tPbVgQ@mail.gmail.com>
 <CY1PR07MB25062AA439DD5903F9C65F3A9F960@CY1PR07MB2506.namprd07.prod.outlook.com>
 <CADHSJjBcnC8qydQ_Z++FzvXOp6FKPzm6fg1UhCGSGa42=a324g@mail.gmail.com>
 <CAOXZzG5XsjYdHnD3dgJYue42G0gd9AgBTsmwe5NJP1cup=JxDA@mail.gmail.com>
Message-ID: <CY1PR07MB250662408C1E7589756611999F970@CY1PR07MB2506.namprd07.prod.outlook.com>

Chuck & Utkarsh,

Well, this is good news, at least we know what is going on.

I tried paraview ?mesa-llvm  and got error that libatomic.so.1 is missing

So, what is the minimum required version of OpenGL required for Paraview5?

At this point, since we have a support contract with realVNC, we will go back to them with your 2 options, but specifying what version of OpenGL is required and then see what they can do.

Thanks very much,  I believe with this 1 additional fact we can chart a path forward with realVNC.

As far as the distro ? we are on SUSE, but are migrating to RedHat very soon.

Dennis

From: Chuck Atkins [mailto:chuck.atkins at kitware.com]
Sent: Wednesday, April 13, 2016 2:38 PM
To: Utkarsh Ayachit <utkarsh.ayachit at kitware.com>
Cc: Dennis Conklin <dennis_conklin at goodyear.com>; ParaView Mailing List <paraview at paraview.org>
Subject: Re: [Paraview] [EXT] Re: v5.0.1 & RealVNC

Hi Dennis,

Xlib:  extension "NV-GLX" missing on display "alnx031:15.0".
OpenGL vendor string: Mesa project: www.mesa3d.org<http://www.mesa3d.org>
OpenGL renderer string: Mesa GLX Indirect
OpenGL version string: 1.2 (1.5 Mesa 6.4.1)
OpenGL extensions:

As I suspected, this is telling us is that the VNC server does not have access to the GPU on the machine it's running on and is falling back to the Mesa software driver, which does not support the version of OpenGL that ParaView requires.  Older versions of ParaView (4.x) used a much older OpenGL stack while the newer 5.x releases have a completely overhauled rendering backend but it requires support for newer OpenGL versions. So, even though older ParaView versions worked, they still were not able to use the GPU and likely had fairly poor performance.  Given that, there are 2 options:

  *   Ideal:

     *   See if your sysadmins can "fix" or configure the VNC server on the workstation to work with the GPU.

  *   Workable:

     *   Run ParaView using a newer version of Mesa.

        *   You can probably use the binaries packaged with Paraview as Utkarsh mentioned by adding --mesa-llvm.
        *   If this doesn't work, the mesa binaries we ship with ParaView are probably incompatible with the Linux distro the server runs.  Which distro does the server run?  We may have a new version already built that you can try to use.
        *   Not ideal since it's still using software rendering but better than nothing if your admins can't get the VNC server working with the GPU.
- Chuck

- Chuck

On Wed, Apr 13, 2016 at 2:19 PM, Utkarsh Ayachit <utkarsh.ayachit at kitware.com<mailto:utkarsh.ayachit at kitware.com>> wrote:
Dennis,

Don't mean to distract this conversation -- I'll let Chuck follow  up
on the VNC thing -- but a a small sidetrack:

Can you trying running paraview as:

> paraview --mesa-llvm

Does that work?

Utkarsh

On Wed, Apr 13, 2016 at 12:12 PM, Dennis Conklin
<dennis_conklin at goodyear.com<mailto:dennis_conklin at goodyear.com>> wrote:
> Chuck,
>
>
>
> This is what I get ? none of this means anything to me!
>
>
>
> Dennis
>
>
>
>
>
> Xlib:  extension "NV-GLX" missing on display "alnx031:15.0".
>
> OpenGL vendor string: Mesa project: www.mesa3d.org<http://www.mesa3d.org>
>
> OpenGL renderer string: Mesa GLX Indirect
>
> OpenGL version string: 1.2 (1.5 Mesa 6.4.1)
>
> OpenGL extensions:
>
>
>
> From: Chuck Atkins [mailto:chuck.atkins at kitware.com<mailto:chuck.atkins at kitware.com>]
> Sent: Wednesday, April 13, 2016 11:56 AM
> To: Dennis Conklin <dennis_conklin at goodyear.com<mailto:dennis_conklin at goodyear.com>>
> Cc: ParaView Mailing List <paraview at paraview.org<mailto:paraview at paraview.org>>
> Subject: Re: [EXT] Re: [Paraview] v5.0.1 & RealVNC
>
>
>
> Hi Dennis,
>
> I suspect the GPU is not getting used by the VNC server and thus falling
> back to a software OpenGL implementation with older mesa and not a new
> enough OpenGL support.  Different VNC servers on Linux have different
> capabilities, with some able to reach their underlying GPU and some not.
> From your VNC session, can you open up a terminal and run: glxinfo | grep
> '^OpenGL' ?  That should be more telling.
>
>
> - Chuck
>
>
>
> On Wed, Apr 13, 2016 at 9:58 AM, Dennis Conklin
> <dennis_conklin at goodyear.com<mailto:dennis_conklin at goodyear.com>> wrote:
>
> Chuck,
>
>
>
> Sorry, got additional details from the sysops.
>
>
>
> We have GPUs in our workstations ? he was referring that we don?t have GPU
> clusters for computation.    I understand that the VNC server is running on
> the workstation that I attach to, and yes, we are using the GPU on that
> workstation to render.
>
>
>
> FYI,  the workstations have Nvidia K4000 cards and we are running realVNC ?
> any chance this is part of your test suite?
>
>
>
> Thanks again, sorry for the confusion, but I am NOT a Linux or VNC guru!!
>
>
>
> Dennis
>
>
>
> From: Chuck Atkins [mailto:chuck.atkins at kitware.com<mailto:chuck.atkins at kitware.com>]
> Sent: Tuesday, April 12, 2016 6:05 PM
> To: Dennis Conklin <dennis_conklin at goodyear.com<mailto:dennis_conklin at goodyear.com>>
> Cc: ParaView Mailing List <paraview at paraview.org<mailto:paraview at paraview.org>>
> Subject: [EXT] Re: [Paraview] v5.0.1 & RealVNC
>
>
>
> Sorry, forgot to cc the list.
>
> Hi Dennis, a few questions:
>
> Are you using the binaries from paraview.org<http://paraview.org> or did you build it yourself?
> Does the machine with the vnc server have a GPU you're trying use?
> You said previous versions of paraview worked.  Does that include 5.0 and
> 4.x or just 4.x?
>
> On Apr 12, 2016 4:04 PM, "Dennis Conklin" <dennis_conklin at goodyear.com<mailto:dennis_conklin at goodyear.com>>
> wrote:
>
> All,
>
>
>
> So I started testing Paraview v5.0.1 Linux and it doesn?t work with RealVNC
> v4, or v5.1.1 or v5.3 (dies with Segmentation fault without even displaying
> a screen).   Earlier versions of Paraview work but not 5.0.1.  I am not very
> familiar with VNC.   Are there graphics or other options in VNC that need to
> be tuned that I could refer to my sysops?
>
>
>
> Thanks for any hints.
>
>
>
> Dennis
>
>
> _______________________________________________
> Powered by www.kitware.com<http://www.kitware.com>
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview
>
>
>
>
> _______________________________________________
> Powered by www.kitware.com<http://www.kitware.com>
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160414/1d4890f7/attachment.html>

From utkarsh.ayachit at kitware.com  Thu Apr 14 10:55:05 2016
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Thu, 14 Apr 2016 10:55:05 -0400
Subject: [Paraview] [EXTERNAL] Re:  [EXT] Re: v5.0.1 & RealVNC
In-Reply-To: <aee634acda5c49f2985c5a73a7b8a7bd@ES01AMSNLNT.srn.sandia.gov>
References: <CY1PR07MB2506A851C555D9491B6D73279F950@CY1PR07MB2506.namprd07.prod.outlook.com>
 <CAOXZzG6iyK=Vm21eBJRMoipvN7Hs7gDPUw0bA8iPRHKtM=a9og@mail.gmail.com>
 <CY1PR07MB250638B049611478865878C59F960@CY1PR07MB2506.namprd07.prod.outlook.com>
 <CAOXZzG6BcGvWOxAc_UZdDMHWPicTFqYdt+g9iJj=7LM0tPbVgQ@mail.gmail.com>
 <CY1PR07MB25062AA439DD5903F9C65F3A9F960@CY1PR07MB2506.namprd07.prod.outlook.com>
 <CADHSJjBcnC8qydQ_Z++FzvXOp6FKPzm6fg1UhCGSGa42=a324g@mail.gmail.com>
 <aee634acda5c49f2985c5a73a7b8a7bd@ES01AMSNLNT.srn.sandia.gov>
Message-ID: <CADHSJjBYkCzqj78-d_SPo1=k_xa3Vrc__0uqoxk7Cp=B1tFMaw@mail.gmail.com>

Alan,


> ./paraview --mesa-llvm
> .../lib/paraview-5.0/paraview: error while loading shared libraries: libatomic.so.1: cannot open shared object file: No such file or directory

Can you try this binary:
http://www.paraview.org/files/v5.0/ParaView-5.0.1-Qt4-OpenGL2-MPI-Linux-64bit-experimental.tar.gz

If it works, then I can update the official binaries.

Utkarsh

From dennis_conklin at goodyear.com  Thu Apr 14 14:20:21 2016
From: dennis_conklin at goodyear.com (Dennis Conklin)
Date: Thu, 14 Apr 2016 18:20:21 +0000
Subject: [Paraview] [EXTERNAL] Re:  [EXT] Re: v5.0.1 & RealVNC
In-Reply-To: <CADHSJjBYkCzqj78-d_SPo1=k_xa3Vrc__0uqoxk7Cp=B1tFMaw@mail.gmail.com>
References: <CY1PR07MB2506A851C555D9491B6D73279F950@CY1PR07MB2506.namprd07.prod.outlook.com>
 <CAOXZzG6iyK=Vm21eBJRMoipvN7Hs7gDPUw0bA8iPRHKtM=a9og@mail.gmail.com>
 <CY1PR07MB250638B049611478865878C59F960@CY1PR07MB2506.namprd07.prod.outlook.com>
 <CAOXZzG6BcGvWOxAc_UZdDMHWPicTFqYdt+g9iJj=7LM0tPbVgQ@mail.gmail.com>
 <CY1PR07MB25062AA439DD5903F9C65F3A9F960@CY1PR07MB2506.namprd07.prod.outlook.com>
 <CADHSJjBcnC8qydQ_Z++FzvXOp6FKPzm6fg1UhCGSGa42=a324g@mail.gmail.com>
 <aee634acda5c49f2985c5a73a7b8a7bd@ES01AMSNLNT.srn.sandia.gov>
 <CADHSJjBYkCzqj78-d_SPo1=k_xa3Vrc__0uqoxk7Cp=B1tFMaw@mail.gmail.com>
Message-ID: <CY1PR07MB2506EE2DD3E171A798A55ECF9F970@CY1PR07MB2506.namprd07.prod.outlook.com>

Utkarsh,

Tried your new version and got this:

alnx031:bin 203> ./paraview --mesa-llvm
?  /ParaView-5.0.1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.0/paraview: /lib64/libpthread.so.0: version `GLIBC_2.12' not found 
(required by ? ParaView-5.0.1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.0/mesa-llvm/libGL.so.1)

Dennis

-----Original Message-----
From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] 
Sent: Thursday, April 14, 2016 10:55 AM
To: Scott, W Alan <wascott at sandia.gov>
Cc: Dennis Conklin <dennis_conklin at goodyear.com>; ParaView Mailing List <paraview at paraview.org>
Subject: Re: [EXTERNAL] Re: [Paraview] [EXT] Re: v5.0.1 & RealVNC

Alan,


> ./paraview --mesa-llvm
> .../lib/paraview-5.0/paraview: error while loading shared libraries: libatomic.so.1: cannot open shared object file: No such file or directory

Can you try this binary:
http://www.paraview.org/files/v5.0/ParaView-5.0.1-Qt4-OpenGL2-MPI-Linux-64bit-experimental.tar.gz

If it works, then I can update the official binaries.

Utkarsh

From utkarsh.ayachit at kitware.com  Thu Apr 14 14:56:17 2016
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Thu, 14 Apr 2016 14:56:17 -0400
Subject: [Paraview] [EXTERNAL] Re:  [EXT] Re: v5.0.1 & RealVNC
In-Reply-To: <CY1PR07MB2506EE2DD3E171A798A55ECF9F970@CY1PR07MB2506.namprd07.prod.outlook.com>
References: <CY1PR07MB2506A851C555D9491B6D73279F950@CY1PR07MB2506.namprd07.prod.outlook.com>
 <CAOXZzG6iyK=Vm21eBJRMoipvN7Hs7gDPUw0bA8iPRHKtM=a9og@mail.gmail.com>
 <CY1PR07MB250638B049611478865878C59F960@CY1PR07MB2506.namprd07.prod.outlook.com>
 <CAOXZzG6BcGvWOxAc_UZdDMHWPicTFqYdt+g9iJj=7LM0tPbVgQ@mail.gmail.com>
 <CY1PR07MB25062AA439DD5903F9C65F3A9F960@CY1PR07MB2506.namprd07.prod.outlook.com>
 <CADHSJjBcnC8qydQ_Z++FzvXOp6FKPzm6fg1UhCGSGa42=a324g@mail.gmail.com>
 <aee634acda5c49f2985c5a73a7b8a7bd@ES01AMSNLNT.srn.sandia.gov>
 <CADHSJjBYkCzqj78-d_SPo1=k_xa3Vrc__0uqoxk7Cp=B1tFMaw@mail.gmail.com>
 <CY1PR07MB2506EE2DD3E171A798A55ECF9F970@CY1PR07MB2506.namprd07.prod.outlook.com>
Message-ID: <CADHSJjAksBGdaUk=OZLsCzogknm9gg1qtK3q-azg=h6NjnjM=A@mail.gmail.com>

> Tried your new version and got this:
 /lib64/libpthread.so.0: version `GLIBC_2.12' not found
> (required by ? ParaView-5.0.1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.0/mesa-llvm/libGL.so.1)

Your linux version, I'm afraid, is too old for the Mesa binaries we ship.

From dennis_conklin at goodyear.com  Thu Apr 14 15:15:58 2016
From: dennis_conklin at goodyear.com (Dennis Conklin)
Date: Thu, 14 Apr 2016 19:15:58 +0000
Subject: [Paraview] [EXTERNAL] Re:  [EXT] Re: v5.0.1 & RealVNC
In-Reply-To: <CADHSJjAksBGdaUk=OZLsCzogknm9gg1qtK3q-azg=h6NjnjM=A@mail.gmail.com>
References: <CY1PR07MB2506A851C555D9491B6D73279F950@CY1PR07MB2506.namprd07.prod.outlook.com>
 <CAOXZzG6iyK=Vm21eBJRMoipvN7Hs7gDPUw0bA8iPRHKtM=a9og@mail.gmail.com>
 <CY1PR07MB250638B049611478865878C59F960@CY1PR07MB2506.namprd07.prod.outlook.com>
 <CAOXZzG6BcGvWOxAc_UZdDMHWPicTFqYdt+g9iJj=7LM0tPbVgQ@mail.gmail.com>
 <CY1PR07MB25062AA439DD5903F9C65F3A9F960@CY1PR07MB2506.namprd07.prod.outlook.com>
 <CADHSJjBcnC8qydQ_Z++FzvXOp6FKPzm6fg1UhCGSGa42=a324g@mail.gmail.com>
 <aee634acda5c49f2985c5a73a7b8a7bd@ES01AMSNLNT.srn.sandia.gov>
 <CADHSJjBYkCzqj78-d_SPo1=k_xa3Vrc__0uqoxk7Cp=B1tFMaw@mail.gmail.com>
 <CY1PR07MB2506EE2DD3E171A798A55ECF9F970@CY1PR07MB2506.namprd07.prod.outlook.com>
 <CADHSJjAksBGdaUk=OZLsCzogknm9gg1qtK3q-azg=h6NjnjM=A@mail.gmail.com>
Message-ID: <CY1PR07MB2506F418F6F6FE19ACF662089F970@CY1PR07MB2506.namprd07.prod.outlook.com>

Utkarsh,

LOL,  yes, we are old, but if we never update we never have to test for compatibility  ;-)     We are moving to RedHat this quarter, which will hopefully improve the situation.   Our postprocessor benchmark is being delayed until RedHat is in, so we will get Paraview5 up and running by then.

Dennis

-----Original Message-----
From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] 
Sent: Thursday, April 14, 2016 2:56 PM
To: Dennis Conklin <dennis_conklin at goodyear.com>
Cc: Scott, W Alan <wascott at sandia.gov>; ParaView Mailing List <paraview at paraview.org>
Subject: Re: [EXTERNAL] Re: [Paraview] [EXT] Re: v5.0.1 & RealVNC

> Tried your new version and got this:
 /lib64/libpthread.so.0: version `GLIBC_2.12' not found
> (required by ? ParaView-5.0.1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.0/mesa-llvm/libGL.so.1)

Your linux version, I'm afraid, is too old for the Mesa binaries we ship.

From cory.quammen at kitware.com  Thu Apr 14 16:41:47 2016
From: cory.quammen at kitware.com (Cory Quammen)
Date: Thu, 14 Apr 2016 16:41:47 -0400
Subject: [Paraview] ParaView numpy interface question
In-Reply-To: <CAFvyM3RY9WP2iW5t98YFB1Qeg0nzCrBuRwnOwmbtwHzkOsruSQ@mail.gmail.com>
References: <CAFvyM3RY9WP2iW5t98YFB1Qeg0nzCrBuRwnOwmbtwHzkOsruSQ@mail.gmail.com>
Message-ID: <CAB5Fpx4Dz8G9J+S2z9rEAYUuW7Eq2SKGGP5akSZ4+K+WYaEoqA@mail.gmail.com>

Kevin,

You would probably be better off using a Programmable Filter to
perform this operation. It will take two inputs and produce one output
that you can render directly -  no need to write and read and
intermediate file.

HTH,
Cory

On Mon, Apr 4, 2016 at 3:46 PM, Dean, Kevin
<kevin.dean at decisionsciencescorp.com> wrote:
> Hey all,
>
> I have a quick question about setting scalar values with the python macro
> inside paraview.
>
> So I have two images that I want to do scalar manipulation with.
>
> example code:
>
> from paraview import simple
>
> from vtk.util import numpy_support as npvtk
>
>
> import vtk.numpy_interface.dataset_adapter as dsa
> import pandas as pd
>
> import vtk
>
>
> scaling_vti = simple.XMLImageDataReader(FileName=[scaling_filename])
>
> scaling_rawData = simple.servermanager.Fetch(scaling_vti)
>
> scaling_data = dsa.WrapDataObject(scaling_rawData)
>
> scaling_array =
> pd.DataFrame(npvtk.vtk_to_numpy(data.GetPointData().GetScalars()), columns=
> ['scaling_error'])
>
> humans_vti = simple.FindSource(humans_filename)
>
> humans_vti.PointArrayStatus = ['Scattering Density']
> humans_rawData = simple.servermanager.Fetch(humans_vti)
> humans_data = dsa.WrapDataObject(humans_rawData)
> humans_array =
> pd.DataFrame(npvtk.vtk_to_numpy(humans_data.GetPointData().GetScalars()),
> columns=['scalar_intensity'])
>
> new_scalars = pd.DataFrame(humans_array.scalar_intensity *
> scaling_array.scaling_error)
>
> data.GetPointData().SetScalars(npvtk.numpy_to_vtk(new_scalars))
>
>
> After I do this, I can bypass the pipeline (because I haven't figure out how
> to use it yet) by
>
> writing this image to a new file then load it again to render it.
>
> Is there a way I can set the paraview image with the new scalar values and
> have it render without
> having to write it to a file first?
>
> Or, is there a way to convert the
> vtk.numpy_interface.dataset_adapter.DataSetAttributes type back
> to paraview.servermanager.FieldDataInformation?
>
> Thanks,
>
> Kevin E. Dean
>
>
> This email and its contents are confidential. If you are not the intended
> recipient, please do not disclose or use the information within this email
> or its attachments. If you have received this email in error, please report
> the error to the sender by return email and delete this communication from
> your records.
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview
>



-- 
Cory Quammen
R&D Engineer
Kitware, Inc.

From u.utku.turuncoglu at be.itu.edu.tr  Fri Apr 15 05:02:19 2016
From: u.utku.turuncoglu at be.itu.edu.tr (Ufuk Utku Turuncoglu (BE))
Date: Fri, 15 Apr 2016 12:02:19 +0300
Subject: [Paraview] couple of issues related with co-processing ...
In-Reply-To: <CAMaOp+EOZ_cXDB4H9haAzpfMBJuJ5r83Az4Aii7EKBWj=OCH2A@mail.gmail.com>
References: <570E3F20.3000602@be.itu.edu.tr>
 <CAMaOp+EOZ_cXDB4H9haAzpfMBJuJ5r83Az4Aii7EKBWj=OCH2A@mail.gmail.com>
Message-ID: <5710AE1B.2020008@be.itu.edu.tr>

Hi Andy,

As you suggested in your previous mail, i used allinputsgridwriter.py 
script to write all the available fields as multiblock dataset and i 
created co-processing scripts using this dataset. Now, i could handle 
multiple 3d fields but i have still problem in the combination of 
contour and vector visualization. In this case, the code hangs in same 
way that i mentioned in my initial mail.

So, to find the source of the problem i tried different pipelines and 
check the co-processing,

1 - A pipeline with only Glyph filter. In this case, i set Gradients as 
Vectors in Active Attributes section in the properties window. The 
co-processing is working without any problem in this case.

2 - I used Calculator Filter to compute vector using u*iHat+v*jHat 
equation along with Glyph to produce vector field visualization. In this 
case, the pipeline is working without any error under co-processing.

3 - A visualization pipeline with an iso-surface which is colored by 
different variable. It works also.

4 - The combination of step 2 and 3. In this case, i used same 
visualization pipeline with 2 but in this case, i add a Contour filter 
to create an iso-surface for a scalar 3d field (same as step 3). The 
co-processing code hands with white screen and does not produce the output.

So, it seems that the combination of Contour and vector visualization 
affects the co-processing. Anyway, do you have similar experience in 
co-processing?

Regards,

--ufuk

On 13/04/16 16:24, Andy Bauer wrote:
> Hi Ufuk,
>
> I would suggest testing out some of the Catalyst examples which are in 
> the source code under the Examples/Catalyst subdirectory. I would also 
> suggest creating Catalyst scripts from data sets generated through 
> Catalyst output instead of the NetCDF files. There are two example 
> scripts for this in Examples/Catalyst/SampleScripts that you can use 
> for this.
>
> As for the grid names for the axes, this may be a bug in ParaView. 
> I'll look into that.
>
> Best,
> Andy
>
> On Wed, Apr 13, 2016 at 8:44 AM, Ufuk Utku Turuncoglu (BE) 
> <u.utku.turuncoglu at be.itu.edu.tr 
> <mailto:u.utku.turuncoglu at be.itu.edu.tr>> wrote:
>
>     Hi,
>
>     I am using co-processing (Catalyst) and i have couple of issues
>     about the behavior of the co-processing module.
>
>     1 - If i send multiple 2d variable or single 3d variable to the
>     co-processor, my custom code is working without any problem and
>     produces desired output. On the other hand, the code hangs with
>     multiple 3d variable (it basically opens a square white window and
>     waits, see the attached screenshot). I have no idea about the
>     problem because the terminal does not produces any output. I could
>     install the ParaView in debug mode and it might help?
>
>     2 - The axis names (edited by Edit Axes Grid section in Properties
>     window) are not written to the produced png file when the
>     visualization pipeline is driven by co-processing but it looks
>     fine under ParaView.
>
>     3 - When i trying to use volume rendering (single 3d field) along
>     with co-processing, the code gives following error
>
>     ERROR: In
>     /opt/progs/paraview-5.0.0/src/VTK/Common/ExecutionModel/vtkCompositeDataPipeline.cxx,
>     line 171
>     vtkPVDataRepresentationPipeline (0x7fea05244010): Can not execute
>     simple alorithm without output ports
>     ...
>     ...
>     ERROR: In
>     /opt/progs/paraview-5.0.0/src/VTK/Filters/Parallel/vtkPKdTree.cxx,
>     line 296
>     vtkPKdTree (0x7fea04f42840): (process 0) NumberOfDatasets = 0,
>     cannot determine volume bounds.
>
>     I could produce iso-surface with same code without any problem.
>     The volume rendering is also working under ParaView.
>
>     The last question might be related with the grid definition in the
>     co-processing because i am using single netcdf dataset to create
>     visualization scripts (python) under ParaView but in the model
>     code (co-processing) the dataset is defined as MultiBlockDataSet
>     due to the parallel nature of the simulation code.
>
>     Regards,
>
>     --ufuk
>
>     _______________________________________________
>     Powered by www.kitware.com <http://www.kitware.com>
>
>     Visit other Kitware open-source projects at
>     http://www.kitware.com/opensource/opensource.html
>
>     Please keep messages on-topic and check the ParaView Wiki at:
>     http://paraview.org/Wiki/ParaView
>
>     Search the list archives at: http://markmail.org/search/?q=ParaView
>
>     Follow this link to subscribe/unsubscribe:
>     http://public.kitware.com/mailman/listinfo/paraview
>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160415/df2dffce/attachment.html>

From thomas.fastl at kcl.ac.uk  Fri Apr 15 05:51:29 2016
From: thomas.fastl at kcl.ac.uk (Fastl, Thomas)
Date: Fri, 15 Apr 2016 09:51:29 +0000
Subject: [Paraview] Changing Opacity with Coordinates
Message-ID: <HE1PR03MB10838FC44C3D1FA00B0A0F6CCC680@HE1PR03MB1083.eurprd03.prod.outlook.com>

Hello Community,

I've imported medical DICOM data into ParaView and visualized them in 'Volume' mode (rendering takes a really long time and around a massive amount of memory). I want to change the visibility/opacity of the medical image structure with the z-coordinate (apply and alpha-channel with full visibility at the bottom and no visibility at the top), is there a way to do that in ParaView? Thanks!

Best wishes, Tom

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160415/202d123f/attachment.html>

From utkarsh.ayachit at kitware.com  Fri Apr 15 08:48:57 2016
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Fri, 15 Apr 2016 08:48:57 -0400
Subject: [Paraview] Changing Opacity with Coordinates
In-Reply-To: <HE1PR03MB10838FC44C3D1FA00B0A0F6CCC680@HE1PR03MB1083.eurprd03.prod.outlook.com>
References: <HE1PR03MB10838FC44C3D1FA00B0A0F6CCC680@HE1PR03MB1083.eurprd03.prod.outlook.com>
Message-ID: <CADHSJjDxsH0n_eF2sk-UGtod3kf7=qG=vN+pdh3ra5BMBZ1ysg@mail.gmail.com>

I am assuming you want to change opacity using Z and color using some
other array -- if that's the case, I am afraid that's not supported
currently. You can only change the color and opacity using the same
array.

Utkarsh

On Fri, Apr 15, 2016 at 5:51 AM, Fastl, Thomas <thomas.fastl at kcl.ac.uk> wrote:
> Hello Community,
>
> I've imported medical DICOM data into ParaView and visualized them in
> 'Volume' mode (rendering takes a really long time and around a massive
> amount of memory). I want to change the visibility/opacity of the medical
> image structure with the z-coordinate (apply and alpha-channel with full
> visibility at the bottom and no visibility at the top), is there a way to do
> that in ParaView? Thanks!
>
> Best wishes, Tom
>
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview
>

From andy.bauer at kitware.com  Fri Apr 15 10:01:30 2016
From: andy.bauer at kitware.com (Andy Bauer)
Date: Fri, 15 Apr 2016 10:01:30 -0400
Subject: [Paraview] couple of issues related with co-processing ...
In-Reply-To: <5710AE1B.2020008@be.itu.edu.tr>
References: <570E3F20.3000602@be.itu.edu.tr>
 <CAMaOp+EOZ_cXDB4H9haAzpfMBJuJ5r83Az4Aii7EKBWj=OCH2A@mail.gmail.com>
 <5710AE1B.2020008@be.itu.edu.tr>
Message-ID: <CAMaOp+EHUhk=LmhDYPA0YmaT_51wmgyRMW2ceu4uvvgAcfGkyA@mail.gmail.com>

I haven't seen issues like that. Can you share the Catalyst script that
fails?

On Fri, Apr 15, 2016 at 5:02 AM, Ufuk Utku Turuncoglu (BE) <
u.utku.turuncoglu at be.itu.edu.tr> wrote:

> Hi Andy,
>
> As you suggested in your previous mail, i used allinputsgridwriter.py
> script to write all the available fields as multiblock dataset and i
> created co-processing scripts using this dataset. Now, i could handle
> multiple 3d fields but i have still problem in the combination of contour
> and vector visualization. In this case, the code hangs in same way that i
> mentioned in my initial mail.
>
> So, to find the source of the problem i tried different pipelines and
> check the co-processing,
>
> 1 - A pipeline with only Glyph filter. In this case, i set Gradients as
> Vectors in Active Attributes section in the properties window. The
> co-processing is working without any problem in this case.
>
> 2 - I used Calculator Filter to compute vector using u*iHat+v*jHat
> equation along with Glyph to produce vector field visualization. In this
> case, the pipeline is working without any error under co-processing.
>
> 3 - A visualization pipeline with an iso-surface which is colored by
> different variable. It works also.
>
> 4 - The combination of step 2 and 3. In this case, i used same
> visualization pipeline with 2 but in this case, i add a Contour filter to
> create an iso-surface for a scalar 3d field (same as step 3). The
> co-processing code hands with white screen and does not produce the output.
>
> So, it seems that the combination of Contour and vector visualization
> affects the co-processing. Anyway, do you have similar experience in
> co-processing?
>
> Regards,
>
> --ufuk
>
> On 13/04/16 16:24, Andy Bauer wrote:
>
> Hi Ufuk,
>
> I would suggest testing out some of the Catalyst examples which are in the
> source code under the Examples/Catalyst subdirectory. I would also suggest
> creating Catalyst scripts from data sets generated through Catalyst output
> instead of the NetCDF files. There are two example scripts for this in
> Examples/Catalyst/SampleScripts that you can use for this.
>
> As for the grid names for the axes, this may be a bug in ParaView. I'll
> look into that.
>
> Best,
> Andy
>
> On Wed, Apr 13, 2016 at 8:44 AM, Ufuk Utku Turuncoglu (BE) <
> <u.utku.turuncoglu at be.itu.edu.tr>u.utku.turuncoglu at be.itu.edu.tr> wrote:
>
>> Hi,
>>
>> I am using co-processing (Catalyst) and i have couple of issues about the
>> behavior of the co-processing module.
>>
>> 1 - If i send multiple 2d variable or single 3d variable to the
>> co-processor, my custom code is working without any problem and produces
>> desired output. On the other hand, the code hangs with multiple 3d variable
>> (it basically opens a square white window and waits, see the attached
>> screenshot). I have no idea about the problem because the terminal does not
>> produces any output. I could install the ParaView in debug mode and it
>> might help?
>>
>> 2 - The axis names (edited by Edit Axes Grid section in Properties
>> window) are not written to the produced png file when the visualization
>> pipeline is driven by co-processing but it looks fine under ParaView.
>>
>> 3 - When i trying to use volume rendering (single 3d field) along with
>> co-processing, the code gives following error
>>
>> ERROR: In
>> /opt/progs/paraview-5.0.0/src/VTK/Common/ExecutionModel/vtkCompositeDataPipeline.cxx,
>> line 171
>> vtkPVDataRepresentationPipeline (0x7fea05244010): Can not execute simple
>> alorithm without output ports
>> ...
>> ...
>> ERROR: In
>> /opt/progs/paraview-5.0.0/src/VTK/Filters/Parallel/vtkPKdTree.cxx, line 296
>> vtkPKdTree (0x7fea04f42840): (process 0) NumberOfDatasets = 0, cannot
>> determine volume bounds.
>>
>> I could produce iso-surface with same code without any problem. The
>> volume rendering is also working under ParaView.
>>
>> The last question might be related with the grid definition in the
>> co-processing because i am using single netcdf dataset to create
>> visualization scripts (python) under ParaView but in the model code
>> (co-processing) the dataset is defined as MultiBlockDataSet due to the
>> parallel nature of the simulation code.
>>
>> Regards,
>>
>> --ufuk
>>
>> _______________________________________________
>> Powered by www.kitware.com
>>
>> Visit other Kitware open-source projects at
>> <http://www.kitware.com/opensource/opensource.html>
>> http://www.kitware.com/opensource/opensource.html
>>
>> Please keep messages on-topic and check the ParaView Wiki at:
>> http://paraview.org/Wiki/ParaView
>>
>> Search the list archives at: http://markmail.org/search/?q=ParaView
>>
>> Follow this link to subscribe/unsubscribe:
>> http://public.kitware.com/mailman/listinfo/paraview
>>
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160415/db15021e/attachment.html>

From wascott at sandia.gov  Fri Apr 15 17:18:24 2016
From: wascott at sandia.gov (Scott, W Alan)
Date: Fri, 15 Apr 2016 21:18:24 +0000
Subject: [Paraview] Help with Programmable Filters
Message-ID: <97e0ddcb82df46b68c52b657acd82990@ES01AMSNLNT.srn.sandia.gov>

From a user:



Hi
I'm trying to get started with programmable filters and am having a little trouble putting it together from the material in the paraview user guide. I have a few questions below:

1.       Is there any documentation generally describing the input and output data objects that form the programmable filter API?

a.       I was able to get some basic info on these objects by executing "print dir(inputs[0])" for example in the program. filter window, but if there is documentation somewhere for each of the object types, that would be useful...

2.       It appears that the user guide suggested methods for accessing the data in the input objects (input.Points, input.PointData['Name'], etc) produce vtk data objects of some form. These can be indexed similar to numpy arrays, but seem to behave differently in other cases. For instance, I couldn't figure how to reshape these arrays (numpy.reshape fails as the vtk array objects don't have any shape attribute defined...). Is there any way to get the input data into actual numpy array form? This would be helpful for direct reuse of existing scripts designed to work on numpy arrays...

3.       I was attempting to write a simple script that does some calcs on a block structured input dataset (input comes in as vtkCompositeDataSet) and writes out some reduced data to a table (I chose vtkTable as the output format). Through inspection of the output object, I found that I could add new rows (which appear in paraview as columns...) of data using output.RowData.append(DATA,NAME). However, DATA needs to be some basic python sequence type or numpy array, and the vtk array types created by the input data access methods (input.Points etc...) don't work... So again here, if there is a good way to convert the data held in the vtk array types to numpy array types, that would be useful here...

Thanks,
Jon




Thanks,

Alan

From read.sean62 at gmail.com  Sat Apr 16 04:42:54 2016
From: read.sean62 at gmail.com (sean read)
Date: Sat, 16 Apr 2016 08:42:54 +0000
Subject: [Paraview] python error when importing paraview.simple with
 paraview 5.0
In-Reply-To: <CABt37mJ0mVHg8mLn1TiaTa6g+AGxmqAZFG5dEK-RJaXE5YkynQ@mail.gmail.com>
References: <CABt37mLbZQnUGS2CmaFHewaJRKASW_4AMjnmbugPF0iqbDaubQ@mail.gmail.com>
 <CADHSJjBOj3ac0oty5h9Vrvv8HtS9iDPFgmKc2TmvHM+XS0CkuA@mail.gmail.com>
 <CABt37m+NYaX5QMZgotZ_-O0ndZfce_SeXasL1+7NVuoUQoRsUg@mail.gmail.com>
 <CABt37mJ0mVHg8mLn1TiaTa6g+AGxmqAZFG5dEK-RJaXE5YkynQ@mail.gmail.com>
Message-ID: <CABt37mKkHw=RKfUb8fD+VGvxynTshUs9Uo+M+AfFa6UwQirEsg@mail.gmail.com>

So I'm using wrapper files, described here
<http://superuser.com/questions/192573/how-do-you-specify-the-location-of-libraries-to-a-binary-linux>
to
add the directory to my LD_LIBRARY_PATH where necessary. Not a great
solution, but it's sufficient for now

On Wed, 13 Apr 2016 at 12:04 sean read <read.sean62 at gmail.com> wrote:

> Wait, check that, so adding  ".../lib/paraview-5.0" did fix the problem
> with python, but it has had other negative side effects. Now when I open
> certain filetypes in vim (so far that I've checked, .py, .tex, .bib, which
> are all types for which I have customised options) the terminal window
> shows strange text. For example:
>
>  "exim.py" 258L, 6565CTraceback (most recent call last):
>                                                          File
> "/usr/lib/python2.7/site.py", line 563, in <module>
>
>                                            main()
>
>                                                    File
> "/usr/lib/python2.7/site.py", line 545, in main
>
>
>                                known_paths =
> addusersitepackages(known_paths)
>
>
>
>    File "/usr/lib/python2.7/site.py", line 272, in addusersitepackages
>                                                                user_site =
> getusersitepackages())
>
>
>
> After this it becomes unresponsive and I have to close the terminal. I am
> not entirely familiar with the use of the LD_LIBRARY_PATH, is there any
> reason that this alteration would effect the operation of vim?
>
>
> On Tue, 12 Apr 2016 at 22:18 sean read <read.sean62 at gmail.com> wrote:
>
>> Great! that fixed the problem, now everything is working perfectly
>>
>> On Tue, 12 Apr 2016 at 22:12 Utkarsh Ayachit <utkarsh.ayachit at kitware.com>
>> wrote:
>>
>>> Try setting your LD_LIBRARY_PATH to include the ".../lib/paraview-5.0"
>>> directory.
>>>
>>> On Tue, Apr 12, 2016 at 5:53 AM, sean read <read.sean62 at gmail.com>
>>> wrote:
>>> > So I've downloaded paraview5.0 from the website
>>> > http://www.paraview.org/download/nload/, and set my python path as
>>> >
>>> >
>>> :/home/sean/bin/ParaView-5.0.1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.0:/home/sean/bin/ParaView-5.0.1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.0/site-packages/vtk:/home/sean/bin/ParaView-5.0.1-Qt4-OpenGL2-MPI-Linux-64bit/bin:/home/sean/bin/ParaView-5.0.1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.0/site-packages
>>> >
>>> > When I import paraview.simple in python I get the error message
>>> >
>>> > ImportError: libvtkCommonCorePython27D-pv5.0.so.1: cannot open shared
>>> object
>>> > file: No such file or directory
>>> >
>>> > but libvtkCommonCorePython27D-pv5.0.so.1 is in
>>> >
>>> /home/sean/bin/ParaView-5.0.1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.0,
>>> > which is in my python path.
>>> >
>>> > PV python is functioning as normal
>>> >
>>> > I am running linux mint 17.3
>>> >
>>> > Any suggestions?
>>> > --
>>> > Sean Read
>>> > Level 1 Yantra Yoga Instructor
>>> >
>>> >
>>> > _______________________________________________
>>> > Powered by www.kitware.com
>>> >
>>> > Visit other Kitware open-source projects at
>>> > http://www.kitware.com/opensource/opensource.html
>>> >
>>> > Please keep messages on-topic and check the ParaView Wiki at:
>>> > http://paraview.org/Wiki/ParaView
>>> >
>>> > Search the list archives at: http://markmail.org/search/?q=ParaView
>>> >
>>> > Follow this link to subscribe/unsubscribe:
>>> > http://public.kitware.com/mailman/listinfo/paraview
>>> >
>>>
>> --
>> Sean Read
>> Level 1 Yantra Yoga Instructor
>>
>> --
> Sean Read
> Level 1 Yantra Yoga Instructor
>
> --
Sean Read
Level 1 Yantra Yoga Instructor
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160416/3288c008/attachment.html>

From u.utku.turuncoglu at be.itu.edu.tr  Sat Apr 16 08:31:17 2016
From: u.utku.turuncoglu at be.itu.edu.tr (u.utku.turuncoglu at be.itu.edu.tr)
Date: Sat, 16 Apr 2016 15:31:17 +0300 (EEST)
Subject: [Paraview] couple of issues related with co-processing ...
In-Reply-To: <CAMaOp+EHUhk=LmhDYPA0YmaT_51wmgyRMW2ceu4uvvgAcfGkyA@mail.gmail.com>
References: <570E3F20.3000602@be.itu.edu.tr>
 <CAMaOp+EOZ_cXDB4H9haAzpfMBJuJ5r83Az4Aii7EKBWj=OCH2A@mail.gmail.com>
 <5710AE1B.2020008@be.itu.edu.tr>
 <CAMaOp+EHUhk=LmhDYPA0YmaT_51wmgyRMW2ceu4uvvgAcfGkyA@mail.gmail.com>
Message-ID: <52008.85.110.174.64.1460809877.squirrel@webmail.be.itu.edu.tr>

Hi,

You can download the Catalyst script from following link,

https://www.dropbox.com/s/eajs9dm0of5b4bi/script_data.tar.gz?dl=0

I also included the data and ParaView state that is used to create the
Catalyst script. So, it might help to find the problem.

Thanks,

--ufuk

> I haven't seen issues like that. Can you share the Catalyst script that
> fails?
>
> On Fri, Apr 15, 2016 at 5:02 AM, Ufuk Utku Turuncoglu (BE) <
> u.utku.turuncoglu at be.itu.edu.tr> wrote:
>
>> Hi Andy,
>>
>> As you suggested in your previous mail, i used allinputsgridwriter.py
>> script to write all the available fields as multiblock dataset and i
>> created co-processing scripts using this dataset. Now, i could handle
>> multiple 3d fields but i have still problem in the combination of
>> contour
>> and vector visualization. In this case, the code hangs in same way that
>> i
>> mentioned in my initial mail.
>>
>> So, to find the source of the problem i tried different pipelines and
>> check the co-processing,
>>
>> 1 - A pipeline with only Glyph filter. In this case, i set Gradients as
>> Vectors in Active Attributes section in the properties window. The
>> co-processing is working without any problem in this case.
>>
>> 2 - I used Calculator Filter to compute vector using u*iHat+v*jHat
>> equation along with Glyph to produce vector field visualization. In this
>> case, the pipeline is working without any error under co-processing.
>>
>> 3 - A visualization pipeline with an iso-surface which is colored by
>> different variable. It works also.
>>
>> 4 - The combination of step 2 and 3. In this case, i used same
>> visualization pipeline with 2 but in this case, i add a Contour filter
>> to
>> create an iso-surface for a scalar 3d field (same as step 3). The
>> co-processing code hands with white screen and does not produce the
>> output.
>>
>> So, it seems that the combination of Contour and vector visualization
>> affects the co-processing. Anyway, do you have similar experience in
>> co-processing?
>>
>> Regards,
>>
>> --ufuk
>>
>> On 13/04/16 16:24, Andy Bauer wrote:
>>
>> Hi Ufuk,
>>
>> I would suggest testing out some of the Catalyst examples which are in
>> the
>> source code under the Examples/Catalyst subdirectory. I would also
>> suggest
>> creating Catalyst scripts from data sets generated through Catalyst
>> output
>> instead of the NetCDF files. There are two example scripts for this in
>> Examples/Catalyst/SampleScripts that you can use for this.
>>
>> As for the grid names for the axes, this may be a bug in ParaView. I'll
>> look into that.
>>
>> Best,
>> Andy
>>
>> On Wed, Apr 13, 2016 at 8:44 AM, Ufuk Utku Turuncoglu (BE) <
>> <u.utku.turuncoglu at be.itu.edu.tr>u.utku.turuncoglu at be.itu.edu.tr> wrote:
>>
>>> Hi,
>>>
>>> I am using co-processing (Catalyst) and i have couple of issues about
>>> the
>>> behavior of the co-processing module.
>>>
>>> 1 - If i send multiple 2d variable or single 3d variable to the
>>> co-processor, my custom code is working without any problem and
>>> produces
>>> desired output. On the other hand, the code hangs with multiple 3d
>>> variable
>>> (it basically opens a square white window and waits, see the attached
>>> screenshot). I have no idea about the problem because the terminal does
>>> not
>>> produces any output. I could install the ParaView in debug mode and it
>>> might help?
>>>
>>> 2 - The axis names (edited by Edit Axes Grid section in Properties
>>> window) are not written to the produced png file when the visualization
>>> pipeline is driven by co-processing but it looks fine under ParaView.
>>>
>>> 3 - When i trying to use volume rendering (single 3d field) along with
>>> co-processing, the code gives following error
>>>
>>> ERROR: In
>>> /opt/progs/paraview-5.0.0/src/VTK/Common/ExecutionModel/vtkCompositeDataPipeline.cxx,
>>> line 171
>>> vtkPVDataRepresentationPipeline (0x7fea05244010): Can not execute
>>> simple
>>> alorithm without output ports
>>> ...
>>> ...
>>> ERROR: In
>>> /opt/progs/paraview-5.0.0/src/VTK/Filters/Parallel/vtkPKdTree.cxx, line
>>> 296
>>> vtkPKdTree (0x7fea04f42840): (process 0) NumberOfDatasets = 0, cannot
>>> determine volume bounds.
>>>
>>> I could produce iso-surface with same code without any problem. The
>>> volume rendering is also working under ParaView.
>>>
>>> The last question might be related with the grid definition in the
>>> co-processing because i am using single netcdf dataset to create
>>> visualization scripts (python) under ParaView but in the model code
>>> (co-processing) the dataset is defined as MultiBlockDataSet due to the
>>> parallel nature of the simulation code.
>>>
>>> Regards,
>>>
>>> --ufuk
>>>
>>> _______________________________________________
>>> Powered by www.kitware.com
>>>
>>> Visit other Kitware open-source projects at
>>> <http://www.kitware.com/opensource/opensource.html>
>>> http://www.kitware.com/opensource/opensource.html
>>>
>>> Please keep messages on-topic and check the ParaView Wiki at:
>>> http://paraview.org/Wiki/ParaView
>>>
>>> Search the list archives at: http://markmail.org/search/?q=ParaView
>>>
>>> Follow this link to subscribe/unsubscribe:
>>> http://public.kitware.com/mailman/listinfo/paraview
>>>
>>>
>>
>>
>


From fabidi89 at vt.edu  Sat Apr 16 12:31:31 2016
From: fabidi89 at vt.edu (Faiz Abidi)
Date: Sat, 16 Apr 2016 12:31:31 -0400
Subject: [Paraview] VRUI vs. VRPN
Message-ID: <CAA7GnUkxS11pMrsFe1_x+5KWNjQFo3iiOKRg+knWpeEYd68g6g@mail.gmail.com>

Hi guys,

Wondering if there are any advantages/disadvantages of using one over the
other. We have Paraview5.0 running on Ubuntu driving a 4 walled CAVE. Any
suggestions?
-- 
Faiz Abidi | Master's Student at Virginia Tech | www.faizabidi.com |
+1-540-998-6636
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160416/97efe156/attachment.html>

From patrick.oleary at kitware.com  Sat Apr 16 12:49:08 2016
From: patrick.oleary at kitware.com (Patrick O'Leary)
Date: Sat, 16 Apr 2016 10:49:08 -0600
Subject: [Paraview] VRUI vs. VRPN
In-Reply-To: <CAA7GnUkxS11pMrsFe1_x+5KWNjQFo3iiOKRg+knWpeEYd68g6g@mail.gmail.com>
References: <CAA7GnUkxS11pMrsFe1_x+5KWNjQFo3iiOKRg+knWpeEYd68g6g@mail.gmail.com>
Message-ID: <CAM8hOwbiJTE_Sg0uzP7GMwE5mgEZii34zFovuWu62_JrXeqyug@mail.gmail.com>

No real advantages or disadvantages. If you are using VRPN for handling
tracking now. Then use VRPN. If not, you could use Vrui for ParaView and
take advantage of other Vrui applications by KeckCaves, Oliver Kreylos, and
Idaho National Laboratory.

I personally don't like configure multiple tracking software, or even one,
for a CAVE. It's a pain. And I love the other applications using Vrui
(LivdarViewer, 3DVisualizer, ...), so I use Vrui instead of VRPN.

Regards,
Patrick

On Sat, Apr 16, 2016 at 10:31 AM, Faiz Abidi <fabidi89 at vt.edu> wrote:

> Hi guys,
>
> Wondering if there are any advantages/disadvantages of using one over the
> other. We have Paraview5.0 running on Ubuntu driving a 4 walled CAVE. Any
> suggestions?
> --
> Faiz Abidi | Master's Student at Virginia Tech | www.faizabidi.com |
> +1-540-998-6636
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160416/44ee99b3/attachment.html>

From dave.demarle at kitware.com  Sat Apr 16 15:27:18 2016
From: dave.demarle at kitware.com (David E DeMarle)
Date: Sat, 16 Apr 2016 15:27:18 -0400
Subject: [Paraview] VRUI vs. VRPN
In-Reply-To: <CAA7GnUkxS11pMrsFe1_x+5KWNjQFo3iiOKRg+knWpeEYd68g6g@mail.gmail.com>
References: <CAA7GnUkxS11pMrsFe1_x+5KWNjQFo3iiOKRg+knWpeEYd68g6g@mail.gmail.com>
Message-ID: <CANjZAi8242LW-1TTeRVa=vN=G76pLwHa_MtNFrPE9SwzowUB5Q@mail.gmail.com>

How did you all make out with the passive stereo connection Faiz?
On Apr 16, 2016 12:31 PM, "Faiz Abidi" <fabidi89 at vt.edu> wrote:

> Hi guys,
>
> Wondering if there are any advantages/disadvantages of using one over the
> other. We have Paraview5.0 running on Ubuntu driving a 4 walled CAVE. Any
> suggestions?
> --
> Faiz Abidi | Master's Student at Virginia Tech | www.faizabidi.com |
> +1-540-998-6636
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160416/0e2c9ad2/attachment.html>

From fabidi89 at vt.edu  Sat Apr 16 15:46:06 2016
From: fabidi89 at vt.edu (Faiz Abidi)
Date: Sat, 16 Apr 2016 15:46:06 -0400
Subject: [Paraview] VRUI vs. VRPN
In-Reply-To: <CANjZAi8242LW-1TTeRVa=vN=G76pLwHa_MtNFrPE9SwzowUB5Q@mail.gmail.com>
References: <CAA7GnUkxS11pMrsFe1_x+5KWNjQFo3iiOKRg+knWpeEYd68g6g@mail.gmail.com>
 <CANjZAi8242LW-1TTeRVa=vN=G76pLwHa_MtNFrPE9SwzowUB5Q@mail.gmail.com>
Message-ID: <CAA7GnUmcMdtSnupxKy_-ndkCTLEUAmCswLZkOD5e1fQGXRs4BA@mail.gmail.com>

Thanks for the reply, Patrick.

We have temporarily put that on hold, David. Will probably resume that next
month.

On Sat, Apr 16, 2016 at 3:27 PM, David E DeMarle <dave.demarle at kitware.com>
wrote:

> How did you all make out with the passive stereo connection Faiz?
> On Apr 16, 2016 12:31 PM, "Faiz Abidi" <fabidi89 at vt.edu> wrote:
>
>> Hi guys,
>>
>> Wondering if there are any advantages/disadvantages of using one over the
>> other. We have Paraview5.0 running on Ubuntu driving a 4 walled CAVE. Any
>> suggestions?
>> --
>> Faiz Abidi | Master's Student at Virginia Tech | www.faizabidi.com |
>> +1-540-998-6636
>>
>> _______________________________________________
>> Powered by www.kitware.com
>>
>> Visit other Kitware open-source projects at
>> http://www.kitware.com/opensource/opensource.html
>>
>> Please keep messages on-topic and check the ParaView Wiki at:
>> http://paraview.org/Wiki/ParaView
>>
>> Search the list archives at: http://markmail.org/search/?q=ParaView
>>
>> Follow this link to subscribe/unsubscribe:
>> http://public.kitware.com/mailman/listinfo/paraview
>>
>>


-- 
Faiz Abidi | Master's Student at Virginia Tech | www.faizabidi.com |
+1-540-998-6636
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160416/d289f965/attachment.html>

From utkarsh.ayachit at kitware.com  Sun Apr 17 11:03:38 2016
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Sun, 17 Apr 2016 11:03:38 -0400
Subject: [Paraview] python error when importing paraview.simple with
 paraview 5.0
In-Reply-To: <CABt37mKkHw=RKfUb8fD+VGvxynTshUs9Uo+M+AfFa6UwQirEsg@mail.gmail.com>
References: <CABt37mLbZQnUGS2CmaFHewaJRKASW_4AMjnmbugPF0iqbDaubQ@mail.gmail.com>
 <CADHSJjBOj3ac0oty5h9Vrvv8HtS9iDPFgmKc2TmvHM+XS0CkuA@mail.gmail.com>
 <CABt37m+NYaX5QMZgotZ_-O0ndZfce_SeXasL1+7NVuoUQoRsUg@mail.gmail.com>
 <CABt37mJ0mVHg8mLn1TiaTa6g+AGxmqAZFG5dEK-RJaXE5YkynQ@mail.gmail.com>
 <CABt37mKkHw=RKfUb8fD+VGvxynTshUs9Uo+M+AfFa6UwQirEsg@mail.gmail.com>
Message-ID: <CADHSJjDoL8n_3T8MO7+r88yp8nVFNbEJR6uCCMhEO5yGX_kwNg@mail.gmail.com>

Sean,

Sorry for not getting back to you sooner. But as you discovered, it's
generally not a good idea to set LD_LIBRARY_PATH globally. What you're
doing is a reasonable approach for now. In future, we do plan to
update the ParaView build infrastructure to use rpath for installed
binaries to avoid running into this issue. Not sure when that would
happen, but it's on the charts.

Utkarsh

On Sat, Apr 16, 2016 at 4:42 AM, sean read <read.sean62 at gmail.com> wrote:
> So I'm using wrapper files, described here to add the directory to my
> LD_LIBRARY_PATH where necessary. Not a great solution, but it's sufficient
> for now
>
> On Wed, 13 Apr 2016 at 12:04 sean read <read.sean62 at gmail.com> wrote:
>>
>> Wait, check that, so adding  ".../lib/paraview-5.0" did fix the problem
>> with python, but it has had other negative side effects. Now when I open
>> certain filetypes in vim (so far that I've checked, .py, .tex, .bib, which
>> are all types for which I have customised options) the terminal window shows
>> strange text. For example:
>>
>>  "exim.py" 258L, 6565CTraceback (most recent call last):
>>                                                          File
>> "/usr/lib/python2.7/site.py", line 563, in <module>
>>
>> main()
>>
>> File "/usr/lib/python2.7/site.py", line 545, in main
>>
>> known_paths = addusersitepackages(known_paths)
>>
>> File "/usr/lib/python2.7/site.py", line 272, in addusersitepackages
>>                                                                user_site =
>> getusersitepackages())
>>
>>
>>
>> After this it becomes unresponsive and I have to close the terminal. I am
>> not entirely familiar with the use of the LD_LIBRARY_PATH, is there any
>> reason that this alteration would effect the operation of vim?
>>
>>
>> On Tue, 12 Apr 2016 at 22:18 sean read <read.sean62 at gmail.com> wrote:
>>>
>>> Great! that fixed the problem, now everything is working perfectly
>>>
>>> On Tue, 12 Apr 2016 at 22:12 Utkarsh Ayachit
>>> <utkarsh.ayachit at kitware.com> wrote:
>>>>
>>>> Try setting your LD_LIBRARY_PATH to include the ".../lib/paraview-5.0"
>>>> directory.
>>>>
>>>> On Tue, Apr 12, 2016 at 5:53 AM, sean read <read.sean62 at gmail.com>
>>>> wrote:
>>>> > So I've downloaded paraview5.0 from the website
>>>> > http://www.paraview.org/download/nload/, and set my python path as
>>>> >
>>>> >
>>>> > :/home/sean/bin/ParaView-5.0.1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.0:/home/sean/bin/ParaView-5.0.1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.0/site-packages/vtk:/home/sean/bin/ParaView-5.0.1-Qt4-OpenGL2-MPI-Linux-64bit/bin:/home/sean/bin/ParaView-5.0.1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.0/site-packages
>>>> >
>>>> > When I import paraview.simple in python I get the error message
>>>> >
>>>> > ImportError: libvtkCommonCorePython27D-pv5.0.so.1: cannot open shared
>>>> > object
>>>> > file: No such file or directory
>>>> >
>>>> > but libvtkCommonCorePython27D-pv5.0.so.1 is in
>>>> >
>>>> > /home/sean/bin/ParaView-5.0.1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.0,
>>>> > which is in my python path.
>>>> >
>>>> > PV python is functioning as normal
>>>> >
>>>> > I am running linux mint 17.3
>>>> >
>>>> > Any suggestions?
>>>> > --
>>>> > Sean Read
>>>> > Level 1 Yantra Yoga Instructor
>>>> >
>>>> >
>>>> > _______________________________________________
>>>> > Powered by www.kitware.com
>>>> >
>>>> > Visit other Kitware open-source projects at
>>>> > http://www.kitware.com/opensource/opensource.html
>>>> >
>>>> > Please keep messages on-topic and check the ParaView Wiki at:
>>>> > http://paraview.org/Wiki/ParaView
>>>> >
>>>> > Search the list archives at: http://markmail.org/search/?q=ParaView
>>>> >
>>>> > Follow this link to subscribe/unsubscribe:
>>>> > http://public.kitware.com/mailman/listinfo/paraview
>>>> >
>>>
>>> --
>>> Sean Read
>>> Level 1 Yantra Yoga Instructor
>>>
>> --
>> Sean Read
>> Level 1 Yantra Yoga Instructor
>>
> --
> Sean Read
> Level 1 Yantra Yoga Instructor
>

From biddisco at cscs.ch  Mon Apr 18 02:36:54 2016
From: biddisco at cscs.ch (Biddiscombe, John A.)
Date: Mon, 18 Apr 2016 06:36:54 +0000
Subject: [Paraview] Specifying camera movement using points from a file
In-Reply-To: <AM4PR03MB1457F775D7FA628601E49EEAA4970@AM4PR03MB1457.eurprd03.prod.outlook.com>
References: <AM4PR03MB1457B8D640B86CF4CB158BADA4960@AM4PR03MB1457.eurprd03.prod.outlook.com>
 <CAB5Fpx7RmTTV=8RtgWS5Ryfihm0-6e3=QRD71X0QHtQbxDcPLw@mail.gmail.com>
 <AM4PR03MB1457F775D7FA628601E49EEAA4970@AM4PR03MB1457.eurprd03.prod.outlook.com>
Message-ID: <50320452A334BD42A5EC72BAD21450993DF0BF7A@MBX210.d.ethz.ch>

There is a very old branch here

https://github.com/biddisco/ParaView/commits/jb-4.0-volrender


with two commits that add a helix generator to the pv gui.

No idea if they would still merge with master - they date back to 2013, but if someone wanted an interactive helix edit for camera path ....

JB

-----Original Message-----
From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Per Adamsen
Sent: 14 April 2016 07:45
To: Cory Quammen
Cc: paraview at paraview.org
Subject: Re: [Paraview] Specifying camera movement using points from a file

Hi Cory,

Thanks for your feedback.

Of course this can be handled with a Python script - sometimes the answer is so obvious ;-)

I will follow your advice and let you know if I encounter any problems.

Regards,
Per

-----Original Message-----
From: Cory Quammen [mailto:cory.quammen at kitware.com]
Sent: 13. april 2016 16:03
To: Per Adamsen <padamsen at grundfos.com>
Cc: paraview at paraview.org
Subject: Re: [Paraview] Specifying camera movement using points from a file

Per,

You can do this with Python scripting in the Python console.

# get active view
renderView1 = GetActiveViewOrCreate('RenderView')

# uncomment following to set a specific view size # renderView1.ViewSize = [689, 340]

# get camera animation track for the view
cameraAnimationCue1 = GetCameraTrack(view=renderView1)

# create keyframes for this animation track # create a key frame
keyFrame4737 = CameraKeyFrame()
keyFrame4737.Position = [0.0, 0.0, 6.69] keyFrame4737.ParallelScale = 1.73

keyFrame4737.PositionPathPoints = [0.0, 0.0, 5.0, 2.938926261462365, 0.0, 4.045084971874736, 4.755282581475766, 0.0, 1.545084971874737, 4.755282581475766, 0.0, -1.5450849718747361, 2.938926261462365, 0.0, -4.045084971874735, 1.3322676295501878e-15, 0.0, -4.9999999999999964, -2.9389262614623624, 0.0, -4.045084971874735, -4.755282581475763, 0.0, -1.5450849718747368, -4.755282581475763, 0.0, 1.5450849718747341, -2.9389262614623632, 0.0, 4.045084971874731]

keyFrame4737.FocalPathPoints = [0.0, 0.0, 0.0] keyFrame4737.ClosedPositionPath = 1

# create a key frame
keyFrame4738 = CameraKeyFrame()
keyFrame4738.KeyTime = 1.0
keyFrame4738.Position = [0.0, 0.0, 6.69] keyFrame4738.ParallelScale = 1.73

# initialize the animation track
cameraAnimationCue1.Mode = 'Path-based'
cameraAnimationCue1.KeyFrames = [keyFrame4737, keyFrame4738]

# get animation scene
animationScene1 = GetAnimationScene()

animationScene1.Play()

Just modify the keyFrame4737.PositionPathPoints. They are ordered [x, y, z, x, y, z ...].

HTH,
Cory


On Wed, Apr 13, 2016 at 7:38 AM, Per Adamsen <padamsen at grundfos.com> wrote:
> Hi,
>
>
>
> I have been playing with the camera animations in PV5.0 and was 
> wondering if there was an easier way to specify the camera path than 
> manually adding and dragging points.
>
>
>
> Is it possible to copy paste camera coordinates from a file to obtain 
> e.g. a helical path?
>
>
>
> Thank you in advance.
>
>
>
> Regards,
>
> Per
>
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at 
> http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview
>



--
Cory Quammen
R&D Engineer
Kitware, Inc.
_______________________________________________
Powered by www.kitware.com

Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView

Search the list archives at: http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview

From biddisco at cscs.ch  Mon Apr 18 02:42:57 2016
From: biddisco at cscs.ch (Biddiscombe, John A.)
Date: Mon, 18 Apr 2016 06:42:57 +0000
Subject: [Paraview] peak memory use on remote nodes
Message-ID: <50320452A334BD42A5EC72BAD21450993DF0BFA8@MBX210.d.ethz.ch>

The python scripting module "paraview.benchmark" allows one to get the memory use using "paraview.benchmark.get_memuse" - but I presume this is the memory reported as used by the system at the moment when the function is called.

Does anyone know a way of recording the peak memory use on remote nodes between t1 and t2 - where t1 and t2 are the start and stop of either a function, job or even paraview python script on the remote node?

thanks

JB

--
John Biddiscombe,                        email:biddisco @.at.@ cscs.ch
http://www.cscs.ch/
CSCS, Swiss National Supercomputing Centre  | Tel:  +41 (91) 610.82.07
Via Trevano 131, 6900 Lugano, Switzerland   | Fax:  +41 (91) 610.82.82

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160418/cb0ac574/attachment.html>

From paul.melis at surfsara.nl  Mon Apr 18 05:54:30 2016
From: paul.melis at surfsara.nl (Paul Melis)
Date: Mon, 18 Apr 2016 11:54:30 +0200
Subject: [Paraview] Client-server mode fails with 5.0.1
Message-ID: <5714AED6.5080101@surfsara.nl>

Hi,

With official binaries of 5.0.1 on Linux 64-bit for both server and 
client nodes I get the following error directly after connecting the client:

paulm at s37n1:~/software/ParaView-5.0.1-Qt4-OpenGL2-MPI-Linux-64bit/bin$ 
./pvserver --use-offscreen-rendering
Waiting for client...
Connection URL: cs://s37n1.int.elvis.surfsara.nl:11111
Accepting connection(s): s37n1.int.elvis.surfsara.nl:11111
Client connected.
X Error of failed request:  BadAlloc (insufficient resources for operation)
   Major opcode of failed request:  135 (GLX)
   Minor opcode of failed request:  34 ()
   Serial number of failed request:  30
   Current serial number in output stream:  31

DISPLAY is set correctly, in glxinfo I see nothing strange, glxgears 
runs without issues (see below).

The message "insufficient resources" is a bit puzzling. I see no problem 
with other OpenGL applications. I also tried server binaries I compiled 
myself, but that gives the same error. Other than the EGL stuff in 5.0 
is there something different in the way ParaView is trying to initialize 
OpenGL/GLX that could cause the above error?

Regards,
Paul


paulm at s37n1:~$ glxgears
Running synchronized to the vertical refresh.  The framerate should be
approximately the same as the monitor refresh rate.
86354 frames in 5.0 seconds = 17270.654 FPS
96998 frames in 5.0 seconds = 19399.479 FPS
^C


paulm at s37n1:~$ glxgears
name of display: :0.0
display: :0  screen: 0
direct rendering: Yes
server glx vendor string: NVIDIA Corporation
server glx version string: 1.4
server glx extensions:
     GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_SGIX_fbconfig,
     GLX_SGIX_pbuffer, GLX_SGI_video_sync, GLX_SGI_swap_control,
     GLX_EXT_swap_control, GLX_EXT_swap_control_tear,
     GLX_EXT_texture_from_pixmap, GLX_EXT_buffer_age, 
GLX_ARB_create_context,
     GLX_ARB_create_context_profile, GLX_EXT_create_context_es_profile,
     GLX_EXT_create_context_es2_profile, GLX_ARB_create_context_robustness,
     GLX_NV_delay_before_swap, GLX_EXT_stereo_tree,
     GLX_ARB_context_flush_control, GLX_ARB_multisample, 
GLX_NV_float_buffer,
     GLX_ARB_fbconfig_float, GLX_EXT_framebuffer_sRGB,
     GLX_NV_multisample_coverage, GLX_NV_copy_image
client glx vendor string: NVIDIA Corporation
client glx version string: 1.4
client glx extensions:
     GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_visual_info,
     GLX_EXT_visual_rating, GLX_EXT_import_context, GLX_SGI_video_sync,
     GLX_NV_swap_group, GLX_NV_video_out, GLX_SGIX_fbconfig, 
GLX_SGIX_pbuffer,
     GLX_SGI_swap_control, GLX_EXT_swap_control, GLX_EXT_swap_control_tear,
     GLX_EXT_buffer_age, GLX_ARB_create_context,
     GLX_ARB_create_context_profile, GLX_NV_float_buffer,
     GLX_ARB_fbconfig_float, GLX_EXT_fbconfig_packed_float,
     GLX_EXT_texture_from_pixmap, GLX_EXT_framebuffer_sRGB,
     GLX_NV_present_video, GLX_NV_copy_image, GLX_NV_copy_buffer,
     GLX_NV_multisample_coverage, GLX_NV_video_capture,
     GLX_EXT_create_context_es_profile, GLX_EXT_create_context_es2_profile,
     GLX_ARB_create_context_robustness, GLX_NV_delay_before_swap,
     GLX_EXT_stereo_tree, GLX_ARB_context_flush_control
GLX version: 1.4
GLX extensions:
     GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_SGIX_fbconfig,
     GLX_SGIX_pbuffer, GLX_SGI_video_sync, GLX_SGI_swap_control,
     GLX_EXT_swap_control, GLX_EXT_swap_control_tear,
     GLX_EXT_texture_from_pixmap, GLX_EXT_buffer_age, 
GLX_ARB_create_context,
     GLX_ARB_create_context_profile, GLX_EXT_create_context_es_profile,
     GLX_EXT_create_context_es2_profile, GLX_ARB_create_context_robustness,
     GLX_NV_delay_before_swap, GLX_EXT_stereo_tree,
     GLX_ARB_context_flush_control, GLX_ARB_multisample, 
GLX_NV_float_buffer,
     GLX_ARB_fbconfig_float, GLX_EXT_framebuffer_sRGB,
     GLX_NV_multisample_coverage, GLX_NV_copy_image, 
GLX_ARB_get_proc_address
OpenGL vendor string: NVIDIA Corporation
OpenGL renderer string: GeForce GTX 780 Ti/PCIe/SSE2
OpenGL version string: 4.5.0 NVIDIA 361.28
OpenGL extensions:
     GL_AMD_multi_draw_indirect, GL_AMD_seamless_cubemap_per_texture,
     GL_ARB_arrays_of_arrays, GL_ARB_base_instance, 
GL_ARB_bindless_texture,
     GL_ARB_blend_func_extended, GL_ARB_buffer_storage,
     GL_ARB_clear_buffer_object, GL_ARB_clear_texture, GL_ARB_clip_control,
     GL_ARB_color_buffer_float, GL_ARB_compatibility,
     GL_ARB_compressed_texture_pixel_storage, GL_ARB_conservative_depth,
     GL_ARB_compute_shader, GL_ARB_compute_variable_group_size,
     GL_ARB_conditional_render_inverted, GL_ARB_copy_buffer, 
GL_ARB_copy_image,
     GL_ARB_cull_distance, GL_ARB_debug_output, GL_ARB_depth_buffer_float,
     GL_ARB_depth_clamp, GL_ARB_depth_texture, GL_ARB_derivative_control,
     GL_ARB_direct_state_access, GL_ARB_draw_buffers,
     GL_ARB_draw_buffers_blend, GL_ARB_draw_indirect,
     GL_ARB_draw_elements_base_vertex, GL_ARB_draw_instanced,
     GL_ARB_enhanced_layouts, GL_ARB_ES2_compatibility,
     GL_ARB_ES3_compatibility, GL_ARB_ES3_1_compatibility,
....







-- 

Paul Melis
| Visualization group leader & developer | SURFsara |
| Science Park 140 | 1098 XG Amsterdam |
| T 020 800 1312 | paul.melis at surfsara.nl | www.surfsara.nl |

From dave.demarle at kitware.com  Mon Apr 18 08:48:29 2016
From: dave.demarle at kitware.com (David E DeMarle)
Date: Mon, 18 Apr 2016 08:48:29 -0400
Subject: [Paraview] peak memory use on remote nodes
In-Reply-To: <50320452A334BD42A5EC72BAD21450993DF0BFA8@MBX210.d.ethz.ch>
References: <50320452A334BD42A5EC72BAD21450993DF0BFA8@MBX210.d.ethz.ch>
Message-ID: <CANjZAi-nS+tT0EDTz-UMS=6VGNe4F0LewZ-E1mucAcpMgqhpWw@mail.gmail.com>

Perhaps extend the benchmark to glean /proc/<PID>/status's VmHWM entry on
Linux at least. Get the number for t1 and at t2 and subtract to see what
the maximum was in between those two times.

Seems the right place to do that is kwsys/SystemInformation.cxx, but you
could prototype in the script.

Hope that helps and please post some code. Seems like a very useful thing
to have.


David E DeMarle
Kitware, Inc.
R&D Engineer
21 Corporate Drive
Clifton Park, NY 12065-8662
Phone: 518-881-4909

On Mon, Apr 18, 2016 at 2:42 AM, Biddiscombe, John A. <biddisco at cscs.ch>
wrote:

> The python scripting module ?paraview.benchmark? allows one to get the
> memory use using ?paraview.benchmark.get_memuse? - but I presume this is
> the memory reported as used by the system at the moment when the function
> is called.
>
>
>
> Does anyone know a way of recording the peak memory use on remote nodes
> between t1 and t2 - where t1 and t2 are the start and stop of either a
> function, job or even paraview python script on the remote node?
>
>
>
> thanks
>
>
>
> JB
>
>
>
> --
>
> John Biddiscombe,                        email:biddisco @.at.@ cscs.ch
>
> http://www.cscs.ch/
>
> CSCS, Swiss National Supercomputing Centre  | Tel:  +41 (91) 610.82.07
>
> Via Trevano 131, 6900 Lugano, Switzerland   | Fax:  +41 (91) 610.82.82
>
>
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160418/8ae2350c/attachment.html>

From biddisco at cscs.ch  Mon Apr 18 08:52:37 2016
From: biddisco at cscs.ch (Biddiscombe, John A.)
Date: Mon, 18 Apr 2016 12:52:37 +0000
Subject: [Paraview] peak memory use on remote nodes
In-Reply-To: <CANjZAi-nS+tT0EDTz-UMS=6VGNe4F0LewZ-E1mucAcpMgqhpWw@mail.gmail.com>
References: <50320452A334BD42A5EC72BAD21450993DF0BFA8@MBX210.d.ethz.ch>
 <CANjZAi-nS+tT0EDTz-UMS=6VGNe4F0LewZ-E1mucAcpMgqhpWw@mail.gmail.com>
Message-ID: <50320452A334BD42A5EC72BAD21450993DF0E1CD@MBX210.d.ethz.ch>

Thanks Dave

A colleague here suggested I put my
aprun pvbatch <blah> into a script and add a ?dtrace? command at the start of the script. This will then dump out a txt file on each node and after the job completes I can grep the info I need.

I?m going to give that a try first as it seems straightforward, but I will revert to your suggestion if I fail and nothing else comes up.

cheers

JB

From: David E DeMarle [mailto:dave.demarle at kitware.com]
Sent: 18 April 2016 14:48
To: Biddiscombe, John A.
Cc: paraview at paraview.org
Subject: Re: [Paraview] peak memory use on remote nodes

Perhaps extend the benchmark to glean /proc/<PID>/status's VmHWM entry on Linux at least. Get the number for t1 and at t2 and subtract to see what the maximum was in between those two times.

Seems the right place to do that is kwsys/SystemInformation.cxx, but you could prototype in the script.
Hope that helps and please post some code. Seems like a very useful thing to have.


David E DeMarle
Kitware, Inc.
R&D Engineer
21 Corporate Drive
Clifton Park, NY 12065-8662
Phone: 518-881-4909

On Mon, Apr 18, 2016 at 2:42 AM, Biddiscombe, John A. <biddisco at cscs.ch<mailto:biddisco at cscs.ch>> wrote:
The python scripting module ?paraview.benchmark? allows one to get the memory use using ?paraview.benchmark.get_memuse? - but I presume this is the memory reported as used by the system at the moment when the function is called.

Does anyone know a way of recording the peak memory use on remote nodes between t1 and t2 - where t1 and t2 are the start and stop of either a function, job or even paraview python script on the remote node?

thanks

JB

--
John Biddiscombe,                        email:biddisco @.at.@ cscs.ch<http://cscs.ch>
http://www.cscs.ch/
CSCS, Swiss National Supercomputing Centre  | Tel:  +41 (91) 610.82.07<tel:%2B41%20%2891%29%20610.82.07>
Via Trevano 131, 6900 Lugano, Switzerland   | Fax:  +41 (91) 610.82.82<tel:%2B41%20%2891%29%20610.82.82>


_______________________________________________
Powered by www.kitware.com<http://www.kitware.com>

Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView

Search the list archives at: http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160418/708ab0b3/attachment.html>

From wascott at sandia.gov  Mon Apr 18 12:48:25 2016
From: wascott at sandia.gov (Scott, W Alan)
Date: Mon, 18 Apr 2016 16:48:25 +0000
Subject: [Paraview] [EXTERNAL]  Client-server mode fails with 5.0.1
In-Reply-To: <5714AED6.5080101@surfsara.nl>
References: <5714AED6.5080101@surfsara.nl>
Message-ID: <c207754961194fd8a69e48f1b9f7f683@ES01AMSNLNT.srn.sandia.gov>

Paul,
Ssh -X is not working with newest ParaView.  X forwarding does not support the needed version of OpenGL for ParaView 5.0.1.

Could that be your problem?

Alan

-----Original Message-----
From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Paul Melis
Sent: Monday, April 18, 2016 3:55 AM
To: paraview at paraview.org
Subject: [EXTERNAL] [Paraview] Client-server mode fails with 5.0.1

Hi,

With official binaries of 5.0.1 on Linux 64-bit for both server and client nodes I get the following error directly after connecting the client:

paulm at s37n1:~/software/ParaView-5.0.1-Qt4-OpenGL2-MPI-Linux-64bit/bin$
./pvserver --use-offscreen-rendering
Waiting for client...
Connection URL: cs://s37n1.int.elvis.surfsara.nl:11111
Accepting connection(s): s37n1.int.elvis.surfsara.nl:11111 Client connected.
X Error of failed request:  BadAlloc (insufficient resources for operation)
   Major opcode of failed request:  135 (GLX)
   Minor opcode of failed request:  34 ()
   Serial number of failed request:  30
   Current serial number in output stream:  31

DISPLAY is set correctly, in glxinfo I see nothing strange, glxgears runs without issues (see below).

The message "insufficient resources" is a bit puzzling. I see no problem with other OpenGL applications. I also tried server binaries I compiled myself, but that gives the same error. Other than the EGL stuff in 5.0 is there something different in the way ParaView is trying to initialize OpenGL/GLX that could cause the above error?

Regards,
Paul


paulm at s37n1:~$ glxgears
Running synchronized to the vertical refresh.  The framerate should be approximately the same as the monitor refresh rate.
86354 frames in 5.0 seconds = 17270.654 FPS
96998 frames in 5.0 seconds = 19399.479 FPS ^C


paulm at s37n1:~$ glxgears
name of display: :0.0
display: :0  screen: 0
direct rendering: Yes
server glx vendor string: NVIDIA Corporation server glx version string: 1.4 server glx extensions:
     GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_SGIX_fbconfig,
     GLX_SGIX_pbuffer, GLX_SGI_video_sync, GLX_SGI_swap_control,
     GLX_EXT_swap_control, GLX_EXT_swap_control_tear,
     GLX_EXT_texture_from_pixmap, GLX_EXT_buffer_age, GLX_ARB_create_context,
     GLX_ARB_create_context_profile, GLX_EXT_create_context_es_profile,
     GLX_EXT_create_context_es2_profile, GLX_ARB_create_context_robustness,
     GLX_NV_delay_before_swap, GLX_EXT_stereo_tree,
     GLX_ARB_context_flush_control, GLX_ARB_multisample, GLX_NV_float_buffer,
     GLX_ARB_fbconfig_float, GLX_EXT_framebuffer_sRGB,
     GLX_NV_multisample_coverage, GLX_NV_copy_image client glx vendor string: NVIDIA Corporation client glx version string: 1.4 client glx extensions:
     GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_visual_info,
     GLX_EXT_visual_rating, GLX_EXT_import_context, GLX_SGI_video_sync,
     GLX_NV_swap_group, GLX_NV_video_out, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer,
     GLX_SGI_swap_control, GLX_EXT_swap_control, GLX_EXT_swap_control_tear,
     GLX_EXT_buffer_age, GLX_ARB_create_context,
     GLX_ARB_create_context_profile, GLX_NV_float_buffer,
     GLX_ARB_fbconfig_float, GLX_EXT_fbconfig_packed_float,
     GLX_EXT_texture_from_pixmap, GLX_EXT_framebuffer_sRGB,
     GLX_NV_present_video, GLX_NV_copy_image, GLX_NV_copy_buffer,
     GLX_NV_multisample_coverage, GLX_NV_video_capture,
     GLX_EXT_create_context_es_profile, GLX_EXT_create_context_es2_profile,
     GLX_ARB_create_context_robustness, GLX_NV_delay_before_swap,
     GLX_EXT_stereo_tree, GLX_ARB_context_flush_control GLX version: 1.4 GLX extensions:
     GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_SGIX_fbconfig,
     GLX_SGIX_pbuffer, GLX_SGI_video_sync, GLX_SGI_swap_control,
     GLX_EXT_swap_control, GLX_EXT_swap_control_tear,
     GLX_EXT_texture_from_pixmap, GLX_EXT_buffer_age, GLX_ARB_create_context,
     GLX_ARB_create_context_profile, GLX_EXT_create_context_es_profile,
     GLX_EXT_create_context_es2_profile, GLX_ARB_create_context_robustness,
     GLX_NV_delay_before_swap, GLX_EXT_stereo_tree,
     GLX_ARB_context_flush_control, GLX_ARB_multisample, GLX_NV_float_buffer,
     GLX_ARB_fbconfig_float, GLX_EXT_framebuffer_sRGB,
     GLX_NV_multisample_coverage, GLX_NV_copy_image, GLX_ARB_get_proc_address OpenGL vendor string: NVIDIA Corporation OpenGL renderer string: GeForce GTX 780 Ti/PCIe/SSE2 OpenGL version string: 4.5.0 NVIDIA 361.28 OpenGL extensions:
     GL_AMD_multi_draw_indirect, GL_AMD_seamless_cubemap_per_texture,
     GL_ARB_arrays_of_arrays, GL_ARB_base_instance, GL_ARB_bindless_texture,
     GL_ARB_blend_func_extended, GL_ARB_buffer_storage,
     GL_ARB_clear_buffer_object, GL_ARB_clear_texture, GL_ARB_clip_control,
     GL_ARB_color_buffer_float, GL_ARB_compatibility,
     GL_ARB_compressed_texture_pixel_storage, GL_ARB_conservative_depth,
     GL_ARB_compute_shader, GL_ARB_compute_variable_group_size,
     GL_ARB_conditional_render_inverted, GL_ARB_copy_buffer, GL_ARB_copy_image,
     GL_ARB_cull_distance, GL_ARB_debug_output, GL_ARB_depth_buffer_float,
     GL_ARB_depth_clamp, GL_ARB_depth_texture, GL_ARB_derivative_control,
     GL_ARB_direct_state_access, GL_ARB_draw_buffers,
     GL_ARB_draw_buffers_blend, GL_ARB_draw_indirect,
     GL_ARB_draw_elements_base_vertex, GL_ARB_draw_instanced,
     GL_ARB_enhanced_layouts, GL_ARB_ES2_compatibility,
     GL_ARB_ES3_compatibility, GL_ARB_ES3_1_compatibility, ....







-- 

Paul Melis
| Visualization group leader & developer | SURFsara | Science Park 140 | 
| 1098 XG Amsterdam | T 020 800 1312 | paul.melis at surfsara.nl | 
| www.surfsara.nl |
_______________________________________________
Powered by www.kitware.com

Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView

Search the list archives at: http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview

From paul.melis at surfsara.nl  Mon Apr 18 14:01:11 2016
From: paul.melis at surfsara.nl (Paul Melis)
Date: Mon, 18 Apr 2016 20:01:11 +0200
Subject: [Paraview] [EXTERNAL]  Client-server mode fails with 5.0.1
In-Reply-To: <c207754961194fd8a69e48f1b9f7f683@ES01AMSNLNT.srn.sandia.gov>
References: <5714AED6.5080101@surfsara.nl>
 <c207754961194fd8a69e48f1b9f7f683@ES01AMSNLNT.srn.sandia.gov>
Message-ID: <571520E7.80300@surfsara.nl>

Hi Alan,

On 04/18/2016 06:48 PM, Scott, W Alan wrote:
> Paul,
> Ssh -X is not working with newest ParaView.  X forwarding does not support the needed version of OpenGL for ParaView 5.0.1.
>
> Could that be your problem?
Err, I'm not sure where the X forwarding suddenly comes from, or why you 
would want to use it in ParaView client-server mode? I'm simply running 
the client locally on my workstation and one or more server processes on 
our render cluster. This has always worked for me with earlier versions 
of ParaView, but something seems to have changed. It could be the newer 
NVidia driver we use since a few weeks, but like I said, I don't see 
issues with any other OpenGL application.

Paul

>
> Alan
>
> -----Original Message-----
> From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Paul Melis
> Sent: Monday, April 18, 2016 3:55 AM
> To: paraview at paraview.org
> Subject: [EXTERNAL] [Paraview] Client-server mode fails with 5.0.1
>
> Hi,
>
> With official binaries of 5.0.1 on Linux 64-bit for both server and client nodes I get the following error directly after connecting the client:
>
> paulm at s37n1:~/software/ParaView-5.0.1-Qt4-OpenGL2-MPI-Linux-64bit/bin$
> ./pvserver --use-offscreen-rendering
> Waiting for client...
> Connection URL: cs://s37n1.int.elvis.surfsara.nl:11111
> Accepting connection(s): s37n1.int.elvis.surfsara.nl:11111 Client connected.
> X Error of failed request:  BadAlloc (insufficient resources for operation)
>     Major opcode of failed request:  135 (GLX)
>     Minor opcode of failed request:  34 ()
>     Serial number of failed request:  30
>     Current serial number in output stream:  31
>
> DISPLAY is set correctly, in glxinfo I see nothing strange, glxgears runs without issues (see below).
>
> The message "insufficient resources" is a bit puzzling. I see no problem with other OpenGL applications. I also tried server binaries I compiled myself, but that gives the same error. Other than the EGL stuff in 5.0 is there something different in the way ParaView is trying to initialize OpenGL/GLX that could cause the above error?
>
> Regards,
> Paul
>
>
> paulm at s37n1:~$ glxgears
> Running synchronized to the vertical refresh.  The framerate should be approximately the same as the monitor refresh rate.
> 86354 frames in 5.0 seconds = 17270.654 FPS
> 96998 frames in 5.0 seconds = 19399.479 FPS ^C
>
>
> paulm at s37n1:~$ glxgears
> name of display: :0.0
> display: :0  screen: 0
> direct rendering: Yes
> server glx vendor string: NVIDIA Corporation server glx version string: 1.4 server glx extensions:
>       GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_SGIX_fbconfig,
>       GLX_SGIX_pbuffer, GLX_SGI_video_sync, GLX_SGI_swap_control,
>       GLX_EXT_swap_control, GLX_EXT_swap_control_tear,
>       GLX_EXT_texture_from_pixmap, GLX_EXT_buffer_age, GLX_ARB_create_context,
>       GLX_ARB_create_context_profile, GLX_EXT_create_context_es_profile,
>       GLX_EXT_create_context_es2_profile, GLX_ARB_create_context_robustness,
>       GLX_NV_delay_before_swap, GLX_EXT_stereo_tree,
>       GLX_ARB_context_flush_control, GLX_ARB_multisample, GLX_NV_float_buffer,
>       GLX_ARB_fbconfig_float, GLX_EXT_framebuffer_sRGB,
>       GLX_NV_multisample_coverage, GLX_NV_copy_image client glx vendor string: NVIDIA Corporation client glx version string: 1.4 client glx extensions:
>       GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_visual_info,
>       GLX_EXT_visual_rating, GLX_EXT_import_context, GLX_SGI_video_sync,
>       GLX_NV_swap_group, GLX_NV_video_out, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer,
>       GLX_SGI_swap_control, GLX_EXT_swap_control, GLX_EXT_swap_control_tear,
>       GLX_EXT_buffer_age, GLX_ARB_create_context,
>       GLX_ARB_create_context_profile, GLX_NV_float_buffer,
>       GLX_ARB_fbconfig_float, GLX_EXT_fbconfig_packed_float,
>       GLX_EXT_texture_from_pixmap, GLX_EXT_framebuffer_sRGB,
>       GLX_NV_present_video, GLX_NV_copy_image, GLX_NV_copy_buffer,
>       GLX_NV_multisample_coverage, GLX_NV_video_capture,
>       GLX_EXT_create_context_es_profile, GLX_EXT_create_context_es2_profile,
>       GLX_ARB_create_context_robustness, GLX_NV_delay_before_swap,
>       GLX_EXT_stereo_tree, GLX_ARB_context_flush_control GLX version: 1.4 GLX extensions:
>       GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_SGIX_fbconfig,
>       GLX_SGIX_pbuffer, GLX_SGI_video_sync, GLX_SGI_swap_control,
>       GLX_EXT_swap_control, GLX_EXT_swap_control_tear,
>       GLX_EXT_texture_from_pixmap, GLX_EXT_buffer_age, GLX_ARB_create_context,
>       GLX_ARB_create_context_profile, GLX_EXT_create_context_es_profile,
>       GLX_EXT_create_context_es2_profile, GLX_ARB_create_context_robustness,
>       GLX_NV_delay_before_swap, GLX_EXT_stereo_tree,
>       GLX_ARB_context_flush_control, GLX_ARB_multisample, GLX_NV_float_buffer,
>       GLX_ARB_fbconfig_float, GLX_EXT_framebuffer_sRGB,
>       GLX_NV_multisample_coverage, GLX_NV_copy_image, GLX_ARB_get_proc_address OpenGL vendor string: NVIDIA Corporation OpenGL renderer string: GeForce GTX 780 Ti/PCIe/SSE2 OpenGL version string: 4.5.0 NVIDIA 361.28 OpenGL extensions:
>       GL_AMD_multi_draw_indirect, GL_AMD_seamless_cubemap_per_texture,
>       GL_ARB_arrays_of_arrays, GL_ARB_base_instance, GL_ARB_bindless_texture,
>       GL_ARB_blend_func_extended, GL_ARB_buffer_storage,
>       GL_ARB_clear_buffer_object, GL_ARB_clear_texture, GL_ARB_clip_control,
>       GL_ARB_color_buffer_float, GL_ARB_compatibility,
>       GL_ARB_compressed_texture_pixel_storage, GL_ARB_conservative_depth,
>       GL_ARB_compute_shader, GL_ARB_compute_variable_group_size,
>       GL_ARB_conditional_render_inverted, GL_ARB_copy_buffer, GL_ARB_copy_image,
>       GL_ARB_cull_distance, GL_ARB_debug_output, GL_ARB_depth_buffer_float,
>       GL_ARB_depth_clamp, GL_ARB_depth_texture, GL_ARB_derivative_control,
>       GL_ARB_direct_state_access, GL_ARB_draw_buffers,
>       GL_ARB_draw_buffers_blend, GL_ARB_draw_indirect,
>       GL_ARB_draw_elements_base_vertex, GL_ARB_draw_instanced,
>       GL_ARB_enhanced_layouts, GL_ARB_ES2_compatibility,
>       GL_ARB_ES3_compatibility, GL_ARB_ES3_1_compatibility, ....
>
>
>
>
>
>
>


-- 

Paul Melis
| Visualization group leader & developer | SURFsara |
| Science Park 140 | 1098 XG Amsterdam |
| T 020 800 1312 | paul.melis at surfsara.nl | www.surfsara.nl |


From utkarsh.ayachit at kitware.com  Mon Apr 18 14:04:53 2016
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Mon, 18 Apr 2016 14:04:53 -0400
Subject: [Paraview] [EXTERNAL] Client-server mode fails with 5.0.1
In-Reply-To: <571520E7.80300@surfsara.nl>
References: <5714AED6.5080101@surfsara.nl>
 <c207754961194fd8a69e48f1b9f7f683@ES01AMSNLNT.srn.sandia.gov>
 <571520E7.80300@surfsara.nl>
Message-ID: <CADHSJjD69fa_HaK3x9DuGTpuThqrsZxLwTCLaEcv8s0raMkJHw@mail.gmail.com>

> This has always worked for me with earlier versions of
> ParaView, but something seems to have changed. It could be the newer NVidia
> driver we use since a few weeks, but like I said, I don't see issues with
> any other OpenGL application.

Paul, can you try with ParaView 5.0.0 and 4.4 binaries as well? Since
those worked before, let's see if it's a NVIdia driver change that's
affecting ParaView.

From Mark.Stock at nrel.gov  Mon Apr 18 15:33:46 2016
From: Mark.Stock at nrel.gov (Stock, Mark)
Date: Mon, 18 Apr 2016 19:33:46 +0000
Subject: [Paraview] VRUI vs. VRPN
In-Reply-To: <CAA7GnUkxS11pMrsFe1_x+5KWNjQFo3iiOKRg+knWpeEYd68g6g@mail.gmail.com>
References: <CAA7GnUkxS11pMrsFe1_x+5KWNjQFo3iiOKRg+knWpeEYd68g6g@mail.gmail.com>
Message-ID: <D33A9205.2D81%Mark.Stock@nrel.gov>

Faiz,

We use both at NREL, but have had a much easier time with VRPN; not only with setting things up for ParaView integration, but also with stability. Ultimately, your choice should depend on which system your trackers and devices will interface with more easily.

Mark

From: ParaView <paraview-bounces at paraview.org<mailto:paraview-bounces at paraview.org>> on behalf of Faiz Abidi <fabidi89 at vt.edu<mailto:fabidi89 at vt.edu>>
Date: Saturday, April 16, 2016 at 11:31 AM
To: "paraview at paraview.org<mailto:paraview at paraview.org>" <paraview at paraview.org<mailto:paraview at paraview.org>>
Subject: [Paraview] VRUI vs. VRPN

Hi guys,

Wondering if there are any advantages/disadvantages of using one over the other. We have Paraview5.0 running on Ubuntu driving a 4 walled CAVE. Any suggestions?
--
Faiz Abidi | Master's Student at Virginia Tech | www.faizabidi.com<http://www.faizabidi.com> | +1-540-998-6636

From fabidi89 at vt.edu  Mon Apr 18 18:25:20 2016
From: fabidi89 at vt.edu (Faiz Abidi)
Date: Mon, 18 Apr 2016 18:25:20 -0400
Subject: [Paraview] VRUI vs. VRPN
In-Reply-To: <D33A9205.2D81%Mark.Stock@nrel.gov>
References: <CAA7GnUkxS11pMrsFe1_x+5KWNjQFo3iiOKRg+knWpeEYd68g6g@mail.gmail.com>
 <D33A9205.2D81%Mark.Stock@nrel.gov>
Message-ID: <CAA7GnUno3mUZHrW=xFjFfSZmDhjAPdrQV4EsmE7GhrYco9FdBg@mail.gmail.com>

Thanks for your input, Mark. I think we'll go ahead with VRPN as well. FYI,
we use DTK <https://github.com/lanceman2/diverse> for tracking for
InstantReality.

On Mon, Apr 18, 2016 at 3:33 PM, Stock, Mark <Mark.Stock at nrel.gov> wrote:

> Faiz,
>
> We use both at NREL, but have had a much easier time with VRPN; not only
> with setting things up for ParaView integration, but also with stability.
> Ultimately, your choice should depend on which system your trackers and
> devices will interface with more easily.
>
> Mark
>
> From: ParaView <paraview-bounces at paraview.org<mailto:
> paraview-bounces at paraview.org>> on behalf of Faiz Abidi <fabidi89 at vt.edu
> <mailto:fabidi89 at vt.edu>>
> Date: Saturday, April 16, 2016 at 11:31 AM
> To: "paraview at paraview.org<mailto:paraview at paraview.org>" <
> paraview at paraview.org<mailto:paraview at paraview.org>>
> Subject: [Paraview] VRUI vs. VRPN
>
> Hi guys,
>
> Wondering if there are any advantages/disadvantages of using one over the
> other. We have Paraview5.0 running on Ubuntu driving a 4 walled CAVE. Any
> suggestions?
> --
> Faiz Abidi | Master's Student at Virginia Tech | www.faizabidi.com<
> http://www.faizabidi.com> | +1-540-998-6636
>



-- 
Faiz Abidi | Master's Student at Virginia Tech | www.faizabidi.com |
+1-540-998-6636
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160418/562995e4/attachment.html>

From masood.molaei at gmail.com  Tue Apr 19 00:48:45 2016
From: masood.molaei at gmail.com (masood molaei)
Date: Tue, 19 Apr 2016 08:18:45 +0330
Subject: [Paraview] Problem With Running in Win 7
Message-ID: <CADQW_qyVXACjOXxJVzX-AqE1Uukr9rYLAMhHdTArAteNR86Xdg@mail.gmail.com>

Dear Sir,

I am a beginner to ParaView. I have installed
"ParaView-5.0.1-Qt4-OpenGL2-MPI-Windows-64bit" on Win 7 x64. However,
It is not run properly and a window of "check for online solution" is
appeared at the beginning. A picture of this error is attached to the
e-mail. I should mention "Microsoft visual Studio+SP" has been
installed on the Windows. Could you please help me to solve this
problem? Thank you very much.

Bests,
Masoud Molaei
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Problem.jpg
Type: image/jpeg
Size: 63874 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160419/01dbc831/attachment.jpg>

From vincent.bosquier at nice-software.com  Tue Apr 19 03:31:13 2016
From: vincent.bosquier at nice-software.com (Vincent BOSQUIER)
Date: Tue, 19 Apr 2016 09:31:13 +0200
Subject: [Paraview] Error 134 when opening ParaView
Message-ID: <5715DEC1.9070706@nice-software.com>

Hi,

I'm using ParaView v4.4 and I have experienced an error code 134 when 
opening the application.
Can anyone tell me what this error is about?
Best regards,

Vincent.

*Vincent BOSQUIER
*HPC & Visualization Architect
NICE Software.

vincent.bosquier at nice-software.com 
<mailto:vincent.bosquier at nice-software.com>
Visit NICE at www.nice-software.com <http://www.nice-software.com/>


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160419/f98ac7a3/attachment.html>

From harald at klimachs.de  Tue Apr 19 03:36:16 2016
From: harald at klimachs.de (Harald Klimach)
Date: Tue, 19 Apr 2016 09:36:16 +0200
Subject: [Paraview] Segfault with OpenGL2
In-Reply-To: <B4D4E337-E9DA-42E1-A6E9-DFCCB500E61A@klimachs.de>
References: <84D39543-ADC1-4210-A8D8-7D230A61D6AC@klimachs.de>
 <CANXz0SYsU8YyTSjKZiF3DuNSLnBOq9h9UQwp7CTgmg-8o8vjQA@mail.gmail.com>
 <CAOXZzG72H0LfFw6V1WztJC30eHjMhPY0JBeP7shQHbfDW7jbZg@mail.gmail.com>
 <53626D34-B441-4AB5-ABEC-90F12DB91A03@klimachs.de>
 <CAOXZzG7p56p9Nn57RXTs+yXMjDKVZEJoj--0VkK77tog+7Sdew@mail.gmail.com>
 <F18A2721-CB6F-492B-B542-5A747FE0FFD2@klimachs.de>
 <CAOXZzG4jytRe=p0nWZDzwPeUr4QFkv_c=Mac_0MY8xD3wQV0sA@mail.gmail.com>
 <E844436F-0040-47CD-8DC4-40785908B0B0@klimachs.de>
 <CAOXZzG4o0us2L14MMJMJO6iUL8zWXOMaSeLbGe3Vr9jE478jGQ@mail.gmail.com>
 <CD101372-6D18-45C0-B5F3-F752897AF032@klimachs.de>
 <B4D4E337-E9DA-42E1-A6E9-DFCCB500E61A@klimachs.de>
Message-ID: <AF83956E-32A5-4E33-B43A-E26CFB5F628C@klimachs.de>

Hi,

just to round this thread up:

The problem with the limited screen (the ungarbled output is VGA 640x480) can be resolved by
using offscreen rendering, so I guess this is somewhat related to the graphics card, though the
connection information still shows the nvidia card being used in that case.

However, there are two systems where the complete screen is garbled. Even when using
offscreen rendering on the pvserver side. For those I needed to fallback to x2go and VirtualGL,
and I am now using the precompiled binaries. Those do not exhibit the segmentation fault that
I observed with the self-compiled version. The main difference seems to be the usage of Qt5.

Thus, I guess the formerly observed segfault is related to some interaction between Qt5 and the
OpenGL2 rendering.

Best,
Harald

> Am 13.04.2016 um 12:44 schrieb Harald Klimach <harald at klimachs.de>:
> 
> The X+OpenGL2 via pvserver works fine for me now.
> However, my colleagues with older local laptops do have some trouble.
> 
> My local system uses:
> OpenGL Version 4.1 INTEL-10.6.33
> OpenGL Renderer Intel Iris Graphics 6100
> 
> This works nicely.
> 
> With an older graphics card like:
> OpenGL Version 3.3 INTEL-10.0.40
> OpenGL Renderer Intel HD Graphics 3000 OpenGL Engine
> 
> There is only a small 3D screen section that is actually usable, the rest of the screen has garbled output.
> The Legend can be displayed correctly on top of the garbled 3D content, and when rotating or moving the
> geometry also the complete scenery is correctly shown. As soon as the 3D scenery is still, there are
> parts of the screen garbled.
> 
> When going back to the legacy OpenGL backend on the server, both kinds of clients
> die when trying to render a 3D object.
> 
>> Am 12.04.2016 um 22:42 schrieb Harald Klimach <harald at klimachs.de>:
>> 
>>> Unfortunately I suspect this is an issue with NVIDIA driver. Their EGL support is still brand new and currently seems to be fairly brittle between driver releases so perhaps best to wait until it settles a bit and just stick with X for now :-(.  Are you able to use the X+OpenGL2 (i.e. no egl)  pvserver for remote rendering?
>> 
>> Yes, as reported in http://paraview.markmail.org/thread/c46ycyk3db4spov4, this
>> option seems to work. One weird thing I observed is the different OpenGL version
>> strings reported when using OpenGL2+EGL.
>> 
>> X+OpenGL2 is perfectly fine, I?ll test this a little more extensively.
>> Thanks a lot for bearing with me!
>> 
>> Harald
>> _______________________________________________
>> Powered by www.kitware.com
>> 
>> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html
>> 
>> Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView
>> 
>> Search the list archives at: http://markmail.org/search/?q=ParaView
>> 
>> Follow this link to subscribe/unsubscribe:
>> http://public.kitware.com/mailman/listinfo/paraview
> 
> _______________________________________________
> Powered by www.kitware.com
> 
> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html
> 
> Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView
> 
> Search the list archives at: http://markmail.org/search/?q=ParaView
> 
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview


From m.schlottke-lakemper at aia.rwth-aachen.de  Tue Apr 19 04:00:45 2016
From: m.schlottke-lakemper at aia.rwth-aachen.de (Schlottke-Lakemper, Michael)
Date: Tue, 19 Apr 2016 08:00:45 +0000
Subject: [Paraview] Store defaults for "Save data..." with CSV data
Message-ID: <1943FB0A-57D9-4D62-8E4E-ED08A397F763@aia.rwth-aachen.de>

Hi folks,

Is there a possibility to store the defaults when saving data as CSV (e.g. from the Plot over line filter)? Right now I always have to confirm that data is gathered on a single process before saving and I have to set the precision and scientific notation options manually. Preferably in PV, but if there is a config file I can edit, I?d be happy as well.

Yours

Michael


--
Michael Schlottke-Lakemper

Chair of Fluid Mechanics and Institute of Aerodynamics
RWTH Aachen University
W?llnerstra?e 5a
52062 Aachen
Germany

Phone: +49 (241) 80 95188
Fax: +49 (241) 80 92257
Mail: m.schlottke-lakemper at aia.rwth-aachen.de<mailto:m.schlottke-lakemper at aia.rwth-aachen.de>
Web: http://www.aia.rwth-aachen.de

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160419/dcba775f/attachment.html>

From m.schlottke-lakemper at aia.rwth-aachen.de  Tue Apr 19 03:53:22 2016
From: m.schlottke-lakemper at aia.rwth-aachen.de (Schlottke-Lakemper, Michael)
Date: Tue, 19 Apr 2016 07:53:22 +0000
Subject: [Paraview] Export scene creates images without actual object
Message-ID: <6D6C2BF3-F871-4A25-8C13-0768B37E83E3@aia.rwth-aachen.de>

Hi folks,

When I connect with PV5 (self-compiled from source) running on OS X to a pvserver on a remote Linux machine, I have problems using the ?Export scene? feature. Whenever I try to save the current scene e.g. as PDF or EPS, the visualization object (in this case a 2D unstructured dataset) flickers on and off for 2-3 times and then stays hidden. When I look at the generated PDF/EPS, indeed, the object is not there either. I can make it reappear in PV if I hide-unhide the object in the pipeline browser, but of course this does not help with the exported file. Strangely enough, the color bar is not affected, i.e., in the exported PDF/EPS file I end up with a lonely color bar on an otherwise empty grey background.

Any idea what I have to do to be able to again create EPS/PDF files?

Thanks a lot in advance

Michael


--
Michael Schlottke-Lakemper

Chair of Fluid Mechanics and Institute of Aerodynamics
RWTH Aachen University
W?llnerstra?e 5a
52062 Aachen
Germany

Phone: +49 (241) 80 95188
Fax: +49 (241) 80 92257
Mail: m.schlottke-lakemper at aia.rwth-aachen.de<mailto:m.schlottke-lakemper at aia.rwth-aachen.de>
Web: http://www.aia.rwth-aachen.de

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160419/684d9b42/attachment.html>

From paul.melis at surfsara.nl  Tue Apr 19 07:04:26 2016
From: paul.melis at surfsara.nl (Paul Melis)
Date: Tue, 19 Apr 2016 13:04:26 +0200
Subject: [Paraview] [EXTERNAL] Client-server mode fails with 5.0.1
In-Reply-To: <CADHSJjD69fa_HaK3x9DuGTpuThqrsZxLwTCLaEcv8s0raMkJHw@mail.gmail.com>
References: <5714AED6.5080101@surfsara.nl>
 <c207754961194fd8a69e48f1b9f7f683@ES01AMSNLNT.srn.sandia.gov>
 <571520E7.80300@surfsara.nl>
 <CADHSJjD69fa_HaK3x9DuGTpuThqrsZxLwTCLaEcv8s0raMkJHw@mail.gmail.com>
Message-ID: <571610BA.4080406@surfsara.nl>

Hi Utkarsh,

On 18-04-16 20:04, Utkarsh Ayachit wrote:
>> This has always worked for me with earlier versions of
>> ParaView, but something seems to have changed. It could be the newer NVidia
>> driver we use since a few weeks, but like I said, I don't see issues with
>> any other OpenGL application.
>
> Paul, can you try with ParaView 5.0.0 and 4.4 binaries as well? Since
> those worked before, let's see if it's a NVIdia driver change that's
> affecting ParaView.

4.4 works without problem in client-server mode (although I can't seem 
to get subsampled rendering during interaction working, no matter what 
remote render settings I try). 5.0.0 shows the same GLX-related issue as 
5.0.1.

It smells like an interaction between the new OpenGL2 backend and the 
NVidia driver we use (361.28): I tested 5.0.1 on my workstation (running 
both client and server there) with driver 364.16 and there it works 
without a problem. A test between my workstation (PV client) and a 
different machine (PV server) with driver 352.79 also works.

Paul

-- 

Paul Melis
| Visualization group leader & developer | SURFsara |
| Science Park 140 | 1098 XG Amsterdam |
| T 020 800 1312 | paul.melis at surfsara.nl | www.surfsara.nl |

From Mandar.Shirke at infosys.com  Tue Apr 19 07:15:18 2016
From: Mandar.Shirke at infosys.com (Mandar Prakash Shirke)
Date: Tue, 19 Apr 2016 11:15:18 +0000
Subject: [Paraview] Error in Launching Paraview 5.0.0
Message-ID: <BBF23853DD0BE54FB8F0F12A6F06A1DA3705256D@blrkecmbx15.ad.infosys.com>

Hello,

I have been trying to install Paraview (5.0.0_64b) but after installation, application does not launch. It says "Paraview.exe has stopped working". Please find below screenshot.
[cid:image001.png at 01D19A5A.DA9C5E30]

I tried Paraview 4.1 & Paraview 3.12 & both are running fine. I am getting this error only for Paraview 5.0.

Please suggest a solution.

Regards,
Mandar
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160419/8b3d7548/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 134462 bytes
Desc: image001.png
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160419/8b3d7548/attachment-0001.png>

From archaerolog at mail.ru  Tue Apr 19 08:02:14 2016
From: archaerolog at mail.ru (Gena Bug)
Date: Tue, 19 Apr 2016 15:02:14 +0300
Subject: [Paraview]  negative value for a vector' magnitude
Message-ID: <57161E46.7030706@mail.ru>

Hi,

I noticed that visualizing a vector' magnitude is incorrect -- minimum 
value in the range of values is negative. It happens when using 
AngularPeriodicFilter (see example in the attachment).

OS: Debian testing amd64
PV: v.5.0.1 downloaded from the site
-------------- next part --------------
<ParaView>
  <ServerManagerState version="5.0.1">
    <Proxy group="animation" type="AnimationScene" id="263" servers="16">
      <Property name="AnimationTime" id="263.AnimationTime" number_of_elements="1">
        <Element index="0" value="0"/>
      </Property>
      <Property name="Cues" id="263.Cues" number_of_elements="1">
        <Proxy value="265"/>
        <Domain name="groups" id="263.Cues.groups"/>
      </Property>
      <Property name="Duration" id="263.Duration" number_of_elements="1">
        <Element index="0" value="10"/>
      </Property>
      <Property name="EndTime" id="263.EndTime" number_of_elements="1">
        <Element index="0" value="1"/>
      </Property>
      <Property name="FramesPerTimestep" id="263.FramesPerTimestep" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="263.FramesPerTimestep.range"/>
      </Property>
      <Property name="GoToFirst" id="263.GoToFirst"/>
      <Property name="GoToLast" id="263.GoToLast"/>
      <Property name="GoToNext" id="263.GoToNext"/>
      <Property name="GoToPrevious" id="263.GoToPrevious"/>
      <Property name="LockEndTime" id="263.LockEndTime" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="263.LockEndTime.bool"/>
      </Property>
      <Property name="LockStartTime" id="263.LockStartTime" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="263.LockStartTime.bool"/>
      </Property>
      <Property name="Loop" id="263.Loop" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="263.Loop.bool"/>
      </Property>
      <Property name="NumberOfFrames" id="263.NumberOfFrames" number_of_elements="1">
        <Element index="0" value="10"/>
        <Domain name="range" id="263.NumberOfFrames.range"/>
      </Property>
      <Property name="Play" id="263.Play"/>
      <Property name="PlayMode" id="263.PlayMode" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="enum" id="263.PlayMode.enum">
          <Entry value="0" text="Sequence"/>
          <Entry value="1" text="Real Time"/>
          <Entry value="2" text="Snap To TimeSteps"/>
        </Domain>
      </Property>
      <Property name="StartTime" id="263.StartTime" number_of_elements="1">
        <Element index="0" value="0"/>
      </Property>
      <Property name="Stop" id="263.Stop"/>
      <Property name="TimeKeeper" id="263.TimeKeeper" number_of_elements="1">
        <Proxy value="259"/>
      </Property>
      <Property name="ViewModules" id="263.ViewModules" number_of_elements="2">
        <Proxy value="4720"/>
        <Proxy value="4720"/>
        <Domain name="groups" id="263.ViewModules.groups"/>
      </Property>
    </Proxy>
    <Proxy group="animation" type="TimeAnimationCue" id="265" servers="16">
      <Property name="AnimatedDomainName" id="265.AnimatedDomainName" number_of_elements="1">
        <Element index="0" value=""/>
      </Property>
      <Property name="AnimatedElement" id="265.AnimatedElement" number_of_elements="1">
        <Element index="0" value="0"/>
      </Property>
      <Property name="AnimatedPropertyName" id="265.AnimatedPropertyName" number_of_elements="1">
        <Element index="0" value="Time"/>
      </Property>
      <Property name="AnimatedProxy" id="265.AnimatedProxy" number_of_elements="1">
        <Proxy value="259"/>
        <Domain name="groups" id="265.AnimatedProxy.groups"/>
      </Property>
      <Property name="Enabled" id="265.Enabled" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="265.Enabled.bool"/>
      </Property>
      <Property name="EndTime" id="265.EndTime" number_of_elements="1">
        <Element index="0" value="1"/>
      </Property>
      <Property name="KeyFrames" id="265.KeyFrames">
        <Domain name="groups" id="265.KeyFrames.groups"/>
      </Property>
      <Property name="LastAddedKeyFrameIndex" id="265.LastAddedKeyFrameIndex"/>
      <Property name="StartTime" id="265.StartTime" number_of_elements="1">
        <Element index="0" value="0"/>
      </Property>
      <Property name="TimeMode" id="265.TimeMode" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="enum" id="265.TimeMode.enum">
          <Entry value="0" text="Normalized"/>
          <Entry value="1" text="Relative"/>
        </Domain>
      </Property>
      <Property name="UseAnimationTime" id="265.UseAnimationTime" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="265.UseAnimationTime.bool"/>
      </Property>
    </Proxy>
    <Proxy group="misc" type="ViewLayout" id="2874" servers="16">
      <Layout number_of_elements="1">
        <Item direction="0" fraction="0.5" view="4720"/>
      </Layout>
    </Proxy>
    <Proxy group="lookup_tables" type="PVLookupTable" id="5174" servers="21">
      <Property name="AboveRangeColor" id="5174.AboveRangeColor" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="1"/>
        <Element index="2" value="1"/>
      </Property>
      <Property name="ActiveAnnotatedValues" id="5174.ActiveAnnotatedValues"/>
      <Property name="AllowDuplicateScalars" id="5174.AllowDuplicateScalars" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="5174.AllowDuplicateScalars.bool"/>
      </Property>
      <Property name="Annotations" id="5174.Annotations"/>
      <Property name="BelowRangeColor" id="5174.BelowRangeColor" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
      </Property>
      <Property name="Build" id="5174.Build"/>
      <Property name="ColorSpace" id="5174.ColorSpace" number_of_elements="1">
        <Element index="0" value="3"/>
        <Domain name="enum" id="5174.ColorSpace.enum">
          <Entry value="0" text="RGB"/>
          <Entry value="1" text="HSV"/>
          <Entry value="2" text="Lab"/>
          <Entry value="3" text="Diverging"/>
        </Domain>
      </Property>
      <Property name="Discretize" id="5174.Discretize" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="5174.Discretize.bool"/>
      </Property>
      <Property name="EnableOpacityMapping" id="5174.EnableOpacityMapping" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5174.EnableOpacityMapping.bool"/>
      </Property>
      <Property name="HSVWrap" id="5174.HSVWrap" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5174.HSVWrap.bool"/>
      </Property>
      <Property name="IndexedColors" id="5174.IndexedColors"/>
      <Property name="IndexedLookup" id="5174.IndexedLookup" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5174.IndexedLookup.bool"/>
      </Property>
      <Property name="LockScalarRange" id="5174.LockScalarRange" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5174.LockScalarRange.bool"/>
      </Property>
      <Property name="NanColor" id="5174.NanColor" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="1"/>
        <Element index="2" value="0"/>
      </Property>
      <Property name="NumberOfTableValues" id="5174.NumberOfTableValues" number_of_elements="1">
        <Element index="0" value="512"/>
        <Domain name="range" id="5174.NumberOfTableValues.range"/>
      </Property>
      <Property name="RGBPoints" id="5174.RGBPoints" number_of_elements="1024">
        <Element index="0" value="-1"/>
        <Element index="1" value="0.050383"/>
        <Element index="2" value="0.029803"/>
        <Element index="3" value="0.527975"/>
        <Element index="4" value="-0.990531454408373"/>
        <Element index="5" value="0.063536"/>
        <Element index="6" value="0.028426"/>
        <Element index="7" value="0.533124"/>
        <Element index="8" value="-0.981065323030308"/>
        <Element index="9" value="0.075353"/>
        <Element index="10" value="0.027206"/>
        <Element index="11" value="0.538007"/>
        <Element index="12" value="-0.971596777438681"/>
        <Element index="13" value="0.086222"/>
        <Element index="14" value="0.026125"/>
        <Element index="15" value="0.542658"/>
        <Element index="16" value="-0.962130646060616"/>
        <Element index="17" value="0.096379"/>
        <Element index="18" value="0.025165"/>
        <Element index="19" value="0.547103"/>
        <Element index="20" value="-0.952662100468989"/>
        <Element index="21" value="0.10598"/>
        <Element index="22" value="0.024309"/>
        <Element index="23" value="0.551368"/>
        <Element index="24" value="-0.943195969090924"/>
        <Element index="25" value="0.115124"/>
        <Element index="26" value="0.023556"/>
        <Element index="27" value="0.555468"/>
        <Element index="28" value="-0.933727423499296"/>
        <Element index="29" value="0.123903"/>
        <Element index="30" value="0.022878"/>
        <Element index="31" value="0.559423"/>
        <Element index="32" value="-0.924258877907669"/>
        <Element index="33" value="0.132381"/>
        <Element index="34" value="0.022258"/>
        <Element index="35" value="0.56325"/>
        <Element index="36" value="-0.914792746529604"/>
        <Element index="37" value="0.140603"/>
        <Element index="38" value="0.021687"/>
        <Element index="39" value="0.566959"/>
        <Element index="40" value="-0.905324200937977"/>
        <Element index="41" value="0.148607"/>
        <Element index="42" value="0.021154"/>
        <Element index="43" value="0.570562"/>
        <Element index="44" value="-0.895858069559912"/>
        <Element index="45" value="0.156421"/>
        <Element index="46" value="0.020651"/>
        <Element index="47" value="0.574065"/>
        <Element index="48" value="-0.886389523968285"/>
        <Element index="49" value="0.16407"/>
        <Element index="50" value="0.020171"/>
        <Element index="51" value="0.577478"/>
        <Element index="52" value="-0.87692339259022"/>
        <Element index="53" value="0.171574"/>
        <Element index="54" value="0.019706"/>
        <Element index="55" value="0.580806"/>
        <Element index="56" value="-0.867454846998593"/>
        <Element index="57" value="0.17895"/>
        <Element index="58" value="0.019252"/>
        <Element index="59" value="0.584054"/>
        <Element index="60" value="-0.857986301406965"/>
        <Element index="61" value="0.186213"/>
        <Element index="62" value="0.018803"/>
        <Element index="63" value="0.587228"/>
        <Element index="64" value="-0.8485201700289"/>
        <Element index="65" value="0.193374"/>
        <Element index="66" value="0.018354"/>
        <Element index="67" value="0.59033"/>
        <Element index="68" value="-0.839051624437273"/>
        <Element index="69" value="0.200445"/>
        <Element index="70" value="0.017902"/>
        <Element index="71" value="0.593364"/>
        <Element index="72" value="-0.829585493059208"/>
        <Element index="73" value="0.207435"/>
        <Element index="74" value="0.017442"/>
        <Element index="75" value="0.596333"/>
        <Element index="76" value="-0.820116947467581"/>
        <Element index="77" value="0.21435"/>
        <Element index="78" value="0.016973"/>
        <Element index="79" value="0.599239"/>
        <Element index="80" value="-0.810650816089516"/>
        <Element index="81" value="0.221197"/>
        <Element index="82" value="0.016497"/>
        <Element index="83" value="0.602083"/>
        <Element index="84" value="-0.801182270497889"/>
        <Element index="85" value="0.227983"/>
        <Element index="86" value="0.016007"/>
        <Element index="87" value="0.604867"/>
        <Element index="88" value="-0.791713724906261"/>
        <Element index="89" value="0.234715"/>
        <Element index="90" value="0.015502"/>
        <Element index="91" value="0.607592"/>
        <Element index="92" value="-0.782247593528197"/>
        <Element index="93" value="0.241396"/>
        <Element index="94" value="0.014979"/>
        <Element index="95" value="0.610259"/>
        <Element index="96" value="-0.772779047936569"/>
        <Element index="97" value="0.248032"/>
        <Element index="98" value="0.014439"/>
        <Element index="99" value="0.612868"/>
        <Element index="100" value="-0.763312916558504"/>
        <Element index="101" value="0.254627"/>
        <Element index="102" value="0.013882"/>
        <Element index="103" value="0.615419"/>
        <Element index="104" value="-0.753844370966877"/>
        <Element index="105" value="0.261183"/>
        <Element index="106" value="0.013308"/>
        <Element index="107" value="0.617911"/>
        <Element index="108" value="-0.744378239588812"/>
        <Element index="109" value="0.267703"/>
        <Element index="110" value="0.012716"/>
        <Element index="111" value="0.620346"/>
        <Element index="112" value="-0.734909693997185"/>
        <Element index="113" value="0.274191"/>
        <Element index="114" value="0.012109"/>
        <Element index="115" value="0.622722"/>
        <Element index="116" value="-0.72544356261912"/>
        <Element index="117" value="0.280648"/>
        <Element index="118" value="0.011488"/>
        <Element index="119" value="0.625038"/>
        <Element index="120" value="-0.715975017027493"/>
        <Element index="121" value="0.287076"/>
        <Element index="122" value="0.010855"/>
        <Element index="123" value="0.627295"/>
        <Element index="124" value="-0.706506471435866"/>
        <Element index="125" value="0.293478"/>
        <Element index="126" value="0.010213"/>
        <Element index="127" value="0.62949"/>
        <Element index="128" value="-0.6970403400578"/>
        <Element index="129" value="0.299855"/>
        <Element index="130" value="0.009561"/>
        <Element index="131" value="0.631624"/>
        <Element index="132" value="-0.687571794466173"/>
        <Element index="133" value="0.30621"/>
        <Element index="134" value="0.008902"/>
        <Element index="135" value="0.633694"/>
        <Element index="136" value="-0.678105663088108"/>
        <Element index="137" value="0.312543"/>
        <Element index="138" value="0.008239"/>
        <Element index="139" value="0.6357"/>
        <Element index="140" value="-0.668637117496481"/>
        <Element index="141" value="0.318856"/>
        <Element index="142" value="0.007576"/>
        <Element index="143" value="0.63764"/>
        <Element index="144" value="-0.659170986118416"/>
        <Element index="145" value="0.32515"/>
        <Element index="146" value="0.006915"/>
        <Element index="147" value="0.639512"/>
        <Element index="148" value="-0.649702440526789"/>
        <Element index="149" value="0.331426"/>
        <Element index="150" value="0.006261"/>
        <Element index="151" value="0.641316"/>
        <Element index="152" value="-0.640233894935161"/>
        <Element index="153" value="0.337683"/>
        <Element index="154" value="0.005618"/>
        <Element index="155" value="0.643049"/>
        <Element index="156" value="-0.630767763557097"/>
        <Element index="157" value="0.343925"/>
        <Element index="158" value="0.004991"/>
        <Element index="159" value="0.64471"/>
        <Element index="160" value="-0.621299217965469"/>
        <Element index="161" value="0.35015"/>
        <Element index="162" value="0.004382"/>
        <Element index="163" value="0.646298"/>
        <Element index="164" value="-0.611833086587404"/>
        <Element index="165" value="0.356359"/>
        <Element index="166" value="0.003798"/>
        <Element index="167" value="0.64781"/>
        <Element index="168" value="-0.602364540995777"/>
        <Element index="169" value="0.362553"/>
        <Element index="170" value="0.003243"/>
        <Element index="171" value="0.649245"/>
        <Element index="172" value="-0.592898409617712"/>
        <Element index="173" value="0.368733"/>
        <Element index="174" value="0.002724"/>
        <Element index="175" value="0.650601"/>
        <Element index="176" value="-0.583429864026085"/>
        <Element index="177" value="0.374897"/>
        <Element index="178" value="0.002245"/>
        <Element index="179" value="0.651876"/>
        <Element index="180" value="-0.573961318434458"/>
        <Element index="181" value="0.381047"/>
        <Element index="182" value="0.001814"/>
        <Element index="183" value="0.653068"/>
        <Element index="184" value="-0.564495187056393"/>
        <Element index="185" value="0.387183"/>
        <Element index="186" value="0.001434"/>
        <Element index="187" value="0.654177"/>
        <Element index="188" value="-0.555026641464766"/>
        <Element index="189" value="0.393304"/>
        <Element index="190" value="0.001114"/>
        <Element index="191" value="0.655199"/>
        <Element index="192" value="-0.545560510086701"/>
        <Element index="193" value="0.399411"/>
        <Element index="194" value="0.000859"/>
        <Element index="195" value="0.656133"/>
        <Element index="196" value="-0.536091964495073"/>
        <Element index="197" value="0.405503"/>
        <Element index="198" value="0.000678"/>
        <Element index="199" value="0.656977"/>
        <Element index="200" value="-0.526625833117008"/>
        <Element index="201" value="0.41158"/>
        <Element index="202" value="0.000577"/>
        <Element index="203" value="0.65773"/>
        <Element index="204" value="-0.517157287525381"/>
        <Element index="205" value="0.417642"/>
        <Element index="206" value="0.000564"/>
        <Element index="207" value="0.65839"/>
        <Element index="208" value="-0.507688741933754"/>
        <Element index="209" value="0.423689"/>
        <Element index="210" value="0.000646"/>
        <Element index="211" value="0.658956"/>
        <Element index="212" value="-0.498222610555689"/>
        <Element index="213" value="0.429719"/>
        <Element index="214" value="0.000831"/>
        <Element index="215" value="0.659425"/>
        <Element index="216" value="-0.488754064964062"/>
        <Element index="217" value="0.435734"/>
        <Element index="218" value="0.001127"/>
        <Element index="219" value="0.659797"/>
        <Element index="220" value="-0.479287933585997"/>
        <Element index="221" value="0.441732"/>
        <Element index="222" value="0.00154"/>
        <Element index="223" value="0.660069"/>
        <Element index="224" value="-0.46981938799437"/>
        <Element index="225" value="0.447714"/>
        <Element index="226" value="0.00208"/>
        <Element index="227" value="0.66024"/>
        <Element index="228" value="-0.460353256616305"/>
        <Element index="229" value="0.453677"/>
        <Element index="230" value="0.002755"/>
        <Element index="231" value="0.66031"/>
        <Element index="232" value="-0.450884711024677"/>
        <Element index="233" value="0.459623"/>
        <Element index="234" value="0.003574"/>
        <Element index="235" value="0.660277"/>
        <Element index="236" value="-0.44141616543305"/>
        <Element index="237" value="0.46555"/>
        <Element index="238" value="0.004545"/>
        <Element index="239" value="0.660139"/>
        <Element index="240" value="-0.431950034054985"/>
        <Element index="241" value="0.471457"/>
        <Element index="242" value="0.005678"/>
        <Element index="243" value="0.659897"/>
        <Element index="244" value="-0.422481488463358"/>
        <Element index="245" value="0.477344"/>
        <Element index="246" value="0.00698"/>
        <Element index="247" value="0.659549"/>
        <Element index="248" value="-0.413015357085293"/>
        <Element index="249" value="0.48321"/>
        <Element index="250" value="0.00846"/>
        <Element index="251" value="0.659095"/>
        <Element index="252" value="-0.403546811493666"/>
        <Element index="253" value="0.489055"/>
        <Element index="254" value="0.010127"/>
        <Element index="255" value="0.658534"/>
        <Element index="256" value="-0.394080680115601"/>
        <Element index="257" value="0.494877"/>
        <Element index="258" value="0.01199"/>
        <Element index="259" value="0.657865"/>
        <Element index="260" value="-0.384612134523973"/>
        <Element index="261" value="0.500678"/>
        <Element index="262" value="0.014055"/>
        <Element index="263" value="0.657088"/>
        <Element index="264" value="-0.375143588932346"/>
        <Element index="265" value="0.506454"/>
        <Element index="266" value="0.016333"/>
        <Element index="267" value="0.656202"/>
        <Element index="268" value="-0.365677457554281"/>
        <Element index="269" value="0.512206"/>
        <Element index="270" value="0.018833"/>
        <Element index="271" value="0.655209"/>
        <Element index="272" value="-0.356208911962654"/>
        <Element index="273" value="0.517933"/>
        <Element index="274" value="0.021563"/>
        <Element index="275" value="0.654109"/>
        <Element index="276" value="-0.346742780584589"/>
        <Element index="277" value="0.523633"/>
        <Element index="278" value="0.024532"/>
        <Element index="279" value="0.652901"/>
        <Element index="280" value="-0.337274234992962"/>
        <Element index="281" value="0.529306"/>
        <Element index="282" value="0.027747"/>
        <Element index="283" value="0.651586"/>
        <Element index="284" value="-0.327808103614897"/>
        <Element index="285" value="0.534952"/>
        <Element index="286" value="0.031217"/>
        <Element index="287" value="0.650165"/>
        <Element index="288" value="-0.318339558023269"/>
        <Element index="289" value="0.54057"/>
        <Element index="290" value="0.03495"/>
        <Element index="291" value="0.64864"/>
        <Element index="292" value="-0.308871012431642"/>
        <Element index="293" value="0.546157"/>
        <Element index="294" value="0.038954"/>
        <Element index="295" value="0.64701"/>
        <Element index="296" value="-0.299404881053577"/>
        <Element index="297" value="0.551715"/>
        <Element index="298" value="0.043136"/>
        <Element index="299" value="0.645277"/>
        <Element index="300" value="-0.28993633546195"/>
        <Element index="301" value="0.557243"/>
        <Element index="302" value="0.047331"/>
        <Element index="303" value="0.643443"/>
        <Element index="304" value="-0.280470204083885"/>
        <Element index="305" value="0.562738"/>
        <Element index="306" value="0.051545"/>
        <Element index="307" value="0.641509"/>
        <Element index="308" value="-0.271001658492258"/>
        <Element index="309" value="0.568201"/>
        <Element index="310" value="0.055778"/>
        <Element index="311" value="0.639477"/>
        <Element index="312" value="-0.261535527114193"/>
        <Element index="313" value="0.573632"/>
        <Element index="314" value="0.060028"/>
        <Element index="315" value="0.637349"/>
        <Element index="316" value="-0.252066981522566"/>
        <Element index="317" value="0.579029"/>
        <Element index="318" value="0.064296"/>
        <Element index="319" value="0.635126"/>
        <Element index="320" value="-0.242600850144501"/>
        <Element index="321" value="0.584391"/>
        <Element index="322" value="0.068579"/>
        <Element index="323" value="0.632812"/>
        <Element index="324" value="-0.233132304552874"/>
        <Element index="325" value="0.589719"/>
        <Element index="326" value="0.072878"/>
        <Element index="327" value="0.630408"/>
        <Element index="328" value="-0.223663758961246"/>
        <Element index="329" value="0.595011"/>
        <Element index="330" value="0.07719"/>
        <Element index="331" value="0.627917"/>
        <Element index="332" value="-0.214197627583181"/>
        <Element index="333" value="0.600266"/>
        <Element index="334" value="0.081516"/>
        <Element index="335" value="0.625342"/>
        <Element index="336" value="-0.204729081991554"/>
        <Element index="337" value="0.605485"/>
        <Element index="338" value="0.085854"/>
        <Element index="339" value="0.622686"/>
        <Element index="340" value="-0.195262950613489"/>
        <Element index="341" value="0.610667"/>
        <Element index="342" value="0.090204"/>
        <Element index="343" value="0.619951"/>
        <Element index="344" value="-0.185794405021862"/>
        <Element index="345" value="0.615812"/>
        <Element index="346" value="0.094564"/>
        <Element index="347" value="0.61714"/>
        <Element index="348" value="-0.176328273643797"/>
        <Element index="349" value="0.620919"/>
        <Element index="350" value="0.098934"/>
        <Element index="351" value="0.614257"/>
        <Element index="352" value="-0.16685972805217"/>
        <Element index="353" value="0.625987"/>
        <Element index="354" value="0.103312"/>
        <Element index="355" value="0.611305"/>
        <Element index="356" value="-0.157391182460542"/>
        <Element index="357" value="0.631017"/>
        <Element index="358" value="0.107699"/>
        <Element index="359" value="0.608287"/>
        <Element index="360" value="-0.147925051082477"/>
        <Element index="361" value="0.636008"/>
        <Element index="362" value="0.112092"/>
        <Element index="363" value="0.605205"/>
        <Element index="364" value="-0.13845650549085"/>
        <Element index="365" value="0.640959"/>
        <Element index="366" value="0.116492"/>
        <Element index="367" value="0.602065"/>
        <Element index="368" value="-0.128990374112785"/>
        <Element index="369" value="0.645872"/>
        <Element index="370" value="0.120898"/>
        <Element index="371" value="0.598867"/>
        <Element index="372" value="-0.119521828521158"/>
        <Element index="373" value="0.650746"/>
        <Element index="374" value="0.125309"/>
        <Element index="375" value="0.595617"/>
        <Element index="376" value="-0.110055697143093"/>
        <Element index="377" value="0.65558"/>
        <Element index="378" value="0.129725"/>
        <Element index="379" value="0.592317"/>
        <Element index="380" value="-0.100587151551466"/>
        <Element index="381" value="0.660374"/>
        <Element index="382" value="0.134144"/>
        <Element index="383" value="0.588971"/>
        <Element index="384" value="-0.0911186059598383"/>
        <Element index="385" value="0.665129"/>
        <Element index="386" value="0.138566"/>
        <Element index="387" value="0.585582"/>
        <Element index="388" value="-0.0816524745817735"/>
        <Element index="389" value="0.669845"/>
        <Element index="390" value="0.142992"/>
        <Element index="391" value="0.582154"/>
        <Element index="392" value="-0.0721839289901465"/>
        <Element index="393" value="0.674522"/>
        <Element index="394" value="0.147419"/>
        <Element index="395" value="0.578688"/>
        <Element index="396" value="-0.0627177976120815"/>
        <Element index="397" value="0.67916"/>
        <Element index="398" value="0.151848"/>
        <Element index="399" value="0.575189"/>
        <Element index="400" value="-0.0532492520204543"/>
        <Element index="401" value="0.683758"/>
        <Element index="402" value="0.156278"/>
        <Element index="403" value="0.57166"/>
        <Element index="404" value="-0.0437831206423894"/>
        <Element index="405" value="0.688318"/>
        <Element index="406" value="0.160709"/>
        <Element index="407" value="0.568103"/>
        <Element index="408" value="-0.0343145750507622"/>
        <Element index="409" value="0.69284"/>
        <Element index="410" value="0.165141"/>
        <Element index="411" value="0.564522"/>
        <Element index="412" value="-0.0248460294591346"/>
        <Element index="413" value="0.697324"/>
        <Element index="414" value="0.169573"/>
        <Element index="415" value="0.560919"/>
        <Element index="416" value="-0.01537989808107"/>
        <Element index="417" value="0.701769"/>
        <Element index="418" value="0.174005"/>
        <Element index="419" value="0.557296"/>
        <Element index="420" value="-0.00591135248944263"/>
        <Element index="421" value="0.706178"/>
        <Element index="422" value="0.178437"/>
        <Element index="423" value="0.553657"/>
        <Element index="424" value="0.00355477888862232"/>
        <Element index="425" value="0.710549"/>
        <Element index="426" value="0.182868"/>
        <Element index="427" value="0.550004"/>
        <Element index="428" value="0.0130233244802493"/>
        <Element index="429" value="0.714883"/>
        <Element index="430" value="0.187299"/>
        <Element index="431" value="0.546338"/>
        <Element index="432" value="0.0224894558583142"/>
        <Element index="433" value="0.719181"/>
        <Element index="434" value="0.191729"/>
        <Element index="435" value="0.542663"/>
        <Element index="436" value="0.0319580014499417"/>
        <Element index="437" value="0.723444"/>
        <Element index="438" value="0.196158"/>
        <Element index="439" value="0.538981"/>
        <Element index="440" value="0.0414265470415691"/>
        <Element index="441" value="0.72767"/>
        <Element index="442" value="0.200586"/>
        <Element index="443" value="0.535293"/>
        <Element index="444" value="0.0508926784196342"/>
        <Element index="445" value="0.731862"/>
        <Element index="446" value="0.205013"/>
        <Element index="447" value="0.531601"/>
        <Element index="448" value="0.0603612240112612"/>
        <Element index="449" value="0.736019"/>
        <Element index="450" value="0.209439"/>
        <Element index="451" value="0.527908"/>
        <Element index="452" value="0.0698273553893261"/>
        <Element index="453" value="0.740143"/>
        <Element index="454" value="0.213864"/>
        <Element index="455" value="0.524216"/>
        <Element index="456" value="0.0792959009809533"/>
        <Element index="457" value="0.744232"/>
        <Element index="458" value="0.218288"/>
        <Element index="459" value="0.520524"/>
        <Element index="460" value="0.0887620323590184"/>
        <Element index="461" value="0.748289"/>
        <Element index="462" value="0.222711"/>
        <Element index="463" value="0.516834"/>
        <Element index="464" value="0.0982305779506454"/>
        <Element index="465" value="0.752312"/>
        <Element index="466" value="0.227133"/>
        <Element index="467" value="0.513149"/>
        <Element index="468" value="0.107699123542272"/>
        <Element index="469" value="0.756304"/>
        <Element index="470" value="0.231555"/>
        <Element index="471" value="0.509468"/>
        <Element index="472" value="0.117165254920337"/>
        <Element index="473" value="0.760264"/>
        <Element index="474" value="0.235976"/>
        <Element index="475" value="0.505794"/>
        <Element index="476" value="0.126633800511965"/>
        <Element index="477" value="0.764193"/>
        <Element index="478" value="0.240396"/>
        <Element index="479" value="0.502126"/>
        <Element index="480" value="0.13609993189003"/>
        <Element index="481" value="0.76809"/>
        <Element index="482" value="0.244817"/>
        <Element index="483" value="0.498465"/>
        <Element index="484" value="0.145568477481657"/>
        <Element index="485" value="0.771958"/>
        <Element index="486" value="0.249237"/>
        <Element index="487" value="0.494813"/>
        <Element index="488" value="0.155034608859722"/>
        <Element index="489" value="0.775796"/>
        <Element index="490" value="0.253658"/>
        <Element index="491" value="0.491171"/>
        <Element index="492" value="0.16450315445135"/>
        <Element index="493" value="0.779604"/>
        <Element index="494" value="0.258078"/>
        <Element index="495" value="0.487539"/>
        <Element index="496" value="0.173971700042977"/>
        <Element index="497" value="0.783383"/>
        <Element index="498" value="0.2625"/>
        <Element index="499" value="0.483918"/>
        <Element index="500" value="0.183437831421042"/>
        <Element index="501" value="0.787133"/>
        <Element index="502" value="0.266922"/>
        <Element index="503" value="0.480307"/>
        <Element index="504" value="0.192906377012668"/>
        <Element index="505" value="0.790855"/>
        <Element index="506" value="0.271345"/>
        <Element index="507" value="0.476706"/>
        <Element index="508" value="0.202372508390734"/>
        <Element index="509" value="0.794549"/>
        <Element index="510" value="0.27577"/>
        <Element index="511" value="0.473117"/>
        <Element index="512" value="0.211841053982361"/>
        <Element index="513" value="0.798216"/>
        <Element index="514" value="0.280197"/>
        <Element index="515" value="0.469538"/>
        <Element index="516" value="0.221307185360426"/>
        <Element index="517" value="0.801855"/>
        <Element index="518" value="0.284626"/>
        <Element index="519" value="0.465971"/>
        <Element index="520" value="0.230775730952053"/>
        <Element index="521" value="0.805467"/>
        <Element index="522" value="0.289057"/>
        <Element index="523" value="0.462415"/>
        <Element index="524" value="0.240241862330118"/>
        <Element index="525" value="0.809052"/>
        <Element index="526" value="0.293491"/>
        <Element index="527" value="0.45887"/>
        <Element index="528" value="0.249710407921745"/>
        <Element index="529" value="0.812612"/>
        <Element index="530" value="0.297928"/>
        <Element index="531" value="0.455338"/>
        <Element index="532" value="0.259178953513372"/>
        <Element index="533" value="0.816144"/>
        <Element index="534" value="0.302368"/>
        <Element index="535" value="0.451816"/>
        <Element index="536" value="0.268645084891438"/>
        <Element index="537" value="0.819651"/>
        <Element index="538" value="0.306812"/>
        <Element index="539" value="0.448306"/>
        <Element index="540" value="0.278113630483065"/>
        <Element index="541" value="0.823132"/>
        <Element index="542" value="0.311261"/>
        <Element index="543" value="0.444806"/>
        <Element index="544" value="0.28757976186113"/>
        <Element index="545" value="0.826588"/>
        <Element index="546" value="0.315714"/>
        <Element index="547" value="0.441316"/>
        <Element index="548" value="0.297048307452757"/>
        <Element index="549" value="0.830018"/>
        <Element index="550" value="0.320172"/>
        <Element index="551" value="0.437836"/>
        <Element index="552" value="0.306514438830822"/>
        <Element index="553" value="0.833422"/>
        <Element index="554" value="0.324635"/>
        <Element index="555" value="0.434366"/>
        <Element index="556" value="0.315982984422449"/>
        <Element index="557" value="0.836801"/>
        <Element index="558" value="0.329105"/>
        <Element index="559" value="0.430905"/>
        <Element index="560" value="0.325451530014076"/>
        <Element index="561" value="0.840155"/>
        <Element index="562" value="0.33358"/>
        <Element index="563" value="0.427455"/>
        <Element index="564" value="0.334917661392142"/>
        <Element index="565" value="0.843484"/>
        <Element index="566" value="0.338062"/>
        <Element index="567" value="0.424013"/>
        <Element index="568" value="0.344386206983769"/>
        <Element index="569" value="0.846788"/>
        <Element index="570" value="0.342551"/>
        <Element index="571" value="0.420579"/>
        <Element index="572" value="0.353852338361833"/>
        <Element index="573" value="0.850066"/>
        <Element index="574" value="0.347048"/>
        <Element index="575" value="0.417153"/>
        <Element index="576" value="0.363320883953461"/>
        <Element index="577" value="0.853319"/>
        <Element index="578" value="0.351553"/>
        <Element index="579" value="0.413734"/>
        <Element index="580" value="0.372787015331526"/>
        <Element index="581" value="0.856547"/>
        <Element index="582" value="0.356066"/>
        <Element index="583" value="0.410322"/>
        <Element index="584" value="0.382255560923153"/>
        <Element index="585" value="0.85975"/>
        <Element index="586" value="0.360588"/>
        <Element index="587" value="0.406917"/>
        <Element index="588" value="0.39172410651478"/>
        <Element index="589" value="0.862927"/>
        <Element index="590" value="0.365119"/>
        <Element index="591" value="0.403519"/>
        <Element index="592" value="0.401190237892845"/>
        <Element index="593" value="0.866078"/>
        <Element index="594" value="0.36966"/>
        <Element index="595" value="0.400126"/>
        <Element index="596" value="0.410658783484472"/>
        <Element index="597" value="0.869203"/>
        <Element index="598" value="0.374212"/>
        <Element index="599" value="0.396738"/>
        <Element index="600" value="0.420124914862537"/>
        <Element index="601" value="0.872303"/>
        <Element index="602" value="0.378774"/>
        <Element index="603" value="0.393355"/>
        <Element index="604" value="0.429593460454165"/>
        <Element index="605" value="0.875376"/>
        <Element index="606" value="0.383347"/>
        <Element index="607" value="0.389976"/>
        <Element index="608" value="0.43905959183223"/>
        <Element index="609" value="0.878423"/>
        <Element index="610" value="0.387932"/>
        <Element index="611" value="0.3866"/>
        <Element index="612" value="0.448528137423857"/>
        <Element index="613" value="0.881443"/>
        <Element index="614" value="0.392529"/>
        <Element index="615" value="0.383229"/>
        <Element index="616" value="0.457996683015484"/>
        <Element index="617" value="0.884436"/>
        <Element index="618" value="0.397139"/>
        <Element index="619" value="0.37986"/>
        <Element index="620" value="0.467462814393549"/>
        <Element index="621" value="0.887402"/>
        <Element index="622" value="0.401762"/>
        <Element index="623" value="0.376494"/>
        <Element index="624" value="0.476931359985177"/>
        <Element index="625" value="0.89034"/>
        <Element index="626" value="0.406398"/>
        <Element index="627" value="0.37313"/>
        <Element index="628" value="0.486397491363241"/>
        <Element index="629" value="0.89325"/>
        <Element index="630" value="0.411048"/>
        <Element index="631" value="0.369768"/>
        <Element index="632" value="0.495866036954868"/>
        <Element index="633" value="0.896131"/>
        <Element index="634" value="0.415712"/>
        <Element index="635" value="0.366407"/>
        <Element index="636" value="0.505332168332933"/>
        <Element index="637" value="0.898984"/>
        <Element index="638" value="0.420392"/>
        <Element index="639" value="0.363047"/>
        <Element index="640" value="0.514800713924561"/>
        <Element index="641" value="0.901807"/>
        <Element index="642" value="0.425087"/>
        <Element index="643" value="0.359688"/>
        <Element index="644" value="0.524269259516188"/>
        <Element index="645" value="0.904601"/>
        <Element index="646" value="0.429797"/>
        <Element index="647" value="0.356329"/>
        <Element index="648" value="0.533735390894253"/>
        <Element index="649" value="0.907365"/>
        <Element index="650" value="0.434524"/>
        <Element index="651" value="0.35297"/>
        <Element index="652" value="0.54320393648588"/>
        <Element index="653" value="0.910098"/>
        <Element index="654" value="0.439268"/>
        <Element index="655" value="0.34961"/>
        <Element index="656" value="0.552670067863945"/>
        <Element index="657" value="0.9128"/>
        <Element index="658" value="0.444029"/>
        <Element index="659" value="0.346251"/>
        <Element index="660" value="0.562138613455573"/>
        <Element index="661" value="0.915471"/>
        <Element index="662" value="0.448807"/>
        <Element index="663" value="0.34289"/>
        <Element index="664" value="0.571604744833637"/>
        <Element index="665" value="0.918109"/>
        <Element index="666" value="0.453603"/>
        <Element index="667" value="0.339529"/>
        <Element index="668" value="0.581073290425265"/>
        <Element index="669" value="0.920714"/>
        <Element index="670" value="0.458417"/>
        <Element index="671" value="0.336166"/>
        <Element index="672" value="0.590541836016892"/>
        <Element index="673" value="0.923287"/>
        <Element index="674" value="0.463251"/>
        <Element index="675" value="0.332801"/>
        <Element index="676" value="0.600007967394957"/>
        <Element index="677" value="0.925825"/>
        <Element index="678" value="0.468103"/>
        <Element index="679" value="0.329435"/>
        <Element index="680" value="0.609476512986584"/>
        <Element index="681" value="0.928329"/>
        <Element index="682" value="0.472975"/>
        <Element index="683" value="0.326067"/>
        <Element index="684" value="0.618942644364649"/>
        <Element index="685" value="0.930798"/>
        <Element index="686" value="0.477867"/>
        <Element index="687" value="0.322697"/>
        <Element index="688" value="0.628411189956277"/>
        <Element index="689" value="0.933232"/>
        <Element index="690" value="0.48278"/>
        <Element index="691" value="0.319325"/>
        <Element index="692" value="0.637877321334341"/>
        <Element index="693" value="0.93563"/>
        <Element index="694" value="0.487712"/>
        <Element index="695" value="0.315952"/>
        <Element index="696" value="0.647345866925968"/>
        <Element index="697" value="0.93799"/>
        <Element index="698" value="0.492667"/>
        <Element index="699" value="0.312575"/>
        <Element index="700" value="0.656814412517595"/>
        <Element index="701" value="0.940313"/>
        <Element index="702" value="0.497642"/>
        <Element index="703" value="0.309197"/>
        <Element index="704" value="0.666280543895661"/>
        <Element index="705" value="0.942598"/>
        <Element index="706" value="0.502639"/>
        <Element index="707" value="0.305816"/>
        <Element index="708" value="0.675749089487288"/>
        <Element index="709" value="0.944844"/>
        <Element index="710" value="0.507658"/>
        <Element index="711" value="0.302433"/>
        <Element index="712" value="0.685215220865353"/>
        <Element index="713" value="0.947051"/>
        <Element index="714" value="0.512699"/>
        <Element index="715" value="0.299049"/>
        <Element index="716" value="0.69468376645698"/>
        <Element index="717" value="0.949217"/>
        <Element index="718" value="0.517763"/>
        <Element index="719" value="0.295662"/>
        <Element index="720" value="0.704149897835045"/>
        <Element index="721" value="0.951344"/>
        <Element index="722" value="0.52285"/>
        <Element index="723" value="0.292275"/>
        <Element index="724" value="0.713618443426672"/>
        <Element index="725" value="0.953428"/>
        <Element index="726" value="0.52796"/>
        <Element index="727" value="0.288883"/>
        <Element index="728" value="0.723084574804737"/>
        <Element index="729" value="0.95547"/>
        <Element index="730" value="0.533093"/>
        <Element index="731" value="0.28549"/>
        <Element index="732" value="0.732553120396365"/>
        <Element index="733" value="0.957469"/>
        <Element index="734" value="0.53825"/>
        <Element index="735" value="0.282096"/>
        <Element index="736" value="0.742021665987992"/>
        <Element index="737" value="0.959424"/>
        <Element index="738" value="0.543431"/>
        <Element index="739" value="0.278701"/>
        <Element index="740" value="0.751487797366056"/>
        <Element index="741" value="0.961336"/>
        <Element index="742" value="0.548636"/>
        <Element index="743" value="0.275305"/>
        <Element index="744" value="0.760956342957684"/>
        <Element index="745" value="0.963203"/>
        <Element index="746" value="0.553865"/>
        <Element index="747" value="0.271909"/>
        <Element index="748" value="0.77042247433575"/>
        <Element index="749" value="0.965024"/>
        <Element index="750" value="0.559118"/>
        <Element index="751" value="0.268513"/>
        <Element index="752" value="0.779891019927376"/>
        <Element index="753" value="0.966798"/>
        <Element index="754" value="0.564396"/>
        <Element index="755" value="0.265118"/>
        <Element index="756" value="0.789357151305441"/>
        <Element index="757" value="0.968526"/>
        <Element index="758" value="0.5697"/>
        <Element index="759" value="0.261721"/>
        <Element index="760" value="0.798825696897068"/>
        <Element index="761" value="0.970205"/>
        <Element index="762" value="0.575028"/>
        <Element index="763" value="0.258325"/>
        <Element index="764" value="0.808294242488695"/>
        <Element index="765" value="0.971835"/>
        <Element index="766" value="0.580382"/>
        <Element index="767" value="0.254931"/>
        <Element index="768" value="0.81776037386676"/>
        <Element index="769" value="0.973416"/>
        <Element index="770" value="0.585761"/>
        <Element index="771" value="0.25154"/>
        <Element index="772" value="0.827228919458388"/>
        <Element index="773" value="0.974947"/>
        <Element index="774" value="0.591165"/>
        <Element index="775" value="0.248151"/>
        <Element index="776" value="0.836695050836453"/>
        <Element index="777" value="0.976428"/>
        <Element index="778" value="0.596595"/>
        <Element index="779" value="0.244767"/>
        <Element index="780" value="0.84616359642808"/>
        <Element index="781" value="0.977856"/>
        <Element index="782" value="0.602051"/>
        <Element index="783" value="0.241387"/>
        <Element index="784" value="0.855629727806145"/>
        <Element index="785" value="0.979233"/>
        <Element index="786" value="0.607532"/>
        <Element index="787" value="0.238013"/>
        <Element index="788" value="0.865098273397772"/>
        <Element index="789" value="0.980556"/>
        <Element index="790" value="0.613039"/>
        <Element index="791" value="0.234646"/>
        <Element index="792" value="0.8745668189894"/>
        <Element index="793" value="0.981826"/>
        <Element index="794" value="0.618572"/>
        <Element index="795" value="0.231287"/>
        <Element index="796" value="0.884032950367464"/>
        <Element index="797" value="0.983041"/>
        <Element index="798" value="0.624131"/>
        <Element index="799" value="0.227937"/>
        <Element index="800" value="0.893501495959092"/>
        <Element index="801" value="0.984199"/>
        <Element index="802" value="0.629718"/>
        <Element index="803" value="0.224595"/>
        <Element index="804" value="0.902967627337157"/>
        <Element index="805" value="0.985301"/>
        <Element index="806" value="0.63533"/>
        <Element index="807" value="0.221265"/>
        <Element index="808" value="0.912436172928784"/>
        <Element index="809" value="0.986345"/>
        <Element index="810" value="0.640969"/>
        <Element index="811" value="0.217948"/>
        <Element index="812" value="0.921902304306849"/>
        <Element index="813" value="0.987332"/>
        <Element index="814" value="0.646633"/>
        <Element index="815" value="0.214648"/>
        <Element index="816" value="0.931370849898476"/>
        <Element index="817" value="0.98826"/>
        <Element index="818" value="0.652325"/>
        <Element index="819" value="0.211364"/>
        <Element index="820" value="0.940839395490104"/>
        <Element index="821" value="0.989128"/>
        <Element index="822" value="0.658043"/>
        <Element index="823" value="0.2081"/>
        <Element index="824" value="0.950305526868168"/>
        <Element index="825" value="0.989935"/>
        <Element index="826" value="0.663787"/>
        <Element index="827" value="0.204859"/>
        <Element index="828" value="0.959774072459795"/>
        <Element index="829" value="0.990681"/>
        <Element index="830" value="0.669558"/>
        <Element index="831" value="0.201642"/>
        <Element index="832" value="0.96924020383786"/>
        <Element index="833" value="0.991365"/>
        <Element index="834" value="0.675355"/>
        <Element index="835" value="0.198453"/>
        <Element index="836" value="0.978708749429488"/>
        <Element index="837" value="0.991985"/>
        <Element index="838" value="0.681179"/>
        <Element index="839" value="0.195295"/>
        <Element index="840" value="0.988174880807553"/>
        <Element index="841" value="0.992541"/>
        <Element index="842" value="0.68703"/>
        <Element index="843" value="0.19217"/>
        <Element index="844" value="0.99764342639918"/>
        <Element index="845" value="0.993032"/>
        <Element index="846" value="0.692907"/>
        <Element index="847" value="0.189084"/>
        <Element index="848" value="1.00711197199081"/>
        <Element index="849" value="0.993456"/>
        <Element index="850" value="0.69881"/>
        <Element index="851" value="0.186041"/>
        <Element index="852" value="1.01657810336887"/>
        <Element index="853" value="0.993814"/>
        <Element index="854" value="0.704741"/>
        <Element index="855" value="0.183043"/>
        <Element index="856" value="1.0260466489605"/>
        <Element index="857" value="0.994103"/>
        <Element index="858" value="0.710698"/>
        <Element index="859" value="0.180097"/>
        <Element index="860" value="1.03551278033856"/>
        <Element index="861" value="0.994324"/>
        <Element index="862" value="0.716681"/>
        <Element index="863" value="0.177208"/>
        <Element index="864" value="1.04498132593019"/>
        <Element index="865" value="0.994474"/>
        <Element index="866" value="0.722691"/>
        <Element index="867" value="0.174381"/>
        <Element index="868" value="1.05444745730826"/>
        <Element index="869" value="0.994553"/>
        <Element index="870" value="0.728728"/>
        <Element index="871" value="0.171622"/>
        <Element index="872" value="1.06391600289988"/>
        <Element index="873" value="0.994561"/>
        <Element index="874" value="0.734791"/>
        <Element index="875" value="0.168938"/>
        <Element index="876" value="1.07338454849151"/>
        <Element index="877" value="0.994495"/>
        <Element index="878" value="0.74088"/>
        <Element index="879" value="0.166335"/>
        <Element index="880" value="1.08285067986958"/>
        <Element index="881" value="0.994355"/>
        <Element index="882" value="0.746995"/>
        <Element index="883" value="0.163821"/>
        <Element index="884" value="1.0923192254612"/>
        <Element index="885" value="0.994141"/>
        <Element index="886" value="0.753137"/>
        <Element index="887" value="0.161404"/>
        <Element index="888" value="1.10178535683927"/>
        <Element index="889" value="0.993851"/>
        <Element index="890" value="0.759304"/>
        <Element index="891" value="0.159092"/>
        <Element index="892" value="1.1112539024309"/>
        <Element index="893" value="0.993482"/>
        <Element index="894" value="0.765499"/>
        <Element index="895" value="0.156891"/>
        <Element index="896" value="1.12072003380896"/>
        <Element index="897" value="0.993033"/>
        <Element index="898" value="0.77172"/>
        <Element index="899" value="0.154808"/>
        <Element index="900" value="1.13018857940059"/>
        <Element index="901" value="0.992505"/>
        <Element index="902" value="0.777967"/>
        <Element index="903" value="0.152855"/>
        <Element index="904" value="1.13965712499221"/>
        <Element index="905" value="0.991897"/>
        <Element index="906" value="0.784239"/>
        <Element index="907" value="0.151042"/>
        <Element index="908" value="1.14912325637028"/>
        <Element index="909" value="0.991209"/>
        <Element index="910" value="0.790537"/>
        <Element index="911" value="0.149377"/>
        <Element index="912" value="1.15859180196191"/>
        <Element index="913" value="0.990439"/>
        <Element index="914" value="0.796859"/>
        <Element index="915" value="0.14787"/>
        <Element index="916" value="1.16805793333997"/>
        <Element index="917" value="0.989587"/>
        <Element index="918" value="0.803205"/>
        <Element index="919" value="0.146529"/>
        <Element index="920" value="1.1775264789316"/>
        <Element index="921" value="0.988648"/>
        <Element index="922" value="0.809579"/>
        <Element index="923" value="0.145357"/>
        <Element index="924" value="1.18699261030966"/>
        <Element index="925" value="0.987621"/>
        <Element index="926" value="0.815978"/>
        <Element index="927" value="0.144363"/>
        <Element index="928" value="1.19646115590129"/>
        <Element index="929" value="0.986509"/>
        <Element index="930" value="0.822401"/>
        <Element index="931" value="0.143557"/>
        <Element index="932" value="1.20592728727936"/>
        <Element index="933" value="0.985314"/>
        <Element index="934" value="0.828846"/>
        <Element index="935" value="0.142945"/>
        <Element index="936" value="1.21539583287098"/>
        <Element index="937" value="0.984031"/>
        <Element index="938" value="0.835315"/>
        <Element index="939" value="0.142528"/>
        <Element index="940" value="1.22486437846261"/>
        <Element index="941" value="0.982653"/>
        <Element index="942" value="0.841812"/>
        <Element index="943" value="0.142303"/>
        <Element index="944" value="1.23433050984068"/>
        <Element index="945" value="0.98119"/>
        <Element index="946" value="0.848329"/>
        <Element index="947" value="0.142279"/>
        <Element index="948" value="1.2437990554323"/>
        <Element index="949" value="0.979644"/>
        <Element index="950" value="0.854866"/>
        <Element index="951" value="0.142453"/>
        <Element index="952" value="1.25326518681037"/>
        <Element index="953" value="0.977995"/>
        <Element index="954" value="0.861432"/>
        <Element index="955" value="0.142808"/>
        <Element index="956" value="1.262733732402"/>
        <Element index="957" value="0.976265"/>
        <Element index="958" value="0.868016"/>
        <Element index="959" value="0.143351"/>
        <Element index="960" value="1.27219986378006"/>
        <Element index="961" value="0.974443"/>
        <Element index="962" value="0.874622"/>
        <Element index="963" value="0.144061"/>
        <Element index="964" value="1.28166840937169"/>
        <Element index="965" value="0.97253"/>
        <Element index="966" value="0.88125"/>
        <Element index="967" value="0.144923"/>
        <Element index="968" value="1.29113695496332"/>
        <Element index="969" value="0.970533"/>
        <Element index="970" value="0.887896"/>
        <Element index="971" value="0.145919"/>
        <Element index="972" value="1.30060308634138"/>
        <Element index="973" value="0.968443"/>
        <Element index="974" value="0.894564"/>
        <Element index="975" value="0.147014"/>
        <Element index="976" value="1.31007163193301"/>
        <Element index="977" value="0.966271"/>
        <Element index="978" value="0.901249"/>
        <Element index="979" value="0.14818"/>
        <Element index="980" value="1.31953776331107"/>
        <Element index="981" value="0.964021"/>
        <Element index="982" value="0.90795"/>
        <Element index="983" value="0.14937"/>
        <Element index="984" value="1.3290063089027"/>
        <Element index="985" value="0.961681"/>
        <Element index="986" value="0.914672"/>
        <Element index="987" value="0.15052"/>
        <Element index="988" value="1.33847244028076"/>
        <Element index="989" value="0.959276"/>
        <Element index="990" value="0.921407"/>
        <Element index="991" value="0.151566"/>
        <Element index="992" value="1.34794098587239"/>
        <Element index="993" value="0.956808"/>
        <Element index="994" value="0.928152"/>
        <Element index="995" value="0.152409"/>
        <Element index="996" value="1.35740953146402"/>
        <Element index="997" value="0.954287"/>
        <Element index="998" value="0.934908"/>
        <Element index="999" value="0.152921"/>
        <Element index="1000" value="1.36687566284208"/>
        <Element index="1001" value="0.951726"/>
        <Element index="1002" value="0.941671"/>
        <Element index="1003" value="0.152925"/>
        <Element index="1004" value="1.37634420843371"/>
        <Element index="1005" value="0.949151"/>
        <Element index="1006" value="0.948435"/>
        <Element index="1007" value="0.152178"/>
        <Element index="1008" value="1.38581033981178"/>
        <Element index="1009" value="0.946602"/>
        <Element index="1010" value="0.95519"/>
        <Element index="1011" value="0.150328"/>
        <Element index="1012" value="1.3952788854034"/>
        <Element index="1013" value="0.944152"/>
        <Element index="1014" value="0.961916"/>
        <Element index="1015" value="0.146861"/>
        <Element index="1016" value="1.40474501678147"/>
        <Element index="1017" value="0.941896"/>
        <Element index="1018" value="0.96859"/>
        <Element index="1019" value="0.140956"/>
        <Element index="1020" value="1.4142135623731"/>
        <Element index="1021" value="0.940015"/>
        <Element index="1022" value="0.975158"/>
        <Element index="1023" value="0.131326"/>
      </Property>
      <Property name="RescaleOnVisibilityChange" id="5174.RescaleOnVisibilityChange" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5174.RescaleOnVisibilityChange.bool"/>
      </Property>
      <Property name="ScalarOpacityFunction" id="5174.ScalarOpacityFunction" number_of_elements="1">
        <Proxy value="5173"/>
      </Property>
      <Property name="ScalarRangeInitialized" id="5174.ScalarRangeInitialized" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="5174.ScalarRangeInitialized.bool"/>
      </Property>
      <Property name="ShowIndexedColorActiveValues" id="5174.ShowIndexedColorActiveValues" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5174.ShowIndexedColorActiveValues.bool"/>
      </Property>
      <Property name="UseAboveRangeColor" id="5174.UseAboveRangeColor" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5174.UseAboveRangeColor.bool"/>
      </Property>
      <Property name="UseBelowRangeColor" id="5174.UseBelowRangeColor" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5174.UseBelowRangeColor.bool"/>
      </Property>
      <Property name="UseLogScale" id="5174.UseLogScale" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5174.UseLogScale.bool"/>
      </Property>
      <Property name="VectorComponent" id="5174.VectorComponent" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="range" id="5174.VectorComponent.range"/>
      </Property>
      <Property name="VectorMode" id="5174.VectorMode" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="enum" id="5174.VectorMode.enum">
          <Entry value="0" text="Magnitude"/>
          <Entry value="1" text="Component"/>
        </Domain>
      </Property>
    </Proxy>
    <Proxy group="piecewise_functions" type="PiecewiseFunction" id="5173" servers="21">
      <Property name="AllowDuplicateScalars" id="5173.AllowDuplicateScalars" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="5173.AllowDuplicateScalars.bool"/>
      </Property>
      <Property name="Points" id="5173.Points" number_of_elements="8">
        <Element index="0" value="-1"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0.5"/>
        <Element index="3" value="0"/>
        <Element index="4" value="1.4142135623731"/>
        <Element index="5" value="1"/>
        <Element index="6" value="0.5"/>
        <Element index="7" value="0"/>
      </Property>
      <Property name="ScalarRangeInitialized" id="5173.ScalarRangeInitialized" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="5173.ScalarRangeInitialized.bool"/>
      </Property>
    </Proxy>
    <Proxy group="misc" type="RepresentationAnimationHelper" id="4710" servers="16">
      <Property name="Source" id="4710.Source" number_of_elements="1">
        <Proxy value="4698"/>
      </Property>
    </Proxy>
    <Proxy group="annotations" type="GridAxes3DActor" id="4718" servers="21">
      <Property name="AxesToLabel" id="4718.AxesToLabel" number_of_elements="1">
        <Element index="0" value="63"/>
        <Domain name="range" id="4718.AxesToLabel.range"/>
      </Property>
      <Property name="DataPosition" id="4718.DataPosition" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="4718.DataPosition.range"/>
      </Property>
      <Property name="DataScale" id="4718.DataScale" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="1"/>
        <Element index="2" value="1"/>
        <Domain name="range" id="4718.DataScale.range"/>
      </Property>
      <Property name="FacesToRender" id="4718.FacesToRender" number_of_elements="1">
        <Element index="0" value="63"/>
        <Domain name="range" id="4718.FacesToRender.range"/>
      </Property>
      <Property name="LabelUniqueEdgesOnly" id="4718.LabelUniqueEdgesOnly" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="4718.LabelUniqueEdgesOnly.bool"/>
      </Property>
      <Property name="ModelBounds" id="4718.ModelBounds" number_of_elements="6">
        <Element index="0" value="0"/>
        <Element index="1" value="1"/>
        <Element index="2" value="0"/>
        <Element index="3" value="1"/>
        <Element index="4" value="0"/>
        <Element index="5" value="1"/>
      </Property>
      <Property name="ModelTransformMatrix" id="4718.ModelTransformMatrix" number_of_elements="16">
        <Element index="0" value="1"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Element index="3" value="0"/>
        <Element index="4" value="0"/>
        <Element index="5" value="1"/>
        <Element index="6" value="0"/>
        <Element index="7" value="0"/>
        <Element index="8" value="0"/>
        <Element index="9" value="0"/>
        <Element index="10" value="1"/>
        <Element index="11" value="0"/>
        <Element index="12" value="0"/>
        <Element index="13" value="0"/>
        <Element index="14" value="0"/>
        <Element index="15" value="1"/>
      </Property>
      <Property name="ShowEdges" id="4718.ShowEdges" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="4718.ShowEdges.bool"/>
      </Property>
      <Property name="ShowGrid" id="4718.ShowGrid" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4718.ShowGrid.bool"/>
      </Property>
      <Property name="ShowTicks" id="4718.ShowTicks" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="4718.ShowTicks.bool"/>
      </Property>
      <Property name="UseModelTransform" id="4718.UseModelTransform" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="range" id="4718.UseModelTransform.range"/>
      </Property>
      <Property name="Visibility" id="4718.Visibility" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4718.Visibility.bool"/>
      </Property>
      <Property name="XAxisLabels" id="4718.XAxisLabels">
        <Domain name="scalar_range" id="4718.XAxisLabels.scalar_range"/>
      </Property>
      <Property name="XAxisNotation" id="4718.XAxisNotation" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="enum" id="4718.XAxisNotation.enum">
          <Entry value="0" text="Mixed"/>
          <Entry value="1" text="Scientific"/>
          <Entry value="2" text="Fixed"/>
        </Domain>
      </Property>
      <Property name="XAxisPrecision" id="4718.XAxisPrecision" number_of_elements="1">
        <Element index="0" value="2"/>
        <Domain name="range" id="4718.XAxisPrecision.range"/>
      </Property>
      <Property name="XAxisUseCustomLabels" id="4718.XAxisUseCustomLabels" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4718.XAxisUseCustomLabels.bool"/>
      </Property>
      <Property name="XTitle" id="4718.XTitle" number_of_elements="1">
        <Element index="0" value="X Axis"/>
      </Property>
      <Property name="YAxisLabels" id="4718.YAxisLabels">
        <Domain name="scalar_range" id="4718.YAxisLabels.scalar_range"/>
      </Property>
      <Property name="YAxisNotation" id="4718.YAxisNotation" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="enum" id="4718.YAxisNotation.enum">
          <Entry value="0" text="Mixed"/>
          <Entry value="1" text="Scientific"/>
          <Entry value="2" text="Fixed"/>
        </Domain>
      </Property>
      <Property name="YAxisPrecision" id="4718.YAxisPrecision" number_of_elements="1">
        <Element index="0" value="2"/>
        <Domain name="range" id="4718.YAxisPrecision.range"/>
      </Property>
      <Property name="YAxisUseCustomLabels" id="4718.YAxisUseCustomLabels" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4718.YAxisUseCustomLabels.bool"/>
      </Property>
      <Property name="YTitle" id="4718.YTitle" number_of_elements="1">
        <Element index="0" value="Y Axis"/>
      </Property>
      <Property name="ZAxisLabels" id="4718.ZAxisLabels">
        <Domain name="scalar_range" id="4718.ZAxisLabels.scalar_range"/>
      </Property>
      <Property name="ZAxisNotation" id="4718.ZAxisNotation" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="enum" id="4718.ZAxisNotation.enum">
          <Entry value="0" text="Mixed"/>
          <Entry value="1" text="Scientific"/>
          <Entry value="2" text="Fixed"/>
        </Domain>
      </Property>
      <Property name="ZAxisPrecision" id="4718.ZAxisPrecision" number_of_elements="1">
        <Element index="0" value="2"/>
        <Domain name="range" id="4718.ZAxisPrecision.range"/>
      </Property>
      <Property name="ZAxisUseCustomLabels" id="4718.ZAxisUseCustomLabels" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4718.ZAxisUseCustomLabels.bool"/>
      </Property>
      <Property name="ZTitle" id="4718.ZTitle" number_of_elements="1">
        <Element index="0" value="Z Axis"/>
      </Property>
      <Property name="CullBackface" id="4718.CullBackface" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4718.CullBackface.bool"/>
      </Property>
      <Property name="CullFrontface" id="4718.CullFrontface" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="4718.CullFrontface.bool"/>
      </Property>
      <Property name="GridColor" id="4718.GridColor" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="1"/>
        <Element index="2" value="1"/>
        <Domain name="range" id="4718.GridColor.range"/>
      </Property>
      <Property name="XLabelBold" id="4718.XLabelBold" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4718.XLabelBold.bool"/>
      </Property>
      <Property name="XLabelColor" id="4718.XLabelColor" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="1"/>
        <Element index="2" value="1"/>
        <Domain name="range" id="4718.XLabelColor.range"/>
      </Property>
      <Property name="XLabelFontFamily" id="4718.XLabelFontFamily" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="enum" id="4718.XLabelFontFamily.enum">
          <Entry value="0" text="Arial"/>
          <Entry value="1" text="Courier"/>
          <Entry value="2" text="Times"/>
        </Domain>
      </Property>
      <Property name="XLabelFontSize" id="4718.XLabelFontSize" number_of_elements="1">
        <Element index="0" value="12"/>
        <Domain name="range" id="4718.XLabelFontSize.range"/>
      </Property>
      <Property name="XLabelItalic" id="4718.XLabelItalic" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4718.XLabelItalic.bool"/>
      </Property>
      <Property name="XLabelOpacity" id="4718.XLabelOpacity" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="4718.XLabelOpacity.range"/>
      </Property>
      <Property name="XLabelShadow" id="4718.XLabelShadow" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4718.XLabelShadow.bool"/>
      </Property>
      <Property name="XTitleBold" id="4718.XTitleBold" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4718.XTitleBold.bool"/>
      </Property>
      <Property name="XTitleColor" id="4718.XTitleColor" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="1"/>
        <Element index="2" value="1"/>
        <Domain name="range" id="4718.XTitleColor.range"/>
      </Property>
      <Property name="XTitleFontFamily" id="4718.XTitleFontFamily" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="enum" id="4718.XTitleFontFamily.enum">
          <Entry value="0" text="Arial"/>
          <Entry value="1" text="Courier"/>
          <Entry value="2" text="Times"/>
        </Domain>
      </Property>
      <Property name="XTitleFontSize" id="4718.XTitleFontSize" number_of_elements="1">
        <Element index="0" value="12"/>
        <Domain name="range" id="4718.XTitleFontSize.range"/>
      </Property>
      <Property name="XTitleItalic" id="4718.XTitleItalic" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4718.XTitleItalic.bool"/>
      </Property>
      <Property name="XTitleOpacity" id="4718.XTitleOpacity" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="4718.XTitleOpacity.range"/>
      </Property>
      <Property name="XTitleShadow" id="4718.XTitleShadow" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4718.XTitleShadow.bool"/>
      </Property>
      <Property name="YLabelBold" id="4718.YLabelBold" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4718.YLabelBold.bool"/>
      </Property>
      <Property name="YLabelColor" id="4718.YLabelColor" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="1"/>
        <Element index="2" value="1"/>
        <Domain name="range" id="4718.YLabelColor.range"/>
      </Property>
      <Property name="YLabelFontFamily" id="4718.YLabelFontFamily" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="enum" id="4718.YLabelFontFamily.enum">
          <Entry value="0" text="Arial"/>
          <Entry value="1" text="Courier"/>
          <Entry value="2" text="Times"/>
        </Domain>
      </Property>
      <Property name="YLabelFontSize" id="4718.YLabelFontSize" number_of_elements="1">
        <Element index="0" value="12"/>
        <Domain name="range" id="4718.YLabelFontSize.range"/>
      </Property>
      <Property name="YLabelItalic" id="4718.YLabelItalic" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4718.YLabelItalic.bool"/>
      </Property>
      <Property name="YLabelOpacity" id="4718.YLabelOpacity" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="4718.YLabelOpacity.range"/>
      </Property>
      <Property name="YLabelShadow" id="4718.YLabelShadow" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4718.YLabelShadow.bool"/>
      </Property>
      <Property name="YTitleBold" id="4718.YTitleBold" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4718.YTitleBold.bool"/>
      </Property>
      <Property name="YTitleColor" id="4718.YTitleColor" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="1"/>
        <Element index="2" value="1"/>
        <Domain name="range" id="4718.YTitleColor.range"/>
      </Property>
      <Property name="YTitleFontFamily" id="4718.YTitleFontFamily" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="enum" id="4718.YTitleFontFamily.enum">
          <Entry value="0" text="Arial"/>
          <Entry value="1" text="Courier"/>
          <Entry value="2" text="Times"/>
        </Domain>
      </Property>
      <Property name="YTitleFontSize" id="4718.YTitleFontSize" number_of_elements="1">
        <Element index="0" value="12"/>
        <Domain name="range" id="4718.YTitleFontSize.range"/>
      </Property>
      <Property name="YTitleItalic" id="4718.YTitleItalic" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4718.YTitleItalic.bool"/>
      </Property>
      <Property name="YTitleOpacity" id="4718.YTitleOpacity" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="4718.YTitleOpacity.range"/>
      </Property>
      <Property name="YTitleShadow" id="4718.YTitleShadow" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4718.YTitleShadow.bool"/>
      </Property>
      <Property name="ZLabelBold" id="4718.ZLabelBold" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4718.ZLabelBold.bool"/>
      </Property>
      <Property name="ZLabelColor" id="4718.ZLabelColor" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="1"/>
        <Element index="2" value="1"/>
        <Domain name="range" id="4718.ZLabelColor.range"/>
      </Property>
      <Property name="ZLabelFontFamily" id="4718.ZLabelFontFamily" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="enum" id="4718.ZLabelFontFamily.enum">
          <Entry value="0" text="Arial"/>
          <Entry value="1" text="Courier"/>
          <Entry value="2" text="Times"/>
        </Domain>
      </Property>
      <Property name="ZLabelFontSize" id="4718.ZLabelFontSize" number_of_elements="1">
        <Element index="0" value="12"/>
        <Domain name="range" id="4718.ZLabelFontSize.range"/>
      </Property>
      <Property name="ZLabelItalic" id="4718.ZLabelItalic" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4718.ZLabelItalic.bool"/>
      </Property>
      <Property name="ZLabelOpacity" id="4718.ZLabelOpacity" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="4718.ZLabelOpacity.range"/>
      </Property>
      <Property name="ZLabelShadow" id="4718.ZLabelShadow" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4718.ZLabelShadow.bool"/>
      </Property>
      <Property name="ZTitleBold" id="4718.ZTitleBold" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4718.ZTitleBold.bool"/>
      </Property>
      <Property name="ZTitleColor" id="4718.ZTitleColor" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="1"/>
        <Element index="2" value="1"/>
        <Domain name="range" id="4718.ZTitleColor.range"/>
      </Property>
      <Property name="ZTitleFontFamily" id="4718.ZTitleFontFamily" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="enum" id="4718.ZTitleFontFamily.enum">
          <Entry value="0" text="Arial"/>
          <Entry value="1" text="Courier"/>
          <Entry value="2" text="Times"/>
        </Domain>
      </Property>
      <Property name="ZTitleFontSize" id="4718.ZTitleFontSize" number_of_elements="1">
        <Element index="0" value="12"/>
        <Domain name="range" id="4718.ZTitleFontSize.range"/>
      </Property>
      <Property name="ZTitleItalic" id="4718.ZTitleItalic" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4718.ZTitleItalic.bool"/>
      </Property>
      <Property name="ZTitleOpacity" id="4718.ZTitleOpacity" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="4718.ZTitleOpacity.range"/>
      </Property>
      <Property name="ZTitleShadow" id="4718.ZTitleShadow" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4718.ZTitleShadow.bool"/>
      </Property>
    </Proxy>
    <Proxy group="sources" type="ArrowSource" id="4816" servers="1">
      <Property name="Invert" id="4816.Invert" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4816.Invert.bool"/>
      </Property>
      <Property name="ShaftRadius" id="4816.ShaftRadius" number_of_elements="1">
        <Element index="0" value="0.03"/>
        <Domain name="range" id="4816.ShaftRadius.range"/>
      </Property>
      <Property name="ShaftResolution" id="4816.ShaftResolution" number_of_elements="1">
        <Element index="0" value="6"/>
        <Domain name="range" id="4816.ShaftResolution.range"/>
      </Property>
      <Property name="TipLength" id="4816.TipLength" number_of_elements="1">
        <Element index="0" value="0.35"/>
        <Domain name="range" id="4816.TipLength.range"/>
      </Property>
      <Property name="TipRadius" id="4816.TipRadius" number_of_elements="1">
        <Element index="0" value="0.1"/>
        <Domain name="range" id="4816.TipRadius.range"/>
      </Property>
      <Property name="TipResolution" id="4816.TipResolution" number_of_elements="1">
        <Element index="0" value="6"/>
        <Domain name="range" id="4816.TipResolution.range"/>
      </Property>
    </Proxy>
    <Proxy group="sources" type="ConeSource" id="4827" servers="1">
      <Property name="Capping" id="4827.Capping" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="4827.Capping.bool"/>
      </Property>
      <Property name="Center" id="4827.Center" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="4827.Center.range"/>
      </Property>
      <Property name="Direction" id="4827.Direction" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="4827.Direction.range"/>
      </Property>
      <Property name="Height" id="4827.Height" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="4827.Height.range"/>
      </Property>
      <Property name="Radius" id="4827.Radius" number_of_elements="1">
        <Element index="0" value="0.5"/>
        <Domain name="range" id="4827.Radius.range"/>
      </Property>
      <Property name="Resolution" id="4827.Resolution" number_of_elements="1">
        <Element index="0" value="6"/>
        <Domain name="range" id="4827.Resolution.range"/>
      </Property>
    </Proxy>
    <Proxy group="sources" type="CubeSource" id="4838" servers="1">
      <Property name="Center" id="4838.Center" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="4838.Center.range"/>
      </Property>
      <Property name="XLength" id="4838.XLength" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="4838.XLength.range"/>
      </Property>
      <Property name="YLength" id="4838.YLength" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="4838.YLength.range"/>
      </Property>
      <Property name="ZLength" id="4838.ZLength" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="4838.ZLength.range"/>
      </Property>
    </Proxy>
    <Proxy group="sources" type="CylinderSource" id="4849" servers="1">
      <Property name="Capping" id="4849.Capping" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="4849.Capping.bool"/>
      </Property>
      <Property name="Center" id="4849.Center" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="4849.Center.range"/>
      </Property>
      <Property name="Height" id="4849.Height" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="4849.Height.range"/>
      </Property>
      <Property name="Radius" id="4849.Radius" number_of_elements="1">
        <Element index="0" value="0.5"/>
        <Domain name="range" id="4849.Radius.range"/>
      </Property>
      <Property name="Resolution" id="4849.Resolution" number_of_elements="1">
        <Element index="0" value="6"/>
        <Domain name="range" id="4849.Resolution.range"/>
      </Property>
    </Proxy>
    <Proxy group="sources" type="LineSource" id="4860" servers="1">
      <Property name="Point1" id="4860.Point1" number_of_elements="3">
        <Element index="0" value="-0.5"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="4860.Point1.range"/>
      </Property>
      <Property name="Point2" id="4860.Point2" number_of_elements="3">
        <Element index="0" value="0.5"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="4860.Point2.range"/>
      </Property>
      <Property name="Resolution" id="4860.Resolution" number_of_elements="1">
        <Element index="0" value="6"/>
        <Domain name="range" id="4860.Resolution.range"/>
      </Property>
    </Proxy>
    <Proxy group="sources" type="SphereSource" id="4871" servers="1">
      <Property name="Center" id="4871.Center" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="4871.Center.range"/>
      </Property>
      <Property name="EndPhi" id="4871.EndPhi" number_of_elements="1">
        <Element index="0" value="180"/>
        <Domain name="range" id="4871.EndPhi.range"/>
      </Property>
      <Property name="EndTheta" id="4871.EndTheta" number_of_elements="1">
        <Element index="0" value="360"/>
        <Domain name="range" id="4871.EndTheta.range"/>
      </Property>
      <Property name="PhiResolution" id="4871.PhiResolution" number_of_elements="1">
        <Element index="0" value="8"/>
        <Domain name="range" id="4871.PhiResolution.range"/>
      </Property>
      <Property name="Radius" id="4871.Radius" number_of_elements="1">
        <Element index="0" value="0.5"/>
        <Domain name="range" id="4871.Radius.range"/>
      </Property>
      <Property name="StartPhi" id="4871.StartPhi" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="range" id="4871.StartPhi.range"/>
      </Property>
      <Property name="StartTheta" id="4871.StartTheta" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="range" id="4871.StartTheta.range"/>
      </Property>
      <Property name="ThetaResolution" id="4871.ThetaResolution" number_of_elements="1">
        <Element index="0" value="8"/>
        <Domain name="range" id="4871.ThetaResolution.range"/>
      </Property>
    </Proxy>
    <Proxy group="sources" type="GlyphSource2D" id="4882" servers="1">
      <Property name="Center" id="4882.Center" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="4882.Center.range"/>
      </Property>
      <Property name="Filled" id="4882.Filled" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4882.Filled.bool"/>
      </Property>
      <Property name="GlyphType" id="4882.GlyphType" number_of_elements="1">
        <Element index="0" value="9"/>
        <Domain name="enum" id="4882.GlyphType.enum">
          <Entry value="1" text="Vertex"/>
          <Entry value="2" text="Dash"/>
          <Entry value="3" text="Cross"/>
          <Entry value="4" text="ThickCross"/>
          <Entry value="5" text="Triangle"/>
          <Entry value="6" text="Square"/>
          <Entry value="7" text="Circle"/>
          <Entry value="8" text="Diamond"/>
          <Entry value="9" text="Arrow"/>
          <Entry value="10" text="ThickArrow"/>
          <Entry value="11" text="HookedArrow"/>
          <Entry value="12" text="EdgeArrow"/>
        </Domain>
      </Property>
    </Proxy>
    <Proxy group="piecewise_functions" type="PiecewiseFunction" id="4915" servers="21">
      <Property name="AllowDuplicateScalars" id="4915.AllowDuplicateScalars" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="4915.AllowDuplicateScalars.bool"/>
      </Property>
      <Property name="Points" id="4915.Points" number_of_elements="8">
        <Element index="0" value="1.77678677818044e-06"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0.5"/>
        <Element index="3" value="0"/>
        <Element index="4" value="1.63208877384008e-05"/>
        <Element index="5" value="1"/>
        <Element index="6" value="0.5"/>
        <Element index="7" value="0"/>
      </Property>
      <Property name="ScalarRangeInitialized" id="4915.ScalarRangeInitialized" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4915.ScalarRangeInitialized.bool"/>
      </Property>
    </Proxy>
    <Proxy group="piecewise_functions" type="PiecewiseFunction" id="4916" servers="21">
      <Property name="AllowDuplicateScalars" id="4916.AllowDuplicateScalars" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="4916.AllowDuplicateScalars.bool"/>
      </Property>
      <Property name="Points" id="4916.Points" number_of_elements="8">
        <Element index="0" value="1.77678677818044e-06"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0.5"/>
        <Element index="3" value="0"/>
        <Element index="4" value="1.63208877384008e-05"/>
        <Element index="5" value="1"/>
        <Element index="6" value="0.5"/>
        <Element index="7" value="0"/>
      </Property>
      <Property name="ScalarRangeInitialized" id="4916.ScalarRangeInitialized" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4916.ScalarRangeInitialized.bool"/>
      </Property>
    </Proxy>
    <Proxy group="misc" type="RepresentationAnimationHelper" id="5005" servers="16">
      <Property name="Source" id="5005.Source" number_of_elements="1">
        <Proxy value="4994"/>
      </Property>
    </Proxy>
    <Proxy group="sources" type="ArrowSource" id="5017" servers="1">
      <Property name="Invert" id="5017.Invert" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5017.Invert.bool"/>
      </Property>
      <Property name="ShaftRadius" id="5017.ShaftRadius" number_of_elements="1">
        <Element index="0" value="0.03"/>
        <Domain name="range" id="5017.ShaftRadius.range"/>
      </Property>
      <Property name="ShaftResolution" id="5017.ShaftResolution" number_of_elements="1">
        <Element index="0" value="6"/>
        <Domain name="range" id="5017.ShaftResolution.range"/>
      </Property>
      <Property name="TipLength" id="5017.TipLength" number_of_elements="1">
        <Element index="0" value="0.35"/>
        <Domain name="range" id="5017.TipLength.range"/>
      </Property>
      <Property name="TipRadius" id="5017.TipRadius" number_of_elements="1">
        <Element index="0" value="0.1"/>
        <Domain name="range" id="5017.TipRadius.range"/>
      </Property>
      <Property name="TipResolution" id="5017.TipResolution" number_of_elements="1">
        <Element index="0" value="6"/>
        <Domain name="range" id="5017.TipResolution.range"/>
      </Property>
    </Proxy>
    <Proxy group="sources" type="ConeSource" id="5028" servers="1">
      <Property name="Capping" id="5028.Capping" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="5028.Capping.bool"/>
      </Property>
      <Property name="Center" id="5028.Center" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="5028.Center.range"/>
      </Property>
      <Property name="Direction" id="5028.Direction" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="5028.Direction.range"/>
      </Property>
      <Property name="Height" id="5028.Height" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="5028.Height.range"/>
      </Property>
      <Property name="Radius" id="5028.Radius" number_of_elements="1">
        <Element index="0" value="0.5"/>
        <Domain name="range" id="5028.Radius.range"/>
      </Property>
      <Property name="Resolution" id="5028.Resolution" number_of_elements="1">
        <Element index="0" value="6"/>
        <Domain name="range" id="5028.Resolution.range"/>
      </Property>
    </Proxy>
    <Proxy group="sources" type="CubeSource" id="5039" servers="1">
      <Property name="Center" id="5039.Center" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="5039.Center.range"/>
      </Property>
      <Property name="XLength" id="5039.XLength" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="5039.XLength.range"/>
      </Property>
      <Property name="YLength" id="5039.YLength" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="5039.YLength.range"/>
      </Property>
      <Property name="ZLength" id="5039.ZLength" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="5039.ZLength.range"/>
      </Property>
    </Proxy>
    <Proxy group="sources" type="CylinderSource" id="5050" servers="1">
      <Property name="Capping" id="5050.Capping" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="5050.Capping.bool"/>
      </Property>
      <Property name="Center" id="5050.Center" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="5050.Center.range"/>
      </Property>
      <Property name="Height" id="5050.Height" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="5050.Height.range"/>
      </Property>
      <Property name="Radius" id="5050.Radius" number_of_elements="1">
        <Element index="0" value="0.5"/>
        <Domain name="range" id="5050.Radius.range"/>
      </Property>
      <Property name="Resolution" id="5050.Resolution" number_of_elements="1">
        <Element index="0" value="6"/>
        <Domain name="range" id="5050.Resolution.range"/>
      </Property>
    </Proxy>
    <Proxy group="sources" type="LineSource" id="5061" servers="1">
      <Property name="Point1" id="5061.Point1" number_of_elements="3">
        <Element index="0" value="-0.5"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="5061.Point1.range"/>
      </Property>
      <Property name="Point2" id="5061.Point2" number_of_elements="3">
        <Element index="0" value="0.5"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="5061.Point2.range"/>
      </Property>
      <Property name="Resolution" id="5061.Resolution" number_of_elements="1">
        <Element index="0" value="6"/>
        <Domain name="range" id="5061.Resolution.range"/>
      </Property>
    </Proxy>
    <Proxy group="sources" type="SphereSource" id="5072" servers="1">
      <Property name="Center" id="5072.Center" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="5072.Center.range"/>
      </Property>
      <Property name="EndPhi" id="5072.EndPhi" number_of_elements="1">
        <Element index="0" value="180"/>
        <Domain name="range" id="5072.EndPhi.range"/>
      </Property>
      <Property name="EndTheta" id="5072.EndTheta" number_of_elements="1">
        <Element index="0" value="360"/>
        <Domain name="range" id="5072.EndTheta.range"/>
      </Property>
      <Property name="PhiResolution" id="5072.PhiResolution" number_of_elements="1">
        <Element index="0" value="8"/>
        <Domain name="range" id="5072.PhiResolution.range"/>
      </Property>
      <Property name="Radius" id="5072.Radius" number_of_elements="1">
        <Element index="0" value="0.5"/>
        <Domain name="range" id="5072.Radius.range"/>
      </Property>
      <Property name="StartPhi" id="5072.StartPhi" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="range" id="5072.StartPhi.range"/>
      </Property>
      <Property name="StartTheta" id="5072.StartTheta" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="range" id="5072.StartTheta.range"/>
      </Property>
      <Property name="ThetaResolution" id="5072.ThetaResolution" number_of_elements="1">
        <Element index="0" value="8"/>
        <Domain name="range" id="5072.ThetaResolution.range"/>
      </Property>
    </Proxy>
    <Proxy group="sources" type="GlyphSource2D" id="5083" servers="1">
      <Property name="Center" id="5083.Center" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="5083.Center.range"/>
      </Property>
      <Property name="Filled" id="5083.Filled" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5083.Filled.bool"/>
      </Property>
      <Property name="GlyphType" id="5083.GlyphType" number_of_elements="1">
        <Element index="0" value="9"/>
        <Domain name="enum" id="5083.GlyphType.enum">
          <Entry value="1" text="Vertex"/>
          <Entry value="2" text="Dash"/>
          <Entry value="3" text="Cross"/>
          <Entry value="4" text="ThickCross"/>
          <Entry value="5" text="Triangle"/>
          <Entry value="6" text="Square"/>
          <Entry value="7" text="Circle"/>
          <Entry value="8" text="Diamond"/>
          <Entry value="9" text="Arrow"/>
          <Entry value="10" text="ThickArrow"/>
          <Entry value="11" text="HookedArrow"/>
          <Entry value="12" text="EdgeArrow"/>
        </Domain>
      </Property>
    </Proxy>
    <Proxy group="piecewise_functions" type="PiecewiseFunction" id="5116" servers="21">
      <Property name="AllowDuplicateScalars" id="5116.AllowDuplicateScalars" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="5116.AllowDuplicateScalars.bool"/>
      </Property>
      <Property name="Points" id="5116.Points" number_of_elements="8">
        <Element index="0" value="1.77678677818044e-06"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0.5"/>
        <Element index="3" value="0"/>
        <Element index="4" value="1.63208877384008e-05"/>
        <Element index="5" value="1"/>
        <Element index="6" value="0.5"/>
        <Element index="7" value="0"/>
      </Property>
      <Property name="ScalarRangeInitialized" id="5116.ScalarRangeInitialized" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5116.ScalarRangeInitialized.bool"/>
      </Property>
    </Proxy>
    <Proxy group="piecewise_functions" type="PiecewiseFunction" id="5117" servers="21">
      <Property name="AllowDuplicateScalars" id="5117.AllowDuplicateScalars" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="5117.AllowDuplicateScalars.bool"/>
      </Property>
      <Property name="Points" id="5117.Points" number_of_elements="8">
        <Element index="0" value="1.77678677818044e-06"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0.5"/>
        <Element index="3" value="0"/>
        <Element index="4" value="1.63208877384008e-05"/>
        <Element index="5" value="1"/>
        <Element index="6" value="0.5"/>
        <Element index="7" value="0"/>
      </Property>
      <Property name="ScalarRangeInitialized" id="5117.ScalarRangeInitialized" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5117.ScalarRangeInitialized.bool"/>
      </Property>
    </Proxy>
    <Proxy group="misc" type="RepresentationAnimationHelper" id="5192" servers="16">
      <Property name="Source" id="5192.Source" number_of_elements="1">
        <Proxy value="5181"/>
      </Property>
    </Proxy>
    <Proxy group="sources" type="ArrowSource" id="5204" servers="1">
      <Property name="Invert" id="5204.Invert" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5204.Invert.bool"/>
      </Property>
      <Property name="ShaftRadius" id="5204.ShaftRadius" number_of_elements="1">
        <Element index="0" value="0.03"/>
        <Domain name="range" id="5204.ShaftRadius.range"/>
      </Property>
      <Property name="ShaftResolution" id="5204.ShaftResolution" number_of_elements="1">
        <Element index="0" value="6"/>
        <Domain name="range" id="5204.ShaftResolution.range"/>
      </Property>
      <Property name="TipLength" id="5204.TipLength" number_of_elements="1">
        <Element index="0" value="0.35"/>
        <Domain name="range" id="5204.TipLength.range"/>
      </Property>
      <Property name="TipRadius" id="5204.TipRadius" number_of_elements="1">
        <Element index="0" value="0.1"/>
        <Domain name="range" id="5204.TipRadius.range"/>
      </Property>
      <Property name="TipResolution" id="5204.TipResolution" number_of_elements="1">
        <Element index="0" value="6"/>
        <Domain name="range" id="5204.TipResolution.range"/>
      </Property>
    </Proxy>
    <Proxy group="sources" type="ConeSource" id="5215" servers="1">
      <Property name="Capping" id="5215.Capping" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="5215.Capping.bool"/>
      </Property>
      <Property name="Center" id="5215.Center" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="5215.Center.range"/>
      </Property>
      <Property name="Direction" id="5215.Direction" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="5215.Direction.range"/>
      </Property>
      <Property name="Height" id="5215.Height" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="5215.Height.range"/>
      </Property>
      <Property name="Radius" id="5215.Radius" number_of_elements="1">
        <Element index="0" value="0.5"/>
        <Domain name="range" id="5215.Radius.range"/>
      </Property>
      <Property name="Resolution" id="5215.Resolution" number_of_elements="1">
        <Element index="0" value="6"/>
        <Domain name="range" id="5215.Resolution.range"/>
      </Property>
    </Proxy>
    <Proxy group="sources" type="CubeSource" id="5226" servers="1">
      <Property name="Center" id="5226.Center" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="5226.Center.range"/>
      </Property>
      <Property name="XLength" id="5226.XLength" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="5226.XLength.range"/>
      </Property>
      <Property name="YLength" id="5226.YLength" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="5226.YLength.range"/>
      </Property>
      <Property name="ZLength" id="5226.ZLength" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="5226.ZLength.range"/>
      </Property>
    </Proxy>
    <Proxy group="sources" type="CylinderSource" id="5237" servers="1">
      <Property name="Capping" id="5237.Capping" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="5237.Capping.bool"/>
      </Property>
      <Property name="Center" id="5237.Center" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="5237.Center.range"/>
      </Property>
      <Property name="Height" id="5237.Height" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="5237.Height.range"/>
      </Property>
      <Property name="Radius" id="5237.Radius" number_of_elements="1">
        <Element index="0" value="0.5"/>
        <Domain name="range" id="5237.Radius.range"/>
      </Property>
      <Property name="Resolution" id="5237.Resolution" number_of_elements="1">
        <Element index="0" value="6"/>
        <Domain name="range" id="5237.Resolution.range"/>
      </Property>
    </Proxy>
    <Proxy group="sources" type="LineSource" id="5248" servers="1">
      <Property name="Point1" id="5248.Point1" number_of_elements="3">
        <Element index="0" value="-0.5"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="5248.Point1.range"/>
      </Property>
      <Property name="Point2" id="5248.Point2" number_of_elements="3">
        <Element index="0" value="0.5"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="5248.Point2.range"/>
      </Property>
      <Property name="Resolution" id="5248.Resolution" number_of_elements="1">
        <Element index="0" value="6"/>
        <Domain name="range" id="5248.Resolution.range"/>
      </Property>
    </Proxy>
    <Proxy group="sources" type="SphereSource" id="5259" servers="1">
      <Property name="Center" id="5259.Center" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="5259.Center.range"/>
      </Property>
      <Property name="EndPhi" id="5259.EndPhi" number_of_elements="1">
        <Element index="0" value="180"/>
        <Domain name="range" id="5259.EndPhi.range"/>
      </Property>
      <Property name="EndTheta" id="5259.EndTheta" number_of_elements="1">
        <Element index="0" value="360"/>
        <Domain name="range" id="5259.EndTheta.range"/>
      </Property>
      <Property name="PhiResolution" id="5259.PhiResolution" number_of_elements="1">
        <Element index="0" value="8"/>
        <Domain name="range" id="5259.PhiResolution.range"/>
      </Property>
      <Property name="Radius" id="5259.Radius" number_of_elements="1">
        <Element index="0" value="0.5"/>
        <Domain name="range" id="5259.Radius.range"/>
      </Property>
      <Property name="StartPhi" id="5259.StartPhi" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="range" id="5259.StartPhi.range"/>
      </Property>
      <Property name="StartTheta" id="5259.StartTheta" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="range" id="5259.StartTheta.range"/>
      </Property>
      <Property name="ThetaResolution" id="5259.ThetaResolution" number_of_elements="1">
        <Element index="0" value="8"/>
        <Domain name="range" id="5259.ThetaResolution.range"/>
      </Property>
    </Proxy>
    <Proxy group="sources" type="GlyphSource2D" id="5270" servers="1">
      <Property name="Center" id="5270.Center" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="5270.Center.range"/>
      </Property>
      <Property name="Filled" id="5270.Filled" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5270.Filled.bool"/>
      </Property>
      <Property name="GlyphType" id="5270.GlyphType" number_of_elements="1">
        <Element index="0" value="9"/>
        <Domain name="enum" id="5270.GlyphType.enum">
          <Entry value="1" text="Vertex"/>
          <Entry value="2" text="Dash"/>
          <Entry value="3" text="Cross"/>
          <Entry value="4" text="ThickCross"/>
          <Entry value="5" text="Triangle"/>
          <Entry value="6" text="Square"/>
          <Entry value="7" text="Circle"/>
          <Entry value="8" text="Diamond"/>
          <Entry value="9" text="Arrow"/>
          <Entry value="10" text="ThickArrow"/>
          <Entry value="11" text="HookedArrow"/>
          <Entry value="12" text="EdgeArrow"/>
        </Domain>
      </Property>
    </Proxy>
    <Proxy group="piecewise_functions" type="PiecewiseFunction" id="5303" servers="21">
      <Property name="AllowDuplicateScalars" id="5303.AllowDuplicateScalars" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="5303.AllowDuplicateScalars.bool"/>
      </Property>
      <Property name="Points" id="5303.Points" number_of_elements="8">
        <Element index="0" value="1.77678677818044e-06"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0.5"/>
        <Element index="3" value="0"/>
        <Element index="4" value="1.63208877384008e-05"/>
        <Element index="5" value="1"/>
        <Element index="6" value="0.5"/>
        <Element index="7" value="0"/>
      </Property>
      <Property name="ScalarRangeInitialized" id="5303.ScalarRangeInitialized" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5303.ScalarRangeInitialized.bool"/>
      </Property>
    </Proxy>
    <Proxy group="piecewise_functions" type="PiecewiseFunction" id="5304" servers="21">
      <Property name="AllowDuplicateScalars" id="5304.AllowDuplicateScalars" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="5304.AllowDuplicateScalars.bool"/>
      </Property>
      <Property name="Points" id="5304.Points" number_of_elements="8">
        <Element index="0" value="1.77678677818044e-06"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0.5"/>
        <Element index="3" value="0"/>
        <Element index="4" value="1.63208877384008e-05"/>
        <Element index="5" value="1"/>
        <Element index="6" value="0.5"/>
        <Element index="7" value="0"/>
      </Property>
      <Property name="ScalarRangeInitialized" id="5304.ScalarRangeInitialized" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5304.ScalarRangeInitialized.bool"/>
      </Property>
    </Proxy>
    <Proxy group="representations" type="GeometryRepresentation" id="4961" servers="21">
      <Property name="CubeAxesVisibility" id="4961.CubeAxesVisibility" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4961.CubeAxesVisibility.bool"/>
      </Property>
      <Property name="Input" id="4961.Input" number_of_elements="1">
        <Proxy value="4698" output_port="0"/>
        <Domain name="input_array_cell" id="4961.Input.input_array_cell"/>
        <Domain name="input_array_point" id="4961.Input.input_array_point"/>
        <Domain name="input_type" id="4961.Input.input_type"/>
      </Property>
      <Property name="Representation" id="4961.Representation" number_of_elements="1">
        <Element index="0" value="Surface"/>
        <Domain name="list" id="4961.Representation.list">
          <String text="3D Glyphs"/>
          <String text="Outline"/>
          <String text="Point Gaussian"/>
          <String text="Points"/>
          <String text="Surface"/>
          <String text="Surface With Edges"/>
          <String text="Wireframe"/>
        </Domain>
      </Property>
      <Property name="RepresentationTypesInfo" id="4961.RepresentationTypesInfo" number_of_elements="7">
        <Element index="0" value="3D Glyphs"/>
        <Element index="1" value="Outline"/>
        <Element index="2" value="Point Gaussian"/>
        <Element index="3" value="Points"/>
        <Element index="4" value="Surface"/>
        <Element index="5" value="Surface With Edges"/>
        <Element index="6" value="Wireframe"/>
      </Property>
      <Property name="SelectionCellFieldDataArrayName" id="4961.SelectionCellFieldDataArrayName" number_of_elements="1">
        <Element index="0" value="vtkOriginalCellIds"/>
        <Domain name="array_list" id="4961.SelectionCellFieldDataArrayName.array_list"/>
      </Property>
      <Property name="SelectionPointFieldDataArrayName" id="4961.SelectionPointFieldDataArrayName" number_of_elements="1">
        <Element index="0" value="vtkOriginalPointIds"/>
        <Domain name="array_list" id="4961.SelectionPointFieldDataArrayName.array_list">
          <String text="Normals"/>
          <String text="TextureCoordinates"/>
        </Domain>
      </Property>
      <Property name="SelectionVisibility" id="4961.SelectionVisibility" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="4961.SelectionVisibility.bool"/>
      </Property>
      <Property name="Visibility" id="4961.Visibility" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4961.Visibility.bool"/>
      </Property>
      <Property name="Ambient" id="4961.Ambient" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="range" id="4961.Ambient.range"/>
      </Property>
      <Property name="AmbientColor" id="4961.AmbientColor" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="1"/>
        <Element index="2" value="1"/>
        <Domain name="range" id="4961.AmbientColor.range"/>
      </Property>
      <Property name="AxesOrigin" id="4961.AxesOrigin" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="4961.AxesOrigin.range"/>
      </Property>
      <Property name="BackfaceAmbientColor" id="4961.BackfaceAmbientColor" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="1"/>
        <Element index="2" value="1"/>
        <Domain name="range" id="4961.BackfaceAmbientColor.range"/>
      </Property>
      <Property name="BackfaceDiffuseColor" id="4961.BackfaceDiffuseColor" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="1"/>
        <Element index="2" value="1"/>
        <Domain name="range" id="4961.BackfaceDiffuseColor.range"/>
      </Property>
      <Property name="BackfaceOpacity" id="4961.BackfaceOpacity" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="4961.BackfaceOpacity.range"/>
      </Property>
      <Property name="BackfaceRepresentation" id="4961.BackfaceRepresentation" number_of_elements="1">
        <Element index="0" value="400"/>
        <Domain name="enum" id="4961.BackfaceRepresentation.enum">
          <Entry value="400" text="Follow Frontface"/>
          <Entry value="401" text="Cull Backface"/>
          <Entry value="402" text="Cull Frontface"/>
          <Entry value="0" text="Points"/>
          <Entry value="1" text="Wireframe"/>
          <Entry value="2" text="Surface"/>
          <Entry value="3" text="Surface With Edges"/>
        </Domain>
      </Property>
      <Property name="BlockColor" id="4961.BlockColor"/>
      <Property name="BlockColorsDistinctValues" id="4961.BlockColorsDistinctValues" number_of_elements="1">
        <Element index="0" value="12"/>
        <Domain name="range" id="4961.BlockColorsDistinctValues.range"/>
      </Property>
      <Property name="BlockOpacity" id="4961.BlockOpacity"/>
      <Property name="BlockVisibility" id="4961.BlockVisibility"/>
      <Property name="CenterStickyAxes" id="4961.CenterStickyAxes" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4961.CenterStickyAxes.bool"/>
      </Property>
      <Property name="Color" id="4961.Color" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="1"/>
        <Element index="2" value="1"/>
        <Domain name="range" id="4961.Color.range"/>
      </Property>
      <Property name="ColorArrayName" id="4961.ColorArrayName" number_of_elements="5">
        <Element index="0" value=""/>
        <Element index="1" value=""/>
        <Element index="2" value=""/>
        <Element index="3" value=""/>
        <Element index="4" value=""/>
        <Domain name="array_list" id="4961.ColorArrayName.array_list">
          <String text="Normals"/>
          <String text="TextureCoordinates"/>
        </Domain>
        <Domain name="field_list" id="4961.ColorArrayName.field_list">
          <Entry value="0" text="Point Data"/>
          <Entry value="1" text="Cell Data"/>
          <Entry value="2" text="Field Data"/>
          <Entry value="4" text="Vertex Data"/>
          <Entry value="5" text="Edge Data"/>
          <Entry value="6" text="Row Data"/>
        </Domain>
      </Property>
      <Property name="CubeAxesColor" id="4961.CubeAxesColor" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="1"/>
        <Element index="2" value="1"/>
        <Domain name="range" id="4961.CubeAxesColor.range"/>
      </Property>
      <Property name="CubeAxesCornerOffset" id="4961.CubeAxesCornerOffset" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="range" id="4961.CubeAxesCornerOffset.range"/>
      </Property>
      <Property name="CubeAxesFlyMode" id="4961.CubeAxesFlyMode" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="enum" id="4961.CubeAxesFlyMode.enum">
          <Entry value="0" text="Outer Edges"/>
          <Entry value="1" text="Closest Triad"/>
          <Entry value="2" text="Furthest Triad"/>
          <Entry value="3" text="Static Triad"/>
          <Entry value="4" text="Static Edges"/>
        </Domain>
      </Property>
      <Property name="CubeAxesGridLineLocation" id="4961.CubeAxesGridLineLocation" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="enum" id="4961.CubeAxesGridLineLocation.enum">
          <Entry value="0" text="All Faces"/>
          <Entry value="1" text="Closest Faces"/>
          <Entry value="2" text="Furthest Faces"/>
        </Domain>
      </Property>
      <Property name="CubeAxesInertia" id="4961.CubeAxesInertia" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="4961.CubeAxesInertia.range"/>
      </Property>
      <Property name="CubeAxesTickLocation" id="4961.CubeAxesTickLocation" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="enum" id="4961.CubeAxesTickLocation.enum">
          <Entry value="0" text="Inside"/>
          <Entry value="1" text="Outside"/>
          <Entry value="2" text="Both"/>
        </Domain>
      </Property>
      <Property name="CubeAxesUseDefaultXTitle" id="4961.CubeAxesUseDefaultXTitle" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="4961.CubeAxesUseDefaultXTitle.bool"/>
      </Property>
      <Property name="CubeAxesUseDefaultYTitle" id="4961.CubeAxesUseDefaultYTitle" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="4961.CubeAxesUseDefaultYTitle.bool"/>
      </Property>
      <Property name="CubeAxesUseDefaultZTitle" id="4961.CubeAxesUseDefaultZTitle" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="4961.CubeAxesUseDefaultZTitle.bool"/>
      </Property>
      <Property name="CubeAxesXAxisMinorTickVisibility" id="4961.CubeAxesXAxisMinorTickVisibility" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="4961.CubeAxesXAxisMinorTickVisibility.bool"/>
      </Property>
      <Property name="CubeAxesXAxisTickVisibility" id="4961.CubeAxesXAxisTickVisibility" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="4961.CubeAxesXAxisTickVisibility.bool"/>
      </Property>
      <Property name="CubeAxesXAxisVisibility" id="4961.CubeAxesXAxisVisibility" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="4961.CubeAxesXAxisVisibility.bool"/>
      </Property>
      <Property name="CubeAxesXGridLines" id="4961.CubeAxesXGridLines" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4961.CubeAxesXGridLines.bool"/>
      </Property>
      <Property name="CubeAxesXLabelFormat" id="4961.CubeAxesXLabelFormat" number_of_elements="1">
        <Element index="0" value="%-#6.3g"/>
      </Property>
      <Property name="CubeAxesXTitle" id="4961.CubeAxesXTitle" number_of_elements="1">
        <Element index="0" value="X-Axis"/>
      </Property>
      <Property name="CubeAxesYAxisMinorTickVisibility" id="4961.CubeAxesYAxisMinorTickVisibility" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="4961.CubeAxesYAxisMinorTickVisibility.bool"/>
      </Property>
      <Property name="CubeAxesYAxisTickVisibility" id="4961.CubeAxesYAxisTickVisibility" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="4961.CubeAxesYAxisTickVisibility.bool"/>
      </Property>
      <Property name="CubeAxesYAxisVisibility" id="4961.CubeAxesYAxisVisibility" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="4961.CubeAxesYAxisVisibility.bool"/>
      </Property>
      <Property name="CubeAxesYGridLines" id="4961.CubeAxesYGridLines" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4961.CubeAxesYGridLines.bool"/>
      </Property>
      <Property name="CubeAxesYLabelFormat" id="4961.CubeAxesYLabelFormat" number_of_elements="1">
        <Element index="0" value="%-#6.3g"/>
      </Property>
      <Property name="CubeAxesYTitle" id="4961.CubeAxesYTitle" number_of_elements="1">
        <Element index="0" value="Y-Axis"/>
      </Property>
      <Property name="CubeAxesZAxisMinorTickVisibility" id="4961.CubeAxesZAxisMinorTickVisibility" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="4961.CubeAxesZAxisMinorTickVisibility.bool"/>
      </Property>
      <Property name="CubeAxesZAxisTickVisibility" id="4961.CubeAxesZAxisTickVisibility" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="4961.CubeAxesZAxisTickVisibility.bool"/>
      </Property>
      <Property name="CubeAxesZAxisVisibility" id="4961.CubeAxesZAxisVisibility" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="4961.CubeAxesZAxisVisibility.bool"/>
      </Property>
      <Property name="CubeAxesZGridLines" id="4961.CubeAxesZGridLines" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4961.CubeAxesZGridLines.bool"/>
      </Property>
      <Property name="CubeAxesZLabelFormat" id="4961.CubeAxesZLabelFormat" number_of_elements="1">
        <Element index="0" value="%-#6.3g"/>
      </Property>
      <Property name="CubeAxesZTitle" id="4961.CubeAxesZTitle" number_of_elements="1">
        <Element index="0" value="Z-Axis"/>
      </Property>
      <Property name="CustomBounds" id="4961.CustomBounds" number_of_elements="6">
        <Element index="0" value="0"/>
        <Element index="1" value="1"/>
        <Element index="2" value="0"/>
        <Element index="3" value="1"/>
        <Element index="4" value="0"/>
        <Element index="5" value="1"/>
      </Property>
      <Property name="CustomBoundsActive" id="4961.CustomBoundsActive" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
      </Property>
      <Property name="CustomRange" id="4961.CustomRange" number_of_elements="6">
        <Element index="0" value="0"/>
        <Element index="1" value="1"/>
        <Element index="2" value="0"/>
        <Element index="3" value="1"/>
        <Element index="4" value="0"/>
        <Element index="5" value="1"/>
      </Property>
      <Property name="CustomRangeActive" id="4961.CustomRangeActive" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
      </Property>
      <Property name="CustomShader" id="4961.CustomShader" number_of_elements="1">
        <Element index="0" value=""/>
      </Property>
      <Property name="DataBounds" id="4961.DataBounds" number_of_elements="6">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Element index="3" value="0"/>
        <Element index="4" value="0"/>
        <Element index="5" value="0"/>
      </Property>
      <Property name="Diffuse" id="4961.Diffuse" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="4961.Diffuse.range"/>
      </Property>
      <Property name="DiffuseColor" id="4961.DiffuseColor" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="1"/>
        <Element index="2" value="1"/>
        <Domain name="range" id="4961.DiffuseColor.range"/>
      </Property>
      <Property name="EdgeColor" id="4961.EdgeColor" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0.5"/>
        <Domain name="range" id="4961.EdgeColor.range"/>
      </Property>
      <Property name="Emissive" id="4961.Emissive" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4961.Emissive.bool"/>
      </Property>
      <Property name="GaussianRadius" id="4961.GaussianRadius" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="range" id="4961.GaussianRadius.range"/>
      </Property>
      <Property name="GlyphType" id="4961.GlyphType" number_of_elements="1">
        <Proxy value="4816" output_port="0"/>
        <Domain name="input_type" id="4961.GlyphType.input_type"/>
        <Domain name="proxy_list" id="4961.GlyphType.proxy_list">
          <Proxy value="4816"/>
          <Proxy value="4827"/>
          <Proxy value="4838"/>
          <Proxy value="4849"/>
          <Proxy value="4860"/>
          <Proxy value="4871"/>
          <Proxy value="4882"/>
        </Domain>
      </Property>
      <Property name="InterpolateScalarsBeforeMapping" id="4961.InterpolateScalarsBeforeMapping" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="4961.InterpolateScalarsBeforeMapping.bool"/>
      </Property>
      <Property name="Interpolation" id="4961.Interpolation" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="enum" id="4961.Interpolation.enum">
          <Entry value="0" text="Flat"/>
          <Entry value="1" text="Gouraud"/>
        </Domain>
      </Property>
      <Property name="LineWidth" id="4961.LineWidth" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="4961.LineWidth.range"/>
      </Property>
      <Property name="LookupTable" id="4961.LookupTable">
        <Domain name="groups" id="4961.LookupTable.groups"/>
      </Property>
      <Property name="MapScalars" id="4961.MapScalars" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="4961.MapScalars.bool"/>
      </Property>
      <Property name="Masking" id="4961.Masking" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4961.Masking.bool"/>
      </Property>
      <Property name="MeshVisibility" id="4961.MeshVisibility" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4961.MeshVisibility.bool"/>
      </Property>
      <Property name="NonlinearSubdivisionLevel" id="4961.NonlinearSubdivisionLevel" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="4961.NonlinearSubdivisionLevel.range"/>
      </Property>
      <Property name="Opacity" id="4961.Opacity" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="4961.Opacity.range"/>
      </Property>
      <Property name="OpacityArray" id="4961.OpacityArray" number_of_elements="5">
        <Element index="0" value=""/>
        <Element index="1" value=""/>
        <Element index="2" value=""/>
        <Element index="3" value=""/>
        <Element index="4" value=""/>
        <Domain name="array_list" id="4961.OpacityArray.array_list"/>
      </Property>
      <Property name="OpacityByArray" id="4961.OpacityByArray" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4961.OpacityByArray.bool"/>
      </Property>
      <Property name="OpacityTransferFunction" id="4961.OpacityTransferFunction" number_of_elements="1">
        <Proxy value="4915"/>
        <Domain name="groups" id="4961.OpacityTransferFunction.groups"/>
        <Domain name="proxy_list" id="4961.OpacityTransferFunction.proxy_list">
          <Proxy value="4915"/>
        </Domain>
      </Property>
      <Property name="Orient" id="4961.Orient" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4961.Orient.bool"/>
      </Property>
      <Property name="Orientation" id="4961.Orientation" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="4961.Orientation.range"/>
      </Property>
      <Property name="OrientationMode" id="4961.OrientationMode" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="enum" id="4961.OrientationMode.enum">
          <Entry value="0" text="Direction"/>
          <Entry value="1" text="Rotation"/>
        </Domain>
      </Property>
      <Property name="Origin" id="4961.Origin" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="4961.Origin.range"/>
      </Property>
      <Property name="OriginalBoundsRangeActive" id="4961.OriginalBoundsRangeActive" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
      </Property>
      <Property name="Pickable" id="4961.Pickable" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="4961.Pickable.bool"/>
      </Property>
      <Property name="PointSize" id="4961.PointSize" number_of_elements="1">
        <Element index="0" value="2"/>
        <Domain name="range" id="4961.PointSize.range"/>
      </Property>
      <Property name="Position" id="4961.Position" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="4961.Position.range"/>
      </Property>
      <Property name="Scale" id="4961.Scale" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="1"/>
        <Element index="2" value="1"/>
        <Domain name="range" id="4961.Scale.range"/>
      </Property>
      <Property name="ScaleByArray" id="4961.ScaleByArray" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4961.ScaleByArray.bool"/>
      </Property>
      <Property name="ScaleFactor" id="4961.ScaleFactor" number_of_elements="1">
        <Element index="0" value="-2e+298"/>
        <Domain name="bounds" id="4961.ScaleFactor.bounds"/>
        <Domain name="scalar_range" id="4961.ScaleFactor.scalar_range"/>
        <Domain name="vector_range" id="4961.ScaleFactor.vector_range"/>
      </Property>
      <Property name="ScaleMode" id="4961.ScaleMode" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="enum" id="4961.ScaleMode.enum">
          <Entry value="0" text="No Data Scaling Off"/>
          <Entry value="1" text="Magnitude"/>
          <Entry value="2" text="Vector Components"/>
        </Domain>
      </Property>
      <Property name="ScaleTransferFunction" id="4961.ScaleTransferFunction" number_of_elements="1">
        <Proxy value="4916"/>
        <Domain name="groups" id="4961.ScaleTransferFunction.groups"/>
        <Domain name="proxy_list" id="4961.ScaleTransferFunction.proxy_list">
          <Proxy value="4916"/>
        </Domain>
      </Property>
      <Property name="Scaling" id="4961.Scaling" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4961.Scaling.bool"/>
      </Property>
      <Property name="SelectMaskArray" id="4961.SelectMaskArray" number_of_elements="1">
        <Element index="0" value=""/>
      </Property>
      <Property name="SelectOrientationVectors" id="4961.SelectOrientationVectors" number_of_elements="1">
        <Element index="0" value=""/>
      </Property>
      <Property name="SelectScaleArray" id="4961.SelectScaleArray" number_of_elements="1">
        <Element index="0" value=""/>
      </Property>
      <Property name="SelectionCellLabelBold" id="4961.SelectionCellLabelBold" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4961.SelectionCellLabelBold.bool"/>
      </Property>
      <Property name="SelectionCellLabelColor" id="4961.SelectionCellLabelColor" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="1"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="4961.SelectionCellLabelColor.range"/>
      </Property>
      <Property name="SelectionCellLabelFontFamily" id="4961.SelectionCellLabelFontFamily" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="enum" id="4961.SelectionCellLabelFontFamily.enum">
          <Entry value="0" text="Arial"/>
          <Entry value="1" text="Courier"/>
          <Entry value="2" text="Times"/>
        </Domain>
      </Property>
      <Property name="SelectionCellLabelFontSize" id="4961.SelectionCellLabelFontSize" number_of_elements="1">
        <Element index="0" value="18"/>
        <Domain name="range" id="4961.SelectionCellLabelFontSize.range"/>
      </Property>
      <Property name="SelectionCellLabelFormat" id="4961.SelectionCellLabelFormat" number_of_elements="1">
        <Element index="0" value=""/>
      </Property>
      <Property name="SelectionCellLabelItalic" id="4961.SelectionCellLabelItalic" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4961.SelectionCellLabelItalic.bool"/>
      </Property>
      <Property name="SelectionCellLabelJustification" id="4961.SelectionCellLabelJustification" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="enum" id="4961.SelectionCellLabelJustification.enum">
          <Entry value="0" text="Left"/>
          <Entry value="1" text="Center"/>
          <Entry value="2" text="Right"/>
        </Domain>
      </Property>
      <Property name="SelectionCellLabelOpacity" id="4961.SelectionCellLabelOpacity" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="4961.SelectionCellLabelOpacity.range"/>
      </Property>
      <Property name="SelectionCellLabelShadow" id="4961.SelectionCellLabelShadow" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4961.SelectionCellLabelShadow.bool"/>
      </Property>
      <Property name="SelectionCellLabelVisibility" id="4961.SelectionCellLabelVisibility" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4961.SelectionCellLabelVisibility.bool"/>
      </Property>
      <Property name="SelectionColor" id="4961.SelectionColor" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="0"/>
        <Element index="2" value="1"/>
        <Domain name="range" id="4961.SelectionColor.range"/>
      </Property>
      <Property name="SelectionLineWidth" id="4961.SelectionLineWidth" number_of_elements="1">
        <Element index="0" value="2"/>
        <Domain name="range" id="4961.SelectionLineWidth.range"/>
      </Property>
      <Property name="SelectionOpacity" id="4961.SelectionOpacity" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="4961.SelectionOpacity.range"/>
      </Property>
      <Property name="SelectionPointLabelBold" id="4961.SelectionPointLabelBold" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4961.SelectionPointLabelBold.bool"/>
      </Property>
      <Property name="SelectionPointLabelColor" id="4961.SelectionPointLabelColor" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="1"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="4961.SelectionPointLabelColor.range"/>
      </Property>
      <Property name="SelectionPointLabelFontFamily" id="4961.SelectionPointLabelFontFamily" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="enum" id="4961.SelectionPointLabelFontFamily.enum">
          <Entry value="0" text="Arial"/>
          <Entry value="1" text="Courier"/>
          <Entry value="2" text="Times"/>
        </Domain>
      </Property>
      <Property name="SelectionPointLabelFontSize" id="4961.SelectionPointLabelFontSize" number_of_elements="1">
        <Element index="0" value="18"/>
        <Domain name="range" id="4961.SelectionPointLabelFontSize.range"/>
      </Property>
      <Property name="SelectionPointLabelFormat" id="4961.SelectionPointLabelFormat" number_of_elements="1">
        <Element index="0" value=""/>
      </Property>
      <Property name="SelectionPointLabelItalic" id="4961.SelectionPointLabelItalic" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4961.SelectionPointLabelItalic.bool"/>
      </Property>
      <Property name="SelectionPointLabelJustification" id="4961.SelectionPointLabelJustification" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="enum" id="4961.SelectionPointLabelJustification.enum">
          <Entry value="0" text="Left"/>
          <Entry value="1" text="Center"/>
          <Entry value="2" text="Right"/>
        </Domain>
      </Property>
      <Property name="SelectionPointLabelOpacity" id="4961.SelectionPointLabelOpacity" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="4961.SelectionPointLabelOpacity.range"/>
      </Property>
      <Property name="SelectionPointLabelShadow" id="4961.SelectionPointLabelShadow" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4961.SelectionPointLabelShadow.bool"/>
      </Property>
      <Property name="SelectionPointLabelVisibility" id="4961.SelectionPointLabelVisibility" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4961.SelectionPointLabelVisibility.bool"/>
      </Property>
      <Property name="SelectionPointSize" id="4961.SelectionPointSize" number_of_elements="1">
        <Element index="0" value="5"/>
        <Domain name="range" id="4961.SelectionPointSize.range"/>
      </Property>
      <Property name="SelectionRepresentation" id="4961.SelectionRepresentation" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="enum" id="4961.SelectionRepresentation.enum">
          <Entry value="0" text="Points"/>
          <Entry value="1" text="Wireframe"/>
          <Entry value="2" text="Surface"/>
        </Domain>
      </Property>
      <Property name="SelectionUseOutline" id="4961.SelectionUseOutline" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4961.SelectionUseOutline.bool"/>
      </Property>
      <Property name="SetScaleArray" id="4961.SetScaleArray" number_of_elements="5">
        <Element index="0" value=""/>
        <Element index="1" value=""/>
        <Element index="2" value=""/>
        <Element index="3" value=""/>
        <Element index="4" value=""/>
        <Domain name="array_list" id="4961.SetScaleArray.array_list"/>
      </Property>
      <Property name="ShaderPreset" id="4961.ShaderPreset" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="enum" id="4961.ShaderPreset.enum">
          <Entry value="0" text="Gaussian Blur (Default)"/>
          <Entry value="1" text="Sphere"/>
          <Entry value="2" text="Black-edged circle"/>
          <Entry value="3" text="Plain circle"/>
          <Entry value="4" text="Triangle"/>
          <Entry value="5" text="Square Outline"/>
        </Domain>
      </Property>
      <Property name="Specular" id="4961.Specular" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="range" id="4961.Specular.range"/>
      </Property>
      <Property name="SpecularColor" id="4961.SpecularColor" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="1"/>
        <Element index="2" value="1"/>
        <Domain name="range" id="4961.SpecularColor.range"/>
      </Property>
      <Property name="SpecularPower" id="4961.SpecularPower" number_of_elements="1">
        <Element index="0" value="100"/>
        <Domain name="range" id="4961.SpecularPower.range"/>
      </Property>
      <Property name="StaticMode" id="4961.StaticMode" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4961.StaticMode.bool"/>
      </Property>
      <Property name="StickyAxes" id="4961.StickyAxes" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4961.StickyAxes.bool"/>
      </Property>
      <Property name="SuppressLOD" id="4961.SuppressLOD" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4961.SuppressLOD.bool"/>
      </Property>
      <Property name="Texture" id="4961.Texture">
        <Domain name="groups" id="4961.Texture.groups"/>
      </Property>
      <Property name="Triangulate" id="4961.Triangulate" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4961.Triangulate.bool"/>
      </Property>
      <Property name="UseAxesOrigin" id="4961.UseAxesOrigin" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4961.UseAxesOrigin.bool"/>
      </Property>
      <Property name="UserTransform" id="4961.UserTransform" number_of_elements="16">
        <Element index="0" value="1"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Element index="3" value="0"/>
        <Element index="4" value="0"/>
        <Element index="5" value="1"/>
        <Element index="6" value="0"/>
        <Element index="7" value="0"/>
        <Element index="8" value="0"/>
        <Element index="9" value="0"/>
        <Element index="10" value="1"/>
        <Element index="11" value="0"/>
        <Element index="12" value="0"/>
        <Element index="13" value="0"/>
        <Element index="14" value="0"/>
        <Element index="15" value="1"/>
      </Property>
    </Proxy>
    <Proxy group="representations" type="GeometryRepresentation" id="5162" servers="21">
      <Property name="CubeAxesVisibility" id="5162.CubeAxesVisibility" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5162.CubeAxesVisibility.bool"/>
      </Property>
      <Property name="Input" id="5162.Input" number_of_elements="1">
        <Proxy value="4994" output_port="0"/>
        <Domain name="input_array_cell" id="5162.Input.input_array_cell"/>
        <Domain name="input_array_point" id="5162.Input.input_array_point"/>
        <Domain name="input_type" id="5162.Input.input_type"/>
      </Property>
      <Property name="Representation" id="5162.Representation" number_of_elements="1">
        <Element index="0" value="Surface"/>
        <Domain name="list" id="5162.Representation.list">
          <String text="3D Glyphs"/>
          <String text="Outline"/>
          <String text="Point Gaussian"/>
          <String text="Points"/>
          <String text="Surface"/>
          <String text="Surface With Edges"/>
          <String text="Wireframe"/>
        </Domain>
      </Property>
      <Property name="RepresentationTypesInfo" id="5162.RepresentationTypesInfo" number_of_elements="7">
        <Element index="0" value="3D Glyphs"/>
        <Element index="1" value="Outline"/>
        <Element index="2" value="Point Gaussian"/>
        <Element index="3" value="Points"/>
        <Element index="4" value="Surface"/>
        <Element index="5" value="Surface With Edges"/>
        <Element index="6" value="Wireframe"/>
      </Property>
      <Property name="SelectionCellFieldDataArrayName" id="5162.SelectionCellFieldDataArrayName" number_of_elements="1">
        <Element index="0" value="vtkOriginalCellIds"/>
        <Domain name="array_list" id="5162.SelectionCellFieldDataArrayName.array_list"/>
      </Property>
      <Property name="SelectionPointFieldDataArrayName" id="5162.SelectionPointFieldDataArrayName" number_of_elements="1">
        <Element index="0" value="Normals"/>
        <Domain name="array_list" id="5162.SelectionPointFieldDataArrayName.array_list">
          <String text="Normals"/>
          <String text="TextureCoordinates"/>
          <String text="V"/>
        </Domain>
      </Property>
      <Property name="SelectionVisibility" id="5162.SelectionVisibility" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="5162.SelectionVisibility.bool"/>
      </Property>
      <Property name="Visibility" id="5162.Visibility" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5162.Visibility.bool"/>
      </Property>
      <Property name="Ambient" id="5162.Ambient" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="range" id="5162.Ambient.range"/>
      </Property>
      <Property name="AmbientColor" id="5162.AmbientColor" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="1"/>
        <Element index="2" value="1"/>
        <Domain name="range" id="5162.AmbientColor.range"/>
      </Property>
      <Property name="AxesOrigin" id="5162.AxesOrigin" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="5162.AxesOrigin.range"/>
      </Property>
      <Property name="BackfaceAmbientColor" id="5162.BackfaceAmbientColor" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="1"/>
        <Element index="2" value="1"/>
        <Domain name="range" id="5162.BackfaceAmbientColor.range"/>
      </Property>
      <Property name="BackfaceDiffuseColor" id="5162.BackfaceDiffuseColor" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="1"/>
        <Element index="2" value="1"/>
        <Domain name="range" id="5162.BackfaceDiffuseColor.range"/>
      </Property>
      <Property name="BackfaceOpacity" id="5162.BackfaceOpacity" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="5162.BackfaceOpacity.range"/>
      </Property>
      <Property name="BackfaceRepresentation" id="5162.BackfaceRepresentation" number_of_elements="1">
        <Element index="0" value="400"/>
        <Domain name="enum" id="5162.BackfaceRepresentation.enum">
          <Entry value="400" text="Follow Frontface"/>
          <Entry value="401" text="Cull Backface"/>
          <Entry value="402" text="Cull Frontface"/>
          <Entry value="0" text="Points"/>
          <Entry value="1" text="Wireframe"/>
          <Entry value="2" text="Surface"/>
          <Entry value="3" text="Surface With Edges"/>
        </Domain>
      </Property>
      <Property name="BlockColor" id="5162.BlockColor"/>
      <Property name="BlockColorsDistinctValues" id="5162.BlockColorsDistinctValues" number_of_elements="1">
        <Element index="0" value="12"/>
        <Domain name="range" id="5162.BlockColorsDistinctValues.range"/>
      </Property>
      <Property name="BlockOpacity" id="5162.BlockOpacity"/>
      <Property name="BlockVisibility" id="5162.BlockVisibility"/>
      <Property name="CenterStickyAxes" id="5162.CenterStickyAxes" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5162.CenterStickyAxes.bool"/>
      </Property>
      <Property name="Color" id="5162.Color" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="1"/>
        <Element index="2" value="1"/>
        <Domain name="range" id="5162.Color.range"/>
      </Property>
      <Property name="ColorArrayName" id="5162.ColorArrayName" number_of_elements="5">
        <Element index="0" value=""/>
        <Element index="1" value=""/>
        <Element index="2" value=""/>
        <Element index="3" value="0"/>
        <Element index="4" value="V"/>
        <Domain name="array_list" id="5162.ColorArrayName.array_list">
          <String text="Normals"/>
          <String text="TextureCoordinates"/>
          <String text="V"/>
        </Domain>
        <Domain name="field_list" id="5162.ColorArrayName.field_list">
          <Entry value="0" text="Point Data"/>
          <Entry value="1" text="Cell Data"/>
          <Entry value="2" text="Field Data"/>
          <Entry value="4" text="Vertex Data"/>
          <Entry value="5" text="Edge Data"/>
          <Entry value="6" text="Row Data"/>
        </Domain>
      </Property>
      <Property name="CubeAxesColor" id="5162.CubeAxesColor" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="1"/>
        <Element index="2" value="1"/>
        <Domain name="range" id="5162.CubeAxesColor.range"/>
      </Property>
      <Property name="CubeAxesCornerOffset" id="5162.CubeAxesCornerOffset" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="range" id="5162.CubeAxesCornerOffset.range"/>
      </Property>
      <Property name="CubeAxesFlyMode" id="5162.CubeAxesFlyMode" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="enum" id="5162.CubeAxesFlyMode.enum">
          <Entry value="0" text="Outer Edges"/>
          <Entry value="1" text="Closest Triad"/>
          <Entry value="2" text="Furthest Triad"/>
          <Entry value="3" text="Static Triad"/>
          <Entry value="4" text="Static Edges"/>
        </Domain>
      </Property>
      <Property name="CubeAxesGridLineLocation" id="5162.CubeAxesGridLineLocation" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="enum" id="5162.CubeAxesGridLineLocation.enum">
          <Entry value="0" text="All Faces"/>
          <Entry value="1" text="Closest Faces"/>
          <Entry value="2" text="Furthest Faces"/>
        </Domain>
      </Property>
      <Property name="CubeAxesInertia" id="5162.CubeAxesInertia" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="5162.CubeAxesInertia.range"/>
      </Property>
      <Property name="CubeAxesTickLocation" id="5162.CubeAxesTickLocation" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="enum" id="5162.CubeAxesTickLocation.enum">
          <Entry value="0" text="Inside"/>
          <Entry value="1" text="Outside"/>
          <Entry value="2" text="Both"/>
        </Domain>
      </Property>
      <Property name="CubeAxesUseDefaultXTitle" id="5162.CubeAxesUseDefaultXTitle" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="5162.CubeAxesUseDefaultXTitle.bool"/>
      </Property>
      <Property name="CubeAxesUseDefaultYTitle" id="5162.CubeAxesUseDefaultYTitle" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="5162.CubeAxesUseDefaultYTitle.bool"/>
      </Property>
      <Property name="CubeAxesUseDefaultZTitle" id="5162.CubeAxesUseDefaultZTitle" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="5162.CubeAxesUseDefaultZTitle.bool"/>
      </Property>
      <Property name="CubeAxesXAxisMinorTickVisibility" id="5162.CubeAxesXAxisMinorTickVisibility" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="5162.CubeAxesXAxisMinorTickVisibility.bool"/>
      </Property>
      <Property name="CubeAxesXAxisTickVisibility" id="5162.CubeAxesXAxisTickVisibility" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="5162.CubeAxesXAxisTickVisibility.bool"/>
      </Property>
      <Property name="CubeAxesXAxisVisibility" id="5162.CubeAxesXAxisVisibility" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="5162.CubeAxesXAxisVisibility.bool"/>
      </Property>
      <Property name="CubeAxesXGridLines" id="5162.CubeAxesXGridLines" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5162.CubeAxesXGridLines.bool"/>
      </Property>
      <Property name="CubeAxesXLabelFormat" id="5162.CubeAxesXLabelFormat" number_of_elements="1">
        <Element index="0" value="%-#6.3g"/>
      </Property>
      <Property name="CubeAxesXTitle" id="5162.CubeAxesXTitle" number_of_elements="1">
        <Element index="0" value="X-Axis"/>
      </Property>
      <Property name="CubeAxesYAxisMinorTickVisibility" id="5162.CubeAxesYAxisMinorTickVisibility" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="5162.CubeAxesYAxisMinorTickVisibility.bool"/>
      </Property>
      <Property name="CubeAxesYAxisTickVisibility" id="5162.CubeAxesYAxisTickVisibility" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="5162.CubeAxesYAxisTickVisibility.bool"/>
      </Property>
      <Property name="CubeAxesYAxisVisibility" id="5162.CubeAxesYAxisVisibility" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="5162.CubeAxesYAxisVisibility.bool"/>
      </Property>
      <Property name="CubeAxesYGridLines" id="5162.CubeAxesYGridLines" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5162.CubeAxesYGridLines.bool"/>
      </Property>
      <Property name="CubeAxesYLabelFormat" id="5162.CubeAxesYLabelFormat" number_of_elements="1">
        <Element index="0" value="%-#6.3g"/>
      </Property>
      <Property name="CubeAxesYTitle" id="5162.CubeAxesYTitle" number_of_elements="1">
        <Element index="0" value="Y-Axis"/>
      </Property>
      <Property name="CubeAxesZAxisMinorTickVisibility" id="5162.CubeAxesZAxisMinorTickVisibility" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="5162.CubeAxesZAxisMinorTickVisibility.bool"/>
      </Property>
      <Property name="CubeAxesZAxisTickVisibility" id="5162.CubeAxesZAxisTickVisibility" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="5162.CubeAxesZAxisTickVisibility.bool"/>
      </Property>
      <Property name="CubeAxesZAxisVisibility" id="5162.CubeAxesZAxisVisibility" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="5162.CubeAxesZAxisVisibility.bool"/>
      </Property>
      <Property name="CubeAxesZGridLines" id="5162.CubeAxesZGridLines" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5162.CubeAxesZGridLines.bool"/>
      </Property>
      <Property name="CubeAxesZLabelFormat" id="5162.CubeAxesZLabelFormat" number_of_elements="1">
        <Element index="0" value="%-#6.3g"/>
      </Property>
      <Property name="CubeAxesZTitle" id="5162.CubeAxesZTitle" number_of_elements="1">
        <Element index="0" value="Z-Axis"/>
      </Property>
      <Property name="CustomBounds" id="5162.CustomBounds" number_of_elements="6">
        <Element index="0" value="0"/>
        <Element index="1" value="1"/>
        <Element index="2" value="0"/>
        <Element index="3" value="1"/>
        <Element index="4" value="0"/>
        <Element index="5" value="1"/>
      </Property>
      <Property name="CustomBoundsActive" id="5162.CustomBoundsActive" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
      </Property>
      <Property name="CustomRange" id="5162.CustomRange" number_of_elements="6">
        <Element index="0" value="0"/>
        <Element index="1" value="1"/>
        <Element index="2" value="0"/>
        <Element index="3" value="1"/>
        <Element index="4" value="0"/>
        <Element index="5" value="1"/>
      </Property>
      <Property name="CustomRangeActive" id="5162.CustomRangeActive" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
      </Property>
      <Property name="CustomShader" id="5162.CustomShader" number_of_elements="1">
        <Element index="0" value=""/>
      </Property>
      <Property name="DataBounds" id="5162.DataBounds" number_of_elements="6">
        <Element index="0" value="1.58101006669199e-322"/>
        <Element index="1" value="3.71447959553346e-316"/>
        <Element index="2" value="6.91928321587424e-310"/>
        <Element index="3" value="0"/>
        <Element index="4" value="6.37344683135208e-322"/>
        <Element index="5" value="3.71451279674486e-316"/>
      </Property>
      <Property name="Diffuse" id="5162.Diffuse" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="5162.Diffuse.range"/>
      </Property>
      <Property name="DiffuseColor" id="5162.DiffuseColor" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="1"/>
        <Element index="2" value="1"/>
        <Domain name="range" id="5162.DiffuseColor.range"/>
      </Property>
      <Property name="EdgeColor" id="5162.EdgeColor" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0.5"/>
        <Domain name="range" id="5162.EdgeColor.range"/>
      </Property>
      <Property name="Emissive" id="5162.Emissive" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5162.Emissive.bool"/>
      </Property>
      <Property name="GaussianRadius" id="5162.GaussianRadius" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="range" id="5162.GaussianRadius.range"/>
      </Property>
      <Property name="GlyphType" id="5162.GlyphType" number_of_elements="1">
        <Proxy value="5017" output_port="0"/>
        <Domain name="input_type" id="5162.GlyphType.input_type"/>
        <Domain name="proxy_list" id="5162.GlyphType.proxy_list">
          <Proxy value="5017"/>
          <Proxy value="5028"/>
          <Proxy value="5039"/>
          <Proxy value="5050"/>
          <Proxy value="5061"/>
          <Proxy value="5072"/>
          <Proxy value="5083"/>
        </Domain>
      </Property>
      <Property name="InterpolateScalarsBeforeMapping" id="5162.InterpolateScalarsBeforeMapping" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="5162.InterpolateScalarsBeforeMapping.bool"/>
      </Property>
      <Property name="Interpolation" id="5162.Interpolation" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="enum" id="5162.Interpolation.enum">
          <Entry value="0" text="Flat"/>
          <Entry value="1" text="Gouraud"/>
        </Domain>
      </Property>
      <Property name="LineWidth" id="5162.LineWidth" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="5162.LineWidth.range"/>
      </Property>
      <Property name="LookupTable" id="5162.LookupTable" number_of_elements="1">
        <Proxy value="5174"/>
        <Domain name="groups" id="5162.LookupTable.groups"/>
      </Property>
      <Property name="MapScalars" id="5162.MapScalars" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="5162.MapScalars.bool"/>
      </Property>
      <Property name="Masking" id="5162.Masking" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5162.Masking.bool"/>
      </Property>
      <Property name="MeshVisibility" id="5162.MeshVisibility" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5162.MeshVisibility.bool"/>
      </Property>
      <Property name="NonlinearSubdivisionLevel" id="5162.NonlinearSubdivisionLevel" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="5162.NonlinearSubdivisionLevel.range"/>
      </Property>
      <Property name="Opacity" id="5162.Opacity" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="5162.Opacity.range"/>
      </Property>
      <Property name="OpacityArray" id="5162.OpacityArray" number_of_elements="5">
        <Element index="0" value=""/>
        <Element index="1" value=""/>
        <Element index="2" value=""/>
        <Element index="3" value=""/>
        <Element index="4" value=""/>
        <Domain name="array_list" id="5162.OpacityArray.array_list"/>
      </Property>
      <Property name="OpacityByArray" id="5162.OpacityByArray" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5162.OpacityByArray.bool"/>
      </Property>
      <Property name="OpacityTransferFunction" id="5162.OpacityTransferFunction" number_of_elements="1">
        <Proxy value="5116"/>
        <Domain name="groups" id="5162.OpacityTransferFunction.groups"/>
        <Domain name="proxy_list" id="5162.OpacityTransferFunction.proxy_list">
          <Proxy value="5116"/>
        </Domain>
      </Property>
      <Property name="Orient" id="5162.Orient" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5162.Orient.bool"/>
      </Property>
      <Property name="Orientation" id="5162.Orientation" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="5162.Orientation.range"/>
      </Property>
      <Property name="OrientationMode" id="5162.OrientationMode" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="enum" id="5162.OrientationMode.enum">
          <Entry value="0" text="Direction"/>
          <Entry value="1" text="Rotation"/>
        </Domain>
      </Property>
      <Property name="Origin" id="5162.Origin" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="5162.Origin.range"/>
      </Property>
      <Property name="OriginalBoundsRangeActive" id="5162.OriginalBoundsRangeActive" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
      </Property>
      <Property name="Pickable" id="5162.Pickable" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="5162.Pickable.bool"/>
      </Property>
      <Property name="PointSize" id="5162.PointSize" number_of_elements="1">
        <Element index="0" value="2"/>
        <Domain name="range" id="5162.PointSize.range"/>
      </Property>
      <Property name="Position" id="5162.Position" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="5162.Position.range"/>
      </Property>
      <Property name="Scale" id="5162.Scale" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="1"/>
        <Element index="2" value="1"/>
        <Domain name="range" id="5162.Scale.range"/>
      </Property>
      <Property name="ScaleByArray" id="5162.ScaleByArray" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5162.ScaleByArray.bool"/>
      </Property>
      <Property name="ScaleFactor" id="5162.ScaleFactor" number_of_elements="1">
        <Element index="0" value="0.1"/>
        <Domain name="bounds" id="5162.ScaleFactor.bounds"/>
        <Domain name="scalar_range" id="5162.ScaleFactor.scalar_range"/>
        <Domain name="vector_range" id="5162.ScaleFactor.vector_range"/>
      </Property>
      <Property name="ScaleMode" id="5162.ScaleMode" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="enum" id="5162.ScaleMode.enum">
          <Entry value="0" text="No Data Scaling Off"/>
          <Entry value="1" text="Magnitude"/>
          <Entry value="2" text="Vector Components"/>
        </Domain>
      </Property>
      <Property name="ScaleTransferFunction" id="5162.ScaleTransferFunction" number_of_elements="1">
        <Proxy value="5117"/>
        <Domain name="groups" id="5162.ScaleTransferFunction.groups"/>
        <Domain name="proxy_list" id="5162.ScaleTransferFunction.proxy_list">
          <Proxy value="5117"/>
        </Domain>
      </Property>
      <Property name="Scaling" id="5162.Scaling" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5162.Scaling.bool"/>
      </Property>
      <Property name="SelectMaskArray" id="5162.SelectMaskArray" number_of_elements="1">
        <Element index="0" value=""/>
      </Property>
      <Property name="SelectOrientationVectors" id="5162.SelectOrientationVectors" number_of_elements="1">
        <Element index="0" value=""/>
      </Property>
      <Property name="SelectScaleArray" id="5162.SelectScaleArray" number_of_elements="1">
        <Element index="0" value=""/>
      </Property>
      <Property name="SelectionCellLabelBold" id="5162.SelectionCellLabelBold" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5162.SelectionCellLabelBold.bool"/>
      </Property>
      <Property name="SelectionCellLabelColor" id="5162.SelectionCellLabelColor" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="1"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="5162.SelectionCellLabelColor.range"/>
      </Property>
      <Property name="SelectionCellLabelFontFamily" id="5162.SelectionCellLabelFontFamily" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="enum" id="5162.SelectionCellLabelFontFamily.enum">
          <Entry value="0" text="Arial"/>
          <Entry value="1" text="Courier"/>
          <Entry value="2" text="Times"/>
        </Domain>
      </Property>
      <Property name="SelectionCellLabelFontSize" id="5162.SelectionCellLabelFontSize" number_of_elements="1">
        <Element index="0" value="18"/>
        <Domain name="range" id="5162.SelectionCellLabelFontSize.range"/>
      </Property>
      <Property name="SelectionCellLabelFormat" id="5162.SelectionCellLabelFormat" number_of_elements="1">
        <Element index="0" value=""/>
      </Property>
      <Property name="SelectionCellLabelItalic" id="5162.SelectionCellLabelItalic" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5162.SelectionCellLabelItalic.bool"/>
      </Property>
      <Property name="SelectionCellLabelJustification" id="5162.SelectionCellLabelJustification" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="enum" id="5162.SelectionCellLabelJustification.enum">
          <Entry value="0" text="Left"/>
          <Entry value="1" text="Center"/>
          <Entry value="2" text="Right"/>
        </Domain>
      </Property>
      <Property name="SelectionCellLabelOpacity" id="5162.SelectionCellLabelOpacity" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="5162.SelectionCellLabelOpacity.range"/>
      </Property>
      <Property name="SelectionCellLabelShadow" id="5162.SelectionCellLabelShadow" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5162.SelectionCellLabelShadow.bool"/>
      </Property>
      <Property name="SelectionCellLabelVisibility" id="5162.SelectionCellLabelVisibility" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5162.SelectionCellLabelVisibility.bool"/>
      </Property>
      <Property name="SelectionColor" id="5162.SelectionColor" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="0"/>
        <Element index="2" value="1"/>
        <Domain name="range" id="5162.SelectionColor.range"/>
      </Property>
      <Property name="SelectionLineWidth" id="5162.SelectionLineWidth" number_of_elements="1">
        <Element index="0" value="2"/>
        <Domain name="range" id="5162.SelectionLineWidth.range"/>
      </Property>
      <Property name="SelectionOpacity" id="5162.SelectionOpacity" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="5162.SelectionOpacity.range"/>
      </Property>
      <Property name="SelectionPointLabelBold" id="5162.SelectionPointLabelBold" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5162.SelectionPointLabelBold.bool"/>
      </Property>
      <Property name="SelectionPointLabelColor" id="5162.SelectionPointLabelColor" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="1"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="5162.SelectionPointLabelColor.range"/>
      </Property>
      <Property name="SelectionPointLabelFontFamily" id="5162.SelectionPointLabelFontFamily" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="enum" id="5162.SelectionPointLabelFontFamily.enum">
          <Entry value="0" text="Arial"/>
          <Entry value="1" text="Courier"/>
          <Entry value="2" text="Times"/>
        </Domain>
      </Property>
      <Property name="SelectionPointLabelFontSize" id="5162.SelectionPointLabelFontSize" number_of_elements="1">
        <Element index="0" value="18"/>
        <Domain name="range" id="5162.SelectionPointLabelFontSize.range"/>
      </Property>
      <Property name="SelectionPointLabelFormat" id="5162.SelectionPointLabelFormat" number_of_elements="1">
        <Element index="0" value=""/>
      </Property>
      <Property name="SelectionPointLabelItalic" id="5162.SelectionPointLabelItalic" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5162.SelectionPointLabelItalic.bool"/>
      </Property>
      <Property name="SelectionPointLabelJustification" id="5162.SelectionPointLabelJustification" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="enum" id="5162.SelectionPointLabelJustification.enum">
          <Entry value="0" text="Left"/>
          <Entry value="1" text="Center"/>
          <Entry value="2" text="Right"/>
        </Domain>
      </Property>
      <Property name="SelectionPointLabelOpacity" id="5162.SelectionPointLabelOpacity" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="5162.SelectionPointLabelOpacity.range"/>
      </Property>
      <Property name="SelectionPointLabelShadow" id="5162.SelectionPointLabelShadow" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5162.SelectionPointLabelShadow.bool"/>
      </Property>
      <Property name="SelectionPointLabelVisibility" id="5162.SelectionPointLabelVisibility" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5162.SelectionPointLabelVisibility.bool"/>
      </Property>
      <Property name="SelectionPointSize" id="5162.SelectionPointSize" number_of_elements="1">
        <Element index="0" value="5"/>
        <Domain name="range" id="5162.SelectionPointSize.range"/>
      </Property>
      <Property name="SelectionRepresentation" id="5162.SelectionRepresentation" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="enum" id="5162.SelectionRepresentation.enum">
          <Entry value="0" text="Points"/>
          <Entry value="1" text="Wireframe"/>
          <Entry value="2" text="Surface"/>
        </Domain>
      </Property>
      <Property name="SelectionUseOutline" id="5162.SelectionUseOutline" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5162.SelectionUseOutline.bool"/>
      </Property>
      <Property name="SetScaleArray" id="5162.SetScaleArray" number_of_elements="5">
        <Element index="0" value=""/>
        <Element index="1" value=""/>
        <Element index="2" value=""/>
        <Element index="3" value=""/>
        <Element index="4" value=""/>
        <Domain name="array_list" id="5162.SetScaleArray.array_list"/>
      </Property>
      <Property name="ShaderPreset" id="5162.ShaderPreset" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="enum" id="5162.ShaderPreset.enum">
          <Entry value="0" text="Gaussian Blur (Default)"/>
          <Entry value="1" text="Sphere"/>
          <Entry value="2" text="Black-edged circle"/>
          <Entry value="3" text="Plain circle"/>
          <Entry value="4" text="Triangle"/>
          <Entry value="5" text="Square Outline"/>
        </Domain>
      </Property>
      <Property name="Specular" id="5162.Specular" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="range" id="5162.Specular.range"/>
      </Property>
      <Property name="SpecularColor" id="5162.SpecularColor" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="1"/>
        <Element index="2" value="1"/>
        <Domain name="range" id="5162.SpecularColor.range"/>
      </Property>
      <Property name="SpecularPower" id="5162.SpecularPower" number_of_elements="1">
        <Element index="0" value="100"/>
        <Domain name="range" id="5162.SpecularPower.range"/>
      </Property>
      <Property name="StaticMode" id="5162.StaticMode" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5162.StaticMode.bool"/>
      </Property>
      <Property name="StickyAxes" id="5162.StickyAxes" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5162.StickyAxes.bool"/>
      </Property>
      <Property name="SuppressLOD" id="5162.SuppressLOD" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5162.SuppressLOD.bool"/>
      </Property>
      <Property name="Texture" id="5162.Texture">
        <Domain name="groups" id="5162.Texture.groups"/>
      </Property>
      <Property name="Triangulate" id="5162.Triangulate" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5162.Triangulate.bool"/>
      </Property>
      <Property name="UseAxesOrigin" id="5162.UseAxesOrigin" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5162.UseAxesOrigin.bool"/>
      </Property>
      <Property name="UserTransform" id="5162.UserTransform" number_of_elements="16">
        <Element index="0" value="1"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Element index="3" value="0"/>
        <Element index="4" value="0"/>
        <Element index="5" value="1"/>
        <Element index="6" value="0"/>
        <Element index="7" value="0"/>
        <Element index="8" value="0"/>
        <Element index="9" value="0"/>
        <Element index="10" value="1"/>
        <Element index="11" value="0"/>
        <Element index="12" value="0"/>
        <Element index="13" value="0"/>
        <Element index="14" value="0"/>
        <Element index="15" value="1"/>
      </Property>
    </Proxy>
    <Proxy group="representations" type="GeometryRepresentation" id="5349" servers="21">
      <Property name="CubeAxesVisibility" id="5349.CubeAxesVisibility" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5349.CubeAxesVisibility.bool"/>
      </Property>
      <Property name="Input" id="5349.Input" number_of_elements="1">
        <Proxy value="5181" output_port="0"/>
        <Domain name="input_array_cell" id="5349.Input.input_array_cell"/>
        <Domain name="input_array_point" id="5349.Input.input_array_point"/>
        <Domain name="input_type" id="5349.Input.input_type"/>
      </Property>
      <Property name="Representation" id="5349.Representation" number_of_elements="1">
        <Element index="0" value="Surface"/>
        <Domain name="list" id="5349.Representation.list">
          <String text="3D Glyphs"/>
          <String text="Outline"/>
          <String text="Point Gaussian"/>
          <String text="Points"/>
          <String text="Surface"/>
          <String text="Surface With Edges"/>
          <String text="Wireframe"/>
        </Domain>
      </Property>
      <Property name="RepresentationTypesInfo" id="5349.RepresentationTypesInfo" number_of_elements="7">
        <Element index="0" value="3D Glyphs"/>
        <Element index="1" value="Outline"/>
        <Element index="2" value="Point Gaussian"/>
        <Element index="3" value="Points"/>
        <Element index="4" value="Surface"/>
        <Element index="5" value="Surface With Edges"/>
        <Element index="6" value="Wireframe"/>
      </Property>
      <Property name="SelectionCellFieldDataArrayName" id="5349.SelectionCellFieldDataArrayName" number_of_elements="1">
        <Element index="0" value="vtkOriginalCellIds"/>
        <Domain name="array_list" id="5349.SelectionCellFieldDataArrayName.array_list"/>
      </Property>
      <Property name="SelectionPointFieldDataArrayName" id="5349.SelectionPointFieldDataArrayName" number_of_elements="1">
        <Element index="0" value="Normals"/>
        <Domain name="array_list" id="5349.SelectionPointFieldDataArrayName.array_list">
          <String text="Normals"/>
          <String text="TextureCoordinates"/>
          <String text="V"/>
        </Domain>
      </Property>
      <Property name="SelectionVisibility" id="5349.SelectionVisibility" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="5349.SelectionVisibility.bool"/>
      </Property>
      <Property name="Visibility" id="5349.Visibility" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="5349.Visibility.bool"/>
      </Property>
      <Property name="Ambient" id="5349.Ambient" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="range" id="5349.Ambient.range"/>
      </Property>
      <Property name="AmbientColor" id="5349.AmbientColor" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="1"/>
        <Element index="2" value="1"/>
        <Domain name="range" id="5349.AmbientColor.range"/>
      </Property>
      <Property name="AxesOrigin" id="5349.AxesOrigin" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="5349.AxesOrigin.range"/>
      </Property>
      <Property name="BackfaceAmbientColor" id="5349.BackfaceAmbientColor" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="1"/>
        <Element index="2" value="1"/>
        <Domain name="range" id="5349.BackfaceAmbientColor.range"/>
      </Property>
      <Property name="BackfaceDiffuseColor" id="5349.BackfaceDiffuseColor" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="1"/>
        <Element index="2" value="1"/>
        <Domain name="range" id="5349.BackfaceDiffuseColor.range"/>
      </Property>
      <Property name="BackfaceOpacity" id="5349.BackfaceOpacity" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="5349.BackfaceOpacity.range"/>
      </Property>
      <Property name="BackfaceRepresentation" id="5349.BackfaceRepresentation" number_of_elements="1">
        <Element index="0" value="400"/>
        <Domain name="enum" id="5349.BackfaceRepresentation.enum">
          <Entry value="400" text="Follow Frontface"/>
          <Entry value="401" text="Cull Backface"/>
          <Entry value="402" text="Cull Frontface"/>
          <Entry value="0" text="Points"/>
          <Entry value="1" text="Wireframe"/>
          <Entry value="2" text="Surface"/>
          <Entry value="3" text="Surface With Edges"/>
        </Domain>
      </Property>
      <Property name="BlockColor" id="5349.BlockColor"/>
      <Property name="BlockColorsDistinctValues" id="5349.BlockColorsDistinctValues" number_of_elements="1">
        <Element index="0" value="12"/>
        <Domain name="range" id="5349.BlockColorsDistinctValues.range"/>
      </Property>
      <Property name="BlockOpacity" id="5349.BlockOpacity"/>
      <Property name="BlockVisibility" id="5349.BlockVisibility"/>
      <Property name="CenterStickyAxes" id="5349.CenterStickyAxes" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5349.CenterStickyAxes.bool"/>
      </Property>
      <Property name="Color" id="5349.Color" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="1"/>
        <Element index="2" value="1"/>
        <Domain name="range" id="5349.Color.range"/>
      </Property>
      <Property name="ColorArrayName" id="5349.ColorArrayName" number_of_elements="5">
        <Element index="0" value=""/>
        <Element index="1" value=""/>
        <Element index="2" value=""/>
        <Element index="3" value="0"/>
        <Element index="4" value="V"/>
        <Domain name="array_list" id="5349.ColorArrayName.array_list">
          <String text="Normals"/>
          <String text="TextureCoordinates"/>
          <String text="V"/>
          <String text="vtkCompositeIndex"/>
        </Domain>
        <Domain name="field_list" id="5349.ColorArrayName.field_list">
          <Entry value="0" text="Point Data"/>
          <Entry value="1" text="Cell Data"/>
          <Entry value="2" text="Field Data"/>
          <Entry value="4" text="Vertex Data"/>
          <Entry value="5" text="Edge Data"/>
          <Entry value="6" text="Row Data"/>
        </Domain>
      </Property>
      <Property name="CubeAxesColor" id="5349.CubeAxesColor" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="1"/>
        <Element index="2" value="1"/>
        <Domain name="range" id="5349.CubeAxesColor.range"/>
      </Property>
      <Property name="CubeAxesCornerOffset" id="5349.CubeAxesCornerOffset" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="range" id="5349.CubeAxesCornerOffset.range"/>
      </Property>
      <Property name="CubeAxesFlyMode" id="5349.CubeAxesFlyMode" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="enum" id="5349.CubeAxesFlyMode.enum">
          <Entry value="0" text="Outer Edges"/>
          <Entry value="1" text="Closest Triad"/>
          <Entry value="2" text="Furthest Triad"/>
          <Entry value="3" text="Static Triad"/>
          <Entry value="4" text="Static Edges"/>
        </Domain>
      </Property>
      <Property name="CubeAxesGridLineLocation" id="5349.CubeAxesGridLineLocation" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="enum" id="5349.CubeAxesGridLineLocation.enum">
          <Entry value="0" text="All Faces"/>
          <Entry value="1" text="Closest Faces"/>
          <Entry value="2" text="Furthest Faces"/>
        </Domain>
      </Property>
      <Property name="CubeAxesInertia" id="5349.CubeAxesInertia" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="5349.CubeAxesInertia.range"/>
      </Property>
      <Property name="CubeAxesTickLocation" id="5349.CubeAxesTickLocation" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="enum" id="5349.CubeAxesTickLocation.enum">
          <Entry value="0" text="Inside"/>
          <Entry value="1" text="Outside"/>
          <Entry value="2" text="Both"/>
        </Domain>
      </Property>
      <Property name="CubeAxesUseDefaultXTitle" id="5349.CubeAxesUseDefaultXTitle" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="5349.CubeAxesUseDefaultXTitle.bool"/>
      </Property>
      <Property name="CubeAxesUseDefaultYTitle" id="5349.CubeAxesUseDefaultYTitle" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="5349.CubeAxesUseDefaultYTitle.bool"/>
      </Property>
      <Property name="CubeAxesUseDefaultZTitle" id="5349.CubeAxesUseDefaultZTitle" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="5349.CubeAxesUseDefaultZTitle.bool"/>
      </Property>
      <Property name="CubeAxesXAxisMinorTickVisibility" id="5349.CubeAxesXAxisMinorTickVisibility" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="5349.CubeAxesXAxisMinorTickVisibility.bool"/>
      </Property>
      <Property name="CubeAxesXAxisTickVisibility" id="5349.CubeAxesXAxisTickVisibility" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="5349.CubeAxesXAxisTickVisibility.bool"/>
      </Property>
      <Property name="CubeAxesXAxisVisibility" id="5349.CubeAxesXAxisVisibility" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="5349.CubeAxesXAxisVisibility.bool"/>
      </Property>
      <Property name="CubeAxesXGridLines" id="5349.CubeAxesXGridLines" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5349.CubeAxesXGridLines.bool"/>
      </Property>
      <Property name="CubeAxesXLabelFormat" id="5349.CubeAxesXLabelFormat" number_of_elements="1">
        <Element index="0" value="%-#6.3g"/>
      </Property>
      <Property name="CubeAxesXTitle" id="5349.CubeAxesXTitle" number_of_elements="1">
        <Element index="0" value="X-Axis"/>
      </Property>
      <Property name="CubeAxesYAxisMinorTickVisibility" id="5349.CubeAxesYAxisMinorTickVisibility" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="5349.CubeAxesYAxisMinorTickVisibility.bool"/>
      </Property>
      <Property name="CubeAxesYAxisTickVisibility" id="5349.CubeAxesYAxisTickVisibility" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="5349.CubeAxesYAxisTickVisibility.bool"/>
      </Property>
      <Property name="CubeAxesYAxisVisibility" id="5349.CubeAxesYAxisVisibility" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="5349.CubeAxesYAxisVisibility.bool"/>
      </Property>
      <Property name="CubeAxesYGridLines" id="5349.CubeAxesYGridLines" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5349.CubeAxesYGridLines.bool"/>
      </Property>
      <Property name="CubeAxesYLabelFormat" id="5349.CubeAxesYLabelFormat" number_of_elements="1">
        <Element index="0" value="%-#6.3g"/>
      </Property>
      <Property name="CubeAxesYTitle" id="5349.CubeAxesYTitle" number_of_elements="1">
        <Element index="0" value="Y-Axis"/>
      </Property>
      <Property name="CubeAxesZAxisMinorTickVisibility" id="5349.CubeAxesZAxisMinorTickVisibility" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="5349.CubeAxesZAxisMinorTickVisibility.bool"/>
      </Property>
      <Property name="CubeAxesZAxisTickVisibility" id="5349.CubeAxesZAxisTickVisibility" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="5349.CubeAxesZAxisTickVisibility.bool"/>
      </Property>
      <Property name="CubeAxesZAxisVisibility" id="5349.CubeAxesZAxisVisibility" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="5349.CubeAxesZAxisVisibility.bool"/>
      </Property>
      <Property name="CubeAxesZGridLines" id="5349.CubeAxesZGridLines" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5349.CubeAxesZGridLines.bool"/>
      </Property>
      <Property name="CubeAxesZLabelFormat" id="5349.CubeAxesZLabelFormat" number_of_elements="1">
        <Element index="0" value="%-#6.3g"/>
      </Property>
      <Property name="CubeAxesZTitle" id="5349.CubeAxesZTitle" number_of_elements="1">
        <Element index="0" value="Z-Axis"/>
      </Property>
      <Property name="CustomBounds" id="5349.CustomBounds" number_of_elements="6">
        <Element index="0" value="0"/>
        <Element index="1" value="1"/>
        <Element index="2" value="0"/>
        <Element index="3" value="1"/>
        <Element index="4" value="0"/>
        <Element index="5" value="1"/>
      </Property>
      <Property name="CustomBoundsActive" id="5349.CustomBoundsActive" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
      </Property>
      <Property name="CustomRange" id="5349.CustomRange" number_of_elements="6">
        <Element index="0" value="0"/>
        <Element index="1" value="1"/>
        <Element index="2" value="0"/>
        <Element index="3" value="1"/>
        <Element index="4" value="0"/>
        <Element index="5" value="1"/>
      </Property>
      <Property name="CustomRangeActive" id="5349.CustomRangeActive" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
      </Property>
      <Property name="CustomShader" id="5349.CustomShader" number_of_elements="1">
        <Element index="0" value=""/>
      </Property>
      <Property name="DataBounds" id="5349.DataBounds" number_of_elements="6">
        <Element index="0" value="1.86920871515295e-306"/>
        <Element index="1" value="4.45061456288812e-308"/>
        <Element index="2" value="9.34605036791278e-307"/>
        <Element index="3" value="2.2251859007657e-307"/>
        <Element index="4" value="9.34587381651593e-307"/>
        <Element index="5" value="1.69119330044931e-306"/>
      </Property>
      <Property name="Diffuse" id="5349.Diffuse" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="5349.Diffuse.range"/>
      </Property>
      <Property name="DiffuseColor" id="5349.DiffuseColor" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="1"/>
        <Element index="2" value="1"/>
        <Domain name="range" id="5349.DiffuseColor.range"/>
      </Property>
      <Property name="EdgeColor" id="5349.EdgeColor" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0.5"/>
        <Domain name="range" id="5349.EdgeColor.range"/>
      </Property>
      <Property name="Emissive" id="5349.Emissive" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5349.Emissive.bool"/>
      </Property>
      <Property name="GaussianRadius" id="5349.GaussianRadius" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="range" id="5349.GaussianRadius.range"/>
      </Property>
      <Property name="GlyphType" id="5349.GlyphType" number_of_elements="1">
        <Proxy value="5204" output_port="0"/>
        <Domain name="input_type" id="5349.GlyphType.input_type"/>
        <Domain name="proxy_list" id="5349.GlyphType.proxy_list">
          <Proxy value="5204"/>
          <Proxy value="5215"/>
          <Proxy value="5226"/>
          <Proxy value="5237"/>
          <Proxy value="5248"/>
          <Proxy value="5259"/>
          <Proxy value="5270"/>
        </Domain>
      </Property>
      <Property name="InterpolateScalarsBeforeMapping" id="5349.InterpolateScalarsBeforeMapping" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="5349.InterpolateScalarsBeforeMapping.bool"/>
      </Property>
      <Property name="Interpolation" id="5349.Interpolation" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="enum" id="5349.Interpolation.enum">
          <Entry value="0" text="Flat"/>
          <Entry value="1" text="Gouraud"/>
        </Domain>
      </Property>
      <Property name="LineWidth" id="5349.LineWidth" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="5349.LineWidth.range"/>
      </Property>
      <Property name="LookupTable" id="5349.LookupTable" number_of_elements="1">
        <Proxy value="5174"/>
        <Domain name="groups" id="5349.LookupTable.groups"/>
      </Property>
      <Property name="MapScalars" id="5349.MapScalars" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="5349.MapScalars.bool"/>
      </Property>
      <Property name="Masking" id="5349.Masking" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5349.Masking.bool"/>
      </Property>
      <Property name="MeshVisibility" id="5349.MeshVisibility" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5349.MeshVisibility.bool"/>
      </Property>
      <Property name="NonlinearSubdivisionLevel" id="5349.NonlinearSubdivisionLevel" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="5349.NonlinearSubdivisionLevel.range"/>
      </Property>
      <Property name="Opacity" id="5349.Opacity" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="5349.Opacity.range"/>
      </Property>
      <Property name="OpacityArray" id="5349.OpacityArray" number_of_elements="5">
        <Element index="0" value=""/>
        <Element index="1" value=""/>
        <Element index="2" value=""/>
        <Element index="3" value=""/>
        <Element index="4" value=""/>
        <Domain name="array_list" id="5349.OpacityArray.array_list"/>
      </Property>
      <Property name="OpacityByArray" id="5349.OpacityByArray" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5349.OpacityByArray.bool"/>
      </Property>
      <Property name="OpacityTransferFunction" id="5349.OpacityTransferFunction" number_of_elements="1">
        <Proxy value="5303"/>
        <Domain name="groups" id="5349.OpacityTransferFunction.groups"/>
        <Domain name="proxy_list" id="5349.OpacityTransferFunction.proxy_list">
          <Proxy value="5303"/>
        </Domain>
      </Property>
      <Property name="Orient" id="5349.Orient" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5349.Orient.bool"/>
      </Property>
      <Property name="Orientation" id="5349.Orientation" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="5349.Orientation.range"/>
      </Property>
      <Property name="OrientationMode" id="5349.OrientationMode" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="enum" id="5349.OrientationMode.enum">
          <Entry value="0" text="Direction"/>
          <Entry value="1" text="Rotation"/>
        </Domain>
      </Property>
      <Property name="Origin" id="5349.Origin" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="5349.Origin.range"/>
      </Property>
      <Property name="OriginalBoundsRangeActive" id="5349.OriginalBoundsRangeActive" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
      </Property>
      <Property name="Pickable" id="5349.Pickable" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="5349.Pickable.bool"/>
      </Property>
      <Property name="PointSize" id="5349.PointSize" number_of_elements="1">
        <Element index="0" value="2"/>
        <Domain name="range" id="5349.PointSize.range"/>
      </Property>
      <Property name="Position" id="5349.Position" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="5349.Position.range"/>
      </Property>
      <Property name="Scale" id="5349.Scale" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="1"/>
        <Element index="2" value="1"/>
        <Domain name="range" id="5349.Scale.range"/>
      </Property>
      <Property name="ScaleByArray" id="5349.ScaleByArray" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5349.ScaleByArray.bool"/>
      </Property>
      <Property name="ScaleFactor" id="5349.ScaleFactor" number_of_elements="1">
        <Element index="0" value="0.2"/>
        <Domain name="bounds" id="5349.ScaleFactor.bounds"/>
        <Domain name="scalar_range" id="5349.ScaleFactor.scalar_range"/>
        <Domain name="vector_range" id="5349.ScaleFactor.vector_range"/>
      </Property>
      <Property name="ScaleMode" id="5349.ScaleMode" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="enum" id="5349.ScaleMode.enum">
          <Entry value="0" text="No Data Scaling Off"/>
          <Entry value="1" text="Magnitude"/>
          <Entry value="2" text="Vector Components"/>
        </Domain>
      </Property>
      <Property name="ScaleTransferFunction" id="5349.ScaleTransferFunction" number_of_elements="1">
        <Proxy value="5304"/>
        <Domain name="groups" id="5349.ScaleTransferFunction.groups"/>
        <Domain name="proxy_list" id="5349.ScaleTransferFunction.proxy_list">
          <Proxy value="5304"/>
        </Domain>
      </Property>
      <Property name="Scaling" id="5349.Scaling" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5349.Scaling.bool"/>
      </Property>
      <Property name="SelectMaskArray" id="5349.SelectMaskArray" number_of_elements="1">
        <Element index="0" value=""/>
      </Property>
      <Property name="SelectOrientationVectors" id="5349.SelectOrientationVectors" number_of_elements="1">
        <Element index="0" value=""/>
      </Property>
      <Property name="SelectScaleArray" id="5349.SelectScaleArray" number_of_elements="1">
        <Element index="0" value=""/>
      </Property>
      <Property name="SelectionCellLabelBold" id="5349.SelectionCellLabelBold" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5349.SelectionCellLabelBold.bool"/>
      </Property>
      <Property name="SelectionCellLabelColor" id="5349.SelectionCellLabelColor" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="1"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="5349.SelectionCellLabelColor.range"/>
      </Property>
      <Property name="SelectionCellLabelFontFamily" id="5349.SelectionCellLabelFontFamily" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="enum" id="5349.SelectionCellLabelFontFamily.enum">
          <Entry value="0" text="Arial"/>
          <Entry value="1" text="Courier"/>
          <Entry value="2" text="Times"/>
        </Domain>
      </Property>
      <Property name="SelectionCellLabelFontSize" id="5349.SelectionCellLabelFontSize" number_of_elements="1">
        <Element index="0" value="18"/>
        <Domain name="range" id="5349.SelectionCellLabelFontSize.range"/>
      </Property>
      <Property name="SelectionCellLabelFormat" id="5349.SelectionCellLabelFormat" number_of_elements="1">
        <Element index="0" value=""/>
      </Property>
      <Property name="SelectionCellLabelItalic" id="5349.SelectionCellLabelItalic" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5349.SelectionCellLabelItalic.bool"/>
      </Property>
      <Property name="SelectionCellLabelJustification" id="5349.SelectionCellLabelJustification" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="enum" id="5349.SelectionCellLabelJustification.enum">
          <Entry value="0" text="Left"/>
          <Entry value="1" text="Center"/>
          <Entry value="2" text="Right"/>
        </Domain>
      </Property>
      <Property name="SelectionCellLabelOpacity" id="5349.SelectionCellLabelOpacity" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="5349.SelectionCellLabelOpacity.range"/>
      </Property>
      <Property name="SelectionCellLabelShadow" id="5349.SelectionCellLabelShadow" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5349.SelectionCellLabelShadow.bool"/>
      </Property>
      <Property name="SelectionCellLabelVisibility" id="5349.SelectionCellLabelVisibility" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5349.SelectionCellLabelVisibility.bool"/>
      </Property>
      <Property name="SelectionColor" id="5349.SelectionColor" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="0"/>
        <Element index="2" value="1"/>
        <Domain name="range" id="5349.SelectionColor.range"/>
      </Property>
      <Property name="SelectionLineWidth" id="5349.SelectionLineWidth" number_of_elements="1">
        <Element index="0" value="2"/>
        <Domain name="range" id="5349.SelectionLineWidth.range"/>
      </Property>
      <Property name="SelectionOpacity" id="5349.SelectionOpacity" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="5349.SelectionOpacity.range"/>
      </Property>
      <Property name="SelectionPointLabelBold" id="5349.SelectionPointLabelBold" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5349.SelectionPointLabelBold.bool"/>
      </Property>
      <Property name="SelectionPointLabelColor" id="5349.SelectionPointLabelColor" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="1"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="5349.SelectionPointLabelColor.range"/>
      </Property>
      <Property name="SelectionPointLabelFontFamily" id="5349.SelectionPointLabelFontFamily" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="enum" id="5349.SelectionPointLabelFontFamily.enum">
          <Entry value="0" text="Arial"/>
          <Entry value="1" text="Courier"/>
          <Entry value="2" text="Times"/>
        </Domain>
      </Property>
      <Property name="SelectionPointLabelFontSize" id="5349.SelectionPointLabelFontSize" number_of_elements="1">
        <Element index="0" value="18"/>
        <Domain name="range" id="5349.SelectionPointLabelFontSize.range"/>
      </Property>
      <Property name="SelectionPointLabelFormat" id="5349.SelectionPointLabelFormat" number_of_elements="1">
        <Element index="0" value=""/>
      </Property>
      <Property name="SelectionPointLabelItalic" id="5349.SelectionPointLabelItalic" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5349.SelectionPointLabelItalic.bool"/>
      </Property>
      <Property name="SelectionPointLabelJustification" id="5349.SelectionPointLabelJustification" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="enum" id="5349.SelectionPointLabelJustification.enum">
          <Entry value="0" text="Left"/>
          <Entry value="1" text="Center"/>
          <Entry value="2" text="Right"/>
        </Domain>
      </Property>
      <Property name="SelectionPointLabelOpacity" id="5349.SelectionPointLabelOpacity" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="5349.SelectionPointLabelOpacity.range"/>
      </Property>
      <Property name="SelectionPointLabelShadow" id="5349.SelectionPointLabelShadow" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5349.SelectionPointLabelShadow.bool"/>
      </Property>
      <Property name="SelectionPointLabelVisibility" id="5349.SelectionPointLabelVisibility" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5349.SelectionPointLabelVisibility.bool"/>
      </Property>
      <Property name="SelectionPointSize" id="5349.SelectionPointSize" number_of_elements="1">
        <Element index="0" value="5"/>
        <Domain name="range" id="5349.SelectionPointSize.range"/>
      </Property>
      <Property name="SelectionRepresentation" id="5349.SelectionRepresentation" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="enum" id="5349.SelectionRepresentation.enum">
          <Entry value="0" text="Points"/>
          <Entry value="1" text="Wireframe"/>
          <Entry value="2" text="Surface"/>
        </Domain>
      </Property>
      <Property name="SelectionUseOutline" id="5349.SelectionUseOutline" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5349.SelectionUseOutline.bool"/>
      </Property>
      <Property name="SetScaleArray" id="5349.SetScaleArray" number_of_elements="5">
        <Element index="0" value=""/>
        <Element index="1" value=""/>
        <Element index="2" value=""/>
        <Element index="3" value=""/>
        <Element index="4" value=""/>
        <Domain name="array_list" id="5349.SetScaleArray.array_list"/>
      </Property>
      <Property name="ShaderPreset" id="5349.ShaderPreset" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="enum" id="5349.ShaderPreset.enum">
          <Entry value="0" text="Gaussian Blur (Default)"/>
          <Entry value="1" text="Sphere"/>
          <Entry value="2" text="Black-edged circle"/>
          <Entry value="3" text="Plain circle"/>
          <Entry value="4" text="Triangle"/>
          <Entry value="5" text="Square Outline"/>
        </Domain>
      </Property>
      <Property name="Specular" id="5349.Specular" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="range" id="5349.Specular.range"/>
      </Property>
      <Property name="SpecularColor" id="5349.SpecularColor" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="1"/>
        <Element index="2" value="1"/>
        <Domain name="range" id="5349.SpecularColor.range"/>
      </Property>
      <Property name="SpecularPower" id="5349.SpecularPower" number_of_elements="1">
        <Element index="0" value="100"/>
        <Domain name="range" id="5349.SpecularPower.range"/>
      </Property>
      <Property name="StaticMode" id="5349.StaticMode" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5349.StaticMode.bool"/>
      </Property>
      <Property name="StickyAxes" id="5349.StickyAxes" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5349.StickyAxes.bool"/>
      </Property>
      <Property name="SuppressLOD" id="5349.SuppressLOD" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5349.SuppressLOD.bool"/>
      </Property>
      <Property name="Texture" id="5349.Texture">
        <Domain name="groups" id="5349.Texture.groups"/>
      </Property>
      <Property name="Triangulate" id="5349.Triangulate" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5349.Triangulate.bool"/>
      </Property>
      <Property name="UseAxesOrigin" id="5349.UseAxesOrigin" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5349.UseAxesOrigin.bool"/>
      </Property>
      <Property name="UserTransform" id="5349.UserTransform" number_of_elements="16">
        <Element index="0" value="1"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Element index="3" value="0"/>
        <Element index="4" value="0"/>
        <Element index="5" value="1"/>
        <Element index="6" value="0"/>
        <Element index="7" value="0"/>
        <Element index="8" value="0"/>
        <Element index="9" value="0"/>
        <Element index="10" value="1"/>
        <Element index="11" value="0"/>
        <Element index="12" value="0"/>
        <Element index="13" value="0"/>
        <Element index="14" value="0"/>
        <Element index="15" value="1"/>
      </Property>
    </Proxy>
    <Proxy group="representations" type="ScalarBarWidgetRepresentation" id="5180" servers="21">
      <Property name="Enabled" id="5180.Enabled" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="5180.Enabled.bool"/>
      </Property>
      <Property name="LockPosition" id="5180.LockPosition" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5180.LockPosition.bool"/>
      </Property>
      <Property name="UseNonCompositedRenderer" id="5180.UseNonCompositedRenderer" number_of_elements="1">
        <Element index="0" value="1"/>
      </Property>
      <Property name="AddRangeAnnotations" id="5180.AddRangeAnnotations" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5180.AddRangeAnnotations.bool"/>
      </Property>
      <Property name="AddRangeLabels" id="5180.AddRangeLabels" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="5180.AddRangeLabels.bool"/>
      </Property>
      <Property name="AspectRatio" id="5180.AspectRatio" number_of_elements="1">
        <Element index="0" value="20"/>
        <Domain name="range" id="5180.AspectRatio.range"/>
      </Property>
      <Property name="AutoOrient" id="5180.AutoOrient" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="5180.AutoOrient.bool"/>
      </Property>
      <Property name="AutoOrientInfo" id="5180.AutoOrientInfo" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="5180.AutoOrientInfo.bool"/>
      </Property>
      <Property name="AutomaticAnnotations" id="5180.AutomaticAnnotations" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5180.AutomaticAnnotations.bool"/>
      </Property>
      <Property name="AutomaticLabelFormat" id="5180.AutomaticLabelFormat" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="5180.AutomaticLabelFormat.bool"/>
      </Property>
      <Property name="ComponentTitle" id="5180.ComponentTitle" number_of_elements="1">
        <Element index="0" value="Magnitude"/>
      </Property>
      <Property name="DrawAnnotations" id="5180.DrawAnnotations" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="5180.DrawAnnotations.bool"/>
      </Property>
      <Property name="DrawNanAnnotation" id="5180.DrawNanAnnotation" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5180.DrawNanAnnotation.bool"/>
      </Property>
      <Property name="DrawSubTickMarks" id="5180.DrawSubTickMarks" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="5180.DrawSubTickMarks.bool"/>
      </Property>
      <Property name="DrawTickLabels" id="5180.DrawTickLabels" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="5180.DrawTickLabels.bool"/>
      </Property>
      <Property name="DrawTickMarks" id="5180.DrawTickMarks" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="5180.DrawTickMarks.bool"/>
      </Property>
      <Property name="LabelBold" id="5180.LabelBold" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5180.LabelBold.bool"/>
      </Property>
      <Property name="LabelColor" id="5180.LabelColor" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="1"/>
        <Element index="2" value="1"/>
        <Domain name="range" id="5180.LabelColor.range"/>
      </Property>
      <Property name="LabelFontFamily" id="5180.LabelFontFamily" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="enum" id="5180.LabelFontFamily.enum">
          <Entry value="0" text="Arial"/>
          <Entry value="1" text="Courier"/>
          <Entry value="2" text="Times"/>
        </Domain>
      </Property>
      <Property name="LabelFontSize" id="5180.LabelFontSize" number_of_elements="1">
        <Element index="0" value="7"/>
        <Domain name="range" id="5180.LabelFontSize.range"/>
      </Property>
      <Property name="LabelFormat" id="5180.LabelFormat" number_of_elements="1">
        <Element index="0" value="%-#6.3g"/>
      </Property>
      <Property name="LabelItalic" id="5180.LabelItalic" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5180.LabelItalic.bool"/>
      </Property>
      <Property name="LabelOpacity" id="5180.LabelOpacity" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="5180.LabelOpacity.range"/>
      </Property>
      <Property name="LabelShadow" id="5180.LabelShadow" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5180.LabelShadow.bool"/>
      </Property>
      <Property name="LookupTable" id="5180.LookupTable" number_of_elements="1">
        <Proxy value="5174"/>
        <Domain name="groups" id="5180.LookupTable.groups"/>
      </Property>
      <Property name="NanAnnotation" id="5180.NanAnnotation" number_of_elements="1">
        <Element index="0" value="NaN"/>
      </Property>
      <Property name="NumberOfLabels" id="5180.NumberOfLabels" number_of_elements="1">
        <Element index="0" value="5"/>
        <Domain name="range" id="5180.NumberOfLabels.range"/>
      </Property>
      <Property name="Orientation" id="5180.Orientation" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="enum" id="5180.Orientation.enum">
          <Entry value="0" text="Horizontal"/>
          <Entry value="1" text="Vertical"/>
        </Domain>
      </Property>
      <Property name="OrientationInfo" id="5180.OrientationInfo" number_of_elements="1">
        <Element index="0" value="1"/>
      </Property>
      <Property name="Position" id="5180.Position" number_of_elements="2">
        <Element index="0" value="0.85"/>
        <Element index="1" value="0.05"/>
        <Domain name="range" id="5180.Position.range"/>
      </Property>
      <Property name="Position2" id="5180.Position2" number_of_elements="2">
        <Element index="0" value="0.12"/>
        <Element index="1" value="0.43"/>
        <Domain name="range" id="5180.Position2.range"/>
      </Property>
      <Property name="Position2Info" id="5180.Position2Info" number_of_elements="2">
        <Element index="0" value="0.12"/>
        <Element index="1" value="0.43"/>
      </Property>
      <Property name="PositionInfo" id="5180.PositionInfo" number_of_elements="2">
        <Element index="0" value="0.85"/>
        <Element index="1" value="0.05"/>
      </Property>
      <Property name="RangeLabelFormat" id="5180.RangeLabelFormat" number_of_elements="1">
        <Element index="0" value="%4.3e"/>
      </Property>
      <Property name="Repositionable" id="5180.Repositionable" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="5180.Repositionable.bool"/>
      </Property>
      <Property name="Resizable" id="5180.Resizable" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="5180.Resizable.bool"/>
      </Property>
      <Property name="Selectable" id="5180.Selectable" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5180.Selectable.bool"/>
      </Property>
      <Property name="TextPosition" id="5180.TextPosition" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="enum" id="5180.TextPosition.enum">
          <Entry value="1" text="Ticks right/top, annotations left/bottom"/>
          <Entry value="0" text="Ticks left/bottom, annotations right/top"/>
        </Domain>
      </Property>
      <Property name="Title" id="5180.Title" number_of_elements="1">
        <Element index="0" value="V"/>
      </Property>
      <Property name="TitleBold" id="5180.TitleBold" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5180.TitleBold.bool"/>
      </Property>
      <Property name="TitleColor" id="5180.TitleColor" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="1"/>
        <Element index="2" value="1"/>
        <Domain name="range" id="5180.TitleColor.range"/>
      </Property>
      <Property name="TitleFontFamily" id="5180.TitleFontFamily" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="enum" id="5180.TitleFontFamily.enum">
          <Entry value="0" text="Arial"/>
          <Entry value="1" text="Courier"/>
          <Entry value="2" text="Times"/>
        </Domain>
      </Property>
      <Property name="TitleFontSize" id="5180.TitleFontSize" number_of_elements="1">
        <Element index="0" value="7"/>
        <Domain name="range" id="5180.TitleFontSize.range"/>
      </Property>
      <Property name="TitleItalic" id="5180.TitleItalic" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5180.TitleItalic.bool"/>
      </Property>
      <Property name="TitleJustification" id="5180.TitleJustification" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="enum" id="5180.TitleJustification.enum">
          <Entry value="0" text="Left"/>
          <Entry value="1" text="Centered"/>
          <Entry value="2" text="Right"/>
        </Domain>
      </Property>
      <Property name="TitleOpacity" id="5180.TitleOpacity" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="5180.TitleOpacity.range"/>
      </Property>
      <Property name="TitleShadow" id="5180.TitleShadow" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5180.TitleShadow.bool"/>
      </Property>
      <Property name="Visibility" id="5180.Visibility" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="5180.Visibility.bool"/>
      </Property>
    </Proxy>
    <Proxy group="filters" type="AngularPeriodicFilter" id="5181" servers="1">
      <Property name="Axis" id="5181.Axis" number_of_elements="1">
        <Element index="0" value="2"/>
        <Domain name="enum" id="5181.Axis.enum">
          <Entry value="0" text="Axis X"/>
          <Entry value="1" text="Axis Y"/>
          <Entry value="2" text="Axis Z"/>
        </Domain>
      </Property>
      <Property name="BlockIndices" id="5181.BlockIndices">
        <Domain name="tree" id="5181.BlockIndices.tree"/>
      </Property>
      <Property name="Center" id="5181.Center" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="5181.Center.range"/>
      </Property>
      <Property name="Input" id="5181.Input" number_of_elements="1">
        <Proxy value="4994" output_port="0"/>
        <Domain name="groups" id="5181.Input.groups"/>
        <Domain name="input_type" id="5181.Input.input_type"/>
      </Property>
      <Property name="IterationMode" id="5181.IterationMode" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="enum" id="5181.IterationMode.enum">
          <Entry value="0" text="Manual"/>
          <Entry value="1" text="Maximum"/>
        </Domain>
      </Property>
      <Property name="NumberOfPeriods" id="5181.NumberOfPeriods" number_of_elements="1">
        <Element index="0" value="3"/>
      </Property>
      <Property name="RotationAngle" id="5181.RotationAngle" number_of_elements="1">
        <Element index="0" value="90"/>
      </Property>
      <Property name="RotationArrayName" id="5181.RotationArrayName" number_of_elements="1">
        <Element index="0" value="periodic angle"/>
      </Property>
      <Property name="RotationMode" id="5181.RotationMode" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="enum" id="5181.RotationMode.enum">
          <Entry value="0" text="Direct Angle"/>
          <Entry value="1" text="Array Value"/>
        </Domain>
      </Property>
    </Proxy>
    <Proxy group="filters" type="Calculator" id="4994" servers="1">
      <Property name="AttributeMode" id="4994.AttributeMode" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="enum" id="4994.AttributeMode.enum">
          <Entry value="1" text="Point Data"/>
          <Entry value="2" text="Cell Data"/>
        </Domain>
      </Property>
      <Property name="CoordinateResults" id="4994.CoordinateResults" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4994.CoordinateResults.bool"/>
      </Property>
      <Property name="Function" id="4994.Function" number_of_elements="1">
        <Element index="0" value="coordsX*iHat + coordsY*jHat"/>
      </Property>
      <Property name="Input" id="4994.Input" number_of_elements="1">
        <Proxy value="4698" output_port="0"/>
        <Domain name="groups" id="4994.Input.groups"/>
        <Domain name="input_array" id="4994.Input.input_array"/>
        <Domain name="input_type" id="4994.Input.input_type"/>
      </Property>
      <Property name="ReplaceInvalidValues" id="4994.ReplaceInvalidValues" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="4994.ReplaceInvalidValues.bool"/>
      </Property>
      <Property name="ReplacementValue" id="4994.ReplacementValue" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="range" id="4994.ReplacementValue.range"/>
      </Property>
      <Property name="ResultArrayName" id="4994.ResultArrayName" number_of_elements="1">
        <Element index="0" value="V"/>
      </Property>
      <Property name="ResultNormals" id="4994.ResultNormals" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4994.ResultNormals.bool"/>
      </Property>
      <Property name="ResultTCoords" id="4994.ResultTCoords" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4994.ResultTCoords.bool"/>
      </Property>
    </Proxy>
    <Proxy group="sources" type="PlaneSource" id="4698" servers="1">
      <Property name="Origin" id="4698.Origin" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="4698.Origin.range"/>
      </Property>
      <Property name="Point1" id="4698.Point1" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="4698.Point1.range"/>
      </Property>
      <Property name="Point2" id="4698.Point2" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="1"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="4698.Point2.range"/>
      </Property>
      <Property name="XResolution" id="4698.XResolution" number_of_elements="1">
        <Element index="0" value="10"/>
        <Domain name="range" id="4698.XResolution.range"/>
      </Property>
      <Property name="YResolution" id="4698.YResolution" number_of_elements="1">
        <Element index="0" value="10"/>
        <Domain name="range" id="4698.YResolution.range"/>
      </Property>
    </Proxy>
    <Proxy group="misc" type="TimeKeeper" id="259" servers="16">
      <Property name="SuppressedTimeSources" id="259.SuppressedTimeSources"/>
      <Property name="Time" id="259.Time" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="range" id="259.Time.range"/>
      </Property>
      <Property name="TimeLabel" id="259.TimeLabel" number_of_elements="1">
        <Element index="0" value="Time"/>
      </Property>
      <Property name="TimeRange" id="259.TimeRange" number_of_elements="2">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
      </Property>
      <Property name="TimeSources" id="259.TimeSources" number_of_elements="3">
        <Proxy value="4698"/>
        <Proxy value="4994"/>
        <Proxy value="5181"/>
      </Property>
      <Property name="TimestepValues" id="259.TimestepValues"/>
      <Property name="Views" id="259.Views" number_of_elements="1">
        <Proxy value="4720"/>
      </Property>
    </Proxy>
    <Proxy group="views" type="RenderView" id="4720" servers="21">
      <Property name="AlphaBitPlanes" id="4720.AlphaBitPlanes" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="4720.AlphaBitPlanes.bool"/>
      </Property>
      <Property name="ArrayComponentToDraw" id="4720.ArrayComponentToDraw" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="range" id="4720.ArrayComponentToDraw.range"/>
      </Property>
      <Property name="ArrayNameToDraw" id="4720.ArrayNameToDraw" number_of_elements="1">
        <Element index="0" value=""/>
      </Property>
      <Property name="ArrayNumberToDraw" id="4720.ArrayNumberToDraw" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="range" id="4720.ArrayNumberToDraw.range"/>
      </Property>
      <Property name="AxesGrid" id="4720.AxesGrid" number_of_elements="1">
        <Proxy value="4718"/>
        <Domain name="proxy_list" id="4720.AxesGrid.proxy_list">
          <Proxy value="4718"/>
        </Domain>
      </Property>
      <Property name="BackLightAzimuth" id="4720.BackLightAzimuth" number_of_elements="1">
        <Element index="0" value="110"/>
        <Domain name="range" id="4720.BackLightAzimuth.range"/>
      </Property>
      <Property name="BackLightElevation" id="4720.BackLightElevation" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="range" id="4720.BackLightElevation.range"/>
      </Property>
      <Property name="BackLightK:B Ratio" id="4720.BackLightK:B Ratio" number_of_elements="1">
        <Element index="0" value="3.5"/>
        <Domain name="range" id="4720.BackLightK:B Ratio.range"/>
      </Property>
      <Property name="BackLightWarmth" id="4720.BackLightWarmth" number_of_elements="1">
        <Element index="0" value="0.5"/>
        <Domain name="range" id="4720.BackLightWarmth.range"/>
      </Property>
      <Property name="Background" id="4720.Background" number_of_elements="3">
        <Element index="0" value="0.32"/>
        <Element index="1" value="0.34"/>
        <Element index="2" value="0.43"/>
        <Domain name="range" id="4720.Background.range"/>
      </Property>
      <Property name="Background2" id="4720.Background2" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0.165"/>
        <Domain name="range" id="4720.Background2.range"/>
      </Property>
      <Property name="BackgroundTexture" id="4720.BackgroundTexture">
        <Domain name="groups" id="4720.BackgroundTexture.groups"/>
      </Property>
      <Property name="CacheKey" id="4720.CacheKey" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="range" id="4720.CacheKey.range"/>
      </Property>
      <Property name="Camera2DManipulators" id="4720.Camera2DManipulators" number_of_elements="9">
        <Element index="0" value="1"/>
        <Element index="1" value="3"/>
        <Element index="2" value="2"/>
        <Element index="3" value="2"/>
        <Element index="4" value="2"/>
        <Element index="5" value="2"/>
        <Element index="6" value="3"/>
        <Element index="7" value="1"/>
        <Element index="8" value="4"/>
        <Domain name="enum" id="4720.Camera2DManipulators.enum">
          <Entry value="0" text="None"/>
          <Entry value="1" text="Pan"/>
          <Entry value="2" text="Zoom"/>
          <Entry value="3" text="Roll"/>
          <Entry value="4" text="Rotate"/>
        </Domain>
      </Property>
      <Property name="Camera3DManipulators" id="4720.Camera3DManipulators" number_of_elements="9">
        <Element index="0" value="4"/>
        <Element index="1" value="1"/>
        <Element index="2" value="2"/>
        <Element index="3" value="3"/>
        <Element index="4" value="4"/>
        <Element index="5" value="1"/>
        <Element index="6" value="2"/>
        <Element index="7" value="4"/>
        <Element index="8" value="2"/>
        <Domain name="enum" id="4720.Camera3DManipulators.enum">
          <Entry value="0" text="None"/>
          <Entry value="1" text="Pan"/>
          <Entry value="2" text="Zoom"/>
          <Entry value="3" text="Roll"/>
          <Entry value="4" text="Rotate"/>
          <Entry value="5" text="Multi-Rotate"/>
        </Domain>
      </Property>
      <Property name="CameraParallelProjection" id="4720.CameraParallelProjection" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4720.CameraParallelProjection.bool"/>
      </Property>
      <Property name="CaptureZBuffer" id="4720.CaptureZBuffer"/>
      <Property name="CenterAxesVisibility" id="4720.CenterAxesVisibility" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4720.CenterAxesVisibility.bool"/>
      </Property>
      <Property name="CenterOfRotation" id="4720.CenterOfRotation" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="-1e-20"/>
      </Property>
      <Property name="CollectGeometryThreshold" id="4720.CollectGeometryThreshold" number_of_elements="1">
        <Element index="0" value="100"/>
      </Property>
      <Property name="CompressorConfig" id="4720.CompressorConfig" number_of_elements="1">
        <Element index="0" value="vtkLZ4Compressor 0 3"/>
      </Property>
      <Property name="DepthPeeling" id="4720.DepthPeeling" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="4720.DepthPeeling.bool"/>
      </Property>
      <Property name="DrawCells" id="4720.DrawCells" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4720.DrawCells.bool"/>
      </Property>
      <Property name="EnableRenderOnInteraction" id="4720.EnableRenderOnInteraction" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="4720.EnableRenderOnInteraction.bool"/>
      </Property>
      <Property name="FillLightAzimuth" id="4720.FillLightAzimuth" number_of_elements="1">
        <Element index="0" value="-10"/>
        <Domain name="range" id="4720.FillLightAzimuth.range"/>
      </Property>
      <Property name="FillLightElevation" id="4720.FillLightElevation" number_of_elements="1">
        <Element index="0" value="-75"/>
        <Domain name="range" id="4720.FillLightElevation.range"/>
      </Property>
      <Property name="FillLightK:F Ratio" id="4720.FillLightK:F Ratio" number_of_elements="1">
        <Element index="0" value="3"/>
        <Domain name="range" id="4720.FillLightK:F Ratio.range"/>
      </Property>
      <Property name="FillLightWarmth" id="4720.FillLightWarmth" number_of_elements="1">
        <Element index="0" value="0.4"/>
        <Domain name="range" id="4720.FillLightWarmth.range"/>
      </Property>
      <Property name="HeadLightK:H Ratio" id="4720.HeadLightK:H Ratio" number_of_elements="1">
        <Element index="0" value="3"/>
        <Domain name="range" id="4720.HeadLightK:H Ratio.range"/>
      </Property>
      <Property name="HeadLightWarmth" id="4720.HeadLightWarmth" number_of_elements="1">
        <Element index="0" value="0.5"/>
        <Domain name="range" id="4720.HeadLightWarmth.range"/>
      </Property>
      <Property name="ImageReductionFactor" id="4720.ImageReductionFactor" number_of_elements="1">
        <Element index="0" value="2"/>
        <Domain name="range" id="4720.ImageReductionFactor.range"/>
      </Property>
      <Property name="InteractionMode" id="4720.InteractionMode" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="enum" id="4720.InteractionMode.enum">
          <Entry value="0" text="3D"/>
          <Entry value="1" text="2D"/>
          <Entry value="2" text="Selection"/>
        </Domain>
      </Property>
      <Property name="KeyLightAzimuth" id="4720.KeyLightAzimuth" number_of_elements="1">
        <Element index="0" value="10"/>
        <Domain name="range" id="4720.KeyLightAzimuth.range"/>
      </Property>
      <Property name="KeyLightElevation" id="4720.KeyLightElevation" number_of_elements="1">
        <Element index="0" value="50"/>
        <Domain name="range" id="4720.KeyLightElevation.range"/>
      </Property>
      <Property name="KeyLightIntensity" id="4720.KeyLightIntensity" number_of_elements="1">
        <Element index="0" value="0.75"/>
        <Domain name="range" id="4720.KeyLightIntensity.range"/>
      </Property>
      <Property name="KeyLightWarmth" id="4720.KeyLightWarmth" number_of_elements="1">
        <Element index="0" value="0.6"/>
        <Domain name="range" id="4720.KeyLightWarmth.range"/>
      </Property>
      <Property name="LODResolution" id="4720.LODResolution" number_of_elements="1">
        <Element index="0" value="0.5"/>
        <Domain name="range" id="4720.LODResolution.range"/>
      </Property>
      <Property name="LODThreshold" id="4720.LODThreshold" number_of_elements="1">
        <Element index="0" value="20"/>
        <Domain name="range" id="4720.LODThreshold.range"/>
      </Property>
      <Property name="LightAmbientColor" id="4720.LightAmbientColor" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="1"/>
        <Element index="2" value="1"/>
        <Domain name="range" id="4720.LightAmbientColor.range"/>
      </Property>
      <Property name="LightDiffuseColor" id="4720.LightDiffuseColor" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="1"/>
        <Element index="2" value="1"/>
        <Domain name="range" id="4720.LightDiffuseColor.range"/>
      </Property>
      <Property name="LightIntensity" id="4720.LightIntensity" number_of_elements="1">
        <Element index="0" value="0.1"/>
        <Domain name="range" id="4720.LightIntensity.range"/>
      </Property>
      <Property name="LightSpecularColor" id="4720.LightSpecularColor" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="1"/>
        <Element index="2" value="1"/>
        <Domain name="range" id="4720.LightSpecularColor.range"/>
      </Property>
      <Property name="LightSwitch" id="4720.LightSwitch" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="4720.LightSwitch.bool"/>
      </Property>
      <Property name="LightType" id="4720.LightType" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="enum" id="4720.LightType.enum">
          <Entry value="1" text="HeadLight"/>
          <Entry value="2" text="CameraLight"/>
          <Entry value="3" text="SceneLight"/>
        </Domain>
      </Property>
      <Property name="LockBounds" id="4720.LockBounds" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4720.LockBounds.bool"/>
      </Property>
      <Property name="MaintainLuminance" id="4720.MaintainLuminance" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4720.MaintainLuminance.bool"/>
      </Property>
      <Property name="MaximumNumberOfPeels" id="4720.MaximumNumberOfPeels" number_of_elements="1">
        <Element index="0" value="4"/>
        <Domain name="range" id="4720.MaximumNumberOfPeels.range"/>
      </Property>
      <Property name="MultiSamples" id="4720.MultiSamples" number_of_elements="1">
        <Element index="0" value="0"/>
      </Property>
      <Property name="NonInteractiveRenderDelay" id="4720.NonInteractiveRenderDelay" number_of_elements="1">
        <Element index="0" value="0"/>
      </Property>
      <Property name="OrientationAxesInteractivity" id="4720.OrientationAxesInteractivity" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4720.OrientationAxesInteractivity.bool"/>
      </Property>
      <Property name="OrientationAxesLabelColor" id="4720.OrientationAxesLabelColor" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="1"/>
        <Element index="2" value="1"/>
      </Property>
      <Property name="OrientationAxesOutlineColor" id="4720.OrientationAxesOutlineColor" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="1"/>
        <Element index="2" value="1"/>
      </Property>
      <Property name="OrientationAxesVisibility" id="4720.OrientationAxesVisibility" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4720.OrientationAxesVisibility.bool"/>
      </Property>
      <Property name="RemoteRenderThreshold" id="4720.RemoteRenderThreshold" number_of_elements="1">
        <Element index="0" value="20"/>
        <Domain name="range" id="4720.RemoteRenderThreshold.range"/>
      </Property>
      <Property name="Representations" id="4720.Representations" number_of_elements="4">
        <Proxy value="4961"/>
        <Proxy value="5162"/>
        <Proxy value="5180"/>
        <Proxy value="5349"/>
      </Property>
      <Property name="RotationFactor" id="4720.RotationFactor" number_of_elements="1">
        <Element index="0" value="1"/>
      </Property>
      <Property name="ScalarRange" id="4720.ScalarRange" number_of_elements="2">
        <Element index="0" value="0"/>
        <Element index="1" value="-1"/>
        <Domain name="range" id="4720.ScalarRange.range"/>
      </Property>
      <Property name="ServerStereoType" id="4720.ServerStereoType" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="enum" id="4720.ServerStereoType.enum">
          <Entry value="0" text="Same As Client"/>
          <Entry value="1" text="Crystal Eyes"/>
          <Entry value="2" text="Red-Blue"/>
          <Entry value="3" text="Interlaced"/>
          <Entry value="4" text="Left"/>
          <Entry value="5" text="Right"/>
          <Entry value="6" text="Dresden"/>
          <Entry value="7" text="Anaglyph"/>
          <Entry value="8" text="Checkerboard"/>
          <Entry value="9" text="SplitViewportHorizontal"/>
          <Entry value="10" text="None"/>
        </Domain>
      </Property>
      <Property name="ShowAnnotation" id="4720.ShowAnnotation" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4720.ShowAnnotation.bool"/>
      </Property>
      <Property name="StartCaptureLuminance" id="4720.StartCaptureLuminance"/>
      <Property name="StartCaptureValues" id="4720.StartCaptureValues"/>
      <Property name="StencilCapable" id="4720.StencilCapable" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="4720.StencilCapable.bool"/>
      </Property>
      <Property name="StereoRender" id="4720.StereoRender" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4720.StereoRender.bool"/>
      </Property>
      <Property name="StereoType" id="4720.StereoType" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="enum" id="4720.StereoType.enum">
          <Entry value="1" text="Crystal Eyes"/>
          <Entry value="2" text="Red-Blue"/>
          <Entry value="3" text="Interlaced"/>
          <Entry value="4" text="Left"/>
          <Entry value="5" text="Right"/>
          <Entry value="6" text="Dresden"/>
          <Entry value="7" text="Anaglyph"/>
          <Entry value="8" text="Checkerboard"/>
          <Entry value="9" text="SplitViewportHorizontal"/>
          <Entry value="10" text="None"/>
        </Domain>
      </Property>
      <Property name="StillRenderImageReductionFactor" id="4720.StillRenderImageReductionFactor" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="4720.StillRenderImageReductionFactor.range"/>
      </Property>
      <Property name="StopCaptureLuminance" id="4720.StopCaptureLuminance"/>
      <Property name="StopCaptureValues" id="4720.StopCaptureValues"/>
      <Property name="UseCache" id="4720.UseCache" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4720.UseCache.bool"/>
      </Property>
      <Property name="UseGradientBackground" id="4720.UseGradientBackground" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4720.UseGradientBackground.bool"/>
      </Property>
      <Property name="UseInteractiveRenderingForScreenshots" id="4720.UseInteractiveRenderingForScreenshots" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4720.UseInteractiveRenderingForScreenshots.bool"/>
      </Property>
      <Property name="UseLight" id="4720.UseLight" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="4720.UseLight.bool"/>
      </Property>
      <Property name="UseOffscreenRendering" id="4720.UseOffscreenRendering" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4720.UseOffscreenRendering.bool"/>
      </Property>
      <Property name="UseOffscreenRenderingForScreenshots" id="4720.UseOffscreenRenderingForScreenshots" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4720.UseOffscreenRenderingForScreenshots.bool"/>
      </Property>
      <Property name="UseOutlineForLODRendering" id="4720.UseOutlineForLODRendering" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4720.UseOutlineForLODRendering.bool"/>
      </Property>
      <Property name="UseTexturedBackground" id="4720.UseTexturedBackground" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4720.UseTexturedBackground.bool"/>
      </Property>
      <Property name="ViewSize" id="4720.ViewSize" number_of_elements="2">
        <Element index="0" value="1544"/>
        <Element index="1" value="1059"/>
      </Property>
      <Property name="ViewTime" id="4720.ViewTime" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="range" id="4720.ViewTime.range"/>
      </Property>
      <Property name="CameraClippingRange" id="4720.CameraClippingRange" number_of_elements="2">
        <Element index="0" value="6.62520912560344"/>
        <Element index="1" value="6.792512386351"/>
      </Property>
      <Property name="CameraClippingRangeInfo" id="4720.CameraClippingRangeInfo" number_of_elements="2">
        <Element index="0" value="6.62520912560344"/>
        <Element index="1" value="6.792512386351"/>
      </Property>
      <Property name="CameraFocalPoint" id="4720.CameraFocalPoint" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="-1e-20"/>
      </Property>
      <Property name="CameraFocalPointInfo" id="4720.CameraFocalPointInfo" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="-1e-20"/>
      </Property>
      <Property name="CameraParallelScale" id="4720.CameraParallelScale" number_of_elements="1">
        <Element index="0" value="1.73205080756888"/>
      </Property>
      <Property name="CameraParallelScaleInfo" id="4720.CameraParallelScaleInfo" number_of_elements="1">
        <Element index="0" value="1.73205080756888"/>
      </Property>
      <Property name="CameraPosition" id="4720.CameraPosition" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="6.69213042990246"/>
      </Property>
      <Property name="CameraPositionInfo" id="4720.CameraPositionInfo" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="6.69213042990246"/>
      </Property>
      <Property name="CameraViewAngle" id="4720.CameraViewAngle" number_of_elements="1">
        <Element index="0" value="30"/>
      </Property>
      <Property name="CameraViewUp" id="4720.CameraViewUp" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="1"/>
        <Element index="2" value="0"/>
      </Property>
      <Property name="CameraViewUpInfo" id="4720.CameraViewUpInfo" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="1"/>
        <Element index="2" value="0"/>
      </Property>
      <Property name="EyeAngle" id="4720.EyeAngle" number_of_elements="1">
        <Element index="0" value="2"/>
        <Domain name="range" id="4720.EyeAngle.range"/>
      </Property>
    </Proxy>
    <ProxyCollection name="animation">
      <Item id="263" name="AnimationScene1"/>
      <Item id="265" name="TimeAnimationCue1"/>
    </ProxyCollection>
    <ProxyCollection name="layouts">
      <Item id="2874" name="ViewLayout1"/>
    </ProxyCollection>
    <ProxyCollection name="lookup_tables">
      <Item id="5174" name="V.PVLookupTable"/>
    </ProxyCollection>
    <ProxyCollection name="piecewise_functions">
      <Item id="5173" name="V.PiecewiseFunction"/>
    </ProxyCollection>
    <ProxyCollection name="pq_helper_proxies.4698">
      <Item id="4710" name="RepresentationAnimationHelper"/>
    </ProxyCollection>
    <ProxyCollection name="pq_helper_proxies.4720">
      <Item id="4718" name="AxesGrid"/>
    </ProxyCollection>
    <ProxyCollection name="pq_helper_proxies.4961">
      <Item id="4816" name="GlyphType"/>
      <Item id="4827" name="GlyphType"/>
      <Item id="4838" name="GlyphType"/>
      <Item id="4849" name="GlyphType"/>
      <Item id="4860" name="GlyphType"/>
      <Item id="4871" name="GlyphType"/>
      <Item id="4882" name="GlyphType"/>
      <Item id="4915" name="OpacityTransferFunction"/>
      <Item id="4916" name="ScaleTransferFunction"/>
    </ProxyCollection>
    <ProxyCollection name="pq_helper_proxies.4994">
      <Item id="5005" name="RepresentationAnimationHelper"/>
    </ProxyCollection>
    <ProxyCollection name="pq_helper_proxies.5162">
      <Item id="5017" name="GlyphType"/>
      <Item id="5028" name="GlyphType"/>
      <Item id="5039" name="GlyphType"/>
      <Item id="5050" name="GlyphType"/>
      <Item id="5061" name="GlyphType"/>
      <Item id="5072" name="GlyphType"/>
      <Item id="5083" name="GlyphType"/>
      <Item id="5116" name="OpacityTransferFunction"/>
      <Item id="5117" name="ScaleTransferFunction"/>
    </ProxyCollection>
    <ProxyCollection name="pq_helper_proxies.5181">
      <Item id="5192" name="RepresentationAnimationHelper"/>
    </ProxyCollection>
    <ProxyCollection name="pq_helper_proxies.5349">
      <Item id="5204" name="GlyphType"/>
      <Item id="5215" name="GlyphType"/>
      <Item id="5226" name="GlyphType"/>
      <Item id="5237" name="GlyphType"/>
      <Item id="5248" name="GlyphType"/>
      <Item id="5259" name="GlyphType"/>
      <Item id="5270" name="GlyphType"/>
      <Item id="5303" name="OpacityTransferFunction"/>
      <Item id="5304" name="ScaleTransferFunction"/>
    </ProxyCollection>
    <ProxyCollection name="representations">
      <Item id="4961" name="GeometryRepresentation1"/>
      <Item id="5162" name="GeometryRepresentation2"/>
      <Item id="5349" name="GeometryRepresentation3"/>
    </ProxyCollection>
    <ProxyCollection name="scalar_bars">
      <Item id="5180" name="ScalarBarWidgetRepresentation1"/>
    </ProxyCollection>
    <ProxyCollection name="sources">
      <Item id="5181" name="AngularPeriodicFilter1"/>
      <Item id="4994" name="Calculator1"/>
      <Item id="4698" name="Plane1"/>
    </ProxyCollection>
    <ProxyCollection name="timekeeper">
      <Item id="259" name="TimeKeeper1"/>
    </ProxyCollection>
    <ProxyCollection name="views">
      <Item id="4720" name="RenderView1"/>
    </ProxyCollection>
    <CustomProxyDefinitions>
      <CustomProxyDefinition name="Contour sub range" group="filters">
        <CompoundSourceProxy id="3086" servers="1">
          <Proxy group="filters" type="IsoVolume" id="2718" servers="1" compound_name="IsoVolume2">
            <Property name="Input" id="2718.Input" number_of_elements="1">
              <Domain name="groups" id="2718.Input.groups"/>
              <Domain name="input_array" id="2718.Input.input_array">
                <InputArray attribute_type="any" number_of_components="1"/>
              </Domain>
              <Domain name="input_type" id="2718.Input.input_type"/>
            </Property>
            <Property name="SelectInputScalars" id="2718.SelectInputScalars" number_of_elements="5">
              <Element index="0" value=""/>
              <Element index="1" value=""/>
              <Element index="2" value=""/>
              <Element index="3" value="0"/>
              <Element index="4" value="Result"/>
              <Domain name="array_list" id="2718.SelectInputScalars.array_list">
                <String text="Result"/>
              </Domain>
              <Domain name="field_list" id="2718.SelectInputScalars.field_list">
                <Entry value="0" text="Point Data"/>
              </Domain>
            </Property>
            <Property name="ThresholdBetween" id="2718.ThresholdBetween" number_of_elements="2">
              <Element index="0" value="7280"/>
              <Element index="1" value="7350"/>
              <Domain name="range" id="2718.ThresholdBetween.range"/>
            </Property>
          </Proxy>
          <Proxy group="filters" type="IsoVolume" id="2823" servers="1" compound_name="IsoVolume3">
            <Property name="Input" id="2823.Input" number_of_elements="1">
              <Domain name="groups" id="2823.Input.groups"/>
              <Domain name="input_array" id="2823.Input.input_array">
                <InputArray attribute_type="any" number_of_components="1"/>
              </Domain>
              <Domain name="input_type" id="2823.Input.input_type"/>
            </Property>
            <Property name="SelectInputScalars" id="2823.SelectInputScalars" number_of_elements="5">
              <Element index="0" value=""/>
              <Element index="1" value=""/>
              <Element index="2" value=""/>
              <Element index="3" value="0"/>
              <Element index="4" value="Result"/>
              <Domain name="array_list" id="2823.SelectInputScalars.array_list">
                <String text="Result"/>
              </Domain>
              <Domain name="field_list" id="2823.SelectInputScalars.field_list">
                <Entry value="0" text="Point Data"/>
              </Domain>
            </Property>
            <Property name="ThresholdBetween" id="2823.ThresholdBetween" number_of_elements="2">
              <Element index="0" value="7350"/>
              <Element index="1" value="284652"/>
              <Domain name="range" id="2823.ThresholdBetween.range"/>
            </Property>
          </Proxy>
          <Proxy group="filters" type="IsoVolume" id="2940" servers="1" compound_name="IsoVolume5">
            <Property name="Input" id="2940.Input" number_of_elements="1">
              <Domain name="groups" id="2940.Input.groups"/>
              <Domain name="input_array" id="2940.Input.input_array">
                <InputArray attribute_type="any" number_of_components="1"/>
              </Domain>
              <Domain name="input_type" id="2940.Input.input_type"/>
            </Property>
            <Property name="SelectInputScalars" id="2940.SelectInputScalars" number_of_elements="5">
              <Element index="0" value=""/>
              <Element index="1" value=""/>
              <Element index="2" value=""/>
              <Element index="3" value="0"/>
              <Element index="4" value="Result"/>
              <Domain name="array_list" id="2940.SelectInputScalars.array_list">
                <String text="Result"/>
              </Domain>
              <Domain name="field_list" id="2940.SelectInputScalars.field_list">
                <Entry value="0" text="Point Data"/>
              </Domain>
            </Property>
            <Property name="ThresholdBetween" id="2940.ThresholdBetween" number_of_elements="2">
              <Element index="0" value="53.0015983581543"/>
              <Element index="1" value="7280"/>
              <Domain name="range" id="2940.ThresholdBetween.range"/>
            </Property>
          </Proxy>
          <ExposedProperties>
            <Property name="ThresholdBetween" proxy_name="IsoVolume5" exposed_name="Threshold Range"/>
            <Property name="Input" proxy_name="IsoVolume2" exposed_name="lower"/>
            <Property name="Input" proxy_name="IsoVolume5" exposed_name="lower value"/>
            <Property name="Input" proxy_name="IsoVolume3" exposed_name="upper"/>
          </ExposedProperties>
          <OutputPort name="aedf" proxy="IsoVolume5" port_index="0"/>
          <Hints>
            <ShowInMenu/>
          </Hints>
        </CompoundSourceProxy>
      </CustomProxyDefinition>
      <CustomProxyDefinition name="poo" group="filters">
        <CompoundSourceProxy id="5033" servers="1">
          <Proxy group="filters" type="Cut" id="135" servers="1" compound_name="Slice1">
            <Property name="ContourValues" id="135.ContourValues" number_of_elements="1">
              <Element index="0" value="0"/>
              <Domain name="bounds" id="135.ContourValues.bounds">
                <Min index="0" value="-0.416506"/>
                <Max index="0" value="0.416506"/>
              </Domain>
            </Property>
            <Property name="CutFunction" id="135.CutFunction" number_of_elements="1">
              <Proxy value="129"/>
              <Domain name="groups" id="135.CutFunction.groups">
                <Group value="implicit_functions"/>
              </Domain>
              <Domain name="proxy_list" id="135.CutFunction.proxy_list">
                <Proxy value="129"/>
                <Proxy value="131"/>
                <Proxy value="133"/>
              </Domain>
            </Property>
            <Property name="Input" id="135.Input" number_of_elements="1">
              <Domain name="groups" id="135.Input.groups">
                <Group value="sources"/>
                <Group value="filters"/>
              </Domain>
              <Domain name="input_type" id="135.Input.input_type">
                <DataType value="vtkDataSet"/>
              </Domain>
            </Property>
            <Property name="InputBounds" id="135.InputBounds">
              <Domain name="bounds" id="135.InputBounds.bounds">
                <Min index="0" value="-0.244"/>
                <Min index="1" value="-0.244"/>
                <Min index="2" value="-0.23325"/>
                <Max index="0" value="0.244"/>
                <Max index="1" value="0.244"/>
                <Max index="2" value="0.23325"/>
              </Domain>
            </Property>
          </Proxy>
          <Proxy group="implicit_functions" type="Plane" id="129" servers="1" compound_name="auto_129">
            <Property name="Normal" id="129.Normal" number_of_elements="3">
              <Element index="0" value="1"/>
              <Element index="1" value="0"/>
              <Element index="2" value="0"/>
              <Domain name="range" id="129.Normal.range"/>
            </Property>
            <Property name="Offset" id="129.Offset" number_of_elements="1">
              <Element index="0" value="0"/>
              <Domain name="range" id="129.Offset.range"/>
            </Property>
            <Property name="Origin" id="129.Origin" number_of_elements="3">
              <Element index="0" value="0"/>
              <Element index="1" value="0"/>
              <Element index="2" value="0"/>
              <Domain name="range" id="129.Origin.range"/>
            </Property>
          </Proxy>
          <ExposedProperties>
            <Property name="Input" proxy_name="Slice1" exposed_name="Input"/>
          </ExposedProperties>
          <OutputPort name="Output" proxy="Slice1" port_index="0"/>
          <Hints>
            <ShowInMenu/>
          </Hints>
        </CompoundSourceProxy>
      </CustomProxyDefinition>
    </CustomProxyDefinitions>
    <Links>
      <GlobalPropertyLink global_name="BackgroundColor" proxy="4720" property="Background"/>
      <GlobalPropertyLink global_name="EdgeColor" proxy="4961" property="EdgeColor"/>
      <GlobalPropertyLink global_name="EdgeColor" proxy="5162" property="EdgeColor"/>
      <GlobalPropertyLink global_name="EdgeColor" proxy="5349" property="EdgeColor"/>
      <GlobalPropertyLink global_name="ForegroundColor" proxy="4718" property="GridColor"/>
      <GlobalPropertyLink global_name="ForegroundColor" proxy="4720" property="OrientationAxesOutlineColor"/>
      <GlobalPropertyLink global_name="ForegroundColor" proxy="4961" property="AmbientColor"/>
      <GlobalPropertyLink global_name="ForegroundColor" proxy="4961" property="Color"/>
      <GlobalPropertyLink global_name="ForegroundColor" proxy="4961" property="CubeAxesColor"/>
      <GlobalPropertyLink global_name="ForegroundColor" proxy="5162" property="AmbientColor"/>
      <GlobalPropertyLink global_name="ForegroundColor" proxy="5162" property="Color"/>
      <GlobalPropertyLink global_name="ForegroundColor" proxy="5162" property="CubeAxesColor"/>
      <GlobalPropertyLink global_name="ForegroundColor" proxy="5349" property="AmbientColor"/>
      <GlobalPropertyLink global_name="ForegroundColor" proxy="5349" property="Color"/>
      <GlobalPropertyLink global_name="ForegroundColor" proxy="5349" property="CubeAxesColor"/>
      <GlobalPropertyLink global_name="SelectionColor" proxy="4961" property="SelectionColor"/>
      <GlobalPropertyLink global_name="SelectionColor" proxy="5162" property="SelectionColor"/>
      <GlobalPropertyLink global_name="SelectionColor" proxy="5349" property="SelectionColor"/>
      <GlobalPropertyLink global_name="SurfaceColor" proxy="4961" property="BackfaceDiffuseColor"/>
      <GlobalPropertyLink global_name="SurfaceColor" proxy="4961" property="DiffuseColor"/>
      <GlobalPropertyLink global_name="SurfaceColor" proxy="5162" property="BackfaceDiffuseColor"/>
      <GlobalPropertyLink global_name="SurfaceColor" proxy="5162" property="DiffuseColor"/>
      <GlobalPropertyLink global_name="SurfaceColor" proxy="5349" property="BackfaceDiffuseColor"/>
      <GlobalPropertyLink global_name="SurfaceColor" proxy="5349" property="DiffuseColor"/>
      <GlobalPropertyLink global_name="TextAnnotationColor" proxy="4718" property="XLabelColor"/>
      <GlobalPropertyLink global_name="TextAnnotationColor" proxy="4718" property="XTitleColor"/>
      <GlobalPropertyLink global_name="TextAnnotationColor" proxy="4718" property="YLabelColor"/>
      <GlobalPropertyLink global_name="TextAnnotationColor" proxy="4718" property="YTitleColor"/>
      <GlobalPropertyLink global_name="TextAnnotationColor" proxy="4718" property="ZLabelColor"/>
      <GlobalPropertyLink global_name="TextAnnotationColor" proxy="4718" property="ZTitleColor"/>
      <GlobalPropertyLink global_name="TextAnnotationColor" proxy="4720" property="OrientationAxesLabelColor"/>
      <GlobalPropertyLink global_name="TextAnnotationColor" proxy="5180" property="LabelColor"/>
      <GlobalPropertyLink global_name="TextAnnotationColor" proxy="5180" property="TitleColor"/>
      <GlobalPropertyLink global_name="UseGradientBackground" proxy="4720" property="UseGradientBackground"/>
    </Links>
  </ServerManagerState>
</ParaView>

From cory.quammen at kitware.com  Tue Apr 19 09:36:59 2016
From: cory.quammen at kitware.com (Cory Quammen)
Date: Tue, 19 Apr 2016 09:36:59 -0400
Subject: [Paraview] Error in Launching Paraview 5.0.0
In-Reply-To: <BBF23853DD0BE54FB8F0F12A6F06A1DA3705256D@blrkecmbx15.ad.infosys.com>
References: <BBF23853DD0BE54FB8F0F12A6F06A1DA3705256D@blrkecmbx15.ad.infosys.com>
Message-ID: <CAB5Fpx593D9fOWbG=q+Yyen49riiF4fN1sa9riWvU-V+e_z8uw@mail.gmail.com>

Hi Mandar,

Could you try something?

Under

C:\Users\<username>\AppData\Roaming

could you rename the ParaView directory to ParaView-backup? Then try to
start ParaView again.

If ParaView starts up, would you mind sending me in a private message you
settings files in ParaV/iew-backup? I would like to track down the cause of
the crash.

Thanks,
Cory

On Tue, Apr 19, 2016 at 7:15 AM, Mandar Prakash Shirke <
Mandar.Shirke at infosys.com> wrote:

> Hello,
>
>
>
> I have been trying to install Paraview (5.0.0_64b) but after installation,
> application does not launch. It says "Paraview.exe has stopped working".
> Please find below screenshot.
>
>
>
> I tried Paraview 4.1 & Paraview 3.12 & both are running fine. I am getting
> this error only for Paraview 5.0.
>
>
>
> Please suggest a solution.
>
>
>
> Regards,
>
> Mandar
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview
>
>


-- 
Cory Quammen
R&D Engineer
Kitware, Inc.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160419/ed3767a6/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 134462 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160419/ed3767a6/attachment.png>

From archaerolog at mail.ru  Tue Apr 19 10:08:26 2016
From: archaerolog at mail.ru (Gena Bug)
Date: Tue, 19 Apr 2016 17:08:26 +0300
Subject: [Paraview] Fwd: Re:  negative value for a vector' magnitude
In-Reply-To: <57162DAE.3040305@mail.ru>
References: <57162DAE.3040305@mail.ru>
Message-ID: <57163BDA.4080105@mail.ru>

-------- Forwarded Message --------
Subject: Re: [Paraview] negative value for a vector' magnitude
Date: Tue, 19 Apr 2016 16:07:58 +0300
From: Gena Bug <archaerolog at mail.ru>
To: Mandar Prakash Shirke <Mandar.Shirke at infosys.com>

On 19.04.2016 15:20, Mandar Prakash Shirke wrote:
> Hello,
Hi,

> Thank you for reply.
> I did not understand what you said here & there is no file with name "negative_magnitude.pvsm" in Paraview directory.
OK, let me explain it again: angular periodic filter creates full region
from a partial one, also, despite transform filter, it correctly handle
vector fields. However, rescale to data range doesn't work for vector
fields in the complete region -- minimum value of magnitude is negative.

Now step-by-step:
1. create a plane [0, 1]x[0, 1]:
Source -> Plane (Origin (0, 0, 0), Point1 (1, 0, 0), Point2 (0, 1, 0))
2. create a vector field in it:
Calculator (Point Data: coordsX*iHat + coordsY*jHat)
3. create a full region [-1, 1]x[-1, 1] from the plane:
AngularPeriodicFilter (Rotation Angle 90, Axis: Axis Z)
4. Activate coloring for the vector field in the full region.

After step 4 I see next (see snapshot.png).

In the previous email I attached a state file with these steps.

> Please find attached screenshot of error.
Don't understand how this message corresponds to the problem... Is it
happen when you try to load the state file?

>
> Regards,
> Mandar
>
> -----Original Message-----
> From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Gena Bug
> Sent: Tuesday, April 19, 2016 5:32 PM
> To: ParaView <paraview at paraview.org>
> Subject: [Paraview] negative value for a vector' magnitude
>
> Hi,
>
> I noticed that visualizing a vector' magnitude is incorrect -- minimum value in the range of values is negative. It happens when using AngularPeriodicFilter (see example in the attachment).
>
> OS: Debian testing amd64
> PV: v.5.0.1 downloaded from the site
>



-------------- next part --------------
A non-text attachment was scrubbed...
Name: snapshot.png
Type: image/png
Size: 216914 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160419/c3c10bf5/attachment-0001.png>

From masood.molaei at gmail.com  Tue Apr 19 10:46:02 2016
From: masood.molaei at gmail.com (masood molaei)
Date: Tue, 19 Apr 2016 18:16:02 +0330
Subject: [Paraview] Error in Launching Paraview 5.0.0
In-Reply-To: <BBF23853DD0BE54FB8F0F12A6F06A1DA3705256D@blrkecmbx15.ad.infosys.com>
References: <BBF23853DD0BE54FB8F0F12A6F06A1DA3705256D@blrkecmbx15.ad.infosys.com>
Message-ID: <CADQW_qwacE_vCirKPQuVN98H7c1kUSvECY8bMhX5Y02O1K3E_A@mail.gmail.com>

Dear Cory,

I had the same problem and solved it. You must update your driver of
VGA card. You can do it using "DriverPack Solution." This worked out
for me. Hope you will find it useful as well.

Bests,
Masoud

On 4/19/16, Mandar Prakash Shirke <Mandar.Shirke at infosys.com> wrote:
> Hello,
>
> I have been trying to install Paraview (5.0.0_64b) but after installation,
> application does not launch. It says "Paraview.exe has stopped working".
> Please find below screenshot.
> [cid:image001.png at 01D19A5A.DA9C5E30]
>
> I tried Paraview 4.1 & Paraview 3.12 & both are running fine. I am getting
> this error only for Paraview 5.0.
>
> Please suggest a solution.
>
> Regards,
> Mandar
>

From kmorel at sandia.gov  Tue Apr 19 11:09:38 2016
From: kmorel at sandia.gov (Moreland, Kenneth)
Date: Tue, 19 Apr 2016 15:09:38 +0000
Subject: [Paraview] Fwd: Re:  negative value for a vector' magnitude
Message-ID: <09465658-8487-44FB-B508-02C1761CA3CB@sandia.gov>

That is clearly wrong, and I also see the same behavior. The problem appears to be in the handling of the data from the Angular Periodic Filter, which is a pretty new feature in ParaView. I?ve submitted a bug:

http://www.paraview.org/Bug/view.php?id=16079

A simple workaround is to use the calculator filter to compute the magnitude. The result of that comes out correct.

-Ken

On 4/19/16, 8:08 AM, "ParaView on behalf of Gena Bug" <paraview-bounces at paraview.org on behalf of archaerolog at mail.ru> wrote:

>-------- Forwarded Message --------
>Subject: Re: [Paraview] negative value for a vector' magnitude
>Date: Tue, 19 Apr 2016 16:07:58 +0300
>From: Gena Bug <archaerolog at mail.ru>
>To: Mandar Prakash Shirke <Mandar.Shirke at infosys.com>
>
>On 19.04.2016 15:20, Mandar Prakash Shirke wrote:
>> Hello,
>Hi,
>
>> Thank you for reply.
>> I did not understand what you said here & there is no file with name "negative_magnitude.pvsm" in Paraview directory.
>OK, let me explain it again: angular periodic filter creates full region
>from a partial one, also, despite transform filter, it correctly handle
>vector fields. However, rescale to data range doesn't work for vector
>fields in the complete region -- minimum value of magnitude is negative.
>
>Now step-by-step:
>1. create a plane [0, 1]x[0, 1]:
>Source -> Plane (Origin (0, 0, 0), Point1 (1, 0, 0), Point2 (0, 1, 0))
>2. create a vector field in it:
>Calculator (Point Data: coordsX*iHat + coordsY*jHat)
>3. create a full region [-1, 1]x[-1, 1] from the plane:
>AngularPeriodicFilter (Rotation Angle 90, Axis: Axis Z)
>4. Activate coloring for the vector field in the full region.
>
>After step 4 I see next (see snapshot.png).
>
>In the previous email I attached a state file with these steps.
>
>> Please find attached screenshot of error.
>Don't understand how this message corresponds to the problem... Is it
>happen when you try to load the state file?
>
>>
>> Regards,
>> Mandar
>>
>> -----Original Message-----
>> From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Gena Bug
>> Sent: Tuesday, April 19, 2016 5:32 PM
>> To: ParaView <paraview at paraview.org>
>> Subject: [Paraview] negative value for a vector' magnitude
>>
>> Hi,
>>
>> I noticed that visualizing a vector' magnitude is incorrect -- minimum value in the range of values is negative. It happens when using AngularPeriodicFilter (see example in the attachment).
>>
>> OS: Debian testing amd64
>> PV: v.5.0.1 downloaded from the site
>>
>
>
>


From wascott at sandia.gov  Tue Apr 19 12:59:08 2016
From: wascott at sandia.gov (Scott, W Alan)
Date: Tue, 19 Apr 2016 16:59:08 +0000
Subject: [Paraview] [EXTERNAL] Store defaults for "Save data..." with
 CSV data
In-Reply-To: <1943FB0A-57D9-4D62-8E4E-ED08A397F763@aia.rwth-aachen.de>
References: <1943FB0A-57D9-4D62-8E4E-ED08A397F763@aia.rwth-aachen.de>
Message-ID: <cb2d249952d54ad8b244dc25033c604e@ES01AMSNLNT.srn.sandia.gov>

This sounds reasonable.  I wrote it up here http://www.paraview.org/Bug/view.php?id=16080.

Alan

From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Schlottke-Lakemper, Michael
Sent: Tuesday, April 19, 2016 2:01 AM
To: ParaView <paraview at paraview.org>
Subject: [EXTERNAL] [Paraview] Store defaults for "Save data..." with CSV data

Hi folks,

Is there a possibility to store the defaults when saving data as CSV (e.g. from the Plot over line filter)? Right now I always have to confirm that data is gathered on a single process before saving and I have to set the precision and scientific notation options manually. Preferably in PV, but if there is a config file I can edit, I?d be happy as well.

Yours

Michael

--
Michael Schlottke-Lakemper

Chair of Fluid Mechanics and Institute of Aerodynamics
RWTH Aachen University
W?llnerstra?e 5a
52062 Aachen
Germany

Phone: +49 (241) 80 95188
Fax: +49 (241) 80 92257
Mail: m.schlottke-lakemper at aia.rwth-aachen.de<mailto:m.schlottke-lakemper at aia.rwth-aachen.de>
Web: http://www.aia.rwth-aachen.de

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160419/11a3b928/attachment.html>

From m.schlottke-lakemper at aia.rwth-aachen.de  Tue Apr 19 13:42:19 2016
From: m.schlottke-lakemper at aia.rwth-aachen.de (Schlottke-Lakemper, Michael)
Date: Tue, 19 Apr 2016 17:42:19 +0000
Subject: [Paraview] [EXTERNAL] Store defaults for "Save data..." with
 CSV data
In-Reply-To: <cb2d249952d54ad8b244dc25033c604e@ES01AMSNLNT.srn.sandia.gov>
References: <1943FB0A-57D9-4D62-8E4E-ED08A397F763@aia.rwth-aachen.de>
 <cb2d249952d54ad8b244dc25033c604e@ES01AMSNLNT.srn.sandia.gov>
Message-ID: <7896A855-E629-461A-83B3-1E3A4DA3775A@aia.rwth-aachen.de>

Thanks for the quick feedback! Is there a way to track the issue on MantisBT, i.e., to get notified if there are changes to it? Also, I can?t seem to find the https Version of MantisBT (or at least the login page) - is there something I?m missing?

Regards,

Michael

On 19 Apr 2016, at 18:59 , Scott, W Alan <wascott at sandia.gov<mailto:wascott at sandia.gov>> wrote:

This sounds reasonable.  I wrote it up here http://www.paraview.org/Bug/view.php?id=16080.

Alan

From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Schlottke-Lakemper, Michael
Sent: Tuesday, April 19, 2016 2:01 AM
To: ParaView <paraview at paraview.org<mailto:paraview at paraview.org>>
Subject: [EXTERNAL] [Paraview] Store defaults for "Save data..." with CSV data

Hi folks,

Is there a possibility to store the defaults when saving data as CSV (e.g. from the Plot over line filter)? Right now I always have to confirm that data is gathered on a single process before saving and I have to set the precision and scientific notation options manually. Preferably in PV, but if there is a config file I can edit, I?d be happy as well.

Yours

Michael

--
Michael Schlottke-Lakemper

Chair of Fluid Mechanics and Institute of Aerodynamics
RWTH Aachen University
W?llnerstra?e 5a
52062 Aachen
Germany

Phone: +49 (241) 80 95188
Fax: +49 (241) 80 92257
Mail: m.schlottke-lakemper at aia.rwth-aachen.de<mailto:m.schlottke-lakemper at aia.rwth-aachen.de>
Web: http://www.aia.rwth-aachen.de<http://www.aia.rwth-aachen.de/>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160419/502a4b2a/attachment.html>

From generacy at gmail.com  Tue Apr 19 14:14:48 2016
From: generacy at gmail.com (Generacy G)
Date: Tue, 19 Apr 2016 11:14:48 -0700
Subject: [Paraview] Several questions regarding Image Data to AMR
Message-ID: <CA+2xwH3mehof-n9ug1SbYyZeoSJLry8+hgBoLLdAkY4nH5vKFA@mail.gmail.com>

I have a block of data that I am trying to AMR. Using the default settings
of num levels 2 and refinement ratio 2, I get an AMR with 2 levels but with
same dimensions. I was hoping for level 1 to be the same dimensions as my
original dataset, and level 0 to be half that in each dimension. How would
I go about doing that? I?ve tried with varying levels of max num blocks. I
guess my general question would be how the resolution of the levels get
determined, because the output is not what I (perhaps naively) expect.



Can someone point me to the flash.smooth dataset, so that I can compare
results, and perhaps move forward from a working example? I looked for it
in vtklargedata but it wasn?t there.



Should I expect AMR vthb datasets to work in ParaViewWeb? I?m running
ParaViewWeb 4.4 from a AWS EC2 AMI instance from here:

http://kitware.github.io/paraviewweb/docs/guides/ami.html

And it won?t load my vthb file, even though my supporting files and folders
are there.



 Thanks for all the help!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160419/9f9904f9/attachment.html>

From wascott at sandia.gov  Tue Apr 19 15:53:45 2016
From: wascott at sandia.gov (Scott, W Alan)
Date: Tue, 19 Apr 2016 19:53:45 +0000
Subject: [Paraview] [EXTERNAL] Store defaults for "Save data..." with
 CSV data
In-Reply-To: <7896A855-E629-461A-83B3-1E3A4DA3775A@aia.rwth-aachen.de>
References: <1943FB0A-57D9-4D62-8E4E-ED08A397F763@aia.rwth-aachen.de>
 <cb2d249952d54ad8b244dc25033c604e@ES01AMSNLNT.srn.sandia.gov>
 <7896A855-E629-461A-83B3-1E3A4DA3775A@aia.rwth-aachen.de>
Message-ID: <e54d888e457c4a758c971fb693dda845@ES01AMSNLNT.srn.sandia.gov>

Click on the bug link I gave below.  Then, add your name to the Users monitoring this issue.  You may need to get an account, I don?t know.


From: Schlottke-Lakemper, Michael [mailto:m.schlottke-lakemper at aia.rwth-aachen.de]
Sent: Tuesday, April 19, 2016 11:42 AM
To: Scott, W Alan <wascott at sandia.gov>
Cc: ParaView <paraview at paraview.org>
Subject: Re: [EXTERNAL] [Paraview] Store defaults for "Save data..." with CSV data

Thanks for the quick feedback! Is there a way to track the issue on MantisBT, i.e., to get notified if there are changes to it? Also, I can?t seem to find the https Version of MantisBT (or at least the login page) - is there something I?m missing?

Regards,

Michael

On 19 Apr 2016, at 18:59 , Scott, W Alan <wascott at sandia.gov<mailto:wascott at sandia.gov>> wrote:

This sounds reasonable.  I wrote it up here http://www.paraview.org/Bug/view.php?id=16080.

Alan

From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Schlottke-Lakemper, Michael
Sent: Tuesday, April 19, 2016 2:01 AM
To: ParaView <paraview at paraview.org<mailto:paraview at paraview.org>>
Subject: [EXTERNAL] [Paraview] Store defaults for "Save data..." with CSV data

Hi folks,

Is there a possibility to store the defaults when saving data as CSV (e.g. from the Plot over line filter)? Right now I always have to confirm that data is gathered on a single process before saving and I have to set the precision and scientific notation options manually. Preferably in PV, but if there is a config file I can edit, I?d be happy as well.

Yours

Michael

--
Michael Schlottke-Lakemper

Chair of Fluid Mechanics and Institute of Aerodynamics
RWTH Aachen University
W?llnerstra?e 5a
52062 Aachen
Germany

Phone: +49 (241) 80 95188
Fax: +49 (241) 80 92257
Mail: m.schlottke-lakemper at aia.rwth-aachen.de<mailto:m.schlottke-lakemper at aia.rwth-aachen.de>
Web: http://www.aia.rwth-aachen.de<http://www.aia.rwth-aachen.de/>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160419/52db816b/attachment.html>

From utkarsh.ayachit at kitware.com  Tue Apr 19 17:15:08 2016
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Tue, 19 Apr 2016 17:15:08 -0400
Subject: [Paraview] [EXTERNAL] Store defaults for "Save data..." with
	CSV data
In-Reply-To: <e54d888e457c4a758c971fb693dda845@ES01AMSNLNT.srn.sandia.gov>
References: <1943FB0A-57D9-4D62-8E4E-ED08A397F763@aia.rwth-aachen.de>
 <cb2d249952d54ad8b244dc25033c604e@ES01AMSNLNT.srn.sandia.gov>
 <7896A855-E629-461A-83B3-1E3A4DA3775A@aia.rwth-aachen.de>
 <e54d888e457c4a758c971fb693dda845@ES01AMSNLNT.srn.sandia.gov>
Message-ID: <CADHSJjD_PX6fqUp_4ak0hpd+1hMFoq211M_=TCZNA5DRsU4WmA@mail.gmail.com>

Here's a potential fix:

https://gitlab.kitware.com/paraview/paraview/merge_requests/744

+ Save data dialog now is the same dialog we use other places e.g.
editing scalar bar properties, which allows user to save the chosen
values to "Settings" after clicking the "Apply" button.
+ I have not deleted the "many to one" warning message, but instead
made it possible for the user to say "Yes, and don't ask again" --
similar to other warning messages we show e.g. when switch to "Volume
Rendering". Alan, this is slightly different than your bug report. Let
me know if that's acceptable.

Utkarsh




On Tue, Apr 19, 2016 at 3:53 PM, Scott, W Alan <wascott at sandia.gov> wrote:
> Click on the bug link I gave below.  Then, add your name to the Users
> monitoring this issue.  You may need to get an account, I don?t know.
>
>
>
>
>
> From: Schlottke-Lakemper, Michael
> [mailto:m.schlottke-lakemper at aia.rwth-aachen.de]
> Sent: Tuesday, April 19, 2016 11:42 AM
> To: Scott, W Alan <wascott at sandia.gov>
> Cc: ParaView <paraview at paraview.org>
> Subject: Re: [EXTERNAL] [Paraview] Store defaults for "Save data..." with
> CSV data
>
>
>
> Thanks for the quick feedback! Is there a way to track the issue on
> MantisBT, i.e., to get notified if there are changes to it? Also, I can?t
> seem to find the https Version of MantisBT (or at least the login page) - is
> there something I?m missing?
>
>
>
> Regards,
>
>
>
> Michael
>
>
>
> On 19 Apr 2016, at 18:59 , Scott, W Alan <wascott at sandia.gov> wrote:
>
>
>
> This sounds reasonable.  I wrote it up here
> http://www.paraview.org/Bug/view.php?id=16080.
>
>
>
> Alan
>
>
>
> From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of
> Schlottke-Lakemper, Michael
> Sent: Tuesday, April 19, 2016 2:01 AM
> To: ParaView <paraview at paraview.org>
> Subject: [EXTERNAL] [Paraview] Store defaults for "Save data..." with CSV
> data
>
>
>
> Hi folks,
>
>
>
> Is there a possibility to store the defaults when saving data as CSV (e.g.
> from the Plot over line filter)? Right now I always have to confirm that
> data is gathered on a single process before saving and I have to set the
> precision and scientific notation options manually. Preferably in PV, but if
> there is a config file I can edit, I?d be happy as well.
>
>
>
> Yours
>
>
>
> Michael
>
>
>
> --
> Michael Schlottke-Lakemper
>
> Chair of Fluid Mechanics and Institute of Aerodynamics
> RWTH Aachen University
> W?llnerstra?e 5a
> 52062 Aachen
> Germany
>
> Phone: +49 (241) 80 95188
> Fax: +49 (241) 80 92257
> Mail: m.schlottke-lakemper at aia.rwth-aachen.de
> Web: http://www.aia.rwth-aachen.de
>
>
>
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview
>

From wascott at sandia.gov  Tue Apr 19 17:16:54 2016
From: wascott at sandia.gov (Scott, W Alan)
Date: Tue, 19 Apr 2016 21:16:54 +0000
Subject: [Paraview] [EXTERNAL] Store defaults for "Save data..." with
 CSV data
In-Reply-To: <CADHSJjD_PX6fqUp_4ak0hpd+1hMFoq211M_=TCZNA5DRsU4WmA@mail.gmail.com>
References: <1943FB0A-57D9-4D62-8E4E-ED08A397F763@aia.rwth-aachen.de>
 <cb2d249952d54ad8b244dc25033c604e@ES01AMSNLNT.srn.sandia.gov>
 <7896A855-E629-461A-83B3-1E3A4DA3775A@aia.rwth-aachen.de>
 <e54d888e457c4a758c971fb693dda845@ES01AMSNLNT.srn.sandia.gov>
 <CADHSJjD_PX6fqUp_4ak0hpd+1hMFoq211M_=TCZNA5DRsU4WmA@mail.gmail.com>
Message-ID: <584acb80da7640e5802e726b9f7f9469@ES01AMSNLNT.srn.sandia.gov>

Nice.  I'll test when it hits master.  

Thanks!

Alan

-----Original Message-----
From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] 
Sent: Tuesday, April 19, 2016 3:15 PM
To: Scott, W Alan <wascott at sandia.gov>
Cc: Schlottke-Lakemper, Michael <m.schlottke-lakemper at aia.rwth-aachen.de>; ParaView <paraview at paraview.org>
Subject: Re: [Paraview] [EXTERNAL] Store defaults for "Save data..." with CSV data

Here's a potential fix:

https://gitlab.kitware.com/paraview/paraview/merge_requests/744

+ Save data dialog now is the same dialog we use other places e.g.
editing scalar bar properties, which allows user to save the chosen values to "Settings" after clicking the "Apply" button.
+ I have not deleted the "many to one" warning message, but instead
made it possible for the user to say "Yes, and don't ask again" -- similar to other warning messages we show e.g. when switch to "Volume Rendering". Alan, this is slightly different than your bug report. Let me know if that's acceptable.

Utkarsh




On Tue, Apr 19, 2016 at 3:53 PM, Scott, W Alan <wascott at sandia.gov> wrote:
> Click on the bug link I gave below.  Then, add your name to the Users 
> monitoring this issue.  You may need to get an account, I don?t know.
>
>
>
>
>
> From: Schlottke-Lakemper, Michael
> [mailto:m.schlottke-lakemper at aia.rwth-aachen.de]
> Sent: Tuesday, April 19, 2016 11:42 AM
> To: Scott, W Alan <wascott at sandia.gov>
> Cc: ParaView <paraview at paraview.org>
> Subject: Re: [EXTERNAL] [Paraview] Store defaults for "Save data..." 
> with CSV data
>
>
>
> Thanks for the quick feedback! Is there a way to track the issue on 
> MantisBT, i.e., to get notified if there are changes to it? Also, I 
> can?t seem to find the https Version of MantisBT (or at least the 
> login page) - is there something I?m missing?
>
>
>
> Regards,
>
>
>
> Michael
>
>
>
> On 19 Apr 2016, at 18:59 , Scott, W Alan <wascott at sandia.gov> wrote:
>
>
>
> This sounds reasonable.  I wrote it up here 
> http://www.paraview.org/Bug/view.php?id=16080.
>
>
>
> Alan
>
>
>
> From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of 
> Schlottke-Lakemper, Michael
> Sent: Tuesday, April 19, 2016 2:01 AM
> To: ParaView <paraview at paraview.org>
> Subject: [EXTERNAL] [Paraview] Store defaults for "Save data..." with 
> CSV data
>
>
>
> Hi folks,
>
>
>
> Is there a possibility to store the defaults when saving data as CSV (e.g.
> from the Plot over line filter)? Right now I always have to confirm 
> that data is gathered on a single process before saving and I have to 
> set the precision and scientific notation options manually. Preferably 
> in PV, but if there is a config file I can edit, I?d be happy as well.
>
>
>
> Yours
>
>
>
> Michael
>
>
>
> --
> Michael Schlottke-Lakemper
>
> Chair of Fluid Mechanics and Institute of Aerodynamics RWTH Aachen 
> University W?llnerstra?e 5a
> 52062 Aachen
> Germany
>
> Phone: +49 (241) 80 95188
> Fax: +49 (241) 80 92257
> Mail: m.schlottke-lakemper at aia.rwth-aachen.de
> Web: http://www.aia.rwth-aachen.de
>
>
>
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at 
> http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview
>

From wascott at sandia.gov  Tue Apr 19 19:27:22 2016
From: wascott at sandia.gov (Scott, W Alan)
Date: Tue, 19 Apr 2016 23:27:22 +0000
Subject: [Paraview] [EXTERNAL] Re:  [EXT] Re: v5.0.1 & RealVNC
In-Reply-To: <CADHSJjBYkCzqj78-d_SPo1=k_xa3Vrc__0uqoxk7Cp=B1tFMaw@mail.gmail.com>
References: <CY1PR07MB2506A851C555D9491B6D73279F950@CY1PR07MB2506.namprd07.prod.outlook.com>
 <CAOXZzG6iyK=Vm21eBJRMoipvN7Hs7gDPUw0bA8iPRHKtM=a9og@mail.gmail.com>
 <CY1PR07MB250638B049611478865878C59F960@CY1PR07MB2506.namprd07.prod.outlook.com>
 <CAOXZzG6BcGvWOxAc_UZdDMHWPicTFqYdt+g9iJj=7LM0tPbVgQ@mail.gmail.com>
 <CY1PR07MB25062AA439DD5903F9C65F3A9F960@CY1PR07MB2506.namprd07.prod.outlook.com>
 <CADHSJjBcnC8qydQ_Z++FzvXOp6FKPzm6fg1UhCGSGa42=a324g@mail.gmail.com>
 <aee634acda5c49f2985c5a73a7b8a7bd@ES01AMSNLNT.srn.sandia.gov>
 <CADHSJjBYkCzqj78-d_SPo1=k_xa3Vrc__0uqoxk7Cp=B1tFMaw@mail.gmail.com>
Message-ID: <ccb529f351d74f95af1c68348fc062a8@ES01AMSNLNT.srn.sandia.gov>

Sorry for taking so long to test.  YES, THIS WORKS.  Yay!

I tested six ways:
* Linux, with NVidia graphics ---- worked.
    ./paraview 

* Linux, with NVidia graphics, but using Mesa ---- worked.  I looked in the help/about, and yes - it is software rendered.
    ./paraview --mesa-llvm

* Linux, without NVidia graphics ---- didn't work (as expected)
   Ssh -X sharedCompileServer
    ./paraview 

* Linux, without NVidia graphics ---- worked.   Note this solves everyone's -X problem.
   Ssh -X sharedCompileServer
    ./paraview --mesa-llvm

* Log in node of a cluster, without NVidia graphics ---- didn't work (as expected)
   Ssh -X sharedCompileServer
    ./paraview 

* Login node of a cluster, without NVidia graphics ---- worked.  
   Ssh -X sharedCompileServer
    ./paraview --mesa-llvm


Yes, this would be worth updating the official binaries.

Thanks as always,

Alan

-----Original Message-----
From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] 
Sent: Thursday, April 14, 2016 8:55 AM
To: Scott, W Alan <wascott at sandia.gov>
Cc: Dennis Conklin <dennis_conklin at goodyear.com>; ParaView Mailing List <paraview at paraview.org>
Subject: Re: [EXTERNAL] Re: [Paraview] [EXT] Re: v5.0.1 & RealVNC

Alan,


> ./paraview --mesa-llvm
> .../lib/paraview-5.0/paraview: error while loading shared libraries: libatomic.so.1: cannot open shared object file: No such file or directory

Can you try this binary:
http://www.paraview.org/files/v5.0/ParaView-5.0.1-Qt4-OpenGL2-MPI-Linux-64bit-experimental.tar.gz

If it works, then I can update the official binaries.

Utkarsh

From dennis_conklin at goodyear.com  Wed Apr 20 07:50:17 2016
From: dennis_conklin at goodyear.com (Dennis Conklin)
Date: Wed, 20 Apr 2016 11:50:17 +0000
Subject: [Paraview] [EXTERNAL] Re:  [EXT] Re: v5.0.1 & RealVNC
In-Reply-To: <ccb529f351d74f95af1c68348fc062a8@ES01AMSNLNT.srn.sandia.gov>
References: <CY1PR07MB2506A851C555D9491B6D73279F950@CY1PR07MB2506.namprd07.prod.outlook.com>
 <CAOXZzG6iyK=Vm21eBJRMoipvN7Hs7gDPUw0bA8iPRHKtM=a9og@mail.gmail.com>
 <CY1PR07MB250638B049611478865878C59F960@CY1PR07MB2506.namprd07.prod.outlook.com>
 <CAOXZzG6BcGvWOxAc_UZdDMHWPicTFqYdt+g9iJj=7LM0tPbVgQ@mail.gmail.com>
 <CY1PR07MB25062AA439DD5903F9C65F3A9F960@CY1PR07MB2506.namprd07.prod.outlook.com>
 <CADHSJjBcnC8qydQ_Z++FzvXOp6FKPzm6fg1UhCGSGa42=a324g@mail.gmail.com>
 <aee634acda5c49f2985c5a73a7b8a7bd@ES01AMSNLNT.srn.sandia.gov>
 <CADHSJjBYkCzqj78-d_SPo1=k_xa3Vrc__0uqoxk7Cp=B1tFMaw@mail.gmail.com>
 <ccb529f351d74f95af1c68348fc062a8@ES01AMSNLNT.srn.sandia.gov>
Message-ID: <CY1PR07MB25065B554352AFA7A88EE6FC9F6D0@CY1PR07MB2506.namprd07.prod.outlook.com>

All,

Can you identify what the minimum requirements are to use v5.0.1?

I think I hear OpenGL minimum is 3.2.  Is that correct?

What is the minimum MESA version required?

Are there other minimum requirements so that I can advise the sysadmins?

Thanks

Dennis

-----Original Message-----
From: Scott, W Alan [mailto:wascott at sandia.gov] 
Sent: Tuesday, April 19, 2016 7:27 PM
To: Utkarsh Ayachit <utkarsh.ayachit at kitware.com>
Cc: Dennis Conklin <dennis_conklin at goodyear.com>; ParaView Mailing List <paraview at paraview.org>
Subject: RE: [EXTERNAL] Re: [Paraview] [EXT] Re: v5.0.1 & RealVNC

Sorry for taking so long to test.  YES, THIS WORKS.  Yay!

I tested six ways:
* Linux, with NVidia graphics ---- worked.
    ./paraview 

* Linux, with NVidia graphics, but using Mesa ---- worked.  I looked in the help/about, and yes - it is software rendered.
    ./paraview --mesa-llvm

* Linux, without NVidia graphics ---- didn't work (as expected)
   Ssh -X sharedCompileServer
    ./paraview 

* Linux, without NVidia graphics ---- worked.   Note this solves everyone's -X problem.
   Ssh -X sharedCompileServer
    ./paraview --mesa-llvm

* Log in node of a cluster, without NVidia graphics ---- didn't work (as expected)
   Ssh -X sharedCompileServer
    ./paraview 

* Login node of a cluster, without NVidia graphics ---- worked.  
   Ssh -X sharedCompileServer
    ./paraview --mesa-llvm


Yes, this would be worth updating the official binaries.

Thanks as always,

Alan

-----Original Message-----
From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] 
Sent: Thursday, April 14, 2016 8:55 AM
To: Scott, W Alan <wascott at sandia.gov>
Cc: Dennis Conklin <dennis_conklin at goodyear.com>; ParaView Mailing List <paraview at paraview.org>
Subject: Re: [EXTERNAL] Re: [Paraview] [EXT] Re: v5.0.1 & RealVNC

Alan,


> ./paraview --mesa-llvm
> .../lib/paraview-5.0/paraview: error while loading shared libraries: libatomic.so.1: cannot open shared object file: No such file or directory

Can you try this binary:
http://www.paraview.org/files/v5.0/ParaView-5.0.1-Qt4-OpenGL2-MPI-Linux-64bit-experimental.tar.gz

If it works, then I can update the official binaries.

Utkarsh

From utkarsh.ayachit at kitware.com  Wed Apr 20 08:12:47 2016
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Wed, 20 Apr 2016 08:12:47 -0400
Subject: [Paraview] [EXTERNAL] Re:  [EXT] Re: v5.0.1 & RealVNC
In-Reply-To: <CY1PR07MB25065B554352AFA7A88EE6FC9F6D0@CY1PR07MB2506.namprd07.prod.outlook.com>
References: <CY1PR07MB2506A851C555D9491B6D73279F950@CY1PR07MB2506.namprd07.prod.outlook.com>
 <CAOXZzG6iyK=Vm21eBJRMoipvN7Hs7gDPUw0bA8iPRHKtM=a9og@mail.gmail.com>
 <CY1PR07MB250638B049611478865878C59F960@CY1PR07MB2506.namprd07.prod.outlook.com>
 <CAOXZzG6BcGvWOxAc_UZdDMHWPicTFqYdt+g9iJj=7LM0tPbVgQ@mail.gmail.com>
 <CY1PR07MB25062AA439DD5903F9C65F3A9F960@CY1PR07MB2506.namprd07.prod.outlook.com>
 <CADHSJjBcnC8qydQ_Z++FzvXOp6FKPzm6fg1UhCGSGa42=a324g@mail.gmail.com>
 <aee634acda5c49f2985c5a73a7b8a7bd@ES01AMSNLNT.srn.sandia.gov>
 <CADHSJjBYkCzqj78-d_SPo1=k_xa3Vrc__0uqoxk7Cp=B1tFMaw@mail.gmail.com>
 <ccb529f351d74f95af1c68348fc062a8@ES01AMSNLNT.srn.sandia.gov>
 <CY1PR07MB25065B554352AFA7A88EE6FC9F6D0@CY1PR07MB2506.namprd07.prod.outlook.com>
Message-ID: <CADHSJjAdXTeomh2EQc=0ZyZ59K6zrph=9xiwzfRvLr6Kjp1nhg@mail.gmail.com>

> I think I hear OpenGL minimum is 3.2.  Is that correct?

Yes.

> What is the minimum MESA version required?

10.5.5 or later. However, 11.2 is strongly recommended. 11.2 is
required if using OSMesa support.

From utkarsh.ayachit at kitware.com  Wed Apr 20 12:41:47 2016
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Wed, 20 Apr 2016 12:41:47 -0400
Subject: [Paraview] Error 134 when opening ParaView
In-Reply-To: <5715DEC1.9070706@nice-software.com>
References: <5715DEC1.9070706@nice-software.com>
Message-ID: <CADHSJjBUiwWEX3RjcqzBobrDvX4fux1y6jERyQABHybtvAiNMA@mail.gmail.com>

Not entirely sure what that is. ParaView doesn't really report error
codes. What OS is this on?

On Tue, Apr 19, 2016 at 3:31 AM, Vincent BOSQUIER
<vincent.bosquier at nice-software.com> wrote:
> Hi,
>
> I'm using ParaView v4.4 and I have experienced an error code 134 when
> opening the application.
> Can anyone tell me what this error is about?
> Best regards,
>
> Vincent.
>
> Vincent BOSQUIER
> HPC & Visualization Architect
> NICE Software.
>
> vincent.bosquier at nice-software.com
> Visit NICE at www.nice-software.com
>
>
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview
>

From Sean.Ziegeler at engilitycorp.com  Wed Apr 20 13:13:01 2016
From: Sean.Ziegeler at engilitycorp.com (Sean.Ziegeler at engilitycorp.com)
Date: Wed, 20 Apr 2016 17:13:01 +0000
Subject: [Paraview] Parallel Unstructured Format Recommendations
Message-ID: <FEBA4B4A0B6E9A4FA7967C7D9FE897CF5102CFAC@DAG22.EGL.ENGILITYCORP.COM>

ParaView has improved its readers a lot lately, so I'd love some guidance on which are the best options these days.  I need something that is rather scalable, especially for the simulation.  Our group had initially arrived at XDMF, but the documentation seems to suggest that it doesn't use Parallel HDF5 (that one must use collections of serial HDF5 files instead).  Maybe that is dated?  CGNS seems to support Parallel HDF5 on the sim side; does the PV reader support reading it in parallel?  I'm leaning toward Parallel HDF5 as the underlying container, but I'd consider other alternatives if they are scalable and reasonably portable.

Thanks!
Sean

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160420/07e04a03/attachment.html>

From nnc at lanl.gov  Wed Apr 20 18:13:00 2016
From: nnc at lanl.gov (Carlson, Neil)
Date: Wed, 20 Apr 2016 22:13:00 +0000
Subject: [Paraview] Extracting cells by label
Message-ID: <F15F421EB9392E4E8AB0A84C912AB2B1989604CD@ECS-EXG-P-MB01.win.lanl.gov>

I have a grid (unstructured and not multi-block) and a cell-centered
data field on the grid.  The field has integer values that serve to
group the cells into conceptual blocks: cells with value 1 form block 1,
and so forth.  Is there some filter that can use such data to actually
extract blocks in such a way that paraview can control their loading
individually, like with the multiblock inspector or the ExtractBlock
filter?

Thanks, Neil

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160420/34470a3d/attachment.html>

From wascott at sandia.gov  Wed Apr 20 19:00:41 2016
From: wascott at sandia.gov (Scott, W Alan)
Date: Wed, 20 Apr 2016 23:00:41 +0000
Subject: [Paraview] [EXTERNAL]  Extracting cells by label
In-Reply-To: <F15F421EB9392E4E8AB0A84C912AB2B1989604CD@ECS-EXG-P-MB01.win.lanl.gov>
References: <F15F421EB9392E4E8AB0A84C912AB2B1989604CD@ECS-EXG-P-MB01.win.lanl.gov>
Message-ID: <014c002cb56b4c04b967ebafd1236f15@ES01AMSNLNT.srn.sandia.gov>

You mean like the threshold filter?  Threshold out those blocks you don't want...

Alan

From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Carlson, Neil
Sent: Wednesday, April 20, 2016 4:13 PM
To: paraview at paraview.org
Subject: [EXTERNAL] [Paraview] Extracting cells by label

I have a grid (unstructured and not multi-block) and a cell-centered
data field on the grid.  The field has integer values that serve to
group the cells into conceptual blocks: cells with value 1 form block 1,
and so forth.  Is there some filter that can use such data to actually
extract blocks in such a way that paraview can control their loading
individually, like with the multiblock inspector or the ExtractBlock
filter?

Thanks, Neil
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160420/2084de28/attachment.html>

From wascott at sandia.gov  Wed Apr 20 19:45:47 2016
From: wascott at sandia.gov (Scott, W Alan)
Date: Wed, 20 Apr 2016 23:45:47 +0000
Subject: [Paraview] [EXTERNAL]  Help with Programmable Filters
In-Reply-To: <97e0ddcb82df46b68c52b657acd82990@ES01AMSNLNT.srn.sandia.gov>
References: <97e0ddcb82df46b68c52b657acd82990@ES01AMSNLNT.srn.sandia.gov>
Message-ID: <53110f53757c4d72b6320cafb6853523@ES01AMSNLNT.srn.sandia.gov>

Ping?

-----Original Message-----
From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Scott, W Alan
Sent: Friday, April 15, 2016 3:18 PM
To: paraview at paraview.org
Subject: [EXTERNAL] [Paraview] Help with Programmable Filters

>From a user:



Hi
I'm trying to get started with programmable filters and am having a little trouble putting it together from the material in the paraview user guide. I have a few questions below:

1.       Is there any documentation generally describing the input and output data objects that form the programmable filter API?

a.       I was able to get some basic info on these objects by executing "print dir(inputs[0])" for example in the program. filter window, but if there is documentation somewhere for each of the object types, that would be useful...

2.       It appears that the user guide suggested methods for accessing the data in the input objects (input.Points, input.PointData['Name'], etc) produce vtk data objects of some form. These can be indexed similar to numpy arrays, but seem to behave differently in other cases. For instance, I couldn't figure how to reshape these arrays (numpy.reshape fails as the vtk array objects don't have any shape attribute defined...). Is there any way to get the input data into actual numpy array form? This would be helpful for direct reuse of existing scripts designed to work on numpy arrays...

3.       I was attempting to write a simple script that does some calcs on a block structured input dataset (input comes in as vtkCompositeDataSet) and writes out some reduced data to a table (I chose vtkTable as the output format). Through inspection of the output object, I found that I could add new rows (which appear in paraview as columns...) of data using output.RowData.append(DATA,NAME). However, DATA needs to be some basic python sequence type or numpy array, and the vtk array types created by the input data access methods (input.Points etc...) don't work... So again here, if there is a good way to convert the data held in the vtk array types to numpy array types, that would be useful here...

Thanks,
Jon




Thanks,

Alan
_______________________________________________
Powered by www.kitware.com

Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView

Search the list archives at: http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview

From biddisco at cscs.ch  Thu Apr 21 06:29:51 2016
From: biddisco at cscs.ch (Biddiscombe, John A.)
Date: Thu, 21 Apr 2016 10:29:51 +0000
Subject: [Paraview] peak memory use on remote nodes
In-Reply-To: <50320452A334BD42A5EC72BAD21450993DF0E1CD@MBX210.d.ethz.ch>
References: <50320452A334BD42A5EC72BAD21450993DF0BFA8@MBX210.d.ethz.ch>
 <CANjZAi-nS+tT0EDTz-UMS=6VGNe4F0LewZ-E1mucAcpMgqhpWw@mail.gmail.com>
 <50320452A334BD42A5EC72BAD21450993DF0E1CD@MBX210.d.ethz.ch>
Message-ID: <50320452A334BD42A5EC72BAD21450993DF11A4E@MBX210.d.ethz.ch>

Dave

So it turns out that aprun/alps won?t let me run a script with dstat to monitor the memory use, and using craypat makes the execution take too long (weeks it seems). So I tried importing part of the dstat python into my paraview python

Using this I am able to query memory use on the node and dump it out.

Question :  If I start a background python thread that polls memory like this

#####################
# start a thread that prints mem use
#####################
def dump_memory():
    # do something here ...
    global stop_thread
    line = ''
    for o in stats:
        o.extract()
        line = line + '  ' + o.show()
    print line + dstat.ansi['reset']

    # call f() again in n seconds
    if stop_thread==0:
      threading.Timer(0.5, dump_memory).start()


and set it going at the start of my paraview python pipeline : Will it actually run and collect info whilst the paraview script is executing the rest of the pipeline.

intuition and brief googling tells me that this won?t work.

Can it be done?

JB

From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Biddiscombe, John A.
Sent: 18 April 2016 14:53
To: David E DeMarle
Cc: paraview at paraview.org
Subject: Re: [Paraview] peak memory use on remote nodes

Thanks Dave

A colleague here suggested I put my
aprun pvbatch <blah> into a script and add a ?dtrace? command at the start of the script. This will then dump out a txt file on each node and after the job completes I can grep the info I need.

I?m going to give that a try first as it seems straightforward, but I will revert to your suggestion if I fail and nothing else comes up.

cheers

JB

From: David E DeMarle [mailto:dave.demarle at kitware.com]
Sent: 18 April 2016 14:48
To: Biddiscombe, John A.
Cc: paraview at paraview.org<mailto:paraview at paraview.org>
Subject: Re: [Paraview] peak memory use on remote nodes

Perhaps extend the benchmark to glean /proc/<PID>/status's VmHWM entry on Linux at least. Get the number for t1 and at t2 and subtract to see what the maximum was in between those two times.

Seems the right place to do that is kwsys/SystemInformation.cxx, but you could prototype in the script.
Hope that helps and please post some code. Seems like a very useful thing to have.


David E DeMarle
Kitware, Inc.
R&D Engineer
21 Corporate Drive
Clifton Park, NY 12065-8662
Phone: 518-881-4909

On Mon, Apr 18, 2016 at 2:42 AM, Biddiscombe, John A. <biddisco at cscs.ch<mailto:biddisco at cscs.ch>> wrote:
The python scripting module ?paraview.benchmark? allows one to get the memory use using ?paraview.benchmark.get_memuse? - but I presume this is the memory reported as used by the system at the moment when the function is called.

Does anyone know a way of recording the peak memory use on remote nodes between t1 and t2 - where t1 and t2 are the start and stop of either a function, job or even paraview python script on the remote node?

thanks

JB

--
John Biddiscombe,                        email:biddisco @.at.@ cscs.ch<http://cscs.ch>
http://www.cscs.ch/
CSCS, Swiss National Supercomputing Centre  | Tel:  +41 (91) 610.82.07<tel:%2B41%20%2891%29%20610.82.07>
Via Trevano 131, 6900 Lugano, Switzerland   | Fax:  +41 (91) 610.82.82<tel:%2B41%20%2891%29%20610.82.82>


_______________________________________________
Powered by www.kitware.com<http://www.kitware.com>

Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView

Search the list archives at: http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160421/6922d1cb/attachment.html>

From utkarsh.ayachit at kitware.com  Thu Apr 21 07:57:25 2016
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Thu, 21 Apr 2016 07:57:25 -0400
Subject: [Paraview] Help with Programmable Filters
In-Reply-To: <97e0ddcb82df46b68c52b657acd82990@ES01AMSNLNT.srn.sandia.gov>
References: <97e0ddcb82df46b68c52b657acd82990@ES01AMSNLNT.srn.sandia.gov>
Message-ID: <CADHSJjCKx40uGOzk=w2btMCQ7kJnr6V63KecD9teVC7cN2K=jw@mail.gmail.com>

> 1.       Is there any documentation generally describing the input and output data objects that form the programmable filter API?

Chapter 14 from the ParaView Guide. And the following series of Berk's
blog posts:

https://blog.kitware.com/improved-vtk-numpy-integration/
https://blog.kitware.com/improved-vtk-numpy-integration-part-2/
https://blog.kitware.com/improved-vtk-numpy-integration-part-3/
https://blog.kitware.com/mpi4py-and-vtk/
https://blog.kitware.com/improved-vtk-numpy-integration-part-4/
https://blog.kitware.com/improved-vtk-numpy-integration-part-5/

> 2.       It appears that the user guide suggested methods for accessing the data in the input objects (input.Points, input.PointData['Name'], etc) produce vtk data objects of some form. These can be indexed similar to numpy arrays, but seem to behave differently in other cases. For instance, I couldn't figure how to reshape these arrays (numpy.reshape fails as the vtk array objects don't have any shape attribute defined...). Is there any way to get the input data into actual numpy array form? This would be helpful for direct reuse of existing scripts designed to work on numpy arrays...

inputs[0].PointData["Name"] is indeed a numpy array for all intents
and purposes. For simple datasets, you can indeed pass these arrays to
numpy functions. Things get a little tricky when dealing with
composite datasets, as described in the references mentioned earlier.

> 3.       I was attempting to write a simple script that does some calcs on a block structured input dataset (input comes in as vtkCompositeDataSet) and writes out some reduced data to a table (I chose vtkTable as the output format). Through inspection of the output object, I found that I could add new rows (which appear in paraview as columns...) of data using output.RowData.append(DATA,NAME). However, DATA needs to be some basic python sequence type or numpy array, and the vtk array types created by the input data access methods (input.Points etc...) don't work... So again here, if there is a good way to convert the data held in the vtk array types to numpy array types, that would be useful here...

If you have an example to demonstrate this issue, that'd be great. In
theory, this is all doable. Chapter 13 in the ParaVIew Guide covers a
few recipies including reading  a CSV file in numpy (hence as numpy
arrays) and pass that out as vtkTable (Section 13.2.1). That sounds
like a good example that could be modified to do what you're trying to
do here.

From vincent.bosquier at nice-software.com  Thu Apr 21 08:09:12 2016
From: vincent.bosquier at nice-software.com (Vincent BOSQUIER)
Date: Thu, 21 Apr 2016 14:09:12 +0200
Subject: [Paraview] Error 134 when opening ParaView
In-Reply-To: <CADHSJjBUiwWEX3RjcqzBobrDvX4fux1y6jERyQABHybtvAiNMA@mail.gmail.com>
References: <5715DEC1.9070706@nice-software.com>
 <CADHSJjBUiwWEX3RjcqzBobrDvX4fux1y6jERyQABHybtvAiNMA@mail.gmail.com>
Message-ID: <5718C2E8.2030506@nice-software.com>

Hi,

My problem appeared on a CentOS 6.7 used through a remote visualisation 
session.
Now that I've fixed some window manager issues, the problem does not 
occur anymore.
But to really understand the problem that I had, I need to know better 
about this ERROR CODE 134 that ParaView was returning.
Best regards,

Vincent.

*Vincent BOSQUIER
*NICE Software.


Le 20/04/2016 18:41, Utkarsh Ayachit a ?crit :
> Not entirely sure what that is. ParaView doesn't really report error
> codes. What OS is this on?
>
> On Tue, Apr 19, 2016 at 3:31 AM, Vincent BOSQUIER
> <vincent.bosquier at nice-software.com> wrote:
>> Hi,
>>
>> I'm using ParaView v4.4 and I have experienced an error code 134 when
>> opening the application.
>> Can anyone tell me what this error is about?
>> Best regards,
>>
>> Vincent.
>>
>> Vincent BOSQUIER
>> HPC & Visualization Architect
>> NICE Software.
>>
>> vincent.bosquier at nice-software.com
>> Visit NICE at www.nice-software.com
>>
>>
>>
>> _______________________________________________
>> Powered by www.kitware.com
>>
>> Visit other Kitware open-source projects at
>> http://www.kitware.com/opensource/opensource.html
>>
>> Please keep messages on-topic and check the ParaView Wiki at:
>> http://paraview.org/Wiki/ParaView
>>
>> Search the list archives at: http://markmail.org/search/?q=ParaView
>>
>> Follow this link to subscribe/unsubscribe:
>> http://public.kitware.com/mailman/listinfo/paraview
>>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160421/54c2d36f/attachment.html>

From chuck.atkins at kitware.com  Thu Apr 21 09:40:36 2016
From: chuck.atkins at kitware.com (Chuck Atkins)
Date: Thu, 21 Apr 2016 09:40:36 -0400
Subject: [Paraview] Error 134 when opening ParaView
In-Reply-To: <5718C2E8.2030506@nice-software.com>
References: <5715DEC1.9070706@nice-software.com>
 <CADHSJjBUiwWEX3RjcqzBobrDvX4fux1y6jERyQABHybtvAiNMA@mail.gmail.com>
 <5718C2E8.2030506@nice-software.com>
Message-ID: <CAOXZzG5UruyYm=v3AEA8jKbHPJ+WJy_FgPzetjSZvo5CQ28obg@mail.gmail.com>

Hi Vincent,

"ERROR CODE 134" is a generic abort code and doesn't really convey anything
specific.  It's essentially the operating system saying "the program
crashed" with no further detail.  To try to diagnose it further, you said
"My problem appeared on a CentOS 6.7 used through a remote visualisation
session".  Can you explain in more detail?  i.e:

   - What OS is the local machine running?
   - What OS is the remote machine running?
      - Are they both Linux, or is this a Windows workstation connection to
      a Linux server or a Linux workstation connecting to a Windows
server, etc.?
      - How is the "remote visualization" connection established?
      - Is this being done through VNC, ssh X11 forwarding, Windows Remote
      Desktop, local ParaView client and remove pvserver, etc.?
   - Are you using the 4.4 binaries from the ParaView download site or did
   you or somebody else build it themselves from source?


- Chuck

- Chuck

On Thu, Apr 21, 2016 at 8:09 AM, Vincent BOSQUIER <
vincent.bosquier at nice-software.com> wrote:

> Hi,
>
> My problem appeared on a CentOS 6.7 used through a remote visualisation
> session.
> Now that I've fixed some window manager issues, the problem does not occur
> anymore.
> But to really understand the problem that I had, I need to know better
> about this ERROR CODE 134 that ParaView was returning.
> Best regards,
>
> Vincent.
>
>
> *Vincent BOSQUIER *NICE Software.
>
>
> Le 20/04/2016 18:41, Utkarsh Ayachit a ?crit :
>
> Not entirely sure what that is. ParaView doesn't really report error
> codes. What OS is this on?
>
> On Tue, Apr 19, 2016 at 3:31 AM, Vincent BOSQUIER<vincent.bosquier at nice-software.com> <vincent.bosquier at nice-software.com> wrote:
>
> Hi,
>
> I'm using ParaView v4.4 and I have experienced an error code 134 when
> opening the application.
> Can anyone tell me what this error is about?
> Best regards,
>
> Vincent.
>
> Vincent BOSQUIER
> HPC & Visualization Architect
> NICE Software.
> vincent.bosquier at nice-software.com
> Visit NICE at www.nice-software.com
>
>
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects athttp://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:http://public.kitware.com/mailman/listinfo/paraview
>
>
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160421/460a9a55/attachment.html>

From nnc at lanl.gov  Thu Apr 21 10:17:19 2016
From: nnc at lanl.gov (Carlson, Neil)
Date: Thu, 21 Apr 2016 14:17:19 +0000
Subject: [Paraview] Which xdmf reader?
Message-ID: <F15F421EB9392E4E8AB0A84C912AB2B198961557@ECS-EXG-P-MB01.win.lanl.gov>

I'm using the pre-built 5.0.0 (64-bit Linux), and when I load
an XDMF file I'm presented with a choice of readers:
  Xdmf3 Reader
  Xdmf3 Reader (Top Level Partition)
  Xdmf Reader
What  is the difference between these?  I'm seeing different behaviour
from each on a silly toy grid consisting of a single quadrilateral element.

Thanks, Neil
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160421/266e7738/attachment.html>

From mgammar at outlook.fr  Thu Apr 21 10:20:24 2016
From: mgammar at outlook.fr (Marwen Gammar)
Date: Thu, 21 Apr 2016 16:20:24 +0200
Subject: [Paraview] 3d text problem
Message-ID: <BAY182-W384D3857734A4ED30B5862D16E0@phx.gbl>

Hello Miss, Mister,I am beginning in the utilisation of the software Paraview and have some problem with its use:I want to use the 3d text on the surface but it is inverted, moreover i don't know how to write it directly on the programm (vtk),and what does this means?:POINT_DATA 8SCALARS sample_scalars float 1LOOKUP_TABLE my_table0.01.02.03.04.05.06.07.0LOOKUP_TABLE my_table 80.0 0.0 0.0 1.01.0 0.0 0.0 1.00.0 1.0 0.0 1.01.0 1.0 0.0 1.00.0 0.0 1.0 1.01.0 0.0 1.0 1.00.0 1.0 1.0 1.01.0 1.0 1.0 1.0Could you please indicate me how to solve those problems?Thank you kindly for your answer,Kind regards,Marwen 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160421/587452bf/attachment.html>

From nnc at lanl.gov  Thu Apr 21 11:01:24 2016
From: nnc at lanl.gov (Carlson, Neil)
Date: Thu, 21 Apr 2016 15:01:24 +0000
Subject: [Paraview] [EXTERNAL]  Extracting cells by label
In-Reply-To: <014c002cb56b4c04b967ebafd1236f15@ES01AMSNLNT.srn.sandia.gov>
References: <F15F421EB9392E4E8AB0A84C912AB2B1989604CD@ECS-EXG-P-MB01.win.lanl.gov>,
 <014c002cb56b4c04b967ebafd1236f15@ES01AMSNLNT.srn.sandia.gov>
Message-ID: <F15F421EB9392E4E8AB0A84C912AB2B19896159A@ECS-EXG-P-MB01.win.lanl.gov>

Sort of, but not exactly.  Threshold would allow me to remove
blocks below a min value and above a max value.  But what I
want is to be able to select (via a checkbox list, for example)
exactly which blocks I want to see, not limited to those in a
range.  And to reiterate, "block n" consists of all cells with
value n in a cell-centered data field.

________________________________
From: Scott, W Alan [wascott at sandia.gov]
Sent: Wednesday, April 20, 2016 5:00 PM
To: Carlson, Neil; paraview at paraview.org
Subject: RE: [EXTERNAL] [Paraview] Extracting cells by label

You mean like the threshold filter?  Threshold out those blocks you don?t want?

Alan

From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Carlson, Neil
Sent: Wednesday, April 20, 2016 4:13 PM
To: paraview at paraview.org
Subject: [EXTERNAL] [Paraview] Extracting cells by label

I have a grid (unstructured and not multi-block) and a cell-centered
data field on the grid.  The field has integer values that serve to
group the cells into conceptual blocks: cells with value 1 form block 1,
and so forth.  Is there some filter that can use such data to actually
extract blocks in such a way that paraview can control their loading
individually, like with the multiblock inspector or the ExtractBlock
filter?

Thanks, Neil
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160421/1743ad52/attachment.html>

From kmorel at sandia.gov  Thu Apr 21 11:07:31 2016
From: kmorel at sandia.gov (Moreland, Kenneth)
Date: Thu, 21 Apr 2016 15:07:31 +0000
Subject: [Paraview] [EXTERNAL]  Extracting cells by label
In-Reply-To: <F15F421EB9392E4E8AB0A84C912AB2B19896159A@ECS-EXG-P-MB01.win.lanl.gov>
References: <F15F421EB9392E4E8AB0A84C912AB2B1989604CD@ECS-EXG-P-MB01.win.lanl.gov>
 <014c002cb56b4c04b967ebafd1236f15@ES01AMSNLNT.srn.sandia.gov>
 <F15F421EB9392E4E8AB0A84C912AB2B19896159A@ECS-EXG-P-MB01.win.lanl.gov>
Message-ID: <075EABDF-8B5D-40A2-81AC-56652573EB5B@sandia.gov>

Neil,

You can do it with the ?Find Data? selection mechanism (Section 6.3 of the ParaView Guide). Open the Find Data dialog and make a selection of where the block id field ?is one of? a comma separated list of block ids you want. When you run the selection query, you should see the cells of those blocks outlined. Then hit the extract selection button that will add a threshold-like filter that will extract those selected blocks.

-Ken

From: ParaView <paraview-bounces at paraview.org> on behalf of "Carlson, Neil" <nnc at lanl.gov>
Date: Thursday, April 21, 2016 at 9:01 AM
To: Walter Scott <wascott at sandia.gov>, "paraview at paraview.org" <paraview at paraview.org>
Subject: Re: [Paraview] [EXTERNAL] Extracting cells by label

Sort of, but not exactly.  Threshold would allow me to remove
blocks below a min value and above a max value.  But what I
want is to be able to select (via a checkbox list, for example)
exactly which blocks I want to see, not limited to those in a
range.  And to reiterate, "block n" consists of all cells with
value n in a cell-centered data field.
________________________________
From: Scott, W Alan [wascott at sandia.gov]
Sent: Wednesday, April 20, 2016 5:00 PM
To: Carlson, Neil; paraview at paraview.org
Subject: RE: [EXTERNAL] [Paraview] Extracting cells by label
You mean like the threshold filter?  Threshold out those blocks you don?t want?

Alan

From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Carlson, Neil
Sent: Wednesday, April 20, 2016 4:13 PM
To: paraview at paraview.org
Subject: [EXTERNAL] [Paraview] Extracting cells by label

I have a grid (unstructured and not multi-block) and a cell-centered
data field on the grid.  The field has integer values that serve to
group the cells into conceptual blocks: cells with value 1 form block 1,
and so forth.  Is there some filter that can use such data to actually
extract blocks in such a way that paraview can control their loading
individually, like with the multiblock inspector or the ExtractBlock
filter?

Thanks, Neil
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160421/dd3d3fd8/attachment.html>

From jason.fleming at seahorsecoastal.com  Thu Apr 21 11:16:07 2016
From: jason.fleming at seahorsecoastal.com (Jason Fleming)
Date: Thu, 21 Apr 2016 11:16:07 -0400
Subject: [Paraview] [EXTERNAL] Extracting cells by label
In-Reply-To: <F15F421EB9392E4E8AB0A84C912AB2B19896159A@ECS-EXG-P-MB01.win.lanl.gov>
References: <F15F421EB9392E4E8AB0A84C912AB2B1989604CD@ECS-EXG-P-MB01.win.lanl.gov>
 <014c002cb56b4c04b967ebafd1236f15@ES01AMSNLNT.srn.sandia.gov>
 <F15F421EB9392E4E8AB0A84C912AB2B19896159A@ECS-EXG-P-MB01.win.lanl.gov>
Message-ID: <CAGOSZgRsr+q9hcnx4y0J0P061GjCeic17Qe=0bjonWjggT8vbQ@mail.gmail.com>

What about checking the box in the color map editor labelled "Interpret
Values as Categories" and then coloring only the category of interest?

Cheers
Jason

On Thu, Apr 21, 2016 at 11:01 AM, Carlson, Neil <nnc at lanl.gov> wrote:

> Sort of, but not exactly.  Threshold would allow me to remove
> blocks below a min value and above a max value.  But what I
> want is to be able to select (via a checkbox list, for example)
> exactly which blocks I want to see, not limited to those in a
> range.  And to reiterate, "block n" consists of all cells with
> value n in a cell-centered data field.
>
> ------------------------------
> *From:* Scott, W Alan [wascott at sandia.gov]
> *Sent:* Wednesday, April 20, 2016 5:00 PM
> *To:* Carlson, Neil; paraview at paraview.org
> *Subject:* RE: [EXTERNAL] [Paraview] Extracting cells by label
>
> You mean like the threshold filter?  Threshold out those blocks you don?t
> want?
>
>
>
> Alan
>
>
>
> *From:* ParaView [mailto:paraview-bounces at paraview.org] *On Behalf Of *Carlson,
> Neil
> *Sent:* Wednesday, April 20, 2016 4:13 PM
> *To:* paraview at paraview.org
> *Subject:* [EXTERNAL] [Paraview] Extracting cells by label
>
>
>
> I have a grid (unstructured and not multi-block) and a cell-centered
> data field on the grid.  The field has integer values that serve to
> group the cells into conceptual blocks: cells with value 1 form block 1,
> and so forth.  Is there some filter that can use such data to actually
> extract blocks in such a way that paraview can control their loading
> individually, like with the multiblock inspector or the ExtractBlock
> filter?
>
> Thanks, Neil
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview
>
>


-- 
Dr. Jason G. Fleming
Chief Engineer, Seahorse Coastal Consulting
3103 Mandy Ln
Morehead City, NC 28557
Tel: (252) 726-6323
Mobile: (252) 269-0962
Web: http://www.seahorsecoastal.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160421/3b87e2c6/attachment.html>

From kmorel at sandia.gov  Thu Apr 21 11:25:01 2016
From: kmorel at sandia.gov (Moreland, Kenneth)
Date: Thu, 21 Apr 2016 15:25:01 +0000
Subject: [Paraview] 3d text problem
Message-ID: <B3192C82-1C40-4A19-B4AF-7E98B9DB72F7@sandia.gov>

Marwen,

You asked 3 questions. I will try to answer them.

?I want to use the 3d text on the surface but it is inverted.? It sounds like you are looking at your text from the back. Try moving the camera around to the front. You can also click the toolbar button marked ?-Z? (2nd row near the right). That should place the camera where the text is forward.

?moreover I don?t know how to write it directly on the program? In the properties panel there is an editable box labeled ?Text?. Change that and then hit the ?Apply? button to change the text.

?what does this mean?? That definitely looks like part of a data file in what is called the legacy VTK format. However, a large part of the file is missing, so that data will not load correctly.

-Ken

From: ParaView <paraview-bounces at paraview.org> on behalf of Marwen Gammar <mgammar at outlook.fr>
Date: Thursday, April 21, 2016 at 8:20 AM
To: "paraview at paraview.org" <paraview at paraview.org>
Subject: [EXTERNAL] [Paraview] 3d text problem

Hello Miss, Mister,
I am beginning in the utilisation of the software Paraview and have some problem with its use:
I want to use the 3d text on the surface but it is inverted,
moreover i don't know how to write it directly on the programm (vtk),
and what does this means?:
POINT_DATA 8
SCALARS sample_scalars float 1
LOOKUP_TABLE my_table
0.0
1.0
2.0
3.0
4.0
5.0
6.0
7.0
LOOKUP_TABLE my_table 8
0.0 0.0 0.0 1.0
1.0 0.0 0.0 1.0
0.0 1.0 0.0 1.0
1.0 1.0 0.0 1.0
0.0 0.0 1.0 1.0
1.0 0.0 1.0 1.0
0.0 1.0 1.0 1.0
1.0 1.0 1.0 1.0

Could you please indicate me how to solve those problems?

Thank you kindly for your answer,
Kind regards,
Marwen
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160421/f5372e1f/attachment.html>

From wascott at sandia.gov  Thu Apr 21 13:04:02 2016
From: wascott at sandia.gov (Scott, W Alan)
Date: Thu, 21 Apr 2016 17:04:02 +0000
Subject: [Paraview] [EXTERNAL] Re:  3d text problem
In-Reply-To: <B3192C82-1C40-4A19-B4AF-7E98B9DB72F7@sandia.gov>
References: <B3192C82-1C40-4A19-B4AF-7E98B9DB72F7@sandia.gov>
Message-ID: <20289564a6e74fd683ffcfc3673727df@ES01AMSNLNT.srn.sandia.gov>

Regarding Ken?s third answer, here is a document on VTK file formats.  It is old, but I believe still up to date.

http://www.vtk.org/wp-content/uploads/2015/04/file-formats.pdf

Alan

From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Moreland, Kenneth
Sent: Thursday, April 21, 2016 9:25 AM
To: Marwen Gammar <mgammar at outlook.fr>; paraview at paraview.org
Subject: [EXTERNAL] Re: [Paraview] 3d text problem

Marwen,

You asked 3 questions. I will try to answer them.

?I want to use the 3d text on the surface but it is inverted.? It sounds like you are looking at your text from the back. Try moving the camera around to the front. You can also click the toolbar button marked ?-Z? (2nd row near the right). That should place the camera where the text is forward.

?moreover I don?t know how to write it directly on the program? In the properties panel there is an editable box labeled ?Text?. Change that and then hit the ?Apply? button to change the text.

?what does this mean?? That definitely looks like part of a data file in what is called the legacy VTK format. However, a large part of the file is missing, so that data will not load correctly.

-Ken

From: ParaView <paraview-bounces at paraview.org<mailto:paraview-bounces at paraview.org>> on behalf of Marwen Gammar <mgammar at outlook.fr<mailto:mgammar at outlook.fr>>
Date: Thursday, April 21, 2016 at 8:20 AM
To: "paraview at paraview.org<mailto:paraview at paraview.org>" <paraview at paraview.org<mailto:paraview at paraview.org>>
Subject: [EXTERNAL] [Paraview] 3d text problem

Hello Miss, Mister,
I am beginning in the utilisation of the software Paraview and have some problem with its use:
I want to use the 3d text on the surface but it is inverted,
moreover i don't know how to write it directly on the programm (vtk),
and what does this means?:
POINT_DATA 8
SCALARS sample_scalars float 1
LOOKUP_TABLE my_table
0.0
1.0
2.0
3.0
4.0
5.0
6.0
7.0
LOOKUP_TABLE my_table 8
0.0 0.0 0.0 1.0
1.0 0.0 0.0 1.0
0.0 1.0 0.0 1.0
1.0 1.0 0.0 1.0
0.0 0.0 1.0 1.0
1.0 0.0 1.0 1.0
0.0 1.0 1.0 1.0
1.0 1.0 1.0 1.0

Could you please indicate me how to solve those problems?

Thank you kindly for your answer,
Kind regards,
Marwen
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160421/dbca5ed1/attachment.html>

From wascott at sandia.gov  Thu Apr 21 13:14:15 2016
From: wascott at sandia.gov (Scott, W Alan)
Date: Thu, 21 Apr 2016 17:14:15 +0000
Subject: [Paraview] [EXTERNAL] Re:  Help with Programmable Filters
In-Reply-To: <CADHSJjCKx40uGOzk=w2btMCQ7kJnr6V63KecD9teVC7cN2K=jw@mail.gmail.com>
References: <97e0ddcb82df46b68c52b657acd82990@ES01AMSNLNT.srn.sandia.gov>
 <CADHSJjCKx40uGOzk=w2btMCQ7kJnr6V63KecD9teVC7cN2K=jw@mail.gmail.com>
Message-ID: <e7fc47e367934b0db37ebc6e809f185a@ES01AMSNLNT.srn.sandia.gov>

Very nice.  I didn't know these existed.  Here is another question from my user:  Is there some detailed documentation (beyond whats in the paraview guide) for the programmable filter API?

Thanks,

Alan

-----Original Message-----
From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] 
Sent: Thursday, April 21, 2016 5:57 AM
To: Scott, W Alan <wascott at sandia.gov>
Cc: paraview at paraview.org
Subject: [EXTERNAL] Re: [Paraview] Help with Programmable Filters

> 1.       Is there any documentation generally describing the input and output data objects that form the programmable filter API?

Chapter 14 from the ParaView Guide. And the following series of Berk's blog posts:

https://blog.kitware.com/improved-vtk-numpy-integration/
https://blog.kitware.com/improved-vtk-numpy-integration-part-2/
https://blog.kitware.com/improved-vtk-numpy-integration-part-3/
https://blog.kitware.com/mpi4py-and-vtk/
https://blog.kitware.com/improved-vtk-numpy-integration-part-4/
https://blog.kitware.com/improved-vtk-numpy-integration-part-5/

> 2.       It appears that the user guide suggested methods for accessing the data in the input objects (input.Points, input.PointData['Name'], etc) produce vtk data objects of some form. These can be indexed similar to numpy arrays, but seem to behave differently in other cases. For instance, I couldn't figure how to reshape these arrays (numpy.reshape fails as the vtk array objects don't have any shape attribute defined...). Is there any way to get the input data into actual numpy array form? This would be helpful for direct reuse of existing scripts designed to work on numpy arrays...

inputs[0].PointData["Name"] is indeed a numpy array for all intents and purposes. For simple datasets, you can indeed pass these arrays to numpy functions. Things get a little tricky when dealing with composite datasets, as described in the references mentioned earlier.

> 3.       I was attempting to write a simple script that does some calcs on a block structured input dataset (input comes in as vtkCompositeDataSet) and writes out some reduced data to a table (I chose vtkTable as the output format). Through inspection of the output object, I found that I could add new rows (which appear in paraview as columns...) of data using output.RowData.append(DATA,NAME). However, DATA needs to be some basic python sequence type or numpy array, and the vtk array types created by the input data access methods (input.Points etc...) don't work... So again here, if there is a good way to convert the data held in the vtk array types to numpy array types, that would be useful here...

If you have an example to demonstrate this issue, that'd be great. In theory, this is all doable. Chapter 13 in the ParaVIew Guide covers a few recipies including reading  a CSV file in numpy (hence as numpy
arrays) and pass that out as vtkTable (Section 13.2.1). That sounds like a good example that could be modified to do what you're trying to do here.

From utkarsh.ayachit at kitware.com  Thu Apr 21 13:16:30 2016
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Thu, 21 Apr 2016 13:16:30 -0400
Subject: [Paraview] [EXTERNAL] Re:  Help with Programmable Filters
In-Reply-To: <e7fc47e367934b0db37ebc6e809f185a@ES01AMSNLNT.srn.sandia.gov>
References: <97e0ddcb82df46b68c52b657acd82990@ES01AMSNLNT.srn.sandia.gov>
 <CADHSJjCKx40uGOzk=w2btMCQ7kJnr6V63KecD9teVC7cN2K=jw@mail.gmail.com>
 <e7fc47e367934b0db37ebc6e809f185a@ES01AMSNLNT.srn.sandia.gov>
Message-ID: <CADHSJjDAE6BDZmcgCniJBfzJsRKo64K2VY+q+6j7TF8u+cM6+w@mail.gmail.com>

> Very nice.  I didn't know these existed.  Here is another question from my user:  Is there some detailed documentation (beyond whats in the paraview guide) for the programmable filter API?

Alas, no. If you have a list of things that are not covered that your
user would like described, we can extend the guide to include that.

From manu.gvm at gmail.com  Thu Apr 21 13:28:46 2016
From: manu.gvm at gmail.com (Manu V G)
Date: Thu, 21 Apr 2016 19:28:46 +0200
Subject: [Paraview] Coordinate system transformation
Message-ID: <CACNtz3iixwJNTAG4spHW+-5N-R+OnyhecxqO60xw9rW9jdwTuA@mail.gmail.com>

Hello everyone!

Is it possible to create new local coordinate system (x1,y1,z1) and compute
velocities in that (in short coordinate transformation) from the original
system (x,y,z)? Google search did not help me much. And 'Transform' filter
do not transform velocities to the new coordinate system (is a geometrical
transformation).

Problem in detail :

I read a 3D velocity field in Paraview and compute orthogonal eigenvectors
(x1,y1,z1) at a certain point 'O1' using 'Programmable Filter'. These
eigenvectors (x1,y1,z1) act as basis for the new coordinate system with
origin 'O1'. I am trying and just want to visualize velocity in plane z1=0.
For this, I need to transform velocity field from original system to new
coordinate system (x1,y1,z1). And I am trying solve it in the following
way. Maybe there is simple way to do it Paraview.

>From eigenvectors, I can specify the plane (z1=0) by using a 'Slice'
filter. The velocities in that plane correspond to the global velocity
(u,v,w) in (x,y,z) coordinate system. Then, I use transformation matrix to
compute new velocity vector (u1,v1,w1) using 'Calculator' or 'Python
Calculation'. However, those velocities correspond to (x1,y1,z1) coordinate
system. So, is there a way to associate these newly computed velocities to
a new coordinate system and plot them?

Or is there a different way to do it Paraview?

I would be very thankful for your suggestions and inputs.


Thanks in advance, yours
-- 
Manu V Goudar
Lab of Aero & Hydrodynamics,
Delft University of Technology
Delft, The Netherlands
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160421/c7096bc4/attachment.html>

From wascott at sandia.gov  Thu Apr 21 15:43:01 2016
From: wascott at sandia.gov (Scott, W Alan)
Date: Thu, 21 Apr 2016 19:43:01 +0000
Subject: [Paraview] [EXTERNAL] Re:  Help with Programmable Filters
In-Reply-To: <CADHSJjCKx40uGOzk=w2btMCQ7kJnr6V63KecD9teVC7cN2K=jw@mail.gmail.com>
References: <97e0ddcb82df46b68c52b657acd82990@ES01AMSNLNT.srn.sandia.gov>
 <CADHSJjCKx40uGOzk=w2btMCQ7kJnr6V63KecD9teVC7cN2K=jw@mail.gmail.com>
Message-ID: <9bdb23e16bb74701a58c33acbee5ef0a@ES01AMSNLNT.srn.sandia.gov>

By the way, I added your references into the Python Calculator and Programmable Filter tutorials.  

Thanks

Alan

-----Original Message-----
From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] 
Sent: Thursday, April 21, 2016 5:57 AM
To: Scott, W Alan <wascott at sandia.gov>
Cc: paraview at paraview.org
Subject: [EXTERNAL] Re: [Paraview] Help with Programmable Filters

> 1.       Is there any documentation generally describing the input and output data objects that form the programmable filter API?

Chapter 14 from the ParaView Guide. And the following series of Berk's blog posts:

https://blog.kitware.com/improved-vtk-numpy-integration/
https://blog.kitware.com/improved-vtk-numpy-integration-part-2/
https://blog.kitware.com/improved-vtk-numpy-integration-part-3/
https://blog.kitware.com/mpi4py-and-vtk/
https://blog.kitware.com/improved-vtk-numpy-integration-part-4/
https://blog.kitware.com/improved-vtk-numpy-integration-part-5/

> 2.       It appears that the user guide suggested methods for accessing the data in the input objects (input.Points, input.PointData['Name'], etc) produce vtk data objects of some form. These can be indexed similar to numpy arrays, but seem to behave differently in other cases. For instance, I couldn't figure how to reshape these arrays (numpy.reshape fails as the vtk array objects don't have any shape attribute defined...). Is there any way to get the input data into actual numpy array form? This would be helpful for direct reuse of existing scripts designed to work on numpy arrays...

inputs[0].PointData["Name"] is indeed a numpy array for all intents and purposes. For simple datasets, you can indeed pass these arrays to numpy functions. Things get a little tricky when dealing with composite datasets, as described in the references mentioned earlier.

> 3.       I was attempting to write a simple script that does some calcs on a block structured input dataset (input comes in as vtkCompositeDataSet) and writes out some reduced data to a table (I chose vtkTable as the output format). Through inspection of the output object, I found that I could add new rows (which appear in paraview as columns...) of data using output.RowData.append(DATA,NAME). However, DATA needs to be some basic python sequence type or numpy array, and the vtk array types created by the input data access methods (input.Points etc...) don't work... So again here, if there is a good way to convert the data held in the vtk array types to numpy array types, that would be useful here...

If you have an example to demonstrate this issue, that'd be great. In theory, this is all doable. Chapter 13 in the ParaVIew Guide covers a few recipies including reading  a CSV file in numpy (hence as numpy
arrays) and pass that out as vtkTable (Section 13.2.1). That sounds like a good example that could be modified to do what you're trying to do here.

From kmorel at sandia.gov  Thu Apr 21 15:56:45 2016
From: kmorel at sandia.gov (Moreland, Kenneth)
Date: Thu, 21 Apr 2016 19:56:45 +0000
Subject: [Paraview] [EXTERNAL]  Coordinate system transformation
In-Reply-To: <CACNtz3iixwJNTAG4spHW+-5N-R+OnyhecxqO60xw9rW9jdwTuA@mail.gmail.com>
References: <CACNtz3iixwJNTAG4spHW+-5N-R+OnyhecxqO60xw9rW9jdwTuA@mail.gmail.com>
Message-ID: <06A80853-0EBE-46F0-B88A-DE44B4406505@sandia.gov>

Maybe somebody else understands better, but I am totally confused by what you are asking. It sounds like you have an original coordinate system x,y,z and a new coordinate system x1,y1,z1. Then you have a velocity vector u,v,w defined in the original coordinate system (x,y,z) that you want to transform to the new coordinate system (x1,y1,z1). This should be straightforward in either Calculator or Python Calculator or Programmable Filter. In fact, it sounds like you are already doing that. When you say, ?however, those velocities correspond to (x1,y1,z1) coordinate system,? I assume that means that you have already done this transformation. What do you mean by ?associate these? velocities to a new coordinate system?? You just have associated them with the new coordinate system.

-Ken


From: ParaView <paraview-bounces at paraview.org> on behalf of Manu V G <manu.gvm at gmail.com>
Date: Thursday, April 21, 2016 at 11:28 AM
To: "paraview at paraview.org" <paraview at paraview.org>
Subject: [EXTERNAL] [Paraview] Coordinate system transformation

Hello everyone!
Is it possible to create new local coordinate system (x1,y1,z1) and compute velocities in that (in short coordinate transformation) from the original system (x,y,z)? Google search did not help me much. And 'Transform' filter do not transform velocities to the new coordinate system (is a geometrical transformation).
Problem in detail :
I read a 3D velocity field in Paraview and compute orthogonal eigenvectors (x1,y1,z1) at a certain point 'O1' using 'Programmable Filter'. These eigenvectors (x1,y1,z1) act as basis for the new coordinate system with origin 'O1'. I am trying and just want to visualize velocity in plane z1=0. For this, I need to transform velocity field from original system to new coordinate system (x1,y1,z1). And I am trying solve it in the following way. Maybe there is simple way to do it Paraview.

From eigenvectors, I can specify the plane (z1=0) by using a 'Slice' filter. The velocities in that plane correspond to the global velocity (u,v,w) in (x,y,z) coordinate system. Then, I use transformation matrix to compute new velocity vector (u1,v1,w1) using 'Calculator' or 'Python Calculation'. However, those velocities correspond to (x1,y1,z1) coordinate system. So, is there a way to associate these newly computed velocities to a new coordinate system and plot them?
Or is there a different way to do it Paraview?

I would be very thankful for your suggestions and inputs.


Thanks in advance, yours
--
Manu V Goudar
Lab of Aero & Hydrodynamics,
Delft University of Technology
Delft, The Netherlands
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160421/26af2763/attachment.html>

From andy.bauer at kitware.com  Thu Apr 21 17:45:50 2016
From: andy.bauer at kitware.com (Andy Bauer)
Date: Thu, 21 Apr 2016 17:45:50 -0400
Subject: [Paraview] Parallel Unstructured Format Recommendations
In-Reply-To: <FEBA4B4A0B6E9A4FA7967C7D9FE897CF5102CFAC@DAG22.EGL.ENGILITYCORP.COM>
References: <FEBA4B4A0B6E9A4FA7967C7D9FE897CF5102CFAC@DAG22.EGL.ENGILITYCORP.COM>
Message-ID: <CAMaOp+F6DUHTVaO-wd8CJx=ncY3Gf89wZXjzZU3S4yqyZabbDw@mail.gmail.com>

Hi Sean,

I don't know the answer since I don't deal with that many different
unstructured grid file formats when reading data into PV. As far as I know,
we don't mark too carefully which unstructured grid readers can partition
data in parallel. My best advice for this is just to try it reading
different data files yourself and see what happens -- not very helpful but
the best suggestion I can give. If you need a sample data set, you can try
cloning from git://vtk.org/VTKData.git which should have most of the data
formats you're interested in.

Best,

Andy


On Wed, Apr 20, 2016 at 1:13 PM, <Sean.Ziegeler at engilitycorp.com> wrote:

> ParaView has improved its readers a lot lately, so I'd love some guidance
> on which are the best options these days.  I need something that is rather
> scalable, especially for the simulation.  Our group had initially arrived
> at XDMF, but the documentation seems to suggest that it doesn't use
> Parallel HDF5 (that one must use collections of serial HDF5 files
> instead).  Maybe that is dated?  CGNS seems to support Parallel HDF5 on the
> sim side; does the PV reader support reading it in parallel?  I'm leaning
> toward Parallel HDF5 as the underlying container, but I'd consider other
> alternatives if they are scalable and reasonably portable.
>
> Thanks!
> Sean
>
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160421/c80828a4/attachment.html>

From manu.gvm at gmail.com  Thu Apr 21 18:28:13 2016
From: manu.gvm at gmail.com (Manu V G)
Date: Fri, 22 Apr 2016 00:28:13 +0200
Subject: [Paraview] [EXTERNAL]  Coordinate system transformation
In-Reply-To: <CACNtz3jycRzXgTwLzBwTXr6WC1DHCk2gWRYYLboOVXenUHjSeQ@mail.gmail.com>
References: <CACNtz3iixwJNTAG4spHW+-5N-R+OnyhecxqO60xw9rW9jdwTuA@mail.gmail.com>
 <06A80853-0EBE-46F0-B88A-DE44B4406505@sandia.gov>
 <CACNtz3iD7PvMmbD5J5TJagQKwpzqZtbWydviLLbMt=dC-dBLbA@mail.gmail.com>
 <CACNtz3jycRzXgTwLzBwTXr6WC1DHCk2gWRYYLboOVXenUHjSeQ@mail.gmail.com>
Message-ID: <CACNtz3g+YeGQh0Y3B-0wnARoUmJm2b1MLL02d7AVji32LZjcHA@mail.gmail.com>

Thanks for your quick reply.
Sorry, I was not very clear. I will try to explain clearly here.

> Maybe somebody else understands better, but I am totally confused by what
you are asking. It sounds like you have an original coordinate system x,y,z
and a new coordinate system x1,y1,z1.

I don't have the new coordinate system (x1,y1,z1) loaded in paraview. I
compute the origin and unit vectors of new coordinate system that I need to
create  in paraview using the programmable filter.

> Then you have a velocity vector u,v,w defined in the original coordinate
system (x,y,z) that you want to transform to the new coordinate system
(x1,y1,z1). This should be straightforward in either Calculator or Python
Calculator or Programmable Filter. In fact, it sounds like you are already
doing that.

Yes. I multiple the velocity vector in (x,y,z) system at all points by
transformation matrix. Hence, a new vector is created in (x,y,z) coordinate
system.

> When you say, ?however, those velocities correspond to (x1,y1,z1)
coordinate system,? I assume that means that you have already done this
transformation. What do you mean by ?associate these? velocities to a new
coordinate system?? You just have associated them with the new coordinate
system.

I meant the new vector created is associated with (x1,y1,z1) coordinate
system. Now, I want to create the new coordinate system (x1,y1,z1) and
associate the new vector to it. If I create a slice normal to 'y' direction
in paraview, I want it to create a slice normal to 'y1' in new coordinate
system.

I hope I am clear?..

Thanks and regards
Manu




>
> From: ParaView <paraview-bounces at paraview.org> on behalf of Manu V G <
manu.gvm at gmail.com>
> Date: Thursday, April 21, 2016 at 11:28 AM
> To: "paraview at paraview.org" <paraview at paraview.org>
> Subject: [EXTERNAL] [Paraview] Coordinate system transformation
>
>
>
> Hello everyone!
>
> Is it possible to create new local coordinate system (x1,y1,z1) and
compute velocities in that (in short coordinate transformation) from the
original system (x,y,z)? Google search did not help me much. And
'Transform' filter do not transform velocities to the new coordinate system
(is a geometrical transformation).
>
> Problem in detail :
>
> I read a 3D velocity field in Paraview and compute orthogonal
eigenvectors (x1,y1,z1) at a certain point 'O1' using 'Programmable
Filter'. These eigenvectors (x1,y1,z1) act as basis for the new coordinate
system with origin 'O1'. I am trying and just want to visualize velocity in
plane z1=0. For this, I need to transform velocity field from original
system to new coordinate system (x1,y1,z1). And I am trying solve it in the
following way. Maybe there is simple way to do it Paraview.
>
> From eigenvectors, I can specify the plane (z1=0) by using a 'Slice'
filter. The velocities in that plane correspond to the global velocity
(u,v,w) in (x,y,z) coordinate system. Then, I use transformation matrix to
compute new velocity vector (u1,v1,w1) using 'Calculator' or 'Python
Calculation'. However, those velocities correspond to (x1,y1,z1) coordinate
system. So, is there a way to associate these newly computed velocities to
a new coordinate system and plot them?
>
> Or is there a different way to do it Paraview?
>
>
>
> I would be very thankful for your suggestions and inputs.
>
>
>
> Thanks in advance, yours
>
> --
>
> Manu V Goudar
>
> Lab of Aero & Hydrodynamics,
>
> Delft University of Technology
>
> Delft, The Netherlands
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160422/bc989829/attachment.html>

From kmorel at sandia.gov  Thu Apr 21 18:37:47 2016
From: kmorel at sandia.gov (Moreland, Kenneth)
Date: Thu, 21 Apr 2016 22:37:47 +0000
Subject: [Paraview] [EXTERNAL]  Coordinate system transformation
In-Reply-To: <CACNtz3g+YeGQh0Y3B-0wnARoUmJm2b1MLL02d7AVji32LZjcHA@mail.gmail.com>
References: <CACNtz3iixwJNTAG4spHW+-5N-R+OnyhecxqO60xw9rW9jdwTuA@mail.gmail.com>
 <06A80853-0EBE-46F0-B88A-DE44B4406505@sandia.gov>
 <CACNtz3iD7PvMmbD5J5TJagQKwpzqZtbWydviLLbMt=dC-dBLbA@mail.gmail.com>
 <CACNtz3jycRzXgTwLzBwTXr6WC1DHCk2gWRYYLboOVXenUHjSeQ@mail.gmail.com>
 <CACNtz3g+YeGQh0Y3B-0wnARoUmJm2b1MLL02d7AVji32LZjcHA@mail.gmail.com>
Message-ID: <7DEED3FF-7508-40F4-AD70-126D8A092C70@sandia.gov>

I?m still not sure what you mean by ?create the new coordinate system.? Do you perhaps mean that you want ParaView to render the data using positions in x1,y1,z1 instead of x,y,z? A straightforward way to do this is to use the calculator filter to perform your matrix transformation from x,y,z to x1,y1,z1 on the point coordinates array (names ?coords? in the ParaView GUI) and then click the checkbox labeled ?Coordinate Results?. That will write the results of the transformation into the point coordinates array and will have the effect of moving the data.

-Ken



From: Manu V G <manu.gvm at gmail.com>
Date: Thursday, April 21, 2016 at 4:28 PM
To: Kenneth Moreland <kmorel at sandia.gov>
Cc: "paraview at paraview.org" <paraview at paraview.org>
Subject: Re: [EXTERNAL] [Paraview] Coordinate system transformation


Thanks for your quick reply.
Sorry, I was not very clear. I will try to explain clearly here.

> Maybe somebody else understands better, but I am totally confused by what you are asking. It sounds like you have an original coordinate system x,y,z and a new coordinate system x1,y1,z1.

I don't have the new coordinate system (x1,y1,z1) loaded in paraview. I compute the origin and unit vectors of new coordinate system that I need to create  in paraview using the programmable filter.

> Then you have a velocity vector u,v,w defined in the original coordinate system (x,y,z) that you want to transform to the new coordinate system (x1,y1,z1). This should be straightforward in either Calculator or Python Calculator or Programmable Filter. In fact, it sounds like you are already doing that.

Yes. I multiple the velocity vector in (x,y,z) system at all points by transformation matrix. Hence, a new vector is created in (x,y,z) coordinate system.

> When you say, ?however, those velocities correspond to (x1,y1,z1) coordinate system,? I assume that means that you have already done this transformation. What do you mean by ?associate these? velocities to a new coordinate system?? You just have associated them with the new coordinate system.

I meant the new vector created is associated with (x1,y1,z1) coordinate system. Now, I want to create the new coordinate system (x1,y1,z1) and associate the new vector to it. If I create a slice normal to 'y' direction in paraview, I want it to create a slice normal to 'y1' in new coordinate system.

I hope I am clear?..

Thanks and regards
Manu




>
> From: ParaView <paraview-bounces at paraview.org<mailto:paraview-bounces at paraview.org>> on behalf of Manu V G <manu.gvm at gmail.com<mailto:manu.gvm at gmail.com>>
> Date: Thursday, April 21, 2016 at 11:28 AM
> To: "paraview at paraview.org<mailto:paraview at paraview.org>" <paraview at paraview.org<mailto:paraview at paraview.org>>
> Subject: [EXTERNAL] [Paraview] Coordinate system transformation
>
>
>
> Hello everyone!
>
> Is it possible to create new local coordinate system (x1,y1,z1) and compute velocities in that (in short coordinate transformation) from the original system (x,y,z)? Google search did not help me much. And 'Transform' filter do not transform velocities to the new coordinate system (is a geometrical transformation).
>
> Problem in detail :
>
> I read a 3D velocity field in Paraview and compute orthogonal eigenvectors (x1,y1,z1) at a certain point 'O1' using 'Programmable Filter'. These eigenvectors (x1,y1,z1) act as basis for the new coordinate system with origin 'O1'. I am trying and just want to visualize velocity in plane z1=0. For this, I need to transform velocity field from original system to new coordinate system (x1,y1,z1). And I am trying solve it in the following way. Maybe there is simple way to do it Paraview.
>
> From eigenvectors, I can specify the plane (z1=0) by using a 'Slice' filter. The velocities in that plane correspond to the global velocity (u,v,w) in (x,y,z) coordinate system. Then, I use transformation matrix to compute new velocity vector (u1,v1,w1) using 'Calculator' or 'Python Calculation'. However, those velocities correspond to (x1,y1,z1) coordinate system. So, is there a way to associate these newly computed velocities to a new coordinate system and plot them?
>
> Or is there a different way to do it Paraview?
>
>
>
> I would be very thankful for your suggestions and inputs.
>
>
>
> Thanks in advance, yours
>
> --
>
> Manu V Goudar
>
> Lab of Aero & Hydrodynamics,
>
> Delft University of Technology
>
> Delft, The Netherlands
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160421/21d5691d/attachment.html>

From mgammar at outlook.fr  Fri Apr 22 04:21:31 2016
From: mgammar at outlook.fr (Marwen Gammar)
Date: Fri, 22 Apr 2016 10:21:31 +0200
Subject: [Paraview] 3d text problem
In-Reply-To: <B3192C82-1C40-4A19-B4AF-7E98B9DB72F7@sandia.gov>
References: <B3192C82-1C40-4A19-B4AF-7E98B9DB72F7@sandia.gov>
Message-ID: <BAY182-W819868CE1F551B4FAA7D07D16F0@phx.gbl>

Thank you for your quick answer, however i am afraid i wasn't explicit in my questions:
For the first point, yes, i knew that, but when i create 3d text, it is always in the same place,i can't put words in each face of my cube for example,
For the second point, i wasn't talking about applying text with Paraview but directly with the Vtk programm i wrote ( i think it could be more simple for me than if i always use the 3d text program)
Here is my programm:
# vtk DataFile Version 2.0 Cube example ASCII DATASET POLYDATA POINTS 8 float 0.0 0.0 0.01.0 0.0 0.01.0 1.0 0.00.0 1.0 0.00.0 0.0 1.01.0 0.0 1.01.0 1.0 1.00.0 1.0 1.0POLYGONS 6 30 4 0 1 2 3 4 4 5 6 7 4 0 1 5 4 4 2 3 7 6 4 0 4 7 3 4 1 2 6 5CELL_DATA 6 SCALARS cell_scalars int 1 LOOKUP_TABLE default 0 1 2 3 4 5 NORMALS cell_normals float0 0 -1 0 0 1 0 -1 0 0 1 0 -1 0 0 1 0 0 FIELD FieldData 2 cellIds 1 6 int 012345 faceAttributes 2 6 float 0.0 1.0 1.0 2.0 2.0 3.0 3.0 4.0 4.0 5.0 5.0 6.0POINT_DATA 8 SCALARS sample_scalars float 1 LOOKUP_TABLE my_table 0.01.02.03.04.05.06.07.0LOOKUP_TABLE my_table 8 0.0 0.0 0.0 1.01.0 0.0 0.0 1.00.0 1.0 0.0 1.01.0 1.0 0.0 1.00.0 0.0 1.0 1.01.0 0.0 1.0 1.00.0 1.0 1.0 1.01.0 1.0 1.0 1.0
i want to apply a text directly on each face from this programm which will be read by Paraview.
Thank you very much for help,Kind regards,Marwen
From: kmorel at sandia.gov
To: mgammar at outlook.fr; paraview at paraview.org
Subject: Re: [Paraview] 3d text problem
Date: Thu, 21 Apr 2016 15:25:01 +0000











Marwen,


 


You asked 3 questions. I will try to answer them.
 
?I want to use the 3d text on the surface but it is inverted.? It sounds like you are looking at your text from the back. Try moving the camera around to the front. You can also click the
 toolbar button marked ?-Z? (2nd row near the right). That should place the camera where the text is forward.
 
?moreover I don?t know how to write it directly on the program? In the properties panel there is an editable box labeled ?Text?. Change that and then hit the ?Apply? button to change the
 text.
 
?what does this mean?? That definitely looks like part of a data file in what is called the legacy VTK format. However, a large part of the file is missing, so that data will not load correctly.
 
-Ken
 

From: 
ParaView <paraview-bounces at paraview.org> on behalf of Marwen Gammar <mgammar at outlook.fr>

Date: Thursday, April 21, 2016 at 8:20 AM

To: "paraview at paraview.org" <paraview at paraview.org>

Subject: [EXTERNAL] [Paraview] 3d text problem


 




Hello Miss, Mister,


I am beginning in the utilisation of the software Paraview and have some problem with its use:


I want to use the 3d text on the surface but it is inverted, 


moreover i don't know how to write it directly on the programm (vtk),


and what does this means?:



POINT_DATA 8

SCALARS sample_scalars float 1

LOOKUP_TABLE my_table

0.0

1.0

2.0

3.0

4.0

5.0

6.0

7.0

LOOKUP_TABLE my_table 8

0.0 0.0 0.0 1.0

1.0 0.0 0.0 1.0

0.0 1.0 0.0 1.0

1.0 1.0 0.0 1.0

0.0 0.0 1.0 1.0

1.0 0.0 1.0 1.0

0.0 1.0 1.0 1.0

1.0 1.0 1.0 1.0

 


Could you please indicate me how to solve those problems?


 


Thank you kindly for your answer,


Kind regards,


Marwen




 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160422/f07406f0/attachment.html>

From manu.gvm at gmail.com  Fri Apr 22 04:45:33 2016
From: manu.gvm at gmail.com (Manu V G)
Date: Fri, 22 Apr 2016 10:45:33 +0200
Subject: [Paraview] [EXTERNAL]  Coordinate system transformation
In-Reply-To: <7DEED3FF-7508-40F4-AD70-126D8A092C70@sandia.gov>
References: <CACNtz3iixwJNTAG4spHW+-5N-R+OnyhecxqO60xw9rW9jdwTuA@mail.gmail.com>
 <06A80853-0EBE-46F0-B88A-DE44B4406505@sandia.gov>
 <CACNtz3iD7PvMmbD5J5TJagQKwpzqZtbWydviLLbMt=dC-dBLbA@mail.gmail.com>
 <CACNtz3jycRzXgTwLzBwTXr6WC1DHCk2gWRYYLboOVXenUHjSeQ@mail.gmail.com>
 <CACNtz3g+YeGQh0Y3B-0wnARoUmJm2b1MLL02d7AVji32LZjcHA@mail.gmail.com>
 <7DEED3FF-7508-40F4-AD70-126D8A092C70@sandia.gov>
Message-ID: <CACNtz3g4r3Hv9PMvhThGdZLRVv6M8EhBGURcSzo4sd6WGqeMug@mail.gmail.com>

> I?m still not sure what you mean by ?create the new coordinate system.? Do you perhaps mean that you want ParaView to render the data using positions in x1,y1,z1 instead of x,y,z?

Yes. Thanks a lot. Now I understand why I was not so clear.


>A straightforward way to do this is to use the calculator filter to perform your matrix transformation from x,y,z to x1,y1,z1 on the point coordinates array (names ?coords? in the ParaView GUI) and then click the checkbox labeled ?Coordinate Results?. That will write the results of the transformation into the point coordinates array and will have the effect of moving the data.

Thank you. I didn't know it was so simple to do this.


Warm Regards
Manu






>
> From: Manu V G <manu.gvm at gmail.com>
> Date: Thursday, April 21, 2016 at 4:28 PM
> To: Kenneth Moreland <kmorel at sandia.gov>
> Cc: "paraview at paraview.org" <paraview at paraview.org>
> Subject: Re: [EXTERNAL] [Paraview] Coordinate system transformation
>
>
>
> Thanks for your quick reply.
> Sorry, I was not very clear. I will try to explain clearly here.
>
> > Maybe somebody else understands better, but I am totally confused by what you are asking. It sounds like you have an original coordinate system x,y,z and a new coordinate system x1,y1,z1.
>
> I don't have the new coordinate system (x1,y1,z1) loaded in paraview. I compute the origin and unit vectors of new coordinate system that I need to create  in paraview using the programmable filter.
>
> > Then you have a velocity vector u,v,w defined in the original coordinate system (x,y,z) that you want to transform to the new coordinate system (x1,y1,z1). This should be straightforward in either Calculator or Python Calculator or Programmable Filter. In fact, it sounds like you are already doing that.
>
> Yes. I multiple the velocity vector in (x,y,z) system at all points by transformation matrix. Hence, a new vector is created in (x,y,z) coordinate system.
>
> > When you say, ?however, those velocities correspond to (x1,y1,z1) coordinate system,? I assume that means that you have already done this transformation. What do you mean by ?associate these? velocities to a new coordinate system?? You just have associated them with the new coordinate system.
>
> I meant the new vector created is associated with (x1,y1,z1) coordinate system. Now, I want to create the new coordinate system (x1,y1,z1) and associate the new vector to it. If I create a slice normal to 'y' direction in paraview, I want it to create a slice normal to 'y1' in new coordinate system.
>
> I hope I am clear?..
>
> Thanks and regards
> Manu
>
>
>
> >
> > From: ParaView <paraview-bounces at paraview.org> on behalf of Manu V G <manu.gvm at gmail.com>
> > Date: Thursday, April 21, 2016 at 11:28 AM
> > To: "paraview at paraview.org" <paraview at paraview.org>
> > Subject: [EXTERNAL] [Paraview] Coordinate system transformation
> >
> >
> >
> > Hello everyone!
> >
> > Is it possible to create new local coordinate system (x1,y1,z1) and compute velocities in that (in short coordinate transformation) from the original system (x,y,z)? Google search did not help me much. And 'Transform' filter do not transform velocities to the new coordinate system (is a geometrical transformation).
> >
> > Problem in detail :
> >
> > I read a 3D velocity field in Paraview and compute orthogonal eigenvectors (x1,y1,z1) at a certain point 'O1' using 'Programmable Filter'. These eigenvectors (x1,y1,z1) act as basis for the new coordinate system with origin 'O1'. I am trying and just want to visualize velocity in plane z1=0. For this, I need to transform velocity field from original system to new coordinate system (x1,y1,z1). And I am trying solve it in the following way. Maybe there is simple way to do it Paraview.
> >
> > From eigenvectors, I can specify the plane (z1=0) by using a 'Slice' filter. The velocities in that plane correspond to the global velocity (u,v,w) in (x,y,z) coordinate system. Then, I use transformation matrix to compute new velocity vector (u1,v1,w1) using 'Calculator' or 'Python Calculation'. However, those velocities correspond to (x1,y1,z1) coordinate system. So, is there a way to associate these newly computed velocities to a new coordinate system and plot them?
> >
> > Or is there a different way to do it Paraview?
> >
> >
> >
> > I would be very thankful for your suggestions and inputs.
> >
> >
> >
> > Thanks in advance, yours
> >
> > --
> >
> > Manu V Goudar
> >
> > Lab of Aero & Hydrodynamics,
> >
> > Delft University of Technology
> >
> > Delft, The Netherlands




-- 
Manu

From ellonpaiva at gmail.com  Fri Apr 22 09:46:42 2016
From: ellonpaiva at gmail.com (Ellon Paiva)
Date: Fri, 22 Apr 2016 15:46:42 +0200
Subject: [Paraview] Build plugin with both local and system vtk
Message-ID: <571A2B42.6040902@gmail.com>

Hello all,

I'm wondering if there's a clean way to build paraview from source when 
you also have a VTK version installed in the system.

I'm asking this because I'm using some (ROS <http://www.ros.org/>) 
packages that depends on VTK, thus I already have it installed in my 
system. Then, when trying to build a plugin (for instance PCLPlugin 
<http://www.paraview.org/Wiki/ParaView/PCL_Plugin>) I have the errors 
you can find below. I imagine that's something related with cmake 
finding the system one libraries instead of the ones from my local build.

Does anyone have an idea how to solve this?

Also, any clue of which cmake_policy to define (CMP0023)?

Best,
Ellon


-----------------------------------------------------------------

cmake -DParaView_DIR=/home/emendes/devel/src/paraview-4.0.1/build 
-DPCL_DIR=/home/emendes/devel/src/pcl/build ..
-- The C compiler identification is GNU 4.8.4
-- The CXX compiler identification is GNU 4.8.4
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Looking for Q_WS_X11
-- Looking for Q_WS_X11 - found
-- Looking for Q_WS_WIN
-- Looking for Q_WS_WIN - not found
-- Looking for Q_WS_QWS
-- Looking for Q_WS_QWS - not found
-- Looking for Q_WS_MAC
-- Looking for Q_WS_MAC - not found
-- Found Qt4: /usr/bin/qmake-qt4 (found version "4.8.6")
-- Found PythonLibs: /usr/lib/x86_64-linux-gnu/libpython2.7.so
-- checking for module 'eigen3'
--   found eigen3, version 3.2.0
-- Found eigen: /usr/include/eigen3
-- Boost version: 1.54.0
-- Found the following Boost libraries:
--   system
--   filesystem
--   thread
--   date_time
--   iostreams
--   serialization
--   chrono
-- checking for module 'flann'
--   found flann, version 1.8.4
-- Found Flann: /usr/lib/x86_64-linux-gnu/libflann_cpp_s.a
-- checking for module 'openni-dev'
--   package 'openni-dev' not found
-- Found openni: /usr/lib/libOpenNI.so
-- checking for module 'openni2-dev'
--   package 'openni2-dev' not found
-- Could NOT find OpenNI2 (missing:  OPENNI2_LIBRARY OPENNI2_INCLUDE_DIRS)
** WARNING ** io features related to openni2 will be disabled
** WARNING ** io features related to pcap will be disabled
** WARNING ** io features related to png will be disabled
-- Some (but not all) targets in this export set were already defined.
Targets Defined: 
vtkWrapTcl;vtkWrapTclInit;vtkWrapPython;vtkWrapPythonInit;vtkParseJava;vtkWrapJava;vtksys;vtkDICOMParser;vtkmetaio;vtkexoIIc;vtkalglib;vtkEncodeString;VPIC;Cosmo;vtkftgl
Targets not yet defined: 
vtkproj4;vtkverdict;vtkCommonTCL;vtkCommonPythonD;vtkCommonJava;vtkCommon;vtkFilteringTCL;vtkFilteringPythonD;vtkFilteringJava;vtkFiltering;vtkImagingTCL;vtkImagingPythonD;vtkImagingJava;vtkImaging;vtkGraphicsTCL;vtkGraphicsPythonD;vtkGraphicsJava;vtkGraphics;vtkGenericFilteringTCL;vtkGenericFilteringPythonD;vtkGenericFilteringJava;vtkGenericFiltering;vtkIOTCL;vtkIOPythonD;vtkIOJava;vtkIO;vtkRenderingTCL;vtkRenderingPythonD;vtkRenderingJava;vtkRendering;vtkRenderingPythonTkWidgets;vtkVolumeRenderingTCL;vtkVolumeRenderingPythonD;vtkVolumeRenderingJava;vtkVolumeRendering;vtkHybridTCL;vtkHybridPythonD;vtkHybridJava;vtkHybrid;vtkWidgetsTCL;vtkWidgetsPythonD;vtkWidgetsJava;vtkWidgets;vtkParallelTCL;vtkParallelPythonD;vtkParallelJava;vtkParallel;vtkInfovisTCL;vtkInfovisPythonD;vtkInfovisJava;vtkInfovis;vtkGeovisTCL;vtkGeovisPythonD;vtkGeovisJava;vtkGeovis;vtkViewsTCL;vtkViewsPythonD;vtkViewsJava;vtkViews;vtkQtChart;QVTK;vtkChartsTCL;vtkChartsPythonD;vtkChartsJava;vtkCharts;vtk;pvtk;vtkPythonCore

CMake Error at /usr/lib/vtk-5.8/VTKTargets.cmake:47 (add_executable):
   add_executable cannot create imported target "vtkWrapTcl" because another
   target with the same name already exists.
Call Stack (most recent call first):
   /usr/lib/vtk-5.8/VTKConfig.cmake:200 (INCLUDE)
   /usr/share/cmake-2.8/Modules/FindVTK.cmake:73 (find_package)
   /home/emendes/devel/src/pcl/build/PCLConfig.cmake:324 (find_package)
   /home/emendes/devel/src/pcl/build/PCLConfig.cmake:464 (find_VTK)
   /home/emendes/devel/src/pcl/build/PCLConfig.cmake:646 
(find_external_library)
   CMakeLists.txt:9 (find_package)


CMake Error at /usr/lib/vtk-5.8/VTKTargets.cmake:50 (add_executable):
   add_executable cannot create imported target "vtkWrapTclInit" because
   another target with the same name already exists.
Call Stack (most recent call first):
   /usr/lib/vtk-5.8/VTKConfig.cmake:200 (INCLUDE)
   /usr/share/cmake-2.8/Modules/FindVTK.cmake:73 (find_package)
   /home/emendes/devel/src/pcl/build/PCLConfig.cmake:324 (find_package)
   /home/emendes/devel/src/pcl/build/PCLConfig.cmake:464 (find_VTK)
   /home/emendes/devel/src/pcl/build/PCLConfig.cmake:646 
(find_external_library)
   CMakeLists.txt:9 (find_package)


CMake Error at /usr/lib/vtk-5.8/VTKTargets.cmake:53 (add_executable):
   add_executable cannot create imported target "vtkWrapPython" because
   another target with the same name already exists.
Call Stack (most recent call first):
   /usr/lib/vtk-5.8/VTKConfig.cmake:200 (INCLUDE)
   /usr/share/cmake-2.8/Modules/FindVTK.cmake:73 (find_package)
   /home/emendes/devel/src/pcl/build/PCLConfig.cmake:324 (find_package)
   /home/emendes/devel/src/pcl/build/PCLConfig.cmake:464 (find_VTK)
   /home/emendes/devel/src/pcl/build/PCLConfig.cmake:646 
(find_external_library)
   CMakeLists.txt:9 (find_package)


CMake Error at /usr/lib/vtk-5.8/VTKTargets.cmake:56 (add_executable):
   add_executable cannot create imported target "vtkWrapPythonInit" because
   another target with the same name already exists.
Call Stack (most recent call first):
   /usr/lib/vtk-5.8/VTKConfig.cmake:200 (INCLUDE)
   /usr/share/cmake-2.8/Modules/FindVTK.cmake:73 (find_package)
   /home/emendes/devel/src/pcl/build/PCLConfig.cmake:324 (find_package)
   /home/emendes/devel/src/pcl/build/PCLConfig.cmake:464 (find_VTK)
   /home/emendes/devel/src/pcl/build/PCLConfig.cmake:646 
(find_external_library)
   CMakeLists.txt:9 (find_package)


CMake Error at /usr/lib/vtk-5.8/VTKTargets.cmake:59 (add_executable):
   add_executable cannot create imported target "vtkParseJava" because 
another
   target with the same name already exists.
Call Stack (most recent call first):
   /usr/lib/vtk-5.8/VTKConfig.cmake:200 (INCLUDE)
   /usr/share/cmake-2.8/Modules/FindVTK.cmake:73 (find_package)
   /home/emendes/devel/src/pcl/build/PCLConfig.cmake:324 (find_package)
   /home/emendes/devel/src/pcl/build/PCLConfig.cmake:464 (find_VTK)
   /home/emendes/devel/src/pcl/build/PCLConfig.cmake:646 
(find_external_library)
   CMakeLists.txt:9 (find_package)


CMake Error at /usr/lib/vtk-5.8/VTKTargets.cmake:62 (add_executable):
   add_executable cannot create imported target "vtkWrapJava" because 
another
   target with the same name already exists.
Call Stack (most recent call first):
   /usr/lib/vtk-5.8/VTKConfig.cmake:200 (INCLUDE)
   /usr/share/cmake-2.8/Modules/FindVTK.cmake:73 (find_package)
   /home/emendes/devel/src/pcl/build/PCLConfig.cmake:324 (find_package)
   /home/emendes/devel/src/pcl/build/PCLConfig.cmake:464 (find_VTK)
   /home/emendes/devel/src/pcl/build/PCLConfig.cmake:646 
(find_external_library)
   CMakeLists.txt:9 (find_package)


CMake Error at /usr/lib/vtk-5.8/VTKTargets.cmake:65 (add_library):
   add_library cannot create imported target "vtksys" because another target
   with the same name already exists.
Call Stack (most recent call first):
   /usr/lib/vtk-5.8/VTKConfig.cmake:200 (INCLUDE)
   /usr/share/cmake-2.8/Modules/FindVTK.cmake:73 (find_package)
   /home/emendes/devel/src/pcl/build/PCLConfig.cmake:324 (find_package)
   /home/emendes/devel/src/pcl/build/PCLConfig.cmake:464 (find_VTK)
   /home/emendes/devel/src/pcl/build/PCLConfig.cmake:646 
(find_external_library)
   CMakeLists.txt:9 (find_package)


CMake Error at /usr/lib/vtk-5.8/VTKTargets.cmake:68 (add_library):
   add_library cannot create imported target "vtkDICOMParser" because 
another
   target with the same name already exists.
Call Stack (most recent call first):
   /usr/lib/vtk-5.8/VTKConfig.cmake:200 (INCLUDE)
   /usr/share/cmake-2.8/Modules/FindVTK.cmake:73 (find_package)
   /home/emendes/devel/src/pcl/build/PCLConfig.cmake:324 (find_package)
   /home/emendes/devel/src/pcl/build/PCLConfig.cmake:464 (find_VTK)
   /home/emendes/devel/src/pcl/build/PCLConfig.cmake:646 
(find_external_library)
   CMakeLists.txt:9 (find_package)


CMake Error at /usr/lib/vtk-5.8/VTKTargets.cmake:77 (add_library):
   add_library cannot create imported target "vtkmetaio" because another
   target with the same name already exists.
Call Stack (most recent call first):
   /usr/lib/vtk-5.8/VTKConfig.cmake:200 (INCLUDE)
   /usr/share/cmake-2.8/Modules/FindVTK.cmake:73 (find_package)
   /home/emendes/devel/src/pcl/build/PCLConfig.cmake:324 (find_package)
   /home/emendes/devel/src/pcl/build/PCLConfig.cmake:464 (find_VTK)
   /home/emendes/devel/src/pcl/build/PCLConfig.cmake:646 
(find_external_library)
   CMakeLists.txt:9 (find_package)


CMake Error at /usr/lib/vtk-5.8/VTKTargets.cmake:80 (add_library):
   add_library cannot create imported target "vtkexoIIc" because another
   target with the same name already exists.
Call Stack (most recent call first):
   /usr/lib/vtk-5.8/VTKConfig.cmake:200 (INCLUDE)
   /usr/share/cmake-2.8/Modules/FindVTK.cmake:73 (find_package)
   /home/emendes/devel/src/pcl/build/PCLConfig.cmake:324 (find_package)
   /home/emendes/devel/src/pcl/build/PCLConfig.cmake:464 (find_VTK)
   /home/emendes/devel/src/pcl/build/PCLConfig.cmake:646 
(find_external_library)
   CMakeLists.txt:9 (find_package)


CMake Error at /usr/lib/vtk-5.8/VTKTargets.cmake:83 (add_library):
   add_library cannot create imported target "vtkalglib" because another
   target with the same name already exists.
Call Stack (most recent call first):
   /usr/lib/vtk-5.8/VTKConfig.cmake:200 (INCLUDE)
   /usr/share/cmake-2.8/Modules/FindVTK.cmake:73 (find_package)
   /home/emendes/devel/src/pcl/build/PCLConfig.cmake:324 (find_package)
   /home/emendes/devel/src/pcl/build/PCLConfig.cmake:464 (find_VTK)
   /home/emendes/devel/src/pcl/build/PCLConfig.cmake:646 
(find_external_library)
   CMakeLists.txt:9 (find_package)


CMake Error at /usr/lib/vtk-5.8/VTKTargets.cmake:86 (add_executable):
   add_executable cannot create imported target "vtkEncodeString" because
   another target with the same name already exists.
Call Stack (most recent call first):
   /usr/lib/vtk-5.8/VTKConfig.cmake:200 (INCLUDE)
   /usr/share/cmake-2.8/Modules/FindVTK.cmake:73 (find_package)
   /home/emendes/devel/src/pcl/build/PCLConfig.cmake:324 (find_package)
   /home/emendes/devel/src/pcl/build/PCLConfig.cmake:464 (find_VTK)
   /home/emendes/devel/src/pcl/build/PCLConfig.cmake:646 
(find_external_library)
   CMakeLists.txt:9 (find_package)


CMake Error at /usr/lib/vtk-5.8/VTKTargets.cmake:89 (add_library):
   add_library cannot create imported target "VPIC" because another target
   with the same name already exists.
Call Stack (most recent call first):
   /usr/lib/vtk-5.8/VTKConfig.cmake:200 (INCLUDE)
   /usr/share/cmake-2.8/Modules/FindVTK.cmake:73 (find_package)
   /home/emendes/devel/src/pcl/build/PCLConfig.cmake:324 (find_package)
   /home/emendes/devel/src/pcl/build/PCLConfig.cmake:464 (find_VTK)
   /home/emendes/devel/src/pcl/build/PCLConfig.cmake:646 
(find_external_library)
   CMakeLists.txt:9 (find_package)


CMake Error at /usr/lib/vtk-5.8/VTKTargets.cmake:92 (add_library):
   add_library cannot create imported target "Cosmo" because another target
   with the same name already exists.
Call Stack (most recent call first):
   /usr/lib/vtk-5.8/VTKConfig.cmake:200 (INCLUDE)
   /usr/share/cmake-2.8/Modules/FindVTK.cmake:73 (find_package)
   /home/emendes/devel/src/pcl/build/PCLConfig.cmake:324 (find_package)
   /home/emendes/devel/src/pcl/build/PCLConfig.cmake:464 (find_VTK)
   /home/emendes/devel/src/pcl/build/PCLConfig.cmake:646 
(find_external_library)
   CMakeLists.txt:9 (find_package)


CMake Error at /usr/lib/vtk-5.8/VTKTargets.cmake:95 (add_library):
   add_library cannot create imported target "vtkftgl" because another 
target
   with the same name already exists.
Call Stack (most recent call first):
   /usr/lib/vtk-5.8/VTKConfig.cmake:200 (INCLUDE)
   /usr/share/cmake-2.8/Modules/FindVTK.cmake:73 (find_package)
   /home/emendes/devel/src/pcl/build/PCLConfig.cmake:324 (find_package)
   /home/emendes/devel/src/pcl/build/PCLConfig.cmake:464 (find_VTK)
   /home/emendes/devel/src/pcl/build/PCLConfig.cmake:646 
(find_external_library)
   CMakeLists.txt:9 (find_package)


-- Found libusb-1.0: /usr/include
-- Found qhull: /usr/lib/x86_64-linux-gnu/libqhull.so
-- checking for module 'openni-dev'
--   package 'openni-dev' not found
-- checking for module 'openni2-dev'
--   package 'openni2-dev' not found
-- Could NOT find OpenNI2 (missing:  OPENNI2_LIBRARY OPENNI2_INCLUDE_DIRS)
** WARNING ** visualization features related to openni2 will be disabled
-- looking for PCL_COMMON
-- Found PCL_COMMON: /home/emendes/devel/src/pcl/build/lib/libpcl_common.so
-- looking for PCL_OCTREE
-- Found PCL_OCTREE: /home/emendes/devel/src/pcl/build/lib/libpcl_octree.so
-- looking for PCL_KDTREE
-- Found PCL_KDTREE: /home/emendes/devel/src/pcl/build/lib/libpcl_kdtree.so
-- looking for PCL_SEARCH
-- Found PCL_SEARCH: /home/emendes/devel/src/pcl/build/lib/libpcl_search.so
-- looking for PCL_SAMPLE_CONSENSUS
-- Found PCL_SAMPLE_CONSENSUS: 
/home/emendes/devel/src/pcl/build/lib/libpcl_sample_consensus.so
-- looking for PCL_FILTERS
-- Found PCL_FILTERS: 
/home/emendes/devel/src/pcl/build/lib/libpcl_filters.so
-- looking for PCL_FEATURES
-- Found PCL_FEATURES: 
/home/emendes/devel/src/pcl/build/lib/libpcl_features.so
-- looking for PCL_REGISTRATION
-- Found PCL_REGISTRATION: 
/home/emendes/devel/src/pcl/build/lib/libpcl_registration.so
-- looking for PCL_IO
-- Found PCL_IO: /home/emendes/devel/src/pcl/build/lib/libpcl_io.so
-- looking for PCL_GEOMETRY
-- Found PCL_GEOMETRY: /home/emendes/devel/src/pcl/geometry/include
-- looking for PCL_KEYPOINTS
-- Found PCL_KEYPOINTS: 
/home/emendes/devel/src/pcl/build/lib/libpcl_keypoints.so
-- looking for PCL_SURFACE
-- Found PCL_SURFACE: 
/home/emendes/devel/src/pcl/build/lib/libpcl_surface.so
-- looking for PCL_SEGMENTATION
-- Found PCL_SEGMENTATION: 
/home/emendes/devel/src/pcl/build/lib/libpcl_segmentation.so
-- looking for PCL_RECOGNITION
-- Found PCL_RECOGNITION: 
/home/emendes/devel/src/pcl/build/lib/libpcl_recognition.so
-- looking for PCL_VISUALIZATION
-- Found PCL_VISUALIZATION: 
/home/emendes/devel/src/pcl/build/lib/libpcl_visualization.so
-- looking for PCL_PEOPLE
-- Found PCL_PEOPLE: /home/emendes/devel/src/pcl/build/lib/libpcl_people.so
-- looking for PCL_OUTOFCORE
-- Found PCL_OUTOFCORE: 
/home/emendes/devel/src/pcl/build/lib/libpcl_outofcore.so
-- looking for PCL_TRACKING
-- Found PCL_TRACKING: 
/home/emendes/devel/src/pcl/build/lib/libpcl_tracking.so
-- Found PCL: 
/usr/lib/x86_64-linux-gnu/libboost_system.so;/usr/lib/x86_64-linux-gnu/libboost_filesystem.so;/usr/lib/x86_64-linux-gnu/libboost_thread.so;/usr/lib/x86_64-linux-gnu/libboost_date_time.so;/usr/lib/x86_64-linux-gnu/libboost_iostreams.so;/usr/lib/x86_64-linux-gnu/libboost_serialization.so;/usr/lib/x86_64-linux-gnu/libboost_chrono.so;/usr/lib/x86_64-linux-gnu/libpthread.so;optimized;/home/emendes/devel/src/pcl/build/lib/libpcl_common.so;debug;/home/emendes/devel/src/pcl/build/lib/libpcl_common.so;optimized;/home/emendes/devel/src/pcl/build/lib/libpcl_octree.so;debug;/home/emendes/devel/src/pcl/build/lib/libpcl_octree.so;optimized;/usr/lib/x86_64-linux-gnu/libflann_cpp_s.a;debug;/usr/lib/x86_64-linux-gnu/libflann_cpp_s.a;optimized;/home/emendes/devel/src/pcl/build/lib/libpcl_kdtree.so;debug;/home/emendes/devel/src/pcl/build/lib/libpcl_kdtree.so;optimized;/home/emendes/devel/src/pcl/build/lib/libpcl_search.so;debug;/home/emendes/devel/src/pcl/build/lib/libpcl_search.so;optimized;/home/emendes/devel/src/pcl/build/lib/libpcl_sample_consensus.so;debug;/home/emendes/devel/src/pcl/build/lib/libpcl_sample_consensus.so;optimized;/home/emendes/devel/src/pcl/build/lib/libpcl_filters.so;debug;/home/emendes/devel/src/pcl/build/lib/libpcl_filters.so;optimized;/home/emendes/devel/src/pcl/build/lib/libpcl_features.so;debug;/home/emendes/devel/src/pcl/build/lib/libpcl_features.so;optimized;/home/emendes/devel/src/pcl/build/lib/libpcl_registration.so;debug;/home/emendes/devel/src/pcl/build/lib/libpcl_registration.so;/usr/lib/libOpenNI.so;vtkCommon;vtkFiltering;vtkImaging;vtkGraphics;vtkGenericFiltering;vtkIO;vtkRendering;vtkVolumeRendering;vtkHybrid;vtkWidgets;vtkParallel;vtkInfovis;vtkGeovis;vtkViews;vtkCharts;optimized;/home/emendes/devel/src/pcl/build/lib/libpcl_io.so;debug;/home/emendes/devel/src/pcl/build/lib/libpcl_io.so;optimized;/home/emendes/devel/src/pcl/build/lib/libpcl_keypoints.so;debug;/home/emendes/devel/src/pcl/build/lib/libpcl_keypoints.so;optimized;/usr/lib/x86_64-linux-gnu/libqhull.so;debug;/usr/lib/x86_64-linux-gnu/libqhull.so;optimized;/home/emendes/devel/src/pcl/build/lib/libpcl_surface.so;debug;/home/emendes/devel/src/pcl/build/lib/libpcl_surface.so;optimized;/home/emendes/devel/src/pcl/build/lib/libpcl_segmentation.so;debug;/home/emendes/devel/src/pcl/build/lib/libpcl_segmentation.so;optimized;/home/emendes/devel/src/pcl/build/lib/libpcl_recognition.so;debug;/home/emendes/devel/src/pcl/build/lib/libpcl_recognition.so;optimized;/home/emendes/devel/src/pcl/build/lib/libpcl_visualization.so;debug;/home/emendes/devel/src/pcl/build/lib/libpcl_visualization.so;optimized;/home/emendes/devel/src/pcl/build/lib/libpcl_people.so;debug;/home/emendes/devel/src/pcl/build/lib/libpcl_people.so;optimized;/home/emendes/devel/src/pcl/build/lib/libpcl_outofcore.so;debug;/home/emendes/devel/src/pcl/build/lib/libpcl_outofcore.so;optimized;/home/emendes/devel/src/pcl/build/lib/libpcl_tracking.so;debug;/home/emendes/devel/src/pcl/build/lib/libpcl_tracking.so;/usr/lib/x86_64-linux-gnu/libboost_system.so;/usr/lib/x86_64-linux-gnu/libboost_filesystem.so;/usr/lib/x86_64-linux-gnu/libboost_thread.so;/usr/lib/x86_64-linux-gnu/libboost_date_time.so;/usr/lib/x86_64-linux-gnu/libboost_iostreams.so;/usr/lib/x86_64-linux-gnu/libboost_serialization.so;/usr/lib/x86_64-linux-gnu/libboost_chrono.so;/usr/lib/x86_64-linux-gnu/libpthread.so;optimized;/usr/lib/x86_64-linux-gnu/libqhull.so;debug;/usr/lib/x86_64-linux-gnu/libqhull.so;/usr/lib/libOpenNI.so;optimized;/usr/lib/x86_64-linux-gnu/libflann_cpp_s.a;debug;/usr/lib/x86_64-linux-gnu/libflann_cpp_s.a;vtkCommon;vtkFiltering;vtkImaging;vtkGraphics;vtkGenericFiltering;vtkIO;vtkRendering;vtkVolumeRendering;vtkHybrid;vtkWidgets;vtkParallel;vtkInfovis;vtkGeovis;vtkViews;vtkCharts 

-- Performing Test COMPILER_HAS_HIDDEN_VISIBILITY
-- Performing Test COMPILER_HAS_HIDDEN_VISIBILITY - Success
-- Performing Test COMPILER_HAS_HIDDEN_INLINE_VISIBILITY
-- Performing Test COMPILER_HAS_HIDDEN_INLINE_VISIBILITY - Success
-- Performing Test COMPILER_HAS_DEPRECATED_ATTR
-- Performing Test COMPILER_HAS_DEPRECATED_ATTR - Success
CMake Warning (dev) at CMakeLists.txt:109 (target_link_libraries):
   Policy CMP0023 is not set: Plain and keyword target_link_libraries
   signatures cannot be mixed.  Run "cmake --help-policy CMP0023" for policy
   details.  Use the cmake_policy command to set the policy and suppress 
this
   warning.

   The plain signature for target_link_libraries has already been used with
   the target "vtkPCLFilters".  All uses of target_link_libraries with a
   target should be either all-keyword or all-plain.

   The uses of the plain signature are here:

    * 
/home/emendes/devel/src/paraview-4.0.1/CMake/ParaViewPlugins.cmake:1086 
(TARGET_LINK_LIBRARIES)
    * 
/home/emendes/devel/src/paraview-4.0.1/CMake/ParaViewPlugins.cmake:1089 
(TARGET_LINK_LIBRARIES)

This warning is for project developers.  Use -Wno-dev to suppress it.

-- Configuring incomplete, errors occurred!
See also 
"/home/emendes/devel/src/paraview_plugins/PCLPlugin/build/CMakeFiles/CMakeOutput.log".
See also 
"/home/emendes/devel/src/paraview_plugins/PCLPlugin/build/CMakeFiles/CMakeError.log".
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160422/204ab1da/attachment.html>

From nnc at lanl.gov  Fri Apr 22 10:12:11 2016
From: nnc at lanl.gov (Carlson, Neil)
Date: Fri, 22 Apr 2016 14:12:11 +0000
Subject: [Paraview] [EXTERNAL]  Extracting cells by label
In-Reply-To: <075EABDF-8B5D-40A2-81AC-56652573EB5B@sandia.gov>
References: <F15F421EB9392E4E8AB0A84C912AB2B1989604CD@ECS-EXG-P-MB01.win.lanl.gov>
 <014c002cb56b4c04b967ebafd1236f15@ES01AMSNLNT.srn.sandia.gov>
 <F15F421EB9392E4E8AB0A84C912AB2B19896159A@ECS-EXG-P-MB01.win.lanl.gov>,
 <075EABDF-8B5D-40A2-81AC-56652573EB5B@sandia.gov>
Message-ID: <F15F421EB9392E4E8AB0A84C912AB2B198961737@ECS-EXG-P-MB01.win.lanl.gov>

Ken,  Thanks so much for this suggestion.  I've given it a
brief try, and it looks like it is going to work for us.  Longer
term we may try to write a filter expressly designed for this
use case, but this is workable until then.  Thanks!  -Neil

________________________________
From: Moreland, Kenneth [kmorel at sandia.gov]
Sent: Thursday, April 21, 2016 9:07 AM
To: Carlson, Neil; Scott, W Alan; paraview at paraview.org
Subject: Re: [Paraview] [EXTERNAL] Extracting cells by label

Neil,

You can do it with the ?Find Data? selection mechanism (Section 6.3 of the ParaView Guide). Open the Find Data dialog and make a selection of where the block id field ?is one of? a comma separated list of block ids you want. When you run the selection query, you should see the cells of those blocks outlined. Then hit the extract selection button that will add a threshold-like filter that will extract those selected blocks.

-Ken

From: ParaView <paraview-bounces at paraview.org> on behalf of "Carlson, Neil" <nnc at lanl.gov>
Date: Thursday, April 21, 2016 at 9:01 AM
To: Walter Scott <wascott at sandia.gov>, "paraview at paraview.org" <paraview at paraview.org>
Subject: Re: [Paraview] [EXTERNAL] Extracting cells by label

Sort of, but not exactly.  Threshold would allow me to remove
blocks below a min value and above a max value.  But what I
want is to be able to select (via a checkbox list, for example)
exactly which blocks I want to see, not limited to those in a
range.  And to reiterate, "block n" consists of all cells with
value n in a cell-centered data field.
________________________________
From: Scott, W Alan [wascott at sandia.gov]
Sent: Wednesday, April 20, 2016 5:00 PM
To: Carlson, Neil; paraview at paraview.org
Subject: RE: [EXTERNAL] [Paraview] Extracting cells by label
You mean like the threshold filter?  Threshold out those blocks you don?t want?

Alan

From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Carlson, Neil
Sent: Wednesday, April 20, 2016 4:13 PM
To: paraview at paraview.org
Subject: [EXTERNAL] [Paraview] Extracting cells by label

I have a grid (unstructured and not multi-block) and a cell-centered
data field on the grid.  The field has integer values that serve to
group the cells into conceptual blocks: cells with value 1 form block 1,
and so forth.  Is there some filter that can use such data to actually
extract blocks in such a way that paraview can control their loading
individually, like with the multiblock inspector or the ExtractBlock
filter?

Thanks, Neil
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160422/3fd7ac01/attachment.html>

From m.schlottke-lakemper at aia.rwth-aachen.de  Fri Apr 22 10:41:17 2016
From: m.schlottke-lakemper at aia.rwth-aachen.de (Schlottke-Lakemper, Michael)
Date: Fri, 22 Apr 2016 14:41:17 +0000
Subject: [Paraview] Export scene creates images without actual object
In-Reply-To: <6D6C2BF3-F871-4A25-8C13-0768B37E83E3@aia.rwth-aachen.de>
References: <6D6C2BF3-F871-4A25-8C13-0768B37E83E3@aia.rwth-aachen.de>
Message-ID: <80C50898-0623-4D15-A6A9-FE8A53E8EFC4@aia.rwth-aachen.de>

*bump*

If this particular behavior has not been observed yet, is there anyone who has encountered a similar issue maybe on other platforms? Or does anyone have a suggestion in which direction I could start to investigate? Sorry for my persistence, but I?m completely at a loss here?

Michael


On 19 Apr 2016, at 09:53 , Michael Schlottke-Lakemper <m.schlottke-lakemper at aia.rwth-aachen.de<mailto:m.schlottke-lakemper at aia.rwth-aachen.de>> wrote:

Hi folks,

When I connect with PV5 (self-compiled from source) running on OS X to a pvserver on a remote Linux machine, I have problems using the ?Export scene? feature. Whenever I try to save the current scene e.g. as PDF or EPS, the visualization object (in this case a 2D unstructured dataset) flickers on and off for 2-3 times and then stays hidden. When I look at the generated PDF/EPS, indeed, the object is not there either. I can make it reappear in PV if I hide-unhide the object in the pipeline browser, but of course this does not help with the exported file. Strangely enough, the color bar is not affected, i.e., in the exported PDF/EPS file I end up with a lonely color bar on an otherwise empty grey background.

Any idea what I have to do to be able to again create EPS/PDF files?

Thanks a lot in advance

Michael


--
Michael Schlottke-Lakemper

Chair of Fluid Mechanics and Institute of Aerodynamics
RWTH Aachen University
W?llnerstra?e 5a
52062 Aachen
Germany

Phone: +49 (241) 80 95188
Fax: +49 (241) 80 92257
Mail: m.schlottke-lakemper at aia.rwth-aachen.de<mailto:m.schlottke-lakemper at aia.rwth-aachen.de>
Web: http://www.aia.rwth-aachen.de<http://www.aia.rwth-aachen.de/>


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160422/e029259c/attachment.html>

From dkxls23 at gmail.com  Fri Apr 22 11:00:36 2016
From: dkxls23 at gmail.com (Armin Wehrfritz)
Date: Fri, 22 Apr 2016 18:00:36 +0300
Subject: [Paraview] Export scene creates images without actual object
In-Reply-To: <6D6C2BF3-F871-4A25-8C13-0768B37E83E3@aia.rwth-aachen.de>
References: <6D6C2BF3-F871-4A25-8C13-0768B37E83E3@aia.rwth-aachen.de>
Message-ID: <571A3C94.7070205@gmail.com>

IIRC there was problem with "Export Scene" and the new OpenGL2 backend.
This has been discussed on the mailing-list several times, see e.g.:
https://www.mail-archive.com/paraview at paraview.org/msg25912.html

Hope this helps!

-Armin




On 04/19/2016 10:53 AM, Schlottke-Lakemper, Michael wrote:
> Hi folks,
>
> When I connect with PV5 (self-compiled from source) running on OS X to a
> pvserver on a remote Linux machine, I have problems using the ?Export
> scene? feature. Whenever I try to save the current scene e.g. as PDF or
> EPS, the visualization object (in this case a 2D unstructured dataset)
> flickers on and off for 2-3 times and then stays hidden. When I look at
> the generated PDF/EPS, indeed, the object is not there either. I can
> make it reappear in PV if I hide-unhide the object in the pipeline
> browser, but of course this does not help with the exported file.
> Strangely enough, the color bar is not affected, i.e., in the exported
> PDF/EPS file I end up with a lonely color bar on an otherwise empty grey
> background.
>
> Any idea what I have to do to be able to again create EPS/PDF files?
>
> Thanks a lot in advance
>
> Michael
>
>
> --
> Michael Schlottke-Lakemper
>
> Chair of Fluid Mechanics and Institute of Aerodynamics
> RWTH Aachen University
> W?llnerstra?e 5a
> 52062 Aachen
> Germany
>
> Phone: +49 (241) 80 95188
> Fax: +49 (241) 80 92257
> Mail: m.schlottke-lakemper at aia.rwth-aachen.de
> <mailto:m.schlottke-lakemper at aia.rwth-aachen.de>
> Web: http://www.aia.rwth-aachen.de
>
>
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview
>

From m.schlottke-lakemper at aia.rwth-aachen.de  Fri Apr 22 11:51:34 2016
From: m.schlottke-lakemper at aia.rwth-aachen.de (Schlottke-Lakemper, Michael)
Date: Fri, 22 Apr 2016 15:51:34 +0000
Subject: [Paraview] Export scene creates images without actual object
In-Reply-To: <571A3C94.7070205@gmail.com>
References: <6D6C2BF3-F871-4A25-8C13-0768B37E83E3@aia.rwth-aachen.de>,
 <571A3C94.7070205@gmail.com>
Message-ID: <10b6d83b23e74b7189e3add9c9a5072f@rwthex-w1-a.rwth-ad.de>

Hi Armin, 

Thanks for the hint! We are using the legacy OpenGL backend client-side. Server-side I don't know since it was pre-installed on the system I'm using. Is there a way for me to check how the pvserver was compiled or is it only dependent on the client anyways? 

Michael 
________________________________________
From: Armin Wehrfritz [dkxls23 at gmail.com]
Sent: Friday, April 22, 2016 5:00 PM
To: Schlottke-Lakemper, Michael; ParaView
Subject: Re: [Paraview] Export scene creates images without actual object

IIRC there was problem with "Export Scene" and the new OpenGL2 backend.
This has been discussed on the mailing-list several times, see e.g.:
https://www.mail-archive.com/paraview at paraview.org/msg25912.html

Hope this helps!

-Armin




On 04/19/2016 10:53 AM, Schlottke-Lakemper, Michael wrote:
> Hi folks,
>
> When I connect with PV5 (self-compiled from source) running on OS X to a
> pvserver on a remote Linux machine, I have problems using the ?Export
> scene? feature. Whenever I try to save the current scene e.g. as PDF or
> EPS, the visualization object (in this case a 2D unstructured dataset)
> flickers on and off for 2-3 times and then stays hidden. When I look at
> the generated PDF/EPS, indeed, the object is not there either. I can
> make it reappear in PV if I hide-unhide the object in the pipeline
> browser, but of course this does not help with the exported file.
> Strangely enough, the color bar is not affected, i.e., in the exported
> PDF/EPS file I end up with a lonely color bar on an otherwise empty grey
> background.
>
> Any idea what I have to do to be able to again create EPS/PDF files?
>
> Thanks a lot in advance
>
> Michael
>
>
> --
> Michael Schlottke-Lakemper
>
> Chair of Fluid Mechanics and Institute of Aerodynamics
> RWTH Aachen University
> W?llnerstra?e 5a
> 52062 Aachen
> Germany
>
> Phone: +49 (241) 80 95188
> Fax: +49 (241) 80 92257
> Mail: m.schlottke-lakemper at aia.rwth-aachen.de
> <mailto:m.schlottke-lakemper at aia.rwth-aachen.de>
> Web: http://www.aia.rwth-aachen.de
>
>
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview
>

From dkxls23 at gmail.com  Fri Apr 22 12:39:38 2016
From: dkxls23 at gmail.com (Armin Wehrfritz)
Date: Fri, 22 Apr 2016 19:39:38 +0300
Subject: [Paraview] Export scene creates images without actual object
In-Reply-To: <10b6d83b23e74b7189e3add9c9a5072f@rwthex-w1-a.rwth-ad.de>
References: <6D6C2BF3-F871-4A25-8C13-0768B37E83E3@aia.rwth-aachen.de>
 <571A3C94.7070205@gmail.com>
 <10b6d83b23e74b7189e3add9c9a5072f@rwthex-w1-a.rwth-ad.de>
Message-ID: <571A53CA.3040602@gmail.com>

> Thanks for the hint! We are using the legacy OpenGL backend
> client-side. Server-side I don't know since it was pre-installed on
> the system I'm using. Is there a way for me to check how the pvserver
> was compiled or is it only dependent on the client anyways?
I don't know how to check for the OpenGL backend on the server. Neither
do I know if that would effect the "export scene" feature.
Where is the rendering done, server-side or client-side?

If you know that your client is compiled with the old OpenGL backend,
you could enforce the rendering on the client and see if that works. To
do that you have to adjust the remote rendering threshold in the settings.

-Armin

From m.schlottke-lakemper at aia.rwth-aachen.de  Sat Apr 23 00:40:45 2016
From: m.schlottke-lakemper at aia.rwth-aachen.de (Schlottke-Lakemper, Michael)
Date: Sat, 23 Apr 2016 04:40:45 +0000
Subject: [Paraview] Export scene creates images without actual object
In-Reply-To: <571A53CA.3040602@gmail.com>
References: <6D6C2BF3-F871-4A25-8C13-0768B37E83E3@aia.rwth-aachen.de>
 <571A3C94.7070205@gmail.com>
 <10b6d83b23e74b7189e3add9c9a5072f@rwthex-w1-a.rwth-ad.de>
 <571A53CA.3040602@gmail.com>
Message-ID: <E869C03C-22BC-4CDD-B94C-FEC27D08B819@aia.rwth-aachen.de>

Hi Armin,

I tried your suggestion and set the remote rendering threshold to the maximum value. This yielded the following error server-side, after which ParaView seemed to hang forever:

ERROR: In /dev/shm/domini/ParaView/5.0.1/intel-para-2015.07-OSMesa/ParaView-v5.0.1-source/VTK/Common/ExecutionModel/vtkExecutive.cxx, line 784
vtkCompositeDataPipeline (0x8adda30): Algorithm vtkAppendCompositeDataLeaves(0x8ae4bc0) returned failure for request: vtkInformation (0x8d42fe0)
  Debug: Off
  Modified Time: 15698004
  Reference Count: 1
  Registered Events: (none)
  Request: REQUEST_DATA_OBJECT
  ALGORITHM_AFTER_FORWARD: 1
  FORWARD_DIRECTION: 0
  FROM_OUTPUT_PORT: 0

Warning: In /dev/shm/domini/ParaView/5.0.1/intel-para-2015.07-OSMesa/ParaView-v5.0.1-source/VTK/Common/DataModel/vtkDataObject.cxx, line 522
vtkMultiBlockDataSet (0x8e5f760): Attempted to ShallowCopy from null.

Then I connected to a ParaView server on another host, where I know for sure that the OpenGL backend is used. Unfortunately, the error with the empty ?Export scene?? results persisted, so it seems like it?s not an issue with OpenGL2. Any other ideas where this could come from?

Regards,

Michael


> On 22 Apr 2016, at 18:39 , Armin Wehrfritz <dkxls23 at gmail.com> wrote:
> 
>> Thanks for the hint! We are using the legacy OpenGL backend
>> client-side. Server-side I don't know since it was pre-installed on
>> the system I'm using. Is there a way for me to check how the pvserver
>> was compiled or is it only dependent on the client anyways?
> I don't know how to check for the OpenGL backend on the server. Neither
> do I know if that would effect the "export scene" feature.
> Where is the rendering done, server-side or client-side?
> 
> If you know that your client is compiled with the old OpenGL backend,
> you could enforce the rendering on the client and see if that works. To
> do that you have to adjust the remote rendering threshold in the settings.
> 
> -Armin


From dave.demarle at kitware.com  Sat Apr 23 09:07:14 2016
From: dave.demarle at kitware.com (David E DeMarle)
Date: Sat, 23 Apr 2016 09:07:14 -0400
Subject: [Paraview] peak memory use on remote nodes
In-Reply-To: <CANjZAi_VRri2cG2o1zTt+EzRAX4prHhV+dhPD-tB3L+BvWfFdg@mail.gmail.com>
References: <50320452A334BD42A5EC72BAD21450993DF0BFA8@MBX210.d.ethz.ch>
 <CANjZAi-nS+tT0EDTz-UMS=6VGNe4F0LewZ-E1mucAcpMgqhpWw@mail.gmail.com>
 <50320452A334BD42A5EC72BAD21450993DF0E1CD@MBX210.d.ethz.ch>
 <50320452A334BD42A5EC72BAD21450993DF11A4E@MBX210.d.ethz.ch>
 <CANjZAi_VRri2cG2o1zTt+EzRAX4prHhV+dhPD-tB3L+BvWfFdg@mail.gmail.com>
Message-ID: <CANjZAi_JokxPZ5pPMyCbqdcDVp8sAbbizVpjoC5p-8NqB57+BQ@mail.gmail.com>

Sorry I've got no insight on this.
On Apr 21, 2016 6:29 AM, "Biddiscombe, John A." <biddisco at cscs.ch> wrote:

Dave



So it turns out that aprun/alps won?t let me run a script with dstat to
monitor the memory use, and using craypat makes the execution take too long
(weeks it seems). So I tried importing part of the dstat python into my
paraview python



Using this I am able to query memory use on the node and dump it out.



Question :  If I start a background python thread that polls memory like
this



#####################

# start a thread that prints mem use

#####################

def dump_memory():

    # do something here ...

    global stop_thread

    line = ''

    for o in stats:

        o.extract()

        line = line + '  ' + o.show()

    print line + dstat.ansi['reset']



    # call f() again in n seconds

    if stop_thread==0:

      threading.Timer(0.5, dump_memory).start()





and set it going at the start of my paraview python pipeline : Will it
actually run and collect info whilst the paraview script is executing the
rest of the pipeline.



intuition and brief googling tells me that this won?t work.



Can it be done?



JB



*From:* ParaView [mailto:paraview-bounces at paraview.org] *On Behalf Of
*Biddiscombe,
John A.
*Sent:* 18 April 2016 14:53
*To:* David E DeMarle

*Cc:* paraview at paraview.org
*Subject:* Re: [Paraview] peak memory use on remote nodes



Thanks Dave



A colleague here suggested I put my

aprun pvbatch <blah> into a script and add a ?dtrace? command at the start
of the script. This will then dump out a txt file on each node and after
the job completes I can grep the info I need.



I?m going to give that a try first as it seems straightforward, but I will
revert to your suggestion if I fail and nothing else comes up.



cheers



JB



*From:* David E DeMarle [mailto:dave.demarle at kitware.com
<dave.demarle at kitware.com>]
*Sent:* 18 April 2016 14:48
*To:* Biddiscombe, John A.
*Cc:* paraview at paraview.org
*Subject:* Re: [Paraview] peak memory use on remote nodes



Perhaps extend the benchmark to glean /proc/<PID>/status's VmHWM entry on
Linux at least. Get the number for t1 and at t2 and subtract to see what
the maximum was in between those two times.

Seems the right place to do that is kwsys/SystemInformation.cxx, but you
could prototype in the script.

Hope that helps and please post some code. Seems like a very useful thing
to have.




David E DeMarle
Kitware, Inc.
R&D Engineer
21 Corporate Drive
Clifton Park, NY 12065-8662
Phone: 518-881-4909



On Mon, Apr 18, 2016 at 2:42 AM, Biddiscombe, John A. <biddisco at cscs.ch>
wrote:

The python scripting module ?paraview.benchmark? allows one to get the
memory use using ?paraview.benchmark.get_memuse? - but I presume this is
the memory reported as used by the system at the moment when the function
is called.



Does anyone know a way of recording the peak memory use on remote nodes
between t1 and t2 - where t1 and t2 are the start and stop of either a
function, job or even paraview python script on the remote node?



thanks



JB



-- 

John Biddiscombe,                        email:biddisco @.at.@ cscs.ch

http://www.cscs.ch/

CSCS, Swiss National Supercomputing Centre  | Tel:  +41 (91) 610.82.07

Via Trevano 131, 6900 Lugano, Switzerland   | Fax:  +41 (91) 610.82.82




_______________________________________________
Powered by www.kitware.com

Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at:
http://paraview.org/Wiki/ParaView

Search the list archives at: http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160423/7eaa56f1/attachment.html>

From benson.muite at ut.ee  Sat Apr 23 12:44:11 2016
From: benson.muite at ut.ee (Benson Muite)
Date: Sat, 23 Apr 2016 19:44:11 +0300
Subject: [Paraview] ISC 2016 Workshop on in-situ visualization
Message-ID: <0808ca99-7388-1956-fbf8-979aaf441472@ut.ee>

If you have interesting work which uses in-situ visualization, consider
submitting a talk for the forthcoming workshop at the ISC conference in
Frankfurt on 23 June. For more information please see:
http://woiv.org/
http://www.isc-hpc.com/workshops.html

Steffen Frey, Benson Muite and Guido Reina


From KSheldon at slb.com  Sat Apr 23 12:51:37 2016
From: KSheldon at slb.com (Ken Sheldon)
Date: Sat, 23 Apr 2016 16:51:37 +0000
Subject: [Paraview] Time Variables in CF Conventions
Message-ID: <2911E772881F8B4AB39462AA4A35EC55017B890981@NL0230MBX12N2.DIR.slb.com>

I am trying to read a CF Conventions NetCDF file  (Sea Surface Temperature from NOAA).
The CF reader in ParaView recognizes the axes and the data correctly.  However, it does not seem to recognize the TIME dimension.

Is anyone here reading CF (Climate Forecasting) files successfully?


Reference: http://www.class.ngdc.noaa.gov/saa/products/search?datatype_family=SST14NA

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160423/96fcc814/attachment.html>

From Jun.Zhang at ed.ac.uk  Sat Apr 23 17:42:55 2016
From: Jun.Zhang at ed.ac.uk (Jun Zhang)
Date: Sat, 23 Apr 2016 22:42:55 +0100
Subject: [Paraview] Errors in find data using paraview 4.1
Message-ID: <20160423224255.11693tdgb7c578mc@www.staffmail.ed.ac.uk>

Hi All

I am using Paraview 4.1 which is installed with OpenFOAM on Ubuntu  
12.04. Basically, Paraview works well. However, when I try to use  
"find data" to extract something, the errors come out like this:

Traceback (most recent call last):
   File "<string>", line 1, in <module>
   File  
"/home/jun/OpenFOAM/ThirdParty-2.4.0/platforms/linux64GccMNF/ParaView-4.1.0/lib/paraview-4.1/site-packages/paraview/extract_selection.py", line 19, in  
<module>
     from paraview.vtk import dataset_adapter
   File  
"/home/jun/OpenFOAM/ThirdParty-2.4.0/platforms/linux64GccMNF/ParaView-4.1.0/lib/paraview-4.1/site-packages/paraview/vtk/dataset_adapter.py", line 5, in  
<module>
     sure that it is installed properly.")
RuntimeError: This module depends on the numpy module. Please makesure  
that it is installed properly.

Anyone knows how to solve this problem? Highly appreciated.

Best,
Jun



-- 
The University of Edinburgh is a charitable body, registered in
Scotland, with registration number SC005336.



From cgunases at gmail.com  Sat Apr 23 19:54:03 2016
From: cgunases at gmail.com (Chathuri Gunasekera)
Date: Sun, 24 Apr 2016 05:24:03 +0530
Subject: [Paraview] (no subject)
Message-ID: <CAJFKOL0JiXon7DYvUCzT2TRA2wx6nq7H6tAgHpZ3oENa_auH1w@mail.gmail.com>

Hi,

I want to install  Paraview and i cannot find a video abt installing
paraview on windows 8. i cannot find a proper one.pls  help.

-- 
Warm regards,
Chathuri Gunasekera.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160424/b621ecd8/attachment.html>

From cory.quammen at kitware.com  Sun Apr 24 11:07:56 2016
From: cory.quammen at kitware.com (Cory Quammen)
Date: Sun, 24 Apr 2016 11:07:56 -0400
Subject: [Paraview] (no subject)
In-Reply-To: <CAJFKOL0JiXon7DYvUCzT2TRA2wx6nq7H6tAgHpZ3oENa_auH1w@mail.gmail.com>
References: <CAJFKOL0JiXon7DYvUCzT2TRA2wx6nq7H6tAgHpZ3oENa_auH1w@mail.gmail.com>
Message-ID: <CAB5Fpx4vJhHs5gtzE-+-2J_YZ6LoxGOM6CYDVz9WcrwJOj2Q9w@mail.gmail.com>

Hi,

Installing on Windows 8 should be very easy.

Please visit

http://www.paraview.org/download/

choose the appropriate installer, download it, and double click the
installation program. Click through the installer, and it should be
all set up.

Hope that helps,
Cory

On Sat, Apr 23, 2016 at 7:54 PM, Chathuri Gunasekera <cgunases at gmail.com> wrote:
> Hi,
>
> I want to install  Paraview and i cannot find a video abt installing
> paraview on windows 8. i cannot find a proper one.pls  help.
>
> --
> Warm regards,
> Chathuri Gunasekera.
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview
>



-- 
Cory Quammen
R&D Engineer
Kitware, Inc.

From utkarsh.ayachit at kitware.com  Sun Apr 24 11:43:07 2016
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Sun, 24 Apr 2016 08:43:07 -0700
Subject: [Paraview] Errors in find data using paraview 4.1
In-Reply-To: <20160423224255.11693tdgb7c578mc@www.staffmail.ed.ac.uk>
References: <20160423224255.11693tdgb7c578mc@www.staffmail.ed.ac.uk>
Message-ID: <CADHSJjB69d3eu-_cPzF1zMRTEJ-m4AEiMaZdRkV70c_3672quQ@mail.gmail.com>

This seems to be an issue with the ParaView build in OpenFOAM. It's
not packaging numpy. Alternatively, if it's using system installed
Python, you will need to install numpy on your local Python
installation.

On Sat, Apr 23, 2016 at 2:42 PM, Jun Zhang <Jun.Zhang at ed.ac.uk> wrote:
> Hi All
>
> I am using Paraview 4.1 which is installed with OpenFOAM on Ubuntu 12.04.
> Basically, Paraview works well. However, when I try to use "find data" to
> extract something, the errors come out like this:
>
> Traceback (most recent call last):
>   File "<string>", line 1, in <module>
>   File
> "/home/jun/OpenFOAM/ThirdParty-2.4.0/platforms/linux64GccMNF/ParaView-4.1.0/lib/paraview-4.1/site-packages/paraview/extract_selection.py",
> line 19, in <module>
>     from paraview.vtk import dataset_adapter
>   File
> "/home/jun/OpenFOAM/ThirdParty-2.4.0/platforms/linux64GccMNF/ParaView-4.1.0/lib/paraview-4.1/site-packages/paraview/vtk/dataset_adapter.py",
> line 5, in <module>
>     sure that it is installed properly.")
> RuntimeError: This module depends on the numpy module. Please makesure that
> it is installed properly.
>
> Anyone knows how to solve this problem? Highly appreciated.
>
> Best,
> Jun
>
>
>
> --
> The University of Edinburgh is a charitable body, registered in
> Scotland, with registration number SC005336.
>
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview

From Jun.Zhang at ed.ac.uk  Sun Apr 24 12:34:52 2016
From: Jun.Zhang at ed.ac.uk (Jun Zhang)
Date: Sun, 24 Apr 2016 17:34:52 +0100
Subject: [Paraview] Errors in find data using paraview 4.1
In-Reply-To: <CADHSJjB69d3eu-_cPzF1zMRTEJ-m4AEiMaZdRkV70c_3672quQ@mail.gmail.com>
References: <20160423224255.11693tdgb7c578mc@www.staffmail.ed.ac.uk>
 <CADHSJjB69d3eu-_cPzF1zMRTEJ-m4AEiMaZdRkV70c_3672quQ@mail.gmail.com>
Message-ID: <20160424173452.7401682qwbi2kyi5@www.staffmail.ed.ac.uk>

Hi Utkarsh

Thanks for your explanation.

Could you please tell me how to install numpy on my local Python  
installation in details?

Many thanks,
Jun

Quoting Utkarsh Ayachit <utkarsh.ayachit at kitware.com> on Sun, 24 Apr  
2016 08:43:07 -0700:

> This seems to be an issue with the ParaView build in OpenFOAM. It's
> not packaging numpy. Alternatively, if it's using system installed
> Python, you will need to install numpy on your local Python
> installation.
>
> On Sat, Apr 23, 2016 at 2:42 PM, Jun Zhang <Jun.Zhang at ed.ac.uk> wrote:
>> Hi All
>>
>> I am using Paraview 4.1 which is installed with OpenFOAM on Ubuntu 12.04.
>> Basically, Paraview works well. However, when I try to use "find data" to
>> extract something, the errors come out like this:
>>
>> Traceback (most recent call last):
>>   File "<string>", line 1, in <module>
>>   File
>> "/home/jun/OpenFOAM/ThirdParty-2.4.0/platforms/linux64GccMNF/ParaView-4.1.0/lib/paraview-4.1/site-packages/paraview/extract_selection.py",
>> line 19, in <module>
>>     from paraview.vtk import dataset_adapter
>>   File
>> "/home/jun/OpenFOAM/ThirdParty-2.4.0/platforms/linux64GccMNF/ParaView-4.1.0/lib/paraview-4.1/site-packages/paraview/vtk/dataset_adapter.py",
>> line 5, in <module>
>>     sure that it is installed properly.")
>> RuntimeError: This module depends on the numpy module. Please makesure that
>> it is installed properly.
>>
>> Anyone knows how to solve this problem? Highly appreciated.
>>
>> Best,
>> Jun
>>
>>
>>
>> --
>> The University of Edinburgh is a charitable body, registered in
>> Scotland, with registration number SC005336.
>>
>>
>> _______________________________________________
>> Powered by www.kitware.com
>>
>> Visit other Kitware open-source projects at
>> http://www.kitware.com/opensource/opensource.html
>>
>> Please keep messages on-topic and check the ParaView Wiki at:
>> http://paraview.org/Wiki/ParaView
>>
>> Search the list archives at: http://markmail.org/search/?q=ParaView
>>
>> Follow this link to subscribe/unsubscribe:
>> http://public.kitware.com/mailman/listinfo/paraview
>
>


-- 
Jun Zhang
Research Associate
School of Engineering, University of Edinburgh

-- 
The University of Edinburgh is a charitable body, registered in
Scotland, with registration number SC005336.



From mgammar at outlook.fr  Mon Apr 25 03:33:36 2016
From: mgammar at outlook.fr (Marwen Gammar)
Date: Mon, 25 Apr 2016 09:33:36 +0200
Subject: [Paraview] Few details i don't know
Message-ID: <BAY182-W749B618AA1A60EBB5B305FD1620@phx.gbl>

Thank you for your quick answer, however i am afraid i wasn't explicit in my questions:For the first point, yes, i knew that, but when i create 3d text, it is always in the same place,i can't put words in each face of my cube for example,For the second point, i wasn't talking about applying text with Paraview but directly with the Vtk programm i wrote ( i think it could be more simple for me than if i always use the 3d text program)Here is my programm:# vtk DataFile Version 2.0 Cube example ASCII DATASET POLYDATA POINTS 8 float 0.0 0.0 0.01.0 0.0 0.01.0 1.0 0.00.0 1.0 0.00.0 0.0 1.01.0 0.0 1.01.0 1.0 1.00.0 1.0 1.0POLYGONS 6 30 4 0 1 2 3 4 4 5 6 7 4 0 1 5 4 4 2 3 7 6 4 0 4 7 3 4 1 2 6 5CELL_DATA 6 SCALARS cell_scalars int 1 LOOKUP_TABLE default 0 1 2 3 4 5 NORMALS cell_normals float0 0 -1 0 0 1 0 -1 0 0 1 0 -1 0 0 1 0 0 FIELD FieldData 2 cellIds 1 6 int 012345 faceAttributes 2 6 float 0.0 1.0 1.0 2.0 2.0 3.0 3.0 4.0 4.0 5.0 5.0 6.0POINT_DATA 8 SCALARS sample_scalars float 1 LOOKUP_TABLE my_table 0.01.02.03.04.05.06.07.0LOOKUP_TABLE my_table 8 0.0 0.0 0.0 1.01.0 0.0 0.0 1.00.0 1.0 0.0 1.01.0 1.0 0.0 1.00.0 0.0 1.0 1.01.0 0.0 1.0 1.00.0 1.0 1.0 1.01.0 1.0 1.0 1.0i want to apply a text directly on each face from this programm which will be read by Paraview.
And is the time annotation only linear? (Can't i use for example time annotation with logarythm?)Thank you very much for help,Kind regards,Marwen 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160425/e83110e0/attachment.html>

From kaiwinter212 at gmail.com  Mon Apr 25 11:41:24 2016
From: kaiwinter212 at gmail.com (Kai Winter)
Date: Mon, 25 Apr 2016 17:41:24 +0200
Subject: [Paraview] Parallel rendering including transparency
Message-ID: <CAJm-X2CDAVpkwqobXwHAWHAaU0gLz-egnWY+OGEeVTL33QrpZw@mail.gmail.com>

Hello,
is it possible to extend the example at
http://www.vtk.org/Wiki/VTK/MultiPass_Rendering_With_IceT for parallel
rendering including transparent objects?

I have tried to modify the above example by first setting
  actor->GetProperty()->SetOpacity(0.3);
after creation of the actor, and, second, adding
  vtkSmartPointer<vtkTranslucentPass> translucent =
vtkSmartPointer<vtkTranslucentPass>::New();
  passes->AddItem(translucent);
after the original line "passes->AddItem(opaque);".

The result is for example, when running with 3 MPI processes:
The sphere segments in the partial Renderers of process 1 and 2 are
transparent (but show some artefacts).
The composite Renderer of process 0 doesn't show any sphere, just the black
background!
When the opacity is set to 1, the sphere segments are composited in three
colors on process 0 as expected.

What is required to correctly perform parallel rendering including
transparency?
(I am using ParaView-v5.0.1, compiled from source on Ubuntu 15.04)

Thank you
Kai
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160425/f4a78861/attachment.html>

From adlinds3 at ncsu.edu  Mon Apr 25 13:16:28 2016
From: adlinds3 at ncsu.edu (Alex Lindsay)
Date: Mon, 25 Apr 2016 13:16:28 -0400
Subject: [Paraview] Reduce significant figures in time display
Message-ID: <571E50EC.2030002@ncsu.edu>

Is there a way to reduce the number of significant figures in the time 
display? I can't see the exponential component of my scientific notation 
which makes it rather difficult to know where I actually am in my 
simulation.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160425/416915ab/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: diajbeea.png
Type: image/png
Size: 43108 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160425/416915ab/attachment.png>

From adlinds3 at ncsu.edu  Mon Apr 25 13:34:29 2016
From: adlinds3 at ncsu.edu (Alex Lindsay)
Date: Mon, 25 Apr 2016 13:34:29 -0400
Subject: [Paraview] Change default color mapping
Message-ID: <571E5525.7080801@ncsu.edu>

Is there a way to change the default color mapping? The default is cool 
to warm, but I prefer blue to red rainbow. I saw in the manual 
directions for customizing properties, sources, filter, etc, but I think 
I need a little more help

From dkxls23 at gmail.com  Mon Apr 25 13:44:36 2016
From: dkxls23 at gmail.com (Armin Wehrfritz)
Date: Mon, 25 Apr 2016 20:44:36 +0300
Subject: [Paraview] Change default color mapping
In-Reply-To: <571E5525.7080801@ncsu.edu>
References: <571E5525.7080801@ncsu.edu>
Message-ID: <571E5784.6050206@gmail.com>

There are there buttons at the bottom of the Color Map Editor panel that
let you save or load the default settings.

-Armin





On 04/25/2016 08:34 PM, Alex Lindsay wrote:
> Is there a way to change the default color mapping? The default is cool
> to warm, but I prefer blue to red rainbow. I saw in the manual
> directions for customizing properties, sources, filter, etc, but I think
> I need a little more help
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview

From cory.quammen at kitware.com  Mon Apr 25 13:56:10 2016
From: cory.quammen at kitware.com (Cory Quammen)
Date: Mon, 25 Apr 2016 13:56:10 -0400
Subject: [Paraview] Reduce significant figures in time display
In-Reply-To: <571E50EC.2030002@ncsu.edu>
References: <571E50EC.2030002@ncsu.edu>
Message-ID: <CAB5Fpx4oSsRjTsU04R-xkf8Yy3FLvNSFumbO+tcM3k_3+_eM3g@mail.gmail.com>

Alex,

I do not believe this is user customizable.

Cory

On Mon, Apr 25, 2016 at 1:16 PM, Alex Lindsay <adlinds3 at ncsu.edu> wrote:

> Is there a way to reduce the number of significant figures in the time
> display? I can't see the exponential component of my scientific notation
> which makes it rather difficult to know where I actually am in my
> simulation.
>
>
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview
>
>


-- 
Cory Quammen
R&D Engineer
Kitware, Inc.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160425/8ad3408a/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: diajbeea.png
Type: image/png
Size: 43108 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160425/8ad3408a/attachment.png>

From adlinds3 at ncsu.edu  Mon Apr 25 14:21:24 2016
From: adlinds3 at ncsu.edu (Alex Lindsay)
Date: Mon, 25 Apr 2016 14:21:24 -0400
Subject: [Paraview] Reduce significant figures in time display
In-Reply-To: <CAB5Fpx4oSsRjTsU04R-xkf8Yy3FLvNSFumbO+tcM3k_3+_eM3g@mail.gmail.com>
References: <571E50EC.2030002@ncsu.edu>
 <CAB5Fpx4oSsRjTsU04R-xkf8Yy3FLvNSFumbO+tcM3k_3+_eM3g@mail.gmail.com>
Message-ID: <571E6024.5020902@ncsu.edu>

That's a bummer. I believe in version 4 the time display only showed a 
few sig figs which worked better for me. I wish I could combine my 
favorite features of versions 4 and 5

On 04/25/2016 01:56 PM, Cory Quammen wrote:
> Alex,
>
> I do not believe this is user customizable.
>
> Cory
>
> On Mon, Apr 25, 2016 at 1:16 PM, Alex Lindsay <adlinds3 at ncsu.edu 
> <mailto:adlinds3 at ncsu.edu>> wrote:
>
>     Is there a way to reduce the number of significant figures in the
>     time display? I can't see the exponential component of my
>     scientific notation which makes it rather difficult to know where
>     I actually am in my simulation.
>
>
>
>     _______________________________________________
>     Powered by www.kitware.com <http://www.kitware.com>
>
>     Visit other Kitware open-source projects at
>     http://www.kitware.com/opensource/opensource.html
>
>     Please keep messages on-topic and check the ParaView Wiki at:
>     http://paraview.org/Wiki/ParaView
>
>     Search the list archives at: http://markmail.org/search/?q=ParaView
>
>     Follow this link to subscribe/unsubscribe:
>     http://public.kitware.com/mailman/listinfo/paraview
>
>
>
>
> -- 
> Cory Quammen
> R&D Engineer
> Kitware, Inc.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160425/49c15605/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 43108 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160425/49c15605/attachment.png>

From CBaumann at slb.com  Mon Apr 25 14:16:30 2016
From: CBaumann at slb.com (Carlos Baumann)
Date: Mon, 25 Apr 2016 18:16:30 +0000
Subject: [Paraview] Paraview not using normals data when rendering
	WarpByVector
Message-ID: <32D0A6E400786141A9A2CB170C1CF1EC01DD46C71E@NL0230MBX07N1.DIR.slb.com>

Hello Paraview !

The attached .vtk file has quad elements defining a tube,
for each point or node it has defined a scalar Pressure, and two vectors, Displacement and Normals.

When I render "Displacement Magnitude" on the surface, the normal are used, this is perfect and this is what I want, see attached snapshot,

However when I use WarpByVector to deform the geometry, and plotting "Displacement Magnitude" on the surface, the normals are not used,
each element uses its own normal, and I see the facets.  How can I change this so that the normals that I have defined in the .vtk file are used ?

Ideally I would want Paraview to use the normal at any point/node by averaging the normal of all the elements attached, weighted by the area,
can this be done automatically with GUI settings ?

Thank you in advance for your help.

Regards,
Carlos





-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160425/a82184fa/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: NormalUsedOK.gif
Type: image/gif
Size: 57359 bytes
Desc: NormalUsedOK.gif
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160425/a82184fa/attachment-0002.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: NormalNotUsed.gif
Type: image/gif
Size: 56450 bytes
Desc: NormalNotUsed.gif
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160425/a82184fa/attachment-0003.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: test.vtk
Type: application/octet-stream
Size: 19899 bytes
Desc: test.vtk
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160425/a82184fa/attachment-0001.obj>

From M.Deij at marin.nl  Tue Apr 26 03:49:07 2016
From: M.Deij at marin.nl (Deij-van Rijswijk, Menno)
Date: Tue, 26 Apr 2016 07:49:07 +0000
Subject: [Paraview] ParaView Catalyst - AttributeError when pipeline is
	evaluated
Message-ID: <25fdd061a31d4c6b94654e3bedf00290@MAR190n2.marin.local>

Hi,

I?m using a Catalyst interface to our in-house CFD simulation (distributed by MPI) and I?m running into problems when the pipeline is evaluated. The ParaView libraries, linked to our simulation code, have been built with OSMesa, MPI, Python. I built the full ParaView, not a Catalyst Edition.

The analysis pipeline that has to run during the simulation has been built with PV 5.0.1 and was saved using the CoProcessing Generator Script plug-in. As far as I can see, this plug-in wraps what is normally in the python state file into the co-processing script: the _CreatePipeline function is 1-to-1 the same as when I write the Python state file.

I get the following errors during the evaluation of the pipeline, and no images are saved:

>>>
AttributeError: Attribute ScalarOpacityUnitDistance does not exist.  This class does not allow addition of new attributes to avoid mistakes due to typos. Use add_attribute() if you really want to add this attribute.
<<<

And similar attribute errors for SetScaleArray, OpacityArray, ScaleTransferFunction and OpacityTransferFunction. If I want to get it working, I have to comment out all calls to these attributes.

Any clues on why this is happening? I have searched the PV codebase for these but could not find anything to go on, except that some of these attributes seem to relate to volume rendering, even though I have Module_vtkRenderingVolumeOpenGL=ON. Maybe there is some other switch in the CMake configuration that I have to set to get rid of the errors?

Thanks and best wishes,


Menno Deij ? van Rijswijk



dr. ir. Menno A. Deij-van Rijswijk  | Researcher / Software Engineer | Maritime Simulation & Software Group
MARIN | T +31 317 49 35 06 | mailto:M.Deij at marin.nl | http://www.marin.nl

MARIN news: http://www.marin.nl/web/News/News-items/MARIN-Report-117-Maintenance-and-life-time-extensions.htm


From u.utku.turuncoglu at be.itu.edu.tr  Tue Apr 26 03:58:59 2016
From: u.utku.turuncoglu at be.itu.edu.tr (Ufuk Utku Turuncoglu (BE))
Date: Tue, 26 Apr 2016 10:58:59 +0300
Subject: [Paraview] ParaView Catalyst - AttributeError when pipeline is
 evaluated
In-Reply-To: <25fdd061a31d4c6b94654e3bedf00290@MAR190n2.marin.local>
References: <25fdd061a31d4c6b94654e3bedf00290@MAR190n2.marin.local>
Message-ID: <216ccf01-1304-1752-b841-67e417299543@be.itu.edu.tr>

Hi,

I had same problem as you and i was commenting out those lines to get 
working. Anyway, i did not find any other solution for the problem and 
there could be a bug in the co-processing.

--ufuk

On 26/04/16 10:49, Deij-van Rijswijk, Menno wrote:
> Hi,
>
> I?m using a Catalyst interface to our in-house CFD simulation (distributed by MPI) and I?m running into problems when the pipeline is evaluated. The ParaView libraries, linked to our simulation code, have been built with OSMesa, MPI, Python. I built the full ParaView, not a Catalyst Edition.
>
> The analysis pipeline that has to run during the simulation has been built with PV 5.0.1 and was saved using the CoProcessing Generator Script plug-in. As far as I can see, this plug-in wraps what is normally in the python state file into the co-processing script: the _CreatePipeline function is 1-to-1 the same as when I write the Python state file.
>
> I get the following errors during the evaluation of the pipeline, and no images are saved:
>
> AttributeError: Attribute ScalarOpacityUnitDistance does not exist.  This class does not allow addition of new attributes to avoid mistakes due to typos. Use add_attribute() if you really want to add this attribute.
> <<<
>
> And similar attribute errors for SetScaleArray, OpacityArray, ScaleTransferFunction and OpacityTransferFunction. If I want to get it working, I have to comment out all calls to these attributes.
>
> Any clues on why this is happening? I have searched the PV codebase for these but could not find anything to go on, except that some of these attributes seem to relate to volume rendering, even though I have Module_vtkRenderingVolumeOpenGL=ON. Maybe there is some other switch in the CMake configuration that I have to set to get rid of the errors?
>
> Thanks and best wishes,
>
>
> Menno Deij ? van Rijswijk
>
>
>
> dr. ir. Menno A. Deij-van Rijswijk  | Researcher / Software Engineer | Maritime Simulation & Software Group
> MARIN | T +31 317 49 35 06 | mailto:M.Deij at marin.nl | http://www.marin.nl
>
> MARIN news: http://www.marin.nl/web/News/News-items/MARIN-Report-117-Maintenance-and-life-time-extensions.htm
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview



From u.utku.turuncoglu at be.itu.edu.tr  Tue Apr 26 04:18:20 2016
From: u.utku.turuncoglu at be.itu.edu.tr (Ufuk Utku Turuncoglu (BE))
Date: Tue, 26 Apr 2016 11:18:20 +0300
Subject: [Paraview] volume rendering with Catalyst ...
Message-ID: <f137412b-ed30-44ee-7d1e-e7120f2f6a12@be.itu.edu.tr>

Hi,

I had a problem in Catalyst when i run a visualization pipeline with 
volume rendering. The attached figures shows the problem and belong to 
same visualization with and without Catalyst. In my case, the 
co-processing Python script (dvr.py) is generated from multi-block 
dataset and the Catalyst code uses MPI code to define multi-block 
dataset also. So, it is consistent in both side. The visualization 
pipeline includes Transform and MergeBlocks filters to create the final 
image and mapper is set as Bunyk Ray Cast. It seems that there is a 
problem in the color transfer function but i am not sure. I also test 
with different mapper such as projected-tetra but the result is same. I 
just wonder that did you see any similar problem before.

Regards,

Istanbul Technical University
Informatics Institute
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image_0_with_catalyst.png
Type: image/png
Size: 87389 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160426/20d2b237/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image_0_with_paraview.png
Type: image/png
Size: 119009 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160426/20d2b237/attachment-0001.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: dvr.py
Type: text/x-python-script
Size: 7020 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160426/20d2b237/attachment.bin>

From kaiwinter212 at gmail.com  Tue Apr 26 06:48:25 2016
From: kaiwinter212 at gmail.com (Kai Winter)
Date: Tue, 26 Apr 2016 12:48:25 +0200
Subject: [Paraview] Parallel rendering including transparency
In-Reply-To: <CAJm-X2CDAVpkwqobXwHAWHAaU0gLz-egnWY+OGEeVTL33QrpZw@mail.gmail.com>
References: <CAJm-X2CDAVpkwqobXwHAWHAaU0gLz-egnWY+OGEeVTL33QrpZw@mail.gmail.com>
Message-ID: <CAJm-X2CYJZr-LQaLbprsJ7xvUPVjpcLJ06C+=h3tt8O0VOspgA@mail.gmail.com>

Please, does anybody have a clue, how to correctly render transparent
objects in parallel?

I attach the modified version of
http://www.vtk.org/Wiki/VTK/MultiPass_Rendering_With_IceT and screenshots
of the render windows for MPI rank 0,1,2 (from left to right), first with
SetOpacity(1), second with SetOpacity(0.5). In the second case, you see the
artifacts in the blue segment, and (worse) that rank 0 shows a black window
instead of the composite image.

Thank you
Kai

On Mon, Apr 25, 2016 at 5:41 PM, Kai Winter <kaiwinter212 at gmail.com> wrote:

> Hello,
> is it possible to extend the example at
> http://www.vtk.org/Wiki/VTK/MultiPass_Rendering_With_IceT for parallel
> rendering including transparent objects?
>
> I have tried to modify the above example by first setting
>   actor->GetProperty()->SetOpacity(0.3);
> after creation of the actor, and, second, adding
>   vtkSmartPointer<vtkTranslucentPass> translucent =
> vtkSmartPointer<vtkTranslucentPass>::New();
>   passes->AddItem(translucent);
> after the original line "passes->AddItem(opaque);".
>
> The result is for example, when running with 3 MPI processes:
> The sphere segments in the partial Renderers of process 1 and 2 are
> transparent (but show some artefacts).
> The composite Renderer of process 0 doesn't show any sphere, just the
> black background!
> When the opacity is set to 1, the sphere segments are composited in three
> colors on process 0 as expected.
>
> What is required to correctly perform parallel rendering including
> transparency?
> (I am using ParaView-v5.0.1, compiled from source on Ubuntu 15.04)
>
> Thank you
> Kai
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160426/9e24e937/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: parallel-notransparency.png
Type: image/png
Size: 30563 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160426/9e24e937/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: parallel-opacity.png
Type: image/png
Size: 26593 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160426/9e24e937/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: MultipassParallel.cxx
Type: text/x-c++src
Size: 6523 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160426/9e24e937/attachment-0001.cxx>

From fenardi87 at gmail.com  Tue Apr 26 07:24:13 2016
From: fenardi87 at gmail.com (Federico Nardi)
Date: Tue, 26 Apr 2016 13:24:13 +0200
Subject: [Paraview] Paraview no more showing glyph
Message-ID: <571F4FDD.2070906@gmail.com>

Hi all,

I'm writing a code for Surface Reconstruction with Level-Set method and 
I use VTK to store 3D data and visualize them with Paraview. So far, 
Paraview has always worked fine, thus I can't understand why I'm having 
the following problem. As shown in the attached picture, I have a 
grid.vtp file which contains a set of points. To visualize these points, 
I used to add a Glyph filter and choose the sphere as glyph type. This 
procedure worked fine since last few days, now the screen is empty. I 
tried also with other files, and the problem seems to be the Glyph 
filter. Can you please tell me how can I solve this problem?

Thaks.
Federico
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Screenshot - 26042016 - 13:09:33.png
Type: image/png
Size: 190488 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160426/3b1c4e0a/attachment.png>

From rdjamis at sandia.gov  Tue Apr 26 09:08:53 2016
From: rdjamis at sandia.gov (Jamison, Ryan Dale)
Date: Tue, 26 Apr 2016 13:08:53 +0000
Subject: [Paraview] Plotting Global Variables Over Time - Connecting first
 and last data points?
Message-ID: <F958A5C1-FBD7-4003-BA53-76786E39F6A8@sandia.gov>

Hello All,

I was wondering if anyone has noticed that when plotting global variables over time, Paraview connects the first and last data points (see attached image)? Why does Paraview do this? Any ideas? Can the user toggle this option off?

I?m running 5.0.1 on a Mac. Thanks,

Ryan

[cid:BD88CAAB-0838-46C5-B0B6-7A43A35C5F2B at srn.sandia.gov]
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160426/291c7386/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: PastedGraphic-2.png
Type: image/png
Size: 64512 bytes
Desc: PastedGraphic-2.png
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160426/291c7386/attachment-0001.png>

From juha.jaykka at gmail.com  Tue Apr 26 08:49:09 2016
From: juha.jaykka at gmail.com (Juha =?ISO-8859-1?Q?J=E4ykk=E4?=)
Date: Tue, 26 Apr 2016 13:49:09 +0100
Subject: [Paraview] visualising a numpy array
Message-ID: <3016982.g3SsLEMJvk@vega>

Dear list,

What's the current best practice to visualise a (3D) numpy array with 
paraview? In particular, I'm wondering if 

vtkdata = numpy_support.numpy_to_vtk(num_array=NumPy_data.ravel(), deep=True, 
array_type=vtk.VTK_FLOAT)

can somehow be directly visualised? In parallel.

I'm aware of ProgrammableSource() and how to do it using that, but only from a 
file! What I'd very much like to do is avoid the file (if I cannot avoid the 
file, I'll just do xdmf and hdf5.)

Just in case it matters, the numpy array is actually not really a numpy array, 
but petsc4py.PETSc._DMDA_Vec_array which of course can be "cast" as 
numpy.ndarray.

Best regards,
Juha


From agsmith424 at gmail.com  Tue Apr 26 10:15:06 2016
From: agsmith424 at gmail.com (Andy Smith)
Date: Tue, 26 Apr 2016 10:15:06 -0400
Subject: [Paraview] Reading json colormap files in Python and exporting
	color data
Message-ID: <CA+yV-vAaQ0C88ZQJkjZkkDTVPBabTUSoBLe7Wozsjhs2k=RZxw@mail.gmail.com>

I have two questions:

1. I am trying to load colormaps in a Python script so that I have access
to the lookup table later in the script.  I have successfully used the
LoadLookupTable function with xml colormap files but this does not seem to
work on json files.  I get a parsing error:

ERROR: parsing lut file /path/to/my/colormap.json

The json colormap file loads correctly inside the GUI.  Is there another
function that I should be calling instead of LoadLookupTable or is there an
issue with this function?  Should it call a different parser based on the
file extension?

2. Is there a way to export the discretized color data?  For example, my
colormap may have seven control points in Lab space but I'd like to export
256 control points and the associated R,G,B values for use in other tools.
Alternatively, are there any ParaView Python functions that I can use to
extract R,G,B values from a colormap based on input array values?

Thanks,
Andy
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160426/9b356f9d/attachment.html>

From dennis_conklin at goodyear.com  Tue Apr 26 10:16:06 2016
From: dennis_conklin at goodyear.com (Dennis Conklin)
Date: Tue, 26 Apr 2016 14:16:06 +0000
Subject: [Paraview] Plotting Global Variables Over Time - Connecting
 first and last data points?
Message-ID: <CY1PR07MB250652A917A62213CFAED5D09F630@CY1PR07MB2506.namprd07.prod.outlook.com>

Ryan,

Not just plot over time - Plot Data does the same thing and it's equally annoying.

Dennis
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160426/e156303e/attachment.html>

From dennis_conklin at goodyear.com  Tue Apr 26 10:32:35 2016
From: dennis_conklin at goodyear.com (Dennis Conklin)
Date: Tue, 26 Apr 2016 14:32:35 +0000
Subject: [Paraview] Threshold doesn't find range of some variables
Message-ID: <CY1PR07MB2506DC0BA140A9730D80AF2F9F630@CY1PR07MB2506.namprd07.prod.outlook.com>

All,

I have a cell variable which is actually sort of a "grouping" variable.    So let's call the variable "Group".   I have 180 elements that have a value of "1",  180 elements that have a value of "2", etc.

In Paraview v5.0.1
When I click on the "Reset using current data values" arrow in Threshold, it does not change the values to reflect the range of this variable.  It just keeps the existing range.  Is it the array of many duplicate values which is confusing this?

This works in v4.4

Dennis
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160426/0d7598e6/attachment.html>

From andy.bauer at kitware.com  Tue Apr 26 12:19:39 2016
From: andy.bauer at kitware.com (Andy Bauer)
Date: Tue, 26 Apr 2016 09:19:39 -0700
Subject: [Paraview] ParaView Catalyst - AttributeError when pipeline is
	evaluated
In-Reply-To: <25fdd061a31d4c6b94654e3bedf00290@MAR190n2.marin.local>
References: <25fdd061a31d4c6b94654e3bedf00290@MAR190n2.marin.local>
Message-ID: <CAMaOp+E_cv2FCZp=Bt6SVUhZANb6bhU+H=NJKGXW0ksJW5PDGw@mail.gmail.com>

Hi,

Did you use the same version of ParaView to generate the script and for
your Catalyst build? If not, you'll want to do that. Also, you may want to
try generating the script in the PV GUI with a version of ParaView that's
using the OpenGL and NOT OpenGL2 rendering backend.

If none of that fixes things, can you share your generated Python script
and the steps you used to generate it?

Cheers,
Andy

On Tue, Apr 26, 2016 at 12:49 AM, Deij-van Rijswijk, Menno <M.Deij at marin.nl>
wrote:

> Hi,
>
> I?m using a Catalyst interface to our in-house CFD simulation (distributed
> by MPI) and I?m running into problems when the pipeline is evaluated. The
> ParaView libraries, linked to our simulation code, have been built with
> OSMesa, MPI, Python. I built the full ParaView, not a Catalyst Edition.
>
> The analysis pipeline that has to run during the simulation has been built
> with PV 5.0.1 and was saved using the CoProcessing Generator Script
> plug-in. As far as I can see, this plug-in wraps what is normally in the
> python state file into the co-processing script: the _CreatePipeline
> function is 1-to-1 the same as when I write the Python state file.
>
> I get the following errors during the evaluation of the pipeline, and no
> images are saved:
>
> >>>
> AttributeError: Attribute ScalarOpacityUnitDistance does not exist.  This
> class does not allow addition of new attributes to avoid mistakes due to
> typos. Use add_attribute() if you really want to add this attribute.
> <<<
>
> And similar attribute errors for SetScaleArray, OpacityArray,
> ScaleTransferFunction and OpacityTransferFunction. If I want to get it
> working, I have to comment out all calls to these attributes.
>
> Any clues on why this is happening? I have searched the PV codebase for
> these but could not find anything to go on, except that some of these
> attributes seem to relate to volume rendering, even though I have
> Module_vtkRenderingVolumeOpenGL=ON. Maybe there is some other switch in the
> CMake configuration that I have to set to get rid of the errors?
>
> Thanks and best wishes,
>
>
> Menno Deij ? van Rijswijk
>
>
>
> dr. ir. Menno A. Deij-van Rijswijk  | Researcher / Software Engineer |
> Maritime Simulation & Software Group
> MARIN | T +31 317 49 35 06 | mailto:M.Deij at marin.nl | http://www.marin.nl
>
> MARIN news:
> http://www.marin.nl/web/News/News-items/MARIN-Report-117-Maintenance-and-life-time-extensions.htm
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160426/b108be8e/attachment.html>

From kmorel at sandia.gov  Tue Apr 26 12:49:42 2016
From: kmorel at sandia.gov (Moreland, Kenneth)
Date: Tue, 26 Apr 2016 16:49:42 +0000
Subject: [Paraview] Paraview no more showing glyph
Message-ID: <C154AC57-1CDD-4288-BFA5-8CA9A89B5062@sandia.gov>

First, I just want to note that you appear to be using a rather old version of ParaView (4.0.1). You might consider updating to see if the problem has been solved.

I can't tell what the problem is from the information provide, but I am going to take a guess that the glyphs might be scaled too small to see. Try finding the "Scale Mode" property in the properties panel and change it to "off". Then make sure "Scale Factor" is set to something rational. (Note that because of issues like this the latest version of ParaView have the Scale Mode set to off by default.)

-Ken



On 4/26/16, 4:24 AM, "ParaView on behalf of Federico Nardi" <paraview-bounces at paraview.org on behalf of fenardi87 at gmail.com> wrote:

>Hi all,
>
>I'm writing a code for Surface Reconstruction with Level-Set method and 
>I use VTK to store 3D data and visualize them with Paraview. So far, 
>Paraview has always worked fine, thus I can't understand why I'm having 
>the following problem. As shown in the attached picture, I have a 
>grid.vtp file which contains a set of points. To visualize these points, 
>I used to add a Glyph filter and choose the sphere as glyph type. This 
>procedure worked fine since last few days, now the screen is empty. I 
>tried also with other files, and the problem seems to be the Glyph 
>filter. Can you please tell me how can I solve this problem?
>
>Thaks.
>Federico

From kmorel at sandia.gov  Tue Apr 26 13:04:53 2016
From: kmorel at sandia.gov (Moreland, Kenneth)
Date: Tue, 26 Apr 2016 17:04:53 +0000
Subject: [Paraview] Reduce significant figures in time display
Message-ID: <707B9268-C19B-4670-94FD-AF8E4BB3AE5D@sandia.gov>

I know this is not the answer you are looking for, but you can quickly add the "Annotate Time" source. I think that will default to the precision you want, plus you can easily edit it.

-Ken


From: ParaView <paraview-bounces at paraview.org<mailto:paraview-bounces at paraview.org>> on behalf of Alex Lindsay <adlinds3 at ncsu.edu<mailto:adlinds3 at ncsu.edu>>
Date: Monday, April 25, 2016 at 11:21 AM
To: Cory Quammen <cory.quammen at kitware.com<mailto:cory.quammen at kitware.com>>
Cc: ParaView <paraview at paraview.org<mailto:paraview at paraview.org>>
Subject: [EXTERNAL] Re: [Paraview] Reduce significant figures in time display

That's a bummer. I believe in version 4 the time display only showed a few sig figs which worked better for me. I wish I could combine my favorite features of versions 4 and 5

On 04/25/2016 01:56 PM, Cory Quammen wrote:
Alex,

I do not believe this is user customizable.

Cory

On Mon, Apr 25, 2016 at 1:16 PM, Alex Lindsay <adlinds3 at ncsu.edu<mailto:adlinds3 at ncsu.edu>> wrote:
Is there a way to reduce the number of significant figures in the time display? I can't see the exponential component of my scientific notation which makes it rather difficult to know where I actually am in my simulation.

[cid:part2.07050902.00020409 at ncsu.edu]

_______________________________________________
Powered by www.kitware.com<http://www.kitware.com>

Visit other Kitware open-source projects at <http://www.kitware.com/opensource/opensource.html> http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView

Search the list archives at: http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview




--
Cory Quammen
R&D Engineer
Kitware, Inc.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160426/da19d0df/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ATT00001.png
Type: image/png
Size: 43108 bytes
Desc: ATT00001.png
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160426/da19d0df/attachment.png>

From kmorel at sandia.gov  Tue Apr 26 13:15:42 2016
From: kmorel at sandia.gov (Moreland, Kenneth)
Date: Tue, 26 Apr 2016 17:15:42 +0000
Subject: [Paraview] Plotting Global Variables Over Time - Connecting
 first and last data points?
Message-ID: <7F2232FD-910B-4D68-B24F-2635EFCCEEEA@sandia.gov>

Ryan,

I am not able to replicate your problem. I am also using ParaView 5.0.1 on a Mac, and when I do plot global variables over time I do not get the looped connection you describe. Is there perhaps a particular set of steps or specific data set you are using?

-Ken


From: ParaView <paraview-bounces at paraview.org<mailto:paraview-bounces at paraview.org>> on behalf of "Jamison, Ryan Dale" <rdjamis at sandia.gov<mailto:rdjamis at sandia.gov>>
Date: Tuesday, April 26, 2016 at 6:08 AM
To: "paraview at paraview.org<mailto:paraview at paraview.org>" <paraview at paraview.org<mailto:paraview at paraview.org>>
Subject: [EXTERNAL] [Paraview] Plotting Global Variables Over Time - Connecting first and last data points?

Hello All,

I was wondering if anyone has noticed that when plotting global variables over time, Paraview connects the first and last data points (see attached image)? Why does Paraview do this? Any ideas? Can the user toggle this option off?

I?m running 5.0.1 on a Mac. Thanks,

Ryan

[cid:BD88CAAB-0838-46C5-B0B6-7A43A35C5F2B at srn.sandia.gov]
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160426/545177da/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: PastedGraphic-2.png
Type: image/png
Size: 64512 bytes
Desc: PastedGraphic-2.png
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160426/545177da/attachment.png>

From kmorel at sandia.gov  Tue Apr 26 13:24:39 2016
From: kmorel at sandia.gov (Moreland, Kenneth)
Date: Tue, 26 Apr 2016 17:24:39 +0000
Subject: [Paraview] Paraview not using normals data when rendering
 WarpByVector
Message-ID: <412C7958-A945-4A34-B081-52457F9EFFD5@sandia.gov>

Carlos,

I suspect the warp by vector filter is removing the normals because in general warping a surface invalidates the normals. Perhaps a feature request could be to add an option to warp by vector to preserve the normals.

There is a filter to generate normals on a polygonal surface. It works by averaging the normals of incident polygons, but I don't think it is weighted by area.

-Ken


From: ParaView <paraview-bounces at paraview.org<mailto:paraview-bounces at paraview.org>> on behalf of Carlos Baumann <CBaumann at slb.com<mailto:CBaumann at slb.com>>
Date: Monday, April 25, 2016 at 11:16 AM
To: "paraview at paraview.org<mailto:paraview at paraview.org>" <paraview at paraview.org<mailto:paraview at paraview.org>>
Subject: [EXTERNAL] [Paraview] Paraview not using normals data when rendering WarpByVector

Hello Paraview !

The attached .vtk file has quad elements defining a tube,
for each point or node it has defined a scalar Pressure, and two vectors, Displacement and Normals.

When I render ?Displacement Magnitude? on the surface, the normal are used, this is perfect and this is what I want, see attached snapshot,

However when I use WarpByVector to deform the geometry, and plotting ?Displacement Magnitude? on the surface, the normals are not used,
each element uses its own normal, and I see the facets.  How can I change this so that the normals that I have defined in the .vtk file are used ?

Ideally I would want Paraview to use the normal at any point/node by averaging the normal of all the elements attached, weighted by the area,
can this be done automatically with GUI settings ?

Thank you in advance for your help.

Regards,
Carlos





-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160426/3d0f6840/attachment.html>

From CBaumann at slb.com  Tue Apr 26 13:32:25 2016
From: CBaumann at slb.com (Carlos Baumann)
Date: Tue, 26 Apr 2016 17:32:25 +0000
Subject: [Paraview] Thank You ! => RE: Paraview not using normals data when
 rendering WarpByVector
Message-ID: <32D0A6E400786141A9A2CB170C1CF1EC01DD46E096@NL0230MBX07N1.DIR.slb.com>

Ken,

Thanks a lot for your reply.

After a few trials I realized that to animate deformation it is best to define the nodal coordinates at each time step, therefore I am not using WarpByVector for the animation and the facets are not an issue for me at this time.  However, your suggestion about putting a feature request could be useful when we want to animate w/o defining time steps.

Cheers,
Carlos

From: Moreland, Kenneth [mailto:kmorel at sandia.gov]
Sent: Tuesday, April 26, 2016 12:25 PM
To: Carlos Baumann <CBaumann at slb.com>; paraview at paraview.org
Subject: Re: [Paraview] Paraview not using normals data when rendering WarpByVector

Carlos,

I suspect the warp by vector filter is removing the normals because in general warping a surface invalidates the normals. Perhaps a feature request could be to add an option to warp by vector to preserve the normals.

There is a filter to generate normals on a polygonal surface. It works by averaging the normals of incident polygons, but I don't think it is weighted by area.

-Ken


From: ParaView <paraview-bounces at paraview.org<mailto:paraview-bounces at paraview.org>> on behalf of Carlos Baumann <CBaumann at slb.com<mailto:CBaumann at slb.com>>
Date: Monday, April 25, 2016 at 11:16 AM
To: "paraview at paraview.org<mailto:paraview at paraview.org>" <paraview at paraview.org<mailto:paraview at paraview.org>>
Subject: [EXTERNAL] [Paraview] Paraview not using normals data when rendering WarpByVector

Hello Paraview !

The attached .vtk file has quad elements defining a tube,
for each point or node it has defined a scalar Pressure, and two vectors, Displacement and Normals.

When I render ?Displacement Magnitude? on the surface, the normal are used, this is perfect and this is what I want, see attached snapshot,

However when I use WarpByVector to deform the geometry, and plotting ?Displacement Magnitude? on the surface, the normals are not used,
each element uses its own normal, and I see the facets.  How can I change this so that the normals that I have defined in the .vtk file are used ?

Ideally I would want Paraview to use the normal at any point/node by averaging the normal of all the elements attached, weighted by the area,
can this be done automatically with GUI settings ?

Thank you in advance for your help.

Regards,
Carlos





-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160426/c0844f06/attachment.html>

From kmorel at sandia.gov  Tue Apr 26 14:02:13 2016
From: kmorel at sandia.gov (Moreland, Kenneth)
Date: Tue, 26 Apr 2016 18:02:13 +0000
Subject: [Paraview] Few details i don't know
Message-ID: <A4C84178-5AE1-43AA-80BA-775053E29D64@sandia.gov>


Thank you for your quick answer, however i am afraid i wasn't explicit in my questions:

For the first point, yes, i knew that, but when i create 3d text, it is always in the same place,i can't put words in each face of my cube for example,

You can use the transform filter to move the 3D text around in space.

For the second point, i wasn't talking about applying text with Paraview but directly with the Vtk programm i wrote ( i think it could be more simple for me than if i always use the 3d text program)

It looks like by program you mean data file. 3D text is really just a bunch of polygons. You can save those polygons out in a .vtk file.

And is the time annotation only linear? (Can't i use for example time annotation with logarythm?)

The time annotation simply tells you the time. The time is what it is. If you have time steps in your data and those time steps happen to be spaced logarithmically, then ParaView will visit those logarithmic steps. If there are no steps, then yes ParaView will take even (linear) steps. There is no special mode to logarithmically space the time steps. You could make a filter to do that, though.

-Ken

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160426/ee15e576/attachment.html>

From kmorel at sandia.gov  Tue Apr 26 14:14:20 2016
From: kmorel at sandia.gov (Moreland, Kenneth)
Date: Tue, 26 Apr 2016 18:14:20 +0000
Subject: [Paraview] Time Variables in CF Conventions
Message-ID: <359D63D8-15DF-4D22-BB06-9F0BF4E2A7FD@sandia.gov>

The netCDF CF reader in ParaView does support time dimensions. For example, the netCDF file tos_O1_2001-2002.nc used for VTK testing (https://midas3.kitware.com/midas/item/206312) has a time dimension and it loads just fine.

As I recall, the CF convention defines the time dimension using a units property on the variable that specifies some unit of time. One problem that has occurred in the past is that sometimes the time unit is something that the reader does not recognize as time. What is the time units used in your data set?

-Ken


From: ParaView <paraview-bounces at paraview.org<mailto:paraview-bounces at paraview.org>> on behalf of Ken Sheldon <KSheldon at slb.com<mailto:KSheldon at slb.com>>
Date: Saturday, April 23, 2016 at 9:51 AM
To: "paraview at paraview.org<mailto:paraview at paraview.org>" <paraview at paraview.org<mailto:paraview at paraview.org>>
Subject: [EXTERNAL] [Paraview] Time Variables in CF Conventions

I am trying to read a CF Conventions NetCDF file  (Sea Surface Temperature from NOAA).
The CF reader in ParaView recognizes the axes and the data correctly.  However, it does not seem to recognize the TIME dimension.

Is anyone here reading CF (Climate Forecasting) files successfully?


Reference: http://www.class.ngdc.noaa.gov/saa/products/search?datatype_family=SST14NA

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160426/fb30c33d/attachment.html>

From KSheldon at slb.com  Tue Apr 26 15:36:08 2016
From: KSheldon at slb.com (Ken Sheldon)
Date: Tue, 26 Apr 2016 19:36:08 +0000
Subject: [Paraview] Time Variables in CF Conventions
In-Reply-To: <359D63D8-15DF-4D22-BB06-9F0BF4E2A7FD@sandia.gov>
References: <359D63D8-15DF-4D22-BB06-9F0BF4E2A7FD@sandia.gov>
Message-ID: <2911E772881F8B4AB39462AA4A35EC55017B89106C@NL0230MBX12N2.DIR.slb.com>

It looks like the units in the CLASS data are, ?hour since 1997-01-01 00:00:00?
In the test data, (which works fine, I confirm) , the units are, ?days since 2001-1-1?

I would expect the attribute axis = ?T? to indicate this is a time dimension.  Time as a UOM might be used in any property, not just dimensions.
What do you think?


TIME1 (-1051845271)
    double,    182
    Number of attributes = 5
        units = hour since 1997-01-01 00:00:00
        time_origin = 1-JAN-1997 00:00:00
        axis = T
        standard_name = time
        bounds = TIME1_bnds



time (-781830246)
    double,    24
    Number of attributes = 7
        standard_name = time
        long_name = time
        units = days since 2001-1-1
        axis = T
        calendar = 360_day
        bounds = time_bnds
        original_units = seconds since 2001-1-1

From: Moreland, Kenneth [mailto:kmorel at sandia.gov]
Sent: Tuesday, April 26, 2016 1:14 PM
To: Ken Sheldon <KSheldon at slb.com>; paraview at paraview.org
Subject: Re: [Paraview] Time Variables in CF Conventions

The netCDF CF reader in ParaView does support time dimensions. For example, the netCDF file tos_O1_2001-2002.nc used for VTK testing (https://midas3.kitware.com/midas/item/206312<https://urldefense.proofpoint.com/v2/url?u=https-3A__midas3.kitware.com_midas_item_206312&d=CwMGaQ&c=uGuXJ43KPkPWEl2imVFDmZQlhQUET7pVRA2PDIOxgqw&r=PPcXhptMPNzBCwHx-o1zqg&m=A7bpyohhfVnNQoUi0GE2BJS2jE2OkxogntGvLqTmVGM&s=HGoAZZDUus7tmDI-abU30H7Ij8Qg_EeQwanbaawq2-w&e=>) has a time dimension and it loads just fine.

As I recall, the CF convention defines the time dimension using a units property on the variable that specifies some unit of time. One problem that has occurred in the past is that sometimes the time unit is something that the reader does not recognize as time. What is the time units used in your data set?

-Ken


From: ParaView <paraview-bounces at paraview.org<mailto:paraview-bounces at paraview.org>> on behalf of Ken Sheldon <KSheldon at slb.com<mailto:KSheldon at slb.com>>
Date: Saturday, April 23, 2016 at 9:51 AM
To: "paraview at paraview.org<mailto:paraview at paraview.org>" <paraview at paraview.org<mailto:paraview at paraview.org>>
Subject: [EXTERNAL] [Paraview] Time Variables in CF Conventions

I am trying to read a CF Conventions NetCDF file  (Sea Surface Temperature from NOAA).
The CF reader in ParaView recognizes the axes and the data correctly.  However, it does not seem to recognize the TIME dimension.

Is anyone here reading CF (Climate Forecasting) files successfully?


Reference: http://www.class.ngdc.noaa.gov/saa/products/search?datatype_family=SST14NA<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.class.ngdc.noaa.gov_saa_products_search-3Fdatatype-5Ffamily-3DSST14NA&d=CwMGaQ&c=uGuXJ43KPkPWEl2imVFDmZQlhQUET7pVRA2PDIOxgqw&r=PPcXhptMPNzBCwHx-o1zqg&m=A7bpyohhfVnNQoUi0GE2BJS2jE2OkxogntGvLqTmVGM&s=SRGkdReFFtTB-YX8wNBb3I5f3OaCiZ27AIVx3iqa78k&e=>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160426/01e09fa2/attachment.html>

From kmorel at sandia.gov  Tue Apr 26 18:17:08 2016
From: kmorel at sandia.gov (Moreland, Kenneth)
Date: Tue, 26 Apr 2016 22:17:08 +0000
Subject: [Paraview] Time Variables in CF Conventions
Message-ID: <54760734-A3D5-41AC-A94B-320473B935F3@sandia.gov>

That is very odd. I just had a look at the code for the reader, and both the units and the axis properties should have caused the reader to treat the dimension as time.

Is there a way I can get a copy of the netCDF file? I tried going to the web site you posted at the beginning of this thread, but I couldn't figure out how to download a netCDF file.


From: Ken Sheldon <KSheldon at slb.com<mailto:KSheldon at slb.com>>
Date: Tuesday, April 26, 2016 at 12:36 PM
To: Kenneth Moreland <kmorel at sandia.gov<mailto:kmorel at sandia.gov>>, "paraview at paraview.org<mailto:paraview at paraview.org>" <paraview at paraview.org<mailto:paraview at paraview.org>>
Subject: [EXTERNAL] RE: [Paraview] Time Variables in CF Conventions

It looks like the units in the CLASS data are, ?hour since 1997-01-01 00:00:00?
In the test data, (which works fine, I confirm) , the units are, ?days since 2001-1-1?

I would expect the attribute axis = ?T? to indicate this is a time dimension.  Time as a UOM might be used in any property, not just dimensions.
What do you think?


TIME1 (-1051845271)
    double,    182
    Number of attributes = 5
        units = hour since 1997-01-01 00:00:00
        time_origin = 1-JAN-1997 00:00:00
        axis = T
        standard_name = time
        bounds = TIME1_bnds



time (-781830246)
    double,    24
    Number of attributes = 7
        standard_name = time
        long_name = time
        units = days since 2001-1-1
        axis = T
        calendar = 360_day
        bounds = time_bnds
        original_units = seconds since 2001-1-1

From: Moreland, Kenneth [mailto:kmorel at sandia.gov]
Sent: Tuesday, April 26, 2016 1:14 PM
To: Ken Sheldon <KSheldon at slb.com<mailto:KSheldon at slb.com>>; paraview at paraview.org<mailto:paraview at paraview.org>
Subject: Re: [Paraview] Time Variables in CF Conventions

The netCDF CF reader in ParaView does support time dimensions. For example, the netCDF file tos_O1_2001-2002.nc used for VTK testing (https://midas3.kitware.com/midas/item/206312<https://urldefense.proofpoint.com/v2/url?u=https-3A__midas3.kitware.com_midas_item_206312&d=CwMGaQ&c=uGuXJ43KPkPWEl2imVFDmZQlhQUET7pVRA2PDIOxgqw&r=PPcXhptMPNzBCwHx-o1zqg&m=A7bpyohhfVnNQoUi0GE2BJS2jE2OkxogntGvLqTmVGM&s=HGoAZZDUus7tmDI-abU30H7Ij8Qg_EeQwanbaawq2-w&e=>) has a time dimension and it loads just fine.

As I recall, the CF convention defines the time dimension using a units property on the variable that specifies some unit of time. One problem that has occurred in the past is that sometimes the time unit is something that the reader does not recognize as time. What is the time units used in your data set?

-Ken


From: ParaView <paraview-bounces at paraview.org<mailto:paraview-bounces at paraview.org>> on behalf of Ken Sheldon <KSheldon at slb.com<mailto:KSheldon at slb.com>>
Date: Saturday, April 23, 2016 at 9:51 AM
To: "paraview at paraview.org<mailto:paraview at paraview.org>" <paraview at paraview.org<mailto:paraview at paraview.org>>
Subject: [EXTERNAL] [Paraview] Time Variables in CF Conventions

I am trying to read a CF Conventions NetCDF file  (Sea Surface Temperature from NOAA).
The CF reader in ParaView recognizes the axes and the data correctly.  However, it does not seem to recognize the TIME dimension.

Is anyone here reading CF (Climate Forecasting) files successfully?


Reference: http://www.class.ngdc.noaa.gov/saa/products/search?datatype_family=SST14NA<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.class.ngdc.noaa.gov_saa_products_search-3Fdatatype-5Ffamily-3DSST14NA&d=CwMGaQ&c=uGuXJ43KPkPWEl2imVFDmZQlhQUET7pVRA2PDIOxgqw&r=PPcXhptMPNzBCwHx-o1zqg&m=A7bpyohhfVnNQoUi0GE2BJS2jE2OkxogntGvLqTmVGM&s=SRGkdReFFtTB-YX8wNBb3I5f3OaCiZ27AIVx3iqa78k&e=>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160426/25b247e5/attachment.html>

From kmorel at sandia.gov  Tue Apr 26 19:06:11 2016
From: kmorel at sandia.gov (Moreland, Kenneth)
Date: Tue, 26 Apr 2016 23:06:11 +0000
Subject: [Paraview] Time Variables in CF Conventions
Message-ID: <BB38B53E-E6EE-42EF-A1E1-2BE833BD7D24@sandia.gov>

Thanks, Ken. I think I have the problem figured out. If you look closely at the time variable (which gives the time values), you will see that there are several invalid 0 values appended to the end. The netCDF reader is being stupid and add these time values, which gives an invalid time bounds. I think ParaView is seeing the invalid time bounds (begin time greater than end time) and determining that there should not be time. If you strip off the 0 values, the time loads fine.

I will make a bug report on this. Is it OK to attach the example file you gave me to it, or would you rather it not be open?

-Ken


From: Ken Sheldon <KSheldon at slb.com<mailto:KSheldon at slb.com>>
Date: Tuesday, April 26, 2016 at 3:25 PM
To: Kenneth Moreland <kmorel at sandia.gov<mailto:kmorel at sandia.gov>>
Subject: [EXTERNAL] RE: [Paraview] Time Variables in CF Conventions

Hi, Ken.
I will email you a ZIPX file , size approx. 800Kbytes.

----Ken


From: Moreland, Kenneth [mailto:kmorel at sandia.gov]
Sent: Tuesday, April 26, 2016 5:17 PM
To: Ken Sheldon <KSheldon at slb.com<mailto:KSheldon at slb.com>>; paraview at paraview.org<mailto:paraview at paraview.org>
Subject: Re: [Paraview] Time Variables in CF Conventions

That is very odd. I just had a look at the code for the reader, and both the units and the axis properties should have caused the reader to treat the dimension as time.

Is there a way I can get a copy of the netCDF file? I tried going to the web site you posted at the beginning of this thread, but I couldn't figure out how to download a netCDF file.


From: Ken Sheldon <KSheldon at slb.com<mailto:KSheldon at slb.com>>
Date: Tuesday, April 26, 2016 at 12:36 PM
To: Kenneth Moreland <kmorel at sandia.gov<mailto:kmorel at sandia.gov>>, "paraview at paraview.org<mailto:paraview at paraview.org>" <paraview at paraview.org<mailto:paraview at paraview.org>>
Subject: [EXTERNAL] RE: [Paraview] Time Variables in CF Conventions

It looks like the units in the CLASS data are, ?hour since 1997-01-01 00:00:00?
In the test data, (which works fine, I confirm) , the units are, ?days since 2001-1-1?

I would expect the attribute axis = ?T? to indicate this is a time dimension.  Time as a UOM might be used in any property, not just dimensions.
What do you think?


TIME1 (-1051845271)
    double,    182
    Number of attributes = 5
        units = hour since 1997-01-01 00:00:00
        time_origin = 1-JAN-1997 00:00:00
        axis = T
        standard_name = time
        bounds = TIME1_bnds



time (-781830246)
    double,    24
    Number of attributes = 7
        standard_name = time
        long_name = time
        units = days since 2001-1-1
        axis = T
        calendar = 360_day
        bounds = time_bnds
        original_units = seconds since 2001-1-1

From: Moreland, Kenneth [mailto:kmorel at sandia.gov]
Sent: Tuesday, April 26, 2016 1:14 PM
To: Ken Sheldon <KSheldon at slb.com<mailto:KSheldon at slb.com>>; paraview at paraview.org<mailto:paraview at paraview.org>
Subject: Re: [Paraview] Time Variables in CF Conventions

The netCDF CF reader in ParaView does support time dimensions. For example, the netCDF file tos_O1_2001-2002.nc used for VTK testing (https://midas3.kitware.com/midas/item/206312<https://urldefense.proofpoint.com/v2/url?u=https-3A__midas3.kitware.com_midas_item_206312&d=CwMGaQ&c=uGuXJ43KPkPWEl2imVFDmZQlhQUET7pVRA2PDIOxgqw&r=PPcXhptMPNzBCwHx-o1zqg&m=A7bpyohhfVnNQoUi0GE2BJS2jE2OkxogntGvLqTmVGM&s=HGoAZZDUus7tmDI-abU30H7Ij8Qg_EeQwanbaawq2-w&e=>) has a time dimension and it loads just fine.

As I recall, the CF convention defines the time dimension using a units property on the variable that specifies some unit of time. One problem that has occurred in the past is that sometimes the time unit is something that the reader does not recognize as time. What is the time units used in your data set?

-Ken


From: ParaView <paraview-bounces at paraview.org<mailto:paraview-bounces at paraview.org>> on behalf of Ken Sheldon <KSheldon at slb.com<mailto:KSheldon at slb.com>>
Date: Saturday, April 23, 2016 at 9:51 AM
To: "paraview at paraview.org<mailto:paraview at paraview.org>" <paraview at paraview.org<mailto:paraview at paraview.org>>
Subject: [EXTERNAL] [Paraview] Time Variables in CF Conventions

I am trying to read a CF Conventions NetCDF file  (Sea Surface Temperature from NOAA).
The CF reader in ParaView recognizes the axes and the data correctly.  However, it does not seem to recognize the TIME dimension.

Is anyone here reading CF (Climate Forecasting) files successfully?


Reference: http://www.class.ngdc.noaa.gov/saa/products/search?datatype_family=SST14NA<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.class.ngdc.noaa.gov_saa_products_search-3Fdatatype-5Ffamily-3DSST14NA&d=CwMGaQ&c=uGuXJ43KPkPWEl2imVFDmZQlhQUET7pVRA2PDIOxgqw&r=PPcXhptMPNzBCwHx-o1zqg&m=A7bpyohhfVnNQoUi0GE2BJS2jE2OkxogntGvLqTmVGM&s=SRGkdReFFtTB-YX8wNBb3I5f3OaCiZ27AIVx3iqa78k&e=>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160426/a3898ad6/attachment-0001.html>

From lukasz.paluszek at airbus.com  Wed Apr 27 05:53:37 2016
From: lukasz.paluszek at airbus.com (Paluszek, Lukasz)
Date: Wed, 27 Apr 2016 09:53:37 +0000
Subject: [Paraview] Overlaying plots in the render view
Message-ID: <27545_1461750824_57208C28_27545_11112_1_333d484d1c0247c2a3612c6cf2a70692@DE0-03DAG13-P04.central.mail.corp>

Is it possible to compose a scene with a 2D plot floating in front of a 3D rendered view, just like you would in Office if you want to squeeze several diagrams in one figure? Exporting separate images and then combining them is of course one option but I would like to generate an animation so if I could compose my scene in Paraview it would save a lot of effort. Currently I can only split my layout view vertically or horizontally but this approach is quite limited in terms of layout aesthetics. Detaching a layout from the main Paraview window and overlaying it over another layout demonstrates roughly what I want to achieve (see attached file).

Regards,
Lukasz



[Beschreibung: Beschreibung: Description?: cid:image001.png at 01CF0B8F.DB7831F0]
?ukasz Paluszek
Airbus Helicopters
Aerodynamics Department (ETGA)
86607 Donauw?rth
Germany
Tel.: +49 (90) 671 8231
Fax.: +49 (90) 671 9122
Lukasz.Paluszek at airbus.com<mailto:Lukasz.Paluszek at airbus.com>


AIRBUS HELICOPTERS DEUTSCHLAND GmbH

Sitz der Gesellschaft / Registered Office: Donauw?rth

Registergericht / Registration Court: Amtsgericht Augsburg HRB 16508

Vorsitzender des Aufsichtsrates / Chairman of the Supervisory Board: Guillaume Faury

Gesch?ftsf?hrung / Board of Management: Dr. Wolfgang Schoder, Vorsitzender / CEO; Johannes Kleidorfer; Dr. Klaus Przemeck; Martin Sch?bel; Stefan Thom?

The information in this e-mail is confidential. The contents may not be disclosed or used by anyone other than the addressee. Access to this e-mail by anyone else is unauthorised.
If you are not the intended recipient, please notify Airbus immediately and delete this e-mail.
Airbus cannot accept any responsibility for the accuracy or completeness of this e-mail as it has been sent over public networks. If you have any concerns over the content of this message or its Accuracy or Integrity, please contact Airbus immediately.
All outgoing e-mails from Airbus are checked using regularly updated virus scanning software but you should take whatever measures you deem to be appropriate to ensure that this message and any attachments are virus free.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160427/b4b2bc21/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 16151 bytes
Desc: image001.png
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160427/b4b2bc21/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: plot.jpeg
Type: image/jpeg
Size: 57771 bytes
Desc: plot.jpeg
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160427/b4b2bc21/attachment.jpeg>

From seongmo.yeon at gmail.com  Wed Apr 27 06:33:32 2016
From: seongmo.yeon at gmail.com (Seong Mo Yeon)
Date: Wed, 27 Apr 2016 19:33:32 +0900
Subject: [Paraview] Paraview 5.0.1 gradientofunstructureddataset filter
Message-ID: <C39CA797-5845-4057-BCF0-717877E1E1E1@gmail.com>

In 5.0.1 binary , the function for q criterion is missing in the filter gradientofunstructureddataset. It is obseved in both linux and ms windows.

---Sent from Boxer | http://getboxer.com

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160427/d955faa7/attachment.html>

From Mandar.Shirke at infosys.com  Wed Apr 27 08:14:39 2016
From: Mandar.Shirke at infosys.com (Mandar Prakash Shirke)
Date: Wed, 27 Apr 2016 12:14:39 +0000
Subject: [Paraview] Paraview.exe has stopped working
Message-ID: <BBF23853DD0BE54FB8F0F12A6F06A1DA370555BD@blrkecmbx15.ad.infosys.com>

Hello,

I have been trying to install Paraview (5.0.0_64b), but after installation, application does not launch. It says "Paraview.exe has stopped working"
[cid:image001.jpg at 01D1A0AC.784BFD00]

I tried Paraview 4.1 & Paraview 3.12 & both are running fine. I am getting this error only for Paraview 5.0.

Please suggest a solution.

Regards,
Mandar
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160427/d461cfe1/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 17972 bytes
Desc: image001.jpg
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160427/d461cfe1/attachment.jpg>

From cory.quammen at kitware.com  Wed Apr 27 09:08:41 2016
From: cory.quammen at kitware.com (Cory Quammen)
Date: Wed, 27 Apr 2016 09:08:41 -0400
Subject: [Paraview] Overlaying plots in the render view
In-Reply-To: <27545_1461750824_57208C28_27545_11112_1_333d484d1c0247c2a3612c6cf2a70692@DE0-03DAG13-P04.central.mail.corp>
References: <27545_1461750824_57208C28_27545_11112_1_333d484d1c0247c2a3612c6cf2a70692@DE0-03DAG13-P04.central.mail.corp>
Message-ID: <CAB5Fpx63dEwsXcSqW+ZeJPTo0AzWVUhKa6kULiye9jfLszPCnQ@mail.gmail.com>

Hi Lukasz,

To my knowledge, there is no built-in functionality in ParaView to do this.
It is theoretically possible to achieve with a custom plugin, but it would
take a fair amount of work to implement.

Best regards,
Cory

On Wed, Apr 27, 2016 at 5:53 AM, Paluszek, Lukasz <
lukasz.paluszek at airbus.com> wrote:

> Is it possible to compose a scene with a 2D plot floating in front of a 3D
> rendered view, just like you would in Office if you want to squeeze several
> diagrams in one figure? Exporting separate images and then combining them
> is of course one option but I would like to generate an animation so if I
> could compose my scene in Paraview it would save a lot of effort. Currently
> I can only split my layout view vertically or horizontally but this
> approach is quite limited in terms of layout aesthetics. Detaching a layout
> from the main Paraview window and overlaying it over another layout
> demonstrates roughly what I want to achieve (see attached file).
>
>
>
> Regards,
>
> Lukasz
>
>
>
>
>
>
>
> [image: Beschreibung: Beschreibung: Description :
> cid:image001.png at 01CF0B8F.DB7831F0]
>
> *?ukasz Paluszek*
>
> Airbus Helicopters
>
> Aerodynamics Department (ETGA)
>
> 86607 Donauw?rth
>
> Germany
>
> Tel.: +49 (90) 671 8231
>
> Fax.: +49 (90) 671 9122
>
> Lukasz.Paluszek at airbus.com
>
>
>
> AIRBUS HELICOPTERS DEUTSCHLAND GmbH
>
> Sitz der Gesellschaft / Registered Office: Donauw?rth
>
> Registergericht / Registration Court: Amtsgericht Augsburg HRB 16508
>
> Vorsitzender des Aufsichtsrates / Chairman of the Supervisory Board:
> Guillaume Faury
>
> Gesch?ftsf?hrung / Board of Management: Dr. Wolfgang Schoder, Vorsitzender
> / CEO; Johannes Kleidorfer; Dr. Klaus Przemeck; Martin Sch?bel; Stefan Thom?
>
> The information in this e-mail is confidential. The contents may not be disclosed or used by anyone other than the addressee. Access to this e-mail by anyone else is unauthorised.
> If you are not the intended recipient, please notify Airbus immediately and delete this e-mail.
> Airbus cannot accept any responsibility for the accuracy or completeness of this e-mail as it has been sent over public networks. If you have any concerns over the content of this message or its Accuracy or Integrity, please contact Airbus immediately.
> All outgoing e-mails from Airbus are checked using regularly updated virus scanning software but you should take whatever measures you deem to be appropriate to ensure that this message and any attachments are virus free.
>
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview
>
>


-- 
Cory Quammen
R&D Engineer
Kitware, Inc.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160427/3c6185c0/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 16151 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160427/3c6185c0/attachment.png>

From cory.quammen at kitware.com  Wed Apr 27 09:33:25 2016
From: cory.quammen at kitware.com (Cory Quammen)
Date: Wed, 27 Apr 2016 09:33:25 -0400
Subject: [Paraview] Parallel rendering including transparency
In-Reply-To: <CAJm-X2CYJZr-LQaLbprsJ7xvUPVjpcLJ06C+=h3tt8O0VOspgA@mail.gmail.com>
References: <CAJm-X2CDAVpkwqobXwHAWHAaU0gLz-egnWY+OGEeVTL33QrpZw@mail.gmail.com>
 <CAJm-X2CYJZr-LQaLbprsJ7xvUPVjpcLJ06C+=h3tt8O0VOspgA@mail.gmail.com>
Message-ID: <CAB5Fpx7oMB1V7vZv5udcL14mz_1wwi2yXupJ-SwZetZkT=8t2w@mail.gmail.com>

Kai,

I'm not sure if this will help, but take a look at

http://www.paraview.org/gitweb?p=ParaView.git;a=blob;f=ParaViewCore/VTKExtensions/Testing/TestIceTCompositePass.cxx;h=9580e8642909eddef3de619dc9286cf9a0fa0a19;hb=HEAD

for some possible clues. You might need to add a vtkDepthPeelingPass,
for example.

HTH,
Cory

On Tue, Apr 26, 2016 at 6:48 AM, Kai Winter <kaiwinter212 at gmail.com> wrote:
> Please, does anybody have a clue, how to correctly render transparent
> objects in parallel?
>
> I attach the modified version of
> http://www.vtk.org/Wiki/VTK/MultiPass_Rendering_With_IceT and screenshots of
> the render windows for MPI rank 0,1,2 (from left to right), first with
> SetOpacity(1), second with SetOpacity(0.5). In the second case, you see the
> artifacts in the blue segment, and (worse) that rank 0 shows a black window
> instead of the composite image.
>
> Thank you
> Kai
>
> On Mon, Apr 25, 2016 at 5:41 PM, Kai Winter <kaiwinter212 at gmail.com> wrote:
>>
>> Hello,
>> is it possible to extend the example at
>> http://www.vtk.org/Wiki/VTK/MultiPass_Rendering_With_IceT for parallel
>> rendering including transparent objects?
>>
>> I have tried to modify the above example by first setting
>>   actor->GetProperty()->SetOpacity(0.3);
>> after creation of the actor, and, second, adding
>>   vtkSmartPointer<vtkTranslucentPass> translucent =
>> vtkSmartPointer<vtkTranslucentPass>::New();
>>   passes->AddItem(translucent);
>> after the original line "passes->AddItem(opaque);".
>>
>> The result is for example, when running with 3 MPI processes:
>> The sphere segments in the partial Renderers of process 1 and 2 are
>> transparent (but show some artefacts).
>> The composite Renderer of process 0 doesn't show any sphere, just the
>> black background!
>> When the opacity is set to 1, the sphere segments are composited in three
>> colors on process 0 as expected.
>>
>> What is required to correctly perform parallel rendering including
>> transparency?
>> (I am using ParaView-v5.0.1, compiled from source on Ubuntu 15.04)
>>
>> Thank you
>> Kai
>>
>
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview
>



-- 
Cory Quammen
R&D Engineer
Kitware, Inc.

From andy.bauer at kitware.com  Wed Apr 27 09:39:16 2016
From: andy.bauer at kitware.com (Andy Bauer)
Date: Wed, 27 Apr 2016 06:39:16 -0700
Subject: [Paraview] Paraview 5.0.1 gradientofunstructureddataset filter
In-Reply-To: <C39CA797-5845-4057-BCF0-717877E1E1E1@gmail.com>
References: <C39CA797-5845-4057-BCF0-717877E1E1E1@gmail.com>
Message-ID: <CAMaOp+HMTVRS1bBeGM_h3S0tupVxRyEM2S8RqF5c+A2tVB=tAg@mail.gmail.com>

Hi,

That option is only shown in the advanced settings of the Properties dialog
box. To get those settings, click on the Gear button right under the
Question mark button. Please let me know if this doesn't solve your issue.

Best,
Andy

On Wed, Apr 27, 2016 at 3:33 AM, Seong Mo Yeon <seongmo.yeon at gmail.com>
wrote:

> In 5.0.1 binary , the function for q criterion is missing in the filter
> gradientofunstructureddataset. It is obseved in both linux and ms windows.
>
>
> ---
> Sent from Boxer | http://getboxer.com <http://bxr.io/PBID1>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160427/b0350b91/attachment.html>

From cory.quammen at kitware.com  Wed Apr 27 09:41:48 2016
From: cory.quammen at kitware.com (Cory Quammen)
Date: Wed, 27 Apr 2016 09:41:48 -0400
Subject: [Paraview] visualising a numpy array
In-Reply-To: <3016982.g3SsLEMJvk@vega>
References: <3016982.g3SsLEMJvk@vega>
Message-ID: <CAB5Fpx55wZjw8Ty+_4rD-O6ZhqnW8-n5ccNY13zoGZU1fejmgw@mail.gmail.com>

Juha,

How are you getting the PETSc._DMDA_Vec_array into ParaView? The
Programmable Filter is also available in ParaView...

You'll need to set up a vtkImageData as the output of a Programmable
Source/Filter at the very least with the proper dimensions, then use
the vtk.numpy_interface.dataset_adapter tools to adapt your numpy
array as a VTK data array that you add to the vtkImageData's point
data.

Parallel is tougher... You can do the full data set in serial and
distribute using the D3 filter, but obviously that has some downsides.
I believe it is possible to distribute the dataset using MPI in a
Programmable Source/Filter, but have never done so myself.

HTH,
Cory

On Tue, Apr 26, 2016 at 8:49 AM, Juha J?ykk? <juha.jaykka at gmail.com> wrote:
> Dear list,
>
> What's the current best practice to visualise a (3D) numpy array with
> paraview? In particular, I'm wondering if
>
> vtkdata = numpy_support.numpy_to_vtk(num_array=NumPy_data.ravel(), deep=True,
> array_type=vtk.VTK_FLOAT)
>
> can somehow be directly visualised? In parallel.
>
> I'm aware of ProgrammableSource() and how to do it using that, but only from a
> file! What I'd very much like to do is avoid the file (if I cannot avoid the
> file, I'll just do xdmf and hdf5.)
>
> Just in case it matters, the numpy array is actually not really a numpy array,
> but petsc4py.PETSc._DMDA_Vec_array which of course can be "cast" as
> numpy.ndarray.
>
> Best regards,
> Juha
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview



-- 
Cory Quammen
R&D Engineer
Kitware, Inc.

From cory.quammen at kitware.com  Wed Apr 27 10:23:30 2016
From: cory.quammen at kitware.com (Cory Quammen)
Date: Wed, 27 Apr 2016 10:23:30 -0400
Subject: [Paraview] Reading json colormap files in Python and exporting
 color data
In-Reply-To: <CA+yV-vAaQ0C88ZQJkjZkkDTVPBabTUSoBLe7Wozsjhs2k=RZxw@mail.gmail.com>
References: <CA+yV-vAaQ0C88ZQJkjZkkDTVPBabTUSoBLe7Wozsjhs2k=RZxw@mail.gmail.com>
Message-ID: <CAB5Fpx55WGRTttc_JTnMsmphih6qCF4cHdqxLJbm8WkCk=0_BQ@mail.gmail.com>

Hi Andy,

On Tue, Apr 26, 2016 at 10:15 AM, Andy Smith <agsmith424 at gmail.com> wrote:
> I have two questions:
>
> 1. I am trying to load colormaps in a Python script so that I have access to
> the lookup table later in the script.  I have successfully used the
> LoadLookupTable function with xml colormap files but this does not seem to
> work on json files.  I get a parsing error:
>
> ERROR: parsing lut file /path/to/my/colormap.json
>
> The json colormap file loads correctly inside the GUI.  Is there another
> function that I should be calling instead of LoadLookupTable or is there an
> issue with this function?  Should it call a different parser based on the
> file extension?

LoadLookupTable works only for XML files. I don't believe there is a
similar compact function for loading JSON files, but one should be
available.

> 2. Is there a way to export the discretized color data?  For example, my
> colormap may have seven control points in Lab space but I'd like to export
> 256 control points and the associated R,G,B values for use in other tools.
> Alternatively, are there any ParaView Python functions that I can use to
> extract R,G,B values from a colormap based on input array values?

This Python is surprisingly slow, but works:

lut = GetColorTransferFunction(arrayName)
dct = lut.SMProxy.GetClientSideObject()
range = dct.GetRange()
for i in xrange(256):
  x = (i*(range[1] - range[0]) / 255.0) + range[0]
  r = dct.GetRedValue(x)
  g = dct.GetGreenValue(x)
  b = dct.GetBlueValue(x)
  print x, r, g, b

HTH,
Cory

>
> Thanks,
> Andy
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview
>



-- 
Cory Quammen
R&D Engineer
Kitware, Inc.

From cory.quammen at kitware.com  Wed Apr 27 10:31:42 2016
From: cory.quammen at kitware.com (Cory Quammen)
Date: Wed, 27 Apr 2016 10:31:42 -0400
Subject: [Paraview] Threshold doesn't find range of some variables
In-Reply-To: <CY1PR07MB2506DC0BA140A9730D80AF2F9F630@CY1PR07MB2506.namprd07.prod.outlook.com>
References: <CY1PR07MB2506DC0BA140A9730D80AF2F9F630@CY1PR07MB2506.namprd07.prod.outlook.com>
Message-ID: <CAB5Fpx727rrnyqX-3rZY7CxO-xWXu-vs=+Owheu6H4F18mwkOA@mail.gmail.com>

Hi Dennis,

Are you sure you have the "Group" variable selected in the Scalars combo box?

Duplicate values should not cause any problems with this. Do you have
a data set you can share?

Thanks,
Cory

On Tue, Apr 26, 2016 at 10:32 AM, Dennis Conklin
<dennis_conklin at goodyear.com> wrote:
> All,
>
>
>
> I have a cell variable which is actually sort of a ?grouping? variable.
> So let?s call the variable ?Group?.   I have 180 elements that have a value
> of ?1?,  180 elements that have a value of ?2?, etc.
>
>
>
> In Paraview v5.0.1
>
> When I click on the ?Reset using current data values? arrow in Threshold, it
> does not change the values to reflect the range of this variable.  It just
> keeps the existing range.  Is it the array of many duplicate values which is
> confusing this?
>
>
>
> This works in v4.4
>
>
>
> Dennis
>
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview
>



-- 
Cory Quammen
R&D Engineer
Kitware, Inc.

From cory.quammen at kitware.com  Wed Apr 27 10:34:35 2016
From: cory.quammen at kitware.com (Cory Quammen)
Date: Wed, 27 Apr 2016 10:34:35 -0400
Subject: [Paraview] Plotting Global Variables Over Time - Connecting
 first and last data points?
In-Reply-To: <7F2232FD-910B-4D68-B24F-2635EFCCEEEA@sandia.gov>
References: <7F2232FD-910B-4D68-B24F-2635EFCCEEEA@sandia.gov>
Message-ID: <CAB5Fpx44-2MswfB47bf-qc5s6X0cq7tqnf09u-CJWokBRRbcuA@mail.gmail.com>

Ryan and Ken,

I, too, and unable to replicate this on a Mac with ParaView 5.0.1.

Cory

On Tue, Apr 26, 2016 at 1:15 PM, Moreland, Kenneth <kmorel at sandia.gov>
wrote:

> Ryan,
>
> I am not able to replicate your problem. I am also using ParaView 5.0.1 on
> a Mac, and when I do plot global variables over time I do not get the
> looped connection you describe. Is there perhaps a particular set of steps
> or specific data set you are using?
>
> -Ken
>
>
> From: ParaView <paraview-bounces at paraview.org> on behalf of "Jamison,
> Ryan Dale" <rdjamis at sandia.gov>
> Date: Tuesday, April 26, 2016 at 6:08 AM
> To: "paraview at paraview.org" <paraview at paraview.org>
> Subject: [EXTERNAL] [Paraview] Plotting Global Variables Over Time -
> Connecting first and last data points?
>
> Hello All,
>
> I was wondering if anyone has noticed that when plotting global variables
> over time, Paraview connects the first and last data points (see attached
> image)? Why does Paraview do this? Any ideas? Can the user toggle this
> option off?
>
> I?m running 5.0.1 on a Mac. Thanks,
>
> Ryan
>
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview
>
>


-- 
Cory Quammen
R&D Engineer
Kitware, Inc.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160427/46ca358a/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: PastedGraphic-2.png
Type: image/png
Size: 64512 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160427/46ca358a/attachment.png>

From rdjamis at sandia.gov  Wed Apr 27 11:20:55 2016
From: rdjamis at sandia.gov (Jamison, Ryan Dale)
Date: Wed, 27 Apr 2016 15:20:55 +0000
Subject: [Paraview] [EXTERNAL] Plotting Global Variables Over Time -
 Connecting first and last data points?
In-Reply-To: <CAB5Fpx44-2MswfB47bf-qc5s6X0cq7tqnf09u-CJWokBRRbcuA@mail.gmail.com>
References: <7F2232FD-910B-4D68-B24F-2635EFCCEEEA@sandia.gov>
 <CAB5Fpx44-2MswfB47bf-qc5s6X0cq7tqnf09u-CJWokBRRbcuA@mail.gmail.com>
Message-ID: <10967D31-12DB-4357-8218-7B95BC6682C0@sandia.gov>

Hi Cory & Ken,

Thanks for the feedback. I discovered something interesting?

When the file I?m viewing is local on my computer, the first and last data points are not connected.

When the file I?m viewing is on a remote HPC server, the first and last data points are connected.

Could it be a setting on the HPC side of things?

Thanks, Ryan

On Apr 27, 2016, at 8:34 AM, Cory Quammen <cory.quammen at kitware.com<mailto:cory.quammen at kitware.com>> wrote:

Ryan and Ken,

I, too, and unable to replicate this on a Mac with ParaView 5.0.1.

Cory

On Tue, Apr 26, 2016 at 1:15 PM, Moreland, Kenneth <kmorel at sandia.gov<mailto:kmorel at sandia.gov>> wrote:
Ryan,

I am not able to replicate your problem. I am also using ParaView 5.0.1 on a Mac, and when I do plot global variables over time I do not get the looped connection you describe. Is there perhaps a particular set of steps or specific data set you are using?

-Ken


From: ParaView <paraview-bounces at paraview.org<mailto:paraview-bounces at paraview.org>> on behalf of "Jamison, Ryan Dale" <rdjamis at sandia.gov<mailto:rdjamis at sandia.gov>>
Date: Tuesday, April 26, 2016 at 6:08 AM
To: "paraview at paraview.org<mailto:paraview at paraview.org>" <paraview at paraview.org<mailto:paraview at paraview.org>>
Subject: [EXTERNAL] [Paraview] Plotting Global Variables Over Time - Connecting first and last data points?

Hello All,

I was wondering if anyone has noticed that when plotting global variables over time, Paraview connects the first and last data points (see attached image)? Why does Paraview do this? Any ideas? Can the user toggle this option off?

I?m running 5.0.1 on a Mac. Thanks,

Ryan

<PastedGraphic-2.png>

_______________________________________________
Powered by www.kitware.com<http://www.kitware.com/>

Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView

Search the list archives at: http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview




--
Cory Quammen
R&D Engineer
Kitware, Inc.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160427/cfecf2d5/attachment-0001.html>

From kaiwinter212 at gmail.com  Wed Apr 27 11:37:54 2016
From: kaiwinter212 at gmail.com (Kai Winter)
Date: Wed, 27 Apr 2016 17:37:54 +0200
Subject: [Paraview] Parallel rendering including transparency
In-Reply-To: <CAB5Fpx7oMB1V7vZv5udcL14mz_1wwi2yXupJ-SwZetZkT=8t2w@mail.gmail.com>
References: <CAJm-X2CDAVpkwqobXwHAWHAaU0gLz-egnWY+OGEeVTL33QrpZw@mail.gmail.com>
 <CAJm-X2CYJZr-LQaLbprsJ7xvUPVjpcLJ06C+=h3tt8O0VOspgA@mail.gmail.com>
 <CAB5Fpx7oMB1V7vZv5udcL14mz_1wwi2yXupJ-SwZetZkT=8t2w@mail.gmail.com>
Message-ID: <CAJm-X2A74z+3B=v1_1Xx0Svqgw2TN==BWY_jpxyAkbB6=dgGag@mail.gmail.com>

The TestIceTCompositePass.cxx test is helpful for sure. It demonstrates
what I am trying to achieve.
The vtkDepthPeelingPass is not required for this simple geometry. This can
be checked by removing the line "passes->AddItem(peeling);" in
TestIceTCompositePass.cxx, which gives the same result.

What does make a difference is whether or not I remove
"iceTPass->SetKdTree(this->KdTree);". Seems like I have to apply a d3
filter to get the kdtree. I could not yet apply everything from
TestIceTCompositePass.cxx to my previous MultipassRendering.cxx example,
but I will successively simplify TestIceTCompositePass.cxx until I
understand what exactly needs to be changed.

Unless somebody can point out the necessary modifications.

Thank you!
Kai


On Wed, Apr 27, 2016 at 3:33 PM, Cory Quammen <cory.quammen at kitware.com>
wrote:

> Kai,
>
> I'm not sure if this will help, but take a look at
>
>
> http://www.paraview.org/gitweb?p=ParaView.git;a=blob;f=ParaViewCore/VTKExtensions/Testing/TestIceTCompositePass.cxx;h=9580e8642909eddef3de619dc9286cf9a0fa0a19;hb=HEAD
>
> for some possible clues. You might need to add a vtkDepthPeelingPass,
> for example.
>
> HTH,
> Cory
>
> On Tue, Apr 26, 2016 at 6:48 AM, Kai Winter <kaiwinter212 at gmail.com>
> wrote:
> > Please, does anybody have a clue, how to correctly render transparent
> > objects in parallel?
> >
> > I attach the modified version of
> > http://www.vtk.org/Wiki/VTK/MultiPass_Rendering_With_IceT and
> screenshots of
> > the render windows for MPI rank 0,1,2 (from left to right), first with
> > SetOpacity(1), second with SetOpacity(0.5). In the second case, you see
> the
> > artifacts in the blue segment, and (worse) that rank 0 shows a black
> window
> > instead of the composite image.
> >
> > Thank you
> > Kai
> >
> > On Mon, Apr 25, 2016 at 5:41 PM, Kai Winter <kaiwinter212 at gmail.com>
> wrote:
> >>
> >> Hello,
> >> is it possible to extend the example at
> >> http://www.vtk.org/Wiki/VTK/MultiPass_Rendering_With_IceT for parallel
> >> rendering including transparent objects?
> >>
> >> I have tried to modify the above example by first setting
> >>   actor->GetProperty()->SetOpacity(0.3);
> >> after creation of the actor, and, second, adding
> >>   vtkSmartPointer<vtkTranslucentPass> translucent =
> >> vtkSmartPointer<vtkTranslucentPass>::New();
> >>   passes->AddItem(translucent);
> >> after the original line "passes->AddItem(opaque);".
> >>
> >> The result is for example, when running with 3 MPI processes:
> >> The sphere segments in the partial Renderers of process 1 and 2 are
> >> transparent (but show some artefacts).
> >> The composite Renderer of process 0 doesn't show any sphere, just the
> >> black background!
> >> When the opacity is set to 1, the sphere segments are composited in
> three
> >> colors on process 0 as expected.
> >>
> >> What is required to correctly perform parallel rendering including
> >> transparency?
> >> (I am using ParaView-v5.0.1, compiled from source on Ubuntu 15.04)
> >>
> >> Thank you
> >> Kai
> >>
> >
> >
> > _______________________________________________
> > Powered by www.kitware.com
> >
> > Visit other Kitware open-source projects at
> > http://www.kitware.com/opensource/opensource.html
> >
> > Please keep messages on-topic and check the ParaView Wiki at:
> > http://paraview.org/Wiki/ParaView
> >
> > Search the list archives at: http://markmail.org/search/?q=ParaView
> >
> > Follow this link to subscribe/unsubscribe:
> > http://public.kitware.com/mailman/listinfo/paraview
> >
>
>
>
> --
> Cory Quammen
> R&D Engineer
> Kitware, Inc.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160427/421d79cf/attachment.html>

From juha.jaykka at gmail.com  Wed Apr 27 11:39:31 2016
From: juha.jaykka at gmail.com (Juha =?ISO-8859-1?Q?J=E4ykk=E4?=)
Date: Wed, 27 Apr 2016 16:39:31 +0100
Subject: [Paraview] visualising a numpy array
In-Reply-To: <CAB5Fpx55wZjw8Ty+_4rD-O6ZhqnW8-n5ccNY13zoGZU1fejmgw@mail.gmail.com>
References: <3016982.g3SsLEMJvk@vega>
 <CAB5Fpx55wZjw8Ty+_4rD-O6ZhqnW8-n5ccNY13zoGZU1fejmgw@mail.gmail.com>
Message-ID: <7473615.6gLVRJUW11@vega>

> How are you getting the PETSc._DMDA_Vec_array into ParaView? The
> Programmable Filter is also available in ParaView...

I was going to use 

my_numpy_data = petsc_dmda_array[:]
vtkobject = paraview.numpy_support.numpy_to_vtk(my_numpy_data.copy())

That works fine, but then I got stuck with how to stick this into paraview's 
pipeline.

> You'll need to set up a vtkImageData as the output of a Programmable
> Source/Filter at the very least with the proper dimensions, then use
> the vtk.numpy_interface.dataset_adapter tools to adapt your numpy
> array as a VTK data array that you add to the vtkImageData's point
> data.

I would have thought I need a vtkStructuredGrid or vtkRectilinearGrid, but I 
don't seem able to figure out how to use them.

With vSG I can

pts = vtk.vtkPoints()
pdo = self.GetOutput()
newArray = vtk.vtkDoubleArray()
# this is how far I've got before...
newArray.SetName("testdata")
newArray.SetNumberOfComponents(1)
pdo.GetPointData().AddArray(newArray)

# stuff our numbers into pdo.GetPointData().GetArray(0).InsertNextValue(float) 
one by one,
# followed by pts.InsertNextPoint(x,y,z), so need to get xyz as well
xmin,xmax,Nx,ymin,ymax,Ny,zmin,zmax,Nz = -1,1,10,-1,2,20,-1,3,30
loci = 
numpy.mgrid[xmin:xmax:1j*Nx,ymin:ymax:1j*Ny,zmin:zmax:1j*Nz].reshape(3,-1)
values = numpy.random.random(loci[0].shape)
for ind in range(loci[0].shape[0]):
    pdo.GetPointData().GetArray(0).InsertNextValue(values[ind])
    pts.InsertNextPoint(loci[0,ind],loci[1,ind],loci[2,ind])
pdo.SetPoints(pts)
exts = [xmin,xmax,ymin,ymax,zmin,zmax]
pdo.SetExtent(exts)

which seems to do the right thing except I can not make paraview plot anything 
using this. In the ProgrammableSource's Information tab I do see the right 
bounds and extents (but I am a bit confused about what the "dimension" means 
in extents: it says 3, 4, 5 for x, y, z, which makes me think it has used unit 
lattice spacing even though I would have thought it uses whatever it finds in 
pts. The "Data Arrays" box has "testdata" in it and has the correct value 
range. Also the number of points is correct (6000). I don't know where it gets 
its 24 cells from, though. (24 = 2*3*4, so I am a bit concerned it gets this 
implicitly from bounds again with unit spacing).

But I don't understand what I'm doing wrong as I'm basically modifying 
examples from the wiki.

Using vtkImageData I can only get a Number of Points: 60 (and no plot) and 
using vtkRectilinearGrid I get the same. I can fix the 60 -> 6000 by fixing 
the extents, but that still leaves the bounds and no plot on screen.

> Parallel is tougher... You can do the full data set in serial and
> distribute using the D3 filter, but obviously that has some downsides.

Unacceptable ones: I cannot even imagine what that bottleneck would do to the 
code.

> I believe it is possible to distribute the dataset using MPI in a
> Programmable Source/Filter, but have never done so myself.

Hmm... so where does the ProgrammableSource run? I was planning on running the 
whole code in parallel, but didn't really think about how to do that yet. Now 
that I start thinking about it, Catalyst is probably the way to do it, isn't 
it?

Cheers,
Juha

> On Tue, Apr 26, 2016 at 8:49 AM, Juha J?ykk? <juha.jaykka at gmail.com> wrote:
> > Dear list,
> > 
> > What's the current best practice to visualise a (3D) numpy array with
> > paraview? In particular, I'm wondering if
> > 
> > vtkdata = numpy_support.numpy_to_vtk(num_array=NumPy_data.ravel(),
> > deep=True, array_type=vtk.VTK_FLOAT)
> > 
> > can somehow be directly visualised? In parallel.
> > 
> > I'm aware of ProgrammableSource() and how to do it using that, but only
> > from a file! What I'd very much like to do is avoid the file (if I cannot
> > avoid the file, I'll just do xdmf and hdf5.)
> > 
> > Just in case it matters, the numpy array is actually not really a numpy
> > array, but petsc4py.PETSc._DMDA_Vec_array which of course can be "cast"
> > as numpy.ndarray.
> > 
> > Best regards,
> > Juha
> > 
> > _______________________________________________
> > Powered by www.kitware.com
> > 
> > Visit other Kitware open-source projects at
> > http://www.kitware.com/opensource/opensource.html
> > 
> > Please keep messages on-topic and check the ParaView Wiki at:
> > http://paraview.org/Wiki/ParaView
> > 
> > Search the list archives at: http://markmail.org/search/?q=ParaView
> > 
> > Follow this link to subscribe/unsubscribe:
> > http://public.kitware.com/mailman/listinfo/paraview


From stali at geology.wisc.edu  Thu Apr 28 09:25:16 2016
From: stali at geology.wisc.edu (Tabrez Ali)
Date: Thu, 28 Apr 2016 08:25:16 -0500
Subject: [Paraview] Direct URL to official binaries
Message-ID: <57220F3C.7040508@geology.wisc.edu>

I want to download ParaView directly on a machine remotely using 
wget/curl but I cannot find a direct working link to the official 
binaries available through http://www.paraview.org/download/

Any ideas?

Thanks in advance.

Tabrez

From dkxls23 at gmail.com  Thu Apr 28 09:25:19 2016
From: dkxls23 at gmail.com (Armin Wehrfritz)
Date: Thu, 28 Apr 2016 16:25:19 +0300
Subject: [Paraview] Direct URL to official binaries
In-Reply-To: <57220F3C.7040508@geology.wisc.edu>
References: <57220F3C.7040508@geology.wisc.edu>
Message-ID: <57220F3F.5010007@gmail.com>

Right next to the download button is a small button which will give you 
the direct link.

Cheers,
Armin




On 04/28/2016 04:25 PM, Tabrez Ali wrote:
> I want to download ParaView directly on a machine remotely using
> wget/curl but I cannot find a direct working link to the official
> binaries available through http://www.paraview.org/download/
>
> Any ideas?
>
> Thanks in advance.
>
> Tabrez
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview

From mgammar at outlook.fr  Thu Apr 28 09:31:02 2016
From: mgammar at outlook.fr (Marwen Gammar)
Date: Thu, 28 Apr 2016 15:31:02 +0200
Subject: [Paraview] Changing the value of the ramp
Message-ID: <BAY182-W33B39E5A77AD28091272B8D1650@phx.gbl>

Hello Miss, Mister, 
Is it possible to change the value of the ramp in the animation view of paraview? How?
Thank  you very much for your help,
Marwen
 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160428/f5fc0047/attachment.html>

From stali at geology.wisc.edu  Thu Apr 28 09:47:47 2016
From: stali at geology.wisc.edu (Tabrez Ali)
Date: Thu, 28 Apr 2016 08:47:47 -0500
Subject: [Paraview] Direct URL to official binaries
In-Reply-To: <57220F3F.5010007@gmail.com>
References: <57220F3C.7040508@geology.wisc.edu> <57220F3F.5010007@gmail.com>
Message-ID: <57221483.8070800@geology.wisc.edu>

But that's not a direct link which I can use with wget/curl. E.g., if I 
right click to vire/copy the URL I get

http://www.paraview.org/paraview-downloads/download.php?submit=Download&version=v5.0&type=binary&os=linux64&downloadFile=ParaView-5.0.1-Qt4-OpenGL2-MPI-Linux-64bit.tar.gz

which cannot be used with wget/curl as it is.

Tabrez

On 04/28/2016 08:25 AM, Armin Wehrfritz wrote:
> Right next to the download button is a small button which will give 
> you the direct link.
>
> Cheers,
> Armin
>
>
>
>
> On 04/28/2016 04:25 PM, Tabrez Ali wrote:
>> I want to download ParaView directly on a machine remotely using
>> wget/curl but I cannot find a direct working link to the official
>> binaries available through http://www.paraview.org/download/
>>
>> Any ideas?
>>
>> Thanks in advance.
>>
>> Tabrez
>> _______________________________________________
>> Powered by www.kitware.com
>>
>> Visit other Kitware open-source projects at
>> http://www.kitware.com/opensource/opensource.html
>>
>> Please keep messages on-topic and check the ParaView Wiki at:
>> http://paraview.org/Wiki/ParaView
>>
>> Search the list archives at: http://markmail.org/search/?q=ParaView
>>
>> Follow this link to subscribe/unsubscribe:
>> http://public.kitware.com/mailman/listinfo/paraview
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at 
> http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at: 
> http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview


From robert.maynard at kitware.com  Thu Apr 28 09:48:45 2016
From: robert.maynard at kitware.com (Robert Maynard)
Date: Thu, 28 Apr 2016 09:48:45 -0400
Subject: [Paraview] Direct URL to official binaries
In-Reply-To: <57221483.8070800@geology.wisc.edu>
References: <57220F3C.7040508@geology.wisc.edu> <57220F3F.5010007@gmail.com>
 <57221483.8070800@geology.wisc.edu>
Message-ID: <CAFzjYVpqJu4ttBJTvagxAXSZAqtyzRMD5BONAAyPUW=nkPBY=Q@mail.gmail.com>

You need to wrap the url in quotes for it to work with wget:

wget -O ParaView-5.0.1-Qt4-OpenGL2-MPI-Linux-64bit.tar.gz
"http://www.paraview.org/paraview-downloads/download.php?submit=Download&version=v5.0&type=binary&os=linux64&downloadFile=ParaView-5.0.1-Qt4-OpenGL2-MPI-Linux-64bit.tar.gz"

On Thu, Apr 28, 2016 at 9:47 AM, Tabrez Ali <stali at geology.wisc.edu> wrote:
> But that's not a direct link which I can use with wget/curl. E.g., if I
> right click to vire/copy the URL I get
>
> http://www.paraview.org/paraview-downloads/download.php?submit=Download&version=v5.0&type=binary&os=linux64&downloadFile=ParaView-5.0.1-Qt4-OpenGL2-MPI-Linux-64bit.tar.gz
>
> which cannot be used with wget/curl as it is.
>
> Tabrez
>
>
> On 04/28/2016 08:25 AM, Armin Wehrfritz wrote:
>>
>> Right next to the download button is a small button which will give you
>> the direct link.
>>
>> Cheers,
>> Armin
>>
>>
>>
>>
>> On 04/28/2016 04:25 PM, Tabrez Ali wrote:
>>>
>>> I want to download ParaView directly on a machine remotely using
>>> wget/curl but I cannot find a direct working link to the official
>>> binaries available through http://www.paraview.org/download/
>>>
>>> Any ideas?
>>>
>>> Thanks in advance.
>>>
>>> Tabrez
>>> _______________________________________________
>>> Powered by www.kitware.com
>>>
>>> Visit other Kitware open-source projects at
>>> http://www.kitware.com/opensource/opensource.html
>>>
>>> Please keep messages on-topic and check the ParaView Wiki at:
>>> http://paraview.org/Wiki/ParaView
>>>
>>> Search the list archives at: http://markmail.org/search/?q=ParaView
>>>
>>> Follow this link to subscribe/unsubscribe:
>>> http://public.kitware.com/mailman/listinfo/paraview
>>
>> _______________________________________________
>> Powered by www.kitware.com
>>
>> Visit other Kitware open-source projects at
>> http://www.kitware.com/opensource/opensource.html
>>
>> Please keep messages on-topic and check the ParaView Wiki at:
>> http://paraview.org/Wiki/ParaView
>>
>> Search the list archives at: http://markmail.org/search/?q=ParaView
>>
>> Follow this link to subscribe/unsubscribe:
>> http://public.kitware.com/mailman/listinfo/paraview
>
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview

From stali at geology.wisc.edu  Thu Apr 28 10:23:58 2016
From: stali at geology.wisc.edu (Tabrez Ali)
Date: Thu, 28 Apr 2016 09:23:58 -0500
Subject: [Paraview] Direct URL to official binaries
In-Reply-To: <CAFzjYVpqJu4ttBJTvagxAXSZAqtyzRMD5BONAAyPUW=nkPBY=Q@mail.gmail.com>
References: <57220F3C.7040508@geology.wisc.edu> <57220F3F.5010007@gmail.com>
 <57221483.8070800@geology.wisc.edu>
 <CAFzjYVpqJu4ttBJTvagxAXSZAqtyzRMD5BONAAyPUW=nkPBY=Q@mail.gmail.com>
Message-ID: <57221CFE.5090001@geology.wisc.edu>

It worked. Thanks!


On 04/28/2016 08:48 AM, Robert Maynard wrote:
> You need to wrap the url in quotes for it to work with wget:
>
> wget -O ParaView-5.0.1-Qt4-OpenGL2-MPI-Linux-64bit.tar.gz
> "http://www.paraview.org/paraview-downloads/download.php?submit=Download&version=v5.0&type=binary&os=linux64&downloadFile=ParaView-5.0.1-Qt4-OpenGL2-MPI-Linux-64bit.tar.gz"
>
> On Thu, Apr 28, 2016 at 9:47 AM, Tabrez Ali <stali at geology.wisc.edu> wrote:
>> But that's not a direct link which I can use with wget/curl. E.g., if I
>> right click to vire/copy the URL I get
>>
>> http://www.paraview.org/paraview-downloads/download.php?submit=Download&version=v5.0&type=binary&os=linux64&downloadFile=ParaView-5.0.1-Qt4-OpenGL2-MPI-Linux-64bit.tar.gz
>>
>> which cannot be used with wget/curl as it is.
>>
>> Tabrez
>>
>>
>> On 04/28/2016 08:25 AM, Armin Wehrfritz wrote:
>>> Right next to the download button is a small button which will give you
>>> the direct link.
>>>
>>> Cheers,
>>> Armin
>>>
>>>
>>>
>>>
>>> On 04/28/2016 04:25 PM, Tabrez Ali wrote:
>>>> I want to download ParaView directly on a machine remotely using
>>>> wget/curl but I cannot find a direct working link to the official
>>>> binaries available through http://www.paraview.org/download/
>>>>
>>>> Any ideas?
>>>>
>>>> Thanks in advance.
>>>>
>>>> Tabrez
>>>> _______________________________________________
>>>> Powered by www.kitware.com
>>>>
>>>> Visit other Kitware open-source projects at
>>>> http://www.kitware.com/opensource/opensource.html
>>>>
>>>> Please keep messages on-topic and check the ParaView Wiki at:
>>>> http://paraview.org/Wiki/ParaView
>>>>
>>>> Search the list archives at: http://markmail.org/search/?q=ParaView
>>>>
>>>> Follow this link to subscribe/unsubscribe:
>>>> http://public.kitware.com/mailman/listinfo/paraview
>>> _______________________________________________
>>> Powered by www.kitware.com
>>>
>>> Visit other Kitware open-source projects at
>>> http://www.kitware.com/opensource/opensource.html
>>>
>>> Please keep messages on-topic and check the ParaView Wiki at:
>>> http://paraview.org/Wiki/ParaView
>>>
>>> Search the list archives at: http://markmail.org/search/?q=ParaView
>>>
>>> Follow this link to subscribe/unsubscribe:
>>> http://public.kitware.com/mailman/listinfo/paraview
>>
>> _______________________________________________
>> Powered by www.kitware.com
>>
>> Visit other Kitware open-source projects at
>> http://www.kitware.com/opensource/opensource.html
>>
>> Please keep messages on-topic and check the ParaView Wiki at:
>> http://paraview.org/Wiki/ParaView
>>
>> Search the list archives at: http://markmail.org/search/?q=ParaView
>>
>> Follow this link to subscribe/unsubscribe:
>> http://public.kitware.com/mailman/listinfo/paraview


From malik_shqer at hotmail.com  Thu Apr 28 13:43:21 2016
From: malik_shqer at hotmail.com (Malik Shukeir)
Date: Thu, 28 Apr 2016 20:43:21 +0300
Subject: [Paraview] Display vector components on Paraview
In-Reply-To: <DUB123-W3983DA45BD552CAD9109368F650@phx.gbl>
References: <DUB123-W3983DA45BD552CAD9109368F650@phx.gbl>
Message-ID: <DUB123-W95673918BF25FD2862A6E8F650@phx.gbl>

Dear all,
Currently, I am a phd student and I am using paraview on Linux, I am working on materials crystallography. I am using Paraview to visualize the cristallographic orientations inside the material.
How can I display the components of a vector as a text, or at least assign a specific color to previously defined orientations
Ex: Directrion <1 1 1> Red      Directrion <1 1 2> Blue, etc ...
I would be grateful for any help
Malik SHUKEIRUPMC-Paris 		 	   		   		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160428/07932c34/attachment.html>

From dennis_conklin at goodyear.com  Thu Apr 28 13:53:23 2016
From: dennis_conklin at goodyear.com (Dennis Conklin)
Date: Thu, 28 Apr 2016 17:53:23 +0000
Subject: [Paraview] Plotting Global Variables Over Time - Connecting
 first and last data points?
Message-ID: <CY1PR07MB2506C54C6856BF02517BE4F89F650@CY1PR07MB2506.namprd07.prod.outlook.com>

I see the first and last points connected for Plot Over Time and for Plot Data.

I am running on a Linux workstation.

Dennis

From: Dennis Conklin
Sent: Tuesday, April 26, 2016 10:16 AM
To: Paraview (paraview at paraview.org) <paraview at paraview.org>
Subject: RE: Plotting Global Variables Over Time - Connecting first and last data points?

Ryan,

Not just plot over time - Plot Data does the same thing and it's equally annoying.

Dennis
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160428/b43009ac/attachment.html>

From dan.lipsa at kitware.com  Thu Apr 28 16:35:26 2016
From: dan.lipsa at kitware.com (Dan Lipsa)
Date: Thu, 28 Apr 2016 16:35:26 -0400
Subject: [Paraview] Display vector components on Paraview
In-Reply-To: <DUB123-W95673918BF25FD2862A6E8F650@phx.gbl>
References: <DUB123-W3983DA45BD552CAD9109368F650@phx.gbl>
 <DUB123-W95673918BF25FD2862A6E8F650@phx.gbl>
Message-ID: <CADwGrVqP2uPSfUVS3UWVr+xxN-nMQe3RA62exro-YRZi-xkdkQ@mail.gmail.com>

Malik,
You can use the Calculator filter to generate a new scalar with the same
value as one of the components of your vector. Then, you can color by that
scalar.

Dan


On Thu, Apr 28, 2016 at 1:43 PM, Malik Shukeir <malik_shqer at hotmail.com>
wrote:

> Dear all,
>
> Currently, I am a phd student and I am using paraview on Linux, I am
> working on materials crystallography. I am using Paraview to visualize the
> cristallographic orientations inside the material.
>
> How can I display the components of a vector as a text, or at least assign
> a specific color to previously defined orientations
>
> Ex: Directrion <1 1 1> Red
>       Directrion <1 1 2> Blue, etc ...
>
> I would be grateful for any help
>
> Malik SHUKEIR
> UPMC-Paris
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160428/948d22d3/attachment.html>

From cory.quammen at kitware.com  Fri Apr 29 09:58:40 2016
From: cory.quammen at kitware.com (Cory Quammen)
Date: Fri, 29 Apr 2016 09:58:40 -0400
Subject: [Paraview] volume rendering with Catalyst ...
In-Reply-To: <f137412b-ed30-44ee-7d1e-e7120f2f6a12@be.itu.edu.tr>
References: <f137412b-ed30-44ee-7d1e-e7120f2f6a12@be.itu.edu.tr>
Message-ID: <CAB5Fpx6OjrFZEGwLV4P26rWvvFbxypcGdCjJT2twXj6VaQ+4bg@mail.gmail.com>

It indeed looks like the scalar opacity function is not being set up
properly when using Catalyst. Looking at your script, it looks like it
should be, though.

Could you describe how you are running this with Catalyst?

Thanks,
Cory

On Tue, Apr 26, 2016 at 4:18 AM, Ufuk Utku Turuncoglu (BE)
<u.utku.turuncoglu at be.itu.edu.tr> wrote:
> Hi,
>
> I had a problem in Catalyst when i run a visualization pipeline with volume
> rendering. The attached figures shows the problem and belong to same
> visualization with and without Catalyst. In my case, the co-processing
> Python script (dvr.py) is generated from multi-block dataset and the
> Catalyst code uses MPI code to define multi-block dataset also. So, it is
> consistent in both side. The visualization pipeline includes Transform and
> MergeBlocks filters to create the final image and mapper is set as Bunyk Ray
> Cast. It seems that there is a problem in the color transfer function but i
> am not sure. I also test with different mapper such as projected-tetra but
> the result is same. I just wonder that did you see any similar problem
> before.
>
> Regards,
>
> Istanbul Technical University
> Informatics Institute
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview
>



-- 
Cory Quammen
R&D Engineer
Kitware, Inc.

From mathieu.westphal at kitware.com  Fri Apr 29 10:07:28 2016
From: mathieu.westphal at kitware.com (Mathieu Westphal)
Date: Fri, 29 Apr 2016 16:07:28 +0200
Subject: [Paraview] VTK/Paraview Courses in June
Message-ID: <CAC2t4UTNZJ=sv6Uu-pcrbHUHQ5Q9_C+501NSLoivJg1a5nGPjg@mail.gmail.com>

Hello

Kitware will be holding a 2-day Advanced VTK and Advanced ParaView course
on June 22th and 23th 2016 in Lyon, France.

Please visit our web site for more information and registration details at
Advanced VTK (English) : http://training.kitware.fr/browse/126
Advanced VTK (French) : http://formations.kitware.fr/browse/126
Advanced ParaView (English) : http://training.kitware.fr/browse/127
Advanced ParaView (French) : http://formations.kitware.fr/browse/127


Note that the course will be taught in English. If you have any question,
please contact us at formations at http://www.kitware.fr

Thank you,

Mathieu Westphal
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160429/8f7f0abb/attachment.html>

From u.utku.turuncoglu at be.itu.edu.tr  Fri Apr 29 10:12:54 2016
From: u.utku.turuncoglu at be.itu.edu.tr (Ufuk Utku Turuncoglu (BE))
Date: Fri, 29 Apr 2016 17:12:54 +0300
Subject: [Paraview] volume rendering with Catalyst ...
In-Reply-To: <CAB5Fpx6OjrFZEGwLV4P26rWvvFbxypcGdCjJT2twXj6VaQ+4bg@mail.gmail.com>
References: <f137412b-ed30-44ee-7d1e-e7120f2f6a12@be.itu.edu.tr>
 <CAB5Fpx6OjrFZEGwLV4P26rWvvFbxypcGdCjJT2twXj6VaQ+4bg@mail.gmail.com>
Message-ID: <6f6c30d4-28f2-12f2-b1ac-195e824baa13@be.itu.edu.tr>

Hi Cory,

Do you think that it is a bug in Catalyst side. In this case, i am 
running the code as follows

export LD_LIBRARY_PATH=/opt/progs/paraview-5.0.0/lib:${LD_LIBRARY_PATH}
export DYLD_LIBRARY_PATH=/opt/progs/paraview-5.0.0/lib:${DYLD_LIBRARY_PATH}
mpirun -np 12 ./main.x

Thanks for your help,

--ufuk


On 29/04/16 16:58, Cory Quammen wrote:
> It indeed looks like the scalar opacity function is not being set up
> properly when using Catalyst. Looking at your script, it looks like it
> should be, though.
>
> Could you describe how you are running this with Catalyst?
>
> Thanks,
> Cory
>
> On Tue, Apr 26, 2016 at 4:18 AM, Ufuk Utku Turuncoglu (BE)
> <u.utku.turuncoglu at be.itu.edu.tr> wrote:
>> Hi,
>>
>> I had a problem in Catalyst when i run a visualization pipeline with volume
>> rendering. The attached figures shows the problem and belong to same
>> visualization with and without Catalyst. In my case, the co-processing
>> Python script (dvr.py) is generated from multi-block dataset and the
>> Catalyst code uses MPI code to define multi-block dataset also. So, it is
>> consistent in both side. The visualization pipeline includes Transform and
>> MergeBlocks filters to create the final image and mapper is set as Bunyk Ray
>> Cast. It seems that there is a problem in the color transfer function but i
>> am not sure. I also test with different mapper such as projected-tetra but
>> the result is same. I just wonder that did you see any similar problem
>> before.
>>
>> Regards,
>>
>> Istanbul Technical University
>> Informatics Institute
>>
>> _______________________________________________
>> Powered by www.kitware.com
>>
>> Visit other Kitware open-source projects at
>> http://www.kitware.com/opensource/opensource.html
>>
>> Please keep messages on-topic and check the ParaView Wiki at:
>> http://paraview.org/Wiki/ParaView
>>
>> Search the list archives at: http://markmail.org/search/?q=ParaView
>>
>> Follow this link to subscribe/unsubscribe:
>> http://public.kitware.com/mailman/listinfo/paraview
>>
>
>


From wascott at sandia.gov  Fri Apr 29 13:27:57 2016
From: wascott at sandia.gov (Scott, W Alan)
Date: Fri, 29 Apr 2016 17:27:57 +0000
Subject: [Paraview] [EXTERNAL] Re: Plotting Global Variables Over Time -
 Connecting first and last data points?
In-Reply-To: <CY1PR07MB2506C54C6856BF02517BE4F89F650@CY1PR07MB2506.namprd07.prod.outlook.com>
References: <CY1PR07MB2506C54C6856BF02517BE4F89F650@CY1PR07MB2506.namprd07.prod.outlook.com>
Message-ID: <6a4db3d2450e499c85fa21922a97d7ad@ES01AMSNLNT.srn.sandia.gov>

Dennis,
I did replicate Ryan's bugs, and wrote them up here:

http://www.paraview.org/Bug/view.php?id=16095
http://www.paraview.org/Bug/view.php?id=16099
http://www.paraview.org/Bug/view.php?id=16100

If there is another connecting first and last points, I would like to know about it, and let's get them written up and fixed.  Note that the issue I saw only shows remote server.

Alan

From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Dennis Conklin
Sent: Thursday, April 28, 2016 11:53 AM
To: Paraview (paraview at paraview.org) <paraview at paraview.org>
Subject: [EXTERNAL] Re: [Paraview] Plotting Global Variables Over Time - Connecting first and last data points?

I see the first and last points connected for Plot Over Time and for Plot Data.

I am running on a Linux workstation.

Dennis

From: Dennis Conklin
Sent: Tuesday, April 26, 2016 10:16 AM
To: Paraview (paraview at paraview.org<mailto:paraview at paraview.org>) <paraview at paraview.org<mailto:paraview at paraview.org>>
Subject: RE: Plotting Global Variables Over Time - Connecting first and last data points?

Ryan,

Not just plot over time - Plot Data does the same thing and it's equally annoying.

Dennis
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160429/0eab1fdd/attachment.html>

From cory.quammen at kitware.com  Fri Apr 29 14:19:01 2016
From: cory.quammen at kitware.com (Cory Quammen)
Date: Fri, 29 Apr 2016 14:19:01 -0400
Subject: [Paraview] visualising a numpy array
In-Reply-To: <7473615.6gLVRJUW11@vega>
References: <3016982.g3SsLEMJvk@vega>
 <CAB5Fpx55wZjw8Ty+_4rD-O6ZhqnW8-n5ccNY13zoGZU1fejmgw@mail.gmail.com>
 <7473615.6gLVRJUW11@vega>
Message-ID: <CAB5Fpx60MexHWQfztmncxpR6bYDAQW4OsR5=kmxkeCq7r0SE9Q@mail.gmail.com>

On Wed, Apr 27, 2016 at 11:39 AM, Juha J?ykk? <juha.jaykka at gmail.com> wrote:
>> How are you getting the PETSc._DMDA_Vec_array into ParaView? The
>> Programmable Filter is also available in ParaView...
>
> I was going to use
>
> my_numpy_data = petsc_dmda_array[:]
> vtkobject = paraview.numpy_support.numpy_to_vtk(my_numpy_data.copy())
>
> That works fine, but then I got stuck with how to stick this into paraview's
> pipeline.
>
>> You'll need to set up a vtkImageData as the output of a Programmable
>> Source/Filter at the very least with the proper dimensions, then use
>> the vtk.numpy_interface.dataset_adapter tools to adapt your numpy
>> array as a VTK data array that you add to the vtkImageData's point
>> data.
>
> I would have thought I need a vtkStructuredGrid or vtkRectilinearGrid, but I
> don't seem able to figure out how to use them.

If your grid points are regularly spaced in each dimension, which I
think they are in this case, you can use a vtkImageData. See the
ParaViewGuide (http://www.paraview.org/paraview-guide/) pages 33 and
34 for pictorial representations of where vtkStructuredGrid or
vtkRectilinearGrid are needed.

> With vSG I can
>
> pts = vtk.vtkPoints()
> pdo = self.GetOutput()
> newArray = vtk.vtkDoubleArray()
> # this is how far I've got before...
> newArray.SetName("testdata")
> newArray.SetNumberOfComponents(1)
> pdo.GetPointData().AddArray(newArray)
>
> # stuff our numbers into pdo.GetPointData().GetArray(0).InsertNextValue(float)
> one by one,
> # followed by pts.InsertNextPoint(x,y,z), so need to get xyz as well
> xmin,xmax,Nx,ymin,ymax,Ny,zmin,zmax,Nz = -1,1,10,-1,2,20,-1,3,30
> loci =
> numpy.mgrid[xmin:xmax:1j*Nx,ymin:ymax:1j*Ny,zmin:zmax:1j*Nz].reshape(3,-1)
> values = numpy.random.random(loci[0].shape)
> for ind in range(loci[0].shape[0]):
>     pdo.GetPointData().GetArray(0).InsertNextValue(values[ind])
>     pts.InsertNextPoint(loci[0,ind],loci[1,ind],loci[2,ind])
> pdo.SetPoints(pts)
> exts = [xmin,xmax,ymin,ymax,zmin,zmax]
> pdo.SetExtent(exts)

Note that the extents are in the integer index space (e.g., i-j-k) of
the grid points rather than physical space, so exts should be
something like

[0, 9, 0, 19, 0, 29]

Also note that xmax, ymax, and zmax should be the highest possible
index, not the number of grid positions in that dimension.

> which seems to do the right thing except I can not make paraview plot anything
> using this. In the ProgrammableSource's Information tab I do see the right
> bounds and extents (but I am a bit confused about what the "dimension" means
> in extents: it says 3, 4, 5 for x, y, z, which makes me think it has used unit
> lattice spacing even though I would have thought it uses whatever it finds in
> pts. The "Data Arrays" box has "testdata" in it and has the correct value
> range. Also the number of points is correct (6000). I don't know where it gets
> its 24 cells from, though. (24 = 2*3*4, so I am a bit concerned it gets this
> implicitly from bounds again with unit spacing).
>
> But I don't understand what I'm doing wrong as I'm basically modifying
> examples from the wiki.
>
> Using vtkImageData I can only get a Number of Points: 60 (and no plot) and
> using vtkRectilinearGrid I get the same. I can fix the 60 -> 6000 by fixing
> the extents, but that still leaves the bounds and no plot on screen.
>
>> Parallel is tougher... You can do the full data set in serial and
>> distribute using the D3 filter, but obviously that has some downsides.
>
> Unacceptable ones: I cannot even imagine what that bottleneck would do to the
> code.
>
>> I believe it is possible to distribute the dataset using MPI in a
>> Programmable Source/Filter, but have never done so myself.
>
> Hmm... so where does the ProgrammableSource run? I was planning on running the
> whole code in parallel, but didn't really think about how to do that yet. Now
> that I start thinking about it, Catalyst is probably the way to do it, isn't
> it?

The Programmable Source is a VTK filter that runs on all nodes on
which you are running the ParaView server. Catalyst may indeed be
useful for you.

Cory

> Cheers,
> Juha
>
>> On Tue, Apr 26, 2016 at 8:49 AM, Juha J?ykk? <juha.jaykka at gmail.com> wrote:
>> > Dear list,
>> >
>> > What's the current best practice to visualise a (3D) numpy array with
>> > paraview? In particular, I'm wondering if
>> >
>> > vtkdata = numpy_support.numpy_to_vtk(num_array=NumPy_data.ravel(),
>> > deep=True, array_type=vtk.VTK_FLOAT)
>> >
>> > can somehow be directly visualised? In parallel.
>> >
>> > I'm aware of ProgrammableSource() and how to do it using that, but only
>> > from a file! What I'd very much like to do is avoid the file (if I cannot
>> > avoid the file, I'll just do xdmf and hdf5.)
>> >
>> > Just in case it matters, the numpy array is actually not really a numpy
>> > array, but petsc4py.PETSc._DMDA_Vec_array which of course can be "cast"
>> > as numpy.ndarray.
>> >
>> > Best regards,
>> > Juha
>> >
>> > _______________________________________________
>> > Powered by www.kitware.com
>> >
>> > Visit other Kitware open-source projects at
>> > http://www.kitware.com/opensource/opensource.html
>> >
>> > Please keep messages on-topic and check the ParaView Wiki at:
>> > http://paraview.org/Wiki/ParaView
>> >
>> > Search the list archives at: http://markmail.org/search/?q=ParaView
>> >
>> > Follow this link to subscribe/unsubscribe:
>> > http://public.kitware.com/mailman/listinfo/paraview
>



-- 
Cory Quammen
R&D Engineer
Kitware, Inc.

From cory.quammen at kitware.com  Fri Apr 29 15:13:00 2016
From: cory.quammen at kitware.com (Cory Quammen)
Date: Fri, 29 Apr 2016 15:13:00 -0400
Subject: [Paraview] Threshold doesn't find range of some variables
In-Reply-To: <CAB5Fpx727rrnyqX-3rZY7CxO-xWXu-vs=+Owheu6H4F18mwkOA@mail.gmail.com>
References: <CY1PR07MB2506DC0BA140A9730D80AF2F9F630@CY1PR07MB2506.namprd07.prod.outlook.com>
 <CAB5Fpx727rrnyqX-3rZY7CxO-xWXu-vs=+Owheu6H4F18mwkOA@mail.gmail.com>
Message-ID: <CAB5Fpx4AXsSpikvadMEvo-JQFb=g5uf29EqP4wk4XOQjKVCKLw@mail.gmail.com>

Dennis,

I filed a bug for what seems to be the issue here:
http://www.paraview.org/Bug/view.php?id=16106

Thanks,
Cory

On Wed, Apr 27, 2016 at 10:31 AM, Cory Quammen <cory.quammen at kitware.com> wrote:
> Hi Dennis,
>
> Are you sure you have the "Group" variable selected in the Scalars combo box?
>
> Duplicate values should not cause any problems with this. Do you have
> a data set you can share?
>
> Thanks,
> Cory
>
> On Tue, Apr 26, 2016 at 10:32 AM, Dennis Conklin
> <dennis_conklin at goodyear.com> wrote:
>> All,
>>
>>
>>
>> I have a cell variable which is actually sort of a ?grouping? variable.
>> So let?s call the variable ?Group?.   I have 180 elements that have a value
>> of ?1?,  180 elements that have a value of ?2?, etc.
>>
>>
>>
>> In Paraview v5.0.1
>>
>> When I click on the ?Reset using current data values? arrow in Threshold, it
>> does not change the values to reflect the range of this variable.  It just
>> keeps the existing range.  Is it the array of many duplicate values which is
>> confusing this?
>>
>>
>>
>> This works in v4.4
>>
>>
>>
>> Dennis
>>
>>
>> _______________________________________________
>> Powered by www.kitware.com
>>
>> Visit other Kitware open-source projects at
>> http://www.kitware.com/opensource/opensource.html
>>
>> Please keep messages on-topic and check the ParaView Wiki at:
>> http://paraview.org/Wiki/ParaView
>>
>> Search the list archives at: http://markmail.org/search/?q=ParaView
>>
>> Follow this link to subscribe/unsubscribe:
>> http://public.kitware.com/mailman/listinfo/paraview
>>
>
>
>
> --
> Cory Quammen
> R&D Engineer
> Kitware, Inc.



-- 
Cory Quammen
R&D Engineer
Kitware, Inc.

From wascott at sandia.gov  Fri Apr 29 19:54:08 2016
From: wascott at sandia.gov (Scott, W Alan)
Date: Fri, 29 Apr 2016 23:54:08 +0000
Subject: [Paraview] [EXTERNAL] Re: Reduce significant figures in time
 display
In-Reply-To: <571E6024.5020902@ncsu.edu>
References: <571E50EC.2030002@ncsu.edu>
 <CAB5Fpx4oSsRjTsU04R-xkf8Yy3FLvNSFumbO+tcM3k_3+_eM3g@mail.gmail.com>
 <571E6024.5020902@ncsu.edu>
Message-ID: <8aa406d7c5004a19a7064ddc5f8e2898@ES01AMSNLNT.srn.sandia.gov>

Trying to catch up on e-mail (Hah!), and found this one.  This was written up here:  http://www.paraview.org/Bug/view.php?id=15767.  Current target is the fall 2016 release.

Alan

From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Alex Lindsay
Sent: Monday, April 25, 2016 12:21 PM
To: Cory Quammen <cory.quammen at kitware.com>
Cc: ParaView <paraview at paraview.org>
Subject: [EXTERNAL] Re: [Paraview] Reduce significant figures in time display

That's a bummer. I believe in version 4 the time display only showed a few sig figs which worked better for me. I wish I could combine my favorite features of versions 4 and 5
On 04/25/2016 01:56 PM, Cory Quammen wrote:
Alex,

I do not believe this is user customizable.

Cory

On Mon, Apr 25, 2016 at 1:16 PM, Alex Lindsay <adlinds3 at ncsu.edu<mailto:adlinds3 at ncsu.edu>> wrote:
Is there a way to reduce the number of significant figures in the time display? I can't see the exponential component of my scientific notation which makes it rather difficult to know where I actually am in my simulation.

[cid:image001.png at 01D1A240.1F9B67A0]

_______________________________________________
Powered by www.kitware.com<http://www.kitware.com>

Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView

Search the list archives at: http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview



--
Cory Quammen
R&D Engineer
Kitware, Inc.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160429/3901ce63/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 43108 bytes
Desc: image001.png
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160429/3901ce63/attachment.png>

From wascott at sandia.gov  Fri Apr 29 20:10:21 2016
From: wascott at sandia.gov (Scott, W Alan)
Date: Sat, 30 Apr 2016 00:10:21 +0000
Subject: [Paraview] [EXTERNAL]  Change default color mapping
In-Reply-To: <571E5525.7080801@ncsu.edu>
References: <571E5525.7080801@ncsu.edu>
Message-ID: <56139d36c6044413866a4f1c697bc0ce@ES01AMSNLNT.srn.sandia.gov>

Alex,
I believe this was answered, but let me give a bit more detail.  At the end, I will answer.

A rainbow color map is considered to be a RBCM (Real Bad Color Map).  It's actually getting a lot of negative attention in the journals and conferences.  There are at least two reasons it's bad.  First is that about 8% of men are color blind, and the vast majority cannot tell the difference between green and red.  Thus, this color table is horrible for 8% of male engineers and scientists.  Second, the normal rainbow colormap does not change color equally to the human eye.  In other words, in the green part of the color table, everything looks the same.   Look at the size of the yellow bands vs the green band.  It's ridiculously different.  The default color map is very good with regards to these two issues.

ParaView comes with many optional color maps.  Unless there is an overriding reason, choose any of them except the Rainbow color map.  You do this through the Edit Color Map (a few icons below the Edit menu), then Preset (icon on the right, looks like a read heart).   My favorite is probably black body, although it only works with some simulations.  If you are looking for a color map that is more shiny (i.e., colorful), try rainbow desaturated.  But, realize that color blind folks will have issues with it.

Alan

-----Original Message-----
From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Alex Lindsay
Sent: Monday, April 25, 2016 11:34 AM
To: ParaView <paraview at paraview.org>
Subject: [EXTERNAL] [Paraview] Change default color mapping

Is there a way to change the default color mapping? The default is cool to warm, but I prefer blue to red rainbow. I saw in the manual directions for customizing properties, sources, filter, etc, but I think I need a little more help _______________________________________________
Powered by www.kitware.com

Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView

Search the list archives at: http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview

From wascott at sandia.gov  Fri Apr 29 20:28:37 2016
From: wascott at sandia.gov (Scott, W Alan)
Date: Sat, 30 Apr 2016 00:28:37 +0000
Subject: [Paraview] Trace recorder, save screenshot and background.
Message-ID: <24658c7133d74f29b31d47830b466979@ES01AMSNLNT.srn.sandia.gov>



When I create a script that exports a screenshot.  The trace option does not capture the commands that make the background white and the vtkblock magnitude colors key turned off.  Is there a work around for this?


Thanks,

Alan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160430/1509ee67/attachment.html>

From archaerolog at mail.ru  Sat Apr 30 04:39:36 2016
From: archaerolog at mail.ru (Gena Bug)
Date: Sat, 30 Apr 2016 11:39:36 +0300
Subject: [Paraview] pv freezes when merging blocks of angular periodic
 filter data
Message-ID: <57246F48.5020109@mail.ru>

Hi!

I was able to freeze Paraview by applying MergeBlocks filter to the data 
generated by AngularPeriodicFilter. In console I see a bunch of warnings:
{
Warning: In 
/home/kitware/dashboards/buildbot/paraview-debian6dash-linux-shared-release_opengl2_qt4_superbuild/build/paraview/src/paraview/VTK/Common/Core/vtkMappedDataArray.txx, 
line 47
20vtkPeriodicDataArrayIdE (0x6dce310): GetVoidPointer called. This is 
very expensive for vtkMappedDataArray subclasses, since the scalar array 
must be generated for each call. Consider using a 
vtkTypedDataArrayIterator instead.
}

Env: debian testing amd64, KF5, pv downloaded from the site.

From archaerolog at mail.ru  Sat Apr 30 05:03:20 2016
From: archaerolog at mail.ru (Gena Bug)
Date: Sat, 30 Apr 2016 12:03:20 +0300
Subject: [Paraview] pv freezes when merging blocks of angular periodic
 filter data
In-Reply-To: <57246F48.5020109@mail.ru>
References: <57246F48.5020109@mail.ru>
Message-ID: <572474D8.9040807@mail.ru>

UPD: Seems it somehow related to cell-data vector arrays, because it 
works with point-data arrays.

I attached a smallest example I came up with that could help. If you 
load the state-file you'll see the next pipeline:
test.vtp
AngularPeriodicFilter (with angle = 90 and axiz = Z)
CellDatatoPointData
MergeBlocks

That works. However if you remove CellDatatoPointData from this pipeline 
and try to merge the result of AngularPeriodicFilter you'll see the problem.

On 30.04.2016 11:39, Gena Bug wrote:
> Hi!
>
> I was able to freeze Paraview by applying MergeBlocks filter to the data
> generated by AngularPeriodicFilter. In console I see a bunch of warnings:
> {
> Warning: In
> /home/kitware/dashboards/buildbot/paraview-debian6dash-linux-shared-release_opengl2_qt4_superbuild/build/paraview/src/paraview/VTK/Common/Core/vtkMappedDataArray.txx,
> line 47
> 20vtkPeriodicDataArrayIdE (0x6dce310): GetVoidPointer called. This is
> very expensive for vtkMappedDataArray subclasses, since the scalar array
> must be generated for each call. Consider using a
> vtkTypedDataArrayIterator instead.
> }
>
> Env: debian testing amd64, KF5, pv downloaded from the site.
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview
>
-------------- next part --------------
<ParaView>
  <ServerManagerState version="5.0.1">
    <Proxy group="animation" type="AnimationScene" id="263" servers="16">
      <Property name="AnimationTime" id="263.AnimationTime" number_of_elements="1">
        <Element index="0" value="0"/>
      </Property>
      <Property name="Cues" id="263.Cues" number_of_elements="1">
        <Proxy value="265"/>
        <Domain name="groups" id="263.Cues.groups"/>
      </Property>
      <Property name="Duration" id="263.Duration" number_of_elements="1">
        <Element index="0" value="10"/>
      </Property>
      <Property name="EndTime" id="263.EndTime" number_of_elements="1">
        <Element index="0" value="1"/>
      </Property>
      <Property name="FramesPerTimestep" id="263.FramesPerTimestep" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="263.FramesPerTimestep.range"/>
      </Property>
      <Property name="GoToFirst" id="263.GoToFirst"/>
      <Property name="GoToLast" id="263.GoToLast"/>
      <Property name="GoToNext" id="263.GoToNext"/>
      <Property name="GoToPrevious" id="263.GoToPrevious"/>
      <Property name="LockEndTime" id="263.LockEndTime" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="263.LockEndTime.bool"/>
      </Property>
      <Property name="LockStartTime" id="263.LockStartTime" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="263.LockStartTime.bool"/>
      </Property>
      <Property name="Loop" id="263.Loop" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="263.Loop.bool"/>
      </Property>
      <Property name="NumberOfFrames" id="263.NumberOfFrames" number_of_elements="1">
        <Element index="0" value="10"/>
        <Domain name="range" id="263.NumberOfFrames.range"/>
      </Property>
      <Property name="Play" id="263.Play"/>
      <Property name="PlayMode" id="263.PlayMode" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="enum" id="263.PlayMode.enum">
          <Entry value="0" text="Sequence"/>
          <Entry value="1" text="Real Time"/>
          <Entry value="2" text="Snap To TimeSteps"/>
        </Domain>
      </Property>
      <Property name="StartTime" id="263.StartTime" number_of_elements="1">
        <Element index="0" value="0"/>
      </Property>
      <Property name="Stop" id="263.Stop"/>
      <Property name="TimeKeeper" id="263.TimeKeeper" number_of_elements="1">
        <Proxy value="259"/>
      </Property>
      <Property name="ViewModules" id="263.ViewModules" number_of_elements="2">
        <Proxy value="4766"/>
        <Proxy value="4766"/>
        <Domain name="groups" id="263.ViewModules.groups"/>
      </Property>
    </Proxy>
    <Proxy group="animation" type="TimeAnimationCue" id="265" servers="16">
      <Property name="AnimatedDomainName" id="265.AnimatedDomainName" number_of_elements="1">
        <Element index="0" value=""/>
      </Property>
      <Property name="AnimatedElement" id="265.AnimatedElement" number_of_elements="1">
        <Element index="0" value="0"/>
      </Property>
      <Property name="AnimatedPropertyName" id="265.AnimatedPropertyName" number_of_elements="1">
        <Element index="0" value="Time"/>
      </Property>
      <Property name="AnimatedProxy" id="265.AnimatedProxy" number_of_elements="1">
        <Proxy value="259"/>
        <Domain name="groups" id="265.AnimatedProxy.groups"/>
      </Property>
      <Property name="Enabled" id="265.Enabled" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="265.Enabled.bool"/>
      </Property>
      <Property name="EndTime" id="265.EndTime" number_of_elements="1">
        <Element index="0" value="1"/>
      </Property>
      <Property name="KeyFrames" id="265.KeyFrames">
        <Domain name="groups" id="265.KeyFrames.groups"/>
      </Property>
      <Property name="LastAddedKeyFrameIndex" id="265.LastAddedKeyFrameIndex"/>
      <Property name="StartTime" id="265.StartTime" number_of_elements="1">
        <Element index="0" value="0"/>
      </Property>
      <Property name="TimeMode" id="265.TimeMode" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="enum" id="265.TimeMode.enum">
          <Entry value="0" text="Normalized"/>
          <Entry value="1" text="Relative"/>
        </Domain>
      </Property>
      <Property name="UseAnimationTime" id="265.UseAnimationTime" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="265.UseAnimationTime.bool"/>
      </Property>
    </Proxy>
    <Proxy group="misc" type="ViewLayout" id="2863" servers="16">
      <Layout number_of_elements="1">
        <Item direction="0" fraction="0.5" view="4766"/>
      </Layout>
    </Proxy>
    <Proxy group="misc" type="RepresentationAnimationHelper" id="4756" servers="16">
      <Property name="Source" id="4756.Source" number_of_elements="1">
        <Proxy value="4744"/>
      </Property>
    </Proxy>
    <Proxy group="annotations" type="GridAxes3DActor" id="4764" servers="21">
      <Property name="AxesToLabel" id="4764.AxesToLabel" number_of_elements="1">
        <Element index="0" value="63"/>
        <Domain name="range" id="4764.AxesToLabel.range"/>
      </Property>
      <Property name="DataPosition" id="4764.DataPosition" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="4764.DataPosition.range"/>
      </Property>
      <Property name="DataScale" id="4764.DataScale" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="1"/>
        <Element index="2" value="1"/>
        <Domain name="range" id="4764.DataScale.range"/>
      </Property>
      <Property name="FacesToRender" id="4764.FacesToRender" number_of_elements="1">
        <Element index="0" value="63"/>
        <Domain name="range" id="4764.FacesToRender.range"/>
      </Property>
      <Property name="LabelUniqueEdgesOnly" id="4764.LabelUniqueEdgesOnly" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="4764.LabelUniqueEdgesOnly.bool"/>
      </Property>
      <Property name="ModelBounds" id="4764.ModelBounds" number_of_elements="6">
        <Element index="0" value="0"/>
        <Element index="1" value="1"/>
        <Element index="2" value="0"/>
        <Element index="3" value="1"/>
        <Element index="4" value="0"/>
        <Element index="5" value="1"/>
      </Property>
      <Property name="ModelTransformMatrix" id="4764.ModelTransformMatrix" number_of_elements="16">
        <Element index="0" value="1"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Element index="3" value="0"/>
        <Element index="4" value="0"/>
        <Element index="5" value="1"/>
        <Element index="6" value="0"/>
        <Element index="7" value="0"/>
        <Element index="8" value="0"/>
        <Element index="9" value="0"/>
        <Element index="10" value="1"/>
        <Element index="11" value="0"/>
        <Element index="12" value="0"/>
        <Element index="13" value="0"/>
        <Element index="14" value="0"/>
        <Element index="15" value="1"/>
      </Property>
      <Property name="ShowEdges" id="4764.ShowEdges" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="4764.ShowEdges.bool"/>
      </Property>
      <Property name="ShowGrid" id="4764.ShowGrid" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4764.ShowGrid.bool"/>
      </Property>
      <Property name="ShowTicks" id="4764.ShowTicks" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="4764.ShowTicks.bool"/>
      </Property>
      <Property name="UseModelTransform" id="4764.UseModelTransform" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="range" id="4764.UseModelTransform.range"/>
      </Property>
      <Property name="Visibility" id="4764.Visibility" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4764.Visibility.bool"/>
      </Property>
      <Property name="XAxisLabels" id="4764.XAxisLabels">
        <Domain name="scalar_range" id="4764.XAxisLabels.scalar_range"/>
      </Property>
      <Property name="XAxisNotation" id="4764.XAxisNotation" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="enum" id="4764.XAxisNotation.enum">
          <Entry value="0" text="Mixed"/>
          <Entry value="1" text="Scientific"/>
          <Entry value="2" text="Fixed"/>
        </Domain>
      </Property>
      <Property name="XAxisPrecision" id="4764.XAxisPrecision" number_of_elements="1">
        <Element index="0" value="2"/>
        <Domain name="range" id="4764.XAxisPrecision.range"/>
      </Property>
      <Property name="XAxisUseCustomLabels" id="4764.XAxisUseCustomLabels" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4764.XAxisUseCustomLabels.bool"/>
      </Property>
      <Property name="XTitle" id="4764.XTitle" number_of_elements="1">
        <Element index="0" value="X Axis"/>
      </Property>
      <Property name="YAxisLabels" id="4764.YAxisLabels">
        <Domain name="scalar_range" id="4764.YAxisLabels.scalar_range"/>
      </Property>
      <Property name="YAxisNotation" id="4764.YAxisNotation" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="enum" id="4764.YAxisNotation.enum">
          <Entry value="0" text="Mixed"/>
          <Entry value="1" text="Scientific"/>
          <Entry value="2" text="Fixed"/>
        </Domain>
      </Property>
      <Property name="YAxisPrecision" id="4764.YAxisPrecision" number_of_elements="1">
        <Element index="0" value="2"/>
        <Domain name="range" id="4764.YAxisPrecision.range"/>
      </Property>
      <Property name="YAxisUseCustomLabels" id="4764.YAxisUseCustomLabels" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4764.YAxisUseCustomLabels.bool"/>
      </Property>
      <Property name="YTitle" id="4764.YTitle" number_of_elements="1">
        <Element index="0" value="Y Axis"/>
      </Property>
      <Property name="ZAxisLabels" id="4764.ZAxisLabels">
        <Domain name="scalar_range" id="4764.ZAxisLabels.scalar_range"/>
      </Property>
      <Property name="ZAxisNotation" id="4764.ZAxisNotation" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="enum" id="4764.ZAxisNotation.enum">
          <Entry value="0" text="Mixed"/>
          <Entry value="1" text="Scientific"/>
          <Entry value="2" text="Fixed"/>
        </Domain>
      </Property>
      <Property name="ZAxisPrecision" id="4764.ZAxisPrecision" number_of_elements="1">
        <Element index="0" value="2"/>
        <Domain name="range" id="4764.ZAxisPrecision.range"/>
      </Property>
      <Property name="ZAxisUseCustomLabels" id="4764.ZAxisUseCustomLabels" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4764.ZAxisUseCustomLabels.bool"/>
      </Property>
      <Property name="ZTitle" id="4764.ZTitle" number_of_elements="1">
        <Element index="0" value="Z Axis"/>
      </Property>
      <Property name="CullBackface" id="4764.CullBackface" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4764.CullBackface.bool"/>
      </Property>
      <Property name="CullFrontface" id="4764.CullFrontface" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="4764.CullFrontface.bool"/>
      </Property>
      <Property name="GridColor" id="4764.GridColor" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="1"/>
        <Element index="2" value="1"/>
        <Domain name="range" id="4764.GridColor.range"/>
      </Property>
      <Property name="XLabelBold" id="4764.XLabelBold" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4764.XLabelBold.bool"/>
      </Property>
      <Property name="XLabelColor" id="4764.XLabelColor" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="1"/>
        <Element index="2" value="1"/>
        <Domain name="range" id="4764.XLabelColor.range"/>
      </Property>
      <Property name="XLabelFontFamily" id="4764.XLabelFontFamily" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="enum" id="4764.XLabelFontFamily.enum">
          <Entry value="0" text="Arial"/>
          <Entry value="1" text="Courier"/>
          <Entry value="2" text="Times"/>
        </Domain>
      </Property>
      <Property name="XLabelFontSize" id="4764.XLabelFontSize" number_of_elements="1">
        <Element index="0" value="12"/>
        <Domain name="range" id="4764.XLabelFontSize.range"/>
      </Property>
      <Property name="XLabelItalic" id="4764.XLabelItalic" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4764.XLabelItalic.bool"/>
      </Property>
      <Property name="XLabelOpacity" id="4764.XLabelOpacity" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="4764.XLabelOpacity.range"/>
      </Property>
      <Property name="XLabelShadow" id="4764.XLabelShadow" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4764.XLabelShadow.bool"/>
      </Property>
      <Property name="XTitleBold" id="4764.XTitleBold" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4764.XTitleBold.bool"/>
      </Property>
      <Property name="XTitleColor" id="4764.XTitleColor" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="1"/>
        <Element index="2" value="1"/>
        <Domain name="range" id="4764.XTitleColor.range"/>
      </Property>
      <Property name="XTitleFontFamily" id="4764.XTitleFontFamily" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="enum" id="4764.XTitleFontFamily.enum">
          <Entry value="0" text="Arial"/>
          <Entry value="1" text="Courier"/>
          <Entry value="2" text="Times"/>
        </Domain>
      </Property>
      <Property name="XTitleFontSize" id="4764.XTitleFontSize" number_of_elements="1">
        <Element index="0" value="12"/>
        <Domain name="range" id="4764.XTitleFontSize.range"/>
      </Property>
      <Property name="XTitleItalic" id="4764.XTitleItalic" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4764.XTitleItalic.bool"/>
      </Property>
      <Property name="XTitleOpacity" id="4764.XTitleOpacity" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="4764.XTitleOpacity.range"/>
      </Property>
      <Property name="XTitleShadow" id="4764.XTitleShadow" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4764.XTitleShadow.bool"/>
      </Property>
      <Property name="YLabelBold" id="4764.YLabelBold" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4764.YLabelBold.bool"/>
      </Property>
      <Property name="YLabelColor" id="4764.YLabelColor" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="1"/>
        <Element index="2" value="1"/>
        <Domain name="range" id="4764.YLabelColor.range"/>
      </Property>
      <Property name="YLabelFontFamily" id="4764.YLabelFontFamily" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="enum" id="4764.YLabelFontFamily.enum">
          <Entry value="0" text="Arial"/>
          <Entry value="1" text="Courier"/>
          <Entry value="2" text="Times"/>
        </Domain>
      </Property>
      <Property name="YLabelFontSize" id="4764.YLabelFontSize" number_of_elements="1">
        <Element index="0" value="12"/>
        <Domain name="range" id="4764.YLabelFontSize.range"/>
      </Property>
      <Property name="YLabelItalic" id="4764.YLabelItalic" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4764.YLabelItalic.bool"/>
      </Property>
      <Property name="YLabelOpacity" id="4764.YLabelOpacity" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="4764.YLabelOpacity.range"/>
      </Property>
      <Property name="YLabelShadow" id="4764.YLabelShadow" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4764.YLabelShadow.bool"/>
      </Property>
      <Property name="YTitleBold" id="4764.YTitleBold" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4764.YTitleBold.bool"/>
      </Property>
      <Property name="YTitleColor" id="4764.YTitleColor" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="1"/>
        <Element index="2" value="1"/>
        <Domain name="range" id="4764.YTitleColor.range"/>
      </Property>
      <Property name="YTitleFontFamily" id="4764.YTitleFontFamily" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="enum" id="4764.YTitleFontFamily.enum">
          <Entry value="0" text="Arial"/>
          <Entry value="1" text="Courier"/>
          <Entry value="2" text="Times"/>
        </Domain>
      </Property>
      <Property name="YTitleFontSize" id="4764.YTitleFontSize" number_of_elements="1">
        <Element index="0" value="12"/>
        <Domain name="range" id="4764.YTitleFontSize.range"/>
      </Property>
      <Property name="YTitleItalic" id="4764.YTitleItalic" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4764.YTitleItalic.bool"/>
      </Property>
      <Property name="YTitleOpacity" id="4764.YTitleOpacity" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="4764.YTitleOpacity.range"/>
      </Property>
      <Property name="YTitleShadow" id="4764.YTitleShadow" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4764.YTitleShadow.bool"/>
      </Property>
      <Property name="ZLabelBold" id="4764.ZLabelBold" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4764.ZLabelBold.bool"/>
      </Property>
      <Property name="ZLabelColor" id="4764.ZLabelColor" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="1"/>
        <Element index="2" value="1"/>
        <Domain name="range" id="4764.ZLabelColor.range"/>
      </Property>
      <Property name="ZLabelFontFamily" id="4764.ZLabelFontFamily" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="enum" id="4764.ZLabelFontFamily.enum">
          <Entry value="0" text="Arial"/>
          <Entry value="1" text="Courier"/>
          <Entry value="2" text="Times"/>
        </Domain>
      </Property>
      <Property name="ZLabelFontSize" id="4764.ZLabelFontSize" number_of_elements="1">
        <Element index="0" value="12"/>
        <Domain name="range" id="4764.ZLabelFontSize.range"/>
      </Property>
      <Property name="ZLabelItalic" id="4764.ZLabelItalic" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4764.ZLabelItalic.bool"/>
      </Property>
      <Property name="ZLabelOpacity" id="4764.ZLabelOpacity" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="4764.ZLabelOpacity.range"/>
      </Property>
      <Property name="ZLabelShadow" id="4764.ZLabelShadow" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4764.ZLabelShadow.bool"/>
      </Property>
      <Property name="ZTitleBold" id="4764.ZTitleBold" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4764.ZTitleBold.bool"/>
      </Property>
      <Property name="ZTitleColor" id="4764.ZTitleColor" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="1"/>
        <Element index="2" value="1"/>
        <Domain name="range" id="4764.ZTitleColor.range"/>
      </Property>
      <Property name="ZTitleFontFamily" id="4764.ZTitleFontFamily" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="enum" id="4764.ZTitleFontFamily.enum">
          <Entry value="0" text="Arial"/>
          <Entry value="1" text="Courier"/>
          <Entry value="2" text="Times"/>
        </Domain>
      </Property>
      <Property name="ZTitleFontSize" id="4764.ZTitleFontSize" number_of_elements="1">
        <Element index="0" value="12"/>
        <Domain name="range" id="4764.ZTitleFontSize.range"/>
      </Property>
      <Property name="ZTitleItalic" id="4764.ZTitleItalic" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4764.ZTitleItalic.bool"/>
      </Property>
      <Property name="ZTitleOpacity" id="4764.ZTitleOpacity" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="4764.ZTitleOpacity.range"/>
      </Property>
      <Property name="ZTitleShadow" id="4764.ZTitleShadow" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4764.ZTitleShadow.bool"/>
      </Property>
    </Proxy>
    <Proxy group="sources" type="ArrowSource" id="4862" servers="1">
      <Property name="Invert" id="4862.Invert" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4862.Invert.bool"/>
      </Property>
      <Property name="ShaftRadius" id="4862.ShaftRadius" number_of_elements="1">
        <Element index="0" value="0.03"/>
        <Domain name="range" id="4862.ShaftRadius.range"/>
      </Property>
      <Property name="ShaftResolution" id="4862.ShaftResolution" number_of_elements="1">
        <Element index="0" value="6"/>
        <Domain name="range" id="4862.ShaftResolution.range"/>
      </Property>
      <Property name="TipLength" id="4862.TipLength" number_of_elements="1">
        <Element index="0" value="0.35"/>
        <Domain name="range" id="4862.TipLength.range"/>
      </Property>
      <Property name="TipRadius" id="4862.TipRadius" number_of_elements="1">
        <Element index="0" value="0.1"/>
        <Domain name="range" id="4862.TipRadius.range"/>
      </Property>
      <Property name="TipResolution" id="4862.TipResolution" number_of_elements="1">
        <Element index="0" value="6"/>
        <Domain name="range" id="4862.TipResolution.range"/>
      </Property>
    </Proxy>
    <Proxy group="sources" type="ConeSource" id="4873" servers="1">
      <Property name="Capping" id="4873.Capping" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="4873.Capping.bool"/>
      </Property>
      <Property name="Center" id="4873.Center" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="4873.Center.range"/>
      </Property>
      <Property name="Direction" id="4873.Direction" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="4873.Direction.range"/>
      </Property>
      <Property name="Height" id="4873.Height" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="4873.Height.range"/>
      </Property>
      <Property name="Radius" id="4873.Radius" number_of_elements="1">
        <Element index="0" value="0.5"/>
        <Domain name="range" id="4873.Radius.range"/>
      </Property>
      <Property name="Resolution" id="4873.Resolution" number_of_elements="1">
        <Element index="0" value="6"/>
        <Domain name="range" id="4873.Resolution.range"/>
      </Property>
    </Proxy>
    <Proxy group="sources" type="CubeSource" id="4884" servers="1">
      <Property name="Center" id="4884.Center" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="4884.Center.range"/>
      </Property>
      <Property name="XLength" id="4884.XLength" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="4884.XLength.range"/>
      </Property>
      <Property name="YLength" id="4884.YLength" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="4884.YLength.range"/>
      </Property>
      <Property name="ZLength" id="4884.ZLength" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="4884.ZLength.range"/>
      </Property>
    </Proxy>
    <Proxy group="sources" type="CylinderSource" id="4895" servers="1">
      <Property name="Capping" id="4895.Capping" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="4895.Capping.bool"/>
      </Property>
      <Property name="Center" id="4895.Center" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="4895.Center.range"/>
      </Property>
      <Property name="Height" id="4895.Height" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="4895.Height.range"/>
      </Property>
      <Property name="Radius" id="4895.Radius" number_of_elements="1">
        <Element index="0" value="0.5"/>
        <Domain name="range" id="4895.Radius.range"/>
      </Property>
      <Property name="Resolution" id="4895.Resolution" number_of_elements="1">
        <Element index="0" value="6"/>
        <Domain name="range" id="4895.Resolution.range"/>
      </Property>
    </Proxy>
    <Proxy group="sources" type="LineSource" id="4906" servers="1">
      <Property name="Point1" id="4906.Point1" number_of_elements="3">
        <Element index="0" value="-0.5"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="4906.Point1.range"/>
      </Property>
      <Property name="Point2" id="4906.Point2" number_of_elements="3">
        <Element index="0" value="0.5"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="4906.Point2.range"/>
      </Property>
      <Property name="Resolution" id="4906.Resolution" number_of_elements="1">
        <Element index="0" value="6"/>
        <Domain name="range" id="4906.Resolution.range"/>
      </Property>
    </Proxy>
    <Proxy group="sources" type="SphereSource" id="4917" servers="1">
      <Property name="Center" id="4917.Center" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="4917.Center.range"/>
      </Property>
      <Property name="EndPhi" id="4917.EndPhi" number_of_elements="1">
        <Element index="0" value="180"/>
        <Domain name="range" id="4917.EndPhi.range"/>
      </Property>
      <Property name="EndTheta" id="4917.EndTheta" number_of_elements="1">
        <Element index="0" value="360"/>
        <Domain name="range" id="4917.EndTheta.range"/>
      </Property>
      <Property name="PhiResolution" id="4917.PhiResolution" number_of_elements="1">
        <Element index="0" value="8"/>
        <Domain name="range" id="4917.PhiResolution.range"/>
      </Property>
      <Property name="Radius" id="4917.Radius" number_of_elements="1">
        <Element index="0" value="0.5"/>
        <Domain name="range" id="4917.Radius.range"/>
      </Property>
      <Property name="StartPhi" id="4917.StartPhi" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="range" id="4917.StartPhi.range"/>
      </Property>
      <Property name="StartTheta" id="4917.StartTheta" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="range" id="4917.StartTheta.range"/>
      </Property>
      <Property name="ThetaResolution" id="4917.ThetaResolution" number_of_elements="1">
        <Element index="0" value="8"/>
        <Domain name="range" id="4917.ThetaResolution.range"/>
      </Property>
    </Proxy>
    <Proxy group="sources" type="GlyphSource2D" id="4928" servers="1">
      <Property name="Center" id="4928.Center" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="4928.Center.range"/>
      </Property>
      <Property name="Filled" id="4928.Filled" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4928.Filled.bool"/>
      </Property>
      <Property name="GlyphType" id="4928.GlyphType" number_of_elements="1">
        <Element index="0" value="9"/>
        <Domain name="enum" id="4928.GlyphType.enum">
          <Entry value="1" text="Vertex"/>
          <Entry value="2" text="Dash"/>
          <Entry value="3" text="Cross"/>
          <Entry value="4" text="ThickCross"/>
          <Entry value="5" text="Triangle"/>
          <Entry value="6" text="Square"/>
          <Entry value="7" text="Circle"/>
          <Entry value="8" text="Diamond"/>
          <Entry value="9" text="Arrow"/>
          <Entry value="10" text="ThickArrow"/>
          <Entry value="11" text="HookedArrow"/>
          <Entry value="12" text="EdgeArrow"/>
        </Domain>
      </Property>
    </Proxy>
    <Proxy group="piecewise_functions" type="PiecewiseFunction" id="4961" servers="21">
      <Property name="AllowDuplicateScalars" id="4961.AllowDuplicateScalars" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="4961.AllowDuplicateScalars.bool"/>
      </Property>
      <Property name="Points" id="4961.Points" number_of_elements="8">
        <Element index="0" value="9.78115956672179e-10"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0.5"/>
        <Element index="3" value="0"/>
        <Element index="4" value="1.3364466998078e-05"/>
        <Element index="5" value="1"/>
        <Element index="6" value="0.5"/>
        <Element index="7" value="0"/>
      </Property>
      <Property name="ScalarRangeInitialized" id="4961.ScalarRangeInitialized" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4961.ScalarRangeInitialized.bool"/>
      </Property>
    </Proxy>
    <Proxy group="piecewise_functions" type="PiecewiseFunction" id="4962" servers="21">
      <Property name="AllowDuplicateScalars" id="4962.AllowDuplicateScalars" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="4962.AllowDuplicateScalars.bool"/>
      </Property>
      <Property name="Points" id="4962.Points" number_of_elements="8">
        <Element index="0" value="9.78115956672179e-10"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0.5"/>
        <Element index="3" value="0"/>
        <Element index="4" value="1.3364466998078e-05"/>
        <Element index="5" value="1"/>
        <Element index="6" value="0.5"/>
        <Element index="7" value="0"/>
      </Property>
      <Property name="ScalarRangeInitialized" id="4962.ScalarRangeInitialized" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4962.ScalarRangeInitialized.bool"/>
      </Property>
    </Proxy>
    <Proxy group="misc" type="RepresentationAnimationHelper" id="5029" servers="16">
      <Property name="Source" id="5029.Source" number_of_elements="1">
        <Proxy value="5018"/>
      </Property>
    </Proxy>
    <Proxy group="sources" type="ArrowSource" id="5041" servers="1">
      <Property name="Invert" id="5041.Invert" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5041.Invert.bool"/>
      </Property>
      <Property name="ShaftRadius" id="5041.ShaftRadius" number_of_elements="1">
        <Element index="0" value="0.03"/>
        <Domain name="range" id="5041.ShaftRadius.range"/>
      </Property>
      <Property name="ShaftResolution" id="5041.ShaftResolution" number_of_elements="1">
        <Element index="0" value="6"/>
        <Domain name="range" id="5041.ShaftResolution.range"/>
      </Property>
      <Property name="TipLength" id="5041.TipLength" number_of_elements="1">
        <Element index="0" value="0.35"/>
        <Domain name="range" id="5041.TipLength.range"/>
      </Property>
      <Property name="TipRadius" id="5041.TipRadius" number_of_elements="1">
        <Element index="0" value="0.1"/>
        <Domain name="range" id="5041.TipRadius.range"/>
      </Property>
      <Property name="TipResolution" id="5041.TipResolution" number_of_elements="1">
        <Element index="0" value="6"/>
        <Domain name="range" id="5041.TipResolution.range"/>
      </Property>
    </Proxy>
    <Proxy group="sources" type="ConeSource" id="5052" servers="1">
      <Property name="Capping" id="5052.Capping" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="5052.Capping.bool"/>
      </Property>
      <Property name="Center" id="5052.Center" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="5052.Center.range"/>
      </Property>
      <Property name="Direction" id="5052.Direction" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="5052.Direction.range"/>
      </Property>
      <Property name="Height" id="5052.Height" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="5052.Height.range"/>
      </Property>
      <Property name="Radius" id="5052.Radius" number_of_elements="1">
        <Element index="0" value="0.5"/>
        <Domain name="range" id="5052.Radius.range"/>
      </Property>
      <Property name="Resolution" id="5052.Resolution" number_of_elements="1">
        <Element index="0" value="6"/>
        <Domain name="range" id="5052.Resolution.range"/>
      </Property>
    </Proxy>
    <Proxy group="sources" type="CubeSource" id="5063" servers="1">
      <Property name="Center" id="5063.Center" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="5063.Center.range"/>
      </Property>
      <Property name="XLength" id="5063.XLength" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="5063.XLength.range"/>
      </Property>
      <Property name="YLength" id="5063.YLength" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="5063.YLength.range"/>
      </Property>
      <Property name="ZLength" id="5063.ZLength" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="5063.ZLength.range"/>
      </Property>
    </Proxy>
    <Proxy group="sources" type="CylinderSource" id="5074" servers="1">
      <Property name="Capping" id="5074.Capping" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="5074.Capping.bool"/>
      </Property>
      <Property name="Center" id="5074.Center" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="5074.Center.range"/>
      </Property>
      <Property name="Height" id="5074.Height" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="5074.Height.range"/>
      </Property>
      <Property name="Radius" id="5074.Radius" number_of_elements="1">
        <Element index="0" value="0.5"/>
        <Domain name="range" id="5074.Radius.range"/>
      </Property>
      <Property name="Resolution" id="5074.Resolution" number_of_elements="1">
        <Element index="0" value="6"/>
        <Domain name="range" id="5074.Resolution.range"/>
      </Property>
    </Proxy>
    <Proxy group="sources" type="LineSource" id="5085" servers="1">
      <Property name="Point1" id="5085.Point1" number_of_elements="3">
        <Element index="0" value="-0.5"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="5085.Point1.range"/>
      </Property>
      <Property name="Point2" id="5085.Point2" number_of_elements="3">
        <Element index="0" value="0.5"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="5085.Point2.range"/>
      </Property>
      <Property name="Resolution" id="5085.Resolution" number_of_elements="1">
        <Element index="0" value="6"/>
        <Domain name="range" id="5085.Resolution.range"/>
      </Property>
    </Proxy>
    <Proxy group="sources" type="SphereSource" id="5096" servers="1">
      <Property name="Center" id="5096.Center" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="5096.Center.range"/>
      </Property>
      <Property name="EndPhi" id="5096.EndPhi" number_of_elements="1">
        <Element index="0" value="180"/>
        <Domain name="range" id="5096.EndPhi.range"/>
      </Property>
      <Property name="EndTheta" id="5096.EndTheta" number_of_elements="1">
        <Element index="0" value="360"/>
        <Domain name="range" id="5096.EndTheta.range"/>
      </Property>
      <Property name="PhiResolution" id="5096.PhiResolution" number_of_elements="1">
        <Element index="0" value="8"/>
        <Domain name="range" id="5096.PhiResolution.range"/>
      </Property>
      <Property name="Radius" id="5096.Radius" number_of_elements="1">
        <Element index="0" value="0.5"/>
        <Domain name="range" id="5096.Radius.range"/>
      </Property>
      <Property name="StartPhi" id="5096.StartPhi" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="range" id="5096.StartPhi.range"/>
      </Property>
      <Property name="StartTheta" id="5096.StartTheta" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="range" id="5096.StartTheta.range"/>
      </Property>
      <Property name="ThetaResolution" id="5096.ThetaResolution" number_of_elements="1">
        <Element index="0" value="8"/>
        <Domain name="range" id="5096.ThetaResolution.range"/>
      </Property>
    </Proxy>
    <Proxy group="sources" type="GlyphSource2D" id="5107" servers="1">
      <Property name="Center" id="5107.Center" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="5107.Center.range"/>
      </Property>
      <Property name="Filled" id="5107.Filled" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5107.Filled.bool"/>
      </Property>
      <Property name="GlyphType" id="5107.GlyphType" number_of_elements="1">
        <Element index="0" value="9"/>
        <Domain name="enum" id="5107.GlyphType.enum">
          <Entry value="1" text="Vertex"/>
          <Entry value="2" text="Dash"/>
          <Entry value="3" text="Cross"/>
          <Entry value="4" text="ThickCross"/>
          <Entry value="5" text="Triangle"/>
          <Entry value="6" text="Square"/>
          <Entry value="7" text="Circle"/>
          <Entry value="8" text="Diamond"/>
          <Entry value="9" text="Arrow"/>
          <Entry value="10" text="ThickArrow"/>
          <Entry value="11" text="HookedArrow"/>
          <Entry value="12" text="EdgeArrow"/>
        </Domain>
      </Property>
    </Proxy>
    <Proxy group="piecewise_functions" type="PiecewiseFunction" id="5140" servers="21">
      <Property name="AllowDuplicateScalars" id="5140.AllowDuplicateScalars" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="5140.AllowDuplicateScalars.bool"/>
      </Property>
      <Property name="Points" id="5140.Points" number_of_elements="8">
        <Element index="0" value="9.78115956672179e-10"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0.5"/>
        <Element index="3" value="0"/>
        <Element index="4" value="1.3364466998078e-05"/>
        <Element index="5" value="1"/>
        <Element index="6" value="0.5"/>
        <Element index="7" value="0"/>
      </Property>
      <Property name="ScalarRangeInitialized" id="5140.ScalarRangeInitialized" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5140.ScalarRangeInitialized.bool"/>
      </Property>
    </Proxy>
    <Proxy group="piecewise_functions" type="PiecewiseFunction" id="5141" servers="21">
      <Property name="AllowDuplicateScalars" id="5141.AllowDuplicateScalars" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="5141.AllowDuplicateScalars.bool"/>
      </Property>
      <Property name="Points" id="5141.Points" number_of_elements="8">
        <Element index="0" value="9.78115956672179e-10"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0.5"/>
        <Element index="3" value="0"/>
        <Element index="4" value="1.3364466998078e-05"/>
        <Element index="5" value="1"/>
        <Element index="6" value="0.5"/>
        <Element index="7" value="0"/>
      </Property>
      <Property name="ScalarRangeInitialized" id="5141.ScalarRangeInitialized" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5141.ScalarRangeInitialized.bool"/>
      </Property>
    </Proxy>
    <Proxy group="misc" type="RepresentationAnimationHelper" id="5208" servers="16">
      <Property name="Source" id="5208.Source" number_of_elements="1">
        <Proxy value="5197"/>
      </Property>
    </Proxy>
    <Proxy group="sources" type="ArrowSource" id="5220" servers="1">
      <Property name="Invert" id="5220.Invert" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5220.Invert.bool"/>
      </Property>
      <Property name="ShaftRadius" id="5220.ShaftRadius" number_of_elements="1">
        <Element index="0" value="0.03"/>
        <Domain name="range" id="5220.ShaftRadius.range"/>
      </Property>
      <Property name="ShaftResolution" id="5220.ShaftResolution" number_of_elements="1">
        <Element index="0" value="6"/>
        <Domain name="range" id="5220.ShaftResolution.range"/>
      </Property>
      <Property name="TipLength" id="5220.TipLength" number_of_elements="1">
        <Element index="0" value="0.35"/>
        <Domain name="range" id="5220.TipLength.range"/>
      </Property>
      <Property name="TipRadius" id="5220.TipRadius" number_of_elements="1">
        <Element index="0" value="0.1"/>
        <Domain name="range" id="5220.TipRadius.range"/>
      </Property>
      <Property name="TipResolution" id="5220.TipResolution" number_of_elements="1">
        <Element index="0" value="6"/>
        <Domain name="range" id="5220.TipResolution.range"/>
      </Property>
    </Proxy>
    <Proxy group="sources" type="ConeSource" id="5231" servers="1">
      <Property name="Capping" id="5231.Capping" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="5231.Capping.bool"/>
      </Property>
      <Property name="Center" id="5231.Center" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="5231.Center.range"/>
      </Property>
      <Property name="Direction" id="5231.Direction" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="5231.Direction.range"/>
      </Property>
      <Property name="Height" id="5231.Height" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="5231.Height.range"/>
      </Property>
      <Property name="Radius" id="5231.Radius" number_of_elements="1">
        <Element index="0" value="0.5"/>
        <Domain name="range" id="5231.Radius.range"/>
      </Property>
      <Property name="Resolution" id="5231.Resolution" number_of_elements="1">
        <Element index="0" value="6"/>
        <Domain name="range" id="5231.Resolution.range"/>
      </Property>
    </Proxy>
    <Proxy group="sources" type="CubeSource" id="5242" servers="1">
      <Property name="Center" id="5242.Center" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="5242.Center.range"/>
      </Property>
      <Property name="XLength" id="5242.XLength" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="5242.XLength.range"/>
      </Property>
      <Property name="YLength" id="5242.YLength" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="5242.YLength.range"/>
      </Property>
      <Property name="ZLength" id="5242.ZLength" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="5242.ZLength.range"/>
      </Property>
    </Proxy>
    <Proxy group="sources" type="CylinderSource" id="5253" servers="1">
      <Property name="Capping" id="5253.Capping" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="5253.Capping.bool"/>
      </Property>
      <Property name="Center" id="5253.Center" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="5253.Center.range"/>
      </Property>
      <Property name="Height" id="5253.Height" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="5253.Height.range"/>
      </Property>
      <Property name="Radius" id="5253.Radius" number_of_elements="1">
        <Element index="0" value="0.5"/>
        <Domain name="range" id="5253.Radius.range"/>
      </Property>
      <Property name="Resolution" id="5253.Resolution" number_of_elements="1">
        <Element index="0" value="6"/>
        <Domain name="range" id="5253.Resolution.range"/>
      </Property>
    </Proxy>
    <Proxy group="sources" type="LineSource" id="5264" servers="1">
      <Property name="Point1" id="5264.Point1" number_of_elements="3">
        <Element index="0" value="-0.5"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="5264.Point1.range"/>
      </Property>
      <Property name="Point2" id="5264.Point2" number_of_elements="3">
        <Element index="0" value="0.5"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="5264.Point2.range"/>
      </Property>
      <Property name="Resolution" id="5264.Resolution" number_of_elements="1">
        <Element index="0" value="6"/>
        <Domain name="range" id="5264.Resolution.range"/>
      </Property>
    </Proxy>
    <Proxy group="sources" type="SphereSource" id="5275" servers="1">
      <Property name="Center" id="5275.Center" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="5275.Center.range"/>
      </Property>
      <Property name="EndPhi" id="5275.EndPhi" number_of_elements="1">
        <Element index="0" value="180"/>
        <Domain name="range" id="5275.EndPhi.range"/>
      </Property>
      <Property name="EndTheta" id="5275.EndTheta" number_of_elements="1">
        <Element index="0" value="360"/>
        <Domain name="range" id="5275.EndTheta.range"/>
      </Property>
      <Property name="PhiResolution" id="5275.PhiResolution" number_of_elements="1">
        <Element index="0" value="8"/>
        <Domain name="range" id="5275.PhiResolution.range"/>
      </Property>
      <Property name="Radius" id="5275.Radius" number_of_elements="1">
        <Element index="0" value="0.5"/>
        <Domain name="range" id="5275.Radius.range"/>
      </Property>
      <Property name="StartPhi" id="5275.StartPhi" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="range" id="5275.StartPhi.range"/>
      </Property>
      <Property name="StartTheta" id="5275.StartTheta" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="range" id="5275.StartTheta.range"/>
      </Property>
      <Property name="ThetaResolution" id="5275.ThetaResolution" number_of_elements="1">
        <Element index="0" value="8"/>
        <Domain name="range" id="5275.ThetaResolution.range"/>
      </Property>
    </Proxy>
    <Proxy group="sources" type="GlyphSource2D" id="5286" servers="1">
      <Property name="Center" id="5286.Center" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="5286.Center.range"/>
      </Property>
      <Property name="Filled" id="5286.Filled" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5286.Filled.bool"/>
      </Property>
      <Property name="GlyphType" id="5286.GlyphType" number_of_elements="1">
        <Element index="0" value="9"/>
        <Domain name="enum" id="5286.GlyphType.enum">
          <Entry value="1" text="Vertex"/>
          <Entry value="2" text="Dash"/>
          <Entry value="3" text="Cross"/>
          <Entry value="4" text="ThickCross"/>
          <Entry value="5" text="Triangle"/>
          <Entry value="6" text="Square"/>
          <Entry value="7" text="Circle"/>
          <Entry value="8" text="Diamond"/>
          <Entry value="9" text="Arrow"/>
          <Entry value="10" text="ThickArrow"/>
          <Entry value="11" text="HookedArrow"/>
          <Entry value="12" text="EdgeArrow"/>
        </Domain>
      </Property>
    </Proxy>
    <Proxy group="piecewise_functions" type="PiecewiseFunction" id="5319" servers="21">
      <Property name="AllowDuplicateScalars" id="5319.AllowDuplicateScalars" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="5319.AllowDuplicateScalars.bool"/>
      </Property>
      <Property name="Points" id="5319.Points" number_of_elements="8">
        <Element index="0" value="9.78115956672179e-10"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0.5"/>
        <Element index="3" value="0"/>
        <Element index="4" value="1.3364466998078e-05"/>
        <Element index="5" value="1"/>
        <Element index="6" value="0.5"/>
        <Element index="7" value="0"/>
      </Property>
      <Property name="ScalarRangeInitialized" id="5319.ScalarRangeInitialized" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5319.ScalarRangeInitialized.bool"/>
      </Property>
    </Proxy>
    <Proxy group="piecewise_functions" type="PiecewiseFunction" id="5320" servers="21">
      <Property name="AllowDuplicateScalars" id="5320.AllowDuplicateScalars" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="5320.AllowDuplicateScalars.bool"/>
      </Property>
      <Property name="Points" id="5320.Points" number_of_elements="8">
        <Element index="0" value="9.78115956672179e-10"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0.5"/>
        <Element index="3" value="0"/>
        <Element index="4" value="1.3364466998078e-05"/>
        <Element index="5" value="1"/>
        <Element index="6" value="0.5"/>
        <Element index="7" value="0"/>
      </Property>
      <Property name="ScalarRangeInitialized" id="5320.ScalarRangeInitialized" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5320.ScalarRangeInitialized.bool"/>
      </Property>
    </Proxy>
    <Proxy group="misc" type="RepresentationAnimationHelper" id="5387" servers="16">
      <Property name="Source" id="5387.Source" number_of_elements="1">
        <Proxy value="5376"/>
      </Property>
    </Proxy>
    <Proxy group="sources" type="ArrowSource" id="5399" servers="1">
      <Property name="Invert" id="5399.Invert" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5399.Invert.bool"/>
      </Property>
      <Property name="ShaftRadius" id="5399.ShaftRadius" number_of_elements="1">
        <Element index="0" value="0.03"/>
        <Domain name="range" id="5399.ShaftRadius.range"/>
      </Property>
      <Property name="ShaftResolution" id="5399.ShaftResolution" number_of_elements="1">
        <Element index="0" value="6"/>
        <Domain name="range" id="5399.ShaftResolution.range"/>
      </Property>
      <Property name="TipLength" id="5399.TipLength" number_of_elements="1">
        <Element index="0" value="0.35"/>
        <Domain name="range" id="5399.TipLength.range"/>
      </Property>
      <Property name="TipRadius" id="5399.TipRadius" number_of_elements="1">
        <Element index="0" value="0.1"/>
        <Domain name="range" id="5399.TipRadius.range"/>
      </Property>
      <Property name="TipResolution" id="5399.TipResolution" number_of_elements="1">
        <Element index="0" value="6"/>
        <Domain name="range" id="5399.TipResolution.range"/>
      </Property>
    </Proxy>
    <Proxy group="sources" type="ConeSource" id="5410" servers="1">
      <Property name="Capping" id="5410.Capping" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="5410.Capping.bool"/>
      </Property>
      <Property name="Center" id="5410.Center" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="5410.Center.range"/>
      </Property>
      <Property name="Direction" id="5410.Direction" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="5410.Direction.range"/>
      </Property>
      <Property name="Height" id="5410.Height" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="5410.Height.range"/>
      </Property>
      <Property name="Radius" id="5410.Radius" number_of_elements="1">
        <Element index="0" value="0.5"/>
        <Domain name="range" id="5410.Radius.range"/>
      </Property>
      <Property name="Resolution" id="5410.Resolution" number_of_elements="1">
        <Element index="0" value="6"/>
        <Domain name="range" id="5410.Resolution.range"/>
      </Property>
    </Proxy>
    <Proxy group="sources" type="CubeSource" id="5421" servers="1">
      <Property name="Center" id="5421.Center" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="5421.Center.range"/>
      </Property>
      <Property name="XLength" id="5421.XLength" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="5421.XLength.range"/>
      </Property>
      <Property name="YLength" id="5421.YLength" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="5421.YLength.range"/>
      </Property>
      <Property name="ZLength" id="5421.ZLength" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="5421.ZLength.range"/>
      </Property>
    </Proxy>
    <Proxy group="sources" type="CylinderSource" id="5432" servers="1">
      <Property name="Capping" id="5432.Capping" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="5432.Capping.bool"/>
      </Property>
      <Property name="Center" id="5432.Center" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="5432.Center.range"/>
      </Property>
      <Property name="Height" id="5432.Height" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="5432.Height.range"/>
      </Property>
      <Property name="Radius" id="5432.Radius" number_of_elements="1">
        <Element index="0" value="0.5"/>
        <Domain name="range" id="5432.Radius.range"/>
      </Property>
      <Property name="Resolution" id="5432.Resolution" number_of_elements="1">
        <Element index="0" value="6"/>
        <Domain name="range" id="5432.Resolution.range"/>
      </Property>
    </Proxy>
    <Proxy group="sources" type="LineSource" id="5443" servers="1">
      <Property name="Point1" id="5443.Point1" number_of_elements="3">
        <Element index="0" value="-0.5"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="5443.Point1.range"/>
      </Property>
      <Property name="Point2" id="5443.Point2" number_of_elements="3">
        <Element index="0" value="0.5"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="5443.Point2.range"/>
      </Property>
      <Property name="Resolution" id="5443.Resolution" number_of_elements="1">
        <Element index="0" value="6"/>
        <Domain name="range" id="5443.Resolution.range"/>
      </Property>
    </Proxy>
    <Proxy group="sources" type="SphereSource" id="5454" servers="1">
      <Property name="Center" id="5454.Center" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="5454.Center.range"/>
      </Property>
      <Property name="EndPhi" id="5454.EndPhi" number_of_elements="1">
        <Element index="0" value="180"/>
        <Domain name="range" id="5454.EndPhi.range"/>
      </Property>
      <Property name="EndTheta" id="5454.EndTheta" number_of_elements="1">
        <Element index="0" value="360"/>
        <Domain name="range" id="5454.EndTheta.range"/>
      </Property>
      <Property name="PhiResolution" id="5454.PhiResolution" number_of_elements="1">
        <Element index="0" value="8"/>
        <Domain name="range" id="5454.PhiResolution.range"/>
      </Property>
      <Property name="Radius" id="5454.Radius" number_of_elements="1">
        <Element index="0" value="0.5"/>
        <Domain name="range" id="5454.Radius.range"/>
      </Property>
      <Property name="StartPhi" id="5454.StartPhi" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="range" id="5454.StartPhi.range"/>
      </Property>
      <Property name="StartTheta" id="5454.StartTheta" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="range" id="5454.StartTheta.range"/>
      </Property>
      <Property name="ThetaResolution" id="5454.ThetaResolution" number_of_elements="1">
        <Element index="0" value="8"/>
        <Domain name="range" id="5454.ThetaResolution.range"/>
      </Property>
    </Proxy>
    <Proxy group="sources" type="GlyphSource2D" id="5465" servers="1">
      <Property name="Center" id="5465.Center" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="5465.Center.range"/>
      </Property>
      <Property name="Filled" id="5465.Filled" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5465.Filled.bool"/>
      </Property>
      <Property name="GlyphType" id="5465.GlyphType" number_of_elements="1">
        <Element index="0" value="9"/>
        <Domain name="enum" id="5465.GlyphType.enum">
          <Entry value="1" text="Vertex"/>
          <Entry value="2" text="Dash"/>
          <Entry value="3" text="Cross"/>
          <Entry value="4" text="ThickCross"/>
          <Entry value="5" text="Triangle"/>
          <Entry value="6" text="Square"/>
          <Entry value="7" text="Circle"/>
          <Entry value="8" text="Diamond"/>
          <Entry value="9" text="Arrow"/>
          <Entry value="10" text="ThickArrow"/>
          <Entry value="11" text="HookedArrow"/>
          <Entry value="12" text="EdgeArrow"/>
        </Domain>
      </Property>
    </Proxy>
    <Proxy group="piecewise_functions" type="PiecewiseFunction" id="5498" servers="21">
      <Property name="AllowDuplicateScalars" id="5498.AllowDuplicateScalars" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="5498.AllowDuplicateScalars.bool"/>
      </Property>
      <Property name="Points" id="5498.Points" number_of_elements="8">
        <Element index="0" value="9.78115956672179e-10"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0.5"/>
        <Element index="3" value="0"/>
        <Element index="4" value="1.3364466998078e-05"/>
        <Element index="5" value="1"/>
        <Element index="6" value="0.5"/>
        <Element index="7" value="0"/>
      </Property>
      <Property name="ScalarRangeInitialized" id="5498.ScalarRangeInitialized" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5498.ScalarRangeInitialized.bool"/>
      </Property>
    </Proxy>
    <Proxy group="piecewise_functions" type="PiecewiseFunction" id="5499" servers="21">
      <Property name="AllowDuplicateScalars" id="5499.AllowDuplicateScalars" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="5499.AllowDuplicateScalars.bool"/>
      </Property>
      <Property name="Points" id="5499.Points" number_of_elements="8">
        <Element index="0" value="9.78115956672179e-10"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0.5"/>
        <Element index="3" value="0"/>
        <Element index="4" value="1.3364466998078e-05"/>
        <Element index="5" value="1"/>
        <Element index="6" value="0.5"/>
        <Element index="7" value="0"/>
      </Property>
      <Property name="ScalarRangeInitialized" id="5499.ScalarRangeInitialized" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5499.ScalarRangeInitialized.bool"/>
      </Property>
    </Proxy>
    <Proxy group="representations" type="GeometryRepresentation" id="5007" servers="21">
      <Property name="CubeAxesVisibility" id="5007.CubeAxesVisibility" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5007.CubeAxesVisibility.bool"/>
      </Property>
      <Property name="Input" id="5007.Input" number_of_elements="1">
        <Proxy value="4744" output_port="0"/>
        <Domain name="input_array_cell" id="5007.Input.input_array_cell"/>
        <Domain name="input_array_point" id="5007.Input.input_array_point"/>
        <Domain name="input_type" id="5007.Input.input_type"/>
      </Property>
      <Property name="Representation" id="5007.Representation" number_of_elements="1">
        <Element index="0" value="Surface"/>
        <Domain name="list" id="5007.Representation.list">
          <String text="3D Glyphs"/>
          <String text="Outline"/>
          <String text="Point Gaussian"/>
          <String text="Points"/>
          <String text="Surface"/>
          <String text="Surface With Edges"/>
          <String text="Wireframe"/>
        </Domain>
      </Property>
      <Property name="RepresentationTypesInfo" id="5007.RepresentationTypesInfo" number_of_elements="7">
        <Element index="0" value="3D Glyphs"/>
        <Element index="1" value="Outline"/>
        <Element index="2" value="Point Gaussian"/>
        <Element index="3" value="Points"/>
        <Element index="4" value="Surface"/>
        <Element index="5" value="Surface With Edges"/>
        <Element index="6" value="Wireframe"/>
      </Property>
      <Property name="SelectionCellFieldDataArrayName" id="5007.SelectionCellFieldDataArrayName" number_of_elements="1">
        <Element index="0" value="v"/>
        <Domain name="array_list" id="5007.SelectionCellFieldDataArrayName.array_list">
          <String text="v"/>
        </Domain>
      </Property>
      <Property name="SelectionPointFieldDataArrayName" id="5007.SelectionPointFieldDataArrayName" number_of_elements="1">
        <Element index="0" value="vtkOriginalPointIds"/>
        <Domain name="array_list" id="5007.SelectionPointFieldDataArrayName.array_list"/>
      </Property>
      <Property name="SelectionVisibility" id="5007.SelectionVisibility" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="5007.SelectionVisibility.bool"/>
      </Property>
      <Property name="Visibility" id="5007.Visibility" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5007.Visibility.bool"/>
      </Property>
      <Property name="Ambient" id="5007.Ambient" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="range" id="5007.Ambient.range"/>
      </Property>
      <Property name="AmbientColor" id="5007.AmbientColor" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="1"/>
        <Element index="2" value="1"/>
        <Domain name="range" id="5007.AmbientColor.range"/>
      </Property>
      <Property name="AxesOrigin" id="5007.AxesOrigin" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="5007.AxesOrigin.range"/>
      </Property>
      <Property name="BackfaceAmbientColor" id="5007.BackfaceAmbientColor" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="1"/>
        <Element index="2" value="1"/>
        <Domain name="range" id="5007.BackfaceAmbientColor.range"/>
      </Property>
      <Property name="BackfaceDiffuseColor" id="5007.BackfaceDiffuseColor" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="1"/>
        <Element index="2" value="1"/>
        <Domain name="range" id="5007.BackfaceDiffuseColor.range"/>
      </Property>
      <Property name="BackfaceOpacity" id="5007.BackfaceOpacity" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="5007.BackfaceOpacity.range"/>
      </Property>
      <Property name="BackfaceRepresentation" id="5007.BackfaceRepresentation" number_of_elements="1">
        <Element index="0" value="400"/>
        <Domain name="enum" id="5007.BackfaceRepresentation.enum">
          <Entry value="400" text="Follow Frontface"/>
          <Entry value="401" text="Cull Backface"/>
          <Entry value="402" text="Cull Frontface"/>
          <Entry value="0" text="Points"/>
          <Entry value="1" text="Wireframe"/>
          <Entry value="2" text="Surface"/>
          <Entry value="3" text="Surface With Edges"/>
        </Domain>
      </Property>
      <Property name="BlockColor" id="5007.BlockColor"/>
      <Property name="BlockColorsDistinctValues" id="5007.BlockColorsDistinctValues" number_of_elements="1">
        <Element index="0" value="12"/>
        <Domain name="range" id="5007.BlockColorsDistinctValues.range"/>
      </Property>
      <Property name="BlockOpacity" id="5007.BlockOpacity"/>
      <Property name="BlockVisibility" id="5007.BlockVisibility"/>
      <Property name="CenterStickyAxes" id="5007.CenterStickyAxes" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5007.CenterStickyAxes.bool"/>
      </Property>
      <Property name="Color" id="5007.Color" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="1"/>
        <Element index="2" value="1"/>
        <Domain name="range" id="5007.Color.range"/>
      </Property>
      <Property name="ColorArrayName" id="5007.ColorArrayName" number_of_elements="5">
        <Element index="0" value=""/>
        <Element index="1" value=""/>
        <Element index="2" value=""/>
        <Element index="3" value=""/>
        <Element index="4" value=""/>
        <Domain name="array_list" id="5007.ColorArrayName.array_list">
          <String text="v"/>
        </Domain>
        <Domain name="field_list" id="5007.ColorArrayName.field_list">
          <Entry value="0" text="Point Data"/>
          <Entry value="1" text="Cell Data"/>
          <Entry value="2" text="Field Data"/>
          <Entry value="4" text="Vertex Data"/>
          <Entry value="5" text="Edge Data"/>
          <Entry value="6" text="Row Data"/>
        </Domain>
      </Property>
      <Property name="CubeAxesColor" id="5007.CubeAxesColor" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="1"/>
        <Element index="2" value="1"/>
        <Domain name="range" id="5007.CubeAxesColor.range"/>
      </Property>
      <Property name="CubeAxesCornerOffset" id="5007.CubeAxesCornerOffset" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="range" id="5007.CubeAxesCornerOffset.range"/>
      </Property>
      <Property name="CubeAxesFlyMode" id="5007.CubeAxesFlyMode" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="enum" id="5007.CubeAxesFlyMode.enum">
          <Entry value="0" text="Outer Edges"/>
          <Entry value="1" text="Closest Triad"/>
          <Entry value="2" text="Furthest Triad"/>
          <Entry value="3" text="Static Triad"/>
          <Entry value="4" text="Static Edges"/>
        </Domain>
      </Property>
      <Property name="CubeAxesGridLineLocation" id="5007.CubeAxesGridLineLocation" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="enum" id="5007.CubeAxesGridLineLocation.enum">
          <Entry value="0" text="All Faces"/>
          <Entry value="1" text="Closest Faces"/>
          <Entry value="2" text="Furthest Faces"/>
        </Domain>
      </Property>
      <Property name="CubeAxesInertia" id="5007.CubeAxesInertia" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="5007.CubeAxesInertia.range"/>
      </Property>
      <Property name="CubeAxesTickLocation" id="5007.CubeAxesTickLocation" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="enum" id="5007.CubeAxesTickLocation.enum">
          <Entry value="0" text="Inside"/>
          <Entry value="1" text="Outside"/>
          <Entry value="2" text="Both"/>
        </Domain>
      </Property>
      <Property name="CubeAxesUseDefaultXTitle" id="5007.CubeAxesUseDefaultXTitle" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="5007.CubeAxesUseDefaultXTitle.bool"/>
      </Property>
      <Property name="CubeAxesUseDefaultYTitle" id="5007.CubeAxesUseDefaultYTitle" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="5007.CubeAxesUseDefaultYTitle.bool"/>
      </Property>
      <Property name="CubeAxesUseDefaultZTitle" id="5007.CubeAxesUseDefaultZTitle" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="5007.CubeAxesUseDefaultZTitle.bool"/>
      </Property>
      <Property name="CubeAxesXAxisMinorTickVisibility" id="5007.CubeAxesXAxisMinorTickVisibility" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="5007.CubeAxesXAxisMinorTickVisibility.bool"/>
      </Property>
      <Property name="CubeAxesXAxisTickVisibility" id="5007.CubeAxesXAxisTickVisibility" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="5007.CubeAxesXAxisTickVisibility.bool"/>
      </Property>
      <Property name="CubeAxesXAxisVisibility" id="5007.CubeAxesXAxisVisibility" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="5007.CubeAxesXAxisVisibility.bool"/>
      </Property>
      <Property name="CubeAxesXGridLines" id="5007.CubeAxesXGridLines" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5007.CubeAxesXGridLines.bool"/>
      </Property>
      <Property name="CubeAxesXLabelFormat" id="5007.CubeAxesXLabelFormat" number_of_elements="1">
        <Element index="0" value="%-#6.3g"/>
      </Property>
      <Property name="CubeAxesXTitle" id="5007.CubeAxesXTitle" number_of_elements="1">
        <Element index="0" value="X-Axis"/>
      </Property>
      <Property name="CubeAxesYAxisMinorTickVisibility" id="5007.CubeAxesYAxisMinorTickVisibility" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="5007.CubeAxesYAxisMinorTickVisibility.bool"/>
      </Property>
      <Property name="CubeAxesYAxisTickVisibility" id="5007.CubeAxesYAxisTickVisibility" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="5007.CubeAxesYAxisTickVisibility.bool"/>
      </Property>
      <Property name="CubeAxesYAxisVisibility" id="5007.CubeAxesYAxisVisibility" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="5007.CubeAxesYAxisVisibility.bool"/>
      </Property>
      <Property name="CubeAxesYGridLines" id="5007.CubeAxesYGridLines" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5007.CubeAxesYGridLines.bool"/>
      </Property>
      <Property name="CubeAxesYLabelFormat" id="5007.CubeAxesYLabelFormat" number_of_elements="1">
        <Element index="0" value="%-#6.3g"/>
      </Property>
      <Property name="CubeAxesYTitle" id="5007.CubeAxesYTitle" number_of_elements="1">
        <Element index="0" value="Y-Axis"/>
      </Property>
      <Property name="CubeAxesZAxisMinorTickVisibility" id="5007.CubeAxesZAxisMinorTickVisibility" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="5007.CubeAxesZAxisMinorTickVisibility.bool"/>
      </Property>
      <Property name="CubeAxesZAxisTickVisibility" id="5007.CubeAxesZAxisTickVisibility" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="5007.CubeAxesZAxisTickVisibility.bool"/>
      </Property>
      <Property name="CubeAxesZAxisVisibility" id="5007.CubeAxesZAxisVisibility" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="5007.CubeAxesZAxisVisibility.bool"/>
      </Property>
      <Property name="CubeAxesZGridLines" id="5007.CubeAxesZGridLines" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5007.CubeAxesZGridLines.bool"/>
      </Property>
      <Property name="CubeAxesZLabelFormat" id="5007.CubeAxesZLabelFormat" number_of_elements="1">
        <Element index="0" value="%-#6.3g"/>
      </Property>
      <Property name="CubeAxesZTitle" id="5007.CubeAxesZTitle" number_of_elements="1">
        <Element index="0" value="Z-Axis"/>
      </Property>
      <Property name="CustomBounds" id="5007.CustomBounds" number_of_elements="6">
        <Element index="0" value="0"/>
        <Element index="1" value="1"/>
        <Element index="2" value="0"/>
        <Element index="3" value="1"/>
        <Element index="4" value="0"/>
        <Element index="5" value="1"/>
      </Property>
      <Property name="CustomBoundsActive" id="5007.CustomBoundsActive" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
      </Property>
      <Property name="CustomRange" id="5007.CustomRange" number_of_elements="6">
        <Element index="0" value="0"/>
        <Element index="1" value="1"/>
        <Element index="2" value="0"/>
        <Element index="3" value="1"/>
        <Element index="4" value="0"/>
        <Element index="5" value="1"/>
      </Property>
      <Property name="CustomRangeActive" id="5007.CustomRangeActive" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
      </Property>
      <Property name="CustomShader" id="5007.CustomShader" number_of_elements="1">
        <Element index="0" value=""/>
      </Property>
      <Property name="DataBounds" id="5007.DataBounds" number_of_elements="6">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Element index="3" value="0"/>
        <Element index="4" value="0"/>
        <Element index="5" value="0"/>
      </Property>
      <Property name="Diffuse" id="5007.Diffuse" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="5007.Diffuse.range"/>
      </Property>
      <Property name="DiffuseColor" id="5007.DiffuseColor" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="1"/>
        <Element index="2" value="1"/>
        <Domain name="range" id="5007.DiffuseColor.range"/>
      </Property>
      <Property name="EdgeColor" id="5007.EdgeColor" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0.5"/>
        <Domain name="range" id="5007.EdgeColor.range"/>
      </Property>
      <Property name="Emissive" id="5007.Emissive" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5007.Emissive.bool"/>
      </Property>
      <Property name="GaussianRadius" id="5007.GaussianRadius" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="range" id="5007.GaussianRadius.range"/>
      </Property>
      <Property name="GlyphType" id="5007.GlyphType" number_of_elements="1">
        <Proxy value="4862" output_port="0"/>
        <Domain name="input_type" id="5007.GlyphType.input_type"/>
        <Domain name="proxy_list" id="5007.GlyphType.proxy_list">
          <Proxy value="4862"/>
          <Proxy value="4873"/>
          <Proxy value="4884"/>
          <Proxy value="4895"/>
          <Proxy value="4906"/>
          <Proxy value="4917"/>
          <Proxy value="4928"/>
        </Domain>
      </Property>
      <Property name="InterpolateScalarsBeforeMapping" id="5007.InterpolateScalarsBeforeMapping" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="5007.InterpolateScalarsBeforeMapping.bool"/>
      </Property>
      <Property name="Interpolation" id="5007.Interpolation" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="enum" id="5007.Interpolation.enum">
          <Entry value="0" text="Flat"/>
          <Entry value="1" text="Gouraud"/>
        </Domain>
      </Property>
      <Property name="LineWidth" id="5007.LineWidth" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="5007.LineWidth.range"/>
      </Property>
      <Property name="LookupTable" id="5007.LookupTable">
        <Domain name="groups" id="5007.LookupTable.groups"/>
      </Property>
      <Property name="MapScalars" id="5007.MapScalars" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="5007.MapScalars.bool"/>
      </Property>
      <Property name="Masking" id="5007.Masking" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5007.Masking.bool"/>
      </Property>
      <Property name="MeshVisibility" id="5007.MeshVisibility" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5007.MeshVisibility.bool"/>
      </Property>
      <Property name="NonlinearSubdivisionLevel" id="5007.NonlinearSubdivisionLevel" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="5007.NonlinearSubdivisionLevel.range"/>
      </Property>
      <Property name="Opacity" id="5007.Opacity" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="5007.Opacity.range"/>
      </Property>
      <Property name="OpacityArray" id="5007.OpacityArray" number_of_elements="5">
        <Element index="0" value=""/>
        <Element index="1" value=""/>
        <Element index="2" value=""/>
        <Element index="3" value=""/>
        <Element index="4" value=""/>
        <Domain name="array_list" id="5007.OpacityArray.array_list"/>
      </Property>
      <Property name="OpacityByArray" id="5007.OpacityByArray" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5007.OpacityByArray.bool"/>
      </Property>
      <Property name="OpacityTransferFunction" id="5007.OpacityTransferFunction" number_of_elements="1">
        <Proxy value="4961"/>
        <Domain name="groups" id="5007.OpacityTransferFunction.groups"/>
        <Domain name="proxy_list" id="5007.OpacityTransferFunction.proxy_list">
          <Proxy value="4961"/>
        </Domain>
      </Property>
      <Property name="Orient" id="5007.Orient" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5007.Orient.bool"/>
      </Property>
      <Property name="Orientation" id="5007.Orientation" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="5007.Orientation.range"/>
      </Property>
      <Property name="OrientationMode" id="5007.OrientationMode" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="enum" id="5007.OrientationMode.enum">
          <Entry value="0" text="Direction"/>
          <Entry value="1" text="Rotation"/>
        </Domain>
      </Property>
      <Property name="Origin" id="5007.Origin" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="5007.Origin.range"/>
      </Property>
      <Property name="OriginalBoundsRangeActive" id="5007.OriginalBoundsRangeActive" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
      </Property>
      <Property name="Pickable" id="5007.Pickable" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="5007.Pickable.bool"/>
      </Property>
      <Property name="PointSize" id="5007.PointSize" number_of_elements="1">
        <Element index="0" value="2"/>
        <Domain name="range" id="5007.PointSize.range"/>
      </Property>
      <Property name="Position" id="5007.Position" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="5007.Position.range"/>
      </Property>
      <Property name="Scale" id="5007.Scale" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="1"/>
        <Element index="2" value="1"/>
        <Domain name="range" id="5007.Scale.range"/>
      </Property>
      <Property name="ScaleByArray" id="5007.ScaleByArray" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5007.ScaleByArray.bool"/>
      </Property>
      <Property name="ScaleFactor" id="5007.ScaleFactor" number_of_elements="1">
        <Element index="0" value="0.00500000007450581"/>
        <Domain name="bounds" id="5007.ScaleFactor.bounds"/>
        <Domain name="scalar_range" id="5007.ScaleFactor.scalar_range"/>
        <Domain name="vector_range" id="5007.ScaleFactor.vector_range"/>
      </Property>
      <Property name="ScaleMode" id="5007.ScaleMode" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="enum" id="5007.ScaleMode.enum">
          <Entry value="0" text="No Data Scaling Off"/>
          <Entry value="1" text="Magnitude"/>
          <Entry value="2" text="Vector Components"/>
        </Domain>
      </Property>
      <Property name="ScaleTransferFunction" id="5007.ScaleTransferFunction" number_of_elements="1">
        <Proxy value="4962"/>
        <Domain name="groups" id="5007.ScaleTransferFunction.groups"/>
        <Domain name="proxy_list" id="5007.ScaleTransferFunction.proxy_list">
          <Proxy value="4962"/>
        </Domain>
      </Property>
      <Property name="Scaling" id="5007.Scaling" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5007.Scaling.bool"/>
      </Property>
      <Property name="SelectMaskArray" id="5007.SelectMaskArray" number_of_elements="1">
        <Element index="0" value=""/>
      </Property>
      <Property name="SelectOrientationVectors" id="5007.SelectOrientationVectors" number_of_elements="1">
        <Element index="0" value=""/>
      </Property>
      <Property name="SelectScaleArray" id="5007.SelectScaleArray" number_of_elements="1">
        <Element index="0" value=""/>
      </Property>
      <Property name="SelectionCellLabelBold" id="5007.SelectionCellLabelBold" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5007.SelectionCellLabelBold.bool"/>
      </Property>
      <Property name="SelectionCellLabelColor" id="5007.SelectionCellLabelColor" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="1"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="5007.SelectionCellLabelColor.range"/>
      </Property>
      <Property name="SelectionCellLabelFontFamily" id="5007.SelectionCellLabelFontFamily" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="enum" id="5007.SelectionCellLabelFontFamily.enum">
          <Entry value="0" text="Arial"/>
          <Entry value="1" text="Courier"/>
          <Entry value="2" text="Times"/>
        </Domain>
      </Property>
      <Property name="SelectionCellLabelFontSize" id="5007.SelectionCellLabelFontSize" number_of_elements="1">
        <Element index="0" value="18"/>
        <Domain name="range" id="5007.SelectionCellLabelFontSize.range"/>
      </Property>
      <Property name="SelectionCellLabelFormat" id="5007.SelectionCellLabelFormat" number_of_elements="1">
        <Element index="0" value=""/>
      </Property>
      <Property name="SelectionCellLabelItalic" id="5007.SelectionCellLabelItalic" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5007.SelectionCellLabelItalic.bool"/>
      </Property>
      <Property name="SelectionCellLabelJustification" id="5007.SelectionCellLabelJustification" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="enum" id="5007.SelectionCellLabelJustification.enum">
          <Entry value="0" text="Left"/>
          <Entry value="1" text="Center"/>
          <Entry value="2" text="Right"/>
        </Domain>
      </Property>
      <Property name="SelectionCellLabelOpacity" id="5007.SelectionCellLabelOpacity" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="5007.SelectionCellLabelOpacity.range"/>
      </Property>
      <Property name="SelectionCellLabelShadow" id="5007.SelectionCellLabelShadow" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5007.SelectionCellLabelShadow.bool"/>
      </Property>
      <Property name="SelectionCellLabelVisibility" id="5007.SelectionCellLabelVisibility" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5007.SelectionCellLabelVisibility.bool"/>
      </Property>
      <Property name="SelectionColor" id="5007.SelectionColor" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="0"/>
        <Element index="2" value="1"/>
        <Domain name="range" id="5007.SelectionColor.range"/>
      </Property>
      <Property name="SelectionLineWidth" id="5007.SelectionLineWidth" number_of_elements="1">
        <Element index="0" value="2"/>
        <Domain name="range" id="5007.SelectionLineWidth.range"/>
      </Property>
      <Property name="SelectionOpacity" id="5007.SelectionOpacity" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="5007.SelectionOpacity.range"/>
      </Property>
      <Property name="SelectionPointLabelBold" id="5007.SelectionPointLabelBold" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5007.SelectionPointLabelBold.bool"/>
      </Property>
      <Property name="SelectionPointLabelColor" id="5007.SelectionPointLabelColor" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="1"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="5007.SelectionPointLabelColor.range"/>
      </Property>
      <Property name="SelectionPointLabelFontFamily" id="5007.SelectionPointLabelFontFamily" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="enum" id="5007.SelectionPointLabelFontFamily.enum">
          <Entry value="0" text="Arial"/>
          <Entry value="1" text="Courier"/>
          <Entry value="2" text="Times"/>
        </Domain>
      </Property>
      <Property name="SelectionPointLabelFontSize" id="5007.SelectionPointLabelFontSize" number_of_elements="1">
        <Element index="0" value="18"/>
        <Domain name="range" id="5007.SelectionPointLabelFontSize.range"/>
      </Property>
      <Property name="SelectionPointLabelFormat" id="5007.SelectionPointLabelFormat" number_of_elements="1">
        <Element index="0" value=""/>
      </Property>
      <Property name="SelectionPointLabelItalic" id="5007.SelectionPointLabelItalic" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5007.SelectionPointLabelItalic.bool"/>
      </Property>
      <Property name="SelectionPointLabelJustification" id="5007.SelectionPointLabelJustification" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="enum" id="5007.SelectionPointLabelJustification.enum">
          <Entry value="0" text="Left"/>
          <Entry value="1" text="Center"/>
          <Entry value="2" text="Right"/>
        </Domain>
      </Property>
      <Property name="SelectionPointLabelOpacity" id="5007.SelectionPointLabelOpacity" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="5007.SelectionPointLabelOpacity.range"/>
      </Property>
      <Property name="SelectionPointLabelShadow" id="5007.SelectionPointLabelShadow" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5007.SelectionPointLabelShadow.bool"/>
      </Property>
      <Property name="SelectionPointLabelVisibility" id="5007.SelectionPointLabelVisibility" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5007.SelectionPointLabelVisibility.bool"/>
      </Property>
      <Property name="SelectionPointSize" id="5007.SelectionPointSize" number_of_elements="1">
        <Element index="0" value="5"/>
        <Domain name="range" id="5007.SelectionPointSize.range"/>
      </Property>
      <Property name="SelectionRepresentation" id="5007.SelectionRepresentation" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="enum" id="5007.SelectionRepresentation.enum">
          <Entry value="0" text="Points"/>
          <Entry value="1" text="Wireframe"/>
          <Entry value="2" text="Surface"/>
        </Domain>
      </Property>
      <Property name="SelectionUseOutline" id="5007.SelectionUseOutline" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5007.SelectionUseOutline.bool"/>
      </Property>
      <Property name="SetScaleArray" id="5007.SetScaleArray" number_of_elements="5">
        <Element index="0" value=""/>
        <Element index="1" value=""/>
        <Element index="2" value=""/>
        <Element index="3" value=""/>
        <Element index="4" value=""/>
        <Domain name="array_list" id="5007.SetScaleArray.array_list"/>
      </Property>
      <Property name="ShaderPreset" id="5007.ShaderPreset" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="enum" id="5007.ShaderPreset.enum">
          <Entry value="0" text="Gaussian Blur (Default)"/>
          <Entry value="1" text="Sphere"/>
          <Entry value="2" text="Black-edged circle"/>
          <Entry value="3" text="Plain circle"/>
          <Entry value="4" text="Triangle"/>
          <Entry value="5" text="Square Outline"/>
        </Domain>
      </Property>
      <Property name="Specular" id="5007.Specular" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="range" id="5007.Specular.range"/>
      </Property>
      <Property name="SpecularColor" id="5007.SpecularColor" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="1"/>
        <Element index="2" value="1"/>
        <Domain name="range" id="5007.SpecularColor.range"/>
      </Property>
      <Property name="SpecularPower" id="5007.SpecularPower" number_of_elements="1">
        <Element index="0" value="100"/>
        <Domain name="range" id="5007.SpecularPower.range"/>
      </Property>
      <Property name="StaticMode" id="5007.StaticMode" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5007.StaticMode.bool"/>
      </Property>
      <Property name="StickyAxes" id="5007.StickyAxes" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5007.StickyAxes.bool"/>
      </Property>
      <Property name="SuppressLOD" id="5007.SuppressLOD" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5007.SuppressLOD.bool"/>
      </Property>
      <Property name="Texture" id="5007.Texture">
        <Domain name="groups" id="5007.Texture.groups"/>
      </Property>
      <Property name="Triangulate" id="5007.Triangulate" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5007.Triangulate.bool"/>
      </Property>
      <Property name="UseAxesOrigin" id="5007.UseAxesOrigin" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5007.UseAxesOrigin.bool"/>
      </Property>
      <Property name="UserTransform" id="5007.UserTransform" number_of_elements="16">
        <Element index="0" value="1"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Element index="3" value="0"/>
        <Element index="4" value="0"/>
        <Element index="5" value="1"/>
        <Element index="6" value="0"/>
        <Element index="7" value="0"/>
        <Element index="8" value="0"/>
        <Element index="9" value="0"/>
        <Element index="10" value="1"/>
        <Element index="11" value="0"/>
        <Element index="12" value="0"/>
        <Element index="13" value="0"/>
        <Element index="14" value="0"/>
        <Element index="15" value="1"/>
      </Property>
    </Proxy>
    <Proxy group="representations" type="GeometryRepresentation" id="5186" servers="21">
      <Property name="CubeAxesVisibility" id="5186.CubeAxesVisibility" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5186.CubeAxesVisibility.bool"/>
      </Property>
      <Property name="Input" id="5186.Input" number_of_elements="1">
        <Proxy value="5018" output_port="0"/>
        <Domain name="input_array_cell" id="5186.Input.input_array_cell"/>
        <Domain name="input_array_point" id="5186.Input.input_array_point"/>
        <Domain name="input_type" id="5186.Input.input_type"/>
      </Property>
      <Property name="Representation" id="5186.Representation" number_of_elements="1">
        <Element index="0" value="Surface"/>
        <Domain name="list" id="5186.Representation.list">
          <String text="3D Glyphs"/>
          <String text="Outline"/>
          <String text="Point Gaussian"/>
          <String text="Points"/>
          <String text="Surface"/>
          <String text="Surface With Edges"/>
          <String text="Wireframe"/>
        </Domain>
      </Property>
      <Property name="RepresentationTypesInfo" id="5186.RepresentationTypesInfo" number_of_elements="7">
        <Element index="0" value="3D Glyphs"/>
        <Element index="1" value="Outline"/>
        <Element index="2" value="Point Gaussian"/>
        <Element index="3" value="Points"/>
        <Element index="4" value="Surface"/>
        <Element index="5" value="Surface With Edges"/>
        <Element index="6" value="Wireframe"/>
      </Property>
      <Property name="SelectionCellFieldDataArrayName" id="5186.SelectionCellFieldDataArrayName" number_of_elements="1">
        <Element index="0" value="v"/>
        <Domain name="array_list" id="5186.SelectionCellFieldDataArrayName.array_list">
          <String text="v"/>
        </Domain>
      </Property>
      <Property name="SelectionPointFieldDataArrayName" id="5186.SelectionPointFieldDataArrayName" number_of_elements="1">
        <Element index="0" value="vtkOriginalPointIds"/>
        <Domain name="array_list" id="5186.SelectionPointFieldDataArrayName.array_list"/>
      </Property>
      <Property name="SelectionVisibility" id="5186.SelectionVisibility" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="5186.SelectionVisibility.bool"/>
      </Property>
      <Property name="Visibility" id="5186.Visibility" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5186.Visibility.bool"/>
      </Property>
      <Property name="Ambient" id="5186.Ambient" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="range" id="5186.Ambient.range"/>
      </Property>
      <Property name="AmbientColor" id="5186.AmbientColor" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="1"/>
        <Element index="2" value="1"/>
        <Domain name="range" id="5186.AmbientColor.range"/>
      </Property>
      <Property name="AxesOrigin" id="5186.AxesOrigin" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="5186.AxesOrigin.range"/>
      </Property>
      <Property name="BackfaceAmbientColor" id="5186.BackfaceAmbientColor" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="1"/>
        <Element index="2" value="1"/>
        <Domain name="range" id="5186.BackfaceAmbientColor.range"/>
      </Property>
      <Property name="BackfaceDiffuseColor" id="5186.BackfaceDiffuseColor" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="1"/>
        <Element index="2" value="1"/>
        <Domain name="range" id="5186.BackfaceDiffuseColor.range"/>
      </Property>
      <Property name="BackfaceOpacity" id="5186.BackfaceOpacity" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="5186.BackfaceOpacity.range"/>
      </Property>
      <Property name="BackfaceRepresentation" id="5186.BackfaceRepresentation" number_of_elements="1">
        <Element index="0" value="400"/>
        <Domain name="enum" id="5186.BackfaceRepresentation.enum">
          <Entry value="400" text="Follow Frontface"/>
          <Entry value="401" text="Cull Backface"/>
          <Entry value="402" text="Cull Frontface"/>
          <Entry value="0" text="Points"/>
          <Entry value="1" text="Wireframe"/>
          <Entry value="2" text="Surface"/>
          <Entry value="3" text="Surface With Edges"/>
        </Domain>
      </Property>
      <Property name="BlockColor" id="5186.BlockColor"/>
      <Property name="BlockColorsDistinctValues" id="5186.BlockColorsDistinctValues" number_of_elements="1">
        <Element index="0" value="12"/>
        <Domain name="range" id="5186.BlockColorsDistinctValues.range"/>
      </Property>
      <Property name="BlockOpacity" id="5186.BlockOpacity"/>
      <Property name="BlockVisibility" id="5186.BlockVisibility"/>
      <Property name="CenterStickyAxes" id="5186.CenterStickyAxes" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5186.CenterStickyAxes.bool"/>
      </Property>
      <Property name="Color" id="5186.Color" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="1"/>
        <Element index="2" value="1"/>
        <Domain name="range" id="5186.Color.range"/>
      </Property>
      <Property name="ColorArrayName" id="5186.ColorArrayName" number_of_elements="5">
        <Element index="0" value=""/>
        <Element index="1" value=""/>
        <Element index="2" value=""/>
        <Element index="3" value=""/>
        <Element index="4" value=""/>
        <Domain name="array_list" id="5186.ColorArrayName.array_list">
          <String text="v"/>
          <String text="vtkCompositeIndex"/>
        </Domain>
        <Domain name="field_list" id="5186.ColorArrayName.field_list">
          <Entry value="0" text="Point Data"/>
          <Entry value="1" text="Cell Data"/>
          <Entry value="2" text="Field Data"/>
          <Entry value="4" text="Vertex Data"/>
          <Entry value="5" text="Edge Data"/>
          <Entry value="6" text="Row Data"/>
        </Domain>
      </Property>
      <Property name="CubeAxesColor" id="5186.CubeAxesColor" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="1"/>
        <Element index="2" value="1"/>
        <Domain name="range" id="5186.CubeAxesColor.range"/>
      </Property>
      <Property name="CubeAxesCornerOffset" id="5186.CubeAxesCornerOffset" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="range" id="5186.CubeAxesCornerOffset.range"/>
      </Property>
      <Property name="CubeAxesFlyMode" id="5186.CubeAxesFlyMode" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="enum" id="5186.CubeAxesFlyMode.enum">
          <Entry value="0" text="Outer Edges"/>
          <Entry value="1" text="Closest Triad"/>
          <Entry value="2" text="Furthest Triad"/>
          <Entry value="3" text="Static Triad"/>
          <Entry value="4" text="Static Edges"/>
        </Domain>
      </Property>
      <Property name="CubeAxesGridLineLocation" id="5186.CubeAxesGridLineLocation" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="enum" id="5186.CubeAxesGridLineLocation.enum">
          <Entry value="0" text="All Faces"/>
          <Entry value="1" text="Closest Faces"/>
          <Entry value="2" text="Furthest Faces"/>
        </Domain>
      </Property>
      <Property name="CubeAxesInertia" id="5186.CubeAxesInertia" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="5186.CubeAxesInertia.range"/>
      </Property>
      <Property name="CubeAxesTickLocation" id="5186.CubeAxesTickLocation" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="enum" id="5186.CubeAxesTickLocation.enum">
          <Entry value="0" text="Inside"/>
          <Entry value="1" text="Outside"/>
          <Entry value="2" text="Both"/>
        </Domain>
      </Property>
      <Property name="CubeAxesUseDefaultXTitle" id="5186.CubeAxesUseDefaultXTitle" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="5186.CubeAxesUseDefaultXTitle.bool"/>
      </Property>
      <Property name="CubeAxesUseDefaultYTitle" id="5186.CubeAxesUseDefaultYTitle" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="5186.CubeAxesUseDefaultYTitle.bool"/>
      </Property>
      <Property name="CubeAxesUseDefaultZTitle" id="5186.CubeAxesUseDefaultZTitle" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="5186.CubeAxesUseDefaultZTitle.bool"/>
      </Property>
      <Property name="CubeAxesXAxisMinorTickVisibility" id="5186.CubeAxesXAxisMinorTickVisibility" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="5186.CubeAxesXAxisMinorTickVisibility.bool"/>
      </Property>
      <Property name="CubeAxesXAxisTickVisibility" id="5186.CubeAxesXAxisTickVisibility" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="5186.CubeAxesXAxisTickVisibility.bool"/>
      </Property>
      <Property name="CubeAxesXAxisVisibility" id="5186.CubeAxesXAxisVisibility" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="5186.CubeAxesXAxisVisibility.bool"/>
      </Property>
      <Property name="CubeAxesXGridLines" id="5186.CubeAxesXGridLines" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5186.CubeAxesXGridLines.bool"/>
      </Property>
      <Property name="CubeAxesXLabelFormat" id="5186.CubeAxesXLabelFormat" number_of_elements="1">
        <Element index="0" value="%-#6.3g"/>
      </Property>
      <Property name="CubeAxesXTitle" id="5186.CubeAxesXTitle" number_of_elements="1">
        <Element index="0" value="X-Axis"/>
      </Property>
      <Property name="CubeAxesYAxisMinorTickVisibility" id="5186.CubeAxesYAxisMinorTickVisibility" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="5186.CubeAxesYAxisMinorTickVisibility.bool"/>
      </Property>
      <Property name="CubeAxesYAxisTickVisibility" id="5186.CubeAxesYAxisTickVisibility" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="5186.CubeAxesYAxisTickVisibility.bool"/>
      </Property>
      <Property name="CubeAxesYAxisVisibility" id="5186.CubeAxesYAxisVisibility" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="5186.CubeAxesYAxisVisibility.bool"/>
      </Property>
      <Property name="CubeAxesYGridLines" id="5186.CubeAxesYGridLines" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5186.CubeAxesYGridLines.bool"/>
      </Property>
      <Property name="CubeAxesYLabelFormat" id="5186.CubeAxesYLabelFormat" number_of_elements="1">
        <Element index="0" value="%-#6.3g"/>
      </Property>
      <Property name="CubeAxesYTitle" id="5186.CubeAxesYTitle" number_of_elements="1">
        <Element index="0" value="Y-Axis"/>
      </Property>
      <Property name="CubeAxesZAxisMinorTickVisibility" id="5186.CubeAxesZAxisMinorTickVisibility" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="5186.CubeAxesZAxisMinorTickVisibility.bool"/>
      </Property>
      <Property name="CubeAxesZAxisTickVisibility" id="5186.CubeAxesZAxisTickVisibility" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="5186.CubeAxesZAxisTickVisibility.bool"/>
      </Property>
      <Property name="CubeAxesZAxisVisibility" id="5186.CubeAxesZAxisVisibility" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="5186.CubeAxesZAxisVisibility.bool"/>
      </Property>
      <Property name="CubeAxesZGridLines" id="5186.CubeAxesZGridLines" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5186.CubeAxesZGridLines.bool"/>
      </Property>
      <Property name="CubeAxesZLabelFormat" id="5186.CubeAxesZLabelFormat" number_of_elements="1">
        <Element index="0" value="%-#6.3g"/>
      </Property>
      <Property name="CubeAxesZTitle" id="5186.CubeAxesZTitle" number_of_elements="1">
        <Element index="0" value="Z-Axis"/>
      </Property>
      <Property name="CustomBounds" id="5186.CustomBounds" number_of_elements="6">
        <Element index="0" value="0"/>
        <Element index="1" value="1"/>
        <Element index="2" value="0"/>
        <Element index="3" value="1"/>
        <Element index="4" value="0"/>
        <Element index="5" value="1"/>
      </Property>
      <Property name="CustomBoundsActive" id="5186.CustomBoundsActive" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
      </Property>
      <Property name="CustomRange" id="5186.CustomRange" number_of_elements="6">
        <Element index="0" value="0"/>
        <Element index="1" value="1"/>
        <Element index="2" value="0"/>
        <Element index="3" value="1"/>
        <Element index="4" value="0"/>
        <Element index="5" value="1"/>
      </Property>
      <Property name="CustomRangeActive" id="5186.CustomRangeActive" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
      </Property>
      <Property name="CustomShader" id="5186.CustomShader" number_of_elements="1">
        <Element index="0" value=""/>
      </Property>
      <Property name="DataBounds" id="5186.DataBounds" number_of_elements="6">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="4.41885396721369e-316"/>
        <Element index="3" value="8.48798316386109e-314"/>
        <Element index="4" value="0"/>
        <Element index="5" value="0"/>
      </Property>
      <Property name="Diffuse" id="5186.Diffuse" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="5186.Diffuse.range"/>
      </Property>
      <Property name="DiffuseColor" id="5186.DiffuseColor" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="1"/>
        <Element index="2" value="1"/>
        <Domain name="range" id="5186.DiffuseColor.range"/>
      </Property>
      <Property name="EdgeColor" id="5186.EdgeColor" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0.5"/>
        <Domain name="range" id="5186.EdgeColor.range"/>
      </Property>
      <Property name="Emissive" id="5186.Emissive" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5186.Emissive.bool"/>
      </Property>
      <Property name="GaussianRadius" id="5186.GaussianRadius" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="range" id="5186.GaussianRadius.range"/>
      </Property>
      <Property name="GlyphType" id="5186.GlyphType" number_of_elements="1">
        <Proxy value="5041" output_port="0"/>
        <Domain name="input_type" id="5186.GlyphType.input_type"/>
        <Domain name="proxy_list" id="5186.GlyphType.proxy_list">
          <Proxy value="5041"/>
          <Proxy value="5052"/>
          <Proxy value="5063"/>
          <Proxy value="5074"/>
          <Proxy value="5085"/>
          <Proxy value="5096"/>
          <Proxy value="5107"/>
        </Domain>
      </Property>
      <Property name="InterpolateScalarsBeforeMapping" id="5186.InterpolateScalarsBeforeMapping" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="5186.InterpolateScalarsBeforeMapping.bool"/>
      </Property>
      <Property name="Interpolation" id="5186.Interpolation" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="enum" id="5186.Interpolation.enum">
          <Entry value="0" text="Flat"/>
          <Entry value="1" text="Gouraud"/>
        </Domain>
      </Property>
      <Property name="LineWidth" id="5186.LineWidth" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="5186.LineWidth.range"/>
      </Property>
      <Property name="LookupTable" id="5186.LookupTable">
        <Domain name="groups" id="5186.LookupTable.groups"/>
      </Property>
      <Property name="MapScalars" id="5186.MapScalars" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="5186.MapScalars.bool"/>
      </Property>
      <Property name="Masking" id="5186.Masking" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5186.Masking.bool"/>
      </Property>
      <Property name="MeshVisibility" id="5186.MeshVisibility" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5186.MeshVisibility.bool"/>
      </Property>
      <Property name="NonlinearSubdivisionLevel" id="5186.NonlinearSubdivisionLevel" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="5186.NonlinearSubdivisionLevel.range"/>
      </Property>
      <Property name="Opacity" id="5186.Opacity" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="5186.Opacity.range"/>
      </Property>
      <Property name="OpacityArray" id="5186.OpacityArray" number_of_elements="5">
        <Element index="0" value=""/>
        <Element index="1" value=""/>
        <Element index="2" value=""/>
        <Element index="3" value=""/>
        <Element index="4" value=""/>
        <Domain name="array_list" id="5186.OpacityArray.array_list"/>
      </Property>
      <Property name="OpacityByArray" id="5186.OpacityByArray" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5186.OpacityByArray.bool"/>
      </Property>
      <Property name="OpacityTransferFunction" id="5186.OpacityTransferFunction" number_of_elements="1">
        <Proxy value="5140"/>
        <Domain name="groups" id="5186.OpacityTransferFunction.groups"/>
        <Domain name="proxy_list" id="5186.OpacityTransferFunction.proxy_list">
          <Proxy value="5140"/>
        </Domain>
      </Property>
      <Property name="Orient" id="5186.Orient" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5186.Orient.bool"/>
      </Property>
      <Property name="Orientation" id="5186.Orientation" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="5186.Orientation.range"/>
      </Property>
      <Property name="OrientationMode" id="5186.OrientationMode" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="enum" id="5186.OrientationMode.enum">
          <Entry value="0" text="Direction"/>
          <Entry value="1" text="Rotation"/>
        </Domain>
      </Property>
      <Property name="Origin" id="5186.Origin" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="5186.Origin.range"/>
      </Property>
      <Property name="OriginalBoundsRangeActive" id="5186.OriginalBoundsRangeActive" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
      </Property>
      <Property name="Pickable" id="5186.Pickable" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="5186.Pickable.bool"/>
      </Property>
      <Property name="PointSize" id="5186.PointSize" number_of_elements="1">
        <Element index="0" value="2"/>
        <Domain name="range" id="5186.PointSize.range"/>
      </Property>
      <Property name="Position" id="5186.Position" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="5186.Position.range"/>
      </Property>
      <Property name="Scale" id="5186.Scale" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="1"/>
        <Element index="2" value="1"/>
        <Domain name="range" id="5186.Scale.range"/>
      </Property>
      <Property name="ScaleByArray" id="5186.ScaleByArray" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5186.ScaleByArray.bool"/>
      </Property>
      <Property name="ScaleFactor" id="5186.ScaleFactor" number_of_elements="1">
        <Element index="0" value="0.0100000001490116"/>
        <Domain name="bounds" id="5186.ScaleFactor.bounds"/>
        <Domain name="scalar_range" id="5186.ScaleFactor.scalar_range"/>
        <Domain name="vector_range" id="5186.ScaleFactor.vector_range"/>
      </Property>
      <Property name="ScaleMode" id="5186.ScaleMode" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="enum" id="5186.ScaleMode.enum">
          <Entry value="0" text="No Data Scaling Off"/>
          <Entry value="1" text="Magnitude"/>
          <Entry value="2" text="Vector Components"/>
        </Domain>
      </Property>
      <Property name="ScaleTransferFunction" id="5186.ScaleTransferFunction" number_of_elements="1">
        <Proxy value="5141"/>
        <Domain name="groups" id="5186.ScaleTransferFunction.groups"/>
        <Domain name="proxy_list" id="5186.ScaleTransferFunction.proxy_list">
          <Proxy value="5141"/>
        </Domain>
      </Property>
      <Property name="Scaling" id="5186.Scaling" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5186.Scaling.bool"/>
      </Property>
      <Property name="SelectMaskArray" id="5186.SelectMaskArray" number_of_elements="1">
        <Element index="0" value=""/>
      </Property>
      <Property name="SelectOrientationVectors" id="5186.SelectOrientationVectors" number_of_elements="1">
        <Element index="0" value=""/>
      </Property>
      <Property name="SelectScaleArray" id="5186.SelectScaleArray" number_of_elements="1">
        <Element index="0" value=""/>
      </Property>
      <Property name="SelectionCellLabelBold" id="5186.SelectionCellLabelBold" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5186.SelectionCellLabelBold.bool"/>
      </Property>
      <Property name="SelectionCellLabelColor" id="5186.SelectionCellLabelColor" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="1"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="5186.SelectionCellLabelColor.range"/>
      </Property>
      <Property name="SelectionCellLabelFontFamily" id="5186.SelectionCellLabelFontFamily" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="enum" id="5186.SelectionCellLabelFontFamily.enum">
          <Entry value="0" text="Arial"/>
          <Entry value="1" text="Courier"/>
          <Entry value="2" text="Times"/>
        </Domain>
      </Property>
      <Property name="SelectionCellLabelFontSize" id="5186.SelectionCellLabelFontSize" number_of_elements="1">
        <Element index="0" value="18"/>
        <Domain name="range" id="5186.SelectionCellLabelFontSize.range"/>
      </Property>
      <Property name="SelectionCellLabelFormat" id="5186.SelectionCellLabelFormat" number_of_elements="1">
        <Element index="0" value=""/>
      </Property>
      <Property name="SelectionCellLabelItalic" id="5186.SelectionCellLabelItalic" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5186.SelectionCellLabelItalic.bool"/>
      </Property>
      <Property name="SelectionCellLabelJustification" id="5186.SelectionCellLabelJustification" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="enum" id="5186.SelectionCellLabelJustification.enum">
          <Entry value="0" text="Left"/>
          <Entry value="1" text="Center"/>
          <Entry value="2" text="Right"/>
        </Domain>
      </Property>
      <Property name="SelectionCellLabelOpacity" id="5186.SelectionCellLabelOpacity" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="5186.SelectionCellLabelOpacity.range"/>
      </Property>
      <Property name="SelectionCellLabelShadow" id="5186.SelectionCellLabelShadow" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5186.SelectionCellLabelShadow.bool"/>
      </Property>
      <Property name="SelectionCellLabelVisibility" id="5186.SelectionCellLabelVisibility" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5186.SelectionCellLabelVisibility.bool"/>
      </Property>
      <Property name="SelectionColor" id="5186.SelectionColor" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="0"/>
        <Element index="2" value="1"/>
        <Domain name="range" id="5186.SelectionColor.range"/>
      </Property>
      <Property name="SelectionLineWidth" id="5186.SelectionLineWidth" number_of_elements="1">
        <Element index="0" value="2"/>
        <Domain name="range" id="5186.SelectionLineWidth.range"/>
      </Property>
      <Property name="SelectionOpacity" id="5186.SelectionOpacity" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="5186.SelectionOpacity.range"/>
      </Property>
      <Property name="SelectionPointLabelBold" id="5186.SelectionPointLabelBold" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5186.SelectionPointLabelBold.bool"/>
      </Property>
      <Property name="SelectionPointLabelColor" id="5186.SelectionPointLabelColor" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="1"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="5186.SelectionPointLabelColor.range"/>
      </Property>
      <Property name="SelectionPointLabelFontFamily" id="5186.SelectionPointLabelFontFamily" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="enum" id="5186.SelectionPointLabelFontFamily.enum">
          <Entry value="0" text="Arial"/>
          <Entry value="1" text="Courier"/>
          <Entry value="2" text="Times"/>
        </Domain>
      </Property>
      <Property name="SelectionPointLabelFontSize" id="5186.SelectionPointLabelFontSize" number_of_elements="1">
        <Element index="0" value="18"/>
        <Domain name="range" id="5186.SelectionPointLabelFontSize.range"/>
      </Property>
      <Property name="SelectionPointLabelFormat" id="5186.SelectionPointLabelFormat" number_of_elements="1">
        <Element index="0" value=""/>
      </Property>
      <Property name="SelectionPointLabelItalic" id="5186.SelectionPointLabelItalic" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5186.SelectionPointLabelItalic.bool"/>
      </Property>
      <Property name="SelectionPointLabelJustification" id="5186.SelectionPointLabelJustification" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="enum" id="5186.SelectionPointLabelJustification.enum">
          <Entry value="0" text="Left"/>
          <Entry value="1" text="Center"/>
          <Entry value="2" text="Right"/>
        </Domain>
      </Property>
      <Property name="SelectionPointLabelOpacity" id="5186.SelectionPointLabelOpacity" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="5186.SelectionPointLabelOpacity.range"/>
      </Property>
      <Property name="SelectionPointLabelShadow" id="5186.SelectionPointLabelShadow" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5186.SelectionPointLabelShadow.bool"/>
      </Property>
      <Property name="SelectionPointLabelVisibility" id="5186.SelectionPointLabelVisibility" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5186.SelectionPointLabelVisibility.bool"/>
      </Property>
      <Property name="SelectionPointSize" id="5186.SelectionPointSize" number_of_elements="1">
        <Element index="0" value="5"/>
        <Domain name="range" id="5186.SelectionPointSize.range"/>
      </Property>
      <Property name="SelectionRepresentation" id="5186.SelectionRepresentation" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="enum" id="5186.SelectionRepresentation.enum">
          <Entry value="0" text="Points"/>
          <Entry value="1" text="Wireframe"/>
          <Entry value="2" text="Surface"/>
        </Domain>
      </Property>
      <Property name="SelectionUseOutline" id="5186.SelectionUseOutline" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5186.SelectionUseOutline.bool"/>
      </Property>
      <Property name="SetScaleArray" id="5186.SetScaleArray" number_of_elements="5">
        <Element index="0" value=""/>
        <Element index="1" value=""/>
        <Element index="2" value=""/>
        <Element index="3" value=""/>
        <Element index="4" value=""/>
        <Domain name="array_list" id="5186.SetScaleArray.array_list"/>
      </Property>
      <Property name="ShaderPreset" id="5186.ShaderPreset" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="enum" id="5186.ShaderPreset.enum">
          <Entry value="0" text="Gaussian Blur (Default)"/>
          <Entry value="1" text="Sphere"/>
          <Entry value="2" text="Black-edged circle"/>
          <Entry value="3" text="Plain circle"/>
          <Entry value="4" text="Triangle"/>
          <Entry value="5" text="Square Outline"/>
        </Domain>
      </Property>
      <Property name="Specular" id="5186.Specular" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="range" id="5186.Specular.range"/>
      </Property>
      <Property name="SpecularColor" id="5186.SpecularColor" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="1"/>
        <Element index="2" value="1"/>
        <Domain name="range" id="5186.SpecularColor.range"/>
      </Property>
      <Property name="SpecularPower" id="5186.SpecularPower" number_of_elements="1">
        <Element index="0" value="100"/>
        <Domain name="range" id="5186.SpecularPower.range"/>
      </Property>
      <Property name="StaticMode" id="5186.StaticMode" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5186.StaticMode.bool"/>
      </Property>
      <Property name="StickyAxes" id="5186.StickyAxes" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5186.StickyAxes.bool"/>
      </Property>
      <Property name="SuppressLOD" id="5186.SuppressLOD" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5186.SuppressLOD.bool"/>
      </Property>
      <Property name="Texture" id="5186.Texture">
        <Domain name="groups" id="5186.Texture.groups"/>
      </Property>
      <Property name="Triangulate" id="5186.Triangulate" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5186.Triangulate.bool"/>
      </Property>
      <Property name="UseAxesOrigin" id="5186.UseAxesOrigin" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5186.UseAxesOrigin.bool"/>
      </Property>
      <Property name="UserTransform" id="5186.UserTransform" number_of_elements="16">
        <Element index="0" value="1"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Element index="3" value="0"/>
        <Element index="4" value="0"/>
        <Element index="5" value="1"/>
        <Element index="6" value="0"/>
        <Element index="7" value="0"/>
        <Element index="8" value="0"/>
        <Element index="9" value="0"/>
        <Element index="10" value="1"/>
        <Element index="11" value="0"/>
        <Element index="12" value="0"/>
        <Element index="13" value="0"/>
        <Element index="14" value="0"/>
        <Element index="15" value="1"/>
      </Property>
    </Proxy>
    <Proxy group="representations" type="GeometryRepresentation" id="5365" servers="21">
      <Property name="CubeAxesVisibility" id="5365.CubeAxesVisibility" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5365.CubeAxesVisibility.bool"/>
      </Property>
      <Property name="Input" id="5365.Input" number_of_elements="1">
        <Proxy value="5197" output_port="0"/>
        <Domain name="input_array_cell" id="5365.Input.input_array_cell"/>
        <Domain name="input_array_point" id="5365.Input.input_array_point"/>
        <Domain name="input_type" id="5365.Input.input_type"/>
      </Property>
      <Property name="Representation" id="5365.Representation" number_of_elements="1">
        <Element index="0" value="Surface"/>
        <Domain name="list" id="5365.Representation.list">
          <String text="3D Glyphs"/>
          <String text="Outline"/>
          <String text="Point Gaussian"/>
          <String text="Points"/>
          <String text="Surface"/>
          <String text="Surface With Edges"/>
          <String text="Wireframe"/>
        </Domain>
      </Property>
      <Property name="RepresentationTypesInfo" id="5365.RepresentationTypesInfo" number_of_elements="7">
        <Element index="0" value="3D Glyphs"/>
        <Element index="1" value="Outline"/>
        <Element index="2" value="Point Gaussian"/>
        <Element index="3" value="Points"/>
        <Element index="4" value="Surface"/>
        <Element index="5" value="Surface With Edges"/>
        <Element index="6" value="Wireframe"/>
      </Property>
      <Property name="SelectionCellFieldDataArrayName" id="5365.SelectionCellFieldDataArrayName" number_of_elements="1">
        <Element index="0" value="vtkOriginalCellIds"/>
        <Domain name="array_list" id="5365.SelectionCellFieldDataArrayName.array_list"/>
      </Property>
      <Property name="SelectionPointFieldDataArrayName" id="5365.SelectionPointFieldDataArrayName" number_of_elements="1">
        <Element index="0" value="v"/>
        <Domain name="array_list" id="5365.SelectionPointFieldDataArrayName.array_list">
          <String text="v"/>
        </Domain>
      </Property>
      <Property name="SelectionVisibility" id="5365.SelectionVisibility" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="5365.SelectionVisibility.bool"/>
      </Property>
      <Property name="Visibility" id="5365.Visibility" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5365.Visibility.bool"/>
      </Property>
      <Property name="Ambient" id="5365.Ambient" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="range" id="5365.Ambient.range"/>
      </Property>
      <Property name="AmbientColor" id="5365.AmbientColor" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="1"/>
        <Element index="2" value="1"/>
        <Domain name="range" id="5365.AmbientColor.range"/>
      </Property>
      <Property name="AxesOrigin" id="5365.AxesOrigin" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="5365.AxesOrigin.range"/>
      </Property>
      <Property name="BackfaceAmbientColor" id="5365.BackfaceAmbientColor" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="1"/>
        <Element index="2" value="1"/>
        <Domain name="range" id="5365.BackfaceAmbientColor.range"/>
      </Property>
      <Property name="BackfaceDiffuseColor" id="5365.BackfaceDiffuseColor" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="1"/>
        <Element index="2" value="1"/>
        <Domain name="range" id="5365.BackfaceDiffuseColor.range"/>
      </Property>
      <Property name="BackfaceOpacity" id="5365.BackfaceOpacity" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="5365.BackfaceOpacity.range"/>
      </Property>
      <Property name="BackfaceRepresentation" id="5365.BackfaceRepresentation" number_of_elements="1">
        <Element index="0" value="400"/>
        <Domain name="enum" id="5365.BackfaceRepresentation.enum">
          <Entry value="400" text="Follow Frontface"/>
          <Entry value="401" text="Cull Backface"/>
          <Entry value="402" text="Cull Frontface"/>
          <Entry value="0" text="Points"/>
          <Entry value="1" text="Wireframe"/>
          <Entry value="2" text="Surface"/>
          <Entry value="3" text="Surface With Edges"/>
        </Domain>
      </Property>
      <Property name="BlockColor" id="5365.BlockColor"/>
      <Property name="BlockColorsDistinctValues" id="5365.BlockColorsDistinctValues" number_of_elements="1">
        <Element index="0" value="12"/>
        <Domain name="range" id="5365.BlockColorsDistinctValues.range"/>
      </Property>
      <Property name="BlockOpacity" id="5365.BlockOpacity"/>
      <Property name="BlockVisibility" id="5365.BlockVisibility"/>
      <Property name="CenterStickyAxes" id="5365.CenterStickyAxes" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5365.CenterStickyAxes.bool"/>
      </Property>
      <Property name="Color" id="5365.Color" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="1"/>
        <Element index="2" value="1"/>
        <Domain name="range" id="5365.Color.range"/>
      </Property>
      <Property name="ColorArrayName" id="5365.ColorArrayName" number_of_elements="5">
        <Element index="0" value=""/>
        <Element index="1" value=""/>
        <Element index="2" value=""/>
        <Element index="3" value=""/>
        <Element index="4" value=""/>
        <Domain name="array_list" id="5365.ColorArrayName.array_list">
          <String text="v"/>
          <String text="vtkCompositeIndex"/>
        </Domain>
        <Domain name="field_list" id="5365.ColorArrayName.field_list">
          <Entry value="0" text="Point Data"/>
          <Entry value="1" text="Cell Data"/>
          <Entry value="2" text="Field Data"/>
          <Entry value="4" text="Vertex Data"/>
          <Entry value="5" text="Edge Data"/>
          <Entry value="6" text="Row Data"/>
        </Domain>
      </Property>
      <Property name="CubeAxesColor" id="5365.CubeAxesColor" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="1"/>
        <Element index="2" value="1"/>
        <Domain name="range" id="5365.CubeAxesColor.range"/>
      </Property>
      <Property name="CubeAxesCornerOffset" id="5365.CubeAxesCornerOffset" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="range" id="5365.CubeAxesCornerOffset.range"/>
      </Property>
      <Property name="CubeAxesFlyMode" id="5365.CubeAxesFlyMode" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="enum" id="5365.CubeAxesFlyMode.enum">
          <Entry value="0" text="Outer Edges"/>
          <Entry value="1" text="Closest Triad"/>
          <Entry value="2" text="Furthest Triad"/>
          <Entry value="3" text="Static Triad"/>
          <Entry value="4" text="Static Edges"/>
        </Domain>
      </Property>
      <Property name="CubeAxesGridLineLocation" id="5365.CubeAxesGridLineLocation" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="enum" id="5365.CubeAxesGridLineLocation.enum">
          <Entry value="0" text="All Faces"/>
          <Entry value="1" text="Closest Faces"/>
          <Entry value="2" text="Furthest Faces"/>
        </Domain>
      </Property>
      <Property name="CubeAxesInertia" id="5365.CubeAxesInertia" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="5365.CubeAxesInertia.range"/>
      </Property>
      <Property name="CubeAxesTickLocation" id="5365.CubeAxesTickLocation" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="enum" id="5365.CubeAxesTickLocation.enum">
          <Entry value="0" text="Inside"/>
          <Entry value="1" text="Outside"/>
          <Entry value="2" text="Both"/>
        </Domain>
      </Property>
      <Property name="CubeAxesUseDefaultXTitle" id="5365.CubeAxesUseDefaultXTitle" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="5365.CubeAxesUseDefaultXTitle.bool"/>
      </Property>
      <Property name="CubeAxesUseDefaultYTitle" id="5365.CubeAxesUseDefaultYTitle" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="5365.CubeAxesUseDefaultYTitle.bool"/>
      </Property>
      <Property name="CubeAxesUseDefaultZTitle" id="5365.CubeAxesUseDefaultZTitle" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="5365.CubeAxesUseDefaultZTitle.bool"/>
      </Property>
      <Property name="CubeAxesXAxisMinorTickVisibility" id="5365.CubeAxesXAxisMinorTickVisibility" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="5365.CubeAxesXAxisMinorTickVisibility.bool"/>
      </Property>
      <Property name="CubeAxesXAxisTickVisibility" id="5365.CubeAxesXAxisTickVisibility" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="5365.CubeAxesXAxisTickVisibility.bool"/>
      </Property>
      <Property name="CubeAxesXAxisVisibility" id="5365.CubeAxesXAxisVisibility" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="5365.CubeAxesXAxisVisibility.bool"/>
      </Property>
      <Property name="CubeAxesXGridLines" id="5365.CubeAxesXGridLines" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5365.CubeAxesXGridLines.bool"/>
      </Property>
      <Property name="CubeAxesXLabelFormat" id="5365.CubeAxesXLabelFormat" number_of_elements="1">
        <Element index="0" value="%-#6.3g"/>
      </Property>
      <Property name="CubeAxesXTitle" id="5365.CubeAxesXTitle" number_of_elements="1">
        <Element index="0" value="X-Axis"/>
      </Property>
      <Property name="CubeAxesYAxisMinorTickVisibility" id="5365.CubeAxesYAxisMinorTickVisibility" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="5365.CubeAxesYAxisMinorTickVisibility.bool"/>
      </Property>
      <Property name="CubeAxesYAxisTickVisibility" id="5365.CubeAxesYAxisTickVisibility" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="5365.CubeAxesYAxisTickVisibility.bool"/>
      </Property>
      <Property name="CubeAxesYAxisVisibility" id="5365.CubeAxesYAxisVisibility" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="5365.CubeAxesYAxisVisibility.bool"/>
      </Property>
      <Property name="CubeAxesYGridLines" id="5365.CubeAxesYGridLines" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5365.CubeAxesYGridLines.bool"/>
      </Property>
      <Property name="CubeAxesYLabelFormat" id="5365.CubeAxesYLabelFormat" number_of_elements="1">
        <Element index="0" value="%-#6.3g"/>
      </Property>
      <Property name="CubeAxesYTitle" id="5365.CubeAxesYTitle" number_of_elements="1">
        <Element index="0" value="Y-Axis"/>
      </Property>
      <Property name="CubeAxesZAxisMinorTickVisibility" id="5365.CubeAxesZAxisMinorTickVisibility" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="5365.CubeAxesZAxisMinorTickVisibility.bool"/>
      </Property>
      <Property name="CubeAxesZAxisTickVisibility" id="5365.CubeAxesZAxisTickVisibility" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="5365.CubeAxesZAxisTickVisibility.bool"/>
      </Property>
      <Property name="CubeAxesZAxisVisibility" id="5365.CubeAxesZAxisVisibility" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="5365.CubeAxesZAxisVisibility.bool"/>
      </Property>
      <Property name="CubeAxesZGridLines" id="5365.CubeAxesZGridLines" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5365.CubeAxesZGridLines.bool"/>
      </Property>
      <Property name="CubeAxesZLabelFormat" id="5365.CubeAxesZLabelFormat" number_of_elements="1">
        <Element index="0" value="%-#6.3g"/>
      </Property>
      <Property name="CubeAxesZTitle" id="5365.CubeAxesZTitle" number_of_elements="1">
        <Element index="0" value="Z-Axis"/>
      </Property>
      <Property name="CustomBounds" id="5365.CustomBounds" number_of_elements="6">
        <Element index="0" value="0"/>
        <Element index="1" value="1"/>
        <Element index="2" value="0"/>
        <Element index="3" value="1"/>
        <Element index="4" value="0"/>
        <Element index="5" value="1"/>
      </Property>
      <Property name="CustomBoundsActive" id="5365.CustomBoundsActive" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
      </Property>
      <Property name="CustomRange" id="5365.CustomRange" number_of_elements="6">
        <Element index="0" value="0"/>
        <Element index="1" value="1"/>
        <Element index="2" value="0"/>
        <Element index="3" value="1"/>
        <Element index="4" value="0"/>
        <Element index="5" value="1"/>
      </Property>
      <Property name="CustomRangeActive" id="5365.CustomRangeActive" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
      </Property>
      <Property name="CustomShader" id="5365.CustomShader" number_of_elements="1">
        <Element index="0" value=""/>
      </Property>
      <Property name="DataBounds" id="5365.DataBounds" number_of_elements="6">
        <Element index="0" value="1.97626258336499e-323"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Element index="3" value="0"/>
        <Element index="4" value="0"/>
        <Element index="5" value="5.62406663660836e-316"/>
      </Property>
      <Property name="Diffuse" id="5365.Diffuse" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="5365.Diffuse.range"/>
      </Property>
      <Property name="DiffuseColor" id="5365.DiffuseColor" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="1"/>
        <Element index="2" value="1"/>
        <Domain name="range" id="5365.DiffuseColor.range"/>
      </Property>
      <Property name="EdgeColor" id="5365.EdgeColor" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0.5"/>
        <Domain name="range" id="5365.EdgeColor.range"/>
      </Property>
      <Property name="Emissive" id="5365.Emissive" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5365.Emissive.bool"/>
      </Property>
      <Property name="GaussianRadius" id="5365.GaussianRadius" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="range" id="5365.GaussianRadius.range"/>
      </Property>
      <Property name="GlyphType" id="5365.GlyphType" number_of_elements="1">
        <Proxy value="5220" output_port="0"/>
        <Domain name="input_type" id="5365.GlyphType.input_type"/>
        <Domain name="proxy_list" id="5365.GlyphType.proxy_list">
          <Proxy value="5220"/>
          <Proxy value="5231"/>
          <Proxy value="5242"/>
          <Proxy value="5253"/>
          <Proxy value="5264"/>
          <Proxy value="5275"/>
          <Proxy value="5286"/>
        </Domain>
      </Property>
      <Property name="InterpolateScalarsBeforeMapping" id="5365.InterpolateScalarsBeforeMapping" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="5365.InterpolateScalarsBeforeMapping.bool"/>
      </Property>
      <Property name="Interpolation" id="5365.Interpolation" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="enum" id="5365.Interpolation.enum">
          <Entry value="0" text="Flat"/>
          <Entry value="1" text="Gouraud"/>
        </Domain>
      </Property>
      <Property name="LineWidth" id="5365.LineWidth" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="5365.LineWidth.range"/>
      </Property>
      <Property name="LookupTable" id="5365.LookupTable">
        <Domain name="groups" id="5365.LookupTable.groups"/>
      </Property>
      <Property name="MapScalars" id="5365.MapScalars" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="5365.MapScalars.bool"/>
      </Property>
      <Property name="Masking" id="5365.Masking" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5365.Masking.bool"/>
      </Property>
      <Property name="MeshVisibility" id="5365.MeshVisibility" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5365.MeshVisibility.bool"/>
      </Property>
      <Property name="NonlinearSubdivisionLevel" id="5365.NonlinearSubdivisionLevel" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="5365.NonlinearSubdivisionLevel.range"/>
      </Property>
      <Property name="Opacity" id="5365.Opacity" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="5365.Opacity.range"/>
      </Property>
      <Property name="OpacityArray" id="5365.OpacityArray" number_of_elements="5">
        <Element index="0" value=""/>
        <Element index="1" value=""/>
        <Element index="2" value=""/>
        <Element index="3" value=""/>
        <Element index="4" value=""/>
        <Domain name="array_list" id="5365.OpacityArray.array_list"/>
      </Property>
      <Property name="OpacityByArray" id="5365.OpacityByArray" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5365.OpacityByArray.bool"/>
      </Property>
      <Property name="OpacityTransferFunction" id="5365.OpacityTransferFunction" number_of_elements="1">
        <Proxy value="5319"/>
        <Domain name="groups" id="5365.OpacityTransferFunction.groups"/>
        <Domain name="proxy_list" id="5365.OpacityTransferFunction.proxy_list">
          <Proxy value="5319"/>
        </Domain>
      </Property>
      <Property name="Orient" id="5365.Orient" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5365.Orient.bool"/>
      </Property>
      <Property name="Orientation" id="5365.Orientation" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="5365.Orientation.range"/>
      </Property>
      <Property name="OrientationMode" id="5365.OrientationMode" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="enum" id="5365.OrientationMode.enum">
          <Entry value="0" text="Direction"/>
          <Entry value="1" text="Rotation"/>
        </Domain>
      </Property>
      <Property name="Origin" id="5365.Origin" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="5365.Origin.range"/>
      </Property>
      <Property name="OriginalBoundsRangeActive" id="5365.OriginalBoundsRangeActive" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
      </Property>
      <Property name="Pickable" id="5365.Pickable" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="5365.Pickable.bool"/>
      </Property>
      <Property name="PointSize" id="5365.PointSize" number_of_elements="1">
        <Element index="0" value="2"/>
        <Domain name="range" id="5365.PointSize.range"/>
      </Property>
      <Property name="Position" id="5365.Position" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="5365.Position.range"/>
      </Property>
      <Property name="Scale" id="5365.Scale" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="1"/>
        <Element index="2" value="1"/>
        <Domain name="range" id="5365.Scale.range"/>
      </Property>
      <Property name="ScaleByArray" id="5365.ScaleByArray" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5365.ScaleByArray.bool"/>
      </Property>
      <Property name="ScaleFactor" id="5365.ScaleFactor" number_of_elements="1">
        <Element index="0" value="0.0100000001490116"/>
        <Domain name="bounds" id="5365.ScaleFactor.bounds"/>
        <Domain name="scalar_range" id="5365.ScaleFactor.scalar_range"/>
        <Domain name="vector_range" id="5365.ScaleFactor.vector_range"/>
      </Property>
      <Property name="ScaleMode" id="5365.ScaleMode" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="enum" id="5365.ScaleMode.enum">
          <Entry value="0" text="No Data Scaling Off"/>
          <Entry value="1" text="Magnitude"/>
          <Entry value="2" text="Vector Components"/>
        </Domain>
      </Property>
      <Property name="ScaleTransferFunction" id="5365.ScaleTransferFunction" number_of_elements="1">
        <Proxy value="5320"/>
        <Domain name="groups" id="5365.ScaleTransferFunction.groups"/>
        <Domain name="proxy_list" id="5365.ScaleTransferFunction.proxy_list">
          <Proxy value="5320"/>
        </Domain>
      </Property>
      <Property name="Scaling" id="5365.Scaling" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5365.Scaling.bool"/>
      </Property>
      <Property name="SelectMaskArray" id="5365.SelectMaskArray" number_of_elements="1">
        <Element index="0" value=""/>
      </Property>
      <Property name="SelectOrientationVectors" id="5365.SelectOrientationVectors" number_of_elements="1">
        <Element index="0" value=""/>
      </Property>
      <Property name="SelectScaleArray" id="5365.SelectScaleArray" number_of_elements="1">
        <Element index="0" value=""/>
      </Property>
      <Property name="SelectionCellLabelBold" id="5365.SelectionCellLabelBold" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5365.SelectionCellLabelBold.bool"/>
      </Property>
      <Property name="SelectionCellLabelColor" id="5365.SelectionCellLabelColor" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="1"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="5365.SelectionCellLabelColor.range"/>
      </Property>
      <Property name="SelectionCellLabelFontFamily" id="5365.SelectionCellLabelFontFamily" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="enum" id="5365.SelectionCellLabelFontFamily.enum">
          <Entry value="0" text="Arial"/>
          <Entry value="1" text="Courier"/>
          <Entry value="2" text="Times"/>
        </Domain>
      </Property>
      <Property name="SelectionCellLabelFontSize" id="5365.SelectionCellLabelFontSize" number_of_elements="1">
        <Element index="0" value="18"/>
        <Domain name="range" id="5365.SelectionCellLabelFontSize.range"/>
      </Property>
      <Property name="SelectionCellLabelFormat" id="5365.SelectionCellLabelFormat" number_of_elements="1">
        <Element index="0" value=""/>
      </Property>
      <Property name="SelectionCellLabelItalic" id="5365.SelectionCellLabelItalic" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5365.SelectionCellLabelItalic.bool"/>
      </Property>
      <Property name="SelectionCellLabelJustification" id="5365.SelectionCellLabelJustification" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="enum" id="5365.SelectionCellLabelJustification.enum">
          <Entry value="0" text="Left"/>
          <Entry value="1" text="Center"/>
          <Entry value="2" text="Right"/>
        </Domain>
      </Property>
      <Property name="SelectionCellLabelOpacity" id="5365.SelectionCellLabelOpacity" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="5365.SelectionCellLabelOpacity.range"/>
      </Property>
      <Property name="SelectionCellLabelShadow" id="5365.SelectionCellLabelShadow" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5365.SelectionCellLabelShadow.bool"/>
      </Property>
      <Property name="SelectionCellLabelVisibility" id="5365.SelectionCellLabelVisibility" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5365.SelectionCellLabelVisibility.bool"/>
      </Property>
      <Property name="SelectionColor" id="5365.SelectionColor" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="0"/>
        <Element index="2" value="1"/>
        <Domain name="range" id="5365.SelectionColor.range"/>
      </Property>
      <Property name="SelectionLineWidth" id="5365.SelectionLineWidth" number_of_elements="1">
        <Element index="0" value="2"/>
        <Domain name="range" id="5365.SelectionLineWidth.range"/>
      </Property>
      <Property name="SelectionOpacity" id="5365.SelectionOpacity" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="5365.SelectionOpacity.range"/>
      </Property>
      <Property name="SelectionPointLabelBold" id="5365.SelectionPointLabelBold" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5365.SelectionPointLabelBold.bool"/>
      </Property>
      <Property name="SelectionPointLabelColor" id="5365.SelectionPointLabelColor" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="1"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="5365.SelectionPointLabelColor.range"/>
      </Property>
      <Property name="SelectionPointLabelFontFamily" id="5365.SelectionPointLabelFontFamily" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="enum" id="5365.SelectionPointLabelFontFamily.enum">
          <Entry value="0" text="Arial"/>
          <Entry value="1" text="Courier"/>
          <Entry value="2" text="Times"/>
        </Domain>
      </Property>
      <Property name="SelectionPointLabelFontSize" id="5365.SelectionPointLabelFontSize" number_of_elements="1">
        <Element index="0" value="18"/>
        <Domain name="range" id="5365.SelectionPointLabelFontSize.range"/>
      </Property>
      <Property name="SelectionPointLabelFormat" id="5365.SelectionPointLabelFormat" number_of_elements="1">
        <Element index="0" value=""/>
      </Property>
      <Property name="SelectionPointLabelItalic" id="5365.SelectionPointLabelItalic" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5365.SelectionPointLabelItalic.bool"/>
      </Property>
      <Property name="SelectionPointLabelJustification" id="5365.SelectionPointLabelJustification" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="enum" id="5365.SelectionPointLabelJustification.enum">
          <Entry value="0" text="Left"/>
          <Entry value="1" text="Center"/>
          <Entry value="2" text="Right"/>
        </Domain>
      </Property>
      <Property name="SelectionPointLabelOpacity" id="5365.SelectionPointLabelOpacity" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="5365.SelectionPointLabelOpacity.range"/>
      </Property>
      <Property name="SelectionPointLabelShadow" id="5365.SelectionPointLabelShadow" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5365.SelectionPointLabelShadow.bool"/>
      </Property>
      <Property name="SelectionPointLabelVisibility" id="5365.SelectionPointLabelVisibility" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5365.SelectionPointLabelVisibility.bool"/>
      </Property>
      <Property name="SelectionPointSize" id="5365.SelectionPointSize" number_of_elements="1">
        <Element index="0" value="5"/>
        <Domain name="range" id="5365.SelectionPointSize.range"/>
      </Property>
      <Property name="SelectionRepresentation" id="5365.SelectionRepresentation" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="enum" id="5365.SelectionRepresentation.enum">
          <Entry value="0" text="Points"/>
          <Entry value="1" text="Wireframe"/>
          <Entry value="2" text="Surface"/>
        </Domain>
      </Property>
      <Property name="SelectionUseOutline" id="5365.SelectionUseOutline" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5365.SelectionUseOutline.bool"/>
      </Property>
      <Property name="SetScaleArray" id="5365.SetScaleArray" number_of_elements="5">
        <Element index="0" value=""/>
        <Element index="1" value=""/>
        <Element index="2" value=""/>
        <Element index="3" value=""/>
        <Element index="4" value=""/>
        <Domain name="array_list" id="5365.SetScaleArray.array_list"/>
      </Property>
      <Property name="ShaderPreset" id="5365.ShaderPreset" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="enum" id="5365.ShaderPreset.enum">
          <Entry value="0" text="Gaussian Blur (Default)"/>
          <Entry value="1" text="Sphere"/>
          <Entry value="2" text="Black-edged circle"/>
          <Entry value="3" text="Plain circle"/>
          <Entry value="4" text="Triangle"/>
          <Entry value="5" text="Square Outline"/>
        </Domain>
      </Property>
      <Property name="Specular" id="5365.Specular" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="range" id="5365.Specular.range"/>
      </Property>
      <Property name="SpecularColor" id="5365.SpecularColor" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="1"/>
        <Element index="2" value="1"/>
        <Domain name="range" id="5365.SpecularColor.range"/>
      </Property>
      <Property name="SpecularPower" id="5365.SpecularPower" number_of_elements="1">
        <Element index="0" value="100"/>
        <Domain name="range" id="5365.SpecularPower.range"/>
      </Property>
      <Property name="StaticMode" id="5365.StaticMode" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5365.StaticMode.bool"/>
      </Property>
      <Property name="StickyAxes" id="5365.StickyAxes" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5365.StickyAxes.bool"/>
      </Property>
      <Property name="SuppressLOD" id="5365.SuppressLOD" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5365.SuppressLOD.bool"/>
      </Property>
      <Property name="Texture" id="5365.Texture">
        <Domain name="groups" id="5365.Texture.groups"/>
      </Property>
      <Property name="Triangulate" id="5365.Triangulate" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5365.Triangulate.bool"/>
      </Property>
      <Property name="UseAxesOrigin" id="5365.UseAxesOrigin" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5365.UseAxesOrigin.bool"/>
      </Property>
      <Property name="UserTransform" id="5365.UserTransform" number_of_elements="16">
        <Element index="0" value="1"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Element index="3" value="0"/>
        <Element index="4" value="0"/>
        <Element index="5" value="1"/>
        <Element index="6" value="0"/>
        <Element index="7" value="0"/>
        <Element index="8" value="0"/>
        <Element index="9" value="0"/>
        <Element index="10" value="1"/>
        <Element index="11" value="0"/>
        <Element index="12" value="0"/>
        <Element index="13" value="0"/>
        <Element index="14" value="0"/>
        <Element index="15" value="1"/>
      </Property>
    </Proxy>
    <Proxy group="representations" type="UnstructuredGridRepresentation" id="5559" servers="21">
      <Property name="CubeAxesVisibility" id="5559.CubeAxesVisibility" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5559.CubeAxesVisibility.bool"/>
      </Property>
      <Property name="Input" id="5559.Input" number_of_elements="1">
        <Proxy value="5376" output_port="0"/>
        <Domain name="input_array_cell" id="5559.Input.input_array_cell"/>
        <Domain name="input_array_point" id="5559.Input.input_array_point"/>
        <Domain name="input_type" id="5559.Input.input_type"/>
      </Property>
      <Property name="Representation" id="5559.Representation" number_of_elements="1">
        <Element index="0" value="Surface"/>
        <Domain name="list" id="5559.Representation.list">
          <String text="3D Glyphs"/>
          <String text="Outline"/>
          <String text="Point Gaussian"/>
          <String text="Points"/>
          <String text="Surface"/>
          <String text="Surface With Edges"/>
          <String text="Volume"/>
          <String text="Wireframe"/>
        </Domain>
      </Property>
      <Property name="RepresentationTypesInfo" id="5559.RepresentationTypesInfo" number_of_elements="8">
        <Element index="0" value="3D Glyphs"/>
        <Element index="1" value="Outline"/>
        <Element index="2" value="Point Gaussian"/>
        <Element index="3" value="Points"/>
        <Element index="4" value="Surface"/>
        <Element index="5" value="Surface With Edges"/>
        <Element index="6" value="Volume"/>
        <Element index="7" value="Wireframe"/>
      </Property>
      <Property name="SelectionCellFieldDataArrayName" id="5559.SelectionCellFieldDataArrayName" number_of_elements="1">
        <Element index="0" value="vtkOriginalCellIds"/>
        <Domain name="array_list" id="5559.SelectionCellFieldDataArrayName.array_list"/>
      </Property>
      <Property name="SelectionPointFieldDataArrayName" id="5559.SelectionPointFieldDataArrayName" number_of_elements="1">
        <Element index="0" value="v"/>
        <Domain name="array_list" id="5559.SelectionPointFieldDataArrayName.array_list">
          <String text="v"/>
        </Domain>
      </Property>
      <Property name="SelectionVisibility" id="5559.SelectionVisibility" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="5559.SelectionVisibility.bool"/>
      </Property>
      <Property name="Visibility" id="5559.Visibility" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="5559.Visibility.bool"/>
      </Property>
      <Property name="Ambient" id="5559.Ambient" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="range" id="5559.Ambient.range"/>
      </Property>
      <Property name="AmbientColor" id="5559.AmbientColor" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="1"/>
        <Element index="2" value="1"/>
        <Domain name="range" id="5559.AmbientColor.range"/>
      </Property>
      <Property name="AxesOrigin" id="5559.AxesOrigin" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="5559.AxesOrigin.range"/>
      </Property>
      <Property name="BackfaceAmbientColor" id="5559.BackfaceAmbientColor" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="1"/>
        <Element index="2" value="1"/>
        <Domain name="range" id="5559.BackfaceAmbientColor.range"/>
      </Property>
      <Property name="BackfaceDiffuseColor" id="5559.BackfaceDiffuseColor" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="1"/>
        <Element index="2" value="1"/>
        <Domain name="range" id="5559.BackfaceDiffuseColor.range"/>
      </Property>
      <Property name="BackfaceOpacity" id="5559.BackfaceOpacity" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="5559.BackfaceOpacity.range"/>
      </Property>
      <Property name="BackfaceRepresentation" id="5559.BackfaceRepresentation" number_of_elements="1">
        <Element index="0" value="400"/>
        <Domain name="enum" id="5559.BackfaceRepresentation.enum">
          <Entry value="400" text="Follow Frontface"/>
          <Entry value="401" text="Cull Backface"/>
          <Entry value="402" text="Cull Frontface"/>
          <Entry value="0" text="Points"/>
          <Entry value="1" text="Wireframe"/>
          <Entry value="2" text="Surface"/>
          <Entry value="3" text="Surface With Edges"/>
        </Domain>
      </Property>
      <Property name="BlockColor" id="5559.BlockColor"/>
      <Property name="BlockColorsDistinctValues" id="5559.BlockColorsDistinctValues" number_of_elements="1">
        <Element index="0" value="12"/>
        <Domain name="range" id="5559.BlockColorsDistinctValues.range"/>
      </Property>
      <Property name="BlockOpacity" id="5559.BlockOpacity"/>
      <Property name="BlockVisibility" id="5559.BlockVisibility"/>
      <Property name="CenterStickyAxes" id="5559.CenterStickyAxes" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5559.CenterStickyAxes.bool"/>
      </Property>
      <Property name="Color" id="5559.Color" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="1"/>
        <Element index="2" value="1"/>
        <Domain name="range" id="5559.Color.range"/>
      </Property>
      <Property name="ColorArrayName" id="5559.ColorArrayName" number_of_elements="5">
        <Element index="0" value=""/>
        <Element index="1" value=""/>
        <Element index="2" value=""/>
        <Element index="3" value=""/>
        <Element index="4" value=""/>
        <Domain name="array_list" id="5559.ColorArrayName.array_list">
          <String text="v"/>
        </Domain>
        <Domain name="field_list" id="5559.ColorArrayName.field_list">
          <Entry value="0" text="Point Data"/>
          <Entry value="1" text="Cell Data"/>
          <Entry value="2" text="Field Data"/>
          <Entry value="4" text="Vertex Data"/>
          <Entry value="5" text="Edge Data"/>
          <Entry value="6" text="Row Data"/>
        </Domain>
      </Property>
      <Property name="CubeAxesColor" id="5559.CubeAxesColor" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="1"/>
        <Element index="2" value="1"/>
        <Domain name="range" id="5559.CubeAxesColor.range"/>
      </Property>
      <Property name="CubeAxesCornerOffset" id="5559.CubeAxesCornerOffset" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="range" id="5559.CubeAxesCornerOffset.range"/>
      </Property>
      <Property name="CubeAxesFlyMode" id="5559.CubeAxesFlyMode" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="enum" id="5559.CubeAxesFlyMode.enum">
          <Entry value="0" text="Outer Edges"/>
          <Entry value="1" text="Closest Triad"/>
          <Entry value="2" text="Furthest Triad"/>
          <Entry value="3" text="Static Triad"/>
          <Entry value="4" text="Static Edges"/>
        </Domain>
      </Property>
      <Property name="CubeAxesGridLineLocation" id="5559.CubeAxesGridLineLocation" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="enum" id="5559.CubeAxesGridLineLocation.enum">
          <Entry value="0" text="All Faces"/>
          <Entry value="1" text="Closest Faces"/>
          <Entry value="2" text="Furthest Faces"/>
        </Domain>
      </Property>
      <Property name="CubeAxesInertia" id="5559.CubeAxesInertia" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="5559.CubeAxesInertia.range"/>
      </Property>
      <Property name="CubeAxesTickLocation" id="5559.CubeAxesTickLocation" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="enum" id="5559.CubeAxesTickLocation.enum">
          <Entry value="0" text="Inside"/>
          <Entry value="1" text="Outside"/>
          <Entry value="2" text="Both"/>
        </Domain>
      </Property>
      <Property name="CubeAxesUseDefaultXTitle" id="5559.CubeAxesUseDefaultXTitle" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="5559.CubeAxesUseDefaultXTitle.bool"/>
      </Property>
      <Property name="CubeAxesUseDefaultYTitle" id="5559.CubeAxesUseDefaultYTitle" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="5559.CubeAxesUseDefaultYTitle.bool"/>
      </Property>
      <Property name="CubeAxesUseDefaultZTitle" id="5559.CubeAxesUseDefaultZTitle" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="5559.CubeAxesUseDefaultZTitle.bool"/>
      </Property>
      <Property name="CubeAxesXAxisMinorTickVisibility" id="5559.CubeAxesXAxisMinorTickVisibility" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="5559.CubeAxesXAxisMinorTickVisibility.bool"/>
      </Property>
      <Property name="CubeAxesXAxisTickVisibility" id="5559.CubeAxesXAxisTickVisibility" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="5559.CubeAxesXAxisTickVisibility.bool"/>
      </Property>
      <Property name="CubeAxesXAxisVisibility" id="5559.CubeAxesXAxisVisibility" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="5559.CubeAxesXAxisVisibility.bool"/>
      </Property>
      <Property name="CubeAxesXGridLines" id="5559.CubeAxesXGridLines" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5559.CubeAxesXGridLines.bool"/>
      </Property>
      <Property name="CubeAxesXLabelFormat" id="5559.CubeAxesXLabelFormat" number_of_elements="1">
        <Element index="0" value="%-#6.3g"/>
      </Property>
      <Property name="CubeAxesXTitle" id="5559.CubeAxesXTitle" number_of_elements="1">
        <Element index="0" value="X-Axis"/>
      </Property>
      <Property name="CubeAxesYAxisMinorTickVisibility" id="5559.CubeAxesYAxisMinorTickVisibility" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="5559.CubeAxesYAxisMinorTickVisibility.bool"/>
      </Property>
      <Property name="CubeAxesYAxisTickVisibility" id="5559.CubeAxesYAxisTickVisibility" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="5559.CubeAxesYAxisTickVisibility.bool"/>
      </Property>
      <Property name="CubeAxesYAxisVisibility" id="5559.CubeAxesYAxisVisibility" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="5559.CubeAxesYAxisVisibility.bool"/>
      </Property>
      <Property name="CubeAxesYGridLines" id="5559.CubeAxesYGridLines" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5559.CubeAxesYGridLines.bool"/>
      </Property>
      <Property name="CubeAxesYLabelFormat" id="5559.CubeAxesYLabelFormat" number_of_elements="1">
        <Element index="0" value="%-#6.3g"/>
      </Property>
      <Property name="CubeAxesYTitle" id="5559.CubeAxesYTitle" number_of_elements="1">
        <Element index="0" value="Y-Axis"/>
      </Property>
      <Property name="CubeAxesZAxisMinorTickVisibility" id="5559.CubeAxesZAxisMinorTickVisibility" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="5559.CubeAxesZAxisMinorTickVisibility.bool"/>
      </Property>
      <Property name="CubeAxesZAxisTickVisibility" id="5559.CubeAxesZAxisTickVisibility" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="5559.CubeAxesZAxisTickVisibility.bool"/>
      </Property>
      <Property name="CubeAxesZAxisVisibility" id="5559.CubeAxesZAxisVisibility" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="5559.CubeAxesZAxisVisibility.bool"/>
      </Property>
      <Property name="CubeAxesZGridLines" id="5559.CubeAxesZGridLines" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5559.CubeAxesZGridLines.bool"/>
      </Property>
      <Property name="CubeAxesZLabelFormat" id="5559.CubeAxesZLabelFormat" number_of_elements="1">
        <Element index="0" value="%-#6.3g"/>
      </Property>
      <Property name="CubeAxesZTitle" id="5559.CubeAxesZTitle" number_of_elements="1">
        <Element index="0" value="Z-Axis"/>
      </Property>
      <Property name="CustomBounds" id="5559.CustomBounds" number_of_elements="6">
        <Element index="0" value="0"/>
        <Element index="1" value="1"/>
        <Element index="2" value="0"/>
        <Element index="3" value="1"/>
        <Element index="4" value="0"/>
        <Element index="5" value="1"/>
      </Property>
      <Property name="CustomBoundsActive" id="5559.CustomBoundsActive" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
      </Property>
      <Property name="CustomRange" id="5559.CustomRange" number_of_elements="6">
        <Element index="0" value="0"/>
        <Element index="1" value="1"/>
        <Element index="2" value="0"/>
        <Element index="3" value="1"/>
        <Element index="4" value="0"/>
        <Element index="5" value="1"/>
      </Property>
      <Property name="CustomRangeActive" id="5559.CustomRangeActive" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
      </Property>
      <Property name="CustomShader" id="5559.CustomShader" number_of_elements="1">
        <Element index="0" value=""/>
      </Property>
      <Property name="DataBounds" id="5559.DataBounds" number_of_elements="6">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Element index="3" value="0"/>
        <Element index="4" value="0"/>
        <Element index="5" value="0"/>
      </Property>
      <Property name="Diffuse" id="5559.Diffuse" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="5559.Diffuse.range"/>
      </Property>
      <Property name="DiffuseColor" id="5559.DiffuseColor" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="1"/>
        <Element index="2" value="1"/>
        <Domain name="range" id="5559.DiffuseColor.range"/>
      </Property>
      <Property name="EdgeColor" id="5559.EdgeColor" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0.5"/>
        <Domain name="range" id="5559.EdgeColor.range"/>
      </Property>
      <Property name="Emissive" id="5559.Emissive" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5559.Emissive.bool"/>
      </Property>
      <Property name="ExtractedBlockIndex" id="5559.ExtractedBlockIndex" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="tree" id="5559.ExtractedBlockIndex.tree"/>
      </Property>
      <Property name="GaussianRadius" id="5559.GaussianRadius" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="range" id="5559.GaussianRadius.range"/>
      </Property>
      <Property name="GlyphType" id="5559.GlyphType" number_of_elements="1">
        <Proxy value="5399" output_port="0"/>
        <Domain name="input_type" id="5559.GlyphType.input_type"/>
        <Domain name="proxy_list" id="5559.GlyphType.proxy_list">
          <Proxy value="5399"/>
          <Proxy value="5410"/>
          <Proxy value="5421"/>
          <Proxy value="5432"/>
          <Proxy value="5443"/>
          <Proxy value="5454"/>
          <Proxy value="5465"/>
        </Domain>
      </Property>
      <Property name="InterpolateScalarsBeforeMapping" id="5559.InterpolateScalarsBeforeMapping" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="5559.InterpolateScalarsBeforeMapping.bool"/>
      </Property>
      <Property name="Interpolation" id="5559.Interpolation" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="enum" id="5559.Interpolation.enum">
          <Entry value="0" text="Flat"/>
          <Entry value="1" text="Gouraud"/>
        </Domain>
      </Property>
      <Property name="LineWidth" id="5559.LineWidth" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="5559.LineWidth.range"/>
      </Property>
      <Property name="LookupTable" id="5559.LookupTable">
        <Domain name="groups" id="5559.LookupTable.groups"/>
      </Property>
      <Property name="MapScalars" id="5559.MapScalars" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="5559.MapScalars.bool"/>
      </Property>
      <Property name="Masking" id="5559.Masking" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5559.Masking.bool"/>
      </Property>
      <Property name="MeshVisibility" id="5559.MeshVisibility" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5559.MeshVisibility.bool"/>
      </Property>
      <Property name="NonlinearSubdivisionLevel" id="5559.NonlinearSubdivisionLevel" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="5559.NonlinearSubdivisionLevel.range"/>
      </Property>
      <Property name="Opacity" id="5559.Opacity" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="5559.Opacity.range"/>
      </Property>
      <Property name="OpacityArray" id="5559.OpacityArray" number_of_elements="5">
        <Element index="0" value=""/>
        <Element index="1" value=""/>
        <Element index="2" value=""/>
        <Element index="3" value=""/>
        <Element index="4" value=""/>
        <Domain name="array_list" id="5559.OpacityArray.array_list"/>
      </Property>
      <Property name="OpacityByArray" id="5559.OpacityByArray" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5559.OpacityByArray.bool"/>
      </Property>
      <Property name="OpacityTransferFunction" id="5559.OpacityTransferFunction" number_of_elements="1">
        <Proxy value="5498"/>
        <Domain name="groups" id="5559.OpacityTransferFunction.groups"/>
        <Domain name="proxy_list" id="5559.OpacityTransferFunction.proxy_list">
          <Proxy value="5498"/>
        </Domain>
      </Property>
      <Property name="Orient" id="5559.Orient" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5559.Orient.bool"/>
      </Property>
      <Property name="Orientation" id="5559.Orientation" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="5559.Orientation.range"/>
      </Property>
      <Property name="OrientationMode" id="5559.OrientationMode" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="enum" id="5559.OrientationMode.enum">
          <Entry value="0" text="Direction"/>
          <Entry value="1" text="Rotation"/>
        </Domain>
      </Property>
      <Property name="Origin" id="5559.Origin" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="5559.Origin.range"/>
      </Property>
      <Property name="OriginalBoundsRangeActive" id="5559.OriginalBoundsRangeActive" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
      </Property>
      <Property name="Pickable" id="5559.Pickable" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="5559.Pickable.bool"/>
      </Property>
      <Property name="PointSize" id="5559.PointSize" number_of_elements="1">
        <Element index="0" value="2"/>
        <Domain name="range" id="5559.PointSize.range"/>
      </Property>
      <Property name="Position" id="5559.Position" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="5559.Position.range"/>
      </Property>
      <Property name="ScalarOpacityFunction" id="5559.ScalarOpacityFunction">
        <Domain name="groups" id="5559.ScalarOpacityFunction.groups"/>
      </Property>
      <Property name="ScalarOpacityUnitDistance" id="5559.ScalarOpacityUnitDistance" number_of_elements="1">
        <Element index="0" value="0.00371512632092895"/>
        <Domain name="bounds" id="5559.ScalarOpacityUnitDistance.bounds"/>
      </Property>
      <Property name="Scale" id="5559.Scale" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="1"/>
        <Element index="2" value="1"/>
        <Domain name="range" id="5559.Scale.range"/>
      </Property>
      <Property name="ScaleByArray" id="5559.ScaleByArray" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5559.ScaleByArray.bool"/>
      </Property>
      <Property name="ScaleFactor" id="5559.ScaleFactor" number_of_elements="1">
        <Element index="0" value="0.0100000001490116"/>
        <Domain name="bounds" id="5559.ScaleFactor.bounds"/>
        <Domain name="scalar_range" id="5559.ScaleFactor.scalar_range"/>
        <Domain name="vector_range" id="5559.ScaleFactor.vector_range"/>
      </Property>
      <Property name="ScaleMode" id="5559.ScaleMode" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="enum" id="5559.ScaleMode.enum">
          <Entry value="0" text="No Data Scaling Off"/>
          <Entry value="1" text="Magnitude"/>
          <Entry value="2" text="Vector Components"/>
        </Domain>
      </Property>
      <Property name="ScaleTransferFunction" id="5559.ScaleTransferFunction" number_of_elements="1">
        <Proxy value="5499"/>
        <Domain name="groups" id="5559.ScaleTransferFunction.groups"/>
        <Domain name="proxy_list" id="5559.ScaleTransferFunction.proxy_list">
          <Proxy value="5499"/>
        </Domain>
      </Property>
      <Property name="Scaling" id="5559.Scaling" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5559.Scaling.bool"/>
      </Property>
      <Property name="SelectMapper" id="5559.SelectMapper" number_of_elements="1">
        <Element index="0" value="Projected tetra"/>
        <Domain name="list" id="5559.SelectMapper.list">
          <String text="Projected tetra"/>
          <String text="Z sweep"/>
          <String text="Bunyk ray cast"/>
        </Domain>
      </Property>
      <Property name="SelectMaskArray" id="5559.SelectMaskArray" number_of_elements="1">
        <Element index="0" value=""/>
      </Property>
      <Property name="SelectOrientationVectors" id="5559.SelectOrientationVectors" number_of_elements="1">
        <Element index="0" value=""/>
      </Property>
      <Property name="SelectScaleArray" id="5559.SelectScaleArray" number_of_elements="1">
        <Element index="0" value=""/>
      </Property>
      <Property name="SelectionCellLabelBold" id="5559.SelectionCellLabelBold" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5559.SelectionCellLabelBold.bool"/>
      </Property>
      <Property name="SelectionCellLabelColor" id="5559.SelectionCellLabelColor" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="1"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="5559.SelectionCellLabelColor.range"/>
      </Property>
      <Property name="SelectionCellLabelFontFamily" id="5559.SelectionCellLabelFontFamily" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="enum" id="5559.SelectionCellLabelFontFamily.enum">
          <Entry value="0" text="Arial"/>
          <Entry value="1" text="Courier"/>
          <Entry value="2" text="Times"/>
        </Domain>
      </Property>
      <Property name="SelectionCellLabelFontSize" id="5559.SelectionCellLabelFontSize" number_of_elements="1">
        <Element index="0" value="18"/>
        <Domain name="range" id="5559.SelectionCellLabelFontSize.range"/>
      </Property>
      <Property name="SelectionCellLabelFormat" id="5559.SelectionCellLabelFormat" number_of_elements="1">
        <Element index="0" value=""/>
      </Property>
      <Property name="SelectionCellLabelItalic" id="5559.SelectionCellLabelItalic" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5559.SelectionCellLabelItalic.bool"/>
      </Property>
      <Property name="SelectionCellLabelJustification" id="5559.SelectionCellLabelJustification" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="enum" id="5559.SelectionCellLabelJustification.enum">
          <Entry value="0" text="Left"/>
          <Entry value="1" text="Center"/>
          <Entry value="2" text="Right"/>
        </Domain>
      </Property>
      <Property name="SelectionCellLabelOpacity" id="5559.SelectionCellLabelOpacity" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="5559.SelectionCellLabelOpacity.range"/>
      </Property>
      <Property name="SelectionCellLabelShadow" id="5559.SelectionCellLabelShadow" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5559.SelectionCellLabelShadow.bool"/>
      </Property>
      <Property name="SelectionCellLabelVisibility" id="5559.SelectionCellLabelVisibility" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5559.SelectionCellLabelVisibility.bool"/>
      </Property>
      <Property name="SelectionColor" id="5559.SelectionColor" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="0"/>
        <Element index="2" value="1"/>
        <Domain name="range" id="5559.SelectionColor.range"/>
      </Property>
      <Property name="SelectionLineWidth" id="5559.SelectionLineWidth" number_of_elements="1">
        <Element index="0" value="2"/>
        <Domain name="range" id="5559.SelectionLineWidth.range"/>
      </Property>
      <Property name="SelectionOpacity" id="5559.SelectionOpacity" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="5559.SelectionOpacity.range"/>
      </Property>
      <Property name="SelectionPointLabelBold" id="5559.SelectionPointLabelBold" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5559.SelectionPointLabelBold.bool"/>
      </Property>
      <Property name="SelectionPointLabelColor" id="5559.SelectionPointLabelColor" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="1"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="5559.SelectionPointLabelColor.range"/>
      </Property>
      <Property name="SelectionPointLabelFontFamily" id="5559.SelectionPointLabelFontFamily" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="enum" id="5559.SelectionPointLabelFontFamily.enum">
          <Entry value="0" text="Arial"/>
          <Entry value="1" text="Courier"/>
          <Entry value="2" text="Times"/>
        </Domain>
      </Property>
      <Property name="SelectionPointLabelFontSize" id="5559.SelectionPointLabelFontSize" number_of_elements="1">
        <Element index="0" value="18"/>
        <Domain name="range" id="5559.SelectionPointLabelFontSize.range"/>
      </Property>
      <Property name="SelectionPointLabelFormat" id="5559.SelectionPointLabelFormat" number_of_elements="1">
        <Element index="0" value=""/>
      </Property>
      <Property name="SelectionPointLabelItalic" id="5559.SelectionPointLabelItalic" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5559.SelectionPointLabelItalic.bool"/>
      </Property>
      <Property name="SelectionPointLabelJustification" id="5559.SelectionPointLabelJustification" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="enum" id="5559.SelectionPointLabelJustification.enum">
          <Entry value="0" text="Left"/>
          <Entry value="1" text="Center"/>
          <Entry value="2" text="Right"/>
        </Domain>
      </Property>
      <Property name="SelectionPointLabelOpacity" id="5559.SelectionPointLabelOpacity" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="5559.SelectionPointLabelOpacity.range"/>
      </Property>
      <Property name="SelectionPointLabelShadow" id="5559.SelectionPointLabelShadow" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5559.SelectionPointLabelShadow.bool"/>
      </Property>
      <Property name="SelectionPointLabelVisibility" id="5559.SelectionPointLabelVisibility" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5559.SelectionPointLabelVisibility.bool"/>
      </Property>
      <Property name="SelectionPointSize" id="5559.SelectionPointSize" number_of_elements="1">
        <Element index="0" value="5"/>
        <Domain name="range" id="5559.SelectionPointSize.range"/>
      </Property>
      <Property name="SelectionRepresentation" id="5559.SelectionRepresentation" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="enum" id="5559.SelectionRepresentation.enum">
          <Entry value="0" text="Points"/>
          <Entry value="1" text="Wireframe"/>
          <Entry value="2" text="Surface"/>
        </Domain>
      </Property>
      <Property name="SelectionUseOutline" id="5559.SelectionUseOutline" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5559.SelectionUseOutline.bool"/>
      </Property>
      <Property name="SetScaleArray" id="5559.SetScaleArray" number_of_elements="5">
        <Element index="0" value=""/>
        <Element index="1" value=""/>
        <Element index="2" value=""/>
        <Element index="3" value=""/>
        <Element index="4" value=""/>
        <Domain name="array_list" id="5559.SetScaleArray.array_list"/>
      </Property>
      <Property name="ShaderPreset" id="5559.ShaderPreset" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="enum" id="5559.ShaderPreset.enum">
          <Entry value="0" text="Gaussian Blur (Default)"/>
          <Entry value="1" text="Sphere"/>
          <Entry value="2" text="Black-edged circle"/>
          <Entry value="3" text="Plain circle"/>
          <Entry value="4" text="Triangle"/>
          <Entry value="5" text="Square Outline"/>
        </Domain>
      </Property>
      <Property name="Specular" id="5559.Specular" number_of_elements="1">
        <Element index="0" value="0.1"/>
        <Domain name="range" id="5559.Specular.range"/>
      </Property>
      <Property name="SpecularColor" id="5559.SpecularColor" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="1"/>
        <Element index="2" value="1"/>
        <Domain name="range" id="5559.SpecularColor.range"/>
      </Property>
      <Property name="SpecularPower" id="5559.SpecularPower" number_of_elements="1">
        <Element index="0" value="100"/>
        <Domain name="range" id="5559.SpecularPower.range"/>
      </Property>
      <Property name="StaticMode" id="5559.StaticMode" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5559.StaticMode.bool"/>
      </Property>
      <Property name="StickyAxes" id="5559.StickyAxes" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5559.StickyAxes.bool"/>
      </Property>
      <Property name="SuppressLOD" id="5559.SuppressLOD" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5559.SuppressLOD.bool"/>
      </Property>
      <Property name="Texture" id="5559.Texture">
        <Domain name="groups" id="5559.Texture.groups"/>
      </Property>
      <Property name="Triangulate" id="5559.Triangulate" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5559.Triangulate.bool"/>
      </Property>
      <Property name="UseAxesOrigin" id="5559.UseAxesOrigin" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5559.UseAxesOrigin.bool"/>
      </Property>
      <Property name="UserTransform" id="5559.UserTransform" number_of_elements="16">
        <Element index="0" value="1"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Element index="3" value="0"/>
        <Element index="4" value="0"/>
        <Element index="5" value="1"/>
        <Element index="6" value="0"/>
        <Element index="7" value="0"/>
        <Element index="8" value="0"/>
        <Element index="9" value="0"/>
        <Element index="10" value="1"/>
        <Element index="11" value="0"/>
        <Element index="12" value="0"/>
        <Element index="13" value="0"/>
        <Element index="14" value="0"/>
        <Element index="15" value="1"/>
      </Property>
    </Proxy>
    <Proxy group="filters" type="AngularPeriodicFilter" id="5018" servers="1">
      <Property name="Axis" id="5018.Axis" number_of_elements="1">
        <Element index="0" value="2"/>
        <Domain name="enum" id="5018.Axis.enum">
          <Entry value="0" text="Axis X"/>
          <Entry value="1" text="Axis Y"/>
          <Entry value="2" text="Axis Z"/>
        </Domain>
      </Property>
      <Property name="BlockIndices" id="5018.BlockIndices">
        <Domain name="tree" id="5018.BlockIndices.tree"/>
      </Property>
      <Property name="Center" id="5018.Center" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="5018.Center.range"/>
      </Property>
      <Property name="Input" id="5018.Input" number_of_elements="1">
        <Proxy value="4744" output_port="0"/>
        <Domain name="groups" id="5018.Input.groups"/>
        <Domain name="input_type" id="5018.Input.input_type"/>
      </Property>
      <Property name="IterationMode" id="5018.IterationMode" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="enum" id="5018.IterationMode.enum">
          <Entry value="0" text="Manual"/>
          <Entry value="1" text="Maximum"/>
        </Domain>
      </Property>
      <Property name="NumberOfPeriods" id="5018.NumberOfPeriods" number_of_elements="1">
        <Element index="0" value="3"/>
      </Property>
      <Property name="RotationAngle" id="5018.RotationAngle" number_of_elements="1">
        <Element index="0" value="90"/>
      </Property>
      <Property name="RotationArrayName" id="5018.RotationArrayName" number_of_elements="1">
        <Element index="0" value="periodic angle"/>
      </Property>
      <Property name="RotationMode" id="5018.RotationMode" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="enum" id="5018.RotationMode.enum">
          <Entry value="0" text="Direct Angle"/>
          <Entry value="1" text="Array Value"/>
        </Domain>
      </Property>
    </Proxy>
    <Proxy group="filters" type="CellDataToPointData" id="5197" servers="1">
      <Property name="Input" id="5197.Input" number_of_elements="1">
        <Proxy value="5018" output_port="0"/>
        <Domain name="groups" id="5197.Input.groups"/>
        <Domain name="input_array" id="5197.Input.input_array"/>
        <Domain name="input_type" id="5197.Input.input_type"/>
      </Property>
      <Property name="PassCellData" id="5197.PassCellData" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5197.PassCellData.bool"/>
      </Property>
      <Property name="PieceInvariant" id="5197.PieceInvariant" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="5197.PieceInvariant.bool"/>
      </Property>
    </Proxy>
    <Proxy group="filters" type="MergeBlocks" id="5376" servers="1">
      <Property name="Input" id="5376.Input" number_of_elements="1">
        <Proxy value="5197" output_port="0"/>
        <Domain name="input_type" id="5376.Input.input_type"/>
      </Property>
      <Property name="MergePoints" id="5376.MergePoints" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="5376.MergePoints.bool"/>
      </Property>
    </Proxy>
    <Proxy group="sources" type="XMLPolyDataReader" id="4744" servers="1">
      <Property name="FileName" id="4744.FileName" number_of_elements="1">
        <Element index="0" value="./test.vtp"/>
        <Domain name="files" id="4744.FileName.files"/>
      </Property>
      <Property name="FileNameInfo" id="4744.FileNameInfo" number_of_elements="1">
        <Element index="0" value="./test.vtp"/>
      </Property>
      <Property name="TimestepValues" id="4744.TimestepValues"/>
      <Property name="CellArrayInfo" id="4744.CellArrayInfo" number_of_elements="2">
        <Element index="0" value="v"/>
        <Element index="1" value="1"/>
      </Property>
      <Property name="CellArrayStatus" id="4744.CellArrayStatus" number_of_elements="2">
        <Element index="0" value="v"/>
        <Element index="1" value="1"/>
        <Domain name="array_list" id="4744.CellArrayStatus.array_list">
          <String text="v"/>
        </Domain>
      </Property>
      <Property name="PointArrayInfo" id="4744.PointArrayInfo"/>
      <Property name="PointArrayStatus" id="4744.PointArrayStatus">
        <Domain name="array_list" id="4744.PointArrayStatus.array_list"/>
      </Property>
    </Proxy>
    <Proxy group="misc" type="TimeKeeper" id="259" servers="16">
      <Property name="SuppressedTimeSources" id="259.SuppressedTimeSources"/>
      <Property name="Time" id="259.Time" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="range" id="259.Time.range"/>
      </Property>
      <Property name="TimeLabel" id="259.TimeLabel" number_of_elements="1">
        <Element index="0" value="Time"/>
      </Property>
      <Property name="TimeRange" id="259.TimeRange" number_of_elements="2">
        <Element index="0" value="0"/>
        <Element index="1" value="1"/>
      </Property>
      <Property name="TimeSources" id="259.TimeSources" number_of_elements="4">
        <Proxy value="4744"/>
        <Proxy value="5018"/>
        <Proxy value="5197"/>
        <Proxy value="5376"/>
      </Property>
      <Property name="TimestepValues" id="259.TimestepValues"/>
      <Property name="Views" id="259.Views" number_of_elements="1">
        <Proxy value="4766"/>
      </Property>
    </Proxy>
    <Proxy group="views" type="RenderView" id="4766" servers="21">
      <Property name="AlphaBitPlanes" id="4766.AlphaBitPlanes" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="4766.AlphaBitPlanes.bool"/>
      </Property>
      <Property name="ArrayComponentToDraw" id="4766.ArrayComponentToDraw" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="range" id="4766.ArrayComponentToDraw.range"/>
      </Property>
      <Property name="ArrayNameToDraw" id="4766.ArrayNameToDraw" number_of_elements="1">
        <Element index="0" value=""/>
      </Property>
      <Property name="ArrayNumberToDraw" id="4766.ArrayNumberToDraw" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="range" id="4766.ArrayNumberToDraw.range"/>
      </Property>
      <Property name="AxesGrid" id="4766.AxesGrid" number_of_elements="1">
        <Proxy value="4764"/>
        <Domain name="proxy_list" id="4766.AxesGrid.proxy_list">
          <Proxy value="4764"/>
        </Domain>
      </Property>
      <Property name="BackLightAzimuth" id="4766.BackLightAzimuth" number_of_elements="1">
        <Element index="0" value="110"/>
        <Domain name="range" id="4766.BackLightAzimuth.range"/>
      </Property>
      <Property name="BackLightElevation" id="4766.BackLightElevation" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="range" id="4766.BackLightElevation.range"/>
      </Property>
      <Property name="BackLightK:B Ratio" id="4766.BackLightK:B Ratio" number_of_elements="1">
        <Element index="0" value="3.5"/>
        <Domain name="range" id="4766.BackLightK:B Ratio.range"/>
      </Property>
      <Property name="BackLightWarmth" id="4766.BackLightWarmth" number_of_elements="1">
        <Element index="0" value="0.5"/>
        <Domain name="range" id="4766.BackLightWarmth.range"/>
      </Property>
      <Property name="Background" id="4766.Background" number_of_elements="3">
        <Element index="0" value="0.32"/>
        <Element index="1" value="0.34"/>
        <Element index="2" value="0.43"/>
        <Domain name="range" id="4766.Background.range"/>
      </Property>
      <Property name="Background2" id="4766.Background2" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0.165"/>
        <Domain name="range" id="4766.Background2.range"/>
      </Property>
      <Property name="BackgroundTexture" id="4766.BackgroundTexture">
        <Domain name="groups" id="4766.BackgroundTexture.groups"/>
      </Property>
      <Property name="CacheKey" id="4766.CacheKey" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="range" id="4766.CacheKey.range"/>
      </Property>
      <Property name="Camera2DManipulators" id="4766.Camera2DManipulators" number_of_elements="9">
        <Element index="0" value="1"/>
        <Element index="1" value="3"/>
        <Element index="2" value="2"/>
        <Element index="3" value="2"/>
        <Element index="4" value="2"/>
        <Element index="5" value="2"/>
        <Element index="6" value="3"/>
        <Element index="7" value="1"/>
        <Element index="8" value="4"/>
        <Domain name="enum" id="4766.Camera2DManipulators.enum">
          <Entry value="0" text="None"/>
          <Entry value="1" text="Pan"/>
          <Entry value="2" text="Zoom"/>
          <Entry value="3" text="Roll"/>
          <Entry value="4" text="Rotate"/>
        </Domain>
      </Property>
      <Property name="Camera3DManipulators" id="4766.Camera3DManipulators" number_of_elements="9">
        <Element index="0" value="4"/>
        <Element index="1" value="1"/>
        <Element index="2" value="2"/>
        <Element index="3" value="3"/>
        <Element index="4" value="4"/>
        <Element index="5" value="1"/>
        <Element index="6" value="2"/>
        <Element index="7" value="4"/>
        <Element index="8" value="2"/>
        <Domain name="enum" id="4766.Camera3DManipulators.enum">
          <Entry value="0" text="None"/>
          <Entry value="1" text="Pan"/>
          <Entry value="2" text="Zoom"/>
          <Entry value="3" text="Roll"/>
          <Entry value="4" text="Rotate"/>
          <Entry value="5" text="Multi-Rotate"/>
        </Domain>
      </Property>
      <Property name="CameraParallelProjection" id="4766.CameraParallelProjection" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4766.CameraParallelProjection.bool"/>
      </Property>
      <Property name="CaptureZBuffer" id="4766.CaptureZBuffer"/>
      <Property name="CenterAxesVisibility" id="4766.CenterAxesVisibility" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4766.CenterAxesVisibility.bool"/>
      </Property>
      <Property name="CenterOfRotation" id="4766.CenterOfRotation" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0.5"/>
      </Property>
      <Property name="CollectGeometryThreshold" id="4766.CollectGeometryThreshold" number_of_elements="1">
        <Element index="0" value="100"/>
      </Property>
      <Property name="CompressorConfig" id="4766.CompressorConfig" number_of_elements="1">
        <Element index="0" value="vtkLZ4Compressor 0 3"/>
      </Property>
      <Property name="DepthPeeling" id="4766.DepthPeeling" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="4766.DepthPeeling.bool"/>
      </Property>
      <Property name="DrawCells" id="4766.DrawCells" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4766.DrawCells.bool"/>
      </Property>
      <Property name="EnableRenderOnInteraction" id="4766.EnableRenderOnInteraction" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="4766.EnableRenderOnInteraction.bool"/>
      </Property>
      <Property name="FillLightAzimuth" id="4766.FillLightAzimuth" number_of_elements="1">
        <Element index="0" value="-10"/>
        <Domain name="range" id="4766.FillLightAzimuth.range"/>
      </Property>
      <Property name="FillLightElevation" id="4766.FillLightElevation" number_of_elements="1">
        <Element index="0" value="-75"/>
        <Domain name="range" id="4766.FillLightElevation.range"/>
      </Property>
      <Property name="FillLightK:F Ratio" id="4766.FillLightK:F Ratio" number_of_elements="1">
        <Element index="0" value="3"/>
        <Domain name="range" id="4766.FillLightK:F Ratio.range"/>
      </Property>
      <Property name="FillLightWarmth" id="4766.FillLightWarmth" number_of_elements="1">
        <Element index="0" value="0.4"/>
        <Domain name="range" id="4766.FillLightWarmth.range"/>
      </Property>
      <Property name="HeadLightK:H Ratio" id="4766.HeadLightK:H Ratio" number_of_elements="1">
        <Element index="0" value="3"/>
        <Domain name="range" id="4766.HeadLightK:H Ratio.range"/>
      </Property>
      <Property name="HeadLightWarmth" id="4766.HeadLightWarmth" number_of_elements="1">
        <Element index="0" value="0.5"/>
        <Domain name="range" id="4766.HeadLightWarmth.range"/>
      </Property>
      <Property name="ImageReductionFactor" id="4766.ImageReductionFactor" number_of_elements="1">
        <Element index="0" value="2"/>
        <Domain name="range" id="4766.ImageReductionFactor.range"/>
      </Property>
      <Property name="InteractionMode" id="4766.InteractionMode" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="enum" id="4766.InteractionMode.enum">
          <Entry value="0" text="3D"/>
          <Entry value="1" text="2D"/>
          <Entry value="2" text="Selection"/>
        </Domain>
      </Property>
      <Property name="KeyLightAzimuth" id="4766.KeyLightAzimuth" number_of_elements="1">
        <Element index="0" value="10"/>
        <Domain name="range" id="4766.KeyLightAzimuth.range"/>
      </Property>
      <Property name="KeyLightElevation" id="4766.KeyLightElevation" number_of_elements="1">
        <Element index="0" value="50"/>
        <Domain name="range" id="4766.KeyLightElevation.range"/>
      </Property>
      <Property name="KeyLightIntensity" id="4766.KeyLightIntensity" number_of_elements="1">
        <Element index="0" value="0.75"/>
        <Domain name="range" id="4766.KeyLightIntensity.range"/>
      </Property>
      <Property name="KeyLightWarmth" id="4766.KeyLightWarmth" number_of_elements="1">
        <Element index="0" value="0.6"/>
        <Domain name="range" id="4766.KeyLightWarmth.range"/>
      </Property>
      <Property name="LODResolution" id="4766.LODResolution" number_of_elements="1">
        <Element index="0" value="0.5"/>
        <Domain name="range" id="4766.LODResolution.range"/>
      </Property>
      <Property name="LODThreshold" id="4766.LODThreshold" number_of_elements="1">
        <Element index="0" value="20"/>
        <Domain name="range" id="4766.LODThreshold.range"/>
      </Property>
      <Property name="LightAmbientColor" id="4766.LightAmbientColor" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="1"/>
        <Element index="2" value="1"/>
        <Domain name="range" id="4766.LightAmbientColor.range"/>
      </Property>
      <Property name="LightDiffuseColor" id="4766.LightDiffuseColor" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="1"/>
        <Element index="2" value="1"/>
        <Domain name="range" id="4766.LightDiffuseColor.range"/>
      </Property>
      <Property name="LightIntensity" id="4766.LightIntensity" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="4766.LightIntensity.range"/>
      </Property>
      <Property name="LightSpecularColor" id="4766.LightSpecularColor" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="1"/>
        <Element index="2" value="1"/>
        <Domain name="range" id="4766.LightSpecularColor.range"/>
      </Property>
      <Property name="LightSwitch" id="4766.LightSwitch" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4766.LightSwitch.bool"/>
      </Property>
      <Property name="LightType" id="4766.LightType" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="enum" id="4766.LightType.enum">
          <Entry value="1" text="HeadLight"/>
          <Entry value="2" text="CameraLight"/>
          <Entry value="3" text="SceneLight"/>
        </Domain>
      </Property>
      <Property name="LockBounds" id="4766.LockBounds" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4766.LockBounds.bool"/>
      </Property>
      <Property name="MaintainLuminance" id="4766.MaintainLuminance" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4766.MaintainLuminance.bool"/>
      </Property>
      <Property name="MaximumNumberOfPeels" id="4766.MaximumNumberOfPeels" number_of_elements="1">
        <Element index="0" value="4"/>
        <Domain name="range" id="4766.MaximumNumberOfPeels.range"/>
      </Property>
      <Property name="MultiSamples" id="4766.MultiSamples" number_of_elements="1">
        <Element index="0" value="0"/>
      </Property>
      <Property name="NonInteractiveRenderDelay" id="4766.NonInteractiveRenderDelay" number_of_elements="1">
        <Element index="0" value="0"/>
      </Property>
      <Property name="OrientationAxesInteractivity" id="4766.OrientationAxesInteractivity" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4766.OrientationAxesInteractivity.bool"/>
      </Property>
      <Property name="OrientationAxesLabelColor" id="4766.OrientationAxesLabelColor" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="1"/>
        <Element index="2" value="1"/>
      </Property>
      <Property name="OrientationAxesOutlineColor" id="4766.OrientationAxesOutlineColor" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="1"/>
        <Element index="2" value="1"/>
      </Property>
      <Property name="OrientationAxesVisibility" id="4766.OrientationAxesVisibility" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4766.OrientationAxesVisibility.bool"/>
      </Property>
      <Property name="RemoteRenderThreshold" id="4766.RemoteRenderThreshold" number_of_elements="1">
        <Element index="0" value="20"/>
        <Domain name="range" id="4766.RemoteRenderThreshold.range"/>
      </Property>
      <Property name="Representations" id="4766.Representations" number_of_elements="4">
        <Proxy value="5007"/>
        <Proxy value="5186"/>
        <Proxy value="5365"/>
        <Proxy value="5559"/>
      </Property>
      <Property name="RotationFactor" id="4766.RotationFactor" number_of_elements="1">
        <Element index="0" value="1"/>
      </Property>
      <Property name="ScalarRange" id="4766.ScalarRange" number_of_elements="2">
        <Element index="0" value="0"/>
        <Element index="1" value="-1"/>
        <Domain name="range" id="4766.ScalarRange.range"/>
      </Property>
      <Property name="ServerStereoType" id="4766.ServerStereoType" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="enum" id="4766.ServerStereoType.enum">
          <Entry value="0" text="Same As Client"/>
          <Entry value="1" text="Crystal Eyes"/>
          <Entry value="2" text="Red-Blue"/>
          <Entry value="3" text="Interlaced"/>
          <Entry value="4" text="Left"/>
          <Entry value="5" text="Right"/>
          <Entry value="6" text="Dresden"/>
          <Entry value="7" text="Anaglyph"/>
          <Entry value="8" text="Checkerboard"/>
          <Entry value="9" text="SplitViewportHorizontal"/>
          <Entry value="10" text="None"/>
        </Domain>
      </Property>
      <Property name="ShowAnnotation" id="4766.ShowAnnotation" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4766.ShowAnnotation.bool"/>
      </Property>
      <Property name="StartCaptureLuminance" id="4766.StartCaptureLuminance"/>
      <Property name="StartCaptureValues" id="4766.StartCaptureValues"/>
      <Property name="StencilCapable" id="4766.StencilCapable" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="4766.StencilCapable.bool"/>
      </Property>
      <Property name="StereoRender" id="4766.StereoRender" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4766.StereoRender.bool"/>
      </Property>
      <Property name="StereoType" id="4766.StereoType" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="enum" id="4766.StereoType.enum">
          <Entry value="1" text="Crystal Eyes"/>
          <Entry value="2" text="Red-Blue"/>
          <Entry value="3" text="Interlaced"/>
          <Entry value="4" text="Left"/>
          <Entry value="5" text="Right"/>
          <Entry value="6" text="Dresden"/>
          <Entry value="7" text="Anaglyph"/>
          <Entry value="8" text="Checkerboard"/>
          <Entry value="9" text="SplitViewportHorizontal"/>
          <Entry value="10" text="None"/>
        </Domain>
      </Property>
      <Property name="StillRenderImageReductionFactor" id="4766.StillRenderImageReductionFactor" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="4766.StillRenderImageReductionFactor.range"/>
      </Property>
      <Property name="StopCaptureLuminance" id="4766.StopCaptureLuminance"/>
      <Property name="StopCaptureValues" id="4766.StopCaptureValues"/>
      <Property name="UseCache" id="4766.UseCache" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4766.UseCache.bool"/>
      </Property>
      <Property name="UseGradientBackground" id="4766.UseGradientBackground" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="4766.UseGradientBackground.bool"/>
      </Property>
      <Property name="UseInteractiveRenderingForScreenshots" id="4766.UseInteractiveRenderingForScreenshots" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4766.UseInteractiveRenderingForScreenshots.bool"/>
      </Property>
      <Property name="UseLight" id="4766.UseLight" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="4766.UseLight.bool"/>
      </Property>
      <Property name="UseOffscreenRendering" id="4766.UseOffscreenRendering" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4766.UseOffscreenRendering.bool"/>
      </Property>
      <Property name="UseOffscreenRenderingForScreenshots" id="4766.UseOffscreenRenderingForScreenshots" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4766.UseOffscreenRenderingForScreenshots.bool"/>
      </Property>
      <Property name="UseOutlineForLODRendering" id="4766.UseOutlineForLODRendering" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4766.UseOutlineForLODRendering.bool"/>
      </Property>
      <Property name="UseTexturedBackground" id="4766.UseTexturedBackground" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4766.UseTexturedBackground.bool"/>
      </Property>
      <Property name="ViewSize" id="4766.ViewSize" number_of_elements="2">
        <Element index="0" value="1547"/>
        <Element index="1" value="939"/>
      </Property>
      <Property name="ViewTime" id="4766.ViewTime" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="range" id="4766.ViewTime.range"/>
      </Property>
      <Property name="CameraClippingRange" id="4766.CameraClippingRange" number_of_elements="2">
        <Element index="0" value="0.270473033979681"/>
        <Element index="1" value="0.27730316110038"/>
      </Property>
      <Property name="CameraClippingRangeInfo" id="4766.CameraClippingRangeInfo" number_of_elements="2">
        <Element index="0" value="0.270473033979681"/>
        <Element index="1" value="0.27730316110038"/>
      </Property>
      <Property name="CameraFocalPoint" id="4766.CameraFocalPoint" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0.5"/>
      </Property>
      <Property name="CameraFocalPointInfo" id="4766.CameraFocalPointInfo" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0.5"/>
      </Property>
      <Property name="CameraParallelScale" id="4766.CameraParallelScale" number_of_elements="1">
        <Element index="0" value="0.070710679172326"/>
      </Property>
      <Property name="CameraParallelScaleInfo" id="4766.CameraParallelScaleInfo" number_of_elements="1">
        <Element index="0" value="0.070710679172326"/>
      </Property>
      <Property name="CameraPosition" id="4766.CameraPosition" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0.773205084827961"/>
      </Property>
      <Property name="CameraPositionInfo" id="4766.CameraPositionInfo" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0.773205084827961"/>
      </Property>
      <Property name="CameraViewAngle" id="4766.CameraViewAngle" number_of_elements="1">
        <Element index="0" value="30"/>
      </Property>
      <Property name="CameraViewUp" id="4766.CameraViewUp" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="1"/>
        <Element index="2" value="0"/>
      </Property>
      <Property name="CameraViewUpInfo" id="4766.CameraViewUpInfo" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="1"/>
        <Element index="2" value="0"/>
      </Property>
      <Property name="EyeAngle" id="4766.EyeAngle" number_of_elements="1">
        <Element index="0" value="2"/>
        <Domain name="range" id="4766.EyeAngle.range"/>
      </Property>
    </Proxy>
    <ProxyCollection name="animation">
      <Item id="263" name="AnimationScene1"/>
      <Item id="265" name="TimeAnimationCue1"/>
    </ProxyCollection>
    <ProxyCollection name="layouts">
      <Item id="2863" name="ViewLayout1"/>
    </ProxyCollection>
    <ProxyCollection name="pq_helper_proxies.4744">
      <Item id="4756" name="RepresentationAnimationHelper"/>
    </ProxyCollection>
    <ProxyCollection name="pq_helper_proxies.4766">
      <Item id="4764" name="AxesGrid"/>
    </ProxyCollection>
    <ProxyCollection name="pq_helper_proxies.5007">
      <Item id="4862" name="GlyphType"/>
      <Item id="4873" name="GlyphType"/>
      <Item id="4884" name="GlyphType"/>
      <Item id="4895" name="GlyphType"/>
      <Item id="4906" name="GlyphType"/>
      <Item id="4917" name="GlyphType"/>
      <Item id="4928" name="GlyphType"/>
      <Item id="4961" name="OpacityTransferFunction"/>
      <Item id="4962" name="ScaleTransferFunction"/>
    </ProxyCollection>
    <ProxyCollection name="pq_helper_proxies.5018">
      <Item id="5029" name="RepresentationAnimationHelper"/>
    </ProxyCollection>
    <ProxyCollection name="pq_helper_proxies.5186">
      <Item id="5041" name="GlyphType"/>
      <Item id="5052" name="GlyphType"/>
      <Item id="5063" name="GlyphType"/>
      <Item id="5074" name="GlyphType"/>
      <Item id="5085" name="GlyphType"/>
      <Item id="5096" name="GlyphType"/>
      <Item id="5107" name="GlyphType"/>
      <Item id="5140" name="OpacityTransferFunction"/>
      <Item id="5141" name="ScaleTransferFunction"/>
    </ProxyCollection>
    <ProxyCollection name="pq_helper_proxies.5197">
      <Item id="5208" name="RepresentationAnimationHelper"/>
    </ProxyCollection>
    <ProxyCollection name="pq_helper_proxies.5365">
      <Item id="5220" name="GlyphType"/>
      <Item id="5231" name="GlyphType"/>
      <Item id="5242" name="GlyphType"/>
      <Item id="5253" name="GlyphType"/>
      <Item id="5264" name="GlyphType"/>
      <Item id="5275" name="GlyphType"/>
      <Item id="5286" name="GlyphType"/>
      <Item id="5319" name="OpacityTransferFunction"/>
      <Item id="5320" name="ScaleTransferFunction"/>
    </ProxyCollection>
    <ProxyCollection name="pq_helper_proxies.5376">
      <Item id="5387" name="RepresentationAnimationHelper"/>
    </ProxyCollection>
    <ProxyCollection name="pq_helper_proxies.5559">
      <Item id="5399" name="GlyphType"/>
      <Item id="5410" name="GlyphType"/>
      <Item id="5421" name="GlyphType"/>
      <Item id="5432" name="GlyphType"/>
      <Item id="5443" name="GlyphType"/>
      <Item id="5454" name="GlyphType"/>
      <Item id="5465" name="GlyphType"/>
      <Item id="5498" name="OpacityTransferFunction"/>
      <Item id="5499" name="ScaleTransferFunction"/>
    </ProxyCollection>
    <ProxyCollection name="representations">
      <Item id="5007" name="GeometryRepresentation1"/>
      <Item id="5186" name="GeometryRepresentation2"/>
      <Item id="5365" name="GeometryRepresentation3"/>
      <Item id="5559" name="UnstructuredGridRepresentation1"/>
    </ProxyCollection>
    <ProxyCollection name="sources">
      <Item id="5018" name="AngularPeriodicFilter1"/>
      <Item id="5197" name="CellDatatoPointData1"/>
      <Item id="5376" name="MergeBlocks1"/>
      <Item id="4744" name="test.vtp"/>
    </ProxyCollection>
    <ProxyCollection name="timekeeper">
      <Item id="259" name="TimeKeeper1"/>
    </ProxyCollection>
    <ProxyCollection name="views">
      <Item id="4766" name="RenderView1"/>
    </ProxyCollection>
    <CustomProxyDefinitions>
      <CustomProxyDefinition name="Contour sub range" group="filters">
        <CompoundSourceProxy id="3086" servers="1">
          <Proxy group="filters" type="IsoVolume" id="2718" servers="1" compound_name="IsoVolume2">
            <Property name="Input" id="2718.Input" number_of_elements="1">
              <Domain name="groups" id="2718.Input.groups"/>
              <Domain name="input_array" id="2718.Input.input_array">
                <InputArray attribute_type="any" number_of_components="1"/>
              </Domain>
              <Domain name="input_type" id="2718.Input.input_type"/>
            </Property>
            <Property name="SelectInputScalars" id="2718.SelectInputScalars" number_of_elements="5">
              <Element index="0" value=""/>
              <Element index="1" value=""/>
              <Element index="2" value=""/>
              <Element index="3" value="0"/>
              <Element index="4" value="Result"/>
              <Domain name="array_list" id="2718.SelectInputScalars.array_list">
                <String text="Result"/>
              </Domain>
              <Domain name="field_list" id="2718.SelectInputScalars.field_list">
                <Entry value="0" text="Point Data"/>
              </Domain>
            </Property>
            <Property name="ThresholdBetween" id="2718.ThresholdBetween" number_of_elements="2">
              <Element index="0" value="7280"/>
              <Element index="1" value="7350"/>
              <Domain name="range" id="2718.ThresholdBetween.range"/>
            </Property>
          </Proxy>
          <Proxy group="filters" type="IsoVolume" id="2823" servers="1" compound_name="IsoVolume3">
            <Property name="Input" id="2823.Input" number_of_elements="1">
              <Domain name="groups" id="2823.Input.groups"/>
              <Domain name="input_array" id="2823.Input.input_array">
                <InputArray attribute_type="any" number_of_components="1"/>
              </Domain>
              <Domain name="input_type" id="2823.Input.input_type"/>
            </Property>
            <Property name="SelectInputScalars" id="2823.SelectInputScalars" number_of_elements="5">
              <Element index="0" value=""/>
              <Element index="1" value=""/>
              <Element index="2" value=""/>
              <Element index="3" value="0"/>
              <Element index="4" value="Result"/>
              <Domain name="array_list" id="2823.SelectInputScalars.array_list">
                <String text="Result"/>
              </Domain>
              <Domain name="field_list" id="2823.SelectInputScalars.field_list">
                <Entry value="0" text="Point Data"/>
              </Domain>
            </Property>
            <Property name="ThresholdBetween" id="2823.ThresholdBetween" number_of_elements="2">
              <Element index="0" value="7350"/>
              <Element index="1" value="284652"/>
              <Domain name="range" id="2823.ThresholdBetween.range"/>
            </Property>
          </Proxy>
          <Proxy group="filters" type="IsoVolume" id="2940" servers="1" compound_name="IsoVolume5">
            <Property name="Input" id="2940.Input" number_of_elements="1">
              <Domain name="groups" id="2940.Input.groups"/>
              <Domain name="input_array" id="2940.Input.input_array">
                <InputArray attribute_type="any" number_of_components="1"/>
              </Domain>
              <Domain name="input_type" id="2940.Input.input_type"/>
            </Property>
            <Property name="SelectInputScalars" id="2940.SelectInputScalars" number_of_elements="5">
              <Element index="0" value=""/>
              <Element index="1" value=""/>
              <Element index="2" value=""/>
              <Element index="3" value="0"/>
              <Element index="4" value="Result"/>
              <Domain name="array_list" id="2940.SelectInputScalars.array_list">
                <String text="Result"/>
              </Domain>
              <Domain name="field_list" id="2940.SelectInputScalars.field_list">
                <Entry value="0" text="Point Data"/>
              </Domain>
            </Property>
            <Property name="ThresholdBetween" id="2940.ThresholdBetween" number_of_elements="2">
              <Element index="0" value="53.0015983581543"/>
              <Element index="1" value="7280"/>
              <Domain name="range" id="2940.ThresholdBetween.range"/>
            </Property>
          </Proxy>
          <ExposedProperties>
            <Property name="ThresholdBetween" proxy_name="IsoVolume5" exposed_name="Threshold Range"/>
            <Property name="Input" proxy_name="IsoVolume2" exposed_name="lower"/>
            <Property name="Input" proxy_name="IsoVolume5" exposed_name="lower value"/>
            <Property name="Input" proxy_name="IsoVolume3" exposed_name="upper"/>
          </ExposedProperties>
          <OutputPort name="aedf" proxy="IsoVolume5" port_index="0"/>
          <Hints>
            <ShowInMenu/>
          </Hints>
        </CompoundSourceProxy>
      </CustomProxyDefinition>
      <CustomProxyDefinition name="poo" group="filters">
        <CompoundSourceProxy id="5033" servers="1">
          <Proxy group="filters" type="Cut" id="135" servers="1" compound_name="Slice1">
            <Property name="ContourValues" id="135.ContourValues" number_of_elements="1">
              <Element index="0" value="0"/>
              <Domain name="bounds" id="135.ContourValues.bounds">
                <Min index="0" value="-0.416506"/>
                <Max index="0" value="0.416506"/>
              </Domain>
            </Property>
            <Property name="CutFunction" id="135.CutFunction" number_of_elements="1">
              <Proxy value="129"/>
              <Domain name="groups" id="135.CutFunction.groups">
                <Group value="implicit_functions"/>
              </Domain>
              <Domain name="proxy_list" id="135.CutFunction.proxy_list">
                <Proxy value="129"/>
                <Proxy value="131"/>
                <Proxy value="133"/>
              </Domain>
            </Property>
            <Property name="Input" id="135.Input" number_of_elements="1">
              <Domain name="groups" id="135.Input.groups">
                <Group value="sources"/>
                <Group value="filters"/>
              </Domain>
              <Domain name="input_type" id="135.Input.input_type">
                <DataType value="vtkDataSet"/>
              </Domain>
            </Property>
            <Property name="InputBounds" id="135.InputBounds">
              <Domain name="bounds" id="135.InputBounds.bounds">
                <Min index="0" value="-0.244"/>
                <Min index="1" value="-0.244"/>
                <Min index="2" value="-0.23325"/>
                <Max index="0" value="0.244"/>
                <Max index="1" value="0.244"/>
                <Max index="2" value="0.23325"/>
              </Domain>
            </Property>
          </Proxy>
          <Proxy group="implicit_functions" type="Plane" id="129" servers="1" compound_name="auto_129">
            <Property name="Normal" id="129.Normal" number_of_elements="3">
              <Element index="0" value="1"/>
              <Element index="1" value="0"/>
              <Element index="2" value="0"/>
              <Domain name="range" id="129.Normal.range"/>
            </Property>
            <Property name="Offset" id="129.Offset" number_of_elements="1">
              <Element index="0" value="0"/>
              <Domain name="range" id="129.Offset.range"/>
            </Property>
            <Property name="Origin" id="129.Origin" number_of_elements="3">
              <Element index="0" value="0"/>
              <Element index="1" value="0"/>
              <Element index="2" value="0"/>
              <Domain name="range" id="129.Origin.range"/>
            </Property>
          </Proxy>
          <ExposedProperties>
            <Property name="Input" proxy_name="Slice1" exposed_name="Input"/>
          </ExposedProperties>
          <OutputPort name="Output" proxy="Slice1" port_index="0"/>
          <Hints>
            <ShowInMenu/>
          </Hints>
        </CompoundSourceProxy>
      </CustomProxyDefinition>
    </CustomProxyDefinitions>
    <Links>
      <GlobalPropertyLink global_name="BackgroundColor" proxy="4766" property="Background"/>
      <GlobalPropertyLink global_name="EdgeColor" proxy="5007" property="EdgeColor"/>
      <GlobalPropertyLink global_name="EdgeColor" proxy="5186" property="EdgeColor"/>
      <GlobalPropertyLink global_name="EdgeColor" proxy="5365" property="EdgeColor"/>
      <GlobalPropertyLink global_name="EdgeColor" proxy="5559" property="EdgeColor"/>
      <GlobalPropertyLink global_name="ForegroundColor" proxy="4764" property="GridColor"/>
      <GlobalPropertyLink global_name="ForegroundColor" proxy="4766" property="OrientationAxesOutlineColor"/>
      <GlobalPropertyLink global_name="ForegroundColor" proxy="5007" property="AmbientColor"/>
      <GlobalPropertyLink global_name="ForegroundColor" proxy="5007" property="Color"/>
      <GlobalPropertyLink global_name="ForegroundColor" proxy="5007" property="CubeAxesColor"/>
      <GlobalPropertyLink global_name="ForegroundColor" proxy="5186" property="AmbientColor"/>
      <GlobalPropertyLink global_name="ForegroundColor" proxy="5186" property="Color"/>
      <GlobalPropertyLink global_name="ForegroundColor" proxy="5186" property="CubeAxesColor"/>
      <GlobalPropertyLink global_name="ForegroundColor" proxy="5365" property="AmbientColor"/>
      <GlobalPropertyLink global_name="ForegroundColor" proxy="5365" property="Color"/>
      <GlobalPropertyLink global_name="ForegroundColor" proxy="5365" property="CubeAxesColor"/>
      <GlobalPropertyLink global_name="ForegroundColor" proxy="5559" property="AmbientColor"/>
      <GlobalPropertyLink global_name="ForegroundColor" proxy="5559" property="Color"/>
      <GlobalPropertyLink global_name="ForegroundColor" proxy="5559" property="CubeAxesColor"/>
      <GlobalPropertyLink global_name="SelectionColor" proxy="5007" property="SelectionColor"/>
      <GlobalPropertyLink global_name="SelectionColor" proxy="5186" property="SelectionColor"/>
      <GlobalPropertyLink global_name="SelectionColor" proxy="5365" property="SelectionColor"/>
      <GlobalPropertyLink global_name="SelectionColor" proxy="5559" property="SelectionColor"/>
      <GlobalPropertyLink global_name="SurfaceColor" proxy="5007" property="BackfaceDiffuseColor"/>
      <GlobalPropertyLink global_name="SurfaceColor" proxy="5007" property="DiffuseColor"/>
      <GlobalPropertyLink global_name="SurfaceColor" proxy="5186" property="BackfaceDiffuseColor"/>
      <GlobalPropertyLink global_name="SurfaceColor" proxy="5186" property="DiffuseColor"/>
      <GlobalPropertyLink global_name="SurfaceColor" proxy="5365" property="BackfaceDiffuseColor"/>
      <GlobalPropertyLink global_name="SurfaceColor" proxy="5365" property="DiffuseColor"/>
      <GlobalPropertyLink global_name="SurfaceColor" proxy="5559" property="BackfaceDiffuseColor"/>
      <GlobalPropertyLink global_name="SurfaceColor" proxy="5559" property="DiffuseColor"/>
      <GlobalPropertyLink global_name="TextAnnotationColor" proxy="4764" property="XLabelColor"/>
      <GlobalPropertyLink global_name="TextAnnotationColor" proxy="4764" property="XTitleColor"/>
      <GlobalPropertyLink global_name="TextAnnotationColor" proxy="4764" property="YLabelColor"/>
      <GlobalPropertyLink global_name="TextAnnotationColor" proxy="4764" property="YTitleColor"/>
      <GlobalPropertyLink global_name="TextAnnotationColor" proxy="4764" property="ZLabelColor"/>
      <GlobalPropertyLink global_name="TextAnnotationColor" proxy="4764" property="ZTitleColor"/>
      <GlobalPropertyLink global_name="TextAnnotationColor" proxy="4766" property="OrientationAxesLabelColor"/>
    </Links>
  </ServerManagerState>
</ParaView>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: test.vtp
Type: application/octet-stream
Size: 114534 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160430/3dbb8172/attachment-0001.obj>

From mathieu.westphal at kitware.com  Sat Apr 30 06:04:15 2016
From: mathieu.westphal at kitware.com (Mathieu Westphal)
Date: Sat, 30 Apr 2016 12:04:15 +0200
Subject: [Paraview] pv freezes when merging blocks of angular periodic
 filter data
In-Reply-To: <572474D8.9040807@mail.ru>
References: <57246F48.5020109@mail.ru>
	<572474D8.9040807@mail.ru>
Message-ID: <CAC2t4UTaxiDtKPR66-JOdf1tDroV9-4cOJp2EuqKr6BL=xh_qw@mail.gmail.com>

I will take a look at it next week.

Regards,

Mathieu Westphal

On Sat, Apr 30, 2016 at 11:03 AM, Gena Bug <archaerolog at mail.ru> wrote:

> UPD: Seems it somehow related to cell-data vector arrays, because it works
> with point-data arrays.
>
> I attached a smallest example I came up with that could help. If you load
> the state-file you'll see the next pipeline:
> test.vtp
> AngularPeriodicFilter (with angle = 90 and axiz = Z)
> CellDatatoPointData
> MergeBlocks
>
> That works. However if you remove CellDatatoPointData from this pipeline
> and try to merge the result of AngularPeriodicFilter you'll see the problem.
>
>
> On 30.04.2016 11:39, Gena Bug wrote:
>
>> Hi!
>>
>> I was able to freeze Paraview by applying MergeBlocks filter to the data
>> generated by AngularPeriodicFilter. In console I see a bunch of warnings:
>> {
>> Warning: In
>>
>> /home/kitware/dashboards/buildbot/paraview-debian6dash-linux-shared-release_opengl2_qt4_superbuild/build/paraview/src/paraview/VTK/Common/Core/vtkMappedDataArray.txx,
>> line 47
>> 20vtkPeriodicDataArrayIdE (0x6dce310): GetVoidPointer called. This is
>> very expensive for vtkMappedDataArray subclasses, since the scalar array
>> must be generated for each call. Consider using a
>> vtkTypedDataArrayIterator instead.
>> }
>>
>> Env: debian testing amd64, KF5, pv downloaded from the site.
>> _______________________________________________
>> Powered by www.kitware.com
>>
>> Visit other Kitware open-source projects at
>> http://www.kitware.com/opensource/opensource.html
>>
>> Please keep messages on-topic and check the ParaView Wiki at:
>> http://paraview.org/Wiki/ParaView
>>
>> Search the list archives at: http://markmail.org/search/?q=ParaView
>>
>> Follow this link to subscribe/unsubscribe:
>> http://public.kitware.com/mailman/listinfo/paraview
>>
>>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160430/122f7b1d/attachment.html>

From utkarsh.ayachit at kitware.com  Sat Apr 30 12:47:38 2016
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Sat, 30 Apr 2016 09:47:38 -0700
Subject: [Paraview] Trace recorder, save screenshot and background.
In-Reply-To: <24658c7133d74f29b31d47830b466979@ES01AMSNLNT.srn.sandia.gov>
References: <24658c7133d74f29b31d47830b466979@ES01AMSNLNT.srn.sandia.gov>
Message-ID: <CADHSJjBhpbDiMm03ory6dRcQEvzYLxuOAuHKkUKBWMDu-4sqOA@mail.gmail.com>

Not presently, I am afraid. I am working on refactoring save
screenshot/save animation diaglogs that will add support for a richer
Python API for the same, enabling trace to record it as well.

Utkarsh

On Fri, Apr 29, 2016 at 5:28 PM, Scott, W Alan <wascott at sandia.gov> wrote:
>
>
> When I create a script that exports a screenshot.  The trace option does not
> capture the commands that make the background white and the vtkblock
> magnitude colors key turned off.  Is there a work around for this?
>
>
>
> Thanks,
>
>
>
> Alan
>
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview
>

From kevin.dean at decisionsciencescorp.com  Sat Apr 30 20:01:39 2016
From: kevin.dean at decisionsciencescorp.com (Dean, Kevin)
Date: Sat, 30 Apr 2016 17:01:39 -0700
Subject: [Paraview] ParaView Plugin Idea
Message-ID: <CAFvyM3QeixQW7LcKAXmXhE0xxR0n8ENChF7Nvq0Rdwc9F93Nhg@mail.gmail.com>

Hey guys,

I am trying to write a paraview filter that utilizes "Extract Subset."
However, I want to base it off of a slider methodology as opposed to typing
in the extents. Are there any examples that could get me started on
manipulating the render view based off sliders?

This is the end goal of what I would like. Something similar at least (for
xmin, xmax, ymin, ymax, zmin, zmax)

Any help would be appreciated! Cheers!

Kevin Dean

-- 
This email and its contents are confidential. If you are not the intended 
recipient, please do not disclose or use the information within this email 
or its attachments. If you have received this email in error, please report 
the error to the sender by return email and delete this communication from 
your records.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160430/16d06325/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: NewPlugin.png
Type: image/png
Size: 47906 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160430/16d06325/attachment.png>

From vaibhav.agrawal at postgrad.curtin.edu.au  Sun Apr  3 12:25:48 2016
From: vaibhav.agrawal at postgrad.curtin.edu.au (Vaibhav Agrawal)
Date: Sun, 03 Apr 2016 16:25:48 -0000
Subject: [Paraview] Regarding filtering of point data array
Message-ID: <HK2PR01MB13610380B1057F4F77DBC6FA899C0@HK2PR01MB1361.apcprd01.prod.exchangelabs.com>

Hi Paraview-Help,
I am working on the DEM simulations of bubbling fluidized bed using MFIX-DEM software.
The output files of my simulations are of two type - one containing the cell data such gas - volume fraction, pressure etc and other file containing the point data such as particle positions and particle velocity. I want to filter my point data file, on the basis of positions, i.e., I want to create a subset of all the particles available at that time step, whose positions (X,Y,Z) lies within a certain range ([Xmin, Xmax], [Ymin, Ymax], [Zmin, Zmax]). For e.g. let's suppose I have an point data array of size 20X7, where my 2nd,3rd and 4th columns contains the X, Y, X position of particles. I want to filter this point data array on the basis of particle position (X,Y,Z) such that my new point data array will be smaller in dimension (let's say 6X7), and will have only those points, whose 2nd, 3rd, 4th column contains the values which lies in the user defined range. I hope I am able to define my problem clearly.

I have tried using some filters like clip, slice etc, but didn't worked out well.
Is there any way - filters/python script to do this? If yes, how should I proceed to sort out my problem?
For your reference, I am attaching here a raw file generated by MFIX-DEM, which has a point data array, which I want to filter. Because of point data array, you won't see anything In the render view, but you'll see the point data array in Spreadsheet view

Thanks and Regards
Vaibhav Agrawal
PhD | Department of Chemical Engineering
Faculty of Science and Engineering

Curtin University
Mobile | +61451818978
Email | Vaibhav.Agrawal at postgrad.curtin.edu.au<mailto:Vaibhav.Agrawal at postgrad.curtin.edu.au>
Web | http://curtin.edu.au<http://curtin.edu.au/>

[Description: email_logo.png]

Curtin University is a trademark of Curtin University of Technology.
CRICOS Provider Code 00301J (WA), 02637B (NSW)

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160403/abad5829/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 2097 bytes
Desc: image001.png
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160403/abad5829/attachment-0001.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: RES_DT_0.01_DES_00020.vtp
Type: application/octet-stream
Size: 2268710 bytes
Desc: RES_DT_0.01_DES_00020.vtp
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160403/abad5829/attachment-0001.obj>