From orion at cora.nwra.com  Mon Oct  3 13:51:35 2016
From: orion at cora.nwra.com (Orion Poplawski)
Date: Mon, 3 Oct 2016 11:51:35 -0600
Subject: [Paraview-developers] Issue recognized as spam
Message-ID: <8a337608-dd20-dc65-b5e1-3b4a146c4d1f@cora.nwra.com>

I'm trying to submit a new issue at
https://gitlab.kitware.com/paraview/paraview/issues# but am getting:

The form contains the following error:

    Your issue has been recognized as spam and has been discarded.

Any suggestions as to how to avoid this?

-- 
Orion Poplawski
Technical Manager                     303-415-9701 x222
NWRA, Boulder/CoRA Office             FAX: 303-415-9702
3380 Mitchell Lane                       orion at nwra.com
Boulder, CO 80301                   http://www.nwra.com

From brad.king at kitware.com  Mon Oct  3 14:04:58 2016
From: brad.king at kitware.com (Brad King)
Date: Mon, 3 Oct 2016 14:04:58 -0400
Subject: [Paraview-developers] Issue recognized as spam
In-Reply-To: <8a337608-dd20-dc65-b5e1-3b4a146c4d1f@cora.nwra.com>
References: <8a337608-dd20-dc65-b5e1-3b4a146c4d1f@cora.nwra.com>
Message-ID: <fa12973f-3d9d-82f2-3b4b-016910100f9f@kitware.com>

On 10/03/2016 01:51 PM, Orion Poplawski wrote:
> I'm trying to submit a new issue at
> https://gitlab.kitware.com/paraview/paraview/issues# but am getting:
> 
> The form contains the following error:
> 
>     Your issue has been recognized as spam and has been discarded.
> 
> Any suggestions as to how to avoid this?

I found the rejection in GitLab's spam log and marked it as ham.
Please try submitting it again with the same content.

Thanks,
-Brad

From wascott at sandia.gov  Mon Oct  3 22:29:44 2016
From: wascott at sandia.gov (Scott, W Alan)
Date: Tue, 4 Oct 2016 02:29:44 +0000
Subject: [Paraview-developers] hidden line removal - default
Message-ID: <593c1de02b674acfa4c08c3b11762d4b@ES01AMSNLNT.srn.sandia.gov>

Why not default hidden line removal on for wireframe?  I think it adds to our look and polish so much that I can't see anyone using the old wireframe.

At the very least, let's make it a standard property on the Properties tab.  It is currently advanced!  That's not where it belongs.

Thoughts?

Alan

--------------------------------------------------------
W. Alan Scott
ParaView Support Manager

SAIC
Sandia National Laboratories, MS 0822
Org 9326 - Building 880 A1-K
(505) 284-0932   FAX (505) 284-5619
---------------------------------------------------------

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20161004/0950615b/attachment.html>

From utkarsh.ayachit at kitware.com  Tue Oct  4 09:40:32 2016
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Tue, 4 Oct 2016 09:40:32 -0400
Subject: [Paraview-developers] hidden line removal - default
In-Reply-To: <593c1de02b674acfa4c08c3b11762d4b@ES01AMSNLNT.srn.sandia.gov>
References: <593c1de02b674acfa4c08c3b11762d4b@ES01AMSNLNT.srn.sandia.gov>
Message-ID: <CADHSJjAECR8t7RPdnD8drSMmBZuxEw2vWF8ZpYQgY6Jb2Frm4A@mail.gmail.com>

Alan,

A couple of reasons why I feel this should not be the default:

1. it doesn't work when using distributed rendering; in that case, it
reverts back to traditional wireframe mode
2. it's more work i.e. it will incur a performance hit

Utkarsh


On Mon, Oct 3, 2016 at 10:29 PM, Scott, W Alan <wascott at sandia.gov> wrote:

> Why not default hidden line removal on for wireframe?  I think it adds to
> our look and polish so much that I can?t see anyone using the old wireframe.
>
>
>
> At the very least, let?s make it a standard property on the Properties
> tab.  It is currently advanced!  That?s not where it belongs.
>
>
>
> Thoughts?
>
>
>
> Alan
>
>
>
> --------------------------------------------------------
>
> W. Alan Scott
>
> ParaView Support Manager
>
>
>
> SAIC
>
> Sandia National Laboratories, MS 0822
>
> Org 9326 - Building 880 A1-K
>
> (505) 284-0932   FAX (505) 284-5619
>
> ---------------------------------------------------------
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20161004/f33a6e07/attachment.html>

From sujin.philip at kitware.com  Tue Oct  4 10:31:28 2016
From: sujin.philip at kitware.com (Sujin Philip)
Date: Tue, 4 Oct 2016 10:31:28 -0400
Subject: [Paraview-developers] ParaView Line widget
Message-ID: <CAEWo2JOt9oStuRr9gncQD40qJ7HA-pGEDP1wz3OR7xQrq836iw@mail.gmail.com>

Hi Devs,

I am currently adding a new feature to ParaView line widget, where the user
can place the end-points using the keys '1' and '2' for point 1 and point 2
respectively. Please refer to issue:
https://gitlab.kitware.com/paraview/paraview/issues/15836.

We are now planning to remove the combo-box that selects the point to place
with the 'P' key, since those cases are handled by the '1' and '2' keys.
Are there any objections to this change?

Thanks
Sujin
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20161004/4e42b94e/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Screenshot_20161004_101740.png
Type: image/png
Size: 37610 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20161004/4e42b94e/attachment-0001.png>

From mathieu.westphal at kitware.com  Tue Oct  4 11:18:55 2016
From: mathieu.westphal at kitware.com (Mathieu Westphal)
Date: Tue, 4 Oct 2016 17:18:55 +0200
Subject: [Paraview-developers] ParaView Line widget
In-Reply-To: <CAEWo2JOt9oStuRr9gncQD40qJ7HA-pGEDP1wz3OR7xQrq836iw@mail.gmail.com>
References: <CAEWo2JOt9oStuRr9gncQD40qJ7HA-pGEDP1wz3OR7xQrq836iw@mail.gmail.com>
Message-ID: <CAC2t4URjFiUkaFpMkcDM2Mh5bmOjkgpnCSTdFqENKGQv3seYCg@mail.gmail.com>

It was me how added the combo box, and i've always found it quite ugly, so
i'm happy with the change !

Mathieu Westphal

On Tue, Oct 4, 2016 at 4:31 PM, Sujin Philip <sujin.philip at kitware.com>
wrote:

> Hi Devs,
>
> I am currently adding a new feature to ParaView line widget, where the
> user can place the end-points using the keys '1' and '2' for point 1 and
> point 2 respectively. Please refer to issue: https://gitlab.kitware.com/
> paraview/paraview/issues/15836.
>
> We are now planning to remove the combo-box that selects the point to
> place with the 'P' key, since those cases are handled by the '1' and '2'
> keys. Are there any objections to this change?
>
> Thanks
> Sujin
>
>
> _______________________________________________
> 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-developers/attachments/20161004/4e4c04f0/attachment.html>

From aron.helser at kitware.com  Tue Oct  4 12:31:56 2016
From: aron.helser at kitware.com (Aron Helser)
Date: Tue, 4 Oct 2016 12:31:56 -0400
Subject: [Paraview-developers] ParaView Line widget
In-Reply-To: <CAC2t4URjFiUkaFpMkcDM2Mh5bmOjkgpnCSTdFqENKGQv3seYCg@mail.gmail.com>
References: <CAEWo2JOt9oStuRr9gncQD40qJ7HA-pGEDP1wz3OR7xQrq836iw@mail.gmail.com>
 <CAC2t4URjFiUkaFpMkcDM2Mh5bmOjkgpnCSTdFqENKGQv3seYCg@mail.gmail.com>
Message-ID: <CAF2skS4=v4OaGs3R96E=BQkhDzPeb0U+tUY=6kVLM0GG7JgFEQ@mail.gmail.com>

What does the 'P' key do now, in that case? Does it always add pt 1, or the
last pt, or alternate?

Thanks,
Aron

On Tue, Oct 4, 2016 at 11:18 AM, Mathieu Westphal <
mathieu.westphal at kitware.com> wrote:

> It was me how added the combo box, and i've always found it quite ugly, so
> i'm happy with the change !
>
> Mathieu Westphal
>
> On Tue, Oct 4, 2016 at 4:31 PM, Sujin Philip <sujin.philip at kitware.com>
> wrote:
>
>> Hi Devs,
>>
>> I am currently adding a new feature to ParaView line widget, where the
>> user can place the end-points using the keys '1' and '2' for point 1 and
>> point 2 respectively. Please refer to issue:
>> https://gitlab.kitware.com/paraview/paraview/issues/15836.
>>
>> We are now planning to remove the combo-box that selects the point to
>> place with the 'P' key, since those cases are handled by the '1' and '2'
>> keys. Are there any objections to this change?
>>
>> Thanks
>> Sujin
>>
>>
>> _______________________________________________
>> 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-developers/attachments/20161004/1df9214e/attachment.html>

From sujin.philip at kitware.com  Tue Oct  4 12:54:11 2016
From: sujin.philip at kitware.com (Sujin Philip)
Date: Tue, 4 Oct 2016 12:54:11 -0400
Subject: [Paraview-developers] ParaView Line widget
In-Reply-To: <CAF2skS4=v4OaGs3R96E=BQkhDzPeb0U+tUY=6kVLM0GG7JgFEQ@mail.gmail.com>
References: <CAEWo2JOt9oStuRr9gncQD40qJ7HA-pGEDP1wz3OR7xQrq836iw@mail.gmail.com>
 <CAC2t4URjFiUkaFpMkcDM2Mh5bmOjkgpnCSTdFqENKGQv3seYCg@mail.gmail.com>
 <CAF2skS4=v4OaGs3R96E=BQkhDzPeb0U+tUY=6kVLM0GG7JgFEQ@mail.gmail.com>
Message-ID: <CAEWo2JNTUFt5W8P9TdeFsXLvDv_Nv84f=t67jhVX+7fdPvStBw@mail.gmail.com>

I am thinking it would do the default behavior which is to alternate.

-Sujin

On Tue, Oct 4, 2016 at 12:31 PM, Aron Helser <aron.helser at kitware.com>
wrote:

> What does the 'P' key do now, in that case? Does it always add pt 1, or
> the last pt, or alternate?
>
> Thanks,
> Aron
>
> On Tue, Oct 4, 2016 at 11:18 AM, Mathieu Westphal <
> mathieu.westphal at kitware.com> wrote:
>
>> It was me how added the combo box, and i've always found it quite ugly,
>> so i'm happy with the change !
>>
>> Mathieu Westphal
>>
>> On Tue, Oct 4, 2016 at 4:31 PM, Sujin Philip <sujin.philip at kitware.com>
>> wrote:
>>
>>> Hi Devs,
>>>
>>> I am currently adding a new feature to ParaView line widget, where the
>>> user can place the end-points using the keys '1' and '2' for point 1 and
>>> point 2 respectively. Please refer to issue:
>>> https://gitlab.kitware.com/paraview/paraview/issues/15836.
>>>
>>> We are now planning to remove the combo-box that selects the point to
>>> place with the 'P' key, since those cases are handled by the '1' and '2'
>>> keys. Are there any objections to this change?
>>>
>>> Thanks
>>> Sujin
>>>
>>>
>>> _______________________________________________
>>> 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-developers/attachments/20161004/cad26c06/attachment.html>

From wascott at sandia.gov  Tue Oct  4 13:13:17 2016
From: wascott at sandia.gov (Scott, W Alan)
Date: Tue, 4 Oct 2016 17:13:17 +0000
Subject: [Paraview-developers] [EXTERNAL] Re: hidden line removal -
	default
In-Reply-To: <CADHSJjAECR8t7RPdnD8drSMmBZuxEw2vWF8ZpYQgY6Jb2Frm4A@mail.gmail.com>
References: <593c1de02b674acfa4c08c3b11762d4b@ES01AMSNLNT.srn.sandia.gov>
 <CADHSJjAECR8t7RPdnD8drSMmBZuxEw2vWF8ZpYQgY6Jb2Frm4A@mail.gmail.com>
Message-ID: <c394a9e2034a47c9bb11e7a69cd57d04@ES01AMSNLNT.srn.sandia.gov>

1)      Yep, I remembered that the second I put foot in the car last night.  Good point.

2)      Easy to fix.  Just don?t do hidden line removal when the mouse is being used.

Alan

From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com]
Sent: Tuesday, October 04, 2016 7:41 AM
To: Scott, W Alan <wascott at sandia.gov>
Cc: paraview-developers at paraview.org
Subject: [EXTERNAL] Re: hidden line removal - default

Alan,

A couple of reasons why I feel this should not be the default:

1. it doesn't work when using distributed rendering; in that case, it reverts back to traditional wireframe mode
2. it's more work i.e. it will incur a performance hit

Utkarsh


On Mon, Oct 3, 2016 at 10:29 PM, Scott, W Alan <wascott at sandia.gov<mailto:wascott at sandia.gov>> wrote:
Why not default hidden line removal on for wireframe?  I think it adds to our look and polish so much that I can?t see anyone using the old wireframe.

At the very least, let?s make it a standard property on the Properties tab.  It is currently advanced!  That?s not where it belongs.

Thoughts?

Alan

--------------------------------------------------------
W. Alan Scott
ParaView Support Manager

SAIC
Sandia National Laboratories, MS 0822
Org 9326 - Building 880 A1-K
(505) 284-0932<tel:%28505%29%20284-0932>   FAX (505) 284-5619<tel:%28505%29%20284-5619>
---------------------------------------------------------


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20161004/7a78d428/attachment-0001.html>

From wascott at sandia.gov  Tue Oct  4 14:48:34 2016
From: wascott at sandia.gov (Scott, W Alan)
Date: Tue, 4 Oct 2016 18:48:34 +0000
Subject: [Paraview-developers] [EXTERNAL]  ParaView Line widget
In-Reply-To: <CAEWo2JOt9oStuRr9gncQD40qJ7HA-pGEDP1wz3OR7xQrq836iw@mail.gmail.com>
References: <CAEWo2JOt9oStuRr9gncQD40qJ7HA-pGEDP1wz3OR7xQrq836iw@mail.gmail.com>
Message-ID: <1eae7a75a95b4d5daa89205c4ebfe8af@ES01AMSNLNT.srn.sandia.gov>

Sounds like a huge improvement.

Alan

From: Paraview-developers [mailto:paraview-developers-bounces at paraview.org] On Behalf Of Sujin Philip
Sent: Tuesday, October 04, 2016 8:31 AM
To: ParaView Developers <paraview-developers at paraview.org>
Subject: [EXTERNAL] [Paraview-developers] ParaView Line widget

