From mzhao at cea-igp.ac.cn  Sat Apr  1 07:01:55 2017
From: mzhao at cea-igp.ac.cn (=?gbk?B?1dTD9w==?=)
Date: Sat, 1 Apr 2017 19:01:55 +0800
Subject: [Paraview-developers] No in situ visualization of the catalyst
	examples
Message-ID: <4b884ee5ac7ce6a8a543cb3df7b01d11@cea-igp.ac.cn>

Hi everyone,

I run the examples in ParaViewCatalyst4.3ExampleCode,and the VTK grid and VTK fields are generated correctly,but the live visualization seems to have some problem.It is like this:

[zm at centos7 SampleScripts]$ ../../build/CxxFullExample/CxxFullExample feslicecinema.py 

And I run paraview catalyst on the command line and make it listen at port 22222

[zm at centos7 bin]$ ./paraview

Accepting connection(s): centos7.destop:22222
Accepting connection(s): centos7.destop:22222
Invalid output port : pqPipelineSource::getOutputPort( 0 ). Available number of output ports:  0 
Aborted (core dumped)

Then Paraview exit and without any live visualization output.Anyone has any idea of this?The catalyst is claimed to have the ability to give in situ outputs...

Best regards
Ming
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20170401/740176ce/attachment.html>

From andy.bauer at kitware.com  Sat Apr  1 12:22:50 2017
From: andy.bauer at kitware.com (Andy Bauer)
Date: Sat, 1 Apr 2017 12:22:50 -0400
Subject: [Paraview-developers] No in situ visualization of the catalyst
	examples
In-Reply-To: <4b884ee5ac7ce6a8a543cb3df7b01d11@cea-igp.ac.cn>
References: <4b884ee5ac7ce6a8a543cb3df7b01d11@cea-igp.ac.cn>
Message-ID: <CAMaOp+FnDnaM1Dj3ztLV0_g94S4pyo2dfNm3yLa1+Uz5ZV3gUQ@mail.gmail.com>

Hi,

ParaView 4.3 is fairly old with respect to Catalyst. Catalyst Live
functionality has been significantly improved since 4.3 as well. Do you
have similar errors when using ParaView 5.3? Also, the  client and the
Catalyst build that you link against must match versions.

Cheers,
Andy

On Sat, Apr 1, 2017 at 7:01 AM, ?? <mzhao at cea-igp.ac.cn> wrote:

> Hi everyone,
>
> I run the examples in ParaViewCatalyst4.3ExampleCode,and the VTK grid and
> VTK fields are generated correctly,but the live visualization seems to have
> some problem.It is like this:
>
> [zm at centos7 SampleScripts]$ ../../build/CxxFullExample/CxxFullExample
> feslicecinema.py
>
> And I run paraview catalyst on the command line and make it listen at port
> 22222
>
> [zm at centos7 bin]$ ./paraview
>
> Accepting connection(s): centos7.destop:22222
> Accepting connection(s): centos7.destop:22222
> Invalid output port : pqPipelineSource::getOutputPort( 0 ). Available
> number of output ports:  0
> Aborted (core dumped)
>
> Then Paraview exit and without any live visualization output.Anyone has
> any idea of this?The catalyst is claimed to have the ability to give in
> situ outputs...
>
> Best regards
> Ming
>
> _______________________________________________
> 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/20170401/bed2d56b/attachment.html>

From joachim.pouderoux at kitware.com  Sun Apr  2 20:58:48 2017
From: joachim.pouderoux at kitware.com (Joachim Pouderoux)
Date: Sun, 2 Apr 2017 20:58:48 -0400
Subject: [Paraview-developers] failed to compile Cosmo
In-Reply-To: <0EB9B6375711A04B820E6B6F5CCA9F684383C921@MBX211.d.ethz.ch>
References: <0EB9B6375711A04B820E6B6F5CCA9F684383C921@MBX211.d.ethz.ch>
Message-ID: <CACJ=gTiELkv=wcH1D8djLU5ZXvBzL70n1iS8Wsnks7kYzvGcTw@mail.gmail.com>

Jean,

Please give a try to the GenericIO we provide for building ParaView
superbuild:
http://www.paraview.org/files/dependencies/genericio-master-a15ffc76cfa9f9674f933e8cb5ffc97a97fd7b27.zip

Best,
Joachim

*Joachim Pouderoux*, PhD

*Technical Expert - Scientific Computing Team*
*Kitware SAS <http://www.kitware.fr>*


2017-03-30 8:08 GMT-04:00 Favre Jean <jfavre at cscs.ch>:

