From keinepostnurmuell at gmail.com  Wed Jun  1 07:08:06 2016
From: keinepostnurmuell at gmail.com (no name)
Date: Wed, 1 Jun 2016 13:08:06 +0200
Subject: [Paraview] Calculater Bug or am I just with stupid?
Message-ID: <CAKrZ8yezLZx1X0q1OyyqHNGrUUcSNn=vui2A2pwE3=FGkHmVFQ@mail.gmail.com>

Hello

I have a problem I cannot figure out:

1 -> read in VTR file (Rectiliniear Grid)
2 -> apply "cell data to point data" filter
3 -> apply "calculator" on it, that selects only the Z component. Call
it "M_Z" (result array name).
4 -> apply "gradientofunstructureddataset" on the calc. with Scalar
Array set to "M_Z".

Works perfectly in the GUI.

Now I code it in a macro and I do it like that (after the celldatatopointdata):

# create a new 'Calculator'
Mz = Calculator(Input=cellDatatoPointData1)
Mz.ResultArrayName = 'M_Z'
Mz.Function = 'M_Z'
RenameSource('Mz', Mz)



# create a new 'Gradient Of Unstructured DataSet'
grad_Mz = GradientOfUnstructuredDataSet(Input=Mz)
grad_Mz.ScalarArray = ['POINTS', 'M_Z']
grad_Mz.ResultArrayName = 'grad_Mz'
RenameSource('grad_Mz', grad_Mz)

No matter what I do, I always get the wrong Scalar Array selected in
the GUI when I start the macro. When I then correct it in the GUI ->
works.

Any ideas?

Thanks
Richard

From richard.c.angelini.civ at mail.mil  Wed Jun  1 07:57:32 2016
From: richard.c.angelini.civ at mail.mil (Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US))
Date: Wed, 1 Jun 2016 11:57:32 +0000
Subject: [Paraview] [Non-DoD Source] Re: ParaView 5.0.1 on an older Mac
In-Reply-To: <574DF4B8.1080203@bluequartz.net>
References: <D373674D.2B87C%Richard.C.Angelini.CIV@mail.mil>
 <574DF4B8.1080203@bluequartz.net>
Message-ID: <D37445A8.2B887%Richard.C.Angelini.CIV@mail.mil>

This system is still running 10.9 and is scheduled for a 10.11 upgrade in the near-term ? presumably the warning message will go away with 10.11 ??.
________________________________
Rick Angelini
USArmy Research Laboratory
CISD/HPC Architectures Team
Phone:  410-278-6266

From: Michael Jackson <mike.jackson at bluequartz.net<mailto:mike.jackson at bluequartz.net>>
Date: Tuesday, May 31, 2016 at 4:31 PM
To: Rick Angelini <Richard.C.Angelini.CIV at mail.mil<mailto:Richard.C.Angelini.CIV at mail.mil>>
Cc: ParaView <paraview at paraview.org<mailto:paraview at paraview.org>>
Subject: [Non-DoD Source] Re: [Paraview] ParaView 5.0.1 on an older Mac

All active links contained in this email were disabled. Please verify the identity of the sender, and confirm the authenticity of all links contained within the message prior to copying and pasting the address to a Web browser.

________________________________


Richard,
   You will get this warning/error message on any OS X machine using ATI/AMD graphics hardware running OS X 10.10 or earlier. OS X 10.11 corrected an OpenGL driver issue that this error is reporting. It is down in the VTK stack. I do not know if we should be worried or not about the warning/error.

--
Mike Jackson  [mike.jackson at bluequartz.net<mailto:mike.jackson at bluequartz.net> < Caution-mailto:mike.jackson at bluequartz.net > ]
Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US) < Caution-mailto:richard.c.angelini.civ at mail.mil >
May 31, 2016 at 4:07 PM
I have the following message from one of my local ParaView users:

Following is the message I am getting with the Paraview 5 client on the Mac. It appears to work in spite of this warning.

Warning: In /Users/kitware/buildbot-slave/paraview-bigmac-osx-shared-release_opengl2_osx10_7_qt4_superbuild/build/paraview/src/paraview/VTK/Rendering/OpenGL2/vtkOpenGLPolyDataMapper.cxx, line 2856
vtkCompositeMapperHelper (0x7fbc4b0e7800): VTK is working around a bug in Apple-AMD hardware related to gl_PrimitiveID.  This may cause significant memory and performance impacts. Your hardware has been identified as vendor ATI Technologies Inc. with renderer of ATI Radeon HD 5770 OpenGL Engine and version 4.1 ATI-1.24.39

About this Mac has the following information about my system:
Graphics  ATI Radeon HD 5770 1024 MB


The user does not see this error running ParaView 4.x.x ? so ? presumably this warning message is related to OpenGL2 running on an older graphics card???    Is this something we should be worried about in the short-term?  I?m not sure how much longer this older Mac will be in service ? but will we run in to issues with OpenGL2 which will preclude it from working on these older systems?




________________________________
Rick Angelini
USArmy Research Laboratory
CISD/HPC Architectures Team
Phone:  410-278-6266
_______________________________________________
Powered by Caution-www.kitware.com < Caution-http://www.kitware.com >

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

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

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

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

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

From cory.quammen at kitware.com  Wed Jun  1 09:46:49 2016
From: cory.quammen at kitware.com (Cory Quammen)
Date: Wed, 1 Jun 2016 15:46:49 +0200
Subject: [Paraview] [Non-DoD Source] Re: ParaView 5.0.1 on an older Mac
In-Reply-To: <D37445A8.2B887%Richard.C.Angelini.CIV@mail.mil>
References: <D373674D.2B87C%Richard.C.Angelini.CIV@mail.mil>
 <574DF4B8.1080203@bluequartz.net>
 <D37445A8.2B887%Richard.C.Angelini.CIV@mail.mil>
Message-ID: <CAB5Fpx5Nu6e15NY4mNhOYOVNdV57_f8SQsCuUsd_wGXa5v+EmA@mail.gmail.com>

On Wed, Jun 1, 2016 at 1:57 PM, Angelini, Richard C (Rick) CIV USARMY
RDECOM ARL (US) <richard.c.angelini.civ at mail.mil> wrote:
> This system is still running 10.9 and is scheduled for a 10.11 upgrade in
> the near-term ? presumably the warning message will go away with 10.11 ??.

Not unless the upgrade includes a driver upgrade for the graphics
hardware to one of the white-listed graphics drivers. I know this
because my Mac with 10.11 complained, but it didn't exhibit the buggy
behavior, so I added it's hardware to the white list.

Ken, could we test for the Apple bug dynamically in VTK or in ParaView
in any easy way?

Thanks,
Cory


> ________________________________
> Rick Angelini
> USArmy Research Laboratory
> CISD/HPC Architectures Team
> Phone:  410-278-6266
>
> From: Michael Jackson <mike.jackson at bluequartz.net>
> Date: Tuesday, May 31, 2016 at 4:31 PM
> To: Rick Angelini <Richard.C.Angelini.CIV at mail.mil>
> Cc: ParaView <paraview at paraview.org>
> Subject: [Non-DoD Source] Re: [Paraview] ParaView 5.0.1 on an older Mac
>
> All active links contained in this email were disabled. Please verify the
> identity of the sender, and confirm the authenticity of all links contained
> within the message prior to copying and pasting the address to a Web
> browser.
>
> ________________________________
>
>
> Richard,
>    You will get this warning/error message on any OS X machine using ATI/AMD
> graphics hardware running OS X 10.10 or earlier. OS X 10.11 corrected an
> OpenGL driver issue that this error is reporting. It is down in the VTK
> stack. I do not know if we should be worried or not about the warning/error.
>
> --
> Mike Jackson  [mike.jackson at bluequartz.net <
> Caution-mailto:mike.jackson at bluequartz.net > ]
>
> Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US) <
> Caution-mailto:richard.c.angelini.civ at mail.mil >
> May 31, 2016 at 4:07 PM
> I have the following message from one of my local ParaView users:
>
> Following is the message I am getting with the Paraview 5 client on the Mac.
> It appears to work in spite of this warning.
>
> Warning: In
> /Users/kitware/buildbot-slave/paraview-bigmac-osx-shared-release_opengl2_osx10_7_qt4_superbuild/build/paraview/src/paraview/VTK/Rendering/OpenGL2/vtkOpenGLPolyDataMapper.cxx,
> line 2856
> vtkCompositeMapperHelper (0x7fbc4b0e7800): VTK is working around a bug in
> Apple-AMD hardware related to gl_PrimitiveID.  This may cause significant
> memory and performance impacts. Your hardware has been identified as vendor
> ATI Technologies Inc. with renderer of ATI Radeon HD 5770 OpenGL Engine and
> version 4.1 ATI-1.24.39
>
> About this Mac has the following information about my system:
> Graphics  ATI Radeon HD 5770 1024 MB
>
>
> The user does not see this error running ParaView 4.x.x ? so ? presumably
> this warning message is related to OpenGL2 running on an older graphics
> card???    Is this something we should be worried about in the short-term?
> I?m not sure how much longer this older Mac will be in service ? but will we
> run in to issues with OpenGL2 which will preclude it from working on these
> older systems?
>
>
>
>
> ________________________________
> Rick Angelini
> USArmy Research Laboratory
> CISD/HPC Architectures Team
> Phone:  410-278-6266
> _______________________________________________
> Powered by Caution-www.kitware.com < Caution-http://www.kitware.com >
>
> Visit other Kitware open-source projects at
> Caution-http://www.kitware.com/opensource/opensource.html <
> Caution-http://www.kitware.com/opensource/opensource.html >
>
> Please keep messages on-topic and check the ParaView Wiki at:
> Caution-http://paraview.org/Wiki/ParaView <
> Caution-http://paraview.org/Wiki/ParaView >
>
> Search the list archives at: Caution-http://markmail.org/search/?q=ParaView
> < Caution-http://markmail.org/search/?q=ParaView >
>
> Follow this link to subscribe/unsubscribe:
> Caution-http://public.kitware.com/mailman/listinfo/paraview <
> Caution-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
>



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

From ken.martin at kitware.com  Wed Jun  1 10:16:32 2016
From: ken.martin at kitware.com (Ken Martin)
Date: Wed, 1 Jun 2016 10:16:32 -0400
Subject: [Paraview] [Non-DoD Source] Re: ParaView 5.0.1 on an older Mac
In-Reply-To: <CAB5Fpx5Nu6e15NY4mNhOYOVNdV57_f8SQsCuUsd_wGXa5v+EmA@mail.gmail.com>
References: <D373674D.2B87C%Richard.C.Angelini.CIV@mail.mil>
 <574DF4B8.1080203@bluequartz.net>
 <D37445A8.2B887%Richard.C.Angelini.CIV@mail.mil>
 <CAB5Fpx5Nu6e15NY4mNhOYOVNdV57_f8SQsCuUsd_wGXa5v+EmA@mail.gmail.com>
Message-ID: <CANXz0SZMhJS37Sv2iwFZP++2vV45S7eLy3Ave1cpRREbxJASdw@mail.gmail.com>

The code has been updated in VTK as of a month or two ago. But PV is using
an older version of the code. I doubt the new code would warn on your
system Cory, but until PV releases a new version (or build PV master) it
will continue to use the old code.

We definitely can dynamically test for it, that is basically what the
appleBug test does. To be safe with it I think on apple systems it would
cause a window to pop up briefly while it tests it. (offscreen might not
match onscreen)

Ken


On Wed, Jun 1, 2016 at 9:46 AM, Cory Quammen <cory.quammen at kitware.com>
wrote:

> On Wed, Jun 1, 2016 at 1:57 PM, Angelini, Richard C (Rick) CIV USARMY
> RDECOM ARL (US) <richard.c.angelini.civ at mail.mil> wrote:
> > This system is still running 10.9 and is scheduled for a 10.11 upgrade in
> > the near-term ? presumably the warning message will go away with 10.11
> ??.
>
> Not unless the upgrade includes a driver upgrade for the graphics
> hardware to one of the white-listed graphics drivers. I know this
> because my Mac with 10.11 complained, but it didn't exhibit the buggy
> behavior, so I added it's hardware to the white list.
>
> Ken, could we test for the Apple bug dynamically in VTK or in ParaView
> in any easy way?
>
> Thanks,
> Cory
>
>
> > ________________________________
> > Rick Angelini
> > USArmy Research Laboratory
> > CISD/HPC Architectures Team
> > Phone:  410-278-6266
> >
> > From: Michael Jackson <mike.jackson at bluequartz.net>
> > Date: Tuesday, May 31, 2016 at 4:31 PM
> > To: Rick Angelini <Richard.C.Angelini.CIV at mail.mil>
> > Cc: ParaView <paraview at paraview.org>
> > Subject: [Non-DoD Source] Re: [Paraview] ParaView 5.0.1 on an older Mac
> >
> > All active links contained in this email were disabled. Please verify the
> > identity of the sender, and confirm the authenticity of all links
> contained
> > within the message prior to copying and pasting the address to a Web
> > browser.
> >
> > ________________________________
> >
> >
> > Richard,
> >    You will get this warning/error message on any OS X machine using
> ATI/AMD
> > graphics hardware running OS X 10.10 or earlier. OS X 10.11 corrected an
> > OpenGL driver issue that this error is reporting. It is down in the VTK
> > stack. I do not know if we should be worried or not about the
> warning/error.
> >
> > --
> > Mike Jackson  [mike.jackson at bluequartz.net <
> > Caution-mailto:mike.jackson at bluequartz.net > ]
> >
> > Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US) <
> > Caution-mailto:richard.c.angelini.civ at mail.mil >
> > May 31, 2016 at 4:07 PM
> > I have the following message from one of my local ParaView users:
> >
> > Following is the message I am getting with the Paraview 5 client on the
> Mac.
> > It appears to work in spite of this warning.
> >
> > Warning: In
> >
> /Users/kitware/buildbot-slave/paraview-bigmac-osx-shared-release_opengl2_osx10_7_qt4_superbuild/build/paraview/src/paraview/VTK/Rendering/OpenGL2/vtkOpenGLPolyDataMapper.cxx,
> > line 2856
> > vtkCompositeMapperHelper (0x7fbc4b0e7800): VTK is working around a bug in
> > Apple-AMD hardware related to gl_PrimitiveID.  This may cause significant
> > memory and performance impacts. Your hardware has been identified as
> vendor
> > ATI Technologies Inc. with renderer of ATI Radeon HD 5770 OpenGL Engine
> and
> > version 4.1 ATI-1.24.39
> >
> > About this Mac has the following information about my system:
> > Graphics  ATI Radeon HD 5770 1024 MB
> >
> >
> > The user does not see this error running ParaView 4.x.x ? so ? presumably
> > this warning message is related to OpenGL2 running on an older graphics
> > card???    Is this something we should be worried about in the
> short-term?
> > I?m not sure how much longer this older Mac will be in service ? but
> will we
> > run in to issues with OpenGL2 which will preclude it from working on
> these
> > older systems?
> >
> >
> >
> >
> > ________________________________
> > Rick Angelini
> > USArmy Research Laboratory
> > CISD/HPC Architectures Team
> > Phone:  410-278-6266
> > _______________________________________________
> > Powered by Caution-www.kitware.com < Caution-http://www.kitware.com >
> >
> > Visit other Kitware open-source projects at
> > Caution-http://www.kitware.com/opensource/opensource.html <
> > Caution-http://www.kitware.com/opensource/opensource.html >
> >
> > Please keep messages on-topic and check the ParaView Wiki at:
> > Caution-http://paraview.org/Wiki/ParaView <
> > Caution-http://paraview.org/Wiki/ParaView >
> >
> > Search the list archives at: Caution-
> http://markmail.org/search/?q=ParaView
> > < Caution-http://markmail.org/search/?q=ParaView >
> >
> > Follow this link to subscribe/unsubscribe:
> > Caution-http://public.kitware.com/mailman/listinfo/paraview <
> > Caution-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
> >
>
>
>
> --
> Cory Quammen
> R&D Engineer
> Kitware, Inc.
>



-- 
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/20160601/21bbc418/attachment.html>

From apeczak at ara.co.uk  Wed Jun  1 13:10:13 2016
From: apeczak at ara.co.uk (Andrzej Peczak)
Date: Wed, 1 Jun 2016 17:10:13 +0000
Subject: [Paraview] Custom panel widget
In-Reply-To: <CADHSJjDct6nAa=AEO8bSYrYMrpH4LPfa0zqS3o1Bm7MWJjAWhw@mail.gmail.com>
References: <5DF928D22AC3AC4B964903E98F2E54515B583281@sooty3.win.ara> 
 <CADHSJjDiUwotu_T2=wH7uV0oR5wgW596L93TM2uQgPt69vhtAw@mail.gmail.com> 
 <5DF928D22AC3AC4B964903E98F2E54515B58352C@sooty3.win.ara> 
 <CADHSJjACOAZ27FT5nRPtuRDq_jiezhcwE7Ri-PODpySkkUYLOw@mail.gmail.com> 
 <5DF928D22AC3AC4B964903E98F2E54515B583E60@sooty3.win.ara> 
 <CADHSJjDct6nAa=AEO8bSYrYMrpH4LPfa0zqS3o1Bm7MWJjAWhw@mail.gmail.com>
Message-ID: <5DF928D22AC3AC4B964903E98F2E54515B5840D0@sooty3.win.ara>

Utkarsh,

If I subclass vtkSIProperty how do I register it so that it can be seen in the xml configuration file of my plugin ? 

Andrzej



-----Original Message-----
From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] 
Sent: 31 May 2016 16:21
To: Andrzej Peczak
Cc: ParaView
Subject: Re: [Paraview] Custom panel widget

Andrzej,

Here's a possible approach:

Add a "information_only" property to the proxy to retrieve the values for  max_distance computed by the filter. You can create a custom SIProperty [1] subclass to support arbitrary API to get the values from your filter and communicate that to the SMProperty. Your widget that can explicitly monitor this property to update view of "current values" as appropriate.

What I am not sure if whether the information_property will get updates every time the filter re-executes, e.g. when time changes. If it doesn't, we may have to explicitly monitor the vtkCommand::UpdateDataEvent fired by the proxy and call
vtkSMProxy::UpdatePropertyInformation() explicitly.

[1] http://www.paraview.org/ParaView3/Doc/Nightly/www/cxx-doc/classvtkSIProperty.html

On Fri, May 27, 2016 at 11:58 AM, Andrzej Peczak <apeczak at ara.co.uk> wrote:
> Yes, this is what I want Utkarsh.
>
> The filter does not necessary has to output the distances on the output port (which I presumably would do by assigning a field array to the output geometry)  but I definitely would like them to display and modify in the panel widget to affect the execution logic of the filter.
>
> Andrzej
>
> -----Original Message-----
> From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com]
> Sent: 27 May 2016 13:51
> To: Andrzej Peczak
> Cc: ParaView
> Subject: Re: [Paraview] Custom panel widget
>
> Andrzej,
>
> Just to make sure I understand:
>
> vtkCpCutter calculates slices aka contours on surface and also outputs an array of  "max-distance"s. You want the user to be able to see these values on the panel for this filter and then change them which in turn affects some execution logic in vtkCpCutter. Is that correct?
>
> Utkarsh
>
> On Thu, May 26, 2016 at 7:30 AM, Andrzej Peczak <apeczak at ara.co.uk> wrote:
>> Hi Utkarsh
>>
>> Our use-case scenario is that we have our own filter based on vtkCpCutter (both vtkPolyData on the input and output port) . We use this filter to generate a set of slices on surface geometry. We then process the obtained contours with vtkPlotEdges. For each contour (slice) we would like to compute a scalar value, say max distance between two points in the contour and output the values to the scalar list widget. Of course we also would like to modify the distances and send it back to the filters. These values will be used to update the output of the filter.
>>
>> Andrzej
>>
>>
>> -----Original Message-----
>> From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com]
>> Sent: 23 May 2016 14:58
>> To: Andrzej Peczak
>> Cc: ParaView
>> Subject: Re: [Paraview] Custom panel widget
>>
>>> Is it possible to create a custom widget for a filter which would allow me to retrieve the results of its computation? I would like to reproduce the functionality of the pqDoubleVectorPropertyWidget and populate it with values computed by the filter. I know how to create and register the widget but I do not know how do I send values to it from the filter. In paraview code base  I found vtkEventQtSlotConnect but I do not know if it is of any use to my problem.
>>
>> There are several ways of skinning this cat. Can you elaborate of what exactly is your use-case? Do you want the default values for this double-vector-property (DVP) set using some values provided by the VTK filter, but allow user to override using UI?
>>
>> *********************************************************************
>> * Please consider the environment. Only print this email if 
>> absolutely necessary.
>>
>> This email contains information that is private and confidential and is intended only for the addressee.
>> If you are not the intended recipient please delete it and notify us immediately by e-mailing the sender.
>> Note: All email sent to or from this address may be accessed by 
>> someone other than the recipient, for system management and security reasons.
>> Aircraft Research Association Ltd.  Registered in England, Registration No 503668 Registered Office:
>> Manton Lane, Bedford MK41 7PF England VAT No GB 196351245
>>
>> *********************************************************************
>> *
>
> **********************************************************************
> Please consider the environment. Only print this email if absolutely necessary.
>
> This email contains information that is private and confidential and is intended only for the addressee.
> If you are not the intended recipient please delete it and notify us immediately by e-mailing the sender.
> Note: All email sent to or from this address may be accessed by 
> someone other than the recipient, for system management and security reasons.
> Aircraft Research Association Ltd.  Registered in England, Registration No 503668 Registered Office:
> Manton Lane, Bedford MK41 7PF England VAT No GB 196351245
>
> **********************************************************************

**********************************************************************
Please consider the environment. Only print this email if absolutely necessary.

This email contains information that is private and confidential and is intended only for the addressee.
If you are not the intended recipient please delete it and notify us immediately by e-mailing the sender.
Note: All email sent to or from this address may be accessed by someone other than the recipient, for
system management and security reasons.
Aircraft Research Association Ltd.  Registered in England, Registration No 503668 Registered Office:
Manton Lane, Bedford MK41 7PF England VAT No GB 196351245

**********************************************************************

From richard.c.angelini.civ at mail.mil  Wed Jun  1 14:02:52 2016
From: richard.c.angelini.civ at mail.mil (Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US))
Date: Wed, 1 Jun 2016 18:02:52 +0000
Subject: [Paraview] [Non-DoD Source] Re:  5.0.1/Exodus Reader
In-Reply-To: <D372F723.2B7B7%Richard.C.Angelini.CIV@mail.mil>
References: <D36E056D.2B768%Richard.C.Angelini.CIV@mail.mil>
 <CADHSJjDuw66ZuMxAEOUfAa8ssre_Fb8o=BRwJLg7RZES1WaM0A@mail.gmail.com>
 <D36E09B8.2B77E%Richard.C.Angelini.CIV@mail.mil>
 <CADHSJjCWs9OxvfvdGcdb30Y41OP7=pahxePxbA_8zvLzPC3=kA@mail.gmail.com>
 <D372F723.2B7B7%Richard.C.Angelini.CIV@mail.mil>
Message-ID: <D3749AB6.2B8E9%Richard.C.Angelini.CIV@mail.mil>

So, we are continuing to have issues with 5.0.1 and OpenGL2.      I have
recompiled the server-side to use OpenGL2, and it works fine if when I run
ParaView 5.0.1 from my Mac.     However, if I run ParaView 5.0.1 from my
Linux box,  I?m still getting failures.   Looks like 5.0.1 on my Linux box
(RHEL6) is also built with OpenGL2, but there are apparently additional
issues?????     Here?s some of the output from the error log on the SERVER
side.    What?s generating these GL_Version info messages?      I?m using
the same exact server-side job launching whether I?m running the client on
my Mac or Linux machine - so it would seem that maybe something?s wrong on
the Linux client?????


/opt/cray/alps/5.2.4-2.0502.9822.32.1.ari/bin/aprun
/usr/cta/DAAC/paraview/5.0.1_osmesa/bin/pvserver
aprun -B pvserver --use-offscreen-rendering -rc -ch=excalibur09-int
-sp=4459 --connect-id=40460
Connecting to client (reverse connection requested)...
Connection URL: csrc://excalibur09-int:4459
Client connected.
GL_Version: 2.1 Mesa 7.11.2
GL_Version: 2.1 Mesa 7.11.2
GL_Version: 2.1 Mesa 7.11.2
GL_Version: 2.1 Mesa 7.11.2
GL_Version: 2.1 Mesa 7.11.2
GL_Version: 2.1 Mesa 7.11.2
GL_Version: 2.1 Mesa 7.11.2
GL_Version: 2.1 Mesa 7.11.2
GL_Version: 2.1 Mesa 7.11.2
GL_Version: 2.1 Mesa 7.11.2
GL_Version: 2.1 Mesa 7.11.2
GL_Version: 2.1 Mesa 7.11.2
ERROR: In
/usr/people/joeh/PV/Build_5.0.1_osmesa/paraview/src/paraview/VTK/Rendering/
OpenGL2/vtkOpenGLRenderWindow.cxx, line 587
vtkOSOpenGLRenderWindow (0x147ab50): GL version 2.1 with the gpu_shader4
extension is not supported by your graphics driver but is required for the
new OpenGL rendering backend. Please update your OpenGL driver. If you are
using Mesa please make sure you have version 10.6.5 or later and make sure
your driver in Mesa supports OpenGL 3.2.




________________________________
Rick Angelini
USArmy Research Laboratory
CISD/HPC Architectures Team
Phone:  410-278-6266




-----Original Message-----
From: ParaView <paraview-bounces at paraview.org> on behalf of Rick Angelini
<Richard.C.Angelini.CIV at mail.mil>
Date: Tuesday, May 31, 2016 at 8:09 AM
To: Utkarsh Ayachit <utkarsh.ayachit at kitware.com>
Cc: ParaView <paraview at paraview.org>
Subject: Re: [Paraview] [Non-DoD Source] Re:  5.0.1/Exodus Reader

All active links contained in this email were disabled.  Please verify the
identity of the sender, and confirm the authenticity of all links
contained within the message prior to copying and pasting the address to a
Web browser.  




----

Utkarsh - thanks for info.    Recompiling the server-side with OpenGL2
resolved the problem!


________________________________
Rick Angelini
USArmy Research Laboratory
CISD/HPC Architectures Team
Phone:  410-278-6266




-----Original Message-----
From: Utkarsh Ayachit <utkarsh.ayachit at kitware.com>
Date: Friday, May 27, 2016 at 2:37 PM
To: Rick Angelini <Richard.C.Angelini.CIV at mail.mil>
Cc: ParaView <paraview at paraview.org>
Subject: Re: [Non-DoD Source] Re: [Paraview] 5.0.1/Exodus Reader

> Yep - we built the HPC-side with ?OpenGL2? ? so does that mean that the
> pre-built Mac/Linux binaries were both built with OpenGL?    Is there
>some
> way to check to see which OpenGL the client was built with?

The binaries distributed by paraview.org are indeed OpenGL2. The title
bar for ParaView 5.0.1 says "(Legacy Rendering Backend)" when using
"OpenGL". Given the error, I think your server is not built with
OpenGL2, despite your intention. Can you check your CMakeCache.txt on
the server build to confirm?

Utkarsh

_______________________________________________
Powered by Caution-www.kitware.com

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

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

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

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


From utkarsh.ayachit at kitware.com  Wed Jun  1 15:48:28 2016
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Wed, 1 Jun 2016 15:48:28 -0400
Subject: [Paraview] [Non-DoD Source] Re: 5.0.1/Exodus Reader
In-Reply-To: <D3749AB6.2B8E9%Richard.C.Angelini.CIV@mail.mil>
References: <D36E056D.2B768%Richard.C.Angelini.CIV@mail.mil>
 <CADHSJjDuw66ZuMxAEOUfAa8ssre_Fb8o=BRwJLg7RZES1WaM0A@mail.gmail.com>
 <D36E09B8.2B77E%Richard.C.Angelini.CIV@mail.mil>
 <CADHSJjCWs9OxvfvdGcdb30Y41OP7=pahxePxbA_8zvLzPC3=kA@mail.gmail.com>
 <D372F723.2B7B7%Richard.C.Angelini.CIV@mail.mil>
 <D3749AB6.2B8E9%Richard.C.Angelini.CIV@mail.mil>
Message-ID: <CADHSJjBLab45qdXtg0w_ohqQO9ydcKDUXPEbb38Fix+5X+jkfg@mail.gmail.com>

Rick,

Are you by any change using local rendering on your Mac and remote
rendering on your linux client box?

Utkarsh

On Wed, Jun 1, 2016 at 2:02 PM, Angelini, Richard C (Rick) CIV USARMY
RDECOM ARL (US) <richard.c.angelini.civ at mail.mil> wrote:
> So, we are continuing to have issues with 5.0.1 and OpenGL2.      I have
> recompiled the server-side to use OpenGL2, and it works fine if when I run
> ParaView 5.0.1 from my Mac.     However, if I run ParaView 5.0.1 from my
> Linux box,  I?m still getting failures.   Looks like 5.0.1 on my Linux box
> (RHEL6) is also built with OpenGL2, but there are apparently additional
> issues?????     Here?s some of the output from the error log on the SERVER
> side.    What?s generating these GL_Version info messages?      I?m using
> the same exact server-side job launching whether I?m running the client on
> my Mac or Linux machine - so it would seem that maybe something?s wrong on
> the Linux client?????
>
>
> /opt/cray/alps/5.2.4-2.0502.9822.32.1.ari/bin/aprun
> /usr/cta/DAAC/paraview/5.0.1_osmesa/bin/pvserver
> aprun -B pvserver --use-offscreen-rendering -rc -ch=excalibur09-int
> -sp=4459 --connect-id=40460
> Connecting to client (reverse connection requested)...
> Connection URL: csrc://excalibur09-int:4459
> Client connected.
> GL_Version: 2.1 Mesa 7.11.2
> GL_Version: 2.1 Mesa 7.11.2
> GL_Version: 2.1 Mesa 7.11.2
> GL_Version: 2.1 Mesa 7.11.2
> GL_Version: 2.1 Mesa 7.11.2
> GL_Version: 2.1 Mesa 7.11.2
> GL_Version: 2.1 Mesa 7.11.2
> GL_Version: 2.1 Mesa 7.11.2
> GL_Version: 2.1 Mesa 7.11.2
> GL_Version: 2.1 Mesa 7.11.2
> GL_Version: 2.1 Mesa 7.11.2
> GL_Version: 2.1 Mesa 7.11.2
> ERROR: In
> /usr/people/joeh/PV/Build_5.0.1_osmesa/paraview/src/paraview/VTK/Rendering/
> OpenGL2/vtkOpenGLRenderWindow.cxx, line 587
> vtkOSOpenGLRenderWindow (0x147ab50): GL version 2.1 with the gpu_shader4
> extension is not supported by your graphics driver but is required for the
> new OpenGL rendering backend. Please update your OpenGL driver. If you are
> using Mesa please make sure you have version 10.6.5 or later and make sure
> your driver in Mesa supports OpenGL 3.2.
>
>
>
>
> ________________________________
> Rick Angelini
> USArmy Research Laboratory
> CISD/HPC Architectures Team
> Phone:  410-278-6266
>
>
>
>
> -----Original Message-----
> From: ParaView <paraview-bounces at paraview.org> on behalf of Rick Angelini
> <Richard.C.Angelini.CIV at mail.mil>
> Date: Tuesday, May 31, 2016 at 8:09 AM
> To: Utkarsh Ayachit <utkarsh.ayachit at kitware.com>
> Cc: ParaView <paraview at paraview.org>
> Subject: Re: [Paraview] [Non-DoD Source] Re:  5.0.1/Exodus Reader
>
> All active links contained in this email were disabled.  Please verify the
> identity of the sender, and confirm the authenticity of all links
> contained within the message prior to copying and pasting the address to a
> Web browser.
>
>
>
>
> ----
>
> Utkarsh - thanks for info.    Recompiling the server-side with OpenGL2
> resolved the problem!
>
>
> ________________________________
> Rick Angelini
> USArmy Research Laboratory
> CISD/HPC Architectures Team
> Phone:  410-278-6266
>
>
>
>
> -----Original Message-----
> From: Utkarsh Ayachit <utkarsh.ayachit at kitware.com>
> Date: Friday, May 27, 2016 at 2:37 PM
> To: Rick Angelini <Richard.C.Angelini.CIV at mail.mil>
> Cc: ParaView <paraview at paraview.org>
> Subject: Re: [Non-DoD Source] Re: [Paraview] 5.0.1/Exodus Reader
>
>> Yep - we built the HPC-side with ?OpenGL2? ? so does that mean that the
>> pre-built Mac/Linux binaries were both built with OpenGL?    Is there
>>some
>> way to check to see which OpenGL the client was built with?
>
> The binaries distributed by paraview.org are indeed OpenGL2. The title
> bar for ParaView 5.0.1 says "(Legacy Rendering Backend)" when using
> "OpenGL". Given the error, I think your server is not built with
> OpenGL2, despite your intention. Can you check your CMakeCache.txt on
> the server build to confirm?
>
> Utkarsh
>
> _______________________________________________
> Powered by Caution-www.kitware.com
>
> Visit other Kitware open-source projects at
> Caution-http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> Caution-http://paraview.org/Wiki/ParaView
>
> Search the list archives at: Caution-http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> Caution-http://public.kitware.com/mailman/listinfo/paraview
>

From richard.c.angelini.civ at mail.mil  Wed Jun  1 15:59:31 2016
From: richard.c.angelini.civ at mail.mil (Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US))
Date: Wed, 1 Jun 2016 19:59:31 +0000
Subject: [Paraview] [Non-DoD Source] Re: 5.0.1/Exodus Reader
In-Reply-To: <CADHSJjBLab45qdXtg0w_ohqQO9ydcKDUXPEbb38Fix+5X+jkfg@mail.gmail.com>
References: <D36E056D.2B768%Richard.C.Angelini.CIV@mail.mil>
 <CADHSJjDuw66ZuMxAEOUfAa8ssre_Fb8o=BRwJLg7RZES1WaM0A@mail.gmail.com>
 <D36E09B8.2B77E%Richard.C.Angelini.CIV@mail.mil>
 <CADHSJjCWs9OxvfvdGcdb30Y41OP7=pahxePxbA_8zvLzPC3=kA@mail.gmail.com>
 <D372F723.2B7B7%Richard.C.Angelini.CIV@mail.mil>
 <D3749AB6.2B8E9%Richard.C.Angelini.CIV@mail.mil>
 <CADHSJjBLab45qdXtg0w_ohqQO9ydcKDUXPEbb38Fix+5X+jkfg@mail.gmail.com>
Message-ID: <D374B54E.2B923%Richard.C.Angelini.CIV@mail.mil>

DOH!  The render threshold values were set differently on the Mac and
Linux systems.   As soon as I forced the Mac to use distributed rendering,
it failed with the same error messages.    So do we have a build issue on
the HPC-side?      We have rebuilt with OpenGL2 enabled, but it seems like
it?s not picking up the correct Mesa libs????    Presumably we?re using
the Superbuild and it should be building using the Mesa that?s part of the
Superbuild????

ERROR: In 
/usr/people/joeh/PV/Build_5.0.1_osmesa/paraview/src/paraview/VTK/Rendering/
OpenGL2/vtkOpenGLRenderWindow.cxx, line 587
vtkOSOpenGLRenderWindow (0x1487a00): GL version 2.1 with the gpu_shader4
extension is not supported by your graphics driver but is required for the
new OpenGL rendering backend. Please update your OpenGL driver. If you are
using Mesa please make sure you have version 10.6.5 or later and make sure
your driver in Mesa supports OpenGL 3.2.


ERROR: In 
/Users/kitware/buildbot-slave/paraview-bigmac-osx-shared-release_opengl2_os
x10_7_qt4_superbuild/build/paraview/src/paraview/ParaViewCore/ServerManager
/Core/vtkSMSessionClient.cxx, line 821
vtkSMSessionClient (0x7fda8344f1a0): Server failed to gather information.




________________________________
Rick Angelini
USArmy Research Laboratory
CISD/HPC Architectures Team
Phone:  410-278-6266




-----Original Message-----
From: Utkarsh Ayachit <utkarsh.ayachit at kitware.com>
Date: Wednesday, June 1, 2016 at 3:48 PM
To: Rick Angelini <Richard.C.Angelini.CIV at mail.mil>
Cc: ParaView <paraview at paraview.org>
Subject: Re: [Paraview] [Non-DoD Source] Re: 5.0.1/Exodus Reader

Rick,

Are you by any change using local rendering on your Mac and remote
rendering on your linux client box?

Utkarsh

On Wed, Jun 1, 2016 at 2:02 PM, Angelini, Richard C (Rick) CIV USARMY
RDECOM ARL (US) <richard.c.angelini.civ at mail.mil> wrote:
> So, we are continuing to have issues with 5.0.1 and OpenGL2.      I have
> recompiled the server-side to use OpenGL2, and it works fine if when I
>run
> ParaView 5.0.1 from my Mac.     However, if I run ParaView 5.0.1 from my
> Linux box,  I?m still getting failures.   Looks like 5.0.1 on my Linux
>box
> (RHEL6) is also built with OpenGL2, but there are apparently additional
> issues?????     Here?s some of the output from the error log on the
>SERVER
> side.    What?s generating these GL_Version info messages?      I?m using
> the same exact server-side job launching whether I?m running the client
>on
> my Mac or Linux machine - so it would seem that maybe something?s wrong
>on
> the Linux client?????
>
>
> /opt/cray/alps/5.2.4-2.0502.9822.32.1.ari/bin/aprun
> /usr/cta/DAAC/paraview/5.0.1_osmesa/bin/pvserver
> aprun -B pvserver --use-offscreen-rendering -rc -ch=excalibur09-int
> -sp=4459 --connect-id=40460
> Connecting to client (reverse connection requested)...
> Connection URL: csrc://excalibur09-int:4459
> Client connected.
> GL_Version: 2.1 Mesa 7.11.2
> GL_Version: 2.1 Mesa 7.11.2
> GL_Version: 2.1 Mesa 7.11.2
> GL_Version: 2.1 Mesa 7.11.2
> GL_Version: 2.1 Mesa 7.11.2
> GL_Version: 2.1 Mesa 7.11.2
> GL_Version: 2.1 Mesa 7.11.2
> GL_Version: 2.1 Mesa 7.11.2
> GL_Version: 2.1 Mesa 7.11.2
> GL_Version: 2.1 Mesa 7.11.2
> GL_Version: 2.1 Mesa 7.11.2
> GL_Version: 2.1 Mesa 7.11.2
> ERROR: In
> 
>/usr/people/joeh/PV/Build_5.0.1_osmesa/paraview/src/paraview/VTK/Rendering
>/
> OpenGL2/vtkOpenGLRenderWindow.cxx, line 587
> vtkOSOpenGLRenderWindow (0x147ab50): GL version 2.1 with the gpu_shader4
> extension is not supported by your graphics driver but is required for
>the
> new OpenGL rendering backend. Please update your OpenGL driver. If you
>are
> using Mesa please make sure you have version 10.6.5 or later and make
>sure
> your driver in Mesa supports OpenGL 3.2.
>
>
>
>
> ________________________________
> Rick Angelini
> USArmy Research Laboratory
> CISD/HPC Architectures Team
> Phone:  410-278-6266
>
>
>
>
> -----Original Message-----
> From: ParaView <paraview-bounces at paraview.org> on behalf of Rick Angelini
> <Richard.C.Angelini.CIV at mail.mil>
> Date: Tuesday, May 31, 2016 at 8:09 AM
> To: Utkarsh Ayachit <utkarsh.ayachit at kitware.com>
> Cc: ParaView <paraview at paraview.org>
> Subject: Re: [Paraview] [Non-DoD Source] Re:  5.0.1/Exodus Reader
>
> All active links contained in this email were disabled.  Please verify
>the
> identity of the sender, and confirm the authenticity of all links
> contained within the message prior to copying and pasting the address to
>a
> Web browser.
>
>
>
>
> ----
>
> Utkarsh - thanks for info.    Recompiling the server-side with OpenGL2
> resolved the problem!
>
>
> ________________________________
> Rick Angelini
> USArmy Research Laboratory
> CISD/HPC Architectures Team
> Phone:  410-278-6266
>
>
>
>
> -----Original Message-----
> From: Utkarsh Ayachit <utkarsh.ayachit at kitware.com>
> Date: Friday, May 27, 2016 at 2:37 PM
> To: Rick Angelini <Richard.C.Angelini.CIV at mail.mil>
> Cc: ParaView <paraview at paraview.org>
> Subject: Re: [Non-DoD Source] Re: [Paraview] 5.0.1/Exodus Reader
>
>> Yep - we built the HPC-side with ?OpenGL2? ? so does that mean that the
>> pre-built Mac/Linux binaries were both built with OpenGL?    Is there
>>some
>> way to check to see which OpenGL the client was built with?
>
> The binaries distributed by paraview.org are indeed OpenGL2. The title
> bar for ParaView 5.0.1 says "(Legacy Rendering Backend)" when using
> "OpenGL". Given the error, I think your server is not built with
> OpenGL2, despite your intention. Can you check your CMakeCache.txt on
> the server build to confirm?
>
> Utkarsh
>
> _______________________________________________
> Powered by Caution-www.kitware.com
>
> Visit other Kitware open-source projects at
> Caution-http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> Caution-http://paraview.org/Wiki/ParaView
>
> Search the list archives at:
>Caution-http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> Caution-http://public.kitware.com/mailman/listinfo/paraview
>


From richard.c.angelini.civ at mail.mil  Wed Jun  1 16:06:11 2016
From: richard.c.angelini.civ at mail.mil (Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US))
Date: Wed, 1 Jun 2016 20:06:11 +0000
Subject: [Paraview] [Non-DoD Source] Re: 5.0.1/Exodus Reader
In-Reply-To: <D374B54E.2B923%Richard.C.Angelini.CIV@mail.mil>
References: <D36E056D.2B768%Richard.C.Angelini.CIV@mail.mil>
 <CADHSJjDuw66ZuMxAEOUfAa8ssre_Fb8o=BRwJLg7RZES1WaM0A@mail.gmail.com>
 <D36E09B8.2B77E%Richard.C.Angelini.CIV@mail.mil>
 <CADHSJjCWs9OxvfvdGcdb30Y41OP7=pahxePxbA_8zvLzPC3=kA@mail.gmail.com>
 <D372F723.2B7B7%Richard.C.Angelini.CIV@mail.mil>
 <D3749AB6.2B8E9%Richard.C.Angelini.CIV@mail.mil>
 <CADHSJjBLab45qdXtg0w_ohqQO9ydcKDUXPEbb38Fix+5X+jkfg@mail.gmail.com>
 <D374B54E.2B923%Richard.C.Angelini.CIV@mail.mil>
Message-ID: <D374B81D.2B935%Richard.C.Angelini.CIV@mail.mil>

Is there an issue in the SuperBuild?   I just did a quick look through the
Superbuild source, and it looks like the file version.cmake is wanting to
use MesaLib-7.11.2 ?..


59  $ git pull
Already up-to-date.


60 $ grep -i mesa versions.cmake
  add_revision(mesa
    URL "http://www.paraview.org/files/dependencies/MesaLib-7.6.1.tar.gz"
  add_revision(mesa
    URL "http://paraview.org/files/dependencies/MesaLib-7.11.2.tar.gz"
# We stick with 7.11.2 for Mesa version for now. Newer mesa doesn't seem to
add_revision(osmesa
    URL "http://paraview.org/files/dependencies/MesaLib-7.11.2.tar.gz"



________________________________
Rick Angelini
USArmy Research Laboratory
CISD/HPC Architectures Team
Phone:  410-278-6266




-----Original Message-----
From: ParaView <paraview-bounces at paraview.org> on behalf of Rick Angelini
<Richard.C.Angelini.CIV at mail.mil>
Date: Wednesday, June 1, 2016 at 3:59 PM
To: Utkarsh Ayachit <utkarsh.ayachit at kitware.com>
Cc: ParaView <paraview at paraview.org>
Subject: Re: [Paraview] [Non-DoD Source] Re: 5.0.1/Exodus Reader

All active links contained in this email were disabled.  Please verify the
identity of the sender, and confirm the authenticity of all links
contained within the message prior to copying and pasting the address to a
Web browser.  




----

DOH!  The render threshold values were set differently on the Mac and
Linux systems.   As soon as I forced the Mac to use distributed rendering,
it failed with the same error messages.    So do we have a build issue on
the HPC-side?      We have rebuilt with OpenGL2 enabled, but it seems like
it?s not picking up the correct Mesa libs????    Presumably we?re using
the Superbuild and it should be building using the Mesa that?s part of the
Superbuild????

ERROR: In 
/usr/people/joeh/PV/Build_5.0.1_osmesa/paraview/src/paraview/VTK/Rendering/
OpenGL2/vtkOpenGLRenderWindow.cxx, line 587
vtkOSOpenGLRenderWindow (0x1487a00): GL version 2.1 with the gpu_shader4
extension is not supported by your graphics driver but is required for the
new OpenGL rendering backend. Please update your OpenGL driver. If you are
using Mesa please make sure you have version 10.6.5 or later and make sure
your driver in Mesa supports OpenGL 3.2.


ERROR: In 
/Users/kitware/buildbot-slave/paraview-bigmac-osx-shared-release_opengl2_os
x10_7_qt4_superbuild/build/paraview/src/paraview/ParaViewCore/ServerManager
/Core/vtkSMSessionClient.cxx, line 821
vtkSMSessionClient (0x7fda8344f1a0): Server failed to gather information.




________________________________
Rick Angelini
USArmy Research Laboratory
CISD/HPC Architectures Team
Phone:  410-278-6266




-----Original Message-----
From: Utkarsh Ayachit <utkarsh.ayachit at kitware.com>
Date: Wednesday, June 1, 2016 at 3:48 PM
To: Rick Angelini <Richard.C.Angelini.CIV at mail.mil>
Cc: ParaView <paraview at paraview.org>
Subject: Re: [Paraview] [Non-DoD Source] Re: 5.0.1/Exodus Reader

Rick,

Are you by any change using local rendering on your Mac and remote
rendering on your linux client box?

Utkarsh

On Wed, Jun 1, 2016 at 2:02 PM, Angelini, Richard C (Rick) CIV USARMY
RDECOM ARL (US) <richard.c.angelini.civ at mail.mil> wrote:
> So, we are continuing to have issues with 5.0.1 and OpenGL2.      I have
> recompiled the server-side to use OpenGL2, and it works fine if when I
>run
> ParaView 5.0.1 from my Mac.     However, if I run ParaView 5.0.1 from my
> Linux box,  I?m still getting failures.   Looks like 5.0.1 on my Linux
>box
> (RHEL6) is also built with OpenGL2, but there are apparently additional
> issues?????     Here?s some of the output from the error log on the
>SERVER
> side.    What?s generating these GL_Version info messages?      I?m using
> the same exact server-side job launching whether I?m running the client
>on
> my Mac or Linux machine - so it would seem that maybe something?s wrong
>on
> the Linux client?????
>
>
> /opt/cray/alps/5.2.4-2.0502.9822.32.1.ari/bin/aprun
> /usr/cta/DAAC/paraview/5.0.1_osmesa/bin/pvserver
> aprun -B pvserver --use-offscreen-rendering -rc -ch=excalibur09-int
> -sp=4459 --connect-id=40460
> Connecting to client (reverse connection requested)...
> Connection Caution-url: csrc://excalibur09-int:4459
> Client connected.
> GL_Version: 2.1 Mesa 7.11.2
> GL_Version: 2.1 Mesa 7.11.2
> GL_Version: 2.1 Mesa 7.11.2
> GL_Version: 2.1 Mesa 7.11.2
> GL_Version: 2.1 Mesa 7.11.2
> GL_Version: 2.1 Mesa 7.11.2
> GL_Version: 2.1 Mesa 7.11.2
> GL_Version: 2.1 Mesa 7.11.2
> GL_Version: 2.1 Mesa 7.11.2
> GL_Version: 2.1 Mesa 7.11.2
> GL_Version: 2.1 Mesa 7.11.2
> GL_Version: 2.1 Mesa 7.11.2
> ERROR: In
> 
>/usr/people/joeh/PV/Build_5.0.1_osmesa/paraview/src/paraview/VTK/Rendering
>/
> OpenGL2/vtkOpenGLRenderWindow.cxx, line 587
> vtkOSOpenGLRenderWindow (0x147ab50): GL version 2.1 with the gpu_shader4
> extension is not supported by your graphics driver but is required for
>the
> new OpenGL rendering backend. Please update your OpenGL driver. If you
>are
> using Mesa please make sure you have version 10.6.5 or later and make
>sure
> your driver in Mesa supports OpenGL 3.2.
>
>
>
>
> ________________________________
> Rick Angelini
> USArmy Research Laboratory
> CISD/HPC Architectures Team
> Phone:  410-278-6266
>
>
>
>
> -----Original Message-----
> From: ParaView <paraview-bounces at paraview.org> on behalf of Rick Angelini
> <Richard.C.Angelini.CIV at mail.mil>
> Date: Tuesday, May 31, 2016 at 8:09 AM
> To: Utkarsh Ayachit <utkarsh.ayachit at kitware.com>
> Cc: ParaView <paraview at paraview.org>
> Subject: Re: [Paraview] [Non-DoD Source] Re:  5.0.1/Exodus Reader
>
> All active links contained in this email were disabled.  Please verify
>the
> identity of the sender, and confirm the authenticity of all links
> contained within the message prior to copying and pasting the address to
>a
> Web browser.
>
>
>
>
> ----
>
> Utkarsh - thanks for info.    Recompiling the server-side with OpenGL2
> resolved the problem!
>
>
> ________________________________
> Rick Angelini
> USArmy Research Laboratory
> CISD/HPC Architectures Team
> Phone:  410-278-6266
>
>
>
>
> -----Original Message-----
> From: Utkarsh Ayachit <utkarsh.ayachit at kitware.com>
> Date: Friday, May 27, 2016 at 2:37 PM
> To: Rick Angelini <Richard.C.Angelini.CIV at mail.mil>
> Cc: ParaView <paraview at paraview.org>
> Subject: Re: [Non-DoD Source] Re: [Paraview] 5.0.1/Exodus Reader
>
>> Yep - we built the HPC-side with ?OpenGL2? ? so does that mean that the
>> pre-built Mac/Linux binaries were both built with OpenGL?    Is there
>>some
>> way to check to see which OpenGL the client was built with?
>
> The binaries distributed by paraview.org are indeed OpenGL2. The title
> bar for ParaView 5.0.1 says "(Legacy Rendering Backend)" when using
> "OpenGL". Given the error, I think your server is not built with
> OpenGL2, despite your intention. Can you check your CMakeCache.txt on
> the server build to confirm?
>
> Utkarsh
>
> _______________________________________________
> Powered by Caution-Caution-www.kitware.com
>
> Visit other Kitware open-source projects at
> Caution-Caution-http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> Caution-Caution-http://paraview.org/Wiki/ParaView
>
> Search the list archives at:
>Caution-Caution-http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> Caution-Caution-http://public.kitware.com/mailman/listinfo/paraview
>

_______________________________________________
Powered by Caution-www.kitware.com

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

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

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

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


From utkarsh.ayachit at kitware.com  Wed Jun  1 16:28:32 2016
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Wed, 1 Jun 2016 16:28:32 -0400
Subject: [Paraview] [Non-DoD Source] Re: 5.0.1/Exodus Reader
In-Reply-To: <D374B81D.2B935%Richard.C.Angelini.CIV@mail.mil>
References: <D36E056D.2B768%Richard.C.Angelini.CIV@mail.mil>
 <CADHSJjDuw66ZuMxAEOUfAa8ssre_Fb8o=BRwJLg7RZES1WaM0A@mail.gmail.com>
 <D36E09B8.2B77E%Richard.C.Angelini.CIV@mail.mil>
 <CADHSJjCWs9OxvfvdGcdb30Y41OP7=pahxePxbA_8zvLzPC3=kA@mail.gmail.com>
 <D372F723.2B7B7%Richard.C.Angelini.CIV@mail.mil>
 <D3749AB6.2B8E9%Richard.C.Angelini.CIV@mail.mil>
 <CADHSJjBLab45qdXtg0w_ohqQO9ydcKDUXPEbb38Fix+5X+jkfg@mail.gmail.com>
 <D374B54E.2B923%Richard.C.Angelini.CIV@mail.mil>
 <D374B81D.2B935%Richard.C.Angelini.CIV@mail.mil>
Message-ID: <CADHSJjDU=Hhwi2Y=ah=rzRRiF1Tuj3B4xz32FE_YvJVdNqFDLQ@mail.gmail.com>

Rick,

The superbuild isn't updated yet to build newer Mesa. Mesa now needs
LLVM etc and hence it's a little tricky. I believe Chuck is working on
getting that working. In the mean time, here's a docker file we use to
build mesa verions:

https://gitlab.kitware.com/paraview/mesa-builds/tree/master

That will show what options to use to build mesa appropriately.

Utkarsh


On Wed, Jun 1, 2016 at 4:06 PM, Angelini, Richard C (Rick) CIV USARMY
RDECOM ARL (US) <richard.c.angelini.civ at mail.mil> wrote:
> Is there an issue in the SuperBuild?   I just did a quick look through the
> Superbuild source, and it looks like the file version.cmake is wanting to
> use MesaLib-7.11.2 ?..
>
>
> 59  $ git pull
> Already up-to-date.
>
>
> 60 $ grep -i mesa versions.cmake
>   add_revision(mesa
>     URL "http://www.paraview.org/files/dependencies/MesaLib-7.6.1.tar.gz"
>   add_revision(mesa
>     URL "http://paraview.org/files/dependencies/MesaLib-7.11.2.tar.gz"
> # We stick with 7.11.2 for Mesa version for now. Newer mesa doesn't seem to
> add_revision(osmesa
>     URL "http://paraview.org/files/dependencies/MesaLib-7.11.2.tar.gz"
>
>
>
> ________________________________
> Rick Angelini
> USArmy Research Laboratory
> CISD/HPC Architectures Team
> Phone:  410-278-6266
>
>
>
>
> -----Original Message-----
> From: ParaView <paraview-bounces at paraview.org> on behalf of Rick Angelini
> <Richard.C.Angelini.CIV at mail.mil>
> Date: Wednesday, June 1, 2016 at 3:59 PM
> To: Utkarsh Ayachit <utkarsh.ayachit at kitware.com>
> Cc: ParaView <paraview at paraview.org>
> Subject: Re: [Paraview] [Non-DoD Source] Re: 5.0.1/Exodus Reader
>
> All active links contained in this email were disabled.  Please verify the
> identity of the sender, and confirm the authenticity of all links
> contained within the message prior to copying and pasting the address to a
> Web browser.
>
>
>
>
> ----
>
> DOH!  The render threshold values were set differently on the Mac and
> Linux systems.   As soon as I forced the Mac to use distributed rendering,
> it failed with the same error messages.    So do we have a build issue on
> the HPC-side?      We have rebuilt with OpenGL2 enabled, but it seems like
> it?s not picking up the correct Mesa libs????    Presumably we?re using
> the Superbuild and it should be building using the Mesa that?s part of the
> Superbuild????
>
> ERROR: In
> /usr/people/joeh/PV/Build_5.0.1_osmesa/paraview/src/paraview/VTK/Rendering/
> OpenGL2/vtkOpenGLRenderWindow.cxx, line 587
> vtkOSOpenGLRenderWindow (0x1487a00): GL version 2.1 with the gpu_shader4
> extension is not supported by your graphics driver but is required for the
> new OpenGL rendering backend. Please update your OpenGL driver. If you are
> using Mesa please make sure you have version 10.6.5 or later and make sure
> your driver in Mesa supports OpenGL 3.2.
>
>
> ERROR: In
> /Users/kitware/buildbot-slave/paraview-bigmac-osx-shared-release_opengl2_os
> x10_7_qt4_superbuild/build/paraview/src/paraview/ParaViewCore/ServerManager
> /Core/vtkSMSessionClient.cxx, line 821
> vtkSMSessionClient (0x7fda8344f1a0): Server failed to gather information.
>
>
>
>
> ________________________________
> Rick Angelini
> USArmy Research Laboratory
> CISD/HPC Architectures Team
> Phone:  410-278-6266
>
>
>
>
> -----Original Message-----
> From: Utkarsh Ayachit <utkarsh.ayachit at kitware.com>
> Date: Wednesday, June 1, 2016 at 3:48 PM
> To: Rick Angelini <Richard.C.Angelini.CIV at mail.mil>
> Cc: ParaView <paraview at paraview.org>
> Subject: Re: [Paraview] [Non-DoD Source] Re: 5.0.1/Exodus Reader
>
> Rick,
>
> Are you by any change using local rendering on your Mac and remote
> rendering on your linux client box?
>
> Utkarsh
>
> On Wed, Jun 1, 2016 at 2:02 PM, Angelini, Richard C (Rick) CIV USARMY
> RDECOM ARL (US) <richard.c.angelini.civ at mail.mil> wrote:
>> So, we are continuing to have issues with 5.0.1 and OpenGL2.      I have
>> recompiled the server-side to use OpenGL2, and it works fine if when I
>>run
>> ParaView 5.0.1 from my Mac.     However, if I run ParaView 5.0.1 from my
>> Linux box,  I?m still getting failures.   Looks like 5.0.1 on my Linux
>>box
>> (RHEL6) is also built with OpenGL2, but there are apparently additional
>> issues?????     Here?s some of the output from the error log on the
>>SERVER
>> side.    What?s generating these GL_Version info messages?      I?m using
>> the same exact server-side job launching whether I?m running the client
>>on
>> my Mac or Linux machine - so it would seem that maybe something?s wrong
>>on
>> the Linux client?????
>>
>>
>> /opt/cray/alps/5.2.4-2.0502.9822.32.1.ari/bin/aprun
>> /usr/cta/DAAC/paraview/5.0.1_osmesa/bin/pvserver
>> aprun -B pvserver --use-offscreen-rendering -rc -ch=excalibur09-int
>> -sp=4459 --connect-id=40460
>> Connecting to client (reverse connection requested)...
>> Connection Caution-url: csrc://excalibur09-int:4459
>> Client connected.
>> GL_Version: 2.1 Mesa 7.11.2
>> GL_Version: 2.1 Mesa 7.11.2
>> GL_Version: 2.1 Mesa 7.11.2
>> GL_Version: 2.1 Mesa 7.11.2
>> GL_Version: 2.1 Mesa 7.11.2
>> GL_Version: 2.1 Mesa 7.11.2
>> GL_Version: 2.1 Mesa 7.11.2
>> GL_Version: 2.1 Mesa 7.11.2
>> GL_Version: 2.1 Mesa 7.11.2
>> GL_Version: 2.1 Mesa 7.11.2
>> GL_Version: 2.1 Mesa 7.11.2
>> GL_Version: 2.1 Mesa 7.11.2
>> ERROR: In
>>
>>/usr/people/joeh/PV/Build_5.0.1_osmesa/paraview/src/paraview/VTK/Rendering
>>/
>> OpenGL2/vtkOpenGLRenderWindow.cxx, line 587
>> vtkOSOpenGLRenderWindow (0x147ab50): GL version 2.1 with the gpu_shader4
>> extension is not supported by your graphics driver but is required for
>>the
>> new OpenGL rendering backend. Please update your OpenGL driver. If you
>>are
>> using Mesa please make sure you have version 10.6.5 or later and make
>>sure
>> your driver in Mesa supports OpenGL 3.2.
>>
>>
>>
>>
>> ________________________________
>> Rick Angelini
>> USArmy Research Laboratory
>> CISD/HPC Architectures Team
>> Phone:  410-278-6266
>>
>>
>>
>>
>> -----Original Message-----
>> From: ParaView <paraview-bounces at paraview.org> on behalf of Rick Angelini
>> <Richard.C.Angelini.CIV at mail.mil>
>> Date: Tuesday, May 31, 2016 at 8:09 AM
>> To: Utkarsh Ayachit <utkarsh.ayachit at kitware.com>
>> Cc: ParaView <paraview at paraview.org>
>> Subject: Re: [Paraview] [Non-DoD Source] Re:  5.0.1/Exodus Reader
>>
>> All active links contained in this email were disabled.  Please verify
>>the
>> identity of the sender, and confirm the authenticity of all links
>> contained within the message prior to copying and pasting the address to
>>a
>> Web browser.
>>
>>
>>
>>
>> ----
>>
>> Utkarsh - thanks for info.    Recompiling the server-side with OpenGL2
>> resolved the problem!
>>
>>
>> ________________________________
>> Rick Angelini
>> USArmy Research Laboratory
>> CISD/HPC Architectures Team
>> Phone:  410-278-6266
>>
>>
>>
>>
>> -----Original Message-----
>> From: Utkarsh Ayachit <utkarsh.ayachit at kitware.com>
>> Date: Friday, May 27, 2016 at 2:37 PM
>> To: Rick Angelini <Richard.C.Angelini.CIV at mail.mil>
>> Cc: ParaView <paraview at paraview.org>
>> Subject: Re: [Non-DoD Source] Re: [Paraview] 5.0.1/Exodus Reader
>>
>>> Yep - we built the HPC-side with ?OpenGL2? ? so does that mean that the
>>> pre-built Mac/Linux binaries were both built with OpenGL?    Is there
>>>some
>>> way to check to see which OpenGL the client was built with?
>>
>> The binaries distributed by paraview.org are indeed OpenGL2. The title
>> bar for ParaView 5.0.1 says "(Legacy Rendering Backend)" when using
>> "OpenGL". Given the error, I think your server is not built with
>> OpenGL2, despite your intention. Can you check your CMakeCache.txt on
>> the server build to confirm?
>>
>> Utkarsh
>>
>> _______________________________________________
>> Powered by Caution-Caution-www.kitware.com
>>
>> Visit other Kitware open-source projects at
>> Caution-Caution-http://www.kitware.com/opensource/opensource.html
>>
>> Please keep messages on-topic and check the ParaView Wiki at:
>> Caution-Caution-http://paraview.org/Wiki/ParaView
>>
>> Search the list archives at:
>>Caution-Caution-http://markmail.org/search/?q=ParaView
>>
>> Follow this link to subscribe/unsubscribe:
>> Caution-Caution-http://public.kitware.com/mailman/listinfo/paraview
>>
>
> _______________________________________________
> Powered by Caution-www.kitware.com
>
> Visit other Kitware open-source projects at
> Caution-http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> Caution-http://paraview.org/Wiki/ParaView
>
> Search the list archives at: Caution-http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> Caution-http://public.kitware.com/mailman/listinfo/paraview
>

From peterdebuchev at gmail.com  Thu Jun  2 01:35:26 2016
From: peterdebuchev at gmail.com (Peter Debuchev)
Date: Thu, 2 Jun 2016 07:35:26 +0200
Subject: [Paraview] basics of paraview client server programming
In-Reply-To: <CAAUk9C4i5x3UF0bYC0FUVpJtR6LUrrS00qnN_dJi2CXFOJo_mg@mail.gmail.com>
References: <CAAUk9C4i5x3UF0bYC0FUVpJtR6LUrrS00qnN_dJi2CXFOJo_mg@mail.gmail.com>
Message-ID: <CAAUk9C6YsFEt=b=RWMwGS3WfUO+iGFXs5NEc3RB0L9digST8=A@mail.gmail.com>

Is any introduction available, how vtkSMServerManager, vtkSMSessions,
vtkProxies etc. are set up to interact with a pvserver or with a custom
server application?
I am not talking about short demos that show how to create and display a
sphere using pvpython. What I am looking for is a book chapter or similar
explaining the principles behind vtkSMSessions, vtkProcies etc.

Does anybody remember, which of the VTK or ITK or Paraview books included
such chapters?

Peter

2016-05-29 19:09 GMT+02:00 Peter Debuchev <peterdebuchev at gmail.com>:

> Dear Paraview programmers,
> I am looking for some information about the basic principles of Paraviews
> client-server model, the setup of client proxies and the communication
> design.
>
> I think that I have seen a chapter with a short introduction on these
> topics some years ago. It was in one of the VTK books or in the Paraview
> User's Guide. Now I cannot find this chapter again. Has it been removed in
> the latest edition of these books? Or is it described in a different book
> which I don't remember?
>
> Peter
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160602/8f745366/attachment.html>

From ellonpaiva at gmail.com  Thu Jun  2 05:19:49 2016
From: ellonpaiva at gmail.com (Ellon Paiva)
Date: Thu, 2 Jun 2016 11:19:49 +0200
Subject: [Paraview] basics of paraview client server programming
In-Reply-To: <CAAUk9C6YsFEt=b=RWMwGS3WfUO+iGFXs5NEc3RB0L9digST8=A@mail.gmail.com>
References: <CAAUk9C4i5x3UF0bYC0FUVpJtR6LUrrS00qnN_dJi2CXFOJo_mg@mail.gmail.com>
 <CAAUk9C6YsFEt=b=RWMwGS3WfUO+iGFXs5NEc3RB0L9digST8=A@mail.gmail.com>
Message-ID: <574FFA35.5040701@gmail.com>

+1 for that. I'm very interested to know if there's such book or document.

When I started developing a plug-in for ParaView I found this 
presentation 
<http://www.paraview.org/Wiki/images/a/a1/ParaViewVis08_CustomizingParaView.ppt> 
almost by accident. Maybe it can help you. Apparently it was used in a 
conference/workshop (VIS08?) to describe briefly the proxy system, and 
refers to the "Paraview Guide, Version 3, section 18.6, and chapter 19 
for details (see slide 30). Unfortunately the version 3 of the Guide I 
couldn't find.

Ellon

On 06/02/2016 07:35 AM, Peter Debuchev wrote:
> Is any introduction available, how vtkSMServerManager, vtkSMSessions, 
> vtkProxies etc. are set up to interact with a pvserver or with a 
> custom server application?
> I am not talking about short demos that show how to create and display 
> a sphere using pvpython. What I am looking for is a book chapter or 
> similar explaining the principles behind vtkSMSessions, vtkProcies etc.
>
> Does anybody remember, which of the VTK or ITK or Paraview books 
> included such chapters?
>
> Peter
>
> 2016-05-29 19:09 GMT+02:00 Peter Debuchev <peterdebuchev at gmail.com 
> <mailto:peterdebuchev at gmail.com>>:
>
>     Dear Paraview programmers,
>     I am looking for some information about the basic principles of
>     Paraviews client-server model, the setup of client proxies and the
>     communication design.
>
>     I think that I have seen a chapter with a short introduction on
>     these topics some years ago. It was in one of the VTK books or in
>     the Paraview User's Guide. Now I cannot find this chapter again.
>     Has it been removed in the latest edition of these books? Or is it
>     described in a different book which I don't remember?
>
>     Peter
>
>
>
>
> _______________________________________________
> 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/20160602/d5d1eef5/attachment.html>

From richard.c.angelini.civ at mail.mil  Thu Jun  2 07:59:37 2016
From: richard.c.angelini.civ at mail.mil (Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US))
Date: Thu, 2 Jun 2016 11:59:37 +0000
Subject: [Paraview] [Non-DoD Source] Re: 5.0.1/Exodus Reader
In-Reply-To: <CADHSJjDU=Hhwi2Y=ah=rzRRiF1Tuj3B4xz32FE_YvJVdNqFDLQ@mail.gmail.com>
References: <D36E056D.2B768%Richard.C.Angelini.CIV@mail.mil>
 <CADHSJjDuw66ZuMxAEOUfAa8ssre_Fb8o=BRwJLg7RZES1WaM0A@mail.gmail.com>
 <D36E09B8.2B77E%Richard.C.Angelini.CIV@mail.mil>
 <CADHSJjCWs9OxvfvdGcdb30Y41OP7=pahxePxbA_8zvLzPC3=kA@mail.gmail.com>
 <D372F723.2B7B7%Richard.C.Angelini.CIV@mail.mil>
 <D3749AB6.2B8E9%Richard.C.Angelini.CIV@mail.mil>
 <CADHSJjBLab45qdXtg0w_ohqQO9ydcKDUXPEbb38Fix+5X+jkfg@mail.gmail.com>
 <D374B54E.2B923%Richard.C.Angelini.CIV@mail.mil>
 <D374B81D.2B935%Richard.C.Angelini.CIV@mail.mil>
 <CADHSJjDU=Hhwi2Y=ah=rzRRiF1Tuj3B4xz32FE_YvJVdNqFDLQ@mail.gmail.com>
Message-ID: <D37597B4.2B94C%Richard.C.Angelini.CIV@mail.mil>

So there is much more to be done than adding

-DPARAVIEW_RENDERING_BACKEND:STRING=OpenGL2
-DVTK_RENDERING_BACKEND:STRING="OpenGL2"



to the cmake flags?
________________________________
Rick Angelini
USArmy Research Laboratory
CISD/HPC Architectures Team
Phone:  410-278-6266




-----Original Message-----
From: Utkarsh Ayachit <utkarsh.ayachit at kitware.com>
Date: Wednesday, June 1, 2016 at 4:28 PM
To: Rick Angelini <Richard.C.Angelini.CIV at mail.mil>, Chuck Atkins
<chuck.atkins at kitware.com>
Cc: ParaView <paraview at paraview.org>
Subject: Re: [Paraview] [Non-DoD Source] Re: 5.0.1/Exodus Reader

All active links contained in this email were disabled.  Please verify the
identity of the sender, and confirm the authenticity of all links
contained within the message prior to copying and pasting the address to a
Web browser.  




----

Rick,

The superbuild isn't updated yet to build newer Mesa. Mesa now needs
LLVM etc and hence it's a little tricky. I believe Chuck is working on
getting that working. In the mean time, here's a docker file we use to
build mesa verions:

Caution-https://gitlab.kitware.com/paraview/mesa-builds/tree/master

That will show what options to use to build mesa appropriately.

Utkarsh


On Wed, Jun 1, 2016 at 4:06 PM, Angelini, Richard C (Rick) CIV USARMY
RDECOM ARL (US) <richard.c.angelini.civ at mail.mil> wrote:
> Is there an issue in the SuperBuild?   I just did a quick look through
>the
> Superbuild source, and it looks like the file version.cmake is wanting to
> use MesaLib-7.11.2 ?..
>
>
> 59  $ git pull
> Already up-to-date.
>
>
> 60 $ grep -i mesa versions.cmake
>   add_revision(mesa
>     URL 
>"Caution-http://www.paraview.org/files/dependencies/MesaLib-7.6.1.tar.gz"
>   add_revision(mesa
>     URL 
>"Caution-http://paraview.org/files/dependencies/MesaLib-7.11.2.tar.gz"
> # We stick with 7.11.2 for Mesa version for now. Newer mesa doesn't seem
>to
> add_revision(osmesa
>     URL 
>"Caution-http://paraview.org/files/dependencies/MesaLib-7.11.2.tar.gz"
>
>
>
> ________________________________
> Rick Angelini
> USArmy Research Laboratory
> CISD/HPC Architectures Team
> Phone:  410-278-6266
>
>
>
>
> -----Original Message-----
> From: ParaView <paraview-bounces at paraview.org> on behalf of Rick Angelini
> <Richard.C.Angelini.CIV at mail.mil>
> Date: Wednesday, June 1, 2016 at 3:59 PM
> To: Utkarsh Ayachit <utkarsh.ayachit at kitware.com>
> Cc: ParaView <paraview at paraview.org>
> Subject: Re: [Paraview] [Non-DoD Source] Re: 5.0.1/Exodus Reader
>
> All active links contained in this email were disabled.  Please verify
>the
> identity of the sender, and confirm the authenticity of all links
> contained within the message prior to copying and pasting the address to
>a
> Web browser.
>
>
>
>
> ----
>
> DOH!  The render threshold values were set differently on the Mac and
> Linux systems.   As soon as I forced the Mac to use distributed
>rendering,
> it failed with the same error messages.    So do we have a build issue on
> the HPC-side?      We have rebuilt with OpenGL2 enabled, but it seems
>like
> it?s not picking up the correct Mesa libs????    Presumably we?re using
> the Superbuild and it should be building using the Mesa that?s part of
>the
> Superbuild????
>
> ERROR: In
> 
>/usr/people/joeh/PV/Build_5.0.1_osmesa/paraview/src/paraview/VTK/Rendering
>/
> OpenGL2/vtkOpenGLRenderWindow.cxx, line 587
> vtkOSOpenGLRenderWindow (0x1487a00): GL version 2.1 with the gpu_shader4
> extension is not supported by your graphics driver but is required for
>the
> new OpenGL rendering backend. Please update your OpenGL driver. If you
>are
> using Mesa please make sure you have version 10.6.5 or later and make
>sure
> your driver in Mesa supports OpenGL 3.2.
>
>
> ERROR: In
> 
>/Users/kitware/buildbot-slave/paraview-bigmac-osx-shared-release_opengl2_o
>s
> 
>x10_7_qt4_superbuild/build/paraview/src/paraview/ParaViewCore/ServerManage
>r
> /Core/vtkSMSessionClient.cxx, line 821
> vtkSMSessionClient (0x7fda8344f1a0): Server failed to gather information.
>
>
>
>
> ________________________________
> Rick Angelini
> USArmy Research Laboratory
> CISD/HPC Architectures Team
> Phone:  410-278-6266
>
>
>
>
> -----Original Message-----
> From: Utkarsh Ayachit <utkarsh.ayachit at kitware.com>
> Date: Wednesday, June 1, 2016 at 3:48 PM
> To: Rick Angelini <Richard.C.Angelini.CIV at mail.mil>
> Cc: ParaView <paraview at paraview.org>
> Subject: Re: [Paraview] [Non-DoD Source] Re: 5.0.1/Exodus Reader
>
> Rick,
>
> Are you by any change using local rendering on your Mac and remote
> rendering on your linux client box?
>
> Utkarsh
>
> On Wed, Jun 1, 2016 at 2:02 PM, Angelini, Richard C (Rick) CIV USARMY
> RDECOM ARL (US) <richard.c.angelini.civ at mail.mil> wrote:
>> So, we are continuing to have issues with 5.0.1 and OpenGL2.      I have
>> recompiled the server-side to use OpenGL2, and it works fine if when I
>>run
>> ParaView 5.0.1 from my Mac.     However, if I run ParaView 5.0.1 from my
>> Linux box,  I?m still getting failures.   Looks like 5.0.1 on my Linux
>>box
>> (RHEL6) is also built with OpenGL2, but there are apparently additional
>> issues?????     Here?s some of the output from the error log on the
>>SERVER
>> side.    What?s generating these GL_Version info messages?      I?m
>>using
>> the same exact server-side job launching whether I?m running the client
>>on
>> my Mac or Linux machine - so it would seem that maybe something?s wrong
>>on
>> the Linux client?????
>>
>>
>> /opt/cray/alps/5.2.4-2.0502.9822.32.1.ari/bin/aprun
>> /usr/cta/DAAC/paraview/5.0.1_osmesa/bin/pvserver
>> aprun -B pvserver --use-offscreen-rendering -rc -ch=excalibur09-int
>> -sp=4459 --connect-id=40460
>> Connecting to client (reverse connection requested)...
>> Connection Caution-Caution-url: csrc://excalibur09-int:4459
>> Client connected.
>> GL_Version: 2.1 Mesa 7.11.2
>> GL_Version: 2.1 Mesa 7.11.2
>> GL_Version: 2.1 Mesa 7.11.2
>> GL_Version: 2.1 Mesa 7.11.2
>> GL_Version: 2.1 Mesa 7.11.2
>> GL_Version: 2.1 Mesa 7.11.2
>> GL_Version: 2.1 Mesa 7.11.2
>> GL_Version: 2.1 Mesa 7.11.2
>> GL_Version: 2.1 Mesa 7.11.2
>> GL_Version: 2.1 Mesa 7.11.2
>> GL_Version: 2.1 Mesa 7.11.2
>> GL_Version: 2.1 Mesa 7.11.2
>> ERROR: In
>>
>>/usr/people/joeh/PV/Build_5.0.1_osmesa/paraview/src/paraview/VTK/Renderin
>>g
>>/
>> OpenGL2/vtkOpenGLRenderWindow.cxx, line 587
>> vtkOSOpenGLRenderWindow (0x147ab50): GL version 2.1 with the gpu_shader4
>> extension is not supported by your graphics driver but is required for
>>the
>> new OpenGL rendering backend. Please update your OpenGL driver. If you
>>are
>> using Mesa please make sure you have version 10.6.5 or later and make
>>sure
>> your driver in Mesa supports OpenGL 3.2.
>>
>>
>>
>>
>> ________________________________
>> Rick Angelini
>> USArmy Research Laboratory
>> CISD/HPC Architectures Team
>> Phone:  410-278-6266
>>
>>
>>
>>
>> -----Original Message-----
>> From: ParaView <paraview-bounces at paraview.org> on behalf of Rick
>>Angelini
>> <Richard.C.Angelini.CIV at mail.mil>
>> Date: Tuesday, May 31, 2016 at 8:09 AM
>> To: Utkarsh Ayachit <utkarsh.ayachit at kitware.com>
>> Cc: ParaView <paraview at paraview.org>
>> Subject: Re: [Paraview] [Non-DoD Source] Re:  5.0.1/Exodus Reader
>>
>> All active links contained in this email were disabled.  Please verify
>>the
>> identity of the sender, and confirm the authenticity of all links
>> contained within the message prior to copying and pasting the address to
>>a
>> Web browser.
>>
>>
>>
>>
>> ----
>>
>> Utkarsh - thanks for info.    Recompiling the server-side with OpenGL2
>> resolved the problem!
>>
>>
>> ________________________________
>> Rick Angelini
>> USArmy Research Laboratory
>> CISD/HPC Architectures Team
>> Phone:  410-278-6266
>>
>>
>>
>>
>> -----Original Message-----
>> From: Utkarsh Ayachit <utkarsh.ayachit at kitware.com>
>> Date: Friday, May 27, 2016 at 2:37 PM
>> To: Rick Angelini <Richard.C.Angelini.CIV at mail.mil>
>> Cc: ParaView <paraview at paraview.org>
>> Subject: Re: [Non-DoD Source] Re: [Paraview] 5.0.1/Exodus Reader
>>
>>> Yep - we built the HPC-side with ?OpenGL2? ? so does that mean that the
>>> pre-built Mac/Linux binaries were both built with OpenGL?    Is there
>>>some
>>> way to check to see which OpenGL the client was built with?
>>
>> The binaries distributed by paraview.org are indeed OpenGL2. The title
>> bar for ParaView 5.0.1 says "(Legacy Rendering Backend)" when using
>> "OpenGL". Given the error, I think your server is not built with
>> OpenGL2, despite your intention. Can you check your CMakeCache.txt on
>> the server build to confirm?
>>
>> Utkarsh
>>
>> _______________________________________________
>> Powered by Caution-Caution-Caution-www.kitware.com
>>
>> Visit other Kitware open-source projects at
>> 
>>Caution-Caution-Caution-http://www.kitware.com/opensource/opensource.html
>>
>> Please keep messages on-topic and check the ParaView Wiki at:
>> Caution-Caution-Caution-http://paraview.org/Wiki/ParaView
>>
>> Search the list archives at:
>>Caution-Caution-Caution-http://markmail.org/search/?q=ParaView
>>
>> Follow this link to subscribe/unsubscribe:
>> 
>>Caution-Caution-Caution-http://public.kitware.com/mailman/listinfo/paravi
>>ew
>>
>
> _______________________________________________
> Powered by Caution-Caution-www.kitware.com
>
> Visit other Kitware open-source projects at
> Caution-Caution-http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> Caution-Caution-http://paraview.org/Wiki/ParaView
>
> Search the list archives at:
>Caution-Caution-http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> Caution-Caution-http://public.kitware.com/mailman/listinfo/paraview
>


From utkarsh.ayachit at kitware.com  Thu Jun  2 08:37:04 2016
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Thu, 2 Jun 2016 08:37:04 -0400
Subject: [Paraview] [Non-DoD Source] Re: 5.0.1/Exodus Reader
In-Reply-To: <D37597B4.2B94C%Richard.C.Angelini.CIV@mail.mil>
References: <D36E056D.2B768%Richard.C.Angelini.CIV@mail.mil>
 <CADHSJjDuw66ZuMxAEOUfAa8ssre_Fb8o=BRwJLg7RZES1WaM0A@mail.gmail.com>
 <D36E09B8.2B77E%Richard.C.Angelini.CIV@mail.mil>
 <CADHSJjCWs9OxvfvdGcdb30Y41OP7=pahxePxbA_8zvLzPC3=kA@mail.gmail.com>
 <D372F723.2B7B7%Richard.C.Angelini.CIV@mail.mil>
 <D3749AB6.2B8E9%Richard.C.Angelini.CIV@mail.mil>
 <CADHSJjBLab45qdXtg0w_ohqQO9ydcKDUXPEbb38Fix+5X+jkfg@mail.gmail.com>
 <D374B54E.2B923%Richard.C.Angelini.CIV@mail.mil>
 <D374B81D.2B935%Richard.C.Angelini.CIV@mail.mil>
 <CADHSJjDU=Hhwi2Y=ah=rzRRiF1Tuj3B4xz32FE_YvJVdNqFDLQ@mail.gmail.com>
 <D37597B4.2B94C%Richard.C.Angelini.CIV@mail.mil>
Message-ID: <CADHSJjAGTRuN=1kdmaR3ZB_OcLd1-qZET+5JE2G1jtNyd5_Vsg@mail.gmail.com>

> So there is much more to be done than adding
> -DPARAVIEW_RENDERING_BACKEND:STRING=OpenGL2
> -DVTK_RENDERING_BACKEND:STRING="OpenGL2"
> to the cmake flags?

As far as ParaView is concerned, no there's not much more to it.
However if your OpenGL implementation doesn't support OpenGL 3.2
(released in 2009), then alas there's more work to get ParaView
working which could include building a newer version of Mesa. Not sure
if you have seen this blog [1], but that talks about how I got Mesa to
build with appropriate OpenGL renderer enabled. Things have gotten a
little better since then and the Docker script encapsulates that. The
moral of the story is get latest Mesa version and build it with
LLVM/Gallum support.

Utkarsh

[1] https://blog.kitware.com/messing-with-mesa-for-paraview-5-0vtk-7-0/

From utkarsh.ayachit at kitware.com  Thu Jun  2 08:43:42 2016
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Thu, 2 Jun 2016 08:43:42 -0400
Subject: [Paraview] basics of paraview client server programming
In-Reply-To: <574FFA35.5040701@gmail.com>
References: <CAAUk9C4i5x3UF0bYC0FUVpJtR6LUrrS00qnN_dJi2CXFOJo_mg@mail.gmail.com>
 <CAAUk9C6YsFEt=b=RWMwGS3WfUO+iGFXs5NEc3RB0L9digST8=A@mail.gmail.com>
 <574FFA35.5040701@gmail.com>
Message-ID: <CADHSJjCX0VagGF-8Tkj=Ro8mbSsEFkTWSkRR0xW3T3aEY9fifg@mail.gmail.com>

Alas, there's nothing up-to-date. I've been meaning to write a blog
series covering various aspect of ParaView internals, but it's hard to
find some downtime to get that going. I'll try to see if I can find
the old PDF for the ParaView Guide v3 and share the old chapter
(although obsolete, but basic design may still be relevant). The
ParaView developers Wiki
(http://www.paraview.org/ParaView/index.php/Main_Page) has a few
articles that we wrote with coming up with the design for some of the
core components. The implementations generally differ slightly from
the design and may have names/APIs changed since, but nonetheless may
be helpful in understanding how things came about. Specifically,

[1] http://www.paraview.org/ParaView/index.php/ServerManager_2.0
[2] http://www.paraview.org/ParaView/index.php/ProcessModule_2.0
[3] http://www.paraview.org/ParaView/index.php/Views_And_Representations
[4] http://www.paraview.org/ParaView/images/2/24/ParaViewCollaborationChanges.pdf

Utkarsh

On Thu, Jun 2, 2016 at 5:19 AM, Ellon Paiva <ellonpaiva at gmail.com> wrote:
> +1 for that. I'm very interested to know if there's such book or document.
>
> When I started developing a plug-in for ParaView I found this presentation
> almost by accident. Maybe it can help you. Apparently it was used in a
> conference/workshop (VIS08?) to describe briefly the proxy system, and
> refers to the "Paraview Guide, Version 3, section 18.6, and chapter 19 for
> details (see slide 30). Unfortunately the version 3 of the Guide I couldn't
> find.
>
> Ellon
>
>
> On 06/02/2016 07:35 AM, Peter Debuchev wrote:
>
> Is any introduction available, how vtkSMServerManager, vtkSMSessions,
> vtkProxies etc. are set up to interact with a pvserver or with a custom
> server application?
> I am not talking about short demos that show how to create and display a
> sphere using pvpython. What I am looking for is a book chapter or similar
> explaining the principles behind vtkSMSessions, vtkProcies etc.
>
> Does anybody remember, which of the VTK or ITK or Paraview books included
> such chapters?
>
> Peter
>
> 2016-05-29 19:09 GMT+02:00 Peter Debuchev <peterdebuchev at gmail.com>:
>>
>> Dear Paraview programmers,
>> I am looking for some information about the basic principles of Paraviews
>> client-server model, the setup of client proxies and the communication
>> design.
>>
>> I think that I have seen a chapter with a short introduction on these
>> topics some years ago. It was in one of the VTK books or in the Paraview
>> User's Guide. Now I cannot find this chapter again. Has it been removed in
>> the latest edition of these books? Or is it described in a different book
>> which I don't remember?
>>
>> Peter
>
>
>
>
> _______________________________________________
> 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 richard.c.angelini.civ at mail.mil  Thu Jun  2 08:48:17 2016
From: richard.c.angelini.civ at mail.mil (Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US))
Date: Thu, 2 Jun 2016 12:48:17 +0000
Subject: [Paraview] [Non-DoD Source] Re: 5.0.1/Exodus Reader
In-Reply-To: <CADHSJjAGTRuN=1kdmaR3ZB_OcLd1-qZET+5JE2G1jtNyd5_Vsg@mail.gmail.com>
References: <D36E056D.2B768%Richard.C.Angelini.CIV@mail.mil>
 <CADHSJjDuw66ZuMxAEOUfAa8ssre_Fb8o=BRwJLg7RZES1WaM0A@mail.gmail.com>
 <D36E09B8.2B77E%Richard.C.Angelini.CIV@mail.mil>
 <CADHSJjCWs9OxvfvdGcdb30Y41OP7=pahxePxbA_8zvLzPC3=kA@mail.gmail.com>
 <D372F723.2B7B7%Richard.C.Angelini.CIV@mail.mil>
 <D3749AB6.2B8E9%Richard.C.Angelini.CIV@mail.mil>
 <CADHSJjBLab45qdXtg0w_ohqQO9ydcKDUXPEbb38Fix+5X+jkfg@mail.gmail.com>
 <D374B54E.2B923%Richard.C.Angelini.CIV@mail.mil>
 <D374B81D.2B935%Richard.C.Angelini.CIV@mail.mil>
 <CADHSJjDU=Hhwi2Y=ah=rzRRiF1Tuj3B4xz32FE_YvJVdNqFDLQ@mail.gmail.com>
 <D37597B4.2B94C%Richard.C.Angelini.CIV@mail.mil>
 <CADHSJjAGTRuN=1kdmaR3ZB_OcLd1-qZET+5JE2G1jtNyd5_Vsg@mail.gmail.com>
Message-ID: <D375A1F9.2B956%Richard.C.Angelini.CIV@mail.mil>

Our current issues seem to be related to our osmesa build for the HPC_side
servers.       The Superbuild is building 7.11.2 - you are suggesting that
we need to *manually* build a different version of Mesa and somehow link
in that new version of Mesa in to the Superbuild?     We rely exclusively
on the Superbuild for compiling ParaView across 20 different HPC systems -
so stepping outside of the super build paradigm isn?t necessarily obvious
to me!    8-)





________________________________
Rick Angelini
USArmy Research Laboratory
CISD/HPC Architectures Team
Phone:  410-278-6266




-----Original Message-----
From: Utkarsh Ayachit <utkarsh.ayachit at kitware.com>
Date: Thursday, June 2, 2016 at 8:37 AM
To: Rick Angelini <Richard.C.Angelini.CIV at mail.mil>
Cc: Chuck Atkins <chuck.atkins at kitware.com>, ParaView
<paraview at paraview.org>
Subject: Re: [Paraview] [Non-DoD Source] Re: 5.0.1/Exodus Reader

All active links contained in this email were disabled.  Please verify the
identity of the sender, and confirm the authenticity of all links
contained within the message prior to copying and pasting the address to a
Web browser.  




----

> So there is much more to be done than adding
> -DPARAVIEW_RENDERING_BACKEND:STRING=OpenGL2
> -DVTK_RENDERING_BACKEND:STRING="OpenGL2"
> to the cmake flags?

As far as ParaView is concerned, no there's not much more to it.
However if your OpenGL implementation doesn't support OpenGL 3.2
(released in 2009), then alas there's more work to get ParaView
working which could include building a newer version of Mesa. Not sure
if you have seen this blog [1], but that talks about how I got Mesa to
build with appropriate OpenGL renderer enabled. Things have gotten a
little better since then and the Docker script encapsulates that. The
moral of the story is get latest Mesa version and build it with
LLVM/Gallum support.

Utkarsh

[1] 
Caution-https://blog.kitware.com/messing-with-mesa-for-paraview-5-0vtk-7-0/


From cfztol at hotmail.com  Thu Jun  2 09:13:20 2016
From: cfztol at hotmail.com (Christian Felter)
Date: Thu, 2 Jun 2016 13:13:20 +0000
Subject: [Paraview] pvserver 5.0.1 crash on localhost
Message-ID: <VI1PR06MB1101B2781F5FA2D5494C79B9C7580@VI1PR06MB1101.eurprd06.prod.outlook.com>

Hello,


I running a fresh install of kubuntu 16.04 xenial xerus on a desktop computer with 2 x 14 cpu's. I've downloaded ParaView-5.0.1-Qt4-OpenGL2-MPI-Linux-64bit binary release (from paraview.org), and I use the binaries in the "bin" subfolder.


When I run in client-server mode on the computer, i.e. using localhost and socket 11111, I experience "random" crashes of pvserver. I start servers like this:


mpirun.mpich -np 14 <path to>/ParaView-5.0.1-Qt4-OpenGL2-MPI-Linux-64bit/bin/pvserver --use-offscreen-rendering


Then in the client many things are working. However, when I use the Contour-filter after playing a few time step (from an ExodusII-file) a small pop-up appears saying "The server side has disconnected". In the terminal I can see different errors. Sometimes it says:

Bus error (signal 7)


other times is it something with:


Unsupported cell type


(I think it comes from void vtkGenericCell::SetCellType(int cellType) )


Does anybody know how to fix these issues? I would be really happy if someone knows a solution.


Christian

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

From utkarsh.ayachit at kitware.com  Thu Jun  2 09:47:47 2016
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Thu, 2 Jun 2016 09:47:47 -0400
Subject: [Paraview] [Non-DoD Source] Re: 5.0.1/Exodus Reader
In-Reply-To: <D375A1F9.2B956%Richard.C.Angelini.CIV@mail.mil>
References: <D36E056D.2B768%Richard.C.Angelini.CIV@mail.mil>
 <CADHSJjDuw66ZuMxAEOUfAa8ssre_Fb8o=BRwJLg7RZES1WaM0A@mail.gmail.com>
 <D36E09B8.2B77E%Richard.C.Angelini.CIV@mail.mil>
 <CADHSJjCWs9OxvfvdGcdb30Y41OP7=pahxePxbA_8zvLzPC3=kA@mail.gmail.com>
 <D372F723.2B7B7%Richard.C.Angelini.CIV@mail.mil>
 <D3749AB6.2B8E9%Richard.C.Angelini.CIV@mail.mil>
 <CADHSJjBLab45qdXtg0w_ohqQO9ydcKDUXPEbb38Fix+5X+jkfg@mail.gmail.com>
 <D374B54E.2B923%Richard.C.Angelini.CIV@mail.mil>
 <D374B81D.2B935%Richard.C.Angelini.CIV@mail.mil>
 <CADHSJjDU=Hhwi2Y=ah=rzRRiF1Tuj3B4xz32FE_YvJVdNqFDLQ@mail.gmail.com>
 <D37597B4.2B94C%Richard.C.Angelini.CIV@mail.mil>
 <CADHSJjAGTRuN=1kdmaR3ZB_OcLd1-qZET+5JE2G1jtNyd5_Vsg@mail.gmail.com>
 <D375A1F9.2B956%Richard.C.Angelini.CIV@mail.mil>
Message-ID: <CADHSJjDcbLOchBqsQ50fRxs+Ei5XnjidCu=Zq7V8DK1dacRJgQ@mail.gmail.com>

Ah okay. Give me a few days to sort it out. The end goal is indeed to
have superbuild build the right versions of Mesa. Do you only  care
about OSMesa or also Mesa with X support?

Utkarsh




On Thu, Jun 2, 2016 at 8:48 AM, Angelini, Richard C (Rick) CIV USARMY
RDECOM ARL (US) <richard.c.angelini.civ at mail.mil> wrote:
> Our current issues seem to be related to our osmesa build for the HPC_side
> servers.       The Superbuild is building 7.11.2 - you are suggesting that
> we need to *manually* build a different version of Mesa and somehow link
> in that new version of Mesa in to the Superbuild?     We rely exclusively
> on the Superbuild for compiling ParaView across 20 different HPC systems -
> so stepping outside of the super build paradigm isn?t necessarily obvious
> to me!    8-)
>
>
>
>
>
> ________________________________
> Rick Angelini
> USArmy Research Laboratory
> CISD/HPC Architectures Team
> Phone:  410-278-6266
>
>
>
>
> -----Original Message-----
> From: Utkarsh Ayachit <utkarsh.ayachit at kitware.com>
> Date: Thursday, June 2, 2016 at 8:37 AM
> To: Rick Angelini <Richard.C.Angelini.CIV at mail.mil>
> Cc: Chuck Atkins <chuck.atkins at kitware.com>, ParaView
> <paraview at paraview.org>
> Subject: Re: [Paraview] [Non-DoD Source] Re: 5.0.1/Exodus Reader
>
> All active links contained in this email were disabled.  Please verify the
> identity of the sender, and confirm the authenticity of all links
> contained within the message prior to copying and pasting the address to a
> Web browser.
>
>
>
>
> ----
>
>> So there is much more to be done than adding
>> -DPARAVIEW_RENDERING_BACKEND:STRING=OpenGL2
>> -DVTK_RENDERING_BACKEND:STRING="OpenGL2"
>> to the cmake flags?
>
> As far as ParaView is concerned, no there's not much more to it.
> However if your OpenGL implementation doesn't support OpenGL 3.2
> (released in 2009), then alas there's more work to get ParaView
> working which could include building a newer version of Mesa. Not sure
> if you have seen this blog [1], but that talks about how I got Mesa to
> build with appropriate OpenGL renderer enabled. Things have gotten a
> little better since then and the Docker script encapsulates that. The
> moral of the story is get latest Mesa version and build it with
> LLVM/Gallum support.
>
> Utkarsh
>
> [1]
> Caution-https://blog.kitware.com/messing-with-mesa-for-paraview-5-0vtk-7-0/
>

From david.larsson at sth.kth.se  Thu Jun  2 11:26:37 2016
From: david.larsson at sth.kth.se (David Larsson)
Date: Thu, 2 Jun 2016 15:26:37 +0000
Subject: [Paraview] visualize traced particles
Message-ID: <1464881196894.57602@sth.kth.se>

Dear Paraview community,


in an external program, I've traced particles inside a 3D(+time) flow field and extracted each particles spatial position (x,y,z) in time.


I have this data saved in an ascii-output where each particle position (with time) is simply written out.


Now to my question: is there any convenient way of visualizing these pathlines in paraview? Can I load and look at that kind of data in a direct way? Or can you even visualize how the particle progresses in space over time?


Thanks for your help.


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

From richard.c.angelini.civ at mail.mil  Thu Jun  2 12:45:27 2016
From: richard.c.angelini.civ at mail.mil (Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US))
Date: Thu, 2 Jun 2016 16:45:27 +0000
Subject: [Paraview] [Non-DoD Source] Re: 5.0.1/Exodus Reader
In-Reply-To: <CADHSJjDcbLOchBqsQ50fRxs+Ei5XnjidCu=Zq7V8DK1dacRJgQ@mail.gmail.com>
References: <D36E056D.2B768%Richard.C.Angelini.CIV@mail.mil>
 <CADHSJjDuw66ZuMxAEOUfAa8ssre_Fb8o=BRwJLg7RZES1WaM0A@mail.gmail.com>
 <D36E09B8.2B77E%Richard.C.Angelini.CIV@mail.mil>
 <CADHSJjCWs9OxvfvdGcdb30Y41OP7=pahxePxbA_8zvLzPC3=kA@mail.gmail.com>
 <D372F723.2B7B7%Richard.C.Angelini.CIV@mail.mil>
 <D3749AB6.2B8E9%Richard.C.Angelini.CIV@mail.mil>
 <CADHSJjBLab45qdXtg0w_ohqQO9ydcKDUXPEbb38Fix+5X+jkfg@mail.gmail.com>
 <D374B54E.2B923%Richard.C.Angelini.CIV@mail.mil>
 <D374B81D.2B935%Richard.C.Angelini.CIV@mail.mil>
 <CADHSJjDU=Hhwi2Y=ah=rzRRiF1Tuj3B4xz32FE_YvJVdNqFDLQ@mail.gmail.com>
 <D37597B4.2B94C%Richard.C.Angelini.CIV@mail.mil>
 <CADHSJjAGTRuN=1kdmaR3ZB_OcLd1-qZET+5JE2G1jtNyd5_Vsg@mail.gmail.com>
 <D375A1F9.2B956%Richard.C.Angelini.CIV@mail.mil>
 <CADHSJjDcbLOchBqsQ50fRxs+Ei5XnjidCu=Zq7V8DK1dacRJgQ@mail.gmail.com>
Message-ID: <345817C8A61EA841AAE0120EC1514D95B61342CC@UMECHPA68.easf.csd.disa.mil>

Our *immediate* concern is OSMesa - but we'll probably eventually want to address Mesa w/X support .....

-----Original Message-----
From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] 
Sent: Thursday, June 02, 2016 9:48 AM
To: Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US) <richard.c.angelini.civ at mail.mil>
Cc: Chuck Atkins <chuck.atkins at kitware.com>; ParaView <paraview at paraview.org>
Subject: Re: [Paraview] [Non-DoD Source] Re: 5.0.1/Exodus Reader

Ah okay. Give me a few days to sort it out. The end goal is indeed to have superbuild build the right versions of Mesa. Do you only  care about OSMesa or also Mesa with X support?

Utkarsh




On Thu, Jun 2, 2016 at 8:48 AM, Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US) <richard.c.angelini.civ at mail.mil> wrote:
> Our current issues seem to be related to our osmesa build for the HPC_side
> servers.       The Superbuild is building 7.11.2 - you are suggesting that
> we need to *manually* build a different version of Mesa and somehow link
> in that new version of Mesa in to the Superbuild?     We rely exclusively
> on the Superbuild for compiling ParaView across 20 different HPC 
> systems - so stepping outside of the super build paradigm isn?t necessarily obvious
> to me!    8-)
>
>
>
>
>
> ________________________________
> Rick Angelini
> USArmy Research Laboratory
> CISD/HPC Architectures Team
> Phone:  410-278-6266
>
>
>
>
> -----Original Message-----
> From: Utkarsh Ayachit <utkarsh.ayachit at kitware.com>
> Date: Thursday, June 2, 2016 at 8:37 AM
> To: Rick Angelini <Richard.C.Angelini.CIV at mail.mil>
> Cc: Chuck Atkins <chuck.atkins at kitware.com>, ParaView 
> <paraview at paraview.org>
> Subject: Re: [Paraview] [Non-DoD Source] Re: 5.0.1/Exodus Reader
>
> All active links contained in this email were disabled.  Please verify 
> the identity of the sender, and confirm the authenticity of all links 
> contained within the message prior to copying and pasting the address 
> to a Web browser.
>
>
>
>
> ----
>
>> So there is much more to be done than adding
>> -DPARAVIEW_RENDERING_BACKEND:STRING=OpenGL2
>> -DVTK_RENDERING_BACKEND:STRING="OpenGL2"
>> to the cmake flags?
>
> As far as ParaView is concerned, no there's not much more to it.
> However if your OpenGL implementation doesn't support OpenGL 3.2 
> (released in 2009), then alas there's more work to get ParaView 
> working which could include building a newer version of Mesa. Not sure 
> if you have seen this blog [1], but that talks about how I got Mesa to 
> build with appropriate OpenGL renderer enabled. Things have gotten a 
> little better since then and the Docker script encapsulates that. The 
> moral of the story is get latest Mesa version and build it with 
> LLVM/Gallum support.
>
> Utkarsh
>
> [1]
> Caution-https://blog.kitware.com/messing-with-mesa-for-paraview-5-0vtk
> -7-0/
>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 5575 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160602/610c06ef/attachment.bin>

From utkarsh.ayachit at kitware.com  Thu Jun  2 13:18:29 2016
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Thu, 2 Jun 2016 13:18:29 -0400
Subject: [Paraview] [Non-DoD Source] Re: 5.0.1/Exodus Reader
In-Reply-To: <345817C8A61EA841AAE0120EC1514D95B61342CC@UMECHPA68.easf.csd.disa.mil>
References: <D36E056D.2B768%Richard.C.Angelini.CIV@mail.mil>
 <CADHSJjDuw66ZuMxAEOUfAa8ssre_Fb8o=BRwJLg7RZES1WaM0A@mail.gmail.com>
 <D36E09B8.2B77E%Richard.C.Angelini.CIV@mail.mil>
 <CADHSJjCWs9OxvfvdGcdb30Y41OP7=pahxePxbA_8zvLzPC3=kA@mail.gmail.com>
 <D372F723.2B7B7%Richard.C.Angelini.CIV@mail.mil>
 <D3749AB6.2B8E9%Richard.C.Angelini.CIV@mail.mil>
 <CADHSJjBLab45qdXtg0w_ohqQO9ydcKDUXPEbb38Fix+5X+jkfg@mail.gmail.com>
 <D374B54E.2B923%Richard.C.Angelini.CIV@mail.mil>
 <D374B81D.2B935%Richard.C.Angelini.CIV@mail.mil>
 <CADHSJjDU=Hhwi2Y=ah=rzRRiF1Tuj3B4xz32FE_YvJVdNqFDLQ@mail.gmail.com>
 <D37597B4.2B94C%Richard.C.Angelini.CIV@mail.mil>
 <CADHSJjAGTRuN=1kdmaR3ZB_OcLd1-qZET+5JE2G1jtNyd5_Vsg@mail.gmail.com>
 <D375A1F9.2B956%Richard.C.Angelini.CIV@mail.mil>
 <CADHSJjDcbLOchBqsQ50fRxs+Ei5XnjidCu=Zq7V8DK1dacRJgQ@mail.gmail.com>
 <345817C8A61EA841AAE0120EC1514D95B61342CC@UMECHPA68.easf.csd.disa.mil>
Message-ID: <CADHSJjDqy4bw8Boc3z-5AoOipg1Bz5fMetAwuKX44HFV2LvR1A@mail.gmail.com>

Roger that. I will have updates for you early next week (plan to work
on it as soon as I am done with the task at hand).

On Thu, Jun 2, 2016 at 12:45 PM, Angelini, Richard C (Rick) CIV USARMY
RDECOM ARL (US) <richard.c.angelini.civ at mail.mil> wrote:
> Our *immediate* concern is OSMesa - but we'll probably eventually want to address Mesa w/X support .....
>
> -----Original Message-----
> From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com]
> Sent: Thursday, June 02, 2016 9:48 AM
> To: Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US) <richard.c.angelini.civ at mail.mil>
> Cc: Chuck Atkins <chuck.atkins at kitware.com>; ParaView <paraview at paraview.org>
> Subject: Re: [Paraview] [Non-DoD Source] Re: 5.0.1/Exodus Reader
>
> Ah okay. Give me a few days to sort it out. The end goal is indeed to have superbuild build the right versions of Mesa. Do you only  care about OSMesa or also Mesa with X support?
>
> Utkarsh
>
>
>
>
> On Thu, Jun 2, 2016 at 8:48 AM, Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US) <richard.c.angelini.civ at mail.mil> wrote:
>> Our current issues seem to be related to our osmesa build for the HPC_side
>> servers.       The Superbuild is building 7.11.2 - you are suggesting that
>> we need to *manually* build a different version of Mesa and somehow link
>> in that new version of Mesa in to the Superbuild?     We rely exclusively
>> on the Superbuild for compiling ParaView across 20 different HPC
>> systems - so stepping outside of the super build paradigm isn?t necessarily obvious
>> to me!    8-)
>>
>>
>>
>>
>>
>> ________________________________
>> Rick Angelini
>> USArmy Research Laboratory
>> CISD/HPC Architectures Team
>> Phone:  410-278-6266
>>
>>
>>
>>
>> -----Original Message-----
>> From: Utkarsh Ayachit <utkarsh.ayachit at kitware.com>
>> Date: Thursday, June 2, 2016 at 8:37 AM
>> To: Rick Angelini <Richard.C.Angelini.CIV at mail.mil>
>> Cc: Chuck Atkins <chuck.atkins at kitware.com>, ParaView
>> <paraview at paraview.org>
>> Subject: Re: [Paraview] [Non-DoD Source] Re: 5.0.1/Exodus Reader
>>
>> All active links contained in this email were disabled.  Please verify
>> the identity of the sender, and confirm the authenticity of all links
>> contained within the message prior to copying and pasting the address
>> to a Web browser.
>>
>>
>>
>>
>> ----
>>
>>> So there is much more to be done than adding
>>> -DPARAVIEW_RENDERING_BACKEND:STRING=OpenGL2
>>> -DVTK_RENDERING_BACKEND:STRING="OpenGL2"
>>> to the cmake flags?
>>
>> As far as ParaView is concerned, no there's not much more to it.
>> However if your OpenGL implementation doesn't support OpenGL 3.2
>> (released in 2009), then alas there's more work to get ParaView
>> working which could include building a newer version of Mesa. Not sure
>> if you have seen this blog [1], but that talks about how I got Mesa to
>> build with appropriate OpenGL renderer enabled. Things have gotten a
>> little better since then and the Docker script encapsulates that. The
>> moral of the story is get latest Mesa version and build it with
>> LLVM/Gallum support.
>>
>> Utkarsh
>>
>> [1]
>> Caution-https://blog.kitware.com/messing-with-mesa-for-paraview-5-0vtk
>> -7-0/
>>

From richard.c.angelini.civ at mail.mil  Thu Jun  2 13:45:03 2016
From: richard.c.angelini.civ at mail.mil (Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US))
Date: Thu, 2 Jun 2016 17:45:03 +0000
Subject: [Paraview] [Non-DoD Source] Re: 5.0.1/Exodus Reader
In-Reply-To: <CADHSJjDqy4bw8Boc3z-5AoOipg1Bz5fMetAwuKX44HFV2LvR1A@mail.gmail.com>
References: <D36E056D.2B768%Richard.C.Angelini.CIV@mail.mil>
 <CADHSJjDuw66ZuMxAEOUfAa8ssre_Fb8o=BRwJLg7RZES1WaM0A@mail.gmail.com>
 <D36E09B8.2B77E%Richard.C.Angelini.CIV@mail.mil>
 <CADHSJjCWs9OxvfvdGcdb30Y41OP7=pahxePxbA_8zvLzPC3=kA@mail.gmail.com>
 <D372F723.2B7B7%Richard.C.Angelini.CIV@mail.mil>
 <D3749AB6.2B8E9%Richard.C.Angelini.CIV@mail.mil>
 <CADHSJjBLab45qdXtg0w_ohqQO9ydcKDUXPEbb38Fix+5X+jkfg@mail.gmail.com>
 <D374B54E.2B923%Richard.C.Angelini.CIV@mail.mil>
 <D374B81D.2B935%Richard.C.Angelini.CIV@mail.mil>
 <CADHSJjDU=Hhwi2Y=ah=rzRRiF1Tuj3B4xz32FE_YvJVdNqFDLQ@mail.gmail.com>
 <D37597B4.2B94C%Richard.C.Angelini.CIV@mail.mil>
 <CADHSJjAGTRuN=1kdmaR3ZB_OcLd1-qZET+5JE2G1jtNyd5_Vsg@mail.gmail.com>
 <D375A1F9.2B956%Richard.C.Angelini.CIV@mail.mil>
 <CADHSJjDcbLOchBqsQ50fRxs+Ei5XnjidCu=Zq7V8DK1dacRJgQ@mail.gmail.com>
 <345817C8A61EA841AAE0120EC1514D95B61342CC@UMECHPA68.easf.csd.disa.mil>
 <CADHSJjDqy4bw8Boc3z-5AoOipg1Bz5fMetAwuKX44HFV2LvR1A@mail.gmail.com>
Message-ID: <345817C8A61EA841AAE0120EC1514D95B613446F@UMECHPA68.easf.csd.disa.mil>

Utkarsh - thanks - in the mean time, we're going to try to build Mesa 11.1 (?) outside of ParaView and link it in and see how far we can get!   8-)    But it would certainly be cleaner to use the Superbuild when you get that updated with the proper Mesa build!



-----Original Message-----
From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] 
Sent: Thursday, June 02, 2016 1:18 PM
To: Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US) <richard.c.angelini.civ at mail.mil>
Cc: Chuck Atkins <chuck.atkins at kitware.com>; ParaView <paraview at paraview.org>
Subject: Re: [Paraview] [Non-DoD Source] Re: 5.0.1/Exodus Reader

Roger that. I will have updates for you early next week (plan to work on it as soon as I am done with the task at hand).

On Thu, Jun 2, 2016 at 12:45 PM, Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US) <richard.c.angelini.civ at mail.mil> wrote:
> Our *immediate* concern is OSMesa - but we'll probably eventually want to address Mesa w/X support .....
>
> -----Original Message-----
> From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com]
> Sent: Thursday, June 02, 2016 9:48 AM
> To: Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US) 
> <richard.c.angelini.civ at mail.mil>
> Cc: Chuck Atkins <chuck.atkins at kitware.com>; ParaView 
> <paraview at paraview.org>
> Subject: Re: [Paraview] [Non-DoD Source] Re: 5.0.1/Exodus Reader
>
> Ah okay. Give me a few days to sort it out. The end goal is indeed to have superbuild build the right versions of Mesa. Do you only  care about OSMesa or also Mesa with X support?
>
> Utkarsh
>
>
>
>
> On Thu, Jun 2, 2016 at 8:48 AM, Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US) <richard.c.angelini.civ at mail.mil> wrote:
>> Our current issues seem to be related to our osmesa build for the HPC_side
>> servers.       The Superbuild is building 7.11.2 - you are suggesting that
>> we need to *manually* build a different version of Mesa and somehow link
>> in that new version of Mesa in to the Superbuild?     We rely exclusively
>> on the Superbuild for compiling ParaView across 20 different HPC 
>> systems - so stepping outside of the super build paradigm isn?t necessarily obvious
>> to me!    8-)
>>
>>
>>
>>
>>
>> ________________________________
>> Rick Angelini
>> USArmy Research Laboratory
>> CISD/HPC Architectures Team
>> Phone:  410-278-6266
>>
>>
>>
>>
>> -----Original Message-----
>> From: Utkarsh Ayachit <utkarsh.ayachit at kitware.com>
>> Date: Thursday, June 2, 2016 at 8:37 AM
>> To: Rick Angelini <Richard.C.Angelini.CIV at mail.mil>
>> Cc: Chuck Atkins <chuck.atkins at kitware.com>, ParaView 
>> <paraview at paraview.org>
>> Subject: Re: [Paraview] [Non-DoD Source] Re: 5.0.1/Exodus Reader
>>
>> All active links contained in this email were disabled.  Please 
>> verify the identity of the sender, and confirm the authenticity of 
>> all links contained within the message prior to copying and pasting 
>> the address to a Web browser.
>>
>>
>>
>>
>> ----
>>
>>> So there is much more to be done than adding
>>> -DPARAVIEW_RENDERING_BACKEND:STRING=OpenGL2
>>> -DVTK_RENDERING_BACKEND:STRING="OpenGL2"
>>> to the cmake flags?
>>
>> As far as ParaView is concerned, no there's not much more to it.
>> However if your OpenGL implementation doesn't support OpenGL 3.2 
>> (released in 2009), then alas there's more work to get ParaView 
>> working which could include building a newer version of Mesa. Not 
>> sure if you have seen this blog [1], but that talks about how I got 
>> Mesa to build with appropriate OpenGL renderer enabled. Things have 
>> gotten a little better since then and the Docker script encapsulates 
>> that. The moral of the story is get latest Mesa version and build it 
>> with LLVM/Gallum support.
>>
>> Utkarsh
>>
>> [1]
>> Caution-https://blog.kitware.com/messing-with-mesa-for-paraview-5-0vt
>> k
>> -7-0/
>>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 5575 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160602/77e2c3bc/attachment.bin>

From bsangee at vt.edu  Thu Jun  2 14:19:23 2016
From: bsangee at vt.edu (Sangeetha Banavathi Srinivasa)
Date: Thu, 2 Jun 2016 14:19:23 -0400
Subject: [Paraview] Upgrade of GPU drivers
Message-ID: <413FB7C6-E434-4C80-9812-FEA2B0F1A5ED@vt.edu>

Hello,

I wanted to know if ParaView should be recompiled on HPC clusters after upgrading GPU drivers?

Thanks,
Sangeetha

From joseph.g.hennessey2.ctr at mail.mil  Thu Jun  2 15:46:46 2016
From: joseph.g.hennessey2.ctr at mail.mil (Hennessey, Joseph G CTR USARMY RDECOM ARL (US))
Date: Thu, 2 Jun 2016 19:46:46 +0000
Subject: [Paraview] [Non-DoD Source] Re: 5.0.1/Exodus Reader
 (UNCLASSIFIED)
Message-ID: <10A03274360DCF47A6EE78C9952A31CA639745D1@UMECHPA7C.easf.csd.disa.mil>

CLASSIFICATION: UNCLASSIFIED

Utkarsh,

I am running ParaView 5.0.1 connecting to a remote ParaView 5.0.1 server built with osmesa

And I have rebuild osmesa from both
Mesa 11.1.2 and Mesa 11.2.2 using

./configure \
    --disable-xvmc \
    --disable-glx \
    --disable-dri \
    --with-dri-drivers= \
    --with-gallium-drivers=swrast \
    --enable-texture-float \
    --disable-egl \
    --enable-shared \
    --with-egl-platforms= \
    --enable-gallium-osmesa \
    --enable-gallium-llvm=yes \
    --prefix=<install prefix>

And I have tried replacing the library

lib/paraview-5.0/libOSMesa.so.7

with both libOSMesa.so from 11.1.2 and 11.2.2

and they are both still giving the same error

paraview/VTK/Rendering/OpenGL2/vtkOpenGLRenderWindow.cxx line 587 vtkOSOpenGLRenderWindow GL Version 2.1 with the gpu_shader4 extension is not supported by your graphics driver, but is required for the new OpenGL rendering  backend. Please update your OpenGL driver.
If you are using Mesa please make sure you have version 10.6.5 and make sure your  driver support OpenGL 3.2

Any suggestions?

Thanks,

Joe Hennessey

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Joseph G. Hennessey Ph.D., Lockheed Martin Army Research Lab DOD Supercomputing Resource Center
120 Aberdeen Blvd.
Aberdeen Proving Ground, MD 21005
Voice:  410-278-3619
Fax:    410-278-8799
Email:  joseph.g.hennessey2.ctr at mail.mil


-----Original Message-----
From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US)
Sent: Thursday, June 02, 2016 1:45 PM
To: Utkarsh Ayachit <utkarsh.ayachit at kitware.com>
Cc: ParaView <paraview at paraview.org>
Subject: Re: [Paraview] [Non-DoD Source] Re: 5.0.1/Exodus Reader

All active links contained in this email were disabled.  Please verify the identity of the sender, and confirm the authenticity of all links contained within the message prior to copying and pasting the address to a Web browser.  




----

Utkarsh - thanks - in the mean time, we're going to try to build Mesa 11.1 (?) outside of ParaView and link it in and see how far we can get!   8-)    But it would certainly be cleaner to use the Superbuild when you get that updated with the proper Mesa build!



-----Original Message-----
From: Utkarsh Ayachit [Caution-mailto:utkarsh.ayachit at kitware.com]
Sent: Thursday, June 02, 2016 1:18 PM
To: Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US) <richard.c.angelini.civ at mail.mil>
Cc: Chuck Atkins <chuck.atkins at kitware.com>; ParaView <paraview at paraview.org>
Subject: Re: [Paraview] [Non-DoD Source] Re: 5.0.1/Exodus Reader

Roger that. I will have updates for you early next week (plan to work on it as soon as I am done with the task at hand).

On Thu, Jun 2, 2016 at 12:45 PM, Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US) <richard.c.angelini.civ at mail.mil> wrote:
> Our *immediate* concern is OSMesa - but we'll probably eventually want to address Mesa w/X support .....
>
> -----Original Message-----
> From: Utkarsh Ayachit [Caution-mailto:utkarsh.ayachit at kitware.com]
> Sent: Thursday, June 02, 2016 9:48 AM
> To: Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US) 
> <richard.c.angelini.civ at mail.mil>
> Cc: Chuck Atkins <chuck.atkins at kitware.com>; ParaView 
> <paraview at paraview.org>
> Subject: Re: [Paraview] [Non-DoD Source] Re: 5.0.1/Exodus Reader
>
> Ah okay. Give me a few days to sort it out. The end goal is indeed to have superbuild build the right versions of Mesa. Do you only  care about OSMesa or also Mesa with X support?
>
> Utkarsh
>
>
>
>
> On Thu, Jun 2, 2016 at 8:48 AM, Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US) <richard.c.angelini.civ at mail.mil> wrote:
>> Our current issues seem to be related to our osmesa build for the HPC_side
>> servers.       The Superbuild is building 7.11.2 - you are suggesting that
>> we need to *manually* build a different version of Mesa and somehow link
>> in that new version of Mesa in to the Superbuild?     We rely exclusively
>> on the Superbuild for compiling ParaView across 20 different HPC 
>> systems - so stepping outside of the super build paradigm isn?t necessarily obvious
>> to me!    8-)
>>
>>
>>
>>
>>
>> ________________________________
>> Rick Angelini
>> USArmy Research Laboratory
>> CISD/HPC Architectures Team
>> Phone:  410-278-6266
>>
>>
>>
>>
>> -----Original Message-----
>> From: Utkarsh Ayachit <utkarsh.ayachit at kitware.com>
>> Date: Thursday, June 2, 2016 at 8:37 AM
>> To: Rick Angelini <Richard.C.Angelini.CIV at mail.mil>
>> Cc: Chuck Atkins <chuck.atkins at kitware.com>, ParaView 
>> <paraview at paraview.org>
>> Subject: Re: [Paraview] [Non-DoD Source] Re: 5.0.1/Exodus Reader
>>
>> All active links contained in this email were disabled.  Please 
>> verify the identity of the sender, and confirm the authenticity of 
>> all links contained within the message prior to copying and pasting 
>> the address to a Web browser.
>>
>>
>>
>>
>> ----
>>
>>> So there is much more to be done than adding
>>> -DPARAVIEW_RENDERING_BACKEND:STRING=OpenGL2
>>> -DVTK_RENDERING_BACKEND:STRING="OpenGL2"
>>> to the cmake flags?
>>
>> As far as ParaView is concerned, no there's not much more to it.
>> However if your OpenGL implementation doesn't support OpenGL 3.2 
>> (released in 2009), then alas there's more work to get ParaView 
>> working which could include building a newer version of Mesa. Not 
>> sure if you have seen this blog [1], but that talks about how I got 
>> Mesa to build with appropriate OpenGL renderer enabled. Things have 
>> gotten a little better since then and the Docker script encapsulates 
>> that. The moral of the story is get latest Mesa version and build it 
>> with LLVM/Gallum support.
>>
>> Utkarsh
>>
>> [1]
>> Caution-Caution-https://blog.kitware.com/messing-with-mesa-for-paravi
>> ew-5-0vt
>> k
>> -7-0/
>>


CLASSIFICATION: UNCLASSIFIED
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 5615 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160602/1aa471d1/attachment.bin>

From joseph.g.hennessey2.ctr at mail.mil  Thu Jun  2 16:13:39 2016
From: joseph.g.hennessey2.ctr at mail.mil (Hennessey, Joseph G CTR USARMY RDECOM ARL (US))
Date: Thu, 2 Jun 2016 20:13:39 +0000
Subject: [Paraview] [Non-DoD Source] Re: 5.0.1/Exodus Reader
 (UNCLASSIFIED)
In-Reply-To: <10A03274360DCF47A6EE78C9952A31CA639745D1@UMECHPA7C.easf.csd.disa.mil>
References: <10A03274360DCF47A6EE78C9952A31CA639745D1@UMECHPA7C.easf.csd.disa.mil>
Message-ID: <10A03274360DCF47A6EE78C9952A31CA6397460E@UMECHPA7C.easf.csd.disa.mil>

CLASSIFICATION: UNCLASSIFIED

Utkarsh,

I was wondering how to hack the superbuild for ParaView to use my newly built versions of osmesa

Swapping out the shared libraries does not seem to work, so perhaps a static link is occurring somewhere in the build process of ParaView If I just drop in my newly built version of osmesa in the superbuild build directory, replacing the current version of osmesa and then delete the source, build and install versions of ParaView in the superbuild directory forcing a recompile of all of ParaView 5.0.1 proper, would you expect that to work? Or am I missing something?

The version of libOSMesa in the superbuild is libOSMesa.so.7 while the new versions I am building are libOSMesa.so.8, I made symbolic link with libOSMesa.so.7 -> LibOSMesa.so.8 Which paraview seems to find but still produces the same error complaining of GL Version 2.1

Thanks,

Joe

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Joseph G. Hennessey Ph.D., Lockheed Martin Army Research Lab DOD Supercomputing Resource Center
Email:  joseph.g.hennessey2.ctr at mail.mil


-----Original Message-----
From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Hennessey, Joseph G CTR USARMY RDECOM ARL (US)
Sent: Thursday, June 02, 2016 3:47 PM
To: Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US) <richard.c.angelini.civ at mail.mil>; Utkarsh Ayachit <utkarsh.ayachit at kitware.com>; Su, Simon M CIV USARMY RDECOM ARL (US) <simon.m.su.civ at mail.mil>
Cc: ParaView <paraview at paraview.org>
Subject: Re: [Paraview] [Non-DoD Source] Re: 5.0.1/Exodus Reader (UNCLASSIFIED)

All active links contained in this email were disabled.  Please verify the identity of the sender, and confirm the authenticity of all links contained within the message prior to copying and pasting the address to a Web browser.  




----

CLASSIFICATION: UNCLASSIFIED

Utkarsh,

I am running ParaView 5.0.1 connecting to a remote ParaView 5.0.1 server built with osmesa

And I have rebuild osmesa from both
Mesa 11.1.2 and Mesa 11.2.2 using

./configure \
    --disable-xvmc \
    --disable-glx \
    --disable-dri \
    --with-dri-drivers= \
    --with-gallium-drivers=swrast \
    --enable-texture-float \
    --disable-egl \
    --enable-shared \
    --with-egl-platforms= \
    --enable-gallium-osmesa \
    --enable-gallium-llvm=yes \
    --prefix=<install prefix>

And I have tried replacing the library

lib/paraview-5.0/libOSMesa.so.7

with both libOSMesa.so from 11.1.2 and 11.2.2

and they are both still giving the same error

paraview/VTK/Rendering/OpenGL2/vtkOpenGLRenderWindow.cxx line 587 vtkOSOpenGLRenderWindow GL Version 2.1 with the gpu_shader4 extension is not supported by your graphics driver, but is required for the new OpenGL rendering  backend. Please update your OpenGL driver.
If you are using Mesa please make sure you have version 10.6.5 and make sure your  driver support OpenGL 3.2

Any suggestions?

Thanks,

Joe Hennessey

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Joseph G. Hennessey Ph.D., Lockheed Martin Army Research Lab DOD Supercomputing Resource Center
Email:  joseph.g.hennessey2.ctr at mail.mil


-----Original Message-----
From: ParaView [Caution-mailto:paraview-bounces at paraview.org] On Behalf Of Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US)
Sent: Thursday, June 02, 2016 1:45 PM
To: Utkarsh Ayachit <utkarsh.ayachit at kitware.com>
Cc: ParaView <paraview at paraview.org>
Subject: Re: [Paraview] [Non-DoD Source] Re: 5.0.1/Exodus Reader

All active links contained in this email were disabled.  Please verify the identity of the sender, and confirm the authenticity of all links contained within the message prior to copying and pasting the address to a Web browser.  




----

Utkarsh - thanks - in the mean time, we're going to try to build Mesa 11.1 (?) outside of ParaView and link it in and see how far we can get!   8-)    But it would certainly be cleaner to use the Superbuild when you get that updated with the proper Mesa build!



-----Original Message-----
From: Utkarsh Ayachit [Caution-Caution-mailto:utkarsh.ayachit at kitware.com]
Sent: Thursday, June 02, 2016 1:18 PM
To: Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US) <richard.c.angelini.civ at mail.mil>
Cc: Chuck Atkins <chuck.atkins at kitware.com>; ParaView <paraview at paraview.org>
Subject: Re: [Paraview] [Non-DoD Source] Re: 5.0.1/Exodus Reader

Roger that. I will have updates for you early next week (plan to work on it as soon as I am done with the task at hand).

On Thu, Jun 2, 2016 at 12:45 PM, Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US) <richard.c.angelini.civ at mail.mil> wrote:
> Our *immediate* concern is OSMesa - but we'll probably eventually want to address Mesa w/X support .....
>
> -----Original Message-----
> From: Utkarsh Ayachit
> [Caution-Caution-mailto:utkarsh.ayachit at kitware.com]
> Sent: Thursday, June 02, 2016 9:48 AM
> To: Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US) 
> <richard.c.angelini.civ at mail.mil>
> Cc: Chuck Atkins <chuck.atkins at kitware.com>; ParaView 
> <paraview at paraview.org>
> Subject: Re: [Paraview] [Non-DoD Source] Re: 5.0.1/Exodus Reader
>
> Ah okay. Give me a few days to sort it out. The end goal is indeed to have superbuild build the right versions of Mesa. Do you only  care about OSMesa or also Mesa with X support?
>
> Utkarsh
>
>
>
>
> On Thu, Jun 2, 2016 at 8:48 AM, Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US) <richard.c.angelini.civ at mail.mil> wrote:
>> Our current issues seem to be related to our osmesa build for the HPC_side
>> servers.       The Superbuild is building 7.11.2 - you are suggesting that
>> we need to *manually* build a different version of Mesa and somehow link
>> in that new version of Mesa in to the Superbuild?     We rely exclusively
>> on the Superbuild for compiling ParaView across 20 different HPC 
>> systems - so stepping outside of the super build paradigm isn?t necessarily obvious
>> to me!    8-)
>>
>>
>>
>>
>>
>> ________________________________
>> Rick Angelini
>> USArmy Research Laboratory
>> CISD/HPC Architectures Team
>> Phone:  410-278-6266
>>
>>
>>
>>
>> -----Original Message-----
>> From: Utkarsh Ayachit <utkarsh.ayachit at kitware.com>
>> Date: Thursday, June 2, 2016 at 8:37 AM
>> To: Rick Angelini <Richard.C.Angelini.CIV at mail.mil>
>> Cc: Chuck Atkins <chuck.atkins at kitware.com>, ParaView 
>> <paraview at paraview.org>
>> Subject: Re: [Paraview] [Non-DoD Source] Re: 5.0.1/Exodus Reader
>>
>> All active links contained in this email were disabled.  Please 
>> verify the identity of the sender, and confirm the authenticity of 
>> all links contained within the message prior to copying and pasting 
>> the address to a Web browser.
>>
>>
>>
>>
>> ----
>>
>>> So there is much more to be done than adding
>>> -DPARAVIEW_RENDERING_BACKEND:STRING=OpenGL2
>>> -DVTK_RENDERING_BACKEND:STRING="OpenGL2"
>>> to the cmake flags?
>>
>> As far as ParaView is concerned, no there's not much more to it.
>> However if your OpenGL implementation doesn't support OpenGL 3.2 
>> (released in 2009), then alas there's more work to get ParaView 
>> working which could include building a newer version of Mesa. Not 
>> sure if you have seen this blog [1], but that talks about how I got 
>> Mesa to build with appropriate OpenGL renderer enabled. Things have 
>> gotten a little better since then and the Docker script encapsulates 
>> that. The moral of the story is get latest Mesa version and build it 
>> with LLVM/Gallum support.
>>
>> Utkarsh
>>
>> [1]
>> Caution-Caution-Caution-https://blog.kitware.com/messing-with-mesa-fo
>> r-paravi
>> ew-5-0vt
>> k
>> -7-0/
>>


CLASSIFICATION: UNCLASSIFIED


CLASSIFICATION: UNCLASSIFIED
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 5615 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160602/b14d2b6c/attachment.bin>

From utkarsh.ayachit at kitware.com  Thu Jun  2 16:19:22 2016
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Thu, 2 Jun 2016 16:19:22 -0400
Subject: [Paraview] [Non-DoD Source] Re: 5.0.1/Exodus Reader
	(UNCLASSIFIED)
In-Reply-To: <10A03274360DCF47A6EE78C9952A31CA639745D1@UMECHPA7C.easf.csd.disa.mil>
References: <10A03274360DCF47A6EE78C9952A31CA639745D1@UMECHPA7C.easf.csd.disa.mil>
Message-ID: <CADHSJjAOCZ-oCuOrXF9awJUva5K7kXWAMZ=HToRVTS2f94w1BA@mail.gmail.com>

> And I have tried replacing the library
> lib/paraview-5.0/libOSMesa.so.7
> with both libOSMesa.so from 11.1.2 and 11.2.2
> and they are both still giving the same error

Simply swapping the libraries won't work. Mesa 11.2 [1] added new API
OSMesaCreateContextAttribs() which is needed to create correct OpenGL
context.  The API is used at compile time if appropriate osmesa.h is
being used.

You can try to update Projects/unix/osmesa.cmake in the superbuild
source to use the configure arguments you used, and also change
versions.cmake in the same repo to point to change the osmesa source
tar ball to be 11.2. Now the superbuid will build 11.2 instead and it
should then have the new API available.

[1] http://www.mesa3d.org/relnotes/11.2.0.html

From utkarsh.ayachit at kitware.com  Thu Jun  2 16:26:02 2016
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Thu, 2 Jun 2016 16:26:02 -0400
Subject: [Paraview] Upgrade of GPU drivers
In-Reply-To: <413FB7C6-E434-4C80-9812-FEA2B0F1A5ED@vt.edu>
References: <413FB7C6-E434-4C80-9812-FEA2B0F1A5ED@vt.edu>
Message-ID: <CADHSJjAct-xNe2zEgiSBt5Ljx-YSdFiDG0UhVcq8r=_ak=FrVA@mail.gmail.com>

No, you don't need to recompile ParaView.

On Thu, Jun 2, 2016 at 2:19 PM, Sangeetha Banavathi Srinivasa
<bsangee at vt.edu> wrote:
> Hello,
>
> I wanted to know if ParaView should be recompiled on HPC clusters after upgrading GPU drivers?
>
> Thanks,
> Sangeetha
> _______________________________________________
> 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 peterdebuchev at gmail.com  Fri Jun  3 01:22:58 2016
From: peterdebuchev at gmail.com (Peter Debuchev)
Date: Fri, 3 Jun 2016 07:22:58 +0200
Subject: [Paraview] basics of paraview client server programming
In-Reply-To: <CADHSJjCX0VagGF-8Tkj=Ro8mbSsEFkTWSkRR0xW3T3aEY9fifg@mail.gmail.com>
References: <CAAUk9C4i5x3UF0bYC0FUVpJtR6LUrrS00qnN_dJi2CXFOJo_mg@mail.gmail.com>
 <CAAUk9C6YsFEt=b=RWMwGS3WfUO+iGFXs5NEc3RB0L9digST8=A@mail.gmail.com>
 <574FFA35.5040701@gmail.com>
 <CADHSJjCX0VagGF-8Tkj=Ro8mbSsEFkTWSkRR0xW3T3aEY9fifg@mail.gmail.com>
Message-ID: <CAAUk9C7s0kL05ohN2cuTf=B9bAbjtewF48-X_q0qa_S1qKJo1A@mail.gmail.com>

Dear Utkarsh,
if those topics have been available in the Paraview Guide v3 and removed in
the new guide, this would explain why I couldn't find the explanations in
any of the recent editions although I went through them several times to
check.

You would do me (and many others) a huge favor if you could share the
missing chapter even if the details are outdated with respect to the newest
Paraview software version.

Thank you
Peter

2016-06-02 14:43 GMT+02:00 Utkarsh Ayachit <utkarsh.ayachit at kitware.com>:

> Alas, there's nothing up-to-date. I've been meaning to write a blog
> series covering various aspect of ParaView internals, but it's hard to
> find some downtime to get that going. I'll try to see if I can find
> the old PDF for the ParaView Guide v3 and share the old chapter
> (although obsolete, but basic design may still be relevant). The
> ParaView developers Wiki
> (http://www.paraview.org/ParaView/index.php/Main_Page) has a few
> articles that we wrote with coming up with the design for some of the
> core components. The implementations generally differ slightly from
> the design and may have names/APIs changed since, but nonetheless may
> be helpful in understanding how things came about. Specifically,
>
> [1] http://www.paraview.org/ParaView/index.php/ServerManager_2.0
> [2] http://www.paraview.org/ParaView/index.php/ProcessModule_2.0
> [3] http://www.paraview.org/ParaView/index.php/Views_And_Representations
> [4]
> http://www.paraview.org/ParaView/images/2/24/ParaViewCollaborationChanges.pdf
>
> Utkarsh
>
> On Thu, Jun 2, 2016 at 5:19 AM, Ellon Paiva <ellonpaiva at gmail.com> wrote:
> > +1 for that. I'm very interested to know if there's such book or
> document.
> >
> > When I started developing a plug-in for ParaView I found this
> presentation
> > almost by accident. Maybe it can help you. Apparently it was used in a
> > conference/workshop (VIS08?) to describe briefly the proxy system, and
> > refers to the "Paraview Guide, Version 3, section 18.6, and chapter 19
> for
> > details (see slide 30). Unfortunately the version 3 of the Guide I
> couldn't
> > find.
> >
> > Ellon
> >
> >
> > On 06/02/2016 07:35 AM, Peter Debuchev wrote:
> >
> > Is any introduction available, how vtkSMServerManager, vtkSMSessions,
> > vtkProxies etc. are set up to interact with a pvserver or with a custom
> > server application?
> > I am not talking about short demos that show how to create and display a
> > sphere using pvpython. What I am looking for is a book chapter or similar
> > explaining the principles behind vtkSMSessions, vtkProcies etc.
> >
> > Does anybody remember, which of the VTK or ITK or Paraview books included
> > such chapters?
> >
> > Peter
> >
> > 2016-05-29 19:09 GMT+02:00 Peter Debuchev <peterdebuchev at gmail.com>:
> >>
> >> Dear Paraview programmers,
> >> I am looking for some information about the basic principles of
> Paraviews
> >> client-server model, the setup of client proxies and the communication
> >> design.
> >>
> >> I think that I have seen a chapter with a short introduction on these
> >> topics some years ago. It was in one of the VTK books or in the Paraview
> >> User's Guide. Now I cannot find this chapter again. Has it been removed
> in
> >> the latest edition of these books? Or is it described in a different
> book
> >> which I don't remember?
> >>
> >> Peter
> >
> >
> >
> >
> > _______________________________________________
> > 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
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160603/f286935d/attachment.html>

From richard.c.angelini.civ at mail.mil  Fri Jun  3 08:16:35 2016
From: richard.c.angelini.civ at mail.mil (Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US))
Date: Fri, 3 Jun 2016 12:16:35 +0000
Subject: [Paraview] [Non-DoD Source] Re: 5.0.1/Exodus Reader
 (UNCLASSIFIED)
In-Reply-To: <CADHSJjAOCZ-oCuOrXF9awJUva5K7kXWAMZ=HToRVTS2f94w1BA@mail.gmail.com>
References: <10A03274360DCF47A6EE78C9952A31CA639745D1@UMECHPA7C.easf.csd.disa.mil>
 <CADHSJjAOCZ-oCuOrXF9awJUva5K7kXWAMZ=HToRVTS2f94w1BA@mail.gmail.com>
Message-ID: <D376ECE6.2B9E1%Richard.C.Angelini.CIV@mail.mil>

Would it be sufficient to change the cmake flags OSMESA_INCLUDE_DIR and
OSMESA_LIBRARY in CMakeCache file to point to the external build of Mesa
11.x.x?


________________________________
Rick Angelini
USArmy Research Laboratory
CISD/HPC Architectures Team
Phone:  410-278-6266




-----Original Message-----
From: Utkarsh Ayachit <utkarsh.ayachit at kitware.com>
Date: Thursday, June 2, 2016 at 4:19 PM
To: "Hennessey, Joseph G CTR USARMY RDECOM ARL (US)"
<joseph.g.hennessey2.ctr at mail.mil>
Cc: Rick Angelini <Richard.C.Angelini.CIV at mail.mil>, Simon Su
<simon.m.su.CIV at mail.mil>, ParaView <paraview at paraview.org>
Subject: Re: [Paraview] [Non-DoD Source] Re: 5.0.1/Exodus Reader
(UNCLASSIFIED)

All active links contained in this email were disabled.  Please verify the
identity of the sender, and confirm the authenticity of all links
contained within the message prior to copying and pasting the address to a
Web browser.  




----

> And I have tried replacing the library
> lib/paraview-5.0/libOSMesa.so.7
> with both libOSMesa.so from 11.1.2 and 11.2.2
> and they are both still giving the same error

Simply swapping the libraries won't work. Mesa 11.2 [1] added new API
OSMesaCreateContextAttribs() which is needed to create correct OpenGL
context.  The API is used at compile time if appropriate osmesa.h is
being used.

You can try to update Projects/unix/osmesa.cmake in the superbuild
source to use the configure arguments you used, and also change
versions.cmake in the same repo to point to change the osmesa source
tar ball to be 11.2. Now the superbuid will build 11.2 instead and it
should then have the new API available.

[1] Caution-http://www.mesa3d.org/relnotes/11.2.0.html


From utkarsh.ayachit at kitware.com  Fri Jun  3 08:39:40 2016
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Fri, 3 Jun 2016 08:39:40 -0400
Subject: [Paraview] [Non-DoD Source] Re: 5.0.1/Exodus Reader
	(UNCLASSIFIED)
In-Reply-To: <D376ECE6.2B9E1%Richard.C.Angelini.CIV@mail.mil>
References: <10A03274360DCF47A6EE78C9952A31CA639745D1@UMECHPA7C.easf.csd.disa.mil>
 <CADHSJjAOCZ-oCuOrXF9awJUva5K7kXWAMZ=HToRVTS2f94w1BA@mail.gmail.com>
 <D376ECE6.2B9E1%Richard.C.Angelini.CIV@mail.mil>
Message-ID: <CADHSJjB94jBhGjChXvT1ex2FrDNCFasSNUhFpjrxbarCR8fUSg@mail.gmail.com>

> Would it be sufficient to change the cmake flags OSMESA_INCLUDE_DIR and
> OSMESA_LIBRARY in CMakeCache file to point to the external build of Mesa
> 11.x.x?

Pretty much (and setting a few other vars to empty including
OPENGL_gl_LIBRARY etc, see the arguments to add_extra_cmake_args()
call in https://gitlab.kitware.com/paraview/paraview-superbuild/blob/master/Projects/unix/osmesa.cmake)

Note, you need 11.2 or newer for the correct OSMesa API. Otherwise you
can use the attached patch to patch 11.1 or older.

Utkarsh
-------------- next part --------------
A non-text attachment was scrubbed...
Name: mesa.patch
Type: text/x-patch
Size: 11012 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160603/b715e141/attachment.bin>

From utkarsh.ayachit at kitware.com  Fri Jun  3 08:49:22 2016
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Fri, 3 Jun 2016 08:49:22 -0400
Subject: [Paraview] Upgrade of GPU drivers
In-Reply-To: <DE5AA6A3-C661-4BA3-BC25-D145C8598A49@vt.edu>
References: <413FB7C6-E434-4C80-9812-FEA2B0F1A5ED@vt.edu>
 <CADHSJjAct-xNe2zEgiSBt5Ljx-YSdFiDG0UhVcq8r=_ak=FrVA@mail.gmail.com>
 <DE5AA6A3-C661-4BA3-BC25-D145C8598A49@vt.edu>
Message-ID: <CADHSJjBi1vHtrpsJ-NdJeOj5wqe8j0TCvvYjFeLxccVbYdWwtg@mail.gmail.com>

Those are errors reported when paraVIew cannot connect to the Xserver.
Try any other tool that needs X, e.g. gvim, glxgears, all will fail
the same way. See this:
http://www.paraview.org/Wiki/Setting_up_a_ParaView_Server#X_Connections

On Thu, Jun 2, 2016 at 5:38 PM, Sangeetha Banavathi Srinivasa
<bsangee at vt.edu> wrote:
> But after a recent upgrade of the GPU drivers on our cluster we are seeing
> the below error:
>
> bad X server connection. DISPLAY=ERROR:
>
> This is seen on ParaView/4.0.1.
>
> We have two different clusters that are supporting this version of ParaView
> and GPU drivers on both these clusters were updated.
> ParaView/4.0.1 is running fine on the first cluster whereas it is throwing
> the above error on the other.
> But on the first cluster all the compilers were recompiled after the GPU
> driver update but this wasn?t done on the second one.
> So I was wondering what change could have actually caused the above error.
>
>
> On Jun 2, 2016, at 4:26 PM, Utkarsh Ayachit <utkarsh.ayachit at kitware.com>
> wrote:
>
> No, you don't need to recompile ParaView.
>
> On Thu, Jun 2, 2016 at 2:19 PM, Sangeetha Banavathi Srinivasa
> <bsangee at vt.edu> wrote:
>
> Hello,
>
> I wanted to know if ParaView should be recompiled on HPC clusters after
> upgrading GPU drivers?
>
> Thanks,
> Sangeetha
> _______________________________________________
> 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 mlohry at gmail.com  Fri Jun  3 17:03:04 2016
From: mlohry at gmail.com (Mark Lohry)
Date: Fri, 3 Jun 2016 15:03:04 -0600
Subject: [Paraview] antialiasing in export scene, vector graphics,
	font selection
Message-ID: <CAJ7aB-JBeLg0R0TW2rsYGZWc9qCvq_h9NQtTUShG=Jv-9YrGmQ@mail.gmail.com>

New here after ditching tecplot, I've run into a few questions in trying to
get publication-quality (for LaTeX) graphic exports:


1) Assuming "export scene" is the preferred way to output images, how do I
get anti-aliasing of the produced image? I see no option for it. Failing
that -- if I choose to not rasterize the image, I'm losing some color
information whereas the save screenshot function correctly outputs the
color (see attached figures).

2) In the color legend font properties, only Arial, Courier, and Times are
available. Is there a way to use some other font from my system?

Any other tips/references on getting high quality exports would be greatly
appreciated.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160603/1de408a2/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: paratest.png
Type: image/png
Size: 85206 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160603/1de408a2/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: paratest_vector.eps.png
Type: image/png
Size: 235935 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160603/1de408a2/attachment-0003.png>

From wascott at sandia.gov  Fri Jun  3 17:44:39 2016
From: wascott at sandia.gov (Scott, W Alan)
Date: Fri, 3 Jun 2016 21:44:39 +0000
Subject: [Paraview] Moving a clip plane
Message-ID: <b336909267e34b518d858bc7141ea7e6@ES01AMSNLNT.srn.sandia.gov>

Is it possible to have a clip filter center the clip on moving data?  For instance, if I want a clip to remain in the middle of the can dataset as the plate flattens the can, is this possible?  How is it done?

Thanks,

Alan

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

From danielbruno at gmail.com  Sat Jun  4 00:14:45 2016
From: danielbruno at gmail.com (Daniel Bruno)
Date: Sat, 04 Jun 2016 04:14:45 +0000
Subject: [Paraview] antialiasing in export scene, vector graphics,
	font selection
In-Reply-To: <CAJ7aB-JBeLg0R0TW2rsYGZWc9qCvq_h9NQtTUShG=Jv-9YrGmQ@mail.gmail.com>
References: <CAJ7aB-JBeLg0R0TW2rsYGZWc9qCvq_h9NQtTUShG=Jv-9YrGmQ@mail.gmail.com>
Message-ID: <CAJ+axnB+RbSH_dj1yH0hDCv3OaS62EhWz9HEVQfQ_mR_CyKP7w@mail.gmail.com>

Really nice topics to discuss, Mark. I have the same questions about image
anti-aliasing and font selection features that are missing (or maybe I
don't know how to reach them).

Hope to have some light shed on this issue. Thank you!

Daniel Bruno.
CFD Researcher


On Fri, Jun 3, 2016, 18:03 Mark Lohry <mlohry at gmail.com> wrote:

> New here after ditching tecplot, I've run into a few questions in trying
> to get publication-quality (for LaTeX) graphic exports:
>
>
> 1) Assuming "export scene" is the preferred way to output images, how do I
> get anti-aliasing of the produced image? I see no option for it. Failing
> that -- if I choose to not rasterize the image, I'm losing some color
> information whereas the save screenshot function correctly outputs the
> color (see attached figures).
>
> 2) In the color legend font properties, only Arial, Courier, and Times are
> available. Is there a way to use some other font from my system?
>
> Any other tips/references on getting high quality exports would be greatly
> appreciated.
> _______________________________________________
> 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
>
-- 



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

From rodrigo.pelorosso at gmail.com  Sun Jun  5 19:45:22 2016
From: rodrigo.pelorosso at gmail.com (Rodrigo Pelorosso)
Date: Sun, 5 Jun 2016 23:45:22 +0000
Subject: [Paraview] pvpython and vtk classes and functions to create objects
Message-ID: <CAMGPr0Ua9hfxqcGsdqZ=d2+4kX=a1bthb0_bRQNtcR0T_huxNQ@mail.gmail.com>

Hi!

Is there a way to use python VTK functions and classes in paraview?  I'm
using paraview through paraviewweb and I've created an RPC that I can call
from the client to run paraview python code:

@exportRpc("my.test.rpc")
    def myTestRPCFunction(self):
        return 0

I would like to create, inside this RPC, a plane with a texture applied.
Searching the mailing list I found this thread,

https://cmake.org/pipermail/paraview/2011-April/020848.html

were someone's trying to accomplish this from a reader written in C++, but
I would really like to do something like that inside my RPC, is that
possible?

Thank you!
Rodrigo
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160605/8b8df90d/attachment.html>

From david.lonie at kitware.com  Mon Jun  6 10:41:58 2016
From: david.lonie at kitware.com (David Lonie)
Date: Mon, 6 Jun 2016 10:41:58 -0400
Subject: [Paraview] antialiasing in export scene, vector graphics,
	font selection
In-Reply-To: <CAJ7aB-JBeLg0R0TW2rsYGZWc9qCvq_h9NQtTUShG=Jv-9YrGmQ@mail.gmail.com>
References: <CAJ7aB-JBeLg0R0TW2rsYGZWc9qCvq_h9NQtTUShG=Jv-9YrGmQ@mail.gmail.com>
Message-ID: <CA+=e1otwypLQQHFQCeKSTmh9DojPU_wcjRwAzbQFVGoNT_K5HQ@mail.gmail.com>

On Fri, Jun 3, 2016 at 5:03 PM, Mark Lohry <mlohry at gmail.com> wrote:

> 1) Assuming "export scene" is the preferred way to output images, how do I
> get anti-aliasing of the produced image? I see no option for it. Failing
> that -- if I choose to not rasterize the image, I'm losing some color
> information whereas the save screenshot function correctly outputs the
> color (see attached figures).
>

The raster-format exports tend to just grab the image directly from the
OpenGL framebuffer, but unfortunately anti-aliased rendering is not
currently enabled in ParaView as it interferes with some of the other
rendering passes. There is some work-in-progress on adding DPI options to
paraview exports that will help with this issue in a future release.

I'm not sure what's going on with the color in the vector export. The GL2PS
library used to generate the vector graphics files is somewhat fickle with
some coloring methods, you may be able to play with the rendering settings
to get that to come out right. I know that, for instance, the "Interpolate
Colors Before Mapping" option will often cause issues.

Right now your best bet for getting an anti-aliased export from ParaView is
to emulate SSAA by making a screenshot with a custom resolution. By setting
the resolution in File > Save Screenshot to a larger resolution than your
desired image size and then shrinking the image externally you should get a
smoother result.


>
> 2) In the color legend font properties, only Arial, Courier, and Times are
> available. Is there a way to use some other font from my system?
>

This is currently not possible in ParaView. There is support for custom
fonts in VTK (the library that drives ParaView's rendering), but it has not
been exposed in ParaView.

Hope this helps,
Dave
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160606/566494f7/attachment.html>

From joseph.g.hennessey2.ctr at mail.mil  Mon Jun  6 12:00:50 2016
From: joseph.g.hennessey2.ctr at mail.mil (Hennessey, Joseph G CTR USARMY RDECOM ARL (US))
Date: Mon, 6 Jun 2016 16:00:50 +0000
Subject: [Paraview] [Non-DoD Source] Re: 5.0.1/Exodus Reader
 (UNCLASSIFIED)
In-Reply-To: <CADHSJjAOCZ-oCuOrXF9awJUva5K7kXWAMZ=HToRVTS2f94w1BA@mail.gmail.com>
References: <10A03274360DCF47A6EE78C9952A31CA639745D1@UMECHPA7C.easf.csd.disa.mil>
 <CADHSJjAOCZ-oCuOrXF9awJUva5K7kXWAMZ=HToRVTS2f94w1BA@mail.gmail.com>
Message-ID: <10A03274360DCF47A6EE78C9952A31CA6397B5E0@UMECHPA7C.easf.csd.disa.mil>

CLASSIFICATION: UNCLASSIFIED

Utkarsh,

I have rebuilt osmesa using mesa 11.2.2 but
it ParaView rebuilt with the new version is giving
me the same error as before, complaining that the
GL version 2.1 with gpu_shader4 extension is not
Supported.

I think I know  why  this is occurring and I wondered if you
could confirm this for me.

I configured mesa with these parameters

./configure \
    --disable-xvmc \
    --disable-glx \
    --disable-dri \
    --with-dri-drivers= \
    --with-gallium-drivers=swrast \
    --enable-texture-float \
    --disable-egl \
    --with-egl-platforms= \
    --enable-gallium-osmesa \
    --enable-gallium-llvm=yes \
    --prefix=<install prefix>

but, I did not have a version of llvm available
and the configure script then set

Llvm = no

>From my reading of this webpage

http://www.paraview.org/Wiki/ParaView/ParaView_And_Mesa_3D

It seems that without gallium-llvm,
the version of OpenGL built reverts to an older version,
which I believe is why I am still getting the error.

Would you agree with this?

Thanks,

Joe

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Joseph G. Hennessey Ph.D., Lockheed Martin
Army Research Lab
DOD Supercomputing Resource Center


-----Original Message-----
From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com]
Sent: Thursday, June 02, 2016 4:19 PM
To: Hennessey, Joseph G CTR USARMY RDECOM ARL (US) 
<joseph.g.hennessey2.ctr at mail.mil>
Cc: Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US) 
<richard.c.angelini.civ at mail.mil>; Su, Simon M CIV USARMY RDECOM ARL (US) 
<simon.m.su.civ at mail.mil>; ParaView <paraview at paraview.org>
Subject: Re: [Paraview] [Non-DoD Source] Re: 5.0.1/Exodus Reader 
(UNCLASSIFIED)

All active links contained in this email were disabled.  Please verify the 
identity of the sender, and confirm the authenticity of all links contained 
within the message prior to copying and pasting the address to a Web browser.




----

> And I have tried replacing the library
> lib/paraview-5.0/libOSMesa.so.7
> with both libOSMesa.so from 11.1.2 and 11.2.2 and they are both still
> giving the same error

Simply swapping the libraries won't work. Mesa 11.2 [1] added new API
OSMesaCreateContextAttribs() which is needed to create correct OpenGL context. 
The API is used at compile time if appropriate osmesa.h is being used.

You can try to update Projects/unix/osmesa.cmake in the superbuild source to 
use the configure arguments you used, and also change versions.cmake in the 
same repo to point to change the osmesa source tar ball to be 11.2. Now the 
superbuid will build 11.2 instead and it should then have the new API 
available.

[1] Caution-http://www.mesa3d.org/relnotes/11.2.0.html


CLASSIFICATION: UNCLASSIFIED
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 5615 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160606/aa968446/attachment.bin>

From utkarsh.ayachit at kitware.com  Mon Jun  6 12:31:30 2016
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Mon, 6 Jun 2016 12:31:30 -0400
Subject: [Paraview] [Non-DoD Source] Re: 5.0.1/Exodus Reader
	(UNCLASSIFIED)
In-Reply-To: <10A03274360DCF47A6EE78C9952A31CA6397B5E0@UMECHPA7C.easf.csd.disa.mil>
References: <10A03274360DCF47A6EE78C9952A31CA639745D1@UMECHPA7C.easf.csd.disa.mil>
 <CADHSJjAOCZ-oCuOrXF9awJUva5K7kXWAMZ=HToRVTS2f94w1BA@mail.gmail.com>
 <10A03274360DCF47A6EE78C9952A31CA6397B5E0@UMECHPA7C.easf.csd.disa.mil>
Message-ID: <CADHSJjCvPLuG-iR4uxBdtQ4Rw0sBYqET9td2wRQMiErhGQxr2w@mail.gmail.com>

I am working on updating superbuild today. Just hold on. I'll email
once I have it working.

On Mon, Jun 6, 2016 at 12:00 PM, Hennessey, Joseph G CTR USARMY RDECOM
ARL (US) <joseph.g.hennessey2.ctr at mail.mil> wrote:
> CLASSIFICATION: UNCLASSIFIED
>
> Utkarsh,
>
> I have rebuilt osmesa using mesa 11.2.2 but
> it ParaView rebuilt with the new version is giving
> me the same error as before, complaining that the
> GL version 2.1 with gpu_shader4 extension is not
> Supported.
>
> I think I know  why  this is occurring and I wondered if you
> could confirm this for me.
>
> I configured mesa with these parameters
>
> ./configure \
>     --disable-xvmc \
>     --disable-glx \
>     --disable-dri \
>     --with-dri-drivers= \
>     --with-gallium-drivers=swrast \
>     --enable-texture-float \
>     --disable-egl \
>     --with-egl-platforms= \
>     --enable-gallium-osmesa \
>     --enable-gallium-llvm=yes \
>     --prefix=<install prefix>
>
> but, I did not have a version of llvm available
> and the configure script then set
>
> Llvm = no
>
> From my reading of this webpage
>
> http://www.paraview.org/Wiki/ParaView/ParaView_And_Mesa_3D
>
> It seems that without gallium-llvm,
> the version of OpenGL built reverts to an older version,
> which I believe is why I am still getting the error.
>
> Would you agree with this?
>
> Thanks,
>
> Joe
>
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> Joseph G. Hennessey Ph.D., Lockheed Martin
> Army Research Lab
> DOD Supercomputing Resource Center
>
>
> -----Original Message-----
> From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com]
> Sent: Thursday, June 02, 2016 4:19 PM
> To: Hennessey, Joseph G CTR USARMY RDECOM ARL (US)
> <joseph.g.hennessey2.ctr at mail.mil>
> Cc: Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US)
> <richard.c.angelini.civ at mail.mil>; Su, Simon M CIV USARMY RDECOM ARL (US)
> <simon.m.su.civ at mail.mil>; ParaView <paraview at paraview.org>
> Subject: Re: [Paraview] [Non-DoD Source] Re: 5.0.1/Exodus Reader
> (UNCLASSIFIED)
>
> All active links contained in this email were disabled.  Please verify the
> identity of the sender, and confirm the authenticity of all links contained
> within the message prior to copying and pasting the address to a Web browser.
>
>
>
>
> ----
>
>> And I have tried replacing the library
>> lib/paraview-5.0/libOSMesa.so.7
>> with both libOSMesa.so from 11.1.2 and 11.2.2 and they are both still
>> giving the same error
>
> Simply swapping the libraries won't work. Mesa 11.2 [1] added new API
> OSMesaCreateContextAttribs() which is needed to create correct OpenGL context.
> The API is used at compile time if appropriate osmesa.h is being used.
>
> You can try to update Projects/unix/osmesa.cmake in the superbuild source to
> use the configure arguments you used, and also change versions.cmake in the
> same repo to point to change the osmesa source tar ball to be 11.2. Now the
> superbuid will build 11.2 instead and it should then have the new API
> available.
>
> [1] Caution-http://www.mesa3d.org/relnotes/11.2.0.html
>
>
> CLASSIFICATION: UNCLASSIFIED

From peterdebuchev at gmail.com  Mon Jun  6 12:59:29 2016
From: peterdebuchev at gmail.com (Peter Debuchev)
Date: Mon, 6 Jun 2016 18:59:29 +0200
Subject: [Paraview] basics of paraview client server programming
In-Reply-To: <CADHSJjCX0VagGF-8Tkj=Ro8mbSsEFkTWSkRR0xW3T3aEY9fifg@mail.gmail.com>
References: <CAAUk9C4i5x3UF0bYC0FUVpJtR6LUrrS00qnN_dJi2CXFOJo_mg@mail.gmail.com>
 <CAAUk9C6YsFEt=b=RWMwGS3WfUO+iGFXs5NEc3RB0L9digST8=A@mail.gmail.com>
 <574FFA35.5040701@gmail.com>
 <CADHSJjCX0VagGF-8Tkj=Ro8mbSsEFkTWSkRR0xW3T3aEY9fifg@mail.gmail.com>
Message-ID: <CAAUk9C5F1ZU8tzGGrgvbpOgrFSwg=Hipnd4cTcKWhOw+drV80g@mail.gmail.com>

Dear Utkarsh,
thank you for your offer to search the old ParaView Guide v3 client-server
programming chapter. May I ask whether your search has been successful?
Even a scan of the pages from the relevant chapter would be nice, if you
are authorized to share it.

I have read all your links, and they are great to get an idea about the
changes that are going on. However, I would need a well structured
book-chapter which builds the story from the basic requirements to a full,
simple application. The information in the links is so spread that
everything seems to depend on everything else, and nowhere is it clear what
are ideas for the future, what is under current development, and what has
been deprecated again.
I would really like to read again the chapter from ParaView Guide v3, which
I remember gave me perfect insight into Paraview years ago. Even if it is
rather out of date, it would give me a solid basis to better understand the
current developments.

Peter

2016-06-02 14:43 GMT+02:00 Utkarsh Ayachit <utkarsh.ayachit at kitware.com>:

> Alas, there's nothing up-to-date. I've been meaning to write a blog
> series covering various aspect of ParaView internals, but it's hard to
> find some downtime to get that going. I'll try to see if I can find
> the old PDF for the ParaView Guide v3 and share the old chapter
> (although obsolete, but basic design may still be relevant). The
> ParaView developers Wiki
> (http://www.paraview.org/ParaView/index.php/Main_Page) has a few
> articles that we wrote with coming up with the design for some of the
> core components. The implementations generally differ slightly from
> the design and may have names/APIs changed since, but nonetheless may
> be helpful in understanding how things came about. Specifically,
>
> [1] http://www.paraview.org/ParaView/index.php/ServerManager_2.0
> [2] http://www.paraview.org/ParaView/index.php/ProcessModule_2.0
> [3] http://www.paraview.org/ParaView/index.php/Views_And_Representations
> [4]
> http://www.paraview.org/ParaView/images/2/24/ParaViewCollaborationChanges.pdf
>
> Utkarsh
>
> On Thu, Jun 2, 2016 at 5:19 AM, Ellon Paiva <ellonpaiva at gmail.com> wrote:
> > +1 for that. I'm very interested to know if there's such book or
> document.
> >
> > When I started developing a plug-in for ParaView I found this
> presentation
> > almost by accident. Maybe it can help you. Apparently it was used in a
> > conference/workshop (VIS08?) to describe briefly the proxy system, and
> > refers to the "Paraview Guide, Version 3, section 18.6, and chapter 19
> for
> > details (see slide 30). Unfortunately the version 3 of the Guide I
> couldn't
> > find.
> >
> > Ellon
> >
> >
> > On 06/02/2016 07:35 AM, Peter Debuchev wrote:
> >
> > Is any introduction available, how vtkSMServerManager, vtkSMSessions,
> > vtkProxies etc. are set up to interact with a pvserver or with a custom
> > server application?
> > I am not talking about short demos that show how to create and display a
> > sphere using pvpython. What I am looking for is a book chapter or similar
> > explaining the principles behind vtkSMSessions, vtkProcies etc.
> >
> > Does anybody remember, which of the VTK or ITK or Paraview books included
> > such chapters?
> >
> > Peter
> >
> > 2016-05-29 19:09 GMT+02:00 Peter Debuchev <peterdebuchev at gmail.com>:
> >>
> >> Dear Paraview programmers,
> >> I am looking for some information about the basic principles of
> Paraviews
> >> client-server model, the setup of client proxies and the communication
> >> design.
> >>
> >> I think that I have seen a chapter with a short introduction on these
> >> topics some years ago. It was in one of the VTK books or in the Paraview
> >> User's Guide. Now I cannot find this chapter again. Has it been removed
> in
> >> the latest edition of these books? Or is it described in a different
> book
> >> which I don't remember?
> >>
> >> Peter
> >
> >
> >
> >
> > _______________________________________________
> > 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
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160606/5edd4722/attachment.html>

From utkarsh.ayachit at kitware.com  Mon Jun  6 13:01:13 2016
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Mon, 6 Jun 2016 13:01:13 -0400
Subject: [Paraview] basics of paraview client server programming
In-Reply-To: <CAAUk9C5F1ZU8tzGGrgvbpOgrFSwg=Hipnd4cTcKWhOw+drV80g@mail.gmail.com>
References: <CAAUk9C4i5x3UF0bYC0FUVpJtR6LUrrS00qnN_dJi2CXFOJo_mg@mail.gmail.com>
 <CAAUk9C6YsFEt=b=RWMwGS3WfUO+iGFXs5NEc3RB0L9digST8=A@mail.gmail.com>
 <574FFA35.5040701@gmail.com>
 <CADHSJjCX0VagGF-8Tkj=Ro8mbSsEFkTWSkRR0xW3T3aEY9fifg@mail.gmail.com>
 <CAAUk9C5F1ZU8tzGGrgvbpOgrFSwg=Hipnd4cTcKWhOw+drV80g@mail.gmail.com>
Message-ID: <CADHSJjCYpyJrTZhRnU4YkrpGksp80sWywnr=0x73D0Ah=E14tg@mail.gmail.com>

Attached.

On Mon, Jun 6, 2016 at 12:59 PM, Peter Debuchev <peterdebuchev at gmail.com> wrote:
> Dear Utkarsh,
> thank you for your offer to search the old ParaView Guide v3 client-server
> programming chapter. May I ask whether your search has been successful? Even
> a scan of the pages from the relevant chapter would be nice, if you are
> authorized to share it.
>
> I have read all your links, and they are great to get an idea about the
> changes that are going on. However, I would need a well structured
> book-chapter which builds the story from the basic requirements to a full,
> simple application. The information in the links is so spread that
> everything seems to depend on everything else, and nowhere is it clear what
> are ideas for the future, what is under current development, and what has
> been deprecated again.
> I would really like to read again the chapter from ParaView Guide v3, which
> I remember gave me perfect insight into Paraview years ago. Even if it is
> rather out of date, it would give me a solid basis to better understand the
> current developments.
>
> Peter
>
> 2016-06-02 14:43 GMT+02:00 Utkarsh Ayachit <utkarsh.ayachit at kitware.com>:
>>
>> Alas, there's nothing up-to-date. I've been meaning to write a blog
>> series covering various aspect of ParaView internals, but it's hard to
>> find some downtime to get that going. I'll try to see if I can find
>> the old PDF for the ParaView Guide v3 and share the old chapter
>> (although obsolete, but basic design may still be relevant). The
>> ParaView developers Wiki
>> (http://www.paraview.org/ParaView/index.php/Main_Page) has a few
>> articles that we wrote with coming up with the design for some of the
>> core components. The implementations generally differ slightly from
>> the design and may have names/APIs changed since, but nonetheless may
>> be helpful in understanding how things came about. Specifically,
>>
>> [1] http://www.paraview.org/ParaView/index.php/ServerManager_2.0
>> [2] http://www.paraview.org/ParaView/index.php/ProcessModule_2.0
>> [3] http://www.paraview.org/ParaView/index.php/Views_And_Representations
>> [4]
>> http://www.paraview.org/ParaView/images/2/24/ParaViewCollaborationChanges.pdf
>>
>> Utkarsh
>>
>> On Thu, Jun 2, 2016 at 5:19 AM, Ellon Paiva <ellonpaiva at gmail.com> wrote:
>> > +1 for that. I'm very interested to know if there's such book or
>> > document.
>> >
>> > When I started developing a plug-in for ParaView I found this
>> > presentation
>> > almost by accident. Maybe it can help you. Apparently it was used in a
>> > conference/workshop (VIS08?) to describe briefly the proxy system, and
>> > refers to the "Paraview Guide, Version 3, section 18.6, and chapter 19
>> > for
>> > details (see slide 30). Unfortunately the version 3 of the Guide I
>> > couldn't
>> > find.
>> >
>> > Ellon
>> >
>> >
>> > On 06/02/2016 07:35 AM, Peter Debuchev wrote:
>> >
>> > Is any introduction available, how vtkSMServerManager, vtkSMSessions,
>> > vtkProxies etc. are set up to interact with a pvserver or with a custom
>> > server application?
>> > I am not talking about short demos that show how to create and display a
>> > sphere using pvpython. What I am looking for is a book chapter or
>> > similar
>> > explaining the principles behind vtkSMSessions, vtkProcies etc.
>> >
>> > Does anybody remember, which of the VTK or ITK or Paraview books
>> > included
>> > such chapters?
>> >
>> > Peter
>> >
>> > 2016-05-29 19:09 GMT+02:00 Peter Debuchev <peterdebuchev at gmail.com>:
>> >>
>> >> Dear Paraview programmers,
>> >> I am looking for some information about the basic principles of
>> >> Paraviews
>> >> client-server model, the setup of client proxies and the communication
>> >> design.
>> >>
>> >> I think that I have seen a chapter with a short introduction on these
>> >> topics some years ago. It was in one of the VTK books or in the
>> >> Paraview
>> >> User's Guide. Now I cannot find this chapter again. Has it been removed
>> >> in
>> >> the latest edition of these books? Or is it described in a different
>> >> book
>> >> which I don't remember?
>> >>
>> >> Peter
>> >
>> >
>> >
>> >
>> > _______________________________________________
>> > 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
>
>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ServerManagerChapter.pdf
Type: application/pdf
Size: 327922 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160606/94f130c2/attachment-0001.pdf>

From utkarsh.ayachit at kitware.com  Mon Jun  6 13:53:30 2016
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Mon, 6 Jun 2016 13:53:30 -0400
Subject: [Paraview] [Non-DoD Source] Re: 5.0.1/Exodus Reader
	(UNCLASSIFIED)
In-Reply-To: <CADHSJjCvPLuG-iR4uxBdtQ4Rw0sBYqET9td2wRQMiErhGQxr2w@mail.gmail.com>
References: <10A03274360DCF47A6EE78C9952A31CA639745D1@UMECHPA7C.easf.csd.disa.mil>
 <CADHSJjAOCZ-oCuOrXF9awJUva5K7kXWAMZ=HToRVTS2f94w1BA@mail.gmail.com>
 <10A03274360DCF47A6EE78C9952A31CA6397B5E0@UMECHPA7C.easf.csd.disa.mil>
 <CADHSJjCvPLuG-iR4uxBdtQ4Rw0sBYqET9td2wRQMiErhGQxr2w@mail.gmail.com>
Message-ID: <CADHSJjCjs30T7zH1StCidpSGrSA-HrJDWPRojok8WqQ30k+OHw@mail.gmail.com>

Here's a MR for update superbuild that builds OSMesa 11.2.2. I've only
updated OSMesa. I'll tackle mesa-glx next.

https://gitlab.kitware.com/paraview/paraview-superbuild/merge_requests/114

Utkarsh

On Mon, Jun 6, 2016 at 12:31 PM, Utkarsh Ayachit
<utkarsh.ayachit at kitware.com> wrote:
> I am working on updating superbuild today. Just hold on. I'll email
> once I have it working.
>
> On Mon, Jun 6, 2016 at 12:00 PM, Hennessey, Joseph G CTR USARMY RDECOM
> ARL (US) <joseph.g.hennessey2.ctr at mail.mil> wrote:
>> CLASSIFICATION: UNCLASSIFIED
>>
>> Utkarsh,
>>
>> I have rebuilt osmesa using mesa 11.2.2 but
>> it ParaView rebuilt with the new version is giving
>> me the same error as before, complaining that the
>> GL version 2.1 with gpu_shader4 extension is not
>> Supported.
>>
>> I think I know  why  this is occurring and I wondered if you
>> could confirm this for me.
>>
>> I configured mesa with these parameters
>>
>> ./configure \
>>     --disable-xvmc \
>>     --disable-glx \
>>     --disable-dri \
>>     --with-dri-drivers= \
>>     --with-gallium-drivers=swrast \
>>     --enable-texture-float \
>>     --disable-egl \
>>     --with-egl-platforms= \
>>     --enable-gallium-osmesa \
>>     --enable-gallium-llvm=yes \
>>     --prefix=<install prefix>
>>
>> but, I did not have a version of llvm available
>> and the configure script then set
>>
>> Llvm = no
>>
>> From my reading of this webpage
>>
>> http://www.paraview.org/Wiki/ParaView/ParaView_And_Mesa_3D
>>
>> It seems that without gallium-llvm,
>> the version of OpenGL built reverts to an older version,
>> which I believe is why I am still getting the error.
>>
>> Would you agree with this?
>>
>> Thanks,
>>
>> Joe
>>
>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>> Joseph G. Hennessey Ph.D., Lockheed Martin
>> Army Research Lab
>> DOD Supercomputing Resource Center
>>
>>
>> -----Original Message-----
>> From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com]
>> Sent: Thursday, June 02, 2016 4:19 PM
>> To: Hennessey, Joseph G CTR USARMY RDECOM ARL (US)
>> <joseph.g.hennessey2.ctr at mail.mil>
>> Cc: Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US)
>> <richard.c.angelini.civ at mail.mil>; Su, Simon M CIV USARMY RDECOM ARL (US)
>> <simon.m.su.civ at mail.mil>; ParaView <paraview at paraview.org>
>> Subject: Re: [Paraview] [Non-DoD Source] Re: 5.0.1/Exodus Reader
>> (UNCLASSIFIED)
>>
>> All active links contained in this email were disabled.  Please verify the
>> identity of the sender, and confirm the authenticity of all links contained
>> within the message prior to copying and pasting the address to a Web browser.
>>
>>
>>
>>
>> ----
>>
>>> And I have tried replacing the library
>>> lib/paraview-5.0/libOSMesa.so.7
>>> with both libOSMesa.so from 11.1.2 and 11.2.2 and they are both still
>>> giving the same error
>>
>> Simply swapping the libraries won't work. Mesa 11.2 [1] added new API
>> OSMesaCreateContextAttribs() which is needed to create correct OpenGL context.
>> The API is used at compile time if appropriate osmesa.h is being used.
>>
>> You can try to update Projects/unix/osmesa.cmake in the superbuild source to
>> use the configure arguments you used, and also change versions.cmake in the
>> same repo to point to change the osmesa source tar ball to be 11.2. Now the
>> superbuid will build 11.2 instead and it should then have the new API
>> available.
>>
>> [1] Caution-http://www.mesa3d.org/relnotes/11.2.0.html
>>
>>
>> CLASSIFICATION: UNCLASSIFIED

From peterdebuchev at gmail.com  Mon Jun  6 16:03:16 2016
From: peterdebuchev at gmail.com (Peter Debuchev)
Date: Mon, 6 Jun 2016 22:03:16 +0200
Subject: [Paraview] basics of paraview client server programming
In-Reply-To: <CADHSJjCYpyJrTZhRnU4YkrpGksp80sWywnr=0x73D0Ah=E14tg@mail.gmail.com>
References: <CAAUk9C4i5x3UF0bYC0FUVpJtR6LUrrS00qnN_dJi2CXFOJo_mg@mail.gmail.com>
 <CAAUk9C6YsFEt=b=RWMwGS3WfUO+iGFXs5NEc3RB0L9digST8=A@mail.gmail.com>
 <574FFA35.5040701@gmail.com>
 <CADHSJjCX0VagGF-8Tkj=Ro8mbSsEFkTWSkRR0xW3T3aEY9fifg@mail.gmail.com>
 <CAAUk9C5F1ZU8tzGGrgvbpOgrFSwg=Hipnd4cTcKWhOw+drV80g@mail.gmail.com>
 <CADHSJjCYpyJrTZhRnU4YkrpGksp80sWywnr=0x73D0Ah=E14tg@mail.gmail.com>
Message-ID: <CAAUk9C6-CBvtFXXQAYtt6e4LMTw1_U93m2xc9HeujW8P5gZeQw@mail.gmail.com>

Excellent, thank you!

2016-06-06 19:01 GMT+02:00 Utkarsh Ayachit <utkarsh.ayachit at kitware.com>:

> Attached.
>
> On Mon, Jun 6, 2016 at 12:59 PM, Peter Debuchev <peterdebuchev at gmail.com>
> wrote:
> > Dear Utkarsh,
> > thank you for your offer to search the old ParaView Guide v3
> client-server
> > programming chapter. May I ask whether your search has been successful?
> Even
> > a scan of the pages from the relevant chapter would be nice, if you are
> > authorized to share it.
> >
> > I have read all your links, and they are great to get an idea about the
> > changes that are going on. However, I would need a well structured
> > book-chapter which builds the story from the basic requirements to a
> full,
> > simple application. The information in the links is so spread that
> > everything seems to depend on everything else, and nowhere is it clear
> what
> > are ideas for the future, what is under current development, and what has
> > been deprecated again.
> > I would really like to read again the chapter from ParaView Guide v3,
> which
> > I remember gave me perfect insight into Paraview years ago. Even if it is
> > rather out of date, it would give me a solid basis to better understand
> the
> > current developments.
> >
> > Peter
> >
> > 2016-06-02 14:43 GMT+02:00 Utkarsh Ayachit <utkarsh.ayachit at kitware.com
> >:
> >>
> >> Alas, there's nothing up-to-date. I've been meaning to write a blog
> >> series covering various aspect of ParaView internals, but it's hard to
> >> find some downtime to get that going. I'll try to see if I can find
> >> the old PDF for the ParaView Guide v3 and share the old chapter
> >> (although obsolete, but basic design may still be relevant). The
> >> ParaView developers Wiki
> >> (http://www.paraview.org/ParaView/index.php/Main_Page) has a few
> >> articles that we wrote with coming up with the design for some of the
> >> core components. The implementations generally differ slightly from
> >> the design and may have names/APIs changed since, but nonetheless may
> >> be helpful in understanding how things came about. Specifically,
> >>
> >> [1] http://www.paraview.org/ParaView/index.php/ServerManager_2.0
> >> [2] http://www.paraview.org/ParaView/index.php/ProcessModule_2.0
> >> [3]
> http://www.paraview.org/ParaView/index.php/Views_And_Representations
> >> [4]
> >>
> http://www.paraview.org/ParaView/images/2/24/ParaViewCollaborationChanges.pdf
> >>
> >> Utkarsh
> >>
> >> On Thu, Jun 2, 2016 at 5:19 AM, Ellon Paiva <ellonpaiva at gmail.com>
> wrote:
> >> > +1 for that. I'm very interested to know if there's such book or
> >> > document.
> >> >
> >> > When I started developing a plug-in for ParaView I found this
> >> > presentation
> >> > almost by accident. Maybe it can help you. Apparently it was used in a
> >> > conference/workshop (VIS08?) to describe briefly the proxy system, and
> >> > refers to the "Paraview Guide, Version 3, section 18.6, and chapter 19
> >> > for
> >> > details (see slide 30). Unfortunately the version 3 of the Guide I
> >> > couldn't
> >> > find.
> >> >
> >> > Ellon
> >> >
> >> >
> >> > On 06/02/2016 07:35 AM, Peter Debuchev wrote:
> >> >
> >> > Is any introduction available, how vtkSMServerManager, vtkSMSessions,
> >> > vtkProxies etc. are set up to interact with a pvserver or with a
> custom
> >> > server application?
> >> > I am not talking about short demos that show how to create and
> display a
> >> > sphere using pvpython. What I am looking for is a book chapter or
> >> > similar
> >> > explaining the principles behind vtkSMSessions, vtkProcies etc.
> >> >
> >> > Does anybody remember, which of the VTK or ITK or Paraview books
> >> > included
> >> > such chapters?
> >> >
> >> > Peter
> >> >
> >> > 2016-05-29 19:09 GMT+02:00 Peter Debuchev <peterdebuchev at gmail.com>:
> >> >>
> >> >> Dear Paraview programmers,
> >> >> I am looking for some information about the basic principles of
> >> >> Paraviews
> >> >> client-server model, the setup of client proxies and the
> communication
> >> >> design.
> >> >>
> >> >> I think that I have seen a chapter with a short introduction on these
> >> >> topics some years ago. It was in one of the VTK books or in the
> >> >> Paraview
> >> >> User's Guide. Now I cannot find this chapter again. Has it been
> removed
> >> >> in
> >> >> the latest edition of these books? Or is it described in a different
> >> >> book
> >> >> which I don't remember?
> >> >>
> >> >> Peter
> >> >
> >> >
> >> >
> >> >
> >> > _______________________________________________
> >> > 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
> >
> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160606/da2110e4/attachment.html>

From peterdebuchev at gmail.com  Tue Jun  7 08:54:00 2016
From: peterdebuchev at gmail.com (Peter Debuchev)
Date: Tue, 7 Jun 2016 14:54:00 +0200
Subject: [Paraview] vtkSMCollaborationManager::FollowUser(id) doesn't update
	view
Message-ID: <CAAUk9C4oh6fOkvh_yfaaXD4x6yoXe+--YiWfHL62oBmg-k3UQw@mail.gmail.com>

Hello,
I have attached a short custom client example which I would like to always
show the same perspective as a ParaView session connected to the same
pvserver.

However, although this example renders once the objects that are available
in the ParaView session, it does not update itself when the camera is
changed in ParaView, despite of the line
"collaboration->FollowUser(collaboration->GetMasterId());" (see attached
code).

Apparently I am missing one important step, maybe register the view with
some proxymanager, call some *::AddObserver(...) or something similar? I
don't know and couldn't find out after several attempts to understand
ParaView with the help of a debugger.

As a side note: collaboration in the other direction runs successfully. If
I choose ParaView to follow this custom client by double-clicking on the
eye symbol in the collaboration panel, then the ParaView view always
displays the same perspective as the custom client.

Which are the missing steps to have the client update its view, when the
(master) ParaView camera changes?

Steps to reproduce:
+ compile attached main.cxx
+ run "pvserver --multi-clients &"
+ run "paraview --server-url=cs://localhost:11111 &"
+ create a simple pipeline in paraview
+ run "./main" -> same pipeline as in paraview is rendered in custom client
+ interact with view in ParaView -> client view does not update although it
is expected to follow the master

Peter
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160607/f61515c6/attachment.html>
-------------- next part --------------
project(myClient)

add_definitions(-std=c++11)
FIND_PACKAGE(ParaView REQUIRED)
INCLUDE( ${PARAVIEW_USE_FILE})

add_executable(main main.cxx)
target_link_libraries(main ${VTK_LIBRARIES})
-------------- next part --------------
A non-text attachment was scrubbed...
Name: main.cxx
Type: text/x-c++src
Size: 3365 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160607/f61515c6/attachment.cxx>

From utkarsh.ayachit at kitware.com  Tue Jun  7 10:58:42 2016
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Tue, 7 Jun 2016 10:58:42 -0400
Subject: [Paraview] vtkSMCollaborationManager::FollowUser(id) doesn't
 update view
In-Reply-To: <CAAUk9C4oh6fOkvh_yfaaXD4x6yoXe+--YiWfHL62oBmg-k3UQw@mail.gmail.com>
References: <CAAUk9C4oh6fOkvh_yfaaXD4x6yoXe+--YiWfHL62oBmg-k3UQw@mail.gmail.com>
Message-ID: <CADHSJjCLJ4=AfAFxPsmYWw0wn8WuKjDS5xeh8SUwJPqvydjRtg@mail.gmail.com>

See pqServer::processServerNotification() [1]. You'll need to call
vtkNetworkAccessManager::ProcessEvents(..) "on idle" to process events
being received from the other client.


[1] https://gitlab.kitware.com/paraview/paraview/blob/master/Qt/Core/pqServer.cxx#L376-401

On Tue, Jun 7, 2016 at 8:54 AM, Peter Debuchev <peterdebuchev at gmail.com> wrote:
> Hello,
> I have attached a short custom client example which I would like to always
> show the same perspective as a ParaView session connected to the same
> pvserver.
>
> However, although this example renders once the objects that are available
> in the ParaView session, it does not update itself when the camera is
> changed in ParaView, despite of the line
> "collaboration->FollowUser(collaboration->GetMasterId());" (see attached
> code).
>
> Apparently I am missing one important step, maybe register the view with
> some proxymanager, call some *::AddObserver(...) or something similar? I
> don't know and couldn't find out after several attempts to understand
> ParaView with the help of a debugger.
>
> As a side note: collaboration in the other direction runs successfully. If I
> choose ParaView to follow this custom client by double-clicking on the eye
> symbol in the collaboration panel, then the ParaView view always displays
> the same perspective as the custom client.
>
> Which are the missing steps to have the client update its view, when the
> (master) ParaView camera changes?
>
> Steps to reproduce:
> + compile attached main.cxx
> + run "pvserver --multi-clients &"
> + run "paraview --server-url=cs://localhost:11111 &"
> + create a simple pipeline in paraview
> + run "./main" -> same pipeline as in paraview is rendered in custom client
> + interact with view in ParaView -> client view does not update although it
> is expected to follow the master
>
> Peter
>
> _______________________________________________
> 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 richard.c.angelini.civ at mail.mil  Tue Jun  7 11:22:36 2016
From: richard.c.angelini.civ at mail.mil (Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US))
Date: Tue, 7 Jun 2016 15:22:36 +0000
Subject: [Paraview] [Non-DoD Source] Re: 5.0.1/Exodus Reader
 (UNCLASSIFIED)
In-Reply-To: <CADHSJjCjs30T7zH1StCidpSGrSA-HrJDWPRojok8WqQ30k+OHw@mail.gmail.com>
References: <10A03274360DCF47A6EE78C9952A31CA639745D1@UMECHPA7C.easf.csd.disa.mil>
 <CADHSJjAOCZ-oCuOrXF9awJUva5K7kXWAMZ=HToRVTS2f94w1BA@mail.gmail.com>
 <10A03274360DCF47A6EE78C9952A31CA6397B5E0@UMECHPA7C.easf.csd.disa.mil>
 <CADHSJjCvPLuG-iR4uxBdtQ4Rw0sBYqET9td2wRQMiErhGQxr2w@mail.gmail.com>
 <CADHSJjCjs30T7zH1StCidpSGrSA-HrJDWPRojok8WqQ30k+OHw@mail.gmail.com>
Message-ID: <D37C5E99.2BB3C%Richard.C.Angelini.CIV@mail.mil>

Utkarsh - I was able to get a clean build with this OSMesa patch - but it
looks like the OSMesa pvserver is not compatible with the production 5.0.1
client??????

ERROR: In 
/usr/people/angel/PV/5.0.1/Build_5.0.1_osmesa/paraview/src/paraview/VTK/Par
allel/Core/vtkSocketCommunicator.cxx, line 558
vtkSocketCommunicator (0x12324f0): Endian handshake failed.

ERROR: In 
/usr/people/angel/PV/5.0.1/Build_5.0.1_osmesa/paraview/src/paraview/ParaVie
wCore/ClientServerCore/Core/vtkTCPNetworkAccessManager.cxx, line 33
0
vtkTCPNetworkAccessManager (0x6612b0): Failed to connect to
excalibur03-int:22886

ERROR: In 
/usr/people/angel/PV/5.0.1/Build_5.0.1_osmesa/paraview/src/paraview/ParaVie
wCore/ClientServerCore/Core/vtkTCPNetworkAccessManager.cxx, line 34
0
vtkTCPNetworkAccessManager (0x6612b0):
**********************************************************************
Connection failed during handshake. This can happen for the following
reasons:
 1. Connection dropped during the handshake.
 2. vtkSocketCommunicator::GetVersion() returns different values on the
    two connecting processes (Current value: 100).
 3. ParaView handshake strings are different on the two connecting
    processes (Current value: paraview.5.0.connect_id.9407).
**********************************************************************





________________________________
Rick Angelini
USArmy Research Laboratory
CISD/HPC Architectures Team
Phone:  410-278-6266




-----Original Message-----
From: Utkarsh Ayachit <utkarsh.ayachit at kitware.com>
Date: Monday, June 6, 2016 at 1:53 PM
To: "Hennessey, Joseph G CTR USARMY RDECOM ARL (US)"
<joseph.g.hennessey2.ctr at mail.mil>
Cc: Rick Angelini <Richard.C.Angelini.CIV at mail.mil>, Simon Su
<simon.m.su.CIV at mail.mil>, ParaView <paraview at paraview.org>
Subject: Re: [Paraview] [Non-DoD Source] Re: 5.0.1/Exodus Reader
(UNCLASSIFIED)

All active links contained in this email were disabled.  Please verify the
identity of the sender, and confirm the authenticity of all links
contained within the message prior to copying and pasting the address to a
Web browser.  




----

Here's a MR for update superbuild that builds OSMesa 11.2.2. I've only
updated OSMesa. I'll tackle mesa-glx next.

Caution-https://gitlab.kitware.com/paraview/paraview-superbuild/merge_reque
sts/114

Utkarsh

On Mon, Jun 6, 2016 at 12:31 PM, Utkarsh Ayachit
<utkarsh.ayachit at kitware.com> wrote:
> I am working on updating superbuild today. Just hold on. I'll email
> once I have it working.
>
> On Mon, Jun 6, 2016 at 12:00 PM, Hennessey, Joseph G CTR USARMY RDECOM
> ARL (US) <joseph.g.hennessey2.ctr at mail.mil> wrote:
>> CLASSIFICATION: UNCLASSIFIED
>>
>> Utkarsh,
>>
>> I have rebuilt osmesa using mesa 11.2.2 but
>> it ParaView rebuilt with the new version is giving
>> me the same error as before, complaining that the
>> GL version 2.1 with gpu_shader4 extension is not
>> Supported.
>>
>> I think I know  why  this is occurring and I wondered if you
>> could confirm this for me.
>>
>> I configured mesa with these parameters
>>
>> ./configure \
>>     --disable-xvmc \
>>     --disable-glx \
>>     --disable-dri \
>>     --with-dri-drivers= \
>>     --with-gallium-drivers=swrast \
>>     --enable-texture-float \
>>     --disable-egl \
>>     --with-egl-platforms= \
>>     --enable-gallium-osmesa \
>>     --enable-gallium-llvm=yes \
>>     --prefix=<install prefix>
>>
>> but, I did not have a version of llvm available
>> and the configure script then set
>>
>> Llvm = no
>>
>> From my reading of this webpage
>>
>> Caution-http://www.paraview.org/Wiki/ParaView/ParaView_And_Mesa_3D
>>
>> It seems that without gallium-llvm,
>> the version of OpenGL built reverts to an older version,
>> which I believe is why I am still getting the error.
>>
>> Would you agree with this?
>>
>> Thanks,
>>
>> Joe
>>
>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>> Joseph G. Hennessey Ph.D., Lockheed Martin
>> Army Research Lab
>> DOD Supercomputing Resource Center
>>
>>
>> -----Original Message-----
>> From: Utkarsh Ayachit [Caution-mailto:utkarsh.ayachit at kitware.com]
>> Sent: Thursday, June 02, 2016 4:19 PM
>> To: Hennessey, Joseph G CTR USARMY RDECOM ARL (US)
>> <joseph.g.hennessey2.ctr at mail.mil>
>> Cc: Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US)
>> <richard.c.angelini.civ at mail.mil>; Su, Simon M CIV USARMY RDECOM ARL
>>(US)
>> <simon.m.su.civ at mail.mil>; ParaView <paraview at paraview.org>
>> Subject: Re: [Paraview] [Non-DoD Source] Re: 5.0.1/Exodus Reader
>> (UNCLASSIFIED)
>>
>> All active links contained in this email were disabled.  Please verify
>>the
>> identity of the sender, and confirm the authenticity of all links
>>contained
>> within the message prior to copying and pasting the address to a Web
>>browser.
>>
>>
>>
>>
>> ----
>>
>>> And I have tried replacing the library
>>> lib/paraview-5.0/libOSMesa.so.7
>>> with both libOSMesa.so from 11.1.2 and 11.2.2 and they are both still
>>> giving the same error
>>
>> Simply swapping the libraries won't work. Mesa 11.2 [1] added new API
>> OSMesaCreateContextAttribs() which is needed to create correct OpenGL
>>context.
>> The API is used at compile time if appropriate osmesa.h is being used.
>>
>> You can try to update Projects/unix/osmesa.cmake in the superbuild
>>source to
>> use the configure arguments you used, and also change versions.cmake in
>>the
>> same repo to point to change the osmesa source tar ball to be 11.2. Now
>>the
>> superbuid will build 11.2 instead and it should then have the new API
>> available.
>>
>> [1] Caution-Caution-http://www.mesa3d.org/relnotes/11.2.0.html
>>
>>
>> CLASSIFICATION: UNCLASSIFIED


From utkarsh.ayachit at kitware.com  Tue Jun  7 11:30:32 2016
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Tue, 7 Jun 2016 11:30:32 -0400
Subject: [Paraview] [Non-DoD Source] Re: 5.0.1/Exodus Reader
	(UNCLASSIFIED)
In-Reply-To: <D37C5E99.2BB3C%Richard.C.Angelini.CIV@mail.mil>
References: <10A03274360DCF47A6EE78C9952A31CA639745D1@UMECHPA7C.easf.csd.disa.mil>
 <CADHSJjAOCZ-oCuOrXF9awJUva5K7kXWAMZ=HToRVTS2f94w1BA@mail.gmail.com>
 <10A03274360DCF47A6EE78C9952A31CA6397B5E0@UMECHPA7C.easf.csd.disa.mil>
 <CADHSJjCvPLuG-iR4uxBdtQ4Rw0sBYqET9td2wRQMiErhGQxr2w@mail.gmail.com>
 <CADHSJjCjs30T7zH1StCidpSGrSA-HrJDWPRojok8WqQ30k+OHw@mail.gmail.com>
 <D37C5E99.2BB3C%Richard.C.Angelini.CIV@mail.mil>
Message-ID: <CADHSJjAOKCU948+e6nB1XWGMCSHn11OLoD3EhfGxqNHR=B=qwg@mail.gmail.com>

> Utkarsh - I was able to get a clean build with this OSMesa patch - but it
> looks like the OSMesa pvserver is not compatible with the production 5.0.1
> client??????

That's not the case. It should be compatible, so long are you're
building 5.0.1 on the server side too.

> **********************************************************************
> Connection failed during handshake. This can happen for the following
> reasons:
>  1. Connection dropped during the handshake.
>  2. vtkSocketCommunicator::GetVersion() returns different values on the
>     two connecting processes (Current value: 100).
>  3. ParaView handshake strings are different on the two connecting
>     processes (Current value: paraview.5.0.connect_id.9407).
> **********************************************************************

This message is printed on both client and server. See the value for
item 3. Do they match? Looks like you're using connection ids. Are
they being specified appropriately on both ends?

From richard.c.angelini.civ at mail.mil  Tue Jun  7 11:48:39 2016
From: richard.c.angelini.civ at mail.mil (Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US))
Date: Tue, 7 Jun 2016 15:48:39 +0000
Subject: [Paraview] [Non-DoD Source] Re: 5.0.1/Exodus Reader
 (UNCLASSIFIED)
In-Reply-To: <CADHSJjAOKCU948+e6nB1XWGMCSHn11OLoD3EhfGxqNHR=B=qwg@mail.gmail.com>
References: <10A03274360DCF47A6EE78C9952A31CA639745D1@UMECHPA7C.easf.csd.disa.mil>
 <CADHSJjAOCZ-oCuOrXF9awJUva5K7kXWAMZ=HToRVTS2f94w1BA@mail.gmail.com>
 <10A03274360DCF47A6EE78C9952A31CA6397B5E0@UMECHPA7C.easf.csd.disa.mil>
 <CADHSJjCvPLuG-iR4uxBdtQ4Rw0sBYqET9td2wRQMiErhGQxr2w@mail.gmail.com>
 <CADHSJjCjs30T7zH1StCidpSGrSA-HrJDWPRojok8WqQ30k+OHw@mail.gmail.com>
 <D37C5E99.2BB3C%Richard.C.Angelini.CIV@mail.mil>
 <CADHSJjAOKCU948+e6nB1XWGMCSHn11OLoD3EhfGxqNHR=B=qwg@mail.gmail.com>
Message-ID: <D37C64CA.2BB49%Richard.C.Angelini.CIV@mail.mil>

I used the same job launching scripts that I use for all of the previous
versions, including the broken attempts at 5.0.1 OSMesa builds  which were
able to connect and launch (and eventually fail).
________________________________
Rick Angelini
USArmy Research Laboratory
CISD/HPC Architectures Team
Phone:  410-278-6266




-----Original Message-----
From: Utkarsh Ayachit <utkarsh.ayachit at kitware.com>
Date: Tuesday, June 7, 2016 at 11:30 AM
To: Rick Angelini <Richard.C.Angelini.CIV at mail.mil>
Cc: "Hennessey, Joseph G CTR USARMY RDECOM ARL (US)"
<joseph.g.hennessey2.ctr at mail.mil>, Simon Su <simon.m.su.CIV at mail.mil>,
ParaView <paraview at paraview.org>
Subject: Re: [Paraview] [Non-DoD Source] Re: 5.0.1/Exodus Reader
(UNCLASSIFIED)

> Utkarsh - I was able to get a clean build with this OSMesa patch - but it
> looks like the OSMesa pvserver is not compatible with the production
>5.0.1
> client??????

That's not the case. It should be compatible, so long are you're
building 5.0.1 on the server side too.

> **********************************************************************
> Connection failed during handshake. This can happen for the following
> reasons:
>  1. Connection dropped during the handshake.
>  2. vtkSocketCommunicator::GetVersion() returns different values on the
>     two connecting processes (Current value: 100).
>  3. ParaView handshake strings are different on the two connecting
>     processes (Current value: paraview.5.0.connect_id.9407).
> **********************************************************************

This message is printed on both client and server. See the value for
item 3. Do they match? Looks like you're using connection ids. Are
they being specified appropriately on both ends?


From richard.c.angelini.civ at mail.mil  Tue Jun  7 12:31:24 2016
From: richard.c.angelini.civ at mail.mil (Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US))
Date: Tue, 7 Jun 2016 16:31:24 +0000
Subject: [Paraview] [Non-DoD Source] Re: 5.0.1/Exodus Reader
 (UNCLASSIFIED)
In-Reply-To: <CADHSJjAOKCU948+e6nB1XWGMCSHn11OLoD3EhfGxqNHR=B=qwg@mail.gmail.com>
References: <10A03274360DCF47A6EE78C9952A31CA639745D1@UMECHPA7C.easf.csd.disa.mil>
 <CADHSJjAOCZ-oCuOrXF9awJUva5K7kXWAMZ=HToRVTS2f94w1BA@mail.gmail.com>
 <10A03274360DCF47A6EE78C9952A31CA6397B5E0@UMECHPA7C.easf.csd.disa.mil>
 <CADHSJjCvPLuG-iR4uxBdtQ4Rw0sBYqET9td2wRQMiErhGQxr2w@mail.gmail.com>
 <CADHSJjCjs30T7zH1StCidpSGrSA-HrJDWPRojok8WqQ30k+OHw@mail.gmail.com>
 <D37C5E99.2BB3C%Richard.C.Angelini.CIV@mail.mil>
 <CADHSJjAOKCU948+e6nB1XWGMCSHn11OLoD3EhfGxqNHR=B=qwg@mail.gmail.com>
Message-ID: <D37C6EFE.2BB56%Richard.C.Angelini.CIV@mail.mil>

We did indeed build 5.0.1 (with your updates) and the connect_id is the
same on both ends ?..


________________________________
Rick Angelini
USArmy Research Laboratory
CISD/HPC Architectures Team
Phone:  410-278-6266




-----Original Message-----
From: Utkarsh Ayachit <utkarsh.ayachit at kitware.com>
Date: Tuesday, June 7, 2016 at 11:30 AM
To: Rick Angelini <Richard.C.Angelini.CIV at mail.mil>
Cc: "Hennessey, Joseph G CTR USARMY RDECOM ARL (US)"
<joseph.g.hennessey2.ctr at mail.mil>, Simon Su <simon.m.su.CIV at mail.mil>,
ParaView <paraview at paraview.org>
Subject: Re: [Paraview] [Non-DoD Source] Re: 5.0.1/Exodus Reader
(UNCLASSIFIED)

> Utkarsh - I was able to get a clean build with this OSMesa patch - but it
> looks like the OSMesa pvserver is not compatible with the production
>5.0.1
> client??????

That's not the case. It should be compatible, so long are you're
building 5.0.1 on the server side too.

> **********************************************************************
> Connection failed during handshake. This can happen for the following
> reasons:
>  1. Connection dropped during the handshake.
>  2. vtkSocketCommunicator::GetVersion() returns different values on the
>     two connecting processes (Current value: 100).
>  3. ParaView handshake strings are different on the two connecting
>     processes (Current value: paraview.5.0.connect_id.9407).
> **********************************************************************

This message is printed on both client and server. See the value for
item 3. Do they match? Looks like you're using connection ids. Are
they being specified appropriately on both ends?


From peterdebuchev at gmail.com  Tue Jun  7 12:40:41 2016
From: peterdebuchev at gmail.com (Peter Debuchev)
Date: Tue, 7 Jun 2016 18:40:41 +0200
Subject: [Paraview] vtkSMCollaborationManager::FollowUser(id) doesn't
 update view
In-Reply-To: <CADHSJjCLJ4=AfAFxPsmYWw0wn8WuKjDS5xeh8SUwJPqvydjRtg@mail.gmail.com>
References: <CAAUk9C4oh6fOkvh_yfaaXD4x6yoXe+--YiWfHL62oBmg-k3UQw@mail.gmail.com>
 <CADHSJjCLJ4=AfAFxPsmYWw0wn8WuKjDS5xeh8SUwJPqvydjRtg@mail.gmail.com>
Message-ID: <CAAUk9C7mTR1jySzX7XHn8cnHCGh2hObw-n28LrssORcVD_=hyg@mail.gmail.com>

Thanks for the reply, but vtkNetworkAccessManager::ProcessEvents() is
already called in the attached example every 100ms repeatedly until it
returns false.
See my code at Callback::Execute(). The Timer Callback is started towards
the end of main.cxx, where it says "Callback *timer=Callback::New();" and
the following lines.

If you run the example as described, you'll see that actually a number of
messages are processed (their number is being logged). But I don't know how
I can print the content of the received vtkSMMessages for debugging
purposes. And I don't know what else to do so that the custom client's
camera will be affected.

Peter

2016-06-07 16:58 GMT+02:00 Utkarsh Ayachit <utkarsh.ayachit at kitware.com>:

> See pqServer::processServerNotification() [1]. You'll need to call
> vtkNetworkAccessManager::ProcessEvents(..) "on idle" to process events
> being received from the other client.
>
>
> [1]
> https://gitlab.kitware.com/paraview/paraview/blob/master/Qt/Core/pqServer.cxx#L376-401
>
> On Tue, Jun 7, 2016 at 8:54 AM, Peter Debuchev <peterdebuchev at gmail.com>
> wrote:
> > Hello,
> > I have attached a short custom client example which I would like to
> always
> > show the same perspective as a ParaView session connected to the same
> > pvserver.
> >
> > However, although this example renders once the objects that are
> available
> > in the ParaView session, it does not update itself when the camera is
> > changed in ParaView, despite of the line
> > "collaboration->FollowUser(collaboration->GetMasterId());" (see attached
> > code).
> >
> > Apparently I am missing one important step, maybe register the view with
> > some proxymanager, call some *::AddObserver(...) or something similar? I
> > don't know and couldn't find out after several attempts to understand
> > ParaView with the help of a debugger.
> >
> > As a side note: collaboration in the other direction runs successfully.
> If I
> > choose ParaView to follow this custom client by double-clicking on the
> eye
> > symbol in the collaboration panel, then the ParaView view always displays
> > the same perspective as the custom client.
> >
> > Which are the missing steps to have the client update its view, when the
> > (master) ParaView camera changes?
> >
> > Steps to reproduce:
> > + compile attached main.cxx
> > + run "pvserver --multi-clients &"
> > + run "paraview --server-url=cs://localhost:11111 &"
> > + create a simple pipeline in paraview
> > + run "./main" -> same pipeline as in paraview is rendered in custom
> client
> > + interact with view in ParaView -> client view does not update although
> it
> > is expected to follow the master
> >
> > Peter
> >
> > _______________________________________________
> > 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/20160607/520cfbb4/attachment.html>

From utkarsh.ayachit at kitware.com  Tue Jun  7 12:41:30 2016
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Tue, 7 Jun 2016 12:41:30 -0400
Subject: [Paraview] [Non-DoD Source] Re: 5.0.1/Exodus Reader
	(UNCLASSIFIED)
In-Reply-To: <D37C6EFE.2BB56%Richard.C.Angelini.CIV@mail.mil>
References: <10A03274360DCF47A6EE78C9952A31CA639745D1@UMECHPA7C.easf.csd.disa.mil>
 <CADHSJjAOCZ-oCuOrXF9awJUva5K7kXWAMZ=HToRVTS2f94w1BA@mail.gmail.com>
 <10A03274360DCF47A6EE78C9952A31CA6397B5E0@UMECHPA7C.easf.csd.disa.mil>
 <CADHSJjCvPLuG-iR4uxBdtQ4Rw0sBYqET9td2wRQMiErhGQxr2w@mail.gmail.com>
 <CADHSJjCjs30T7zH1StCidpSGrSA-HrJDWPRojok8WqQ30k+OHw@mail.gmail.com>
 <D37C5E99.2BB3C%Richard.C.Angelini.CIV@mail.mil>
 <CADHSJjAOKCU948+e6nB1XWGMCSHn11OLoD3EhfGxqNHR=B=qwg@mail.gmail.com>
 <D37C6EFE.2BB56%Richard.C.Angelini.CIV@mail.mil>
Message-ID: <CADHSJjD+ZrgeALDy7MyNxrmMP46FwPDKW79qa9oc1LqOubtT4g@mail.gmail.com>

Can you attach your CMakeCache.txt please? Also, try this:

On server side:
./pvserver --version

On client side:
./paraview --version

What do they say?



On Tue, Jun 7, 2016 at 12:31 PM, Angelini, Richard C (Rick) CIV USARMY
RDECOM ARL (US) <richard.c.angelini.civ at mail.mil> wrote:
> We did indeed build 5.0.1 (with your updates) and the connect_id is the
> same on both ends ?..
>
>
> ________________________________
> Rick Angelini
> USArmy Research Laboratory
> CISD/HPC Architectures Team
> Phone:  410-278-6266
>
>
>
>
> -----Original Message-----
> From: Utkarsh Ayachit <utkarsh.ayachit at kitware.com>
> Date: Tuesday, June 7, 2016 at 11:30 AM
> To: Rick Angelini <Richard.C.Angelini.CIV at mail.mil>
> Cc: "Hennessey, Joseph G CTR USARMY RDECOM ARL (US)"
> <joseph.g.hennessey2.ctr at mail.mil>, Simon Su <simon.m.su.CIV at mail.mil>,
> ParaView <paraview at paraview.org>
> Subject: Re: [Paraview] [Non-DoD Source] Re: 5.0.1/Exodus Reader
> (UNCLASSIFIED)
>
>> Utkarsh - I was able to get a clean build with this OSMesa patch - but it
>> looks like the OSMesa pvserver is not compatible with the production
>>5.0.1
>> client??????
>
> That's not the case. It should be compatible, so long are you're
> building 5.0.1 on the server side too.
>
>> **********************************************************************
>> Connection failed during handshake. This can happen for the following
>> reasons:
>>  1. Connection dropped during the handshake.
>>  2. vtkSocketCommunicator::GetVersion() returns different values on the
>>     two connecting processes (Current value: 100).
>>  3. ParaView handshake strings are different on the two connecting
>>     processes (Current value: paraview.5.0.connect_id.9407).
>> **********************************************************************
>
> This message is printed on both client and server. See the value for
> item 3. Do they match? Looks like you're using connection ids. Are
> they being specified appropriately on both ends?
>

From michalwozniak at live.ca  Tue Jun  7 15:50:45 2016
From: michalwozniak at live.ca (michal wozniak)
Date: Tue, 7 Jun 2016 15:50:45 -0400
Subject: [Paraview] Coordinate Result from Calculator
Message-ID: <BLU180-W3990C386557A21F93F4E75AD5D0@phx.gbl>

Hi everyone, 
I am calculating the mean of two source point using the python calculator. Then I use the calculator filter to get the Coordinate Result. How do I access that value? 
in my pipeline, my Calculator1 produce a Coordinate Result Array  called "Result". What do I do to access this array to be able to use the coordinate? 
thanks 
Michal  		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160607/465d1565/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: pipeline.PNG
Type: image/png
Size: 16927 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160607/465d1565/attachment.png>

From wascott at sandia.gov  Tue Jun  7 19:13:43 2016
From: wascott at sandia.gov (Scott, W Alan)
Date: Tue, 7 Jun 2016 23:13:43 +0000
Subject: [Paraview] Moving clip plane
Message-ID: <ee1acf8aad764ce3a54d3f68753ff59b@ES01AMSNLNT.srn.sandia.gov>

Is there a way to create a clip plane and have it translate with a moving part so that the same material is clipped throughout?


Thanks,

Alan

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

From joachim.pouderoux at kitware.com  Wed Jun  8 07:48:27 2016
From: joachim.pouderoux at kitware.com (Joachim Pouderoux)
Date: Wed, 8 Jun 2016 13:48:27 +0200
Subject: [Paraview] Coordinate Result from Calculator
In-Reply-To: <BLU180-W3990C386557A21F93F4E75AD5D0@phx.gbl>
References: <BLU180-W3990C386557A21F93F4E75AD5D0@phx.gbl>
Message-ID: <CACJ=gTjesmdTaH0G1ybshOR2vnffq=fF6k9e-tDA1Pr103hj0Q@mail.gmail.com>

Michal,

Maybe I did not correctly understand your question but if you want to
access point coordinates in the Calculator, they are available through the
(pseudo) scalar variables coordsX, coordsY and coordsZ - you will find them
in the Scalars list button.

Regards,

*Joachim Pouderoux*

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


2016-06-07 21:50 GMT+02:00 michal wozniak <michalwozniak at live.ca>:

> Hi everyone,
>
> I am calculating the mean of two source point using the python calculator.
> Then I use the calculator filter to get the Coordinate Result.
> How do I access that value?
>
> in my pipeline, my Calculator1 produce a Coordinate Result Array  called
> "Result". What do I do to access this array to be able to use the
> coordinate?
>
> thanks
>
> Michal
>
> _______________________________________________
> 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/20160608/d561321f/attachment.html>

From michalwozniak at live.ca  Wed Jun  8 07:58:47 2016
From: michalwozniak at live.ca (michal wozniak)
Date: Wed, 8 Jun 2016 07:58:47 -0400
Subject: [Paraview] Coordinate Result from Calculator
In-Reply-To: <CACJ=gTjesmdTaH0G1ybshOR2vnffq=fF6k9e-tDA1Pr103hj0Q@mail.gmail.com>
References: <BLU180-W3990C386557A21F93F4E75AD5D0@phx.gbl>
 <CACJ=gTjesmdTaH0G1ybshOR2vnffq=fF6k9e-tDA1Pr103hj0Q@mail.gmail.com>
Message-ID: <BLU405-EAS148A1E3252ECE1143E70D0FAD5E0@phx.gbl>

Hi,

I would like to access it in a following programmable filter or for eg link the coordinate result from the calculator to the center property of a slice filter using the manager link

It more about being able to access the coordinate result in another filter  

On Jun 8, 2016 7:48 AM, Joachim Pouderoux <joachim.pouderoux at kitware.com> wrote:

Michal,

Maybe I did not correctly understand your question but if you want to access point coordinates in the Calculator, they are available through the (pseudo) scalar variables coordsX, coordsY and coordsZ - you will find them in the Scalars list button.

Regards,


Joachim Pouderoux

PhD, Technical Expert
Kitware SAS


2016-06-07 21:50 GMT+02:00 michal wozniak <michalwozniak at live.ca>:

Hi everyone, 


I am calculating the mean of two source point using the python calculator. Then I use the calculator filter to get the Coordinate Result. 

How do I access that value? 


in my pipeline, my Calculator1 produce a Coordinate Result Array  called "Result". What do I do to access this array to be able to use the coordinate? 


thanks 


Michal 

		 	 		 


_______________________________________________
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/20160608/95c4620f/attachment.html>

From dave.demarle at kitware.com  Wed Jun  8 08:50:05 2016
From: dave.demarle at kitware.com (David E DeMarle)
Date: Wed, 8 Jun 2016 08:50:05 -0400
Subject: [Paraview] Moving clip plane
In-Reply-To: <ee1acf8aad764ce3a54d3f68753ff59b@ES01AMSNLNT.srn.sandia.gov>
References: <ee1acf8aad764ce3a54d3f68753ff59b@ES01AMSNLNT.srn.sandia.gov>
Message-ID: <CANjZAi-LhO4LT7K96Yta_tUQWTt12QQDyoo+6v7vhvk-t5h6ag@mail.gmail.com>

If the slice stays fixed relative to the bounding box of the moving object,
try a python calculator to calculate the normalized local coordinates, than
apply isocontour on them.

On Tuesday, June 7, 2016, Scott, W Alan <wascott at sandia.gov> wrote:

> Is there a way to create a clip plane and have it translate with a moving
> part so that the same material is clipped throughout?
>
>
>
>
>
> Thanks,
>
>
>
> Alan
>
>
>


-- 
David E DeMarle
Kitware, Inc.
R&D Engineer
21 Corporate Drive
Clifton Park, NY 12065-8662
Phone: 518-881-4909
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160608/9ef97777/attachment.html>

From utkarsh.ayachit at kitware.com  Wed Jun  8 10:05:53 2016
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Wed, 8 Jun 2016 10:05:53 -0400
Subject: [Paraview] Moving clip plane
In-Reply-To: <CANjZAi-LhO4LT7K96Yta_tUQWTt12QQDyoo+6v7vhvk-t5h6ag@mail.gmail.com>
References: <ee1acf8aad764ce3a54d3f68753ff59b@ES01AMSNLNT.srn.sandia.gov>
 <CANjZAi-LhO4LT7K96Yta_tUQWTt12QQDyoo+6v7vhvk-t5h6ag@mail.gmail.com>
Message-ID: <CADHSJjB86hOBO6MBf5-yUbP0Vje_mneM8MSWJCeZpi1qpb7enA@mail.gmail.com>

In theory, you can do this using a Python animation cue too... let me
see how that can be put together.

On Wed, Jun 8, 2016 at 8:50 AM, David E DeMarle
<dave.demarle at kitware.com> wrote:
>
> If the slice stays fixed relative to the bounding box of the moving object,
> try a python calculator to calculate the normalized local coordinates, than
> apply isocontour on them.
>
> On Tuesday, June 7, 2016, Scott, W Alan <wascott at sandia.gov> wrote:
>>
>> Is there a way to create a clip plane and have it translate with a moving
>> part so that the same material is clipped throughout?
>>
>>
>>
>>
>>
>> Thanks,
>>
>>
>>
>> Alan
>>
>>
>
>
>
> --
> David E DeMarle
> Kitware, Inc.
> R&D Engineer
> 21 Corporate Drive
> Clifton Park, NY 12065-8662
> Phone: 518-881-4909
>
> _______________________________________________
> 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  Wed Jun  8 10:29:44 2016
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Wed, 8 Jun 2016 10:29:44 -0400
Subject: [Paraview] Moving clip plane
In-Reply-To: <CADHSJjB86hOBO6MBf5-yUbP0Vje_mneM8MSWJCeZpi1qpb7enA@mail.gmail.com>
References: <ee1acf8aad764ce3a54d3f68753ff59b@ES01AMSNLNT.srn.sandia.gov>
 <CANjZAi-LhO4LT7K96Yta_tUQWTt12QQDyoo+6v7vhvk-t5h6ag@mail.gmail.com>
 <CADHSJjB86hOBO6MBf5-yUbP0Vje_mneM8MSWJCeZpi1qpb7enA@mail.gmail.com>
Message-ID: <CADHSJjCyU+6K30UoLjNe0odM8TJwJYLZF4Sppuod_7VO8CANiQ@mail.gmail.com>

State file attached. It uses can.ex2.

The crux is in the Python Animation Cue script:

def start_cue(self): pass

def tick(self):
  ts = self.GetClockTime()
  from paraview import simple as pvs
  clip = pvs.FindSource("Clip1")
  ip = clip.Input
  ip.UpdatePipeline(ts)
  bds = ip.GetDataInformation().GetBounds()
  center = [ (bds[0] + bds[1]) / 2.0,
             (bds[2] + bds[3]) / 2.0,
             (bds[4] + bds[5]) / 2.0 ]
  clip.ClipType.Origin = center

def end_cue(self): pass



On Wed, Jun 8, 2016 at 10:05 AM, Utkarsh Ayachit
<utkarsh.ayachit at kitware.com> wrote:
> In theory, you can do this using a Python animation cue too... let me
> see how that can be put together.
>
> On Wed, Jun 8, 2016 at 8:50 AM, David E DeMarle
> <dave.demarle at kitware.com> wrote:
>>
>> If the slice stays fixed relative to the bounding box of the moving object,
>> try a python calculator to calculate the normalized local coordinates, than
>> apply isocontour on them.
>>
>> On Tuesday, June 7, 2016, Scott, W Alan <wascott at sandia.gov> wrote:
>>>
>>> Is there a way to create a clip plane and have it translate with a moving
>>> part so that the same material is clipped throughout?
>>>
>>>
>>>
>>>
>>>
>>> Thanks,
>>>
>>>
>>>
>>> Alan
>>>
>>>
>>
>>
>>
>> --
>> David E DeMarle
>> Kitware, Inc.
>> R&D Engineer
>> 21 Corporate Drive
>> Clifton Park, NY 12065-8662
>> Phone: 518-881-4909
>>
>> _______________________________________________
>> 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: ClipAndCenterOfData.pvsm
Type: application/octet-stream
Size: 181539 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160608/5fbd9251/attachment-0001.obj>

From cory.quammen at kitware.com  Wed Jun  8 10:45:43 2016
From: cory.quammen at kitware.com (Cory Quammen)
Date: Wed, 8 Jun 2016 16:45:43 +0200
Subject: [Paraview] visualize traced particles
In-Reply-To: <1464881196894.57602@sth.kth.se>
References: <1464881196894.57602@sth.kth.se>
Message-ID: <CAB5Fpx4qthu7C6TP-FTKbNo5ZVKO7Q8rtKBjo_b6UT-fkbDmyg@mail.gmail.com>

David,

Sure, this is possible. To view pathlines, you'll need to either write
a kind of file reader, probably a python Programmable Source, or
convert your file into a format ParaView can read, such as an XML
polydata file. The pathlines can be stored as vtkPolyLine cells in a
vtkPolyData.

If you just want to view the particles, you can likely read the file
directly using the CSV reader. Assuming your data is in the format

x y z t

the file will be read as a table. You'll need to convert the table to
points using the Table to Points filter. Choose the X, Y, and Z
columns for your data. The time column will be added as a variable
associated with the point.

HTH,
Cory

On Thu, Jun 2, 2016 at 5:26 PM, David Larsson <david.larsson at sth.kth.se> wrote:
> Dear Paraview community,
>
>
> in an external program, I've traced particles inside a 3D(+time) flow field
> and extracted each particles spatial position (x,y,z) in time.
>
>
> I have this data saved in an ascii-output where each particle position (with
> time) is simply written out.
>
>
> Now to my question: is there any convenient way of visualizing these
> pathlines in paraview? Can I load and look at that kind of data in a direct
> way? Or can you even visualize how the particle progresses in space over
> time?
>
>
> Thanks for your help.
>
>
> /David
>
>
> _______________________________________________
> 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 michalwozniak at live.ca  Wed Jun  8 13:38:50 2016
From: michalwozniak at live.ca (michal wozniak)
Date: Wed, 8 Jun 2016 13:38:50 -0400
Subject: [Paraview] Coordinate Result from Calculator
In-Reply-To: <BLU405-EAS148A1E3252ECE1143E70D0FAD5E0@phx.gbl>
References: <BLU180-W3990C386557A21F93F4E75AD5D0@phx.gbl>,
 <CACJ=gTjesmdTaH0G1ybshOR2vnffq=fF6k9e-tDA1Pr103hj0Q@mail.gmail.com>,
 <BLU405-EAS148A1E3252ECE1143E70D0FAD5E0@phx.gbl>
Message-ID: <BLU180-W64DB304FE39434742C1390AD5E0@phx.gbl>

Hi, 
I found out how  to get my coordinates. I used a programmable filter to get my inputs and calculate the mean. I would like to be able to add that value to the properties that appear when you use the manager link (mode : property link). 
My objective is to be able to link my custom property which will show my mean result to a different filter ( slide for eg). So that I could link Clip->Plane->Origin  to ProgrammableFIlter->CustomValue
Is this possible ? 

Date: Wed, 8 Jun 2016 07:58:47 -0400
From: michalwozniak at live.ca
To: joachim.pouderoux at kitware.com
CC: paraview at paraview.org
Subject: Re: [Paraview] Coordinate Result from Calculator

Hi,
I would like to access it in a following programmable filter or for eg link the coordinate result from the calculator to the center property of a slice filter using the manager link
It more about being able to access the coordinate result in another filter  


On Jun 8, 2016 7:48 AM, Joachim Pouderoux <joachim.pouderoux at kitware.com> wrote:
Michal,

Maybe I did not correctly understand your question but if you want to access point coordinates in the Calculator, they are available through the (pseudo) scalar variables coordsX, coordsY and coordsZ - you will find them in the Scalars list button.

Regards,
Joachim Pouderoux
PhD, Technical Expert
Kitware SAS



2016-06-07 21:50 GMT+02:00 michal wozniak <michalwozniak at live.ca>:



Hi everyone, 
I am calculating the mean of two source point using the python calculator. Then I use the calculator filter to get the Coordinate Result. How do I access that value? 
in my pipeline, my Calculator1 produce a Coordinate Result Array  called "Result". What do I do to access this array to be able to use the coordinate? 
thanks 
Michal  		 	   		  

_______________________________________________

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/20160608/fe87f5c4/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: manageLink.PNG
Type: image/png
Size: 30496 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160608/fe87f5c4/attachment.png>

From peterdebuchev at gmail.com  Wed Jun  8 14:18:17 2016
From: peterdebuchev at gmail.com (Peter Debuchev)
Date: Wed, 8 Jun 2016 20:18:17 +0200
Subject: [Paraview] vtkSMCollaborationManager::FollowUser(id) doesn't
 update view
In-Reply-To: <CADHSJjCLJ4=AfAFxPsmYWw0wn8WuKjDS5xeh8SUwJPqvydjRtg@mail.gmail.com>
References: <CAAUk9C4oh6fOkvh_yfaaXD4x6yoXe+--YiWfHL62oBmg-k3UQw@mail.gmail.com>
 <CADHSJjCLJ4=AfAFxPsmYWw0wn8WuKjDS5xeh8SUwJPqvydjRtg@mail.gmail.com>
Message-ID: <CAAUk9C5WxrVg2YiFvfLy=mkc5gAU36JA2rxCFNO0HnOKGEqpyw@mail.gmail.com>

Dear Utkarsh,
may I ask you to check again, which step is missing for following another
user's view using collaboration? It is definitely not the missing
ProcessEvents call. This problem is a real show-stopper for my batch
visualization system.

Unfortunately this is documented nowhere, and the comments in the header
files are not sufficient for me to reproduce how the event observation
mechanism is set up in ParaView.

Peter

2016-06-07 16:58 GMT+02:00 Utkarsh Ayachit <utkarsh.ayachit at kitware.com>:

> See pqServer::processServerNotification() [1]. You'll need to call
> vtkNetworkAccessManager::ProcessEvents(..) "on idle" to process events
> being received from the other client.
>
>
> [1]
> https://gitlab.kitware.com/paraview/paraview/blob/master/Qt/Core/pqServer.cxx#L376-401
>
> On Tue, Jun 7, 2016 at 8:54 AM, Peter Debuchev <peterdebuchev at gmail.com>
> wrote:
> > Hello,
> > I have attached a short custom client example which I would like to
> always
> > show the same perspective as a ParaView session connected to the same
> > pvserver.
> >
> > However, although this example renders once the objects that are
> available
> > in the ParaView session, it does not update itself when the camera is
> > changed in ParaView, despite of the line
> > "collaboration->FollowUser(collaboration->GetMasterId());" (see attached
> > code).
> >
> > Apparently I am missing one important step, maybe register the view with
> > some proxymanager, call some *::AddObserver(...) or something similar? I
> > don't know and couldn't find out after several attempts to understand
> > ParaView with the help of a debugger.
> >
> > As a side note: collaboration in the other direction runs successfully.
> If I
> > choose ParaView to follow this custom client by double-clicking on the
> eye
> > symbol in the collaboration panel, then the ParaView view always displays
> > the same perspective as the custom client.
> >
> > Which are the missing steps to have the client update its view, when the
> > (master) ParaView camera changes?
> >
> > Steps to reproduce:
> > + compile attached main.cxx
> > + run "pvserver --multi-clients &"
> > + run "paraview --server-url=cs://localhost:11111 &"
> > + create a simple pipeline in paraview
> > + run "./main" -> same pipeline as in paraview is rendered in custom
> client
> > + interact with view in ParaView -> client view does not update although
> it
> > is expected to follow the master
> >
> > Peter
> >
> > _______________________________________________
> > 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/20160608/f5d3f6df/attachment.html>

From hitcaozx at gmail.com  Wed Jun  8 15:40:03 2016
From: hitcaozx at gmail.com (=?UTF-8?B?5pu55pm66YCJ?=)
Date: Wed, 8 Jun 2016 15:40:03 -0400
Subject: [Paraview] use pv-meshless
Message-ID: <CANO2j4Pmi=MLAp0nMi9XBUwcouvCSJ2y8keEbtAeHnNcZZwrJw@mail.gmail.com>

Hello,
I am looking for a possible way to render simulation results by SPH (a
Lagrange method). To to be more specifically, I want to project SPH results
onto a pre-defined regular mesh. It seems that one plugin of paraview ---
pv-meshless support such functionality. So
1) What kind of data storage format does pv-meshless support, does it
support h5part?
2) Is there any detailed documentation about how to install and use
pv-meshless?

Best!

Zhixuan Cao
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160608/08eac38e/attachment.html>

From jfavre at cscs.ch  Wed Jun  8 16:09:30 2016
From: jfavre at cscs.ch (Favre  Jean)
Date: Wed, 8 Jun 2016 20:09:30 +0000
Subject: [Paraview] use pv-meshless
In-Reply-To: <CANO2j4Pmi=MLAp0nMi9XBUwcouvCSJ2y8keEbtAeHnNcZZwrJw@mail.gmail.com>
References: <CANO2j4Pmi=MLAp0nMi9XBUwcouvCSJ2y8keEbtAeHnNcZZwrJw@mail.gmail.com>
Message-ID: <0EB9B6375711A04B820E6B6F5CCA9F684362643B@MBX111.d.ethz.ch>

My advice is that you use the new features of ParaView master branch.

it includes new SPH interpolators under the Category "Filters->Point Interpolation". You have the choice to sample you rPSH points onto a high resolution 1D line, a 2D cutting plane, or a 3D volume.

-----------------
Jean/
CSCS
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160608/120d66a0/attachment.html>

From hitcaozx at gmail.com  Wed Jun  8 17:28:34 2016
From: hitcaozx at gmail.com (=?UTF-8?B?5pu55pm66YCJ?=)
Date: Wed, 8 Jun 2016 17:28:34 -0400
Subject: [Paraview] use pv-meshless
In-Reply-To: <0EB9B6375711A04B820E6B6F5CCA9F684362643B@MBX111.d.ethz.ch>
References: <CANO2j4Pmi=MLAp0nMi9XBUwcouvCSJ2y8keEbtAeHnNcZZwrJw@mail.gmail.com>
 <0EB9B6375711A04B820E6B6F5CCA9F684362643B@MBX111.d.ethz.ch>
Message-ID: <CANO2j4MHyD-KEg26F0RVjiHNtTwdtQtV-z6dsKZ8jMNgj=vbtg@mail.gmail.com>

Thank you Jean,
Sounds like it is exactly the feature I was looking for,
When you talk about master branch, are you mean the master branch of
paraview on github?
As I was using binary version of paraview, I am not sure where is the best
source to get the most recent stable release of paraview. Could you give me
any recommendation?

Best!

Zhixuan Cao

2016-06-08 16:09 GMT-04:00 Favre Jean <jfavre at cscs.ch>:

> My advice is that you use the new features of ParaView master branch.
>
> it includes new SPH interpolators under the Category "Filters->Point
> Interpolation". You have the choice to sample you rPSH points onto a high
> resolution 1D line, a 2D cutting plane, or a 3D volume.
>
> -----------------
> Jean/
> CSCS
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160608/95f5b3e6/attachment.html>

From jfavre at cscs.ch  Thu Jun  9 00:48:16 2016
From: jfavre at cscs.ch (Favre  Jean)
Date: Thu, 9 Jun 2016 04:48:16 +0000
Subject: [Paraview] use pv-meshless
In-Reply-To: <CANO2j4MHyD-KEg26F0RVjiHNtTwdtQtV-z6dsKZ8jMNgj=vbtg@mail.gmail.com>
References: <CANO2j4Pmi=MLAp0nMi9XBUwcouvCSJ2y8keEbtAeHnNcZZwrJw@mail.gmail.com>
 <0EB9B6375711A04B820E6B6F5CCA9F684362643B@MBX111.d.ethz.ch>,
 <CANO2j4MHyD-KEg26F0RVjiHNtTwdtQtV-z6dsKZ8jMNgj=vbtg@mail.gmail.com>
Message-ID: <0EB9B6375711A04B820E6B6F5CCA9F68436265C5@MBX111.d.ethz.ch>

>>Could you give me any recommendation?

yes, I can: see Utkarsh's posting:

<<
ParaView 5.1.0-RC1 has been tagged.

Git tag name: v5.1.0-RC1

Source tar/zip files are available for download:
http://www.paraview.org/download/

Binaries will be available for testing within the next few days.

Utkarsh
Best!
<<
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160609/6afacd26/attachment.html>

From giorginor21 at gmail.com  Thu Jun  9 05:23:55 2016
From: giorginor21 at gmail.com (Giorgino R)
Date: Thu, 9 Jun 2016 10:23:55 +0100
Subject: [Paraview] paraview python anaconda
Message-ID: <CA+c1-+_vAFaHPwmpcY3z8wPciHQ8CiV8+ek9iEDy3XEEw1v-rw@mail.gmail.com>

Dear users,

I would like to use PyQt4 with Paraview. I have installed Paraview from
pre-compiled binaries. When I am using pvpython, I cannot use PyQt4 since
this is not installed. Is there any chance that I could install PyQt4 with
pvpython? Otherwise, does any of you know how to configure Paraview's
python version to that of my Anaconda?

Thanks a lot, Giorgino.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160609/e0d731b2/attachment.html>

From Matthias.Zenker at erbe-med.com  Thu Jun  9 07:39:40 2016
From: Matthias.Zenker at erbe-med.com (Zenker, Dr. Matthias)
Date: Thu, 9 Jun 2016 11:39:40 +0000
Subject: [Paraview] Questions to stream tracer
Message-ID: <F9562F3B302F29479A203FC5AF9E3E050F48DFB9@SERBE4I1.intra.erbe-med.de>

Hi,

I want to visualize an electric field (calculated with Elmer). The data are in a vtu file. When I use the Stream Tracer filter to visualize the field, the stream lines extend well beyond the simulated region. Is there a way to make them end at the border of the simulated region? Since they do not have the same length, I cannot use the settings for maximum length or maximum number of steps to control that.
Another question: can I use a complex line as seed? If I integrate in both directions, I get artifacts, I think due to the fact that the field is zero in a part of the simulated region.

Thanks for helpful hints and/or a pointer to documentation (didn't find the answer in the help).

Matthias

________________________________

Erbe Elektromedizin GmbH Firmensitz: 72072 Tuebingen Geschaeftsfuehrer: Christian O. Erbe, Reiner Thede Registergericht: Stuttgart HRB 380137

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

From utkarsh.ayachit at kitware.com  Thu Jun  9 10:59:50 2016
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Thu, 9 Jun 2016 10:59:50 -0400
Subject: [Paraview] ANN: ParaView 5.1.0-RC1 available for download
Message-ID: <CADHSJjCTEFP3VOFm+k2vE-gxN8nojz5q4rDjKL9ZUhgDFeG9hw@mail.gmail.com>

Folks,

ParaView 5.1.0-RC1 is now available for download [1]. For fixes that
went into this release, refer to the change log on bug tracker [2].

Detailed release notes coming soon.

- The ParaView team

[1] http://www.paraview.org/download/
[2] http://www.paraview.org/Bug/changelog_page.php

From hitcaozx at gmail.com  Thu Jun  9 12:27:49 2016
From: hitcaozx at gmail.com (Zhixuan Cao)
Date: Thu, 9 Jun 2016 12:27:49 -0400
Subject: [Paraview] ANN: ParaView 5.1.0-RC1 available for download
In-Reply-To: <CADHSJjCTEFP3VOFm+k2vE-gxN8nojz5q4rDjKL9ZUhgDFeG9hw@mail.gmail.com>
References: <CADHSJjCTEFP3VOFm+k2vE-gxN8nojz5q4rDjKL9ZUhgDFeG9hw@mail.gmail.com>
Message-ID: <96B43CB6-F195-489A-A24A-2305F5AD5C10@gmail.com>

Very happy to hear that. Is there any documentation about the detail of new features? For example, what is the exact equation for the new feature SPH interpolation?
> On Jun 9, 2016, at 10:59 AM, Utkarsh Ayachit <utkarsh.ayachit at kitware.com> wrote:
> 
> Folks,
> 
> ParaView 5.1.0-RC1 is now available for download [1]. For fixes that
> went into this release, refer to the change log on bug tracker [2].
> 
> Detailed release notes coming soon.
> 
> - The ParaView team
> 
> [1] http://www.paraview.org/download/
> [2] http://www.paraview.org/Bug/changelog_page.php
> _______________________________________________
> 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  Thu Jun  9 12:29:36 2016
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Thu, 9 Jun 2016 12:29:36 -0400
Subject: [Paraview] vtkSMCollaborationManager::FollowUser(id) doesn't
 update view
In-Reply-To: <CAAUk9C5WxrVg2YiFvfLy=mkc5gAU36JA2rxCFNO0HnOKGEqpyw@mail.gmail.com>
References: <CAAUk9C4oh6fOkvh_yfaaXD4x6yoXe+--YiWfHL62oBmg-k3UQw@mail.gmail.com>
 <CADHSJjCLJ4=AfAFxPsmYWw0wn8WuKjDS5xeh8SUwJPqvydjRtg@mail.gmail.com>
 <CAAUk9C5WxrVg2YiFvfLy=mkc5gAU36JA2rxCFNO0HnOKGEqpyw@mail.gmail.com>
Message-ID: <CADHSJjB9NQSdGShv1ThyWSpznOa1MRAKz-hagm6vve=k39BE4A@mail.gmail.com>

Here's the fix:

diff --git a/main.cxx b/main.cxx
index dd47991..0f679ba 100644
--- a/main.cxx
+++ b/main.cxx
@@ -65,7 +65,7 @@ int main(int argc, char* argv[]){
   vtkSMSessionProxyManager* pxm = session->GetSessionProxyManager();

   //Collaboration:
-  vtkSMCollaborationManager *collaboration=vtkSMCollaborationManager::New();
+  vtkSMCollaborationManager *collaboration= session->GetCollaborationManager();
   collaboration->SetSession(session);
   collaboration->UpdateUserInformations();

From hitcaozx at gmail.com  Thu Jun  9 14:40:11 2016
From: hitcaozx at gmail.com (=?UTF-8?B?5pu55pm66YCJ?=)
Date: Thu, 9 Jun 2016 14:40:11 -0400
Subject: [Paraview] ANN: ParaView 5.1.0-RC1 available for download
In-Reply-To: <96B43CB6-F195-489A-A24A-2305F5AD5C10@gmail.com>
References: <CADHSJjCTEFP3VOFm+k2vE-gxN8nojz5q4rDjKL9ZUhgDFeG9hw@mail.gmail.com>
 <96B43CB6-F195-489A-A24A-2305F5AD5C10@gmail.com>
Message-ID: <CANO2j4MxWh8PN7GQtWb_nBh=Fm8pjwoUHTGG-7Siybuy=BZhKQ@mail.gmail.com>

I had an problem with the binary version for Linux64bits:

I could not open paraview due to the following error:
error while loading shared libraries: libpython2.7.so.1.0: cannot open
shared object file: No such file or directory

2016-06-09 12:27 GMT-04:00 Zhixuan Cao <hitcaozx at gmail.com>:

> Very happy to hear that. Is there any documentation about the detail of
> new features? For example, what is the exact equation for the new feature
> SPH interpolation?
> > On Jun 9, 2016, at 10:59 AM, Utkarsh Ayachit <
> utkarsh.ayachit at kitware.com> wrote:
> >
> > Folks,
> >
> > ParaView 5.1.0-RC1 is now available for download [1]. For fixes that
> > went into this release, refer to the change log on bug tracker [2].
> >
> > Detailed release notes coming soon.
> >
> > - The ParaView team
> >
> > [1] http://www.paraview.org/download/
> > [2] http://www.paraview.org/Bug/changelog_page.php
> > _______________________________________________
> > 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/20160609/50786044/attachment.html>

From utkarsh.ayachit at kitware.com  Thu Jun  9 15:01:38 2016
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Thu, 9 Jun 2016 15:01:38 -0400
Subject: [Paraview] ANN: ParaView 5.1.0-RC1 available for download
In-Reply-To: <CANO2j4MxWh8PN7GQtWb_nBh=Fm8pjwoUHTGG-7Siybuy=BZhKQ@mail.gmail.com>
References: <CADHSJjCTEFP3VOFm+k2vE-gxN8nojz5q4rDjKL9ZUhgDFeG9hw@mail.gmail.com>
 <96B43CB6-F195-489A-A24A-2305F5AD5C10@gmail.com>
 <CANO2j4MxWh8PN7GQtWb_nBh=Fm8pjwoUHTGG-7Siybuy=BZhKQ@mail.gmail.com>
Message-ID: <CADHSJjBrA7KTCZVAV07593hDeO0QCSwbgLFSHnu61JG0Ffs9Kg@mail.gmail.com>

Roger that. I'll track it down and upload a new version of the binaries.

On Thu, Jun 9, 2016 at 2:40 PM, ??? <hitcaozx at gmail.com> wrote:
> I had an problem with the binary version for Linux64bits:
>
> I could not open paraview due to the following error:
> error while loading shared libraries: libpython2.7.so.1.0: cannot open
> shared object file: No such file or directory
>
> 2016-06-09 12:27 GMT-04:00 Zhixuan Cao <hitcaozx at gmail.com>:
>>
>> Very happy to hear that. Is there any documentation about the detail of
>> new features? For example, what is the exact equation for the new feature
>> SPH interpolation?
>> > On Jun 9, 2016, at 10:59 AM, Utkarsh Ayachit
>> > <utkarsh.ayachit at kitware.com> wrote:
>> >
>> > Folks,
>> >
>> > ParaView 5.1.0-RC1 is now available for download [1]. For fixes that
>> > went into this release, refer to the change log on bug tracker [2].
>> >
>> > Detailed release notes coming soon.
>> >
>> > - The ParaView team
>> >
>> > [1] http://www.paraview.org/download/
>> > [2] http://www.paraview.org/Bug/changelog_page.php
>> > _______________________________________________
>> > 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 archaerolog at mail.ru  Thu Jun  9 15:31:51 2016
From: archaerolog at mail.ru (Gena Bug)
Date: Thu, 9 Jun 2016 22:31:51 +0300
Subject: [Paraview] ANN: ParaView 5.1.0-RC1 available for download
In-Reply-To: <96B43CB6-F195-489A-A24A-2305F5AD5C10@gmail.com>
References: <CADHSJjCTEFP3VOFm+k2vE-gxN8nojz5q4rDjKL9ZUhgDFeG9hw@mail.gmail.com>
 <96B43CB6-F195-489A-A24A-2305F5AD5C10@gmail.com>
Message-ID: <c571d7c3-69b7-dcd8-4b5d-5379f90a46f6@mail.ru>

Hi!

Can't run anything from bin:

$ ./paraview
ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/paraview: 
error while loading shared libraries: libmpich.so.3: cannot open shared 
object file: No such file or directory

I have libmpich.so in the system (Debian testing), so I symlinked to it, 
but it didn't help -- after a series of new symlinks:
1. libmpich.so.3 -> libmpich.so
2. libopa.so.1 -> libopa.so
3. libmpl.so.1 -> libmpl.so
4. ??? -> libembree.so.2

I stopped at last step because can't find any package with libembree...


On 09.06.2016 19:27, Zhixuan Cao wrote:
> Very happy to hear that. Is there any documentation about the detail of new features? For example, what is the exact equation for the new feature SPH interpolation?
>> On Jun 9, 2016, at 10:59 AM, Utkarsh Ayachit <utkarsh.ayachit at kitware.com> wrote:
>>
>> Folks,
>>
>> ParaView 5.1.0-RC1 is now available for download [1]. For fixes that
>> went into this release, refer to the change log on bug tracker [2].
>>
>> Detailed release notes coming soon.
>>
>> - The ParaView team
>>
>> [1] http://www.paraview.org/download/
>> [2] http://www.paraview.org/Bug/changelog_page.php
>> _______________________________________________
>> 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 utkarsh.ayachit at kitware.com  Thu Jun  9 19:10:05 2016
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Thu, 9 Jun 2016 19:10:05 -0400
Subject: [Paraview] ANN: ParaView 5.1.0-RC1 available for download
In-Reply-To: <c571d7c3-69b7-dcd8-4b5d-5379f90a46f6@mail.ru>
References: <CADHSJjCTEFP3VOFm+k2vE-gxN8nojz5q4rDjKL9ZUhgDFeG9hw@mail.gmail.com>
 <96B43CB6-F195-489A-A24A-2305F5AD5C10@gmail.com>
 <c571d7c3-69b7-dcd8-4b5d-5379f90a46f6@mail.ru>
Message-ID: <CADHSJjAcCR+zggqXUk75yfCi6Vd5dw+ncqt5SmYLNS2nKUcnbw@mail.gmail.com>

Roger that. I've getting a new build. I switched to using a new build
machine -- looks like that was premature. I'll upload binaries from
the old build machine once they are available.



On Thu, Jun 9, 2016 at 3:31 PM, Gena Bug via ParaView
<paraview at paraview.org> wrote:
> Hi!
>
> Can't run anything from bin:
>
> $ ./paraview
> ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/paraview:
> error while loading shared libraries: libmpich.so.3: cannot open shared
> object file: No such file or directory
>
> I have libmpich.so in the system (Debian testing), so I symlinked to it, but
> it didn't help -- after a series of new symlinks:
> 1. libmpich.so.3 -> libmpich.so
> 2. libopa.so.1 -> libopa.so
> 3. libmpl.so.1 -> libmpl.so
> 4. ??? -> libembree.so.2
>
> I stopped at last step because can't find any package with libembree...
>
>
>
> On 09.06.2016 19:27, Zhixuan Cao wrote:
>>
>> Very happy to hear that. Is there any documentation about the detail of
>> new features? For example, what is the exact equation for the new feature
>> SPH interpolation?
>>>
>>> On Jun 9, 2016, at 10:59 AM, Utkarsh Ayachit
>>> <utkarsh.ayachit at kitware.com> wrote:
>>>
>>> Folks,
>>>
>>> ParaView 5.1.0-RC1 is now available for download [1]. For fixes that
>>> went into this release, refer to the change log on bug tracker [2].
>>>
>>> Detailed release notes coming soon.
>>>
>>> - The ParaView team
>>>
>>> [1] http://www.paraview.org/download/
>>> [2] http://www.paraview.org/Bug/changelog_page.php
>>> _______________________________________________
>>> 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 peterdebuchev at gmail.com  Fri Jun 10 01:24:07 2016
From: peterdebuchev at gmail.com (Peter Debuchev)
Date: Fri, 10 Jun 2016 07:24:07 +0200
Subject: [Paraview] vtkSMCollaborationManager::FollowUser(id) doesn't
 update view
In-Reply-To: <CADHSJjB9NQSdGShv1ThyWSpznOa1MRAKz-hagm6vve=k39BE4A@mail.gmail.com>
References: <CAAUk9C4oh6fOkvh_yfaaXD4x6yoXe+--YiWfHL62oBmg-k3UQw@mail.gmail.com>
 <CADHSJjCLJ4=AfAFxPsmYWw0wn8WuKjDS5xeh8SUwJPqvydjRtg@mail.gmail.com>
 <CAAUk9C5WxrVg2YiFvfLy=mkc5gAU36JA2rxCFNO0HnOKGEqpyw@mail.gmail.com>
 <CADHSJjB9NQSdGShv1ThyWSpznOa1MRAKz-hagm6vve=k39BE4A@mail.gmail.com>
Message-ID: <CAAUk9C7xotQgBGb7XtB41WSO-TY0cow8veu=VjvU23CbaLDnLA@mail.gmail.com>

That did the trick, thank you very much! I would have never found the
problem.

One more question out of curiosity: isn't it quite ineffient, if clients
continuously invoke vtkNetworkAccessManager::ProcessEvents?()? For smooth
interaction this has to happen at least 10 times per second, which causes a
lot of network traffic by polling the server again and again,  especially
if more than one client connects to the same server.
Isn't it possible to react on incoming server events by registering a
callback that does the same server event processing only when a new event
has occurred? I mean, all of VTK and ParaView is event based, why not the
server message processing?

Peter

2016-06-09 18:29 GMT+02:00 Utkarsh Ayachit <utkarsh.ayachit at kitware.com>:

> Here's the fix:
>
> diff --git a/main.cxx b/main.cxx
> index dd47991..0f679ba 100644
> --- a/main.cxx
> +++ b/main.cxx
> @@ -65,7 +65,7 @@ int main(int argc, char* argv[]){
>    vtkSMSessionProxyManager* pxm = session->GetSessionProxyManager();
>
>    //Collaboration:
> -  vtkSMCollaborationManager
> *collaboration=vtkSMCollaborationManager::New();
> +  vtkSMCollaborationManager *collaboration=
> session->GetCollaborationManager();
>    collaboration->SetSession(session);
>    collaboration->UpdateUserInformations();
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160610/94ca7eb6/attachment.html>

From utkarsh.ayachit at kitware.com  Fri Jun 10 09:17:05 2016
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Fri, 10 Jun 2016 09:17:05 -0400
Subject: [Paraview] vtkSMCollaborationManager::FollowUser(id) doesn't
 update view
In-Reply-To: <CAAUk9C7xotQgBGb7XtB41WSO-TY0cow8veu=VjvU23CbaLDnLA@mail.gmail.com>
References: <CAAUk9C4oh6fOkvh_yfaaXD4x6yoXe+--YiWfHL62oBmg-k3UQw@mail.gmail.com>
 <CADHSJjCLJ4=AfAFxPsmYWw0wn8WuKjDS5xeh8SUwJPqvydjRtg@mail.gmail.com>
 <CAAUk9C5WxrVg2YiFvfLy=mkc5gAU36JA2rxCFNO0HnOKGEqpyw@mail.gmail.com>
 <CADHSJjB9NQSdGShv1ThyWSpznOa1MRAKz-hagm6vve=k39BE4A@mail.gmail.com>
 <CAAUk9C7xotQgBGb7XtB41WSO-TY0cow8veu=VjvU23CbaLDnLA@mail.gmail.com>
Message-ID: <CADHSJjB=u7ZzsTQ5902yjiDv+ie_Bpkvn9byZ5s44p-Rg9yX2w@mail.gmail.com>

ProcessEvents() doesn't poll the server. It only "select"s on the
socket to see if the server sent any new messages to the client.

> One more question out of curiosity: isn't it quite ineffient, if clients
> continuously invoke vtkNetworkAccessManager::ProcessEvents?()? For smooth
> interaction this has to happen at least 10 times per second, which causes a
> lot of network traffic by polling the server again and again,  especially if
> more than one client connects to the same server.
> Isn't it possible to react on incoming server events by registering a
> callback that does the same server event processing only when a new event
> has occurred? I mean, all of VTK and ParaView is event based, why not the
> server message processing?
>
> Peter
>
> 2016-06-09 18:29 GMT+02:00 Utkarsh Ayachit <utkarsh.ayachit at kitware.com>:
>>
>> Here's the fix:
>>
>> diff --git a/main.cxx b/main.cxx
>> index dd47991..0f679ba 100644
>> --- a/main.cxx
>> +++ b/main.cxx
>> @@ -65,7 +65,7 @@ int main(int argc, char* argv[]){
>>    vtkSMSessionProxyManager* pxm = session->GetSessionProxyManager();
>>
>>    //Collaboration:
>> -  vtkSMCollaborationManager
>> *collaboration=vtkSMCollaborationManager::New();
>> +  vtkSMCollaborationManager *collaboration=
>> session->GetCollaborationManager();
>>    collaboration->SetSession(session);
>>    collaboration->UpdateUserInformations();
>
>

From utkarsh.ayachit at kitware.com  Fri Jun 10 11:21:33 2016
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Fri, 10 Jun 2016 11:21:33 -0400
Subject: [Paraview] ANN: ParaView 5.1.0-RC1 available for download
In-Reply-To: <CADHSJjAcCR+zggqXUk75yfCi6Vd5dw+ncqt5SmYLNS2nKUcnbw@mail.gmail.com>
References: <CADHSJjCTEFP3VOFm+k2vE-gxN8nojz5q4rDjKL9ZUhgDFeG9hw@mail.gmail.com>
 <96B43CB6-F195-489A-A24A-2305F5AD5C10@gmail.com>
 <c571d7c3-69b7-dcd8-4b5d-5379f90a46f6@mail.ru>
 <CADHSJjAcCR+zggqXUk75yfCi6Vd5dw+ncqt5SmYLNS2nKUcnbw@mail.gmail.com>
Message-ID: <CADHSJjDrpBFvbiXTjvJDY0YFcUh_BPAoZYW9f=bJUt45t3bgxQ@mail.gmail.com>

New binaries for linux have been uploaded. Please give them a go.

Thanks
Utkarsh

On Thu, Jun 9, 2016 at 7:10 PM, Utkarsh Ayachit
<utkarsh.ayachit at kitware.com> wrote:
> Roger that. I've getting a new build. I switched to using a new build
> machine -- looks like that was premature. I'll upload binaries from
> the old build machine once they are available.
>
>
>
> On Thu, Jun 9, 2016 at 3:31 PM, Gena Bug via ParaView
> <paraview at paraview.org> wrote:
>> Hi!
>>
>> Can't run anything from bin:
>>
>> $ ./paraview
>> ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/paraview:
>> error while loading shared libraries: libmpich.so.3: cannot open shared
>> object file: No such file or directory
>>
>> I have libmpich.so in the system (Debian testing), so I symlinked to it, but
>> it didn't help -- after a series of new symlinks:
>> 1. libmpich.so.3 -> libmpich.so
>> 2. libopa.so.1 -> libopa.so
>> 3. libmpl.so.1 -> libmpl.so
>> 4. ??? -> libembree.so.2
>>
>> I stopped at last step because can't find any package with libembree...
>>
>>
>>
>> On 09.06.2016 19:27, Zhixuan Cao wrote:
>>>
>>> Very happy to hear that. Is there any documentation about the detail of
>>> new features? For example, what is the exact equation for the new feature
>>> SPH interpolation?
>>>>
>>>> On Jun 9, 2016, at 10:59 AM, Utkarsh Ayachit
>>>> <utkarsh.ayachit at kitware.com> wrote:
>>>>
>>>> Folks,
>>>>
>>>> ParaView 5.1.0-RC1 is now available for download [1]. For fixes that
>>>> went into this release, refer to the change log on bug tracker [2].
>>>>
>>>> Detailed release notes coming soon.
>>>>
>>>> - The ParaView team
>>>>
>>>> [1] http://www.paraview.org/download/
>>>> [2] http://www.paraview.org/Bug/changelog_page.php
>>>> _______________________________________________
>>>> 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 elliot.kaplan at gmail.com  Fri Jun 10 11:47:06 2016
From: elliot.kaplan at gmail.com (Elliot Kaplan)
Date: Fri, 10 Jun 2016 17:47:06 +0200
Subject: [Paraview] Loading xdmf files fails in Paraview
Message-ID: <CA+pdR5gyc=98JMOirXkEF0_f8oR3QHY3DNhr8Qr3iJWZJKvumw@mail.gmail.com>

I'm trying to use Paraview with xdmf files which I've generated in a python
script (both the xml light data and the hdf5 heavy data). Initially I was
working with Paraview-4.0.1 which I could install from apt and loaded the
data fine. Recently I downloaded Paraview-5.0.1, which fails to load the
xdmf file in a variety of ways. If I try to load the dataset with the Xdmf3
Reader, I get the following error:

    'Content' not found in itemProperties in XdmfArray::populateItem
    Qt has caught an exception thrown from an event handler. Throwing
    exceptions from an event handler is not supported in Qt. You must
    reimplement QApplication::notify() and catch all exceptions there.

    terminate called after throwing an instance of 'XdmfError'
      what():  'Content' not found in itemProperties in
XdmfArray::populateItem
    Aborted (core dumped)

If I try to load with the Xdmf Reader, Paraview segfaults. I found the same
set of problems with Paraview-4.4.1.

How do I correct the lack of content in the xdmfarry? What does that even
mean? (I don't recall there being a content tag necessary in the xdmf
specification). I can post the xml and hdf5 files if necessary.

I would file a bug, but the bug tracker isn't accepting new users at the
moment.

thanks
-Elliot
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160610/4ae88433/attachment.html>

From andrew.j.burns35.ctr at mail.mil  Fri Jun 10 12:33:31 2016
From: andrew.j.burns35.ctr at mail.mil (Burns, Andrew J CTR USARMY RDECOM ARL (US))
Date: Fri, 10 Jun 2016 16:33:31 +0000
Subject: [Paraview] [Non-DoD Source] Loading xdmf files fails in Paraview
In-Reply-To: <CA+pdR5gyc=98JMOirXkEF0_f8oR3QHY3DNhr8Qr3iJWZJKvumw@mail.gmail.com>
References: <CA+pdR5gyc=98JMOirXkEF0_f8oR3QHY3DNhr8Qr3iJWZJKvumw@mail.gmail.com>
Message-ID: <DEE37B508E36B64285856EEA9FC0C33734632DCE@ucolhpkl.easf.csd.disa.mil>

Content in Xdmf's context is the data that XdmfArray contains. In XML this is the data between the XML tags.

For the Array:
<DataItem DataType="Int" Dimensions="2" Format="HDF" Precision="4">output.h5:Data6</DataItem>

The "Content" is "output.h5:Data6" which is then parsed into an HDF5 reference.

The term "Content" is a carryover from the XML parser that Xdmf uses.

Andrew Burns
Lockheed Martin
Software Engineer
410-306-0409
ARL DSRC
andrew.j.burns35.ctr at mail.mil

-----Original Message-----
From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Elliot Kaplan
Sent: Friday, June 10, 2016 11:47 AM
To: paraview at paraview.org
Subject: [Non-DoD Source] [Paraview] Loading xdmf files fails in Paraview

I'm trying to use Paraview with xdmf files which I've generated in a python script (both the xml light data and the hdf5 heavy data). Initially I was working with Paraview-4.0.1 which I could install from apt and loaded the data fine. Recently I downloaded Paraview-5.0.1, which fails to load the xdmf file in a variety of ways. If I try to load the dataset with the Xdmf3 Reader, I get the following error:

    'Content' not found in itemProperties in XdmfArray::populateItem
    Qt has caught an exception thrown from an event handler. Throwing
    exceptions from an event handler is not supported in Qt. You must
    reimplement QApplication::notify() and catch all exceptions there.

    terminate called after throwing an instance of 'XdmfError'
      what():  'Content' not found in itemProperties in XdmfArray::populateItem
    Aborted (core dumped)


If I try to load with the Xdmf Reader, Paraview segfaults. I found the same set of problems with Paraview-4.4.1.


How do I correct the lack of content in the xdmfarry? What does that even mean? (I don't recall there being a content tag necessary in the xdmf specification). I can post the xml and hdf5 files if necessary.


I would file a bug, but the bug tracker isn't accepting new users at the moment.


thanks

-Elliot


From peterdebuchev at gmail.com  Fri Jun 10 12:58:59 2016
From: peterdebuchev at gmail.com (Peter Debuchev)
Date: Fri, 10 Jun 2016 18:58:59 +0200
Subject: [Paraview] vtkSMCollaborationManager::FollowUser(id) doesn't
 update view
In-Reply-To: <CADHSJjB=u7ZzsTQ5902yjiDv+ie_Bpkvn9byZ5s44p-Rg9yX2w@mail.gmail.com>
References: <CAAUk9C4oh6fOkvh_yfaaXD4x6yoXe+--YiWfHL62oBmg-k3UQw@mail.gmail.com>
 <CADHSJjCLJ4=AfAFxPsmYWw0wn8WuKjDS5xeh8SUwJPqvydjRtg@mail.gmail.com>
 <CAAUk9C5WxrVg2YiFvfLy=mkc5gAU36JA2rxCFNO0HnOKGEqpyw@mail.gmail.com>
 <CADHSJjB9NQSdGShv1ThyWSpznOa1MRAKz-hagm6vve=k39BE4A@mail.gmail.com>
 <CAAUk9C7xotQgBGb7XtB41WSO-TY0cow8veu=VjvU23CbaLDnLA@mail.gmail.com>
 <CADHSJjB=u7ZzsTQ5902yjiDv+ie_Bpkvn9byZ5s44p-Rg9yX2w@mail.gmail.com>
Message-ID: <CAAUk9C5e8N=n-59yqbh3_=8mo_Oe68Xwbfm-Vq_Fy_3RBWMQdg@mail.gmail.com>

Ok, that doesn't sound as bad as I expected. But still, is it necessary to
"poll" the socket, checking its "select" method?
I am not familiar with the details of socket communication, but I expect it
should be possible that the socket invokes some callback when a message
arrives? Or does some of the VTK design contradict such socket callbacks?

I found that it is always problematic performance-wise if more than a few
timers are running on one cpu.

Peter

2016-06-10 15:17 GMT+02:00 Utkarsh Ayachit <utkarsh.ayachit at kitware.com>:

> ProcessEvents() doesn't poll the server. It only "select"s on the
> socket to see if the server sent any new messages to the client.
>
> > One more question out of curiosity: isn't it quite ineffient, if clients
> > continuously invoke vtkNetworkAccessManager::ProcessEvents?()? For smooth
> > interaction this has to happen at least 10 times per second, which
> causes a
> > lot of network traffic by polling the server again and again,
> especially if
> > more than one client connects to the same server.
> > Isn't it possible to react on incoming server events by registering a
> > callback that does the same server event processing only when a new event
> > has occurred? I mean, all of VTK and ParaView is event based, why not the
> > server message processing?
> >
> > Peter
> >
> > 2016-06-09 18:29 GMT+02:00 Utkarsh Ayachit <utkarsh.ayachit at kitware.com
> >:
> >>
> >> Here's the fix:
> >>
> >> diff --git a/main.cxx b/main.cxx
> >> index dd47991..0f679ba 100644
> >> --- a/main.cxx
> >> +++ b/main.cxx
> >> @@ -65,7 +65,7 @@ int main(int argc, char* argv[]){
> >>    vtkSMSessionProxyManager* pxm = session->GetSessionProxyManager();
> >>
> >>    //Collaboration:
> >> -  vtkSMCollaborationManager
> >> *collaboration=vtkSMCollaborationManager::New();
> >> +  vtkSMCollaborationManager *collaboration=
> >> session->GetCollaborationManager();
> >>    collaboration->SetSession(session);
> >>    collaboration->UpdateUserInformations();
> >
> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160610/e872f612/attachment.html>

From archaerolog at mail.ru  Fri Jun 10 17:16:11 2016
From: archaerolog at mail.ru (Gena Bug)
Date: Sat, 11 Jun 2016 00:16:11 +0300
Subject: [Paraview] ANN: ParaView 5.1.0-RC1 available for download
In-Reply-To: <CADHSJjDrpBFvbiXTjvJDY0YFcUh_BPAoZYW9f=bJUt45t3bgxQ@mail.gmail.com>
References: <CADHSJjCTEFP3VOFm+k2vE-gxN8nojz5q4rDjKL9ZUhgDFeG9hw@mail.gmail.com>
 <96B43CB6-F195-489A-A24A-2305F5AD5C10@gmail.com>
 <c571d7c3-69b7-dcd8-4b5d-5379f90a46f6@mail.ru>
 <CADHSJjAcCR+zggqXUk75yfCi6Vd5dw+ncqt5SmYLNS2nKUcnbw@mail.gmail.com>
 <CADHSJjDrpBFvbiXTjvJDY0YFcUh_BPAoZYW9f=bJUt45t3bgxQ@mail.gmail.com>
Message-ID: <9699c536-51d3-950f-b5a5-fcbce6811dce@mail.ru>

On 10.06.2016 18:21, Utkarsh Ayachit wrote:
> New binaries for linux have been uploaded. Please give them a go.
Now it seems to work... At least it starts and I can do basic stuff.

Thanks, Utkarsh!

> Thanks
> Utkarsh
>
> On Thu, Jun 9, 2016 at 7:10 PM, Utkarsh Ayachit
> <utkarsh.ayachit at kitware.com> wrote:
>> Roger that. I've getting a new build. I switched to using a new build
>> machine -- looks like that was premature. I'll upload binaries from
>> the old build machine once they are available.
>>
>>
>>
>> On Thu, Jun 9, 2016 at 3:31 PM, Gena Bug via ParaView
>> <paraview at paraview.org> wrote:
>>> Hi!
>>>
>>> Can't run anything from bin:
>>>
>>> $ ./paraview
>>> ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/paraview:
>>> error while loading shared libraries: libmpich.so.3: cannot open shared
>>> object file: No such file or directory
>>>
>>> I have libmpich.so in the system (Debian testing), so I symlinked to it, but
>>> it didn't help -- after a series of new symlinks:
>>> 1. libmpich.so.3 -> libmpich.so
>>> 2. libopa.so.1 -> libopa.so
>>> 3. libmpl.so.1 -> libmpl.so
>>> 4. ??? -> libembree.so.2
>>>
>>> I stopped at last step because can't find any package with libembree...
>>>
>>>
>>>
>>> On 09.06.2016 19:27, Zhixuan Cao wrote:
>>>>
>>>> Very happy to hear that. Is there any documentation about the detail of
>>>> new features? For example, what is the exact equation for the new feature
>>>> SPH interpolation?
>>>>>
>>>>> On Jun 9, 2016, at 10:59 AM, Utkarsh Ayachit
>>>>> <utkarsh.ayachit at kitware.com> wrote:
>>>>>
>>>>> Folks,
>>>>>
>>>>> ParaView 5.1.0-RC1 is now available for download [1]. For fixes that
>>>>> went into this release, refer to the change log on bug tracker [2].
>>>>>
>>>>> Detailed release notes coming soon.
>>>>>
>>>>> - The ParaView team
>>>>>
>>>>> [1] http://www.paraview.org/download/
>>>>> [2] http://www.paraview.org/Bug/changelog_page.php
>>>>> _______________________________________________
>>>>> 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 hitcaozx at gmail.com  Fri Jun 10 18:07:46 2016
From: hitcaozx at gmail.com (=?UTF-8?B?5pu55pm66YCJ?=)
Date: Fri, 10 Jun 2016 18:07:46 -0400
Subject: [Paraview] ANN: ParaView 5.1.0-RC1 available for download
In-Reply-To: <9699c536-51d3-950f-b5a5-fcbce6811dce@mail.ru>
References: <CADHSJjCTEFP3VOFm+k2vE-gxN8nojz5q4rDjKL9ZUhgDFeG9hw@mail.gmail.com>
 <96B43CB6-F195-489A-A24A-2305F5AD5C10@gmail.com>
 <c571d7c3-69b7-dcd8-4b5d-5379f90a46f6@mail.ru>
 <CADHSJjAcCR+zggqXUk75yfCi6Vd5dw+ncqt5SmYLNS2nKUcnbw@mail.gmail.com>
 <CADHSJjDrpBFvbiXTjvJDY0YFcUh_BPAoZYW9f=bJUt45t3bgxQ@mail.gmail.com>
 <9699c536-51d3-950f-b5a5-fcbce6811dce@mail.ru>
Message-ID: <CANO2j4OWNiN2wdZ8Lw1-oQ97xURrrHtmhdd_p24cgm7ewJDovw@mail.gmail.com>

Why I still have the error:
How could I get rid of them?


 /rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/paraview:
/usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by
/rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/libvtkPVServerManagerCore-pv5.1.so.1)
/rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/paraview:
/usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by
/rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/libvtkPVClientServerCoreCore-pv5.1.so.1)
/rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/paraview:
/usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by
/rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/libvtkParallelCore-pv5.1.so.1)
/rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/paraview:
/usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by
/rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/libvtkIOCore-pv5.1.so.1)
/rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/paraview:
/usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by
/rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/libvtkRenderingCore-pv5.1.so.1)
/rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/paraview:
/usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by
/rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/libvtkCommonDataModel-pv5.1.so.1)
/rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/paraview:
/usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by
/rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/libvtkPVServerManagerRendering-pv5.1.so.1)
/rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/paraview:
/usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by
/rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/libvtkPVVTKExtensionsDefault-pv5.1.so.1)
/rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/paraview:
/usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by
/rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/libvtkFiltersParallelFlowPaths-pv5.1.so.1)
/rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/paraview:
/usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by
/rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/libvtkFiltersFlowPaths-pv5.1.so.1)
/rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/paraview:
/usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by
/rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/libvtkIOImport-pv5.1.so.1)
/rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/paraview:
/usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by
/rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/libvtkIOParallel-pv5.1.so.1)
/rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/paraview:
/usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by
/rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/libvtkIOExodus-pv5.1.so.1)
/rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/paraview:
/usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by
/rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/libembree.so.2)
/rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/paraview:
/usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.17' not found (required by
/rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/libospray.so.0)
/rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/paraview:
/usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by
/rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/libvtkInteractionWidgets-pv5.1.so.1)
/rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/paraview:
/usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by
/rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/libvtkRenderingAnnotation-pv5.1.so.1)
/rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/paraview:
/usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by
/rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/libvtkRenderingVolume-pv5.1.so.1)
/rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/paraview:
/usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by
/rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/libvtkPVClientServerCoreDefault-pv5.1.so.1)
/rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/paraview:
/usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by
/rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/libvtkFiltersParallelDIY2-pv5.1.so.1)
/rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/paraview:
/usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by
/rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/libvtkIOLSDyna-pv5.1.so.1)
/rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/paraview:
/usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by
/rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/libvtkIOVisItBridge-pv5.1.so.1)
/rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/paraview:
/usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by
/rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/libvtkRenderingParallelLIC-pv5.1.so.1)
/rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/paraview:
/usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by
/rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/libvtkRenderingContextOpenGL2-pv5.1.so.1)
/rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/paraview:
/usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by
/rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/libQtCLucene.so.4)
/rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/paraview:
/usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by
/rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/libvtkmetaio-pv5.1.so.1)
/rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/paraview:
/usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by
/rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/libvtkavtdatabase_par-pv5.1.so.1)
/rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/paraview:
/usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by
/rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/libvtklightweight_visit_vtk-pv5.1.so.1)
/rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/paraview:
/usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by
/rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/libvtkavtdbatts-pv5.1.so.1)
/rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/paraview:
/usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by
/rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/libXdmfCore.so)


2016-06-10 17:16 GMT-04:00 Gena Bug via ParaView <paraview at paraview.org>:

> On 10.06.2016 18:21, Utkarsh Ayachit wrote:
>
>> New binaries for linux have been uploaded. Please give them a go.
>>
> Now it seems to work... At least it starts and I can do basic stuff.
>
> Thanks, Utkarsh!
>
>
> Thanks
>> Utkarsh
>>
>> On Thu, Jun 9, 2016 at 7:10 PM, Utkarsh Ayachit
>> <utkarsh.ayachit at kitware.com> wrote:
>>
>>> Roger that. I've getting a new build. I switched to using a new build
>>> machine -- looks like that was premature. I'll upload binaries from
>>> the old build machine once they are available.
>>>
>>>
>>>
>>> On Thu, Jun 9, 2016 at 3:31 PM, Gena Bug via ParaView
>>> <paraview at paraview.org> wrote:
>>>
>>>> Hi!
>>>>
>>>> Can't run anything from bin:
>>>>
>>>> $ ./paraview
>>>>
>>>> ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/paraview:
>>>> error while loading shared libraries: libmpich.so.3: cannot open shared
>>>> object file: No such file or directory
>>>>
>>>> I have libmpich.so in the system (Debian testing), so I symlinked to
>>>> it, but
>>>> it didn't help -- after a series of new symlinks:
>>>> 1. libmpich.so.3 -> libmpich.so
>>>> 2. libopa.so.1 -> libopa.so
>>>> 3. libmpl.so.1 -> libmpl.so
>>>> 4. ??? -> libembree.so.2
>>>>
>>>> I stopped at last step because can't find any package with libembree...
>>>>
>>>>
>>>>
>>>> On 09.06.2016 19:27, Zhixuan Cao wrote:
>>>>
>>>>>
>>>>> Very happy to hear that. Is there any documentation about the detail of
>>>>> new features? For example, what is the exact equation for the new
>>>>> feature
>>>>> SPH interpolation?
>>>>>
>>>>>>
>>>>>> On Jun 9, 2016, at 10:59 AM, Utkarsh Ayachit
>>>>>> <utkarsh.ayachit at kitware.com> wrote:
>>>>>>
>>>>>> Folks,
>>>>>>
>>>>>> ParaView 5.1.0-RC1 is now available for download [1]. For fixes that
>>>>>> went into this release, refer to the change log on bug tracker [2].
>>>>>>
>>>>>> Detailed release notes coming soon.
>>>>>>
>>>>>> - The ParaView team
>>>>>>
>>>>>> [1] http://www.paraview.org/download/
>>>>>> [2] http://www.paraview.org/Bug/changelog_page.php
>>>>>> _______________________________________________
>>>>>> 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
>>>>
>>>
>> _______________________________________________
> 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/20160610/024009ff/attachment.html>

From dave.demarle at kitware.com  Fri Jun 10 20:03:14 2016
From: dave.demarle at kitware.com (David E DeMarle)
Date: Fri, 10 Jun 2016 20:03:14 -0400
Subject: [Paraview] ANN: ParaView 5.1.0-RC1 available for download
In-Reply-To: <CANO2j4OWNiN2wdZ8Lw1-oQ97xURrrHtmhdd_p24cgm7ewJDovw@mail.gmail.com>
References: <CADHSJjCTEFP3VOFm+k2vE-gxN8nojz5q4rDjKL9ZUhgDFeG9hw@mail.gmail.com>
 <96B43CB6-F195-489A-A24A-2305F5AD5C10@gmail.com>
 <c571d7c3-69b7-dcd8-4b5d-5379f90a46f6@mail.ru>
 <CADHSJjAcCR+zggqXUk75yfCi6Vd5dw+ncqt5SmYLNS2nKUcnbw@mail.gmail.com>
 <CADHSJjDrpBFvbiXTjvJDY0YFcUh_BPAoZYW9f=bJUt45t3bgxQ@mail.gmail.com>
 <9699c536-51d3-950f-b5a5-fcbce6811dce@mail.ru>
 <CANO2j4OWNiN2wdZ8Lw1-oQ97xURrrHtmhdd_p24cgm7ewJDovw@mail.gmail.com>
Message-ID: <CANjZAi-B8ErxgadSVVaVS_kWKZsB2tOaZ_0AEjxd0Sci3GcBUQ@mail.gmail.com>

Looks like your linux distribution's libc++ is too old for the binary.

What linux distribution are you on?


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

On Fri, Jun 10, 2016 at 6:07 PM, ??? <hitcaozx at gmail.com> wrote:

> Why I still have the error:
> How could I get rid of them?
>
>
>  /rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/paraview:
> /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by
> /rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/libvtkPVServerManagerCore-pv5.1.so.1)
> /rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/paraview:
> /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by
> /rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/libvtkPVClientServerCoreCore-pv5.1.so.1)
> /rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/paraview:
> /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by
> /rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/libvtkParallelCore-pv5.1.so.1)
> /rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/paraview:
> /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by
> /rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/libvtkIOCore-pv5.1.so.1)
> /rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/paraview:
> /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by
> /rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/libvtkRenderingCore-pv5.1.so.1)
> /rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/paraview:
> /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by
> /rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/libvtkCommonDataModel-pv5.1.so.1)
> /rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/paraview:
> /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by
> /rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/libvtkPVServerManagerRendering-pv5.1.so.1)
> /rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/paraview:
> /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by
> /rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/libvtkPVVTKExtensionsDefault-pv5.1.so.1)
> /rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/paraview:
> /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by
> /rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/libvtkFiltersParallelFlowPaths-pv5.1.so.1)
> /rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/paraview:
> /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by
> /rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/libvtkFiltersFlowPaths-pv5.1.so.1)
> /rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/paraview:
> /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by
> /rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/libvtkIOImport-pv5.1.so.1)
> /rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/paraview:
> /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by
> /rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/libvtkIOParallel-pv5.1.so.1)
> /rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/paraview:
> /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by
> /rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/libvtkIOExodus-pv5.1.so.1)
> /rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/paraview:
> /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by
> /rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/libembree.so.2)
> /rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/paraview:
> /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.17' not found (required by
> /rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/libospray.so.0)
> /rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/paraview:
> /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by
> /rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/libvtkInteractionWidgets-pv5.1.so.1)
> /rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/paraview:
> /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by
> /rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/libvtkRenderingAnnotation-pv5.1.so.1)
> /rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/paraview:
> /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by
> /rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/libvtkRenderingVolume-pv5.1.so.1)
> /rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/paraview:
> /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by
> /rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/libvtkPVClientServerCoreDefault-pv5.1.so.1)
> /rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/paraview:
> /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by
> /rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/libvtkFiltersParallelDIY2-pv5.1.so.1)
> /rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/paraview:
> /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by
> /rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/libvtkIOLSDyna-pv5.1.so.1)
> /rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/paraview:
> /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by
> /rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/libvtkIOVisItBridge-pv5.1.so.1)
> /rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/paraview:
> /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by
> /rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/libvtkRenderingParallelLIC-pv5.1.so.1)
> /rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/paraview:
> /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by
> /rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/libvtkRenderingContextOpenGL2-pv5.1.so.1)
> /rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/paraview:
> /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by
> /rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/libQtCLucene.so.4)
> /rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/paraview:
> /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by
> /rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/libvtkmetaio-pv5.1.so.1)
> /rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/paraview:
> /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by
> /rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/libvtkavtdatabase_par-pv5.1.so.1)
> /rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/paraview:
> /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by
> /rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/libvtklightweight_visit_vtk-pv5.1.so.1)
> /rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/paraview:
> /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by
> /rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/libvtkavtdbatts-pv5.1.so.1)
> /rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/paraview:
> /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by
> /rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/libXdmfCore.so)
>
>
> 2016-06-10 17:16 GMT-04:00 Gena Bug via ParaView <paraview at paraview.org>:
>
>> On 10.06.2016 18:21, Utkarsh Ayachit wrote:
>>
>>> New binaries for linux have been uploaded. Please give them a go.
>>>
>> Now it seems to work... At least it starts and I can do basic stuff.
>>
>> Thanks, Utkarsh!
>>
>>
>> Thanks
>>> Utkarsh
>>>
>>> On Thu, Jun 9, 2016 at 7:10 PM, Utkarsh Ayachit
>>> <utkarsh.ayachit at kitware.com> wrote:
>>>
>>>> Roger that. I've getting a new build. I switched to using a new build
>>>> machine -- looks like that was premature. I'll upload binaries from
>>>> the old build machine once they are available.
>>>>
>>>>
>>>>
>>>> On Thu, Jun 9, 2016 at 3:31 PM, Gena Bug via ParaView
>>>> <paraview at paraview.org> wrote:
>>>>
>>>>> Hi!
>>>>>
>>>>> Can't run anything from bin:
>>>>>
>>>>> $ ./paraview
>>>>>
>>>>> ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/paraview:
>>>>> error while loading shared libraries: libmpich.so.3: cannot open shared
>>>>> object file: No such file or directory
>>>>>
>>>>> I have libmpich.so in the system (Debian testing), so I symlinked to
>>>>> it, but
>>>>> it didn't help -- after a series of new symlinks:
>>>>> 1. libmpich.so.3 -> libmpich.so
>>>>> 2. libopa.so.1 -> libopa.so
>>>>> 3. libmpl.so.1 -> libmpl.so
>>>>> 4. ??? -> libembree.so.2
>>>>>
>>>>> I stopped at last step because can't find any package with libembree...
>>>>>
>>>>>
>>>>>
>>>>> On 09.06.2016 19:27, Zhixuan Cao wrote:
>>>>>
>>>>>>
>>>>>> Very happy to hear that. Is there any documentation about the detail
>>>>>> of
>>>>>> new features? For example, what is the exact equation for the new
>>>>>> feature
>>>>>> SPH interpolation?
>>>>>>
>>>>>>>
>>>>>>> On Jun 9, 2016, at 10:59 AM, Utkarsh Ayachit
>>>>>>> <utkarsh.ayachit at kitware.com> wrote:
>>>>>>>
>>>>>>> Folks,
>>>>>>>
>>>>>>> ParaView 5.1.0-RC1 is now available for download [1]. For fixes that
>>>>>>> went into this release, refer to the change log on bug tracker [2].
>>>>>>>
>>>>>>> Detailed release notes coming soon.
>>>>>>>
>>>>>>> - The ParaView team
>>>>>>>
>>>>>>> [1] http://www.paraview.org/download/
>>>>>>> [2] http://www.paraview.org/Bug/changelog_page.php
>>>>>>> _______________________________________________
>>>>>>> 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
>>>>>
>>>>
>>> _______________________________________________
>> 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/20160610/906589be/attachment.html>

From ansingh16 at gmail.com  Mon Jun 13 02:29:37 2016
From: ansingh16 at gmail.com (Ankit Singh)
Date: Mon, 13 Jun 2016 11:59:37 +0530
Subject: [Paraview] Fwd: Error : vtkProcessShader not found
In-Reply-To: <mailman.435.1465798684.17623.paraview@paraview.org>
References: <mailman.435.1465798684.17623.paraview@paraview.org>
Message-ID: <CALh38Uf5ev1qzPHFU+4=y9LZqK+LwhiAVGuXxocP21cUWWwJUw@mail.gmail.com>

Hi,

I am trying to install a plugin to paraview called parastro :

https://github.com/corbett/parastro

when I ccmake it  I am getting an error of :

 CMake Error at /usr/lib/cmake/paraview/ParaViewTargets.cmake:1498
(message):
   The imported target "ProcessShader" references the file

      "/usr/bin/vtkProcessShader"

   but this file does not exist.  Possible reasons include:

   * The file was deleted, renamed, or moved to another location.

   * An install or uninstall procedure did not complete successfully.

   * The installation package was faulty and contained

      "/usr/lib/cmake/paraview/ParaViewTargets.cmake"

   but not all the files it references.

 Call Stack (most recent call first):
   /usr/lib/cmake/paraview/ParaViewConfig.cmake:36 (include)
   CMakeLists.txt:6 (FIND_PACKAGE)

I already have installed paraview-dev and libvtk5-dev packages but still
the error persists . I am using a 32 bit machine with linux-mint .

Please help,

Thanks in advance.


Ankit SIngh
IISER Mohali,
India
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160613/ee7f23dc/attachment.html>

From david.larsson at sth.kth.se  Mon Jun 13 04:12:26 2016
From: david.larsson at sth.kth.se (David Larsson)
Date: Mon, 13 Jun 2016 08:12:26 +0000
Subject: [Paraview] visualize traced particles
In-Reply-To: <CAB5Fpx4qthu7C6TP-FTKbNo5ZVKO7Q8rtKBjo_b6UT-fkbDmyg@mail.gmail.com>
References: <1464881196894.57602@sth.kth.se>,
 <CAB5Fpx4qthu7C6TP-FTKbNo5ZVKO7Q8rtKBjo_b6UT-fkbDmyg@mail.gmail.com>
Message-ID: <1465805546331.48445@sth.kth.se>

Hi Cory,

thanks for the helpful info.

As an initial test step, I loaded the traced particles as a csv table and converted the spatial coordinates to data points (as you suggested). I can then see time as a variable in the scroll list gui, also enabling me to see different time points as different colors (i.e. with differently annoted values), as seen in the attachment.

What I would like to is to select a given time points and see where my particles are at that time. I thought that would be easily achievable with a "Threshold" filter, but even though I can see that the time data range spans (in this case) [0.478, 0.522], whenever I threshold within that time (e.g. [min, max]: [0.478, 0.5]) all my particles disappear. Do you know why that is? Or is there another way I could do to select a specified time step?

I've also added the actual csv-file if that helps.

Thansk for all suggestions,

/David

________________________________________
Fr?n: Cory Quammen <cory.quammen at kitware.com>
Skickat: den 8 juni 2016 16:45
Till: David Larsson
Kopia: paraview at paraview.org
?mne: Re: [Paraview] visualize traced particles

David,

Sure, this is possible. To view pathlines, you'll need to either write
a kind of file reader, probably a python Programmable Source, or
convert your file into a format ParaView can read, such as an XML
polydata file. The pathlines can be stored as vtkPolyLine cells in a
vtkPolyData.

If you just want to view the particles, you can likely read the file
directly using the CSV reader. Assuming your data is in the format

x y z t

the file will be read as a table. You'll need to convert the table to
points using the Table to Points filter. Choose the X, Y, and Z
columns for your data. The time column will be added as a variable
associated with the point.

HTH,
Cory

On Thu, Jun 2, 2016 at 5:26 PM, David Larsson <david.larsson at sth.kth.se> wrote:
> Dear Paraview community,
>
>
> in an external program, I've traced particles inside a 3D(+time) flow field
> and extracted each particles spatial position (x,y,z) in time.
>
>
> I have this data saved in an ascii-output where each particle position (with
> time) is simply written out.
>
>
> Now to my question: is there any convenient way of visualizing these
> pathlines in paraview? Can I load and look at that kind of data in a direct
> way? Or can you even visualize how the particle progresses in space over
> time?
>
>
> Thanks for your help.
>
>
> /David
>
>
> _______________________________________________
> 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 --------------
A non-text attachment was scrubbed...
Name: traces.png
Type: image/png
Size: 36023 bytes
Desc: traces.png
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160613/2e67a9ba/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: myTraces.csv
Type: text/csv
Size: 77573 bytes
Desc: myTraces.csv
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160613/2e67a9ba/attachment.csv>

From cory.quammen at kitware.com  Mon Jun 13 06:12:14 2016
From: cory.quammen at kitware.com (Cory Quammen)
Date: Mon, 13 Jun 2016 12:12:14 +0200
Subject: [Paraview] visualize traced particles
In-Reply-To: <1465805546331.48445@sth.kth.se>
References: <1464881196894.57602@sth.kth.se>
 <CAB5Fpx4qthu7C6TP-FTKbNo5ZVKO7Q8rtKBjo_b6UT-fkbDmyg@mail.gmail.com>
 <1465805546331.48445@sth.kth.se>
Message-ID: <CAB5Fpx5c+1M-n-UjuNFnOPd9nk54umzMNBr53GNmx25kSmL-9g@mail.gmail.com>

David,

It is subtle, but the reason is that the Threshold filter works only
on data with cells, not directly on points. The typical solution is to
apply the Glyph filter, then the Threshold filter.

There really should be a Threshold Points filter in ParaView because
this comes up time and time again.

Thanks,
Cory

On Mon, Jun 13, 2016 at 10:12 AM, David Larsson
<david.larsson at sth.kth.se> wrote:
> Hi Cory,
>
> thanks for the helpful info.
>
> As an initial test step, I loaded the traced particles as a csv table and converted the spatial coordinates to data points (as you suggested). I can then see time as a variable in the scroll list gui, also enabling me to see different time points as different colors (i.e. with differently annoted values), as seen in the attachment.
>
> What I would like to is to select a given time points and see where my particles are at that time. I thought that would be easily achievable with a "Threshold" filter, but even though I can see that the time data range spans (in this case) [0.478, 0.522], whenever I threshold within that time (e.g. [min, max]: [0.478, 0.5]) all my particles disappear. Do you know why that is? Or is there another way I could do to select a specified time step?
>
> I've also added the actual csv-file if that helps.
>
> Thansk for all suggestions,
>
> /David
>
> ________________________________________
> Fr?n: Cory Quammen <cory.quammen at kitware.com>
> Skickat: den 8 juni 2016 16:45
> Till: David Larsson
> Kopia: paraview at paraview.org
> ?mne: Re: [Paraview] visualize traced particles
>
> David,
>
> Sure, this is possible. To view pathlines, you'll need to either write
> a kind of file reader, probably a python Programmable Source, or
> convert your file into a format ParaView can read, such as an XML
> polydata file. The pathlines can be stored as vtkPolyLine cells in a
> vtkPolyData.
>
> If you just want to view the particles, you can likely read the file
> directly using the CSV reader. Assuming your data is in the format
>
> x y z t
>
> the file will be read as a table. You'll need to convert the table to
> points using the Table to Points filter. Choose the X, Y, and Z
> columns for your data. The time column will be added as a variable
> associated with the point.
>
> HTH,
> Cory
>
> On Thu, Jun 2, 2016 at 5:26 PM, David Larsson <david.larsson at sth.kth.se> wrote:
>> Dear Paraview community,
>>
>>
>> in an external program, I've traced particles inside a 3D(+time) flow field
>> and extracted each particles spatial position (x,y,z) in time.
>>
>>
>> I have this data saved in an ascii-output where each particle position (with
>> time) is simply written out.
>>
>>
>> Now to my question: is there any convenient way of visualizing these
>> pathlines in paraview? Can I load and look at that kind of data in a direct
>> way? Or can you even visualize how the particle progresses in space over
>> time?
>>
>>
>> Thanks for your help.
>>
>>
>> /David
>>
>>
>> _______________________________________________
>> 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 david.larsson at sth.kth.se  Mon Jun 13 06:16:57 2016
From: david.larsson at sth.kth.se (David Larsson)
Date: Mon, 13 Jun 2016 10:16:57 +0000
Subject: [Paraview] visualize traced particles
In-Reply-To: <CAB5Fpx5c+1M-n-UjuNFnOPd9nk54umzMNBr53GNmx25kSmL-9g@mail.gmail.com>
References: <1464881196894.57602@sth.kth.se>
 <CAB5Fpx4qthu7C6TP-FTKbNo5ZVKO7Q8rtKBjo_b6UT-fkbDmyg@mail.gmail.com>
 <1465805546331.48445@sth.kth.se>,
 <CAB5Fpx5c+1M-n-UjuNFnOPd9nk54umzMNBr53GNmx25kSmL-9g@mail.gmail.com>
Message-ID: <1465813016785.30548@sth.kth.se>

Right. Good to know. Using your work-around method seem to work.

Thanks again for all the help.

/David

________________________________________
Fr?n: Cory Quammen <cory.quammen at kitware.com>
Skickat: den 13 juni 2016 12:12
Till: David Larsson
Kopia: paraview at paraview.org
?mne: Re: [Paraview] visualize traced particles

David,

It is subtle, but the reason is that the Threshold filter works only
on data with cells, not directly on points. The typical solution is to
apply the Glyph filter, then the Threshold filter.

There really should be a Threshold Points filter in ParaView because
this comes up time and time again.

Thanks,
Cory

On Mon, Jun 13, 2016 at 10:12 AM, David Larsson
<david.larsson at sth.kth.se> wrote:
> Hi Cory,
>
> thanks for the helpful info.
>
> As an initial test step, I loaded the traced particles as a csv table and converted the spatial coordinates to data points (as you suggested). I can then see time as a variable in the scroll list gui, also enabling me to see different time points as different colors (i.e. with differently annoted values), as seen in the attachment.
>
> What I would like to is to select a given time points and see where my particles are at that time. I thought that would be easily achievable with a "Threshold" filter, but even though I can see that the time data range spans (in this case) [0.478, 0.522], whenever I threshold within that time (e.g. [min, max]: [0.478, 0.5]) all my particles disappear. Do you know why that is? Or is there another way I could do to select a specified time step?
>
> I've also added the actual csv-file if that helps.
>
> Thansk for all suggestions,
>
> /David
>
> ________________________________________
> Fr?n: Cory Quammen <cory.quammen at kitware.com>
> Skickat: den 8 juni 2016 16:45
> Till: David Larsson
> Kopia: paraview at paraview.org
> ?mne: Re: [Paraview] visualize traced particles
>
> David,
>
> Sure, this is possible. To view pathlines, you'll need to either write
> a kind of file reader, probably a python Programmable Source, or
> convert your file into a format ParaView can read, such as an XML
> polydata file. The pathlines can be stored as vtkPolyLine cells in a
> vtkPolyData.
>
> If you just want to view the particles, you can likely read the file
> directly using the CSV reader. Assuming your data is in the format
>
> x y z t
>
> the file will be read as a table. You'll need to convert the table to
> points using the Table to Points filter. Choose the X, Y, and Z
> columns for your data. The time column will be added as a variable
> associated with the point.
>
> HTH,
> Cory
>
> On Thu, Jun 2, 2016 at 5:26 PM, David Larsson <david.larsson at sth.kth.se> wrote:
>> Dear Paraview community,
>>
>>
>> in an external program, I've traced particles inside a 3D(+time) flow field
>> and extracted each particles spatial position (x,y,z) in time.
>>
>>
>> I have this data saved in an ascii-output where each particle position (with
>> time) is simply written out.
>>
>>
>> Now to my question: is there any convenient way of visualizing these
>> pathlines in paraview? Can I load and look at that kind of data in a direct
>> way? Or can you even visualize how the particle progresses in space over
>> time?
>>
>>
>> Thanks for your help.
>>
>>
>> /David
>>
>>
>> _______________________________________________
>> 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 apeczak at ara.co.uk  Mon Jun 13 07:20:53 2016
From: apeczak at ara.co.uk (Andrzej Peczak)
Date: Mon, 13 Jun 2016 11:20:53 +0000
Subject: [Paraview] Forcing update on view
Message-ID: <5DF928D22AC3AC4B964903E98F2E54515B59F2DA@sooty3.win.ara>

Hi, 

I have a snippet code which I wrote to allow me to save multiple plot images to files. I do it by changing property checkboxes of Composite Data Set Index property. I can change their status programmatically but the view is not being updated. When I change them manually in the UI the view knows about their status change and plots only the content I select. I tried to force the update with UpdateVTkObjects() of available properties plus explicitly calling render()/forceRender() of the view but with no success.  Every file I create has multiple plot curves in it instead of one.

Andrzej

	pqDataRepresentation *repr = source->getRepresentation( view );
	auto chartRepresentationProxy = repr->getProxy();
	vtkSMPropertyHelper helper( repr->getProxy(), "CompositeDataSetIndex" );

	vtkSMProperty *property = chartRepresentationProxy->GetProperty( "CompositeDataSetIndex" );
	if ( property ) {

		auto VectorProperty = vtkSMIntVectorProperty::SafeDownCast( property );
		if ( VectorProperty ) {

			const auto numElements = VectorProperty->GetNumberOfElements();
			int elements[ numElements ];
			std::copy( VectorProperty->GetElements(), VectorProperty->GetElements() + numElements, elements );
			for ( auto i = 0 ; i != numElements ; ++i ) {
				VectorProperty->SetElement( elements[ i ], 0 );
			}

			for ( auto i = 0 ; i != numElements ; ++i ) {
				VectorProperty->SetElement( elements[ i ], 1 );

				source->getSourceProxy()->UpdateVTKObjects();
				view->getViewProxy()->UpdateVTKObjects();
				view->getViewProxy()->Update();
				repr = source->getRepresentation( view );
				repr->getProxy()->UpdateVTKObjects();
				repr->renderView( true );
				property->GetParent()->UpdateVTKObjects();
				view->cancelPendingRenders();
				view->forceRender();

				std::stringstream ssFileName;
				std::string ext , newName2;
				std::string::size_type dot_pos = newName.rfind( '.' );
				if ( dot_pos != std::string::npos ) {
					ext = newName.substr( dot_pos );
					newName2 = newName.substr( 0, dot_pos );
				}
				ssFileName << newName2 << "_" << i + 1 << ext;
				view->writeImage( ssFileName.str().c_str(), size, quality );
				VectorProperty->SetElement( elements[ i ], 0 );
			}

			VectorProperty->SetElements( elements );
		}
	}

**********************************************************************
Please consider the environment. Only print this email if absolutely necessary.

This email contains information that is private and confidential and is intended only for the addressee.
If you are not the intended recipient please delete it and notify us immediately by e-mailing the sender.
Note: All email sent to or from this address may be accessed by someone other than the recipient, for
system management and security reasons.
Aircraft Research Association Ltd.  Registered in England, Registration No 503668 Registered Office:
Manton Lane, Bedford MK41 7PF England VAT No GB 196351245

**********************************************************************

From dkxls23 at gmail.com  Mon Jun 13 11:56:54 2016
From: dkxls23 at gmail.com (Armin Wehrfritz)
Date: Mon, 13 Jun 2016 18:56:54 +0300
Subject: [Paraview] tikz/tex export for paraview contour plots
In-Reply-To: <572FDED6.9030405@gmail.com>
References: <572FDED6.9030405@gmail.com>
Message-ID: <575ED7C6.9080000@gmail.com>

Hi Richard,


> We created a small python tool, that essentially embeds the figure
> created in paraview into a tikz picture and adds axes. However, we
> still need to manually specify the the extent of the plot in that
> script which is tedious.
This is slightly off-topic, but I have been using a similar approach
(tikz/tex + png images) to include plots from python/matplotlib in my
LaTeX documents. For this I can just recommend the matplotlib2tikz
package [1].

Using VTK/ParaView, I have had some attempts to set the render window
size and camera in python scripts, but could not yet figure out how
to extract the information on the data/viewport extend.


> a) Did anyone encounter the same issue and is willing to share a
> script or so?
My VTK and ParaView scripts are based on information I gathered from two
mailing list discussions, see [2,3]. My scripts are probably not much of
help, but I can dig them out if you are interested.


> b) If not, is there a way to extract the Viewport extent in a python
>  script so that we can directly set them in the script?
That's the missing piece in the puzzle I couldn't quite figure out yet,
but I would also be interested in this. The code in discussion [2] has
some examples on coordinate transforms in VTK, but I didn't have the
time to look deeper into this.


Cheers,
Armin


[1] https://github.com/nschloe/matplotlib2tikz
[2] http://www.vtk.org/pipermail/vtk-developers/2005-November/019314.html
[3]
http://paraview.paraview.narkive.com/8hsmkC4u/python-paraview-simple-zoom-to-data


From hitcaozx at gmail.com  Mon Jun 13 12:11:29 2016
From: hitcaozx at gmail.com (=?UTF-8?B?5pu55pm66YCJ?=)
Date: Mon, 13 Jun 2016 12:11:29 -0400
Subject: [Paraview] ANN: ParaView 5.1.0-RC1 available for download
In-Reply-To: <CANO2j4OWNiN2wdZ8Lw1-oQ97xURrrHtmhdd_p24cgm7ewJDovw@mail.gmail.com>
References: <CADHSJjCTEFP3VOFm+k2vE-gxN8nojz5q4rDjKL9ZUhgDFeG9hw@mail.gmail.com>
 <96B43CB6-F195-489A-A24A-2305F5AD5C10@gmail.com>
 <c571d7c3-69b7-dcd8-4b5d-5379f90a46f6@mail.ru>
 <CADHSJjAcCR+zggqXUk75yfCi6Vd5dw+ncqt5SmYLNS2nKUcnbw@mail.gmail.com>
 <CADHSJjDrpBFvbiXTjvJDY0YFcUh_BPAoZYW9f=bJUt45t3bgxQ@mail.gmail.com>
 <9699c536-51d3-950f-b5a5-fcbce6811dce@mail.ru>
 <CANO2j4OWNiN2wdZ8Lw1-oQ97xURrrHtmhdd_p24cgm7ewJDovw@mail.gmail.com>
Message-ID: <CANO2j4P8KAThsr8Jr+ZYeC8XQt7XWcPvY5W+q=EDGUe9gpF6+g@mail.gmail.com>

It turned out that the operating system on my machine does not have the
library: GLIBCXX_3.4.15. And the linux system on my machine does not allow
me upgrading the library to GLIBCXX_3.4.15.
Is there any other way that I can still use the new version of paraview
without GLIBCXX_3.4.15? I only want to use the SPH interpolation feature of
the new paraview.

Thanks!

Zhixuan Cao

2016-06-10 18:07 GMT-04:00 ??? <hitcaozx at gmail.com>:

> Why I still have the error:
> How could I get rid of them?
>
>
>  /rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/paraview:
> /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by
> /rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/libvtkPVServerManagerCore-pv5.1.so.1)
> /rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/paraview:
> /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by
> /rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/libvtkPVClientServerCoreCore-pv5.1.so.1)
> /rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/paraview:
> /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by
> /rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/libvtkParallelCore-pv5.1.so.1)
> /rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/paraview:
> /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by
> /rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/libvtkIOCore-pv5.1.so.1)
> /rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/paraview:
> /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by
> /rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/libvtkRenderingCore-pv5.1.so.1)
> /rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/paraview:
> /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by
> /rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/libvtkCommonDataModel-pv5.1.so.1)
> /rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/paraview:
> /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by
> /rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/libvtkPVServerManagerRendering-pv5.1.so.1)
> /rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/paraview:
> /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by
> /rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/libvtkPVVTKExtensionsDefault-pv5.1.so.1)
> /rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/paraview:
> /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by
> /rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/libvtkFiltersParallelFlowPaths-pv5.1.so.1)
> /rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/paraview:
> /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by
> /rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/libvtkFiltersFlowPaths-pv5.1.so.1)
> /rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/paraview:
> /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by
> /rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/libvtkIOImport-pv5.1.so.1)
> /rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/paraview:
> /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by
> /rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/libvtkIOParallel-pv5.1.so.1)
> /rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/paraview:
> /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by
> /rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/libvtkIOExodus-pv5.1.so.1)
> /rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/paraview:
> /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by
> /rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/libembree.so.2)
> /rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/paraview:
> /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.17' not found (required by
> /rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/libospray.so.0)
> /rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/paraview:
> /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by
> /rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/libvtkInteractionWidgets-pv5.1.so.1)
> /rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/paraview:
> /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by
> /rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/libvtkRenderingAnnotation-pv5.1.so.1)
> /rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/paraview:
> /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by
> /rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/libvtkRenderingVolume-pv5.1.so.1)
> /rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/paraview:
> /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by
> /rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/libvtkPVClientServerCoreDefault-pv5.1.so.1)
> /rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/paraview:
> /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by
> /rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/libvtkFiltersParallelDIY2-pv5.1.so.1)
> /rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/paraview:
> /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by
> /rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/libvtkIOLSDyna-pv5.1.so.1)
> /rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/paraview:
> /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by
> /rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/libvtkIOVisItBridge-pv5.1.so.1)
> /rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/paraview:
> /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by
> /rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/libvtkRenderingParallelLIC-pv5.1.so.1)
> /rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/paraview:
> /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by
> /rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/libvtkRenderingContextOpenGL2-pv5.1.so.1)
> /rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/paraview:
> /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by
> /rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/libQtCLucene.so.4)
> /rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/paraview:
> /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by
> /rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/libvtkmetaio-pv5.1.so.1)
> /rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/paraview:
> /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by
> /rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/libvtkavtdatabase_par-pv5.1.so.1)
> /rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/paraview:
> /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by
> /rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/libvtklightweight_visit_vtk-pv5.1.so.1)
> /rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/paraview:
> /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by
> /rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/libvtkavtdbatts-pv5.1.so.1)
> /rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/paraview:
> /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by
> /rohit1/data/users/zhixuanc/Soft/ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/libXdmfCore.so)
>
>
> 2016-06-10 17:16 GMT-04:00 Gena Bug via ParaView <paraview at paraview.org>:
>
>> On 10.06.2016 18:21, Utkarsh Ayachit wrote:
>>
>>> New binaries for linux have been uploaded. Please give them a go.
>>>
>> Now it seems to work... At least it starts and I can do basic stuff.
>>
>> Thanks, Utkarsh!
>>
>>
>> Thanks
>>> Utkarsh
>>>
>>> On Thu, Jun 9, 2016 at 7:10 PM, Utkarsh Ayachit
>>> <utkarsh.ayachit at kitware.com> wrote:
>>>
>>>> Roger that. I've getting a new build. I switched to using a new build
>>>> machine -- looks like that was premature. I'll upload binaries from
>>>> the old build machine once they are available.
>>>>
>>>>
>>>>
>>>> On Thu, Jun 9, 2016 at 3:31 PM, Gena Bug via ParaView
>>>> <paraview at paraview.org> wrote:
>>>>
>>>>> Hi!
>>>>>
>>>>> Can't run anything from bin:
>>>>>
>>>>> $ ./paraview
>>>>>
>>>>> ParaView-5.1.0-RC1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.1/paraview:
>>>>> error while loading shared libraries: libmpich.so.3: cannot open shared
>>>>> object file: No such file or directory
>>>>>
>>>>> I have libmpich.so in the system (Debian testing), so I symlinked to
>>>>> it, but
>>>>> it didn't help -- after a series of new symlinks:
>>>>> 1. libmpich.so.3 -> libmpich.so
>>>>> 2. libopa.so.1 -> libopa.so
>>>>> 3. libmpl.so.1 -> libmpl.so
>>>>> 4. ??? -> libembree.so.2
>>>>>
>>>>> I stopped at last step because can't find any package with libembree...
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> On 09.06.2016 19:27, Zhixuan Cao wrote:
>>>>>
>>>>>>
>>>>>> Very happy to hear that. Is there any documentation about the detail
>>>>>> of
>>>>>> new features? For example, what is the exact equation for the new
>>>>>> feature
>>>>>> SPH interpolation?
>>>>>>
>>>>>>>
>>>>>>> On Jun 9, 2016, at 10:59 AM, Utkarsh Ayachit
>>>>>>> <utkarsh.ayachit at kitware.com> wrote:
>>>>>>>
>>>>>>> Folks,
>>>>>>>
>>>>>>> ParaView 5.1.0-RC1 is now available for download [1]. For fixes that
>>>>>>> went into this release, refer to the change log on bug tracker [2].
>>>>>>>
>>>>>>> Detailed release notes coming soon.
>>>>>>>
>>>>>>> - The ParaView team
>>>>>>>
>>>>>>> [1] http://www.paraview.org/download/
>>>>>>> [2] http://www.paraview.org/Bug/changelog_page.php
>>>>>>> _______________________________________________
>>>>>>> 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
>>>>>
>>>>
>>> _______________________________________________
>> 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/20160613/46ef62b7/attachment.html>

From Matthias.Zenker at erbe-med.com  Mon Jun 13 12:43:31 2016
From: Matthias.Zenker at erbe-med.com (Zenker, Dr. Matthias)
Date: Mon, 13 Jun 2016 16:43:31 +0000
Subject: [Paraview] display boundaries of 2D geometry
Message-ID: <F9562F3B302F29479A203FC5AF9E3E050F48E2CA@SERBE4I1.intra.erbe-med.de>

Hi,

is there a way to display the boundaries (edges) of a 2D geometry? I have converted my mesh to vtu using Elmergrid, so I have the IDs of bodies (=surfaces in 2D) and boundaries (edges) in a vtu file. Can I just display the edges having the same ID? The extract edges filter does not help.  What else could I try?

Thank you for a helpful hint,

Matthias
________________________________

Erbe Elektromedizin GmbH Firmensitz: 72072 Tuebingen Geschaeftsfuehrer: Christian O. Erbe, Reiner Thede Registergericht: Stuttgart HRB 380137

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

From cory.quammen at kitware.com  Mon Jun 13 16:27:37 2016
From: cory.quammen at kitware.com (Cory Quammen)
Date: Mon, 13 Jun 2016 22:27:37 +0200
Subject: [Paraview] display boundaries of 2D geometry
In-Reply-To: <F9562F3B302F29479A203FC5AF9E3E050F48E2CA@SERBE4I1.intra.erbe-med.de>
References: <F9562F3B302F29479A203FC5AF9E3E050F48E2CA@SERBE4I1.intra.erbe-med.de>
Message-ID: <CAB5Fpx6cvUqnhYgNH295WEdN0T2FfQ9u=q4dfU4mP4jM4=xP-g@mail.gmail.com>

Matthias,

I'm not sure I fully understand exactly what you are trying to do, but
I will try to make a suggestion anyway. If the edges have a cell data
array giving the ID, you should be able to use the Threshold filter to
extract the edges associated with a particular body ID. Just set the
threshold values to the ID you want to see.

Hope that helps,
Cory

On Mon, Jun 13, 2016 at 6:43 PM, Zenker, Dr. Matthias
<Matthias.Zenker at erbe-med.com> wrote:
> Hi,
>
>
>
> is there a way to display the boundaries (edges) of a 2D geometry? I have
> converted my mesh to vtu using Elmergrid, so I have the IDs of bodies
> (=surfaces in 2D) and boundaries (edges) in a vtu file. Can I just display
> the edges having the same ID? The extract edges filter does not help.  What
> else could I try?
>
>
>
> Thank you for a helpful hint,
>
>
>
> Matthias
>
> ________________________________
>
> Erbe Elektromedizin GmbH Firmensitz: 72072 Tuebingen Geschaeftsfuehrer:
> Christian O. Erbe, Reiner Thede Registergericht: Stuttgart HRB 380137
>
>
> _______________________________________________
> 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 apeczak at ara.co.uk  Tue Jun 14 05:35:20 2016
From: apeczak at ara.co.uk (Andrzej Peczak)
Date: Tue, 14 Jun 2016 09:35:20 +0000
Subject: [Paraview] Forcing update on view
In-Reply-To: <5DF928D22AC3AC4B964903E98F2E54515B59F2DA@sooty3.win.ara>
References: <5DF928D22AC3AC4B964903E98F2E54515B59F2DA@sooty3.win.ara>
Message-ID: <5DF928D22AC3AC4B964903E98F2E54515B59F4D9@sooty3.win.ara>

I missed the question regarding the problem I describe. Is there a way to programmatically display the content of CompositeDataSetIndex property depending on status of the checkbox widgets I change through vector properties? 

Andrzej

Hi, 

I have a snippet code which I wrote to allow me to save multiple plot images to files. I do it by changing property checkboxes of Composite Data Set Index property. I can change their status programmatically but the view is not being updated. When I change them manually in the UI the view knows about their status change and plots only the content I select. I tried to force the update with UpdateVTkObjects() of available properties plus explicitly calling render()/forceRender() of the view but with no success.  Every file I create has multiple plot curves in it instead of one.

Andrzej

	pqDataRepresentation *repr = source->getRepresentation( view );
	auto chartRepresentationProxy = repr->getProxy();

	vtkSMProperty *property = chartRepresentationProxy->GetProperty( "CompositeDataSetIndex" );
	if ( property ) {

		auto VectorProperty = vtkSMIntVectorProperty::SafeDownCast( property );
		if ( VectorProperty ) {

			const auto numElements = VectorProperty->GetNumberOfElements();
			int elements[ numElements ];
			std::copy( VectorProperty->GetElements(), VectorProperty->GetElements() + numElements, elements );
			for ( auto i = 0 ; i != numElements ; ++i ) {
				VectorProperty->SetElement( elements[ i ], 0 );
			}

			for ( auto i = 0 ; i != numElements ; ++i ) {
				VectorProperty->SetElement( elements[ i ], 1 );

				source->getSourceProxy()->UpdateVTKObjects();
				view->getViewProxy()->UpdateVTKObjects();
				view->getViewProxy()->Update();
				repr = source->getRepresentation( view );
				repr->getProxy()->UpdateVTKObjects();
				repr->renderView( true );
				property->GetParent()->UpdateVTKObjects();
				view->cancelPendingRenders();
				view->forceRender();

				std::stringstream ssFileName;
				std::string ext , newName2;
				std::string::size_type dot_pos = newName.rfind( '.' );
				if ( dot_pos != std::string::npos ) {
					ext = newName.substr( dot_pos );
					newName2 = newName.substr( 0, dot_pos );
				}
				ssFileName << newName2 << "_" << i + 1 << ext;
				view->writeImage( ssFileName.str().c_str(), size, quality );
				VectorProperty->SetElement( elements[ i ], 0 );
			}

			VectorProperty->SetElements( elements );
		}
	}

**********************************************************************
Please consider the environment. Only print this email if absolutely necessary.

This email contains information that is private and confidential and is intended only for the addressee.
If you are not the intended recipient please delete it and notify us immediately by e-mailing the sender.
Note: All email sent to or from this address may be accessed by someone other than the recipient, for
system management and security reasons.
Aircraft Research Association Ltd.  Registered in England, Registration No 503668 Registered Office:
Manton Lane, Bedford MK41 7PF England VAT No GB 196351245

**********************************************************************

From Matthias.Zenker at erbe-med.com  Tue Jun 14 07:11:19 2016
From: Matthias.Zenker at erbe-med.com (Zenker, Dr. Matthias)
Date: Tue, 14 Jun 2016 11:11:19 +0000
Subject: [Paraview] display boundaries of 2D geometry
In-Reply-To: <CAB5Fpx6cvUqnhYgNH295WEdN0T2FfQ9u=q4dfU4mP4jM4=xP-g@mail.gmail.com>
References: <F9562F3B302F29479A203FC5AF9E3E050F48E2CA@SERBE4I1.intra.erbe-med.de>
 <CAB5Fpx6cvUqnhYgNH295WEdN0T2FfQ9u=q4dfU4mP4jM4=xP-g@mail.gmail.com>
Message-ID: <F9562F3B302F29479A203FC5AF9E3E050F48E330@SERBE4I1.intra.erbe-med.de>

Hi Cory,

this helped indeed, thank you.
I  load the mesh.vtu file and apply the Threshold filter on the GeometryID, and display that together with my simulation results. That works fine.
If I want to display several parts selectively, I can use several Thresholds, which is a bit clumsy.
It would be nice to be able to get a list of all GeometryIDs, and to check those which I want displayed. Do you know if there is a way to do that? Or on a more general basis: are there other, more elegant ways to display a geometry in ParaView?

Thanks again,

Matthias


> -----Urspr?ngliche Nachricht-----
> Von: Cory Quammen [mailto:cory.quammen at kitware.com]
> Gesendet: Montag, 13. Juni 2016 22:28
> An: Zenker, Dr. Matthias
> Cc: paraview at paraview.org
> Betreff: Re: [Paraview] display boundaries of 2D geometry
>
> Matthias,
>
> I'm not sure I fully understand exactly what you are trying to do, but
> I will try to make a suggestion anyway. If the edges have a cell data
> array giving the ID, you should be able to use the Threshold filter to
> extract the edges associated with a particular body ID. Just set the
> threshold values to the ID you want to see.
>
> Hope that helps,
> Cory
>
> On Mon, Jun 13, 2016 at 6:43 PM, Zenker, Dr. Matthias
> <Matthias.Zenker at erbe-med.com> wrote:
> > Hi,
> >
> >
> >
> > is there a way to display the boundaries (edges) of a 2D geometry? I have
> > converted my mesh to vtu using Elmergrid, so I have the IDs of bodies
> > (=surfaces in 2D) and boundaries (edges) in a vtu file. Can I just display
> > the edges having the same ID? The extract edges filter does not help.
> What
> > else could I try?
> >
> >
> >
> > Thank you for a helpful hint,
> >
> >
> >
> > Matthias
> >
> > ________________________________
> >
> > Erbe Elektromedizin GmbH Firmensitz: 72072 Tuebingen
> Geschaeftsfuehrer:
> > Christian O. Erbe, Reiner Thede Registergericht: Stuttgart HRB 380137
> >
> >
> > _______________________________________________
> > 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.
________________________________

Erbe Elektromedizin GmbH Firmensitz: 72072 Tuebingen Geschaeftsfuehrer: Christian O. Erbe, Reiner Thede Registergericht: Stuttgart HRB 380137


From dkxls23 at gmail.com  Tue Jun 14 08:06:41 2016
From: dkxls23 at gmail.com (Armin Wehrfritz)
Date: Tue, 14 Jun 2016 15:06:41 +0300
Subject: [Paraview] Slow with just 1M cells
In-Reply-To: <A49F5253-951C-4F62-B7DB-0CD73C3DD57C@sandia.gov>
References: <C732BAF0-0404-4FF7-A3B3-0AFC9F69A7C5@sandia.gov>
 <A49F5253-951C-4F62-B7DB-0CD73C3DD57C@sandia.gov>
Message-ID: <575FF351.4010703@gmail.com>

Hi Michele and Ken,

I'm also dealing with dataset that contain polyhedral cells. More
precisely my grids are generated using a "cutcell" approach where an
initially fully hexahedral mesh is refined in the main region of
interest. While most cells will be again hexahedral after the
refinement, the cells on the coarse side of the interface are of general
polyhderal shape. I assume Michele has a very similar approach, though
my data stem from CFD simulation using OpenFOAM.

The OpenFOAM reader in ParaView has an option to decompose polyhedral
cells into standard shapes (mostly pyramids in my case). For instance,
my original dataset has about 10.9M hexahedral and 147k polyhedral
cells. When reading the dataset in ParaView and decomposing the
polyhedral cells, I get in total 12.7M cells, i.e. approximately 1.7M
more than in the original dataset due to the decomposition.
Applying the tetrahedralize filter to the original dataset leads to
67.4M cells and the memory usage more than doubles. (The numbers are
listed below.)

I also experience a slowdown when I do not decompose the polyhedral
cells for the usual post-processing/visualization tasks.
However, I should note that for instance volume rendering of my dataset
with decomposed polyhedral cells is still painfully slow using ParaView
5.0.1 on my laptop (Intel i7-4800MQ 2.70GHz/ NVIDIA Quadro K2100M).
ParaView appears to spend the most of the time with something called
"OpenGLProjectedTetrahedraMapper".

I'm not sure which readers, other than the OpenFOAM reader, support the
decomposition of polyhedral cells, but the approach should work for any
unstructured dataset. So it might be worth considering to implement this
on a more general level, rather than in a specific reader.

Best regards,
Armin



Statistics
==========

OpenFOAM reader
Decompose polyhedra: On
------------------------
Cells: 12.7M
Points: 11.4M
Memory: 1100 MB

OpenFOAM reader
Decompose polyhedra: Off
------------------------
Cells: 11M
Points: 11.3M
Memory: 1800 MB

OpenFOAM reader
Decompose polyhedra: Off
Tetrahedralize filter
------------------------
Cells: 67.4M
Points: 11.3M
Memory: 3400 MB





On 05/25/2016 09:05 PM, Moreland, Kenneth wrote:
> Michele,
>
> I took a look at the data you sent me. I experienced many of the
> issues you brought up.
>
> After taking a closer look at the data, I realized that many of the
> cells in your data are of the general polyhedral type. Unlike the
> standard cell shapes like tetrahedron and hexahedron, polyhedral
> shapes are general polyhedra formed by specifying the face polygons.
> They allow you to specify any flat faceted shape, but computing basic
> operations on them such as interpolations, derivatives, and location
> finding is very expensive. This is why operations like streamlines
> are going so slowly.
>
> If the cells are represented as standard shapes, things go much
> faster. For example, if you tetrahedralize the data, streamlines
> takes well under 10 seconds. That gets the operations to about the
> range where your nameless commercial product is running. I suspect,
> but cannot verify, that this other visualization package is probably
> downgrading the cells to something like hexahedra, which makes it run
> faster.
>
> I don?t recommend running the tetrahedralization filter all the time
> on your data. It is also slow and really bloats the data. If you
> could write out an alternate form of the data that wrote hexahedra
> instead of polyhedra, I suspect things would run much faster. You
> would probably have a problem with faces not being aligned, though.
>
> One final note, although the clip filter is taking a long time, I
> found the slice filter to be much faster. Generally, when dealing
> with large data, you should favor slice over clip. It?s much faster,
> uses much less memory, and usually gives you the same information.
>
> -Ken
>
> On 5/21/16, 9:47 AM, "Moreland, Kenneth" <kmorel at sandia.gov> wrote:
>
>> Michele,
>>
>> Taking over a minute to process a data set with 1 million cells
>> does seem like an unreasonably long time, even for a moderately
>> powered PC. Perhaps something odd is happening here. Can you
>> describe in more detail what your data look like and what you are
>> doing with them?
>>
>> -Ken
>>
>> On 5/20/16, 11:55 AM, "ParaView on behalf of Michele Battistoni"
>> <paraview-bounces at paraview.org on behalf of
>> michele.battistoni at unipg.it> wrote:
>>
>>> Paraview is awesome for lots of functionalities, however I find
>>> it extremely slow in processing data with any filter type, or in
>>> changing timestep as soon as the model size is around one million
>>> cells or above. I have experience with a commercial tool which on
>>> the same model and pc is 100x faster. Let's say a second vs. a
>>> min!
>>>
>>> Is there any specific settings for ram of parallelization among
>>> cores?
>>>
>>> Thanks Michele

From cory.quammen at kitware.com  Tue Jun 14 08:27:16 2016
From: cory.quammen at kitware.com (Cory Quammen)
Date: Tue, 14 Jun 2016 14:27:16 +0200
Subject: [Paraview] display boundaries of 2D geometry
In-Reply-To: <F9562F3B302F29479A203FC5AF9E3E050F48E330@SERBE4I1.intra.erbe-med.de>
References: <F9562F3B302F29479A203FC5AF9E3E050F48E2CA@SERBE4I1.intra.erbe-med.de>
 <CAB5Fpx6cvUqnhYgNH295WEdN0T2FfQ9u=q4dfU4mP4jM4=xP-g@mail.gmail.com>
 <F9562F3B302F29479A203FC5AF9E3E050F48E330@SERBE4I1.intra.erbe-med.de>
Message-ID: <CAB5Fpx4n_urZ6=2b1tS-Sya=Crcqt5w-DfPWWffnoHzjkTdmLg@mail.gmail.com>

Hi Matthais,

People typically use multi-block data sets for this purpose. ParaView
has a multi-block inspector that enables you change the visibility of
the blocks in a data set. If you make each surface a block, then you
can show/hide each at will.

HTH,
Cory

On Tue, Jun 14, 2016 at 1:11 PM, Zenker, Dr. Matthias
<Matthias.Zenker at erbe-med.com> wrote:
> Hi Cory,
>
> this helped indeed, thank you.
> I  load the mesh.vtu file and apply the Threshold filter on the GeometryID, and display that together with my simulation results. That works fine.
> If I want to display several parts selectively, I can use several Thresholds, which is a bit clumsy.
> It would be nice to be able to get a list of all GeometryIDs, and to check those which I want displayed. Do you know if there is a way to do that? Or on a more general basis: are there other, more elegant ways to display a geometry in ParaView?
>
> Thanks again,
>
> Matthias
>
>
>> -----Urspr?ngliche Nachricht-----
>> Von: Cory Quammen [mailto:cory.quammen at kitware.com]
>> Gesendet: Montag, 13. Juni 2016 22:28
>> An: Zenker, Dr. Matthias
>> Cc: paraview at paraview.org
>> Betreff: Re: [Paraview] display boundaries of 2D geometry
>>
>> Matthias,
>>
>> I'm not sure I fully understand exactly what you are trying to do, but
>> I will try to make a suggestion anyway. If the edges have a cell data
>> array giving the ID, you should be able to use the Threshold filter to
>> extract the edges associated with a particular body ID. Just set the
>> threshold values to the ID you want to see.
>>
>> Hope that helps,
>> Cory
>>
>> On Mon, Jun 13, 2016 at 6:43 PM, Zenker, Dr. Matthias
>> <Matthias.Zenker at erbe-med.com> wrote:
>> > Hi,
>> >
>> >
>> >
>> > is there a way to display the boundaries (edges) of a 2D geometry? I have
>> > converted my mesh to vtu using Elmergrid, so I have the IDs of bodies
>> > (=surfaces in 2D) and boundaries (edges) in a vtu file. Can I just display
>> > the edges having the same ID? The extract edges filter does not help.
>> What
>> > else could I try?
>> >
>> >
>> >
>> > Thank you for a helpful hint,
>> >
>> >
>> >
>> > Matthias
>> >
>> > ________________________________
>> >
>> > Erbe Elektromedizin GmbH Firmensitz: 72072 Tuebingen
>> Geschaeftsfuehrer:
>> > Christian O. Erbe, Reiner Thede Registergericht: Stuttgart HRB 380137
>> >
>> >
>> > _______________________________________________
>> > 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.
> ________________________________
>
> Erbe Elektromedizin GmbH Firmensitz: 72072 Tuebingen Geschaeftsfuehrer: Christian O. Erbe, Reiner Thede Registergericht: Stuttgart HRB 380137
>



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

From samuelkey at bresnan.net  Tue Jun 14 09:03:36 2016
From: samuelkey at bresnan.net (Samuel Key)
Date: Tue, 14 Jun 2016 07:03:36 -0600
Subject: [Paraview] display boundaries of 2D geometry
In-Reply-To: <F9562F3B302F29479A203FC5AF9E3E050F48E330@SERBE4I1.intra.erbe-med.de>
References: <F9562F3B302F29479A203FC5AF9E3E050F48E2CA@SERBE4I1.intra.erbe-med.de>
 <CAB5Fpx6cvUqnhYgNH295WEdN0T2FfQ9u=q4dfU4mP4jM4=xP-g@mail.gmail.com>
 <F9562F3B302F29479A203FC5AF9E3E050F48E330@SERBE4I1.intra.erbe-med.de>
Message-ID: <26834b3c-9327-d92c-a6bd-6c9e7fb759bf@bresnan.net>

Matthias,

An approach that works well for me is to exploit the "Part" feature in 
either the VTK-formats or the EnSight format.

The "Part" construct in the VTK XML-format looks to me to have 
originated based on the need to combine for ParaView a set of results 
generated from individual CPU's. It can also be used for an assembly of 
parts. In my case, material domains are used to define the "Parts." The 
PV Extract Block filter displays the user's part names and can be used 
to display any combination of "Parts."

Again in my case, it is important to know that point-sets, and element 
edge-sets  and face-sets at time(0.0) are properly defined. At 
time(0.0), a mesh-by-material, point-sets, edge-sets, and face-sets (aka 
side-sets) are generated, all based on the "Part" construct, for the 
express purpose of visualizing these in ParaView before a simulation is run.

The key to doing this is to understand that each "Part" needs to be a 
complete, standalone, displayable graphics object.

Should you or your staff be interested in exploring this approach, a set 
of FORTRAN language routines can be provided.

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


On 6/14/2016 5:11 AM, Zenker, Dr. Matthias wrote:
> Hi Cory,
>
> this helped indeed, thank you.
> I  load the mesh.vtu file and apply the Threshold filter on the GeometryID, and display that together with my simulation results. That works fine.
> If I want to display several parts selectively, I can use several Thresholds, which is a bit clumsy.
> It would be nice to be able to get a list of all GeometryIDs, and to check those which I want displayed. Do you know if there is a way to do that? Or on a more general basis: are there other, more elegant ways to display a geometry in ParaView?
>
> Thanks again,
>
> Matthias
>
>
>> -----Urspr?ngliche Nachricht-----
>> Von: Cory Quammen [mailto:cory.quammen at kitware.com]
>> Gesendet: Montag, 13. Juni 2016 22:28
>> An: Zenker, Dr. Matthias
>> Cc: paraview at paraview.org
>> Betreff: Re: [Paraview] display boundaries of 2D geometry
>>
>> Matthias,
>>
>> I'm not sure I fully understand exactly what you are trying to do, but
>> I will try to make a suggestion anyway. If the edges have a cell data
>> array giving the ID, you should be able to use the Threshold filter to
>> extract the edges associated with a particular body ID. Just set the
>> threshold values to the ID you want to see.
>>
>> Hope that helps,
>> Cory
>>
>> On Mon, Jun 13, 2016 at 6:43 PM, Zenker, Dr. Matthias
>> <Matthias.Zenker at erbe-med.com> wrote:
>>> Hi,
>>>
>>>
>>>
>>> is there a way to display the boundaries (edges) of a 2D geometry? I have
>>> converted my mesh to vtu using Elmergrid, so I have the IDs of bodies
>>> (=surfaces in 2D) and boundaries (edges) in a vtu file. Can I just display
>>> the edges having the same ID? The extract edges filter does not help.
>> What
>>> else could I try?
>>>
>>>
>>>
>>> Thank you for a helpful hint,
>>>
>>>
>>>
>>> Matthias
>>>
>>> ________________________________
>>>
>>> Erbe Elektromedizin GmbH Firmensitz: 72072 Tuebingen
>> Geschaeftsfuehrer:
>>> Christian O. Erbe, Reiner Thede Registergericht: Stuttgart HRB 380137
>>>
>>>
>>> _______________________________________________
>>> 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.
> ________________________________
>
> Erbe Elektromedizin GmbH Firmensitz: 72072 Tuebingen Geschaeftsfuehrer: Christian O. Erbe, Reiner Thede Registergericht: Stuttgart HRB 380137
>
> _______________________________________________
> 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 Matthias.Zenker at erbe-med.com  Tue Jun 14 11:21:45 2016
From: Matthias.Zenker at erbe-med.com (Zenker, Dr. Matthias)
Date: Tue, 14 Jun 2016 15:21:45 +0000
Subject: [Paraview] display boundaries of 2D geometry
In-Reply-To: <CAB5Fpx4n_urZ6=2b1tS-Sya=Crcqt5w-DfPWWffnoHzjkTdmLg@mail.gmail.com>
References: <F9562F3B302F29479A203FC5AF9E3E050F48E2CA@SERBE4I1.intra.erbe-med.de>
 <CAB5Fpx6cvUqnhYgNH295WEdN0T2FfQ9u=q4dfU4mP4jM4=xP-g@mail.gmail.com>
 <F9562F3B302F29479A203FC5AF9E3E050F48E330@SERBE4I1.intra.erbe-med.de>
 <CAB5Fpx4n_urZ6=2b1tS-Sya=Crcqt5w-DfPWWffnoHzjkTdmLg@mail.gmail.com>
Message-ID: <F9562F3B302F29479A203FC5AF9E3E050F48E38E@SERBE4I1.intra.erbe-med.de>

Hi Cory,

thank you for the hint.
However, I don't know how to make a mesh generated by Salom? a multi-block dataset. Could you tell me more or give me a pointer on where I can find that out?

Thanks,

Matthias

> -----Urspr?ngliche Nachricht-----
> Von: Cory Quammen [mailto:cory.quammen at kitware.com]
> Gesendet: Dienstag, 14. Juni 2016 14:27
> An: Zenker, Dr. Matthias
> Cc: paraview at paraview.org
> Betreff: Re: [Paraview] display boundaries of 2D geometry
>
> Hi Matthais,
>
> People typically use multi-block data sets for this purpose. ParaView has a
> multi-block inspector that enables you change the visibility of the blocks in a
> data set. If you make each surface a block, then you can show/hide each at
> will.
>
> HTH,
> Cory
>
> On Tue, Jun 14, 2016 at 1:11 PM, Zenker, Dr. Matthias
> <Matthias.Zenker at erbe-med.com> wrote:
> > Hi Cory,
> >
> > this helped indeed, thank you.
> > I  load the mesh.vtu file and apply the Threshold filter on the GeometryID,
> and display that together with my simulation results. That works fine.
> > If I want to display several parts selectively, I can use several Thresholds,
> which is a bit clumsy.
> > It would be nice to be able to get a list of all GeometryIDs, and to check
> those which I want displayed. Do you know if there is a way to do that? Or on
> a more general basis: are there other, more elegant ways to display a
> geometry in ParaView?
> >
> > Thanks again,
> >
> > Matthias
> >
> >
> >> -----Urspr?ngliche Nachricht-----
> >> Von: Cory Quammen [mailto:cory.quammen at kitware.com]
> >> Gesendet: Montag, 13. Juni 2016 22:28
> >> An: Zenker, Dr. Matthias
> >> Cc: paraview at paraview.org
> >> Betreff: Re: [Paraview] display boundaries of 2D geometry
> >>
> >> Matthias,
> >>
> >> I'm not sure I fully understand exactly what you are trying to do,
> >> but I will try to make a suggestion anyway. If the edges have a cell
> >> data array giving the ID, you should be able to use the Threshold
> >> filter to extract the edges associated with a particular body ID.
> >> Just set the threshold values to the ID you want to see.
> >>
> >> Hope that helps,
> >> Cory
> >>
> >> On Mon, Jun 13, 2016 at 6:43 PM, Zenker, Dr. Matthias
> >> <Matthias.Zenker at erbe-med.com> wrote:
> >> > Hi,
> >> >
> >> >
> >> >
> >> > is there a way to display the boundaries (edges) of a 2D geometry?
> >> > I have converted my mesh to vtu using Elmergrid, so I have the IDs
> >> > of bodies (=surfaces in 2D) and boundaries (edges) in a vtu file.
> >> > Can I just display the edges having the same ID? The extract edges filter
> does not help.
> >> What
> >> > else could I try?
> >> >
> >> >
> >> >
> >> > Thank you for a helpful hint,
> >> >
> >> >
> >> >
> >> > Matthias
> >> >
> >> > ________________________________
> >> >
> >> > Erbe Elektromedizin GmbH Firmensitz: 72072 Tuebingen
> >> Geschaeftsfuehrer:
> >> > Christian O. Erbe, Reiner Thede Registergericht: Stuttgart HRB
> >> > 380137
> >> >
> >> >
> >> > _______________________________________________
> >> > 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.
> > ________________________________
> >
> > Erbe Elektromedizin GmbH Firmensitz: 72072 Tuebingen
> > Geschaeftsfuehrer: Christian O. Erbe, Reiner Thede Registergericht:
> > Stuttgart HRB 380137
> >
>
>
>
> --
> Cory Quammen
> R&D Engineer
> Kitware, Inc.
________________________________

Erbe Elektromedizin GmbH Firmensitz: 72072 Tuebingen Geschaeftsfuehrer: Christian O. Erbe, Reiner Thede Registergericht: Stuttgart HRB 380137


From cory.quammen at kitware.com  Tue Jun 14 11:35:10 2016
From: cory.quammen at kitware.com (Cory Quammen)
Date: Tue, 14 Jun 2016 17:35:10 +0200
Subject: [Paraview] display boundaries of 2D geometry
In-Reply-To: <F9562F3B302F29479A203FC5AF9E3E050F48E38E@SERBE4I1.intra.erbe-med.de>
References: <F9562F3B302F29479A203FC5AF9E3E050F48E2CA@SERBE4I1.intra.erbe-med.de>
 <CAB5Fpx6cvUqnhYgNH295WEdN0T2FfQ9u=q4dfU4mP4jM4=xP-g@mail.gmail.com>
 <F9562F3B302F29479A203FC5AF9E3E050F48E330@SERBE4I1.intra.erbe-med.de>
 <CAB5Fpx4n_urZ6=2b1tS-Sya=Crcqt5w-DfPWWffnoHzjkTdmLg@mail.gmail.com>
 <F9562F3B302F29479A203FC5AF9E3E050F48E38E@SERBE4I1.intra.erbe-med.de>
Message-ID: <CAB5Fpx5AzVWeoS7_HsTMESzd==MjUiy6ib6VqyOqm8h_ovjYdA@mail.gmail.com>

Matthias,

Alas, I don't know much about Salom?. If no one here replies, you
might have better luck on the Salom? forum:

http://www.salome-platform.org/forum

Best,
Cory

On Tue, Jun 14, 2016 at 5:21 PM, Zenker, Dr. Matthias
<Matthias.Zenker at erbe-med.com> wrote:
> Hi Cory,
>
> thank you for the hint.
> However, I don't know how to make a mesh generated by Salom? a multi-block dataset. Could you tell me more or give me a pointer on where I can find that out?
>
> Thanks,
>
> Matthias
>
>> -----Urspr?ngliche Nachricht-----
>> Von: Cory Quammen [mailto:cory.quammen at kitware.com]
>> Gesendet: Dienstag, 14. Juni 2016 14:27
>> An: Zenker, Dr. Matthias
>> Cc: paraview at paraview.org
>> Betreff: Re: [Paraview] display boundaries of 2D geometry
>>
>> Hi Matthais,
>>
>> People typically use multi-block data sets for this purpose. ParaView has a
>> multi-block inspector that enables you change the visibility of the blocks in a
>> data set. If you make each surface a block, then you can show/hide each at
>> will.
>>
>> HTH,
>> Cory
>>
>> On Tue, Jun 14, 2016 at 1:11 PM, Zenker, Dr. Matthias
>> <Matthias.Zenker at erbe-med.com> wrote:
>> > Hi Cory,
>> >
>> > this helped indeed, thank you.
>> > I  load the mesh.vtu file and apply the Threshold filter on the GeometryID,
>> and display that together with my simulation results. That works fine.
>> > If I want to display several parts selectively, I can use several Thresholds,
>> which is a bit clumsy.
>> > It would be nice to be able to get a list of all GeometryIDs, and to check
>> those which I want displayed. Do you know if there is a way to do that? Or on
>> a more general basis: are there other, more elegant ways to display a
>> geometry in ParaView?
>> >
>> > Thanks again,
>> >
>> > Matthias
>> >
>> >
>> >> -----Urspr?ngliche Nachricht-----
>> >> Von: Cory Quammen [mailto:cory.quammen at kitware.com]
>> >> Gesendet: Montag, 13. Juni 2016 22:28
>> >> An: Zenker, Dr. Matthias
>> >> Cc: paraview at paraview.org
>> >> Betreff: Re: [Paraview] display boundaries of 2D geometry
>> >>
>> >> Matthias,
>> >>
>> >> I'm not sure I fully understand exactly what you are trying to do,
>> >> but I will try to make a suggestion anyway. If the edges have a cell
>> >> data array giving the ID, you should be able to use the Threshold
>> >> filter to extract the edges associated with a particular body ID.
>> >> Just set the threshold values to the ID you want to see.
>> >>
>> >> Hope that helps,
>> >> Cory
>> >>
>> >> On Mon, Jun 13, 2016 at 6:43 PM, Zenker, Dr. Matthias
>> >> <Matthias.Zenker at erbe-med.com> wrote:
>> >> > Hi,
>> >> >
>> >> >
>> >> >
>> >> > is there a way to display the boundaries (edges) of a 2D geometry?
>> >> > I have converted my mesh to vtu using Elmergrid, so I have the IDs
>> >> > of bodies (=surfaces in 2D) and boundaries (edges) in a vtu file.
>> >> > Can I just display the edges having the same ID? The extract edges filter
>> does not help.
>> >> What
>> >> > else could I try?
>> >> >
>> >> >
>> >> >
>> >> > Thank you for a helpful hint,
>> >> >
>> >> >
>> >> >
>> >> > Matthias
>> >> >
>> >> > ________________________________
>> >> >
>> >> > Erbe Elektromedizin GmbH Firmensitz: 72072 Tuebingen
>> >> Geschaeftsfuehrer:
>> >> > Christian O. Erbe, Reiner Thede Registergericht: Stuttgart HRB
>> >> > 380137
>> >> >
>> >> >
>> >> > _______________________________________________
>> >> > 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.
>> > ________________________________
>> >
>> > Erbe Elektromedizin GmbH Firmensitz: 72072 Tuebingen
>> > Geschaeftsfuehrer: Christian O. Erbe, Reiner Thede Registergericht:
>> > Stuttgart HRB 380137
>> >
>>
>>
>>
>> --
>> Cory Quammen
>> R&D Engineer
>> Kitware, Inc.
> ________________________________
>
> Erbe Elektromedizin GmbH Firmensitz: 72072 Tuebingen Geschaeftsfuehrer: Christian O. Erbe, Reiner Thede Registergericht: Stuttgart HRB 380137
>



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

From cory.quammen at kitware.com  Tue Jun 14 11:42:21 2016
From: cory.quammen at kitware.com (Cory Quammen)
Date: Tue, 14 Jun 2016 17:42:21 +0200
Subject: [Paraview] [ParaView] How to add slice thickness ?
In-Reply-To: <CAJFKOL1aoshdzhM5Ucgqkt2wN+GNco8HnMzuJJZQ2mepdWCWRw@mail.gmail.com>
References: <CAJFKOL1aoshdzhM5Ucgqkt2wN+GNco8HnMzuJJZQ2mepdWCWRw@mail.gmail.com>
Message-ID: <CAB5Fpx4MyHsvOsMJG++oFP1=rx23YMY1sdUG_tpzQEjTL9gSxg@mail.gmail.com>

Chathuri,

I'm not really sure what you mean by adding slice thickness. Slices
are always infinitesimally thin planes in ParaView.

Do you mean setting the spacing between image slices? If so, you
should be able to do that with the Transform filter, which lets you
specify a different scale in X, Y, and Z. I am assuming your slices
are read in with spacing of 1 x 1 x 1 (no units specified). You should
be able to scale to whatever units you wish to use with your knowledge
of both the X and Y spacing in each slice and the Z spacing between
slices.

HTH,
Cory

On Sat, May 14, 2016 at 11:54 AM, Chathuri Gunasekera
<cgunases at gmail.com> wrote:
> Hi,
>
> I have lot of image slices which need to employ in generating a 3D model.
>
> Can someone kindly tell me, how to add the  slice thickness in ParaView?
>
> Thanks in advance.
> --
> 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 ben.boeckel at kitware.com  Tue Jun 14 13:19:04 2016
From: ben.boeckel at kitware.com (Ben Boeckel)
Date: Tue, 14 Jun 2016 13:19:04 -0400
Subject: [Paraview] ANN: ParaView 5.1.0-RC1 available for download
In-Reply-To: <CANO2j4P8KAThsr8Jr+ZYeC8XQt7XWcPvY5W+q=EDGUe9gpF6+g@mail.gmail.com>
References: <CADHSJjCTEFP3VOFm+k2vE-gxN8nojz5q4rDjKL9ZUhgDFeG9hw@mail.gmail.com>
 <96B43CB6-F195-489A-A24A-2305F5AD5C10@gmail.com>
 <c571d7c3-69b7-dcd8-4b5d-5379f90a46f6@mail.ru>
 <CADHSJjAcCR+zggqXUk75yfCi6Vd5dw+ncqt5SmYLNS2nKUcnbw@mail.gmail.com>
 <CADHSJjDrpBFvbiXTjvJDY0YFcUh_BPAoZYW9f=bJUt45t3bgxQ@mail.gmail.com>
 <9699c536-51d3-950f-b5a5-fcbce6811dce@mail.ru>
 <CANO2j4OWNiN2wdZ8Lw1-oQ97xURrrHtmhdd_p24cgm7ewJDovw@mail.gmail.com>
 <CANO2j4P8KAThsr8Jr+ZYeC8XQt7XWcPvY5W+q=EDGUe9gpF6+g@mail.gmail.com>
Message-ID: <20160614171904.GA26263@rotor>

On Mon, Jun 13, 2016 at 12:11:29 -0400, ??? wrote:
> It turned out that the operating system on my machine does not have the
> library: GLIBCXX_3.4.15. And the linux system on my machine does not allow
> me upgrading the library to GLIBCXX_3.4.15.
> Is there any other way that I can still use the new version of paraview
> without GLIBCXX_3.4.15? I only want to use the SPH interpolation feature of
> the new paraview.

This is a "symbol version". It basically means that your libstdc++ is
too old for the build we created. What Linux distribution and version
are you using?

--Ben

From hitcaozx at gmail.com  Tue Jun 14 13:28:29 2016
From: hitcaozx at gmail.com (=?UTF-8?B?5pu55pm66YCJ?=)
Date: Tue, 14 Jun 2016 13:28:29 -0400
Subject: [Paraview] ANN: ParaView 5.1.0-RC1 available for download
In-Reply-To: <20160614171904.GA26263@rotor>
References: <CADHSJjCTEFP3VOFm+k2vE-gxN8nojz5q4rDjKL9ZUhgDFeG9hw@mail.gmail.com>
 <96B43CB6-F195-489A-A24A-2305F5AD5C10@gmail.com>
 <c571d7c3-69b7-dcd8-4b5d-5379f90a46f6@mail.ru>
 <CADHSJjAcCR+zggqXUk75yfCi6Vd5dw+ncqt5SmYLNS2nKUcnbw@mail.gmail.com>
 <CADHSJjDrpBFvbiXTjvJDY0YFcUh_BPAoZYW9f=bJUt45t3bgxQ@mail.gmail.com>
 <9699c536-51d3-950f-b5a5-fcbce6811dce@mail.ru>
 <CANO2j4OWNiN2wdZ8Lw1-oQ97xURrrHtmhdd_p24cgm7ewJDovw@mail.gmail.com>
 <CANO2j4P8KAThsr8Jr+ZYeC8XQt7XWcPvY5W+q=EDGUe9gpF6+g@mail.gmail.com>
 <20160614171904.GA26263@rotor>
Message-ID: <CANO2j4OsnF14jKk_n-miTp1tm8N3UVJ5TC5nYTVyoo3Cn4b+Yg@mail.gmail.com>

 Centos 6.7, 6.8 OS

2016-06-14 13:19 GMT-04:00 Ben Boeckel <ben.boeckel at kitware.com>:

> On Mon, Jun 13, 2016 at 12:11:29 -0400, ??? wrote:
> > It turned out that the operating system on my machine does not have the
> > library: GLIBCXX_3.4.15. And the linux system on my machine does not
> allow
> > me upgrading the library to GLIBCXX_3.4.15.
> > Is there any other way that I can still use the new version of paraview
> > without GLIBCXX_3.4.15? I only want to use the SPH interpolation feature
> of
> > the new paraview.
>
> This is a "symbol version". It basically means that your libstdc++ is
> too old for the build we created. What Linux distribution and version
> are you using?
>
> --Ben
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160614/4d49d344/attachment.html>

From cgunases at gmail.com  Tue Jun 14 13:34:24 2016
From: cgunases at gmail.com (Chathu Gunasekera)
Date: Tue, 14 Jun 2016 23:04:24 +0530
Subject: [Paraview] [ParaView] How to add slice thickness ?
In-Reply-To: <CAB5Fpx4MyHsvOsMJG++oFP1=rx23YMY1sdUG_tpzQEjTL9gSxg@mail.gmail.com>
References: <CAJFKOL1aoshdzhM5Ucgqkt2wN+GNco8HnMzuJJZQ2mepdWCWRw@mail.gmail.com>
 <CAB5Fpx4MyHsvOsMJG++oFP1=rx23YMY1sdUG_tpzQEjTL9gSxg@mail.gmail.com>
Message-ID: <CAJFKOL3fgBuTWxREnhH7Ojj-A=pK0O=ddFcREboJR1SW+vHy1Q@mail.gmail.com>

Thank you so much for your response Cory.
Well, you're correct, i am referring to the spacing.
When i use the Transform Filter (units in mm) and apply it to the model,
the Paraview crashes (Paraview stops working and close the program by
itself). Do you know what could be the error?
What am i doing wrong here? I am clueless..
Your suggestions are welcome.
Thank you .



-- 
Warm regards,
Chathuri Gunasekera.


On Tue, Jun 14, 2016 at 9:12 PM, Cory Quammen <cory.quammen at kitware.com>
wrote:

> Chathuri,
>
> I'm not really sure what you mean by adding slice thickness. Slices
> are always infinitesimally thin planes in ParaView.
>
> Do you mean setting the spacing between image slices? If so, you
> should be able to do that with the Transform filter, which lets you
> specify a different scale in X, Y, and Z. I am assuming your slices
> are read in with spacing of 1 x 1 x 1 (no units specified). You should
> be able to scale to whatever units you wish to use with your knowledge
> of both the X and Y spacing in each slice and the Z spacing between
> slices.
>
> HTH,
> Cory
>
> On Sat, May 14, 2016 at 11:54 AM, Chathuri Gunasekera
> <cgunases at gmail.com> wrote:
> > Hi,
> >
> > I have lot of image slices which need to employ in generating a 3D model.
> >
> > Can someone kindly tell me, how to add the  slice thickness in ParaView?
> >
> > Thanks in advance.
> > --
> > 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.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160614/58b074c2/attachment.html>

From utkarsh.ayachit at kitware.com  Tue Jun 14 15:21:53 2016
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Tue, 14 Jun 2016 15:21:53 -0400
Subject: [Paraview] Forcing update on view
In-Reply-To: <5DF928D22AC3AC4B964903E98F2E54515B59F4D9@sooty3.win.ara>
References: <5DF928D22AC3AC4B964903E98F2E54515B59F2DA@sooty3.win.ara>
 <5DF928D22AC3AC4B964903E98F2E54515B59F4D9@sooty3.win.ara>
Message-ID: <CADHSJjA-x0sjXTc-o4nBaU0JvR61gu8Crxwo4jN50HgNnAYTWA@mail.gmail.com>

I am not sure I follow what you're doing, but here are a few things to note.

1. vtkSMProxy::UpdateVTKObjects() is called to push changes done to a
property. Thus, only needs to be called on the proxy whose properties
you're changing. Thus, if you are chaning "CompositeDataSetIIndex"
property on the chartRepresentationProxy, you only need to call
UpdateVTKObjects() on it.
2. pqView::forceRender() cancels pending renders, so you don't have to
do that explicitly.
3. When CompositeDataSetIndex property is changed and successfully
pushed, vtkChartRepresentation::AddCompositeDataSetIndex() should be
called. Try putting a breakpoint there to ensure it's getting called
when you're expecting it to happen.

Hope that helps,
Utkarsh

On Tue, Jun 14, 2016 at 5:35 AM, Andrzej Peczak <apeczak at ara.co.uk> wrote:
> I missed the question regarding the problem I describe. Is there a way to programmatically display the content of CompositeDataSetIndex property depending on status of the checkbox widgets I change through vector properties?
>
> Andrzej
>
> Hi,
>
> I have a snippet code which I wrote to allow me to save multiple plot images to files. I do it by changing property checkboxes of Composite Data Set Index property. I can change their status programmatically but the view is not being updated. When I change them manually in the UI the view knows about their status change and plots only the content I select. I tried to force the update with UpdateVTkObjects() of available properties plus explicitly calling render()/forceRender() of the view but with no success.  Every file I create has multiple plot curves in it instead of one.
>
> Andrzej
>
>         pqDataRepresentation *repr = source->getRepresentation( view );
>         auto chartRepresentationProxy = repr->getProxy();
>
>         vtkSMProperty *property = chartRepresentationProxy->GetProperty( "CompositeDataSetIndex" );
>         if ( property ) {
>
>                 auto VectorProperty = vtkSMIntVectorProperty::SafeDownCast( property );
>                 if ( VectorProperty ) {
>
>                         const auto numElements = VectorProperty->GetNumberOfElements();
>                         int elements[ numElements ];
>                         std::copy( VectorProperty->GetElements(), VectorProperty->GetElements() + numElements, elements );
>                         for ( auto i = 0 ; i != numElements ; ++i ) {
>                                 VectorProperty->SetElement( elements[ i ], 0 );
>                         }
>
>                         for ( auto i = 0 ; i != numElements ; ++i ) {
>                                 VectorProperty->SetElement( elements[ i ], 1 );
>
>                                 source->getSourceProxy()->UpdateVTKObjects();
>                                 view->getViewProxy()->UpdateVTKObjects();
>                                 view->getViewProxy()->Update();
>                                 repr = source->getRepresentation( view );
>                                 repr->getProxy()->UpdateVTKObjects();
>                                 repr->renderView( true );
>                                 property->GetParent()->UpdateVTKObjects();
>                                 view->cancelPendingRenders();
>                                 view->forceRender();
>
>                                 std::stringstream ssFileName;
>                                 std::string ext , newName2;
>                                 std::string::size_type dot_pos = newName.rfind( '.' );
>                                 if ( dot_pos != std::string::npos ) {
>                                         ext = newName.substr( dot_pos );
>                                         newName2 = newName.substr( 0, dot_pos );
>                                 }
>                                 ssFileName << newName2 << "_" << i + 1 << ext;
>                                 view->writeImage( ssFileName.str().c_str(), size, quality );
>                                 VectorProperty->SetElement( elements[ i ], 0 );
>                         }
>
>                         VectorProperty->SetElements( elements );
>                 }
>         }
>
> **********************************************************************
> Please consider the environment. Only print this email if absolutely necessary.
>
> This email contains information that is private and confidential and is intended only for the addressee.
> If you are not the intended recipient please delete it and notify us immediately by e-mailing the sender.
> Note: All email sent to or from this address may be accessed by someone other than the recipient, for
> system management and security reasons.
> Aircraft Research Association Ltd.  Registered in England, Registration No 503668 Registered Office:
> Manton Lane, Bedford MK41 7PF England VAT No GB 196351245
>
> **********************************************************************
> _______________________________________________
> 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  Tue Jun 14 15:36:27 2016
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Tue, 14 Jun 2016 15:36:27 -0400
Subject: [Paraview] pvpython and vtk classes and functions to create
	objects
In-Reply-To: <CAMGPr0Ua9hfxqcGsdqZ=d2+4kX=a1bthb0_bRQNtcR0T_huxNQ@mail.gmail.com>
References: <CAMGPr0Ua9hfxqcGsdqZ=d2+4kX=a1bthb0_bRQNtcR0T_huxNQ@mail.gmail.com>
Message-ID: <CADHSJjBroSivmPSn6wf17r+ta44NE823Y7T1iO46v399_YRBsQ@mail.gmail.com>

Yes, you just need to import the appropriate module in python.
e.g.

 @exportRpc("my.test.rpc")
    def myTestRPCFunction(self):

        from paraview.vtk.vtkIOImage import vtkImageReader2Factory
        reader = vtkImageReader2Factory.CreateImageReader(filename)

        from paraview.vtk.vtkFiltersTexture import vtkTextureMapToPlane
        texturePlane.SetInputConnection(reader.GetOutputPort())

        ....

        return 0

On Sun, Jun 5, 2016 at 7:45 PM, Rodrigo Pelorosso
<rodrigo.pelorosso at gmail.com> wrote:
> Hi!
>
> Is there a way to use python VTK functions and classes in paraview?  I'm
> using paraview through paraviewweb and I've created an RPC that I can call
> from the client to run paraview python code:
>
> @exportRpc("my.test.rpc")
>     def myTestRPCFunction(self):
>         return 0
>
> I would like to create, inside this RPC, a plane with a texture applied.
> Searching the mailing list I found this thread,
>
> https://cmake.org/pipermail/paraview/2011-April/020848.html
>
> were someone's trying to accomplish this from a reader written in C++, but I
> would really like to do something like that inside my RPC, is that possible?
>
> Thank you!
> Rodrigo
>
>
> _______________________________________________
> 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 vperry at fandm.edu  Tue Jun 14 16:26:45 2016
From: vperry at fandm.edu (Vincent Perry)
Date: Tue, 14 Jun 2016 16:26:45 -0400
Subject: [Paraview] (no subject)
Message-ID: <CAGZC-_fmxm-L9cMyvRHTFKGZqVuAdACK0UD=EQZW8fWkw5QvVw@mail.gmail.com>

Hello,

When running ParaViewWeb on a Mac, a pvpython window entitled
'Visualization Toolkit - Cocoa #1' pops up on start-up. This window
displays the exact same output as the Visualizer in the browser, but there
is no way to interact with it directly.  If I quit out of this window, the
entire application fails. I am wondering what launches this window, and why
is it necessary? Is there any way to launch ParaViewWeb without having this
extra window pop up?

Thanks,
Vince
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160614/a60edf21/attachment.html>

From shawn.waldon at kitware.com  Tue Jun 14 17:13:44 2016
From: shawn.waldon at kitware.com (Shawn Waldon)
Date: Tue, 14 Jun 2016 17:13:44 -0400
Subject: [Paraview] (no subject)
In-Reply-To: <CAGZC-_fmxm-L9cMyvRHTFKGZqVuAdACK0UD=EQZW8fWkw5QvVw@mail.gmail.com>
References: <CAGZC-_fmxm-L9cMyvRHTFKGZqVuAdACK0UD=EQZW8fWkw5QvVw@mail.gmail.com>
Message-ID: <CALSpCT2jknq5eR1Rs+qiBm-bTFnvbQKtz9x4Vqgj4P+xXaf2mA@mail.gmail.com>

Hi Vince,

This is expected.  Essentially ParaViewWeb allows you to remotely view the
ParaView output with your browser.  If you launched the Visualizer without
pointing a browser at it and then went to another computer and pointed a
browser at the first computer, you would see the ParaViewWeb output.  The
window would still pop up on the computer running ParaViewWeb.  Essentially
the problem is that ParaView needs an OpenGL context to do its rendering
and on most operating systems this requires a window.  So it creates a
window to get the OpenGL context and uses onscreen OpenGL.

You can change it to use offscreen rendering by finding where it creates
its render view and setting view.UseOffscreenRendering = 1.  But you still
get a window that pops up (it is just a blank window now).  I'll let you
know if I figure out how to get rid of the window altogether.

Shawn

On Tue, Jun 14, 2016 at 4:26 PM, Vincent Perry <vperry at fandm.edu> wrote:

> Hello,
>
> When running ParaViewWeb on a Mac, a pvpython window entitled
> 'Visualization Toolkit - Cocoa #1' pops up on start-up. This window
> displays the exact same output as the Visualizer in the browser, but there
> is no way to interact with it directly.  If I quit out of this window, the
> entire application fails. I am wondering what launches this window, and why
> is it necessary? Is there any way to launch ParaViewWeb without having this
> extra window pop up?
>
> Thanks,
> Vince
>
> _______________________________________________
> 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/20160614/c2674863/attachment.html>

From cory.quammen at kitware.com  Tue Jun 14 17:55:16 2016
From: cory.quammen at kitware.com (Cory Quammen)
Date: Tue, 14 Jun 2016 23:55:16 +0200
Subject: [Paraview] [ParaView] How to add slice thickness ?
In-Reply-To: <CAJFKOL3fgBuTWxREnhH7Ojj-A=pK0O=ddFcREboJR1SW+vHy1Q@mail.gmail.com>
References: <CAJFKOL1aoshdzhM5Ucgqkt2wN+GNco8HnMzuJJZQ2mepdWCWRw@mail.gmail.com>
 <CAB5Fpx4MyHsvOsMJG++oFP1=rx23YMY1sdUG_tpzQEjTL9gSxg@mail.gmail.com>
 <CAJFKOL3fgBuTWxREnhH7Ojj-A=pK0O=ddFcREboJR1SW+vHy1Q@mail.gmail.com>
Message-ID: <CAB5Fpx6A=Py+dJvwbdwj4TM6-x8pgjDDUYRWTzjepTuCwP7wMg@mail.gmail.com>

I suspect you are running out of memory with the Transform Filter.

Another approach would be to use a Programmable Filter and just change
the spacing information of the image data. Try this Python in the
Script property of the Programmable Filter:

input = self.GetInput()
output = self.GetOutput()
output.ShallowCopy(input)
output.SetSpacing(xSpacing, ySpacing, zSpacing)

That should do the trick.

HTH,
Cory


On Tue, Jun 14, 2016 at 7:34 PM, Chathu Gunasekera <cgunases at gmail.com> wrote:
> Thank you so much for your response Cory.
> Well, you're correct, i am referring to the spacing.
> When i use the Transform Filter (units in mm) and apply it to the model, the
> Paraview crashes (Paraview stops working and close the program by itself).
> Do you know what could be the error?
> What am i doing wrong here? I am clueless..
> Your suggestions are welcome.
> Thank you .
>
>
>
> --
> Warm regards,
> Chathuri Gunasekera.
>
>
> On Tue, Jun 14, 2016 at 9:12 PM, Cory Quammen <cory.quammen at kitware.com>
> wrote:
>>
>> Chathuri,
>>
>> I'm not really sure what you mean by adding slice thickness. Slices
>> are always infinitesimally thin planes in ParaView.
>>
>> Do you mean setting the spacing between image slices? If so, you
>> should be able to do that with the Transform filter, which lets you
>> specify a different scale in X, Y, and Z. I am assuming your slices
>> are read in with spacing of 1 x 1 x 1 (no units specified). You should
>> be able to scale to whatever units you wish to use with your knowledge
>> of both the X and Y spacing in each slice and the Z spacing between
>> slices.
>>
>> HTH,
>> Cory
>>
>> On Sat, May 14, 2016 at 11:54 AM, Chathuri Gunasekera
>> <cgunases at gmail.com> wrote:
>> > Hi,
>> >
>> > I have lot of image slices which need to employ in generating a 3D
>> > model.
>> >
>> > Can someone kindly tell me, how to add the  slice thickness in ParaView?
>> >
>> > Thanks in advance.
>> > --
>> > 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.
>
>
>
>
>



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

From cgunases at gmail.com  Tue Jun 14 22:13:12 2016
From: cgunases at gmail.com (Chathu Gunasekera)
Date: Wed, 15 Jun 2016 07:43:12 +0530
Subject: [Paraview] [ParaView] How to add slice thickness ?
In-Reply-To: <CAB5Fpx6A=Py+dJvwbdwj4TM6-x8pgjDDUYRWTzjepTuCwP7wMg@mail.gmail.com>
References: <CAJFKOL1aoshdzhM5Ucgqkt2wN+GNco8HnMzuJJZQ2mepdWCWRw@mail.gmail.com>
 <CAB5Fpx4MyHsvOsMJG++oFP1=rx23YMY1sdUG_tpzQEjTL9gSxg@mail.gmail.com>
 <CAJFKOL3fgBuTWxREnhH7Ojj-A=pK0O=ddFcREboJR1SW+vHy1Q@mail.gmail.com>
 <CAB5Fpx6A=Py+dJvwbdwj4TM6-x8pgjDDUYRWTzjepTuCwP7wMg@mail.gmail.com>
Message-ID: <CAJFKOL0PKJe06vAAaqVVQZQ0gdtTASecXmmN2Kxqq33c=uUqzw@mail.gmail.com>

Hi Cory,

Thank you so much for your response. Really appreciate it.

Well, i used the Programmable Filter and gave the spacing in mm.
(i am suppose to get a 3D model), unfortunately i am getting a straight
line (pls see the attachment).

Earlier i was using the Calculator filter and i only could see slices.
My intention is to obtain a model with one smooth surface  (if there is an
approach to smooth the transitions of the slices that would do my job
:)....)

Kindly give me a hint.


-- 
Warm regards,
Chathuri Gunasekera.



On Wed, Jun 15, 2016 at 3:25 AM, Cory Quammen <cory.quammen at kitware.com>
wrote:

> I suspect you are running out of memory with the Transform Filter.
>
> Another approach would be to use a Programmable Filter and just change
> the spacing information of the image data. Try this Python in the
> Script property of the Programmable Filter:
>
> input = self.GetInput()
> output = self.GetOutput()
> output.ShallowCopy(input)
> output.SetSpacing(xSpacing, ySpacing, zSpacing)
>
> That should do the trick.
>
> HTH,
> Cory
>
>
> On Tue, Jun 14, 2016 at 7:34 PM, Chathu Gunasekera <cgunases at gmail.com>
> wrote:
> > Thank you so much for your response Cory.
> > Well, you're correct, i am referring to the spacing.
> > When i use the Transform Filter (units in mm) and apply it to the model,
> the
> > Paraview crashes (Paraview stops working and close the program by
> itself).
> > Do you know what could be the error?
> > What am i doing wrong here? I am clueless..
> > Your suggestions are welcome.
> > Thank you .
> >
> >
> >
> > --
> > Warm regards,
> > Chathuri Gunasekera.
> >
> >
> > On Tue, Jun 14, 2016 at 9:12 PM, Cory Quammen <cory.quammen at kitware.com>
> > wrote:
> >>
> >> Chathuri,
> >>
> >> I'm not really sure what you mean by adding slice thickness. Slices
> >> are always infinitesimally thin planes in ParaView.
> >>
> >> Do you mean setting the spacing between image slices? If so, you
> >> should be able to do that with the Transform filter, which lets you
> >> specify a different scale in X, Y, and Z. I am assuming your slices
> >> are read in with spacing of 1 x 1 x 1 (no units specified). You should
> >> be able to scale to whatever units you wish to use with your knowledge
> >> of both the X and Y spacing in each slice and the Z spacing between
> >> slices.
> >>
> >> HTH,
> >> Cory
> >>
> >> On Sat, May 14, 2016 at 11:54 AM, Chathuri Gunasekera
> >> <cgunases at gmail.com> wrote:
> >> > Hi,
> >> >
> >> > I have lot of image slices which need to employ in generating a 3D
> >> > model.
> >> >
> >> > Can someone kindly tell me, how to add the  slice thickness in
> ParaView?
> >> >
> >> > Thanks in advance.
> >> > --
> >> > 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.
> >
> >
> >
> >
> >
>
>
>
> --
> Cory Quammen
> R&D Engineer
> Kitware, Inc.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160615/5b8e2bf0/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: programmable_filter_output.JPG
Type: image/jpeg
Size: 11547 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160615/5b8e2bf0/attachment.jpe>

From svenkramer40 at gmail.com  Wed Jun 15 01:34:37 2016
From: svenkramer40 at gmail.com (Sven Kramer)
Date: Wed, 15 Jun 2016 07:34:37 +0200
Subject: [Paraview] vtkSMCollaborationManager::FollowUser(id) doesn't
 update view
In-Reply-To: <CAAUk9C5e8N=n-59yqbh3_=8mo_Oe68Xwbfm-Vq_Fy_3RBWMQdg@mail.gmail.com>
References: <CAAUk9C4oh6fOkvh_yfaaXD4x6yoXe+--YiWfHL62oBmg-k3UQw@mail.gmail.com>
 <CADHSJjCLJ4=AfAFxPsmYWw0wn8WuKjDS5xeh8SUwJPqvydjRtg@mail.gmail.com>
 <CAAUk9C5WxrVg2YiFvfLy=mkc5gAU36JA2rxCFNO0HnOKGEqpyw@mail.gmail.com>
 <CADHSJjB9NQSdGShv1ThyWSpznOa1MRAKz-hagm6vve=k39BE4A@mail.gmail.com>
 <CAAUk9C7xotQgBGb7XtB41WSO-TY0cow8veu=VjvU23CbaLDnLA@mail.gmail.com>
 <CADHSJjB=u7ZzsTQ5902yjiDv+ie_Bpkvn9byZ5s44p-Rg9yX2w@mail.gmail.com>
 <CAAUk9C5e8N=n-59yqbh3_=8mo_Oe68Xwbfm-Vq_Fy_3RBWMQdg@mail.gmail.com>
Message-ID: <CAJZHu4RXiQjpG9cVStA6nQ_c1dye--J87g6QLTGxjLBRWx-Ssw@mail.gmail.com>

Yes, all these timer loops in paraview are annoying. There is no platform
independent solution for registering callbacks on sockets, but for each
supported OS a clean solution exists, which you could implement. So, it is
doable, but requires more effort than what is usually put into paraview.
Additionally you wouldn't probably want a callback after each received
byte, but rather after each complete message. This is not possible in a
generic way with the present message construction.

You seem to be stuck with similar problems as I was. You may want to
consider Visit as an alternative. Visit has an active user and developer
community so that there are more than two people on the mailing lists who
can answer questions like yours. Most of Visit has evolved over the last
few years rather than the "don't touch if not necessary" long history of
paraview, so that it has a much more modern design. These are some of the
reasons why my supervisor convinced me to favour Visit even after I was
half way through my project.

2016-06-10 18:58 GMT+02:00 Peter Debuchev <peterdebuchev at gmail.com>:

> Ok, that doesn't sound as bad as I expected. But still, is it necessary to
> "poll" the socket, checking its "select" method?
> I am not familiar with the details of socket communication, but I expect
> it should be possible that the socket invokes some callback when a message
> arrives? Or does some of the VTK design contradict such socket callbacks?
>
> I found that it is always problematic performance-wise if more than a few
> timers are running on one cpu.
>
> Peter
>
> 2016-06-10 15:17 GMT+02:00 Utkarsh Ayachit <utkarsh.ayachit at kitware.com>:
>
>> ProcessEvents() doesn't poll the server. It only "select"s on the
>> socket to see if the server sent any new messages to the client.
>>
>> > One more question out of curiosity: isn't it quite ineffient, if clients
>> > continuously invoke vtkNetworkAccessManager::ProcessEvents?()? For
>> smooth
>> > interaction this has to happen at least 10 times per second, which
>> causes a
>> > lot of network traffic by polling the server again and again,
>> especially if
>> > more than one client connects to the same server.
>> > Isn't it possible to react on incoming server events by registering a
>> > callback that does the same server event processing only when a new
>> event
>> > has occurred? I mean, all of VTK and ParaView is event based, why not
>> the
>> > server message processing?
>> >
>> > Peter
>> >
>> > 2016-06-09 18:29 GMT+02:00 Utkarsh Ayachit <utkarsh.ayachit at kitware.com
>> >:
>> >>
>> >> Here's the fix:
>> >>
>> >> diff --git a/main.cxx b/main.cxx
>> >> index dd47991..0f679ba 100644
>> >> --- a/main.cxx
>> >> +++ b/main.cxx
>> >> @@ -65,7 +65,7 @@ int main(int argc, char* argv[]){
>> >>    vtkSMSessionProxyManager* pxm = session->GetSessionProxyManager();
>> >>
>> >>    //Collaboration:
>> >> -  vtkSMCollaborationManager
>> >> *collaboration=vtkSMCollaborationManager::New();
>> >> +  vtkSMCollaborationManager *collaboration=
>> >> session->GetCollaborationManager();
>> >>    collaboration->SetSession(session);
>> >>    collaboration->UpdateUserInformations();
>> >
>> >
>>
>
>
> _______________________________________________
> 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/20160615/44a36a89/attachment.html>

From cory.quammen at kitware.com  Wed Jun 15 03:07:52 2016
From: cory.quammen at kitware.com (Cory Quammen)
Date: Wed, 15 Jun 2016 09:07:52 +0200
Subject: [Paraview] [ParaView] How to add slice thickness ?
In-Reply-To: <CAJFKOL0PKJe06vAAaqVVQZQ0gdtTASecXmmN2Kxqq33c=uUqzw@mail.gmail.com>
References: <CAJFKOL1aoshdzhM5Ucgqkt2wN+GNco8HnMzuJJZQ2mepdWCWRw@mail.gmail.com>
 <CAB5Fpx4MyHsvOsMJG++oFP1=rx23YMY1sdUG_tpzQEjTL9gSxg@mail.gmail.com>
 <CAJFKOL3fgBuTWxREnhH7Ojj-A=pK0O=ddFcREboJR1SW+vHy1Q@mail.gmail.com>
 <CAB5Fpx6A=Py+dJvwbdwj4TM6-x8pgjDDUYRWTzjepTuCwP7wMg@mail.gmail.com>
 <CAJFKOL0PKJe06vAAaqVVQZQ0gdtTASecXmmN2Kxqq33c=uUqzw@mail.gmail.com>
Message-ID: <CAB5Fpx6k6gm+3n9j+pHz0DKDE9s0ML6Jij+nFg_x0rv3dJ8V-g@mail.gmail.com>

Chaturi,

I'm still not clear on what your input is. Are you loading a series of
2D images? Is that working? What kind of data set do you get after
loading (look under the Information tab under Type:)? Do you see just
one slice when the data is loaded or an outline of a 3D box?

Please provide step-by-step what you are doing in ParaView up to the
point you want to specify the spacing between slices. Links to
pictures of what you are seeing are often helpful as well.

Thanks,
Cory

On Wed, Jun 15, 2016 at 4:13 AM, Chathu Gunasekera <cgunases at gmail.com> wrote:
> Hi Cory,
>
> Thank you so much for your response. Really appreciate it.
>
> Well, i used the Programmable Filter and gave the spacing in mm.
> (i am suppose to get a 3D model), unfortunately i am getting a straight line
> (pls see the attachment).
>
> Earlier i was using the Calculator filter and i only could see slices.
> My intention is to obtain a model with one smooth surface  (if there is an
> approach to smooth the transitions of the slices that would do my job
> :)....)
>
> Kindly give me a hint.
>
>
> --
> Warm regards,
> Chathuri Gunasekera.
>
>
>
> On Wed, Jun 15, 2016 at 3:25 AM, Cory Quammen <cory.quammen at kitware.com>
> wrote:
>>
>> I suspect you are running out of memory with the Transform Filter.
>>
>> Another approach would be to use a Programmable Filter and just change
>> the spacing information of the image data. Try this Python in the
>> Script property of the Programmable Filter:
>>
>> input = self.GetInput()
>> output = self.GetOutput()
>> output.ShallowCopy(input)
>> output.SetSpacing(xSpacing, ySpacing, zSpacing)
>>
>> That should do the trick.
>>
>> HTH,
>> Cory
>>
>>
>> On Tue, Jun 14, 2016 at 7:34 PM, Chathu Gunasekera <cgunases at gmail.com>
>> wrote:
>> > Thank you so much for your response Cory.
>> > Well, you're correct, i am referring to the spacing.
>> > When i use the Transform Filter (units in mm) and apply it to the model,
>> > the
>> > Paraview crashes (Paraview stops working and close the program by
>> > itself).
>> > Do you know what could be the error?
>> > What am i doing wrong here? I am clueless..
>> > Your suggestions are welcome.
>> > Thank you .
>> >
>> >
>> >
>> > --
>> > Warm regards,
>> > Chathuri Gunasekera.
>> >
>> >
>> > On Tue, Jun 14, 2016 at 9:12 PM, Cory Quammen <cory.quammen at kitware.com>
>> > wrote:
>> >>
>> >> Chathuri,
>> >>
>> >> I'm not really sure what you mean by adding slice thickness. Slices
>> >> are always infinitesimally thin planes in ParaView.
>> >>
>> >> Do you mean setting the spacing between image slices? If so, you
>> >> should be able to do that with the Transform filter, which lets you
>> >> specify a different scale in X, Y, and Z. I am assuming your slices
>> >> are read in with spacing of 1 x 1 x 1 (no units specified). You should
>> >> be able to scale to whatever units you wish to use with your knowledge
>> >> of both the X and Y spacing in each slice and the Z spacing between
>> >> slices.
>> >>
>> >> HTH,
>> >> Cory
>> >>
>> >> On Sat, May 14, 2016 at 11:54 AM, Chathuri Gunasekera
>> >> <cgunases at gmail.com> wrote:
>> >> > Hi,
>> >> >
>> >> > I have lot of image slices which need to employ in generating a 3D
>> >> > model.
>> >> >
>> >> > Can someone kindly tell me, how to add the  slice thickness in
>> >> > ParaView?
>> >> >
>> >> > Thanks in advance.
>> >> > --
>> >> > 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.
>> >
>> >
>> >
>> >
>> >
>>
>>
>>
>> --
>> Cory Quammen
>> R&D Engineer
>> Kitware, Inc.
>
>
>
>



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

From svenkramer40 at gmail.com  Wed Jun 15 06:54:28 2016
From: svenkramer40 at gmail.com (Sven Kramer)
Date: Wed, 15 Jun 2016 12:54:28 +0200
Subject: [Paraview] Comparison of Visit and ParaView development
Message-ID: <CAJZHu4RT7dek6wuyEWDDOL85m4kk58gnP8mgdM2-W2knZs7NgQ@mail.gmail.com>

Dear ParaView programmers,
I would like to have some opinions on the suitability of either ParaView or
Visit for large scalable visualization applications. When I had the first
contact to visualization more than 5 years ago, Visit was not quite
scalable and ParaView seemed the only open source alternative.
Now I am trying to get into some serious developments, and although most
papers in the field still cite ParaView as their development framework,
there seems to be no active developers community except for two or three
kitware employees. Questions on this list are at the most basic level, and
nobody seems to be able to answer, who isn't working for kitware.
My impression is that ParaView has grown so complicated over the years that
it is no longer usable as a framework for parallel visualization
development. Only the ParaView application itself is still frequently used.
On the other hand, Visit seems to have overtaken ParaView in all aspects.
Most important is the high quality documentation and very active community,
scalability is now as good as ParaView, and collaborative web visualization
is coming rapidly.

What is your opinion? Are there any points, where ParaView is clearly
advantageous over Visit? Or is it used by most people only out of
convenience, because they have always worked with ParaView?
Given the horribly out of date books on ParaView and parallel VTK
development, web documentation mixing three major versions without stating
which version is referred to, and the dead development discussions I don't
see any possibility of learning ParaView programming today. Which material
do you use for tutorials and documentation?

Thank you
Sven
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160615/3a5d11ee/attachment.html>

From utkarsh.ayachit at kitware.com  Wed Jun 15 08:16:26 2016
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Wed, 15 Jun 2016 08:16:26 -0400
Subject: [Paraview] vtkSMCollaborationManager::FollowUser(id) doesn't
 update view
In-Reply-To: <CAJZHu4RXiQjpG9cVStA6nQ_c1dye--J87g6QLTGxjLBRWx-Ssw@mail.gmail.com>
References: <CAAUk9C4oh6fOkvh_yfaaXD4x6yoXe+--YiWfHL62oBmg-k3UQw@mail.gmail.com>
 <CADHSJjCLJ4=AfAFxPsmYWw0wn8WuKjDS5xeh8SUwJPqvydjRtg@mail.gmail.com>
 <CAAUk9C5WxrVg2YiFvfLy=mkc5gAU36JA2rxCFNO0HnOKGEqpyw@mail.gmail.com>
 <CADHSJjB9NQSdGShv1ThyWSpznOa1MRAKz-hagm6vve=k39BE4A@mail.gmail.com>
 <CAAUk9C7xotQgBGb7XtB41WSO-TY0cow8veu=VjvU23CbaLDnLA@mail.gmail.com>
 <CADHSJjB=u7ZzsTQ5902yjiDv+ie_Bpkvn9byZ5s44p-Rg9yX2w@mail.gmail.com>
 <CAAUk9C5e8N=n-59yqbh3_=8mo_Oe68Xwbfm-Vq_Fy_3RBWMQdg@mail.gmail.com>
 <CAJZHu4RXiQjpG9cVStA6nQ_c1dye--J87g6QLTGxjLBRWx-Ssw@mail.gmail.com>
Message-ID: <CADHSJjBGLwvYsD_yMX1W39Mnyj-ox6Gd1TKuGV4y=rcF3wN-Rg@mail.gmail.com>

I am going to limit my responses to technical parts. It's too early in
the morning for anything else :).

> Yes, all these timer loops in paraview are annoying.

I am not sure there "many" timer loops in ParaView. Please feel free
to elaborate. Even this collaboration timer comes into play only when
connected to a collaboration enabled session. Also, not collaboration
support is one of those advanced, not often used features and hence
the road is expected to be bumpy.

> There is no platform
> independent solution for registering callbacks on sockets, but for each
> supported OS a clean solution exists, which you could implement. So, it is
> doable,

Having the event loop calling select on the socket is a fairly common
practice esp. in single threaded applications.

From arctica1963 at gmail.com  Wed Jun 15 09:34:00 2016
From: arctica1963 at gmail.com (Lester Anderson)
Date: Wed, 15 Jun 2016 14:34:00 +0100
Subject: [Paraview] Colormap loading (xml)
Message-ID: <CAE3taFCywS0TM9aTJ0kth+51_Y_8BNM94M4DaLwL0qXHpiwxiA@mail.gmail.com>

Hello,

I have a couple xml colormaps I want to load as presets but the import
option does not do anything; no error messages.

<ColorMap name="Haxby" space="RGB">
    <Point x="0" o="1" r="0.0392156862745098" g="0" b="0.474509803921569"/>
    <Point x="1" o="1" r="0.0392156862745098" g="0" b="0.474509803921569"/>
    <Point x="1" o="1" r="0.156862745098039" g="0" b="0.588235294117647"/>
.......
    <Point x="30" o="1" r="1" g="0.92156862745098" b="0.92156862745098"/>
    <Point x="31" o="1" r="1" g="0.92156862745098" b="0.92156862745098"/>
    <Point x="31" o="1" r="1" g="1" b="1"/>
    <Point x="32" o="1" r="1" g="1" b="1"/>
</ColorMap>

These worked before, but not in 5.0.0

Pretty sure the file structure is right, but be good if someone could
test. Tried removing the duplicate line entries and still no joy.

Thanks

Lester
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Haxby_reversed_revised.xml
Type: text/xml
Size: 2694 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160615/728d3530/attachment.xml>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Haxby_revised.xml
Type: text/xml
Size: 2687 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160615/728d3530/attachment-0001.xml>

From spl at tirebiter.org  Wed Jun 15 09:36:14 2016
From: spl at tirebiter.org (Steve Lamont)
Date: Wed, 15 Jun 2016 06:36:14 -0700
Subject: [Paraview] Visualization of strata in ParaView
Message-ID: <576159CE.7010609@tirebiter.org>

Before starting, I should state that I'm a complete noob to ParaView, 
having only worked with it for a couple of weeks, so if this is a FAQ, I 
will be humbly abashed if pointed to somewhere rather obvious.

I have a dataset which is somewhat different than those which I believe 
are normally visualized with ParaView.  It is of geological strata and 
the samples are of discrete layers, rather than samples of some 
continuous function.  Furthermore, there are missing data or void regions.

I would like to display cross sections of these data showing the layers 
without color interpolation.  Is there a way to tell ParaView to display 
the colors in a step function rather than as a "continuous tone?"

Also, is there a way to tell ParaView to display the missing data as 
completely transparent -- in other words, setting the NaN color to 
having an opacity of zero?

Thanks for your attention and helpful RTFMs.

Regards.

							spl


From agsmith424 at gmail.com  Wed Jun 15 09:46:18 2016
From: agsmith424 at gmail.com (Andy Smith)
Date: Wed, 15 Jun 2016 09:46:18 -0400
Subject: [Paraview] Colormap loading (xml)
In-Reply-To: <CAE3taFCywS0TM9aTJ0kth+51_Y_8BNM94M4DaLwL0qXHpiwxiA@mail.gmail.com>
References: <CAE3taFCywS0TM9aTJ0kth+51_Y_8BNM94M4DaLwL0qXHpiwxiA@mail.gmail.com>
Message-ID: <CA+yV-vAZenqjHdmR8rCrEfwexcB0i=enxcgXzqW0FJy9pkiGRQ@mail.gmail.com>

Can you try enclosing your map with ColorMaps tags, i.e.,

<ColorMaps>
   <ColorMap name="Haxby" space="RGB">
    <Point x="0" o="1" r="0.0392156862745098" g="0" b="0.474509803921569"/>
    <Point x="1" o="1" r="0.0392156862745098" g="0" b="0.474509803921569"/>
    <Point x="1" o="1" r="0.156862745098039" g="0" b="0.588235294117647"/>
.......
    <Point x="30" o="1" r="1" g="0.92156862745098" b="0.92156862745098"/>
    <Point x="31" o="1" r="1" g="0.92156862745098" b="0.92156862745098"/>
    <Point x="31" o="1" r="1" g="1" b="1"/>
    <Point x="32" o="1" r="1" g="1" b="1"/>
   </ColorMap>
</ColorMaps>

-Andy

On Wed, Jun 15, 2016 at 9:34 AM, Lester Anderson <arctica1963 at gmail.com>
wrote:

> Hello,
>
> I have a couple xml colormaps I want to load as presets but the import
> option does not do anything; no error messages.
>
> <ColorMap name="Haxby" space="RGB">
>     <Point x="0" o="1" r="0.0392156862745098" g="0" b="0.474509803921569"/>
>     <Point x="1" o="1" r="0.0392156862745098" g="0" b="0.474509803921569"/>
>     <Point x="1" o="1" r="0.156862745098039" g="0" b="0.588235294117647"/>
> .......
>     <Point x="30" o="1" r="1" g="0.92156862745098" b="0.92156862745098"/>
>     <Point x="31" o="1" r="1" g="0.92156862745098" b="0.92156862745098"/>
>     <Point x="31" o="1" r="1" g="1" b="1"/>
>     <Point x="32" o="1" r="1" g="1" b="1"/>
> </ColorMap>
>
> These worked before, but not in 5.0.0
>
> Pretty sure the file structure is right, but be good if someone could
> test. Tried removing the duplicate line entries and still no joy.
>
> Thanks
>
> Lester
>
> _______________________________________________
> 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/20160615/a9b47dec/attachment.html>

From arctica1963 at gmail.com  Wed Jun 15 09:52:18 2016
From: arctica1963 at gmail.com (Lester Anderson)
Date: Wed, 15 Jun 2016 14:52:18 +0100
Subject: [Paraview] Colormap loading (xml)
In-Reply-To: <CA+yV-vAZenqjHdmR8rCrEfwexcB0i=enxcgXzqW0FJy9pkiGRQ@mail.gmail.com>
References: <CAE3taFCywS0TM9aTJ0kth+51_Y_8BNM94M4DaLwL0qXHpiwxiA@mail.gmail.com>
 <CA+yV-vAZenqjHdmR8rCrEfwexcB0i=enxcgXzqW0FJy9pkiGRQ@mail.gmail.com>
Message-ID: <CAE3taFCKhUg+-MQVgJj7EvG2d97b5LCmDKkJXcwY9j0UeeT4MA@mail.gmail.com>

On 15 June 2016 at 14:46, Andy Smith <agsmith424 at gmail.com> wrote:
> Can you try enclosing your map with ColorMaps tags, i.e.,
>
> <ColorMaps>
>    <ColorMap name="Haxby" space="RGB">
>     <Point x="0" o="1" r="0.0392156862745098" g="0" b="0.474509803921569"/>
>     <Point x="1" o="1" r="0.0392156862745098" g="0" b="0.474509803921569"/>
>     <Point x="1" o="1" r="0.156862745098039" g="0" b="0.588235294117647"/>
> .......
>     <Point x="30" o="1" r="1" g="0.92156862745098" b="0.92156862745098"/>
>     <Point x="31" o="1" r="1" g="0.92156862745098" b="0.92156862745098"/>
>     <Point x="31" o="1" r="1" g="1" b="1"/>
>     <Point x="32" o="1" r="1" g="1" b="1"/>
>    </ColorMap>
> </ColorMaps>
>
> -Andy
>
> On Wed, Jun 15, 2016 at 9:34 AM, Lester Anderson <arctica1963 at gmail.com>
> wrote:
>>
>> Hello,
>>
>> I have a couple xml colormaps I want to load as presets but the import
>> option does not do anything; no error messages.
>>
>> <ColorMap name="Haxby" space="RGB">
>>     <Point x="0" o="1" r="0.0392156862745098" g="0"
>> b="0.474509803921569"/>
>>     <Point x="1" o="1" r="0.0392156862745098" g="0"
>> b="0.474509803921569"/>
>>     <Point x="1" o="1" r="0.156862745098039" g="0" b="0.588235294117647"/>
>> .......
>>     <Point x="30" o="1" r="1" g="0.92156862745098" b="0.92156862745098"/>
>>     <Point x="31" o="1" r="1" g="0.92156862745098" b="0.92156862745098"/>
>>     <Point x="31" o="1" r="1" g="1" b="1"/>
>>     <Point x="32" o="1" r="1" g="1" b="1"/>
>> </ColorMap>
>>
>> These worked before, but not in 5.0.0
>>
>> Pretty sure the file structure is right, but be good if someone could
>> test. Tried removing the duplicate line entries and still no joy.
>>
>> Thanks
>>
>> Lester
>>
>> _______________________________________________
>> 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
>>
>

Thanks Andy, that solved the problem :)

From berk.geveci at kitware.com  Wed Jun 15 10:18:06 2016
From: berk.geveci at kitware.com (Berk Geveci)
Date: Wed, 15 Jun 2016 10:18:06 -0400
Subject: [Paraview] Comparison of Visit and ParaView development
In-Reply-To: <CAJZHu4RT7dek6wuyEWDDOL85m4kk58gnP8mgdM2-W2knZs7NgQ@mail.gmail.com>
References: <CAJZHu4RT7dek6wuyEWDDOL85m4kk58gnP8mgdM2-W2knZs7NgQ@mail.gmail.com>
Message-ID: <CAE32kpXUPhmNGSYNqG0YkCRXJARv8jnvCjGvhkhQ7PiSVusEZA@mail.gmail.com>

I will leave it to the community to address some of these concerns since I
am obviously biased.

However, Sven made some misguided and unfair statements and I would like to
address those.

Books: Utkarsh & the ParaView community have put a lot of effort in
developing a User's Guide for ParaView, which is excellent. This is a
community developed effort, which is maintained very regularly and is
available in print and download form in addition to the LaTeX source code.
Yes, this is focused on users rather than developers but the same would be
true for any visualization tool out there. In addition, we are in the
process of open sourcing both VTK books, something which will take some
effort because they need to be converted from Framemaker to LaTeX. The goal
is to combine them in some way and open the development to the community.
In addition, ParaView will soon leverage VTK-m for shared-memory parallel
processing (http://m.vtk.org/) and we are developing two open source books
for that.

Community: First of all, ParaView is a natural extension of VTK. Therefore,
a lot of development happens at VTK level. I encourage everyone to take a
look at the archives of the VTK mailing lists including the developer list.
You will find a very vibrant community that goes well beyond Kitware there.
In fact, we are a minority on those lists very often. There are well over
50 developers who have contributed to VTK over the last few years, from
academia, industry and government. Almost all algorithmic work is done in
VTK. It is true that most of the ParaView application is developed by folks
at Kitware. Only a few folks from the ParaView development team regularly
responds to the mailing lists (kudos to them). Our team is now 43 people
about 20 of whom are focused on VTK and ParaView development.

Applications: There are a number of ParaView based applications out there,
clearly demonstrating ParaView as a viable application platform. Not
counting VTK based applications because there are too many of those to list
here.

* Tomviz: http://www.tomviz.org/
* CMB: http://www.computationalmodelbuilder.org/
* VeloView: http://www.paraview.org/veloview/
* Mantid 3D viewer: http://www.mantidproject.org/

In addition to a number of commercial cloud based platforms based on
ParaViewWeb such as SimScale (https://www.simscale.com/). Some of these are
developed at Kitware but some of the have been almost entirely developed
without very little help from us.

Features: There are a lot of huge features that are making their way into
ParaView. To be fair, these will also make their way into VisIt because
they come from VTK so these are really not differentiators between the two.
The two major ones are the new rendering engine including the use of much
more modern OpenGL features with huge performance increase and a focus on
next generation architectures such as GPUs and Xeon Phis though the
development of VTK-m. In addition, we have a strong focus on in situ
analysis through the development of Catalyst, which I would argue is the
premier in situ library with lots of advanced features not available
anywhere else. Something we demonstrated working very well on 1 million MPI
ranks on the Argonne Blue Gene (Mira). Other more research focused areas
such as Cinema (http://cinemascience.org/) are being pushed in
VTK/ParaView/Catalyst quite heavily right now. All of these focus on
exascale computing, which is US Department of Energy push right now.

Issues with ParaView as a development platform:

* It is true that our developer documentation is lacking. ParaView as a
development platform has never been the main driver so making it more
accessible to the larger community is something that has not been pushed as
much as we would like. Not true for VTK though.

* The ParaView code architecture is fairly complicated. This is because it
has evolved to address the needs of various kinds of applications. A much
broader set of needs that tools like VisIt tend to focus on. This is
because our community targets more than HPC Visualization, which were the
original drivers for both VisIt and ParaView. The kind of applications I
listed above is a good demonstration of this.

I believe that the main differentiator between ParaView and other vis tools
out there is the broad functionality _and_ the code quality. Having the two
together is really tough but our community managed this with a heavy
emphasis on code review and code testing. I strongly recommend that folks
look at the software processes used to develop VTK & ParaView as well as
the huge amount of testing (both test quantity and platform coverage) that
we do before every single commit in addition to nightly. There is a very
good overlap between the CMake, CTest & CDash communities and the
VTK/ParaView development communities and there is very good reason behind
this.

Best,
-berk


On Wed, Jun 15, 2016 at 6:54 AM, Sven Kramer <svenkramer40 at gmail.com> wrote:

> Dear ParaView programmers,
> I would like to have some opinions on the suitability of either ParaView
> or Visit for large scalable visualization applications. When I had the
> first contact to visualization more than 5 years ago, Visit was not quite
> scalable and ParaView seemed the only open source alternative.
> Now I am trying to get into some serious developments, and although most
> papers in the field still cite ParaView as their development framework,
> there seems to be no active developers community except for two or three
> kitware employees. Questions on this list are at the most basic level, and
> nobody seems to be able to answer, who isn't working for kitware.
> My impression is that ParaView has grown so complicated over the years
> that it is no longer usable as a framework for parallel visualization
> development. Only the ParaView application itself is still frequently used.
> On the other hand, Visit seems to have overtaken ParaView in all aspects.
> Most important is the high quality documentation and very active community,
> scalability is now as good as ParaView, and collaborative web visualization
> is coming rapidly.
>
> What is your opinion? Are there any points, where ParaView is clearly
> advantageous over Visit? Or is it used by most people only out of
> convenience, because they have always worked with ParaView?
> Given the horribly out of date books on ParaView and parallel VTK
> development, web documentation mixing three major versions without stating
> which version is referred to, and the dead development discussions I don't
> see any possibility of learning ParaView programming today. Which material
> do you use for tutorials and documentation?
>
> Thank you
> Sven
>
> _______________________________________________
> 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/20160615/386943dd/attachment.html>

From Matthias.Zenker at erbe-med.com  Wed Jun 15 10:20:17 2016
From: Matthias.Zenker at erbe-med.com (Zenker, Dr. Matthias)
Date: Wed, 15 Jun 2016 14:20:17 +0000
Subject: [Paraview] display boundaries of 2D geometry
Message-ID: <F9562F3B302F29479A203FC5AF9E3E050F48E46D@SERBE4I1.intra.erbe-med.de>

Hi Samuel,

thank you! So there is a way to do what I want provided that the mesh data are converted similar to the files you sent me. Good to know.
It would probably require some coding from my side to implement that solution for my workflow, i.e. teach Salom? and/or Elmer to convert the mesh into that multi-file format. Since I am short in time at the moment, I will live with the threshold filter solution Cory proposed.

Thank you again,

Matthias


Von: Samuel Key [mailto:samuelkey at bresnan.net]
Gesendet: Dienstag, 14. Juni 2016 18:45
An: Zenker, Dr. Matthias
Betreff: Re: [Paraview] display boundaries of 2D geometry


Matthias,

Here is a time(0.0) mesh datum set that you or your staff can use in PV 5.0.0 to see how PV's Extract Block filter works. Take a look at the ASCII-formatted file fmavto.mesh.pvd; it is a "mother file" that tells ParaView about all of the *.vtu files. (Also, the *.vtu can be loaded individually if you like.)

Samuel W. Key
FMS Development, LLC
1005 39th Ave. NE
Great Falls, Montana 59404
USA

On 6/14/2016 9:21 AM, Zenker, Dr. Matthias wrote:

Hi Cory,



thank you for the hint.

However, I don't know how to make a mesh generated by Salom? a multi-block dataset. Could you tell me more or give me a pointer on where I can find that out?



Thanks,



Matthias



-----Urspr?ngliche Nachricht-----

Von: Cory Quammen [mailto:cory.quammen at kitware.com]

Gesendet: Dienstag, 14. Juni 2016 14:27

An: Zenker, Dr. Matthias

Cc: paraview at paraview.org<mailto:paraview at paraview.org>

Betreff: Re: [Paraview] display boundaries of 2D geometry



Hi Matthais,



People typically use multi-block data sets for this purpose. ParaView has a

multi-block inspector that enables you change the visibility of the blocks in a

data set. If you make each surface a block, then you can show/hide each at

will.



HTH,

Cory



On Tue, Jun 14, 2016 at 1:11 PM, Zenker, Dr. Matthias

<Matthias.Zenker at erbe-med.com><mailto:Matthias.Zenker at erbe-med.com> wrote:

Hi Cory,



this helped indeed, thank you.

I  load the mesh.vtu file and apply the Threshold filter on the GeometryID,

and display that together with my simulation results. That works fine.

If I want to display several parts selectively, I can use several Thresholds,

which is a bit clumsy.

It would be nice to be able to get a list of all GeometryIDs, and to check

those which I want displayed. Do you know if there is a way to do that? Or on

a more general basis: are there other, more elegant ways to display a

geometry in ParaView?



Thanks again,



Matthias





-----Urspr?ngliche Nachricht-----

Von: Cory Quammen [mailto:cory.quammen at kitware.com]

Gesendet: Montag, 13. Juni 2016 22:28

An: Zenker, Dr. Matthias

Cc: paraview at paraview.org<mailto:paraview at paraview.org>

Betreff: Re: [Paraview] display boundaries of 2D geometry



Matthias,



I'm not sure I fully understand exactly what you are trying to do,

but I will try to make a suggestion anyway. If the edges have a cell

data array giving the ID, you should be able to use the Threshold

filter to extract the edges associated with a particular body ID.

Just set the threshold values to the ID you want to see.



Hope that helps,

Cory



On Mon, Jun 13, 2016 at 6:43 PM, Zenker, Dr. Matthias

<Matthias.Zenker at erbe-med.com><mailto:Matthias.Zenker at erbe-med.com> wrote:

Hi,







is there a way to display the boundaries (edges) of a 2D geometry?

I have converted my mesh to vtu using Elmergrid, so I have the IDs

of bodies (=surfaces in 2D) and boundaries (edges) in a vtu file.

Can I just display the edges having the same ID? The extract edges filter

does not help.

What

else could I try?







Thank you for a helpful hint,







Matthias



________________________________



Erbe Elektromedizin GmbH Firmensitz: 72072 Tuebingen

Geschaeftsfuehrer:

Christian O. Erbe, Reiner Thede Registergericht: Stuttgart HRB

380137





_______________________________________________

Powered by www.kitware.com<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.kitware.com&d=BQMDaQ&c=7vND7vRFB1FzfxRXc-X80O-MJSZd5Q-IVyyYW-Ff2gY&r=3enlI3TuQDmO9BnMCnxq2Mfm4tAO6Z3_Ae1Yc57DMr4&m=a_OAZXRTIHEvXxA9eQQtPP-BXWp4aSK9LyLPg-xLmTw&s=h2wNX1lfcnxjPQHbJd88eRG7TWnY6Zm-xnl-zmwyZ5E&e=>



Visit other Kitware open-source projects at

http://www.kitware.com/opensource/opensource.html<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.kitware.com_opensource_opensource.html&d=BQMDaQ&c=7vND7vRFB1FzfxRXc-X80O-MJSZd5Q-IVyyYW-Ff2gY&r=3enlI3TuQDmO9BnMCnxq2Mfm4tAO6Z3_Ae1Yc57DMr4&m=a_OAZXRTIHEvXxA9eQQtPP-BXWp4aSK9LyLPg-xLmTw&s=3cfw58koLrjvg3wx-EBboGeCbwWHPzfBEu4dHWGrubE&e=>



Please keep messages on-topic and check the ParaView Wiki at:

http://paraview.org/Wiki/ParaView<https://urldefense.proofpoint.com/v2/url?u=http-3A__paraview.org_Wiki_ParaView&d=BQMDaQ&c=7vND7vRFB1FzfxRXc-X80O-MJSZd5Q-IVyyYW-Ff2gY&r=3enlI3TuQDmO9BnMCnxq2Mfm4tAO6Z3_Ae1Yc57DMr4&m=a_OAZXRTIHEvXxA9eQQtPP-BXWp4aSK9LyLPg-xLmTw&s=o9dx18Zn4PU3_xFzvTtd9ozxZwG-VFM3cKK6JvtaeQ8&e=>



Search the list archives at: http://markmail.org/search/?q=ParaView<https://urldefense.proofpoint.com/v2/url?u=http-3A__markmail.org_search_-3Fq-3DParaView&d=BQMDaQ&c=7vND7vRFB1FzfxRXc-X80O-MJSZd5Q-IVyyYW-Ff2gY&r=3enlI3TuQDmO9BnMCnxq2Mfm4tAO6Z3_Ae1Yc57DMr4&m=a_OAZXRTIHEvXxA9eQQtPP-BXWp4aSK9LyLPg-xLmTw&s=Cqdyx4vJH-JeZUWg8taxp92SLMyZLj3ZFp37taZasBQ&e=>



Follow this link to subscribe/unsubscribe:

http://public.kitware.com/mailman/listinfo/paraview<https://urldefense.proofpoint.com/v2/url?u=http-3A__public.kitware.com_mailman_listinfo_paraview&d=BQMDaQ&c=7vND7vRFB1FzfxRXc-X80O-MJSZd5Q-IVyyYW-Ff2gY&r=3enlI3TuQDmO9BnMCnxq2Mfm4tAO6Z3_Ae1Yc57DMr4&m=a_OAZXRTIHEvXxA9eQQtPP-BXWp4aSK9LyLPg-xLmTw&s=CfbsSNdmDPkGMMwjEjwdLhEQ6A0GJJ3y3UxDmuggOJk&e=>









--

Cory Quammen

R&D Engineer

Kitware, Inc.

________________________________



Erbe Elektromedizin GmbH Firmensitz: 72072 Tuebingen

Geschaeftsfuehrer: Christian O. Erbe, Reiner Thede Registergericht:

Stuttgart HRB 380137









--

Cory Quammen

R&D Engineer

Kitware, Inc.

________________________________



Erbe Elektromedizin GmbH Firmensitz: 72072 Tuebingen Geschaeftsfuehrer: Christian O. Erbe, Reiner Thede Registergericht: Stuttgart HRB 380137



_______________________________________________

Powered by www.kitware.com<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.kitware.com&d=BQMDaQ&c=7vND7vRFB1FzfxRXc-X80O-MJSZd5Q-IVyyYW-Ff2gY&r=3enlI3TuQDmO9BnMCnxq2Mfm4tAO6Z3_Ae1Yc57DMr4&m=a_OAZXRTIHEvXxA9eQQtPP-BXWp4aSK9LyLPg-xLmTw&s=h2wNX1lfcnxjPQHbJd88eRG7TWnY6Zm-xnl-zmwyZ5E&e=>



Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.kitware.com_opensource_opensource.html&d=BQMDaQ&c=7vND7vRFB1FzfxRXc-X80O-MJSZd5Q-IVyyYW-Ff2gY&r=3enlI3TuQDmO9BnMCnxq2Mfm4tAO6Z3_Ae1Yc57DMr4&m=a_OAZXRTIHEvXxA9eQQtPP-BXWp4aSK9LyLPg-xLmTw&s=3cfw58koLrjvg3wx-EBboGeCbwWHPzfBEu4dHWGrubE&e=>



Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView<https://urldefense.proofpoint.com/v2/url?u=http-3A__paraview.org_Wiki_ParaView&d=BQMDaQ&c=7vND7vRFB1FzfxRXc-X80O-MJSZd5Q-IVyyYW-Ff2gY&r=3enlI3TuQDmO9BnMCnxq2Mfm4tAO6Z3_Ae1Yc57DMr4&m=a_OAZXRTIHEvXxA9eQQtPP-BXWp4aSK9LyLPg-xLmTw&s=o9dx18Zn4PU3_xFzvTtd9ozxZwG-VFM3cKK6JvtaeQ8&e=>



Search the list archives at: http://markmail.org/search/?q=ParaView<https://urldefense.proofpoint.com/v2/url?u=http-3A__markmail.org_search_-3Fq-3DParaView&d=BQMDaQ&c=7vND7vRFB1FzfxRXc-X80O-MJSZd5Q-IVyyYW-Ff2gY&r=3enlI3TuQDmO9BnMCnxq2Mfm4tAO6Z3_Ae1Yc57DMr4&m=a_OAZXRTIHEvXxA9eQQtPP-BXWp4aSK9LyLPg-xLmTw&s=Cqdyx4vJH-JeZUWg8taxp92SLMyZLj3ZFp37taZasBQ&e=>



Follow this link to subscribe/unsubscribe:

http://public.kitware.com/mailman/listinfo/paraview<https://urldefense.proofpoint.com/v2/url?u=http-3A__public.kitware.com_mailman_listinfo_paraview&d=BQMDaQ&c=7vND7vRFB1FzfxRXc-X80O-MJSZd5Q-IVyyYW-Ff2gY&r=3enlI3TuQDmO9BnMCnxq2Mfm4tAO6Z3_Ae1Yc57DMr4&m=a_OAZXRTIHEvXxA9eQQtPP-BXWp4aSK9LyLPg-xLmTw&s=CfbsSNdmDPkGMMwjEjwdLhEQ6A0GJJ3y3UxDmuggOJk&e=>

________________________________

Erbe Elektromedizin GmbH Firmensitz: 72072 Tuebingen Geschaeftsfuehrer: Christian O. Erbe, Reiner Thede Registergericht: Stuttgart HRB 380137

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

From rdjamis at sandia.gov  Wed Jun 15 11:10:39 2016
From: rdjamis at sandia.gov (Jamison, Ryan Dale)
Date: Wed, 15 Jun 2016 15:10:39 +0000
Subject: [Paraview] Plot csv over time
Message-ID: <0B5B1BD3-5DFE-4454-98B5-C8744B75D7C1@sandia.gov>

Hello,

I was wondering if there is a way to plot csv data over time? Specifically, I would like to read into an active Paraview session that already has some exodus results loaded a csv file (this I can already do). This csv file came from the same simulation as the exodus data. I?d like to then plot the csv results over time such that the green vertical line shows up denoting time as a video plays. 

I?ve found I can use ?plot data? for the csv data and I can indeed plot time vs. variable but the green vertical line doesn?t appear. My theory is that the vertical time marker only appears when plotting something over time with the appropriate filter. Any idea how to get the time marker to appear in the plot? 

Thanks, Ryan Jamison

From peterdebuchev at gmail.com  Wed Jun 15 11:26:23 2016
From: peterdebuchev at gmail.com (Peter Debuchev)
Date: Wed, 15 Jun 2016 17:26:23 +0200
Subject: [Paraview] created representation is invisible in view
Message-ID: <CAAUk9C5UGS_1XYgMKGcgg-jtc+NM5JYT1RQQqg5Hwo5huHCBXQ@mail.gmail.com>

Hello,
short question, probably with an easy answer:

Why is the vtkSMRepresentationProxy, created for a vtkSMSourceProxy of a
SphereSource not rendered in the attached c++ code?

I guess I am missing a step which adds the representation to the view. But
how?

Peter

#include "vtkSMSession.h"
#include "vtkSMSessionClient.h"
#include "vtkProcessModule.h"
#include "vtkPVOptions.h"
#include "vtkInitializationHelper.h"
#include "vtkSMProxy.h"
#include "vtkSMProxyManager.h"
#include "vtkSMSessionProxyManager.h"
#include "vtkSMProxy.h"
#include "vtkSMPropertyHelper.h"
#include "vtkSMParaViewPipelineController.h"
#include "vtkSMProxy.h"
#include "vtkSMRepresentationProxy.h"
#include "vtkSMRenderViewProxy.h"
#include "vtkRenderWindowInteractor.h"

using namespace std;

int main(int argc, char* argv[]){
  vtkPVOptions *options=vtkPVOptions::New();

vtkInitializationHelper::Initialize(argc,argv,vtkProcessModule::PROCESS_CLIENT,options);

  vtkSMSessionClient *session=vtkSMSessionClient::New();
  session->Connect("cs://localhost:11111");

  vtkSMParaViewPipelineController*
smcontroller=vtkSMParaViewPipelineController::New();
  smcontroller->InitializeSession(session);

  vtkSMSessionProxyManager* pxm = session->GetSessionProxyManager();

  vtkSMRenderViewProxy
*view=vtkSMRenderViewProxy::SafeDownCast(pxm->NewProxy("views","RenderView"));

  vtkSMSourceProxy
*sphere=vtkSMSourceProxy::SafeDownCast(pxm->NewProxy("sources","SphereSource"));
  sphere->UpdatePipeline();

  vtkSMRepresentationProxy
*repr=view->CreateDefaultRepresentation(sphere,0);
  repr->UpdateVTKObjects();

  view->MakeRenderWindowInteractor(true);
  vtkRenderWindowInteractor *iren=view->GetInteractor();
  iren->Initialize();
  view->GetInteractor()->Start();

  session->CloseSession();
  vtkInitializationHelper::Finalize();
}
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160615/a09f2de6/attachment.html>

From peterdebuchev at gmail.com  Wed Jun 15 11:30:55 2016
From: peterdebuchev at gmail.com (Peter Debuchev)
Date: Wed, 15 Jun 2016 17:30:55 +0200
Subject: [Paraview] vtkSMCollaborationManager::FollowUser(id) doesn't
 update view
In-Reply-To: <CAJZHu4RXiQjpG9cVStA6nQ_c1dye--J87g6QLTGxjLBRWx-Ssw@mail.gmail.com>
References: <CAAUk9C4oh6fOkvh_yfaaXD4x6yoXe+--YiWfHL62oBmg-k3UQw@mail.gmail.com>
 <CADHSJjCLJ4=AfAFxPsmYWw0wn8WuKjDS5xeh8SUwJPqvydjRtg@mail.gmail.com>
 <CAAUk9C5WxrVg2YiFvfLy=mkc5gAU36JA2rxCFNO0HnOKGEqpyw@mail.gmail.com>
 <CADHSJjB9NQSdGShv1ThyWSpznOa1MRAKz-hagm6vve=k39BE4A@mail.gmail.com>
 <CAAUk9C7xotQgBGb7XtB41WSO-TY0cow8veu=VjvU23CbaLDnLA@mail.gmail.com>
 <CADHSJjB=u7ZzsTQ5902yjiDv+ie_Bpkvn9byZ5s44p-Rg9yX2w@mail.gmail.com>
 <CAAUk9C5e8N=n-59yqbh3_=8mo_Oe68Xwbfm-Vq_Fy_3RBWMQdg@mail.gmail.com>
 <CAJZHu4RXiQjpG9cVStA6nQ_c1dye--J87g6QLTGxjLBRWx-Ssw@mail.gmail.com>
Message-ID: <CAAUk9C7DYgHwrjX-jYAbsCzmwtc5828Ce7onaUZnN8guNNM15w@mail.gmail.com>

I don't find anything constructive in your answer. If you think paraview
sucks, I don't care if you discuss it in your own thread. But I am of a
different opinion and I prefer positive discussions, so please stop it here.

Peter

2016-06-15 7:34 GMT+02:00 Sven Kramer <svenkramer40 at gmail.com>:

> Yes, all these timer loops in paraview are annoying. There is no platform
> independent solution for registering callbacks on sockets, but for each
> supported OS a clean solution exists, which you could implement. So, it is
> doable, but requires more effort than what is usually put into paraview.
> Additionally you wouldn't probably want a callback after each received
> byte, but rather after each complete message. This is not possible in a
> generic way with the present message construction.
>
> You seem to be stuck with similar problems as I was. You may want to
> consider Visit as an alternative. Visit has an active user and developer
> community so that there are more than two people on the mailing lists who
> can answer questions like yours. Most of Visit has evolved over the last
> few years rather than the "don't touch if not necessary" long history of
> paraview, so that it has a much more modern design. These are some of the
> reasons why my supervisor convinced me to favour Visit even after I was
> half way through my project.
>
> 2016-06-10 18:58 GMT+02:00 Peter Debuchev <peterdebuchev at gmail.com>:
>
>> Ok, that doesn't sound as bad as I expected. But still, is it necessary
>> to "poll" the socket, checking its "select" method?
>> I am not familiar with the details of socket communication, but I expect
>> it should be possible that the socket invokes some callback when a message
>> arrives? Or does some of the VTK design contradict such socket callbacks?
>>
>> I found that it is always problematic performance-wise if more than a few
>> timers are running on one cpu.
>>
>> Peter
>>
>> 2016-06-10 15:17 GMT+02:00 Utkarsh Ayachit <utkarsh.ayachit at kitware.com>:
>>
>>> ProcessEvents() doesn't poll the server. It only "select"s on the
>>> socket to see if the server sent any new messages to the client.
>>>
>>> > One more question out of curiosity: isn't it quite ineffient, if
>>> clients
>>> > continuously invoke vtkNetworkAccessManager::ProcessEvents?()? For
>>> smooth
>>> > interaction this has to happen at least 10 times per second, which
>>> causes a
>>> > lot of network traffic by polling the server again and again,
>>> especially if
>>> > more than one client connects to the same server.
>>> > Isn't it possible to react on incoming server events by registering a
>>> > callback that does the same server event processing only when a new
>>> event
>>> > has occurred? I mean, all of VTK and ParaView is event based, why not
>>> the
>>> > server message processing?
>>> >
>>> > Peter
>>> >
>>> > 2016-06-09 18:29 GMT+02:00 Utkarsh Ayachit <
>>> utkarsh.ayachit at kitware.com>:
>>> >>
>>> >> Here's the fix:
>>> >>
>>> >> diff --git a/main.cxx b/main.cxx
>>> >> index dd47991..0f679ba 100644
>>> >> --- a/main.cxx
>>> >> +++ b/main.cxx
>>> >> @@ -65,7 +65,7 @@ int main(int argc, char* argv[]){
>>> >>    vtkSMSessionProxyManager* pxm = session->GetSessionProxyManager();
>>> >>
>>> >>    //Collaboration:
>>> >> -  vtkSMCollaborationManager
>>> >> *collaboration=vtkSMCollaborationManager::New();
>>> >> +  vtkSMCollaborationManager *collaboration=
>>> >> session->GetCollaborationManager();
>>> >>    collaboration->SetSession(session);
>>> >>    collaboration->UpdateUserInformations();
>>> >
>>> >
>>>
>>
>>
>> _______________________________________________
>> 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/20160615/849f966d/attachment.html>

From utkarsh.ayachit at kitware.com  Wed Jun 15 13:46:07 2016
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Wed, 15 Jun 2016 13:46:07 -0400
Subject: [Paraview] created representation is invisible in view
In-Reply-To: <CAAUk9C5UGS_1XYgMKGcgg-jtc+NM5JYT1RQQqg5Hwo5huHCBXQ@mail.gmail.com>
References: <CAAUk9C5UGS_1XYgMKGcgg-jtc+NM5JYT1RQQqg5Hwo5huHCBXQ@mail.gmail.com>
Message-ID: <CADHSJjCXg8aE5sEYXW71VChVW1P2WdhOgsh2qyhjWPgg3cx8Lg@mail.gmail.com>

You're missing "adding the representation to the view" part, typically
done using vtkSMParaViewPipelineControllerWithRendering::Show.

See this example:

https://gitlab.kitware.com/paraview/paraview/blob/master/ParaViewCore/ServerManager/Rendering/Testing/Cxx/TestParaViewPipelineControllerWithRendering.cxx#L126-128

From peterdebuchev at gmail.com  Wed Jun 15 13:51:22 2016
From: peterdebuchev at gmail.com (Peter Debuchev)
Date: Wed, 15 Jun 2016 19:51:22 +0200
Subject: [Paraview] created representation is invisible in view
In-Reply-To: <CADHSJjCXg8aE5sEYXW71VChVW1P2WdhOgsh2qyhjWPgg3cx8Lg@mail.gmail.com>
References: <CAAUk9C5UGS_1XYgMKGcgg-jtc+NM5JYT1RQQqg5Hwo5huHCBXQ@mail.gmail.com>
 <CADHSJjCXg8aE5sEYXW71VChVW1P2WdhOgsh2qyhjWPgg3cx8Lg@mail.gmail.com>
Message-ID: <CAAUk9C6Qzd+WwHZkh_0WewNHLBvm-3=KdkBGQYO+8dsxmfqNhg@mail.gmail.com>

Thanks!
Just found out that another solution is to set the view's "Representations"
property to repr and the representation's "Input" property to sphere. I'll
try yours as well, it looks much simpler.

Peter


2016-06-15 19:46 GMT+02:00 Utkarsh Ayachit <utkarsh.ayachit at kitware.com>:

> You're missing "adding the representation to the view" part, typically
> done using vtkSMParaViewPipelineControllerWithRendering::Show.
>
> See this example:
>
>
> https://gitlab.kitware.com/paraview/paraview/blob/master/ParaViewCore/ServerManager/Rendering/Testing/Cxx/TestParaViewPipelineControllerWithRendering.cxx#L126-128
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160615/b61f1d90/attachment.html>

From utkarsh.ayachit at kitware.com  Wed Jun 15 13:54:53 2016
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Wed, 15 Jun 2016 13:54:53 -0400
Subject: [Paraview] Plot csv over time
In-Reply-To: <0B5B1BD3-5DFE-4454-98B5-C8744B75D7C1@sandia.gov>
References: <0B5B1BD3-5DFE-4454-98B5-C8744B75D7C1@sandia.gov>
Message-ID: <CADHSJjCBdrxx5JHV1dUUdDgkuqucNomVYX0q5S-ouxmu=GtdCQ@mail.gmail.com>

The green line appears with the X axis is set to a data array named
"Time". See the attached state file. You'll can.ex2 (included in
ParaView Example Data) and the attached csv file to load the state.

On Wed, Jun 15, 2016 at 11:10 AM, Jamison, Ryan Dale <rdjamis at sandia.gov> wrote:
> Hello,
>
> I was wondering if there is a way to plot csv data over time? Specifically, I would like to read into an active Paraview session that already has some exodus results loaded a csv file (this I can already do). This csv file came from the same simulation as the exodus data. I?d like to then plot the csv results over time such that the green vertical line shows up denoting time as a video plays.
>
> I?ve found I can use ?plot data? for the csv data and I can indeed plot time vs. variable but the green vertical line doesn?t appear. My theory is that the vertical time marker only appears when plotting something over time with the appropriate filter. Any idea how to get the time marker to appear in the plot?
>
> Thanks, Ryan Jamison
> _______________________________________________
> 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: can0.csv
Type: text/csv
Size: 7461 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160615/5fa2e1db/attachment.csv>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: sample.pvsm
Type: application/octet-stream
Size: 160046 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160615/5fa2e1db/attachment.obj>

From dave.demarle at kitware.com  Wed Jun 15 16:21:14 2016
From: dave.demarle at kitware.com (David E DeMarle)
Date: Wed, 15 Jun 2016 16:21:14 -0400
Subject: [Paraview] Comparison of Visit and ParaView development
In-Reply-To: <CAJZHu4RT7dek6wuyEWDDOL85m4kk58gnP8mgdM2-W2knZs7NgQ@mail.gmail.com>
References: <CAJZHu4RT7dek6wuyEWDDOL85m4kk58gnP8mgdM2-W2knZs7NgQ@mail.gmail.com>
Message-ID: <CANjZAi8-gS_F=7HaD4BGAwRW1tPBaHpmGFy_7wxcrFPH+soMLg@mail.gmail.com>

Dear ParaView programmers,

> ... there seems to be no active developers community except for two or
> three kitware employees.
>

git shortlog 39fb355b..37d222b6 | grep "):" | wc -l
32
granted, most of those who committed between v5.0.0 and v5.1.0.rc1 were
from kitware, but 10x more than 3 active developers.

Questions on this list are at the most basic level, and nobody seems to be
> able to answer, who isn't working for kitware.
>

Try paraview-developers list for paraview development questions.

We would of course like for all questions to be answered and we can
certainly do a better job at it but the fact is that everyone is of course
very busy. Kitware of course offers paid support if you need a guarantee
that your questions will be answered.


> My impression is that ParaView has grown so complicated over the years
> that it is no longer usable as a framework for parallel visualization
> development. Only the ParaView application itself is still frequently used.
> On the other hand, Visit seems to have overtaken ParaView in all aspects.
> Most important is the high quality documentation and very active community,
> scalability is now as good as ParaView, and collaborative web visualization
> is coming rapidly.
>

Both VisIt and ParaView are very good - and free! If you watch them both
long enough, over time you will see that at any given point one is better
at some things than the other, and that over time the specific things
(stability, HPC installation base, scalability, ease of use, documentation,
applicability to scientific domain X, etc) change as they both improve,


>
> What is your opinion? Are there any points, where ParaView is clearly
> advantageous over Visit? Or is it used by most people only out of
> convenience, because they have always worked with ParaView?
>

I leave the opinion about what is currently better about each tool to those
who know them both better than I.

I will agree that people use ParaView mostly out of convenience. But the
same thing goes for VisIt. Same thing goes for operating systems and text
editors for that matter. Once you invest the time to become an expert at
something, you are naturally loathe to bear with the frustration of
starting over.


> Given the horribly out of date books on ParaView and parallel VTK
> development, web documentation mixing three major versions without stating
> which version is referred to, and the dead development discussions I don't
> see any possibility of learning ParaView programming today. Which material
> do you use for tutorials and documentation?
>
>
We should certainly do a better job at documenting ParaView. We really
really do want to increase the developer pool.

But alas, good developing training material takes a lot of time to put
together and there aren't all that many people who want and need  advanced
ParaView material. The people who know a lot are always very busy trying to
making it better at X and don't have a lot of time to help other people
learn to know a lot.

The best way to learn is looking at the code, studying the on-line and in
source examples, asking politely on the mailing list, and taking the time
to get over the learning curve.


> Thank you
> Sven
>
>
Hope that helps.


> _______________________________________________
> 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/20160615/ba464f2d/attachment.html>

From wascott at sandia.gov  Wed Jun 15 17:13:01 2016
From: wascott at sandia.gov (Scott, W Alan)
Date: Wed, 15 Jun 2016 21:13:01 +0000
Subject: [Paraview] [EXTERNAL] Re: Comparison of Visit and ParaView
 development
In-Reply-To: <CAE32kpXUPhmNGSYNqG0YkCRXJARv8jnvCjGvhkhQ7PiSVusEZA@mail.gmail.com>
References: <CAJZHu4RT7dek6wuyEWDDOL85m4kk58gnP8mgdM2-W2knZs7NgQ@mail.gmail.com>
 <CAE32kpXUPhmNGSYNqG0YkCRXJARv8jnvCjGvhkhQ7PiSVusEZA@mail.gmail.com>
Message-ID: <825f253022ef40849ae26cb3f9e49d7d@ES01AMSNLNT.srn.sandia.gov>

I think Berk answered well from a technical and custom applications viewpoint.  Although not your primary question, I thought I would add just a few words regarding ParaView from a user?s perspective.

Here at Sandia National Laboratories, we have seen amazing growth of ParaView usage over the last decade.  Last year we had over 330 users.  Last month alone we had 161 individual users (not counting support or developers).  ParaView is used for projects ranging from toys (learning how to use ParaView with the can.exo dataset) to huge (a 100 million cell, 2048 file dataset with 204 timesteps).  It is being used on everything from interplanetary space probe research to visualizing wind turbines to climate change.  Catalyst is also part of ParaView development, and Catalyst is making a huge impact here at Sandia.

Regarding documentation, ParaView has come a long way in the last few years with regards to user documentation, and I would argue is now similar to commercial packages.  Further, the website has all of this information easily available.  The next version of ParaView (5.1) features an updated Help menu, providing easy access to the ParaView guide, and two full tutorials (the Supercomputing tutorial and the Sandia tutorial).
http://www.paraview.org/
http://www.paraview.org/paraview-guide/
http://www.paraview.org/tutorials/

You mention that Kitware appears to be the most active at answering the paraview.org list, and this is true.  I believe this is primarily because Kitware is by far the most knowledgeable, not because they are the only ones on the list.  Thus, you tend to hear from them first.

Regarding your primary question ? VisIt vs ParaView, I have no opinions, since I don?t know VisIt.

Alan



From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Berk Geveci
Sent: Wednesday, June 15, 2016 8:18 AM
To: Sven Kramer <svenkramer40 at gmail.com>
Cc: ParaView <paraview at paraview.org>
Subject: [EXTERNAL] Re: [Paraview] Comparison of Visit and ParaView development

I will leave it to the community to address some of these concerns since I am obviously biased.

However, Sven made some misguided and unfair statements and I would like to address those.

Books: Utkarsh & the ParaView community have put a lot of effort in developing a User's Guide for ParaView, which is excellent. This is a community developed effort, which is maintained very regularly and is available in print and download form in addition to the LaTeX source code. Yes, this is focused on users rather than developers but the same would be true for any visualization tool out there. In addition, we are in the process of open sourcing both VTK books, something which will take some effort because they need to be converted from Framemaker to LaTeX. The goal is to combine them in some way and open the development to the community. In addition, ParaView will soon leverage VTK-m for shared-memory parallel processing (http://m.vtk.org/) and we are developing two open source books for that.

Community: First of all, ParaView is a natural extension of VTK. Therefore, a lot of development happens at VTK level. I encourage everyone to take a look at the archives of the VTK mailing lists including the developer list. You will find a very vibrant community that goes well beyond Kitware there. In fact, we are a minority on those lists very often. There are well over 50 developers who have contributed to VTK over the last few years, from academia, industry and government. Almost all algorithmic work is done in VTK. It is true that most of the ParaView application is developed by folks at Kitware. Only a few folks from the ParaView development team regularly responds to the mailing lists (kudos to them). Our team is now 43 people about 20 of whom are focused on VTK and ParaView development.

Applications: There are a number of ParaView based applications out there, clearly demonstrating ParaView as a viable application platform. Not counting VTK based applications because there are too many of those to list here.

* Tomviz: http://www.tomviz.org/
* CMB: http://www.computationalmodelbuilder.org/
* VeloView: http://www.paraview.org/veloview/
* Mantid 3D viewer: http://www.mantidproject.org/

In addition to a number of commercial cloud based platforms based on ParaViewWeb such as SimScale (https://www.simscale.com/). Some of these are developed at Kitware but some of the have been almost entirely developed without very little help from us.

Features: There are a lot of huge features that are making their way into ParaView. To be fair, these will also make their way into VisIt because they come from VTK so these are really not differentiators between the two. The two major ones are the new rendering engine including the use of much more modern OpenGL features with huge performance increase and a focus on next generation architectures such as GPUs and Xeon Phis though the development of VTK-m. In addition, we have a strong focus on in situ analysis through the development of Catalyst, which I would argue is the premier in situ library with lots of advanced features not available anywhere else. Something we demonstrated working very well on 1 million MPI ranks on the Argonne Blue Gene (Mira). Other more research focused areas such as Cinema (http://cinemascience.org/) are being pushed in VTK/ParaView/Catalyst quite heavily right now. All of these focus on exascale computing, which is US Department of Energy push right now.

Issues with ParaView as a development platform:

* It is true that our developer documentation is lacking. ParaView as a development platform has never been the main driver so making it more accessible to the larger community is something that has not been pushed as much as we would like. Not true for VTK though.

* The ParaView code architecture is fairly complicated. This is because it has evolved to address the needs of various kinds of applications. A much broader set of needs that tools like VisIt tend to focus on. This is because our community targets more than HPC Visualization, which were the original drivers for both VisIt and ParaView. The kind of applications I listed above is a good demonstration of this.

I believe that the main differentiator between ParaView and other vis tools out there is the broad functionality _and_ the code quality. Having the two together is really tough but our community managed this with a heavy emphasis on code review and code testing. I strongly recommend that folks look at the software processes used to develop VTK & ParaView as well as the huge amount of testing (both test quantity and platform coverage) that we do before every single commit in addition to nightly. There is a very good overlap between the CMake, CTest & CDash communities and the VTK/ParaView development communities and there is very good reason behind this.

Best,
-berk


On Wed, Jun 15, 2016 at 6:54 AM, Sven Kramer <svenkramer40 at gmail.com<mailto:svenkramer40 at gmail.com>> wrote:
Dear ParaView programmers,
I would like to have some opinions on the suitability of either ParaView or Visit for large scalable visualization applications. When I had the first contact to visualization more than 5 years ago, Visit was not quite scalable and ParaView seemed the only open source alternative.
Now I am trying to get into some serious developments, and although most papers in the field still cite ParaView as their development framework, there seems to be no active developers community except for two or three kitware employees. Questions on this list are at the most basic level, and nobody seems to be able to answer, who isn't working for kitware.
My impression is that ParaView has grown so complicated over the years that it is no longer usable as a framework for parallel visualization development. Only the ParaView application itself is still frequently used.
On the other hand, Visit seems to have overtaken ParaView in all aspects. Most important is the high quality documentation and very active community, scalability is now as good as ParaView, and collaborative web visualization is coming rapidly.
What is your opinion? Are there any points, where ParaView is clearly advantageous over Visit? Or is it used by most people only out of convenience, because they have always worked with ParaView?
Given the horribly out of date books on ParaView and parallel VTK development, web documentation mixing three major versions without stating which version is referred to, and the dead development discussions I don't see any possibility of learning ParaView programming today. Which material do you use for tutorials and documentation?
Thank you
Sven

_______________________________________________
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/20160615/bcb15319/attachment.html>

From samuelkey at bresnan.net  Wed Jun 15 17:15:11 2016
From: samuelkey at bresnan.net (Samuel Key)
Date: Wed, 15 Jun 2016 15:15:11 -0600
Subject: [Paraview] Visualization of strata in ParaView
In-Reply-To: <576159CE.7010609@tirebiter.org>
References: <576159CE.7010609@tirebiter.org>
Message-ID: <8b8ae433-99f8-9c6e-4580-ac31285b3e68@bresnan.net>

Welcome to ParaView Steve,

Everybody was a noob when they first tried to use ParaView, but the more 
you use ParaView, the smarter it gets.

Now, to your question about displaying a geological stratigraphy in 
ParaView, assuming that you have surfaces (of some sort, but preferably 
cell boundaries) at the material interfaces and that you have cells 
containing a datum item that is a number from a monotone sequence, the 
following is a possibility:

(1) Load and display your mesh in ParaView. ("Load and display" is an 
overloaded phrase, that is, you need to have a 2-D or 3-D geometric grid 
of points and cells that is in a file format that ParaView can read.)

(2) Select the cell-variable "Material-Number" (or whatever name you 
supplied with the material data for the cells like MatID, MatNo, ...) 
For void or unknown material regions you can have two choices, a real 
low number (say, -999) and a real high number (say, 999)

(3) The default color bar will appear along with a panel named Color Map 
Editor. Button number #2 allows you to set the lower and upper color 
range values you want to use. Below the color map you have the option of 
selecting a color for below range data and a color for above-range data.

(4) As a last step, button #6 (a yellow folder icon overlaid with a red 
heart) lets you select the color bar you prefer. In your case, go to the 
very bottom of the Preset Color Scales where you will find a color scale 
named "blot" (The blot color scale is a set of, for want of a better 
word, distinct colors.) It is a historic color scale that was widely 
used in the early days of 2-D contour plotting where the contour levels 
were at the color boundaries.

Historically, if more than 7 contours were used, the color sequence 
repeated. I don't know what ParaView will do if you have more than six 
distinct geologic layers.

I could easily imagine that you could outgrow the above approach, but 
maybe it will help to get you started with ParaView.

Enjoy,

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


On 6/15/2016 7:36 AM, Steve Lamont wrote:
> Before starting, I should state that I'm a complete noob to ParaView, 
> having only worked with it for a couple of weeks, so if this is a FAQ, 
> I will be humbly abashed if pointed to somewhere rather obvious.
>
> I have a dataset which is somewhat different than those which I 
> believe are normally visualized with ParaView.  It is of geological 
> strata and the samples are of discrete layers, rather than samples of 
> some continuous function.  Furthermore, there are missing data or void 
> regions.
>
> I would like to display cross sections of these data showing the 
> layers without color interpolation.  Is there a way to tell ParaView 
> to display the colors in a step function rather than as a "continuous 
> tone?"
>
> Also, is there a way to tell ParaView to display the missing data as 
> completely transparent -- in other words, setting the NaN color to 
> having an opacity of zero?
>
> Thanks for your attention and helpful RTFMs.
>
> Regards.
>
>                             spl
>
> _______________________________________________
> 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 rdjamis at sandia.gov  Wed Jun 15 17:57:58 2016
From: rdjamis at sandia.gov (Jamison, Ryan Dale)
Date: Wed, 15 Jun 2016 21:57:58 +0000
Subject: [Paraview] [EXTERNAL]  Plot csv over time
In-Reply-To: <CADHSJjCBdrxx5JHV1dUUdDgkuqucNomVYX0q5S-ouxmu=GtdCQ@mail.gmail.com>
References: <0B5B1BD3-5DFE-4454-98B5-C8744B75D7C1@sandia.gov>
 <CADHSJjCBdrxx5JHV1dUUdDgkuqucNomVYX0q5S-ouxmu=GtdCQ@mail.gmail.com>
Message-ID: <CB9FB3C3-DE13-4B7E-95E6-DCE9EB9960CF@sandia.gov>

Thanks for the information. I think I almost got it but still have a question. I?m not able to plot the time vs. some other variable from the csv file.

In the ?Display (QuartileChartRepresentation)? I can select the ?X Array Name? to be any of the variables from the csv file, including time. When I select time, the green vertical time marker appears (this is good). The one thing that does not happen is that the ?Series Parameters? do not list any of the variables from the csv file. All that is listed are variables from the can.ex2. How can I plot two variables from the csv file?

I?ve included an image of what I?m seeing?

Thanks, Ryan

[cid:B829425F-DF76-4CCD-9A6F-FD6B62879FB3 at srn.sandia.gov]


On Jun 15, 2016, at 11:54 AM, Utkarsh Ayachit <utkarsh.ayachit at kitware.com<mailto:utkarsh.ayachit at kitware.com>> wrote:

The green line appears with the X axis is set to a data array named
"Time". See the attached state file. You'll can.ex2 (included in
ParaView Example Data) and the attached csv file to load the state.

On Wed, Jun 15, 2016 at 11:10 AM, Jamison, Ryan Dale <rdjamis at sandia.gov<mailto:rdjamis at sandia.gov>> wrote:
Hello,

I was wondering if there is a way to plot csv data over time? Specifically, I would like to read into an active Paraview session that already has some exodus results loaded a csv file (this I can already do). This csv file came from the same simulation as the exodus data. I?d like to then plot the csv results over time such that the green vertical line shows up denoting time as a video plays.

I?ve found I can use ?plot data? for the csv data and I can indeed plot time vs. variable but the green vertical line doesn?t appear. My theory is that the vertical time marker only appears when plotting something over time with the appropriate filter. Any idea how to get the time marker to appear in the plot?

Thanks, Ryan Jamison
_______________________________________________
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
<can0.csv><sample.pvsm>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160615/69845338/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: PastedGraphic-3.png
Type: image/png
Size: 137387 bytes
Desc: PastedGraphic-3.png
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160615/69845338/attachment-0001.png>

From mvanmoer at illinois.edu  Wed Jun 15 18:55:22 2016
From: mvanmoer at illinois.edu (Vanmoer, Mark W)
Date: Wed, 15 Jun 2016 22:55:22 +0000
Subject: [Paraview] [EXTERNAL] Re: Comparison of Visit and ParaView
 development
In-Reply-To: <825f253022ef40849ae26cb3f9e49d7d@ES01AMSNLNT.srn.sandia.gov>
References: <CAJZHu4RT7dek6wuyEWDDOL85m4kk58gnP8mgdM2-W2knZs7NgQ@mail.gmail.com>
 <CAE32kpXUPhmNGSYNqG0YkCRXJARv8jnvCjGvhkhQ7PiSVusEZA@mail.gmail.com>
 <825f253022ef40849ae26cb3f9e49d7d@ES01AMSNLNT.srn.sandia.gov>
Message-ID: <7F781841FF1E044388AFA42B70703A7AC36A5381@CHIMBX5.ad.uillinois.edu>

I use both VisIt and ParaView at NCSA regularly, depending upon what the teams I support are already using. If I have a free hand I generally pick ParaView because (1) I learned VTK first and it?s very straightforward to mentally map a VTK vis pipeline to ParaView and (2) I find the ParaView GUI more intuitive, which is not to be underestimated. Now that VisItBridge is available, I?m even able to get away with mixed projects (though those are rendering projects, not dev projects).

Both scale well in my experience and have for years. I?d like to hear more about what VisIt wasn?t able to scale in the past.

For in situ I have developed with both VisIt?s libsim2 and Catalyst and find Catalyst much easier. With libsim2, it seemed more like that the simulation code had to be shoehorned into VisIt, but maybe that?s been improved since I looked into it.

Both codebases are non-trivial. If you?re planning on developing in the primary codebase as opposed to writing plugins/operators/filters, I don?t think one would be markedly easier than the other.

The python API for ParaView is much more pythonic, IMO.

The downloadable VisIt user manual is for 1.5 and from 2005. Looking at the history in the developer wiki, some of the wiki pages are from 2008, so it?s not clear that its documentation is more up to date.

I don?t mean to bash VisIt, VisIt has some nice features: setting up interactive remote client-server jobs is a snap, the color map editor for volume rendering has easy to use Gaussian opacity transfer functions, you can do some interesting things with queries, etc.

I?ve found both mailing lists to be professional and responsive. I certainly don?t have any complaints about Kitware answering many of the questions, Alan is right, they know more! ?


From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Scott, W Alan
Sent: Wednesday, June 15, 2016 4:13 PM
To: Geveci, Berk (External Contact) <berk.geveci at kitware.com>; Sven Kramer <svenkramer40 at gmail.com>
Cc: ParaView <paraview at paraview.org>
Subject: Re: [Paraview] [EXTERNAL] Re: Comparison of Visit and ParaView development

I think Berk answered well from a technical and custom applications viewpoint.  Although not your primary question, I thought I would add just a few words regarding ParaView from a user?s perspective.

Here at Sandia National Laboratories, we have seen amazing growth of ParaView usage over the last decade.  Last year we had over 330 users.  Last month alone we had 161 individual users (not counting support or developers).  ParaView is used for projects ranging from toys (learning how to use ParaView with the can.exo dataset) to huge (a 100 million cell, 2048 file dataset with 204 timesteps).  It is being used on everything from interplanetary space probe research to visualizing wind turbines to climate change.  Catalyst is also part of ParaView development, and Catalyst is making a huge impact here at Sandia.

Regarding documentation, ParaView has come a long way in the last few years with regards to user documentation, and I would argue is now similar to commercial packages.  Further, the website has all of this information easily available.  The next version of ParaView (5.1) features an updated Help menu, providing easy access to the ParaView guide, and two full tutorials (the Supercomputing tutorial and the Sandia tutorial).
http://www.paraview.org/<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.paraview.org_&d=CwMGaQ&c=8hUWFZcy2Z-Za5rBPlktOQ&r=lLjWQse1m7sIE-wZm9lCGeCv45WZDxzY072HGbCi4Mg&m=Fk9FzrSbKPDpKCfLSdae3u20A7v10NbTnDTf9cgUpsQ&s=SAAzhkAwLgR023Hbff-s_Nnn2CD4yPAzsHNaxH31AQM&e=>
http://www.paraview.org/paraview-guide/<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.paraview.org_paraview-2Dguide_&d=CwMGaQ&c=8hUWFZcy2Z-Za5rBPlktOQ&r=lLjWQse1m7sIE-wZm9lCGeCv45WZDxzY072HGbCi4Mg&m=Fk9FzrSbKPDpKCfLSdae3u20A7v10NbTnDTf9cgUpsQ&s=JUMVwWUn5SZRNuzU_LQ18qbosbb-rQFXGETrmg0trTc&e=>
http://www.paraview.org/tutorials/<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.paraview.org_tutorials_&d=CwMGaQ&c=8hUWFZcy2Z-Za5rBPlktOQ&r=lLjWQse1m7sIE-wZm9lCGeCv45WZDxzY072HGbCi4Mg&m=Fk9FzrSbKPDpKCfLSdae3u20A7v10NbTnDTf9cgUpsQ&s=YBESG2Ue0IRJ6XxOPiFnUO7Vmz5DJkwlALOH4kmmbWA&e=>

You mention that Kitware appears to be the most active at answering the paraview.org list, and this is true.  I believe this is primarily because Kitware is by far the most knowledgeable, not because they are the only ones on the list.  Thus, you tend to hear from them first.

Regarding your primary question ? VisIt vs ParaView, I have no opinions, since I don?t know VisIt.

Alan



From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Berk Geveci
Sent: Wednesday, June 15, 2016 8:18 AM
To: Sven Kramer <svenkramer40 at gmail.com<mailto:svenkramer40 at gmail.com>>
Cc: ParaView <paraview at paraview.org<mailto:paraview at paraview.org>>
Subject: [EXTERNAL] Re: [Paraview] Comparison of Visit and ParaView development

I will leave it to the community to address some of these concerns since I am obviously biased.

However, Sven made some misguided and unfair statements and I would like to address those.

Books: Utkarsh & the ParaView community have put a lot of effort in developing a User's Guide for ParaView, which is excellent. This is a community developed effort, which is maintained very regularly and is available in print and download form in addition to the LaTeX source code. Yes, this is focused on users rather than developers but the same would be true for any visualization tool out there. In addition, we are in the process of open sourcing both VTK books, something which will take some effort because they need to be converted from Framemaker to LaTeX. The goal is to combine them in some way and open the development to the community. In addition, ParaView will soon leverage VTK-m for shared-memory parallel processing (http://m.vtk.org/<https://urldefense.proofpoint.com/v2/url?u=http-3A__m.vtk.org_&d=CwMGaQ&c=8hUWFZcy2Z-Za5rBPlktOQ&r=lLjWQse1m7sIE-wZm9lCGeCv45WZDxzY072HGbCi4Mg&m=Fk9FzrSbKPDpKCfLSdae3u20A7v10NbTnDTf9cgUpsQ&s=Gt3SCqqRBHKh9_fwCuJDZKzH1EG2_fbPpTYr3Rzpkjk&e=>) and we are developing two open source books for that.

Community: First of all, ParaView is a natural extension of VTK. Therefore, a lot of development happens at VTK level. I encourage everyone to take a look at the archives of the VTK mailing lists including the developer list. You will find a very vibrant community that goes well beyond Kitware there. In fact, we are a minority on those lists very often. There are well over 50 developers who have contributed to VTK over the last few years, from academia, industry and government. Almost all algorithmic work is done in VTK. It is true that most of the ParaView application is developed by folks at Kitware. Only a few folks from the ParaView development team regularly responds to the mailing lists (kudos to them). Our team is now 43 people about 20 of whom are focused on VTK and ParaView development.

Applications: There are a number of ParaView based applications out there, clearly demonstrating ParaView as a viable application platform. Not counting VTK based applications because there are too many of those to list here.

* Tomviz: http://www.tomviz.org/<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.tomviz.org_&d=CwMGaQ&c=8hUWFZcy2Z-Za5rBPlktOQ&r=lLjWQse1m7sIE-wZm9lCGeCv45WZDxzY072HGbCi4Mg&m=Fk9FzrSbKPDpKCfLSdae3u20A7v10NbTnDTf9cgUpsQ&s=3KY60D4eDhxAb0vCc7bq8-6cDRwwyayhk6UFKIezQzE&e=>
* CMB: http://www.computationalmodelbuilder.org/<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.computationalmodelbuilder.org_&d=CwMGaQ&c=8hUWFZcy2Z-Za5rBPlktOQ&r=lLjWQse1m7sIE-wZm9lCGeCv45WZDxzY072HGbCi4Mg&m=Fk9FzrSbKPDpKCfLSdae3u20A7v10NbTnDTf9cgUpsQ&s=Zg88rgnlu_l7IfCtARJDItW1JqVmL_nTvr-fyfuSlQE&e=>
* VeloView: http://www.paraview.org/veloview/<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.paraview.org_veloview_&d=CwMGaQ&c=8hUWFZcy2Z-Za5rBPlktOQ&r=lLjWQse1m7sIE-wZm9lCGeCv45WZDxzY072HGbCi4Mg&m=Fk9FzrSbKPDpKCfLSdae3u20A7v10NbTnDTf9cgUpsQ&s=o6h4oemSxG7pY2OW8rP4kR65agxQ9kvd8htsyeRozEA&e=>
* Mantid 3D viewer: http://www.mantidproject.org/<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.mantidproject.org_&d=CwMGaQ&c=8hUWFZcy2Z-Za5rBPlktOQ&r=lLjWQse1m7sIE-wZm9lCGeCv45WZDxzY072HGbCi4Mg&m=Fk9FzrSbKPDpKCfLSdae3u20A7v10NbTnDTf9cgUpsQ&s=dn0S-qxIgeHWGNAndivz8NTZ9ukbiEWlWhlVSqF5D_w&e=>

In addition to a number of commercial cloud based platforms based on ParaViewWeb such as SimScale (https://www.simscale.com/<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.simscale.com_&d=CwMGaQ&c=8hUWFZcy2Z-Za5rBPlktOQ&r=lLjWQse1m7sIE-wZm9lCGeCv45WZDxzY072HGbCi4Mg&m=Fk9FzrSbKPDpKCfLSdae3u20A7v10NbTnDTf9cgUpsQ&s=3AW8FukzHiAC9Q9ubbOteGC5fRiiFUbmMuwEGueYKz8&e=>). Some of these are developed at Kitware but some of the have been almost entirely developed without very little help from us.

Features: There are a lot of huge features that are making their way into ParaView. To be fair, these will also make their way into VisIt because they come from VTK so these are really not differentiators between the two. The two major ones are the new rendering engine including the use of much more modern OpenGL features with huge performance increase and a focus on next generation architectures such as GPUs and Xeon Phis though the development of VTK-m. In addition, we have a strong focus on in situ analysis through the development of Catalyst, which I would argue is the premier in situ library with lots of advanced features not available anywhere else. Something we demonstrated working very well on 1 million MPI ranks on the Argonne Blue Gene (Mira). Other more research focused areas such as Cinema (http://cinemascience.org/<https://urldefense.proofpoint.com/v2/url?u=http-3A__cinemascience.org_&d=CwMGaQ&c=8hUWFZcy2Z-Za5rBPlktOQ&r=lLjWQse1m7sIE-wZm9lCGeCv45WZDxzY072HGbCi4Mg&m=Fk9FzrSbKPDpKCfLSdae3u20A7v10NbTnDTf9cgUpsQ&s=tQ1IQkvZg4OA-e-tH9n6SgrrSPZxDOo9BLO51ADVS0M&e=>) are being pushed in VTK/ParaView/Catalyst quite heavily right now. All of these focus on exascale computing, which is US Department of Energy push right now.

Issues with ParaView as a development platform:

* It is true that our developer documentation is lacking. ParaView as a development platform has never been the main driver so making it more accessible to the larger community is something that has not been pushed as much as we would like. Not true for VTK though.

* The ParaView code architecture is fairly complicated. This is because it has evolved to address the needs of various kinds of applications. A much broader set of needs that tools like VisIt tend to focus on. This is because our community targets more than HPC Visualization, which were the original drivers for both VisIt and ParaView. The kind of applications I listed above is a good demonstration of this.

I believe that the main differentiator between ParaView and other vis tools out there is the broad functionality _and_ the code quality. Having the two together is really tough but our community managed this with a heavy emphasis on code review and code testing. I strongly recommend that folks look at the software processes used to develop VTK & ParaView as well as the huge amount of testing (both test quantity and platform coverage) that we do before every single commit in addition to nightly. There is a very good overlap between the CMake, CTest & CDash communities and the VTK/ParaView development communities and there is very good reason behind this.

Best,
-berk


On Wed, Jun 15, 2016 at 6:54 AM, Sven Kramer <svenkramer40 at gmail.com<mailto:svenkramer40 at gmail.com>> wrote:
Dear ParaView programmers,
I would like to have some opinions on the suitability of either ParaView or Visit for large scalable visualization applications. When I had the first contact to visualization more than 5 years ago, Visit was not quite scalable and ParaView seemed the only open source alternative.
Now I am trying to get into some serious developments, and although most papers in the field still cite ParaView as their development framework, there seems to be no active developers community except for two or three kitware employees. Questions on this list are at the most basic level, and nobody seems to be able to answer, who isn't working for kitware.
My impression is that ParaView has grown so complicated over the years that it is no longer usable as a framework for parallel visualization development. Only the ParaView application itself is still frequently used.
On the other hand, Visit seems to have overtaken ParaView in all aspects. Most important is the high quality documentation and very active community, scalability is now as good as ParaView, and collaborative web visualization is coming rapidly.
What is your opinion? Are there any points, where ParaView is clearly advantageous over Visit? Or is it used by most people only out of convenience, because they have always worked with ParaView?
Given the horribly out of date books on ParaView and parallel VTK development, web documentation mixing three major versions without stating which version is referred to, and the dead development discussions I don't see any possibility of learning ParaView programming today. Which material do you use for tutorials and documentation?
Thank you
Sven

_______________________________________________
Powered by www.kitware.com<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.kitware.com&d=CwMGaQ&c=8hUWFZcy2Z-Za5rBPlktOQ&r=lLjWQse1m7sIE-wZm9lCGeCv45WZDxzY072HGbCi4Mg&m=Fk9FzrSbKPDpKCfLSdae3u20A7v10NbTnDTf9cgUpsQ&s=yCiIJBhE_L7jsX3g6j7UDbFYnl2N-YTNH_zsSC1wIQc&e=>

Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.kitware.com_opensource_opensource.html&d=CwMGaQ&c=8hUWFZcy2Z-Za5rBPlktOQ&r=lLjWQse1m7sIE-wZm9lCGeCv45WZDxzY072HGbCi4Mg&m=Fk9FzrSbKPDpKCfLSdae3u20A7v10NbTnDTf9cgUpsQ&s=cifwbbW13A85aFipcFjJMGjy_U5BDaClUrRCliM-ld4&e=>

Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView<https://urldefense.proofpoint.com/v2/url?u=http-3A__paraview.org_Wiki_ParaView&d=CwMGaQ&c=8hUWFZcy2Z-Za5rBPlktOQ&r=lLjWQse1m7sIE-wZm9lCGeCv45WZDxzY072HGbCi4Mg&m=Fk9FzrSbKPDpKCfLSdae3u20A7v10NbTnDTf9cgUpsQ&s=6kw0TUb4QE0eeIs7sPZU9wmNKrZr-RWrGcFGWhwpEQk&e=>

Search the list archives at: http://markmail.org/search/?q=ParaView<https://urldefense.proofpoint.com/v2/url?u=http-3A__markmail.org_search_-3Fq-3DParaView&d=CwMGaQ&c=8hUWFZcy2Z-Za5rBPlktOQ&r=lLjWQse1m7sIE-wZm9lCGeCv45WZDxzY072HGbCi4Mg&m=Fk9FzrSbKPDpKCfLSdae3u20A7v10NbTnDTf9cgUpsQ&s=_TK0t8tj3NdhAim4oJg1T6CGFfc-XG51PNWeOQPr41k&e=>

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview<https://urldefense.proofpoint.com/v2/url?u=http-3A__public.kitware.com_mailman_listinfo_paraview&d=CwMGaQ&c=8hUWFZcy2Z-Za5rBPlktOQ&r=lLjWQse1m7sIE-wZm9lCGeCv45WZDxzY072HGbCi4Mg&m=Fk9FzrSbKPDpKCfLSdae3u20A7v10NbTnDTf9cgUpsQ&s=zko__e7dzS0b-b3NRk4BK_pegurpzfB81BXVFeP3M8o&e=>

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

From guilfordstuff at gmail.com  Wed Jun 15 22:10:18 2016
From: guilfordstuff at gmail.com (Jim)
Date: Wed, 15 Jun 2016 22:10:18 -0400
Subject: [Paraview] Questions on Paraview with 3D vector fields
Message-ID: <57620A8A.4000908@gmail.com>

Hello All:

I'm working with 3D vector fields (2 of them in the same space) and want 
to do a fly through, set the center to be one of the arrow glyphs, and 
do some calculations on both fields using the calculator. I can't seem 
to do any of these. Any ideas?

It looks like the center selection was designed to work with polymeshes. 
The arrow glyphs just can't be selected. Is there any way to fake out 
Paraview and place something that the selector can see?

I saw fly through mentioned on some forum but no solution. I can place a 
line into my space. Is there some way to use the line as a camera path? 
I'm really interested in fly throughs in the program, not watching them 
as a movie. There's just too many things to change to make it a movie 
and not take forever to make/look at them.

The calculator looks like it only hooks up to one vector field at a 
time. Is there some object linking trick or running one field through an 
intermediate calculation that would make both fields visible to the 
calculator?

Any help appreciated.

-J





From paul.melis at surfsara.nl  Thu Jun 16 04:52:21 2016
From: paul.melis at surfsara.nl (Paul Melis)
Date: Thu, 16 Jun 2016 10:52:21 +0200
Subject: [Paraview] Comparison of Visit and ParaView development
In-Reply-To: <CAE32kpXUPhmNGSYNqG0YkCRXJARv8jnvCjGvhkhQ7PiSVusEZA@mail.gmail.com>
References: <CAJZHu4RT7dek6wuyEWDDOL85m4kk58gnP8mgdM2-W2knZs7NgQ@mail.gmail.com>
 <CAE32kpXUPhmNGSYNqG0YkCRXJARv8jnvCjGvhkhQ7PiSVusEZA@mail.gmail.com>
Message-ID: <82e5e4df-999a-d8a4-0d75-8a91195922bb@surfsara.nl>

Hi,

On 15-06-16 16:18, Berk Geveci wrote:
> I believe that the main differentiator between ParaView and other vis
> tools out there is the broad functionality _and_ the code quality.
> Having the two together is really tough but our community managed this
> with a heavy emphasis on code review and code testing. I strongly
> recommend that folks look at the software processes used to develop VTK
> & ParaView as well as the huge amount of testing (both test quantity and
> platform coverage) that we do before every single commit in addition to
> nightly. There is a very good overlap between the CMake, CTest & CDash
> communities and the VTK/ParaView development communities and there is
> very good reason behind this.

Slightly off-topic (not fully about ParaView vs VisIt), but I always 
wondered about the development process of VTK/ParaView with respect to 
bug reports. There seem to be a huge number of reported bugs for 
ParaView (and a few for VTK), ranging from crashes to incorrect 
functionality to feature requests. Over the years I have entered more 
than two dozen myself, but was always surprised about the lack of 
response, especially when reporting things that were easily reproducible 
and/or crasher bugs (e.g. VTK #10528, ParaView #15291, ParaView #15944, 
ParaView #13802).

Now, I understand that what's not working for me might not be important 
to others, so, of course, assigning priorty and doing actual fixes for 
reports is done by the developer community. A second "handicap" in this 
respect is undoubtedly the fact that KitWare is a business and so has 
different priorities than a bunch of hackers working mostly in their 
spare time on their pet project.

But basically anything reported these days immediately gets status 
"backlog" and I would guesstimate getting a response to a report only 
about 25% of the time. I report bugs quite often for other open-source 
projects (and try to enter concise reports with a testcase), but with 
ParaView/VTK I get the feeling it's not worth the trouble, which is a 
shame. Actually getting back on topic: the one or two times I reported a 
bug in VisIt I got a reply and fix quickly!

Furthermore, ParaView seems quite easy to segfault and it happens even 
with moderately complex pipelines and modest datasets. Parallel volume 
rendering has been broken for ages (or is it fixed these days? Can't 
tell, ParaView #13801 did not get any replies). Some examples shown on 
the wiki cause Python errors (e.g. #15291, #12796). And so on.

So the comment above about code quality making ParaView stand out from 
other visualization tools is a bit a stretch in my opinion. I would 
certainly not call ParaView "stable". In fact, in the introductory 
scivis courses we teach with ParaView we always warn people that crashes 
are to be expected regularly and even during the course assignments they 
sometimes happen.

The development process as mentioned by Berk is indeed impressive, but 
seems mostly focused on preventing regressions in existing 
functionality. This is a worthy goal in itself, but is only one half of 
the story when it comes to guaranteeing code quality. The things that 
aren't working (see bug reports) are maybe not getting the attention 
they deserve, but are apparently things folks run into when using 
ParaView, so they signal something real.

After the stuff above I wanted to finish on a less critical note :) I 
prefer using ParaView over VisIt mostly because of being able to build a 
pipeline and prefer ParaView's nice single-window GUI over VisIt's 
a-window-here-a-window-there-a-window-everywhere approach. They are both 
good and useful tools and are work-horses for scivis tasks. Whenever I 
get a request from an HPC user which one to use I recommend ParaView, as 
it is easier to get into for basic scivis work.

Regards,
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  Thu Jun 16 09:23:06 2016
From: Mandar.Shirke at infosys.com (Mandar Prakash Shirke)
Date: Thu, 16 Jun 2016 13:23:06 +0000
Subject: [Paraview] Error in Launching Paraview 5.0.0
Message-ID: <BBF23853DD0BE54FB8F0F12A6F06A1DA49001D9D@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 01D1C800.50D16370]

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/20160616/8ed03e11/attachment.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/20160616/8ed03e11/attachment.png>

From shawn.waldon at kitware.com  Thu Jun 16 09:32:48 2016
From: shawn.waldon at kitware.com (Shawn Waldon)
Date: Thu, 16 Jun 2016 09:32:48 -0400
Subject: [Paraview] Error in Launching Paraview 5.0.0
In-Reply-To: <BBF23853DD0BE54FB8F0F12A6F06A1DA49001D9D@blrkecmbx15.ad.infosys.com>
References: <BBF23853DD0BE54FB8F0F12A6F06A1DA49001D9D@blrkecmbx15.ad.infosys.com>
Message-ID: <CALSpCT3ojaaw+y_0BDY_TP2Gwq-4+3638oPVc1pjni+PCEzhHQ@mail.gmail.com>

Hi Mandar,

I'm not 100% sure, but I suspect that what is going on is this:  ParaView
5.0 was updated to require a much newer version of OpenGL, so your graphics
hardware and/or drivers may need to be updated.  In 5.0.0, this causes a
crash like this since trying to create the OpenGL context fails.  One of
the fixes in ParaView 5.0.1 was that it checks your OpenGL version first
and if ParaView can't run with that version it gives you a nice error
message.  I would recommend trying with 5.0.1 to see if this is indeed the
problem.  Then if it is, you will need to figure out how to get your
computer to supports an OpenGL version >= 3.2 or build ParaView from source
with the older OpenGL1 rendering backend.

HTH,
Shawn

On Thu, Jun 16, 2016 at 9:23 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
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160616/4a9b8b7e/attachment-0001.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/20160616/4a9b8b7e/attachment-0001.png>

From utkarsh.ayachit at kitware.com  Thu Jun 16 09:46:58 2016
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Thu, 16 Jun 2016 09:46:58 -0400
Subject: [Paraview] Comparison of Visit and ParaView development
In-Reply-To: <82e5e4df-999a-d8a4-0d75-8a91195922bb@surfsara.nl>
References: <CAJZHu4RT7dek6wuyEWDDOL85m4kk58gnP8mgdM2-W2knZs7NgQ@mail.gmail.com>
 <CAE32kpXUPhmNGSYNqG0YkCRXJARv8jnvCjGvhkhQ7PiSVusEZA@mail.gmail.com>
 <82e5e4df-999a-d8a4-0d75-8a91195922bb@surfsara.nl>
Message-ID: <CADHSJjCkZS2Gnk9go535RAewxUFKSpCgn5v8=SwLe+NwH2h8_A@mail.gmail.com>

> but I always wondered about the development process of VTK/ParaView with respect to bug
> reports. There seem to be a huge number of reported bugs for ParaView (and a
> few for VTK), ranging from crashes to incorrect functionality to feature
> requests.

Bugs often get prioritized by several of the customers/community
members that drive the development of ParaView. While several others
get fixed as developers notice them. As you said, bug trackers does
accumulate several reports. Hence it's good to make some noise on the
mailing list to get some attention when you report a bug, for example.
While we do endeavour to monitor the bug tracker, in practice it's
hard to stay on top of it and things can easily slip down the cracks.
For example, I don't think I ever even saw the bugs you mention.
Several were indeed easily answerable.

> A second "handicap" in this respect is
> undoubtedly the fact that KitWare is a business and so has different
> priorities than a bunch of hackers working mostly in their spare time on
> their pet project.

Sure, Kitware is a business, but not most of us here are driven by the
open source ideals and everything that it brings -- community, greater
good etc. etc. Many of us do respond in our spare or personal time
just because we enjoy it -- when we could very easily be simply
catching up on the latest Game of Thrones gossip :). Of course, life
is always less than ideal and deadlines and requirements of ongoing
projects often dictate how things get prioritized, but that doesn't
mean we are any less driven. At the same time, these are community
projects. Community members using ParaView and developing with it are
encouraged to take over bugs, ask for assistance on how to track them,
as needed. Everyone will only be glad to help. We've even made it
easier with Gitlab to get community changes reviewed and tested and
merged. There have been a few new folks contributing since that
happened -- kudos to them -- but just looking at the kinds of
questions we answer on the mailing list, there are clearly a lot more
people with the know how out there who just don't contribute back.

> But basically anything reported these days immediately gets status "backlog"

"backlog" is just the default state.

> Furthermore, ParaView seems quite easy to segfault and it happens even with
> moderately complex pipelines and modest datasets. Parallel volume rendering
> has been broken for ages

There have been quite a few recent announcements that went into
revamping the volume rendering code.
https://blog.kitware.com/paraview-5-0-1-release-notes/
https://blog.kitware.com/volume-rendering-enhancements-in-vtk/
https://blog.kitware.com/paraview-5-0-0-rc1-available-for-download/

> So the comment above about code quality making ParaView stand out from other
> visualization tools is a bit a stretch in my opinion. I would certainly not
> call ParaView "stable". In fact, in the introductory scivis courses we teach
> with ParaView we always warn people that crashes are to be expected
> regularly and even during the course assignments they sometimes happen.

Please do report issues with information on how to reproduce them. The
whole team including members from outside Kitware, like Alan Scott
from Sandia and others work tirelessly to keep things stable. But
note, ParaView is also constantly pushing the envelope. There are
always a hoard of new features being added to support new usecases.
That does mean more opportunities to make mistakes. Thankfully,
several community members already help out a lot with testing and
making sure things continue to work, so the picture is really not that
bleak. There are community members ensuring things build and deploy on
esoteric HPC systems we don't have access to, there are folks
deploying on various linux distributions and working with us to
address any issues, the list goes on and on!

The moral of the story is: just speak up and grab someone's attention,
and if that fails, just grab your coding toolbox and dive in -- how
bad can it be :)!

Utkarsh

From Mandar.Shirke at infosys.com  Thu Jun 16 10:01:08 2016
From: Mandar.Shirke at infosys.com (Mandar Prakash Shirke)
Date: Thu, 16 Jun 2016 14:01:08 +0000
Subject: [Paraview] Error in Launching Paraview 5.0.0
In-Reply-To: <CALSpCT3ojaaw+y_0BDY_TP2Gwq-4+3638oPVc1pjni+PCEzhHQ@mail.gmail.com>
References: <BBF23853DD0BE54FB8F0F12A6F06A1DA49001D9D@blrkecmbx15.ad.infosys.com>
 <CALSpCT3ojaaw+y_0BDY_TP2Gwq-4+3638oPVc1pjni+PCEzhHQ@mail.gmail.com>
Message-ID: <BBF23853DD0BE54FB8F0F12A6F06A1DA49001DED@blrkecmbx15.ad.infosys.com>

Hello Shawn,

Thank you for replying.
I tried installing ParaView 5.0.1 but I received same error message.

Regards,
Mandar

From: Shawn Waldon [mailto:shawn.waldon at kitware.com]
Sent: Thursday, June 16, 2016 7:03 PM
To: Mandar Prakash Shirke <Mandar.Shirke at infosys.com>
Cc: paraview at paraview.org
Subject: Re: [Paraview] Error in Launching Paraview 5.0.0

Hi Mandar,
I'm not 100% sure, but I suspect that what is going on is this:  ParaView 5.0 was updated to require a much newer version of OpenGL, so your graphics hardware and/or drivers may need to be updated.  In 5.0.0, this causes a crash like this since trying to create the OpenGL context fails.  One of the fixes in ParaView 5.0.1 was that it checks your OpenGL version first and if ParaView can't run with that version it gives you a nice error message.  I would recommend trying with 5.0.1 to see if this is indeed the problem.  Then if it is, you will need to figure out how to get your computer to supports an OpenGL version >= 3.2 or build ParaView from source with the older OpenGL1 rendering backend.
HTH,
Shawn

On Thu, Jun 16, 2016 at 9:23 AM, Mandar Prakash Shirke <Mandar.Shirke at infosys.com<mailto: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 01D1C805.A0C2D5D0]

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<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/20160616/6b3e2c0e/attachment.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/20160616/6b3e2c0e/attachment.png>

From utkarsh.ayachit at kitware.com  Thu Jun 16 11:19:57 2016
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Thu, 16 Jun 2016 11:19:57 -0400
Subject: [Paraview] Error in Launching Paraview 5.0.0
In-Reply-To: <BBF23853DD0BE54FB8F0F12A6F06A1DA49001DED@blrkecmbx15.ad.infosys.com>
References: <BBF23853DD0BE54FB8F0F12A6F06A1DA49001D9D@blrkecmbx15.ad.infosys.com>
 <CALSpCT3ojaaw+y_0BDY_TP2Gwq-4+3638oPVc1pjni+PCEzhHQ@mail.gmail.com>
 <BBF23853DD0BE54FB8F0F12A6F06A1DA49001DED@blrkecmbx15.ad.infosys.com>
Message-ID: <CADHSJjD740U4mh7h5st9eg_FR2u-j5fKpXg5YrAabxCmfpvLCA@mail.gmail.com>

Try ParaView 4.4. If that works than it's indeed an OpenGL driver issue.
You may have to update your drivers.

On Thu, Jun 16, 2016 at 10:01 AM, Mandar Prakash Shirke <
Mandar.Shirke at infosys.com> wrote:

> Hello Shawn,
>
>
>
> Thank you for replying.
>
> I tried installing ParaView 5.0.1 but I received same error message.
>
>
>
> Regards,
>
> Mandar
>
>
>
> *From:* Shawn Waldon [mailto:shawn.waldon at kitware.com]
> *Sent:* Thursday, June 16, 2016 7:03 PM
> *To:* Mandar Prakash Shirke <Mandar.Shirke at infosys.com>
> *Cc:* paraview at paraview.org
> *Subject:* Re: [Paraview] Error in Launching Paraview 5.0.0
>
>
>
> Hi Mandar,
>
> I'm not 100% sure, but I suspect that what is going on is this:  ParaView
> 5.0 was updated to require a much newer version of OpenGL, so your graphics
> hardware and/or drivers may need to be updated.  In 5.0.0, this causes a
> crash like this since trying to create the OpenGL context fails.  One of
> the fixes in ParaView 5.0.1 was that it checks your OpenGL version first
> and if ParaView can't run with that version it gives you a nice error
> message.  I would recommend trying with 5.0.1 to see if this is indeed the
> problem.  Then if it is, you will need to figure out how to get your
> computer to supports an OpenGL version >= 3.2 or build ParaView from source
> with the older OpenGL1 rendering backend.
>
> HTH,
>
> Shawn
>
>
>
> On Thu, Jun 16, 2016 at 9:23 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
>
>
>
> _______________________________________________
> 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/20160616/942938d8/attachment-0001.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/20160616/942938d8/attachment-0001.png>

From peterdebuchev at gmail.com  Thu Jun 16 12:47:27 2016
From: peterdebuchev at gmail.com (Peter Debuchev)
Date: Thu, 16 Jun 2016 18:47:27 +0200
Subject: [Paraview] Can a collaborative client share a pipeline without
	creating a view itself?
Message-ID: <CAAUk9C7zY8P25QWDeZdcCA7Vx18uiBBe_+_LbyepsFt8FUQaGA@mail.gmail.com>

Hello again,
I have a follow-up question concerning my attempts to create a
collaborative standalone client. The attached example connects to a
pvserver running on localhost (with --multi-clients option) and creates a
SphereSource together with its representation. Depending on whether
"USEVIEW" is defined or undefined in the beginning, also a RenderView is
created and shows the sphere.

The plan is that other clients can pick up and display the created
pipeline. Unfortunately this doesn't work if the example code doesn't
create a RenderView by itself. Maybe my understanding is wrong, but isn't
it sufficient if a client creates sources and their representations so that
other clients can display these in their views? Moreover, the behaviour
depends on the order in which the example client and the ParaView client
are started.

This is a more structured summary of the different test "modes":

If I compile the example with "USEVIEW" defined in the beginning,
a) Starting in the order pvserver->example->ParaView, ParaView reports
"This code may not work in multi-clients mode. Could not locate server on
which the source is being added." and shows the sphere in the renderer, but
not in the pipeline panel.
b) Starting in the order pvserver->ParaView->example, everything works as
expected.

If I undefine "USEVIEW" in the beginning, it is not quite running as
expected:
c) Starting in the order pvserver->example->ParaView, ParaView reports
"Could not locate server on which the source is being added." and shows
nothing.
d) Starting in the order pvserver->ParaView->example, ParaView shows "Sph1"
in the pipeline panel, but nothing in the renderer.

Why does the Sphere not show up in ParaView's pipeline panel in case a)?
Why does the Sphere show up in ParaView's pipeline panel, but not in the
renderer in case d)?
And what does "This code may not work in multi-clients mode" and "Could not
locate server on which the source is being added" exactly wnat to tell me?

If you could share any answers to one or more of these questions or suggest
what else to try, it'll be highly appreciated.

Peter
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160616/02f79877/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: main.cxx
Type: text/x-c++src
Size: 3374 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160616/02f79877/attachment.cxx>

From wascott at sandia.gov  Thu Jun 16 13:06:47 2016
From: wascott at sandia.gov (Scott, W Alan)
Date: Thu, 16 Jun 2016 17:06:47 +0000
Subject: [Paraview] [EXTERNAL] Re: Comparison of Visit and ParaView
 development
In-Reply-To: <82e5e4df-999a-d8a4-0d75-8a91195922bb@surfsara.nl>
References: <CAJZHu4RT7dek6wuyEWDDOL85m4kk58gnP8mgdM2-W2knZs7NgQ@mail.gmail.com>
 <CAE32kpXUPhmNGSYNqG0YkCRXJARv8jnvCjGvhkhQ7PiSVusEZA@mail.gmail.com>
 <82e5e4df-999a-d8a4-0d75-8a91195922bb@surfsara.nl>
Message-ID: <3902be902af94a2ab7c02e73ba3303cf@ES01AMSNLNT.srn.sandia.gov>

Paul,
I looked at a few of the bugs listed below.  

I replicated 15944, this would impact my users.  It's on Sandia's list.  

13802 works correctly on 5.0.1.  Note that you are creating 2.6 billion cells, and from what I can tell, you are running out of memory on your server side.  I was able to get this to work with 8 nodes of a cluster.  Try running the View/ Memory Inspector, it will tell you how much pressure you are putting on your memory.

Alan



-----Original Message-----
From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Paul Melis
Sent: Thursday, June 16, 2016 2:52 AM
To: Geveci, Berk (External Contact) <berk.geveci at kitware.com>; Sven Kramer <svenkramer40 at gmail.com>
Cc: ParaView <paraview at paraview.org>
Subject: [EXTERNAL] Re: [Paraview] Comparison of Visit and ParaView development

Hi,

On 15-06-16 16:18, Berk Geveci wrote:
> I believe that the main differentiator between ParaView and other vis 
> tools out there is the broad functionality _and_ the code quality.
> Having the two together is really tough but our community managed this 
> with a heavy emphasis on code review and code testing. I strongly 
> recommend that folks look at the software processes used to develop 
> VTK & ParaView as well as the huge amount of testing (both test 
> quantity and platform coverage) that we do before every single commit 
> in addition to nightly. There is a very good overlap between the 
> CMake, CTest & CDash communities and the VTK/ParaView development 
> communities and there is very good reason behind this.

Slightly off-topic (not fully about ParaView vs VisIt), but I always wondered about the development process of VTK/ParaView with respect to bug reports. There seem to be a huge number of reported bugs for ParaView (and a few for VTK), ranging from crashes to incorrect functionality to feature requests. Over the years I have entered more than two dozen myself, but was always surprised about the lack of response, especially when reporting things that were easily reproducible and/or crasher bugs (e.g. VTK #10528, ParaView #15291, ParaView #15944, ParaView #13802).

Now, I understand that what's not working for me might not be important to others, so, of course, assigning priorty and doing actual fixes for reports is done by the developer community. A second "handicap" in this respect is undoubtedly the fact that KitWare is a business and so has different priorities than a bunch of hackers working mostly in their spare time on their pet project.

But basically anything reported these days immediately gets status "backlog" and I would guesstimate getting a response to a report only about 25% of the time. I report bugs quite often for other open-source projects (and try to enter concise reports with a testcase), but with ParaView/VTK I get the feeling it's not worth the trouble, which is a shame. Actually getting back on topic: the one or two times I reported a bug in VisIt I got a reply and fix quickly!

Furthermore, ParaView seems quite easy to segfault and it happens even with moderately complex pipelines and modest datasets. Parallel volume rendering has been broken for ages (or is it fixed these days? Can't tell, ParaView #13801 did not get any replies). Some examples shown on the wiki cause Python errors (e.g. #15291, #12796). And so on.

So the comment above about code quality making ParaView stand out from other visualization tools is a bit a stretch in my opinion. I would certainly not call ParaView "stable". In fact, in the introductory scivis courses we teach with ParaView we always warn people that crashes are to be expected regularly and even during the course assignments they sometimes happen.

The development process as mentioned by Berk is indeed impressive, but seems mostly focused on preventing regressions in existing functionality. This is a worthy goal in itself, but is only one half of the story when it comes to guaranteeing code quality. The things that aren't working (see bug reports) are maybe not getting the attention they deserve, but are apparently things folks run into when using ParaView, so they signal something real.

After the stuff above I wanted to finish on a less critical note :) I prefer using ParaView over VisIt mostly because of being able to build a pipeline and prefer ParaView's nice single-window GUI over VisIt's a-window-here-a-window-there-a-window-everywhere approach. They are both good and useful tools and are work-horses for scivis tasks. Whenever I get a request from an HPC user which one to use I recommend ParaView, as it is easier to get into for basic scivis work.

Regards,
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 |
_______________________________________________
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 berk.geveci at kitware.com  Thu Jun 16 15:04:31 2016
From: berk.geveci at kitware.com (Berk Geveci)
Date: Thu, 16 Jun 2016 15:04:31 -0400
Subject: [Paraview] SC16 Visualization Showcase submission deadline - July
	31, 2016
Message-ID: <CAE32kpWJMW+bGzf5=83KLBiOZKRv=7Zyw+4xLKp-DzopcYqctA@mail.gmail.com>

Visualization Showcase
------------------------------

Important Dates:
February 16, 2016: *Submissions open*
July 31, 2016: *Submissions deadline*
September 1, 2016: *Notifications sent*
------------------------------

*A new format for 2016!*

SC16?s Visualization and Data Analytics Showcase Program provides a forum
for the year?s most instrumental movies in HPC. This year, there will be
both a live display throughout the conference so that attendees can
experience and enjoy the latest in science and engineering HPC results
expressed through state-of-the-art visualization technologies, and a
session at SC16 dedicated to the best of the submissions.

Selected entries will be displayed live in a museum/art gallery format and
six finalists will compete for the Best Visualization Award, with each
finalist presenting his or her movie in a 15-minute presentation.

Movies are judged based on how their movie illuminates science, by the
quality of the movie, and for innovations in the process used for creating
the movie.

The six finalist submissions will appear as short papers on the SC16
webpage and archive.

*Review and selection process:*

Submissions need to include a movie (up to 250MB in size) and a short paper
(up to 4 pages including references). The short paper should describe the
scientific story conveyed by the movie, how the visualization helps
scientific discovery, and the ?state-of-the-practice? information (
ieeevis.org)information behind making the movie.

Each submission will be peer reviewed by the Visualization and Data
Analytics Showcase Committee. Criteria for review include:

   - How effective is the visual communication of the data?
   - How relevant to the HPC community is the visualization?
   - What is the impact of the science story and how well is it told?
   - What visualization techniques were necessary to create the movie?

Finally, submissions should support SC16?s overall theme ?HPC matters.?
http://sc16.supercomputing.org/submitters/showcases/scientific-visualization-showcase/

*Web Submissions:* https://submissions.supercomputing.org/

*Email Contact:* vis_showcase at info.supercomputing.org

SC16 Visualization Showcase Chair
Chris Johnson, University of Utah

SC16 Visualization Showcase Vice Chair
Kristin Potter, University of Oregon
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160616/0ec3610c/attachment.html>

From utkarsh.ayachit at kitware.com  Thu Jun 16 15:41:55 2016
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Thu, 16 Jun 2016 15:41:55 -0400
Subject: [Paraview] Can a collaborative client share a pipeline without
 creating a view itself?
In-Reply-To: <CAAUk9C7zY8P25QWDeZdcCA7Vx18uiBBe_+_LbyepsFt8FUQaGA@mail.gmail.com>
References: <CAAUk9C7zY8P25QWDeZdcCA7Vx18uiBBe_+_LbyepsFt8FUQaGA@mail.gmail.com>
Message-ID: <CADHSJjAj5of=VckLN=VCe5KoHhaPqzYck79u=kGLpfrtO3856Q@mail.gmail.com>

Peter,

In ParaView's collaboration support there's the notion of a master and
everyone else. The first client that connects to the pvserver is the
"master" by default. The master is the only one that should create new
proxies. This doesn't preclude the other clients from not creating new
proxies, but if they do, things start acting funny. Also all client
have exactly the same views as the proxy. They can be showing a
different camera, but not have different number of views or types of
views etc.

> If I compile the example with "USEVIEW" defined in the beginning,
> a) Starting in the order pvserver->example->ParaView, ParaView reports "This
> code may not work in multi-clients mode. Could not locate server on which
> the source is being added." and shows the sphere in the renderer, but not in
> the pipeline panel.

There seems to be a bug where the ParaView client has trouble loading
existing state from another client. It seems to work as expected if
the "master" starts creating sphere etc. after the other client has
connected.

> c) Starting in the order pvserver->example->ParaView, ParaView reports
> "Could not locate server on which the source is being added." and shows
> nothing.

Same issue as (a).

> d) Starting in the order pvserver->ParaView->example, ParaView shows "Sph1"
> in the pipeline panel, but nothing in the renderer.

In this case your non-master example has created a view which is not supported.

> Why does the Sphere not show up in ParaView's pipeline panel in case a)?

A bug in loading initial collaboration state.

> Why does the Sphere show up in ParaView's pipeline panel, but not in the
> renderer in case d)?

You're showing sphere in a view not known to master.

> And what does "This code may not work in multi-clients mode" and "Could not
> locate server on which the source is being added" exactly wnat to tell me?

Proxies are being created before the session was "ready for use". Like
I said, collaboration isn't being used actively in production so such
issues are expected. Since I don't have active projects funding this,
I will try to track down the bug exposed by (a) and give you a fix
over the weekend if I can.

Utkarsh

From utkarsh.ayachit at kitware.com  Thu Jun 16 15:50:46 2016
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Thu, 16 Jun 2016 15:50:46 -0400
Subject: [Paraview] [EXTERNAL]  Plot csv over time
In-Reply-To: <CB9FB3C3-DE13-4B7E-95E6-DCE9EB9960CF@sandia.gov>
References: <0B5B1BD3-5DFE-4454-98B5-C8744B75D7C1@sandia.gov>
 <CADHSJjCBdrxx5JHV1dUUdDgkuqucNomVYX0q5S-ouxmu=GtdCQ@mail.gmail.com>
 <CB9FB3C3-DE13-4B7E-95E6-DCE9EB9960CF@sandia.gov>
Message-ID: <CADHSJjCSduM40opdYhjmv__6F+-wMMZxE=fxpMjezpftMS+=CA@mail.gmail.com>

You're actually seeing all the variables in this file :). The quartile view
adds special meaning to variables prefixed by min/max/q1 etc. Just close
this view and instead show the output in a LineChartView. You'll see all
the columns in the CSV individually.

On Wed, Jun 15, 2016 at 5:57 PM, Jamison, Ryan Dale <rdjamis at sandia.gov>
wrote:

> Thanks for the information. I think I almost got it but still have a
> question. I?m not able to plot the time vs. some other variable from the
> csv file.
>
> In the ?Display (QuartileChartRepresentation)? I can select the ?X Array
> Name? to be any of the variables from the csv file, including time. When I
> select time, the green vertical time marker appears (this is good). The one
> thing that does not happen is that the ?Series Parameters? do not list any
> of the variables from the csv file. All that is listed are variables from
> the can.ex2. How can I plot two variables from the csv file?
>
> I?ve included an image of what I?m seeing?
>
> Thanks, Ryan
>
>
>
> On Jun 15, 2016, at 11:54 AM, Utkarsh Ayachit <utkarsh.ayachit at kitware.com>
> wrote:
>
> The green line appears with the X axis is set to a data array named
> "Time". See the attached state file. You'll can.ex2 (included in
> ParaView Example Data) and the attached csv file to load the state.
>
> On Wed, Jun 15, 2016 at 11:10 AM, Jamison, Ryan Dale <rdjamis at sandia.gov>
> wrote:
>
> Hello,
>
> I was wondering if there is a way to plot csv data over time?
> Specifically, I would like to read into an active Paraview session that
> already has some exodus results loaded a csv file (this I can already do).
> This csv file came from the same simulation as the exodus data. I?d like to
> then plot the csv results over time such that the green vertical line shows
> up denoting time as a video plays.
>
> I?ve found I can use ?plot data? for the csv data and I can indeed plot
> time vs. variable but the green vertical line doesn?t appear. My theory is
> that the vertical time marker only appears when plotting something over
> time with the appropriate filter. Any idea how to get the time marker to
> appear in the plot?
>
> Thanks, Ryan Jamison
> _______________________________________________
> 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
>
> <can0.csv><sample.pvsm>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160616/6a1a560e/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: PastedGraphic-3.png
Type: image/png
Size: 137387 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160616/6a1a560e/attachment.png>

From craig.christensen at ucalgary.ca  Thu Jun 16 14:45:30 2016
From: craig.christensen at ucalgary.ca (Craig Christensen)
Date: Thu, 16 Jun 2016 12:45:30 -0600
Subject: [Paraview] Rendering issue with cross-sections in 3D
Message-ID: <CADPbR1iTP010aEp5MMWgfn_QV9eTh0Xsktw_vegskSf7d5uDig@mail.gmail.com>

Hello all,

I'm using Paraview v5.0.1 to visualize some geophysical data, but I'm
running into a rendering issue. When I zoom in to my data sets, data in the
background randomly jumps in front of cross-sections in the foreground.
Here's a video link showing an example of this issue:
https://www.youtube.com/watch?v=vVSPfuS-OVM


Do you encounter the same issue with my data files? Here is a sample of two
of my lines here. They are legacy Paraview v2.0 VTK in ASCII format using
the POLYDATA type.
https://www.dropbox.com/sh/9e7iyajk29kxwt3/AACix63qx9ali632d9uFjE6ta?dl=0

Any suggestions on how to fix this problem are most welcome. You can reach
me at craig.christensen at ucalgary.ca .

Thanks,
--------------
*Craig W. Christensen*
M.Sc. Candidate (Geoscience), University of Calgary
BSc.Eng. (Geological), Queen's University at Kingston

<LinkedIn <http://ca.linkedin.com/pub/craig-christensen/21/240/19/en>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160616/272ea200/attachment.html>

From spl at tirebiter.org  Thu Jun 16 21:11:43 2016
From: spl at tirebiter.org (Steve Lamont)
Date: Thu, 16 Jun 2016 18:11:43 -0700
Subject: [Paraview] Rendering issue with cross-sections in 3D
In-Reply-To: <CADPbR1iTP010aEp5MMWgfn_QV9eTh0Xsktw_vegskSf7d5uDig@mail.gmail.com>
References: <CADPbR1iTP010aEp5MMWgfn_QV9eTh0Xsktw_vegskSf7d5uDig@mail.gmail.com>
Message-ID: <57634E4F.8070307@tirebiter.org>

> I'm using Paraview v5.0.1 to visualize some geophysical data, but I'm
> running into a rendering issue. When I zoom in to my data sets, data in
> the background randomly jumps in front of cross-sections in the
> foreground.

I'm running into a similar issue.

I have three cross sections, along the three major axes, and they do not 
seem to occlude one another as one would expect.

I've turned on depth peeling and have experimented with setting the 
maximum number of peels to no avail.

I know this is a classic OpenGL depth sorting issue since I've run into 
myself back when I was coding such things.

I've updated my nVidia drivers to what passes for the Latest and 
Greatest for Ubuntu Linux and I have a fairly recent graphics card 
(Quadro K2000D).  I'll be happy to supply any other system information I 
can if it'll help.

Is there something else I need to switch on in order to get ParaView to 
operate in the "expected" manner?

Thanx.

							spl


From wascott at sandia.gov  Thu Jun 16 21:15:16 2016
From: wascott at sandia.gov (Scott, W Alan)
Date: Fri, 17 Jun 2016 01:15:16 +0000
Subject: [Paraview] [EXTERNAL] Re: Rendering issue with cross-sections
 in 3D
In-Reply-To: <57634E4F.8070307@tirebiter.org>
References: <CADPbR1iTP010aEp5MMWgfn_QV9eTh0Xsktw_vegskSf7d5uDig@mail.gmail.com>
 <57634E4F.8070307@tirebiter.org>
Message-ID: <7e20cbe07254485db66e745aba2f2358@ES01AMSNLNT.srn.sandia.gov>

Steve,

I worry it sounds a bit like a bug.

Can you provide us with a toy dataset (or non-toy, if necessary) that replicates the issue?  Also, really, really good directions (+Y, roll mouse wheel in 4 times)?

Alan

-----Original Message-----
From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Steve Lamont
Sent: Thursday, June 16, 2016 7:12 PM
To: paraview at paraview.org
Subject: [EXTERNAL] Re: [Paraview] Rendering issue with cross-sections in 3D

> I'm using Paraview v5.0.1 to visualize some geophysical data, but I'm 
> running into a rendering issue. When I zoom in to my data sets, data 
> in the background randomly jumps in front of cross-sections in the 
> foreground.

I'm running into a similar issue.

I have three cross sections, along the three major axes, and they do not seem to occlude one another as one would expect.

I've turned on depth peeling and have experimented with setting the maximum number of peels to no avail.

I know this is a classic OpenGL depth sorting issue since I've run into myself back when I was coding such things.

I've updated my nVidia drivers to what passes for the Latest and Greatest for Ubuntu Linux and I have a fairly recent graphics card (Quadro K2000D).  I'll be happy to supply any other system information I can if it'll help.

Is there something else I need to switch on in order to get ParaView to operate in the "expected" manner?

Thanx.

							spl

_______________________________________________
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  Thu Jun 16 21:30:18 2016
From: wascott at sandia.gov (Scott, W Alan)
Date: Fri, 17 Jun 2016 01:30:18 +0000
Subject: [Paraview] python calculator confusion
Message-ID: <a0b8b0d7cdce467d8feeb8279009ab25@ES01AMSNLNT.srn.sandia.gov>

I'm trying to figure out the volume of each cell of a dataset.  I am trying to use the Python Calculator.  However, frankly, the data doesn't make sense.  So, I tried something really, really simple.  And things still aren't making sense.  Here is what I did:


*         ParaView 5.0.1, local server, Linux.

*         Sources/ Wavelet.  Change extents to go from 0 to 10 for X, Y and Z.  So, each cell has a volume of 1, there are 1000 cells, total volume of 1000.

*         Python Calculator.

o   Expression: volume(inputs[0])

o   Result: 31.62



Any idea what this volume is?  Why isn't it 1 or 1000, and how do I get a correct volume?



Thanks,



Alan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160617/6124b0e4/attachment.html>

From wascott at sandia.gov  Thu Jun 16 21:39:22 2016
From: wascott at sandia.gov (Scott, W Alan)
Date: Fri, 17 Jun 2016 01:39:22 +0000
Subject: [Paraview] [EXTERNAL]  python calculator confusion
In-Reply-To: <a0b8b0d7cdce467d8feeb8279009ab25@ES01AMSNLNT.srn.sandia.gov>
References: <a0b8b0d7cdce467d8feeb8279009ab25@ES01AMSNLNT.srn.sandia.gov>
Message-ID: <05e0418529e642c689e692201bf729b2@ES01AMSNLNT.srn.sandia.gov>

And at a more basic level, how do I find the volume of cells in my dataset?

Thanks,

Alan

From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Scott, W Alan
Sent: Thursday, June 16, 2016 7:30 PM
To: paraview at paraview.org
Subject: [EXTERNAL] [Paraview] python calculator confusion

I'm trying to figure out the volume of each cell of a dataset.  I am trying to use the Python Calculator.  However, frankly, the data doesn't make sense.  So, I tried something really, really simple.  And things still aren't making sense.  Here is what I did:


*         ParaView 5.0.1, local server, Linux.

*         Sources/ Wavelet.  Change extents to go from 0 to 10 for X, Y and Z.  So, each cell has a volume of 1, there are 1000 cells, total volume of 1000.

*         Python Calculator.

o   Expression: volume(inputs[0])

o   Result: 31.62



Any idea what this volume is?  Why isn't it 1 or 1000, and how do I get a correct volume?



Thanks,



Alan

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

From utkarsh.ayachit at kitware.com  Thu Jun 16 23:58:49 2016
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Thu, 16 Jun 2016 23:58:49 -0400
Subject: [Paraview] [EXTERNAL] python calculator confusion
In-Reply-To: <05e0418529e642c689e692201bf729b2@ES01AMSNLNT.srn.sandia.gov>
References: <a0b8b0d7cdce467d8feeb8279009ab25@ES01AMSNLNT.srn.sandia.gov>
 <05e0418529e642c689e692201bf729b2@ES01AMSNLNT.srn.sandia.gov>
Message-ID: <CADHSJjDG+7G3PnjqAW3sidosrbmCaFtaQZ9YWadCL0dV4Wehww@mail.gmail.com>

Here's what I found:

1. Make sure you set "Array Association" on "Python Calculator" to "Cell Data".
2. The volume() code internally uses vtkCellQuality filter. Now, when
I debugged into it, I see that is doesn;t support voxel cell types --
the cells produced by vtkImageData. Now is there are reason for that,
I don't know. I will have to dig deeper, but just stating things I see
here. For cases where it doesn't know support the cell type, the
filter just puts out -1. And the "result" I am getting is indeed just
-1 for all cells.
3. If I instead apply the Tetrahedralize filter before apply Python
Calculator, I get the right cell volume since the filter seems to
support tets, triangle, triangle strip, quad, and hexahedron. Why only
these -- I'll need to check with original developers as I don't know.

So the question is what is type of dataset you're originally trying to
use. Is it unstructured grid with the above listed cell types? If yes,
the Python Calculator should work. If not, we need another solution.
As far as I can tell there's no filter that computes volume for any
kind of cell.

Utkarsh

From david.thompson at kitware.com  Fri Jun 17 02:09:48 2016
From: david.thompson at kitware.com (David Thompson)
Date: Fri, 17 Jun 2016 02:09:48 -0400
Subject: [Paraview] [EXTERNAL] python calculator confusion
In-Reply-To: <CADHSJjDG+7G3PnjqAW3sidosrbmCaFtaQZ9YWadCL0dV4Wehww@mail.gmail.com>
References: <a0b8b0d7cdce467d8feeb8279009ab25@ES01AMSNLNT.srn.sandia.gov>
 <05e0418529e642c689e692201bf729b2@ES01AMSNLNT.srn.sandia.gov>
 <CADHSJjDG+7G3PnjqAW3sidosrbmCaFtaQZ9YWadCL0dV4Wehww@mail.gmail.com>
Message-ID: <1D378A0D-C44A-4B9D-BED7-2B6CC8E07703@kitware.com>

Hi all,

> ...
> 1. Make sure you set "Array Association" on "Python Calculator" to "Cell Data".
> 2. The volume() code internally uses vtkCellQuality filter. Now, when
> I debugged into it, I see that is doesn;t support voxel cell types --
> the cells produced by vtkImageData.

Yes, that is an artifact of using the verdict library to compute volume. The cell quality filter is being used to compute a "quality" metric that is rarely used as a primary indicator of mesh quality, so this is not really the intended use of the filter. The cell quality of axis aligned boxes is not usually of interest to anyone, so when writing the quality filter I did not consider that cell type... only those types directly supported by verdict. While volume can be obtained for other types by tetrahedralizing and summing, that does not work for other metrics like Frobenius norm. Many element shapes do not have well-characterized quality metrics.

    David

From apeczak at ara.co.uk  Fri Jun 17 04:11:22 2016
From: apeczak at ara.co.uk (Andrzej Peczak)
Date: Fri, 17 Jun 2016 08:11:22 +0000
Subject: [Paraview] Forcing update on view
In-Reply-To: <CADHSJjA-x0sjXTc-o4nBaU0JvR61gu8Crxwo4jN50HgNnAYTWA@mail.gmail.com>
References: <5DF928D22AC3AC4B964903E98F2E54515B59F2DA@sooty3.win.ara> 
 <5DF928D22AC3AC4B964903E98F2E54515B59F4D9@sooty3.win.ara> 
 <CADHSJjA-x0sjXTc-o4nBaU0JvR61gu8Crxwo4jN50HgNnAYTWA@mail.gmail.com>
Message-ID: <5DF928D22AC3AC4B964903E98F2E54515B5A3792@sooty3.win.ara>

Thanks Utkarsh, this was exactly what I was looking for!

Andrzej

-----Original Message-----
From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] 
Sent: 14 June 2016 20:22
To: Andrzej Peczak
Cc: paraview at paraview.org
Subject: Re: [Paraview] Forcing update on view

I am not sure I follow what you're doing, but here are a few things to note.

1. vtkSMProxy::UpdateVTKObjects() is called to push changes done to a property. Thus, only needs to be called on the proxy whose properties you're changing. Thus, if you are chaning "CompositeDataSetIIndex"
property on the chartRepresentationProxy, you only need to call
UpdateVTKObjects() on it.
2. pqView::forceRender() cancels pending renders, so you don't have to do that explicitly.
3. When CompositeDataSetIndex property is changed and successfully pushed, vtkChartRepresentation::AddCompositeDataSetIndex() should be called. Try putting a breakpoint there to ensure it's getting called when you're expecting it to happen.

Hope that helps,
Utkarsh

On Tue, Jun 14, 2016 at 5:35 AM, Andrzej Peczak <apeczak at ara.co.uk> wrote:
> I missed the question regarding the problem I describe. Is there a way to programmatically display the content of CompositeDataSetIndex property depending on status of the checkbox widgets I change through vector properties?
>
> Andrzej
>
> Hi,
>
> I have a snippet code which I wrote to allow me to save multiple plot images to files. I do it by changing property checkboxes of Composite Data Set Index property. I can change their status programmatically but the view is not being updated. When I change them manually in the UI the view knows about their status change and plots only the content I select. I tried to force the update with UpdateVTkObjects() of available properties plus explicitly calling render()/forceRender() of the view but with no success.  Every file I create has multiple plot curves in it instead of one.
>
> Andrzej
>
>         pqDataRepresentation *repr = source->getRepresentation( view );
>         auto chartRepresentationProxy = repr->getProxy();
>
>         vtkSMProperty *property = chartRepresentationProxy->GetProperty( "CompositeDataSetIndex" );
>         if ( property ) {
>
>                 auto VectorProperty = vtkSMIntVectorProperty::SafeDownCast( property );
>                 if ( VectorProperty ) {
>
>                         const auto numElements = VectorProperty->GetNumberOfElements();
>                         int elements[ numElements ];
>                         std::copy( VectorProperty->GetElements(), VectorProperty->GetElements() + numElements, elements );
>                         for ( auto i = 0 ; i != numElements ; ++i ) {
>                                 VectorProperty->SetElement( elements[ i ], 0 );
>                         }
>
>                         for ( auto i = 0 ; i != numElements ; ++i ) {
>                                 VectorProperty->SetElement( elements[ 
> i ], 1 );
>
>                                 source->getSourceProxy()->UpdateVTKObjects();
>                                 view->getViewProxy()->UpdateVTKObjects();
>                                 view->getViewProxy()->Update();
>                                 repr = source->getRepresentation( view );
>                                 repr->getProxy()->UpdateVTKObjects();
>                                 repr->renderView( true );
>                                 property->GetParent()->UpdateVTKObjects();
>                                 view->cancelPendingRenders();
>                                 view->forceRender();
>
>                                 std::stringstream ssFileName;
>                                 std::string ext , newName2;
>                                 std::string::size_type dot_pos = newName.rfind( '.' );
>                                 if ( dot_pos != std::string::npos ) {
>                                         ext = newName.substr( dot_pos );
>                                         newName2 = newName.substr( 0, dot_pos );
>                                 }
>                                 ssFileName << newName2 << "_" << i + 1 << ext;
>                                 view->writeImage( ssFileName.str().c_str(), size, quality );
>                                 VectorProperty->SetElement( elements[ i ], 0 );
>                         }
>
>                         VectorProperty->SetElements( elements );
>                 }
>         }
>
> **********************************************************************
> Please consider the environment. Only print this email if absolutely necessary.
>
> This email contains information that is private and confidential and is intended only for the addressee.
> If you are not the intended recipient please delete it and notify us immediately by e-mailing the sender.
> Note: All email sent to or from this address may be accessed by 
> someone other than the recipient, for system management and security reasons.
> Aircraft Research Association Ltd.  Registered in England, Registration No 503668 Registered Office:
> Manton Lane, Bedford MK41 7PF England VAT No GB 196351245
>
> **********************************************************************
> _______________________________________________
> 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

**********************************************************************
Please consider the environment. Only print this email if absolutely necessary.

This email contains information that is private and confidential and is intended only for the addressee.
If you are not the intended recipient please delete it and notify us immediately by e-mailing the sender.
Note: All email sent to or from this address may be accessed by someone other than the recipient, for
system management and security reasons.
Aircraft Research Association Ltd.  Registered in England, Registration No 503668 Registered Office:
Manton Lane, Bedford MK41 7PF England VAT No GB 196351245

**********************************************************************

From u.utku.turuncoglu at be.itu.edu.tr  Fri Jun 17 04:17:42 2016
From: u.utku.turuncoglu at be.itu.edu.tr (u.utku.turuncoglu at be.itu.edu.tr)
Date: Fri, 17 Jun 2016 11:17:42 +0300 (EEST)
Subject: [Paraview] capability of ParaView,
 Catalyst in distributed computing environment ...
Message-ID: <52703.93.115.84.202.1466151462.squirrel@webmail.be.itu.edu.tr>

Hi All,

I was working on the issue recently and i am very close to having
prototype code but i had some difficulties in initialization of the
co-processing component with coprocessorinitializewithpython call. In my
case, two model components and adaptor have its own processing source (or
MPI_COMM_WORLD). For example, MPI processor 0, 1, 2, 3 are used by 1st
model, 4, 5, 6, 7 are used by 2nd model code and 8, 9, 10, 11 is used by
adaptor. The code basically handles transferring the grid information and
data to adaptor. So, the problem is that if i try to call my custom
coprocessorinitializewithpython call in adaptor (only in 8, 9, 10, 11)
then it hangs in g_coprocessor->Initialize(); (see code at the end of the
mail) step but if i call coprocessorinitializewithpython in the main code
that uses all the available processor (between 0 and 11) and it runs
without any problem. It seems that there is a restriction in the ParaView
side (expecially vtkCPProcessor::Initialize() that can be found in
CoProcessing/Catalyst/vtkCPProcessor.cxx) but i am not sure. Do you have
any suggestion about that? Do you think that is it possible to fix it
easily. Of corse the adaptor code could use all the processor but it is
better to have its own dedicated resource that might have GPU support in
those specific servers or processors. I am relatively new to VTK and it
might be difficult for me to fix it and i need your guidance to start.

Best Regards,

--ufuk

vtkCPProcessor* g_coprocessor;

extern "C" void my_coprocessorinitializewithpython_(const char*
pythonScriptName, const char strarr[][255], int *size) {
  if (pythonScriptName != NULL) {
    if (!g_coprocessor) {
      g_coprocessor = vtkCPProcessor::New();
      g_coprocessor->Initialize();
      vtkSmartPointer<vtkCPPythonScriptPipeline> pipeline =
vtkSmartPointer<vtkCPPythonScriptPipeline>::New();
      pipeline->Initialize(pythonScriptName);
      g_coprocessor->AddPipeline(pipeline);
      //pipeline->FastDelete();
    }

    if (!g_coprocessorData) {
      g_coprocessorData = vtkCPDataDescription::New();
      // must be input port for all model components and for all dimensions
      for (int i = 0; i < *size; i++) {
        g_coprocessorData->AddInput(strarr[i]);
        std::cout << "adding input port [" << i << "] = " << strarr[i] <<
std::endl;
      }
    }
  }
}


From peterdebuchev at gmail.com  Fri Jun 17 05:08:55 2016
From: peterdebuchev at gmail.com (Peter Debuchev)
Date: Fri, 17 Jun 2016 11:08:55 +0200
Subject: [Paraview] Can a collaborative client share a pipeline without
 creating a view itself?
In-Reply-To: <CADHSJjAj5of=VckLN=VCe5KoHhaPqzYck79u=kGLpfrtO3856Q@mail.gmail.com>
References: <CAAUk9C7zY8P25QWDeZdcCA7Vx18uiBBe_+_LbyepsFt8FUQaGA@mail.gmail.com>
 <CADHSJjAj5of=VckLN=VCe5KoHhaPqzYck79u=kGLpfrtO3856Q@mail.gmail.com>
Message-ID: <CAAUk9C5y84eHpyrJnrrrc2fzrQS+GnLNV4DLNPUPTeCznThfdA@mail.gmail.com>

Dear Utkarsh,
thank you for these very clear explanations and for offering to fix the
issue with loading the initial collaboration state. Although I had
understood that data sources can only be created by the master, it wasn't
obvious to me that the same holds for views. I think I have a better
understanding now.

Concerning the master-slave differentiation I will have some questions in
the near future. Maybe you can quickly answer some thoughts on this topic
so that I don't follow the wrong path. I would like to implement "real"
collaboration where the master can allow selected clients to change the
rendering pipeline themselves. I don't see a contradiction why noone
besides the master should modify the pipeline if the state is properly
synchronized among all participants, do you?
I can imagine two or three options how to achieve this more open
collaboration without changing too much of the paraview design:
1) Let the master promote any slave to "temporary" master on request and
expect the temporary master to promote the original master again after
finishing the pipeline modification. Pro: easy implementation, Con:
problematic if original master is not promoted again for any reason.
2) Let the master modify the pipeline on behalf of slave requests. Slaves
would stream their requests to the master who actually performs the
requested changes. Pro: clean solution, Con: more complex implementation
3) Weaken the master-slave differentiation in a way that every participant
gets certain rights for modifications. Con: probably too many side effects
Can you recommend ad hoc, whether any of the approaches sound reasonable or
something similar is maybe already implemented?

Finally, I believe that I will have to dive into message passing between
paraview clients, soon. Not exactly talking about MPI, but rather in the
style of the collaboration messages that ParaView sends around, although I
am not familiar with any of the details. I would need something like "Hey
Master, please add this source X to the pipeline, append filter Y. And
notify me when you're done."
Do you happen to remember some blog post, tutorial or documentation that
gives any introduction how this can be done using ParaView classes?

Thanks a lot
Peter


2016-06-16 21:41 GMT+02:00 Utkarsh Ayachit <utkarsh.ayachit at kitware.com>:

> Peter,
>
> In ParaView's collaboration support there's the notion of a master and
> everyone else. The first client that connects to the pvserver is the
> "master" by default. The master is the only one that should create new
> proxies. This doesn't preclude the other clients from not creating new
> proxies, but if they do, things start acting funny. Also all client
> have exactly the same views as the proxy. They can be showing a
> different camera, but not have different number of views or types of
> views etc.
>
> > If I compile the example with "USEVIEW" defined in the beginning,
> > a) Starting in the order pvserver->example->ParaView, ParaView reports
> "This
> > code may not work in multi-clients mode. Could not locate server on which
> > the source is being added." and shows the sphere in the renderer, but
> not in
> > the pipeline panel.
>
> There seems to be a bug where the ParaView client has trouble loading
> existing state from another client. It seems to work as expected if
> the "master" starts creating sphere etc. after the other client has
> connected.
>
> > c) Starting in the order pvserver->example->ParaView, ParaView reports
> > "Could not locate server on which the source is being added." and shows
> > nothing.
>
> Same issue as (a).
>
> > d) Starting in the order pvserver->ParaView->example, ParaView shows
> "Sph1"
> > in the pipeline panel, but nothing in the renderer.
>
> In this case your non-master example has created a view which is not
> supported.
>
> > Why does the Sphere not show up in ParaView's pipeline panel in case a)?
>
> A bug in loading initial collaboration state.
>
> > Why does the Sphere show up in ParaView's pipeline panel, but not in the
> > renderer in case d)?
>
> You're showing sphere in a view not known to master.
>
> > And what does "This code may not work in multi-clients mode" and "Could
> not
> > locate server on which the source is being added" exactly wnat to tell
> me?
>
> Proxies are being created before the session was "ready for use". Like
> I said, collaboration isn't being used actively in production so such
> issues are expected. Since I don't have active projects funding this,
> I will try to track down the bug exposed by (a) and give you a fix
> over the weekend if I can.
>
> Utkarsh
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160617/c77d8b2b/attachment-0001.html>

From cory.quammen at kitware.com  Fri Jun 17 05:34:33 2016
From: cory.quammen at kitware.com (Cory Quammen)
Date: Fri, 17 Jun 2016 11:34:33 +0200
Subject: [Paraview] [EXTERNAL] Re: Rendering issue with cross-sections
	in 3D
In-Reply-To: <7e20cbe07254485db66e745aba2f2358@ES01AMSNLNT.srn.sandia.gov>
References: <CADPbR1iTP010aEp5MMWgfn_QV9eTh0Xsktw_vegskSf7d5uDig@mail.gmail.com>
 <57634E4F.8070307@tirebiter.org>
 <7e20cbe07254485db66e745aba2f2358@ES01AMSNLNT.srn.sandia.gov>
Message-ID: <CAB5Fpx4W_y3wPLSC5KjVdRqYFBPu-7uCwQTuHKzw807HoJn2cA@mail.gmail.com>

Folks,

The bad news: I can reproduce this in ParaView 5.0.1 on a Mac given
the data files Craig shared.

The good news: I cannot reproduce it in my development version of
ParaView 5.1 RC1. Mind downloading that version of ParaView and giving
it a shot? I would guess there might have been a rendering bug in the
OpenGL2 backend in VTK that has since been fixed.

Thanks,
Cory



On Fri, Jun 17, 2016 at 3:15 AM, Scott, W Alan <wascott at sandia.gov> wrote:
> Steve,
>
> I worry it sounds a bit like a bug.
>
> Can you provide us with a toy dataset (or non-toy, if necessary) that replicates the issue?  Also, really, really good directions (+Y, roll mouse wheel in 4 times)?
>
> Alan
>
> -----Original Message-----
> From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Steve Lamont
> Sent: Thursday, June 16, 2016 7:12 PM
> To: paraview at paraview.org
> Subject: [EXTERNAL] Re: [Paraview] Rendering issue with cross-sections in 3D
>
>> I'm using Paraview v5.0.1 to visualize some geophysical data, but I'm
>> running into a rendering issue. When I zoom in to my data sets, data
>> in the background randomly jumps in front of cross-sections in the
>> foreground.
>
> I'm running into a similar issue.
>
> I have three cross sections, along the three major axes, and they do not seem to occlude one another as one would expect.
>
> I've turned on depth peeling and have experimented with setting the maximum number of peels to no avail.
>
> I know this is a classic OpenGL depth sorting issue since I've run into myself back when I was coding such things.
>
> I've updated my nVidia drivers to what passes for the Latest and Greatest for Ubuntu Linux and I have a fairly recent graphics card (Quadro K2000D).  I'll be happy to supply any other system information I can if it'll help.
>
> Is there something else I need to switch on in order to get ParaView to operate in the "expected" manner?
>
> Thanx.
>
>                                                         spl
>
> _______________________________________________
> 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



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

From david.lonie at kitware.com  Fri Jun 17 07:22:34 2016
From: david.lonie at kitware.com (David Lonie)
Date: Fri, 17 Jun 2016 07:22:34 -0400
Subject: [Paraview] [EXTERNAL] Re: Rendering issue with cross-sections
	in 3D
In-Reply-To: <CAB5Fpx4W_y3wPLSC5KjVdRqYFBPu-7uCwQTuHKzw807HoJn2cA@mail.gmail.com>
References: <CADPbR1iTP010aEp5MMWgfn_QV9eTh0Xsktw_vegskSf7d5uDig@mail.gmail.com>
 <57634E4F.8070307@tirebiter.org>
 <7e20cbe07254485db66e745aba2f2358@ES01AMSNLNT.srn.sandia.gov>
 <CAB5Fpx4W_y3wPLSC5KjVdRqYFBPu-7uCwQTuHKzw807HoJn2cA@mail.gmail.com>
Message-ID: <CA+=e1oufoWfAHqHH5zpNW89kGgjFyWTOWV-QAu1W72WpLkVavg@mail.gmail.com>

Has anyone tested OpenGL1 vs. OpenGL2 backends on master?

It may be an issue with the recent changes to depth peeling. OpenGL1 will
still use the old implementation, OpenGL2 (not on mesa) will use the new
version.

On Fri, Jun 17, 2016 at 5:34 AM, Cory Quammen <cory.quammen at kitware.com>
wrote:

> Folks,
>
> The bad news: I can reproduce this in ParaView 5.0.1 on a Mac given
> the data files Craig shared.
>
> The good news: I cannot reproduce it in my development version of
> ParaView 5.1 RC1. Mind downloading that version of ParaView and giving
> it a shot? I would guess there might have been a rendering bug in the
> OpenGL2 backend in VTK that has since been fixed.
>
> Thanks,
> Cory
>
>
>
> On Fri, Jun 17, 2016 at 3:15 AM, Scott, W Alan <wascott at sandia.gov> wrote:
> > Steve,
> >
> > I worry it sounds a bit like a bug.
> >
> > Can you provide us with a toy dataset (or non-toy, if necessary) that
> replicates the issue?  Also, really, really good directions (+Y, roll mouse
> wheel in 4 times)?
> >
> > Alan
> >
> > -----Original Message-----
> > From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of
> Steve Lamont
> > Sent: Thursday, June 16, 2016 7:12 PM
> > To: paraview at paraview.org
> > Subject: [EXTERNAL] Re: [Paraview] Rendering issue with cross-sections
> in 3D
> >
> >> I'm using Paraview v5.0.1 to visualize some geophysical data, but I'm
> >> running into a rendering issue. When I zoom in to my data sets, data
> >> in the background randomly jumps in front of cross-sections in the
> >> foreground.
> >
> > I'm running into a similar issue.
> >
> > I have three cross sections, along the three major axes, and they do not
> seem to occlude one another as one would expect.
> >
> > I've turned on depth peeling and have experimented with setting the
> maximum number of peels to no avail.
> >
> > I know this is a classic OpenGL depth sorting issue since I've run into
> myself back when I was coding such things.
> >
> > I've updated my nVidia drivers to what passes for the Latest and
> Greatest for Ubuntu Linux and I have a fairly recent graphics card (Quadro
> K2000D).  I'll be happy to supply any other system information I can if
> it'll help.
> >
> > Is there something else I need to switch on in order to get ParaView to
> operate in the "expected" manner?
> >
> > Thanx.
> >
> >                                                         spl
> >
> > _______________________________________________
> > 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
>
>
>
> --
> 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
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160617/edacec6b/attachment.html>

From richard.c.angelini.civ at mail.mil  Fri Jun 17 08:00:46 2016
From: richard.c.angelini.civ at mail.mil (Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US))
Date: Fri, 17 Jun 2016 12:00:46 +0000
Subject: [Paraview] [Non-DoD Source] Re: [EXTERNAL] Re: Rendering issue
 with cross-sections in 3D
In-Reply-To: <CA+=e1oufoWfAHqHH5zpNW89kGgjFyWTOWV-QAu1W72WpLkVavg@mail.gmail.com>
References: <CADPbR1iTP010aEp5MMWgfn_QV9eTh0Xsktw_vegskSf7d5uDig@mail.gmail.com>
 <57634E4F.8070307@tirebiter.org>
 <7e20cbe07254485db66e745aba2f2358@ES01AMSNLNT.srn.sandia.gov>
 <CAB5Fpx4W_y3wPLSC5KjVdRqYFBPu-7uCwQTuHKzw807HoJn2cA@mail.gmail.com>
 <CA+=e1oufoWfAHqHH5zpNW89kGgjFyWTOWV-QAu1W72WpLkVavg@mail.gmail.com>
Message-ID: <D3895E66.2BFBE%Richard.C.Angelini.CIV@mail.mil>

With regard to OpenGL1 vs OpenGL2 backends ? I think that there?s an issue with 5.0.1 where the frontend/backend need to be compiled using the same OpenGL ?.. so if you want to jump back to OpenGL1 on the backend, you?ll need a similarly configured frontend ??


________________________________
Rick Angelini
USArmy Research Laboratory
CISD/HPC Architectures Team
Phone:  410-278-6266

From: ParaView <paraview-bounces at paraview.org<mailto:paraview-bounces at paraview.org>> on behalf of David Lonie <david.lonie at kitware.com<mailto:david.lonie at kitware.com>>
Date: Friday, June 17, 2016 at 7:22 AM
To: Cory Quammen <cory.quammen at kitware.com<mailto:cory.quammen at kitware.com>>
Cc: Craig Christensen <craig.christensen at ucalgary.ca<mailto:craig.christensen at ucalgary.ca>>, "paraview at paraview.org<mailto:paraview at paraview.org>" <paraview at paraview.org<mailto:paraview at paraview.org>>
Subject: [Non-DoD Source] Re: [Paraview] [EXTERNAL] Re: Rendering issue with cross-sections in 3D

All active links contained in this email were disabled. Please verify the identity of the sender, and confirm the authenticity of all links contained within the message prior to copying and pasting the address to a Web browser.

________________________________


Has anyone tested OpenGL1 vs. OpenGL2 backends on master?

It may be an issue with the recent changes to depth peeling. OpenGL1 will still use the old implementation, OpenGL2 (not on mesa) will use the new version.

On Fri, Jun 17, 2016 at 5:34 AM, Cory Quammen <cory.quammen at kitware.com<mailto:cory.quammen at kitware.com> < Caution-mailto:cory.quammen at kitware.com > > wrote:
Folks,

The bad Caution-news: I can reproduce this in ParaView 5.0.1 on a Mac given
the data files Craig shared.

The good Caution-news: I cannot reproduce it in my development version of
ParaView 5.1 RC1. Mind downloading that version of ParaView and giving
it a shot? I would guess there might have been a rendering bug in the
OpenGL2 backend in VTK that has since been fixed.

Thanks,
Cory



On Fri, Jun 17, 2016 at 3:15 AM, Scott, W Alan <wascott at sandia.gov<mailto:wascott at sandia.gov> < Caution-mailto:wascott at sandia.gov > > wrote:
> Steve,
>
> I worry it sounds a bit like a bug.
>
> Can you provide us with a toy dataset (or non-toy, if necessary) that replicates the issue?  Also, really, really good directions (+Y, roll mouse wheel in 4 times)?
>
> Alan
>
> -----Original Message-----
> From: ParaView [Caution-mailto:paraview-bounces at paraview.org < Caution-mailto:paraview-bounces at paraview.org > ] On Behalf Of Steve Lamont
> Sent: Thursday, June 16, 2016 7:12 PM
> To: paraview at paraview.org<mailto:paraview at paraview.org> < Caution-mailto:paraview at paraview.org >
> Subject: [EXTERNAL] Re: [Paraview] Rendering issue with cross-sections in 3D
>
>> I'm using Paraview v5.0.1 to visualize some geophysical data, but I'm
>> running into a rendering issue. When I zoom in to my data sets, data
>> in the background randomly jumps in front of cross-sections in the
>> foreground.
>
> I'm running into a similar issue.
>
> I have three cross sections, along the three major axes, and they do not seem to occlude one another as one would expect.
>
> I've turned on depth peeling and have experimented with setting the maximum number of peels to no avail.
>
> I know this is a classic OpenGL depth sorting issue since I've run into myself back when I was coding such things.
>
> I've updated my nVidia drivers to what passes for the Latest and Greatest for Ubuntu Linux and I have a fairly recent graphics card (Quadro K2000D).  I'll be happy to supply any other system information I can if it'll help.
>
> Is there something else I need to switch on in order to get ParaView to operate in the "expected" manner?
>
> Thanx.
>
>                                                         spl
>
> _______________________________________________
> Powered by Caution-www.kitware.com < Caution-http://www.kitware.com >
>
> Visit other Kitware open-source projects at Caution-http://www.kitware.com/opensource/opensource.html < Caution-http://www.kitware.com/opensource/opensource.html >
>
> Please keep messages on-topic and check the ParaView Wiki at: Caution-http://paraview.org/Wiki/ParaView < Caution-http://paraview.org/Wiki/ParaView >
>
> Search the list archives at: Caution-http://markmail.org/search/?q=ParaView < Caution-http://markmail.org/search/?q=ParaView >
>
> Follow this link to subscribe/unsubscribe:
> Caution-http://public.kitware.com/mailman/listinfo/paraview < Caution-http://public.kitware.com/mailman/listinfo/paraview >
> _______________________________________________
> Powered by Caution-www.kitware.com < Caution-http://www.kitware.com >
>
> Visit other Kitware open-source projects at Caution-http://www.kitware.com/opensource/opensource.html < Caution-http://www.kitware.com/opensource/opensource.html >
>
> Please keep messages on-topic and check the ParaView Wiki at: Caution-http://paraview.org/Wiki/ParaView < Caution-http://paraview.org/Wiki/ParaView >
>
> Search the list archives at: Caution-http://markmail.org/search/?q=ParaView < Caution-http://markmail.org/search/?q=ParaView >
>
> Follow this link to subscribe/unsubscribe:
> Caution-http://public.kitware.com/mailman/listinfo/paraview < Caution-http://public.kitware.com/mailman/listinfo/paraview >



--
Cory Quammen
R&D Engineer
Kitware, Inc.
_______________________________________________
Powered by Caution-www.kitware.com < Caution-http://www.kitware.com >

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

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

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

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

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

From utkarsh.ayachit at kitware.com  Fri Jun 17 09:03:06 2016
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Fri, 17 Jun 2016 09:03:06 -0400
Subject: [Paraview] Rendering issue with cross-sections in 3D
In-Reply-To: <57634E4F.8070307@tirebiter.org>
References: <CADPbR1iTP010aEp5MMWgfn_QV9eTh0Xsktw_vegskSf7d5uDig@mail.gmail.com>
 <57634E4F.8070307@tirebiter.org>
Message-ID: <CADHSJjAOG6vPS7ns_F9LbErq2U7Zhp+5-kWgu3uU03-9ZnmAMw@mail.gmail.com>

This could also be related to the age-old "tiny bounds at far away
locations" issue with OpenGL precision. Looks like your data bounds
are a few 100 units in each dimension while located at (6.0e5, 6.0e6,
2e3). Try using the "Transform" filter to move the data closer to the
origin. Does that overcome the issue?

FWIW, I too cannot reproduce the issue with 5.1.0-RC1 on my Mac
(10.11) as Cory said. I can try on a Linux box later today.

Utkarsh

On Thu, Jun 16, 2016 at 9:11 PM, Steve Lamont <spl at tirebiter.org> wrote:
>> I'm using Paraview v5.0.1 to visualize some geophysical data, but I'm
>> running into a rendering issue. When I zoom in to my data sets, data in
>> the background randomly jumps in front of cross-sections in the
>> foreground.
>
>
> I'm running into a similar issue.
>
> I have three cross sections, along the three major axes, and they do not
> seem to occlude one another as one would expect.
>
> I've turned on depth peeling and have experimented with setting the maximum
> number of peels to no avail.
>
> I know this is a classic OpenGL depth sorting issue since I've run into
> myself back when I was coding such things.
>
> I've updated my nVidia drivers to what passes for the Latest and Greatest
> for Ubuntu Linux and I have a fairly recent graphics card (Quadro K2000D).
> I'll be happy to supply any other system information I can if it'll help.
>
> Is there something else I need to switch on in order to get ParaView to
> operate in the "expected" manner?
>
> Thanx.
>
>                                                         spl
>
> _______________________________________________
> 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 Jun 17 10:39:31 2016
From: andy.bauer at kitware.com (Andy Bauer)
Date: Fri, 17 Jun 2016 10:39:31 -0400
Subject: [Paraview] capability of ParaView,
 Catalyst in distributed computing environment ...
In-Reply-To: <52703.93.115.84.202.1466151462.squirrel@webmail.be.itu.edu.tr>
References: <52703.93.115.84.202.1466151462.squirrel@webmail.be.itu.edu.tr>
Message-ID: <CAMaOp+GiKf71a2cV_7FuciX0=dkXwTyZFDU5DwioH15kMa580w@mail.gmail.com>

Hi Ufuk,

I can think of two potential fixes:

   - Use the vtkCPProcessor:: Initialize(vtkMPICommunicatorOpaqueComm&
   comm) method to initialize each process with the proper MPI communicator.
   Note that vtkMPICommunicatorOpaqueComm is defined in
   vtkMPICommunicator.cxx. A similar example to this is available in the
   Examples/Catalyst/MPISubCommunicatorExample directory.
   - Call vtkCPProcessor::Initialize() on all processes with your global
   communicator and then create a vtkMPIController partitioned the way you
   want and set that to be the "global" communicator through
   vtkMPIController::SetGlobalController().

Please let us know if either of these methods work for you.

Also, what code are you working on and is it a publicly available code? If
you show your implementation I may have some in-depth suggestions for
improvements.

Best,

Andy



On Fri, Jun 17, 2016 at 4:17 AM, <u.utku.turuncoglu at be.itu.edu.tr> wrote:

> Hi All,
>
> I was working on the issue recently and i am very close to having
> prototype code but i had some difficulties in initialization of the
> co-processing component with coprocessorinitializewithpython call. In my
> case, two model components and adaptor have its own processing source (or
> MPI_COMM_WORLD). For example, MPI processor 0, 1, 2, 3 are used by 1st
> model, 4, 5, 6, 7 are used by 2nd model code and 8, 9, 10, 11 is used by
> adaptor. The code basically handles transferring the grid information and
> data to adaptor. So, the problem is that if i try to call my custom
> coprocessorinitializewithpython call in adaptor (only in 8, 9, 10, 11)
> then it hangs in g_coprocessor->Initialize(); (see code at the end of the
> mail) step but if i call coprocessorinitializewithpython in the main code
> that uses all the available processor (between 0 and 11) and it runs
> without any problem. It seems that there is a restriction in the ParaView
> side (expecially vtkCPProcessor::Initialize() that can be found in
> CoProcessing/Catalyst/vtkCPProcessor.cxx) but i am not sure. Do you have
> any suggestion about that? Do you think that is it possible to fix it
> easily. Of corse the adaptor code could use all the processor but it is
> better to have its own dedicated resource that might have GPU support in
> those specific servers or processors. I am relatively new to VTK and it
> might be difficult for me to fix it and i need your guidance to start.
>
> Best Regards,
>
> --ufuk
>
> vtkCPProcessor* g_coprocessor;
>
> extern "C" void my_coprocessorinitializewithpython_(const char*
> pythonScriptName, const char strarr[][255], int *size) {
>   if (pythonScriptName != NULL) {
>     if (!g_coprocessor) {
>       g_coprocessor = vtkCPProcessor::New();
>       g_coprocessor->Initialize();
>       vtkSmartPointer<vtkCPPythonScriptPipeline> pipeline =
> vtkSmartPointer<vtkCPPythonScriptPipeline>::New();
>       pipeline->Initialize(pythonScriptName);
>       g_coprocessor->AddPipeline(pipeline);
>       //pipeline->FastDelete();
>     }
>
>     if (!g_coprocessorData) {
>       g_coprocessorData = vtkCPDataDescription::New();
>       // must be input port for all model components and for all dimensions
>       for (int i = 0; i < *size; i++) {
>         g_coprocessorData->AddInput(strarr[i]);
>         std::cout << "adding input port [" << i << "] = " << strarr[i] <<
> std::endl;
>       }
>     }
>   }
> }
>
> _______________________________________________
> 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/20160617/f480faac/attachment.html>

From rdjamis at sandia.gov  Fri Jun 17 13:01:13 2016
From: rdjamis at sandia.gov (Jamison, Ryan Dale)
Date: Fri, 17 Jun 2016 17:01:13 +0000
Subject: [Paraview] [EXTERNAL]  Plot csv over time
In-Reply-To: <CADHSJjCSduM40opdYhjmv__6F+-wMMZxE=fxpMjezpftMS+=CA@mail.gmail.com>
References: <0B5B1BD3-5DFE-4454-98B5-C8744B75D7C1@sandia.gov>
 <CADHSJjCBdrxx5JHV1dUUdDgkuqucNomVYX0q5S-ouxmu=GtdCQ@mail.gmail.com>
 <CB9FB3C3-DE13-4B7E-95E6-DCE9EB9960CF@sandia.gov>
 <CADHSJjCSduM40opdYhjmv__6F+-wMMZxE=fxpMjezpftMS+=CA@mail.gmail.com>
Message-ID: <EFBAE05B-34F5-4DB8-8E7A-A3294D103D11@sandia.gov>

Ah, I see it now! Thank you very much! I still have much to learn about how Paraview works.

On Jun 16, 2016, at 1:50 PM, Utkarsh Ayachit <utkarsh.ayachit at kitware.com<mailto:utkarsh.ayachit at kitware.com>> wrote:

You're actually seeing all the variables in this file :). The quartile view adds special meaning to variables prefixed by min/max/q1 etc. Just close this view and instead show the output in a LineChartView. You'll see all the columns in the CSV individually.

On Wed, Jun 15, 2016 at 5:57 PM, Jamison, Ryan Dale <rdjamis at sandia.gov<mailto:rdjamis at sandia.gov>> wrote:
Thanks for the information. I think I almost got it but still have a question. I?m not able to plot the time vs. some other variable from the csv file.

In the ?Display (QuartileChartRepresentation)? I can select the ?X Array Name? to be any of the variables from the csv file, including time. When I select time, the green vertical time marker appears (this is good). The one thing that does not happen is that the ?Series Parameters? do not list any of the variables from the csv file. All that is listed are variables from the can.ex2. How can I plot two variables from the csv file?

I?ve included an image of what I?m seeing?

Thanks, Ryan

<PastedGraphic-3.png>


On Jun 15, 2016, at 11:54 AM, Utkarsh Ayachit <utkarsh.ayachit at kitware.com<mailto:utkarsh.ayachit at kitware.com>> wrote:

The green line appears with the X axis is set to a data array named
"Time". See the attached state file. You'll can.ex2 (included in
ParaView Example Data) and the attached csv file to load the state.

On Wed, Jun 15, 2016 at 11:10 AM, Jamison, Ryan Dale <rdjamis at sandia.gov<mailto:rdjamis at sandia.gov>> wrote:
Hello,

I was wondering if there is a way to plot csv data over time? Specifically, I would like to read into an active Paraview session that already has some exodus results loaded a csv file (this I can already do). This csv file came from the same simulation as the exodus data. I?d like to then plot the csv results over time such that the green vertical line shows up denoting time as a video plays.

I?ve found I can use ?plot data? for the csv data and I can indeed plot time vs. variable but the green vertical line doesn?t appear. My theory is that the vertical time marker only appears when plotting something over time with the appropriate filter. Any idea how to get the time marker to appear in the plot?

Thanks, Ryan Jamison
_______________________________________________
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
<can0.csv><sample.pvsm>



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

From dwneumann at gmail.com  Fri Jun 17 13:38:00 2016
From: dwneumann at gmail.com (Dean Neumann)
Date: Fri, 17 Jun 2016 10:38:00 -0700
Subject: [Paraview] syntax for "global variables" for a dataset
Message-ID: <CAGgSO3jwfkdLSGHJs8d3a0mDaUoTMGCRwThT68Hy8OWD1of2YQ@mail.gmail.com>

I have seen references to the following statement in a Paraview tutorial
from University of Houston:
"Data sets sometimes capture information in ?global" variables that apply
to an entire dataset rather than a single point or cell."

If this is indeed true can someone please share example syntax of how one
would manually specify a set of global variables in a .pvd or .vtu xml file
(not programmatically via a VTK function call)  that are not contained
within an enclosing PointData or CellData element.
(I am not talking about GlobalNodeIDs or GlobalElementIDs but rather to
field data that apply to all points and arrays of an entire dataset).
I am aware of the "Plot Global Variables Over Time" filter but that seems
to apply to field values that persist over many timesteps, not field data
that are common to all points and cells.

many thanks....
Dean Neumann
Malaspina Labs Inc.
www.malaspina-labs.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160617/86c874ba/attachment.html>

From utkarsh.ayachit at kitware.com  Fri Jun 17 14:03:30 2016
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Fri, 17 Jun 2016 14:03:30 -0400
Subject: [Paraview] [EXTERNAL]  Plot csv over time
In-Reply-To: <EFBAE05B-34F5-4DB8-8E7A-A3294D103D11@sandia.gov>
References: <0B5B1BD3-5DFE-4454-98B5-C8744B75D7C1@sandia.gov>
 <CADHSJjCBdrxx5JHV1dUUdDgkuqucNomVYX0q5S-ouxmu=GtdCQ@mail.gmail.com>
 <CB9FB3C3-DE13-4B7E-95E6-DCE9EB9960CF@sandia.gov>
 <CADHSJjCSduM40opdYhjmv__6F+-wMMZxE=fxpMjezpftMS+=CA@mail.gmail.com>
 <EFBAE05B-34F5-4DB8-8E7A-A3294D103D11@sandia.gov>
Message-ID: <CADHSJjAo37KFE6fzb+GRi+=mG-z8SVnj8iZww80BKTpoR_FUXg@mail.gmail.com>

> Ah, I see it now! Thank you very much! I still have much to learn about how
> Paraview works.

Glad it's working.

From wascott at sandia.gov  Fri Jun 17 16:26:32 2016
From: wascott at sandia.gov (Scott, W Alan)
Date: Fri, 17 Jun 2016 20:26:32 +0000
Subject: [Paraview] [EXTERNAL] python calculator confusion
In-Reply-To: <CADHSJjDG+7G3PnjqAW3sidosrbmCaFtaQZ9YWadCL0dV4Wehww@mail.gmail.com>
References: <a0b8b0d7cdce467d8feeb8279009ab25@ES01AMSNLNT.srn.sandia.gov>
 <05e0418529e642c689e692201bf729b2@ES01AMSNLNT.srn.sandia.gov>
 <CADHSJjDG+7G3PnjqAW3sidosrbmCaFtaQZ9YWadCL0dV4Wehww@mail.gmail.com>
Message-ID: <3f8653961ba44f8c98825d2572d5ec7c@ES01AMSNLNT.srn.sandia.gov>

Wow, you?re an animal.  Good job.

I'm working back from a amr cth problem.  Basically, my user is trying to do data analysis on a volume of hot gas.  He ran the simulation, and the simulation and ParaView are telling him different things.  So, I took the Dave's Small CTH dataset, which starts as a smashed sphere.  I can guess the diameter, thus can guess the radius, thus can guess the volume.  And, when I used the python calculator on that, once again, I got bad results.  From there, I backed up to Wavelet, hoping for some sanity.  

I will rerun my test, remembering to set Cell Data.   Good point, I bet I messed up.

Seems to me that even more than supporting all or at least most cell types, we need to never provide wrong data.  We can coordinate off line to get this fixed.

Alan

-----Original Message-----
From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] 
Sent: Thursday, June 16, 2016 9:59 PM
To: Scott, W Alan <wascott at sandia.gov>
Cc: paraview at paraview.org
Subject: Re: [Paraview] [EXTERNAL] python calculator confusion

Here's what I found:

1. Make sure you set "Array Association" on "Python Calculator" to "Cell Data".
2. The volume() code internally uses vtkCellQuality filter. Now, when I debugged into it, I see that is doesn;t support voxel cell types -- the cells produced by vtkImageData. Now is there are reason for that, I don't know. I will have to dig deeper, but just stating things I see here. For cases where it doesn't know support the cell type, the filter just puts out -1. And the "result" I am getting is indeed just
-1 for all cells.
3. If I instead apply the Tetrahedralize filter before apply Python Calculator, I get the right cell volume since the filter seems to support tets, triangle, triangle strip, quad, and hexahedron. Why only these -- I'll need to check with original developers as I don't know.

So the question is what is type of dataset you're originally trying to use. Is it unstructured grid with the above listed cell types? If yes, the Python Calculator should work. If not, we need another solution.
As far as I can tell there's no filter that computes volume for any kind of cell.

Utkarsh

From wascott at sandia.gov  Fri Jun 17 18:24:58 2016
From: wascott at sandia.gov (Scott, W Alan)
Date: Fri, 17 Jun 2016 22:24:58 +0000
Subject: [Paraview] Finding cell coordinates in Python
Message-ID: <8aebef182a574c0a995efde995fd9ede@ES01AMSNLNT.srn.sandia.gov>

>From a user:

We have been successful at implementing python scripts and routines to analyze much of our data, but we would like for the ability to obtain the [X,Y,Z] coordinates for each cell. Is there currently a way to do this? This is CTH AMR data.

Thanks,

Alan


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

From craig.christensen at ucalgary.ca  Fri Jun 17 18:33:57 2016
From: craig.christensen at ucalgary.ca (Craig Christensen)
Date: Fri, 17 Jun 2016 16:33:57 -0600
Subject: [Paraview] [Non-DoD Source] Re: [EXTERNAL] Re: Rendering issue
 with cross-sections in 3D
In-Reply-To: <D3895E66.2BFBE%Richard.C.Angelini.CIV@mail.mil>
References: <CADPbR1iTP010aEp5MMWgfn_QV9eTh0Xsktw_vegskSf7d5uDig@mail.gmail.com>
 <57634E4F.8070307@tirebiter.org>
 <7e20cbe07254485db66e745aba2f2358@ES01AMSNLNT.srn.sandia.gov>
 <CAB5Fpx4W_y3wPLSC5KjVdRqYFBPu-7uCwQTuHKzw807HoJn2cA@mail.gmail.com>
 <CA+=e1oufoWfAHqHH5zpNW89kGgjFyWTOWV-QAu1W72WpLkVavg@mail.gmail.com>
 <D3895E66.2BFBE%Richard.C.Angelini.CIV@mail.mil>
Message-ID: <CADPbR1iP=BpOKBCO-S049_cSWz_V+QSu7jpDE0=9SRjs0Y42LA@mail.gmail.com>

Hi all,

Utkarsh's suggestion to transform the dataset closer to the origin using a
translation seems to have worked for me. I was working in UTM coordinates,
so I was working about 6,000 km away from the origin of the coordinate
system. Thanks for your help, Utkarsh!

All the best,
Craig

--------------
*Craig W. Christensen*
M.Sc. Candidate (Geoscience), University of Calgary
BSc.Eng. (Geological), Queen's University at Kingston

<LinkedIn <http://ca.linkedin.com/pub/craig-christensen/21/240/19/en>>

On Fri, Jun 17, 2016 at 6:00 AM, Angelini, Richard C (Rick) CIV USARMY
RDECOM ARL (US) <richard.c.angelini.civ at mail.mil> wrote:

> With regard to OpenGL1 vs OpenGL2 backends ? I think that there?s an issue
> with 5.0.1 where the frontend/backend need to be compiled using the same
> OpenGL ?.. so if you want to jump back to OpenGL1 on the backend, you?ll
> need a similarly configured frontend ??
>
>
> ________________________________
> Rick Angelini
> USArmy Research Laboratory
> CISD/HPC Architectures Team
> Phone:  410-278-6266
>
> From: ParaView <paraview-bounces at paraview.org> on behalf of David Lonie <
> david.lonie at kitware.com>
> Date: Friday, June 17, 2016 at 7:22 AM
> To: Cory Quammen <cory.quammen at kitware.com>
> Cc: Craig Christensen <craig.christensen at ucalgary.ca>, "
> paraview at paraview.org" <paraview at paraview.org>
> Subject: [Non-DoD Source] Re: [Paraview] [EXTERNAL] Re: Rendering issue
> with cross-sections in 3D
>
> All active links contained in this email were disabled. Please verify the
> identity of the sender, and confirm the authenticity of all links contained
> within the message prior to copying and pasting the address to a Web
> browser.
>
> ------------------------------
>
>
> Has anyone tested OpenGL1 vs. OpenGL2 backends on master?
>
> It may be an issue with the recent changes to depth peeling. OpenGL1 will
> still use the old implementation, OpenGL2 (not on mesa) will use the new
> version.
>
> On Fri, Jun 17, 2016 at 5:34 AM, Cory Quammen <cory.quammen at kitware.com
>  < Caution-mailto:cory.quammen at kitware.com <cory.quammen at kitware.com> > >
> wrote:
>
>> Folks,
>>
>> The bad Caution-news: I can reproduce this in ParaView 5.0.1 on a Mac
>> given
>> the data files Craig shared.
>>
>> The good Caution-news: I cannot reproduce it in my development version of
>> ParaView 5.1 RC1. Mind downloading that version of ParaView and giving
>> it a shot? I would guess there might have been a rendering bug in the
>> OpenGL2 backend in VTK that has since been fixed.
>>
>> Thanks,
>> Cory
>>
>>
>>
>> On Fri, Jun 17, 2016 at 3:15 AM, Scott, W Alan <wascott at sandia.gov
>>  < Caution-mailto:wascott at sandia.gov <wascott at sandia.gov> > > wrote:
>> > Steve,
>> >
>> > I worry it sounds a bit like a bug.
>> >
>> > Can you provide us with a toy dataset (or non-toy, if necessary) that
>> replicates the issue?  Also, really, really good directions (+Y, roll mouse
>> wheel in 4 times)?
>> >
>> > Alan
>> >
>> > -----Original Message-----
>> > From: ParaView [Caution-mailto:paraview-bounces at paraview.org
>> <paraview-bounces at paraview.org> < Caution-
>> mailto:paraview-bounces at paraview.org <paraview-bounces at paraview.org> > ]
>> On Behalf Of Steve Lamont
>> > Sent: Thursday, June 16, 2016 7:12 PM
>> > To: paraview at paraview.org < Caution-mailto:paraview at paraview.org
>> <paraview at paraview.org> >
>> > Subject: [EXTERNAL] Re: [Paraview] Rendering issue with cross-sections
>> in 3D
>> >
>> >> I'm using Paraview v5.0.1 to visualize some geophysical data, but I'm
>> >> running into a rendering issue. When I zoom in to my data sets, data
>> >> in the background randomly jumps in front of cross-sections in the
>> >> foreground.
>> >
>> > I'm running into a similar issue.
>> >
>> > I have three cross sections, along the three major axes, and they do
>> not seem to occlude one another as one would expect.
>> >
>> > I've turned on depth peeling and have experimented with setting the
>> maximum number of peels to no avail.
>> >
>> > I know this is a classic OpenGL depth sorting issue since I've run into
>> myself back when I was coding such things.
>> >
>> > I've updated my nVidia drivers to what passes for the Latest and
>> Greatest for Ubuntu Linux and I have a fairly recent graphics card (Quadro
>> K2000D).  I'll be happy to supply any other system information I can if
>> it'll help.
>> >
>> > Is there something else I need to switch on in order to get ParaView to
>> operate in the "expected" manner?
>> >
>> > Thanx.
>> >
>> >                                                         spl
>> >
>> > _______________________________________________
>> > Powered by Caution-www.kitware.com < Caution-http://www.kitware.com >
>> >
>> > Visit other Kitware open-source projects at Caution-
>> http://www.kitware.com/opensource/opensource.html < Caution-
>> http://www.kitware.com/opensource/opensource.html >
>> >
>> > Please keep messages on-topic and check the ParaView Wiki at: Caution-
>> http://paraview.org/Wiki/ParaView < Caution-
>> http://paraview.org/Wiki/ParaView >
>> >
>> > Search the list archives at: Caution-
>> http://markmail.org/search/?q=ParaView < Caution-
>> http://markmail.org/search/?q=ParaView >
>> >
>> > Follow this link to subscribe/unsubscribe:
>> > Caution-http://public.kitware.com/mailman/listinfo/paraview < Caution-
>> http://public.kitware.com/mailman/listinfo/paraview >
>> > _______________________________________________
>> > Powered by Caution-www.kitware.com < Caution-http://www.kitware.com >
>> >
>> > Visit other Kitware open-source projects at Caution-
>> http://www.kitware.com/opensource/opensource.html < Caution-
>> http://www.kitware.com/opensource/opensource.html >
>> >
>> > Please keep messages on-topic and check the ParaView Wiki at: Caution-
>> http://paraview.org/Wiki/ParaView < Caution-
>> http://paraview.org/Wiki/ParaView >
>> >
>> > Search the list archives at: Caution-
>> http://markmail.org/search/?q=ParaView < Caution-
>> http://markmail.org/search/?q=ParaView >
>> >
>> > Follow this link to subscribe/unsubscribe:
>> > Caution-http://public.kitware.com/mailman/listinfo/paraview < Caution-
>> http://public.kitware.com/mailman/listinfo/paraview >
>>
>>
>>
>> --
>> Cory Quammen
>> R&D Engineer
>> Kitware, Inc.
>> _______________________________________________
>> Powered by Caution-www.kitware.com < Caution-http://www.kitware.com >
>>
>> Visit other Kitware open-source projects at Caution-
>> http://www.kitware.com/opensource/opensource.html < Caution-
>> http://www.kitware.com/opensource/opensource.html >
>>
>> Please keep messages on-topic and check the ParaView Wiki at: Caution-
>> http://paraview.org/Wiki/ParaView < Caution-
>> http://paraview.org/Wiki/ParaView >
>>
>> Search the list archives at: Caution-
>> http://markmail.org/search/?q=ParaView < Caution-
>> http://markmail.org/search/?q=ParaView >
>>
>> Follow this link to subscribe/unsubscribe:
>> Caution-http://public.kitware.com/mailman/listinfo/paraview < Caution-
>> http://public.kitware.com/mailman/listinfo/paraview >
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160617/e5988ba2/attachment.html>

From spl at tirebiter.org  Fri Jun 17 20:10:23 2016
From: spl at tirebiter.org (Steve Lamont)
Date: Fri, 17 Jun 2016 17:10:23 -0700
Subject: [Paraview] [Non-DoD Source] Re: [EXTERNAL] Re: Rendering issue
 with cross-sections in 3D
In-Reply-To: <CADPbR1iP=BpOKBCO-S049_cSWz_V+QSu7jpDE0=9SRjs0Y42LA@mail.gmail.com>
References: <CADPbR1iTP010aEp5MMWgfn_QV9eTh0Xsktw_vegskSf7d5uDig@mail.gmail.com>
 <57634E4F.8070307@tirebiter.org>
 <7e20cbe07254485db66e745aba2f2358@ES01AMSNLNT.srn.sandia.gov>
 <CAB5Fpx4W_y3wPLSC5KjVdRqYFBPu-7uCwQTuHKzw807HoJn2cA@mail.gmail.com>
 <CA+=e1oufoWfAHqHH5zpNW89kGgjFyWTOWV-QAu1W72WpLkVavg@mail.gmail.com>
 <D3895E66.2BFBE%Richard.C.Angelini.CIV@mail.mil>
 <CADPbR1iP=BpOKBCO-S049_cSWz_V+QSu7jpDE0=9SRjs0Y42LA@mail.gmail.com>
Message-ID: <5764916F.7090501@tirebiter.org>

A followup on this issue.

I uninstalled the 5.0.1 version as distributed on the download site and 
reinstalled the Ubuntu version found in the distro repository and the 
problem went away.  This version gives a "warning" in its titlebar 
"Legacy Rendering Backend."

As luck would have it, an associate of mine installed the 5.0.1 Windows 
version at the ParaView download site and it exhibits the same bad behavior.

It looks to me as if the newer version, *without* the "Legacy Rendering 
Backend" does not do proper polygon sorting such that scenes are 
rendered back to front so that objects properly occlude one another.

Just for grins, I'm going to download and test the 5.0.0 version, just 
to see if it's equally borked.

							spl


From spl at tirebiter.org  Fri Jun 17 20:23:59 2016
From: spl at tirebiter.org (Steve Lamont)
Date: Fri, 17 Jun 2016 17:23:59 -0700
Subject: [Paraview] [Non-DoD Source] Re: [EXTERNAL] Re: Rendering issue
 with cross-sections in 3D
In-Reply-To: <5764916F.7090501@tirebiter.org>
References: <CADPbR1iTP010aEp5MMWgfn_QV9eTh0Xsktw_vegskSf7d5uDig@mail.gmail.com>
 <57634E4F.8070307@tirebiter.org>
 <7e20cbe07254485db66e745aba2f2358@ES01AMSNLNT.srn.sandia.gov>
 <CAB5Fpx4W_y3wPLSC5KjVdRqYFBPu-7uCwQTuHKzw807HoJn2cA@mail.gmail.com>
 <CA+=e1oufoWfAHqHH5zpNW89kGgjFyWTOWV-QAu1W72WpLkVavg@mail.gmail.com>
 <D3895E66.2BFBE%Richard.C.Angelini.CIV@mail.mil>
 <CADPbR1iP=BpOKBCO-S049_cSWz_V+QSu7jpDE0=9SRjs0Y42LA@mail.gmail.com>
 <5764916F.7090501@tirebiter.org>
Message-ID: <5764949F.9000807@tirebiter.org>

> Just for grins, I'm going to download and test the 5.0.0 version, just
> to see if it's equally borked.

Following up my own post, 5.0.0 exhibits the same behavior.

							spl



From kmorel at sandia.gov  Sat Jun 18 12:41:59 2016
From: kmorel at sandia.gov (Moreland, Kenneth)
Date: Sat, 18 Jun 2016 16:41:59 +0000
Subject: [Paraview] Finding cell coordinates in Python
Message-ID: <32D59F29-1BA9-4213-9E9B-3777F2765CC5@sandia.gov>

Cells in CTH take up some amount of volume (in 3D), meaning that there is no single [X,Y,Z] coordinate to give. Perhaps your user is looking for the [X,Y,Z] at the center of the cell, in which case the Cell Centers filter will do just that.

-Ken

From: ParaView <paraview-bounces at paraview.org> on behalf of Walter Scott <wascott at sandia.gov>
Date: Friday, June 17, 2016 at 4:24 PM
To: "paraview at paraview.org" <paraview at paraview.org>
Subject: [EXTERNAL] [Paraview] Finding cell coordinates in Python

From a user:

We have been successful at implementing python scripts and routines to analyze much of our data, but we would like for the ability to obtain the [X,Y,Z] coordinates for each cell. Is there currently a way to do this? This is CTH AMR data.

Thanks,

Alan


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

From david.thompson at kitware.com  Sat Jun 18 12:44:44 2016
From: david.thompson at kitware.com (David Thompson)
Date: Sat, 18 Jun 2016 12:44:44 -0400
Subject: [Paraview] Finding cell coordinates in Python
In-Reply-To: <8aebef182a574c0a995efde995fd9ede@ES01AMSNLNT.srn.sandia.gov>
References: <8aebef182a574c0a995efde995fd9ede@ES01AMSNLNT.srn.sandia.gov>
Message-ID: <67D4AEEC-C99F-4C00-A2AB-34E88585FB6D@kitware.com>

> We have been successful at implementing python scripts and routines to analyze much of our data, but we would like for the ability to obtain the [X,Y,Z] coordinates for each cell. Is there currently a way to do this? This is CTH AMR data.

Perhaps they have been writing client-side scripts to get at the metadata but now want access to the full dataset?

	David


From u.utku.turuncoglu at be.itu.edu.tr  Sun Jun 19 04:07:47 2016
From: u.utku.turuncoglu at be.itu.edu.tr (u.utku.turuncoglu at be.itu.edu.tr)
Date: Sun, 19 Jun 2016 11:07:47 +0300 (EEST)
Subject: [Paraview] capability of ParaView,
 Catalyst in distributed computing environment ...
In-Reply-To: <CAMaOp+GiKf71a2cV_7FuciX0=dkXwTyZFDU5DwioH15kMa580w@mail.gmail.com>
References: <52703.93.115.84.202.1466151462.squirrel@webmail.be.itu.edu.tr>
 <CAMaOp+GiKf71a2cV_7FuciX0=dkXwTyZFDU5DwioH15kMa580w@mail.gmail.com>
Message-ID: <64414.95.5.187.100.1466323667.squirrel@webmail.be.itu.edu.tr>

Hi Andy,

I used first approach and fix the issue using following customised
coprocessorinitializewithpython function. In this case, i converted type
of communicator coming from Fortran to C using MPI_Comm_f2c call. Now, the
code works without any problem. Thanks for your kindly help.

extern "C" void my_coprocessorinitializewithpython_(int *fcomm, const
char* pythonScriptName, const char strarr[][255], int *size) {
  if (pythonScriptName != NULL) {
    if (!g_coprocessor) {
      g_coprocessor = vtkCPProcessor::New();
      MPI_Comm handle = MPI_Comm_f2c(*fcomm);
      vtkMPICommunicatorOpaqueComm *Comm = new
vtkMPICommunicatorOpaqueComm(&handle);
      g_coprocessor->Initialize(*Comm);
      vtkSmartPointer<vtkCPPythonScriptPipeline> pipeline =
vtkSmartPointer<vtkCPPythonScriptPipeline>::New();
      pipeline->Initialize(pythonScriptName);
      g_coprocessor->AddPipeline(pipeline);
      //pipeline->FastDelete();
    }

    if (!g_coprocessorData) {
      g_coprocessorData = vtkCPDataDescription::New();
      // must be input port for all model components and for all dimensions
      for (int i = 0; i < *size; i++) {
        g_coprocessorData->AddInput(strarr[i]);
        std::cout << "adding input port [" << i << "] = " << strarr[i] <<
std::endl;
      }
    }
  }
}

Regards,

--ufuk

> Hi Ufuk,
>
> I can think of two potential fixes:
>
>    - Use the vtkCPProcessor:: Initialize(vtkMPICommunicatorOpaqueComm&
>    comm) method to initialize each process with the proper MPI
> communicator.
>    Note that vtkMPICommunicatorOpaqueComm is defined in
>    vtkMPICommunicator.cxx. A similar example to this is available in the
>    Examples/Catalyst/MPISubCommunicatorExample directory.
>    - Call vtkCPProcessor::Initialize() on all processes with your global
>    communicator and then create a vtkMPIController partitioned the way you
>    want and set that to be the "global" communicator through
>    vtkMPIController::SetGlobalController().
>
> Please let us know if either of these methods work for you.
>
> Also, what code are you working on and is it a publicly available code? If
> you show your implementation I may have some in-depth suggestions for
> improvements.
>
> Best,
>
> Andy
>
>
>
> On Fri, Jun 17, 2016 at 4:17 AM, <u.utku.turuncoglu at be.itu.edu.tr> wrote:
>
>> Hi All,
>>
>> I was working on the issue recently and i am very close to having
>> prototype code but i had some difficulties in initialization of the
>> co-processing component with coprocessorinitializewithpython call. In my
>> case, two model components and adaptor have its own processing source
>> (or
>> MPI_COMM_WORLD). For example, MPI processor 0, 1, 2, 3 are used by 1st
>> model, 4, 5, 6, 7 are used by 2nd model code and 8, 9, 10, 11 is used by
>> adaptor. The code basically handles transferring the grid information
>> and
>> data to adaptor. So, the problem is that if i try to call my custom
>> coprocessorinitializewithpython call in adaptor (only in 8, 9, 10, 11)
>> then it hangs in g_coprocessor->Initialize(); (see code at the end of
>> the
>> mail) step but if i call coprocessorinitializewithpython in the main
>> code
>> that uses all the available processor (between 0 and 11) and it runs
>> without any problem. It seems that there is a restriction in the
>> ParaView
>> side (expecially vtkCPProcessor::Initialize() that can be found in
>> CoProcessing/Catalyst/vtkCPProcessor.cxx) but i am not sure. Do you have
>> any suggestion about that? Do you think that is it possible to fix it
>> easily. Of corse the adaptor code could use all the processor but it is
>> better to have its own dedicated resource that might have GPU support in
>> those specific servers or processors. I am relatively new to VTK and it
>> might be difficult for me to fix it and i need your guidance to start.
>>
>> Best Regards,
>>
>> --ufuk
>>
>> vtkCPProcessor* g_coprocessor;
>>
>> extern "C" void my_coprocessorinitializewithpython_(const char*
>> pythonScriptName, const char strarr[][255], int *size) {
>>   if (pythonScriptName != NULL) {
>>     if (!g_coprocessor) {
>>       g_coprocessor = vtkCPProcessor::New();
>>       g_coprocessor->Initialize();
>>       vtkSmartPointer<vtkCPPythonScriptPipeline> pipeline =
>> vtkSmartPointer<vtkCPPythonScriptPipeline>::New();
>>       pipeline->Initialize(pythonScriptName);
>>       g_coprocessor->AddPipeline(pipeline);
>>       //pipeline->FastDelete();
>>     }
>>
>>     if (!g_coprocessorData) {
>>       g_coprocessorData = vtkCPDataDescription::New();
>>       // must be input port for all model components and for all
>> dimensions
>>       for (int i = 0; i < *size; i++) {
>>         g_coprocessorData->AddInput(strarr[i]);
>>         std::cout << "adding input port [" << i << "] = " << strarr[i]
>> <<
>> std::endl;
>>       }
>>     }
>>   }
>> }
>>
>> _______________________________________________
>> 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 pmopanhx at gmail.com  Sun Jun 19 08:48:18 2016
From: pmopanhx at gmail.com (hengxing pan)
Date: Sun, 19 Jun 2016 20:48:18 +0800
Subject: [Paraview] why can't I connect a remote server on cluster ?
Message-ID: <CAFJvLTZ4ADwJqp2stj+Rm6m26gOSJKFw6j2XQ0WL_nj4L-7fow@mail.gmail.com>

Hi, all

when I started a remote server(./pvserver), it failed with the ERRORs
below.


ERROR: In
/home/kitware/dashboards/buildbot/paraview-debian6dash-linux-shared-release_opengl2_qt4_superbuild/source-paraview/VTK/Common/System/vtkSocket.cxx,
line 481

vtkClientSocket (0x3160c80): Socket error in call to connect. Connection
timed out.



ERROR: In
/home/kitware/dashboards/buildbot/paraview-debian6dash-linux-shared-release_opengl2_qt4_superbuild/source-paraview/VTK/Common/System/vtkClientSocket.cxx,
line 53

vtkClientSocket (0x3160c80): Failed to connect to server hw:11111



ERROR: In
/home/kitware/dashboards/buildbot/paraview-debian6dash-linux-shared-release_opengl2_qt4_superbuild/source-paraview/ParaViewCore/ClientServerCore/Core/vtkTCPNetworkAccessManager.cxx,
line 309

vtkTCPNetworkAccessManager (0x1d3e870): Connect timeout.



ERROR: In
/home/kitware/dashboards/buildbot/paraview-debian6dash-linux-shared-release_opengl2_qt4_superbuild/source-paraview/ParaViewCore/ServerManager/Core/vtkSMSessionClient.cxx,
line 261

vtkSMSessionClient (0x3b70fd0): Some error in socket processing.

v

Then I tried to use a reverse connection, but it still didn't work like
below. Is there anyone who knows what happened on my remote connection ?
Thanks in advance!
BTW, I used the paraview binary installer:
ParaView-5.0.0-Qt4-OpenGL2-MPI-Linux-64bit.tar.gz on both
sides(client/server).

Hengxing

./pvserver -rc --client-host=localhost --server-port=11111
Connecting to client (reverse connection requested)...
Connection URL: csrc://localhost:11111
ERROR: In
/home/kitware/dashboards/buildbot/paraview-debian6dash-linux-shared-release_opengl2_qt4_superbuild/source-paraview/VTK/Common/System/vtkSock
vtkClientSocket (0x19aa490): Socket error in call to connect. Connection
refused.

ERROR: In
/home/kitware/dashboards/buildbot/paraview-debian6dash-linux-shared-release_opengl2_qt4_superbuild/source-paraview/VTK/Common/System/vtkClie
vtkClientSocket (0x19aa490): Failed to connect to server localhost:11111

Warning: In
/home/kitware/dashboards/buildbot/paraview-debian6dash-linux-shared-release_opengl2_qt4_superbuild/source-paraview/ParaViewCore/ClientServ
vtkTCPNetworkAccessManager (0xe51e60): Connect failed.  Retrying for
59.9991 more seconds.

ERROR: In
/home/kitware/dashboards/buildbot/paraview-debian6dash-linux-shared-release_opengl2_qt4_superbuild/source-paraview/VTK/Common/System/vtkSock
vtkClientSocket (0x19aa490): Socket error in call to connect. Connection
refused.

ERROR: In
/home/kitware/dashboards/buildbot/paraview-debian6dash-linux-shared-release_opengl2_qt4_superbuild/source-paraview/VTK/Common/System/vtkClie
vtkClientSocket (0x19aa490): Failed to connect to server localhost:11111

Warning: In
/home/kitware/dashboards/buildbot/paraview-debian6dash-linux-shared-release_opengl2_qt4_superbuild/source-paraview/ParaViewCore/ClientServ
vtkTCPNetworkAccessManager (0xe51e60): Connect failed.  Retrying for
58.9983 more seconds.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160619/693da3cc/attachment.html>

From peterdebuchev at gmail.com  Sun Jun 19 09:17:02 2016
From: peterdebuchev at gmail.com (Peter Debuchev)
Date: Sun, 19 Jun 2016 15:17:02 +0200
Subject: [Paraview] why can't I connect a remote server on cluster ?
In-Reply-To: <CAFJvLTZ4ADwJqp2stj+Rm6m26gOSJKFw6j2XQ0WL_nj4L-7fow@mail.gmail.com>
References: <CAFJvLTZ4ADwJqp2stj+Rm6m26gOSJKFw6j2XQ0WL_nj4L-7fow@mail.gmail.com>
Message-ID: <CAAUk9C7vZei_AKSC4NSo4woKntP1gq+jXPvyAUxDBMG50_yPbg@mail.gmail.com>

Hi Hengxing,
which commands did you run precisely on which machine? Did you check that
port 11111 is available on the server for the client or, in the case of the
reverse connection, available on the client for the server?

when I started a remote server(./pvserver), it failed with the ERRORs
> below.
>

The errors with vtkClientSocket seem like a problem of a client, was is
really pvserver, which failed with those messages?

Peter


>
>
> ERROR: In
> /home/kitware/dashboards/buildbot/paraview-debian6dash-linux-shared-release_opengl2_qt4_superbuild/source-paraview/VTK/Common/System/vtkSocket.cxx,
> line 481
>
> vtkClientSocket (0x3160c80): Socket error in call to connect. Connection
> timed out.
>
>
>
> ERROR: In
> /home/kitware/dashboards/buildbot/paraview-debian6dash-linux-shared-release_opengl2_qt4_superbuild/source-paraview/VTK/Common/System/vtkClientSocket.cxx,
> line 53
>
> vtkClientSocket (0x3160c80): Failed to connect to server hw:11111
>
>
>
> ERROR: In
> /home/kitware/dashboards/buildbot/paraview-debian6dash-linux-shared-release_opengl2_qt4_superbuild/source-paraview/ParaViewCore/ClientServerCore/Core/vtkTCPNetworkAccessManager.cxx,
> line 309
>
> vtkTCPNetworkAccessManager (0x1d3e870): Connect timeout.
>
>
>
> ERROR: In
> /home/kitware/dashboards/buildbot/paraview-debian6dash-linux-shared-release_opengl2_qt4_superbuild/source-paraview/ParaViewCore/ServerManager/Core/vtkSMSessionClient.cxx,
> line 261
>
> vtkSMSessionClient (0x3b70fd0): Some error in socket processing.
>
> v
>
> Then I tried to use a reverse connection, but it still didn't work like
> below. Is there anyone who knows what happened on my remote connection ?
> Thanks in advance!
> BTW, I used the paraview binary installer:
> ParaView-5.0.0-Qt4-OpenGL2-MPI-Linux-64bit.tar.gz on both
> sides(client/server).
>
> Hengxing
>
> ./pvserver -rc --client-host=localhost --server-port=11111
> Connecting to client (reverse connection requested)...
> Connection URL: csrc://localhost:11111
> ERROR: In
> /home/kitware/dashboards/buildbot/paraview-debian6dash-linux-shared-release_opengl2_qt4_superbuild/source-paraview/VTK/Common/System/vtkSock
> vtkClientSocket (0x19aa490): Socket error in call to connect. Connection
> refused.
>
> ERROR: In
> /home/kitware/dashboards/buildbot/paraview-debian6dash-linux-shared-release_opengl2_qt4_superbuild/source-paraview/VTK/Common/System/vtkClie
> vtkClientSocket (0x19aa490): Failed to connect to server localhost:11111
>
> Warning: In
> /home/kitware/dashboards/buildbot/paraview-debian6dash-linux-shared-release_opengl2_qt4_superbuild/source-paraview/ParaViewCore/ClientServ
> vtkTCPNetworkAccessManager (0xe51e60): Connect failed.  Retrying for
> 59.9991 more seconds.
>
> ERROR: In
> /home/kitware/dashboards/buildbot/paraview-debian6dash-linux-shared-release_opengl2_qt4_superbuild/source-paraview/VTK/Common/System/vtkSock
> vtkClientSocket (0x19aa490): Socket error in call to connect. Connection
> refused.
>
> ERROR: In
> /home/kitware/dashboards/buildbot/paraview-debian6dash-linux-shared-release_opengl2_qt4_superbuild/source-paraview/VTK/Common/System/vtkClie
> vtkClientSocket (0x19aa490): Failed to connect to server localhost:11111
>
> Warning: In
> /home/kitware/dashboards/buildbot/paraview-debian6dash-linux-shared-release_opengl2_qt4_superbuild/source-paraview/ParaViewCore/ClientServ
> vtkTCPNetworkAccessManager (0xe51e60): Connect failed.  Retrying for
> 58.9983 more seconds.
>
>
>
>
>
>
>
>
>
> _______________________________________________
> 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/20160619/dad60178/attachment.html>

From utkarsh.ayachit at kitware.com  Sun Jun 19 19:23:57 2016
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Sun, 19 Jun 2016 19:23:57 -0400
Subject: [Paraview] Can a collaborative client share a pipeline without
 creating a view itself?
In-Reply-To: <CAAUk9C5y84eHpyrJnrrrc2fzrQS+GnLNV4DLNPUPTeCznThfdA@mail.gmail.com>
References: <CAAUk9C7zY8P25QWDeZdcCA7Vx18uiBBe_+_LbyepsFt8FUQaGA@mail.gmail.com>
 <CADHSJjAj5of=VckLN=VCe5KoHhaPqzYck79u=kGLpfrtO3856Q@mail.gmail.com>
 <CAAUk9C5y84eHpyrJnrrrc2fzrQS+GnLNV4DLNPUPTeCznThfdA@mail.gmail.com>
Message-ID: <CADHSJjA7kNZ7ZnwXZ+u-QakryAUQhReA2h2Ng8wvhxE1R-2huw@mail.gmail.com>

Peter,

ParaView already supports changing the master. A "master" can make any
other connected process the new master. Once that happens the new
master can start changing pipelines etc.

> Finally, I believe that I will have to dive into message passing between
> paraview clients, soon.

Try running both the client and server with --cslog=<filename> and
tail those files. You'll see a log for messages being sent between
client and server.

From utkarsh.ayachit at kitware.com  Sun Jun 19 20:46:35 2016
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Sun, 19 Jun 2016 20:46:35 -0400
Subject: [Paraview] Custom panel widget
In-Reply-To: <5DF928D22AC3AC4B964903E98F2E54515B5840D0@sooty3.win.ara>
References: <5DF928D22AC3AC4B964903E98F2E54515B583281@sooty3.win.ara>
 <CADHSJjDiUwotu_T2=wH7uV0oR5wgW596L93TM2uQgPt69vhtAw@mail.gmail.com>
 <5DF928D22AC3AC4B964903E98F2E54515B58352C@sooty3.win.ara>
 <CADHSJjACOAZ27FT5nRPtuRDq_jiezhcwE7Ri-PODpySkkUYLOw@mail.gmail.com>
 <5DF928D22AC3AC4B964903E98F2E54515B583E60@sooty3.win.ara>
 <CADHSJjDct6nAa=AEO8bSYrYMrpH4LPfa0zqS3o1Bm7MWJjAWhw@mail.gmail.com>
 <5DF928D22AC3AC4B964903E98F2E54515B5840D0@sooty3.win.ara>
Message-ID: <CADHSJjCA9sS=0X0FuYQ7-bRF3jUFmadZQoOp=eMHdzJKfoRjog@mail.gmail.com>

> If I subclass vtkSIProperty how do I register it so that it can be seen in the xml configuration file of my plugin ?

Just adding it to the plugin under SERVER_MANAGER_SOURCES in
add_paraview_plugin will do the trick.

Utkarsh

From paul.melis at surfsara.nl  Mon Jun 20 03:54:05 2016
From: paul.melis at surfsara.nl (Paul Melis)
Date: Mon, 20 Jun 2016 09:54:05 +0200
Subject: [Paraview] [EXTERNAL] Re: Comparison of Visit and ParaView
 development
In-Reply-To: <3902be902af94a2ab7c02e73ba3303cf@ES01AMSNLNT.srn.sandia.gov>
References: <CAJZHu4RT7dek6wuyEWDDOL85m4kk58gnP8mgdM2-W2knZs7NgQ@mail.gmail.com>
 <CAE32kpXUPhmNGSYNqG0YkCRXJARv8jnvCjGvhkhQ7PiSVusEZA@mail.gmail.com>
 <82e5e4df-999a-d8a4-0d75-8a91195922bb@surfsara.nl>
 <3902be902af94a2ab7c02e73ba3303cf@ES01AMSNLNT.srn.sandia.gov>
Message-ID: <9517dbef-2a5a-1c14-9f19-c6f47c8390aa@surfsara.nl>

Hi all,

Thanks for all the replies and sudden bug report action ;-)

I haven't had the time to check the bugs that got updated, will try to 
do that soon.

Regards,
Paul

On 16-06-16 19:06, Scott, W Alan wrote:
> Paul,
> I looked at a few of the bugs listed below.
>
> I replicated 15944, this would impact my users.  It's on Sandia's list.
>
> 13802 works correctly on 5.0.1.  Note that you are creating 2.6 billion cells, and from what I can tell, you are running out of memory on your server side.  I was able to get this to work with 8 nodes of a cluster.  Try running the View/ Memory Inspector, it will tell you how much pressure you are putting on your memory.
>
> Alan
>
>
>
> -----Original Message-----
> From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Paul Melis
> Sent: Thursday, June 16, 2016 2:52 AM
> To: Geveci, Berk (External Contact) <berk.geveci at kitware.com>; Sven Kramer <svenkramer40 at gmail.com>
> Cc: ParaView <paraview at paraview.org>
> Subject: [EXTERNAL] Re: [Paraview] Comparison of Visit and ParaView development
>
> Hi,
>
> On 15-06-16 16:18, Berk Geveci wrote:
>> I believe that the main differentiator between ParaView and other vis
>> tools out there is the broad functionality _and_ the code quality.
>> Having the two together is really tough but our community managed this
>> with a heavy emphasis on code review and code testing. I strongly
>> recommend that folks look at the software processes used to develop
>> VTK & ParaView as well as the huge amount of testing (both test
>> quantity and platform coverage) that we do before every single commit
>> in addition to nightly. There is a very good overlap between the
>> CMake, CTest & CDash communities and the VTK/ParaView development
>> communities and there is very good reason behind this.
>
> Slightly off-topic (not fully about ParaView vs VisIt), but I always wondered about the development process of VTK/ParaView with respect to bug reports. There seem to be a huge number of reported bugs for ParaView (and a few for VTK), ranging from crashes to incorrect functionality to feature requests. Over the years I have entered more than two dozen myself, but was always surprised about the lack of response, especially when reporting things that were easily reproducible and/or crasher bugs (e.g. VTK #10528, ParaView #15291, ParaView #15944, ParaView #13802).
>
> Now, I understand that what's not working for me might not be important to others, so, of course, assigning priorty and doing actual fixes for reports is done by the developer community. A second "handicap" in this respect is undoubtedly the fact that KitWare is a business and so has different priorities than a bunch of hackers working mostly in their spare time on their pet project.
>
> But basically anything reported these days immediately gets status "backlog" and I would guesstimate getting a response to a report only about 25% of the time. I report bugs quite often for other open-source projects (and try to enter concise reports with a testcase), but with ParaView/VTK I get the feeling it's not worth the trouble, which is a shame. Actually getting back on topic: the one or two times I reported a bug in VisIt I got a reply and fix quickly!
>
> Furthermore, ParaView seems quite easy to segfault and it happens even with moderately complex pipelines and modest datasets. Parallel volume rendering has been broken for ages (or is it fixed these days? Can't tell, ParaView #13801 did not get any replies). Some examples shown on the wiki cause Python errors (e.g. #15291, #12796). And so on.
>
> So the comment above about code quality making ParaView stand out from other visualization tools is a bit a stretch in my opinion. I would certainly not call ParaView "stable". In fact, in the introductory scivis courses we teach with ParaView we always warn people that crashes are to be expected regularly and even during the course assignments they sometimes happen.
>
> The development process as mentioned by Berk is indeed impressive, but seems mostly focused on preventing regressions in existing functionality. This is a worthy goal in itself, but is only one half of the story when it comes to guaranteeing code quality. The things that aren't working (see bug reports) are maybe not getting the attention they deserve, but are apparently things folks run into when using ParaView, so they signal something real.
>
> After the stuff above I wanted to finish on a less critical note :) I prefer using ParaView over VisIt mostly because of being able to build a pipeline and prefer ParaView's nice single-window GUI over VisIt's a-window-here-a-window-there-a-window-everywhere approach. They are both good and useful tools and are work-horses for scivis tasks. Whenever I get a request from an HPC user which one to use I recommend ParaView, as it is easier to get into for basic scivis work.
>
> Regards,
> 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 peterdebuchev at gmail.com  Mon Jun 20 05:22:03 2016
From: peterdebuchev at gmail.com (Peter Debuchev)
Date: Mon, 20 Jun 2016 11:22:03 +0200
Subject: [Paraview] Can a collaborative client share a pipeline without
 creating a view itself?
In-Reply-To: <CADHSJjA7kNZ7ZnwXZ+u-QakryAUQhReA2h2Ng8wvhxE1R-2huw@mail.gmail.com>
References: <CAAUk9C7zY8P25QWDeZdcCA7Vx18uiBBe_+_LbyepsFt8FUQaGA@mail.gmail.com>
 <CADHSJjAj5of=VckLN=VCe5KoHhaPqzYck79u=kGLpfrtO3856Q@mail.gmail.com>
 <CAAUk9C5y84eHpyrJnrrrc2fzrQS+GnLNV4DLNPUPTeCznThfdA@mail.gmail.com>
 <CADHSJjA7kNZ7ZnwXZ+u-QakryAUQhReA2h2Ng8wvhxE1R-2huw@mail.gmail.com>
Message-ID: <CAAUk9C4fmnk32D=WJLGicv6RYtwJ4mDtEAHKRBCSdM2i75mX3Q@mail.gmail.com>

Dear Utkarsh,
to have some basis for this discussion, I'd like to mention that my
knowledge on the collaboration functionality is limited to what is shown in
http://vimeo.com/34480656 and to the class reference
http://www.paraview.org/ParaView/Doc/Nightly/www/cxx-doc/classvtkSMCollaborationManager.html.
Everything else I am trying to understand by debugging. Or does additional
documentation (design documents, message exchange protocols, ...) exist?

So, although the concept of promoting different clients as master is
obvious from the video above, something more is needed to allow any slave
to change the pipeline automatically by permission of the master: the slave
(S) must request to be promoted as master to the current master (M), M must
promote S as master, S operates on the pipeline, and S must promote M as
master again.
After some thoughts, my suggested option 2) may be easier and more secure:
S would send its intended operations to M, and M executes them. Here, the
question is whether I have to invent a new streaming language to encode
pipeline changes that S wants to send to M? Or can S just build the
pipeline as intended and use some available serialization to send this
pipeline state to M?

Any of the options requires some additional messages to be send between
slaves and master. This is what I am trying to figure out. The --cslog
options looks very useful, but a short overview which classes are involved
in sending custom messages including an encoded pipeline state would be
even more helpful.

Thanks
Peter


2016-06-20 1:23 GMT+02:00 Utkarsh Ayachit <utkarsh.ayachit at kitware.com>:

> Peter,
>
> ParaView already supports changing the master. A "master" can make any
> other connected process the new master. Once that happens the new
> master can start changing pipelines etc.
>
> > Finally, I believe that I will have to dive into message passing between
> > paraview clients, soon.
>
> Try running both the client and server with --cslog=<filename> and
> tail those files. You'll see a log for messages being sent between
> client and server.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160620/b5dff2e2/attachment.html>

From utkarsh.ayachit at kitware.com  Mon Jun 20 10:03:00 2016
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Mon, 20 Jun 2016 10:03:00 -0400
Subject: [Paraview] Can a collaborative client share a pipeline without
 creating a view itself?
In-Reply-To: <CAAUk9C4fmnk32D=WJLGicv6RYtwJ4mDtEAHKRBCSdM2i75mX3Q@mail.gmail.com>
References: <CAAUk9C7zY8P25QWDeZdcCA7Vx18uiBBe_+_LbyepsFt8FUQaGA@mail.gmail.com>
 <CADHSJjAj5of=VckLN=VCe5KoHhaPqzYck79u=kGLpfrtO3856Q@mail.gmail.com>
 <CAAUk9C5y84eHpyrJnrrrc2fzrQS+GnLNV4DLNPUPTeCznThfdA@mail.gmail.com>
 <CADHSJjA7kNZ7ZnwXZ+u-QakryAUQhReA2h2Ng8wvhxE1R-2huw@mail.gmail.com>
 <CAAUk9C4fmnk32D=WJLGicv6RYtwJ4mDtEAHKRBCSdM2i75mX3Q@mail.gmail.com>
Message-ID: <CADHSJjBptG45ntAN3tx1TMb0Fvqvj5kvUvNWo7GcM4cpRJ+ZbQ@mail.gmail.com>

Peter,


> Or does additional
> documentation (design documents, message exchange protocols, ...) exist?

Sorry my friend. Nothing more than what I previously mentioned on the
mailing list.

http://www.paraview.org/ParaView/images/2/24/ParaViewCollaborationChanges.pdf
http://www.paraview.org/ParaView/index.php/ProcessModule_2.0
http://www.paraview.org/ParaView/index.php/ServerManager_2.0


> So, although the concept of promoting different clients as master is obvious
> from the video above, something more is needed to allow any slave to change
> the pipeline automatically by permission of the master: the slave (S) must
> request to be promoted as master to the current master (M), M must promote S
> as master, S operates on the pipeline, and S must promote M as master again.

(My knowledge on how several of these things is quite rusty  -- so
bear with me). I'd suggest look at pqCollaborationManager and see how
it implements chat messages. You should be able to extend that concept
to add support for custom messages.


> After some thoughts, my suggested option 2) may be easier and more secure: S
> would send its intended operations to M, and M executes them. Here, the
> question is whether I have to invent a new streaming language to encode
> pipeline changes that S wants to send to M? Or can S just build the pipeline
> as intended and use some available serialization to send this pipeline state
> to M?

Why not make M aware of the code that needs to be executed and then
just trigger those through higher level messages from S? This is like
your first option, but you're only sending coarse messages eg. "Do
Action1" etc to M.

> Any of the options requires some additional messages to be send between
> slaves and master. This is what I am trying to figure out. The --cslog
> options looks very useful, but a short overview which classes are involved
> in sending custom messages including an encoded pipeline state would be even
> more helpful.

Follow the code path  from  pqCollaborationManager::onChatMessage().
It calls pqServer::sendToOtherClients(...) with a vtkSMMessage object
created.

Utkarsh

From peterdebuchev at gmail.com  Mon Jun 20 10:21:45 2016
From: peterdebuchev at gmail.com (Peter Debuchev)
Date: Mon, 20 Jun 2016 16:21:45 +0200
Subject: [Paraview] Can a collaborative client share a pipeline without
 creating a view itself?
In-Reply-To: <CADHSJjBptG45ntAN3tx1TMb0Fvqvj5kvUvNWo7GcM4cpRJ+ZbQ@mail.gmail.com>
References: <CAAUk9C7zY8P25QWDeZdcCA7Vx18uiBBe_+_LbyepsFt8FUQaGA@mail.gmail.com>
 <CADHSJjAj5of=VckLN=VCe5KoHhaPqzYck79u=kGLpfrtO3856Q@mail.gmail.com>
 <CAAUk9C5y84eHpyrJnrrrc2fzrQS+GnLNV4DLNPUPTeCznThfdA@mail.gmail.com>
 <CADHSJjA7kNZ7ZnwXZ+u-QakryAUQhReA2h2Ng8wvhxE1R-2huw@mail.gmail.com>
 <CAAUk9C4fmnk32D=WJLGicv6RYtwJ4mDtEAHKRBCSdM2i75mX3Q@mail.gmail.com>
 <CADHSJjBptG45ntAN3tx1TMb0Fvqvj5kvUvNWo7GcM4cpRJ+ZbQ@mail.gmail.com>
Message-ID: <CAAUk9C5m2nR=-gA8xtvuWD1K+j7ifiFu+fqzMT6FEj2EqcpoSg@mail.gmail.com>

Well, I see that I'll need some more debug sessions to get this solved.

>Why not make M aware of the code that needs to be executed and then
>just trigger those through higher level messages from S? This is like
>your first option, but you're only sending coarse messages eg. "Do
>Action1" etc to M.

Yes, this would be my option 2). "Make M aware of the code" means that I
need some interpreted language that I send from S to M. (I would probably
not use a separate message to execute the transmitted code, but rather
execute it as soon as it has completely arrived. But this is a minor
detail.)

What I don't understand is why only the master is allowed to add sources
etc. My attempts run fine if I start ParaView as master and then add
sources through my custom (slave) clients. Is the missing thread safety in
VTK the problem, so that I could run into synchronization issues if several
clients request changes on the server "at the same time"? (If so, I'd
suggest that the server rejects messages which are not originating from the
master.)

There is this one remaining problem that ParaView seems not to initialize
correctly if a different master has set up a pipeline earlier. Did you have
a chance to look into this issue? I might also file a bug report, if you
prefer.

Thanks
Peter


2016-06-20 16:03 GMT+02:00 Utkarsh Ayachit <utkarsh.ayachit at kitware.com>:

> Peter,
>
>
> > Or does additional
> > documentation (design documents, message exchange protocols, ...) exist?
>
> Sorry my friend. Nothing more than what I previously mentioned on the
> mailing list.
>
>
> http://www.paraview.org/ParaView/images/2/24/ParaViewCollaborationChanges.pdf
> http://www.paraview.org/ParaView/index.php/ProcessModule_2.0
> http://www.paraview.org/ParaView/index.php/ServerManager_2.0
>
>
> > So, although the concept of promoting different clients as master is
> obvious
> > from the video above, something more is needed to allow any slave to
> change
> > the pipeline automatically by permission of the master: the slave (S)
> must
> > request to be promoted as master to the current master (M), M must
> promote S
> > as master, S operates on the pipeline, and S must promote M as master
> again.
>
> (My knowledge on how several of these things is quite rusty  -- so
> bear with me). I'd suggest look at pqCollaborationManager and see how
> it implements chat messages. You should be able to extend that concept
> to add support for custom messages.
>
>
> > After some thoughts, my suggested option 2) may be easier and more
> secure: S
> > would send its intended operations to M, and M executes them. Here, the
> > question is whether I have to invent a new streaming language to encode
> > pipeline changes that S wants to send to M? Or can S just build the
> pipeline
> > as intended and use some available serialization to send this pipeline
> state
> > to M?
>
> Why not make M aware of the code that needs to be executed and then
> just trigger those through higher level messages from S? This is like
> your first option, but you're only sending coarse messages eg. "Do
> Action1" etc to M.
>
> > Any of the options requires some additional messages to be send between
> > slaves and master. This is what I am trying to figure out. The --cslog
> > options looks very useful, but a short overview which classes are
> involved
> > in sending custom messages including an encoded pipeline state would be
> even
> > more helpful.
>
> Follow the code path  from  pqCollaborationManager::onChatMessage().
> It calls pqServer::sendToOtherClients(...) with a vtkSMMessage object
> created.
>
> Utkarsh
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160620/9003411b/attachment.html>

From berk.geveci at kitware.com  Mon Jun 20 12:02:14 2016
From: berk.geveci at kitware.com (Berk Geveci)
Date: Mon, 20 Jun 2016 12:02:14 -0400
Subject: [Paraview] Comparison of Visit and ParaView development
In-Reply-To: <82e5e4df-999a-d8a4-0d75-8a91195922bb@surfsara.nl>
References: <CAJZHu4RT7dek6wuyEWDDOL85m4kk58gnP8mgdM2-W2knZs7NgQ@mail.gmail.com>
 <CAE32kpXUPhmNGSYNqG0YkCRXJARv8jnvCjGvhkhQ7PiSVusEZA@mail.gmail.com>
 <82e5e4df-999a-d8a4-0d75-8a91195922bb@surfsara.nl>
Message-ID: <CAE32kpX_tRvw06ipLbz0B=_5N00iJ_Z8-ywKLvbxTegUqRyy3w@mail.gmail.com>

Hi Paul,

This is very valid criticism. As I read it, there are two parts to the
issue.

> How bugs are handled.

You are absolutely right that we have done a poor job responding to
community bug reports and fixes. Both on VTK & ParaView bug trackers but
especially on the ParaView side. We have been having some discussions on
how to address this. Part of the solution is going to be on the tool side.
We will move away from the Mantis bug tracker to the Gitlab bug tracker and
setup some processes to maintain the bug list more easily. We will also
expire bugs more quickly to manage the list in a reasonable way. The other
part is to change our attitude towards community bugs (as opposed to bugs
Kitware is funded to fix). We have always had resources to go after a
modest amount of such bugs but culturally it has not been a priority.
Utkarsh and I will work on ways of addressing this. More on this in the
near future...

> Stability of ParaView.

I don't (fully) agree with your assessment here. ParaView is very stable,
within a particular expanding feature set that the community actively
supports. Two issues here: 1. It is hard to define what this feature set
is, 2. ParaView is open ended so it supports a much larger feature set out
of box. We support a large community that uses ParaView day-to-day for
their production work and we have clear evidence (feedback) that ParaView
has grown very stable. These folks usually leverage a small subset of what
can be done with ParaView - the same feature set provided by many other vis
tools. If you go beyond this set, you venture into areas that are not
tested for all different combinations and because of the previous issue of
how we address (don't) community bugs, issues are not always addressed
here. We will work at doing better addressing bugs here but it will never
be perfect. We will never be able to gracefully handle input files that are
out of spec for example. This is probably the #1 reason ParaView crashes.
Nor will we able to handle all cases where ParaView runs out of memory (for
example because someone converted a regular grid to an unstructured grid
through clipping). It is simply not possible to provide an open-ended tool,
which is a light layer on top of VTK, and support stability of every
infinite combination. Let's not even get started with what one can do using
Python :-)

Best,
-berk


On Thu, Jun 16, 2016 at 4:52 AM, Paul Melis <paul.melis at surfsara.nl> wrote:

> Hi,
>
> On 15-06-16 16:18, Berk Geveci wrote:
>
>> I believe that the main differentiator between ParaView and other vis
>> tools out there is the broad functionality _and_ the code quality.
>> Having the two together is really tough but our community managed this
>> with a heavy emphasis on code review and code testing. I strongly
>> recommend that folks look at the software processes used to develop VTK
>> & ParaView as well as the huge amount of testing (both test quantity and
>> platform coverage) that we do before every single commit in addition to
>> nightly. There is a very good overlap between the CMake, CTest & CDash
>> communities and the VTK/ParaView development communities and there is
>> very good reason behind this.
>>
>
> Slightly off-topic (not fully about ParaView vs VisIt), but I always
> wondered about the development process of VTK/ParaView with respect to bug
> reports. There seem to be a huge number of reported bugs for ParaView (and
> a few for VTK), ranging from crashes to incorrect functionality to feature
> requests. Over the years I have entered more than two dozen myself, but was
> always surprised about the lack of response, especially when reporting
> things that were easily reproducible and/or crasher bugs (e.g. VTK #10528,
> ParaView #15291, ParaView #15944, ParaView #13802).
>
> Now, I understand that what's not working for me might not be important to
> others, so, of course, assigning priorty and doing actual fixes for reports
> is done by the developer community. A second "handicap" in this respect is
> undoubtedly the fact that KitWare is a business and so has different
> priorities than a bunch of hackers working mostly in their spare time on
> their pet project.
>
> But basically anything reported these days immediately gets status
> "backlog" and I would guesstimate getting a response to a report only about
> 25% of the time. I report bugs quite often for other open-source projects
> (and try to enter concise reports with a testcase), but with ParaView/VTK I
> get the feeling it's not worth the trouble, which is a shame. Actually
> getting back on topic: the one or two times I reported a bug in VisIt I got
> a reply and fix quickly!
>
> Furthermore, ParaView seems quite easy to segfault and it happens even
> with moderately complex pipelines and modest datasets. Parallel volume
> rendering has been broken for ages (or is it fixed these days? Can't tell,
> ParaView #13801 did not get any replies). Some examples shown on the wiki
> cause Python errors (e.g. #15291, #12796). And so on.
>
> So the comment above about code quality making ParaView stand out from
> other visualization tools is a bit a stretch in my opinion. I would
> certainly not call ParaView "stable". In fact, in the introductory scivis
> courses we teach with ParaView we always warn people that crashes are to be
> expected regularly and even during the course assignments they sometimes
> happen.
>
> The development process as mentioned by Berk is indeed impressive, but
> seems mostly focused on preventing regressions in existing functionality.
> This is a worthy goal in itself, but is only one half of the story when it
> comes to guaranteeing code quality. The things that aren't working (see bug
> reports) are maybe not getting the attention they deserve, but are
> apparently things folks run into when using ParaView, so they signal
> something real.
>
> After the stuff above I wanted to finish on a less critical note :) I
> prefer using ParaView over VisIt mostly because of being able to build a
> pipeline and prefer ParaView's nice single-window GUI over VisIt's
> a-window-here-a-window-there-a-window-everywhere approach. They are both
> good and useful tools and are work-horses for scivis tasks. Whenever I get
> a request from an HPC user which one to use I recommend ParaView, as it is
> easier to get into for basic scivis work.
>
> Regards,
> 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 |
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160620/bab66196/attachment.html>

From dkxls23 at gmail.com  Mon Jun 20 12:03:32 2016
From: dkxls23 at gmail.com (Armin Wehrfritz)
Date: Mon, 20 Jun 2016 19:03:32 +0300
Subject: [Paraview] Transparent background in python scripts
Message-ID: <576813D4.8090804@gmail.com>

Hi!

How can I save screenshots with a transparent (alpha channel based)
background from a python script?

Currently, I'm using this command to save screenshots:
> SaveScreenshot('image.png', magnification=3, view=renderView)
But this does not write the alpha channel information.


Using "File/ Save Screenshot" in the Paraview GUI, the screenshots
have the alpha channel information saved correctly when I setting "Edit/
Settings/ General/ Transparent Background".

I'm using ParaView 5.0.1 on a 64bit Linux workstation with the latest
Nvidia driver (367.27).


-Armin

From andy.bauer at kitware.com  Mon Jun 20 14:03:56 2016
From: andy.bauer at kitware.com (Andy Bauer)
Date: Mon, 20 Jun 2016 14:03:56 -0400
Subject: [Paraview] capability of ParaView,
 Catalyst in distributed computing environment ...
In-Reply-To: <64414.95.5.187.100.1466323667.squirrel@webmail.be.itu.edu.tr>
References: <52703.93.115.84.202.1466151462.squirrel@webmail.be.itu.edu.tr>
 <CAMaOp+GiKf71a2cV_7FuciX0=dkXwTyZFDU5DwioH15kMa580w@mail.gmail.com>
 <64414.95.5.187.100.1466323667.squirrel@webmail.be.itu.edu.tr>
Message-ID: <CAMaOp+Ghx4TWpAnivBbWi2USayeDVQY1H-oAYgU=dYXoJ1efkw@mail.gmail.com>

Hi,

Glad to hear that this is working for you and thanks for sharing how you
did it! This is definitely a corner case that few Catalyst users/developers
will ever care about so I'm glad that the Catalyst API is flexible enough
to handle this.

Best,
Andy

On Sun, Jun 19, 2016 at 4:07 AM, <u.utku.turuncoglu at be.itu.edu.tr> wrote:

> Hi Andy,
>
> I used first approach and fix the issue using following customised
> coprocessorinitializewithpython function. In this case, i converted type
> of communicator coming from Fortran to C using MPI_Comm_f2c call. Now, the
> code works without any problem. Thanks for your kindly help.
>
> extern "C" void my_coprocessorinitializewithpython_(int *fcomm, const
> char* pythonScriptName, const char strarr[][255], int *size) {
>   if (pythonScriptName != NULL) {
>     if (!g_coprocessor) {
>       g_coprocessor = vtkCPProcessor::New();
>       MPI_Comm handle = MPI_Comm_f2c(*fcomm);
>       vtkMPICommunicatorOpaqueComm *Comm = new
> vtkMPICommunicatorOpaqueComm(&handle);
>       g_coprocessor->Initialize(*Comm);
>       vtkSmartPointer<vtkCPPythonScriptPipeline> pipeline =
> vtkSmartPointer<vtkCPPythonScriptPipeline>::New();
>       pipeline->Initialize(pythonScriptName);
>       g_coprocessor->AddPipeline(pipeline);
>       //pipeline->FastDelete();
>     }
>
>     if (!g_coprocessorData) {
>       g_coprocessorData = vtkCPDataDescription::New();
>       // must be input port for all model components and for all dimensions
>       for (int i = 0; i < *size; i++) {
>         g_coprocessorData->AddInput(strarr[i]);
>         std::cout << "adding input port [" << i << "] = " << strarr[i] <<
> std::endl;
>       }
>     }
>   }
> }
>
> Regards,
>
> --ufuk
>
> > Hi Ufuk,
> >
> > I can think of two potential fixes:
> >
> >    - Use the vtkCPProcessor:: Initialize(vtkMPICommunicatorOpaqueComm&
> >    comm) method to initialize each process with the proper MPI
> > communicator.
> >    Note that vtkMPICommunicatorOpaqueComm is defined in
> >    vtkMPICommunicator.cxx. A similar example to this is available in the
> >    Examples/Catalyst/MPISubCommunicatorExample directory.
> >    - Call vtkCPProcessor::Initialize() on all processes with your global
> >    communicator and then create a vtkMPIController partitioned the way
> you
> >    want and set that to be the "global" communicator through
> >    vtkMPIController::SetGlobalController().
> >
> > Please let us know if either of these methods work for you.
> >
> > Also, what code are you working on and is it a publicly available code?
> If
> > you show your implementation I may have some in-depth suggestions for
> > improvements.
> >
> > Best,
> >
> > Andy
> >
> >
> >
> > On Fri, Jun 17, 2016 at 4:17 AM, <u.utku.turuncoglu at be.itu.edu.tr>
> wrote:
> >
> >> Hi All,
> >>
> >> I was working on the issue recently and i am very close to having
> >> prototype code but i had some difficulties in initialization of the
> >> co-processing component with coprocessorinitializewithpython call. In my
> >> case, two model components and adaptor have its own processing source
> >> (or
> >> MPI_COMM_WORLD). For example, MPI processor 0, 1, 2, 3 are used by 1st
> >> model, 4, 5, 6, 7 are used by 2nd model code and 8, 9, 10, 11 is used by
> >> adaptor. The code basically handles transferring the grid information
> >> and
> >> data to adaptor. So, the problem is that if i try to call my custom
> >> coprocessorinitializewithpython call in adaptor (only in 8, 9, 10, 11)
> >> then it hangs in g_coprocessor->Initialize(); (see code at the end of
> >> the
> >> mail) step but if i call coprocessorinitializewithpython in the main
> >> code
> >> that uses all the available processor (between 0 and 11) and it runs
> >> without any problem. It seems that there is a restriction in the
> >> ParaView
> >> side (expecially vtkCPProcessor::Initialize() that can be found in
> >> CoProcessing/Catalyst/vtkCPProcessor.cxx) but i am not sure. Do you have
> >> any suggestion about that? Do you think that is it possible to fix it
> >> easily. Of corse the adaptor code could use all the processor but it is
> >> better to have its own dedicated resource that might have GPU support in
> >> those specific servers or processors. I am relatively new to VTK and it
> >> might be difficult for me to fix it and i need your guidance to start.
> >>
> >> Best Regards,
> >>
> >> --ufuk
> >>
> >> vtkCPProcessor* g_coprocessor;
> >>
> >> extern "C" void my_coprocessorinitializewithpython_(const char*
> >> pythonScriptName, const char strarr[][255], int *size) {
> >>   if (pythonScriptName != NULL) {
> >>     if (!g_coprocessor) {
> >>       g_coprocessor = vtkCPProcessor::New();
> >>       g_coprocessor->Initialize();
> >>       vtkSmartPointer<vtkCPPythonScriptPipeline> pipeline =
> >> vtkSmartPointer<vtkCPPythonScriptPipeline>::New();
> >>       pipeline->Initialize(pythonScriptName);
> >>       g_coprocessor->AddPipeline(pipeline);
> >>       //pipeline->FastDelete();
> >>     }
> >>
> >>     if (!g_coprocessorData) {
> >>       g_coprocessorData = vtkCPDataDescription::New();
> >>       // must be input port for all model components and for all
> >> dimensions
> >>       for (int i = 0; i < *size; i++) {
> >>         g_coprocessorData->AddInput(strarr[i]);
> >>         std::cout << "adding input port [" << i << "] = " << strarr[i]
> >> <<
> >> std::endl;
> >>       }
> >>     }
> >>   }
> >> }
> >>
> >> _______________________________________________
> >> 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/20160620/ad2c4474/attachment.html>

From kmorel at sandia.gov  Mon Jun 20 14:46:25 2016
From: kmorel at sandia.gov (Moreland, Kenneth)
Date: Mon, 20 Jun 2016 18:46:25 +0000
Subject: [Paraview] Questions on Paraview with 3D vector fields
Message-ID: <1ebea75c3aae498dbb95b1f927407aff@ES08AMSNLNT.srn.sandia.gov>

Jim,

It looks like you are asking two questions.

The first question is about using the glyph filter. I'm not sure what the confusion is. The arrow glyph filter works equal well with polygons and polyhedral. I have no trouble loading in a 3D dataset with 3D cells and cell-centered data. I just select the arrow glyph and everything works fine. In short, I cannot replicate what your issue is. Perhaps you can give more information.

As far as a fly through, yes it is possible in ParaView although, admittingly, the controls are not very good. To add a camera path, first open the Animation View (View -> Animation View). Then add a track to the Animation View for "Camera, Follow Path". After that, double click the track to bring up the keyframes dialog. From there you can double click "Path..." to get yet another dialog box to edit the path. Click "Camera Position" and then click back to the main ParaView window to edit the camera path.

-Ken

-----Original Message-----
From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Jim
Sent: Wednesday, June 15, 2016 8:10 PM
To: paraview at paraview.org
Subject: [EXTERNAL] [Paraview] Questions on Paraview with 3D vector fields

Hello All:

I'm working with 3D vector fields (2 of them in the same space) and want to do a fly through, set the center to be one of the arrow glyphs, and do some calculations on both fields using the calculator. I can't seem to do any of these. Any ideas?

It looks like the center selection was designed to work with polymeshes. 
The arrow glyphs just can't be selected. Is there any way to fake out Paraview and place something that the selector can see?

I saw fly through mentioned on some forum but no solution. I can place a line into my space. Is there some way to use the line as a camera path? 
I'm really interested in fly throughs in the program, not watching them as a movie. There's just too many things to change to make it a movie and not take forever to make/look at them.

The calculator looks like it only hooks up to one vector field at a time. Is there some object linking trick or running one field through an intermediate calculation that would make both fields visible to the calculator?

Any help appreciated.

-J




_______________________________________________
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 berk.geveci at kitware.com  Mon Jun 20 16:30:04 2016
From: berk.geveci at kitware.com (Berk Geveci)
Date: Mon, 20 Jun 2016 16:30:04 -0400
Subject: [Paraview] ParaView bug hackathon
Message-ID: <CAE32kpWcH5N2VNtCrLjAwFebQuqZBsNk4GY=RLKC4dNwY48oVg@mail.gmail.com>

Hi folks,

We are planning a ParaView bug hackathon on July 13. Going forward, we
would like this to be a monthly event during which the community comes
together to address bugs reported to the tracker. It will be an all day
event that we will host physically at Kitware Headquarters in Clifton Park,
NY as well as online via Google Hangout. All are welcome to attend as long
as they know the code base enough to fix bugs.

Any questions? Comments? Any potential issue with the date?

Best,
-berk
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160620/43006ea2/attachment.html>

From utkarsh.ayachit at kitware.com  Mon Jun 20 16:57:00 2016
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Mon, 20 Jun 2016 16:57:00 -0400
Subject: [Paraview] [Paraview-developers] ParaView bug hackathon
In-Reply-To: <CAE32kpWcH5N2VNtCrLjAwFebQuqZBsNk4GY=RLKC4dNwY48oVg@mail.gmail.com>
References: <CAE32kpWcH5N2VNtCrLjAwFebQuqZBsNk4GY=RLKC4dNwY48oVg@mail.gmail.com>
Message-ID: <CADHSJjA+H=2W2kkseivT-fX4SjdGHqeshm7S4hPhPLxFVzM8Zw@mail.gmail.com>

+1. I will be there.

On Mon, Jun 20, 2016 at 4:30 PM, Berk Geveci <berk.geveci at kitware.com> wrote:
> Hi folks,
>
> We are planning a ParaView bug hackathon on July 13. Going forward, we would
> like this to be a monthly event during which the community comes together to
> address bugs reported to the tracker. It will be an all day event that we
> will host physically at Kitware Headquarters in Clifton Park, NY as well as
> online via Google Hangout. All are welcome to attend as long as they know
> the code base enough to fix bugs.
>
> Any questions? Comments? Any potential issue with the date?
>
> Best,
> -berk
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Search the list archives at:
> http://markmail.org/search/?q=Paraview-developers
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview-developers
>

From ziganshinshagit at hotmail.com  Tue Jun 21 05:50:08 2016
From: ziganshinshagit at hotmail.com (=?iso-8859-5?B?yNDT2OIgt9jT0N3o2N0=?=)
Date: Tue, 21 Jun 2016 09:50:08 +0000
Subject: [Paraview] Windows build scripts
Message-ID: <DUB123-W322344AB59EA6CDB3226EA82B0@phx.gbl>

Hi! Where I can find actual Paraview v5.1 build script for Windows?

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

From dave.demarle at kitware.com  Tue Jun 21 06:14:53 2016
From: dave.demarle at kitware.com (David E DeMarle)
Date: Tue, 21 Jun 2016 12:14:53 +0200
Subject: [Paraview] Windows build scripts
In-Reply-To: <DUB123-W322344AB59EA6CDB3226EA82B0@phx.gbl>
References: <DUB123-W322344AB59EA6CDB3226EA82B0@phx.gbl>
Message-ID: <CANjZAi_0EPWqjdxx+StEGR3NTxd9e+tp0LBjJiHyVSb1Ci32MA@mail.gmail.com>

We use the ParaView super build project to build paraview and all of its
dependencies for our binaries (and for some supercomputers as well).
* https://gitlab.kitware.com/paraview/paraview-superbuild

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

On Tue, Jun 21, 2016 at 11:50 AM, ????? ???????? <
ziganshinshagit at hotmail.com> wrote:

> Hi! Where I can find actual Paraview v5.1 build script for Windows?
>
>
> _______________________________________________
> 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/20160621/07a7646f/attachment.html>

From e.devilliers at engys.com  Tue Jun 21 06:21:05 2016
From: e.devilliers at engys.com (Eugene de Villiers)
Date: Tue, 21 Jun 2016 10:21:05 +0000
Subject: [Paraview] Minor bug in OPENFOAM filter
Message-ID: <AM4PR08MB1188876E7BD0171D10755DF88B2B0@AM4PR08MB1188.eurprd08.prod.outlook.com>

Hi,

We have come across a minor but annoying bug in the Paraview OPENFOAM reader.

The component of the Paraview OPENFOAM parser that reads boundary conditions has been set up to always expect another number where a scalar is encountered in the following configuration:

(1.111 ###

when you follow a bracket-scalar with another bracket like this

(1.111 (

an exception is thrown and the field is not loaded. However, if the leading number is an integer, then it copes fine:

(1 (###

So it simply doesn't parse a scalar followed by a bracket. Most of such instances are not relevant to the display of data as they concern table inputs for time varying vector boundary conditions. The current workaround is to always use integers in interpolation input tables, but obviously this is not ideal. To reproduce the issue, simply add the following entry to any boundary condition for any volumetric field:

RandomEntry table (1.1 ( 1 2 3));

It will result in an "Error reading line XXX ... " output and the field that the entry was added to will not be loaded. If you change it to:

RandomEntry table (1 ( 1 2 3));

Then it works fine. I can provide a small case that reproduces the issue if the above is not clear.

Best regards,

Eugene de Villiers
e.devilliers at engys.com<mailto:e.devilliers at engys.com>
Mob: +44 (0) 77 89748490
Tel: +44 (0)20 32393041 (ext. 102)
Fax: +44 (0)20 33573123
[logo_red-black_fonts_signature]<http://www.engys.com/>

This message is intended only for the use of the addressee and may contain information that is privileged, confidential and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, or the employee or agent responsible for delivering the message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this e-mail in error, please notify us immediately by return e-mail and delete this e-mail and all attachments from your system.

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

From arctica1963 at gmail.com  Tue Jun 21 11:02:31 2016
From: arctica1963 at gmail.com (Lester Anderson)
Date: Tue, 21 Jun 2016 16:02:31 +0100
Subject: [Paraview] Table to structured grid problem
Message-ID: <CAE3taFBz2Yfwyqg6N5NjAiJzFuXd3nJMTNZUyym9nCd2qbgY7g@mail.gmail.com>

Hello,

I have tried to generate a structured grid from a csv file comprising
51 layers with X and Y as Long and Lat respectively.

(1) Load CSV file
(2) Filter -> TableToStructuredGrid
set dimensions:
x = 0 - 115
y = 0 - 50
z = 0 - 50

This all works fine, but the plot is skewed oddly in the gridding, as
in the outline view does not show a nice regular shaped outline but
rather a jagged edge, almost like it is trying to join points on the
front and back faces (see test picture).

TableTo Points worked fine and all points were placed correctly.

Paraview 5.0.0 64-bit Windows

Any ideas what might be going on? I never had this problem before and
the CSV file is fine.

Thanks
Lester
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Test.jpg
Type: image/jpeg
Size: 11720 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160621/e7cad5a8/attachment.jpg>

From dave.demarle at kitware.com  Tue Jun 21 11:40:08 2016
From: dave.demarle at kitware.com (David E DeMarle)
Date: Tue, 21 Jun 2016 17:40:08 +0200
Subject: [Paraview] [Paraview-developers] ParaView bug hackathon
In-Reply-To: <CADHSJjA+H=2W2kkseivT-fX4SjdGHqeshm7S4hPhPLxFVzM8Zw@mail.gmail.com>
References: <CAE32kpWcH5N2VNtCrLjAwFebQuqZBsNk4GY=RLKC4dNwY48oVg@mail.gmail.com>
 <CADHSJjA+H=2W2kkseivT-fX4SjdGHqeshm7S4hPhPLxFVzM8Zw@mail.gmail.com>
Message-ID: <CANjZAi9tCCXc2JOCj3=GnDYQkwi0ZnFjEbso32R2H9P-wtZiQQ@mail.gmail.com>

I'd like to add review of merge requests to the agenda.
On Jun 20, 2016 10:57 PM, "Utkarsh Ayachit" <utkarsh.ayachit at kitware.com>
wrote:

> +1. I will be there.
>
> On Mon, Jun 20, 2016 at 4:30 PM, Berk Geveci <berk.geveci at kitware.com>
> wrote:
> > Hi folks,
> >
> > We are planning a ParaView bug hackathon on July 13. Going forward, we
> would
> > like this to be a monthly event during which the community comes
> together to
> > address bugs reported to the tracker. It will be an all day event that we
> > will host physically at Kitware Headquarters in Clifton Park, NY as well
> as
> > online via Google Hangout. All are welcome to attend as long as they know
> > the code base enough to fix bugs.
> >
> > Any questions? Comments? Any potential issue with the date?
> >
> > Best,
> > -berk
> >
> > _______________________________________________
> > Powered by www.kitware.com
> >
> > Visit other Kitware open-source projects at
> > http://www.kitware.com/opensource/opensource.html
> >
> > Search the list archives at:
> > http://markmail.org/search/?q=Paraview-developers
> >
> > Follow this link to subscribe/unsubscribe:
> > http://public.kitware.com/mailman/listinfo/paraview-developers
> >
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Search the list archives at:
> http://markmail.org/search/?q=Paraview-developers
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview-developers
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160621/fe40a95d/attachment.html>

From utkarsh.ayachit at kitware.com  Tue Jun 21 12:04:57 2016
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Tue, 21 Jun 2016 12:04:57 -0400
Subject: [Paraview] ANN: ParaView 5.1.0 available for download
Message-ID: <CADHSJjDNbpmpc5ZQPds6XpiEBsBWS9jd5_fBJ0vzH8ZuNHVg3g@mail.gmail.com>

Folks,

ParaView 5.1.0 is now available for download [1]. Please refer to the
release notes on the Kitware blog [2]. As always, we look forward to
your feedback [3].

Also stay tuned to the Kitware Blog [4] for upcoming features and
enhancements to ParaView, ParaView Catalyst, ParaViewWeb and much
more!

- ParaView Team

[1] http://www.paraview.org/download/
[2] https://blog.kitware.com/paraview-5-1-0-release-notes/
[3] http://paraview.uservoice.com
[4] https://blog.kitware.com/tag/ParaView/

From kmorel at sandia.gov  Tue Jun 21 12:30:59 2016
From: kmorel at sandia.gov (Moreland, Kenneth)
Date: Tue, 21 Jun 2016 16:30:59 +0000
Subject: [Paraview] Table to structured grid problem
Message-ID: <f87ab203cb514684919b4599ed925827@ES08AMSNLNT.srn.sandia.gov>

Lester,

What are the dimensions of the grid in the table? Are they 116x51x51 or 115x50x50?

The extent that you set in the TableToStructuredGrid filter uses inclusive indices. That means they should go from 0 to one less than the size of the dimension. So if your grid is 115x50x50, then the extent should be set as
X = 0 - 114
Y = 0 - 49
Z = 0 - 49

-Ken

-----Original Message-----
From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Lester Anderson
Sent: Tuesday, June 21, 2016 9:03 AM
To: paraview at paraview.org
Subject: [EXTERNAL] [Paraview] Table to structured grid problem

Hello,

I have tried to generate a structured grid from a csv file comprising
51 layers with X and Y as Long and Lat respectively.

(1) Load CSV file
(2) Filter -> TableToStructuredGrid
set dimensions:
x = 0 - 115
y = 0 - 50
z = 0 - 50

This all works fine, but the plot is skewed oddly in the gridding, as in the outline view does not show a nice regular shaped outline but rather a jagged edge, almost like it is trying to join points on the front and back faces (see test picture).

TableTo Points worked fine and all points were placed correctly.

Paraview 5.0.0 64-bit Windows

Any ideas what might be going on? I never had this problem before and the CSV file is fine.

Thanks
Lester

From kmorel at sandia.gov  Tue Jun 21 13:17:07 2016
From: kmorel at sandia.gov (Moreland, Kenneth)
Date: Tue, 21 Jun 2016 17:17:07 +0000
Subject: [Paraview] Questions on Paraview with 3D vector fields
Message-ID: <d6a97414d72248f9b8a66c542686af27@ES08AMSNLNT.srn.sandia.gov>

Jim,

I think I'm pretty confused about what you are trying to do. I don't know what you mean by "pick center on one of the glyphs." Can you back up and describe in detail how you are setting up your visualization. What you use to read the data, what filters you apply, how you set up the display, and the interactions you are doing.

-Ken

-----Original Message-----
From: Jim [mailto:guilfordstuff at gmail.com] 
Sent: Monday, June 20, 2016 5:36 PM
To: Moreland, Kenneth <kmorel at sandia.gov>; paraview at paraview.org
Subject: [EXTERNAL] Re: [Paraview] Questions on Paraview with 3D vector fields

Ken:

I'm loading the vectors from a file (raw data format, 3 floats). I extract subset and make glyphs from that. When I try to pick center on one of the glyphs, I get the following message: "vtkSMRenderViewProxy
(0000000000056914B0): Snapping to the surface is not available therefore the camera focal point will be used to determine the depth of the picking."  This is the only reason I want to select a glyph. I've tried the point selection options that I can find.

I'm afraid animation is non-existent for my case. I have custom .vtp files that contain lines. I want to move the camera along that path. 
When I double click on the camera track I can see that it has the basics, a path and a focus (thanks for that, by the way), but I don't see a way to get my data into the camera track. It doesn't even look like there is a cut and paste option. I can write custom files for this sort of thing, but I just don't know how to get things to interact with my path data.

I have a similar problem with data display; I want to turn on vector glyphs around my path, but this line (I think Paraview considers it a point set) doesn't seem to be a first class object... there isn't a way to calculate using a line and a vector field or even two vector fields for that matter. It's starting to look like I have to learn to program yet another environment.

Thanks for any help you can give.

-Jim Daniels

On 06/20/2016 02:46 PM, Moreland, Kenneth wrote:
> Jim,
>
> It looks like you are asking two questions.
>
> The first question is about using the glyph filter. I'm not sure what the confusion is. The arrow glyph filter works equal well with polygons and polyhedral. I have no trouble loading in a 3D dataset with 3D cells and cell-centered data. I just select the arrow glyph and everything works fine. In short, I cannot replicate what your issue is. Perhaps you can give more information.
>
> As far as a fly through, yes it is possible in ParaView although, admittingly, the controls are not very good. To add a camera path, first open the Animation View (View -> Animation View). Then add a track to the Animation View for "Camera, Follow Path". After that, double click the track to bring up the keyframes dialog. From there you can double click "Path..." to get yet another dialog box to edit the path. Click "Camera Position" and then click back to the main ParaView window to edit the camera path.
>
> -Ken
>
> -----Original Message-----
> From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Jim
> Sent: Wednesday, June 15, 2016 8:10 PM
> To: paraview at paraview.org
> Subject: [EXTERNAL] [Paraview] Questions on Paraview with 3D vector 
> fields
>
> Hello All:
>
> I'm working with 3D vector fields (2 of them in the same space) and want to do a fly through, set the center to be one of the arrow glyphs, and do some calculations on both fields using the calculator. I can't seem to do any of these. Any ideas?
>
> It looks like the center selection was designed to work with polymeshes.
> The arrow glyphs just can't be selected. Is there any way to fake out Paraview and place something that the selector can see?
>
> I saw fly through mentioned on some forum but no solution. I can place a line into my space. Is there some way to use the line as a camera path?
> I'm really interested in fly throughs in the program, not watching them as a movie. There's just too many things to change to make it a movie and not take forever to make/look at them.
>
> The calculator looks like it only hooks up to one vector field at a time. Is there some object linking trick or running one field through an intermediate calculation that would make both fields visible to the calculator?
>
> Any help appreciated.
>
> -J
>
>
>
>
> _______________________________________________
> 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 foss at grueninger.de  Tue Jun 21 14:18:43 2016
From: foss at grueninger.de (=?UTF-8?Q?Christoph_Gr=C3=BCninger?=)
Date: Tue, 21 Jun 2016 20:18:43 +0200 (CEST)
Subject: [Paraview] Required CMake version 3.5
Message-ID: <14169594.887742.1466533123403.JavaMail.open-xchange@omgreatgod.store>

Dear Paraview developers,
congratulations to the 5.1 release and thanks for your hard work!

I currently try to package it for openSuse and I stumbled upon the
required CMake version. What's the reason for this harsh requirement?
Wouldn't be 3.0 or similar be sufficient?
Currently all stable releases are excluded. I hope you can reduce the
required version for 5.1.1.

Bye
Christoph

From spl at tirebiter.org  Tue Jun 21 18:09:20 2016
From: spl at tirebiter.org (Steve Lamont)
Date: Tue, 21 Jun 2016 15:09:20 -0700
Subject: [Paraview] Version 5.1.0
Message-ID: <20160621220920.9FF9B8E2FD4@tirebiter.org>

Just FYI, Version 5.1.0 seems to fix most of the z-sorting issue I was
kvetching about prior to the weekend.  However, intersecting cross
section planes still do not properly occlude one another.

Tested on Ubuntu Studio 16.04.

							spl
							

From cory.quammen at kitware.com  Tue Jun 21 19:01:15 2016
From: cory.quammen at kitware.com (Cory Quammen)
Date: Wed, 22 Jun 2016 01:01:15 +0200
Subject: [Paraview] Required CMake version 3.5
In-Reply-To: <14169594.887742.1466533123403.JavaMail.open-xchange@omgreatgod.store>
References: <14169594.887742.1466533123403.JavaMail.open-xchange@omgreatgod.store>
Message-ID: <CAB5Fpx5UZOh4QPo8pHx4oG-59A8g2bo=1H3Jm-H5ABRO3079wA@mail.gmail.com>

Hi Christoph,

Thank you for working on packaging ParaView for openSUSE!

Please see this discussion in the paraview-developers mailing list
archive that gives reasons for updating the required version of CMake
to 3.5:

http://public.kitware.com/pipermail/paraview-developers/2016-April/004229.html

Based on that discussion, loosening the requirement to CMake 3.0 does
not appear to be feasible. The latest version of CMake in openSUSE to
my perhaps na?ve eye appears to be 3.3.2:

https://software.opensuse.org/package/cmake

I'm not sure we can go back that far - is there a chance you can try
building ParaView with CMake 3.3.2? You need only modify the
cmake_minimum_required command in the top level CMakeLists.txt file.

- Cory

On Tue, Jun 21, 2016 at 8:18 PM, Christoph Gr?ninger <foss at grueninger.de> wrote:
> Dear Paraview developers,
> congratulations to the 5.1 release and thanks for your hard work!
>
> I currently try to package it for openSuse and I stumbled upon the
> required CMake version. What's the reason for this harsh requirement?
> Wouldn't be 3.0 or similar be sufficient?
> Currently all stable releases are excluded. I hope you can reduce the
> required version for 5.1.1.
>
> Bye
> Christoph
> _______________________________________________
> 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 foss at grueninger.de  Tue Jun 21 23:21:33 2016
From: foss at grueninger.de (=?UTF-8?Q?Christoph_Gr=C3=BCninger?=)
Date: Wed, 22 Jun 2016 05:21:33 +0200 (CEST)
Subject: [Paraview] Required CMake version 3.5
In-Reply-To: <CAB5Fpx5UZOh4QPo8pHx4oG-59A8g2bo=1H3Jm-H5ABRO3079wA@mail.gmail.com>
References: <14169594.887742.1466533123403.JavaMail.open-xchange@omgreatgod.store>
 <CAB5Fpx5UZOh4QPo8pHx4oG-59A8g2bo=1H3Jm-H5ABRO3079wA@mail.gmail.com>
Message-ID: <1354112273.905026.1466565693599.JavaMail.open-xchange@omgreatgod.store>

Hi Cory,
thanks for link to the developer mailing list discussion. I think CMake 3.3 is better then
3.5, because at least the last Leap 42.1 release provides that.
I patched ParaView to require CMake 3.0 and it builds fine. I will package ParaView 5.1
that way and hope you reduce the requirement to CMake 3.3 for the next time.

> Based on that discussion, loosening the requirement to CMake 3.0 does
> not appear to be feasible.

CMake 3.0 helped to clean some code paths, nothing really complicated. You have
to check whether you can get other improvements from newer CMake version by
copying the relevant parts and calling that instead of the built-in functions.
So 3.0 might be feasible and reasonable.

Bye
Christoph

From peterdebuchev at gmail.com  Wed Jun 22 01:31:07 2016
From: peterdebuchev at gmail.com (Peter Debuchev)
Date: Wed, 22 Jun 2016 07:31:07 +0200
Subject: [Paraview] Can a collaborative client share a pipeline without
 creating a view itself?
In-Reply-To: <CADHSJjAj5of=VckLN=VCe5KoHhaPqzYck79u=kGLpfrtO3856Q@mail.gmail.com>
References: <CAAUk9C7zY8P25QWDeZdcCA7Vx18uiBBe_+_LbyepsFt8FUQaGA@mail.gmail.com>
 <CADHSJjAj5of=VckLN=VCe5KoHhaPqzYck79u=kGLpfrtO3856Q@mail.gmail.com>
Message-ID: <CAAUk9C5WDLoKXx58XVCHSQCQycX-TSMM=Y8FuGCU1EJ-e4bhjA@mail.gmail.com>

Dear Utkarsh,
can you give a quick update whether the suggested bug fix is likely to be
solved:

> Proxies are being created before the session was "ready for use". Like
> I said, collaboration isn't being used actively in production so such
> issues are expected. Since I don't have active projects funding this,
> I will try to track down the bug exposed by (a) and give you a fix
> over the weekend if I can.

Otherwise I'll have to find a workaround like having my client queue all
pipeline commands until ParaView has connected and only then execute them
so that ParaView can follow the correct pipeline state.

Peter

2016-06-16 21:41 GMT+02:00 Utkarsh Ayachit <utkarsh.ayachit at kitware.com>:

> Peter,
>
> In ParaView's collaboration support there's the notion of a master and
> everyone else. The first client that connects to the pvserver is the
> "master" by default. The master is the only one that should create new
> proxies. This doesn't preclude the other clients from not creating new
> proxies, but if they do, things start acting funny. Also all client
> have exactly the same views as the proxy. They can be showing a
> different camera, but not have different number of views or types of
> views etc.
>
> > If I compile the example with "USEVIEW" defined in the beginning,
> > a) Starting in the order pvserver->example->ParaView, ParaView reports
> "This
> > code may not work in multi-clients mode. Could not locate server on which
> > the source is being added." and shows the sphere in the renderer, but
> not in
> > the pipeline panel.
>
> There seems to be a bug where the ParaView client has trouble loading
> existing state from another client. It seems to work as expected if
> the "master" starts creating sphere etc. after the other client has
> connected.
>
> > c) Starting in the order pvserver->example->ParaView, ParaView reports
> > "Could not locate server on which the source is being added." and shows
> > nothing.
>
> Same issue as (a).
>
> > d) Starting in the order pvserver->ParaView->example, ParaView shows
> "Sph1"
> > in the pipeline panel, but nothing in the renderer.
>
> In this case your non-master example has created a view which is not
> supported.
>
> > Why does the Sphere not show up in ParaView's pipeline panel in case a)?
>
> A bug in loading initial collaboration state.
>
> > Why does the Sphere show up in ParaView's pipeline panel, but not in the
> > renderer in case d)?
>
> You're showing sphere in a view not known to master.
>
> > And what does "This code may not work in multi-clients mode" and "Could
> not
> > locate server on which the source is being added" exactly wnat to tell
> me?
>
> Proxies are being created before the session was "ready for use". Like
> I said, collaboration isn't being used actively in production so such
> issues are expected. Since I don't have active projects funding this,
> I will try to track down the bug exposed by (a) and give you a fix
> over the weekend if I can.
>
> Utkarsh
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160622/5cf7c72b/attachment.html>

From arctica1963 at gmail.com  Wed Jun 22 01:42:07 2016
From: arctica1963 at gmail.com (Lester Anderson)
Date: Wed, 22 Jun 2016 06:42:07 +0100
Subject: [Paraview] Table to structured grid problem
In-Reply-To: <f87ab203cb514684919b4599ed925827@ES08AMSNLNT.srn.sandia.gov>
References: <f87ab203cb514684919b4599ed925827@ES08AMSNLNT.srn.sandia.gov>
Message-ID: <CAE3taFBC+rDHEXXcxa89u3E_Gu9OfSuv+KN4aDQ06_6=hP-PSw@mail.gmail.com>

Hi Ken,

The data dimensions are: 116 x 51 x 51 (xyz), so the model extent was set to:
X = 0 - 115, Y = 0 - 50, Z = 0 -50
These extents work fine and no errors assciated with the input, and no
missing nodes. The model comprises 51 layers and each is 116 x 51 and
all have the total 5916.

Not sure what is going on because loading as points is fine.

On 21 June 2016 at 17:30, Moreland, Kenneth <kmorel at sandia.gov> wrote:
> Lester,
>
> What are the dimensions of the grid in the table? Are they 116x51x51 or 115x50x50?
>
> The extent that you set in the TableToStructuredGrid filter uses inclusive indices. That means they should go from 0 to one less than the size of the dimension. So if your grid is 115x50x50, then the extent should be set as
> X = 0 - 114
> Y = 0 - 49
> Z = 0 - 49
>
> -Ken
>
> -----Original Message-----
> From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Lester Anderson
> Sent: Tuesday, June 21, 2016 9:03 AM
> To: paraview at paraview.org
> Subject: [EXTERNAL] [Paraview] Table to structured grid problem
>
> Hello,
>
> I have tried to generate a structured grid from a csv file comprising
> 51 layers with X and Y as Long and Lat respectively.
>
> (1) Load CSV file
> (2) Filter -> TableToStructuredGrid
> set dimensions:
> x = 0 - 115
> y = 0 - 50
> z = 0 - 50
>
> This all works fine, but the plot is skewed oddly in the gridding, as in the outline view does not show a nice regular shaped outline but rather a jagged edge, almost like it is trying to join points on the front and back faces (see test picture).
>
> TableTo Points worked fine and all points were placed correctly.
>
> Paraview 5.0.0 64-bit Windows
>
> Any ideas what might be going on? I never had this problem before and the CSV file is fine.
>
> Thanks
> Lester

From cory.quammen at kitware.com  Wed Jun 22 02:41:59 2016
From: cory.quammen at kitware.com (Cory Quammen)
Date: Wed, 22 Jun 2016 08:41:59 +0200
Subject: [Paraview] Required CMake version 3.5
In-Reply-To: <1354112273.905026.1466565693599.JavaMail.open-xchange@omgreatgod.store>
References: <14169594.887742.1466533123403.JavaMail.open-xchange@omgreatgod.store>
 <CAB5Fpx5UZOh4QPo8pHx4oG-59A8g2bo=1H3Jm-H5ABRO3079wA@mail.gmail.com>
 <1354112273.905026.1466565693599.JavaMail.open-xchange@omgreatgod.store>
Message-ID: <CAB5Fpx4qyaAPa0HNBBT6_B02sZDMhDoYiqu_VzX77oUmLMLevQ@mail.gmail.com>

Hi Christoph,

Thanks for the information, and again, thanks for your hard work
packaging ParaView.

Best regards,
Cory



On Wed, Jun 22, 2016 at 5:21 AM, Christoph Gr?ninger <foss at grueninger.de> wrote:
> Hi Cory,
> thanks for link to the developer mailing list discussion. I think CMake 3.3 is better then
> 3.5, because at least the last Leap 42.1 release provides that.
> I patched ParaView to require CMake 3.0 and it builds fine. I will package ParaView 5.1
> that way and hope you reduce the requirement to CMake 3.3 for the next time.
>
>> Based on that discussion, loosening the requirement to CMake 3.0 does
>> not appear to be feasible.
>
> CMake 3.0 helped to clean some code paths, nothing really complicated. You have
> to check whether you can get other improvements from newer CMake version by
> copying the relevant parts and calling that instead of the built-in functions.
> So 3.0 might be feasible and reasonable.
>
> Bye
> Christoph



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

From bravo.loic at gmail.com  Wed Jun 22 02:46:20 2016
From: bravo.loic at gmail.com (LB)
Date: Wed, 22 Jun 2016 08:46:20 +0200
Subject: [Paraview]  XML plugin syntax for FileChooser
In-Reply-To: <CAJ-2Sz3kCmOofa=XwMkCX4yy3q74XR+XOsqJaht8r=65pwSedA@mail.gmail.com>
References: <CAJ-2Sz0f--EvyaMqVFFYBSJJcMn8LQfMy__-iQrX2_cH95Haig@mail.gmail.com>
 <CAJ-2Sz31NBS00+PEmcSPTY_PJUE9aKwEitBnrQP1wUjPGBqEqg@mail.gmail.com>
 <CAJ-2Sz3kCmOofa=XwMkCX4yy3q74XR+XOsqJaht8r=65pwSedA@mail.gmail.com>
Message-ID: <CAJ-2Sz3bW=SDML-d9BP61HSy8_Bf7Eynp_ug2gofZ+M3yon8Ew@mail.gmail.com>

[Paraview] XML plugin syntax for FileChooser.



Hi,



I would like to create a custom programmable python filter  to write some
calculation results in a file.

I?ve tried to use the following XML plugin syntax to define a FileChooser
button and help the user select the path of the output file :

<StringVectorProperty
  label="Path"
  command="SetParameter"
  name="QFileName"
  initial_string="QFileName"
  number_of_elements="1"
  panel_visibility="default">
  <FileListDomain name="files" />
  <Documentation>Path of the output file</Documentation>
  <Hints>
    <FileChooser extensions="inp" file_description="APDL input file" />
  </Hints>
</StringVectorProperty>

This create a text field with an associated file chooser button as I wanted.

But it seems that I can only select existing files.

Is-there a way to tell Paraview that this path is an output path and not an
input path ?

Best regards,
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160622/16b61b67/attachment.html>

From arctica1963 at gmail.com  Wed Jun 22 05:23:29 2016
From: arctica1963 at gmail.com (Lester Anderson)
Date: Wed, 22 Jun 2016 10:23:29 +0100
Subject: [Paraview] Table to structured grid problem
In-Reply-To: <CAE3taFBC+rDHEXXcxa89u3E_Gu9OfSuv+KN4aDQ06_6=hP-PSw@mail.gmail.com>
References: <f87ab203cb514684919b4599ed925827@ES08AMSNLNT.srn.sandia.gov>
 <CAE3taFBC+rDHEXXcxa89u3E_Gu9OfSuv+KN4aDQ06_6=hP-PSw@mail.gmail.com>
Message-ID: <CAE3taFC_e4uxXjw8r0f7QP0W6wd69EeGa0mXTdQSJ0a+WQnD+Q@mail.gmail.com>

As a quick note, each layer is ordered bottom left to top right. The
region is defined as:
west = 117, East = 128.5, South = -11, North = -6

On 22 June 2016 at 06:42, Lester Anderson <arctica1963 at gmail.com> wrote:
> Hi Ken,
>
> The data dimensions are: 116 x 51 x 51 (xyz), so the model extent was set to:
> X = 0 - 115, Y = 0 - 50, Z = 0 -50
> These extents work fine and no errors assciated with the input, and no
> missing nodes. The model comprises 51 layers and each is 116 x 51 and
> all have the total 5916.
>
> Not sure what is going on because loading as points is fine.
>
> On 21 June 2016 at 17:30, Moreland, Kenneth <kmorel at sandia.gov> wrote:
>> Lester,
>>
>> What are the dimensions of the grid in the table? Are they 116x51x51 or 115x50x50?
>>
>> The extent that you set in the TableToStructuredGrid filter uses inclusive indices. That means they should go from 0 to one less than the size of the dimension. So if your grid is 115x50x50, then the extent should be set as
>> X = 0 - 114
>> Y = 0 - 49
>> Z = 0 - 49
>>
>> -Ken
>>
>> -----Original Message-----
>> From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Lester Anderson
>> Sent: Tuesday, June 21, 2016 9:03 AM
>> To: paraview at paraview.org
>> Subject: [EXTERNAL] [Paraview] Table to structured grid problem
>>
>> Hello,
>>
>> I have tried to generate a structured grid from a csv file comprising
>> 51 layers with X and Y as Long and Lat respectively.
>>
>> (1) Load CSV file
>> (2) Filter -> TableToStructuredGrid
>> set dimensions:
>> x = 0 - 115
>> y = 0 - 50
>> z = 0 - 50
>>
>> This all works fine, but the plot is skewed oddly in the gridding, as in the outline view does not show a nice regular shaped outline but rather a jagged edge, almost like it is trying to join points on the front and back faces (see test picture).
>>
>> TableTo Points worked fine and all points were placed correctly.
>>
>> Paraview 5.0.0 64-bit Windows
>>
>> Any ideas what might be going on? I never had this problem before and the CSV file is fine.
>>
>> Thanks
>> Lester

From corinnareuter75 at gmail.com  Wed Jun 22 06:51:19 2016
From: corinnareuter75 at gmail.com (corinna reuter)
Date: Wed, 22 Jun 2016 12:51:19 +0200
Subject: [Paraview] Automatically updating time variable dataset
Message-ID: <CAOyh2eYmdc2UmjC-aCvLYSk4UGQARJbQgkP5Orc7qmPjniibJQ@mail.gmail.com>

A question to the specialists:
Can Paraview refresh its view automatically when a dataset updates its
state?

A plugin starts a background thread that calculates new dataset values
periodically. Each time a calculation step is finished, all filters and
views connected to the generated dataset should be updated. (Something
similar is done in a live catalyst connection. But catalyst has a serious
drawback for large datasets. It runs in a separate process, so that the
datasets cannot be in shared memory, but have to be transferred, requiring
redundant storage space and wasted network bandwidth.) Although paraview is
said to be not thread safe, it should't be problematic as long as access to
VTK classes is limited to the main thread. The difficult question is, how
can paraview be notified that a plugin has updated its output while the
main thread only waits for GUI or network events when idle?

Any ideas or recommendations?
Conny
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160622/f8123986/attachment.html>

From mathieu.westphal at kitware.com  Wed Jun 22 06:59:22 2016
From: mathieu.westphal at kitware.com (Mathieu Westphal)
Date: Wed, 22 Jun 2016 12:59:22 +0200
Subject: [Paraview] Automatically updating time variable dataset
In-Reply-To: <CAOyh2eYmdc2UmjC-aCvLYSk4UGQARJbQgkP5Orc7qmPjniibJQ@mail.gmail.com>
References: <CAOyh2eYmdc2UmjC-aCvLYSk4UGQARJbQgkP5Orc7qmPjniibJQ@mail.gmail.com>
Message-ID: <CAC2t4UT+5yT47ja=BEs5Pi32QRTd9KA2NO1hCt4HV1+KL4=HRA@mail.gmail.com>

Hello

A work around would be to declare two (fake) timestep in your reader and
play the animation in loop in paraview.

Regards,

Mathieu Westphal

On Wed, Jun 22, 2016 at 12:51 PM, corinna reuter <corinnareuter75 at gmail.com>
wrote:

> A question to the specialists:
> Can Paraview refresh its view automatically when a dataset updates its
> state?
>
> A plugin starts a background thread that calculates new dataset values
> periodically. Each time a calculation step is finished, all filters and
> views connected to the generated dataset should be updated. (Something
> similar is done in a live catalyst connection. But catalyst has a serious
> drawback for large datasets. It runs in a separate process, so that the
> datasets cannot be in shared memory, but have to be transferred, requiring
> redundant storage space and wasted network bandwidth.) Although paraview is
> said to be not thread safe, it should't be problematic as long as access to
> VTK classes is limited to the main thread. The difficult question is, how
> can paraview be notified that a plugin has updated its output while the
> main thread only waits for GUI or network events when idle?
>
> Any ideas or recommendations?
> Conny
>
> _______________________________________________
> 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/20160622/06b794c8/attachment.html>

From arctica1963 at gmail.com  Wed Jun 22 07:15:39 2016
From: arctica1963 at gmail.com (Lester Anderson)
Date: Wed, 22 Jun 2016 12:15:39 +0100
Subject: [Paraview] Table to structured grid problem
In-Reply-To: <CAE3taFC_e4uxXjw8r0f7QP0W6wd69EeGa0mXTdQSJ0a+WQnD+Q@mail.gmail.com>
References: <f87ab203cb514684919b4599ed925827@ES08AMSNLNT.srn.sandia.gov>
 <CAE3taFBC+rDHEXXcxa89u3E_Gu9OfSuv+KN4aDQ06_6=hP-PSw@mail.gmail.com>
 <CAE3taFC_e4uxXjw8r0f7QP0W6wd69EeGa0mXTdQSJ0a+WQnD+Q@mail.gmail.com>
Message-ID: <CAE3taFAGqtMrV0buKs2RpehuQf2kc4J-NTKD+0pyyLekO7nivA@mail.gmail.com>

Think I sorted it by reordering the data:
sort(z) -> sort(y) -> sort(x) (in Excel)
Gives the volume rendered properly. So is there a specific ordering
scheme to follow?

On 22 June 2016 at 10:23, Lester Anderson <arctica1963 at gmail.com> wrote:
> As a quick note, each layer is ordered bottom left to top right. The
> region is defined as:
> west = 117, East = 128.5, South = -11, North = -6
>
> On 22 June 2016 at 06:42, Lester Anderson <arctica1963 at gmail.com> wrote:
>> Hi Ken,
>>
>> The data dimensions are: 116 x 51 x 51 (xyz), so the model extent was set to:
>> X = 0 - 115, Y = 0 - 50, Z = 0 -50
>> These extents work fine and no errors assciated with the input, and no
>> missing nodes. The model comprises 51 layers and each is 116 x 51 and
>> all have the total 5916.
>>
>> Not sure what is going on because loading as points is fine.
>>
>> On 21 June 2016 at 17:30, Moreland, Kenneth <kmorel at sandia.gov> wrote:
>>> Lester,
>>>
>>> What are the dimensions of the grid in the table? Are they 116x51x51 or 115x50x50?
>>>
>>> The extent that you set in the TableToStructuredGrid filter uses inclusive indices. That means they should go from 0 to one less than the size of the dimension. So if your grid is 115x50x50, then the extent should be set as
>>> X = 0 - 114
>>> Y = 0 - 49
>>> Z = 0 - 49
>>>
>>> -Ken
>>>
>>> -----Original Message-----
>>> From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Lester Anderson
>>> Sent: Tuesday, June 21, 2016 9:03 AM
>>> To: paraview at paraview.org
>>> Subject: [EXTERNAL] [Paraview] Table to structured grid problem
>>>
>>> Hello,
>>>
>>> I have tried to generate a structured grid from a csv file comprising
>>> 51 layers with X and Y as Long and Lat respectively.
>>>
>>> (1) Load CSV file
>>> (2) Filter -> TableToStructuredGrid
>>> set dimensions:
>>> x = 0 - 115
>>> y = 0 - 50
>>> z = 0 - 50
>>>
>>> This all works fine, but the plot is skewed oddly in the gridding, as in the outline view does not show a nice regular shaped outline but rather a jagged edge, almost like it is trying to join points on the front and back faces (see test picture).
>>>
>>> TableTo Points worked fine and all points were placed correctly.
>>>
>>> Paraview 5.0.0 64-bit Windows
>>>
>>> Any ideas what might be going on? I never had this problem before and the CSV file is fine.
>>>
>>> Thanks
>>> Lester

From cory.quammen at kitware.com  Wed Jun 22 07:55:44 2016
From: cory.quammen at kitware.com (Cory Quammen)
Date: Wed, 22 Jun 2016 13:55:44 +0200
Subject: [Paraview] Table to structured grid problem
In-Reply-To: <CAE3taFAGqtMrV0buKs2RpehuQf2kc4J-NTKD+0pyyLekO7nivA@mail.gmail.com>
References: <f87ab203cb514684919b4599ed925827@ES08AMSNLNT.srn.sandia.gov>
 <CAE3taFBC+rDHEXXcxa89u3E_Gu9OfSuv+KN4aDQ06_6=hP-PSw@mail.gmail.com>
 <CAE3taFC_e4uxXjw8r0f7QP0W6wd69EeGa0mXTdQSJ0a+WQnD+Q@mail.gmail.com>
 <CAE3taFAGqtMrV0buKs2RpehuQf2kc4J-NTKD+0pyyLekO7nivA@mail.gmail.com>
Message-ID: <CAB5Fpx4fdGNzBwtiQ4KE2ySkvJ4D224S1_=h-xxdmWi9Z8poAw@mail.gmail.com>

Lester,

Yes, in structured grids in VTK the x dimension changes fastest, then y, then z.

Cory

On Wed, Jun 22, 2016 at 1:15 PM, Lester Anderson <arctica1963 at gmail.com> wrote:
> Think I sorted it by reordering the data:
> sort(z) -> sort(y) -> sort(x) (in Excel)
> Gives the volume rendered properly. So is there a specific ordering
> scheme to follow?
>
> On 22 June 2016 at 10:23, Lester Anderson <arctica1963 at gmail.com> wrote:
>> As a quick note, each layer is ordered bottom left to top right. The
>> region is defined as:
>> west = 117, East = 128.5, South = -11, North = -6
>>
>> On 22 June 2016 at 06:42, Lester Anderson <arctica1963 at gmail.com> wrote:
>>> Hi Ken,
>>>
>>> The data dimensions are: 116 x 51 x 51 (xyz), so the model extent was set to:
>>> X = 0 - 115, Y = 0 - 50, Z = 0 -50
>>> These extents work fine and no errors assciated with the input, and no
>>> missing nodes. The model comprises 51 layers and each is 116 x 51 and
>>> all have the total 5916.
>>>
>>> Not sure what is going on because loading as points is fine.
>>>
>>> On 21 June 2016 at 17:30, Moreland, Kenneth <kmorel at sandia.gov> wrote:
>>>> Lester,
>>>>
>>>> What are the dimensions of the grid in the table? Are they 116x51x51 or 115x50x50?
>>>>
>>>> The extent that you set in the TableToStructuredGrid filter uses inclusive indices. That means they should go from 0 to one less than the size of the dimension. So if your grid is 115x50x50, then the extent should be set as
>>>> X = 0 - 114
>>>> Y = 0 - 49
>>>> Z = 0 - 49
>>>>
>>>> -Ken
>>>>
>>>> -----Original Message-----
>>>> From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Lester Anderson
>>>> Sent: Tuesday, June 21, 2016 9:03 AM
>>>> To: paraview at paraview.org
>>>> Subject: [EXTERNAL] [Paraview] Table to structured grid problem
>>>>
>>>> Hello,
>>>>
>>>> I have tried to generate a structured grid from a csv file comprising
>>>> 51 layers with X and Y as Long and Lat respectively.
>>>>
>>>> (1) Load CSV file
>>>> (2) Filter -> TableToStructuredGrid
>>>> set dimensions:
>>>> x = 0 - 115
>>>> y = 0 - 50
>>>> z = 0 - 50
>>>>
>>>> This all works fine, but the plot is skewed oddly in the gridding, as in the outline view does not show a nice regular shaped outline but rather a jagged edge, almost like it is trying to join points on the front and back faces (see test picture).
>>>>
>>>> TableTo Points worked fine and all points were placed correctly.
>>>>
>>>> Paraview 5.0.0 64-bit Windows
>>>>
>>>> Any ideas what might be going on? I never had this problem before and the CSV file is fine.
>>>>
>>>> Thanks
>>>> Lester
> _______________________________________________
> 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 e.devilliers at engys.com  Wed Jun 22 08:04:05 2016
From: e.devilliers at engys.com (Eugene de Villiers)
Date: Wed, 22 Jun 2016 12:04:05 +0000
Subject: [Paraview]  Minor bug in OPENFOAM import filter
Message-ID: <AM4PR08MB1188BAC0AF0C79B9A3D3BC9B8B2C0@AM4PR08MB1188.eurprd08.prod.outlook.com>

Hi,

We have come across a minor, but annoying bug in the Paraview OPENFOAM reader.

The component of the Paraview OPENFOAM parser that reads boundary conditions has been set up to always expect another number where a scalar is encountered in the following configuration:

(1.111 ###

when you follow a bracket-scalar with another bracket like this

(1.111 (

an exception is thrown and the field is not loaded. However, if the leading number is an integer, then it copes fine:

(1 (###

So it simply doesn't parse a scalar followed by a bracket. Most of such instances are not relevant to the display of data as they concern table inputs for time varying vector boundary conditions. The current workaround is to always use integers in interpolation input tables, but obviously this is not ideal. To reproduce the issue, simply add the following entry to any boundary condition for any volumetric field:

RandomEntry table (1.1 ( 1 2 3));

It will result in an "Error reading line XXX ... " output and the field that the entry was added to will not be loaded. If you change it to:

RandomEntry table (1 ( 1 2 3));

Then it works fine. I can provide a small case that reproduces the issue if the above is not clear.

Best regards,

Eugene de Villiers
e.devilliers at engys.com<mailto:e.devilliers at engys.com>
Mob: +44 (0) 77 89748490
Tel: +44 (0)20 32393041 (ext. 102)
Fax: +44 (0)20 33573123
[logo_red-black_fonts_signature]<http://www.engys.com/>

This message is intended only for the use of the addressee and may contain information that is privileged, confidential and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, or the employee or agent responsible for delivering the message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this e-mail in error, please notify us immediately by return e-mail and delete this e-mail and all attachments from your system.

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

From david.lonie at kitware.com  Wed Jun 22 10:19:30 2016
From: david.lonie at kitware.com (David Lonie)
Date: Wed, 22 Jun 2016 10:19:30 -0400
Subject: [Paraview] Minor bug in OPENFOAM import filter
In-Reply-To: <AM4PR08MB1188BAC0AF0C79B9A3D3BC9B8B2C0@AM4PR08MB1188.eurprd08.prod.outlook.com>
References: <AM4PR08MB1188BAC0AF0C79B9A3D3BC9B8B2C0@AM4PR08MB1188.eurprd08.prod.outlook.com>
Message-ID: <CA+=e1ouj8q447Q0uKPM6WtBPGphMM+Fc=R7hqSzDB6RNE1_A8w@mail.gmail.com>

On Wed, Jun 22, 2016 at 8:04 AM, Eugene de Villiers <e.devilliers at engys.com>
wrote:

> Hi,
>
>
>
> We have come across a minor, but annoying bug in the Paraview OPENFOAM
> reader.
>

Hi Eugene,

I'll take a look at this. I'm not terribly familiar with openfoam files, so
if you could send me that small example to reproduce the bug I'd appreciate
it :)

Thanks,
Dave
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160622/6cc3487e/attachment.html>

From utkarsh.ayachit at kitware.com  Wed Jun 22 11:25:43 2016
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Wed, 22 Jun 2016 11:25:43 -0400
Subject: [Paraview] Can a collaborative client share a pipeline without
 creating a view itself?
In-Reply-To: <CAAUk9C5WDLoKXx58XVCHSQCQycX-TSMM=Y8FuGCU1EJ-e4bhjA@mail.gmail.com>
References: <CAAUk9C7zY8P25QWDeZdcCA7Vx18uiBBe_+_LbyepsFt8FUQaGA@mail.gmail.com>
 <CADHSJjAj5of=VckLN=VCe5KoHhaPqzYck79u=kGLpfrtO3856Q@mail.gmail.com>
 <CAAUk9C5WDLoKXx58XVCHSQCQycX-TSMM=Y8FuGCU1EJ-e4bhjA@mail.gmail.com>
Message-ID: <CADHSJjB1SXkBJZH70bw7ssWupe+ZTckGRcLnhRrfNFcpPvN9xQ@mail.gmail.com>

> can you give a quick update whether the suggested bug fix is likely to be
> solved:

Here you go: https://gitlab.kitware.com/paraview/paraview/merge_requests/844

Once the dashboards come back clean, this will get merged. If do get
around to testing it, I'd suggest getting involved and giving the
merge-request a +1 ;).

Utkarsh

From oshima at eng.niigata-u.ac.jp  Wed Jun 22 11:21:35 2016
From: oshima at eng.niigata-u.ac.jp (Takuya OSHIMA)
Date: Thu, 23 Jun 2016 00:21:35 +0900 (JST)
Subject: [Paraview] Minor bug in OPENFOAM filter
In-Reply-To: <AM4PR08MB1188876E7BD0171D10755DF88B2B0@AM4PR08MB1188.eurprd08.prod.outlook.com>
References: <AM4PR08MB1188876E7BD0171D10755DF88B2B0@AM4PR08MB1188.eurprd08.prod.outlook.com>
Message-ID: <20160623.002135.18399807.oshima@eng.niigata-u.ac.jp>

Hi Eugene and all,

Sorry for not giving a concrete solution but just a comment. The
current reader handles the complex OpenFOAM format without a priori
knowledge of exact format of a specific dictionary entry. With further
growing complexity and format extensions made over OpenFOAM versions,
there can always be such a problem especially when reading entries
required by certain types of boundary conditions. Either implementing
such knowledge or skipping the entire dictionary entries other than
the "value" entries in the boudaryFields could be an idea though.

Takuya OSHIMA, Ph.D.
Faculty of Engineering, Niigata University
8050 Ikarashi-Ninocho, Nishi-ku, Niigata, 950-2181, JAPAN

From: paraview-request at paraview.org
Subject: ParaView Digest, Vol 146, Issue 25
Date: Tue, 21 Jun 2016 12:00:08 -0400

> Hi,
> 
> We have come across a minor but annoying bug in the Paraview OPENFOAM reader.
> 
> The component of the Paraview OPENFOAM parser that reads boundary conditions has been set up to always expect another number where a scalar is encountered in the following configuration:
> 
> (1.111 ###
> 
> when you follow a bracket-scalar with another bracket like this
> 
> (1.111 (
> 
> an exception is thrown and the field is not loaded. However, if the leading number is an integer, then it copes fine:
> 
> (1 (###
> 
> So it simply doesn't parse a scalar followed by a bracket. Most of such instances are not relevant to the display of data as they concern table inputs for time varying vector boundary conditions. The current workaround is to always use integers in interpolation input tables, but obviously this is not ideal. To reproduce the issue, simply add the following entry to any boundary condition for any volumetric field:
> 
> RandomEntry table (1.1 ( 1 2 3));
> 
> It will result in an "Error reading line XXX ... " output and the field that the entry was added to will not be loaded. If you change it to:
> 
> RandomEntry table (1 ( 1 2 3));
> 
> Then it works fine. I can provide a small case that reproduces the issue if the above is not clear.
> 
> Best regards,
> 
> Eugene de Villiers
> e.devilliers at engys.com<mailto:e.devilliers at engys.com>
> Mob: +44 (0) 77 89748490
> Tel: +44 (0)20 32393041 (ext. 102)
> Fax: +44 (0)20 33573123
> [logo_red-black_fonts_signature]<http://www.engys.com/>
> 
> This message is intended only for the use of the addressee and may contain information that is privileged, confidential and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, or the employee or agent responsible for delivering the message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this e-mail in error, please notify us immediately by return e-mail and delete this e-mail and all attachments from your system.
> 

From utkarsh.ayachit at kitware.com  Wed Jun 22 11:43:25 2016
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Wed, 22 Jun 2016 11:43:25 -0400
Subject: [Paraview] XML plugin syntax for FileChooser
In-Reply-To: <CAJ-2Sz3bW=SDML-d9BP61HSy8_Bf7Eynp_ug2gofZ+M3yon8Ew@mail.gmail.com>
References: <CAJ-2Sz0f--EvyaMqVFFYBSJJcMn8LQfMy__-iQrX2_cH95Haig@mail.gmail.com>
 <CAJ-2Sz31NBS00+PEmcSPTY_PJUE9aKwEitBnrQP1wUjPGBqEqg@mail.gmail.com>
 <CAJ-2Sz3kCmOofa=XwMkCX4yy3q74XR+XOsqJaht8r=65pwSedA@mail.gmail.com>
 <CAJ-2Sz3bW=SDML-d9BP61HSy8_Bf7Eynp_ug2gofZ+M3yon8Ew@mail.gmail.com>
Message-ID: <CADHSJjBOH4DR9=+WOGS03Cve_TW1Ch5UgzP5CAZhavhtJgmrWw@mail.gmail.com>

Ah! No, the current implementation doesn't support that, but if you
want to extend the code to do so and push a merge-request on ParaView
(d) -- which would be awesome -- here are a few pointers:

1. Extend pqFileChooserWidget (a) to add support for non-existing files.
2. Extend pqStringVectorPropertyWidget to (b) add support for new
attribute on the <FileChooser /> hint to support non-exisiting files
and if and when it's present, tell pqFileChooseWidget  using the API
added in 1.
3. Update PropertyHints.md (c) to document the new hint attribute added in 2.

Thanks
Utkarsh

(a) https://gitlab.kitware.com/paraview/paraview/blob/master/Qt/Components/pqFileChooserWidget.h
(b) https://gitlab.kitware.com/paraview/paraview/blob/master/Qt/Components/pqStringVectorPropertyWidget.cxx#L173-233
(c) https://gitlab.kitware.com/paraview/paraview/blob/master/Utilities/Doxygen/pages/PropertyHints.md#filechooser
(d) https://gitlab.kitware.com/paraview/paraview


On Wed, Jun 22, 2016 at 2:46 AM, LB <bravo.loic at gmail.com> wrote:
> [Paraview] XML plugin syntax for FileChooser.
>
>
>
> Hi,
>
>
>
> I would like to create a custom programmable python filter  to write some
> calculation results in a file.
>
> I?ve tried to use the following XML plugin syntax to define a FileChooser
> button and help the user select the path of the output file :
>
> <StringVectorProperty
>   label="Path"
>   command="SetParameter"
>   name="QFileName"
>   initial_string="QFileName"
>   number_of_elements="1"
>   panel_visibility="default">
>   <FileListDomain name="files" />
>   <Documentation>Path of the output file</Documentation>
>   <Hints>
>     <FileChooser extensions="inp" file_description="APDL input file" />
>   </Hints>
> </StringVectorProperty>
>
> This create a text field with an associated file chooser button as I wanted.
>
> But it seems that I can only select existing files.
>
> Is-there a way to tell Paraview that this path is an output path and not an
> input path ?
>
> Best regards,
>
>
> _______________________________________________
> 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 e.devilliers at engys.com  Wed Jun 22 11:45:37 2016
From: e.devilliers at engys.com (Eugene de Villiers)
Date: Wed, 22 Jun 2016 15:45:37 +0000
Subject: [Paraview] Minor bug in OPENFOAM import filter
In-Reply-To: <CA+=e1ouj8q447Q0uKPM6WtBPGphMM+Fc=R7hqSzDB6RNE1_A8w@mail.gmail.com>
References: <AM4PR08MB1188BAC0AF0C79B9A3D3BC9B8B2C0@AM4PR08MB1188.eurprd08.prod.outlook.com>
 <CA+=e1ouj8q447Q0uKPM6WtBPGphMM+Fc=R7hqSzDB6RNE1_A8w@mail.gmail.com>
Message-ID: <AM4PR08MB1188DE8BD6DCE85F6005673D8B2C0@AM4PR08MB1188.eurprd08.prod.outlook.com>

Hi Dave,

Sure thing. Attached find a small case. Just load the ?case.foam? file from inside the directory once you have uncompressed it. You will see the error pop up (I am running Paraview 5.0.0).

Thanks for your help,

Eugene



From: David Lonie [mailto:david.lonie at kitware.com]
Sent: 22 June 2016 15:20
To: Eugene de Villiers <e.devilliers at engys.com>
Cc: paraview at paraview.org
Subject: Re: [Paraview] Minor bug in OPENFOAM import filter

On Wed, Jun 22, 2016 at 8:04 AM, Eugene de Villiers <e.devilliers at engys.com<mailto:e.devilliers at engys.com>> wrote:
Hi,

We have come across a minor, but annoying bug in the Paraview OPENFOAM reader.

Hi Eugene,

I'll take a look at this. I'm not terribly familiar with openfoam files, so if you could send me that small example to reproduce the bug I'd appreciate it :)

Thanks,
Dave
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160622/316ee9e3/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: cavity.tar.gz
Type: application/x-gzip
Size: 19567 bytes
Desc: cavity.tar.gz
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160622/316ee9e3/attachment.bin>

From spl at tirebiter.org  Wed Jun 22 11:55:10 2016
From: spl at tirebiter.org (Steve Lamont)
Date: Wed, 22 Jun 2016 08:55:10 -0700
Subject: [Paraview] Map Projection filter
In-Reply-To: <AM4PR08MB1188DE8BD6DCE85F6005673D8B2C0@AM4PR08MB1188.eurprd08.prod.outlook.com>
References: <AM4PR08MB1188BAC0AF0C79B9A3D3BC9B8B2C0@AM4PR08MB1188.eurprd08.prod.outlook.com>
 <CA+=e1ouj8q447Q0uKPM6WtBPGphMM+Fc=R7hqSzDB6RNE1_A8w@mail.gmail.com>
 <AM4PR08MB1188DE8BD6DCE85F6005673D8B2C0@AM4PR08MB1188.eurprd08.prod.outlook.com>
Message-ID: <576AB4DE.1040504@tirebiter.org>

Perhaps I'm just missing it but I can't find any documentation for the 
Map Projection filter.

It looks as if it's producing a Mercator projection but I wouldn't swear 
to it.

Also, is there any way when using it to retain the latitude/longitude 
values for the axes?

Any guidance would be appreciated.

Thanx.

							spl


From e.devilliers at engys.com  Wed Jun 22 11:56:56 2016
From: e.devilliers at engys.com (Eugene de Villiers)
Date: Wed, 22 Jun 2016 15:56:56 +0000
Subject: [Paraview] Minor bug in OPENFOAM filter
In-Reply-To: <20160623.002135.18399807.oshima@eng.niigata-u.ac.jp>
References: <AM4PR08MB1188876E7BD0171D10755DF88B2B0@AM4PR08MB1188.eurprd08.prod.outlook.com>
 <20160623.002135.18399807.oshima@eng.niigata-u.ac.jp>
Message-ID: <AM4PR08MB11885FDECBDA72BA6FD357998B2C0@AM4PR08MB1188.eurprd08.prod.outlook.com>

Hi Takuya!

The problem is that not all boundaries have "value" entries. zeroGradient, fixedGradient, symmetry, empty - none have values. It is a frustrating inconsistency for 3rd-party interfaces, but that's the way it is unfortunately. 

If you want a reasonable and straight-forward solution, I would say check for a "value" entry and if you don't find it assume zero gradient. From our side it is much easier to modify boundaries to write value fields than to change the reader to deal with exceptions and new formats. The "value" entry format is also well defined (i.e. there are only two permutations), so it is easier to support. 

I know nothing about the parser, but I should note that it is entirely possible that multiple "value" keywords might exist in a boundary at different levels of the input structure. It is important that only the first value entry on the base level of the boundary condition is actually identified as the face value correlated "value" entry. So some kind of interpretation of OPENFOAM syntax would be required - a simple pattern-match won't work.

Eugene

-----Original Message-----
From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Takuya OSHIMA
Sent: 22 June 2016 16:22
To: paraview at paraview.org
Subject: Re: [Paraview] Minor bug in OPENFOAM filter

Hi Eugene and all,

Sorry for not giving a concrete solution but just a comment. The current reader handles the complex OpenFOAM format without a priori knowledge of exact format of a specific dictionary entry. With further growing complexity and format extensions made over OpenFOAM versions, there can always be such a problem especially when reading entries required by certain types of boundary conditions. Either implementing such knowledge or skipping the entire dictionary entries other than the "value" entries in the boudaryFields could be an idea though.

Takuya OSHIMA, Ph.D.
Faculty of Engineering, Niigata University
8050 Ikarashi-Ninocho, Nishi-ku, Niigata, 950-2181, JAPAN

From: paraview-request at paraview.org
Subject: ParaView Digest, Vol 146, Issue 25
Date: Tue, 21 Jun 2016 12:00:08 -0400

> Hi,
> 
> We have come across a minor but annoying bug in the Paraview OPENFOAM reader.
> 
> The component of the Paraview OPENFOAM parser that reads boundary conditions has been set up to always expect another number where a scalar is encountered in the following configuration:
> 
> (1.111 ###
> 
> when you follow a bracket-scalar with another bracket like this
> 
> (1.111 (
> 
> an exception is thrown and the field is not loaded. However, if the leading number is an integer, then it copes fine:
> 
> (1 (###
> 
> So it simply doesn't parse a scalar followed by a bracket. Most of such instances are not relevant to the display of data as they concern table inputs for time varying vector boundary conditions. The current workaround is to always use integers in interpolation input tables, but obviously this is not ideal. To reproduce the issue, simply add the following entry to any boundary condition for any volumetric field:
> 
> RandomEntry table (1.1 ( 1 2 3));
> 
> It will result in an "Error reading line XXX ... " output and the field that the entry was added to will not be loaded. If you change it to:
> 
> RandomEntry table (1 ( 1 2 3));
> 
> Then it works fine. I can provide a small case that reproduces the issue if the above is not clear.
> 
> Best regards,
> 
> Eugene de Villiers
> e.devilliers at engys.com<mailto:e.devilliers at engys.com>
> Mob: +44 (0) 77 89748490
> Tel: +44 (0)20 32393041 (ext. 102)
> Fax: +44 (0)20 33573123
> [logo_red-black_fonts_signature]<http://www.engys.com/>
> 
> This message is intended only for the use of the addressee and may contain information that is privileged, confidential and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, or the employee or agent responsible for delivering the message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this e-mail in error, please notify us immediately by return e-mail and delete this e-mail and all attachments from your system.
> 
_______________________________________________
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 apeczak at ara.co.uk  Wed Jun 22 13:25:16 2016
From: apeczak at ara.co.uk (Andrzej Peczak)
Date: Wed, 22 Jun 2016 17:25:16 +0000
Subject: [Paraview] Paraview 5.0.1 - Registering new view
Message-ID: <5DF928D22AC3AC4B964903E98F2E54515B5A7C2D@sooty3.win.ara>

Hi

I am trying to figure out how can I register a new view under a name different  than the default "YXYChartView" which replaces the default representation in Paraview,  but I am either getting the  assertion failure "ASSERT: "pqPreferredView" in file /spare/Andrzej/packages/ParaView-5.0-source/Qt/ApplicationComponents/pqApplyBehavior.cxx, line 277" when 
do things like this 

	<ProxyGroup name="views">
		<ContextViewProxy base_proxygroup="internal_views"
			base_proxyname="ARAXYChartViewBase4Axes" class="ARAPVXYChartViewClass"
			name="ARAXYChartView" label=" My  Line Chart View" processes="client|renderserver|dataserver"
			representation_name="ARAXYChartRepresentation" post_creation="SetChartTypeToLine">
		</ContextViewProxy>		
	</ProxyGroup>

or more specifically like this

	<ProxyGroup name="views">
		<ContextViewProxy base_proxygroup="internal_views"
			base_proxyname="XYChartViewBase4Axes" class="vtkPVXYChartViewClass"
			name="ARAXYChartView" label=" My  Line Chart View" processes="client|renderserver|dataserver"
			representation_name="XYChartRepresentation" post_creation="SetChartTypeToLine">
		</ContextViewProxy>		
	</ProxyGroup>

and then

	<ProxyGroup name="filters">
		<SourceProxy class="vtkPassThrough" label="ARA Plot Data"
			name="ARAPlotAttributes">
			<InputProperty command="SetInputConnection" name="Input">
				<ProxyGroupDomain name="groups">
					<Group name="sources" />
					<Group name="filters" />
				</ProxyGroupDomain>
				<DataTypeDomain name="input_type">
					<DataType value="vtkDataObject" />
				</DataTypeDomain>
				<Documentation>The input.</Documentation>
			</InputProperty>
			<Hints>
				<ShowInMenu category="ARA Extensions" show_in_toolbar="0" />
				<View type="ARAXYChartView" />
				<Plotable />
			</Hints>
		</SourceProxy>
	</ProxyGroup>

Is there a way to register a new view at all ?

Thank you,

Andrzej


**********************************************************************
Please consider the environment. Only print this email if absolutely necessary.

This email contains information that is private and confidential and is intended only for the addressee.
If you are not the intended recipient please delete it and notify us immediately by e-mailing the sender.
Note: All email sent to or from this address may be accessed by someone other than the recipient, for
system management and security reasons.
Aircraft Research Association Ltd.  Registered in England, Registration No 503668 Registered Office:
Manton Lane, Bedford MK41 7PF England VAT No GB 196351245

**********************************************************************

From richard.c.angelini.civ at mail.mil  Wed Jun 22 14:02:38 2016
From: richard.c.angelini.civ at mail.mil (Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US))
Date: Wed, 22 Jun 2016 18:02:38 +0000
Subject: [Paraview] [Non-DoD Source] ANN: ParaView 5.1.0 available for
 download
In-Reply-To: <CADHSJjDNbpmpc5ZQPds6XpiEBsBWS9jd5_fBJ0vzH8ZuNHVg3g@mail.gmail.com>
References: <CADHSJjDNbpmpc5ZQPds6XpiEBsBWS9jd5_fBJ0vzH8ZuNHVg3g@mail.gmail.com>
Message-ID: <D3904AB1.2C19D%Richard.C.Angelini.CIV@mail.mil>

Should there be a tag for v5.1.0 for the Superbuild?    I was looking at
the Superbuild wiki and I should be able to checkout the Superbuild using
a new tag - unless those instructions are now obsolete?


________________________________
Rick Angelini
USArmy Research Laboratory
CISD/HPC Architectures Team
Phone:  410-278-6266




-----Original Message-----
From: ParaView <paraview-bounces at paraview.org> on behalf of Utkarsh
Ayachit <utkarsh.ayachit at kitware.com>
Date: Tuesday, June 21, 2016 at 12:04 PM
To: ParaView <paraview at paraview.org>, ParaView Developers
<paraview-developers at paraview.org>
Subject: [Non-DoD Source] [Paraview] ANN: ParaView 5.1.0 available for
download

All active links contained in this email were disabled.  Please verify the
identity of the sender, and confirm the authenticity of all links
contained within the message prior to copying and pasting the address to a
Web browser.  




----

Folks,

ParaView 5.1.0 is now available for download [1]. Please refer to the
release notes on the Kitware blog [2]. As always, we look forward to
your feedback [3].

Also stay tuned to the Kitware Blog [4] for upcoming features and
enhancements to ParaView, ParaView Catalyst, ParaViewWeb and much
more!

- ParaView Team

[1] Caution-http://www.paraview.org/download/
[2] Caution-https://blog.kitware.com/paraview-5-1-0-release-notes/
[3] Caution-http://paraview.uservoice.com
[4] Caution-https://blog.kitware.com/tag/ParaView/
_______________________________________________
Powered by Caution-www.kitware.com

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

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

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

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


From utkarsh.ayachit at kitware.com  Wed Jun 22 14:20:58 2016
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Wed, 22 Jun 2016 14:20:58 -0400
Subject: [Paraview] [Non-DoD Source] ANN: ParaView 5.1.0 available for
	download
In-Reply-To: <D3904AB1.2C19D%Richard.C.Angelini.CIV@mail.mil>
References: <CADHSJjDNbpmpc5ZQPds6XpiEBsBWS9jd5_fBJ0vzH8ZuNHVg3g@mail.gmail.com>
 <D3904AB1.2C19D%Richard.C.Angelini.CIV@mail.mil>
Message-ID: <CADHSJjBHb2qjX41bitWweEw7vCysA-LCHz-jibCmtQFLdTmDfw@mail.gmail.com>

> Should there be a tag for v5.1.0 for the Superbuild?    I was looking at
> the Superbuild wiki and I should be able to checkout the Superbuild using
> a new tag - unless those instructions are now obsolete?

Doh, I always forget that :). All set.

From corinnareuter75 at gmail.com  Wed Jun 22 15:54:01 2016
From: corinnareuter75 at gmail.com (corinna reuter)
Date: Wed, 22 Jun 2016 21:54:01 +0200
Subject: [Paraview] Automatically updating time variable dataset
In-Reply-To: <CAC2t4UT+5yT47ja=BEs5Pi32QRTd9KA2NO1hCt4HV1+KL4=HRA@mail.gmail.com>
References: <CAOyh2eYmdc2UmjC-aCvLYSk4UGQARJbQgkP5Orc7qmPjniibJQ@mail.gmail.com>
 <CAC2t4UT+5yT47ja=BEs5Pi32QRTd9KA2NO1hCt4HV1+KL4=HRA@mail.gmail.com>
Message-ID: <CAOyh2ebcfP8mW7BDcLJy7XcUBpAXx-4ASQA6vO4i0Bhkj_BvLQ@mail.gmail.com>

This is not practical. We have tried this before. The data are updated in a
background thread, so that data to be displayed are always available
without any delay. The continuous redrawing uses 100% cpu. Even with a
refresh rate reduced to 20 updates per second (sleep commands) cpu usage is
still 70%. Slower refresh rates cause unwanted effects for calculations
that vary quickly. This load is predominantly caused by the communication
overhead and almost independent of the actual rendering work (tested with a
50x50 pixel window and single triangle dataset).

Does anybody have a real solution how a background thread can wake up the
main thread when data has changed? A continuous trigger from the GUI wastes
too many resources. An event based mechanism is needed.

Conny


On Wed, Jun 22, 2016 at 12:59 PM, Mathieu Westphal <
mathieu.westphal at kitware.com> wrote:

> Hello
>
> A work around would be to declare two (fake) timestep in your reader and
> play the animation in loop in paraview.
>
> Regards,
>
> Mathieu Westphal
>
> On Wed, Jun 22, 2016 at 12:51 PM, corinna reuter <
> corinnareuter75 at gmail.com> wrote:
>
>> A question to the specialists:
>> Can Paraview refresh its view automatically when a dataset updates its
>> state?
>>
>> A plugin starts a background thread that calculates new dataset values
>> periodically. Each time a calculation step is finished, all filters and
>> views connected to the generated dataset should be updated. (Something
>> similar is done in a live catalyst connection. But catalyst has a serious
>> drawback for large datasets. It runs in a separate process, so that the
>> datasets cannot be in shared memory, but have to be transferred, requiring
>> redundant storage space and wasted network bandwidth.) Although paraview is
>> said to be not thread safe, it should't be problematic as long as access to
>> VTK classes is limited to the main thread. The difficult question is, how
>> can paraview be notified that a plugin has updated its output while the
>> main thread only waits for GUI or network events when idle?
>>
>> Any ideas or recommendations?
>> Conny
>>
>> _______________________________________________
>> 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/20160622/689c8d3d/attachment.html>

From ben.boeckel at kitware.com  Wed Jun 22 16:29:32 2016
From: ben.boeckel at kitware.com (Ben Boeckel)
Date: Wed, 22 Jun 2016 16:29:32 -0400
Subject: [Paraview] Required CMake version 3.5
In-Reply-To: <1354112273.905026.1466565693599.JavaMail.open-xchange@omgreatgod.store>
References: <14169594.887742.1466533123403.JavaMail.open-xchange@omgreatgod.store>
 <CAB5Fpx5UZOh4QPo8pHx4oG-59A8g2bo=1H3Jm-H5ABRO3079wA@mail.gmail.com>
 <1354112273.905026.1466565693599.JavaMail.open-xchange@omgreatgod.store>
Message-ID: <20160622202932.GA20021@megas.kitware.com>

On Wed, Jun 22, 2016 at 05:21:33 +0200, Christoph Gr?ninger wrote:
> thanks for link to the developer mailing list discussion. I think CMake 3.3 is better then
> 3.5, because at least the last Leap 42.1 release provides that.
> I patched ParaView to require CMake 3.0 and it builds fine. I will package ParaView 5.1
> that way and hope you reduce the requirement to CMake 3.3 for the next time.

I think the easiest way to check this would be to set the minimum to 3.3
and run against 3.5 to see if any POLICY warnings are triggered for the
way openSUSE builds ParaView. If they are, the old version is probably
silently doing something wrong.

--Ben

From utkarsh.ayachit at kitware.com  Wed Jun 22 16:39:13 2016
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Wed, 22 Jun 2016 16:39:13 -0400
Subject: [Paraview] Paraview 5.0.1 - Registering new view
In-Reply-To: <5DF928D22AC3AC4B964903E98F2E54515B5A7C2D@sooty3.win.ara>
References: <5DF928D22AC3AC4B964903E98F2E54515B5A7C2D@sooty3.win.ara>
Message-ID: <CADHSJjD4QNj8aKmA19t6gw0VrqRPiO49tcJZH1RwVpda5r42bA@mail.gmail.com>

You just need to tell ParaView which pqView subclass to create for
your view proxy e.g. if pqContextView class would work for your case,
then you'd add something like the following in your CMakeList.txt

add_pqproxy(OUTIFACES OUTSRCS
   TYPE pqContextView
   XML_GROUP views
   XML_NAME ARAXYChartView)

Utkarsh

On Wed, Jun 22, 2016 at 1:25 PM, Andrzej Peczak <apeczak at ara.co.uk> wrote:
> Hi
>
> I am trying to figure out how can I register a new view under a name different  than the default "YXYChartView" which replaces the default representation in Paraview,  but I am either getting the  assertion failure "ASSERT: "pqPreferredView" in file /spare/Andrzej/packages/ParaView-5.0-source/Qt/ApplicationComponents/pqApplyBehavior.cxx, line 277" when
> do things like this
>
>         <ProxyGroup name="views">
>                 <ContextViewProxy base_proxygroup="internal_views"
>                         base_proxyname="ARAXYChartViewBase4Axes" class="ARAPVXYChartViewClass"
>                         name="ARAXYChartView" label=" My  Line Chart View" processes="client|renderserver|dataserver"
>                         representation_name="ARAXYChartRepresentation" post_creation="SetChartTypeToLine">
>                 </ContextViewProxy>
>         </ProxyGroup>
>
> or more specifically like this
>
>         <ProxyGroup name="views">
>                 <ContextViewProxy base_proxygroup="internal_views"
>                         base_proxyname="XYChartViewBase4Axes" class="vtkPVXYChartViewClass"
>                         name="ARAXYChartView" label=" My  Line Chart View" processes="client|renderserver|dataserver"
>                         representation_name="XYChartRepresentation" post_creation="SetChartTypeToLine">
>                 </ContextViewProxy>
>         </ProxyGroup>
>
> and then
>
>         <ProxyGroup name="filters">
>                 <SourceProxy class="vtkPassThrough" label="ARA Plot Data"
>                         name="ARAPlotAttributes">
>                         <InputProperty command="SetInputConnection" name="Input">
>                                 <ProxyGroupDomain name="groups">
>                                         <Group name="sources" />
>                                         <Group name="filters" />
>                                 </ProxyGroupDomain>
>                                 <DataTypeDomain name="input_type">
>                                         <DataType value="vtkDataObject" />
>                                 </DataTypeDomain>
>                                 <Documentation>The input.</Documentation>
>                         </InputProperty>
>                         <Hints>
>                                 <ShowInMenu category="ARA Extensions" show_in_toolbar="0" />
>                                 <View type="ARAXYChartView" />
>                                 <Plotable />
>                         </Hints>
>                 </SourceProxy>
>         </ProxyGroup>
>
> Is there a way to register a new view at all ?
>
> Thank you,
>
> Andrzej
>
>
> **********************************************************************
> Please consider the environment. Only print this email if absolutely necessary.
>
> This email contains information that is private and confidential and is intended only for the addressee.
> If you are not the intended recipient please delete it and notify us immediately by e-mailing the sender.
> Note: All email sent to or from this address may be accessed by someone other than the recipient, for
> system management and security reasons.
> Aircraft Research Association Ltd.  Registered in England, Registration No 503668 Registered Office:
> Manton Lane, Bedford MK41 7PF England VAT No GB 196351245
>
> **********************************************************************
> _______________________________________________
> 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  Wed Jun 22 16:42:11 2016
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Wed, 22 Jun 2016 16:42:11 -0400
Subject: [Paraview] Transparent background in python scripts
In-Reply-To: <576813D4.8090804@gmail.com>
References: <576813D4.8090804@gmail.com>
Message-ID: <CADHSJjB0UxGvn6jVimh2pEP-7HEN1nTa3aQQg4sHQxEvahUyVA@mail.gmail.com>

Currently, it's not exposed to Python. It's on the TODO list to get
that fixed for 5.2.

On Mon, Jun 20, 2016 at 12:03 PM, Armin Wehrfritz <dkxls23 at gmail.com> wrote:
> Hi!
>
> How can I save screenshots with a transparent (alpha channel based)
> background from a python script?
>
> Currently, I'm using this command to save screenshots:
>>
>> SaveScreenshot('image.png', magnification=3, view=renderView)
>
> But this does not write the alpha channel information.
>
>
> Using "File/ Save Screenshot" in the Paraview GUI, the screenshots
> have the alpha channel information saved correctly when I setting "Edit/
> Settings/ General/ Transparent Background".
>
> I'm using ParaView 5.0.1 on a 64bit Linux workstation with the latest
> Nvidia driver (367.27).
>
>
> -Armin
> _______________________________________________
> 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 timothy.a.beach at nasa.gov  Wed Jun 22 20:43:40 2016
From: timothy.a.beach at nasa.gov (Beach, Timothy A. (GRC-LTE0)[Vantage Partners, LLC])
Date: Thu, 23 Jun 2016 00:43:40 +0000
Subject: [Paraview] need some help reading data in pvpython
Message-ID: <D390AB88.157C8%timothy.a.beach@nasa.gov>

I?ve done some neat stuff with pvpython but I?m stuck on something really basic.  I?ve read a structured multi block dataset(plot3d).  Where do I find the number of blocks and the size of each block.  I?ve been using help and dir() but I haven?t found that info.
Thanks
Tim
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160623/c9adc9dd/attachment.html>

From wascott at sandia.gov  Wed Jun 22 21:38:02 2016
From: wascott at sandia.gov (Scott, W Alan)
Date: Thu, 23 Jun 2016 01:38:02 +0000
Subject: [Paraview] [EXTERNAL] [Paraview-developers] ANN: ParaView 5.1.0
 available for download
In-Reply-To: <CADHSJjDNbpmpc5ZQPds6XpiEBsBWS9jd5_fBJ0vzH8ZuNHVg3g@mail.gmail.com>
References: <CADHSJjDNbpmpc5ZQPds6XpiEBsBWS9jd5_fBJ0vzH8ZuNHVg3g@mail.gmail.com>
Message-ID: <2fe1fffed08b4b6899d47e20ff04fbef@ES01AMSNLNT.srn.sandia.gov>

Very nice.  Pat on the back to the VTK and ParaView developers, and especially Kitware.  Nice help menu and startup screen!

Alan

-----Original Message-----
From: Paraview-developers [mailto:paraview-developers-bounces at paraview.org] On Behalf Of Utkarsh Ayachit
Sent: Tuesday, June 21, 2016 10:05 AM
To: ParaView <paraview at paraview.org>; ParaView Developers <paraview-developers at paraview.org>
Subject: [EXTERNAL] [Paraview-developers] ANN: ParaView 5.1.0 available for download

Folks,

ParaView 5.1.0 is now available for download [1]. Please refer to the release notes on the Kitware blog [2]. As always, we look forward to your feedback [3].

Also stay tuned to the Kitware Blog [4] for upcoming features and enhancements to ParaView, ParaView Catalyst, ParaViewWeb and much more!

- ParaView Team

[1] http://www.paraview.org/download/
[2] https://blog.kitware.com/paraview-5-1-0-release-notes/
[3] http://paraview.uservoice.com
[4] https://blog.kitware.com/tag/ParaView/
_______________________________________________
Powered by www.kitware.com

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

Search the list archives at: http://markmail.org/search/?q=Paraview-developers

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

From mathieu.westphal at kitware.com  Thu Jun 23 08:15:04 2016
From: mathieu.westphal at kitware.com (Mathieu Westphal)
Date: Thu, 23 Jun 2016 14:15:04 +0200
Subject: [Paraview] [Paraview-developers] ParaView bug hackathon
In-Reply-To: <CANjZAi9tCCXc2JOCj3=GnDYQkwi0ZnFjEbso32R2H9P-wtZiQQ@mail.gmail.com>
References: <CAE32kpWcH5N2VNtCrLjAwFebQuqZBsNk4GY=RLKC4dNwY48oVg@mail.gmail.com>
 <CADHSJjA+H=2W2kkseivT-fX4SjdGHqeshm7S4hPhPLxFVzM8Zw@mail.gmail.com>
 <CANjZAi9tCCXc2JOCj3=GnDYQkwi0ZnFjEbso32R2H9P-wtZiQQ@mail.gmail.com>
Message-ID: <CAC2t4UQyndiqNcVJ4xqKByYX-eJXU5BJZeYzqh+7GFw2b+Z4WQ@mail.gmail.com>

Joachim and I will also be remotelly present !



Mathieu Westphal

On Tue, Jun 21, 2016 at 5:40 PM, David E DeMarle <dave.demarle at kitware.com>
wrote:

> I'd like to add review of merge requests to the agenda.
> On Jun 20, 2016 10:57 PM, "Utkarsh Ayachit" <utkarsh.ayachit at kitware.com>
> wrote:
>
>> +1. I will be there.
>>
>> On Mon, Jun 20, 2016 at 4:30 PM, Berk Geveci <berk.geveci at kitware.com>
>> wrote:
>> > Hi folks,
>> >
>> > We are planning a ParaView bug hackathon on July 13. Going forward, we
>> would
>> > like this to be a monthly event during which the community comes
>> together to
>> > address bugs reported to the tracker. It will be an all day event that
>> we
>> > will host physically at Kitware Headquarters in Clifton Park, NY as
>> well as
>> > online via Google Hangout. All are welcome to attend as long as they
>> know
>> > the code base enough to fix bugs.
>> >
>> > Any questions? Comments? Any potential issue with the date?
>> >
>> > Best,
>> > -berk
>> >
>> > _______________________________________________
>> > Powered by www.kitware.com
>> >
>> > Visit other Kitware open-source projects at
>> > http://www.kitware.com/opensource/opensource.html
>> >
>> > Search the list archives at:
>> > http://markmail.org/search/?q=Paraview-developers
>> >
>> > Follow this link to subscribe/unsubscribe:
>> > http://public.kitware.com/mailman/listinfo/paraview-developers
>> >
>> _______________________________________________
>> Powered by www.kitware.com
>>
>> Visit other Kitware open-source projects at
>> http://www.kitware.com/opensource/opensource.html
>>
>> Search the list archives at:
>> http://markmail.org/search/?q=Paraview-developers
>>
>> Follow this link to subscribe/unsubscribe:
>> http://public.kitware.com/mailman/listinfo/paraview-developers
>>
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Search the list archives at:
> http://markmail.org/search/?q=Paraview-developers
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview-developers
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160623/d75fde1c/attachment.html>

From foss at grueninger.de  Thu Jun 23 10:20:14 2016
From: foss at grueninger.de (=?UTF-8?Q?Christoph_Gr=C3=BCninger?=)
Date: Thu, 23 Jun 2016 16:20:14 +0200 (CEST)
Subject: [Paraview] Required CMake version 3.5
In-Reply-To: <20160622202932.GA20021@megas.kitware.com>
References: <14169594.887742.1466533123403.JavaMail.open-xchange@omgreatgod.store>
 <CAB5Fpx5UZOh4QPo8pHx4oG-59A8g2bo=1H3Jm-H5ABRO3079wA@mail.gmail.com>
 <1354112273.905026.1466565693599.JavaMail.open-xchange@omgreatgod.store>
 <20160622202932.GA20021@megas.kitware.com>
Message-ID: <1828645824.1045733.1466691614734.JavaMail.open-xchange@patina.store>

Hi Ben,

> I think the easiest way to check this would be to set the minimum to 3.3
> and run against 3.5 to see if any POLICY warnings are triggered for the
> way openSUSE builds ParaView. If they are, the old version is probably
> silently doing something wrong.

I just did exactly that, no warning from CMake occurs. So we can assume
everything would be fine with CMake 3.3. Should I create an according
Github merge request?

Bye
Christoph

From b.gazanion at gantha.com  Thu Jun 23 10:13:16 2016
From: b.gazanion at gantha.com (Bertrand Gazanion)
Date: Thu, 23 Jun 2016 16:13:16 +0200
Subject: [Paraview] Find points within radius
Message-ID: <002c01d1cd59$634dedd0$29e9c970$@gazanion@gantha.com>

Forgot the pictures... Sorry for the spam.

Bertrand

 

De : Bertrand Gazanion [mailto:b.gazanion at gantha.com] 
Envoy? : jeudi 23 juin 2016 16:11
? : 'paraview at paraview.org'
Objet : Find points within radius

 

On behalf of a colleague of mine working with ParaView 4.3.1

 

Hello,


I am using an algorithm doing calculation on points and their neighbours and
I find the results of those points locators to be strange. To test it I made
a simple algorithm counting how many neighbours each point has.
When I create a plane and set its x and y resolution to 100 each, all points
should have the same number of neighbours except on the sides. However
vtkPointLocator, vtkKdTreePointLocator and vtkOctreePointLocator do not find
the same number of neighbours for each point.

Here is the algorithm that I use to get the number of neighbors each points
has :
import vtk

pdi = self.GetInputDataObject(0,0)
nb_pts = pdi.GetNumberOfPoints()

# Point locator
loc = vtk.vtkPointLocator()
#loc = vtk.vtkOctreePointLocator()
#loc = vtk. vtkKdTreePointLocator()

loc.SetDataSet(pdi)
loc.BuildLocator()

pts = pdi.GetPoints()

neighbours = vtk.vtkTypeInt64Array()
neighbours.SetNumberOfComponents(1)
neighbours.SetNumberOfTuples(nb_pts)
neighbours.SetName('neighbours')

for k in range(nb_pts):

    xp = pdi.GetPoint(k)

    id_list = vtk.vtkIdList()

    loc.FindPointsWithinRadius(0.01,xp,id_list)
    loc.Update()

    N = id_list.GetNumberOfIds()
    neighbours.InsertTuple1(k,N)


self.GetOutput().GetPointData().AddArray(neighbours)

 

You will find attached sample picture describing the result I get with each
point locator.

thank you very much

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160623/c5174453/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: vtkPointLocator.png
Type: image/png
Size: 27606 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160623/c5174453/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: vtkKdTreePointLocator.png
Type: image/png
Size: 27709 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160623/c5174453/attachment-0001.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: vtkOctreePointLocator.png
Type: image/png
Size: 24031 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160623/c5174453/attachment-0002.png>

From kmorel at sandia.gov  Thu Jun 23 11:11:22 2016
From: kmorel at sandia.gov (Moreland, Kenneth)
Date: Thu, 23 Jun 2016 15:11:22 +0000
Subject: [Paraview] Find points within radius
Message-ID: <82b57ab76af748eeba6c5f91a1cbc743@ES08AMSNLNT.srn.sandia.gov>

The problem you are facing is with the precision of floating point numbers. The way you are setting up your problem is that the points are exactly 0.01 units away from each other. When you ask the point locator for all points within a radius of 0.01, then what happens when a point is exactly 0.01 units away from the center? That depends on what happens in the limited precision of your computer's floating point values. Sometimes it will be 0.01 + epsilon, in which case the point will be considered inside the radius. Sometimes it will be 0.01 - epsilon, in which case the point will be considered outside the radius. This is a well known issue with floating point numbers. There are lots of resources describing it. A quick Google search gave this article: https://docs.oracle.com/cd/E19957-01/806-3568/ncg_goldberg.html.

Anyway, the simple solution is to increase the radius in FindPointsWithinRadius by a small amount. Changing the line to:

    loc.FindPointsWithinRadius(0.01,xp,id_list)

fixes the problem for all point locators.

BTW, although perhaps convenient, using a point locator to find neighbors is not the most robust way to do it. It would be safer to use the find neighbor facilities of the different vtkDataSet classes.

-Ken

From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Bertrand Gazanion
Sent: Thursday, June 23, 2016 8:13 AM
To: paraview at paraview.org
Subject: [EXTERNAL] Re: [Paraview] Find points within radius

Forgot the pictures... Sorry for the spam.
Bertrand

De : Bertrand Gazanion [mailto:b.gazanion at gantha.com]
Envoy? : jeudi 23 juin 2016 16:11
? : 'paraview at paraview.org'
Objet : Find points within radius

On behalf of a colleague of mine working with ParaView 4.3.1

Hello,

I am using an algorithm doing calculation on points and their neighbours and I find the results of those points locators to be strange. To test it I made a simple algorithm counting how many neighbours each point has.
When I create a plane and set its x and y resolution to 100 each, all points should have the same number of neighbours except on the sides. However vtkPointLocator, vtkKdTreePointLocator and vtkOctreePointLocator do not find the same number of neighbours for each point.

Here is the algorithm that I use to get the number of neighbors each points has :
import vtk

pdi = self.GetInputDataObject(0,0)
nb_pts = pdi.GetNumberOfPoints()

# Point locator
loc = vtk.vtkPointLocator()
#loc = vtk.vtkOctreePointLocator()
#loc = vtk. vtkKdTreePointLocator()

loc.SetDataSet(pdi)
loc.BuildLocator()

pts = pdi.GetPoints()

neighbours = vtk.vtkTypeInt64Array()
neighbours.SetNumberOfComponents(1)
neighbours.SetNumberOfTuples(nb_pts)
neighbours.SetName('neighbours')

for k in range(nb_pts):

    xp = pdi.GetPoint(k)

    id_list = vtk.vtkIdList()

    loc.FindPointsWithinRadius(0.01,xp,id_list)
    loc.Update()

    N = id_list.GetNumberOfIds()
    neighbours.InsertTuple1(k,N)


self.GetOutput().GetPointData().AddArray(neighbours)

You will find attached sample picture describing the result I get with each point locator.

thank you very much
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160623/dca87e8b/attachment.html>

From b.gazanion at gantha.com  Thu Jun 23 10:10:57 2016
From: b.gazanion at gantha.com (Bertrand Gazanion)
Date: Thu, 23 Jun 2016 16:10:57 +0200
Subject: [Paraview] Find points within radius
Message-ID: <002701d1cd59$1129cab0$337d6010$@gazanion@gantha.com>

On behalf of a colleague of mine working with ParaView 4.3.1

 

Hello,


I am using an algorithm doing calculation on points and their neighbours and
I find the results of those points locators to be strange. To test it I made
a simple algorithm counting how many neighbours each point has.
When I create a plane and set its x and y resolution to 100 each, all points
should have the same number of neighbours except on the sides. However
vtkPointLocator, vtkKdTreePointLocator and vtkOctreePointLocator do not find
the same number of neighbours for each point.

Here is the algorithm that I use to get the number of neighbors each points
has :
import vtk

pdi = self.GetInputDataObject(0,0)
nb_pts = pdi.GetNumberOfPoints()

# Point locator
loc = vtk.vtkPointLocator()
#loc = vtk.vtkOctreePointLocator()
#loc = vtk. vtkKdTreePointLocator()

loc.SetDataSet(pdi)
loc.BuildLocator()

pts = pdi.GetPoints()

neighbours = vtk.vtkTypeInt64Array()
neighbours.SetNumberOfComponents(1)
neighbours.SetNumberOfTuples(nb_pts)
neighbours.SetName('neighbours')

for k in range(nb_pts):

    xp = pdi.GetPoint(k)

    id_list = vtk.vtkIdList()

    loc.FindPointsWithinRadius(0.01,xp,id_list)
    loc.Update()

    N = id_list.GetNumberOfIds()
    neighbours.InsertTuple1(k,N)


self.GetOutput().GetPointData().AddArray(neighbours)

 

You will find attached sample picture describing the result I get with each
point locator.

thank you very much

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

From utkarsh.ayachit at kitware.com  Thu Jun 23 11:45:14 2016
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Thu, 23 Jun 2016 11:45:14 -0400
Subject: [Paraview] need some help reading data in pvpython
In-Reply-To: <D390AB88.157C8%timothy.a.beach@nasa.gov>
References: <D390AB88.157C8%timothy.a.beach@nasa.gov>
Message-ID: <CADHSJjCjoiGS=R5w=ZRzHDc5Eevr-aOADCQ8yRk4+Fxu=CBDnQ@mail.gmail.com>

Here's a snippet:

reader = ...
di = reader.GetDataInformation()
numDatasets = di.GetNumberOfDataSets()
for i in range(numDatasets):
    blockDI = di.GetCompositeDataInformation().GetDataInformation(i)
    print i, "Num Points", blockDI.GetNumberOfPoints()
    print i, "Num Cells", blockDI.GetNumberOfCells()

Utkarsh

On Wed, Jun 22, 2016 at 8:43 PM, Beach, Timothy A. (GRC-LTE0)[Vantage
Partners, LLC] <timothy.a.beach at nasa.gov> wrote:
> I?ve done some neat stuff with pvpython but I?m stuck on something really
> basic.  I?ve read a structured multi block dataset(plot3d).  Where do I find
> the number of blocks and the size of each block.  I?ve been using help and
> dir() but I haven?t found that info.
> Thanks
> Tim
>
> _______________________________________________
> 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 dennis_conklin at goodyear.com  Thu Jun 23 10:48:40 2016
From: dennis_conklin at goodyear.com (Dennis Conklin)
Date: Thu, 23 Jun 2016 14:48:40 +0000
Subject: [Paraview] ANN: ParaView 5.1.0 available for download
Message-ID: <CY1PR07MB2506AB8938D6EAA0258A31A79F2D0@CY1PR07MB2506.namprd07.prod.outlook.com>

Utkarsh, et al.,

There is a problem with missing cell variables in v5.1.

To replicate it load bake.e.    In v4.4 and v5.0.1, there are 3 cell variables, Object IDs, Global Element IDs, and processor_id, which can be loaded from the file.

In v5.1, there are only 2 cell variables available for loading,  Object IDs, and Global Element IDs.

In my case I have ~60 cell variables which are missing and only Object IDs and Global Element IDs are available to load.

This makes v5.1 unusable for us.

Dennis
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160623/01dc709e/attachment.html>

From utkarsh.ayachit at kitware.com  Thu Jun 23 12:58:32 2016
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Thu, 23 Jun 2016 12:58:32 -0400
Subject: [Paraview] ANN: ParaView 5.1.0 available for download
In-Reply-To: <CY1PR07MB2506AB8938D6EAA0258A31A79F2D0@CY1PR07MB2506.namprd07.prod.outlook.com>
References: <CY1PR07MB2506AB8938D6EAA0258A31A79F2D0@CY1PR07MB2506.namprd07.prod.outlook.com>
Message-ID: <CADHSJjAGSCrSA9i7beOc73zxcTqTupvaVg-Eu6HbN9-skrP3HQ@mail.gmail.com>

> To replicate it load bake.e.    In v4.4 and v5.0.1, there are 3 cell
> variables, Object IDs, Global Element IDs, and processor_id, which can be
> loaded from the file.

Could not reproduce this (see attached image). Can you try running with "-dr"?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Screenshot from 2016-06-23 12-57-24.png
Type: image/png
Size: 25228 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160623/dbe47482/attachment.png>

From dwneumann at gmail.com  Thu Jun 23 14:38:59 2016
From: dwneumann at gmail.com (Dean Neumann)
Date: Thu, 23 Jun 2016 11:38:59 -0700
Subject: [Paraview] SyntaxError reported parsing Python Calculator ?
Message-ID: <CAGgSO3jX7Lnkz5yiHWJCQK8dPKLEQ-V9A2BzGKKWU6F3NcMkiA@mail.gmail.com>

on my paraview 5.0.1 64-bit on Windows-7
(from precompiled distribution at paraview.org)

What is the reason that I get the following errors when instantiating a
Python Calculator filter on a single input of type UnstructuredGrid:

Traceback (most recent call last):

File "<string>", line 4, in <module>

File "C:\Program
Files\ParaView\lib\paraview-5.0\site-packages\paraview\calculator.py", line
102, in execute

retVal = compute(inputs, expression, ns=variables)

File "C:\Program
Files\ParaView\lib\paraview-5.0\site-packages\paraview\calculator.py", line
74, in compute

retVal = eval(expression, globals(), mylocals)

File "<string>", line 0

^

SyntaxError: unexpected EOF while parsing


What is being parsed?   The filter input is an internal paraview data set.
The input was active at the time the filter was instantiated.  The error
occurs as soon as the filter is selected and added to the pipeline.
I can attach the input dataset if requested.
Thanks.

Dean Neumann

CEO,  Malaspina Labs Inc.

www.malaspina-labs.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160623/e80126d8/attachment.html>

From guilfordstuff at gmail.com  Thu Jun 23 16:32:04 2016
From: guilfordstuff at gmail.com (Jim)
Date: Thu, 23 Jun 2016 16:32:04 -0400
Subject: [Paraview] Scalar scaling of glyphs causes unrecoverable error
Message-ID: <576C4744.9030301@gmail.com>

I can import (raw binary) a 3D file (1178x1202x1000x1float), extract a 
subset and display it using sphere glyphs where the spheres are too 
large. However, when I set the scale mode to scalar and 1, the program 
displays nothing. The display area is just background color. I can't 
turn anything on or off. If I delete everything and then retry without 
the scaling, I still see nothing.

This looks like some sort of workspace corruption.  It looks like a bug 
to me.

From cory.quammen at kitware.com  Thu Jun 23 18:25:00 2016
From: cory.quammen at kitware.com (Cory Quammen)
Date: Fri, 24 Jun 2016 00:25:00 +0200
Subject: [Paraview] Required CMake version 3.5
In-Reply-To: <1828645824.1045733.1466691614734.JavaMail.open-xchange@patina.store>
References: <14169594.887742.1466533123403.JavaMail.open-xchange@omgreatgod.store>
 <CAB5Fpx5UZOh4QPo8pHx4oG-59A8g2bo=1H3Jm-H5ABRO3079wA@mail.gmail.com>
 <1354112273.905026.1466565693599.JavaMail.open-xchange@omgreatgod.store>
 <20160622202932.GA20021@megas.kitware.com>
 <1828645824.1045733.1466691614734.JavaMail.open-xchange@patina.store>
Message-ID: <CAB5Fpx5+RaKdPPzWJhfBb=zkq7VtDpifFFYzJoNG-1TEfAwiVw@mail.gmail.com>

On Thu, Jun 23, 2016 at 4:20 PM, Christoph Gr?ninger <foss at grueninger.de> wrote:
> Hi Ben,
>
>> I think the easiest way to check this would be to set the minimum to 3.3
>> and run against 3.5 to see if any POLICY warnings are triggered for the
>> way openSUSE builds ParaView. If they are, the old version is probably
>> silently doing something wrong.
>
> I just did exactly that, no warning from CMake occurs. So we can assume
> everything would be fine with CMake 3.3. Should I create an according
> Github merge request?

Sure, sounds like a plan.

@Utkarsh, any foreseeable problems reducing the CMake required version to 3.3?

@Ben, I assume all the dashboard machines are running CMake 3.5. Do
you think we should downgrade one to CMake 3.3?

Thanks,
Cory

>
> Bye
> Christoph
> _______________________________________________
> 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  Thu Jun 23 18:39:40 2016
From: cory.quammen at kitware.com (Cory Quammen)
Date: Fri, 24 Jun 2016 00:39:40 +0200
Subject: [Paraview] SyntaxError reported parsing Python Calculator ?
In-Reply-To: <CAGgSO3jX7Lnkz5yiHWJCQK8dPKLEQ-V9A2BzGKKWU6F3NcMkiA@mail.gmail.com>
References: <CAGgSO3jX7Lnkz5yiHWJCQK8dPKLEQ-V9A2BzGKKWU6F3NcMkiA@mail.gmail.com>
Message-ID: <CAB5Fpx4oxO9J27j5f7WUJiZhy7y_nFx0XNQnm1Jz1tVwADgGpQ@mail.gmail.com>

Dean,

Do you have "Auto Apply" on? This may be leading to the problem - this
filter is added to the pipeline and the Apply button is effectively
pressed right away while the Python Calculator expression is empty.
Having "Auto Apply" on, I can reproduce the error message you get.

Can you try disabling "Auto Apply" and report how that goes? We really
should handle the empty expression better for this very case.

Thanks,
Cory

On Thu, Jun 23, 2016 at 8:38 PM, Dean Neumann <dwneumann at gmail.com> wrote:
> on my paraview 5.0.1 64-bit on Windows-7
> (from precompiled distribution at paraview.org)
>
> What is the reason that I get the following errors when instantiating a
> Python Calculator filter on a single input of type UnstructuredGrid:
>
> Traceback (most recent call last):
>
> File "<string>", line 4, in <module>
>
> File "C:\Program
> Files\ParaView\lib\paraview-5.0\site-packages\paraview\calculator.py", line
> 102, in execute
>
> retVal = compute(inputs, expression, ns=variables)
>
> File "C:\Program
> Files\ParaView\lib\paraview-5.0\site-packages\paraview\calculator.py", line
> 74, in compute
>
> retVal = eval(expression, globals(), mylocals)
>
> File "<string>", line 0
>
> ^
>
> SyntaxError: unexpected EOF while parsing
>
>
> What is being parsed?   The filter input is an internal paraview data set.
> The input was active at the time the filter was instantiated.  The error
> occurs as soon as the filter is selected and added to the pipeline.
> I can attach the input dataset if requested.
> Thanks.
>
> Dean Neumann
>
> CEO,  Malaspina Labs Inc.
>
> www.malaspina-labs.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
>



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

From cory.quammen at kitware.com  Thu Jun 23 18:42:58 2016
From: cory.quammen at kitware.com (Cory Quammen)
Date: Fri, 24 Jun 2016 00:42:58 +0200
Subject: [Paraview] SyntaxError reported parsing Python Calculator ?
In-Reply-To: <CAB5Fpx4oxO9J27j5f7WUJiZhy7y_nFx0XNQnm1Jz1tVwADgGpQ@mail.gmail.com>
References: <CAGgSO3jX7Lnkz5yiHWJCQK8dPKLEQ-V9A2BzGKKWU6F3NcMkiA@mail.gmail.com>
 <CAB5Fpx4oxO9J27j5f7WUJiZhy7y_nFx0XNQnm1Jz1tVwADgGpQ@mail.gmail.com>
Message-ID: <CAB5Fpx4=OzQgjxDMKmCRBQ=Q0vD4Jstv4z1iAByXwJd30zRa0A@mail.gmail.com>

Turns out there is an existing related bug in the bug tracker:

http://www.paraview.org/Bug/view.php?id=15923

On Fri, Jun 24, 2016 at 12:39 AM, Cory Quammen <cory.quammen at kitware.com> wrote:
> Dean,
>
> Do you have "Auto Apply" on? This may be leading to the problem - this
> filter is added to the pipeline and the Apply button is effectively
> pressed right away while the Python Calculator expression is empty.
> Having "Auto Apply" on, I can reproduce the error message you get.
>
> Can you try disabling "Auto Apply" and report how that goes? We really
> should handle the empty expression better for this very case.
>
> Thanks,
> Cory
>
> On Thu, Jun 23, 2016 at 8:38 PM, Dean Neumann <dwneumann at gmail.com> wrote:
>> on my paraview 5.0.1 64-bit on Windows-7
>> (from precompiled distribution at paraview.org)
>>
>> What is the reason that I get the following errors when instantiating a
>> Python Calculator filter on a single input of type UnstructuredGrid:
>>
>> Traceback (most recent call last):
>>
>> File "<string>", line 4, in <module>
>>
>> File "C:\Program
>> Files\ParaView\lib\paraview-5.0\site-packages\paraview\calculator.py", line
>> 102, in execute
>>
>> retVal = compute(inputs, expression, ns=variables)
>>
>> File "C:\Program
>> Files\ParaView\lib\paraview-5.0\site-packages\paraview\calculator.py", line
>> 74, in compute
>>
>> retVal = eval(expression, globals(), mylocals)
>>
>> File "<string>", line 0
>>
>> ^
>>
>> SyntaxError: unexpected EOF while parsing
>>
>>
>> What is being parsed?   The filter input is an internal paraview data set.
>> The input was active at the time the filter was instantiated.  The error
>> occurs as soon as the filter is selected and added to the pipeline.
>> I can attach the input dataset if requested.
>> Thanks.
>>
>> Dean Neumann
>>
>> CEO,  Malaspina Labs Inc.
>>
>> www.malaspina-labs.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
>>
>
>
>
> --
> Cory Quammen
> R&D Engineer
> Kitware, Inc.



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

From peterdebuchev at gmail.com  Fri Jun 24 01:08:32 2016
From: peterdebuchev at gmail.com (Peter Debuchev)
Date: Fri, 24 Jun 2016 07:08:32 +0200
Subject: [Paraview] Can a collaborative client share a pipeline without
 creating a view itself?
In-Reply-To: <CADHSJjB1SXkBJZH70bw7ssWupe+ZTckGRcLnhRrfNFcpPvN9xQ@mail.gmail.com>
References: <CAAUk9C7zY8P25QWDeZdcCA7Vx18uiBBe_+_LbyepsFt8FUQaGA@mail.gmail.com>
 <CADHSJjAj5of=VckLN=VCe5KoHhaPqzYck79u=kGLpfrtO3856Q@mail.gmail.com>
 <CAAUk9C5WDLoKXx58XVCHSQCQycX-TSMM=Y8FuGCU1EJ-e4bhjA@mail.gmail.com>
 <CADHSJjB1SXkBJZH70bw7ssWupe+ZTckGRcLnhRrfNFcpPvN9xQ@mail.gmail.com>
Message-ID: <CAAUk9C7mO1TEqzeU+HwJKk7mefmDdMq5M11eoAHSSXLd3A1HvQ@mail.gmail.com>

Thank you for the patch. There is still something missing. If I modify the
custom client such that it adds an object every half second or so, then
first start this clients and then ParaView after a few seconds, ParaView
misses one of the objects. ParaView finds those objects that are added
before ParaView starts and those that are added later. But during ParaView
startup one of the objects is lost.
I'll see if I can make this reproducible and send a code example in the
next days.

Peter

2016-06-22 17:25 GMT+02:00 Utkarsh Ayachit <utkarsh.ayachit at kitware.com>:

> > can you give a quick update whether the suggested bug fix is likely to be
> > solved:
>
> Here you go:
> https://gitlab.kitware.com/paraview/paraview/merge_requests/844
>
> Once the dashboards come back clean, this will get merged. If do get
> around to testing it, I'd suggest getting involved and giving the
> merge-request a +1 ;).
>
> Utkarsh
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160624/a8d2342c/attachment.html>

From apeczak at ara.co.uk  Fri Jun 24 05:46:52 2016
From: apeczak at ara.co.uk (Andrzej Peczak)
Date: Fri, 24 Jun 2016 09:46:52 +0000
Subject: [Paraview] Paraview 5.0.1 - Registering new view
In-Reply-To: <CADHSJjD4QNj8aKmA19t6gw0VrqRPiO49tcJZH1RwVpda5r42bA@mail.gmail.com>
References: <5DF928D22AC3AC4B964903E98F2E54515B5A7C2D@sooty3.win.ara> 
 <CADHSJjD4QNj8aKmA19t6gw0VrqRPiO49tcJZH1RwVpda5r42bA@mail.gmail.com>
Message-ID: <5DF928D22AC3AC4B964903E98F2E54515B5B53CE@sooty3.win.ara>

Thank you so much Utkarsh, this is the function I was looking for.

Andrzej

-----Original Message-----
From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] 
Sent: 22 June 2016 21:39
To: Andrzej Peczak
Cc: paraview at paraview.org
Subject: Re: [Paraview] Paraview 5.0.1 - Registering new view

You just need to tell ParaView which pqView subclass to create for your view proxy e.g. if pqContextView class would work for your case, then you'd add something like the following in your CMakeList.txt

add_pqproxy(OUTIFACES OUTSRCS
   TYPE pqContextView
   XML_GROUP views
   XML_NAME ARAXYChartView)

Utkarsh

On Wed, Jun 22, 2016 at 1:25 PM, Andrzej Peczak <apeczak at ara.co.uk> wrote:
> Hi
>
> I am trying to figure out how can I register a new view under a name 
> different  than the default "YXYChartView" which replaces the default 
> representation in Paraview,  but I am either getting the  assertion 
> failure "ASSERT: "pqPreferredView" in file 
> /spare/Andrzej/packages/ParaView-5.0-source/Qt/ApplicationComponents/p
> qApplyBehavior.cxx, line 277" when do things like this
>
>         <ProxyGroup name="views">
>                 <ContextViewProxy base_proxygroup="internal_views"
>                         base_proxyname="ARAXYChartViewBase4Axes" class="ARAPVXYChartViewClass"
>                         name="ARAXYChartView" label=" My  Line Chart View" processes="client|renderserver|dataserver"
>                         representation_name="ARAXYChartRepresentation" post_creation="SetChartTypeToLine">
>                 </ContextViewProxy>
>         </ProxyGroup>
>
> or more specifically like this
>
>         <ProxyGroup name="views">
>                 <ContextViewProxy base_proxygroup="internal_views"
>                         base_proxyname="XYChartViewBase4Axes" class="vtkPVXYChartViewClass"
>                         name="ARAXYChartView" label=" My  Line Chart View" processes="client|renderserver|dataserver"
>                         representation_name="XYChartRepresentation" post_creation="SetChartTypeToLine">
>                 </ContextViewProxy>
>         </ProxyGroup>
>
> and then
>
>         <ProxyGroup name="filters">
>                 <SourceProxy class="vtkPassThrough" label="ARA Plot Data"
>                         name="ARAPlotAttributes">
>                         <InputProperty command="SetInputConnection" name="Input">
>                                 <ProxyGroupDomain name="groups">
>                                         <Group name="sources" />
>                                         <Group name="filters" />
>                                 </ProxyGroupDomain>
>                                 <DataTypeDomain name="input_type">
>                                         <DataType value="vtkDataObject" />
>                                 </DataTypeDomain>
>                                 <Documentation>The input.</Documentation>
>                         </InputProperty>
>                         <Hints>
>                                 <ShowInMenu category="ARA Extensions" show_in_toolbar="0" />
>                                 <View type="ARAXYChartView" />
>                                 <Plotable />
>                         </Hints>
>                 </SourceProxy>
>         </ProxyGroup>
>
> Is there a way to register a new view at all ?
>
> Thank you,
>
> Andrzej
>
>
> **********************************************************************
> Please consider the environment. Only print this email if absolutely necessary.
>
> This email contains information that is private and confidential and is intended only for the addressee.
> If you are not the intended recipient please delete it and notify us immediately by e-mailing the sender.
> Note: All email sent to or from this address may be accessed by 
> someone other than the recipient, for system management and security reasons.
> Aircraft Research Association Ltd.  Registered in England, Registration No 503668 Registered Office:
> Manton Lane, Bedford MK41 7PF England VAT No GB 196351245
>
> **********************************************************************
> _______________________________________________
> 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

**********************************************************************
Please consider the environment. Only print this email if absolutely necessary.

This email contains information that is private and confidential and is intended only for the addressee.
If you are not the intended recipient please delete it and notify us immediately by e-mailing the sender.
Note: All email sent to or from this address may be accessed by someone other than the recipient, for
system management and security reasons.
Aircraft Research Association Ltd.  Registered in England, Registration No 503668 Registered Office:
Manton Lane, Bedford MK41 7PF England VAT No GB 196351245

**********************************************************************

From rccm.kyoshimi at gmail.com  Fri Jun 24 06:37:35 2016
From: rccm.kyoshimi at gmail.com (kenichiro yoshimi)
Date: Fri, 24 Jun 2016 19:37:35 +0900
Subject: [Paraview] Question mark button launches a blank window with 5.1.0
Message-ID: <CAHDyfPDpFqhs_GCKC=9orYxyamrBG6phn=nW+UeP-twMWEPLfw@mail.gmail.com>

Hi all,

I use ParaView 5.1.0 version installed from a binary file
ParaView-5.1.0-Qt4-OpenGL2-Windows-64bit.exe. Unfortunately, this version's
"ParaView Online Help" launched by clicking on Question mark button is not
available because
the opened window is blank. This problem did not occur with 5.0.1 version.

Best Regards,
yoshimi kenichiro
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160624/3070edc6/attachment.html>

From ben.boeckel at kitware.com  Fri Jun 24 09:23:57 2016
From: ben.boeckel at kitware.com (Ben Boeckel)
Date: Fri, 24 Jun 2016 09:23:57 -0400
Subject: [Paraview] Required CMake version 3.5
In-Reply-To: <CAB5Fpx5+RaKdPPzWJhfBb=zkq7VtDpifFFYzJoNG-1TEfAwiVw@mail.gmail.com>
References: <14169594.887742.1466533123403.JavaMail.open-xchange@omgreatgod.store>
 <CAB5Fpx5UZOh4QPo8pHx4oG-59A8g2bo=1H3Jm-H5ABRO3079wA@mail.gmail.com>
 <1354112273.905026.1466565693599.JavaMail.open-xchange@omgreatgod.store>
 <20160622202932.GA20021@megas.kitware.com>
 <1828645824.1045733.1466691614734.JavaMail.open-xchange@patina.store>
 <CAB5Fpx5+RaKdPPzWJhfBb=zkq7VtDpifFFYzJoNG-1TEfAwiVw@mail.gmail.com>
Message-ID: <20160624132357.GA21782@megas.kitware.com>

On Fri, Jun 24, 2016 at 00:25:00 +0200, Cory Quammen wrote:
> @Utkarsh, any foreseeable problems reducing the CMake required version to 3.3?

I think we'll want 3.5 in the (hopefully) near future, so if
distributions don't have a new enough CMake, they can patch it down to
3.3 in the meantime. A comment might be worthwhile.

Though I question the distro update policies surrounding where ParaView
is aggressively pushed forward when CMake isn't. CMake is *much* better
with its backwards compatibility, but I guess it's down to maintainer
style to some extent.

> @Ben, I assume all the dashboard machines are running CMake 3.5. Do
> you think we should downgrade one to CMake 3.3?

I was actually going to upgrade them to 3.6's rc today to test it out.

--Ben

From guilfordstuff at gmail.com  Fri Jun 24 09:28:29 2016
From: guilfordstuff at gmail.com (Jim)
Date: Fri, 24 Jun 2016 09:28:29 -0400
Subject: [Paraview] Required CMake version 3.5
In-Reply-To: <20160624132357.GA21782@megas.kitware.com>
References: <14169594.887742.1466533123403.JavaMail.open-xchange@omgreatgod.store>
 <CAB5Fpx5UZOh4QPo8pHx4oG-59A8g2bo=1H3Jm-H5ABRO3079wA@mail.gmail.com>
 <1354112273.905026.1466565693599.JavaMail.open-xchange@omgreatgod.store>
 <20160622202932.GA20021@megas.kitware.com>
 <1828645824.1045733.1466691614734.JavaMail.open-xchange@patina.store>
 <CAB5Fpx5+RaKdPPzWJhfBb=zkq7VtDpifFFYzJoNG-1TEfAwiVw@mail.gmail.com>
 <20160624132357.GA21782@megas.kitware.com>
Message-ID: <576D357D.40601@gmail.com>

On 06/24/2016 09:23 AM, Ben Boeckel wrote:
> On Fri, Jun 24, 2016 at 00:25:00 +0200, Cory Quammen wrote:
>> @Ben, I assume all the dashboard machines are running CMake 3.5. Do
>> you think we should downgrade one to CMake 3.3?
> I was actually going to upgrade them to 3.6's rc today to test it out.
>
>
Can you let me know how it goes?  I just pulled the latest versions of 
Paraview & cmake and want to build under VS2015. I'm going to work on it 
over the weekend. If you're doing the same, I could use any 
configuration tricks you discover.

-Jim

From richard.c.angelini.civ at mail.mil  Fri Jun 24 09:48:08 2016
From: richard.c.angelini.civ at mail.mil (Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US))
Date: Fri, 24 Jun 2016 13:48:08 +0000
Subject: [Paraview] [Non-DoD Source] ANN: ParaView 5.1.0 available for
 download
In-Reply-To: <CADHSJjDNbpmpc5ZQPds6XpiEBsBWS9jd5_fBJ0vzH8ZuNHVg3g@mail.gmail.com>
References: <CADHSJjDNbpmpc5ZQPds6XpiEBsBWS9jd5_fBJ0vzH8ZuNHVg3g@mail.gmail.com>
Message-ID: <D392B1E0.2C226%Richard.C.Angelini.CIV@mail.mil>

Utkarsh - I?ve having trouble getting a build using 5.1 ?.   I?m running a
?make install? and it seems to be looking for install/lib/paraview-5.1 but
what actually exists in the build directory is install/lib/paraview-5.0  ?
not sure if my superbuild is hosed or if there?s something wrong deep in
one of the configuration files.



-- Installing: 
/home/angel/PV/5.1.0/Build/install/share/applications/paraview.desktop
-- Up-to-date: 
/home/angel/PV/5.1.0/Build/install/share/icons/hicolor/22x22/apps/paraview.
png
-- Up-to-date: 
/home/angel/PV/5.1.0/Build/install/share/icons/hicolor/32x32/apps/paraview.
png
-- Up-to-date: 
/home/angel/PV/5.1.0/Build/install/share/icons/hicolor/96x96/apps/paraview.
png
-- Up-to-date: 
/home/angel/PV/5.1.0/Build/install/share/appdata/paraview.appdata.xml
[100%] Completed 'paraview'
[100%] Built target paraview
Install the project...
-- Install configuration: "Release"
CMake Error at cmake_install.cmake:36 (file):
  file INSTALL cannot find
  "/home/angel/PV/5.1.0/Build/install/lib/paraview-5.1".


________________________________
Rick Angelini
USArmy Research Laboratory
CISD/HPC Architectures Team
Phone:  410-278-6266




-----Original Message-----
From: ParaView <paraview-bounces at paraview.org> on behalf of Utkarsh
Ayachit <utkarsh.ayachit at kitware.com>
Date: Tuesday, June 21, 2016 at 12:04 PM
To: ParaView <paraview at paraview.org>, ParaView Developers
<paraview-developers at paraview.org>
Subject: [Non-DoD Source] [Paraview] ANN: ParaView 5.1.0 available for
download

All active links contained in this email were disabled.  Please verify the
identity of the sender, and confirm the authenticity of all links
contained within the message prior to copying and pasting the address to a
Web browser.  




----

Folks,

ParaView 5.1.0 is now available for download [1]. Please refer to the
release notes on the Kitware blog [2]. As always, we look forward to
your feedback [3].

Also stay tuned to the Kitware Blog [4] for upcoming features and
enhancements to ParaView, ParaView Catalyst, ParaViewWeb and much
more!

- ParaView Team

[1] Caution-http://www.paraview.org/download/
[2] Caution-https://blog.kitware.com/paraview-5-1-0-release-notes/
[3] Caution-http://paraview.uservoice.com
[4] Caution-https://blog.kitware.com/tag/ParaView/
_______________________________________________
Powered by Caution-www.kitware.com

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

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

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

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


From foss at grueninger.de  Fri Jun 24 09:50:45 2016
From: foss at grueninger.de (=?UTF-8?Q?Christoph_Gr=C3=BCninger?=)
Date: Fri, 24 Jun 2016 15:50:45 +0200 (CEST)
Subject: [Paraview] Required CMake version 3.5
In-Reply-To: <20160624132357.GA21782@megas.kitware.com>
References: <14169594.887742.1466533123403.JavaMail.open-xchange@omgreatgod.store>
 <CAB5Fpx5UZOh4QPo8pHx4oG-59A8g2bo=1H3Jm-H5ABRO3079wA@mail.gmail.com>
 <1354112273.905026.1466565693599.JavaMail.open-xchange@omgreatgod.store>
 <20160622202932.GA20021@megas.kitware.com>
 <1828645824.1045733.1466691614734.JavaMail.open-xchange@patina.store>
 <CAB5Fpx5+RaKdPPzWJhfBb=zkq7VtDpifFFYzJoNG-1TEfAwiVw@mail.gmail.com>
 <20160624132357.GA21782@megas.kitware.com>
Message-ID: <1331020432.76096.1466776245238.JavaMail.open-xchange@oxapp01-01.store>

Hi Ben,
I don't think it is a good idea to ask for the latest version. Only developers like us have
a current version of CMake installed. From already released distributions nobody
provides CMake 3.5.

> Though I question the distro update policies surrounding where ParaView
> is aggressively pushed forward when CMake isn't. CMake is *much* better
> with its backwards compatibility, but I guess it's down to maintainer
> style to some extent.

Sorry, there is a misunderstanding. We provide packages for already released
distributions. We cannot change the CMake version shipped with them. By
requesting a too recent version, there won't be updated versions of
ParaView for users of released openSuses any more.
I know they can download the binaries you provide or get a more recent
CMake and compile it themselves. You have to weight your inconveniences
against the ones of your users.

Bye
Christoph

From joseph.g.hennessey2.ctr at mail.mil  Fri Jun 24 09:59:22 2016
From: joseph.g.hennessey2.ctr at mail.mil (Hennessey, Joseph G CTR USARMY RDECOM ARL (US))
Date: Fri, 24 Jun 2016 13:59:22 +0000
Subject: [Paraview] [Non-DoD Source] ANN: ParaView 5.1.0 available for
 download (UNCLASSIFIED)
Message-ID: <10A03274360DCF47A6EE78C9952A31CA775C3E25@UMECHPA7C.easf.csd.disa.mil>

CLASSIFICATION: UNCLASSIFIED

Rick,

In the superbuild source directory

The file

CMake/DetermineParaViewVersion.cmake line 10

Change

set (hardcoded_paraview_version "5.0.1")

to

set (hardcoded_paraview_version "5.1.0")

Thanks,

Joe

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Joseph G. Hennessey Ph.D., Lockheed Martin
Army Research Lab
DOD Supercomputing Resource Center
120 Aberdeen Blvd.
Aberdeen Proving Ground, MD 21005
Voice:  410-278-3619
Fax:    410-278-8799
Email:  joseph.g.hennessey2.ctr at mail.mil


-----Original Message-----
From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US)
Sent: Friday, June 24, 2016 9:48 AM
To: Utkarsh Ayachit <utkarsh.ayachit at kitware.com>; ParaView <paraview at paraview.org>; ParaView Developers <paraview-developers at paraview.org>
Subject: Re: [Paraview] [Non-DoD Source] ANN: ParaView 5.1.0 available for download

All active links contained in this email were disabled.  Please verify the identity of the sender, and confirm the authenticity of all links contained within the message prior to copying and pasting the address to a Web browser.  




----

Utkarsh - I?ve having trouble getting a build using 5.1 ?.   I?m running a
?make install? and it seems to be looking for install/lib/paraview-5.1 but what actually exists in the build directory is install/lib/paraview-5.0  ? not sure if my superbuild is hosed or if there?s something wrong deep in one of the configuration files.



-- Installing: 
/home/angel/PV/5.1.0/Build/install/share/applications/paraview.desktop
-- Up-to-date: 
/home/angel/PV/5.1.0/Build/install/share/icons/hicolor/22x22/apps/paraview.
png
-- Up-to-date: 
/home/angel/PV/5.1.0/Build/install/share/icons/hicolor/32x32/apps/paraview.
png
-- Up-to-date: 
/home/angel/PV/5.1.0/Build/install/share/icons/hicolor/96x96/apps/paraview.
png
-- Up-to-date: 
/home/angel/PV/5.1.0/Build/install/share/appdata/paraview.appdata.xml
[100%] Completed 'paraview'
[100%] Built target paraview
Install the project...
-- Install configuration: "Release"
CMake Error at cmake_install.cmake:36 (file):
  file INSTALL cannot find
  "/home/angel/PV/5.1.0/Build/install/lib/paraview-5.1".


________________________________
Rick Angelini
USArmy Research Laboratory
CISD/HPC Architectures Team
Phone:  410-278-6266




-----Original Message-----
From: ParaView <paraview-bounces at paraview.org> on behalf of Utkarsh Ayachit <utkarsh.ayachit at kitware.com>
Date: Tuesday, June 21, 2016 at 12:04 PM
To: ParaView <paraview at paraview.org>, ParaView Developers <paraview-developers at paraview.org>
Subject: [Non-DoD Source] [Paraview] ANN: ParaView 5.1.0 available for download

All active links contained in this email were disabled.  Please verify the identity of the sender, and confirm the authenticity of all links contained within the message prior to copying and pasting the address to a Web browser.  




----

Folks,

ParaView 5.1.0 is now available for download [1]. Please refer to the release notes on the Kitware blog [2]. As always, we look forward to your feedback [3].

Also stay tuned to the Kitware Blog [4] for upcoming features and enhancements to ParaView, ParaView Catalyst, ParaViewWeb and much more!

- ParaView Team

[1] Caution-Caution-http://www.paraview.org/download/
[2] Caution-Caution-https://blog.kitware.com/paraview-5-1-0-release-notes/
[3] Caution-Caution-http://paraview.uservoice.com
[4] Caution-Caution-https://blog.kitware.com/tag/ParaView/
_______________________________________________
Powered by Caution-Caution-www.kitware.com

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

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

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

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

_______________________________________________
Powered by Caution-www.kitware.com

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

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

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

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


CLASSIFICATION: UNCLASSIFIED
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 5615 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160624/c9f75e5c/attachment.bin>

From utkarsh.ayachit at kitware.com  Fri Jun 24 10:18:37 2016
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Fri, 24 Jun 2016 10:18:37 -0400
Subject: [Paraview] [Non-DoD Source] ANN: ParaView 5.1.0 available for
	download
In-Reply-To: <D392B1E0.2C226%Richard.C.Angelini.CIV@mail.mil>
References: <CADHSJjDNbpmpc5ZQPds6XpiEBsBWS9jd5_fBJ0vzH8ZuNHVg3g@mail.gmail.com>
 <D392B1E0.2C226%Richard.C.Angelini.CIV@mail.mil>
Message-ID: <CADHSJjCjpORmwcy_eDf75A1KGG-rGUtWrkoroQdeWVj0TbKpQw@mail.gmail.com>

Just make sure you check out the latest superbuild (or the release
branch). It has all the fixes needed to ensure the internal harcoded
version is set to 5.1.0
(https://gitlab.kitware.com/paraview/paraview-superbuild/blob/release/CMake/DetermineParaViewVersion.cmake)


Utkarsh

On Fri, Jun 24, 2016 at 9:48 AM, Angelini, Richard C (Rick) CIV USARMY
RDECOM ARL (US) <richard.c.angelini.civ at mail.mil> wrote:
> Utkarsh - I?ve having trouble getting a build using 5.1 ?.   I?m running a
> ?make install? and it seems to be looking for install/lib/paraview-5.1 but
> what actually exists in the build directory is install/lib/paraview-5.0  ?
> not sure if my superbuild is hosed or if there?s something wrong deep in
> one of the configuration files.
>
>
>
> -- Installing:
> /home/angel/PV/5.1.0/Build/install/share/applications/paraview.desktop
> -- Up-to-date:
> /home/angel/PV/5.1.0/Build/install/share/icons/hicolor/22x22/apps/paraview.
> png
> -- Up-to-date:
> /home/angel/PV/5.1.0/Build/install/share/icons/hicolor/32x32/apps/paraview.
> png
> -- Up-to-date:
> /home/angel/PV/5.1.0/Build/install/share/icons/hicolor/96x96/apps/paraview.
> png
> -- Up-to-date:
> /home/angel/PV/5.1.0/Build/install/share/appdata/paraview.appdata.xml
> [100%] Completed 'paraview'
> [100%] Built target paraview
> Install the project...
> -- Install configuration: "Release"
> CMake Error at cmake_install.cmake:36 (file):
>   file INSTALL cannot find
>   "/home/angel/PV/5.1.0/Build/install/lib/paraview-5.1".
>
>
> ________________________________
> Rick Angelini
> USArmy Research Laboratory
> CISD/HPC Architectures Team
> Phone:  410-278-6266
>
>
>
>
> -----Original Message-----
> From: ParaView <paraview-bounces at paraview.org> on behalf of Utkarsh
> Ayachit <utkarsh.ayachit at kitware.com>
> Date: Tuesday, June 21, 2016 at 12:04 PM
> To: ParaView <paraview at paraview.org>, ParaView Developers
> <paraview-developers at paraview.org>
> Subject: [Non-DoD Source] [Paraview] ANN: ParaView 5.1.0 available for
> download
>
> All active links contained in this email were disabled.  Please verify the
> identity of the sender, and confirm the authenticity of all links
> contained within the message prior to copying and pasting the address to a
> Web browser.
>
>
>
>
> ----
>
> Folks,
>
> ParaView 5.1.0 is now available for download [1]. Please refer to the
> release notes on the Kitware blog [2]. As always, we look forward to
> your feedback [3].
>
> Also stay tuned to the Kitware Blog [4] for upcoming features and
> enhancements to ParaView, ParaView Catalyst, ParaViewWeb and much
> more!
>
> - ParaView Team
>
> [1] Caution-http://www.paraview.org/download/
> [2] Caution-https://blog.kitware.com/paraview-5-1-0-release-notes/
> [3] Caution-http://paraview.uservoice.com
> [4] Caution-https://blog.kitware.com/tag/ParaView/
> _______________________________________________
> Powered by Caution-www.kitware.com
>
> Visit other Kitware open-source projects at
> Caution-http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> Caution-http://paraview.org/Wiki/ParaView
>
> Search the list archives at: Caution-http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> Caution-http://public.kitware.com/mailman/listinfo/paraview
>

From ben.boeckel at kitware.com  Fri Jun 24 10:25:46 2016
From: ben.boeckel at kitware.com (Ben Boeckel)
Date: Fri, 24 Jun 2016 10:25:46 -0400
Subject: [Paraview] Required CMake version 3.5
In-Reply-To: <1331020432.76096.1466776245238.JavaMail.open-xchange@oxapp01-01.store>
References: <14169594.887742.1466533123403.JavaMail.open-xchange@omgreatgod.store>
 <CAB5Fpx5UZOh4QPo8pHx4oG-59A8g2bo=1H3Jm-H5ABRO3079wA@mail.gmail.com>
 <1354112273.905026.1466565693599.JavaMail.open-xchange@omgreatgod.store>
 <20160622202932.GA20021@megas.kitware.com>
 <1828645824.1045733.1466691614734.JavaMail.open-xchange@patina.store>
 <CAB5Fpx5+RaKdPPzWJhfBb=zkq7VtDpifFFYzJoNG-1TEfAwiVw@mail.gmail.com>
 <20160624132357.GA21782@megas.kitware.com>
 <1331020432.76096.1466776245238.JavaMail.open-xchange@oxapp01-01.store>
Message-ID: <20160624142546.GA31044@megas.kitware.com>

On Fri, Jun 24, 2016 at 15:50:45 +0200, Christoph Gr?ninger wrote:
> I don't think it is a good idea to ask for the latest version. Only developers like us have
> a current version of CMake installed. From already released distributions nobody
> provides CMake 3.5.

My thought here is that building ParaView is much harder than CMake, so
it's not a super high barrier to require a custom-built CMake to build a
custom ParaView build.

> > Though I question the distro update policies surrounding where ParaView
> > is aggressively pushed forward when CMake isn't. CMake is *much* better
> > with its backwards compatibility, but I guess it's down to maintainer
> > style to some extent.
> 
> Sorry, there is a misunderstanding. We provide packages for already released
> distributions. We cannot change the CMake version shipped with them. By
> requesting a too recent version, there won't be updated versions of
> ParaView for users of released openSuses any more.
> I know they can download the binaries you provide or get a more recent
> CMake and compile it themselves. You have to weight your inconveniences
> against the ones of your users.

Ah, so this is more like a PPA? Yeah, I guess overriding the CMake from
those wouldn't be a great thing to recommend.

Talking with Utkarsh, we can move the version down since that's our
actual minimum version. However, if things get added to ParaView's build
that require newer CMake support, bumping the minimum version would not
be a huge blocker.

--Ben

From ben.boeckel at kitware.com  Fri Jun 24 10:29:03 2016
From: ben.boeckel at kitware.com (Ben Boeckel)
Date: Fri, 24 Jun 2016 10:29:03 -0400
Subject: [Paraview] Required CMake version 3.5
In-Reply-To: <576D357D.40601@gmail.com>
References: <14169594.887742.1466533123403.JavaMail.open-xchange@omgreatgod.store>
 <CAB5Fpx5UZOh4QPo8pHx4oG-59A8g2bo=1H3Jm-H5ABRO3079wA@mail.gmail.com>
 <1354112273.905026.1466565693599.JavaMail.open-xchange@omgreatgod.store>
 <20160622202932.GA20021@megas.kitware.com>
 <1828645824.1045733.1466691614734.JavaMail.open-xchange@patina.store>
 <CAB5Fpx5+RaKdPPzWJhfBb=zkq7VtDpifFFYzJoNG-1TEfAwiVw@mail.gmail.com>
 <20160624132357.GA21782@megas.kitware.com>
 <576D357D.40601@gmail.com>
Message-ID: <20160624142903.GB31044@megas.kitware.com>

On Fri, Jun 24, 2016 at 09:28:29 -0400, Jim wrote:
> Can you let me know how it goes?  I just pulled the latest versions of 
> Paraview & cmake and want to build under VS2015. I'm going to work on it 
> over the weekend. If you're doing the same, I could use any 
> configuration tricks you discover.

I thought we had a VS2015 dashboard, but I see it is just VS2013
(thinking back, probably because there isn't a Qt4 build against 2015 on
that machine). They're not that different for setup though. I'll look at
getting the other Windows machine onto the dashboard setup here today.

I don't expect any issues, but if you find any, feel free to email the
list or open issues.

Thanks,

--Ben

From lukasz.paluszek at airbus.com  Fri Jun 24 11:15:26 2016
From: lukasz.paluszek at airbus.com (Paluszek, Lukasz)
Date: Fri, 24 Jun 2016 15:15:26 +0000
Subject: [Paraview] Opacity Issues
Message-ID: <9385_1466781329_576D4E91_9385_11640_1_d6606d3c88134b9bb7ca3e3b5a83459f@DE0-03DAG13-P03.central.mail.corp>

Hello,

In Paraview 5.1.0 with OpenGL2, I have black slices throughout the model when opacity is on in parallel mode (see attached picture). When switching depth peeling off, the black slices disappear but the image gets blurred and some pixels glow with random colours. I can't reproduce it with 5.0.0, my NVidia driver is 361.42. Does anyone else experience similar behaviour?


Reagrds,
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; Thomas Hundt; 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/20160624/3d0ac147/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/20160624/3d0ac147/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: opacity.jpeg
Type: image/jpeg
Size: 14749 bytes
Desc: opacity.jpeg
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160624/3d0ac147/attachment.jpeg>

From spl at tirebiter.org  Fri Jun 24 11:44:45 2016
From: spl at tirebiter.org (Steve Lamont)
Date: Fri, 24 Jun 2016 08:44:45 -0700
Subject: [Paraview] Opacity Issues
In-Reply-To: <9385_1466781329_576D4E91_9385_11640_1_d6606d3c88134b9bb7ca3e3b5a83459f@DE0-03DAG13-P03.central.mail.corp>
References: <9385_1466781329_576D4E91_9385_11640_1_d6606d3c88134b9bb7ca3e3b5a83459f@DE0-03DAG13-P03.central.mail.corp>
Message-ID: <576D556D.20501@tirebiter.org>

> In Paraview 5.1.0 with OpenGL2, I have black slices throughout the model
> when opacity is on in parallel mode (see attached picture). When
> switching depth peeling off, the black slices disappear but the image
> gets blurred and some pixels glow with random colours.

Is there a version with the "Legacy" rendering backend available?  I 
find that it does a better job with rendering, including the depth 
sorting issues I've discussed here previously.

I don't notice any significant difference in performance between the 
OpenGL2 version and the putative Legacy version.

							sp


From david.lonie at kitware.com  Fri Jun 24 12:24:02 2016
From: david.lonie at kitware.com (David Lonie)
Date: Fri, 24 Jun 2016 12:24:02 -0400
Subject: [Paraview] Opacity Issues
In-Reply-To: <9385_1466781329_576D4E91_9385_11640_1_d6606d3c88134b9bb7ca3e3b5a83459f@DE0-03DAG13-P03.central.mail.corp>
References: <9385_1466781329_576D4E91_9385_11640_1_d6606d3c88134b9bb7ca3e3b5a83459f@DE0-03DAG13-P03.central.mail.corp>
Message-ID: <CA+=e1otaNJNUweQTEqOzSKU0jnDivxMBBcP6FMB-4KY64za6KA@mail.gmail.com>

On Fri, Jun 24, 2016 at 11:15 AM, Paluszek, Lukasz <
lukasz.paluszek at airbus.com> wrote:

> Hello,
>
>
>
> In Paraview 5.1.0 with OpenGL2, I have black slices throughout the model
> when opacity is on in parallel mode (see attached picture). When switching
> depth peeling off, the black slices disappear but the image gets blurred
> and some pixels glow with random colours. I can?t reproduce it with 5.0.0,
> my NVidia driver is 361.42. Does anyone else experience similar behaviour?
>

Interesting, I haven't seen this before. Does it happen for all depth
peeled transparent rendering, or just certain scenes? If it's only certain
scenes, can you provide a state file or details on the scene?

Also, which OS is this?

Thanks,
Dave
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160624/4dbecd55/attachment.html>

From lukasz.paluszek at airbus.com  Fri Jun 24 13:10:57 2016
From: lukasz.paluszek at airbus.com (Paluszek, Lukasz)
Date: Fri, 24 Jun 2016 17:10:57 +0000
Subject: [Paraview] Opacity Issues
In-Reply-To: <13295_1466785464_576D5EB7_13295_19000_1_CA+=e1otaNJNUweQTEqOzSKU0jnDivxMBBcP6FMB-4KY64za6KA@mail.gmail.com>
References: <9385_1466781329_576D4E91_9385_11640_1_d6606d3c88134b9bb7ca3e3b5a83459f@DE0-03DAG13-P03.central.mail.corp>
 <13295_1466785464_576D5EB7_13295_19000_1_CA+=e1otaNJNUweQTEqOzSKU0jnDivxMBBcP6FMB-4KY64za6KA@mail.gmail.com>
Message-ID: <622_1466788260_576D69A4_622_19423_1_7fd68ea2d27f4d6bb0a2ed8cb27e1b71@DE0-03DAG13-P03.central.mail.corp>

It doesn?t happen all the time, I suppose you need a fairly large surface dataset. I managed to reproduce the problem on a wavelet source (attached state file), try increasing the number of elements if you do not see any artifacts. I have bult Paraview from source on OpenSuse 13.1 but also cross-checked with the Linux binaries from Paraview.org and had same issues. There was no problem with the osmesa-llvm flavor though.


[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>

From: David Lonie [mailto:david.lonie at kitware.com]
Sent: 24 June 2016 18:24
To: Paluszek, Lukasz
Cc: paraview at paraview.org
Subject: Re: [Paraview] Opacity Issues

On Fri, Jun 24, 2016 at 11:15 AM, Paluszek, Lukasz <lukasz.paluszek at airbus.com<mailto:lukasz.paluszek at airbus.com>> wrote:
Hello,

In Paraview 5.1.0 with OpenGL2, I have black slices throughout the model when opacity is on in parallel mode (see attached picture). When switching depth peeling off, the black slices disappear but the image gets blurred and some pixels glow with random colours. I can?t reproduce it with 5.0.0, my NVidia driver is 361.42. Does anyone else experience similar behaviour?

Interesting, I haven't seen this before. Does it happen for all depth peeled transparent rendering, or just certain scenes? If it's only certain scenes, can you provide a state file or details on the scene?

Also, which OS is this?

Thanks,
Dave

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; Thomas Hundt; 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/20160624/78055839/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/20160624/78055839/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: opacity.pvsm
Type: application/octet-stream
Size: 139485 bytes
Desc: opacity.pvsm
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160624/78055839/attachment.obj>

From david.lonie at kitware.com  Fri Jun 24 13:34:10 2016
From: david.lonie at kitware.com (David Lonie)
Date: Fri, 24 Jun 2016 13:34:10 -0400
Subject: [Paraview] Minor bug in OPENFOAM import filter
In-Reply-To: <AM4PR08MB1188DE8BD6DCE85F6005673D8B2C0@AM4PR08MB1188.eurprd08.prod.outlook.com>
References: <AM4PR08MB1188BAC0AF0C79B9A3D3BC9B8B2C0@AM4PR08MB1188.eurprd08.prod.outlook.com>
 <CA+=e1ouj8q447Q0uKPM6WtBPGphMM+Fc=R7hqSzDB6RNE1_A8w@mail.gmail.com>
 <AM4PR08MB1188DE8BD6DCE85F6005673D8B2C0@AM4PR08MB1188.eurprd08.prod.outlook.com>
Message-ID: <CA+=e1otGNN2HFHh_nBLvrgq3cH3+hvJcHUZz5F0uQ6WNWKiQXg@mail.gmail.com>

Hi Eugene,

On Wed, Jun 22, 2016 at 11:45 AM, Eugene de Villiers <e.devilliers at engys.com
> wrote:

> Attached find a small case
>

Thanks -- I've loaded this up and can reproduce the error. The error occurs
in vtkFoamEntryValue::ReadList, which contains the following comment:

// general-purpose list reader - guess the type of the list and read

// it. only supports ascii format and assumes the preceding '(' has

// already been thrown away.  the reader supports nested list with

// variable lengths (e. g. `((token token) (token token token)).'

// also *supports compound of tokens and lists (e. g. `((token token)*

// *token)') only if a list comes as the first value.*


So the list (1.1 (1 2 3)) is being parsed as a list, and our reader
only supports lists

containing mixed tokens / lists if the lists precede the tokens. And
indeed, changing

file to read ((1 2 3) 1.1) will eliminate the error. The current
parser assumes that the

remainder of the list will also be scalars and attempts to read them
in -- then it

chokes when it encounters a '(' instead of another scalar.


Again, I'm not familiar with the openFOAM format, but would writing
the list with the

nested list first be feasible on your end? I'm not sure if this is a
format restriction or

an implementation detail of our reader.


Alternatively, I saw some discussion around skipping every entry in
boundaryField

specifications other than 'value'. This would likely be quite easy to
implement. My

only question is, would it break anything for the visualization?


Dave
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160624/7a339f65/attachment.html>

From david.lonie at kitware.com  Fri Jun 24 14:15:44 2016
From: david.lonie at kitware.com (David Lonie)
Date: Fri, 24 Jun 2016 14:15:44 -0400
Subject: [Paraview] Opacity Issues
In-Reply-To: <622_1466788260_576D69A4_622_19423_1_7fd68ea2d27f4d6bb0a2ed8cb27e1b71@DE0-03DAG13-P03.central.mail.corp>
References: <9385_1466781329_576D4E91_9385_11640_1_d6606d3c88134b9bb7ca3e3b5a83459f@DE0-03DAG13-P03.central.mail.corp>
 <13295_1466785464_576D5EB7_13295_19000_1_CA+=e1otaNJNUweQTEqOzSKU0jnDivxMBBcP6FMB-4KY64za6KA@mail.gmail.com>
 <622_1466788260_576D69A4_622_19423_1_7fd68ea2d27f4d6bb0a2ed8cb27e1b71@DE0-03DAG13-P03.central.mail.corp>
Message-ID: <CA+=e1ov_PyX74TcDMJq2RFqhPGmBuCazwKwrJdTnxWOBpL1f7A@mail.gmail.com>

On Fri, Jun 24, 2016 at 1:10 PM, Paluszek, Lukasz <
lukasz.paluszek at airbus.com> wrote:

> It doesn?t happen all the time, I suppose you need a fairly large surface
> dataset. I managed to reproduce the problem on a wavelet source (attached
> state file), try increasing the number of elements if you do not see any
> artifacts. I have bult Paraview from source on OpenSuse 13.1 but also
> cross-checked with the Linux binaries from Paraview.org and had same
> issues. There was no problem with the osmesa-llvm flavor though.
>

I couldn't reproduce this here on arch linux with a newer nVidia driver
(367.27), so I'm suspicious that this is a driver bug that's affecting the
new depth peeling implementation.

Since you're building from source, can you try editing
VTK/Rendering/OpenGL2/vtkOpenGLRenderer.cxx, and change line 322

if (dualDepthPeelingSupported)

to

if (false)

in DeviceRenderTranslucentPolygonalGeometry, recompile using the OpenGL2
backend, and let me know if the issue goes away? I suspect it will since
both the OpenGL1 backend and OpenGL2 mesa/llvm do not use the new code.

I'll put together a patch to force the older peeling implementation via an
environment variable to make the work-around easier to apply.

Dave
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160624/70e03602/attachment.html>

From david.lonie at kitware.com  Fri Jun 24 15:22:29 2016
From: david.lonie at kitware.com (David Lonie)
Date: Fri, 24 Jun 2016 15:22:29 -0400
Subject: [Paraview] Opacity Issues
In-Reply-To: <CA+=e1ov_PyX74TcDMJq2RFqhPGmBuCazwKwrJdTnxWOBpL1f7A@mail.gmail.com>
References: <9385_1466781329_576D4E91_9385_11640_1_d6606d3c88134b9bb7ca3e3b5a83459f@DE0-03DAG13-P03.central.mail.corp>
 <13295_1466785464_576D5EB7_13295_19000_1_CA+=e1otaNJNUweQTEqOzSKU0jnDivxMBBcP6FMB-4KY64za6KA@mail.gmail.com>
 <622_1466788260_576D69A4_622_19423_1_7fd68ea2d27f4d6bb0a2ed8cb27e1b71@DE0-03DAG13-P03.central.mail.corp>
 <CA+=e1ov_PyX74TcDMJq2RFqhPGmBuCazwKwrJdTnxWOBpL1f7A@mail.gmail.com>
Message-ID: <CA+=e1osFVg1tZgXnCuCkkqLNigDTB093D_QPd42Pjcfh4=bo3A@mail.gmail.com>

On Fri, Jun 24, 2016 at 2:15 PM, David Lonie <david.lonie at kitware.com>
wrote:

> On Fri, Jun 24, 2016 at 1:10 PM, Paluszek, Lukasz <
> lukasz.paluszek at airbus.com> wrote:
>
>> It doesn?t happen all the time, I suppose you need a fairly large surface
>> dataset. I managed to reproduce the problem on a wavelet source (attached
>> state file), try increasing the number of elements if you do not see any
>> artifacts. I have bult Paraview from source on OpenSuse 13.1 but also
>> cross-checked with the Linux binaries from Paraview.org and had same
>> issues. There was no problem with the osmesa-llvm flavor though.
>>
>
> I couldn't reproduce this here on arch linux with a newer nVidia driver
> (367.27), so I'm suspicious that this is a driver bug that's affecting the
> new depth peeling implementation.
>
> Since you're building from source, can you try editing
> VTK/Rendering/OpenGL2/vtkOpenGLRenderer.cxx, and change line 322
>
> if (dualDepthPeelingSupported)
>
> to
>
> if (false)
>
> in DeviceRenderTranslucentPolygonalGeometry, recompile using the OpenGL2
> backend, and let me know if the issue goes away? I suspect it will since
> both the OpenGL1 backend and OpenGL2 mesa/llvm do not use the new code.
>
> I'll put together a patch to force the older peeling implementation via an
> environment variable to make the work-around easier to apply.
>

Patch is here: https://gitlab.kitware.com/vtk/vtk/merge_requests/1589

By the way, are you running paraview with remote rendering via pvserver? I
was just made aware of a similar issue with remote rendering and depth
peeling.

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

From utkarsh.ayachit at kitware.com  Fri Jun 24 15:44:23 2016
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Fri, 24 Jun 2016 15:44:23 -0400
Subject: [Paraview] Question mark button launches a blank window with
	5.1.0
In-Reply-To: <CAHDyfPDpFqhs_GCKC=9orYxyamrBG6phn=nW+UeP-twMWEPLfw@mail.gmail.com>
References: <CAHDyfPDpFqhs_GCKC=9orYxyamrBG6phn=nW+UeP-twMWEPLfw@mail.gmail.com>
Message-ID: <CADHSJjCgpKwYiF4H=yWrPwtB2NBKN4_pdxir02WUnz0mJoNCog@mail.gmail.com>

Thanks for reporting that. We may need to do a 5.1.1 patch release
soon. If so, I'll make sure this one gets addressed too.

On Fri, Jun 24, 2016 at 6:37 AM, kenichiro yoshimi
<rccm.kyoshimi at gmail.com> wrote:
> Hi all,
>
> I use ParaView 5.1.0 version installed from a binary file
> ParaView-5.1.0-Qt4-OpenGL2-Windows-64bit.exe. Unfortunately, this version's
> "ParaView Online Help" launched by clicking on Question mark button is not
> available because
> the opened window is blank. This problem did not occur with 5.0.1 version.
>
> Best Regards,
> yoshimi kenichiro
>
> _______________________________________________
> 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 b.gazanion at gantha.com  Fri Jun 24 10:21:20 2016
From: b.gazanion at gantha.com (Bertrand Gazanion)
Date: Fri, 24 Jun 2016 16:21:20 +0200
Subject: [Paraview] Find points within radius
In-Reply-To: <82b57ab76af748eeba6c5f91a1cbc743@ES08AMSNLNT.srn.sandia.gov>
References: <82b57ab76af748eeba6c5f91a1cbc743@ES08AMSNLNT.srn.sandia.gov>
Message-ID: <003101d1ce23$af808df0$0e81a9d0$@gazanion@gantha.com>

Dear Kenneth, thank you for your answer. Here is the message from my
colleague.

Bertrand

 

Hello, I am the colleague using ParaView 4.3.1!

 

First of all, thank you for your response, it has explained a lot of results
since I tend to forget about computer and floating point.

 

Unfortunately the physics behind my algorithm forces me to look for all the
neighbors inside a sphere of each point of my unstructured grid.

 

My curiosity has pushed me to look how the FindPointsWithinRadius function
works and I have seen that it does an inferior or equal comparison. Isn't
the equal part the source of inconsistent return values? 

I have read a more straightforward  <http://floating-point-gui.de/> website
about floating point number :  <http://floating-point-gui.de/>
http://floating-point-gui.de/  which I hope offer good information.

The page about  <http://floating-point-gui.de/errors/comparison/> comparison
offer a way to check if two numbers are equal that seems to be accurate, I
have tried to implement it in the FindPointsWithinRadius function of
vtkPointLocator but I am not proficient at c++, vtk and your coding
guidelines, see attachment.

 

I am not sure if it is vtk responsibility to find out how to deal with those
case but I find the solution interesting.

 

Thank you!

 

 

From: Moreland, Kenneth [mailto:kmorel at sandia.gov] 
Sent: Thursday, June 23, 2016 5:11 PM
To: Bertrand Gazanion; paraview at paraview.org
Subject: Re: [Paraview] Find points within radius

 

The problem you are facing is with the precision of floating point numbers.
The way you are setting up your problem is that the points are exactly 0.01
units away from each other. When you ask the point locator for all points
within a radius of 0.01, then what happens when a point is exactly 0.01
units away from the center? That depends on what happens in the limited
precision of your computer?s floating point values. Sometimes it will be
0.01 + epsilon, in which case the point will be considered inside the
radius. Sometimes it will be 0.01 ? epsilon, in which case the point will be
considered outside the radius. This is a well known issue with floating
point numbers. There are lots of resources describing it. A quick Google
search gave this article:
https://docs.oracle.com/cd/E19957-01/806-3568/ncg_goldberg.html.

 

Anyway, the simple solution is to increase the radius in
FindPointsWithinRadius by a small amount. Changing the line to:

 

    loc.FindPointsWithinRadius(0.01,xp,id_list)

 

fixes the problem for all point locators.

 

BTW, although perhaps convenient, using a point locator to find neighbors is
not the most robust way to do it. It would be safer to use the find neighbor
facilities of the different vtkDataSet classes.

 

-Ken

 

From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Bertrand
Gazanion
Sent: Thursday, June 23, 2016 8:13 AM
To: paraview at paraview.org
Subject: [EXTERNAL] Re: [Paraview] Find points within radius

 

Forgot the pictures... Sorry for the spam.

Bertrand

 

De : Bertrand Gazanion [mailto:b.gazanion at gantha.com] 
Envoy? : jeudi 23 juin 2016 16:11
? : 'paraview at paraview.org'
Objet : Find points within radius

 

On behalf of a colleague of mine working with ParaView 4.3.1

 

Hello,


I am using an algorithm doing calculation on points and their neighbours and
I find the results of those points locators to be strange. To test it I made
a simple algorithm counting how many neighbours each point has.
When I create a plane and set its x and y resolution to 100 each, all points
should have the same number of neighbours except on the sides. However
vtkPointLocator, vtkKdTreePointLocator and vtkOctreePointLocator do not find
the same number of neighbours for each point.

Here is the algorithm that I use to get the number of neighbors each points
has :
import vtk

pdi = self.GetInputDataObject(0,0)
nb_pts = pdi.GetNumberOfPoints()

# Point locator
loc = vtk.vtkPointLocator()
#loc = vtk.vtkOctreePointLocator()
#loc = vtk. vtkKdTreePointLocator()

loc.SetDataSet(pdi)
loc.BuildLocator()

pts = pdi.GetPoints()

neighbours = vtk.vtkTypeInt64Array()
neighbours.SetNumberOfComponents(1)
neighbours.SetNumberOfTuples(nb_pts)
neighbours.SetName('neighbours')

for k in range(nb_pts):

    xp = pdi.GetPoint(k)

    id_list = vtk.vtkIdList()

    loc.FindPointsWithinRadius(0.01,xp,id_list)
    loc.Update()

    N = id_list.GetNumberOfIds()
    neighbours.InsertTuple1(k,N)


self.GetOutput().GetPointData().AddArray(neighbours)

 

You will find attached sample picture describing the result I get with each
point locator.

thank you very much

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160624/cdd74b01/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: FindPointsWithinRadius.cxx
Type: application/octet-stream
Size: 2066 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160624/cdd74b01/attachment.obj>

From Joshua.Murphy at lasp.colorado.edu  Fri Jun 24 21:52:06 2016
From: Joshua.Murphy at lasp.colorado.edu (Joshua Murphy)
Date: Sat, 25 Jun 2016 01:52:06 +0000
Subject: [Paraview] error when trying to hide a sphere in a python script....
Message-ID: <1466819526927.35021@lasp.colorado.edu>

Hello,


I am writing a python script to do some analysis on magnetic field lines, and I am trying to generate some images for a sanity check.


The first image I have attached is the type of image I am trying to produce (verification_(5.25,0,0).png).


The second image is generated in the same script.  The red and blue spheres that correspond to the ones in the first image should have been hidden, but when I try to hide them, I get the error:

(verification_(-5.25,0,0).png)

ERROR: In /Users/jjm390/src/Paraview/ParaView/ParaViewCore/ServerManager/Rendering/vtkSMParaViewPipelineControllerWithRendering.cxx, line 409
vtkSMParaViewPipelineControllerWithRendering (0x7fca9e4cd180): Invalid producer (0x7fca9e4e12f0) or outputPort (0)


When the final render to screen is done, the spheres are all gone, but they do not get hidden when the image is generated.

The script I wrote is attached.  Note, if you need the entire project to help figure out why it isn't working, I can share it individually.  This is the script that generates the images.

?I would appreciate any help people might be able to offer!  I am running ParaView 5.0.1 on Mac OS X 10.11.5.

Thanks,
Josh Murphy



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160625/1e64afe6/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: verification_(5.25, 0, 0).png
Type: image/png
Size: 70278 bytes
Desc: verification_(5.25, 0, 0).png
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160625/1e64afe6/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: verification_(-5.25, 0, 0).png
Type: image/png
Size: 93076 bytes
Desc: verification_(-5.25, 0, 0).png
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160625/1e64afe6/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: noon_midnight_test.py
Type: text/x-python-script
Size: 4748 bytes
Desc: noon_midnight_test.py
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160625/1e64afe6/attachment-0001.bin>

From oshima at eng.niigata-u.ac.jp  Sat Jun 25 07:11:10 2016
From: oshima at eng.niigata-u.ac.jp (Takuya OSHIMA)
Date: Sat, 25 Jun 2016 20:11:10 +0900 (JST)
Subject: [Paraview] Minor bug in OPENFOAM import filter
In-Reply-To: <CA+=e1otGNN2HFHh_nBLvrgq3cH3+hvJcHUZz5F0uQ6WNWKiQXg@mail.gmail.com>
References: <CA+=e1ouj8q447Q0uKPM6WtBPGphMM+Fc=R7hqSzDB6RNE1_A8w@mail.gmail.com>
 <AM4PR08MB1188DE8BD6DCE85F6005673D8B2C0@AM4PR08MB1188.eurprd08.prod.outlook.com>
 <CA+=e1otGNN2HFHh_nBLvrgq3cH3+hvJcHUZz5F0uQ6WNWKiQXg@mail.gmail.com>
Message-ID: <20160625.201110.156085895.oshima@eng.niigata-u.ac.jp>

Hi David and Eugene,

From: David Lonie <david.lonie at kitware.com>
Subject: Re: [Paraview] Minor bug in OPENFOAM import filter
Date: Fri, 24 Jun 2016 13:34:10 -0400

> Alternatively, I saw some discussion around skipping every entry in
> boundaryField specifications other than 'value'. This would likely
> be quite easy to implement. My only question is, would it break
> anything for the visualization?

It would be better if other entries like "gradient" (for Neumann-type
boundary conditions) can also be taken into account.  However it needs
a lot of work (we need to add a logic to calculate the distance from
the adjacent cell center to the boundary face etc.).  I think for now
we need to live with skipping every entry other than "value".

From: Eugene de Villiers <e.devilliers at engys.com>
Subject: RE: [Paraview] Minor bug in OPENFOAM filter
Date: Wed, 22 Jun 2016 15:56:56 +0000

> I would say check for a "value" entry and if you don't find it
> assume zero gradient.

If I remember correctly, the reader already has a check for a "value"
entry and if not found it assumes zero gradient.

> It is important that only the first value entry on the base level of
> the boundary condition is actually identified as the face value
> correlated "value" entry.

I am sure that the reader already does this as well.

Takuya OSHIMA, Ph.D.
Faculty of Engineering, Niigata University
8050 Ikarashi-Ninocho, Nishi-ku, Niigata, 950-2181, JAPAN

From: David Lonie <david.lonie at kitware.com>
Subject: Re: [Paraview] Minor bug in OPENFOAM import filter
Date: Fri, 24 Jun 2016 13:34:10 -0400

> Hi Eugene,
> 
> On Wed, Jun 22, 2016 at 11:45 AM, Eugene de Villiers <e.devilliers at engys.com
>> wrote:
> 
>> Attached find a small case
>>
> 
> Thanks -- I've loaded this up and can reproduce the error. The error occurs
> in vtkFoamEntryValue::ReadList, which contains the following comment:
> 
> // general-purpose list reader - guess the type of the list and read
> 
> // it. only supports ascii format and assumes the preceding '(' has
> 
> // already been thrown away.  the reader supports nested list with
> 
> // variable lengths (e. g. `((token token) (token token token)).'
> 
> // also *supports compound of tokens and lists (e. g. `((token token)*
> 
> // *token)') only if a list comes as the first value.*
> 
> 
> So the list (1.1 (1 2 3)) is being parsed as a list, and our reader
> only supports lists
> 
> containing mixed tokens / lists if the lists precede the tokens. And
> indeed, changing
> 
> file to read ((1 2 3) 1.1) will eliminate the error. The current
> parser assumes that the
> 
> remainder of the list will also be scalars and attempts to read them
> in -- then it
> 
> chokes when it encounters a '(' instead of another scalar.
> 
> 
> Again, I'm not familiar with the openFOAM format, but would writing
> the list with the
> 
> nested list first be feasible on your end? I'm not sure if this is a
> format restriction or
> 
> an implementation detail of our reader.
> 
> 
> Alternatively, I saw some discussion around skipping every entry in
> boundaryField
> 
> specifications other than 'value'. This would likely be quite easy to
> implement. My
> 
> only question is, would it break anything for the visualization?
> 
> 
> Dave

From e.devilliers at engys.com  Sat Jun 25 13:02:51 2016
From: e.devilliers at engys.com (Eugene de Villiers)
Date: Sat, 25 Jun 2016 17:02:51 +0000
Subject: [Paraview] Minor bug in OPENFOAM import filter
In-Reply-To: <20160625.201110.156085895.oshima@eng.niigata-u.ac.jp>
References: <CA+=e1ouj8q447Q0uKPM6WtBPGphMM+Fc=R7hqSzDB6RNE1_A8w@mail.gmail.com>
 <AM4PR08MB1188DE8BD6DCE85F6005673D8B2C0@AM4PR08MB1188.eurprd08.prod.outlook.com>
 <CA+=e1otGNN2HFHh_nBLvrgq3cH3+hvJcHUZz5F0uQ6WNWKiQXg@mail.gmail.com>
 <20160625.201110.156085895.oshima@eng.niigata-u.ac.jp>
Message-ID: <AM4PR08MB1188D0A13FFA958B1BA8F73E8B2F0@AM4PR08MB1188.eurprd08.prod.outlook.com>

Hi Takuya, David,

That would be perfect. What kind of timeline are we looking at to see this in a release version?

Eugene

-----Original Message-----
From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Takuya OSHIMA
Sent: 25 June 2016 12:11
To: paraview at paraview.org
Subject: Re: [Paraview] Minor bug in OPENFOAM import filter

Hi David and Eugene,

From: David Lonie <david.lonie at kitware.com>
Subject: Re: [Paraview] Minor bug in OPENFOAM import filter
Date: Fri, 24 Jun 2016 13:34:10 -0400

> Alternatively, I saw some discussion around skipping every entry in 
> boundaryField specifications other than 'value'. This would likely be 
> quite easy to implement. My only question is, would it break anything 
> for the visualization?

It would be better if other entries like "gradient" (for Neumann-type boundary conditions) can also be taken into account.  However it needs a lot of work (we need to add a logic to calculate the distance from the adjacent cell center to the boundary face etc.).  I think for now we need to live with skipping every entry other than "value".

From: Eugene de Villiers <e.devilliers at engys.com>
Subject: RE: [Paraview] Minor bug in OPENFOAM filter
Date: Wed, 22 Jun 2016 15:56:56 +0000

> I would say check for a "value" entry and if you don't find it assume 
> zero gradient.

If I remember correctly, the reader already has a check for a "value"
entry and if not found it assumes zero gradient.

> It is important that only the first value entry on the base level of 
> the boundary condition is actually identified as the face value 
> correlated "value" entry.

I am sure that the reader already does this as well.

Takuya OSHIMA, Ph.D.
Faculty of Engineering, Niigata University
8050 Ikarashi-Ninocho, Nishi-ku, Niigata, 950-2181, JAPAN

From: David Lonie <david.lonie at kitware.com>
Subject: Re: [Paraview] Minor bug in OPENFOAM import filter
Date: Fri, 24 Jun 2016 13:34:10 -0400

> Hi Eugene,
> 
> On Wed, Jun 22, 2016 at 11:45 AM, Eugene de Villiers 
> <e.devilliers at engys.com
>> wrote:
> 
>> Attached find a small case
>>
> 
> Thanks -- I've loaded this up and can reproduce the error. The error 
> occurs in vtkFoamEntryValue::ReadList, which contains the following comment:
> 
> // general-purpose list reader - guess the type of the list and read
> 
> // it. only supports ascii format and assumes the preceding '(' has
> 
> // already been thrown away.  the reader supports nested list with
> 
> // variable lengths (e. g. `((token token) (token token token)).'
> 
> // also *supports compound of tokens and lists (e. g. `((token token)*
> 
> // *token)') only if a list comes as the first value.*
> 
> 
> So the list (1.1 (1 2 3)) is being parsed as a list, and our reader 
> only supports lists
> 
> containing mixed tokens / lists if the lists precede the tokens. And 
> indeed, changing
> 
> file to read ((1 2 3) 1.1) will eliminate the error. The current 
> parser assumes that the
> 
> remainder of the list will also be scalars and attempts to read them 
> in -- then it
> 
> chokes when it encounters a '(' instead of another scalar.
> 
> 
> Again, I'm not familiar with the openFOAM format, but would writing 
> the list with the
> 
> nested list first be feasible on your end? I'm not sure if this is a 
> format restriction or
> 
> an implementation detail of our reader.
> 
> 
> Alternatively, I saw some discussion around skipping every entry in 
> boundaryField
> 
> specifications other than 'value'. This would likely be quite easy to 
> implement. My
> 
> only question is, would it break anything for the visualization?
> 
> 
> Dave
_______________________________________________
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 dwneumann at gmail.com  Sat Jun 25 21:05:46 2016
From: dwneumann at gmail.com (Dean Neumann)
Date: Sat, 25 Jun 2016 18:05:46 -0700
Subject: [Paraview] SyntaxError reported parsing Python Calculator ?
Message-ID: <CAGgSO3i4mV82hYekgu1g7KcFOOphHJrgPk6y74iyCw-NF65WTA@mail.gmail.com>

Cory Quammen wrote:
> Do you have "Auto Apply" on? This may be leading to the problem -

Thank you Cory.  I did indeed have Auto Apply on and disabling that fixed
the problem.
Cheers,
Dean
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160625/761e9678/attachment.html>

From cory.quammen at kitware.com  Sun Jun 26 08:25:47 2016
From: cory.quammen at kitware.com (Cory Quammen)
Date: Sun, 26 Jun 2016 14:25:47 +0200
Subject: [Paraview] SyntaxError reported parsing Python Calculator ?
In-Reply-To: <CAGgSO3i4mV82hYekgu1g7KcFOOphHJrgPk6y74iyCw-NF65WTA@mail.gmail.com>
References: <CAGgSO3i4mV82hYekgu1g7KcFOOphHJrgPk6y74iyCw-NF65WTA@mail.gmail.com>
Message-ID: <CAB5Fpx5ujS3xuKVHr1tDq0=S9D9s-x7bpueJkOwoKbOjTr9j=w@mail.gmail.com>

Dean,

I have a merge request in that should fix this in the next ParaView release :

https://gitlab.kitware.com/paraview/paraview/merge_requests/852

Best,
Cory

On Sun, Jun 26, 2016 at 3:05 AM, Dean Neumann <dwneumann at gmail.com> wrote:
> Cory Quammen wrote:
>> Do you have "Auto Apply" on? This may be leading to the problem -
>
> Thank you Cory.  I did indeed have Auto Apply on and disabling that fixed
> the problem.
> Cheers,
> Dean
>
> _______________________________________________
> 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 Jun 26 12:09:48 2016
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Sun, 26 Jun 2016 12:09:48 -0400
Subject: [Paraview] [Paraview-developers] error when trying to hide a
 sphere in a python script....
In-Reply-To: <1466819526927.35021@lasp.colorado.edu>
References: <1466819526927.35021@lasp.colorado.edu>
Message-ID: <CADHSJjAOOa1Sj=QtXAKd7120dQfzPUaPQfWXLd3GJ_Ey+VtevA@mail.gmail.com>

Josh,

Can you narrow down the error to specific pv.Hide() call? The  error
is popping up due to something calling the Hide with arguments that
have not been setup properly. Let's isolate that and we can then trace
backwards from there. If you want to send me the reset of the code +
data, feel free to do that off line.


Utkarsh

On Fri, Jun 24, 2016 at 9:52 PM, Joshua Murphy
<Joshua.Murphy at lasp.colorado.edu> wrote:
> Hello,
>
>
> I am writing a python script to do some analysis on magnetic field lines,
> and I am trying to generate some images for a sanity check.
>
>
> The first image I have attached is the type of image I am trying to produce
> (verification_(5.25,0,0).png).
>
>
> The second image is generated in the same script.  The red and blue spheres
> that correspond to the ones in the first image should have been hidden, but
> when I try to hide them, I get the error:
>
> (verification_(-5.25,0,0).png)
>
>
> ERROR: In
> /Users/jjm390/src/Paraview/ParaView/ParaViewCore/ServerManager/Rendering/vtkSMParaViewPipelineControllerWithRendering.cxx,
> line 409
> vtkSMParaViewPipelineControllerWithRendering (0x7fca9e4cd180): Invalid
> producer (0x7fca9e4e12f0) or outputPort (0)
>
>
> When the final render to screen is done, the spheres are all gone, but they
> do not get hidden when the image is generated.
>
> The script I wrote is attached.  Note, if you need the entire project to
> help figure out why it isn't working, I can share it individually.  This is
> the script that generates the images.
>
> I would appreciate any help people might be able to offer!  I am running
> ParaView 5.0.1 on Mac OS X 10.11.5.
>
> Thanks,
> Josh Murphy
>
>
>
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Search the list archives at:
> http://markmail.org/search/?q=Paraview-developers
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview-developers
>

From spl at tirebiter.org  Sun Jun 26 20:06:32 2016
From: spl at tirebiter.org (Steve Lamont)
Date: Sun, 26 Jun 2016 17:06:32 -0700
Subject: [Paraview] A request
Message-ID: <20160627000632.173138E2FD4@tirebiter.org>

Is there any way that ParaView could be coded to give a better, more
helpful diagnostic than a core dump when a memory allocation fails?

In fact, could ParaView be coded to use an anonymous memory mapped file
allocation if the standard malloc() fails.  While this would result in
possibly degraded performance, at least one could get some sort of 
visualization done.

Thanks.

							spl

From stephen.wornom at inria.fr  Mon Jun 27 04:14:45 2016
From: stephen.wornom at inria.fr (Stephen Wornom)
Date: Mon, 27 Jun 2016 10:14:45 +0200 (CEST)
Subject: [Paraview] PV 4.1 how to extract a surface
In-Reply-To: <1689747090.39389016.1467014626656.JavaMail.zimbra@inria.fr>
Message-ID: <1993301348.39398155.1467015285186.JavaMail.zimbra@inria.fr>

The mesh is 3D unstructured about a 3D cylinder. I would like to extract the surface of the cylinder. 

I have experience extracting surfaces with another code where the surfaces are defined by a variable (-3= cylinder surface). 
I do it like this: 
1-select extract surface 
2-select conductivity 
3-select threshold (choose -3 which corresponds to the cylinder surface). 

but I am using a code where the cylinder surface is NOT a predefined variable. 
How do I do I extract the surface? 
Hope my question is clear, 
Stephen 


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

From lukasz.paluszek at airbus.com  Mon Jun 27 06:06:13 2016
From: lukasz.paluszek at airbus.com (Paluszek, Lukasz)
Date: Mon, 27 Jun 2016 10:06:13 +0000
Subject: [Paraview] Opacity Issues
In-Reply-To: <13489_1466796170_576D888A_13489_10295_1_CA+=e1osFVg1tZgXnCuCkkqLNigDTB093D_QPd42Pjcfh4=bo3A@mail.gmail.com>
References: <9385_1466781329_576D4E91_9385_11640_1_d6606d3c88134b9bb7ca3e3b5a83459f@DE0-03DAG13-P03.central.mail.corp>
 <13295_1466785464_576D5EB7_13295_19000_1_CA+=e1otaNJNUweQTEqOzSKU0jnDivxMBBcP6FMB-4KY64za6KA@mail.gmail.com>
 <622_1466788260_576D69A4_622_19423_1_7fd68ea2d27f4d6bb0a2ed8cb27e1b71@DE0-03DAG13-P03.central.mail.corp>
 <CA+=e1ov_PyX74TcDMJq2RFqhPGmBuCazwKwrJdTnxWOBpL1f7A@mail.gmail.com>
 <13489_1466796170_576D888A_13489_10295_1_CA+=e1osFVg1tZgXnCuCkkqLNigDTB093D_QPd42Pjcfh4=bo3A@mail.gmail.com>
Message-ID: <18567_1467021978_5770FA9A_18567_834_1_d98830eff0424c24a5bccc0b3d88ca54@DE0-03DAG13-P03.central.mail.corp>

Switching to the old peeling implementation did the trick, no more issues and yes I am using remote rendering via pvserver.

[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>

From: David Lonie [mailto:david.lonie at kitware.com]
Sent: 24 June 2016 21:22
To: Paluszek, Lukasz
Cc: paraview at paraview.org
Subject: Re: [Paraview] Opacity Issues

On Fri, Jun 24, 2016 at 2:15 PM, David Lonie <david.lonie at kitware.com<mailto:david.lonie at kitware.com>> wrote:
On Fri, Jun 24, 2016 at 1:10 PM, Paluszek, Lukasz <lukasz.paluszek at airbus.com<mailto:lukasz.paluszek at airbus.com>> wrote:
It doesn?t happen all the time, I suppose you need a fairly large surface dataset. I managed to reproduce the problem on a wavelet source (attached state file), try increasing the number of elements if you do not see any artifacts. I have bult Paraview from source on OpenSuse 13.1 but also cross-checked with the Linux binaries from Paraview.org and had same issues. There was no problem with the osmesa-llvm flavor though.

I couldn't reproduce this here on arch linux with a newer nVidia driver (367.27), so I'm suspicious that this is a driver bug that's affecting the new depth peeling implementation.

Since you're building from source, can you try editing VTK/Rendering/OpenGL2/vtkOpenGLRenderer.cxx, and change line 322

if (dualDepthPeelingSupported)

to

if (false)

in DeviceRenderTranslucentPolygonalGeometry, recompile using the OpenGL2 backend, and let me know if the issue goes away? I suspect it will since both the OpenGL1 backend and OpenGL2 mesa/llvm do not use the new code.

I'll put together a patch to force the older peeling implementation via an environment variable to make the work-around easier to apply.

Patch is here: https://gitlab.kitware.com/vtk/vtk/merge_requests/1589

By the way, are you running paraview with remote rendering via pvserver? I was just made aware of a similar issue with remote rendering and depth peeling.

Dave

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; Thomas Hundt; 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/20160627/7b2bd28b/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/20160627/7b2bd28b/attachment.png>

From utkarsh.ayachit at kitware.com  Mon Jun 27 08:53:42 2016
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Mon, 27 Jun 2016 08:53:42 -0400
Subject: [Paraview] Scalar scaling of glyphs causes unrecoverable error
In-Reply-To: <576C4744.9030301@gmail.com>
References: <576C4744.9030301@gmail.com>
Message-ID: <CADHSJjBMQY_5UZARmDE-d=uEHn9JnYp4XXOzEj9C3UAWXiJFhg@mail.gmail.com>

Do you have a sample dataset to share to reproduce this issue? Also
what version of ParaView are you trying this with?

On Thu, Jun 23, 2016 at 4:32 PM, Jim <guilfordstuff at gmail.com> wrote:
> I can import (raw binary) a 3D file (1178x1202x1000x1float), extract a
> subset and display it using sphere glyphs where the spheres are too large.
> However, when I set the scale mode to scalar and 1, the program displays
> nothing. The display area is just background color. I can't turn anything on
> or off. If I delete everything and then retry without the scaling, I still
> see nothing.
>
> This looks like some sort of workspace corruption.  It looks like a bug to
> me.
> _______________________________________________
> 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 samuelkey at bresnan.net  Mon Jun 27 09:47:07 2016
From: samuelkey at bresnan.net (Samuel Key)
Date: Mon, 27 Jun 2016 07:47:07 -0600
Subject: [Paraview] PV 4.1 how to extract a surface
In-Reply-To: <1993301348.39398155.1467015285186.JavaMail.zimbra@inria.fr>
References: <1993301348.39398155.1467015285186.JavaMail.zimbra@inria.fr>
Message-ID: <ac99d540-dd63-dec6-eb02-cd812df1c5a6@bresnan.net>

An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160627/2568baa4/attachment.html>

From paul.melis at surfsara.nl  Mon Jun 27 11:29:37 2016
From: paul.melis at surfsara.nl (Paul Melis)
Date: Mon, 27 Jun 2016 17:29:37 +0200
Subject: [Paraview] [EXTERNAL] Client-server mode fails with 5.0.1
In-Reply-To: <571610BA.4080406@surfsara.nl>
References: <5714AED6.5080101@surfsara.nl>
 <c207754961194fd8a69e48f1b9f7f683@ES01AMSNLNT.srn.sandia.gov>
 <571520E7.80300@surfsara.nl>
 <CADHSJjD69fa_HaK3x9DuGTpuThqrsZxLwTCLaEcv8s0raMkJHw@mail.gmail.com>
 <571610BA.4080406@surfsara.nl>
Message-ID: <26d03815-073e-d9ec-3619-191ed47576ee@surfsara.nl>

On 04/19/2016 01:04 PM, Paul Melis wrote:
> 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.
I just tried on a node with an updated nvidia driver (367.27, latest for 
the specific model of GPU used) and get the same error on the server 
side with 5.0.1.

Trying 5.1.0 (binary from paraview.org for both client and server) and I 
no longer get the error and PV seems work fine in client-server mode.

Paul



From paul.melis at surfsara.nl  Mon Jun 27 11:37:44 2016
From: paul.melis at surfsara.nl (Paul Melis)
Date: Mon, 27 Jun 2016 17:37:44 +0200
Subject: [Paraview] [EXTERNAL] Client-server mode fails with 5.0.1
In-Reply-To: <26d03815-073e-d9ec-3619-191ed47576ee@surfsara.nl>
References: <5714AED6.5080101@surfsara.nl>
 <c207754961194fd8a69e48f1b9f7f683@ES01AMSNLNT.srn.sandia.gov>
 <571520E7.80300@surfsara.nl>
 <CADHSJjD69fa_HaK3x9DuGTpuThqrsZxLwTCLaEcv8s0raMkJHw@mail.gmail.com>
 <571610BA.4080406@surfsara.nl>
 <26d03815-073e-d9ec-3619-191ed47576ee@surfsara.nl>
Message-ID: <b976ca43-d010-e2bc-63aa-7f506320b96d@surfsara.nl>



On 06/27/2016 05:29 PM, Paul Melis wrote:
> On 04/19/2016 01:04 PM, Paul Melis wrote:
>> 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.
> I just tried on a node with an updated nvidia driver (367.27, latest 
> for the specific model of GPU used) and get the same error on the 
> server side with 5.0.1.
>
> Trying 5.1.0 (binary from paraview.org for both client and server) and 
> I no longer get the error and PV seems work fine in client-server mode.
This might or might not be related, but while retesting 
http://www.paraview.org/Bug/view.php?id=13802 with 5.1.0 I get an error 
relating to the OpenGL context on the server when switching to slice mode:

paulm at s37n2:~/software/ParaView-5.1.0-Qt4-OpenGL2-MPI-Linux-64bit/bin$ 
./pvserver --use-offscreen-rendering
Waiting for client...
Connection URL: cs://s37n2.int.elvis.surfsara.nl:11111
Accepting connection(s): s37n2.int.elvis.surfsara.nl:11111
Client connected.
Warning: In 
/home/kitware/dashboards/buildbot/paraview-debian6dash-linux-shared-release_opengl2_qt4_superbuild/source-paraview/VTK/Rendering/OpenGL2/vtkOpenGLRenderWindow.cxx, 
line 616
vtkXOpenGLRenderWindow (0x30b0eb0): VTK is designed to work with OpenGL 
version 3.2 but it appears it has been given a context that does not 
support 3.2. VTK will run in a compatibility mode designed to work with 
earlier versions of OpenGL but some features may not work.

Segmentation fault (core dumped)

The supported OpenGL version is 4.2.0, so I don't understand why the 
context is not 3.2 compatible:

$ glxinfo
name of display: :0.0
display: :0  screen: 0
direct rendering: Yes
server glx vendor string: NVIDIA Corporation
server glx version string: 1.4
...
client glx vendor string: NVIDIA Corporation, NVIDIA Corporation
client glx version string: 1.4
...
OpenGL vendor string: NVIDIA Corporation
OpenGL renderer string: GeForce GTX 780 Ti/PCIe/SSE2
OpenGL version string: 4.5.0 NVIDIA 367.27
....

The nvidia driver used is 367.27, Debian 7.11 (wheezy), 64-bit

Paul

From utkarsh.ayachit at kitware.com  Mon Jun 27 13:15:24 2016
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Mon, 27 Jun 2016 13:15:24 -0400
Subject: [Paraview] [EXTERNAL] Client-server mode fails with 5.0.1
In-Reply-To: <b976ca43-d010-e2bc-63aa-7f506320b96d@surfsara.nl>
References: <5714AED6.5080101@surfsara.nl>
 <c207754961194fd8a69e48f1b9f7f683@ES01AMSNLNT.srn.sandia.gov>
 <571520E7.80300@surfsara.nl>
 <CADHSJjD69fa_HaK3x9DuGTpuThqrsZxLwTCLaEcv8s0raMkJHw@mail.gmail.com>
 <571610BA.4080406@surfsara.nl>
 <26d03815-073e-d9ec-3619-191ed47576ee@surfsara.nl>
 <b976ca43-d010-e2bc-63aa-7f506320b96d@surfsara.nl>
Message-ID: <CADHSJjB2Lw2R80wSJBaJmADNTrGoThezNp6p_84Cx1bNqTEccA@mail.gmail.com>

Paul,

Can you try this:
1. Connect to pvserver started with  --use-offscreen-rendering
2. From Edit | Settings, Render View tab, set "Remote Render
Threshold" to 0.  Accept the change using OK.
3. Interact with render view.

Do you get the same segfault? If so, it's independent of what you're
rendering, but just the fact that remote rendering kicks in. We can
then debug further.

Utkarsh

On Mon, Jun 27, 2016 at 11:37 AM, Paul Melis <paul.melis at surfsara.nl> wrote:
>
>
> On 06/27/2016 05:29 PM, Paul Melis wrote:
>>
>> On 04/19/2016 01:04 PM, Paul Melis wrote:
>>>
>>> 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.
>>
>> I just tried on a node with an updated nvidia driver (367.27, latest for
>> the specific model of GPU used) and get the same error on the server side
>> with 5.0.1.
>>
>> Trying 5.1.0 (binary from paraview.org for both client and server) and I
>> no longer get the error and PV seems work fine in client-server mode.
>
> This might or might not be related, but while retesting
> http://www.paraview.org/Bug/view.php?id=13802 with 5.1.0 I get an error
> relating to the OpenGL context on the server when switching to slice mode:
>
> paulm at s37n2:~/software/ParaView-5.1.0-Qt4-OpenGL2-MPI-Linux-64bit/bin$
> ./pvserver --use-offscreen-rendering
> Waiting for client...
> Connection URL: cs://s37n2.int.elvis.surfsara.nl:11111
> Accepting connection(s): s37n2.int.elvis.surfsara.nl:11111
> Client connected.
> Warning: In
> /home/kitware/dashboards/buildbot/paraview-debian6dash-linux-shared-release_opengl2_qt4_superbuild/source-paraview/VTK/Rendering/OpenGL2/vtkOpenGLRenderWindow.cxx,
> line 616
> vtkXOpenGLRenderWindow (0x30b0eb0): VTK is designed to work with OpenGL
> version 3.2 but it appears it has been given a context that does not support
> 3.2. VTK will run in a compatibility mode designed to work with earlier
> versions of OpenGL but some features may not work.
>
> Segmentation fault (core dumped)
>
> The supported OpenGL version is 4.2.0, so I don't understand why the context
> is not 3.2 compatible:
>
> $ glxinfo
> name of display: :0.0
> display: :0  screen: 0
> direct rendering: Yes
> server glx vendor string: NVIDIA Corporation
> server glx version string: 1.4
> ...
> client glx vendor string: NVIDIA Corporation, NVIDIA Corporation
> client glx version string: 1.4
> ...
> OpenGL vendor string: NVIDIA Corporation
> OpenGL renderer string: GeForce GTX 780 Ti/PCIe/SSE2
> OpenGL version string: 4.5.0 NVIDIA 367.27
> ....
>
> The nvidia driver used is 367.27, Debian 7.11 (wheezy), 64-bit
>
> Paul

From dwneumann at gmail.com  Mon Jun 27 13:30:54 2016
From: dwneumann at gmail.com (Dean Neumann)
Date: Mon, 27 Jun 2016 10:30:54 -0700
Subject: [Paraview] vtkPythonProgrammableFilter,
 could not find requested method: "SetCellArrayStatus" ?
Message-ID: <CAGgSO3hssYTAHt_qQ1GuRY37S9jOhsLNMuXJ=pjiw5fAav1R0A@mail.gmail.com>

Fellas,  can someone please point me to examples (current as of v5.0.1) of
how a PythonProgrammableFilter accesses the values of properties entered
via a DropDownList on the filter's Properties panel....

I have written a Python programmable filter which extracts user-specified
field arrays from user-specified blocks of multiple (MultiBlock) input
datasets.  I use this to perfrom statistical analysis of values from many
different simulatyions.
The filter works fine when the field array names and block numbers are
hardcoded in the script.
.
Then I used Pat Marion's python_filter_generator.py to wrap the filter in
XML and allow these values to be entered via TextBoxes in the Properties
panel.   That also works fine.  The property TextBoxes are accessible to
the Python script and I can retrieve the user-entered values.

Then I attempted to change the field array input widget from a textbox to a
DropDownList of cell arrays with checkboxes for selection, following the
example in http://www.paraview.org/Wiki/ParaView/Plugin_HowTo#Drop_down_list.
The DropDownList does appear correctly, populated correctly, along with
checkboxes for selecting items from the list.  However when I hit Apply I
get the following error:


> ERROR: In
>> C:\bbd\5105004d\build\paraview\src\paraview\ParaViewCore\ServerImplementation\Core\vtkPVSessionCore.cxx,
>> line 390
>
> vtkPVSessionCore (00000000036E8610): Object type:
>> vtkPythonProgrammableFilter, could not find requested method:
>> "SetCellArrayStatus"
>
> or the method was called with incorrect arguments.
>
>
>> while processing
>
> Message 0 = Invoke
>
>   Argument 0 = vtk_object_pointer {vtkPythonProgrammableFilter
>> (000000000D1BCCD0)}
>
>   Argument 1 = string_value {SetCellArrayStatus}
>
>   Argument 2 = string_value {cellInputs}
>
>   Argument 3 = int32_value {0}
>
>
>> ERROR: In
>> C:\bbd\5105004d\build\paraview\src\paraview\ParaViewCore\ServerImplementation\Core\vtkPVSessionCore.cxx,
>> line 391
>
> vtkPVSessionCore (00000000036E8610): Aborting execution for debugging
>> purposes.
>
>
>> ERROR: In
>> C:\bbd\5105004d\build\paraview\src\paraview\ParaViewCore\ServerImplementation\Core\vtkSIProxy.cxx,
>> line 134
>
> vtkSISourceProxy (000000000A29BFE0): Error pushing property state:
>> CellArrayStatus
>
>
I looked at the examples in
ParaView/ParaViewCore/ServerManager/SMApplication/Resources/readers.xml
as suggested, but nowhere do I see examples of how a Python script accesses
the user's selections (only examples of the XML code is shown, not the
Python scripts).  I also perused the site-packages subdirectory of my
installation, but those are all compiled Python and of no help.

I'm sure if I just see some Python code examples I can get this working.  I
have attached my filter if that helps...
many thanks for your help.

Dean Neumann
CEO, Malaspina Lans Inc
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160627/39ec77ac/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: SliceAcrossDatasets_Dropdown.xml
Type: text/xml
Size: 4793 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160627/39ec77ac/attachment.xml>

From utkarsh.ayachit at kitware.com  Mon Jun 27 14:56:29 2016
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Mon, 27 Jun 2016 14:56:29 -0400
Subject: [Paraview] vtkPythonProgrammableFilter,
 could not find requested method: "SetCellArrayStatus" ?
In-Reply-To: <CAGgSO3hssYTAHt_qQ1GuRY37S9jOhsLNMuXJ=pjiw5fAav1R0A@mail.gmail.com>
References: <CAGgSO3hssYTAHt_qQ1GuRY37S9jOhsLNMuXJ=pjiw5fAav1R0A@mail.gmail.com>
Message-ID: <CADHSJjC_ExERbdrKBewodiKTz8qQTGERhGVBS=UzUNse37GfhA@mail.gmail.com>

Attached a fixed version. I've also change the "Script" to just print
the value for sFields which is a array of selected array names. You'll
need to update your code accordingly. Note, if the user selected
nothing then sFields will not be defined. So you may want to handle
that in your code as well.

On Mon, Jun 27, 2016 at 1:30 PM, Dean Neumann <dwneumann at gmail.com> wrote:
> Fellas,  can someone please point me to examples (current as of v5.0.1) of
> how a PythonProgrammableFilter accesses the values of properties entered via
> a DropDownList on the filter's Properties panel....
>
> I have written a Python programmable filter which extracts user-specified
> field arrays from user-specified blocks of multiple (MultiBlock) input
> datasets.  I use this to perfrom statistical analysis of values from many
> different simulatyions.
> The filter works fine when the field array names and block numbers are
> hardcoded in the script.
> .
> Then I used Pat Marion's python_filter_generator.py to wrap the filter in
> XML and allow these values to be entered via TextBoxes in the Properties
> panel.   That also works fine.  The property TextBoxes are accessible to the
> Python script and I can retrieve the user-entered values.
>
> Then I attempted to change the field array input widget from a textbox to a
> DropDownList of cell arrays with checkboxes for selection, following the
> example in
> http://www.paraview.org/Wiki/ParaView/Plugin_HowTo#Drop_down_list.  The
> DropDownList does appear correctly, populated correctly, along with
> checkboxes for selecting items from the list.  However when I hit Apply I
> get the following error:
>
>>>
>>> ERROR: In
>>> C:\bbd\5105004d\build\paraview\src\paraview\ParaViewCore\ServerImplementation\Core\vtkPVSessionCore.cxx,
>>> line 390
>>>
>>> vtkPVSessionCore (00000000036E8610): Object type:
>>> vtkPythonProgrammableFilter, could not find requested method:
>>> "SetCellArrayStatus"
>>>
>>> or the method was called with incorrect arguments.
>>>
>>>
>>> while processing
>>>
>>> Message 0 = Invoke
>>>
>>>   Argument 0 = vtk_object_pointer {vtkPythonProgrammableFilter
>>> (000000000D1BCCD0)}
>>>
>>>   Argument 1 = string_value {SetCellArrayStatus}
>>>
>>>   Argument 2 = string_value {cellInputs}
>>>
>>>   Argument 3 = int32_value {0}
>>>
>>>
>>> ERROR: In
>>> C:\bbd\5105004d\build\paraview\src\paraview\ParaViewCore\ServerImplementation\Core\vtkPVSessionCore.cxx,
>>> line 391
>>>
>>> vtkPVSessionCore (00000000036E8610): Aborting execution for debugging
>>> purposes.
>>>
>>>
>>> ERROR: In
>>> C:\bbd\5105004d\build\paraview\src\paraview\ParaViewCore\ServerImplementation\Core\vtkSIProxy.cxx,
>>> line 134
>>>
>>> vtkSISourceProxy (000000000A29BFE0): Error pushing property state:
>>> CellArrayStatus
>
>
> I looked at the examples in
> ParaView/ParaViewCore/ServerManager/SMApplication/Resources/readers.xml as
> suggested, but nowhere do I see examples of how a Python script accesses the
> user's selections (only examples of the XML code is shown, not the Python
> scripts).  I also perused the site-packages subdirectory of my installation,
> but those are all compiled Python and of no help.
>
> I'm sure if I just see some Python code examples I can get this working.  I
> have attached my filter if that helps...
> many thanks for your help.
>
> Dean Neumann
> CEO, Malaspina Lans 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
>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: SliceAcrossDatasets_Dropdown.xml
Type: text/xml
Size: 2857 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160627/c16f87f2/attachment.xml>

From david.lonie at kitware.com  Mon Jun 27 15:34:09 2016
From: david.lonie at kitware.com (David Lonie)
Date: Mon, 27 Jun 2016 15:34:09 -0400
Subject: [Paraview] Opacity Issues
In-Reply-To: <18567_1467021978_5770FA9A_18567_834_1_d98830eff0424c24a5bccc0b3d88ca54@DE0-03DAG13-P03.central.mail.corp>
References: <9385_1466781329_576D4E91_9385_11640_1_d6606d3c88134b9bb7ca3e3b5a83459f@DE0-03DAG13-P03.central.mail.corp>
 <13295_1466785464_576D5EB7_13295_19000_1_CA+=e1otaNJNUweQTEqOzSKU0jnDivxMBBcP6FMB-4KY64za6KA@mail.gmail.com>
 <622_1466788260_576D69A4_622_19423_1_7fd68ea2d27f4d6bb0a2ed8cb27e1b71@DE0-03DAG13-P03.central.mail.corp>
 <CA+=e1ov_PyX74TcDMJq2RFqhPGmBuCazwKwrJdTnxWOBpL1f7A@mail.gmail.com>
 <13489_1466796170_576D888A_13489_10295_1_CA+=e1osFVg1tZgXnCuCkkqLNigDTB093D_QPd42Pjcfh4=bo3A@mail.gmail.com>
 <18567_1467021978_5770FA9A_18567_834_1_d98830eff0424c24a5bccc0b3d88ca54@DE0-03DAG13-P03.central.mail.corp>
Message-ID: <CA+=e1ot_uAPQ=u=QsTTTy4V4P40SNwgZhiUYYWy9FRvcyK+i2A@mail.gmail.com>

This patch fixes the remote-rendering issue in the new peeling
implementation:

https://gitlab.kitware.com/vtk/vtk/merge_requests/1589

Cheers,
Dave

On Mon, Jun 27, 2016 at 6:06 AM, Paluszek, Lukasz <
lukasz.paluszek at airbus.com> wrote:

> Switching to the old peeling implementation did the trick, no more issues
> and yes I am using remote rendering via pvserver.
>
>
>
> [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
>
>
>
> *From:* David Lonie [mailto:david.lonie at kitware.com]
> *Sent:* 24 June 2016 21:22
> *To:* Paluszek, Lukasz
> *Cc:* paraview at paraview.org
> *Subject:* Re: [Paraview] Opacity Issues
>
>
>
> On Fri, Jun 24, 2016 at 2:15 PM, David Lonie <david.lonie at kitware.com>
> wrote:
>
> On Fri, Jun 24, 2016 at 1:10 PM, Paluszek, Lukasz <
> lukasz.paluszek at airbus.com> wrote:
>
> It doesn?t happen all the time, I suppose you need a fairly large surface
> dataset. I managed to reproduce the problem on a wavelet source (attached
> state file), try increasing the number of elements if you do not see any
> artifacts. I have bult Paraview from source on OpenSuse 13.1 but also
> cross-checked with the Linux binaries from Paraview.org and had same
> issues. There was no problem with the osmesa-llvm flavor though.
>
>
>
> I couldn't reproduce this here on arch linux with a newer nVidia driver
> (367.27), so I'm suspicious that this is a driver bug that's affecting the
> new depth peeling implementation.
>
>
>
> Since you're building from source, can you try editing
> VTK/Rendering/OpenGL2/vtkOpenGLRenderer.cxx, and change line 322
>
>
>
> if (dualDepthPeelingSupported)
>
>
>
> to
>
>
>
> if (false)
>
>
>
> in *DeviceRenderTranslucentPolygonalGeometry*, recompile using the
> OpenGL2 backend, and let me know if the issue goes away? I suspect it will
> since both the OpenGL1 backend and OpenGL2 mesa/llvm do not use the new
> code.
>
>
>
> I'll put together a patch to force the older peeling implementation via an
> environment variable to make the work-around easier to apply.
>
>
>
> Patch is here: https://gitlab.kitware.com/vtk/vtk/merge_requests/1589
>
>
>
> By the way, are you running paraview with remote rendering via pvserver? I
> was just made aware of a similar issue with remote rendering and depth
> peeling.
>
>
>
> Dave
>
> 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; Thomas Hundt; 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/20160627/c03b905f/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/20160627/c03b905f/attachment.png>

From dwneumann at gmail.com  Mon Jun 27 16:21:25 2016
From: dwneumann at gmail.com (Dean Neumann)
Date: Mon, 27 Jun 2016 13:21:25 -0700
Subject: [Paraview] vtkPythonProgrammableFilter,
 could not find requested method: "SetCellArrayStatus" ?
In-Reply-To: <CADHSJjC_ExERbdrKBewodiKTz8qQTGERhGVBS=UzUNse37GfhA@mail.gmail.com>
References: <CAGgSO3hssYTAHt_qQ1GuRY37S9jOhsLNMuXJ=pjiw5fAav1R0A@mail.gmail.com>
 <CADHSJjC_ExERbdrKBewodiKTz8qQTGERhGVBS=UzUNse37GfhA@mail.gmail.com>
Message-ID: <CAGgSO3hYxkCENedi0A=uyHwphgPpwfZFq2FmVYiz80RRi+Rp2w@mail.gmail.com>

thank you Utkarsh.   Your fix works like a charm.
Regards,
Dean

On Mon, Jun 27, 2016 at 11:56 AM, Utkarsh Ayachit <
utkarsh.ayachit at kitware.com> wrote:

> Attached a fixed version. I've also change the "Script" to just print
> the value for sFields which is a array of selected array names. You'll
> need to update your code accordingly. Note, if the user selected
> nothing then sFields will not be defined. So you may want to handle
> that in your code as well.
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160627/bb60ee58/attachment.html>

From malurobu at gmail.com  Mon Jun 27 18:35:16 2016
From: malurobu at gmail.com (Mariana Rodriguez)
Date: Mon, 27 Jun 2016 18:35:16 -0400
Subject: [Paraview] boundary export data
Message-ID: <0A5323CB-6435-40FA-AEF5-E8B4DC430BC2@gmail.com>

Hello,
I have a file with certani values of p and T. I want to export to a .e file that data, but also the boundaries of my mesh (keeping the names and the definition).
Does anyone know how to do this?
My .e file contain all the data but not the boundaries. I need the boundaries to start another simulation from this .e file.
Thank you,
Mariana

From dkxls23 at gmail.com  Tue Jun 28 00:24:58 2016
From: dkxls23 at gmail.com (Armin Wehrfritz)
Date: Tue, 28 Jun 2016 04:24:58 +0000
Subject: [Paraview] Transparent background in python scripts
In-Reply-To: <CADHSJjB0UxGvn6jVimh2pEP-7HEN1nTa3aQQg4sHQxEvahUyVA@mail.gmail.com>
References: <576813D4.8090804@gmail.com>
 <CADHSJjB0UxGvn6jVimh2pEP-7HEN1nTa3aQQg4sHQxEvahUyVA@mail.gmail.com>
Message-ID: <7wmb55.o9gs9p.31lq5f-qmf@smtp.gmail.com>

Thanks, I would really appreciate this feature. 
I'm looking forward to 5.2 then. :)


-Armin 



On Wed Jun 22 23:42:11 2016 GMT+0300, Utkarsh Ayachit wrote:
> Currently, it's not exposed to Python. It's on the TODO list to get
> that fixed for 5.2.
> 
> On Mon, Jun 20, 2016 at 12:03 PM, Armin Wehrfritz <dkxls23 at gmail.com> wrote:
> > Hi!
> >
> > How can I save screenshots with a transparent (alpha channel based)
> > background from a python script?
> >
> > Currently, I'm using this command to save screenshots:
> >>
> >> SaveScreenshot('image.png', magnification=3, view=renderView)
> >
> > But this does not write the alpha channel information.
> >
> >
> > Using "File/ Save Screenshot" in the Paraview GUI, the screenshots
> > have the alpha channel information saved correctly when I setting "Edit/
> > Settings/ General/ Transparent Background".
> >
> > I'm using ParaView 5.0.1 on a 64bit Linux workstation with the latest
> > Nvidia driver (367.27).
> >
> >
> > -Armin
> > _______________________________________________
> > 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 stephane at fujielectric.com  Tue Jun 28 04:24:40 2016
From: stephane at fujielectric.com (=?UTF-8?B?c3RlcGhhbmXjg7Pjg4njg7PjgrAg44Oh44OV44Kh44ON?=)
Date: Tue, 28 Jun 2016 17:24:40 +0900
Subject: [Paraview] Import of .PLY fails in Paraview 5.1
Message-ID: <CADLMsL5VrW=2=1fwCvkp-Oj-=Kh8pEMPKw0p_A6ifAzwZBQ=NA@mail.gmail.com>

Hello,

Paraview crashes everytime I try to import a point cloud (.PLY) file.The
same problem occurs when it is a .PLY file exported from Paraview. Any idea
on how to solve that problem?

Ndong-Mefane Stephane, Dr.Eng
Basic Design Sec.
Steam Turbine Dept.
Kawasaki Factory

Fuji Electric Co., Ltd
1-1, Tanabeshinden, Kawasaki-ku,
Kawasaki-city 210-9530, Japan
Phone: +81-44-329-2155
Fax: +81-44-329-2394
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160628/9dbbf4e3/attachment.html>

From stephane at fujielectric.com  Tue Jun 28 04:38:40 2016
From: stephane at fujielectric.com (=?UTF-8?B?c3RlcGhhbmXjg7Pjg4njg7PjgrAg44Oh44OV44Kh44ON?=)
Date: Tue, 28 Jun 2016 17:38:40 +0900
Subject: [Paraview] Interpolating Point Clouds
Message-ID: <CADLMsL4UZueOFMs5qJ4GY3bvNX4aaXwStwj-koFXSkKGKb1i_w@mail.gmail.com>

Hello,

On what kind of input does the "interpolating point cloud" does work?
I imported a VRML point cloud and even extracted the points of interest,
but the interpolation tools are grayed out and cannot be used.

Ndong-Mefane Stephane, Dr.Eng
Basic Design Sec.
Steam Turbine Dept.
Kawasaki Factory

Fuji Electric Co., Ltd
1-1, Tanabeshinden, Kawasaki-ku,
Kawasaki-city 210-9530, Japan
Phone: +81-44-329-2155
Fax: +81-44-329-2394
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160628/c6bcadcf/attachment.html>

From paul.melis at surfsara.nl  Tue Jun 28 07:49:31 2016
From: paul.melis at surfsara.nl (Paul Melis)
Date: Tue, 28 Jun 2016 13:49:31 +0200
Subject: [Paraview] [EXTERNAL] Client-server mode fails with 5.0.1
In-Reply-To: <CADHSJjB2Lw2R80wSJBaJmADNTrGoThezNp6p_84Cx1bNqTEccA@mail.gmail.com>
References: <5714AED6.5080101@surfsara.nl>
 <c207754961194fd8a69e48f1b9f7f683@ES01AMSNLNT.srn.sandia.gov>
 <571520E7.80300@surfsara.nl>
 <CADHSJjD69fa_HaK3x9DuGTpuThqrsZxLwTCLaEcv8s0raMkJHw@mail.gmail.com>
 <571610BA.4080406@surfsara.nl>
 <26d03815-073e-d9ec-3619-191ed47576ee@surfsara.nl>
 <b976ca43-d010-e2bc-63aa-7f506320b96d@surfsara.nl>
 <CADHSJjB2Lw2R80wSJBaJmADNTrGoThezNp6p_84Cx1bNqTEccA@mail.gmail.com>
Message-ID: <b7fe80c3-237d-c416-5798-ccc7ecf1a4b8@surfsara.nl>

Hi Utkarsh,

On 06/27/2016 07:15 PM, Utkarsh Ayachit wrote:
> Paul,
>
> Can you try this:
> 1. Connect to pvserver started with  --use-offscreen-rendering
> 2. From Edit | Settings, Render View tab, set "Remote Render
> Threshold" to 0.  Accept the change using OK.
As soon as I set the threshold to 0 the warning about the OpenGL 3.2 
context pops up (but no segfault in this case).

I tried a very minimal example that creates a 3.2 context (using SDL) 
and that fails as well, so maybe something strange is going in with our 
nvidia driver installation. I'll see if I can do some more tests.

Paul
> 3. Interact with render view.
>
> Do you get the same segfault? If so, it's independent of what you're
> rendering, but just the fact that remote rendering kicks in. We can
> then debug further.
>
> Utkarsh
>
> On Mon, Jun 27, 2016 at 11:37 AM, Paul Melis <paul.melis at surfsara.nl> wrote:
>>
>> On 06/27/2016 05:29 PM, Paul Melis wrote:
>>> On 04/19/2016 01:04 PM, Paul Melis wrote:
>>>> 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.
>>> I just tried on a node with an updated nvidia driver (367.27, latest for
>>> the specific model of GPU used) and get the same error on the server side
>>> with 5.0.1.
>>>
>>> Trying 5.1.0 (binary from paraview.org for both client and server) and I
>>> no longer get the error and PV seems work fine in client-server mode.
>> This might or might not be related, but while retesting
>> http://www.paraview.org/Bug/view.php?id=13802 with 5.1.0 I get an error
>> relating to the OpenGL context on the server when switching to slice mode:
>>
>> paulm at s37n2:~/software/ParaView-5.1.0-Qt4-OpenGL2-MPI-Linux-64bit/bin$
>> ./pvserver --use-offscreen-rendering
>> Waiting for client...
>> Connection URL: cs://s37n2.int.elvis.surfsara.nl:11111
>> Accepting connection(s): s37n2.int.elvis.surfsara.nl:11111
>> Client connected.
>> Warning: In
>> /home/kitware/dashboards/buildbot/paraview-debian6dash-linux-shared-release_opengl2_qt4_superbuild/source-paraview/VTK/Rendering/OpenGL2/vtkOpenGLRenderWindow.cxx,
>> line 616
>> vtkXOpenGLRenderWindow (0x30b0eb0): VTK is designed to work with OpenGL
>> version 3.2 but it appears it has been given a context that does not support
>> 3.2. VTK will run in a compatibility mode designed to work with earlier
>> versions of OpenGL but some features may not work.
>>
>> Segmentation fault (core dumped)
>>
>> The supported OpenGL version is 4.2.0, so I don't understand why the context
>> is not 3.2 compatible:
>>
>> $ glxinfo
>> name of display: :0.0
>> display: :0  screen: 0
>> direct rendering: Yes
>> server glx vendor string: NVIDIA Corporation
>> server glx version string: 1.4
>> ...
>> client glx vendor string: NVIDIA Corporation, NVIDIA Corporation
>> client glx version string: 1.4
>> ...
>> OpenGL vendor string: NVIDIA Corporation
>> OpenGL renderer string: GeForce GTX 780 Ti/PCIe/SSE2
>> OpenGL version string: 4.5.0 NVIDIA 367.27
>> ....
>>
>> The nvidia driver used is 367.27, Debian 7.11 (wheezy), 64-bit
>>
>> Paul


From joseph.g.hennessey2.ctr at mail.mil  Tue Jun 28 09:57:20 2016
From: joseph.g.hennessey2.ctr at mail.mil (Hennessey, Joseph G CTR USARMY RDECOM ARL (US))
Date: Tue, 28 Jun 2016 13:57:20 +0000
Subject: [Paraview] Issues with ParaView 5.1.0 and VGL (UNCLASSIFIED)
Message-ID: <10A03274360DCF47A6EE78C9952A31CA775DE313@UMECHPA7C.easf.csd.disa.mil>

CLASSIFICATION: UNCLASSIFIED

Hello,

I am experiencing an error when running ParaView 5.1.0 using VGL

When starting ParaView 5.1.0 I get the following warnings

[VGL] WARNING: The OpenGL rendering context obtained on X display
[VGL]    :0.0 is indirect, which may cause performance to suffer.
[VGL]    If :0.0 is a local X display, then the framebuffer device
[VGL]    permissions may be set incorrectly.

And then ParaView 5.1.0 seg faults.

ParaView 5.0.1 when run under VGL does not produce the same
warnings and works just fine.

Is their some new requirement for VGL support that ParaView 5.1.0 has
over version 5.0.1?

Thanks,

Joe

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Joseph G. Hennessey Ph.D., Lockheed Martin
Army Research Lab
DOD Supercomputing Resource Center
Email:  joseph.g.hennessey2.ctr at mail.mil



CLASSIFICATION: UNCLASSIFIED
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 5615 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160628/9f44b576/attachment.bin>

From utkarsh.ayachit at kitware.com  Tue Jun 28 10:29:26 2016
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Tue, 28 Jun 2016 10:29:26 -0400
Subject: [Paraview] [EXTERNAL] Client-server mode fails with 5.0.1
In-Reply-To: <b7fe80c3-237d-c416-5798-ccc7ecf1a4b8@surfsara.nl>
References: <5714AED6.5080101@surfsara.nl>
 <c207754961194fd8a69e48f1b9f7f683@ES01AMSNLNT.srn.sandia.gov>
 <571520E7.80300@surfsara.nl>
 <CADHSJjD69fa_HaK3x9DuGTpuThqrsZxLwTCLaEcv8s0raMkJHw@mail.gmail.com>
 <571610BA.4080406@surfsara.nl>
 <26d03815-073e-d9ec-3619-191ed47576ee@surfsara.nl>
 <b976ca43-d010-e2bc-63aa-7f506320b96d@surfsara.nl>
 <CADHSJjB2Lw2R80wSJBaJmADNTrGoThezNp6p_84Cx1bNqTEccA@mail.gmail.com>
 <b7fe80c3-237d-c416-5798-ccc7ecf1a4b8@surfsara.nl>
Message-ID: <CADHSJjD1NJJ9kWjR4F7yY67GB_SZ2JOZePswRCEamC2U3j6XLw@mail.gmail.com>

> As soon as I set the threshold to 0 the warning about the OpenGL 3.2 context
> pops up (but no segfault in this case).

No segfault just means that the scene didn't attempt to rendering
something that needed newer OpenGL.

> I tried a very minimal example that creates a 3.2 context (using SDL) and
> that fails as well, so maybe something strange is going in with our nvidia
> driver installation. I'll see if I can do some more tests.

Cool. Thanks.

From peterdebuchev at gmail.com  Tue Jun 28 11:46:46 2016
From: peterdebuchev at gmail.com (Peter Debuchev)
Date: Tue, 28 Jun 2016 17:46:46 +0200
Subject: [Paraview] Can a collaborative client share a pipeline without
 creating a view itself?
In-Reply-To: <CAAUk9C7mO1TEqzeU+HwJKk7mefmDdMq5M11eoAHSSXLd3A1HvQ@mail.gmail.com>
References: <CAAUk9C7zY8P25QWDeZdcCA7Vx18uiBBe_+_LbyepsFt8FUQaGA@mail.gmail.com>
 <CADHSJjAj5of=VckLN=VCe5KoHhaPqzYck79u=kGLpfrtO3856Q@mail.gmail.com>
 <CAAUk9C5WDLoKXx58XVCHSQCQycX-TSMM=Y8FuGCU1EJ-e4bhjA@mail.gmail.com>
 <CADHSJjB1SXkBJZH70bw7ssWupe+ZTckGRcLnhRrfNFcpPvN9xQ@mail.gmail.com>
 <CAAUk9C7mO1TEqzeU+HwJKk7mefmDdMq5M11eoAHSSXLd3A1HvQ@mail.gmail.com>
Message-ID: <CAAUk9C5yGqeXjb99=_8ffNy9Wk2DWDzXT53_=cQC=bai2Mn6kA@mail.gmail.com>

Dear Utkarsh,
I tried to reproduce the error as described in my previous email, but
haven't been able to until now, don't know what happend. The attached code
attaches to a pvserver at localhost:11111 and adds a sphere every half
second. Unfortunately it crashes as soon as I connect ParaView to the same
server.
I guess I'll have to give up programming ParaView and work the old way,
writing VTK files and loading them in ParaView. It is way too complicated.

Peter

2016-06-24 7:08 GMT+02:00 Peter Debuchev <peterdebuchev at gmail.com>:

> Thank you for the patch. There is still something missing. If I modify the
> custom client such that it adds an object every half second or so, then
> first start this clients and then ParaView after a few seconds, ParaView
> misses one of the objects. ParaView finds those objects that are added
> before ParaView starts and those that are added later. But during ParaView
> startup one of the objects is lost.
> I'll see if I can make this reproducible and send a code example in the
> next days.
>
> Peter
>
> 2016-06-22 17:25 GMT+02:00 Utkarsh Ayachit <utkarsh.ayachit at kitware.com>:
>
>> > can you give a quick update whether the suggested bug fix is likely to
>> be
>> > solved:
>>
>> Here you go:
>> https://gitlab.kitware.com/paraview/paraview/merge_requests/844
>>
>> Once the dashboards come back clean, this will get merged. If do get
>> around to testing it, I'd suggest getting involved and giving the
>> merge-request a +1 ;).
>>
>> Utkarsh
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160628/2dab3e54/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: main.cxx
Type: text/x-c++src
Size: 3519 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160628/2dab3e54/attachment.cxx>

From samuelkey at bresnan.net  Tue Jun 28 11:48:24 2016
From: samuelkey at bresnan.net (Samuel Key)
Date: Tue, 28 Jun 2016 09:48:24 -0600
Subject: [Paraview] boundary export data
In-Reply-To: <0A5323CB-6435-40FA-AEF5-E8B4DC430BC2@gmail.com>
References: <0A5323CB-6435-40FA-AEF5-E8B4DC430BC2@gmail.com>
Message-ID: <70967436-d08f-aef2-ebc4-85cfe730d56b@bresnan.net>

Marina,

Have you tried ParaViews Extract Block filter followed by Save Data?

Sam


On 6/27/2016 4:35 PM, Mariana Rodriguez wrote:
> Hello,
> I have a file with certani values of p and T. I want to export to a .e file that data, but also the boundaries of my mesh (keeping the names and the definition).
> Does anyone know how to do this?
> My .e file contain all the data but not the boundaries. I need the boundaries to start another simulation from this .e file.
> Thank you,
> Mariana
> _______________________________________________
> 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  Tue Jun 28 14:42:37 2016
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Tue, 28 Jun 2016 14:42:37 -0400
Subject: [Paraview] Interpolating Point Clouds
In-Reply-To: <CADLMsL4UZueOFMs5qJ4GY3bvNX4aaXwStwj-koFXSkKGKb1i_w@mail.gmail.com>
References: <CADLMsL4UZueOFMs5qJ4GY3bvNX4aaXwStwj-koFXSkKGKb1i_w@mail.gmail.com>
Message-ID: <CADHSJjDkhCcJCHX9xq4uEKbZbPQxa0i01Ok6pD7BTW3Ngs5A-A@mail.gmail.com>

The "Point Interpolation" filters need a scalar array to be present on
the dataset.

On Tue, Jun 28, 2016 at 4:38 AM, stephane???? ????
<stephane at fujielectric.com> wrote:
> Hello,
>
> On what kind of input does the "interpolating point cloud" does work?
> I imported a VRML point cloud and even extracted the points of interest, but
> the interpolation tools are grayed out and cannot be used.
>
> Ndong-Mefane Stephane, Dr.Eng
> Basic Design Sec.
> Steam Turbine Dept.
> Kawasaki Factory
>
> Fuji Electric Co., Ltd
> 1-1, Tanabeshinden, Kawasaki-ku,
> Kawasaki-city 210-9530, Japan
> Phone: +81-44-329-2155
> Fax: +81-44-329-2394
>
>
> _______________________________________________
> 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 david.lonie at kitware.com  Tue Jun 28 15:06:23 2016
From: david.lonie at kitware.com (David Lonie)
Date: Tue, 28 Jun 2016 15:06:23 -0400
Subject: [Paraview] Minor bug in OPENFOAM import filter
In-Reply-To: <AM4PR08MB1188D0A13FFA958B1BA8F73E8B2F0@AM4PR08MB1188.eurprd08.prod.outlook.com>
References: <CA+=e1ouj8q447Q0uKPM6WtBPGphMM+Fc=R7hqSzDB6RNE1_A8w@mail.gmail.com>
 <AM4PR08MB1188DE8BD6DCE85F6005673D8B2C0@AM4PR08MB1188.eurprd08.prod.outlook.com>
 <CA+=e1otGNN2HFHh_nBLvrgq3cH3+hvJcHUZz5F0uQ6WNWKiQXg@mail.gmail.com>
 <20160625.201110.156085895.oshima@eng.niigata-u.ac.jp>
 <AM4PR08MB1188D0A13FFA958B1BA8F73E8B2F0@AM4PR08MB1188.eurprd08.prod.outlook.com>
Message-ID: <CA+=e1oudenUnZCc4Ni8WZQuLxFUk+FZVVk3wgD8ZqD+5Dtn5pg@mail.gmail.com>

On Sat, Jun 25, 2016 at 1:02 PM, Eugene de Villiers <e.devilliers at engys.com>
wrote:

> Hi Takuya, David,
>
> That would be perfect. What kind of timeline are we looking at to see this
> in a release version?
>

It's difficult to say for sure. It might be out in the next patch release,
but it might have to wait for the next major/minor release. The openFOAM
reader is a complicated bit of code, I'm still investigating the best way
to go about implementing this. I'll update this thread once I know more.

Dave
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160628/2f94ec57/attachment.html>

From rdjamis at sandia.gov  Tue Jun 28 16:14:06 2016
From: rdjamis at sandia.gov (Jamison, Ryan Dale)
Date: Tue, 28 Jun 2016 20:14:06 +0000
Subject: [Paraview] [EXTERNAL]  Visualization of strata in ParaView
In-Reply-To: <576159CE.7010609@tirebiter.org>
References: <576159CE.7010609@tirebiter.org>
Message-ID: <EEB4245A-5F22-4878-9918-9C0908D5D386@sandia.gov>

I know this is thread is already a couple of weeks old, but I was curious if you ever figured out how to set the NaN color to have an opacity of zero? I?ve been wanting to something very similar. 
Best, Ryan Jamison

> On Jun 15, 2016, at 7:36 AM, Steve Lamont <spl at tirebiter.org> wrote:
> 
> Before starting, I should state that I'm a complete noob to ParaView, having only worked with it for a couple of weeks, so if this is a FAQ, I will be humbly abashed if pointed to somewhere rather obvious.
> 
> I have a dataset which is somewhat different than those which I believe are normally visualized with ParaView.  It is of geological strata and the samples are of discrete layers, rather than samples of some continuous function.  Furthermore, there are missing data or void regions.
> 
> I would like to display cross sections of these data showing the layers without color interpolation.  Is there a way to tell ParaView to display the colors in a step function rather than as a "continuous tone?"
> 
> Also, is there a way to tell ParaView to display the missing data as completely transparent -- in other words, setting the NaN color to having an opacity of zero?
> 
> Thanks for your attention and helpful RTFMs.
> 
> Regards.
> 
> 							spl
> 
> _______________________________________________
> 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 david.lonie at kitware.com  Tue Jun 28 16:40:07 2016
From: david.lonie at kitware.com (David Lonie)
Date: Tue, 28 Jun 2016 16:40:07 -0400
Subject: [Paraview] Minor bug in OPENFOAM import filter
In-Reply-To: <CA+=e1oudenUnZCc4Ni8WZQuLxFUk+FZVVk3wgD8ZqD+5Dtn5pg@mail.gmail.com>
References: <CA+=e1ouj8q447Q0uKPM6WtBPGphMM+Fc=R7hqSzDB6RNE1_A8w@mail.gmail.com>
 <AM4PR08MB1188DE8BD6DCE85F6005673D8B2C0@AM4PR08MB1188.eurprd08.prod.outlook.com>
 <CA+=e1otGNN2HFHh_nBLvrgq3cH3+hvJcHUZz5F0uQ6WNWKiQXg@mail.gmail.com>
 <20160625.201110.156085895.oshima@eng.niigata-u.ac.jp>
 <AM4PR08MB1188D0A13FFA958B1BA8F73E8B2F0@AM4PR08MB1188.eurprd08.prod.outlook.com>
 <CA+=e1oudenUnZCc4Ni8WZQuLxFUk+FZVVk3wgD8ZqD+5Dtn5pg@mail.gmail.com>
Message-ID: <CA+=e1ouM=L1iv2u74eb4keSn-w+S_U9WpXjS28+eQA+8FNCJNg@mail.gmail.com>

On Tue, Jun 28, 2016 at 3:06 PM, David Lonie <david.lonie at kitware.com>
wrote:

> On Sat, Jun 25, 2016 at 1:02 PM, Eugene de Villiers <
> e.devilliers at engys.com> wrote:
>
>> Hi Takuya, David,
>>
>> That would be perfect. What kind of timeline are we looking at to see
>> this in a release version?
>>
>
> It's difficult to say for sure. It might be out in the next patch release,
> but it might have to wait for the next major/minor release. The openFOAM
> reader is a complicated bit of code, I'm still investigating the best way
> to go about implementing this. I'll update this thread once I know more.
>

Good news -- I found an easy fix. Instead of failing outright when

(scalar (scalar scalar))

is found because the internal data structures can't handle nested lists
following scalar data, I patched the reader to simply read the nested list,
discard it, print a warning, and continue reading the file.

You'll still see a warning pop up in paraview, but the file should still
read successfully as long as the unsupported list does not appear in a
field used for visualization.

The patch is here: https://gitlab.kitware.com/vtk/vtk/merge_requests/1598

If this is agreeable to everyone, we'll get it merged and incorporated into
a future release.

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

From huangrui.mo at uwaterloo.ca  Tue Jun 28 17:47:58 2016
From: huangrui.mo at uwaterloo.ca (Huangrui Mo)
Date: Tue, 28 Jun 2016 17:47:58 -0400
Subject: [Paraview] A Potential Bug About Glyph (Paraview 5.1.0)
In-Reply-To: <9dc162fc-3ef3-9eae-1367-54e27ce841b9@uwaterloo.ca>
References: <9dc162fc-3ef3-9eae-1367-54e27ce841b9@uwaterloo.ca>
Message-ID: <31c64ebc-7e85-7a99-e39d-d7e3d3846363@uwaterloo.ca>

Dear Paraview Developer,

When using the Glyph function to rend point sets, it may skip some 
points, as shown below

This happens either in steady case or a unsteady case. In the latter, 
Glyph works at first and then disappear afterward.

The .vtp file for generating the above point set has been attached in 
this email.

Thank you very much for taking time to read this email.

Sincerely,

Huangrui Mo


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160628/497754f9/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 37614 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160628/497754f9/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: point_set_for_glyph_test.vtp
Type: text/xml
Size: 40269 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160628/497754f9/attachment.xml>

From wascott at sandia.gov  Tue Jun 28 18:23:41 2016
From: wascott at sandia.gov (Scott, W Alan)
Date: Tue, 28 Jun 2016 22:23:41 +0000
Subject: [Paraview] [EXTERNAL] A Potential Bug About Glyph (Paraview
 5.1.0)
In-Reply-To: <31c64ebc-7e85-7a99-e39d-d7e3d3846363@uwaterloo.ca>
References: <9dc162fc-3ef3-9eae-1367-54e27ce841b9@uwaterloo.ca>
 <31c64ebc-7e85-7a99-e39d-d7e3d3846363@uwaterloo.ca>
Message-ID: <04b833b541ed43a7883d9eb3b50dc371@ES01AMSNLNT.srn.sandia.gov>

Huangrui Mo,

Try outputting a glyph every point.  On the Properties tab, under Masking, Glyph Mode, change this to off.

Alan


From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Huangrui Mo
Sent: Tuesday, June 28, 2016 3:48 PM
To: paraview at paraview.org
Subject: [EXTERNAL] [Paraview] A Potential Bug About Glyph (Paraview 5.1.0)


Dear Paraview Developer,

When using the Glyph function to rend point sets, it may skip some points, as shown below

[cid:image002.jpg at 01D1D159.6CD64010]

This happens either in steady case or a unsteady case. In the latter, Glyph works at first and then disappear afterward.

The .vtp file for generating the above point set has been attached in this email.

Thank you very much for taking time to read this email.

Sincerely,

Huangrui Mo


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160628/69c57747/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.jpg
Type: image/jpeg
Size: 32528 bytes
Desc: image002.jpg
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160628/69c57747/attachment.jpg>

From wascott at sandia.gov  Tue Jun 28 18:29:55 2016
From: wascott at sandia.gov (Scott, W Alan)
Date: Tue, 28 Jun 2016 22:29:55 +0000
Subject: [Paraview] [EXTERNAL]  Visualization of strata in ParaView
In-Reply-To: <EEB4245A-5F22-4878-9918-9C0908D5D386@sandia.gov>
References: <576159CE.7010609@tirebiter.org>
 <EEB4245A-5F22-4878-9918-9C0908D5D386@sandia.gov>
Message-ID: <f5422ae8725c480badbfdc9d8918ae92@ES01AMSNLNT.srn.sandia.gov>

Ryan/ Steve,
I don't believe that it is possible to change the opacity of NAN data to transparent.  I added a bug, here:  http://www.paraview.org/Bug/view.php?id=16759.

Alan


-----Original Message-----
From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Jamison, Ryan Dale
Sent: Tuesday, June 28, 2016 2:14 PM
To: Steve Lamont <spl at tirebiter.org>
Cc: paraview at paraview.org
Subject: Re: [Paraview] [EXTERNAL] Visualization of strata in ParaView

I know this is thread is already a couple of weeks old, but I was curious if you ever figured out how to set the NaN color to have an opacity of zero? I?ve been wanting to something very similar. 
Best, Ryan Jamison

> On Jun 15, 2016, at 7:36 AM, Steve Lamont <spl at tirebiter.org> wrote:
> 
> Before starting, I should state that I'm a complete noob to ParaView, having only worked with it for a couple of weeks, so if this is a FAQ, I will be humbly abashed if pointed to somewhere rather obvious.
> 
> I have a dataset which is somewhat different than those which I believe are normally visualized with ParaView.  It is of geological strata and the samples are of discrete layers, rather than samples of some continuous function.  Furthermore, there are missing data or void regions.
> 
> I would like to display cross sections of these data showing the layers without color interpolation.  Is there a way to tell ParaView to display the colors in a step function rather than as a "continuous tone?"
> 
> Also, is there a way to tell ParaView to display the missing data as completely transparent -- in other words, setting the NaN color to having an opacity of zero?
> 
> Thanks for your attention and helpful RTFMs.
> 
> Regards.
> 
> 							spl
> 
> _______________________________________________
> 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 janessasocialmedia at gmail.com  Wed Jun 29 00:44:44 2016
From: janessasocialmedia at gmail.com (Janessa Tran)
Date: Tue, 28 Jun 2016 21:44:44 -0700
Subject: [Paraview] Animating trajectories of points
Message-ID: <CAJ62sAqggjtqBjmhVHbm_o8eW8QDoanTL+5HC9rphHMLx=mY+g@mail.gmail.com>

Hi,

This is my first time using ParaView and I am trying to get an animation of
a trajectory of points. I have the data stored in separate csv files (one
file for each time step). When I upload the data into ParaView, it is all
grouped together and I can do it all at once. I am able to use the filter
Table to Points to see the outcome of all the points together. What i am
looking to do, however, is to animate a trajectory of the points over time.

Do you know how I should approach doing this? I assumed that i would be
able to click "play" and it would work once I uploaded the data, however,
this does not seem to be doing anything.

Thank you very much in advance!

This is what I have so far:

[image: Inline image 1]

- Janessa
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160628/3df7454a/attachment.html>

From paul.melis at surfsara.nl  Wed Jun 29 03:45:16 2016
From: paul.melis at surfsara.nl (Paul Melis)
Date: Wed, 29 Jun 2016 09:45:16 +0200
Subject: [Paraview] [EXTERNAL] A Potential Bug About Glyph (Paraview
 5.1.0)
In-Reply-To: <04b833b541ed43a7883d9eb3b50dc371@ES01AMSNLNT.srn.sandia.gov>
References: <9dc162fc-3ef3-9eae-1367-54e27ce841b9@uwaterloo.ca>
 <31c64ebc-7e85-7a99-e39d-d7e3d3846363@uwaterloo.ca>
 <04b833b541ed43a7883d9eb3b50dc371@ES01AMSNLNT.srn.sandia.gov>
Message-ID: <ab95ff53-739e-d5fc-04e4-028ffcbcf470@surfsara.nl>

I got bitten by the default masking settings a couple of times as well. 
Maybe change the default to not do masking when the number of input 
points is low, like 10000?

Paul


On 06/29/2016 12:23 AM, Scott, W Alan wrote:
>
> Huangrui Mo,
>
> Try outputting a glyph every point.  On the Properties tab, under 
> Masking, Glyph Mode, change this to off.
>
> Alan
>
> *From:*ParaView [mailto:paraview-bounces at paraview.org] *On Behalf Of 
> *Huangrui Mo
> *Sent:* Tuesday, June 28, 2016 3:48 PM
> *To:* paraview at paraview.org
> *Subject:* [EXTERNAL] [Paraview] A Potential Bug About Glyph (Paraview 
> 5.1.0)
>
> Dear Paraview Developer,
>
> When using the Glyph function to rend point sets, it may skip some 
> points, as shown below
>
> This happens either in steady case or a unsteady case. In the latter, 
> Glyph works at first and then disappear afterward.
>
> The .vtp file for generating the above point set has been attached in 
> this email.
>
> Thank you very much for taking time to read this email.
>
> Sincerely,
>
> Huangrui Mo
>
>
>
> _______________________________________________
> 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/20160629/bd5d114e/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/jpeg
Size: 32528 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160629/bd5d114e/attachment.jpe>

From lukasz.paluszek at airbus.com  Wed Jun 29 03:48:02 2016
From: lukasz.paluszek at airbus.com (Paluszek, Lukasz)
Date: Wed, 29 Jun 2016 07:48:02 +0000
Subject: [Paraview] Opacity Issues
In-Reply-To: <26629_1467056071_57717FC7_26629_12705_1_CA+=e1ot_uAPQ=u=QsTTTy4V4P40SNwgZhiUYYWy9FRvcyK+i2A@mail.gmail.com>
References: <9385_1466781329_576D4E91_9385_11640_1_d6606d3c88134b9bb7ca3e3b5a83459f@DE0-03DAG13-P03.central.mail.corp>
 <13295_1466785464_576D5EB7_13295_19000_1_CA+=e1otaNJNUweQTEqOzSKU0jnDivxMBBcP6FMB-4KY64za6KA@mail.gmail.com>
 <622_1466788260_576D69A4_622_19423_1_7fd68ea2d27f4d6bb0a2ed8cb27e1b71@DE0-03DAG13-P03.central.mail.corp>
 <CA+=e1ov_PyX74TcDMJq2RFqhPGmBuCazwKwrJdTnxWOBpL1f7A@mail.gmail.com>
 <13489_1466796170_576D888A_13489_10295_1_CA+=e1osFVg1tZgXnCuCkkqLNigDTB093D_QPd42Pjcfh4=bo3A@mail.gmail.com>
 <18567_1467021978_5770FA9A_18567_834_1_d98830eff0424c24a5bccc0b3d88ca54@DE0-03DAG13-P03.central.mail.corp>
 <26629_1467056071_57717FC7_26629_12705_1_CA+=e1ot_uAPQ=u=QsTTTy4V4P40SNwgZhiUYYWy9FRvcyK+i2A@mail.gmail.com>
Message-ID: <22051_1467186484_57737D34_22051_18934_1_3c8c3a0d287f4a169da7b387caed67ea@DE0-03DAG13-P03.central.mail.corp>

Hi Dave,

I tested the patch by simply replacing the two modified files and the new peeling worked with parallel rendering. I noticed, however, that I cannot load any state files saved before the patch application (or even from previous versions), Paraview segfaulted each time. I did not investigate the matter any further but perhaps you could double check that there is no backward compatibility issue with older state files that do have opacity information. In addition the peeling, regardless whether it?s the old or new implementation, takes significantly more time with parallel rendering than in the serial mode. Although, it?s expectable, the overhead is suspiciously high, I tried on 8 processes and a geometry which, in serial mode can be made opaque dynamically with no visible delay, took 34 seconds to be rendered. Most of the overhead comes from parallel distribution for compositing.

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>

From: David Lonie [mailto:david.lonie at kitware.com]
Sent: 27 June 2016 21:34
To: Paluszek, Lukasz
Cc: paraview at paraview.org
Subject: Re: [Paraview] Opacity Issues

This patch fixes the remote-rendering issue in the new peeling implementation:

https://gitlab.kitware.com/vtk/vtk/merge_requests/1589

Cheers,
Dave

On Mon, Jun 27, 2016 at 6:06 AM, Paluszek, Lukasz <lukasz.paluszek at airbus.com<mailto:lukasz.paluszek at airbus.com>> wrote:
Switching to the old peeling implementation did the trick, no more issues and yes I am using remote rendering via pvserver.

[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<tel:%2B49%20%2890%29%20671%208231>
Fax.: +49 (90) 671 9122
Lukasz.Paluszek at airbus.com<mailto:Lukasz.Paluszek at airbus.com>

From: David Lonie [mailto:david.lonie at kitware.com<mailto:david.lonie at kitware.com>]
Sent: 24 June 2016 21:22
To: Paluszek, Lukasz
Cc: paraview at paraview.org<mailto:paraview at paraview.org>
Subject: Re: [Paraview] Opacity Issues

On Fri, Jun 24, 2016 at 2:15 PM, David Lonie <david.lonie at kitware.com<mailto:david.lonie at kitware.com>> wrote:
On Fri, Jun 24, 2016 at 1:10 PM, Paluszek, Lukasz <lukasz.paluszek at airbus.com<mailto:lukasz.paluszek at airbus.com>> wrote:
It doesn?t happen all the time, I suppose you need a fairly large surface dataset. I managed to reproduce the problem on a wavelet source (attached state file), try increasing the number of elements if you do not see any artifacts. I have bult Paraview from source on OpenSuse 13.1 but also cross-checked with the Linux binaries from Paraview.org and had same issues. There was no problem with the osmesa-llvm flavor though.

I couldn't reproduce this here on arch linux with a newer nVidia driver (367.27), so I'm suspicious that this is a driver bug that's affecting the new depth peeling implementation.

Since you're building from source, can you try editing VTK/Rendering/OpenGL2/vtkOpenGLRenderer.cxx, and change line 322

if (dualDepthPeelingSupported)

to

if (false)

in DeviceRenderTranslucentPolygonalGeometry, recompile using the OpenGL2 backend, and let me know if the issue goes away? I suspect it will since both the OpenGL1 backend and OpenGL2 mesa/llvm do not use the new code.

I'll put together a patch to force the older peeling implementation via an environment variable to make the work-around easier to apply.

Patch is here: https://gitlab.kitware.com/vtk/vtk/merge_requests/1589

By the way, are you running paraview with remote rendering via pvserver? I was just made aware of a similar issue with remote rendering and depth peeling.

Dave

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; Thomas Hundt; 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.








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; Thomas Hundt; 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/20160629/7676f2b6/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/20160629/7676f2b6/attachment.png>

From stephen.wornom at inria.fr  Wed Jun 29 03:49:22 2016
From: stephen.wornom at inria.fr (Stephen Wornom)
Date: Wed, 29 Jun 2016 09:49:22 +0200 (CEST)
Subject: [Paraview] PV 4.1 how to extract a surface
In-Reply-To: <2136303395.40251158.1467186514453.JavaMail.zimbra@inria.fr>
Message-ID: <1930652711.40251792.1467186562031.JavaMail.zimbra@inria.fr>

Thanks Samuel, 
The clip function does what I want. 
The steps that I used are: 
1-select extract surface 
2-select conductivity 
3-clip (to remove the x-right face) 
4-clip (to remove the x-left face) 
5-clip (to remove the y-top face) 
6-clip (to remove the y-bottom face) 
7-slice (to get the 2D circle) 

Stephen 
----- Original Message -----


From: "Samuel Key" <samuelkey at bresnan.net> 
To: paraview at paraview.org 
Sent: Monday, June 27, 2016 3:47:07 PM 
Subject: Re: [Paraview] PV 4.1 how to extract a surface 



Stephen, 

Does not ParaView's Extract Surface filter give what you are looking to obtain? 

The result of the Extract Surface filter can also be trimmed visa the Clip filter. 

Sam 

On 6/27/2016 2:14 AM, Stephen Wornom wrote: 

<blockquote>

The mesh is 3D unstructured about a 3D cylinder. I would like to extract the surface of the cylinder. 

I have experience extracting surfaces with another code where the surfaces are defined by a variable (-3= cylinder surface). 
I do it like this: 
1-select extract surface 
2-select conductivity 
3-select threshold (choose -3 which corresponds to the cylinder surface). 

but I am using a code where the cylinder surface is NOT a predefined variable. 
How do I do I extract the surface? 
Hope my question is clear, 
Stephen 




_______________________________________________
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 

</blockquote>


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160629/94a59c18/attachment-0001.html>

From e.devilliers at engys.com  Wed Jun 29 03:49:46 2016
From: e.devilliers at engys.com (Eugene de Villiers)
Date: Wed, 29 Jun 2016 07:49:46 +0000
Subject: [Paraview] Minor bug in OPENFOAM import filter
In-Reply-To: <CA+=e1ouM=L1iv2u74eb4keSn-w+S_U9WpXjS28+eQA+8FNCJNg@mail.gmail.com>
References: <CA+=e1ouj8q447Q0uKPM6WtBPGphMM+Fc=R7hqSzDB6RNE1_A8w@mail.gmail.com>
 <AM4PR08MB1188DE8BD6DCE85F6005673D8B2C0@AM4PR08MB1188.eurprd08.prod.outlook.com>
 <CA+=e1otGNN2HFHh_nBLvrgq3cH3+hvJcHUZz5F0uQ6WNWKiQXg@mail.gmail.com>
 <20160625.201110.156085895.oshima@eng.niigata-u.ac.jp>
 <AM4PR08MB1188D0A13FFA958B1BA8F73E8B2F0@AM4PR08MB1188.eurprd08.prod.outlook.com>
 <CA+=e1oudenUnZCc4Ni8WZQuLxFUk+FZVVk3wgD8ZqD+5Dtn5pg@mail.gmail.com>
 <CA+=e1ouM=L1iv2u74eb4keSn-w+S_U9WpXjS28+eQA+8FNCJNg@mail.gmail.com>
Message-ID: <AM4PR08MB1188FE8B2D6ABF2943DAC1AA8B230@AM4PR08MB1188.eurprd08.prod.outlook.com>

David,

That?s perfect.

Eugene

From: David Lonie [mailto:david.lonie at kitware.com]
Sent: 28 June 2016 21:40
To: Eugene de Villiers <e.devilliers at engys.com>
Cc: Takuya OSHIMA <oshima at eng.niigata-u.ac.jp>; paraview at paraview.org
Subject: Re: [Paraview] Minor bug in OPENFOAM import filter

On Tue, Jun 28, 2016 at 3:06 PM, David Lonie <david.lonie at kitware.com<mailto:david.lonie at kitware.com>> wrote:
On Sat, Jun 25, 2016 at 1:02 PM, Eugene de Villiers <e.devilliers at engys.com<mailto:e.devilliers at engys.com>> wrote:
Hi Takuya, David,

That would be perfect. What kind of timeline are we looking at to see this in a release version?

It's difficult to say for sure. It might be out in the next patch release, but it might have to wait for the next major/minor release. The openFOAM reader is a complicated bit of code, I'm still investigating the best way to go about implementing this. I'll update this thread once I know more.

Good news -- I found an easy fix. Instead of failing outright when

(scalar (scalar scalar))

is found because the internal data structures can't handle nested lists following scalar data, I patched the reader to simply read the nested list, discard it, print a warning, and continue reading the file.

You'll still see a warning pop up in paraview, but the file should still read successfully as long as the unsupported list does not appear in a field used for visualization.

The patch is here: https://gitlab.kitware.com/vtk/vtk/merge_requests/1598

If this is agreeable to everyone, we'll get it merged and incorporated into a future release.

Dave
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160629/6370f8f5/attachment.html>

From christophe.bourcier.pv at gmail.com  Wed Jun 29 04:58:16 2016
From: christophe.bourcier.pv at gmail.com (Christophe Bourcier)
Date: Wed, 29 Jun 2016 10:58:16 +0200
Subject: [Paraview] "X Error: BadMatch" when loading state file with OpenGL2
 rendering on Fedora 18
Message-ID: <CAKtnqfkY0YdddPhrDWOphR21tWwFRhzNVyDtLfEnZQfS6n1s5Q@mail.gmail.com>

Hi,

I have an issue when loading state files on Fedora 18 with Paraview
compiled with the new OpenGL2 rendering backend, while there is no
error with the legacy OpenGL backend. Steps to reproduce the issue:

- Create a cylinder
- File/Save state: cylinder.pvsm
- File/Load state: load cylinder.pvsm

=> Paraview freezes. In the terminal, there is the error:

X Error: BadMatch (invalid parameter attributes) 8
  Major opcode: 1 (X_CreateWindow)
  Resource id:  0x3000104

This error is not reproduced in Fedora 20.

When loading more complex state file, there are more errors:


X Error: BadWindow (invalid Window parameter) 3
  Major opcode: 3 (X_GetWindowAttributes)
  Resource id:  0x3000111
X Error: GLXBadDrawable 169
  Extension:    152 (Uknown extension)
  Minor opcode: 5 (Unknown request)
  Resource id:  0x3000111
X Error: GLXBadDrawable 169
  Extension:    152 (Uknown extension)
  Minor opcode: 5 (Unknown request)
  Resource id:  0x3000111
X Error: GLXBadDrawable 169
  Extension:    152 (Uknown extension)
  Minor opcode: 5 (Unknown request)
  Resource id:  0x3000111
ERROR: In /export/home/bourcier/salome/prerequisites-src/ParaView-master-post-v5.1.0-RC1/VTK/Rendering/OpenGL2/vtkShaderProgram.cxx,
line 408
vtkShaderProgram (0x4aea610): Shader object was not initialized,
cannot attach it.

Does anyone know where it can come from?

Christophe

From lukasz.paluszek at airbus.com  Wed Jun 29 05:59:42 2016
From: lukasz.paluszek at airbus.com (Paluszek, Lukasz)
Date: Wed, 29 Jun 2016 09:59:42 +0000
Subject: [Paraview] Clip Filter box colour
Message-ID: <5435_1467194388_57739C14_5435_19773_1_1d70ed91c6814496a9d95d239da4886e@DE0-03DAG13-P03.central.mail.corp>

Is there a way to change the colour of the box selection in the clip filter? If someone is working with a white background then clipping by a box is difficult as you can't see the box bounds. It's not a showstopper, but perhaps could be integrated into the colour palette.

[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; Thomas Hundt; 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/20160629/5995368e/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/20160629/5995368e/attachment.png>

From lukasz.paluszek at airbus.com  Wed Jun 29 07:34:25 2016
From: lukasz.paluszek at airbus.com (Paluszek, Lukasz)
Date: Wed, 29 Jun 2016 11:34:25 +0000
Subject: [Paraview] Box-clipping of 2D slices
Message-ID: <28132_1467200071_5773B247_28132_2782_4_4822c085881a490dbb8df6c3035ca5ba@DE0-03DAG13-P03.central.mail.corp>

It seems that it is not possible to clip or extract cells from a 2D slice by means of a box selector. This approach works with the sphere or cylinder clipping but the box selection fails to extracted anything. Most likely because of the third dimension of the box is missing. To reproduce, create a plane source with 10 x10 cells and the select theclip filter, then set clip type to box, scale the box down and hit apply. Do the same with a sphere clip type.

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; Thomas Hundt; 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/20160629/be35e52b/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/20160629/be35e52b/attachment.png>

From david.lonie at kitware.com  Wed Jun 29 08:55:42 2016
From: david.lonie at kitware.com (David Lonie)
Date: Wed, 29 Jun 2016 08:55:42 -0400
Subject: [Paraview] Opacity Issues
In-Reply-To: <22051_1467186484_57737D34_22051_18934_1_3c8c3a0d287f4a169da7b387caed67ea@DE0-03DAG13-P03.central.mail.corp>
References: <9385_1466781329_576D4E91_9385_11640_1_d6606d3c88134b9bb7ca3e3b5a83459f@DE0-03DAG13-P03.central.mail.corp>
 <13295_1466785464_576D5EB7_13295_19000_1_CA+=e1otaNJNUweQTEqOzSKU0jnDivxMBBcP6FMB-4KY64za6KA@mail.gmail.com>
 <622_1466788260_576D69A4_622_19423_1_7fd68ea2d27f4d6bb0a2ed8cb27e1b71@DE0-03DAG13-P03.central.mail.corp>
 <CA+=e1ov_PyX74TcDMJq2RFqhPGmBuCazwKwrJdTnxWOBpL1f7A@mail.gmail.com>
 <13489_1466796170_576D888A_13489_10295_1_CA+=e1osFVg1tZgXnCuCkkqLNigDTB093D_QPd42Pjcfh4=bo3A@mail.gmail.com>
 <18567_1467021978_5770FA9A_18567_834_1_d98830eff0424c24a5bccc0b3d88ca54@DE0-03DAG13-P03.central.mail.corp>
 <26629_1467056071_57717FC7_26629_12705_1_CA+=e1ot_uAPQ=u=QsTTTy4V4P40SNwgZhiUYYWy9FRvcyK+i2A@mail.gmail.com>
 <22051_1467186484_57737D34_22051_18934_1_3c8c3a0d287f4a169da7b387caed67ea@DE0-03DAG13-P03.central.mail.corp>
Message-ID: <CA+=e1ouyXSAC=o8tS38BbXdwYtt2mdD1biSw+GmdjEuLv6p=9A@mail.gmail.com>

On Wed, Jun 29, 2016 at 3:48 AM, Paluszek, Lukasz <
lukasz.paluszek at airbus.com> wrote:

> I tested the patch by simply replacing the two modified files and the new
> peeling worked with parallel rendering.
>

Great!


> I noticed, however, that I cannot load any state files saved before the
> patch application (or even from previous versions), Paraview segfaulted
> each time. I did not investigate the matter any further but perhaps you
> could double check that there is no backward compatibility issue with older
> state files that do have opacity information.
>

The changes only affected shader code in the rendering engine, this
shouldn't make any difference in the ParaView state. Do they still segfault
in master without patching the files for the opacity fix?

In addition the peeling, regardless whether it?s the old or new
> implementation, takes significantly more time with parallel rendering than
> in the serial mode. Although, it?s expectable, the overhead is suspiciously
> high, I tried on 8 processes and a geometry which, in serial mode can be
> made opaque dynamically with no visible delay, took 34 seconds to be
> rendered. Most of the overhead comes from parallel distribution for
> compositing.
>

Was it 34 seconds for the initial frame, or for every frame? If the dataset
is large a longer first render would be expected as the data propagates.

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

From utkarsh.ayachit at kitware.com  Wed Jun 29 10:05:59 2016
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Wed, 29 Jun 2016 10:05:59 -0400
Subject: [Paraview] ParaView 5.1.1 Release Plans
Message-ID: <CADHSJjAGJmma5MENXXpNdkD44Hd-9sShbLhfCfADPq2o9kH70w@mail.gmail.com>

Folks,

Since there we a couple of crucial issues reported after the 5.1.0
release, we are planning on putting out a 5.1.1 patch release.

Currently, this will include the following fixes:

1. Address issues with depth peeling not working as expected in
client-server mode.
2. Address issues with ExodisIIReader not loading certain variables.
3. Address issue with nested lists in OpenFOAM
4. Address issue with "?" button not working in ParaView binaries.

Is there anything else that's can qualify as critical that should go
in this patch release? Note the 5.2.0 release in planned for SC16 i.e.
Oct/Nov.

If there's nothing else, I think we have fixes for almost all of
these, so we can put the release out early next week.

Utkarsh

From utkarsh.ayachit at kitware.com  Wed Jun 29 10:30:15 2016
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Wed, 29 Jun 2016 10:30:15 -0400
Subject: [Paraview] ParaView 5.1.1 Release Plans
In-Reply-To: <CADHSJjAGJmma5MENXXpNdkD44Hd-9sShbLhfCfADPq2o9kH70w@mail.gmail.com>
References: <CADHSJjAGJmma5MENXXpNdkD44Hd-9sShbLhfCfADPq2o9kH70w@mail.gmail.com>
Message-ID: <CADHSJjC-JkTTpFvpt=pNJ0w728MVQfXEaqrnfoU+ms=GHKRebg@mail.gmail.com>

(grrr, I really need to start proof reading my emails before sending
them. Sorry about all the glaring grammatical errors -- things often
seem to get lost in translation between my mind and fingers :) )

On Wed, Jun 29, 2016 at 10:05 AM, Utkarsh Ayachit
<utkarsh.ayachit at kitware.com> wrote:
> Folks,
>
> Since there we a couple of crucial issues reported after the 5.1.0
> release, we are planning on putting out a 5.1.1 patch release.
>
> Currently, this will include the following fixes:
>
> 1. Address issues with depth peeling not working as expected in
> client-server mode.
> 2. Address issues with ExodisIIReader not loading certain variables.
> 3. Address issue with nested lists in OpenFOAM
> 4. Address issue with "?" button not working in ParaView binaries.
>
> Is there anything else that's can qualify as critical that should go
> in this patch release? Note the 5.2.0 release in planned for SC16 i.e.
> Oct/Nov.
>
> If there's nothing else, I think we have fixes for almost all of
> these, so we can put the release out early next week.
>
> Utkarsh

From kmorel at sandia.gov  Wed Jun 29 11:22:47 2016
From: kmorel at sandia.gov (Moreland, Kenneth)
Date: Wed, 29 Jun 2016 15:22:47 +0000
Subject: [Paraview] Animating trajectories of points
Message-ID: <0f977f7fe46343829f8070c39d05b6df@ES08AMSNLNT.srn.sandia.gov>

Janessa,

ParaView should be able to read in a series of csv files as a time series. I just verified that when I have a sequence of csv files, ParaView treats it as a time series and plays through them.

For whatever reason, the image you originally attached to the email did not come through to me, so I cannot see exactly what you are doing. One problem could be that the names of the csv files have to follow a numbering convention so that ParaView knows to treat them as a sequence. Simply having them with sequential number names should do the trick (e.g. points1.csv, points2.csv, points3.csv, etc.). If ParaView understands the numbering convention, then the files should be grouped together in the file browser.

-Ken

From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Janessa Tran
Sent: Tuesday, June 28, 2016 10:45 PM
To: paraview at paraview.org
Subject: [EXTERNAL] [Paraview] Animating trajectories of points

Hi,

This is my first time using ParaView and I am trying to get an animation of a trajectory of points. I have the data stored in separate csv files (one file for each time step). When I upload the data into ParaView, it is all grouped together and I can do it all at once. I am able to use the filter Table to Points to see the outcome of all the points together. What i am looking to do, however, is to animate a trajectory of the points over time.

Do you know how I should approach doing this? I assumed that i would be able to click "play" and it would work once I uploaded the data, however, this does not seem to be doing anything.

Thank you very much in advance!

This is what I have so far:

[Inline image 1]

- Janessa
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160629/37fb9d69/attachment.html>

From wascott at sandia.gov  Wed Jun 29 12:44:40 2016
From: wascott at sandia.gov (Scott, W Alan)
Date: Wed, 29 Jun 2016 16:44:40 +0000
Subject: [Paraview] [EXTERNAL]  Box-clipping of 2D slices
In-Reply-To: <28132_1467200071_5773B247_28132_2782_4_4822c085881a490dbb8df6c3035ca5ba@DE0-03DAG13-P03.central.mail.corp>
References: <28132_1467200071_5773B247_28132_2782_4_4822c085881a490dbb8df6c3035ca5ba@DE0-03DAG13-P03.central.mail.corp>
Message-ID: <52c5936ff9b245919726ed5b89676ec9@ES01AMSNLNT.srn.sandia.gov>

Lukasz,
Could you please write up a bug report?  Or, if you can't log in, just let us know, and I will write it up.

Alan

From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Paluszek, Lukasz
Sent: Wednesday, June 29, 2016 5:34 AM
To: paraview at paraview.org
Subject: [EXTERNAL] [Paraview] Box-clipping of 2D slices

It seems that it is not possible to clip or extract cells from a 2D slice by means of a box selector. This approach works with the sphere or cylinder clipping but the box selection fails to extracted anything. Most likely because of the third dimension of the box is missing. To reproduce, create a plane source with 10 x10 cells and the select theclip filter, then set clip type to box, scale the box down and hit apply. Do the same with a sphere clip type.

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; Thomas Hundt; 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/20160629/a2f88e79/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/20160629/a2f88e79/attachment.png>

From kmorel at sandia.gov  Wed Jun 29 12:44:56 2016
From: kmorel at sandia.gov (Moreland, Kenneth)
Date: Wed, 29 Jun 2016 16:44:56 +0000
Subject: [Paraview] Animating trajectories of points
Message-ID: <77679e851c1f4bdcb28452686c2933e4@ES08AMSNLNT.srn.sandia.gov>

(Responding back to paraview list.)

That is odd behavior. Can you take a look at the csv files in a text editor? It looks like maybe all the data got appended to output1.csv, and the rest of the files are empty.

-Ken

From: Janessa Tran [mailto:janessasocialmedia at gmail.com]
Sent: Wednesday, June 29, 2016 10:04 AM
To: Moreland, Kenneth <kmorel at sandia.gov>
Subject: [EXTERNAL] Re: [Paraview] Animating trajectories of points

Hi Ken,

Thank you for your response. I managed to upload the sequence of files. They are named in the numeric fashion you mentioned (output1.csv, output2.csv, output3.csv, etc). When I add a filter "Table to Points" on the spreadsheet, I get the results in the image I attached to the email. What I am trying to do is to get an animation of the trajectory of the points, such that I can see the points being plotted over time.

Currently when I click play, everything goes blank. If you look at the second attached image, you will see the time is 13 of 150000 at the top of the screen. How can I fix this so I can get the animation of the points over time?

Thank you very much in advance!

On Wed, Jun 29, 2016 at 8:22 AM, Moreland, Kenneth <kmorel at sandia.gov<mailto:kmorel at sandia.gov>> wrote:
Janessa,

ParaView should be able to read in a series of csv files as a time series. I just verified that when I have a sequence of csv files, ParaView treats it as a time series and plays through them.

For whatever reason, the image you originally attached to the email did not come through to me, so I cannot see exactly what you are doing. One problem could be that the names of the csv files have to follow a numbering convention so that ParaView knows to treat them as a sequence. Simply having them with sequential number names should do the trick (e.g. points1.csv, points2.csv, points3.csv, etc.). If ParaView understands the numbering convention, then the files should be grouped together in the file browser.

-Ken

From: ParaView [mailto:paraview-bounces at paraview.org<mailto:paraview-bounces at paraview.org>] On Behalf Of Janessa Tran
Sent: Tuesday, June 28, 2016 10:45 PM
To: paraview at paraview.org<mailto:paraview at paraview.org>
Subject: [EXTERNAL] [Paraview] Animating trajectories of points

Hi,

This is my first time using ParaView and I am trying to get an animation of a trajectory of points. I have the data stored in separate csv files (one file for each time step). When I upload the data into ParaView, it is all grouped together and I can do it all at once. I am able to use the filter Table to Points to see the outcome of all the points together. What i am looking to do, however, is to animate a trajectory of the points over time.

Do you know how I should approach doing this? I assumed that i would be able to click "play" and it would work once I uploaded the data, however, this does not seem to be doing anything.

Thank you very much in advance!

This is what I have so far:

[Image removed by sender. Inline image 1]

- Janessa

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160629/b913babd/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 1886 bytes
Desc: image001.jpg
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160629/b913babd/attachment.jpg>

From wascott at sandia.gov  Wed Jun 29 12:50:48 2016
From: wascott at sandia.gov (Scott, W Alan)
Date: Wed, 29 Jun 2016 16:50:48 +0000
Subject: [Paraview] [EXTERNAL]  Clip Filter box colour
In-Reply-To: <5435_1467194388_57739C14_5435_19773_1_1d70ed91c6814496a9d95d239da4886e@DE0-03DAG13-P03.central.mail.corp>
References: <5435_1467194388_57739C14_5435_19773_1_1d70ed91c6814496a9d95d239da4886e@DE0-03DAG13-P03.central.mail.corp>
Message-ID: <49588e2abd1d42be9413d04ef35268ca@ES01AMSNLNT.srn.sandia.gov>

This was written up here: http://www.paraview.org/Bug/view.php?id=14843.  No, there is no way to change it.

Since it makes the white color palette unusable, I put it on the todo list.

Alan

From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Paluszek, Lukasz
Sent: Wednesday, June 29, 2016 4:00 AM
To: paraview at paraview.org
Subject: [EXTERNAL] [Paraview] Clip Filter box colour

Is there a way to change the colour of the box selection in the clip filter? If someone is working with a white background then clipping by a box is difficult as you can't see the box bounds. It's not a showstopper, but perhaps could be integrated into the colour palette.

[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; Thomas Hundt; 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/20160629/dbc329a7/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/20160629/dbc329a7/attachment.png>

From foss at grueninger.de  Wed Jun 29 14:24:17 2016
From: foss at grueninger.de (=?UTF-8?Q?Christoph_Gr=c3=bcninger?=)
Date: Wed, 29 Jun 2016 20:24:17 +0200
Subject: [Paraview] ParaView 5.1.1 Release Plans
In-Reply-To: <CADHSJjAGJmma5MENXXpNdkD44Hd-9sShbLhfCfADPq2o9kH70w@mail.gmail.com>
References: <CADHSJjAGJmma5MENXXpNdkD44Hd-9sShbLhfCfADPq2o9kH70w@mail.gmail.com>
Message-ID: <57741251.4010609@grueninger.de>

Hi Utkarsh,
I'd like to get the reduced CMake requirement in for 5.1.1. See pull
request #8 from GitHub, https://github.com/Kitware/ParaView/pull/8

Bye
Christoph

Am 29.06.2016 um 16:05 schrieb Utkarsh Ayachit:
> Folks,
> 
> Since there we a couple of crucial issues reported after the 5.1.0
> release, we are planning on putting out a 5.1.1 patch release.
> 
> Currently, this will include the following fixes:
> 
> 1. Address issues with depth peeling not working as expected in
> client-server mode.
> 2. Address issues with ExodisIIReader not loading certain variables.
> 3. Address issue with nested lists in OpenFOAM
> 4. Address issue with "?" button not working in ParaView binaries.
> 
> Is there anything else that's can qualify as critical that should go
> in this patch release? Note the 5.2.0 release in planned for SC16 i.e.
> Oct/Nov.
> 
> If there's nothing else, I think we have fixes for almost all of
> these, so we can put the release out early next week.
> 
> Utkarsh

From dwneumann at gmail.com  Wed Jun 29 18:12:28 2016
From: dwneumann at gmail.com (Dean Neumann)
Date: Wed, 29 Jun 2016 15:12:28 -0700
Subject: [Paraview] Preserve ordering when transposing Table?
Message-ID: <CAGgSO3gAtUdEPW4e4wWjPtpQQkPLjH1WdygnJ+Nfgdxzgw=nBw@mail.gmail.com>

When I view field data in a spreadsheet view the Row IDs are numerically
ordered correctly (i.e. 1-9, followed by 10-19, followed by 20-29, ...) etc.

When I  then apply a Transpose Table filter, the row numbers become the
columns but they are ordered alphabetically (i.e. 1, 10, 11, 12, ..., 2,
20, 21, 22, ..., 3, 30, 31...).  I cannot see a property that preserves
numeric ordering when transposing a table using the Transpose Table
filter.  Is this possible?

thanks...
Dean Neumann
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160629/18c7e57f/attachment.html>

From utkarsh.ayachit at kitware.com  Wed Jun 29 21:13:50 2016
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Wed, 29 Jun 2016 21:13:50 -0400
Subject: [Paraview] ParaView 5.1.1 Release Plans
In-Reply-To: <57741251.4010609@grueninger.de>
References: <CADHSJjAGJmma5MENXXpNdkD44Hd-9sShbLhfCfADPq2o9kH70w@mail.gmail.com>
 <57741251.4010609@grueninger.de>
Message-ID: <CADHSJjAyTROyn632=qsi+x4rYGvdhsy7XsU4uW3LiDWjaV2ePg@mail.gmail.com>

> I'd like to get the reduced CMake requirement in for 5.1.1. See pull
> request #8 from GitHub, https://github.com/Kitware/ParaView/pull/8

Roger. I'll include this one as well.

From wascott at sandia.gov  Wed Jun 29 21:24:05 2016
From: wascott at sandia.gov (Scott, W Alan)
Date: Thu, 30 Jun 2016 01:24:05 +0000
Subject: [Paraview] sum of a variable over all cells of one timestep
Message-ID: <66377404782e45978cb70770712c1cd6@ES01AMSNLNT.srn.sandia.gov>

I am trying to find the sum of a variable for all cells at one timestep.  It's ending up being surprisingly hard.  This is in parallel on dozens of servers, with hundreds of input files.  The Integrate Variable filter doesn't work, because it multiplies by cell volume.  At Ken's suggestion, I tried the Descriptive Statistics filter, and am totally confused what is there.  The first column is Process Id - does mean I get statistics for each processor, rather than for the whole dataset?  Then I see Cardinality, M2, M3, M4, which mean nothing to me.

Is there a way to turn off the cell volume multiply with the Integrate variables filter?  Or, is there a way to use the Descriptive Statistics filter?  Or, is there another, easier way to just sum up a variable?

Thanks,

Alan

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

From utkarsh.ayachit at kitware.com  Wed Jun 29 21:55:35 2016
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Wed, 29 Jun 2016 21:55:35 -0400
Subject: [Paraview] sum of a variable over all cells of one timestep
In-Reply-To: <66377404782e45978cb70770712c1cd6@ES01AMSNLNT.srn.sandia.gov>
References: <66377404782e45978cb70770712c1cd6@ES01AMSNLNT.srn.sandia.gov>
Message-ID: <CADHSJjBmNkiaaKAtiti8+QAbPYzuJ=40tbEp1nAORq5Nt8bNOw@mail.gmail.com>

> I am trying to find the sum of a variable for all cells at one timestep.

Try using the Python calculator. Make sure you set the "Array
Association" to "Cell Data" and then enter the expression sum(ARRAY).
Example for can.ex2, I can do "sum(EQPS)".

From wascott at sandia.gov  Wed Jun 29 22:11:08 2016
From: wascott at sandia.gov (Scott, W Alan)
Date: Thu, 30 Jun 2016 02:11:08 +0000
Subject: [Paraview] [EXTERNAL] Re: sum of a variable over all cells of
 one timestep
In-Reply-To: <CADHSJjBmNkiaaKAtiti8+QAbPYzuJ=40tbEp1nAORq5Nt8bNOw@mail.gmail.com>
References: <66377404782e45978cb70770712c1cd6@ES01AMSNLNT.srn.sandia.gov>
 <CADHSJjBmNkiaaKAtiti8+QAbPYzuJ=40tbEp1nAORq5Nt8bNOw@mail.gmail.com>
Message-ID: <7e8fac7c634b4a2e9d668498f128eaf0@ES01AMSNLNT.srn.sandia.gov>

Does that work multiple remote servers?

Thanks,

Alan

-----Original Message-----
From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] 
Sent: Wednesday, June 29, 2016 7:56 PM
To: Scott, W Alan <wascott at sandia.gov>
Cc: paraview at paraview.org
Subject: [EXTERNAL] Re: [Paraview] sum of a variable over all cells of one timestep

> I am trying to find the sum of a variable for all cells at one timestep.

Try using the Python calculator. Make sure you set the "Array Association" to "Cell Data" and then enter the expression sum(ARRAY).
Example for can.ex2, I can do "sum(EQPS)".

From Heather.Sheldon at csiro.au  Wed Jun 29 23:50:32 2016
From: Heather.Sheldon at csiro.au (Heather.Sheldon at csiro.au)
Date: Thu, 30 Jun 2016 03:50:32 +0000
Subject: [Paraview] Python script not working after updating to 5.1
Message-ID: <D39AB831.2A37F%Heather.Sheldon@csiro.au>

I have just updated from Paraview 4.3.1 to 5.1.0 and am having trouble with a Python script that no longer works correctly.

The attached script cycles through exodus files in a given directory, and for each file plots a surface plot of GlobalElementId overlain with a threshold plot of 2 other cell variables (one after the other), producing a screenshot of each image. This was working just fine with v4.3.1, but when I run it in 5.1.0 it fails to plot  GlobalElementId except for the first file, and fails to show the scalar color bar for any of the files. What has gone wrong?

Regards.
Heather
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160630/98fca237/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: aParaview_element_threshold_with_background.py
Type: text/x-python-script
Size: 5242 bytes
Desc: aParaview_element_threshold_with_background.py
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160630/98fca237/attachment.bin>

From utkarsh.ayachit at kitware.com  Thu Jun 30 07:32:21 2016
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Thu, 30 Jun 2016 07:32:21 -0400
Subject: [Paraview] Python script not working after updating to 5.1
In-Reply-To: <D39AB831.2A37F%Heather.Sheldon@csiro.au>
References: <D39AB831.2A37F%Heather.Sheldon@csiro.au>
Message-ID: <CADHSJjCf8Lpvh16RF9gaUiPBjuTg-fQs6Qt4t6sEByYS2Jn+-Q@mail.gmail.com>

Can you share the dataset to reproduce the issue? Feel free to send it
off the list if needed.

Thanks
Utkarsh

On Wed, Jun 29, 2016 at 11:50 PM,  <Heather.Sheldon at csiro.au> wrote:
> I have just updated from Paraview 4.3.1 to 5.1.0 and am having trouble with
> a Python script that no longer works correctly.
>
> The attached script cycles through exodus files in a given directory, and
> for each file plots a surface plot of GlobalElementId overlain with a
> threshold plot of 2 other cell variables (one after the other), producing a
> screenshot of each image. This was working just fine with v4.3.1, but when I
> run it in 5.1.0 it fails to plot  GlobalElementId except for the first file,
> and fails to show the scalar color bar for any of the files. What has gone
> wrong?
>
> Regards.
> Heather
>
> _______________________________________________
> 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  Thu Jun 30 09:13:56 2016
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Thu, 30 Jun 2016 09:13:56 -0400
Subject: [Paraview] [EXTERNAL] Re: sum of a variable over all cells of
	one timestep
In-Reply-To: <7e8fac7c634b4a2e9d668498f128eaf0@ES01AMSNLNT.srn.sandia.gov>
References: <66377404782e45978cb70770712c1cd6@ES01AMSNLNT.srn.sandia.gov>
 <CADHSJjBmNkiaaKAtiti8+QAbPYzuJ=40tbEp1nAORq5Nt8bNOw@mail.gmail.com>
 <7e8fac7c634b4a2e9d668498f128eaf0@ES01AMSNLNT.srn.sandia.gov>
Message-ID: <CADHSJjB_9dxojorBvDr9JE3K4SZGQpasXzmBiXwdiQSi+XMeWw@mail.gmail.com>

Yes. Just tested it with g1s1 on 8 servers.

On Wed, Jun 29, 2016 at 10:11 PM, Scott, W Alan <wascott at sandia.gov> wrote:
> Does that work multiple remote servers?
>
> Thanks,
>
> Alan
>
> -----Original Message-----
> From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com]
> Sent: Wednesday, June 29, 2016 7:56 PM
> To: Scott, W Alan <wascott at sandia.gov>
> Cc: paraview at paraview.org
> Subject: [EXTERNAL] Re: [Paraview] sum of a variable over all cells of one timestep
>
>> I am trying to find the sum of a variable for all cells at one timestep.
>
> Try using the Python calculator. Make sure you set the "Array Association" to "Cell Data" and then enter the expression sum(ARRAY).
> Example for can.ex2, I can do "sum(EQPS)".

From wascott at sandia.gov  Thu Jun 30 13:01:34 2016
From: wascott at sandia.gov (Scott, W Alan)
Date: Thu, 30 Jun 2016 17:01:34 +0000
Subject: [Paraview] [EXTERNAL] Re: sum of a variable over all cells of
 one timestep
In-Reply-To: <CADHSJjBmNkiaaKAtiti8+QAbPYzuJ=40tbEp1nAORq5Nt8bNOw@mail.gmail.com>
References: <66377404782e45978cb70770712c1cd6@ES01AMSNLNT.srn.sandia.gov>
 <CADHSJjBmNkiaaKAtiti8+QAbPYzuJ=40tbEp1nAORq5Nt8bNOw@mail.gmail.com>
Message-ID: <c3408d3b42c24e1c9f6f35ce503be6aa@ES01AMSNLNT.srn.sandia.gov>

That appears to work.  Thanks!!

Alan

-----Original Message-----
From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] 
Sent: Wednesday, June 29, 2016 7:56 PM
To: Scott, W Alan <wascott at sandia.gov>
Cc: paraview at paraview.org
Subject: [EXTERNAL] Re: [Paraview] sum of a variable over all cells of one timestep

> I am trying to find the sum of a variable for all cells at one timestep.

Try using the Python calculator. Make sure you set the "Array Association" to "Cell Data" and then enter the expression sum(ARRAY).
Example for can.ex2, I can do "sum(EQPS)".

From kmorel at sandia.gov  Thu Jun 30 15:10:50 2016
From: kmorel at sandia.gov (Moreland, Kenneth)
Date: Thu, 30 Jun 2016 19:10:50 +0000
Subject: [Paraview] Symbol WinMain missing when compiling with Visual Studio
Message-ID: <5269c2588321423ca7117304f81ab262@ES08AMSNLNT.srn.sandia.gov>

I'm trying to build ParaView for the first time in many years on a Windows machine with Visual Studio (using the ninja build program), and I am running into the following linker error. It appears that the link command for paraview.exe is failing because the symbol WinMain is not defined. (I am listing the verbose error below at the end if this email for reference.)

The ParaView GUI should be a "windows" program (vs. a "console" program), so defining WinMain sounds like the right thing. But I do not see where WinMain is defined in the code. Looking at the paraview_main.cxx source file that is generated, sure enough it defines main instead of WinMain. Am I missing something when configuring the build?

-Ken


[124/124 0.0/sec] Linking CXX executable bin\paraview.exe

FAILED: bin/paraview.exe

cmd.exe /C "cd . && "C:\Program Files (x86)\CMake\bin\cmake.exe" -E vs_link_exe --intdir=Applications\ParaView\CMakeFiles\paraview.dir --manifests -- C:\PROGRA~2\MICROS~1.0\VC\bin\amd64\link.exe /nologo Applications\ParaView\CMakeFiles\paraview.dir\paraview_main.cxx.obj Applications\ParaView\CMakeFiles\paraview.dir\Icon.rc.res Applications\ParaView\CMakeFiles\paraview.dir\pqparaviewInitializer.cxx.obj Applications\ParaView\CMakeFiles\paraview.dir\qrc_paraview_generated.cxx.obj Applications\ParaView\CMakeFiles\paraview.dir\qrc_paraview_configuration.cxx.obj Applications\ParaView\CMakeFiles\paraview.dir\ParaViewMainWindow.cxx.obj Applications\ParaView\CMakeFiles\paraview.dir\moc_ParaViewMainWindow.cxx.obj /out:bin\paraview.exe /implib:lib\paraview.lib /pdb:bin\paraview.pdb /version:0.0 /machine:x64 /debug /INCREMENTAL /subsystem:windows -LIBPATH:C:\Qt\Qt4.8.6\lib lib\vtkpqApplicationComponents-pv5.1.lib lib\vtkParaViewDocumentation.lib lib\vtkUtilitiesPythonInitializer-pv5.1.lib lib\vtkpqComponents-pv5.1.lib lib\vtkpqPython-pv5.1.lib lib\vtkpqCore-pv5.1.lib lib\vtkPVServerManagerApplication-pv5.1.lib lib\vtkpqWidgets-pv5.1.lib lib\QtTesting.lib C:\Qt\Qt4.8.6\lib\QtHelpd4.lib C:\Qt\Qt4.8.6\lib\QtCLucened4.lib C:\Qt\Qt4.8.6\lib\QtXmld4.lib C:\Qt\Qt4.8.6\lib\QtSqld4.lib lib\vtkPVServerManagerCore-pv5.1.lib lib\vtkPVServerImplementationCore-pv5.1.lib lib\protobuf.lib lib\vtkPVClientServerCoreCore-pv5.1.lib lib\vtkFiltersProgrammable-pv5.1.lib lib\vtkGUISupportQt-pv5.1.lib lib\vtkPVVTKExtensionsCore-pv5.1.lib lib\vtkPVCommon-pv5.1.lib lib\vtkClientServer-pv5.1.lib lib\vtkPythonInterpreter-pv5.1.lib lib\vtkFiltersParallel-pv5.1.lib lib\vtkRenderingOpenGL2-pv5.1.lib lib\vtkParallelCore-pv5.1.lib lib\vtkIOLegacy-pv5.1.lib lib\vtkIOXMLParser-pv5.1.lib lib\vtkInteractionStyle-pv5.1.lib lib\vtkFiltersExtraction-pv5.1.lib lib\vtkFiltersStatistics-pv5.1.lib lib\vtkImagingFourier-pv5.1.lib lib\vtkalglib-pv5.1.lib lib\vtkFiltersModeling-pv5.1.lib lib\vtkIOCore-pv5.1.lib lib\vtkRenderingCore-pv5.1.lib lib\vtkCommonColor-pv5.1.lib lib\vtkFiltersGeometry-pv5.1.lib lib\vtkFiltersSources-pv5.1.lib lib\vtkFiltersGeneral-pv5.1.lib lib\vtkFiltersCore-pv5.1.lib lib\vtkCommonComputationalGeometry-pv5.1.lib lib\vtkImagingCore-pv5.1.lib lib\vtkCommonExecutionModel-pv5.1.lib lib\vtkCommonDataModel-pv5.1.lib lib\vtkCommonMisc-pv5.1.lib lib\vtkCommonSystem-pv5.1.lib lib\vtkCommonTransforms-pv5.1.lib lib\vtkCommonMath-pv5.1.lib C:\Qt\Qt4.8.6\lib\QtGuid4.lib C:\Qt\Qt4.8.6\lib\QtNetworkd4.lib C:\Qt\Qt4.8.6\lib\QtCored4.lib lib\vtkWrappingPython27Core-pv5.1.lib lib\vtkCommonCore-pv5.1.lib lib\vtksys-pv5.1.lib ws2_32.lib Psapi.lib "C:\Program Files\tbb44_20160526oss\lib\intel64\vc12\tbb_debug.lib" C:\Users\kmorel\AppData\Local\Continuum\Anaconda2\libs\python27.lib kernel32.lib user32.lib gdi32.lib winspool.lib shell32.lib ole32.lib oleaut32.lib uuid.lib comdlg32.lib advapi32.lib && cd ."

MSVCRTD.lib(crtexew.obj) : error LNK2019: unresolved external symbol WinMain referenced in function __tmainCRTStartup





bin\paraview.exe : fatal error LNK1120: 1 unresolved externals





LINK Pass 1 failed. with 1120



   ****      Kenneth Moreland
    ***      Sandia National Laboratories
***********
*** *** ***  email: kmorel at sandia.gov<mailto:kmorel at sandia.gov>
**  ***  **  phone: (505) 844-8919
    ***      web:   http://kennethmoreland.com


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

From wascott at sandia.gov  Thu Jun 30 15:20:58 2016
From: wascott at sandia.gov (Scott, W Alan)
Date: Thu, 30 Jun 2016 19:20:58 +0000
Subject: [Paraview] [EXTERNAL] Symbol WinMain missing when compiling
 with Visual Studio
In-Reply-To: <5269c2588321423ca7117304f81ab262@ES08AMSNLNT.srn.sandia.gov>
References: <5269c2588321423ca7117304f81ab262@ES08AMSNLNT.srn.sandia.gov>
Message-ID: <a9c5e35f84b240eb8a9bf32a1012616a@ES01AMSNLNT.srn.sandia.gov>

Try building without Ninja?  If that also fails, I could try a build of my own.  Haven't done so in 6 months, but it seems to work.

By the way, what version of Visual Studio?

Alan

From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Moreland, Kenneth
Sent: Thursday, June 30, 2016 1:11 PM
To: paraview at paraview.org
Subject: [EXTERNAL] [Paraview] Symbol WinMain missing when compiling with Visual Studio

I'm trying to build ParaView for the first time in many years on a Windows machine with Visual Studio (using the ninja build program), and I am running into the following linker error. It appears that the link command for paraview.exe is failing because the symbol WinMain is not defined. (I am listing the verbose error below at the end if this email for reference.)

The ParaView GUI should be a "windows" program (vs. a "console" program), so defining WinMain sounds like the right thing. But I do not see where WinMain is defined in the code. Looking at the paraview_main.cxx source file that is generated, sure enough it defines main instead of WinMain. Am I missing something when configuring the build?

-Ken


[124/124 0.0/sec] Linking CXX executable bin\paraview.exe

FAILED: bin/paraview.exe

cmd.exe /C "cd . && "C:\Program Files (x86)\CMake\bin\cmake.exe" -E vs_link_exe --intdir=Applications\ParaView\CMakeFiles\paraview.dir --manifests -- C:\PROGRA~2\MICROS~1.0\VC\bin\amd64\link.exe /nologo Applications\ParaView\CMakeFiles\paraview.dir\paraview_main.cxx.obj Applications\ParaView\CMakeFiles\paraview.dir\Icon.rc.res Applications\ParaView\CMakeFiles\paraview.dir\pqparaviewInitializer.cxx.obj Applications\ParaView\CMakeFiles\paraview.dir\qrc_paraview_generated.cxx.obj Applications\ParaView\CMakeFiles\paraview.dir\qrc_paraview_configuration.cxx.obj Applications\ParaView\CMakeFiles\paraview.dir\ParaViewMainWindow.cxx.obj Applications\ParaView\CMakeFiles\paraview.dir\moc_ParaViewMainWindow.cxx.obj /out:bin\paraview.exe /implib:lib\paraview.lib /pdb:bin\paraview.pdb /version:0.0 /machine:x64 /debug /INCREMENTAL /subsystem:windows -LIBPATH:C:\Qt\Qt4.8.6\lib lib\vtkpqApplicationComponents-pv5.1.lib lib\vtkParaViewDocumentation.lib lib\vtkUtilitiesPythonInitializer-pv5.1.lib lib\vtkpqComponents-pv5.1.lib lib\vtkpqPython-pv5.1.lib lib\vtkpqCore-pv5.1.lib lib\vtkPVServerManagerApplication-pv5.1.lib lib\vtkpqWidgets-pv5.1.lib lib\QtTesting.lib C:\Qt\Qt4.8.6\lib\QtHelpd4.lib C:\Qt\Qt4.8.6\lib\QtCLucened4.lib C:\Qt\Qt4.8.6\lib\QtXmld4.lib C:\Qt\Qt4.8.6\lib\QtSqld4.lib lib\vtkPVServerManagerCore-pv5.1.lib lib\vtkPVServerImplementationCore-pv5.1.lib lib\protobuf.lib lib\vtkPVClientServerCoreCore-pv5.1.lib lib\vtkFiltersProgrammable-pv5.1.lib lib\vtkGUISupportQt-pv5.1.lib lib\vtkPVVTKExtensionsCore-pv5.1.lib lib\vtkPVCommon-pv5.1.lib lib\vtkClientServer-pv5.1.lib lib\vtkPythonInterpreter-pv5.1.lib lib\vtkFiltersParallel-pv5.1.lib lib\vtkRenderingOpenGL2-pv5.1.lib lib\vtkParallelCore-pv5.1.lib lib\vtkIOLegacy-pv5.1.lib lib\vtkIOXMLParser-pv5.1.lib lib\vtkInteractionStyle-pv5.1.lib lib\vtkFiltersExtraction-pv5.1.lib lib\vtkFiltersStatistics-pv5.1.lib lib\vtkImagingFourier-pv5.1.lib lib\vtkalglib-pv5.1.lib lib\vtkFiltersModeling-pv5.1.lib lib\vtkIOCore-pv5.1.lib lib\vtkRenderingCore-pv5.1.lib lib\vtkCommonColor-pv5.1.lib lib\vtkFiltersGeometry-pv5.1.lib lib\vtkFiltersSources-pv5.1.lib lib\vtkFiltersGeneral-pv5.1.lib lib\vtkFiltersCore-pv5.1.lib lib\vtkCommonComputationalGeometry-pv5.1.lib lib\vtkImagingCore-pv5.1.lib lib\vtkCommonExecutionModel-pv5.1.lib lib\vtkCommonDataModel-pv5.1.lib lib\vtkCommonMisc-pv5.1.lib lib\vtkCommonSystem-pv5.1.lib lib\vtkCommonTransforms-pv5.1.lib lib\vtkCommonMath-pv5.1.lib C:\Qt\Qt4.8.6\lib\QtGuid4.lib C:\Qt\Qt4.8.6\lib\QtNetworkd4.lib C:\Qt\Qt4.8.6\lib\QtCored4.lib lib\vtkWrappingPython27Core-pv5.1.lib lib\vtkCommonCore-pv5.1.lib lib\vtksys-pv5.1.lib ws2_32.lib Psapi.lib "C:\Program Files\tbb44_20160526oss\lib\intel64\vc12\tbb_debug.lib" C:\Users\kmorel\AppData\Local\Continuum\Anaconda2\libs\python27.lib kernel32.lib user32.lib gdi32.lib winspool.lib shell32.lib ole32.lib oleaut32.lib uuid.lib comdlg32.lib advapi32.lib && cd ."

MSVCRTD.lib(crtexew.obj) : error LNK2019: unresolved external symbol WinMain referenced in function __tmainCRTStartup





bin\paraview.exe : fatal error LNK1120: 1 unresolved externals





LINK Pass 1 failed. with 1120



   ****      Kenneth Moreland
    ***      Sandia National Laboratories
***********
*** *** ***  email: kmorel at sandia.gov<mailto:kmorel at sandia.gov>
**  ***  **  phone: (505) 844-8919
    ***      web:   http://kennethmoreland.com


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

From kmorel at sandia.gov  Thu Jun 30 15:22:06 2016
From: kmorel at sandia.gov (Moreland, Kenneth)
Date: Thu, 30 Jun 2016 19:22:06 +0000
Subject: [Paraview] Animating trajectories of points
Message-ID: <025d4329fc2448d8b74681436d830e13@ES08AMSNLNT.srn.sandia.gov>

Janessa,

Whether or not you need a separate file for each time step depends on how time is represented in the file format. For csv files, the only way to represent time is through a sequence of files, so you will always need those 150,000 (unless you create your own reader or filter that adds a time-based convention to the file).

Most of the simplest text-based file formats I can think of also use a separate file for each time step (such as legacy VTK, XML-based VTK, PVD). I?m pretty sure XDMF (http://www.xdmf.org/) can support your data over all time steps in a single file, but you would have to write it out using the HDF5 library. The Exodus II file format can also support your data (as long as the number of points remains constant), but it also requires using an associated library.

-Ken

From: Janessa Tran [mailto:janessasocialmedia at gmail.com]
Sent: Wednesday, June 29, 2016 7:24 PM
To: Moreland, Kenneth <kmorel at sandia.gov>
Subject: [EXTERNAL] Re: [Paraview] Animating trajectories of points

Thank you for your assistance, Ken. I was able to get it to run. An issue I see is that my animation requires 150,000 files. Is there a way to combine the data into a single file and run an animation over time?

Thank you,
Janessa

On Wed, Jun 29, 2016 at 9:44 AM, Moreland, Kenneth <kmorel at sandia.gov<mailto:kmorel at sandia.gov>> wrote:
(Responding back to paraview list.)

That is odd behavior. Can you take a look at the csv files in a text editor? It looks like maybe all the data got appended to output1.csv, and the rest of the files are empty.

-Ken

From: Janessa Tran [mailto:janessasocialmedia at gmail.com<mailto:janessasocialmedia at gmail.com>]
Sent: Wednesday, June 29, 2016 10:04 AM
To: Moreland, Kenneth <kmorel at sandia.gov<mailto:kmorel at sandia.gov>>
Subject: [EXTERNAL] Re: [Paraview] Animating trajectories of points

Hi Ken,

Thank you for your response. I managed to upload the sequence of files. They are named in the numeric fashion you mentioned (output1.csv, output2.csv, output3.csv, etc). When I add a filter "Table to Points" on the spreadsheet, I get the results in the image I attached to the email. What I am trying to do is to get an animation of the trajectory of the points, such that I can see the points being plotted over time.

Currently when I click play, everything goes blank. If you look at the second attached image, you will see the time is 13 of 150000 at the top of the screen. How can I fix this so I can get the animation of the points over time?

Thank you very much in advance!

On Wed, Jun 29, 2016 at 8:22 AM, Moreland, Kenneth <kmorel at sandia.gov<mailto:kmorel at sandia.gov>> wrote:
Janessa,

ParaView should be able to read in a series of csv files as a time series. I just verified that when I have a sequence of csv files, ParaView treats it as a time series and plays through them.

For whatever reason, the image you originally attached to the email did not come through to me, so I cannot see exactly what you are doing. One problem could be that the names of the csv files have to follow a numbering convention so that ParaView knows to treat them as a sequence. Simply having them with sequential number names should do the trick (e.g. points1.csv, points2.csv, points3.csv, etc.). If ParaView understands the numbering convention, then the files should be grouped together in the file browser.

-Ken

From: ParaView [mailto:paraview-bounces at paraview.org<mailto:paraview-bounces at paraview.org>] On Behalf Of Janessa Tran
Sent: Tuesday, June 28, 2016 10:45 PM
To: paraview at paraview.org<mailto:paraview at paraview.org>
Subject: [EXTERNAL] [Paraview] Animating trajectories of points

Hi,

This is my first time using ParaView and I am trying to get an animation of a trajectory of points. I have the data stored in separate csv files (one file for each time step). When I upload the data into ParaView, it is all grouped together and I can do it all at once. I am able to use the filter Table to Points to see the outcome of all the points together. What i am looking to do, however, is to animate a trajectory of the points over time.

Do you know how I should approach doing this? I assumed that i would be able to click "play" and it would work once I uploaded the data, however, this does not seem to be doing anything.

Thank you very much in advance!

This is what I have so far:

[Image removed by sender. Inline image 1]

- Janessa


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160630/5b782238/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 1886 bytes
Desc: image001.jpg
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160630/5b782238/attachment.jpg>

From utkarsh.ayachit at kitware.com  Thu Jun 30 15:27:19 2016
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Thu, 30 Jun 2016 15:27:19 -0400
Subject: [Paraview] Symbol WinMain missing when compiling with Visual
	Studio
In-Reply-To: <5269c2588321423ca7117304f81ab262@ES08AMSNLNT.srn.sandia.gov>
References: <5269c2588321423ca7117304f81ab262@ES08AMSNLNT.srn.sandia.gov>
Message-ID: <CADHSJjAkUX0nkzVgjeFAhv_GQjUirT_oEMf=M2Uk+SpE9yYYkg@mail.gmail.com>

Ben, do you have any insight? I remember this was something to do with
CMake and Qt.

FWIW, our dashboards to test with ninja so that's not the issue.

On Thu, Jun 30, 2016 at 3:10 PM, Moreland, Kenneth <kmorel at sandia.gov> wrote:
> I?m trying to build ParaView for the first time in many years on a Windows
> machine with Visual Studio (using the ninja build program), and I am running
> into the following linker error. It appears that the link command for
> paraview.exe is failing because the symbol WinMain is not defined. (I am
> listing the verbose error below at the end if this email for reference.)
>
>
>
> The ParaView GUI should be a ?windows? program (vs. a ?console? program), so
> defining WinMain sounds like the right thing. But I do not see where WinMain
> is defined in the code. Looking at the paraview_main.cxx source file that is
> generated, sure enough it defines main instead of WinMain. Am I missing
> something when configuring the build?
>
>
>
> -Ken
>
>
>
> [124/124 0.0/sec] Linking CXX executable bin\paraview.exe
>
> FAILED: bin/paraview.exe
>
> cmd.exe /C "cd . && "C:\Program Files (x86)\CMake\bin\cmake.exe" -E
> vs_link_exe --intdir=Applications\ParaView\CMakeFiles\paraview.dir
> --manifests -- C:\PROGRA~2\MICROS~1.0\VC\bin\amd64\link.exe /nologo
> Applications\ParaView\CMakeFiles\paraview.dir\paraview_main.cxx.obj
> Applications\ParaView\CMakeFiles\paraview.dir\Icon.rc.res
> Applications\ParaView\CMakeFiles\paraview.dir\pqparaviewInitializer.cxx.obj
> Applications\ParaView\CMakeFiles\paraview.dir\qrc_paraview_generated.cxx.obj
> Applications\ParaView\CMakeFiles\paraview.dir\qrc_paraview_configuration.cxx.obj
> Applications\ParaView\CMakeFiles\paraview.dir\ParaViewMainWindow.cxx.obj
> Applications\ParaView\CMakeFiles\paraview.dir\moc_ParaViewMainWindow.cxx.obj
> /out:bin\paraview.exe /implib:lib\paraview.lib /pdb:bin\paraview.pdb
> /version:0.0 /machine:x64 /debug /INCREMENTAL /subsystem:windows
> -LIBPATH:C:\Qt\Qt4.8.6\lib lib\vtkpqApplicationComponents-pv5.1.lib
> lib\vtkParaViewDocumentation.lib lib\vtkUtilitiesPythonInitializer-pv5.1.lib
> lib\vtkpqComponents-pv5.1.lib lib\vtkpqPython-pv5.1.lib
> lib\vtkpqCore-pv5.1.lib lib\vtkPVServerManagerApplication-pv5.1.lib
> lib\vtkpqWidgets-pv5.1.lib lib\QtTesting.lib C:\Qt\Qt4.8.6\lib\QtHelpd4.lib
> C:\Qt\Qt4.8.6\lib\QtCLucened4.lib C:\Qt\Qt4.8.6\lib\QtXmld4.lib
> C:\Qt\Qt4.8.6\lib\QtSqld4.lib lib\vtkPVServerManagerCore-pv5.1.lib
> lib\vtkPVServerImplementationCore-pv5.1.lib lib\protobuf.lib
> lib\vtkPVClientServerCoreCore-pv5.1.lib lib\vtkFiltersProgrammable-pv5.1.lib
> lib\vtkGUISupportQt-pv5.1.lib lib\vtkPVVTKExtensionsCore-pv5.1.lib
> lib\vtkPVCommon-pv5.1.lib lib\vtkClientServer-pv5.1.lib
> lib\vtkPythonInterpreter-pv5.1.lib lib\vtkFiltersParallel-pv5.1.lib
> lib\vtkRenderingOpenGL2-pv5.1.lib lib\vtkParallelCore-pv5.1.lib
> lib\vtkIOLegacy-pv5.1.lib lib\vtkIOXMLParser-pv5.1.lib
> lib\vtkInteractionStyle-pv5.1.lib lib\vtkFiltersExtraction-pv5.1.lib
> lib\vtkFiltersStatistics-pv5.1.lib lib\vtkImagingFourier-pv5.1.lib
> lib\vtkalglib-pv5.1.lib lib\vtkFiltersModeling-pv5.1.lib
> lib\vtkIOCore-pv5.1.lib lib\vtkRenderingCore-pv5.1.lib
> lib\vtkCommonColor-pv5.1.lib lib\vtkFiltersGeometry-pv5.1.lib
> lib\vtkFiltersSources-pv5.1.lib lib\vtkFiltersGeneral-pv5.1.lib
> lib\vtkFiltersCore-pv5.1.lib lib\vtkCommonComputationalGeometry-pv5.1.lib
> lib\vtkImagingCore-pv5.1.lib lib\vtkCommonExecutionModel-pv5.1.lib
> lib\vtkCommonDataModel-pv5.1.lib lib\vtkCommonMisc-pv5.1.lib
> lib\vtkCommonSystem-pv5.1.lib lib\vtkCommonTransforms-pv5.1.lib
> lib\vtkCommonMath-pv5.1.lib C:\Qt\Qt4.8.6\lib\QtGuid4.lib
> C:\Qt\Qt4.8.6\lib\QtNetworkd4.lib C:\Qt\Qt4.8.6\lib\QtCored4.lib
> lib\vtkWrappingPython27Core-pv5.1.lib lib\vtkCommonCore-pv5.1.lib
> lib\vtksys-pv5.1.lib ws2_32.lib Psapi.lib "C:\Program
> Files\tbb44_20160526oss\lib\intel64\vc12\tbb_debug.lib"
> C:\Users\kmorel\AppData\Local\Continuum\Anaconda2\libs\python27.lib
> kernel32.lib user32.lib gdi32.lib winspool.lib shell32.lib ole32.lib
> oleaut32.lib uuid.lib comdlg32.lib advapi32.lib && cd ."
>
> MSVCRTD.lib(crtexew.obj) : error LNK2019: unresolved external symbol WinMain
> referenced in function __tmainCRTStartup
>
>
>
>
>
> bin\paraview.exe : fatal error LNK1120: 1 unresolved externals
>
>
>
>
>
> LINK Pass 1 failed. with 1120
>
>
>
>
>
>
>
>    ****      Kenneth Moreland
>
>     ***      Sandia National Laboratories
> ***********
> *** *** ***  email: kmorel at sandia.gov
>
> **  ***  **  phone: (505) 844-8919
>     ***      web:   http://kennethmoreland.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 ziganshinshagit at hotmail.com  Thu Jun 30 23:05:18 2016
From: ziganshinshagit at hotmail.com (=?iso-8859-5?B?yNDT2OIgt9jT0N3o2N0=?=)
Date: Fri, 1 Jul 2016 03:05:18 +0000
Subject: [Paraview] Plugin Debug
Message-ID: <DUB123-W1105CDBEEFACC6FEBEDA5A8250@phx.gbl>

Hi!How to debug plugin in Paraview 5.1 in Windows, if Paraview force close after loading plugin?Best regards,Shagit Ziganshin. 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160701/b4c489d8/attachment.html>

From spl at tirebiter.org  Thu Jun 16 21:33:12 2016
From: spl at tirebiter.org (Steve Lamont)
Date: Fri, 17 Jun 2016 01:33:12 -0000
Subject: [Paraview] [EXTERNAL] Re: Rendering issue with cross-sections
 in 3D
In-Reply-To: <7e20cbe07254485db66e745aba2f2358@ES01AMSNLNT.srn.sandia.gov>
References: <CADPbR1iTP010aEp5MMWgfn_QV9eTh0Xsktw_vegskSf7d5uDig@mail.gmail.com>
 <57634E4F.8070307@tirebiter.org>
 <7e20cbe07254485db66e745aba2f2358@ES01AMSNLNT.srn.sandia.gov>
Message-ID: <5763534A.5090508@tirebiter.org>

> Can you provide us with a toy dataset (or non-toy, if necessary) that replicates the issue?  Also, really, really good directions (+Y, roll mouse wheel in 4 times)?

Sure.  Attached are a dataset and the ParaView saveset.

There's not much needed to replicate.  The view in the save set pretty 
much exemplify the problem.  The three planes intersect and they are not 
occluded in the expected manner.

Thanks for looking at this.

							spl

-------------- next part --------------
A non-text attachment was scrubbed...
Name: out4.nc
Type: application/x-netcdf
Size: 1432012 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160617/d09ac699/attachment.nc>
-------------- 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="4705"/>
        <Proxy value="4705"/>
        <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="4706" servers="16">
      <Layout number_of_elements="1">
        <Item direction="0" fraction="0.5" view="4705"/>
      </Layout>
    </Proxy>
    <Proxy group="lookup_tables" type="PVLookupTable" id="3961" servers="21">
      <Property name="AboveRangeColor" id="3961.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="3961.ActiveAnnotatedValues"/>
      <Property name="AllowDuplicateScalars" id="3961.AllowDuplicateScalars" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="3961.AllowDuplicateScalars.bool"/>
      </Property>
      <Property name="Annotations" id="3961.Annotations" number_of_elements="44">
        <Element index="0" value="-2"/>
        <Element index="1" value="data"/>
        <Element index="2" value="-1"/>
        <Element index="3" value="layer cake"/>
        <Element index="4" value="1"/>
        <Element index="5" value="Stratum 1"/>
        <Element index="6" value="2"/>
        <Element index="7" value="Stratum 2"/>
        <Element index="8" value="3"/>
        <Element index="9" value="Stratum 3"/>
        <Element index="10" value="4"/>
        <Element index="11" value="Stratum 4"/>
        <Element index="12" value="5"/>
        <Element index="13" value="Stratum 5"/>
        <Element index="14" value="6"/>
        <Element index="15" value="Stratum 6"/>
        <Element index="16" value="7"/>
        <Element index="17" value="Stratum 7"/>
        <Element index="18" value="8"/>
        <Element index="19" value="Stratum 8"/>
        <Element index="20" value="9"/>
        <Element index="21" value="Stratum 9"/>
        <Element index="22" value="10"/>
        <Element index="23" value="Stratum 10"/>
        <Element index="24" value="11"/>
        <Element index="25" value="Stratum 11"/>
        <Element index="26" value="12"/>
        <Element index="27" value="Stratum 12"/>
        <Element index="28" value="13"/>
        <Element index="29" value="Stratum 13"/>
        <Element index="30" value="14"/>
        <Element index="31" value="Stratum 14"/>
        <Element index="32" value="15"/>
        <Element index="33" value="Stratum 15"/>
        <Element index="34" value="16"/>
        <Element index="35" value="Stratum 16"/>
        <Element index="36" value="17"/>
        <Element index="37" value="Stratum 17"/>
        <Element index="38" value="18"/>
        <Element index="39" value="Stratum 18"/>
        <Element index="40" value="19"/>
        <Element index="41" value="Stratum 19"/>
        <Element index="42" value="20"/>
        <Element index="43" value="Stratum 20"/>
      </Property>
      <Property name="BelowRangeColor" id="3961.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="3961.Build"/>
      <Property name="ColorSpace" id="3961.ColorSpace" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="enum" id="3961.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="3961.Discretize" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="3961.Discretize.bool"/>
      </Property>
      <Property name="EnableOpacityMapping" id="3961.EnableOpacityMapping" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="3961.EnableOpacityMapping.bool"/>
      </Property>
      <Property name="HSVWrap" id="3961.HSVWrap" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="3961.HSVWrap.bool"/>
      </Property>
      <Property name="IndexedColors" id="3961.IndexedColors" number_of_elements="66">
        <Element index="0" value="0.666666666666667"/>
        <Element index="1" value="0.666666666666667"/>
        <Element index="2" value="0"/>
        <Element index="3" value="0.666666666666667"/>
        <Element index="4" value="0.666666666666667"/>
        <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="0"/>
        <Element index="11" value="1"/>
        <Element index="12" value="0"/>
        <Element index="13" value="0"/>
        <Element index="14" value="0.545098039215686"/>
        <Element index="15" value="0"/>
        <Element index="16" value="1"/>
        <Element index="17" value="1"/>
        <Element index="18" value="0.647058823529412"/>
        <Element index="19" value="0.164705882352941"/>
        <Element index="20" value="0.164705882352941"/>
        <Element index="21" value="0.545098039215686"/>
        <Element index="22" value="0.137254901960784"/>
        <Element index="23" value="0.137254901960784"/>
        <Element index="24" value="0.956862745098039"/>
        <Element index="25" value="0.643137254901961"/>
        <Element index="26" value="0.376470588235294"/>
        <Element index="27" value="0.745098039215686"/>
        <Element index="28" value="0.745098039215686"/>
        <Element index="29" value="0.745098039215686"/>
        <Element index="30" value="0.662745098039216"/>
        <Element index="31" value="0.662745098039216"/>
        <Element index="32" value="0.662745098039216"/>
        <Element index="33" value="0.827450980392157"/>
        <Element index="34" value="0.827450980392157"/>
        <Element index="35" value="0.827450980392157"/>
        <Element index="36" value="0"/>
        <Element index="37" value="1"/>
        <Element index="38" value="0"/>
        <Element index="39" value="0"/>
        <Element index="40" value="0.392156862745098"/>
        <Element index="41" value="0"/>
        <Element index="42" value="0.564705882352941"/>
        <Element index="43" value="0.933333333333333"/>
        <Element index="44" value="0.564705882352941"/>
        <Element index="45" value="1"/>
        <Element index="46" value="0.647058823529412"/>
        <Element index="47" value="0"/>
        <Element index="48" value="1"/>
        <Element index="49" value="0.752941176470588"/>
        <Element index="50" value="0.796078431372549"/>
        <Element index="51" value="0.627450980392157"/>
        <Element index="52" value="0.125490196078431"/>
        <Element index="53" value="0.941176470588235"/>
        <Element index="54" value="1"/>
        <Element index="55" value="0"/>
        <Element index="56" value="0"/>
        <Element index="57" value="0.87843137254902"/>
        <Element index="58" value="1"/>
        <Element index="59" value="1"/>
        <Element index="60" value="0.823529411764706"/>
        <Element index="61" value="0.705882352941177"/>
        <Element index="62" value="0.549019607843137"/>
        <Element index="63" value="1"/>
        <Element index="64" value="1"/>
        <Element index="65" value="0"/>
      </Property>
      <Property name="IndexedLookup" id="3961.IndexedLookup" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="3961.IndexedLookup.bool"/>
      </Property>
      <Property name="LockScalarRange" id="3961.LockScalarRange" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="3961.LockScalarRange.bool"/>
      </Property>
      <Property name="NanColor" id="3961.NanColor" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="1"/>
        <Element index="2" value="1"/>
      </Property>
      <Property name="NumberOfTableValues" id="3961.NumberOfTableValues" number_of_elements="1">
        <Element index="0" value="21"/>
        <Domain name="range" id="3961.NumberOfTableValues.range"/>
      </Property>
      <Property name="RGBPoints" id="3961.RGBPoints" number_of_elements="84">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Element index="3" value="0"/>
        <Element index="4" value="1"/>
        <Element index="5" value="0"/>
        <Element index="6" value="0"/>
        <Element index="7" value="1"/>
        <Element index="8" value="2"/>
        <Element index="9" value="0"/>
        <Element index="10" value="0"/>
        <Element index="11" value="0.545098"/>
        <Element index="12" value="3"/>
        <Element index="13" value="0"/>
        <Element index="14" value="1"/>
        <Element index="15" value="1"/>
        <Element index="16" value="4"/>
        <Element index="17" value="0.647059"/>
        <Element index="18" value="0.164706"/>
        <Element index="19" value="0.164706"/>
        <Element index="20" value="5"/>
        <Element index="21" value="0.545098"/>
        <Element index="22" value="0.137255"/>
        <Element index="23" value="0.137255"/>
        <Element index="24" value="6"/>
        <Element index="25" value="0.956863"/>
        <Element index="26" value="0.643137"/>
        <Element index="27" value="0.376471"/>
        <Element index="28" value="7"/>
        <Element index="29" value="0.745098"/>
        <Element index="30" value="0.745098"/>
        <Element index="31" value="0.745098"/>
        <Element index="32" value="8"/>
        <Element index="33" value="0.662745"/>
        <Element index="34" value="0.662745"/>
        <Element index="35" value="0.662745"/>
        <Element index="36" value="9"/>
        <Element index="37" value="0.827451"/>
        <Element index="38" value="0.827451"/>
        <Element index="39" value="0.827451"/>
        <Element index="40" value="10"/>
        <Element index="41" value="0"/>
        <Element index="42" value="1"/>
        <Element index="43" value="0"/>
        <Element index="44" value="11"/>
        <Element index="45" value="0"/>
        <Element index="46" value="0.392157"/>
        <Element index="47" value="0"/>
        <Element index="48" value="12"/>
        <Element index="49" value="0.564706"/>
        <Element index="50" value="0.933333"/>
        <Element index="51" value="0.564706"/>
        <Element index="52" value="13"/>
        <Element index="53" value="1"/>
        <Element index="54" value="0.647059"/>
        <Element index="55" value="0"/>
        <Element index="56" value="14"/>
        <Element index="57" value="1"/>
        <Element index="58" value="0.752941"/>
        <Element index="59" value="0.796078"/>
        <Element index="60" value="15"/>
        <Element index="61" value="0.627451"/>
        <Element index="62" value="0.12549"/>
        <Element index="63" value="0.941176"/>
        <Element index="64" value="16"/>
        <Element index="65" value="1"/>
        <Element index="66" value="0.592156862745098"/>
        <Element index="67" value="0.443137254901961"/>
        <Element index="68" value="17"/>
        <Element index="69" value="1"/>
        <Element index="70" value="0"/>
        <Element index="71" value="0"/>
        <Element index="72" value="18"/>
        <Element index="73" value="0.878431"/>
        <Element index="74" value="1"/>
        <Element index="75" value="1"/>
        <Element index="76" value="19"/>
        <Element index="77" value="0.823529"/>
        <Element index="78" value="0.705882"/>
        <Element index="79" value="0.54902"/>
        <Element index="80" value="20"/>
        <Element index="81" value="1"/>
        <Element index="82" value="1"/>
        <Element index="83" value="0"/>
      </Property>
      <Property name="RescaleOnVisibilityChange" id="3961.RescaleOnVisibilityChange" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="3961.RescaleOnVisibilityChange.bool"/>
      </Property>
      <Property name="ScalarOpacityFunction" id="3961.ScalarOpacityFunction" number_of_elements="1">
        <Proxy value="3960"/>
      </Property>
      <Property name="ScalarRangeInitialized" id="3961.ScalarRangeInitialized" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="3961.ScalarRangeInitialized.bool"/>
      </Property>
      <Property name="ShowIndexedColorActiveValues" id="3961.ShowIndexedColorActiveValues" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="3961.ShowIndexedColorActiveValues.bool"/>
      </Property>
      <Property name="UseAboveRangeColor" id="3961.UseAboveRangeColor" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="3961.UseAboveRangeColor.bool"/>
      </Property>
      <Property name="UseBelowRangeColor" id="3961.UseBelowRangeColor" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="3961.UseBelowRangeColor.bool"/>
      </Property>
      <Property name="UseLogScale" id="3961.UseLogScale" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="3961.UseLogScale.bool"/>
      </Property>
      <Property name="VectorComponent" id="3961.VectorComponent" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="range" id="3961.VectorComponent.range"/>
      </Property>
      <Property name="VectorMode" id="3961.VectorMode" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="enum" id="3961.VectorMode.enum">
          <Entry value="0" text="Magnitude"/>
          <Entry value="1" text="Component"/>
        </Domain>
      </Property>
    </Proxy>
    <Proxy group="piecewise_functions" type="PiecewiseFunction" id="3960" servers="21">
      <Property name="AllowDuplicateScalars" id="3960.AllowDuplicateScalars" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="3960.AllowDuplicateScalars.bool"/>
      </Property>
      <Property name="Points" id="3960.Points" number_of_elements="84">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0.5"/>
        <Element index="3" value="0"/>
        <Element index="4" value="1.05263157894737"/>
        <Element index="5" value="1"/>
        <Element index="6" value="0.5"/>
        <Element index="7" value="0"/>
        <Element index="8" value="2.10526315789474"/>
        <Element index="9" value="1"/>
        <Element index="10" value="0.5"/>
        <Element index="11" value="0"/>
        <Element index="12" value="3.15789473684211"/>
        <Element index="13" value="1"/>
        <Element index="14" value="0.5"/>
        <Element index="15" value="0"/>
        <Element index="16" value="4.21052631578947"/>
        <Element index="17" value="1"/>
        <Element index="18" value="0.5"/>
        <Element index="19" value="0"/>
        <Element index="20" value="5.26315789473684"/>
        <Element index="21" value="1"/>
        <Element index="22" value="0.5"/>
        <Element index="23" value="0"/>
        <Element index="24" value="6.31578947368421"/>
        <Element index="25" value="1"/>
        <Element index="26" value="0.5"/>
        <Element index="27" value="0"/>
        <Element index="28" value="7.36842105263158"/>
        <Element index="29" value="1"/>
        <Element index="30" value="0.5"/>
        <Element index="31" value="0"/>
        <Element index="32" value="8.42105263157895"/>
        <Element index="33" value="1"/>
        <Element index="34" value="0.5"/>
        <Element index="35" value="0"/>
        <Element index="36" value="9.47368421052632"/>
        <Element index="37" value="1"/>
        <Element index="38" value="0.5"/>
        <Element index="39" value="0"/>
        <Element index="40" value="10.5263157894737"/>
        <Element index="41" value="1"/>
        <Element index="42" value="0.5"/>
        <Element index="43" value="0"/>
        <Element index="44" value="10.5263157894737"/>
        <Element index="45" value="1"/>
        <Element index="46" value="0.5"/>
        <Element index="47" value="0"/>
        <Element index="48" value="11.5789473684211"/>
        <Element index="49" value="1"/>
        <Element index="50" value="0.5"/>
        <Element index="51" value="0"/>
        <Element index="52" value="12.6315789473684"/>
        <Element index="53" value="1"/>
        <Element index="54" value="0.5"/>
        <Element index="55" value="0"/>
        <Element index="56" value="13.6842105263158"/>
        <Element index="57" value="1"/>
        <Element index="58" value="0.5"/>
        <Element index="59" value="0"/>
        <Element index="60" value="14.7368421052632"/>
        <Element index="61" value="1"/>
        <Element index="62" value="0.5"/>
        <Element index="63" value="0"/>
        <Element index="64" value="15.7894736842105"/>
        <Element index="65" value="1"/>
        <Element index="66" value="0.5"/>
        <Element index="67" value="0"/>
        <Element index="68" value="16.8421052631579"/>
        <Element index="69" value="1"/>
        <Element index="70" value="0.5"/>
        <Element index="71" value="0"/>
        <Element index="72" value="17.8947368421053"/>
        <Element index="73" value="1"/>
        <Element index="74" value="0.5"/>
        <Element index="75" value="0"/>
        <Element index="76" value="18.9473684210526"/>
        <Element index="77" value="1"/>
        <Element index="78" value="0.5"/>
        <Element index="79" value="0"/>
        <Element index="80" value="20"/>
        <Element index="81" value="1"/>
        <Element index="82" value="0.5"/>
        <Element index="83" value="0"/>
      </Property>
      <Property name="ScalarRangeInitialized" id="3960.ScalarRangeInitialized" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="3960.ScalarRangeInitialized.bool"/>
      </Property>
    </Proxy>
    <Proxy group="annotations" type="GridAxes3DActor" id="3860" servers="21">
      <Property name="AxesToLabel" id="3860.AxesToLabel" number_of_elements="1">
        <Element index="0" value="63"/>
        <Domain name="range" id="3860.AxesToLabel.range"/>
      </Property>
      <Property name="DataPosition" id="3860.DataPosition" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="3860.DataPosition.range"/>
      </Property>
      <Property name="DataScale" id="3860.DataScale" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="1"/>
        <Element index="2" value="1"/>
        <Domain name="range" id="3860.DataScale.range"/>
      </Property>
      <Property name="FacesToRender" id="3860.FacesToRender" number_of_elements="1">
        <Element index="0" value="63"/>
        <Domain name="range" id="3860.FacesToRender.range"/>
      </Property>
      <Property name="LabelUniqueEdgesOnly" id="3860.LabelUniqueEdgesOnly" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="3860.LabelUniqueEdgesOnly.bool"/>
      </Property>
      <Property name="ModelBounds" id="3860.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="3860.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="3860.ShowEdges" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="3860.ShowEdges.bool"/>
      </Property>
      <Property name="ShowGrid" id="3860.ShowGrid" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="3860.ShowGrid.bool"/>
      </Property>
      <Property name="ShowTicks" id="3860.ShowTicks" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="3860.ShowTicks.bool"/>
      </Property>
      <Property name="UseModelTransform" id="3860.UseModelTransform" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="range" id="3860.UseModelTransform.range"/>
      </Property>
      <Property name="Visibility" id="3860.Visibility" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="3860.Visibility.bool"/>
      </Property>
      <Property name="XAxisLabels" id="3860.XAxisLabels">
        <Domain name="scalar_range" id="3860.XAxisLabels.scalar_range"/>
      </Property>
      <Property name="XAxisNotation" id="3860.XAxisNotation" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="enum" id="3860.XAxisNotation.enum">
          <Entry value="0" text="Mixed"/>
          <Entry value="1" text="Scientific"/>
          <Entry value="2" text="Fixed"/>
        </Domain>
      </Property>
      <Property name="XAxisPrecision" id="3860.XAxisPrecision" number_of_elements="1">
        <Element index="0" value="2"/>
        <Domain name="range" id="3860.XAxisPrecision.range"/>
      </Property>
      <Property name="XAxisUseCustomLabels" id="3860.XAxisUseCustomLabels" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="3860.XAxisUseCustomLabels.bool"/>
      </Property>
      <Property name="XTitle" id="3860.XTitle" number_of_elements="1">
        <Element index="0" value="X Axis"/>
      </Property>
      <Property name="YAxisLabels" id="3860.YAxisLabels">
        <Domain name="scalar_range" id="3860.YAxisLabels.scalar_range"/>
      </Property>
      <Property name="YAxisNotation" id="3860.YAxisNotation" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="enum" id="3860.YAxisNotation.enum">
          <Entry value="0" text="Mixed"/>
          <Entry value="1" text="Scientific"/>
          <Entry value="2" text="Fixed"/>
        </Domain>
      </Property>
      <Property name="YAxisPrecision" id="3860.YAxisPrecision" number_of_elements="1">
        <Element index="0" value="2"/>
        <Domain name="range" id="3860.YAxisPrecision.range"/>
      </Property>
      <Property name="YAxisUseCustomLabels" id="3860.YAxisUseCustomLabels" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="3860.YAxisUseCustomLabels.bool"/>
      </Property>
      <Property name="YTitle" id="3860.YTitle" number_of_elements="1">
        <Element index="0" value="Y Axis"/>
      </Property>
      <Property name="ZAxisLabels" id="3860.ZAxisLabels">
        <Domain name="scalar_range" id="3860.ZAxisLabels.scalar_range"/>
      </Property>
      <Property name="ZAxisNotation" id="3860.ZAxisNotation" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="enum" id="3860.ZAxisNotation.enum">
          <Entry value="0" text="Mixed"/>
          <Entry value="1" text="Scientific"/>
          <Entry value="2" text="Fixed"/>
        </Domain>
      </Property>
      <Property name="ZAxisPrecision" id="3860.ZAxisPrecision" number_of_elements="1">
        <Element index="0" value="2"/>
        <Domain name="range" id="3860.ZAxisPrecision.range"/>
      </Property>
      <Property name="ZAxisUseCustomLabels" id="3860.ZAxisUseCustomLabels" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="3860.ZAxisUseCustomLabels.bool"/>
      </Property>
      <Property name="ZTitle" id="3860.ZTitle" number_of_elements="1">
        <Element index="0" value="Z Axis"/>
      </Property>
      <Property name="CullBackface" id="3860.CullBackface" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="3860.CullBackface.bool"/>
      </Property>
      <Property name="CullFrontface" id="3860.CullFrontface" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="3860.CullFrontface.bool"/>
      </Property>
      <Property name="GridColor" id="3860.GridColor" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="1"/>
        <Element index="2" value="1"/>
        <Domain name="range" id="3860.GridColor.range"/>
      </Property>
      <Property name="XLabelBold" id="3860.XLabelBold" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="3860.XLabelBold.bool"/>
      </Property>
      <Property name="XLabelColor" id="3860.XLabelColor" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="1"/>
        <Element index="2" value="1"/>
        <Domain name="range" id="3860.XLabelColor.range"/>
      </Property>
      <Property name="XLabelFontFamily" id="3860.XLabelFontFamily" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="enum" id="3860.XLabelFontFamily.enum">
          <Entry value="0" text="Arial"/>
          <Entry value="1" text="Courier"/>
          <Entry value="2" text="Times"/>
        </Domain>
      </Property>
      <Property name="XLabelFontSize" id="3860.XLabelFontSize" number_of_elements="1">
        <Element index="0" value="12"/>
        <Domain name="range" id="3860.XLabelFontSize.range"/>
      </Property>
      <Property name="XLabelItalic" id="3860.XLabelItalic" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="3860.XLabelItalic.bool"/>
      </Property>
      <Property name="XLabelOpacity" id="3860.XLabelOpacity" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="3860.XLabelOpacity.range"/>
      </Property>
      <Property name="XLabelShadow" id="3860.XLabelShadow" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="3860.XLabelShadow.bool"/>
      </Property>
      <Property name="XTitleBold" id="3860.XTitleBold" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="3860.XTitleBold.bool"/>
      </Property>
      <Property name="XTitleColor" id="3860.XTitleColor" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="1"/>
        <Element index="2" value="1"/>
        <Domain name="range" id="3860.XTitleColor.range"/>
      </Property>
      <Property name="XTitleFontFamily" id="3860.XTitleFontFamily" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="enum" id="3860.XTitleFontFamily.enum">
          <Entry value="0" text="Arial"/>
          <Entry value="1" text="Courier"/>
          <Entry value="2" text="Times"/>
        </Domain>
      </Property>
      <Property name="XTitleFontSize" id="3860.XTitleFontSize" number_of_elements="1">
        <Element index="0" value="12"/>
        <Domain name="range" id="3860.XTitleFontSize.range"/>
      </Property>
      <Property name="XTitleItalic" id="3860.XTitleItalic" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="3860.XTitleItalic.bool"/>
      </Property>
      <Property name="XTitleOpacity" id="3860.XTitleOpacity" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="3860.XTitleOpacity.range"/>
      </Property>
      <Property name="XTitleShadow" id="3860.XTitleShadow" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="3860.XTitleShadow.bool"/>
      </Property>
      <Property name="YLabelBold" id="3860.YLabelBold" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="3860.YLabelBold.bool"/>
      </Property>
      <Property name="YLabelColor" id="3860.YLabelColor" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="1"/>
        <Element index="2" value="1"/>
        <Domain name="range" id="3860.YLabelColor.range"/>
      </Property>
      <Property name="YLabelFontFamily" id="3860.YLabelFontFamily" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="enum" id="3860.YLabelFontFamily.enum">
          <Entry value="0" text="Arial"/>
          <Entry value="1" text="Courier"/>
          <Entry value="2" text="Times"/>
        </Domain>
      </Property>
      <Property name="YLabelFontSize" id="3860.YLabelFontSize" number_of_elements="1">
        <Element index="0" value="12"/>
        <Domain name="range" id="3860.YLabelFontSize.range"/>
      </Property>
      <Property name="YLabelItalic" id="3860.YLabelItalic" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="3860.YLabelItalic.bool"/>
      </Property>
      <Property name="YLabelOpacity" id="3860.YLabelOpacity" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="3860.YLabelOpacity.range"/>
      </Property>
      <Property name="YLabelShadow" id="3860.YLabelShadow" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="3860.YLabelShadow.bool"/>
      </Property>
      <Property name="YTitleBold" id="3860.YTitleBold" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="3860.YTitleBold.bool"/>
      </Property>
      <Property name="YTitleColor" id="3860.YTitleColor" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="1"/>
        <Element index="2" value="1"/>
        <Domain name="range" id="3860.YTitleColor.range"/>
      </Property>
      <Property name="YTitleFontFamily" id="3860.YTitleFontFamily" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="enum" id="3860.YTitleFontFamily.enum">
          <Entry value="0" text="Arial"/>
          <Entry value="1" text="Courier"/>
          <Entry value="2" text="Times"/>
        </Domain>
      </Property>
      <Property name="YTitleFontSize" id="3860.YTitleFontSize" number_of_elements="1">
        <Element index="0" value="12"/>
        <Domain name="range" id="3860.YTitleFontSize.range"/>
      </Property>
      <Property name="YTitleItalic" id="3860.YTitleItalic" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="3860.YTitleItalic.bool"/>
      </Property>
      <Property name="YTitleOpacity" id="3860.YTitleOpacity" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="3860.YTitleOpacity.range"/>
      </Property>
      <Property name="YTitleShadow" id="3860.YTitleShadow" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="3860.YTitleShadow.bool"/>
      </Property>
      <Property name="ZLabelBold" id="3860.ZLabelBold" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="3860.ZLabelBold.bool"/>
      </Property>
      <Property name="ZLabelColor" id="3860.ZLabelColor" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="1"/>
        <Element index="2" value="1"/>
        <Domain name="range" id="3860.ZLabelColor.range"/>
      </Property>
      <Property name="ZLabelFontFamily" id="3860.ZLabelFontFamily" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="enum" id="3860.ZLabelFontFamily.enum">
          <Entry value="0" text="Arial"/>
          <Entry value="1" text="Courier"/>
          <Entry value="2" text="Times"/>
        </Domain>
      </Property>
      <Property name="ZLabelFontSize" id="3860.ZLabelFontSize" number_of_elements="1">
        <Element index="0" value="12"/>
        <Domain name="range" id="3860.ZLabelFontSize.range"/>
      </Property>
      <Property name="ZLabelItalic" id="3860.ZLabelItalic" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="3860.ZLabelItalic.bool"/>
      </Property>
      <Property name="ZLabelOpacity" id="3860.ZLabelOpacity" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="3860.ZLabelOpacity.range"/>
      </Property>
      <Property name="ZLabelShadow" id="3860.ZLabelShadow" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="3860.ZLabelShadow.bool"/>
      </Property>
      <Property name="ZTitleBold" id="3860.ZTitleBold" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="3860.ZTitleBold.bool"/>
      </Property>
      <Property name="ZTitleColor" id="3860.ZTitleColor" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="1"/>
        <Element index="2" value="1"/>
        <Domain name="range" id="3860.ZTitleColor.range"/>
      </Property>
      <Property name="ZTitleFontFamily" id="3860.ZTitleFontFamily" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="enum" id="3860.ZTitleFontFamily.enum">
          <Entry value="0" text="Arial"/>
          <Entry value="1" text="Courier"/>
          <Entry value="2" text="Times"/>
        </Domain>
      </Property>
      <Property name="ZTitleFontSize" id="3860.ZTitleFontSize" number_of_elements="1">
        <Element index="0" value="12"/>
        <Domain name="range" id="3860.ZTitleFontSize.range"/>
      </Property>
      <Property name="ZTitleItalic" id="3860.ZTitleItalic" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="3860.ZTitleItalic.bool"/>
      </Property>
      <Property name="ZTitleOpacity" id="3860.ZTitleOpacity" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="3860.ZTitleOpacity.range"/>
      </Property>
      <Property name="ZTitleShadow" id="3860.ZTitleShadow" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="3860.ZTitleShadow.bool"/>
      </Property>
    </Proxy>
    <Proxy group="misc" type="RepresentationAnimationHelper" id="4774" servers="16">
      <Property name="Source" id="4774.Source" number_of_elements="1">
        <Proxy value="3783"/>
      </Property>
    </Proxy>
    <Proxy group="sources" type="ArrowSource" id="3883" servers="1">
      <Property name="Invert" id="3883.Invert" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="3883.Invert.bool"/>
      </Property>
      <Property name="ShaftRadius" id="3883.ShaftRadius" number_of_elements="1">
        <Element index="0" value="0.03"/>
        <Domain name="range" id="3883.ShaftRadius.range"/>
      </Property>
      <Property name="ShaftResolution" id="3883.ShaftResolution" number_of_elements="1">
        <Element index="0" value="6"/>
        <Domain name="range" id="3883.ShaftResolution.range"/>
      </Property>
      <Property name="TipLength" id="3883.TipLength" number_of_elements="1">
        <Element index="0" value="0.35"/>
        <Domain name="range" id="3883.TipLength.range"/>
      </Property>
      <Property name="TipRadius" id="3883.TipRadius" number_of_elements="1">
        <Element index="0" value="0.1"/>
        <Domain name="range" id="3883.TipRadius.range"/>
      </Property>
      <Property name="TipResolution" id="3883.TipResolution" number_of_elements="1">
        <Element index="0" value="6"/>
        <Domain name="range" id="3883.TipResolution.range"/>
      </Property>
    </Proxy>
    <Proxy group="sources" type="ConeSource" id="3894" servers="1">
      <Property name="Capping" id="3894.Capping" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="3894.Capping.bool"/>
      </Property>
      <Property name="Center" id="3894.Center" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="3894.Center.range"/>
      </Property>
      <Property name="Direction" id="3894.Direction" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="3894.Direction.range"/>
      </Property>
      <Property name="Height" id="3894.Height" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="3894.Height.range"/>
      </Property>
      <Property name="Radius" id="3894.Radius" number_of_elements="1">
        <Element index="0" value="0.5"/>
        <Domain name="range" id="3894.Radius.range"/>
      </Property>
      <Property name="Resolution" id="3894.Resolution" number_of_elements="1">
        <Element index="0" value="6"/>
        <Domain name="range" id="3894.Resolution.range"/>
      </Property>
    </Proxy>
    <Proxy group="sources" type="CubeSource" id="3905" servers="1">
      <Property name="Center" id="3905.Center" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="3905.Center.range"/>
      </Property>
      <Property name="XLength" id="3905.XLength" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="3905.XLength.range"/>
      </Property>
      <Property name="YLength" id="3905.YLength" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="3905.YLength.range"/>
      </Property>
      <Property name="ZLength" id="3905.ZLength" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="3905.ZLength.range"/>
      </Property>
    </Proxy>
    <Proxy group="sources" type="CylinderSource" id="3916" servers="1">
      <Property name="Capping" id="3916.Capping" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="3916.Capping.bool"/>
      </Property>
      <Property name="Center" id="3916.Center" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="3916.Center.range"/>
      </Property>
      <Property name="Height" id="3916.Height" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="3916.Height.range"/>
      </Property>
      <Property name="Radius" id="3916.Radius" number_of_elements="1">
        <Element index="0" value="0.5"/>
        <Domain name="range" id="3916.Radius.range"/>
      </Property>
      <Property name="Resolution" id="3916.Resolution" number_of_elements="1">
        <Element index="0" value="6"/>
        <Domain name="range" id="3916.Resolution.range"/>
      </Property>
    </Proxy>
    <Proxy group="sources" type="LineSource" id="3927" servers="1">
      <Property name="Point1" id="3927.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="3927.Point1.range"/>
      </Property>
      <Property name="Point2" id="3927.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="3927.Point2.range"/>
      </Property>
      <Property name="Resolution" id="3927.Resolution" number_of_elements="1">
        <Element index="0" value="6"/>
        <Domain name="range" id="3927.Resolution.range"/>
      </Property>
    </Proxy>
    <Proxy group="sources" type="SphereSource" id="3938" servers="1">
      <Property name="Center" id="3938.Center" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="3938.Center.range"/>
      </Property>
      <Property name="EndPhi" id="3938.EndPhi" number_of_elements="1">
        <Element index="0" value="180"/>
        <Domain name="range" id="3938.EndPhi.range"/>
      </Property>
      <Property name="EndTheta" id="3938.EndTheta" number_of_elements="1">
        <Element index="0" value="360"/>
        <Domain name="range" id="3938.EndTheta.range"/>
      </Property>
      <Property name="PhiResolution" id="3938.PhiResolution" number_of_elements="1">
        <Element index="0" value="8"/>
        <Domain name="range" id="3938.PhiResolution.range"/>
      </Property>
      <Property name="Radius" id="3938.Radius" number_of_elements="1">
        <Element index="0" value="0.5"/>
        <Domain name="range" id="3938.Radius.range"/>
      </Property>
      <Property name="StartPhi" id="3938.StartPhi" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="range" id="3938.StartPhi.range"/>
      </Property>
      <Property name="StartTheta" id="3938.StartTheta" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="range" id="3938.StartTheta.range"/>
      </Property>
      <Property name="ThetaResolution" id="3938.ThetaResolution" number_of_elements="1">
        <Element index="0" value="8"/>
        <Domain name="range" id="3938.ThetaResolution.range"/>
      </Property>
    </Proxy>
    <Proxy group="sources" type="GlyphSource2D" id="3949" servers="1">
      <Property name="Center" id="3949.Center" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="3949.Center.range"/>
      </Property>
      <Property name="Filled" id="3949.Filled" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="3949.Filled.bool"/>
      </Property>
      <Property name="GlyphType" id="3949.GlyphType" number_of_elements="1">
        <Element index="0" value="9"/>
        <Domain name="enum" id="3949.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="3962" servers="21">
      <Property name="AllowDuplicateScalars" id="3962.AllowDuplicateScalars" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="3962.AllowDuplicateScalars.bool"/>
      </Property>
      <Property name="Points" id="3962.Points" number_of_elements="88">
        <Element index="0" value="-2"/>
        <Element index="1" value="1"/>
        <Element index="2" value="0.5"/>
        <Element index="3" value="0"/>
        <Element index="4" value="-1"/>
        <Element index="5" value="1"/>
        <Element index="6" value="0.5"/>
        <Element index="7" value="0"/>
        <Element index="8" value="0"/>
        <Element index="9" value="0"/>
        <Element index="10" value="0.5"/>
        <Element index="11" value="0"/>
        <Element index="12" value="0.2"/>
        <Element index="13" value="1"/>
        <Element index="14" value="0.5"/>
        <Element index="15" value="0"/>
        <Element index="16" value="1.3"/>
        <Element index="17" value="1"/>
        <Element index="18" value="0.5"/>
        <Element index="19" value="0"/>
        <Element index="20" value="2.4"/>
        <Element index="21" value="1"/>
        <Element index="22" value="0.5"/>
        <Element index="23" value="0"/>
        <Element index="24" value="3.5"/>
        <Element index="25" value="1"/>
        <Element index="26" value="0.5"/>
        <Element index="27" value="0"/>
        <Element index="28" value="4.6"/>
        <Element index="29" value="1"/>
        <Element index="30" value="0.5"/>
        <Element index="31" value="0"/>
        <Element index="32" value="5.7"/>
        <Element index="33" value="1"/>
        <Element index="34" value="0.5"/>
        <Element index="35" value="0"/>
        <Element index="36" value="6.8"/>
        <Element index="37" value="1"/>
        <Element index="38" value="0.5"/>
        <Element index="39" value="0"/>
        <Element index="40" value="7.9"/>
        <Element index="41" value="1"/>
        <Element index="42" value="0.5"/>
        <Element index="43" value="0"/>
        <Element index="44" value="9"/>
        <Element index="45" value="1"/>
        <Element index="46" value="0.5"/>
        <Element index="47" value="0"/>
        <Element index="48" value="10.1"/>
        <Element index="49" value="1"/>
        <Element index="50" value="0.5"/>
        <Element index="51" value="0"/>
        <Element index="52" value="11.2"/>
        <Element index="53" value="1"/>
        <Element index="54" value="0.5"/>
        <Element index="55" value="0"/>
        <Element index="56" value="12.3"/>
        <Element index="57" value="1"/>
        <Element index="58" value="0.5"/>
        <Element index="59" value="0"/>
        <Element index="60" value="13.4"/>
        <Element index="61" value="1"/>
        <Element index="62" value="0.5"/>
        <Element index="63" value="0"/>
        <Element index="64" value="14.5"/>
        <Element index="65" value="1"/>
        <Element index="66" value="0.5"/>
        <Element index="67" value="0"/>
        <Element index="68" value="15.6"/>
        <Element index="69" value="1"/>
        <Element index="70" value="0.5"/>
        <Element index="71" value="0"/>
        <Element index="72" value="16.7"/>
        <Element index="73" value="1"/>
        <Element index="74" value="0.5"/>
        <Element index="75" value="0"/>
        <Element index="76" value="17.8"/>
        <Element index="77" value="1"/>
        <Element index="78" value="0.5"/>
        <Element index="79" value="0"/>
        <Element index="80" value="18.9"/>
        <Element index="81" value="1"/>
        <Element index="82" value="0.5"/>
        <Element index="83" value="0"/>
        <Element index="84" value="20"/>
        <Element index="85" value="1"/>
        <Element index="86" value="0.5"/>
        <Element index="87" value="0"/>
      </Property>
      <Property name="ScalarRangeInitialized" id="3962.ScalarRangeInitialized" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="3962.ScalarRangeInitialized.bool"/>
      </Property>
    </Proxy>
    <Proxy group="piecewise_functions" type="PiecewiseFunction" id="3963" servers="21">
      <Property name="AllowDuplicateScalars" id="3963.AllowDuplicateScalars" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="3963.AllowDuplicateScalars.bool"/>
      </Property>
      <Property name="Points" id="3963.Points" number_of_elements="88">
        <Element index="0" value="-2"/>
        <Element index="1" value="1"/>
        <Element index="2" value="0.5"/>
        <Element index="3" value="0"/>
        <Element index="4" value="-1"/>
        <Element index="5" value="1"/>
        <Element index="6" value="0.5"/>
        <Element index="7" value="0"/>
        <Element index="8" value="0"/>
        <Element index="9" value="0"/>
        <Element index="10" value="0.5"/>
        <Element index="11" value="0"/>
        <Element index="12" value="0.2"/>
        <Element index="13" value="1"/>
        <Element index="14" value="0.5"/>
        <Element index="15" value="0"/>
        <Element index="16" value="1.3"/>
        <Element index="17" value="1"/>
        <Element index="18" value="0.5"/>
        <Element index="19" value="0"/>
        <Element index="20" value="2.4"/>
        <Element index="21" value="1"/>
        <Element index="22" value="0.5"/>
        <Element index="23" value="0"/>
        <Element index="24" value="3.5"/>
        <Element index="25" value="1"/>
        <Element index="26" value="0.5"/>
        <Element index="27" value="0"/>
        <Element index="28" value="4.6"/>
        <Element index="29" value="1"/>
        <Element index="30" value="0.5"/>
        <Element index="31" value="0"/>
        <Element index="32" value="5.7"/>
        <Element index="33" value="1"/>
        <Element index="34" value="0.5"/>
        <Element index="35" value="0"/>
        <Element index="36" value="6.8"/>
        <Element index="37" value="1"/>
        <Element index="38" value="0.5"/>
        <Element index="39" value="0"/>
        <Element index="40" value="7.9"/>
        <Element index="41" value="1"/>
        <Element index="42" value="0.5"/>
        <Element index="43" value="0"/>
        <Element index="44" value="9"/>
        <Element index="45" value="1"/>
        <Element index="46" value="0.5"/>
        <Element index="47" value="0"/>
        <Element index="48" value="10.1"/>
        <Element index="49" value="1"/>
        <Element index="50" value="0.5"/>
        <Element index="51" value="0"/>
        <Element index="52" value="11.2"/>
        <Element index="53" value="1"/>
        <Element index="54" value="0.5"/>
        <Element index="55" value="0"/>
        <Element index="56" value="12.3"/>
        <Element index="57" value="1"/>
        <Element index="58" value="0.5"/>
        <Element index="59" value="0"/>
        <Element index="60" value="13.4"/>
        <Element index="61" value="1"/>
        <Element index="62" value="0.5"/>
        <Element index="63" value="0"/>
        <Element index="64" value="14.5"/>
        <Element index="65" value="1"/>
        <Element index="66" value="0.5"/>
        <Element index="67" value="0"/>
        <Element index="68" value="15.6"/>
        <Element index="69" value="1"/>
        <Element index="70" value="0.5"/>
        <Element index="71" value="0"/>
        <Element index="72" value="16.7"/>
        <Element index="73" value="1"/>
        <Element index="74" value="0.5"/>
        <Element index="75" value="0"/>
        <Element index="76" value="17.8"/>
        <Element index="77" value="1"/>
        <Element index="78" value="0.5"/>
        <Element index="79" value="0"/>
        <Element index="80" value="18.9"/>
        <Element index="81" value="1"/>
        <Element index="82" value="0.5"/>
        <Element index="83" value="0"/>
        <Element index="84" value="20"/>
        <Element index="85" value="1"/>
        <Element index="86" value="0.5"/>
        <Element index="87" value="0"/>
      </Property>
      <Property name="ScalarRangeInitialized" id="3963.ScalarRangeInitialized" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="3963.ScalarRangeInitialized.bool"/>
      </Property>
    </Proxy>
    <Proxy group="implicit_functions" type="Plane" id="3794" servers="1">
      <Property name="Normal" id="3794.Normal" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="3794.Normal.range"/>
      </Property>
      <Property name="Offset" id="3794.Offset" number_of_elements="1">
        <Element index="0" value="0"/>
      </Property>
      <Property name="Origin" id="3794.Origin" number_of_elements="3">
        <Element index="0" value="-84751.8295051263"/>
        <Element index="1" value="51063.9968332023"/>
        <Element index="2" value="-12750"/>
        <Domain name="range" id="3794.Origin.range"/>
      </Property>
    </Proxy>
    <Proxy group="implicit_functions" type="Box" id="3795" servers="1">
      <Property name="Bounds" id="3795.Bounds" 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="Position" id="3795.Position" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="3795.Position.range"/>
      </Property>
      <Property name="Rotation" id="3795.Rotation" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="3795.Rotation.range"/>
      </Property>
      <Property name="Scale" id="3795.Scale" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="1"/>
        <Element index="2" value="1"/>
        <Domain name="range" id="3795.Scale.range"/>
      </Property>
    </Proxy>
    <Proxy group="implicit_functions" type="Sphere" id="3796" servers="1">
      <Property name="Center" id="3796.Center" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="3796.Center.range"/>
      </Property>
      <Property name="Radius" id="3796.Radius" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="range" id="3796.Radius.range"/>
      </Property>
    </Proxy>
    <Proxy group="implicit_functions" type="Cylinder" id="3797" servers="1">
      <Property name="Axis" id="3797.Axis" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="1"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="3797.Axis.range"/>
      </Property>
      <Property name="Center" id="3797.Center" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="3797.Center.range"/>
      </Property>
      <Property name="Radius" id="3797.Radius" number_of_elements="1">
        <Element index="0" value="0.5"/>
        <Domain name="range" id="3797.Radius.range"/>
      </Property>
    </Proxy>
    <Proxy group="misc" type="RepresentationAnimationHelper" id="4775" servers="16">
      <Property name="Source" id="4775.Source" number_of_elements="1">
        <Proxy value="3798"/>
      </Property>
    </Proxy>
    <Proxy group="sources" type="ArrowSource" id="4058" servers="1">
      <Property name="Invert" id="4058.Invert" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4058.Invert.bool"/>
      </Property>
      <Property name="ShaftRadius" id="4058.ShaftRadius" number_of_elements="1">
        <Element index="0" value="0.03"/>
        <Domain name="range" id="4058.ShaftRadius.range"/>
      </Property>
      <Property name="ShaftResolution" id="4058.ShaftResolution" number_of_elements="1">
        <Element index="0" value="6"/>
        <Domain name="range" id="4058.ShaftResolution.range"/>
      </Property>
      <Property name="TipLength" id="4058.TipLength" number_of_elements="1">
        <Element index="0" value="0.35"/>
        <Domain name="range" id="4058.TipLength.range"/>
      </Property>
      <Property name="TipRadius" id="4058.TipRadius" number_of_elements="1">
        <Element index="0" value="0.1"/>
        <Domain name="range" id="4058.TipRadius.range"/>
      </Property>
      <Property name="TipResolution" id="4058.TipResolution" number_of_elements="1">
        <Element index="0" value="6"/>
        <Domain name="range" id="4058.TipResolution.range"/>
      </Property>
    </Proxy>
    <Proxy group="sources" type="ConeSource" id="4069" servers="1">
      <Property name="Capping" id="4069.Capping" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="4069.Capping.bool"/>
      </Property>
      <Property name="Center" id="4069.Center" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="4069.Center.range"/>
      </Property>
      <Property name="Direction" id="4069.Direction" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="4069.Direction.range"/>
      </Property>
      <Property name="Height" id="4069.Height" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="4069.Height.range"/>
      </Property>
      <Property name="Radius" id="4069.Radius" number_of_elements="1">
        <Element index="0" value="0.5"/>
        <Domain name="range" id="4069.Radius.range"/>
      </Property>
      <Property name="Resolution" id="4069.Resolution" number_of_elements="1">
        <Element index="0" value="6"/>
        <Domain name="range" id="4069.Resolution.range"/>
      </Property>
    </Proxy>
    <Proxy group="sources" type="CubeSource" id="4080" servers="1">
      <Property name="Center" id="4080.Center" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="4080.Center.range"/>
      </Property>
      <Property name="XLength" id="4080.XLength" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="4080.XLength.range"/>
      </Property>
      <Property name="YLength" id="4080.YLength" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="4080.YLength.range"/>
      </Property>
      <Property name="ZLength" id="4080.ZLength" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="4080.ZLength.range"/>
      </Property>
    </Proxy>
    <Proxy group="sources" type="CylinderSource" id="4091" servers="1">
      <Property name="Capping" id="4091.Capping" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="4091.Capping.bool"/>
      </Property>
      <Property name="Center" id="4091.Center" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="4091.Center.range"/>
      </Property>
      <Property name="Height" id="4091.Height" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="4091.Height.range"/>
      </Property>
      <Property name="Radius" id="4091.Radius" number_of_elements="1">
        <Element index="0" value="0.5"/>
        <Domain name="range" id="4091.Radius.range"/>
      </Property>
      <Property name="Resolution" id="4091.Resolution" number_of_elements="1">
        <Element index="0" value="6"/>
        <Domain name="range" id="4091.Resolution.range"/>
      </Property>
    </Proxy>
    <Proxy group="sources" type="LineSource" id="4102" servers="1">
      <Property name="Point1" id="4102.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="4102.Point1.range"/>
      </Property>
      <Property name="Point2" id="4102.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="4102.Point2.range"/>
      </Property>
      <Property name="Resolution" id="4102.Resolution" number_of_elements="1">
        <Element index="0" value="6"/>
        <Domain name="range" id="4102.Resolution.range"/>
      </Property>
    </Proxy>
    <Proxy group="sources" type="SphereSource" id="4113" servers="1">
      <Property name="Center" id="4113.Center" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="4113.Center.range"/>
      </Property>
      <Property name="EndPhi" id="4113.EndPhi" number_of_elements="1">
        <Element index="0" value="180"/>
        <Domain name="range" id="4113.EndPhi.range"/>
      </Property>
      <Property name="EndTheta" id="4113.EndTheta" number_of_elements="1">
        <Element index="0" value="360"/>
        <Domain name="range" id="4113.EndTheta.range"/>
      </Property>
      <Property name="PhiResolution" id="4113.PhiResolution" number_of_elements="1">
        <Element index="0" value="8"/>
        <Domain name="range" id="4113.PhiResolution.range"/>
      </Property>
      <Property name="Radius" id="4113.Radius" number_of_elements="1">
        <Element index="0" value="0.5"/>
        <Domain name="range" id="4113.Radius.range"/>
      </Property>
      <Property name="StartPhi" id="4113.StartPhi" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="range" id="4113.StartPhi.range"/>
      </Property>
      <Property name="StartTheta" id="4113.StartTheta" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="range" id="4113.StartTheta.range"/>
      </Property>
      <Property name="ThetaResolution" id="4113.ThetaResolution" number_of_elements="1">
        <Element index="0" value="8"/>
        <Domain name="range" id="4113.ThetaResolution.range"/>
      </Property>
    </Proxy>
    <Proxy group="sources" type="GlyphSource2D" id="4124" servers="1">
      <Property name="Center" id="4124.Center" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="4124.Center.range"/>
      </Property>
      <Property name="Filled" id="4124.Filled" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4124.Filled.bool"/>
      </Property>
      <Property name="GlyphType" id="4124.GlyphType" number_of_elements="1">
        <Element index="0" value="9"/>
        <Domain name="enum" id="4124.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="4135" servers="21">
      <Property name="AllowDuplicateScalars" id="4135.AllowDuplicateScalars" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="4135.AllowDuplicateScalars.bool"/>
      </Property>
      <Property name="Points" id="4135.Points" number_of_elements="88">
        <Element index="0" value="-2"/>
        <Element index="1" value="1"/>
        <Element index="2" value="0.5"/>
        <Element index="3" value="0"/>
        <Element index="4" value="-1"/>
        <Element index="5" value="1"/>
        <Element index="6" value="0.5"/>
        <Element index="7" value="0"/>
        <Element index="8" value="0"/>
        <Element index="9" value="0"/>
        <Element index="10" value="0.5"/>
        <Element index="11" value="0"/>
        <Element index="12" value="0.2"/>
        <Element index="13" value="1"/>
        <Element index="14" value="0.5"/>
        <Element index="15" value="0"/>
        <Element index="16" value="1.3"/>
        <Element index="17" value="1"/>
        <Element index="18" value="0.5"/>
        <Element index="19" value="0"/>
        <Element index="20" value="2.4"/>
        <Element index="21" value="1"/>
        <Element index="22" value="0.5"/>
        <Element index="23" value="0"/>
        <Element index="24" value="3.5"/>
        <Element index="25" value="1"/>
        <Element index="26" value="0.5"/>
        <Element index="27" value="0"/>
        <Element index="28" value="4.6"/>
        <Element index="29" value="1"/>
        <Element index="30" value="0.5"/>
        <Element index="31" value="0"/>
        <Element index="32" value="5.7"/>
        <Element index="33" value="1"/>
        <Element index="34" value="0.5"/>
        <Element index="35" value="0"/>
        <Element index="36" value="6.8"/>
        <Element index="37" value="1"/>
        <Element index="38" value="0.5"/>
        <Element index="39" value="0"/>
        <Element index="40" value="7.9"/>
        <Element index="41" value="1"/>
        <Element index="42" value="0.5"/>
        <Element index="43" value="0"/>
        <Element index="44" value="9"/>
        <Element index="45" value="1"/>
        <Element index="46" value="0.5"/>
        <Element index="47" value="0"/>
        <Element index="48" value="10.1"/>
        <Element index="49" value="1"/>
        <Element index="50" value="0.5"/>
        <Element index="51" value="0"/>
        <Element index="52" value="11.2"/>
        <Element index="53" value="1"/>
        <Element index="54" value="0.5"/>
        <Element index="55" value="0"/>
        <Element index="56" value="12.3"/>
        <Element index="57" value="1"/>
        <Element index="58" value="0.5"/>
        <Element index="59" value="0"/>
        <Element index="60" value="13.4"/>
        <Element index="61" value="1"/>
        <Element index="62" value="0.5"/>
        <Element index="63" value="0"/>
        <Element index="64" value="14.5"/>
        <Element index="65" value="1"/>
        <Element index="66" value="0.5"/>
        <Element index="67" value="0"/>
        <Element index="68" value="15.6"/>
        <Element index="69" value="1"/>
        <Element index="70" value="0.5"/>
        <Element index="71" value="0"/>
        <Element index="72" value="16.7"/>
        <Element index="73" value="1"/>
        <Element index="74" value="0.5"/>
        <Element index="75" value="0"/>
        <Element index="76" value="17.8"/>
        <Element index="77" value="1"/>
        <Element index="78" value="0.5"/>
        <Element index="79" value="0"/>
        <Element index="80" value="18.9"/>
        <Element index="81" value="1"/>
        <Element index="82" value="0.5"/>
        <Element index="83" value="0"/>
        <Element index="84" value="20"/>
        <Element index="85" value="1"/>
        <Element index="86" value="0.5"/>
        <Element index="87" value="0"/>
      </Property>
      <Property name="ScalarRangeInitialized" id="4135.ScalarRangeInitialized" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4135.ScalarRangeInitialized.bool"/>
      </Property>
    </Proxy>
    <Proxy group="piecewise_functions" type="PiecewiseFunction" id="4136" servers="21">
      <Property name="AllowDuplicateScalars" id="4136.AllowDuplicateScalars" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="4136.AllowDuplicateScalars.bool"/>
      </Property>
      <Property name="Points" id="4136.Points" number_of_elements="88">
        <Element index="0" value="-2"/>
        <Element index="1" value="1"/>
        <Element index="2" value="0.5"/>
        <Element index="3" value="0"/>
        <Element index="4" value="-1"/>
        <Element index="5" value="1"/>
        <Element index="6" value="0.5"/>
        <Element index="7" value="0"/>
        <Element index="8" value="0"/>
        <Element index="9" value="0"/>
        <Element index="10" value="0.5"/>
        <Element index="11" value="0"/>
        <Element index="12" value="0.2"/>
        <Element index="13" value="1"/>
        <Element index="14" value="0.5"/>
        <Element index="15" value="0"/>
        <Element index="16" value="1.3"/>
        <Element index="17" value="1"/>
        <Element index="18" value="0.5"/>
        <Element index="19" value="0"/>
        <Element index="20" value="2.4"/>
        <Element index="21" value="1"/>
        <Element index="22" value="0.5"/>
        <Element index="23" value="0"/>
        <Element index="24" value="3.5"/>
        <Element index="25" value="1"/>
        <Element index="26" value="0.5"/>
        <Element index="27" value="0"/>
        <Element index="28" value="4.6"/>
        <Element index="29" value="1"/>
        <Element index="30" value="0.5"/>
        <Element index="31" value="0"/>
        <Element index="32" value="5.7"/>
        <Element index="33" value="1"/>
        <Element index="34" value="0.5"/>
        <Element index="35" value="0"/>
        <Element index="36" value="6.8"/>
        <Element index="37" value="1"/>
        <Element index="38" value="0.5"/>
        <Element index="39" value="0"/>
        <Element index="40" value="7.9"/>
        <Element index="41" value="1"/>
        <Element index="42" value="0.5"/>
        <Element index="43" value="0"/>
        <Element index="44" value="9"/>
        <Element index="45" value="1"/>
        <Element index="46" value="0.5"/>
        <Element index="47" value="0"/>
        <Element index="48" value="10.1"/>
        <Element index="49" value="1"/>
        <Element index="50" value="0.5"/>
        <Element index="51" value="0"/>
        <Element index="52" value="11.2"/>
        <Element index="53" value="1"/>
        <Element index="54" value="0.5"/>
        <Element index="55" value="0"/>
        <Element index="56" value="12.3"/>
        <Element index="57" value="1"/>
        <Element index="58" value="0.5"/>
        <Element index="59" value="0"/>
        <Element index="60" value="13.4"/>
        <Element index="61" value="1"/>
        <Element index="62" value="0.5"/>
        <Element index="63" value="0"/>
        <Element index="64" value="14.5"/>
        <Element index="65" value="1"/>
        <Element index="66" value="0.5"/>
        <Element index="67" value="0"/>
        <Element index="68" value="15.6"/>
        <Element index="69" value="1"/>
        <Element index="70" value="0.5"/>
        <Element index="71" value="0"/>
        <Element index="72" value="16.7"/>
        <Element index="73" value="1"/>
        <Element index="74" value="0.5"/>
        <Element index="75" value="0"/>
        <Element index="76" value="17.8"/>
        <Element index="77" value="1"/>
        <Element index="78" value="0.5"/>
        <Element index="79" value="0"/>
        <Element index="80" value="18.9"/>
        <Element index="81" value="1"/>
        <Element index="82" value="0.5"/>
        <Element index="83" value="0"/>
        <Element index="84" value="20"/>
        <Element index="85" value="1"/>
        <Element index="86" value="0.5"/>
        <Element index="87" value="0"/>
      </Property>
      <Property name="ScalarRangeInitialized" id="4136.ScalarRangeInitialized" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4136.ScalarRangeInitialized.bool"/>
      </Property>
    </Proxy>
    <Proxy group="implicit_functions" type="Plane" id="3809" servers="1">
      <Property name="Normal" id="3809.Normal" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="1"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="3809.Normal.range"/>
      </Property>
      <Property name="Offset" id="3809.Offset" number_of_elements="1">
        <Element index="0" value="0"/>
      </Property>
      <Property name="Origin" id="3809.Origin" number_of_elements="3">
        <Element index="0" value="-75008.1425983384"/>
        <Element index="1" value="33083.1623034241"/>
        <Element index="2" value="-12750"/>
        <Domain name="range" id="3809.Origin.range"/>
      </Property>
    </Proxy>
    <Proxy group="implicit_functions" type="Box" id="3810" servers="1">
      <Property name="Bounds" id="3810.Bounds" 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="Position" id="3810.Position" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="3810.Position.range"/>
      </Property>
      <Property name="Rotation" id="3810.Rotation" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="3810.Rotation.range"/>
      </Property>
      <Property name="Scale" id="3810.Scale" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="1"/>
        <Element index="2" value="1"/>
        <Domain name="range" id="3810.Scale.range"/>
      </Property>
    </Proxy>
    <Proxy group="implicit_functions" type="Sphere" id="3811" servers="1">
      <Property name="Center" id="3811.Center" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="3811.Center.range"/>
      </Property>
      <Property name="Radius" id="3811.Radius" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="range" id="3811.Radius.range"/>
      </Property>
    </Proxy>
    <Proxy group="implicit_functions" type="Cylinder" id="3812" servers="1">
      <Property name="Axis" id="3812.Axis" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="1"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="3812.Axis.range"/>
      </Property>
      <Property name="Center" id="3812.Center" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="3812.Center.range"/>
      </Property>
      <Property name="Radius" id="3812.Radius" number_of_elements="1">
        <Element index="0" value="0.5"/>
        <Domain name="range" id="3812.Radius.range"/>
      </Property>
    </Proxy>
    <Proxy group="misc" type="RepresentationAnimationHelper" id="4776" servers="16">
      <Property name="Source" id="4776.Source" number_of_elements="1">
        <Proxy value="3813"/>
      </Property>
    </Proxy>
    <Proxy group="sources" type="ArrowSource" id="4225" servers="1">
      <Property name="Invert" id="4225.Invert" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4225.Invert.bool"/>
      </Property>
      <Property name="ShaftRadius" id="4225.ShaftRadius" number_of_elements="1">
        <Element index="0" value="0.03"/>
        <Domain name="range" id="4225.ShaftRadius.range"/>
      </Property>
      <Property name="ShaftResolution" id="4225.ShaftResolution" number_of_elements="1">
        <Element index="0" value="6"/>
        <Domain name="range" id="4225.ShaftResolution.range"/>
      </Property>
      <Property name="TipLength" id="4225.TipLength" number_of_elements="1">
        <Element index="0" value="0.35"/>
        <Domain name="range" id="4225.TipLength.range"/>
      </Property>
      <Property name="TipRadius" id="4225.TipRadius" number_of_elements="1">
        <Element index="0" value="0.1"/>
        <Domain name="range" id="4225.TipRadius.range"/>
      </Property>
      <Property name="TipResolution" id="4225.TipResolution" number_of_elements="1">
        <Element index="0" value="6"/>
        <Domain name="range" id="4225.TipResolution.range"/>
      </Property>
    </Proxy>
    <Proxy group="sources" type="ConeSource" id="4236" servers="1">
      <Property name="Capping" id="4236.Capping" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="4236.Capping.bool"/>
      </Property>
      <Property name="Center" id="4236.Center" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="4236.Center.range"/>
      </Property>
      <Property name="Direction" id="4236.Direction" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="4236.Direction.range"/>
      </Property>
      <Property name="Height" id="4236.Height" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="4236.Height.range"/>
      </Property>
      <Property name="Radius" id="4236.Radius" number_of_elements="1">
        <Element index="0" value="0.5"/>
        <Domain name="range" id="4236.Radius.range"/>
      </Property>
      <Property name="Resolution" id="4236.Resolution" number_of_elements="1">
        <Element index="0" value="6"/>
        <Domain name="range" id="4236.Resolution.range"/>
      </Property>
    </Proxy>
    <Proxy group="sources" type="CubeSource" id="4247" servers="1">
      <Property name="Center" id="4247.Center" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="4247.Center.range"/>
      </Property>
      <Property name="XLength" id="4247.XLength" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="4247.XLength.range"/>
      </Property>
      <Property name="YLength" id="4247.YLength" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="4247.YLength.range"/>
      </Property>
      <Property name="ZLength" id="4247.ZLength" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="4247.ZLength.range"/>
      </Property>
    </Proxy>
    <Proxy group="sources" type="CylinderSource" id="4258" servers="1">
      <Property name="Capping" id="4258.Capping" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="4258.Capping.bool"/>
      </Property>
      <Property name="Center" id="4258.Center" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="4258.Center.range"/>
      </Property>
      <Property name="Height" id="4258.Height" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="4258.Height.range"/>
      </Property>
      <Property name="Radius" id="4258.Radius" number_of_elements="1">
        <Element index="0" value="0.5"/>
        <Domain name="range" id="4258.Radius.range"/>
      </Property>
      <Property name="Resolution" id="4258.Resolution" number_of_elements="1">
        <Element index="0" value="6"/>
        <Domain name="range" id="4258.Resolution.range"/>
      </Property>
    </Proxy>
    <Proxy group="sources" type="LineSource" id="4269" servers="1">
      <Property name="Point1" id="4269.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="4269.Point1.range"/>
      </Property>
      <Property name="Point2" id="4269.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="4269.Point2.range"/>
      </Property>
      <Property name="Resolution" id="4269.Resolution" number_of_elements="1">
        <Element index="0" value="6"/>
        <Domain name="range" id="4269.Resolution.range"/>
      </Property>
    </Proxy>
    <Proxy group="sources" type="SphereSource" id="4280" servers="1">
      <Property name="Center" id="4280.Center" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="4280.Center.range"/>
      </Property>
      <Property name="EndPhi" id="4280.EndPhi" number_of_elements="1">
        <Element index="0" value="180"/>
        <Domain name="range" id="4280.EndPhi.range"/>
      </Property>
      <Property name="EndTheta" id="4280.EndTheta" number_of_elements="1">
        <Element index="0" value="360"/>
        <Domain name="range" id="4280.EndTheta.range"/>
      </Property>
      <Property name="PhiResolution" id="4280.PhiResolution" number_of_elements="1">
        <Element index="0" value="8"/>
        <Domain name="range" id="4280.PhiResolution.range"/>
      </Property>
      <Property name="Radius" id="4280.Radius" number_of_elements="1">
        <Element index="0" value="0.5"/>
        <Domain name="range" id="4280.Radius.range"/>
      </Property>
      <Property name="StartPhi" id="4280.StartPhi" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="range" id="4280.StartPhi.range"/>
      </Property>
      <Property name="StartTheta" id="4280.StartTheta" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="range" id="4280.StartTheta.range"/>
      </Property>
      <Property name="ThetaResolution" id="4280.ThetaResolution" number_of_elements="1">
        <Element index="0" value="8"/>
        <Domain name="range" id="4280.ThetaResolution.range"/>
      </Property>
    </Proxy>
    <Proxy group="sources" type="GlyphSource2D" id="4291" servers="1">
      <Property name="Center" id="4291.Center" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="4291.Center.range"/>
      </Property>
      <Property name="Filled" id="4291.Filled" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4291.Filled.bool"/>
      </Property>
      <Property name="GlyphType" id="4291.GlyphType" number_of_elements="1">
        <Element index="0" value="9"/>
        <Domain name="enum" id="4291.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="4302" servers="21">
      <Property name="AllowDuplicateScalars" id="4302.AllowDuplicateScalars" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="4302.AllowDuplicateScalars.bool"/>
      </Property>
      <Property name="Points" id="4302.Points" number_of_elements="88">
        <Element index="0" value="-2"/>
        <Element index="1" value="1"/>
        <Element index="2" value="0.5"/>
        <Element index="3" value="0"/>
        <Element index="4" value="-1"/>
        <Element index="5" value="1"/>
        <Element index="6" value="0.5"/>
        <Element index="7" value="0"/>
        <Element index="8" value="0"/>
        <Element index="9" value="0"/>
        <Element index="10" value="0.5"/>
        <Element index="11" value="0"/>
        <Element index="12" value="0.2"/>
        <Element index="13" value="1"/>
        <Element index="14" value="0.5"/>
        <Element index="15" value="0"/>
        <Element index="16" value="1.3"/>
        <Element index="17" value="1"/>
        <Element index="18" value="0.5"/>
        <Element index="19" value="0"/>
        <Element index="20" value="2.4"/>
        <Element index="21" value="1"/>
        <Element index="22" value="0.5"/>
        <Element index="23" value="0"/>
        <Element index="24" value="3.5"/>
        <Element index="25" value="1"/>
        <Element index="26" value="0.5"/>
        <Element index="27" value="0"/>
        <Element index="28" value="4.6"/>
        <Element index="29" value="1"/>
        <Element index="30" value="0.5"/>
        <Element index="31" value="0"/>
        <Element index="32" value="5.7"/>
        <Element index="33" value="1"/>
        <Element index="34" value="0.5"/>
        <Element index="35" value="0"/>
        <Element index="36" value="6.8"/>
        <Element index="37" value="1"/>
        <Element index="38" value="0.5"/>
        <Element index="39" value="0"/>
        <Element index="40" value="7.9"/>
        <Element index="41" value="1"/>
        <Element index="42" value="0.5"/>
        <Element index="43" value="0"/>
        <Element index="44" value="9"/>
        <Element index="45" value="1"/>
        <Element index="46" value="0.5"/>
        <Element index="47" value="0"/>
        <Element index="48" value="10.1"/>
        <Element index="49" value="1"/>
        <Element index="50" value="0.5"/>
        <Element index="51" value="0"/>
        <Element index="52" value="11.2"/>
        <Element index="53" value="1"/>
        <Element index="54" value="0.5"/>
        <Element index="55" value="0"/>
        <Element index="56" value="12.3"/>
        <Element index="57" value="1"/>
        <Element index="58" value="0.5"/>
        <Element index="59" value="0"/>
        <Element index="60" value="13.4"/>
        <Element index="61" value="1"/>
        <Element index="62" value="0.5"/>
        <Element index="63" value="0"/>
        <Element index="64" value="14.5"/>
        <Element index="65" value="1"/>
        <Element index="66" value="0.5"/>
        <Element index="67" value="0"/>
        <Element index="68" value="15.6"/>
        <Element index="69" value="1"/>
        <Element index="70" value="0.5"/>
        <Element index="71" value="0"/>
        <Element index="72" value="16.7"/>
        <Element index="73" value="1"/>
        <Element index="74" value="0.5"/>
        <Element index="75" value="0"/>
        <Element index="76" value="17.8"/>
        <Element index="77" value="1"/>
        <Element index="78" value="0.5"/>
        <Element index="79" value="0"/>
        <Element index="80" value="18.9"/>
        <Element index="81" value="1"/>
        <Element index="82" value="0.5"/>
        <Element index="83" value="0"/>
        <Element index="84" value="20"/>
        <Element index="85" value="1"/>
        <Element index="86" value="0.5"/>
        <Element index="87" value="0"/>
      </Property>
      <Property name="ScalarRangeInitialized" id="4302.ScalarRangeInitialized" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4302.ScalarRangeInitialized.bool"/>
      </Property>
    </Proxy>
    <Proxy group="piecewise_functions" type="PiecewiseFunction" id="4303" servers="21">
      <Property name="AllowDuplicateScalars" id="4303.AllowDuplicateScalars" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="4303.AllowDuplicateScalars.bool"/>
      </Property>
      <Property name="Points" id="4303.Points" number_of_elements="88">
        <Element index="0" value="-2"/>
        <Element index="1" value="1"/>
        <Element index="2" value="0.5"/>
        <Element index="3" value="0"/>
        <Element index="4" value="-1"/>
        <Element index="5" value="1"/>
        <Element index="6" value="0.5"/>
        <Element index="7" value="0"/>
        <Element index="8" value="0"/>
        <Element index="9" value="0"/>
        <Element index="10" value="0.5"/>
        <Element index="11" value="0"/>
        <Element index="12" value="0.2"/>
        <Element index="13" value="1"/>
        <Element index="14" value="0.5"/>
        <Element index="15" value="0"/>
        <Element index="16" value="1.3"/>
        <Element index="17" value="1"/>
        <Element index="18" value="0.5"/>
        <Element index="19" value="0"/>
        <Element index="20" value="2.4"/>
        <Element index="21" value="1"/>
        <Element index="22" value="0.5"/>
        <Element index="23" value="0"/>
        <Element index="24" value="3.5"/>
        <Element index="25" value="1"/>
        <Element index="26" value="0.5"/>
        <Element index="27" value="0"/>
        <Element index="28" value="4.6"/>
        <Element index="29" value="1"/>
        <Element index="30" value="0.5"/>
        <Element index="31" value="0"/>
        <Element index="32" value="5.7"/>
        <Element index="33" value="1"/>
        <Element index="34" value="0.5"/>
        <Element index="35" value="0"/>
        <Element index="36" value="6.8"/>
        <Element index="37" value="1"/>
        <Element index="38" value="0.5"/>
        <Element index="39" value="0"/>
        <Element index="40" value="7.9"/>
        <Element index="41" value="1"/>
        <Element index="42" value="0.5"/>
        <Element index="43" value="0"/>
        <Element index="44" value="9"/>
        <Element index="45" value="1"/>
        <Element index="46" value="0.5"/>
        <Element index="47" value="0"/>
        <Element index="48" value="10.1"/>
        <Element index="49" value="1"/>
        <Element index="50" value="0.5"/>
        <Element index="51" value="0"/>
        <Element index="52" value="11.2"/>
        <Element index="53" value="1"/>
        <Element index="54" value="0.5"/>
        <Element index="55" value="0"/>
        <Element index="56" value="12.3"/>
        <Element index="57" value="1"/>
        <Element index="58" value="0.5"/>
        <Element index="59" value="0"/>
        <Element index="60" value="13.4"/>
        <Element index="61" value="1"/>
        <Element index="62" value="0.5"/>
        <Element index="63" value="0"/>
        <Element index="64" value="14.5"/>
        <Element index="65" value="1"/>
        <Element index="66" value="0.5"/>
        <Element index="67" value="0"/>
        <Element index="68" value="15.6"/>
        <Element index="69" value="1"/>
        <Element index="70" value="0.5"/>
        <Element index="71" value="0"/>
        <Element index="72" value="16.7"/>
        <Element index="73" value="1"/>
        <Element index="74" value="0.5"/>
        <Element index="75" value="0"/>
        <Element index="76" value="17.8"/>
        <Element index="77" value="1"/>
        <Element index="78" value="0.5"/>
        <Element index="79" value="0"/>
        <Element index="80" value="18.9"/>
        <Element index="81" value="1"/>
        <Element index="82" value="0.5"/>
        <Element index="83" value="0"/>
        <Element index="84" value="20"/>
        <Element index="85" value="1"/>
        <Element index="86" value="0.5"/>
        <Element index="87" value="0"/>
      </Property>
      <Property name="ScalarRangeInitialized" id="4303.ScalarRangeInitialized" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4303.ScalarRangeInitialized.bool"/>
      </Property>
    </Proxy>
    <Proxy group="incremental_point_locators" type="MergePoints" id="3824" servers="1">
      <Property name="Divisions" id="3824.Divisions" number_of_elements="3">
        <Element index="0" value="50"/>
        <Element index="1" value="50"/>
        <Element index="2" value="50"/>
      </Property>
      <Property name="NumberOfPointsPerBucket" id="3824.NumberOfPointsPerBucket" number_of_elements="1">
        <Element index="0" value="8"/>
      </Property>
    </Proxy>
    <Proxy group="incremental_point_locators" type="IncrementalOctreeMergePoints" id="3825" servers="1">
      <Property name="MaxPointsPerLeaf" id="3825.MaxPointsPerLeaf" number_of_elements="1">
        <Element index="0" value="128"/>
        <Domain name="range" id="3825.MaxPointsPerLeaf.range"/>
      </Property>
      <Property name="Tolerance" id="3825.Tolerance" number_of_elements="1">
        <Element index="0" value="0"/>
      </Property>
    </Proxy>
    <Proxy group="incremental_point_locators" type="NonMergingPointLocator" id="3826" servers="1">
      <Property name="Divisions" id="3826.Divisions" number_of_elements="3">
        <Element index="0" value="50"/>
        <Element index="1" value="50"/>
        <Element index="2" value="50"/>
      </Property>
      <Property name="NumberOfPointsPerBucket" id="3826.NumberOfPointsPerBucket" number_of_elements="1">
        <Element index="0" value="8"/>
      </Property>
    </Proxy>
    <Proxy group="misc" type="RepresentationAnimationHelper" id="4777" servers="16">
      <Property name="Source" id="4777.Source" number_of_elements="1">
        <Proxy value="3827"/>
      </Property>
    </Proxy>
    <Proxy group="sources" type="ArrowSource" id="4392" servers="1">
      <Property name="Invert" id="4392.Invert" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4392.Invert.bool"/>
      </Property>
      <Property name="ShaftRadius" id="4392.ShaftRadius" number_of_elements="1">
        <Element index="0" value="0.03"/>
        <Domain name="range" id="4392.ShaftRadius.range"/>
      </Property>
      <Property name="ShaftResolution" id="4392.ShaftResolution" number_of_elements="1">
        <Element index="0" value="6"/>
        <Domain name="range" id="4392.ShaftResolution.range"/>
      </Property>
      <Property name="TipLength" id="4392.TipLength" number_of_elements="1">
        <Element index="0" value="0.35"/>
        <Domain name="range" id="4392.TipLength.range"/>
      </Property>
      <Property name="TipRadius" id="4392.TipRadius" number_of_elements="1">
        <Element index="0" value="0.1"/>
        <Domain name="range" id="4392.TipRadius.range"/>
      </Property>
      <Property name="TipResolution" id="4392.TipResolution" number_of_elements="1">
        <Element index="0" value="6"/>
        <Domain name="range" id="4392.TipResolution.range"/>
      </Property>
    </Proxy>
    <Proxy group="sources" type="ConeSource" id="4403" servers="1">
      <Property name="Capping" id="4403.Capping" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="4403.Capping.bool"/>
      </Property>
      <Property name="Center" id="4403.Center" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="4403.Center.range"/>
      </Property>
      <Property name="Direction" id="4403.Direction" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="4403.Direction.range"/>
      </Property>
      <Property name="Height" id="4403.Height" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="4403.Height.range"/>
      </Property>
      <Property name="Radius" id="4403.Radius" number_of_elements="1">
        <Element index="0" value="0.5"/>
        <Domain name="range" id="4403.Radius.range"/>
      </Property>
      <Property name="Resolution" id="4403.Resolution" number_of_elements="1">
        <Element index="0" value="6"/>
        <Domain name="range" id="4403.Resolution.range"/>
      </Property>
    </Proxy>
    <Proxy group="sources" type="CubeSource" id="4414" servers="1">
      <Property name="Center" id="4414.Center" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="4414.Center.range"/>
      </Property>
      <Property name="XLength" id="4414.XLength" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="4414.XLength.range"/>
      </Property>
      <Property name="YLength" id="4414.YLength" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="4414.YLength.range"/>
      </Property>
      <Property name="ZLength" id="4414.ZLength" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="4414.ZLength.range"/>
      </Property>
    </Proxy>
    <Proxy group="sources" type="CylinderSource" id="4425" servers="1">
      <Property name="Capping" id="4425.Capping" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="4425.Capping.bool"/>
      </Property>
      <Property name="Center" id="4425.Center" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="4425.Center.range"/>
      </Property>
      <Property name="Height" id="4425.Height" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="4425.Height.range"/>
      </Property>
      <Property name="Radius" id="4425.Radius" number_of_elements="1">
        <Element index="0" value="0.5"/>
        <Domain name="range" id="4425.Radius.range"/>
      </Property>
      <Property name="Resolution" id="4425.Resolution" number_of_elements="1">
        <Element index="0" value="6"/>
        <Domain name="range" id="4425.Resolution.range"/>
      </Property>
    </Proxy>
    <Proxy group="sources" type="LineSource" id="4436" servers="1">
      <Property name="Point1" id="4436.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="4436.Point1.range"/>
      </Property>
      <Property name="Point2" id="4436.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="4436.Point2.range"/>
      </Property>
      <Property name="Resolution" id="4436.Resolution" number_of_elements="1">
        <Element index="0" value="6"/>
        <Domain name="range" id="4436.Resolution.range"/>
      </Property>
    </Proxy>
    <Proxy group="sources" type="SphereSource" id="4447" servers="1">
      <Property name="Center" id="4447.Center" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="4447.Center.range"/>
      </Property>
      <Property name="EndPhi" id="4447.EndPhi" number_of_elements="1">
        <Element index="0" value="180"/>
        <Domain name="range" id="4447.EndPhi.range"/>
      </Property>
      <Property name="EndTheta" id="4447.EndTheta" number_of_elements="1">
        <Element index="0" value="360"/>
        <Domain name="range" id="4447.EndTheta.range"/>
      </Property>
      <Property name="PhiResolution" id="4447.PhiResolution" number_of_elements="1">
        <Element index="0" value="8"/>
        <Domain name="range" id="4447.PhiResolution.range"/>
      </Property>
      <Property name="Radius" id="4447.Radius" number_of_elements="1">
        <Element index="0" value="0.5"/>
        <Domain name="range" id="4447.Radius.range"/>
      </Property>
      <Property name="StartPhi" id="4447.StartPhi" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="range" id="4447.StartPhi.range"/>
      </Property>
      <Property name="StartTheta" id="4447.StartTheta" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="range" id="4447.StartTheta.range"/>
      </Property>
      <Property name="ThetaResolution" id="4447.ThetaResolution" number_of_elements="1">
        <Element index="0" value="8"/>
        <Domain name="range" id="4447.ThetaResolution.range"/>
      </Property>
    </Proxy>
    <Proxy group="sources" type="GlyphSource2D" id="4458" servers="1">
      <Property name="Center" id="4458.Center" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="4458.Center.range"/>
      </Property>
      <Property name="Filled" id="4458.Filled" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4458.Filled.bool"/>
      </Property>
      <Property name="GlyphType" id="4458.GlyphType" number_of_elements="1">
        <Element index="0" value="9"/>
        <Domain name="enum" id="4458.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="4469" servers="21">
      <Property name="AllowDuplicateScalars" id="4469.AllowDuplicateScalars" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="4469.AllowDuplicateScalars.bool"/>
      </Property>
      <Property name="Points" id="4469.Points" number_of_elements="88">
        <Element index="0" value="-2"/>
        <Element index="1" value="1"/>
        <Element index="2" value="0.5"/>
        <Element index="3" value="0"/>
        <Element index="4" value="-1"/>
        <Element index="5" value="1"/>
        <Element index="6" value="0.5"/>
        <Element index="7" value="0"/>
        <Element index="8" value="0"/>
        <Element index="9" value="0"/>
        <Element index="10" value="0.5"/>
        <Element index="11" value="0"/>
        <Element index="12" value="0.2"/>
        <Element index="13" value="1"/>
        <Element index="14" value="0.5"/>
        <Element index="15" value="0"/>
        <Element index="16" value="1.3"/>
        <Element index="17" value="1"/>
        <Element index="18" value="0.5"/>
        <Element index="19" value="0"/>
        <Element index="20" value="2.4"/>
        <Element index="21" value="1"/>
        <Element index="22" value="0.5"/>
        <Element index="23" value="0"/>
        <Element index="24" value="3.5"/>
        <Element index="25" value="1"/>
        <Element index="26" value="0.5"/>
        <Element index="27" value="0"/>
        <Element index="28" value="4.6"/>
        <Element index="29" value="1"/>
        <Element index="30" value="0.5"/>
        <Element index="31" value="0"/>
        <Element index="32" value="5.7"/>
        <Element index="33" value="1"/>
        <Element index="34" value="0.5"/>
        <Element index="35" value="0"/>
        <Element index="36" value="6.8"/>
        <Element index="37" value="1"/>
        <Element index="38" value="0.5"/>
        <Element index="39" value="0"/>
        <Element index="40" value="7.9"/>
        <Element index="41" value="1"/>
        <Element index="42" value="0.5"/>
        <Element index="43" value="0"/>
        <Element index="44" value="9"/>
        <Element index="45" value="1"/>
        <Element index="46" value="0.5"/>
        <Element index="47" value="0"/>
        <Element index="48" value="10.1"/>
        <Element index="49" value="1"/>
        <Element index="50" value="0.5"/>
        <Element index="51" value="0"/>
        <Element index="52" value="11.2"/>
        <Element index="53" value="1"/>
        <Element index="54" value="0.5"/>
        <Element index="55" value="0"/>
        <Element index="56" value="12.3"/>
        <Element index="57" value="1"/>
        <Element index="58" value="0.5"/>
        <Element index="59" value="0"/>
        <Element index="60" value="13.4"/>
        <Element index="61" value="1"/>
        <Element index="62" value="0.5"/>
        <Element index="63" value="0"/>
        <Element index="64" value="14.5"/>
        <Element index="65" value="1"/>
        <Element index="66" value="0.5"/>
        <Element index="67" value="0"/>
        <Element index="68" value="15.6"/>
        <Element index="69" value="1"/>
        <Element index="70" value="0.5"/>
        <Element index="71" value="0"/>
        <Element index="72" value="16.7"/>
        <Element index="73" value="1"/>
        <Element index="74" value="0.5"/>
        <Element index="75" value="0"/>
        <Element index="76" value="17.8"/>
        <Element index="77" value="1"/>
        <Element index="78" value="0.5"/>
        <Element index="79" value="0"/>
        <Element index="80" value="18.9"/>
        <Element index="81" value="1"/>
        <Element index="82" value="0.5"/>
        <Element index="83" value="0"/>
        <Element index="84" value="20"/>
        <Element index="85" value="1"/>
        <Element index="86" value="0.5"/>
        <Element index="87" value="0"/>
      </Property>
      <Property name="ScalarRangeInitialized" id="4469.ScalarRangeInitialized" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4469.ScalarRangeInitialized.bool"/>
      </Property>
    </Proxy>
    <Proxy group="piecewise_functions" type="PiecewiseFunction" id="4470" servers="21">
      <Property name="AllowDuplicateScalars" id="4470.AllowDuplicateScalars" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="4470.AllowDuplicateScalars.bool"/>
      </Property>
      <Property name="Points" id="4470.Points" number_of_elements="88">
        <Element index="0" value="-2"/>
        <Element index="1" value="1"/>
        <Element index="2" value="0.5"/>
        <Element index="3" value="0"/>
        <Element index="4" value="-1"/>
        <Element index="5" value="1"/>
        <Element index="6" value="0.5"/>
        <Element index="7" value="0"/>
        <Element index="8" value="0"/>
        <Element index="9" value="0"/>
        <Element index="10" value="0.5"/>
        <Element index="11" value="0"/>
        <Element index="12" value="0.2"/>
        <Element index="13" value="1"/>
        <Element index="14" value="0.5"/>
        <Element index="15" value="0"/>
        <Element index="16" value="1.3"/>
        <Element index="17" value="1"/>
        <Element index="18" value="0.5"/>
        <Element index="19" value="0"/>
        <Element index="20" value="2.4"/>
        <Element index="21" value="1"/>
        <Element index="22" value="0.5"/>
        <Element index="23" value="0"/>
        <Element index="24" value="3.5"/>
        <Element index="25" value="1"/>
        <Element index="26" value="0.5"/>
        <Element index="27" value="0"/>
        <Element index="28" value="4.6"/>
        <Element index="29" value="1"/>
        <Element index="30" value="0.5"/>
        <Element index="31" value="0"/>
        <Element index="32" value="5.7"/>
        <Element index="33" value="1"/>
        <Element index="34" value="0.5"/>
        <Element index="35" value="0"/>
        <Element index="36" value="6.8"/>
        <Element index="37" value="1"/>
        <Element index="38" value="0.5"/>
        <Element index="39" value="0"/>
        <Element index="40" value="7.9"/>
        <Element index="41" value="1"/>
        <Element index="42" value="0.5"/>
        <Element index="43" value="0"/>
        <Element index="44" value="9"/>
        <Element index="45" value="1"/>
        <Element index="46" value="0.5"/>
        <Element index="47" value="0"/>
        <Element index="48" value="10.1"/>
        <Element index="49" value="1"/>
        <Element index="50" value="0.5"/>
        <Element index="51" value="0"/>
        <Element index="52" value="11.2"/>
        <Element index="53" value="1"/>
        <Element index="54" value="0.5"/>
        <Element index="55" value="0"/>
        <Element index="56" value="12.3"/>
        <Element index="57" value="1"/>
        <Element index="58" value="0.5"/>
        <Element index="59" value="0"/>
        <Element index="60" value="13.4"/>
        <Element index="61" value="1"/>
        <Element index="62" value="0.5"/>
        <Element index="63" value="0"/>
        <Element index="64" value="14.5"/>
        <Element index="65" value="1"/>
        <Element index="66" value="0.5"/>
        <Element index="67" value="0"/>
        <Element index="68" value="15.6"/>
        <Element index="69" value="1"/>
        <Element index="70" value="0.5"/>
        <Element index="71" value="0"/>
        <Element index="72" value="16.7"/>
        <Element index="73" value="1"/>
        <Element index="74" value="0.5"/>
        <Element index="75" value="0"/>
        <Element index="76" value="17.8"/>
        <Element index="77" value="1"/>
        <Element index="78" value="0.5"/>
        <Element index="79" value="0"/>
        <Element index="80" value="18.9"/>
        <Element index="81" value="1"/>
        <Element index="82" value="0.5"/>
        <Element index="83" value="0"/>
        <Element index="84" value="20"/>
        <Element index="85" value="1"/>
        <Element index="86" value="0.5"/>
        <Element index="87" value="0"/>
      </Property>
      <Property name="ScalarRangeInitialized" id="4470.ScalarRangeInitialized" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4470.ScalarRangeInitialized.bool"/>
      </Property>
    </Proxy>
    <Proxy group="implicit_functions" type="Plane" id="4778" servers="1">
      <Property name="Normal" id="4778.Normal" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="4778.Normal.range"/>
      </Property>
      <Property name="Offset" id="4778.Offset" number_of_elements="1">
        <Element index="0" value="0"/>
      </Property>
      <Property name="Origin" id="4778.Origin" number_of_elements="3">
        <Element index="0" value="-82660.4640934327"/>
        <Element index="1" value="51063.9968332023"/>
        <Element index="2" value="-12750"/>
        <Domain name="range" id="4778.Origin.range"/>
      </Property>
    </Proxy>
    <Proxy group="implicit_functions" type="Box" id="4779" servers="1">
      <Property name="Bounds" id="4779.Bounds" 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="Position" id="4779.Position" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="4779.Position.range"/>
      </Property>
      <Property name="Rotation" id="4779.Rotation" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="4779.Rotation.range"/>
      </Property>
      <Property name="Scale" id="4779.Scale" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="1"/>
        <Element index="2" value="1"/>
        <Domain name="range" id="4779.Scale.range"/>
      </Property>
    </Proxy>
    <Proxy group="implicit_functions" type="Sphere" id="4780" servers="1">
      <Property name="Center" id="4780.Center" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="4780.Center.range"/>
      </Property>
      <Property name="Radius" id="4780.Radius" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="range" id="4780.Radius.range"/>
      </Property>
    </Proxy>
    <Proxy group="implicit_functions" type="Cylinder" id="4781" servers="1">
      <Property name="Axis" id="4781.Axis" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="1"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="4781.Axis.range"/>
      </Property>
      <Property name="Center" id="4781.Center" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="4781.Center.range"/>
      </Property>
      <Property name="Radius" id="4781.Radius" number_of_elements="1">
        <Element index="0" value="0.5"/>
        <Domain name="range" id="4781.Radius.range"/>
      </Property>
    </Proxy>
    <Proxy group="misc" type="RepresentationAnimationHelper" id="4782" servers="16">
      <Property name="Source" id="4782.Source"/>
    </Proxy>
    <Proxy group="sources" type="ArrowSource" id="4783" servers="1">
      <Property name="Invert" id="4783.Invert" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4783.Invert.bool"/>
      </Property>
      <Property name="ShaftRadius" id="4783.ShaftRadius" number_of_elements="1">
        <Element index="0" value="0.03"/>
        <Domain name="range" id="4783.ShaftRadius.range"/>
      </Property>
      <Property name="ShaftResolution" id="4783.ShaftResolution" number_of_elements="1">
        <Element index="0" value="6"/>
        <Domain name="range" id="4783.ShaftResolution.range"/>
      </Property>
      <Property name="TipLength" id="4783.TipLength" number_of_elements="1">
        <Element index="0" value="0.35"/>
        <Domain name="range" id="4783.TipLength.range"/>
      </Property>
      <Property name="TipRadius" id="4783.TipRadius" number_of_elements="1">
        <Element index="0" value="0.1"/>
        <Domain name="range" id="4783.TipRadius.range"/>
      </Property>
      <Property name="TipResolution" id="4783.TipResolution" number_of_elements="1">
        <Element index="0" value="6"/>
        <Domain name="range" id="4783.TipResolution.range"/>
      </Property>
    </Proxy>
    <Proxy group="sources" type="ConeSource" id="4794" servers="1">
      <Property name="Capping" id="4794.Capping" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="4794.Capping.bool"/>
      </Property>
      <Property name="Center" id="4794.Center" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="4794.Center.range"/>
      </Property>
      <Property name="Direction" id="4794.Direction" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="4794.Direction.range"/>
      </Property>
      <Property name="Height" id="4794.Height" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="4794.Height.range"/>
      </Property>
      <Property name="Radius" id="4794.Radius" number_of_elements="1">
        <Element index="0" value="0.5"/>
        <Domain name="range" id="4794.Radius.range"/>
      </Property>
      <Property name="Resolution" id="4794.Resolution" number_of_elements="1">
        <Element index="0" value="6"/>
        <Domain name="range" id="4794.Resolution.range"/>
      </Property>
    </Proxy>
    <Proxy group="sources" type="CubeSource" id="4805" servers="1">
      <Property name="Center" id="4805.Center" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="4805.Center.range"/>
      </Property>
      <Property name="XLength" id="4805.XLength" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="4805.XLength.range"/>
      </Property>
      <Property name="YLength" id="4805.YLength" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="4805.YLength.range"/>
      </Property>
      <Property name="ZLength" id="4805.ZLength" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="4805.ZLength.range"/>
      </Property>
    </Proxy>
    <Proxy group="sources" type="CylinderSource" id="4816" servers="1">
      <Property name="Capping" id="4816.Capping" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="4816.Capping.bool"/>
      </Property>
      <Property name="Center" id="4816.Center" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="4816.Center.range"/>
      </Property>
      <Property name="Height" id="4816.Height" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="4816.Height.range"/>
      </Property>
      <Property name="Radius" id="4816.Radius" number_of_elements="1">
        <Element index="0" value="0.5"/>
        <Domain name="range" id="4816.Radius.range"/>
      </Property>
      <Property name="Resolution" id="4816.Resolution" number_of_elements="1">
        <Element index="0" value="6"/>
        <Domain name="range" id="4816.Resolution.range"/>
      </Property>
    </Proxy>
    <Proxy group="sources" type="LineSource" id="4827" servers="1">
      <Property name="Point1" id="4827.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="4827.Point1.range"/>
      </Property>
      <Property name="Point2" id="4827.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="4827.Point2.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="SphereSource" 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="EndPhi" id="4838.EndPhi" number_of_elements="1">
        <Element index="0" value="180"/>
        <Domain name="range" id="4838.EndPhi.range"/>
      </Property>
      <Property name="EndTheta" id="4838.EndTheta" number_of_elements="1">
        <Element index="0" value="360"/>
        <Domain name="range" id="4838.EndTheta.range"/>
      </Property>
      <Property name="PhiResolution" id="4838.PhiResolution" number_of_elements="1">
        <Element index="0" value="8"/>
        <Domain name="range" id="4838.PhiResolution.range"/>
      </Property>
      <Property name="Radius" id="4838.Radius" number_of_elements="1">
        <Element index="0" value="0.5"/>
        <Domain name="range" id="4838.Radius.range"/>
      </Property>
      <Property name="StartPhi" id="4838.StartPhi" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="range" id="4838.StartPhi.range"/>
      </Property>
      <Property name="StartTheta" id="4838.StartTheta" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="range" id="4838.StartTheta.range"/>
      </Property>
      <Property name="ThetaResolution" id="4838.ThetaResolution" number_of_elements="1">
        <Element index="0" value="8"/>
        <Domain name="range" id="4838.ThetaResolution.range"/>
      </Property>
    </Proxy>
    <Proxy group="sources" type="GlyphSource2D" id="4849" servers="1">
      <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="Filled" id="4849.Filled" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4849.Filled.bool"/>
      </Property>
      <Property name="GlyphType" id="4849.GlyphType" number_of_elements="1">
        <Element index="0" value="9"/>
        <Domain name="enum" id="4849.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="4860" servers="21">
      <Property name="AllowDuplicateScalars" id="4860.AllowDuplicateScalars" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="4860.AllowDuplicateScalars.bool"/>
      </Property>
      <Property name="Points" id="4860.Points" number_of_elements="88">
        <Element index="0" value="-2"/>
        <Element index="1" value="1"/>
        <Element index="2" value="0.5"/>
        <Element index="3" value="0"/>
        <Element index="4" value="-1"/>
        <Element index="5" value="1"/>
        <Element index="6" value="0.5"/>
        <Element index="7" value="0"/>
        <Element index="8" value="0"/>
        <Element index="9" value="0"/>
        <Element index="10" value="0.5"/>
        <Element index="11" value="0"/>
        <Element index="12" value="0.2"/>
        <Element index="13" value="1"/>
        <Element index="14" value="0.5"/>
        <Element index="15" value="0"/>
        <Element index="16" value="1.3"/>
        <Element index="17" value="1"/>
        <Element index="18" value="0.5"/>
        <Element index="19" value="0"/>
        <Element index="20" value="2.4"/>
        <Element index="21" value="1"/>
        <Element index="22" value="0.5"/>
        <Element index="23" value="0"/>
        <Element index="24" value="3.5"/>
        <Element index="25" value="1"/>
        <Element index="26" value="0.5"/>
        <Element index="27" value="0"/>
        <Element index="28" value="4.6"/>
        <Element index="29" value="1"/>
        <Element index="30" value="0.5"/>
        <Element index="31" value="0"/>
        <Element index="32" value="5.7"/>
        <Element index="33" value="1"/>
        <Element index="34" value="0.5"/>
        <Element index="35" value="0"/>
        <Element index="36" value="6.8"/>
        <Element index="37" value="1"/>
        <Element index="38" value="0.5"/>
        <Element index="39" value="0"/>
        <Element index="40" value="7.9"/>
        <Element index="41" value="1"/>
        <Element index="42" value="0.5"/>
        <Element index="43" value="0"/>
        <Element index="44" value="9"/>
        <Element index="45" value="1"/>
        <Element index="46" value="0.5"/>
        <Element index="47" value="0"/>
        <Element index="48" value="10.1"/>
        <Element index="49" value="1"/>
        <Element index="50" value="0.5"/>
        <Element index="51" value="0"/>
        <Element index="52" value="11.2"/>
        <Element index="53" value="1"/>
        <Element index="54" value="0.5"/>
        <Element index="55" value="0"/>
        <Element index="56" value="12.3"/>
        <Element index="57" value="1"/>
        <Element index="58" value="0.5"/>
        <Element index="59" value="0"/>
        <Element index="60" value="13.4"/>
        <Element index="61" value="1"/>
        <Element index="62" value="0.5"/>
        <Element index="63" value="0"/>
        <Element index="64" value="14.5"/>
        <Element index="65" value="1"/>
        <Element index="66" value="0.5"/>
        <Element index="67" value="0"/>
        <Element index="68" value="15.6"/>
        <Element index="69" value="1"/>
        <Element index="70" value="0.5"/>
        <Element index="71" value="0"/>
        <Element index="72" value="16.7"/>
        <Element index="73" value="1"/>
        <Element index="74" value="0.5"/>
        <Element index="75" value="0"/>
        <Element index="76" value="17.8"/>
        <Element index="77" value="1"/>
        <Element index="78" value="0.5"/>
        <Element index="79" value="0"/>
        <Element index="80" value="18.9"/>
        <Element index="81" value="1"/>
        <Element index="82" value="0.5"/>
        <Element index="83" value="0"/>
        <Element index="84" value="20"/>
        <Element index="85" value="1"/>
        <Element index="86" value="0.5"/>
        <Element index="87" value="0"/>
      </Property>
      <Property name="ScalarRangeInitialized" id="4860.ScalarRangeInitialized" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4860.ScalarRangeInitialized.bool"/>
      </Property>
    </Proxy>
    <Proxy group="piecewise_functions" type="PiecewiseFunction" id="4861" servers="21">
      <Property name="AllowDuplicateScalars" id="4861.AllowDuplicateScalars" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="4861.AllowDuplicateScalars.bool"/>
      </Property>
      <Property name="Points" id="4861.Points" number_of_elements="88">
        <Element index="0" value="-2"/>
        <Element index="1" value="1"/>
        <Element index="2" value="0.5"/>
        <Element index="3" value="0"/>
        <Element index="4" value="-1"/>
        <Element index="5" value="1"/>
        <Element index="6" value="0.5"/>
        <Element index="7" value="0"/>
        <Element index="8" value="0"/>
        <Element index="9" value="0"/>
        <Element index="10" value="0.5"/>
        <Element index="11" value="0"/>
        <Element index="12" value="0.2"/>
        <Element index="13" value="1"/>
        <Element index="14" value="0.5"/>
        <Element index="15" value="0"/>
        <Element index="16" value="1.3"/>
        <Element index="17" value="1"/>
        <Element index="18" value="0.5"/>
        <Element index="19" value="0"/>
        <Element index="20" value="2.4"/>
        <Element index="21" value="1"/>
        <Element index="22" value="0.5"/>
        <Element index="23" value="0"/>
        <Element index="24" value="3.5"/>
        <Element index="25" value="1"/>
        <Element index="26" value="0.5"/>
        <Element index="27" value="0"/>
        <Element index="28" value="4.6"/>
        <Element index="29" value="1"/>
        <Element index="30" value="0.5"/>
        <Element index="31" value="0"/>
        <Element index="32" value="5.7"/>
        <Element index="33" value="1"/>
        <Element index="34" value="0.5"/>
        <Element index="35" value="0"/>
        <Element index="36" value="6.8"/>
        <Element index="37" value="1"/>
        <Element index="38" value="0.5"/>
        <Element index="39" value="0"/>
        <Element index="40" value="7.9"/>
        <Element index="41" value="1"/>
        <Element index="42" value="0.5"/>
        <Element index="43" value="0"/>
        <Element index="44" value="9"/>
        <Element index="45" value="1"/>
        <Element index="46" value="0.5"/>
        <Element index="47" value="0"/>
        <Element index="48" value="10.1"/>
        <Element index="49" value="1"/>
        <Element index="50" value="0.5"/>
        <Element index="51" value="0"/>
        <Element index="52" value="11.2"/>
        <Element index="53" value="1"/>
        <Element index="54" value="0.5"/>
        <Element index="55" value="0"/>
        <Element index="56" value="12.3"/>
        <Element index="57" value="1"/>
        <Element index="58" value="0.5"/>
        <Element index="59" value="0"/>
        <Element index="60" value="13.4"/>
        <Element index="61" value="1"/>
        <Element index="62" value="0.5"/>
        <Element index="63" value="0"/>
        <Element index="64" value="14.5"/>
        <Element index="65" value="1"/>
        <Element index="66" value="0.5"/>
        <Element index="67" value="0"/>
        <Element index="68" value="15.6"/>
        <Element index="69" value="1"/>
        <Element index="70" value="0.5"/>
        <Element index="71" value="0"/>
        <Element index="72" value="16.7"/>
        <Element index="73" value="1"/>
        <Element index="74" value="0.5"/>
        <Element index="75" value="0"/>
        <Element index="76" value="17.8"/>
        <Element index="77" value="1"/>
        <Element index="78" value="0.5"/>
        <Element index="79" value="0"/>
        <Element index="80" value="18.9"/>
        <Element index="81" value="1"/>
        <Element index="82" value="0.5"/>
        <Element index="83" value="0"/>
        <Element index="84" value="20"/>
        <Element index="85" value="1"/>
        <Element index="86" value="0.5"/>
        <Element index="87" value="0"/>
      </Property>
      <Property name="ScalarRangeInitialized" id="4861.ScalarRangeInitialized" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4861.ScalarRangeInitialized.bool"/>
      </Property>
    </Proxy>
    <Proxy group="implicit_functions" type="Plane" id="3838" servers="1">
      <Property name="Normal" id="3838.Normal" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="1"/>
        <Domain name="range" id="3838.Normal.range"/>
      </Property>
      <Property name="Offset" id="3838.Offset" number_of_elements="1">
        <Element index="0" value="0"/>
      </Property>
      <Property name="Origin" id="3838.Origin" number_of_elements="3">
        <Element index="0" value="-75008.1425983384"/>
        <Element index="1" value="51063.9968332023"/>
        <Element index="2" value="-5204.05531672699"/>
        <Domain name="range" id="3838.Origin.range"/>
      </Property>
    </Proxy>
    <Proxy group="implicit_functions" type="Box" id="3839" servers="1">
      <Property name="Bounds" id="3839.Bounds" 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="Position" id="3839.Position" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="3839.Position.range"/>
      </Property>
      <Property name="Rotation" id="3839.Rotation" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="3839.Rotation.range"/>
      </Property>
      <Property name="Scale" id="3839.Scale" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="1"/>
        <Element index="2" value="1"/>
        <Domain name="range" id="3839.Scale.range"/>
      </Property>
    </Proxy>
    <Proxy group="implicit_functions" type="Sphere" id="3840" servers="1">
      <Property name="Center" id="3840.Center" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="3840.Center.range"/>
      </Property>
      <Property name="Radius" id="3840.Radius" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="range" id="3840.Radius.range"/>
      </Property>
    </Proxy>
    <Proxy group="implicit_functions" type="Cylinder" id="3841" servers="1">
      <Property name="Axis" id="3841.Axis" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="1"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="3841.Axis.range"/>
      </Property>
      <Property name="Center" id="3841.Center" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="3841.Center.range"/>
      </Property>
      <Property name="Radius" id="3841.Radius" number_of_elements="1">
        <Element index="0" value="0.5"/>
        <Domain name="range" id="3841.Radius.range"/>
      </Property>
    </Proxy>
    <Proxy group="misc" type="RepresentationAnimationHelper" id="4862" servers="16">
      <Property name="Source" id="4862.Source" number_of_elements="1">
        <Proxy value="3842"/>
      </Property>
    </Proxy>
    <Proxy group="sources" type="ArrowSource" id="4559" servers="1">
      <Property name="Invert" id="4559.Invert" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4559.Invert.bool"/>
      </Property>
      <Property name="ShaftRadius" id="4559.ShaftRadius" number_of_elements="1">
        <Element index="0" value="0.03"/>
        <Domain name="range" id="4559.ShaftRadius.range"/>
      </Property>
      <Property name="ShaftResolution" id="4559.ShaftResolution" number_of_elements="1">
        <Element index="0" value="6"/>
        <Domain name="range" id="4559.ShaftResolution.range"/>
      </Property>
      <Property name="TipLength" id="4559.TipLength" number_of_elements="1">
        <Element index="0" value="0.35"/>
        <Domain name="range" id="4559.TipLength.range"/>
      </Property>
      <Property name="TipRadius" id="4559.TipRadius" number_of_elements="1">
        <Element index="0" value="0.1"/>
        <Domain name="range" id="4559.TipRadius.range"/>
      </Property>
      <Property name="TipResolution" id="4559.TipResolution" number_of_elements="1">
        <Element index="0" value="6"/>
        <Domain name="range" id="4559.TipResolution.range"/>
      </Property>
    </Proxy>
    <Proxy group="sources" type="ConeSource" id="4570" servers="1">
      <Property name="Capping" id="4570.Capping" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="4570.Capping.bool"/>
      </Property>
      <Property name="Center" id="4570.Center" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="4570.Center.range"/>
      </Property>
      <Property name="Direction" id="4570.Direction" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="4570.Direction.range"/>
      </Property>
      <Property name="Height" id="4570.Height" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="4570.Height.range"/>
      </Property>
      <Property name="Radius" id="4570.Radius" number_of_elements="1">
        <Element index="0" value="0.5"/>
        <Domain name="range" id="4570.Radius.range"/>
      </Property>
      <Property name="Resolution" id="4570.Resolution" number_of_elements="1">
        <Element index="0" value="6"/>
        <Domain name="range" id="4570.Resolution.range"/>
      </Property>
    </Proxy>
    <Proxy group="sources" type="CubeSource" id="4581" servers="1">
      <Property name="Center" id="4581.Center" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="4581.Center.range"/>
      </Property>
      <Property name="XLength" id="4581.XLength" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="4581.XLength.range"/>
      </Property>
      <Property name="YLength" id="4581.YLength" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="4581.YLength.range"/>
      </Property>
      <Property name="ZLength" id="4581.ZLength" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="4581.ZLength.range"/>
      </Property>
    </Proxy>
    <Proxy group="sources" type="CylinderSource" id="4592" servers="1">
      <Property name="Capping" id="4592.Capping" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="4592.Capping.bool"/>
      </Property>
      <Property name="Center" id="4592.Center" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="4592.Center.range"/>
      </Property>
      <Property name="Height" id="4592.Height" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="4592.Height.range"/>
      </Property>
      <Property name="Radius" id="4592.Radius" number_of_elements="1">
        <Element index="0" value="0.5"/>
        <Domain name="range" id="4592.Radius.range"/>
      </Property>
      <Property name="Resolution" id="4592.Resolution" number_of_elements="1">
        <Element index="0" value="6"/>
        <Domain name="range" id="4592.Resolution.range"/>
      </Property>
    </Proxy>
    <Proxy group="sources" type="LineSource" id="4603" servers="1">
      <Property name="Point1" id="4603.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="4603.Point1.range"/>
      </Property>
      <Property name="Point2" id="4603.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="4603.Point2.range"/>
      </Property>
      <Property name="Resolution" id="4603.Resolution" number_of_elements="1">
        <Element index="0" value="6"/>
        <Domain name="range" id="4603.Resolution.range"/>
      </Property>
    </Proxy>
    <Proxy group="sources" type="SphereSource" id="4614" servers="1">
      <Property name="Center" id="4614.Center" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="4614.Center.range"/>
      </Property>
      <Property name="EndPhi" id="4614.EndPhi" number_of_elements="1">
        <Element index="0" value="180"/>
        <Domain name="range" id="4614.EndPhi.range"/>
      </Property>
      <Property name="EndTheta" id="4614.EndTheta" number_of_elements="1">
        <Element index="0" value="360"/>
        <Domain name="range" id="4614.EndTheta.range"/>
      </Property>
      <Property name="PhiResolution" id="4614.PhiResolution" number_of_elements="1">
        <Element index="0" value="8"/>
        <Domain name="range" id="4614.PhiResolution.range"/>
      </Property>
      <Property name="Radius" id="4614.Radius" number_of_elements="1">
        <Element index="0" value="0.5"/>
        <Domain name="range" id="4614.Radius.range"/>
      </Property>
      <Property name="StartPhi" id="4614.StartPhi" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="range" id="4614.StartPhi.range"/>
      </Property>
      <Property name="StartTheta" id="4614.StartTheta" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="range" id="4614.StartTheta.range"/>
      </Property>
      <Property name="ThetaResolution" id="4614.ThetaResolution" number_of_elements="1">
        <Element index="0" value="8"/>
        <Domain name="range" id="4614.ThetaResolution.range"/>
      </Property>
    </Proxy>
    <Proxy group="sources" type="GlyphSource2D" id="4625" servers="1">
      <Property name="Center" id="4625.Center" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="4625.Center.range"/>
      </Property>
      <Property name="Filled" id="4625.Filled" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4625.Filled.bool"/>
      </Property>
      <Property name="GlyphType" id="4625.GlyphType" number_of_elements="1">
        <Element index="0" value="9"/>
        <Domain name="enum" id="4625.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="4636" servers="21">
      <Property name="AllowDuplicateScalars" id="4636.AllowDuplicateScalars" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="4636.AllowDuplicateScalars.bool"/>
      </Property>
      <Property name="Points" id="4636.Points" number_of_elements="88">
        <Element index="0" value="-2"/>
        <Element index="1" value="1"/>
        <Element index="2" value="0.5"/>
        <Element index="3" value="0"/>
        <Element index="4" value="-1"/>
        <Element index="5" value="1"/>
        <Element index="6" value="0.5"/>
        <Element index="7" value="0"/>
        <Element index="8" value="0"/>
        <Element index="9" value="0"/>
        <Element index="10" value="0.5"/>
        <Element index="11" value="0"/>
        <Element index="12" value="0.2"/>
        <Element index="13" value="1"/>
        <Element index="14" value="0.5"/>
        <Element index="15" value="0"/>
        <Element index="16" value="1.3"/>
        <Element index="17" value="1"/>
        <Element index="18" value="0.5"/>
        <Element index="19" value="0"/>
        <Element index="20" value="2.4"/>
        <Element index="21" value="1"/>
        <Element index="22" value="0.5"/>
        <Element index="23" value="0"/>
        <Element index="24" value="3.5"/>
        <Element index="25" value="1"/>
        <Element index="26" value="0.5"/>
        <Element index="27" value="0"/>
        <Element index="28" value="4.6"/>
        <Element index="29" value="1"/>
        <Element index="30" value="0.5"/>
        <Element index="31" value="0"/>
        <Element index="32" value="5.7"/>
        <Element index="33" value="1"/>
        <Element index="34" value="0.5"/>
        <Element index="35" value="0"/>
        <Element index="36" value="6.8"/>
        <Element index="37" value="1"/>
        <Element index="38" value="0.5"/>
        <Element index="39" value="0"/>
        <Element index="40" value="7.9"/>
        <Element index="41" value="1"/>
        <Element index="42" value="0.5"/>
        <Element index="43" value="0"/>
        <Element index="44" value="9"/>
        <Element index="45" value="1"/>
        <Element index="46" value="0.5"/>
        <Element index="47" value="0"/>
        <Element index="48" value="10.1"/>
        <Element index="49" value="1"/>
        <Element index="50" value="0.5"/>
        <Element index="51" value="0"/>
        <Element index="52" value="11.2"/>
        <Element index="53" value="1"/>
        <Element index="54" value="0.5"/>
        <Element index="55" value="0"/>
        <Element index="56" value="12.3"/>
        <Element index="57" value="1"/>
        <Element index="58" value="0.5"/>
        <Element index="59" value="0"/>
        <Element index="60" value="13.4"/>
        <Element index="61" value="1"/>
        <Element index="62" value="0.5"/>
        <Element index="63" value="0"/>
        <Element index="64" value="14.5"/>
        <Element index="65" value="1"/>
        <Element index="66" value="0.5"/>
        <Element index="67" value="0"/>
        <Element index="68" value="15.6"/>
        <Element index="69" value="1"/>
        <Element index="70" value="0.5"/>
        <Element index="71" value="0"/>
        <Element index="72" value="16.7"/>
        <Element index="73" value="1"/>
        <Element index="74" value="0.5"/>
        <Element index="75" value="0"/>
        <Element index="76" value="17.8"/>
        <Element index="77" value="1"/>
        <Element index="78" value="0.5"/>
        <Element index="79" value="0"/>
        <Element index="80" value="18.9"/>
        <Element index="81" value="1"/>
        <Element index="82" value="0.5"/>
        <Element index="83" value="0"/>
        <Element index="84" value="20"/>
        <Element index="85" value="1"/>
        <Element index="86" value="0.5"/>
        <Element index="87" value="0"/>
      </Property>
      <Property name="ScalarRangeInitialized" id="4636.ScalarRangeInitialized" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4636.ScalarRangeInitialized.bool"/>
      </Property>
    </Proxy>
    <Proxy group="piecewise_functions" type="PiecewiseFunction" id="4637" servers="21">
      <Property name="AllowDuplicateScalars" id="4637.AllowDuplicateScalars" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="4637.AllowDuplicateScalars.bool"/>
      </Property>
      <Property name="Points" id="4637.Points" number_of_elements="88">
        <Element index="0" value="-2"/>
        <Element index="1" value="1"/>
        <Element index="2" value="0.5"/>
        <Element index="3" value="0"/>
        <Element index="4" value="-1"/>
        <Element index="5" value="1"/>
        <Element index="6" value="0.5"/>
        <Element index="7" value="0"/>
        <Element index="8" value="0"/>
        <Element index="9" value="0"/>
        <Element index="10" value="0.5"/>
        <Element index="11" value="0"/>
        <Element index="12" value="0.2"/>
        <Element index="13" value="1"/>
        <Element index="14" value="0.5"/>
        <Element index="15" value="0"/>
        <Element index="16" value="1.3"/>
        <Element index="17" value="1"/>
        <Element index="18" value="0.5"/>
        <Element index="19" value="0"/>
        <Element index="20" value="2.4"/>
        <Element index="21" value="1"/>
        <Element index="22" value="0.5"/>
        <Element index="23" value="0"/>
        <Element index="24" value="3.5"/>
        <Element index="25" value="1"/>
        <Element index="26" value="0.5"/>
        <Element index="27" value="0"/>
        <Element index="28" value="4.6"/>
        <Element index="29" value="1"/>
        <Element index="30" value="0.5"/>
        <Element index="31" value="0"/>
        <Element index="32" value="5.7"/>
        <Element index="33" value="1"/>
        <Element index="34" value="0.5"/>
        <Element index="35" value="0"/>
        <Element index="36" value="6.8"/>
        <Element index="37" value="1"/>
        <Element index="38" value="0.5"/>
        <Element index="39" value="0"/>
        <Element index="40" value="7.9"/>
        <Element index="41" value="1"/>
        <Element index="42" value="0.5"/>
        <Element index="43" value="0"/>
        <Element index="44" value="9"/>
        <Element index="45" value="1"/>
        <Element index="46" value="0.5"/>
        <Element index="47" value="0"/>
        <Element index="48" value="10.1"/>
        <Element index="49" value="1"/>
        <Element index="50" value="0.5"/>
        <Element index="51" value="0"/>
        <Element index="52" value="11.2"/>
        <Element index="53" value="1"/>
        <Element index="54" value="0.5"/>
        <Element index="55" value="0"/>
        <Element index="56" value="12.3"/>
        <Element index="57" value="1"/>
        <Element index="58" value="0.5"/>
        <Element index="59" value="0"/>
        <Element index="60" value="13.4"/>
        <Element index="61" value="1"/>
        <Element index="62" value="0.5"/>
        <Element index="63" value="0"/>
        <Element index="64" value="14.5"/>
        <Element index="65" value="1"/>
        <Element index="66" value="0.5"/>
        <Element index="67" value="0"/>
        <Element index="68" value="15.6"/>
        <Element index="69" value="1"/>
        <Element index="70" value="0.5"/>
        <Element index="71" value="0"/>
        <Element index="72" value="16.7"/>
        <Element index="73" value="1"/>
        <Element index="74" value="0.5"/>
        <Element index="75" value="0"/>
        <Element index="76" value="17.8"/>
        <Element index="77" value="1"/>
        <Element index="78" value="0.5"/>
        <Element index="79" value="0"/>
        <Element index="80" value="18.9"/>
        <Element index="81" value="1"/>
        <Element index="82" value="0.5"/>
        <Element index="83" value="0"/>
        <Element index="84" value="20"/>
        <Element index="85" value="1"/>
        <Element index="86" value="0.5"/>
        <Element index="87" value="0"/>
      </Property>
      <Property name="ScalarRangeInitialized" id="4637.ScalarRangeInitialized" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4637.ScalarRangeInitialized.bool"/>
      </Property>
    </Proxy>
    <Proxy group="representations" type="GeometryRepresentation" id="4019" servers="21">
      <Property name="CubeAxesVisibility" id="4019.CubeAxesVisibility" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4019.CubeAxesVisibility.bool"/>
      </Property>
      <Property name="Input" id="4019.Input" number_of_elements="1">
        <Proxy value="3783" output_port="0"/>
        <Domain name="input_array_cell" id="4019.Input.input_array_cell"/>
        <Domain name="input_array_point" id="4019.Input.input_array_point"/>
        <Domain name="input_type" id="4019.Input.input_type"/>
      </Property>
      <Property name="Representation" id="4019.Representation" number_of_elements="1">
        <Element index="0" value="Outline"/>
        <Domain name="list" id="4019.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="4019.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="4019.SelectionCellFieldDataArrayName" number_of_elements="1">
        <Element index="0" value="Lithology_type"/>
        <Domain name="array_list" id="4019.SelectionCellFieldDataArrayName.array_list">
          <String text="Lithology_type"/>
        </Domain>
      </Property>
      <Property name="SelectionPointFieldDataArrayName" id="4019.SelectionPointFieldDataArrayName" number_of_elements="1">
        <Element index="0" value="Lithology_type"/>
        <Domain name="array_list" id="4019.SelectionPointFieldDataArrayName.array_list">
          <String text="Lithology_type"/>
        </Domain>
      </Property>
      <Property name="SelectionVisibility" id="4019.SelectionVisibility" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="4019.SelectionVisibility.bool"/>
      </Property>
      <Property name="Visibility" id="4019.Visibility" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="4019.Visibility.bool"/>
      </Property>
      <Property name="Ambient" id="4019.Ambient" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="range" id="4019.Ambient.range"/>
      </Property>
      <Property name="AmbientColor" id="4019.AmbientColor" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="1"/>
        <Element index="2" value="1"/>
        <Domain name="range" id="4019.AmbientColor.range"/>
      </Property>
      <Property name="AxesOrigin" id="4019.AxesOrigin" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="4019.AxesOrigin.range"/>
      </Property>
      <Property name="BackfaceAmbientColor" id="4019.BackfaceAmbientColor" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="1"/>
        <Element index="2" value="1"/>
        <Domain name="range" id="4019.BackfaceAmbientColor.range"/>
      </Property>
      <Property name="BackfaceDiffuseColor" id="4019.BackfaceDiffuseColor" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="1"/>
        <Element index="2" value="1"/>
        <Domain name="range" id="4019.BackfaceDiffuseColor.range"/>
      </Property>
      <Property name="BackfaceOpacity" id="4019.BackfaceOpacity" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="4019.BackfaceOpacity.range"/>
      </Property>
      <Property name="BackfaceRepresentation" id="4019.BackfaceRepresentation" number_of_elements="1">
        <Element index="0" value="400"/>
        <Domain name="enum" id="4019.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="4019.BlockColor"/>
      <Property name="BlockColorsDistinctValues" id="4019.BlockColorsDistinctValues" number_of_elements="1">
        <Element index="0" value="12"/>
        <Domain name="range" id="4019.BlockColorsDistinctValues.range"/>
      </Property>
      <Property name="BlockOpacity" id="4019.BlockOpacity"/>
      <Property name="BlockVisibility" id="4019.BlockVisibility"/>
      <Property name="CenterStickyAxes" id="4019.CenterStickyAxes" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4019.CenterStickyAxes.bool"/>
      </Property>
      <Property name="Color" id="4019.Color" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="1"/>
        <Element index="2" value="1"/>
        <Domain name="range" id="4019.Color.range"/>
      </Property>
      <Property name="ColorArrayName" id="4019.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="Lithology_type"/>
        <Domain name="array_list" id="4019.ColorArrayName.array_list">
          <String text="Lithology_type"/>
        </Domain>
        <Domain name="field_list" id="4019.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="4019.CubeAxesColor" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="1"/>
        <Element index="2" value="1"/>
        <Domain name="range" id="4019.CubeAxesColor.range"/>
      </Property>
      <Property name="CubeAxesCornerOffset" id="4019.CubeAxesCornerOffset" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="range" id="4019.CubeAxesCornerOffset.range"/>
      </Property>
      <Property name="CubeAxesFlyMode" id="4019.CubeAxesFlyMode" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="enum" id="4019.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="4019.CubeAxesGridLineLocation" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="enum" id="4019.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="4019.CubeAxesInertia" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="4019.CubeAxesInertia.range"/>
      </Property>
      <Property name="CubeAxesTickLocation" id="4019.CubeAxesTickLocation" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="enum" id="4019.CubeAxesTickLocation.enum">
          <Entry value="0" text="Inside"/>
          <Entry value="1" text="Outside"/>
          <Entry value="2" text="Both"/>
        </Domain>
      </Property>
      <Property name="CubeAxesUseDefaultXTitle" id="4019.CubeAxesUseDefaultXTitle" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="4019.CubeAxesUseDefaultXTitle.bool"/>
      </Property>
      <Property name="CubeAxesUseDefaultYTitle" id="4019.CubeAxesUseDefaultYTitle" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="4019.CubeAxesUseDefaultYTitle.bool"/>
      </Property>
      <Property name="CubeAxesUseDefaultZTitle" id="4019.CubeAxesUseDefaultZTitle" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="4019.CubeAxesUseDefaultZTitle.bool"/>
      </Property>
      <Property name="CubeAxesXAxisMinorTickVisibility" id="4019.CubeAxesXAxisMinorTickVisibility" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="4019.CubeAxesXAxisMinorTickVisibility.bool"/>
      </Property>
      <Property name="CubeAxesXAxisTickVisibility" id="4019.CubeAxesXAxisTickVisibility" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="4019.CubeAxesXAxisTickVisibility.bool"/>
      </Property>
      <Property name="CubeAxesXAxisVisibility" id="4019.CubeAxesXAxisVisibility" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="4019.CubeAxesXAxisVisibility.bool"/>
      </Property>
      <Property name="CubeAxesXGridLines" id="4019.CubeAxesXGridLines" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4019.CubeAxesXGridLines.bool"/>
      </Property>
      <Property name="CubeAxesXLabelFormat" id="4019.CubeAxesXLabelFormat" number_of_elements="1">
        <Element index="0" value="%-#6.3g"/>
      </Property>
      <Property name="CubeAxesXTitle" id="4019.CubeAxesXTitle" number_of_elements="1">
        <Element index="0" value="X-Axis"/>
      </Property>
      <Property name="CubeAxesYAxisMinorTickVisibility" id="4019.CubeAxesYAxisMinorTickVisibility" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="4019.CubeAxesYAxisMinorTickVisibility.bool"/>
      </Property>
      <Property name="CubeAxesYAxisTickVisibility" id="4019.CubeAxesYAxisTickVisibility" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="4019.CubeAxesYAxisTickVisibility.bool"/>
      </Property>
      <Property name="CubeAxesYAxisVisibility" id="4019.CubeAxesYAxisVisibility" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="4019.CubeAxesYAxisVisibility.bool"/>
      </Property>
      <Property name="CubeAxesYGridLines" id="4019.CubeAxesYGridLines" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4019.CubeAxesYGridLines.bool"/>
      </Property>
      <Property name="CubeAxesYLabelFormat" id="4019.CubeAxesYLabelFormat" number_of_elements="1">
        <Element index="0" value="%-#6.3g"/>
      </Property>
      <Property name="CubeAxesYTitle" id="4019.CubeAxesYTitle" number_of_elements="1">
        <Element index="0" value="Y-Axis"/>
      </Property>
      <Property name="CubeAxesZAxisMinorTickVisibility" id="4019.CubeAxesZAxisMinorTickVisibility" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="4019.CubeAxesZAxisMinorTickVisibility.bool"/>
      </Property>
      <Property name="CubeAxesZAxisTickVisibility" id="4019.CubeAxesZAxisTickVisibility" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="4019.CubeAxesZAxisTickVisibility.bool"/>
      </Property>
      <Property name="CubeAxesZAxisVisibility" id="4019.CubeAxesZAxisVisibility" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="4019.CubeAxesZAxisVisibility.bool"/>
      </Property>
      <Property name="CubeAxesZGridLines" id="4019.CubeAxesZGridLines" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4019.CubeAxesZGridLines.bool"/>
      </Property>
      <Property name="CubeAxesZLabelFormat" id="4019.CubeAxesZLabelFormat" number_of_elements="1">
        <Element index="0" value="%-#6.3g"/>
      </Property>
      <Property name="CubeAxesZTitle" id="4019.CubeAxesZTitle" number_of_elements="1">
        <Element index="0" value="Z-Axis"/>
      </Property>
      <Property name="CustomBounds" id="4019.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="4019.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="4019.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="4019.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="4019.CustomShader" number_of_elements="1">
        <Element index="0" value=""/>
      </Property>
      <Property name="DataBounds" id="4019.DataBounds" number_of_elements="6">
        <Element index="0" value="2.61360726650019e-321"/>
        <Element index="1" value="5.74326570482905e-316"/>
        <Element index="2" value="6.92589253794838e-310"/>
        <Element index="3" value="4.82406556136926e+228"/>
        <Element index="4" value="5.43472210425371e-322"/>
        <Element index="5" value="1.57110171793844e-76"/>
      </Property>
      <Property name="Diffuse" id="4019.Diffuse" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="4019.Diffuse.range"/>
      </Property>
      <Property name="DiffuseColor" id="4019.DiffuseColor" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="1"/>
        <Element index="2" value="1"/>
        <Domain name="range" id="4019.DiffuseColor.range"/>
      </Property>
      <Property name="EdgeColor" id="4019.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="4019.EdgeColor.range"/>
      </Property>
      <Property name="Emissive" id="4019.Emissive" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4019.Emissive.bool"/>
      </Property>
      <Property name="GaussianRadius" id="4019.GaussianRadius" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="range" id="4019.GaussianRadius.range"/>
      </Property>
      <Property name="GlyphType" id="4019.GlyphType" number_of_elements="1">
        <Proxy value="3883" output_port="0"/>
        <Domain name="input_type" id="4019.GlyphType.input_type"/>
        <Domain name="proxy_list" id="4019.GlyphType.proxy_list">
          <Proxy value="3883"/>
          <Proxy value="3894"/>
          <Proxy value="3905"/>
          <Proxy value="3916"/>
          <Proxy value="3927"/>
          <Proxy value="3938"/>
          <Proxy value="3949"/>
        </Domain>
      </Property>
      <Property name="InterpolateScalarsBeforeMapping" id="4019.InterpolateScalarsBeforeMapping" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4019.InterpolateScalarsBeforeMapping.bool"/>
      </Property>
      <Property name="Interpolation" id="4019.Interpolation" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="enum" id="4019.Interpolation.enum">
          <Entry value="0" text="Flat"/>
          <Entry value="1" text="Gouraud"/>
        </Domain>
      </Property>
      <Property name="LineWidth" id="4019.LineWidth" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="4019.LineWidth.range"/>
      </Property>
      <Property name="LookupTable" id="4019.LookupTable" number_of_elements="1">
        <Proxy value="3961"/>
        <Domain name="groups" id="4019.LookupTable.groups"/>
      </Property>
      <Property name="MapScalars" id="4019.MapScalars" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="4019.MapScalars.bool"/>
      </Property>
      <Property name="Masking" id="4019.Masking" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4019.Masking.bool"/>
      </Property>
      <Property name="MeshVisibility" id="4019.MeshVisibility" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4019.MeshVisibility.bool"/>
      </Property>
      <Property name="NonlinearSubdivisionLevel" id="4019.NonlinearSubdivisionLevel" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="4019.NonlinearSubdivisionLevel.range"/>
      </Property>
      <Property name="Opacity" id="4019.Opacity" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="4019.Opacity.range"/>
      </Property>
      <Property name="OpacityArray" id="4019.OpacityArray" 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="Lithology_type"/>
        <Domain name="array_list" id="4019.OpacityArray.array_list">
          <String text="Lithology_type"/>
        </Domain>
      </Property>
      <Property name="OpacityByArray" id="4019.OpacityByArray" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="4019.OpacityByArray.bool"/>
      </Property>
      <Property name="OpacityTransferFunction" id="4019.OpacityTransferFunction" number_of_elements="1">
        <Proxy value="3962"/>
        <Domain name="groups" id="4019.OpacityTransferFunction.groups"/>
        <Domain name="proxy_list" id="4019.OpacityTransferFunction.proxy_list">
          <Proxy value="3962"/>
        </Domain>
      </Property>
      <Property name="Orient" id="4019.Orient" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4019.Orient.bool"/>
      </Property>
      <Property name="Orientation" id="4019.Orientation" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="4019.Orientation.range"/>
      </Property>
      <Property name="OrientationMode" id="4019.OrientationMode" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="enum" id="4019.OrientationMode.enum">
          <Entry value="0" text="Direction"/>
          <Entry value="1" text="Rotation"/>
        </Domain>
      </Property>
      <Property name="Origin" id="4019.Origin" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="4019.Origin.range"/>
      </Property>
      <Property name="OriginalBoundsRangeActive" id="4019.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="4019.Pickable" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="4019.Pickable.bool"/>
      </Property>
      <Property name="PointSize" id="4019.PointSize" number_of_elements="1">
        <Element index="0" value="2"/>
        <Domain name="range" id="4019.PointSize.range"/>
      </Property>
      <Property name="Position" id="4019.Position" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="4019.Position.range"/>
      </Property>
      <Property name="Scale" id="4019.Scale" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="1"/>
        <Element index="2" value="1"/>
        <Domain name="range" id="4019.Scale.range"/>
      </Property>
      <Property name="ScaleByArray" id="4019.ScaleByArray" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4019.ScaleByArray.bool"/>
      </Property>
      <Property name="ScaleFactor" id="4019.ScaleFactor" number_of_elements="1">
        <Element index="0" value="6632.25115757818"/>
        <Domain name="bounds" id="4019.ScaleFactor.bounds"/>
        <Domain name="scalar_range" id="4019.ScaleFactor.scalar_range"/>
        <Domain name="vector_range" id="4019.ScaleFactor.vector_range"/>
      </Property>
      <Property name="ScaleMode" id="4019.ScaleMode" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="enum" id="4019.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="4019.ScaleTransferFunction" number_of_elements="1">
        <Proxy value="3963"/>
        <Domain name="groups" id="4019.ScaleTransferFunction.groups"/>
        <Domain name="proxy_list" id="4019.ScaleTransferFunction.proxy_list">
          <Proxy value="3963"/>
        </Domain>
      </Property>
      <Property name="Scaling" id="4019.Scaling" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4019.Scaling.bool"/>
      </Property>
      <Property name="SelectMaskArray" id="4019.SelectMaskArray" number_of_elements="1">
        <Element index="0" value=""/>
      </Property>
      <Property name="SelectOrientationVectors" id="4019.SelectOrientationVectors" number_of_elements="1">
        <Element index="0" value=""/>
      </Property>
      <Property name="SelectScaleArray" id="4019.SelectScaleArray" number_of_elements="1">
        <Element index="0" value=""/>
      </Property>
      <Property name="SelectionCellLabelBold" id="4019.SelectionCellLabelBold" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4019.SelectionCellLabelBold.bool"/>
      </Property>
      <Property name="SelectionCellLabelColor" id="4019.SelectionCellLabelColor" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="1"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="4019.SelectionCellLabelColor.range"/>
      </Property>
      <Property name="SelectionCellLabelFontFamily" id="4019.SelectionCellLabelFontFamily" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="enum" id="4019.SelectionCellLabelFontFamily.enum">
          <Entry value="0" text="Arial"/>
          <Entry value="1" text="Courier"/>
          <Entry value="2" text="Times"/>
        </Domain>
      </Property>
      <Property name="SelectionCellLabelFontSize" id="4019.SelectionCellLabelFontSize" number_of_elements="1">
        <Element index="0" value="18"/>
        <Domain name="range" id="4019.SelectionCellLabelFontSize.range"/>
      </Property>
      <Property name="SelectionCellLabelFormat" id="4019.SelectionCellLabelFormat" number_of_elements="1">
        <Element index="0" value=""/>
      </Property>
      <Property name="SelectionCellLabelItalic" id="4019.SelectionCellLabelItalic" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4019.SelectionCellLabelItalic.bool"/>
      </Property>
      <Property name="SelectionCellLabelJustification" id="4019.SelectionCellLabelJustification" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="enum" id="4019.SelectionCellLabelJustification.enum">
          <Entry value="0" text="Left"/>
          <Entry value="1" text="Center"/>
          <Entry value="2" text="Right"/>
        </Domain>
      </Property>
      <Property name="SelectionCellLabelOpacity" id="4019.SelectionCellLabelOpacity" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="4019.SelectionCellLabelOpacity.range"/>
      </Property>
      <Property name="SelectionCellLabelShadow" id="4019.SelectionCellLabelShadow" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4019.SelectionCellLabelShadow.bool"/>
      </Property>
      <Property name="SelectionCellLabelVisibility" id="4019.SelectionCellLabelVisibility" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4019.SelectionCellLabelVisibility.bool"/>
      </Property>
      <Property name="SelectionColor" id="4019.SelectionColor" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="0"/>
        <Element index="2" value="1"/>
        <Domain name="range" id="4019.SelectionColor.range"/>
      </Property>
      <Property name="SelectionLineWidth" id="4019.SelectionLineWidth" number_of_elements="1">
        <Element index="0" value="2"/>
        <Domain name="range" id="4019.SelectionLineWidth.range"/>
      </Property>
      <Property name="SelectionOpacity" id="4019.SelectionOpacity" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="4019.SelectionOpacity.range"/>
      </Property>
      <Property name="SelectionPointLabelBold" id="4019.SelectionPointLabelBold" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4019.SelectionPointLabelBold.bool"/>
      </Property>
      <Property name="SelectionPointLabelColor" id="4019.SelectionPointLabelColor" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="1"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="4019.SelectionPointLabelColor.range"/>
      </Property>
      <Property name="SelectionPointLabelFontFamily" id="4019.SelectionPointLabelFontFamily" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="enum" id="4019.SelectionPointLabelFontFamily.enum">
          <Entry value="0" text="Arial"/>
          <Entry value="1" text="Courier"/>
          <Entry value="2" text="Times"/>
        </Domain>
      </Property>
      <Property name="SelectionPointLabelFontSize" id="4019.SelectionPointLabelFontSize" number_of_elements="1">
        <Element index="0" value="18"/>
        <Domain name="range" id="4019.SelectionPointLabelFontSize.range"/>
      </Property>
      <Property name="SelectionPointLabelFormat" id="4019.SelectionPointLabelFormat" number_of_elements="1">
        <Element index="0" value=""/>
      </Property>
      <Property name="SelectionPointLabelItalic" id="4019.SelectionPointLabelItalic" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4019.SelectionPointLabelItalic.bool"/>
      </Property>
      <Property name="SelectionPointLabelJustification" id="4019.SelectionPointLabelJustification" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="enum" id="4019.SelectionPointLabelJustification.enum">
          <Entry value="0" text="Left"/>
          <Entry value="1" text="Center"/>
          <Entry value="2" text="Right"/>
        </Domain>
      </Property>
      <Property name="SelectionPointLabelOpacity" id="4019.SelectionPointLabelOpacity" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="4019.SelectionPointLabelOpacity.range"/>
      </Property>
      <Property name="SelectionPointLabelShadow" id="4019.SelectionPointLabelShadow" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4019.SelectionPointLabelShadow.bool"/>
      </Property>
      <Property name="SelectionPointLabelVisibility" id="4019.SelectionPointLabelVisibility" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4019.SelectionPointLabelVisibility.bool"/>
      </Property>
      <Property name="SelectionPointSize" id="4019.SelectionPointSize" number_of_elements="1">
        <Element index="0" value="5"/>
        <Domain name="range" id="4019.SelectionPointSize.range"/>
      </Property>
      <Property name="SelectionRepresentation" id="4019.SelectionRepresentation" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="enum" id="4019.SelectionRepresentation.enum">
          <Entry value="0" text="Points"/>
          <Entry value="1" text="Wireframe"/>
          <Entry value="2" text="Surface"/>
        </Domain>
      </Property>
      <Property name="SelectionUseOutline" id="4019.SelectionUseOutline" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4019.SelectionUseOutline.bool"/>
      </Property>
      <Property name="SetScaleArray" id="4019.SetScaleArray" 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="Lithology_type"/>
        <Domain name="array_list" id="4019.SetScaleArray.array_list">
          <String text="Lithology_type"/>
        </Domain>
      </Property>
      <Property name="ShaderPreset" id="4019.ShaderPreset" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="enum" id="4019.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="4019.Specular" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="range" id="4019.Specular.range"/>
      </Property>
      <Property name="SpecularColor" id="4019.SpecularColor" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="1"/>
        <Element index="2" value="1"/>
        <Domain name="range" id="4019.SpecularColor.range"/>
      </Property>
      <Property name="SpecularPower" id="4019.SpecularPower" number_of_elements="1">
        <Element index="0" value="100"/>
        <Domain name="range" id="4019.SpecularPower.range"/>
      </Property>
      <Property name="StaticMode" id="4019.StaticMode" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4019.StaticMode.bool"/>
      </Property>
      <Property name="StickyAxes" id="4019.StickyAxes" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4019.StickyAxes.bool"/>
      </Property>
      <Property name="SuppressLOD" id="4019.SuppressLOD" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4019.SuppressLOD.bool"/>
      </Property>
      <Property name="Texture" id="4019.Texture">
        <Domain name="groups" id="4019.Texture.groups"/>
      </Property>
      <Property name="Triangulate" id="4019.Triangulate" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="4019.Triangulate.bool"/>
      </Property>
      <Property name="UseAxesOrigin" id="4019.UseAxesOrigin" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4019.UseAxesOrigin.bool"/>
      </Property>
      <Property name="UserTransform" id="4019.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="4192" servers="21">
      <Property name="CubeAxesVisibility" id="4192.CubeAxesVisibility" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="4192.CubeAxesVisibility.bool"/>
      </Property>
      <Property name="Input" id="4192.Input" number_of_elements="1">
        <Proxy value="3798" output_port="0"/>
        <Domain name="input_array_cell" id="4192.Input.input_array_cell"/>
        <Domain name="input_array_point" id="4192.Input.input_array_point"/>
        <Domain name="input_type" id="4192.Input.input_type"/>
      </Property>
      <Property name="Representation" id="4192.Representation" number_of_elements="1">
        <Element index="0" value="Surface"/>
        <Domain name="list" id="4192.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="4192.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="4192.SelectionCellFieldDataArrayName" number_of_elements="1">
        <Element index="0" value="Lithology_type"/>
        <Domain name="array_list" id="4192.SelectionCellFieldDataArrayName.array_list">
          <String text="Lithology_type"/>
        </Domain>
      </Property>
      <Property name="SelectionPointFieldDataArrayName" id="4192.SelectionPointFieldDataArrayName" number_of_elements="1">
        <Element index="0" value="Lithology_type"/>
        <Domain name="array_list" id="4192.SelectionPointFieldDataArrayName.array_list">
          <String text="Lithology_type"/>
        </Domain>
      </Property>
      <Property name="SelectionVisibility" id="4192.SelectionVisibility" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="4192.SelectionVisibility.bool"/>
      </Property>
      <Property name="Visibility" id="4192.Visibility" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="4192.Visibility.bool"/>
      </Property>
      <Property name="Ambient" id="4192.Ambient" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="range" id="4192.Ambient.range"/>
      </Property>
      <Property name="AmbientColor" id="4192.AmbientColor" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="1"/>
        <Element index="2" value="1"/>
        <Domain name="range" id="4192.AmbientColor.range"/>
      </Property>
      <Property name="AxesOrigin" id="4192.AxesOrigin" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="4192.AxesOrigin.range"/>
      </Property>
      <Property name="BackfaceAmbientColor" id="4192.BackfaceAmbientColor" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="1"/>
        <Element index="2" value="1"/>
        <Domain name="range" id="4192.BackfaceAmbientColor.range"/>
      </Property>
      <Property name="BackfaceDiffuseColor" id="4192.BackfaceDiffuseColor" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="1"/>
        <Element index="2" value="1"/>
        <Domain name="range" id="4192.BackfaceDiffuseColor.range"/>
      </Property>
      <Property name="BackfaceOpacity" id="4192.BackfaceOpacity" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="4192.BackfaceOpacity.range"/>
      </Property>
      <Property name="BackfaceRepresentation" id="4192.BackfaceRepresentation" number_of_elements="1">
        <Element index="0" value="400"/>
        <Domain name="enum" id="4192.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="4192.BlockColor"/>
      <Property name="BlockColorsDistinctValues" id="4192.BlockColorsDistinctValues" number_of_elements="1">
        <Element index="0" value="12"/>
        <Domain name="range" id="4192.BlockColorsDistinctValues.range"/>
      </Property>
      <Property name="BlockOpacity" id="4192.BlockOpacity"/>
      <Property name="BlockVisibility" id="4192.BlockVisibility"/>
      <Property name="CenterStickyAxes" id="4192.CenterStickyAxes" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4192.CenterStickyAxes.bool"/>
      </Property>
      <Property name="Color" id="4192.Color" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="1"/>
        <Element index="2" value="1"/>
        <Domain name="range" id="4192.Color.range"/>
      </Property>
      <Property name="ColorArrayName" id="4192.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="Lithology_type"/>
        <Domain name="array_list" id="4192.ColorArrayName.array_list">
          <String text="Lithology_type"/>
        </Domain>
        <Domain name="field_list" id="4192.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="4192.CubeAxesColor" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="1"/>
        <Element index="2" value="1"/>
        <Domain name="range" id="4192.CubeAxesColor.range"/>
      </Property>
      <Property name="CubeAxesCornerOffset" id="4192.CubeAxesCornerOffset" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="range" id="4192.CubeAxesCornerOffset.range"/>
      </Property>
      <Property name="CubeAxesFlyMode" id="4192.CubeAxesFlyMode" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="enum" id="4192.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="4192.CubeAxesGridLineLocation" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="enum" id="4192.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="4192.CubeAxesInertia" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="4192.CubeAxesInertia.range"/>
      </Property>
      <Property name="CubeAxesTickLocation" id="4192.CubeAxesTickLocation" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="enum" id="4192.CubeAxesTickLocation.enum">
          <Entry value="0" text="Inside"/>
          <Entry value="1" text="Outside"/>
          <Entry value="2" text="Both"/>
        </Domain>
      </Property>
      <Property name="CubeAxesUseDefaultXTitle" id="4192.CubeAxesUseDefaultXTitle" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="4192.CubeAxesUseDefaultXTitle.bool"/>
      </Property>
      <Property name="CubeAxesUseDefaultYTitle" id="4192.CubeAxesUseDefaultYTitle" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="4192.CubeAxesUseDefaultYTitle.bool"/>
      </Property>
      <Property name="CubeAxesUseDefaultZTitle" id="4192.CubeAxesUseDefaultZTitle" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="4192.CubeAxesUseDefaultZTitle.bool"/>
      </Property>
      <Property name="CubeAxesXAxisMinorTickVisibility" id="4192.CubeAxesXAxisMinorTickVisibility" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="4192.CubeAxesXAxisMinorTickVisibility.bool"/>
      </Property>
      <Property name="CubeAxesXAxisTickVisibility" id="4192.CubeAxesXAxisTickVisibility" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="4192.CubeAxesXAxisTickVisibility.bool"/>
      </Property>
      <Property name="CubeAxesXAxisVisibility" id="4192.CubeAxesXAxisVisibility" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="4192.CubeAxesXAxisVisibility.bool"/>
      </Property>
      <Property name="CubeAxesXGridLines" id="4192.CubeAxesXGridLines" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4192.CubeAxesXGridLines.bool"/>
      </Property>
      <Property name="CubeAxesXLabelFormat" id="4192.CubeAxesXLabelFormat" number_of_elements="1">
        <Element index="0" value="%-#6.3g"/>
      </Property>
      <Property name="CubeAxesXTitle" id="4192.CubeAxesXTitle" number_of_elements="1">
        <Element index="0" value="X-Axis"/>
      </Property>
      <Property name="CubeAxesYAxisMinorTickVisibility" id="4192.CubeAxesYAxisMinorTickVisibility" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="4192.CubeAxesYAxisMinorTickVisibility.bool"/>
      </Property>
      <Property name="CubeAxesYAxisTickVisibility" id="4192.CubeAxesYAxisTickVisibility" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="4192.CubeAxesYAxisTickVisibility.bool"/>
      </Property>
      <Property name="CubeAxesYAxisVisibility" id="4192.CubeAxesYAxisVisibility" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="4192.CubeAxesYAxisVisibility.bool"/>
      </Property>
      <Property name="CubeAxesYGridLines" id="4192.CubeAxesYGridLines" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4192.CubeAxesYGridLines.bool"/>
      </Property>
      <Property name="CubeAxesYLabelFormat" id="4192.CubeAxesYLabelFormat" number_of_elements="1">
        <Element index="0" value="%-#6.3g"/>
      </Property>
      <Property name="CubeAxesYTitle" id="4192.CubeAxesYTitle" number_of_elements="1">
        <Element index="0" value="Y-Axis"/>
      </Property>
      <Property name="CubeAxesZAxisMinorTickVisibility" id="4192.CubeAxesZAxisMinorTickVisibility" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="4192.CubeAxesZAxisMinorTickVisibility.bool"/>
      </Property>
      <Property name="CubeAxesZAxisTickVisibility" id="4192.CubeAxesZAxisTickVisibility" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="4192.CubeAxesZAxisTickVisibility.bool"/>
      </Property>
      <Property name="CubeAxesZAxisVisibility" id="4192.CubeAxesZAxisVisibility" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="4192.CubeAxesZAxisVisibility.bool"/>
      </Property>
      <Property name="CubeAxesZGridLines" id="4192.CubeAxesZGridLines" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4192.CubeAxesZGridLines.bool"/>
      </Property>
      <Property name="CubeAxesZLabelFormat" id="4192.CubeAxesZLabelFormat" number_of_elements="1">
        <Element index="0" value="%-#6.3g"/>
      </Property>
      <Property name="CubeAxesZTitle" id="4192.CubeAxesZTitle" number_of_elements="1">
        <Element index="0" value="Z-Axis"/>
      </Property>
      <Property name="CustomBounds" id="4192.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="4192.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="4192.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="4192.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="4192.CustomShader" number_of_elements="1">
        <Element index="0" value=""/>
      </Property>
      <Property name="DataBounds" id="4192.DataBounds" number_of_elements="6">
        <Element index="0" value="2.01035311292803e-320"/>
        <Element index="1" value="8.48798316731955e-314"/>
        <Element index="2" value="8.54239501659515e-321"/>
        <Element index="3" value="6.0147140662096e-316"/>
        <Element index="4" value="6.92589253794838e-310"/>
        <Element index="5" value="0"/>
      </Property>
      <Property name="Diffuse" id="4192.Diffuse" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="4192.Diffuse.range"/>
      </Property>
      <Property name="DiffuseColor" id="4192.DiffuseColor" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="1"/>
        <Element index="2" value="1"/>
        <Domain name="range" id="4192.DiffuseColor.range"/>
      </Property>
      <Property name="EdgeColor" id="4192.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="4192.EdgeColor.range"/>
      </Property>
      <Property name="Emissive" id="4192.Emissive" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4192.Emissive.bool"/>
      </Property>
      <Property name="GaussianRadius" id="4192.GaussianRadius" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="range" id="4192.GaussianRadius.range"/>
      </Property>
      <Property name="GlyphType" id="4192.GlyphType" number_of_elements="1">
        <Proxy value="4058" output_port="0"/>
        <Domain name="input_type" id="4192.GlyphType.input_type"/>
        <Domain name="proxy_list" id="4192.GlyphType.proxy_list">
          <Proxy value="4058"/>
          <Proxy value="4069"/>
          <Proxy value="4080"/>
          <Proxy value="4091"/>
          <Proxy value="4102"/>
          <Proxy value="4113"/>
          <Proxy value="4124"/>
        </Domain>
      </Property>
      <Property name="InterpolateScalarsBeforeMapping" id="4192.InterpolateScalarsBeforeMapping" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="4192.InterpolateScalarsBeforeMapping.bool"/>
      </Property>
      <Property name="Interpolation" id="4192.Interpolation" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="enum" id="4192.Interpolation.enum">
          <Entry value="0" text="Flat"/>
          <Entry value="1" text="Gouraud"/>
        </Domain>
      </Property>
      <Property name="LineWidth" id="4192.LineWidth" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="4192.LineWidth.range"/>
      </Property>
      <Property name="LookupTable" id="4192.LookupTable" number_of_elements="1">
        <Proxy value="3961"/>
        <Domain name="groups" id="4192.LookupTable.groups"/>
      </Property>
      <Property name="MapScalars" id="4192.MapScalars" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="4192.MapScalars.bool"/>
      </Property>
      <Property name="Masking" id="4192.Masking" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4192.Masking.bool"/>
      </Property>
      <Property name="MeshVisibility" id="4192.MeshVisibility" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4192.MeshVisibility.bool"/>
      </Property>
      <Property name="NonlinearSubdivisionLevel" id="4192.NonlinearSubdivisionLevel" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="4192.NonlinearSubdivisionLevel.range"/>
      </Property>
      <Property name="Opacity" id="4192.Opacity" number_of_elements="1">
        <Element index="0" value="0.99"/>
        <Domain name="range" id="4192.Opacity.range"/>
      </Property>
      <Property name="OpacityArray" id="4192.OpacityArray" 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="Lithology_type"/>
        <Domain name="array_list" id="4192.OpacityArray.array_list">
          <String text="Lithology_type"/>
        </Domain>
      </Property>
      <Property name="OpacityByArray" id="4192.OpacityByArray" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="4192.OpacityByArray.bool"/>
      </Property>
      <Property name="OpacityTransferFunction" id="4192.OpacityTransferFunction" number_of_elements="1">
        <Proxy value="4135"/>
        <Domain name="groups" id="4192.OpacityTransferFunction.groups"/>
        <Domain name="proxy_list" id="4192.OpacityTransferFunction.proxy_list">
          <Proxy value="4135"/>
        </Domain>
      </Property>
      <Property name="Orient" id="4192.Orient" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4192.Orient.bool"/>
      </Property>
      <Property name="Orientation" id="4192.Orientation" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="4192.Orientation.range"/>
      </Property>
      <Property name="OrientationMode" id="4192.OrientationMode" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="enum" id="4192.OrientationMode.enum">
          <Entry value="0" text="Direction"/>
          <Entry value="1" text="Rotation"/>
        </Domain>
      </Property>
      <Property name="Origin" id="4192.Origin" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="4192.Origin.range"/>
      </Property>
      <Property name="OriginalBoundsRangeActive" id="4192.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="4192.Pickable" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="4192.Pickable.bool"/>
      </Property>
      <Property name="PointSize" id="4192.PointSize" number_of_elements="1">
        <Element index="0" value="2"/>
        <Domain name="range" id="4192.PointSize.range"/>
      </Property>
      <Property name="Position" id="4192.Position" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="4192.Position.range"/>
      </Property>
      <Property name="Scale" id="4192.Scale" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="1"/>
        <Element index="2" value="1"/>
        <Domain name="range" id="4192.Scale.range"/>
      </Property>
      <Property name="ScaleByArray" id="4192.ScaleByArray" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4192.ScaleByArray.bool"/>
      </Property>
      <Property name="ScaleFactor" id="4192.ScaleFactor" number_of_elements="1">
        <Element index="0" value="5705.9720703125"/>
        <Domain name="bounds" id="4192.ScaleFactor.bounds"/>
        <Domain name="scalar_range" id="4192.ScaleFactor.scalar_range"/>
        <Domain name="vector_range" id="4192.ScaleFactor.vector_range"/>
      </Property>
      <Property name="ScaleMode" id="4192.ScaleMode" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="enum" id="4192.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="4192.ScaleTransferFunction" number_of_elements="1">
        <Proxy value="4136"/>
        <Domain name="groups" id="4192.ScaleTransferFunction.groups"/>
        <Domain name="proxy_list" id="4192.ScaleTransferFunction.proxy_list">
          <Proxy value="4136"/>
        </Domain>
      </Property>
      <Property name="Scaling" id="4192.Scaling" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4192.Scaling.bool"/>
      </Property>
      <Property name="SelectMaskArray" id="4192.SelectMaskArray" number_of_elements="1">
        <Element index="0" value=""/>
      </Property>
      <Property name="SelectOrientationVectors" id="4192.SelectOrientationVectors" number_of_elements="1">
        <Element index="0" value=""/>
      </Property>
      <Property name="SelectScaleArray" id="4192.SelectScaleArray" number_of_elements="1">
        <Element index="0" value=""/>
      </Property>
      <Property name="SelectionCellLabelBold" id="4192.SelectionCellLabelBold" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4192.SelectionCellLabelBold.bool"/>
      </Property>
      <Property name="SelectionCellLabelColor" id="4192.SelectionCellLabelColor" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="1"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="4192.SelectionCellLabelColor.range"/>
      </Property>
      <Property name="SelectionCellLabelFontFamily" id="4192.SelectionCellLabelFontFamily" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="enum" id="4192.SelectionCellLabelFontFamily.enum">
          <Entry value="0" text="Arial"/>
          <Entry value="1" text="Courier"/>
          <Entry value="2" text="Times"/>
        </Domain>
      </Property>
      <Property name="SelectionCellLabelFontSize" id="4192.SelectionCellLabelFontSize" number_of_elements="1">
        <Element index="0" value="18"/>
        <Domain name="range" id="4192.SelectionCellLabelFontSize.range"/>
      </Property>
      <Property name="SelectionCellLabelFormat" id="4192.SelectionCellLabelFormat" number_of_elements="1">
        <Element index="0" value=""/>
      </Property>
      <Property name="SelectionCellLabelItalic" id="4192.SelectionCellLabelItalic" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4192.SelectionCellLabelItalic.bool"/>
      </Property>
      <Property name="SelectionCellLabelJustification" id="4192.SelectionCellLabelJustification" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="enum" id="4192.SelectionCellLabelJustification.enum">
          <Entry value="0" text="Left"/>
          <Entry value="1" text="Center"/>
          <Entry value="2" text="Right"/>
        </Domain>
      </Property>
      <Property name="SelectionCellLabelOpacity" id="4192.SelectionCellLabelOpacity" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="4192.SelectionCellLabelOpacity.range"/>
      </Property>
      <Property name="SelectionCellLabelShadow" id="4192.SelectionCellLabelShadow" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4192.SelectionCellLabelShadow.bool"/>
      </Property>
      <Property name="SelectionCellLabelVisibility" id="4192.SelectionCellLabelVisibility" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4192.SelectionCellLabelVisibility.bool"/>
      </Property>
      <Property name="SelectionColor" id="4192.SelectionColor" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="0"/>
        <Element index="2" value="1"/>
        <Domain name="range" id="4192.SelectionColor.range"/>
      </Property>
      <Property name="SelectionLineWidth" id="4192.SelectionLineWidth" number_of_elements="1">
        <Element index="0" value="2"/>
        <Domain name="range" id="4192.SelectionLineWidth.range"/>
      </Property>
      <Property name="SelectionOpacity" id="4192.SelectionOpacity" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="4192.SelectionOpacity.range"/>
      </Property>
      <Property name="SelectionPointLabelBold" id="4192.SelectionPointLabelBold" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4192.SelectionPointLabelBold.bool"/>
      </Property>
      <Property name="SelectionPointLabelColor" id="4192.SelectionPointLabelColor" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="1"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="4192.SelectionPointLabelColor.range"/>
      </Property>
      <Property name="SelectionPointLabelFontFamily" id="4192.SelectionPointLabelFontFamily" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="enum" id="4192.SelectionPointLabelFontFamily.enum">
          <Entry value="0" text="Arial"/>
          <Entry value="1" text="Courier"/>
          <Entry value="2" text="Times"/>
        </Domain>
      </Property>
      <Property name="SelectionPointLabelFontSize" id="4192.SelectionPointLabelFontSize" number_of_elements="1">
        <Element index="0" value="18"/>
        <Domain name="range" id="4192.SelectionPointLabelFontSize.range"/>
      </Property>
      <Property name="SelectionPointLabelFormat" id="4192.SelectionPointLabelFormat" number_of_elements="1">
        <Element index="0" value=""/>
      </Property>
      <Property name="SelectionPointLabelItalic" id="4192.SelectionPointLabelItalic" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4192.SelectionPointLabelItalic.bool"/>
      </Property>
      <Property name="SelectionPointLabelJustification" id="4192.SelectionPointLabelJustification" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="enum" id="4192.SelectionPointLabelJustification.enum">
          <Entry value="0" text="Left"/>
          <Entry value="1" text="Center"/>
          <Entry value="2" text="Right"/>
        </Domain>
      </Property>
      <Property name="SelectionPointLabelOpacity" id="4192.SelectionPointLabelOpacity" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="4192.SelectionPointLabelOpacity.range"/>
      </Property>
      <Property name="SelectionPointLabelShadow" id="4192.SelectionPointLabelShadow" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4192.SelectionPointLabelShadow.bool"/>
      </Property>
      <Property name="SelectionPointLabelVisibility" id="4192.SelectionPointLabelVisibility" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4192.SelectionPointLabelVisibility.bool"/>
      </Property>
      <Property name="SelectionPointSize" id="4192.SelectionPointSize" number_of_elements="1">
        <Element index="0" value="5"/>
        <Domain name="range" id="4192.SelectionPointSize.range"/>
      </Property>
      <Property name="SelectionRepresentation" id="4192.SelectionRepresentation" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="enum" id="4192.SelectionRepresentation.enum">
          <Entry value="0" text="Points"/>
          <Entry value="1" text="Wireframe"/>
          <Entry value="2" text="Surface"/>
        </Domain>
      </Property>
      <Property name="SelectionUseOutline" id="4192.SelectionUseOutline" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4192.SelectionUseOutline.bool"/>
      </Property>
      <Property name="SetScaleArray" id="4192.SetScaleArray" 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="Lithology_type"/>
        <Domain name="array_list" id="4192.SetScaleArray.array_list">
          <String text="Lithology_type"/>
        </Domain>
      </Property>
      <Property name="ShaderPreset" id="4192.ShaderPreset" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="enum" id="4192.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="4192.Specular" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="range" id="4192.Specular.range"/>
      </Property>
      <Property name="SpecularColor" id="4192.SpecularColor" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="1"/>
        <Element index="2" value="1"/>
        <Domain name="range" id="4192.SpecularColor.range"/>
      </Property>
      <Property name="SpecularPower" id="4192.SpecularPower" number_of_elements="1">
        <Element index="0" value="100"/>
        <Domain name="range" id="4192.SpecularPower.range"/>
      </Property>
      <Property name="StaticMode" id="4192.StaticMode" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4192.StaticMode.bool"/>
      </Property>
      <Property name="StickyAxes" id="4192.StickyAxes" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4192.StickyAxes.bool"/>
      </Property>
      <Property name="SuppressLOD" id="4192.SuppressLOD" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4192.SuppressLOD.bool"/>
      </Property>
      <Property name="Texture" id="4192.Texture">
        <Domain name="groups" id="4192.Texture.groups"/>
      </Property>
      <Property name="Triangulate" id="4192.Triangulate" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4192.Triangulate.bool"/>
      </Property>
      <Property name="UseAxesOrigin" id="4192.UseAxesOrigin" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4192.UseAxesOrigin.bool"/>
      </Property>
      <Property name="UserTransform" id="4192.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="4359" servers="21">
      <Property name="CubeAxesVisibility" id="4359.CubeAxesVisibility" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="4359.CubeAxesVisibility.bool"/>
      </Property>
      <Property name="Input" id="4359.Input" number_of_elements="1">
        <Proxy value="3813" output_port="0"/>
        <Domain name="input_array_cell" id="4359.Input.input_array_cell"/>
        <Domain name="input_array_point" id="4359.Input.input_array_point"/>
        <Domain name="input_type" id="4359.Input.input_type"/>
      </Property>
      <Property name="Representation" id="4359.Representation" number_of_elements="1">
        <Element index="0" value="Surface"/>
        <Domain name="list" id="4359.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="4359.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="4359.SelectionCellFieldDataArrayName" number_of_elements="1">
        <Element index="0" value="Lithology_type"/>
        <Domain name="array_list" id="4359.SelectionCellFieldDataArrayName.array_list">
          <String text="Lithology_type"/>
        </Domain>
      </Property>
      <Property name="SelectionPointFieldDataArrayName" id="4359.SelectionPointFieldDataArrayName" number_of_elements="1">
        <Element index="0" value="Lithology_type"/>
        <Domain name="array_list" id="4359.SelectionPointFieldDataArrayName.array_list">
          <String text="Lithology_type"/>
        </Domain>
      </Property>
      <Property name="SelectionVisibility" id="4359.SelectionVisibility" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="4359.SelectionVisibility.bool"/>
      </Property>
      <Property name="Visibility" id="4359.Visibility" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="4359.Visibility.bool"/>
      </Property>
      <Property name="Ambient" id="4359.Ambient" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="range" id="4359.Ambient.range"/>
      </Property>
      <Property name="AmbientColor" id="4359.AmbientColor" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="1"/>
        <Element index="2" value="1"/>
        <Domain name="range" id="4359.AmbientColor.range"/>
      </Property>
      <Property name="AxesOrigin" id="4359.AxesOrigin" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="4359.AxesOrigin.range"/>
      </Property>
      <Property name="BackfaceAmbientColor" id="4359.BackfaceAmbientColor" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="1"/>
        <Element index="2" value="1"/>
        <Domain name="range" id="4359.BackfaceAmbientColor.range"/>
      </Property>
      <Property name="BackfaceDiffuseColor" id="4359.BackfaceDiffuseColor" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="1"/>
        <Element index="2" value="1"/>
        <Domain name="range" id="4359.BackfaceDiffuseColor.range"/>
      </Property>
      <Property name="BackfaceOpacity" id="4359.BackfaceOpacity" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="4359.BackfaceOpacity.range"/>
      </Property>
      <Property name="BackfaceRepresentation" id="4359.BackfaceRepresentation" number_of_elements="1">
        <Element index="0" value="400"/>
        <Domain name="enum" id="4359.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="4359.BlockColor"/>
      <Property name="BlockColorsDistinctValues" id="4359.BlockColorsDistinctValues" number_of_elements="1">
        <Element index="0" value="12"/>
        <Domain name="range" id="4359.BlockColorsDistinctValues.range"/>
      </Property>
      <Property name="BlockOpacity" id="4359.BlockOpacity"/>
      <Property name="BlockVisibility" id="4359.BlockVisibility"/>
      <Property name="CenterStickyAxes" id="4359.CenterStickyAxes" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4359.CenterStickyAxes.bool"/>
      </Property>
      <Property name="Color" id="4359.Color" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="1"/>
        <Element index="2" value="1"/>
        <Domain name="range" id="4359.Color.range"/>
      </Property>
      <Property name="ColorArrayName" id="4359.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="Lithology_type"/>
        <Domain name="array_list" id="4359.ColorArrayName.array_list">
          <String text="Lithology_type"/>
        </Domain>
        <Domain name="field_list" id="4359.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="4359.CubeAxesColor" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="1"/>
        <Element index="2" value="1"/>
        <Domain name="range" id="4359.CubeAxesColor.range"/>
      </Property>
      <Property name="CubeAxesCornerOffset" id="4359.CubeAxesCornerOffset" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="range" id="4359.CubeAxesCornerOffset.range"/>
      </Property>
      <Property name="CubeAxesFlyMode" id="4359.CubeAxesFlyMode" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="enum" id="4359.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="4359.CubeAxesGridLineLocation" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="enum" id="4359.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="4359.CubeAxesInertia" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="4359.CubeAxesInertia.range"/>
      </Property>
      <Property name="CubeAxesTickLocation" id="4359.CubeAxesTickLocation" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="enum" id="4359.CubeAxesTickLocation.enum">
          <Entry value="0" text="Inside"/>
          <Entry value="1" text="Outside"/>
          <Entry value="2" text="Both"/>
        </Domain>
      </Property>
      <Property name="CubeAxesUseDefaultXTitle" id="4359.CubeAxesUseDefaultXTitle" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="4359.CubeAxesUseDefaultXTitle.bool"/>
      </Property>
      <Property name="CubeAxesUseDefaultYTitle" id="4359.CubeAxesUseDefaultYTitle" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="4359.CubeAxesUseDefaultYTitle.bool"/>
      </Property>
      <Property name="CubeAxesUseDefaultZTitle" id="4359.CubeAxesUseDefaultZTitle" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="4359.CubeAxesUseDefaultZTitle.bool"/>
      </Property>
      <Property name="CubeAxesXAxisMinorTickVisibility" id="4359.CubeAxesXAxisMinorTickVisibility" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="4359.CubeAxesXAxisMinorTickVisibility.bool"/>
      </Property>
      <Property name="CubeAxesXAxisTickVisibility" id="4359.CubeAxesXAxisTickVisibility" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="4359.CubeAxesXAxisTickVisibility.bool"/>
      </Property>
      <Property name="CubeAxesXAxisVisibility" id="4359.CubeAxesXAxisVisibility" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="4359.CubeAxesXAxisVisibility.bool"/>
      </Property>
      <Property name="CubeAxesXGridLines" id="4359.CubeAxesXGridLines" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4359.CubeAxesXGridLines.bool"/>
      </Property>
      <Property name="CubeAxesXLabelFormat" id="4359.CubeAxesXLabelFormat" number_of_elements="1">
        <Element index="0" value="%-#6.3g"/>
      </Property>
      <Property name="CubeAxesXTitle" id="4359.CubeAxesXTitle" number_of_elements="1">
        <Element index="0" value="X-Axis"/>
      </Property>
      <Property name="CubeAxesYAxisMinorTickVisibility" id="4359.CubeAxesYAxisMinorTickVisibility" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="4359.CubeAxesYAxisMinorTickVisibility.bool"/>
      </Property>
      <Property name="CubeAxesYAxisTickVisibility" id="4359.CubeAxesYAxisTickVisibility" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="4359.CubeAxesYAxisTickVisibility.bool"/>
      </Property>
      <Property name="CubeAxesYAxisVisibility" id="4359.CubeAxesYAxisVisibility" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="4359.CubeAxesYAxisVisibility.bool"/>
      </Property>
      <Property name="CubeAxesYGridLines" id="4359.CubeAxesYGridLines" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4359.CubeAxesYGridLines.bool"/>
      </Property>
      <Property name="CubeAxesYLabelFormat" id="4359.CubeAxesYLabelFormat" number_of_elements="1">
        <Element index="0" value="%-#6.3g"/>
      </Property>
      <Property name="CubeAxesYTitle" id="4359.CubeAxesYTitle" number_of_elements="1">
        <Element index="0" value="Y-Axis"/>
      </Property>
      <Property name="CubeAxesZAxisMinorTickVisibility" id="4359.CubeAxesZAxisMinorTickVisibility" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="4359.CubeAxesZAxisMinorTickVisibility.bool"/>
      </Property>
      <Property name="CubeAxesZAxisTickVisibility" id="4359.CubeAxesZAxisTickVisibility" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="4359.CubeAxesZAxisTickVisibility.bool"/>
      </Property>
      <Property name="CubeAxesZAxisVisibility" id="4359.CubeAxesZAxisVisibility" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="4359.CubeAxesZAxisVisibility.bool"/>
      </Property>
      <Property name="CubeAxesZGridLines" id="4359.CubeAxesZGridLines" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4359.CubeAxesZGridLines.bool"/>
      </Property>
      <Property name="CubeAxesZLabelFormat" id="4359.CubeAxesZLabelFormat" number_of_elements="1">
        <Element index="0" value="%-#6.3g"/>
      </Property>
      <Property name="CubeAxesZTitle" id="4359.CubeAxesZTitle" number_of_elements="1">
        <Element index="0" value="Z-Axis"/>
      </Property>
      <Property name="CustomBounds" id="4359.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="4359.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="4359.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="4359.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="4359.CustomShader" number_of_elements="1">
        <Element index="0" value=""/>
      </Property>
      <Property name="DataBounds" id="4359.DataBounds" number_of_elements="6">
        <Element index="0" value="6.92589253794838e-310"/>
        <Element index="1" value="6.29197542838632e+233"/>
        <Element index="2" value="4.99006302299659e-322"/>
        <Element index="3" value="7.11454530011395e-322"/>
        <Element index="4" value="3.16202013338398e-322"/>
        <Element index="5" value="6.40457533855518e-316"/>
      </Property>
      <Property name="Diffuse" id="4359.Diffuse" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="4359.Diffuse.range"/>
      </Property>
      <Property name="DiffuseColor" id="4359.DiffuseColor" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="1"/>
        <Element index="2" value="1"/>
        <Domain name="range" id="4359.DiffuseColor.range"/>
      </Property>
      <Property name="EdgeColor" id="4359.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="4359.EdgeColor.range"/>
      </Property>
      <Property name="Emissive" id="4359.Emissive" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4359.Emissive.bool"/>
      </Property>
      <Property name="GaussianRadius" id="4359.GaussianRadius" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="range" id="4359.GaussianRadius.range"/>
      </Property>
      <Property name="GlyphType" id="4359.GlyphType" number_of_elements="1">
        <Proxy value="4225" output_port="0"/>
        <Domain name="input_type" id="4359.GlyphType.input_type"/>
        <Domain name="proxy_list" id="4359.GlyphType.proxy_list">
          <Proxy value="4225"/>
          <Proxy value="4236"/>
          <Proxy value="4247"/>
          <Proxy value="4258"/>
          <Proxy value="4269"/>
          <Proxy value="4280"/>
          <Proxy value="4291"/>
        </Domain>
      </Property>
      <Property name="InterpolateScalarsBeforeMapping" id="4359.InterpolateScalarsBeforeMapping" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="4359.InterpolateScalarsBeforeMapping.bool"/>
      </Property>
      <Property name="Interpolation" id="4359.Interpolation" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="enum" id="4359.Interpolation.enum">
          <Entry value="0" text="Flat"/>
          <Entry value="1" text="Gouraud"/>
        </Domain>
      </Property>
      <Property name="LineWidth" id="4359.LineWidth" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="4359.LineWidth.range"/>
      </Property>
      <Property name="LookupTable" id="4359.LookupTable" number_of_elements="1">
        <Proxy value="3961"/>
        <Domain name="groups" id="4359.LookupTable.groups"/>
      </Property>
      <Property name="MapScalars" id="4359.MapScalars" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="4359.MapScalars.bool"/>
      </Property>
      <Property name="Masking" id="4359.Masking" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4359.Masking.bool"/>
      </Property>
      <Property name="MeshVisibility" id="4359.MeshVisibility" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4359.MeshVisibility.bool"/>
      </Property>
      <Property name="NonlinearSubdivisionLevel" id="4359.NonlinearSubdivisionLevel" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="4359.NonlinearSubdivisionLevel.range"/>
      </Property>
      <Property name="Opacity" id="4359.Opacity" number_of_elements="1">
        <Element index="0" value="0.99"/>
        <Domain name="range" id="4359.Opacity.range"/>
      </Property>
      <Property name="OpacityArray" id="4359.OpacityArray" 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="Lithology_type"/>
        <Domain name="array_list" id="4359.OpacityArray.array_list">
          <String text="Lithology_type"/>
        </Domain>
      </Property>
      <Property name="OpacityByArray" id="4359.OpacityByArray" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="4359.OpacityByArray.bool"/>
      </Property>
      <Property name="OpacityTransferFunction" id="4359.OpacityTransferFunction" number_of_elements="1">
        <Proxy value="4302"/>
        <Domain name="groups" id="4359.OpacityTransferFunction.groups"/>
        <Domain name="proxy_list" id="4359.OpacityTransferFunction.proxy_list">
          <Proxy value="4302"/>
        </Domain>
      </Property>
      <Property name="Orient" id="4359.Orient" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4359.Orient.bool"/>
      </Property>
      <Property name="Orientation" id="4359.Orientation" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="4359.Orientation.range"/>
      </Property>
      <Property name="OrientationMode" id="4359.OrientationMode" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="enum" id="4359.OrientationMode.enum">
          <Entry value="0" text="Direction"/>
          <Entry value="1" text="Rotation"/>
        </Domain>
      </Property>
      <Property name="Origin" id="4359.Origin" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="4359.Origin.range"/>
      </Property>
      <Property name="OriginalBoundsRangeActive" id="4359.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="4359.Pickable" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="4359.Pickable.bool"/>
      </Property>
      <Property name="PointSize" id="4359.PointSize" number_of_elements="1">
        <Element index="0" value="2"/>
        <Domain name="range" id="4359.PointSize.range"/>
      </Property>
      <Property name="Position" id="4359.Position" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="4359.Position.range"/>
      </Property>
      <Property name="Scale" id="4359.Scale" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="1"/>
        <Element index="2" value="1"/>
        <Domain name="range" id="4359.Scale.range"/>
      </Property>
      <Property name="ScaleByArray" id="4359.ScaleByArray" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4359.ScaleByArray.bool"/>
      </Property>
      <Property name="ScaleFactor" id="4359.ScaleFactor" number_of_elements="1">
        <Element index="0" value="6632.251171875"/>
        <Domain name="bounds" id="4359.ScaleFactor.bounds"/>
        <Domain name="scalar_range" id="4359.ScaleFactor.scalar_range"/>
        <Domain name="vector_range" id="4359.ScaleFactor.vector_range"/>
      </Property>
      <Property name="ScaleMode" id="4359.ScaleMode" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="enum" id="4359.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="4359.ScaleTransferFunction" number_of_elements="1">
        <Proxy value="4303"/>
        <Domain name="groups" id="4359.ScaleTransferFunction.groups"/>
        <Domain name="proxy_list" id="4359.ScaleTransferFunction.proxy_list">
          <Proxy value="4303"/>
        </Domain>
      </Property>
      <Property name="Scaling" id="4359.Scaling" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4359.Scaling.bool"/>
      </Property>
      <Property name="SelectMaskArray" id="4359.SelectMaskArray" number_of_elements="1">
        <Element index="0" value=""/>
      </Property>
      <Property name="SelectOrientationVectors" id="4359.SelectOrientationVectors" number_of_elements="1">
        <Element index="0" value=""/>
      </Property>
      <Property name="SelectScaleArray" id="4359.SelectScaleArray" number_of_elements="1">
        <Element index="0" value=""/>
      </Property>
      <Property name="SelectionCellLabelBold" id="4359.SelectionCellLabelBold" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4359.SelectionCellLabelBold.bool"/>
      </Property>
      <Property name="SelectionCellLabelColor" id="4359.SelectionCellLabelColor" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="1"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="4359.SelectionCellLabelColor.range"/>
      </Property>
      <Property name="SelectionCellLabelFontFamily" id="4359.SelectionCellLabelFontFamily" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="enum" id="4359.SelectionCellLabelFontFamily.enum">
          <Entry value="0" text="Arial"/>
          <Entry value="1" text="Courier"/>
          <Entry value="2" text="Times"/>
        </Domain>
      </Property>
      <Property name="SelectionCellLabelFontSize" id="4359.SelectionCellLabelFontSize" number_of_elements="1">
        <Element index="0" value="18"/>
        <Domain name="range" id="4359.SelectionCellLabelFontSize.range"/>
      </Property>
      <Property name="SelectionCellLabelFormat" id="4359.SelectionCellLabelFormat" number_of_elements="1">
        <Element index="0" value=""/>
      </Property>
      <Property name="SelectionCellLabelItalic" id="4359.SelectionCellLabelItalic" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4359.SelectionCellLabelItalic.bool"/>
      </Property>
      <Property name="SelectionCellLabelJustification" id="4359.SelectionCellLabelJustification" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="enum" id="4359.SelectionCellLabelJustification.enum">
          <Entry value="0" text="Left"/>
          <Entry value="1" text="Center"/>
          <Entry value="2" text="Right"/>
        </Domain>
      </Property>
      <Property name="SelectionCellLabelOpacity" id="4359.SelectionCellLabelOpacity" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="4359.SelectionCellLabelOpacity.range"/>
      </Property>
      <Property name="SelectionCellLabelShadow" id="4359.SelectionCellLabelShadow" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4359.SelectionCellLabelShadow.bool"/>
      </Property>
      <Property name="SelectionCellLabelVisibility" id="4359.SelectionCellLabelVisibility" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4359.SelectionCellLabelVisibility.bool"/>
      </Property>
      <Property name="SelectionColor" id="4359.SelectionColor" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="0"/>
        <Element index="2" value="1"/>
        <Domain name="range" id="4359.SelectionColor.range"/>
      </Property>
      <Property name="SelectionLineWidth" id="4359.SelectionLineWidth" number_of_elements="1">
        <Element index="0" value="2"/>
        <Domain name="range" id="4359.SelectionLineWidth.range"/>
      </Property>
      <Property name="SelectionOpacity" id="4359.SelectionOpacity" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="4359.SelectionOpacity.range"/>
      </Property>
      <Property name="SelectionPointLabelBold" id="4359.SelectionPointLabelBold" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4359.SelectionPointLabelBold.bool"/>
      </Property>
      <Property name="SelectionPointLabelColor" id="4359.SelectionPointLabelColor" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="1"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="4359.SelectionPointLabelColor.range"/>
      </Property>
      <Property name="SelectionPointLabelFontFamily" id="4359.SelectionPointLabelFontFamily" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="enum" id="4359.SelectionPointLabelFontFamily.enum">
          <Entry value="0" text="Arial"/>
          <Entry value="1" text="Courier"/>
          <Entry value="2" text="Times"/>
        </Domain>
      </Property>
      <Property name="SelectionPointLabelFontSize" id="4359.SelectionPointLabelFontSize" number_of_elements="1">
        <Element index="0" value="18"/>
        <Domain name="range" id="4359.SelectionPointLabelFontSize.range"/>
      </Property>
      <Property name="SelectionPointLabelFormat" id="4359.SelectionPointLabelFormat" number_of_elements="1">
        <Element index="0" value=""/>
      </Property>
      <Property name="SelectionPointLabelItalic" id="4359.SelectionPointLabelItalic" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4359.SelectionPointLabelItalic.bool"/>
      </Property>
      <Property name="SelectionPointLabelJustification" id="4359.SelectionPointLabelJustification" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="enum" id="4359.SelectionPointLabelJustification.enum">
          <Entry value="0" text="Left"/>
          <Entry value="1" text="Center"/>
          <Entry value="2" text="Right"/>
        </Domain>
      </Property>
      <Property name="SelectionPointLabelOpacity" id="4359.SelectionPointLabelOpacity" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="4359.SelectionPointLabelOpacity.range"/>
      </Property>
      <Property name="SelectionPointLabelShadow" id="4359.SelectionPointLabelShadow" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4359.SelectionPointLabelShadow.bool"/>
      </Property>
      <Property name="SelectionPointLabelVisibility" id="4359.SelectionPointLabelVisibility" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4359.SelectionPointLabelVisibility.bool"/>
      </Property>
      <Property name="SelectionPointSize" id="4359.SelectionPointSize" number_of_elements="1">
        <Element index="0" value="5"/>
        <Domain name="range" id="4359.SelectionPointSize.range"/>
      </Property>
      <Property name="SelectionRepresentation" id="4359.SelectionRepresentation" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="enum" id="4359.SelectionRepresentation.enum">
          <Entry value="0" text="Points"/>
          <Entry value="1" text="Wireframe"/>
          <Entry value="2" text="Surface"/>
        </Domain>
      </Property>
      <Property name="SelectionUseOutline" id="4359.SelectionUseOutline" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4359.SelectionUseOutline.bool"/>
      </Property>
      <Property name="SetScaleArray" id="4359.SetScaleArray" 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="Lithology_type"/>
        <Domain name="array_list" id="4359.SetScaleArray.array_list">
          <String text="Lithology_type"/>
        </Domain>
      </Property>
      <Property name="ShaderPreset" id="4359.ShaderPreset" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="enum" id="4359.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="4359.Specular" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="range" id="4359.Specular.range"/>
      </Property>
      <Property name="SpecularColor" id="4359.SpecularColor" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="1"/>
        <Element index="2" value="1"/>
        <Domain name="range" id="4359.SpecularColor.range"/>
      </Property>
      <Property name="SpecularPower" id="4359.SpecularPower" number_of_elements="1">
        <Element index="0" value="100"/>
        <Domain name="range" id="4359.SpecularPower.range"/>
      </Property>
      <Property name="StaticMode" id="4359.StaticMode" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4359.StaticMode.bool"/>
      </Property>
      <Property name="StickyAxes" id="4359.StickyAxes" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4359.StickyAxes.bool"/>
      </Property>
      <Property name="SuppressLOD" id="4359.SuppressLOD" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4359.SuppressLOD.bool"/>
      </Property>
      <Property name="Texture" id="4359.Texture">
        <Domain name="groups" id="4359.Texture.groups"/>
      </Property>
      <Property name="Triangulate" id="4359.Triangulate" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4359.Triangulate.bool"/>
      </Property>
      <Property name="UseAxesOrigin" id="4359.UseAxesOrigin" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4359.UseAxesOrigin.bool"/>
      </Property>
      <Property name="UserTransform" id="4359.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="4693" servers="21">
      <Property name="CubeAxesVisibility" id="4693.CubeAxesVisibility" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="4693.CubeAxesVisibility.bool"/>
      </Property>
      <Property name="Input" id="4693.Input" number_of_elements="1">
        <Proxy value="3842" output_port="0"/>
        <Domain name="input_array_cell" id="4693.Input.input_array_cell"/>
        <Domain name="input_array_point" id="4693.Input.input_array_point"/>
        <Domain name="input_type" id="4693.Input.input_type"/>
      </Property>
      <Property name="Representation" id="4693.Representation" number_of_elements="1">
        <Element index="0" value="Surface"/>
        <Domain name="list" id="4693.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="4693.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="4693.SelectionCellFieldDataArrayName" number_of_elements="1">
        <Element index="0" value="Lithology_type"/>
        <Domain name="array_list" id="4693.SelectionCellFieldDataArrayName.array_list">
          <String text="Lithology_type"/>
        </Domain>
      </Property>
      <Property name="SelectionPointFieldDataArrayName" id="4693.SelectionPointFieldDataArrayName" number_of_elements="1">
        <Element index="0" value="Lithology_type"/>
        <Domain name="array_list" id="4693.SelectionPointFieldDataArrayName.array_list">
          <String text="Lithology_type"/>
        </Domain>
      </Property>
      <Property name="SelectionVisibility" id="4693.SelectionVisibility" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="4693.SelectionVisibility.bool"/>
      </Property>
      <Property name="Visibility" id="4693.Visibility" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="4693.Visibility.bool"/>
      </Property>
      <Property name="Ambient" id="4693.Ambient" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="range" id="4693.Ambient.range"/>
      </Property>
      <Property name="AmbientColor" id="4693.AmbientColor" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="1"/>
        <Element index="2" value="1"/>
        <Domain name="range" id="4693.AmbientColor.range"/>
      </Property>
      <Property name="AxesOrigin" id="4693.AxesOrigin" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="4693.AxesOrigin.range"/>
      </Property>
      <Property name="BackfaceAmbientColor" id="4693.BackfaceAmbientColor" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="1"/>
        <Element index="2" value="1"/>
        <Domain name="range" id="4693.BackfaceAmbientColor.range"/>
      </Property>
      <Property name="BackfaceDiffuseColor" id="4693.BackfaceDiffuseColor" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="1"/>
        <Element index="2" value="1"/>
        <Domain name="range" id="4693.BackfaceDiffuseColor.range"/>
      </Property>
      <Property name="BackfaceOpacity" id="4693.BackfaceOpacity" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="4693.BackfaceOpacity.range"/>
      </Property>
      <Property name="BackfaceRepresentation" id="4693.BackfaceRepresentation" number_of_elements="1">
        <Element index="0" value="400"/>
        <Domain name="enum" id="4693.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="4693.BlockColor"/>
      <Property name="BlockColorsDistinctValues" id="4693.BlockColorsDistinctValues" number_of_elements="1">
        <Element index="0" value="12"/>
        <Domain name="range" id="4693.BlockColorsDistinctValues.range"/>
      </Property>
      <Property name="BlockOpacity" id="4693.BlockOpacity"/>
      <Property name="BlockVisibility" id="4693.BlockVisibility"/>
      <Property name="CenterStickyAxes" id="4693.CenterStickyAxes" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4693.CenterStickyAxes.bool"/>
      </Property>
      <Property name="Color" id="4693.Color" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="1"/>
        <Element index="2" value="1"/>
        <Domain name="range" id="4693.Color.range"/>
      </Property>
      <Property name="ColorArrayName" id="4693.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="Lithology_type"/>
        <Domain name="array_list" id="4693.ColorArrayName.array_list">
          <String text="Lithology_type"/>
        </Domain>
        <Domain name="field_list" id="4693.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="4693.CubeAxesColor" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="1"/>
        <Element index="2" value="1"/>
        <Domain name="range" id="4693.CubeAxesColor.range"/>
      </Property>
      <Property name="CubeAxesCornerOffset" id="4693.CubeAxesCornerOffset" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="range" id="4693.CubeAxesCornerOffset.range"/>
      </Property>
      <Property name="CubeAxesFlyMode" id="4693.CubeAxesFlyMode" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="enum" id="4693.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="4693.CubeAxesGridLineLocation" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="enum" id="4693.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="4693.CubeAxesInertia" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="4693.CubeAxesInertia.range"/>
      </Property>
      <Property name="CubeAxesTickLocation" id="4693.CubeAxesTickLocation" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="enum" id="4693.CubeAxesTickLocation.enum">
          <Entry value="0" text="Inside"/>
          <Entry value="1" text="Outside"/>
          <Entry value="2" text="Both"/>
        </Domain>
      </Property>
      <Property name="CubeAxesUseDefaultXTitle" id="4693.CubeAxesUseDefaultXTitle" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="4693.CubeAxesUseDefaultXTitle.bool"/>
      </Property>
      <Property name="CubeAxesUseDefaultYTitle" id="4693.CubeAxesUseDefaultYTitle" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="4693.CubeAxesUseDefaultYTitle.bool"/>
      </Property>
      <Property name="CubeAxesUseDefaultZTitle" id="4693.CubeAxesUseDefaultZTitle" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="4693.CubeAxesUseDefaultZTitle.bool"/>
      </Property>
      <Property name="CubeAxesXAxisMinorTickVisibility" id="4693.CubeAxesXAxisMinorTickVisibility" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="4693.CubeAxesXAxisMinorTickVisibility.bool"/>
      </Property>
      <Property name="CubeAxesXAxisTickVisibility" id="4693.CubeAxesXAxisTickVisibility" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="4693.CubeAxesXAxisTickVisibility.bool"/>
      </Property>
      <Property name="CubeAxesXAxisVisibility" id="4693.CubeAxesXAxisVisibility" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="4693.CubeAxesXAxisVisibility.bool"/>
      </Property>
      <Property name="CubeAxesXGridLines" id="4693.CubeAxesXGridLines" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4693.CubeAxesXGridLines.bool"/>
      </Property>
      <Property name="CubeAxesXLabelFormat" id="4693.CubeAxesXLabelFormat" number_of_elements="1">
        <Element index="0" value="%-#6.3g"/>
      </Property>
      <Property name="CubeAxesXTitle" id="4693.CubeAxesXTitle" number_of_elements="1">
        <Element index="0" value="X-Axis"/>
      </Property>
      <Property name="CubeAxesYAxisMinorTickVisibility" id="4693.CubeAxesYAxisMinorTickVisibility" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="4693.CubeAxesYAxisMinorTickVisibility.bool"/>
      </Property>
      <Property name="CubeAxesYAxisTickVisibility" id="4693.CubeAxesYAxisTickVisibility" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="4693.CubeAxesYAxisTickVisibility.bool"/>
      </Property>
      <Property name="CubeAxesYAxisVisibility" id="4693.CubeAxesYAxisVisibility" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="4693.CubeAxesYAxisVisibility.bool"/>
      </Property>
      <Property name="CubeAxesYGridLines" id="4693.CubeAxesYGridLines" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4693.CubeAxesYGridLines.bool"/>
      </Property>
      <Property name="CubeAxesYLabelFormat" id="4693.CubeAxesYLabelFormat" number_of_elements="1">
        <Element index="0" value="%-#6.3g"/>
      </Property>
      <Property name="CubeAxesYTitle" id="4693.CubeAxesYTitle" number_of_elements="1">
        <Element index="0" value="Y-Axis"/>
      </Property>
      <Property name="CubeAxesZAxisMinorTickVisibility" id="4693.CubeAxesZAxisMinorTickVisibility" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="4693.CubeAxesZAxisMinorTickVisibility.bool"/>
      </Property>
      <Property name="CubeAxesZAxisTickVisibility" id="4693.CubeAxesZAxisTickVisibility" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="4693.CubeAxesZAxisTickVisibility.bool"/>
      </Property>
      <Property name="CubeAxesZAxisVisibility" id="4693.CubeAxesZAxisVisibility" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="4693.CubeAxesZAxisVisibility.bool"/>
      </Property>
      <Property name="CubeAxesZGridLines" id="4693.CubeAxesZGridLines" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4693.CubeAxesZGridLines.bool"/>
      </Property>
      <Property name="CubeAxesZLabelFormat" id="4693.CubeAxesZLabelFormat" number_of_elements="1">
        <Element index="0" value="%-#6.3g"/>
      </Property>
      <Property name="CubeAxesZTitle" id="4693.CubeAxesZTitle" number_of_elements="1">
        <Element index="0" value="Z-Axis"/>
      </Property>
      <Property name="CustomBounds" id="4693.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="4693.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="4693.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="4693.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="4693.CustomShader" number_of_elements="1">
        <Element index="0" value=""/>
      </Property>
      <Property name="DataBounds" id="4693.DataBounds" number_of_elements="6">
        <Element index="0" value="3.16202013338398e-322"/>
        <Element index="1" value="6.78636713552036e-316"/>
        <Element index="2" value="0"/>
        <Element index="3" value="2.61854792295861e-322"/>
        <Element index="4" value="6.78638136461096e-316"/>
        <Element index="5" value="6.78638610764116e-316"/>
      </Property>
      <Property name="Diffuse" id="4693.Diffuse" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="4693.Diffuse.range"/>
      </Property>
      <Property name="DiffuseColor" id="4693.DiffuseColor" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="1"/>
        <Element index="2" value="1"/>
        <Domain name="range" id="4693.DiffuseColor.range"/>
      </Property>
      <Property name="EdgeColor" id="4693.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="4693.EdgeColor.range"/>
      </Property>
      <Property name="Emissive" id="4693.Emissive" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4693.Emissive.bool"/>
      </Property>
      <Property name="GaussianRadius" id="4693.GaussianRadius" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="range" id="4693.GaussianRadius.range"/>
      </Property>
      <Property name="GlyphType" id="4693.GlyphType" number_of_elements="1">
        <Proxy value="4559" output_port="0"/>
        <Domain name="input_type" id="4693.GlyphType.input_type"/>
        <Domain name="proxy_list" id="4693.GlyphType.proxy_list">
          <Proxy value="4559"/>
          <Proxy value="4570"/>
          <Proxy value="4581"/>
          <Proxy value="4592"/>
          <Proxy value="4603"/>
          <Proxy value="4614"/>
          <Proxy value="4625"/>
        </Domain>
      </Property>
      <Property name="InterpolateScalarsBeforeMapping" id="4693.InterpolateScalarsBeforeMapping" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="4693.InterpolateScalarsBeforeMapping.bool"/>
      </Property>
      <Property name="Interpolation" id="4693.Interpolation" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="enum" id="4693.Interpolation.enum">
          <Entry value="0" text="Flat"/>
          <Entry value="1" text="Gouraud"/>
        </Domain>
      </Property>
      <Property name="LineWidth" id="4693.LineWidth" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="4693.LineWidth.range"/>
      </Property>
      <Property name="LookupTable" id="4693.LookupTable" number_of_elements="1">
        <Proxy value="3961"/>
        <Domain name="groups" id="4693.LookupTable.groups"/>
      </Property>
      <Property name="MapScalars" id="4693.MapScalars" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="4693.MapScalars.bool"/>
      </Property>
      <Property name="Masking" id="4693.Masking" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4693.Masking.bool"/>
      </Property>
      <Property name="MeshVisibility" id="4693.MeshVisibility" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4693.MeshVisibility.bool"/>
      </Property>
      <Property name="NonlinearSubdivisionLevel" id="4693.NonlinearSubdivisionLevel" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="4693.NonlinearSubdivisionLevel.range"/>
      </Property>
      <Property name="Opacity" id="4693.Opacity" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="4693.Opacity.range"/>
      </Property>
      <Property name="OpacityArray" id="4693.OpacityArray" 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="Lithology_type"/>
        <Domain name="array_list" id="4693.OpacityArray.array_list">
          <String text="Lithology_type"/>
        </Domain>
      </Property>
      <Property name="OpacityByArray" id="4693.OpacityByArray" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="4693.OpacityByArray.bool"/>
      </Property>
      <Property name="OpacityTransferFunction" id="4693.OpacityTransferFunction" number_of_elements="1">
        <Proxy value="4636"/>
        <Domain name="groups" id="4693.OpacityTransferFunction.groups"/>
        <Domain name="proxy_list" id="4693.OpacityTransferFunction.proxy_list">
          <Proxy value="4636"/>
        </Domain>
      </Property>
      <Property name="Orient" id="4693.Orient" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4693.Orient.bool"/>
      </Property>
      <Property name="Orientation" id="4693.Orientation" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="4693.Orientation.range"/>
      </Property>
      <Property name="OrientationMode" id="4693.OrientationMode" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="enum" id="4693.OrientationMode.enum">
          <Entry value="0" text="Direction"/>
          <Entry value="1" text="Rotation"/>
        </Domain>
      </Property>
      <Property name="Origin" id="4693.Origin" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="4693.Origin.range"/>
      </Property>
      <Property name="OriginalBoundsRangeActive" id="4693.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="4693.Pickable" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="4693.Pickable.bool"/>
      </Property>
      <Property name="PointSize" id="4693.PointSize" number_of_elements="1">
        <Element index="0" value="2"/>
        <Domain name="range" id="4693.PointSize.range"/>
      </Property>
      <Property name="Position" id="4693.Position" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="4693.Position.range"/>
      </Property>
      <Property name="Scale" id="4693.Scale" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="1"/>
        <Element index="2" value="1"/>
        <Domain name="range" id="4693.Scale.range"/>
      </Property>
      <Property name="ScaleByArray" id="4693.ScaleByArray" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4693.ScaleByArray.bool"/>
      </Property>
      <Property name="ScaleFactor" id="4693.ScaleFactor" number_of_elements="1">
        <Element index="0" value="6632.251171875"/>
        <Domain name="bounds" id="4693.ScaleFactor.bounds"/>
        <Domain name="scalar_range" id="4693.ScaleFactor.scalar_range"/>
        <Domain name="vector_range" id="4693.ScaleFactor.vector_range"/>
      </Property>
      <Property name="ScaleMode" id="4693.ScaleMode" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="enum" id="4693.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="4693.ScaleTransferFunction" number_of_elements="1">
        <Proxy value="4637"/>
        <Domain name="groups" id="4693.ScaleTransferFunction.groups"/>
        <Domain name="proxy_list" id="4693.ScaleTransferFunction.proxy_list">
          <Proxy value="4637"/>
        </Domain>
      </Property>
      <Property name="Scaling" id="4693.Scaling" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4693.Scaling.bool"/>
      </Property>
      <Property name="SelectMaskArray" id="4693.SelectMaskArray" number_of_elements="1">
        <Element index="0" value=""/>
      </Property>
      <Property name="SelectOrientationVectors" id="4693.SelectOrientationVectors" number_of_elements="1">
        <Element index="0" value=""/>
      </Property>
      <Property name="SelectScaleArray" id="4693.SelectScaleArray" number_of_elements="1">
        <Element index="0" value=""/>
      </Property>
      <Property name="SelectionCellLabelBold" id="4693.SelectionCellLabelBold" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4693.SelectionCellLabelBold.bool"/>
      </Property>
      <Property name="SelectionCellLabelColor" id="4693.SelectionCellLabelColor" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="1"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="4693.SelectionCellLabelColor.range"/>
      </Property>
      <Property name="SelectionCellLabelFontFamily" id="4693.SelectionCellLabelFontFamily" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="enum" id="4693.SelectionCellLabelFontFamily.enum">
          <Entry value="0" text="Arial"/>
          <Entry value="1" text="Courier"/>
          <Entry value="2" text="Times"/>
        </Domain>
      </Property>
      <Property name="SelectionCellLabelFontSize" id="4693.SelectionCellLabelFontSize" number_of_elements="1">
        <Element index="0" value="18"/>
        <Domain name="range" id="4693.SelectionCellLabelFontSize.range"/>
      </Property>
      <Property name="SelectionCellLabelFormat" id="4693.SelectionCellLabelFormat" number_of_elements="1">
        <Element index="0" value=""/>
      </Property>
      <Property name="SelectionCellLabelItalic" id="4693.SelectionCellLabelItalic" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4693.SelectionCellLabelItalic.bool"/>
      </Property>
      <Property name="SelectionCellLabelJustification" id="4693.SelectionCellLabelJustification" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="enum" id="4693.SelectionCellLabelJustification.enum">
          <Entry value="0" text="Left"/>
          <Entry value="1" text="Center"/>
          <Entry value="2" text="Right"/>
        </Domain>
      </Property>
      <Property name="SelectionCellLabelOpacity" id="4693.SelectionCellLabelOpacity" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="4693.SelectionCellLabelOpacity.range"/>
      </Property>
      <Property name="SelectionCellLabelShadow" id="4693.SelectionCellLabelShadow" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4693.SelectionCellLabelShadow.bool"/>
      </Property>
      <Property name="SelectionCellLabelVisibility" id="4693.SelectionCellLabelVisibility" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4693.SelectionCellLabelVisibility.bool"/>
      </Property>
      <Property name="SelectionColor" id="4693.SelectionColor" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="0"/>
        <Element index="2" value="1"/>
        <Domain name="range" id="4693.SelectionColor.range"/>
      </Property>
      <Property name="SelectionLineWidth" id="4693.SelectionLineWidth" number_of_elements="1">
        <Element index="0" value="2"/>
        <Domain name="range" id="4693.SelectionLineWidth.range"/>
      </Property>
      <Property name="SelectionOpacity" id="4693.SelectionOpacity" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="4693.SelectionOpacity.range"/>
      </Property>
      <Property name="SelectionPointLabelBold" id="4693.SelectionPointLabelBold" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4693.SelectionPointLabelBold.bool"/>
      </Property>
      <Property name="SelectionPointLabelColor" id="4693.SelectionPointLabelColor" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="1"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="4693.SelectionPointLabelColor.range"/>
      </Property>
      <Property name="SelectionPointLabelFontFamily" id="4693.SelectionPointLabelFontFamily" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="enum" id="4693.SelectionPointLabelFontFamily.enum">
          <Entry value="0" text="Arial"/>
          <Entry value="1" text="Courier"/>
          <Entry value="2" text="Times"/>
        </Domain>
      </Property>
      <Property name="SelectionPointLabelFontSize" id="4693.SelectionPointLabelFontSize" number_of_elements="1">
        <Element index="0" value="18"/>
        <Domain name="range" id="4693.SelectionPointLabelFontSize.range"/>
      </Property>
      <Property name="SelectionPointLabelFormat" id="4693.SelectionPointLabelFormat" number_of_elements="1">
        <Element index="0" value=""/>
      </Property>
      <Property name="SelectionPointLabelItalic" id="4693.SelectionPointLabelItalic" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4693.SelectionPointLabelItalic.bool"/>
      </Property>
      <Property name="SelectionPointLabelJustification" id="4693.SelectionPointLabelJustification" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="enum" id="4693.SelectionPointLabelJustification.enum">
          <Entry value="0" text="Left"/>
          <Entry value="1" text="Center"/>
          <Entry value="2" text="Right"/>
        </Domain>
      </Property>
      <Property name="SelectionPointLabelOpacity" id="4693.SelectionPointLabelOpacity" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="4693.SelectionPointLabelOpacity.range"/>
      </Property>
      <Property name="SelectionPointLabelShadow" id="4693.SelectionPointLabelShadow" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4693.SelectionPointLabelShadow.bool"/>
      </Property>
      <Property name="SelectionPointLabelVisibility" id="4693.SelectionPointLabelVisibility" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4693.SelectionPointLabelVisibility.bool"/>
      </Property>
      <Property name="SelectionPointSize" id="4693.SelectionPointSize" number_of_elements="1">
        <Element index="0" value="5"/>
        <Domain name="range" id="4693.SelectionPointSize.range"/>
      </Property>
      <Property name="SelectionRepresentation" id="4693.SelectionRepresentation" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="enum" id="4693.SelectionRepresentation.enum">
          <Entry value="0" text="Points"/>
          <Entry value="1" text="Wireframe"/>
          <Entry value="2" text="Surface"/>
        </Domain>
      </Property>
      <Property name="SelectionUseOutline" id="4693.SelectionUseOutline" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4693.SelectionUseOutline.bool"/>
      </Property>
      <Property name="SetScaleArray" id="4693.SetScaleArray" 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="Lithology_type"/>
        <Domain name="array_list" id="4693.SetScaleArray.array_list">
          <String text="Lithology_type"/>
        </Domain>
      </Property>
      <Property name="ShaderPreset" id="4693.ShaderPreset" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="enum" id="4693.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="4693.Specular" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="range" id="4693.Specular.range"/>
      </Property>
      <Property name="SpecularColor" id="4693.SpecularColor" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="1"/>
        <Element index="2" value="1"/>
        <Domain name="range" id="4693.SpecularColor.range"/>
      </Property>
      <Property name="SpecularPower" id="4693.SpecularPower" number_of_elements="1">
        <Element index="0" value="100"/>
        <Domain name="range" id="4693.SpecularPower.range"/>
      </Property>
      <Property name="StaticMode" id="4693.StaticMode" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4693.StaticMode.bool"/>
      </Property>
      <Property name="StickyAxes" id="4693.StickyAxes" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4693.StickyAxes.bool"/>
      </Property>
      <Property name="SuppressLOD" id="4693.SuppressLOD" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4693.SuppressLOD.bool"/>
      </Property>
      <Property name="Texture" id="4693.Texture">
        <Domain name="groups" id="4693.Texture.groups"/>
      </Property>
      <Property name="Triangulate" id="4693.Triangulate" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4693.Triangulate.bool"/>
      </Property>
      <Property name="UseAxesOrigin" id="4693.UseAxesOrigin" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4693.UseAxesOrigin.bool"/>
      </Property>
      <Property name="UserTransform" id="4693.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="4035" servers="21">
      <Property name="Enabled" id="4035.Enabled" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="4035.Enabled.bool"/>
      </Property>
      <Property name="LockPosition" id="4035.LockPosition" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="4035.LockPosition.bool"/>
      </Property>
      <Property name="UseNonCompositedRenderer" id="4035.UseNonCompositedRenderer" number_of_elements="1">
        <Element index="0" value="1"/>
      </Property>
      <Property name="AddRangeAnnotations" id="4035.AddRangeAnnotations" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4035.AddRangeAnnotations.bool"/>
      </Property>
      <Property name="AddRangeLabels" id="4035.AddRangeLabels" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="4035.AddRangeLabels.bool"/>
      </Property>
      <Property name="AspectRatio" id="4035.AspectRatio" number_of_elements="1">
        <Element index="0" value="20"/>
        <Domain name="range" id="4035.AspectRatio.range"/>
      </Property>
      <Property name="AutoOrient" id="4035.AutoOrient" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4035.AutoOrient.bool"/>
      </Property>
      <Property name="AutoOrientInfo" id="4035.AutoOrientInfo" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="4035.AutoOrientInfo.bool"/>
      </Property>
      <Property name="AutomaticAnnotations" id="4035.AutomaticAnnotations" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4035.AutomaticAnnotations.bool"/>
      </Property>
      <Property name="AutomaticLabelFormat" id="4035.AutomaticLabelFormat" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="4035.AutomaticLabelFormat.bool"/>
      </Property>
      <Property name="ComponentTitle" id="4035.ComponentTitle" number_of_elements="1">
        <Element index="0" value=""/>
      </Property>
      <Property name="DrawAnnotations" id="4035.DrawAnnotations" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4035.DrawAnnotations.bool"/>
      </Property>
      <Property name="DrawNanAnnotation" id="4035.DrawNanAnnotation" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4035.DrawNanAnnotation.bool"/>
      </Property>
      <Property name="DrawSubTickMarks" id="4035.DrawSubTickMarks" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="4035.DrawSubTickMarks.bool"/>
      </Property>
      <Property name="DrawTickLabels" id="4035.DrawTickLabels" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="4035.DrawTickLabels.bool"/>
      </Property>
      <Property name="DrawTickMarks" id="4035.DrawTickMarks" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="4035.DrawTickMarks.bool"/>
      </Property>
      <Property name="LabelBold" id="4035.LabelBold" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4035.LabelBold.bool"/>
      </Property>
      <Property name="LabelColor" id="4035.LabelColor" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="1"/>
        <Element index="2" value="1"/>
        <Domain name="range" id="4035.LabelColor.range"/>
      </Property>
      <Property name="LabelFontFamily" id="4035.LabelFontFamily" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="enum" id="4035.LabelFontFamily.enum">
          <Entry value="0" text="Arial"/>
          <Entry value="1" text="Courier"/>
          <Entry value="2" text="Times"/>
        </Domain>
      </Property>
      <Property name="LabelFontSize" id="4035.LabelFontSize" number_of_elements="1">
        <Element index="0" value="7"/>
        <Domain name="range" id="4035.LabelFontSize.range"/>
      </Property>
      <Property name="LabelFormat" id="4035.LabelFormat" number_of_elements="1">
        <Element index="0" value="%-#6.3g"/>
      </Property>
      <Property name="LabelItalic" id="4035.LabelItalic" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4035.LabelItalic.bool"/>
      </Property>
      <Property name="LabelOpacity" id="4035.LabelOpacity" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="4035.LabelOpacity.range"/>
      </Property>
      <Property name="LabelShadow" id="4035.LabelShadow" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4035.LabelShadow.bool"/>
      </Property>
      <Property name="LookupTable" id="4035.LookupTable" number_of_elements="1">
        <Proxy value="3961"/>
        <Domain name="groups" id="4035.LookupTable.groups"/>
      </Property>
      <Property name="NanAnnotation" id="4035.NanAnnotation" number_of_elements="1">
        <Element index="0" value="NaN"/>
      </Property>
      <Property name="NumberOfLabels" id="4035.NumberOfLabels" number_of_elements="1">
        <Element index="0" value="5"/>
        <Domain name="range" id="4035.NumberOfLabels.range"/>
      </Property>
      <Property name="Orientation" id="4035.Orientation" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="enum" id="4035.Orientation.enum">
          <Entry value="0" text="Horizontal"/>
          <Entry value="1" text="Vertical"/>
        </Domain>
      </Property>
      <Property name="OrientationInfo" id="4035.OrientationInfo" number_of_elements="1">
        <Element index="0" value="0"/>
      </Property>
      <Property name="Position" id="4035.Position" number_of_elements="2">
        <Element index="0" value="0.264819819819819"/>
        <Element index="1" value="0.0434146341463412"/>
        <Domain name="range" id="4035.Position.range"/>
      </Property>
      <Property name="Position2" id="4035.Position2" number_of_elements="2">
        <Element index="0" value="0.43"/>
        <Element index="1" value="0.12"/>
        <Domain name="range" id="4035.Position2.range"/>
      </Property>
      <Property name="Position2Info" id="4035.Position2Info" number_of_elements="2">
        <Element index="0" value="0.43"/>
        <Element index="1" value="0.12"/>
      </Property>
      <Property name="PositionInfo" id="4035.PositionInfo" number_of_elements="2">
        <Element index="0" value="0.264819819819819"/>
        <Element index="1" value="0.0434146341463412"/>
      </Property>
      <Property name="RangeLabelFormat" id="4035.RangeLabelFormat" number_of_elements="1">
        <Element index="0" value="%4.3e"/>
      </Property>
      <Property name="Repositionable" id="4035.Repositionable" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="4035.Repositionable.bool"/>
      </Property>
      <Property name="Resizable" id="4035.Resizable" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="4035.Resizable.bool"/>
      </Property>
      <Property name="Selectable" id="4035.Selectable" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4035.Selectable.bool"/>
      </Property>
      <Property name="TextPosition" id="4035.TextPosition" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="enum" id="4035.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="4035.Title" number_of_elements="1">
        <Element index="0" value="Lithology_type"/>
      </Property>
      <Property name="TitleBold" id="4035.TitleBold" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4035.TitleBold.bool"/>
      </Property>
      <Property name="TitleColor" id="4035.TitleColor" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="1"/>
        <Element index="2" value="1"/>
        <Domain name="range" id="4035.TitleColor.range"/>
      </Property>
      <Property name="TitleFontFamily" id="4035.TitleFontFamily" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="enum" id="4035.TitleFontFamily.enum">
          <Entry value="0" text="Arial"/>
          <Entry value="1" text="Courier"/>
          <Entry value="2" text="Times"/>
        </Domain>
      </Property>
      <Property name="TitleFontSize" id="4035.TitleFontSize" number_of_elements="1">
        <Element index="0" value="7"/>
        <Domain name="range" id="4035.TitleFontSize.range"/>
      </Property>
      <Property name="TitleItalic" id="4035.TitleItalic" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4035.TitleItalic.bool"/>
      </Property>
      <Property name="TitleJustification" id="4035.TitleJustification" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="enum" id="4035.TitleJustification.enum">
          <Entry value="0" text="Left"/>
          <Entry value="1" text="Centered"/>
          <Entry value="2" text="Right"/>
        </Domain>
      </Property>
      <Property name="TitleOpacity" id="4035.TitleOpacity" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="4035.TitleOpacity.range"/>
      </Property>
      <Property name="TitleShadow" id="4035.TitleShadow" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4035.TitleShadow.bool"/>
      </Property>
      <Property name="Visibility" id="4035.Visibility" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="4035.Visibility.bool"/>
      </Property>
    </Proxy>
    <Proxy group="filters" type="Cut" id="3798" servers="1">
      <Property name="ContourValues" id="3798.ContourValues" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bounds" id="3798.ContourValues.bounds"/>
      </Property>
      <Property name="CutFunction" id="3798.CutFunction" number_of_elements="1">
        <Proxy value="3794"/>
        <Domain name="groups" id="3798.CutFunction.groups"/>
        <Domain name="proxy_list" id="3798.CutFunction.proxy_list">
          <Proxy value="3794"/>
          <Proxy value="3795"/>
          <Proxy value="3796"/>
          <Proxy value="3797"/>
        </Domain>
      </Property>
      <Property name="Input" id="3798.Input" number_of_elements="1">
        <Proxy value="3783" output_port="0"/>
        <Domain name="groups" id="3798.Input.groups"/>
        <Domain name="input_type" id="3798.Input.input_type"/>
      </Property>
      <Property name="InputBounds" id="3798.InputBounds">
        <Domain name="bounds" id="3798.InputBounds.bounds"/>
      </Property>
      <Property name="PreserveInputCells" id="3798.PreserveInputCells" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="3798.PreserveInputCells.bool"/>
      </Property>
      <Property name="Triangulate the slice" id="3798.Triangulate the slice" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="3798.Triangulate the slice.bool"/>
      </Property>
    </Proxy>
    <Proxy group="filters" type="Cut" id="3813" servers="1">
      <Property name="ContourValues" id="3813.ContourValues" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bounds" id="3813.ContourValues.bounds"/>
      </Property>
      <Property name="CutFunction" id="3813.CutFunction" number_of_elements="1">
        <Proxy value="3809"/>
        <Domain name="groups" id="3813.CutFunction.groups"/>
        <Domain name="proxy_list" id="3813.CutFunction.proxy_list">
          <Proxy value="3809"/>
          <Proxy value="3810"/>
          <Proxy value="3811"/>
          <Proxy value="3812"/>
        </Domain>
      </Property>
      <Property name="Input" id="3813.Input" number_of_elements="1">
        <Proxy value="3783" output_port="0"/>
        <Domain name="groups" id="3813.Input.groups"/>
        <Domain name="input_type" id="3813.Input.input_type"/>
      </Property>
      <Property name="InputBounds" id="3813.InputBounds">
        <Domain name="bounds" id="3813.InputBounds.bounds"/>
      </Property>
      <Property name="PreserveInputCells" id="3813.PreserveInputCells" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="3813.PreserveInputCells.bool"/>
      </Property>
      <Property name="Triangulate the slice" id="3813.Triangulate the slice" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="3813.Triangulate the slice.bool"/>
      </Property>
    </Proxy>
    <Proxy group="filters" type="Cut" id="3842" servers="1">
      <Property name="ContourValues" id="3842.ContourValues" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bounds" id="3842.ContourValues.bounds"/>
      </Property>
      <Property name="CutFunction" id="3842.CutFunction" number_of_elements="1">
        <Proxy value="3838"/>
        <Domain name="groups" id="3842.CutFunction.groups"/>
        <Domain name="proxy_list" id="3842.CutFunction.proxy_list">
          <Proxy value="3838"/>
          <Proxy value="3839"/>
          <Proxy value="3840"/>
          <Proxy value="3841"/>
        </Domain>
      </Property>
      <Property name="Input" id="3842.Input" number_of_elements="1">
        <Proxy value="3783" output_port="0"/>
        <Domain name="groups" id="3842.Input.groups"/>
        <Domain name="input_type" id="3842.Input.input_type"/>
      </Property>
      <Property name="InputBounds" id="3842.InputBounds">
        <Domain name="bounds" id="3842.InputBounds.bounds"/>
      </Property>
      <Property name="PreserveInputCells" id="3842.PreserveInputCells" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="3842.PreserveInputCells.bool"/>
      </Property>
      <Property name="Triangulate the slice" id="3842.Triangulate the slice" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="3842.Triangulate the slice.bool"/>
      </Property>
    </Proxy>
    <Proxy group="sources" type="netCDFReader" id="3783" servers="1">
      <Property name="FileName" id="3783.FileName" number_of_elements="1">
        <Element index="0" value="/home/spl/tmp/try/out4.nc"/>
        <Domain name="files" id="3783.FileName.files"/>
      </Property>
      <Property name="TimestepValues" id="3783.TimestepValues"/>
      <Property name="DimensionInfo" id="3783.DimensionInfo" number_of_elements="1">
        <Element index="0" value="(depth, y, x)"/>
      </Property>
      <Property name="Dimensions" id="3783.Dimensions" number_of_elements="1">
        <Element index="0" value="(depth, y, x)"/>
        <Domain name="array_list" id="3783.Dimensions.array_list">
          <String text="(depth, y, x)"/>
        </Domain>
      </Property>
      <Property name="OutputType" id="3783.OutputType" number_of_elements="1">
        <Element index="0" value="-1"/>
        <Domain name="enum" id="3783.OutputType.enum">
          <Entry value="-1" text="Automatic"/>
          <Entry value="6" text="Image"/>
          <Entry value="3" text="Rectilinear"/>
          <Entry value="2" text="Structured"/>
          <Entry value="4" text="Unstructured"/>
        </Domain>
      </Property>
      <Property name="ReplaceFillValueWithNan" id="3783.ReplaceFillValueWithNan" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="3783.ReplaceFillValueWithNan.bool"/>
      </Property>
      <Property name="SphericalCoordinates" id="3783.SphericalCoordinates" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="3783.SphericalCoordinates.bool"/>
      </Property>
      <Property name="VariableArrayInfo" id="3783.VariableArrayInfo" number_of_elements="1">
        <Element index="0" value="Lithology_type"/>
      </Property>
      <Property name="VariableDimensionInfo" id="3783.VariableDimensionInfo" number_of_elements="1">
        <Element index="0" value="(depth, y, x)"/>
      </Property>
      <Property name="VerticalBias" id="3783.VerticalBias" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="range" id="3783.VerticalBias.range"/>
      </Property>
      <Property name="VerticalScale" id="3783.VerticalScale" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="3783.VerticalScale.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="1"/>
      </Property>
      <Property name="TimeSources" id="259.TimeSources" number_of_elements="4">
        <Proxy value="3783"/>
        <Proxy value="3798"/>
        <Proxy value="3813"/>
        <Proxy value="3842"/>
      </Property>
      <Property name="TimestepValues" id="259.TimestepValues"/>
      <Property name="Views" id="259.Views" number_of_elements="1">
        <Proxy value="4705"/>
      </Property>
    </Proxy>
    <Proxy group="views" type="RenderView" id="4705" servers="21">
      <Property name="AlphaBitPlanes" id="4705.AlphaBitPlanes" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="4705.AlphaBitPlanes.bool"/>
      </Property>
      <Property name="ArrayComponentToDraw" id="4705.ArrayComponentToDraw" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="range" id="4705.ArrayComponentToDraw.range"/>
      </Property>
      <Property name="ArrayNameToDraw" id="4705.ArrayNameToDraw" number_of_elements="1">
        <Element index="0" value=""/>
      </Property>
      <Property name="ArrayNumberToDraw" id="4705.ArrayNumberToDraw" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="range" id="4705.ArrayNumberToDraw.range"/>
      </Property>
      <Property name="AxesGrid" id="4705.AxesGrid" number_of_elements="1">
        <Proxy value="3860"/>
        <Domain name="proxy_list" id="4705.AxesGrid.proxy_list">
          <Proxy value="3860"/>
        </Domain>
      </Property>
      <Property name="BackLightAzimuth" id="4705.BackLightAzimuth" number_of_elements="1">
        <Element index="0" value="110"/>
        <Domain name="range" id="4705.BackLightAzimuth.range"/>
      </Property>
      <Property name="BackLightElevation" id="4705.BackLightElevation" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="range" id="4705.BackLightElevation.range"/>
      </Property>
      <Property name="BackLightK:B Ratio" id="4705.BackLightK:B Ratio" number_of_elements="1">
        <Element index="0" value="3.5"/>
        <Domain name="range" id="4705.BackLightK:B Ratio.range"/>
      </Property>
      <Property name="BackLightWarmth" id="4705.BackLightWarmth" number_of_elements="1">
        <Element index="0" value="0.5"/>
        <Domain name="range" id="4705.BackLightWarmth.range"/>
      </Property>
      <Property name="Background" id="4705.Background" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="0"/>
        <Domain name="range" id="4705.Background.range"/>
      </Property>
      <Property name="Background2" id="4705.Background2" number_of_elements="3">
        <Element index="0" value="0"/>
        <Element index="1" value="0"/>
        <Element index="2" value="1"/>
        <Domain name="range" id="4705.Background2.range"/>
      </Property>
      <Property name="BackgroundTexture" id="4705.BackgroundTexture">
        <Domain name="groups" id="4705.BackgroundTexture.groups"/>
      </Property>
      <Property name="CacheKey" id="4705.CacheKey" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="range" id="4705.CacheKey.range"/>
      </Property>
      <Property name="Camera2DManipulators" id="4705.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="4705.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="4705.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="4705.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="4705.CameraParallelProjection" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4705.CameraParallelProjection.bool"/>
      </Property>
      <Property name="CaptureZBuffer" id="4705.CaptureZBuffer"/>
      <Property name="CenterAxesVisibility" id="4705.CenterAxesVisibility" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4705.CenterAxesVisibility.bool"/>
      </Property>
      <Property name="CenterOfRotation" id="4705.CenterOfRotation" number_of_elements="3">
        <Element index="0" value="-74615.443359375"/>
        <Element index="1" value="50632.298828125"/>
        <Element index="2" value="-12750"/>
      </Property>
      <Property name="CollectGeometryThreshold" id="4705.CollectGeometryThreshold" number_of_elements="1">
        <Element index="0" value="100"/>
      </Property>
      <Property name="CompressorConfig" id="4705.CompressorConfig" number_of_elements="1">
        <Element index="0" value=""/>
      </Property>
      <Property name="DepthPeeling" id="4705.DepthPeeling" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4705.DepthPeeling.bool"/>
      </Property>
      <Property name="DrawCells" id="4705.DrawCells" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4705.DrawCells.bool"/>
      </Property>
      <Property name="EnableRenderOnInteraction" id="4705.EnableRenderOnInteraction" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="4705.EnableRenderOnInteraction.bool"/>
      </Property>
      <Property name="FillLightAzimuth" id="4705.FillLightAzimuth" number_of_elements="1">
        <Element index="0" value="-10"/>
        <Domain name="range" id="4705.FillLightAzimuth.range"/>
      </Property>
      <Property name="FillLightElevation" id="4705.FillLightElevation" number_of_elements="1">
        <Element index="0" value="-75"/>
        <Domain name="range" id="4705.FillLightElevation.range"/>
      </Property>
      <Property name="FillLightK:F Ratio" id="4705.FillLightK:F Ratio" number_of_elements="1">
        <Element index="0" value="3"/>
        <Domain name="range" id="4705.FillLightK:F Ratio.range"/>
      </Property>
      <Property name="FillLightWarmth" id="4705.FillLightWarmth" number_of_elements="1">
        <Element index="0" value="0.4"/>
        <Domain name="range" id="4705.FillLightWarmth.range"/>
      </Property>
      <Property name="HeadLightK:H Ratio" id="4705.HeadLightK:H Ratio" number_of_elements="1">
        <Element index="0" value="3"/>
        <Domain name="range" id="4705.HeadLightK:H Ratio.range"/>
      </Property>
      <Property name="HeadLightWarmth" id="4705.HeadLightWarmth" number_of_elements="1">
        <Element index="0" value="0.5"/>
        <Domain name="range" id="4705.HeadLightWarmth.range"/>
      </Property>
      <Property name="ImageReductionFactor" id="4705.ImageReductionFactor" number_of_elements="1">
        <Element index="0" value="20"/>
        <Domain name="range" id="4705.ImageReductionFactor.range"/>
      </Property>
      <Property name="InteractionMode" id="4705.InteractionMode" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="enum" id="4705.InteractionMode.enum">
          <Entry value="0" text="3D"/>
          <Entry value="1" text="2D"/>
          <Entry value="2" text="Selection"/>
        </Domain>
      </Property>
      <Property name="KeyLightAzimuth" id="4705.KeyLightAzimuth" number_of_elements="1">
        <Element index="0" value="10"/>
        <Domain name="range" id="4705.KeyLightAzimuth.range"/>
      </Property>
      <Property name="KeyLightElevation" id="4705.KeyLightElevation" number_of_elements="1">
        <Element index="0" value="50"/>
        <Domain name="range" id="4705.KeyLightElevation.range"/>
      </Property>
      <Property name="KeyLightIntensity" id="4705.KeyLightIntensity" number_of_elements="1">
        <Element index="0" value="0.75"/>
        <Domain name="range" id="4705.KeyLightIntensity.range"/>
      </Property>
      <Property name="KeyLightWarmth" id="4705.KeyLightWarmth" number_of_elements="1">
        <Element index="0" value="0.6"/>
        <Domain name="range" id="4705.KeyLightWarmth.range"/>
      </Property>
      <Property name="LODResolution" id="4705.LODResolution" number_of_elements="1">
        <Element index="0" value="0.5"/>
        <Domain name="range" id="4705.LODResolution.range"/>
      </Property>
      <Property name="LODThreshold" id="4705.LODThreshold" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="range" id="4705.LODThreshold.range"/>
      </Property>
      <Property name="LightAmbientColor" id="4705.LightAmbientColor" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="1"/>
        <Element index="2" value="1"/>
        <Domain name="range" id="4705.LightAmbientColor.range"/>
      </Property>
      <Property name="LightDiffuseColor" id="4705.LightDiffuseColor" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="1"/>
        <Element index="2" value="1"/>
        <Domain name="range" id="4705.LightDiffuseColor.range"/>
      </Property>
      <Property name="LightIntensity" id="4705.LightIntensity" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="4705.LightIntensity.range"/>
      </Property>
      <Property name="LightSpecularColor" id="4705.LightSpecularColor" number_of_elements="3">
        <Element index="0" value="1"/>
        <Element index="1" value="1"/>
        <Element index="2" value="1"/>
        <Domain name="range" id="4705.LightSpecularColor.range"/>
      </Property>
      <Property name="LightSwitch" id="4705.LightSwitch" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4705.LightSwitch.bool"/>
      </Property>
      <Property name="LightType" id="4705.LightType" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="enum" id="4705.LightType.enum">
          <Entry value="1" text="HeadLight"/>
          <Entry value="2" text="CameraLight"/>
          <Entry value="3" text="SceneLight"/>
        </Domain>
      </Property>
      <Property name="LockBounds" id="4705.LockBounds" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4705.LockBounds.bool"/>
      </Property>
      <Property name="MaintainLuminance" id="4705.MaintainLuminance" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4705.MaintainLuminance.bool"/>
      </Property>
      <Property name="MaximumNumberOfPeels" id="4705.MaximumNumberOfPeels" number_of_elements="1">
        <Element index="0" value="4"/>
        <Domain name="range" id="4705.MaximumNumberOfPeels.range"/>
      </Property>
      <Property name="MultiSamples" id="4705.MultiSamples" number_of_elements="1">
        <Element index="0" value="0"/>
      </Property>
      <Property name="NonInteractiveRenderDelay" id="4705.NonInteractiveRenderDelay" number_of_elements="1">
        <Element index="0" value="2"/>
      </Property>
      <Property name="OrientationAxesInteractivity" id="4705.OrientationAxesInteractivity" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4705.OrientationAxesInteractivity.bool"/>
      </Property>
      <Property name="OrientationAxesLabelColor" id="4705.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="4705.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="4705.OrientationAxesVisibility" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="4705.OrientationAxesVisibility.bool"/>
      </Property>
      <Property name="RemoteRenderThreshold" id="4705.RemoteRenderThreshold" number_of_elements="1">
        <Element index="0" value="500"/>
        <Domain name="range" id="4705.RemoteRenderThreshold.range"/>
      </Property>
      <Property name="Representations" id="4705.Representations" number_of_elements="5">
        <Proxy value="4019"/>
        <Proxy value="4035"/>
        <Proxy value="4192"/>
        <Proxy value="4359"/>
        <Proxy value="4693"/>
      </Property>
      <Property name="RotationFactor" id="4705.RotationFactor" number_of_elements="1">
        <Element index="0" value="1"/>
      </Property>
      <Property name="ScalarRange" id="4705.ScalarRange" number_of_elements="2">
        <Element index="0" value="0"/>
        <Element index="1" value="-1"/>
        <Domain name="range" id="4705.ScalarRange.range"/>
      </Property>
      <Property name="ServerStereoType" id="4705.ServerStereoType" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="enum" id="4705.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="4705.ShowAnnotation" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4705.ShowAnnotation.bool"/>
      </Property>
      <Property name="StartCaptureLuminance" id="4705.StartCaptureLuminance"/>
      <Property name="StartCaptureValues" id="4705.StartCaptureValues"/>
      <Property name="StencilCapable" id="4705.StencilCapable" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="4705.StencilCapable.bool"/>
      </Property>
      <Property name="StereoRender" id="4705.StereoRender" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4705.StereoRender.bool"/>
      </Property>
      <Property name="StereoType" id="4705.StereoType" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="enum" id="4705.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="4705.StillRenderImageReductionFactor" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="range" id="4705.StillRenderImageReductionFactor.range"/>
      </Property>
      <Property name="StopCaptureLuminance" id="4705.StopCaptureLuminance"/>
      <Property name="StopCaptureValues" id="4705.StopCaptureValues"/>
      <Property name="UseCache" id="4705.UseCache" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4705.UseCache.bool"/>
      </Property>
      <Property name="UseGradientBackground" id="4705.UseGradientBackground" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="4705.UseGradientBackground.bool"/>
      </Property>
      <Property name="UseInteractiveRenderingForScreenshots" id="4705.UseInteractiveRenderingForScreenshots" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4705.UseInteractiveRenderingForScreenshots.bool"/>
      </Property>
      <Property name="UseLight" id="4705.UseLight" number_of_elements="1">
        <Element index="0" value="1"/>
        <Domain name="bool" id="4705.UseLight.bool"/>
      </Property>
      <Property name="UseOffscreenRendering" id="4705.UseOffscreenRendering" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4705.UseOffscreenRendering.bool"/>
      </Property>
      <Property name="UseOffscreenRenderingForScreenshots" id="4705.UseOffscreenRenderingForScreenshots" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4705.UseOffscreenRenderingForScreenshots.bool"/>
      </Property>
      <Property name="UseOutlineForLODRendering" id="4705.UseOutlineForLODRendering" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4705.UseOutlineForLODRendering.bool"/>
      </Property>
      <Property name="UseTexturedBackground" id="4705.UseTexturedBackground" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="bool" id="4705.UseTexturedBackground.bool"/>
      </Property>
      <Property name="ViewSize" id="4705.ViewSize" number_of_elements="2">
        <Element index="0" value="1777"/>
        <Element index="1" value="1313"/>
      </Property>
      <Property name="ViewTime" id="4705.ViewTime" number_of_elements="1">
        <Element index="0" value="0"/>
        <Domain name="range" id="4705.ViewTime.range"/>
      </Property>
      <Property name="CameraClippingRange" id="4705.CameraClippingRange" number_of_elements="2">
        <Element index="0" value="19990.2271674183"/>
        <Element index="1" value="227424.068967362"/>
      </Property>
      <Property name="CameraClippingRangeInfo" id="4705.CameraClippingRangeInfo" number_of_elements="2">
        <Element index="0" value="19990.2271674183"/>
        <Element index="1" value="227424.068967362"/>
      </Property>
      <Property name="CameraFocalPoint" id="4705.CameraFocalPoint" number_of_elements="3">
        <Element index="0" value="-30662.4063769425"/>
        <Element index="1" value="4132.71185002032"/>
        <Element index="2" value="-30010.811269414"/>
      </Property>
      <Property name="CameraFocalPointInfo" id="4705.CameraFocalPointInfo" number_of_elements="3">
        <Element index="0" value="-30662.4063769425"/>
        <Element index="1" value="4132.71185002032"/>
        <Element index="2" value="-30010.811269414"/>
      </Property>
      <Property name="CameraParallelScale" id="4705.CameraParallelScale" number_of_elements="1">
        <Element index="0" value="46121.6043811914"/>
      </Property>
      <Property name="CameraParallelScaleInfo" id="4705.CameraParallelScaleInfo" number_of_elements="1">
        <Element index="0" value="46121.6043811914"/>
      </Property>
      <Property name="CameraPosition" id="4705.CameraPosition" number_of_elements="3">
        <Element index="0" value="-161708.327315767"/>
        <Element index="1" value="117062.596268412"/>
        <Element index="2" value="12757.370954858"/>
      </Property>
      <Property name="CameraPositionInfo" id="4705.CameraPositionInfo" number_of_elements="3">
        <Element index="0" value="-161708.327315767"/>
        <Element index="1" value="117062.596268412"/>
        <Element index="2" value="12757.370954858"/>
      </Property>
      <Property name="CameraViewAngle" id="4705.CameraViewAngle" number_of_elements="1">
        <Element index="0" value="30"/>
      </Property>
      <Property name="CameraViewUp" id="4705.CameraViewUp" number_of_elements="3">
        <Element index="0" value="0.16328875815931"/>
        <Element index="1" value="-0.178015596988301"/>
        <Element index="2" value="0.970385092985094"/>
      </Property>
      <Property name="CameraViewUpInfo" id="4705.CameraViewUpInfo" number_of_elements="3">
        <Element index="0" value="0.16328875815931"/>
        <Element index="1" value="-0.178015596988301"/>
        <Element index="2" value="0.970385092985094"/>
      </Property>
      <Property name="EyeAngle" id="4705.EyeAngle" number_of_elements="1">
        <Element index="0" value="2"/>
        <Domain name="range" id="4705.EyeAngle.range"/>
      </Property>
    </Proxy>
    <ProxyCollection name="animation">
      <Item id="263" name="AnimationScene1"/>
      <Item id="265" name="TimeAnimationCue1"/>
    </ProxyCollection>
    <ProxyCollection name="layouts">
      <Item id="4706" name="ViewLayout1"/>
    </ProxyCollection>
    <ProxyCollection name="lookup_tables">
      <Item id="3961" name="Lithologytype.PVLookupTable"/>
    </ProxyCollection>
    <ProxyCollection name="piecewise_functions">
      <Item id="3960" name="Lithologytype.PiecewiseFunction"/>
    </ProxyCollection>
    <ProxyCollection name="pq_helper_proxies.12002">
      <Item id="3860" name="AxesGrid"/>
    </ProxyCollection>
    <ProxyCollection name="pq_helper_proxies.12090">
      <Item id="4774" name="RepresentationAnimationHelper"/>
    </ProxyCollection>
    <ProxyCollection name="pq_helper_proxies.12336">
      <Item id="3883" name="GlyphType"/>
      <Item id="3894" name="GlyphType"/>
      <Item id="3905" name="GlyphType"/>
      <Item id="3916" name="GlyphType"/>
      <Item id="3927" name="GlyphType"/>
      <Item id="3938" name="GlyphType"/>
      <Item id="3949" name="GlyphType"/>
      <Item id="3962" name="OpacityTransferFunction"/>
      <Item id="3963" name="ScaleTransferFunction"/>
    </ProxyCollection>
    <ProxyCollection name="pq_helper_proxies.12359">
      <Item id="3794" name="CutFunction"/>
      <Item id="3795" name="CutFunction"/>
      <Item id="3796" name="CutFunction"/>
      <Item id="3797" name="CutFunction"/>
      <Item id="4775" name="RepresentationAnimationHelper"/>
    </ProxyCollection>
    <ProxyCollection name="pq_helper_proxies.12530">
      <Item id="4058" name="GlyphType"/>
      <Item id="4069" name="GlyphType"/>
      <Item id="4080" name="GlyphType"/>
      <Item id="4091" name="GlyphType"/>
      <Item id="4102" name="GlyphType"/>
      <Item id="4113" name="GlyphType"/>
      <Item id="4124" name="GlyphType"/>
      <Item id="4135" name="OpacityTransferFunction"/>
      <Item id="4136" name="ScaleTransferFunction"/>
    </ProxyCollection>
    <ProxyCollection name="pq_helper_proxies.12551">
      <Item id="3809" name="CutFunction"/>
      <Item id="3810" name="CutFunction"/>
      <Item id="3811" name="CutFunction"/>
      <Item id="3812" name="CutFunction"/>
      <Item id="4776" name="RepresentationAnimationHelper"/>
    </ProxyCollection>
    <ProxyCollection name="pq_helper_proxies.12722">
      <Item id="4225" name="GlyphType"/>
      <Item id="4236" name="GlyphType"/>
      <Item id="4247" name="GlyphType"/>
      <Item id="4258" name="GlyphType"/>
      <Item id="4269" name="GlyphType"/>
      <Item id="4280" name="GlyphType"/>
      <Item id="4291" name="GlyphType"/>
      <Item id="4302" name="OpacityTransferFunction"/>
      <Item id="4303" name="ScaleTransferFunction"/>
    </ProxyCollection>
    <ProxyCollection name="pq_helper_proxies.12758">
      <Item id="3824" name="Locator"/>
      <Item id="3825" name="Locator"/>
      <Item id="3826" name="Locator"/>
      <Item id="4777" name="RepresentationAnimationHelper"/>
    </ProxyCollection>
    <ProxyCollection name="pq_helper_proxies.12926">
      <Item id="4392" name="GlyphType"/>
      <Item id="4403" name="GlyphType"/>
      <Item id="4414" name="GlyphType"/>
      <Item id="4425" name="GlyphType"/>
      <Item id="4436" name="GlyphType"/>
      <Item id="4447" name="GlyphType"/>
      <Item id="4458" name="GlyphType"/>
      <Item id="4469" name="OpacityTransferFunction"/>
      <Item id="4470" name="ScaleTransferFunction"/>
    </ProxyCollection>
    <ProxyCollection name="pq_helper_proxies.12941">
      <Item id="4778" name="CutFunction"/>
      <Item id="4779" name="CutFunction"/>
      <Item id="4780" name="CutFunction"/>
      <Item id="4781" name="CutFunction"/>
      <Item id="4782" name="RepresentationAnimationHelper"/>
    </ProxyCollection>
    <ProxyCollection name="pq_helper_proxies.13112">
      <Item id="4783" name="GlyphType"/>
      <Item id="4794" name="GlyphType"/>
      <Item id="4805" name="GlyphType"/>
      <Item id="4816" name="GlyphType"/>
      <Item id="4827" name="GlyphType"/>
      <Item id="4838" name="GlyphType"/>
      <Item id="4849" name="GlyphType"/>
      <Item id="4860" name="OpacityTransferFunction"/>
      <Item id="4861" name="ScaleTransferFunction"/>
    </ProxyCollection>
    <ProxyCollection name="pq_helper_proxies.13127">
      <Item id="3838" name="CutFunction"/>
      <Item id="3839" name="CutFunction"/>
      <Item id="3840" name="CutFunction"/>
      <Item id="3841" name="CutFunction"/>
      <Item id="4862" name="RepresentationAnimationHelper"/>
    </ProxyCollection>
    <ProxyCollection name="pq_helper_proxies.13298">
      <Item id="4559" name="GlyphType"/>
      <Item id="4570" name="GlyphType"/>
      <Item id="4581" name="GlyphType"/>
      <Item id="4592" name="GlyphType"/>
      <Item id="4603" name="GlyphType"/>
      <Item id="4614" name="GlyphType"/>
      <Item id="4625" name="GlyphType"/>
      <Item id="4636" name="OpacityTransferFunction"/>
      <Item id="4637" name="ScaleTransferFunction"/>
    </ProxyCollection>
    <ProxyCollection name="representations">
      <Item id="4019" name="GeometryRepresentation1"/>
      <Item id="4192" name="GeometryRepresentation2"/>
      <Item id="4359" name="GeometryRepresentation3"/>
      <Item id="4693" name="GeometryRepresentation6"/>
    </ProxyCollection>
    <ProxyCollection name="scalar_bars">
      <Item id="4035" name="ScalarBarWidgetRepresentation1"/>
    </ProxyCollection>
    <ProxyCollection name="sources">
      <Item id="3798" name="Slice1"/>
      <Item id="3813" name="Slice2"/>
      <Item id="3842" name="Slice4"/>
      <Item id="3783" name="out..nc"/>
    </ProxyCollection>
    <ProxyCollection name="timekeeper">
      <Item id="259" name="TimeKeeper1"/>
    </ProxyCollection>
    <ProxyCollection name="views">
      <Item id="4705" name="RenderView1"/>
    </ProxyCollection>
    <CustomProxyDefinitions>
      <CustomProxyDefinition name="Map Projection" group="filters">
        <CompoundSourceProxy id="5387" servers="1">
          <Proxy group="filters" type="TransformFilter" id="4739" servers="1" compound_name="Transform1">
            <Property name="Input" id="4739.Input" number_of_elements="1">
              <Domain name="groups" id="4739.Input.groups"/>
              <Domain name="input_type" id="4739.Input.input_type"/>
            </Property>
            <Property name="Transform" id="4739.Transform" number_of_elements="1">
              <Proxy value="4738"/>
              <Domain name="groups" id="4739.Transform.groups"/>
              <Domain name="proxy_list" id="4739.Transform.proxy_list">
                <Proxy value="4738"/>
              </Domain>
            </Property>
          </Proxy>
          <Proxy group="extended_sources" type="Transform3" id="4738" servers="1" compound_name="auto_4738">
            <Property name="Position" id="4738.Position" number_of_elements="3">
              <Element index="0" value="-1.81898940354586e-12"/>
              <Element index="1" value="0"/>
              <Element index="2" value="-9.09494701772928e-13"/>
              <Domain name="range" id="4738.Position.range"/>
            </Property>
            <Property name="PositionInfo" id="4738.PositionInfo" number_of_elements="3">
              <Element index="0" value="0"/>
              <Element index="1" value="0"/>
              <Element index="2" value="0"/>
            </Property>
            <Property name="Rotation" id="4738.Rotation" number_of_elements="3">
              <Element index="0" value="0"/>
              <Element index="1" value="0"/>
              <Element index="2" value="0"/>
              <Domain name="range" id="4738.Rotation.range"/>
            </Property>
            <Property name="RotationInfo" id="4738.RotationInfo" number_of_elements="3">
              <Element index="0" value="0"/>
              <Element index="1" value="0"/>
              <Element index="2" value="0"/>
            </Property>
            <Property name="Scale" id="4738.Scale" number_of_elements="3">
              <Element index="0" value="100"/>
              <Element index="1" value="100"/>
              <Element index="2" value="0.1"/>
              <Domain name="range" id="4738.Scale.range"/>
            </Property>
            <Property name="ScaleInfo" id="4738.ScaleInfo" number_of_elements="3">
              <Element index="0" value="100"/>
              <Element index="1" value="100"/>
              <Element index="2" value="0.1"/>
            </Property>
          </Proxy>
          <ExposedProperties>
            <Property name="Input" proxy_name="Transform1" exposed_name="Input"/>
          </ExposedProperties>
          <OutputPort name="Output" proxy="Transform1" port_index="0"/>
          <Hints>
            <ShowInMenu/>
          </Hints>
        </CompoundSourceProxy>
      </CustomProxyDefinition>
    </CustomProxyDefinitions>
    <Links>
      <GlobalPropertyLink global_name="EdgeColor" proxy="4019" property="EdgeColor"/>
      <GlobalPropertyLink global_name="EdgeColor" proxy="4192" property="EdgeColor"/>
      <GlobalPropertyLink global_name="EdgeColor" proxy="4359" property="EdgeColor"/>
      <GlobalPropertyLink global_name="EdgeColor" proxy="4693" property="EdgeColor"/>
      <GlobalPropertyLink global_name="ForegroundColor" proxy="3860" property="GridColor"/>
      <GlobalPropertyLink global_name="ForegroundColor" proxy="4705" property="OrientationAxesOutlineColor"/>
      <GlobalPropertyLink global_name="ForegroundColor" proxy="4019" property="AmbientColor"/>
      <GlobalPropertyLink global_name="ForegroundColor" proxy="4019" property="Color"/>
      <GlobalPropertyLink global_name="ForegroundColor" proxy="4019" property="CubeAxesColor"/>
      <GlobalPropertyLink global_name="ForegroundColor" proxy="4192" property="AmbientColor"/>
      <GlobalPropertyLink global_name="ForegroundColor" proxy="4192" property="Color"/>
      <GlobalPropertyLink global_name="ForegroundColor" proxy="4192" property="CubeAxesColor"/>
      <GlobalPropertyLink global_name="ForegroundColor" proxy="4359" property="AmbientColor"/>
      <GlobalPropertyLink global_name="ForegroundColor" proxy="4359" property="Color"/>
      <GlobalPropertyLink global_name="ForegroundColor" proxy="4359" property="CubeAxesColor"/>
      <GlobalPropertyLink global_name="ForegroundColor" proxy="4693" property="AmbientColor"/>
      <GlobalPropertyLink global_name="ForegroundColor" proxy="4693" property="Color"/>
      <GlobalPropertyLink global_name="ForegroundColor" proxy="4693" property="CubeAxesColor"/>
      <GlobalPropertyLink global_name="SelectionColor" proxy="4019" property="SelectionColor"/>
      <GlobalPropertyLink global_name="SelectionColor" proxy="4192" property="SelectionColor"/>
      <GlobalPropertyLink global_name="SelectionColor" proxy="4359" property="SelectionColor"/>
      <GlobalPropertyLink global_name="SelectionColor" proxy="4693" property="SelectionColor"/>
      <GlobalPropertyLink global_name="SurfaceColor" proxy="4019" property="BackfaceDiffuseColor"/>
      <GlobalPropertyLink global_name="SurfaceColor" proxy="4019" property="DiffuseColor"/>
      <GlobalPropertyLink global_name="SurfaceColor" proxy="4192" property="BackfaceDiffuseColor"/>
      <GlobalPropertyLink global_name="SurfaceColor" proxy="4192" property="DiffuseColor"/>
      <GlobalPropertyLink global_name="SurfaceColor" proxy="4359" property="BackfaceDiffuseColor"/>
      <GlobalPropertyLink global_name="SurfaceColor" proxy="4359" property="DiffuseColor"/>
      <GlobalPropertyLink global_name="SurfaceColor" proxy="4693" property="BackfaceDiffuseColor"/>
      <GlobalPropertyLink global_name="SurfaceColor" proxy="4693" property="DiffuseColor"/>
      <GlobalPropertyLink global_name="TextAnnotationColor" proxy="3860" property="XLabelColor"/>
      <GlobalPropertyLink global_name="TextAnnotationColor" proxy="3860" property="XTitleColor"/>
      <GlobalPropertyLink global_name="TextAnnotationColor" proxy="3860" property="YLabelColor"/>
      <GlobalPropertyLink global_name="TextAnnotationColor" proxy="3860" property="YTitleColor"/>
      <GlobalPropertyLink global_name="TextAnnotationColor" proxy="3860" property="ZLabelColor"/>
      <GlobalPropertyLink global_name="TextAnnotationColor" proxy="3860" property="ZTitleColor"/>
      <GlobalPropertyLink global_name="TextAnnotationColor" proxy="4705" property="OrientationAxesLabelColor"/>
      <GlobalPropertyLink global_name="TextAnnotationColor" proxy="4035" property="LabelColor"/>
      <GlobalPropertyLink global_name="TextAnnotationColor" proxy="4035" property="TitleColor"/>
    </Links>
  </ServerManagerState>
</ParaView>

From david.hora at iwf.mavt.ethz.ch  Wed Jun  8 11:54:38 2016
From: david.hora at iwf.mavt.ethz.ch (Hora  David)
Date: Wed, 08 Jun 2016 15:54:38 -0000
Subject: [Paraview] Surface Streamlines
Message-ID: <8F022B11FBA69944857353AB6A65527618067672@MBX112.d.ethz.ch>

Hello everybody

I observed a problem with surface streamlines in ParaView 4.4. It can be reproduced with the attached files.

The case has a flat geometry in the XZ plane and a velocity distribution without Y-component. Using the filter 'Stream Tracer with Custom Source' gives me very nice results. Unfortunately, the streamlines look bad as soon as I activate the option 'Surface Streamlines'. I would expect more or less the same results as everything is in the same plane. Adjusting the settings didn't help. The standard 'Stream Tracer' filter is also affected.

The conclusion is that the option doesn't work reliably in certain cases. It can be avoided in cases with the plane perpendicular to an axis (by removing the corresponding velocity component with the calculator) but not for planes with arbitrary positions.

Best regards
David


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160608/ccb9bb7a/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: plane.pvsm
Type: application/octet-stream
Size: 147268 bytes
Desc: plane.pvsm
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160608/ccb9bb7a/attachment-0002.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: plane.vtp
Type: application/octet-stream
Size: 486799 bytes
Desc: plane.vtp
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160608/ccb9bb7a/attachment-0003.obj>

From s.neethling at imperial.ac.uk  Fri Jun 17 11:22:35 2016
From: s.neethling at imperial.ac.uk (Neethling, Stephen)
Date: Fri, 17 Jun 2016 15:22:35 -0000
Subject: [Paraview] Bug with Opacity
Message-ID: <DB3PR06MB188C37E33B8D7783A40C20FC2570@DB3PR06MB188.eurprd06.prod.outlook.com>

Version: Paraview 5.0.1

I have found a bug when rendering points with opacity. All the data for the render is stored in a single vtp file, but as this file is generated from the raw data outputted by my simulator, the points are ordered based on the processor with outputted the data. This has resulted in artefacts associated with the boundaries between the processor regions. When I take the identical data, but randomise the order of the points the artefacts disappear, which means that is not due the underlying data. In the attached image the LHS picture has the points randomised in terms of their order and on the LHS it is ordered based on the processors that created it (otherwise exactly the same number of points containing exactly the same set of data). The opacity in these plots was set to 0.05.

I can't easily attach the input files as altogether they are nearly a Gigabyte is size (images each contain a few million points), but can upload them if required.

Regards,
Stephen


Prof Stephen Neethling
Professor in Minerals Processing
Dept. of Earth Science and Engineering
Imperial College London
Tel: +44 (0)20 7594 9341

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160617/a3e041cd/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: comparison.png
Type: image/png
Size: 820465 bytes
Desc: comparison.png
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160617/a3e041cd/attachment-0001.png>