Hi Devs,
I am currently adding a new feature to ParaView line widget, where the user can place the end-points using the keys '1' and '2' for point 1 and point 2 respectively. Please refer to issue: https://gitlab.kitware.com/paraview/paraview/issues/15836.
We are now planning to remove the combo-box that selects the point to place with the 'P' key, since those cases are handled by the '1' and '2' keys. Are there any objections to this change?
Thanks
Sujin
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20161004/d908edfb/attachment.html>

From sujin.philip at kitware.com  Wed Oct  5 08:43:55 2016
From: sujin.philip at kitware.com (Sujin Philip)
Date: Wed, 5 Oct 2016 08:43:55 -0400
Subject: [Paraview-developers] [EXTERNAL]  ParaView Line widget
In-Reply-To: <1eae7a75a95b4d5daa89205c4ebfe8af@ES01AMSNLNT.srn.sandia.gov>
References: <CAEWo2JOt9oStuRr9gncQD40qJ7HA-pGEDP1wz3OR7xQrq836iw@mail.gmail.com>
 <1eae7a75a95b4d5daa89205c4ebfe8af@ES01AMSNLNT.srn.sandia.gov>
Message-ID: <CAEWo2JMRBPKJVt7kokHk=wLprXBfpJ5cB=vw_WSh3uxZ5_NCcA@mail.gmail.com>

Thanks everyone for your feedback.

-Sujin


On Tue, Oct 4, 2016 at 2:48 PM, Scott, W Alan <wascott at sandia.gov> wrote:

> Sounds like a huge improvement.
>
>
>
> Alan
>
>
>
> *From:* Paraview-developers [mailto:paraview-developers-
> bounces at paraview.org] *On Behalf Of *Sujin Philip
> *Sent:* Tuesday, October 04, 2016 8:31 AM
> *To:* ParaView Developers <paraview-developers at paraview.org>
> *Subject:* [EXTERNAL] [Paraview-developers] ParaView Line widget
>
>
>
> Hi Devs,
>
> I am currently adding a new feature to ParaView line widget, where the
> user can place the end-points using the keys '1' and '2' for point 1 and
> point 2 respectively. Please refer to issue: https://gitlab.kitware.com/
> paraview/paraview/issues/15836.
>
> We are now planning to remove the combo-box that selects the point to
> place with the 'P' key, since those cases are handled by the '1' and '2'
> keys. Are there any objections to this change?
>
> Thanks
>
> Sujin
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20161005/248409be/attachment.html>

From mathieu.westphal at kitware.com  Fri Oct  7 03:42:19 2016
From: mathieu.westphal at kitware.com (Mathieu Westphal)
Date: Fri, 7 Oct 2016 09:42:19 +0200
Subject: [Paraview-developers] Property that keep in sync (via information
	only properties ? )
Message-ID: <CAC2t4UTAKoh4CM7H4v-eaZPOW8Ajra2=C627F6mC0rsHgHu_Pg@mail.gmail.com>

Hi

I'm looking for an xml only way to have "kept-in-sync" properties widget in
paraview.

eg : You have a SetColor, a SetLineColor, a SetBodyColor
using SetColor should influence both SetLineColor and SetBodyColor property
widget as well.

Regards,

Mathieu Westphal
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20161007/8a52ff6b/attachment.html>

From cory.quammen at kitware.com  Fri Oct  7 16:44:48 2016
From: cory.quammen at kitware.com (Cory Quammen)
Date: Fri, 7 Oct 2016 16:44:48 -0400
Subject: [Paraview-developers] ParaView 5.2.0-RC1 tagged
Message-ID: <CAB5Fpx60y47s7E-5280xkye-JcgGYXTp-005dyOsi-swfogdEQ@mail.gmail.com>

Folks,

v5.2.0-RC1 has been tagged. Please do not merge anything into `master`
until the dashboards have cycled through and been able to build to the
binaries for this version.

I'll send an email when it is okay to merge to `master` again.

Thanks,
Cory

-- 
Cory Quammen
Staff R&D Engineer
Kitware, Inc.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20161007/d132e746/attachment.html>

From liujieigcea at gmail.com  Sun Oct  9 09:13:19 2016
From: liujieigcea at gmail.com (Jie_SYSU)
Date: Sun, 9 Oct 2016 06:13:19 -0700 (MST)
Subject: [Paraview-developers] eliminate shadows of surface in partitioned
	boundaries?
Message-ID: <1476018799802-4798.post@n6.nabble.com>

I have partitioned my big models to several data blocks and written in pvtu
format. The models can be visualised in Paraview almost as normal -- except
there are shadows in the partitioning boundaries in surface view and using
transparency parameter. This is caused by repeated points on boundaries. 
Is there any way to eliminate the shadows?

Thanks.

Jie



--
View this message in context: http://the-unofficial-paraview-developers-forum.34153.x6.nabble.com/eliminate-shadows-of-surface-in-partitioned-boundaries-tp4798.html
Sent from the The Unofficial ParaView Developers Forum mailing list archive at Nabble.com.

From cory.quammen at kitware.com  Mon Oct 10 11:22:14 2016
From: cory.quammen at kitware.com (Cory Quammen)
Date: Mon, 10 Oct 2016 11:22:14 -0400
Subject: [Paraview-developers] ParaView 5.2.0-RC1 tagged
In-Reply-To: <CAB5Fpx60y47s7E-5280xkye-JcgGYXTp-005dyOsi-swfogdEQ@mail.gmail.com>
References: <CAB5Fpx60y47s7E-5280xkye-JcgGYXTp-005dyOsi-swfogdEQ@mail.gmail.com>
Message-ID: <CAB5Fpx4-c6BzweeERVJJz0-xkS6d+eK=Jmn3QK3x+v_EtGw3MA@mail.gmail.com>

Thanks for your patience. The ParaView v5.2.0-RC1 binaries have been built.

It is okay to merge to ParaView master now.

Cory



On Fri, Oct 7, 2016 at 4:44 PM, Cory Quammen <cory.quammen at kitware.com>
wrote:

> Folks,
>
> v5.2.0-RC1 has been tagged. Please do not merge anything into `master`
> until the dashboards have cycled through and been able to build to the
> binaries for this version.
>
> I'll send an email when it is okay to merge to `master` again.
>
> Thanks,
> Cory
>
> --
> Cory Quammen
> Staff R&D Engineer
> Kitware, Inc.
>



-- 
Cory Quammen
Staff R&D Engineer
Kitware, Inc.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20161010/623d04c8/attachment.html>

From kmorel at sandia.gov  Mon Oct 10 12:17:46 2016
From: kmorel at sandia.gov (Moreland, Kenneth)
Date: Mon, 10 Oct 2016 16:17:46 +0000
Subject: [Paraview-developers] [EXTERNAL] eliminate shadows of surface
 in partitioned	boundaries?
In-Reply-To: <1476018799802-4798.post@n6.nabble.com>
References: <1476018799802-4798.post@n6.nabble.com>
Message-ID: <2bd35b0efd654b35b15923c25bd4cdfa@ES08AMSNLNT.srn.sandia.gov>

Jie,

Assuming you are running ParaView in parallel, try running the Ghost Cells Generator filter.

Alternately, you can write out your partitioned data with a layer of ghost cells.

-Ken

-----Original Message-----
From: Paraview-developers [mailto:paraview-developers-bounces at paraview.org] On Behalf Of Jie_SYSU
Sent: Sunday, October 9, 2016 7:13 AM
To: paraview-developers at paraview.org
Subject: [EXTERNAL] [Paraview-developers] eliminate shadows of surface in partitioned boundaries?

I have partitioned my big models to several data blocks and written in pvtu format. The models can be visualised in Paraview almost as normal -- except there are shadows in the partitioning boundaries in surface view and using transparency parameter. This is caused by repeated points on boundaries. 
Is there any way to eliminate the shadows?

Thanks.

Jie



--
View this message in context: http://the-unofficial-paraview-developers-forum.34153.x6.nabble.com/eliminate-shadows-of-surface-in-partitioned-boundaries-tp4798.html
Sent from the The Unofficial ParaView Developers Forum mailing list archive at Nabble.com.
_______________________________________________
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 cory.quammen at kitware.com  Tue Oct 11 09:50:23 2016
From: cory.quammen at kitware.com (Cory Quammen)
Date: Tue, 11 Oct 2016 09:50:23 -0400
Subject: [Paraview-developers] ParaView 5.2 Release Candidate 1 available
	for download
Message-ID: <CAB5Fpx42BmbwNz-hwnH=g4gNRBRTCcdhJ9osOdCsiX5_pG9_tA@mail.gmail.com>

On behalf of the ParaView development team, I am pleased to announce
that ParaView 5.2 Release Candidate 1 binaries and source tarballs are
now available for download at

http://www.paraview.org/download/

Please let us know if you encounter any problems with this release candidate.

Thanks,
Cory

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

From utkarsh.ayachit at kitware.com  Tue Oct 11 11:15:53 2016
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Tue, 11 Oct 2016 11:15:53 -0400
Subject: [Paraview-developers] ParaView 5.2 Release Candidate 1
 available for download
In-Reply-To: <CAB5Fpx42BmbwNz-hwnH=g4gNRBRTCcdhJ9osOdCsiX5_pG9_tA@mail.gmail.com>
References: <CAB5Fpx42BmbwNz-hwnH=g4gNRBRTCcdhJ9osOdCsiX5_pG9_tA@mail.gmail.com>
Message-ID: <CADHSJjAS10QzFJd+M4o1HdfDYWYKUZLm4qLOqE0XapJKFZyipA@mail.gmail.com>

Folks,

Among several new features, this release includes anti-aliasing
support [1]. Currently, it's off by default. I'd encourage all testers
and early adopters to turn it on and report any issues you notice. If
we don't hear of any major obstacles, we would anti-aliasing on my
default in the final release (or subsequent RCs)

Utkarsh

[1] https://blog.kitware.com/new-fxaa-anti-aliasing-option-in-paraviewvtk/


On Tue, Oct 11, 2016 at 9:50 AM, Cory Quammen <cory.quammen at kitware.com> wrote:
> On behalf of the ParaView development team, I am pleased to announce
> that ParaView 5.2 Release Candidate 1 binaries and source tarballs are
> now available for download at
>
> http://www.paraview.org/download/
>
> Please let us know if you encounter any problems with this release candidate.
>
> Thanks,
> Cory
>
> --
> Cory Quammen
> Staff R&D Engineer
> Kitware, Inc.
> _______________________________________________
> 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 marcus.hanwell at kitware.com  Wed Oct 12 18:57:15 2016
From: marcus.hanwell at kitware.com (Marcus D. Hanwell)
Date: Wed, 12 Oct 2016 18:57:15 -0400
Subject: [Paraview-developers] Disable test data download seems to be broken
Message-ID: <CAMkPkZX1xwMWJqCYWC-i48if5o7EWHyv9P67V6YNviT8RPq_Mw@mail.gmail.com>

Hi,

I just got a new laptop, and wanted to see how ParaView did, and tried
to disable download of test data. First I tried turning on the CMake
variable, next I tried using the set up for development script and
chose to exclude from the all target.

In both cases I still see many downloads from MIDAS, is there a new
way to enable this, or perhaps it got broken at some point? This is
ParaView master as of a few minutes ago with CMake 3.5.1 on Linux with
the Unix Makefiles generator.

Thanks,

Marcus

From brad.king at kitware.com  Thu Oct 13 08:16:01 2016
From: brad.king at kitware.com (Brad King)
Date: Thu, 13 Oct 2016 08:16:01 -0400
Subject: [Paraview-developers] Disable test data download seems to be
 broken
In-Reply-To: <CAMkPkZX1xwMWJqCYWC-i48if5o7EWHyv9P67V6YNviT8RPq_Mw@mail.gmail.com>
References: <CAMkPkZX1xwMWJqCYWC-i48if5o7EWHyv9P67V6YNviT8RPq_Mw@mail.gmail.com>
Message-ID: <54c15a59-ca2b-6b6e-f770-2f8eb482e8c0@kitware.com>

On 10/12/2016 06:57 PM, Marcus D. Hanwell wrote:
> In both cases I still see many downloads from MIDAS, is there a new
> way to enable this, or perhaps it got broken at some point?

It looks like the paraview_test_data_target function creates
new test data targets without honoring the
PARAVIEW_DATA_EXCLUDE_FROM_ALL option.  Those targets then have
a dependency on the main ParaViewData target and thus bring it
into the "all" target anyway.

Why is the paraview_test_data_target function needed?  Why can't
all data be handled by the one ParaViewData target?

-Brad


From ben.boeckel at kitware.com  Thu Oct 13 09:05:53 2016
From: ben.boeckel at kitware.com (Ben Boeckel)
Date: Thu, 13 Oct 2016 09:05:53 -0400
Subject: [Paraview-developers] Disable test data download seems to be
 broken
In-Reply-To: <54c15a59-ca2b-6b6e-f770-2f8eb482e8c0@kitware.com>
References: <CAMkPkZX1xwMWJqCYWC-i48if5o7EWHyv9P67V6YNviT8RPq_Mw@mail.gmail.com>
 <54c15a59-ca2b-6b6e-f770-2f8eb482e8c0@kitware.com>
Message-ID: <20161013130553.GA12309@megas.kitware.com>

On Thu, Oct 13, 2016 at 08:16:01 -0400, Brad King wrote:
> On 10/12/2016 06:57 PM, Marcus D. Hanwell wrote:
> > In both cases I still see many downloads from MIDAS, is there a new
> > way to enable this, or perhaps it got broken at some point?
> 
> It looks like the paraview_test_data_target function creates
> new test data targets without honoring the
> PARAVIEW_DATA_EXCLUDE_FROM_ALL option.  Those targets then have
> a dependency on the main ParaViewData target and thus bring it
> into the "all" target anyway.
> 
> Why is the paraview_test_data_target function needed?  Why can't
> all data be handled by the one ParaViewData target?

Looking at its usage, it is used inside of the plugins. I believe they
may not have access to the main ParaViewData target. This may have been
an incorrect assumption or conclusion (I forget which it may have been).

The logic boils down to:

  set(data)
  foreach (datafile IN LISTS ARGN)
    list(APPEND data
      "DATA{${PARAVIEW_TEST_DATA_DIR}/${datafile}/,REGEX:.*}")
  endforeach ()
  ExternalData_Expand_Arguments("ParaViewData${name}" files ${data})
  ExternalData_Add_Target("ParaViewData${name}")
  add_dependencies("ParaViewData${name}"
    ParaViewData)

I'll add the logic for EXCLUDE_FROM_ALL at least.

--Ben

From brad.king at kitware.com  Thu Oct 13 09:10:19 2016
From: brad.king at kitware.com (Brad King)
Date: Thu, 13 Oct 2016 09:10:19 -0400
Subject: [Paraview-developers] Disable test data download seems to be
 broken
In-Reply-To: <20161013130553.GA12309@megas.kitware.com>
References: <CAMkPkZX1xwMWJqCYWC-i48if5o7EWHyv9P67V6YNviT8RPq_Mw@mail.gmail.com>
 <54c15a59-ca2b-6b6e-f770-2f8eb482e8c0@kitware.com>
 <20161013130553.GA12309@megas.kitware.com>