>
> Developers
>
> I'd like to compile the CosmoHaloFinder, with parallel support.
>
> compilation fails with the error:
>
> ThirdParty/CosmoHaloFinder/FOFDistribute.cxx:59:32: fatal error:
> GenericIOMPIReader.h: No such file or directory
>
> I have looked for that file, have browsed the ANL site (
> http://trac.alcf.anl.gov/projects/genericio) but cannot find it anywhere.
>
> ParaView web page [1] lists at least a couple of Halo finder options, but
> it is not clear to me how to build them.
>
> [1] http://www.paraview.org/astro-physics/
>
> -----------------
> Jean/CSCS
>
> _______________________________________________
> 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/20170402/b964b378/attachment.html>

From mzhao at cea-igp.ac.cn  Sun Apr  2 22:17:49 2017
From: mzhao at cea-igp.ac.cn (=?utf-8?B?6LW15piO?=)
Date: Mon, 3 Apr 2017 10:17:49 +0800
Subject: [Paraview-developers] No in situ visualization of the catalyst
	examples
In-Reply-To: <CAMaOp+FnDnaM1Dj3ztLV0_g94S4pyo2dfNm3yLa1+Uz5ZV3gUQ@mail.gmail.com>
References: <4b884ee5ac7ce6a8a543cb3df7b01d11@cea-igp.ac.cn>,
 <CAMaOp+FnDnaM1Dj3ztLV0_g94S4pyo2dfNm3yLa1+Uz5ZV3gUQ@mail.gmail.com>
Message-ID: <b3edab9dbd0d56ab4478be4e25849fd9@cea-igp.ac.cn>

Hi Bauer,

I would love to try  ParaView 5.3.The only problem is I never succeed with superbuild,it always gives me this error :

$ make -j 16
......
[ 96%] Performing configure step for 'paraview'
Not searching for unused variables given on the command line.
-- The C compiler identification is GNU 4.8.5
-- The CXX compiler identification is GNU 4.8.5
......
-- Found HDF5: hdf5 (found version "1.8.13") found components:  C HL 
.......
-- Plugin: VaporPlugin - Plugin to read NCAR VDR files : Disabled
-- Found PythonInterp: /home/zm/Desktop/paraview-superbuild/build_paraview/install/bin/python2.7 (found version "2.7.11") 
CMake Error at CommandLineExecutables/CMakeLists.txt:77 (get_property):
  get_property could not find TARGET hdf5.  Perhaps it has not yet been
  created.
......

The wired thing is:I chose Enable_hdf5 and it actually found hdf5,and it still told me there is no hdf5..

Best
Ming
--------- Original Message ---------
From: "Andy Bauer" <andy.bauer at kitware.com>
To: "??" <mzhao at cea-igp.ac.cn>
Cc: "paraview-developers at paraview.org" <paraview-developers at paraview.org>
Subject: Re: [Paraview-developers] No in situ visualization of the catalyst examples
Date: 04/02/2017 00:22:52 (Sun)

Hi,

ParaView 4.3 is fairly old with respect to Catalyst. Catalyst Live functionality has been significantly improved since 4.3 as well. Do you have similar errors when using ParaView 5.3? Also, the  client and the Catalyst build that you link against must match versions.

Cheers,
Andy

On Sat, Apr 1, 2017 at 7:01 AM, ?? <mzhao at cea-igp.ac.cn> wrote:
CxxFullExample feslicecinema.py 

And I run paraview catalyst on the command line and make it listen at port 22222

[zm at centos7 bin]$ ./paraview

Accepting connection(s): centos7.destop:22222
Accepting connection(s): centos7.destop:22222
Invalid output port : pqPipelineSource::getOutputPort( 0 ). Available number of output ports:  0 
Aborted (core dumped)

Then Paraview exit and without any live visualization output.Anyone has any idea of this?The catalyst is claimed to have the ability to give in situ outputs...

Best regards
Ming

_______________________________________________

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/20170403/7d7abce0/attachment.html>

From daanvanvugt at gmail.com  Mon Apr  3 04:34:40 2017
From: daanvanvugt at gmail.com (Daan van Vugt)
Date: Mon, 3 Apr 2017 10:34:40 +0200
Subject: [Paraview-developers] H5py in paraview python
In-Reply-To: <CADHSJjAMZdeL3GescDmk+fuJohQJmbSxpSwF2oZJ1KPFKn5iZQ@mail.gmail.com>
References: <CAAyVbOD8OWSLzQEquRUFpyZS0vP-LEvy8c+rnbdN50QbPQiAYg@mail.gmail.com>
 <CADHSJjAMZdeL3GescDmk+fuJohQJmbSxpSwF2oZJ1KPFKn5iZQ@mail.gmail.com>
Message-ID: <CAAyVbOAt7pUje2_TkMiL5rjjHOCHEkhr2D2-E7Gm32VskQht4A@mail.gmail.com>

Perhaps a more general (but maybe not easier) solution would be to include
pip in the paraview python environment?
Then users can install additional modules themselves. We have been trying
to include h5py in a binary windows install of Paraview and are having
quite some troubles.

Best,
Daan

On Wed, Mar 22, 2017 at 6:05 PM, Utkarsh Ayachit <
utkarsh.ayachit at kitware.com> wrote:

> It's indeed a great suggestion -- something I've been thinking of
> doing, but never got around to it. Ben, how hard would it be?
>
> On Wed, Mar 22, 2017 at 12:34 PM, Daan van Vugt <daanvanvugt at gmail.com>
> wrote:
> > Hi,
> >
> > Just a quick question: Would it be possible to include h5py in the
> ParaView
> > distribution?
> > It would make the development of file readers based on the python
> > programmable filter much easier.
> >
> > Thanks,
> > Daan
> >
> > _______________________________________________
> > 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/20170403/776b88c0/attachment.html>

From jfavre at cscs.ch  Mon Apr  3 07:01:33 2017
From: jfavre at cscs.ch (Favre  Jean)
Date: Mon, 3 Apr 2017 11:01:33 +0000
Subject: [Paraview-developers] failed to compile Cosmo
In-Reply-To: <CACJ=gTiELkv=wcH1D8djLU5ZXvBzL70n1iS8Wsnks7kYzvGcTw@mail.gmail.com>
References: <0EB9B6375711A04B820E6B6F5CCA9F684383C921@MBX211.d.ethz.ch>,
 <CACJ=gTiELkv=wcH1D8djLU5ZXvBzL70n1iS8Wsnks7kYzvGcTw@mail.gmail.com>
Message-ID: <0EB9B6375711A04B820E6B6F5CCA9F684383D392@MBX211.d.ethz.ch>

Thanks Joachim

that did the job. I have now a compiled lib/libvtkCosmoHaloFinder-pv5.3.so.

But then what? I loaded my data, but can't find any filters/sources related to Halo Finding. Any tip?

Thanks

-----------------
Jean
________________________________
From: Joachim Pouderoux [joachim.pouderoux at kitware.com]
Sent: Monday, April 03, 2017 2:58 AM
To: Favre Jean
Cc: paraview-developers at paraview.org
Subject: Re: [Paraview-developers] failed to compile Cosmo

Jean,

Please give a try to the GenericIO we provide for building ParaView superbuild:
http://www.paraview.org/files/dependencies/genericio-master-a15ffc76cfa9f9674f933e8cb5ffc97a97fd7b27.zip

Best,
Joachim

Joachim Pouderoux, PhD
Technical Expert - Scientific Computing Team
Kitware SAS<http://www.kitware.fr>

2017-03-30 8:08 GMT-04:00 Favre Jean <jfavre at cscs.ch<mailto:jfavre at cscs.ch>>:

Developers

I'd like to compile the CosmoHaloFinder, with parallel support.

compilation fails with the error:

ThirdParty/CosmoHaloFinder/FOFDistribute.cxx:59:32: fatal error: GenericIOMPIReader.h: No such file or directory

I have looked for that file, have browsed the ANL site (http://trac.alcf.anl.gov/projects/genericio) but cannot find it anywhere.

ParaView web page [1] lists at least a couple of Halo finder options, but it is not clear to me how to build them.

[1] http://www.paraview.org/astro-physics/

-----------------
Jean/CSCS

_______________________________________________
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/20170403/df8003e2/attachment-0001.html>

From mathieu.westphal at kitware.com  Mon Apr  3 07:10:50 2017
From: mathieu.westphal at kitware.com (Mathieu Westphal)
Date: Mon, 3 Apr 2017 13:10:50 +0200
Subject: [Paraview-developers] failed to compile Cosmo
In-Reply-To: <0EB9B6375711A04B820E6B6F5CCA9F684383D392@MBX211.d.ethz.ch>
References: <0EB9B6375711A04B820E6B6F5CCA9F684383C921@MBX211.d.ethz.ch>
 <CACJ=gTiELkv=wcH1D8djLU5ZXvBzL70n1iS8Wsnks7kYzvGcTw@mail.gmail.com>
 <0EB9B6375711A04B820E6B6F5CCA9F684383D392@MBX211.d.ethz.ch>
Message-ID: <CAC2t4UQ1YpYyMy_82PjtLdJTq1SKg8sX_1nLPD-vWjeWJd1ygg@mail.gmail.com>

Hello

Please make sure that the following option are activated in CMake
configuration
PARAVIEW_ENABLE_COSMOTOOLS
Module_vtkCosmoHaloFinder
Module_vtkPVVTKExtensionsCosmoTools

If it is, you should have a filter named
LANL FOF/SOD Halo Finder

Regards,

Mathieu Westphal

On Mon, Apr 3, 2017 at 1:01 PM, Favre Jean <jfavre at cscs.ch> wrote:

> Thanks Joachim
>
> that did the job. I have now a compiled lib/libvtkCosmoHaloFinder-pv5.3.so
> .
>
> But then what? I loaded my data, but can't find any filters/sources
> related to Halo Finding. Any tip?
>
> Thanks
>
> -----------------
> Jean
> ------------------------------
> *From:* Joachim Pouderoux [joachim.pouderoux at kitware.com]
> *Sent:* Monday, April 03, 2017 2:58 AM
> *To:* Favre Jean
> *Cc:* paraview-developers at paraview.org
> *Subject:* Re: [Paraview-developers] failed to compile Cosmo
>
> Jean,
>
> Please give a try to the GenericIO we provide for building ParaView
> superbuild:
> http://www.paraview.org/files/dependencies/genericio-master-
> a15ffc76cfa9f9674f933e8cb5ffc97a97fd7b27.zip
>
> Best,
> Joachim
>
> *Joachim Pouderoux*, PhD
>
> *Technical Expert - Scientific Computing Team*
> *Kitware SAS <http://www.kitware.fr>*
>
>
> 2017-03-30 8:08 GMT-04:00 Favre Jean <jfavre at cscs.ch>:
>
>>
>> Developers
>>
>> I'd like to compile the CosmoHaloFinder, with parallel support.
>>
>> compilation fails with the error:
>>
>> ThirdParty/CosmoHaloFinder/FOFDistribute.cxx:59:32: fatal error:
>> GenericIOMPIReader.h: No such file or directory
>>
>> I have looked for that file, have browsed the ANL site (
>> http://trac.alcf.anl.gov/projects/genericio) but cannot find it anywhere.
>>
>> ParaView web page [1] lists at least a couple of Halo finder options, but
>> it is not clear to me how to build them.
>>
>> [1] http://www.paraview.org/astro-physics/
>>
>> -----------------
>> Jean/CSCS
>>
>> _______________________________________________
>> 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/20170403/eb3004fb/attachment.html>

From ben.boeckel at kitware.com  Mon Apr  3 07:53:49 2017
From: ben.boeckel at kitware.com (Ben Boeckel)
Date: Mon, 3 Apr 2017 07:53:49 -0400
Subject: [Paraview-developers] No in situ visualization of the catalyst
 examples
In-Reply-To: <b3edab9dbd0d56ab4478be4e25849fd9@cea-igp.ac.cn>
References: <4b884ee5ac7ce6a8a543cb3df7b01d11@cea-igp.ac.cn>
 <CAMaOp+FnDnaM1Dj3ztLV0_g94S4pyo2dfNm3yLa1+Uz5ZV3gUQ@mail.gmail.com>
 <b3edab9dbd0d56ab4478be4e25849fd9@cea-igp.ac.cn>
Message-ID: <20170403115349.GA30932@megas.kitware.com>

On Mon, Apr 03, 2017 at 10:17:49 +0800, ?? wrote:
> The wired thing is:I chose Enable_hdf5 and it actually found hdf5,and
> it still told me there is no hdf5..

This is a problem with CMake 3.8.0-rc; you'll need either CMake 3.7 or
to use a ParaView master build.

--Ben

From ben.boeckel at kitware.com  Mon Apr  3 08:38:15 2017
From: ben.boeckel at kitware.com (Ben Boeckel)
Date: Mon, 3 Apr 2017 08:38:15 -0400
Subject: [Paraview-developers] H5py in paraview python
In-Reply-To: <CAAyVbOAt7pUje2_TkMiL5rjjHOCHEkhr2D2-E7Gm32VskQht4A@mail.gmail.com>
References: <CAAyVbOD8OWSLzQEquRUFpyZS0vP-LEvy8c+rnbdN50QbPQiAYg@mail.gmail.com>
 <CADHSJjAMZdeL3GescDmk+fuJohQJmbSxpSwF2oZJ1KPFKn5iZQ@mail.gmail.com>
 <CAAyVbOAt7pUje2_TkMiL5rjjHOCHEkhr2D2-E7Gm32VskQht4A@mail.gmail.com>
Message-ID: <20170403123815.GB30932@megas.kitware.com>

On Mon, Apr 03, 2017 at 10:34:40 +0200, Daan van Vugt wrote:
> Perhaps a more general (but maybe not easier) solution would be to include
> pip in the paraview python environment?
> Then users can install additional modules themselves.

Definitely not easier. We currently don't ship an SDK for ParaView with
the packages we make. Part of the problem (at least for Windows) is that
Python builds everything with a VS9 (2008) compiler, but C++ code needs
to use VS12 (2013). On macOS, we just use the system Python, but there's
still no SDK for ParaView since frameworks aren't created.

> We have been trying to include h5py in a binary windows install of
> Paraview and are having quite some troubles.

I'll try and take a stab at getting it into the superbuild this week.

--Ben

From joseph.g.hennessey2.ctr at mail.mil  Mon Apr  3 10:15:49 2017
From: joseph.g.hennessey2.ctr at mail.mil (Hennessey, Joseph G CTR USARMY RDECOM ARL (US))
Date: Mon, 3 Apr 2017 14:15:49 +0000
Subject: [Paraview-developers] Problems with mpi4py and SGI's mpt 2.14
	version of MPI
Message-ID: <10A03274360DCF47A6EE78C9952A31CA91E5F56C@UCOLHPUD.easf.csd.disa.mil>

Hello,

I have been running into problems with
mpi4py and SGI's mpt 2.14 version of MPI
while compiling ParaView 5.3.0 on HPC systems.

mpi4py cannot find MPI_CONVERSION_FN_NULL
when compiling mpi4py.MPI.c

MPI_CONVERSION_FN_NULL was not used by the
version of mpi4py that came with ParaView 5.2.0
and when I swap the ParaView 5.2.0 version of mpi4py
in place of the ParaView 5.3.0 version of mpi4py then
ParaView 5.3.0 (with the 5.2.0 version of mpi4py) compiles just fine.

Is this a known problem? Is there a minimum version
of mpt that is required for ParaView 5.3.0? What 
will break if use the ParaView 5.2.0 version of mpi4py
instead with ParaView 5.3.0?

Thanks,

Joe

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Joseph G. Hennessey Ph.D., SAIC
Team SAIC
Army Research Lab
DOD Supercomputing Resource Center
Aberdeen Proving Ground, MD 21005


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

From ben.boeckel at kitware.com  Mon Apr  3 11:30:13 2017
From: ben.boeckel at kitware.com (Ben Boeckel)
Date: Mon, 3 Apr 2017 11:30:13 -0400
Subject: [Paraview-developers] Problems with mpi4py and SGI's mpt 2.14
 version of MPI
In-Reply-To: <10A03274360DCF47A6EE78C9952A31CA91E5F56C@UCOLHPUD.easf.csd.disa.mil>
References: <10A03274360DCF47A6EE78C9952A31CA91E5F56C@UCOLHPUD.easf.csd.disa.mil>
Message-ID: <20170403153013.GA7715@rotor>

On Mon, Apr 03, 2017 at 14:15:49 +0000, Hennessey, Joseph G CTR USARMY RDECOM ARL (US) wrote:
> I have been running into problems with
> mpi4py and SGI's mpt 2.14 version of MPI
> while compiling ParaView 5.3.0 on HPC systems.
> 
> mpi4py cannot find MPI_CONVERSION_FN_NULL
> when compiling mpi4py.MPI.c
> 
> MPI_CONVERSION_FN_NULL was not used by the
> version of mpi4py that came with ParaView 5.2.0
> and when I swap the ParaView 5.2.0 version of mpi4py
> in place of the ParaView 5.3.0 version of mpi4py then
> ParaView 5.3.0 (with the 5.2.0 version of mpi4py) compiles just fine.
> 
> Is this a known problem? Is there a minimum version
> of mpt that is required for ParaView 5.3.0? What 
> will break if use the ParaView 5.2.0 version of mpi4py
> instead with ParaView 5.3.0?

We updated from mpi4py from 1.3.0 to 2.0.0. You can see
upstream-documented differences here:

    https://gitlab.kitware.com/vtk/vtk/blob/master/ThirdParty/mpi4py/vtkmpi4py/CHANGES.rst

It doesn't appear that VTK cares about the backwards-incompat changes
listed there (we use it to allow MPI Controllers to be shared between
VTK's C++ code and other Python code).

It seems that the MPI_CONVERSION_FN_NULL is used because the
upstream-generated Cython code says it exists. Maybe the module could be
updated to optionally rerun the Cython code generator so that it works
with an arbitrary MPI?

--Ben

From joseph.g.hennessey2.ctr at mail.mil  Mon Apr  3 12:10:46 2017
From: joseph.g.hennessey2.ctr at mail.mil (Hennessey, Joseph G CTR USARMY RDECOM ARL (US))
Date: Mon, 3 Apr 2017 16:10:46 +0000
Subject: [Paraview-developers] [Non-DoD Source] Re: Problems with mpi4py
 and SGI's mpt 2.14 version of MPI
In-Reply-To: <20170403153013.GA7715@rotor>
References: <10A03274360DCF47A6EE78C9952A31CA91E5F56C@UCOLHPUD.easf.csd.disa.mil>
 <20170403153013.GA7715@rotor>
Message-ID: <10A03274360DCF47A6EE78C9952A31CA91E5F5CA@UCOLHPUD.easf.csd.disa.mil>

Ben,

The idea of reruning the Cython code generator so that it works with an 
arbitrary MPI,
sounds like a good idea to me. I compile and install ParaView across a wide 
range of HPC systems,
with many variations of MPI across all of them.

Do you know what would be involved in implementing this?

Thanks,

Joe

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Joseph G. Hennessey Ph.D., SAIC
Team SAIC
Army Research Lab
DOD Supercomputing Resource Center
Aberdeen Proving Ground, MD 21005


-----Original Message-----
From: Ben Boeckel [mailto:ben.boeckel at kitware.com]
Sent: Monday, April 03, 2017 11:30 AM
To: Hennessey, Joseph G CTR USARMY RDECOM ARL (US) 
<joseph.g.hennessey2.ctr at mail.mil>
Cc: ParaView Developers <paraview-developers at paraview.org>
Subject: [Non-DoD Source] Re: [Paraview-developers] Problems with mpi4py and 
SGI's mpt 2.14 version of MPI

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




----

On Mon, Apr 03, 2017 at 14:15:49 +0000, Hennessey, Joseph G CTR USARMY RDECOM 
ARL (US) wrote:
> I have been running into problems with mpi4py and SGI's mpt 2.14
> version of MPI while compiling ParaView 5.3.0 on HPC systems.
>
> mpi4py cannot find MPI_CONVERSION_FN_NULL when compiling mpi4py.MPI.c
>
> MPI_CONVERSION_FN_NULL was not used by the version of mpi4py that came
> with ParaView 5.2.0 and when I swap the ParaView 5.2.0 version of
> mpi4py in place of the ParaView 5.3.0 version of mpi4py then ParaView
> 5.3.0 (with the 5.2.0 version of mpi4py) compiles just fine.
>
> Is this a known problem? Is there a minimum version of mpt that is
> required for ParaView 5.3.0? What will break if use the ParaView 5.2.0
> version of mpi4py instead with ParaView 5.3.0?

We updated from mpi4py from 1.3.0 to 2.0.0. You can see upstream-documented 
differences here:

    Caution-https://gitlab.kitware.com/vtk/vtk/blob/master/ThirdParty/mpi4py/vtkmpi4py/CHANGES.rst

It doesn't appear that VTK cares about the backwards-incompat changes listed 
there (we use it to allow MPI Controllers to be shared between VTK's C++ code 
and other Python code).

It seems that the MPI_CONVERSION_FN_NULL is used because the 
upstream-generated Cython code says it exists. Maybe the module could be 
updated to optionally rerun the Cython code generator so that it works with an 
arbitrary MPI?

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

From ben.boeckel at kitware.com  Mon Apr  3 13:40:46 2017
From: ben.boeckel at kitware.com (Ben Boeckel)
Date: Mon, 3 Apr 2017 13:40:46 -0400
Subject: [Paraview-developers] [Non-DoD Source] Re: Problems with mpi4py
 and SGI's mpt 2.14 version of MPI
In-Reply-To: <10A03274360DCF47A6EE78C9952A31CA91E5F5CA@UCOLHPUD.easf.csd.disa.mil>
References: <10A03274360DCF47A6EE78C9952A31CA91E5F56C@UCOLHPUD.easf.csd.disa.mil>
 <20170403153013.GA7715@rotor>
 <10A03274360DCF47A6EE78C9952A31CA91E5F5CA@UCOLHPUD.easf.csd.disa.mil>
Message-ID: <20170403174046.GB30585@megas.kitware.com>

On Mon, Apr 03, 2017 at 16:10:46 +0000, Hennessey, Joseph G CTR USARMY RDECOM ARL (US) wrote:
> The idea of reruning the Cython code generator so that it works with an 
> arbitrary MPI,
> sounds like a good idea to me. I compile and install ParaView across a wide 
> range of HPC systems,
> with many variations of MPI across all of them.
> 
> Do you know what would be involved in implementing this?

First, it should be optional since requiring Cython is not something
we'd want to do in general or by default.

I don't know if mpi4py documents how to run cython to generate the
source files, but that would need investigation.

The third-party repo for mpi4py is here:

    https://gitlab.kitware.com/third-party/mpi4py

--Ben

From kriolog at gmail.com  Mon Apr  3 21:28:57 2017
From: kriolog at gmail.com (Maxim Torgonskiy)
Date: Mon, 3 Apr 2017 21:28:57 -0400
Subject: [Paraview-developers] Bind a points table from a properties panel
 directly with a 3D widget, not with its representation
Message-ID: <CAHXhknsp5ZgSq2Vf1ZMVahN5ZUYir1nobR07JnF3GJC6OVHFZA@mail.gmail.com>

Hello,

I'm trying to create a paraview plugin for vtkSeedsWidget. The problem
occurs when I try to bind handle positions from a QTreeWidget of the
pqSeedsPropertyWidget  directly with the vtkSeedsWidget (I should do
that because unlike vtkPolyLine{Widget,Representation}
creation/removal can be governed only through the Widget part):

pqSeedsPropertyWidget::pqSeedsPropertyWidget(
  vtkSMProxy* smproxy,
  vtkSMPropertyGroup* smgroup,
  QWidget* parent
) :
  ...
  if (vtkSMProperty* handlePositions =
smgroup->GetProperty("HandlePositions")) {
    Internals->PointsAdaptor = new
pqSignalAdaptorTreeWidget(Internals->Ui.handlesTable, true);
    addPropertyLink(Internals->PointsAdaptor, "values",
SIGNAL(valuesChanged()), handlePositions);
  }
  ...
}

where HandlePositions corresponds to the vtkSeedsWidget:

 <ProxyGroup name="3d_widgets">
    <Proxy base_proxygroup="3d_widgets"
            base_proxyname="WidgetBase"
            class="vtkSeedsWidget"
            name="SeedsWidget">
      <DoubleVectorProperty command="SetHandlePosition"
                            default_values="0 0 1 0 0 0"
                            information_property="HandlePositionsInfo"
                            name="HandlePositions"
                            number_of_elements="6"
                            number_of_elements_per_command="3"
                            repeat_command="1"
                            set_number_command="SetNumberOfHandles"
                            use_index="1">
      </DoubleVectorProperty>
      <DoubleVectorProperty command="GetHandlePositions"
                            information_only="1"
                            name="HandlePositionsInfo">
        <DoubleArrayInformationHelper />
      </DoubleVectorProperty>
    </Proxy>
  </ProxyGroup>

In the vtkSeedsWidget class I've added these corresponding functions:

void vtkSeedsWidget::SetNumberOfHandles(int n)
{...}

void vtkSeedsWidget::SetHandlePosition(int i, double x, double y, double z)
{...}

vtkDoubleArray* vtkSeedsWidget::GetHandlePositions()
{...}

The forward connection from the table to the 3D widget works as
expected, but the backward one doesn't (function GetHandlePositions is
called once during construction but never after  the InvokeEvent is
called in the vtkSeedsWidget). I understand that I shouldn't expect to
have this behavior "out of box" but I didn't find how to modify the
code to make it work (or I need at least understand that it's not
possible :) ). Could you please help me with this little problem?

Thanks,
Maxim

From jfavre at cscs.ch  Tue Apr  4 09:37:56 2017
From: jfavre at cscs.ch (Favre  Jean)
Date: Tue, 4 Apr 2017 13:37:56 +0000
Subject: [Paraview-developers] failed to compile Cosmo
In-Reply-To: <CAC2t4UQ1YpYyMy_82PjtLdJTq1SKg8sX_1nLPD-vWjeWJd1ygg@mail.gmail.com>
References: <0EB9B6375711A04B820E6B6F5CCA9F684383C921@MBX211.d.ethz.ch>
 <CACJ=gTiELkv=wcH1D8djLU5ZXvBzL70n1iS8Wsnks7kYzvGcTw@mail.gmail.com>
 <0EB9B6375711A04B820E6B6F5CCA9F684383D392@MBX211.d.ethz.ch>,
 <CAC2t4UQ1YpYyMy_82PjtLdJTq1SKg8sX_1nLPD-vWjeWJd1ygg@mail.gmail.com>
Message-ID: <0EB9B6375711A04B820E6B6F5CCA9F684383D9A7@MBX211.d.ethz.ch>


Thanks Mathieu. I got everything enabled now.

I have plugged my own data...but the vtkPLANLHaloFinder does not find any halos. It runs for a while, does not complain, but does not give indication of missing features. I am wondering if I am providing the right data. I have looked at the source code of the CosmoReader to get some hints.

Am not sure about the required array called "ghost". What exactly should it contain? any user of the CosmoTools can comment on the input data requirements?

I have got the 4 arrays required (an int-array called "ghost", 2 float-arrays called "mass" and "velocity", and an idtype-array called "tag". But no halos so far.

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

From haocheng.liu at kitware.com  Tue Apr  4 15:10:33 2017
From: haocheng.liu at kitware.com (Haocheng Liu)
Date: Tue, 4 Apr 2017 15:10:33 -0400
Subject: [Paraview-developers] FYI: ParaView 5.3.0 + Ubuntu 16.04 needs
	OpenGL driver update
Message-ID: <CACbTE7OeQZ8KHr36KVtYnCJZdKwahxGDiH9bMyD5gem3XozR-Q@mail.gmail.com>

Hi,

I am a developer on Computational Model builder
<http://www.computationalmodelbuilder.org/> which is a project depends on
ParaView. Recently CMB-superbuild is bumped to use ParaView 5.3.0. However,
it is not happy with OpenGL drivers on Ubuntu 16.04 and I also find that I
cannot use *"opacity" and "slice" operations in ParaView*. After some test
and trial, I found this solution:

```type these terminal

apt-add-repository ppa:oibaf/graphics-drivers

apt-get update

apt-get dist-upgrade
```

It perfectly solves the problem.
Reference link
<http://askubuntu.com/questions/800540/paraview-in-ubuntu/897739#897739>


-- 
Best regards
Haocheng

Haocheng LIU
Kitware, Inc.
R&D Engineer
21 Corporate Drive
Clifton Park, NY 12065-8662
Phone: 518-881-4421 <(518)%20881-4421>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20170404/2878913f/attachment.html>

From utkarsh.ayachit at kitware.com  Tue Apr  4 15:16:43 2017
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Tue, 4 Apr 2017 15:16:43 -0400
Subject: [Paraview-developers] FYI: ParaView 5.3.0 + Ubuntu 16.04 needs
 OpenGL driver update
In-Reply-To: <CACbTE7OeQZ8KHr36KVtYnCJZdKwahxGDiH9bMyD5gem3XozR-Q@mail.gmail.com>
References: <CACbTE7OeQZ8KHr36KVtYnCJZdKwahxGDiH9bMyD5gem3XozR-Q@mail.gmail.com>
Message-ID: <CADHSJjA5462gA_W2ALGvx2ZAkow3h80ty7w5wFecZF+TP3JVqA@mail.gmail.com>

Thanks for the info, Haocheng.

Utkarsh

On Tue, Apr 4, 2017 at 3:10 PM, Haocheng Liu <haocheng.liu at kitware.com> wrote:
> Hi,
>
> I am a developer on Computational Model builder which is a project depends
> on ParaView. Recently CMB-superbuild is bumped to use ParaView 5.3.0.
> However, it is not happy with OpenGL drivers on Ubuntu 16.04 and I also find
> that I cannot use "opacity" and "slice" operations in ParaView. After some
> test and trial, I found this solution:
>
> ```type these terminal
>
> apt-add-repository ppa:oibaf/graphics-drivers
>
> apt-get update
>
> apt-get dist-upgrade
>
> ```
>
> It perfectly solves the problem.
> Reference link
>
>
> --
> Best regards
> Haocheng
>
> Haocheng LIU
> Kitware, Inc.
> R&D Engineer
> 21 Corporate Drive
> Clifton Park, NY 12065-8662
> Phone: 518-881-4421
>
> _______________________________________________
> 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 wascott at sandia.gov  Tue Apr  4 16:46:20 2017
From: wascott at sandia.gov (Scott, W Alan)
Date: Tue, 4 Apr 2017 20:46:20 +0000
Subject: [Paraview-developers] ParaView is hanging Mac when closing
Message-ID: <a5701670c44640acb319755721e2f29d@ES01AMSNLNT.srn.sandia.gov>

Utkarsh,

I have a user that is seeing a strange hang with PV 5.3.0, and his Mac.  He is dealing with a different issue (probably a bad sideset on a large dataset), which is crashing the ParaView server.  At this point, ParaView client dies (not unexpected).  However, ParaView continues to appear running.  If you right click on ParaView on the doc, and you say close, ParaView disappears.  Terminal/ ps -ef does not show ParaView.  But, it remains in the doc, with the little dot below saying it is running.

At this point, my user can't start up another ParaView instance and connect remotely, since the port appears to be tied up.  The only option is to reboot.  But, the mac won't reboot!  It is hanging on the ParaView process that is still coming down.   So, we are having to power cycle the Mac.

I cannot replicate this on my macbook pro, thus am not writing up a bug (yet).    When we tried running ParaView from a terminal window, no warning messages were seen, and ParaView closed correctly.

User's OS is: 10.11.6 (El Capitan)
My OS is: 10.11.6 (El Capitan)

My user has two AMD FirePro D300 graphics cards.

Any 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

The most exciting phrase to hear in science
is not "Eureka!" but "That's funny..."  -- Isaac Asimov
---------------------------------------------------------

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20170404/90e2d8d8/attachment.html>

From wascott at sandia.gov  Tue Apr  4 16:52:46 2017
From: wascott at sandia.gov (Scott, W Alan)
Date: Tue, 4 Apr 2017 20:52:46 +0000
Subject: [Paraview-developers] [EXTERNAL] ParaView is hanging Mac when
 closing
In-Reply-To: <a5701670c44640acb319755721e2f29d@ES01AMSNLNT.srn.sandia.gov>
References: <a5701670c44640acb319755721e2f29d@ES01AMSNLNT.srn.sandia.gov>
Message-ID: <d67881b42d30458a9a11783a599b0d4a@ES01AMSNLNT.srn.sandia.gov>

I forgot to mention - I did delete his .config/ParaView/paraview5.3.0.ini file and servers.pvsc file.  Error below continued.

Alan

From: Paraview-developers [mailto:paraview-developers-bounces at paraview.org] On Behalf Of Scott, W Alan
Sent: Tuesday, April 4, 2017 2:46 PM
To: paraview-developers at paraview.org
Subject: [EXTERNAL] [Paraview-developers] ParaView is hanging Mac when closing

Utkarsh,

I have a user that is seeing a strange hang with PV 5.3.0, and his Mac.  He is dealing with a different issue (probably a bad sideset on a large dataset), which is crashing the ParaView server.  At this point, ParaView client dies (not unexpected).  However, ParaView continues to appear running.  If you right click on ParaView on the doc, and you say close, ParaView disappears.  Terminal/ ps -ef does not show ParaView.  But, it remains in the doc, with the little dot below saying it is running.

At this point, my user can't start up another ParaView instance and connect remotely, since the port appears to be tied up.  The only option is to reboot.  But, the mac won't reboot!  It is hanging on the ParaView process that is still coming down.   So, we are having to power cycle the Mac.

I cannot replicate this on my macbook pro, thus am not writing up a bug (yet).    When we tried running ParaView from a terminal window, no warning messages were seen, and ParaView closed correctly.

User's OS is: 10.11.6 (El Capitan)
My OS is: 10.11.6 (El Capitan)

My user has two AMD FirePro D300 graphics cards.

Any 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

The most exciting phrase to hear in science
is not "Eureka!" but "That's funny..."  -- Isaac Asimov
---------------------------------------------------------

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

From mathieu.westphal at kitware.com  Wed Apr  5 03:03:21 2017
From: mathieu.westphal at kitware.com (Mathieu Westphal)
Date: Wed, 5 Apr 2017 09:03:21 +0200
Subject: [Paraview-developers] BUILD_TESTING Default value
Message-ID: <CAC2t4URNWcp7DbmBFkxZYdvLmf09eJRxTwSLxCxHCiNb3ZRqAA@mail.gmail.com>

Hi

I would like to change BUILD_TESTING default value to OFF.
If somebody have some intencive regarding keeping it to ON, please let me
know !

Regards,

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

From daanvanvugt at gmail.com  Wed Apr  5 03:25:00 2017
From: daanvanvugt at gmail.com (Daan van Vugt)
Date: Wed, 5 Apr 2017 09:25:00 +0200
Subject: [Paraview-developers] File extensions and plugins
Message-ID: <CAAyVbOB8fNDU+24g3fNt=vYC5eio9OrRn_8r4bnkesNnedy3Pg@mail.gmail.com>

Hi,

A general question about your preferences for file extensions:
If we have a custom restart file using hdf5, should we use the .h5
extension or create a more specific extension to indicate the type of file?
It is slightly annoying to have to select from a growing mass of readers
all supporting .h5 files.

Best,
Daan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20170405/f66f8efc/attachment.html>

From mathieu.westphal at kitware.com  Wed Apr  5 03:29:03 2017
From: mathieu.westphal at kitware.com (Mathieu Westphal)
Date: Wed, 5 Apr 2017 09:29:03 +0200
Subject: [Paraview-developers] File extensions and plugins
In-Reply-To: <CAAyVbOB8fNDU+24g3fNt=vYC5eio9OrRn_8r4bnkesNnedy3Pg@mail.gmail.com>
References: <CAAyVbOB8fNDU+24g3fNt=vYC5eio9OrRn_8r4bnkesNnedy3Pg@mail.gmail.com>
Message-ID: <CAC2t4URe39w79dKBfjxABYDn9REVWrn1ZCEqMsWMmr87Hr-ydg@mail.gmail.com>

Hi

Nothing prevents you to create your own specific extension and use it in
your plugin xml to ensure your reader is selected.
You could even set your reader to open file like : .h5 .myh5 so you can
still use it with "non-renamed' file.

Regards,

Mathieu Westphal

On Wed, Apr 5, 2017 at 9:25 AM, Daan van Vugt <daanvanvugt at gmail.com> wrote:

> Hi,
>
> A general question about your preferences for file extensions:
> If we have a custom restart file using hdf5, should we use the .h5
> extension or create a more specific extension to indicate the type of file?
> It is slightly annoying to have to select from a growing mass of readers
> all supporting .h5 files.
>
> Best,
> Daan
>
>
>
> _______________________________________________
> 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/20170405/cd6aac2c/attachment.html>

From mathieu.westphal at kitware.com  Wed Apr  5 06:08:34 2017
From: mathieu.westphal at kitware.com (Mathieu Westphal)
Date: Wed, 5 Apr 2017 12:08:34 +0200
Subject: [Paraview-developers] QT 5.8 Bug
Message-ID: <CAC2t4USm2DSnuAxBxt2whavjGnu7V0Gk9XZJDest8c1JeeY38A@mail.gmail.com>

Hi

It looks like we are impacted by this bug :
https://bugreports.qt.io/browse/QTBUG-59460

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

From joachim.pouderoux at kitware.com  Wed Apr  5 08:15:45 2017
From: joachim.pouderoux at kitware.com (Joachim Pouderoux)
Date: Wed, 5 Apr 2017 08:15:45 -0400
Subject: [Paraview-developers] BUILD_TESTING Default value
In-Reply-To: <CAC2t4URNWcp7DbmBFkxZYdvLmf09eJRxTwSLxCxHCiNb3ZRqAA@mail.gmail.com>
References: <CAC2t4URNWcp7DbmBFkxZYdvLmf09eJRxTwSLxCxHCiNb3ZRqAA@mail.gmail.com>
Message-ID: <CACJ=gTg02OHi_WMm1nYkxvoUb4NtF6P011fYXyfN4LRaaDntOg@mail.gmail.com>

I agree with you testing is for 'advanced users' and should be OFF by
default.
Note that BUILD_TESTING=OFF is default value on VTK.

Joachim

*Joachim Pouderoux*, PhD

*Technical Expert - Scientific Computing Team*
*Kitware SAS <http://www.kitware.fr>*


2017-04-05 3:03 GMT-04:00 Mathieu Westphal <mathieu.westphal at kitware.com>:

> Hi
>
> I would like to change BUILD_TESTING default value to OFF.
> If somebody have some intencive regarding keeping it to ON, please let me
> know !
>
> Regards,
>
> Mathieu Westphal
>
> _______________________________________________
> 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/20170405/005a8e02/attachment.html>

From cornelis.bockemuehl at gmail.com  Wed Apr  5 08:23:49 2017
From: cornelis.bockemuehl at gmail.com (=?UTF-8?Q?Cornelis_Bockem=C3=BChl?=)
Date: Wed, 5 Apr 2017 14:23:49 +0200
Subject: [Paraview-developers] QT 5.8 Bug
In-Reply-To: <CAC2t4USm2DSnuAxBxt2whavjGnu7V0Gk9XZJDest8c1JeeY38A@mail.gmail.com>
References: <CAC2t4USm2DSnuAxBxt2whavjGnu7V0Gk9XZJDest8c1JeeY38A@mail.gmail.com>
Message-ID: <CACqg2jf_AV8DTNWob6dgf8ddeZFM9N2rTC9UD=eVDVUeVRus2g@mail.gmail.com>

I assume that this one could help also in your case: At least it helped in
mine where I was also running into some "unknown interface" issue:

https://codereview.qt-project.org/#/c/184321/

Regards,
Cornelis

PS: Actually the hint comes from Ben Boeckel, also on this list: Thanks
again Ben!


2017-04-05 12:08 GMT+02:00 Mathieu Westphal <mathieu.westphal at kitware.com>:

> Hi
>
> It looks like we are impacted by this bug :
> https://bugreports.qt.io/browse/QTBUG-59460
>
> Mathieu Westphal
>
> _______________________________________________
> 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
>
>


-- 
Cornelis Bockem?hl
Basel, Schweiz
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20170405/86a5b8ee/attachment-0001.html>

From mathieu.westphal at kitware.com  Wed Apr  5 08:36:09 2017
From: mathieu.westphal at kitware.com (Mathieu Westphal)
Date: Wed, 5 Apr 2017 14:36:09 +0200
Subject: [Paraview-developers] Install Guide updated
Message-ID: <CAC2t4UTDUht16OZgA8afB-GQNQSh3smp8V6xfum6Z5n-KcumQQ@mail.gmail.com>

Hi

I've updated the install guide (mostly the windows part).
Anyone willing to check it are welcome !
http://www.paraview.org/Wiki/ParaView:Build_And_Install

Regards,

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

From utkarsh.ayachit at kitware.com  Wed Apr  5 09:04:54 2017
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Wed, 5 Apr 2017 09:04:54 -0400
Subject: [Paraview-developers] Install Guide updated
In-Reply-To: <CAC2t4UTDUht16OZgA8afB-GQNQSh3smp8V6xfum6Z5n-KcumQQ@mail.gmail.com>
References: <CAC2t4UTDUht16OZgA8afB-GQNQSh3smp8V6xfum6Z5n-KcumQQ@mail.gmail.com>
Message-ID: <CADHSJjDVX98mZ4TwUGQK40f6QHaKjJ6Xb6atuX4zVWf8Akg8JQ@mail.gmail.com>

Thanks, Mathieu!

I wonder if we should move the Build/Install Guide to Markdown files
in Gitlab itself so we can keep it updated with each release more
easily.

Utkarsh

On Wed, Apr 5, 2017 at 8:36 AM, Mathieu Westphal
<mathieu.westphal at kitware.com> wrote:
> Hi
>
> I've updated the install guide (mostly the windows part).
> Anyone willing to check it are welcome !
> http://www.paraview.org/Wiki/ParaView:Build_And_Install
>
> Regards,
>
> Mathieu Westphal
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Search the list archives at:
> http://markmail.org/search/?q=Paraview-developers
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview-developers
>

From mathieu.westphal at kitware.com  Wed Apr  5 09:05:55 2017
From: mathieu.westphal at kitware.com (Mathieu Westphal)
Date: Wed, 5 Apr 2017 15:05:55 +0200
Subject: [Paraview-developers] Install Guide updated
In-Reply-To: <CADHSJjDVX98mZ4TwUGQK40f6QHaKjJ6Xb6atuX4zVWf8Akg8JQ@mail.gmail.com>
References: <CAC2t4UTDUht16OZgA8afB-GQNQSh3smp8V6xfum6Z5n-KcumQQ@mail.gmail.com>
 <CADHSJjDVX98mZ4TwUGQK40f6QHaKjJ6Xb6atuX4zVWf8Akg8JQ@mail.gmail.com>
Message-ID: <CAC2t4UQQMo6pJuKGer9Dvca=EteroDEqw11bg76rAXqNsk3w_w@mail.gmail.com>

Sounds like a good idea to me.

Mathieu Westphal

On Wed, Apr 5, 2017 at 3:04 PM, Utkarsh Ayachit <utkarsh.ayachit at kitware.com
> wrote:

> Thanks, Mathieu!
>
> I wonder if we should move the Build/Install Guide to Markdown files
> in Gitlab itself so we can keep it updated with each release more
> easily.
>
> Utkarsh
>
> On Wed, Apr 5, 2017 at 8:36 AM, Mathieu Westphal
> <mathieu.westphal at kitware.com> wrote:
> > Hi
> >
> > I've updated the install guide (mostly the windows part).
> > Anyone willing to check it are welcome !
> > http://www.paraview.org/Wiki/ParaView:Build_And_Install
> >
> > Regards,
> >
> > Mathieu Westphal
> >
> > _______________________________________________
> > 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/20170405/a064c286/attachment.html>

From utkarsh.ayachit at kitware.com  Wed Apr  5 09:06:22 2017
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Wed, 5 Apr 2017 09:06:22 -0400
Subject: [Paraview-developers] BUILD_TESTING Default value
In-Reply-To: <CACJ=gTg02OHi_WMm1nYkxvoUb4NtF6P011fYXyfN4LRaaDntOg@mail.gmail.com>
References: <CAC2t4URNWcp7DbmBFkxZYdvLmf09eJRxTwSLxCxHCiNb3ZRqAA@mail.gmail.com>
 <CACJ=gTg02OHi_WMm1nYkxvoUb4NtF6P011fYXyfN4LRaaDntOg@mail.gmail.com>
Message-ID: <CADHSJjDZR14210fO5s4x1NFDFmPBOwJo+xDmYC4NQcnEAJPZ_g@mail.gmail.com>

+1

On Wed, Apr 5, 2017 at 8:15 AM, Joachim Pouderoux
<joachim.pouderoux at kitware.com> wrote:
> I agree with you testing is for 'advanced users' and should be OFF by
> default.
> Note that BUILD_TESTING=OFF is default value on VTK.
>
> Joachim
>
> Joachim Pouderoux, PhD
>
> Technical Expert - Scientific Computing Team
> Kitware SAS
>
>
> 2017-04-05 3:03 GMT-04:00 Mathieu Westphal <mathieu.westphal at kitware.com>:
>>
>> Hi
>>
>> I would like to change BUILD_TESTING default value to OFF.
>> If somebody have some intencive regarding keeping it to ON, please let me
>> know !
>>
>> Regards,
>>
>> Mathieu Westphal
>>
>> _______________________________________________
>> 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
>

From aron.helser at kitware.com  Wed Apr  5 10:52:16 2017
From: aron.helser at kitware.com (Aron Helser)
Date: Wed, 5 Apr 2017 10:52:16 -0400
Subject: [Paraview-developers] Install Guide updated
In-Reply-To: <CAC2t4UQQMo6pJuKGer9Dvca=EteroDEqw11bg76rAXqNsk3w_w@mail.gmail.com>
References: <CAC2t4UTDUht16OZgA8afB-GQNQSh3smp8V6xfum6Z5n-KcumQQ@mail.gmail.com>
 <CADHSJjDVX98mZ4TwUGQK40f6QHaKjJ6Xb6atuX4zVWf8Akg8JQ@mail.gmail.com>
 <CAC2t4UQQMo6pJuKGer9Dvca=EteroDEqw11bg76rAXqNsk3w_w@mail.gmail.com>
Message-ID: <CAF2skS5H7e3Si7SwcW-x_oQBMSF8n5ZHc4xPCK60qsBxJtt0Kg@mail.gmail.com>

Yes, please expand
https://gitlab.kitware.com/paraview/paraview/blob/master/Documentation/dev/build.md
or perhaps add sub-pages with platform-specific info?
Aron

On Wed, Apr 5, 2017 at 9:05 AM, Mathieu Westphal <
mathieu.westphal at kitware.com> wrote:

> Sounds like a good idea to me.
>
> Mathieu Westphal
>
> On Wed, Apr 5, 2017 at 3:04 PM, Utkarsh Ayachit <
> utkarsh.ayachit at kitware.com> wrote:
>
>> Thanks, Mathieu!
>>
>> I wonder if we should move the Build/Install Guide to Markdown files
>> in Gitlab itself so we can keep it updated with each release more
>> easily.
>>
>> Utkarsh
>>
>> On Wed, Apr 5, 2017 at 8:36 AM, Mathieu Westphal
>> <mathieu.westphal at kitware.com> wrote:
>> > Hi
>> >
>> > I've updated the install guide (mostly the windows part).
>> > Anyone willing to check it are welcome !
>> > http://www.paraview.org/Wiki/ParaView:Build_And_Install
>> >
>> > Regards,
>> >
>> > Mathieu Westphal
>> >
>> > _______________________________________________
>> > 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/20170405/1f9106ca/attachment.html>

From cory.quammen at kitware.com  Wed Apr  5 10:53:40 2017
From: cory.quammen at kitware.com (Cory Quammen)
Date: Wed, 5 Apr 2017 10:53:40 -0400
Subject: [Paraview-developers] BUILD_TESTING Default value
In-Reply-To: <CADHSJjDZR14210fO5s4x1NFDFmPBOwJo+xDmYC4NQcnEAJPZ_g@mail.gmail.com>
References: <CAC2t4URNWcp7DbmBFkxZYdvLmf09eJRxTwSLxCxHCiNb3ZRqAA@mail.gmail.com>
 <CACJ=gTg02OHi_WMm1nYkxvoUb4NtF6P011fYXyfN4LRaaDntOg@mail.gmail.com>
 <CADHSJjDZR14210fO5s4x1NFDFmPBOwJo+xDmYC4NQcnEAJPZ_g@mail.gmail.com>
Message-ID: <CAB5Fpx4RfkmQXMYUCDTsbBPscixU5nt_tZpZ-PL+FDPYPwXy0w@mail.gmail.com>

+1

On Wed, Apr 5, 2017 at 9:06 AM, Utkarsh Ayachit
<utkarsh.ayachit at kitware.com> wrote:
> +1
>
> On Wed, Apr 5, 2017 at 8:15 AM, Joachim Pouderoux
> <joachim.pouderoux at kitware.com> wrote:
>> I agree with you testing is for 'advanced users' and should be OFF by
>> default.
>> Note that BUILD_TESTING=OFF is default value on VTK.
>>
>> Joachim
>>
>> Joachim Pouderoux, PhD
>>
>> Technical Expert - Scientific Computing Team
>> Kitware SAS
>>
>>
>> 2017-04-05 3:03 GMT-04:00 Mathieu Westphal <mathieu.westphal at kitware.com>:
>>>
>>> Hi
>>>
>>> I would like to change BUILD_TESTING default value to OFF.
>>> If somebody have some intencive regarding keeping it to ON, please let me
>>> know !
>>>
>>> Regards,
>>>
>>> Mathieu Westphal
>>>
>>> _______________________________________________
>>> Powered by www.kitware.com
>>>
>>> Visit other Kitware open-source projects at
>>> http://www.kitware.com/opensource/opensource.html
>>>
>>> Search the list archives at:
>>> http://markmail.org/search/?q=Paraview-developers
>>>
>>> Follow this link to subscribe/unsubscribe:
>>> http://public.kitware.com/mailman/listinfo/paraview-developers
>>>
>>
>>
>> _______________________________________________
>> Powered by www.kitware.com
>>
>> Visit other Kitware open-source projects at
>> http://www.kitware.com/opensource/opensource.html
>>
>> Search the list archives at:
>> http://markmail.org/search/?q=Paraview-developers
>>
>> Follow this link to subscribe/unsubscribe:
>> http://public.kitware.com/mailman/listinfo/paraview-developers
>>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html
>
> Search the list archives at: http://markmail.org/search/?q=Paraview-developers
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview-developers



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

From wascott at sandia.gov  Wed Apr  5 12:56:23 2017
From: wascott at sandia.gov (Scott, W Alan)
Date: Wed, 5 Apr 2017 16:56:23 +0000
Subject: [Paraview-developers] [EXTERNAL] Re: BUILD_TESTING Default value
In-Reply-To: <CAB5Fpx4RfkmQXMYUCDTsbBPscixU5nt_tZpZ-PL+FDPYPwXy0w@mail.gmail.com>
References: <CAC2t4URNWcp7DbmBFkxZYdvLmf09eJRxTwSLxCxHCiNb3ZRqAA@mail.gmail.com>
 <CACJ=gTg02OHi_WMm1nYkxvoUb4NtF6P011fYXyfN4LRaaDntOg@mail.gmail.com>
 <CADHSJjDZR14210fO5s4x1NFDFmPBOwJo+xDmYC4NQcnEAJPZ_g@mail.gmail.com>
 <CAB5Fpx4RfkmQXMYUCDTsbBPscixU5nt_tZpZ-PL+FDPYPwXy0w@mail.gmail.com>
Message-ID: <614c6354338742dabbc7b018c553e779@ES01AMSNLNT.srn.sandia.gov>

I have always hard coded it off from the beginning of time.  Seems silly for me to have to do such..

Alan

> -----Original Message-----
> From: Paraview-developers [mailto:paraview-developers-
> bounces at paraview.org] On Behalf Of Cory Quammen
> Sent: Wednesday, April 5, 2017 8:54 AM
> To: Ayachit, Utkarsh (External Contacts) <utkarsh.ayachit at kitware.com>
> Cc: ParaView Developers <paraview-developers at paraview.org>
> Subject: [EXTERNAL] Re: [Paraview-developers] BUILD_TESTING Default
> value
> 
> +1
> 
> On Wed, Apr 5, 2017 at 9:06 AM, Utkarsh Ayachit
> <utkarsh.ayachit at kitware.com> wrote:
> > +1
> >
> > On Wed, Apr 5, 2017 at 8:15 AM, Joachim Pouderoux
> > <joachim.pouderoux at kitware.com> wrote:
> >> I agree with you testing is for 'advanced users' and should be OFF by
> >> default.
> >> Note that BUILD_TESTING=OFF is default value on VTK.
> >>
> >> Joachim
> >>
> >> Joachim Pouderoux, PhD
> >>
> >> Technical Expert - Scientific Computing Team Kitware SAS
> >>
> >>
> >> 2017-04-05 3:03 GMT-04:00 Mathieu Westphal
> <mathieu.westphal at kitware.com>:
> >>>
> >>> Hi
> >>>
> >>> I would like to change BUILD_TESTING default value to OFF.
> >>> If somebody have some intencive regarding keeping it to ON, please let
> me
> >>> know !
> >>>
> >>> Regards,
> >>>
> >>> Mathieu Westphal
> >>>
> >>> _______________________________________________
> >>> Powered by www.kitware.com
> >>>
> >>> Visit other Kitware open-source projects at
> >>> http://www.kitware.com/opensource/opensource.html
> >>>
> >>> Search the list archives at:
> >>> http://markmail.org/search/?q=Paraview-developers
> >>>
> >>> Follow this link to subscribe/unsubscribe:
> >>> http://public.kitware.com/mailman/listinfo/paraview-developers
> >>>
> >>
> >>
> >> _______________________________________________
> >> Powered by www.kitware.com
> >>
> >> Visit other Kitware open-source projects at
> >> http://www.kitware.com/opensource/opensource.html
> >>
> >> Search the list archives at:
> >> http://markmail.org/search/?q=Paraview-developers
> >>
> >> Follow this link to subscribe/unsubscribe:
> >> http://public.kitware.com/mailman/listinfo/paraview-developers
> >>
> > _______________________________________________
> > Powered by www.kitware.com
> >
> > Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
> >
> > Search the list archives at: http://markmail.org/search/?q=Paraview-
> developers
> >
> > Follow this link to subscribe/unsubscribe:
> > http://public.kitware.com/mailman/listinfo/paraview-developers
> 
> 
> 
> --
> 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 utkarsh.ayachit at kitware.com  Wed Apr  5 13:15:19 2017
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Wed, 5 Apr 2017 13:15:19 -0400
Subject: [Paraview-developers] ParaView is hanging Mac when closing
In-Reply-To: <a5701670c44640acb319755721e2f29d@ES01AMSNLNT.srn.sandia.gov>
References: <a5701670c44640acb319755721e2f29d@ES01AMSNLNT.srn.sandia.gov>
Message-ID: <CADHSJjAom9p1zc=hh2ZmbiMNE4g8-C_EJCjMNyeMF876qL7CCQ@mail.gmail.com>

Alan,

What kind of Mac hardware does you user have? Also, what happened when
you ran via the terminal? Does it still hang? Does it produce any
output?

Next, if the issue is reproducible when you run via terminal, then try
running via lldb (even for the release build) and where it hangs,
Ctrl-C and let's see if the stack can point where it's hanging.

Utkarsh

On Tue, Apr 4, 2017 at 4:46 PM, Scott, W Alan <wascott at sandia.gov> wrote:
> Utkarsh,
>
>
>
> I have a user that is seeing a strange hang with PV 5.3.0, and his Mac.  He
> is dealing with a different issue (probably a bad sideset on a large
> dataset), which is crashing the ParaView server.  At this point, ParaView
> client dies (not unexpected).  However, ParaView continues to appear
> running.  If you right click on ParaView on the doc, and you say close,
> ParaView disappears.  Terminal/ ps -ef does not show ParaView.  But, it
> remains in the doc, with the little dot below saying it is running.
>
>
>
> At this point, my user can?t start up another ParaView instance and connect
> remotely, since the port appears to be tied up.  The only option is to
> reboot.  But, the mac won?t reboot!  It is hanging on the ParaView process
> that is still coming down.   So, we are having to power cycle the Mac.
>
>
>
> I cannot replicate this on my macbook pro, thus am not writing up a bug
> (yet).    When we tried running ParaView from a terminal window, no warning
> messages were seen, and ParaView closed correctly.
>
>
>
> User?s OS is: 10.11.6 (El Capitan)
>
> My OS is: 10.11.6 (El Capitan)
>
>
>
> My user has two AMD FirePro D300 graphics cards.
>
>
>
> Any 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
>
>
>
> The most exciting phrase to hear in science
>
> is not "Eureka!" but "That's funny..."  -- Isaac Asimov
>
> ---------------------------------------------------------
>
>
>
>
> _______________________________________________
> 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 wascott at sandia.gov  Wed Apr  5 13:28:08 2017
From: wascott at sandia.gov (Scott, W Alan)
Date: Wed, 5 Apr 2017 17:28:08 +0000
Subject: [Paraview-developers] [EXTERNAL] Re: ParaView is hanging Mac
 when closing
In-Reply-To: <CADHSJjAom9p1zc=hh2ZmbiMNE4g8-C_EJCjMNyeMF876qL7CCQ@mail.gmail.com>
References: <a5701670c44640acb319755721e2f29d@ES01AMSNLNT.srn.sandia.gov>
 <CADHSJjAom9p1zc=hh2ZmbiMNE4g8-C_EJCjMNyeMF876qL7CCQ@mail.gmail.com>
Message-ID: <9d61f253b2e34d2998c2145097572c96@ES01AMSNLNT.srn.sandia.gov>

I will ask regarding hardware. 

We tried running ParaView from the terminal, and it does NOT hang.  No warnings at all.  I was totally surprised.

Alan

> -----Original Message-----
> From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com]
> Sent: Wednesday, April 5, 2017 11:15 AM
> To: Scott, W Alan <wascott at sandia.gov>
> Cc: paraview-developers at paraview.org
> Subject: [EXTERNAL] Re: [Paraview-developers] ParaView is hanging Mac
> when closing
> 
> Alan,
> 
> What kind of Mac hardware does you user have? Also, what happened when
> you ran via the terminal? Does it still hang? Does it produce any output?
> 
> Next, if the issue is reproducible when you run via terminal, then try running
> via lldb (even for the release build) and where it hangs, Ctrl-C and let's see if
> the stack can point where it's hanging.
> 
> Utkarsh
> 
> On Tue, Apr 4, 2017 at 4:46 PM, Scott, W Alan <wascott at sandia.gov> wrote:
> > Utkarsh,
> >
> >
> >
> > I have a user that is seeing a strange hang with PV 5.3.0, and his
> > Mac.  He is dealing with a different issue (probably a bad sideset on
> > a large dataset), which is crashing the ParaView server.  At this
> > point, ParaView client dies (not unexpected).  However, ParaView
> > continues to appear running.  If you right click on ParaView on the
> > doc, and you say close, ParaView disappears.  Terminal/ ps -ef does
> > not show ParaView.  But, it remains in the doc, with the little dot below
> saying it is running.
> >
> >
> >
> > At this point, my user can?t start up another ParaView instance and
> > connect remotely, since the port appears to be tied up.  The only
> > option is to reboot.  But, the mac won?t reboot!  It is hanging on the
> ParaView process
> > that is still coming down.   So, we are having to power cycle the Mac.
> >
> >
> >
> > I cannot replicate this on my macbook pro, thus am not writing up a bug
> > (yet).    When we tried running ParaView from a terminal window, no
> warning
> > messages were seen, and ParaView closed correctly.
> >
> >
> >
> > User?s OS is: 10.11.6 (El Capitan)
> >
> > My OS is: 10.11.6 (El Capitan)
> >
> >
> >
> > My user has two AMD FirePro D300 graphics cards.
> >
> >
> >
> > Any 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
> >
> >
> >
> > The most exciting phrase to hear in science
> >
> > is not "Eureka!" but "That's funny..."  -- Isaac Asimov
> >
> > ---------------------------------------------------------
> >
> >
> >
> >
> > _______________________________________________
> > 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 utkarsh.ayachit at kitware.com  Wed Apr  5 15:54:51 2017
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Wed, 5 Apr 2017 15:54:51 -0400
Subject: [Paraview-developers] Is someone editing descrptions on ParaView
	Issues
Message-ID: <CADHSJjD3-y2BsCGV+wJs4V0CXHNfz9W+rrJoba-1HMv0TieFzQ@mail.gmail.com>

Folks,

Is someone editing descriptions on ParaView issue tracker? For some
reason all issues seem to be getting edited and seems to many for a
person to be doing it.

Thanks
Utkarsh

From brad.king at kitware.com  Wed Apr  5 15:59:02 2017
From: brad.king at kitware.com (Brad King)
Date: Wed, 5 Apr 2017 15:59:02 -0400
Subject: [Paraview-developers] Is someone editing descrptions on
 ParaView Issues
In-Reply-To: <CADHSJjD3-y2BsCGV+wJs4V0CXHNfz9W+rrJoba-1HMv0TieFzQ@mail.gmail.com>
References: <CADHSJjD3-y2BsCGV+wJs4V0CXHNfz9W+rrJoba-1HMv0TieFzQ@mail.gmail.com>
Message-ID: <4a84b6d8-b9c4-a0dd-47ed-64e3bdaf1482@kitware.com>

On 04/05/2017 03:54 PM, Utkarsh Ayachit wrote:
> Is someone editing descriptions on ParaView issue tracker? For some
> reason all issues seem to be getting edited and seems to many for a
> person to be doing it.

All the recently updated issues have the "5.4 (ISC 2017)" milestone.
Did anyone edit the milestone in some way, such as changing its name?

-Brad


From utkarsh.ayachit at kitware.com  Wed Apr  5 15:59:45 2017
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Wed, 5 Apr 2017 15:59:45 -0400
Subject: [Paraview-developers] Is someone editing descrptions on
	ParaView Issues
In-Reply-To: <4a84b6d8-b9c4-a0dd-47ed-64e3bdaf1482@kitware.com>
References: <CADHSJjD3-y2BsCGV+wJs4V0CXHNfz9W+rrJoba-1HMv0TieFzQ@mail.gmail.com>
 <4a84b6d8-b9c4-a0dd-47ed-64e3bdaf1482@kitware.com>
Message-ID: <CADHSJjCs0yaANk5NLEFzf9aDHAT-AR_mkaVmTUapMBOvtBfnJg@mail.gmail.com>

> All the recently updated issues have the "5.4 (ISC 2017)" milestone.
> Did anyone edit the milestone in some way, such as changing its name?

Not to my knowledge.

From utkarsh.ayachit at kitware.com  Wed Apr  5 16:03:58 2017
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Wed, 5 Apr 2017 16:03:58 -0400
Subject: [Paraview-developers] Is someone editing descrptions on
	ParaView Issues
In-Reply-To: <CADHSJjCs0yaANk5NLEFzf9aDHAT-AR_mkaVmTUapMBOvtBfnJg@mail.gmail.com>
References: <CADHSJjD3-y2BsCGV+wJs4V0CXHNfz9W+rrJoba-1HMv0TieFzQ@mail.gmail.com>
 <4a84b6d8-b9c4-a0dd-47ed-64e3bdaf1482@kitware.com>
 <CADHSJjCs0yaANk5NLEFzf9aDHAT-AR_mkaVmTUapMBOvtBfnJg@mail.gmail.com>
Message-ID: <CADHSJjCWHL2D9nADh+sZSjPPhtbmbH2TKW1dWJs=1TJf8-oKYw@mail.gmail.com>

I believe it started with this issue:
https://gitlab.kitware.com/paraview/paraview/issues/17136

It says the description was edited at 10:22 am. Since then quite a few
issues have been so "edited".

On Wed, Apr 5, 2017 at 3:59 PM, Utkarsh Ayachit
<utkarsh.ayachit at kitware.com> wrote:
>> All the recently updated issues have the "5.4 (ISC 2017)" milestone.
>> Did anyone edit the milestone in some way, such as changing its name?
>
> Not to my knowledge.

From cory.quammen at kitware.com  Wed Apr  5 16:05:15 2017
From: cory.quammen at kitware.com (Cory Quammen)
Date: Wed, 5 Apr 2017 16:05:15 -0400
Subject: [Paraview-developers] Is someone editing descrptions on
	ParaView Issues
In-Reply-To: <CADHSJjCWHL2D9nADh+sZSjPPhtbmbH2TKW1dWJs=1TJf8-oKYw@mail.gmail.com>
References: <CADHSJjD3-y2BsCGV+wJs4V0CXHNfz9W+rrJoba-1HMv0TieFzQ@mail.gmail.com>
 <4a84b6d8-b9c4-a0dd-47ed-64e3bdaf1482@kitware.com>
 <CADHSJjCs0yaANk5NLEFzf9aDHAT-AR_mkaVmTUapMBOvtBfnJg@mail.gmail.com>
 <CADHSJjCWHL2D9nADh+sZSjPPhtbmbH2TKW1dWJs=1TJf8-oKYw@mail.gmail.com>
Message-ID: <CAB5Fpx7WA5Nho4iA8p+zbEV7Xv8zpLwB-=s7Pv4z3OpwR8j-Jw@mail.gmail.com>

On Wed, Apr 5, 2017 at 4:03 PM, Utkarsh Ayachit
<utkarsh.ayachit at kitware.com> wrote:
> I believe it started with this issue:
> https://gitlab.kitware.com/paraview/paraview/issues/17136
>
> It says the description was edited at 10:22 am. Since then quite a few
> issues have been so "edited".

I noticed that, too. No idea who or what process is doing it, though.

> On Wed, Apr 5, 2017 at 3:59 PM, Utkarsh Ayachit
> <utkarsh.ayachit at kitware.com> wrote:
>>> All the recently updated issues have the "5.4 (ISC 2017)" milestone.
>>> Did anyone edit the milestone in some way, such as changing its name?
>>
>> Not to my knowledge.
> _______________________________________________
> 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.

From brad.king at kitware.com  Wed Apr  5 16:10:21 2017
From: brad.king at kitware.com (Brad King)
Date: Wed, 5 Apr 2017 16:10:21 -0400
Subject: [Paraview-developers] Is someone editing descrptions on
 ParaView Issues
In-Reply-To: <CAB5Fpx7WA5Nho4iA8p+zbEV7Xv8zpLwB-=s7Pv4z3OpwR8j-Jw@mail.gmail.com>
References: <CADHSJjD3-y2BsCGV+wJs4V0CXHNfz9W+rrJoba-1HMv0TieFzQ@mail.gmail.com>
 <4a84b6d8-b9c4-a0dd-47ed-64e3bdaf1482@kitware.com>
 <CADHSJjCs0yaANk5NLEFzf9aDHAT-AR_mkaVmTUapMBOvtBfnJg@mail.gmail.com>
 <CADHSJjCWHL2D9nADh+sZSjPPhtbmbH2TKW1dWJs=1TJf8-oKYw@mail.gmail.com>
 <CAB5Fpx7WA5Nho4iA8p+zbEV7Xv8zpLwB-=s7Pv4z3OpwR8j-Jw@mail.gmail.com>
Message-ID: <6b5f76f2-397e-32d6-4f42-723bdce7cb6c@kitware.com>

On 04/05/2017 04:05 PM, Cory Quammen wrote:
> On Wed, Apr 5, 2017 at 4:03 PM, Utkarsh Ayachit wrote:
>> I believe it started with this issue:
>> https://gitlab.kitware.com/paraview/paraview/issues/17136
>>
>> It says the description was edited at 10:22 am. Since then quite a few
>> issues have been so "edited".
> 
> I noticed that, too. No idea who or what process is doing it, though.

FYI, even though the "Edited $time" messages appear at the bottom of the
descriptions they don't refer only to the descriptions themselves.  Any
event that updates an issue in any way will update the "Edited $time"
message.

-Brad


From wascott at sandia.gov  Wed Apr  5 16:10:41 2017
From: wascott at sandia.gov (Scott, W Alan)
Date: Wed, 5 Apr 2017 20:10:41 +0000
Subject: [Paraview-developers] [EXTERNAL] Re: Is someone editing
 descrptions on	ParaView Issues
In-Reply-To: <CAB5Fpx7WA5Nho4iA8p+zbEV7Xv8zpLwB-=s7Pv4z3OpwR8j-Jw@mail.gmail.com>
References: <CADHSJjD3-y2BsCGV+wJs4V0CXHNfz9W+rrJoba-1HMv0TieFzQ@mail.gmail.com>
 <4a84b6d8-b9c4-a0dd-47ed-64e3bdaf1482@kitware.com>
 <CADHSJjCs0yaANk5NLEFzf9aDHAT-AR_mkaVmTUapMBOvtBfnJg@mail.gmail.com>
 <CADHSJjCWHL2D9nADh+sZSjPPhtbmbH2TKW1dWJs=1TJf8-oKYw@mail.gmail.com>
 <CAB5Fpx7WA5Nho4iA8p+zbEV7Xv8zpLwB-=s7Pv4z3OpwR8j-Jw@mail.gmail.com>
Message-ID: <12170a281ad54c2f984273cec3b65759@ES01AMSNLNT.srn.sandia.gov>

That's my bug.  I have not even opened that bug (or commented or edited) it today (or for the last 2 months).  


> -----Original Message-----
> From: Paraview-developers [mailto:paraview-developers-
> bounces at paraview.org] On Behalf Of Cory Quammen
> Sent: Wednesday, April 5, 2017 2:05 PM
> To: Ayachit, Utkarsh (External Contacts) <utkarsh.ayachit at kitware.com>
> Cc: ParaView Developers <paraview-developers at paraview.org>
> Subject: [EXTERNAL] Re: [Paraview-developers] Is someone editing
> descrptions on ParaView Issues
> 
> On Wed, Apr 5, 2017 at 4:03 PM, Utkarsh Ayachit
> <utkarsh.ayachit at kitware.com> wrote:
> > I believe it started with this issue:
> > https://gitlab.kitware.com/paraview/paraview/issues/17136
> >
> > It says the description was edited at 10:22 am. Since then quite a few
> > issues have been so "edited".
> 
> I noticed that, too. No idea who or what process is doing it, though.
> 
> > On Wed, Apr 5, 2017 at 3:59 PM, Utkarsh Ayachit
> > <utkarsh.ayachit at kitware.com> wrote:
> >>> All the recently updated issues have the "5.4 (ISC 2017)" milestone.
> >>> Did anyone edit the milestone in some way, such as changing its name?
> >>
> >> Not to my knowledge.
> > _______________________________________________
> > 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.
> _______________________________________________
> 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 utkarsh.ayachit at kitware.com  Wed Apr  5 16:28:16 2017
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Wed, 5 Apr 2017 16:28:16 -0400
Subject: [Paraview-developers] Is someone editing descrptions on
	ParaView Issues
In-Reply-To: <6b5f76f2-397e-32d6-4f42-723bdce7cb6c@kitware.com>
References: <CADHSJjD3-y2BsCGV+wJs4V0CXHNfz9W+rrJoba-1HMv0TieFzQ@mail.gmail.com>
 <4a84b6d8-b9c4-a0dd-47ed-64e3bdaf1482@kitware.com>
 <CADHSJjCs0yaANk5NLEFzf9aDHAT-AR_mkaVmTUapMBOvtBfnJg@mail.gmail.com>
 <CADHSJjCWHL2D9nADh+sZSjPPhtbmbH2TKW1dWJs=1TJf8-oKYw@mail.gmail.com>
 <CAB5Fpx7WA5Nho4iA8p+zbEV7Xv8zpLwB-=s7Pv4z3OpwR8j-Jw@mail.gmail.com>
 <6b5f76f2-397e-32d6-4f42-723bdce7cb6c@kitware.com>
Message-ID: <CADHSJjC0O5NTGvpuiRso+woacE-vYSCKM9ymeNJtjTOEfYK=SA@mail.gmail.com>

Hmm. Let's keep a wary eye on it. Not sure if there's anything to be
alarmed about just yet. Seems peculiar for sure.

On Wed, Apr 5, 2017 at 4:10 PM, Brad King <brad.king at kitware.com> wrote:
> On 04/05/2017 04:05 PM, Cory Quammen wrote:
>> On Wed, Apr 5, 2017 at 4:03 PM, Utkarsh Ayachit wrote:
>>> I believe it started with this issue:
>>> https://gitlab.kitware.com/paraview/paraview/issues/17136
>>>
>>> It says the description was edited at 10:22 am. Since then quite a few
>>> issues have been so "edited".
>>
>> I noticed that, too. No idea who or what process is doing it, though.
>
> FYI, even though the "Edited $time" messages appear at the bottom of the
> descriptions they don't refer only to the descriptions themselves.  Any
> event that updates an issue in any way will update the "Edited $time"
> message.
>
> -Brad
>

From wascott at sandia.gov  Wed Apr  5 16:43:39 2017
From: wascott at sandia.gov (Scott, W Alan)
Date: Wed, 5 Apr 2017 20:43:39 +0000
Subject: [Paraview-developers] ParaView is hanging Mac when closing
Message-ID: <4592fd52b9f6443896a8981bd9750cc3@ES01AMSNLNT.srn.sandia.gov>




[cid:02C2C788-7748-45FB-8D36-F3F2AFD1F586 at srn.sandia.gov]

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20170405/426efb83/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Screen Shot 2017-04-05 at 13.57.33.png
Type: image/png
Size: 75753 bytes
Desc: Screen Shot 2017-04-05 at 13.57.33.png
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20170405/426efb83/attachment-0001.png>

From utkarsh.ayachit at kitware.com  Wed Apr  5 17:12:11 2017
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Wed, 5 Apr 2017 17:12:11 -0400
Subject: [Paraview-developers] [EXTERNAL] Re: ParaView is hanging Mac
	when closing
In-Reply-To: <9d61f253b2e34d2998c2145097572c96@ES01AMSNLNT.srn.sandia.gov>
References: <a5701670c44640acb319755721e2f29d@ES01AMSNLNT.srn.sandia.gov>
 <CADHSJjAom9p1zc=hh2ZmbiMNE4g8-C_EJCjMNyeMF876qL7CCQ@mail.gmail.com>
 <9d61f253b2e34d2998c2145097572c96@ES01AMSNLNT.srn.sandia.gov>
Message-ID: <CADHSJjD7OTyY32uer-LuGD0gM-fR3QrderJT_VuYjwSsueV49A@mail.gmail.com>

> We tried running ParaView from the terminal, and it does NOT hang.  No warnings at all.  I was totally surprised.

Hmm. Then let's try this. Launch as normal. Attach to the running
process via lldb. Then quit and it it hangs, Ctrl+C and let's look at
the call stack.

Utkarsh

From wascott at sandia.gov  Wed Apr  5 20:35:48 2017
From: wascott at sandia.gov (Scott, W Alan)
Date: Thu, 6 Apr 2017 00:35:48 +0000
Subject: [Paraview-developers] Superbuild error
Message-ID: <4f90271826fc470095ffd4e01f1dce3e@ES01AMSNLNT.srn.sandia.gov>

I'm doing Superbuilds again.  Here is the first error.  I am failing getting to vtk-m.

[ 60%] Performing download step (git clone) for 'vtkm'
Cloning into 'src'...
fatal: unable to access 'https://gitlab.kitware.com/vtk/vtk-m.git/': Failed connect to gitlab.kitware.com:443; Operation now in progress
Cloning into 'src'...

But, I can pull other tarballs from where I am:
Scanning dependencies of target tbb
[ 52%] Creating directories for 'tbb'
[ 53%] Performing download step (download, verify and extract) for 'tbb'
-- downloading...
     src='http://www.paraview.org/files/dependencies/tbb44_20150728oss_lin_0.tgz'
     dst='<snip>/tbb44_20150728oss_lin_0.tgz'
     timeout='none'
-- [download 0% complete]


Help?



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

The most exciting phrase to hear in science
is not "Eureka!" but "That's funny..."  -- Isaac Asimov
---------------------------------------------------------

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

From utkarsh.ayachit at kitware.com  Wed Apr  5 23:48:07 2017
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Wed, 5 Apr 2017 23:48:07 -0400
Subject: [Paraview-developers] Superbuild error
In-Reply-To: <4f90271826fc470095ffd4e01f1dce3e@ES01AMSNLNT.srn.sandia.gov>
References: <4f90271826fc470095ffd4e01f1dce3e@ES01AMSNLNT.srn.sandia.gov>
Message-ID: <CADHSJjC+Wk_D7Fx-XLa6U0KuBaoV=mM1Q59C2v-2phj2zDNVcA@mail.gmail.com>

Alan,

Can you try manually cloning the VTK-m repo? Does it work?

You can clone as follows:

> git clone https://gitlab.kitware.com/vtk/vtk-m.git

Utkarsh

On Wed, Apr 5, 2017 at 8:35 PM, Scott, W Alan <wascott at sandia.gov> wrote:
> I?m doing Superbuilds again.  Here is the first error.  I am failing getting
> to vtk-m.
>
>
>
> [ 60%] Performing download step (git clone) for 'vtkm'
>
> Cloning into 'src'...
>
> fatal: unable to access 'https://gitlab.kitware.com/vtk/vtk-m.git/': Failed
> connect to gitlab.kitware.com:443; Operation now in progress
>
> Cloning into 'src'...
>
>
>
> But, I can pull other tarballs from where I am:
>
> Scanning dependencies of target tbb
>
> [ 52%] Creating directories for 'tbb'
>
> [ 53%] Performing download step (download, verify and extract) for 'tbb'
>
> -- downloading...
>
>
> src='http://www.paraview.org/files/dependencies/tbb44_20150728oss_lin_0.tgz'
>
>      dst='<snip>/tbb44_20150728oss_lin_0.tgz'
>
>      timeout='none'
>
> -- [download 0% complete]
>
>
>
>
>
> Help?
>
>
>
>
>
>
>
> 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
>
>
>
> The most exciting phrase to hear in science
>
> is not "Eureka!" but "That's funny..."  -- Isaac Asimov
>
> ---------------------------------------------------------
>
>
>
>
> _______________________________________________
> 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 wascott at sandia.gov  Fri Apr  7 16:41:52 2017
From: wascott at sandia.gov (Scott, W Alan)
Date: Fri, 7 Apr 2017 20:41:52 +0000
Subject: [Paraview-developers] strcpy and other bad actors
Message-ID: <6f18e30b711349528f39eb5e8a2e0ddb@ES01AMSNLNT.srn.sandia.gov>

I am reading a plug here at Sandia about the new Samsung phone and it's very vulnerable software: https://motherboard.vice.com/en_us/article/samsung-tizen-operating-system-bugs-vulnerabilities

When I looked up strcpy, I found this: https://randomascii.wordpress.com/2013/04/03/stop-using-strncpy-already/

It made me start to wonder - do we care about ParaView (which of course runs in user space).  I just looked, and there are about 1800 uses of strcpy in ParaView.  Is that an issue?

Thanks all,

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

The most exciting phrase to hear in science
is not "Eureka!" but "That's funny..."  -- Isaac Asimov
---------------------------------------------------------

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20170407/00943d5a/attachment.html>

From mzhao at cea-igp.ac.cn  Mon Apr 10 01:55:27 2017
From: mzhao at cea-igp.ac.cn (=?utf-8?B?6LW15piO?=)
Date: Mon, 10 Apr 2017 13:55:27 +0800
Subject: [Paraview-developers] =?utf-8?b?5Zue5aSNOiBSZTogIE5vIGxpdmUgdmlz?=
	=?utf-8?q?ualization_of_the_catalyst_examples?=
In-Reply-To: <CAMaOp+FnDnaM1Dj3ztLV0_g94S4pyo2dfNm3yLa1+Uz5ZV3gUQ@mail.gmail.com>
References: <4b884ee5ac7ce6a8a543cb3df7b01d11@cea-igp.ac.cn>,
 <CAMaOp+FnDnaM1Dj3ztLV0_g94S4pyo2dfNm3yLa1+Uz5ZV3gUQ@mail.gmail.com>
Message-ID: <6e2735c226f754ca7a0cf34a0553a998@cea-igp.ac.cn>

Hi,
I tried under Paraview 5.3 and the error message is quite different:
p, li { white-space: pre-wrap; }

ERROR: In /home/zm/ParaView_superbuild/build/superbuild/paraview/src/VTK/Parallel/Core/vtkSocketCommunicator.cxx, line 809

vtkSocketCommunicator (0x55cb425a3130): Could not receive tag. 1
then there will be a popup window saying:
p, li { white-space: pre-wrap; }

CxxFullExample feslicecinema.py 

And I run paraview catalyst on the command line and make it listen at port 22222

[zm at centos7 bin]$ ./paraview

Accepting connection(s): centos7.destop:22222
Accepting connection(s): centos7.destop:22222
Invalid output port : pqPipelineSource::getOutputPort( 0 ). Available number of output ports:  0 
Aborted (core dumped)

Then Paraview exit and without any live visualization output.Anyone has any idea of this?The catalyst is claimed to have the ability to give in situ outputs...

Best regards
Ming

_______________________________________________

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/20170410/6a77215f/attachment.html>

From mzhao at cea-igp.ac.cn  Mon Apr 10 02:07:08 2017
From: mzhao at cea-igp.ac.cn (=?gbk?B?1dTD9w==?=)
Date: Mon, 10 Apr 2017 14:07:08 +0800
Subject: [Paraview-developers] live visualiztion error of paraview catalyst
Message-ID: <3eb3c63e81959c5bb798767d1f8781ab@cea-igp.ac.cn>

Hi,
I tried under Paraview 5.3 and the error message is quite different:

ERROR: In /home/zm/ParaView_superbuild/build/superbuild/paraview/src/VTK/Parallel/Core/vtkSocketCommunicator.cxx, line 809

vtkSocketCommunicator (0x55cb425a3130): Could not receive tag. 1
then there will be a popup window saying:

p, li { white-space: pre-wrap; }

Connection to Catalyst Co-Processor has been terminated involuntarily. This implies either a communication error, or that the Catalyst co-processor has terminated. The Catalyst session will now be cleaned up. You can start a new one if you want to monitor for additional Catalyst connection requests.
Are there anyone encounter similar problems?I tried centos and ubuntu,they all have this kind of error..
Best regardsMing
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20170410/408b4f60/attachment.html>

From andy.bauer at kitware.com  Mon Apr 10 08:30:28 2017
From: andy.bauer at kitware.com (Andy Bauer)
Date: Mon, 10 Apr 2017 08:30:28 -0400
Subject: [Paraview-developers] live visualiztion error of paraview
	catalyst
In-Reply-To: <3eb3c63e81959c5bb798767d1f8781ab@cea-igp.ac.cn>
References: <3eb3c63e81959c5bb798767d1f8781ab@cea-igp.ac.cn>
Message-ID: <CAMaOp+H00Egc7HgEFsoG8GrbdxfEvj7ggqA5d773aBrZ5m8JHw@mail.gmail.com>

Hi,

I have seen this error but have not been able to regularly replicate it.
Please let us know if you have a way to regularly replicate it so that
hopefully it can be fixed.

Best,
Andy

On Mon, Apr 10, 2017 at 2:07 AM, ?? <mzhao at cea-igp.ac.cn> wrote:

> Hi,
>
> I tried under Paraview 5.3 and the error message is quite different:
>
> ERROR: In /home/zm/ParaView_superbuild/build/superbuild/paraview/src/
> VTK/Parallel/Core/vtkSocketCommunicator.cxx, line 809
>
> vtkSocketCommunicator (0x55cb425a3130): Could not receive tag. 1
>
> then there will be a popup window saying:
>
> p, li { white-space: pre-wrap; }
>
> Connection to Catalyst Co-Processor has been terminated involuntarily.
> This implies either a communication error, or that the Catalyst
> co-processor has terminated. The Catalyst session will now be cleaned up.
> You can start a new one if you want to monitor for additional Catalyst
> connection requests.
>
> Are there anyone encounter similar problems?I tried centos and ubuntu,they
> all have this kind of error..
>
> Best regards
> Ming
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20170410/aa11311a/attachment.html>

From ben.boeckel at kitware.com  Mon Apr 10 09:48:20 2017
From: ben.boeckel at kitware.com (Ben Boeckel)
Date: Mon, 10 Apr 2017 09:48:20 -0400
Subject: [Paraview-developers] strcpy and other bad actors
In-Reply-To: <6f18e30b711349528f39eb5e8a2e0ddb@ES01AMSNLNT.srn.sandia.gov>
References: <6f18e30b711349528f39eb5e8a2e0ddb@ES01AMSNLNT.srn.sandia.gov>
Message-ID: <20170410134820.GA12500@megas.kitware.com>

On Fri, Apr 07, 2017 at 20:41:52 +0000, Scott, W Alan wrote:
> It made me start to wonder - do we care about ParaView (which of
> course runs in user space).  I just looked, and there are about 1800
> uses of strcpy in ParaView.  Is that an issue?

As with many thing, it depends :) . I wouldn't object to moving to at
least `strncpy`, but I suspect that just switching over to `std::string`
would just be easier in the long run (since even `strncpy` has buffer
calculations which can be done improperly). That may require some
reworking around each change though, so is not likely scriptable.

--Ben

From kmorel at sandia.gov  Mon Apr 10 11:36:01 2017
From: kmorel at sandia.gov (Moreland, Kenneth)
Date: Mon, 10 Apr 2017 15:36:01 +0000
Subject: [Paraview-developers] strcpy and other bad actors
Message-ID: <7890573b66954d2d80225f639876bc10@ES08AMSNLNT.srn.sandia.gov>

If you are worried about malicious code, I would be even more worried about the use of sprintf. Like strcpy there is no check that the target buffer is not overrun, and it is much harder to predict how large of a buffer you will need to begin with. Plus, there are multiple points in the ParaView interface that allow users to pass format descriptors to sprintf from the GUI or a script. This could definitely be a target for malicious code. We could (and probably should) protected these by using snprintf, but in the cases where users pass in their own format descriptors they could do all sorts of weird stuff like read data off the stack.

-Ken

-----Original Message-----
From: Paraview-developers [mailto:paraview-developers-bounces at paraview.org] On Behalf Of Ben Boeckel
Sent: Monday, April 10, 2017 7:48 AM
To: Scott, W Alan <wascott at sandia.gov>
Cc: paraview-developers at paraview.org
Subject: [EXTERNAL] Re: [Paraview-developers] strcpy and other bad actors

On Fri, Apr 07, 2017 at 20:41:52 +0000, Scott, W Alan wrote:
> It made me start to wonder - do we care about ParaView (which of 
> course runs in user space).  I just looked, and there are about 1800 
> uses of strcpy in ParaView.  Is that an issue?