Message-ID: <b9c68a9a-ad2b-6b17-463b-d1e31dde96f1@kitware.com>

On 10/13/2016 09:05 AM, Ben Boeckel wrote:
>   ExternalData_Expand_Arguments("ParaViewData${name}" files ${data})
>   ExternalData_Add_Target("ParaViewData${name}")
>   add_dependencies("ParaViewData${name}"
>     ParaViewData)

They should be able to just use

  ExternalData_Expand_Arguments("ParaViewData" files ${data})

without adding another target.

-Brad


From shawn.waldon at kitware.com  Thu Oct 13 17:31:47 2016
From: shawn.waldon at kitware.com (Shawn Waldon)
Date: Thu, 13 Oct 2016 17:31:47 -0400
Subject: [Paraview-developers] [ANNOUNCE] ParaView coding style transition:
	use clang-format
Message-ID: <CALSpCT3QaOzm9v1q3gNpro44FBxhiuiCA-z1xjKQiWfV+XXWHw@mail.gmail.com>

Hi all,

VTK recently changed their code style rules to move curly braces to align
with the statement above.  When considering whether to follow this change,
the ParaView team has decided to use clang-format to auto-format our code.
I am putting together a branch that will convert all of the ParaView source
code to the clang-format style we have chosen [1]*.  Since this branch will
touch every C/C++ file, it is guaranteed to conflict will all outstanding
branches.

Here is the style we have decided on:
---
# This configuration requires clang-format 3.8 or higher.
BasedOnStyle: Mozilla
AlignAfterOpenBracket: DontAlign
AlignOperands: false
AlwaysBreakAfterReturnType: None
AlwaysBreakAfterDefinitionReturnType: None
BreakBeforeBraces: Allman
ColumnLimit: 100
Standard: Cpp03
...

I will be creating a one-shot conversion commit with the author "Kitware
Robot" using an automated script to apply the formatting across all of
ParaView's source and header files.  We plan to do this after the next RC
is tagged.  There will be an empty commit prior to the conversion commit
with instructions in its commit message for rebasing current branches
across the style transition.

We are adding a script in Utilities/Scripts/clang-format.bash to aid in
reformatting code.  It has options to reformat the currently changed code,
the amend the last commit or rewrite the current branch with the formatting
corrected (note: this is assuming the branch is based after the transition
commit, rebasing across the transition is trickier).  It also has an option
to reformat the entire ParaView codebase that I will be using to
automatically convert everything.

Shawn

[1]: https://gitlab.kitware.com/paraview/paraview/merge_requests/1097

*: this branch is out of date right now, but will be rebased and the
reformatting re-run before it is merged.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20161013/611c7aa8/attachment.html>

From wascott at sandia.gov  Thu Oct 13 19:45:50 2016
From: wascott at sandia.gov (Scott, W Alan)
Date: Thu, 13 Oct 2016 23:45:50 +0000
Subject: [Paraview-developers] New color map for colorblind folks
Message-ID: <8AC59980-2D69-4C61-BFC4-4EF4DF7FEED7@sandia.gov>

Here is a proposed color map  for use by colorblind folks.  It was created here at Sandia by some of our color blind engineers for a different project.  Evidently, this group included folks with different types of color blindness.  Although it isn?t my favorite, it appears to be fairly well balanced, and we can?t say it is bad for color blind folks?

Should we put ColorBlind in the name?  I don?t want to label folks, but I want to make clear why this color map exists?

We could also put it out on paraview.org if we like.  Ask the community if it is a good color blind color map?

Thoughts?

Alan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20161013/4075814f/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: colorblindColorMap.png
Type: image/png
Size: 106384 bytes
Desc: colorblindColorMap.png
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20161013/4075814f/attachment-0001.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: colorblindColorMap.json
Type: application/json
Size: 600 bytes
Desc: colorblindColorMap.json
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20161013/4075814f/attachment-0001.json>

From david.thompson at kitware.com  Thu Oct 13 21:02:08 2016
From: david.thompson at kitware.com (David Thompson)
Date: Thu, 13 Oct 2016 21:02:08 -0400
Subject: [Paraview-developers] New color map for colorblind folks
In-Reply-To: <8AC59980-2D69-4C61-BFC4-4EF4DF7FEED7@sandia.gov>
References: <8AC59980-2D69-4C61-BFC4-4EF4DF7FEED7@sandia.gov>
Message-ID: <6384B09B-87CA-4D9B-86DB-063CE81D3757@kitware.com>

Hi Alan,

I would be worried that -- even though the palette allows people with one form of color blindness or another to distinguish values -- that it might create perceptual problems for them. We might try one of the color-blindness simulators (like http://www.color-blindness.com/coblis-color-blindness-simulator/ ) to see whether the simulated images contain artificial perceptual discontinuities due to sharp changes in the apparent luminance or hue.

    David

> On Oct 13, 2016, at 19:45, Scott, W Alan <wascott at sandia.gov> wrote:
> 
> Here is a proposed color map  for use by colorblind folks.  It was created here at Sandia by some of our color blind engineers for a different project.  Evidently, this group included folks with different types of color blindness.  Although it isn?t my favorite, it appears to be fairly well balanced, and we can?t say it is bad for color blind folks?
> 
> Should we put ColorBlind in the name?  I don?t want to label folks, but I want to make clear why this color map exists?
> 
> We could also put it out on paraview.org if we like.  Ask the community if it is a good color blind color map?
> 
> Thoughts?
> 
> Alan
> <colorblindColorMap.png>
> <colorblindColorMap.json>
> _______________________________________________
> 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-developers/attachments/20161013/aa742666/attachment.html>

From cory.quammen at kitware.com  Mon Oct 17 16:13:10 2016
From: cory.quammen at kitware.com (Cory Quammen)
Date: Mon, 17 Oct 2016 16:13:10 -0400
Subject: [Paraview-developers] Preparing to tag ParaView 5.2 RC2 tomorrow
Message-ID: <CAB5Fpx7ocAz7_6HRevdVjhn8xYGPnwEiY5rWAC+gtrZKrQSXZA@mail.gmail.com>

Hi folks,

Just a heads up that we are preparing to tag ParaView 5.2 Release Candidate
2 tomorrow.

Thanks!
Cory

-- 
Cory Quammen
Staff R&D Engineer
Kitware, Inc.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20161017/f866dcb3/attachment.html>

From cory.quammen at kitware.com  Tue Oct 18 15:25:18 2016
From: cory.quammen at kitware.com (Cory Quammen)
Date: Tue, 18 Oct 2016 15:25:18 -0400
Subject: [Paraview-developers] ParaView 5.2.0-RC2 tagged
Message-ID: <CAB5Fpx5Hsq4tVfWG=u25GkfbQZE_fdeovhpHfX=A=4GBkTr4BA@mail.gmail.com>

Folks,

v5.2.0-RC2 has been tagged. Please do not merge anything into `master`
until the dashboards have cycled through and been able to build to the
binaries for this version.

I'll send an email when it is okay to merge to `master` again.

Thanks,
Cory

-- 
Cory Quammen
Staff R&D Engineer
Kitware, Inc.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20161018/f4057c25/attachment.html>

From shawn.waldon at kitware.com  Tue Oct 18 16:41:10 2016
From: shawn.waldon at kitware.com (Shawn Waldon)
Date: Tue, 18 Oct 2016 16:41:10 -0400
Subject: [Paraview-developers] ParaView 5.2.0-RC2 tagged
In-Reply-To: <CAB5Fpx5Hsq4tVfWG=u25GkfbQZE_fdeovhpHfX=A=4GBkTr4BA@mail.gmail.com>
References: <CAB5Fpx5Hsq4tVfWG=u25GkfbQZE_fdeovhpHfX=A=4GBkTr4BA@mail.gmail.com>
Message-ID: <CALSpCT1g9jy_sE0fX93aAdxEx+vLNQV=KXph++VNDK7-adaSUw@mail.gmail.com>

Cory,

I am working on doxygen style conversion and clang-format update branches
for ParaView (similar to what Dave DeMarle and David Gobbi did for VTK last
month).  I'd like to try to get those merged during/just after this freeze
on merging if possible.  I've put links to the MRs below.  The doxygen
formatting one is rebased on master and I'm working on rebasing the
clang-format branch onto it now.  Can we wait to re-enable merges until
these have been tested and merge them first?

Shawn

clang-format:
https://gitlab.kitware.com/paraview/paraview/merge_requests/1097
documentation to /** doxygen style:
https://gitlab.kitware.com/paraview/paraview/merge_requests/1117

On Tue, Oct 18, 2016 at 3:25 PM, Cory Quammen <cory.quammen at kitware.com>
wrote:

> Folks,
>
> v5.2.0-RC2 has been tagged. Please do not merge anything into `master`
> until the dashboards have cycled through and been able to build to the
> binaries for this version.
>
> I'll send an email when it is okay to merge to `master` again.
>
> Thanks,
> Cory
>
> --
> Cory Quammen
> Staff R&D Engineer
> Kitware, Inc.
>
> _______________________________________________
> 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-developers/attachments/20161018/11402b9b/attachment.html>

From cory.quammen at kitware.com  Tue Oct 18 22:13:08 2016
From: cory.quammen at kitware.com (Cory Quammen)
Date: Tue, 18 Oct 2016 22:13:08 -0400
Subject: [Paraview-developers] ParaView 5.2.0-RC2 tagged
In-Reply-To: <CALSpCT1g9jy_sE0fX93aAdxEx+vLNQV=KXph++VNDK7-adaSUw@mail.gmail.com>
References: <CAB5Fpx5Hsq4tVfWG=u25GkfbQZE_fdeovhpHfX=A=4GBkTr4BA@mail.gmail.com>
 <CALSpCT1g9jy_sE0fX93aAdxEx+vLNQV=KXph++VNDK7-adaSUw@mail.gmail.com>
Message-ID: <CAB5Fpx6Ut=c1f4tE=JpQjLWp-AEiaaJcZj0aX_Gi42oS+v42tA@mail.gmail.com>

Shawn,

That sounds like a good plan. The binaries should be built by Wednesday
morning, so if you can work on it tomorrow and work out the kinks, that
would be great.

Thanks,
Cory

On Tue, Oct 18, 2016 at 4:41 PM, Shawn Waldon <shawn.waldon at kitware.com>
wrote:

> Cory,
>
> I am working on doxygen style conversion and clang-format update branches
> for ParaView (similar to what Dave DeMarle and David Gobbi did for VTK last
> month).  I'd like to try to get those merged during/just after this freeze
> on merging if possible.  I've put links to the MRs below.  The doxygen
> formatting one is rebased on master and I'm working on rebasing the
> clang-format branch onto it now.  Can we wait to re-enable merges until
> these have been tested and merge them first?
>
> Shawn
>
> clang-format: https://gitlab.kitware.com/paraview/paraview/merge_
> requests/1097
> documentation to /** doxygen style: https://gitlab.kitware.com/
> paraview/paraview/merge_requests/1117
>
> On Tue, Oct 18, 2016 at 3:25 PM, Cory Quammen <cory.quammen at kitware.com>
> wrote:
>
>> Folks,
>>
>> v5.2.0-RC2 has been tagged. Please do not merge anything into `master`
>> until the dashboards have cycled through and been able to build to the
>> binaries for this version.
>>
>> I'll send an email when it is okay to merge to `master` again.
>>
>> Thanks,
>> Cory
>>
>> --
>> Cory Quammen
>> Staff R&D Engineer
>> Kitware, Inc.
>>
>> _______________________________________________
>> 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
>>
>>
>


-- 
Cory Quammen
Staff R&D Engineer
Kitware, Inc.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20161018/d8a0d8a8/attachment.html>

From shawn.waldon at kitware.com  Wed Oct 19 09:50:39 2016
From: shawn.waldon at kitware.com (Shawn Waldon)
Date: Wed, 19 Oct 2016 09:50:39 -0400
Subject: [Paraview-developers] [ANNOUNCE] ParaView coding style
	transition: use clang-format
In-Reply-To: <CALSpCT3QaOzm9v1q3gNpro44FBxhiuiCA-z1xjKQiWfV+XXWHw@mail.gmail.com>
References: <CALSpCT3QaOzm9v1q3gNpro44FBxhiuiCA-z1xjKQiWfV+XXWHw@mail.gmail.com>
Message-ID: <CALSpCT0haVQcUWK802ryCdwVP5VDGp9NzyKs-u9s0M-7UeW9Jg@mail.gmail.com>

Hi all,

The branch to switch to clang-format was just merged.

For those creating a new branch, you can use the script in
Utilities/Scripts/clang-format.bash to apply formatting before you commit
your changes.  You will need to have clang-format 3.8 or higher installed.

If you have any outstanding branches they will need to be rebased across
the transition.  The process to do this is:
1) Rebase your work on the empty commit prior to the transition
(609f2afcd5e2f963e4fe36203b08d2ebfc0476f9).  This will require you to fix
any changes that conflict with the doxygen style comment update.  ParaView
switched to /** style doxygen comments like VTK did last month.
2) Run `git filter-branch --tree-filter 'Utilties/Scripts/clang-format.bash
--tracked' 609f2afcd5e2f963e4fe36203b08d2ebfc0476f9~..HEAD`  This will
rewrite each commit from the empty commit to the top of your branch to have
the new format.  The empty commit's rewrite will become equivalent to the
convert-to-clang-format commit.
3) Run `git rebase b41d27999a4ac854f4a0e61d98d09c53e7583a60` to rebase your
branch onto the commit where the clang-format changes were merged.  The
"empty commit" should go away since all of its changes were applied by the
'apply clang-format' commit and only the rewritten commits in your branch
should remain.

That will get your branch rebased across the style transition.  You can
then rebase it on master or put it up for review if there are no further
conflicts.

Shawn
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20161019/3650d578/attachment.html>

From cory.quammen at kitware.com  Wed Oct 19 10:41:21 2016
From: cory.quammen at kitware.com (Cory Quammen)
Date: Wed, 19 Oct 2016 10:41:21 -0400
Subject: [Paraview-developers] ParaView 5.2.0-RC2 tagged
In-Reply-To: <CAB5Fpx6Ut=c1f4tE=JpQjLWp-AEiaaJcZj0aX_Gi42oS+v42tA@mail.gmail.com>
References: <CAB5Fpx5Hsq4tVfWG=u25GkfbQZE_fdeovhpHfX=A=4GBkTr4BA@mail.gmail.com>
 <CALSpCT1g9jy_sE0fX93aAdxEx+vLNQV=KXph++VNDK7-adaSUw@mail.gmail.com>
 <CAB5Fpx6Ut=c1f4tE=JpQjLWp-AEiaaJcZj0aX_Gi42oS+v42tA@mail.gmail.com>
Message-ID: <CAB5Fpx5bxw+Mqyu-cidzW+1b4yQrYt-TgqbpCANus0vkA9AUfw@mail.gmail.com>

Hi all,

It is okay to merge to ParaView master again. Thank you for your patience.

Please see Shawn's note sent out about an hour ago for how to rebase your
outstanding merge request branches on master to cross the large-scale
clang-format commits.

Thanks,
Cory


On Tue, Oct 18, 2016 at 10:13 PM, Cory Quammen <cory.quammen at kitware.com>
wrote:

> Shawn,
>
> That sounds like a good plan. The binaries should be built by Wednesday
> morning, so if you can work on it tomorrow and work out the kinks, that
> would be great.
>
> Thanks,
> Cory
>
> On Tue, Oct 18, 2016 at 4:41 PM, Shawn Waldon <shawn.waldon at kitware.com>
> wrote:
>
>> Cory,
>>
>> I am working on doxygen style conversion and clang-format update branches
>> for ParaView (similar to what Dave DeMarle and David Gobbi did for VTK last
>> month).  I'd like to try to get those merged during/just after this freeze
>> on merging if possible.  I've put links to the MRs below.  The doxygen
>> formatting one is rebased on master and I'm working on rebasing the
>> clang-format branch onto it now.  Can we wait to re-enable merges until
>> these have been tested and merge them first?
>>
>> Shawn
>>
>> clang-format: https://gitlab.kitware.com/par
>> aview/paraview/merge_requests/1097
>> documentation to /** doxygen style: https://gitlab.kitware.com/par
>> aview/paraview/merge_requests/1117
>>
>> On Tue, Oct 18, 2016 at 3:25 PM, Cory Quammen <cory.quammen at kitware.com>
>> wrote:
>>
>>> Folks,
>>>
>>> v5.2.0-RC2 has been tagged. Please do not merge anything into `master`
>>> until the dashboards have cycled through and been able to build to the
>>> binaries for this version.
>>>
>>> I'll send an email when it is okay to merge to `master` again.
>>>
>>> Thanks,
>>> Cory
>>>
>>> --
>>> Cory Quammen
>>> Staff R&D Engineer
>>> Kitware, Inc.
>>>
>>> _______________________________________________
>>> 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
>>>
>>>
>>
>
>
> --
> Cory Quammen
> Staff R&D Engineer
> Kitware, Inc.
>



-- 
Cory Quammen
Staff R&D Engineer
Kitware, Inc.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20161019/21d39e51/attachment-0001.html>

From utkarsh.ayachit at kitware.com  Wed Oct 19 12:52:28 2016
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Wed, 19 Oct 2016 12:52:28 -0400
Subject: [Paraview-developers] ParaView Hackathon - Oct 25, 2016
Message-ID: <CADHSJjDzAOD420ez3ouBcRyQrXgpK-R4NJkv11qBmd8C=gOXmw@mail.gmail.com>

Folks,

Reminder that we're having a ParaView hackathon on Oct 25th - 10 am - 5 pm (EDT)

I have the following list of people who have confirmed so far:

Dave DeMarle
Mathieu Westphal
Andy Bauer
Berk Geveci
Utkarsh Ayachit
Alan Scott

Please let me know if I've missed anyone especially if you're are
intending to attend at Kitware offices.

Thanks
Utkarsh

From cory.quammen at kitware.com  Wed Oct 19 14:42:29 2016
From: cory.quammen at kitware.com (Cory Quammen)
Date: Wed, 19 Oct 2016 14:42:29 -0400
Subject: [Paraview-developers] ParaView 5.2 Release Candidate 2 available
	for download
Message-ID: <CAB5Fpx7Lv0eRGtxG4HBANL_y=VTXW46_3of0yVeyZtsPCPJrkA@mail.gmail.com>

On behalf of the ParaView development team, I am happy to announce that
ParaView 5.2 Release Candidate 2 binaries and source tarballs are now
available for download at

http://www.paraview.org/download/

Please let us know if you encounter any problems with this release
 candidate.

Thanks,
Cory

-- 
Cory Quammen
Staff R&D Engineer
Kitware, Inc.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20161019/9c4b0d09/attachment.html>

From Oliver.Fernandes at visus.uni-stuttgart.de  Thu Oct 20 07:34:32 2016
From: Oliver.Fernandes at visus.uni-stuttgart.de (Oliver Fernandes)
Date: Thu, 20 Oct 2016 11:34:32 +0000
Subject: [Paraview-developers] Building a module pipeline offline
Message-ID: <1476963271072.10346@visus.uni-stuttgart.de>

Hello all,


I have a question regarding the component pipeline.

Is there an easy way to build this pipeline 'offline', i.e. not using the GUI, but by some third party code?


Stuff I have tried:

- I tried reverse-engineering the .pvsm state files, which seem to do exactly what I want, but without any specification describing them, this seems too tedious a  task. With some docs for the state file composition this would be my favored m.o.,i.e. being able to manually write state files.

- A colleague of mine also suggested using the python macro functionality, I have yet to look into that though.


Maybe there is an even better option I didn't think of.


Any advice would be great, thanks in advance!


BR,

Oliver
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20161020/698a0a42/attachment.html>

From dave.demarle at kitware.com  Thu Oct 20 07:42:23 2016
From: dave.demarle at kitware.com (David E DeMarle)
Date: Thu, 20 Oct 2016 07:42:23 -0400
Subject: [Paraview-developers] Building a module pipeline offline
In-Reply-To: <1476963271072.10346@visus.uni-stuttgart.de>
References: <1476963271072.10346@visus.uni-stuttgart.de>
Message-ID: <CANjZAi9vDhh5p2kiS4Tw1b+hK_8LkeaTiugmkQqxvkHKbWwXaw@mail.gmail.com>

python scripting (macro functionality) is the way to go.

Simplest way to get started is:
open gui
tools->Start Trace
do something in the gui
tools->Stop Trace
save that to filename.py
then from command prompt: "pvbatch filename.py"

See the documentation and tutorials for much more information.



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

On Thu, Oct 20, 2016 at 7:34 AM, Oliver Fernandes <
Oliver.Fernandes at visus.uni-stuttgart.de> wrote:

> Hello all,
>
>
> I have a question regarding the component pipeline.
>
> Is there an easy way to build this pipeline 'offline', i.e. not using the
> GUI, but by some third party code?
>
>
> Stuff I have tried:
>
> - I tried reverse-engineering the .pvsm state files, which seem to do
> exactly what I want, but without any specification describing them, this
> seems too tedious a  task. With some docs for the state file composition
> this would be my favored m.o.,i.e. being able to manually write state files.
>
> - A colleague of mine also suggested using the python macro functionality,
> I have yet to look into that though.
>
>
> Maybe there is an even better option I didn't think of.
>
>
> Any advice would be great, thanks in advance!
>
>
> BR,
>
> Oliver
>
> _______________________________________________
> 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-developers/attachments/20161020/019e4d3f/attachment.html>

From Oliver.Fernandes at visus.uni-stuttgart.de  Fri Oct 21 08:54:14 2016
From: Oliver.Fernandes at visus.uni-stuttgart.de (Oliver Fernandes)
Date: Fri, 21 Oct 2016 12:54:14 +0000
Subject: [Paraview-developers] Building a module pipeline offline
In-Reply-To: <CANjZAi9vDhh5p2kiS4Tw1b+hK_8LkeaTiugmkQqxvkHKbWwXaw@mail.gmail.com>
References: <1476963271072.10346@visus.uni-stuttgart.de>,
 <CANjZAi9vDhh5p2kiS4Tw1b+hK_8LkeaTiugmkQqxvkHKbWwXaw@mail.gmail.com>
Message-ID: <1477054451722.24649@visus.uni-stuttgart.de>

The python method works like a charm.

Thanks David & Grzegorz!

-Oli

________________________________
Von: David E DeMarle <dave.demarle at kitware.com>
Gesendet: Donnerstag, 20. Oktober 2016 13:42
An: Oliver Fernandes
Cc: paraview-developers at paraview.org
Betreff: Re: [Paraview-developers] Building a module pipeline offline

python scripting (macro functionality) is the way to go.

Simplest way to get started is:
open gui
tools->Start Trace
do something in the gui
tools->Stop Trace
save that to filename.py
then from command prompt: "pvbatch filename.py"

See the documentation and tutorials for much more information.



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

On Thu, Oct 20, 2016 at 7:34 AM, Oliver Fernandes <Oliver.Fernandes at visus.uni-stuttgart.de<mailto:Oliver.Fernandes at visus.uni-stuttgart.de>> wrote:

Hello all,


I have a question regarding the component pipeline.

Is there an easy way to build this pipeline 'offline', i.e. not using the GUI, but by some third party code?


Stuff I have tried:

- I tried reverse-engineering the .pvsm state files, which seem to do exactly what I want, but without any specification describing them, this seems too tedious a  task. With some docs for the state file composition this would be my favored m.o.,i.e. being able to manually write state files.

- A colleague of mine also suggested using the python macro functionality, I have yet to look into that though.


Maybe there is an even better option I didn't think of.


Any advice would be great, thanks in advance!


BR,

Oliver

_______________________________________________
Powered by www.kitware.com<http://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-developers/attachments/20161021/5214d0c0/attachment.html>

From sur.chiranjib at gmail.com  Fri Oct 21 13:56:20 2016
From: sur.chiranjib at gmail.com (Chiranjib Sur)
Date: Fri, 21 Oct 2016 23:26:20 +0530
Subject: [Paraview-developers] need some pointer for the Qt property
Message-ID: <CAJk8dSCBpXqWUEEgFTOs0NyabP63pH61OViDZaALMJqXJi+GSw@mail.gmail.com>

Hi,
I want to learn more about how the qt functionality is handled via
pqpropertywidget. For example, the below link from the wiki contains
details of the functionlity

the
http://www.paraview.org/Wiki/ParaView/Properties_Panel#pqPropertyWidgetDecorator_.28base-class:_QObject.29

Can anybody point me the source code of the above example (from he link)?

Thanks much in advance.
Chiranjib
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20161021/09adcebf/attachment.html>

From utkarsh.ayachit at kitware.com  Fri Oct 21 14:02:36 2016
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Fri, 21 Oct 2016 14:02:36 -0400
Subject: [Paraview-developers] need some pointer for the Qt property
In-Reply-To: <CAJk8dSCBpXqWUEEgFTOs0NyabP63pH61OViDZaALMJqXJi+GSw@mail.gmail.com>
References: <CAJk8dSCBpXqWUEEgFTOs0NyabP63pH61OViDZaALMJqXJi+GSw@mail.gmail.com>
Message-ID: <CADHSJjA1zzKwD0z0OS+WzWTX88N+zwtMzr7rmKTwWcLAGY0QUQ@mail.gmail.com>

Chiranjib,

Start with pqProxyWidget[1]. That's the class that iterates over all
properties on the proxy and then creates widgets for each property.

[1] https://gitlab.kitware.com/paraview/paraview/blob/master/Qt/Components/pqProxyWidget.cxx

On Fri, Oct 21, 2016 at 1:56 PM, Chiranjib Sur <sur.chiranjib at gmail.com> wrote:
> Hi,
> I want to learn more about how the qt functionality is handled via
> pqpropertywidget. For example, the below link from the wiki contains details
> of the functionlity
>
> the
> http://www.paraview.org/Wiki/ParaView/Properties_Panel#pqPropertyWidgetDecorator_.28base-class:_QObject.29
>
> Can anybody point me the source code of the above example (from he link)?
>
> Thanks much in advance.
> Chiranjib
>
> _______________________________________________
> 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 sur.chiranjib at gmail.com  Fri Oct 21 14:25:56 2016
From: sur.chiranjib at gmail.com (Chiranjib Sur)
Date: Fri, 21 Oct 2016 23:55:56 +0530
Subject: [Paraview-developers] need some pointer for the Qt property
In-Reply-To: <CADHSJjA1zzKwD0z0OS+WzWTX88N+zwtMzr7rmKTwWcLAGY0QUQ@mail.gmail.com>
References: <CAJk8dSCBpXqWUEEgFTOs0NyabP63pH61OViDZaALMJqXJi+GSw@mail.gmail.com>
 <CADHSJjA1zzKwD0z0OS+WzWTX88N+zwtMzr7rmKTwWcLAGY0QUQ@mail.gmail.com>
Message-ID: <CAJk8dSD=GTgQA+Tt-+7VAkT2rwpi5VMPYXoaTh4SYVOvgGJxLg@mail.gmail.com>

Thanks Utkarsh, I started looking at this. Is there a quick example where I
can learn how these classes are used. For example in the wiki, "*Extract
CTH Parts* filter" is referenced. Can you point me towards the .cxx files
for this filter, where the qt frame decorators are used?
Chiranjib

On Fri, Oct 21, 2016 at 11:32 PM, Utkarsh Ayachit <
utkarsh.ayachit at kitware.com> wrote:

> Chiranjib,
>
> Start with pqProxyWidget[1]. That's the class that iterates over all
> properties on the proxy and then creates widgets for each property.
>
> [1] https://gitlab.kitware.com/paraview/paraview/blob/master/
> Qt/Components/pqProxyWidget.cxx
>
> On Fri, Oct 21, 2016 at 1:56 PM, Chiranjib Sur <sur.chiranjib at gmail.com>
> wrote:
> > Hi,
> > I want to learn more about how the qt functionality is handled via
> > pqpropertywidget. For example, the below link from the wiki contains
> details
> > of the functionlity
> >
> > the
> > http://www.paraview.org/Wiki/ParaView/Properties_Panel#
> pqPropertyWidgetDecorator_.28base-class:_QObject.29
> >
> > Can anybody point me the source code of the above example (from he link)?
> >
> > Thanks much in advance.
> > Chiranjib
> >
> > _______________________________________________
> > 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-developers/attachments/20161021/5dafaa4f/attachment.html>

From thomasblome at startmail.com  Sat Oct 22 13:46:34 2016
From: thomasblome at startmail.com (thomasblome at startmail.com)
Date: Sat, 22 Oct 2016 19:46:34 +0200
Subject: [Paraview-developers] Linker error building Fortran90FullExample
Message-ID: <bdb3e5da01c90c8d2364af520a915e91.startmail@www.startmail.com>

Hello,

I'm trying to compile the Fortran90FullExample using MSVS (Intel 
Fortran Compiler 2017 and Visual C++ 2015 compiler).
Doing so I'm getting following linker error:

Error?? ?LNK2019?? ?unresolved external symbol main referenced in 
function "int __cdecl __scrt_common_main_seh(void)" 
(?__scrt_common_main_seh@@YAHXZ)?? ?Fortran90FullExample.

Obviously, the source code doesn't contain a main method at all, since 
the entry point is given by the fortran program in file 'FEDriver.f90'.
Nevertheless, I guess the compiler internally creates a main method, 
and the linker cannot resolve the reference due to a name mangling 
problem, as there are different compilers involved. But I'm not quite 
sure about that, nor how to solve it, at that matter.

Can you give me a hint how to solve that problem?

Kind regards,
Thomas
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20161022/9f4e7fc6/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 7F53DEC77F67D0E0.asc
Type: application/pgp-keys
Size: 3082 bytes
Desc: OpenPGP public keys
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20161022/9f4e7fc6/attachment.key>

From andy.bauer at kitware.com  Mon Oct 24 16:00:50 2016
From: andy.bauer at kitware.com (Andy Bauer)
Date: Mon, 24 Oct 2016 16:00:50 -0400
Subject: [Paraview-developers] Linker error building Fortran90FullExample
In-Reply-To: <bdb3e5da01c90c8d2364af520a915e91.startmail@www.startmail.com>
References: <bdb3e5da01c90c8d2364af520a915e91.startmail@www.startmail.com>
Message-ID: <CAMaOp+E6JdB43qcYoKPVMRuGX+aUyzV_wXZ8mNdP4AkqyY-w6Q@mail.gmail.com>

Hi Thomas,

If you change from coproc to main in the "program" and "end program" lines
in FEDriver.f90 does that fix the problem?

I'm working on a fix for this but don't have access to any MSVS compilers.

Thanks,
Andy

On Sat, Oct 22, 2016 at 1:46 PM, <thomasblome at startmail.com> wrote:

> Hello,
>
> I'm trying to compile the Fortran90FullExample using MSVS (Intel Fortran
> Compiler 2017 and Visual C++ 2015 compiler).
> Doing so I'm getting following linker error:
>
> Error    LNK2019    unresolved external symbol main referenced in function
> "int __cdecl __scrt_common_main_seh(void)" (?__scrt_common_main_seh@@YAHXZ)
>  Fortran90FullExample.
>
> Obviously, the source code doesn't contain a main method at all, since the
> entry point is given by the fortran program in file 'FEDriver.f90'.
> Nevertheless, I guess the compiler internally creates a main method, and
> the linker cannot resolve the reference due to a name mangling problem, as
> there are different compilers involved. But I'm not quite sure about that,
> nor how to solve it, at that matter.
>
> Can you give me a hint how to solve that problem?
>
> Kind regards,
> Thomas
>
> _______________________________________________
> 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-developers/attachments/20161024/d219afa5/attachment.html>

From dlawrie at ara.co.uk  Tue Oct 25 06:15:28 2016
From: dlawrie at ara.co.uk (David Lawrie)
Date: Tue, 25 Oct 2016 10:15:28 +0000
Subject: [Paraview-developers] Problem using vtkSetStringMacro with
	StringListDomain
Message-ID: <D327EFC022902140A6E855DC8604CCFB5B5B03EF@sooty3.win.ara>

Dear list,

I am trying to set up a filter and having some difficulty with the XML for the ServerManager.

I have set up a filter which, at construction, generates a list of strings. This list should populate a
combobox in the GUI. This part appears to work. However when I select an option from the list
the SetChosenOne method does not appear to be called. I have SetDebug(1) in the constructor
but no vtkDebug statements are being generated by the method.
The current approach I am trying is below:

<StringVectorProperty name="ChosenOne" command="SetChosenOne">
  <StringListDomain name="List">
    <RequiredProperties>
      <Property function="StringList" name="AvailableOptionsInfo"/>
    </RequiredProperties>
  </StringListDomain>
</StringVectorProperty>
<StringVectorProperty name="AvailableOptionsInfo" command="GetAvailableOptions" information_only="1" si_class="vtkSIDataArrayProperty" />

The SetChosenOne method is generated using vtkSetStringMacro(ChosenOne).

Any ideas as to what I am doing wrong?

Thanks,
David.

**********************************************************************
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

**********************************************************************
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20161025/84112abe/attachment.html>

From wascott at sandia.gov  Tue Oct 25 16:40:46 2016
From: wascott at sandia.gov (Scott, W Alan)
Date: Tue, 25 Oct 2016 20:40:46 +0000
Subject: [Paraview-developers] kudos for ParaView
Message-ID: <4cf6044f97234e1d875af004f6e51c97@ES01AMSNLNT.srn.sandia.gov>

All,
I just had a project manager for an FE code in my office.  He has previously complained (gently and graciously) about the confusing nature of ParaView.  He says he hears this from all of the DoE and also DoD labs.  He said that in many ways, VisIt is a better tool than ParaView.  So, we went through his points one by one.  Mainly, his issues have to do with the complexity and poor documentation of ParaView.  I showed him the new Help menu (incredibly improved by Cory in 5.1.0), the training resources from Ken and Sandia, the User's Guide (thanks to Utkarsh and many others), the trace recorder, and the new getting started guide (once again, new in 5.1.0, and complements to Cory).  He basically folded up his sheet of paper, said "wow".  Before going out the door, he asked about CTH.  I showed him the extractCTHParts filter and Material Interface Filter.  More wows.  Finally, he mentioned Catalyst, and I showed him the CoProcessing state writer.  Once again, very complementary.  He then went off to tell his folks what he had seen

My action items - none.  User - left impressed.  We did well.

Good job everyone.

Alan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20161025/4cb9bc32/attachment.html>

From thomasblome at startmail.com  Wed Oct 26 03:39:00 2016
From: thomasblome at startmail.com (thomasblome at startmail.com)
Date: Wed, 26 Oct 2016 09:39:00 +0200
Subject: [Paraview-developers] Linker error building Fortran90FullExample
In-Reply-To: <CAMaOp+E6JdB43qcYoKPVMRuGX+aUyzV_wXZ8mNdP4AkqyY-w6Q@mail.gmail.com>
References: <bdb3e5da01c90c8d2364af520a915e91.startmail@www.startmail.com>
 <CAMaOp+E6JdB43qcYoKPVMRuGX+aUyzV_wXZ8mNdP4AkqyY-w6Q@mail.gmail.com>
Message-ID: <37e92c2e377a8c1121402c7a06a64c23.startmail@www.startmail.com>

Hi Andy,

I have changed both lines from coproc to main, but the error message 
remains the same.

Best,
Thomas
?
Am Montag, 24. Oktober 2016 22:00 schrieb Andy Bauer 
<andy.bauer at kitware.com>:
?
> Hi Thomas,
> ?
> If you change from coproc to main in the "program" and "end program" 
> lines in FEDriver.f90 does that fix the problem?
> ?
> I'm working on a fix for this but don't have access to any MSVS 
> compilers.
> ?
> Thanks,
> Andy
> ?
> On Sat, Oct 22, 2016 at 1:46 PM, <thomasblome at startmail.com> wrote:
>> Hello,
>> 
>> I'm trying to compile the Fortran90FullExample using MSVS (Intel 
>> Fortran Compiler 2017 and Visual C++ 2015 compiler).
>> Doing so I'm getting following linker error:
>> 
>> Error?? ?LNK2019?? ?unresolved external symbol main referenced in 
>> function "int __cdecl __scrt_common_main_seh(void)" 
>> (?__scrt_common_main_seh@@YAHXZ)?? ?Fortran90FullExample.
>> 
>> Obviously, the source code doesn't contain a main method at all, 
>> since the entry point is given by the fortran program in file 
>> 'FEDriver.f90'.
>> Nevertheless, I guess the compiler internally creates a main method, 
>> and the linker cannot resolve the reference due to a name mangling 
>> problem, as there are different compilers involved. But I'm not 
>> quite sure about that, nor how to solve it, at that matter.
>> 
>> Can you give me a hint how to solve that problem?
>> 
>> Kind regards,
>> Thomas
>> _______________________________________________
>> Powered by www.kitware.com <http://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-developers/attachments/20161026/2eb6e9e1/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 7F53DEC77F67D0E0.asc
Type: application/pgp-keys
Size: 3082 bytes
Desc: OpenPGP public keys
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20161026/2eb6e9e1/attachment.key>

From jfavre at cscs.ch  Wed Oct 26 07:50:24 2016
From: jfavre at cscs.ch (Favre  Jean)
Date: Wed, 26 Oct 2016 11:50:24 +0000
Subject: [Paraview-developers] =?windows-1252?q?vtkOSPRayRendererNode=2Ecx?=
 =?windows-1252?q?x=3A_error=3A_=91isnan=92_was_not_declared?=
Message-ID: <0EB9B6375711A04B820E6B6F5CCA9F6843718AE4@MBX111.d.ethz.ch>

Hello developers

I switched to a new machine with a newer compiler.

g++ (Ubuntu 5.4.0) does not like

vtkOSPRayRendererNode.cxx:124:36: error: ?isnan? was not declared in this scope

I corrected to the following line to make it compile cleanly:

if (std::isnan(ospDepthBuffer[i]))

This is both in ParaView master, and 5.2RC2

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

From utkarsh.ayachit at kitware.com  Wed Oct 26 08:27:14 2016
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Wed, 26 Oct 2016 08:27:14 -0400
Subject: [Paraview-developers] kudos for ParaView
In-Reply-To: <4cf6044f97234e1d875af004f6e51c97@ES01AMSNLNT.srn.sandia.gov>
References: <4cf6044f97234e1d875af004f6e51c97@ES01AMSNLNT.srn.sandia.gov>
Message-ID: <CADHSJjDYnsYP2_2iv1Xju7OXfzmbGWUwGOFhAjBScXiTtCMTCQ@mail.gmail.com>

That's nice to hear! Thanks for sharing, Alan. Glad we're heading in the
right direction :).

On Tue, Oct 25, 2016 at 4:40 PM, Scott, W Alan <wascott at sandia.gov> wrote:

> All,
>
> I just had a project manager for an FE code in my office.  He has
> previously complained (gently and graciously) about the confusing nature of
> ParaView.  He says he hears this from all of the DoE and also DoD labs.  He
> said that in many ways, VisIt is a better tool than ParaView.  So, we went
> through his points one by one.  Mainly, his issues have to do with the
> complexity and poor documentation of ParaView.  I showed him the new Help
> menu (incredibly improved by Cory in 5.1.0), the training resources from
> Ken and Sandia, the User?s Guide (thanks to Utkarsh and many others), the
> trace recorder, and the new getting started guide (once again, new in
> 5.1.0, and complements to Cory).  He basically folded up his sheet of
> paper, said ?wow?.  Before going out the door, he asked about CTH.  I
> showed him the extractCTHParts filter and Material Interface Filter.  More
> wows.  Finally, he mentioned Catalyst, and I showed him the CoProcessing
> state writer.  Once again, very complementary.  He then went off to tell
> his folks what he had seen
>
>
>
> My action items ? none.  User ? left impressed.  We did well.
>
>
>
> Good job everyone.
>
>
>
> Alan
>
> _______________________________________________
> 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-developers/attachments/20161026/8af6b56b/attachment-0001.html>

From dave.demarle at kitware.com  Wed Oct 26 08:29:34 2016
From: dave.demarle at kitware.com (David E DeMarle)
Date: Wed, 26 Oct 2016 08:29:34 -0400
Subject: [Paraview-developers] kudos for ParaView
In-Reply-To: <CADHSJjDYnsYP2_2iv1Xju7OXfzmbGWUwGOFhAjBScXiTtCMTCQ@mail.gmail.com>
References: <4cf6044f97234e1d875af004f6e51c97@ES01AMSNLNT.srn.sandia.gov>
 <CADHSJjDYnsYP2_2iv1Xju7OXfzmbGWUwGOFhAjBScXiTtCMTCQ@mail.gmail.com>
Message-ID: <CANjZAi87CFw04jKPU88QeRyTgkVtS6u3RTVn4icK5LJu8yBZKw@mail.gmail.com>

We've come a long way from ParaView 2's Help button.
As I recall that popped up a dialog that said "Buy the book". ;)


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

On Wed, Oct 26, 2016 at 8:27 AM, Utkarsh Ayachit <
utkarsh.ayachit at kitware.com> wrote:

> That's nice to hear! Thanks for sharing, Alan. Glad we're heading in the
> right direction :).
>
> On Tue, Oct 25, 2016 at 4:40 PM, Scott, W Alan <wascott at sandia.gov> wrote:
>
>> All,
>>
>> I just had a project manager for an FE code in my office.  He has
>> previously complained (gently and graciously) about the confusing nature of
>> ParaView.  He says he hears this from all of the DoE and also DoD labs.  He
>> said that in many ways, VisIt is a better tool than ParaView.  So, we went
>> through his points one by one.  Mainly, his issues have to do with the
>> complexity and poor documentation of ParaView.  I showed him the new Help
>> menu (incredibly improved by Cory in 5.1.0), the training resources from
>> Ken and Sandia, the User?s Guide (thanks to Utkarsh and many others), the
>> trace recorder, and the new getting started guide (once again, new in
>> 5.1.0, and complements to Cory).  He basically folded up his sheet of
>> paper, said ?wow?.  Before going out the door, he asked about CTH.  I
>> showed him the extractCTHParts filter and Material Interface Filter.  More
>> wows.  Finally, he mentioned Catalyst, and I showed him the CoProcessing
>> state writer.  Once again, very complementary.  He then went off to tell
>> his folks what he had seen
>>
>>
>>
>> My action items ? none.  User ? left impressed.  We did well.
>>
>>
>>
>> Good job everyone.
>>
>>
>>
>> Alan
>>
>> _______________________________________________
>> 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-developers/attachments/20161026/04d2adeb/attachment.html>

From dave.demarle at kitware.com  Wed Oct 26 08:31:50 2016
From: dave.demarle at kitware.com (David E DeMarle)
Date: Wed, 26 Oct 2016 08:31:50 -0400
Subject: [Paraview-developers]
	=?utf-8?q?vtkOSPRayRendererNode=2Ecxx=3A_er?=
	=?utf-8?b?cm9yOiDigJhpc25hbuKAmSB3YXMgbm90IGRlY2xhcmVk?=
In-Reply-To: <0EB9B6375711A04B820E6B6F5CCA9F6843718AE4@MBX111.d.ethz.ch>
References: <0EB9B6375711A04B820E6B6F5CCA9F6843718AE4@MBX111.d.ethz.ch>
Message-ID: <CANjZAi-sZnU1pSu0PLzAHRbMBgAjh2n0RYDsoefQmz=ERWJFAQ@mail.gmail.com>

Thanks Jean.

Mind filing a issue report on VTK's gitlab to help me keep track of this?

https://gitlab.kitware.com/vtk/vtk/issues

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

On Wed, Oct 26, 2016 at 7:50 AM, Favre Jean <jfavre at cscs.ch> wrote:

> Hello developers
>
> I switched to a new machine with a newer compiler.
>
> g++ (Ubuntu 5.4.0) does not like
>
> vtkOSPRayRendererNode.cxx:124:36: error: ?isnan? was not declared in this
> scope
>
> I corrected to the following line to make it compile cleanly:
>
> if (std::isnan(ospDepthBuffer[i]))
>
> This is both in ParaView master, and 5.2RC2
>
> -----------------
> Jean
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at http://www.kitware.com/opensou
> rce/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-developers/attachments/20161026/8094379c/attachment.html>

From haocheng.liu at kitware.com  Wed Oct 26 08:52:43 2016
From: haocheng.liu at kitware.com (Haocheng Liu)
Date: Wed, 26 Oct 2016 08:52:43 -0400
Subject: [Paraview-developers]
	=?utf-8?q?vtkOSPRayRendererNode=2Ecxx=3A_er?=
	=?utf-8?b?cm9yOiDigJhpc25hbuKAmSB3YXMgbm90IGRlY2xhcmVk?=
In-Reply-To: <CANjZAi-sZnU1pSu0PLzAHRbMBgAjh2n0RYDsoefQmz=ERWJFAQ@mail.gmail.com>
References: <0EB9B6375711A04B820E6B6F5CCA9F6843718AE4@MBX111.d.ethz.ch>
 <CANjZAi-sZnU1pSu0PLzAHRbMBgAjh2n0RYDsoefQmz=ERWJFAQ@mail.gmail.com>
Message-ID: <CACbTE7MsUHzUe79fsVEFxr0_c8NG1f8sthH7eSh4C0K7EA-Weg@mail.gmail.com>

On Wed, Oct 26, 2016 at 8:31 AM, David E DeMarle <dave.demarle at kitware.com>
wrote:

> Thanks Jean.
>
> Mind filing a issue report on VTK's gitlab to help me keep track of this?
>
> https://gitlab.kitware.com/vtk/vtk/issues
>
> David E DeMarle
> Kitware, Inc.
> R&D Engineer
> 21 Corporate Drive
> Clifton Park, NY 12065-8662
> Phone: 518-881-4909
>
> On Wed, Oct 26, 2016 at 7:50 AM, Favre Jean <jfavre at cscs.ch> wrote:
>
>> Hello developers
>>
>> I switched to a new machine with a newer compiler.
>>
>> g++ (Ubuntu 5.4.0) does not like
>>
>> vtkOSPRayRendererNode.cxx:124:36: error: ?isnan? was not declared in
>> this scope
>>
>> I corrected to the following line to make it compile cleanly:
>>
>> if (std::isnan(ospDepthBuffer[i]))
>>
>> This is both in ParaView master, and 5.2RC2
>>
> Hi all,

I encountered the  same isnan problem when working on CMB projects, and
here is my solution to solve the problem once for all:

```C++
#if defined (__GNUC__) && (__GNUC__ > 4) && (__cplusplus)
#  include <cmath>
using std::isnan;
#else
#  include <math.h>
#endif
```

It works fine on Ubuntu 14.04(with GCC4.8) and Ubuntu 16.04(with GCC
5.4.1). Mac and Windows are also happy with it.

Hope it helps.


>
>>
>
>> -----------------
>> Jean
>>
>> _______________________________________________
>> 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
>
>


-- 
Best regards
Haocheng
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20161026/1241e9b7/attachment.html>

From utkarsh.ayachit at kitware.com  Wed Oct 26 09:06:24 2016
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Wed, 26 Oct 2016 09:06:24 -0400
Subject: [Paraview-developers] Problem using vtkSetStringMacro with
	StringListDomain
In-Reply-To: <D327EFC022902140A6E855DC8604CCFB5B5B03EF@sooty3.win.ara>
References: <D327EFC022902140A6E855DC8604CCFB5B5B03EF@sooty3.win.ara>
Message-ID: <CADHSJjAOVQm5GwYg=5b4u_LW83F7sQ7-1R2fB7T1vyu_EeMncg@mail.gmail.com>

>.... However when I select an option from the list
> the SetChosenOne method does not appear to be called.

Try setting number_of_elements="1" and "default_values="" on the
<StringVectorProperty ..> element.

Does that work?

Utkarsh

From dlawrie at ara.co.uk  Wed Oct 26 09:45:26 2016
From: dlawrie at ara.co.uk (David Lawrie)
Date: Wed, 26 Oct 2016 13:45:26 +0000
Subject: [Paraview-developers] Problem using vtkSetStringMacro with
 StringListDomain
In-Reply-To: <CADHSJjAOVQm5GwYg=5b4u_LW83F7sQ7-1R2fB7T1vyu_EeMncg@mail.gmail.com>
References: <D327EFC022902140A6E855DC8604CCFB5B5B03EF@sooty3.win.ara> 
 <CADHSJjAOVQm5GwYg=5b4u_LW83F7sQ7-1R2fB7T1vyu_EeMncg@mail.gmail.com>
Message-ID: <D327EFC022902140A6E855DC8604CCFB5B5B06D8@sooty3.win.ara>

Hi Utkarsh,

That appears to solve the issue as I can now see the SetChosenOne debug output appear when I click apply.

Is it possible to link the chosen value to another StringVectorProperty as I intend for this combobox to provide 
the keys to a map<string:string> and provide the value for editing/acceptance by the user? 

Thanks,

David

-----Original Message-----
From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] 
Sent: 26 October 2016 14:06
To: David Lawrie
Cc: paraview-developers at paraview.org
Subject: Re: [Paraview-developers] Problem using vtkSetStringMacro with StringListDomain

>.... However when I select an option from the list  the SetChosenOne 
>method does not appear to be called.

Try setting number_of_elements="1" and "default_values="" on the <StringVectorProperty ..> element.

Does that work?

Utkarsh

**********************************************************************
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 dave.demarle at kitware.com  Wed Oct 26 10:22:49 2016
From: dave.demarle at kitware.com (David E DeMarle)
Date: Wed, 26 Oct 2016 10:22:49 -0400
Subject: [Paraview-developers]
	=?utf-8?q?vtkOSPRayRendererNode=2Ecxx=3A_er?=
	=?utf-8?b?cm9yOiDigJhpc25hbuKAmSB3YXMgbm90IGRlY2xhcmVk?=
In-Reply-To: <CACbTE7MsUHzUe79fsVEFxr0_c8NG1f8sthH7eSh4C0K7EA-Weg@mail.gmail.com>
References: <0EB9B6375711A04B820E6B6F5CCA9F6843718AE4@MBX111.d.ethz.ch>
 <CANjZAi-sZnU1pSu0PLzAHRbMBgAjh2n0RYDsoefQmz=ERWJFAQ@mail.gmail.com>
 <CACbTE7MsUHzUe79fsVEFxr0_c8NG1f8sthH7eSh4C0K7EA-Weg@mail.gmail.com>
Message-ID: <CANjZAi9z_FymNfwYnMK=6cq7eTY8tejVijeDqU3wpnJmF6BwGw@mail.gmail.com>

better yet vtkMath::IsNan()

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

On Wed, Oct 26, 2016 at 8:52 AM, Haocheng Liu <haocheng.liu at kitware.com>
wrote:

>
>
> On Wed, Oct 26, 2016 at 8:31 AM, David E DeMarle <dave.demarle at kitware.com
> > wrote:
>
>> Thanks Jean.
>>
>> Mind filing a issue report on VTK's gitlab to help me keep track of this?
>>
>> https://gitlab.kitware.com/vtk/vtk/issues
>>
>> David E DeMarle
>> Kitware, Inc.
>> R&D Engineer
>> 21 Corporate Drive
>> Clifton Park, NY 12065-8662
>> Phone: 518-881-4909
>>
>> On Wed, Oct 26, 2016 at 7:50 AM, Favre Jean <jfavre at cscs.ch> wrote:
>>
>>> Hello developers
>>>
>>> I switched to a new machine with a newer compiler.
>>>
>>> g++ (Ubuntu 5.4.0) does not like
>>>
>>> vtkOSPRayRendererNode.cxx:124:36: error: ?isnan? was not declared in
>>> this scope
>>>
>>> I corrected to the following line to make it compile cleanly:
>>>
>>> if (std::isnan(ospDepthBuffer[i]))
>>>
>>> This is both in ParaView master, and 5.2RC2
>>>
>> Hi all,
>
> I encountered the  same isnan problem when working on CMB projects, and
> here is my solution to solve the problem once for all:
>
> ```C++
> #if defined (__GNUC__) && (__GNUC__ > 4) && (__cplusplus)
> #  include <cmath>
> using std::isnan;
> #else
> #  include <math.h>
> #endif
> ```
>
> It works fine on Ubuntu 14.04(with GCC4.8) and Ubuntu 16.04(with GCC
> 5.4.1). Mac and Windows are also happy with it.
>
> Hope it helps.
>
>
>>
>>>
>>
>>> -----------------
>>> Jean
>>>
>>> _______________________________________________
>>> 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
>>
>>
>
>
> --
> Best regards
> Haocheng
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20161026/ce6a3b77/attachment.html>

From wascott at sandia.gov  Wed Oct 26 13:24:27 2016
From: wascott at sandia.gov (Scott, W Alan)
Date: Wed, 26 Oct 2016 17:24:27 +0000
Subject: [Paraview-developers] [EXTERNAL] Re:  kudos for ParaView
In-Reply-To: <CANjZAi87CFw04jKPU88QeRyTgkVtS6u3RTVn4icK5LJu8yBZKw@mail.gmail.com>
References: <4cf6044f97234e1d875af004f6e51c97@ES01AMSNLNT.srn.sandia.gov>
 <CADHSJjDYnsYP2_2iv1Xju7OXfzmbGWUwGOFhAjBScXiTtCMTCQ@mail.gmail.com>
 <CANjZAi87CFw04jKPU88QeRyTgkVtS6u3RTVn4icK5LJu8yBZKw@mail.gmail.com>
Message-ID: <f447b4b732c54ea082511d4b1182f44f@ES01AMSNLNT.srn.sandia.gov>

If I remember correctly, the popup often failed.

Yes, we have come a long way.

From: David E DeMarle [mailto:dave.demarle at kitware.com]
Sent: Wednesday, October 26, 2016 6:30 AM
To: Utkarsh Ayachit <utkarsh.ayachit at kitware.com>
Cc: Scott, W Alan <wascott at sandia.gov>; paraview-developers at paraview.org
Subject: [EXTERNAL] Re: [Paraview-developers] kudos for ParaView

We've come a long way from ParaView 2's Help button.
As I recall that popped up a dialog that said "Buy the book". ;)


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

On Wed, Oct 26, 2016 at 8:27 AM, Utkarsh Ayachit <utkarsh.ayachit at kitware.com<mailto:utkarsh.ayachit at kitware.com>> wrote:
That's nice to hear! Thanks for sharing, Alan. Glad we're heading in the right direction :).

On Tue, Oct 25, 2016 at 4:40 PM, Scott, W Alan <wascott at sandia.gov<mailto:wascott at sandia.gov>> wrote:
All,
I just had a project manager for an FE code in my office.  He has previously complained (gently and graciously) about the confusing nature of ParaView.  He says he hears this from all of the DoE and also DoD labs.  He said that in many ways, VisIt is a better tool than ParaView.  So, we went through his points one by one.  Mainly, his issues have to do with the complexity and poor documentation of ParaView.  I showed him the new Help menu (incredibly improved by Cory in 5.1.0), the training resources from Ken and Sandia, the User?s Guide (thanks to Utkarsh and many others), the trace recorder, and the new getting started guide (once again, new in 5.1.0, and complements to Cory).  He basically folded up his sheet of paper, said ?wow?.  Before going out the door, he asked about CTH.  I showed him the extractCTHParts filter and Material Interface Filter.  More wows.  Finally, he mentioned Catalyst, and I showed him the CoProcessing state writer.  Once again, very complementary.  He then went off to tell his folks what he had seen

My action items ? none.  User ? left impressed.  We did well.

Good job everyone.

Alan

_______________________________________________
Powered by www.kitware.com<http://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<http://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-developers/attachments/20161026/df029437/attachment.html>

From andy.bauer at kitware.com  Wed Oct 26 13:47:28 2016
From: andy.bauer at kitware.com (Andy Bauer)
Date: Wed, 26 Oct 2016 13:47:28 -0400
Subject: [Paraview-developers] Linker error building Fortran90FullExample
In-Reply-To: <37e92c2e377a8c1121402c7a06a64c23.startmail@www.startmail.com>
References: <bdb3e5da01c90c8d2364af520a915e91.startmail@www.startmail.com>
 <CAMaOp+E6JdB43qcYoKPVMRuGX+aUyzV_wXZ8mNdP4AkqyY-w6Q@mail.gmail.com>
 <37e92c2e377a8c1121402c7a06a64c23.startmail@www.startmail.com>
Message-ID: <CAMaOp+GoGEu2D08YvwQxQf56FR5Ghh8OHigEDKof=xPu70wuNw@mail.gmail.com>

Hi Thomas,

I really don't know about this. Do you get the same behavior if you don't
link with Catalyst? Can you create a simple helloworld.f90 example that
works?

Best,
Andy

On Wed, Oct 26, 2016 at 3:39 AM, <thomasblome at startmail.com> wrote:

> Hi Andy,
>
> I have changed both lines from coproc to main, but the error message
> remains the same.
>
> Best,
> Thomas
>
> Am Montag, 24. Oktober 2016 22:00 schrieb Andy Bauer <
> andy.bauer at kitware.com>:
>
>
> Hi Thomas,
>
> If you change from coproc to main in the "program" and "end program" lines
> in FEDriver.f90 does that fix the problem?
>
> I'm working on a fix for this but don't have access to any MSVS compilers.
>
> Thanks,
> Andy
>
> On Sat, Oct 22, 2016 at 1:46 PM, <thomasblome at startmail.com> wrote:
>
> Hello,
>
> I'm trying to compile the Fortran90FullExample using MSVS (Intel Fortran
> Compiler 2017 and Visual C++ 2015 compiler).
> Doing so I'm getting following linker error:
>
> Error    LNK2019    unresolved external symbol main referenced in function
> "int __cdecl __scrt_common_main_seh(void)" (?__scrt_common_main_seh@@YAHXZ)
>  Fortran90FullExample.
>
> Obviously, the source code doesn't contain a main method at all, since the
> entry point is given by the fortran program in file 'FEDriver.f90'.
> Nevertheless, I guess the compiler internally creates a main method, and
> the linker cannot resolve the reference due to a name mangling problem, as
> there are different compilers involved. But I'm not quite sure about that,
> nor how to solve it, at that matter.
>
> Can you give me a hint how to solve that problem?
>
> Kind regards,
> Thomas
>
> _______________________________________________
> 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-developers/attachments/20161026/8ec0af48/attachment.html>

From cory.quammen at kitware.com  Fri Oct 28 16:27:20 2016
From: cory.quammen at kitware.com (Cory Quammen)
Date: Fri, 28 Oct 2016 16:27:20 -0400
Subject: [Paraview-developers] ParaView 5.2.0-RC3 tagged
Message-ID: <CAB5Fpx6iW_73c9Gxc6hR5oCmfTZBXuFxYwGsU=rc-HQ4WGMgQQ@mail.gmail.com>

Folks,

v5.2.0-RC3 has been tagged. Please do not merge anything into `master`
until the dashboards have cycled through and been able to build to the
binaries for this version.

I'll send an email when it is okay to merge to `master` again.

Thanks,
Cory

-- 
Cory Quammen
Staff R&D Engineer
Kitware, Inc.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20161028/45a14aea/attachment.html>

From orion at cora.nwra.com  Sun Oct 30 10:34:28 2016
From: orion at cora.nwra.com (Orion Poplawski)
Date: Sun, 30 Oct 2016 08:34:28 -0600
Subject: [Paraview-developers] New build failure with 5.2.0-RC3
Message-ID: <20adb49c-8b48-1b81-c98c-fc86ec8575d2@cora.nwra.com>

This appears to be new with RC3 (over RC2);

[ 48%] Building CXX object 
VTK/Rendering/GL2PSOpenGL2/CMakeFiles/vtkRenderingGL2PSOpenGL2.dir/vtkOpenGLGL2PSHelperImpl.cxx.o
cd 
/builddir/build/BUILD/ParaView-v5.2.0-RC3/i686-redhat-linux-gnu/VTK/Rendering/GL2PSOpenGL2 
&& /usr/bin/c++   -DVTK_IN_VTK -DvtkRenderingGL2PSOpenGL2_EXPORTS 
-I/builddir/build/BUILD/ParaView-v5.2.0-RC3/i686-redhat-linux-gnu 
-I/builddir/build/BUILD/ParaView-v5.2.0-RC3/i686-redhat-linux-gnu/VTK/Rendering/GL2PSOpenGL2 
-I/builddir/build/BUILD/ParaView-v5.2.0-RC3/VTK/Rendering/GL2PSOpenGL2 
-I/builddir/build/BUILD/ParaView-v5.2.0-RC3/i686-redhat-linux-gnu/VTK/Common/Core 
-I/builddir/build/BUILD/ParaView-v5.2.0-RC3/VTK/Common/Core 
-I/builddir/build/BUILD/ParaView-v5.2.0-RC3/i686-redhat-linux-gnu/VTK/Utilities/KWIML 
-I/builddir/build/BUILD/ParaView-v5.2.0-RC3/VTK/Utilities/KWIML 
-I/builddir/build/BUILD/ParaView-v5.2.0-RC3/i686-redhat-linux-gnu/VTK/Utilities/KWSys 
-I/builddir/build/BUILD/ParaView-v5.2.0-RC3/VTK/Utilities/KWSys 
-I/builddir/build/BUILD/ParaView-v5.2.0-RC3/i686-redhat-linux-gnu/VTK/Common/DataModel 
-I/builddir/build/BUILD/ParaView-v5.2.0-RC3/VTK/Common/DataModel 
-I/builddir/build/BUILD/ParaView-v5.2.0-RC3/i686-redhat-linux-gnu/VTK/Common/Math 
-I/builddir/build/BUILD/ParaView-v5.2.0-RC3/VTK/Common/Math 
-I/builddir/build/BUILD/ParaView-v5.2.0-RC3/i686-redhat-linux-gnu/VTK/Common/Misc 
-I/builddir/build/BUILD/ParaView-v5.2.0-RC3/VTK/Common/Misc 
-I/builddir/build/BUILD/ParaView-v5.2.0-RC3/i686-redhat-linux-gnu/VTK/Common/System 
-I/builddir/build/BUILD/ParaView-v5.2.0-RC3/VTK/Common/System 
-I/builddir/build/BUILD/ParaView-v5.2.0-RC3/i686-redhat-linux-gnu/VTK/Common/Transforms 
-I/builddir/build/BUILD/ParaView-v5.2.0-RC3/VTK/Common/Transforms 
-I/builddir/build/BUILD/ParaView-v5.2.0-RC3/i686-redhat-linux-gnu/VTK/Rendering/Core 
-I/builddir/build/BUILD/ParaView-v5.2.0-RC3/VTK/Rendering/Core 
-I/builddir/build/BUILD/ParaView-v5.2.0-RC3/i686-redhat-linux-gnu/VTK/Common/Color 
-I/builddir/build/BUILD/ParaView-v5.2.0-RC3/VTK/Common/Color 
-I/builddir/build/BUILD/ParaView-v5.2.0-RC3/i686-redhat-linux-gnu/VTK/Common/ComputationalGeometry 
-I/builddir/build/BUILD/ParaView-v5.2.0-RC3/VTK/Common/ComputationalGeometry 
-I/builddir/build/BUILD/ParaView-v5.2.0-RC3/i686-redhat-linux-gnu/VTK/Common/ExecutionModel 
-I/builddir/build/BUILD/ParaView-v5.2.0-RC3/VTK/Common/ExecutionModel 
-I/builddir/build/BUILD/ParaView-v5.2.0-RC3/i686-redhat-linux-gnu/VTK/Filters/Core 
-I/builddir/build/BUILD/ParaView-v5.2.0-RC3/VTK/Filters/Core 
-I/builddir/build/BUILD/ParaView-v5.2.0-RC3/i686-redhat-linux-gnu/VTK/Filters/General 
-I/builddir/build/BUILD/ParaView-v5.2.0-RC3/VTK/Filters/General 
-I/builddir/build/BUILD/ParaView-v5.2.0-RC3/i686-redhat-linux-gnu/VTK/Filters/Geometry 
-I/builddir/build/BUILD/ParaView-v5.2.0-RC3/VTK/Filters/Geometry 
-I/builddir/build/BUILD/ParaView-v5.2.0-RC3/i686-redhat-linux-gnu/VTK/Filters/Sources 
-I/builddir/build/BUILD/ParaView-v5.2.0-RC3/VTK/Filters/Sources 
-I/builddir/build/BUILD/ParaView-v5.2.0-RC3/i686-redhat-linux-gnu/VTK/Rendering/OpenGL2 
-I/builddir/build/BUILD/ParaView-v5.2.0-RC3/VTK/Rendering/OpenGL2 
-I/builddir/build/BUILD/ParaView-v5.2.0-RC3/i686-redhat-linux-gnu/VTK/IO/Image 
-I/builddir/build/BUILD/ParaView-v5.2.0-RC3/VTK/IO/Image 
-I/builddir/build/BUILD/ParaView-v5.2.0-RC3/i686-redhat-linux-gnu/VTK/Utilities/DICOMParser 
-I/builddir/build/BUILD/ParaView-v5.2.0-RC3/VTK/Utilities/DICOMParser 
-I/builddir/build/BUILD/ParaView-v5.2.0-RC3/i686-redhat-linux-gnu/VTK/Utilities/MetaIO/vtkmetaio 
-I/builddir/build/BUILD/ParaView-v5.2.0-RC3/i686-redhat-linux-gnu/VTK/Utilities/MetaIO 
-I/builddir/build/BUILD/ParaView-v5.2.0-RC3/VTK/Utilities/MetaIO 
-I/builddir/build/BUILD/ParaView-v5.2.0-RC3/i686-redhat-linux-gnu/VTK/ThirdParty/zlib 
-I/builddir/build/BUILD/ParaView-v5.2.0-RC3/VTK/ThirdParty/zlib 
-I/builddir/build/BUILD/ParaView-v5.2.0-RC3/i686-redhat-linux-gnu/VTK/ThirdParty/jpeg 
-I/builddir/build/BUILD/ParaView-v5.2.0-RC3/VTK/ThirdParty/jpeg 
-I/builddir/build/BUILD/ParaView-v5.2.0-RC3/i686-redhat-linux-gnu/VTK/ThirdParty/png 
-I/builddir/build/BUILD/ParaView-v5.2.0-RC3/VTK/ThirdParty/png 
-I/builddir/build/BUILD/ParaView-v5.2.0-RC3/i686-redhat-linux-gnu/VTK/ThirdParty/tiff 
-I/builddir/build/BUILD/ParaView-v5.2.0-RC3/VTK/ThirdParty/tiff 
-I/builddir/build/BUILD/ParaView-v5.2.0-RC3/i686-redhat-linux-gnu/VTK/Imaging/Core 
-I/builddir/build/BUILD/ParaView-v5.2.0-RC3/VTK/Imaging/Core 
-I/builddir/build/BUILD/ParaView-v5.2.0-RC3/i686-redhat-linux-gnu/VTK/Utilities/EncodeString 
-I/builddir/build/BUILD/ParaView-v5.2.0-RC3/VTK/Utilities/EncodeString 
-I/builddir/build/BUILD/ParaView-v5.2.0-RC3/i686-redhat-linux-gnu/VTK/ThirdParty/glew 
-I/builddir/build/BUILD/ParaView-v5.2.0-RC3/VTK/ThirdParty/glew 
-I/builddir/build/BUILD/ParaView-v5.2.0-RC3/i686-redhat-linux-gnu/VTK/ThirdParty/gl2ps 
-I/builddir/build/BUILD/ParaView-v5.2.0-RC3/VTK/ThirdParty/gl2ps  -O2 -g 
-pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -fexceptions 
-fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches 
-specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -m32 -march=i686 
-mtune=atom -fasynchronous-unwind-tables   -O2 -g -DNDEBUG -fPIC 
-fvisibility=hidden   -o 
CMakeFiles/vtkRenderingGL2PSOpenGL2.dir/vtkOpenGLGL2PSHelperImpl.cxx.o 
-c 
/builddir/build/BUILD/ParaView-v5.2.0-RC3/VTK/Rendering/GL2PSOpenGL2/vtkOpenGLGL2PSHelperImpl.cxx
/builddir/build/BUILD/ParaView-v5.2.0-RC3/VTK/Rendering/GL2PSOpenGL2/vtkOpenGLGL2PSHelperImpl.cxx: 
In member function 'virtual void 
vtkOpenGLGL2PSHelperImpl::ProcessTransformFeedback(vtkTransformFeedback*, 
vtkRenderer*, float*)':
/builddir/build/BUILD/ParaView-v5.2.0-RC3/VTK/Rendering/GL2PSOpenGL2/vtkOpenGLGL2PSHelperImpl.cxx:114:3: 
error: 'GL2PSvertex' was not declared in this scope
    GL2PSvertex verts[3];
    ^~~~~~~~~~~
/builddir/build/BUILD/ParaView-v5.2.0-RC3/VTK/Rendering/GL2PSOpenGL2/vtkOpenGLGL2PSHelperImpl.cxx:123:18: 
error: 'vert' was not declared in this scope
      GL2PSvertex &vert = verts[curVert];
                   ^~~~
/builddir/build/BUILD/ParaView-v5.2.0-RC3/VTK/Rendering/GL2PSOpenGL2/vtkOpenGLGL2PSHelperImpl.cxx:123:25: 
error: 'verts' was not declared in this scope
      GL2PSvertex &vert = verts[curVert];
                          ^~~~~
/builddir/build/BUILD/ParaView-v5.2.0-RC3/VTK/Rendering/GL2PSOpenGL2/vtkOpenGLGL2PSHelperImpl.cxx:185:31: 
error: 'GL2PS_POINT' was not declared in this scope
          gl2psAddPolyPrimitive(GL2PS_POINT, 1, verts, 0, 0.f, 0.f, 
0xffff, 1,
                                ^~~~~~~~~~~
/builddir/build/BUILD/ParaView-v5.2.0-RC3/VTK/Rendering/GL2PSOpenGL2/vtkOpenGLGL2PSHelperImpl.cxx:186:43: 
error: 'gl2psAddPolyPrimitive' was not declared in this scope
                                pointSize, 0);
                                            ^
/builddir/build/BUILD/ParaView-v5.2.0-RC3/VTK/Rendering/GL2PSOpenGL2/vtkOpenGLGL2PSHelperImpl.cxx:193:33: 
error: 'GL2PS_LINE' was not declared in this scope
            gl2psAddPolyPrimitive(GL2PS_LINE, 2, verts, 0, 0.f, 0.f,
                                  ^~~~~~~~~~
/builddir/build/BUILD/ParaView-v5.2.0-RC3/VTK/Rendering/GL2PSOpenGL2/vtkOpenGLGL2PSHelperImpl.cxx:202:33: 
error: 'GL2PS_TRIANGLE' was not declared in this scope
            gl2psAddPolyPrimitive(GL2PS_TRIANGLE, 3, verts, 0, 0.f, 0.f, 
0xffff,
                                  ^~~~~~~~~~~~~~
/builddir/build/BUILD/ParaView-v5.2.0-RC3/VTK/Rendering/GL2PSOpenGL2/vtkOpenGLGL2PSHelperImpl.cxx: 
In member function 'virtual void 
vtkOpenGLGL2PSHelperImpl::DrawString(const string&, vtkTextProperty*, 
double*, double, vtkRenderer*)':
/builddir/build/BUILD/ParaView-v5.2.0-RC3/VTK/Rendering/GL2PSOpenGL2/vtkOpenGLGL2PSHelperImpl.cxx:245:7: 
error: 'GL2PSvertex' was not declared in this scope
        GL2PSvertex bgVerts[5];
        ^~~~~~~~~~~
/builddir/build/BUILD/ParaView-v5.2.0-RC3/VTK/Rendering/GL2PSOpenGL2/vtkOpenGLGL2PSHelperImpl.cxx:250:39: 
error: 'bgVerts' was not declared in this scope
        std::copy(bgColor, bgColor + 4, bgVerts[0].rgba);
                                        ^~~~~~~
/builddir/build/BUILD/ParaView-v5.2.0-RC3/VTK/Rendering/GL2PSOpenGL2/vtkOpenGLGL2PSHelperImpl.cxx:272:29: 
error: 'GL2PS_TRIANGLE' was not declared in this scope
        gl2psAddPolyPrimitive(GL2PS_TRIANGLE, 3, bgVerts,     0, 0, 0, 
0xffff, 0,
                              ^~~~~~~~~~~~~~
/builddir/build/BUILD/ParaView-v5.2.0-RC3/VTK/Rendering/GL2PSOpenGL2/vtkOpenGLGL2PSHelperImpl.cxx:273:33: 
error: 'gl2psAddPolyPrimitive' was not declared in this scope
                              0, 0);
                                  ^
/builddir/build/BUILD/ParaView-v5.2.0-RC3/VTK/Rendering/GL2PSOpenGL2/vtkOpenGLGL2PSHelperImpl.cxx:302:5: 
error: 'GL2PSvertex' was not declared in this scope
      GL2PSvertex gl2psRasterPos;
      ^~~~~~~~~~~
/builddir/build/BUILD/ParaView-v5.2.0-RC3/VTK/Rendering/GL2PSOpenGL2/vtkOpenGLGL2PSHelperImpl.cxx:303:5: 
error: 'gl2psRasterPos' was not declared in this scope
      gl2psRasterPos.xyz[0] = static_cast<float>(pos[0]);
      ^~~~~~~~~~~~~~
/builddir/build/BUILD/ParaView-v5.2.0-RC3/VTK/Rendering/GL2PSOpenGL2/vtkOpenGLGL2PSHelperImpl.cxx:310:40: 
error: 'gl2psForceRasterPos' was not declared in this scope
      gl2psForceRasterPos(&gl2psRasterPos);
                                         ^
/builddir/build/BUILD/ParaView-v5.2.0-RC3/VTK/Rendering/GL2PSOpenGL2/vtkOpenGLGL2PSHelperImpl.cxx: 
In member function 'virtual void 
vtkOpenGLGL2PSHelperImpl::DrawImage(vtkImageData*, double*)':
/builddir/build/BUILD/ParaView-v5.2.0-RC3/VTK/Rendering/GL2PSOpenGL2/vtkOpenGLGL2PSHelperImpl.cxx:419:3: 
error: 'GL2PSvertex' was not declared in this scope
    GL2PSvertex gl2psRasterPos;
    ^~~~~~~~~~~
/builddir/build/BUILD/ParaView-v5.2.0-RC3/VTK/Rendering/GL2PSOpenGL2/vtkOpenGLGL2PSHelperImpl.cxx:420:3: 
error: 'gl2psRasterPos' was not declared in this scope
    gl2psRasterPos.xyz[0] = static_cast<float>(pos[0]);
    ^~~~~~~~~~~~~~
/builddir/build/BUILD/ParaView-v5.2.0-RC3/VTK/Rendering/GL2PSOpenGL2/vtkOpenGLGL2PSHelperImpl.cxx:431:38: 
error: 'gl2psForceRasterPos' was not declared in this scope
    gl2psForceRasterPos(&gl2psRasterPos);
                                       ^
/builddir/build/BUILD/ParaView-v5.2.0-RC3/VTK/Rendering/GL2PSOpenGL2/vtkOpenGLGL2PSHelperImpl.cxx: 
In member function 'void vtkOpenGLGL2PSHelperImpl::DrawPathPS(vtkPath*, 
double*, double*, unsigned char*, double*, double, float, const string&)':
/builddir/build/BUILD/ParaView-v5.2.0-RC3/VTK/Rendering/GL2PSOpenGL2/vtkOpenGLGL2PSHelperImpl.cxx:860:3: 
error: 'GL2PSvertex' was not declared in this scope
    GL2PSvertex gl2psRasterPos;
    ^~~~~~~~~~~
/builddir/build/BUILD/ParaView-v5.2.0-RC3/VTK/Rendering/GL2PSOpenGL2/vtkOpenGLGL2PSHelperImpl.cxx:861:3: 
error: 'gl2psRasterPos' was not declared in this scope
    gl2psRasterPos.xyz[0] = static_cast<float>(rasterPos[0]);
    ^~~~~~~~~~~~~~
/builddir/build/BUILD/ParaView-v5.2.0-RC3/VTK/Rendering/GL2PSOpenGL2/vtkOpenGLGL2PSHelperImpl.cxx:868:38: 
error: 'gl2psForceRasterPos' was not declared in this scope
    gl2psForceRasterPos(&gl2psRasterPos);
                                       ^
/builddir/build/BUILD/ParaView-v5.2.0-RC3/VTK/Rendering/GL2PSOpenGL2/vtkOpenGLGL2PSHelperImpl.cxx: 
In member function 'void vtkOpenGLGL2PSHelperImpl::DrawPathPDF(vtkPath*, 
double*, double*, unsigned char*, double*, double, float, const string&)':
/builddir/build/BUILD/ParaView-v5.2.0-RC3/VTK/Rendering/GL2PSOpenGL2/vtkOpenGLGL2PSHelperImpl.cxx:1017:3: 
error: 'GL2PSvertex' was not declared in this scope
    GL2PSvertex gl2psRasterPos;
    ^~~~~~~~~~~
/builddir/build/BUILD/ParaView-v5.2.0-RC3/VTK/Rendering/GL2PSOpenGL2/vtkOpenGLGL2PSHelperImpl.cxx:1018:3: 
error: 'gl2psRasterPos' was not declared in this scope
    gl2psRasterPos.xyz[0] = static_cast<float>(rasterPos[0]);
    ^~~~~~~~~~~~~~
/builddir/build/BUILD/ParaView-v5.2.0-RC3/VTK/Rendering/GL2PSOpenGL2/vtkOpenGLGL2PSHelperImpl.cxx:1025:38: 
error: 'gl2psForceRasterPos' was not declared in this scope
    gl2psForceRasterPos(&gl2psRasterPos);
                                       ^
/builddir/build/BUILD/ParaView-v5.2.0-RC3/VTK/Rendering/GL2PSOpenGL2/vtkOpenGLGL2PSHelperImpl.cxx: 
In member function 'void vtkOpenGLGL2PSHelperImpl::DrawPathSVG(vtkPath*, 
double*, double*, unsigned char*, double*, double, float, const string&)':
/builddir/build/BUILD/ParaView-v5.2.0-RC3/VTK/Rendering/GL2PSOpenGL2/vtkOpenGLGL2PSHelperImpl.cxx:1177:3: 
error: 'GL2PSvertex' was not declared in this scope
    GL2PSvertex gl2psRasterPos;
    ^~~~~~~~~~~
/builddir/build/BUILD/ParaView-v5.2.0-RC3/VTK/Rendering/GL2PSOpenGL2/vtkOpenGLGL2PSHelperImpl.cxx:1178:3: 
error: 'gl2psRasterPos' was not declared in this scope
    gl2psRasterPos.xyz[0] = static_cast<float>(rasterPos[0]);
    ^~~~~~~~~~~~~~
/builddir/build/BUILD/ParaView-v5.2.0-RC3/VTK/Rendering/GL2PSOpenGL2/vtkOpenGLGL2PSHelperImpl.cxx:1185:38: 
error: 'gl2psForceRasterPos' was not declared in this scope
    gl2psForceRasterPos(&gl2psRasterPos);
                                       ^
make[2]: *** 
[VTK/Rendering/GL2PSOpenGL2/CMakeFiles/vtkRenderingGL2PSOpenGL2.dir/build.make:77: 
VTK/Rendering/GL2PSOpenGL2/CMakeFiles/vtkRenderingGL2PSOpenGL2.dir/vtkOpenGLGL2PSHelperImpl.cxx.o] 
Error 1

-- 
Orion Poplawski
Technical Manager                     303-415-9701 x222
NWRA/CoRA Division                    FAX: 303-415-9702
3380 Mitchell Lane                  orion at cora.nwra.com
Boulder, CO 80301              http://www.cora.nwra.com

From ben.boeckel at kitware.com  Mon Oct 31 09:22:34 2016
From: ben.boeckel at kitware.com (Ben Boeckel)
Date: Mon, 31 Oct 2016 09:22:34 -0400
Subject: [Paraview-developers] New build failure with 5.2.0-RC3
In-Reply-To: <20adb49c-8b48-1b81-c98c-fc86ec8575d2@cora.nwra.com>
References: <20adb49c-8b48-1b81-c98c-fc86ec8575d2@cora.nwra.com>
Message-ID: <20161031132234.GA5084@megas.kitware.com>

On Sun, Oct 30, 2016 at 08:34:28 -0600, Orion Poplawski wrote:
> This appears to be new with RC3 (over RC2);

VTK updated its GL2PS requirements; the patches we need has been
submitted upstream, but has not been released yet.

    http://www.geuz.org/pipermail/gl2ps/2016/000429.html
    http://www.geuz.org/pipermail/gl2ps/2016/000424.html

--Ben

From cory.quammen at kitware.com  Mon Oct 31 11:53:55 2016
From: cory.quammen at kitware.com (Cory Quammen)
Date: Mon, 31 Oct 2016 11:53:55 -0400
Subject: [Paraview-developers] ParaView 5.2.0-RC3 tagged
In-Reply-To: <CAB5Fpx6iW_73c9Gxc6hR5oCmfTZBXuFxYwGsU=rc-HQ4WGMgQQ@mail.gmail.com>
References: <CAB5Fpx6iW_73c9Gxc6hR5oCmfTZBXuFxYwGsU=rc-HQ4WGMgQQ@mail.gmail.com>
Message-ID: <CAB5Fpx76vb9gQ-oFxfbp2aCT+Y7dZZ2ObJ1zqbAn2FgJXK1=ZA@mail.gmail.com>

The binaries for v5.2.0-RC3 have been generated. Please feel free to merge
to ParaView master again.

Thanks,
Cory

On Fri, Oct 28, 2016 at 4:27 PM, Cory Quammen <cory.quammen at kitware.com>
wrote:

> Folks,
>
> v5.2.0-RC3 has been tagged. Please do not merge anything into `master`
> until the dashboards have cycled through and been able to build to the
> binaries for this version.
>
> I'll send an email when it is okay to merge to `master` again.
>
> Thanks,
> Cory
>
> --
> Cory Quammen
> Staff R&D Engineer
> Kitware, Inc.
>



-- 
Cory Quammen
Staff R&D Engineer
Kitware, Inc.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20161031/bb246fa0/attachment.html>

From joachim.pouderoux at kitware.com  Mon Oct 31 14:06:26 2016
From: joachim.pouderoux at kitware.com (Joachim Pouderoux)
Date: Mon, 31 Oct 2016 14:06:26 -0400
Subject: [Paraview-developers] Proxy Property names & labels
Message-ID: <CACJ=gTiLqSx-irkKhM2TsdTjwb3yeSvKit0S0QB+DF-q4UxHyw@mail.gmail.com>

Hi,

Writing a python script for PV5.2, I needed to save a temporal ptvtu file
and faced this problem again: looking at the proxy's XML definition, the
writer has the *name=*WriteAllTimeSteps property.

      <IntVectorProperty command="SetWriteAllTimeSteps"
                         default_values="0"
                         label="Write all timesteps as file-series"
                         name="WriteAllTimeSteps"
                         number_of_elements="1">

So I tried something like this:

  SaveData("test.pvtu", WriteAllTimeSteps=1)

But it failed claiming that the writer has no WriteAllTimeSteps property!
Well, looking at the help() on the writer instance it looked like indeed,
the exposed python property is not call WriteAllTimeSteps but
Writealltimestepsasfileseries:
 |  Writealltimestepsasfileseries
 |      When WriteAllTimeSteps is turned ON, the writer is
 |      executed once for each timestep available from the
 |      reader.

Isn't it ugly?
So is the choice of exposing the property using its concatenated label a
deliberate choice or a bug?
It seems to me very unnatural, the label should be reserved for better
human readable UI printing.

What do you think?

Best,

*Joachim Pouderoux*, PhD

*Technical Expert - Scientific Computing Team*
*Kitware SAS <http://www.kitware.fr>*
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20161031/6df37547/attachment.html>

From cory.quammen at kitware.com  Mon Oct 31 16:48:20 2016
From: cory.quammen at kitware.com (Cory Quammen)
Date: Mon, 31 Oct 2016 16:48:20 -0400
Subject: [Paraview-developers] ParaView 5.2 Release Candidate 3 available
	for download
Message-ID: <CAB5Fpx4DOO4W-crxLkYxrv23efupxrE61YdUf2T=j3x95jnqGA@mail.gmail.com>

On behalf of the ParaView development team, I am pleased to announce
that ParaView 5.2 Release Candidate 3 binaries and source tarballs are
now available for download at

http://www.paraview.org/download/

Please let us know if you encounter any problems with this release candidate.

Thanks,
Cory

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

From ZiganshinShagit at hotmail.com  Mon Oct 31 16:47:47 2016
From: ZiganshinShagit at hotmail.com (=?koi8-r?B?+snHwc7byc4g+8HHydQ=?=)
Date: Mon, 31 Oct 2016 20:47:47 +0000
Subject: [Paraview-developers] Collapse in pqPipelineBrowserWidget
Message-ID: <DB5PR1001MB0872A90095593E6C9CC9E9B4A8AE0@DB5PR1001MB0872.EURPRD10.PROD.OUTLOOK.COM>

Hi!

I'm tryng to implement autocollapse in pipeline browser, but overriding pqPipelineBrowserWidget::expandWithModelIndexTranslation or implement my method for autocollapse cause crashes, e.g

void pqPipelineBrowserWidget::collapseWithModelTranslation(const QModelIndex& index)
{
  this->collapse(this->FilteredPipelineModel->mapFromSource(index));
}


this method calling by a signal in pqPipelineModel::addChild. The signal emitts like a pqPipelineModel::firstChildAdded signal, but my signal calls when row count is more than 0.

Where did I go wrong?


Shagit Ziganshin
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20161031/bfbcf1f4/attachment.html>

From utkarsh.ayachit at kitware.com  Mon Oct 31 17:16:11 2016
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Mon, 31 Oct 2016 17:16:11 -0400
Subject: [Paraview-developers] Proxy Property names & labels
In-Reply-To: <CACJ=gTiLqSx-irkKhM2TsdTjwb3yeSvKit0S0QB+DF-q4UxHyw@mail.gmail.com>
References: <CACJ=gTiLqSx-irkKhM2TsdTjwb3yeSvKit0S0QB+DF-q4UxHyw@mail.gmail.com>
Message-ID: <CADHSJjDnCp+uMgnFPSWOpywoh8ZTe3jzs=bEoFFV7s9rB0Q+1Q@mail.gmail.com>

When we started, we indeed used the property's XMLName as the name for
the parameter in the Python script. However, it was noted that the
parameter name in Python would not match what the user saw in the UI
and hence he had no clue how to look for it. Hence, we changed it such
that the Python parameter name uses label instead.

This would not have been an issue if a property's (or proxy's) name
and label are the same, however this didn't happen for historical
reasons.

Now changing property names after the fact is harder since we need to
ensure backwards compability for pvsm and py files.

Utkarsh

On Mon, Oct 31, 2016 at 2:06 PM, Joachim Pouderoux
<joachim.pouderoux at kitware.com> wrote:
> Hi,
>
> Writing a python script for PV5.2, I needed to save a temporal ptvtu file
> and faced this problem again: looking at the proxy's XML definition, the
> writer has the name=WriteAllTimeSteps property.
>
>       <IntVectorProperty command="SetWriteAllTimeSteps"
>                          default_values="0"
>                          label="Write all timesteps as file-series"
>                          name="WriteAllTimeSteps"
>                          number_of_elements="1">
>
> So I tried something like this:
>
>   SaveData("test.pvtu", WriteAllTimeSteps=1)
>
> But it failed claiming that the writer has no WriteAllTimeSteps property!
> Well, looking at the help() on the writer instance it looked like indeed,
> the exposed python property is not call WriteAllTimeSteps but
> Writealltimestepsasfileseries:
>  |  Writealltimestepsasfileseries
>  |      When WriteAllTimeSteps is turned ON, the writer is
>  |      executed once for each timestep available from the
>  |      reader.
>
> Isn't it ugly?
> So is the choice of exposing the property using its concatenated label a
> deliberate choice or a bug?
> It seems to me very unnatural, the label should be reserved for better human
> readable UI printing.
>
> What do you think?
>
> Best,
>
> Joachim Pouderoux, PhD
>
> Technical Expert - Scientific Computing Team
> Kitware SAS
>
>
> _______________________________________________
> 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
>