As with many thing, it depends :) . I wouldn't object to moving to at least `strncpy`, but I suspect that just switching over to `std::string` would just be easier in the long run (since even `strncpy` has buffer calculations which can be done improperly). That may require some reworking around each change though, so is not likely scriptable.

--Ben
_______________________________________________
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 thomasblome at startmail.com  Mon Apr 10 11:40:22 2017
From: thomasblome at startmail.com (thomasblome at startmail.com)
Date: Mon, 10 Apr 2017 17:40:22 +0200
Subject: [Paraview-developers] Spreadsheet View
Message-ID: <bac69c41dbfafd4216e03047402eaf27.startmail@www.startmail.com>

Hi,

I would like to display the coordinates in the paraview spreadsheet 
view which were generated in my simulation.
After I have established a Catalyst Live connection I select the input 
item in the "Pipeline Browser"-view in Paraview.
In the information panel below it says the number of points equals 21 
and the bounds (i.e. x,y,z ranges) are displayed correctly, too.
However, when I open up another tab and select "Spreadsheet View" to 
take a look at the actual coordinates, I get an error message saying:

ERROR: In 
C:\Kitware\ParaView-v5.1.0\VTK\Common\ExecutionModel\vtkExecutive.cxx, 
line 784
vtkPVCompositeDataPipeline (000000001377FA10): Algorithm 
vtkPVExtractSelection(0000000009DCE6D0) returned failure for request: 
vtkInformation (0000000014A42BE0)
? Debug: Off
? Modified Time: 299127
? Reference Count: 1
? Registered Events: (none)
? Request: REQUEST_DATA_OBJECT
? ALGORITHM_AFTER_FORWARD: 1
? FORWARD_DIRECTION: 0
? FROM_OUTPUT_PORT: 0

Does anybody know how to solve this? (I'm using Paraview 5.1.0)

Regards,
Thomas
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20170410/95b2f92f/attachment-0001.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/20170410/95b2f92f/attachment-0001.key>

From dave.demarle at kitware.com  Mon Apr 10 11:53:35 2017
From: dave.demarle at kitware.com (David E DeMarle)
Date: Mon, 10 Apr 2017 11:53:35 -0400
Subject: [Paraview-developers] strcpy and other bad actors
In-Reply-To: <7890573b66954d2d80225f639876bc10@ES08AMSNLNT.srn.sandia.gov>
References: <7890573b66954d2d80225f639876bc10@ES08AMSNLNT.srn.sandia.gov>
Message-ID: <CANjZAi_JCONv9udDTmg+-QCLRacEpapvjRJUR2M1yMxfv4km3w@mail.gmail.com>

In related news...
https://gitlab.kitware.com/vtk/vtk/merge_requests/2675


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

On Mon, Apr 10, 2017 at 11:36 AM, Moreland, Kenneth <kmorel at sandia.gov>
wrote:

> If you are worried about malicious code, I would be even more worried
> about the use of sprintf. Like strcpy there is no check that the target
> buffer is not overrun, and it is much harder to predict how large of a
> buffer you will need to begin with. Plus, there are multiple points in the
> ParaView interface that allow users to pass format descriptors to sprintf
> from the GUI or a script. This could definitely be a target for malicious
> code. We could (and probably should) protected these by using snprintf, but
> in the cases where users pass in their own format descriptors they could do
> all sorts of weird stuff like read data off the stack.
>
> -Ken
>
> -----Original Message-----
> From: Paraview-developers [mailto:paraview-developers-bounces at paraview.org]
> On Behalf Of Ben Boeckel
> Sent: Monday, April 10, 2017 7:48 AM
> To: Scott, W Alan <wascott at sandia.gov>
> Cc: paraview-developers at paraview.org
> Subject: [EXTERNAL] Re: [Paraview-developers] strcpy and other bad actors
>
> On Fri, Apr 07, 2017 at 20:41:52 +0000, Scott, W Alan wrote:
> > It made me start to wonder - do we care about ParaView (which of
> > course runs in user space).  I just looked, and there are about 1800
> > uses of strcpy in ParaView.  Is that an issue?
>
> As with many thing, it depends :) . I wouldn't object to moving to at
> least `strncpy`, but I suspect that just switching over to `std::string`
> would just be easier in the long run (since even `strncpy` has buffer
> calculations which can be done improperly). That may require some reworking
> around each change though, so is not likely scriptable.
>
> --Ben
> _______________________________________________
> 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/20170410/e352ae2a/attachment.html>

From andy.bauer at kitware.com  Mon Apr 10 11:59:22 2017
From: andy.bauer at kitware.com (Andy Bauer)
Date: Mon, 10 Apr 2017 11:59:22 -0400
Subject: [Paraview-developers] Spreadsheet View
In-Reply-To: <bac69c41dbfafd4216e03047402eaf27.startmail@www.startmail.com>
References: <bac69c41dbfafd4216e03047402eaf27.startmail@www.startmail.com>
Message-ID: <CAMaOp+HNjoxmLoL85WkieGA6oH6PG+g=REC=i470GJLJsU0cVA@mail.gmail.com>

Hi Thomas,

Are you selecting the filter in the Catalyst pipeline or have you already
extracted the Catalyst output to the pvserver to look at in the spreadsheet
view? The meta-information will be available when you highlight the items
in the either the Catalyst pipeline or pvserver pipeline but the full data
is not automatically shared with the pvserver (and thus will not be in the
pvserver pipeline) since it may be quite large.

I just tried doing this with ParaView master and it worked so it's possible
that this didn't work with PV 5.1 but has been fixed.

Cheers,
Andy



On Mon, Apr 10, 2017 at 11:40 AM, <thomasblome at startmail.com> wrote:

> Hi,
>
> I would like to display the coordinates in the paraview spreadsheet view
> which were generated in my simulation.
> After I have established a Catalyst Live connection I select the input
> item in the "Pipeline Browser"-view in Paraview.
> In the information panel below it says the number of points equals 21 and
> the bounds (i.e. x,y,z ranges) are displayed correctly, too.
> However, when I open up another tab and select "Spreadsheet View" to take
> a look at the actual coordinates, I get an error message saying:
>
> ERROR: In C:\Kitware\ParaView-v5.1.0\VTK\Common\ExecutionModel\vtkExecutive.cxx,
> line 784
> vtkPVCompositeDataPipeline (000000001377FA10): Algorithm
> vtkPVExtractSelection(0000000009DCE6D0) returned failure for request:
> vtkInformation (0000000014A42BE0)
>   Debug: Off
>   Modified Time: 299127
>   Reference Count: 1
>   Registered Events: (none)
>   Request: REQUEST_DATA_OBJECT
>   ALGORITHM_AFTER_FORWARD: 1
>   FORWARD_DIRECTION: 0
>   FROM_OUTPUT_PORT: 0
>
> Does anybody know how to solve this? (I'm using Paraview 5.1.0)
>
> 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/20170410/b89c400a/attachment.html>

From kmorel at sandia.gov  Mon Apr 10 12:30:11 2017
From: kmorel at sandia.gov (Moreland, Kenneth)
Date: Mon, 10 Apr 2017 16:30:11 +0000
Subject: [Paraview-developers] [EXTERNAL] Re: strcpy and other bad actors
In-Reply-To: <CANjZAi_JCONv9udDTmg+-QCLRacEpapvjRJUR2M1yMxfv4km3w@mail.gmail.com>
References: <7890573b66954d2d80225f639876bc10@ES08AMSNLNT.srn.sandia.gov>
 <CANjZAi_JCONv9udDTmg+-QCLRacEpapvjRJUR2M1yMxfv4km3w@mail.gmail.com>
Message-ID: <dd1a2c395ff84dd2bb0611a18f43ab20@ES08AMSNLNT.srn.sandia.gov>

Nice!

From: David E DeMarle [mailto:dave.demarle at kitware.com]
Sent: Monday, April 10, 2017 9:54 AM
To: Moreland, Kenneth <kmorel at sandia.gov>
Cc: Boeckel, Ben (External Contacts) <ben.boeckel at kitware.com>; Scott, W Alan <wascott at sandia.gov>; paraview-developers at paraview.org
Subject: [EXTERNAL] Re: [Paraview-developers] strcpy and other bad actors

In related news...
https://gitlab.kitware.com/vtk/vtk/merge_requests/2675

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

On Mon, Apr 10, 2017 at 11:36 AM, Moreland, Kenneth <kmorel at sandia.gov<mailto:kmorel at sandia.gov>> wrote:
If you are worried about malicious code, I would be even more worried about the use of sprintf. Like strcpy there is no check that the target buffer is not overrun, and it is much harder to predict how large of a buffer you will need to begin with. Plus, there are multiple points in the ParaView interface that allow users to pass format descriptors to sprintf from the GUI or a script. This could definitely be a target for malicious code. We could (and probably should) protected these by using snprintf, but in the cases where users pass in their own format descriptors they could do all sorts of weird stuff like read data off the stack.

-Ken

-----Original Message-----
From: Paraview-developers [mailto:paraview-developers-bounces at paraview.org<mailto:paraview-developers-bounces at paraview.org>] On Behalf Of Ben Boeckel
Sent: Monday, April 10, 2017 7:48 AM
To: Scott, W Alan <wascott at sandia.gov<mailto:wascott at sandia.gov>>
Cc: paraview-developers at paraview.org<mailto:paraview-developers at paraview.org>
Subject: [EXTERNAL] Re: [Paraview-developers] strcpy and other bad actors

On Fri, Apr 07, 2017 at 20:41:52 +0000, Scott, W Alan wrote:
> It made me start to wonder - do we care about ParaView (which of
> course runs in user space).  I just looked, and there are about 1800
> uses of strcpy in ParaView.  Is that an issue?

As with many thing, it depends :) . I wouldn't object to moving to at least `strncpy`, but I suspect that just switching over to `std::string` would just be easier in the long run (since even `strncpy` has buffer calculations which can be done improperly). That may require some reworking around each change though, so is not likely scriptable.

--Ben
_______________________________________________
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/20170410/c5360d8d/attachment.html>

From ben.boeckel at kitware.com  Mon Apr 10 13:24:46 2017
From: ben.boeckel at kitware.com (Ben Boeckel)
Date: Mon, 10 Apr 2017 13:24:46 -0400
Subject: [Paraview-developers] strcpy and other bad actors
In-Reply-To: <7890573b66954d2d80225f639876bc10@ES08AMSNLNT.srn.sandia.gov>
References: <20170410134820.GA12500@megas.kitware.com>
 <7890573b66954d2d80225f639876bc10@ES08AMSNLNT.srn.sandia.gov>
Message-ID: <20170410172446.GB8976@megas.kitware.com>

On Mon, Apr 10, 2017 at 15:36:01 +0000, Moreland, Kenneth wrote:
> If you are worried about malicious code, I would be even more worried
> about the use of sprintf. Like strcpy there is no check that the
> target buffer is not overrun, and it is much harder to predict how
> large of a buffer you will need to begin with. Plus, there are
> multiple points in the ParaView interface that allow users to pass
> format descriptors to sprintf from the GUI or a script. This could
> definitely be a target for malicious code. We could (and probably
> should) protected these by using snprintf, but in the cases where
> users pass in their own format descriptors they could do all sorts of
> weird stuff like read data off the stack.

Really, I guess we should look hard at any code which includes `cstdlib`
or `cstring` :) .

--Ben

From ben.boeckel at kitware.com  Mon Apr 10 17:01:47 2017
From: ben.boeckel at kitware.com (Ben Boeckel)
Date: Mon, 10 Apr 2017 17:01:47 -0400
Subject: [Paraview-developers] H5py in paraview python
In-Reply-To: <20170403123815.GB30932@megas.kitware.com>
References: <CAAyVbOD8OWSLzQEquRUFpyZS0vP-LEvy8c+rnbdN50QbPQiAYg@mail.gmail.com>
 <CADHSJjAMZdeL3GescDmk+fuJohQJmbSxpSwF2oZJ1KPFKn5iZQ@mail.gmail.com>
 <CAAyVbOAt7pUje2_TkMiL5rjjHOCHEkhr2D2-E7Gm32VskQht4A@mail.gmail.com>
 <20170403123815.GB30932@megas.kitware.com>
Message-ID: <20170410210147.GA18612@megas.kitware.com>

On Mon, Apr 03, 2017 at 08:38:15 -0400, Ben Boeckel wrote:
> > We have been trying to include h5py in a binary windows install of
> > Paraview and are having quite some troubles.
> 
> I'll try and take a stab at getting it into the superbuild this week.

Here's the current status of this MR which adds h5py to the packages:

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

First, it appears that h5py doesn't work with HDF5 1.8.13, so I tried
updating HDF5 to 1.8.18. Unfortunately, *lots* of things changed in that
period and now `H5_BUILT_AS_DYNAMIC_LIB` is required to use it on
Windows as a shared library. Silo and netcdf are patched on that branch
to handle it. However, VTK cannot. I have a WIP branch here:

    https://gitlab.kitware.com/vtk/vtk/merge_requests/2678

but Xdmf3 stands in the way there since it needs updated to do the same
logic (rather, to use `vtk_hdf5.h` which handles this instead of trying
to use `hdf5.h` on its own), but that's a longer process. It also looks
like VisItBridge has issues with the new Silo update as well, but that
is easier.

You can use that branch with a ParaView patched with the linked VTK MR
if you can disable XDMF3 in your local binaries (our binaries enable it,
so I can't merge it yet). Alternatively, you can hack Xdmf3 to include
`vtk_hdf5.h` anywhere it includes `H5public.h` or `hdf5.h` directly
instead. VisItBridge should have an update soonish, but may also be
disabled as well.

--Ben

From thomasblome at startmail.com  Tue Apr 11 04:42:33 2017
From: thomasblome at startmail.com (thomasblome at startmail.com)
Date: Tue, 11 Apr 2017 10:42:33 +0200
Subject: [Paraview-developers] Spreadsheet View
In-Reply-To: <CAMaOp+HNjoxmLoL85WkieGA6oH6PG+g=REC=i470GJLJsU0cVA@mail.gmail.com>
References: <bac69c41dbfafd4216e03047402eaf27.startmail@www.startmail.com>
 <CAMaOp+HNjoxmLoL85WkieGA6oH6PG+g=REC=i470GJLJsU0cVA@mail.gmail.com>
Message-ID: <aaaeef8ecf3032c5bd3d7df0cdbe6218.startmail@www.startmail.com>

Hi Andy,

I have tried either way:
1.) just clicking on the "input" icon and then opening a spreadsheet 
view, or
2.) additionaly clicking on the small icon to the left of the "input" 
filter, that is, extracting the Catalyst output and afterwards opening 
the spreadsheet view (here selecting both, "input" or "Extract: input", 
from the dropdown menu)

I shall note that when selecting the "input" filter in the pipeline 
browser as the active module, the information panel displays the 
correct number of points and corresponding bounds. However, if 
"Extract: input" is being activated instead, the status of these items 
becomes "NA".

Also, I ran the CxxFullExample and tried to use the spreadsheet view 
during the simulation run, but the very same error message appeared.

Best,
Thomas




?
Am Montag, 10. April 2017 17:59 schrieb Andy Bauer 
<andy.bauer at kitware.com>:
?
> Hi Thomas,
> ?
> Are you selecting the filter in the Catalyst pipeline or have you 
> already extracted the Catalyst output to the pvserver to look at in 
> the spreadsheet view? The meta-information will be available when you 
> highlight the items in the either the Catalyst pipeline or pvserver 
> pipeline but the full data is not automatically shared with the 
> pvserver (and thus will not be in the pvserver pipeline) since it may 
> be quite large.
> ?
> I just tried doing this with ParaView master and it worked so it's 
> possible that this didn't work with PV 5.1 but has been fixed.
> ?
> Cheers,
> Andy
> ?
> ?
> On Mon, Apr 10, 2017 at 11:40 AM, <thomasblome at startmail.com> wrote:
>> Hi,
>> 
>> I would like to display the coordinates in the paraview spreadsheet 
>> view which were generated in my simulation.
>> After I have established a Catalyst Live connection I select the 
>> input item in the "Pipeline Browser"-view in Paraview.
>> In the information panel below it says the number of points equals 
>> 21 and the bounds (i.e. x,y,z ranges) are displayed correctly, too.
>> However, when I open up another tab and select "Spreadsheet View" to 
>> take a look at the actual coordinates, I get an error message 
>> saying:
>> 
>> ERROR: In 
>> C:\Kitware\ParaView-v5.1.0\VTK\Common\ExecutionModel\vtkExecutive.cxx, 
>> line 784
>> vtkPVCompositeDataPipeline (000000001377FA10): Algorithm 
>> vtkPVExtractSelection(0000000009DCE6D0) returned failure for 
>> request: vtkInformation (0000000014A42BE0)
>> ? Debug: Off
>> ? Modified Time: 299127
>> ? Reference Count: 1
>> ? Registered Events: (none)
>> ? Request: REQUEST_DATA_OBJECT
>> ? ALGORITHM_AFTER_FORWARD: 1
>> ? FORWARD_DIRECTION: 0
>> ? FROM_OUTPUT_PORT: 0
>> 
>> Does anybody know how to solve this? (I'm using Paraview 5.1.0)
>> 
>> 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/20170411/9972974b/attachment-0001.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/20170411/9972974b/attachment-0001.key>

From sur.chiranjib at gmail.com  Tue Apr 11 06:45:52 2017
From: sur.chiranjib at gmail.com (Chiranjib Sur)
Date: Tue, 11 Apr 2017 16:15:52 +0530
Subject: [Paraview-developers] accelerate ParaView graphics rendering speed
Message-ID: <CAJk8dSCDsrgdeaNtG96px0P6jHx9Jpi8JLJLh5hEFz9GApa5jA@mail.gmail.com>

Hi,
Can anyone tell me what are the settings I need to use to execute ParaView
using accelerated graphics?

I have build ParaView in Linux and the runtime says (OpenGL driver is
enabled)

[image: Inline image 1]

I observe that the application takes significant amount of time while
loading large files (~5 GB).

Is there any settings I need to configure for accelerated rendering?

Thanks in advance!

Chiranjib
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20170411/1a540b5e/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 9381 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20170411/1a540b5e/attachment.png>

From jfavre at cscs.ch  Tue Apr 11 08:19:31 2017
From: jfavre at cscs.ch (Favre  Jean)
Date: Tue, 11 Apr 2017 12:19:31 +0000
Subject: [Paraview-developers] OSPRay high memory cost
Message-ID: <0EB9B6375711A04B820E6B6F5CCA9F684383FF52@MBX211.d.ethz.ch>

Hello folks

I am displaying particle datasets in the range of 0.3-3 billion particles

Taking one dataset of 368,135,844 particles loaded as a PolyData with a single cell and a Poly-Vertex, with the default Point Rendering representation, the Unix "top" command shows that ParaView uses 13.8GB of memory. Expensive, but fair - I suppose. (No scalar attached, just coordinates).

Switching on to OSPRay Point rendering, I get into massive swapping, and when the dust settles, I get interactive rendering, and ParaView uses 43.5 GB of RAM. That's about 30GB for 368M particles.

Is this a fair memory consumption?

ospray-1.2.1.x86_64.linux
embree-2.15.0.x86_64.linux
ParaView master April 10, 2017

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

From aron.helser at kitware.com  Tue Apr 11 10:14:57 2017
From: aron.helser at kitware.com (Aron Helser)
Date: Tue, 11 Apr 2017 10:14:57 -0400
Subject: [Paraview-developers] accelerate ParaView graphics rendering
	speed
In-Reply-To: <CAJk8dSCDsrgdeaNtG96px0P6jHx9Jpi8JLJLh5hEFz9GApa5jA@mail.gmail.com>
References: <CAJk8dSCDsrgdeaNtG96px0P6jHx9Jpi8JLJLh5hEFz9GApa5jA@mail.gmail.com>
Message-ID: <CAF2skS4Um2LX3pLwgW5r8Db6UhnWjHJeCJM1TW=erJo-r7WYTg@mail.gmail.com>

Hi Chiranjib,
The 'legacy rendering backend' is referring to OpenGL 1.X support, which is
still hardware accelerated. However, you will probably get better
performance with the OpenGL 2 backend, which became the default in ParaView
5.2+. Can you upgrade?

On Linux, you also may have to take some extra steps to install graphics
drivers appropriate to your graphics card. If you can install those drivers
and confirm they are working, ParaView will use them automatically.

Loading time for a large file, 5 Gb, is determined largely by the speed of
the disk it is stored on. If you want to speed that up, have you tried an
SSD?
Hope this helps,
Aron

On Tue, Apr 11, 2017 at 6:45 AM, Chiranjib Sur <sur.chiranjib at gmail.com>
wrote:

> Hi,
> Can anyone tell me what are the settings I need to use to execute ParaView
> using accelerated graphics?
>
> I have build ParaView in Linux and the runtime says (OpenGL driver is
> enabled)
>
> [image: Inline image 1]
>
> I observe that the application takes significant amount of time while
> loading large files (~5 GB).
>
> Is there any settings I need to configure for accelerated rendering?
>
> Thanks 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/20170411/c788c7a4/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 9381 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20170411/c788c7a4/attachment-0001.png>

From sur.chiranjib at gmail.com  Tue Apr 11 10:31:52 2017
From: sur.chiranjib at gmail.com (Chiranjib Sur)
Date: Tue, 11 Apr 2017 20:01:52 +0530
Subject: [Paraview-developers] accelerate ParaView graphics rendering
	speed
In-Reply-To: <CAF2skS4Um2LX3pLwgW5r8Db6UhnWjHJeCJM1TW=erJo-r7WYTg@mail.gmail.com>
References: <CAJk8dSCDsrgdeaNtG96px0P6jHx9Jpi8JLJLh5hEFz9GApa5jA@mail.gmail.com>
 <CAF2skS4Um2LX3pLwgW5r8Db6UhnWjHJeCJM1TW=erJo-r7WYTg@mail.gmail.com>
Message-ID: <CAJk8dSDaWGAn1KQ+1Tvwmq-V4zYf-FdKydQgAq584qH9qtJ_QA@mail.gmail.com>

Hi Aron,
Ofcourse, this helps!

I am trying to compile PV5.2 with the OSPray module (dependent on Mesa
libraries) and I am learning while I struggle to make it work.

No my HDD is not a SSD but it's a NFS mounted drive. I am not so bothered
about the I/O speed at this moment, but I sincerely hope that upgrading to
a newer version of PV will accelerate the rendering.

BTW, I have asked this question before in the forum. Is there any
implementation in PV in newer version which taken care some Qt
functionality using a background thread without making the GUI frozen. What
I mean, while I add some functionality to some button and press it to do
some operation, it always runs on the foreground and at that time
(operation is in progress), I can't use other PV functionalities. Has
anything changed in the newer version of PV?

Thanks again.
Kind regards,
Chiranjib



On Tue, Apr 11, 2017 at 7:44 PM, Aron Helser <aron.helser at kitware.com>
wrote:

> Hi Chiranjib,
> The 'legacy rendering backend' is referring to OpenGL 1.X support, which
> is still hardware accelerated. However, you will probably get better
> performance with the OpenGL 2 backend, which became the default in ParaView
> 5.2+. Can you upgrade?
>
> On Linux, you also may have to take some extra steps to install graphics
> drivers appropriate to your graphics card. If you can install those drivers
> and confirm they are working, ParaView will use them automatically.
>
> Loading time for a large file, 5 Gb, is determined largely by the speed of
> the disk it is stored on. If you want to speed that up, have you tried an
> SSD?
> Hope this helps,
> Aron
>
> On Tue, Apr 11, 2017 at 6:45 AM, Chiranjib Sur <sur.chiranjib at gmail.com>
> wrote:
>
>> Hi,
>> Can anyone tell me what are the settings I need to use to execute
>> ParaView using accelerated graphics?
>>
>> I have build ParaView in Linux and the runtime says (OpenGL driver is
>> enabled)
>>
>> [image: Inline image 1]
>>
>> I observe that the application takes significant amount of time while
>> loading large files (~5 GB).
>>
>> Is there any settings I need to configure for accelerated rendering?
>>
>> Thanks 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/20170411/18410cc1/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 9381 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20170411/18410cc1/attachment.png>

From dave.demarle at kitware.com  Tue Apr 11 10:45:18 2017
From: dave.demarle at kitware.com (David E DeMarle)
Date: Tue, 11 Apr 2017 10:45:18 -0400
Subject: [Paraview-developers] accelerate ParaView graphics rendering
	speed
In-Reply-To: <CAJk8dSDaWGAn1KQ+1Tvwmq-V4zYf-FdKydQgAq584qH9qtJ_QA@mail.gmail.com>
References: <CAJk8dSCDsrgdeaNtG96px0P6jHx9Jpi8JLJLh5hEFz9GApa5jA@mail.gmail.com>
 <CAF2skS4Um2LX3pLwgW5r8Db6UhnWjHJeCJM1TW=erJo-r7WYTg@mail.gmail.com>
 <CAJk8dSDaWGAn1KQ+1Tvwmq-V4zYf-FdKydQgAq584qH9qtJ_QA@mail.gmail.com>
Message-ID: <CANjZAi_Di9BcODYPOrB9tobxJnCGMwC6hT_JdwY8eJnTETzW+A@mail.gmail.com>

On Tue, Apr 11, 2017 at 10:31 AM, Chiranjib Sur <sur.chiranjib at gmail.com>
wrote:

> OSPray module (dependent on Mesa libraries)


OSPRay does not depend on Mesa and it works with GL1 or GL2 backend.



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

From sur.chiranjib at gmail.com  Tue Apr 11 10:48:05 2017
From: sur.chiranjib at gmail.com (Chiranjib Sur)
Date: Tue, 11 Apr 2017 20:18:05 +0530
Subject: [Paraview-developers] accelerate ParaView graphics rendering
	speed
In-Reply-To: <CANjZAi_Di9BcODYPOrB9tobxJnCGMwC6hT_JdwY8eJnTETzW+A@mail.gmail.com>
References: <CAJk8dSCDsrgdeaNtG96px0P6jHx9Jpi8JLJLh5hEFz9GApa5jA@mail.gmail.com>
 <CAF2skS4Um2LX3pLwgW5r8Db6UhnWjHJeCJM1TW=erJo-r7WYTg@mail.gmail.com>
 <CAJk8dSDaWGAn1KQ+1Tvwmq-V4zYf-FdKydQgAq584qH9qtJ_QA@mail.gmail.com>
 <CANjZAi_Di9BcODYPOrB9tobxJnCGMwC6hT_JdwY8eJnTETzW+A@mail.gmail.com>
Message-ID: <CAJk8dSAy8a5mnpnZaR7qeuYs=mUSNZR5oE0DXPqv+zytjO9gxA@mail.gmail.com>

This is great news. I was unaware of this. Hope this make life little
simpler with the build.

Thanks and regards,
Chiranjib

Using handheld, sorry for the typos, if any.

On 11-Apr-2017 8:15 PM, "David E DeMarle" <dave.demarle at kitware.com> wrote:

>
> On Tue, Apr 11, 2017 at 10:31 AM, Chiranjib Sur <sur.chiranjib at gmail.com>
> wrote:
>
>> OSPray module (dependent on Mesa libraries)
>
>
> OSPRay does not depend on Mesa and it works with GL1 or GL2 backend.
>
>
>
> David E DeMarle
> Kitware, Inc.
> R&D Engineer
> 21 Corporate Drive
> Clifton Park, NY 12065-8662
> Phone: 518-881-4909
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20170411/1313b735/attachment-0001.html>

From andy.bauer at kitware.com  Wed Apr 12 14:36:02 2017
From: andy.bauer at kitware.com (Andy Bauer)
Date: Wed, 12 Apr 2017 14:36:02 -0400
Subject: [Paraview-developers] Spreadsheet View
In-Reply-To: <aaaeef8ecf3032c5bd3d7df0cdbe6218.startmail@www.startmail.com>
References: <bac69c41dbfafd4216e03047402eaf27.startmail@www.startmail.com>
 <CAMaOp+HNjoxmLoL85WkieGA6oH6PG+g=REC=i470GJLJsU0cVA@mail.gmail.com>
 <aaaeef8ecf3032c5bd3d7df0cdbe6218.startmail@www.startmail.com>
Message-ID: <CAMaOp+G_JLjAHOkHQ3PGStRWmQdCL9TMESDmuZfMxgJBGmXmRA@mail.gmail.com>

Hi Thomas,

I suspect this is an issue that has since been fixed. Can you try the
attached script with the CxxFullExample from ParaView 5.3? It works for me
if I run that and connect the PV 5.3 GUI to the simulation, extract the
slice and then view the "Extract: Slice1" filter source in the GUI's
spreadsheetview.

Best,
Andy

On Tue, Apr 11, 2017 at 4:42 AM, <thomasblome at startmail.com> wrote:

> Hi Andy,
>
> I have tried either way:
> 1.) just clicking on the "input" icon and then opening a spreadsheet view,
> or
> 2.) additionaly clicking on the small icon to the left of the "input"
> filter, that is, extracting the Catalyst output and afterwards opening the
> spreadsheet view (here selecting both, "input" or "Extract: input", from
> the dropdown menu)
>
> I shall note that when selecting the "input" filter in the pipeline
> browser as the active module, the information panel displays the correct
> number of points and corresponding bounds. However, if "Extract: input" is
> being activated instead, the status of these items becomes "NA".
>
> Also, I ran the CxxFullExample and tried to use the spreadsheet view
> during the simulation run, but the very same error message appeared.
>
> Best,
> Thomas
>
>
>
>
>
> Am Montag, 10. April 2017 17:59 schrieb Andy Bauer <andy.bauer at kitware.com>:
>
>
>
> Hi Thomas,
>
> Are you selecting the filter in the Catalyst pipeline or have you already
> extracted the Catalyst output to the pvserver to look at in the spreadsheet
> view? The meta-information will be available when you highlight the items
> in the either the Catalyst pipeline or pvserver pipeline but the full data
> is not automatically shared with the pvserver (and thus will not be in the
> pvserver pipeline) since it may be quite large.
>
> I just tried doing this with ParaView master and it worked so it's
> possible that this didn't work with PV 5.1 but has been fixed.
>
> Cheers,
> Andy
>
>
>
> On Mon, Apr 10, 2017 at 11:40 AM, <thomasblome at startmail.com> wrote:
>
> Hi,
>
> I would like to display the coordinates in the paraview spreadsheet view
> which were generated in my simulation.
> After I have established a Catalyst Live connection I select the input
> item in the "Pipeline Browser"-view in Paraview.
> In the information panel below it says the number of points equals 21 and
> the bounds (i.e. x,y,z ranges) are displayed correctly, too.
> However, when I open up another tab and select "Spreadsheet View" to take
> a look at the actual coordinates, I get an error message saying:
>
> ERROR: In C:\Kitware\ParaView-v5.1.0\VTK\Common\ExecutionModel\vtkExecutive.cxx,
> line 784
> vtkPVCompositeDataPipeline (000000001377FA10): Algorithm
> vtkPVExtractSelection(0000000009DCE6D0) returned failure for request:
> vtkInformation (0000000014A42BE0)
>   Debug: Off
>   Modified Time: 299127
>   Reference Count: 1
>   Registered Events: (none)
>   Request: REQUEST_DATA_OBJECT
>   ALGORITHM_AFTER_FORWARD: 1
>   FORWARD_DIRECTION: 0
>   FROM_OUTPUT_PORT: 0
>
> Does anybody know how to solve this? (I'm using Paraview 5.1.0)
>
> 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/20170412/393c4d54/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: catlive.py
Type: text/x-python
Size: 4156 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20170412/393c4d54/attachment.py>

From dave.demarle at kitware.com  Thu Apr 13 09:21:21 2017
From: dave.demarle at kitware.com (David E DeMarle)
Date: Thu, 13 Apr 2017 09:21:21 -0400
Subject: [Paraview-developers] OSPRay high memory cost
In-Reply-To: <0EB9B6375711A04B820E6B6F5CCA9F684383FF52@MBX211.d.ethz.ch>
References: <0EB9B6375711A04B820E6B6F5CCA9F684383FF52@MBX211.d.ethz.ch>
Message-ID: <CANjZAi_5R2Pbhv3tq1CuVt4fGEx5BgvWVMzMp1K=0ztLTOvGGQ@mail.gmail.com>

Memory use is definitely higher than I would like it to be right now. Paul
Navratil and I have an IPCC going with Intel were we are looking at this
and related issues. Little progress so far yet I am afraid in identifying
what fat we can trim.

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

On Tue, Apr 11, 2017 at 8:19 AM, Favre Jean <jfavre at cscs.ch> wrote:

> Hello folks
>
> I am displaying particle datasets in the range of 0.3-3 billion particles
>
> Taking one dataset of 368,135,844 particles loaded as a PolyData with a
> single cell and a Poly-Vertex, with the default Point Rendering
> representation, the Unix "top" command shows that ParaView uses 13.8GB of
> memory. Expensive, but fair - I suppose. (No scalar attached, just
> coordinates).
>
> Switching on to OSPRay Point rendering, I get into massive swapping, and
> when the dust settles, I get interactive rendering, and ParaView uses 43.5
> GB of RAM. That's about 30GB for 368M particles.
>
> Is this a fair memory consumption?
>
> ospray-1.2.1.x86_64.linux
> embree-2.15.0.x86_64.linux
> ParaView master April 10, 2017
>
> -----------------
> Jean/CSCS
>
> _______________________________________________
> 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/20170413/a7ab9af4/attachment.html>

From thomasblome at startmail.com  Thu Apr 13 11:57:21 2017
From: thomasblome at startmail.com (thomasblome at startmail.com)
Date: Thu, 13 Apr 2017 17:57:21 +0200
Subject: [Paraview-developers] Spreadsheet View
In-Reply-To: <CAMaOp+G_JLjAHOkHQ3PGStRWmQdCL9TMESDmuZfMxgJBGmXmRA@mail.gmail.com>
References: <bac69c41dbfafd4216e03047402eaf27.startmail@www.startmail.com>
 <CAMaOp+HNjoxmLoL85WkieGA6oH6PG+g=REC=i470GJLJsU0cVA@mail.gmail.com>
 <aaaeef8ecf3032c5bd3d7df0cdbe6218.startmail@www.startmail.com>
 <CAMaOp+G_JLjAHOkHQ3PGStRWmQdCL9TMESDmuZfMxgJBGmXmRA@mail.gmail.com>
Message-ID: <8184315598abfb903d507462c2401642.startmail@www.startmail.com>

Hi Andy,

I did a mistake, the spreadsheet view in the CxxFullExample works fine 
(also in PV 5.1). I just forgot to extract the Catalyst output at this 
point.

I'm sorry for any inconvenience.

Thanks,
Thomas


?
Am Mittwoch, 12. April 2017 20:36 schrieb Andy Bauer 
<andy.bauer at kitware.com>:
?
> Hi Thomas,
> ?
> I suspect this is an issue that has since been fixed. Can you try the 
> attached script with the CxxFullExample from ParaView 5.3? It works 
> for me if I run that and connect the PV 5.3 GUI to the simulation, 
> extract the slice and then view the "Extract: Slice1" filter source 
> in the GUI's spreadsheetview.
> ?
> Best,
> Andy
> ?
> On Tue, Apr 11, 2017 at 4:42 AM, <thomasblome at startmail.com> wrote:
>> Hi Andy,
>> 
>> I have tried either way:
>> 1.) just clicking on the "input" icon and then opening a spreadsheet 
>> view, or
>> 2.) additionaly clicking on the small icon to the left of the 
>> "input" filter, that is, extracting the Catalyst output and 
>> afterwards opening the spreadsheet view (here selecting both, 
>> "input" or "Extract: input", from the dropdown menu)
>> 
>> I shall note that when selecting the "input" filter in the pipeline 
>> browser as the active module, the information panel displays the 
>> correct number of points and corresponding bounds. However, if 
>> "Extract: input" is being activated instead, the status of these 
>> items becomes "NA".
>> 
>> Also, I ran the CxxFullExample and tried to use the spreadsheet view 
>> during the simulation run, but the very same error message appeared.
>> 
>> Best,
>> Thomas
>> 
>> 
>> 
>> ?
>> Am Montag, 10. April 2017 17:59 schrieb Andy Bauer <andy.bauer at kitware.com>:
>> ?
>>> Hi Thomas,
>>> ?
>>> Are you selecting the filter in the Catalyst pipeline or have you 
>>> already extracted the Catalyst output to the pvserver to look at in 
>>> the spreadsheet view? The meta-information will be available when 
>>> you highlight the items in the either the Catalyst pipeline or 
>>> pvserver pipeline but the full data is not automatically shared 
>>> with the pvserver (and thus will not be in the pvserver pipeline) 
>>> since it may be quite large.
>>> ?
>>> I just tried doing this with ParaView master and it worked so it's 
>>> possible that this didn't work with PV 5.1 but has been fixed.
>>> ?
>>> Cheers,
>>> Andy
>>> ?
>>> ?
>>> On Mon, Apr 10, 2017 at 11:40 AM, <thomasblome at startmail.com> 
>>> wrote:
>>>> Hi,
>>>> 
>>>> I would like to display the coordinates in the paraview 
>>>> spreadsheet view which were generated in my simulation.
>>>> After I have established a Catalyst Live connection I select the 
>>>> input item in the "Pipeline Browser"-view in Paraview.
>>>> In the information panel below it says the number of points equals 
>>>> 21 and the bounds (i.e. x,y,z ranges) are displayed correctly, 
>>>> too.
>>>> However, when I open up another tab and select "Spreadsheet View" 
>>>> to take a look at the actual coordinates, I get an error message 
>>>> saying:
>>>> 
>>>> ERROR: In 
>>>> C:\Kitware\ParaView-v5.1.0\VTK\Common\ExecutionModel\vtkExecutive.cxx, 
>>>> line 784
>>>> vtkPVCompositeDataPipeline (000000001377FA10): Algorithm 
>>>> vtkPVExtractSelection(0000000009DCE6D0) returned failure for 
>>>> request: vtkInformation (0000000014A42BE0)
>>>> ? Debug: Off
>>>> ? Modified Time: 299127
>>>> ? Reference Count: 1
>>>> ? Registered Events: (none)
>>>> ? Request: REQUEST_DATA_OBJECT
>>>> ? ALGORITHM_AFTER_FORWARD: 1
>>>> ? FORWARD_DIRECTION: 0
>>>> ? FROM_OUTPUT_PORT: 0
>>>> 
>>>> Does anybody know how to solve this? (I'm using Paraview 5.1.0)
>>>> 
>>>> 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/20170413/32080e59/attachment-0001.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/20170413/32080e59/attachment-0001.key>

From andy.bauer at kitware.com  Thu Apr 13 12:46:27 2017
From: andy.bauer at kitware.com (Andy Bauer)
Date: Thu, 13 Apr 2017 12:46:27 -0400
Subject: [Paraview-developers] Spreadsheet View
In-Reply-To: <8184315598abfb903d507462c2401642.startmail@www.startmail.com>
References: <bac69c41dbfafd4216e03047402eaf27.startmail@www.startmail.com>
 <CAMaOp+HNjoxmLoL85WkieGA6oH6PG+g=REC=i470GJLJsU0cVA@mail.gmail.com>
 <aaaeef8ecf3032c5bd3d7df0cdbe6218.startmail@www.startmail.com>
 <CAMaOp+G_JLjAHOkHQ3PGStRWmQdCL9TMESDmuZfMxgJBGmXmRA@mail.gmail.com>
 <8184315598abfb903d507462c2401642.startmail@www.startmail.com>
Message-ID: <CAMaOp+F9K5xjLLLnEb9M5N184pJ0gweCNjqXBKJseskOozE+4Q@mail.gmail.com>

Hi Thomas,

Glad you have it working now.

Best,
Andy

On Thu, Apr 13, 2017 at 11:57 AM, <thomasblome at startmail.com> wrote:

> Hi Andy,
>
> I did a mistake, the spreadsheet view in the CxxFullExample works fine
> (also in PV 5.1). I just forgot to extract the Catalyst output at this
> point.
>
> I'm sorry for any inconvenience.
>
> Thanks,
> Thomas
>
>
>
> Am Mittwoch, 12. April 2017 20:36 schrieb Andy Bauer <
> andy.bauer at kitware.com>:
>
>
> Hi Thomas,
>
> I suspect this is an issue that has since been fixed. Can you try the
> attached script with the CxxFullExample from ParaView 5.3? It works for me
> if I run that and connect the PV 5.3 GUI to the simulation, extract the
> slice and then view the "Extract: Slice1" filter source in the GUI's
> spreadsheetview.
>
> Best,
> Andy
>
> On Tue, Apr 11, 2017 at 4:42 AM, <thomasblome at startmail.com> wrote:
>
> Hi Andy,
>
> I have tried either way:
> 1.) just clicking on the "input" icon and then opening a spreadsheet view,
> or
> 2.) additionaly clicking on the small icon to the left of the "input"
> filter, that is, extracting the Catalyst output and afterwards opening the
> spreadsheet view (here selecting both, "input" or "Extract: input", from
> the dropdown menu)
>
> I shall note that when selecting the "input" filter in the pipeline
> browser as the active module, the information panel displays the correct
> number of points and corresponding bounds. However, if "Extract: input" is
> being activated instead, the status of these items becomes "NA".
>
> Also, I ran the CxxFullExample and tried to use the spreadsheet view
> during the simulation run, but the very same error message appeared.
>
> Best,
> Thomas
>
>
>
>
>
> Am Montag, 10. April 2017 17:59 schrieb Andy Bauer <andy.bauer at kitware.com>:
>
>
>
> Hi Thomas,
>
> Are you selecting the filter in the Catalyst pipeline or have you already
> extracted the Catalyst output to the pvserver to look at in the spreadsheet
> view? The meta-information will be available when you highlight the items
> in the either the Catalyst pipeline or pvserver pipeline but the full data
> is not automatically shared with the pvserver (and thus will not be in the
> pvserver pipeline) since it may be quite large.
>
> I just tried doing this with ParaView master and it worked so it's
> possible that this didn't work with PV 5.1 but has been fixed.
>
> Cheers,
> Andy
>
>
>
> On Mon, Apr 10, 2017 at 11:40 AM, <thomasblome at startmail.com> wrote:
>
> Hi,
>
> I would like to display the coordinates in the paraview spreadsheet view
> which were generated in my simulation.
> After I have established a Catalyst Live connection I select the input
> item in the "Pipeline Browser"-view in Paraview.
> In the information panel below it says the number of points equals 21 and
> the bounds (i.e. x,y,z ranges) are displayed correctly, too.
> However, when I open up another tab and select "Spreadsheet View" to take
> a look at the actual coordinates, I get an error message saying:
>
> ERROR: In C:\Kitware\ParaView-v5.1.0\VTK\Common\ExecutionModel\vtkExecutive.cxx,
> line 784
> vtkPVCompositeDataPipeline (000000001377FA10): Algorithm
> vtkPVExtractSelection(0000000009DCE6D0) returned failure for request:
> vtkInformation (0000000014A42BE0)
>   Debug: Off
>   Modified Time: 299127
>   Reference Count: 1
>   Registered Events: (none)
>   Request: REQUEST_DATA_OBJECT
>   ALGORITHM_AFTER_FORWARD: 1
>   FORWARD_DIRECTION: 0
>   FROM_OUTPUT_PORT: 0
>
> Does anybody know how to solve this? (I'm using Paraview 5.1.0)
>
> 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/20170413/19e0d1b6/attachment.html>

From sumeet.kumar507 at gmail.com  Thu Apr 13 23:34:41 2017
From: sumeet.kumar507 at gmail.com (sumeet kumar)
Date: Thu, 13 Apr 2017 20:34:41 -0700
Subject: [Paraview-developers] Rendering in Paraview using python
Message-ID: <CADWn_Z7uNsF0Od0ZG1eyCwdBABBDr_UQpXMN9dQhjNt+Q-caqg@mail.gmail.com>

Hey,

I have a reader plugin integrated with paraview that works perfectly fine.
I could use the same plugin to trace an "equivalent python code" for any
visualization example.  The generated python code can be run again on
paraview gui.
BUT, when i try to follow the same python command in python externally like
pvpython. I get the following error.

>>> from paraview.simple import *
updating active connection None
paraview version 5.2.0-RC1
updating active connection Connection (builtin:) [1]
updating active connection Connection (builtin:) [1]
>>> beam_Axial_Loadh5feioutput = pvESSI(FileName="/home/sumeet/Desktop
/Beam_Axial_Load.h5.feioutput")
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
NameError: name 'pvESSI' is not defined

My plugin name is pvESSI. the same line works on paraview GUI mode in
python shell. I tried to look on the Internet and build the plugin inside
the paraview source itself, but the problem remains.

Others have suggested here on link
http://www.paraview.org/pipermail/paraview/2013-October/029428.html, but I
dont understand where to make changes to fix this problem.


Any help would be highly appreciated.

Best Regards
Sumeet
-- 

Sumeet Kumar Sinha
Graduate Student
Phone: (+1)  <%28%2B91%29%209910516219>5306018271
Website : http://www.sumeetksinha.com/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20170413/b0aae2c8/attachment.html>

From rehr at nbi.ku.dk  Fri Apr 14 06:59:12 2017
From: rehr at nbi.ku.dk (Martin Rehr)
Date: Fri, 14 Apr 2017 12:59:12 +0200
Subject: [Paraview-developers] vtkSMDirectoryProxy::List
Message-ID: <56F2A505-B6D0-445F-8C22-5811DA912492@nbi.ku.dk>

Greetings,

I have trouble getting a list of directory entries through the ParaviewWeb Visualizer.

The ParaviewWeb Visualizer utilizes the ParaView source file: 'Web/Python2/paraview/web/protocols.py?

I have isolated the python code causing trouble and made a simple test:

--------------------------------------------------------------
from paraview import simple

pxm = simple.servermanager.ProxyManager()
directory_proxy = pxm.NewProxy('misc', 'ListDirectory?)
directory_proxy.List(path)
file_list = directory_proxy.GetProperty('FileList?)
print "file_list.GetNumberOfElements(): %s" % file_list.GetNumberOfElements()
--------------------------------------------------------------

?file_list' remain empty no matter how many files located in ?path?

I have tracked the problem down to that ?vtkSIDirectoryProxy::Pull'[1] is never called and therefore the 'FileList' and ?DirectoryList? properties of ?vtkSMDirectoryProxy' is never updated.
This can be fixed by modifying vtkSMDirectoryProxy::List[2] to:

--------------------------------------------------------------
bool vtkSMDirectoryProxy::List(const char* dir)
{
  bool result = this->CallDirectoryMethod("OpenDirectory", dir);
  if (result)
  {
    this->UpdatePropertyInformation(this->GetProperty("DirectoryList"));
    this->UpdatePropertyInformation(this->GetProperty("FileList"));
  }
  return result;
}
--------------------------------------------------------------

And changing ?vtkSIDirectoryProxy::ReadXMLProperty?[1]:
--------------------------------------------------------------------------------
if (strcmp(name.c_str(), "FileList") == 0 || strcmp(name.c_str(), "DirectoryList?))
->
if (strcmp(name.c_str(), "FileList") == 0 || strcmp(name.c_str(), "DirectoryList") == 0)
--------------------------------------------------------------------------------

I?m new to the ParaView code-base so I don?t know if this is the correct way to fix the above problem, any comments is appreciated.

The above tests are performed on an Ubuntu 14.04 with kernel 3.13.0-112-generic #159-Ubuntu SMP and the official 5.3 source release (ParaView-v5.3.0.tar.gz) as well as the latest git checkout.

Best Regards,
   Martin Rehr

[1] ParaViewCore/ServerImplementation/Core/vtkSIDirectoryProxy.cxx
[2] ParaViewCore/ServerManager/Default/vtkSMDirectoryProxy.cxx




-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 841 bytes
Desc: Message signed with OpenPGP
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20170414/5142f15d/attachment.sig>

From sebastien.jourdain at kitware.com  Fri Apr 14 09:15:40 2017
From: sebastien.jourdain at kitware.com (Sebastien Jourdain)
Date: Fri, 14 Apr 2017 07:15:40 -0600
Subject: [Paraview-developers] vtkSMDirectoryProxy::List
In-Reply-To: <56F2A505-B6D0-445F-8C22-5811DA912492@nbi.ku.dk>
References: <56F2A505-B6D0-445F-8C22-5811DA912492@nbi.ku.dk>
Message-ID: <CABObKxf35SLYbdmMHS5Zn9OjcJrxxr7s5Zo_0zKvuc0RHrSW_A@mail.gmail.com>

Thanks Martin,

The way we fixed that issue was by adding that line:

https://github.com/Kitware/ParaView/blob/master/Web/Python/paraview/web/protocols.py#L2287

Can you check if that solve the problem on your end?

Seb

On Fri, Apr 14, 2017 at 4:59 AM, Martin Rehr <rehr at nbi.ku.dk> wrote:

> Greetings,
>
> I have trouble getting a list of directory entries through the ParaviewWeb
> Visualizer.
>
> The ParaviewWeb Visualizer utilizes the ParaView source file:
> 'Web/Python2/paraview/web/protocols.py?
>
> I have isolated the python code causing trouble and made a simple test:
>
> --------------------------------------------------------------
> from paraview import simple
>
> pxm = simple.servermanager.ProxyManager()
> directory_proxy = pxm.NewProxy('misc', 'ListDirectory?)
> directory_proxy.List(path)
> file_list = directory_proxy.GetProperty('FileList?)
> print "file_list.GetNumberOfElements(): %s" %
> file_list.GetNumberOfElements()
> --------------------------------------------------------------
>
> ?file_list' remain empty no matter how many files located in ?path?
>
> I have tracked the problem down to that ?vtkSIDirectoryProxy::Pull'[1] is
> never called and therefore the 'FileList' and ?DirectoryList? properties of
> ?vtkSMDirectoryProxy' is never updated.
> This can be fixed by modifying vtkSMDirectoryProxy::List[2] to:
>
> --------------------------------------------------------------
> bool vtkSMDirectoryProxy::List(const char* dir)
> {
>   bool result = this->CallDirectoryMethod("OpenDirectory", dir);
>   if (result)
>   {
>     this->UpdatePropertyInformation(this->GetProperty("DirectoryList"));
>     this->UpdatePropertyInformation(this->GetProperty("FileList"));
>   }
>   return result;
> }
> --------------------------------------------------------------
>
> And changing ?vtkSIDirectoryProxy::ReadXMLProperty?[1]:
> ------------------------------------------------------------
> --------------------
> if (strcmp(name.c_str(), "FileList") == 0 || strcmp(name.c_str(),
> "DirectoryList?))
> ->
> if (strcmp(name.c_str(), "FileList") == 0 || strcmp(name.c_str(),
> "DirectoryList") == 0)
> ------------------------------------------------------------
> --------------------
>
> I?m new to the ParaView code-base so I don?t know if this is the correct
> way to fix the above problem, any comments is appreciated.
>
> The above tests are performed on an Ubuntu 14.04 with kernel
> 3.13.0-112-generic #159-Ubuntu SMP and the official 5.3 source release
> (ParaView-v5.3.0.tar.gz) as well as the latest git checkout.
>
> Best Regards,
>    Martin Rehr
>
> [1] ParaViewCore/ServerImplementation/Core/vtkSIDirectoryProxy.cxx
> [2] ParaViewCore/ServerManager/Default/vtkSMDirectoryProxy.cxx
>
>
>
>
>
> _______________________________________________
> 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/20170414/a51b777a/attachment-0001.html>

From rehr at nbi.ku.dk  Fri Apr 14 09:34:33 2017
From: rehr at nbi.ku.dk (Martin Rehr)
Date: Fri, 14 Apr 2017 15:34:33 +0200
Subject: [Paraview-developers] vtkSMDirectoryProxy::List
In-Reply-To: <CABObKxf35SLYbdmMHS5Zn9OjcJrxxr7s5Zo_0zKvuc0RHrSW_A@mail.gmail.com>
References: <56F2A505-B6D0-445F-8C22-5811DA912492@nbi.ku.dk>
 <CABObKxf35SLYbdmMHS5Zn9OjcJrxxr7s5Zo_0zKvuc0RHrSW_A@mail.gmail.com>
Message-ID: <F428E841-E57A-4B83-B037-18054AD66D46@nbi.ku.dk>

Hej Sebastien,

Thanks, that did the trick, nice and simple :)

/ Martin

> On 14 Apr 2017, at 15.15, Sebastien Jourdain <sebastien.jourdain at kitware.com> wrote:
> 
> Thanks Martin,
> 
> The way we fixed that issue was by adding that line:
> 
> https://github.com/Kitware/ParaView/blob/master/Web/Python/paraview/web/protocols.py#L2287 <https://github.com/Kitware/ParaView/blob/master/Web/Python/paraview/web/protocols.py#L2287>
> 
> Can you check if that solve the problem on your end?
> 
> Seb
> 
> On Fri, Apr 14, 2017 at 4:59 AM, Martin Rehr <rehr at nbi.ku.dk <mailto:rehr at nbi.ku.dk>> wrote:
> Greetings,
> 
> I have trouble getting a list of directory entries through the ParaviewWeb Visualizer.
> 
> The ParaviewWeb Visualizer utilizes the ParaView source file: 'Web/Python2/paraview/web/protocols.py?
> 
> I have isolated the python code causing trouble and made a simple test:
> 
> --------------------------------------------------------------
> from paraview import simple
> 
> pxm = simple.servermanager.ProxyManager()
> directory_proxy = pxm.NewProxy('misc', 'ListDirectory?)
> directory_proxy.List(path)
> file_list = directory_proxy.GetProperty('FileList?)
> print "file_list.GetNumberOfElements(): %s" % file_list.GetNumberOfElements()
> --------------------------------------------------------------
> 
> ?file_list' remain empty no matter how many files located in ?path?
> 
> I have tracked the problem down to that ?vtkSIDirectoryProxy::Pull'[1] is never called and therefore the 'FileList' and ?DirectoryList? properties of ?vtkSMDirectoryProxy' is never updated.
> This can be fixed by modifying vtkSMDirectoryProxy::List[2] to:
> 
> --------------------------------------------------------------
> bool vtkSMDirectoryProxy::List(const char* dir)
> {
>   bool result = this->CallDirectoryMethod("OpenDirectory", dir);
>   if (result)
>   {
>     this->UpdatePropertyInformation(this->GetProperty("DirectoryList"));
>     this->UpdatePropertyInformation(this->GetProperty("FileList"));
>   }
>   return result;
> }
> --------------------------------------------------------------
> 
> And changing ?vtkSIDirectoryProxy::ReadXMLProperty?[1]:
> --------------------------------------------------------------------------------
> if (strcmp(name.c_str(), "FileList") == 0 || strcmp(name.c_str(), "DirectoryList?))
> ->
> if (strcmp(name.c_str(), "FileList") == 0 || strcmp(name.c_str(), "DirectoryList") == 0)
> --------------------------------------------------------------------------------
> 
> I?m new to the ParaView code-base so I don?t know if this is the correct way to fix the above problem, any comments is appreciated.
> 
> The above tests are performed on an Ubuntu 14.04 with kernel 3.13.0-112-generic #159-Ubuntu SMP and the official 5.3 source release (ParaView-v5.3.0.tar.gz) as well as the latest git checkout.
> 
> Best Regards,
>    Martin Rehr
> 
> [1] ParaViewCore/ServerImplementation/Core/vtkSIDirectoryProxy.cxx
> [2] ParaViewCore/ServerManager/Default/vtkSMDirectoryProxy.cxx
> 
> 
> 
> 
> 
> _______________________________________________
> Powered by www.kitware.com <http://www.kitware.com/>
> 
> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html <http://www.kitware.com/opensource/opensource.html>
> 
> Search the list archives at: http://markmail.org/search/?q=Paraview-developers <http://markmail.org/search/?q=Paraview-developers>
> 
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview-developers <http://public.kitware.com/mailman/listinfo/paraview-developers>
> 
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20170414/168e5408/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 841 bytes
Desc: Message signed with OpenPGP
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20170414/168e5408/attachment.sig>

From andy.bauer at kitware.com  Fri Apr 14 10:01:51 2017
From: andy.bauer at kitware.com (Andy Bauer)
Date: Fri, 14 Apr 2017 10:01:51 -0400
Subject: [Paraview-developers] Rendering in Paraview using python
In-Reply-To: <CADWn_Z7uNsF0Od0ZG1eyCwdBABBDr_UQpXMN9dQhjNt+Q-caqg@mail.gmail.com>
References: <CADWn_Z7uNsF0Od0ZG1eyCwdBABBDr_UQpXMN9dQhjNt+Q-caqg@mail.gmail.com>
Message-ID: <CAMaOp+GnEoHpBE7C1WGyHJ+yTTWUWv-d4+j58mWrzTkaUc21yw@mail.gmail.com>

Hi,

My guess is that the reader plugin is automatically loaded in the GUI but
not when you run pvpython directly. Look at the LoadPlugin() or
LoadDistributedPlugin() command in pvpython.

Are you setting PV_PLUGIN_PATH or PV_PLUGIN_CONFIG_FILE? Another guess may
be that you're using PV_PLUGIN_PATH and/or PV_PLUGIN_CONFIG_FILE to load
the plugin automatically through the GUI and that isn't being utilized when
running with pvpython. See http://www.paraview.org/Wiki/Plugin_HowTo for
information on that.

Best,
Andy

On Thu, Apr 13, 2017 at 11:34 PM, sumeet kumar <sumeet.kumar507 at gmail.com>
wrote:

> Hey,
>
> I have a reader plugin integrated with paraview that works perfectly fine.
> I could use the same plugin to trace an "equivalent python code" for any
> visualization example.  The generated python code can be run again on
> paraview gui.
> BUT, when i try to follow the same python command in python externally
> like pvpython. I get the following error.
>
> >>> from paraview.simple import *
> updating active connection None
> paraview version 5.2.0-RC1
> updating active connection Connection (builtin:) [1]
> updating active connection Connection (builtin:) [1]
> >>> beam_Axial_Loadh5feioutput = pvESSI(FileName="/home/sumeet/Desktop
> /Beam_Axial_Load.h5.feioutput")
> Traceback (most recent call last):
>   File "<stdin>", line 1, in <module>
> NameError: name 'pvESSI' is not defined
>
> My plugin name is pvESSI. the same line works on paraview GUI mode in
> python shell. I tried to look on the Internet and build the plugin inside
> the paraview source itself, but the problem remains.
>
> Others have suggested here on link http://www.paraview.org/
> pipermail/paraview/2013-October/029428.html, but I dont understand where
> to make changes to fix this problem.
>
>
> Any help would be highly appreciated.
>
> Best Regards
> Sumeet
> --
>
> Sumeet Kumar Sinha
> Graduate Student
> Phone: (+1)  <%28%2B91%29%209910516219>5306018271 <(530)%20601-8271>
> Website : http://www.sumeetksinha.com/
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20170414/91906f11/attachment.html>

From sumeet.kumar507 at gmail.com  Fri Apr 14 11:08:43 2017
From: sumeet.kumar507 at gmail.com (sumeet kumar)
Date: Fri, 14 Apr 2017 08:08:43 -0700
Subject: [Paraview-developers] Rendering in Paraview using python
In-Reply-To: <CAMaOp+GnEoHpBE7C1WGyHJ+yTTWUWv-d4+j58mWrzTkaUc21yw@mail.gmail.com>
References: <CADWn_Z7uNsF0Od0ZG1eyCwdBABBDr_UQpXMN9dQhjNt+Q-caqg@mail.gmail.com>
 <CAMaOp+GnEoHpBE7C1WGyHJ+yTTWUWv-d4+j58mWrzTkaUc21yw@mail.gmail.com>
Message-ID: <CADWn_Z7MfRXZ+23fJq2Ff7JhO57gyBQVxgHGfSHb5bbZeVDojw@mail.gmail.com>

Hi Andy,

LoadPlugin() helps in pvpython. But why does
*from  paraview.simple import * *does not work???

Why I need to externally load my plugin even I build with paraview source.
Also, I don't think, Its a good design to set PV_PLUGIN_PATH  or
PV_PLUGIN_CONFIG_FILE even when the plugin is build with source. The file
"plugin.cmake" should take care all of this.

Thanks
Sumeet

On Fri, Apr 14, 2017 at 7:01 AM, Andy Bauer <andy.bauer at kitware.com> wrote:

> Hi,
>
> My guess is that the reader plugin is automatically loaded in the GUI but
> not when you run pvpython directly. Look at the LoadPlugin() or
> LoadDistributedPlugin() command in pvpython.
>
> Are you setting PV_PLUGIN_PATH or PV_PLUGIN_CONFIG_FILE? Another guess may
> be that you're using PV_PLUGIN_PATH and/or PV_PLUGIN_CONFIG_FILE to load
> the plugin automatically through the GUI and that isn't being utilized when
> running with pvpython. See http://www.paraview.org/Wiki/Plugin_HowTo for
> information on that.
>
> Best,
> Andy
>
> On Thu, Apr 13, 2017 at 11:34 PM, sumeet kumar <sumeet.kumar507 at gmail.com>
> wrote:
>
>> Hey,
>>
>> I have a reader plugin integrated with paraview that works perfectly
>> fine. I could use the same plugin to trace an "equivalent python code" for
>> any visualization example.  The generated python code can be run again on
>> paraview gui.
>> BUT, when i try to follow the same python command in python externally
>> like pvpython. I get the following error.
>>
>> >>> from paraview.simple import *
>> updating active connection None
>> paraview version 5.2.0-RC1
>> updating active connection Connection (builtin:) [1]
>> updating active connection Connection (builtin:) [1]
>> >>> beam_Axial_Loadh5feioutput = pvESSI(FileName="/home/sumeet/Desktop
>> /Beam_Axial_Load.h5.feioutput")
>> Traceback (most recent call last):
>>   File "<stdin>", line 1, in <module>
>> NameError: name 'pvESSI' is not defined
>>
>> My plugin name is pvESSI. the same line works on paraview GUI mode in
>> python shell. I tried to look on the Internet and build the plugin inside
>> the paraview source itself, but the problem remains.
>>
>> Others have suggested here on link http://www.paraview.org/piperm
>> ail/paraview/2013-October/029428.html, but I dont understand where to
>> make changes to fix this problem.
>>
>>
>> Any help would be highly appreciated.
>>
>> Best Regards
>> Sumeet
>> --
>>
>> Sumeet Kumar Sinha
>> Graduate Student
>> Phone: (+1)  <%28%2B91%29%209910516219>5306018271 <(530)%20601-8271>
>> Website : http://www.sumeetksinha.com/
>>
>
>


-- 

Sumeet Kumar Sinha
Graduate Student
Phone: (+1)  <%28%2B91%29%209910516219>5306018271
Website : http://www.sumeetksinha.com/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20170414/ef4612e4/attachment-0001.html>

From andy.bauer at kitware.com  Fri Apr 14 11:15:57 2017
From: andy.bauer at kitware.com (Andy Bauer)
Date: Fri, 14 Apr 2017 11:15:57 -0400
Subject: [Paraview-developers] Rendering in Paraview using python
In-Reply-To: <CADWn_Z7MfRXZ+23fJq2Ff7JhO57gyBQVxgHGfSHb5bbZeVDojw@mail.gmail.com>
References: <CADWn_Z7uNsF0Od0ZG1eyCwdBABBDr_UQpXMN9dQhjNt+Q-caqg@mail.gmail.com>
 <CAMaOp+GnEoHpBE7C1WGyHJ+yTTWUWv-d4+j58mWrzTkaUc21yw@mail.gmail.com>
 <CADWn_Z7MfRXZ+23fJq2Ff7JhO57gyBQVxgHGfSHb5bbZeVDojw@mail.gmail.com>
Message-ID: <CAMaOp+GbeCK6A1pfda6q4zfHYi3pux+k4K-XfiOYi11e3+RjrQ@mail.gmail.com>

There are quite a few plugins with ParaView and it's probably a bad idea to
automatically load them all. Some of them change the GUI, others require
MPI, etc.

In your plugin.cmake file you can set your plugin to be automatically
loaded by adding in the AUTOLOAD option. See
http://www.paraview.org/Wiki/Plugin_HowTo#Adding_plugins_to_ParaView_source.

On Fri, Apr 14, 2017 at 11:08 AM, sumeet kumar <sumeet.kumar507 at gmail.com>
wrote:

> Hi Andy,
>
> LoadPlugin() helps in pvpython. But why does
> *from  paraview.simple import * *does not work???
>
> Why I need to externally load my plugin even I build with paraview source.
> Also, I don't think, Its a good design to set PV_PLUGIN_PATH  or
> PV_PLUGIN_CONFIG_FILE even when the plugin is build with source. The file
> "plugin.cmake" should take care all of this.
>
> Thanks
> Sumeet
>
> On Fri, Apr 14, 2017 at 7:01 AM, Andy Bauer <andy.bauer at kitware.com>
> wrote:
>
>> Hi,
>>
>> My guess is that the reader plugin is automatically loaded in the GUI but
>> not when you run pvpython directly. Look at the LoadPlugin() or
>> LoadDistributedPlugin() command in pvpython.
>>
>> Are you setting PV_PLUGIN_PATH or PV_PLUGIN_CONFIG_FILE? Another guess
>> may be that you're using PV_PLUGIN_PATH and/or PV_PLUGIN_CONFIG_FILE to
>> load the plugin automatically through the GUI and that isn't being utilized
>> when running with pvpython. See http://www.paraview.org/Wiki/Plugin_HowTo
>> for information on that.
>>
>> Best,
>> Andy
>>
>> On Thu, Apr 13, 2017 at 11:34 PM, sumeet kumar <sumeet.kumar507 at gmail.com
>> > wrote:
>>
>>> Hey,
>>>
>>> I have a reader plugin integrated with paraview that works perfectly
>>> fine. I could use the same plugin to trace an "equivalent python code" for
>>> any visualization example.  The generated python code can be run again on
>>> paraview gui.
>>> BUT, when i try to follow the same python command in python externally
>>> like pvpython. I get the following error.
>>>
>>> >>> from paraview.simple import *
>>> updating active connection None
>>> paraview version 5.2.0-RC1
>>> updating active connection Connection (builtin:) [1]
>>> updating active connection Connection (builtin:) [1]
>>> >>> beam_Axial_Loadh5feioutput = pvESSI(FileName="/home/sumeet/Desktop
>>> /Beam_Axial_Load.h5.feioutput")
>>> Traceback (most recent call last):
>>>   File "<stdin>", line 1, in <module>
>>> NameError: name 'pvESSI' is not defined
>>>
>>> My plugin name is pvESSI. the same line works on paraview GUI mode in
>>> python shell. I tried to look on the Internet and build the plugin inside
>>> the paraview source itself, but the problem remains.
>>>
>>> Others have suggested here on link http://www.paraview.org/piperm
>>> ail/paraview/2013-October/029428.html, but I dont understand where to
>>> make changes to fix this problem.
>>>
>>>
>>> Any help would be highly appreciated.
>>>
>>> Best Regards
>>> Sumeet
>>> --
>>>
>>> Sumeet Kumar Sinha
>>> Graduate Student
>>> Phone: (+1)  <%28%2B91%29%209910516219>5306018271 <(530)%20601-8271>
>>> Website : http://www.sumeetksinha.com/
>>>
>>
>>
>
>
> --
>
> Sumeet Kumar Sinha
> Graduate Student
> Phone: (+1)  <%28%2B91%29%209910516219>5306018271 <(530)%20601-8271>
> Website : http://www.sumeetksinha.com/
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20170414/5e63efac/attachment.html>

From sumeet.kumar507 at gmail.com  Fri Apr 14 11:55:29 2017
From: sumeet.kumar507 at gmail.com (sumeet kumar)
Date: Fri, 14 Apr 2017 08:55:29 -0700
Subject: [Paraview-developers] Rendering in Paraview using python
In-Reply-To: <CAMaOp+GbeCK6A1pfda6q4zfHYi3pux+k4K-XfiOYi11e3+RjrQ@mail.gmail.com>
References: <CADWn_Z7uNsF0Od0ZG1eyCwdBABBDr_UQpXMN9dQhjNt+Q-caqg@mail.gmail.com>
 <CAMaOp+GnEoHpBE7C1WGyHJ+yTTWUWv-d4+j58mWrzTkaUc21yw@mail.gmail.com>
 <CADWn_Z7MfRXZ+23fJq2Ff7JhO57gyBQVxgHGfSHb5bbZeVDojw@mail.gmail.com>
 <CAMaOp+GbeCK6A1pfda6q4zfHYi3pux+k4K-XfiOYi11e3+RjrQ@mail.gmail.com>
Message-ID: <CADWn_Z42Adc6hdT6cp0OpvEUha-ddYEOSLUmK-sRi-CWzLNrqw@mail.gmail.com>

Yeah, it works perfectly with paraview-gui. But, does not work when I am
using pvpython or batch option. I have to manually load using  LoadPlugin()
python command .

On Fri, Apr 14, 2017 at 8:15 AM, Andy Bauer <andy.bauer at kitware.com> wrote:

> There are quite a few plugins with ParaView and it's probably a bad idea
> to automatically load them all. Some of them change the GUI, others require
> MPI, etc.
>
> In your plugin.cmake file you can set your plugin to be automatically
> loaded by adding in the AUTOLOAD option. See http://www.paraview.org/Wiki/
> Plugin_HowTo#Adding_plugins_to_ParaView_source.
>
> On Fri, Apr 14, 2017 at 11:08 AM, sumeet kumar <sumeet.kumar507 at gmail.com>
> wrote:
>
>> Hi Andy,
>>
>> LoadPlugin() helps in pvpython. But why does
>> *from  paraview.simple import * *does not work???
>>
>> Why I need to externally load my plugin even I build with paraview
>> source. Also, I don't think, Its a good design to set PV_PLUGIN_PATH  or
>> PV_PLUGIN_CONFIG_FILE even when the plugin is build with source. The file
>> "plugin.cmake" should take care all of this.
>>
>> Thanks
>> Sumeet
>>
>> On Fri, Apr 14, 2017 at 7:01 AM, Andy Bauer <andy.bauer at kitware.com>
>> wrote:
>>
>>> Hi,
>>>
>>> My guess is that the reader plugin is automatically loaded in the GUI
>>> but not when you run pvpython directly. Look at the LoadPlugin() or
>>> LoadDistributedPlugin() command in pvpython.
>>>
>>> Are you setting PV_PLUGIN_PATH or PV_PLUGIN_CONFIG_FILE? Another guess
>>> may be that you're using PV_PLUGIN_PATH and/or PV_PLUGIN_CONFIG_FILE to
>>> load the plugin automatically through the GUI and that isn't being utilized
>>> when running with pvpython. See http://www.paraview.org/Wiki/P
>>> lugin_HowTo for information on that.
>>>
>>> Best,
>>> Andy
>>>
>>> On Thu, Apr 13, 2017 at 11:34 PM, sumeet kumar <
>>> sumeet.kumar507 at gmail.com> wrote:
>>>
>>>> Hey,
>>>>
>>>> I have a reader plugin integrated with paraview that works perfectly
>>>> fine. I could use the same plugin to trace an "equivalent python code" for
>>>> any visualization example.  The generated python code can be run again on
>>>> paraview gui.
>>>> BUT, when i try to follow the same python command in python externally
>>>> like pvpython. I get the following error.
>>>>
>>>> >>> from paraview.simple import *
>>>> updating active connection None
>>>> paraview version 5.2.0-RC1
>>>> updating active connection Connection (builtin:) [1]
>>>> updating active connection Connection (builtin:) [1]
>>>> >>> beam_Axial_Loadh5feioutput = pvESSI(FileName="/home/sumeet/Desktop
>>>> /Beam_Axial_Load.h5.feioutput")
>>>> Traceback (most recent call last):
>>>>   File "<stdin>", line 1, in <module>
>>>> NameError: name 'pvESSI' is not defined
>>>>
>>>> My plugin name is pvESSI. the same line works on paraview GUI mode in
>>>> python shell. I tried to look on the Internet and build the plugin inside
>>>> the paraview source itself, but the problem remains.
>>>>
>>>> Others have suggested here on link http://www.paraview.org/piperm
>>>> ail/paraview/2013-October/029428.html, but I dont understand where to
>>>> make changes to fix this problem.
>>>>
>>>>
>>>> Any help would be highly appreciated.
>>>>
>>>> Best Regards
>>>> Sumeet
>>>> --
>>>>
>>>> Sumeet Kumar Sinha
>>>> Graduate Student
>>>> Phone: (+1)  <%28%2B91%29%209910516219>5306018271 <(530)%20601-8271>
>>>> Website : http://www.sumeetksinha.com/
>>>>
>>>
>>>
>>
>>
>> --
>>
>> Sumeet Kumar Sinha
>> Graduate Student
>> Phone: (+1)  <%28%2B91%29%209910516219>5306018271 <(530)%20601-8271>
>> Website : http://www.sumeetksinha.com/
>>
>
>


-- 

Sumeet Kumar Sinha
Graduate Student
Phone: (+1)  <%28%2B91%29%209910516219>5306018271
Website : http://www.sumeetksinha.com/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20170414/5717c21d/attachment-0001.html>

From andy.bauer at kitware.com  Fri Apr 14 12:13:56 2017
From: andy.bauer at kitware.com (Andy Bauer)
Date: Fri, 14 Apr 2017 12:13:56 -0400
Subject: [Paraview-developers] Rendering in Paraview using python
In-Reply-To: <CADWn_Z42Adc6hdT6cp0OpvEUha-ddYEOSLUmK-sRi-CWzLNrqw@mail.gmail.com>
References: <CADWn_Z7uNsF0Od0ZG1eyCwdBABBDr_UQpXMN9dQhjNt+Q-caqg@mail.gmail.com>
 <CAMaOp+GnEoHpBE7C1WGyHJ+yTTWUWv-d4+j58mWrzTkaUc21yw@mail.gmail.com>
 <CADWn_Z7MfRXZ+23fJq2Ff7JhO57gyBQVxgHGfSHb5bbZeVDojw@mail.gmail.com>
 <CAMaOp+GbeCK6A1pfda6q4zfHYi3pux+k4K-XfiOYi11e3+RjrQ@mail.gmail.com>
 <CADWn_Z42Adc6hdT6cp0OpvEUha-ddYEOSLUmK-sRi-CWzLNrqw@mail.gmail.com>
Message-ID: <CAMaOp+FvorvJ3FgNyk3_1Pptiu70oQGS0R+UaTK1LVwBkaXrWg@mail.gmail.com>

Hi,

Could you add in an issue for this at
https://gitlab.kitware.com/paraview/paraview?

Thanks,
Andy

On Fri, Apr 14, 2017 at 11:55 AM, sumeet kumar <sumeet.kumar507 at gmail.com>
wrote:

> Yeah, it works perfectly with paraview-gui. But, does not work when I am
> using pvpython or batch option. I have to manually load using  LoadPlugin()
> python command .
>
> On Fri, Apr 14, 2017 at 8:15 AM, Andy Bauer <andy.bauer at kitware.com>
> wrote:
>
>> There are quite a few plugins with ParaView and it's probably a bad idea
>> to automatically load them all. Some of them change the GUI, others require
>> MPI, etc.
>>
>> In your plugin.cmake file you can set your plugin to be automatically
>> loaded by adding in the AUTOLOAD option. See
>> http://www.paraview.org/Wiki/Plugin_HowTo#Adding_plugins_to_
>> ParaView_source.
>>
>> On Fri, Apr 14, 2017 at 11:08 AM, sumeet kumar <sumeet.kumar507 at gmail.com
>> > wrote:
>>
>>> Hi Andy,
>>>
>>> LoadPlugin() helps in pvpython. But why does
>>> *from  paraview.simple import * *does not work???
>>>
>>> Why I need to externally load my plugin even I build with paraview
>>> source. Also, I don't think, Its a good design to set PV_PLUGIN_PATH  or
>>> PV_PLUGIN_CONFIG_FILE even when the plugin is build with source. The file
>>> "plugin.cmake" should take care all of this.
>>>
>>> Thanks
>>> Sumeet
>>>
>>> On Fri, Apr 14, 2017 at 7:01 AM, Andy Bauer <andy.bauer at kitware.com>
>>> wrote:
>>>
>>>> Hi,
>>>>
>>>> My guess is that the reader plugin is automatically loaded in the GUI
>>>> but not when you run pvpython directly. Look at the LoadPlugin() or
>>>> LoadDistributedPlugin() command in pvpython.
>>>>
>>>> Are you setting PV_PLUGIN_PATH or PV_PLUGIN_CONFIG_FILE? Another guess
>>>> may be that you're using PV_PLUGIN_PATH and/or PV_PLUGIN_CONFIG_FILE to
>>>> load the plugin automatically through the GUI and that isn't being utilized
>>>> when running with pvpython. See http://www.paraview.org/Wiki/P
>>>> lugin_HowTo for information on that.
>>>>
>>>> Best,
>>>> Andy
>>>>
>>>> On Thu, Apr 13, 2017 at 11:34 PM, sumeet kumar <
>>>> sumeet.kumar507 at gmail.com> wrote:
>>>>
>>>>> Hey,
>>>>>
>>>>> I have a reader plugin integrated with paraview that works perfectly
>>>>> fine. I could use the same plugin to trace an "equivalent python code" for
>>>>> any visualization example.  The generated python code can be run again on
>>>>> paraview gui.
>>>>> BUT, when i try to follow the same python command in python externally
>>>>> like pvpython. I get the following error.
>>>>>
>>>>> >>> from paraview.simple import *
>>>>> updating active connection None
>>>>> paraview version 5.2.0-RC1
>>>>> updating active connection Connection (builtin:) [1]
>>>>> updating active connection Connection (builtin:) [1]
>>>>> >>> beam_Axial_Loadh5feioutput = pvESSI(FileName="/home/sumeet/Desktop
>>>>> /Beam_Axial_Load.h5.feioutput")
>>>>> Traceback (most recent call last):
>>>>>   File "<stdin>", line 1, in <module>
>>>>> NameError: name 'pvESSI' is not defined
>>>>>
>>>>> My plugin name is pvESSI. the same line works on paraview GUI mode in
>>>>> python shell. I tried to look on the Internet and build the plugin inside
>>>>> the paraview source itself, but the problem remains.
>>>>>
>>>>> Others have suggested here on link http://www.paraview.org/piperm
>>>>> ail/paraview/2013-October/029428.html, but I dont understand where to
>>>>> make changes to fix this problem.
>>>>>
>>>>>
>>>>> Any help would be highly appreciated.
>>>>>
>>>>> Best Regards
>>>>> Sumeet
>>>>> --
>>>>>
>>>>> Sumeet Kumar Sinha
>>>>> Graduate Student
>>>>> Phone: (+1)  <%28%2B91%29%209910516219>5306018271 <(530)%20601-8271>
>>>>> Website : http://www.sumeetksinha.com/
>>>>>
>>>>
>>>>
>>>
>>>
>>> --
>>>
>>> Sumeet Kumar Sinha
>>> Graduate Student
>>> Phone: (+1)  <%28%2B91%29%209910516219>5306018271 <(530)%20601-8271>
>>> Website : http://www.sumeetksinha.com/
>>>
>>
>>
>
>
> --
>
> Sumeet Kumar Sinha
> Graduate Student
> Phone: (+1)  <%28%2B91%29%209910516219>5306018271 <(530)%20601-8271>
> Website : http://www.sumeetksinha.com/
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20170414/000afc0c/attachment.html>

From sumeet.kumar507 at gmail.com  Fri Apr 14 14:42:38 2017
From: sumeet.kumar507 at gmail.com (sumeet kumar)
Date: Fri, 14 Apr 2017 11:42:38 -0700
Subject: [Paraview-developers] Rendering in Paraview using python
In-Reply-To: <CAMaOp+FvorvJ3FgNyk3_1Pptiu70oQGS0R+UaTK1LVwBkaXrWg@mail.gmail.com>
References: <CADWn_Z7uNsF0Od0ZG1eyCwdBABBDr_UQpXMN9dQhjNt+Q-caqg@mail.gmail.com>
 <CAMaOp+GnEoHpBE7C1WGyHJ+yTTWUWv-d4+j58mWrzTkaUc21yw@mail.gmail.com>
 <CADWn_Z7MfRXZ+23fJq2Ff7JhO57gyBQVxgHGfSHb5bbZeVDojw@mail.gmail.com>
 <CAMaOp+GbeCK6A1pfda6q4zfHYi3pux+k4K-XfiOYi11e3+RjrQ@mail.gmail.com>
 <CADWn_Z42Adc6hdT6cp0OpvEUha-ddYEOSLUmK-sRi-CWzLNrqw@mail.gmail.com>
 <CAMaOp+FvorvJ3FgNyk3_1Pptiu70oQGS0R+UaTK1LVwBkaXrWg@mail.gmail.com>
Message-ID: <CADWn_Z4qaFKxzuecTo2edbdJOrg3vDEoRH7tH4-AgsH-+f3okA@mail.gmail.com>

Sure!,

I have added this issue her
https://gitlab.kitware.com/paraview/paraview/issues/17378

Thanks
Sumeet

On Fri, Apr 14, 2017 at 9:13 AM, Andy Bauer <andy.bauer at kitware.com> wrote:

> Hi,
>
> Could you add in an issue for this at https://gitlab.kitware.com/
> paraview/paraview?
>
> Thanks,
> Andy
>
> On Fri, Apr 14, 2017 at 11:55 AM, sumeet kumar <sumeet.kumar507 at gmail.com>
> wrote:
>
>> Yeah, it works perfectly with paraview-gui. But, does not work when I am
>> using pvpython or batch option. I have to manually load using  LoadPlugin()
>> python command .
>>
>> On Fri, Apr 14, 2017 at 8:15 AM, Andy Bauer <andy.bauer at kitware.com>
>> wrote:
>>
>>> There are quite a few plugins with ParaView and it's probably a bad idea
>>> to automatically load them all. Some of them change the GUI, others require
>>> MPI, etc.
>>>
>>> In your plugin.cmake file you can set your plugin to be automatically
>>> loaded by adding in the AUTOLOAD option. See
>>> http://www.paraview.org/Wiki/Plugin_HowTo#Adding_plugins_to_
>>> ParaView_source.
>>>
>>> On Fri, Apr 14, 2017 at 11:08 AM, sumeet kumar <
>>> sumeet.kumar507 at gmail.com> wrote:
>>>
>>>> Hi Andy,
>>>>
>>>> LoadPlugin() helps in pvpython. But why does
>>>> *from  paraview.simple import * *does not work???
>>>>
>>>> Why I need to externally load my plugin even I build with paraview
>>>> source. Also, I don't think, Its a good design to set PV_PLUGIN_PATH  or
>>>> PV_PLUGIN_CONFIG_FILE even when the plugin is build with source. The file
>>>> "plugin.cmake" should take care all of this.
>>>>
>>>> Thanks
>>>> Sumeet
>>>>
>>>> On Fri, Apr 14, 2017 at 7:01 AM, Andy Bauer <andy.bauer at kitware.com>
>>>> wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> My guess is that the reader plugin is automatically loaded in the GUI
>>>>> but not when you run pvpython directly. Look at the LoadPlugin() or
>>>>> LoadDistributedPlugin() command in pvpython.
>>>>>
>>>>> Are you setting PV_PLUGIN_PATH or PV_PLUGIN_CONFIG_FILE? Another guess
>>>>> may be that you're using PV_PLUGIN_PATH and/or PV_PLUGIN_CONFIG_FILE to
>>>>> load the plugin automatically through the GUI and that isn't being utilized
>>>>> when running with pvpython. See http://www.paraview.org/Wiki/P
>>>>> lugin_HowTo for information on that.
>>>>>
>>>>> Best,
>>>>> Andy
>>>>>
>>>>> On Thu, Apr 13, 2017 at 11:34 PM, sumeet kumar <
>>>>> sumeet.kumar507 at gmail.com> wrote:
>>>>>
>>>>>> Hey,
>>>>>>
>>>>>> I have a reader plugin integrated with paraview that works perfectly
>>>>>> fine. I could use the same plugin to trace an "equivalent python code" for
>>>>>> any visualization example.  The generated python code can be run again on
>>>>>> paraview gui.
>>>>>> BUT, when i try to follow the same python command in python
>>>>>> externally like pvpython. I get the following error.
>>>>>>
>>>>>> >>> from paraview.simple import *
>>>>>> updating active connection None
>>>>>> paraview version 5.2.0-RC1
>>>>>> updating active connection Connection (builtin:) [1]
>>>>>> updating active connection Connection (builtin:) [1]
>>>>>> >>> beam_Axial_Loadh5feioutput = pvESSI(FileName="/home/sumeet/
>>>>>> Desktop/Beam_Axial_Load.h5.feioutput")
>>>>>> Traceback (most recent call last):
>>>>>>   File "<stdin>", line 1, in <module>
>>>>>> NameError: name 'pvESSI' is not defined
>>>>>>
>>>>>> My plugin name is pvESSI. the same line works on paraview GUI mode in
>>>>>> python shell. I tried to look on the Internet and build the plugin inside
>>>>>> the paraview source itself, but the problem remains.
>>>>>>
>>>>>> Others have suggested here on link http://www.paraview.org/piperm
>>>>>> ail/paraview/2013-October/029428.html, but I dont understand where
>>>>>> to make changes to fix this problem.
>>>>>>
>>>>>>
>>>>>> Any help would be highly appreciated.
>>>>>>
>>>>>> Best Regards
>>>>>> Sumeet
>>>>>> --
>>>>>>
>>>>>> Sumeet Kumar Sinha
>>>>>> Graduate Student
>>>>>> Phone: (+1)  <%28%2B91%29%209910516219>5306018271 <(530)%20601-8271>
>>>>>> Website : http://www.sumeetksinha.com/
>>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>>
>>>> Sumeet Kumar Sinha
>>>> Graduate Student
>>>> Phone: (+1)  <%28%2B91%29%209910516219>5306018271 <(530)%20601-8271>
>>>> Website : http://www.sumeetksinha.com/
>>>>
>>>
>>>
>>
>>
>> --
>>
>> Sumeet Kumar Sinha
>> Graduate Student
>> Phone: (+1)  <%28%2B91%29%209910516219>5306018271 <(530)%20601-8271>
>> Website : http://www.sumeetksinha.com/
>>
>
>


-- 

Sumeet Kumar Sinha
Graduate Student
Phone: (+1)  <%28%2B91%29%209910516219>5306018271
Website : http://www.sumeetksinha.com/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20170414/12ff828f/attachment-0001.html>

From sumeet.kumar507 at gmail.com  Fri Apr 14 14:48:58 2017
From: sumeet.kumar507 at gmail.com (sumeet kumar)
Date: Fri, 14 Apr 2017 11:48:58 -0700
Subject: [Paraview-developers] Save paraview animation in High Resolution
	and pictures in vector Graphics
Message-ID: <CADWn_Z4bwUCwVNKiP92StyQSitLdQfy4=YpS15rNW-mzX6NY7w@mail.gmail.com>

Hi,

I am struggling a bit to make animations and images in high resolution in
paraview. I have latest Paraview 5.12 build on my linux machine.

Currenntly, I am not able to save the images in vetor graphics format nor
the animation over certain resolution fixed by paraview.

Any help would be highly appreciated.

-- 

Sumeet Kumar Sinha
Graduate Student
Phone: (+1)  <%28%2B91%29%209910516219>5306018271
Website : http://www.sumeetksinha.com/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20170414/64378d54/attachment.html>

From aron.helser at kitware.com  Sat Apr 15 16:12:18 2017
From: aron.helser at kitware.com (Aron Helser)
Date: Sat, 15 Apr 2017 16:12:18 -0400
Subject: [Paraview-developers] Ctest OpenGL2 error,
Message-ID: <CAF2skS6D04bUMbowNL_3jYNiHmv1h8T50k64yhXrbHZyCAQh+Q@mail.gmail.com>

Hi all,
Whenever I run ctest locally, I'm seeing errors like the one below. I'm
running on a win10 laptop, with an Optimus setup - both integrated Intel
graphics and an nvidia Quadro M1000M. My search only turned up an error
like this on mobile Android builds. It happens on any test that does OpenGL
rendering, as far as I can tell, like pv.SaveLoadStatePython or pv.XYChart.
So far, the tests have produced correct image output.

Has anyone else encountered this? Ideas on what might be wrong? Thanks!
Aron

1577: "ERROR: In
C:\akit\ParaView\src\VTK\Rendering\OpenGL2\vtkTextureObject.cxx, line 562"
1577: vtkTextureObject (000001A76321D600): failed at glBindTexture(0) 16
OpenGL errors detected
1577:   0 : (1282) Invalid operation
1577:   1 : (1282) Invalid operation
1577:   2 : (1282) Invalid operation
1577:   3 : (1282) Invalid operation
1577:   4 : (1282) Invalid operation
1577:   5 : (1282) Invalid operation
1577:   6 : (1282) Invalid operation
1577:   7 : (1282) Invalid operation
1577:   8 : (1282) Invalid operation
1577:   9 : (1282) Invalid operation
1577:   10 : (1282) Invalid operation
1577:   11 : (1282) Invalid operation
1577:   12 : (1282) Invalid operation
1577:   13 : (1282) Invalid operation
1577:   14 : (1282) Invalid operation
1577:   15 : (1282) Invalid operation
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20170415/09c64130/attachment.html>

From utkarsh.ayachit at kitware.com  Mon Apr 17 10:30:24 2017
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Mon, 17 Apr 2017 10:30:24 -0400
Subject: [Paraview-developers] Save paraview animation in High
	Resolution and pictures in vector Graphics
In-Reply-To: <CADWn_Z4bwUCwVNKiP92StyQSitLdQfy4=YpS15rNW-mzX6NY7w@mail.gmail.com>
References: <CADWn_Z4bwUCwVNKiP92StyQSitLdQfy4=YpS15rNW-mzX6NY7w@mail.gmail.com>
Message-ID: <CADHSJjC-7hR=T6Ku9CjfgnccsSZfvEudZiae=VjriBpaqhAckw@mail.gmail.com>

Sumeet,

It's not clear what problem you are having or how you want us to help.
Please describe the steps to reproduce the issue and the issue so that we
can reproduce it to suggest alternatives or fixes.

Utkarsh

p.s. please avoid cc-ing folks when emailing the mailing list. There's no
need for it.

On Fri, Apr 14, 2017 at 2:48 PM, sumeet kumar <sumeet.kumar507 at gmail.com>
wrote:

> Hi,
>
> I am struggling a bit to make animations and images in high resolution in
> paraview. I have latest Paraview 5.12 build on my linux machine.
>
> Currenntly, I am not able to save the images in vetor graphics format nor
> the animation over certain resolution fixed by paraview.
>
> Any help would be highly appreciated.
>
> --
>
> Sumeet Kumar Sinha
> Graduate Student
> Phone: (+1)  <%28%2B91%29%209910516219>5306018271 <(530)%20601-8271>
> Website : http://www.sumeetksinha.com/
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20170417/f8b261f9/attachment.html>

From joseph.g.hennessey2.ctr at mail.mil  Tue Apr 18 09:43:43 2017
From: joseph.g.hennessey2.ctr at mail.mil (Hennessey, Joseph G CTR USARMY RDECOM ARL (US))
Date: Tue, 18 Apr 2017 13:43:43 +0000
Subject: [Paraview-developers] Problem with ParaView 5.3.0 mac client on
	some HPC systems
Message-ID: <10A03274360DCF47A6EE78C9952A31CA91E6C2C7@UCOLHPUD.easf.csd.disa.mil>

Hello,

I am having a problem with ParaView 5.3.0 mac client on some HPC systems.
When connected to a remote render/data server the remote server is not
sending the rendered image to the mac client. The same servers are sending
the images to the linux client for 5.3.0, so I do not think it is the
server.
Also, the same systems work just fine with ParaView 5.2.0 servers and
clients.

Has anyone else seen this issue with the ParaView 5.3.0 mac client?

Thanks,

Joe

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Joseph G. Hennessey Ph.D., SAIC
Team SAIC
Army Research Lab
DOD Supercomputing Resource Center

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

From utkarsh.ayachit at kitware.com  Tue Apr 18 10:05:04 2017
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Tue, 18 Apr 2017 10:05:04 -0400
Subject: [Paraview-developers] Problem with ParaView 5.3.0 mac client on
 some HPC systems
In-Reply-To: <10A03274360DCF47A6EE78C9952A31CA91E6C2C7@UCOLHPUD.easf.csd.disa.mil>
References: <10A03274360DCF47A6EE78C9952A31CA91E6C2C7@UCOLHPUD.easf.csd.disa.mil>
Message-ID: <CADHSJjCcQ5k++XORhgHyadpiNNno2SEXAyUtYQrTrx8PM3WXaw@mail.gmail.com>

That's odd. Can you clarify what you mean by "not sending rendering image".
Does it mean you just see a blank screen? Just to confirm, both were built
with OpenGL2 rendering backend, right? If you try running pvserver on the
Mac client itself, does that work?

On Tue, Apr 18, 2017 at 9:43 AM, Hennessey, Joseph G CTR USARMY RDECOM ARL
(US) <joseph.g.hennessey2.ctr at mail.mil> wrote:

> Hello,
>
> I am having a problem with ParaView 5.3.0 mac client on some HPC systems.
> When connected to a remote render/data server the remote server is not
> sending the rendered image to the mac client. The same servers are sending
> the images to the linux client for 5.3.0, so I do not think it is the
> server.
> Also, the same systems work just fine with ParaView 5.2.0 servers and
> clients.
>
> Has anyone else seen this issue with the ParaView 5.3.0 mac client?
>
> Thanks,
>
> Joe
>
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> Joseph G. Hennessey Ph.D., SAIC
> Team SAIC
> Army Research Lab
> DOD Supercomputing Resource Center
>
>
> _______________________________________________
> 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/20170418/c91b5c42/attachment.html>

From thomasblome at startmail.com  Tue Apr 18 10:56:13 2017
From: thomasblome at startmail.com (thomasblome at startmail.com)
Date: Tue, 18 Apr 2017 16:56:13 +0200
Subject: [Paraview-developers] Reinitialization of Catalyst
Message-ID: <2ec2ce94a66718f6e4215334706847f3.startmail@www.startmail.com>

Hi,

In my simulation programme one can reinput changed system data after 
Catalyst has already been initialized to rerun the simulation with 
modified data.
So, I guess the coprocessor has to be reinitialized too. That's why I 
have tried something like:

// first run
call coprocessorinitializewithpython("coproc.py",9)
...some code...

// after reinput of new system data (same programme session)
call coprocessorfinalize()
call coprocessorinitializewithpython("coproc.py",9)

but the programme breaks during the second call to 
coprocessorinitializewithpython().
The problem is that if I don?t finalize and/or initialize again, I get 
error messages saying "New time step is not after last time step" and 
so on.

I don?t want to exit the programme and restart it, just to get it 
working.
What is the correct way to solve this?

Best regards,
Thomas
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20170418/8154e685/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/20170418/8154e685/attachment.key>

From joseph.g.hennessey2.ctr at mail.mil  Tue Apr 18 11:33:56 2017
From: joseph.g.hennessey2.ctr at mail.mil (Hennessey, Joseph G CTR USARMY RDECOM ARL (US))
Date: Tue, 18 Apr 2017 15:33:56 +0000
Subject: [Paraview-developers] [Non-DoD Source] Re: Problem with
 ParaView 5.3.0 mac client on some HPC systems
In-Reply-To: <CADHSJjCcQ5k++XORhgHyadpiNNno2SEXAyUtYQrTrx8PM3WXaw@mail.gmail.com>
References: <10A03274360DCF47A6EE78C9952A31CA91E6C2C7@UCOLHPUD.easf.csd.disa.mil>
 <CADHSJjCcQ5k++XORhgHyadpiNNno2SEXAyUtYQrTrx8PM3WXaw@mail.gmail.com>
Message-ID: <10A03274360DCF47A6EE78C9952A31CA91E6C311@UCOLHPUD.easf.csd.disa.mil>

Utkarsh,

The render windows has no image rendered in it.
The data will render on the client, but once it gets,
complex enough to render on the server (or you set the limit to 0 MBs)
then nothing is rendered in the render window.
Both are using the OpenGL2 render backend, and the client on
the Mac is the one I have downloaded for the ParaView web site.

I will check if it runs correctly with a local pvserver, at the next 
opportunity.

Thanks,

Joe

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Joseph G. Hennessey Ph.D., SAIC
Team SAIC
Army Research Lab
DOD Supercomputing Resource Center


-----Original Message-----
From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com]
Sent: Tuesday, April 18, 2017 10:05 AM
To: Hennessey, Joseph G CTR USARMY RDECOM ARL (US) 
<joseph.g.hennessey2.ctr at mail.mil>
Cc: ParaView Developers <paraview-developers at paraview.org>
Subject: [Non-DoD Source] Re: [Paraview-developers] Problem with ParaView 
5.3.0 mac client on some HPC systems

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


________________________________



That's odd. Can you clarify what you mean by "not sending rendering image". 
Does it mean you just see a blank screen? Just to confirm, both were built 
with OpenGL2 rendering backend, right? If you try running pvserver on the Mac 
client itself, does that work?

On Tue, Apr 18, 2017 at 9:43 AM, Hennessey, Joseph G CTR USARMY RDECOM ARL 
(US) <joseph.g.hennessey2.ctr at mail.mil < 
Caution-mailto:joseph.g.hennessey2.ctr at mail.mil > > wrote:


	Hello,

	I am having a problem with ParaView 5.3.0 mac client on some HPC systems.
	When connected to a remote render/data server the remote server is not
	sending the rendered image to the mac client. The same servers are sending
	the images to the linux client for 5.3.0, so I do not think it is the
	server.
	Also, the same systems work just fine with ParaView 5.2.0 servers and
	clients.

	Has anyone else seen this issue with the ParaView 5.3.0 mac client?

	Thanks,

	Joe

	~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
	Joseph G. Hennessey Ph.D., SAIC
	Team SAIC
	Army Research Lab
	DOD Supercomputing Resource Center


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

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

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

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




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

From utkarsh.ayachit at kitware.com  Tue Apr 18 13:41:10 2017
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Tue, 18 Apr 2017 13:41:10 -0400
Subject: [Paraview-developers] [Non-DoD Source] Re: Problem with
 ParaView 5.3.0 mac client on some HPC systems
In-Reply-To: <10A03274360DCF47A6EE78C9952A31CA91E6C311@UCOLHPUD.easf.csd.disa.mil>
References: <10A03274360DCF47A6EE78C9952A31CA91E6C2C7@UCOLHPUD.easf.csd.disa.mil>
 <CADHSJjCcQ5k++XORhgHyadpiNNno2SEXAyUtYQrTrx8PM3WXaw@mail.gmail.com>
 <10A03274360DCF47A6EE78C9952A31CA91E6C311@UCOLHPUD.easf.csd.disa.mil>
Message-ID: <CADHSJjAnNW6GyUHv3wdsL1ONqs0Q+LDhs_DG9qQF+6AAeYJcoQ@mail.gmail.com>

Odd. I have not see this. Let me know how the local-pvserver test
goes. Maybe that'll give us some clues.

On Tue, Apr 18, 2017 at 11:33 AM, Hennessey, Joseph G CTR USARMY
RDECOM ARL (US) <joseph.g.hennessey2.ctr at mail.mil> wrote:
> Utkarsh,
>
> The render windows has no image rendered in it.
> The data will render on the client, but once it gets,
> complex enough to render on the server (or you set the limit to 0 MBs)
> then nothing is rendered in the render window.
> Both are using the OpenGL2 render backend, and the client on
> the Mac is the one I have downloaded for the ParaView web site.
>
> I will check if it runs correctly with a local pvserver, at the next
> opportunity.
>
> Thanks,
>
> Joe
>
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> Joseph G. Hennessey Ph.D., SAIC
> Team SAIC
> Army Research Lab
> DOD Supercomputing Resource Center
>
>
> -----Original Message-----
> From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com]
> Sent: Tuesday, April 18, 2017 10:05 AM
> To: Hennessey, Joseph G CTR USARMY RDECOM ARL (US)
> <joseph.g.hennessey2.ctr at mail.mil>
> Cc: ParaView Developers <paraview-developers at paraview.org>
> Subject: [Non-DoD Source] Re: [Paraview-developers] Problem with ParaView
> 5.3.0 mac client on some HPC systems
>
> All active links contained in this email were disabled. Please verify the
> identity of the sender, and confirm the authenticity of all links contained
> within the message prior to copying and pasting the address to a Web browser.
>
>
> ________________________________
>
>
>
> That's odd. Can you clarify what you mean by "not sending rendering image".
> Does it mean you just see a blank screen? Just to confirm, both were built
> with OpenGL2 rendering backend, right? If you try running pvserver on the Mac
> client itself, does that work?
>
> On Tue, Apr 18, 2017 at 9:43 AM, Hennessey, Joseph G CTR USARMY RDECOM ARL
> (US) <joseph.g.hennessey2.ctr at mail.mil <
> Caution-mailto:joseph.g.hennessey2.ctr at mail.mil > > wrote:
>
>
>         Hello,
>
>         I am having a problem with ParaView 5.3.0 mac client on some HPC systems.
>         When connected to a remote render/data server the remote server is not
>         sending the rendered image to the mac client. The same servers are sending
>         the images to the linux client for 5.3.0, so I do not think it is the
>         server.
>         Also, the same systems work just fine with ParaView 5.2.0 servers and
>         clients.
>
>         Has anyone else seen this issue with the ParaView 5.3.0 mac client?
>
>         Thanks,
>
>         Joe
>
>         ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>         Joseph G. Hennessey Ph.D., SAIC
>         Team SAIC
>         Army Research Lab
>         DOD Supercomputing Resource Center
>
>
>         _______________________________________________
>         Powered by Caution-www.kitware.com < Caution-http://www.kitware.com >
>
>         Visit other Kitware open-source projects at
> Caution-http://www.kitware.com/opensource/opensource.html <
> Caution-http://www.kitware.com/opensource/opensource.html >
>
>         Search the list archives at:
> Caution-http://markmail.org/search/?q=Paraview-developers <
> Caution-http://markmail.org/search/?q=Paraview-developers >
>
>         Follow this link to subscribe/unsubscribe:
>         Caution-http://public.kitware.com/mailman/listinfo/paraview-developers <
> Caution-http://public.kitware.com/mailman/listinfo/paraview-developers >
>
>
>
>

From aron.helser at kitware.com  Tue Apr 18 21:44:24 2017
From: aron.helser at kitware.com (Aron Helser)
Date: Tue, 18 Apr 2017 21:44:24 -0400
Subject: [Paraview-developers] Ctest OpenGL2 error,
In-Reply-To: <CAF2skS6D04bUMbowNL_3jYNiHmv1h8T50k64yhXrbHZyCAQh+Q@mail.gmail.com>
References: <CAF2skS6D04bUMbowNL_3jYNiHmv1h8T50k64yhXrbHZyCAQh+Q@mail.gmail.com>
Message-ID: <CAF2skS7erfY2jj0GbTo0bSHQFRGVFS2BtE3q5L7k6zWgF9qz9g@mail.gmail.com>

I can reproduce this error inside a ParaView debug build simply by creating
a sphere source, then closing the connection (File .. Disconnect). It
doesn't repro with the ParaView 5.3 downloaded version because that's not a
debug build.

Does anyone else have a win10 debug build of ParaView and can confirm or
deny this behavior?
I can repro when using either nvidia or intel graphics, as reported by the
ParaView About box.
Thanks!
Aron

On Sat, Apr 15, 2017 at 4:12 PM, Aron Helser <aron.helser at kitware.com>
wrote:

> Hi all,
> Whenever I run ctest locally, I'm seeing errors like the one below. I'm
> running on a win10 laptop, with an Optimus setup - both integrated Intel
> graphics and an nvidia Quadro M1000M. My search only turned up an error
> like this on mobile Android builds. It happens on any test that does OpenGL
> rendering, as far as I can tell, like pv.SaveLoadStatePython or pv.XYChart.
> So far, the tests have produced correct image output.
>
> Has anyone else encountered this? Ideas on what might be wrong? Thanks!
> Aron
>
> 1577: "ERROR: In C:\akit\ParaView\src\VTK\Rendering\OpenGL2\vtkTextureObject.cxx,
> line 562"
> 1577: vtkTextureObject (000001A76321D600): failed at glBindTexture(0) 16
> OpenGL errors detected
> 1577:   0 : (1282) Invalid operation
> 1577:   1 : (1282) Invalid operation
> 1577:   2 : (1282) Invalid operation
> 1577:   3 : (1282) Invalid operation
> 1577:   4 : (1282) Invalid operation
> 1577:   5 : (1282) Invalid operation
> 1577:   6 : (1282) Invalid operation
> 1577:   7 : (1282) Invalid operation
> 1577:   8 : (1282) Invalid operation
> 1577:   9 : (1282) Invalid operation
> 1577:   10 : (1282) Invalid operation
> 1577:   11 : (1282) Invalid operation
> 1577:   12 : (1282) Invalid operation
> 1577:   13 : (1282) Invalid operation
> 1577:   14 : (1282) Invalid operation
> 1577:   15 : (1282) Invalid operation
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20170418/30f0fc6d/attachment.html>

From joseph.g.hennessey2.ctr at mail.mil  Wed Apr 19 12:00:58 2017
From: joseph.g.hennessey2.ctr at mail.mil (Hennessey, Joseph G CTR USARMY RDECOM ARL (US))
Date: Wed, 19 Apr 2017 16:00:58 +0000
Subject: [Paraview-developers] [Non-DoD Source] Re: Problem with
 ParaView 5.3.0 mac client on some HPC systems
In-Reply-To: <CADHSJjAnNW6GyUHv3wdsL1ONqs0Q+LDhs_DG9qQF+6AAeYJcoQ@mail.gmail.com>
References: <10A03274360DCF47A6EE78C9952A31CA91E6C2C7@UCOLHPUD.easf.csd.disa.mil>
 <CADHSJjCcQ5k++XORhgHyadpiNNno2SEXAyUtYQrTrx8PM3WXaw@mail.gmail.com>
 <10A03274360DCF47A6EE78C9952A31CA91E6C311@UCOLHPUD.easf.csd.disa.mil>
 <CADHSJjAnNW6GyUHv3wdsL1ONqs0Q+LDhs_DG9qQF+6AAeYJcoQ@mail.gmail.com>
Message-ID: <10A03274360DCF47A6EE78C9952A31CA91E6E9B3@UCOLHPUD.easf.csd.disa.mil>

Utkarsh,

When tested under 10.9.5 with a local pvserver,
the problems exists, (ie no visible geometry rendered by the local pvserver).
With MacOS 10.12.4 the problem does not occur and the local pvserver,
correctly renderers the geometry. This is with the standard MacOS 5.3.0 binary
from the kitware site. My problem is I have some systems that cannot yet
be upgraded past 10.9.5 due to security restrictions. Any suggestions?

Thanks,

Joe

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Joseph G. Hennessey Ph.D., SAIC
Team SAIC
Army Research Lab
DOD Supercomputing Resource Center

-----Original Message-----
From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com]
Sent: Tuesday, April 18, 2017 1:41 PM
To: Hennessey, Joseph G CTR USARMY RDECOM ARL (US) 
<joseph.g.hennessey2.ctr at mail.mil>
Cc: ParaView Developers <paraview-developers at paraview.org>
Subject: Re: [Non-DoD Source] Re: [Paraview-developers] Problem with ParaView 
5.3.0 mac client on some HPC systems

Odd. I have not see this. Let me know how the local-pvserver test goes. Maybe 
that'll give us some clues.

On Tue, Apr 18, 2017 at 11:33 AM, Hennessey, Joseph G CTR USARMY RDECOM ARL 
(US) <joseph.g.hennessey2.ctr at mail.mil> wrote:
> Utkarsh,
>
> The render windows has no image rendered in it.
> The data will render on the client, but once it gets, complex enough
> to render on the server (or you set the limit to 0 MBs) then nothing
> is rendered in the render window.
> Both are using the OpenGL2 render backend, and the client on the Mac
> is the one I have downloaded for the ParaView web site.
>
> I will check if it runs correctly with a local pvserver, at the next
> opportunity.
>
> Thanks,
>
> Joe
>
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> Joseph G. Hennessey Ph.D., SAIC
> Team SAIC
> Army Research Lab
> DOD Supercomputing Resource Center
>
>
> -----Original Message-----
> From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com]
> Sent: Tuesday, April 18, 2017 10:05 AM
> To: Hennessey, Joseph G CTR USARMY RDECOM ARL (US)
> <joseph.g.hennessey2.ctr at mail.mil>
> Cc: ParaView Developers <paraview-developers at paraview.org>
> Subject: [Non-DoD Source] Re: [Paraview-developers] Problem with
> ParaView
> 5.3.0 mac client on some HPC systems
>
> All active links contained in this email were disabled. Please verify
> the identity of the sender, and confirm the authenticity of all links
> contained within the message prior to copying and pasting the address to a 
> Web browser.
>
>
> ________________________________
>
>
>
> That's odd. Can you clarify what you mean by "not sending rendering image".
> Does it mean you just see a blank screen? Just to confirm, both were
> built with OpenGL2 rendering backend, right? If you try running
> pvserver on the Mac client itself, does that work?
>
> On Tue, Apr 18, 2017 at 9:43 AM, Hennessey, Joseph G CTR USARMY RDECOM
> ARL
> (US) <joseph.g.hennessey2.ctr at mail.mil <
> Caution-mailto:joseph.g.hennessey2.ctr at mail.mil > > wrote:
>
>
>         Hello,
>
>         I am having a problem with ParaView 5.3.0 mac client on some HPC 
> systems.
>         When connected to a remote render/data server the remote server is 
> not
>         sending the rendered image to the mac client. The same servers are 
> sending
>         the images to the linux client for 5.3.0, so I do not think it is 
> the
>         server.
>         Also, the same systems work just fine with ParaView 5.2.0 servers 
> and
>         clients.
>
>         Has anyone else seen this issue with the ParaView 5.3.0 mac client?
>
>         Thanks,
>
>         Joe
>
>         ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>         Joseph G. Hennessey Ph.D., SAIC
>         Team SAIC
>         Army Research Lab
>         DOD Supercomputing Resource Center
>
>
>         _______________________________________________
>         Powered by Caution-www.kitware.com <
> Caution-http://www.kitware.com >
>
>         Visit other Kitware open-source projects at
> Caution-http://www.kitware.com/opensource/opensource.html <
> Caution-http://www.kitware.com/opensource/opensource.html >
>
>         Search the list archives at:
> Caution-http://markmail.org/search/?q=Paraview-developers <
> Caution-http://markmail.org/search/?q=Paraview-developers >
>
>         Follow this link to subscribe/unsubscribe:
>
> Caution-http://public.kitware.com/mailman/listinfo/paraview-developers
> <
> Caution-http://public.kitware.com/mailman/listinfo/paraview-developers
> >
>
>
>
>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 5615 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20170419/401b10c6/attachment.bin>

From thomasblome at startmail.com  Wed Apr 19 12:41:54 2017
From: thomasblome at startmail.com (thomasblome at startmail.com)
Date: Wed, 19 Apr 2017 18:41:54 +0200
Subject: [Paraview-developers] Reinitialization of Catalyst
In-Reply-To: <2ec2ce94a66718f6e4215334706847f3.startmail@www.startmail.com>
References: <2ec2ce94a66718f6e4215334706847f3.startmail@www.startmail.com>
Message-ID: <8fd98f3db764f57f8205acb900019843.startmail@www.startmail.com>

I just found out that I can go without the extra calls to 
coprocessorfinalize() and 
coprocessorinitializewithpython("coproc.py",9) (obviously, they can 
only be called once).
In the PV pipeline browser the time data is correct after rerunning the 
simulation and modified system data gets updated and displayed 
correctly too.

However, I still get following warning:

Warning: In 
C:\Kitware\ParaView-v5.3.0\ParaViewCore\VTKExtensions\Core\vtkPVTriv
ialProducer.cxx, line 66
vtkPVTrivialProducer (000000000A19E000): New time step is not after 
last time st
ep.

That?s why I assumed the state of the coprocessor is not correct after 
restarting the simulation.

But I guess one can savely ignore this warning?!

Best,
Thomas

?
Am Dienstag, 18. April 2017 16:56 schrieb thomasblome at startmail.com:
?
> Hi,
> 
> In my simulation programme one can reinput changed system data after 
> Catalyst has already been initialized to rerun the simulation with 
> modified data.
> So, I guess the coprocessor has to be reinitialized too. That's why I 
> have tried something like:
> 
> // first run
> call coprocessorinitializewithpython("coproc.py",9)
> ...some code...
> 
> // after reinput of new system data (same programme session)
> call coprocessorfinalize()
> call coprocessorinitializewithpython("coproc.py",9)
> 
> but the programme breaks during the second call to 
> coprocessorinitializewithpython().
> The problem is that if I don?t finalize and/or initialize again, I 
> get error messages saying "New time step is not after last time step" 
> and so on.
> 
> I don?t want to exit the programme and restart it, just to get it 
> working.
> What is the correct way to solve this?
> 
> Best regards,
> Thomas
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20170419/043a37ce/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/20170419/043a37ce/attachment.key>

From ben.boeckel at kitware.com  Wed Apr 19 13:20:55 2017
From: ben.boeckel at kitware.com (Ben Boeckel)
Date: Wed, 19 Apr 2017 13:20:55 -0400
Subject: [Paraview-developers] Reinitialization of Catalyst
In-Reply-To: <8fd98f3db764f57f8205acb900019843.startmail@www.startmail.com>
References: <2ec2ce94a66718f6e4215334706847f3.startmail@www.startmail.com>
 <8fd98f3db764f57f8205acb900019843.startmail@www.startmail.com>
Message-ID: <20170419172055.GC17603@megas.kitware.com>

On Wed, Apr 19, 2017 at 18:41:54 +0200, thomasblome at startmail.com wrote:
> But I guess one can savely ignore this warning?!

Looking at the code, it is just a warning. It looks like the list of
timesteps is not cleared internally (there is no method exposed to do
this either). It can be ignored only if the TIME_RANGE output can be
ignored: that is generated by getting the first time step and the last
time step. It should work if the start time step for all of your runs
starts at the same value though.

--Ben

From utkarsh.ayachit at kitware.com  Wed Apr 19 13:38:52 2017
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Wed, 19 Apr 2017 13:38:52 -0400
Subject: [Paraview-developers] [Non-DoD Source] Re: Problem with
 ParaView 5.3.0 mac client on some HPC systems
In-Reply-To: <10A03274360DCF47A6EE78C9952A31CA91E6E9B3@UCOLHPUD.easf.csd.disa.mil>
References: <10A03274360DCF47A6EE78C9952A31CA91E6C2C7@UCOLHPUD.easf.csd.disa.mil>
 <CADHSJjCcQ5k++XORhgHyadpiNNno2SEXAyUtYQrTrx8PM3WXaw@mail.gmail.com>
 <10A03274360DCF47A6EE78C9952A31CA91E6C311@UCOLHPUD.easf.csd.disa.mil>
 <CADHSJjAnNW6GyUHv3wdsL1ONqs0Q+LDhs_DG9qQF+6AAeYJcoQ@mail.gmail.com>
 <10A03274360DCF47A6EE78C9952A31CA91E6E9B3@UCOLHPUD.easf.csd.disa.mil>
Message-ID: <CADHSJjDxRn7KFvBDkGw2YLhr3jveFYeNzaVLgN1ogKCe9WxT0Q@mail.gmail.com>

Odd. I think I have a Mavericks machine at home. Let me try to see if
I can reproduce it there this evening.

Utkarsh

On Wed, Apr 19, 2017 at 12:00 PM, Hennessey, Joseph G CTR USARMY
RDECOM ARL (US) <joseph.g.hennessey2.ctr at mail.mil> wrote:
> Utkarsh,
>
> When tested under 10.9.5 with a local pvserver,
> the problems exists, (ie no visible geometry rendered by the local pvserver).
> With MacOS 10.12.4 the problem does not occur and the local pvserver,
> correctly renderers the geometry. This is with the standard MacOS 5.3.0 binary
> from the kitware site. My problem is I have some systems that cannot yet
> be upgraded past 10.9.5 due to security restrictions. Any suggestions?
>
> Thanks,
>
> Joe
>
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> Joseph G. Hennessey Ph.D., SAIC
> Team SAIC
> Army Research Lab
> DOD Supercomputing Resource Center
>
> -----Original Message-----
> From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com]
> Sent: Tuesday, April 18, 2017 1:41 PM
> To: Hennessey, Joseph G CTR USARMY RDECOM ARL (US)
> <joseph.g.hennessey2.ctr at mail.mil>
> Cc: ParaView Developers <paraview-developers at paraview.org>
> Subject: Re: [Non-DoD Source] Re: [Paraview-developers] Problem with ParaView
> 5.3.0 mac client on some HPC systems
>
> Odd. I have not see this. Let me know how the local-pvserver test goes. Maybe
> that'll give us some clues.
>
> On Tue, Apr 18, 2017 at 11:33 AM, Hennessey, Joseph G CTR USARMY RDECOM ARL
> (US) <joseph.g.hennessey2.ctr at mail.mil> wrote:
>> Utkarsh,
>>
>> The render windows has no image rendered in it.
>> The data will render on the client, but once it gets, complex enough
>> to render on the server (or you set the limit to 0 MBs) then nothing
>> is rendered in the render window.
>> Both are using the OpenGL2 render backend, and the client on the Mac
>> is the one I have downloaded for the ParaView web site.
>>
>> I will check if it runs correctly with a local pvserver, at the next
>> opportunity.
>>
>> Thanks,
>>
>> Joe
>>
>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>> Joseph G. Hennessey Ph.D., SAIC
>> Team SAIC
>> Army Research Lab
>> DOD Supercomputing Resource Center
>>
>>
>> -----Original Message-----
>> From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com]
>> Sent: Tuesday, April 18, 2017 10:05 AM
>> To: Hennessey, Joseph G CTR USARMY RDECOM ARL (US)
>> <joseph.g.hennessey2.ctr at mail.mil>
>> Cc: ParaView Developers <paraview-developers at paraview.org>
>> Subject: [Non-DoD Source] Re: [Paraview-developers] Problem with
>> ParaView
>> 5.3.0 mac client on some HPC systems
>>
>> All active links contained in this email were disabled. Please verify
>> the identity of the sender, and confirm the authenticity of all links
>> contained within the message prior to copying and pasting the address to a
>> Web browser.
>>
>>
>> ________________________________
>>
>>
>>
>> That's odd. Can you clarify what you mean by "not sending rendering image".
>> Does it mean you just see a blank screen? Just to confirm, both were
>> built with OpenGL2 rendering backend, right? If you try running
>> pvserver on the Mac client itself, does that work?
>>
>> On Tue, Apr 18, 2017 at 9:43 AM, Hennessey, Joseph G CTR USARMY RDECOM
>> ARL
>> (US) <joseph.g.hennessey2.ctr at mail.mil <
>> Caution-mailto:joseph.g.hennessey2.ctr at mail.mil > > wrote:
>>
>>
>>         Hello,
>>
>>         I am having a problem with ParaView 5.3.0 mac client on some HPC
>> systems.
>>         When connected to a remote render/data server the remote server is
>> not
>>         sending the rendered image to the mac client. The same servers are
>> sending
>>         the images to the linux client for 5.3.0, so I do not think it is
>> the
>>         server.
>>         Also, the same systems work just fine with ParaView 5.2.0 servers
>> and
>>         clients.
>>
>>         Has anyone else seen this issue with the ParaView 5.3.0 mac client?
>>
>>         Thanks,
>>
>>         Joe
>>
>>         ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>         Joseph G. Hennessey Ph.D., SAIC
>>         Team SAIC
>>         Army Research Lab
>>         DOD Supercomputing Resource Center
>>
>>
>>         _______________________________________________
>>         Powered by Caution-www.kitware.com <
>> Caution-http://www.kitware.com >
>>
>>         Visit other Kitware open-source projects at
>> Caution-http://www.kitware.com/opensource/opensource.html <
>> Caution-http://www.kitware.com/opensource/opensource.html >
>>
>>         Search the list archives at:
>> Caution-http://markmail.org/search/?q=Paraview-developers <
>> Caution-http://markmail.org/search/?q=Paraview-developers >
>>
>>         Follow this link to subscribe/unsubscribe:
>>
>> Caution-http://public.kitware.com/mailman/listinfo/paraview-developers
>> <
>> Caution-http://public.kitware.com/mailman/listinfo/paraview-developers
>> >
>>
>>
>>
>>

From utkarsh.ayachit at kitware.com  Wed Apr 19 20:47:58 2017
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Wed, 19 Apr 2017 20:47:58 -0400
Subject: [Paraview-developers] [Non-DoD Source] Re: Problem with
 ParaView 5.3.0 mac client on some HPC systems
In-Reply-To: <CADHSJjDxRn7KFvBDkGw2YLhr3jveFYeNzaVLgN1ogKCe9WxT0Q@mail.gmail.com>
References: <10A03274360DCF47A6EE78C9952A31CA91E6C2C7@UCOLHPUD.easf.csd.disa.mil>
 <CADHSJjCcQ5k++XORhgHyadpiNNno2SEXAyUtYQrTrx8PM3WXaw@mail.gmail.com>
 <10A03274360DCF47A6EE78C9952A31CA91E6C311@UCOLHPUD.easf.csd.disa.mil>
 <CADHSJjAnNW6GyUHv3wdsL1ONqs0Q+LDhs_DG9qQF+6AAeYJcoQ@mail.gmail.com>
 <10A03274360DCF47A6EE78C9952A31CA91E6E9B3@UCOLHPUD.easf.csd.disa.mil>
 <CADHSJjDxRn7KFvBDkGw2YLhr3jveFYeNzaVLgN1ogKCe9WxT0Q@mail.gmail.com>
Message-ID: <CADHSJjBmK2zTtZvXJtomNrP47oQdfv0CM4FY8V8AMX7fSuP5qA@mail.gmail.com>

Joe,

I can definitely reproduce this on my Mavericks macbook. I'll track it
down and get back to you.

Utkarsh

On Wed, Apr 19, 2017 at 1:38 PM, Utkarsh Ayachit
<utkarsh.ayachit at kitware.com> wrote:
> Odd. I think I have a Mavericks machine at home. Let me try to see if
> I can reproduce it there this evening.
>
> Utkarsh
>
> On Wed, Apr 19, 2017 at 12:00 PM, Hennessey, Joseph G CTR USARMY
> RDECOM ARL (US) <joseph.g.hennessey2.ctr at mail.mil> wrote:
>> Utkarsh,
>>
>> When tested under 10.9.5 with a local pvserver,
>> the problems exists, (ie no visible geometry rendered by the local pvserver).
>> With MacOS 10.12.4 the problem does not occur and the local pvserver,
>> correctly renderers the geometry. This is with the standard MacOS 5.3.0 binary
>> from the kitware site. My problem is I have some systems that cannot yet
>> be upgraded past 10.9.5 due to security restrictions. Any suggestions?
>>
>> Thanks,
>>
>> Joe
>>
>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>> Joseph G. Hennessey Ph.D., SAIC
>> Team SAIC
>> Army Research Lab
>> DOD Supercomputing Resource Center
>>
>> -----Original Message-----
>> From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com]
>> Sent: Tuesday, April 18, 2017 1:41 PM
>> To: Hennessey, Joseph G CTR USARMY RDECOM ARL (US)
>> <joseph.g.hennessey2.ctr at mail.mil>
>> Cc: ParaView Developers <paraview-developers at paraview.org>
>> Subject: Re: [Non-DoD Source] Re: [Paraview-developers] Problem with ParaView
>> 5.3.0 mac client on some HPC systems
>>
>> Odd. I have not see this. Let me know how the local-pvserver test goes. Maybe
>> that'll give us some clues.
>>
>> On Tue, Apr 18, 2017 at 11:33 AM, Hennessey, Joseph G CTR USARMY RDECOM ARL
>> (US) <joseph.g.hennessey2.ctr at mail.mil> wrote:
>>> Utkarsh,
>>>
>>> The render windows has no image rendered in it.
>>> The data will render on the client, but once it gets, complex enough
>>> to render on the server (or you set the limit to 0 MBs) then nothing
>>> is rendered in the render window.
>>> Both are using the OpenGL2 render backend, and the client on the Mac
>>> is the one I have downloaded for the ParaView web site.
>>>
>>> I will check if it runs correctly with a local pvserver, at the next
>>> opportunity.
>>>
>>> Thanks,
>>>
>>> Joe
>>>
>>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>> Joseph G. Hennessey Ph.D., SAIC
>>> Team SAIC
>>> Army Research Lab
>>> DOD Supercomputing Resource Center
>>>
>>>
>>> -----Original Message-----
>>> From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com]
>>> Sent: Tuesday, April 18, 2017 10:05 AM
>>> To: Hennessey, Joseph G CTR USARMY RDECOM ARL (US)
>>> <joseph.g.hennessey2.ctr at mail.mil>
>>> Cc: ParaView Developers <paraview-developers at paraview.org>
>>> Subject: [Non-DoD Source] Re: [Paraview-developers] Problem with
>>> ParaView
>>> 5.3.0 mac client on some HPC systems
>>>
>>> All active links contained in this email were disabled. Please verify
>>> the identity of the sender, and confirm the authenticity of all links
>>> contained within the message prior to copying and pasting the address to a
>>> Web browser.
>>>
>>>
>>> ________________________________
>>>
>>>
>>>
>>> That's odd. Can you clarify what you mean by "not sending rendering image".
>>> Does it mean you just see a blank screen? Just to confirm, both were
>>> built with OpenGL2 rendering backend, right? If you try running
>>> pvserver on the Mac client itself, does that work?
>>>
>>> On Tue, Apr 18, 2017 at 9:43 AM, Hennessey, Joseph G CTR USARMY RDECOM
>>> ARL
>>> (US) <joseph.g.hennessey2.ctr at mail.mil <
>>> Caution-mailto:joseph.g.hennessey2.ctr at mail.mil > > wrote:
>>>
>>>
>>>         Hello,
>>>
>>>         I am having a problem with ParaView 5.3.0 mac client on some HPC
>>> systems.
>>>         When connected to a remote render/data server the remote server is
>>> not
>>>         sending the rendered image to the mac client. The same servers are
>>> sending
>>>         the images to the linux client for 5.3.0, so I do not think it is
>>> the
>>>         server.
>>>         Also, the same systems work just fine with ParaView 5.2.0 servers
>>> and
>>>         clients.
>>>
>>>         Has anyone else seen this issue with the ParaView 5.3.0 mac client?
>>>
>>>         Thanks,
>>>
>>>         Joe
>>>
>>>         ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>>         Joseph G. Hennessey Ph.D., SAIC
>>>         Team SAIC
>>>         Army Research Lab
>>>         DOD Supercomputing Resource Center
>>>
>>>
>>>         _______________________________________________
>>>         Powered by Caution-www.kitware.com <
>>> Caution-http://www.kitware.com >
>>>
>>>         Visit other Kitware open-source projects at
>>> Caution-http://www.kitware.com/opensource/opensource.html <
>>> Caution-http://www.kitware.com/opensource/opensource.html >
>>>
>>>         Search the list archives at:
>>> Caution-http://markmail.org/search/?q=Paraview-developers <
>>> Caution-http://markmail.org/search/?q=Paraview-developers >
>>>
>>>         Follow this link to subscribe/unsubscribe:
>>>
>>> Caution-http://public.kitware.com/mailman/listinfo/paraview-developers
>>> <
>>> Caution-http://public.kitware.com/mailman/listinfo/paraview-developers
>>> >
>>>
>>>
>>>
>>>

From Mark.Olesen at esi-group.com  Sat Apr 22 07:39:17 2017
From: Mark.Olesen at esi-group.com (Mark Olesen)
Date: Sat, 22 Apr 2017 11:39:17 +0000
Subject: [Paraview-developers] good way to wrap different array types?
Message-ID: <DB5PR05MB1288F3D52F494243FDA3FD6CBD1D0@DB5PR05MB1288.eurprd05.prod.outlook.com>

I was considering some cleanup of the OpenFOAM reader - there are loads of special int32, int64 handling. For example near here:
https://gitlab.kitware.com/vtk/vtk/blob/master/IO/Geometry/vtkOpenFOAMReader.cxx#L5716 ,
which also uses a number of helper functions for retrieving back the correct value from the vtkDataArray.

Since the decision of 32/64-bit input is run-time, I don't see any really elegant means of avoiding explicitly specifying and later checking 32 vs. 64-bit.
What I would like is something along the lines of a wrapped vtkDataArray with additional flag (32/64).
For example,

struct someIntArray : public vtkDataArray
{
bool is64;

// Construct with 32/64?
someIntArray(bool use64Bit)
: is64(use64Bit)
{
   if (use64Bit)
   {
    ... etc
   } 

}

The question is if this approach even makes sense. How the constructor should actually look. Should the constructor use a New, smartpointer, whatever?

Any ideas or comments?

Cheers,
/mark

From sumeet.kumar507 at gmail.com  Sat Apr 22 20:09:01 2017
From: sumeet.kumar507 at gmail.com (sumeet kumar)
Date: Sat, 22 Apr 2017 17:09:01 -0700
Subject: [Paraview-developers] NaN values if a node or element id is not
	present.
Message-ID: <CADWn_Z606UE6XkwUhvfMKrwkHX1jw6AiSKr7Ny4fhp7ycYUXQQ@mail.gmail.com>

Hello All,

I am visualizing my output in paraview. But, many times, my nodes number
may or ,may not be in order i.e. For example 1,3,5,7.

If i visualize with my original node number or element number in paraview,
NAN attributes gets introduced for the left out ones. Because of that
auto-range feature of colour bar during visualization do not work properly.
Is there any way out for that.

Thanks
Sumeet

-- 

Sumeet Kumar Sinha
Graduate Student
Phone: (+1)  <%28%2B91%29%209910516219>5306018271
Website : http://www.sumeetksinha.com/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20170422/efab5820/attachment.html>

From david.thompson at kitware.com  Sun Apr 23 16:32:51 2017
From: david.thompson at kitware.com (David Thompson)
Date: Sun, 23 Apr 2017 16:32:51 -0400
Subject: [Paraview-developers] ParaView for Oculus and OpenVR/Vive
In-Reply-To: <CANXz0Sb3sKKz9uJzjup0aZt=1-tuByJ7iew8aRdO3YXWL4b12Q@mail.gmail.com>
References: <CANXz0Sb3sKKz9uJzjup0aZt=1-tuByJ7iew8aRdO3YXWL4b12Q@mail.gmail.com>
Message-ID: <CANpjaa2=MxX-8RC+6LBE-sLrC_P_SHwdXwWVeNW+OkXSkpfLyA@mail.gmail.com>

Hi all,

I've built ParaView master with OpenVR on Linux so I could try out the
SteamVR beta. However, it looks like ParaView's OpenVR UI has changed; now
there is a VR plugin that presents a panel instead of a button the display
properties tab. When I try to create a new connection, the "type" dropdown
is disabled. I have SteamVR running and have been through room setup. Is
there something I need to do to make sure that ParaView can talk to the
OpenVR library?

    Thanks,
    David
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20170423/c1f263e5/attachment.html>

From ken.martin at kitware.com  Sun Apr 23 16:50:09 2017
From: ken.martin at kitware.com (Ken Martin)
Date: Sun, 23 Apr 2017 16:50:09 -0400
Subject: [Paraview-developers] ParaView for Oculus and OpenVR/Vive
In-Reply-To: <CANpjaa2=MxX-8RC+6LBE-sLrC_P_SHwdXwWVeNW+OkXSkpfLyA@mail.gmail.com>
References: <CANXz0Sb3sKKz9uJzjup0aZt=1-tuByJ7iew8aRdO3YXWL4b12Q@mail.gmail.com>
 <CANpjaa2=MxX-8RC+6LBE-sLrC_P_SHwdXwWVeNW+OkXSkpfLyA@mail.gmail.com>
Message-ID: <CANXz0SbFb0B86Xu5nEgxEzxr1XNQWRQQ1uS3=6SpoBRr45FKjQ@mail.gmail.com>

You built

https://gitlab.kitware.com/paraview/paraview/merge_requests/1492

?



On Sun, Apr 23, 2017 at 4:32 PM, David Thompson <david.thompson at kitware.com>
wrote:

> Hi all,
>
> I've built ParaView master with OpenVR on Linux so I could try out the
> SteamVR beta. However, it looks like ParaView's OpenVR UI has changed; now
> there is a VR plugin that presents a panel instead of a button the display
> properties tab. When I try to create a new connection, the "type" dropdown
> is disabled. I have SteamVR running and have been through room setup. Is
> there something I need to do to make sure that ParaView can talk to the
> OpenVR library?
>
>     Thanks,
>     David
>



-- 
Ken Martin PhD
Distinguished Engineer
Kitware Inc.
28 Corporate Drive
Clifton Park NY 12065

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

From david.lonie at kitware.com  Mon Apr 24 10:57:06 2017
From: david.lonie at kitware.com (David Lonie)
Date: Mon, 24 Apr 2017 10:57:06 -0400
Subject: [Paraview-developers] good way to wrap different array types?
In-Reply-To: <DB5PR05MB1288F3D52F494243FDA3FD6CBD1D0@DB5PR05MB1288.eurprd05.prod.outlook.com>
References: <DB5PR05MB1288F3D52F494243FDA3FD6CBD1D0@DB5PR05MB1288.eurprd05.prod.outlook.com>
Message-ID: <CA+=e1ou0nt37yzZBmJtaijwM1FB=MoKCEspcTH6mb_LPGn9crA@mail.gmail.com>

On Sat, Apr 22, 2017 at 7:39 AM, Mark Olesen <Mark.Olesen at esi-group.com> wrote:
> I was considering some cleanup of the OpenFOAM reader - there are loads of special int32, int64 handling. For example near here:
> https://gitlab.kitware.com/vtk/vtk/blob/master/IO/Geometry/vtkOpenFOAMReader.cxx#L5716 ,
> which also uses a number of helper functions for retrieving back the correct value from the vtkDataArray.
>
> Since the decision of 32/64-bit input is run-time, I don't see any really elegant means of avoiding explicitly specifying and later checking 32 vs. 64-bit.
> What I would like is something along the lines of a wrapped vtkDataArray with additional flag (32/64).
> For example,
>
> struct someIntArray : public vtkDataArray
> {
> bool is64;
>
> // Construct with 32/64?
> someIntArray(bool use64Bit)
> : is64(use64Bit)
> {
>    if (use64Bit)
>    {
>     ... etc
>    }
>
> }
>
> The question is if this approach even makes sense. How the constructor should actually look. Should the constructor use a New, smartpointer, whatever?

Feel free to clean up the internals of that class as much as you like :-)

As for the data array class, I like the idea, but wouldn't try to make
a full-fledged subclass of vtkDataArray. VTK supports arbitrary
subclasses of vtkDataArray, but using the built-in versions gives much
better performance since performance-critical areas of code in VTK
have fast-paths implemented for them. Plus it's a giant pain to get
the APIs right for new vtkDataArrays :-)

Instead, I think an internal wrapper class that basically encapsulates
the helper functions and the use64bit boolean would simpler, e.g.

class vtkFOAMLabelArray
{
  vtkNew<vtkTypeInt32Array> Data32;
  vtkNew<vtkTypeInt64Array> Data64;
  bool Use64BitArray;

public:
  vtkFOAMLabelArray(bool use64BitArray) {...}

  vtkTypeInt64 GetValue(...) {...}
  void SetValue(..., vtkTypeInt64) {...}

  vtkDataArray *GetDataArray() {...}
};

You can interact with the arrays through the wrapper API, and then
call GetDataArray at the end when building up the final data set.

HTH,
Dave

From andy.bauer at kitware.com  Mon Apr 24 11:57:41 2017
From: andy.bauer at kitware.com (Andy Bauer)
Date: Mon, 24 Apr 2017 11:57:41 -0400
Subject: [Paraview-developers] Reinitialization of Catalyst
In-Reply-To: <20170419172055.GC17603@megas.kitware.com>
References: <2ec2ce94a66718f6e4215334706847f3.startmail@www.startmail.com>
 <8fd98f3db764f57f8205acb900019843.startmail@www.startmail.com>
 <20170419172055.GC17603@megas.kitware.com>
Message-ID: <CAMaOp+HwZijYogGCp3NkX1pBnTig69-rtje6sCEnWgrMY+Kfmg@mail.gmail.com>

Hi Thomas,

My recommendation would be to skip Catalyst's Fortran API and play around
with the Catalyst pipelines manually. Then you can add and remove the
pipelines yourself and you should be able to get rid of the warning.

Alternatively, you should be able to get rid of the warning if you go
through and create the vtkCPProcessor object yourself instead of going
through the Fortran API.

On Wed, Apr 19, 2017 at 1:20 PM, Ben Boeckel <ben.boeckel at kitware.com>
wrote:

> On Wed, Apr 19, 2017 at 18:41:54 +0200, thomasblome at startmail.com wrote:
> > But I guess one can savely ignore this warning?!
>
> Looking at the code, it is just a warning. It looks like the list of
> timesteps is not cleared internally (there is no method exposed to do
> this either). It can be ignored only if the TIME_RANGE output can be
> ignored: that is generated by getting the first time step and the last
> time step. It should work if the start time step for all of your runs
> starts at the same value though.
>
> --Ben
> _______________________________________________
> 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/20170424/9a91e86b/attachment.html>

From Mark.Olesen at esi-group.com  Mon Apr 24 18:30:57 2017
From: Mark.Olesen at esi-group.com (Mark Olesen)
Date: Mon, 24 Apr 2017 22:30:57 +0000
Subject: [Paraview-developers] good way to wrap different array types?
In-Reply-To: <CA+=e1ou0nt37yzZBmJtaijwM1FB=MoKCEspcTH6mb_LPGn9crA@mail.gmail.com>
References: <DB5PR05MB1288F3D52F494243FDA3FD6CBD1D0@DB5PR05MB1288.eurprd05.prod.outlook.com>,
 <CA+=e1ou0nt37yzZBmJtaijwM1FB=MoKCEspcTH6mb_LPGn9crA@mail.gmail.com>
Message-ID: <DB5PR05MB12888277B9F60FFC53DCB147BD1F0@DB5PR05MB1288.eurprd05.prod.outlook.com>

Thanks Dave for the basics.
If there is any rewriting, I think we'll need something more coordinated than gitlab merge requests.
Either email, or some design document/discussion on gitlab first to get the main layout etc.

For the reader code itself, we really need a separate 'OpenFOAM' directory, and later a namespace for all the bits and pieces.
For the git mv, should I raise an issue, or can someone from KitWare just do it?

Cheers,
/mark
________________________________________
From: David Lonie <david.lonie at kitware.com>
Sent: Monday, April 24, 2017 4:57:06 PM
To: Mark Olesen
Cc: ParaView Developers
Subject: Re: [Paraview-developers] good way to wrap different array types?

On Sat, Apr 22, 2017 at 7:39 AM, Mark Olesen <Mark.Olesen at esi-group.com> wrote:
> I was considering some cleanup of the OpenFOAM reader - there are loads of special int32, int64 handling. For example near here:
> https://gitlab.kitware.com/vtk/vtk/blob/master/IO/Geometry/vtkOpenFOAMReader.cxx#L5716 ,
> which also uses a number of helper functions for retrieving back the correct value from the vtkDataArray.
>
> Since the decision of 32/64-bit input is run-time, I don't see any really elegant means of avoiding explicitly specifying and later checking 32 vs. 64-bit.
> What I would like is something along the lines of a wrapped vtkDataArray with additional flag (32/64).
> For example,
>
> struct someIntArray : public vtkDataArray
> {
> bool is64;
>
> // Construct with 32/64?
> someIntArray(bool use64Bit)
> : is64(use64Bit)
> {
>    if (use64Bit)
>    {
>     ... etc
>    }
>
> }
>
> The question is if this approach even makes sense. How the constructor should actually look. Should the constructor use a New, smartpointer, whatever?

Feel free to clean up the internals of that class as much as you like :-)

As for the data array class, I like the idea, but wouldn't try to make
a full-fledged subclass of vtkDataArray. VTK supports arbitrary
subclasses of vtkDataArray, but using the built-in versions gives much
better performance since performance-critical areas of code in VTK
have fast-paths implemented for them. Plus it's a giant pain to get
the APIs right for new vtkDataArrays :-)

Instead, I think an internal wrapper class that basically encapsulates
the helper functions and the use64bit boolean would simpler, e.g.

class vtkFOAMLabelArray
{
  vtkNew<vtkTypeInt32Array> Data32;
  vtkNew<vtkTypeInt64Array> Data64;
  bool Use64BitArray;

public:
  vtkFOAMLabelArray(bool use64BitArray) {...}

  vtkTypeInt64 GetValue(...) {...}
  void SetValue(..., vtkTypeInt64) {...}

  vtkDataArray *GetDataArray() {...}
};

You can interact with the arrays through the wrapper API, and then
call GetDataArray at the end when building up the final data set.

HTH,
Dave

From cory.quammen at kitware.com  Tue Apr 25 09:37:34 2017
From: cory.quammen at kitware.com (Cory Quammen)
Date: Tue, 25 Apr 2017 09:37:34 -0400
Subject: [Paraview-developers] NaN values if a node or element id is not
	present.
In-Reply-To: <CADWn_Z606UE6XkwUhvfMKrwkHX1jw6AiSKr7Ny4fhp7ycYUXQQ@mail.gmail.com>
References: <CADWn_Z606UE6XkwUhvfMKrwkHX1jw6AiSKr7Ny4fhp7ycYUXQQ@mail.gmail.com>
Message-ID: <CAB5Fpx7cjDZSN2+HY7tqYKtOrtZWJReoBrWhVCCMF1QYNOCaww@mail.gmail.com>

Sumeet,

I believe the presence of NaNs should not affect the auto range
computation. The ParaView test suite has a test where the data has NaNs
(pv.RenderNan). Running that test manually I can rescale the range just
fine and see the NaN values with the special NaN color in the color map.

Do you have a sample file you can share that shows the behavior you see?

Thanks,
Cory

On Sat, Apr 22, 2017 at 8:09 PM, sumeet kumar <sumeet.kumar507 at gmail.com>
wrote:

> Hello All,
>
> I am visualizing my output in paraview. But, many times, my nodes number
> may or ,may not be in order i.e. For example 1,3,5,7.
>
> If i visualize with my original node number or element number in paraview,
> NAN attributes gets introduced for the left out ones. Because of that
> auto-range feature of colour bar during visualization do not work properly.
> Is there any way out for that.
>
> Thanks
> Sumeet
>
> --
>
> Sumeet Kumar Sinha
> Graduate Student
> Phone: (+1)  <%28%2B91%29%209910516219>5306018271 <(530)%20601-8271>
> Website : http://www.sumeetksinha.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
>
>


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

From david.lonie at kitware.com  Tue Apr 25 09:45:46 2017
From: david.lonie at kitware.com (David Lonie)
Date: Tue, 25 Apr 2017 09:45:46 -0400
Subject: [Paraview-developers] good way to wrap different array types?
In-Reply-To: <DB5PR05MB12888277B9F60FFC53DCB147BD1F0@DB5PR05MB1288.eurprd05.prod.outlook.com>
References: <DB5PR05MB1288F3D52F494243FDA3FD6CBD1D0@DB5PR05MB1288.eurprd05.prod.outlook.com>
 <CA+=e1ou0nt37yzZBmJtaijwM1FB=MoKCEspcTH6mb_LPGn9crA@mail.gmail.com>
 <DB5PR05MB12888277B9F60FFC53DCB147BD1F0@DB5PR05MB1288.eurprd05.prod.outlook.com>
Message-ID: <CA+=e1ou1X6x9_BYrPBNYU4tXUtxJUR6rEeiHWsrQfJWj97OpoQ@mail.gmail.com>

On Mon, Apr 24, 2017 at 6:30 PM, Mark Olesen <Mark.Olesen at esi-group.com> wrote:
> Thanks Dave for the basics.
> If there is any rewriting, I think we'll need something more coordinated than gitlab merge requests.
> Either email, or some design document/discussion on gitlab first to get the main layout etc.
>
> For the reader code itself, we really need a separate 'OpenFOAM' directory, and later a namespace for all the bits and pieces.
> For the git mv, should I raise an issue, or can someone from KitWare just do it?

I'm cc'ing Mathieu Westphal on this, as I think he's the one doing
OpenFOAM work these days. I'm not actively working on OpenFOAM related
projects anymore, and don't really have much familiarity with the
format aside from a few one-off fixes. As such, I don't really feel
comfortable making any decisions for a rewrite of this reader. I
support the decision to clean it up, but don't really have any free
cycles to spend working on it.

I think there are a few other contributors that work with this format,
so starting a discussion thread on the mailing list to gauge support
would be a good first step, I think.

Cheers,
Dave

From david.thompson at kitware.com  Tue Apr 25 18:33:13 2017
From: david.thompson at kitware.com (David Thompson)
Date: Tue, 25 Apr 2017 18:33:13 -0400
Subject: [Paraview-developers] ParaView for Oculus and OpenVR/Vive
In-Reply-To: <CANXz0SYbCMsQzw5OOcQpXED9oHqTag2rbWSH4DBTPJXL3wdHvw@mail.gmail.com>
References: <CANXz0Sb3sKKz9uJzjup0aZt=1-tuByJ7iew8aRdO3YXWL4b12Q@mail.gmail.com>
 <CANpjaa2=MxX-8RC+6LBE-sLrC_P_SHwdXwWVeNW+OkXSkpfLyA@mail.gmail.com>
 <CANXz0SbFb0B86Xu5nEgxEzxr1XNQWRQQ1uS3=6SpoBRr45FKjQ@mail.gmail.com>
 <CANpjaa3Edt3fTpw=gVuPHBsfU5en+-534mQTzx04gGwwFJ9EOQ@mail.gmail.com>
 <CANXz0SYbCMsQzw5OOcQpXED9oHqTag2rbWSH4DBTPJXL3wdHvw@mail.gmail.com>
Message-ID: <1DFECCFB-B592-495A-A186-320D8446E058@kitware.com>

Hi all,

>> ... I built PV master with
>> 
>> + PARAVIEW_BUILD_PLUGIN_VRPlugin:BOOL=TRUE
>> + Module_vtkRenderingOpenVR:BOOL=ON
>> 
> https://gitlab.kitware.com/paraview/paraview/merge_requests/1492
>> 
>> I take it I should build the MR?
>> 
> Yes. I believe the VRPlugin is support for VRUI. The MR adds support (and a PV cmake option) for openvr.

Success on x86_64 Ubuntu 16.04.2 (with some hacks, described below for the record)!

Also, at least on my machine, the VTK OpenVR dashboard appears right-side up, but the y location of the pointer appears to be flipped (i.e., aiming at the top of the dashboard highlights the bottom row of buttons; aiming near the bottom of the dashboard highlights the top row of buttons). Maybe some transforms have changed from the release to the beta I'm running?

	David

# Using the SteamVR beta with PV on Linux


1. After installing SteamVR, and opting into the beta I could not start SteamVR from the desktop (it opened a dialog claiming that a download had to complete, but it lies). However, I could start it from the command line with

  ~/.local/share/Steam/ubuntu12_32/steam-runtime/run.sh ~/.local/share/Steam/steamapps/common/SteamVR/tools/bin/vrmonitor.sh

2. But first (before running vrmonitor, anyway), I had to create symlinks to some vulkan and udev libraries included with SteamVR that were not in the system search path. This is a hack, but it works for now:

  sudo -s # i.e., run the following as root
  cd /usr/lib/x86_64-linux-gnu
  ln -s ~/.local/share/Steam/ubuntu12_32/steam-runtime/amd64/usr/lib/x86_64-linux-gnu/libvulkan.so.1.0.39 .
  ln -s libvulkan.so.1.0.39 libvulkan.so.1.0
  ln -s libvulkan.so.1.0.39 libvulkan.so.1
  ln -s libvulkan.so.1.0.39 libvulkan.so
  ln -s ~/.local/share/Steam/ubuntu12_32/steam-runtime/amd64/lib/x86_64-linux-gnu/libudev.so.0 .
  ldconfig


From cory.quammen at kitware.com  Fri Apr 28 11:05:55 2017
From: cory.quammen at kitware.com (Cory Quammen)
Date: Fri, 28 Apr 2017 11:05:55 -0400
Subject: [Paraview-developers] ParaView 5.4 release cycle starts next week
Message-ID: <CAB5Fpx6hq7tcvzAC-Kwjn4QRbG1cewkL7rEZnXG=HWQa6SZcsg@mail.gmail.com>

Dear ParaView developers,

The ParaView 5.4 release cycle begins next week! As in previous
releases, we will put out some release candidates leading up to the
final 5.4 release scheduled for June 9, 2017.

If you have new features that you would like to see in the 5.4
release, please try to get them in before Friday, May 5 (next week) so
that we can focus on bug fixes after the release candidate cycle
starts.

FYI, other scheduled releases are posted at
https://gitlab.kitware.com/paraview/paraview/milestones.

Thanks!
Cory

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